I found this...
http://forum.xda-developers.com/showthread.php?p=19819539#post19819539
but I'm not familiar enough with APK Manager to do this...anybody want to take a crack at this that knows what they are doing?
I don't believe the Settings.apk is the same (file size is smaller) as the one found in the Note. Possibly because there are extra options (i.e. Pen settings, etc)? This is why I didn't try copying the file from the link to test it.
In either case thanks in advance! I'm using Stock ROM and just want to replace and remove 'mostly' all remnants of AT&T (including Software Update) now that I don't need it since my kernel is rooted.
Thanks again!
Related
Ok I've done a little research on this but can't find what I'm looking for exactly.
I really don't like the Blur Contacts app. I have figured out how to filter things correctly so I only get my usual Google contacts but I'd still like to get one feature back that I had on CM - direct dial and direct text message shortcuts. They were supported through the AOSP Contacts app from what I can figure out. The Blur Contacts app has something similar but it doesn't work consistently. Does anyone know if it's possible to install the Contacts.apk and ContactsProvider.apk extracted from CM 6.1.1 (what I had on my EVO) and bring them over to my rooted Atrix?
I'd like a different contacts manager as well. This one combines services which is not what I want/need. Any suggestions that are similar to CM contacts on N1 would be appreciated!
+1 more here for a different contacts app.
+1
Bump
I'd also love the AOSP dialer
phobos512 said:
install the Contacts.apk and ContactsProvider.apk extracted from CM 6.1.1
Click to expand...
Click to collapse
I tired this few days ago, nothing worked. =/
Click install throws an error and says it can't be installed. Pushing the apk to /system just has no result.
Moto's contacts are terrible.
How to Install Android AOSP Apk, in any system.
Find the AOSP apps from a CM6 build by unzipping and pulling the .apk file like browser.apk. Install "File Expert" (Free and amazing file browser with full root access and alteration capabilities application)
Copy the .apk you wish to have on to your phones SD Card
Run File Expert,
hit menu/more/File Explorer settings. Then check "Root Explorer" on the bottom.
hit menu/more/mount/Mount As Read Write
Browse to /System/Apps Find the App you wish to replace with the AOSP version.
Hold Down on the App and when the options come up choose file operations and rename to something like application name.apk.bak
Browse to your SD Card find your app. hold down to choose file operation then choose copy.
Go back to /System/Apps then hit Menu button and choose paste.
Locate the app you just pasted and hold down on it and in file operations choose "permissions" Check Everything and exit out of File Expert
Note: You may need to redo the shortcuts for the app on your desktop and or launcher.
Note: Must have a rooted phone.
Note: 2.3.3 apps may or may not work on 2.2 Android Roms and vice versa.
Note: if this causes errors or failures delete the new apk and rename the old apk to its original name.
Good luck!!
can someone upload the contacts apks?
Sent from my MB860
Download the latest Cyanogen mod for your phone or any. Unzip on your pc and go to the folder labeled system/apps. Get the apps you want from there and pass them to your phone via USB to your phone then follow my previous instructions.
I have already tried to install a different dialer/contacts app. I had no luck, I think that the stock dialer/contacts are to deeply tied into motoblur and the phone system. It won't break your system but you just will not have a dialer or contacts.
Did you try it to my exact instructions. Making sure to you the cyanogen mod that corresponds to your version of android? If it didnt show up on your list you may have tried the 2.3.3 instead of s2.2 dialer.
Oh, I would love to hear the solution to this. I have been trying to figure this out for a couple days now. I pulled Contacts.apk from a Liberty backup I have and have been trying to replace BlurContacts.apk with it to no avail. I believe someone above may have touched on it. Possibly to change when other things look for BlurContacts, and instead refer to Contacts.apk?
I have tried several different contact apps. None work I think that the blur apps are to deeply tied into the system to allow a change.
Bump
any progress ??
sent from my gingerblur 3.1 atrix. with 1% mod & clock delete
I've actually been using GoContacts. It seems to work like how I want my contacts to work(I.E like ASOP) plus allows for a little bit more tweakability.
Love the write up here: http://forum.xda-developers.com/showthread.php?t=1208320
Trying to follow it and I keep getting the device to boot, however, the Settings icon (Settings.apk and Settings.odex) are what I modified on an Asus Transformer Prime. I do believe it has to do with signature check. I compared the HEX of the files using Beyond Compare and the signature, which I believe is in the first few lines, is completely different than original. Also, I had to add a few .jar's from the /system/framework of the Transformer Prime's system in order to get it to deodex and odex properly.
Am I missing something? Could the signature be copied via a hex editor instead of using the dd command. If so, which HEX is start and end position? Isn't there a trailer as well that needs removed??
Please help if you have any idea about ODEX vs DEODEX. I prefer ODEX which is why I am trying to modify manually and put back. Plus, I learn more this way, which is +1....even though, it's alot more work, I don't mind.
Has anyone ever used this method? I don't want a completely DEODEXED ROM, in fact, I would prefer if NONE of it was DEODEXED which is why I am doing it the hard way Any help is much appreciated.
bump....need an answer please guys...
older thread but I'm bumping this because I'm running into a similar issue. I prefer most of my rom to be odex apart from settings, systemui, framework-res, and my services.jar.
I know that I ask a lot of questions, some of them just a bit bonehead. I really appreciate everyones help here.
So, I finally for 1.4.3 running, rooted it, restored my backup from titanium backup. I have noticed, however, that when Installed my custom resources like SystemUI.apk and framework_res.apk there are a few little bugs here and there in the text it displays...
For instance, when you hit the menu button and it displays the block of buttons for some apps (like ADW / ADW EX and Titanium Backup) the arrow that used to say "More" now says "Allows the Application to set an alarm in an" and then it trails off. Obviously this is a mistake, probably they changed some reference between files in the framework folder. Additionally, the "Set as Default" now displays a bunch of %'s and letters as if, again, some reference is bad.
I like running the current software, these are minor issues. I'm sure they can be fixed, just not sure how. I was kind of stupid and didn't make a backup of my original framework_res.apk and SystemUI.apk files from the Nook after I updated but before I replaced them. Stupid of me, I know. I assumed from the file dates that nothing was changed. So, I can't really go back to the originals until I get it sorted out.
Anyone have any suggestions? If perhaps someone who has updated to 1.4.3 could send me those two files so I could make the mods myself on the new APK files? I'm almost positive it is framework_res.apk that is the culprit.
Does anyone have framework_res.apk from v1.4.3?
titanshadow said:
Does anyone have framework_res.apk from v1.4.3?
Click to expand...
Click to collapse
You can just get the full 1.4.3 update zip from B&N yourself, unpack the zip, and it's all there: http://su.barnesandnoble.com/nook/nooktablet/1.4.3/nZU6wA3e3CCckqXRQI6gqoT0ZKAA8MujlFdXFU08/nooktablet_1_4_3_update.zip
(I found that by looking here first: http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
lack_android said:
You can just get the full 1.4.3 update zip from B&N yourself, unpack the zip, and it's all there: http://su.barnesandnoble.com/nook/n...0ZKAA8MujlFdXFU08/nooktablet_1_4_3_update.zip
(I found that by looking here first: http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Click to expand...
Click to collapse
To my knowledge you can't just unpack them anymore, I tried and I just got a large archive file that I didn't have anything to decompress. Do you know what program to use to unpack the archive inside the zip?
titanshadow said:
To my knowledge you can't just unpack them anymore, I tried and I just got a large archive file that I didn't have anything to decompress. Do you know what program to use to unpack the archive inside the zip?
Click to expand...
Click to collapse
I believe it is '7zip' to the rescue.
Finally got it... Now trying to figure out how to modify it, the contents are a lot different...
I'm on stock gingerbread 2.3.4. I plan to use this, to get rid of my stock battery icon
http://forum.xda-developers.com/showthread.php?t=1159848
but i've hesitated because of the AT&T label. And framework-res.apk file sizes seem to be different.(edit: of course i compared mine with the untouched file given)
So as an international user, should I avoid it or is it OK for me to flash it?
And it seems to replace framework-res.apk and SystemUI.apk; what if i do it with root explorer?
Should I be worried about anything? (except file permissions)
I can't advise neither for nor against trying it out, but if you do some framework edits/mods, of course the sizes are going to be different. Framework files are not machine code where you need to deploy tricks such as byte padding in order to preserve the original file size.
ravilov said:
I can't advise neither for nor against trying it out, but if you do some framework edits/mods, of course the sizes are going to be different. Framework files are not machine code where you need to deploy tricks such as byte padding in order to preserve the original file size.
Click to expand...
Click to collapse
My comparison wast between my original files and the original (untouched) backup files given in the same thread; it seems that AT&T framework and european frameworks differ in size.
Oh I see. Well I can see that happening too. There is after all a reason they would release two separate variants of the firmware, right?
ravilov said:
Oh I see. Well I can see that happening too. There is after all a reason they would release two separate variants of the firmware, right?
Click to expand...
Click to collapse
So I think I'd better create my own backup zip
Oh yes, definitely. Always prefer your own backups over anyone else's.
Answer to my own question is: NO. At least the one i used is not internationally compatible. causes bootloop.
I've seen previously that you can modify 'more_keys_for_smiley' in LatinIME.apk to modify the predefined smilies in the keyboard ( http://forum.xda-developers.com/showthread.php?p=23362533 ).
I'm trying to do this for LatinImeGoogle.apk.
I've got it decompiled with apktool, but I can't seem to find where 'more_keys_for_smiley' is defined to change it. The only reference to it inside of that apk is in key_styles_common.xml where it has:
<key-style latin:moreKeys="!text/more_keys_for_smiley" latin:backgroundType="functional" latin:keyOutputText=" " latin:keyLabel="" latin:keyLabelFlags="hasPopupHint" latin:styleName="enterKeyStyle" />
Can anyone help me locate more_keys_for_smiley so I can modify it? Does the "!text" refer to a different package?
Thanks in advance for any help.
Ok, thanks to someone's help I was able to figure out that the string is now located in the odex file for the keyboard. I was able to deodex LatinImeGoogle.odex using baksmali and edited the file com/android/inputmethod/keyboard/internal/KeyboardTextsSet.smali. I then used smali to recreate the odex file, but pushing it to my device and rebooting causes the keyboard to not load. Do I need to do anything special with this new odex file?
I tried following tutorials ( http://forum.xda-developers.com/showthread.php?t=1208320 ) and using automatic batch scripts ( http://forum.xda-developers.com/showthread.php?p=31360029 ) for recreating the new odex file and copying the signature from the old one, but I could not get it to work. At best I got the keyboard to load and instantly crash, at worst it wouldn't even load the keyboard upon boot.
Anyone want to offer some advice or take a stab at this?
Seems like your doing exactly what i'm trying to accomplish, and had success, so i'm gonna ask a couple questions, but first some background info.
I'm using a (Verizon) Galaxy Nexus, CM10.1 Clockwork Recovery, GAPPS. (no custom Kernels, etc)
I'm a windows guy, definitely a noob to linux, i'm comfortable following the more complicated instructionals, but traveling off the beaten path is difficult for me.
I was able to use apktool tool to decompile Latinime.apk, and i found KeyboardTextsSet.smali, and the smileys i want modified.
Is it as simple as recompiling and installing it? (remove/uninstall keyboard via TitaniumBackup first?)
You refer to a LatinImeGoogle.odex, is this only relevant to someone using an odexed rom?
I appreciate greatly any assistance you are able to provide!:good:
PrettyPistol555 said:
Seems like your doing exactly what i'm trying to accomplish, and had success, so i'm gonna ask a couple questions, but first some background info.
I'm using a (Verizon) Galaxy Nexus, CM10.1 Clockwork Recovery, GAPPS. (no custom Kernels, etc)
I'm a windows guy, definitely a noob to linux, i'm comfortable following the more complicated instructionals, but traveling off the beaten path is difficult for me.
I was able to use apktool tool to decompile Latinime.apk, and i found KeyboardTextsSet.smali, and the smileys i want modified.
Is it as simple as recompiling and installing it? (remove/uninstall keyboard via TitaniumBackup first?)
You refer to a LatinImeGoogle.odex, is this only relevant to someone using an odexed rom?
I appreciate greatly any assistance you are able to provide!:good:
Click to expand...
Click to collapse
Yes, you should be able to modify KeyboardTextsSet.smali and then recompile and install the keyboard. I never achieved any success because I'm on an odexed ROM and couldn't get reodexing to work properly.
Tried but no joy, then realized it could be because the apk was from a previous nightly (couple days) than the one currently installed. Crossing my fingers that it's the reason it didn't work.
I'll try again.
sent from my vzw Galaxy Nexus / CM10.1 (nightlies)