Hi,
i'm trying to install few apps on Fujitsu Arrows F-03L (Android 8.1 Oreo). Most of them are requiring Google Services which is also not pre-installed on the phone. The most recent versions of Google Play Services are just crushing, so i've ended up with 14.5.82 (040400-222134188) build, and the older ones are saying that Play Services should be updated. Play Services require Services Framework, so i've installed 8.1.0-4487743 build.
The apps (Youtube) however are still failing to start. I can see the error in logs, but do not know how to fix it:
Code:
11-22 12:05:19.091 2391 2391 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: addOnPermissionsChangeListener: Neither user 10103 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5920)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.-wrap1(Unknown Source:0)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1699)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6680)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:467)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:821)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: Caused by: java.lang.SecurityException: addOnPermissionsChangeListener: Neither user 10103 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2013)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1959)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.addOnPermissionsChangeListener(IPackageManager.java:6145)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ApplicationPackageManager.addOnPermissionsChangeListener(ApplicationPackageManager.java:1442)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at qkz.a(:[email protected]@14.5.82 (040400-222134188):12)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.google.android.gms.common.app.GmsApplication.onCreate(:[email protected]@14.5.82 (040400-222134188):49)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1120)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5917)
I wonder if anyone has positive (or any) experience with these phones? E.g. rooting/custom builds/installing gapps... any help appreciated.
Hi,
I have the same phone as you. I feel like not a single soul is using it except me bruh. I only found this page about it, and even there is no answers... Do you still use it? The version of Play Services you installed is already kinda old and is asking for an update. Did you managed to find a new one that works? Maybe working Play Store? Or just anything that could help me with this phone, working gapps, root, way to have a cursor on the screen, bc the navigation it has doesn't allow me to even register in a lot of apps i need like Telegram or Whatsapp, maybe just working versions of that apps. Anything will help..
Hi mate, i've abandoned the idea of using this phone as an Android device - i couldn't make it work with Play Store/Gapps, and without them it's pretty useless - i can't even sync my contacts. It's a shame cause i love both the form-factor and build quality of this device.
Oh well, thanks for answering. Good to know you're still on that forum. I still do not leave hopes to switch to it as the main device, tho. Fortunately, I don’t need G-Services so much (besides, they may be banned from us so soon), and with the rest of the necessary applications, I got used to working and configuring them through emulation of clicks through adb. With all the cons and inconveniences, I like it, it has everything i need for now, like messengers, browser and some specific android apps. I bought it for a digital detox. But still, if i wasn't so stubborn in my desire to use it, i wouldn't even try after a couple of unsuccessful attempts. There must be a line between stripped down functionality and simple disrespect and limitation of important functions. It's very sad that they ruined such a great smartphone (and the form factor in general)
Related
I've noticed that multiple people, including myself, have had multiple issues with random reboots on various ICS roms. Well it was driving me crazy, so I decided to catch it in the act. Please see this from my logcat:
Code:
04-18 17:04:36.799 E AlarmManagerService: android_server_AlarmManagerService_set to type=2, 115438.634000000
04-18 17:04:36.799 V AlarmManager: trigger WAKEUP Alarm{41c5fcd8 type 2 android}
04-18 17:04:36.809 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x40c231f8)
04-18 17:04:36.809 E android.os.Debug: [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_sys_error
04-18 17:04:36.809 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
04-18 17:04:36.809 E AndroidRuntime: java.lang.NoSuchMethodError: com.android.server.WimaxService.access$1002
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.WimaxService$4.onReceive(WimaxService.java:1150)
04-18 17:04:36.809 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:728)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:605)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:92)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.ServerThread.run(SystemServer.java:986)
04-18 17:04:36.834 I dumpstate: Check if stand-alone
04-18 17:04:36.859 I dumpstate: begin
I went back through several saved logcats after these reboots, and the signature looks the same. It looks to me as if the WiMax service (WimaxService.java) is calling an invalid method (com.android.server.WimaxService.access$1002), and causing android server to crash with a FATAL exception.
Now, I'm not a programmer, but does anyone have any ideas on how we can investigate the code and see if we can make a workaround? Thoughts anyone? I'll keep at this.
I'm not a program either, but I know Team Nocturnal had this same issue on a couple of their ROMs and Mijjah was working on it. Not sure if he has any logs of it happening.
I do know he's working on an AOKP rom as well, which I'm using, and I haven't had the issue yet.
Maybe post this in the dev thread of the rom you are using. I think we can all benefit from this Im sick of my phone rebooting while using 4g!!
Hello everyone,
I'm having problems trying to figure it out what's happening with my HTC One M9. Right now the phone is
S-OFF
Software status: modified
Bootloader unlocked
It's running latest software 3.35.401.12. Upgraded via official OTA from 1.32.401.8 (flashed using link found here).
The problem I have right now is that when I reboot in download mode and chose hardware information the CPU appears unknown and some other weird stuff. Quote:
LCD: HIME FHD Tianma/Renesas video mode dsi panel?
CPU: UNKNOWN
CPU rev: 2.1
DDR: 00000001, 3GB
cx voltage Error
mx voltage Error
No CPU param
RFG_3: Error
CRADIO: N/A
The phone works properly most of the times, but after every some time (might be month or even 2 days) it reboots itself and then is unusable unless I do a factory reset. After the "fatal" reboot I was able to pull logs and they were full with stuff like this:
HTML:
07-13 16:33:43.069 22059 22059 E AndroidRuntime: FATAL EXCEPTION: main
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Process: com.google.process.gapps, PID: 22059
07-13 16:33:43.069 22059 22059 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2824)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.access$1800(ActivityThread.java:150)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1484)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Looper.loop(Looper.java:168)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5845)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:360)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:254)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:163)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.a.a(SourceFile:43)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.c.a(SourceFile:175)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.b.a(SourceFile:213)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter.onReceive(SourceFile:246)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2810)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: ... 8 more
07-13 16:33:43.684 22098 22098 E AndroidRuntime: FATAL EXCEPTION: main
I got the phone SH with Viper ROM on it. It had issues related to WiFi hardware and also random reboots (but after reboot everything worked). Then I tried to back to stock rom/firmware and the phone worked for ~ 3-4 months. Then it did the reboot happened, I did a factory reset, and worked again for ~ 2 days.
Any ideas how I can fix/debug this? Or can it that my MID and CID are completely wrong and I need a different ROM?
mid: 0PJA10000
cid: HTC__102
Did you flash twrp too?. Which version twrp do you have, which version supersu?.
A LOT of sqlite issues there, could be related rather than responsible..
Beamed in by telepathy.
I don't have TWRP and no root. I try to keep my phones as stock as possible since I don't need that stuff. The error log is after the "reboot" happened. The events succeeded as following
reboot (out of the blue)
reboot loop for a while
I'm not sure, but I think I was able to clear the cache from bootloader/recovery
phone started by I had a lot of issues (Google Apps keep crashing)
fetched the log (posted above)
So I also think the logs are more like the effect of the problem. I wasn't able to fetch the kernel logs (I saw that you can usually ready what caused a kernel panic), but since was happening twice now, I expect it to happen again. That's why I want to be prepared and try to get as much information as I need.
Another theory is that NAND is broken, and the phone works until it gets to write in a bad block. But I don't know how to properly test that.
BTW: the phone is my backup phone. So I can do a lot of test with it for the next few days without worrying about data.
Sorry for the double post, but I don't want to create another topic for this. I tried to make a nandroid backup today, but without flashing twrp
Code:
fastboot boot twrp-2.8.7.0-hima.img
I selected all partitions, except cache, but this happened (see link to "screenshot" below). Is it normal? Does it mean anything? I mounted system as "read-only".
i.imgur.com/RQsbxzT.jpg (apparently I'm not allowed to post links, so you have to copy/paste this)
Hello techy people,
I have bought XA2, unlocked bootloader and installed latest LOS 15 (30 Nov build). Installed Magisk, MicroG, Afwall, all worked well and today random reboots started to happen. Sometimes it happens when I play with location settings in maps app, sometimes when I use the messenger. I did a few logcats and all of them have the following bit:
12-02 39.242 12603 12689 D ConnectivityService: handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 100]
12-02 39.258 12449 12488 W IptablesRestoreController: iptables-restore process 12453 terminated status=256
12-02 39.262 12449 12488 E Netd : failed to change iptables rule that sets incoming packet mark
12-02 39.262 12449 12488 E Netd : failed to change permission on interface rmnet_data0 of netId 100 from 0 to 1
12-02 39.266 12603 12689 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityServiceThread
12-02 39.266 12603 12689 E AndroidRuntime: java.lang.IllegalStateException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2707)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.updateCapabilities(ConnectivityService.java:4708)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.handleLingerComplete(ConnectivityService.java:4879)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.-wrap9(Unknown Source:0)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.maybeHandleNetworkAgentInfoMessage(ConnectivityService.java:2213)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.handleMessage(ConnectivityService.java:2225)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.internal.util.WakeupMessage.onAlarm(WakeupMessage.java:111)
12-02 39.266 12603 12689 E AndroidRuntime: at android.app.AlarmManager$ListenerWrapper.run(AlarmManager.java:243)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
12-02 39.266 12603 12689 E AndroidRuntime: Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:505)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:401)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:396)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2702)
12-02 39.266 12603 12689 E AndroidRuntime: ... 12 more
12-02 39.284 12603 12689 I Process : Sending signal. PID: 12603 SIG: 9
12-02 39.440 889 889 I adbd : Framework disconnect
12-02 39.445 859 859 I lowmemorykiller: ActivityManager disconnected
12-02 39.445 859 859 I lowmemorykiller: Closing Activity Manager data connection
12-02 39.446 924 924 E LocSvc_GnssInterface: serviceDied] service died. cookie: 0, who: 0x70de233c20
12-02 39.447 924 924 E LocSvc_APIClientBase: locAPIStopTracking:339] invalid session: 0.
12-02 39.447 924 924 E GnssHal_GnssGeofencing: serviceDied] service died. cookie: 0, who: 0x70de233fe0
12-02 39.447 924 924 E LocSvc_GnssNiInterface: serviceDied] service died. cookie: 0, who: 0x70de2b3020
12-02 39.451 12727 12744 W Sensors : sensorservice died [0x722207c3e0]
12-02 39.451 598 598 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x750ae5f000
12-02 39.451 575 575 I ServiceManager: service 'launcherapps' died
12-02 39.452 14342 14420 W Sensors : sensorservice died [0xe6b374c0]
12-02 39.452 575 575 I ServiceManager: service 'media_projection' died
12-02 39.452 575 575 I ServiceManager: service 'media.camera.proxy' died
12-02 39.453 575 575 I ServiceManager: service 'autofill' died
12-02 39.453 575 575 I ServiceManager: service 'imms' died
12-02 39.453 575 575 I ServiceManager: service 'profile' died
12-02 39.454 575 575 I ServiceManager: service 'usb' died
12-02 39.454 575 575 I ServiceManager: service 'serial' died
12-02 39.455 575 575 I ServiceManager: service 'hardware_properties' died
12-02 39.457 12445 12445 E Zygote : Exit zygote because system server (12603) has terminated
Click to expand...
Click to collapse
I understand that bootloops are caused by setPermissionForNetworks() but not sure how to fix it.
Any help would be appreciated.
All sorted, many thanks
pupsidze said:
All sorted, many thanks
Click to expand...
Click to collapse
How did you fix it?
I've unlocked the bootloader and rooted my OP11 (CPH2449GDRP), and when I try to set up any screen lock mechanism, it doesn't save it, but rather stops at the repeated input step and does nothing.
In ADB logcat, I can see that there's a crash happening when trying to setup any screen lock mechanism.
Spoiler: ADB Logcat
Code:
--------- beginning of crash
02-15 18:06:00.408 5591 19164 E AndroidRuntime: FATAL EXCEPTION: SET2T7cached
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Process: com.android.settings, PID: 5591
02-15 18:06:00.408 5591 19164 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:269)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3048)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3024)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3007)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2949)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1225)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:727)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.oplus.settings.feature.password.SaveLockPatternAndFinishWorker.F1(SaveLockPatternAndFinishWorker.java:9)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.a(SaveChosenLockWorkerBase.java:2)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.doInBackground(SaveChosenLockWorkerBase.java:1)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:264)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: ... 3 more
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:841)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2961)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1910)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1821)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:580)
02-15 18:06:00.408 5591 19164 E AndroidRuntime:
Any idea how to fix this issue? I've recently updated from A.06 to A.07 firmware (by patching init_boot.img into inactive slot) but issue still persists. Thanks!
I have the exact same issue, it does not matter if I pick pin or pattern.
CoinsClassic said:
I've unlocked the bootloader and rooted my OP11 (CPH2449GDRP), and when I try to set up any screen lock mechanism, it doesn't save it, but rather stops at the repeated input step and does nothing.
In ADB logcat, I can see that there's a crash happening when trying to setup any screen lock mechanism.
Spoiler: ADB Logcat
Code:
--------- beginning of crash
02-15 18:06:00.408 5591 19164 E AndroidRuntime: FATAL EXCEPTION: SET2T7cached
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Process: com.android.settings, PID: 5591
02-15 18:06:00.408 5591 19164 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:269)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3048)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3024)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3007)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2949)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1225)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:727)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.oplus.settings.feature.password.SaveLockPatternAndFinishWorker.F1(SaveLockPatternAndFinishWorker.java:9)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.a(SaveChosenLockWorkerBase.java:2)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.doInBackground(SaveChosenLockWorkerBase.java:1)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:264)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: ... 3 more
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:841)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2961)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1910)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1821)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:580)
02-15 18:06:00.408 5591 19164 E AndroidRuntime:
Any idea how to fix this issue? I've recently updated from A.06 to A.07 firmware (by patching init_boot.img into inactive slot) but issue still persists. Thanks!
Click to expand...
Click to collapse
rootet with magisk or magisk delta ? (stock , beta or canary )
ChrisFeiveel84 said:
rootet with magisk or magisk delta ? (stock , beta or canary )
Click to expand...
Click to collapse
Latest Canary of official Magisk
CoinsClassic said:
Latest Canary of official Magisk
Click to expand...
Click to collapse
does the problem only occur with root or also without root?
ChrisFeiveel84 said:
does the problem only occur with root or also without root?
Click to expand...
Click to collapse
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.
CoinsClassic said:
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.
Click to expand...
Click to collapse
Since I don't have my op11 yet (I'm not toying with the idea of unlocking the bootloader either), the best option is to ask the telegram group about something like this, as there are more people there who deal with the op11 and co
OnePlus Chat [EN/ZH]
Discussion Group / 讨论群: https://t.me/OnePlusChat System Update / 系统更新: https://t.me/OnePlusOTA Resources Center / 资源中心: http://t.me/OnePlusRes
t.me
ChrisFeiveel84 said:
does the problem only occur with root or also without
Click to expand...
Click to collapse
CoinsClassic said:
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.
Click to expand...
Click to collapse
Mine worked before rooting. I set my fingerprint then unlocked the boot loader. Now it doesnt work.
I just reset my phone and it still does not work with the bootloader unlocked. I am actually sending the phone back and buying a oneplus 10 pro. After using the phone for the day I cannot stand the usb 2.0 tranfer speeds. I tried using wifi transfers but it is still not as fast as I would like. I make a lot of youtube videos so most times I am transfering 16gb - 30gb files and over usb it was taking forever. So, hopefully by friday I will have a new phone. Its sad, I figured going from a oneplus 9 pro it would have been a huge upgrade. I do not know why they send a type c to usb A 3.0 adapter with the phone if it is only capable of 2.0 speeds.
This happened to me right after unlocking bootloader. GOOD NEWS: I fixed it by locking and re-unlocking the bootloader. I then immediately set my password during setup and it worked fine. Face unlock and fingerprint also work perfect.
Edit: someone also said that it may not be a set thing, so maybe if that doesnt work try re-locking and unlocking again.
I know that this is a pain, but it should be a one time thing. I have not rooted yet but will do so soon.
JPower123 said:
This happened to me right after unlocking bootloader. GOOD NEWS: I fixed it by locking and re-unlocking the bootloader. I then immediately set my password during setup and it worked fine. Face unlock and fingerprint also work perfect.
Edit: someone also said that it may not be a set thing, so maybe if that doesnt work try re-locking and unlocking again.
I know that this is a pain, but it should be a one time thing. I have not rooted yet but will do so soon.
Click to expand...
Click to collapse
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.
cavalier3400z said:
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.
Click to expand...
Click to collapse
Are you using fastboot commands? I don't think adb Is supposed to detect it in bootloader. Also have you flashed any roms?
I have same issue on EU OP11 with firmware CPH2449_11_A.07.
Unlocked bootloader - fine.
Booted into OOS but cant set a lock password/code, just sits there with no error. I can skip that and get into the OS OK.
I tried a factory reset in OOS, no change.
I then tried a format in recovery, no change.
Relocked the bootloader and now I can set a lock password/code.
At no point had I flashed anything for root access. Very unusual.
Yep. Same issue here. Europe OP11 firmware CPH2449_11_A.07. Cannot set the lock screen password/pin/pattern I did skip it. Cannot set fingerprint or anything because of that.
cavalier3400z said:
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.
Click to expand...
Click to collapse
Are you on full unrooted stock before locking? Do not know how oppo works, but if you were not on stock, I think you ahve to somehow recover thru edl, or maybe ur device is paper weight (If you were not on 100% stock)
gahffi said:
Yep. Same issue here. Europe OP11 firmware CPH2449_11_A.07. Cannot set the lock screen password/pin/pattern I did skip it. Cannot set fingerprint or anything because of that.
Click to expand...
Click to collapse
grim00 said:
I have same issue on EU OP11 with firmware CPH2449_11_A.07.
Unlocked bootloader - fine.
Booted into OOS but cant set a lock password/code, just sits there with no error. I can skip that and get into the OS OK.
I tried a factory reset in OOS, no change.
I then tried a format in recovery, no change.
Relocked the bootloader and now I can set a lock password/code.
At no point had I flashed anything for root access. Very unusual.
Click to expand...
Click to collapse
But the massacre with this model:/
Did you do something else or just unlocked a bootloader?
Arealhooman said:
Are you on full unrooted stock before locking? Do not know how oppo works, but if you were not on stock, I think you ahve to somehow recover thru edl, or maybe ur device is paper weight (If you were not on 100% stock)
Click to expand...
Click to collapse
How can they do anything at EDL, since there is no msmdownload for OP11?
regards
f.
qriozum said:
But the massacre with this model:/
Did you do something else or just unlocked a bootloader?
Click to expand...
Click to collapse
Problem started with just the unlocked bootloader. Not even rooted yet.
gahffi said:
Problem started with just the unlocked bootloader. Not even rooted yet.
Click to expand...
Click to collapse
Here in several threads there were so many attempts to restore OP11 that I already mix it all.
I am not sure if the accident @ChrisFeiveel84 has not shared the video as he removes the "cow" partitions and performs something else.
Maybe it will help?
In the thread with the conversion of the Chinese version OP11 at 2447/2449 there was also a problem with the pin/screen lock - but they probably solved it.
I can confirm:
Relock and Unlock bootloader a few times (3 cycles in my case) eventually allows lock screen security to be set with an unlocked bootloader.
Here is the log that caused the restart
04-05 09:33:57.788 31933 31977 E AndroidRuntime: FATAL EXCEPTION: pool-5-thread-1
04-05 09:33:57.788 31933 31977 E AndroidRuntime: Process: com.shannon.imsservice, PID: 31933
04-05 09:33:57.788 31933 31977 E AndroidRuntime: java.lang.RuntimeException: failed to set system property (check logcat for reason)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at android.os.SystemProperties.native_set(Native Method)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:235)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.setCallWaitingSyncProperty(ImsUt.java:1393)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.lambda$refreshCallWaiting$28(ImsUt.java:1211)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.$r8$lambda$A880XJDdCNHXPHCDkqclCeZT2U8(Unknown Source:0)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt$$ExternalSyntheticLambda22.execute(Unknown Source:6)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.runStoredUtRequest(ImsUt.java:999)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.runNewUtRequest(ImsUt.java:946)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.executeIfAvailable(ImsUt.java:940)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.executeIfAvailable(ImsUt.java:933)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.refreshCallWaiting(ImsUt.java:1201)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.lambda$refreshCallWaitingAsync$27(ImsUt.java:1155)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.$r8$lambda$V3-4-1Ak7OCWx7C1l3QhRu_06mA(Unknown Source:0)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt$$ExternalSyntheticLambda15.run(Unknown Source:4)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
04-05 09:33:57.788 523 565 D display : setActiveConfigWithConstraints:: PrimaryDisplay config(36) test(0)
04-05 09:33:57.788 31933 31971 D SHANNON_IMS: 0161 [CONN] triggerRegistering by WIFI_CONNECT_CHANGE [SLID:0] (ImsConnectivityMgr%triggerRegistering:3534)
04-05 09:33:57.789 2690 2746 D LocalImageResolver: Couldn't use ImageDecoder for drawable, falling back to non-resized load.
04-05 09:33:57.789 31933 31979 D SHANNON_IMS: 0162 [UT##] Other Ut request already running. Add request in pending queue [SLID:0 ] (ImsUt%runNewUtRequest:948)
04-05 09:33:57.791 1452 1525 W ActivityManager: Process com.shannon.imsservice has crashed too many times, killing! Reason: crashed quickly
04-05 09:33:57.791 31933 31977 I Process : Sending signal. PID: 31933 SIG: 9
04-05 09:33:57.793 1452 1526 W RescueParty: Attempting rescue level WARM_REBOOT
04-05 09:33:57.794 1452 1526 D PackageManager: Finished rescue level WARM_REBOOT for package com.shannon.imsservice
Post sources links, maybe there's something in there
I'm compiling my own custom rom and never found this error
Schnedi said:
发布资源链接，也许那里有东西
我正在编译自己的自定义 ROM，但从未发现此错误
Click to expand...
Click to collapse
rom sources https://github.com/exthmui
kernel sources https://android.googlesource.com/device/google/raviole-kernel/
vendor image https://dl.google.com/dl/android/aosp/google_devices-raven-tq2a.230305.008.f1-54772b94.tgz
As the log says, the error is caused by: com.shannon.imsservice
Didn't see anything on the rom sources that may cause the error, and kernel is stock, so I'd say not its fault
Not sure how that vendor image file works, but shannon ims is provided by the vendor (also the needed permissions): https://gitlab.com/schnedi3/vendor_...13/proprietary/system_ext/priv-app/ShannonIms
I recommend you to use a vendor tree extracted with adevtool (or even lineageos extract tool)
Schnedi said:
As the log says, the error is caused by: com.shannon.imsservice
Didn't see anything on the rom sources that may cause the error, and kernel is stock, so I'd say not its fault
Not sure how that vendor image file works, but shannon ims is provided by the vendor (also the needed permissions): https://gitlab.com/schnedi3/vendor_...13/proprietary/system_ext/priv-app/ShannonIms
I recommend you to use a vendor tree extracted with adevtool (or even lineageos extract tool)
Click to expand...
Click to collapse
I modified the device tree and added some SELinux rules, but this happened again in the compilation
FAILED: /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil
/mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/checkpolicy -C -M -c 30 -o /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.conf/android_common/pub_policy.conf && /mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/build_sepolicy filter_out -f /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/reqd_policy_mask.cil/android_common/reqd_policy_mask.cil -t /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil # hash of input list: aa6039e1ca8cac20dc39c60dd5d085ec691a6a1094a3c1fa4f3948e274bc8992
device/google/gs101-sepolicy/whitechapel/vendor/google/chre.te:16:ERROR 'syntax error' at token 'usf_low_latency_transport' on line 38138:
usf_low_latency_transport(chre)
# Allow CHRE to use the USF low latency transport
checkpolicy: error(s) encountered while parsing configuration
21:34:40 ninja failed with: exit status 1
Revert this commit for now
Add policy for USF low latency transport gralloc usage. · RealSchnedi/[email protected]
Bug: 183233052 Test: Verified regular and direct report sampling on Raven with shared memory transport enabled. Test: See details in testing done comment in https://googleplex-android-review.git....
github.com
Schnedi said:
Revert this commit for now
Add policy for USF low latency transport gralloc usage. · RealSchnedi/[email protected]
Bug: 183233052 Test: Verified regular and direct report sampling on Raven with shared memory transport enabled. Test: See details in testing done comment in https://googleplex-android-review.git....
github.com
Click to expand...
Click to collapse
I have restored this commit, but I get an error like the following
[ 50% 180/355] //system/sepolicyub_policy_for_vendor.cil Building cil for pub_policy_for_vendor.cil [common]
FAILED: /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil
/mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/checkpolicy -C -M -c 30 -o /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.conf/android_common/pub_policy_for_vendor.conf && /mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/build_sepolicy filter_out -f /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/reqd_policy_mask_for_vendor.cil/android_common/reqd_policy_mask_for_vendor.cil -t /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil # hash of input list: ff0f05a68765c0a567c7a6b5bb400a51419bef0bfa17d3fdd1bdda6c7d41d03f
device/google/gs101-sepolicy/whitechapel/vendor/google/hal_audio_default.te:26:ERROR 'unknown type hal_audio_default' at token ';' on line 39333:
#line 26
typeattribute hal_audio_default halclientdomain;
checkpolicy: error(s) encountered while parsing configuration
06:09:05 ninja failed with: exit status 1
any luck figuring this out? I'm seeing the same thing with my AOSP build on a Pixel 6a ... works fine on a 4a but not the 6a ... if I remove the SIM card it's fine but with the SIM card in, it'll reboot the phone with this error
I got this reboot to stop by disabling SELinux as it was an SELinux violation causing the issue... not sure what the root cause is though. I'm only doing testing so disabling SELinux isn't a big deal.