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.
I'm not well versed in this type of work but I'm using a Samsung S4mini and Windows 10. From this debugging report, can someone help me figure out what is wrong ?
11-23 19:07:00:793 W/I Tool version : 3.19
11-23 19:07:00:793 W/I adb.exe
11-23 19:07:00:793 W/I aapt.exe
11-23 19:07:00:923 W/I Android Debug Bridge version 1.0.31
11-23 19:07:01.84 A/W process (30772) : Implicit intents with startService are not safe: Intent { act=service.tracetool.SocketService.ACTION (has extras) } android.content.ContextWrapper.startService:506 android.content.ContextWrapper.startService:506 service.tracetool.TTBroadcastReceiver.onReceive:41
11-23 19:07:01.85 A/I UsbThread : thread main : wait current UsbThread to terminate 0
11-23 19:07:01.85 A/I UsbThread2.run() needToBeClosed is true
11-23 19:07:02:510 W/I Wait java service
11-23 19:07:02:617 W/I waiting android server connection ... 1
11-23 19:07:02.25 A/I UsbThread2 : thread stopped
11-23 19:07:02.35 A/I TunnelController : thread stopped
11-23 19:07:02:875 W/I Waiting for connection
11-23 19:07:02.76 A/I TunnelController : thread stopped
11-23 19:07:02.86 A/I UsbThread3 : usbServerSocket : Waiting for the host to connect
11-23 19:07:05:108 W/I Sending busybox21
11-23 19:07:04.94 A/E UsbThread3.run() loop error. firstByte : 39 : WTOA_copyFile
11-23 19:07:04.94 A/E UsbThread3.run() loop error. lastCommand : 32 : WTOA_setGlobalVar
11-23 19:07:04.94 A/E UsbThread3.run() loop error. Exception type : class java.io.FileNotFoundException
11-23 19:07:04.94 A/E UsbThread3.run() loop error. Exception message : /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E UsbThread3.run() loop error. Exception cause : libcore.io.ErrnoException: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E UsbThread3.run() loop error. Exception string : java.io.FileNotFoundException: /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E libcore.io.IoBridge.open(IoBridge.java:409)
11-23 19:07:04.95 A/E java.io.FileInputStream.<init>(FileInputStream.java:78)
11-23 19:07:04.95 A/E service.tracetool.Api.copy(Api.java:1471)
11-23 19:07:04.95 A/E service.tracetool.UsbThread.copyFile(UsbThread.java:1944)
11-23 19:07:04.95 A/E service.tracetool.UsbThread.run(UsbThread.java:316)
11-23 19:07:04.96 A/E UsbThread3.run() -> unexpected disconnection
11-23 19:07:04.96 A/I UsbThread3 : usbServerSocket : Waiting for the host to connect
11-23 19:07:15:538 W/D UsbThread : ReadBytes : Connection Closed Gracefully.
Server List at 11-23 19:08:05:322
DNS List
24.200.241.37
24.202.72.13
24.200.0.1
192.168.42.129
Did you use supersu?
Which version android?
Use busybox?
erkin98 said:
Did you use supersu?
Which version android?
Use busybox?
Click to expand...
Click to collapse
Sorry for not updating my posting but by reading other postings I tried to install Busybox on its own and it worked for me. Thanks for looking into it for me
GANBRO said:
Sorry for not updating my posting but by reading other postings I tried to install Busybox on its own and it worked for me. Thanks for looking into it for me
Click to expand...
Click to collapse
Your welcome
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
Anyone know of an app that I can use to track reboots and to try and find out why they are happening?
Mine has been sent out for "repair" a couple times and they can't figure out why it's happening. I'm getting so tired of this, I'd like to make absolutely sure that it's not an app I'm running. Although it does happen with a "stripped down" version of what I'm running.
logcat, dmesg, last_kmsg? Maybe:
https://play.google.com/store/apps/details?id=com.tortel.syslog
So the phone rebooted on me after less than a day of having it back. I was able to get the dumpstate and I can see where it rebooted, but I just don't know how to interpret the info. Can anyone help?
Code:
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #1: 2 when =46076699 package=com.google.android.gmsoperation =*walarm*:com.google.android.gms.gcm.ACTION_CHECK_QUEUE
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #2: 2 when =46093358 package=androidoperation = null listenTag =*job.delay*
12-06 07:05:56.722 1392 1392 I DeviceIdleController: updateChargingLocked: charging=false
12-06 07:05:59.999 1392 2067 V AlarmManager: Triggering alarm #0: 3 when =46108403 package=androidoperation =*alarm*:android.intent.action.TIME_TICK
12-06 07:06:16.323 5536 5536 E AndroidRuntime: FATAL EXCEPTION: main
12-06 07:06:16.323 5536 5536 E AndroidRuntime: Process: com.android.bluetooth, PID: 5536
12-06 07:06:16.323 5536 5536 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-06 07:06:18.183 12055 12055 I chatty : uid=1000 system_server expire 15 lines
12-06 07:06:18.446 12055 12145 I chatty : uid=1000(system) CpuTracker expire 1 line
12-06 07:06:18.450 12055 12090 I chatty : uid=1000(system) batterystats-sy expire 1 line
12-06 07:06:18.452 12055 12055 I chatty : uid=1000 system_server expire 1 line
Reboots monitor can notify for not voluntary reboots
https://play.google.com/store/apps/details?id=com.ryosoftware.rebootsmonitor
Seems like a bluetooth problem