yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] combatdeity:
I can confirm the phone doesn't seem to like staying at 300 mhz as it did before, now it tends to bounce around in the lower frequencies.

Perhaps this prevents spikes to higher frequencies from being more frequent?

Just reporting what I have observed, hopefully this is by design.
[Nexus 5 Original Android Development] californicated:
Frequencies are bouncing, but battery life is as great as the performance :good:
[Nexus 5 Original Android Development] msgfromside3:
+1

I don't care if the frequencies are bouncing around because I am seeing the fantastic battery life. 1.6%/hr for 5.5 hours - never had this before. With the comparable screen-on time, I normally got 3%/hr. It seems wake-up time is reasonable vs screen-on time (meaning I still see much longer wake-up time than screen-on time).

FYI, this is even better than with location off to kill the stupid nlpwakelock.

Good job!!!
[Nexus 5 Original Android Development] franciscofranco:
Yes. Basically make the phone use a higher frequency for a certain type of action/job/thread/whatever, finish whatever it has to do faster, then scale back down faster too.
[Nexus 5 Original Android Development] franciscofranco:
Yes. I merged the same patch on my One Plus One and the battery life is even better. 90% left with 1h screen on time with 4G. Monster.
[Nexus 5 Original Android Development] Ryrynz:
Should 300mhz be getting more action when just sitting on the desktop? R55 prefers 345 and 422. No complaints everything is super smooth. Just seems weird.
[Nexus 5 Original Android Development] TheLastSidekick:
Possibly a bad question here but, which device is your favorite between the one Plus one or Nexus 5?
[Nexus 5 Original Android Development] franciscofranco:
One Plus One, bigger display, faster due to the better and more modern SoC all-together and the battery life... don't start me on that one. But I use the N5 everyday for development.
[Nexus 5 Original Android Development] Technecium:
I recently detect a change in the direction of the kernel design. It seems that the balance of battery life and performance has changed. I believe in the past the idea was to get as much uptime as possible without affecting performance. I was getting nearly 20hrs consistently. Recently though I sense that it is no longer about getting as much uptime as possible, but instead getting a reasonable amount of uptime, maybe 8-10 hrs.

Most of us can get to a charger every few hours or plug in for a few minutes here and there so getting 8-10 hrs works out ok for most people.

Is that the case?
[Nexus 5 Original Android Development] Tzfardaya:
It could also be that by modifying the kernel to get those 20hr up times, performance was being sacrificed, and the pendulum is simply swinging back towards improving performance again (while minimizing battery life loss)

If one wanted to, one could probably tweak the kernels settings to get several days usage out of the n5, extremely low back light, severe underclocking, locking the data radio to 2g, etc etc but the phone would perform like crap...

Or one could go the other way, pure performance, lock the CPU to higher freqs, full brightness on backlash, lte radio, have the phone fly but only last a handful of hours.

The trick is to find the balance that provides a smooth experience in performance, yet still lasts sufficient time to survive a day of normal usage.
[Nexus 5 Original Android Development] franciscofranco:
It's impossible to have a 50% decrease in battery life by the changes I've been pushing. For example Services 5.0.77 frakked the battery life, the 4.4.3 radio frakked it as well. Since 4.4.3 I've seen a tremendous battery life hit and I have absolutely no idea why.

The balance is still there you can see my commits and figure out that I've been increasing things there, decreasing there (specially governor tunables). This is a cat & mouse game - Android is SO broken in terms of how it handles wakeups/wakelocks that anything can easily rape your battery regardless of the kernel you're using. For example that Always scanning Wi-Fi option is so dumb that it actively scans every Wi-Fi channel, thus rapping your battery life by no reason. From what I heard in the I/O they are writing a new Wi-Fi HAL to abstract this easily and make it only scan channels one by one. It's just an example on how frakked Android is towards battery life. There's other reasons of course, but this is what I remember. One can only do much with Kernel tweaks/changes/whatever.
[Nexus 5 Original Android Development] RobbieL811:
I am trying to get one myself right now, but damn if they didn't make it IMPOSSIBLE to buy one! I have no clue where I can get an "invitation". I guess I'll probably get stuck buying one from some ****er that bought the device & marked it up $100. SOOOOOOOO screwed up how that works man! Pisses me off!

Sent from my Nexus 5
[Nexus 5 Original Android Development] Technecium:
Thanks for the response. I love the code and use it as a base. I just wanted to check that your philosophy hasn't changed. I fully agree with you that the governor/wakelock relationship is the issue.

