[Help Needed] Problem Morphing Phone.apk, res folder duped, not images replaced - Nexus One Themes and Apps

So while trying to improve on my lockscreen morph that changes the circle icons to other shapes, i decided that since the Phone.apk uses those same (pretty much) icons to answer/decline a call, I should change them there as well.
I made the xml, making sure to place the framework-res changes last in the xml list, as recommended, and zipped. All file names and pathways are correct and have been double checked.
When I actually apply the morph with metamorph however, it starts applying the Phone.apk and all seems to be fine at first, then before it gets a chance to morph the framework-res, i get a series of FC's with the message "Sorry!, The process com.android.phone has stopped unexpectedly. Please try again." I push the FC button and the message reappears non-stop until I either reboot the phone, or since i dont trust it, restore with nandroid.
After I rebooted the first time I made a copy of the "morphed" Phone.apk. After unzipping it I found that instead of replacing the images of the res folder, it had created a duplicate, so now i had 2 res folders.
Anyone else have any insight on why this happens?

I have thte same problem. maybe not the duplicate res files, i'm a noob to all of this, but i do have the fc and that theme doesn't get applied. is that an issue with morph and 2.2? I am running KaosFroyo v38

Related

Modding Audio Manager Pro

Hey guys,
I'm trying to finish up my new homescreens, and my last widget is Audio Manager Pro. I've tried the metamorph on it, but it wasn't working. I've also tried to manually open the .apk and edit the .pngs i needed to edit, but have issues getting it signed. Any modders have some free time to help a theme noob?
What I am trying to do is make the background .pngs for the widgets transparent. Any help would be greatly appreciated!
Bump, any help or suggestions would be great!
Sent from my Evo.
I will be keeping an eye on this. The transparent skin they have for AM is transparent BUT the little bars that show levels are yellow, orange, and green or red or some yucky (to me) color combo! (they match NONE of the wallpapers I use) I wrote the developer this morning and asked for transparent but with like white, or shiny metallic bars ....
Yea, the am transparent skin on the market isn't really fully transparent. I also want the background to the fuxia skin transparent.
Sent from my Evo.
I answered my own question, but I thought I'd share what I did to make it happen.
1. adb pulled the apk
2. Opened the .apk in betterzip (mac user) WITHOUT EXTRACTING, and pulled the folders that needed editing.
3. Edited .pngs in Photoshop
4. Dragged the folders back into Betterzip into the correct directories.
5. Saved the changes to the .apk
6. adb pushed the .apk to /system/app
7. Profit!
Hopefully that helped someone!
That would help me IF i knew what I was doing ... I don't have Photoshop and I def don't know how to do that.
I did see under standalone's on this following link, 6th one down had it. Isn't that it? I tried it but it didnt' work for me. Just like the Genie one won't. Everything else my phone had taken easy.
http://forum.xda-developers.com/showthread.php?t=652661
kyleblakepeters said:
I answered my own question, but I thought I'd share what I did to make it happen.
1. adb pulled the apk
2. Opened the .apk in betterzip (mac user) WITHOUT EXTRACTING, and pulled the folders that needed editing.
3. Edited .pngs in Photoshop
4. Dragged the folders back into Betterzip into the correct directories.
5. Saved the changes to the .apk
6. adb pushed the .apk to /system/app
7. Profit!
Hopefully that helped someone!
Click to expand...
Click to collapse
Having the same problem, also can't get SetCPU widget to go transparent.
So, open the apk in a zip program, take out what needs editing, edit, put back in?
Yes and push back to system/app. Make sure to delete the app from the phone before pushing back.
Sent from my Evo.
effluent said:
Having the same problem, also can't get SetCPU widget to go transparent.
So, open the apk in a zip program, take out what needs editing, edit, put back in?
Click to expand...
Click to collapse
Umm.. SetCPU has an option to make the background clear.. Just an FYI.. It's a setting you change when you first open the widget..

[Q] Problems Recompiling Protips.apk

