yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Gil Smash:
Ive read through alot of it and all I can fidn relating to the app is the fact that some can download and some can't. Unless I missed something. I just get a 403 error everytime I try... I guess I should have said has anyone been able to download recently then. I saw something about the app being authorized by google in the last day or two but it still doesn't work.
[Samsung Galaxy Nexus] sinik420:
have you tried doing it via the market on the computer? also, what ROM are you running
[Samsung Galaxy Nexus] Stockmoose16:
Is there any way to confirm that hotplug is activated? I simply went in with a text editor to the file and changed the only piece of text, which was a '0' to a '1'.

I have to say that I switched to the Toro ROM and the Franco kernel and have not noticed much difference in battery performance. I've had the phone on for about 3 hours, and from a 92% charge, I'm already down to 13%. My screen on time is approx 1hr and 30 min.

I'd read that some got 6 hours of screen on time, but I'm lucky to get 2 hrs. Am I doing something wrong?
[Samsung Galaxy Nexus] Stadsport:
I think anyone who says they're getting 6 hours of screen on time is full of it, or they're putting it in airplane mode and letting it idle on a black screen. But 1.5hour of screen on to 13% is unacceptable, you've got some kind of drain going on. Battery drain should be next to nothing with the screen off, but I consistently get about 3 hours of screen-on time per full charge, a little more if I'm on wifi the whole time.
[Samsung Galaxy Nexus] dobo84:
So I wonder what is up Franco's sleeve next : )
[Samsung Galaxy Nexus] Stockmoose16:
Not much room for wake lock problems, I've now had the phone up for 3:20 minutes, with 2:20 minutes of that with the screen on. I'm at 4%. Most of the screen on time was used surfing the internet. I assume surfing will do more damage than just having the screen on playing with apps and settings. I've been on 4g the whole time, but in a strong area.
[Samsung Galaxy Nexus] Stockmoose16:
Here are my stats with Toro and Franco ROM.

Not great.
[Samsung Galaxy Nexus] sophware:
This is why I'm not allowed to have 60 tabs open at the same time.
[Samsung Galaxy Nexus] NexusMMM:
Okay, so Franco kernel definitely doesn't play nice with the CM9 kang. Willy try with GummyNex tomorrow. Hopefully battery life and general stability are better. If not, it's back to stock kernel which is just boring.
[Samsung Galaxy Nexus] Magnus_CA:
I'm also jumping from the Franco ship for a bit. I'm seeing low deep sleep numbers and a sharp decline in battery life for meager periods of screen on time. I'm also seeing high Android OS%, a problem I thought was well behind us. It's too bad because #12 was by far the smoothest and fastest kernel I've run with AOKP.

I'll likely be back when lucky #13 comes around.
[Samsung Galaxy Nexus] masri1987:
same here. battery was just absolute **** lol although performance and smoothness was top notch. i jumped to savaged zen for now until the next update. either way franco kernels have given me the best success.
[Samsung Galaxy Nexus] mike216:
It could be your rom throwing off those android OS drain numbers? I say that because I ran androidusers rom and got that android system drain no matter what kernel I tried. Let me know how the other kernel you try sizes up?
[Samsung Galaxy Nexus] Gil Smash:
Well right now it wont work at all on Redemption Rom but it showed as compatible with Gummy earlier today and it would still give me the 403 error and on the computer it would show up on my phone and then sit there with a loading bar and then eventually just go away...
[Samsung Galaxy Nexus] Stadsport:
Heh, I actually went in kind of the opposite direction. I installed CM9 Kang last week and ran it with imo's kernel and was getting some really bad screen off wakelocks for no apparent reason. I switched to Franco's kernel and got really good battery life overall. Yesterday, I switched back to the new GummyNex build and tried imo's kernel (even his latest 1.6.6) and it just didn't seem to be doing as nicely as franco's kernel. Once again installed franco#12 (this time on Gummy) and the battery life is better, but I actually still feel like I got better battery life out of CM9 kang.

The problem I'm having is right now, all ROMs seem to be pretty good in their own way, but none stands out to me. I'm looking forward to ARHD for 4.0.3, I suppose.
[Samsung Galaxy Nexus] mike216:
I just tried the current moseyonlean kernel for two days and Francos has better performance with the same battery life. So far I've tried everyones kernel I could find and this #12 is the cream of the crop! I'm going to keep this one in the A-kernel archives for safe keeping lol..

