OK... Every other day or so I'll go to turn on my screen and it acts like I just told it to power on....
It's acting like it was off. I don't know if hitting the power on button is causing a random reboot when trying to wake the screen or what.
I have the extended the battery and cover, both seem secure. Battery also holds a charge quite excellently. I'm only averaging half the internal memory used by active programs.
Is this a hardware problem? Is there a log file I could turn on or check to see if my phone was active right up til I hit the button or if it had been off for an hour?
It's just the nature of CM7. No one wants to admit it, but it's buggy as hell. Random reboots, touchscreen not responding, power button not waking up the phone until the 3rd or 4th try, it's all part of the gig.
But, we all put up with it because there are so many other amazing things about it. You need to weigh out if you can deal with these types of issues in exchange for things you like about CM7. Because I have been using Cyanogenmod off and on for probably 9 or 10 months, and the bugs never go away, they just turn into new ones. "Release candidates" are usually more buggy than the nightlies. My recommendation would be to download and install one of the latest nightlies. I have found that many of the nightlies have more stability than the release candidates.
I still love the rom, and and I am happy to put up with it because it offers me a lot that I can't get with a sense based rom.
Just my two cents. Everyone is entitled to their opinion.
ARHD 7.04. No doubt it's an amazing rom, smooth, fast, perfectly tweaked..
Now and then I'm experiencing this annoying trouble with Google Navigation.. It starts itself, sometimes every 2 minutes, sometimes less often, sometimes only twice in a day.. What should I do? I've experiencing this since ARHD 7.02.. I also have some problems with the volume- button, so I'm not sure whether it may depend on it or not.. Thinking to step back to RD-MIUI.. What do you think?
I bought a galaxy nexus (GSM canadian maguro model) in damaged condition, cracked screen and a bit of cola in the charger port. Replaced everything in the phone except the main logic board, metal frame, and cameras/lightsensors/earpiece.
at this point the device is way more stable than it was when i bought it, however about 2-3 times a day it locks up, sometimes with no reason, sometimes while listening to music, and reboots about 20-30 seconds later. When it locks up with music playing, the last 1 second of sound is looped until the device reboots. I suppose it could be happening more often than I notice, however I have noticed it happens more often when the device is busy and receiving text messages at the same time (ie listening to music on the bus).
Where do i start in tracking down the cause of these reboots? I've got the device on CM10 Stable, and I've attempted using a customer kernel, link: http://forum.xda-developers.com/showthread.php?t=1958143. Though it does not seem to have stopped any of the reboots (though it did make the device seem faster and more stable) Any information or nudges in the right direction would be much appreciated. Thanks.
quanium said:
I bought a galaxy nexus (GSM canadian maguro model) in damaged condition, cracked screen and a bit of cola in the charger port. Replaced everything in the phone except the main logic board, metal frame, and cameras/lightsensors/earpiece.
at this point the device is way more stable than it was when i bought it, however about 2-3 times a day it locks up, sometimes with no reason, sometimes while listening to music, and reboots about 20-30 seconds later. When it locks up with music playing, the last 1 second of sound is looped until the device reboots. I suppose it could be happening more often than I notice, however I have noticed it happens more often when the device is busy and receiving text messages at the same time (ie listening to music on the bus).
Where do i start in tracking down the cause of these reboots? I've got the device on CM10 Stable, and I've attempted using a customer kernel, link: http://forum.xda-developers.com/showthread.php?t=19 58143. Though it does not seem to have stopped any of the reboots (though it did make the device seem faster and more stable) Any information or nudges in the right direction would be much appreciated. Thanks.
Click to expand...
Click to collapse
And you did a completely clean flash?
JamesPumaEnjoi said:
And you did a completely clean flash?
Click to expand...
Click to collapse
Yes the device was completely wiped and updated to CM9 stable before I ever used it. and CM10 stable when it was released.
just for the sake of ruling out software issues, I've updated the phone using the galaxy nexus toolkit to the latest google factory image. Hoping this will solve the reboots. (sorry if I should not have double posted)
Bump. This device is still randomly rebooting for me from time to time. Anyone, please, advice on how to track down the source/cause?
Hi chaps
I've had my note 2 for nearly 3 years so it's getting on a bit. I've got Android Revolution HD v31 on it, supposed to be one of the most stable roms I think?
Sometimes I get a problem where the keyboard shows up like normal, and when I type it gives the haptic feedback and the app acts like you're typing, but nothing actually enters into the textbox. When I get this problem it can be quite persistent, and it happens in all apps. Chrome/whatsapp/messenger, you name it. I've experienced this with Swiftkey, but also the stock samsung keyboard. Restarting fixes it too but just waiting a few minutes and coming back or force closing all apps and trying again usually works too.
This is really really irritating (probably happens ~20% of the time I go to use the keyboard) - As soon as I get some time I'm going to flash the original samsung firmware again and start afresh but I don't have ODIN setup on this laptop anymore and I don't currently have the time. Any short term solutions or the fastest way to get back to stock would be ideal. Cheers!
I can get notifications on my watch if I restart my Galaxy Note 3 and restart my Huawei watch. This works for a short time and then inexplicably drops out.
I had a stable period a while ago when I completely unpaired the two, but this took hours to re-load everything. I recognise there are a lot of similar experiences out there, but have not seen one describing my exact problem.
Thanks for anticipated help! :highfive: