yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sway40:
Could it be draining bc your at 1.4ghz? I think that could be it, and switch to ondemand.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
Lol............... that might be the reason
[Samsung Galaxy Nexus] tacosrdelicioso:
Who knows though. I wasn't aware of this suggestion and had no reason to be. No problems here....weird
[Samsung Galaxy Nexus] mike216:
yes this was my experience. Would pull it off the charger and listen to some music while walking my dogs around the block. The damn thing dropped 5% in 15 minutes. I bought the OEM 2100 but its complete snake oil :mad:
[Samsung Galaxy Nexus] mike216:
It turns out that BLX (battery life extender) could be a huge benefit to prolong battery life. If your conservative and smart with your money then this mod is for you. I'm the big dummy type who spends it before its earned so ill probably fork out 20$ when this one stops holding up well
[Samsung Galaxy Nexus] mursepaolo:
Is BLX an app on the market?

I've been reading the past couple of pages and decided to use OEM battery with r185 and see how it holds up. What could be the problem with the 2100 Samsung battery?
[Samsung Galaxy Nexus] mike216:
I believe your going to be pleasantly surprised and you can control BLX using Franco's app
[Samsung Galaxy Nexus] mike216:
I bought my OEM 2100 battery on Amazon. Its supposed to be OEM but the packaging in my opinion was suspect. I could be wrong but it never produced like the 13% increase it was supposed to. Maybe I got burned or not? Its hard to say but I can't ever remember an OEM battery loosing so much life in 4-5 months. Hell my buddy has an iPhone and has put it through a beating by having all day conversations at work ( talks more on the phone then any female I've ever seen in my life) and its been going strong for years! That's what makes me think I should get at the minimum a solid year before it takes a ****. There both simple lithium ion batterys
[Samsung Galaxy Nexus] gaming09:
lol well yeah, but even at 1ghz it was just running through the battery i mean like a % a min
[Samsung Galaxy Nexus] FlipFlops24/7:
M4 and Later Issue w/ AOKP and LiquidSmooth

**AOKP/LiquidSmooth + Franco Kernel M4 (or Later) Problem**

I was using AOKP B37 and B38 with stock kernel and never had boot issues until I flashed Franco M4. I said "to heck with it" and gave LiquidSmooth 1.4 a try which comes with Franco Kernel #162. I had absolutely no issues with it until I tried flashing M4...then bam, after using it for a day I get a sudden reboot and stuck at boot animation screen (not Google boot image, AOKP/LiquidSmooth ROM Boot animation.

Two different ROMs, same problem with same kernel after doing complete wipes. I see on here and on other forums that people start having this issue of getting stuck at the boot animation screen and needing to restore a Nandroid or wipe/re-flash their ROM. Has there been any known problem with these recent Franco kernels from M4 on? Most of you seem fine but there is a small majority of people that are having the same issue getting stuck at the boot animation.
[Samsung Galaxy Nexus] azsl1326:
Anyone else having problems running 1.85 (384mhz)? I am on Liquid 1.4 and my phone won't get past the Google screen. Same issue also happened on AOKP b38. Did the standard install procedures:wipe cache, wipe dalvik, etc. Still nothing but the Google screen. Reverted back to 156 and all is fine.

Thanks.
[Samsung Galaxy Nexus] sledge3n8:
Yes, I did have the same "stuck at Google screen" problem after installing 1.85. I actually reverted back to M4 b/c it ran great for me. I didn't have a problem until I began undervolting. I used the same voltages as I did with M4 (at least the matching ones) and after a couple minutes my phone would reboot. This happened a few times until finally it hung at the Google screen. I had to Nand restore. I kept up-ing my voltages in increments of 5v each per reboot...to no avail.

GNex

AOKP b38 (Cuz Codename is out of service)

Franco

