Frequent reboots and phone lockups

[GoogleCodeExporter]

What steps will reproduce the problem?
Unfortunately, there are no steps per se. I'm experiencing about 6 to 7 phone 
lockups or straight reboots every day. The phone lockups I'm referring to are 
when the phone stops being responsive and hitting the back key or home key has 
no effect, so the only solution is to reboot the phone. In a last ditch effort 
to narrow down the cause (in case it was app-related and not ROM-related, I 
wiped EVERYTHING off the phone (/system, factory reset, cache, dalvik cache, 
and external storage...all twice), then copied over the CM10-819 ROM and the 
7/26 gapps, both of which were md5-verified. I then flashed CM10, booted into 
CM10, then rebooted back into recovery, flashed gapps, and then booted back 
into CM10 and proceeded to configure CM10. I had been configuring CM10 (setting 
up my google account, changing the notification bar buttons the way I like 
them, laying out home screen shortcuts...) for about 10-15 minutes when the 
phone locked up. Since this happened with ONLY the gapps installed, and since I 
then went and installed CleanROM 4.5 (with only a factory reset and cache wipe) 
and since THAT ran for a whole day (even with frequent Chrome usage, which 
seemed to cause a higher percentage of system lockups than other tasks) without 
any reboots or lockups, I have to assume that the problem lies with the ROM 
itself.

What is the expected output? What do you see instead?
I would expect that I could use the ROM without fear of it constantly rebooting.

What version of the product are you using? On what operating system?
8/19 version of CM10, downloaded late in the day of 8/19 (the file seemed to go 
offline in the early afternoon), and then verified the sha1 with what was 
listed on the download site. However, this issue has existed for quite a while, 
at the very least, over a week, so the problem doesn't seem to be restricted to 
the latest build.

Please provide any additional information below.
I've put down all the information I think might be relevant. I've tried 
capturing logs a dozen different ways, but it seems that the pertinent logs 
never make it past the write buffer into the log files I create. If you can 
think of a way I might be able to capture the logs the moment it crashes, or if 
there's other information you need to address the problem, please let me know.

Original issue reported on code.google.com by Bikerace...@gmail.com on 20 Aug 2012 at 2:02

[GoogleCodeExporter]

Does your device have GPS On and you use Facebook?

http://forum.xda-developers.com/showpost.php?p=29651949&postcount=2184

Original comment by h8r...@gmail.com on 21 Aug 2012 at 10:45

[GoogleCodeExporter]

The answer is yes to both, but on the last wipe and install, the first lockup 
occurred before I ever got around to installing Facebook. I'm not sure what the 
state of the GPS was at that point, since I hadn't turned it on, but I'm not 
sure what the default setting is.

Original comment by Bikerace...@gmail.com on 21 Aug 2012 at 3:23

[GoogleCodeExporter]

Original comment by h8r...@gmail.com on 22 Aug 2012 at 1:32

[GoogleCodeExporter]

I am able to confirm this happens with my device as well. I ALWAYS do a full 
wipe (System, Factory Reset, Dalvik Cache/Cache) and install. After CM10 
flashes, I do another Factory Reset and Dalvik wipe. Install current JB gapps, 
factory reset and clear Dalvik again. I did not install any other apps, just 
was testing out the newest build. Rebooted in the middle of Navigation and also 
rebooted an hour later when I tried to access the messaging app (GPS was still 
enabled, but Navigation was not running). These reboots have happened on every 
build that I've used (last 4 versions).

Original comment by christop...@gmail.com on 22 Aug 2012 at 1:53

[GoogleCodeExporter]

So after flashing the ROM this morning and getting a lockup JUST when I was 
starting to hope maybe the problem had magically disappeared, I decided to to 
try disabling the GPS (which is apparently on by default). It's only been about 
3 hours without a crash, but that's longer than any other period I've gone 
previously, so it seems you might be on to something with the GPS thing. I'm 
not ready to say that it's COMPLETELY resolved by turning off the GPS, but 
given how much I've been using Chrome today and how frequently it locked up 
before, at the very least there has been a SIGNIFICANT improvement.

I'm currently running the 8-22 ROM with the 2.20 AT&T radio and only the basic 
google apps plus my trusty Swiftkey keyboard. I'll start gradually adding back 
my old apps (saving Facebook for last) this evening if all goes well.

Original comment by Bikerace...@gmail.com on 22 Aug 2012 at 6:04

[GoogleCodeExporter]

Well, after almost 14 hours of no lockups or crashes, it's like a switch was 
flipped or something. Around 11:30 last night while reading on Chrome, I got 2 
lockups inside of 20 minutes (both while in Chrome. I also discovered that 
after freezing, if I just waited ~10 seconds or so, it would reboot on its 
own). An hour later it just rebooted itself while the screen was off and it was 
just charging on my night stand. This morning in the car it turned off while 
streaming music over bluetooth, at which point I uninstalled Maps (I think I 
remember someone commenting on the new Maps app at one point) to see if that 
would help, but 10 minutes later it turned off again.

Ugh, I seem to be right where I started, and while I did start reinstalling 
SOME apps, they're just the basic Google apps (Talk, Google+, Voice, Drive, 
etc...) plus some other core apps (Kindle, IMDB, Root Explorer, Last.fm...) and 
I have only JUST over 2 pages of apps (as opposed to the 6-7 I usually have) so 
I just don't know what, if anything, could be causing this...

Original comment by Bikerace...@gmail.com on 23 Aug 2012 at 2:12

[GoogleCodeExporter]

Issue 51 has been merged into this issue.

Original comment by h8r...@gmail.com on 26 Aug 2012 at 11:09

[GoogleCodeExporter]

So, on Monday (Aug 27), I relocked the bootloader, installed the 1.85 RUU, then 
booted into the OS, setting up only the bare essentials I needed to install 2 
OTA updates until I was running the 2.20 software (with an updated hboot). 
After this I used the Unlock_code.bin file from my initial bootloader unlock to 
re-unlock the bootloader, and then installed the latest version of TWRP 
(2.2.2.0). Using TWRP I did a full wipe of both caches, factory reset, and 
/system followed by installing the 8-27 Nightly, and then booted back into the 
bootloader and used fastboot to flash the boot.img since apparently the 
recovery can no longer flash the boot.img after the hboot update. After 
successfully booting into the OS I went back to recovery and installed gapps 
and did a factory reset before booting back into the OS and setting everything 
up. Even with the system wipe I had 4G LTE by default. After all this I've been 
VERY slowly installing apps, sticking mainly to the core Google apps for the 
first 2 days. It's now been 3 days and I've had Google Maps installed for the 
last 2 days, and Facebook installed for the last day, GPS, Bluetooth, and NFC 
are all enabled and working and I haven't had a single lockup or reboot since I 
first started the process on Monday...*fingers crossed*

Original comment by Bikerace...@gmail.com on 30 Aug 2012 at 3:39

[GoogleCodeExporter]

Closing this out. Please re-report if you continue having issues. I've never 
had a lock-up before and I've been on CM for over a month :-S

Original comment by h8r...@gmail.com on 3 Sep 2012 at 12:20

• Changed state: Done