yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kioshi:
Francos 290 kernal on stock 1800mah battery....

Good or bad?

Underclocked and undervolted

729 max 230 min

950mV and 825mV

Interactive governor

TCP congestion = cubic

IO scheduler (AOKP rom control) = bfq

Brightness 12%

3G from start to end on picture

Everything is synced. Google Now running the whole time. Everything set to "on" for location based. No GPS and WiFi on, thats about it.
[Samsung Galaxy Nexus] SnrSuave:
Tried M6 but phone seemed to be running real slow. Ran antutu multiple times and was getting barely over 3000. Tried latest nightly and had the same results. Flashed back to kernel provided with bugless beast and was in the 5000 range. I didn't change any options and it was interactive governor. Did I do something wrong?
[Samsung Galaxy Nexus] davidukfl:
So i wiped data/cache etc, reinstalled AOKP from scratch and reinstalled M6 from scratch...... still getting random data drops.

any theories?

Other kernels are fine, but not nearly as quick and smooth as M6 so i'd rather not have to use them
[Samsung Galaxy Nexus] b.huss2:
I was having some wake issues with m6. something kept poling during the day and killed the battery. It very well could have been fix with a wipe cache and reboot but I didn't even try it or look into the matter too much. just moved on to nightly 290. all good now. :good:
[Samsung Galaxy Nexus] Sleuth255:
back to r277 which had good voice/no data drops. So far, voice problems gone, and no data drops. The big test will be tonight when I hit the gym. Something about that location reliably kills my data connection when I head up from the locker room. Suspect the 3G-4G handoff...
[Samsung Galaxy Nexus] Sleuth255:
Ok... data drop today at the appointed place/time. I'm going to check to see if it has something to do with bluetooth being active during a 3G/4G handoff. I always fire up my BT headset in the locker room with 3G coverage and when I get upstairs, I'm back on 4G but the data connection is dead. Next time, I'll leave the headset off until after the handoff.
[Samsung Galaxy Nexus] AirBoss24K:
I'm having an issue where the System UI will stop working and I lose my nav buttons and notification drawer for about 30 seconds and the UI restarts. This has been happening about 3 times a day since I flashed M6. Wipe caches and reflash?

I'm also experiencing the random data/network drops. Is #290 any better?
[Samsung Galaxy Nexus] modernbummer:
Currently running r290 with latest build of BB and getting excellent battery life.
[Samsung Galaxy Nexus] TEK112:
Doesn't sound kernel related although a locat would help. I would just wipe caches and see if it behaves. If not, then start reflashing.
[Samsung Galaxy Nexus] tattedupboy:
About four or five times per day, regardless of which ROM and kernel I use.
[Samsung Galaxy Nexus] Shogun_Iggy:
The link in the original post says "for jelly bean version 4.1/4.1.1 only......but in previous statements in the original post it also says he has a download for 4.1.2....???
[Samsung Galaxy Nexus] TEK112:
Easy there, Punctuation Man!

It works with Jelly Bean versions 4.1 to 4.1.2. Franco probably didn't update the OP yet. He's a busy guy.
[Samsung Galaxy Nexus] b.huss2:
vvvvvvvvvvvvvvvvvvvvv
[Samsung Galaxy Nexus] iviustang50h:
Well that's not good (duh). Are you the only one experiencing this in your area? I had that happen earlier this year and it was a bad sim card. All is well since getting the new one.
[Samsung Galaxy Nexus] TEK112:
Bad SIM or bad hardware. Regardless, you are running out of time to get a device replacement which I plan on doing in the next couple of weeks.
[Samsung Galaxy Nexus] slayer621:
Just flashed the latest nightly (290 i think?) and now I can't boot. Recovery neither, only fastboot.
[Samsung Galaxy Nexus] TEK112:
Boot can take 15 minutes.

