yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
Thing is the minimum voltage allowed is 840mV on the kernel voltage header file, thats why it didn't calibrate lower than ~830mV. If you disable SR however you will be able to undervolt that step a little bit further, but thats about it.

Not directly to Wi-Fi, but to TCP.
[Samsung Galaxy Nexus] yellowdie:
Does that apply for stuff that's taken out of SR's control? And is 192MHz being touched by SR right now?
[Samsung Galaxy Nexus] nikulogical:
It could very well be something else but I'm missing a lot of texts today, like they're not coming in. Happened about 4 times that I know of. Using r290 which I flashed this morning. Could it be the kernel?

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] osm0sis:
Interesting, how did you get 230MHz down to 820mV then? Just something from hardcoding it out of SR? Maybe you could do that same for 192MHz then.
[Samsung Galaxy Nexus] franciscofranco:
If you disable SR you will be able to go down as much as you want. Yes 192Mhz is being calibrated by SR, 230Mhz wasn't so I thought that might be the problem with 230Mhz on r292.

Not that I know of, no one reported something similar.

Yaps.
[Samsung Galaxy Nexus] schizophrenia:
having SoD with min set as 230Mhz...

at least twice already
[Samsung Galaxy Nexus] yellowdie:
Cool. So did our testing (and rambling) help? You gonna leave 192MHz under SR's control at 1000mV?

And I'm likin' whatever was changed in deadline. Things feel snappier, and I didn't think that was possible! lol. My max is set at 1036 and my phone is flyin'. :D

EDIT: Ah, and I see we got bumped to 3.0.47. Nice. :) But seriously, this is crazy. It's so fast and smooth, it feels like the phone knows what I am gonna press before I do. Lol
[Samsung Galaxy Nexus] Shadow-Nexus:
Hey I have created a thread on which anyone can share their kernel info and battery stats if anyone is interested
[Samsung Galaxy Nexus] franciscofranco:
Bump it to 384Mhz.
[Samsung Galaxy Nexus] kyokeun1234:
YOU SUCK FRANCO!

Since that caught your attention, I would like to say that your kernels are awesome and I'm enjoying too much with this kernel! Everything runs smooth and now Wi-Fi seems to be improved, along with call volume. Awesome job :)

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] osm0sis:
I gotta say, it DOES feel faster and smoother again, even running with 192MHz (UV at 725mV) min. That first swipe in the apps drawer doesn't seem as slow to start anymore. Did franco somehow rediscover the r276-7 magic?! :D Definitely hoping he'll hardcode 192MHz to 725mV. :good:

Edit: On second thought, seeing a bit more microlag when going from the app drawer to the homescreens using the home button at 192MHz min. Might just be a tad too low. :(
[Samsung Galaxy Nexus] Shadow-Nexus:
Hey Franco I have found a bug in the Franco kernel updater app

When setting the clock speed for screen off if I press the 3xx option it triggers the 7xx and if I press the 2xx it triggers the 3xx

Is it a bug or is it supposed to be like this?
[Samsung Galaxy Nexus] BigBake88:
R290 may be the smoothest kernel I have had on my gnex to date. Thanks, Franco.
[Samsung Galaxy Nexus] yellowdie:
Okay, this is disgusting.

Up until a few days ago I was running 729 min / 1036 max. Recently Simms convinced me to try 384 again so I have been running 384/1036.

I just set my min to 192 and my MAX TO 729 and this kernel feels *FAST*!!! WTH?! 729 max and it's super smooth!! INSANE. Just insane. I will try this for a while and see how it goes. Lol. I will probably end up going back to 1036, but this will give me crazy battery. Lol.

(max screen off is 384, stock battery). :D :D :D
[Samsung Galaxy Nexus] schizophrenia:
did..... thanks

just saying the problem is there with me too.
[Samsung Galaxy Nexus] franciscofranco:
Hmm thanks, I'll see what goes.

I know, thanks :) as far as I can see its fixed on r294_test. I'll let it run until tomorrow and if all is ok I'll release it as nightly.
[Samsung Galaxy Nexus] Blackcrx:
Noob question. Why is everyone running such low CPU speeds? I've ran 230-1228, 384-1228, 729-1228, 729-1036. The battery usage seems the same on all the settings but 729-1228 seems the best overall for me.
[Samsung Galaxy Nexus] schizophrenia:
does it all depend on what is your usage pattern?

