yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] 777.300:
Nice work Franco, great to have your kernel also back on the N7. Thanks for all your great work and long device support. Now waiting for Simple ASOP to update the N7 ROM to 6.0.1 before flashing, it is still on 6.0. But when that takes to long I will switch to another ROM. Any suggestions?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] androidsnax:
Woohoo! No more tablet dying unexpectedly ?

***edit: although, this is usually due to young son not plugging back in after watching YouTube videos of construction vehicles! ?

Sent from my Nexus 5X
[Nexus 7 (2013) Original Android Development] seba112:
[MENTION=3292224]franciscofranco[/MENTION]

On Deb stuck on:

https://www.dropbox.com/s/ld94zz1qfj4su0t/20160109_124904.jpg

ROM - stock 6.0.1 with root.
[Nexus 7 (2013) Original Android Development] osm0sis:
What ramdisk did you base this off? A whole bunch of stuff doesn't match up (performance profiles don't have the setprop command, cores are turned off for power saving, etc.). r21 was more updated than that.

Edit: Francisco has since informed me both of these things were intentional and he remade the ramdisk from scratch. :good:
[Nexus 7 (2013) Original Android Development] jordirpz:
[MENTION=4544860]osm0sis[/MENTION]

Can i flash you r79aka2 kernel directly above r79? Thanks
[Nexus 7 (2013) Original Android Development] osm0sis:
You're in the wrong thread buddy. And no, that would be pointless.

That said, since I'll be uploading my r23 zip soon, I'll reiterate the correct procedure for AK2 zips, which is the same on all devices. You should flash it over the ROM's boot.img (dirty flash the ROM if you have to), flash the lastest SuperSU zip (if needed), then flash the AK2 zip.
[Nexus 7 (2013) Original Android Development] jordirpz:
Ok, thanks & sorry.

Maybe you think open thread about you kernels?
[Nexus 7 (2013) Original Android Development] zaclimon:
[MENTION=3292224]franciscofranco[/MENTION] Is it normal that nothing happens when trying to set a Min or Max CPU frequency? I suppose that would be something related to the new cpu boost driver that you've put and that it wouldn't change anything except for the values shown on the screen right?

Honestly, I would only know if the cpu's return to the min freq or they keep the current CPU Boost driver freq?
[Nexus 7 (2013) Original Android Development] osm0sis:
No. They're not my kernels.
[Nexus 7 (2013) Original Android Development] osm0sis:
This should work for both flo and deb, all ROMs, all root types, and I fixed the ramdisk issues I mentioned to [MENTION=3292224]franciscofranco[/MENTION] above.

franco.Kernel-flo-r23-AK2-signed.zip:

https://s.basketbuild.com/devs/osm0sis/osmods/ -- http://v.ht/osmods
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION] can you add back kexec-hardboot for MultiROM support? Also the lower min brightness seems a bit too aggressive now.
[Nexus 7 (2013) Original Android Development] zaclimon:
Just wondering, is it normal that the current CPU freq is always staying at the input boost one even when nothing is being done in the device? (With all 4 cores)
[Nexus 7 (2013) Original Android Development] seba112:
[MENTION=4217103]zaclimon[/MENTION]

I have the same issue.
[Nexus 7 (2013) Original Android Development] L.F.B.:
Thank you master Franco for keepin' Nexus 7 alive!

And master osm0sis for your amazing work to make the best kernel availiable for CM roms!

I love you both! :good::good:
[Nexus 7 (2013) Original Android Development] osm0sis:
For me it only happens to cores 1-3, 0 still scales back down to the min. Weird indeed. Guess cpu-boost needs some work [MENTION=3292224]franciscofranco[/MENTION].
[Nexus 7 (2013) Original Android Development] Srandista:
Yeah, I found out, that RGB settings have no efect what so ever.

Also, where I should put some display presents, so the option for load them will show in FKU?
[Nexus 7 (2013) Original Android Development] osm0sis:
They do, you just have to screen off a couple times.
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION], rollup for you.
[Nexus 7 (2013) Original Android Development] zaclimon:
Maybe he'll see this?
[Nexus 7 (2013) Original Android Development] BS86:
got that too on my deb - and also a quite strange explanation. MMB29O leaves only 3MB free on /system. Rooting and flashing busybox with NRT already filled my /system so that TWRP claimed it has 0MB left - but still allowed me to flash Xposed and the r23 kernel - although on later tries to recreate the problem, flashing xposed already failed - could it be that the detection of space issues while flashing is broken or not apparent in TWRP?

because after deleting some system apps, flashing and booting worked smoothly ;)

thanks, works great on deb ;)
[Nexus 7 (2013) Original Android Development] bautrupp:
Kernel flashes to boot partition not to /system.
[Nexus 7 (2013) Original Android Development] franciscofranco:
r24 is up. Me and [MENTION=4544860]osm0sis[/MENTION] went through some things last night so here we go!
[Nexus 7 (2013) Original Android Development] osm0sis:
franco.Kernel-flo-r24-AK2-signed.zip:

https://s.basketbuild.com/devs/osm0sis/osmods/ -- http://v.ht/osmods
[Nexus 7 (2013) Original Android Development] franciscofranco:
Y U STEALING MY MOJO?
[Nexus 7 (2013) Original Android Development] osm0sis:
Haha thought you might want to add the link to the OP here like you did in the hammerhead thread, especially since it has deb support. :p

I also cleaned up the AK2 script to actually comment out whole services like you did, and make it so that from r24 onward someone could just flash the AK2 zips over the previous and not worry about any issues because it'll detect tweaks are already applied, or replace the ones that are there (which is what people should be shooting for in an AK2 zip). :D :good:

So ROM's default boot.img -> SuperSU -> AK2 initially, and then flash AK2's over top to update just the zImage and any newer tweaks forevah! :cool:

Also, congrats on 100,000 Thanks! I think I was 100,010 just now. What's the next milestone 101,010? ;)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Been using this Kern for a few hours now...very snappy...kudos to Franco and yourself.

Very impressive.
[Nexus 7 (2013) Original Android Development] osm0sis:
Any reports from deb users with the r24 AK2?
[Nexus 7 (2013) Original Android Development] seba112:
I will check on Deb tonight.
[Nexus 7 (2013) Original Android Development] seba112:
Wifi not working on Deb :/
[Nexus 7 (2013) Original Android Development] lanpot:
Same there, no wifi
[Nexus 7 (2013) Original Android Development] osm0sis:
Damn. I'm not sure about r23 AK2, but I definitely remember deb being reported working with r21 AK2... I'm just waking up now, but I'll make a test zip later today that only flashes the zImage over (no tweaks) to test and rule out the possibility that the AK2 ramdisk changes could be at fault. Sit tight. :good:
[Nexus 7 (2013) Original Android Development] osm0sis:
deb users, flash your ROM's default boot.img (extract it from the ROM zip if you aren't on Stock ROM and don't have a backup), then flash the following zip.

Let me know if/how WiFi performs.

[ test zip removed - it worked ]
[Nexus 7 (2013) Original Android Development] lanpot:
Just tested, wifi is OK now.

I'm pleased to get FK working on deb?
[Nexus 7 (2013) Original Android Development] osm0sis:
Okay, now please try the updated one on my BasketBuild:

https://s.basketbuild.com/devs/osm0sis/osmods/

It's using the new organization [MENTION=3292224]franciscofranco[/MENTION] will be officially supporting soon. :D
[Nexus 7 (2013) Original Android Development] lanpot:
I have juste flashed stock and the updated zip?

No bootloop, better than FK...

But still unable to activate wifi. Only LTE avalaible.
[Nexus 7 (2013) Original Android Development] seba112:
For me this same issue, wifi not working.
[Nexus 7 (2013) Original Android Development] osm0sis:
Interesting that means it's something in one of the WiFi-unrelated AK2 tweaks. Can you look in init.flo.rc and see what's commented out?

Point me at your ROM zips, I'll try to figure out what's going on.
[Nexus 7 (2013) Original Android Development] seba112:
My init.flo.rc:

https://www.dropbox.com/s/t3imd1iq3explbs/init.flo.rc

From 6.0.1 MMB29K
[Nexus 7 (2013) Original Android Development] osm0sis:
Great now can you send me one from when the wifi is broken? I can diff them and will hopefully be able to figure out where things went wrong. :)
[Nexus 7 (2013) Original Android Development] osm0sis:
I think I figured it out anyway.

[MENTION=5781460]seba112[/MENTION] [MENTION=5628432]lanpot[/MENTION] [MENTION=4020672]part2style[/MENTION] I uploaded another to my BasketBuild, please flash your ROM's default boot.img then it and let me know if WiFi is working. :)
[Nexus 7 (2013) Original Android Development] lanpot:
Juste tried, both LTE and WiFi are OK.

Thanks to both?
[Nexus 7 (2013) Original Android Development] seba112:
On My N7, wifi still not working.

Here my init.flo.rc, when wifi not work:

