yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] 75markus:
Francisco, just a question, would it be possible to release an optional next build with the stock colors until gamma control is fully implemented ?

I´m one of the guys whos screen definitely look better with the stock colors ...

if it´s too time consuming for you to release 2 builds until gamma control is ready, no problem, too.
[Nexus 5 Original Android Development] Bogusetti:
look at #2418
[Nexus 5 Original Android Development] Bei60:
Just bought the app. How come I can't update the kernel to r12 from there? When I choose the updater, I just get this blank page...
[Nexus 5 Original Android Development] Walhalla:
I don't get it, as it's totally vital to run useless benchmarks. Where else is the device rebooting for you?
[Nexus 5 Original Android Development] zetorrr:
Awesome job Franco, however... Weird thing!

I flashed r12 via fastboot and it said it went all ok, but in phone infos i still see r11; someone else?
[Nexus 5 Original Android Development] shawnaye:
App isn't fully compatible yet. Read back the past like 20 posts. Franco mentioned a million times Sunday will see the v11 of the app released.
[Nexus 5 Original Android Development] Giroyac:
Sorry if this is the stupidest question to date, I did buy the app couple of years ago, and already signed up for the beta from G+ and have it running ..

I do see the r12 update there, but before going ahead and pressing that, do I need a custom recovery to flash it from within the apl? I am rooted but haven't installed any recovery yet since I heard they're both unstable at the moment (cwm & twrp)

Again I apologize for my noobness and if this was asked before
[Nexus 5 Original Android Development] shawnaye:
Quite a legit question.

My advice is to flash cwm

Stable as all can be compared to people facing issues with TWRP.

I get TWRP has a nicer interface. But I've never had issued with cwm.
[Nexus 5 Original Android Development] Giroyac:
thanks for the reply man, So i do need a custom recovery!! What about the cache erase slowness issue with cwm, also is the one in android development thread the only one available at the moment from (playfulgod)?
[Nexus 5 Original Android Development] Bei60:
I don't have noticable issiues with twrp. Just throwing it out there.
[Nexus 5 Original Android Development] wolverineclaws:
I just have to say, I am having amazing amazing battery life with this kernel. People always say that using a custom kernel will help a lot but I haven't really noticed a difference until this kernel with this phone. Thank you!
[Nexus 5 Original Android Development] Giroyac:
Not even the super duper slow cache erasing problem ?
[Nexus 5 Original Android Development] psp9000333:
I have no idea what you did [MENTION=3292224]franciscofranco[/MENTION], but I somehow undervolted my minimum frequency to 700 mV, when previously 725 mV made the phone crash. I'm using [MENTION=1363323]vomer[/MENTION] 's tweaks as well. by tomorrow I'm confident I'll get through without rebooting.
[Nexus 5 Original Android Development] VoluntaryMan:
I bought two n5s (black and red) and they can both handle 650mV @ 300MHz. You should try it out!
[Nexus 5 Original Android Development] BTT8:
Mine can go to 625 at 300 without a hitch.
[Nexus 5 Original Android Development] Tzfardaya:
Weak sauce.... Take them down to 550 and see what happens... ;) (mine survives 600 quite nicely...)
[Nexus 5 Original Android Development] psyren:
EDIT: crap, wrong forum.
[Nexus 5 Original Android Development] Enddo:
how do you get them below 600? anytime I have ever used FKU to underclock I have never been able to get it below 600. trying results in FKU bringing them back up to 600. both on the N5 and the N4

but i think there's some bug that causes voltage to not actually go down at all. i was trying to UV in -25 steps and after trying 575 and noticing it automatically put it back to 600, doing a manual reboot causes the device to reboot due to low voltage when it boots back up

my new device is a PVS 3 and I've been able to bring 300MHz down to 620. my old PVS 2 device had a limit of 635 mV.

what PVS is yours?
[Nexus 5 Original Android Development] neriamarillo:
Franco has it set so that I won't go past 600. Before he had it that I wouldn't go past 700 but he added later until 600.
[Nexus 5 Original Android Development] visceralpsyche:
I'm seeing a real speedup in my H/LTE throughput so it's definitely better than Westwood for me. Like 2x better on average. Try it for a while and see if it's the same for you.

HTH

Cheers,

