yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] PeQuEsan:
Any simple changelog we can read? I know it's just 5 iterations, but first mods are always the most feature rich ones... I see you've changed haptic feedback as in N4, for example... Any more noticeable changes? Or just test stability builds?
[Nexus 5 Original Android Development] flex0r:
In the Google Keyboard settings, scroll down to 'Advanced settings'. Second to last option there is 'Keypress vibration duration', I changed that to 2ms, nice and short, but of course you can put it a little higher if you like and probably still enjoy little or no rambling as long as you put the overall power on the motor down using fku
[Nexus 5 Original Android Development] thegtfusion:
hello :D

i just received my N5 last night. i really hope your device is fine (no rattling power button/ sick vibration motor) so that the development can go full speed soon :D
[Nexus 5 Original Android Development] Testraindrop:
Well as Franco removed MPDecision like on the Nexus4, the Android framework can't find it and throws the powerhal error.

Nothing new, normal.

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] Neejay:
Does anyone know if the kernel source used in the r14 build? I saw franco post that it was finally released, but just curious if he merged it in yet.
[Nexus 5 Original Android Development] aimetti:
Back on fku for first time in forever. App is sick now. Gj
[Nexus 5 Original Android Development] NoobieExtraordinare:
Fellas, sorry if this has been answered before, I tried to follow the last 20 pages of this thread. I have seen quite a few screenshots showing 5+ hours of screen on time as an indicator of battery life. My question is, is this only on wifi or more a realistic indicator with wifi and LTE on? My work has LTE, but not that great. I was wondering if any of you had real life examples of battery life on the kernel with both wifi and LTE on. Even better if your LTE reception isn't all that great. Thanks in advance.
[Nexus 5 Original Android Development] 850T5m:
That's on lte all day, horrible signal. Usually 0-1 bar lol

2h21m screen on time

Listened to 20 minutes of music

Stock kernel settings, r14
[Nexus 5 Original Android Development] NoobieExtraordinare:
Many thanks. I wanna see how on screen time can one squeeze out with an LTE signal like that. I'm getting as much with stock I believe.
[Nexus 5 Original Android Development] 850T5m:
This was a few days ago, not sure if I was on r13 or r14 tho

Still pretty awesome
[Nexus 5 Original Android Development] dwang:
I think ~430 hours on LTE is pretty normal.

A mixture of LTE and WiFi and I've gotten 5 hours.

WiFi only and I've gotten close to 6 hours of SOT.
[Nexus 5 Original Android Development] IIMaxII:
Loving your kernal so far Franco. I made adjustments for more battery. :D
[Nexus 5 Original Android Development] IIMaxII:
Can't attack 2 images in one post.
[Nexus 5 Original Android Development] nitzer71:
What adjustments have you made?
[Nexus 5 Original Android Development] rccar:
I don't see how people are getting such great deep sleep. I get a drain of about 5% per 2 hours. Give or take. On WiFi. I charge it to 100% while off, pull it off, turn it on, within a minute its already down to 99%. I think stock I got better battery.. Or maybe the same.
[Nexus 5 Original Android Development] nitzer71:
That's not bad. I get a drain of about 10% every 30 minutes!!!??? :( ( using r14)
[Nexus 5 Original Android Development] Media_Blitz:
Are you hibernating any apps?
[Nexus 5 Original Android Development] yldlj:
Im getting 0.2 - 0.4% battery drain overnight! Was on stock ROM now on PSX and its the same drain overnight. Stock setttings, mobile data on, location off, greenify all apps.
[Nexus 5 Original Android Development] :
I wish I could UV my life :)
[Nexus 5 Original Android Development] javacody:
Can you people please learn how to read?

Your drain issues have nothing to do with the kernel. Its an issue with Google play services. Get the beta BBS app for KitKat and check it out for yourselves.

Franco's gone for 4 freakin days and I swear, every lazy dumbass starts whining in this thread.
[Nexus 5 Original Android Development] vomer:
R14 still seems to have some music playback stutter when screen is off.

Sent from my Nexus 5
[Nexus 5 Original Android Development] i860:
What player are you using? I run a lot with google player, endomondo traking and no playback stutter, and this is over 2+ Hours.
[Nexus 5 Original Android Development] chw2006:
I just flashed r14 on my replacement unit, but the colors didn't change at all?

I flashed r14 on my previous unit and the colors are visibly different on the two units.
[Nexus 5 Original Android Development] TheLastSidekick:
Thank you both. I never took into account that the faster charging would stress the battery. I have a BlackBerry charger for the PlayBook that charges rather fast. Perhaps I should use a slower charger.

