Develop Bugs

Need help editing CyanBread.apk theme

Hi, I basically want to change the Battery Icon in the Notification Bar.
Yes I replaced the .png files with the ones I wanted but the problem is, the png files I have are exact battery percentages but in my Dinc it only shows battery levels in intervals of 5's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is the battery icon I am replacing it with. There are 134 .png's (100 battery status, 33 for battery charge, and 1 for unknown battery).
Basically my question is, how can I edit the theme so that it will show all .png files so the phone will display the exact battery percentage it is on?
This is how my phone looks so far
Thanks in advance!

I believe you'll need to edit XML files to make it pull the correct image for each 1% icon like you want. Just adding the images won't do it. I have never done this before, so maybe someone like fernando sor or Hatman (just to name a couple of themers) can help you out with that.

RMarkwald said:
I believe you'll need to edit XML files to make it pull the correct image for each 1% icon like you want. Just adding the images won't do it. I have never done this before, so maybe someone like fernando sor or Hatman (just to name a couple of themers) can help you out with that.
Click to expand...
Click to collapse
Do you have an idea of what xml file I need to edit I can't find anything that connects to the battery.
Sent from my ADR6300

eljean said:
Do you have an idea of what xml file I need to edit I can't find anything that connects to the battery.
Sent from my ADR6300
Click to expand...
Click to collapse
Maybe in framework-res - res - drawable - stat_sys_battery and stat_sys_battery_charge xml's....?
I am not running CM7/Cyanbread theme, so I'm not sure if those XML's are there.

RMarkwald said:
Maybe in framework-res - res - drawable - stat_sys_battery and stat_sys_battery_charge xml's....?
I am not running CM7/Cyanbread theme, so I'm not sure if those XML's are there.
Click to expand...
Click to collapse
Yeah is not in the Cyanbread.apk its only in the framework-res.apk... also Im kinda noobish at this sort of stuff how do I exactly edit these files?

You'd need to edit those files in the framework-res.apk to make them show. You'd need to decompile the apk file with apktool to view the XML's, then recompile it. I've decompiled framework-res, but never recompiled things with it or really made any changes.
You're best bet is to PM fernando sor or Stoney666, maybe they can help out further.

First thing is you need to decompile the apk. To get the phone to display 1% increments you will need to edit the stat_sys_battery xml file in drawable. To have the apk display your battery images you will need to define them in the android xml file in the xml folder. Once the edits are done recompile, sign the apk and install.

N-Forced said:
First thing is you need to decompile the apk. To get the phone to display 1% increments you will need to edit the stat_sys_battery xml file in drawable. To have the apk display your battery images you will need to define them in the android xml file in the xml folder. Once the edits are done recompile, sign the apk and install.
Click to expand...
Click to collapse
Will try this once I get home. Can I just open the apk using winrar and edit the xml file? Or do I need to decompile in order to read the xml file?
Sent from my ADR6300

Need to decompile first.

My suggestion would be to decompile the cyanbread apk and add the xmls for the battery to the apk. Then there's a couple more xmls in the theme apk that would need to be edited as well. When I get to my computer I can give you more info on it if you'd like but doing it this way would avoid any interference of the xml being in framework and having a standard battery icon if you go back to stock. This way too when you change nightlies you can bring your modified cyanbread theme with you instead of having to change the framework each time. Just a thought though.
Sent from my ADR6300

CondemnedSoul said:
My suggestion would be to decompile the cyanbread apk and add the xmls for the battery to the apk. Then there's a couple more xmls in the theme apk that would need to be edited as well. When I get to my computer I can give you more info on it if you'd like but doing it this way would avoid any interference of the xml being in framework and having a standard battery icon if you go back to stock. This way too when you change nightlies you can bring your modified cyanbread theme with you instead of having to change the framework each time. Just a thought though.
Sent from my ADR6300
Click to expand...
Click to collapse
Will I be able to install it by simply ADB Pushing the new Cyanbread.apk or will I have to reflash?
**This is a lot of writing sheesh, I started 10 minutes ago and I am only up to 50. Now I know how hard it is to make a theme, i really need to start donating to themers for their work lol.

CondemnedSoul said:
My suggestion would be to decompile the cyanbread apk and add the xmls for the battery to the apk. Then there's a couple more xmls in the theme apk that would need to be edited as well. When I get to my computer I can give you more info on it if you'd like but doing it this way would avoid any interference of the xml being in framework and having a standard battery icon if you go back to stock. This way too when you change nightlies you can bring your modified cyanbread theme with you instead of having to change the framework each time. Just a thought though.
Sent from my ADR6300
Click to expand...
Click to collapse
Any help signing the new APK? I cant seem to get this. I had just about done everything, eexcept this.

eljean said:
Any help signing the new APK? I cant seem to get this. I had just about done everything, eexcept this.
Click to expand...
Click to collapse
I've used Android Signer from PPC Geeks.
Sent from my ADR6300 using xda premium

Yes you can install it with adb or with root explorer and setting permissions. I've used android signer from ppc geeks as well on Windows.
Sent from my ADR6300 using XDA App

Thank you all. As I tried to install it however it tells me I compiled it wrong and to contact the developer or whatever.
All I changed was the stat_sys_battery and stat_sys_battery_charge xml files. I used cyanbreadx.apk and i dont want to edit framework-res on my rom just incase I mess it up.
I'm I missing something here? Do I have to edit anymore xml? Is it maybe the public.xml or android. xml?
Sent from my ADR6300 using XDA App

