Database Info

How to decrease the number of home screens of jellybean stock launcher?

Hey guys, I need some assistance of those who know please. I decompiled the launcher2.apk of eos Xoom ROM and made changes to
res/layout-port/launcher.xml
And to
res/layout-land/launcher.xml
By deleting some lines related to launcher screens. By default they come 5, I made them 3.
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
<include android:id="@id/cell4" layout="@layout/workspace_screen" />
<include android:id="@id/cell5" layout="@layout/workspace_screen" />
I also made launcher:defaultScreen="1" to set the default screen to be the middle one.
I compiled the apk and replaced the original one with the same permission , however' the launcher remains with 5 screens...
Can anyone please point out how to get around this?
The way I compiled is using apktool manager and deleted resources.arcs from the keep folder !!! Does this need to be signed even if it is a system apk?
As soon as this works, I thought to provide a mod for xoomers...
Sent from my MZ601 using Tapatalk 2

Guys... no one?!!
Come on.... someone must have an answer here.
I decompiled the modded launcher and found the changes I made are gone and back to 5 screens !!
Sent from my MZ601 using Tapatalk 2

Have you tried adding workspaces? I for one would like 7 instead of 5.
Off topic: are there any launchers that work like compiz fusion under ubuntu?
Sent from my SGH-I717R using xda premium

Eun-Hjzjined said:
Have you tried adding workspaces? I for one would like 7 instead of 5.
Off topic: are there any launchers that work like compiz fusion under ubuntu?
Sent from my SGH-I717R using xda premium
Click to expand...
Click to collapse
The problem is that I am trying to make the changes I do persistent . However, whenever I compile the apk, it goes back to 5 screens. If I can manage removing screens, I will be able to add more. All I need is a little help of guideness if someone knows, plz step in...
Sent from my MZ601 using Tapatalk 2

wesamothman said:
The problem is that I am trying to make the changes I do persistent . However, whenever I compile the apk, it goes back to 5 screens. If I can manage removing screens, I will be able to add more. All I need is a little help of guideness if someone knows, plz step in...
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
ok you have it right, however i can 99.99% guarantee you that your problem is with apkmanager
becasue there is no why that once you make the changes that the changes will "revert" back to that what is was previously
use good old fashion cmd or terminal ( if on linux) or even simpler build it from the source,
however if you insist on using apktool use these ( which are moddified for ICS/JB) https://dl.dropbox.com/u/25886627/apktoo_8.15.12.zip
only follow these steps to the "T"
put the zip anywhere, open cmd ( command promt)
and CD to C:\were\extracted\zip\is\
and then take the framework-res.apk and the Launcher2.apk
and place both in the same folder you extraacted zip to
now in cmd type
apktool if framework-res.apk
followed by
apktool d Launcher2.apk
now this will decompile the apk to :\were\extracted\zip\is\Launcher2\
make changes
back in cmd type
apktool b Launcher2
now navigate to :\were\extracted\zip\is\Launcher2\build\apk\
copy the original Launcher2.apk from :\were\extracted\zip\is\ to :\were\extracted\zip\is\Launcher2\build\apk\
OPEN not extract the apk with 7zip ( or any archive manager) and now click and highlight from the :\were\extracted\zip\is\Launcher2\build\apk\ the res folder the classes.dex file and the resouces.arsc and drag them into the root of the Launcher2.apk that is open in 7zip
now that is the ready file to be sent to device
about signing...
system apps you dont sign becasue you dont have the authers signing tools, so if you try to simple sideload it an error of mismatching keys will prevent the app from installing
becasue we are flashing it ( or adb push) signing is not needed.
now i have not looked at the launcher as far as the amoutn of home screens ( done some customization for my own use on the n7) but what you have said you did should without a doubt work

