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
Related
I Just recieved my new captivate (sent the other one in for warranty issues) in the mail, and am wondering if it's worth it to upgrade this 100% stock captivate to JH7, or if I should wait for 2.2?
Another suggestion
Upgrade to the Cognition ROM...you get JH7 with a lot of other goodies... http://cognition.theidiotshideout.net/phpmyfaq/index.php?action=show&cat=1
The GPS issue appears to have been resolved with this ROM, and the whole phone seems quite a bit snappier.
ag4vr said:
Upgrade to the Cognition ROM...you get JH7 with a lot of other goodies... http://cognition.theidiotshideout.net/phpmyfaq/index.php?action=show&cat=1
The GPS issue appears to have been resolved with this ROM, and the whole phone seems quite a bit snappier.
Click to expand...
Click to collapse
That's awesome; I'm gone for a week-ish and THIS pops up?
Major thanks.
+1 for the Cognition ROM... I have had my device 2 days now and the first thing I did on night #1 was blow away all that ATT and Samsung [email protected] and load Cog.... this ROM rocks... super fast for me. No telling when 2.2 will be baked enough on our devices for me to use it as my daily driver.... weeks maybe....
Flashed Cognition 2.1; Works wonderfully, sans GPS... This phone is turning out to be a real debbie downer in that department.
My GPS has been somewhat OK.... for the 3 times I used it, it was pretty darn close. It drifted a little when driving highway speeds, but crap, close enough for me most times. I think my phone is a late build... I waited for a while to pick one up due to the glass shortage that occurred earlier... curious, can we tell when our units left the factory, and if so, I wonder if they are coming out with different GPS chips on them?
One last thought - did you do a batt pull once your new ROM was in place? Just shooting off ideas... I hope it starts working better for you... I am really liking this phone compared to my Bold 9000.
jaxf250 said:
My GPS has been somewhat OK.... for the 3 times I used it, it was pretty darn close. It drifted a little when driving highway speeds, but crap, close enough for me most times. I think my phone is a late build... I waited for a while to pick one up due to the glass shortage that occurred earlier... curious, can we tell when our units left the factory, and if so, I wonder if they are coming out with different GPS chips on them?
One last thought - did you do a batt pull once your new ROM was in place? Just shooting off ideas... I hope it starts working better for you... I am really liking this phone compared to my Bold 9000.
Click to expand...
Click to collapse
I've never gotten a lock with either of my Captivates; What do you mean by a battery pull? Just lug the battery out of the phone while it's running and put it back in? I'm curious as to how that would be beneficial to GPS. (I've done a reset, but that's about it)
snapplefish said:
I've never gotten a lock with either of my Captivates; What do you mean by a battery pull? Just lug the battery out of the phone while it's running and put it back in? I'm curious as to how that would be beneficial to GPS. (I've done a reset, but that's about it)
Click to expand...
Click to collapse
Yes, exactly. Pull the battery out, wait for a minute, put it back in and reboot. In many cases, this has (for me) fixed weird little issues after ROM updates etc. I have no evidence that this would affect the GPS in your case, but I thought I'd mention any tips/methods that have helped me in the past.
Yeah a battery pull usually solves a lot of issues when upgrading roms...I've had t so that twice.
Sent from my SAMSUNG-SGH-I897 using XDA App
It seems that no matter what mods/roms I tried gps has been able to get and keep a lock while using maps or navigation. Am I the only one?
Sent from my SAMSUNG-SGH-I897 using XDA App
Somehow the other day I got it to lock,stay locked and navigate me for a while but it wasn't perfect.it would basically just jump back to the spot where I really was
Yay no more fc
zavier100 said:
It seems that no matter what mods/roms I tried gps has been able to get and keep a lock while using maps or navigation. Am I the only one?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I have seriously wondered why this is,....even thought about making a post about it, but
In every rom I have ran so far I have never had an issue. I have consistently gotten 8-12 satellites and the first 8 lock within seconds. Since I got my new car mount I have been running the "GPS Test" application and just let it go while I drive. I even went as far as to get the Track Me app and traced my drive to and from work.
I only seem to see complaints about GPS but I have had nothing but a great experience. The worst performance I have had is with the "Cog 2.2 Beta1" and I still do not feel it was sub par performance.
I know this is the opposite of what you asked but I thought it might be informative. Could this be a sign that the problem is hardware and not software?
Hi Vibrant owners!
I made a post over in the Captivate forum about how we can configure the GLGPS daemon in our phones (this is used to control the GPS behavior)
Attached are some update.zips with a new glgps daemon pulled from the Nexus S, secgps.conf and a jupiter.xml configuration inside. The GPS chipset is common among all SGS models, so this should work for you. Please try it, feedback is appreciated!
Sweet!
Sent from the helm of the vibrant Galaxy S!
I thought the vibrant does not use the jupiter.xml
Sent from my SGH-T959 using XDA App
I know at least one model of Vibrant does (Bell), not sure about the others (CDMA does not I believe)
With the vibrant froyo leaks, we now use gpsd and jupiter.xml Samsung decided to make it the same across the board. At least for the i9k, cap and vib. Not sure aboit the epic and fascinate though
Sent from my SGH-T959 using XDA App
i really don't understand these "fix your gps" threads. Hasn't it already been fixed a while back with the newer 2.2 roms? Mine is just fine now.
boodies said:
i really don't understand these "fix your gps" threads. Hasn't it already been fixed a while back with the newer 2.2 roms? Mine is just fine now.
Click to expand...
Click to collapse
Wow. Your like saying that people doesn't have to fix their gps if yours has been already fixed.
im saying if you've upgraded to a new rom like most here then it should have been fixed. what kind of fix are you expecting a 100/100 Sat lock the instant you turn on the GPS app?
boodies said:
im saying if you've upgraded to a new rom like most here then it should have been fixed.
Click to expand...
Click to collapse
Yeah it should have been fixed, but to some it isn't. Maybe because of the hardware or other issues.
boodies said:
what kind of fix are you expecting a 100/100 Sat lock the instant you turn on the GPS app?
Click to expand...
Click to collapse
I'm not expecting that, we all just want it to be usable like having a better accuracy.
sorry it's getting late and my brain is not fully functional ^_^ though it is sorta confusing how the same hardware can produce different results with the newer 2.2 roms.
It's not the same though.
The antenna got revised in October 2010. See the post about the gps fix in the Vibrant general forum.
Sent from my SGH-T959 using XDA App
ic... that's even more depressing lol. you would think a newer antenna would fix it.
boodies said:
ic... that's even more depressing lol. you would think a newer antenna would fix it.
Click to expand...
Click to collapse
It seems the newer antenna did fix it - the older design is unreliable so "identical" hardware can have different GPS performance depending on how much the connection has worked loose.
http://forum.xda-developers.com/showthread.php?t=878970
if you compare to HTC model like HD2, you will see that vibrant is very slow altough gps is fixed...I once use htc hd2 with MDJ mod for android GPS is real fast, never more than one minutes from start ( case compared when u totally delete gps data) I don't know how HTC did it...just for your guy to concern
My GPS has never worked and I've tried every ROM and every fix. Sure I can get a lock on 8 of 12 satellites, and I can easily get 10 foot accuracy. As soon as I try to use Navigation, it sucks. It'll jump around by a few feet here and there, and that's enough to totally throw off the navigation. All of a sudden it thinks I'm the wrong street and its telling me to turn around.
im sorry guys, that sucks. mine has been fine for a while now. and i navigate quite a bit as I am new to Cali. Initially it truly pissed me off when I was on 2.1, telling me i'm staying on the highway when i infact took the off ramp etc... lol. I'd get a replacement.
Can anyone ever say the word GPS without sending everyone into a pissing frenzy?
BACK ON TOPIC:
OP which one do you recommend starting out on for us Vibrant owners?
I highly.. very highly recommend Sombionix' Nero 3. I've used a lot of roms and this one is very very fast. And I usually refrain from saying "fast" because most phones are initially fast when new roms are installed but this one definitely deserves it even after massive app installs and use.
I tryed out the google version and it killed my GPS it sees 12 birds but won't connect to any.
Which do I install? I have a Tmobile Vibrant. You have 3 files listed. Thanks.
Ok a rewrite
Monster rom 1.1i is what I've been on all day and there is an update to 1.1j that just came out so my thought are of the 1.1I
Theme of the rom is very little at this time its still very new. The notification bar is a metallic black with white symbols and a battery meter that shows 1%. Very nice. The dialer is also themed with a metallic look.
The rom is I would say looks like an OASP rom even though its not. I like the look and feel of the launcher.
I think that its faster then stock. Feels snappier do to the adrenaline shot that he gave it. I don't know what that does but I like it. No lag or slow downs of any kind.
There is a bloated and a debloaded rom as well.
Also the free ram has been really good. Every time I look I have at least 200 to 230mb of free ram all the time. Can't beat that. The battery has also been good for me as well, as of 12 hour of moderate use I still have 50% left. That's good for me.
I've had no issues with it as of now so im really liking it and im looking forward to more updates. He updates it every couple of days wich I ike. They are not big updates but good ones.
Rom is by 05gsxrk5 and BenLand150
Im sorry if i left someone out.
Sent from my DROID3 using DroidForums
I like the idea of rom reviews.. but no disrespect I think you should put more detail maybe pros and cons in each to you, other specifics and structure your paragraphs better.
Sent from my DROID3 using XDA App
I read it back and you are right. When I do the next one I will add more I was pressed for time I had somewhere to go so it was a fast reveiw. I am far from a good writer and was never great in english class either I think a teacher said the same thing to me once its why I got a c in that class. I think the next one I will make a paragraph for each specific thing. I think that way we can get a better idea of the pros and cons. Thanks for the insight
Sent from my DROID3 using XDA App
Monster ROM is by 05gsxrk5. I'm just supporting it on Droidforums so people know about. The first post gives credit to him, too. Just pointing that out.
Yes thank you for doing that. I did not think about the other people involved with the rom.
Sent from my DROID3 using XDA App
I rerwrote it. A little better now
Sent from my DROID3 using XDA App
Monster Rom is not AOSP, it just doesn't use Blur launcher.
I know that its not it just looks that way I will update my post
Sent from my DROID3 using XDA App
Is this thread meant for anyone to chime in? I like that idea too. If you ever want to read reviews without searching through what will end up probably being 100+ pages of questions/comments in the actual respective ROMs threads u could just come here search for the name and read up.
Please chime in. I think its great to here from people who are using these rims. I like one place where we can go to read what people are saying about the rims. As of now im on 1.1k just came out last night. So far I like the changes. Later im going to steel DROID and try out 3.0 that just came out.
Sent from my DROID3 using XDA App
Ok time for steel DROID 3.0
Ive been running this for a full day now and
It very snappy. Opening apps is ferry fast it just kinda snaps open very quick. I have not ran into any slow downs or lag. Been very happy with the speed. It also has the adrenaline shot along with some ram tweaks. This rom is the only one out that I've seen with tweaks that I think are done to make a faster rom.
It is also themed a little bit. It has a 1% battery meter on top a black notification bar. The wifi and bars are changed to a blue and look like ice theme. I do like the look
It is running on the blur launcher as of now.
I've ran into no problems that I needs to be fixed with away. There were a few issues but since have been fixed. He also has some addons that you can put back onto the phone if you need certain Apps that he took off. It is debloated rom, I also think there is a bloated rom as well.
The free ram is not as high as the monster rom but still better then stock. Im usually at 120 to 180mb of free ram.
With every update it gets better and better.
Sent from my DROID3 using DroidForums
Sent from my DROID3 using XDA App
Actually, dpwhitty is doing the poll on his themed rom
Sent from my DROID3 using Tapatalk
Ya I got my rom switched up. Thank you for that im updating my post.
Sent from my DROID3 using XDA App
bump let's hear more reviews
I just put Liberty on my phone last night and I like it even better than Monster. It's heavily debloated imo which made me nervous, but Titanium made it easy to restore apps I needed and now i probably have a more refined list of back ups geared towards how I use the phone, so not a bad thing all in all. It moves quicker on my phone than Monster, the way i measure it is hit home on the homescreen of LauncherPro and it no longer glitches when the screens zoom out into formation.
The only bug i've noticed is I can't dial *228. I was able to still call voicemail so I'm wondering if this says anything to the effect of it needing to be provisioned like what I used to have to do in WinMo, but unless I see a problem surface I doubt i'll investigate into that too much. Not really a big deal for me. A lot of people said they had bugs like front facing camera force closing but I haven't had those problems. I used the blur camera as well as the blur calendar/email in the customization options and it all works well.
Liberty is as good as always and will only get better. After Hashcode is done with this new version of safestrap: http://goo.gl/FDYlE I will be dual booting this and CM7 indefinitely.
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