Database Develop

Help Please!! Incredible S Camera fatal problem!

Hey guys,
Not sure anybody met this problem before.
My camera just happen to restarting when I open it. Last time it works fine and now it's like this. I didn't change anything in the system or install any software. Just restarting. To be specifically, when I entered the camera, camera vision shows, then screen black after 1 second and vision comes back. It repeats again and again. But, if I switch to cam record during the vision appears, the cam recording function works good.
Not only the camera app, but other apps involving a camera function like barcode scanner, google shoppers, the camera restarting again and again.
Anybody knows what's going on?

Doesn't sound like software problem. I suggest take it to the service center for replacement.

My camera has stopped working all together, every time I open the camera or camcorder app, it quickly flashes the icon and then either returns to the home screen or it hangs on a black screen. Although our problems are different, I wonder if other people are having troubles with their cameras. I have done a hard reset and it still doesn't work, so mine also seems to be a hardware issue and I will be returning mine shortly, perhaps you should do the same.

stupid question probably: have you tried a reboot? and i mean a real reboot.
Disable the fastboot or pull the battery, maybe it helps maybe it doesnt.
If thats not going to work i would say: factory reset and if it still doesnt work its time for the service center.
it can also be that there are some faulty images/files on your sd-card so if you have a spare, try that one

I had the same issue with my camera, starting with the logo and then only black screen. Other apps using the camera like Barcode scnanner had the same issue. After contacting HTC they told me to remove the battery for 30s and then reboot. That did the trick for me and the camera went back to normal.

Came across similar problem with a HTC desire, turned out to be the sd card having a fault! Not sure why but when replaced SD card the thing worked great as it should. Just a thought for you but a hard reset and battery out for a minute or two could help.

Ty for the tips guys, will remember them, I learn something new everyday in here haha.
Sent from my HTC Incredible S using XDA App

Try resetting the camera to factory default....

wipe it !!!!!!!

I had this problem, but restarting it solves it.

i think i know how 2 fix it...it is a weird roundabout solution
-goto ur gallery
-select the latest photo you have taken from your camera(or basically any photo taken from your mobile will work)
-here`s the tricky part...long press the photo,and select "show on map" from the menu
-let the mobile take its course using the maps installed on ur phone(it should take 2-3 mins max depending on ur speed of course)
-u r DONE!!!!!!!!!!!!! the camera should work just fine now
***** what happens is that the photo tries to tag itself from the location involved which sends it 2 a continuous loop hence the camera stops working*****
if any queries,PM me

coolxcali said:
i think i know how 2 fix it...it is a weird roundabout solution
-goto ur gallery
-select the latest photo you have taken from your camera(or basically any photo taken from your mobile will work)
-here`s the tricky part...long press the photo,and select "show on map" from the menu
-let the mobile take its course using the maps installed on ur phone(it should take 2-3 mins max depending on ur speed of course)
-u r DONE!!!!!!!!!!!!! the camera should work just fine now
***** what happens is that the photo tries to tag itself from the location involved which sends it 2 a continuous loop hence the camera stops working*****
if any queries,PM me
Click to expand...
Click to collapse
Works but only 1 time...now the front camera can't function

wipe and install new rom

if software problem
Boot into recovery
wipe cache and Dalvik Cache & reboot
If it is a software problem, ie. if it was working earlier, should revert back to working condition!
Old thread, I know, but might help someone
Cheers!

try removing battery for 30secs, then reboot

Did anyone get a fix for this problem?
My camera has now stop working and I can´t get it to work again. Help Please.

strumpan76 said:
Did anyone get a fix for this problem?
My camera has now stop working and I can´t get it to work again. Help Please.
Click to expand...
Click to collapse
Have you got a custom ROM or the stock ROM?

[Q] Camera GPS tagging feature keeps shutting off. Why?