eljean said:
Thank you all. As I tried to install it however it tells me I compiled it wrong and to contact the developer or whatever.
All I changed was the stat_sys_battery and stat_sys_battery_charge xml files. I used cyanbreadx.apk and i dont want to edit framework-res on my rom just incase I mess it up.
I'm I missing something here? Do I have to edit anymore xml? Is it maybe the public.xml or android. xml?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Well, you could make a backup of your framework-res on your ROM by using adb shell. You can then use adb to revert it back if you screwed something up or it's unusable.
Create backup:
adb shell
cd /system/framework
cp framework-res.apk framework-res.bak
Restore backup:
adb shell
cd /system/framework
cp framework-res.bak framework-res.apk
Then you can try modifying your apk, and use adb push to put it back into /system/framework.
As far as other file editing, I'm not sure about that.

A very simple solution to your problem would be to use the theme kitchen http://uot.dakra.lt/. Just pick what battery you want from the ones provided, upload the cyanbread.apk, then install like a normal apk file.

RMarkwald said:
Well, you could make a backup of your framework-res on your ROM by using adb shell. You can then use adb to revert it back if you screwed something up or it's unusable.
Create backup:
adb shell
cd /system/framework
cp framework-res.apk framework-res.bak
Restore backup:
adb shell
cd /system/framework
cp framework-res.bak framework-res.apk
Then you can try modifying your apk, and use adb push to put it back into /system/framework.
As far as other file editing, I'm not sure about that.
Click to expand...
Click to collapse
It sent me in a bootloop, I guess I am compiling it wrong. I have no Idea what I am doing wrong. I rather edit the CyanbreadX.apk. So far I fixed the /res/drawable/stat_sys_battery.xml , /res/drawable/stat_sys_battery_charge and res/xml/Android.xml . I do not know what else I need to edit or what I am doing wrong.
Attached are the .xml files I customized.
Please if you can tell me what I did wrong and check them out.
***I changed the extension to .txt so it can attach.

N-Forced said:
A very simple solution to your problem would be to use the theme kitchen http://uot.dakra.lt/. Just pick what battery you want from the ones provided, upload the cyanbread.apk, then install like a normal apk file.
Click to expand...
Click to collapse
Anyway I can use my .png's since I spent a good minute modifying it in photoshop to get the colors I wanted?

eljean said:
Anyway I can use my .png's since I spent a good minute modifying it in photoshop to get the colors I wanted?
Click to expand...
Click to collapse
the theme kitchen allows you to define a custom color if you want.
Sent from my ADR6300 using XDA App

[MOD]/[HOWTO] Make E4GT ROMs show 1X/3G instead of just 3G! (FF18/ICS)

