Can someone point me to the proper xml and lines that need to be edited to disable the wifi nag? i am running scrosler's stock odexed rom and I compared default.xml in /system/customize/ACC with his but couldn't find anything. Any help would be great. Thanks.
jbeitel said:
Can someone point me to the proper xml and lines that need to be edited to disable the wifi nag? i am running scrosler's stock odexed rom and I compared default.xml in /system/customize/ACC with his but couldn't find anything. Any help would be great. Thanks.
Click to expand...
Click to collapse
Hopefully we can get some other comments on this, but with this latest OTA, I am having a semi issue getting it to work.
I do know that the way to do it before was like you said, in ACC/default.xml.
There are .png images of the wifi nag though in both framework-res.apk and framework-htc-res.apk
in default.xml find these two and change to this
Code:
<item type="boolean" name="support_Wifioffload">false</item>
<item type="integer" name="wlan_wifi_status">1</item>
I think if you do the edits above in just the default.xml the nag will show up on boot, but all you have to do is go into settings > WiFi > advanced > and uncheck the Wi-Fi- pop-up. This should fully remove the Wifi nag.
I did all the edits I posted above, but remove the .png image in either framework-res.apk or framework-htc-res.apk removed the image so some random one shows up instead, so I suggest just editing the ACC/default.xml and unchecking in Wi-Fi advanced settings.
andybones said:
Hopefully we can get some other comments on this, but with this latest OTA, I am having a semi issue getting it to work.
I do know that the way to do it before was like you said, in ACC/default.xml.
There are .png images of the wifi nag though in both framework-res.apk and framework-htc-res.apk
in default.xml find these two and change to this
Code:
<item type="boolean" name="support_Wifioffload">false</item>
<item type="integer" name="wlan_wifi_status">1</item>
I think if you do the edits above in just the default.xml the nag will show up on boot, but all you have to do is go into settings > WiFi > advanced > and uncheck the Wi-Fi- pop-up. This should fully remove the Wifi nag.
I did all the edits I posted above, but remove the .png image in either framework-res.apk or framework-htc-res.apk removed the image so some random one shows up instead, so I suggest just editing the ACC/default.xml and unchecking in Wi-Fi advanced settings.
Click to expand...
Click to collapse
excellent, I'll give that a try, thanks.
Related
Can anyone help me try and remove the DriveSmart settings menu found in Settings.
I deleted the DriveSmart APKs but its still showing in Settings which means its hardcoded in there...
you will have to decompile the settings.apk and remove the entire line of drivesmart
I actually tried that already but couldn't recompile it for some reason.
Can you give it a go? I can send you the edited files...
jboogie3 said:
you will have to decompile the settings.apk and remove the entire line of drivesmart
Click to expand...
Click to collapse
Actually, only this line needs to be edited if I'm not mistaken:
Path: res\values\
File: bools.xml
Line: <bool name="has_tmo_driveSmart_settings">true</bool>
Process: Change the value from true to false
Any help would be appreciated. I've been trying but get errors when I try to recompile Settings.apk
Thanks!
Here's the original APK.
I hope someone can help me out. I've used APK Manager and APK Edit and neither tool can recompile it after I've edited it...
I was kinda hoping it would get rid of the settings portion when the apk's for drive smart were deleted as well. oh well.
That is exactly what this is aimed at.
I was able to delete the strings from the de-compiled code however, I got errors when re-compiling it.
Hopefully, someone out there can help with this...
dlamber7 said:
I was kinda hoping it would get rid of the settings portion when the apk's for drive smart were deleted as well. oh well.
Click to expand...
Click to collapse
Was finally able to compile it without any errors.
Someone, try this please: Modified T-Mo Froyo Settings
Thanks!
Has anyone tried the modified Settings I posted?
I'll try it here in a little bit. If not today than tomorrow and let you know. Just install zip via recovery?
Nope. Rename the existing Settings.apk and Setting.odex and then move the modified Settings.apk to system/app/
Don't forget to set the correct permissions...
Thanks!
dlamber7 said:
I'll try it here in a little bit. If not today than tomorrow and let you know. Just install zip via recovery?
Click to expand...
Click to collapse
I still really want this done.
Can someone post a deodexed Settings.apk from the latest FroYo update please...
Anyone figure this out yet? I tried placing the settings.apk from this thread into my working kitchen folder over writing the stock settings.apk but when I flashed the rom the settings option was missing from the app draw???
This guide assumes you already know how to use apktool and / or apkmanager. If you don`t, there are plenty of guides already on XDA.
Latest Sense 4.0 and apktool are not great friends. The 3 most important files framework-res.apk, com.htc.resources.apk and systemui.apk all create fatal errors, when using latest apktool 1.43 version. Apktool`s error log is always a big help to solve compile issues, but you need a bit of compile and coding experience to finally solve these. After I stumbled about many people having Sense 4.0 compile issues, I decided to post this guide. Hopefully this will encourage more guys to add mods to One S, after they might have hit a wall before.
Credits:
brut for his awesome apktool
daneshm for original apkmanager
Known issues: ATM com.htc.resources fix does not work with One X
1. Framework-res.apk
a) Since ICS apktool creates multiple plurals errors, but you can easily fix these by using a custom version of apktool. Now updated incl. latest smali baksmali properties for ICS (thx fernando)
Custom ICS apktool version - http://minus.com/mIA3OFkYq/19
b) if you get tag errors like these
anims.xml:3: error: Found tag anim where item is expected
layouts.xml:3: error: Found tag layout where item is expected
raws.xml:3: error: Found tag raw where item is expected
Replace all tags in layouts.xml in values folder with:
<item type="layout" at the front and </item> at the end
Replace all tags in anims.xml in values folder with:
<item type="anim" at the front and </item> at the end
Replace all tags in raw.xml in values folder with:
<item type="raw" at the front and </item> at the end
2. Systemui.apk
When trying to decompile systemui, you will get bad magic value errors. Solution is to decompile without classes, as long as you don`t need to edit smali code. Even if you need to do that, you can still decompile classes.dex separately with smali baksmali.
a) Use -s switch when decompiling to copy classes.dex instead of decompiling it
java -jar apktool.jar d -s systemui.apk systemui-decoded
b) If you are using apkmanager, you can just export classes.dex, then delete classes inside the apk. Then decompile, edit, compile and add classes.dex back when ready.
EDIT: with updated apktool version systemui now compiles fine incl. classes.dex
3. com.htc.resources.apk
Here you get nice layouts tag errors and public entry issues. Again there`s an easy fix for that.
a) Replace all tags in layouts.xml in values folder with:
<item type="layout" at the front and </item> at the end
PHP:
<resources>
<item type="layout" name="htc_list_item_imageicon_text">@layout/zzzz_htc_list_item_imageicon_text</item>
<item type="layout" name="pin_keyboard">@layout/zzzz_pin_keyboard</item>
<item type="layout" name="zero_dummy_layout">@layout/alert_dialog</item>
<item type="layout" name="htc_list_item_2text_2stamp">@layout/zzzz_htc_list_item_2text_2stamp</item>
<item type="layout" name="htc_list_item_2text_bright">@layout/zzzz_htc_list_item_2text_bright</item>
<item type="layout" name="htc_list_item_image_2text_image_bright">@layout/zzzz_htc_list_item_image_2text_image_bright</item>
<item type="layout" name="htc_list_item_imageicon_2text_2stamp">@layout/zzzz_htc_list_item_imageicon_2text_2stamp</item>
<item type="layout" name="htc_list_item_separator">@layout/zzzz_htc_list_item_separator</item>
<item type="layout" name="htc_list_item_dlna_1">false</item>
</resources>
b) Delete entry "zero_dummy_dimen" in public.xml - it will be created correctly again during compile
In case you still have issues, here is my apkmanager build environment, that works fine with all these fixes.
http://minus.com/mIA3OFkYq/20
Hex editing solution for latest com.htc - thx to tbonanno231 - http://forum.xda-developers.com/showpost.php?p=32222697&postcount=112
Latest apktool version 1.4.9 from ibotpeaches
Big thx to ibotpeaches for the tremendous follow up on apktool
Fixes plural errors
Fixes item tag errors
Fixes bad magic value errors
Adds ICS smali properties (compared to latest official version from brutall)
Fixes unknown folder issues (only with patched aapt.exe)
Download apktool 1.4.9:
http://sdrv.ms/T0LpzK
Download patched aapt.exe
http://sdrv.ms/Mfrkaa
c) Workaround for One X ROMĀ“s
Since many of you guys might only be in need to decompile all the .9`s in com.htc.resources, there is a workaround that allows you to compile these.
Decompile with:
1. java -jar apktool.jar d --keep-broken-res com.htc.resources.apk com.htc.resources-decoded
This ignores all errors and decompiles the apk incl. all patched pngs.
2. Make your changes and copy the changed png`s in any given decompiled apk (I use calendarprovider.apk for this task, very slim apk, compiles fast...) and compile them
Updated with new custom apktool version, that includes latest smali baksmali properties to properly decompile ICS Java code.
Updated with new section b), that explains how to fix tag errors with latest 1.78 framework-res.apk
After trying this method.....it compiles framework-res 100% with absolutely NO issues. Thanks a million!!! I'm pretty sure everything else works....
Now I guess I'll try and work and see if I can find out how integrated in the framework WiFi calling is in the T-Mobile One S build in hopes we can get it working on any One S ROM, US or EU based....
Any ideas would help! lol
You can PM chrisch1974 from Virtuous team, he is already working on this. Maybe your combined efforts help.
Updated apkmanager with latest apktool version that includes ICS smali properties
he_stheone64 said:
Updated apkmanager with latest apktool version that includes ICS smali properties
Click to expand...
Click to collapse
Would be amazing integrate this tutorial with mine on vts!
Inviato dal mio HTC Sensation XE con Tapatalk 2
no problem old DHD buddy, just go ahead.
Really appreciate this man! Exactly what I've been waiting for. The apktool.jar seems to be working fine, but the apk manager build environment won't compile .apks correctly for me. Is it supposed to be working straight out of the box?
Edit: Has anyone successfully edited colors.xml in Camera.apk without breaking the video recording function? Seems to be impossible for me.
Edit 2: Has anyone successfully edited colors.xml in Contacts.apk without breaking it?
I tried HTCContacts and resources like colors and styles are fine, it did not break anything on the phone.
First of all great work.
But i have a little problem.
When i decompile the systemUi its works well but when a compilate it, after i made a few changes, it simple dont change anyting. The final system is the same that de original...
Can you help me?
Thanks
he_stheone64 said:
no problem old DHD buddy, just go ahead.
Click to expand...
Click to collapse
Yeah now I'm on Sensation, ASAP I'll send you a pm
Inviato dal mio HTC Sensation XE con Tapatalk 2
MatZ69 said:
First of all great work.
But i have a little problem.
When i decompile the systemUi its works well but when a compilate it, after i made a few changes, it simple dont change anyting. The final system is the same that de original...
Can you help me?
Thanks
Click to expand...
Click to collapse
Have you spelled the name of your compiled apk correctly? Once I had like four systemuis in there, with variations of capital/ non-capital letters you can check via adb:
adb shell
Cd system/app
Ls
Then you can use rm commands to remove the apks there and push your modded one
Sent from my HTC One S using XDA
Double post
Habarug said:
Have you spelled the name of your compiled apk correctly? Once I had like four systemuis in there, with variations of capital/ non-capital letters you can check via adb:
adb shell
Cd system/app
Ls
Then you can use rm commands to remove the apks there and push your modded one
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Yh you are right. Now have another problrm. Im trying to compile te settings but i need the dependencies of framework
Bu whe do decompile whit dependencies it simple dont accept it. I cant figure what its wrong. Thanks
Sent from my GT-S5660 using XDA
Did you install proper framework with apktool if command or with 10 in apkmanager?
he_stheone64 said:
Did you install proper framework with apktool if command or with 10 in apkmanager?
Click to expand...
Click to collapse
Yh but it says: "Sorry that is not a dependencie apk"...
and i did with apktool the "if" command...
Dont know :/
did you try dragging in the htc.resources.apk from your rom in the first step of option 10. in apk manager?
Sorry but i'm using a samsung :S
Then you need to do the same with twframework.
See Post Eight for download link for fixed SystemUI- thanks to mentose457.
Loving the new CleanRom 6 R2. One thing I have had no luck with is getting the status bar to be transparent. I have tried flashable zips, I have tried the method below which seems to be the consensus on how to go about doing this and I have tried changing out the status bar png's as well but each time I get no status bar and the inability to change my wallpaper (it just goes black). Is there anyone out the who has had success on changing the status bar to 100% transparent or is there a flashable zip that works with Scott's CleanRom 6 R2? I can attach my SystemUI, framework-res, lidroid-res and twframework-res if there is anyone that can help me out.
Credit to team-nocturnals website for where I found this method
1. You should decompile SystemUI.apk
2. Open /SystemUI/res/layout/tw_super_status_bar.xml and change android:background to 100% transparent:
Code:
<com.android.systemui.statusbar.phone.StatusBarW in dowView android:background="#00000000" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
3. Save /SystemUI/res/layout/tw_super_status_bar.xml
4. Open /SystemUI/res/values/drawables.xml and edit this line to get transparency you need, for example, 100% transparent:
Code:
<item type="drawable" name="status_bar_background">#00000000</item>
5. Save /SystemUI/res/values/drawables.xml
6. Recompile SystemUI.apk
Done... Now you have 100% transparent homescreen statusbar
anarchyhunter80 said:
Loving the new CleanRom 6 R2. One thing I have had no luck with is getting the status bar to be transparent. I have tried flashable zips, I have tried the method below which seems to be the consensus on how to go about doing this and I have tried changing out the status bar png's as well but each time I get no status bar and the inability to change my wallpaper (it just goes black). Is there anyone out the who has had success on changing the status bar to 100% transparent or is there a flashable zip that works with Scott's CleanRom 6 R2? I can attach my SystemUI, framework-res, lidroid-res and twframework-res if there is anyone that can help me out.
Credit to team-nocturnals website for where I found this method
1. You should decompile SystemUI.apk
2. Open /SystemUI/res/layout/tw_super_status_bar.xml and change android:background to 100% transparent:
Code:
<com.android.systemui.statusbar.phone.StatusBarW in dowView android:background="#00000000" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
3. Save /SystemUI/res/layout/tw_super_status_bar.xml
4. Open /SystemUI/res/values/drawables.xml and edit this line to get transparency you need, for example, 100% transparent:
Code:
<item type="drawable" name="status_bar_background">#00000000</item>
5. Save /SystemUI/res/values/drawables.xml
6. Recompile SystemUI.apk
Done... Now you have 100% transparent homescreen statusbar
Click to expand...
Click to collapse
not sure, but after doing this, then go into res/colors.xml and look for the status bar color, (it's either black or that ugly gray) and change that to "00000000" as well. see if that works.
Use morphology. Keep everything else the same but make the status bar transparent.
Sent from my SCH-I535 using xda app-developers app
so i tried the color xml and morphlogy and I still get the same results no status bar and with morphology I am getting a Unfortunately, No recent apps has stopped message.
anarchyhunter80 said:
so i tried the color xml and morphlogy and I still get the same results no status bar and with morphology I am getting a Unfortunately, No recent apps has stopped message.
Click to expand...
Click to collapse
Alright send your sysui here and ill do it.
mentose457 said:
Alright send your sysui here and ill do it.
Click to expand...
Click to collapse
Thanks for the assistance. Attached is the SystemUI.apk, I cannot attach the framwork-res.apk it is to big.
anarchyhunter80 said:
Thanks for the assistance. Attached is the SystemUI.apk, I cannot attach the framwork-res.apk it is to big.
Click to expand...
Click to collapse
Out of curiosity, have you flashed any mods or are you on stock CleanROM?
anarchyhunter80 said:
Thanks for the assistance. Attached is the SystemUI.apk, I cannot attach the framwork-res.apk it is to big.
Click to expand...
Click to collapse
Rename to SystemUI.apk then push to /system/app/ then change permissions to rw-r--r-- then restart. You may have to restart then change the permissions as SystemUI will stop working till you restart. Note that when you first restart the status bar will be black. You need to pull down on the status bar for it to go transparent.
Enjoy.
https://dl.dropbox.com/u/44601870/SystemUICROM6.apk
mentose457 said:
Out of curiosity, have you flashed any mods or are you on stock CleanROM?
Click to expand...
Click to collapse
no flashing just stock clean rom 6 r2
mentose457 said:
Rename to SystemUI.apk then push to /system/app/ then change permissions to rw-r--r-- then restart. You may have to restart then change the permissions as SystemUI will stop working till you restart. Note that when you first restart the status bar will be black. You need to pull down on the status bar for it to go transparent.
Enjoy.
https://dl.dropbox.com/u/44601870/SystemUICROM6.apk
Click to expand...
Click to collapse
My friend I don't know what you did but would love to know how you did it. This is much better. Thank you. If you don't mind may I share your link on the CleanRom 6 thread?
anarchyhunter80 said:
no flashing just stock clean rom 6 r2
Click to expand...
Click to collapse
anarchyhunter80 said:
My friend I don't know what you did but would love to know how you did it. This is much better. Thank you. If you don't mind may I share your link on the CleanRom 6 thread?
Click to expand...
Click to collapse
All that needed to be changed was #4 from the OP. I also used 00ffffff instead of 00000000, though I dont think it would make a difference. Go ahead and share it.
mentose457 said:
All that needed to be changed was #4 from the OP. I also used 00ffffff instead of 00000000, though I dont think it would make a difference. Go ahead and share it.
Click to expand...
Click to collapse
So I didn't need to change the tw_super_status_bar? Only had to change the values/drawable.xml.
anarchyhunter80 said:
So I didn't need to change the tw_super_status_bar? Only had to change the values/drawable.xml.
Click to expand...
Click to collapse
Yep. I didnt look at what the other changes did. It may be that they make it so it boots up transparent.
I'm using kindacrap mods over cleanrom.. just make sure you don't use the kindacrap policy mods. I love the transparent status bar.
Sent from my SCH-I535 using xda app-developers app
This is how you can change all the system backgrounds plain colors (settings, contacts, etc) to an actual image instead of a color
The how to:
1. Decompile the framework-res.apk using Android Multitool
2. navigate to the res>styles>styles.xml and with notepad++ locate <style name="Theme"> and edit these lines:
change:
Code:
<item name="colorBackground">@color/background_dark</item>
to this
Code:
<item name="colorBackground">@color/transparent</item>
then change:
Code:
<item name="windowBackground">@drawable/screen_background_dark</item>
to this one to use a png for the background:
Code:
<item name="windowBackground">@drawable/backgroundftw</item>
3. Locate <style name="Theme.Black" parent="@style/Theme">
and change this line:
Code:
<item name="colorBackground">@color/black</item>
to this:
Code:
<item name="colorBackground">@color/transparent</item>
then change:
Code:
<item name="windowBackground">@color/black</item>
to this for the png image:
Code:
<item name="windowBackground">@drawable/backgroundftw</item>
4. Use a 512x512 png , name it "backgroundftw" and place it in drawable-nodpi folder
5. Recompile the framework-res.apk and replace it with the old framework-res.apk in system/framework
6. Enjoy
Things required for this tutorial:
1. Android Miltitool to decompile and replace image
2. notepad++ for the coding
3. Your brain
4. You have to know where to obtain the framework-res.apk from on your phone. Just go to system/framework using root explorer
5. Make a backup of ur ROM or a flashable of your old framework-res.apk just incase if you make a mistake while coding. So that you dont encounter a bootloop
6. Find a video on youtube to learn how to compile and decompile your framework-res.apk
Difficulty for this tutorial: medium
For images CLICK HERE
good but wrong way bro......
ur steps are correct but method is wrong....
u cannot obtain styles.xml or find value folder with 7 zip....
u need apktool for that....
n just adding images or edited styles.xml ...to framework-res.apk
bootloops n fcs.....
i
Avenger4droid said:
good but wrong way bro......
ur steps are correct but method is wrong....
u cannot obtain styles.xml or find value folder with 7 zip....
u need apktool for that....
n just adding images or edited styles.xml ...to framework-res.apk
bootloops n fcs.....
i
Click to expand...
Click to collapse
Will update the thread tomorrow
nathanjp said:
will update the thread tomorrow
Click to expand...
Click to collapse
update the thread then i will try for sure don't want bootloop
upload video bro
awesome workk bro but if u upload a video step by step then its very useful to every one or if not possible then plzz upload a image bro
Thread updated try it now
gaurav247star said:
update the thread then i will try for sure don't want bootloop
Click to expand...
Click to collapse
Bro i updated the thread a couple days ago. Try it now
great work and helpful guide
nathanjp said:
This is how you can change all the system backgrounds plain colors (settings, contacts, etc) to an actual image instead of a color
The how to:
1. Decompile the framework-res.apk using Android Multitool
2. navigate to the res>lstyles>styles.xml and with notepad++ locate <style name="Theme"> and edit these lines:
change:
Code:
<item name="colorBackground">@color/background_dark</item>
to this
Code:
<item name="colorBackground">@color/transparent</item>
then change:
Code:
<item name="windowBackground">@drawable/screen_background_dark</item>
to this one to use a png for the background:
Code:
<item name="windowBackground">@drawable/backgroundftw</item>
3. Locate <style name="Theme.Black" parent="@style/Theme">
and change this line:
Code:
<item name="colorBackground">@color/black</item>
to this:
Code:
<item name="colorBackground">@color/transparent</item>
then change:
Code:
<item name="windowBackground">@color/black</item>
to this for the png image:
Code:
<item name="windowBackground">@drawable/backgroundftw</item>
4. Use a 512x512 png , name it "backgroundftw" and place it in drawable-nodpi folder
5. Recompile the framework-res.apk and replace it with the old framework-res.apk in system/framework
6. Enjoy
Things required for this tutorial:
1. Android Miltitool to decompile and replace image
2. notepad++ for the coding
3. Your brain
4. You have to know where to obtain the framework-res.apk from on your phone. Just go to system/framework using root explorer
5. Make a backup of ur ROM or a flashable of your old framework-res.apk just incase if you make a mistake while coding. So that you dont encounter a bootloop
6. Find a video on youtube to learn how to compile and decompile your framework-res.apk
Difficulty for this tutorial: medium
Click to expand...
Click to collapse
Good work keep it up
djrkb24 said:
Good work keep it up
Click to expand...
Click to collapse
Have u tried the tutorial??
Guys do post your screenshots if you have tried out the tutorial
Will post a newer and simpler tutorial to make it easy for u guys. All you have to do is replace the image in this. Flash able zip will so be available
Hit the thanks button if you guys would like that
nathanjp said:
Will post a newer and simpler tutorial to make it easy for u guys. All you have to do is replace the image in this. Flash able zip will so be available
Hit the thanks button if you guys would like that
Click to expand...
Click to collapse
Isn't the settings background located in /res/drawable/background_holo_dark.xml?
DonDizzurp said:
Isn't the settings background located in /res/drawable/background_holo_dark.xml?
Click to expand...
Click to collapse
Nope you dont wanna edit that
nathanjp said:
Nope you dont wanna edit that
Click to expand...
Click to collapse
That's what I edited in order to remove the gradient and get an all black background. I did the styles.xml mod to get the wallpaper working though.
Its A Brilliant Guide Brother..Thanks..!
Thunder_Droid said:
Its A Brilliant Guide Brother..Thanks..!
Click to expand...
Click to collapse
Thanks bro.
work..thank you bro
could any1 let me know that how to make background transpearent
Copied Post GARBAGE
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.