I have an un-rooted Galaxy Note (1) GT-N7000B running the latest 4.0.4 ICS Android.
Going back at least to June when I got the first version of Ice Cream Sandwich (and maybe earlier) I began to notice that sometimes I find the GPS-tag feature of the camera has reverted to "off". I don't know why this is happening? It is not immediate; it is usually after a few weeks. Inevitably, it is discovered after I have taken some photos that I thought were being tagged, then come to find they were not because the GPS-tag feature has reverted to "off".
Any ideas as to what triggers this to happen?

Percy Dolarhyde said:
I have an un-rooted Galaxy Note (1) GT-N7000B running the latest 4.0.4 ICS Android.
Going back at least to June when I got the first version of Ice Cream Sandwich (and maybe earlier) I began to notice that sometimes I find the GPS-tag feature of the camera has reverted to "off". I don't know why this is happening? It is not immediate; it is usually after a few weeks. Inevitably, it is discovered after I have taken some photos that I thought were being tagged, then come to find they were not because the GPS-tag feature has reverted to "off".
Any ideas as to what triggers this to happen?
Click to expand...
Click to collapse
Turning GPS to off *may* turn off the geo-tag feature..just turn geo-tag on, then come back, turn off the gps & again go & check if the geo-tag is on or off..I may b wrong, but plz try it once..

Yes shyamub4u, you are correct. Toggling GPS off turns off the GPS-Tagging feature in the camera, while turning GPS back on does not return GPS-Tagging in the camera to it's previous ON state.
Thing is, I was never turning the GPS off in the first place. But I'm guessing on a few occasions when the battery got down pretty low it went into the Power Saving mode, which killed the GPS, which in turn killed the GPS-tagging feature in the camera.
I will play around with the settings a bit later when my battery is down lower than it is now, and confirm this is what's happening. If so, I can adjust custom power settings to avoid this from happening again in the future.
Thanks

Percy Dolarhyde said:
Yes shyamub4u, you are correct. Toggling GPS off turns off the GPS-Tagging feature in the camera, while turning GPS back on does not return GPS-Tagging in the camera to it's previous ON state.
Thing is, I was never turning the GPS off in the first place. But I'm guessing on a few occasions when the battery got down pretty low it went into the Power Saving mode, which killed the GPS, which in turn killed the GPS-tagging feature in the camera.
I will play around with the settings a bit later when my battery is down lower than it is now, and confirm this is what's happening. If so, I can adjust custom power settings to avoid this from happening again in the future.
Thanks
Click to expand...
Click to collapse
I think u r right..powersaving mode will turn of the gps once its <15%, if I am not wrong..once if u find this is the exact reason, plz let us knw

[FAQ] - Known bugs & issues for the HTC ONE (M7)

Like every other device on the market, the HTC ONE is not perfect, both at device and software levels it is likely that some glitches and hitches will be discovered, this is exactly the place to report those bugs. It is important here to distinguish between a bug from the device and a bug from an XDA ROM developer, the latter case must be reported in the appropriate topic and not here.​
Confirmed or Known BUGS:
BUG : I find that on the odd occasion my back button or home button becomes dead.
SOLUTION : Have a read HERE​
BUG : Beats causes a hissing background noise, most noticeable at low volumes.
SOLUTION : Some say disabling WiFi and re enabling it solved their issue.​
BUG : Bluetooth streaming audio issues, audio keeps cutting out.
SOLUTION : Some has solved this by disabling the energy saving options or simply turn OFF WiFi. To discuss this issue click HERE​
BUG :
SOLUTION :​
BUG :
SOLUTION :​
Post your bugs and issues and if they get confirmed frequently I will add them to this list.​​

I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.

I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something.
Click to expand...
Click to collapse
Also beats causes a hissing background noise, most noticeable at low volumes.

Xperia23 said:
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=2231832

Thank you guys, OP updated.

the cursor jumps into false positions, when i drag it to one. (keyboard)
Sometimes my keyboard disappears, when i was writing and no i didnt pressed back or anything like this.
o2 v1.27 firmware