GTab 10.1 (rooted, AOKP), Iconia A500 (rooted, AOKP), Galaxy Player 5 (rooted, Eryigit), Galaxy Player 3.6 (unrooted - can't find an exploit yet), THC Rezound (rooted, stock [son's]), Droid X (rooted, Liquid Smooth [wife]), Samsung Stratosphere (unrooted [daughter]), Logitech Google TV (unrooted)
[Samsung Galaxy Nexus] sirmims:
If I wanna run my kernel at 1.3 instead of 1.4 would wheatley still beva good idea?
[Samsung Galaxy Nexus] EDNYLaw:
Check out the GSM thread http://xdaforums.com/showthread.php?p=27355627 one of the people complied a build with 100_OC_VALUE and it seems to be working out for people who couldn't boot Franco's build. I haven't tested this as mine runs Franco's build.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] kuronosan:
My wifi tether app doesn't work with 185 for some reason.
[Samsung Galaxy Nexus] Gahh Its Lee:
Seems to be a known issue.
[Samsung Galaxy Nexus] kuronosan:
Well that's a relief.
[Samsung Galaxy Nexus] zeke1988:
same boat with u
[Samsung Galaxy Nexus] timbck2:
I get the occasional random reboot (once a week or so) but I've never had it get stuck at the animation. I suspect that in most cases, undervolting is the most likely cause. I'm not undervolting beyond the values set by Smartreflex in Franco's app.
[Samsung Galaxy Nexus] azsl1326:
Not undervolting. It's a clean install of Liquid which includes 185. Simply gets stuck at the Google logo.
[Samsung Galaxy Nexus] sledge3n8:
Have you tried installing a Milestone version, M4?, to see if it will get past the Google screen?

---------- Post added at 11:15 AM ---------- Previous post was at 11:08 AM ----------

Thanks EDNYLaw! I will try this out once I confirm WiFi tether is working. I haven't had any issues with Franco...until Nightly 185. Hell, maybe I'll just try it anyway to see if it boots and stays booted. I can always go back to M4.
[Samsung Galaxy Nexus] azsl1326:
Yes M4 works.
[Samsung Galaxy Nexus] sledge3n8:
Did you check out this link that EDNYLaw put up? http://xdaforums.com/show...php?p=27355627
[Samsung Galaxy Nexus] mike216:
I wonder if some are not being patient. It can take up to 5 minutes sometimes to get past the Google logo after the flash
[Samsung Galaxy Nexus] a1exus:
can this be installed on stock ROM and would there be any benefits of doing so?
[Samsung Galaxy Nexus] azsl1326:
That looks like it's for GSM phones?

---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------

I haven't had it take more than a minute with any kernel I have ever flashed to get past the Google screen. With that said I waited at least 3 minutes before pulling the battery.
[Samsung Galaxy Nexus] sledge3n8:
If the stock rom is 4.0.3 or 4.0.4 I believe you can. The benefits are numerous. The biggest for me is undervolting which significantly increases battery up-time! My phone easily lasts the whole day now with normal/moderate use.
[Samsung Galaxy Nexus] sway40:
I get way past a day with normal use without touching undervolting. Imo and prolly fact is that undervolting won't be a noticeable difference.

You can flash the kernel on stock rom as long as your rooted

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
Undervolting is useless
[Samsung Galaxy Nexus] BrandT90:
My idle temps are down by a couple of degrees Celsius. It don't believe it has any performance advantages, but I wouldn't go as far as saying it's useless.
[Samsung Galaxy Nexus] sway40:
It's not a comp I game on so temps make no difference either, as long as your phone isn't melting in your hand or burning through your pocket again imo is just fine.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
I would say marginally useless. The initial few hundred mv that the voltage can be reduced helps, but those trying to squeeze that extra 25mv are only wasting their time.
[Samsung Galaxy Nexus] sledge3n8:
Not true for me. When I undervolt I gain battery up-time. It might be useless in your setup but I gain a couple hours when I undervolt and I make no other changes to the kernel settings. I believe a lot of the battery savings comes when in the idle state AND undervolted. Before undervolting I would unplug my phone from the charger and by the time I got to work I would be down to 90-92%. Now, after undervolting, I get to work and I am still at 98%. Most of the time from when I wake up to the time I get to work is all idle (standby) time.
[Samsung Galaxy Nexus] sway40:
Placebo affect

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kingoanklebreakn:
Yeah I agree. Undervolting doesn't even affect deep sleep does it?
[Samsung Galaxy Nexus] sledge3n8:
The numbers speak for themselves. How do u explain the increase in battery time. Is it coincidence? Why does Franco waste his time coding a placebo? Why do I gain time when I under volt?
[Samsung Galaxy Nexus] stick1300:
"No, guys, seriously, these Extenze really work!"
[Samsung Galaxy Nexus] TEK112:
Quote of the Day!
[Samsung Galaxy Nexus] blckngldhwk:
I have a complaint. I flashed 185 and ocd to 1500 and now my phone is too damn fast! I don't know what to do.
[Samsung Galaxy Nexus] gnexdude:
Lol