And no, I don't own a BlackBerry phone or tablet.. Just the chargers due to their charging speed and price.
[Nexus 5 Original Android Development] Tzfardaya:
I have 2A chargers I use too, but I also make a point of charging off USB (or one of my 0.7A adapters) overnight from time to time...

In theory, our 3300mAh batteries should be able to charge up to 3.3A with no issues, but in practice I find that slow charging is still beneficial.
[Nexus 5 Original Android Development] TheLastSidekick:
I will do this and report my findings on if it helps or not for science. For the record I average about 4-5 SOT. I can tell when the battery is having a bad day cause I'll get a 3 SOT with about the same usage.

Plus it seems the recent Google Play Services update is at it again and everyone has to band-aid it until Google fixes it.
[Nexus 5 Original Android Development] Tzfardaya:
No no no... It's not for science.... It's FOR SCIENCE!
[Nexus 5 Original Android Development] yeiyei0891:
I get 5:15h SOT maximum with stock and Franco kernel.

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Arstoien:
Potential hotplug bug, try to reproduce: if cpu scaling max or min freq is changed, all cores become online and don't go offline until screen off/on. Regardless of hotplug load threshold. Reflashed kernel and rom and can reproduce 100% of the time.
[Nexus 5 Original Android Development] idriff:
I got a question, don't know if it's r63 or every version of Franco kernel but I can't use usb otg with Franco r63 (the one I was using) any help?
[Nexus 5 Original Android Development] Tzfardaya:
Franco otg is Stock, meaning you need a helper app to mount sdcard, USB stick, external hdd....
[Nexus 5 Original Android Development] idriff:
Thanks, didn't know that. Going to try that.
[Nexus 5 Original Android Development] brotbuexe:
Stickmount works great.
[Nexus 5 Original Android Development] DiST_EL:
If you want a really stable release you should get the elemental X kernel. It focuses very strictly on very high stability and good battery life. It is also very smooth. I am using it and never had drains or stability issues.

But Franco is definitely a good kernel as well which experiments more with new features, which is also nice.
[Nexus 5 Original Android Development] WettbackMartyr:
Seriously........

You're drunk [emoji52] Go home [emoji19]

...................
[Nexus 5 Original Android Development] Technecium:
Better yet, if you really want stable get an iPhone.

Oh, was that wrong? Should I not have posted this in here?
[Nexus 5 Original Android Development] occtec:
Yay, Francisco is still with us, LOL... New test boot.img 20141017 is out http://kernels.franco-lnx.net/Nexus5/4.4/tests/ ;)
[Nexus 5 Original Android Development] garzacorporations:
I'm having license problems with the FKU after the last update. I've bought the app on the play store but even if I clear data & uninstall it and after reinstall it still has problems. ¿any solution?
[Nexus 5 Original Android Development] looknohands14:
Hi guys, I've been having a problem with r62 on my stock N5. I'm running out of ideas and this has been happening for about 4-5 days now. The phone charges just fine but when I unplugged and leave it to sleep it will discharge my battery big time without me doing anything. I have tested by fully charging the phone and leaving it overnight using Aeroplane mode. It left me with +-60% when i wake up. Crazy

Next: Please see these screenshots. This is after I've installed App Ops to remove the crazy permissions, and also uninstalled (or rather disabled) Google apps that I barely use. Today I went to work out and left the phone for about 3 hours and this is the outcome.

It appears to be sleeping fine but man, look at the consumption during 'sleep'!

Further inspection using a battery app.

And the monitor on FKU..

And a few minutes of having the screen on after the 3 hours.. This is also abnormal.

As you can see it is abnormal. And this happened all of a sudden, it was a perfect phone! I could leave it for about 20 hours and it won't discharge much! I first noticed that the phone was overheating and then it won't charge using the orginal charger (cable is fine). It charges using a 2.1AMP charger fine. So, I went on to check the phone some more and this was the outcome (it was worse before i did some tweaking).

I've installed r63 moments ago and we'll see how that fares.

Can someone help me please?
[Nexus 5 Original Android Development] Tzfardaya:
Installed any tap to wake apps?
[Nexus 5 Original Android Development] msgfromside3:
Better yet, bbs will be more helpful. I cant see a thing from these screenshots because they are all too high level analysis.
[Nexus 5 Original Android Development] krazeecracker:
See below
[Nexus 5 Original Android Development] looknohands14:
I did not install any of those.