What happens when you boot normally?
[Samsung Galaxy Nexus] slayer621:
It sat at the Google logo. I definitely left it for a good 20 minutes, flashed it while I was pooping. However, I should note that it may have attempted to flash it twice, as when I clicked the "auto-flash", nothing happened so I hit it again.

REGARDLESS, I got it working. I downloaded the more stable Milestone 6, extracted the .img file, and used the Gnex toolkit to convert it into an Odin flashable .tar. Flashed it in Odin and it booted in less than 1 minute. Thanks for replying though.
[Samsung Galaxy Nexus] TEK112:
Sounds like a bad flash. Next time just flash in ADB through fastboot, much quicker. Regardless, it doesn't explain how you lost the ability to reboot into recovery... strange.

Anyway, glad you got it back up and running.

PS - 20 minute poop? You need more fiber...lol
[Samsung Galaxy Nexus] davidukfl:
I only get the data drops with franco or trinity kernel
[Samsung Galaxy Nexus] kioshi:
data drops has to do with location, imo. If I'm at work and crappy college classrooms, i go from 4g to 3g with two to one bars showing for data.

At home, i have three-four 4G bars but only two 3G bars.

I'm getting good battery life with nightly 290 with 1036mhz clock speed (instead of 729mhz) undervolted at 1125mV.
[Samsung Galaxy Nexus] mr4r4n:
not really i have a nexus that will wiiiiiiiiiiiildly vary with whats run on it and how it likes to mess with signal, its annoying as hell
[Samsung Galaxy Nexus] Sleuth255:
Today, I left my BT headset disconnected at the Gym and no data drop after the 3G/4G handoff. Looks like a connected BT device might have something to do with data drops during a handoff on r277 at least. Once I establish this (will need to try a few more times). I'll move to the latest daily and re-test.
[Samsung Galaxy Nexus] davidukfl:
The data drops happen anytime anywhere. I still show full signal 3g or 4g but there will be no data. Toggling airplane mode on and off again gets data going again.
[Samsung Galaxy Nexus] :
What settings do you guys use for the best screen on time? I'm on M6 BTW.
[Samsung Galaxy Nexus] kioshi:
Sorry to hear that, I've never experienced that where i have bars showing blue and data isn't working. Usually it will go grey/empty and show up again for me. Its really hard to pinpoint whats at fault here....could be kernal, could be the way the person flashed the kernal/rom, phone hardware, etc.. :(
[Samsung Galaxy Nexus] Sheetzie03:
Hello I was a big fan of M5.

I was going to move to M6 of course. I thought I would follow the thread a bit first before I did.

To the ppl who have been following the thread much more than I have and have actually had experience running this kernel, is it true that M6 to date has been functioning much less than M5 ever did? From what I'm reading, there has been nothing but trouble with M6. Is this true?

Any help would be great. Thanks
[Samsung Galaxy Nexus] Knowpig:
It's funny, I don't often use my Nexus as a phone......but I installed 292 yesterday (from 264) and so far calls have been fine.

Not sure what the issue was, but my calls sound perfect on 292 so far.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TheKeeperOfPie:
Yeah, if you're looking to upgrade from M5, I'd recommend r292. I had many problems, reboots, etc. with M6, but r292 seems stable. Some people have said they had problems running the lowest 240 frequency, but I run min at 384, so I haven't experienced that. If you need to use 240, the r294-test experiment should fix that, but I wouldn't recommend M6. Too many problems. :x
[Samsung Galaxy Nexus] Sheetzie03:
Thanks a lot buddy. I'll try 292 out.
[Samsung Galaxy Nexus] snubs:
Is there a reason that changes to the sampling rate aren't sticking? I make a change, exit, and they go right back to the default 30k.

Am I missing something?
[Samsung Galaxy Nexus] jcmm11:
What governor?
[Samsung Galaxy Nexus] kioshi:
285 nightly is up.

Running smooth for me, a little better battery life when streaming music via google music
[Samsung Galaxy Nexus] jcmm11:
I think you meant 295 :)
[Samsung Galaxy Nexus] snubs:
ondemand. If only certain governors can be tinkered with, I'll give em a shot.
[Samsung Galaxy Nexus] kioshi:
Yes sir, thanks for the correction. Never posting at 12am again
[Samsung Galaxy Nexus] Sleuth255:
r292: no data drop today at the gym. Good trend. Also, is it just me or is A2DP profile volume better on 292? My Halo 2 headset rocked Robert Plant on Pandora today... Ears are still ringing :)