Another great thing about it is that it runs the coolest on my CPU
[Samsung Galaxy Nexus] franciscofranco:
Android OS % = some app keeping the system awake, nothing to do with the kernel. I can get 0% loss in 10 hours idle and while the screen is on it is using a lot less power than it did before, so I don't see how is it possible to have bad battery with this kernel.
[Samsung Galaxy Nexus] EyeOfTruth:
I went to the Gym and I streamed music for 2hrs bouncing from 3g and 4g (Using pandora) with screen on and off sending txt messages and I use my phone to track what I do at the gym (i use jefit) and made a 30 minute phone call. It only used about 30-40% battery. The screen is more on then off. But then again I run at max 920 and on conservative w/hotplug disabled. I am hoping hotplug enabled will give me better batter. Yes I have the extended battery, the question I Would ask people with bad battery issues is are you opening and closing the camera on reboot, do you leave programs running in the background or do you close it when your done, and then how many services do you have running in the background.

---------- Post added at 04:04 AM ---------- Previous post was at 03:52 AM ----------

Does hotplug get disabled on reboot. I ran the command to enable it and then rebooted my phone and it was disabled again. If that normal? And is it because I am not running Franco's App? Sorry franco I tend to prefer to do the commands manually as its better practice and helps keep part of my linux knowledge fresh since I deal with windows most of the day.
[Samsung Galaxy Nexus] TEK112:
What does your Cell Standby look like under Battery?
[Samsung Galaxy Nexus] mike216:
+1 ondemand is so much better on battery then the other great performing governors like interactive and wheetley. Having said that those governors are very good for pure speed
[Samsung Galaxy Nexus] mike216:
Get alogcat from the market and run it for a couple minutes. Post it,this will tell exactly what's running and not working properly
[Samsung Galaxy Nexus] mroneeyedboh:
Are there any recommended color setting to use with Franco's app?
[Samsung Galaxy Nexus] Shamrock13:
I feel like the application isn't keeping my settings. When I reboot, my governor is changed back to wheatly. The clock speeds are changed back to 1228 and 384. I have my power mode set to Balanced, and it's not changing any of my mHz. I changed the screen-off CPU to 192, but it's still showing up as 384 so I'm not sure if it's actually sticking.

