yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
Yeah... Fastboot would have been better... I was thinking "eh, this will be a quick flash and restore my nandroid, then done." Nope! lol

I haven't had a change to compare 5/5/4/2 to 6/6/5/2 yet. But I'll give it a whirl soon. :)

Actually, I think szale may be correct. This is the definition I've seen: "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load."

So in theory, it's hit hispeed, then wait X amount of time before being allowed to move up. So if we have go_hispeed_load at 50 (or 60), and the CPU bumps up to 90% usage, it's going to go to the hispeed_freq and sit there for awhile before increasing to your max clockspeed. So Google default is 100k, some of the stuff I've seen was recommending 20k. I think 20-40 will make more sense. If you get hit with a bunch of mutlitasking (or an intensive app), you don't want to stop at your hispeed_freq for that long. So, Os, try 3/6/5/2 and see how that feels. :)

EDIT: Yeah, what Boss Man said. :p

EDIT2: Is anyone else annoyed that it's "hispeed" instead of "highspeed?" I mean, come on, Google, get your grammar right! lol
[Samsung Galaxy Nexus] franciscofranco:
It basically depends a bit on the sampling rate. If the timer rate is 30ms setting go_above_delay to 60ms it goes through 2 samples, 90ms to 3 samples on and on. The more samples we give it the less it will change above hi_speed. I think setting it below the sample rate time its not ideal at all. I wouldn't bump hi_speed above 729Mhz as most times the device won't need to ramp above that. If we set it to 1036 it will use that step a lot more and it will use a more power hungry OPP, more voltage etc etc. This is very interesting to be honest, I think its the first time I've took some time to study some of its proprieties and its effects, so thanks for bringing it up guys, keep it coming!!!
[Samsung Galaxy Nexus] osm0sis:
Holy smokes! You got it under 700? Your silicon is strong man! :D Maybe 725mV was more mid-range than I thought!

Whoops my bad, good to know! Trying out 3/6/5/2 now. :)

Err maybe it should be 5/6/5/2 taking into account Franco's last post.
[Samsung Galaxy Nexus] franciscofranco:
I'm lost, whats 5/6/5/2 referring to? Just type out the names of the settings or it will confuse most users :D
[Samsung Galaxy Nexus] osm0sis:
Haha sorry, I guess we kind of evolved a shorthand in the last page.

50000/60/50000/20000 -> 50k/60/50k/20k -> 5/6/5/2

Basically we're just working our way down the dialog. ;)

Either way I still like the following:

above_hispeed_delay 60000

hispeed_load 60

min_sample_time 50000

timer_rate 20000

Lowering delay any more, even to 50k, seems to make things slower. Not sure why.

Also, I've had hispeed_freq at 1036 pretty much since switching to your kernel and I still pull 3h screen on and 24+h on battery, with a nice boost in responsiveness and lag reduction. 729 has always felt slow. This is all 384GPU of course. I know 512GPU smooths a lot but it runs hotter than I like..
[Samsung Galaxy Nexus] nemotheblue:
Didn't Franco just say that we should set above_hispeed as a multiple of timer_rate?

I've long been running 4/8/4/2, mostly for battery life, but it's been good for me
[Samsung Galaxy Nexus] osm0sis:
I didn't say it made sense, just that it still seems better :p

Edit: It should work, no? 60k is 20k x 3, unless I've completely lost it! :cyclops:

Edit 2: Lowering min_sample_rate below 50k also seems to slow things down from my above settings.
[Samsung Galaxy Nexus] franciscofranco:
It doesn't need to be a multiple or timer_rate, but for consistency (if I'm understanding correctly) it would be a good idea if its multiple.
[Samsung Galaxy Nexus] yellowdie:
I agree. Here's what I'm thinkin'. 6/6/6/2 (Leaning towards 4/5/6/2). Which is:

above_hispeed_delay 60000 (I'm leaning towards 40000)

hispeed_load 60 (I'm leaning towards 50)

min_sample_time 60000 (higher is better for performance here, lower better for battery. And 60k is Google default)

timer_rate 20000 (everyone agrees on this (I think), and this is the Google default)

Min 192

Max 1036 (or higher if you really want to)

input_boost_freq 729

hispeed_freq 729

So what that means is when I touch my screen, and when the CPU is at 60%, it'll be 729. When it jumps above 60%, it will wait (is that 6 seconds or .6 seconds?) before jumping to 1036 (or higher).
[Samsung Galaxy Nexus] franciscofranco:
I dont agree with time_rate and with input_boost_freq. I prefer the timer_rate to be the same as the cpu frequency transition latency which is 30ms. Input_boost_freq I think it should be higher than hispeed_freq. input boost will ramp to the selected frequency when it detects finger movement and thats independent of the load so we want more responsiveness. With hispeed_freq it will ramp to that selected frequency as an intermediate point before it decides if it needs to ramp to max or not depending on the load. Thats my opinion, doesnt mean its what it should be.
[Samsung Galaxy Nexus] yellowdie:
With go_hispeed_load (calling it GHL) at 50, and my hispeed at 729, I'm jumping up to 1036 a lot more than I would expect. So maybe setting GHL at 70 is gonna be better.
[Samsung Galaxy Nexus] franciscofranco:
Yaps, thats what I'm betting my money on. Already sent r295 to minooch and forced him to use my settings (including that 70 go hispeed load) so lets see what comes from this.
[Samsung Galaxy Nexus] yellowdie:
hhmmm... I thought input_freq should be lower than hispeed because you don't need crazy high when you first touch it, but you want it to boost when you start launching more programs.

To the testing grounds! :D

---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------

lol. Sounds good. :)

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

I'm gonna keep playing with it tonight, but I'm signing off to go spend time with my wife. :D
[Samsung Galaxy Nexus] franciscofranco:
input_boost_freq triggers when it detects finger movement and not when only touched, thats how google designed project butter.
[Samsung Galaxy Nexus] franciscofranco:
Thats really strange. I'll have a look later.
[Samsung Galaxy Nexus] esoomenona:
So I'm not sure if anyone else has encountered anything like this but I use Gentle Alarm, and it doesn't go off until I turn on the screen, even if that is after the time the alarm should sound. It seems like the clock doesn't update until I turn on the screen. This also occurs with the stock alarm.

I've tried enabling and disabling hotplug, and with interactive and conservative governors.
[Samsung Galaxy Nexus] TheXclusive814:
OP says anytime you reboot the phone, you should open and close the camera app due to a bug that drains the battery . Is this still an issue to watch for when rebooting?
[Samsung Galaxy Nexus] nic85:
Someone had reboot using browser? I just had two reboot while surfing the web.

#11 conservative 700-1200 foxhound 4.03
[Samsung Galaxy Nexus] franciscofranco:
You're the second user to report this. I'll look into it, it's probably a voltage thingy.
[Samsung Galaxy Nexus] sishgupta:
Ahh the issue is more complicated than I thought.

I have data but....no sms or phone?
[Samsung Galaxy Nexus] definator:
which baseband are you using?
[Samsung Galaxy Nexus] sishgupta:
XXKK6
[Samsung Galaxy Nexus] omid_freesky:
COULD YOU PLEASE ADD THE VERSION NUMBER TO THE NAME?

I know it's a lame request but trust me it's worth it.
[Samsung Galaxy Nexus] definator:
have u tried UGKL1 for your region? should be the one for you with latest bootloader
[Samsung Galaxy Nexus] sishgupta:
i haven't had an issue with xxkk6 until today and I've been running it for weeks. two drops now in 4 hours.

also the recommended radio for 4.0.3 is xxkk6 so i wasnt gonna use the NA radio until it was updated for 4.0.3 or higher
[Samsung Galaxy Nexus] aron7awol:
I got a reboot last night while I was out. The phone froze when I unlocked, screen was stuck on black, and then it rebooted a few seconds later. I am OCed so that could be the reason but this is the first reboot I've had and I've been OCed for a long time, and I've stressed the phone a lot while OCed.

Just something to make a note of I guess, and I'll see if it happens again. I didn't get a dmesg
[Samsung Galaxy Nexus] esoomenona:
So I rebooted my phone and my alarm started working again. Oh well. I just hope it doesn't decide to act up again tomorrow morning and make me late for work.
[Samsung Galaxy Nexus] 3c:
Why disable something that works well for many?

Sorry to be such a bother but here is the settings I use and they are damn stable for me! Yes 200mV less than your kernel's defaults! :D
[Samsung Galaxy Nexus] sishgupta:
Stable for you is not necessarily stable for everyone. As you may know, not all chips are identical, some can be pushed higher freq/lower voltage than others.

AFAIK Franco's goal is stability for everyone.
[Samsung Galaxy Nexus] Thracks:
I can't seem to get hotplug enabled. Every time I echo 1 to the new hotplug_enabled file, it still reports as 0 when I check the file manually.

I've even tried creating an init.d script (named 99hotplug) containing the following. I also chmod'ed both files to 777, just in case. Still no luck.

//edit:

Fixed it with a double >> in the script.
[Samsung Galaxy Nexus] esoomenona:
I think you only need one >

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

Maybe that's your problem?

edit: and the 1 comes before the > not after.
[Samsung Galaxy Nexus] Thracks:
Just a typo. Woops! I'll fix it.
[Samsung Galaxy Nexus] dpaine88:
I know in the app it says we don't have to wipe anything, is that just going from nightly to nightly? Or do we not have to wipe cache/dalvik even if coming from a different kernel.
[Samsung Galaxy Nexus] Thracks:
Crisis averted. Fixed the script by doubling up the angle bracket ("echo 1 >> /...").
[Samsung Galaxy Nexus] sruel3216:
I usually set

His speed_freq 1228

Input_boost 1228

Very smooth and make an full charge and 2.5 hours of screen on time. Maybe over kill but I like smooth :)
[Samsung Galaxy Nexus] yellowdie:
Yeah, but I didn't think it needed to run at 1036 or higher when you touch it. I'm curious now. :)

