yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] deltatux:
I did 1188 MHz and 95 on go_hispeed_load, seems to work even better. Thanks for the go_hispeed_load suggestion. I upped the timer_rate back to 15000, seems to have largely solved the problem. Still testing.

Stop teasing us and release it already :P

deltatux
[Nexus 4 Original Android Development] franciscofranco:
Careful with timer_rate, too low and will cripple your battery.
[Nexus 4 Original Android Development] deltatux:
So I've read, that's why I've been tweaking the timer_rate to balance it, I might raise it to 17000 to balance it out.

Cheers,

deltatux
[Nexus 4 Original Android Development] Gugus38:
Why don't you guys play with go above hipseed? The idea seems good, I tried but didn't get any results.

Also I don't understand the concept of putting higher medium than low, isn't there conflict? If the load is between 25 (medium) and 40 (low) what are the cores doing?

Sent from my Nexus 4
[Nexus 4 Original Android Development] mjehan:
Are you also testing them with the other tweaks the user suggested like:

Governor Control > timer_rate: 25000, min_sample_time: 50000
[Nexus 4 Original Android Development] franciscofranco:
If the load is above 25% it onlines one core, restarts the monitor, if the load is above 25% it onlines another core, restarts the monitor, if the load is below 50% it passes the first_level check, it passes the second_level check and goes to the third_level check and offlines all cores.
[Nexus 4 Original Android Development] thebryceee:
My phone is noticeably cooler with these settings as well
[Nexus 4 Original Android Development] yokuyuki:
I think BBS just reads the log. It shouldn't consume any battery in the background.

Actually it wouldn't be very hard. Don't take any calls and just disable cellular signal since neither of those are affected by kernel anyways. You can probably just leave it on airplane mode since the kernel shouldn't affect the battery use of wifi either and just run load tests to see how the kernel is responding to idle drain and hotplugging.

You don't need to replicate usage to do battery tests for kernels because the kernel only impacts certain activities. Anything else would vary from user to user.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Yeah not sure what people are talking about. I think people see the toast notification and freak out. But in reality when you look at battery statistics on Android for BBS, it sits at the bottom. I'm guessing if BBS were to use battery, it's like 1% tops throughout the day.

So a video test would work well here.
[Nexus 4 Original Android Development] Nocturnal86:
Pardong my ignorance but is there somewhere or can someone explain the Governor Control? Like what does each setting do? The "above_hispeed_delay" "boost" "go_hispeed_load" etc...? I would love to understand so i can better learn to tweak the app and understand what you guys are talking about when you guys discuss them. Thanks for any help!
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Well you can try your best by testing at the same point in the house. Yes you might get extra emails or something, but honestly, we can't control perfectly right? Those small variances that exist in an experiment like this are negligible. It's 100x better than some user saying today I got better battery life than yesterday in standard use. That's by far the most uncontrolled experiment ever, and at least running the same test day to day would be much better.

This is exactly why I feel like daily use shouldn't be a real measure of battery.

The other day I had 98% wakelock for the wireless charger, but I got my average ~5%/hour discharge. I didn't even notice my battery life really changing much. More importantly, I wouldn't have known about the wakelock if I didn't look for it. So yeah, I do frequently point at the placebo effect when people try to treat their observations as a fact, and especially when observations are so full of bias.

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

Franco, I was reading something in the HTC One review by Anandtech and they mentioned the use of network batch operations.

I think 3G use on the Nexus 4 is very draining in battery life. Would this be something controlled by the kernel? Or is this something totally separate? I've been doing a deep dive into improving battery life, and it seems there's a significant gap between the Nexus phones and other flagship phones. Perhaps this is the missing key?
[Nexus 4 Original Android Development] hospital349:
I've been testing these for the last 20 minutes. Performance seems to be a little more sluggish, (though I'm not using a new kernel like you are). I know you're looking for a way to counteract the 25 second and 50 third predicament, as am I. I'm going through the motions and really think that setting input_boost to 0 is the cause of the performance drop. Obviously, you have access to back-end tweaks in the Kernel and really hope you can find a solution, so that the combination doesn't upset battery life.

