yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Tzfardaya:
Yes, the zip

Or you can use fku to flash it for yiu

Flashify is another good option.

Fastboot works too.
[Nexus 5 Original Android Development] Carnage:
Ok..thanks for the answer mate!..
[Nexus 5 Original Android Development] Enddo:
will this split the kernel between one that only works on Android L and one that only works on 4.4.4? Or will it be interchangeable to both of them?

In any case, bad ass man, and thank you for the work. I look forward to getting this working on Android L. I've heard some people say they have had FKU force close on the Android L preview. Will this new build need to be flashed with fastboot?
[Nexus 5 Original Android Development] franciscofranco:
I couldn't give 5 ****s about Android L, I'm merging it to use on KitKat. I'm not going to develop for an unreleased Android software which is prone to change.
[Nexus 5 Original Android Development] Tzfardaya:
No worries, I figured that would be the case. :P
[Nexus 5 Original Android Development] franciscofranco:
boot.img with Android L Kernel commits merged: http://kernels.franco-lnx.net/Nexus5/4.4/tests/boot.img

Give it a whirl. Before you ask NO it's not for Android L, don't bother me with Android L I don't give a **** about it.

Heads up, it ships with a new touch firmware:

- Improved noise peak filter (increase from 60 to 70)

- Increased IM threshold of switching into 60Hz

- Increased software filter delay

- Less frequency shifting in noisy state

- Improved low temperature environment
[Nexus 5 Original Android Development] Hatshipuh:
Ermagerd new touch firmware, this gives me hope for the multi touch issues of Flo!

Tap-a-talked from my Nexus 7
[Nexus 5 Original Android Development] franciscofranco:
Why? This is N5 only...
[Nexus 5 Original Android Development] vomer:
I wouldn't hope for much tbh
[Nexus 5 Original Android Development] Tzfardaya:
Oi, keep yer mitts of m'gurl Flo...
[Nexus 5 Original Android Development] qbanlinxx:
Mr. franco, Would you ever consider adding to the fku app, a way to adjust the screen off cpu max
[Nexus 5 Original Android Development] franciscofranco:
It needs to be added in the Kernel - unless there's an amazingly huge demand for that I doubt it. I was an adept of it once, but I'm not so much.
[Nexus 5 Original Android Development] Technecium:
Then I'll be the second if we're voting. Logic behind it being that the newest interactive brings amazing performance and equal if not better battery life but music listeners will take a battery hit. Since per-app modes won't stick with the screen off, this could be one solution.

If anyone is also interested speak up..

Just tested a Tasker screen off profile, works like a charm.
[Nexus 5 Original Android Development] Enddo:
I definitely agree that this feature would be awesome, as long as it doesn't affect how the current kernel operates(performance/battery saving wise)
[Nexus 5 Original Android Development] fatspirit:
What is Flo?
[Nexus 5 Original Android Development] Technecium:
It wouldn't have to. Leave it default for the people who don't listen to music, but those of us that do can echo it.
[Nexus 5 Original Android Development] justibasa:
N7 2013. Back on topic. Test kernel seems nice. Phone seems as smooth as "L". Hoping battery life is still awesome. Thanks Franco.
[Nexus 5 Original Android Development] prstorero:
Nexus 7 2013 WiFi.
[Nexus 5 Original Android Development] Technecium:
Google, "Nexus 7".

Yes, that is a sentence.

Sorry for quotes again.. I did a little poking around, another option if it's not implemented at kernel level is a screen off profile in Tasker.
[Nexus 5 Original Android Development] cobhc:
I'm giving my vote.
[Nexus 5 Original Android Development] TSFox0317:
Flashed latest kernel on 4.4.4 aokp rom and it doesn't boot past the Google logo, anyone else have this issue, I've tried everything
[Nexus 5 Original Android Development] RobbieL811:
You need a CAF compatible kernel. In other words, FK doesn't work with AOKP like it used to back in the good ole days.

Sent from my Nexus 5
[Nexus 5 Original Android Development] nexusmaniac:
Oh no! :'( Ah well guess it'll be in a few months then ;)
[Nexus 5 Original Android Development] TheLastSidekick:
Can confirm that latest test boot.img with commits from L works on Rastakat 4.4.4 and is BREATHTAKING ON ART.

Franco, you busted your ass with those commits and it shows! I have NEVER been more satisfied with my Nexus 5 then tonight.

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] Bluewall:
Set a screen off max cpu freq doesn't really help the battery life. It has been discussed many times and it seems it doesn't change much.
[Nexus 5 Original Android Development] Technecium:
Yes, it does. Play 8 hours of audio with r55 or later without screen off max and with. Let me know what you get.