msgfromside3, do you need any other kind? My phone has been performing as such at all times now.

---------- Post added at 05:03 PM ---------- Previous post was at 04:37 PM ----------

Installed BBS, and I don't really know how to navigate around it yet but the initial overview gave me this impression.
[Nexus 5 Original Android Development] garzacorporations:
Already done it and nothing
[Nexus 5 Original Android Development] ejadsyahrizad:
try clean flash or clear dalvik n cache at recovery... ✌

MOD EDIT: there are users using mobile to access this FORUM. Quoting such big images could be avoided.
[Nexus 5 Original Android Development] Ryrynz:
Omg could we quote his entire post more? My finger just loves to swipe!
[Nexus 5 Original Android Development] looknohands14:
Then I guess you're lurking around the wrong thread.

---------- Post added at 06:55 AM ---------- Previous post was at 06:50 AM ----------

Alrighty, second report. I've cleared cache, uninstall recently installed apps hoping to find a culprit. But nothing yet, overview suggests that it is a kernel problem with it recording high numbers of activity. BBS shows the phone never goes to sleep and I've identified slimport_wake_lock to be the culprit. This is found under the Kernel wake lock filter. PowerManagerService.WakeLocks is also active as well as additional small processes keeping the phone awake. But I think to deactivate or make slimport work normally would be the first step. I've tried searching for answers but I've come up with none. can someone help me? Anyone?
[Nexus 5 Original Android Development] pkelly517:
Two things.

There are hide tags that allow you to quote a message while hiding all the images.

Secondly, you appear to be posting in the wrong thread. Your answers are more likely to be found in the BBS thread.
[Nexus 5 Original Android Development] leuuuuu:
Someone tested franco Kernel in the L Developer Preview LPX13D?
[Nexus 5 Original Android Development] beezy420:
it didn't work on the first preview so it be pointless to try on the new android L release. Just wait till source code then franco can work his magic.
[Nexus 5 Original Android Development] RVDigital:
VERY happy to see that while the Kernel is not Lollipop ready, I can still make some basic adjustments, notably the Vibration Amplifier.

It's crazy having to go from a low setting (32) to stock (100?) when switching to L. It was driving me crazy!
[Nexus 5 Original Android Development] blueren:
HI All,

I recently installed the latest L preview. Will fku's PAM work with the default kernel as intended? I'm guessing it should, just want a confirmation.

Thanks
[Nexus 5 Original Android Development] mibtnt:
Let's just say I used r63 for my trip abroad and man I had almost 0 hiccups. Awesome stuff man.

And I use that same BlackBerry playbook 1.8A charger.

If you want better than 5hrs SOT with WiFi and 3.5hrs with mobile data and calls, buy another phone. Although I know of users who get almost 6hrs.

Can't wait for Lollipop and FKU.

Also in the initial days of use I did notice some heating but its gone now. I'm not exactly sure what caused the increase in heat but. Its no longer there. Also. What's up the the downgraded FKU app?
[Nexus 5 Original Android Development] andredn8:
Dose this kernel work with L Dev Preview LPX13D?
[Nexus 5 Original Android Development] Hatshipuh:
Don't know if sarcasm or not being able to read 4 posts back...

Tap-a-talked from my Nexus 7
[Nexus 5 Original Android Development] Ltdrev:
The hardest part about moving forward is not looking back.

this IS sarcasm

:crying:
[Nexus 5 Original Android Development] krystyuc:
Franco did an official announcement that the kernel will be work on Android L after 1 source will be released :)

Original: "Exciting times with Android mean cool things are coming from me. Before I write about the Nexus 6 let's start out with FK related info:

It's mostly good news, but two probably not so good:

1 - Galaxy Nexus FK updates will finish once I reach r400 (currently r398). This is a 3 year old device, and I've already extended way beyond the minimum 18 months. Reason for this is that I don't even touch the device, it's collecting dust on the drawer and I've done everything I can about its Kernel. There's no point working on it anymore after r400. FKU will support GN forever, just no more Kernels.

2 - I probably won't buy the Nexus 9. I don't use tablets and my update cycle on the current N7's and N10 is horrible, I simply don't use them so motivation to work on them is not on par. For this reason, I'm not going to waste my hard earned money to buy hardware to be unused on my drawer. However if someone buys me the device I'll gladly work on it. Make no mistake, the N9 is an amazing device spec wise. Please respect my decision.