I had a weird issue in the car the other day
I was using the USB plugged into a Fiat 500 which has the Blue & Me system. I wasn't particularly bothered about having sound through the speakers, I just wanted to charge.
The stereo turned on anyway, and I was having random directions given through the stereo, with the Highlight Video music in between!! And then the ACTUAL directions coming through the phone speakers. I just turned the stereo off but it was really weird
Martin

I've had problems with random restarts and WiFi not connecting/WiFI settings freezing. Not allowing WiFi to be switched off during sleep seems to have cured it.

HTC One M7 speaker
I got my new HTC one the othe day from Harvey Norman and I have noticed that the bottom one of the two speakers cuts in and out and if you press on it then it works, but this is for all audio has anyone had this issue or know why it is happening?
Thanks

I got my HTC One last week and the wifi signal is really weak. When I am at 5mt from the hub (virgin media) I bearly have a signal.
My boyfriend's Xperia Z (with known wifi issues) has more signal at the same distance.
Anyone else experiencing this?

Phone in pocket after call
I am surprised no one has reported this annoying bug:
1) Have the phone in the pocket
2) Listen to music via the provided headphones (same if you use bluetooth)
3) Someone calls you and you answer via headphones button
4) After you or the other party hangs the phone, the phone turns on in the pocket.
VERY annoying!!! Please report this bug to HTC (I already did)
Otherwise I just LOVE this phone!!!

Problems charging phone and file transfers.
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.

xqlusive84 said:
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.
Click to expand...
Click to collapse
Sounds like you have accidentally bent some pins in the connection, potentially hardware not software related. I'd return for exchange.

2G connection issues
I have no idea whether its my ONE's problem or of the connection provider........ I cant use my 2G connection, it connects and disconnects at its will........Is there any way to test whether my ONE has any problem?

Strangeness with touch screen sounds
I may be the the only one.... but I like a click sound when the touch screen is presssed for a command. This works alright on my Sensation (pyramid) but not on my new HTC (M7).
There is sometimes a very very faint noise about a second or more after touching the screen for a command, kind of a delayed reaction? Anyway no amount of tweaking volume controls or using any sound mod produces a decent loud click sound. I revert any tweaks after experimenting with them.
Setup; HTC M7ul - ARHD ROM (12 currently)
Any information on this would be gratefully received!

This has been annoying me for the past week...
When I make or receive a call people tell me that they hear me far away. People cant tell its me on the phone! Gonna try to clean the speakers with a toothbrush but this phone is fairly new, bought it in September...

Push Bug (Whats app, sms), htc stay in standby
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school

thepate94227 said:
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school
Click to expand...
Click to collapse
Sounds like you've set your minimum frequency/screen off to too low, increase it to around 800Mhz and see whether you face the same problems again.
Sent from my iPod touch using Tapatalk

thepate94227 said:
so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too.
Click to expand...
Click to collapse
There's a fix for the camera bug in Venom Hub/Addons/Other

Thank you for your answers
@spiralOut
Thank you, this add-on fixed the camera bug, I hope, it fix the other too
@n1234d
Do you mean the undervolt option during the elemtalx kernel installation? Because first I choose 800kHz, now I choose stock, I think the stock is higher than 800, right? And the bug still appeared.
And what I forget to say: I used the swift option from HTC, that i can write with swiping on my keyboard, maybe this has something to do with the bug, now today I deactivated it.

[Q] [CM11] Reboots with every notification with screen off

Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off

Strange bug indeed and i have no idea why. The vibration on boot is always there to tell that bootloader boots. Its easier to troubleshoot a black phone that way, according to the service manual.
Sent through time and space from my s3mini/CM11

Jucarez said:
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Click to expand...
Click to collapse
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:

Meticulus said:
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Click to expand...
Click to collapse
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance

Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11

i have the i8190 and have the same problems
So I'm using Carbon and Slimkat, works perfectly fine

Jucarez said:
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Click to expand...
Click to collapse
Did you try it ?

tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!