Sent premium
[Samsung Galaxy Nexus] XfrostX:
Anyone have trouble getting tethering to work with the latest nightly
[Samsung Galaxy Nexus] kuronosan:
Yep, appears to be a pretty common problem. Methinks it's the new wifi driver system. Franco'll probably get it fixed in the next one.
[Samsung Galaxy Nexus] impulse101:
Takes forever for a gps lock with 185 and AOKP 39
[Samsung Galaxy Nexus] snubs:
Running 185 on Revolution HD and I actually got a GPS lock, in the middle of nowhere, so fast that it blew my mind.
[Samsung Galaxy Nexus] TheGratefulDead:
i have same probl;em but its on all roms and all kernals wtf? i install and run gps status and tool box and it works but still takes bout 15 minutes to hook up never seen anyhthing like this before edit: so i just tried to lock on now and i open up maps and bam shows my location and two seconds later somehow im 4500meters accurate maybe its 4.0.4
[Samsung Galaxy Nexus] T-Keith:
Have you tried using something like fastergps to set your region?
[Samsung Galaxy Nexus] TheGratefulDead:
just installed and waited 10 minutes and still 4500

Sent from my GT-I9300 using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] kuronosan:
No tethering here still.
[Samsung Galaxy Nexus] diomark:
185 killed my wifi after a few hours... wouldn't see any access points... flashing milestone4 didn't fix it. What did fix it was wiping /system then reinstalling (the same cm9 nightly / milestone4.
[Samsung Galaxy Nexus] Mayze23:
No tethering here also.
[Samsung Galaxy Nexus] csseale:
I am in love with Franco!! #justsayin
[Samsung Galaxy Nexus] csseale:
And the screen on time....
[Samsung Galaxy Nexus] sway40:
Average, you should be able to get way better. Right now in at 8hrs at 62% battery with 1hr 26min screen on time. All this with ****ty signal at work.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
Not hatin, just saying it should be better.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Yatkoos:
186 fixed my flashing issue. Now I can finally stay up to date past m4. Thank you sir
[Samsung Galaxy Nexus] Stank0:
Wrked for me on 185. doesn't work on 186.
[Samsung Galaxy Nexus] EvoRocker:
what build you running?
[Samsung Galaxy Nexus] sway40:
Sorry should've specified that, im on 180 bc hands down it's been the best nightly in a while imo.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] laureanop:
Have you tried the 185 linaro build with the wifi fix ? Simply spectacular

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] mursepaolo:
How are you guys getting these insane battery lives??
[Samsung Galaxy Nexus] sway40:
Heard to many issues with new kernels, especially with linaro added in. I'll wait till everything gets ironed out, im becoming more comfortable just sticking with what works lately...if it's amazing that's a bonus, like 180. I can get 24hrs + battery with min 2hrs + screen on, on stock clock, stock battery, data on all the time (3g)...can't really ask for more.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Moonkae:
I've noticed when first flashing (especially new roms) it takes a while for GPS to get a lock but after this initial period it usually does it faster. I've been running liquid 1.4 for a while and with Franco's m4 its ridiculous how fast I get a GPS lock. Overall I've had GPS problems with any roms for the most part but the issue seems to correct itself over time.
[Samsung Galaxy Nexus] T-Keith:
I think it has a lot to do with screen brightness. I like a bright screen myself but try to use as much black as possible. Yeah I could get better life out of a dim screen, but not worth it to me if I can't see a damn thing.
[Samsung Galaxy Nexus] past_pluto:
Screen brightness, wifi, cell signal, app use are how they are doing it. I'm never getting over 3hrs screen time because I average 2-5 hours of Pandora a day.
[Samsung Galaxy Nexus] neederishelp:
Still getting wlan_rx_wake wakelocks on 189,any advice?
[Samsung Galaxy Nexus] Mikes30000:
189 Tethering works on unsecured network but not on WPA2. Any ideas?
[Samsung Galaxy Nexus] pluto22:
Anyone experiencing slow wireless performance on 189? I usually get 25mbps but I was getting around 5mbps. I toggled my wireless on/off and then I was back to normal.