However, if you have no background apps running you are correct.
[Nexus 5 Original Android Development] RobLudo:
Here's my vote too
[Nexus 5 Original Android Development] jaimbo:
And my vote also!
[Nexus 5 Original Android Development] Juzman:
Working well on latest PA 4.4.4.
[Nexus 5 Original Android Development] kecinzer:
Latest patches are not compatible with inline building with ROM :(.
[Nexus 5 Original Android Development] Hatshipuh:
Since N5 got new touchscreen driver, it gets my hopes up that Flo gets some love too when it's release time.

I know, but hope is hard to kill D:
[Nexus 5 Original Android Development] SketchyStunts:
7/2 test boot.img running great on omni.
[Nexus 5 Original Android Development] LaboDJ:
Hi Franco, I just cherrypicked this commit but it gives me errors:

arch/arm/mach-msm/perf_trace_counters.c: In function ‘tracectr_cpu_hotplug_notifier’:
arch/arm/mach-msm/perf_trace_counters.c:31:18: error: ‘CPU_TASKS_FROZEN’ undeclared (first use in this function)
if ((action & (~CPU_TASKS_FROZEN)) == CPU_UP_PREPARE) {
^
arch/arm/mach-msm/perf_trace_counters.c:31:18: note: each undeclared identifier is reported only once for each function it appears in
arch/arm/mach-msm/perf_trace_counters.c:31:40: error: ‘CPU_UP_PREPARE’ undeclared (first use in this function)
if ((action & (~CPU_TASKS_FROZEN)) == CPU_UP_PREPARE) {
^
arch/arm/mach-msm/perf_trace_counters.c: In function ‘init_tracecounters’:
arch/arm/mach-msm/perf_trace_counters.c:140:2: error: implicit declaration of function ‘register_cpu_notifier’ [-Werror=implicit-function-declaration]
register_cpu_notifier(&tracectr_cpu_hotplug_notifier_block);
^
arch/arm/mach-msm/perf_trace_counters.c: In function ‘exit_tracecounters’:
arch/arm/mach-msm/perf_trace_counters.c:146:2: error: implicit declaration of function ‘unregister_cpu_notifier’ [-Werror=implicit-function-declaration]
unregister_cpu_notifier(&tracectr_cpu_hotplug_notifier_block);
^
cc1: some warnings being treated as errors

Could you help me? Sources are here
[Nexus 5 Original Android Development] dox81:
Ondemand governor is broken in r55. On idle, one core goes to 300mhz and the other stays above 1000mhz. Any fixes for this?
[Nexus 5 Original Android Development] Mr.Jay:
How's battery life and performance on the latest test build with Android L sources?

Nexus 5 || Android 4.4.4 || Paranoid Android
[Nexus 5 Original Android Development] fcisco13:
Flash n try.

Whatchu talking bout willis!
[Nexus 5 Original Android Development] jfim88:
Is the r55 the one that includes patches from Android L?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Technecium:
https://github.com/franciscofranco/hammerhead/blob/nightlies/arch/arm/kernel/perf_event.c

line 906 .. looks like your missing some code
[Nexus 5 Original Android Development] gambe89:
No, it isn't. Download it from here http://kernels.franco-lnx.net/Nexus5/4.4/tests/boot.img
[Nexus 5 Original Android Development] combatdeity:
Could you, or anyone, possibly dumb these down a bit for a layman?
[Nexus 5 Original Android Development] LaboDJ:
Nope it's not like so.

My online sources are latest working sources, you can compile them without problems, but if I cherrypick this commits then everything will be f**ked up.

If I can't cherrypick that commit without problems then I can't apply these patches:

msm: perf: Fix cpu id logic in tracectr notifier

msm: perf: fix formatting of trace entry

Perf: preserve registers across hotplug

Perf: Fix PID for tracepoints

and my missing lines in perf_event.c are coming from "Perf: preserve registers across hotplug" that comes after the problematic commit
[Nexus 5 Original Android Development] Technecium:
My bad, I thought you had already cherry picked. It's getting late where I live so I don't have enough time to clone your repository. Franco probably knows or has a good idea where to look. But I usually figure out the undefined by doing the following..

$ find . - iname "*.c" | xargs grep "whatever is undefined"

Run it against the root of nightlies and your own and compare. You might have to also run it with "*.h"

Then I use meld to compare the files listed from the find.

PS. Hope I'm not insulting your intelligence. I have checked out your work a few times. Nice work on the Linux subversion updates.
[Nexus 5 Original Android Development] LaboDJ:
I solved my problem reverting an old patch that disabled tracing, everything is up in my git
[Nexus 5 Original Android Development] ludorexmundi:
flash the test boot.img r56 in my nexus 5 stock 4.4.4 then switch to ART and unable to lock the device with power button, which seems to be inresponsive O.o switching back to dalvik and everything works now!
[Nexus 5 Original Android Development] cobhc:
Exact same setup here and my device is locking fine using the power button, still on ART.

Maybe you just needed a reboot?
[Nexus 5 Original Android Development] ludorexmundi:
already done.. just retrying to switch on ART and will see..thank you however!

deleting fku settings solved the problem!
[Nexus 5 Original Android Development] bradputt:
On 56 now, my phone will get the no sim card inserted or cannot get any network

anyone having the same issue?
[Nexus 5 Original Android Development] franciscofranco:
Care you elaborate?

I didn't change Ondemand.

I don't really know how to explain it, sorry, but it's mostly to decrease noise while touching the display and give a more smooth feeling.

No.
[Nexus 5 Original Android Development] pchtc:
no

test 56 working great

in fact

in r55 the cpu never went below 345 as was usually over 422 or 652 at idle

now in test 56

the cpu scales down to 300 again
[Nexus 5 Original Android Development] simonarturo:
Reporting my R55 experience:

3 cycles, saw better performance and less battery drain with Screen On, though I did notice a 12% drain while I was sleeping (location off, auto-sync off, data off). So I'd say great SoT but less idle time. This could be caused by the dismal cellular data reception around my house though.

Testing R56 now, will let you know how it goes
[Nexus 5 Original Android Development] franciscofranco:
CPU always scaled down to 300MHz even if you didn't see it on system monitor... the frequencies change every 30ms...

Screen off idle power usage doesn't change between Kernel changes, I've said this countless times... either you have too many wakelocks from your apps or you don't... What changes is screen on drain.
[Nexus 5 Original Android Development] simonarturo:
That's why I added that it could be caused by the radio and my bad data connection around the house. I try to manage wakelocks with gsam and greenify but the drain is still very irregular, sometimes 5%, sometimes +10%, which is why I suspect the radio.

R56 is working great, 13% drain with 1hr SoT is good on my book
[Nexus 5 Original Android Development] Falconite:
want to ask

now im using franco kernel r53 and 4.4.3

how is the easiest and fastest way to update to 4.4.4 ?

am I have to change it to the stock kernel ? if yes, how to do that ?

sry im newbie :p
[Nexus 5 Original Android Development] italia0101:
Was this directly after booting, sometimes my device does this regardless of kernel while it's starting up.... I wait 2 mins and it was fine and locked.
[Nexus 5 Original Android Development] TrenchKato:
Do you have a custom recovery?
[Nexus 5 Original Android Development] Tzfardaya:
Google nexus image, first link... Follow the directions on that page... Easiest way to go stock.. (quickest too)
[Nexus 5 Original Android Development] franciscofranco:
You don't need to do anything for 4.4.4, just run the system update thingy and the ota will flash.
[Nexus 5 Original Android Development] tylerdurden83:
Franco, on Play you wrote:

Does this mean that if I load for example the Piereligio premade gamma profile, I get different results than before?

Because I loaded it, and frankly I can't really say that it looks good to me, so I'm wondering if that is why.

Thanks!
[Nexus 5 Original Android Development] simonarturo:
Hmmm, so far I have been seeing some instability on R56 that was not present on R55. Have had 4 reboots in about 2 hours of use. Will switch to Dalvik to see if it keeps happening and report back after some more testing
[Nexus 5 Original Android Development] Tzfardaya:
Are you making any changes to the kernel tunables? Undervolt?
[Nexus 5 Original Android Development] nexusmaniac:
Hi Franco,

Is there a chance you could make the FKU app work with L? Or is it pointless because L is prone to change/you don't have everything you need to make it work properly?

Thanks! :)
[Nexus 5 Original Android Development] Red5:
Bingo!

As stated already, Franco dosent give a **** about L right now.
[Nexus 5 Original Android Development] Tzfardaya:
I'd rather see a kernel for L first... :P but Franco doesn't care about L yet... ;)

---------- Post added at 03:36 PM ---------- Previous post was at 03:36 PM ----------

I'm sure there's enough source out for L now he could, if he so desired...
[Nexus 5 Original Android Development] TheLastSidekick:
Rooted apps as is aren't safe on L. I was sent into a bootloop for loading up Greenify and granting it root.

And for good reason, too. There's many bugs that can only be squashed by Google right now, people stating that L is stable clearly haven't played around with it enough.

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] nexusmaniac:
Yeah, I know he doesn't really care about it, but I do :P haha, it's my daily driver (only some minor issues with it)