I've been using Cool Tools for a few weeks (https://play.google.com/store/apps/details?id=ds.cpuoverlay) to see my active clockspeed and load. But does anyone know a good app to

track and graph

CPU clockspeeds? That would be really interesting to see. :)
[Samsung Galaxy Nexus] osm0sis:
Okay given these, and yellowdie reminding that a higher sample_time is better, I'm running 60k/60/60k/30k now (can't lower delay anymore due to the multiple rule) and you're right, things seem smoother! :D

Edit: ... but keeps starting to lag randomly, so I'm back to 6/6/5/2 again. Can't seem to do much better than this at 192min.
[Samsung Galaxy Nexus] Paragon_X:
I am coming from jellybelly and this kernel 290. Now I'm on AOKP B5 the lastest along with kernel 290. However my wifi has authentication problem? I'm unsure if it's a kernel issue because it worked fine with jellybelly but thought I ask regardless.

Edit: I've gone back to Milestone 6 and it seems Wifi connects. But once again with the nightly, specifically 290 and 292 wifi has authentication problems. I am on AOKP B5, any suggestions?
[Samsung Galaxy Nexus] LibertyMonger:
Hey Franco, I run every kernel you put up for us from your app it is great and thanks bud. I don't know much and not sure if you care to hear or if it's any help to ya but I just happened to notice on the r292 seems to be an issue with wifi, playing videos on youtube freeze up. Back to Milestone 6 and it is smooth again. Not complaining, very happy just thought i would throw out my 2 cents lol. I am not very educated in any of the technical stuff I can only point out any basic stuff I can see HaHa. Thanks again bud Been loving every release it just keeps getting better!
[Samsung Galaxy Nexus] yellowdie:
So you keep bringing the sample down from 6 to 5. I'm thinking we should push the min_samle_time down to 3 (30000). Here's the definition: "min_sample_time - The minimum amount of time to spend at a frequency before we can ramp down."

Stock is 60k. Lower is better for battery because it allows it to leave the higher speeds sooner. Well, if we're pushing it up to 729 or 1036 whenever you touch it or it gets under load, then when you aren't touching it, I think letting it lower itself sooner will help with the battery side of things. Everything else has been about pushing for higher performance, but I think that's a great place to grab a little extra battery life. Thoughts? How about trying 6/7/3/3? :)
[Samsung Galaxy Nexus] osm0sis:
Feels pretty good, but weirdly enough 6/6/5/2 still feels smoother. timer_rate just does not seem to be working well for me at 30k. Played with that idea a bit though.. try 6/6/3/2. Feels faster! 20k all the way. :)

Edit: Ahhaha and I still come back to 6/6/5/2. Makes it feel fast and reasonably smooth, considering it's min 192MHz. :good:
[Samsung Galaxy Nexus] yellowdie:
Been testing 6/7/3/3 for about an hour and I really like it! As a side note, I am still running 192-729! Obviously I will bump up my max from 729 soon, but it is crazy that this kernel is smooth enough that I can run at a max clockspeed of 729 and be totally fine! Lol. I did a lot of flashing and rebooting today, so I couldn't see a good battery comparison, but hopefully tomorrow I will see how it is doing. :D
[Samsung Galaxy Nexus] Shadow-Nexus:
Dude I though this kernel was fast before but now that I switched to paranoid android

