Database Develop

Background threads created by supersu (until phone stops working)

I'm running Supersu with one app that requires root access , everything works but I've detected that supersu creates background processes that keep running forever and hogging memory and resources. After about 12 hours the phone's memory is depleted and hangs . I've got to reboot it or create a periodic task that kills processes like this one:
app_process /system/bin/com.android.commands.am.Am broadcast --user 0 -a eu.chainfire.supersu.NativeAccess -es su_appname net.zhdev.whatstasker -ei su_fromuid 10123 -eu su_access 1 -ei su_access 1 -ei su_touid 0 --es su_cmd INTERACTIVE --ei su_code 825807 -ei su_uid_mismatch 0 -n eu.chainfire.supersu/.NativeAccessReceiver --receiver-replace-pending --include-stopped-packages
{
"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"
}
This happens in Android 5.0 and Android 7.1.2.
When the phone hangs there are about 200 threads like this.
Could someone help me to fix it?
Thank you.

It means, there's something wrong with either your superuser permissions or SuperSU app itself.
Such broadcast messages occur, when some app tries to get superuser permissions, fails to and tries again and again. Every broadcast message like that eats a significant amount of memory (~6.8 MiB in my case). That's why, the system quickly slows down. I'm not 100% sure, but it looks like this broadcast messages don't die after reboot...
I can't provide you with reliable solution to the problem, but It would be reasonable to do the following:
Open SuperSU, Settings and try to play with Security settings like "Mount namespace separation".
Clean the memory from any broadcast messages. Use this script for that. BusyBox must be installed. To call the script, type in the root shell:
Code:
sh /path/to/the/script/clean_memory_from_supersu_objects
Reinstall SuperSU app. To do that, open SuperSU, go to Settings -> CleanUp -> Full unroot. Then, go to the custom recovery and reflash SuperSU binary again.
If the problem still persists, the only solution I see is to call the script I provided every minute or so using any automation app (I use this one for that). Or, you can change the script, if you wish. To add an infinite loop, you can wrap the script code with something like that:
Code:
while true
do
# Put entire code of the script here
sleep 60
done
Then, copy modified script into /etc/init.d and set "execute" permission to it:
Code:
cd /etc/init.d
chmod 555 clean_memory_from_supersu_objects

Two Magisk Manager Apps in system tray. One force closes, the other does not.

I'm having an issue where Magisk Manager (among other applications) have two icons in the app drawer. I think this is due to one of them being a "system app" and the other just being a normal application.
The issue I am having is that the normal Magisk application force closes upon launching, while the system app is able to open, but does not have any options for installing zips from repos.
I am using a Moto Z Play on 8.0. I've tried completely uninstalling Magisk and reinstalling but did not have luck with this. I'm not sure what I can do to fix this issue?
Thank you for any help!
Here are some screenshots showing this.
The system tray showing both apps:
{
"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"
}
The app details for the system app (I noticed this app details is not substratum themed):
The app details for the normal app (I noticed this app details is substratum themed):
The system application showing that Magisk is installed:
But the system application showing no option to install from repos:

Uninstall both apps and reinstall with the apk from the release thread, and you should be good to go.

Thank you for the reply.
I have uninstalled both installations, and installed the v5.7.0 from the release thread. Unfortunately the application force closes upon launching. I actually started this uninstall/reinstall process due to this initial issue of the Magisk Manager force closing upon launch. From my searches this is usually fixed by clearing the applications data and cache and a reboot. However, for me those steps did not work.

One thing I find odd is that it says it "keeps stopping" but the application does launch just fine...
EDIT: Let me post back with some logcat details, once I figure out how to get those

Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb

MrTissues said:
Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb
Click to expand...
Click to collapse
There's this in there:
Code:
[ 07-06 16:34:52.493 29515:29536 E/AndroidRuntime ]
FATAL EXCEPTION: Thread-2 Process: com.topjohnwu.magisk, PID: 29515
java.lang.StringIndexOutOfBoundsException: length=441; index=-1
at java.lang.String.charAt(Native Method)
at com.topjohnwu.superuser.internal.StreamGobbler.run(Unknown Source:52)
Doesn't look too good...
I would be interested in seeing your Magisk debug log. If you're not already on Magisk v16.4 beta, please install that and provide the debug log that you'll find in /data/adb. It'd probably also be a good idea to run the uninstaller first and do a clean install (from which it would be interesting to see the install log).

Thanks!
Here are the logs for uninstalling Magisk, installing Magisk 16.4 beta, and then installing f2loopback fix (necessary for Moto Z): https://paste.ee/p/A9ZXz
Here are logs from Magisk itself: https://paste.ee/p/P5iyO
The need for f2loopback is maybe troubling, though I can confirm that this did work. I know Magisk is properly doing its thing b/c I am able to get root access (confirmation dialog appears) in apps like Solid Explorer so that I can provide these logs. Its just the Manager itself that has crash issues.

I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.

MrTissues said:
I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
Click to expand...
Click to collapse
Could you provide a logcat from v5.8.0 crashing? Just to make sure that all the information collected is relevant?
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.
Click to expand...
Click to collapse
You could test by going without the f2loopback module. It wouldn't be necessary for basic Magisk functionality, and then we'd knew if it was caused by the module or not.

Based on the orange icons, you have some things installed under your work profile as well. That's why there's 2.

I've had problems Magisk disappearing on my OnePlus 5T. I've run the Uninstaller in TWRP followed by 18.1. Now have two Magisks in the add drawer: one labelled 'Magisk Manager' which says the phone is rooted and all is well; the other (same icon) is labelled simply 'Manager' and says that Magisk isn't installed! As things stand, it's just a nuisance. Everything seems to work fine with the Magisk. I'm reluctant to uninstall the 'Manager' in case in brings down the other one, but I'd love to tidy it up.
Running OOS 9.3.

@chriscross
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

[OOS 11] Fix: Enable AOD, Re-enable DC Dimming & Removing OnePlus Login Option In Settings

I've just upgraded to OOS 11 on my OP7T Pro and noticed two major things: DC dimming isn't an option anymore (might be fixed in the future) and for some reason my EU firmware shows a OnePlus account login at the top of the Settings app.
Pre-requisites for everything​Without root
Use a PC with ADB (plenty of tutorials online)
Enable ADB debugging in dev settings of your device
(tap on the OOS 11 version number multiple times to enable dev settings)
With root
Use a terminal like Terminal Emulator and paste the code line without "adb shell".
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy ​​Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/​​What it does? It first asks for root permissions ("su") and then sets a prop that tells OOS to allow the AOD setting to be shown. At the end we restart SystemUI to allow the changes to be applied.​​​
Fixing DC dimming​Variant #1
On your PC using ADB type:
Code:
adb shell
settings put system oneplus_dc_dimming_value 1
Done. To disable change "1" to "0".
What it does? It sets the variable for DC dimming to 1 (enabled) or to 0 (disabled). Variant 2 does the same thing but it is accessed by opening up a hidden panel. As both require ADB this one is quicker and easier.​
Spoiler: Variant 2 (old method)
On your PC using ADB type:
Code:
adb shell
am start-activity -a oneplus.intent.action.ONEPLUS_LAB_FEATURE_DETAILS -e oneplus_lab_feature_key oneplus_dc_dimming_value
The settings panel for DC dimming will now start on your device
Enable or disable it as you please
What it does? It starts the part of the OnePlus Lab that contains DC dimming. It is still there but for some reason it is hidden. The command will start the panel and let you enable or disable it.​
​
Removing the OnePlus "Login in to account" Option in Settings​
On your PC using ADB type:
Code:
adb shell
pm uninstall --user 0 com.oneplus.account
Close the Settings app and thank me later
What it does? It removes the culprit (the app "com.oneplus.account") from the user space. Meaning it will act as it is uninstalled for your user account. If you use multiple user accounts on one device you need to do that for each user account. It could affect other OnePlus apps like the Community app so be aware. It is never truly removed as it is a system app.​
Re-adding the app is easy. Use:
Code:
adb shell
cmd package install-existing com.oneplus.account
{
"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"
}
"Log in to account" is added sometimes. The old way was to remove the /data/india/india.img file but on OOS 11 it doesn't exist.
I'm not sure if the EU version should even contain this but it is still annoying to some as it sits above all important settings options.
Please note: I'm not responsible for anything you do to your device. You use these tutorials at your own risk. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!

