Hey all,
Currently running CM 10.2 on my One XL. Using proper gapps and 3.18 radio. 3.4.11-gf8fed45 kernel.
All is well and I find the experience fantastic. The issue is that the camera is non functional. Going to start the camera results in a black screen with the camera UI overlay. It will then inform me that gallery has to close.
I have tried full clean installs, revert to a sense rom, change the radio, install different camera apks, used 3rd party apps, nothing results in success. I've scoured the forum here and elsewhere and no suggestions solve it. The front camera does work, but mine currently has dust in it...different story.
Bar myself going in and ensuring the camera pin is connected is there any other method to fix this? I'd rather like to have my camera functional.
Have you tried running an RUU?
Sent from my Evita
timmaaa said:
Have you tried running an RUU?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I've gone back down to 1.85 and then back to 3.18. No avail
If it doesn't work after an ruu then it's hardware related
Sent from my VENOMized HoxL
I have the same trouble. I installed cm 10.1 after running 3.18 ruu and everything was perfect. The in runned the ruu again because I was selling my phone and needed to be stock, and the problem appeared. I have intalled cm 10.1 and 10.2 after running ruu and nothing appears to solve the problem. The camera works at the first boot but after unlocking the phone when it goes to sleep mode the camera just shuts down. Ahother thing is that when I have the phone in usb storage mode the camera works, but obviusly it sais that an sd card is needed.
Alright, so some things are going one and I believe I'm headed in the right direction. I mispoke earlier saying I had run RUU and so I went a ran RUU for 3.18, appeared to be on 2.20 previously. This led to no camera improvement. So it seemed the last ditch effort was to RUU to an older version and I attempted 1.85 RUU. Except it sticks on the sending screen and does not complete the RUU. So I RUU back to 3.18 again to ensure any changes are corrected. Upon boot, I open the camera, can see the viewfinder, which works properly for a few seconds before crashing.
Thus, leading me to believe it is not actually a hardware issue, as the camera was physically functioning before exiting. Now, as to why none of the older RUU work I have no idea, no what a next solution could be. Advice, help?
I've seen this problem reported across numerous devices, maybe you'll need to do some serious digging on the net.
Sent from my Evita
timmaaa said:
I've seen this problem reported across numerous devices, maybe you'll need to do some serious digging on the net.
Sent from my Evita
Click to expand...
Click to collapse
I've also encountered it multiple times in different contexts, and have done plenty of digging. The most promising lead at this point is possibly a kernel issue, though wouldn't that be reset during RUU? I think I'll try a new/custom kernel and see what happens.
Yeah, the stock kernel is installed during an RUU. Every time you flash a different ROM a new kernel is installed along with the ROM.
Sent from my Evita
It appears I'll be camera less for a while. I've flashed RUU, wiped multiple timed over, installed multiple ROMS and kernels and the camera refuses to work.
If anyone has a fix or suggestion please let me know!
Getting a log might give a clue as to what's going on.
I've pulled the log and found what the issue appears to be.
CAM_PhotoModule attemps to set Width = 3264 and Height = 2448
This shows as an error.
Also, interesting to note that the camera overlay does show as if the phone were in landscape orientation. Hence the width and height being switched. Perhaps this causes it.
After, java.lang.RuntimeException: startPreview failed at android.hardware.Camera.startPreview(Native Method)
and then camera closes.
It seemes to me that the preview is being set at too large of a size by CAM_PhotoModule, and subsequently that startPreview method fails. Where is the CAM_PhotoModule located so I can go in and change the height and width to see if that helps. Else it looks to be a hardware issue.
http://pastebin.com/93mW2Wpv
The logcat from attempting to open the camera is there, see lines 179, 267 for what I see as the issues.
Anyone got an idea or possible solution?
cheers
Related
I get a black screen in Camera, Camcorder,
I'm using the XTv2MIUI ROM.
Anybody can help to fix it. Have install back to the 2.1 stock rom, format the SD ,deleted the 3rd party cam apps. Still can't fix it.
tubekeeper said:
I get a black screen in Camera, Camcorder,
I'm using the XTv2MIUI ROM.
Anybody can help to fix it. Have install back to the 2.1 stock rom, format the SD ,deleted the 3rd party cam apps. Still :confused can't fix it.
Click to expand...
Click to collapse
Wow so even after flashing back to stock you're still getting black screen? I've seen the black screen a few times with miui but not everytime. I was hoping it would be fixed with the final v5.
thats weird. the first time a flashed Miui I had that same problem. I just reflashed the same rom and the problem went away. I have never carried the black screen through multiple roms.
Even I flash back to the stock rom by RSD the black screen can't fixed. I already replaced the camera module but not fixed.
Do you use autokiller memory optimizer? I got black screens when I set it above strict. If you do maybe youd want to lower those settings.
I didn't install the auto killer, But even i flash back to 2.1 stock rom without any tweak apps,it still can't fixed the black screen
Hmm, same issue in several ROMs, sounds like an hardware error.
I have found the following in Loyat Forum:
(http://forum.lowyat.net/topic/1667176)
Help! My camera shutter suddenly closed up and can't open anymore. Is this normal or my phone is screwed?
This is a known issue for xt720. Not all of them though but quite a number have experienced it already where the shutter just completely shut. There's nothing much can be done other than sending it back for warranty... OR you can try this trick. Get a magnet and put its South field close to the shutter. Apparently it will open up. Not sure how true is this but yea.... better than dismantle the whole phone just to find out you really screw the phone up for good...
Maybe this could help...
try-and-error said:
Hmm, same issue in several ROMs, sounds like an hardware error.
I have found the following in Loyat Forum:
(http://forum.lowyat.net/topic/1667176)
Help! My camera shutter suddenly closed up and can't open anymore. Is this normal or my phone is screwed?
This is a known issue for xt720. Not all of them though but quite a number have experienced it already where the shutter just completely shut. There's nothing much can be done other than sending it back for warranty... OR you can try this trick. Get a magnet and put its South field close to the shutter. Apparently it will open up. Not sure how true is this but yea.... better than dismantle the whole phone just to find out you really screw the phone up for good...
Maybe this could help...
Click to expand...
Click to collapse
I will try. I have replaced the camera module and it work for a while and then black screen again.
[Solved]
Finally solved by replaced the motherbroad from service center.
Thanks all the comments provided!!!
Hello,
When the JB-update came last year, i was disappointed and rooted my phone and wanted to try out some custom roms.
But, when i switched from ViperOneS to Trickdroid, my touch input was suddenly mirrored (touching on the bottom-left side is recognized as touching on the bottom right side, in portrait mode). From then on, it was always this way,changing roms did not change anything on that behaviour.
BUT:
Int TWRP the touch input is perfectly fine, not mirrored, its just like before.
When it happened, i asked in a german android forum, but i got no good answer there, so i searched around and came up with a workaround: i modified the touch driver source (from htc-dev) in the kernel and recompiled it ( changed "input_report_abs(idev, ABS_MT_POSITION_X, fdata->x);" to "input_report_abs(idev, ABS_MT_POSITION_X, 540-(fdata->x));".
That worked, but i could feel that all input was slowed down.
Now, after i read that we can make the phone S-Off, i thought "hey, the ruu changes more than just system data and boot, maybe that will fix it".
But it didn't. And the slowed down reaction is annoying me more and more.
Please, anyone got a clue on what went wrong, or how to solve it? I am pretty sure its not a Hardware problem, because its working in TWRP. As i understand, TWRP is build from android sources too, why is it working as before, while full Android isn`t?
Please help!
Phone: One S with S4 Processor, hboot 2.15, rooted, s-off
Silfa said:
Hello,
When the JB-update came last year, i was disappointed and rooted my phone and wanted to try out some custom roms.
But, when i switched from ViperOneS to Trickdroid, my touch input was suddenly mirrored (touching on the bottom-left side is recognized as touching on the bottom right side, in portrait mode). From then on, it was always this way,changing roms did not change anything on that behaviour.
BUT:
Int TWRP the touch input is perfectly fine, not mirrored, its just like before.
When it happened, i asked in a german android forum, but i got no good answer there, so i searched around and came up with a workaround: i modified the touch driver source (from htc-dev) in the kernel and recompiled it ( changed "input_report_abs(idev, ABS_MT_POSITION_X, fdata->x);" to "input_report_abs(idev, ABS_MT_POSITION_X, 540-(fdata->x));".
That worked, but i could feel that all input was slowed down.
Now, after i read that we can make the phone S-Off, i thought "hey, the ruu changes more than just system data and boot, maybe that will fix it".
But it didn't. And the slowed down reaction is annoying me more and more.
Please, anyone got a clue on what went wrong, or how to solve it? I am pretty sure its not a Hardware problem, because its working in TWRP. As i understand, TWRP is build from android sources too, why is it working as before, while full Android isn`t?
Please help!
Phone: One S with S4 Processor, hboot 2.15, rooted, s-off
Click to expand...
Click to collapse
have you found a fix for this by chance? or can you explain how you changed the kernel in your workaround?
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
Are you completely stock? Any custom kernel? Any rom?
Usually it's a kernel issue - tearing, but it's only present on custom kernels (never came across on the stock cm11 kernel). You might wanna try a different kernel though, if you're comfortable with that.
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
mupper said:
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
Click to expand...
Click to collapse
Was it working before those changes?
edit:
Perhaps this might help?
http://forum.xda-developers.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
I had exact same issue during recording a video yesterday night !! I am latest mahdi and latest franco...
Funny thing is it went away once i exited the camera... what rom and kernel are u using ?
I've been having the same issue too. I don't have a solution for you, though. I haven't been able to find much about it.
Same issue here, stock all the way, only been since latest update. The update didn't flash properly, it gave an error stating it couldn't be located but i went through the files and it was there and then upgraded OK
I had the same problem. Selecting "Force GPU Rendering" in developer options cured it.
i have stock everything. i'm not rooted.
a reboot fixes the problem temporarily. shoot, all the issues i've ran into with this phone thus far (like the GPS not locking on) is fixed by a reboot. i know a reboot is good to do every now-and-again regardless, but having to do it constantly to fix issues is the sign of a failing device and is very annoying; it shouldn't be something you have to do with a brand new device.
i am facing this too randomly. Am on rooted 38R with Franco kernel. Rebooting is a temp cure but it will frustrating to keep doing it.
This happened to me after getting 38R. Fortunately it hasn't been back since a hard reboot. It would show up on Youtube & when dragging down the notifications area.
I had this today on PAC ROM. When I unlock phone and lock ring animation dots flash up made lines come across screen not sure what it was or why. Just rebooted phone. Back to normal. But trying out vanir later tonight try something abit different.
Also experiencing this here.
Stock ROM, clean 38R install.
Stock kernel.
Rooted, with a few xposed modules.
Started a day or two ago. Haven't found a way to recreate it. When it does happen, a reboot remedies it, but only temporarily.
I will attempt to screenrec it the next time.
I find it interesting that I only see mentions of this starting recently.
Same problem for me since the last update. Restarting the Phone solves the problem for some times. Maybe a driver issue?
Glad to see that it is not a hardware issue.
Same here
Same here, mahdi-2.8-bacon-20141001 ROM, enabled "Force GPU rendering" in Developer options, let's see if this comes back!
I have the same problem on latest cm nightly with stock kernel. And dev options works sometimes but it resets on reboot and my phone reboots randomly all the time. I'm starting to hate this device
Sent from my A0001 using Tapatalk
I also have the same issue on Stock 38R update + franco kernel r27
It happens after the latest kernel update, before I never had this lines.
Lucky for me I don't have any reboots now but I fear that will come to pass as well.
Got the same problem with Mahdi Rom 2.8 - 20141016
Will be solved in Franco Kernel r28,he just confirmed this on his kernel thread.
Sent from my OnePlus One using XDA Free mobile app
same issue here. i have to reboot. its happened on stock and AK kernel. will try enabling force gpu rendering and see if it comes back
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.1.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
bakmanhans said:
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.2.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
Click to expand...
Click to collapse
I've been tempted by the idea of jumping the MaximusHD rom ship for a while too. Are you happy with the camera performance? One of the reasons I'm reluctant to go the non-Sense rom way is the lack of the full hardware access to the camera on those roms.
I just jumped the ship three days ago. I didn't use the camera besides taking 3 pictures for test purposes. I'm a long time Camera ZOOM FX user so the app installed itself again. I replaced the CM12 camera app in the drawer with it.
I need more user experience time with the camera to tell you it lacks in any way.
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
bakmanhans said:
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
Click to expand...
Click to collapse
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
twotimer said:
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
Click to expand...
Click to collapse
I can't find slow motion video. I never saw it in the MaximusHD ROM either. ZOOM FX cam does have the HDR option, just like with MaximusHD. But seriously, it's nothing more than a gimmick. Do you ever use it?
twotimer said:
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
Click to expand...
Click to collapse
With stock CM camera I don't see these options. This cam app is really minimal. Some say you need to set resolution by entering the hamburger menu upper-left but I don't have the menu. App version is 2.0.002.
With ZOOM FX Premium all resolutions settings are there.
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
bakmanhans said:
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
Click to expand...
Click to collapse
It's not part of the ROM, it's rather a part of the bootloader itself. You can change it by flashing a modified bootloader version:
http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Just read the thread on how to do that and find the one that fits your HBOOT version.
Coming from MaximusHD my hboot is at version 2.16... I don't see any download for that.
I've been using 20151223 UNOFFICIAL for some time now without the camera/flashlight issue. I've been using the camera more than once during the holidays.
Only trouble I have is getting cellular (3G) back online after flight modus. It's not possible. I have to restart the device every time. Anybody else experiencing this?
No, working great here on 2015-12-23 Unofficial HBOOT 2.16 from Flyer. When going out of plane mode, it takes around 15 seconds to get H icon (for HSDPA, 3G if you prefer). It may be a problem with the SIM card or advanced operator settings.
I'm facing an issue with my camera which I couldn't find anything about via a web search. So I would like to know if anyone experienced something similar?
I'm running the stock rom and didn't tinker with the phone.
Since yesterday my rear camera is really slow an only slowing blurred images. The whole phone seems to be running really slow and unable to handle the data. Switching to the front camera takes ages but once it's active it's working normally.
If I try to use the camera several times I end up with a black preview image. A reboot returns the camera to the previous laggy state.
Changing to a different camera app yields the same behavior. Could be an issue with the latest patch for Android 12 I i installed around the same time or my hardware is fried...
stephael said:
I'm facing an issue with my camera which I couldn't find anything about via a web search. So I would like to know if anyone experienced something similar?
I'm running the stock rom and didn't tinker with the phone.
Since yesterday my rear camera is really slow an only slowing blurred images. The whole phone seems to be running really slow and unable to handle the data. Switching to the front camera takes ages but once it's active it's working normally.
If I try to use the camera several times I end up with a black preview image. A reboot returns the camera to the previous laggy state.
Changing to a different camera app yields the same behavior. Could be an issue with the latest patch for Android 12 I i installed around the same time or my hardware is fried...
Click to expand...
Click to collapse
I would try a system reset if possible, I know its a pain but if it works problem solved, You could also try going back to a different build via android flash tool , just a couple of ideas although extreme ,would narrow it down even more to a hardware issue over corrupt software. Hth
hammered58 said:
I would try a system reset if possible, I know its a pain but if it works problem solved, You could also try going back to a different build via android flash tool , just a couple of ideas although extreme ,would narrow it down even more to a hardware issue over corrupt software. Hth
Click to expand...
Click to collapse
I feared that I would have to do this. Factory reset and flashing an older version didn't help.
Now I can hear that something is moving inside when I shake the phone. Time to crack it open and have a look.
Thanks for the suggestions.