Here is a quick guide on how to remove the bloatet Samsung QuickSettings from the notification area.
This screenshots show what this guide should help you achieve:
Before:
{
"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"
}
(I'm using enox reVenge. So my Notification QuickSettings look a little different than the stock version)
After:
So here is how I did it:
Prerequirements:
- a rooted ROM
- apktool.jar, helper-script for your OS and aapt (get them from code.google.com/p/android-apktool/ and throw them all into one folder)
Decompile:
Get /system/app/SystemUI.apk and /system/framework/framework-res.apk from your phone
Code:
adb pull /system/app/SystemUI.apk
adb pull /system/framework/framework-res.apk
Then install framework and decompile SystemUI.apk
Code:
apktool if framework-res.apk
apktool d SystemUi.apk
Additionally unzip the SystemUI.apk and get the META-INF folder and the AndroidManifest.xml file. Save them somewhere for later.
Modify (aka: the interesting part):
In SystemUI/res/values/dimens.xml change all values starting with "quick_setting_button_" to "0.0dip"
For me this was changing
Code:
<dimen name="quick_setting_button_height">80.0dip</dimen>
<dimen name="quick_setting_button_image_height">40.0dip</dimen>
<dimen name="quick_setting_button_text_height">30.0dip</dimen>
<dimen name="quick_setting_button_text_size">12.0dip</dimen>
<dimen name="quick_setting_button_status_height">8.0dip</dimen>
<dimen name="quick_setting_button_status_padding">2.0dip</dimen>
<dimen name="quick_setting_button_margin_top">2.0dip</dimen>
to
Code:
<dimen name="quick_setting_button_height">0.0dip</dimen>
<dimen name="quick_setting_button_image_height">0.0dip</dimen>
<dimen name="quick_setting_button_text_height">0.0dip</dimen>
<dimen name="quick_setting_button_text_size">0.0dip</dimen>
<dimen name="quick_setting_button_status_height">0.0dip</dimen>
<dimen name="quick_setting_button_status_padding">0.0dip</dimen>
<dimen name="quick_setting_button_margin_top">0.0dip</dimen>
Recompile:
Code:
apktool b SystemUI
- go to the newly created SystemUI/build/apk/
- paste the META-INF folder and AndroidManifest.xml file which you unziped earlier here (overwriting the existing AndroidManifest.xml)
- do another:
Code:
apktool b SystemUI
(will be faster than the first run)
Install:
- get your modded SystemUI.apk in SystemUI/dist/
- move it to your phone (to /system/app/) (this requires R/W access to /system. One way to get this is starting CWM)
- start CWM and mount /system
Code:
adb push SystemUI.apk /system/app/
- change the permissions to 644
Code:
adb shell
chmod 644 /system/app/SystemUI.apk
reboot
DONE
Great for people who doesn't like settings on their phone?
I was looking for this exact thing since for some reason, my Sprint S3 does not have the Notification Panel option available under display to customize this area.
However, I followed these steps and did not get the results you did. For one, I did not get a META-INF folder so that may have been part of the issue. Loading my new SystemUI.apk resulted in the notification bar disappearing completely and my Holo launcher being severly confused. I had to put my original apk back.
Perhaps the launcher is what caused the problem...
Mike
*** UPDATE ***
Had a friend of mine do this and he extracted the META-INF folder from the apk and recompiled. This time it the UI looked normal when the phone booted, but the bar was the same with all the quick setting still visible.
@mtbowen:
You have to get the META-INF folder and the AndroidManifest.xml from the original/unmodified SystemUI.apk .
Just unzip the apk with WinRAR or whatever you use.
I updated the HowTo to make this clearer.
META-INF contains the APKs certificate. Since you didn't include it your APK wasn't signed and thus didn't work.
Can they be modified instead of completely erased? I do use some of them, but others just take up space and make the whole thing scroll every time I open the notification drawer
Yes. Should be possible.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=2191593
it works but the brightness slider doesn't seem to go up, the area of quick settings stays blank
have you looked at making an Xposed module for this?
Is this truly of help?
Correct me if I'm mistaken but this appears to be only a cosmetic fix. I have not done this as yet because the one user seems to have reported that this does not actually recover the space used by the buttons. This implies that it only makes them disappear. If this is the case this solves nothing; you have gotten rid of no bloat, you've just hidden it. Any system resources are still being used, other than the little bit (the tiny little bit) involved in displaying the graphics.
Has anyone a real solution for this?
I followed the instructions of this guide on a Canadian version of the Samsung S III mini. Unfortunately it did not remove the drawer icons, i.e. it appears that the solution will only work depending on some other unknown conditions. I was however successful when using instead the reGXM Ex xposed module as described in thread 2698143, even though this does not seem to have been the objectives of the original developer.
Related
This is posted in the N1 forum, before xda got the new sections, but I suppose it works for any phone. I personally have a Droid, and can only vouch that it works on Droid and N1.
I haven't updated my metamorph since stericson looks like he's abandoned it, and since people started commenting that it doesn't work anymore. I have two/three options here. xml version (the 1.1 zip), .thm version (first zip), and the .png for you to pack yourself. The notification .png is in the zip so you can go ahead and extract that, and re-pack it yourself too if you want that.
01-05-10 Update: Updated control file to .xml to be compatible with newest Metamorph. v1.1 is the new version, but the older ones including .thm control files are still there for people holding over.
20-04-10 Update: Added a notification icon. The first zip is still just the launcher icon, and the second includes both the launcher, and notification icons.
Got tired of the straight up blue text so I made it look more like the splash screen text, and sort of what the 1.5 looked like. I have two options, grab the .png and copy over the icon within the Talk.apk and push it back to your /system/app folder, or metamorph.
Let me know what you think. If this is a grey area because it's a Google trademark just delete the post, or let me know and I'll remove it.
Directions:
Download the zip and use MetaMorph like normal to apply a theme.
or
Make a backup of your original Talk.apk
Pull your Talk.apk from /system/app or just copy it to your sdcard.
Open the archive (don't need to extract it) and drag the .png into it, and overwrite the old one. Update the archive if it prompts you.
*If something stops working, just replace it with your backup, or reinstall the gapps. I'm not responsible for anything that happens to your phone.*
#As root, copy apk and modify it from your computer
#as root make /system read/write
#copy the updated Talk.apk or push it from adb
#remount as read only
#sync filesystem
#exit root, and terminal and the new icon will appear
#restarting launcher or rebooting will fix the icon text in launcher
su
cp /system/app/Talk.apk /sdcard
exit
exit
#follow directions to modify the archive and place it back on sdcard or push it directly
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
cp /sdcard/Talk.apk /system/app (or from the folder Talk.apk is in) adb push Talk.apk /system/app
mount -o ro,remount -t yaffs2 /dev/mtdblock3 /system
sync
exit
exit
{
"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"
}
Bump.
Tested and works with CM 7.0 (2.3).
cute work, man
While I was searching for how to change the clock & notification colour in statusbar
there i got so many guide with lot of way....
I tried them tooo...
But soory to say that very few of them works for mee...actualy
those guide support few devices not for all...
Then one of my friend(Abhishek Kumar Singh) gave me a guide which is a perfect one..
but there also few changes to be done......as the guide is totally messed..
so Here I am going to make a guide for all those who want to change there clock & notification colour.
Requirements:-
1)ColorChange.jarv3.1 [Download]
2)Rootes Android Phone
3)Sdk Installed
4)Little knowedge on Messing with Cmd
Processsss/Working:-
1)Plug in your phone( make sure that usb debugging is ticked on)(Dont't mount the sdcard)
2) open command prompt from Pc..(To open=> click start->run->type cmd->ok)
3) Navigate to the android sdk platform tools folder..
4) Type this commands:
adb remount
adb pull /system/framework/services.jar services.jar
adb pull /system/framework/framework-res.apk framework-res.apk
5)Now extract the colorChangev3.7z & paste the extracted file colorChangev3.jar in platform tools folder
6)Now make a folder called 'framework' inside Platform tools folder & move the services.jar into that folder
7)Create a zip file of the framework folder and name it theme.zip
(steps 7 & 8 shuld be done correctly or u will get errors)
8)Type this commands....
java -Xmx512M -jar colorChangev3.jar theme.zip clock=FFb4ff00 date=FFffffff
(definetly 'FFb4ff00' denotes the clock colour & 'ffffffff' denotes the date colour)
9) When its done it will leave a theme-new.zip in platform tools folder,take the new service.jar file out
& put that in platform tools folder.
10) Its almost done....Now you can take the new services.jar make flashable zip & flash...If you don't know how to make flashable zip then do this.
11) Type this command in already opened cmd
Commands:
adb remount
adb push services.jar /system/framework/
adb push framework-res.apk /system/framework/framework-res.apk
adb shell reboot
That's all you are done now.......:good:
One think you should note that you shouldn't get any error while following this whole process otherwise it will not wrk....
Basically this above process doesn't harm your mobile...But if anything wrong happend with you..Then you can't blame me..
Credits
milrtime83 for his guide
Please Dont forget to Hit The Thanks Button.......... :good::good::good:
Reserve
{
"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"
}
Resreve
Hi all XDA members, today I am going to show you how to edit xml files in your framework-res.apk so you can edit auto - rotation on lockscreen or CRT - Animation. This does not apply to the Arc only, most Android phone's framework can be edited this way except maybe Samsung or HTC phones which have an extra resource file. This guide contains screenshots and is meant to be noob friendly so everything is self explanatory, you don't need a rocket scientist to explain everything.
What you need:
Framework-res.apk you want to edit
Apktool
Notepad++ is recommended for editing XMLs.
7-zip
So let's get started:
1. If you want to edit the framework file, naturally you should have extracted it from your phone. If you have not done so, the framework-res.apk can be found in system/framework/framework-res.apk(requires root access)
{
"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"
}
2. Place the file into apktool directory
4. Press shift and right click the directory(don't select any file, just press shift right click in the empty space of your apktool directory, you should see "Open command window here")
5. You should see a command window like this:
6. Type this command: apktool if framework-res.apk. You should get a response like this:
7. Now type this command:apktool d framework-res.apk. This will decompile your framework-res.apk so you can access the xml files.
8. Go back to your apktool file. You should see a new folder called framework-res(Yes, please take a good look. I circled it for your sake.)
9. Open the folder. go to res/values/bools.xml
10. Right click on file, select edit with Notepad++
11. Now open in Notepad++, you can edit and choose the functions you want to add just by editing the boolean with "true" or "false"
That's it, you are now ready to choose if you want auto rotation lockscreen or enable CRT animation.
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
At the request of some users, I have updated the thread with the compiling and signing steps as well, so please continue reading.
12. Firstly we need some files to sign the apks, so go to your original framework-res.apk, right click -> 7 zip -> Open Archive
13. Extract the folder "META-INF" and the file "AndroidManifest.xml" from the framework-res.apk
13a. Alternatively, you can find the files in <your framework-res folder> -> Original // No "<>" symbols, please see attached screenshot
14. Before we compile the framework, please rename the folder to avoid any conflicts with the existing framework-res.apk
15. Type this command: apktool b <your framework-res folder> and press Enter // No "<>" symbols, please see attached screenshot
16. You should get a response like this:
17. Go to <your framework-res folder> -> dist -> framework-res.apk // No "<>" symbols, please see attached screenshot
WARNING! DO NOT PUSH THIS FILE INTO YOUR PHONE YET. IT HAS NOT BEEN SIGNED AND WILL CAUSE A BOOTLOOP IF YOU PUSH IT TO /SYSTEM. PLEASE CHECK THAT THESE FEW STEPS HAVE BEEN COMPLETED BEFORE PUSHING IT TO /SYSTEM
18. Right click the file, go to 7-zip -> Open Archive
19. Select the files you extracted or received from step 10 or 10a
20. Drag and drop into 7-zip. You will get a warning message. Press "Yes".
21. You should have both files copied into the apk. You have signed the framework-res.apk and the file is OK for use.
22. Push the framework-res.apk into /system/framework, set RW-R--R-- permissions and reboot.
That's it. Your phone should be functioning normally and the changes you did internally should take effect.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
Also, please PM me or comment if you have questions.
If the question has been asked before, please read the previous posts if there are any.
Repeat questions will not be entertained.
popthosegaskets said:
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
Click to expand...
Click to collapse
Would be better keeping it all in one thread.
Sent from Myushi
XperienceD said:
Would be better keeping it all in one thread.
Sent from Myushi
Click to expand...
Click to collapse
Ok, thanks for the feedback
僕のLT18iから送られてきた
did you ever manage to get round to posting a recompiling guide??
Inside 4ndroid said:
did you ever manage to get round to posting a recompiling guide??
Click to expand...
Click to collapse
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
popthosegaskets said:
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Inside 4ndroid said:
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Click to expand...
Click to collapse
Ok... I shall redo this guide.
僕のLT18iから送られてきた
Thread content updated per user request.
This tutorial is for people building roms based on CyanogenMod only !
This tutorial will explain how to use a custom CyanogenMod apk theme as the default when building roms
Things you will need
1. Java JDK and Java JRE installed
2. ApkTool - Download
3. Notepad++ - Download
4. Theme apk file
5. Your custom rom
Step 1
Download and extract apktool into a folder on the root of you drive, call the folder apk
Once extracted you you have three files 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"
}
Step 2
If you have already packaged your rom use something such as WinRAR to extract it to a folder.
Once extracted it should look similar to this
Step 3
In your rom folder navigate to system/framework and look for the framework-res.apk file
It should look like this
Step 4
Copy the framework file to your apktool folder
Your apk tool folder should now look like thisView attachment 2484553
Step 5
Now copy your theme into the same folder
The folder should now look like thisView attachment 2484556
Step 6
Run command prompt and enter the following commands
Code:
cd C:\apk
Code:
apktool if framework-res.apk
Code:
apktool d <whatever your theme apk is called>.apk
Your CMD windows should now look like this
Step 6
Go back to your apktool folder and now you should have a folder called <your theme name>.apk
It will look like this View attachment 2484571
Step 7
Go inside that folder and open AndroidManifest.xml with Notepad++
Step 8
Once you open this file you need to look for two strings, they should look similar to these ones
Step 9
Once you have found these strings minimize the Notepad++ window and navigate back to your rom folder
Now navigate to system and open build.prop with Notepad++ and add these two lines
Code:
persist.sys.themeId=~~~~~~
persist.sys.themePackageName=+++++++++
Replace "~~~~~" with theme id from AndriodManifest.xml
Replace "+++++" with package name from AndroidManifest.xml
Mine would look like this
Now save build.prop
Step 10
Go to your rom folder and navigate to system/app and copy your theme apk inside of this folder
Now zip your rom back up and flash it
When your rom boots you should now see you custom theme
Note
If you cant get apktool to work and it keeps saying something along the lines of "java is not an exacutable command"
Make sure you have installed the Java SDK and Java JRE and navigate to C:\Program Files (x86)\java
and you should see a folder called "jdk1.7.0_45" or "jdk" with different numbers after it
Now go to control panel and on the right hand side click "Advanced System Settings"
Then click "environment variables"
Under "system variables" create a new variable and call it JAVA_HOME
In variable value put the path of your java sdk folder so it would be
C:\Program Files (x86)\Java\jdk<what ever numbers are here on your pc>
Or 32 bit users
C:\Program Files\Java\jdk<what ever numbers are here on your pc>
Now before you save the environment variable put the path in speech marks like this
Now save and reboot
And for CM12.1 its possible? Or CM11?? I try but not work :/
{
"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"
}
APKTOOL FOR WINDOWS
First and foremost thanks to @iBotPeaches for his dedication to Apktool!
Because I can double-click more accurately than I can type, I made this up to avoid having to use command line and speed up modding the couple of apks that I try to keep up on. Maybe it'll help a few others speed up their process too.
Now, this is a Windows based GUI for Apktool. No command line needed. That said, you should be very familiar with already using Apktool via command line so you know the process that it follows and the corrective measures needed should errors pop up. You need to have the exact same setup as Apktool (Java in your environment path and current Java version AND relevant frameworks installed via apktool!! ). All that this does is provide a simple Windows style menu for the process. You can very easily update apktool.jar as @iBotPeaches updates it. Also, if you would like to add any switch to the decompile or compile command other than the typical (which is what I used) you can just modify the corresponding .bat file located in SupportFiles that APKTool For WIN calls on.
See the attached screenshots in the following post for the easy to follow layout and it's capabilities. It will install frameworks/etc, decompile, compile (with or without original manifest and meta-inf), sign (with testkey or your personal one), and display an apktool log.
As this directly uses apktool.jar, it will have the same quirks/issues such as this current one:
10/18/2016 - for apktool v2.2.1 regarding v2 signed apps - LINK
V4 - As I was posting this, I noticed there was an update to apktool.jar (v2.2.1) which I updated the file to reflect. I modded several apps with the earlier version but only attempted two apps with the updated one (didn't see any issue with either app but I'm still on MM). I haven't looked more in depth at this V2 signed apps issue yet to see if I can modify the signing.bat to account for it (it's 230am). I will update it if there is.
V5 - (1) Updated apktool.jar to 2.2.2 if you haven't already yourself and (2) added java version info in your log file on Decompile routine to help identify a beginners issue on determining whether or not you have java installed in your path
Copy apks to the "APKs_To Decompile" folder.
Copy your framework-res, twframework-res, systemUI as needed to the folder "Frameworks".
Install frameworks.
Running the APKTool For WIN.exe select Install Frameworks
Decompile.
Select Decompile .apk
Choose your apk.
Decompiled app will be in the Decompiled folder.
Compile.
Select Compile
Choose your app to compile.
(One backup will be automatically created if there is an existing one to be safe in the decompiled app's folder)
Choose to copy the original manifest and meta-inf if desired
Compiled apk will be in the Compiled folder
Sign.
Select Sign APK
Choose the apk to sign.
Choose to sign with the testkey or with your personal key (help file is included in the zip for initial setup for using your own key)
Signed apk will be in the Signed folder
APKTool Log
If an Error message is displayed after decompiling or compiling you can check the log.
It's also beneficial to clear the log sometimes.
reserved for future use, faqs, issues
hmmm......after being away for a while i'm checking back to see if anyone had issues with trying to use this....and.......
not a single issue/question/comment with nearly 100 downloads. you guys are GOOD!!! (unless y'all think it's pointless and are being too kind to comment )
in the next few days, i'll use it a bit more in depth with the updated source and see if anything needs tweaking
Great tool !! I like it , this is solve my problems.
thank you so much , please keep it up.
Small update - V5
1. Updated to apktool 2.2.2 in case you haven't already done so yourself.
2. Added your java version info to the log generated when you run a Decompile routine to help beginners identify whether or not java is in the required path