yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Arstoien:
Just one final report from me. I did the following:

– clean flash factory image (flash-all.bat). Cleaned everything from the phone

– flashed TWRP

– rooted with SuperSU 2.71

– installed FKU

– flashed latest r82 from FKU

After boot, and waiting a couple of minutes for the cpu to settle, I observed the same lag and frame drops as reported before. Afterwards, I flashed r80 (with TWRP), and they were significantly lower (as on the screenshots). Then flashed the latest test zip, which you said was the same as r80, and the frame drops were back. No uv, no mods, nothing else modifying kernel settings, etc.

I understand you say latest zip is the same as r80, and there's nothing you can do. But just saying that what I'm observing seems to hold up even after complete clean flash. I can't see this having to do with anything messed up on my device, software-wise, but I don't have any explanation. Just thought to come back with this info. Again, thanks for your effort in solving the issue.
[Nexus 5 Original Android Development] franciscofranco:
That power hal message is there since day 1. It's not relevant, don't worry about it.

Something is definitely ****ed up I'm very ****ing surprised and genuinely without any other ideas at this point. I'll see what I can do. Sorry & thanks for taking the time to help me.
[Nexus 5 Original Android Development] franciscofranco:
Try this, echo 1 > /dev/cpuctl/cpu.notify_on_migrate
[Nexus 5 Original Android Development] Arstoien:
Wow, that made things smooth again. Just like on r80. Nice! What does that mean?

PS: I tested it on the latest official r82.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
I don't know why I disabled that thing to be honest. That'll let the scheduler send boost hints when there's a thread migration.
[Nexus 5 Original Android Development] Arstoien:
Great, thanks for going through this and finding the root of this. I'll keep this enabled for now, since it does eliminate the micro lags here and there.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Yeah, it's enabled on r80. I flashed r80 and went through and compared both init.fk.rc files (just where I store my ramdisk changes) and that thing was disabled on r81/82. Why? I have no ****ing idea. Probably drunk when I did that.

Try the attached r82, has it enabled and I dialed back some of the performance boosts on r82 since they will hurt now with this thing enabled. Test it out for me please and I'll adjust things a little bit more if needed.
[Nexus 5 Original Android Development] Arstoien:
Yep, it runs fine through my initial tests. You sure the correct value for go_hispeed_load is still 99 and not 95? Used to be 95 on r80 for hispeed_freq of 1497, so just checking in case you missed it.

Also, at the moment applying Balanced profile in FKU changes some of the default settings to old values. You probably know but worth saying just regardless.

?

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Yes, it should be 99 now because of some other changes - just to balance things out. Yes I'll update the profiles before I push this out officially. Thanks again.
[Nexus 5 Original Android Development] Madsunable:
[MENTION=3292224]franciscofranco[/MENTION] Thanks for still supporting our Nexus 5. With your kernel my phone runs so smooth. I follow your work since maguro ;)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Arstoien:
By the way, what is the path for the CPU-boost tunables?