i think logically listening to music running 729 seems to consume more battery than 230?
[Samsung Galaxy Nexus] BigBake88:
Hmmm 1228 slot seems to be buggy in the app. It seems to revert to 1200 and since this kernel doesn't even have a 1200 slot it doesn't use 12xx at all and will use 10xx and below. Can anyone else replicate?
[Samsung Galaxy Nexus] franciscofranco:
Do another auto-flash of my kernel, should fix that.
[Samsung Galaxy Nexus] Blackcrx:
I thought so too before. But in the nexus s forums a user tested battery drain while running the music app. He tested 100-200-400-800mhz. Ironically 400mhz used the least about of battery.

I use the music app when I'm at the gym. Honestly, 230-384-729mhz all seemed to drain relatively the same. But then again I'm usually only at the gym around and hour or so.

Feel free to try it out yourself and let me know what your results are.
[Samsung Galaxy Nexus] omar m5:
Does M6 works with 4.1.2 ?
[Samsung Galaxy Nexus] schizophrenia:
i use Rmap and MyTrack very often and I remember half a year ago when MyTrack ran on 729Mhz and the phone heated up real fast and battery went down over 30% within an hour as well but usually MyTrack/Rmap can last for 6 to 8 hours running at 230Mhz with screen off.

But of course I dont know if any kernel related stuff changed now that 729 runs as little battery as 230 nowadays.
[Samsung Galaxy Nexus] sajty:
Sure.
[Samsung Galaxy Nexus] atiartstudio:
Why 2nd core is off at interactive?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Shadow-Nexus:
Do you have a power mode on?
[Samsung Galaxy Nexus] atiartstudio:
Edit : r294 fix core off/online

No

Also I have some unknowing lag from full memory . Maybe is ROM related.

Sent from my Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Thanks Franco for 294 test build and app update. I'm running 192 at 725mv and so far so good. I'm at a training day today for a new job I'm starting very soon so I probably won't have chance to post much I doubt. Just wanted to say thanks! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
That is the great debate. :)