I do have to disagree with you on, "It's impossible to have a 50% decrease in battery life by the changes I've been pushing." The latest commits to iterative seem to favor processes that require shorter time (shorter wakelock) to complete. For example, the average consumption of something like a browser or facebook that asks for scrolling and rest, download/upload data and rest, etc. may overtime use the same or less battery because the governor can select an appropriate freq and complete faster.

However something that has a consistent wakelock like audio, video or skype, will most likely not benefit. I'm pretty sure we agree that the cpu does not sit at 300MHz as much as before. Take audio playback for example, from my experience 8hrs of audio @ 300MHz comes out to about 20-25% loss. If the cpu is running higher, say 345-729MHz there is going to be a big difference. The governor doesn't know what the wakelock needs.

Like you said, cat and mouse, but it more like, you can please some of the people some of the time but not all the people all the time.

Thanks again for taking the time.
[Nexus 5 Original Android Development] franciscofranco:
Hopefully they'll have enough stock soon to sell it for the masses.

I think playing with timer_rate will help balance things out now that the governor is much more aware of load changes and scales accordingly. Try this (not sure how this will play out, I'm booting a Kernel with this as I type):

echo 60000 500000:40000 1500000:30000 2000000:20000 > timer_rate_path

Edit: the timer rate above works great in reducing unwanted ramps during non-load times. Removing the 342MHz step also helps. Test boot.img ships with these.
[Nexus 5 Original Android Development] Zyphur:
5/10 my N5 won't play the ringer, only the vibe. Sound works on everything else though.

Anybody have any ideas on what it could be before I just rma it?

And r55 hasn't given me any issues thus far!
[Nexus 5 Original Android Development] blackt5:
Flash 100% stock with images then see what happens. Don't load any backed up apps and see what happens. Don't forget to copy all your photos/music/downloads to your computer first, your gonna lose it all
[Nexus 5 Original Android Development] fatspirit:
Check ringer volume (:
[Nexus 5 Original Android Development] EnricoTFYKD:
[MENTION=3292224]franciscofranco[/MENTION] I have a little bit of a "dream" request here: it looks like the guys working on the CM kernel were able to enable the ULPS mode for the display which is basically the panel self-refresh (the so-called "GRAM" feature of the G2, more or less).

If it was possible to enable that feature also in your kernel, that could probably give us some more battery life. However, I don't know if this is doable or not. The commits I'm talking about are related to this one: https://github.com/CyanogenMod/andr...mmit/a170c12ef9f3880d8f41d7865400a7d23596f685
[Nexus 5 Original Android Development] Bluewall:
Yeah, I had the chance to do a little testing about this and it *seems* to improve my battery.
[Nexus 5 Original Android Development] Technecium:
Excellent! Did you specifically suggest using echo for a reason? I tried to enter the settings in FKU with SwiftKey but I'm unable to insert a space. I don't have any other soft keyboards installed so I can't check if it is FKU or SwiftKey.
[Nexus 5 Original Android Development] franciscofranco:
It's not as easy as enabling that option... it requires a massive upgrade of the video subsystem which we're not prepared for.

TL:DR won't happen. Even in the One Plus One using the latest Qualcomm Kernel tree that feature is not really mega stable. I talked with Cyanogen couple days about it when we met here in San Francisco and he confirmed it to me. Nevertheless I think the G2 has a separate controller/chip to handle that stuff.

Probably FKU bug. Just echo it or use the latest boot.img in the tests folder.
[Nexus 5 Original Android Development] TheLastSidekick:
There are simply too many factors that alter battery life to chock it up to just a kernel or ROM.

1. Radios

2. Coverage by your carrier

3. 2G/3G/LTE usage

4. ROM

5. Kernel

6. Wakelocks

7. Environmental temperature

8. Screen brightness

9. Misc settings like NFC, WiFi Scanning Always on

10. GPS

11. Quality of SoC during manufacturing and other hardware

12. Vibration strength

13. Phone volume

Again, the list may not be even remotely close to complete but it's an example. I've noticed this too, but that's with all Android phones regardless of kernel or ROM. There's always that one time you'll get 7 hrs of screen time for whatever reason and never manage to get to 6 hours ever again. Regardless, you would be hard pressed to find yourself under 4 hours of screen time no matter what you do.. Unless you're running performance governor constantly ;)
[Nexus 5 Original Android Development] Technecium:
Cool, then consider my last post a potential bug report.

Here are the result from BBS r55 vs test boot.img both default FKU settings. This is airplane mode + 8 mins of only audio.
[Nexus 5 Original Android Development] EdgA#1:
USB OTG don´t work on PA ?? with stock PA kernel it works
[Nexus 5 Original Android Development] RobLudo:
Just tried with r55 and stock 4.4.4 and it works.

Do you use stickmount? (I don't know if it's necessary on custom Roms).

By the way, it's possible to mount NTFS drive? Long time ago I read about putting a ntfs-3g binary in the sdcard folder, then stickmount would use it.

I tried as soon as I bought my n5 (December) and I don't remember if it worked, but nowadays it doesn't.
[Nexus 5 Original Android Development] Technecium:
In one of the two interactive commit comments it states, "In case of equal distance between 2 frequencies, it will select the greater freq."

How often do you suppose this happens? Would it be worth it to select the lower freq?
[Nexus 5 Original Android Development] shreddintyres:
The binaries for that NTFS and Exfat need to put in the /system/bin directory and set to permissions 755 (-rwxr-xr-x) to be properly used by stick mount or at least that has been my experience for some time now

- cheers
[Nexus 5 Original Android Development] jordirpz:
In the last r-56 test, i had reboot, and after doesnt boot the phone.

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Not necessarily, I rarely get even 3 hrs sot, even on stock Franco settings with my usage. (2.5hrs sot over 8-10hrs on battery time) and I never use the performance governor.

But, because I have such heavy app usage, I haven't noticed as much of a battery loss due to Android system changes (maybe 30 minutes of sot lost)

My largest battery drain while at work (other than the obvious screen) is the late radio, I could probably etch out another 15-30 min sot by dropping to the 3g radio, but it's too much of a hassle to keep switching it back and forth, and I haven't found a way to get tasker to automate this switching. Perhaps [MENTION=3292224]franciscofranco[/MENTION] can find a way to remotely change the preferred network type. ;)
[Nexus 5 Original Android Development] kv1dr:
For me it doesn't work on PA, but I didn't know it worked with stock PA kernel.
[Nexus 5 Original Android Development] RobLudo:
Thanks, works!
[Nexus 5 Original Android Development] Arstoien:
Regarding Tasker and preferred network mode: you need custom rom which supports it (any rom with 3g/4g toggle) and secure settings. Mine works fine and I sometimes use Tasker to toggle between 3/4g.
[Nexus 5 Original Android Development] Tzfardaya:
Yeah, I forgot about the custom rom way... I use stock.. :P, so need to find another way.. ;)
[Nexus 5 Original Android Development] Arstoien:
That would be giving up ART and using Xposed (GravityBox). No other way as far as I know :\
[Nexus 5 Original Android Development] Joomlar:
I am on stock 4.4.4 and elementalx 1.0.0 kernel. How i can flash franco? Is it just via recovery or i need backup to stock kernel and then flash franco? Which kernel is best for battery life, elementalx or franco?
[Nexus 5 Original Android Development] Technecium:
To eliminate any possible issues, restore stock via advice/howto from the elemental thread. if all goes well, flash img via fastboot/flashify/fku or zip via recovery.

battery life is all about how you use it. you're going to have to try it out with your normal routine and see.

good luck
[Nexus 5 Original Android Development] tylerdurden83:
Clearly I agree with you on that. I just wanted to report that while under kitkat I couldn't get past 3 hours sot, maybe a lil bit more, with the stock kernel, with L the situation is radically different.

This is with the L preview, all the apps that also ran before flashing L, most of them are also not updated to take advantage of the new scheduler api, so maybe we are in for a treat with L.
[Nexus 5 Original Android Development] Edge330:
Very stable battery with r54.

Wifi and mobile data always on.
[Nexus 5 Original Android Development] Rapper_skull:
I noticed a big improvement in battery life with screen off with r55.
[Nexus 5 Original Android Development] K Rich:
Thanks Franco!! R55 is awesome!! Always appreciate your work, time, and patience.
[Nexus 5 Original Android Development] nickmv:
I experienced quite the opposite with the L preview. My battery drained really fast, and no matter how many reboots, cache redbuilds, etc that I would perform, the battery would always be >60% dominated by a "Miscellaneous" item in the Battery menu. Was pretty disappointing.

Overall I liked the L preview, but got tired of it enough to recover/reflash my 4.4.4 setup, and am glad I did. There's a lot of work left to do for Android L.
[Nexus 5 Original Android Development] Tzfardaya:
as much as I don't like quoting myself... I dislike repeating myself unless absolutely necessary so.... :p but it was in another thread so...
[Nexus 5 Original Android Development] aeroseek:
This is in regards to setting the ZIP download path in FKU 11.5 (358). Was this resolved and I missed it? Still can't get it to set. Haven't found any discussion about it. Just wondering.
[Nexus 5 Original Android Development] lesp4ul:
I'm using PA 1july + Test 55 also stock PA, it works with this app

