Same here with the change from XA2 to 10 III.
It might be out of memory eventually, but same same happens on my XA2 since… 4.3? 4.4? It is a regression, and it really seems triggered by the use of GNSS in Android apps, and not low memory to begin with. And it’s one of those bugs which make me wonder why it isn’t long hotfixed, given the incidence and effect.
Yeah I might upgrade to X10 V eventually, although I realy dislike the long form factor of those new sonys. Still “upgrade your hardware” as a a fix for a software bug is… not nice.
Hi I tried but something went wrong:
appsupport-attach sh
lxc-attach: aliendalvik: terminal.c: lxc_terminal_create_native: 927 Not a directory - Failed to open termina
l multiplexer device
lxc-attach: aliendalvik: af_unix.c: lxc_abstract_unix_recv_fds_iov: 318 Invalid argument - Received no file d
escriptors
lxc-attach: aliendalvik: commands.c: lxc_cmd_rsp_recv_fds: 129 Failed to receive file descriptors
lxc-attach: aliendalvik: af_unix.c: lxc_abstract_unix_recv_fds_iov: 318 Invalid argument - Received no file d
escriptors
lxc-attach: aliendalvik: commands.c: lxc_cmd_rsp_recv_fds: 129 Failed to receive file descriptors
#
Post your phone model, too.
Y’all are doing devel-su before trying to attach appsupport, right?
Yes, devel-su, than
"[root@Xperia10III defaultuser]# appsupport-attach sh
lxc-attach: aliendalvik: terminal.c: lxc_terminal_create_native: 927 Not a directory - Failed to open terminal multiplexer device
lxc-attach: aliendalvik: af_unix.c: lxc_abstract_unix_recv_fds_iov: 318 Invalid argument - Received no file descriptors
lxc-attach: aliendalvik: commands.c: lxc_cmd_rsp_recv_fds: 129 Failed to receive file descriptors
lxc-attach: aliendalvik: af_unix.c: lxc_abstract_unix_recv_fds_iov: 318 Invalid argument - Received no file descriptors
lxc-attach: aliendalvik: commands.c: lxc_cmd_rsp_recv_fds: 129 Failed to receive file descriptors
#"
Then if try
" # pm grant com.google.android.gms android.permission.COARSE_LOCATION
Exception occurred while executing ‘grant’:
java.lang.IllegalArgumentException: Unknown permission: android.permission.COARSE_LOCATION
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1588)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManager Service.java:1547)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2287)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:249)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21719)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4603)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4307)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
255|:/ #"
App support is running. Micro g uninstalled. Gapps installed with play store.
My device is xperia 10 III with sfos 4.5.0.25.
I don’t know what this is about, never seen.
Could someone help me with dealibg with appsupport. Obviously I have issues with it. I couldn’t find some other cases in the forum. Maybe I should make new thread or ask zendesk for support…
I think the correct permission would be android.permission.ACCESS_COARSE_LOCATION. Or not. At least that permission exists while android.permission.COARSE_LOCATION does not.
2 Likes
Thank you very much for your comment. Everything is fine now.