https://www.dropbox.com/s/t3imd1iq3explbs/init.flo.rc?dl=0
[Nexus 7 (2013) Original Android Development] osm0sis:
Worked for 2 out of 3 of you. Did you remember to flash your ROMs default boot.img first? Please also make sure you've got my latest upload and try again.
[Nexus 7 (2013) Original Android Development] seba112:
Yes, I remember to flash stock kernel.
[Nexus 7 (2013) Original Android Development] osm0sis:
What recovery? Please download again and try again.
[Nexus 7 (2013) Original Android Development] seba112:
Latest TWRP. I trying two times and no change :/
[Nexus 7 (2013) Original Android Development] osm0sis:
I uploaded a new one at 4am. You've tried that? It works for the other deb guys now, and there's no reason I can think of it shouldn't work for you in TWRP.. :confused:
[Nexus 7 (2013) Original Android Development] seba112:
I flash new version two hours ago.

I will try again, I may succeed ^^

Ehh, wifi working, earlier I flash kernel from primary directory, new version I had in /Download...
[Nexus 7 (2013) Original Android Development] osm0sis:
Thought so! Thanks! :)
[Nexus 7 (2013) Original Android Development] seba112:
[MENTION=3292224]franciscofranco[/MENTION]

Can You add Ondemand CPU governor, is more battery friendly than interactive.
[Nexus 7 (2013) Original Android Development] justibasa:
That probably won't happen.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Show me numbers Ondemand vs Interactive to back that up. If you can prove that I'll add it ?
[Nexus 7 (2013) Original Android Development] seba112:
Ehh, You win :D

Galaxy S6™
[Nexus 7 (2013) Original Android Development] BS86:
Don't want to disappoint you, but 5Ghz wifi is not working, 2,4Ghz works fine.

I am on MMB29O stock with supersu 2.66 - was on Stock kernel until now.

What do you need to debug?

Edit: sorry my bad... Just found out that most nexus devices including the n7 don't work on DFS channels 52 - 140 and my Router was using 52 on autochannel - now on channel 44 everything works fine [emoji2]

Edit2: just found out that DFS channels should work since marshmallow and I can't believe that my router never used those channels while on Stock kernel (I have that router since 6 weeks) - could it be that this support still needs to be added to the kernel [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 7 (2013) Original Android Development] franciscofranco:
Nope, I have all N7 2013 commits from Google.
[Nexus 7 (2013) Original Android Development] BS86:
just checked again and on MMB29K and MMB29O stock kernel, the DFS channels are working - on the updated r24 release by @osm0sis the deb fails to see the SSIDs on the DFS channels.

I suppose logs won't help as it does not even see the channels, is there anything else that could be of help?
[Nexus 7 (2013) Original Android Development] osm0sis:
Copy and paste the contents of your init.flo.rc to pastebin.com and I'll see if we can rule out AK2. :good:
[Nexus 7 (2013) Original Android Development] BS86:
Here you are [emoji16]

http://pastebin.com/5jQgmCxa

Sent from my Nexus 7 LTE using a TARDIS
[Nexus 7 (2013) Original Android Development] osm0sis:
Looks perfect. AK2 can be ruled out. Only thing that crosses my mind is that thermald is part of the radio group, and [MENTION=3292224]franciscofranco[/MENTION] has that disabled as part of his usual ramdisk tweaks (as you can see in the file you posted). I can't see what thermal throttling would have to do with accessing the DFS channels, but that's the only vaguely thing on the ramdisk side that I notice.

Edit: [MENTION=5077573]BS86[/MENTION] You can test to see if it's just a kernel source difference by flashing stock kernel via fastboot flash boot boot.img, then doing: fastboot flash zimage zImage

You'll need to extract zImage from the AK2 zip first, but that will use the Stock kernel's ramdisk with the f.K zImage, no other changes. Let us know if the DFS channels work or not afterward.
[Nexus 7 (2013) Original Android Development] BS86:
Thanks, will do so, but won't have access to my N7 until Sunday - will report as soon as I got it done

Sent from my D5503 using a TARDIS

Edit: [MENTION=4544860]osm0sis[/MENTION] : Have tried that, and with the stock kernel + your zImage, the DFS channels did not work. BUT: I have reflashed stock again afterwards and now, the DFS channels are also NOT working on stock kernel - therefore please don't waste time on fixing this as I can not yet tell for sure if its a hardware fault on my N7 or a fault of my router or a bug that also occurs randomly on the stock kernel .... (I know that DFS channels can sometimes be blocked due to radar, but my router tells that in the logs, and there is no such entry in the last 2 days)
[Nexus 7 (2013) Original Android Development] :
Hi [MENTION=3292224]franciscofranco[/MENTION]. Are you going to make an anykernel for this device? I have that on my 6P that come out the good result. Thanks!
[Nexus 7 (2013) Original Android Development] franciscofranco:
Yup, coming ASAP.
[Nexus 7 (2013) Original Android Development] masri1987:
I've been having a peculiar issue.

