yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] szale9001:
Yea, it is definitely looking like a bug. I have been talking with Franco over on G+ about it. He said he'd look into it but he is having trouble reproducing it on his end. Tbh, so am I as it seems to be rather inconsistent. It seems to happen after suspend wakeup but beyond that I can't narrow down a way to get it to happen. Dmesg seems to report it as a thermal throttle but the tablet CPU temp is too low for that to be legit...
[Nexus 7 (2013) Original Android Development] L.F.B.:
Is happen exacly you said...

I close my tab with the smart case... wen reopen the max cpu turns 702...
[Nexus 7 (2013) Original Android Development] justibasa:
Same thing here. Weird. Oh well Franco well fix it. Franco can fix anything.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Yeah I didn't realize it until after I pushed r18. I'm almost finishing the fix, been at it for about an hour already. It's something in the Kernel thermal driver. Also input boost was also borked on r18, also fixed it on the local build.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Pushed r19.
[Nexus 7 (2013) Original Android Development] manishnraj:
look who is back :beer:
[Nexus 7 (2013) Original Android Development] paaaulo:
Does it work with deb?
[Nexus 7 (2013) Original Android Development] franciscofranco:
Deb has Lollipop? No, so no...
[Nexus 7 (2013) Original Android Development] L.F.B.:
Ok, using r19 for a couple of hours...

Till now all good here! Franco, we love you!:D
[Nexus 7 (2013) Original Android Development] habylab:
An update, hurrah! Thank you

Sent from my HTC One M8. Long live the Galaxy S3 and S. Those forums will be missed!
[Nexus 7 (2013) Original Android Development] diwakar2030:
Thanks for the update

Many thanks for the update. Using it from past 12 Hrs. Everything going Smooth here :)
[Nexus 7 (2013) Original Android Development] hasenbein1966:
Runs really fast and smooth with r19 here! Leaves a Nexus 9 in the dust! Great, thanks!
[Nexus 7 (2013) Original Android Development] bcote311:
Running great as usual! Thanks for the update Franco!
[Nexus 7 (2013) Original Android Development] osm0sis:
Thanks for the rebase Francisco!

I noticed the Linux revision is back to 3.4.0 instead of 3.4.88 where you had it before. I take it there's nothing terribly important in there, per usual, but I wanted to mention it regardless in case there was. :) :good:
[Nexus 7 (2013) Original Android Development] franciscofranco:
There's never nothing really really important on those minor patch-fix releases. Google is on .67 on their common branch but if they didn't merge it here or on their other msm devices I don't really care. 99% of the fixes are just for x86 or parts of the Kernel that are unused by our mobile devices.
[Nexus 7 (2013) Original Android Development] DNarsingh:
Hey guys, I have been off custom kernels for a while, but with lollipop being out, I would like to run this one again. Are you guys adjusting settings at all or should I just flash the kernel and leave it be with the default settings?
[Nexus 7 (2013) Original Android Development] franciscofranco:
Flash and forget!
[Nexus 7 (2013) Original Android Development] Ra1nst0rm:
[MENTION=3292224]franciscofranco[/MENTION]

I was trying to compile your kernel from source for learning,but I'm getting an error:

drivers/cpufreq/cpufreq_ondemand.c:177:27: error: conflicting types for 'get_cpu_idle_time'
static inline cputime64_t get_cpu_idle_time(unsigned int cpu, cputime64_t *wall)
^
In file included from drivers/cpufreq/cpufreq_ondemand.c:17:0:
include/linux/cpufreq.h:325:5: note: previous declaration of 'get_cpu_idle_time' was here
u64 get_cpu_idle_time(unsigned int cpu, u64 *wall, int io_busy);
^
make[2]: *** [drivers/cpufreq/cpufreq_ondemand.o] Error 1
make[1]: *** [drivers/cpufreq] Error 2
make: *** [drivers] Error 2

What should i do to fix it?
[Nexus 7 (2013) Original Android Development] L.F.B.:
LoL... Is this truth? This NVIDIA socs really "suks" :P
[Nexus 7 (2013) Original Android Development] szale9001:
I'm not an expert here, but if you are not using franco's defconfig or one with similar settings you could get errors like this if features are enabled that franco hasn't kept up with/purposely disabled.

From the above it looks like you have ondemand enabled in the defconfig and when it tries to compile it errors out. Since Franco doesn't enable ondemand for us, the code is probably messed up from lack of maintenance. You could prevent this particular error by disabling ondemand in the defconfig.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Use my config or simply disable Ondemand.

