Related
my camera on Desier HD stop working. Each time I tried to open Camera aplication, I received message - unable to connect to camera
I tried use also different apps, I also tried to install my ROM again with all wipes and factory reset without success.
All was working fine before with this ROM, camera stoped working about 3 days ago. Only thing I know about is that it afll down on carpet from my hands. Tha t day I tried later to make phone and camera was not working.
Is there any apps how to test if there is HW problem with camera?
I'm using this ROM: JellyTime for DHD 4.2.2 R11
/devlog/system_log:
Code:
11-23 23:54:47.978 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.028 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Sun Jun 23 14:18:49 PDT 2013
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build description: yakju-user 4.2.2 JDQ39 573038 release-keys
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
11-23 23:54:48.208 E/QualcommCameraHardware( 1484): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
11-23 23:54:48.218 E/QualcommCameraHardware( 1484): createInstance: startCamera failed!
11-23 23:54:48.218 E/CameraClient( 1484): Could not open camera 0: -1
11-23 23:54:48.218 E/CameraClient( 1484): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
11-23 23:54:48.218 E/CameraHolder( 4195): fail to connect Camera
11-23 23:54:48.218 E/CameraHolder( 4195): java.lang.RuntimeException: Fail to connect to camera service
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.native_setup(Native Method)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.<init>(Camera.java:340)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.open(Camera.java:302)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:291)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.Util.openCamera(Util.java:478)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:344)
11-23 23:54:48.228 W/SensorService( 1809): sensor 00000000 already enabled in connection 0x51df4d58 (ignoring)
11-23 23:54:50.430 W/InputMethodManagerService( 1809): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000c in package table 0 because it is not complex!
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000d in package table 0 because it is not complex!
Thank You for help
jordibravo said:
my camera on Desier HD stop working. Each time I tried to open Camera aplication, I received message - unable to connect to camera
I tried use also different apps, I also tried to install my ROM again with all wipes and factory reset without success.
All was working fine before with this ROM, camera stoped working about 3 days ago. Only thing I know about is that it afll down on carpet from my hands. Tha t day I tried later to make phone and camera was not working.
Is there any apps how to test if there is HW problem with camera?
I'm using this ROM: JellyTime for DHD 4.2.2 R11
/devlog/system_log:
Code:
11-23 23:54:47.978 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.028 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Sun Jun 23 14:18:49 PDT 2013
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build description: yakju-user 4.2.2 JDQ39 573038 release-keys
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
11-23 23:54:48.208 E/QualcommCameraHardware( 1484): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
11-23 23:54:48.218 E/QualcommCameraHardware( 1484): createInstance: startCamera failed!
11-23 23:54:48.218 E/CameraClient( 1484): Could not open camera 0: -1
11-23 23:54:48.218 E/CameraClient( 1484): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
11-23 23:54:48.218 E/CameraHolder( 4195): fail to connect Camera
11-23 23:54:48.218 E/CameraHolder( 4195): java.lang.RuntimeException: Fail to connect to camera service
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.native_setup(Native Method)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.<init>(Camera.java:340)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.open(Camera.java:302)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:291)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.Util.openCamera(Util.java:478)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:344)
11-23 23:54:48.228 W/SensorService( 1809): sensor 00000000 already enabled in connection 0x51df4d58 (ignoring)
11-23 23:54:50.430 W/InputMethodManagerService( 1809): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000c in package table 0 because it is not complex!
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000d in package table 0 because it is not complex!
Thank You for help
Click to expand...
Click to collapse
I suppose there is a loose connection between camera module and circuit board
sent from my Nokia Lumia 820
the easiest way to make sure is flashing stock rom. if it doesnt work, it is most likely hw
Same problem here
Hello I have a problem with my HTC desire eye. After factory reset camera stops working. When I try to open it appear the message "camera closed unexpectedly" what can I do to solve it? Camera app is updated, Android version is updated to the latest version
Same thing happened with me. I just flashed another rom and everything was good. Try deleting camera app data and cache. If that don't help then u might probably have wrong camera files. What rom are u on and what firmware? Are u using custom kernel?
I recommend doing a factory reset if nothing else works and check and if still it doesnt work then ya install another rom.
I have Android 6.0. I've tried to take a reset to clear cache and data but no chance. And after update to 6.0 flashlight too is not working. In flashlight app appears"loading" and doesn't start.
{
"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"
}
Same behavior. I've tried Viper, Stock MM, and the new S.Rom, all of them behave the same way. NFC, WiFi, etc, everything else works. But once you give the camera the permissions it needs to launch, it crashes. I'm on an ATT Desire EYE ul_ca 0PFH100 to be specific.. OTA'd to the latest update, used HTC dev unlock, and installed Viper first.. No dice, then tried Mini's Stock MM, no dice.. Finally the new S.Rom, same thing. Did I miss a firmware update somewhere or did I skip a step somewhere and screw up a driver somewhere?
Baseband: [email protected]_40.50.C33069.02F
Ruu'd back to stock AT&T lollipop via the official ruu page on HTC, still no camera. What did I do to completely break the camera drivers so badly that it persists through an ruu?
Try manually replacing camera files like mini told in the port guide. If this doesn't work it's most probably a hardware issue... Which I do think it is.
I've flashed s. Rom but camera app still have problems.I'll try to view camera connector if it's ok
TahirZX said:
Try manually replacing camera files like mini told in the port guide. If this doesn't work it's most probably a hardware issue... Which I do think it is.
Click to expand...
Click to collapse
Forgive my ignorance/arrogance one would be safe in assuming that an RUU should in theory replace those files right? I'll most definitely give it a try or seven, but I've gone back and forth between roms and now the ruu's, I'd sincerely hope something has overwritten those files at some point.
Question: I am S-On would that have any effect on being able to access those files (for an ruu). I'm pretty sure I'd need to temp s-off or disable swp to get at the system files from within a Rom. Idk the main marketing point for this phone was the twin cameras, and it worked immediately before I unlocked, flashed twrp, then viper/venom so I don't see how it could be a physical hardware issue.
Not saying it isn't,as the internet insists it's a common issue, just don't understand software causing a hardware problem (except something like overvolting).
U r right at some point files must have overwritten but if that's the case and u have tried multiple roms and still not fixed then. U should seriously consider it being a physical fault since everything else that could be done on software side is done.
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
S-on can still access those files u just have to mount system partition as writable
TahirZX said:
Same thing happened with me. I just flashed another rom and everything was good. Try deleting camera app data and cache. If that don't help then u might probably have wrong camera files. What rom are u on and what firmware? Are u using custom kernel?
I recommend doing a factory reset if nothing else works and check and if still it doesnt work then ya install another rom.
Click to expand...
Click to collapse
Could you share with us the rom you use right now with link pls coz i have the same problem and flashed the RR-N-v585-20171111-eyeul-unofficial, and still have the same problem.
Charlie.High said:
Could you share with us the rom you use right now with link pls coz i have the same problem and flashed the RR-N-v585-20171111-eyeul-unofficial, and still have the same problem.
Click to expand...
Click to collapse
I'm on RR 5.8.4 nougat 20170905 build camera works great both front and back with flash and focus. The latest build 20171111 has bugs mostly on the front camera lacking focus and has no flash. Tho camera did work for me on both builds.
In ur case are u coming from a sense based rom directly over to RR? Or previous RR build to the new RR build?
Coming from a sense based rom u will need to wipe everything. Install tark's recovery and then flash the rom through it.
If u dirty flashed latest RR on top of old build then do a clean install using Tark's recovery.
This will fix any camera problems that u have. I highly suggest using 20170905 build. Link is in the same download link as the latest one.
TahirZX said:
I'm on RR 5.8.4 nougat 20170905 build camera works great both front and back with flash and focus. The latest build 20171111 has bugs mostly on the front camera lacking focus and has no flash. Tho camera did work for me on both builds.
In ur case are u coming from a sense based rom directly over to RR? Or previous RR build to the new RR build?
Coming from a sense based rom u will need to wipe everything. Install tark's recovery and then flash the rom through it.
If u dirty flashed latest RR on top of old build then do a clean install using Tark's recovery.
This will fix any camera problems that u have. I highly suggest using 20170905 build. Link is in the same download link as the latest one.
Click to expand...
Click to collapse
First I had the problem in my official stock ROM 6.1 to CyanogenMod C14.1 then to RR and all had the same problem.
I never have dirty flash every time make a full wipe with deleting every thing by using the WRTP v3.1, first the camera is work normally then after while when I back to lunch it it does not work. I'm sure it is not a HW or physical problem coz some times with many Data clear and cash for the camera and switch off and on mobile it's come to work but stop again ... I really need some one to take me through the steps of fixing this problem.
Charlie.High said:
First I had the problem in my official stock ROM 6.1 to CyanogenMod C14.1 then to RR and all had the same problem.
I never have dirty flash every time make a full wipe with deleting every thing by using the WRTP v3.1, first the camera is work normally then after while when I back to lunch it it does not work. I'm sure it is not a HW or physical problem coz some times with many Data clear and cash for the camera and switch off and on mobile it's come to work but stop again ... I really need some one to take me through the steps of fixing this problem.
Click to expand...
Click to collapse
I already did tell u the steps bro
---------- Post added at 03:21 AM ---------- Previous post was at 03:19 AM ----------
Charlie.High said:
First I had the problem in my official stock ROM 6.1 to CyanogenMod C14.1 then to RR and all had the same problem.
I never have dirty flash every time make a full wipe with deleting every thing by using the WRTP v3.1, first the camera is work normally then after while when I back to lunch it it does not work. I'm sure it is not a HW or physical problem coz some times with many Data clear and cash for the camera and switch off and on mobile it's come to work but stop again ... I really need some one to take me through the steps of fixing this problem.
Click to expand...
Click to collapse
CM14.1 already had camera problems I have no idea why would u even consider it a good idea to flash it.
This is basically from where ur problem began.
TahirZX said:
I'm on RR 5.8.4 nougat 20170905 build camera works great both front and back with flash and focus. The latest build 20171111 has bugs mostly on the front camera lacking focus and has no flash. Tho camera did work for me on both builds.
In ur case are u coming from a sense based rom directly over to RR? Or previous RR build to the new RR build?
Coming from a sense based rom u will need to wipe everything. Install tark's recovery and then flash the rom through it.
If u dirty flashed latest RR on top of old build then do a clean install using Tark's recovery.
This will fix any camera problems that u have. I highly suggest using 20170905 build. Link is in the same download link as the latest one.
Click to expand...
Click to collapse
//I'll try and report back if it works
*Didnt work. Camera has stopped.
#Im using GPE 6.0 only rear camera is working. There isnt even a front cam change button. Ive tried every rom on xda. RUU and all. Nothing works for me.
cagatay28 said:
//I'll try and report back if it works
*Didnt work. Camera has stopped.
#Im using GPE 6.0 only rear camera is working. There isnt even a front cam change button. Ive tried every rom on xda. RUU and all. Nothing works for me.
Click to expand...
Click to collapse
Strange man for some of u guys the cameras just stop working which is very weird. I never really had any issue like this.
Can u guys tell me what camera app are u guys using?
Did u wipe app data?
When clean flashing did u decrypt phone by wiping data partition and all other partitions too?
1- go to play store download htc camera and use that and see if it works.
2-I'll leave a zip file here try that if all else fails.
After that I can't help you guys any further sorry.
---------- Post added at 04:08 PM ---------- Previous post was at 04:02 PM ----------
Clean cache/data of htc camera app after flashing this and try if the problem is fixed
https://drive.google.com/file/d/1b0XbZxJeT5ODaDxIyVz7OwL9uedo-viE/view?usp=drivesdk
TahirZX said:
Strange man for some of u guys the cameras just stop working which is very weird. I never really had any issue like this.
Can u guys tell me what camera app are u guys using?
Did u wipe app data?
When clean flashing did u decrypt phone by wiping data partition and all other partitions too?
1- go to play store download htc camera and use that and see if it works.
2-I'll leave a zip file here try that if all else fails.
After that I can't help you guys any further sorry.
---------- Post added at 04:08 PM ---------- Previous post was at 04:02 PM ----------
Clean cache/data of htc camera app after flashing this and try if the problem is fixed
https://drive.google.com/file/d/1b0XbZxJeT5ODaDxIyVz7OwL9uedo-viE/view?usp=drivesdk
Click to expand...
Click to collapse
I have tried every cam app that google play had no luck. Sense camera doest open on many roms ive tried and for gpe 6.0 sense cam doesnt open front cam, im swiping but it only focuses. And yes clean install every time ,formated every partition that recovery let me. Btw can u make drive link public so i can try it?
cagatay28 said:
I have tried every cam app that google play had no luck. Sense camera doest open on many roms ive tried and for gpe 6.0 sense cam doesnt open front cam, im swiping but it only focuses. And yes clean install every time ,formated every partition that recovery let me. Btw can u make drive link public so i can try it?
Click to expand...
Click to collapse
Drive link is public. Also try RR rom 20170905 and let me know.
Gpe 6.0 is a ported rom not build from scratch so that might be the issue.
https://drive.google.com/folderview?id=1YTFYxRsair0GzbxspFtPXBicMrGGce1B
TahirZX said:
Drive link is public. Also try RR rom 20170905 and let me know.
Gpe 6.0 is a ported rom not build from scratch so that might be the issue.
https://drive.google.com/folderview?id=1YTFYxRsair0GzbxspFtPXBicMrGGce1B
Click to expand...
Click to collapse
//I'll try RR 20170905 later this day. Here is GPE 6.0
Crashed, here is log
HTML:
CrashLog 2.0.0(14)
Device : HTC htc_eyeul
Build number : 666671
CPU ABI : armeabi-v7a
Kernel version : 3.4.0-ElementalX-eye-5.01-GPE
Firmware version : 6.0
Screen width : 1080
Screen height : 1776
URATION_CHANGED, 1ms
11-23 10:23:45.583 V/Perf ( 1501): [email protected] onReceive:android.intent.action.CONFIGURATION_CHANGED, 0ms
11-23 10:23:45.583 V/Perf ( 1501): [email protected] onReceive:android.intent.action.CONFIGURATION_CHANGED, 0ms
11-23 10:23:45.587 V/Perf ( 1501): [email protected] onReceive:android.intent.action.CONFIGURATION_CHANGED, 4ms
11-23 10:23:45.588 V/Perf ( 1501): [email protected] onReceive:android.intent.action.CONFIGURATION_CHANGED, 2ms
11-23 10:23:45.590 I/ServiceManager(14158): Waiting for service AtCmdFwd...
11-23 10:23:45.600 D/qdmemalloc( 432): ion: Allocated buffer base:0xb374c000 size:737280 fd:72
11-23 10:23:45.600 D/qdmemalloc( 432): ion: Allocated buffer base:0xb5ece000 size:4096 fd:73
11-23 10:23:45.601 D/qdmemalloc( 1501): ion: Mapped buffer base:0x9ac70000 size:737280 offset:0 fd:62
11-23 10:23:45.601 D/qdmemalloc( 1501): ion: Mapped buffer base:0xb5933000 size:4096 offset:0 fd:64
11-23 10:23:45.603 D/ViewRootImpl( 1501): RW(11001):1,AssistPreviewPanel,null,f=[0,1080][1794,1080] o=[0,0][0,0] c=[0,0][0,0] s=[0,0][0,0] v=[0,0][0,0]
11-23 10:23:45.605 D/qdmemalloc( 432): ion: Allocated buffer base:0xb3411000 size:581632 fd:74
11-23 10:23:45.605 D/qdmemalloc( 432): ion: Allocated buffer base:0xb3410000 size:4096 fd:76
11-23 10:23:45.605 D/qdmemalloc( 1501): ion: Mapped buffer base:0x9e8f9000 size:581632 offset:0 fd:65
11-23 10:23:45.605 D/qdmemalloc( 1501): ion: Mapped buffer base:0xb58f4000 size:4096 offset:0 fd:66
11-23 10:23:45.618 V/FeatureTable(14919): Project ID : 13410
11-23 10:23:45.618 W/SystemReader(14919): Cannot find sku_id, use default value instead
11-23 10:23:45.618 V/FeatureTable(14919): SKU ID : 0
11-23 10:23:45.621 V/FeatureTable(14919): Use builder [email protected] for project 13410 and SKU 0
11-23 10:23:45.634 V/HTCCamera(14919): onCreate() - Create Settings component [Start]
11-23 10:23:45.634 W/UIComponentFactory(14919): createComponents(Launch_Before_Grant_Permission) - start
11-23 10:23:45.634 W/UIComponentFactory(14919): Creating component 'Settings Manager'
11-23 10:23:45.639 V/FeatureConfig(14919): mSelfieSkinLevel:0.5
11-23 10:23:45.639 W/FeatureConfig(14919): isDefaultLockFocusInVideo() - true
11-23 10:23:45.640 V/CameraSettings(14919): upgrade() - Current version is the latest
11-23 10:23:45.643 D/CameraSettings(14919): [Property] IsGeoTaggingEnabled : true -> false
11-23 10:23:45.649 D/PropertyBinding(14919): (Settings) null [128197612] (MainWhiteBalance) <-----> (Settings) null [128197612] (FrontWhiteBalance)
11-23 10:23:45.649 W/UIComponentFactory(14919): Take 15 ms to create com.htc.camera.component.SettingsManager(Settings Manager)
11-23 10:23:45.650 D/UIComponentManager(14919): Adding component com.htc.camera.component.SettingsManager(Settings Manager)
11-23 10:23:45.650 W/UIComponentFactory(14919): createComponents(Launch_Before_Grant_Permission) - end
11-23 10:23:45.650 V/HTCCamera(14919): onCreate() - Create Launch component [End]
11-23 10:23:45.650 D/UIComponentManager(14919): Initializing component com.htc.camera.component.SettingsManager(Settings Manager)
11-23 10:23:45.651 D/PropertyBinding(14919): [email protected] (Settings) ------> [email protected] (Settings)
11-23 10:23:45.651 V/HTCCamera(14919): onCreate() - Set content view [Start]
11-23 10:23:45.655 I/lyapota (14919): <getNavBarTweak> ForcedWindowFlags=0x810100, isFloatWindow=false, result=2
11-23 10:23:45.681 V/HTCCamera(14919): onCreate() - Set content view [End]
11-23 10:23:45.681 V/HTCCamera(14919): checkPermissions
11-23 10:23:45.681 V/HTCCamera(14919): Request permissions : check basic permission
11-23 10:23:45.682 V/HTCCamera(14919): Request permissions : check basic permission done
11-23 10:23:45.682 V/HTCCamera(14919): Request permissions : Basic permissions granted
11-23 10:23:45.683 V/HTCCamera(14919): Launch: all permissions granted
11-23 10:23:45.683 V/HTCCamera(14919): Request permissions : check MediaProvider permission
11-23 10:23:45.683 D/AndroidRuntime(14919): Shutting down VM
11-23 10:23:45.684 E/CameraApplication(14919): ***** Unhandled Exception *****
11-23 10:23:45.684 E/CameraApplication(14919): java.lang.NoSuchMethodError: No virtual method isInMultiWindowMode()Z in class Lcom/htc/camera/HTCCamera; or its super classes (declaration of 'com.htc.camera.HTCCamera' appears in /system/priv-app/Camera/Camera.apk)
11-23 10:23:45.684 E/CameraApplication(14919): at com.htc.camera.HTCCamera.onCreate_l(HTCCamera.java)
11-23 10:23:45.684 E/CameraApplication(14919): at com.htc.camera.HTCCamera.checkPermissions(HTCCamera.java)
11-23 10:23:45.684 E/CameraApplication(14919): at com.htc.camera.HTCCamera.onCreate(HTCCamera.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.Activity.performCreate(Activity.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.ActivityThread.access$900(ActivityThread.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.os.Handler.dispatchMessage(Handler.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.os.Looper.loop(Looper.java)
11-23 10:23:45.684 E/CameraApplication(14919): at android.app.ActivityThread.main(ActivityThread.java)
11-23 10:23:45.684 E/CameraApplication(14919): at java.lang.reflect.Method.invoke(Native Method)
11-23 10:23:45.684 E/CameraApplication(14919): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
11-23 10:23:45.684 E/CameraApplication(14919): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
11-23 10:23:45.684 W/CameraApplication(14919): [Event] UnhandledException [2] : Handler count : 1
11-23 10:23:45.684 W/CameraApplication(14919): [Event] UnhandledException [2] : Call [0] 1
--------- beginning of crash
11-23 10:23:45.684 E/AndroidRuntime(14919): FATAL EXCEPTION: main
11-23 10:23:45.684 E/AndroidRuntime(14919): Process: com.htc.camera, PID: 14919
11-23 10:23:45.684 E/AndroidRuntime(14919): java.lang.NoSuchMethodError: No virtual method isInMultiWindowMode()Z in class Lcom/htc/camera/HTCCamera; or its super classes (declaration of 'com.htc.camera.HTCCamera' appears in /system/priv-app/Camera/Camera.apk)
11-23 10:23:45.684 E/AndroidRuntime(14919): at com.htc.camera.HTCCamera.onCreate_l(HTCCamera.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at com.htc.camera.HTCCamera.checkPermissions(HTCCamera.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at com.htc.camera.HTCCamera.onCreate(HTCCamera.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.Activity.performCreate(Activity.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.ActivityThread.access$900(ActivityThread.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.os.Handler.dispatchMessage(Handler.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.os.Looper.loop(Looper.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at android.app.ActivityThread.main(ActivityThread.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at java.lang.reflect.Method.invoke(Native Method)
11-23 10:23:45.684 E/AndroidRuntime(14919): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
11-23 10:23:45.684 E/AndroidRuntime(14919): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
11-23 10:23:45.692 I/MediaManager( 8215): [MediaManagerProvider] [call] arg = null
Try these and launch camera after each step
1-turn off multi window mode and restart.
2-go to permissions and allow camera app all permissions from within settings.
I'm not an expert on log/fixes but try these steps cuz that's what I could make out as far as I could from the logs.
Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted.
They in fact check if SE Linux is in enforcement mode. Here is the log snippet:
Code:
11-23 18:44:54.894 2259 2521 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity bnds=[350,815][506,994] (has extras)} from uid 10036
11-23 18:44:54.935 2084 2084 I display : [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(0)
11-23 18:44:54.969 2259 4027 I ActivityManager: Start proc 20526:com.fidor.fsw/u0a119 for activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
11-23 18:44:55.190 2084 2084 I display : [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(39)
11-23 18:44:55.229 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libEGL_mali.so from the current namespace instead.
11-23 18:44:55.326 20526 20540 D libEGL : loaded /system/lib/egl/libEGL_mali.so
11-23 18:44:55.339 2084 2133 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
11-23 18:44:55.356 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv1_CM_mali.so from the current namespace instead.
11-23 18:44:55.362 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv1_CM_mali.so
11-23 18:44:55.586 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv2_mali.so from the current namespace instead.
11-23 18:44:55.588 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv2_mali.so
11-23 18:44:56.455 20526 20526 I putmethod.latin: type=1400 audit(0.0:774): avc: denied { read } for name="/" dev="tmpfs" ino=3689 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-23 18:44:56.455 20526 20526 W putmethod.latin: type=1300 audit(0.0:774): arch=40000028 syscall=334 per=800008 success=yes exit=0 a0=ffffff9c a1=898ca354 a2=4 a3=0 items=1 ppid=2066 auid=4294967295 uid=10119 gid=10119 euid=10119 suid=10119 fsuid=10119 egid=10119 sgid=10119 fsgid=10119 tty=(none) ses=4294967295 exe="/system/bin/app_process32" subj=u:r:untrusted_app_25:s0:c512,c768 key=(null)
11-23 18:44:56.455 1978 1978 W auditd : type=1307 audit(0.0:774): cwd="/"
11-23 18:44:56.455 1978 1978 W auditd : type=1302 audit(0.0:774): item=0 name="/sbin" inode=3689 dev=00:12 mode=040755 ouid=0 ogid=0 rdev=00:00 obj=u:object_r:rootfs:s0
11-23 18:44:56.455 1978 1978 W auditd : type=1327 audit(0.0:774): proctitle="com.google.android.inputmethod.latin"
11-23 18:44:56.455 1978 1978 W auditd : type=1320 audit(0.0:774):
11-23 18:44:56.527 2259 3192 W ActivityManager: Force finishing activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
Since LineageOS sets SELinux by default into permissive, this check fails and the app crashes. I'm able to set it to enforced with "SE Linux mode changer" or any other app of that kind, but immediately after the change the phone starts eating 100% cpu and modem (neither internet, nor SMS/phone calls) aren't working, which makes me think LineageOS doesn't work really well in enforcement mode of SE Linux. But the app itself launches just fine with SELinux in enforced.
I'm not an expert in Android and SELinux, but would like to know if there is a way:
to workaround the check we see in the logs and work with the app in permissive mode
to make LineageOS work correctly under enforced
PS. It doesn't matter which way to set the SELinux mode. Whatever is done - through kernel, in init.d or in adb shell, the symptoms are exactly the same after the change.
Thanks
bytes85 said:
Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Unofficial LineageOS (since there's no Official LineageOS Oreo released yet) thread for your device.
https://forum.xda-developers.com/showthread.php?t=3678205
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
CLEAN FLASH:
• Make sure you have a custom recovery installed (https://www.androidfilehost.com/?fid=4349826312261812924)
• Download the latest Resurrection Remix Rom & the latest OpenGapps package
• Boot into recovery
• Perform a FULL factory wipe and wipe system, vendor, data, cache and dalvik cache as a precaution
• Flash OpenGapps [Pico or Nano] (Optional)
• Flash Magisk Root (Optional)
• Reboot to recovery and then to system
• First boot may take up to 5-10 minutes.
DIRTY FLASH:
• Download the latest Resurrection Remix update for your device
• Reboot to recovery
• Flash firmware
• Flash Resurrection Remix update
• Wipe dalvik cache
• Reboot to system and wait some seconds or minutes.
(If you flashed the recommended Gapps package mentioned above, no needed to flash them again)
ROM Download
OpenGapps
Magisk
Resurrection Remix Source
Kernel Source
XDA Developers
LineageOS
AICP
crDroid
AOSiP
Dirty Unicorns
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
Join our RR Ginkgo & Willow Telegram support group : https://t.me/rr_ginkgo
IMPORTANT!: IF YOU COMPLAIN ABOUT A BUG OR ANY OTHER STUFF ON THIS ROM AND YOU MISSED TO POST THE LOG, YOU WILL BE IGNORED!
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
XDA:DevDB Information
Resurrection Remix for Xperia XZ Premium , ROM for the Sony Xperia XZ Premium
Contributors
Shujath
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-11-22
Last Updated 2020-11-22
Thank you for your hard job Shujath, but when I try to flash it, I have seen this error:
Zip file is corrupt!
Error installing zip file: "/external_sd/RROS-Q-8.6.4-20201122-maple-Unofficial"
I've downloaded it a couple of times and the result is the same. My phone is G8141. The all others ROM's working well.
Woahhh RR Q thx mate for hardworkkkk....
i try RR shutter button/launch camera with key always cant off, in setting camera i choose off...
oh i find a way to stop the camera key but consequently the camera button is unable to take pictures
go system/usr/keylayout/gpio-keys.kl
edit/delete key 766 CAMERA to null and save...
After full wipe of the device (cache, dalvik cache, data, system and internal storage ) the ROM is working great. Thanks Shujath for your hard work.
Thanks @Shujath
Every things works perfect
Thank you....
Damn @Shujath how many ROMs do you work on for us ❤ You're hard work is always appreciated by us.
Good Rom With High Performance & Good Appearance
Thank you Shujath !
This is the second ROM (Havoc OS & RROS) that I have used from you
Anything is extremely good except not using Microsoft Edge because it can not download with the error (SD Card Not Found)
Have a nice day :laugh: !
thinhcao3110 said:
Thank you Shujath !
This is the second ROM (Havoc OS & RROS) that I have used from you
Anything is extremely good except not using Microsoft Edge because it can not download with the error (SD Card Not Found)
Have a nice day :laugh: !
Click to expand...
Click to collapse
For me Microsoft Edge working well , please check your SD card
ted5300 said:
For me Microsoft Edge working well , please check your SD card
Click to expand...
Click to collapse
Sorry, however I don't use SD Cards. All application requesting storage permission also has this trouble.
Only Microsoft Edge can not use because of not saving the download file.
I feel very confused. I tried to many way to fix this error but not succeed.
Do you have any solution for the phenomenon ?
thinhcao3110 said:
Sorry, however I don't use SD Cards. All application requesting storage permission also has this trouble.
Only Microsoft Edge can not use because of not saving the download file.
I feel very confused. I tried to many way to fix this error but not succeed.
Do you have any solution for the phenomenon ?
Click to expand...
Click to collapse
I think that is a bug in MS Edge. Please try to install Edge version 45.11.2.5101 or 45.11.2.5102 (the latest one from yesterday ). If you download it directly from the Google play store the version is 45.10.4.5088.
Hello, my maple G8141 can't connect to Internet, here is the part of logs about it
When Tap Data on in QS, it show LTE or 4G but not show on status bar icon, only show signal icon without "x", and no Internet connetion. No problem with WiFi.
I did all the correct steps to install it. I checked the data in fw before flash it and data working in fw. I have no idea how to use matlog, I did this one with adb shell logcat -b all. Hope RR can working normally on my maple really love this ROM, and cheers Shujath for the great job, really appreciate it.
11-23 23:23:06.282 2114 2152 D SubscriptionController: [getActiveSubscriptionInfo]+ subId=1 subInfo={id=1, iccId=893401137[****] simSlotIndex=0 carrierId=678 displayName=Orange carrierName=Orange nameSource=1 iconTint=-16746133 mNumber= dataRoaming=0 [email protected] mcc 214 mnc 03mCountryIso=es isEmbedded false nativeAccessRules null cardString=893401137[****] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = [] hplmns = [] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
11-23 23:23:06.282 1788 1929 D DataUsageController: setMobileDataEnabled: enabled=false
11-23 23:23:06.283 1788 1929 D TelephonyManager: setDataEnabled: enabled=false
11-23 23:23:06.286 2114 4435 D QcDataStatusNotification Service: onChange():uri=content://settings/global/mobile_data authority=settings path=/global/mobile_data segments=[global, mobile_data] uriLastSegment=mobile_data
11-23 23:23:06.286 1398 1398 V SettingsProvider: Notifying for 0: content://settings/global/mobile_data
11-23 23:23:06.286 2114 4435 D QcDataStatusNotification Service: handleMessage: Data Enable changed to 0 on phoneId = 0
11-23 23:23:06.286 2586 2586 D QcrilMsgTunnelIfaceManager: handleMessage what = 3
11-23 23:23:06.287 2586 2586 I QcrilOemhookMsgTunnel: [0]invokeOemRilRequestRaw: serial=1025 length=20
11-23 23:23:06.286 2114 2152 I chatty : uid=1001(radio) Binder:2114_2 identical 2 lines
11-23 23:23:06.287 2114 2152 D SubscriptionController: [getActiveSubscriptionInfo]+ subId=1 subInfo={id=1, iccId=893401137[****] simSlotIndex=0 carrierId=678 displayName=Orange carrierName=Orange nameSource=1 iconTint=-16746133 mNumber= dataRoaming=0 [email protected] mcc 214 mnc 03mCountryIso=es isEmbedded false nativeAccessRules null cardString=893401137[****] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = [] hplmns = [] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
11-23 23:23:06.288 2114 2114 D DCT-C : isEmergency: result=false
11-23 23:23:06.288 2114 2114 E CarrierActionAgent: [0]Unsupported action: 5
11-23 23:23:06.288 2114 2114 D CarrierActionAgent: [0]EVENT_MOBILE_DATA_SETTINGS_CHANGED
11-23 23:23:06.288 2114 2114 D SubscriptionController: [getActiveSubscriptionInfo]+ subId=1 subInfo={id=1, iccId=893401137[****] simSlotIndex=0 carrierId=678 displayName=Orange carrierName=Orange nameSource=1 iconTint=-16746133 mNumber= dataRoaming=0 [email protected] mcc 214 mnc 03mCountryIso=es isEmbedded false nativeAccessRules null cardString=893401137[****] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = [] hplmns = [] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
11-23 23:23:06.289 2586 2616 I QcrilOemhookMsgTunnel: [0]processOemHookResponse serial no: 1025 error: 0length=0
11-23 23:23:06.289 2586 2586 D QcrilMsgTunnelIfaceManager: handleMessage what = 4
11-23 23:23:06.289 2586 2586 D QcrilMsgTunnelIfaceManager: OEM_RIL_REQUEST_ASYNC_DONE requestAsync.sub :0
11-23 23:23:06.289 2114 2152 D use-Rlog/RLOG-QC_RIL_OEM_HOOK: QCRIL send data enable status DONE!
11-23 23:23:06.290 2114 2114 D CarrierSignalAgent: [0]Sending signal com.android.internal.telephony.CARRIER_SIGNAL_RESET to the carrier signal receiver: ComponentInfo{com.android.carrierdefaultapp/com.android.carrierdefaultapp.CarrierDefaultBroadcastReceiver}
11-23 23:23:06.290 2114 2114 D DCT-C : onDataEnabledChanged: enable=false, enabledChangedReason=2
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: detach=true reason=specificDisabled
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type default shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type mms shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type cbs shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type fota shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type supl shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type emergency shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type dun shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type hipri shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: APN type ims shouldn't be cleaned up.
11-23 23:23:06.290 2114 2114 D DCT-C : stopNetStatPoll
11-23 23:23:06.291 1398 1398 W AnomalyReporter: AnomalyReporter not yet initialized, dropping event=a3ab0b9d-f2aa-4baf-911d-7096c0d4645a
11-23 23:23:06.291 7650 7650 D CarrierDefaultBroadcastReceiver: onReceive intent: com.android.internal.telephony.CARRIER_SIGNAL_RESET
11-23 23:23:06.291 2114 2114 D DCT-C : cleanUpAllConnectionsInternal: mDisconnectPendingCount = 0
11-23 23:23:06.291 2114 2114 D ImsPhoneCallTracker: [0] handleMessage what=23
11-23 23:23:06.291 2114 2114 D ImsPhoneCallTracker: [0] onDataEnabledChanged: enabled=false, reason=2
11-23 23:23:06.294 7650 7650 D CarrierDefaultBroadcastReceiver: apply carrier action idx: 6
11-23 23:23:06.294 7650 7650 D CarrierActionUtils: onCancelAllNotifications
11-23 23:23:06.294 1398 1398 I notification_cancel_all: [10217,7650,com.android.carrierdefaultapp,0,0,64,9,NULL]
11-23 23:23:06.294 7650 7650 D CarrierDefaultBroadcastReceiver: apply carrier action idx: 8
11-23 23:23:06.294 7650 7650 D CarrierActionUtils: onDisableDefaultURLHandler
11-23 23:23:06.295 2114 2114 D SubscriptionController: getSubscriptionProperty Query value = -1
11-23 23:23:06.298 2114 2114 D ImsManager: updateVolteFeatureValue: available = false, enabled = true, nonTTY = true
11-23 23:23:06.304 1788 1929 I DataUsageUtils: Subscription is not active: -1
Thank you @Shujath
---------- Post added at 05:59 PM ---------- Previous post was at 05:59 PM ----------
Thank you @Shujath
4K
Youtube no 4k
Fix pls :crying:
Thank you Shujath
Thelight92 said:
4K
Youtube no 4k
Fix pls :crying:
Thank you Shujath
Click to expand...
Click to collapse
Add these line at end of build.prop
#4K for Youtube
sys.display-size=3840x2160
Thank you Shujath.
The only question is my xz premium is dual sim version but after I install this rom only sim1 works, what should I do to activate sim2?
I love RR but, it has random freezes follow by a reboot.
RR Is on the right track like always.
Today I have a couples of reboots when try to change the settings in the Resurrection tools menu.
No dark mode?
Thanks for this. Everything seems to be working on G142
Dark mode working here.
Yeah I found it lol
Hi,
I have just installed LineageOS for microg 19 (19-20220522-microg-bramble) on my Pixel 4a 5g and I am receiving a regular popup every few minutes saying that "Intent Filter Verification Service has stopped".
From what I have read this is used to call another application on the phone (based on what type of thing needs to be handled)??
The logs I am getting with logcat do not seem to lead me towards anything (see below from two examples). I'm not sure if anyone has any suggestions on what could be causing this or where else I can look??
My suspicion is that this is something to do with not having the google apps (using microg instead) but not sure. I did find one other mention of it here, but no solution
Note: I did have LineageOS for microg 18 installed previously which did not exhibit this behaviour...
Example1:
Code:
05-31 23:53:49.627 966 966 D Zygote : Forked child process 10622
05-31 23:53:49.628 1718 2114 I ActivityManager: Start proc 10622:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:53:49.632 10622 10622 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:53:49.644 1357 1429 I adbd : jdwp connection from 10622
05-31 23:53:49.646 10622 10622 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:53:49.638 0 0 I : c7 10622 binder: 10622:10622 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:53:49.651 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:53:49.655 10622 10622 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:53:49.658 10622 10622 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:53:49.668 10622 10622 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.687 10622 10639 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:53:49.689 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:53:49.757 10622 10641 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:53:49.757 10622 10641 E AndroidRuntime: Process: com.android.statementservice, PID: 10622
05-31 23:53:49.757 10622 10641 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:53:49.761 1718 10645 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
05-31 23:53:49.762 10622 10641 I Process : Sending signal. PID: 10622 SIG: 9
05-31 23:53:49.782 1718 14826 I ActivityManager: Process com.android.statementservice (pid 10622) has died: cch+5 CEM
05-31 23:53:49.782 1718 2118 I libprocessgroup: Successfully killed process cgroup uid 10074 pid 10622 in 0ms
05-31 23:53:49.782 966 966 I Zygote : Process 10622 exited due to signal 9 (Killed)
Example2:
Code:
05-31 23:54:24.620 966 966 D Zygote : Forked child process 10707
05-31 23:54:24.620 1718 2114 I ActivityManager: Start proc 10707:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:54:24.625 10707 10707 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:54:24.639 1357 1429 I adbd : jdwp connection from 10707
05-31 23:54:24.640 10707 10707 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:54:24.633 0 0 I : c3 10707 binder: 10707:10707 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:54:24.650 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:54:24.654 10707 10707 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:54:24.660 10707 10707 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:54:24.679 10707 10707 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.699 10707 10724 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:54:24.700 1718 4358 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211 response handler invoked
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211_response_handler: cmd 103, vendorID 4980, subcmd 13 received
05-31 23:54:24.727 1017 2427 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-31 23:54:24.765 10707 10726 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:54:24.765 10707 10726 E AndroidRuntime: Process: com.android.statementservice, PID: 10707
05-31 23:54:24.765 10707 10726 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:54:24.768 1718 10731 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
Sorry I don't have a solution for you but since you are using LineageOS+microG on a Pixel phone, you might be interested in switching to CalyxOS as they seem to already have a workaround in place even though the bug isn't fixed yet.
See here under "Issues":
CalyxOS News
📰 Read about what we're working on, important announcements, and upcoming events.
calyxos.org
Relevant commit:
https://review.calyxos.org/c/CalyxOS/vendor_calyx/+/7976
As a bonus, with CalyxOS you also get better security than just LineageOS+microG thanks to bootloader relocking.
I am suffered by that bug too. I can't see any harm by this, but it is annoying. The patch in CalyxOS is just to hide that problem as a workaround.
I filed a bug report here:
Intent filter verification service / com.android.statementservice regularly crashing on LineageOS for microg · Issue #1740 · microg/GmsCore
I am aware this is a very unclear specification of a bug. It is not clear who and what is responsible for this - can be also Android12 (LOS). But it seems to be that the combination of LOS and micr...
github.com
Please report there all your findings @maloo1 and @johnfocker
So I ended up following @johnfocker's suggestion and installed CalyxOS (android 12) and it does "fix" the issue.
I guess Calyx is a perfect fit for my needs anyway (microg, locked boot loader, great polished daily driver) so Ill probably stick with it unless I end up with a phone that is not supported.
It would make sense to have it fixed in microg thou if thats the root cause... I'll see what I can add to the bug...
Thanks again!
Very strange. The messages disappear to pop up after some time.
Lately I installe the new Magisk 25 and BetterBatteryStats (XDA) and it appears again - althoug I am not sure that was really reason. There is continiously changes in phone, so difficult to nail it down.
Quote from flipreverse:
This seems to be a bug in AOSP: https://android.googlesource.com/platform/frameworks/base/+/4978d1ad10293900e9b5feea349abd09ceb6e710
The LOS repo android_frameworks_base does not have this commit at the moment. I'll cherry-pick that one, and give it a try.
Click to expand...
Click to collapse
ale5000 said:
Quote from flipreverse:
Click to expand...
Click to collapse
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
kurtn said:
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
Click to expand...
Click to collapse
Yes.
ale5000 said:
Yes.
Click to expand...
Click to collapse
Just too late for the lineage.microg.org August round of builds.