That being said; I can still vouch for battery life being fantastic with the original Hotplug values that I posted, combined with timer_rate @ 25000 and min_sample_time @ 50000 as well. (Again, these were part of my original settings).

When I mentioned that the Kernel feels on par with Trinity performance, I wasn''t kidding. I have always respected your work and all though performance throughout your releases hasn't always been consistent, I have always returned here because you create a little bit of everything that I need from a kernel, rolled into one. Now that I have these settings on my device (with input_boost: 1), I personally feel that franco.Kernel is on par, or possibly ahead of the game in regards to performance. I can easily stay on these (or similar settings) for the unforeseeable future. :good:
[Nexus 4 Original Android Development] wizshaw:
Try changing your governor.. One step up from what it was. Seemed to clear mine nicely. Adds just a bit of extra juice.
[Nexus 4 Original Android Development] inculto:
is anyone seeing improvements in using fast charge in trickster mod? cause im using it and i cant really see my battery to charge faster!

thanks
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
fast charge works only if your computer supports it... it basically draws up to the max the phone supports which is 950 mA (correct me if I'm wrong). Otherwise you're drawing 500mA which is for a slow charge.
[Nexus 4 Original Android Development] mrfantastic:
saving color profiles

Is anyone having trouble saving color profiles? Im on xylon latest nightly(stock kernel that came with it) tried to save the color profile on it and the updater app fcs
[Nexus 4 Original Android Development] franciscofranco:
What is your kernel and app version?
[Nexus 4 Original Android Development] Arstoien:
The app force closes if I'm on Conservative governor and click Governor Control.

I wanted to play around with Conservative but...
[Nexus 4 Original Android Development] resynx:
Exit from the app and reenter. Now try getting into governor control.
[Nexus 4 Original Android Development] drawde40599:
I don't use it but confirmed it fc me 2

---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------

Funny that works
[Nexus 4 Original Android Development] franciscofranco:
Its because sometimes after choosing a governor the governor files are not yet ready and set in the kernel sysfs and the app tries to read from them and they are not there. Just choose the governor and wait 2 seconds before entering governor control. I tried to fix that before but wasn't very successful. I need to treat the error more gracefully I guess.
[Nexus 4 Original Android Development] resynx:
Just wondering, had a random reboot and there is no last_kmsg for me to pull. Does that happen sometime to others? Having no lkast_msg upon boot?
[Nexus 4 Original Android Development] santeana:
I just used the same settings except changed the load from 25 to 30. seems to keep to the one core for the most part and I haven't noticed a difference in the performance at all.
[Nexus 4 Original Android Development] Isham.padron:
Franco,

I'm on 119 with the most update app and I see its not onlining my other cores. Pretty bad lag all around. I did a photosphere and I could is the single core running at 100 with no help from the others.
[Nexus 4 Original Android Development] franciscofranco:
r120:

* Cleanup of the Hotplug driver code. Functionality is the same though

* Adjust the load thresholds of the Hotplug driver, should eliminate some micro stutters

* Fix the latest thermal throttling step bug where it wasn't being applied correctly

Lets hope I don't have to release a new one soon, have other stuff to do as well ;)
[Nexus 4 Original Android Development] yoft1:
OMG battery life on r120 sucks!!!!

:)
[Nexus 4 Original Android Development] pyr0sphere:
Were there any changes to the default settings to match what you run? You had posted some settings earlier in the thread
[Nexus 4 Original Android Development] franciscofranco:
Nope, gave me 1 week of battery life, sorry.:angel:
[Nexus 4 Original Android Development] itshotinhere:
I get the humor, but will the average noob? :confused:
[Nexus 4 Original Android Development] franciscofranco:
Nothing changed besides the thresholds for onlining/offlining cores, governor settings are the same.
[Nexus 4 Original Android Development] thebryceee:
Is it the settings you mentioned with medium load at 25 and low load at 50
[Nexus 4 Original Android Development] leader288:
Sike!

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Luigiesin:
Franco, don't know if you responded to this before, but how can you save all the interactive, governor, freqs settings as a profile in your app?

I think I'm ready to use r120 after using r111 all this time... But don't want to screen cap all my settings if I want to go back.. Thanks!

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar07)

