yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] doubleho:
ya I found the battery life became worse too and I downgraded to r47, best battery life so far
[Nexus 5 Original Android Development] vs0587:
+1

:good:
[Nexus 5 Original Android Development] RobbieL811:
Has anyone figured out a good PAM for Asphalt? I'm still getting some glitching & skipping with my settings. Only way I can get it to play stable is set load threshold to 0 & max freq to 1190. And even then it will still glitch a little.

Sent from my Nexus 5
[Nexus 5 Original Android Development] leAndroid91:
hi guys,

i updated to r48 yesterday.

now when screen's on core 0 runs at 300mhz and core 1 runs at 1036 mhz.

(300mhz is my min freq).

is this caused by franco?

as far as i know both cores stayed at min freq until you touch the screen or anything else happens since r47.

when touching the screen both cores go to 1497mhz.

this is just like always.

thanks!
[Nexus 5 Original Android Development] zai89:
Crazy setting if you want to try ?
[Nexus 5 Original Android Development] Arstoien:
I don't know if I like the values for up_threshold_any_spu_freq and _cpu_load. Particularly the load seems too low and the phone ramps up to sync_freq too often when I'm really not doing anything. Could be just me but I'll test raising it a bit. Immediately I don't see any dropped animation frames.

That would throttle within minutes.. ?
[Nexus 5 Original Android Development] neriamarillo:
He did say crazy settings lol
[Nexus 5 Original Android Development] floepie:
Huh, I find the opposite is true. At low light levels, a light theme doesn't provide enough contrast with a dim white background.
[Nexus 5 Original Android Development] franciscofranco:
If its using 1GHz then its because there's load for that. There are only 3 tunables wich can ramp you cpu to that value, which is sync_freq, that is triggered when theres a thread migration (task is moved from one core to another) and hispeed_freq which is a middle ground freq to prevent the cpu to ramp to max when theres high load but no need to go big. I decreased hispeed_freq immensely on r48 for improved battery life, but on the other hand made it more easily to hold the cpu at 1GHz when theres some quick load bursts (eg. App openings, quick scrolling etc). All in all its sustained freq > big bursts of high frequencies. You'll have a better overall experience with this and without battery life drop. If you don't like this just change sync_freq to 0 and you'll lose performance substancially probably without any major battery gains (in the long run at least).
[Nexus 5 Original Android Development] franciscofranco:
Sure, test a couple things and let me know if you have any ideas for improvement. I explained my reasoning on my post above :)
[Nexus 5 Original Android Development] Tzfardaya:
Heh, I agree, if you look at my phone all the settable screens are dark.. I was just echoing Enddo's reasoning for the light themes.. ;)
[Nexus 5 Original Android Development] prstorero:
Not sure if this sod is kernel related, but I have no idea since I'm not sure how to read a last kmsg. Could someone let me know if it was just a user space derp? I've had a few but waited to see if it happened more before posting something.

pastebin.com/Yd9yMxyd

Wasn't sure if pastebin is preferred or an attached log.
[Nexus 5 Original Android Development] SedyBenoitPeace:
I made a new profile with "When Wifi Connected" and then i put on this profile a "Run Shell" and here i put the command that i posted on my previous post :)

Do you need a step by step? :D
[Nexus 5 Original Android Development] AmmVid:
Oh thanks, but [MENTION=4860519]Tzfardaya[/MENTION] already made a little video and everything :p well anyways I have it on reboot, do you think that would be better to do or have it when WiFi is turned on?
[Nexus 5 Original Android Development] SedyBenoitPeace:
Oh well sorry.. I didn't see.. Well I made the script when I connect to a network with wifi.. But i think that also at reboot or wifi turned on will be good.. There isn't any difference I think :) the main thing is that the ipv6 will be disabled.. No matter when :)

Inviato dal mio fantastico Nexus 5 con Franco's kernel
[Nexus 5 Original Android Development] Wenzo2:
[MENTION=4809179]yorici[/MENTION] any news about your color profile?
[Nexus 5 Original Android Development] Red5:
Piereligio V7 is the new standard. ;)
[Nexus 5 Original Android Development] Tzfardaya:
Are you trying to start another colour calibration war?
[Nexus 5 Original Android Development] Ben36:
I only use my own colour profile as it's the best for battery degradation ;)
[Nexus 5 Original Android Development] gharrrrrr:
?

