Database Info

Best battery life with custom rom/kernel

Suggestions? I currently use cm7 151 with faux's oc/uv 0.4.2 kernel. Not really happy with battery life, only get about 7 hours with moderate use. I have great signal everywhere I go.
Sent from my LG-P999 using xda premium

wgrant said:
Suggestions? I currently use cm7 151 with faux's oc/uv 0.4.2 kernel. Not really happy with battery life, only get about 7 hours with moderate use. I have great signal everywhere I go.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm in the same boat. 8 hours ish on Weapon 2.7 - doesn't matter which kernel, or how much I undervolt it.

Eaglesblood 2.3.5 with faux 42 oc/uv best combo ever everything works
Sent from my LG-P999 using XDA App

How heavy is your usage and how long does the battery last?
Sent from my LG-P999 using xda premium

I'm going to give EB 2.2 a try seeing as it's new with faux's kernel and hopefully have a better time with it then last time.
Hope to post back with good results battery-wise.

I get about 12 hours with Eagleblood and the kernal it comes with. I use setCPU to lower the clock speed when the screen is off. I can use the phone at work for most of my 10 hour shift listening to music and browsing facebook or other apps that use data on my lunch and breaks along with texting a lot throughout my shift.

ZeroT| Demented said:
Eaglesblood 2.3.5 with faux 42 oc/uv best combo ever everything works
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
What's your setcpu settings with the oc/uv kernel?

Scoobyracing03 said:
I get about 12 hours with Eagleblood and the kernal it comes with. I use setCPU to lower the clock speed when the screen is off. I can use the phone at work for most of my 10 hour shift listening to music and browsing facebook or other apps that use data on my lunch and breaks along with texting a lot throughout my shift.
Click to expand...
Click to collapse
which eb version and is it 2.3.3 or 2.3.5?
Thanks in Advance
I know this thread is about batt life, but what about games are there any rom / kernel combos that make games look and run better?
I'm using xboarders stock debloated and tweaked rom with stck kernel and I also get about 12 hours of light to moderate use in a day.
fauxs kernel causes my phone to black screen and shut off some times.

ZeroT| Demented said:
Eaglesblood 2.3.5 with faux 42 oc/uv best combo ever everything works
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
im using EB 2.2 Faux 4.2 the one that dose no OC or UV and it took me 8 hours of super heavy usage trying to waist my battery for me to drain it hope this helps

My solution is My custom overlay on cm7 nightly 158 with faux123's cm7 kernel STANDARD VOLTAGE with setcpu tuning it down to the second to lowest voltage when the screen goes off. My battery lasts about 35 hours!!!! I know this because I took an overnight trip.
Sent from my LG-P999 using XDA App

[Q] Draw something on CM7 based roms

Anyone able to play "Draw Something" on any CM7 based roms without it freezing? The game would start up but then after like 20 seconds it would freeze. I've tried on a few CM7 based roms and even MIUI but it only seems to be fully functional with no issues on stock roms.

Iam having problems to with it also on my cm7 T-Mobile g2x it would freeze and can't touch anything. Can't even play it.

Same here its not working ...idk how we could get around this....
Sent from my LG-P999 using XDA App

It sucks too cause all of my friends are playing -___-

same here with O2x, do anyone hv this problem on CM9?

It works on cm9

alteredmass said:
It works on cm9
Click to expand...
Click to collapse
I works "OK" on cm9. still very usable becasue i have been playing it for the last week, but it does freeze up every once in a while, and FC, and one thime form me it froze completely and i had to do a battery pull. So it works, but not really super well.

I'm having the same issue on the latest nightly for my G2x. I thought it might have been AdFree or another conflicting app but I haven't had any luck narrowing it down. Anyone find a way around this?

Add me to the can't play list also.
Sent from my LG-P999 using XDA

Yeah this poses a problem for me as well. Girlfriend just found out about this game and she was in love with it. Then found out it doesn't work on CM7 ROM's... F'in bummer.
Had to wipe and flash a stock based 2.3.3 ROM in the middle of the night just because she wanted to play the game with me.
Lol needless to say, I hope this problem is fixed somehow because stock based G2x ROM's are so bad compared to CM7.