Kernel: Franco M1/r111

T-Mobile
[Nexus 4 Original Android Development] BrandoHD:
We will soon see

Sent from neXus 4 using Tapatalk 2
[Nexus 4 Original Android Development] Pheno.menon:
I had about 3 SOD total using 118 and 119. Hopefully it's fixed in 120

Sent from my Nexus 4
[Nexus 4 Original Android Development] simorangkir_dcs:
This thread is the best place to learn, I think :D
[Nexus 4 Original Android Development] SleemLDJ:
Can someone please post what the new default values of the hot plug thresholds for R120 are?

Thanks.
[Nexus 4 Original Android Development] pdiddyfan:
Can you post a screenie of your settings? I'm trying to follow your posts and others and write down different settings to try. It'd be nice if we could save the whole hotplug profile in the app and reload each reboot...

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
When the governor is changed the app can block sleep 1 sec, check whether the files exist, if not go back to sleep 1 sec, check again, etc. repeat 4-5 times and bail and show error if they don't show up as to not wait forever if something went horribly wrong. I think the users would be fine waiting 1-2 sec.
[Nexus 4 Original Android Development] drawde40599:
90 50 30. U can just reset the app.....
[Nexus 4 Original Android Development] sirxdroid:
Can governor selection and governor settings be set via sysfs to use an init.d script? Is there any documentation please what all kernel settings can be set via sysfs? thanks!

---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------

+1 Saving a complete profile rather than just the color profiles would be very nice. Not sure if it's possible to control the governors via sysfs. If it is, I would go for an init.d script.
[Nexus 4 Original Android Development] Luigiesin:
+1... It would be great actually! Saving ALL the settings with one click... Even if the colors are not included but definitely the governor settings, hotplug and such.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar07)

Kernel: Franco M1/r111

T-Mobile
[Nexus 4 Original Android Development] Nocturnal86:
(Im sure this question got lost but i would like some help) Is there somewhere or can someone explain the Governor Control? Like what does each setting do? The "above_hispeed_delay" "boost" "go_hispeed_load" etc...? I would love to understand so i can better learn to tweak the app and understand what you guys are talking about when you guys discuss them. Thanks for any help!
[Nexus 4 Original Android Development] thebryceee:
I'd like to know too
[Nexus 4 Original Android Development] yethz:
@franco:

Hey bro 1st of all. Great job on your kernel.

And the app also makes things easier.

I just want to ask, is touch sensitivity also implemented in your M1 or nightly releases? (The E015 Touch driver what i mean)

Thanks for keeping your work on...

=[ Nexus 4 is all that I need ]=
[Nexus 4 Original Android Development] mitchdickson:
If you search the thread, you would find that the driver is not and will never be in then kernel.

Sent from my iPad 4
[Nexus 4 Original Android Development] MrDarkKV:
WOW r120 is amazing, first time since the r90's where I can say there is truly 0 micro lags and lag in general, great work Franco, keep it up!
[Nexus 4 Original Android Development] scream4cheese:
http://xdaforums.com/showthread.php?t=1369817

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

http://layer8problem.wordpress.com/2012/10/01/interactive-governor-settings/

I tried.
[Nexus 4 Original Android Development] ManOnTheMoon:
Your welcome.

http://droid-hive.com/index.php?/topic/610-rom-killrom-felonyone-aosp-421-mako/
[Nexus 4 Original Android Development] Ballastatuz:
If I unroot my phone will this kernel still work.
[Nexus 4 Original Android Development] drawde40599:
Y would u unroot ? I've never unrooted seems crazy to me ,but it should still be installed if u did , depending on how u unroot

---------- Post added at 12:08 AM ---------- Previous post was at 12:01 AM ----------

Funny ! I don't think these guys realize " this is what u do " if everyone would just install and use there phone , get rid of all these foncy apps that do nothing but casue mental issues , they would love this kernel alot more .

Had no issues Franco at all with 17 , worked better than flawless , great battery love the speed , 18 same results so far and seems faster overall ?

Great work !!!
[Nexus 4 Original Android Development] SleemLDJ:
Thanks for the new update Franco.

