Related
Was searching the forums looking for a way to remove the clock from my status bar and have come to the conclusion it may be a little over my head at this point. Can make me a flashable zip to remove the clock? Or maybe some step by step instructions on how I would accomplish this? Thanks in advance.
Update 3/26---------------------------------------------------------------------------
JKILO is working on a flashable .zip for MikShift, so until then here's how you do it manually....
Instructions for removing status bar clock on an odex rom:
Props to JKILO and riggsandroid for helping a total noob and doing most of the work. Also thanks to Steelh for showing us the lines to replace. His method for deodex roms is here. If I forgot to add anyone that helped out, let me know. I always throw props where its deserved.
You are modding at your own risk. Nobody who helped bring this to you is responsible for bricked phones or temper-tantrums.
Requirements:
-Rooted Evo Shift
-Odex Rom
-Windows (I used Windows 7. If you are using another os, I'm sure you can figure it out. If not, ask)
-sdk properly set up
-smali\baksmali
-dexopt-wrapper
-knowledge of the above things (at least have the ability to google for info)
-a nandroid backup of your phone (for obvious reasons)
-patience
-/system mounted as r/w (I did this in terminal emulator from my phone: type:
"su" then hit enter. type: "mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system" then hit enter)
First thing you need to do is pull services.jar from /system/framework;
-"adb pull /system/framework/services.jar"
Next you need to open up services.jar with 7zip or winrar or something similar
Pull classes.dex out into a working folder with smali\baksmali
(I just did everything in my platform-tools folder in sdk so I didnt have to switch back and forth. You can do it however you want.)
Open command prompt as administrator
Cd to your work folder
Type this line:
java -jar baksmali.jar classes.dex
This will will create a folder named out in your work folder
Navigate to \com\android\server\status and look for StatusBarPolicy.smali
Open StatusBarPolicy.smali with Notepad or something similar
Search for:
.line 593
invoke-direct {p0}, Lcom/android/server/status/StatusBarPolicy;->updateClock()V
Add the following line two spaces under that to look like this:
invoke-virtual {p2, v3, v6}, Lcom/android/server/status/StatusBarService;->setinvisibilty(Landroid/os/IBinder;Z)V
It should look like this now:
.line 593
invoke-direct {p0}, Lcom/android/server/status/StatusBarPolicy;->updateClock()V
invoke-virtual {p2, v3, v6}, Lcom/android/server/status/StatusBarService;->setinvisibilty(Landroid/os/IBinder;Z)V
Now click file then save as. Be sure to change the file type or youll save it as a text file that is useless to you.
Now head back to your command prompt.
still being cd'd to your work folder, type this:
java -jar smali.jar out
This will create a new .dex file named out.dex. Rename it to classes.dex and replace the classes.dex from services.jar with the new one you just made.
Now place the modified services.jar and dexopt-wrapper on your sdcard and plug your phone into your computer. (charge only)
Back to command prompt in your platform-tools directory
Type these commands in the order they appear, hitting enter after each one:
-adb shell
-cd /system/bin
-busybox cp /sdcard/dexopt-wrapper /system/bin
-busybox chmod 755 dexopt-wrapper
-cd /sdcard
-dexopt-wrapper services.jar new.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar
- busybox dd if=/system/framework/services.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
-cd /system/framework
-busybox cp /sdcard/new.odex services.odex
-busybox chmod 644 services.odex
-sync
-reboot
Your phone will reboot and, viola! NO Clock!!!!
bobtsunam said:
Was searching the forums looking for a way to remove the clock from my status bar and have come to the conclusion it may be a little over my head at this point. Can make me a flashable zip to remove the clock? Or maybe some step by step instructions on how I would accomplish this? Thanks in advance.
<Blaze One>
Click to expand...
Click to collapse
on page 2 of this forum.
http://forum.xda-developers.com/showthread.php?t=966190
riggsandroid said:
on page 2 of this forum.
http://forum.xda-developers.com/showthread.php?t=966190
Click to expand...
Click to collapse
Saw that one but I havent done anything to that extent before. Was really hoping someone had a zip out there I could flash. Oh well. Maybe in the future. Until then ill try my hand at compiling....
<Blaze One>
bobtsunam said:
Saw that one but I havent done anything to that extent before. Was really hoping someone had a zip out there I could flash. Oh well. Maybe in the future. Until then ill try my hand at compiling....
<Blaze One>
Click to expand...
Click to collapse
what rom are you on?
riggsandroid said:
what rom are you on?
Click to expand...
Click to collapse
Currently on infinite's 2.0.
<Blaze One>
So I'm still trying to figure this out. From what I read I need to edit system/framework/services/classes? How would I go about editing this?
<Blaze One>
bobtsunam said:
So I'm still trying to figure this out. From what I read I need to edit system/framework/services/classes? How would I go about editing this?
<Blaze One>
Click to expand...
Click to collapse
Download apktool - http://code.google.com/p/android-apktool/
Follow instructions to setup your machine (installing framework, etc)
Decompile the services.jar in the /system/framework folder
Edit the lines indicated in teh smali files and recompile.
Push updated services.jar to your phone, reboot (takes a while, has to rebuild dalvik cache) and you should be good to go.
Thanks. I'll attempt this when I get home. If/when I get this completed, is it possible to make a general .zip file for others to flash if they are interested in doing the same thing? I've seen the question posed on many forums but haven't found a file that can be flashed. Would be nice to have something everyone can benefit from...
Edit: I'm guessing its gonna be Rom specific?
bobtsunam said:
Thanks. I'll attempt this when I get home. If/when I get this completed, is it possible to make a general .zip file for others to flash if they are interested in doing the same thing? I've seen the question posed on many forums but haven't found a file that can be flashed. Would be nice to have something everyone can benefit from...
Edit: I'm guessing its gonna be Rom specific?
Click to expand...
Click to collapse
Definitely rom specific. Unique for themes as well, I believe.
Sent from my MikShift.
smoothtaste said:
Definitely rom specific. Unique for themes as well, I believe.
Sent from my MikShift.
Click to expand...
Click to collapse
Figured as much. Hopefully I will be able to pull this off. I have not done any programming related stuff on Android yet. Most I've done is change an icon or two but that was pretty simple using ninjamorph. I literally know nothing about the file structure or coding. Might he time to start learning java at least if I'm gonna get into modding to this extent. We shall see how all this goes later tonight.
<Blaze One>
I have been trying to rebuild services.jar after editing StatusBarPolicy.smali and for some reason it doesn't work. I get something to this extent:
Exception in thread "main" java.lang.NullPointerException
(and then a bunch of other lines...)
Any idea what's goin on?
By the way, I'm replacing this:
.line 593
invoke-direct {p0}, Lcom/android/server/status/StatusBarPolicy;->updateClock()V
With this:
.line 593
invoke-direct {p0}, Lcom/android/server/status/StatusBarPolicy;->updateClock()V
invoke-virtual {p2, v3, v6}, Lcom/android/server/status/StatusBarService;->setIconVisibility(Landroid/os/IBinder;Z)V
Does this look right?
Thanks for any help...
Ok....I noob'd it. When a saved the changes to the StatusBarPolicy file I saved it as a text file somehow. Was able to build services.jar and push it back but the changes didn't take or something. Clock is still there. Am I editing the right line with right changes?
bobtsunam said:
Ok....I noob'd it. When a saved the changes to the StatusBarPolicy file I saved it as a text file somehow. Was able to build services.jar and push it back but the changes didn't take or something. Clock is still there. Am I editing the right line with right changes?
Click to expand...
Click to collapse
Just want to make sure - you restarted? It will take a little while because it has to rebuild the Dalvik Cache cause you modified the .jar file.
Yeah I actually mounted /system from recovery and pushed back in from there. I even tried it a second time, formatting dalvik cache. Do I need to restart an additional time?
<Blaze One>
bobtsunam said:
Yeah I actually mounted /system from recovery and pushed back in from there. I even tried it a second time, formatting dalvik cache. Do I need to restart an additional time?
<Blaze One>
Click to expand...
Click to collapse
No that should work the way you're doing it. Not sure...
riggsandroid said:
No that should work the way you're doing it. Not sure...
Click to expand...
Click to collapse
Just remembered something I saw as services.jar was rebuilding. Right before it finished it said sources not found. Don't know if this gives a clue. Also I'm running dreads blue honeycomb theme. Would that have something to do with it?
<Blaze One>
Figured I would post the steps I took in case I'm messing it up somehow. I'm using Windows 7.
First thing I did was adb pull services.jar from /system/framework using: adb pull /system/framework/services.jar
Moved services.jar to a folder I created on the root of my c: drive called test.
Opened cmd as an administrator.
Decoded services.jar using : apktool d services.jar which created services.jar.out in my test folder.
Navigated to StatusBarPolicy.smali @ c:\test\services.jar.out\smali\com\Android\server\status
Edited the lines as stated previously.
Opened cmd back up and rebuilt with: apktool b -f -d services.jar.out which put the new services.jar in a new folder called build located in services.jar.out
Noticed at this point that the meta file wasn't in services.jar so I copied from the original to the new.
Then pushed back to phone while in recovery using: adb push services.jar /system/framework and booted.
See anything I'm doing wrong?
<Blaze One>
You don't need apktool to do that. Use smali.jar and baksmali.jar to decompile and recompile.
http://code.google.com/p/smali/
Download the two jar files under featured downloads. For ease of typing, rename them baksmali.jar and smali.jar, respectively, and put them in c:\. Open as archive with 7zip to pull the classes.dex file out. Move classes.dex to c:\. Open admin cmd prompt and type:
java -jar -Xmx512M baksmali.jar c:\classes.dex
This will dump classes.dex into a folder c:\out. Make your smali edit then to recompile the dex file type:
java -jar -Xmx512M smali.jar c:\out
This will produce c:\out.dex. Move the file to your Desktop, rename it classes.dex and put it back in your services.jar. Push the file in recovery, no need to clear dalvik cache and it should work. If it's still not working, link me your original services.jar and I'll try to get it working for you.
EDIT: btw, kudos to you for taking the initiative to learn this. I have much respect for that.
EDIT 2: Are you on 2.0 odexed or deodexed?
Sent from my PG06100 using Tapatalk
tambourineman86 said:
You don't need apktool to do that. Use smali.jar and baksmali.jar to decompile and recompile.
http://code.google.com/p/smali/
Download the two jar files under featured downloads. For ease of typing, rename them baksmali.jar and smali.jar, respectively, and put them in c:\. Open as archive with 7zip to pull the classes.dex file out. Move classes.dex to c:\. Open admin cmd prompt and type:
java -jar -Xmx512M baksmali.jar c:\classes.dex
This will dump classes.dex into a folder c:\out. Make your smali edit then to recompile the dex file type:
java -jar -Xmx512M smali.jar c:\out
This will produce c:\out.dex. Move the file to your Desktop, rename it classes.dex and put it back in your services.jar. Push the file in recovery, no need to clear dalvik cache and it should work. If it's still not working, link me your original services.jar and I'll try to get it working for you.
EDIT: btw, kudos to you for taking the initiative to learn this. I have much respect for that.
EDIT 2: Are you on 2.0 odexed or deodexed?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Its mikshift lol we've been tryin to figure it out together..so odexed
Sent from my PG06100 using XDA App
You know apktool uses small baksmali right?
i find it easier to use the same program for stuff - its nice that apktool does both .jar and .apk files.
tambourineman86 said:
You don't need apktool to do that. Use smali.jar and baksmali.jar to decompile and recompile.
http://code.google.com/p/smali/
Download the two jar files under featured downloads. For ease of typing, rename them baksmali.jar and smali.jar, respectively, and put them in c:\. Open as archive with 7zip to pull the classes.dex file out. Move classes.dex to c:\. Open admin cmd prompt and type:
java -jar -Xmx512M baksmali.jar c:\classes.dex
This will dump classes.dex into a folder c:\out. Make your smali edit then to recompile the dex file type:
java -jar -Xmx512M smali.jar c:\out
This will produce c:\out.dex. Move the file to your Desktop, rename it classes.dex and put it back in your services.jar. Push the file in recovery, no need to clear dalvik cache and it should work. If it's still not working, link me your original services.jar and I'll try to get it working for you.
EDIT: btw, kudos to you for taking the initiative to learn this. I have much respect for that.
EDIT 2: Are you on 2.0 odexed or deodexed?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using XDA App
I found a solution to disable increasing ringtone:
I attached modified Phone.apk (from deodexed JPM - Android 2.2). Download it and skip tutorial to the 9 step.
0. Download Apk Manager from here: http://forum.xda-developers.com/showthread.php?t=695701
1. Get your Phone.apk (/system/app/Phone.apk) and copy it to apk_manager\place-apk-here-for-modding.
2. Get twframework-res.apk (system/framework/twframework-res.apk) and copy it to apk_manager\place-apk-here-for-modding.
3. Open Apk Manager running Script.bat inside apk_manager folder.
4. Choose option 22 and select the number corresponding to Phone.apk.
4.5. Choose option 19 (compression level) and select 7 (maybe works with 9, i just tried with 7 and worked).
5. Choose option 10 and when asked drag twframework-res.apk to it.
3. Open folder with Phone source (<Apk Manager folder>\projects\Phone.apk\smali\com\android\phone ).
4. Open file Ringer$1.smali with your favourite text editor.
5. Find lines (2 lines) that reads:
Code:
invoke-virtual {v1, v5, v2, v4}, Landroid/media/AudioManager;->setStreamVolume(III)V
and
Code:
invoke-virtual {v1, v5, v3, v4}, Landroid/media/AudioManager;->setStreamVolume(III)V
6. Delete this lines, save the file.
7. Go back to Apk Manager and choose option 11, when asked if a system apk choose "yes", then when asked if u want to put aditional files say "yes".
8. When "Press any key to continue . . ." appears go to apk_manager\keep\ and remove classes.dex (this is the compiled modified data or something ), then press Enter to finish.
Click to expand...
Click to collapse
9. Put the phone into Flight mode.
10. Push Phone.apk into /system/app folder
10.5 Turn Flight mode off and/or reboot the phone to avoid FCs.
11. Enjoy constant-volume ringtones.
Click to expand...
Click to collapse
If you get a "force close" Unzip (do not decompile!) from modified Phone.apk file "classes.dex".
Next unzip Stock, deodexed Phone.apk, and replace "classes.dex" with file with same name from modified file and zip it. Then go to 9 step of this tutorial.
Founded on XDA - original thread: http://forum.xda-developers.com/showthread.php?t=893461
Thanks to Kyrillos13 for editing Ringer$1.smali and recompile.
What kind of issues? I had also problems with apktool, but then i found out that i have to download both, the install and the apktool itself... hope that helps.
I am trying
will post results soon!
have a try
anybody tryed already? i will find time in 5 hours or so...
I tried and... done It is working.
kyrillos13 said:
I tried and... done It is working.
Click to expand...
Click to collapse
Can you attach edited Phone.apk (stock, deodexed)?
tgm28 said:
Can you attach edited Phone.apk (stock, deodexed)?
Click to expand...
Click to collapse
Yeah Of Course... Here it is
Don't forget to disable the phone call sounds.
Configuration -> Call Settings -> All Calls -> Call Status Tones.
Uncheck them all. If you don't disable the sounds, your calls will be dropped (can't receive and also cant's make calls).
Hope it helps.
Docnus said:
Don't forget to disable the phone call sounds.
Configuration -> Call Settings -> All Calls -> Call Status Tones.
Uncheck them all. If you don't disable the sounds, your calls will be dropped (can't receive and also cant's make calls).
Hope it helps.
Click to expand...
Click to collapse
If someone know How to Fix that may feel free to post it here.
Wipe /data don't fix that.
eventually you could try the phone.apk from Jumba´s NeonGT SGS theme (may need porting work like image scaledown...) it features non increasing ringtone without those troubles along with call recording. dont know if this is so easy, but definitley worth a try...
Yeah, i did try it yesterday (there is a phone.apk and 3 lib files) but the phone stucked at bootloader :/
to bad....
I Fix that.
I copy classes.dex (this file contain a smali folder) from modified Phone.apk to stock, deodexed Phone.apk
And Everything Works. No Force Close
tgm28 said:
I Fix that.
I copy classes.dex (this file contain a smali folder) from modified Phone.apk to stock, deodexed Phone.apk
And Everything Works. No Force Close
Click to expand...
Click to collapse
so now we have perfect non increasing ringtone? congrats...
I have problem with non working Phone.apk. I replaced the apk but now I have no signal(no working connection). I also did buck up the wrong file so I cannot restore it. What can I do to fix it?
You could request the original file here ;-)
Can I have an original Phone.apk from 2.1 eclair?
Just tried it and failed. Going for reflash...
Huuu, didn't think u could be on eclair rom nowadays. This mod is only for froyo roms... i think there wont be many people with eclair around on xda anymore. Better request in general forum eventually.
FadeFx said:
Huuu, didn't think u could be on eclair rom nowadays. This mod is only for froyo roms... i think there wont be many people with eclair around on xda anymore. Better request in general forum eventually.
Click to expand...
Click to collapse
Hahaha! I'm rather conservative! But I forgot to update the above. I eventually flashed the JPF. But again, the Phone.apk icon is different. Do I have to deodex the rom?
Here is another solution to disable the lockscreen vibration. Root is needed.
Be careful, you are responsible for everything you do, not me.
Please don't ask, i won't do anything like a graphical interface or else to enable/disable.
This thread was the inspiration: http://forum.xda-developers.com/showthread.php?t=1605363
I dont yet know how to compile the source from this thread, so i searched for another way, baksmalimanager is the solution.
It decompiles and recompiles .jar files and their contents.
Download baksmalimanager
Take the framework.jar from /system/framework/ on the device and place it into the baksmalimanager directory on the pc.
Be sure to remain a backup of this file if something doesn't work.
Then run "baksmali Manager.bat" press 4 to select the framework.jar file and then 1 to decompile it.
Open this directory path inside your baksmalimanager directory framework\com\android\internal\widget\multiwaveview.
Open MultiWaveView.smali in a text editor, search for "setVibrateEnabled" until you find following line, remove it completely:
Code:
invoke-virtual {p0, v11}, Lcom/android/internal/widget/multiwaveview/MultiWaveView;->setVibrateEnabled(Z)V
Save the file. Run "baksmali Manager.bat" again if you closed it. Press 4, select the framework.jar and then press 2 to recompile.
Then open the framework.jar with 7-Zip or something else like that and replace the classes.odex file with the one from the baksmalimanager directory. Think of the backup before you do it.
Then replace the framework.jar in your devices /system/framework/ directory with the modded framework.jar.
Reboot and vibration is gone.
If something doesn't work like expected. Replace with the original framework.jar again.
works great on CM9 ROM latest nightly build for SGS2,,,,,now i can remove the vibra,,,,,thx a lot mate,,,
just suggestion, it's better to include adb.exe and all related files because without it,your program cannot work,,,
And you're now +1 in your thx meter,,,,
A couple of Qs before I replace my old framework.jar:
1.What if I just put '#' before the line I'm supposed delete? Seeing as # is usually a comment and does not affect the code, isn't it the same if I comment it or delete it? I did delete it, i'm just asking out of curiosity...
2.As much as I can understand, you don't need ADB for this, right? The program decompiles the .jar file without it with no problems, at least for me...
You got your thanks
EDIT: Works like a charm on my HTC Desire (SpazeDog's ICS ROM). Finally, the dreaded vibrations have stopped!
Though the answers to the upper questions would be appreciated...
thank you for this, works great on Galaxy Ace with CM9
Thanks Heaps badcrow! Works perfectly on Galaxy S2, CM9.0.0.
1. Tested commenting out the line (with #) and it works perfectly.
2. Doesn't need ADB coz it's working on the file on your PC, not on your phone, just hit any key when baksmali tells you.
Still have vibrate elsewhere, just not on lockscreen. Also, the file I replaced in framework.jar was classes.dex (not .odex).
siganid said:
1. Tested commenting out the line (with #) and it works perfectly.
Click to expand...
Click to collapse
Thanks for confirming, I thought that might happen, but I just didn't want to destroy my phone
siganid said:
2. Doesn't need ADB coz it's working on the file on your PC, not on your phone, just hit any key when baksmali tells you.
Click to expand...
Click to collapse
I really don't want to say this, but; I told you so
As for the other vibrations, see other settings ot other baksmali files and mess with them
on AOSP JellyBean 4.1.1, I had to edit GlowPadView.smali to remove the vibration.
"framework\com\android\internal\widget\multiwaveview"
form this:
Code:
invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
to this:
Code:
[B]#[/B]invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
this has worked for me.
im very confused bro...
"replace the classes.odex file with the one from the baksmalimanager directory."
in baksmalimanager directory not file the classes.odex,,,
You 'baksmali' the jar file (de-compile), make the edits you need and 'smali' (compile). Once you do that, you should have a classes.dex (not .odex, but .dex !!) file.
Then just take 7Zip (or winrar, or whatever else can open .jar files) and replace the original classes.dex with the one you 'smali'd'
badcrow said:
Take the framework.jar from /system/framework/ on the device and place it into the baksmalimanager directory on the pc.
Be sure to remain a backup of this file if something doesn't work.
Then run "baksmali Manager.bat" press 4 to select the framework.jar file and then 1 to decompile it.
Open this directory path inside your baksmalimanager directory framework\com\android\internal\widget\multiwaveview.
Open MultiWaveView.smali in a text editor, search for "setVibrateEnabled" until you find following line, remove it completely:
Code:
invoke-virtual {p0, v11}, Lcom/android/internal/widget/multiwaveview/MultiWaveView;->setVibrateEnabled(Z)V
Save the file. Run "baksmali Manager.bat" again if you closed it. Press 4, select the framework.jar and then press 2 to recompile.
Then open the framework.jar with 7-Zip or something else like that and replace the classes.odex file with the one from the baksmalimanager directory. Think of the backup before you do it.
Then replace the framework.jar in your devices /system/framework/ directory with the modded framework.jar.
Reboot and vibration is gone.
If something doesn't work like expected. Replace with the original framework.jar again.
Click to expand...
Click to collapse
Hmmm. Doesn't seem to work for me Maybe I did something wrong. I had to deviate from these steps a little for my phone. Maybe I screwed it up.
I have a deodexed stock rom for Droid 4 running ICS 4.0.4. I actually found this file and line of code in the framework-ext.jar file instead of framework.jar. And, for some reason, baksmali manager wouldn't find the file when I typed 4, unless I renamed the file to framework.jar. Once I did, it found it and decompiled it fine. I changed the code and recompiled, and copied the classes.odex file into the framework.jar file. Then I renamed it BACK to framework-ext.jar. But when I put it back in the system/framework directory, the phone got stuck at the Droid Eye screen on bootup. It just continuously showed it. I had to used adb to push the old file back in place.
Can you just not do it this way? Any ideas? Thanks
How come Baksmali didn't recognize a .jar file? It does, with every version of the name 'framework' I've tried...
BTW, was there even an .dex file inside the .jar file? (de-odexed, kinda sounds like there aren't any more .dex files... just a thought, tho, since I have no idea what that actually means...)
Did you delete the old version of the framework-ext.jar? Or at least rename it (I keep a renamed original copy of the file right there in /system/framework, just in case)?
someone755 said:
How come Baksmali didn't recognize a .jar file? It does, with every version of the name 'framework' I've tried...
BTW, was there even an .dex file inside the .jar file? (de-odexed, kinda sounds like there aren't any more .dex files... just a thought, tho, since I have no idea what that actually means...)
Did you delete the old version of the framework-ext.jar? Or at least rename it (I keep a renamed original copy of the file right there in /system/framework, just in case)?
Click to expand...
Click to collapse
I'm not sure why it didn't recognize the framework-ext.jar file. Was hoping you could tell me Well anyway, it looks like my rename method should work, because all that Baksmali does is extract the file. So, if I gotta rename framework-ext.jar to framework.jar to do the work, and then change it back, it shouldn't matter. And yes the .dex file was in there (and lol nice xP )
I figured out what I did wrong. I replaced the .dex file with 7Zip incorrectly. I couldn't figure out how to place the new .dex file into the .jar file, so I tried clicking "Copy" and changed the destination directory to C:\...\framework-ext.jar. What that did was erase the .jar file, and replaced it with a renamed version of the .dex file. Whoops, haha I later figured out that you can just drag and drop.
Ok, so my phone boots now....Buuuuuuut....the vibration is still there???? The lockscreen still vibrates. Although, the vibration doesn't seem as intense as before. But, it's still there, even if I disable "Vibrate on Touch" in the sound menu.
I checked to make sure that I didn't accidentally put the original framework-ext.jar file into /system/framework/, but I confirmed that I put the modified file in there with the line of code removed, so I'm not crazy Maybe this method just doesn't work completely on my ROM, but I like that the vibration is at least less intense. Thanks so much for the help!
Request for option on CM website
Hi gyus,
thaks for the explanations.
I don't really like to change the code so I requested the option to able or disable vibrations on lock screen on the CM website.
Maybe if we're enough to say it's a good idea, they'll actually program it
Here is the post (as I'm a new member I can't post outside links, repalce underscores by dots)
forum_cyanogenmod_com/topic/59819-request-lock-screen-vibration-option/
If you didn't subscribe, I suggest you do it because there is many many good stuff there too
Bijnok
Thanks!! ...works great on my SGSII..
Sent from my AOKP'd T989
reapsor said:
on AOSP JellyBean 4.1.1, I had to edit GlowPadView.smali to remove the vibration.
"framework\com\android\internal\widget\multiwaveview"
form this:
Code:
invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
to this:
Code:
[B]#[/B]invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
this has worked for me.
Click to expand...
Click to collapse
Recently installed CM9 from modpank and encountered this problem, but your version, help me! Thank you!
Just an update on this, if you want this to work on the ICs and JB lockscreen you also need to repeat the process for GlowPadView.smali as well.
4.2.1
Does anyone know how to get it to work on 4.2.1? I tried it 3 different times with no luck.
thats what you get with a new firmware
Ask on the ROM thread, maybe? If there's enough interest, maybe the DEVs will include a setting in the next version...
there‘s no MultiWaveView.smali after decompiling of moto fire xt
What about some info about your ROM...?
Wouldn't that be nice?
*THIS HOPES TO SERVE AS A SLIPPERY STEPPING STONE FOR THOSE VENTURING INTO THE MODDING SCENE - AND FOR ANYONE TO POST THEIR QUESTIONS, ANSWERS, REQUESTS, AND COMMENTS ABOUT THEMES/MODS*
NOTE: This is still a WIP... I will clean it up, add/remove/replace as I, and others, see fit. Trying to make this a good resource for those wanting to journey into the rabbit hole..
I will try to make this as general as possible, but it is still mostly based off of Windows 7 OS. I will attempt to incorporate Linux (Ubuntu) as I can. Also, I urge other devs and users to please offer your advice or comments on how to make this thread as useful as possible, "I accept opinions, phone numbers, and the fact that not everyone wants smiles and eye contact" (sorry, homage to doseone - couldn't resist) - but PM's or posts are fine...
Finally, I have said it before about Android, and will say it again.. “there is more than one way to skin a cat...” meaning, that there are many, many ways to achieve the same outcome with different methods (but, I’m not sure who would want to skin a cat, and what for… but I guess I don’t even want to know where that phrase came from) - so, PLEASE SEARCH for more information, methods, tricks, and techniques - I can't fit everything under the sun into two posts - plus, I still got a lot to learn myself ...
Tools
Java JDK
Android SDK
7-zip (or similar file manager)
Notepad++ (or similar text editor – do not use windows notepad!)
GIMP (or similar image editor)
Sign+ (or similar zip-signing program)
Getting files from your phone
-Root browser: copy from original file location to sdcard
-adb pull (I will not go into an adb tutorial, but here’s an example):
Code:
adb pull /system/app/SystemUI.apk C:\Pulled
(I have two folders (“Pulled” and “Push”) in the root of my C:\ drive, where I do all my pulling and pushing)
-Take from a cwm backup (nandroid)
-Make a System Dump through adb (this is just something kind of fun, but not so necessary):
Code:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
You can delete it from your sdcard once it’s on your computer.
(for a Data Dump, just change the location to /data, and rename the tar file output..)
Edit png/jpeg images
-use 7-zip, winzip, (or stock File Roller on Ubuntu)
-GIMP or Photoshop (work best – but there are many other “tools” out there)
-open the apk (archive) with one of the above mentioned file managers and navigate to the appropriate /res/drawable folder (usually drawable-hdpi, but not only..). And, either copy the files you want to edit directly from there to your desktop or working folder, and make edits and/or drop your replacement files in the appropriate drawable folder in the apk with your file manager. Then move to your system to try it out.
GIMP Notes (it’s what I’m most familiar with, so, Photoshop users use your similar methods):
-Many times the images are in “Indexed” color mode. Go to Image>Mode and change it to RGB mode to avoid editing troubles.
-In GIMP 2.8.0, use the “Export..” feature to save your edited images (in older versions, use “Save as..”), and given quality options, I usually tend to the highest, and all boxes checked.
Decompiling/editing apks
Decompiling apks is necessary to edit .xml files and .9.png files.
See here for more information on the original apktool by brut.all: http://code.google.com/p/android-apktool/ <-- for ICS framework-res.apk, you need to decompile with v1.4.2, and compile with v1.4.3
See here for new version (v1.4.9) of apktool taken over by iBotPeaches: http://forum.xda-developers.com/showthread.php?t=1755243 <-- USE THIS ONE (it works for decompiling AND recompiling framework-res.apk on ICS)
More resources for decompiling/recompiling:
http://forum.xda-developers.com/showthread.php?t=1752201
http://forum.xda-developers.com/showthread.php?t=1466100
Some Tools:
APK Manager/APK Multi-Tool: http://apkmultitool.com/?q=node/5
APK Changer: http://forum.xda-developers.com/showthread.php?t=1189971
Studio Android: http://forum.xda-developers.com/showthread.php?t=1491689
Tickle My Android: http://forum.xda-developers.com/showthread.php?t=1633333
-use apktool alone (see above links for details)
-use an APK editing program (I still mostly use APK Manager v5.0.2 and switch out the apktool files)
-set the proper framework for apktool by placing framework-res.apk, moto-res.apk, blur-res.apk, and SystemUI.apk in the same folder as apktool.jar. Then, open the command prompt or terminal on that folder (need to hold shift and right-click maybe), and type the following, one at a time for each of the four apks listed above, hitting Enter after each entry (note that not all 4 apks are needed for all files, but it doesn’t hurt):
Code:
apktool if framework-res.apk
You should get a “Framework installed to:” message after each, showing you the location to which they were saved. Note on that: In all actuality, you could simply drop a copy of each in the \apktool\framework folder (my path is C:\Users\Owner\apktool\framework\), but rename them as following:
framework-res.apk --> 1.apk
moto-res.apk --> 2.apk
blur-res.apk --> 3.apk
SystemUI.apk --> 127.apk
Re-compiling apks
When compiling system apks, the trick is to save the original signatures (META-INF) folder, the AndroidManifest.xml (unless you are editing that but, that’s a whole different story depending on the apk), and not to compress the resources.arsc file (where all of the /values folders get hidden). Some apk tools do some of the work for you, but here’s few methods (they can be dependent on what was edited):
-after re-compiling your apk, copy your edited and compiled files back over to the original apk to preserve signatures and everything else you did not edit (do this with two 7-zip windows open). For edits to any xml in the /values folders, you need to copy over the resources.arsc also (see next note).
-after editing anything in the values folder, you need to re-insert the resources.arsc without compression. For example, rename your SystemUI.apk to SystemUI.zip, take out the newly compiled resources.arsc with your file manager and then “Add to archive..” that resources.arsc to the SystemUI.zip in “Store” mode (or “No compression”). Then rename the .zip back to .apk, and you should be good to go (you can check the compression directly in the 7-zip window – if the “Size” and “Packed size” values are different, then it’s compressed).
-you can also do it vice-versa, and copy the original META-INF, AndroidManifest.xml, etc., to your edited apk with 7-zip
-if you want to edit the AndroidManifest.xml, depending on the specific apk, be prepared to re-sign nearly all system and framework apps
Edit 9patch (.9.png) images
Do some research on what 9patch images are and how they work, but the most important point is to not disturb the 1-pixel black border around the image, unless you want to redraw it. You must decompile in order to edit 9patch images.
-use GIMP or Photoshop
-use draw9patch included in the android-sdk (fool-proof)
-with GIMP you can select the inner area, leaving the 1-pixel border unselected, and edit colors and such that way
-draw9patch is included in the /tools folder in the Android SDK, it only allows you to edit the 1-pixel border and only draws in #000000 (black) color. It will add one pixel to all sides if you are not careful, so you may need to resize it (down 2 pixels) with GIMP first
Baksmali/smali classes.dex (jar/apk files)
You need to have deodexed files to edit the classes.dex and the smali files within. See here for more info, downloads, and the definition of smali, baksmali, and dalvik: http://code.google.com/p/smali/
-decompiling the apk or jar with apktool will also disassemble (for editing) the smali files
-I used to use this baksmali/smali set with tutor (a good resource): http://forum.xda-developers.com/showthread.php?t=1136625
-or, as I typically do now, just remove the classes.dex from the apk/jar and just baksmali, edit, then smali that into a new-classes.dex. For example, I have a folder called smali_bak on my desktop containing baksmali.jar, smali.jar, and a .txt file with the commands shown below (I’m lazy to type it each time, so I copy and paste) – I put the classes.dex that I wish to edit in that same folder, then open the command prompt on that folder and type the following:
To disassemble (baksmali):
Code:
java -jar baksmali.jar -o classout/ classes.dex
To assemble (smali):
Code:
java -Xmx512M -jar smali.jar classout/ -o new-classes.dex
Then, rename it to classes.dex and drop it in the original apk or jar file with a file manager (no need to worry about compression with the classes.dex, as far as I know)
Deodex and create new odex files
Deodexing is basically the process of converting your .odex files into classes.dex files, and inserting those into the apk/jar - basically. And, re-odexing is the opposite - basically.
See cogeary's excellent guide on deodexing for an excellent guide on deodexing.
-xUltimate v2.4+ works well for deodexing
-see also dsixda's Android Kitchen, and there are many other tools for deodexing..
-See here for manual deodex methods: http://forum.xda-developers.com/showthread.php?t=1208320
-See here for a tool/guide to create a new odex file: http://forum.xda-developers.com/showthread.php?t=1853523
This is the new bootclass path for us (and a bunch of other Motos) to use with ICS (taken from /init.rc, minus the jars that didn't exist in /system/framework):
Code:
/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework-ext.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar:/system/framework/com.motorola.frameworks.core.addon.jar
Methods to move your modded files to your phone
-Create cwm recovery flash zips: Create a zip package (normal compression is fine) containing the proper folder structure (for example: /system/app/ and put your apk in the /app folder if that’s where it belongs). I have two folders on my desktop: /system and /META-INF, which I re-use basically for any flashable zip that I make (except ROM’s, of course). The /system folder has an /app folder or /framework folder usually, depending on what I was last working on (but it can obviously have different paths and many folders if need be), and in the /META-INF/com/google/android folder is an updater-script, and an update-binary file (just grab those from another update.zip mod package around here for now). The updater-script has the installation (or removal) info – meaning the location, permissions, and so on… After you create a zip package with those items and your modded files, then use a program like Sign+ to sign the package (or don’t but then you will need to toggle signature checks in recovery mode before installing). This will create three new files in the /META-INF folder (two CERT files and a MANIFEST).
-Use adb to push the files (don’t forget to set proper permissions!):
-Use Root Explorer (or similar) to move it (don’t forget to set proper permissions!):
NOTE: When experimenting with system files, please have a backup accessible just in case. Or, as I often do, make two zip packages - one with the modded files, and one with the original files to restore if necessary. And, as always, you are responsible for what you do to your device.
FURTHER READING:
Since I am obviously not the first to put something like this together, here are a few other general themeing guides:
Guide by theimpaler747: http://forum.xda-developers.com/showthread.php?t=916814
Guide by Nottach: http://forum.xda-developers.com/showthread.php?t=1186819
Interactive help thread by jeffsanace: http://forum.xda-developers.com/showthread.php?t=1605509
More (possibly out-dated) tips from Stericson: http://forum.xda-developers.com/showthread.php?p=3175518
See also this theming guide - did not read fully through it, but looks promising.
[HOW-TO] ADB/Change Moto Lockscreen to AOSP
BRIEF GUIDE TO USING ADB:
I will run through some example commands using adb - like pulling files from phone, pushing files to phone, deleting, setting permisisons, etc..
If you have adb set up in your environmental variables or .bashrc, then you can simply open a command prompt on the folder you would like to use adb from (right-click, or hold shift and right-click on the folder). Just always keep in mind your paths and folder structures.. Also, see HERE for more on adb.
Make sure you have adb and your device drivers installed and set up properly, then connect your usb..
Code:
#Terminates the adb server process (can help clear up adb issues):
adb kill-server
#Starts adb (or just use any adb command to start):
adb start-server
#List attached devices
adb devices
#Start logcat (Ctrl+C will terminate the current process)
adb logcat
#To pull files to the folder in your command prompt/terminal path
adb pull /system/framework/framework-res.apk
adb pull /system/etc/paranoid/preferences.conf
adb pull /cache/recovery/last_log
#To push files to our phone we need to first push them to the sdcard (also making a new directory on the sdcard called "newfolder")
adb push framework-res.apk /sdcard/
adb push SystemUI.apk /sdcard/
adb shell mkdir /sdcard/newfolder
adb push dexopt-wrapper /sdcard/newfolder
#To start a remote shell in the attached device and get superuser access
adb shell
su
#The following commands need to be run from shell..
#Mount /system re-writable
mount -o rw,remount -t ext3 /dev/block/system /system
#Copy files from sdcard to system
cp /sdcard/framework-res.apk /system/framework
cp /sdcard/SystemUI.apk /system/app
cp /sdcard/newfolder/dexopt-wrapper /system/bin
#Set proper permissions
chmod 0644 /system/framework/framework-res.apk
chmod 0644 /system/app/SystemUI.apk
chmod 0755 /system/bin/dexopt-wrapper
#Remove dalvik-cache and/or other files (note: on some ROMs, dalvik-cache is in /cache/dalvik-cache)
rm /data/dalvik-cache/[email protected]@[email protected]
rmdir /sdcard/newfolder
#Mount /system read-only (not necessary if rebooting right away)
mount -o ro,remount -t ext3 /dev/block/system /system
#Exit shell
exit
exit
#Reboot the device
adb reboot
Change Moto Lockscreen to stock AOSP (MultiwaveView)
(FYI - In GB it was a simple bools.xml edit to switch the Moto lock off.. and there's probably another way to do this - like by bypassing the zz_moto stuff entirely, but..)
If you have a custom locksceen already, then this probably doesn't apply or has already been done...
-decompile framework-res.apk
-open /res/layout/zz_moto_keyguard_unlock_widget.xml with Notepad++, Geany, or similar text editor
-delete all text there, and replace with this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.android.internal.widget.multiwaveview.MultiWaveView android:orientation="horizontal" android:id="@id/unlock_widget" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_alignParentBottom="true" android:targetDescriptions="@array/lockscreen_target_descriptions_with_camera" android:directionDescriptions="@array/lockscreen_direction_descriptions" android:targetDrawables="@array/lockscreen_targets_with_camera" android:handleDrawable="@drawable/ic_lockscreen_handle" android:rightChevronDrawable="@drawable/ic_lockscreen_chevron_right" android:waveDrawable="@drawable/ic_lockscreen_outerring" android:outerRadius="@dimen/multiwaveview_target_placement_radius" android:hitRadius="@dimen/multiwaveview_hit_radius" android:vibrationDuration="20" android:snapMargin="@dimen/multiwaveview_snap_margin" android:feedbackCount="3" android:verticalOffset="0.0dip" android:horizontalOffset="0.0dip"
xmlns:android="http://schemas.android.com/apk/res/android" />
Stopping here and recompiling would give you something like 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"
}
The above just changes the "widget" to the aosp multiwaveview and uses resources/drawables that we already have, which Moto decided to overlay with theirs (adding more bulk to the apks/jars)...
To edit the layout (remove/rearrange things in general), you need to edit keyguard_screentab_unlock.xml in the same folder - it's all there - the clock, date, sound toggle, horz. divider, charge (@id/status1) and alarm icons, unlock widget, music controls, etc... just play around with things..
To add the phone and text msg icons to the unlock widget, we need to edit the android.policy.jar and other xmls in framework-res.
More to come on that...
For Honeycomb style ripple lockscren mod, see here: http://forum.xda-developers.com/showpost.php?p=33854556&postcount=70
Change Clock Color in Status Bar (OUTDATED: FOR GB)
(This is a method I came up with myself)
-First, find a color that you want for your status bar clock.
-Now, find the hex code (combination of 6 letters and numbers) for that color --> see HERE, and/or HERE, and the Android Design guide for colors HERE. You may also use programs like GIMP and Photoshop to preview colors by hex code.
*For reference, 000000 is the absence of color (completely black), on the other end is ffffff (full on, all blinding color - completely white). Also, 33b5e5 is for ICS blue, 99cc00 is for android green (used below in the example).
-Decompile SystemUI.apk
-Open /res/layout/status_bar.xml (with a proper text editor like Notepad++)
-Look for the line that I highlighted in blue (from stock 2.3.6):
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.android.systemui.statusbar.StatusBarView android:orientation="vertical" android:background="@drawable/statusbar_background" android:focusable="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:orientation="horizontal" android:id="@id/icons" android:layout_width="fill_parent" android:layout_height="fill_parent">
<TextView android:textAppearance="@android:style/TextAppearance.StatusBar.Icon" android:textSize="16.0sp" android:textStyle="bold" android:gravity="left|center" android:id="@id/onsText" android:paddingLeft="6.0px" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" android:maxLength="18" />
<com.android.systemui.statusbar.IconMerger android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/notificationIcons" android:paddingLeft="6.0dip" android:layout_width="0.0dip" android:layout_height="fill_parent" android:layout_weight="1.0" android:layout_alignParentLeft="true" />
<LinearLayout android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/statusIcons" android:paddingRight="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_alignParentRight="true" />
[COLOR="Blue"]<com.android.systemui.statusbar.Clock android:textAppearance="@android:style/TextAppearance.StatusBar.Icon" android:gravity="left|center" android:paddingRight="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />[/COLOR]
</LinearLayout>
<LinearLayout android:orientation="horizontal" android:id="@id/ticker" android:paddingLeft="6.0dip" android:animationCache="false" android:layout_width="fill_parent" android:layout_height="fill_parent">
-Add the code android:textColor="#ff33b5e5" to the line that starts with <com.android.systemui.statusbar.Clock as shown highlighted red below (NOTE: Insert your choice of hex code here - the 33b5e5 is just used as an example):
Code:
<com.android.systemui.statusbar.Clock android:textAppearance="@android:style/TextAppearance.StatusBar.Icon" [COLOR="Red"]android:textColor="#ff99cc00"[/COLOR] android:gravity="left|center" android:paddingRight="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />
Again, insert your choice of color in the blanks> android:textColor="#ff------"
-Make sure your spaces are uniform and then save the xml.
-Compile the apk, and use your own method for copying signatures (I use APK Manager, it does it for you)
-Move to your phone by your own means... Enjoy! Please don't blame me if you mess something up!
Related:
There are a lot more mods with partial direction in individual posts throughout this thread.. read on, if interested. I will hopefully compose a location list or something for some of these other mods in the near future.. until then, good luck, and godspeed...
HOW-TO Remove Carrier Name from Status Bar
Bools.xml mods list
Very nice! A while ago I figured out a different way to do it, having to do with editing framework-res/res/values/styles.xml and changing a color code in there. But your way is a bit simpler .
Thanks for the guide! It would be awesome if this thread turned into something like this (see the 2nd and 3rd posts).
cogeary said:
Very nice! A while ago I figured out a different way to do it, having to do with editing framework-res/res/values/styles.xml and changing a color code in there. But your way is a bit simpler .
Click to expand...
Click to collapse
I've learned that there are definitely multiple ways to skin a cat, in terms of themeing android - I went the long way with inverting some apks in Romulus (I did not touch the AndroidManifest), and that forced me to learn how to read and understand this "extensible markup language" a bit better - and to correct my text color issues, I learned that you can just add the text colors if you find the right xml...
cogeary said:
Thanks for the guide! It would be awesome if this thread turned into something like this (see the 2nd and 3rd posts).
Click to expand...
Click to collapse
Oh boy, I should've reserved more posts for something like that! I would love to put something comprehensive together like Nottach did, but with ICS coming, I know a few things will change - so, I figure I'm better off waiting and learning that system first..
Not sure why but I couldnt find those exact lines you have in the exampme box. And whats with the crazy symbols? Sorry man...still a lil new as you know at messing with this type of stuff.
sorry the pics are so ****ty. Lo-light, laptops and cameras/phones dont mix well lol. Thanks in advance man.
Sent From MY DROID That DOES! Not YOUR APPLE That DIDN'T!
^
I think you just unzipped, did not decompile SystemUI.apk
DX2Trip said:
Not sure why but I couldnt find those exact lines you have in the exampme box. And whats with the crazy symbols? Sorry man...still a lil new as you know at messing with this type of stuff.
sorry the pics are so ****ty. Lo-light, laptops and cameras/phones dont mix well lol. Thanks in advance man.
Sent From MY DROID That DOES! Not YOUR APPLE That DIDN'T!
Click to expand...
Click to collapse
Did u decompile the apk ?? That's y u probably got the wired symbols
Sent from my MB865 using xda premium
You are going to need to decompile the apk to be able to read those xmls...
I use APK Manager 5.0.2 for Windows - see updated OP.
Then read up on some other threads about the process, also check the carrier name removal post I linked in OP#2... but yea, there is good literature on de/recompiling out there..
P.S. - for me, all of my codes in the op's are botched and have smiley faces on the xda app - I did use code tags..!? Reference them on a computer for easier reading...
Sent from my phone's mind
EDIT: edited.
I updated the heck out of this thread to give some guidance on using APK Manager for decompiling and compiling (at least they way I do it)... hope it helps a few people.
Man...seem to always run into an error. Any thoughts? Don't know why it shows up as status bar right before installing. It does say SystemUI.apk in the folder though...
Sent From My DROID That DOES Not My APPLE That DIDN'T.
Are you getting errors compiling the apk? How are you trying to install the apk on your phone? It looks like some sort of SystemUI is installed from your pic (since you still have a status bar showing)... But, the Status Bar process is the SystemUI.apk. So, I'm a little confused..
I need a bit more info on how you're doing things to try and help you better..
Are you getting errors compiling the apk? How are you trying to install the apk on your phone? It looks like some sort of SystemUI is installed from your pic (since you still have a status bar showing)... But, the Status Bar process is the SystemUI.apk. So, I'm a little confused..
I need a bit more info on how you're doing things to try and help you better..
Click to expand...
Click to collapse
My bad lol, should have explained better. No errors decompiling, editing, compiling or signing. Just trying to install right from the root folder I placed it on in my SD. Don't know if its because it wont install over the OG SystemUI.akp or what. Yeah the OG was still intact while I tried installing the edited one. In fact I tried just moving the edited one into my system apps n it kept forceclosing to the point where I had to reboot and when it started back up I had no status bar at all! lol no worries though, had a nandroid and have still been trying to figure it out...maybe signatures have somthing to do with it. Idk...
heres what it looks like on the SD card. But right when I press it, it turns into status bar...odd.
Sent From My DROID That DOES Not My APPLE That DIDN'T.
I followed the instructions to the letter worked great ur awesome. Got my status bar clock red yea buddy lol
Sent from my MB865 using xda premium
DX2Trip said:
My bad lol, should have explained better. No errors decompiling, editing, compiling or signing. Just trying to install right from the root folder I placed it on in my SD. Don't know if its because it wont install over the OG SystemUI.akp or what. Yeah the OG was still intact while I tried installing the edited one. In fact I tried just moving the edited one into my system apps n it kept forceclosing to the point where I had to reboot and when it started back up I had no status bar at all! lol no worries though, had a nandroid and have still been trying to figure it out...maybe signatures have somthing to do with it. Idk...
Sent From My DROID That DOES Not My APPLE That DIDN'T.
Click to expand...
Click to collapse
I used root explore to move my SystemUI.apk into system/app folder with permission set at rw-r-r override and replace old 1 reboot and should be fine
Sent from my MB865 using xda premium
DX2Trip said:
My bad lol, should have explained better. No errors decompiling, editing, compiling or signing. Just trying to install right from the root folder I placed it on in my SD. Don't know if its because it wont install over the OG SystemUI.akp or what. Yeah the OG was still intact while I tried installing the edited one. In fact I tried just moving the edited one into my system apps n it kept forceclosing to the point where I had to reboot and when it started back up I had no status bar at all! lol no worries though, had a nandroid and have still been trying to figure it out...maybe signatures have somthing to do with it. Idk...
Sent From My DROID That DOES Not My APPLE That DIDN'T.
Click to expand...
Click to collapse
Thank goodness for cwm on boot and fresh backups ..
Well, I can tell you right off the bat that your method of installation is giving you problems. Also, don't sign the SystemUI.apk, you want to retain the original signature.
It is possible to move it on your phone with root explorer, but I know some people are against this method.. but, here it goes anyway..
-First go and check the permissions of (and possibly make a copy of) the file that you want to replace. Go to the file location, mount R/W, and long-press the file and choose permissions - and remember them, or write it down. (Note: All apps and framework in /system are rw-r--r--)
- Next, copy the new file that you want to put on your phone from your sdcard.
- IMPORTANT: Paste it in another system folder besides the final destination and SET the proper PERMISSIONS and rename if necessary to match the file you are replacing (need to mount R/W first). For example, paste your edited SystemUI.apk in the /system folder (NOT directly in the app folder), and change the perms there..
- IMPORTANT: Long-press on the file you are moving and select "MOVE".
- Then paste it in the final destination folder (i.e. /system/app), and select ok to overwrite the existing.
- Don't try to do anything else except reboot. And, it would be nice to wipe dalvik and cache partition while you are rebooting, if you have the chance.
Please, if anyone tries this method, be cautious, use CWM on Boot, and have a fresh backup just in case.. also, I assume no responsibility for your actions.. I have done this multiple times with many different file types and locations..
Sent from my phone's mind
chrisn91 said:
I followed the instructions to the letter worked great ur awesome. Got my status bar clock red yea buddy lol
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Very cool! Glad to hear it worked for you! You got a screenshot of the red?
Sent from my phone's mind
Yea..
Im reading on how to center my lockscreen clock and changing the color red as well
Sent from my MB865 using xda premium
chrisn91 said:
Yea..
Im reading on how to center my lockscreen clock and changing the color red as well
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nice. You make all the edits yourself or is that a custom rom? Either way, lookin good, man.. keep it up!
And, I was also just about to dig into a few things, lockscreen clock color happens to be one of them.. but, I got the old moto lockscreen (which has a centered clock), so I'm thinking those xmls might be in a different place than the new moto lockscreen stuff... we'll see..
Sent from my phone's mind
alteredlikeness said:
Nice. You make all the edits yourself or is that a custom rom? Either way, lookin good, man.. keep it up!
And, I was also just about to dig into a few things, lockscreen clock color happens to be one of them.. but, I got the old moto lockscreen (which has a centered clock), so I'm thinking those xmls might be in a different place than the new moto lockscreen stuff... we'll see..
Sent from my phone's mind
Click to expand...
Click to collapse
Its a little of both. I.did some theming to sv6 with some pngs from other roms although I've learned alot here creating a img from scratch is a hard thing for me to grasp lol. I've tried many times to change the status bar clock but it won't work I would get systemui force closures or no change at all but thanks to ur steps and how to guide I got it
Sent from my MB865 using xda premium
Well I couldn't figure it out for the old native AOSP jog tab lockscreen, but I managed to change the clock and date color on the new Moto sliding door lockscreen... also changed the font style of the clock to DroidSans (which is actually Ubuntu font on Romulus, the default system font - it was Chulho_Neue)..
But, as you can see, I didn't get the "charging" text color. Also didn't look at moving the position yet..
Oh, yea... it's in framework-res.apk/layout/zz_moto_sd_keyguard_screen_tab_unlock.xml - look for the lines with the ids "timeDisplay", "am_pm", and "date"...
But the zz_moto_keyguard_screen_unlock_portrait.xml threw me off, and may have something more to do with this...
I'll try to look into this and post something better 2moro..
Sent from my phone's mind
EDIT: I think I just found it for the native jog tab lock... in a very obvious place: keyguard_screen_tab_unlock.xml (without the zz_moto_sd part, obviously) - this may help to center the zz_moto_sildingdoor lockscreen text as well... get some ideas or lines of code from it, and copy it over to the zz_moto keyguard xml..
I have installed a ROM.When i go to settings,it shows at the end 'Custom build by Rocky" This really sucks.
I tried to change it by build.prop but i couldn't do that as 'Custom build by Rocky';this text was even not present there. I searched a lot for this.Now can anyone tell me how to change this..I am sure this specific text is not present in build.prop,is there any other file to do that?
I've had my fair share in rom development a year or so ago. And I can tell you that the name there is just a way of marking the rom.
But if you're really bothered by it, I can tell you how to find the string, edit it or completely remove it. To find the string - Custom build by Rocky, you can't just change it in build.prop. For this, you must go into /system/app and then copy Settings.apk file to your desktop. From there, go ahead and decompile Settings.apk with a preferred decompiler. When decompiled, head into the project, and navigate to the following folder - res/values and open strings.xml with a text editor. Search for Custom build by Rocky in the text file, once found. You may change it to whatever you wish. But if you want to remove it, you have to remember the ID of the string. For example, in - example text - which is the string, the text to the right. The ID is text the ID is found in the left hand side, it's after the word name . So remember that, now go back to the res directory and scroll down to the xml folder, open it and look for about.xml. In there search for text which is the ID. And remove the line completely. Also make sure to remove the header line too. As this will stop the layout from having an invisible section.
Now compile the Settings.apk and push it to your device - adb push desktop/path/to/Settings.apk /system/app or just copy Settings.apk to device and do it from there.
I do not encourage you to do this. And you can do this at your own risk. I will not take any responsibility if you mess up your phone.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
I've had my fair share in rom development a year or so ago. And I can tell you that the name there is just a way of marking the rom.
But if you're really bothered by it, I can tell you how to find the string, edit it or completely remove it. To find the string - Custom build by Rocky, you can't just change it in build.prop. For this, you must go into /system/app and then copy Settings.apk file to your desktop. From there, go ahead and decompile Settings.apk with a preferred decompiler. When decompiled, head into the project, and navigate to the following folder - res/values and open strings.xml with a text editor. Search for Custom build by Rocky in the text file, once found. You may change it to whatever you wish. But if you want to remove it, you have to remember the ID of the string. For example, in - example text - which is the string, the text to the right. The ID is text the ID is found in the left hand side, it's after the word name . So remember that, now go back to the res directory and scroll down to the xml folder, open it and look for about.xml. In there search for text which is the ID. And remove the line completely. Also make sure to remove the header line too. As this will stop the layout from having an invisible section.
Now compile the Settings.apk and push it to your device - adb push desktop/path/to/Settings.apk /system/app or just copy Settings.apk to device and do it from there.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can u suggest me some apk decompilers?
Try "APKTool" just search for it on the search part of this site, it should come up.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Try "APKTool" just search for it on the search part of this site, it should come up.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey bro! This method worked..
But,now i am in a more big problem.
By the way that test was 'Custom build by Jatin' not Rocky.
The new settings.apk which i recompiled after editing that line successfully was not directly installing on my phone.
So,i replaced that new apk with the settings.apk in my ROM which contains 'Custom Build by Jatin' text..
Now,when i installed that ROM again,everthing went right ..but when i cheked the apps ...My settings option was no more..It was not installed during the ROM installation..I manually also tried to install that but nothing was achieved!
Now ,how to fix this? Hey bro,I am also attaching that settings.apk ,see if you can edit that line yourself and then again attach here for my use.Its line 176 in res/strings ,,just replace that line from 'Custom Build' only...
Please help me bro.
This happens sometimes. Its best to push the .apk to your device rather than moving it
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
This happens sometimes. Its best to push the .apk to your device rather than moving it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Now,the settings.apk is crashing..Bro,there is somewhere error between the app..I have attached that apk in this forum before..Can't u yourself rename that line and attach here..Please bro
Problem fixed
The unsigned settings.apk worked now....
Sorry, I just saw your post. Oh and I'm glad it works now. With system apps, you mustn't sign them. They don't work properly.
Sent from my Nexus 5 using Tapatalk