I'm not sure if it's my network or the new kernel but I figured I'd post it in case anyone else is having similar issues.
[Samsung Galaxy Nexus] sway40:
Maybe your being throttled...just saying.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pluto22:
Nope, my PC and laptop both got 23-30mbps for over 15 mins straight. Rebooted the router too but my phone WiFi keeps slowing down.

It's getting late so I'll test at work tomorrow. If I get similar results I'll try and re-flash 180 to see if that's the culprit or if it's one of the other changes/apps I loaded today.

UPDATE: Flashing back 180 fixed the problem.
[Samsung Galaxy Nexus] fclifton:
Build 189. Still Wifi tethering is not working for me. Using WPA2 PSK. Galaxy Nexus LTE, ICS 4.0.4, IMM76K.
[Samsung Galaxy Nexus] npavlo:
Yup,

Toggling wifi fixes it for a while.
[Samsung Galaxy Nexus] racketier:
I've always had trouble staying in deep sleep on my company's wifi, and unfortunately this is still the case on r190. I'm using interactive governor and testing with CPU Spy.
[Samsung Galaxy Nexus] billku:
So 190, given that it's a wifi reversion, should fix my tethering problems, but it hasn't, sigh, still can't password tether. Anyone else, or is it just me?
[Samsung Galaxy Nexus] TEK112:
You could always use WiFi Tether Beta like I do and run an Open network with MAC Filtering.
[Samsung Galaxy Nexus] billku:
Yeah, I just discovered that it's only broken in the native app (on liquid 1.5rc), which I do love using as it's a simple toggle away, but at least I can use third-party apps now, even with password encryption...
[Samsung Galaxy Nexus] Amphibliam:
I'll be happy to give it a shot, but right now I'm rocking on demand on M4 which has everything working. Should I try 190 or wait?
[Samsung Galaxy Nexus] pluto22:
Yeah I went back to 180 this morning and WiFi is back to normal (12 hrs and I'm still getting 25mbps).

Work is insanely busy this week so it will be a few days before I flash 190 since I won't have time to troubleshoot/test any issues.
[Samsung Galaxy Nexus] pluto22:
Double post. Guess I'll just wish everyone a happy Monday to fill the space!
[Samsung Galaxy Nexus] Amphibliam:
Are people still having issues with Wi-Fi on 190?
[Samsung Galaxy Nexus] Turb0wned:
Can someone help me out. Im running cm9 with Franco's 190 nightly. I purchased Franco's app but I don't see the option for hot plug..
[Samsung Galaxy Nexus] grim281:
I think a while back franco saw that the OS was already "hotplugging" itself, so he took the option out of the app.
[Samsung Galaxy Nexus] TEK112:
Correct. The kernel is designed to already shutdown one core depending on load and conditions. It was deemed redundant and removed.
[Samsung Galaxy Nexus] Turb0wned:
Thank you. One more question. Which governor works best for battery life?
[Samsung Galaxy Nexus] TEK112:
That depends on how you use your phone. My suggestion is to try each one for three days and then you decide. Each one has its trade-offs.
[Samsung Galaxy Nexus] flytechguy:
Been finding Wheatley to work really well with a step down underclock wise. I get about 16-18 hours with slight to moderate use. Would probably last longer. Still using 189.
[Samsung Galaxy Nexus] MasteRaven:
Is Franco's kernel compatible with linaro roms?

ASAFP!
[Samsung Galaxy Nexus] TEK112:
I am pretty sure he made a Linaro specific kernel.
[Samsung Galaxy Nexus] BrandT90:
rogersnm has been kind enough to compile the new nightlies from Franco with the Linaro tool chain.

Here's the OP.

http://xdaforums.com/showthread.php?t=1708982
[Samsung Galaxy Nexus] alphanu22:
Updated the app

:(
[Samsung Galaxy Nexus] alphanu22:
fixed, THANK YOU!
[Samsung Galaxy Nexus] apaxi:
Fast USB charge setting is not retained using the latest two versions of Franco app after reboot. Tried M4 and nightly 181... same result. After toggling setting in Franco app after reboot fast USB works again. On CM9.
[Samsung Galaxy Nexus] upther:
I think this might be a CM9 issue. I had the same problem when I was on CM9.
[Samsung Galaxy Nexus] TEK112:
I had the same problem with AOKP 38 & 39
[Samsung Galaxy Nexus] rsantana:
M4 awesome

This M4 kernel is best i've ever tried. Been getting best damn results ever and this is on the extended 2100 battery if you're wondering. 4 hrs and 11 min in screnshot, but then I managed to get 9 more mins and have drop down to 2% This was all achieved with power saver mode on franco's app, and auto brightness on my phone with wifi on as often as possible.
[Samsung Galaxy Nexus] apaxi:
Ahh... I was afraid of that. Sorry for the false alarm. Are there any known workarounds to make the settings 'stick' on reboot?
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
It doesn't seem to stick at all, no matter the ROM or kernel, or even what you use to set the option. I am on AOKP with LeanKernel and the notification bar toggle doesn't stick either.
[Samsung Galaxy Nexus] LocoTSX:
I'm getting a weird problem with Google play music with milestone4. It'll be playing fine and then stop. I will have to press play again or switch songs. Its very intermittent. I've wiped the cache and still not better :/
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
This has been a problem with Google Music from Day 1.
[Samsung Galaxy Nexus] TEK112:
You have to lower the max sound one notch and it will play fine.
[Samsung Galaxy Nexus] LocoTSX:
Sorry, I'm new to Franco's. Thank you for the help.
[Samsung Galaxy Nexus] TEK112:
No worries. Glad to have you!
[Samsung Galaxy Nexus] SocialReject:
Good work.

Sent from the future.
[Samsung Galaxy Nexus] dadoc04:
thanks Franco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stick1300:
Franco, any chance we could see compatibility with this app:

http://xdaforums.com/showthread.php?t=1721895
[Samsung Galaxy Nexus] brmayhem:
It's been asked in the GSM thread and Franco said that he will add it.
[Samsung Galaxy Nexus] stick1300:
A. Dammit! I REALLY should keep up with that thread better

B. Yay!
[Samsung Galaxy Nexus] kingoanklebreakn:
The change in 191 is to add compatibility.
[Samsung Galaxy Nexus] stick1300:
How am i so bad at this thread?!
[Samsung Galaxy Nexus] kingoanklebreakn:
Lol. Don't feel bad, it's just rebooting when trying to enable it so my guess is the guy needs to update his app.
[Samsung Galaxy Nexus] cooch:
Can I please get a link to Milestone 3? Updated Milestone 4 via the app and it is killing my battery. It's the only variable that I touched. Thanks.
[Samsung Galaxy Nexus] EvoRocker:
Which governor do you run? I've been using 163 up until now, going to give 180 a shot.
[Samsung Galaxy Nexus] revolt1:
experienced my first reboot on 191
[Samsung Galaxy Nexus] sway40:
Ondemand, im still running 180... nothing has made me wanna switch.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
How long has it been on your phone, don't respond if it's less than a day bc that's not long enough to judge a kernel with battery.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Download cpuspy from the market and see if your phone is sleeping. If not, reboot into recovery and wipe both caches.
[Samsung Galaxy Nexus] sway40:
This is with 180, stock clock, stock battery, data on all the time (3g), wifi was on just last night and I had a good signal all day.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] LothianScykle:
Governers described

I'm not sure if this has been answered here before, but I was curious to know what the different governers did. I found this, which does a farily good job of answering that question.

http://blog.g4team.com/?p=5519

Cheers

~g
[Samsung Galaxy Nexus] upther:
I went from ParanoidAndroid(CM9 Hybrid) to CM9 to AOKP 38 which is where I'm at now. On the two CM9 ROMs, my color setting and the USB fast charge would not stick on a reboot. Now that I'm on AOKP 38, both those settings stick on a reboot.
[Samsung Galaxy Nexus] xavier86:
I flashed the latest build 191 and I'm using CM9 unofficial build 2012613.

Before I was able to play Max Payne and

GTA 3.

Now they just open, black screen and back to home screen. Here are the logcats. Maybe they will help you guys help me solve this.

GTA3: http://db.tt/VpKIErjl

Max Payne: http://db.tt/S4cOK9m8

Thank you very much.

Edit. I'm going to switch to the latest official and will see what happens
[Samsung Galaxy Nexus] franciscofranco:
You're actually not the first person to tell me a script doesn't work on reboot. It works for me to be honest and I have it like this:

#!/system/bin/sh

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
[Samsung Galaxy Nexus] EyeOfTruth:
That's what I figured I would do I have script manager installed and I think it has an option to run script on boot
[Samsung Galaxy Nexus] Musik847:
Franco are you supposed to open and close camera every reboot or just the first one? And should I force stop it or simple press the back button? Thanks.
[Samsung Galaxy Nexus] Timdor:
I don't see what the problem is then. Full 100% charge, fresh reboot, camera force close, disabled location services, disabled auto-rotate, and here were my results this morning:

All I did was drive to work and send a few text messages. 20% drain in 1.5 hours. :mad: You can see how much faster the battery drained as soon as I disabled wifi and stuck to mobile data.
[Samsung Galaxy Nexus] Elganja:
i suspect your phone isn't getting into deep sleep... get cpuspy from the market, it will confirm this (note, deep sleep != phone idle, but it's a good place to start)

