yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
Yes stock is just like that. During screen off Wi-Fi gets in a semi power saving mode and the connection strength gets cut off big time. Enabling Wifi_PM will force the driver not to enter that power saving mode during screen off and it will work as normal.
[Samsung Galaxy Nexus] sachilleas:
Perfectly explained. Thank you very much!
[Samsung Galaxy Nexus] kecinzer:
I'm experiencing again data drops. When I changing network types (2G/3G) sometimes I completly lost data. Only reboot helps. I had this problems if past, and solved by clear data of franco.Kernel updater. So I try it again.
[Samsung Galaxy Nexus] LibertyMonger:
Hi all, not sure if this issue has been reported, don't think so but I started to have issues with my power button after a few days of using 268 (I think that's the right number for the latest nightly) when I tap the power button to force sleep it brings up the power menu. I just flashed back milestone 5 and it is working fine now.

***edit

Never mind, still having the same issue with milestone 5 so it may be the ROM. Running snap black.

So I think I will try blackbean for a bit and try to figure this thing out
[Samsung Galaxy Nexus] bradm23:
If not ROM issue it may be a hardware issue. The power buttons on these phones are used a lot and tend to break down over time.
[Samsung Galaxy Nexus] osm0sis:
After a bit more testing, most of the blocks run "none" (I'm guessing the ram, loop and dm blocks), only 4 have schedulers (mtdblock0, mmcblk0, mmcblk0boot1 and mmcblk0boot0 I assume), and only mmcblk0 defaults to bfq. The mass echo you proposed to all the subfolders doesn't work, but even the working method I found would probably be a bad idea, since even franco has only set just mmcblk0 to bfq, leaving the others running deadline..

So to be on the safe side, I'm going to assume people should probably only change the scheduler for mmcblk0, and can do so following the original method I posted. :)
[Samsung Galaxy Nexus] Astug:
I'm getting horrible battery life with the latest nightly. :(

2h of screen on time at the most and I hit the 15% mark in 40-50 hours.

I'm running Bugless Beast, with dyninteractive at 1228/230.

Any tips or tricks? :cyclops:

EDIT: This is mostly idle even! I'm not a heavy user, I don't play games, sync is not on but data is enabled 100% of the time.
[Samsung Galaxy Nexus] franciscofranco:
mmcblk0boot partitions are the boot partitions, dont worry about them at all. mtdblock may be mounted but I doubt we have anything using mtd partitions, they are legacy stuff used when Google mounted partitions with yaffs2 as a file system. I still think yaffs2 should be the one used as a main file system, ext4 is mainly for rotational devices. Yaffs2 is named Yet Another Flash File System. Its aimed for NAND memory blocks and its aimed for high performance. Maybe Google decided to go with ext4 because its maintained by mainstream Linux Kernel... who knows really.
[Samsung Galaxy Nexus] osm0sis:
So would there be any effect if we switched them all to bfq?
[Samsung Galaxy Nexus] Piccles:
Give Paranoid Android a try (tablet ui is awesome!)

Sent from my Gnex
[Samsung Galaxy Nexus] :
Re,

I use System Tuner pro: https://market.android.com/details?...ult#?t=W251bGwsMSwxLDEsImNjYzcxLnBtdy5wcm8iXQ

:)
[Samsung Galaxy Nexus] pan466:
scroll lag

Guys i think i found the scrolling lag problem.

The cause to scrolling lag is layers...

When a second layer comes on top of the main one scrolling fps decreases by half or may be even more. I can give an example for you to see:

Open market on your phone and download an app after download you will get an information or two like desktop shortcut created. this warning creates another layer on screen. Now when its still visible try to scroll, you will notice that until this layer is gets invisible your scrolling will suffer from really low framerates.

You can see this everywhere when a pop up comes out or even when you try to scroll with keyboard open.

may be thats about nexus high screen resolution but i dont think so, i think its ics code related. it happens on all roms and kernels i ever tried on my nexus.

Coming from an S2 i must say i am really impressed with this phone other than this issue i have a really smooth, fast and bugless (not mentioning unoptimized apps) phone thanks to google, aokp rom and franco's kernel.
[Samsung Galaxy Nexus] kecinzer:
franciscofranco:

Can I ask you what ROM do you use?
[Samsung Galaxy Nexus] Dr_Ownage:
To answer the question for him, he is running AOKP milestone 1 unless he has updated this morning when build 14 came out.

:P

sorry franco stole ya thunder :P
[Samsung Galaxy Nexus] sirj00:
Good morning to all. Just to help those that are still looking for a rom

