Related
My Droid Charge is freezing randomly when I take a picture with it. After hitting the shutter button the screen goes black and unresponsive. I have to pull the battery in order to restart the phone.
Is anyone else having this issue?
EDIT:
Yes, I am stock. Running Widget Locker and Launcher Pro.
wontmatterlater said:
My Droid Charge is freezing randomly when I take a picture with it. After hitting the shutter button the screen goes black and unresponsive. I have to pull the battery in order to restart the phone.
Is anyone else having this issue?
Click to expand...
Click to collapse
More infomation about your setup: Are you stock? If not what ROM and kernel? Are you undervolting?
similar issue
I have a similar issues sometimes with games and random apps on my stock rom. For the camera though I would start by unchecking the review option under settings and see if that helps at all.
Yes I am stock. Thank you.
wontmatterlater said:
Yes I am stock. Thank you.
Click to expand...
Click to collapse
This happens to me as well. Very random. I have only noticed it happening when I had the LED flash on. This happened to me while I was on imnut's debloated ee4 rom and humble 1.2
Yes, I have had this happen. I am currently running the stock ROM with the PBJ voodoo kernel. I have also had this happen when running completely stock.
I thought that this may have been a ROM issue but since you guys are having similar problems while stock, it appears to be an issue with our phones. We may want to report these problems to VZ/Samsung for a possible fix.
Going through the VZ forums, I see that this is actually a common issue.
I suggest that anyone else who is having this problem voices their concerns on their support site as well
http://community.vzw.com/t5/DROID-C...ts-down-and-locks-up-Droid-Charge/td-p/569034
http://community.vzw.com/t5/DROID-C...s-when-taking-pictures-with-Flash/td-p/600910
Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...
Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.
GPS on when this happens, by any chance?
redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.
Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app
Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me
I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.
No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.
nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.
I understand what you're saying but i have checked it,i'm sure..
nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).
No my main problem are the Sleeps of Death.There are no BSODs in android
nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.
Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.
I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often
Is there a fix for the Sleep-of-death for CROMI-X 5.4. I am running that v8, GPU enabled, fsync off & no data2sd or rom2sd. I searched through the ROM thread, but the discussion about the SOD issue kinda petered out with no apparent closure.
Thanks.
mallard56 said:
Is there a fix for the Sleep-of-death for CROMI-X 5.4. I am running that v8, GPU enabled, fsync off & no data2sd or rom2sd. I searched through the ROM thread, but the discussion about the SOD issue kinda petered out with no apparent closure.
Thanks.
Click to expand...
Click to collapse
If you don't mind trying other than _that's kernel, I have something for you to test out....
LetMeKnow said:
If you don't mind trying other than _that's kernel, I have something for you to test out....
Click to expand...
Click to collapse
What do you suggest. I need some stability as I use this for business.
As far as I can tell, there isn't a solid solution because it is really hard to replicate the issue. I can go for a few weeks without any SODs, then SOD happens for a few days and just disappears after that.
mallard56 said:
What do you suggest. I need some stability as I use this for business.
Click to expand...
Click to collapse
It is very stable on my setup but it may be different on other users depending on how you are setting up your device. If you want to look for a solution, you may want to spend some time and test it out... I am not even sure if it is going to solve your SOD issue but I set it to kill any hang apps on the background so your device can response to your input or wake it up.
I am still running my modded 10.6.1.14.4 stock ROM with the latest version of my kernel, and I have never had a SOD since I installed the ROM, that must have been about a year ago. If you get a SOD, try to get a logcat and kernel log (dmesg).
_that said:
I am still running my modded 10.6.1.14.4 stock ROM with the latest version of my kernel, and I have never had a SOD since I installed the ROM, that must have been about a year ago. If you get a SOD, try to get a logcat and kernel log (dmesg).
Click to expand...
Click to collapse
I've never had a SOD either. I know it happens to TF300 users but not seen much of it on the TF700.
Log files after SOD
Not sure if I got these right; took logcat and dmesg from adb. I hope someone smarter than me can find something usefull in them
This SOD seems to be simply that the screen won't turn on. I get notification pings when mail is received, I can connect with adb and run commands, etc. Its just that the damn screen won't turn on.
Anyway, I appreciate what you all have done to make this a useable tablet.
mallard56 said:
This SOD seems to be simply that the screen won't turn on. I get notification pings when mail is received, I can connect with adb and run commands, etc. Its just that the damn screen won't turn on.
Click to expand...
Click to collapse
That's at least a good thing to know.
I don't find any obvious reasons for your problem in your logs, but next time it happens you could try to undock it and see if it makes any difference.
_that said:
That's at least a good thing to know.
I don't find any obvious reasons for your problem in your logs, but next time it happens you could try to undock it and see if it makes any difference.
Click to expand...
Click to collapse
Yeah, tried that; dock, undock, combination of key presses, etc. The only thing that works is to press and hold power for several long seconds until it reboots.
mallard56 said:
Yeah, tried that; dock, undock, combination of key presses, etc. The only thing that works is to press and hold power for several long seconds until it reboots.
Click to expand...
Click to collapse
I suspect it will eventually turn on. The log indicstes it registers your button press. It is not asleep.
Im using PA4.5 with franco kernel (i switched to this kernel because the standard kernel also had this problem
After a while i try to wake up the device with gestures (i always try with gestures first and then with the power button) it just dont turn on the display.
Adb and the home, back and option buttons are lighted up, the cpu is also pushed to different freqs, but the screen keeps empty. I need to force a restart and it boots normally.
I have turned on any gesture.
I couldnt find any to Opo related thread
Edit:
I have installed xposed app settings
Does it happen on other ROMs our only on PA?
Transmitted via Bacon
I didnt test, but isnt there anybody who has the same problem? I love this phone, and PA makes it more awesomer
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
timmaaa said:
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
Click to expand...
Click to collapse
I now flashed cm11 nighly for testing
zephiK said:
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
_Beni_ said:
I now flashed cm11 nighly for testing
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
Click to expand...
Click to collapse
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
_Beni_ said:
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
Click to expand...
Click to collapse
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
zephiK said:
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I dirty flashed CM, in the offical OPO forum smb wrote that uninstalling xposed fixs it.
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
skydayzer said:
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
Click to expand...
Click to collapse
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
_Beni_ said:
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
Click to expand...
Click to collapse
I've used Franco's Kernel upto now with Mahdi-Rom 2.7... And now am running it's kernel and it's working well
Ok i dont want anymore a noname rom, too much change when i switch the phone
EDIT:
nice my bluetooth headset is not working with cm11, lets go back to PA
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
gary93 said:
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
Click to expand...
Click to collapse
Did you update to XNPH33R to see if the problem still occur?
had the issue too, guess it wasnt resolved and i created a jira ticket, you may as well just vote for it now..
Google: jira bacon-736
sorry, but i'm not yet allowed to post outside links!
?
is it a kernel problem?