Sent from my Nexus 5
[Nexus 5 Original Android Development] xeraphael:
/sys/module/cpu_boost/*
[Nexus 5 Original Android Development] piotrus22:
is it possible to flash this kernel via fastboot without unlocking the bootloader? I already got confirmation that I don't have to be rooted but wondering if I can do this without even installing custom recovery, etc. Just literally ADB this kernel onto the stock rom?
[Nexus 5 Original Android Development] franciscofranco:
You can't flash anything through the bootloader unless you're unlocked. You don't even need to flash a custom recovery, you can just boot it: fastboot boot recovery.img and then you can adb sideload the kernel .zip file. The recovery will be back to stock as soon as you leave it.
[Nexus 5 Original Android Development] nmlssit:
I am coming from another kernel, i flashed stock boot.img cause im in stock factory image but im in bootloops. I did something wrong or is it because f2fs?

Fixed: flashing stock boot.img is not enough, i flashed stock system.img too.
[Nexus 5 Original Android Development] franciscofranco:
Uh... I don't know. I support f2fs just fine.
[Nexus 5 Original Android Development] Arstoien:
After some time using it, I can say it does occasionally feel less responsive – little longer response time after touching the screen, some little animation lag occasionally. Happens when I push it a little bit – changing apps quickly and doing a lot of stuff in a rapid sequence.

I'm telling you this, if you're considering adjusting the performance internally. Perhaps it's a decent tradeoff for battery life. I'm just more concerned about performance, so I'll be looking into tweaking the kernel settings myself to boost the performance a bit, if you choose to keep the settings as they are

I wonder about the best approach to gradually increasing the performance. Perhaps lowering the go_hispeed_load to say 95 as a first step. If that's not enough, maybe slightly increasing the hispeed_freq and find a good spot for both values. I don't think touching the cpu boost settings would be needed? Just asking for a quick suggestion for a starting point.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Driver007:
above_highspeed_delay - 20000

boost - 0

boostpulse_duration - 80000

go_highspeed_load - 99

hispeed_freq - 1190400

min_sample_time - 40000

target_loads - 98 300000:64 422400:58 652800:81 729600:74 883200:83 960000:73 1190400:85 1267200:95 1497600:76 1574400:9 1728000:13 1958400:16 2265600:5

timer_rate - 45000

timer_slack - 30000

Found this settings for interactive, consider to try these.
[Nexus 5 Original Android Development] Arstoien:
Appreciate the effort but these are silly. I wouldn't recommend you using that. Also, I didn't mean to look for specific settings – just direction to which would tunables would be good to adjust, since I don't know the back-end workings of the kernel.
[Nexus 5 Original Android Development] osm0sis:
I think I can confirm this. I can readily produce some choppiness playing Alto's Adventure with the original r82. Flashed back to r80 and it plays smoothly, then tried [MENTION=3292224]franciscofranco[/MENTION]'s latest test build and it's definitely a bit choppy again.
[Nexus 5 Original Android Development] Arstoien:
I've currently got go_hispeed_load at 95 and target loads at "70 1350000:90 1800000:99" and it seems to perform better.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Great feedback, thanks! Let's try two things, seperatedly:

1 - go_hispeed_load to 95

2 - cpu-boost -> sync_threshold to 960000

Try these things one at a time and let me know.

I'm sorry but that's simply retarded.
[Nexus 5 Original Android Development] trailblazerz11:
I have reason to believe it might be a bug with BBS. For me at least, the audio mix time isn't included in Power Manager service. Anyone else notice this?
[Nexus 5 Original Android Development] GeekMcLeod:
Finally received my N5! Can't wait to get home and finally get it all rooted and set up! Now all I'll need is ParanoidAndroid and it will be perfect!

Does anyone have any recommendations for a rom to use while waiting for PA? I already know I'll be forever using Franco's kernel.

Sent from your fridge. Yeah, YOUR fridge. Not mine. Yours!
[Nexus 5 Original Android Development] zephiK:
Cataclysm or PSX
[Nexus 5 Original Android Development] webvictim:
Do you have location set to "High accuracy' or "battery saving"? Background apps on sync? Stuff polling? The location stuff that Google Now does is awful at draining the battery - i see the same thing, down to 97% within 10-15 minutes off the charger if I leave it on. When I set to "device only", I can be at 99% off the charger for an hour.

Disable always-on wifi scanning if you haven't already (in the wifi settings) and switch location to "Device only". You should see a big decrease in load on your battery.

I'm going to say that your issue is nothing to do with the kernel - it doesn't touch Bluetooth. I've used the last 6 or 7 Franco kernels for the N5 on mine and it still works the same as it ever did in my car. It sounds like maybe your car's Bluetooth implementation isn't friendly with the phone or something. The only way you can be absolutely sure is if you go back to the stock kernel and try it then, but I honestly think it's nothing to do with it.

I think Google acknowledged this as a software bug and have fixed it? I thought I saw a link to an issue somewhere on code.google.com where there was a comment saying a specific commit fixed the issue - unfortunately I can't find it now.

Some people here are having the same issue; http://xdaforums.com/showthread.php?t=2514982
[Nexus 5 Original Android Development] miracler:
My settings for interaction sounds were all off from the beginning, except for the "vibe on keypress", which I have also turned off a few days ago hoping to solve the issue. :(

I'm wondering if it could be the IM clients like WhatsApp, which are firing off the notification sounds (from crazy group chat spamming)
[Nexus 5 Original Android Development] Bytecode:
Hello people, quick question, Franco's app (not the free version) won't save my settings after a reboot. Every time I reboot I have to re-underclock and under volt and you know, set everything back up. Only app profiles get saved. Ideas?
[Nexus 5 Original Android Development] beaver2233:
have you selected 'set on reboot' for each option?
[Nexus 5 Original Android Development] DerItaliener:
Yep, longpress the option you want to stick and you will see a checkbox. :) Reading what the in App tutorial says, or the first post here. Could have solved your problem too.
[Nexus 5 Original Android Development] webvictim:
After my previous posts around how the wifi at work drains my battery, I've decided to switch wifi off in the office and see how the battery does on LTE/HSPA+. The LTE signal here is generally pretty bad inside but we have some AT&T cells installed out the back of the premises, so HSPA+ signal is usually very good. The wifi is just a guest network anyway which provides a fast internet connection and lots of spammy ARP traffic; I have unlimited data so no real concern around that.

I'll report back, but the early signs are that my battery drain is vastly reduced when wifi is disabled. It might honestly be more economical for me to switch off wifi and use mobile data in the office.
[Nexus 5 Original Android Development] Bytecode:
Thanks :) i couldn't see the app tutorial as the app crashed on 1st run lol
[Nexus 5 Original Android Development] tyrellcorpnexus:
Can you clarify this a bit?

It's really weird, I tried comparing r12 and r14 and it seems to do the same thing on mine.

Has difficulty locking GPS indoors, on Google Maps, but on Mapquest, it finds a lock. Sometimes mapquest defaults to the location nearby but not precise that was pulled from Google Maps.

So confused with whats going on.

Google Maps seems to be working fine when I test it out while driving though?
[Nexus 5 Original Android Development] franciscofranco:
Ok guys I need some help testing r15 since it has a couple of more than trivial changes. Download r15 from here: http://192.241.177.15/Nexus5/4.4/tests/boot-test15.img and fastboot flash boot boot-test15.img - don't bother asking me for a flashable .zip.

Theres a lot of underlying changes and I need specific tests on performance while the device is being stressed (eg. games) and battery life (at least for 24 hours):

* touchboost has been re-worked so that it doesn't go through interactive's speedtask thread therefore avoiding spinlocks and a less direct code path

* when there's a thread migration (eg. thread X is migrated from cpu0 to cpu3) it evaluates what's the source cpu current frequency and if its higher than the target cpu frequency then it boosts the target cpu to the source cpu freq therefore avoiding perceiving loss of performance during thread migrations

* the hotplug driver has been changed a bit in regards of evaluating the current cpu load to determine when to online/offline cores - I optimized the code to reduce calculations and less useless code executions thus reducing the algorithm complexity

* suspend_frequency is no more to see if it removes the audio stutters on screen off completely

* to balance out performance/battery ratio, since the thread migration thingy will make the device run on higher freqs a little more often, I increased timer_rate to 30000 and the hotplug threshold to 70 which should help the battery life on the longer run

* sound control custom values should not be reset anymore, please test this

Code is pushed to github if anyone wants to take a look. For r15 official release I'll add a toggle to change the colors to and from stock.

That should be it - can't wait for your tests so that I can push this as an official release asap!
[Nexus 5 Original Android Development] tcat007:
Make sure you're outdoors to test GPS lock speed, satellites need to be "in view". Tower lock should work fast w/o GPS on as long as you're not in a dead zone. I wouldn't think it would have anything to do with the kernel.
[Nexus 5 Original Android Development] shaker2k:
Do you want us to keep everything at stock values while testing
[Nexus 5 Original Android Development] Tom540:
Just flashed, seems great so far but I'll report back tomorrow
[Nexus 5 Original Android Development] franciscofranco:
Yes please.
[Nexus 5 Original Android Development] i860:
Very smooth r15, benchmarks scores are very high. Sound boost seems to stick, will test more tomorrow.

Upsss

Reboot during my game dead trigger 2 ( never had a reboot on all r's ) not sure if krenel related a fc with fire fox since r15.

http://pastebin.com/Kb4LJQ5m
[Nexus 5 Original Android Development] Craxx:
Firefox is fc with 15

Best regards ;)

Craxx

Send from my Nexus 5 with Tapatalk
[Nexus 5 Original Android Development] Bogusetti:
Oops, after playing a round Dead trigger phone freezes when I tried to unlock

https://www.dropbox.com/s/yn7lrzhut3rrgta/2013-11-26_23.20.zip
[Nexus 5 Original Android Development] franciscofranco:
And? FC's are bound to userspace, not Kernel.

pastie.org please, thank you.
[Nexus 5 Original Android Development] Driver007:
It's retarded or not don't care, not mine settings, just some guy showed sot of 6 hours...
[Nexus 5 Original Android Development] franciscofranco:
Of course, those will put your device back to the stone age.
[Nexus 5 Original Android Development] marcusva79:
Does input_boost_ms do anything for app speed? Lag in app scrolling.
[Nexus 5 Original Android Development] nexterultim:
what about this?

above_hispeed_delay 20000

align_windows 1

boost 0

boostpulse_duration 0

go_highspeed_load 20

hispeed_freq 300000

i/o_is_busy 0

max_freq_hysteresis 80000

min_sample_time 10000

target_loads 65

timer_rate 80000

timer_slack -1

These settings were made by my friend vitromanof to decrease heating while gaming. Touchboost handles the smootheness (1.2Ghz on tounch for CPU0-1)

---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------

Of course. It's the amount of time, while CPU freq will be boosted to values set in input_boost_freq
[Nexus 5 Original Android Development] marcusva79:
Thanks. Was noticing a bit in apps. Any other recommendations? Make these best of phone butter? I read that r80 is phenomenal.
[Nexus 5 Original Android Development] nexterultim:
You can set conservative governor with cpu-boost enabled. It's way snappier than interactive
[Nexus 5 Original Android Development] marcusva79:
Okay just set it to conservative. I'll let it settle and see what it does. Running r80.
[Nexus 5 Original Android Development] Arstoien:
I'll use each for a bit and let you know. As I said above, both lowering go_hispeed_load to 95 and lowering the target_loads for the lower frequencies (simultaneously) did improve the performance to an acceptable level (for me). Increasing sync_threshold seems like a good idea to try out.

So I'll give you some feedback after I've used each of your two suggestions for a bit.
[Nexus 5 Original Android Development] franciscofranco:
timer_rate to 80000 is ridiculous and it'll be lag fast.

Thanks. I think sync_threshold to 960000 will help a lot.
[Nexus 5 Original Android Development] Arstoien:
It may take some time, I don't see any immediate changes, so I'll run it for day or two. Trying not to fall for placebo effects, since I don't really have an objective way to compare.

?

Will wait to see some reproducible lag and try to reproduce it with different settings.
[Nexus 5 Original Android Development] franciscofranco:
[KERNEL][N5][ALL ROMS] franco.Kernel - r82

That and go_hispeed_load to 95 should be enough.

If all fails I'll go back to r80 parameters and we can go sleep happily.
[Nexus 5 Original Android Development] Arstoien:
I guess we can call it ok with your suggested settings – go_hispeed_load 95 and sync_threshold 960. Seems decent for now.

Looking at the settings from r80, they seem the same with the exception that sync_threshold shows 0 in the app and boost_ms is 20 instead of 30. I suppose there's more behind the scenes?

Since we're on the topic, mind if I ask you a couple of things? What does boost_ms do? And isn't boostpulse_duration obsolete now, since you use CPU-boost now and input_boost_ms is doing what boostpulse_duration used to do before?

And as a little bit of off-topic, if I may – I'm planning on upgrading in the near future and I'm considering whether I should wait for the september nexuses in hopes of a decent ~5" nexus that isn't terribly expensive. Alternatively I could go sooner for the 5X or OnePlus X. I'm a bit hesitant to go for the OnePlus, seeing their customer support is **** and they don't promise anything related to upgrades. The 5X seems ok but a bit too big for me, so that would be a compromise. Also I've heard that it actually has less usable RAM than the 5 because of its 64bit architecture. Any thoughts? Cheers :good:

PS: It s actually running pretty damn well with these two changes.
[Nexus 5 Original Android Development] franciscofranco:
Yeah, but I I think we can lower input_boost_ms to 100ms or even lower now. sync_threshold to 960MHz guarantees the target core will be boosted to at least that value when there's a thread migration (for a minimum time of 30ms = boost_ms).

I think boostpulse_duration isn't used anywhere at the moment. I'll double check and remove it if needed.

Don't buy the One Plus X. It's a downgrade compared to the N5. If you don't need a better camera & fingerprint scanner then you better off with the N5.
[Nexus 5 Original Android Development] Arstoien:
Yes, I think that's a brilliant idea. I don't notice any negative impact on performance from lowering to 100ms

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
I made it 125ms on my local build and it seems to be fine. Will push r83 later today when I get home.
[Nexus 5 Original Android Development] Eltorito94:
can't wait!! :D
[Nexus 5 Original Android Development] franciscofranco:
r83 is up!

Sent from franco.Kernel updater (http://goo.gl/MtECP5)
[Nexus 5 Original Android Development] franciscofranco:
Any feedback?
[Nexus 5 Original Android Development] RucaNebas:
So far....very snappy = smooth !!:good:
[Nexus 5 Original Android Development] Peksman:
Works perfect. Smooth as ever
[Nexus 5 Original Android Development] osm0sis:
All seems smooth in Alto's Adventure again. ;):highfive:
[Nexus 5 Original Android Development] ej8989:
Very snappy on r83.
[Nexus 5 Original Android Development] Arstoien:
Running quite well here too. I've even lowered the sync threshold a bit to 1.5 GHz
[Nexus 5 Original Android Development] franciscofranco:
Awesome!!!
[Nexus 5 Original Android Development] Alex Kane:
Yup.

Nice_&_Fast :)
[Nexus 5 Original Android Development] Arstoien:
May I ask what's the reason for tuning the sync_threshold so high? To me, it seems to be using the sync frequency a decent amount of time. Usually almost no time in higher frequencies. And lowering to 1.5 doesn't reveal any lags. I see that some of the other tunables are compensating for it in the cpu boost but was just curious why so high – maybe just to be on the safe side?

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Seemed like a good value seeing how often threads are migrated. I can lower it down eventually based on user feedback :)
[Nexus 5 Original Android Development] Paschfire:
r83 is fabulous!! its just buttery smooth!
[Nexus 5 Original Android Development] osm0sis:
So now is it time for flo/deb to get an official AK2 release? :angel:;):fingers-crossed:
[Nexus 5 Original Android Development] franciscofranco:
Yes it is! Probably monday/tuesday, ****ing wedding this weekend -_-
[Nexus 5 Original Android Development] fatspirit:
Your own?
[Nexus 5 Original Android Development] iZak17:
Thank you so much for your effort. This kernel is SO much stable. Very well battery life and speed.

Sometimes, without apparent reason, the CPU goes to its maximum capacity (I know it because tinycore app) and any phone process starts to run veeryyy slow. After a few minutes (or if I reboot) everything goes back to normal.

Any advice?
[Nexus 5 Original Android Development] :
Would like to know the same :D
[Nexus 5 Original Android Development] franciscofranco:
Nope.

I don't know, I don't know how your phone works or what apps/processes are running.
[Nexus 5 Original Android Development] asdgonzalez:
Just awesome!! Very smooth and got likely more than 4h screen
[Nexus 5 Original Android Development] :
Yeah.. I guess r83 comes straight from heaven :D
[Nexus 5 Original Android Development] franciscofranco:
It does!
[Nexus 5 Original Android Development] :
I seend'ed it in a dream, r83... Then it came and I knew where it was from. :cowboy: Really cool to see you still here dropping your kernels for Hammerhead. I recently had an accident w/ my 6p so back to the good ole N5 for now. Thanks Franco! :good:
[Nexus 5 Original Android Development] kanin_rider:
R83 also runs perfectly awesome here. [emoji41][emoji23]
[Nexus 5 Original Android Development] :
Question: This kernel work with latest 300HZ tick rate?
[Nexus 5 Original Android Development] Arstoien:
No, Google never changed that for Hammerhead so it's not really "the latest".

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
What do you mean "works"? Open my github and you'll see.
[Nexus 5 Original Android Development] :
Ok
[Nexus 5 Original Android Development] franciscofranco:
Some users reported Haptic Vibration setting wasn't restoring on boot using FKUpdater. I just can't reproduce it. Can anyone with this issue let me know which values to->from are you using?
[Nexus 5 Original Android Development] :
I just checked with my device. I'm running stock ROM and the default value is "63". So I changed it to "70", rebooted and it's still there! :)

Can't tell anything except that it survived a reboot and that the setting is working fine...
[Nexus 5 Original Android Development] franciscofranco:
Awesome.
[Nexus 5 Original Android Development] franciscofranco:
FKU 14.2 is up: https://plus.google.com/u/0/+FranciscoFranco1990/posts/bq7pniLkpBE
[Nexus 5 Original Android Development] jvifdz:
Im noob in kernels but what is your prefer configuation settings for the sp800?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] ItachiSama:
FKUF with fixed support for downloads?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
The ones I ship with.

Not yet.