Related
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, =)
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Hey guys... as it says in the title, I am having issues with my G-nex randomly losing connection/signal but then coming back again. From what I have read, this is a common problem... anyone have any tips? Also wanting to know if I flash a custom ROM if that would possibly fix the problem. Thanks!
Not necessarily the ROM, but the radios. Try that.
There are a few 4.0.4 ROMs for the LTE GNex out now you could try as well if you want to go the ROM route.
Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.
XanderDelores said:
Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.
Click to expand...
Click to collapse
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!
in_dmand said:
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!
Click to expand...
Click to collapse
Hmm.. interesting. The problem here is that this started on March 24th... :/ But, still trying Airplane mode, even though I'm not optimistic..
I emailed my provider, asking them for info, but a friend of mine has been working beside me for the past few days, on the same network with the same phone, without problem. So I guess it's time to bring it in..
Thanks for the info! I may try to put the latest rom/radio on it and see if that helps... if not i'll un-root it and send it in I guess.
I'm having a similar issue with my GSM model, It started when my phone was updated to 4.0.4. Phone signal suddenly drops and comes back again in less than 10 seconds. Sometimes it happens with 1 minute intervals between signal losses, sometimes 5 or 20 minutes, it's very random. After noticing the issue thanks to "Light Flow" that blinks the notification light in white when there is a signal loss, I installed this app (https://play.google.com/store/apps/details?id=com.smartandroidapps.missedcall&hl=en) to track it properly. The results are very frightening, I'm about to do a full wipe in hopes that the issue will be gone :|
ps: like you guys, I did notice that it's very most likelly to happen while the screen is off. Actually, it has never happened while the screen was on.
Same here, post 4.0.4 update on my GSM GNex.
Found this explanation....
Hello,
I've been experiencing annoying freezing up issues with my second-hand Glide. In all cases, the freeze happens with the screen off and a race condition ensues discharging the battery (even when plugged into power). Searching around, I've seen a good number of references to this problem:
androidforums.com/samsung-captivate-glide/462710-freeze-ups-anyone.html
gsmarena.com/samsung_i927_captivate_glide-reviews-4071.php
comparecellular.com/cell-phones/galaxy-s-glide
but I have not been able to find any resolution. Sometimes I feel like this: xkcd.com/979 . In essence I'm trying to determine if this is a hardware fault or something which can be fixed by software. Seeing minimal Glide development does not help since there are very limited options for ROMs. Since this device did get a nod for ICS, there's still hope in that, but until then have to suffer.
Anyone seen a resolution other than exchange? Warranty?
Unfortunately, this is quite common but there are few users that did not had any freezes since day one of their Glides.
One issue is, you have your Google calendar sync and you have "Auto Sync" active. This leads for the Calendar to Sync improperly during sleep mode resulting in a sync loop, which makes the device unresponsive thus, wont wake up upon pressing power/lock key. Solution, uncheck the "Auto Sync" function in Settings, Manually sync everything, or uncheck the "Sync Calendar on your Google account.
The other thing which is very common, is leaving wifi on while charging. This results on the same issue above but the reason is not clear. I experience this one in 1 out of 5 chances, so I turn wifi off or set the wifi sleep policy to "when screen turns off" in Settings. Happens on stock and custom ROM(s), except when Cranium Kernel is flashed.
In conclusion, I never thought that these are hardware issues ATM, for my previous Samsung devices also have these, but is eliminated by updating firmware, or flashing a custom ROM.
Thank you for the suggestions. I will verify wifi sleep policy as well as disable calendar sync to see if it helps. And now that there is some activity regarding ICS for this unit, maybe I'll get to test a new ROM to see if it helps.
thanks again
Neither unsynching google+calendars, or the WiFi+charging solutions worked for me.
Is there any hope for those of us with no immediate remedy?
Has Samsung even acknowledged that this is an issue?
When do you predict us getting an ICS update that will solve the issue?
Its a damn shame since I'm ****in loving this phone so far, yet i can't even use it when I want to sometimes.
Well yeah....I can confirm. I reflashed my device and restore my apps...did not do any mods and whatnot. Used it for a day and charged it overnight, no internet. And bam! Sleep Death. Like i said, this is common, and does not think that this is a hardware issue for a lot is experiencing it. So for now, dont left your glide charging overnight, or if you will, download a night clock, or use the stock desk clock. You will have a clock beside you and will keep your device awake all night.
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
wLnston said:
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
Click to expand...
Click to collapse
The issue you addressed is so called "sleep death." A few weeks past, ATT announced that 10 of their devices will get ICS in less than a month (including the Glide). No word from Rogers when will they update their version of the device.
Unfortunately AT&T did not state when they would push the update as well they only named the devices that will get it.
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
wLnston said:
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
Click to expand...
Click to collapse
I believe Samsung is already knowledgeable about the issue....unfortunately, it is not that easy to make a software update just to solve 1 problem (on the contrary to the Captivate SGH-I897 with GPS issues on Eclair, ATT immediately released a FW update within less than 2 weeks to fix it). And, even though I said the Sleep Death is quite common, not all of the users have this, so again, maybe unless a considerable large number of users (or all users) experience this, they might look into it. So I also believe that Samsung (along with ATT/Rogers) will correct the issue on the next update. When? Heaven knows.
If you are experiencing the sleep death more than twice a day, without doing anything, or if you believe non of your installed programs is at fault, and you are still in your return period, I suggest you exchange your device. You might get a unit that is unaffected. My Sleep Death only occurs when I left the phone charging for extended periods of time, like charging overnight which I always do. As I've mentioned, I keep the device awake like installing a night clock application or activating the stock desk clock app.
Well I'm going to try turning on the night clock app this night and see if that stops the sleep death.
And I bought the phone second hand off craigslist. Even if its within the 90-day period, I doubt I'll get any warranty/return ability as I am not the original customer.
interesting problem, will this should hold me back from buying it when my friends will be in the states?
taiber2000 said:
interesting problem, will this should hold me back from buying it when my friends will be in the states?
Click to expand...
Click to collapse
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day (on the contrary of the OP's post). In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
gabby131 said:
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day. In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
Click to expand...
Click to collapse
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
dudejb said:
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
Click to expand...
Click to collapse
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
i have a therory about that, as some other user mentaioned when they useed adracat kernel (that is OC) the problem is gone. maybe samsung uses a underclocked tegra2 prossesor and that tha problem.
gabby131 said:
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
Click to expand...
Click to collapse
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
dudejb said:
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
Click to expand...
Click to collapse
this is exactly what I am experiencing....and I can replicate this issue about 8/10 times....well this should hopefully be fixable via FW update (like my SGH-I896 from 2.1 to 2.2).
Yes I have CWMR installed and is very handy....I am now going back to flash OsiMood ROM for I think I already know what triggers the Sleep Death specially in stock ROMs....
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
wLnston said:
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
Click to expand...
Click to collapse
Some people have stated that once you install a Rooted Rom you will no longer get pushed the updated from your service provider. They stated this from Gingerbread 2.3.5 to 2.3.6
In order to go back to stock you have to somehow back up what you have before you flash anything or find it on the web. I am not sure about this but have heard of others doing this.
Your other option is use a ROM that someone cooks with ICS when it becomes available. I have heard of many people toying with getting this set up.
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2451 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Edited: Fat fingered the model #. Fixed.
simplicityy said:
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2541 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Click to expand...
Click to collapse
This might be obvious to you, so just ignore if you know this.
When holding your phone in your hand like you're texting in portrait mode, there's a switch top right and on side of phone.
Adjust the switch so it's down.
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
kevp75 said:
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
Click to expand...
Click to collapse
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
simplicityy said:
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
Click to expand...
Click to collapse
don't know if they are aware. just to add to the weirdness of it... for me... after the second time, the setting sticks...
i have this problem with my 8 pro, the phone doesn't ring and i think it goes straight to VM? seems like something broke with one of the latest OP updates?
There's no such version as CPH2541.
And here it works perfectly. Factory reset and try again.