N7 2013 this Mo rom + glitch kernel , if i don't turn it off once a day, the screen responsiveness gets flaky, not sure how to explain it, i have a glass screen protector on it too, so i'm not sure if it's that (but it works fine when i reboot it flawless)

Any ideas?
[Nexus 7 (2013) Original Android Development] quickdraw86:
It'd be a great idea to pose this question in the glitch thread, as opposed to this one. I see that you posted in the morom thread, but, ROM threads aren't meant to provide users with support for custom kernels not included with the individual ROM...

http://xdaforums.com/showthread.php?t=2449919
[Nexus 7 (2013) Original Android Development] masri1987:
LOL truth be told, i was intoxicated when i made this post, i did intend for it to go to the glitch thread. thank you for being kind -
[Nexus 7 (2013) Original Android Development] osm0sis:
For what it's worth this used to be an issue on both stock and franco.Kernel r23 but Francisco and I troubleshot it and I haven't seen it yet in r24. He added some graphics driver memory leak fixes, some LMK and some Moto patches that improve memory usage. My device was usually at 500-600 free memory, getting worse when the stuttering, touch lag, etc. was happening and now it tends to sit at 800-900 and it's smooth smooth smooth.
[Nexus 7 (2013) Original Android Development] masri1987:
i'd totally use r24, i just remember there is no double tap to wake, i have the tablet in my dash in the car.
[Nexus 7 (2013) Original Android Development] BS86:
is the only way to report bugs of the FKU through the G+ page? The achievement for changing Governor and autoflashing from filemanager is not working (they were not working before the 14.1 update, too), however kernel autoflash, download a kernel, backup a kernel, learner, the opener and the donation achievements are working.
[Nexus 7 (2013) Original Android Development] osm0sis:
I stand corrected! Managed to reproduce it finally and sent [MENTION=3292224]franciscofranco[/MENTION] some logs. For what it's worth it's still far more difficult to trigger on r24 than on previous builds or stock.

While we wait for him to look through and sort things out for r25, I've uploaded my r24-AK2 again to my BasketBuild. This has been updated to the same branch of AK2 I worked out for Franco for the latest FKU so feel free to flash it from the FKU File Manager to get a taste of what's next. :)

http://v.ht/osmods -- https://s.basketbuild.com/devs/osm0sis/osmods/
[Nexus 7 (2013) Original Android Development] BS86:
It's me again with a stupid "problem" :p

I realized that the battery life of my N7 is not extremely bad, but it is worse than on stock kernel. On stock kernel my battery lasts for 3-5 days, while on FK, it lasts only 2-3 days. (MMB29Q stock is my ROM)

Wakelocks and the deepsleep ratio have not changed, and also my usage has not changed so I tried to find the reason for that.

The only obvious thing that is different is the behaviour of the cores. On stock, 2-3 cores go offline in low and mid load situations, and the one to two active cores take the load, on complete idle (e.g. when reading something) 3 cores are offline and one idles at 384MHz.

On FK, no matter which governor I choose, all 4 cores stay online but idle at 384 MHz at complete idle situations, and on low to mid load situations all cores are at speeds up to 1512 MHz.

There is no other app that changes the settings and in FKU all settings are at standard settings.

Is there a setting to change the activation behaviour of the cores on FK that I fail to find? Or is this cores staying online "problem" caused by something else? Which logs would be helpful and what should I do that needs to be in the logs?

Edit: this behaviour is also the same on your last update from today, @osm0sis
[Nexus 7 (2013) Original Android Development] osm0sis:
Check the changelog.
[Nexus 7 (2013) Original Android Development] BS86:
oh ... thanks :eek: missed that: "All cores are online during screen on since they hit idle way more often than stock when they have no tasks running"

but still, is there a setting to change that behaviour? I have the strong presumption that cores going offline in idle would save a lot more battery than staying idle at 384MHz - especially when the device is used a lot for reading and browsing, meaning screen on but nothing to do.