I've been a long time reader and I've learned quite a bit today on Android and its applications. I've been trying to recompile a modified Protips.apk and have it successfully run on my D1. I've been unsuccessful, and would like some pointers on where to looks next.
I'm intrigued by the modified Home Screen Tips widget as seen on Cyanogen and BuglessBeast. I figured I could do it too since it seems rather simple.
I pulled Protips.apk from my D1, archived it somewhere else, and ran apktools to decompile the app. I found that in: res/values/arrays.xml there's all the code I need to start changing text. I wanted to do something basic like Hello World as a test, so I slightly changed the first item to read Hello World! on the first line. So I edited the .xml file and considered the job done.
I recompiled my modified contents using apktools, and pushed the apk to my phone. It didn't show up in the widgets menu, so I figured I needed to sign the thing.
First I tried copying the META-INF data from the original APK into the new one, and though the you could apply the widget to the homescreen, it'd error. "Problem loading widget." Next I took the original manifest and popped it into the new APK. Same thing.
I thought I could try singing the modded APK myself. After recompiling I ran the APK through Auto-Sign. It still errors.
Someone mentioned that if you're modifying XML files, the resources.arsc file should be removed "prior to recompiling." I'm lost at this point, since when you decompile with apktools, you don't have access to that resource. If you remove it from the final apk, the app doesn't show up in the widgets menu.
I'm trying to figure out where I'm going wrong. Surely it has to be something rather simple.
------------------
Resolved
Decided to give Apk Manager a try. Decompiled the APK, edited the arrays.xml file, Compiled (deleting resources.arsc where instructed in the keep folder), signed the app, then pushed it to my phone. It works. I'll attempt the process using apktools again now that I have a working mod.
derik001 said:
I've been a long time reader and I've learned quite a bit today on Android and its applications. I've been trying to recompile a modified Protips.apk and have it successfully run on my D1. I've been unsuccessful, and would like some pointers on where to looks next.
I'm intrigued by the modified Home Screen Tips widget as seen on Cyanogen and BuglessBeast. I figured I could do it too since it seems rather simple.
I pulled Protips.apk from my D1, archived it somewhere else, and ran apktools to decompile the app. I found that in: res/values/arrays.xml there's all the code I need to start changing text. I wanted to do something basic like Hello World as a test, so I slightly changed the first item to read Hello World! on the first line. So I edited the .xml file and considered the job done.
I recompiled my modified contents using apktools, and pushed the apk to my phone. It didn't show up in the widgets menu, so I figured I needed to sign the thing.
First I tried copying the META-INF data from the original APK into the new one, and though the you could apply the widget to the homescreen, it'd error. "Problem loading widget." Next I took the original manifest and popped it into the new APK. Same thing.
I thought I could try singing the modded APK myself. After recompiling I ran the APK through Auto-Sign. It still errors.
Someone mentioned that if you're modifying XML files, the resources.arsc file should be removed "prior to recompiling." I'm lost at this point, since when you decompile with apktools, you don't have access to that resource. If you remove it from the final apk, the app doesn't show up in the widgets menu.
I'm trying to figure out where I'm going wrong. Surely it has to be something rather simple.
------------------
Resolved
Decided to give Apk Manager a try. Decompiled the APK, edited the arrays.xml file, Compiled (deleting resources.arsc where instructed in the keep folder), signed the app, then pushed it to my phone. It works. I'll attempt the process using apktools again now that I have a working mod.
Click to expand...
Click to collapse
Using apktool you must sign after other wise it won't install... I had issues using it to do a status bar mod.. Wondering if I can just sign it using that apkmanager and have it work... I used a kitchen to sign mine and it didn't sign right...

[ICON] Basic Framework Change - Enables HSxPA Icon