No, Denver chip is pretty amazing.
[Nexus 7 (2013) Original Android Development] drewski_1:
This is not Nvidia. You're thinking of 2012 version?
[Nexus 7 (2013) Original Android Development] zaclimon:
Use this commit:

https://github.com/franciscofranco/hammerhead/commit/7df417ba405e19c2e51f648667a7e621795f06c8

Looks like franco pushed it for the N5 but hasn't done so on the other devices (Probably because he disabled the ondemand on his own config)

Also [MENTION=3292224]franciscofranco[/MENTION] your config doesn't seem to be pushed on github. I suppose we have to use the regular flo's config in this case right?

I think he was talking about the Nexus 9's chip which is powered by Nvidia.
[Nexus 7 (2013) Original Android Development] franciscofranco:
You can get the config from /proc/config.gz but I can push it to git in heartbeat no problem.

There: https://github.com/franciscofranco/flo/commit/7c06816fa5c700e086d02e301e5133c23e9d690f
[Nexus 7 (2013) Original Android Development] szale9001:
Hey [MENTION=3292224]franciscofranco[/MENTION] , I hope you see this. Just found something that might explain a lot of the YouTube/video error reports going around (not necessarily on this thread).

When google increased the vmalloc to help fix the issue, they did so in the kernel's CMDLINE in the ramdisk. Turns out that particular addition did not make it into your kernel (I unpacked the image to check). I don't know if people are necessarily having issues on this thread, but on the google code thread, custom kernels are specifically mentioned (and also I have had issues).

https://code.google.com/p/android/issues/detail?id=79316#c326

So, I tried adding it to the console part of the ramdisk and it seemed to fix the issue (at least for now :p )

At the end of the day, the correct cmdline would look like this

I guess a lot of the video problems stemming from custom kernels may be a result of either this 'vmalloc' being left out or anykernel installs. I also figure, even if it doesn't fix everything long term, we should probably be including it for consistency's sake.
[Nexus 7 (2013) Original Android Development] zaclimon:
Thanks I was about to say that I've been getting the same video playback issues with youtube recently. I thought it was related to the inner kernel. Looks like it was a cmdline issue after all. :good:
[Nexus 7 (2013) Original Android Development] L.F.B.:
Yes, since the custom kernel my previous 5.0 playback issue is back to 5.0.1...

Anyway to fix this in franco kernel? This playback issue is killing me...
[Nexus 7 (2013) Original Android Development] DNarsingh:
I can confirm that I am having this playback issues with YouTube while using the kernel on a 5.0.1 rom.
[Nexus 7 (2013) Original Android Development] zaclimon:
Unless a kernel is recompiled with the right vmalloc allocation, there's no way out this issue.
[Nexus 7 (2013) Original Android Development] L.F.B.:
I have tried everything... Clean cache, disable nu player reboot... Nothing worked.

Good to know you discovered this issue. Franco will fix for us. Hes the man :)
[Nexus 7 (2013) Original Android Development] szale9001:
Actually I think it is way easier. Just unpack the ramdisk and add the vmalloc part to the end of the command line and repack. I did it pretty quick with Android Image Kitchen. Anyone feeling brave lol. This image is R19 with the one change I spoke of in the ramdisk.

No guarantees of course and boilerplate boilerplate...

Also may not hurt to clear YouTube data. I didn't, but, it wouldn't hurt :p
[Nexus 7 (2013) Original Android Development] zaclimon:
Yeah there's the ramdisk unpack/repack option also. Would save some time but I'm already accustomed to compiling anyway XD.
[Nexus 7 (2013) Original Android Development] L.F.B.:
How do we flash this? Only in bootloader?
[Nexus 7 (2013) Original Android Development] szale9001:
yea, or flashify I guess?

If in bootloader its

fastboot flash boot boot-r19_fix.img
[Nexus 7 (2013) Original Android Development] L.F.B.:
Just flashed your fix but the playback issue still persist...

Cleaned data from youtube only the first video work but wen go to another video, the black screen with problem appears... :'(

I think Ill go back to stock kernel till franco fix this... :-\
[Nexus 7 (2013) Original Android Development] JassyNL:
Thanks Franco for both your kernels which I've installed on my Nexus 5 and Nexus 7 2013. Both work like a charm !!
[Nexus 7 (2013) Original Android Development] szale9001:
Sorry to hear. Weird too, as it seems to have made the difference for me. I'm still able to play youtube vids and before I had the exact problem you just described.
[Nexus 7 (2013) Original Android Development] L.F.B.:
Im having problem with embed video in pages...

I think is related to this playback issue... Im having problems in all browser chrome, opera...
[Nexus 7 (2013) Original Android Development] zaclimon:
Yep I had issues with embed videos as well. Looks like this fixes for me. It's weird that your device still acts up weird. Do you have these issues with the stock kernel as well?

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] L.F.B.:
No, Ive just flashed back the stock 5.0.1 kernel did a clean data in all browsers, youtube and enabled nu player in dev options...

Till now all seems fine...
[Nexus 7 (2013) Original Android Development] msgfromside3:
This is the first flash for me (was on stock) and I have no issue with your fix.
[Nexus 7 (2013) Original Android Development] szale9001:
Yea, I came home tonight and tried it out again and everything is still good (Youtube and embedded). Definitely looking like that was the missing piece...

Still though, :fingers-crossed:
[Nexus 7 (2013) Original Android Development] franciscofranco:
Thanks for the lively discussion. I'll check this once I'm back home :)
[Nexus 7 (2013) Original Android Development] osm0sis:
Adding init.d and darmonsu root service support back would also be pretty sweet. :)
[Nexus 7 (2013) Original Android Development] franciscofranco:
darmonsu or daemonsu? :p
[Nexus 7 (2013) Original Android Development] L.F.B.:
Thanks again Franco. We are very happy with your attention besides your huge time working on all nexus devices :)

Edit:

Finally I bought FK updater for my N5 and 7 and now Im officially a menber of FK comunity and beta teste! Yeay! :D
[Nexus 7 (2013) Original Android Development] fritzcola:
Is it compatible with Cm 12?
[Nexus 7 (2013) Original Android Development] zaclimon:
No it is not, only compatible with AOSP roms.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] franciscofranco:
Sorry for not saying anything about the video thingy, I've slept 10 hours the last 3 or so days, been working on FKU non-stop. Will look at this tonight.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Please test the boot.img below. I played a couple youtube videos and they were flawless.
[Nexus 7 (2013) Original Android Development] L.F.B.:
Flashed and embed video from this page working smooth now:

http://sg.hu/forum/tema/1118059139

Viral app working good and youtube... All seems fine for me now :)
[Nexus 7 (2013) Original Android Development] hardwareadictos:
+1
[Nexus 7 (2013) Original Android Development] DNarsingh:
I flashed as well and everything is working fine so far.
[Nexus 7 (2013) Original Android Development] szale9001:
So besides the cmdline change, anything else different?
[Nexus 7 (2013) Original Android Development] mikejr83:
It has moar unicorn tears. :)
[Nexus 7 (2013) Original Android Development] szale9001:
damn... i was really hoping for moar cat upgrades
[Nexus 7 (2013) Original Android Development] L.F.B.:
Chill out, were still beta... And Franco is doing pretty good so far for us...
[Nexus 7 (2013) Original Android Development] sonofevil77:
Sorry I'm having a brain fart. Can I flash this in recovery or fastboot only?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] L.F.B.:
If you have bought FKU you can flash with the buit in file manager.

We also have flashify and rarshr in playstore.
[Nexus 7 (2013) Original Android Development] sonofevil77:
I own FKU.thanks for the quick response!

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] szale9001:
Relax, I was only making a joke :good:
[Nexus 7 (2013) Original Android Development] franciscofranco:
Pushed r20 with the video fix!

Some misc commits with a couple fixes from the newest N4 source push and some others from upstream.
[Nexus 7 (2013) Original Android Development] szale9001:
Gotcha. Well, as always, thanks very much for the effort. Now, get some more sleep lol
[Nexus 7 (2013) Original Android Development] franciscofranco:
Sleep is overrated :)
[Nexus 7 (2013) Original Android Development] zaclimon:
Asking to people who is compiling perhaps their own builds of FK, have you got an issue while compiling your own zImage? I've been trying but I can't get my zImages to boot, only Franco's work though. :confused:
[Nexus 7 (2013) Original Android Development] poondog:
Are you using a toolchain higher than GCC 4.7? My builds (not franco kernel) will not boot with 4.8+
[Nexus 7 (2013) Original Android Development] zaclimon:
Yeah, I've been using 4.8 and 4.9. That's strange hmm, I could use 4.9 with some tweaks on KK.

Alright then, I'll use 4.7.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] poondog:
If you're able to boot something new let me know :)
[Nexus 7 (2013) Original Android Development] zwliew:
https://github.com/zwliew/flo/commit/fd23da5ce72616dfe17cdebb8c7630f9ef9b9d85