runandhide05 said:
ok you have it right, however i can 99.99% guarantee you that your problem is with apkmanager
becasue there is no why that once you make the changes that the changes will "revert" back to that what is was previously
use good old fashion cmd or terminal ( if on linux) or even simpler build it from the source,
however if you insist on using apktool use these ( which are moddified for ICS/JB) https://dl.dropbox.com/u/25886627/apktoo_8.15.12.zip
only follow these steps to the "T"
put the zip anywhere, open cmd ( command promt)
and CD to C:\were\extracted\zip\is\
and then take the framework-res.apk and the Launcher2.apk
and place both in the same folder you extraacted zip to
now in cmd type
apktool if framework-res.apk
followed by
apktool d Launcher2.apk
now this will decompile the apk to :\were\extracted\zip\is\Launcher2\
make changes
back in cmd type
apktool b Launcher2
now navigate to :\were\extracted\zip\is\Launcher2\build\apk\
copy the original Launcher2.apk from :\were\extracted\zip\is\ to :\were\extracted\zip\is\Launcher2\build\apk\
OPEN not extract the apk with 7zip ( or any archive manager) and now click and highlight from the :\were\extracted\zip\is\Launcher2\build\apk\ the res folder the classes.dex file and the resouces.arsc and drag them into the root of the Launcher2.apk that is open in 7zip
now that is the ready file to be sent to device
about signing...
system apps you dont sign becasue you dont have the authers signing tools, so if you try to simple sideload it an error of mismatching keys will prevent the app from installing
becasue we are flashing it ( or adb push) signing is not needed.
now i have not looked at the launcher as far as the amoutn of home screens ( done some customization for my own use on the n7) but what you have said you did should without a doubt work
Click to expand...
Click to collapse
Thx a million times. I will do as said
Sent from my MZ601 using Tapatalk 2

Hi runandhide05. First allow me to send you a bigggggg thank you for your apktool. It really was apktool problem.
I did as you suggested, still, didn't work from the first time (modified to 3 screens) although the changes were persistent this time. so, in addition to the above files, i had to modify the following as well:
workspace.xml in layout-sw720dp
and public.xml in res/values in which I had to delete
<public type="id" name="cell4" id="hex val xxxxx" />
<public type="id" name="cell5" id="hex val xxxxx" />
So, now I tested with these changes and I got 3 screens
I will try to do 1 screen, and 7 screens.
Thanks again. you are truly appreciated.
EDIT: 1 Screen is successful too. I will try 7 soon.
EDIT: 7 Screens is successful too
I will try to write a flashable zips for them and post them as mods ...

wesamothman said:
Hi runandhide05. First allow me to send you a bigggggg thank you for your apktool. It really was apktool problem.
I did as you suggested, still, didn't work from the first time (modified to 3 screens) although the changes were persistent this time. so, in addition to the above files, i had to modify the following as well:
workspace.xml in layout-sw720dp
and public.xml in res/values in which I had to delete
<public type="id" name="cell4" id="hex val xxxxx" />
<public type="id" name="cell5" id="hex val xxxxx" />
So, now I tested with these changes and I got 3 screens
I will try to do 1 screen, and 7 screens.
Thanks again. you are truly appreciated.
Click to expand...
Click to collapse
ah, sorry completely forgot about the public XML. glad u got it
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
ah, sorry completely forgot about the public XML. glad u got it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Dear runandhide, your brilliant advises/expertise is what helped me getting these mods in place. Thx again trillion times and I shall never forget that. I will finalize the flashable zips as mods in dev forum for xoomers of team eos jellybean interest.
Sent from my MZ601 using Tapatalk 2

Awesome work. Pm me when you have 7 screens cwm.zip
EOS3 N132 @ MZ604 [XDA HD]
Stock ICS @ SGH-i717R [XDA Premium]

Eun-Hjzjined said:
Awesome work. Pm me when you have 7 screens cwm.zip
EOS3 N132 @ MZ604 [XDA HD]
Stock ICS @ SGH-i717R [XDA Premium]
Click to expand...
Click to collapse
It will available today on DEV Forum. 1 screen, 3 screens, 5 screens (default) and 7 screens.
Keep an eye on the dev section.

Here is the link for the mods. 1,3,5,7,9 screens mods added.
http://forum.xda-developers.com/showthread.php?p=30306937
Sent from my MZ601 using Tapatalk 2

[MOD]TF700T Battery % Mod

