Bug: Problem with Android 13 / GrapheneOS - Greenify

When I would add an app and select the add button it crashes with the following error.
```
type: crash
osVersion: google/sunfish/sunfish:13/TP1A.220905.004/2022091400:user/release-keys
package: com.oasisfeng.greenify:47500
process: com.oasisfeng.greenify
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
at java.util.concurrent.FutureTask.run(FutureTask.java:269)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.SecurityException: Permission Denial: getUidProcessState from com.oasisfeng.greenify asks to run as user 11 but is calling from uid u0a242; this requires android.permission.INTERACT_ACROSS_USERS_FULL
at android.os.Parcel.createExceptionOrNull(Parcel.java:3012)
at android.os.Parcel.createException(Parcel.java:2996)
at android.os.Parcel.readException(Parcel.java:2979)
at android.os.Parcel.readException(Parcel.java:2921)
at android.app.IActivityManager$Stub$Proxy.getUidProcessState(IActivityManager.java:4838)
at android.app.ActivityManager.getUidImportance(ActivityManager.java:3792)
at java.lang.reflect.Method.invoke(Native Method)
at lq1$c0.a(SourceFile:1)
at lq1$e0.a(SourceFile:3)
at lq1$k.a(SourceFile:2)
at df1.a(SourceFile:164)
at df1.a(SourceFile:113)
at na1.a(SourceFile:5)
at oa1$e.doInBackground(SourceFile:2)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
... 4 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.am.UserController.handleIncomingUser(UserController.java:2243)
at com.android.server.am.ActivityManagerService.getUidProcessState(ActivityManagerService.java:7340)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2060)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2641)
at android.os.Binder.execTransactInternal(Binder.java:1302)
```

I think you'll find active support on the GrapheneOS Element chat. The people there have been very helpful for me in the past.
GrapheneOS contact information
Contact information for GrapheneOS.
grapheneos.org

hopeless.unknown said:
Caused by: java.lang.SecurityException: Permission Denial: getUidProcessState from com.oasisfeng.greenify asks to run as user 11 but is calling from uid u0a242; this requires android.permission.INTERACT_ACROSS_USERS_FULL
Click to expand...
Click to collapse
User 11 is related to your work profile. You may be using Island/Insular and Greenify tries to access the state of a process belonging to that work profile user. But it lacks the necessary permission INTERACT_ACROSS_USERS_FULL.
You can try to grant it via ADB:
Code:
pm grant om.oasisfeng.greenify android.permission.INTERACT_ACROSS_USERS_FULL

4ndr0x said:
User 11 is related to your work profile. You may be using Island/Insular and Greenify tries to access the state of a process belonging to that work profile user. But it lacks the necessary permission INTERACT_ACROSS_USERS_FULL.
You can try to grant it via ADB:
Code:
pm grant om.oasisfeng.greenify android.permission.INTERACT_ACROSS_USERS_FULL
Click to expand...
Click to collapse
Thanks @4ndr0x for your answer. I tried the adb command, but I got only the following message:
Exception occurred while executing 'grant':
java.lang.SecurityException: Permission android.permission.INTERACT_ACROSS_USERS_FULL is managed by role
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1390)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1321)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:547)
at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:602)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2546)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:292)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:5959)
at android.os.Binder.shellCommand(Binder.java:1058)
at android.os.Binder.onTransact(Binder.java:886)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4397)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:5943)
at android.os.Binder.execTransactInternal(Binder.java:1307)
at android.os.Binder.execTransact(Binder.java:1265)
Click to expand...
Click to collapse

Related

[HELP] Bind to com.android.music service from my app

