yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] aavvaallooss:
There is not such thing than 4.4.2-specific Franco kernel. Correct me if I'm wrong
[Nexus 5 Original Android Development] fbf2201:
He merges commits from new stock kernels, this is kind of version specific, imo. But anyways, there was no new stock kernel for 4.4.2.
[Nexus 5 Original Android Development] theknut:
Please correct me if I'm wrong but I thought Franco merged both the 4.4.3 and 4.4.4 sources. So I guess I can't use those kernel versions. That's why I asked for the last kernel which was compiled with the 4.4.2 sources. I didn't ask for a new one.

[MENTION=4039290]aavvaallooss[/MENTION] & [MENTION=4860519]Tzfardaya[/MENTION]

Way to go...

I've donated twice to Franco plus I bought the app. It would be nice if I could get a serious answer. It's not much I ask for.
[Nexus 5 Original Android Development] Tzfardaya:
Not all the versions have kernel changes... If there were no changes to the kernel in 4.4.3 and 4.4.4, which iirc there weren't, then the current kernel would work with 4.4.2 as well...

As to being too much to ask for... It's seems like such a little thing doesn't it? Getting a serious answer... Well, we think the same about people searching for their own answers prior to posting their questions. . Serious answers need serious effort, from both parties. . Put some serious effort into looking up your own answers (such as searching this thread for 4.4.2), then, if you can't find an answer, (either it's very obscure or fairly unique) feel free to ask. . Make sure though that you outline the steps you've taken on your own so we don't duplicate your work, or so we can correct any errors in the processes you've tried.
[Nexus 5 Original Android Development] franciscofranco:
They were being serious, you can flash r57 on 4.4.2.
[Nexus 5 Original Android Development] sam razzy:
Wow Material design... #androidL and Franco will be the another best combination.
[Nexus 5 Original Android Development] theknut:
They troll linked me to the 4.4.2 stock kernel so they aren't actually serious.

But thanks for your answer. Stupid me stayed on the same kernel the whole time because I thought it wouldn't be compatible. Now I can use the latest on 4.4.2, awesome!

Thanks for your work!
[Nexus 5 Original Android Development] Tzfardaya:
No, you were linked to a search for the stock kernel, all you had to do was switch stock with Franco and search again...
[Nexus 5 Original Android Development] arpitnathany:
No we don't as of yet know where the problem is the first time this happened I was on complete stock no root no mods just stock. I rooted and installed fku to help diagnose the issue that's all. Anyway don't worry I am sure well find the cause of the problem one day.
[Nexus 5 Original Android Development] Red5:
Looks like I'll be retiring on r57...Unless Franco decides to push r58 tonight.
[Nexus 5 Original Android Development] simonarturo:
R58 test image is already up. Have been running it for most of the day.
[Nexus 5 Original Android Development] sir*mez:
battery is waaaaayyy better with test-r58. thank you fraco for making a change to save battery.
[Nexus 5 Original Android Development] Technecium:
I'm not sure that max_cap is responsible for the lower battery usage. Quick explanation...

The results below are from a 2 minute data transfer from my NAS my phone with the screen off.

2.27 GHz (): 46 s 31.2%
1.96 GHz (): 36 s 24.7%
1.73 GHz (): 18 s 12.4%
1.57 GHz (): 13 s 9.0%
1.5 GHz (): 10 s 7.0%
1.27 GHz (): 4 s 3.0%
1.19 GHz (): 8 s 6.0%
1.04 GHz (): 2 s 1.5%
960 MHz (): 1 s 0.8%
883.2 MHz (): 1 s 0.8%
729.6 MHz (): 0.6%
652.8 MHz (): 1 s 0.8%
422.4 MHz (): 2 s 1.5%
300 MHz (): 1 s 0.8%

It looks as if the max_cap isn't actually taking place.

Can someone else test and confirm. This is on t58.

Thx.

EDIT: Just to follow up. Another test from a 1hr+ data transfer on my own personal build. Note the screen on time and how much time collectively accumulated at freqs above 1GHz. FYI: This is my own custom build and the max_cap is 96000.
[Nexus 5 Original Android Development] franciscofranco:
You're absolutely right. Just calling cpufreq_within_limits wasn't enough (duh!). I just made it work properly. I thought it was working because the log said so, but then cat scaling_max_freq showed another history.

I'll push the code in a sec, just cleaning it up.