I tend to like things to look mostly stock, but I also wanted an H icon when it was in use... so I've knocked up this framework (used my FRG83D one, dunno if it's OK to use on older versions) with only that one change.
Probably not of that much interest to people, but rude not to share all the same.
http://www.multiupload.com/JB9SXZLF1G
Just overwrite (might want to take a backup first etc.) /system/framework/framework-res.apk with the one in the link and reboot.
I noticed that after pushing/rebooting, my accounts had vanished. No idea if that's normal when replacing the framework, but it only took a minute to re-add them.
Or, flashable .zip so you don't lose account details: http://www.multiupload.com/22TNJDP10X
New version, updated for FRG83G: http://www.multiupload.com/1DI1TBZNWA
Rusty! said:
...I noticed that after pushing/rebooting, my accounts had vanished. No idea if that's normal when replacing the framework, but it only took a minute to re-add them.
Click to expand...
Click to collapse
If you make a flashable update.zip your accounts do not vanish
Ahh right, well to save anyone that issue, I'll add one to the OP
Anyone on this side of the pond try this ?
Like the title says....anyone here in the US/Canada try this out yet ?
I'm running 2.2.1 (FRG83D) and the IN/OUT H PNG's icons are already there in the framework-res.apk, so I'm just curious what it is you did to turn them in your update script.
Also...the
Cert.rsa
Cert.sf
Manifest.mf
files you're including are older than the certs that are in the framework-res.apk that's in 2.2.1 (FRG83D). This is both within the update zip, and inside the framework-res.apk that's in your update zip.
Any particular reason you included the older certs in the framework-res.apk ?
Just curious trying to see what you've turned on to get the H to appear.
Decompile framework-res.apk, and look in /res/values for bools.xml
In there you just change config_hspa_data_distinguishable to true, save and recompile.
The reason the certs are in the update are because I just flung my updated framework into an existing update.zip for framework. Worked fine though. No idea why they would be older in my .apk, as I pulled it straight from my phone By product of recompiling perhaps?
So...anyone take the plunge ?
Anyone try this on theirs ?
Update: Works as advertised...ran speedtest.....definitely picks up the difference.
Updated for FRG83G: http://www.multiupload.com/1DI1TBZNWA

[Q] changing default call icon/g3 specific

Hello,
I ve been trying to change my default call icon (for unknown contacts) when receiving a call with ninjamorph... I opened phone.apk and found icon, changed it and nothing happens... It does change when I open preview in Ninjamorph... I think I probably changed the wrong icon because there are hundreds of them, most of them I never saw on my phone...
Can somebody tell me which one to change? There are some general tutorials but I cant find the directories and filenames they are refering to...
Of course, phone is rooted, running Destiny 2.1 ROM...
I would also like to change that awful phone animation when making a call if possible...
Thank you very much
change the icons in
DialerTabActivity.apk
I tried, changed some icons in drawable-Ldpi in dialertabActivity.apk but still nothing happens, not even in dialer screen
I applied and finished Ninjamorph project, and when it is done I can see by starting the project again that icons are changed indeed but still nothing changes...
Could you please be more specific about what icons to change?
well...
to be on safe side. check all *contact*.png pictures
the icon you search may have the naming like
default_icon...
unknown_contact_icon...
or something like that
the G3 is ldpi but sometimes (dont know when or why) the icons from mdpi folders are taken
therfore to be on safe side, just exchange all pngs which may sound like that
in framework-res.apk there are also some default icons...
maybe one of them is taken? Dont know.

Android Keyboard Force Closing After Mods...Dev Help Needed =)

So I've been on a big themeing kick lately and got bored of themeing systemui and framework so I decided to modify my MMS. I blacked it out with blue text and looks pretty sweet. I then decided to try and modify my keyboard to have red color keys instead of the original white. I decompiled LatinIME.apk, went into values/styles.xml. I only edited 3 lines of hex code changing it from white to red (#FFFFFFFF to #FFF44444). I recompiled, deleted the resources file and pushed it to system/app using Root Explorer and of course I fixed permissions. After rebooting device for mods to take affect I immediately get an error message stating, "Unfortunately, Android Keyboard Has Stopped." I have tried everything I can think of to make this work but for some reason I just can't get the keyboard to stop force closing. I know my mods DO work because when I open my MMS and try to open the keyboard, after the error message pops up my keyboard pops up behind it with the red keys! But then it goes away after I discard the message. I took some logcats but I can't figure out what the issue is with them......please take a look and let me know if you see anything that I don't.
For your information I am running Eaglesblood 4.0.4 AOSP, stock kernel.
Well I finally got it working, if anyone is interested. All I had to do was replace the resources.arsc file in the original apk with my modded resources.arsc from the newly compiled apk and push THAT one to my phone. Now I have a working themed keyboard!
Hi.. maybe a late answer.
for any system apk, after building the apk, you should :
Copy the original META-INF folder and perhaps AndroidManifest.xml from the original apk to the new one
Repack the apk, no need to sign.
Appreciate the response, but I posted my solution just above your's lol

Categories

Resources