For the Gingerbread version of this fix, click here!
Greetings and Salutations, Epic 4G Touch Owners and other curious parties!
Disclaimer: Just reading this may cause your head to burst, your phone to catch fire, dogs and cats may do the tango! I am not responsible for any bad stuff that happens from you reading or acting on the information in this thread.
If any ROM authors want to use this fix in their ROMs, I'm completely cool with that. A quick kudos in your credits section would be nice, though.
Background: One of the things that really peeves me off about Sprint is that they want us to think we always have 3G service. I know that I don't have 3G in all of the areas I travel, and I also don't when I am roaming.
Thankfully, the fix is quite simple! It was a bit more difficult than the fix for HTC Sense ROMs as the smali edit was not quite as simple.
This was my primary reason for rooting my phone, that's how aggravating it is for me.
Let's change this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To this:
Credits
Calkulin, sextape, sfhub, Other brave folks - For providing the leaked ROMs for me to fiddle with.
Calkulin - (indirectly) helped me find how to fix this for Sense ROMs which I wrote up here.
Samsung - for a relatively good phone. Hopefully the weird auto-brightness and battery life will be fixed next update.
The brave XDA members who try these instructions and report their success or failure!!!
XDA for being a great source of information!!!
XDA members for thinking outside of the box!!!
The fix:
This fix requires editing your SystemUI.apk file. If you are using one of the fine custom ROMs on XDA, be aware that the you or the author may have already made changes to the SystemUI.apk file, so using my file IS NOT RECOMMENDED.
If you are using Calk's E4GT 2 v1.6 ROM, you can safely use my attached SystemUI.apk file. It may work with other "stock-ish" ROMs, but this is the one I based it on. The attachment will NOT work on stock FF18.
This mod relies on the assumption that your ROM developer has not deleted any of the 1x graphic files in the ROM. The developer CAN theme or otherwise change the images as long as the file names remain the same.
What you need to perform this mod:
1. An Epic 4G Touch ROM ZIP file, or a phone running a Epic 4G Touch ROM -- AOSP ROMs already have the correct indicators.
2. The Java SDK -- So you can run Smali.
3. Smali/Baksmali -- So you can decompile/compile the classes.dex file.
4. Android SDK -- To push/pull files from your phone (adb only).
5. Some sort of archive tool (such as WinRAR, 7zip, etc).
5. A text editor capable of editing UNIX-formatted files. I recommend Notepad++, personally.
Ease Of Use Tips: Install Java SDK first, then Android SDK (if you need adb). Download the smali files (smali-1.3.2.jar and baksmali-1.3.2.jar at the time of this writing) to a new "working" folder where we can do our magic.
KEEP A COPY OF YOUR PRE-EDITED SYSTEMUI.APK FILE, just in case!
Instructions:
1a. [If you are using a ROM ZIP File]: Use 7zip/WinRAR/WinZip to open the ROM ZIP file. Navigate to system\app and extract SystemUI.apk to your "working" folder.
1b. [If you want to grab SystemUI.apk from your running phone]: Use adb to pull SystemUI.apk to your working folder. Example: adb pull /system/app/SystemUI.apk C:\Working\SystemUI.apk
To avoid problems, ONLY USE adb to pull/push SystemUI.apk. Phone apps may cause unknown issues.
2. Go to a command prompt in your "working" folder and run the following command: java -jar baksmali-1.3.2.jar -o SystemUI/ SystemUI.apk
3. Browse to your "working" folder and see that there is now an SystemUI folder inside, with other subfolders. Browse to SystemUI\com\android\systemui\statusbar\policy.
4. Edit the file called NetworkController.smali with your favorite UNIX-format compatible text editor and look for the following text. The key is to search for .line 751. Edit the line below that is in BOLD.
Code:
.line 751
:pswitch_e8
iget-boolean v3, p0, Lcom/android/systemui/statusbar/policy/NetworkController;->mShowAtLeastThreeGees:Z
[B]if-nez v3, :cond_103[/B]
5. Change that line to say #if-nez v3, :cond_103 (add the # at the beginning to comment it out)
6. Save NetworkController.smali
7. Go back to your command prompt, change to your "working" folder and issue the following command: java -jar smali-1.3.2.jar SystemUI/ -o newclasses.dex
8. If there weren't any errors, go ahead and rename the original classes.dex to classes.old and rename newclasses.dex to classes.dex.
9. Open SystemUI.apk in your favorite archiver (if you closed it earlier).
10. Drag the file called classes.dex from your "working" folder into SystemUI.apk and replace the one already in there.
11. Run the following commands to get the file on your phone:
Code:
adb remount
adb push SystemUI.apk /system/app/SystemUI.apk
adb shell stop
adb shell start
You should hear your bootup sound and then the changes should be instantly applied.
To Test:
1. Dial ##DATA# (##3282#) on your phone.
2. Enter your MSL (can be found by typing getprop ril.MSL from Terminal Emulator or adb shell).
3. Scroll to Others at the bottom of the list.
4. Click on HDR/1X Selection
5. Change from Hybrid Mode to CDMA Only Mode. This puts your phone in 1X only mode.
6. Press OK.
7. Verify 1X icon comes within 30 seconds, if you have service.
8. Repeat steps 4-7, substituting Hybrid Mode for CDMA Only Mode to switch back.
How I found this: The files in ICS are different than Gingerbread. Looking for 1x led me to NetworkController.smali. There is a lookup called mShowAtLeastThreeGees (which I thought was hilarious). There are 6 locations that reference this boolean value. The correct one is the a couple of lines before a reference to DATA_1X. I wish I noticed that earlier as I was commenting out each one at a time until I found the last one, which coincidentally was right before DATA_1X. That's what happens when you've got too many things going on at once.
Please let me know whether or not this worked for you. I'd like to make a list of ROMs (with applicable mods) this works for or doesn't work for.
I will do whatever I can to help if you are struggling. If there's something you don't understand, please let me know. I can update the instructions if I accidentally wrote something wrong.

Great work once again
Sent from my SPH-D710 using Tapatalk 2

Finally!!! I will give it a go right now... mShowAtLeastThreeGees - that IS pretty funny. I guess Google programmers do have a sense of humor.
EDIT: Works like a charm. Here's modded SystemUI.apk from Calkuin's newest FE22 ROM, for those who don't want to mess with SMALI edits.

Awesome work! Now help us find where they've buried the lines to hide AM/PM in there

datajosh said:
Awesome work! Now help us find where they've buried the lines to hide AM/PM in there
Click to expand...
Click to collapse
i'll +1 that. Its one of the main reasons I can't stand TW.

nice work

Thanks Nivron. Here is the systemUI.apk for the stock deodexed rom.

Nice work.

Haven't tested it just yet but it looks like they changed it from line 752 to 751 in FF02 for anyone wanting to make the change in the latest build.

Is it possible for someone to update this for the new FF02 build?

DevalB said:
Is it possible for someone to update this for the new FF02 build?
Click to expand...
Click to collapse
Here it is for stock FF02.

dtm_stretch said:
Here it is for stock FF02.
Click to expand...
Click to collapse
To install, I just ADB push?

DevalB said:
To install, I just ADB push?
Click to expand...
Click to collapse
Yeah, or you can use a file explorer and drop it in system/app, then reboot.

dtm_stretch said:
Yeah, or you can use a file explorer and drop it in system/app, then reboot.
Click to expand...
Click to collapse
I tried dropping it into system/app, which caused the device to lock up and FC systemui. I did a battery pull, and now I'm left with no UI icons, etc.
I think it's due to no space left in my /system/ folder. I deleted the failed install of S-voice, which cleared up 20MB, and now it works!
---------- Post added at 04:59 PM ---------- Previous post was at 04:46 PM ----------
So I tried changing my mode from Hybrid to CDMA only, and waited about a minute, and my device stayed on 3G. I even rebooted just to be sure.
Thoughts?
I downloaded the modified FF02 systemui.apk file, and used ES File Explorer to paste it into /systemUI/app/, after backing up (adb pull) the stock systemUI.apk