Anyone else experiencing this or is it just me? :(
[Samsung Galaxy Nexus] TEK112:
I hate to ask the obvious, but did you check off set on boot?

Also, does the ROM have CPU controls which are set on boot?
[Samsung Galaxy Nexus] rdoane:
Two quick random question:

1. Does keeping USB fast charge on drain battery?

2. What gamma multiplier is everyone using? Specifically with the recommended color values.
[Samsung Galaxy Nexus] Gahh Its Lee:
No and I use 1.2. Sometimes 1.4 but I always go back to 1.2
[Samsung Galaxy Nexus] Shamrock13:
Gotta get all the info. I understand. There are neither built into this ROM, and before either this kernel or app update, I was on 166 and all of my settings stayed perfectly fine. I didn't change anything.

:(
[Samsung Galaxy Nexus] ShredEight02:
I'm having this exact same issue. After making a selection for power mode, it will just say none still and a change in governor, the clock speeds don't change. I dunno if it's just a visual bug in the app or nothing is actually being changed.

In the changelog Franco did mention that there are bugs and that he sent it out for testing and feedback, so I'm making a guess that he may be aware of this?
[Samsung Galaxy Nexus] cdchris12:
Here's an interesting error for you guys... Flashed M4 a day or so ago, then went to nightly #181 last night at work, both autoflashed via the app. Anyway, now, when I lock my phone, within a minute or two (literally, between 1 and 2 minutes after) my phone will unlock itself, show itself as charging, then show itself as not charging. My battery life curve now literally shows itself as a line almost straight down; I'm rocking 2 hours of (supposed to be) screen off time.

Any ideas? I'm willing to post a logcat if anyone is willing to look over it for me.
[Samsung Galaxy Nexus] djk21108:
Is there any reason the kernel has the default min clock speed at 384 MHz? The option for 192 is there but not selected. Does anymore use it?
[Samsung Galaxy Nexus] Gahh Its Lee:
I use it.
[Samsung Galaxy Nexus] Amphibliam:
So you guys recommend ondemand over wheatley and interactive. Wow. Never imagined that. I will have to give it a shot.
[Samsung Galaxy Nexus] Shamrock13:
Interactive feels a lot quicker and smoother. I don't know the toll it will take on the battery, but the on demand with balanced profile made my battery last for a while. I still can't get 4 hours on screen time like most of you guys. I don't use my phone much anymore anyway, but it would be nice.
[Samsung Galaxy Nexus] laureanop:
5 different phones and on demand has always been king. At least for me, Wheatley works better if I wanna use the 1.4 and 1.5 frequencies.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Dr01_D:
Anyone running nightly 181 with recent cm9 nightly?
[Samsung Galaxy Nexus] EDNYLaw:
I figured I'd post my resolution to an issue I just had in case anyone else has the issue.

Reading in the GSM thread about Franco's sdcard binary when flashing through recovery, I know some users are having issues with compatibility of programs. I usually flash the kernels through Franco's app because I'm lazy, but recently I flashed R181 through recovery. I plugged my phone into my computer today and I could see my files on my sdcard but they were the files that were there prior to my flash. I know this because I made a nandroid then flashed the kernel then on my phone renamed the nandroid. On my computer the nandroid was named as it is in CWM. I couldn't access any of my files on my sdcard from my computer, but I could access them just fine through my phone.

I figured I'd give it a shot and see if it was the sdcard binary messing with things. Through adb I pulled the binary from /system/bin (so I'd have a backup in case I fuxed something up) and took the binary from the ROM and

adb push sdcard /system/bin

adb shell

chmod 755 /system/bin/sdcard

exit

adb reboot

and it completely cleared up the issue. Just wanted to post that in case people run into that issue. Not complaining about the binary or anything, I love Franco's kernels and R181 with wheatly at 1.5 Ghz is tits!
[Samsung Galaxy Nexus] Dr01_D:
Running cm9 nightly 6/8 with the M4 kernel. Battery life is AMAZING thank you Franco
[Samsung Galaxy Nexus] timbck2:
What is Franco's sdcard binary? I've never heard of it before now.
[Samsung Galaxy Nexus] NeoandGeo:
Battery life is amazing in idle with nightly 180 I think. Only lose about 11% in a 10 hour period. Is there anything we can do to stop the battery from draining so much with the screen on? Seems like with auto brightness I lose 1% or more every minute even when I'm not doing anything.
[Samsung Galaxy Nexus] dr_w:
POLL

FRANCO,

I feel like there needs to be a poll with statistics. Sure the use of everyone's unique GNEX will differ but at least it will give us a snapshot of how everyones battery life is. Do you concur? If you do I will make a new thread with the information below. Definitely open to inputs as well.

The poll itself will be numbered (last 20 kernels) and users will vote on which gave the best battery life. Performance is clearly apparent in all your Kernels so that really isn't a factor in my opinion. People can certainly weigh in and comment on performance all they want but at this point, battery life is the topic.

Deliverables to contribute to this post: Must have screen shots of 'battery screen' and 'screen on' time. Must fill in the form below.

ROM using:

Script/Mod using:

Kernel#

Max CPU:

Min CPU:

Scaling Governer:

On battery time:

Screen on time:

Auto brightness: Y or No

Again, this will differ from person to person (too many variables) but at least we can all see how each is doing.

Endstate/goal: Helpful tool for fans of yours to just look at what others experience is without having to sift through 20 pages of forums.

Let me know, thank you.
[Samsung Galaxy Nexus] sway40:
I agree, with 180 battery life is the best I've seen in a while, with stock clocks, data on all the time, 3g(some wifi) no 4g, ondemand, I squeezed over a day of battery and 2 and a half hrs screen on time and had a few more percent to go. I also had a ****ty signal most of the day as well. Im always the one turning off my data but I've been running with it on constantly with awesome results.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] innov8ion:
Your experiment (poll w/statistics) is likely to provide near meaningless data unless common testing parameters (esp regarding usage) are used. Since that doesn't appear practical, a poll might serve more in detriment than anything. There's enough subjective posts as it is.

I just use Franco because I see that benchmarks show greater performance while battery life is still decent. Thx Franco!
[Samsung Galaxy Nexus] dr_w:
Using Francos kernel for benchmarks clearly shows you know what "meaningful data" is. Thanks for actually reading my request addressed to Franco where i clearly state that individual results are dynamic.
[Samsung Galaxy Nexus] EDNYLaw:
Franco included an sdcard binary that speeds up I/O or read/write or something but can cause issues with certain games and apparently with my computer ;) if you want more info check out the GSM thread around page 1882 on tapatalk.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] mike216:
I'm very happy with M4. I broke 3 hours of screen on time using data over a 16 hour period. First for me,I usually get around 2 1/2 hours of screen on using data. Wifi around 4+ hours
[Samsung Galaxy Nexus] ibenjakinov:
I also seem to have about 1% drain every minute or so. I have been looking into this issue and found a kernel from ch33kybutt (CMPlus kernel) that includes some screen state optimization and voltage adjustments. There is also a mod from bigeyes0x0 called the Trickster mod that allows you to incorporate the screen state mods on whatever rom/kernel you are currently running, but I don't know about these regulator voltage mods from ch33kybutt's kernel. Maybe Franco already includes these?