https://play.google.com/store/apps/details?id=wired.usbotg

But i only tried FAT32 drive.
[Nexus 5 Original Android Development] franciscofranco:
The chance for that to happen is so dim that it's not worth to change it. Anyway thanks for the time in state test in your last post, I think the changes on r56 test image are sufficient to counter balance the highly responsive governor load changes. Please keep testing and providing amazing feedback!

I've fixed it on my local build, will push today.
[Nexus 5 Original Android Development] antypas:
ULPS is not by any means the GRAM/Self refresh technology. It relies on it but it is a different thing.

[MENTION=3292224]franciscofranco[/MENTION] , [MENTION=4594696]EnricoTFYKD[/MENTION]

Nexus 5 HAS a MIPI command panel. What that means is that IT IS a self refresh panel WITH GRAM. Just like the LG G2's

ULPS is another -optional- feature which further reduces power consumption and it is not available in the G2 yet (haven't checked their kernel sources but it is a fairly new tech so...)

The proof of PSR (Panel Self Refresh) is, besides the Anandtech review, these three commits:

1) The kernel supports Self Refresh (aka command mode) panels: https://github.com/franciscofranco/hammerhead/commit/ea3fd87529aeedcc9502e71d47bce407c159d5c8

2) The Nexus 5 panel is a command mode one:

https://github.com/franciscofranco/hammerhead/commit/c3140b56b4d01d06e98dca1f376a84334618940b

https://github.com/franciscofranco/hammerhead/commit/5dc5fdb3f342e609029d0b00c260ea12478dd9b7

Both of these JDI panels are command mode panels, they mention it in their description. The self refresh thing is transparent and always enabled...
[Nexus 5 Original Android Development] franciscofranco:
All true.
[Nexus 5 Original Android Development] ToMmY_hun:
I'm still experiencing this deep sleep mode problem with other custom roms too. Only the Purity rom worked fine with franco kernel. With c-rom and mahdi rom the phone stucks in deep sleep mode randomly.
[Nexus 5 Original Android Development] The Gingerbread Man:
*******s to that, this is a game for 'real' men https://www.youtube.com/watch?v=gq-pTwyU8c8&feature=youtube_gdata_player take particular notice how they don't roll around in agony unlike their soccer / football counter parts do at the slightest bit of contact. The hits they take and dont wear vagina armour like the american football players do. Check out Chris Aston's eye at the end of the clip, he had a good game! Although that video doesn't really show it England gave New Zealand (world no1) a good run for their money on Saturday.
[Nexus 5 Original Android Development] mythenmetz:
'real' men... what's 'wrong' with you?
[Nexus 5 Original Android Development] The Gingerbread Man:
Probably many many things
[Nexus 5 Original Android Development] alanwyl:
Hey Franco userspace stuff can be modified with a root app, I won't suggest which.
[Nexus 5 Original Android Development] digweed4me:
made my nexus 5 noticebaly louder.

http://xdaforums.com/showthread.php?t=2532788
[Nexus 5 Original Android Development] franciscofranco:
Sure but that modification requires to parse the xml, then modify the value, then make the user reboot to apply the changes. Seems cumbersome to me.
[Nexus 5 Original Android Development] franciscofranco:
Ok so what? Congratulations :cowboy:
[Nexus 5 Original Android Development] Skinpipe:
i have been experiencing audio stutters listening to spotify using stock settings on r13 i have tried increasing suspend frequency but it didnt help at all but what made a difference but did not fix the issue was raising min freq=729600 and also suspend freq=729600. i know its not ideal but its as if the cpu polling from min freq to suspend freq or any freq inbetween those is causing the stutter. i have tried other frequencies but its as if thats the sweet spot.

aside from that my battery life is so good its offensive to my work mates so thanks franco.
[Nexus 5 Original Android Development] caribouxda:
You said it; "real" men;)
[Nexus 5 Original Android Development] Rhatfield25:
Not undervolt profiles, but clock speed profiles. Would I just set the ondervolt values with FKU and continue to use set CPU for my clock speed profiles?

