This is very important feature to Android users.
This is very important feature to Android users. Because we install the screen recorder app, long screenshot app, launcher app ......etc the app won't run fully (fully functional) in our phone. Android 9go have this feature but android 10go dosen't have this feature. Please bring back to this feature in next update
Comments
The android 10 go source code has this feature disabled, hence, HMD cant bring this feature back with an update, unless they have a set team work on it, that is very unlikely, so we cant get this feature back...........
Bro. can I change my android 10 software to Android 9 ?????
If I can did that ? What is procedure ? Without PC
Yes, but the updates will be force installed on your phone anyways, so I don't recommend doing that, well, yes you can use mtk su on older builds of pie, but it's only a temporary solution, and it can get annoying at times, because it trips safety net everytime the exploit is used........
For which app you need this feature to be allowed? If it is super important to you, use Bugjaeger (you already know how to) and run this command:
appops set <package name> SYSTEM_ALERT_WINDOW allow
If you want to do the opposite, run this one instead:
appops set <package name> SYSTEM_ALERT_WINDOW ignore
This feature is turned off at system level
Oh, nice, thanks for reading the massive adb command list, it works for any apps, I wish we could do something about trying to get magisk working.....
You're welcome... Did you successfully unlock the oem of Nokia 1. Does that old xda method still work on android 10 go? If it is, then it's quite easy to install magisk on this device.
First, unlock the oem
Then, install the full ota from this link:
https://android.googleapis.com/packages/ota-api/nokia_frt_frontier00ww/470411602b9c1727b74b7b8c7494ea83378db07a.zip
(Yes I know, it's huge)
Now unzip it and extract the boot.img file.
Last, follow this instruction (no TWRP method) https://www.youtube.com/watch?v=PgyjtWb4cQA to modify that file and then install the same via magisk. You could also use Bugjaeger in this case as a PC alternative.
Did you try this (just curious)? Also, if we get an MR update, is flashing the original boot image enough to install future updates?
But one more thing is that 'topjohnwu'(developer of magisk) said that magisk v21 is having issues on mediatek devices, that's the reason I want to make sure that it actually is stable enough to use it....
The old method from XDA still works
Obviously I didn't try to do major experiments on my phone in this lockdown situation. I'm a bit wary of bricking the device due to a wrong step or any bug in magisk itself (you already mentioned one).
Oh, by the way, if you want to save your time and data, you could extract and then download the boot.img file by unzipping the large ota file online here:
https://extract.me
Do let me know when you succeed in the adventure ;)
Yeah, but the issue now is that if I patch the image with magisk, it's size is about 7 mb rather than the original 16 mb size, flashing it causes the phone to not boot.......(black screen)
I'm not sure where the 8-9 mb of data went, I think it was necessary because flashing it causes it to not boot.......
Was the OEM effectively unlocked? Go to 'developer options' and check if the 'OEM unlocking' option is greyed out. The other day I found out on an XDA post that it's not uncommon for magisk manager to cut down the boot.img file size to remove some security features which prevent android from getting rooted. In his/her case, the boot.img file was trimmed down by 3mb.
Yes, the option is greyed out and it says'The bootloader is already unlocked'........ Also, is there a step that I'm missing, like doing a factory reset after flashing the boot image, or some different fastboot command to prevent the device from bootlooping?
Bro this method dosen't work
I don't know what happened
If you followed those steps correctly, it will work. Yes, Bugjaeger doesn't show anything like "successful", "completed" etc after the command is applied. But then you can check the 'Display over other apps' state by going to the specific app info screen. Just don't expand the option and see if it's "allowed" or "not allowed"
I think the pro version has the command output feature, I'm not sure, can anyone confirm?
After applying this command appops set <package name> SYSTEM_ALERT_WINDOW allow the app showed "error"
Exit from Bugjaeger, reconnect the usb otg and check if the device id shows up at the bottom Bugjaeger's home screen. If it does, then apply the command again. Do check the spelling of the package name and other keywords. Also, for some system apps it might not work, because they have been given "privileged level permission" by the android OS.
"Bugjaeger pro" is quite pricey for a premium app. So, not very soon you'll be getting that confirmation for sure ;)
I wish the command output feature was available in the free version.......