once you confirm that, get an app called betterbatterystats from the market and see what shows up under partial wake locks.
[Samsung Galaxy Nexus] Timdor:
I'm using both apps. Deep sleep will account for 65-80% of the time and 300mhz will usually be the rest. Right now, better battery stats shows these partial wakelocks:

AudioOut_1 5m58s 4.5%

com.google.android.googlevoice.UpdateService 2m36s 2.0%

MAIL_SERVICE 1m8s 0.9%

and CPU Spy shows:

1200 - 10%

920 - 1%

700 - 1%

350 - 11%

Deep Sleep - 75%
[Samsung Galaxy Nexus] TEK112:
Check facebook and google+. Some have indicated facebook is causing unnecessary wakes and google+ may be doing the same. You can clear the data on both of these, then restart and toggle the camera. Also, if you are on Codename Android, I believe you have to toggle BT as well.
[Samsung Galaxy Nexus] Timdor:
As I said before, this was after a fresh reboot. G+ nor Facebook had been opened and neither showed up in betterbatterystats or the battery breakdown. I'm pretty sure they aren't causing it but I could be wrong.

I'll clear the app data for FB and G+ but I'm not sure that's what the problem is. If it was, wouldn't either G+ or FB be noted in CPU Spy or betterbatterystats?
[Samsung Galaxy Nexus] TEK112:
Since they are integrated into the OS, the battery querying tools will point at Android OS as the culprit. Heck, uninstall them completely just to rule it out.