Sent from my Mako using my T.A.R.D.I.S.
[Nexus 5 Original Android Development] Tzfardaya:
Pfffff

I still prefer my colour profile, colour accurate, nice deep blacks, charges the battery

slightly, but I can't release it yet I'm still working out the ham on rye bug... (keeps making me a turkey on white instead.)

He's just messing with you...
[Nexus 5 Original Android Development] vomer:
I have my pitchfork ready!!!
[Nexus 5 Original Android Development] granets:
Going to get my torch now. I happen to be back to stock, because I keep flashing stuff and you really can't get better than stock for now
[Nexus 5 Original Android Development] Tzfardaya:
Don't get caught flashing... The neighborhood parents and cops frown on it. ;)
[Nexus 5 Original Android Development] granets:
Nah cops here don't mind :D
[Nexus 5 Original Android Development] Tzfardaya:
Must be nice.. They've warned me twice.... :(
[Nexus 5 Original Android Development] granets:
Gotta be more careful when you flash in public :D
[Nexus 5 Original Android Development] leAndroid91:
OK i got your point.

But i've an additional question.

You said (if i understood correctly) that the 1ghz is caused by some load.

But according to your CPU monitor there is nothing i'd call load.

So is it just preventing and waiting for load?

tapatalked from hammerhead
[Nexus 5 Original Android Development] yorici:
Hi there, thx for taking interest.

I had calibrated a great deal of values until I discovered a bug in the KCAL Color Control (The 3 sliders). They multiply the colour channels with (255/256). RGB-255 is therefore lost and we lose a color to display. That isn't the worst issue, but the parameters work a bit different now. It has less use for to calibrate the display when the bug is still present. I have already talked to some people and we are working on it. (I'm just a tester as I can't code for sh*t ;P)

I'm afraid you are right. The displays delivered by Samsung, LG and even Apple have higher colour temperatures. This is in no way accurate of course. Though I do not prefer higher colour temperatures, I do think Piereligio V7 can be improved. The colour temperature is allround oke, but the gamma is horrible. Because of the higher colour temperature, the gamma needs to be a bit higher (2.3/2.4). But it's current state is V shape, ranging from 1.8 to 2.4 to 1.8 again. This is in no way recommended. When the bug is finished and I finished a D65 colour profile, I will try to improve Piereligio V7.

____

I have not done nothing whilst the bug is present, because I have written a guide to calibrate the Nexus 5 without much complication with a colorimeter. I will release that including all the little things I have made for it, like the spreadsheet where colour temperature and gamma are customisable. Also in the guide is the truth about what those without a colorimeter can do (which is not a lot unfortunately) to improve their screen.

____

Does anyone know a method to adjust screen brightnesslevels? I'm not talking about autobrightness here.

Example:

When you move the slider to 50% it get's around 50% darker in cd/m2, but not to the eye. The way our eye perceives light is different and uses a power law (for colours this is gamma correction). I want to make the brightness slider linear, so 50% brightness feels like 50% brightness, not 70%. Anyone? I'm happy to share the results when I'm done doing that (as I will use my colorimeter for it)
[Nexus 5 Original Android Development] franciscofranco:
Do you really think the governor evaluates the load every second? It calculates it dozens of time every tenth of a second, while you don't see it with a monitor app the governor fluctuates a lot...
[Nexus 5 Original Android Development] vs0587:
Any news for the battery consumption with r48? :confused:
[Nexus 5 Original Android Development] Enddo:
48 is as good as the others are. if you're having unusual battery drain i bet it is a rogue app
[Nexus 5 Original Android Development] vs0587:
The drain is started when I flashed r48, the drain is stopped when I reflashed r47...... This is unusual..
[Nexus 5 Original Android Development] Tzfardaya:
I get unusual battery drain that starts as soon as I turn the phone on... Drain stops when I turn it off..
[Nexus 5 Original Android Development] vs0587:
Compliments for you fu...ing phone.. Maybe it's better that you throw it in the rubbish..
[Nexus 5 Original Android Development] Enddo:
i dunno what to tell you then

i get the exact same battery life. and im very vigilant on keeping track of how long it takes to drain each 10% interval