This is a mod for the TF700T to add 1% battery indicators for both the tablet and dock.
This posting is for developers, not newbies who usually do not know what they are doing.
First things first: I am a retired software engineer (and approaching retirement age). I do not have much time for support of this mod as I spend most of my time teaching English in Thailand and I develop ROMs for the SGS3. With that said, you are free to use this however you wish. BUT, please give me credit for the work. A link back to this page would be great. AND, I cannot guaratee it will will for everyone. Use at your own risk.
I will try to answer questions as soon as I can. Hopefully, some of the better developers can jump in and help with questions. If I do not answer a question right away, it is because I am busy with school.
This is probably not one of the better how-to-do-it posts, but it is the best I can do at this time.
What you will need:
1. Winmerge - you can get it here: Winmerge
This is a great app for making changes to newer ROMs without having to manually find all your previous changes. It is a pretty much cut 'n paste layout as you can see where the changes are and just copy them into the new source file. It uses a split window format for comparing previous and new source files. I usually view the original modded file in the right window and the new file I want to mod in the left window. Differences will be highlighted. Just marked the changes and copy them from the right window to the left window. Don't forget to save the file before exiting.
2. The attached zip file which contains the battery icons for both the dock and tablet and the modified xml files. The icons were created using BatteryIconCreator_V9.0 which you can find on the web. Makes creating icons easy plus you can merge 2 icons into 1. The zip file contains xml files for JellyBean v10.4.4.20 ROMs. It should work on previous versions as I started working on this with v10.4.4.16.
3. apktool150.jar - from here: http://miui.connortumbleson.com/other/apktool/apktool_1.5.0.jar
4. aapt.exe - from here: http://miui.connortumbleson.com/other/apktool/aapt/win/aapt.exe
For items 3 and 4, I have included them for Windows only. You should already know how to use apktool already and where these files go.
IF your ARE NOT on Windows O/S, go to this link to get the correct aapt file: APKTOOL
You MUST HAVE both of the files (3 & 4). Very important.
There are no install zips attached to this post. I am just too lazy to make them.
This is mostly for developers of TF700T Roms.
The files we will be modding:
framework-res.apk
SystemUI.apk
Transformer.apk
First thing to do is to decompile all 3 files:
java -jar apktool150.jar d <source.apk> <folder>
where <source.apk> is one of the above 3 files and <folder> is where you want them decompiled to.
Example: java -jar apktool150.jar d SystemUI.apk systemui
First the tablet battery mod:
SYSTEMUI.APK
Tablet icons
1. Copy the tablet battery icons to: /res/drawable-sw720dp-hdpi
2. Copy stat_sys_battery.xml AND stat_sys_battery_charge.xml to /res/drawable
3. Add the following to the end of /res/values-sw600dp/styles.xml:
<style name="StatusBarBatteryNotificationText2">
<item name="android:textSize">1.0dip</item>
<item name="android:textColor">#00999999</item>
</style>
4. Change /res/layout/status_bar_quick_settings_title.xml
(change both dock and battery) below is the modified script change (partial script).
<TextView android:id="@id/battery_text" android:layout_width="wrap_content" android:layout_height="1.0dip" android:layout_marginTop="-4.0dip" android:src="@drawable/ic_notification_open" android:text="@string/status_bar_settings_settings_button" android:singleLine="true" android:layout_below="@id/battery" android:layout_centerHorizontal="true" style="@style/StatusBarBatteryNotificationText2" />
FRAMEWORK_RES.APK
Dock-icons
1. Copy the dock battery icons to /res/drawable-hdpi
2. Copy stat_sys_dock_battery.xml AND stat_sys_dock_battery_charge.xml to /res/drawable
TRANSFORMER.APK
1. Change res/layout/status_bar_docking.xml:below is the modified script change (partial script).
<ImageView android:layout_gravity="center_vertical" android:src="@drawable/asus_ep_kb_battery_dock" android:layout_width="32.0dip" android:layout_height="32.0dip" android:scaleType="centerInside" />
<TextView android:layout_gravity="right|center" android:id="@id/battery_level" androidaddingRight="12.0dip" android:layout_width="56.0dip" android:layout_height="wrap_content" android:singleLine="true" android:layout_toRightOf="@drawable/asus_ep_kb_battery_dock" android:layout_alignBaseline="@drawable/asus_ep_kb_battery_dock" style="@style/StatusBarNotificationText" />
2. Add asus_ep_kb_battery_dock.png to /res/drawable-hdpi/
After you have done all of that, you need to compile them:
BUT FIRST: SystemUI.apk will not be decompiled correctly -> res/values/public.xml
We need to change some things or it will not compile.
Open /res/values/public.xml and go all the way to the end.
Change the last 2 entries to look like the following (the decompile hex value ordering in out of sequence):
<public type="menu" name="notification_popup_menu" id="0x7f0f0000" />
<public type="menu" name="recent_popup_menu" id="0x7f0f0001" />
Save the file and exit.
Now we can compile all the files.
java -jar apktool150.jar b <source folder>
where <source folder> is where you decompile the apk to.
Example: java -jar apktool150.jar b systemui
the apk file will be in the dist subfolder under systemui
After all 3 files have been compiled, you need to copy the META-INF folder and the AndroidManifest.xml from the original apk to the newly built apk. You need to do this for each of the 3 files.
The TF700T does not like the resources.arsc entry compressed. So...we have to extract the contents from SystemUI.apk and Transformer.apk. Create a new apk (using store only) no compression. You can use 7zip for this.
After you have done this for the SystemUI.apk and Transformer.apk files, zipalign all 3 files and install them in their proper folders on your tablet. I have included a zip align program in the attached zip file. Put the 3 files in the align folder and run the zip-app.bat program.
I have tried to make this easy, especially if you use WinMerge. It's as easy as copy 'n paste.
All files, including the modded source files (except Winmerge) are included in the attached zip file.
ZIPFILE: TF700T 1% Battery Mod

