Hmm, yeah I saw those posts on xda haha. I haven't had any issues yet with AK Diamond 018 yet, but battery life could definitely be better.
I didn't do anything special to make it work. Trinity in theory should work as they use anykernel.He seems to be the only developer interested in making it boot, so i recommend it. Lol
Sent from my Galaxy Nexus
We never disabled it so no clue what this is about. Mine maximize just fine. If the lock widget shows, just use your finger to hide it.No Maximize widget option on the lock screen options??? Hmmm...
I ran diamond 18 and I had horrible battery life, but because it was having a constant gps wakelock. I'm running diamond 19 now with the newest Slim build and it is working flawlessly. 1-2% battery drain per hour as it should on standby. It is the only rom i've ran that has the gps fixed.Hmm, yeah I saw those posts on xda haha. I haven't had any issues yet with AK Diamond 018 yet, but battery life could definitely be better.
once I let maps get a GPS lock, I started getting deep sleep the second I hit the power button.I ran diamond 18 and I had horrible battery life, but because it was having a constant gps wakelock. I'm running diamond 19 now with the newest Slim build and it is working flawlessly. 1-2% battery drain per hour as it should on standby. It is the only rom i've ran that has the gps fixed.
Frankly GPS and location services suck on the GNex. Always have. I leave it off unless i really need it.once I let maps get a GPS lock, I started getting deep sleep the second I hit the power button.
Sent from my Galaxy Nexus using Tapatalk 2
Well I was trying to use DashClock widget on lockscreen and make it my default power on lockscreen. It would only show the top half of the widget ( and show the pattern lock) and then i would swipe to the right then back to the orginal screen before it showed all the info. Did I miss something in the options?We never disabled it so no clue what this is about. Mine maximize just fine. If the lock widget shows, just use your finger to hide it.
Try 019 it seems to have better battery lifeHmm, yeah I saw those posts on xda haha. I haven't had any issues yet with AK Diamond 018 yet, but battery life could definitely be better.
Already said that bro.Try 019 it seems to have better battery life
Brace yourself v020 is in testing phase tonightTry 019 it seems to have better battery life
http://db.tt/kUx9UbqmRight that's what I had to do before, but like I said the new build of Slim Bean has GPS fixed so it works properly from boot. It's also smooth as silk from the start. I feel it's the best rom atm.
Read above and previous posts...The problem with disabling gps is google wants to know your location for their ad algorithms so disabling gps causes odd behavior that they don't want. I wish the devs of this and other roms would just put the fixed binaries and be done with it. I have zero GPS issues on the latest Slim Bean.
So screw over the majority? That sounds logical. That doesn't even make sense because toro is only for Verizon. Verizon is only in the US so how does that apply? Leaving it the way it is severely degrades battery performance unless you constantly open maps and get a lock. Who wants to have to do that when it could just work?http://db.tt/kUx9Ubqm
Drop that in /system/etc and reboot. We don't include it by default because it severely degrades gps performance for other carriers/countries. Some of our members have packaged some up for other areas as well on our site.
As far as location services are concerned, they work fine without actual GPS enabled. ie. Using aGPS via wifi and mobile network.
Sent from my Galaxy Nexus
GPS.conf has nothing to do with the wakelock issue. It's when the GPS binaries don't fully match up.So screw over the majority? That sounds logical. That doesn't even make sense because toro is only for Verizon. Verizon is only in the US so how does that apply? Leaving it the way it is severely degrades battery performance unless you constantly open maps and get a lock. Who wants to have to do that when it could just work?
Why are you telling me that? I'm the one that said it's the binaries...GPS.conf has nothing to do with the wakelock issue. It's when the GPS binaries don't fully match up.
Sent from my Galaxy Nexus using Tapatalk 2
We don't build just for Verizon. I'm just going to bow out of this anyway. Clearly you know more than I, so I'll go back to my hole.So screw over the majority? That sounds logical. That doesn't even make sense because toro is only for Verizon. Verizon is only in the US so how does that apply? Leaving it the way it is severely degrades battery performance unless you constantly open maps and get a lock. Who wants to have to do that when it could just work?
I know you don't just build for Verizon, but each build is different isn't it? It should if it isn't. So on the toro builds have the right binaries so that Verizon people don't have to deal with that wakelock issue. It's so simple to solve this...I just don't get it.We don't build just for Verizon. I'm just going to bow out of this anyway. Clearly you know more than I, so I'll go back to my hole.
Sent from my Galaxy Nexus