mackster248 said:
Yeah this poses a problem for me as well. Girlfriend just found out about this game and she was in love with it. Then found out it doesn't work on CM7 ROM's... F'in bummer.
Had to wipe and flash a stock based 2.3.3 ROM in the middle of the night just because she wanted to play the game with me.
Lol needless to say, I hope this problem is fixed somehow because stock based G2x ROM's are so bad compared to CM7.
Click to expand...
Click to collapse
Lol I am in the same boat bro, my girl is begging me to play every day and Im on CM7. Sucks. Was thinking about wiping and flashing a stock ROM myself but just not worth the hassle. Hoping someone finds a fix soon, I tried everything.
Also thought it was an adblock problem, till I stumbled accross this topic.

What? Are you guys running straight CM7 or CM7 based ROMS? I am running EaglesBlood v2.8, which is based off of CM7, and Draw Something works perfectly. Even faster than it was running on Bionic Reloaded v1.2 which is based off of stock.
The only "lag" I noticed was when I first started up the app, it took around 10 seconds to show me the login screen.
Sent from my LG-P999 using XDA

theking_13 said:
What? Are you guys running straight CM7 or CM7 based ROMS? I am running EaglesBlood v2.8, which is based off of CM7, and Draw Something works perfectly. Even faster than it was running on Bionic Reloaded v1.2 which is based off of stock.
The only "lag" I noticed was when I first started up the app, it took around 10 seconds to show me the login screen.
Click to expand...
Click to collapse
I'm running that too, and it crashes non-stop for me.

What kernel are the people that are affected running?
Personally, I'm running Faux's UV one, without DS.

I'm running straight CM7, the latest nightly to be exact. With the latest update of the game I can launch the app almost every time but it freezes when I try to enter actual gameplay. Ridiculous.

Try using Faux's kernel.
Sent from my LG-P999 using XDA

theking_13 said:
What? Are you guys running straight CM7 or CM7 based ROMS? I am running EaglesBlood v2.8, which is based off of CM7, and Draw Something works perfectly. Even faster than it was running on Bionic Reloaded v1.2 which is based off of stock.
The only "lag" I noticed was when I first started up the app, it took around 10 seconds to show me the login screen.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I'm using EBv28 also and it froze when I first tried to open it.

I just updated to nightly 225 and also updated draw something and still no go...at least now i can get to the start up screen now instead of crashing almost immediately...
Also running stock cm7 nightly
Sent from my LG-P999 using XDA App

theking_13 said:
What kernel are the people that are affected running?
Personally, I'm running Faux's UV one, without DS.
Click to expand...
Click to collapse
This is the fix. I installed Faux kernel with CM stock voltage. No freezes and ****. You can try other kernels too I guess. The only other kernel I tried was trinity and stock and they were both freezing.
http://forum.xda-developers.com/showthread.php?t=1073626
Thanks to theking_13!

nvus said:
This is the fix. I installed Faux UV with CM stock voltage. No freezes and ****. You can try other kernels too I guess. The only other kernel I tried was trinity and stock and they were both freezing.
http://forum.xda-developers.com/showthread.php?t=1073626
Thanks to theking_13!
Click to expand...
Click to collapse
Can anyone else confirm this?

Request: Any Stock GB Kernel

I'm looking for Blues, and Strappeds Kernels. I want to get my Kernel thread updated. So hoepfully I can get a hold of a couple. Then main one I really want is Blues UV 8% Kernel. Thanks.
Sent from my myTouch 4G Slide using xda app-developers app