It'd be great to see a kernel for it (not likely any time soon lol) but having the ability to change from on demand to interactive etc. in FKU would be nice :)
[Nexus 5 Original Android Development] The Gingerbread Man:
I have been using the trickster app to tweak the stock L kernel. Set to interactive / deadline / read ahead 512kb and that's as close as you can get for now.
[Nexus 5 Original Android Development] Tzfardaya:
L itself if very stable... Root is fine... Apps that make changes to the /system partition reboot the device...

But that's less of a bug and more of a change in how the of works, so those apps will likely need to be rewritten.

But yes, there are a series of bugs to squash, such as mms via hangouts...
[Nexus 5 Original Android Development] TheLastSidekick:
That had been my initial opinion. Then stuff like tethering wasn't working, data and WiFi would cut out every 20 minutes or so. I think L is for the most part fine..if you treat it like its truly stock and you make NO modifications haha. For me, that's when things started acting strange.

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] Falconite:
i tried it

but after reboot its still 4.4.3
[Nexus 5 Original Android Development] msgfromside3:
This is not a kernel issue but rather n5 issue. I get this on and off with stock kernel and this kernel.
[Nexus 5 Original Android Development] Tzfardaya:
Yeah, I've always ran fairly stock... I haven't had any issues with data/WiFi, how did you flash to L?