Edit: pushed the code, you can pull it and try.
[Nexus 5 Original Android Development] Technecium:
Will do shortly but first....

Previously, I had said that interactive was responsible for the higher battery drain compared to ondemand. We have unknowingly disproved that. The bbs results show that. 11-13% loss over 6-8hrs is right back where it was before the new code was added to interactive.

So something else was responsible for the 20-30% loss I was experiencing before t58. Either another app/service was busy in the background or other t58 commits have helped.

Either way I think 1GHz might be too low. I can only think of a few things people do when their screens are off, listening to music, download/uploaded/copy related processes and screencasting.

From the bbs results you can see the cpu wanted 1.2GHz for a fair amount of time. 1GHz is more than enough for audio but it might impact disk and network processes.
[Nexus 5 Original Android Development] franciscofranco:
Yeah sure, but I've merged a gazillion commits for the apps processor secure driver (QSSECOM) and for the crypto driver that the apps processor uses. There are a couple commits with optimizations and support for suspend/resume of both qssecom and crypto layers.... maybe that helped.

We'll figure out about the optimal freq later!
[Nexus 5 Original Android Development] Technecium:
I compiled with the latest commits and it is definitely working now.
[Nexus 5 Original Android Development] franciscofranco:
Yep, that it is. What's the stats with 5m of music?
[Nexus 5 Original Android Development] Prattham:
can i flash this on the latest mahdi rom??

if someone helped you...don't say thanks just hit the thanks button
[Nexus 5 Original Android Development] franciscofranco:
Because #leak again (the trash can icon is too small, won't be like that, don't worry).
[Nexus 5 Original Android Development] granets:
I have terrible battery life when listening to music with screen off... Lost around 10% in 1h

Using latest test image.
[Nexus 5 Original Android Development] franciscofranco:
Yes, very helpful... you can use ondemand for now if you're an heavy music listener until we finish rolling out some improvements as you can read in the last pages....
[Nexus 5 Original Android Development] granets:
Sorry, I'm at work. Will upload some images ASAP
[Nexus 5 Original Android Development] sandeep.kodeti:
Yep u can use ...and its works perfect
[Nexus 5 Original Android Development] The Gingerbread Man:
The area you high lighted your radio (phone signal) went to ****. I think that's the cause of your drain
[Nexus 5 Original Android Development] granets:
You might be right. It's strange though... Had the phone in a drawer in my desk playing music in my earphones. No idea why mobile signal went to sh*t then... Nothing is different from every other day.
[Nexus 5 Original Android Development] The Gingerbread Man:
Well if the device is in a closed drawer in a desk that's one more object between the the phones antenna and the sky where the signal is picked up. Depending on the material the deal is made from it could be harder for signal to get through metal / wood that plastic for instance. But look at your stats picture again. The area with drained you high lighted your signal bar went yellow which is bad. Red is no signal. White is average. Green is good. Your sign went to the yellow area at that time
[Nexus 5 Original Android Development] yeiyei0891:
What improvements or changes has the new test image?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] simonarturo:
Lol, I knew it was a good decision not to post about my improvements to battery life with the test image until some confirmation came this way.

I'm sure that it might be placebo but I woke up to the best screen off drain time I have had in a long time. I went to bed with some music with a 30 min timer and then slept soundly for about 8 hours. In the morning got a bunch of mails and instant messages from friends and work and it only drained 5% total. That's with music on and everything!
[Nexus 5 Original Android Development] ironjon:
https://github.com/franciscofranco/hammerhead/commits/nightlies
[Nexus 5 Original Android Development] cobyman7035:
in 17 hours of standby with BT on but not using much, i lost like 6% and deep sleep was around 97%, thats normal?i figure someone else on FK could prolly lose only like 1% during that time?
[Nexus 5 Original Android Development] Technecium:
It's all good! I thought, "Damn, this new 1GHz max is amazing! 11% 6-8hrs woohoo! " Then I realized it wasn't active.. hahaha! You're certainly not experiencing a placebo.
[Nexus 5 Original Android Development] simonarturo:
That is actually pretty good. 6% for 17hrs of standby, that's 0.35% per hour.

I hope you are not being ironic here....
[Nexus 5 Original Android Development] Red5:
New r58 test kernel coming soon?
[Nexus 5 Original Android Development] Tzfardaya:
What's the eta for the eta announcement?