ITS BLAZING FAST!!!
[Samsung Galaxy Nexus] yellowdie:
I'll try the timer_rate at 20k again. But Franco seemed to really like go_hispeed_load at 70. So lets try 6/7/3/

2

vs 6/7/3/

3

. You feel

2

0k is better, Franco thinks

3

0k will be better. I'm not sure which. lol

---------- Post added at 10:47 PM ---------- Previous post was at 10:46 PM ----------

Which of those is your "haha" number? Is it the 5 that you don't like being at a 3? Or the 2 that you don't like being at a 3? lol. So many variables!
[Samsung Galaxy Nexus] franciscofranco:
I'm pretty sure I'll ship r295 with go_hispeed_delay: 60ms, go_hispeed_load: 70, min_sampling_rate: 60ms, timer_rate: 30ms. I have nearly 50% spent on lowest freq, then almost perfect 10% on each of the upper ones and 6% on max, 0 lag etc etc.
[Samsung Galaxy Nexus] yellowdie:
Hey Franco, I know you've said in the past that BoostPulse is controlled by PowerHAL (Look guys! I know how to use the SEARCH tool!), but how does that relate to what we're testing and looking into right now? Is that a tweakable variable that we should investigate or is it just an on/off style thing?

The description I found was: "boostpulse: Immediately boost speed of all CPUs to hispeed_freq for min_sample_time, after which speeds are allowed to drop below hispeed_freq according to load as usual." (From here: http://goo.gl/ZmzhN) :)

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

That's pretty much exactly what I'm thinking as well. The only variable I'm playing with is whether or not min_sample_rate at 30 would save extra battery over 60. I think 60 is a little faster, so I'm inclined to say screw battery, but I'm interested to see the difference. :D
[Samsung Galaxy Nexus] franciscofranco:
boostpulse is goes on/off depending on what the HAL thinks best so thats not up to us. By default it goes to hispeed_freq, but I changed it to ramp to input_boost_freq and let the governor work just use hispeed_freq for its normal governor-like behavior.

I'll test 30ms on min_sampling_time.
[Samsung Galaxy Nexus] joeyfong:
@franco, pls update the app at AndroidPIT too, thanks.
[Samsung Galaxy Nexus] yellowdie:
Cool. Good to know. So will r295 have input_boost_freq at 1036 and hispeed_freq at 729? Also, did you lower the voltages at all?

I'm running:

192MHz at 750mV

384MHz at 1000mV

729MHz at 1100mV

1036MHz at 1200mV

Also, since we're looking at tweaks for a new build, my init.d script includes these as well. What are your thought?

echo "90" > /proc/sys/vm/dirty_ratio;

echo "70" > /proc/sys/vm/dirty_background_ratio

echo "4096" > /proc/sys/vm/min_free_kbytes;

:) :D
[Samsung Galaxy Nexus] franciscofranco:
Pushed it few hours ago.

input_boost_freq and hispeed_freq are with those values for a long time already. Neps, I don't mess with my voltages, Smartreflex is enough for me.
[Samsung Galaxy Nexus] yellowdie:
Okay cool, then I'll scratch my undervolts. I trust you and I trust SR. :D
[Samsung Galaxy Nexus] franciscofranco:
Thats a whole new monster...I'll answer it tomorrow, 4am can't think clearly, super tired. Good night!!
[Samsung Galaxy Nexus] franciscofranco:
Better let SR calibrate everything. If you want less voltage on 192Mhz you might be able to lower it for a good punch, but let it calibrate the others. You said you were using 1000mV on 384Mhz but SR calibrates that step with 840mV lol.
[Samsung Galaxy Nexus] yellowdie:
lol. It's only 11pm here, but I'm heading to bed as well. See ya' tomorrow.

---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------

Well I still have SR on and running. But I guess you're right, my UVs for those were kinda pointless when I think about it. lol. 192 would be the only one I see as beneficial.
[Samsung Galaxy Nexus] osm0sis:
Both really. 50k for min_sampling_time doesn't like being lower, and also feels marginally better than 60k for some reason. And I know it makes sense to have the timer_rate match the latency at 30k, but that also still feels markedly faster when down at 20k.