DevalB said:
I tried dropping it into system/app, which caused the device to lock up and FC systemui. I did a battery pull, and now I'm left with no UI icons, etc.
I think it's due to no space left in my /system/ folder. I deleted the failed install of S-voice, which cleared up 20MB, and now it works!
---------- Post added at 04:59 PM ---------- Previous post was at 04:46 PM ----------
So I tried changing my mode from Hybrid to CDMA only, and waited about a minute, and my device stayed on 3G. I even rebooted just to be sure.
Thoughts?
I downloaded the modified FF02 systemui.apk file, and used ES File Explorer to paste it into /systemUI/app/, after backing up (adb pull) the stock systemUI.apk
Click to expand...
Click to collapse
Are you stock and deodexed? Also have you tried changing the permissions of systemUI.apk to match the other apks in system/app?

dtm_stretch said:
Are you stock and deodexed? Also have you tried changing the permissions of systemUI.apk to match the other apks in system/app?
Click to expand...
Click to collapse
Stock FF02, rooted: http://forum.xda-developers.com/showthread.php?t=1694695
Let me try the permissions, see what it does.

DevalB said:
Stock FF02, rooted: http://forum.xda-developers.com/showthread.php?t=1694695
Let me try the permissions, see what it does.
Click to expand...
Click to collapse
That isn't deodexed and this is a smali edit, so I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2

dtm_stretch said:
That isn't deodexed and this is a smali edit, so I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You can use a odex rom and with root explorer delete both SystemUI files and replace it with the SyetemUI.apk posted in this thread, it will work I have tried it.
now I'm assuming that you can do the same thing if you know how to take out the systemUI from your odex rom and deodex it and then do the mod.

OP updated for FF18, small change (.line 752 to .line 751). Note that the attachment is still for Calk's E4GT 2 v1.6 ROM and won't work right with FF18.

Deodexed FH13
Here it is for FH13 Deodexed

Remove Recent Apps

I use the RCMixS rom (with Htc Sense 2.1 + 3.0) and I'm trying to remove the Recent Apps' bar from the SystemUI menu.
I have been following 3 or 4 different guides, but no one worked for me...
Can anyone please help me removing the Recent Apps?
This is my SystemUI.apk
I hope that someone can help me
Thank you in advance,
Sbarabau

Sbarabau said:
I use the RCMixS rom (with Htc Sense 2.1 + 3.0) and I'm trying to remove the Recent Apps' bar from the SystemUI menu.
I have been following 3 or 4 different guides, but no one worked for me...
Can anyone please help me removing the Recent Apps?
This is my SystemUI.apk
I hope that someone can help me
Thank you in advance,
Sbarabau
Click to expand...
Click to collapse
Do u have the RCMix tweaks in settings? Coz u can disable the recent app in notifications there.
(requires reboot)
Sent from my HTC Desire

jmcclue said:
Do u have the RCMix tweaks in settings? Coz u can disable the recent app in notifications there.
(requires reboot)
Sent from my HTC Desire
Click to expand...
Click to collapse
No, I don't have RCMix Tweaks... In my case the only way to remove the recent apps is to modify the SystemUI.apk
I've followed several guides, but unfortunately no one worked for me...

Up....

Up...

Post a screen shot of what u have, then clearly state what u want to remove? Draw on the screen shot if u need to
Sent from my Galaxy Nexus using Tapatalk 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yeah same problem .. but I found some nice step by step tutorial to remove it using apktool, i did exactly what it said but i could'nt edit some framework files and now i lost the link to the tutorial ...

Sbarabau said:
Click to expand...
Click to collapse
O I thought you were talking about something else, is your from deodex that your running? And what android version are you one?
Also upload your framework-res.apk
And com.htc.resources.apk
Sent from my Galaxy Nexus using Tapatalk 2

The way to do it,
Deconpile the syatemui.apk
At SystemUI\smali\com\android\systemui\statusbar - open the file StatusBarFlag.smali with
Find
Code:
sput-boolean v0, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_RECENT_APP:Z
Change to
Code:
sput-boolean v2, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_RECENT_APP:Z

runandhide05 said:
The way to do it,
Deconpile the syatemui.apk
At SystemUI\smali\com\android\systemui\statusbar - open the file StatusBarFlag.smali with
Find
Code:
sput-boolean v0, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_RECENT_APP:Z
Change to
Code:
sput-boolean v2, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_RECENT_APP:Z
Click to expand...
Click to collapse
I've already tried this but it force closes. Now i upload the framework and the com.htc.resources apks

SystemUI.apk is deodexed and I'm running Gingerbread 2.3.3
This is the link to download framework-res.apk and com.htc.resources.apk
com.htc.resources.apk: https://rapidshare.com/files/4035992333/com.htc.resources.apk
framework-res.apk: https://rapidshare.com/files/646835451/framework-res.apk
Thank you for the help you're giving to me