you're going to want to monitor BBS logs to find the culprit
[Nexus 5 Original Android Development] Tzfardaya:
Why would I throw it out? It drains unusually slowly.... :P
[Nexus 5 Original Android Development] vs0587:
I haven't do anything new (install, uninstall app) when I flashed r48.. From r47 to r48 the only change is the kernel, and the battery life is minor than r47.. :eek:
[Nexus 5 Original Android Development] Tylog:
I really ask me why some people can't accept when some guys say that for “ these “ guy's the battery drains more then before.

It's fact , 47 lesser battery consume as 48 , (i read a lot about it and test it self) , not extreme but notable. And please don't start now to tell me i need BBS/GSAM , Santa Claus or whatever.

Its ok when some people got the same results as before, but should also respect if it is not the case for some other.

And posting stupid crap like phone off no drain blala is really helpful for asking guys.

Some times it's better to say nothing when nothing to say.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] gerbig:
If you feel like battery is going faster with r48, maybe try setting thermal throttle back to 60? The default changed from 60 to 70 with r48, less aggressive thermal throttling = more battery usage....
[Nexus 5 Original Android Development] Tzfardaya:
But I'd never be able to say anything then... :(
[Nexus 5 Original Android Development] Enddo:
where are your tests that show this 'fact'. lots of people like to throw that term around here yet no one is citing any actual proof

sometimes it's better to not say anything when you're ignorant to what is actually going on. how about you look at stats and pinpoint what is different. look at BBS logs and see if Google Now, GPS, Cell Signal or the 200+ ****ty apps you have installed is draining the battery more due to syncing, not letting the device sleep, etc

or you can show BBS stats for r48 with BBS stats for r47 and show us what is causing more drain. the battery usage is in the stats. if you're too ****ing lazy to look for them and to actually show what is using the battery then you will continue to get responses like 'i get no battery drain when i turn the phone off'

oh right. you would rather come into a development thread and blame the custom kernel, blame the custom ROM because that takes the blame off yourself, takes the blame off your usage, takes the blame off your apps and takes the blame off your everything else

so yes, show me where this 'not extreme but notable' battery drain is. show me what is being used with logs and then ill add some credence to your opinion of excessive battery drain
[Nexus 5 Original Android Development] farplaner:
Thanks for the suggestion. The weather did get a lot hotter here the day after I flashed r48 lol so its hard to tell for me
[Nexus 5 Original Android Development] Serious_Beans:
How do you make the max frequency stick? I'm on stock ROM with r48, when I turn off the screen my max CPU freq goes back to 1497 when I set it to 2265. I tried searching this thread and Google and I can't find any solid answers.

Thanks
[Nexus 5 Original Android Development] Tzfardaya:
Check the FAQ listed in the op of this thread and read up on thermal throttling there
[Nexus 5 Original Android Development] RobbieL811:
Do you even know who you quoted? I think that the "Recognized Contributor" by his name, alone, shows that he is not a lazy or stupid person as you have implied. I'm pretty sure that by now in his android career, he knows how to figure out what apps use and don't use battery. If he says that he's getting less battery life, he's getting less battery life. Most likely all of the other people that have posted about it are getting less battery life too.

---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------

Is it possible that you could be getting thermal throttled. It does that when you are getting throttled. If you leave it alone, it should go back to 2.2.
[Nexus 5 Original Android Development] Haidary.T:
Fight! Fight! Fight! Fight! XD
[Nexus 5 Original Android Development] hello00:
hows the test boot?
[Nexus 5 Original Android Development] resynx:
Very smooth. Battery seems good so far too :D
[Nexus 5 Original Android Development] blueren:
If it's not thermal throttled, then ur phone seems to have the same behaviour my phone does.
[Nexus 5 Original Android Development] 530farm:
I saw there is a new test boot.img, however github doesn't show any changes since the r48 release. Am I not looking in the right place on github ?
[Nexus 5 Original Android Development] RobbieL811:
I'm pretty sure that he works out of his "nightlies" branch. Here is the link. I don't see anything new.

https://github.com/franciscofranco/hammerhead/commits/nightlies

