Cheeky, I TOLD you so lol...your kernels need exorcism!!!
Sent from my Galaxy Nexus using xda premium
Cheeky, I TOLD you so lol...your kernels need exorcism!!!
Sent from my Galaxy Nexus using xda premium
That's the reason for SOD, then. Recommend Hotplug OFF and let MPUSS handle CPU1 suspend.
There is. Post /proc/last_kmsgok I disabled hotplug (in fact I'm using the default script now).
This morning, my alarm app went off and I snoozed it (as usual ). 10 minutes later I woke up to a freezed phone and extremely high tempreture. It wasn't too hot to touch but damn it was close. I panicked and removed the battery instantly.
Hopefully there is a way to debug this (wherever the problem is, I'm using CM9 nightlies).
I meant besides last_kmsg. It wasn't generated (in fact, I've never seen a last_kmsg when my phone freezes, only when it reboots)
Maybe you could provide more details, such as ROM, cpufreq governor, min & max freqs, hotplug on\off, then I could try to replicate the scenario.I meant besides last_kmsg. It wasn't generated (in fact, I've never seen a last_kmsg when my phone freezes, only when it reboots)
I was having that issue too, and since I set SCREENSTATE=0 it didn't happen any more.
Maybe you could provide more details, such as ROM, cpufreq governor, min & max freqs, hotplug on\off, then I could try to replicate the scenario.
Lol, didn't I say I was taking a break? Actually testing some scheduler tweaks which improve responsiveness, and also waiting for Linux kernel 3.0.32 to drop.
Had a strange, idk what to call it on the new kernel this morning (forced me back to Franco for now). I went to bed, phone at 99%, woke up and it was on with a dark grey screen with the led light staying on white. Couldn't do anything but a battery pull and when I rebooted it was at 62%
ok I disabled hotplug (in fact I'm using the default script now).
This morning, my alarm app went off and I snoozed it (as usual ). 10 minutes later I woke up to a freezed phone and extremely high tempreture. It wasn't too hot to touch but damn it was close. I panicked and removed the battery instantly.
Hopefully there is a way to debug this (wherever the problem is, I'm using CM9 nightlies).
I was having that issue too, and since I set SCREENSTATE=0 it didn't happen any more.
Yesterday I had to call 911.
Every time the call connected, the phone hung up. Tried 3 times. Luckily they were able to trace the call to my location.
Is this more likely to be an issue with this particular rom, or CM9 base, or ??
Kind of serious, no?
Bad luck, dude. Glad you're okay. The thing is, android kernel has nothing to do with emergency calling. What ROM and Baseband were you using?This may be considered a double post, but I can report also that I have had problems with 911.
I was robbed yesterday (my other galaxy nexus was stolen) as well as a Samsung Galaxy S II Skyrocket. I tried calling 911 but my phone would not dial out to emergency services. It said "Call Failed" with no ring and 55 seconds on the call time. I tried this about nine times before I went into a target and used their phone. My phone calls everyone else fine. I just tried again and it still does this. I was never able to get through.
My Gnex is running May 8th's nightly. Luckily I was not bleeding out or anything, but this might need to be fixed. Still love the ROM and all the developers who work on it.
Here is the original post
http://www.xdaforums.com/showthread.php?t=1398495&page=396
It probably doesn't. I was just adding onto that guy's experience that it didn't work.
Baseband: I9250XXKK6
Cyanogenmod Version:
9-20120508-NIGHTLY-maguro
Superb battery life today. I unplugged at 7:45am and now it's 9:51pm with 40% battery left. This is texting all day, some web browsing, and 2 hours at the gym. Awesome!
1. Start terminal emulator session
2. > su
3. # dmesg > /sdcard/dmesg.txt
For reboot/freeze problem, replace Step 3 above with
3. # cat /proc/last_kmsg > /sdcard/last_kmsg.txt
4. Paste contents of resultant txt files to pastebin.com
5. Post pastebin URLs here in this thread for diagnosis