http://xdaforums.com/showpost.php?p=27092112&postcount=778
[Samsung Galaxy Nexus] mike216:
Has anyone noticed how Franco is able to make the UI so much more responsive then some of the others. If you try other kernels for a few weeks then come back and try one of his you really notice this. Very snappy kernel and it almost feels like he does something different to his? Even at stock speeds it feels quicker then some of the others OC'ed
[Samsung Galaxy Nexus] laureanop:
Completely agree

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] zeke1988:
his kernel and miui are the best combo. EVER!
[Samsung Galaxy Nexus] mike216:
I would say AOKP but that's the beautiful thing about Android ;)
[Samsung Galaxy Nexus] Veritas06:
Is anyone else having a problem after using the app to flash the Nightly Kernel? Sprint Nexus user here, & for like the past week, any time i auto flash the kernel thru the app my phone locks up at the bootloader.

Any solutions?

EDIT: Gonna be really pissed if i get locked out of Google Wallet because of auto-flash...
[Samsung Galaxy Nexus] TheSonicEmerald:
I pulled my battery, booted to recovery, wiped cache and dalvik, and flashed it from there. Rebooted, and it works :)
[Samsung Galaxy Nexus] Veritas06:
Thanks of the tip, don't know why that never occured to me. Wiped & flashed back to AOKP but the next time i try i'll let everyone know.

Thanks again!
[Samsung Galaxy Nexus] phydo:
Did anyone ever figure out why core two will shut down and never come back online? I'm having that issue. Power modes don't save it.
[Samsung Galaxy Nexus] spectrumfox:
Asking here in case anyone knows.

I replaced the stock kernel on 4.0.4 with Franco's, but I'm doing some testing and want to switch back. Anyone know an easy way to do this and what I need to flash?
[Samsung Galaxy Nexus] sway40:
Nandroid restore, unless someone has a copy of the stock kernel. I'll save you some testing though...francos kernel is all you need ever, the end.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Droid316:
Maybe not. different kernels work better on different phones
[Samsung Galaxy Nexus] Dr01_D:
I'm with sway I've tried other kernels but always come back to Franco its a disease for phone speed and I found it with M4
[Samsung Galaxy Nexus] fronc:
I saw that on 181. Hasn't happened since I went back to M4.

---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------

Guessing that Linaro optimization compatibility will be baked into 182? Is Linaro kernel-related?
[Samsung Galaxy Nexus] fishhelmet:
Afaik linaro does require a compliant kernel. Don't know what's needed to make that happen though.
[Samsung Galaxy Nexus] laureanop:
I couldn't pinpoint what was wrong with 181 where the phone would lag in certain responses and now I realize that it was behaving like one core was off. When I went back to m4 the problem went away.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Veritas06:
Still having problems flashing after wiping cache & dalvik. I flash, & get stuck at the bootloader. Anyone else with the same problem or a solution?

Thanks in advance.
[Samsung Galaxy Nexus] phydo:
I believe if you flash a clean kernel after that, you can check a log in a folder called "last_kmesg" which is basically the last shizz the kernel said before it crapped the bed. It might be worth a try

Edit: its /proc/last_kmesg