About current supported devices, all franco.Kernels will be re-worked (except GN of course). So expect a release cycle within the 30-days after Lollipop drops. The order of updates will be:

1 - Nexus 5

2 - Nexus 4

3 - Nexus 7 2013

4 - Nexus 10

5 - Nexus 7

If the changes on 2012's N7 are minimal I'll drop it faster, but its currently unknown.

I'm also dependent on Google's source drop so don't bother asking me for updates before its sources are released.

About the Nexus 6 - it's definitely a MUST buy. I love big displays and I cannot wait to play with top notch technology. The One Plus One is currently the un-disputed King, and it will be interesting to see how it fares with Shamu. Expect FK for the Nexus 6 as soon as I have the device (or maybe sooner if the source builds and works fine out of the box).

Also BIG franco.Kernel updater release expected soon. I'm gonna time it with FK releases for Lollipop so ETA somewhere end of November.

I guess this is it for now, literally can't wait!"
[Nexus 5 Original Android Development] tylerdurden83:
Hello everyone. I've been running franco kernel r63 with stock settings for a while now, but I can't go anywhere near your results. As you can see from the attached images, I had green signal most of the times, and the device was awake for just 4% of the time, so I cant really try to optimize anything else as far as I know...

What would you try to do?

Thank you,

TD
[Nexus 5 Original Android Development] Koragg618:
Under clock to 1.7 GHz, undervolt by 50-100, depending on your device (my device can go down by 100, but only for 1.7 and lower; for higher speeds, I have to bring the voltage back up) and lock GPU at 320 MHz. Then make a couple of profiles that bring up the CPU and GPU clock speeks, and voltage back to the default for power hungry apps like games.

Location off (only on when using maps), wifi off when screen has been off for some time, still using LTE, and setting brightness manually.

I get 4-5 SOT with this setup, and very minimal battery drain at standby; around 1% loss in 1-2 hours. (well know I'm on Lollipop now).

EDIT:

Forgot to mention speed; its still very quick, and with ART, it just makes it faster.
[Nexus 5 Original Android Development] Tylog:
L source https://github.com/android/kernel_msm/commits/android-msm-hammerhead-3.4-l-preview?page=1
[Nexus 5 Original Android Development] topgeardave:
Brightness is your issue here mate, and turn off data when you're not using it
[Nexus 5 Original Android Development] Dungeon47:
I'm a willing test subject.

http://media-cache-ak0.pinimg.com/736x/a2/3c/37/a23c376be956e707159e53b8e6f5d45e.jpg
[Nexus 5 Original Android Development] msgfromside3:
You need to look at partial wakelock to see wihch apps are keeping your phone awake. 100% wake time is not normal and something you run must cause it. You should find out and squash them - either deinstall it or greenify them.
[Nexus 5 Original Android Development] brotbuexe:
Anyone else have issues with BT get stuck when using an android wearable? I tried r63 and the last test version on stock 4.4.4.

I have a Moto 360. Sometimes (especially when resyncing all the apps) the BT get stuck.

The Android Wear App can't connect anymore with the Watch, and I can't disable bluetooth on the phone. It tries disabling and then says enabled again until I reboot the phone.

Tried stock kernel for some time and it didn't happen there.

Without the Moto I didn't have this issue, using only BT headsets.

[MENTION=3292224]franciscofranco[/MENTION], I collected logs with "andy log" I could share.
[Nexus 5 Original Android Development] fredfox_uk:
I have a similar problem with my Parrot mki9200 if I don't disconnect the phone first. If I forget I have to reboot the phone. I've not tried stock kernel or any other kernel although I don't have any problems with my (work provided) HTC Desire S
[Nexus 5 Original Android Development] SpasilliumNexus:
Beta FKU is back on the Play Store :D
[Nexus 5 Original Android Development] looknohands14:
I'm getting a high percentage of activity with slimport_wake_lock under kernel wake lock. its keping my phone awake.
[Nexus 5 Original Android Development] fredfox_uk:
Per App Mode (now Per App Profiles) is working again and no crashes so far.
[Nexus 5 Original Android Development] sjknight413:
And this relates to Franco's kernel how?

Sent from my Android 5.0 Lollipop + ElementalX powered Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Just checked and the Kernel sources from the latest Preview drop are up. I imagine they won't change much up until the final release so I'll start working on it today. KitKat releases are obviously EOL.
[Nexus 5 Original Android Development] msgfromside3:
I think you got the answer then. Google is your Friend from here. :)
[Nexus 5 Original Android Development] looknohands14:
I've googled everything for the past few days, but there's nothing out there.
[Nexus 5 Original Android Development] franciscofranco:
SlimPort is a bus to connect the device to other displays: http://www.slimportconnect.com/