Thank you for the response
[Nexus 5 Original Android Development] franciscofranco:
I don't have any stutters at all, I listen to spotify all day. I remember something similar on Mako when it was launched. I'll see what I can dig.

There's something called PerAppModes on FKU, you should take a look.
[Nexus 5 Original Android Development] zephiK:
Android 4.4 KRT16S coming, https://groups.google.com/forum/#!topic/android-building/o70T70DOals
[Nexus 5 Original Android Development] Savant:
Nice been looking forward to it.
[Nexus 5 Original Android Development] shaker2k:
With cataclysm rom. WOW! :thumbup::beer:
[Nexus 5 Original Android Development] franciscofranco:
By the way I fixed the Antutu panic doing a little bit heavier throttling. Heavier as in sooner, but its less steep in throttle steps.
[Nexus 5 Original Android Development] franciscofranco:
Oh ****, Flo, Grouper, Mako and Manta Kernel sources are up... nice timing as I needed to sleep today -.-
[Nexus 5 Original Android Development] NYLimited:
You still can't do this in your sleep? :D:D:D

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 5 Original Android Development] franciscofranco:
No :crying:
[Nexus 5 Original Android Development] m3lover1:
My Swedish coworker was screaming his butt off at work today listening to the game. I'm not a football fan, but I was rooting for Portugal because of Franco! :P
[Nexus 5 Original Android Development] The Gingerbread Man:
Nexus 4, 7 & 10. I was hoping for an OTA fix for when the cameras won't load on nexus 5. It's highly inconvenient to need to reboot to take a photo. Huge errors going on in log cat when it happens too. Hopefully its being worked on.
[Nexus 5 Original Android Development] DesertVelo:
I have not experienced any sleep issues with Carbon or OMNI ROMs. I always seem to head back to OMNI which I have been using fk since it was available for the N5. Give a try, you may like the experience.
[Nexus 5 Original Android Development] TheLastSidekick:
I myself use Rastakat and FK is stable as hell with it. But that being said, you can't get more stable than stock 4.4.4 with FK. For all of you having trouble, try that first.

Seeing a stupid comment on Google Play about an app you love and marking it as "spam". You've done it too.
[Nexus 5 Original Android Development] Binary Droids:
Download path in settings working perfect [MENTION=3292224]franciscofranco[/MENTION]. Thanks for all your hard work.

Nexus 5 - Stock 4.4.4 - franco.Kernel
[Nexus 5 Original Android Development] franciscofranco:
Actually it was working fine on the debug build (when you click Run on Eclipse it builds a debug apk without being signed for release on the store) but Proguard (a mechanism to obfuscate Java code) was removing some parts of code from a library that I use and was preventing that specific piece of code to work due to that (note to self: read a library documentation with both eyes and more carefully). All is back to normal now!
[Nexus 5 Original Android Development] Zyphur:
Battery life improved for me on r55. Jesus. Franco the god.
[Nexus 5 Original Android Development] pchtc:
i am having the same behaviour as others

since r55

never hit 300

345 sometimes

but 422 and 625 alot

that being said

battery life seems to be same as before

and deep sleep is just as much as before

so... while the "ramp-up" seems a little too sensitive

i am not experiencing a negative impact
[Nexus 5 Original Android Development] zephiK:
Looks like Android L AOSP is up. Hopefully kernel sources and whatnot become available

http://www.androidpolice.com/2014/0...ve-aosp-includes-support-nexus-4-5-7-2013-10/

Interesting article by Ars Technica in terms of Android L battery http://arstechnica.com/gadgets/2014...ta-we-put-android-l-through-our-battery-test/

Woo excited.
[Nexus 5 Original Android Development] Enddo:
I just read this too. I'm curious what can be used by the custom kernel and custom ROM community :)
[Nexus 5 Original Android Development] franciscofranco:
I just merged L Kernel sources. It was one of the hardest merges I had to do because Google decided to rebase the frakking tree. Sigh... still compiling.

Besides there's some audio subsystem changes, I'm not sure it will work perfectly on KitKat without some userspace changes. Booting to check.
[Nexus 5 Original Android Development] Tzfardaya:
You mea I can haz Franco on L soons?

:D :D :D :D :D :D :D :D :D :D
[Nexus 5 Original Android Development] Carnage:
Got my nexus 5 yesterday.unlock the bootloader,flash recovery(twrp),rooted.running stock 4.4.4...can i simply flash this kernel in recovery?..sorry for the noob question.i'm coming from samsung and this device is new for me.