Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,730,261 Members 52,338 Now Online
XDA Developers Android and Mobile Development Forum

[KERNEL] [GPL] [GN] franco.Kernel r396

Tip us?
 
sunra0815
Old
#30441  
Senior Member
Thanks Meter 64
Posts: 184
Join Date: Nov 2010
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
 
garuhhh
Old
#30442  
Senior Member
Thanks Meter 15
Posts: 119
Join Date: Jul 2010

 
DONATE TO ME
Quote:
Originally Posted by nuwan32 View Post
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

Sent from my Galaxy Nexus using XDA Premium HD app
Oh sorry, I use setCPU, don't have the francoKernelUpdater app.
 
Ridho1
Old
#30443  
Ridho1's Avatar
Senior Member
Thanks Meter 153
Posts: 375
Join Date: Dec 2011
Location: Suroboyo cok!
Is posibble for you to give a powermode widget in your app?

Sent from my Galaxy Nexus
 
leets4uc3
Old
#30444  
leets4uc3's Avatar
Senior Member
Thanks Meter 234
Posts: 889
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by Ridho1 View Post
Is posibble for you to give a powermode widget in your app?

Sent from my Galaxy Nexus
I think its on the to do list.

Sent from my Galaxy Nexus using xda premium
DO YOU LIKE ELECTRO, DUBSTEP, HIP-HOP, HOUSE, ETC?
High in protein and bass

 
garuhhh
Old
#30445  
Senior Member
Thanks Meter 15
Posts: 119
Join Date: Jul 2010

 
DONATE TO ME
I got these from that thread:
Quote:
iii) min_sample_time - The minimum amount of time to spend at a frequency before we can ramp down. (Sounds like Lazy governor?!)
iv) timer_rate - The sample rate of the timer used to increase frequency.
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.
 
The Gingerbread Man
Old
#30446  
The Gingerbread Man's Avatar
Recognized Contributor
Thanks Meter 3815
Posts: 7,947
Join Date: Sep 2010
Location: Gloucester
Just woken up and feel like my head is going to explode already this last 5 pages is crazy

Sent from my Galaxy Nexus
The Following 9 Users Say Thank You to The Gingerbread Man For This Useful Post: [ Click to Expand ]
 
gaich
Old
#30447  
gaich's Avatar
Senior Member
Thanks Meter 532
Posts: 789
Join Date: Mar 2012
Location: Chitago
Quote:
Originally Posted by The Gingerbread Man View Post
Just woken up and feel like my head is going to explode already this last 5 pages is crazy

Sent from my Galaxy Nexus
It seems to me your post managed to stop this...
MAGURO [ROM] AOKP (kitkat 4.4.4)-17.07.14 [KERNEL] Franco r396 [RADIO] tDVMK1 [RECOVERY] TWRP 2.7.1.0 Holofied [BL] PRIMEMD04 [LAUNCHER] Nova Prime [FRAMEWORK] Xposed [CUSTOMIZATION] GravityBox KK
For those appreciating my translations - you cannot use donations in Russian PayPal account, but if you want to thank me this way, you can send them as payments for goods and services to PayPal address gaich@live.ru.
The Following User Says Thank You to gaich For This Useful Post: [ Click to Expand ]
 
chickentuna
Old
#30448  
Senior Member
Thanks Meter 405
Posts: 1,113
Join Date: Feb 2012
Quote:
Originally Posted by gaich View Post
It seems to me your post managed to stop this...
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
The Following 2 Users Say Thank You to chickentuna For This Useful Post: [ Click to Expand ]
 
tjackbjorn
Old
#30449  
tjackbjorn's Avatar
Senior Member
Thanks Meter 254
Posts: 1,067
Join Date: Jan 2012
Location: Falun
Like a baws!



Sent from my super fast Prime filled with beans.
Nexus 5
ROM: All of them!
Kernel: What ever fits my needs.
Recovery: TWRP


If you think about how stupid a human is, on average. Consider then, that half of them is even more stupid.
 
yellowdie
Old
#30450  
yellowdie's Avatar
Senior Member
Thanks Meter 1288
Posts: 1,157
Join Date: May 2011
Location: Orlando, FL
Quote:
Originally Posted by The Gingerbread Man View Post
Just woken up and feel like my head is going to explode already this last 5 pages is crazy
haha. It's been a crazy two days. But it's been a blast.

Now, sleep is over, time to get back to work!

Quote:
Originally Posted by garuhhh View Post
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.
Yes and no. Here's what we're thinkin' so far.

THIS POST WILL BE A RECAP OF THE LAST FEW PAGES OF RESEARCH!

This was my original settings that I've been using for weeks:
Quote:
above_hispeed_delay: 20000
go_hispeed_load: 50
min_sample_time: 40000
timer_rate: 20000
So to make the short hand easier, we kept it in that order and just said: 20000/50/40000/20000 became 20k/50/40k/20k became 2/5/4/2. Make sense?

Here is a breakdown of what they each mean:
Quote:
-above_hispeed_delay: Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load.
-go_hispeed_load: The CPU load at which to ramp to the intermediate "hi speed".
-min_sample_time: The minimum amount of time to spend at a frequency before we can ramp down.
-timer_rate: Sample rate for reevaluating cpu load when the system is not idle.
This is a good explanation that I wrote back on page 3038:
Quote:
-above_hispeed_delay: higher = better battery, lower = better performance. (100k is default)
-go_hispeed_load:.......higher = better battery, lower = better performance. (50 is default)
-min_sample_time:......lower = better battery, higher = better performance. (60k is default)
-timer_rate:.................higher = better battery, lower = better performance. (20k is default)
So Google's default is 10/5/6/2. Lower numbers are all better for performance except min_sample_time (there higher is faster). So our goal is to find a sweet spot.

The default 10 is for "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load." So we think 10 is too high, but if you go too low, then you'll be using the higher freqs a lot more than you need and it will hurt the battery. So we are leaning towards 6 (60000) for above_hispeed_delay.

The default 5 is for "when the CPU hits X% amount of load, then jump to the hispeed_freq." Again if this one is too low then it will cause the higher freqs to be used more often then they need, so we actually turn go_hispeed_load up a little bit to 7 (70).

The default 6 is for "how long do I wait before lowering the clock speed from what it's currently at." So the lower we put this, the better battery will be. We're still trying to decide between 3 (30000) and 5 (50000). Osm0sis is getting more lag at lower levels, and finds the best performance mark at 5. So we turn min_sample_time down a little from stock to help with the battery.

The default 2 is for "wait this long before changing the clockspeeds from what it's at now." While technically 2 sounds better because it's changing more often, Franco believes that by setting the timer_rate to be the same thing as the CPU sample_rate (which is preset at 30000), then that will make the CPU more efficient at switching. So we increased it from 2 (20000) to 3 (30000).

So TO RECAP: Using the stuff from above, Google's defaults for these settings are 10/5/6/2 and we are changing them to 6/7/3/3 or 6/7/5/3 (again, still testing that third number for the min_sample_time).

Does that make sense for everyone interested in following along? Any questions? Feel free to try out these settings yourself (the easiest way is with Franco's app or something like Trickster). We want as much feedback as possible on this.
The next kernel release will have the totally tweaked settings for everyone to test without having to change their own stuff.


The Following 162 Users Say Thank You to yellowdie For This Useful Post: [ Click to Expand ]
Tags
4.0.4, 4.1, 4.2, best kernel, best support, fast, franco, galaxy, jb 4.1, kernel, nexus, samsung
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes