Had to buy a new phone due to severe mechanical damage.
While my old was still on 108 firmware, the new came 157.
Flashed 108, rooted and restored recent nandroid backup w/ Philz Touch.
Everything works fine except both cameras and the (flashlight) LED. The apps just quit.
Would like to keep my old 108.
Wiped dalvik, data and cache of the camera app and rebooted. No dice.
Is it possible, Sony made hardware modifikations that do not get adressed with roms prior to 157?
Any advice on how to proceed?
Is it possible to selectively update the camera only?
Thanks
I had the same problem when rooting the .157, two options to restore the camera function can be found here: http://forum.xda-developers.com/sony-xperia-z1-compact/help/camera-upgrading-to-lollipop-t3090499/post60837766#post60837766
Thanks.
The catch seems to be, not to switch on the phone between flashes, right?
But I would need to flash .108, root and install dual recovery and finally restore my nandroid.
To avoid switching on for root and recovery install I'd need a prerooted .108 ftf with recovery, right?
Does anyone know, if such already exists for download or if I have to make my own?
On another thought.: I did no separate wiping in Philz, before restoring the nandroid, assuming, the restore would take care. Is that correct?
mistrix said:
Thanks.
The catch seems to be, not to switch on the phone between flashes, right?
But I would need to flash .108, root and install dual recovery and finally restore my nandroid.
To avoid switching on for root and recovery install I'd need a prerooted .108 ftf with recovery, right?
Does anyone know, if such already exists for download or if I have to make my own?
On another thought.: I did no separate wiping in Philz, before restoring the nandroid, assuming, the restore would take care. Is that correct?
Click to expand...
Click to collapse
Correct, you may want to create a prerooted .108 FTF file with recovery yourself, unless you have better luck in finding the prerooted in the general section. I tried separate wiping in Philz before restoring the nandroid, in my case my cameras still didn't work.
komedol said:
Correct, you may want to create a prerooted .108 FTF file with recovery yourself, unless you have better luck in finding the prerooted in the general section. I tried separate wiping in Philz before restoring the nandroid, in my case my cameras still didn't work.
Click to expand...
Click to collapse
Did that, but unfortunately w/o success. Still no cameras or flashlight.
But everything works just fine, w/ the prerooted .108 ftf only. Hence it's the nandroid restore (tried Philz and TWRP) that messes things up.
Here is a Logcat Extreme log for an unsuccessfull camera start. Does that help somebody help me on how to proceed?
Code:
07-04 23:36:24.189 14289 14289 I ActivityManager: Timeline: Activity_launch_request id:com.sonyericsson.android.camera time:405572
07-04 23:36:24.189 1394 1758 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity (has extras)} from pid 14289
07-04 23:36:24.699 14289 14289 W ContextImpl: Implicit intents with startService are not safe: Intent { act=com.sonyericsson.psm.sysmonservice.ISysmonService } android.content.ContextWrapper.bindService:517 com.sonyericsson.cameracommon.thermal.ThermalAlertReceiver.bindThermalService:185 com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity.onResume:405
07-04 23:36:24.899 1394 1420 I ActivityManager: Displayed com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity: +475ms
07-04 23:36:24.899 1394 1420 I ActivityManager: Timeline: Activity_windows_visible id: ActivityRecord{440a9338 u0 com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity t14} time:406281
07-04 23:36:26.019 14289 14289 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 14289
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.CameraDeviceHandler.getLatestCachedParameters(CameraDeviceHandler.java:2172)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.StateMachine.getCurrentCameraParameters(StateMachine.java:438)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.getFlashOptions(FastViewFinder.java:1267)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.generateShortcutSettingItem(FastViewFinder.java:1121)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.addItem(FastViewFinder.java:1190)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.generateShortcutItemAdapter(FastViewFinder.java:1070)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.setupShortcutTray(FastViewFinder.java:966)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.setupHeadUpDisplay(FastViewFinder.java:634)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.view.FastViewFinder.sendViewUpdateEvent(FastViewFinder.java:1955)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.StateMachine$StateStandby.handleRequestSetupHeadUpDisplay(StateMachine.java:1356)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.StateMachine.sendEvent(StateMachine.java:3861)
07-04 23:36:26.019 14289 14289 E AndroidRuntime: at com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity$PostDeviceInitializationTask.run(FastCapturingActivity.java:775)
07-04 23:36:26.029 1394 1566 W ActivityManager: Force finishing activity com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity
07-04 23:36:26.729 1394 1421 W ActivityManager: Activity pause timeout for ActivityRecord{440a9338 u0 com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity t14 f}
07-04 23:36:28.409 1394 1420 W WindowManager: Force clearing orientation change: Window{43ba95a8 u0 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity}
07-04 23:36:28.429 1394 1420 I WindowManager: Screen frozen for +2s28ms due to Window{43ba95a8 u0 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity}
07-04 23:36:30.219 1394 1858 I ActivityManager: Process com.sonyericsson.android.camera (pid 14289) has died.
07-04 23:36:30.219 1394 1725 I WindowState: WIN DEATH: Window{43ba95a8 u0 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity}
07-04 23:36:30.229 1394 1463 W InputDispatcher: channel '43ba95a8 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
07-04 23:36:30.229 1394 1463 E InputDispatcher: channel '43ba95a8 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
07-04 23:36:30.229 1394 1725 W InputDispatcher: Attempted to unregister already unregistered input channel '43ba95a8 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity (server)'
07-04 23:36:30.229 1394 1725 W WindowManager: Force-removing child win Window{43bba8e8 u0 SurfaceView} from container Window{43ba95a8 u0 com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.FastCapturingActivity}
---- 04.07.2015 23:36:57 ----
Thanks
For anyone looking for some info about Nandroid Xperia restoring and a possible fix for the camera. I've posted about it here:
http://forum.xda-developers.com/showpost.php?p=68645956&postcount=6
Infy_AsiX said:
For anyone looking for some info about Nandroid Xperia restoring and a possible fix for the camera. I've posted about it here:
http://forum.xda-developers.com/show...56&postcount=6
Click to expand...
Click to collapse
Sounds interesting, but unfortunately only links to 404
http://forum.xda-developers.com/z3/help/nandroid-restore-z3-t3043999/post68645956#post68645956 ?
So still no dice for KK, right?
mistrix said:
Sounds interesting, but unfortunately only links to 404
http://forum.xda-developers.com/z3/help/nandroid-restore-z3-t3043999/post68645956#post68645956 ?
So still no dice for KK, right?
Click to expand...
Click to collapse
oopsies, fixed the link thanks.
Well I'm not sure yet. I'll try to narrow down the cause when I've got some extra time. Seems likely to be somewhat MM related though.
Now's a better time than ever to make the upgrade to MM with a few custom Kernels around with good support. We're not getting Nougat so MM is the final destination. If it's indeed MM related, all the more reason to update.
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 need to record 1080p60fps videos on my Redmi Note 5 (pro) global. I have official Pixel Experience rom. I don't really care about Google Cam, but it seems like the only app that allows to record in 60fps (open camera record in 4k, but not in 1080p60), so I tried to install it. I have Magisk v16.0 with Camera2 API Enabler installed (checked using getprop and it is enabled), but I practically every google camera mod I tried is crashing. Here is log (same for all):
HTML:
07-18 11:27:15.713 746 796 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 0]
07-18 11:27:15.779 3205 3475 D AudioService: Stream muted, skip playback
07-18 11:27:15.780 3205 8023 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.Pixel2Mod/com.android.camera.CameraLauncher bnds=[30,880][234,1172]} from uid 10026
07-18 11:27:15.835 3205 3963 I ActivityManager: Start proc 9448:com.google.android.Pixel2Mod/u0a122 for activity com.google.android.Pixel2Mod/com.android.camera.CameraLauncher
07-18 11:27:15.923 4495 4495 I MicroDetector: Keeping mic open: false
07-18 11:27:15.923 4495 4288 I DeviceStateChecker: DeviceStateChecker cancelled
07-18 11:27:15.923 4495 2001 I AudioController: internalShutdown
07-18 11:27:15.924 4495 9439 I MicroRecognitionRunner: Stopping hotword detection.
07-18 11:27:15.924 4495 1171 I MicroRecognitionRunner: Detection finished
07-18 11:27:15.952 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:15.993 9448 9466 I CameraManagerGlobal: Connecting to camera service
07-18 11:27:16.000 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 2
07-18 11:27:16.001 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 3
07-18 11:27:16.003 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:16.007 720 7863 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
07-18 11:27:16.008 720 7863 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 18 of type 1 for Event 2, with Raise=0
07-18 11:27:16.008 720 7863 D hardware_info: hw_info_append_hw_type : device_name = voice-rec-mic
07-18 11:27:16.008 720 7863 D audio_hw_primary: disable_snd_device: snd_device(95: voice-rec-mic)
07-18 11:27:16.008 720 7863 D msm8916_platform: platform_split_snd_device: snd_device(95) num devices(0) new_snd_devices(0)
07-18 11:27:16.011 720 7863 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x5f of type 1 for Event 0, with Raise=1
07-18 11:27:16.011 720 7863 D sound_trigger_platform: platform_stdev_check_and_update_concurrency: concurrency active 0, tx 0, rx 0, concurrency session_allowed 1
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 0 API version 256
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 0 resource cost is 100
07-18 11:27:16.013 720 7863 D audio_hw_primary: in_set_parameters: enter: kvpairs=routing=0
07-18 11:27:16.014 2715 3296 I SoundTriggerHwService::Module: onCallbackEvent no clients
07-18 11:27:16.015 4495 2002 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
07-18 11:27:16.017 720 7863 D audio_hw_primary: adev_close_input_stream: enter:stream_handle(0xe64c4800)
07-18 11:27:16.017 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:16.035 9448 9466 I CAM_MaxNativeMemory: Max native memory overridden (device): 1160
07-18 11:27:16.036 9448 9466 I CAM_MemoryManager: Max native memory: 1160000000 bytes. (1160MB).
07-18 11:27:16.046 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate duration: 8ms
07-18 11:27:16.047 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate End to Activity OnCreate Start: 24ms
07-18 11:27:16.047 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onCreate
07-18 11:27:16.050 9448 9466 W linker : "/data/app/com.google.android.Pixel2Mod-jEj88MEA0xdz3YI6ZIKzOA==/lib/arm64/libgcam_swig_jni.so" unused DT entry: type 0xf arg 0x46e68
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 1 API version 256
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 1 resource cost is 100
07-18 11:27:16.064 9448 9448 I CAM_CameraUiInflater: Initializing Window Flags
07-18 11:27:16.066 9448 9467 I CAM_PermissionsChecker: Checking for critical permissions.
07-18 11:27:16.076 3205 3963 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.android.packageinstaller cmp=com.android.packageinstaller/.permission.ui.GrantPermissionsActivity (has extras)} from uid 10122
07-18 11:27:16.104 9448 9448 I CAM_CameraUiInflater: Initializing Camera Ui
07-18 11:27:16.106 9448 9466 I CAM_MemoryManager: Registering feature: HDR_PLUS
07-18 11:27:16.108 9448 9466 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.203 9448 9448 I CAM_CameraUiInflater: Initializing Action Bar
07-18 11:27:16.213 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate duration: 166ms
07-18 11:27:16.213 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onStart
07-18 11:27:16.215 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate End to OnResume Start: 2ms
07-18 11:27:16.215 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onResume
07-18 11:27:16.216 9448 9448 I CAM_Instrumentation: CameraActivity: OnResume duration: 0ms
07-18 11:27:16.220 9448 9474 D OpenGLRenderer: HWUI GL Pipeline
07-18 11:27:16.226 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onPause
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 D AndroidRuntime: Shutting down VM
07-18 11:27:16.239 9448 9448 E AndroidRuntime: FATAL EXCEPTION: main
07-18 11:27:16.239 9448 9448 E AndroidRuntime: Process: com.google.android.Pixel2Mod, PID: 9448
07-18 11:27:16.239 9448 9448 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at cok.a(Unknown Source:166)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at ccv.a(Unknown Source:54)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at com.a(Unknown Source:58)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at jxg.a(Unknown Source:15)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at con.run(Unknown Source:36)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at gvc.run(Unknown Source:8)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at hzy.run(Unknown Source:2)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at avv.run(Unknown Source:5)
07-18 11:27:16.244 9448 9448 E CAM_SilentFeedback: Could not find SilentFeedbackService, not sending crash info.
07-18 11:27:16.248 3205 3298 I ActivityManager: Showing crash dialog for package com.google.android.Pixel2Mod u0
07-18 11:27:17.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:18.877 4495 1171 I EventLogSendingHelper: Sending log events.
07-18 11:27:19.006 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:19.195 4470 4525 I cr_BindingManager: Release moderate connections: 1
07-18 11:27:22.009 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:25.811 3205 3295 W ActivityManager: Launch timeout has expired, giving up wake lock!
07-18 11:27:25.012 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:27.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:28.015 833 891 I mmid : select timeout: wait for receiving msg
It immediately crashes right after I open it. It just asks for camera and microphone permissions. I think there is some internal issue (maybe?). Crashing at:
HTML:
java.lang.NullPointerException: Attempt to get length of null array
I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot
burish said:
I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot
Click to expand...
Click to collapse
OH YEEEEAAAAAHHH! Thanks a lot! It is working now!
Damm. It's working, but there is no 60fps recording. Any ideas?
Which Version of GCAM do you use?
In https://forum.xda-developers.com/redmi-note-5-pro/themes/app-arnova8g2s-google-camera-port-t3784423 its actually listed as a feature
Maybe you should try the listed gcam from 1 post
I am also on Pixel Experience. For me Arnovas GCAM Pixel2 Mod v.8.1. works without any bugs. I flashed camera2api as zip file trough twrp. Now im waiting for stock camera port.
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)
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.