Sent from my Nexus 5
[Nexus 5 Original Android Development] 530farm:
Yeah, that's where I was looking. There is a new boot.IMG uploaded today, 5/9. Which is why I was asking
[Nexus 5 Original Android Development] RobbieL811:
Yeah. I see that. Maybe it is something that he built locally. Idk what it is.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tylog:
Thanks, I had yesterday still considering whether I answer but this is my time to shame. When I say "do not tell me me to take BBS / GSAM" is the name that I know what to do and not that I'm too lazy. I work in SlimRom Team and yes, I'm RC, suggests that I know a little bit what I'm talking about, what i have to do , how to do and whatever :). My post was merely to point it when several people say it is so, there will be something to it, and I never say it drain when the phone sleeps, the bigger consume is present when the device is in use. Discuss on the lower level is not what I like, so I'll leave it , one point this guy say is true, it's a developer thread.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Madpiercing:
My impression of this r48 so far it's very good.

Honestly, i see the general consensus is this is a battery life oriented kernel but.. So far with r48 i had the best benchmarks results of all the setups i've tried as of now lol!

I know benchmarks don't means a lot. However i think antutu is a good indicator of how your setup behave in stressing scenarios (especially in regard to thermal throttling). Well, i use franco since.. i dunno.. r18-20 or something. Well with r48 i just scored 37453, with hotplug at 0, and an oc to 2400 mhz. After antutu the cpu was at 28 °. I mean 28 ° and it's almost summer? With previous setups i couldn't even complete the test or i scored 28000 due to thermal trottling. Goes to show how good this kernel is and in how much it improved managing energy and heat.

As far as battery life goes, i had the best with the series of kernel which implemented the caf optimizations, but i prefer these recent revisions. They feel more snappier and 10 min less battery life isn't really a problem for me. But i can see where the users are coming from, i noticed that the cpu run at average core speeds more often than with r47 and i've read franco explanation of why is this, and i think with certain usage scenarios this could lead to a little bit less battery time.Doesn't bother me. If it bothers you, change the tunables or revert to r47, the difference isn't night and day aniway. But you have to ask yourself, do 5 minutes less sot really matters?

r48 is the best all around revision so far imho.

Thanks Franco!
[Nexus 5 Original Android Development] piumach:
I went back this morning to R47 after some days of R48. With R47 the battery was amazing (4 to 5 hours of Screen On and 1,5 to 2 days with my normal use). With R48 1 day maximum and very less Screen On time.

I will post my impression again with R47 and no other changement :)
[Nexus 5 Original Android Development] Tylog:
You can test following.

Change from Interactive to Ondemand ~ set Thermal from 70 to 60 , rest leave on Stock :)

I test it yesterday and it gives a notable ++ on the Display Time.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Madpiercing:
I haven't tested battery life properly on r48 yet (installed about 10 h ago), i will test properly with the next charge, as i've found that after rebooting to flash a kernel, the first battery run almost always last less, so i use the first battery charge to do benchmarks run only. So far, to me, it doesn't seem to be much worse, but i can't judge it properly as of now.

However i had r47 installed for a while, and yeah it was good. But like i said nothing like the caf revisions; with my standard usage scenarios, which is pretty low use, i could get almost 3 days on the caf revs, and when i tried to mimic an intensive usage i got 6-7 hours of sot.

With my normal low usage and these new revisions i get on average one day less,i charge the phone every 36-48 h, and i sit around 3 h sot per charge. But honestly i happily leave the various bugs and lesser performance of the caf revisions to the past.

The thing is, as long as my phone last around 36 hours, i tend to not care about 2-3 hours more or less idle, because if i have say 30% left, i charge it aniway before going out. So, as a parameter to decide if a kernel is a keeper or not, i look more at the general smoothness of the phone. All the revision after the kernel reboot without caf commits where good in this regards in my experience.

In the end it all comes down to your habits and usage patterns :) use whatever rev you're happy with and i don't see the need for anyone to hate on the people who feel an older version is more suited at them.

The thing is, we are at a level of optimization right now that is almost perfect, so franco can change one thing and maybe the phone gets a little bit better on performance but a little bit worse on battery, or viceversa. But all the latest version are very good, i used them all and i don't see much difference beetween them honestly if i don't painstakely watch my battery reports and benchmarks every hour lol
[Nexus 5 Original Android Development] vijaysivakula:
Compatible ROMs please

