Develop Bugs

ICS reboots due to 4g/WiMax

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!!

Camera won't work

Hi,
Two weeks ago, my back-facing camera fc the stock CM camera app and won't be recognized in any other cam apps...
I didn't changed any setting!
Here is the log from the CM camera app..
java.lang.AssertionError: Supported FPS ranges cannot be null.
at android.hardware.camera2.legacy.LegacyMetadataMapper.mapControlAe(LegacyMetadataMapper.java:410)
at android.hardware.camera2.legacy.LegacyMetadataMapper.mapCharacteristicsFromParameters(LegacyMetadataMapper.java:183)
at android.hardware.camera2.legacy.LegacyMetadataMapper.createCharacteristics(LegacyMetadataMapper.java:154)
at android.hardware.camera2.CameraManager.getCameraCharacteristics(CameraManager.java:191)
at com.android.camera.one.OneCameraManager.isCamera2Supported(OneCameraManager.java:132)
at com.android.camera.one.OneCameraManager.create(OneCameraManager.java:95)
at com.android.camera.one.OneCameraManager.get(OneCameraManager.java:74)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1415)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:101)
at android.app.Activity.performCreate(Activity.java:5990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2310)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2419)
at android.app.ActivityThread.access$900(ActivityThread.java:154)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1321)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5293)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
I've already cleaned the cache.
Thanks for anything that can help me!

FrKamikaze said:
Hi,
Two weeks ago, my back-facing camera fc the stock CM camera app and won't be recognized in any other cam apps...
I didn't changed any setting!
Here is the log from the CM camera app..
java.lang.AssertionError: Supported FPS ranges cannot be null.
at android.hardware.camera2.legacy.LegacyMetadataMapper.mapControlAe(LegacyMetadataMapper.java:410)
at android.hardware.camera2.legacy.LegacyMetadataMapper.mapCharacteristicsFromParameters(LegacyMetadataMapper.java:183)
at android.hardware.camera2.legacy.LegacyMetadataMapper.createCharacteristics(LegacyMetadataMapper.java:154)
at android.hardware.camera2.CameraManager.getCameraCharacteristics(CameraManager.java:191)
at com.android.camera.one.OneCameraManager.isCamera2Supported(OneCameraManager.java:132)
at com.android.camera.one.OneCameraManager.create(OneCameraManager.java:95)
at com.android.camera.one.OneCameraManager.get(OneCameraManager.java:74)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1415)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:101)
at android.app.Activity.performCreate(Activity.java:5990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2310)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2419)
at android.app.ActivityThread.access$900(ActivityThread.java:154)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1321)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5293)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
I've already cleaned the cache.
Thanks for anything that can help me!
Click to expand...
Click to collapse
Boot into recovery wipe cache & dalvik cache. Reboot system.
Open settings/apps/all/camera/clear data

I've just done that, then launched the camera. But it recrashed after two seconds of black screen

FrKamikaze said:
I've just done that, then launched the camera. But it recrashed after two seconds of black screen
Click to expand...
Click to collapse
Then the only way is reflash the rom

Well okay, thanks anyway! :/

[10] LineageOS 17.1 for z3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Ask me
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3
Latest firmware .291
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Download TWRP
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Downloads
Download ROM
MD5: 78a54bc2c55ce935a97b4c16cebe3c69
Addons
OpenGapps
BiTGApps
microGISG (Alternative GApps microG based)
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
Tell me
XDA:DevDB Information
LineageOS 17.1 z3, ROM for the Sony Xperia Z3
Contributors
NeoArian & Mr.Tom_Tom
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
ROM OS Version: 10.x
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2020-08-18
Stable Release Date: 2020-05-01
Current Beta Version: 2020-02-23
Beta Release Date: 2020-02-08
Created 2019-10-17
Last Updated 2020-08-18

Working LOS17 build achieved
Yep, here it is: LineageOS 17 with Android 10 for our good old Z3. Shinano's not dead (yet)!
Thanks to @NeoArian for sharing repos, manifests and some hints. Behavior seems to be similar to the Z3c build.
The following links are provided for testing purposes only and may be deleted in a few days, please refer to the "official" download links of the thread owner (thanks @ronidianpatisa).
Warning: the links below are now outdated, use the download links in post #1 please
Download: LOS 17 ROM for Z3, compiled as userdebug for TESTING ONLY (alternate hoster here)
Download: Related MD5 checksum file
Download: TWRP for Z3, compatible with Android 10 ROMs for TESTING ONLY
Download: GAPPS BETA
What I have tested so far: checklist working/not working (again, thanks to @NeoArian for this idea and the initial list)

What about Z3 Dual support ? Can D6633 users test the rom safely ?

