Develop Bugs

Cannot connect to camera

When I first start the camera app after a reboot I get the message "Cannot connect to camera". If I try to start the app again it works fine every time until the next reboot.
I've tried a factory reset which worked for a few reboots until the message started happening again.
I'm running the latest stock rom and can't figure out what's changing to cause this.
Any ideas?

Had you got that problem on earlier versions of stock ROM?
Sent from my R800i using xda premium

Sorry, I haven't had the phone long enough to have an older version of the stock rom.

Even I had this error once, I had to reboot the device to get that fixed.
This was the 1st time it happened.
One thing is it happened while shooting a 720p Video.

I don't think it's software problem, probably camera is damaged, or its flex cable. I had the same problem for a moment after disassembling my Play but I forgot to completely connect flex to the connector.
I think the only way to fix your problem is to bring Your Play to authorized service or (if your phone has warranty) send it to SE.
Sent from my R800i using xda premium

It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.

Well.
shadow wave said:
It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.
Click to expand...
Click to collapse
I'm having an issue like that right now. However, I started getting it after I messed with a ton of system files and the framework-res.apk
Did you do the same? I'm working on figuring out what went wrong, it's definitely a software issue for me.

Possible Problem and Solution
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox

Fox Bailey said:
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox
Click to expand...
Click to collapse
YES, i agree, should make a fix btw, =)

Several very weird heavy bugs (wifi, Bluetooth, calling networks)