That wakelock is most likely active because you're connecting your N5 to other displays? Slimport drivers are stock here.
[Nexus 5 Original Android Development] looknohands14:
Hey Franco, I've never connected this phone to another display or even thought of doing so. I've switched off most of the background processes and minimised any wake locks but the slimport one is still active and keeping my phone awake. It's listed under kernel wake lock but I am struggling to find a solution.
[Nexus 5 Original Android Development] franciscofranco:
Don't ask me, I don't own your phone. Reboot or something, if it's wakelocking there's obviously some process/app making use it happen.
[Nexus 5 Original Android Development] simonarturo:
EOL? Encyclopedia Of Animals? Or is it End of Life? Either one could apply here since there's a cat involved
[Nexus 5 Original Android Development] franciscofranco:
I see what you did there! It's End of Life!
[Nexus 5 Original Android Development] tylerdurden83:
I keep it at around 25%... You keep it even lower? Or use auto brightness? Cheers
[Nexus 5 Original Android Development] topgeardave:
I always keep mine at 20%, but the issue here is data. Turn it off whenever you're not using it because even when screen off it will slowly sip away at your battery. Most of these people with 5-6h SOT here are always on wifi which causes little drain.
[Nexus 5 Original Android Development] simonarturo:
25% seems too high to me, unless you are always in a high luminosity environment

I use an app called Lux to manage brightness and it seems to do the trick. Some users claim that it doesn't do anything battery wise but I would suggest that you give it a try
[Nexus 5 Original Android Development] topgeardave:
There's no need for Lux when you can do it at a hardware level changing minimum brightness levels in fku.
[Nexus 5 Original Android Development] Akath19:
Lux seems to be better regarding brightness changes.

Also, Lux's night mode is amazing!!!
[Nexus 5 Original Android Development] rabaker07:
What, with all Red?

Also, I feel like Lux went downhill. Maybe my sensor went downhill. I had the N5 plugin as well and it just started acting wonky lately. Takes a second when I unlock the screen to go from dim to bright, often too dim, slow to change, etc. Bizarre. I like the kernel idea better.

And does Franco support 5.0 "L" yet?
[Nexus 5 Original Android Development] Akath19:
Nah, that's astronomer mode which is IMO, hideous.

Night mode is when the screen light turns from Blue to light yellow, it's easily configurable in the settings.

Dunno about your slowness, mine works almost instantly.

Lastly, Franco is merging Lollipop's kernel source, so, hopefully, by the end of this week we might see r64.
[Nexus 5 Original Android Development] mibtnt:
[emoji33] [emoji33] [emoji33]

I've never been more excited!
[Nexus 5 Original Android Development] fatspirit:
Emerging Of Lollipop (:
[Nexus 5 Original Android Development] PhantomGamers:
Any chance we might see a test build that works with the preview? I expect probably not but I'm currently running the preview myself and the battery life improvements are phenomenal, I can only imagine what might come of having your changes on top of it!
[Nexus 5 Original Android Development] Köhvwezd:
Lux is very wonky for me. I just use Mahdi's auto brightness with cf.lumen, works well enough.
[Nexus 5 Original Android Development] franciscofranco:
Yes, I'll push a boot.img for the latest preview ASAP, currently working on it, it's a full re-merge so it takes time.
[Nexus 5 Original Android Development] nexusmaniac:
I for one truly can't wait! I've been using code blue for ages with the L preview and it's just not the same as Franco :) It'll be great to be back :D
[Nexus 5 Original Android Development] amaces:
Yep, same observation. Lux has been increasingly flaky for months now. Too bad given that the plugin/kernel support approach is probably the best.

Nexus 5/FK/Xposed
[Nexus 5 Original Android Development] sordna:
Have you tried Velis Auto Brightness? I never tried Lux but Velis has been working very well for me.
[Nexus 5 Original Android Development] PhantomGamers:
Thanks man, no rush at all! Glad to hear it's on the way. :highfive:
[Nexus 5 Original Android Development] ilaf0106:
I can't wait for Android muffins
[Nexus 5 Original Android Development] Tzfardaya:
No, you're not allowed to turn Mr. Muffins into an android...

?
[Nexus 5 Original Android Development] sordna:
Muffin? How about Android Marshmallow ?