Thanks man, donno if im gonna implement this but hopefully we can get some devs to preload it onto other roms. You should pm scott and hiemanshu! thanks again.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

gutts10 said:
Thanks man, donno if im gonna implement this but hopefully we can get some devs to preload it onto other roms. You should pm scott and hiemanshu! thanks again.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I'm sure users would prefer percentage anyways, right?
From TF700, hit THANKS for others

Hi! thanks for this mod and for opening a dedicated thread.

Does the zip have a version to go for the latest job update? I can implement it straight into the ROM quickly if so. Otherwise I'll work through instructions and ask as I go.

sbdags said:
Does the zip have a version to go for the latest job update? I can implement it straight into the ROM quickly if so. Otherwise I'll work through instructions and ask as I go.
Click to expand...
Click to collapse
The easiest way is to just do file compares based on the files mentioned in Post #1.
If you use winmerge.exe it is easy to find the differences and cut and paste. It's what I use for all my ROM development for TF700T and GS3.
The files are from 104420.

OK Couple of questions - I tried to use the .20 files but SystemUI.apk is different.
There is no res/values folder......
neither is there a /res/values-sw600dp either ....
Are they important or have Asus changed the files?
Edit: Ah figured it out - ignore me!

I'm watching you
sbdags said:
OK Couple of questions - I tried to use the .20 files but SystemUI.apk is different.
There is no res/values folder......
neither is there a /res/values-sw600dp either ....
Are they important or have Asus changed the files?
Edit: Ah figured it out - ignore me!
Click to expand...
Click to collapse
Sent from my ASUS Transformer Pad TF700T

chogardjr said:
I'm watching you
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
Figured it out and got it working
Thanks OP!

The icon and the % are not clear like stock...hard to read.

buhohitr said:
The icon and the % are not clear like stock...hard to read.
Click to expand...
Click to collapse
Agreed.
For my GNex I use circlesmod by hooolm, which is a lot clearer. I think I'll try throwing a mod together with those icons...
http://circlesmod.dk/?s=dl

[TUTORIAL] Speed up notification pullup and dropdown (SystemUI.apk) all devices :)

Tutorial about speeding up notification center drop down/pull up
1.First of all you need to get SystemUI.apk of yur actual rom
The ne im using is open root explorer and copy SystemUI.apk to your sdcard
2.Connect the phone to the computer and copy the SystemUI.apk to the extracted APKTOOL directory (download apktoolApktool.zip)
3.There is a guide on how to use apktool here :Guide apktool
4.Decompile SystemUI.apk
5.Navigate \SystemUI\res\values and open dimens.xml (use notepad ++)
6. Find self_expand_velocity, self collapse velocity. and change the values from the defalut +2000 per each.
7.You can change other values too, they are pretty much selfexplanatory.
8.After the necessary changes save the file and recompile systemui.apk
9.After recmpiling you can push it to system using ADB or i made a .zip to flash it in recovery.(Just put SystemUI.apk in system/app and you are ok) Just whatch out for the name as it should be exactly the ssame as it was before.
10.Flash the zip wipe cache/dalvik and enjoy your new fast dropdown and pullup
DONT FORGET THANX BUTTON
EDIT: It was pointed out that in newer versions of android (dip=dp) its the same thing so don't change it.