the other behaviour in low and mid load situations does not really bother me, I understand that jobs being done at higher freq leads to them being done faster and therefore idle is hit earlier again :o.
[Nexus 7 (2013) Original Android Development] Doo Doo:
[MENTION=4544860]osm0sis[/MENTION] I can't get your Franco any kernel to work on my Flo with PacRom for some reason but on my OnePlus One the Franco any kernel works like a charm with PacRom
[Nexus 7 (2013) Original Android Development] osm0sis:
What happens on Pac ROM? It's possible they've changed something that throws things off.
[Nexus 7 (2013) Original Android Development] Doo Doo:
It boots up real slow then runs super slow when booted & the colors are inverted
[Nexus 7 (2013) Original Android Development] osm0sis:
So it's CAF?
[Nexus 7 (2013) Original Android Development] Doo Doo:
I'm not to sure but if it is you think you could try to make me a compatible Franco kernel to work with it

Or maybe its because I'm still on lollipop instead of marshmallow I don't really know
[Nexus 7 (2013) Original Android Development] osm0sis:
Yeah both of those are reasons I can't make it compatible due to driver differences.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Yeah, PAC is CAF.

Franco doesn't now, and according to what he's said in the past, will not ever build kernels based on CM sources.
[Nexus 7 (2013) Original Android Development] Doo Doo:
I think r21 was the last Franco kernel working with Android version 5.1 you think you could make that a any kernel & let me see if that works

---------- Post added at 12:33 AM ---------- Previous post was at 12:29 AM ----------

Yea but what's weird about it is that the Franco any kernel for the OnePlus One works on PacRom so there shouldn't be any difference than the devices being different
[Nexus 7 (2013) Original Android Development] quickdraw86:
If-this-then-that logic doesn't apply to development well. I don't own a OPO, but have read before that OPO is an exception for Franco, as his kernel for that device is based on cyanogenmodOS, and he has said that it should work on any 5.1.1 custom ROM for that device. His nexus kernels are based on Google/AOSP, and he won't ever produce CM variants for nexus devices he supports.
[Nexus 7 (2013) Original Android Development] Doo Doo:
Which is understandable which is why I'm trying to get osm0sis to help me out ;)
[Nexus 7 (2013) Original Android Development] osm0sis:
It won't. AOSP kernels will never work with CAF ROMs, end of story.
[Nexus 7 (2013) Original Android Development] Doo Doo:
Then why does it work on the OnePlus One? Same Franco Kernel & same ROM (PacRom) being used just different devices.

Also out of curiosity I flashed the newest cm13 nightly to my Flo just to see if your Franco (Any Kernel) r24 would work with it & it didn't why not?
[Nexus 7 (2013) Original Android Development] osm0sis:
His 1+One kernel isn't AOSP, it's CAF. It's not an AOSP device and his general support of it is a special case. This has already all been explained to you.

There were forks of the flo franco.Kernel which users made that had the necessary commits to work on CAF ROMs but I'm not sure they've kept them up to date. Search for them if you want to try them, and if you're that set on having franco.Kernel r24 running on a CAF ROM, I suggest you look into building it yourself.

As for CM13, probably the same story.
[Nexus 7 (2013) Original Android Development] Doo Doo:
Come on bro if I knew how to build it myself I would not be on here asking for help would I ?

But if you can't help me its all good I'll look for it somewhere else thanks for trying anyways.
[Nexus 7 (2013) Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] I have made some test with my Flo and i have found some issue with your kernel; when i set the max brightness screen goes into blinking mode. With stock kernel is all ok without any problem
[Nexus 7 (2013) Original Android Development] 777.300:
Hi Franco, Any chance on a official Any Kernel version?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] quickdraw86:
He said back on April 26th that flo was coming, and he's been releasing AK kernels for other devices, so, you never know.
[Nexus 7 (2013) Original Android Development] Srandista:
Guys, can someone test, if OTG is working on your Nexus 7 with FK?

EDIT: Never mind, wrong OTG cable.
[Nexus 7 (2013) Original Android Development] binuralka:
hello I flashed the latest r24 boot.img over my stock 6.0.1 using twrp. After I rebooted and have usual experience..does thia kernel provide some kind of a user interface or what app should I use to control stuff?

thanks indeed for work!
[Nexus 7 (2013) Original Android Development] quickdraw86:
FKU
[Nexus 7 (2013) Original Android Development] binuralka:
quickdraw86,

no, the kernel was already installed :) I am looking for an app that will help to control things like cpu freq. or other feautures of the kernel.
[Nexus 7 (2013) Original Android Development] quickdraw86:
The free version updates only, the paid version is the kernel manager. Those are the official apps for FK. Otherwise, just use kernel adiutor, trickstermod, or whichever other app you like.
[Nexus 7 (2013) Original Android Development] jordirpz:
Vamos a contar mentiras tralara, vamos a contar mentiras tralara, vamos a contar mentiras.