Related
I have recently gotten into flashing custom roms, and am currently running Axura 2.5 with SetiroN's 1.4.3
After initial battery conditioning and what not, I have been having good life out of my phone.
I do every now and then wake up to a warm phone which has dropped nearly 40% battery in 6 hours of sleep.
The culprit as per OS Monitor is system/bin/mediaserver
It seems to use a constant cpu of 10%-20%
Trying to kill the process just results in it restarting and burning up cpu again.
Only way to kill it is to reboot the phone.
Since the Axura development thread has been closed and appears Adam is either upset with people complaining or maybe just taking a breather (love the rom) I am not able to get more information there, though when I did bring it up there, others also noticed similar findings.
Anyone know what this file is, what is causing it to go spastic and kill my battery, and how to make it behave?
Sent from my SAMSUNG-SGH-I897 using XDA App
Could be gallery. Not really sure
Install SGS tools from market, and install Gallery 3D from there. The default Gallery on phone has a bug that keeps the sensor on draining battery.
is this true? Will that truly solve the battery issues? Let me know because if so I wanna flash back to it.
I was watching my battery drain like 1 percent every 2 minutes , I watched it. I absolutely loved the rom tho, let us know if it works
Yep its true. There were issues for awhile. But not sure if the fixed one was included or not. But worth a shot.
Krooked22 said:
is this true? Will that truly solve the battery issues? Let me know because if so I wanna flash back to it.
I was watching my battery drain like 1 percent every 2 minutes , I watched it. I absolutely loved the rom tho, let us know if it works
Click to expand...
Click to collapse
Yes. This is the first thing I do on every ROM I set up now. Gallery by Samsung that is distributed by default has a sensor bug that keeps the sensor all even after closing gallery.
Thanks for the tip.
I know I've done that in previous flashes, must have forgotten this time.
Will see how my baby does now.
Definately love Axura Froyo compared to AT&T Eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App
thanks for the tip..installed gallery 3d and im seeing much better battery life ..
This does not work on the newer nightlys, it breaks GPS. Removed the attachment.
---
update.zip to replace /system/lib/hw/gps.inc.so with the file found in the Incredible_C_GB_S_VERIZON_WWE_4.01.605.0 leak that rmk40 posted/updated from 911Sniper's.
I really can't take any credit at all for any of this. I just saw what the Evo guys did, tweaked a line in the updater script, switched their gps file for ours, and then signed it with Signapktic.
If you want to thank someone, please thank galandy and daryelv.
Runkeeper has been having problems for me, so I'm seeing if this helps. i've flashed this and made sure I still got a GPS lock (CM7 Nightly 134), but I haven't had a chance to try it with Runkeeper.... hopefully this isn't an epic fail. One image shows what it looks like good, and one what it has been doing lately.
If you aren't having a problem, I wouldn't flash it, and remember the nandroid!
md5: 2c1f40fcdeabfd4068ef13b9f3358aa6
Hey so do you think you can elaborate on what exactly this does?
On first glance it looks like it is having the GPS refresh much more rapidly (therefore consuming more battery life I'm guessing).
Is this the only thing this mod does?
Yes, how is the battery life with this?
Sent from my ADR6300 using XDA Premium App
I can't comment on battery life at this point. I'm going to use GPS on Monday evening and will report back. I expect it may drain the battery more while using GPS, but for me, the trade off of more polling is worth it.
The update.zip simply replaces the CM7 GPS driver with the driver found in the Gingerbread leak. I can't speak to the changes in the HTC driver, because I've not seen the code (probably wouldn't do much good for me to see it anyway), and the source is not released.
If you are not having a problem, I wouldn't flash it.
I'm curious how this turns out, since I've noticed the same thing with RunKeeper lately. I don't think it has a negative effect on my total mileage, but every once in a while the accuracy goes completely wonky and it can't give me an accurate reading of my pace at the moment.
I had my days mixed up, today isn't a run day.
I wanted to get some initial results though, so I did do a quick run. GPS seems to have a higher polling/refresh/whatever it's called rate. The only thing I did was flash this update.zip.
Tomorrow I go for a 40 minute run so I'll have a better idea on how it hits the battery. I just went 5 minutes today, so it didn't really do anything.
So far, seems to be good. No more corners being cut off!
I'll have to keep my eye on this, when I was running sense roms maps was able to be able to track me with pinpoint accuracy, with cm7 it seems off by a few yards. Not a lot but enough to say im in my backyard when i'm in my bedroom or my neighbors front yard when i'm in my kitchen. If I can get that lock I got in sense with cm7 i'll be a happy camper.
Curious as well
I have noticed issues with GPS being off 5-10 yards as well. I ad recently flashed back to 7.28 radio which seemed to help initially or so I thought. I noticed it off about 10 yards on golf apps.
Looking forward to how this turns out
k_flan said:
I had my days mixed up, today isn't a run day.
I wanted to get some initial results though, so I did do a quick run. GPS is back to being accurate. The only thing I did was flash this update.zip.
Tomorrow I go for a 40 minute run so I'll have a better idea on how it hits the battery. I just went 5 minutes today, so it didn't really do anything.
So far, seems to be good. No more corners being cut off!
Click to expand...
Click to collapse
Nice. I'll have to flash this...
Is this something that I will need to flash every time I update to a new nightly?
Subscribing to this, Thanks OP!
Goalieman009 said:
Is this something that I will need to flash every time I update to a new nightly?
Click to expand...
Click to collapse
Yup, sounds like it
Just got done with a 35 minute run, GPS is working much better for me. I have an 8 month old 1500mAh TP2 battery. It dropped 6% in 35 minutes (screen off the whole time, just using runkeeper), which does not appear to be better or worse on the battery to me than the stock CM7 GPS driver.
If you are flashing this driver, you will have to re-flash it after flashing CM7.
I haven't tested accuracy, I can only say that it has increased the blue dots on my run keeper map which is what I wanted.
Thanks for looking into this. I've noticed that my tracks has been working poorly lately for me. Sometimes it even skips parts of my course altogether. Some of this may be due to the terrain (I use it for MTB ) but I never noticed it when I was using the stock rom. Ill try it out and report back if anything gets better.
Sent from my ADR6300 using XDA App
I look forward to hearing if it helps you or anyone else.
None of this was my idea, I just saw what other people had done on the evo and applied the idea to our phone.
Sent from my ADR6300 using XDA App
k_flan said:
I look forward to hearing if it helps you or anyone else.
None of this was my idea, I just saw what other people had done on the evo and applied the idea to our phone.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, this helped me. Maps is smoother, and MyTracks is insanely smooth! No noticeable difference in battery use either.
Just got finished with my evening ride and it seems my tracks is working perfectly as far as smooth maps. I did notice something odd however, my tracks reported almost one mile more than the odometer on my bike computer! The first two miles were right on and then it seems something went wrong. Ill have to try it with a known distance and see which one is the culprit.
Sent from my ADR6300 using XDA App
Very odd. Please let us know what you find.
NemesisXV6800 said:
Just got finished with my evening ride and it seems my tracks is working perfectly as far as smooth maps. I did notice something odd however, my tracks reported almost one mile more than the odometer on my bike computer! The first two miles were right on and then it seems something went wrong. Ill have to try it with a known distance and see which one is the culprit.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Did a quick walk this morning to get breakfast and I notice that it polls a lot more. Good job, k_flan!
Ok, I've tried it a couple more times and I'm confident the error was in the bike computer. I may have bumped the magnet attached to the wheel at some point and that's what threw off the readings. Everything looks good now, thanks for this!
Sent from my ADR6300 using XDA App
Glad you got it sorted and it wasn't something crazy caused from flashing this.
NemesisXV6800 said:
Ok, I've tried it a couple more times and I'm confident the error was in the bike computer. I may have bumped the magnet attached to the wheel at some point and that's what threw off the readings. Everything looks good now, thanks for this!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Hi guys... ill be receiving my optimus 2x next week... id been reading about all the fixes for it and all that stuff... im planning on installing cm7... but id been reading about problems with sound quality and all that stuff, can anyone point me what baseband (or any other fixes) should i install on the cellphone to get everything working propertly? thanks in advance!
I have had mine for a while now..... 2 months or so? I insdtalled CM7 on it the first night I had it and I have never looked back.... I update every few days although to be honest usually I cant tell the difference between the roms.
Lovely phone, running cm7 - baseband/rij 725, launcher pro and htc sence theme... think its called ntsence.
Plenty other mods as well but these are the main ones
Never had a problem with call quality, there is screen bleeding but tbh unless you really look at a black screen you dont notice it
Bert
ohhh i see, i have to learn about the lg baseband thing hahahah... when i receive my cellphone ill have to check that, cause it seems that cm7 its running fine... but i keep reading about updating and replacing baseband!
to be honest I was running baseband 200 ( or 225 or something ) until a couple days ago.... never had a problem with it and only updated because we get a crap signal in the house ( on all 4 different mobiles.... 2x orange, t-mobile, o2 so I thought I'd try it.... cant say I notice a difference tho lol
Ohhh i see thanks man... ill check all that... what about your battery life?
My battery lasts about a day with wifi on, 3g on, fair usage of both, not many calls tbh but a few txts a day, 3 hours audiobook use per day, screen at full brightness.
As said in another post... if you think the 2x is bad try my wifes iphone :/
it seems pretty good battery life im used with my previous android to carry another battery on my pocket... maybe ill keep doing it... but it seems that this lg got better battery life, thanks man!
I don't mine I get half a day with having everything on and not using and by then I'm at 60% but I use and app for it now and I go home with 90% lol
Sent from my LG-P999 using XDA App
chudm said:
Hi guys... ill be receiving my optimus 2x next week... id been reading about all the fixes for it and all that stuff... im planning on installing cm7... but id been reading about problems with sound quality and all that stuff, can anyone point me what baseband (or any other fixes) should i install on the cellphone to get everything working propertly? thanks in advance!
Click to expand...
Click to collapse
First of all go here http://forum.xda-developers.com/showthread.php?t=1082195
That will give you a clue on what baseband to choose (personally I use 725bb and 725 ril)
Then go here http://android.modaco.com/topic/335494-12-aug-smartflash-stock-baseband-release-103521-20110725/
That tells you what you need to do to change basebands. If you're planning on using CM7 (It comes with the 218 ril as standard, it doesn't change your baseband though) but you will need this program from the market 'LG Getril' it tells you what baseband you have and suggests a matching ril, it also lets you download and instal the ril too.
cm7 is running fine with stock baseband and ril for me
There is an app which automatically detects and recommends the best RIL for your Optimus 2X. It's called LG GetRIL.
Because I'm a new user, I can't post direct link
In terms of battery life, a good matching RIL to your phone can help increase your battery life.
Hope this helps!
thanks will check that too
Try android booster it works wonders I would go to work with full battery and be left with maybe 40% if I was lucky but with that app I go home with 89% so saves me about 50% battery every day
Sent from my LG-P999 using XDA App
any specific settings for the phone?
Not really just read the instructions they give and you'll be fine
Sent from my LG-P999 using XDA App
is there any app like setcpu? im using CM7 without problems... but i can only select 2 rofiles... performance y powersave... any suggestion?
chudm said:
is there any app like setcpu? im using CM7 without problems... but i can only select 2 rofiles... performance y powersave... any suggestion?
Click to expand...
Click to collapse
Don't really need profiles I use antutu which is great for what I use my phone for
Sent from my LG-P999 using XDA
I just mod my rom to CM9 Nova HD RC9-18, find out my battery life is draining. After full charge and use for 1hr, 50% is gone. Any one can share you experience here. Live wallpaper is turn off and other as per default.
Thanks
ailusong said:
I just mod my rom to CM9 Nova HD RC9-18, find out my battery life is draining. After full charge and use for 1hr, 50% is gone. Any one can share you experience here. Live wallpaper is turn off and other as per default.
Thanks[/QUOTE
i have great battery life with cm9 owains kang.
i get about 15 percent loss for an hour with screen on with brightness 50%
Which lasts me 15 hours to a whole day with moderate to high usage
Click to expand...
Click to collapse
Alright.. this is as far as this thread goes Please search and do some reading..
Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2
athdaraxen said:
Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2
Click to expand...
Click to collapse
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?
Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
BWolf56 said:
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?
Click to expand...
Click to collapse
That's just it, I bought 2 new batteries, RavPower ones. They work great and last forever when I charge. My original battery and my cheap one off ebay do the same.
And yes it shows the charging thing, by battery monitor says it's charging and shows the different kinds like a/c or usb, everything acts as it should just no charging.
I have never tried the fast charge, I forgot I even had that. I'll give it a shot.
laughingT said:
Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
Click to expand...
Click to collapse
Also something I haven't tried over a long period. I will try that as well.
Thank you both.
Sent from my SGH-I897 using Tapatalk 2
Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).
x0ne215 said:
Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).
Click to expand...
Click to collapse
I actually have mine stable at 110% still don't know how lol. Cappys seem to be very picky. I'll try turning it back down.
Also fast charge didn't change anything sadly. 2% lost in about 6mins. It was sitting on my bed doing nothing l
Sent from my SGH-I897 using Tapatalk 2
Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).
x0ne215 said:
Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).
Click to expand...
Click to collapse
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.
x0ne215 said:
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.
Click to expand...
Click to collapse
Sorry x3 was a smiley not a build number, I'm on 4.2.
Anyways! I let my phone charge while off for about an hour. It was at 49% turned it back on and it was at 23% see what I mean? That's a crazy amount of juice.
Also, yeah I did play around with some other ROMs and I hated how big they all are, I like how small everything is on Slim. It just works better for me. X3
Sent from my SGH-I897 using Tapatalk 2
Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.
I
x0ne215 said:
Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.
Click to expand...
Click to collapse
I'll try not to use it so you don't get confused. Its just habit.
I don't either. I really did see much on hardware issues that would drain it like this. I really am stumped by this.
And recently I did flash back to stock and work my way back up to Slim to see if it would help and it didn't. I didn't think to see if it would charge on stock or CM 10 but if it really came down to it I guess I could flash back to stock and play with it. Only reason I don't think it's the ROM is because to my knowledge no one else is having this particular issue.
If you have anything I can do to test or provide info just ask. I'll do whatever is needed to help figure it out. And I'd really like to as I'll have this phone for a bit longer then I thought so I'd like to see it fixed
Sent from my SGH-I897 using Tapatalk 2
Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.
x0ne215 said:
Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.
Click to expand...
Click to collapse
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:
x0ne215 said:
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:
Click to expand...
Click to collapse
Huzzah! Well, I got CM loaded, did a full wipe too. Everything looks so big. I'll report back in an hour or two. :3
EDIT
And its charging!
I guess it is in fact the ROM. Dang. I wonder why?
I'm going to see if I can get this to charge fully before bringing it to the SlimBean thread. Just to be extra sure.
EDIT
It seems to get to around 30% (31% as of now) and it just stops. It won't charge any higher. Been like that for about 45 mins.
And EDIT again. x3
Ok so I (still on CM10) couldn't get it go charge past 30% so I decided, I'm gonna poke around and I thought back on the fast charge, I wondered if it had an app, I managed to find one (Fast Battery Charging x2) and ITS CHARGING! I downloaded another app before this called Battery Mix, I love it as it has awesome battery graphs, anyways before I used Fast Battery Charging x2 it (Battery Mix) didn't have any stats on how long it would take to charge, now it does, says about 3 hrs to full, so we shall see where it goes. I don't know how the app works but I will wait and see. If this works I'll hop back to Slim and see if I can't make it work there. I don't know if it will though.
EDIT:
Got to 100%, going to flash back to Slim and see if I can't get it to charge there with the setup in CM 10 I have now, if I doesn't then I guess it must be Slim?
Edit!
Alright so back to Slim and the best I could muster is to keep my battery level the same over night. I tried using the phone for a bit and the battery drain happened again. Overnight I had nothing installed aside from gapps.
Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...
x0ne215 said:
Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...
Click to expand...
Click to collapse
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?
x0ne215 said:
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?
Click to expand...
Click to collapse
Its just so annoying as I don't know a lot but I am trying to learn.
And thanks that would be fantastic actually. I appreciate it. :3
No I haven't I've tried CM 10 stable, Avatar, Pac-ROM (very fun ROM so many settings to mess with), C-ROM, Xylon, and Slim.
Sent from my SGH-I897 using Tapatalk 2
OK, I know the battery life issue for 4.2 ROMs has been beat to death, but I've got something weird happening with AOIP on my phone that doesn't happen with other ROMs.
Basically, when I'm at work, the battery graph (from Battery Monitor Widget Pro) looks like in the AOIPbattery image attached below.
As you can see, it ate all but 3% of the battery in about 11 hours. At times Battery Monitor Widget Pro indicated it was using the battery at 11%/hr or more! This is while I'm at work, and the phone is not doing anything, just sitting on the desk with the screen off, connected to a wifi network but not doing anything with that either.
After a few days of that, I decided I needed to try something else. Originally was going to go back to my "old reliable" backup of 4.1 Rootbox, then thought instead that I'd try the last build of 4.2 Slimbean I still had as a backup. Restored that and got all my current data for the apps reloaded, seemed to be working fine (though still had the stuttering and dumping of apps issues, which was why I wuit using it). Thing is, it's using battery not much faster than the Rootbox one did. See the SlimbeanBattery image to see how it did at work. Same scenario (sitting on the desk, connected to wifi, screen off almost all day). The little bit of high usage was while I was at lunch, reading some web pages and rss feeds, so the screen was on for about a half hour.
So, I'm wondering what the heck is making it use batter so fast on AOIP? I tried several things before switching to Slimbean. Airplane mode made no difference. Used Wakelock Detector to see what was using it up, and it was some part of Android OS making AlarmManager go nuts with wakelocks.
I even backed everything up, factory wiped it a couple times, then loaded the base AOIP 6/3 ROM and loaded GAPPS to see if it still did it.
Nothing seemed to make any difference.
In one sense, I'm hoping the new build that keeps getting hinted at might correct some of this, but I kinda doubt it considering how everyone who brings up battery issues usually gets treated.
That's normal for 4.2 Roms
Sent from my HTC One X using xda premium
I see your point, why does one 4.2 room use that much more battery life then the other, it makes no sense to me. Maybe camcory can shed some light in this issue
Sent from my SGH-T679 using xda app-developers app
That's how my battery life has been on all 4.2 Roms. If aoip is worse for you then most obviously you need to switch Roms.
Sent from my HTC One X using xda premium
I really was hoping that you would see that there might be something wrong with AOIP and take a look at it at least, and not throw out the same tired response. While I do appreciate the work put into AOIP, forum thanks have not happened due to the refusal to notice the glaring issue that everyone else does.
I would really like to know if you even read my post, Smartguy? Seems not or you would have noticed that AOIP in that scenario eats battery three times faster than another 4.2 ROM. Why?
I'm not trying to upset anyone, just trying to hopefully get this resolved in an amicable manner.
Some people don't have battery drain issues that bad with AOIP. You should keep in mind that this phone was never intended to run anything above gingerbread. Every one of these phones handles issues differently, which is unfortunate, but if a Dev doesn't have the same issue it is hard to address. Its just how it is.
Sent from my SGH-T679 using xda app-developers app
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
smartguy044 said:
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Wow hard to believe (well not really) this horse has been beat to death more times than a cat has lives! I'm pretty happy with battery life for the performance and OS I'm getting with AOIP. No hiccups and I have access to all the latest android features. The phone has a small battery anyway so if you want better battery life, time for a new phone or switch to a Gingerbread OS. I charge the phone once a day typically so that's hardly an inconvenience.
Thing is there is something major different in AOIP, as I can typically get just over 24 hours out of this battery in anything other than AOIP, including while I'm at work where the battery usage is a little higher than at home in every ROM I've tried (4.1 and 4.2 based included).
AOIP for some reason eats battery at more than 10% per hour only when I'm at work (less than 3% per hour at home) even when I haven't loaded any apps.
Every time I look at what is using it, it is either "cell standby" or "android os" that is using the most with the other of those two second and the screen usage following in a distant third.
I've tried to figure out what specific item in those two are the source, but it always comes back to some generic service or component in the os that is used by almost everything.
Really any advice to try and improve this, other than "use another ROM", would be appreciated.
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
get a new battery. i dont know what else to tell you. if you are getting 24 hours out of every other 4.2 rom youll be the only one. as i stated i get 10-11 tops on ANY 4.2 rom. so you have 2 choices new battery or different rom
Best thing to to is kill background data turn off Bluetooth WiFi sync and locations when not using your phone for a couple of hours. But your best bet would spring for an 2900mh battery.
tazmaniondvl said:
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
That was the first thing I thought, but it acts the same.
Sent from my SGH-T679 using xda app-developers app
im going to vote you get a new battery if its that big a deal....:good:
go back to gingerbread OS. we gave you suggestions already. 1) new battery. 2) gingerbread OS. simple as that
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
dwolfman said:
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
dwolfman said:
since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
maybe you can code in a "battery fix" and share it with all of us.
Just use a different ROM. Jesus Christ!
teerout said:
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
Click to expand...
Click to collapse
It didn't matter what I installed or didn't install. Once I got the phone at work with AOIP on it, it ate the battery three times faster than any other 4.2 ROM. One time, to rule out anything I was setting or loading, I loaded AOIP, gapps, then put in my account info and disabled auto updates with nothing else changed. It still did it.
As QA software tester, I know how to identify software issues and bugs. The only explanation for what I have happening is there is something going on with AOIP itself to cause this. Like I've already demonstrated other 4.2 ROMs only use the battery a little faster than RootBox 4.1 (RB about 0.6%/hr vs slimbean 4.2 using 1.1 to 1.5 %/hr) with that screenshot in my OP. AOIP uses about 2.5 %/hr at home but over 10%/hr at work.
In any case, it's quite apparent now that this little group of ostriches with their heads still stuck in the sand isn't interested in hearing the truth, so consider this a closed thread.
Sent from my SGH-T679 using xda app-developers app