Edit again: it may be difficult to see what's going on. Might not be like dmesg output all pretty. But Franco may be able to give some insight if he sees that. I mean I'm sure you've checked md5s and stuff? I'm assuming by boot loader you mean at the boot animation? Or on the "Google" screen?
[Samsung Galaxy Nexus] mike216:
Hi sway,I came back to 180 and was wondering what's your favorite governor? I'm torn between all of them,well mostly between wheetley, interactive and ondemand. Thanks in advance bud!
[Samsung Galaxy Nexus] laureanop:
My two cents : wheatly if you wanna use the 1420 and 1536 frequencies . On demand for anything else

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] mcp770:
I'm giving the aokp linaro build a shot. Question is will franco kernel play well with the linaro builds coming out? The app is working great with the included imo kernel but I'm a die hard franco fan so I would like to switch. Linaro performs perfectly though so don't want to mess with anything unless it's compliant.
[Samsung Galaxy Nexus] Amphibliam:
GPS doesnt work on linaro. When you come back and tell me that it does, turn off Wi-Fi and go into NAVIGATION not maps.
[Samsung Galaxy Nexus] BrandT90:
I've been running Milestone 4 with AOKP Linaro since they released it yesterday. Everything is running smooth. :)
[Samsung Galaxy Nexus] spinkick:
Is it twice as fast?
[Samsung Galaxy Nexus] BrandT90:
I haven't had time to play around with it too much, but it is a little faster. Definitely not twice as fast, though. :p
[Samsung Galaxy Nexus] LexusBrian400:
I used GPS Status to test the GPS on that build.. It took 150 seconds to lock! Thats crazy, But it DID lock and it DOES work. For me at least... No wifi on.
[Samsung Galaxy Nexus] cabagekiller:
Any chance for a linaro compiled kernel? I've heard it has a much faster effect on performance.
[Samsung Galaxy Nexus] Gahh Its Lee:
There is a link floating around on the GSM thread. General thought seems to be it does nothing.
[Samsung Galaxy Nexus] azsl1326:
Running AOKP-Linaro and installed Franco's 185-Linaro and it doesn't play nice with my phone. It won't get past the Google screen.
[Samsung Galaxy Nexus] mike216:
Pull the battery. Leave it out for 2 minutes and fire up ;)
[Samsung Galaxy Nexus] EvoRocker:
How does it perform?
[Samsung Galaxy Nexus] azsl1326:
Truthfully, I did not notice a big difference in performance. I was running Liquid 1.4 with Franco's kernel (156) and it ran smoother and faster than AOKP b38 Linaro. I ended up going back to Liquid as the phone was heating up really fast with virtually no noticeable performance increases.

I know Quadrant scores aren't really good for anything, however just for the heck of it, I ran Quadrant on the Linaro build with the stock kernel and got 2500. Switched to Franco's kernel and got 3100. I think all we really need is Franco's kernel :) !
[Samsung Galaxy Nexus] past_pluto:
Aokp lags way more than liquid by default so that comparison is null and void.
[Samsung Galaxy Nexus] mike216:
I put my stock battery back in and battery life increased by 30%?

Strange smaller battery but is holding up much better. Simply amazing battery life on m4.

Don't know if my 2100 battery is damaged or worn out? Anyone have a similar experience?
[Samsung Galaxy Nexus] Gahh Its Lee:
How old is the battery? I'm curious if there is a way to test batteries to see if they are wearing.
[Samsung Galaxy Nexus] Amphibliam:
You aren't the only one. I was so pissed that I spent $30 on a piece of junk, but I just picked up a 2nd stock battery. Life is so much better.
[Samsung Galaxy Nexus] mike216:
About 5 months old. It shouldn't have worn out that fast?
[Samsung Galaxy Nexus] TEK112:
I was going to post a similar post. My extended battery never has charged to 100% even with the battery extender changed from 96 to 100. The only one however, did. Plus, it goes from 96/98 to 90 in about 5 minutes, then it tapers off. I may switch back to my old stock battery and see if there is a change. Maybe I will have to exchange the extra capacity one for another.
[Samsung Galaxy Nexus] Amphibliam:
Mine lasted maybe a month
[Samsung Galaxy Nexus] upther:
What's the best place to get another stock battery? I'd like to pick one up for when I'm hanging out on the boat.
[Samsung Galaxy Nexus] Dr01_D:
I feel that! Gotta have Pandora when I'm out on my Seadoo. Check Amazon.
[Samsung Galaxy Nexus] gaming09:
185 draining my battery like whoa, no kernel wakelocks, @ 1.4 with wheatly balanced power options, gonna head to the milestone till 186, ty for the hardwork franco !
[Samsung Galaxy Nexus] Amphibliam:
I got mine on amazon for like $15.
[Samsung Galaxy Nexus] mike216:
I ran alogcat and everything seemed fine so I said what the hell I'll throw my old but new battery in and see what happens. Battery life is sooo much better now! I might even break 3 hours on 3-4G ;)
[Samsung Galaxy Nexus] TEK112:
50% off through Verizon

http://www.verizonwireless.com/b2c/...d=12916&accessoryId=49869&initialPhoneId=5801

$19.99
[Samsung Galaxy Nexus] npavlo:
I am not sure what is wrong with my phone, but anything nightly 175 plus will not boot. I just sit on the "google" logo.

I have flashed different roms, wiped, super wiped, and completely cleared out my internal storage even. Right now I am testing with winners 6/8 cm9 rom.

I have been through the thread and this doesn't seem like a common issue! I have tried 185 384mhz also with no luck.
[Samsung Galaxy Nexus] TEK112:
It was suggested that you pull the battery wait 2min and put it in again.