Related
Okay so i made a custom taskbar for my evo and it looks pretty cool when i put it on but when i unlock the phone im hit with constant fc's. Is there something i missed that would cause this?
screen cap please. let me see if I can spot the issue
Okay one second i'll see if i can get a screen cap.
Edit: Screens up
Hmm I made myself a transparent bar for myself the other day and no force closes. at all.
Did you edit the original or made an entirely new one?
i edited the original. My guess is its some kind of signed file issue or something but idk
saf100792 said:
i edited the original. My guess is its some kind of signed file issue or something but idk
Click to expand...
Click to collapse
Yea..you can't add, remove, or change the names of any files. If you are going to edit them pull them....change what you want and save it as it was...a png using the same exact name as it had before. The "ear" icon in the battery's spot suggests to me that you have used a different framework then the ROM you are using it with......
That ear came with the rom for some reason. I'm using damages rom and i pulled the entire apk then extracted the archive and rebuilt it after editing. Maybe thats why?
Disclaimer: I do not have any formal training with anything I'm covering here and it's entirely possible….dare I say probable…that I may state something incorrectly either partially or wholly (hopefully I’m not that far off). So this is just how I've come to understand things from my own self study as well as staring smali for countless hours (although I have to say the more I learn, the more I learn I don't know ). Hopefully there’s another beginning android hobbyist that finds this useful and/or inspires him to try some new things.
**These instructions apply to Mac and Linux only, due to the fact we're working with aosp source and building in windows is not supported at this time**
Enabling Translucency
I approached this a little different than I’m used to seeing in terms of a mod. Normally we start off by decompiling an apk and go from there. Since this is for an aosp rom, we have easy access to the source code and can make changes there. Now, I don’t proclaim to know java. I have very, very little programming experience, and even that is limited to an introductory C++ class I just took. But even without knowing java, you’ll have a much easier time reading java source code than you will smali. So, yes, you need to sync with aosp to use this guide. It's not hard, and there's good instructions HERE. As an aside, my personal opinion is that anyone that a true-blue xda'er should have aosp syned...even if you have no intention of building roms. It's like an android encyclopedia. I've learned A TON just from poking around/reading though some parts. I probably comprehend < 10%, but it's easily been one of the most beneficial things I've done to further my understanding.
So now you have the source code. What we need to change is the PixelFormat for the statusbar. In froyo and gingerbread this was done in StatusBarService. It’s been changed a little in ics, although the edits remain in SystemUI. The two files I changed were StatusBar and PhoneStatusBar.
Starting in the root of your aosp working directory, the absolute path of the first file I edited is
Code:
frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/StatusBar.java
Open this in a good text editor. The PixelFormat parameter is specified in the getStatusBarHeight function. In the version I edited it is easily found on lne 124. Just search for “PixelFormat” and you’ll find it. (ignore the search return that’s part of the import statement at the beginning of the file) As soon as you get there you’ll see the problem. PixelFormat.OPAQUE. Replace OPAQUE with TRANSLUCENT. Save
Next you make similar edit in PhoneStatusBar.java. From the same directory that StatusBar.java is in, go to the phone directory and open PhoneStatusBar.java in your text editor. Now this file is much, much longer to read through. Rather than doing that (of course you can if you want) just performa search for that same text again “PixelFormat” You’ll get several returns, some of them will already have TRANSLUCENT set.
BUT...Don’t get carried away and change all the OPAQUE values. One of the search returns will be part of the function getRecentsLayoutParams (starts on line 378). The portion of code that you might be temted to change checks the PixelFormat by way of a boolean test
Code:
(opaque ? PixelFormat.OPAQUE : PixelFormat.TRANSLUCENT)
I left this alone.Edit: After reading the entire code a little bit more, I think we could change it to
Code:
PixelFormat.TRANSLUCENT
without any ill effects, although I'm not sure what, if any, additional benefit we'd see. I have not tried.
The exact places I did change OPAQUE to TRANSLUCENT were in lines 311, and 481. That’s it for the code portion. Make sure to save your changes. Now go back to the res directory and we need to edit some xml files.
From the root of the SystemUI directory, open res/values/colors.xml. Find the entry for “status_bar_background” and change it’s value to whatever you want. In mine I’ve set it to “a6000000” which black but 35% translucent. The first 2 characters control the opacity on a scale from 0-255 where 0 is completely transparent and 255 is fully opaque. That value is then stated in hexadecimal format; e.g. 0=00, 255=ff.
*if you also want a translucent bottom menu bar, it is set in res/layout/navigation_bar.xml. Change the hex value of android:background=”ff000000” to your desired value for opacity.*
Now you should have all the edits in place for a translucent statusbar. All that’s left is to compile the apk. Before you compile SystemUI, you need to have ran the extract-files script. Only needs to be done once. Connect your phone to the computer(making sure that usb debugging is turned on) then in terminal, starting from the root of your aosp working directory:
Code:
cd device/samsung/maguro/
./extract-files.sh
Let the script finish. It will create a new vendor directory in the root of your working directory and copy several files from your phone.
Now cd back to the root of your working directory and run
Code:
. build/envsetup.sh
Note the period and space before build. This is an important step which initialized the build environment. Several new commands will be available now such as "mm" "mmm" "croot" amongst others. Type "help" (without the quotes) for a full list of the new commands available.
Next step to build your SystemUI is to run lunch. Just type "lunch" and press enter:
Code:
pendo:master pendo$ lunch
You're building on Darwin
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_stingray-userdebug
5. full_wingray-userdebug
6. full_crespo-userdebug
7. full_crespo4g-userdebug
8. full_maguro-userdebug
9. full_toro-userdebug
10. full_panda-eng
Which would you like? [full-eng]
It will list the available builds. Number 8 should be for maguro-user debug. Select it and press enter. And lastly, type
Code:
make SystemUI
It will take several minutes to build, especially the first time. But once it’s done, your new SystemUI will be in out/target/product/maguro/system/app/SystemUI.apk.
Here is a SystemUI that I built that has a translucent statusbar. It also has a circle battery mod I recently made in ics blue. This was built on 4.0.3 sources.
Here's a flashable zip:
TransStatusbar-SmoothCircleMod_4.0.3.maguro-signed.zip
Smali edits
OK...here's some instructions as a smali edit. Things to keep in mind here....smali is, for me at least, challenging to follow and fully comprehend what you are looking at. Also, this set of instructions is based off of working on a SystemUI for 4.0.3. My goal here is to give precise enough steps so that the right edits are made, while also trying to be "universal" in that this will hopefully work on other SystemUI's going forward. If we discover that tweaks need to be made, I'll edit this list.
Pixel format is stored as a integer constant. To review, here are some values of interest for this thread. (blue text is value)
OPAQUE(no alpha bit): -0x1
RGB_565(also no alpha): 0x4
TRANSLUCENT(many alpha bits) -0x3
First file to edit is StatusBar.smali. Open in your preferred text editor and search for this text:
Code:
Landroid/view/WindowManager$LayoutParams;-><init>(IIIII)V
Go to the line above it and change the last value from -0x1 to -0x3.
Next open PhoneStatusBar.smali. Search for this text:
Code:
const v4, 0x4800068
replace the 2 lines underneath with this:
Code:
const/4 v5, -0x3
move v2, v1
Next search for this text:
Code:
Lcom/android/systemui/statusbar/phone/PhoneStatusBar;->mPixelFormat:I
Once again we're going to edit the line above and change the last value to -0x3.
You can see the pattern of changing -0x1 to -0x3. However, you may notice that it's a 0x4 that your're replacing. You won't ever be replacing anything vastly different. So when following these instructions if you find that you're replacing something other than -0x1 or a 0x4, that should raise a red flag that it might not be the right thing to edit. *The first edit in PhoneStatusBar is a little different than the others and I think there is more than one way to do that, but this is how I did.
You may notice that I haven't listed the entire line for the search criteria ....this is because there may be differences with the local variables associated. Your file may be assigning the pixel format to local variable v8 and the next guys v9. *The first search in PhoneStatusBar I did give the whole line.
That's it for smali edits. Now you still have the res directory edits. With an aosp based rom, you need to change the hex value for status_bar_background in drawables.xml. Also, you now have translucency available for the softkey area.....it's background is set via hex color in res/layout/navigation_bar.xml.
I've been wanting a smooth circle battery mod! Only problem is, on Roman's AOKP rom flashing it makes the statusbar and virtual buttons disappear Happens with the other circle battery mod as well :/
Same here, soft buttons and status bar dissapear
Sent from my Galaxy Nexus using xda premium
This may just be me, but I got the battery only circle mod going on Romano's rom with the apex 4 kernel. Didn't work with the other kernel I was on.
awesome instructions im going to download asop on my linux pc tonight and have at the systemui on boxing day or something. ive got the softkeys themed but thats as far as i can get without a ton of fc's when decompiling and editing xml's and some pngs, so hopefully this will help me learn a bit more.
thanks for the awesome write up!
edit: i get the same problem as the above people when flashing this on the rom in my sig
pendo, thanks so much for this. its very educational and I appreciate the time you took to help all of us.
my question is...
in the cyanogenmod source instead of stating "opaque" or "translucent" it shows PixelFormat.RGB_565 which (I think) means it's 16bit and opaque. do you think it would have to then be changed to ARGB_8888, or something different? here's the link to the info I found: http://developer.android.com/reference/android/graphics/Bitmap.Config.html
I'm just unsure how to apply this info.
thanks man, love your work, glad to see you here!
Sent from my Galaxy Nexus using xda premium
I used apktool to decompile the systemui.apk. I found the status bar files. But they are smali. When I edit them with notepad+ I cannot find the PixelFormat line. Sucks.
Sent from my Galaxy Nexus using XDA App
joshnichols189 said:
I've been wanting a smooth circle battery mod! Only problem is, on Roman's AOKP rom flashing it makes the statusbar and virtual buttons disappear Happens with the other circle battery mod as well :/
Click to expand...
Click to collapse
My bad, I left out one VERY IMPORTANT detail. Whether or not you build your own or use the one I compiled it is a deodexed SystemUI.apk. If you previously had an odexed SystemUI then you MUST delete SystemUI.odex
I have been told that my apk works with this 4.0.3 IML74K rom.
gn00my said:
Same here, soft buttons and status bar dissapear
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Please see above note.
Also, these instructions as well as the provided apk DO NOT have Paul's softkey mod. I'm hesitant to say this, but I am tinkering a bit trying to replicate the edits in source form. I know I posted a SystemUI that had those edits for 4.0.2 but I did them as smali edits. I wish to add them to the source code which would make it much easier for updates. But I have no progress report on that. The *main* purpose of this thread was informational. I wanted to offer some help for someone to either do it themselves, or help someone who has the capacity/desire to update the apk as needed.
EkostonS said:
awesome instructions im going to download asop on my linux pc tonight and have at the systemui on boxing day or something. ive got the softkeys themed but thats as far as i can get without a ton of fc's when decompiling and editing xml's and some pngs, so hopefully this will help me learn a bit more.
thanks for the awesome write up!
edit: i get the same problem as the above people when flashing this on the rom in my sig
Click to expand...
Click to collapse
This is built purely from aosp sources, not CM. I would not expect what I compiled to work on anything other than aosp 4.0.3. However, the information in the first post should help you make a translucent statusbar if the CM9 source code is available somewhere.
allofusjw said:
pendo, thanks so much for this. its very educational and I appreciate the time you took to help all of us.
my question is...
in the cyanogenmod source instead of stating "opaque" or "translucent" it shows PixelFormat.RGB_565 which (I think) means it's 16bit and opaque. do you think it would have to then be changed to ARGB_8888, or something different? here's the link to the info I found: http://developer.android.com/reference/android/graphics/Bitmap.Config.html
I'm just unsure how to apply this info.
thanks man, love your work, glad to see you here!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I actually had some information regarding that in the first draft I had made, however I was getting concerned with the length as it was so I trimmed it down a bit.
Yes, RGB_565 is 16bit opaque. You should just change it to TRANSLUCENT. I've done this before, but in smali. One thing that I haven't figured out is why it's called RGBA vs ARGB. The hex values are done in ARGB. Go figure.
Also, here's some info that will help when trying to do this edit backwards, aka decompiling with apktool Obviously when aapt compiles it doesn't store the code as TRANSLUCENT....but here's some of the values that it does store of what you'll most commonly see:
TRANSLUCENT = -0x3
OPAQUE = 0x1
RGBA_8888 = 0x1
RGBX_8888 = 0x2
RGB_565 = 0x4
fatsix said:
I used apktool to decompile the systemui.apk. I found the status bar files. But they are smali. When I edit them with notepad+ I cannot find the PixelFormat line. Sucks.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
No....you cannot edit with Notepad.
my bad, I missed the "+"
Make your search for "mPixelFormat" and you should get better results. But it isn't as straight forward in smali. I'm still getting better at, but it is definitely more difficult to decipher what's happening in smali. Something that I've done to help is to compare source code with decompiled smali (making sure it's the same file).
I decompiled the classes.dex before with something else. Was easier to edit. Can't remember which or find the directions. Java - jar I think.
Sent from my Galaxy Nexus using XDA App
pendo said:
The *main* purpose of this thread was informational. I wanted to offer some help for someone to either do it themselves, or help someone who has the capacity/desire to update the apk as needed.
-Yes, I actually had some information regarding that in the first draft I had made, however I was getting concerned with the length as it was so I trimmed it down a bit.
-Yes, RGB_565 is 16bit opaque. You should just change it to TRANSLUCENT. I've done this before, but in smali. One thing that I haven't figured out is why it's called RGBA vs ARGB. The hex values are done in ARGB. Go figure.
Click to expand...
Click to collapse
-mission accomplished!
-isn't that how things always work out?
great, thank you very much! i hate having to reapply my theme edits with every rom flash. this is very helpful.
one more question...
will this edit "stick" in my local cyanogenmod workspace after a repo sync, or, would that require setting up my own github repo to view changes to cm framework vs my edited framework? please don't feel obligated to give an in depth explanation if that's what this question requires. I'd just like to know if my thinking is on the right path. thank you!
Sent from my Galaxy Nexus using xda premium
ahh that would make sense, but cm is built off asop and your last transparancy mod worked on cm9
Would anyone please show a pic with the final result? I am most interested in this mod once i get my GNex by new year.
Here you go mind of small but not a problem at all.
Sent from my Galaxy Nexus using xda premium
Neat trick. Many thanks!
did you noticed dialer status bar isn't black?..How can l fix taht?Thanks!
fatsix said:
I decompiled the classes.dex before with something else. Was easier to edit. Can't remember which or find the directions. Java - jar I think.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
If you're including the need to download aosp source, you would be correct. But the mod itself I feel is easier in source, solely based on the fact that it's easier to read. Sure, if you're familiar with the edit and have done it before you can decompile and search for whatever key terms you wish and then make the "-0x3" edits. But by viewing the source, it's pretty obvious on where/how to make the edits.
allofusjw said:
-mission accomplished!
-isn't that how things always work out?
great, thank you very much! i hate having to reapply my theme edits with every rom flash. this is very helpful.
one more question...
will this edit "stick" in my local cyanogenmod workspace after a repo sync, or, would that require setting up my own github repo to view changes to cm framework vs my edited framework? please don't feel obligated to give an in depth explanation if that's what this question requires. I'd just like to know if my thinking is on the right path. thank you!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It should, or at least it does with aosp and repo. Unless the package is updated.....(I think...)
EkostonS said:
ahh that would make sense, but cm is built off asop and your last transparancy mod worked on cm9
Click to expand...
Click to collapse
Yes, CM is based off aosp but I can assure you there are some significant differences...at least for gingerbread. I would anticipate there are less differences between CM9 and ics at this stage of the game. I didn't know that my last one worked on CM9.....my guess is that whatever changed in 4.0.3 hasn't made it's way into CM9's source.
manager77 said:
did you noticed dialer status bar isn't black?..How can l fix taht?Thanks!
Click to expand...
Click to collapse
No, I didn't notice anything....I have no way to view what I built! Lol...
Well, I'm not exactly sure off the top of my head. Does anyone know if my previous SystemUI had a translucent statusbar? I should be able to figure it out pretty easily if it was...
Thanks for the info. You really got me interested in this stuff!
For Windows users (like me), I believe somebody posted a VMWare images ready to do these kind of things.
Might give it a try when I'm back from holiday.
Sent from my Galaxy Nexus using xda premium
MODERATOR- Please move to correct sub-forum, it originally started as question but was solved and i turned it into a guide. Thanks.
Well... i had been trying to figure out how to change the carrier name in the notification bar for a few days and with some luck and some good tips from XDA Members and from antEris for pointing me in the right direction... here is a guide to help others who may want to change theirs as well!
**CAUTION- You will need to re-enter your google account info. This will wipe your contacts, and sync settings, so make sure you re-sync once complete!!**
Requirements:
Must have ROOT
FOR CDMA Devices ONLY! Will NOT work on GSM
Untested on all others. (if you test it on r800a, or any other one, let me know so i can update this.)
Things you will need:
1. Ninjamorph (Market)
2. HxD (google it, its free)
3. USB Cable
Method 1:
Steps:
1. Using Ninjamorph, select "New Project"
2. Navigate to system/framework
3. Select the framework-res.apk
4. Exit to home
5. Connect phone to PC
6. Browse to AndroidThemes/workspace/framework-resapk/res/xml on your sdcard.
7. COPY eri.xml to the desktop.
8. Now open the HxD application on your PC.
9. Drag the eri.xml into the big gray area.
10. You will now see a bunch of code, scroll till you see "Verizon Wireless"
11. Highlight Verizon Wireless, starting from the last letter going back to the "V" in Verizon.
12. Now you can type in what you want, UP TO 16 characters. If your custom banner is less than 16 characters, use the SPACEBAR and hit it for a total of 16 characters including how many your custom banner is. (i.e... XperianceIT is 11 characters, so i hit space bar 5 times)
13. Once thats done go ahead and exit HxD, it will ask if you want to save, say yes.
14. Now place the new eri.xml back on to the root of your sd card.
15. Disconnect Phone from PC
16. Open Ninjamorph
17. Select "Existing Project".
18. Browse to the ORIGINAL eri.xml and select it.
19. Now browse to the eri.xml you placed on the sdcard after modifying it.
20. Hit yes, a few times here, it will now take you back to the Ninjamorph main screen.
21. Select "Finish Project".
You will now be prompted for a few things, like if you want Ninjamorph to optimize it since its a .apk, I chose NO, not sure what will happen if you choose yes. Once thats done, reboot and enjoy!!
Method 2:
COMING SOON!
dont forget to thank/donate to me if you like this and it helps you out!
I'm not 100% sure on this,but as I recall,build.prop changes are undone after each reboot. You cant see changes until you reboot,but it gets reset,so you cant do it.
But google for it and you will find an answer
Fokezy said:
I'm not 100% sure on this,but as I recall,build.prop changes are undone after each reboot. You cant see changes until you reboot,but it gets reset,so you cant do it.
But google for it and you will find an answer
Click to expand...
Click to collapse
That's not true. If it was we wouldn't be changing dpi, model etc via build.Prop
Sent from my R800i using Tapatalk
XperianceIT said:
Ok here is a question for ya guys... is there a way to modify the build.prop to change the word "Verizon Wireless" on my status bar to say something different? I did it once on my Optimus S which was fully unlocked and rooted. My Play is rooted but BL locked. I have tried a few times using ROM Toolbox's build.prop editor and it saves the words i put in, but nothing changes on status bar even after reboot. What i did on my Optimus was every word that said "Sprint" i changed to say "gROM 2.2" and it worked, but i cant get it to work on my Play.
Click to expand...
Click to collapse
You mean in the notification drop down? I believe that information is stored in the framework not in the build.prop.
Sent from my R800i using Tapatalk
Yes in the drop down. I know for Optimus S it was in build.prop, but it could be different for Verizon Xperia Play.
The text for the carrier label is in an XML file in the framework-res.apk.
Its under /system/framework/framework-res.apk
Then you'll need to edit eri.xml inside the apk on your computer, then push it back to your phone
You can find more specific instructions Googling "how to edit eri.xml"
Or you might try conap's app to do it all for you, not sure if it will work as its intended for use with aosp roms but heck, Verizon's rom kinda looks aosp. Worth a try anyway.
http://forum.xda-developers.com/showthread.php?t=960099
Hope this helps.
Sent from my R800x using xda premium
Oh dude, im so walking to my laptop right now to try it!
**UPDATE: The Conaps App didnt work, resulted in having to do a nandroid recovery.
Got it! Took over an hour of playing and several crashes, 2 bootloops, and 2 nandroid recoveries later! But its friggin done!
See Original Post for full guide!!
Screenshots attached!
Sent from my R800x using XDA App
Has anyone on Three UK managed to get this to work?? It's hard to find the right lines of code when you're looking for "3".
Sent from my R800i using Tapatalk
kupo5131 said:
Has anyone on Three UK managed to get this to work?? It's hard to find the right lines of code when you're looking for "3".
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Oh wow, i didnt think of that.... let me take a look at the ERI.XML i have and see if maybe i can reference where my banner name is, maybe that will help.
I attached a screenshot of my eri.xml with some notes, let me know if this works, so i can update the guide for your guys phones as well.
XperianceIT said:
Oh wow, i didnt think of that.... let me take a look at the ERI.XML i have and see if maybe i can reference where my banner name is, maybe that will help.
I attached a screenshot of my eri.xml with some notes, let me know if this works, so i can update the guide for your guys phones as well.
Click to expand...
Click to collapse
Thanks for the quick reply but I don't see any attachments
Sent from my R800i using Tapatalk
kupo5131 said:
Thanks for the quick reply but I don't see any attachments
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Thats very odd.... i know it was there i even looked at it! Here it is again though...
That's what I have... No sign of a 3 :what:
Edit: I've played with the eri.xml file (changed a few values) and nothing at all changed. I have a feeling I need to find a different file to edit.
If i find out anymore information I'll let you know.
Sent from my R800i using Tapatalk
That is weird! I cant imagine it would be any different for your guys' phones. Is it possible for you to pull the eri.xml and send it to me. I don't think I will be able to test it on my phone. But Id like to look at it.
Edit: I wonder if yours can be changed in build.prop. are you running a custom rom?
XperianceIT
sent from my Xplay R800X, using XDA App!
Here is my eri.xml I'm running stock rom 42, rooted and bootloader locked. Using a Ice Cream Sandwich theme from the theme forums.
http://db.tt/uQpsalgf
Thanks for all the help so far.
Sent from my R800i using Tapatalk
Ok, I will check it out after work. Also, you might want to try changing it by editing your build.prop file, I know it doesn't work with mine but it might on yours. This can be done easily by using I rom tool box then click performance, then select build.prop editor. Yours might be a little harder cause of the "3". But I will copy the one I did on my old phine using this method to show which lines to edit, when I get off work.
EDIT- I couldn't download/view your eri.xml when I click the link I get an error.
XperianceIT
sent from my Xplay R800X, using XDA App!
kupo5131 said:
Here is my eri.xml I'm running stock rom 42, rooted and bootloader locked. Using a Ice Cream Sandwich theme from the theme forums.
http://db.tt/uQpsalgf
Thanks for all the help so far.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I couldnt download your XML, i get an error when i try. Also, what are you using to view the xml on your phone? I love the way that one looks, does it allow you to edit it as well?
Will this work on unlocked devices?
I zipped the xml so hopefully it will download this time.
http://db.tt/s5L0mENb
The app I used is called HEX Editor, it's free on the market!
I looked at the build.prop editor but I can't find anything referring to "3". This MAY be useful information to you but when my phone first starts and is searching for a signal is displays "3 UK" then when it has the signal it displays "3"
Sent from my R800i using Tapatalk
TheCraig said:
Will this work on unlocked devices?
Click to expand...
Click to collapse
I unfortunately do not have a unlocked device so i havent been able to try it. Honestly, i would just make a nandroid backup, and then try see if it works, if not then, restore nandroid, THEN i would try doing it using the build.prop method. (which i havent made a do it yourself tutorial) but you can try using ROMTool Box, it has a built in build.prop editor, you would just find your carrier name in the .prop file and replace it whith whatever you want. This method allows for more character input, but it didnt work with my phone, so im not sure if its a Stock ROM vs. Custom ROM or if its CDMA vs. GMS thing. It worked on my old Sprint Optimus S w/ Custom ROM. If you try it and get it to work, let me know which method you used, so i can update the OP for compatibility.
kupo5131 said:
I zipped the xml so hopefully it will download this time.
http://db.tt/s5L0mENb
The app I used is called HEX Editor, it's free on the market!
I looked at the build.prop editor but I can't find anything referring to "3". This MAY be useful information to you but when my phone first starts and is searching for a signal is displays "3 UK" then when it has the signal it displays "3"
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
That is useful, it gives me more line info to try and look for. Whats going to make it hard, is i wont have any way to test it myself, in order to narrow down what the value is we need to change, but i will look it over and see if anything stands out in comparison to mine. Can you send me a screen shot of the notification drawer pulled down? I want to see how it looks. Cause thats where the name will be not up in the bar by the clock and signal meter. (I ask, cause mine never said anything different while searching for signal as opposed to finding signal on the bar, or in notification pull down.)
Hi all,
I am trying to make a simple change to the Launcher2 desktop, I can't stand the divider line above the app drawer launcher button, which image file do I need to make transparent to achieve this?
Or is it not that simple??
Many thanks
Haven't tested, but check out res/drawable-xhdpi/divider_launcher_holo.9.png. I believe 9-patches have to be recompiled before replacing them in the APK, but I could be mistaken.
EDIT: Actually, might be hotseat_scrubber_holo.9.png and hotseat_track_holo.9.png instead.
copkay said:
Haven't tested, but check out res/drawable-xhdpi/divider_launcher_holo.9.png. I believe 9-patches have to be recompiled before replacing them in the APK, but I could be mistaken.
EDIT: Actually, might be hotseat_scrubber_holo.9.png and hotseat_track_holo.9.png instead.
Click to expand...
Click to collapse
Many thanks for this.
I am bringing this thread back to life folks as I would like to perform the same edit in Jelly Bean, but I would actually like to learn how to do it.
What are .9.png's and how do I edit them and are the files mentioned above still the same in Jelly Bean??
As I said I want to learn rather than rely on others to create mods so any help or a quick tutorial in how to remove the dock divider would be much appreciated!
Again, many thanks all!
wilskywalker said:
Many thanks for this.
I am bringing this thread back to life folks as I would like to perform the same edit in Jelly Bean, but I would actually like to learn how to do it.
What are .9.png's and how do I edit them and are the files mentioned above still the same in Jelly Bean??
As I said I want to learn rather than rely on others to create mods so any help or a quick tutorial in how to remove the dock divider would be much appreciated!
Again, many thanks all!
Click to expand...
Click to collapse
.9.png's are PNG image files that android recognizes as being stretchable, and it knows where to stretch them via the black outline around the image that can only be seen when decompiled.
.9.png's can only be edited when an apk has been decompiled, not just unzipped.
After decompilation you can use draw9patch, which is included with the Android SDK, to edit the border.
However, if you're just them(e)ing the image, you don't touch the border, as it could possibly mess things up. You really only use draw9patch to create a border on a new image.
Sent from my Galaxy Nexus using Tapatalk 2
The reason for this little hack is the fact those 2 pop-ups can become an extreme double-annoyance while driving in hot weather. Imagine, your battery is below 15%, yet scorching hot, beyond the charging cut-off threshold. Connect a charger and you get bombarded with the "charging paused, battery temperature too high" pop-ups. Disconnect it and you get a low battery ones. This little patch deals with the issue by simply disabling the annoying pop-ups. It also disables the annoying battery full notification.
Please note, this doesn't modify any functionality, it just disables the pop-ups. The battery will not and should not charge when overheated.
Instructions:
Download and unpack "BatteryPatch.zip", you should now have "Patch.js" jscript along with the "utils" directory.
Fetch your "/system/app/SystemUI.apk" from the device, place it in the same directory, along with the "Patch.js".
Apply the patch by launching "Patch.js" and push the patched SystemUI.apk back to the device.
Updates:
Not every ROM seems to have the battery full notification and/or battery overheating popup. Patching those is now optional, the script will show a warning in case it fails to patch those instead of erroring out completely.
There are some ROMs out there with showLowBatteryWarning method looking somewhat different from what i've seen on my S3. In order to try & let the patch work on more ROMs, the showLowBatteryWarning method is now being bypassed entirely. Hopefully, no ROM does anything important inside that method, besides showing the annoying low battery popups. In any case, as usual, you use the patch - you take the risk.
PS: For those willing and able to apply the patch manually, download the second zip and do a 3 way merge.
===> reserved <===
Nice mod...just added it to my rom.. purposely drained the battery...no notification pop up (hopefully won't get the temp warning anyway)
Lovely work
Already given 8 thanks today...I will come back!
_neutron_ said:
Nice mod...just added it to my rom.. purposely drained the battery...no notification pop up (hopefully won't get the temp warning anyway)
Lovely work
Already given 8 thanks today...I will come back!
Click to expand...
Click to collapse
Thanks. Temp warning should not be there any longer, too. But the rest of them (bad charger, overcurrent, stuff like that) are still there, i don't think killing those is a good idea.
The reason i did this was primarily the temperature warning. I've been looking all over the forum on how to disable it, but couldn't find any info, so i though, "what the hell, i can find it myself, it's not such a big deal"... during the search i've noticed the low bat one, too, and though "hmm, i hate that one too, lets kill it as well".
Thats about it.
Just patched and tested the full battery notification as well, first post updated.
Lovely, gonna test this when I get home
Thanks for the update
sorry to sound like a total noob, but im completely new to apktool. was reading up on it and trying it, but im slightly confused. what options do you chose exactly when decompiling? i couldnt find the power smali file after decompiling
There are plenty of explanations/tutorials on this around the forum. About not having the smali after decompiling... any chance your rom is odexed? In this case you wont be getting any smali files, cause all the code is in the odex file, not the apk. You will have to deodex it in this case and, possibly, reodex it before placing it back on the device (not sure about it, specifically i am unsure how the odex dependecies work).
Sadly, i cannot provide a ready to use apk, there are too many versions being in use, especially considering the 15 toggles mod, the battery icon mod as well as many other visual mods also patch stuff inside this apk, increasing the number of variations even further. So, sorry, no ready to use apk.
Is there a flashable file?
Sent from my GT-I9300 using Tapatalk 2
baste07 said:
Is there a flashable file?
Click to expand...
Click to collapse
Nope, and it is extremely hard to make. In fact, impossible, with the currently available CWM tools, as far as i know. It would be "for ROM version <insert_version_here> with 15 toggles and circle battery", "for ROM version <insert_version_here> without 15 toggles and green battery" etc etc etc kind of variations, and as i already mentioned, i doubt this is a viable option.
Anyone can prove me wrong and provide a way of writing a CWM script that would decompile (deodex if needed) an existing apk, apply a patch, recompile it and than replace it ? Out of all the things needed, i only know how to do the "replacing" part
Can i ask a massive favour?
im now havin problems with my systemui in regards to it recording the changes (decompiling & recompiling - i think i have an issue with my pc but i cant figure it out)
Could you apply the changes to the attached file for me?
InfX said:
There are plenty of explanations/tutorials on this around the forum. About not having the smali after decompiling... any chance your rom is odexed? In this case you wont be getting any smali files, cause all the code is in the odex file, not the apk. You will have to deodex it in this case and, possibly, reodex it before placing it back on the device (not sure about it, specifically i am unsure how the odex dependecies work).
Sadly, i cannot provide a ready to use apk, there are too many versions being in use, especially considering the 15 toggles mod, the battery icon mod as well as many other visual mods also patch stuff inside this apk, increasing the number of variations even further. So, sorry, no ready to use apk.
Click to expand...
Click to collapse
ah that explains why there is no smali file. thanks for the help!
I also cannot get this mod to work, wishing easier method coming soon, like one zip file thru recovery or similar... i dont have patience to this sorta things.
Sent from my GT-I9300 using xda app-developers app
_neutron_ said:
Can i ask a massive favour?
im now havin problems with my systemui in regards to it recording the changes (decompiling & recompiling - i think i have an issue with my pc but i cant figure it out)
Could you apply the changes to the attached file for me?
Click to expand...
Click to collapse
Done. Enjoy.
GalaxyS3man said:
I also cannot get this mod to work, wishing easier method coming soon, like one zip file thru recovery or similar... i dont have patience to this sorta things.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Well, if you know of someone that could have possibly coded an infrastructure for doing this kind of patches onboard, automatically, i would be glad to get pointed to the right direction, and will integrate it there. Currently, i don't know of any.
Seriously, though... is it possible to baksmali in recovery mode somehow ? Can one run patch, sed and similar utilities there ? If yes, can i see an example ? Cause if that's possible, it can make a "flashable zip" for stuff like that possible.
hmm, so if i have these files in my app folder:
systemui.apk
systemui.odex
I cannot just add/replace the code as described?
reprazent said:
hmm, so if i have these files in my app folder:
systemui.apk
systemui.odex
I cannot just add/replace the code as described?
Click to expand...
Click to collapse
You can deodex, patch the smali while having it handy during deodexing, and, possibly, reodex it back into an odex file and replace just the odex. Never did it myself, though. I find odexed roms to be too much of a hassle while modding stuff to use those.
Is it ok if i ask help too?
InfX said:
You can deodex, patch the smali while having it handy during deodexing, and, possibly, reodex it back into an odex file and replace just the odex. Never did it myself, though. I find odexed roms to be too much of a hassle while modding stuff to use those.
Click to expand...
Click to collapse
I been trying for days...help, i go crazy with those popups
Thats what i have on my rooted S3 I just like Omega rom, tried several others non Samsung based aswell.
Sent from my GT-I9300 using xda app-developers app
GalaxyS3man, your apk is NOT odexed. Took me barely 2 minutes to apply the patch. Here we go...
PS: TBH, i've been under impression people on XDA are perfectly familiar applying and/or finding out this kind of stuff, really