Just updated to the latest CM7 Nightly, and so far twice today, when I went to hit the sleep button. The screen remains black. I can see a blacklight go on though or something, as the screen changes from when its in sleep. But it remains black.. Is this a known bug? Any suggestions? I would really hate to have to go back to Weapon as I spent all day setting up CM7.
edit: upon further investigation, this appears to be called sleep of death? Are there any known fixes for it?
I had the same problem, happened with every cm7 based rom....i tried posting my problem on this forum for help but no 1 really had any idea what was the issue or how to fix it...as far as I know we're stuck using 2.3.3 roms
Btw do you have a wind optimus 2x or a tmobile g2x? Mine is from wind
Sent from my LG-P999 using XDA App
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
jamadio said:
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
Click to expand...
Click to collapse
Will it only work with the nightlies? I would've preferred to use the stable release or the cm7 eagleblood
Sent from my LG-P999 using XDA App
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Thanks for posting that, I was about to test it myself
Sent from my LG-P999 using XDA App
I think there are 2 different sleeps of death, one of them only happens sometimes, whereas the one we get happens every single time the screen turns off
Sent from my LG-P999 using XDA App
hopefully we can fix this problem together.. It seems Cm7 has better battery life then the other roms so I would hate to go back.
well weapon has been pretty good for me...can't complain really...which CM rom did u try with faux's kernel?
The very latest nightly. Cant remember off hand which one it is.
Also, If I flashed weapon right now (being on CM7 + faux kernel), will I retain the faux kernel? Or will I need to reflash faux's kernel. And even though this kernel says CM7, will it still work with weapon?
I believe the kernel would be flashed over by the stock kernel in weapon, if it doesn't get flashed over then i doubt your phone would be able to boot up, because the kernel shouldn't be compatible with stock 2.3.3
give a shot and try it out, also if you want to over clock on weapon there should be another kernel by faux that u can use, look for it in the development forum
I am going to stay a little longer on CM7, maybe someone can help me with these SOD's.. Then I guess I wil go back to weapon or try out that eagle one. Not sure which is better..
i think the stock eagleblood is very plain and clean....i like weapon because its a little more customized, plus its the only stock rom that has the notification power menu...and from the looks of it, our problem seems very rare so i don't think anyone has or will develop a fix for it
---------- Post added at 02:07 AM ---------- Previous post was at 01:16 AM ----------
hesher said:
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Click to expand...
Click to collapse
i ended up trying it for myself even though it didn't work for u, and it actually ended up working for me
i'll give u detailed steps for what i did and maybe it'll work for u too
(this is all on CWM recovery)
after backing up i factory reset (wiped data), wiped cache, wiped dalvik, and formatted /system
then i flashed the latest CM7 nightly (195), then i flashed gapps
i wiped cache and dalvik again then i flashed faux's 0.4.4 CM SV kernel
i then pessimistically rebooted and voila for the first time i had a functional CM7 rom....i've put the screen to sleep about 10 times so far and it awoke every time so i think it should be fixed
I hope it works for you. I probally didnt see my first SOD until maybe 50 or 60 sleeps.
well I used to get the SOD on the first sleep so its definitely an improvement for me...i'll let you know if it lasts i guess
Related
Im having issues that the lockscreen is freezing up so i have to pull out the battery to make it work again
You can't make such a bold statement, and not include info like what ROM you're running and other relevant info. There's also no need to start a new thread...there's already a thread on the Gingerbread kernel in the development section.
So, because you're having problems, you want to warn everyone on problems that no one else is having??..
Faux's kernels are working just fine for me.
Faux's Kernels are fine. Update and don't listen to this Guy.
Sent from my HTC Glacier using XDA App and a perfectly working Faux Kernel.
WOW. Really, Really ???
Running without a kernel...That's amazing...
Faux's kernels are rock solid...Running 2.5.1 since release and NO issues...
then why has my mytouch freezing alot when i get it out of sleep
Plus i am on RoyalGinger V1.6
OP is an idiot. Faux kernel works fantastic. If you have problem with the rom, ask in the rom thread. Don't try and talk about something you don't understand.
Sent from my HTC Glacier using XDA Premium App
Had problems with it the other day. Running stock rom. Kept losing signal and data. Wifi stopped after about 10 minutes and had to restart the phone just to get it working again. Went back to what I was using before and problem went away.
Not sure what the real deal was as I have NEVER had a problem with his kernal.
Sent from my HTC Glacier using XDA App
mustk1ll20 said:
Had problems with it the other day. Running stock rom. Kept losing signal and data. Wifi stopped after about 10 minutes and had to restart the phone just to get it working again. Went back to what I was using before and problem went away.
Not sure what the real deal was as I have NEVER had a problem with his kernal.
Click to expand...
Click to collapse
The kernel being discussed here is faux's Gingerbread version.
Wouldn't it be great if there was a Mytouch 4G forum that was specifically for roms, kernals, and any other type of hacking? Oh wait there is one and this thread is in the wrong forum.
baller1 said:
then why has my mytouch freezing alot when i get it out of sleep
Click to expand...
Click to collapse
you're a retard.. the reason why your phone is freezing on lockscreen, is cause you either have setcpu installed & have your screen off settings too low! don't have Max set below 368, which 245 freezes your phone! set min& Max to 368 and you will not get any freeze ups and save a lot of battery also! try it!
just don't make a thread about smashing someone's kernal who works so hard to make it for us! faux has great kernals, & you should give him the credit.
Lol sorry. Was on latest cm when tried it. Long day forgot what all I went through with this. Went back to stock rom after it was screwing up. Prolly try again with cm and this kernal. Think maybe it was a bad download causing the problem for me. Although would think I would get some kind of error when installing it.
TeeJay3800 said:
The kernel being discussed here is faux's Gingerbread version.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
This thread is full of nubness.
+1000 for not reading. Not searching. Posting in the wrong section.... and thinking faux would ever fail us lowly 4g users.
Sent from my HTC Glacier using XDA App
First check whatever Rom is fully downloaded. Then check to make sure you fully downloaded the kernel. Make sure you have the proper kernel for your rom. Make sure you wipe cache and wipe dalvik cache. Then install the proper kernel when it boots up let everything load for 4-5 minutes then reboot. If your using a low voltage version try stock version. Also use the cfs kernel and not bfs since your phone is lagging.
Sent from my HTC Glacier using XDA Premium App
I thought these battery usage statistics are only meant to get "Reset" when you full charge battery or when you wipe battery stats. But mine are resetting back to 0 minutes every time I reboot the phone. Is there a fix for this?
Did you do a proper wipe before you installed the ROM?
Yes I did a proper wipe. :/ I guess you don't have this issue?
I went back to nightly 116 and it started to work again. So looks like its broken in recent nightlies.
Nope just broke on yours. latest nightly doesn't reset for me.
Sent from my LG-P999 using xda premium
Looks like it is just me :'(. I have done FULL wipes and everything, even formatted SD cards and flashed back to stock. Seems to be a problem with Nightly 124 and all of the recent KANG builds. But nightly 116 and stock GB has no problems. It can't be hardware then right?
Ok, I have narrowed it down. This happened in Nightly 118. Worked in Nightly 116. There was a kernel update from CM_arcee in between these which might be the cause.
The guys that can't reproduce it, are you running Stock kernel?
I am running nightly 124 and it happens to my phone as well. Any reboot (hard or soft) resets the battery counter ...
Does it on mine also.
Using 124 and fauxs kernel
Sent from my LG-P999 using xda premium
Does it on mine also running trigger 8/22 2.3.5GB with faux123's oc/uv kernel. Not a big deal just hard ta screen shot the great battery life. .
Sent from my LG-P999 using xda premium
It does it on mine also. NIghtly #147 stock cm7 kernel.
I flashed faux uv kernel (ds) and it didn't reset in the first charge. But once I chearged it again, the battery use reset in every reboot.
Is anyone able to contact the CM7 maintainers for our phone?
syl0n said:
Is anyone able to contact the CM7 maintainers for our phone?
Click to expand...
Click to collapse
Sadly, only via postcard
I'm having this problem too. It was fine on the CM7.1 RC I believe. Pretty sure it only started happening to me after moving on to the stable release. Same results on stock CM, as well as when using Morfic's and Faux's kernels...
I have a rooted G2x with running Bionix 2. She runs fine until I try to flash a Kernel. It will get stuck in a boot cycle, run really slow, and have no service. I can restore before flashing the Kernel and its fine again. Have tried a few different ones with the same outcome. Tried a pretty solid search but nothing comes up that fits.
UBER THX in advanced.
Is this post my you too http://forum.xda-developers.com/showthread.php?p=18427267
I answered on there. But is bionix a cm7 based rom?
Sent from my LG-P999 using xda premium
Hill.Jonathan.87 said:
I have a rooted G2x with running Bionix 2. She runs fine until I try to flash a Kernel. It will get stuck in a boot cycle, run really slow, and have no service. I can restore before flashing the Kernel and its fine again. Have tried a few different ones with the same outcome. Tried a pretty solid search but nothing comes up that fits.
UBER THX in advanced.
Click to expand...
Click to collapse
Bionix 2 is VERY outdated and abandoned at this point.
But if your bootlooping than you've probably flashed the wrong kernel. But if your positive it's the correct kernel then it's probably because Bionix is ANCIENT.
You really are better off on something based on the official OTA 2.3.3 like Weapon G2x. CM7 is a better option as well
Hello all you g2x users. Just got a g2x. Ran thru all the different roms without flashing a kernel. DL both ds/cm faux kernels, when i flash it, the screen goes black when rebooting. Reading the op, every room i have tried it with is compatible. Anyone have this happen
Sent from my Sensation using XDA App
U are flashing wrong kernel.
Roms and kernels?
roms were eaglesblood and weapon. the kernels were the faux ds, cm, and gb which im sure was supposed to work. i really want to load a kernel to get my g2x getting higher scores then my sensation. already did stock if i remember right.
We need exact name and version of rom you are currently on, just whitehawks or cm7 wont due.
NVIDIA NEVER AGAIN!
That's what I was trying to say. I have tried several combos. Right notei just tried eaglesblood with faux gb kernel. I will look up the name and post back
Sent from my LG-P999 using XDA App
ksnexusone said:
That's what I was trying to say. I have tried several combos. Right notei just tried eaglesblood with faux gb kernel. I will look up the name and post back
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Eaglesblood has 2 versions and you must use the correct kernel for the specific version. Example: if you are using weapon rom you cannot use faux cm version kernel. If you are using eaglesblood cm version rom you cannot use faux gb kernel. Read carefully and make sure you are mating them correctly.
Sent from my LG-P999 using XDA App
Eagles blood 10-15-11
Sent from my LG-P999 using XDA App
ksnexusone said:
Eagles blood 10-15-11
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
EaglesBlood is based on an older version of CM. The current version of Faux's CM kernel (0.44) is based on 173+. You need to use version 0.43 (at the bottom of the OP) for 10-15-11.
For Weapon you have to use Faux's GB (gingerbread) kernel. Link here: http://forum.xda-developers.com/showthread.php?t=1102720
Read carefully for stock voltage or OC/UV (OverClock/UnderVolt), both versions 0.1.3.
Groove is correct.
Sent from my LG-P999 using XDA App
so i loaded up eaglesblood 10-15 and derkernel and it was cool that i could finally overclock my g2x but i took a call and when i pulled the phone away to end the call the screen went black and no matter what i did i couldnt get the screen back on. had to pull the battery. nothing like that had ever happened til i loaded derkernel and turned it up to 1.5 ghz, anyone else have this happen??
The call wonk is a known issue with cm based roms. Listen, you've got to read the threads a little better before someone gets upset at you for asking questions that have already been answered. Usually you can find out about known issues in the OP (Original Post).
Also use the Stock Volt SV roms. There are 4 types of kernels. Regular Overclocked/Undervolted and stock volt... each one has CM and DS battery driver.
I used the SV DS one.
His standard pre overclocked kernel never booted for me. His rom never worked for me either.... got the black death too. So choose wisely.
LG G2x - 2.3.7 CM7
Asus Transformer - 3.7 Revolver OC/UV
Grooveoriented said:
The call wonk is a known issue with cm based roms. Listen, you've got to read the threads a little better before someone gets upset at you for asking questions that have already been answered. Usually you can find out about known issues in the OP (Original Post).
Click to expand...
Click to collapse
I was not aware that call wonk was an issue on the g2x.
I understand where you are coming from but you can read the op in the "eaglesblood 10-15" thread and there was nothing about an issues such as call wonk. I thought the only phone with that issue was the sensation. I have had a number of android phones and trust me I have done my fair share of reading. If i remember right the only reason I started this thread in the first place was because on that day I had flashed several different combinations of roms/kernels and what I was reading wasnt translating when I tried to flash them. I am sellling my sensation and using this g2x in the mean time til the galaxy nexus finally gets off the boat.
ksnexusone said:
I was not aware that call wonk was an issue on the g2x.
I understand where you are coming from but you can read the op in the "eaglesblood 10-15" thread and there was nothing about an issues such as call wonk. I thought the only phone with that issue was the sensation. I have had a number of android phones and trust me I have done my fair share of reading. If i remember right the only reason I started this thread in the first place was because on that day I had flashed several different combinations of roms/kernels and what I was reading wasnt translating when I tried to flash them. I am sellling my sensation and using this g2x in the mean time til the galaxy nexus finally gets off the boat.
Click to expand...
Click to collapse
It was wonky in earlier 100 builds but I haven't had any problems lately. Using #190-201.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
player911 said:
It was wonky in earlier 100 builds but I haven't had any problems lately. Using #190-201.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
Click to expand...
Click to collapse
EB isn't based on those builds.
Hi all,
My LG G2x phone flash with Pheonix Blood 1.6 CM7 is acting weird. It would have full signal bar, but I can't make or receive call. I would get a message saying 'No Services Area', but then it would work again after a few try. It happen when I do not use the phone for awhile and it sit there on my desk or in my pocket. I seem to only get this error when I am using CM7, because the Miui Rom is fine when I try it. I google it but not many post out there with this issue, and the one that do has it has no answer. Could someone please help? thank you.
Android Noob
I'd say re-flash and if that doesn't fix it, go to a different ROM. I used Phoenix Blood myself for about a day, then switched. Check your PM.
Yeah try reflash a couple of rom, seem like any cyanogenmod base rom give me that issue, and Miui give me random crash.
Phoenix Blood is technically a mod based on CM7, don't blame it on CM7. I had problems with PB as well, the one I have now, none. Haven't tried MIUI.
Yeah, I try the stable build from cyanogenmod website, the nightly build from the G2X forumn, and Eagle blood with all the same result for some reason. Yet stock and Miui doesn't have that issue. So that was why I though it was a CM issue.
lamgiang said:
Yeah, I try the stable build from cyanogenmod website, the nightly build from the G2X forumn, and Eagle blood with all the same result for some reason. Yet stock and Miui doesn't have that issue. So that was why I though it was a CM issue.
Click to expand...
Click to collapse
If so it would have to be something with your phone, I don't get that problem and I haven't seen it mentioned before. Let me know how it goes with the ROM and Kernel I mentioned to you, and don't forget to flash gaaps.
Yup tried that kernel and rom you recommended and still having the same issue. Guess back to either stock or Miui for now and hope for better luck with ICS.
lamgiang said:
Yup tried that kernel and rom you recommended and still having the same issue. Guess back to either stock or Miui for now and hope for better luck with ICS.
Click to expand...
Click to collapse
Weird, sounds like a phone problem to me. Good luck.