Let me ask u this, you say it causes force close,
Have you tried to decompule the systemui and DO NOT make any changes and simply recompile the apk, then push to your phone? Try this and see if the systemui still force closes, I have seen APKTOOL mess up a LOT of HTC apks when recompiling , try that and report back
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Let me ask u this, you say it causes force close,
Have you tried to decompule the systemui and DO NOT make any changes and simply recompile the apk, then push to your phone? Try this and see if the systemui still force closes, I have seen APKTOOL mess up a LOT of HTC apks when recompiling , try that and report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've tried as you said, and it doesn't work
First I tried to decompile, recompile and pushing the file... I rebooted and SystemUI didn't start...
Then I tried to recompile with his META-INF datas... the result is the same...
Can you please try to edit the SystemUI.apk and give me it back, to see if I am doing something wrong or not?
Thank you in advance

Sbarabau said:
I've tried as you said, and it doesn't work
First I tried to decompile, recompile and pushing the file... I rebooted and SystemUI didn't start...
Then I tried to recompile with his META-INF datas... the result is the same...
Can you please try to edit the SystemUI.apk and give me it back, to see if I am doing something wrong or not?
Thank you in advance
Click to expand...
Click to collapse
Okay,
in this zip is four SystemUI.apk
each one is in its own folder, there are two sets, one set i made NO changes to the smalis, just decompiled and then rebuilt, one is a distro, and one is a little bit of a different way to use apk (but i have noticed it to work best when dealing with HTC)
try both, remember to set your permissions correctly on the apk after you move it to /system/app then reboot.
if one of the ones that i did not change the smalis on works, use the corresponding files in the remove recent apps folder
for example
if the no changes distro build works and does not casue force close, go straight to the removed recent apps folder labels disrto and use that one.
hope this helps you out,
by the way, what part of Italy are you from?
zip
https://www.box.com/s/80233766e0e29235614f

runandhide05 said:
Okay,
in this zip is four SystemUI.apk
each one is in its own folder, there are two sets, one set i made NO changes to the smalis, just decompiled and then rebuilt, one is a distro, and one is a little bit of a different way to use apk (but i have noticed it to work best when dealing with HTC)
try both, remember to set your permissions correctly on the apk after you move it to /system/app then reboot.
if one of the ones that i did not change the smalis on works, use the corresponding files in the remove recent apps folder
for example
if the no changes distro build works and does not casue force close, go straight to the removed recent apps folder labels disrto and use that one.
hope this helps you out,
by the way, what part of Italy are you from?
zip
https://www.box.com/s/80233766e0e29235614f
Click to expand...
Click to collapse
I've tried them all and the only one who worked for me is the one under "/decomp then rebuilt/no changes build/SystemUI.apk"
P.s: I'm from northern Italy

Sbarabau said:
I've tried them all and the only one who worked for me is the one under "/decomp then rebuilt/no changes build/SystemUI.apk"
P.s: I'm from northern Italy
Click to expand...
Click to collapse
did all the others cause force close?
PS i ask cause my family is from Bari
edit:
try this one

runandhide05 said:
did all the others cause force close?
PS i ask cause my family is from Bari
edit:
try this one
Click to expand...
Click to collapse
Force close again...
-------------------------------------------------------
Build not modified: worked xD
Distro not modified: no force close, but it didn't start
Build modified: force close
Distro modified: force close
-------------------------------------------------------
P.S: I'm from Mantova

Sbarabau said:
Force close again...
-------------------------------------------------------
Build not modified: worked xD
Distro not modified: no force close, but it didn't start
Build modified: force close
Distro modified: force close
-------------------------------------------------------
P.S: I'm from Mantova
Click to expand...
Click to collapse
ok, then clearly the same mod does not work as it use to.
but atleast the recompile works(kinda)
once u build the apk, open the original apk in 7zip and open the file directory in apktool /systemui/build/apk and copy everything but the AndroidManifest into the archive of the orginal apk.
see pic

runandhide05 said:
ok, then clearly the same mod does not work as it use to.
but atleast the recompile works(kinda)
once u build the apk, open the original apk in 7zip and open the file directory in apktool /systemui/build/apk and copy everything but the AndroidManifest into the archive of the orginal apk.
see pic
Click to expand...
Click to collapse
Still force close

[HOW TO] Theme ALL keyboards without FCs! [A guide for beginners]