Has anyone noticed that when the updater auto flashes a new version of the kernel and restarts the phone, the network bars are greyed out

Until another manual reboot is done.

I'm running this on CM10.1
[Nexus 4 Original Android Development] catlog:
Hey there. I'm not sure if it's to do with the kernel but since I went to r18, screen no longer appears in Battery. I've restarted multiple times to no success. I would really appreciate if someone can help me.
[Nexus 4 Original Android Development] danielvc:
it popped up, just need to use the screen more :)
[Nexus 4 Original Android Development] franciscofranco:
Its working fine...
[Nexus 4 Original Android Development] catlog:
Hmm... Weird as I've had the screen on for around half an hour more and nothing's turning up. Anyways, I'll stop clogging this thread up with my complaining for now.
[Nexus 4 Original Android Development] zimphishmonger:
Franco, was wondering your opinion about a slight gpu of or the ability to control via the app. Any plans to add or will you leave the gpu alone?

Sent from my Nexus 7
[Nexus 4 Original Android Development] afbengochea:
Do a Google search. It's actually on a different forum but it should pop up right away in a search
[Nexus 4 Original Android Development] catlog:
Follow up: its finally shown up now. Took a while. I'll stop clogging the thread now.

My advice to those with the problem is to give it a few hours.
[Nexus 4 Original Android Development] immunityx:
What ROM do you run Franco?
[Nexus 4 Original Android Development] cchant:
he was running stock not too long ago
[Nexus 4 Original Android Development] Mancubus99:
I just installed r18 and notice lag on touch response as well as jerkiness during scrolling lists like G+ and Facebook. As a result I've reverted back to the CM default kernel. The lag and jerkiness is now gone.
[Nexus 4 Original Android Development] estallings15:
I'm having a lot of jerkiness while scrolling, as well.

R18
[Nexus 4 Original Android Development] 0.0:
Dang it. I was going to try it. I will have to wait for an update

Sent from my Nexus 4
[Nexus 4 Original Android Development] syncopy:
MinCo!
[Nexus 4 Original Android Development] cchant:
Didn't know minco was out?
[Nexus 4 Original Android Development] d0nnie:
Maybe a stupid question but...Where can you find/download the CM default kernel?
[Nexus 4 Original Android Development] mosd:


Installed the latest one and sometimes my lock screen not reacting! Have to turn off screen and then activate it again, and battery is not good
[Nexus 4 Original Android Development] yethz:
Sorry but i dont have enough time to search, thousands of pages already :cool:

And thank u for ur reply. I wondered what would be the issues arises when using the old E015 touch driver... just curious...

Coz Im using the init.d ways to revert back the touch drivers, but it lags almost a minute or more at reboot when Im using franco's kernel, other kernels does too but just 10secs to 20 or even less..

=[ Nexus 4 is all that I need ]=
[Nexus 4 Original Android Development] walkingmike:
I've noticed it's really smooth though I can't say if there are zero lags. Not that I've experienced lags but I just haven't used 120 long enough.

I'm just surprised that Franco been releasing all these nightlies so fast I can barely keep up!
[Nexus 4 Original Android Development] Mercado_Negro:
Has someone experienced auto reboots (two or three times in a row in some cases)? I've been experiencing this with the two latest versions. I'll try to get a logcat via adb (if someone has a better idea please let me know) but first I have to read about it because this would be the first time I need to do this via adb.

It only happens after a manual reboot, the phone reboots itself two or three times in a row and I've noticed it happens when the application is changing colors right after each reboot. Maybe it's a bug in Superuser because I don't see a root access notification before the application tries to change colors (or maybe I'm not considering how this is handled after a reboot).

Cheers
[Nexus 4 Original Android Development] jmudrick:
Are you running another init d? I have more like 20 seconds (stock ROM)
[Nexus 4 Original Android Development] JNewms:
I've never experienced that

Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
[Nexus 4 Original Android Development] drawde40599:
Nope work's fine here doing same thing u r, im using Koush's superuser built into AOKP, april 6th build try remove permissions clear app, reboot and try agn
[Nexus 4 Original Android Development] abjexstallion:
Too much UV perhaps?