Mr.Nigma... said:
Tutorial about speeding up notification center drop down/pull up
1.First of all you need to get SystemUI.apk of yur actual rom
The ne im using is open root explorer and copy SystemUI.apk to your sdcard
2.Connect the phone to the computer and copy the SystemUI.apk to the extracted APKTOOL directory (download apktoolApktool.zip)
3.There is a guide on how to use apktool here :Guide apktool
4.Decompile SystemUI.apk
5.Navigate \SystemUI\res\values and open dimens.xml (use notepad ++)
6. Find self_expand_velocity, self collapse velocity. and change the values from the defalut +2000 per each.
7.You can change other values too, they are pretty much selfexplanatory.
8.After the necessary changes save the file and recompile systemui.apk
9.After recmpiling you can push it to system using ADB or i made a .zip to flash it in recovery.(Just put SystemUI.apk in system/app and you are ok) Just whatch out for the name as it should be exactly the ssame as it was before.
10.Flash the zip wipe cache/dalvik and enjoy your new fast dropdown and pullup
DONT FORGET THANX BUTTON
Click to expand...
Click to collapse
I decompiled systemui.apk but i can/t find \SystemUI\res\values

I have the same question. maybe your decompilation have some problems.
Sent from my lenovo A789 using xda app-developers app

Got it working... FINALLY
OK first of all thanks for this, makes a huge difference on the notification pullup and dropdown speed.
I couldn't apply the path with just the regular apktool, tried different revisions and none worked until I found apktoolsjb on this forum
http://forum.xda-developers.com/showthread.php?t=1809649
Thanks again

yonutz said:
I decompiled systemui.apk but i can/t find \SystemUI\res\values
Click to expand...
Click to collapse
it is in that folder for sure. have followed the guide step by step? maybe u havent decompiled just extracted the apk.

On Note 2 (and probably other Samsung devices) there is no layout.xml, but values are inside smali file (SystemUI\smali\com\android\systemui\R$layout.smali). However those are in hex format which I cannot decode.
.field public static final self_collapse_velocity:I = 0x7f0c001c
.field public static final self_expand_velocity:I = 0x7f0c001b
Click to expand...
Click to collapse
Above value translates to 2131492892 as integer, which makes zero sense. Probably some kind of float value?

matejdro said:
On Note 2 (and probably other Samsung devices) there is no layout.xml, but values are inside smali file (SystemUI\smali\com\android\systemui\R$layout.smali). However those are in hex format which I cannot decode.
Above value translates to 2131492892 as integer, which makes zero sense. Probably some kind of float value?
Click to expand...
Click to collapse
Looks more like a reference to resources to me.

matejdro said:
On Note 2 (and probably other Samsung devices) there is no layout.xml, but values are inside smali file (SystemUI\smali\com\android\systemui\R$layout.smali). However those are in hex format which I cannot decode.
Above value translates to 2131492892 as integer, which makes zero sense. Probably some kind of float value?
Click to expand...
Click to collapse
Try to check for that id (0x7f0c001c and/or 0x7f0c001b) in res/values/ids.xml. It could point to any value in any of the xml inside res/ folder.

No xml file contains those values (I ran search over whole folder). Only before mentioned R$layout.smali and com\android\systemui\statusbar\phone\PhoneStatusBar.smali

Linux
Any way I con do this in Linux, ubuntu to be specific.
I figured it out, Ijust hope I can put back into .apk format.

Be careful:
"dp" was actually called "dip" in early versions of the SDK. They changed it to "dp" shortly after.
Click to expand...
Click to collapse
That screenshot isn't from a 4.1/4.2 rom - So anyone who wants to try this and has 4.2 (I'm having 4.2.2), change only the values. leave the "dp" as is, don't change it into "dip".
OP - you might as well write this down!

Great, some developer with Xposed skills to do that through an Xposed module .... (You know that would be great)

I used your MOD as an Add On for my ROM. I hope thats ok credit was given (see bottom of OP). Thanks for the Info..
http://forum.xda-developers.com/showpost.php?p=37148754&postcount=1

Thanks. I already hitted it.
Sent from my C6603 using xda app-developers app

Great tut, I would suggest turning off animations entierly in developers options for the best UI smoothness.

self_expand_velocity, self collapse velocity NOT FOUND
I dint find anything like that in \SystemUI\res\values\dimens.xml
Samsung galaxy ace GT-S5830i

I can't find a values folder in my SystemUI

riteshpanjwani said:
I dint find anything like that in \SystemUI\res\values\dimens.xml
Samsung galaxy ace GT-S5830i
Click to expand...
Click to collapse
As some people replied these values are in another file. But i'll look again and edit the op with SAMSUNG specific files

Hmmm
JDogg1329 said:
I can't find a values folder in my SystemUI
Click to expand...
Click to collapse
Check your ROM if it is odex, check /system/app/ if there is SystemUI.odex. You need to deodexed if first so you can edit. However you can also di it using baksmali you just need the SystemUI.odex.