Hi,

Could someone please share a list of compatible ROMs? I am a new buyer of Nexus 5 and have installed the latest OmniROM / CM11. Heard a lot about this kernel and would like to know if it is compatible with those ROMs. Thanks in advance.
[Nexus 5 Original Android Development] Tzfardaya:
There's a link in the op of this thread for a FAQ page... Might want to check there... Seems like the type of question that would be answered in a FAQ, right?
[Nexus 5 Original Android Development] choosetobelieve:
Has to be on demard??
[Nexus 5 Original Android Development] californicated:
Wow! r48 is giving me two days of standby with 5h SoT. The best results I've ever seen on my phone. Still smooth as f*ck

Franco, you're a magician ☺

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] OGroteKoning:
You should really try r48...
[Nexus 5 Original Android Development] californicated:
Whooooops! That's what I meant :D

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Enddo:
weird how you say you have more battery life with r48 and others say there is less

ill wait for the coveted 'recognized contributor' to 'shame' some more

I am with you ccab, I have great SoT with r48 too
[Nexus 5 Original Android Development] Tzfardaya:
Different use cases, different scenarios... No two people are going to get identical battery stats from their phones, unless they are using there phones identically, with identical network strength/quality... (meaning the phones practically need to exist in the exact same location)

For some the changes in the kernel code will increase sot/idle time, and for others it will decrease slightly...

Same as gasoline for your vehicle... Two people can have the same car, use the same gas, but get very different mpg... Both change to a second type/brand/mix of gasoline, and ones mpg can increase and the others decrease... Why? Different driving styles..

To make the claim that just because your battery life has improved, therefore everyone else's battery life must improve as well, and that no one's battery life can be reduced, ignores all the other factors that contribute to how long (or short) the battery life is on out phones.
[Nexus 5 Original Android Development] TheLastSidekick:
SOT has been amazing as far as performance is concerned as well. R48 is a sweet spot for sure. Interactive has gotten a bit faster too.

And yeah battery is always going to be different especially now that its summer (Spring actually with summer temperatures) here in the US, phones will get hotter and battery drain will be slightly worse.
[Nexus 5 Original Android Development] Tylog:
Could you please refrain from your references?

I'm

A: too old for such a moronic so things I've done 40 years ago

B: too busy, and

C: not interesiert on such a nonsense

. As you've said, Developers thread, you want the other stick to it, then go ahead with a good example.

Take a minute to read my last TWO Postings , (I explained extra again) in order to clean up any misunderstanding

Thank you and have a nice Weekend.

My words, for one better, for other bad, bad for the other, reasons it may have many. Both perspectives have to draw into consideration :)
[Nexus 5 Original Android Development] Exostenza:
I have been off the forums for a bit and am out of touch with this thread so please forgive me if these have been spoken about.

[MENTION=3292224]franciscofranco[/MENTION]

Since moving over to R48 I have had some really strange issues while nothing else has changed on my phone that I can account for. Firstly, sometimes when I hit the power button to put the phone to sleep I get a black screen with the backlight still on and it sits there until I unlock and relock it. Secondly, I have had problems with charging where it will hit a number (random it seems as last two were 63 and 93) and it just flatlines and won't charge above that number.

Very strange behaviour...

last kmsg
[Nexus 5 Original Android Development] prstorero:
I can't speak for the black screen stuff, but I did notice the same battery issue. Sometimes it capped at 74 sometimes 90. It doesn't happen every day either. Just switched back to stock last night to see if it happens again.
[Nexus 5 Original Android Development] Exostenza:
I would not fault the rom on this as I have never had this problem before and have been running the same rom since I got my phone in November. It is most likely the kernel. I have been running Franco for the whole time as well and have not had this problem until r48. Maybe I'll go back to r47 as I can't head out in the morning with around 60 percent battery. I hope he sorts it soon!
[Nexus 5 Original Android Development] yorici:
Bug has been fixed by faux and me. [MENTION=3292224]franciscofranco[/MENTION] please implement in Franco Kernel! r37 to r48 were flawed by it.

https://github.com/faux123/Nexus_5/commit/3f404a3420918a5093d9f97947a33ed740546b53