Theming a keyboard may be common knowledge to some of the amazing Devs here. But to a noob like me, it took some research and time to get it working without breaking the original signature (That's the trick!). I searched the forum and it doesn't look like anyone has posted a "How To" on theming a keyboard, so I thought I'd share my experience with you all.
**Some of these steps may seem elementary, but I tried to explain everything in layman's terms so even a beginner can theme a keyboard.
// Before you get started:
You must have a working environment setup. Check out QBKing77's awesome video "How to install the android-sdk" to get that going.http://forum.xda-developers.com/showthread.php?t=1614922
Make sure you also have installed:
Notepad++ (for editing xml) // (www.notepad-plus-plus.org)
7zip (for extracting apks) // (www.7-zip.org)
the image editor of your choice. I use Paint.Net(www.getpaint.net), and Gimp(www.gimp.org). Both FREE!
apktool (http://forum.xda-developers.com/showthread.php?t=1755243)
LatinImeDictionaryPack.apk (drop in the 'system\app' folder on your phone. Only for the LatinIME.apk) Grab it here: http://d-h.st/Ebb
// This method has worked with every keyboard that I have encountered so far. I will use 'LatinIME.apk' for reference, as that is the stock ICS keyboard. //
WARNING.. DO NOT POST DISTRIBUTION LINKS TO ANY MODDED 'Swype.apk'. XDA HAS A STANDING ORDER FROM NUANCE (MAKERS OF SWYPE), THAT DOES NOT ALLOW SUCH LINKS TO BE POSTED.
1) To start make sure you have a working copy of your keyboard apk; grab it out of a ROM, download it, or use a file manager with root access (like Root Explorer) to copy it to your SD card then to your computer.
**I would suggest dropping the keyboard apk into a folder on the desktop, seperate from anything else, and making a backup of the original so that you have a spare copy.
2) Using 7zip extract the 'res\drawable-xhdpi' folder into the folder you created. This folder will contain the pngs that control some of the keys, outlined in red on this pic:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Color these pngs to match using your favorite editor and save (bucket fill with Paint.Net is a breeze!)
3) Now that your pngs are themed.. Within the folder that you created containing your apk, hold down shift and right click. Select "Open Command Window Here" to fire up command prompt.
4) Next to decompile the keyboard apk with apktool (again using 'LatinIME.apk' for reference, but the apk may be of a different name; SamsungIME.apk, HTC_IME.apk, etc.).
Type this command:
Code:
apktool d LatinIME.apk
When it's done, you will see a folder with the apk name appear, within the folder you created. Click into it and you should see at minimun a 'res' folder and a 'smali' folder.
5) Navigate to 'res\values' folder. Depending on the keyboard you are working on, the xml controlling the remaining key colors will be contained in the 'colors.xml' or 'styles.xml' file. Open with Notepad++, and change the color codes as needed. Save and close.
6) Go back to the root of the folder containing your apk, and fire up command prompt (if it's not still open). Now it's time to build using this command (again using 'LatinIME.apk' for reference, but the apk may be of a different name; SamsungIME.apk, HTC_IME.apk, etc.)
Code:
apktool b LatinIME
7) When it's done building, you should have 4 folders minimum now (res, smali, build, dist) and it's time for the key to success. Navigate into the 'dist' folder and you will see the "Built" apk. Open it with 7zip, and extract the 'resources.arsc' file to your folder. Close 7zip.
8) Now it's time to pull it all together. Navigate back to the ORIGINAL keyboard apk, and open with 7zip.
Copy (you can drag and drop with 7zip) the 'resources.arsc' that you extracted from your "Built" apk, into the "ORIGINAL" apk overwriting the file. Then with 7zip still open and the apk loaded, navigate (within 7zip) into the 'res\drawable-xhdpi' folder where you should see the list of unthemed pngs. Simply drop your edited pngs into this folder. Close 7zip and you're done here!
9) Finally, take your "ORIGINAL" but themed apk, and push it back the 'system\app' folder on your phone.
Fix permissions to 'rw-r--r--' (only check everything under 'read' and Owner under 'write')
Reboot, and bask in the glory of your new themed keyboard!
**Alternatively, grab my empty zip installer here: http://d-h.st/oKG to flash in recovery. You must drop your themed apk into the system\app folder of the zip and save. Also, the zip already contains the 'LatinImeDictionaryPack.apk'
Please hit THANKS if I helped!! And please keep this thread alive!

Nice,
Now, we need a simple guide on how to theme Jelly Bean...all of it ... (tapping foot patiently)
Thanks!

Naddict said:
Nice,
Now, we need a simple guide on how to theme Jelly Bean...all of it ... (tapping foot patiently)
Thanks!
Click to expand...
Click to collapse
Themed the same just new xml and some new images. I got everything to decompile and recompile, just some of the xml's have changed.
---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------
Thanks rompnit. I can there a whole Rom but always have issues with the keyboard. I'll try this tomorrow night.

Sorry i'm a nub but does the apktool jar file have to be in the same folder as android-sdk?

shehroze3 said:
Sorry i'm a nub but does the apktool jar file have to be in the same folder as android-sdk?
Click to expand...
Click to collapse
I actually created a folder 'C:\apktool' where I dropped everything, then added that folder to the Path system variable; same method as you would add the SDK. Otherwise, drop it into the 'platform-tools' folder within the android-sdk. When configured properly, you should be able to open command prompt in any directory, simply type 'apktool' and see a list of commands.

rompnit said:
I actually created a folder 'C:\apktool' where I dropped everything, then added that folder to the Path system variable; same method as you would add the SDK. Otherwise, drop it into the 'platform-tools' folder within the android-sdk. When configured properly, you should be able to open command prompt in any directory, simply type 'apktool' and see a list of commands.
Click to expand...
Click to collapse
ok i did what u said and put the apktool jar file into the platform-tool folder, but when i type apktool in cmd prompt nothing happens.

shehroze3 said:
ok i did what u said and put the apktool jar file into the platform-tool folder, but when i type apktool in cmd prompt nothing happens.
Click to expand...
Click to collapse
Did you also grab the "wrapper" script from the link as well? It contains a few more necessary files that go with apktool.
Sent from my SPH-L710 using xda app-developers app

time for dazed and rompnit to collaborate. maybe a simple guide for us wannabees...
recompiling never works for me, I read somewhere about empty folders being my problem...oh well, I can use 7zip though! and notepad+...

rompnit said:
Did you also grab the "wrapper" script from the link as well? It contains a few more necessary files that go with apktool.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I'll check it out when I get home. Thanks
Sent from my SPH-L710 using xda premium

ok i got it to work. All i had to do was rename apktool_1.5.0 to apktool. I'm a noob, i know, try not to laugh to hard lmao

shehroze3 said:
ok i got it to work. All i had to do was rename apktool_1.5.0 to apktool. I'm a noob, i know, try not to laugh to hard lmao
Click to expand...
Click to collapse
Glad you got it to work!! And everyone has to start somewhere! Let me know how it turns out for ya!!
Sent from my SPH-L710 using xda app-developers app

Does this method work for both Odex and De-Odex ROMs??? I am currently on an Odex rom. Thanks!!

taihard said:
Does this method work for both Odex and De-Odex ROMs??? I am currently on an Odex rom. Thanks!!
Click to expand...
Click to collapse
This method will not work on .odex keyboard apk's, at least to my knowledge but I've always run deodexed ROMS. However, check to see if the keyboard apk you are working with even contains an odex file; a lot of them do not. If it does, you could always grab the apk off the web, mod it, and install it after removing the original files.

Thank you for the walk through, this is awesome

Hey Rompnit. Ok, I was having trouble getting apktool to run on my computer. That's what I was talking about on morphology anyway, so I was trying to learn how to theme an app and somehow was lead to morphology and got all caught up over there. Lol. But ya, I'm gonna have to crap clean my laptop to use this. Thanks. See ya over there
Sent from my Insanely Morphed S3 LI3 ktoonsez747 (196-2106) TW FreeGs3 2.0.0

rompnit said:
This method will not work on .odex keyboard apk's, at least to my knowledge but I've always run deodexed ROMS. However, check to see if the keyboard apk you are working with even contains an odex file; a lot of them do not. If it does, you could always grab the apk off the web, mod it, and install it after removing the original files.
Click to expand...
Click to collapse
This method WILL in fact work on odexed keyboards. Theming for an odex base is no different then a de-odexed base. You are not making any smali adjustments here so nothing that concerns the odex, thus it will not be affected.
Sent from my SPH-L710 using xda app-developers app

Guess no one was interested in theming an odexed keyboard after all huh? ....
Sent from my SPH-L710 using xda app-developers app

gruesomewolf said:
Guess no one was interested in theming an odexed keyboard after all huh? ....
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Guess not.. This thread's been quiet for a while... I guess people just don't want to theme keyboards in general!

Hey do you know if this process will work with keyboards from the market like SwiftKey 3? The themeson there are so boring need new colors lol

rompnit said:
Guess not.. This thread's been quiet for a while... I guess people just don't want to theme keyboards in general!
Click to expand...
Click to collapse
Guess that's what we get for trying to help. ... lol

Need help

Okay so I have been using the androidmenifest of 4.1.1 on my ma7 4.1.2 to make the flashlight and reboot toggles to work but ive been using the MC2 systemUI 4.1.2 got everything right but the flashlight and reboot toogles still doesnt work I gave permission to both of them and it keeps FC'ing my whole systemUI... doesnt any1 know why ???
Any opinion on this, im open to suggestions anything.. the only think I havent tried is only do the 23 toggles and see the outcome but idk what else to do -___-
Sent from my SPH-L900 using xda premium

Mundo Hackz said:
Okay so I have been using the androidmenifest of 4.1.1 on my ma7 4.1.2 to make the flashlight and reboot toggles to work but ive been using the MC2 systemUI 4.1.2 got everything right but the flashlight and reboot toogles still doesnt work I gave permission to both of them and it keeps FC'ing my whole systemUI... doesnt any1 know why ???
Any opinion on this, im open to suggestions anything.. the only think I havent tried is only do the 23 toggles and see the outcome but idk what else to do -___-
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
MA7 did some things with systemui and a few other things that need modding.
The androidmanifest ROM MA7 requires a few line changes concerning CORE apps. After modding that one needs to resign the apk since the manifest has been changed upon recompile. Then one must modify the services.jar to disable a unified Sig check(your sysemui will be signed but not matching others).
If the toggles are written in correctly to systemUI, the manifest is modded, the systemUI is resigned(as a "platform" key), and services.jar modded to disable SIG check, your flashlight and reboot options will work like a charm. I did all of this to my Venum Ice ROM if you want to decompile and look at the manifest etc. If you Google "disable signature check services" you should get those how to's as well

sleshepic said:
MA7 did some things with systemui and a few other things that need modding.
The androidmanifest ROM MA7 requires a few line changes concerning CORE apps. After modding that one needs to resign the apk since the manifest has been changed upon recompile. Then one must modify the android.policy.jar to disable a unified Sig check(your sysemui will be signed but not matching others).
If the toggles are written in correctly to systemUI, the manifest is modded, the systemUI is resigned(as a "platform" key), and android.policy modded to disable SIG check, your flashlight and reboot options will work like a charm. I did all of this to my Venom Ice ROM if you want to decompile and look at the manifest etc. If you Google "disable signature check android.policy" you should get those how to's as well
Click to expand...
Click to collapse
I gave permission to camera and reboot but nothing so I think only way is disable the sig and hopefully it will work
When I compile I just copy the mexa-inf right because the androidmenifest is modded
Sent from my SPH-L900 using xda premium

