Develop Bugs

Smaller LTE Data Icon Android P

Flash these in TWRP if you want a smaller LTE Data Icon. I also have one for removing it completely. These will also be in my next updated Aroma installers.
Oct Pie
https://www.androidfilehost.com/?fid=1322778262904023071
Oct Magisk
https://www.androidfilehost.com/?fid=1322778262904023073
DP3 uploaded
{
"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"
}

Thought you might want to see how it looks.
Big improvement over the large LTE stock P version.

Thanks for your hard work and releasing it us!

I uploaded new Magisk versions just now. Updater-script problems.

So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?

Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash TWRP

Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.

liam_davenport said:
If it's a Magisk Module go into Magisk > Modules and the + icon go to where the zip is located and install it
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.

Tulsadiver said:
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.
Click to expand...
Click to collapse
Thanks for clarification

Cause bootloop on DP3.

Queentus said:
Cause bootloop on DP3.
Click to expand...
Click to collapse
Which one did you flash?

Tulsadiver said:
Which one did you flash?
Click to expand...
Click to collapse
Sorry for not making it clear back then. I flashed the older mod which I believe was made for DP2, and it caused system ui crashing.
No problems with the DP3 updated one and thanks for the awesome work!:good:

Magisk installation failed on DP3, Magisk 16.4.
Log below.

Google Pay no longer working with PIE+ROOT (Magisk hide)

Ok so i was using Google Pay on oreo with full root using Magisk didn't even have to have GPAY ticked under Magisk Hide, only my banking app to allow fingerprint login. But since updating to the official PIE via ODIN and rerooting i no longer get GPAY is there any possible way i can get round this issue on PIE as that feature was really handy
My Phone history (Galaxy S9 SM-G960F)
Pie: Official FW + Root + Magisk 17.2 + TGP Kernel
Pie: Official FW + Root + Magisk 18.1 + TGP Kernel
{
"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"
}

Fine here.
Using canary build, make sure to clear cache in play services and gpay.
Enable hide
Hide magisk
All fine.

Aye did that but didn't solve my issue ? knox is tripped but pretty sure that was from the first time I rooted on oreo and pay worked perfectly

Redberry said:
Aye did that but didn't solve my issue ? knox is tripped but pretty sure that was from the first time I rooted on oreo and pay worked perfectly
Click to expand...
Click to collapse
I don't use it but there is a dedicated thread that may help with your issues in regards to google pay issues
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703

i was able to enable it after i locked the bootloader (and restored to stock pie rom)

spawnlives said:
I don't use it but there is a dedicated thread that may help with your issues in regards to google pay issues
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Click to expand...
Click to collapse
Good lad, didn't see that thread. But got gpay working again on rooted Pie

Redberry said:
Good lad, didn't see that thread. But got gpay working again on rooted Pie
Click to expand...
Click to collapse
Hi.
How did you manage to do this after all? Tks

Question How can I fix this annoying misalignment of Digital Wellbeing and Google ?

How can I fix this annoying misalignment of Digital Wellbeing and Google ?
{
"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"
}

AndroidsKings said:
How can I fix this annoying misalignment of Digital Wellbeing and Google ?
View attachment 5477655
Click to expand...
Click to collapse
thats after downgrading to 11? I remember this and I cant remember if I had downgraded, factory reset or upgraded to get rid of it.

Mine has done this as well! It started off with just Google being like that, and the DW joined it. I'm running a custom kernel and I'm rooted with Magisk. Have you got a similar setup?

samwhiteUK said:
Mine has done this as well! It started off with just Google being like that, and the DW joined it. I'm running a custom kernel and I'm rooted with Magisk. Have you got a similar setup?
Click to expand...
Click to collapse
I'm on factory firmware mate. Purely stock.

samwhiteUK said:
Mine has done this as well! It started off with just Google being like that, and the DW joined it. I'm running a custom kernel and I'm rooted with Magisk. Have you got a similar setup?
Click to expand...
Click to collapse
I'm on factory firmware mate. Purely stoc
Zeus0fyork said:
thats after downgrading to 11? I remember this and I cant remember if I had downgraded, factory reset or upgraded to get rid of it.
Click to expand...
Click to collapse
I did that mate but it's still the same.

AndroidsKings said:
I'm on factory firmware mate. Purely stoc
I did that mate but it's still the same.
Click to expand...
Click to collapse
Are you staying on 11 or updating to 12? If you're on 11 which version? When I downgraded and went to 11.8.8 or whatever it was like this. Flash update to both slots and see if that helps

@AndroidsKings that work?

Just uninstall updates for digital wellbeing and all will be fine

Question how do i know which version of magisk patched boot img to flash?

how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?

The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).

ekin_strops said:
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
Click to expand...
Click to collapse
ah i see, thanks!

Veid71 said:
how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
Click to expand...
Click to collapse
Settings > About Device > Version > Build Number
{
"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"
}
Make sure you've done all the OEM Unlock, etc first

djsubterrain said:
Settings > About Device > Version > Build Number
View attachment 5587231
Make sure you've done all the OEM Unlock, etc first
Click to expand...
Click to collapse
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?

Veid71 said:
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Click to expand...
Click to collapse
Jump in here :
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com

Just Incase anyone else runs into this issue on that magisk forum there's a universal safetynet fix (UNSF) that you can download and it'll fix it

Question Lost L1 Widevine after installing SparkOS and Magisk.

Anyone else had this issue, or any known fix for this? Had just flashed SparkOS.

Hello,
Install xiaomi.eu rom, you should be able from-> fingerprint unlock->payment with fingerprint to redownload widevine certificate. My language is italian maybe name of settings are a little bit different from what I write
Bye

Claudio67 said:
Hello,
Install xiaomi.eu rom, you should be able from-> fingerprint unlock->payment with fingerprint to redownload widevine certificate. My language is italian maybe name of settings are a little bit different from what I write
Bye
Click to expand...
Click to collapse
Right on cue, just got my phone working again. I saw this method, and flashed EU ROM via orange fox from Spark OS. Phone sadly got bricked. At the time, MiFlash wasn't recognizing my device and all I could do was fastboot.
Lots of YouTube and 3 hours later, finally was able to sideload stock ROM, then MiFlashed to clean everything, then installed SparkOS again. L1 is back.
I'm thinking the L1 certificate got lost due to Magisk?

Nice, I don't think it's a magisk issue, I've installed and still widevive is l1

Cool! I think I'll pass Magisk for now haha. The trauma!
In any case, if ever I do get Magisk again, can I see what ur modules are?

I'm using sparkOS too, still have it
{
"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"
}

lkamio said:
I'm using sparkOS too, still have it
View attachment 5845023
Click to expand...
Click to collapse
Got mine fixed. Looks like I messed up something during flashing.

glidarts0730 said:
Cool! I think I'll pass Magisk for now haha. The trauma!
In any case, if ever I do get Magisk again, can I see what ur modules are?
Click to expand...
Click to collapse
Hi,
I use safetynet fix (needed with magisk) and viper4android