Paul :)
[Nexus 5 Original Android Development] LibiSC:
Color profile please
[Nexus 5 Original Android Development] BullHorn7:
I think r38 broke my AdAway...
[Nexus 5 Original Android Development] harshalkatakia:
Does it really save battery while idling if you UV it so much?
[Nexus 5 Original Android Development] Ben36:
Not massively but every little helps
[Nexus 5 Original Android Development] harshalkatakia:
Works fine on mine. Try re downloading and applying the host files. There's an update to AdAway, so you might wanna download that.
[Nexus 5 Original Android Development] gee2012:
UV`ing is mainly done to keep the CPU temps lower, so for limiting overheating.
[Nexus 5 Original Android Development] harshalkatakia:
Got it. Thanks! :)
[Nexus 5 Original Android Development] Ben36:
Franco,

if everyone else thinks it's a good idea, can you change the -25/+25 across the board tabs in voltage control to -5/+5 so we can have more accurate settings without having to go through every value individually?
[Nexus 5 Original Android Development] zukа:
I agree - I went back to R36 cause the animation stutters and lag were annoying me. Not sure what changed in R38 to cause this, but I was also experiencing these bugs/slowdowns
[Nexus 5 Original Android Development] granets:
I would have to say that after saying r38 doesn't stutter to me, after a day of usage, I did feel some stutter here and there, that was not present on r37. I am not going back to r37 because battery life is better on r38, and the stuttering is not that prominent for me. but there is something in r38 that is causing some problems.
[Nexus 5 Original Android Development] alcurtis93:
Can anyone explain why I'm getting this wake lock..

Stock ROM

Franco r37

Not used usb-otg ever with this device

Not had it plugged into a laptop/ PC within this time.
[Nexus 5 Original Android Development] ThePresence:
[MENTION=3292224]franciscofranco[/MENTION]

hi buddy....after flashing this kernel on pacman rom it stucks at google logo screen....
[Nexus 5 Original Android Development] davej23:
Pacman doesn't support AOSP kernels like Franco. It needs CAF kernel.
[Nexus 5 Original Android Development] Enddo:
google search says it's Qualcomms USB controller. maybe try contacting them
[Nexus 5 Original Android Development] alcurtis93:
Which is controlled by the kernel which is why I'm asking here...
[Nexus 5 Original Android Development] Enddo:
10 to 1 odds says franco comes in and says it's the same as stock

is that qualcomm battery guru running? i would start by getting rid of that...
[Nexus 5 Original Android Development] theknut:
Hi Franco,

been using your kernel since the day I rooted my N5 back in early November and never flashed a different kernel. I wanted double tap to wake so I tried a kernel based off of yours. It only took me two days to come back to your kernel. Your kernel is simply the best, thank you so much.

I remember some months ago you said you gonna have a telephon interview with Google. Did you get the job? You'd deserve it after all!

Thanks for you hard work, it's greatly appreciated!
[Nexus 5 Original Android Development] big_adventure:
Stutter?

Well, I was against the whole "stuttering" thing under r38, but I also like testing things. So I flashed back to r37, set the TCP congestion algorithm to HTPD, and tested things.

I then went back to r38, tested the same things.

Back to r37, tested some things.

Finally, back to r38 for a last round of tests.

All configuration options are the same between r37 and r38 - I don't change anything in my configuration.

System: Stock 4.4.2, ART runtime

Settings - General:

load_threshold 0

Max: 1574

Min: 300

GPU: 320

GPU up: 25

GPU down: 5

Voltage: 675 @ 300, 700 @ 422, -25 everywhere else

Above high speed 120000

Boostpulse duration: 250000

go_hispeed_load 99

hispeed freq: 1574400

input_boost: 1190400

min_sample_time: 10000

sync_freq: 960000

target loads 90

up_threshold_any_cpu 50

I have a PAM for Chrome:

hotplug_load_threshold 60

GPU up: 50

GPU down: 25

Max GPU 450

Max CPU 2265

Min CPU 300

input boost: 1267000

I did tests in Chrome, and...

r38, with these settings, displays some slight slowdowns that don't exist in r37. Especially when scrolling slowly on a massive, busy page, sometimes there is a slight jerkiness that doesn't exist in r37 with the same settings. It is incredibly slight, and really unnoticeable unless you compare back-to-back.

So, I changed the PAM for Chrome to load_threshold 0, and there is no more stutter or jerkiness in r38.

This leads me to think that something might be bothering the hotplug routine?
[Nexus 5 Original Android Development] mibtnt:
I found that r38 is a lil bit laggy. Only setting I changed was deadline.

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] franciscofranco:
I just pushed a r39 test release http://192.241.177.15/Nexus5/4.4/tests/boot-test39.img

The reason for the test is because I merged a very interesting patchlist from CAF which adds some awesome functionality to the task scheduler and how it deals with CPU freqs. You can check my git and read the commit messages. I'll most likely push it to normal release later today, but since I'll be a bit busy you can all test it in the mean time.
[Nexus 5 Original Android Development] VoluntaryMan:
I don't know anything about Westwood since I always used htcp but I do know that htcp is optimized for high-latency connections (as much of mobile connections are)
[Nexus 5 Original Android Development] franciscofranco:
Exactly.
[Nexus 5 Original Android Development] vomer:
Flashed! Not noticing any "lags" here either
[Nexus 5 Original Android Development] Plugyy:
No need to put lags in quotation marks. There are lags in r38 and if you don't have or recognize them you're fine.
[Nexus 5 Original Android Development] zukа:
That's the most frustrating thing about custom kernels. Because people's devices are different, some experience problems that others have never encountered - I've seen kernel devs call bull**** on genuine bug reports because they 'don't have this issue, so it's not real.'

Plus with some bugs, it's just impossible to capture it in a log, or describe it in a way that doesn't make a dev roll their eyes and think it's all in our heads. Today I was using R38 for the first time and thought 'this is weird, it's choppy compared to the last version I ran', and that was independent of reading all these other reports.

Anyway - I guess that's why Google's kernels are so conservative. They have to work for every device with none of these little issues that pop up.

TL;DR the R38 lag is real and troubleshooting kernel problems is f**king frustrating
[Nexus 5 Original Android Development] JamFan05:
I was one of the ones having the "issue" on r38 and i just flashed test 39 and all is good again. Thanks Franco, you sir are a beast.
[Nexus 5 Original Android Development] vomer:
You are reading way too much into my quotations.

Sent from my Nexus 5
[Nexus 5 Original Android Development] fugn:
The stutter went away on this test release.
[Nexus 5 Original Android Development] alcurtis93:
I thought battery guru was good? Has good reviews....
[Nexus 5 Original Android Development] Enddo:
battery saving apps and 'hibernators' are generally frowned upon. much like task killers are simply not really useful anymore with current versions of Android

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

if used intelligently on rogue apps, they can be beneficial. but to let a battery saving app automate everything isn't usually wise. at the very least, learn what the device is doing in order to save your battery. if all it's doing is disabling wifi 90% of the time when the screen is off, then that can be helpful, but depending on usage it can also be useless

different strokes for different folks. but an application like that, running all the time can have an impact on your device that others might not experience. im not saying it's causing the lags with r38 and your device. but it could be contributing to the cause.

when troubleshooting an issue you want to eliminate as many variables like this from the equation as possible.
[Nexus 5 Original Android Development] alvaretto:
Hi Franco, Amaizing work. test r39 is working great. Very very fluid. not a single lag here. Keep it up!! :D
[Nexus 5 Original Android Development] tsubus:
I get this error when compiling latest code:

arch/arm/kernel/built-in.o:mako_hotplug.c:function decide_hotplug_func: error: undefined reference to 'boosted'

I moved the declaration of 'bool boosted' to where it was on r38 ( http://bb.lagat.org/ilwt_franco/commits/e2abd240808f8ddd1bd07b995af1126d658e5b33 ), and it compiles fine. Have you changed anything in your environment to make it compile in the other location?
[Nexus 5 Original Android Development] franciscofranco:
Yes, I haven't pushed that patch to git because I was not sure if I wanted to do something different. Just remove the extern bool boosted from the mako_hotplug.c.
[Nexus 5 Original Android Development] PainfulLover:
r39test is a keeper, very smooth.
[Nexus 5 Original Android Development] FCDHBubbles:
+1
[Nexus 5 Original Android Development] Ladaga:
Then it's better than westwood without wifi xD thanks for the ask
[Nexus 5 Original Android Development] wund3rground:
Franco's kernel is so good it'll make you wanna slap yo mamma.
[Nexus 5 Original Android Development] KuChar_:
Guys, I have a question.

Is it better for battery life keeping online only 2 cores at high frequency or 4 cores at lower? On gaming ofc.

I'm just curious..

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] KTT16:
Loving r38! About 4.5 SOT.
[Nexus 5 Original Android Development] Enddo:
i think the general consensus is to use 4 since it will prevent them from needing to reach those higher clocks. but you'll want to underclock it to ~1.0GHz, give or take. you really should do testing though, everyone's usage and device is different
[Nexus 5 Original Android Development] arbi97:
Oh! Test version!!! Need to test it!

P.S Sorry pls for this question, but what gamma profile u used?
[Nexus 5 Original Android Development] Tzfardaya:
Absolutely no where near topical... But

have a chuckle at this...

to set the mental scene imagine Bob and Doug MacKenzie driving snowmobiles with Leslie Neilson from "the naked gun" as the cop...
[Nexus 5 Original Android Development] Arstoien:
I would say yes, for me (and quite a few others) running 4 cores always online is actually improving the battery life. But that depends on your usage. If you want to test, [MENTION=1363323]vomer[/MENTION] and [MENTION=3473030]Gingerbread Man[/MENTION] have settings in their signatures with the tunables they use, and many others also use them.

Simple underclocking might not be the best; it's much better to actually optimize the governor tunables. If you only underclock and don't change the other governor settings, the CPU will scale too aggressively, because the default settings are optimised for hotplugging. I, for example, am even overclocking, so when it really needs it, it can use those high frequencies, but with optimized settings, anything in the high freqs (say above ~1.5 GHz) is used for less than a minute combined throughout a whole day.
[Nexus 5 Original Android Development] aow1980:
I've been doing the same with my setup and have seen decent battery life with 4 cores on and set at stock min/max frequency.
[Nexus 5 Original Android Development] PainfulLover:
I do not tweak gamma or color, I think it's perfect out of the box.
[Nexus 5 Original Android Development] Hatshipuh:
Could finally test the new release, stutter is really gone.

Wonder what changed :>

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] myprecious27:
Pebble is constantly disconnecting since r38 update.
[Nexus 5 Original Android Development] drdrewdown:
my sony smartwatch isn't exhibiting this issue fwiw
[Nexus 5 Original Android Development] franciscofranco:
I have a pebble, and no.
[Nexus 5 Original Android Development] Visa Declined:
I agree. I've not felt the need to adjust the colors of my device, although I think it's cool that I can.

On a separate note, I installed r38 yesterday and charged my phone up completely before going to bed. After sleeping 6 hours and piddling around a bit after breakfast, I just noticed that my phone only lost 2% of battery while sitting idle that whole time. I find that stand-by time to be simply amazing.
[Nexus 5 Original Android Development] myprecious27:
Hm, perhaps it's just a coincidence. Thanks for the feedback anyway:)
[Nexus 5 Original Android Development] jdec529:
Test R39 is snappy and very smooth
[Nexus 5 Original Android Development] omvir:
Hi guys. Do you know if there is a way to limit screen off frequency? Other than globally under clocking.
[Nexus 5 Original Android Development] defffizz:
Lag is absolutely gone in the test version, it's smooth like stock :)

Bright Red Nexus 5
[Nexus 5 Original Android Development] castaway1:
I feel r39test more snappy then r38.
[Nexus 5 Original Android Development] danieljcf:
Mine also disconnects and reconnects frequently, but it happens on stock too. Hopefully 4.4.3 will fix this, or an update to the pebble app, since I don't have any problem with other Bluetooth devices. Pebble forums have some threads with more people with the same problem.
[Nexus 5 Original Android Development] Notechis:
The last kernels are outstanding and snappy... Great work
[Nexus 5 Original Android Development] fcisco13:
39 = beauty

Whatchu talking bout willis!
[Nexus 5 Original Android Development] Adrozz07:
Bluetooth connectivity issue on 38 with Dodge Ram factory system. Rapid fire disconnects
[Nexus 5 Original Android Development] ironjon:
Guys r39 test is awesome
[Nexus 5 Original Android Development] street675:
And smoothness is back [emoji106]

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] kypeth:
test39 gave me pigment disorder, installed norton and avast, caused bootloops and deleted all the contacts from my gmail account, rolled back to r25 and all is running smooth, thanks franco
[Nexus 5 Original Android Development] ZacksBuilds:
Where do you get test kernels?

Sent From My Carbonated Nexus 5 w/ Franco r37 ARTifyed
[Nexus 5 Original Android Development] SketchyStunts:
few pages back
[Nexus 5 Original Android Development] ZacksBuilds:
Thanks!

[MENTION=1363323]vomer[/MENTION] a while back I tried to install your settings via the flashing method but it failed in TWRP. Should I just do the manual method?

Sent From My Carbonated Nexus 5 w/ Franco r37 ARTifyed
[Nexus 5 Original Android Development] franciscofranco:
Not in the OP for sure.
[Nexus 5 Original Android Development] Tzfardaya:
Flash back to stock and see if the issue persists... If yes, then android issue, if no, then Franco issue...
[Nexus 5 Original Android Development] nitzer71:
T39 gave me goose bumps. Very good job Franco. Thanks for all your hard work... Wonder how much more you can improve the performance of our precious? Let's see and surprise us! Thanks again.
[Nexus 5 Original Android Development] Bruce Lee:
I am running r38 too and the pebble also with no issues. Have you updated your pebble recently? I had issues with the passed kernels though.
[Nexus 5 Original Android Development] vomer:
It should work... I have used it multiple times. Just redownload... But yes do it manually if you get issues

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
As a general rule... You should ALWAYS run scripts manually until you are absolutely certain that they run properly... Only then do you look for ways to automate them.... :P
[Nexus 5 Original Android Development] suchevent:
that would be the absolute worst place to look if you are looking for a kernel in a kernel thread. who would do such a thing?
[Nexus 5 Original Android Development] Tzfardaya:
Of course not, the op is for things like starting ot chats, abusing devs and just causing mayhem... I'd never look in the op for relevant information...
[Nexus 5 Original Android Development] justibasa:
Reboot on Instagram on t39.

http://pastebin.com/csVuysRM

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] laureanop:
Test 39 running like a champ. Just for reference I went back to 38 and the lag starts right away.

Back to 39 and it's a smooth sail. Go figure.
[Nexus 5 Original Android Development] Tzfardaya:
Really? I loved that show... What's the Instagram tag for it?
[Nexus 5 Original Android Development] DarknessWarrior:
any way to disable franco's auto brightness system and use android's default one? Every since I flashed r38 (was on r32 and seemed fine) the auto brightness is so dim that I literally can't read anything on screen unless I'm on a pitch black room... It seems to be on the lowest brightness pretty much all the time...
[Nexus 5 Original Android Development] david279:
Disable in fku
[Nexus 5 Original Android Development] justibasa:
What?????

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] DarknessWarrior:
thanks. had fku free, just bought the paid version
[Nexus 5 Original Android Development] shaker2k:
Fun fact..

Putting multiple question marks implies that the question was stupid, and how dare you ask it.

I think one would suffice. ;)
[Nexus 5 Original Android Development] tcat007:
Purity 4/4 + r39 = awesome! No lag, YouTube smooth, Dolphin flash smooth... won't be upgrading anything until the next Google upgrade!
[Nexus 5 Original Android Development] franciscofranco:
I'm gonna play some WoW, then I'll push r39 to the normal release channel, probably in 1h, 2h the most.
[Nexus 5 Original Android Development] nerotix:
LOL, that was unexpected, the wow part ;) Stopped like half a year ago myself, gladiator was way to easy to get .. kinda made it less fun =(
[Nexus 5 Original Android Development] justibasa:
Didn't mean to put the thanks, and I don't really care if you don't like how many question marks I put.

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] franciscofranco:
Easiest Gladiator was first WoTLK season with Holy Paladin + DK. Easy Glad.
[Nexus 5 Original Android Development] franciscofranco:
Pushed r39:

* Task scheduler improvements from CAF for better CPU frequency management

Enjoy ;)
[Nexus 5 Original Android Development] 530farm:
Was there any new changes from the r39 test from earlier this morning?
[Nexus 5 Original Android Development] iPsychoGeek:
Yes, check his github.

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] 530farm:
I've tried, but have no idea how to navigate github and find any changelog.
[Nexus 5 Original Android Development] iPsychoGeek:
https://github.com/franciscofranco/hammerhead/commits/nightlies

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] 530farm:
Thanks! Is there to see what was pushed to a certain version or is just basing it on the time stamp?
[Nexus 5 Original Android Development] iPsychoGeek:
It's basing on time.

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] Ltdrev:
Just installed r39 and got stuck into boot loop :what:

Furstentum Liechtenstein
[Nexus 5 Original Android Development] Tzfardaya:
Which rom?
[Nexus 5 Original Android Development] Savant:
Switch ROMs if your on cm since Franco is only an aosp compatible.
[Nexus 5 Original Android Development] psp9000333:
what I thought was impossible is possible. I over clocked to 3.01 GHz. I crashed a few times, but it works!
[Nexus 5 Original Android Development] Tzfardaya:
just need to overvolt to get it stable...