Anybody tried the modded Google camera app for Snapdragon 820 and above?
Sent from my F8331 using XDA-Developers Legacy app
Lawliet918 said:
Anybody tried the modded Google camera app for Snapdragon 820 and above?
Sent from my F8331 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I tried it but the app is not working. Force closes everytime I open
Lawliet918 said:
Anybody tried the modded Google camera app for Snapdragon 820 and above?
Sent from my F8331 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Eh, not working.
Didn't open shtting down all time
So annoying! it works on other phones... HDR+ would probably make the XZ one of the best camera's!
omarfarrah said:
So annoying! it works on other phones... HDR+ would probably make the XZ one of the best camera's!
Click to expand...
Click to collapse
First app I really wanted to work on this phone :crying:
Well I even tried converting it to system app but no luck
maybe some devs here can mod the app for our XZ. :fingers-crossed::fingers-crossed::fingers-crossed:
Wny post a question in a themes/apps topic ?
Sometimes i dont understand why people aimt reading the rules and mess up the entire forum -__-
Verstuurd vanaf mijn F8331 met Tapatalk
Pandemic said:
Wny post a question in a themes/apps topic ?
Sometimes i dont understand why people aimt reading the rules and mess up the entire forum -__-
Verstuurd vanaf mijn F8331 met Tapatalk
Click to expand...
Click to collapse
read the rules. this forum is not only for themes and apps but also for announcements and DISCUSSIONS of themes and apps. we are discussing the google camera app. i don't see anything wrong in posting it here. don't be so rigid.
Sent from my F8331 using XDA-Developers Legacy app
Lawliet918 said:
read the rules. this forum is not only for themes and apps but also for announcements and DISCUSSIONS of themes and apps. we are discussing the google camera app. i don't see anything wrong in posting it here. don't be so rigid.
Sent from my F8331 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Oh yes where you see here discussions after Themes and Apps ?
It need to be posted in Guides, News and Discussions and not here !
{
"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"
}
Verstuurd vanaf mijn F8331 met Tapatalk
Pandemic said:
Oh yes where you see here discussions after Themes and Apps ?
It need to be posted in Guides, News and Discussions and not here !
Verstuurd vanaf mijn F8331 met Tapatalk
Click to expand...
Click to collapse
here's a screenshot of the forum rules. it clearly says you could post announcements and DISCUSSIONS regarding themes and apps here. so before you even go policing everybody else's post, make sure you understand the rules yourself. i don't frickin' care if you're a senior member. go police somebody else's post because, last time i checked, i'm perfectly abiding by the forum rules myself.
Calm down guyz. Let's think of ways we can make it work on our phones. No need to get edgy over simple things
was perfectly calm here until this guy goes barging into my thread like he's the owner of XDA.
is there anyone that try this on aosp?
I think we can't use it on stock xz because hdr+ on google camera needs raw support to work.
as I suppose, here is the logcat:
08-16 09:53:37.061 4746 4746 I Timeline: Timeline: Activity_launch_request id:com.google.android.GoogleCamera time:1742999
08-16 09:53:37.064 3542 4267 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[861,521][1075,817]} from uid 10085 on display 0
08-16 09:53:37.066 2652 2652 I QNS : QNS: soc=69, v=3996, i=142, t=305
08-16 09:53:37.068 2652 2652 I QNS : QNS: requested charging current: 1600
08-16 09:53:37.084 3542 4267 D ActivityTrigger: ActivityTrigger activityPauseTrigger
08-16 09:53:37.110 3542 5150 I ActivityManager: Start proc 16892:com.google.android.GoogleCamera/u0a202 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
08-16 09:53:37.179 16892 16909 I CameraManagerGlobal: Connecting to camera service
08-16 09:53:37.194 16892 16892 E CameraSpecTypesProvider: authority from the request (com.google.android.apps.camera.specialtypes.SpecialTypesProvider1) doesn't match the current content provider flavor: RELEASE
08-16 09:53:37.203 16892 16909 I CAM_MaxNativeMemory: Max native memory overridden (device): 420
08-16 09:53:37.203 16892 16909 I CAM_MemoryManager: Max native memory: 420000000 bytes. (420MB).
08-16 09:53:37.207 16892 16892 W CAM_Log : Tag BurstSessionStatistics is 3 chars longer than limit.
08-16 09:53:37.207 16892 16892 I CAM_Instrumentation: CameraActivity: App OnCreate duration: 2ms
08-16 09:53:37.207 16892 16892 I CAM_Instrumentation: CameraActivity: App OnCreate End to Activity OnCreate Start: 8ms
08-16 09:53:37.207 16892 16892 I CAM_GcaActivity: [8a458a7] GcaActivity#onCreate
08-16 09:53:37.215 16892 16892 I CAM_CameraUiInflater: Initializing Window Flags
08-16 09:53:37.217 16892 16912 I CAM_PermissionsChecker: Checking for critical permissions.
08-16 09:53:37.221 3542 4396 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.google.android.packageinstaller cmp=com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity (has extras)} from uid 10202 on display 0
08-16 09:53:37.223 16892 16892 V BoostFramework: mAcquireFunc method = public int com.qualcomm.qti.Performance.perfLockAcquire(int,int[])
08-16 09:53:37.223 16892 16892 V BoostFramework: mReleaseFunc method = public int com.qualcomm.qti.Performance.perfLockRelease()
08-16 09:53:37.223 16892 16892 V BoostFramework: mAcquireTouchFunc method = public int com.qualcomm.qti.Performance.perfLockAcquireTouch(android.view.MotionEvent,android.util.DisplayMetrics,int,int[])
08-16 09:53:37.224 3542 4396 D ActivityTrigger: ActivityTrigger activityPauseTrigger
08-16 09:53:37.226 16892 16892 V BoostFramework: BoostFramework() : mPerf = [email protected]
08-16 09:53:37.226 16892 16892 V BoostFramework: BoostFramework() : mPerf = [email protected]
08-16 09:53:37.229 16892 16909 I CAM_MemoryManager: Registering feature: HDR_PLUS
08-16 09:53:37.230 16892 16909 I CAM_MemoryManager: State updated. Free Memory: 420000000
08-16 09:53:37.237 16892 16892 I CAM_CameraUiInflater: Initializing Camera Ui
08-16 09:53:37.280 16892 16892 I CAM_CameraUiInflater: Initializing Action Bar
08-16 09:53:37.287 16892 16892 W CAM_CameraActivity: Could not find method: setDisablePreviewScreenshots
08-16 09:53:37.287 16892 16892 I CAM_Instrumentation: CameraActivity: OnCreate duration: 80ms
08-16 09:53:37.288 16892 16892 I CAM_GcaActivity: [8a458a7] GcaActivity#onStart
08-16 09:53:37.289 16892 16892 I CAM_Instrumentation: CameraActivity: OnCreate End to OnResume Start: 1ms
08-16 09:53:37.289 16892 16892 I CAM_GcaActivity: [8a458a7] GcaActivity#onResume
08-16 09:53:37.290 16892 16892 I CAM_Instrumentation: CameraActivity: OnResume duration: 0ms
08-16 09:53:37.299 16892 16892 I CAM_GcaActivity: [8a458a7] GcaActivity#onPause
08-16 09:53:37.308 16892 16892 I CAM_MemoryManager: State updated. Free Memory: 420000000
08-16 09:53:37.308 16892 16892 I CAM_MemoryManager: State updated. Free Memory: 420000000
08-16 09:53:37.308 16892 16892 D AndroidRuntime: Shutting down VM
08-16 09:53:37.326 3542 4697 I ActivityManager: Start proc 16920:com.google.android.GoogleCamera:crash_report/u0a202 for service com.google.android.GoogleCamera/com.google.android.apps.camera.legacy.app.silentfeedback.SilentFeedbackService
08-16 09:53:37.327 16892 16892 E AndroidRuntime: FATAL EXCEPTION: main
08-16 09:53:37.327 16892 16892 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 16892
08-16 09:53:37.327 16892 16892 E AndroidRuntime: java.lang.IllegalStateException: No HDR+ compatible raw format supported.
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at cll.a(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at clx.a(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at bry.a(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at clz.a(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at iyc.a(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at cma.run(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at ghz.run(Unknown Source)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at avd.run(PG)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:272)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at java.lang.Thread.run(Thread.java:761)
08-16 09:53:37.327 16892 16892 E AndroidRuntime: at asu.run(PG)
Click to expand...
Click to collapse
and I already try this on AOSP but no luck, aosp doesn't even have camera2 support.
Anyone have any idea for this?
And magisk module to enable support again results in crash
Interesting.....c'mon DEVs. make it happen :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
modified google camera with HDR+ version 1.3. support for more phones but not sure if XZ is already included. https://www.androidfilehost.com/?fid=673368273298980236
Lawliet918 said:
modified google camera with HDR+ version 1.3. support for more phones but not sure if XZ is already included. https://www.androidfilehost.com/?fid=673368273298980236
Click to expand...
Click to collapse
I don't think it's gonna work, unless our device have raw support.
Rudy said:
I don't think it's gonna work, unless our device have raw support.
Click to expand...
Click to collapse
yeah, i think so too. that's just too bad.
Yeah.still no luck
Related
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.
As requested by @Arnova8G2 and as already available in other supported devices subforum, this thread is dedicated to Arnova8G2's version of Google Camera Port.
Latest known working version: GCam5.1.018-Arnova8G2-V1.7Beta2.apk
Config camera HDR+: Nexus 6 Auto, any other config will result in blank viewfinder.
Both lens blur and portrait mode works, but portrait works only for human object. The closer the object the more aggressive the blur is.
Other features work as expected.
Latest tested beta version: GoogleCamera-Pixel2Mod-Arnova8G2-V6-Beta16.apk
Bug: crash on start
Logcat:
Code:
02-19 04:59:57.234 1663 1687 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher (has extras)} from uid 10120 on display 0
02-19 04:59:57.237 597 2729 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
02-19 04:59:57.239 1663 1687 D ActivityTrigger: activityStartTrigger: Activity is Triggerred in full screen ApplicationInfo{b6c6157 com.google.android.GoogleCamera}
02-19 04:59:57.239 1663 1687 E ActivityTrigger: activityStartTrigger: not whiteListedcom.google.android.GoogleCamera/com.android.camera.CameraLauncher/41362666
02-19 04:59:57.239 2960 3156 I WtProcessController: mCurTask:6955
02-19 04:59:57.240 1663 1687 E ResourceType: Style contains key with bad entry: 0x0101053a
02-19 04:59:57.240 1663 1687 E ResourceType: Style contains key with bad entry: 0x0101053a
02-19 04:59:57.240 1663 1687 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.240 1663 1687 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.240 1663 1687 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.241 1663 1868 E ResourceType: Style contains key with bad entry: 0x0101053a
02-19 04:59:57.242 1663 1687 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{b6c6157 com.google.android.GoogleCamera} is now in focus and seems to be in full-screen mode
02-19 04:59:57.242 1663 1687 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.google.android.GoogleCamera/com.android.camera.CameraLauncher/41362666
02-19 04:59:57.242 1663 1687 D ActivityTrigger: ActivityTrigger activityPauseTrigger
02-19 04:59:57.258 1663 22378 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{b6c6157 com.google.android.GoogleCamera} is now in focus and seems to be in full-screen mode
02-19 04:59:57.258 1663 22378 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.google.android.GoogleCamera/com.android.camera.CameraLauncher/41362666
02-19 04:59:57.266 1663 22378 I ActivityManager: Start proc 14981:com.google.android.GoogleCamera/u0a247 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher caller=com.teslacoilsw.launcher
02-19 04:59:57.275 14981 14981 D TidaProvider: TidaProvider()
02-19 04:59:57.284 1663 1687 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.284 1663 1687 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.284 1663 1687 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.288 1663 1687 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.288 1663 1687 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.288 1663 1687 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.288 2960 3156 I WtProcessController: MOVE TO FOREGROUND: com.google.android.GoogleCamera 10247
02-19 04:59:57.289 2960 3156 I StatusController: Last foreground:com.teslacoilsw.launcher uid:10120 Current foreground:com.google.android.GoogleCamera uid:10247
02-19 04:59:57.289 1663 1687 I Timeline: Timeline: App_transition_ready time:17525606
02-19 04:59:57.289 2960 3156 I WtProcessController: FOREGROUND INFO: name=com.google.android.GoogleCamera uid=10247 pid=14981 TaskId:6955
02-19 04:59:57.290 1663 3189 V LocationPolicy: writePolicyLocked()
02-19 04:59:57.308 1663 1868 I Timeline: Timeline: App_transition_ready time:17525625
02-19 04:59:57.316 2117 2117 V PhoneStatusBarPolicy: updateManagedProfile mManagedProfileFocused: false mManagedProfileInQuietMode: false mKeyguardVisible: false mCurrentUserId:0 mCurrentProfileId:0 mSecondSpaceStatusIconVisible: true showIcon:false
02-19 04:59:57.316 1663 17820 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.316 1663 17820 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.316 1663 17820 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.344 1663 1765 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.344 1663 1765 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.344 1663 1765 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.354 1663 1765 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.354 1663 1765 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.354 1663 1765 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.363 14981 15007 I CameraManagerGlobal: Connecting to camera service
02-19 04:59:57.366 14981 14995 W CameraManagerGlobal: ignore the status update of camera: 2
02-19 04:59:57.366 14981 14995 W CameraManagerGlobal: ignore the status update of camera: 3
02-19 04:59:57.366 14981 14995 W CameraManagerGlobal: ignore the torch status update of camera: 2
02-19 04:59:57.366 14981 14995 W CameraManagerGlobal: ignore the torch status update of camera: 3
02-19 04:59:57.382 14981 14981 E ResourceType: Style contains key with bad entry: 0x0101053a
02-19 04:59:57.384 14981 14981 I CAM_Instrumentation: CameraActivity: App OnCreate duration: 3ms
02-19 04:59:57.384 14981 14981 I CAM_Instrumentation: CameraActivity: App OnCreate End to Activity OnCreate Start: 10ms
02-19 04:59:57.384 14981 14981 I CAM_GcaActivity: [d609883] GcaActivity#onCreate
02-19 04:59:57.385 14981 15007 I CAM_MaxNativeMemory: Max native memory overridden (device): 580
02-19 04:59:57.386 14981 15007 I CAM_MemoryManager: Max native memory: 580000000 bytes. (580MB).
02-19 04:59:57.389 14981 15007 W linker : /data/app/com.google.android.GoogleCamera-1/lib/arm64/libgcam_swig_jni.so: unused DT entry: type 0xf arg 0x46e68
02-19 04:59:57.393 14981 14981 I CAM_CameraUiInflater: Initializing Window Flags
02-19 04:59:57.393 14981 14981 E ResourceType: Style contains key with bad entry: 0x0101053a
02-19 04:59:57.393 14981 15008 I CAM_PermissionsChecker: Checking for critical permissions.
02-19 04:59:57.398 14981 15008 I Timeline: Timeline: Activity_launch_request time:17525715
02-19 04:59:57.400 1663 3189 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.google.android.packageinstaller cmp=com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity (has extras)} from uid 10247 on display 0
02-19 04:59:57.400 14981 14981 D AccessibilityManager: current package=com.google.android.GoogleCamera, accessibility manager mIsFinalEnabled=false, mOptimizeEnabled=true, mIsUiAutomationEnabled=false, mIsInterestedPackage=false
02-19 04:59:57.402 1663 3189 D ActivityTrigger: activityStartTrigger: Activity is Triggerred in full screen ApplicationInfo{699b321 com.google.android.packageinstaller}
02-19 04:59:57.402 1663 3189 E ActivityTrigger: activityStartTrigger: not whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/25
02-19 04:59:57.402 1663 3189 D CompatibilityInfo: mCompatibilityFlags - 0
02-19 04:59:57.402 1663 3189 D CompatibilityInfo: applicationDensity - 440
02-19 04:59:57.402 1663 3189 D CompatibilityInfo: applicationScale - 1.0
02-19 04:59:57.404 1663 3189 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{699b321 com.google.android.packageinstaller} is now in focus and seems to be in full-screen mode
02-19 04:59:57.404 1663 3189 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity/25
02-19 04:59:57.404 1663 3189 D ActivityTrigger: ActivityTrigger activityPauseTrigger
02-19 04:59:57.417 14981 15007 I CAM_MemoryManager: Registering feature: HDR_PLUS
02-19 04:59:57.417 14981 14981 I CAM_CameraUiInflater: Initializing Camera Ui
02-19 04:59:57.418 14981 15007 I CAM_MemoryManager: State updated. Free Memory: 580000000
02-19 04:59:57.418 14981 15007 I CAM_HexagonEnv: Loading libadsprpc.so from the app
02-19 04:59:57.419 14981 15007 I CAM_HexagonEnv: Loading libhalide_hexagon_host.so from the app
02-19 04:59:57.420 14981 15007 I CAM_HexagonEnv: Writing libhalide_hexagon_remote_skel.so to /data/user/0/com.google.android.GoogleCamera/libhalide_hexagon_remote_skel.so
02-19 04:59:57.421 14981 15007 I CAM_HexagonEnv: ADSP_LIBRARY_PATH=/data/user/0/com.google.android.GoogleCamera;/dsp
02-19 04:59:57.422 14981 15007 E libgcam : [static_metadata.cc:487]: Check: StaticMetadata:frame_raw_max_{width,height} matches neither the active area nor pixel array size.
02-19 04:59:57.422 14981 15007 E libgcam : [gcam.cc:158]: Create: StaticMetadata for sensor ID 1 failed basic error checks.
02-19 04:59:57.451 14981 14981 I CAM_CameraUiInflater: Initializing Action Bar
02-19 04:59:57.454 14981 14981 D AndroidRuntime: Shutting down VM
02-19 04:59:57.456 14981 14981 E CAM_SilentFeedback: Could not find SilentFeedbackService, not sending crash info.
02-19 04:59:57.456 14981 14981 E AndroidRuntime: FATAL EXCEPTION: main
02-19 04:59:57.456 14981 14981 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 14981
02-19 04:59:57.456 14981 14981 E AndroidRuntime: java.lang.VerifyError: Verifier rejected class dam: java.lang.Object dam.a() failed to verify: java.lang.Object dam.a(): [0x14] invalid argument count (4) exceeds outsSize (3) (declaration of 'dam' appears in /data/app/com.google.android.GoogleCamera-1/base.apk)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at btf.a(PG)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at btf.<init>(PG)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at com.google.android.apps.camera.legacy.app.activity.main.CameraActivity.onCreate(PG)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.os.Looper.loop(Looper.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
02-19 04:59:57.456 14981 14981 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
02-19 04:59:57.458 2960 3156 I WtProcessController: Receive am_crash event for pid: 14981 pkg = com.google.android.GoogleCamera
02-19 04:59:57.458 2960 3156 W KloServer: Aborted broadcast does not supprt for: com.google.android.GoogleCamera
device info: View attachment jason.device_info.txt
@leledumbo
Test for Mi Note 3
https://drive.google.com/open?id=1fuNlVPSlgWyjs4QJqsnemTy3ZV8BQQhV
Arnova8G2 said:
@leledumbo
Test for Mi Note 3
https://drive.google.com/open?id=1fuNlVPSlgWyjs4QJqsnemTy3ZV8BQQhV
Click to expand...
Click to collapse
Blank viewfinder, even after changing config to "Nexus 6 Auto". Logcat: View attachment logcat.txt
Do you test with other config ?
Arnova8G2 said:
Do you test with other config ?
Click to expand...
Click to collapse
Yes, all of them results in blank viewfinder.
Arnova8G2 said:
@leledumbo
Test for Mi Note 3
Thanks, the test for Mi Note 3 works perfectly. Only HDR on the front camera does not work.
Click to expand...
Click to collapse
andrei_046 said:
Arnova8G2 said:
@leledumbo
Test for Mi Note 3
Thanks, the test for Mi Note 3 works perfectly. Only HDR on the front camera does not work.
Click to expand...
Click to collapse
How could it work for you? So weird...
Click to expand...
Click to collapse
Arnova8G2 said:
Do you test with other config ?
Click to expand...
Click to collapse
Thanks Arnova for support Mi Note 3!
Here are logs from each config, I've also grep-ed the logcat to only those having CAM_:
View attachment logcat.auto.txt
View attachment logcat.nexus6auto.txt
View attachment logcat.nexus6p.txt
View attachment logcat.pixel2017zslhdr+.txt
The stacktrace look similar, they all fail in InitParams.
leledumbo said:
Blank viewfinder, even after changing config to "Nexus 6 Auto". Logcat: View attachment 4424352
Click to expand...
Click to collapse
try to disable front HDR, its not working on our phone
Guys, i have this installed:
GC_3.2.045_Mi6_MiMix_final_1.1.apk.
It works very well on my Mi Note 3 for photos.
Is this version worse than the post 1?
lubikem01 said:
try to disable front HDR, its not working on our phone
Click to expand...
Click to collapse
Damn, it's so simple but I didn't try! HUGE thanks!
Mord0rr said:
Guys, i have this installed:
GC_3.2.045_Mi6_MiMix_final_1.1.apk.
It works very well on my Mi Note 3 for photos.
Is this version worse than the post 1?
Click to expand...
Click to collapse
Not worse, just different and is based on older version. It's more stable but has less features. I believe that's BSG work.
@Arnova8G2 after some night testing, I found that the last one you gave has greenish issue on dark area. Here are some comparisons both outdoor and indoor, compared to MIUI camera (outdoor one with HDR on):
{
"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"
}
Arnova8G2 said:
Do you test with other config ?
Click to expand...
Click to collapse
Hi,
I tested both AUTO and Nexus6AUTO config. Still blank view finder
Here are the logs.
lubikem01 said:
try to disable front HDR, its not working on our phone
Click to expand...
Click to collapse
I had another version of GCam5Mod working. Using config Nexus6Auto. It even works with ZSL. However the video has blank viewfinder.
However I uninstalled it somehow. The only thing I remember is that it has model selection from the first page of the settings menu. Not sure which one was it just randomly grabbed from xda posts lol
---------- Post added at 02:40 AM ---------- Previous post was at 02:18 AM ----------
leledumbo said:
Damn, it's so simple but I didn't try! HUGE thanks!
Click to expand...
Click to collapse
Tried this, it totally works.
There are some minor issues. HDR+Enhanced crashes, video 1080p60fps video output is corrupted.
Let me try tweak these.
For tests before the final version
https://drive.google.com/open?id=1QFqNimgDUG539RsmgD_bkj7hwzKfLzTA
Arnova8G2 said:
For tests before the final version
Click to expand...
Click to collapse
Focus on pressing the screen does not work.
Arnova8G2 said:
For tests before the final version
https://drive.google.com/open?id=1QFqNimgDUG539RsmgD_bkj7hwzKfLzTA
Click to expand...
Click to collapse
This seems to fix the front camera, at least it's usable even if HDR+ for it still has to be disabled. Pixel 2017 Zsl+ config causes blurry image, though. But perhaps it's expected, it's ZSL after all. Choosing auto config makes more appropriate shutter speed. Portrait mode causes blank viewfinder with non-responding interface which finally terminates itself.
For the back camera, greenish hue issue is still there.
Strangely, MI6 i put above works very well after a small tests e did at night...
Hello techy people,
I have bought XA2, unlocked bootloader and installed latest LOS 15 (30 Nov build). Installed Magisk, MicroG, Afwall, all worked well and today random reboots started to happen. Sometimes it happens when I play with location settings in maps app, sometimes when I use the messenger. I did a few logcats and all of them have the following bit:
12-02 39.242 12603 12689 D ConnectivityService: handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 100]
12-02 39.258 12449 12488 W IptablesRestoreController: iptables-restore process 12453 terminated status=256
12-02 39.262 12449 12488 E Netd : failed to change iptables rule that sets incoming packet mark
12-02 39.262 12449 12488 E Netd : failed to change permission on interface rmnet_data0 of netId 100 from 0 to 1
12-02 39.266 12603 12689 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityServiceThread
12-02 39.266 12603 12689 E AndroidRuntime: java.lang.IllegalStateException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2707)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.updateCapabilities(ConnectivityService.java:4708)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.handleLingerComplete(ConnectivityService.java:4879)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.-wrap9(Unknown Source:0)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.maybeHandleNetworkAgentInfoMessage(ConnectivityService.java:2213)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.handleMessage(ConnectivityService.java:2225)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.internal.util.WakeupMessage.onAlarm(WakeupMessage.java:111)
12-02 39.266 12603 12689 E AndroidRuntime: at android.app.AlarmManager$ListenerWrapper.run(AlarmManager.java:243)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
12-02 39.266 12603 12689 E AndroidRuntime: Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:505)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:401)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:396)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2702)
12-02 39.266 12603 12689 E AndroidRuntime: ... 12 more
12-02 39.284 12603 12689 I Process : Sending signal. PID: 12603 SIG: 9
12-02 39.440 889 889 I adbd : Framework disconnect
12-02 39.445 859 859 I lowmemorykiller: ActivityManager disconnected
12-02 39.445 859 859 I lowmemorykiller: Closing Activity Manager data connection
12-02 39.446 924 924 E LocSvc_GnssInterface: serviceDied] service died. cookie: 0, who: 0x70de233c20
12-02 39.447 924 924 E LocSvc_APIClientBase: locAPIStopTracking:339] invalid session: 0.
12-02 39.447 924 924 E GnssHal_GnssGeofencing: serviceDied] service died. cookie: 0, who: 0x70de233fe0
12-02 39.447 924 924 E LocSvc_GnssNiInterface: serviceDied] service died. cookie: 0, who: 0x70de2b3020
12-02 39.451 12727 12744 W Sensors : sensorservice died [0x722207c3e0]
12-02 39.451 598 598 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x750ae5f000
12-02 39.451 575 575 I ServiceManager: service 'launcherapps' died
12-02 39.452 14342 14420 W Sensors : sensorservice died [0xe6b374c0]
12-02 39.452 575 575 I ServiceManager: service 'media_projection' died
12-02 39.452 575 575 I ServiceManager: service 'media.camera.proxy' died
12-02 39.453 575 575 I ServiceManager: service 'autofill' died
12-02 39.453 575 575 I ServiceManager: service 'imms' died
12-02 39.453 575 575 I ServiceManager: service 'profile' died
12-02 39.454 575 575 I ServiceManager: service 'usb' died
12-02 39.454 575 575 I ServiceManager: service 'serial' died
12-02 39.455 575 575 I ServiceManager: service 'hardware_properties' died
12-02 39.457 12445 12445 E Zygote : Exit zygote because system server (12603) has terminated
Click to expand...
Click to collapse
I understand that bootloops are caused by setPermissionForNetworks() but not sure how to fix it.
Any help would be appreciated.
All sorted, many thanks
pupsidze said:
All sorted, many thanks
Click to expand...
Click to collapse
How did you fix it?
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.