And my opo doesn't have a scan since leaving cali... :(
[Nexus 5 Original Android Development] aavvaallooss:
Offtopic!!! ;)
[Nexus 5 Original Android Development] Tzfardaya:
So is yours.... :p

So what?
[Nexus 5 Original Android Development] Red5:
I get mine today. :highfive:
[Nexus 5 Original Android Development] amphi66:
That would be "opotopic", to be correct!
[Nexus 5 Original Android Development] Technecium:
Wrong thread but I'll leave this here for you..
[Nexus 5 Original Android Development] Technecium:
Red, I'm glad you know I'm just messing with you.

Back to kernel stuff...

https://github.com/franciscofranco/hammerhead/commit/8952b1150def931175bf5f9f0b88dfe76a1fc76a

This looks very promising. Should result in better scaling, correct? Do you suppose this might explain why the last test I did resulted in more time at 300mhz?
[Nexus 5 Original Android Development] Tzfardaya:
I might... If I can figure out dhl's automated phone system....
[Nexus 5 Original Android Development] franciscofranco:
:good:

Yes I can build it now. Need to ssh with my GF's computer, not home at the moment. Should be there in 5m tops.

EDIT: it's there.

I thought that making the calculation based on cpuinfo.max_freq would be good, but I guess the calculation goes over the board with that. I guess it's more fair now based on the current max_freq instead of the 3GHz hard cap. We'll see but it looks ok now!
[Nexus 5 Original Android Development] Red5:
Thank you!
[Nexus 5 Original Android Development] The Gingerbread Man:
I wonder if its worth removing the over clock speeds? Do we really need them? Does anyone actually overclock with an already very powerful CPU?
[Nexus 5 Original Android Development] Tzfardaya:
Mo' PAWA! always want MO' PAWA!
[Nexus 5 Original Android Development] granets:
I see no point. I'd venture and say that the phone is actually bottlenecked by the slow memory, and not the CPU.
[Nexus 5 Original Android Development] tlrsax54:
I tried OC once and even just the slightest increase gave me a reboot :( but the phone runs great at stock speed so its whatever lol
[Nexus 5 Original Android Development] Tzfardaya:
Yeah, even Franco admitted when he added the op ability that we would need to raise the voltages of the op steps for stability..
[Nexus 5 Original Android Development] franciscofranco:
Overclock = because users.
[Nexus 5 Original Android Development] bjoswald:
I think it's cool that they're in there because I hate having things hidden from me. I don't use them, though. The phone flies fast enough as it is!
[Nexus 5 Original Android Development] 5FOOTER:
Voltage= because of users?

Great battery life = because of franciscofranco

Sent from my Nexus 5
[Nexus 5 Original Android Development] combatdeity:
Liking your take on material.
[Nexus 5 Original Android Development] Tzfardaya:
future -Overclock & -Undervolt = because L.A.R.T.'s banned by society
[Nexus 5 Original Android Development] krystyuc:
As a wise man sayd "However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance. By Chainfire"

That's the only thing people whant OC :)
[Nexus 5 Original Android Development] Binary Droids:
To anyone having problems where your device doesn't go back to max freq after thermal throttle or your max freq is lower than what it should be after boot, make sure you're using SuperSu. I tried out Paranoid Android & noticed that my max freq would "jump around" after reboots. Sometimes it would be 1958 or 1574 or 1190...

After a little digging I noticed that the power.msm.8974.so & thermal-engine-hh files were not being disabled like they should be. Paranoid Android uses Superuser for root & doesn't play nice w/ franco.Kernel. So I flashed SuperSu, revoked my apps root permissions from Superuser, disabled all root access from within Superuser, and reopened all my root apps granting them access with SuperSu instead.

As soon as I did that the two files were disabled like they're supposed to be & my max freq has been 2265 across 5 reboots now. Will try thermal throttling to make sure, but [MENTION=3292224]franciscofranco[/MENTION] disables those files for a reason.

If anything, at least check the files to make sure they are being disabled. One is located at /system/lib/hw/power.msm.8974.so (it should be power.msm.8974.so.bak) and the other one is at /system/bin/thermal-engine-hh (should be thermal-engine-hh.bak). Hope this helps anyone having problems...

[MENTION=4788211]Aerowinder[/MENTION] [MENTION=2185591]sjknight413[/MENTION]

Nexus 5 - Paranoid Android - franco.Kernel
[Nexus 5 Original Android Development] SynnyG:
OC is really useless on this phone, the SoC is fast enough on stock frequencies ! Ok on some old phone it can be usefull but with the Snap 800 no, just for getting 1 or 2 more points in antutu...
[Nexus 5 Original Android Development] Renton91:
Hello everybody, I tried to install this kernel right now and since I did it (about 20 minutes ago) I'm having very frequent reboot especially when I try to increase CPU frequency.

I use PA 4.44, Xposed Framework and Performance Control to set CPU (actually I'm trying to use it but I can't do any change withouth it reboots by itself, so CPU settings are default so far yet).

Can anyone give me a hand to understand what is going on on my N5?

Thank you in advance.
[Nexus 5 Original Android Development] myfluxi:
policy->max is always preferred due to a) user settings, b) throttling. Unfortunately there is no way to know policy->min reliably but honestly, do we have to give a...?

I'm not sure if we want Stratos' "correct" formula on mobiles. Maybe we'll find a fair weight for freqs that does not lead to terrible behaviour as with all those over-the-top google/caf calculations.
[Nexus 5 Original Android Development] franciscofranco:
Increase the frequency to what?

Of course we want policy->max, I terribly didn't account for that user setting/throttling thing when applying the code.

Well anything is better than what Google/CAF did to be honest. The way you're doing right now is very close, if not similar, to Ondemand, which is actually fair.
[Nexus 5 Original Android Development] Renton91:
It reboots everytime I try to set it on 2880 or more, so now I'm using 2572.

Why does this happen?

I apologize for my lack of knowledge, I've had this phone few days ago.
[Nexus 5 Original Android Development] franciscofranco:
Because you're overclocking... and your device does not handle that much overclock...
[Nexus 5 Original Android Development] WettbackMartyr:
It's amazing that in the past 50 pages or more no one has complained that they have a problem due to over clocking....yet as soon as someone brings up over clocking possibilities, SOMEONE ends up with a problem from over clocking!

People please...if you don't know what the hell your doing to your device just leave it be. I beg you. Or, at least ask someone what will happen if you do it before you do it. I swear it's like watching a child with a hot stove in here sometimes.....
[Nexus 5 Original Android Development] Renton91:
It's amazing how just a question can make people go crazy.
[Nexus 5 Original Android Development] Technecium:
There is MSM_CPU_FREQ_SET_MIN_MAX and I noticed it's not set in franco_defconfig. Would that be something useful to make the calculations more reliable?
[Nexus 5 Original Android Development] franciscofranco:
Nah, that's just a legacy define.
[Nexus 5 Original Android Development] The Gingerbread Man:
Honestly I think the only report of someone having a bad time with over clock in this entire thread
[Nexus 5 Original Android Development] 5FOOTER:
Its not the question that makes people crazy its the fact some do not do any reading or just flash stuff or change settings that they don't understand. Then without trying to figure it out they demand an answer and a fix. I don't have time to learn how to code or what not,but I take my time and read what I'm flashing. I guess most of us are grown ass men/women and feel its time to take you off the tit and let you start feeding yourself.

Rant over....

Sent from my Nexus 5
[Nexus 5 Original Android Development] Technecium:
OP has a point though. Mention something janky and folks come out of the woodwork. I think it's a case of 99% of the users either don't notice or look for problems. Then someone asks or mentions an issue with the flux capacitor and all of a sudden everyone's flux capacitor is acting funny!
[Nexus 5 Original Android Development] WettbackMartyr:
You're probably right. I just wish people would search and try to resolve issues on their own instead of asking first thinking later. And if all else fails try stock settings. If it works on stock it usually isn't broken.
[Nexus 5 Original Android Development] Tzfardaya:
Speaking of flux capacitors, mine started flashing red and blue last night... And for some reason there's a British police box in my living room now... Don't think the two issues are related though...
[Nexus 5 Original Android Development] rbrenart:
My battery life is what I'd call schizophrenic. I'll go from .5%/hr overnight to 3.5%/hr the next night. I know Franco says that's not the kernel, and I believe him, so please forgive my OT post - what's the go to resource for figuring this out?

I have GSAM Battery Monitor with the root extension and App Sucker tells me that I have 570 AlaramManager wakelocks since last night, and 51 ActivityManager-Launch and and and... but I don't know what's necessary and what's bad. Not expecting this thread to become a battery helper thread, but would be grateful if you all could point me in a useful direction since this has been by far the most helpful thread I've ever been a part of on XDA.
[Nexus 5 Original Android Development] Tzfardaya:
One extreme way to check, is to take a nandroid of your working system, factory reset, then add a couple apps each night to see which are throwing unnecessary wake locks...
[Nexus 5 Original Android Development] rbrenart:
The problem with that is they don't throw them every night. So I'd need to let it go for a week per set of apps and I just don't have that kind of commitment to the "problem".
[Nexus 5 Original Android Development] Tzfardaya:
Fair enough..
[Nexus 5 Original Android Development] AGiLiT:
Alarm Manager is called by many apps. To see which ones are most active:

adb shell dumpsys alarm > AlarmDump.txt - this will give you a log file.
[Nexus 5 Original Android Development] rbrenart:
That is awesome, thank you.
[Nexus 5 Original Android Development] akash3656:
For this phone, I'd say this behavior is normal. I had wakelocks and have eliminated them, still battery life can be epic for one day and plain sh*t the next day. Happens on every kernel and ROM (stock too). Even after removing all apps and starting fresh with limited apps, this issue still remains present.
[Nexus 5 Original Android Development] norwoodesteel:
xposed is not compatible with PA
[Nexus 5 Original Android Development] Tzfardaya:
Since when?
[Nexus 5 Original Android Development] qu4nd:
It's more likely that PA doesn't officially support xposed.
[Nexus 5 Original Android Development] norwoodesteel:
Since forever read the xposed OP
[Nexus 5 Original Android Development] Tzfardaya:
I never used xposed, but I do recall others in this thread using the two together... It's my understanding that no rom supports xposed issues...
[Nexus 5 Original Android Development] Aerowinder:
Using Superuser, my files have not been renamed. I have now put the throttle back to 55c, renamed those files manually and rebooted. Time will tell if that was the issue. But it does explain where the phantom 1958MHz throttle was coming from.

[MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] akash3656:
Well sorry if I sound like I'm ranting. Use superSU plox. Superuser by koush just doesn't cut it ever since android 4.3

It used to be decent back in the 4.2 days. Now it's just some legacy software that's being pushed into mainstream ROMs. I guess this is exactly why some ROMs come unrooted these days. No root is better than broken root which causes headaches for everyone.
[Nexus 5 Original Android Development] bjoswald:
I've been supporting Chainfire since before I got this phone, but never knew that Koush's root was messy. Still love CWM Recovery though.
[Nexus 5 Original Android Development] Aerowinder:
I've always preferred SuperSU. Always used that when I was on stock ROM. I only use Superuser because it comes baked into most custom ROMs. I did not realize it was a problem. I've never had any issues with it before. Is it more Koush abandonware?
[Nexus 5 Original Android Development] dustinraditya:
Hi folks I'm using Franco r57 and using trickster mod to control it. Could anybody share the best setting for battery life and temperature? My temperature goes up to 47C in moderate use
[Nexus 5 Original Android Development] Technecium:
You won't get a definitive answer. We all use our devices differently. I'm on wifi 99% of the time. I never use gps, nfc, and hardly ever use mobile data or bluetooth. I have only have 102 apps. No games, so social media, blah blah.

Another person might use mobile data and gps all day and play games, social media app etc connected and updating, tweeting and twerking and playing music through bluetooth.

The answer you're going to get in here is, and it is correct, "the settings that suit your usage."

EDIT: General rule of thumb... If you don't use it, turn it off. If you don't use it often, use an app like Tasker to automate it. If you use it all the time, leave it on.

EDIT: You'll also get some rhetorical questions. :D

| |

| |

| |

V
[Nexus 5 Original Android Development] mpgrimes:
Who cares about temperature, it's still well within safe zone. I'm using the default settings, great battery life. And my temp hits that often, until around 53 after a reboot. And thermal throttle doesn't kick in till around 70. Reboot around 100
[Nexus 5 Original Android Development] simonarturo:
Anyone running the latest test image with the lowered screen-off frequency fix?

Any impact on battery life? Performance?
[Nexus 5 Original Android Development] Technecium:
I'm using it. It's really too early to say. There are some inherent positives to a lower freq with the screen off. There are some potential negatives.

Positives: Processes running in the background while the screen is off will never go above 1GHz. Since many don't require more than 1GHz it can save battery by not needlessly jumping to the max freq.

Negatives: Processes that should be allowed or actually benefit from using a higher clock speed, such as copying a large file might, and I stress might, get slowed down.

All in all, I would say give it a try. The changes only affect the device when the screen is off.