to match with this great kernel.

Axiom 2.4 with nightly 10 is a match made in heaven.

Bench scores are phenomenal and battery life superb.

11hrs later 5% battery drain sipping 12ma per hr.

Lag what lag, none. Tie your seat belt and hang on.

Hope this helps people on the fence regarding which route to take.
[Samsung Galaxy Nexus] inffy:
WEll yeah...Axiom is a LTE ROM, and this is GSM forum...so no dice :)
[Samsung Galaxy Nexus] Dr_Ownage:
does anyone here use Light Flow?
[Samsung Galaxy Nexus] sethyx:
Yes, I do.
[Samsung Galaxy Nexus] slimfady:
Just to confirm,

We're talking about this bootloder:

http://xdaforums.com/showthread.php?t=1394076

Right?
[Samsung Galaxy Nexus] kecinzer:
Dr_Ownage:

Thank you for reply, but I want reply directly from franco :).
[Samsung Galaxy Nexus] jkoljo:
Nope, this one: http://xdaforums.com/showpost.php?p=20725207&postcount=2835

TL41D - 4.0.1 = primekj10

ICL53F - 4.0.2 = primekk15

IML74K - 4.0.3 = primekl01
[Samsung Galaxy Nexus] Dr_Ownage:
Negative, http://dl.dropbox.com/u/6390060/bootloader-maguro-primekl01_fastboot_flash.zip

are you one of the people experiencing high drain?

this might be the cause... apparently it causes high wake periods in AndroidOS
[Samsung Galaxy Nexus] slimfady:
Thanks :)

10char
[Samsung Galaxy Nexus] Felixpau86:
Battery and speed of this kernel is insane.
[Samsung Galaxy Nexus] sethyx:
Nope, my idle drain is 0,5-1%, depending on network signal strength, with full sync on.

However my AndroidOS percentage is sometimes ridiculously high in the battery menu, but I don't think that has anything to do with LightFlow.
[Samsung Galaxy Nexus] chrisexv6:
Me too, just because Im curious as to why Im not seeing any color differences with the same setup he seems to have (Im actually running AOKP latest build, not milestone, along with the latest nightly of the Franco kernel)

The rest of this kernel rocks....idle drain is very very little, no lag, etc. If it could make my screen color temp a little cooler (at it seems it should), it would be perfect.

Only difference is that Im on LTE.....does that make a difference to the color portion kernel? I didnt think it would.
[Samsung Galaxy Nexus] apsis:
I dont know why some people keep saying that franco's kernel is a battery drainer...

Uploaded with ImageShack.us

Uploaded with ImageShack.us

Looks great to me. And Wifi didnt even disconnect when Screen turned off.

So in my oppinion, absolutely great work from franco. Just wish it would be possible to buy his app outside from the market. (Havent registered a credit card in android market)

Maybe its a bit off topic, but because it was discussed on the last pages, do you guys know if there's a flashable *.zip file for the new bootloader to flash it on CWM? I dont know much about fastboot,thats why.
[Samsung Galaxy Nexus] igotgame:
Does anyone else notice that when on WiFi you have more awake instances than when not on Wifi?

I can't figure out why on 3g I don't see hardly any awake instances on the battery stats, but on Wifi they occur every so often. I have everything off and no syncing whatsoever.
[Samsung Galaxy Nexus] nmesisca:
????WTF Wifi???

Hi all,

I know how this will sound... :confused:

I have the strangest of the issues with wifi here.

wifi is off, 3g is off.

browsing (as you would expect) doesnt work.

but I still get emails and gtalk messages????

its not the first time this happens to me either.

is this even in the realm of possibilities? :)

update: opened gtalk, all seems offline, all contacts greyed out etc. decided to write to a friend.. although delayed he got the message. and my gtalk says "sent at..."
[Samsung Galaxy Nexus] aron7awol:
I think it has to do with how frequently it needs to "check in" with the router. Really, though, even on wifi my drain while sleeping is minimal. Less than 1% an hour.

As far as Light Flow, the only state I could see it having to keep waking the device up is if you have multiple notifications and it needs to wake up to switch the color. With zero or only one notification, it doesn't need to wake the device up, as it simply sets the color and frequency of the light in a file and the system takes care of the rest. I think you can change a setting in light flow to have it use priority and show one color rather than cycle between multiple colors, but I haven't tried it since my drain is still minimal even when I have multiple notifications going for hours.
[Samsung Galaxy Nexus] franciscofranco:
Dont worry about that. We only use mmcblk0p1 (its the internal memory partition where /system /data /cache etc are stored in), thats what matters.
[Samsung Galaxy Nexus] osm0sis:
Thought so, thanks! :)
[Samsung Galaxy Nexus] P30SiNa:
Nice Job Franco & Minooch.

Best battery life since I got this phone. and wlan_rx wakelock is not high anymore with r268 even better than stock wifi drivers.

No undervolt. dyninteractive. 384 Mhz / 1036 MHz
[Samsung Galaxy Nexus] saintpanache:
Just had to do a battery pull. I have a GSM Gnex running MiNCOv4 with franco kernel r268. I tried rebooting in recovery from MiNCO's menu. My screen went black and my device stopped responding. I pulled the battery and everything is now fine, including booting in recovery.

Log : http://db.tt/0yOTxwS1

Any idea?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Wh1t3Rose:
I'm gonna try this kernel now for the 1st (excluding the few days I was MINCO) lol your first sentence in the OP made me lmao. You seem like a kool guy Franco. I hope you kernel is just as cool. Especially with battery life. :)

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] shr33kant:
I had something similar to this, Did you just get a green android lying on it's back with a red X on it whenever you try to go into recovery mode? If so I think you need to re-flash your recovery via fastboot.
[Samsung Galaxy Nexus] saintpanache:
Nope, it just would not turn on.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] drawde40599:
Roll back to working rom backup or try different ROM, AOKP build 2 has been working 100% flawless with Frank kernel (s) http://aokp.co/index.php/news

---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------

On.(384gpu) 268 with aokp build 2, Im getting 3.5 hours + OC to 729/1305 dynintinteractive so try different different rom if already been few days of ****ty life my recommended "fix"
[Samsung Galaxy Nexus] Puzzlegirl:
I went back to Interactive (all Franco settings) and my battery life improved amazingly.
[Samsung Galaxy Nexus] ssglackey:
I had this also, but on milestone 5 and minco v4.
[Samsung Galaxy Nexus] farfromovin:
So did I...
[Samsung Galaxy Nexus] osm0sis:
Just went back to it today myself, with the old hispeed_freq = 1037000 tweak, and I've gotta say, r268 is unbelievably smooth! :good:
[Samsung Galaxy Nexus] irizwan:
I think 268 could be considered a milestone release :P smooth i'm getting great battery.
[Samsung Galaxy Nexus] RoscoeDpG:
has anyone run a day with interactive and a day dyninteractive and see which one gives better batt life? so far ive done interactive and after 2 days i got 1 day 7 hrs of uptime with 4 hrs screen time 2hr 30 min talk time with this 3800 extended batt but wanted to see some normal stock or 2100 sized batt
[Samsung Galaxy Nexus] franciscofranco:
Not yet, I'm doing some experiments with Smartreflex and Core voltages etc. More news soon, waiting for minooch to test my ****s.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the log, but logcat is a bit useless. Logcat is for rom stuff, dmesg is for kernel stuff. How to get dmesg log is in the OP.
[Samsung Galaxy Nexus] gzub:
zRam support?

Franco,

I saw back a bit that you rejected the possibility of building the kernel with zRam support, just wanted to see again if you thought about adding it. I am asking as it got included in the CyanogenMod Kernel build for Tuna (http://review.cyanogenmod.com/#/c/23775/) and looks someone has submitted some init changes to support it as well (http://r.cyanogenmod.com/#/c/23777/)

I have read some information on it and it seems like it might help, but not sure and would love to hear your explanation as to pros/cons...

Geoff
[Samsung Galaxy Nexus] ÜBER™:
From what I've been told its for older devices and not necessary. Its pretty pointless on our devices. Also morific has spoken to cyanogen about zRam still being in the options for new phones and has since removed that option.

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] ac3theone:
+1

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Just like UBER said ZRAM is so ****ing useless for new phones. ZRAM just compresses swapped data into memory ram. Since we have 1GB ram with usually only 300mb used, we rarely if ever hit 80% of our total capacity so ZRAM is really useless and it would create overhead during scanning and actual compressing.

:)
[Samsung Galaxy Nexus] saintpanache:
@franco here is my last_kmsg

http://db.tt/t2H9cvNV

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
GPU driver crashed: [ 8104.176208] PVR: PVRSRVDriverShutdown(pDevice=c78a4000)

Are you using 512Mhz GPU?
[Samsung Galaxy Nexus] saintpanache:
Nope, I'm using nightly r268 384mhz with the latest MiNCO rom. No tweaks to the kernel either.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] creeve4:
What am I doing wrong?
[Samsung Galaxy Nexus] franciscofranco:
Nothing, its my derp.
[Samsung Galaxy Nexus] creeve4:
Thanks, I was thinking maybe ROM issue or something...

Do you have a fixed 512 version?
[Samsung Galaxy Nexus] franciscofranco:
Oh my phone, yes.
[Samsung Galaxy Nexus] Savant:
You devious tease.
[Samsung Galaxy Nexus] Hungry Man:
Are there any plans to include a lower IVA and/or CPU frequency in the future? Or a higher GPU frequency?

I'm also wondering if instead of going from 153mhz to 307mhz to 512mhz if it couldn't go 153mhz to 307mhz to 384mhz to 512mhz so that it doesn't have to jump from 307 to 512 as often.

If any of this is possible that would be really cool.

And if anyone knows how to stress test the IVA I'd appreciate that.
[Samsung Galaxy Nexus] franciscofranco:
I'm not touching IVA. Also not adding anything lower than 230Mhz on the CPU. Higher GPU frequency is also tricky, most of us wouldn't be able to run it.

Yes I can add an extra step for 512Mhz and see what happens.
[Samsung Galaxy Nexus] franciscofranco:
r272:

* I removed the hacky routine for disabling SR for some frequencies so now we gotta make the device to boot with our desired voltages on certain frequencies. So for 230Mhz SR is disabled, from 1420Mhz to 1804Mhz is also disabled. Core OPP1 also has SR disabled. Smartreflex calibrates this OPP too aggressively and it causes a few data drops in the long run. Booting it with more voltage and no calibration should help on data dropage.

* Add an extra step to GPU driversm 384Mhz on the 512Mhz build class. Should reduce the amount of times 512Mhz is used.

* Some other patches and merges from android-3.4
[Samsung Galaxy Nexus] Culex316:
how come I cannot set both min and max CPU Speed at 384mhz? I can't even set the max CPU speed lower than 729Mhz in the app....(using latest nightly r268 with stock ROM)..is this an app bug or a kernel thing?
[Samsung Galaxy Nexus] creeve4:
The 384 step for the 512 GPU causes the GPU to jump up and down causing stuttering in some games.
[Samsung Galaxy Nexus] Wynnded:
Why on earth would you wish to do that on a device as spectacular as this?
[Samsung Galaxy Nexus] ingbrzy:
Hi franco...

little bug in the app... dont showing download file size when downloading with "yes - bring it on"
[Samsung Galaxy Nexus] Culex316:
For testing purposes
[Samsung Galaxy Nexus] Wynnded:
That's been reported I'm pretty certain.

Oh, okay.
[Samsung Galaxy Nexus] creeve4:
Is the an app like CPU Spy, but for the GPU?
[Samsung Galaxy Nexus] LeftForLiving:
I'm running CM10 and would like to run this on top of it for the battery improvements however it breaks the color tweaking settings on CM10 under Settings > Advanced. Any chance you can add in support for that? Not sure how complicated that is.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joeyfong:
It is not complicated, he will not do that.
[Samsung Galaxy Nexus] nuwan32:
For me it doesn't even download. Stuck at 0. Will have to do it manually
[Samsung Galaxy Nexus] dehein:
I have discovered that the - 1B bug only occurs whilr pressing the autoflash button. Using the download button everything goes fine. Maybe this can help.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Fenvarien:
IVA and Core voltages are higher @idle with SR compared to the previous nightlies. IVA uses 987 MHz (previously 886) and Core 925 MHz (previously 860).

GNex with franco.Kernel R272 / MiNCO ROM
[Samsung Galaxy Nexus] atiartstudio:
@512 latest release NenaMark2 lag "very well" 11.2fps . My max fps are 33.2 with previous release

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ÜBER™:
384 GPU got 32.6 FPS on nenmark2

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] ahse0w:
flashed r272, on every boot there's the starting apps sign.

didn't have this on r268.

edit: flashed back to r268. still there. not sure how to get rid of it.
[Samsung Galaxy Nexus] Mayday_XL:
No problems with the r272. :good:
[Samsung Galaxy Nexus] styr:
With dyniteractive (in r268 and r272) my logcat is spammed with this:

11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.614 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.615 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11:10:55.615 Error Tuna PowerHAL 368 Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device