I got some of that stuff. I have a strapped kernel, a couple Blue kernels, a He Who Must Not be Named kernel, Virtuous V1A, bone stock that kind of thing. (I'll have to dig). I'll put up some db links a little later.
Hastily spouted for your befuddlement

AgentCherryColla said:
I'm looking for Blues, and Strappeds Kernels. I want to get my Kernel thread updated. So hoepfully I can get a hold of a couple. Then main one I really want is Blues UV 8% Kernel. Thanks.
Sent from my myTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
I believe it's listed here in the 3rd post under BulletProof 1.1
http://forum.xda-developers.com/showthread.php?t=1835645
I'm afraid I don't have anything on any of Strapped's GB ROMs. Sorry.

I found a couple.
Stock from one of the first two firmware versions IIRC as supplied by he who must not be named - https://www.dropbox.com/s/dmfetmygompfkf6/Stock_Kernel_v1.0_CIFS_UTF8_TUN_KINETO_UC_Stable.zip
Strapped Mik touch 1.5 - https://www.dropbox.com/s/yxxpp004j4ha548/Mik-Touch-1.5 Ghz-Kernel.zip
Blue kernels - https://www.dropbox.com/s/genofmizy5zgvv9/doubleshot_GB_Base_1-7-A_kernel_2-6-35-10_installer.zip
https://www.dropbox.com/s/nuk0fgul5fwgcpd/doubleshot_GB_OC_1-5-A_kernel_2-6-35-10_installer.zip
https://www.dropbox.com/s/2x7s4koipkxjw63/doubleshot_GB_UV6_kernel_2-6-35-10_installer.zip
Unity v1a - https://dl.dropbox.com/u/22171764/unity_v1a_doubleshot.zip
Unity v2 - https://dl.dropbox.com/u/22171764/unity_v2_doubleshot.zip
I have one other I can't identify but can PM.
I have Romanbb's Kanged stock voltage and undervolted GB if you want them.
I'll see if there is anything else I can find...

AgentCherryColla said:
I'm looking for Blues, and Strappeds Kernels. I want to get my Kernel thread updated. So hoepfully I can get a hold of a couple. Then main one I really want is Blues UV 8% Kernel. Thanks.
Sent from my myTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
I have the stock 1.63.531.2 HTC kernel as well as 3 of Strapped's 1.7 OC/UV kernels (the original, plus the remix and remix2).

We should rekang the already kanged kernel for the new stock source. Maybe today ill cook one with just a kanged clock table to see how it works out
Sent from my HTC MyTouch 4G Slide running MikXE

strapped365 said:
We should rekang the already kanged kernel for the new stock source. Maybe today ill cook one with just a kanged clock table to see how it works out
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Any plans for a 3.0 Sense Kernel? The soucre is public.
Sent from my Bulletproof_Doubleshot using xda app-developers app

AgentCherryColla said:
Any plans for a 3.0 Sense Kernel? The soucre is public.
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
But it won't outright compile. For me at least
Sent from my HTC MyTouch 4G Slide running MikXE

strapped365 said:
But it won't outright compile. For me at least
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
That sucks Xo
Sent from my Bulletproof_Doubleshot using xda app-developers app

AgentCherryColla said:
That sucks Xo
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
Could have just been the source at the time. I deleted it and haven't looked for it since. I guess I could search for it and redownload it.
I did end up starting over on a GB kernel though, didn't mess with the .config much this time around and gonna do it one slow compile at a time with one change to see when things go south
*edit*
Ok so from the looks of the source roman had changed 2 files when overclocking and undervolting and it was for global cpu voltages (faux code). After using the code changed in arch/arm/mach-msm/kconfig the phone bootlooped at the splash screen, but the change to arch/arm/mach-msm/acpuclock-8x60.c (faux code for 1.5Ghz oc/uv?) it boots just fine,but still at full speed no matter if setcpu is ticked to set at boot or not, and my guess is that's just is what it is, )90% of kernels boot at the speed on this device. Anyways that's what I did today trying to start as simple as using code that already works. Now back to the work week
Sent from my HTC MyTouch 4G Slide running MikXE

strapped365 said:
Could have just been the source at the time. I deleted it and haven't looked for it since. I guess I could search for it and redownload it.
I did end up starting over on a GB kernel though, didn't mess with the .config much this time around and gonna do it one slow compile at a time with one change to see when things go south
*edit*
Ok so from the looks of the source roman had changed 2 files when overclocking and undervolting and it was for global cpu voltages (faux code). After using the code changed in arch/arm/mach-msm/kconfig the phone bootlooped at the splash screen, but the change to arch/arm/mach-msm/acpuclock-8x60.c (faux code for 1.5Ghz oc/uv?) it boots just fine,but still at full speed no matter if setcpu is ticked to set at boot or not, and my guess is that's just is what it is, )90% of kernels boot at the speed on this device. Anyways that's what I did today trying to start as simple as using code that already works. Now back to the work week
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Just from my observations, it seems there is something about a Sense ROM that causes the kernel to always boot at max speed of the kernel regardless of any settings in SetCPU or other cpu-clocking app. Only after the device is booted can you manually run SetCPU and then the desired speeds/options will take effect. I've watched it working, as soon as I boot up, I open SetCPU and just watch it... it starts out at 1.7GHz (the max on your kernel). SetCPU will then adjust it down to my desired 1.5GHz. As the phone goes through all its bootup steps (syncing, etc.), suddenly the speed will revert to 1.7GHz again. I can then reset it to 1.5 and it will remain there from then on. So, whatever it is that Sense is doing messes with the cpu clock. Non-sense ROMs don't exhibit this behavior, at least not that I've seen.

Fuzi0719 said:
Just from my observations, it seems there is something about a Sense ROM that causes the kernel to always boot at max speed of the kernel regardless of any settings in SetCPU or other cpu-clocking app. Only after the device is booted can you manually run SetCPU and then the desired speeds/options will take effect. I've watched it working, as soon as I boot up, I open SetCPU and just watch it... it starts out at 1.7GHz (the max on your kernel). SetCPU will then adjust it down to my desired 1.5GHz. As the phone goes through all its bootup steps (syncing, etc.), suddenly the speed will revert to 1.7GHz again. I can then reset it to 1.5 and it will remain there from then on. So, whatever it is that Sense is doing messes with the cpu clock. Non-sense ROMs don't exhibit this behavior, at least not that I've seen.
Click to expand...
Click to collapse
Yeah I've seen it a lot but was just rechecking and after installing super su the speed started sticking after a reboot
*edit*
A few reboots later and all is well
PM me or gtalk me for last nights build
Sent from my HTC MyTouch 4G Slide running MikXE

I'll be diving back into kernels soon.
My laptop is fried, but it'll run in ten/fifteen minute increments sitting on a handful of ice packs fresh from the freezer.
Once I finish migrating everything off of it to usb hdd devices I can start going through what I got.
Meantime, I'll browse through what I got moved onto my phones sdcard and throw some tips out. Been a while, but a quick review and I can throw down what you need to change for stable cpu table edits.
Don't want to steer ya wrong off the top of my head when it's been months since I've looked at it.
Definitely we need to get some stuff thrown around if a lot of old works were lost.
Sent from a digital distance.

Don't oc the 2.3.4 gb stock rom!!

I oc'd it (HTC Glacier) today wayyy earlier to the max OC with my kernel (about 2GHz) and my 245 as the mininum. Governer was the ondemand, and the I/O Sched. was bfq/noop can't remember. So, I was using my phone and decided to run a quadrant, so before the test even started it froze. Like a brick. I looked at the time, and it was 3 minutes behind the current time now. So, I pulled my battery, and tried to boot. It wouldn't. It would have the blinking LED (amber/orange) and like when it was about to boot, the LED would just start over. I call that the "LED Loop". Once I figured what was wrong, I consulted my closest expert, XDA. I cleared the cache, still no dice but it actually booted, and once I unlocked, Rosie crashed and it froze once again. So here is the fix if you think your Glacier has given all hope on you.
1. Grab the same ROM
2. Unplug the phone, pull the battery, and hold POWER for 15 secs.
3. Insert the battery, plug up the phone, then LED Loop should begin.
4. Now hold VOL DWN+POWER together, LED Loop will continue, but don't let it fool you.
5. Then that place where you flash the PD15IMG.zip with the android on the skateboard will show.
6. After the check, go down to Recovery option and select it.
7. If you use 4EXT and go into WIPE screen, and format all partitions (except SD card, unless you want to)
8. Wipe Dalvik
9. Flash that ROM
10. DON'T FLASH ANY CUSTOM KERNELS!!! GIVE YOUR CPU ABOUT A 1 WEEK BREAK BEFORE EVEN FLASHING A NEW KERNEL, WHEN YOU DO, DON'T OVERCLOCK BEYOND 1.5GHz TO BE SAFE!!
That is the revive that I just tried and it worked. If you can't get into that screen. Check this out.. -NiNja.

Moral of the story: [in the words of faux123] not all chipsets are created equal. (Oh and don't oc to the max obviously) I only oc slightly when testing benchmarks and I've really only started testing benchmarks recently because I've been trying to learn some kernel tweaking and sometimes that's the only way you'll physically see a difference (I.e. the effects snappy compression on I/O). Other than that I see no point in benchmarking imo.
Sent from my MyTouch 4G using xda app-developers app

Synthetic.Nightmare said:
Moral of the story: [in the words of faux123] not all chipsets are created equal. (Oh and don't oc to the max obviously) I only oc slightly when testing benchmarks and I've really only started testing benchmarks recently because I've been trying to learn some kernel tweaking and sometimes that's the only way you'll physically see a difference (I.e. the effects snappy compression on I/O). Other than that I see no point in benchmarking imo.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Right, but even without a benchmark. There would've been something that would have made it come to the same outcome though...

Also having almost 2ghz between your min and max is asking for trouble. You're gonna get a freeze, period.
You don't check "Set on boot" until you're SURE the settings will work.
Sent from my HTC Glacier using xda app-developers app

estallings15 said:
Also having almost 2ghz between your min and max is asking for trouble. You're gonna get a freeze, period.
You don't check "Set on boot" until you're SURE the settings will work.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
I've learned my lesson. At 1.5GHz it will stay, forever.

InvisibleNinja98 said:
I've learned my lesson. At 1.5GHz it will stay, forever.
Click to expand...
Click to collapse
Even 1.5 ghz is a little much, I would go at 1.3. I personally just keep mine at stock frequency. Also, I didn't read your whole story but when I pushed my phone to 2 ghz and set on boot, ik I was smart back then, all I did was boot into recovery and restore my backup
Sent from my Dark JellyBellyG1 using xda app-developers app

I have done that to see how I high I could get benchmark scores... yeah not a good idea. I was using one of the earlier aokp roms from Awesome and I had it oc'd to the max. It didn't freeze it just drained my battery like no other. Took me a few days to realize. For what ever reason tge oc stuck. Sad part was that my benchmark scores were about the same lol
Sent from my SGH-T999 using xda premium

[Q] stable ROM with good battery life?

So my wife has an LG G2X on stock android 2.3.4 and she complains that after a while it will move so slowly that it is almost unusable. I have told her to restart the phone whenever that happens and she is having to do that about once a week, but that clears up the problem for a while. Aside from that, everything works as it should. It is using the march 2012 baseband.
Since it is not my phone, I do not know exactly what all she is doing on her phone, but I assume it is mostly facebook, watching videos, texting, and calls. I'm looking for a stable ROM where everything works like stock and has at least the same (if not better) battery life as stock.
And yes, I have searched but a lot of the info seems outdated. I am thinking that I might just run a rooted stock ROM with a custom kernel (leaning towards faux's here: http://forum.xda-developers.com/showthread.php?t=1102720 )... or maybe the stable cm-7.2.0-p999
summary: wife's G2X becomes VERY laggy after ~1 week use, suggest a fix
thanks :good:

Having to restart once a week is not problem, if anything that's a good thing lol. I had to restart my stock unrooted g2x multiple times a week.......if you move to a custom rom your wife will probably have to restart about the same if not more. I'm on cm7 and i restart about once a day just because i like to, not out of necessity. If your wife isn't huge into customization than a stock rooted rom will work just fine. Faux makes a great kernel but it was a little harsher on battery for my liking. I'm running Trinity oc right now and love it. If i were you, i would look at mazouts latest kernel build. He makes AWESOME kernels and ill be moving over to his latest release whenever it comes out tonight or tomorrow.
Sent from my LG-P999 using xda premium

Pain-N-Panic said:
Having to restart once a week is not problem, if anything that's a good thing lol. I had to restart my stock unrooted g2x multiple times a week.......if you move to a custom rom your wife will probably have to restart about the same if not more. I'm on cm7 and i restart about once a day just because i like to, not out of necessity. If your wife isn't huge into customization than a stock rooted rom will work just fine. Faux makes a great kernel but it was a little harsher on battery for my liking. I'm running Trinity oc right now and love it. If i were you, i would look at mazouts latest kernel build. He makes AWESOME kernels and ill be moving over to his latest release whenever it comes out tonight or tomorrow.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
i had her on a cm7 build with her previous phone (motorola defy) and she seemed to like it OK. didn't customize it too much, just used all the default settings.
after i posted this thread, i actually started to look at, and downloaded mazout's kernel... so now i'm thinking of trying out the 3/1 "nightly" build of cm7 with mazout's 0323 kernel. i can't seem to find a known bugs list for cm7 on this phone. are there any known bugs?
does this build of cm7 have a "restart" option in the power menu? that is one of my pet peeves with the stock ROM. the only way i have found to restart the phone is to "power off" and then "power on". i think she would be more willing to restart the phone if it was an automated restart

Yes there is aa "reboot" option that comes up from holding the power button. Maz's 0323oc kernel is awesome. I wouldn't put the Max over 1015 and keep the minimum at 216. Known bugs.....for me the only bug i had was the phone would heat up pretty bad overnight while charging. It was instantly fixed by going into my development settings under applications and selecting the "keep awake" option while charging.
Sent from my LG-P999 using xda premium
---------- Post added at 03:06 AM ---------- Previous post was at 03:05 AM ----------
Is her g2x already rooted?
Sent from my LG-P999 using xda premium

ive actually been having surprisingly good luck running hellfire rom compared to when i was running CM7, its been stable for almost a week now, battery life isnt as good, but much better then stock.

Whaaaat? Hellfire is tweaked out isn't it? Looks like a badass looking rom, just too comfortable with vanilla cm7
Sent from my LG-P999 using xda premium
---------- Post added at 08:07 AM ---------- Previous post was at 08:04 AM ----------
http://forum.xda-developers.com/showthread.php?t=1661610
This is a link to BuRom. Its a slightly modded 2.3.4 stock ROM. Just throwing it out there as another option.
Sent from my LG-P999 using xda premium

If you want to stay with stock just root it and install an app to give yourself access to either full reboot or a quick warm reboot from the home screen.
Rebooting is a necessary evil
Sent from my LG-P999 using xda app-developers app

mansa_noob said:
If you want to stay with stock just root it and install an app to give yourself access to either full reboot or a quick warm reboot from the home screen.
Rebooting is a necessary evil
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
now there's an idea. i didn't think about that. do you know of any of those types of apps that you could suggest?

I have the app Reboot Scheduler. It reboots my phone at 5 am so in the morning it's nice and fast.
Sent from my LG-P999 using xda app-developers app

Just search for reboot in play store.
Sent from my LG-P999 using xda app-developers app

threw "fast reboot" on there to see how she likes it since it doesn't require root, works more like an app killer, but kills all in one press.
now, would i see any noticeable gains by using a custom kernel (stock voltage, no overclock)?

donjuan81 said:
threw "fast reboot" on there to see how she likes it since it doesn't require root, works more like an app killer, but kills all in one press.
now, would i see any noticeable gains by using a custom kernel (stock voltage, no overclock)?
Click to expand...
Click to collapse
Yes, not an extreme amount but a definite yes. I know by experience with CM7 that mazout's stock voltage beta kernel was much better than the stock CM7 kernel. Those kernels are only for CM7 though. I do not have any experience with an upgraded kernel on my g2x while it was stock as I flashed CM7 and mazouts kernel right after.

Pain-N-Panic said:
Whaaaat? Hellfire is tweaked out isn't it? Looks like a badass looking rom, just too comfortable with vanilla cm7
Sent from my LG-P999 using xda premium
---------- Post added at 08:07 AM ---------- Previous post was at 08:04 AM ----------
http://forum.xda-developers.com/showthread.php?t=1661610
This is a link to BuRom. Its a slightly modded 2.3.4 stock ROM. Just throwing it out there as another option.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Went 1 day 8 hours down to 30% yesterday, unbelievable. lol Here i am today, over 14 hours already.

Spawne32 said:
Went 1 day 8 hours down to 30% yesterday, unbelievable. lol Here i am today, over 14 hours already.
Click to expand...
Click to collapse
What ROM are you using now, hellfire still?

Pain-N-Panic said:
What ROM are you using now, hellfire still?
Click to expand...
Click to collapse
yah hellfire phoenix 2.4.2, comes with faux123 kernel from cm7

Faux makes good kernels.
Sent from my LG-P999 using xda premium

^ those stats are kind of irrelevant considering he's asking for a decent play out on battery while using performance. [All around use.] You just showed us what a phone with no data signals and almost no use other then the odd screen wake [possibly texts/calls] the op explained he needed a ROM that takes minimal battery with most use, and being a girl I would imagine she's using social networking which requires WiFi or 3G/4G Please don't take what I'm saying as offensive, your information is very handy however it steers the op in the wrong direction as I'm sure his wife likes to use her phone as much as possible without being stuck to a charger. My girlfriend is currently using my old g2x and so far we've had the best luck with cm7 stable and the trinity kernel with slight under volt. What I would suggest the op do is maybe take a little research nightly on her battery drain, find out what she's using the most and go from there. Unfortunately because its not HIS phone, he's not going to witness distinction first hand and won't be able come to a easy conclusion, and it doesn't help that the g2x devs are stuck on GB, too many ports to keep interest and the search could take forever.
LETS KEEP PRAYING TMOBILE HASNT FORGOT US!
PS spawne32, when you did have your phone like the picture did that include battery apps or task killers? Or just straight up OS? Whenever I tried the ROM you suggested [it has been a while, maybe since updated.] I get screen wake issues and all kinds of battery drain.
Sent from my Galaxy Nexus using Tapatalk

To the op, also recommend to your wife the app called "screen filter" it has an option to lower the key brightness, there are a few of those apps out there but I only remember using that, one of the g2x sad but true battery drainers.
Sent from my Galaxy Nexus using Tapatalk 2

Similar issue - frequent reboots - please suggest ROMs, kernels, other solutions!
I have an LG Optimus G2X (P-999) running the original, unrooted, stock OS (android 2.3.4 "gingerbread", with the "old" bootloader and the baseband from March 2012).
Similar to the OP's wife's phone, mine is running slower and slower, frequently locks up, sometimes so badly that I need to remove the battery to restart it, and sometimes it just restarts itself. I've already tried uninstalling unused apps, clearing caches, moving apps to the SD card, etc. None of that seemed to noticeably help, and lately I need to restart it at least once every 24 hours.
(There are other annoyances too, like the way the GPS hangs and drops, and the battery life isn't great - although the battery may just be too old.)
I'm planning to root it and uninstall the bloatware as a first step, using the instructions I found here: http://forum.xda-developers.com/showthread.php?t=1050534
Then, I'm considering installing a custom ROM and/or kernel. (Most up-to-date list, I believe, is here: http://forum.xda-developers.com/showthread.php?t=1975934 )
Given the problems I'm having, do you think one or both will help? (If yes, do you have any specific recommendations for a ROM and/or kernel, or tips, or possible pitfalls I should avoid?) Are there other ideas I should consider?
Thanks in advance!