---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------

Usually from a poor cut Sim, a slight misalignment of the tray, etc etc... A drop which jars the sim
[Nexus 5 Original Android Development] simonarturo:
-75 UV, same values I've been using in R53,54 & 55

Now whenever I try to change voltage in FKU I get a reboot. Will try running it with Dalvik instead to see if ART is the problem here
[Nexus 5 Original Android Development] TheLastSidekick:
Vomers flashable zip, then rooted kernel, then flashed SuperSU on MultiROM 25. (The first day it was out basically haha)

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] Tzfardaya:
It could be that the new kernel has different voltage sensitivities... It's happened before, try without the uv

---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------

Try via the flash-all script included with Google distribution.. Vomers zip has been known to flash incompletely for some reason, if you head over to his thread there's the occasional hiccups after flashing his zip (SD card issues mostly, but some others) I think it had to do with the fact his scripts don't wipe the device clean first.
[Nexus 5 Original Android Development] JaqaL06:
and i get missed call notification bug. even i check them it counts +1 always .
[Nexus 5 Original Android Development] Skyrocket2Paradise:
anybody getting force closes on every open on dolphin browser? probably the app but just checking
[Nexus 5 Original Android Development] ConMcCRay:
Force closes trying to open chrome and when playing a vine after the vine is finished (or any video I guess) the screen freezes for a second or two then you can move it again
[Nexus 5 Original Android Development] msgfromside3:
Yeah, but not for N5 case, unless N5 has a major issue with its sim card tray. There have been many reports for this and for my case, it happens even when my phone is sitting on the desk, not moving. :crying:
[Nexus 5 Original Android Development] Skyrocket2Paradise:
im pretty sure its because of the android L merges he made. Dolphin brower crashes as soon as I try to load a webpage
[Nexus 5 Original Android Development] franciscofranco:
Yes, probably one of the Android L patches that I merged.
[Nexus 5 Original Android Development] simonarturo:
EDIT: just read answer above
[Nexus 5 Original Android Development] RobbieL811:
[MENTION=3292224]franciscofranco[/MENTION] I am thinking of making and maintaining a CAF version of your kernel for our phones. Do you by any chance know what patches/commits I will need to make your kernel compatible with CM?
[Nexus 5 Original Android Development] franciscofranco:
No idea, sorry. Go to CM's repo and you'll have to figure out for yourself, I don't have time for that sorry!
[Nexus 5 Original Android Development] RobbieL811:
Ok. Thought I my be able to ease some of the asking for it. I'll look around.
[Nexus 5 Original Android Development] TrenchKato:
Someone posted them in this thread already but Tapatalk search is not pulling it up.
[Nexus 5 Original Android Development] RobbieL811:
I'm searching now. If you stumble across them, please let me know. Thanks.
[Nexus 5 Original Android Development] franciscofranco:
Basically it's the changes on the video stack (mdss) and IOMMU stack because both require userspace work.
[Nexus 5 Original Android Development] RobbieL811:
Thanks. Just trying to learn a few things.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Juzman:
Just noticed with the test kernel I am getting SoD. Phone rebooted and went to Dalvik instead of ART. Was running fine on r55.
[Nexus 5 Original Android Development] bhu1:
Guys, I am using this kernel on top of PA and USB OTG isn't working.
[Nexus 5 Original Android Development] franciscofranco:
Coincidence, Kernel doesn't change your runtime, besides it doesn't know a single **** about what is the runtime compiler.
[Nexus 5 Original Android Development] franciscofranco:
For the 1000th time, use StickyMount and SuperSu.
[Nexus 5 Original Android Development] bhu1:
Sorry for getting on ur nerves there. Its just that I already tried stick mount and it didn't work, I'll try it again though.
[Nexus 5 Original Android Development] franciscofranco:
Not getting on my nerves at all. Use SuperSu, it doesn't work with superuser.
[Nexus 5 Original Android Development] Juzman:
Yeah, I don't believe the switch from ART to Dalvik has anything to do with your kernel. I figured more so because of the SoD, then when it booted, it rebooted again and "Android is Upgrading".

