Hello!
I flashed CM9 nightly on my GSM Galaxy Nexus a few days ago, and it has worked like a charm ever since. Until a few hours ago, that is...
I dug around in the CM-specific settings and (unfortunately!) ended up finding the Advanced settings, more specifically the CPU frequency setting. Just to see how it would handle things, I tried setting the max. frequency to 350 MHz (aka the default min. frequency). I was very surprised to see that the game Road Trip worked perfectly, and so I chose to keep it this way to save energy; I ticked "restore on boot". Later on, the phone rebooted during a phone call, but I thought, "oh, it's a nightly, this is to be expected."
What I noticed a few seconds thereafter (what is my real problem) is that the boot animation froze a few cycles in (after running at full fps for about one cycle), and the phone rebooted again, running into the same problem.
I still have this issue, even after factory resetting and reflashing the nightly (which I thought would remove the freq. "lock", but didn't).
Does anyone know how I can fix this? Is it as easy (or hard, because I can't access the actual system) as flashing some CPU-fixing ROM, or do I need to do something more, even send it to repair?
Thank you guys!
I flashed CM9 nightly on my GSM Galaxy Nexus a few days ago, and it has worked like a charm ever since. Until a few hours ago, that is...
I dug around in the CM-specific settings and (unfortunately!) ended up finding the Advanced settings, more specifically the CPU frequency setting. Just to see how it would handle things, I tried setting the max. frequency to 350 MHz (aka the default min. frequency). I was very surprised to see that the game Road Trip worked perfectly, and so I chose to keep it this way to save energy; I ticked "restore on boot". Later on, the phone rebooted during a phone call, but I thought, "oh, it's a nightly, this is to be expected."
What I noticed a few seconds thereafter (what is my real problem) is that the boot animation froze a few cycles in (after running at full fps for about one cycle), and the phone rebooted again, running into the same problem.
I still have this issue, even after factory resetting and reflashing the nightly (which I thought would remove the freq. "lock", but didn't).
Does anyone know how I can fix this? Is it as easy (or hard, because I can't access the actual system) as flashing some CPU-fixing ROM, or do I need to do something more, even send it to repair?
Thank you guys!