Please advise.
[Samsung Galaxy Nexus] slvrarrow:
I'm seeing a lot more choppiness when scrolling Web pages. At 1ghz max 384 gpu default interactive sites such as xda in desktop mode would scroll as smooth as butter in 268. This may coincide with the above report of lower nenamark performance?
[Samsung Galaxy Nexus] chugger93:
My phone was at 99% taken off the charger just before bed, I wake up and its at 86%. That's with wifi off, gps off, 3g data off. Doesnt seem right. Although i'm running and have been running r249, don't remember it doing that before, but then again I'm on a new nightly of jellybro.

I guess its time to flash the latest and greatest 268 or 272. Well it was 268 as of yesterday when I checked these forums, lol.
[Samsung Galaxy Nexus] arhung:
flashed 272-gpu512, seems the battery drain faster than 268-512gpu, but it just a feeling, looking forward for a more few days.
[Samsung Galaxy Nexus] kyokeun1234:
Seems like a lot of people are having issues... Maybe I'll skip this flash....
[Samsung Galaxy Nexus] joaquinf:
Reporting bugs and issues is part of the beta testing stage and the more is reported the more polished the milestone version will be. Flashing a nightly and don't give proper feedback (logcats) when you experience any problem make things harder for Francisco. If you want to be passive is ok, but please don't spam the board with posts like this, it doesn't add anything to the development thread.

Thanks
[Samsung Galaxy Nexus] lucas4ever:
+1
[Samsung Galaxy Nexus] yyz71:
Yep this new one is working nicely:good: Seems very smooth.No problems to report. Thank you franco:highfive:
[Samsung Galaxy Nexus] tobitronics:
How do I reset my kernel settings to franco settings? Running 268 with franco updater app.

And is 272 any good?

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] caioketo:
Is kexec enabled in this kernel?

If it is, can I call it by terminal emulator???
[Samsung Galaxy Nexus] franciscofranco:
IVA is fine. Core is higher on purpose, read the changelog.
[Samsung Galaxy Nexus] yellowdie:
Okay, this just blew my mind. I've been running 384/1420 min/max voltages and it's been fine, but my wife was complaining about it seeming slow. So I decided to bump the min to 729 and OH MY GOSH!! It makes things SO much smoother! So I now run 729/1305 and it is BLAZING fast! And battery doesn't take much of a hit at all! Yesterday I had 1 day 8 hours with 3 hours of screen time, and that left me with 25% battery. That's better than I normally do!! So 729/1305 is my new AWESOME SWEET point!! :D Just figured I'd share the love. :good:
[Samsung Galaxy Nexus] franciscofranco:
r273:

* Remove 384Mhz GPU step in the 512Mhz GPU build, only 3 steps now.
[Samsung Galaxy Nexus] nktje:
Just wanted to say thank you. All my wifi woes seem distant after switching from cm10 nightlies to minco. Awesome work. Performance and battery life are simply outstanding. Thank you :)
[Samsung Galaxy Nexus] tobitronics:
Anyone?

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Wipe app data in settings or with titanium. 272 seems good so far, battery is to early to tell. I'm updating to 273 now which should sort out the few minor scrolling lags.

Suggestion to Franco, maybe 1xx 384 and 512 would be better steps to have as the 3 chosen steps?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thats exactly what we use. 157Mhz, 384Mhz and 512Mhz.

The 384Mhz build is 157Mhz, 307Mhz and 384Mhz.
[Samsung Galaxy Nexus] The Gingerbread Man:
I knew youd know best haha

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shadow_empire1:
Hi Franco,

when downloading/flashing you kernel I always have this:

/ -1B
[Samsung Galaxy Nexus] styr:
Happens in r273 too.
[Samsung Galaxy Nexus] :
me2 - it's only with Auto-Flash, downloading the zip-file is fine
[Samsung Galaxy Nexus] TyroneLT:
Just curious to know what governor you were using.

---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------

Just curious to know what governor you were using.
[Samsung Galaxy Nexus] guidocioni:
Hey franco, dunno if it's a bug or me but...today I was listening to music with Google play music and the volume was very low.. So I opened your control app and saw that the volume booster was on 3.. Not possible! So che I've tried to go back to 2. Same. Finally going back to 1 boosted my volume a lot, I think almost 100% (i was in the train and folks all around me were scared by me all of a sudden :D). Was my fault or a problem in the volume control? Anyway now I get nice volume boost only for step 1. The others step are getting the same value from my hears and it's too low.

Cheers!

P. S. Have you Read my email?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] TEK112:
Remember, the audio enhancements only affect the headphone jack. If you were listening to it through the external speaker of your device, the volume hack was not involved.
[Samsung Galaxy Nexus] Moz007:
How can i desactivate the fast charge message at boot ?