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)
Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.
mrhnn said:
Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.
Click to expand...
Click to collapse
Did you buy it on eBay?
FoneWatcher said:
Did you buy it on eBay?
Click to expand...
Click to collapse
No, no. I bought it in the electronics store in Jan-22.
mrhnn said:
No, no. I bought it in the electronics store in Jan-22.
Click to expand...
Click to collapse
I've never used eSIM, but, I looked around & found this:
How to use dual SIMs on your Google Pixel phone - Pixel Phone Help
New to Pixel? Use our setup guide If you have a Pixel 3a or later Pixel phone, you can use two
support.google.com
Namely, have you checked/verified that your carrier(s) allow for Dual-Sim?
Other than that, my only guess is that the phone is SIM locked, but, if you bought it new & the phone is paid off, that can be ruled out.
Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9
mrhnn said:
Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9
Click to expand...
Click to collapse
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working
akbulut00 said:
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working
Click to expand...
Click to collapse
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!
mrhnn said:
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!
Click to expand...
Click to collapse
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.
akbulut00 said:
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.
Click to expand...
Click to collapse
Dissolved. The problem was the incomplete update.
sagolasin yine de
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.
Trying to follow this thread, says the HW3 is eligible, but unsuccessful in logging into MicroG. Has anyone else been able to install Play Store?
Steps so far:
Code:
adb shell pm disable-user com.android.packageinstaller
adb install huagu3.apk
adb shell appops set com.bishua666.luxxx1 GET_USAGE_STATS allow
Disable route to internet.
Set date on phone to July 20, 2020 and sync watch.
Open huagu3 on watch and allow full access
Step 1 successful.
Step 2 immediately closes app
adb install 01_MicroG.apk -> success
Open MicroG and try to add account, app immediately closes.
logcat:
Code:
--------- beginning of crash huagu3
07-20 15:56:27.370 12290 12290 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:27.370 12290 12290 E AndroidRuntime: Process: com.bishua666.luxxx1, PID: 12290
07-20 15:56:27.370 12290 12290 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.DATE_SETTINGS }
MicroG:
07-20 15:56:37.557 12395 12395 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:37.557 12395 12395 E AndroidRuntime: Process: com.google.android.gms:ui, PID: 12395
07-20 15:56:37.557 12395 12395 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.auth.login.LoginActivity}: java.lang.UnsupportedOperationException
Appreciate any assistance in advance, thanks.
Ref:
Install native GMS, Google Play Store directly on Harmony OS 3.0 (Tested Feb 2023)
How to install GMS Harmony OS 3.1 has newer processes https://forum.xda-developers.com/t/install-native-gms-on-harmony-os-3-1-tested-may-2023-on-huawei-mate-x3.4583737/ *** IMPORTANT NOTE *** I am working on the step by step instructions, stay...
forum.xda-developers.com
Current Eligible Devices:
Huawei Wear Series
HUAWEI WATCH 3
Hi,
Exactly the same for me ...