Related
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...
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
Sometimes some keys of keyboard become inactive, I have to close and reopen keyboard or press back space to make it alive again.
This issue only happens with non sense Roms, I'm currently on cm7,but it happens too on reaper and cm9. On endymion/fallout/iceds this never happens.
Anyone have the same issue? There is any solution?
Thanks
Sent from my HTC Desire S using xda app-developers app
Fredericosilva said:
Sometimes some keys of keyboard become inactive, I have to close and reopen keyboard or press back space to make it alive again.
This issue only happens with non sense Roms, I'm currently on cm7,but it happens too on reaper and cm9. On endymion/fallout/iceds this never happens.
Anyone have the same issue? There is any solution?
Thanks
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
ROM problem. Inform the dev of the ROM that you are using.
Skanob said:
ROM problem. Inform the dev of the ROM that you are using.
Click to expand...
Click to collapse
The problem is that all development for non sense Roms are stopped(except JB).
Sent from my HTC Desire S using xda app-developers app
Fredericosilva said:
This issue only happens with non sense Roms, I'm currently on cm7,but it happens too on reaper and cm9. On endymion/fallout/iceds this never happens.
Click to expand...
Click to collapse
Actually this happened to me once on Fallout v4.4.0 , also take into consideration that I use a [MOD] Sense 4 ParfieldIME ( Arabic/Persian Keyboard ) that might caused it.
but it's highly unlikely, prolly happens when I just type too fast, then the keyboard keys seem not to respond (some of them).
I have no idea what might be the cause, but it only occurred once to me and never again (I still type fast).
Fredericosilva said:
The problem is that all development for non sense Roms are stopped(except JB).
Click to expand...
Click to collapse
I can understand problems on CM9 as it is still beta (AFAIK). On CM7 or Reaper I have never had this problem and I use Reaper all the time as my daily. The main reason that development stopped on that is that the CM7 base isn't getting changes and Lowveld is focused on Fallout. It may be worth taking a Nandroid backup first, then doing a full wipe, installing Reaper and testing out the keyboard thoroughly before making any changes or installing any of your apps. It sounds more like something else running on the phone to me - if this was a problem with Reaper then it would have been found a long time ago.
I'm getting frustrated with the daily random reboots of my G2x running stock gingerbread. Does CM 7.2 resolve this? I've been holding off waiting for the official ICS to release so I can install CM10 but I'm getting impatient... Also, do I have to reinstall all my apps, and is my data erased?
Thanks!
I don't think random reboots will ever be solved 100% for this phone. However comparing stock 7.2CM vs other Roms I've used for the G2X, it has been the most reliable and stable for me. The phone still crashes or reboots once every 2-3 days for me usually, when I'm running cpu/gpu intensive apps but almost never when its idle.
helloha1 said:
Also, do I have to reinstall all my apps, and is my data erased?
Thanks!
Click to expand...
Click to collapse
Invest in Titanium Backup and the Pro Key. I can't even put into words how worth it it is
Sent from my LG-P999 using xda premium
Im on cm 7.2 and have been for quite some time and since i flashed trinity kernel i have yet to experience one reboot.
Sent from my LG-P999 using xda app-developers app
Did you try it?
TMOfo said:
Did you try it?
Click to expand...
Click to collapse
No, I haven't yet. I think that i will sometime this weekend. Are there any good guides that I can follow? The one that is stickied says that it is outdated. I am running the latest baseband and software.
Just installed cm 7.2 with faux kernel 52... we'll see how this goes :laugh:
Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.
Just restore a backup it will work fine
Sent from my SGH-T769 using Tapatalk 4
so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.
exo114 said:
so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.
Click to expand...
Click to collapse
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
flyers00 said:
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Sorry to hear but the nightlies are very stable and with use of one of the custom kernels (lz or blue lightning) the phone is stable. If you decide to go back to stock ROM good luck with everything
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
exo114 said:
Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.
Click to expand...
Click to collapse
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....
mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.
exo114 said:
mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1591601
The last post addresses your question...
Sent from atop a BeanStalk
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you
xWolf13 said:
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you
Click to expand...
Click to collapse
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
flyers00 said:
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.
Romman0 said:
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.
Click to expand...
Click to collapse
Truly amazing its almost a year. The cm10.2 ROM and variations are pretty stable for alpha builds. Once the camera is fixed we should be good to go.
I remember being the guinea pig testing a fully functioning rooted ROM stock and cm7. Come a long way lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
in the end i just went back to stock ics rom. no need to worry about random shut-offs (used to happen on stock rom rooted, with "shell has been granted superuser permissions"). can i delete the clockworkmod folder and root stuff? i take it i cant go into cwm recovery without root.
bump. final question is what do i need to delete to leave no traces of being rooted before? is it safe to delete the clockworkmod folder in my phone files?
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
boulos said:
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....
Click to expand...
Click to collapse
The quote-unquote "Stable" build was not stable at all. It was captured before it was supposed to. Something like 2 or 3 nightly builds after that they incorporated the SOD fix into the kernel.
The latest nightly for CM10 is 100% stable as far as SOD, reboots, crashes, etc. I didn't ever have any problems with it up until I flashed beanstalk. I encourage you to give the latest nightly a chance before you go back to 4.0.4, but it's ultimately your choice
Agreed with above
Sent from my SAMSUNG-SGH-T769 using xda app-developers app