Hi guys,
I tried it. It's working perfectly. Hallelujah!
Now I'm discovering the Xposed to do a lot of other things (autohide the navbar, disable the "3-dot" button on apps, etc)
Thank you very much!

down
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Click to expand...
Click to collapse
LMH1998 said:
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Click to expand...
Click to collapse
Jucarez said:
I tried it. It's working perfectly. Hallelujah!
Click to expand...
Click to collapse
Unfortunately, the workaround "patch" is not available anymore :crying:
would it be possible to upload it again anywhere, maybe here?
or is there another possibility to fix that problem yet?

Flashlight/Camera Bug Back in 5.1

Remember the bug a while back where if you turned on the flash, it would time out in a minute or so and turn itself off? And then you would get the "Cannot connect to camera" bug and couldn't use the flash or camera until you rebooted?
That was either in the L dev preview or 5.0.0, i don't remember. It seemed to be fixed in the latest patch prior to 5.1, though.
Sadly, it appears to be back in 5.1. Is there an open bug for this?

Oh gawd

lotherius said:
Remember the bug a while back where if you turned on the flash, it would time out in a minute or so and turn itself off? And then you would get the "Cannot connect to camera" bug and couldn't use the flash or camera until you rebooted?
Click to expand...
Click to collapse
FWIW, I have never been able to duplicate the problem on my N5, either with 5.0.1 or with 5.1. Just now I turned on the flashlight via the quick settings shade and left it on for over 10 minutes. It stayed on all that time, and after I turned it off, the camera is working fine. I don't know what to conclude, but I'm glad I'm not experiencing the problem.

Also was there with 5.0.1
Sometimes the flashlight worked, but most of the time it behaved the way as in OPs post.
Annoying, especially since Xposed also doesn't work with 5.1.....used the Wanam Torch module the whole time.

Yeah Wow and I thought I was the only person with this problem I thought my flashlight LED blew out the first time it happened because it wouldn't turn back on until after I Rebooted.

yup, had the problem just now..

The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
Wrong, faced it on Day 1 when i was in 5.0, it was a clean flash of factory image with no user apps installed.
In 5.1 so far i haven't encountered that bug.

Didnt experience it before 5.1 but now do

It did it on the developer preview also
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

I had this bug from 4.4 and still happening, im used to it not a big deal. Just dont keep flash on longer then 10 min.

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
Not using any of those things you mentioned.
And what you call a prevention from burning out the flash....I don't know man, since when did "having to reboot your phone because the flash would never turn back on after it turned off by itself" become a feature?

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
So you're telling me.. When I drop down the notification page and toggle "Flashlight" and it goes out it's the "APPS" Fault. Which is the built in notification area?

I've never had a problem regarding this, fortunately.

https://code.google.com/p/android/issues/detail?id=79565
Everyone comment and star the issue

markdapimp said:
https://code.google.com/p/android/issues/detail?id=79565
Everyone comment and star the issue
Click to expand...
Click to collapse
Don't comment unless you have useful input for the developers - commenting just spams everyone on the list, meaning many will un-star it. Just star it instead.

Have this bug on clean install of 5.1
Pretty random in nature

I had the same issue and I solved going in the development option and I switched on the Awesome player option.
Seems it works. I had for 2 minutes the flash light on without problems

Initially I didn't think I had it....and I don't on a fresh boot when no notifications come in. Then I had the flashlight on and an e-mail (Gmail) notification came in, and I couldn't turn off the flashlight. Before 5.1 had it stuck on every time if the screen timed out, at least that is fixed (I think).

coluichepensa said:
I had the same issue and I solved going in the development option and I switched on the Awesome player option.
Seems it works. I had for 2 minutes the flash light on without problems
Click to expand...
Click to collapse
I have no idea why this worked, but it did. 10+ minutes, no timeout!
this has been the most infuriating bug I have experienced going all the way back to making my htc ozone run on gingerbread.
has been present on every variation of lollipop I could find. my flash light would time out in 2 minutes or so.
Thank you so much!