I have this, dont have this what you say.What do now?.Custom ROM - CM7

[Q] How to change Phone Defaults except build.prop?

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

[GUIDE] How to Remove the Lockscreen Wallpaper and Notification pulldown Dimming Tint

This is a guide for Android 8.1 and Android P for removing the tint on the lockscreen wallpaper. It has been tested on Pixel, Pixel 2, and Nexus 5X but I would imagine it would work on others as well.
Pull and decompile the SystemUIGoogle.apk, SystemUI.apk, or whatever your SystemUI is named.
Go to the res/values folder and open the bools.xlm with notepad++
Find the below lines of code (these are not all grouped together)
Code:
<bool name="config_showDividersWhenGroupNotificationExpanded">false</bool>
<bool name="config_showGroupNotificationBgWhenExpanded">false</bool>
<bool name="config_showNotificationExpandButtonAtEnd">false</bool>
<bool name="config_status_bar_scrim_behind_use_src">true</bool>
and change them to this:
Code:
<bool name="config_showDividersWhenGroupNotificationExpanded">true</bool>
<bool name="config_showGroupNotificationBgWhenExpanded">true</bool>
<bool name="config_showNotificationExpandButtonAtEnd">true</bool>
<bool name="config_status_bar_scrim_behind_use_src">false</bool>
Next, open super_status_bar.xml located in the res/layout folder.
Add this after each of these 3 codes:
android:background="#00000000"
1.
Code:
android:fitsSystemWindows="true"
2.
Code:
android:id="@id/backdrop_back"
3.
Code:
android:id="@id/status_bar_container"
After this code add android:visibility="invisible"
Code:
android:id="@id/scrim_behind"
Your code might not be exactly the same but find the line that contains android:id="@id/scrim_behind" and you should be good. Save your changes, recompile, and replace your SystemUI.apk with your newly modded one with whatever method works best for you.
I have not found any adverse effects from these changes.

Has anyone tried this on Android Pie?

Augustin79 said:
Has anyone tried this on Android Pie?
Click to expand...
Click to collapse
Yes it still does.

Is this possible to apply on aosp rom?
I tried to decompile the systemui.apk with framework_res.apk and edit it then recompile the apk.
But no luck, after reboot my phone, the phone shows the home page directly without lock screen, status bar. I can't open the status bar or back to my lock screen until I restore the systemui.apk.
Maybe, there is something wrong with decompiling and recompiling. I will try again.

This doesn't work for me.
If I sign SystemUI.apk with my own key, it can't acquire the right permissions (logcat says "this requires android.permission.INTERACT_ACROSS_USERS_FULL") and the keyguard is skipped (boots to home screen).
If I use the META-INF from the original apk, even with the original classes.dex, the phone bootloops and spams logcat with "android.content.res.Resources$NotFoundException: String resource ID #0x0".

Cebtenzzre said:
This doesn't work for me.
If I sign SystemUI.apk with my own key, it can't acquire the right permissions (logcat says "this requires android.permission.INTERACT_ACROSS_USERS_FULL") and the keyguard is skipped (boots to home screen).
If I use the META-INF from the original apk, even with the original classes.dex, the phone bootloops and spams logcat with "android.content.res.Resources$NotFoundException: String resource ID #0x0".
Click to expand...
Click to collapse
I was able to get these changes to work by making a Substratum theme for SystemUI. Ideally this wouldn't also apply to the notifications pulldown, but at least my lock screen finally looks good.

I got it working!
So, I have been trying to modify the value of SCRIM_BEHIND_ALPHA_KEYGUARD in SystemUI, which needs more than just a Substratum theme.
I discovered that with "apksigner verify --print-certs" you can get helpful information about the verification status of an APK.
That command told me that the APK built by apktool was missing some resources. So instead of using that, I made a copy of the original APK and replaced the classes.dex with the one that apktool built.
That at least made the MANIFEST.MF agree with the contents, but the signature did not verify because the APK had been modified.
So, I signed it with the platform key using "apksigner sign --key platform.pk8 --cert platform.x509.pem --v1-signer-name CERT". Then the signature verified, and it had the same certificate digests.
It seems as though my phone only accepts a privileged system app if apksigner cannot disinguish it from one that was officially built and shipped with the ROM, which is probably a good thing.
Now I know to be more careful about A) assuming that apktool works seamlessly, B) replacing the right files in an apk and leaving everything else alone, and C) verifying an APK before putting it on my phone.