Works perfectly on rooted stable OOS11 on oneplus 7T.
Thanks a bunch bruh!

How to enable phone record?

Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/

Both of these methods work perfectly on my rooted 7T with latest OOS11 stable, bugfree smooth aff. Termux and magisk is all you need. I'm grateful that I'm not among those reddit crybabies, who cry over this **** all the time and are too afraid to root their phones.
Thanks a bunch devs!

joEmonkey351 said:
Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/
Click to expand...
Click to collapse
You're supposed to flash it from magisk manager, after applying the mentioned command in Terminal manager/adb shell.

Is there really no way to get DC dimming back? I really miss that feature already

iKlutz said:
Is there really no way to get DC dimming back? I really miss that feature already
Click to expand...
Click to collapse
If you read the op it works there is just no switch

toolhas4degrees said:
If you read the op it works there is just no switch
Click to expand...
Click to collapse
Re-read the OP my man. Dc dimming is gone in latest OS11 update. Another great feature that vanished was the manual screen rotate button that would appear if you turned the screen sideways. Hopefully further updates will put them back.

Works on OP7P

Great tip for removing the Log in to Oneplus Account stuff, thanks.

Removing the OnePlus login from settings is failing for me. Rooted, oos 11.0.2
$ pm uninstall --user 0 com.oneplus.account
cmd: Failure calling service package: Failed transaction (2147483646)
edit: above failure was entering the command via Termux. Connecting to a pc via abd and entering the commands
Code:
pm uninstall --user 0 com.oneplus
and
Code:
pm uninstall --user 0 com.oneplus.account
did the trick.

I am not completely sure if this is the right place to ask but - are there a similar way to replace the leftmost screen with OnePlus Shelf instead of Google Discover. (using the ADB)
Some people have:
- toggle switch on that page to choose which one they prefer (Shelf or Google)
- (or) a setting in OnePlus Launcher where to enable the leftmost screen and also specify if you want it to be the (Shelf or Google)
What I imagine is that there should be a hidden setting which can do that, and that can be altered through ADB. Could someone please help me find it? Or share another way to make the OnePlus shelf as the leftmost screen? I am using OnePlus 8.

Is it possible to remove "Tips & Support" from the settings menu? On OOS10 this is a useless function as there is no OOS10 support anymore and nothing is displayed in this menu. Maybe there is some ADB command to remove it? I found nothing on the internet about this.

Unable to Install Modules

Rooted my phone (Galaxy S21 Ultra) recently, used Magisk, it seems to be working ok (ver. 25.1), although initially it seemed I couldn't install Modules from outside the app. I am unable to pass SafetyNet. Super User authorizations working fine.
After some helping from others and plenty of research, I installed Fox MMM and was able to install two modules. Now it seems I can't install modules from storage because the files themselves aren't being recognized as proper modules.
As you can see in this image, the icon itself is different from the ones recognized although they are all *.zip files. Safetynet and Shamiko are greyed out, while MagiskHide and Liboencrypt aren't - these two I can and did install.
Initially I thought it could be something to do with names, as the latter have underscores instead of dashes, but renaming them didn't work.
Neither Magisk nor Fox MMM recognize these files as modules, and they were all downloaded from GitHub.
I'm really stumped by this.
What could I do?
-- This is the image in the link, for easier 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"
}

