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
I'm new at trying out different ROM's. I rooted my phone, installed CWM through NVflash.
Here's my issue: I've tried both Hellfire GB 2.1 and EaglesBlood ICS 4.0.4. First let me say they both seem to have done great jobs!
The problem I'm experiencing is with placing calls. I tried calling my voicemail and there is a LOT of static and I can only faintly hear the voicemail behind the static. I've tried this through the earpiece, speakerphone, and on a bluetooth headset.
I followed flashing instructions precisely: wipe wipe wipe (even with the Nullifier), install ROM zip, then gapp zip. Boot up and wait 10 minutes.
I backed up my original (T-mobile GB 2.3.4) and can restore to that with no problem making calls.
Help?
try reading a little more next time, the new baseband will not work with anything besides 2.3.4...2.3.4 rom will only be able to make calls on 2.3.4 roms... the only other way is to revert back to 2.3.3 (V21e)
mt3g said:
try reading a little more next time, the new baseband will not work with anything besides 2.3.4...2.3.4 rom will only be able to make calls on 2.3.4 roms... the only other way is to revert back to 2.3.3 (V21e)
Click to expand...
Click to collapse
Sorry I tried various search words, and I'm not sure what "baseband" is haha.
Am I understanding you right: I have to find an older Gingerbread ROM, flash that on my phone, and THEN I can flash to something newer like EaglesBlood 4.0.4?
My phone was GB 2.3.3 until about 2 weeks ago with the OTA update to 2.3.4.
firehawkco said:
Sorry I tried various search words, and I'm not sure what "baseband" is haha.
Am I understanding you right: I have to find an older Gingerbread ROM, flash that on my phone, and THEN I can flash to something newer like EaglesBlood 4.0.4?
My phone was GB 2.3.3 until about 2 weeks ago with the OTA update to 2.3.4.
Click to expand...
Click to collapse
No, once you get the official OTA update with the new March 2012 baseband (you can check which baseband you have in settings>about phone) you CANNOT flash any other custom ROM other than the official OTA update or a rom that is based of it because of compatability issues.
The only way that you can flash the Eaglesblood ROM or whivhever ROM you want is to downgrade down to the v21e ROM for the G2x if you search on XDA youll find some instructions on how to do so
Hope this hhelps clear up some things
Sent from my LG-P999 using XDA
Here's how to fix. Go to g2x developement, the thread how to unbrick. Then second post. Follow that.
But flash stock recovery first.
Be sure while the procedure is happening, just wait patiently
Sent from my LG-P999 using XDA
OP just restore your nandroid and enjoy your phone. 2.3.4 with new baseband works great.
He wants a custom rom. Just follow the steps I told you
Sent from my LG-P999 using XDA
Thanks!
Thanks for everyone's input... I restored to my stock ROM for now. I'm hoping it's just a matter of time before custom ROMs use the newer baseband
firehawkco said:
Thanks for everyone's input... I restored to my stock ROM for now. I'm hoping it's just a matter of time before custom ROMs use the newer baseband
Click to expand...
Click to collapse
If you want custom roms just do what I said. Because all the hype for ics, I think tweaks wont come out for a while
Sent from my LG-P999 using XDA
Having a similar problem after downgrading from ICS ROM to CM7
firehawkco said:
I'm new at trying out different ROM's. I rooted my phone, installed CWM through NVflash.
Here's my issue: I've tried both Hellfire GB 2.1 and EaglesBlood ICS 4.0.4. First let me say they both seem to have done great jobs!
The problem I'm experiencing is with placing calls. I tried calling my voicemail and there is a LOT of static and I can only faintly hear the voicemail behind the static. I've tried this through the earpiece, speakerphone, and on a bluetooth headset.
I followed flashing instructions precisely: wipe wipe wipe (even with the Nullifier), install ROM zip, then gapp zip. Boot up and wait 10 minutes.
I backed up my original (T-mobile GB 2.3.4) and can restore to that with no problem making calls.
Help?
Click to expand...
Click to collapse
I've recently downgraded from ICS ROM Genesis Stable Build 1 after having some lagging issues and problems with call audio.
I just wiped and flashed CM7 HF Phoenix with Trinity T15 kernel, but I'm having similar problems that I had with the Genesis ROM. I updated to the newer baseband on Genesis to correct some call audio issues, but I'm now having the same problems after downgrading back to CM7.
I already tried GetRIL and have matched my baseband, but I'm still having the call audio problem. Do I have to revert back to stock and reflash or is there another solution?
Search for owains new baseband zipfile. If you're using the March 2012 BB then you need to patch the ROM to work
Sent from my LG-P999 using xda premium
Flash this through CWM.
http://forum.xda-developers.com/atta...6&d=1339901539
If my lack of posts makes you nervous, here's my source
http://forum.xda-developers.com/showthread.php?t=1501667&page=629
New2my8125 said:
Search for owains new baseband zipfile. If you're using the March 2012 BB then you need to patch the ROM to work
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
awesome, will try this
New2my8125 said:
Search for owains new baseband zipfile. If you're using the March 2012 BB then you need to patch the ROM to work
Fixed my calling issue thanks
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
bamathafan said:
New2my8125 said:
Search for owains new baseband zipfile. If you're using the March 2012 BB then you need to patch the ROM to work
Fixed my calling issue thanks
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
You're welcome
Click to expand...
Click to collapse
I'm having a problem with clockworkmod app and Eaglesblood ICS AOSP. I've seen tons of videos and comments about how sweet this ICS is and all of those comments are coming from owners of the lg g2x (P999). Seems like I'm the only one out in the dark as to how exactly to get this to work. I'm running the basic NVFlash S/W update (2.3.3) March 11, 2012 baseband. I'm becoming a professional at bricking/unbricking this thing, ha ha ha. For some reason, I cannot get clockworkmod or any of it's roms to install, except the Eaglesblood ICS Aosp. It goes through it's fancy, and really cool, intallation but when it reboots the g2x it displays the LG logo first, followed by the red Eaglesblood android with wings logo, then repeated does this. What am I doing wrong here? HELP, PLEASE!
Have you tried redownloading the zip? Also when you're in recovery you should wipe data/factory reset + format system before flashing the zip
If you are on the 2012 Baseband you can only make calls on the stock rom or CM7 RC3 as no other rom right now has working in-call audio on that baseband
Well it automatically goes into the installation process. Yes I've tried downloading the zip again.
Sent from my LG-P999 using XDA
I am using clockwork mod however and I can't seem to get it to work for me anymore
Sent from my LG-P999 using XDA
Have you tried reflashing CWM using your computer?
I would advice installing cmw touch. It is pretty smooth and works on my g2x.
If I helped you, push the thanks button for goodness sakes!
You're running March 2012 baseband? I thought none of the CM7/CM9 source were working properly with this baseband. I dunno about the AOSP builds
I was in the same boat as yourself... The information is getting overwhelming at times... it's nice to search and all... Been doing this for a few months already and the different info, versions, everyones versions is getting to a point you have no clue what to install...
I had tried diffent NVFlash + CWM without success. Some people even suggested using ROM Manager (DON'T).
So I got lucky! I fell on a post with CWM 5.0.2.8 and NVFlash to be ran under Windows. Finally that worked! Then ROMS started doing the same as you. Just booting and not going past the splash screens.
I'm currently running EaglesBlood AOSP 4.0.4... This is one of the first ROMs I have had that pretty much has minor bugs. The rest I tried had issues with Wifi and 4G...
So perhaps you could search for that version of CWM, might work for you. (I'll try to find that info for you where I downloaded it, I'm mad at myself for not bookmarking it )
EDIT: This is the CWM install I performed... http://forum.xda-developers.com/showthread.php?p=24087341#post24087341
There are very few ROM's that work on the new baseband and last I checked EB ROM's were no exception. cm7 rc3 apparently works on the new baseband, but thats the only one I'm currently aware of.
TeamJTB said:
I'm having a problem with clockworkmod app and Eaglesblood ICS AOSP. I've seen tons of videos and comments about how sweet this ICS is and all of those comments are coming from owners of the lg g2x (P999). Seems like I'm the only one out in the dark as to how exactly to get this to work. I'm running the basic NVFlash S/W update (2.3.3) March 11, 2012 baseband. I'm becoming a professional at bricking/unbricking this thing, ha ha ha. For some reason, I cannot get clockworkmod or any of it's roms to install, except the Eaglesblood ICS Aosp. It goes through it's fancy, and really cool, intallation but when it reboots the g2x it displays the LG logo first, followed by the red Eaglesblood android with wings logo, then repeated does this. What am I doing wrong here? HELP, PLEASE!
Click to expand...
Click to collapse
Any update on your situation?
Have you tried the CWM version I used?
Also, are you using ROM Manager? If so, stop, it doesn't work.
So I recently acquired my second G2x. I rooted it with no prob just like i did my last one,and began installing custom roms. All was going well as i had flashed a few roms with no problem. I was running Eaglesblood ICS for a cpl days,and it was working good. A few days in,it started acting funny,apps force closing,random reboots,so i decided to go back to a GB rom,Hellfire Phoenix. Flashed it,went to boot,Lg icon appears for a few seconds,then nothing. Ok,no problem,tried clearing caches and fixing permissions,still no go. At this point,I tried CM7 and could get it to boot,but calls wouldnt work,some odd clicking sound. Did some research and found out this could be caused by a bad baseband,so i flashed my backup of the stock rom,and it works perfectly,only problem is whenever i flash any rom other than stock,it either wont boot,or in call audio is borked. Any advice or links to a tutorial to fix this would be much appreciated! I am on the stock 2.3.4 GB rom with the March 11 2012 baseband, 2.6.32.9 kernal....
Prepare to get flamed for not searching first. The answers you seek are already on the forum. I'll give u a quick answer anyways. Check the original post for the ROM you flash for if it's new or old baseband. Then check the stickies for info about a patch for each instance of incompatibility. If you're using a T-Mobile G2x, all this baseband/RIL stuff has been addressed. Check out the sticky thread by noahk423 in the General section.
Why would he get flammed? He searched, he just misunderstood what the info was.
@op
http://forum.xda-developers.com/showthread.php?t=1776843
Go there, flash the zip to fix the noise. If a phone has the newer baseband but you are using a ROM which wasn't built from G2x CM7 sources, eg, Temansek CM7, you will need to flash that zip.
Sent from my LG-P999 using xda premium