I have a Verizon G3 running stock 4.4.2 rom, it is also rooted with stump root. I have not changed anything extreme with the root only used G3 TweaksBox to change colors and themes. I also installed the google dialer and contacts apps by downloading the .apk files and moving them manually, these have been working fine. I tried to change the LgInCallUI.apk with a different black themed one I found on the forums and overwrote the original one however it is not working now (also forgot to backup the original one). When I try to make a call I hear the call connect tone however the screen never changes and stays in the dialer app, It also does not change when a call comes in, the ringtone goes off but there is no way to answer the call. I tried removing the file from the priv app folder and trying to manually move it again by changing the permissions and moving it back to the folder but this did not help. There is also a file in the priv app folder called LGInCallUI.odex that I think was a part of the old version since it is dated a few months old like all of the other files. Any assistance would be appreciated, thank you.
Related
I installed the stock MMS.apk file on my de'odexed stock rom (rooted of course). Everything worked well and the app runs, but when reading text threads there is an ugly white border around the edge of the screen, its strange. Its not present when viewing the list of conversations, only in the thread view. I'm not sure if that's how its supposed to look or not, but if not, anyone have any idea how to fix this?
I'll get a screenshot up as soon as I get home.
I first obtained the MMS.apk from the cyanogen rom, then thinking that it might be modified and thus creating my problem, I grabbed the AOSP version from this thread:
http://forum.xda-developers.com/showthread.php?t=789493
Any help will be greatly appreciated.
UPDATE:
Found another thread where people are experiencing the same issue, apparently its a problem with how sense handles the application:
http://forum.xda-developers.com/showthread.php?t=752604
I attempted to open up the Mms.apk (AOSP version) with APKtool and play around with the xml files for the UI, but wasn't able to get it to recompile and test any changes I made, the app would just crash on launch. I simply made a few changes to the colors, but I admittedly don't really know what I'm doing and it wouldn't run. If anyone who's more experienced in this area could offer some advice I'll try again.
That's a picture of the issue, it appears in both landscape and portrait mode.
Texts were blacked out just for privacy sake.
Well after a few hours of messing around in the XML files for the AOSP messaging app, I was able to find a solution to this issue. I modified the XML file to have it correctly display the black color background when using the black theme. I was not able to eliminate the border entirely, but by changing the scrollbar type from Inset to Overlay I was able to make it uniform and far more visually pleasing.
I have attached my modified Mms.apk file, feel free to test it out.
For the specifics of what I did for those who are interested:
Two files were modified in the apk
- /res/layout/compose_message_activity.xml
- /res/layout/compose_message_activity_black.xml
In both files I changed the scrollbarStyle propery to "insideOverlay", in addition to removing the reference to always show the scrollbar track.
In the black xml file I changed the background color to "@android:color/black".
The original XML files were extracted using APKTool and Recompiled to their binary format, then reinserted into the original apk without resigning.
This is awesome! ... Except it doesn't filter out the VVM message streams that come through. :|
I haven't encountered this problem though I use google voice so I'm not really sure what it is you're referring to.
Sent from my PC36100 using XDA App
ty!
beautiful ty!!!!!!!!!
Imma cry
I cant send mms!
Try turning off wifi while sending/receiving mms
no wifi
i don't have wifi on when i do this i just have 3g on so i can send mms!
i zipped the file with the one that had the white outline .is there a way to make this new apk. file into a .zip file for me ?
I'd imagine you could simply replace the APK file in your zip with my modified one and install that way. Use a program like winrar or 7zip to replace the apk within the zip.
tehpsyc said:
I'd imagine you could simply replace the APK file in your zip with my modified one and install that way. Use a program like winrar or 7zip to replace the apk within the zip.
Click to expand...
Click to collapse
sorry but i cant find either of thoses programs u mention to replace the APK file in my zip with your modified version .is there another program or a manual way of doing this process ?
how do i install this? since it's an APK, i thought i'd just install it from Astro but it says it's already installed and asked if i wanted to uninstall.
To install this you need to either delete or rename the Mms.apk that's already on your phone in the /system/app directory (I just rename to Mms.apk.bak) and then copy the modified one into that same directory followed by a restart of the phone. Because its a system app you cant install it the same way you would a regular apk, at least from my understanding.
You will need to get write access to the system directory to accomplish this (I used an app on the market called root explorer, though you can also do all this through the ADB shell)
Trying to edit some of the images of the yahoo mail app. The previous version I pulled the images I wanted to change from the apk, edited them (just changed the color) and pushed them back into the apk. Put the apk on my phone and installed it...no problems. Now yahoo released a newer verison of its mail app and I go to do the same thing. I used the 10 images I edited from the previous version and put them into the new version since the unedited ones in the new version were the same file names as the ones I edited. I pushed my edited images to the new version and sent the apk to my phone. But it won't install. I have tried everything I can find (or Google) and still the apk will not install. Attached are my two versions. The old version which has the edited images and works perfect, and the newer version that has the edited images and does not want to work. The zip file has the images I edited. Anyone want to tell me what I'm doing wrong?
Put it in system/app
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
Pushed to system/app, tried to open app and it gives an FC. I tried redownloading from market, backing up, copying and editing the backup and repushing to system/app (after uninstalling the untouched version) but still gives FC. I know its something with the edited images since the newer untouched version installs fine with no problems.
Did you sign the files?
Make sure there weren't any .9.pngs that you edited also. Those are special.
No I did not sign the apk. I was told before that you don't need to resign an apk, just check the "unknown sources" checkbox in the application menu under settings. But quite a few of these do have .9.PNG in the filename. I looked up DrawPatch9 images and am confused about what they are and how to modify a png into one. I am surprised the modded images will work in 1.3.6 and not 1.3.7.
So I googled and D/L'ed a signing tool, signed the apk (or at least the program told me it was signed) and tried to install on my phone with no success. I tried pushing it manually again and it gave an FC when I try to run it. Most likely the .9.PNG's are the problem. Anyone recommend a site/program to use to fix the .9.PNG's?
I have a ZL running 4.2.2 and it is rooted.
I wanted the upgraded mail app that is found on the Z1.
I got my hands on the semcemail.apk v5 and used root explorer to move it into system\apps and set the permissions to rw r r. I first tried having the name be different (semcemail2) to see if I could run it along side the native one. On reboot it would not now up as an app.
Then I figured it must be a core app and have the same file name but when the original apk of the same name is over-written the mail service fails and the app simply doesn't run.
Replacing the original gets me back to where I started.
Am I missing something? Others seem to have been able to get it to run on non z1 with these steps.
Hello,
for those who would like to try and put G2 keyboard on Optimus G running stock 4.4.2 KK, here are the files that I used to make it working. Since upgraded to stock KK I tried different versions of keyboard files, and I used to get FC on many of them.
This is the combination that works for me.
First, be sure to have another keyboard installed, just for any case, since if you get FC it would be hard to revert your files as it was because you will get FC message every second.
This is how I did it (maybe not the right way). Switch as default keyboard, to another one, I have installed google keyboard with numerical 5th row from http://forum.xda-developers.com/showthread.php?t=2657791
Then:
Here are the files: https://www.mediafire.com/folder/0d...ajajh9,vt3d7wl6wyg3wv3,r364kdi1go6wwil/shared
Backup your old files first.
Copy G2LGIME.apk to system/app, rename it to LGIMEbin.apk, change permission to 644. Delete old apk and odex file.
Themes you can install as common apk.
Copy other files to system/lib, also do a backup first. Change permission to 644.
Edit buildprop, and add lines:
ime_extend_row_keyboard=true
ime_onehand_keyboard=true
ime_split_keyboard=true
ime_vibration_pattern=0:20
For Emoji, add the lines:
ro.config.libemoji=libemoji_lge.so
ro.lge.capp_emoji=true
Save and reboot. It should work.
Only thing it does not work here, is voice input, but you can make it work, if you install Voice Search by Google, from Play store.
Best regards
You have G3 keyboard with 5th numerical 5th row? Sr for my bad english
I hate the G3's emoticons, and I'd love to use the aosp android emoticons. I had a Galaxy Nexus running CM11 before this G3 and I miss those emojis dearly.
I see that in the system/fonts/ folder of the root there are 4 total emoticon .ttf files and I made the three of them, LG_Emoticon.ttf, LG_Emoticon_AME.ttf, and LG_Emoticon_nonAME.ttf null by adding .nothanks to the end of all three. Which leaves only the AndroidEmoji.ttf file valid, I assumed the system would fall back upon it with the others being no longer valid file types. I rebooted and nothing happened, still the same ugly ass emoticons. I checked and the file names remained with the .nothanks on the end. I also tried renaming the AndroidEmoji.ttf to LG_Emoticon.ttf and still nothing happened.
Has anyone succesfully changed the emojis on their G3? If so how? Im open to all suggestions.
Thanks