Thanks @ MrTom_Tom for the sharing of the early LOS 17 build. Very nice from you.
One question: For what stands tbd in the linked checklist?
Nevetheless i will wait for the builds from NeoArian with working encryption.

I have tested your Android 10 rom for z3! Here it is some issues that I have found!
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
.
.
.

dhacke said:
[...] i will wait for the builds from NeoArian with working encryption.
Click to expand...
Click to collapse
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
dhacke said:
For what stands tbd in the linked checklist?
Click to expand...
Click to collapse
tbd = to be determined = not yet tested
elmxx said:
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
Click to expand...
Click to collapse
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?

Thanks you for your concern and your hard work along with your dedication.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
----------------------------------------------------------------------
Yes, I wiped cache, dalvik cache, data but I did wipe system either. May be wipe the SYSTEM wasn't such a good idea!
ignore " 4. some google sound cant be saved."
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
You are right , when you swipe down, a percentage value is shown next to the icon but without swipe down you wont able to see percentage value even if you enable it.
I think this rom will be better then pie rom.... Thanks for your time.

Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
On Android pie, digital wellbeing is not working unless gapps is installed. After installing gapps, digital wellbeing works like a charm. At least on android pie, I can confirm that.

Deleted

Today I took a look at the issue with Digital Wellbeing as reported by @elmxx.
I can confirm the issue - when trying to access Digital Wellbeing through Settings, the app force closes.
Log Cat excerpt:
Code:
10-19 21:47:20.091 19366 19366 D AndroidRuntime: Shutting down VM
10-19 21:47:20.092 19366 19366 E AndroidRuntime: FATAL EXCEPTION: main
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Process: com.google.android.apps.wellbeing, PID: 19366
10-19 21:47:20.092 19366 19366 E AndroidRuntime: java.lang.RuntimeException: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jex.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1987)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.getUnsuspendablePackagesForUser(IPackageManager.java:7072)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ApplicationPackageManager.getUnsuspendablePackages(ApplicationPackageManager.java:2368)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzd.get(PG:1)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at doj.get(PG:10)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzb.a(PG:2)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kik.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxx.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxy.run(PG:27)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at laq.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jgl.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jen.run(PG:4)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforce(ContextImpl.java:1896)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1924)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.getUnsuspendablePackagesForUser(PackageManagerService.java:13936)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3326)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4028)
10-19 21:47:20.092 19366 19366 E AndroidRuntime:
I think the key info here is:
Code:
Neither user 10100 nor current process has android.permission.SUSPEND_APPS
I will look into that in more detail later, but it might be not that simple that there are some GAPPS missing.
Update:
I guess I found a solution, test was successful and submitted a patch already. Problem should be fixed in future builds.

elmxx said:
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
Click to expand...
Click to collapse
As you @elmxx have been the first to provide a detailed feedback I took some time to look after your FM Radio request, see updated post #2. It isn't working perfect as explained here by @NeoArian.
AbdullahSayed said:
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Click to expand...
Click to collapse
Sorry, I have zero experience with the Dual Sim variant, I do not hink it will currently work.

FM Radio
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.

Thanks for the great work guys! It's awesome to see our shinano getting a 10 build. Will flash ASAP. Keep it up!

elmxx said:
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Click to expand...
Click to collapse
Yes, ignore the LOS email and calender app for the moment, they are buggy but the LOS team is working hard to fix them soon.

Flashing LineageOS rom without Gapps!
I just did flash lineageos rom without flashing Gapps! Here is what I found.......
Every lineageos apps work fine except message app. not getting Text Message Notifications. ------> " google message app works fine".
By the way, May be Gapps beta caused E-mail "keep closed" issue! I am not sure.

C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????

Technoolli said:
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Click to expand...
Click to collapse
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
elmxx said:
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Click to expand...
Click to collapse
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?

nikapos said:
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
Click to expand...
Click to collapse
I do not get into recovery like that, fastboot flashing does not work anymore ...

Technoolli said:
I do not get into recovery like that, fastboot flashing does not work anymore ...
Click to expand...
Click to collapse
ok then, start over.
1. flash original .291 rom with flashtool
2. make sure your bootloader is unlocked
3. enter fastboot to flash 3.3.1 twrp recovery to FOTAPartition
4. press power button holding down volume button until you feel one short vibration.
hope this does the trick. however this is not the proper thread to discuss unbricking or installing recoveries.

Thank you, but with the Flashtool I can not select the firmware ... Can I flash it somehow different? I just can not do more in the gas pedal, also I do not come in the recovery or Android system ... help

Question Pixel 6 Pro Reboots after enabling SIM or eSim

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

Question Screen lock setup crashing (Unlocked bootloader + rooted)

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.