https://github.com/zwliew/flo/commit/41ad677fbb0291ca8bc1756055bbeb2e986b6198
[Nexus 7 (2013) Original Android Development] poondog:
Hi sir, is this working for you? I have this in my kernel and its in the stock kernel too I believe

Edit: its in the 3.4.70 patchset too
[Nexus 7 (2013) Original Android Development] zaclimon:
I remember having updated my kernel up to 3.4.104 and it still wasn't working hmm.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] petran_7:
I read that it will work with rastakat. Will the latest version work with rastapop? http://xdaforums.com/showthread.php?t=2487664

on Nexus 7 2013
[Nexus 7 (2013) Original Android Development] drewski_1:
Yes. 2nd line of OP ?
[Nexus 7 (2013) Original Android Development] zaclimon:
[MENTION=5604178]zwliew[/MENTION] I confirm that the patches you sent me are working. Thank you dude!! I'm wondering as of why they weren't included in the later Linux patches like [MENTION=4379011]poondog[/MENTION] said. :confused:
[Nexus 7 (2013) Original Android Development] poondog:
Did you merge from kernel.org or from someone else's git? I always get them from kernel.org

They have always been in my source I just thought something else was needed so I didn't try anytihing else lol

http://lwn.net/Articles/574436/

^thats the 3.4.70 article that outlines the changes, they're there

Which toolchain did you use now?

Do we need a kernel discussion thread lol
[Nexus 7 (2013) Original Android Development] zaclimon:
I took them from another git. Sadly doesn't looked like it was there. Oh well, next time, I'll go the kernel.org way! Anyway let's end this clutter as this thread isn't a kernel discussion one. XD

Btw I'm using the SM-4.9 toolchain.
[Nexus 7 (2013) Original Android Development] poondog:
Woop, mine boots too!

/ot
[Nexus 7 (2013) Original Android Development] fritzcola:
Found a bug.

Installed v20 on Euphoria OS and after that i dont have any navigation bar(only back key)!!
[Nexus 7 (2013) Original Android Development] idCyber:
I can confirm. Just tried out with Euphoria OS and Franco and navigation buttons dissapear and only back button remains. If I reflash the ROM and I go with Glitch or ElementalX, the navigation bar is fine.
[Nexus 7 (2013) Original Android Development] baturcotte:
Does the r20 kernel still have the kexec-hardboot patch? I went to install Multirom v30, and it claims the patch isn't there...
[Nexus 7 (2013) Original Android Development] zephiK:
No it was removed because it breaks encryption.
[Nexus 7 (2013) Original Android Development] klaust58:
Not nice.

But there are other good kernels with this patch available. Thats why my franco-experience ends with 4.4.4. :(

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] zaclimon:
Don't want to make any promotion but here's something that's similar to Franco and has the kexec patch

http://xdaforums.com/showthread.php?t=2809979

Also it is said that Franco may add back the patch in a newer release.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] klaust58:
Cool, thanks!

I will try this asap ☺

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] habylab:
Working well.

Can't seem to keep my Max CPU or sound settings on reboot. I've set to different values, and to stick on boot, but they always revert to the default.

Had this on the last few versions, KK and L. Data wipe doesn't help, either.

Sent from my Nexus 9 (2015). My phone is a HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] 777.300:
Hi Franco, Thanks again for all your great work, my N7 is running great with your latest lollipop kernel.

One question: had to pull some tricks to get Viper4android working again on my Nexus 7 lollipop, which is very important to me, cannot live without that superb audio mod.

http://xdaforums.com/showthread.php?t=2951546

The above link shows the solution to get Viper4android working on my N7 and my question is now do I really need the SELinuxModeChanges app running in the background to set/leave the kernel in Permissive mode?

P. S. Just found out that switching back to enforcing mode stops Viper4android. So my question should be: is it bad / harmful to operate my Nexus 7 with your kernel in Permissive mode?

Verstuurd van mijn Nexus 7
[Nexus 7 (2013) Original Android Development] gravedigger76:
Hi

Will there be support on this kernel with the latest CM12 nightlies on flo?

Looks like flo with CM is not aosp.

Thanks
[Nexus 7 (2013) Original Android Development] lemene:
You can find one here:

"Originally Posted by h0tkey

Yes, this one. http://xdaforums.com/nexus-7-2013/development/kernel-sabermod-franco-r17-t2809979

With it, DT2W can be enabled in /system/etc/touchcontrols.sh.
[Nexus 7 (2013) Original Android Development] L.F.B.:
Master Franco.

It seems the new 5.0.2 update broke the r20 flashing...

I just try to flash and nothing happens.