Man, everyone is gettin' new jobs! lol
[Samsung Galaxy Nexus] gaich:
Don`t know whether it is kernel related, but after more than 2 hours of hard testing 292-512(2 hours of battery=2 hours of screen)-chrome,games and gmail without rest - my wifi internet stopped almost completely, skype did not open, internet pages either, 294 kernel download proceeded some 10 minutes since 72 to 74 percent, all I maneged to open was an incoming message in gmail. On the computer the same wifi internet had no problem. I had to reboot the phone, everything returned to work fine. :confused:
[Samsung Galaxy Nexus] schizophrenia:
so where is the r294? it's actually the r292 if I download from the app?

or do I have to autoflash to get the r294?
[Samsung Galaxy Nexus] Wynnded:
Remembering that it's experimental.... http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/experiments/
[Samsung Galaxy Nexus] yellowdie:
Two pages back:

:highfive:
[Samsung Galaxy Nexus] schizophrenia:
thanks.. would you happen to know if it's a GPU384 or 512?

i saw he mentioned it but i dont see any link and that's why i asked.
[Samsung Galaxy Nexus] shawnaye:
Quick question, i've updated my ROM to AOKP B5 which shows my amount of ram usage, been checking and checking, but i'm never ever able to get more than 200mb of free RAM even though i kill all my apps.

It's kinda irritating to having to continuously launch chrome and wait for it to load whenever i need it.

Does the heavy RAM usage gotta do with the kernel?
[Samsung Galaxy Nexus] danielvc:
This is me with Minco + R294 and a few apps running.
[Samsung Galaxy Nexus] JarGnex:
I think this has been discussed before, but does any one get a little noise (kinda like a scratched music CD) while playing songs on power amp ? I like power amp , that's a bit annoying though. I'm using stock values on minco v4 latest exp kernel
[Samsung Galaxy Nexus] Hans QC:
Temperature problem?

Are you sure the phone didn't get too hot? Thermal throttle can slow the processor down.
[Samsung Galaxy Nexus] franciscofranco:
What that many rogue apps I would be impressed if you could get a good battery life lol.
[Samsung Galaxy Nexus] shawnaye:
hmm.. seems like the number shown on the running apps page is miles away from what the aokp task manager shows.

obvious whose fault it is now. haha.
[Samsung Galaxy Nexus] danielvc:
Well, AOKP isn't really known as a stable and ****-free rom :)

I know there are a few rogue apps and I don't have a problem with them (I'm not shouting here Y AMZ I NOT GETTIN 4 HOURS SCREEN ON TIME!!!). Still getting 2.5-3 hours screen on time with ~ 15 hours of use and that's enough for me. I really like to have a colored LED-notification (Light Flow), automatic photo upload (Dropbox) and Facebook-messages/notifications. And I use Maps a lot and I don't want to freeze/unfreeze is constantly. I just turn GPS off when I'm not using it.

And uhm, the Heart Container Battery-widget is awe-some! :)
[Samsung Galaxy Nexus] Raijin:
Have init.d this kernel? Thank you.
[Samsung Galaxy Nexus] shawnaye:
Talk like yoda, you do.
[Samsung Galaxy Nexus] Raijin:
Any useful answer?
[Samsung Galaxy Nexus] shawnaye:
no init.d

search the thread dude, you'll get tons of answers saying it's ROM dependent.
[Samsung Galaxy Nexus] IAmAN00bie:
Yes it supports it.
[Samsung Galaxy Nexus] Raijin:
@shawnaye: Before posting, I found this:

@IAmAN00bie: But no system/etc/init.d folder. Maybe only need to create it?

Thank you both.
[Samsung Galaxy Nexus] franciscofranco:
Yes create that folder.
[Samsung Galaxy Nexus] BigBake88:
Franco, I tried auto-flashing 292 from 290 to try and correct the max frequency in the app bouncing back to 1200mhz (no matter what frequency I set it to) and it did not work. I tried reflashing 290 in recovery and wiped cache and dalvik (i know they have nothing to do with the kernel, but just wanted to make sure) and had the same issue. Auto-flashed 292 again and still had the issue. I uninstalled Franco updater app and went to trickster to see if this fixed the issue. It did not. I tried fixing permissions in recovery and it did not work either. Even going to the governor control for interactive had high speed for 700mhz and not 729mhz. I have never had this issue before and am out of ideas. :confused::(
[Samsung Galaxy Nexus] Raijin:
Working perfect! Thank you.
[Samsung Galaxy Nexus] osm0sis:
Normally true, it's either ROM or ramdisk. Most kernels don't replace the ramdisk so that leaves it up to the ROM, but franco does, so init.d support is enabled when flashing franco's kernel, regardless of ROM. For example, I'm on stock and it works fine. ;)

---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------

In other news, I'm running 192-1536MHz (192MHz@750mV, SR on for 384-1305MHz, 1420MHz@1250mV and 1536MHz@1300mV), 729 screen off max, 1036 hispeed_freq, and my most recent tweak which makes a world of difference in terms of device responsiveness is 80000 above_hispeed_delay. Feels like a new phone! :good:
[Samsung Galaxy Nexus] yellowdie:
Rock on. :) I'm still running 192-729 and it's surprisingly fast! lol. Don't forget that Franco said 192 IS being controlled by SR in this build. 230 was not in the previous ones, but he changed it in r294.

Also, above_hispeed_delay is "how long do I wait when I hit the hispeed_load mark before I actually ramp up to the hispeed_freq." So I used to have it between 80000-100000, until I found out that stock is actually 20000. So that means we were making it wait LONGER before jumping up to high speeds.

(Documentation: https://github.com/sakuramilk/sc02c_kernel_ics/pull/19.diff). So try knocking it down to 20000 and it makes it jump to higher speeds sooner. :D :D

My temporary setup:
Min: 192MHz @ 750mV
Max screen off: 384MHz @ 1000mV
Max: 729MHz @ 1100mV
above_hispeed_delay: 20000
go_hispeed_load: 50
hispeed_freq: 729
min_sample_time: 40000
timer_rate: 20000
input_boost_freq: 729

:):D:laugh::good:
[Samsung Galaxy Nexus] osm0sis:
Cool! What are the other interactive tunables set to in stock? hispeed_load would be an important one to knowif we're going to drop our response time.

Also, yes 192 is SR controlled, but since it only SR calibrates it to 830, as soon as we go below that it circumvents SR and gets undervolted. :good:

Edit: Okay, checked out your link. above_hispeed_delay is 20000, but hispeed_load is 85% and hispeed_freq is max_speed. So Franco is clearly using the hispeed system differently from stock to provide an initial bump without going to the max where stock ramps all the way up, so I'm not sure how useful carrying the stock tunables over really is. :( Definitely could shoot for some middle ground though. :)
[Samsung Galaxy Nexus] yellowdie:
Ah, true, good point. And hispeed_load default is 85%, which I think is crazy. But check out that link above. That's the most comprehensive list I've found that answers ALL the questions on it:

Between that link and this thread: http://xdaforums.com/showthread.php?t=1369817. I have learned a ton, and that's where I came up with my settings from the previous post. :)
[Samsung Galaxy Nexus] franciscofranco:
I'm currently testing this to ship with r295 (I'm skipping r294 number):

go_hispeed_load: 70

min_sample_time: 50000

timer_rate: 30000

I set my min to 192Mhz (since its slower than my usual 384Mhz I can take account if system is slower or faster with different interactive settings) and I've yet to see any lag. With higher go_high_speed load it takes a little extra time on lower frequencies. timer_rate (default 20k) = cpu frequency transition latency which is 30ms. min_sample_time (default 60k) = minimum rate spend on higher frequencies before it can ramp down.

Would be very nice to cook up some balanced levels to ship the kernel with so keep your tests coming.
[Samsung Galaxy Nexus] schizophrenia:
deleted
[Samsung Galaxy Nexus] c_86:
Read his entire post... you'll see
[Samsung Galaxy Nexus] TheKeeperOfPie:
Wifi Problems

Yay! Someone else is having this problem. I mean, no! Someone else is having this problem! D: After a random time of usage, the wifi completely shuts off. The wifi toggle on my rom doesn't work, it never finishes scanning for a network, and apps that use the wifi connection don't work at all. I'm not sure if this is kernel related, but it should be at least looked into. The only way to fix it is a reboot.
[Samsung Galaxy Nexus] TEK112:
This happened to me once. I wiped caches and reflashed and it hasn't come back. If you want to help him, provide logs.
[Samsung Galaxy Nexus] BigBake88:
Bump. Anyone have any other suggestions or ideas? Not trying to be a nag Franco, just want to see if I am missing something before I just wipe everything and start from scratch, which obviously I would like to avoid. :(

Edit: Running Latest Rasbean Jelly....
[Samsung Galaxy Nexus] TheKeeperOfPie:
Do you know how to pull the log? It doesn't crash, so the log wouldn't record it, would it? The system itself still functions, just the wifi doesn't scan properly.
[Samsung Galaxy Nexus] TEK112:
This will be the easiest way.

https://play.google.com/store/apps/...rch_result#?t=W251bGwsMSwxLDEsInNjZC5sY2V4Il0.

Skip the logcat, just copy the dmesg.
[Samsung Galaxy Nexus] sunra0815:
Hi!

Thanks for this great kernel and App!

My Color settings does not stick after a reboot.

I could make a init.d script but I wonder why the settings I do in the Kernel Updater App has to be restored via my backup after every boot.

... sorry for my bad english.
[Samsung Galaxy Nexus] franciscofranco:
I have no idea, seems like a PowerHAL issue or something. My kernel automatically installs the correct HAL but I guess something didn't go alright with you.

Use SuperSu...
[Samsung Galaxy Nexus] BigBake88:
Thanks for the response, Franco. Is it possible I had three bad downloads in a row between 290 and 292? Oh well, I guess I will reflash my ROM and then reflash your latest nightly. Looking forward to 295 and if Minco V5 ever comes out for Toro I'd lake to make the switch! Thanks for your awesome work!
[Samsung Galaxy Nexus] sunra0815:
Ah, ok ... after updating the su binary it works. Thanks a lot!

This is my first dualcore device and I use the interactive governor with the timings you have postet above.

I´m searching for the best performance I could get. Battery drain is not a big problem for me because I have a second battery and a charging station ...

Is the interactive governour the best choise for max. performance except the performance governour?
[Samsung Galaxy Nexus] yellowdie:
Did you undervolt your 192MHz? Just curious if that's something you're even thinking about doing. I've never used less that 384 before, but if this all goes well, maybe I'll make the 192 (or 230) my bottom. For me it's all about smoothness and performance. So we'll see. :)

From what I've learned by reading and doing my own tests:

I gotta say, this is fun! :D I love testin' and trying new stuff like this. :laugh: :highfive::good:
[Samsung Galaxy Nexus] BigBake88:
Yes, go with interactive. Default setting with Franco work great, and interactive is the most "optimized" governor from google for Jelly Bean.
[Samsung Galaxy Nexus] yellowdie:
Yep, Interactive is the best. And we're trying to find the absolute best settings for everyone. :) Try out some of the different settings and feel free to post what you think about them. :)
[Samsung Galaxy Nexus] !crazy:
Have you maybe forgotten one of your system apps which is setting the frequency to 1.2 GHz? Try removing all such apps except the one you really need.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just a little report 294 has been 100% stable for me, used 192 min CPU set to 725 MV. I made 2 calls which were not quiet, infact the call quality was excellent so that sound bug seems to be fixed. This kernel is rocking well indeed!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
The defaults you wrote are wrong, this are the defaults from JellyBean.

cpufreq interactive governor: timer 20ms, min sample 60ms, go_hispeed_load 50%, above_hispeed_delay 100ms
[Samsung Galaxy Nexus] BigBake88:
yea only tunable app I have is Franco kernel app, and there is no built in tuner for Rasbean. I really am at a loss lol. The previous kernel I ran didnt even have a 1200mhz slot either lol.
[Samsung Galaxy Nexus] yellowdie:
You're right, I stand corrected. I edited my post to show the right go_hispeed_load and above_hispeed_delay. :) Thanks.
[Samsung Galaxy Nexus] osm0sis:
Wow! Lots of great info here! I attempted to split the difference and so far I'm liking the following:

above_hispeed_delay 60000; go_hispeed_load 60; hispeed_freq 1036; min_sample_time 50000; timer_rate 20000. :good:
[Samsung Galaxy Nexus] Kappa Lamda:
For me r292 just doesnt stick very well.

First my phone stuck at google logo after auto-flash! Removed battery, and then booted!

Secondly my battery life is worse tha m6 or r290...
[Samsung Galaxy Nexus] yellowdie:
That looks like it's gonna be a good middle ground. :) I think for performance, I'd push to 50k, 50, 40k, 20k (in your order listed). But 60k, 60, 50k, 20k will be a tad bit better for battery. :)

---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------

***

FACEPALM

***

I decided to flash back to stock and take a look around the pure kernel to see defaults and stuff.

T o t a l l y forgot that it wipes the SD card.......

*FACEPALM*

*FACEPALM*

*FACEPALM*

*FACEPALM*

*FACEPALM*

Luckily! I had just made a nandroid and said "Hey, I should copy it to my computer to keep it safe while I have it plugged in to do the stock flash." lol. So I can nandroid back just fine. But I just wiped everything else. lol. FAIL!
[Samsung Galaxy Nexus] Shadow-Nexus:
Hey Franco I've been experiencing major lag in 294

I have it set to 12xx max and 7xx min with interactive and 3xx max screen off

I experience the lags when I use a torrent client app
[Samsung Galaxy Nexus] CaspaTheGhost:
I'm running the performance setup but again keeping it real with 729/1305.

Flying.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nuwan32:
That's probably the apps fault for not being optimized.

Anyway.. gotta say 192 mhz at 675 mV is amazing :D
[Samsung Galaxy Nexus] Vangelis13:
What did you do, lock-unlock the bootloader..? :p At least, fresh clean phone now. ;)
[Samsung Galaxy Nexus] gaich:
I wouldn`t say "too hot", but it was hot... Maybe, this is the reason, but I am not sure, I remember the moments my phone was extremely hot,and it worked fine...
[Samsung Galaxy Nexus] osm0sis:
Yikes! What did you do?! :eek: All you needed was to flash the boot.img ... or basically anything BUT userdata.img or relocking the bootloader! :(

:laugh: Of course you are! Performance governor keeps it at the max 100% of the time! Your battery life will be hurting. ;)
[Samsung Galaxy Nexus] yellowdie:
Nope, didn't lock the bootloader. I used Mike's GNEX Toolkit 9.1 to flash the stock image. I didn't think it would be a full wipe like the bootloader clearing. Oh well. Like I said, I had just copied a nandroid to my computer (Praise God!!) so I'm back up and running now. lol. *whew* Nerve wrenching last hour. haha.
[Samsung Galaxy Nexus] Empty Hand:
I'm still on r290, debating waiting for r295 before flashing another nightly. What are you all liking in the meantime, 292 or the 294 test kernel?
[Samsung Galaxy Nexus] szale9001:
Correct me if I'm wrong, but I thought the above_hispeed_delay is how long your phone waits before jumping above the hispeed_freq, yes? You said it was how long it waits before it ramps up to the hispeed_freq.

Not trying to nitpick, but it is an important distinction and I just want to make sure I know what it is before I play with it.
[Samsung Galaxy Nexus] !crazy:
You have mentioned trickster in one of previous posts that's why I thought maybe you have more such apps. The easiest would probably be to reflash ROM and kernel, or to change the kernel for a while and recheck later..
[Samsung Galaxy Nexus] osm0sis:
Ouch buddy, the toolkit probably flashed userdata.img ... I hate toolkits. Get your fastboot on next time brother. :highfive:

I tried "50k, 50, 40k, 20k" but things still didn't seem quite as responsive as "60k, 60, 50k, 20k". Not sure why.

r294 over r292, that much I know, especially with the new balanced tunables we're working on.

As far as I know, yellowdie is correct. above_hispeed_delay is how long it waits once the load is above hispeed_load before jumping to hispeed_freq, the idea being maybe the lower freq can handle the load without needing the jump, so it's given time to try.
[Samsung Galaxy Nexus] franciscofranco:
"Wait this long before raising speed above hispeed, by default a single timer interval." I'd say anything between 30ms and 60ms would be a balanced choice. Default 100ms might be a little to much.