Flashed r55 and changed to ART, and all is beautiful again. :)
[Nexus 5 Original Android Development] Zyphur:
15% left. 22h exact on battery. 4h 58m screen on time. Estimating would've got almost another hour more if I didn't have to max brightness on 1 show I watched.

Overnight 6 hours lost me 0-1% life.

Good stuff :)
[Nexus 5 Original Android Development] baturcotte:
I've had an issue with test r56 and Xposed...if I try to reinstall (and I've used both classic and the recovery zip installation methods) the framework, my phone almost immediately spontaneously reboots and then when it finishes loading everything and granting root permissions, it reboots again and again...reverting the kernel to either the earlier (non-L) r56 or the release r55 doesn't stop the reboots, only either going back to the stock image or uninstalling Xposed stops them.
[Nexus 5 Original Android Development] franciscofranco:
Xposed is 100% framework, has nothing to do with the Kernel.
[Nexus 5 Original Android Development] rbrenart:
I'm confused, do you mean just within your kernel or in general?

(Anecdote) Screen off idle time was one of the first things that for me hooked on your kernel. At home, on WiFi, I was dropping 20%+ while sleeping on stock whereas with your kernel it's 5% or so. (/Anecdote)
[Nexus 5 Original Android Development] franciscofranco:
In general.

That was because when the Nexus 5 was launched they had a bug on the Wi-Fi drivers that frakked the battery life. Before they launched 4.4.2 I merged a couple patches from kernel_common (base Kernel tree from Android) that fixed it ;)
[Nexus 5 Original Android Development] Aerowinder:
You have a wakelock problem for sure.
[Nexus 5 Original Android Development] simonarturo:
Same thing happened to me, was on ART, phone crashed and rebooted on Dalvik.

I see that you're also using PA, that might be the issue.

For me, changing to Dalvik and doing a more conservative UV (-50 instead of -75) than what I had in R55 got me through the day without a crash. Will try again on ART with the same stable UV to see if I can isolate the source of my reboots.
[Nexus 5 Original Android Development] iPsychoGeek:
Hello, I just got a random reboot. Sorry, my internet is so slow, so I can't upload it on pastebin. Also I have a little undervolting but it was always stable. https://www.dropbox.com/s/kxw74j25y5ad7oj/last_kmsg

Отправлено с моего Nexus 5 через Tapatalk
[Nexus 5 Original Android Development] Juzman:
Ah right. I'm undervolted a fair bit. However r55 and ART with my UV runs well. May go back to stock voltages.
[Nexus 5 Original Android Development] simonarturo:
Go back to stock and then UV bit by bit until you find how low you can go while being stable. For me it's between -60 and -50. My previous -75 UV that worked fine with R53,54 & 55 is not stable in R56 with my configuration. Also, just changed to ART, will run a couple cycles to see if it any problems arise
[Nexus 5 Original Android Development] Damian2013:
I've been on it since day 1 and no issues for me so don't count everyone in that statistic.
[Nexus 5 Original Android Development] Juzman:
My voltages have been fine on all previous versions with ART except r56 test. So I guess it is voltages.

---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------

Only issue I found was Facebook comments being transparent and my carrier widget being transparent. It was solid otherwise.

Sorry for going OT.
[Nexus 5 Original Android Development] der_sascha:
is this working fine with latest r55 build