Mundo Hackz said:
I gave permission to camera and reboot but nothing so I think only way is disable the sig and hopefully it will work
When I compile I just copy the mexa-inf right because the androidmenifest is modded
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Meant to say services.jar not android.policy the second i hit submit the forums went down and couldn't change it (at work and distracted )
Not sure what you mean by "permission", This is what I would suggest doing, it is too easy to use zip signer to sign an apk than to copy and paste a meta-inf folder not knowing if that's the issue.
1) decompile my venum ice systemui and look at the android manifest, change your first line to look like mine, its a small edit.
2) use zip signer to sign newly compiled systemui(with modded android.manifest) with Platform key
3) mod services.jar using this http://forum.xda-developers.com/showthread.php?t=1698352

sleshepic said:
Meant to say services.jar not android.policy the second i hit submit the forums went down and couldn't change it (at work and distracted )
Not sure what you mean by "permission", This is what I would suggest doing, it is too easy to use zip signer to sign an apk than to copy and paste a meta-inf folder not knowing if that's the issue.
1) decompile my venum ice systemui and look at the android manifest, change your first line to look like mine, its a small edit.
2) use zip signer to sign newly compiled systemui(with modded android.manifest) with Platform key
3) mod services.jar using this http://forum.xda-developers.com/showthread.php?t=1698352
Click to expand...
Click to collapse
uses-permission placed on manifest so that way camera and reboot will function

Mundo Hackz said:
uses-permission placed on manifest so that way camera and reboot will function
Click to expand...
Click to collapse
When I said "I'm not sure what you mean" you should have taken that as "it has nothing to do with making it work" lol. Only way to make it work is do exactly what I said, done it several times now from scratch.

sleshepic said:
When I said "I'm not sure what you mean" you should have taken that as "it has nothing to do with making it work" lol. Only way to make it work is do exactly what I said, done it several times now from scratch.
Click to expand...
Click to collapse
did not work -___-

Mundo Hackz said:
did not work -___-
Click to expand...
Click to collapse
Then it wasnt done right frankly, I couldn't go into great detail but that was the jist of it. It works, like I said done it several times now from scratch each time.
Did you resign the apk yourself? Did you mod the services.jar and it boots? Was the android.manifest properly modified so systemui is a core app?
What did you do? And how

sleshepic said:
Then it wasnt done right frankly, I couldn't go into great detail but that was the jist of it. It works, like I said done it several times now from scratch each time.
Did you resign the apk yourself? Did you mod the services.jar and it boots? Was the android.manifest properly modified so systemui is a core app?
What did you do? And how
Click to expand...
Click to collapse
okay modded the services.jar and it booted..
i decompiled your systemUI and it was the same as mine ..
the zip signer is a tool that i download from google right
??

Mundo Hackz said:
okay modded the services.jar and it booted..
i decompiled your systemUI and it was the same as mine ..
the zip signer is a tool that i download from google right
??
Click to expand...
Click to collapse
Use a diff program to look at the android.manifest if you don't see the diff, its not the same. Its an addition to one of the first lines
If you didn't change your manifest and it was left stock that is your issue. None of the steps can be skipped

sleshepic said:
Use a diff program to look at the android.manifest if you don't see the diff, its not the same. Its an addition to one of the first lines
If you didn't change your manifest and it was left stock that is your issue. None of the steps can be skipped
Click to expand...
Click to collapse
i added this android:sharedUserId="android.uid.system" androidrocess="system

Mundo Hackz said:
i added this android:sharedUserId="android.uid.system" androidrocess="system
Click to expand...
Click to collapse
That looks right but then again I'm at work dealing with annoying customers so I can't really double check.
It should be the only diff between your MA7 manifest from systemui and mine, so honestly there's not much more I can say than copy the one line that's diff up toward the beginning. Then resign, and mod services.

sleshepic said:
That looks right but then again I'm at work dealing with annoying customers so I can't really double check.
It should be the only diff between your MA7 manifest from systemui and mine, so honestly there's not much more I can say than copy the one line that's diff. Then resign, and mod services.
Click to expand...
Click to collapse
I got it working well the thing I did was get a zip signer from the app store than I just singed it thru my phone and just tried and it worked even the brightness works now without any problems
Sent from my SPH-L900 using xda premium

Good, glad you got it. Everything will work now :thumbup:

Ok...I guess I'll throw a question in here since it sounds like were playing with the same things. Lol
I just got the 15 toggles working fine. I was porting a theme over from the s3.
Only after testing did we notice its using a 4bar signal. I edited the integers.xml to increase the max higher and its refusing to do it?
Ive looked all over. Only thing I had was that it was also using the stat signal as opposed to the tw signal pngs
Any thoughts on where else I can look?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cbucz24 said:
Ok...I guess I'll throw a question in here since it sounds like were playing with the same things. Lol
I just got the 15 toggles working fine. I was porting a theme over from the s3.
Only after testing did we notice its using a 4bar signal. I edited the integers.xml to increase the max higher and its refusing to do it?
Ive looked all over. Only thing I had was that it was also using the stat signal as opposed to the tw signal pngs
Any thoughts on where else I can look?
Click to expand...
Click to collapse
To me it work my guess is to get the ones and xml files the same . So no conflict you know
Wolfed out Note Dos