If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.

NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
Where do I type this?

wbane said:
Where do I type this?
Click to expand...
Click to collapse
Any terminal emulator (to skip using the adb shell command), like Termux, OR via ADB on a PC

If someone in the future finds this thread, I've got this solution:
Have you tried using Samsung's file manager? On the top left of your screenshot press the sandwich menu icon and select Samsung's file manager and try to select the module from there.​​I tried the above and it worked!​

NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
I was stuck on Android 13 having "installation failed" message, but running this from the shell worked.

It seems like you're encountering issues with installing modules on your rooted Galaxy S21 Ultra using Magisk. Despite successfully rooting your phone and having Super User authorizations working fine, you're unable to pass SafetyNet. Additionally, you've tried installing modules from storage, but they aren't being recognized as proper modules.

fastboot devices problem

Hello everyone, I had a problem with the command fastboot devices, didnt display the serial nimber of the device, but adb devices works fine. where is the problem please
{
"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"
}

hamza19r said:
Hello everyone, I had a problem with the command fastboot devices, didnt display the serial nimber of the device, but adb devices works fine. where is the problem please View attachment 5874893
Click to expand...
Click to collapse
You have to boot to bootloader to use fastboot commands.

xunholyx said:
You have to boot to bootloader to use fastboot commands.
Click to expand...
Click to collapse
Thanks a lot for your help, I have boot it to bootloader the fastboot works fine now and I could transfer the patched image but the smartphonne not rooted yet after checking with root checker app. I have used the latest image redfine. What should I do?
Thanks a lot

hamza19r said:
Thanks a lot for your help, I have boot it to bootloader the fastboot works fine now and I could transfer the patched image but the smartphonne not rooted yet after checking with root checker app. I have used the latest image redfine. What should I do?
Thanks a lot
Click to expand...
Click to collapse
When you open the Magisk app, does it show up like this?
Installed 25.2 (25200)
Zygisk Yes
Ramdisk Yes
If so, then your phone is definitely rooted. At the bottom of the app, go to the "Superuser" tab with the shield icon. Make sure that the app you want to grant superuser has the slider set to the 'on' position.

swangjang said:
When you open the Magisk app, does it show up like this?
Installed 25.2 (25200)
Zygisk Yes
Ramdisk Yes
If so, then your phone is definitely rooted. At the bottom of the app, go to the "Superuser" tab with the shield icon. Make sure that the app you want to grant superuser has the slider set to the 'on' position.
Click to expand...
Click to collapse
Zygisk No, what should I do please

hamza19r said:
Zygisk No, what should I do please
Click to expand...
Click to collapse
Actually, if it just says "Installed 25.2 (25200)", your device should be rooted.
Zygisk can be turned on or off in the settings (top right gear icon from the home screen).
One thing you can do to really check root access is:
Download Termux and open the app. At the bottom, you will see a $ dollar sign on the left.
Type in:
su
then press the enter key
There will be a popup asking if you grant superuser access to Termux. Tap yes.
The $ sign will change to
:/data/data/com.termux/files/home #
If this happens, you definitely have root.
If this doesn't happen, open the Magisk app, go to the Superuser tab at the bottom, find Termux and turn the slider to the "on" position and try again at step 2.

swangjang said:
Actually, if it just says "Installed 25.2 (25200)", your device should be rooted.
Zygisk can be turned on or off in the settings (top right gear icon from the home screen).
One thing you can do to really check root access is:
Download Termux and open the app. At the bottom, you will see a $ dollar sign on the left.
Type in:
su
then press the enter key
There will be a popup asking if you grant superuser access to Termux. Tap yes.
The $ sign will change to
:/data/data/com.termux/files/home #
If this happens, you definitely have root.
If this doesn't happen, open the Magisk app, go to the Superuser tab at the bottom, find Termux and turn the slider to the "on" position and try again at step 2.
Click to expand...
Click to collapse
I have rooted it, thanks a lot