Thanks for your attention :)
[Nexus 7 (2013) Original Android Development] Hatshipuh:
No problems here with 5.0.2 and flashing r20.

Must be something on your end.

Tap-a-talked from my Nexus 5
[Nexus 7 (2013) Original Android Development] L.F.B.:
I just flashed in recovery and all fine. Maybe my dirty flash messed up the autoflash...

But now all working smooth :)
[Nexus 7 (2013) Original Android Development] compuguy1088:
The nexus 7 2013 LTE bootloops with the latest franco kernel (using the factory image, with this kernel's boot.img).
[Nexus 7 (2013) Original Android Development] L.F.B.:
Yes, this is only for wifi. I think the new rom for LTE N7 have a diferent kernel...

We need to wait feedback from Franco...
[Nexus 7 (2013) Original Android Development] compuguy1088:
Funny thing is this kernel is linked in a sticky thread in the LTE development thread.
[Nexus 7 (2013) Original Android Development] shreddintyres:
That's because initially Flo and Deb were both running the same kernels on kit kat then that began to deviate on google's side of things. Then when lollipop released deb wasnt updated until a few days ago. I'm sure there will be a compatible build in the future. But franco has stated one way or the other that secondary devices namely tablets dont get much support from him becuase he focuses on mainline devices (phones specifically).

There will likely be returned support for Deb but it may not be for some time as Franco's current projects keep him busy on phones and on a new app he is developing not to mention his continued support and work on FKU.
[Nexus 7 (2013) Original Android Development] compuguy1088:
Thanks for the clarification. I understand the need for priorities (he does support a large amount of devices). I resolved the issues I was having previously (nightly issues).
[Nexus 7 (2013) Original Android Development] runt:
Really looking forward to deb getting support again since it now has Lollipop. Running CM and I always ran franco kernels in the past when using CM.
[Nexus 7 (2013) Original Android Development] fenixus:
Awesome kernel! My n7flo loves it :)
[Nexus 7 (2013) Original Android Development] jordirpz:
is the nexus 7 forgotten?
[Nexus 7 (2013) Original Android Development] php5_developer:
Yes

Sent from N7 2013
[Nexus 7 (2013) Original Android Development] php5_developer:
Franco seems to be busy with newer devices, time to move on guys

Sent from N7 2013
[Nexus 7 (2013) Original Android Development] osm0sis:
Quit trolling.
[Nexus 7 (2013) Original Android Development] paaaulo:
Is there r20 with a deb ramdisk modified by you?
[Nexus 7 (2013) Original Android Development] osm0sis:
Try using my Android Image Kitchen to repack the factory image deb boot.img ramdisk with Franco's r20 zImage. Let us know how it goes!
[Nexus 7 (2013) Original Android Development] paaaulo:
[MENTION=4544860]osm0sis[/MENTION]

It works fine. Thank you.
[Nexus 7 (2013) Original Android Development] sd_matto:
deb issues

Tried the AIK run directly from my N7 deb. Successfully built two different versions of a hybrid kernel for deb based on franco's R20 (using deb ramdisk). Two hybrids were:

1. Replace JUST the zImage from the "split-image" folder with franco's zImage; and

2. Replace the entire "split-image" folder (which includes the stock zImage) with franco's entire "split-image" folder (which includes franco's zImage).

I am probably using the AIK wrong (fully admit I am a newbie with this).

With both hybrid kernels, the tablet booted up, but when I tried to change the governor from performance to interactive, the tablet crashed.

Help/thoughts appreciated.
[Nexus 7 (2013) Original Android Development] osm0sis:
Probably just some governor permissions stuff missing from the ramdisk since it's full Google. You could try an AOSP/CM deb ramdisk instead.
[Nexus 7 (2013) Original Android Development] sd_matto:
Thanks for the quick response. Will try that out.

Just so that I am sure that I am doing things right, am I supposed to be utilizing approach 1 above (i.e., JUST the zImage replacement in split-image folder) or approach 2 above (i.e., entire split-image folder replacement)?

Thanks again.
[Nexus 7 (2013) Original Android Development] osm0sis:
Either works. Contents are probably about the same. Check the cmdline. With the vmalloc stuff we were talking about awhile back which affects video playback performance, that'd be the only really important thing.
[Nexus 7 (2013) Original Android Development] fenixus:
First, great work on this kernel, thanks for maintaining it. Kernel works flawlessly on my n7flo, but looks like battery life degraded significantly since flashing it. I'm not overclocking cpu now and with mostly book reading few hours a day on tablet it doesn't last 2 days. It drains down even when not in use. Stock kernel was much more forgiving...