Please give 50k a shot while you're at it. Could be a decent compromise and honestly feels faster to me as I said above. Thanks. :)

Also, if you're going to leave it in SR, 192Mhz is kind of a pointless step to include. :( Since I don't think anyone will want to run it when they can run 384 at the same voltage...
[Samsung Galaxy Nexus] franciscofranco:
I'll try to dream about it and do some testing while I'm sleeping - that will save me some time back in "real world".
[Samsung Galaxy Nexus] yellowdie:
Honestly, to me I didn't feel much of a difference between 30-50k on that one, so I'd be fine with it at 50 as well. Franco was leaning towards 60, and is now trying 30, so let's see his response on that and probably settle in the middle ground there somewhere. :)

GAH. Why am I still up? Freakin' Android... lol
[Samsung Galaxy Nexus] osm0sis:
Haha, if anyone can do it you can Franco. :laugh: :D

Edit: Also please dream about my added note above re: 192. ;)
[Samsung Galaxy Nexus] yellowdie:
You hear that, Os?! Franco's gonna dream about us! :laugh: lol :angel: Sleep well, Boss Man.
[Samsung Galaxy Nexus] osm0sis:
Poor guy. :laugh:
[Samsung Galaxy Nexus] gaich:
Tried 294 in benchmarks

1305-729,interactive, 729 screen off, SR off, undervolting
[Samsung Galaxy Nexus] garuhhh:
min_sample_time and timer_rate (?)

when setting the input_boost_freq and hispeed_freq, should they be in the actual frequencies (e.g. 1036800 and 729600) or can I just use 1000000 and 700000?

in my observation, setting the go_hi_speed_load to 70 to 80 doesn't make much difference with 60, and keeping this value as high as possible is good for battery life, as the frequencies will be kept as low as possible, and they'll be boosted up (up to the set hispeed_freq) if this go_hi_speed_load mark is reached.

Using the default delays and timers with r290 gave me lots of lags. setting above_hispeed_delay, min_sample_time, and timer_rate to 20k solved the lag for me, while giving approximately 4 hrs of screen time. but franco suggested a 30k value for timer_rate (?).

Can anyone explain what these timers are? why did franco suggested 30k?

I'm aware as what above_hispeed_delay is (amount of time to wait before deciding to bring up/down the frequency after reaching the set hispeed_freq --> this means it needs to be low in order to save battery and improve performance, especially if hispeed_freq is not the maximum frequency), Does anybody have idea what are the other two?
[Samsung Galaxy Nexus] yellowdie:
Check out this link: http://xdaforums.com/showthread.php?t=1369817 for info on the timers. Scroll down to the '5. Interactive' section.

And, yes, the freqs should be the exact 729600 or 1036800 etc values. :)
[Samsung Galaxy Nexus] nuwan32:
The frequency selector is a list, so it's impossible to choose anything else since its given values, unless your using a old bootleg version of the app
[Samsung Galaxy Nexus] sunra0815:
Please can anybody give me a hint how I can improve the touchscreen sensitivity.

On my SGS I had an option in the kernel app for this.

Compared to my SGS the touchscreen feels like a restrictive one ;)
[Samsung Galaxy Nexus] garuhhh:
Oh sorry, I use setCPU, don't have the francoKernelUpdater app.
[Samsung Galaxy Nexus] Ridho1:
Is posibble for you to give a powermode widget in your app?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leets4uc3:
I think its on the to do list.
[Samsung Galaxy Nexus] garuhhh:
I got these from that thread:

so it makes much sense, to make the min_sample_time as low as possible (?), but how low? what's the most appropriate sample time for battery and performance?

for the timer_rate, franco suggested 30k to consider the CPUs latency. What has it to do with the cpu's latency?

he also said min_sample_time doesn't have to be in multiple of timer_rate.

in my case, all my timers are in 20k, which works fine as of now. But i must be missing some things, because I just saw somebody post these values, and no detailed explanation for having them.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just woken up and feel like my head is going to explode already this last 5 pages is crazy

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
It seems to me your post managed to stop this...:D:D:D
[Samsung Galaxy Nexus] chickentuna:
nah, they're probably sleeping and taking a good rest right now lol. Srsly the last 3-5 pages is mind blowing, haven't got any clue of what they're talking about
[Samsung Galaxy Nexus] tjackbjorn:
Like a baws!

Sent from my super fast Prime filled with beans.