Next up: voice call testing.
[Samsung Galaxy Nexus] jcmm11:
He played with the volume code.
[Samsung Galaxy Nexus] Sleuth255:
r292: So far, no issues with voice calls either. Good battery life too. I'm liking it!
[Samsung Galaxy Nexus] AirBoss24K:
Getting excellent results with r295 after having switched from M6 - which I did not consider a good experience.

I have a standard battery and got 15 hours on time. 2 hours screen time and 40 minutes talk time. Didn't utilize 4G at all. Wifi and service was quality all day. The experience was also very fluid with no to little "lag" between app changes and home screen scrolling. Probably my favorite nightly so far.
[Samsung Galaxy Nexus] bigbear6708:
Damn man...I wish I could get Franco to work again...tried m6, 292, and 295...all lock my phone up..have to battery pull. It was my go to up till m6...then not so good!!! Still can't get enough faux kernel...still testing battery life.. I can't make it a full charge without flashing...I just got an extended battery too...so life may not be an issue if faux keeps performing like it is!!
[Samsung Galaxy Nexus] warrior420:
Maybe it's just me but coming from stock everything seems to take a second to execute. Like apps, tapping home, apps drawer. Nothing seems instant like stock.
[Samsung Galaxy Nexus] EDNYLaw:
Depending on the ROM, check any conflicting init.d scripts. Specifically, any init.d scripts that are kernel tweaks, these may be interfering with Franco's settings and causing a lock up. It happened on a ROM that had always used, but Franco changed something in his kernel that conflicted with a kernel script. Deleted the script, no more problems. Highly recommend r295, 192Mhz undervolted to 700mv is all day battery plus some. Just excellent work.
[Samsung Galaxy Nexus] AirBoss24K:
I second your recommendation here. I didn't need to tinker with the Kernel or anything. Using CNA 3.6.5 with r295 and I'm getting 3 hours of on screen time with my standard battery (strong wifi signal for the most part with 4g disabled). This is an hour to an hour and a half more than what I was getting with M6 and some of the earlier nightlies. Great work!
[Samsung Galaxy Nexus] ramerco:
Just bumping this question. Franco can you answer/explain the lowmemorykiller? I think I am seeing weird behavior on Widget Locker and Nova Launcher since this change.. Example, sometimes widget locker doesn't showup leaving the stock lockscreen instead, and sometimes novalauncher seems to be relaunching (home screen is jsut blank for 2 seconds)
[Samsung Galaxy Nexus] Knowpig:
No idea what changed but..........

264 and 292 would lock up WiFi on liquid rc5.

With 295 the WiFi is fixed.

But phone talking was better on 292.

Sent from my Galaxy Nexus using Xparent SkyBlue Tapatalk 2
[Samsung Galaxy Nexus] Natolx:
Franco

Thank you so much for Milestone 6! It fixed the 4g antenna problems on the lemon replacement phone Verizon sent me :)
[Samsung Galaxy Nexus] BlaJod:
I have a standard battery as well and Im on the AOKP Milestone 1 with Francos Milestone 6 and battery life obviosly could be better. Do I need to download the 312 or 524 GPU version, and also what about the R298 version, any feedback on it (battery life is a big concern right now)?
[Samsung Galaxy Nexus] EDNYLaw:
Because the GNex isn't the greatest with battery life, you have to work with it a bit. I get at minimum 4 hours of screen on time and a day's worth of operation. I have the VZW GNex with the 2100 maH battery. Here are my settings (your mileage may, and most likely will, vary):