Hello!
Like in title... I am developing my app which should to use Android Native Media Player (android.com.htc.music). I found information, how to do it: http://www.adityatalpade.com/2010/07/31/how-to-bind-to-services-from-the-android-source/. Everything is fine, because I can bind to service, but I can use it. Always I have exception: java.lang.RuntimeException: java.lang.SecurityException: Binder invocation to an incorrect interface.
Full exception is: http://android.pastebin.com/Xj7WpiJ3.
I will be appreciate for advice, how to resolve this problem.
gmadajczak said:
Hello!
Like in title... I am developing my app which should to use Android Native Media Player (android.com.htc.music). I found information, how to do it: http://www.adityatalpade.com/2010/07/31/how-to-bind-to-services-from-the-android-source/. Everything is fine, because I can bind to service, but I can use it. Always I have exception: java.lang.RuntimeException: java.lang.SecurityException: Binder invocation to an incorrect interface.
Full exception is: http://android.pastebin.com/Xj7WpiJ3.
I will be appreciate for advice, how to resolve this problem.
Click to expand...
Click to collapse
that is because it is com.android.music
Jr33 said:
that is because it is com.android.music
Click to expand...
Click to collapse
OK... Could you elaborate a little more on that, please?
I know that is from com.android.music package, but according to article, which I mentioned in previous message - it should work.

Is there a way to root new OTA 45.4.13.MB855?

Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
I want to add that I was rooted before applying the OTA.
stevetrooper said:
Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
Click to expand...
Click to collapse
Wait, what? Even photon-torpedo didn't work?
any updated status with this yet?
I'm curious too...
Please keep us apprised and a system dump would be helpful from someone who has the update.
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Wait, what? Even photon-torpedo didn't work?
Click to expand...
Click to collapse
Nope, tried it multiple times.
Torpedo worked for me this evening.
Sent from my MB855 using Tapatalk 2
Torpedo worked for me, AIO did not.
I still laugh when ppl are still using the AIO root when its been so unreliable in the past. The photon-torpedo method has ALWAYS worked and I don't know why people aren't using the torpedo method to root by default.
OP you must be doing something wrong because the torpedo method still works any many folks have confirmed that.
Glad to hear its still working, here is the error I get:
$ ./photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
./photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
Then looking at the log:
$ cat /var/log/Xorg.0.log
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
(WW) xf86OpenConsole: VT_GETSTATE failed: Bad file descriptor
ddxSigGiveUp: Closing log
following for further developments..
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
stevetrooper said:
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
Click to expand...
Click to collapse
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
ericdabbs said:
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
Click to expand...
Click to collapse
Unfortunately the script does not give me the # prompt. So when you run the install-su script it fails. I found others that had the same problem and they never figured out how to get it to work.
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
ddxSigGiveUp: Closing log
$ ./install-su.sh Usage: mount [-r] [-w] [-o options] [-t type] device directory cp: /system/bin/su: Read-only file system Unable to chmod /system/bin/su: Read-only file system Usage: mount [-r] [-w] [-o options] [-t type] device directory rm failed for /lib/libphoton-torpedo.so, Permission denied.
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
stevetrooper said:
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
Click to expand...
Click to collapse
Do you have the right drivers? i.e. - do other adb commands work?
willysp said:
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
Do you have the right drivers? i.e. - do other adb commands work?
Click to expand...
Click to collapse
I downloaded the drivers from the photon torpedo thread. adb works just fine, can push the file to the photon, without any errors. I even tried adb on 2 different computers, Windows XP and the other Windows 7.
The photon-torpedo.sh is very simple:
#!/bin/bash
umask 0
LD_AUDIT="libpcprofile.so" PCPROFILE_OUTPUT="/lib/libphoton-torpedo.so" /usr/bin/X
cat /data/tmp/libphoton-torpedo.so > /lib/libphoton-torpedo.so
LD_AUDIT="libphoton-torpedo.so" /usr/bin/X
When I look in /lib the file libphoton-torpedo.so exists and has a timestamp from when I ran, so its catting the file correctly.
I don't get the # prompt, so running install-su.sh does not work.
Found this in the photon-torpedo thread in Development:
Sparky_McBurning said:
I figured out the problem and a fix.
Problem:
If /lib/libphoton-torpedo.so was not removed from /lib before the OTA update, the permissions are updated to no longer be over-writable, so the /data/tmp/photon-torpedo.sh step that 'cat's libphoton-torpedo cannot re-write the file with new permissions.
Fix:
Update photon-torpedo.sh to use a different filename for libphoton-torpedo.so. I used libphoton-torpedo2.so. No problems. Just make sure you remove any versions of libphoton-torpedo.so from /lib/ after rooting, and you won't have this problem in the future.
Click to expand...
Click to collapse