Sent from this MAKO!!! SwEeEeT!!!
[Nexus 4 Original Android Development] shilent:
I am experiencing this. It only happens when I manually reboot. I can recreate this by manually rebooting, wait for the lockscreen, wait for screen to turn off, then pressing the power button reboots the phone. If I unlock my phone before the screen turns off, it does not happen.

Running AOKP build 6
[Nexus 4 Original Android Development] gianton:
No such problem both with r119 and r120, running CM-10.1 nightlies.
[Nexus 4 Original Android Development] gravitysandwich:
I had this problem. Here's a snapshot since I don't have a computer to get to now computer to upload the text file. Its the last.kmsg. but I think this was on r111.
[Nexus 4 Original Android Development] Nocturnal86:
Thanks that helped! I had another question thought when changing the highspeed_freq to a lower than 1512 is that the same as locking the maximum cpu frequency? or is there a differnce and if so what is it? Cause i tried changing the highspeed_freq to 1188 but in the monitor it still jumped up to the max 1512. So Im a little confused.. hope someone can help elaborate!
[Nexus 4 Original Android Development] franciscofranco:
I gotta work on that!

90/25/50.
[Nexus 4 Original Android Development] franciscofranco:
Yes I know what it is. If the screen goes off while the Gamma values are being set on boot it will create a big mess in the DMA pipe and boom. I don't know how to fix that currently.
[Nexus 4 Original Android Development] gianton:
After clearing fku app data and flashing r120 the values are 90/50/30? Should I change them to these above?
[Nexus 4 Original Android Development] sirxdroid:
Is there a good guide to the names of the sysfs virtual files that captures all the settings your kernel supports? I know the colors ones, but I'm not sure about freq, governor, scheduler, etc. settings. It would be useful to create a init.d script to keep around as a go-to.
[Nexus 4 Original Android Development] franciscofranco:
Oh ****. The driver is using 90/25/50 but the sysfs is 90/50/30 because I forgot to update that file as well. The driver is correct and its using the new thresholds, its just the sysfs file displaying it wrong. Thanks.
[Nexus 4 Original Android Development] franciscofranco:
They are so many...

cpu stuff is /sys/device/system/cpu/*

scheduler is /sys/block/mmcblk0/queue/scheduler

There are tons, I have to write a big post with all paths, but not today.
[Nexus 4 Original Android Development] JaqaL06:
after flash latest nightly signal bars won't return blue even i can connect internet :) is it bug? :)
[Nexus 4 Original Android Development] resynx:
Doesn't seem to be kernel related for me, my signal bars are still blue.
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for clearing that out. I guess I'll have to find a way to delay the screen off on boot.

Cheers

[EDIT] On a second thought, could you please add a couple of options to delay this gamma changes on boot? It would be truly appreciated.
[Nexus 4 Original Android Development] keyra74:
r120 wow 3dmark scores have never been that high before : 10396 and 5917

no lags or else for now, hope that battery life is the same as before
[Nexus 4 Original Android Development] :
If I use my phone similarly (browsing, gaming, videos, tumblr, youtube etc) with different kernels while at home, signal strength being the same and get similar SOT's (more or less in the same league), I believe I have a right to my claim that I get similar battery life between them. I don't have a lab in my house to run those controlled battery test you like mentioning! I'd suggest you use objective reasoning before making assumptions
[Nexus 4 Original Android Development] sirxdroid:
+1 At the end of the day how a kernel feels to you and how happy you are with its performance and battery life is all that matters.
[Nexus 4 Original Android Development] otariq:
I'm getting the same thing. It never happened before until I flashed 119 but now even when I go back to older versions it still stays gray unless I reconnect to WiFi
[Nexus 4 Original Android Development] drawde40599:
so us OCD challanged people can just change it to 90high _25med _50low for the visual in app anyways right ? :mad:

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------

Just log into gtalk and reboot or clear Google services cache may take few reboots
[Nexus 4 Original Android Development] Pheno.menon:
What are the stock voltage settings?

Sent from my Nexus 4
[Nexus 4 Original Android Development] ceejay83:
Just clear app data and reboot
[Nexus 4 Original Android Development] agalvin13:
it depends on your binning