Phone: 4G LTE while out or work, WIFI no data at home, bluetooth when on phone or listening to music, GPS off unless using maps

ROM: AOKP based Hybryd B24 (made by DHO a member of team Vanir, check out romdroidhacks.com for more info)

Kernel: Franco r298 (soon to be r300 it looks like) here are my Franco Kernel updater app settings:

max: 12xx

min: 192

governor: interactive

governor controls:

above_hispeed_delay: 60000

go_hispeed_load: 65

hispeed_freq: 729 MHz

min_sample_time: 45000

timer_rate: 15000

input_boost_freq: 537 MHz

CPU Undervolting (these are my settings, yours WILL vary as it's wholly dependent on your silicon, test and find out or rely on Smart Reflex)

1228: 1150mV

1036: 1075mV

729: 875mV

537: 850mV

384: 775mV

192: 700mV

max screen off frequency: 537 MHz

IO scheduler: deadline

Screen brightness: less than 25% (don't use auto-brightness, uses too many CPU resources)

Accounts: all I have syncing is GMail, GWallet, Contacts, Calendar and Google Music for my primary email account, that's it except for once a week on WIFI only (meaning when I'm at home) facebook sync happens (not the FB app, just a picture sync for contacts)

Apps: Get rid of Facebook, it's the worst coded app ever, download better battery stats and see if there's a rogue app causes excessive wakelocks

Automateitpro: I use this app to automate everything so I don't worry about radios being on when they're not needed. Some of the rules i have are turn off WIFI when disconnecting and turn on data. When I connect to the cell towers around my house WIFI is turned on and when it connects it turns off data. Bluetooth on for phone calls and music, off when disconnected from Bluetooth device or ending phone call... things like that. All things you can do manually, I just don't want to think about it, plus it ensures no radio is on when not being used.

In my experience, these settings provide phenomenal battery life and really good performance. The only lag I get is sometimes when waking up it takes a couple of seconds before I can swipe to unlock the screen, I'd imagine this is because of the 192 MHz slot being used. Whatever, that doesn't bother me. As for lag, I really don't see any. I used to use 14xx as my max but then lowered it when Franco said 12xx was his max and I haven't looked back.

That's all I can think of as of right now. If you have more questions, ask away.
[Samsung Galaxy Nexus] guywmustang:
So, here's an interesting question. I keep seeing the kernel wakelocks "wlan_rx_wake" and "wlan_ctrl_wake" which I think are due to my setting of having the Wifi always on during sleep in the Wifi->Advanced settings. But I find this strange as I have the Wifi manually set to "off" all day.

I read somewhere that the kernel has something to do with this, and how the kernel is setup will make some kind of difference. Does anyone know anything about this?

I just now turned it so Wifi is off during sleep, because I'm seeing these wakelocks when at work on 4G, wifi powered off and not connected to anything, but I have the Wifi manually off with a toggle. Input?

This is with:

VZW Galaxy Nexus

Codename Android 3.8

Franco r298 - stock settings
[Samsung Galaxy Nexus] EDNYLaw:
Try changing the setting to avoid poor WIFI connections. This should help as it'll ignore weak signals.
[Samsung Galaxy Nexus] bolt_of_thunder:
Anyone experience very slow to non existent charging while the screen is on? Using build 295.
[Samsung Galaxy Nexus] AirBoss24K:
I was chewing through kernels like candy but I'm still on r295 (paired with CNA 3.6.5) because I was so happy with the results. I'm using the 312 GPU version.

I've also recently upgraded to a 3800mAh battery and I must say I love getting 5 hours of screen time. If you're concerned with battery life to the extent I was and don't care much about the sleekness of your device, I would recommend the Hyperion Extended Battery off Amazon for like $20. I can go very heavy usage for a good chunk of the day and maybe need the charger at the end of the day, but for the most part I've been going 2 days (about 36 hours including 5 hours of screen time) without a charger. I've gone through roughly 5 charging cycles with the battery and have yet to push it to its limit - I bet I could get 6 or maybe even 7 hours of screen time on a single charge if I have an extremely heavy day of usage.
[Samsung Galaxy Nexus] bigbear6708:
I've have similar issues on sorcery with this kernel ever since m5...I think it has something conflicting in init.d. over my head..so I just flashed a new kernel till I have time to search
[Samsung Galaxy Nexus] EDNYLaw:
You guys can try adjusting the VFS Cache Pressure (use JRummy's app or something similar for kernel tweaks) or navigate to /proc/sys/vm/vfs_cache_pressure and try lowering the value from 300 to something between 300 and 10. That's how aggressive the kernel reclaims cache, may make a difference with RAM.

You might also try adjusting the low memory killer values found in /sys/module/lowmemorykiller/parameters/minfree I know Franco was adjusting these in the late 280's and 290's so you can try playing around and seeing if those help. I can tell you running an AOKP kang with stock Franco r298 my phone flies and sips battery.
[Samsung Galaxy Nexus] :
For done strange reason I get poor battery life on r298, although on milestone 6 I get much better results. I don't know, im using MMuzzy's ROM currently with the stock CPU frequencies, interactive, and have the screen off frequency at 729MHZ. Anyone getting the same problem?
[Samsung Galaxy Nexus] BOY_:
I was running JB kernel with mmuzzy's ROM and it was solid until 4.1.2 then I started having weird issues with lagging lock screen and streaming music apps becoming non responsive. I stopped running the kernel and have had no issues since. Battery and performance are pretty good. Not sure if it's a related issue but it sounded similar.
[Samsung Galaxy Nexus] :
Hmmm... using it right now but not experiencing what you're saying. And I really wanna keep Franco because it has awesome mods :)
[Samsung Galaxy Nexus] TheHunterOfShadows:
Good idea thanks! I installed 268 again, so i'll see what it was set to for that, then reinstall 295 or so and check those settings and adjust.

So i did that, the pressure was the same between 268 and 295 (20) but the low memory killer had much lower values in 295. so I used 268 values and will see if that helps. Thanks for your help!
[Samsung Galaxy Nexus] guywmustang:
So, after turning the Wifi always during sleep to "Never", I have gotten definitely better battery life. It doesn't keep the "wlan_ctrl_wake" wakelock active. Yesterday I got about 12 hours to 50% with 40 minutes of screen on mostly 4G. This is still with stock setting-ed Franco r298. I also set it to avoid weak wifi connections as another user had stated.

Give this setting a try, and see if it helps you.
[Samsung Galaxy Nexus] TheHunterOfShadows:
Well here's a question, how do I get those modified values to persist after a reboot?

" /sys/module/lowmemorykiller/parameters/minfree"
[Samsung Galaxy Nexus] EDNYLaw:
Make an init.d script

Quick tutorial

go to /system/etc/init.d

make a new file (no extention) and name it 37lmk (the name doesn't really matter just pick a 2 digit number not already in that folder and lmk for lowmemorykiller)

edit the file with the text editor and put:

#!/system/bin/sh
echo "8099,10132,20000,20000,50000,100000">/sys/module/lowmemorykiller/parameters/minfree

save and exit

Replace the values above with whatever values work best for you
[Samsung Galaxy Nexus] TheHunterOfShadows:
Boom!! Worked, and thus far this change seems to be working for me. Not sure why JBS, my installed apps, and the lower mem setting don't jive, but for the moment raising these helps. Thank you for your help!!!

Another question, does any one have a link on the color based command line commands exist for this kernel? Would like to do this same thing for the some color multiplier, gamma and contrast setting i'm doing manually with trickster atm.
[Samsung Galaxy Nexus] EDNYLaw:
Terminal commands for all the options in this kernel:

Color Multipliers:

echo r g b > /sys/class/misc/colorcontrol/multiplier

Replace r g and b for 2000000000 for stock color. If you want to change the colors just replace the first 3 numbers of each r/g/b with 0-400 of your choice.

Gamma Control:

echo r g b > /sys/class/misc/colorcontrol/v1_offset

Replace r/g/b by -255/200 of your choice.

Fsync:

echo 1 > /sys/module/sync/parameters/fsync_enabled - to enable

echo 0 > /sys/module/sync/parameters/fsync_enabled - to disable

Sound Control:

echo i > /sys/devices/virtual/misc/soundcontrol/volume_boost

Replace i with 0-3 of your choice.

Sound High Performance:

echo 1 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to enable

echo 0 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to disable

USB Fast Charge:

echo 1 > /sys/kernel/fast_charge/force_fast_charge - to enable

echo 0 > /sys/kernel/fast_charge/force_fast_charge - to disable

wifi_pm:

echo 1 > /sys/module/bcmdhd/parameters/wifi_pm - to enable

echo 0 > /sys/module/bcmdhd/parameters/wifi_pm - to disable

Trinity's Contrast:

echo i > /sys/module/panel_s6e8aa0/parameters/contrast

Replace i with -25/16 of your choice.

BLX:

echo i > /sys/class/misc/batterylifeextender/charging_limit

Replace i with 0-100 of your choice.

OMAP Gamma interface:

echo i > /sys/devices/platform/omapdss/manager0/gamma

Replace i with 5-10 of your choice.

Thermal Throttle:

echo 1 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to enable

echo 0 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to disable
[Samsung Galaxy Nexus] TheHunterOfShadows:
Geez! The biggest tip any one can ever give, is, READ don't just look at the instructions. Stupid mistake on my part. I saw this somewhere else, but thought maybe they didn't apply to the vz kernel because i was having issues. For the color multiplier, i was using 3 digit values. Kept wondering why the screen would go black :o

Thanks again, all is good now. have a script that runs at boot to adjust mem settings, and the color settings. ahhh, life is good :)
[Samsung Galaxy Nexus] EDNYLaw:
Glad to help, slow day at work :D also, you should definitely follow Franco's other GNex kernel thread. It's all the same CMDA/GSM in terms of the kernel. That thread has taught me a ton and the man himself will drop in on occasion and throw some stuff out.
[Samsung Galaxy Nexus] Rob_Storm:
I love your kernel and use it on all my devices for which you support.

I'm in need of some help and will gladly pay for your service.

I am in dire need for a gnex kernel that includes the 2 way call record patch.

I must have the capability for businesses purposes as well as an adoption process I am currently going through.

Can you please help? You name the price.

Sincerely,

Rob Storm
[Samsung Galaxy Nexus] EDNYLaw:
I'm not sure if this fulfills your needs but if you place a call using Google Voice and hit "4" during the call it records the call.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] wtherrell:
TCP Congestion Control Algorithms

I have searched this forum and also (ugh) Wikipedia an this. I sorta understand what it does. But there are so many choices in the Kernel. How do I decide which one I should use? Point me in the right direction, someone, please?

No particular problems, just want to understand.
[Samsung Galaxy Nexus] EDNYLaw:
Just flash a kernel and try it out and see what's the best for your phone. Everyone's phone is different so no one can tell you what's the best for your phone. I really only use Franco's kernels since the work best on mine. Low power consumption and super fast and stable. Flash it and give it a try.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] wtherrell:
Thanks for the reply. Yes, I like Franco's kernel as well . Somehow I left out part of my question though. I was really asking about TCP Congestion Control Algo's. Cubic, Reno, Westwood, etc. I have about 7 devices that regularly use my WiFi network and was wondering about these whether one could be favored over the others.