LineageOS update caused permission erros for GApps

Hello together,
I recently made an update of LineageOS for my LG G5 (LineageOS 14.1) as well as my Samsung Galaxy S5 (LineageOS 15.1). They both seem to have serious issues afterwards and I don't know what happened. I assume something has changed within the last month or so and my problem appears with both devices.
It appears as if the permissions for all GApps have changed (or the uids perhaps). All other apps work perfectly fine so far. I also downloaded the latest GApps and installed them via TWRP but that doesn't seem to solve any problem. However I'm not sure that overwrites the old applications or only installs currently not installed ones.
So when ever I use one of these apps (Gmail, Playstore, Maps, some of the system processes), it always crashes and I see the log messages looking like this:
Code:
com.google.android.gms.persistent, PID: 13071
java.lang.RuntimeException: Unable to create application
com.google.android.gms.common.app.GmsApplication:
java.lang.SecurityException: addOnPermissionsChangeListener:
Neither user 10039 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5451)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1564)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
or
Code:
java.lang.SecurityException: Permission Denial: opening provider
com.google.android.gsf.gservices.GservicesProvider from
ProcessRecord{22a7d3b 23968:com.google.android.youtube/u0a108}
(pid=23968, uid=10108) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
at android.os.Parcel.readException(Parcel.java:1684)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4199)
or
Code:
java.lang.SecurityException: tname=Sensors - Permission Denial: opening provider com.google.android.gsf.gservices.GservicesProvider from ProcessRecord{3745b29 6048:com.google.android.apps.maps/u0a179} (pid=6048, uid=10179) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
They all have in common that they tell me that "Neither user [???] nor current process has android.permission.[???] "
It seems to work uninstalling the specific app and reinstalling it. However this is a lot of work and isn't really easy for some apps that are closer to the system.
So what can I do? What exactly is the problem here? Did the UIDs change? Any suggestions please!

Greenify on Non root phone

Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
exodius48 said:
Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
Click to expand...
Click to collapse
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
tnsmani said:
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
Click to expand...
Click to collapse
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
exodius48 said:
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
Click to expand...
Click to collapse
Good plan. Greenify really isn't needed on your device/rom.
When you run ADB on the computer make sure the CMD (the black window) is running As Administrator.
It really is worth it to run these ADB commands on a Non-Rooted device, Greenify works great.
I have an OPPO K5 - China domestic version. When I tried to grant permission to GSAM I also had the same long error message. Then I discovered further down the Developer Options menu, there's a tab called "Disable Permission Monitoring", I switched it on and the adb command worked without the long error message. Not sure if MIUI has a similar tab though.
exodius48 said:
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Click to expand...
Click to collapse
Hi.
Link is broken. Any tutorial copy to post here?
Regards.

Error: couldn't create User

Hello, I am getting the following error on a rooted android 9 device.
Code:
# pm create-user youser
Error: couldn't create User.
On the other hand, logcat displays the following message.
Code:
W UserManagerService: Cannot add user. no_add_user is enabled.
Is there a way to disable no_add_user ?
Tortux4e said:
Hello, I am getting the following error on a rooted android 9 device.
Code:
# pm create-user youser
Error: couldn't create User.
On the other hand, logcat displays the following message.
Code:
W UserManagerService: Cannot add user. no_add_user is enabled.
Is there a way to disable no_add_user ?
Click to expand...
Click to collapse
Have a look here:
https://developer.android.com/reference/android/os/UserManager#DISALLOW_ADD_USER
And here:
https://developer.android.com/refer...roid.content.ComponentName, java.lang.String)
On some devices, it may not work to remove the restriction to add users. Needs to be a multi-user system which is not managed by an organisation.

Categories

Resources