Hey guys,
A year after replacing my Desire with an S2, I wanted to set up the old girl again, giving it to a friend of mine as her first smartphone. Well, now, all of a sudden I have several issues.
First of all: it worked absolutely fine before, up and including the day I turned it off for the last time. Back then, I took out the battery, SIM- and SD card and stored it in its box in my desk. It's rooted (no idea how I did it, hell, t'was over a year ago. I do suspect superoneclick though) and was running 2.2 until last night (more on that later).
Put it together, turned it on, sure thing: battery almost dead, so I plugged it in while checking it out. Turned on wifi, set up market so I could install some apps & updates. Well, I was in the middle of downloading some updates, when it told me there's some minor update for 2.2. I had no SD in, which was mandatory for the update, so I decided to turn it off and put in a card (while the app updates where still coming in). Well here's where it all went downhill. After reboot:
- No more wifi ("error", wifi-symbol turnes greyed-out green)
- No more Bluetooth (just won't turn on, no notification whatsoever)
- Calling one of my other phones resulted in the screen turning off, with no way of getting it back on (although the phone kept working fine, left a message on my answering machine with dead screen)
- mobile networks was activated, yet would not show in notification bar/actually connect.
Out of desperation, I then installed the official HTC 2.3.3 Rom, which - hey presto - got rid of the calling screen and mobile networks bugs.
I researched online, read a lot, and I just don't know what's going on. Bluetooth and wifi errors seem to be connected, but there's two kind of threads on that online (and here): People who run custom Roms and have that problem (I am on stock Rom, with no modification other than root) , and people who just had wifi magically turn on again after two weeks. I don't even understand how it can go from totally fine to being this busted. Was it rebooting while updating? All it updated was apps like Flash & Google streetview, after all.
But honestly, without wifi this is as good as a brick to me. I can't figure out what's wrong. I thought it was a hardware issue, because pretty much all communication was shot, but the major update to 2.3.3 sorted out two of the four issues. Well, I really need wifi. If Bluetooth is shot, I can live with that.
Is there anybody who can tell me what's busted and point me towards the next step? I'm absolutely out of ideas and can't seem to find anything that applies on Google and/or xda.
Thanks a bunch for ANY help & suggestion!
Sent from my GT-I9300 using xda premium

And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium

Vortagh said:
And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I think it is your best shot to flash custom recovery such as 4ext and to wipe everything (you can flash it via app so no fastboot required, and it is probably best recovery). By everything, I mean every single partition including sdcard. Then try to install some other rom, for example oxygen and then test the phone. If you need instructions just say.

First of all, thanks for the quick reply!
Yeah, I was thinking about flashing cyanogenmod at one point, but all these bugs put doing that at the end of the to-do list.
Regarding instructions, I'm a bit intimidated about formating the whole thing, simply because I've never used anything like 4ext before. So if you could point me to a good tutorial...
Sent from my GT-I9300 using xda premium

Ok, battery is apparently totally dead, so I have to wait till I can borrow one from a friend.
A question though. You mentioned "format everything". I assume this is, what CWM lists as "format boot/system/data/cache/sdcard/sd-ext"? All of that? Including boot? Just making sure here.
Thanks a bunch!

Well, finally got to ordering a new battery. No change. Phone won't start up, no charge light (although the battery, just like the last one, gets warm).
Guess I'm looking at a major hardware failure and thus a brick
Sent from my GT-I9300 using xda premium

[Q] How to fix Google Logo Boot delay problem?

All right, I've googled the crap out of this topic and have found many threads on many sites where people think they are STUCK at this screen, and have to pull the battery. For some people that may be the case, but in my case, it is a delay of about 5 minutes. And it is driving me crazy that nobody finds this as troublesome as I do.
I have the Verizon GNex, and I just recently unrooted and got back to stock in order to get the official Jelly Bean OTA update from Verizon. Once I got it, I rooted using CWM and SuperUser. Everything's great except that almost every time I boot my phone it gets stuck on the Google Logo for about 5 minutes before resuming boot. I've used CWM to clear cache, clear dalvik cache, fix permissions, etc. Not fixed, still does it (not EVERY time, but more often than not).
For the love of Homer Simpson, WHAT IS THE SOLUTION TO THIS PROBLEM?!? It is clearly a Jelly Bean issue, as every JB Rom I've tried has the issue, where ICS never did. I turn my phone off at night, and can't deal with this almost every morning. Can anybody else with Verizon's stock JB just comment and let me know if you also have this problem, and if you know how to make it stop PLEASE SHARE! Thank you in advance!

I would say try flashing the new bootloader but since you took the OTA I would think it came with it. It might be worth a shot anyway.
It is a common problem with JB. Mine takes a minute or two even with the new bootloader.
Allons-y

The ota did indeed come with the new bootloader. So I don't know what else to do. Extremely annoyed about it, especially since there is no REASON I've heard that explains why it happens. Thanks for posting though, good to know I'm not the only one.

[Q] Weird WiFi Issue (Wont Turn On)

Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!

KingKash420 said:
Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!
Click to expand...
Click to collapse
I'm having the same problem. I upgraded to the KK 4.4.2 and now my WiFi won't turn on! I'm getting the Security notice that "Your phone's security has blocked an action that is not permitted. No further action is required." So, I went to the phone security tab to see what my settings were and it is set to Normal and the only other choice is High. So, I don't want to change that setting!

Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk

serio22 said:
Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!

KingKash420 said:
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!
Click to expand...
Click to collapse
Right.. But other than that, the only other thing I can think of is to Odin the 4.4.2 firmware and see if that would fix it, if not then its likely a hardware problem
Sent from my SGH-M919 using Tapatalk

Random reboots after Andorid 7.0 Nougat update

I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!

This could be part of the hardware issue that is happening, it talented to me and I finally have my phone back
Sent from my Nexus 5X using Tapatalk

Which Model of LG 5X?
Do you have H-790 or H-791 Model?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse

sorry my bad, wrong thread

ashokabs said:
Do you have H-790 or H-791 Model?
Click to expand...
Click to collapse
I have a H-790 Nexus 5x on Verizon.

has been happening to me too -- reboots randomly about once or twice a day. (only realize it since fingerprint scanner does not work and i am forced to key my passcode at first login post reboot).

It seems that the H 790 production series are faulty

Nexus 5x reboot problems
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
giannism13 said:
It seems that the H 790 production series are faulty
Click to expand...
Click to collapse

Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?

ashokabs said:
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
Click to expand...
Click to collapse
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
Cheesejam said:
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
Click to expand...
Click to collapse
You could try too, but I doubt it will fix anything. Its a hardware problem

giannism13 said:
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
You could try too, but I doubt it will fix anything. Its a hardware problem
Click to expand...
Click to collapse
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.

ashokabs said:
There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series.
Click to expand...
Click to collapse
IMO opinion this is just the eMMC dying problem that people have reportedly sporadically over the past 12mo. That problem has affected both H790 and H791. It likely just became more likely to show up after the 7.0 update because that was a large update, but by no means is a large update going to cause the problem by itself. The core problem is eMMC that was waiting to fail and could have happened just when web browsing but a large update just pushed it over the edge. Some phones you can do many large updates and never see a problem, then boom, one day randomly it just reboots and bootloops, with no amount of flashing or resetting making any difference.

Cheesejam said:
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
Click to expand...
Click to collapse
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it

giannism13 said:
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
Click to expand...
Click to collapse
I really wish Google would fix this, this isn't really an acceptable solution to me. :/

I have a h790 nexus 5x and haven't seen this issue, knock on wood. However if it's linked to wifi scanning that was issued in another post you may try disabling wifi scanning to see if the issue is resolved. If not it's definitely the emmc in my opinion
Sent from my Nexus 5X using XDA-Developers mobile app

Cheesejam said:
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
Click to expand...
Click to collapse
If it is indeed not a a hardware problem, then don't wait for Google to fix it overnight. Besides, it may be the case that there is no bug at all, and you flashed a corrupted firmware. Your Best bet right now is to try some custom Roms and kernels and see if it fixes the problem. If you don't want to mess with user made firmware then I would suggest you to reflash the latest stock image form Google. If both of the above fail, the you are forced to roll back to marshmallow

You can try to disable wifi scanner on sleep,.

After the Nougat upgrade, I was having random reboots on my 5X (LG-H791). It always happened when my 5X was sleeping (laying on my working desk or on my bedside table for some time). After the reboot it was working fine again for some hours, so it does not seem to be the bootloop issue. I remember that I had a few rare reboots after upgrading to Nougat 7.0, but after the last 7.1.1 upgrade the reboots occured at least every second day.
Last Friday I had enough of it. I downgraded to the last stock Marshmallow 6.0.1 (MTC20K), and it didn't crash a single time after that.
My wife's 5X is having the same random reboots. The reboots are less frequent (but still occur) when WLAN is turned off. I will downgrade her's too, if my 5X is still still stable after the next weekend.
I wonder if this is a different problem, or if this is just a first symptom of the bootloop issue. If it's a bug in Nougat, then shouldn't much more (if not all) 5X owners experience these random reboots?

Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess):
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
hi, i had the exact same problem with my nexus 5x from carphonewarehouse (uk), and when it was given in to repair i was promised money in return, however they ended up refusing to give money and gave a replacement phone instead, the only way to fix this issue is apparently to get a replacement, as it is most likely a hardware issue google haven't accounted for

I've had the random restart issue for a while now. I got a "new" replacement in November for a different issue and have been on 7.0 the whole time (until last week when I got 7.1.1 OTA). I'm going to call today about another replacement. I've just had two restarts in the last hour.