bug:set ro.debuggable success,but ddms do not show all processes about magiskhidepropsconf HOT 8 CLOSED

Not sure what that could be about...

Are you using the "Edit MagiskHide props" option or "Add/edit custom props"?

from magiskhidepropsconf.

Not sure what that could be about...

Are you using the "Edit MagiskHide props" option or "Add/edit custom props"?

I am using the "Edit MagiskHide props"

from magiskhidepropsconf.

Could you run a few tests for me?

1. Edit /data/adb/modules/MagiskHidePropsConf/service.sh line 105 and remove the n from resetprop -nv. Then reboot and see if there's any difference.
2. Use the "Add/edit custom props" option instead, and test all three boot stages one by one and let me know if any of them work as expected.

from magiskhidepropsconf.

Could you run a few tests for me?

1. Edit /data/adb/modules/MagiskHidePropsConf/service.sh line 105 and remove the n from resetprop -nv. Then reboot and see if there's any difference.
2. Use the "Add/edit custom props" option instead, and test all three boot stages one by one and let me know if any of them work as expected.

Success. I do as fallow:

1. change service.sh line 102 resetprop -nv to resetprop -v ,reboot but no difference.
2. reset MagiskHide props ,Use the "Add/edit custom props" option instead, add ro.debuggable=1,then select 4 - both boot stages (current),then reboot and I find DDMS show all processes.
3. change service.sh line 102 resetprop -v to resetprop -nv ,reboot but no difference.
   so, Use the Add/edit custom props is success, resetprop -v or resetprop -nv seems no difference.

thanks a lot.

from magiskhidepropsconf.

Success. I do as fallow:

1. change service.sh line 102 resetprop -nv to resetprop -v ,reboot but no difference.
2. reset MagiskHide props ,Use the "Add/edit custom props" option instead, add ro.debuggable=1,then select 4 - both boot stages (current),then reboot and I find DDMS show all processes.
3. change service.sh line 102 resetprop -v to resetprop -nv ,reboot but no difference.
   so, Use the Add/edit custom props is success, resetprop -v or resetprop -nv seems no difference.

thanks a lot.

Could you test what happens if you use the custom prop option and set boot stage to late_start service?

from magiskhidepropsconf.

use the custom prop option,boot stage test :
1.set late_start service,ddms show no process.
2.set post-fs-data,ddms show all processes.
3.set default,ddms show no processes.

by the way , reboot devices and execute props show error:

 The service.sh module script does not
 appear to have run during boot.

 This means the module won't work.

 Please reboot your device and see if
 it does run.

 Things to try:
 Disable EdXposed.
 Change boot stage settings or background
 execution for the boot script
 (run the props
 command with the -s option).

 If the issue persists after a reboot,
 please report the issue, with logs!

 Logs have automatically been saved
 to your internal storage
 (propslogs.tar.gz).

 If the automatic collection failed,
 please collect the logs manually.

the log file :
propslogs.tar.gz

from magiskhidepropsconf.

Ok, thank you for testing. I might add a stop;start; to the "Edit MagiskHide props" function...

The service.sh script doesn't finish and that's why you're seeing that error. Possibly caused by EdXposed.

from magiskhidepropsconf.

Probably fixed in 13a72e0

from magiskhidepropsconf.