yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] sgt. meow:
GEL can rotate properly. I can confirm that.

I know this sounds stupid, but maybe the auto-rotate option isn't checked.

Otherwise, you may have to try wiping and re-installing.

Shouldn't be kernel-related.
[Nexus 7 Original Development] montresor60:
Running Purify as a secondary (soon to be primary) in MultiRom. Booted to TWRP recovery, selected MultiRom, selected installed Purity ROM, deleted boot.img, installed R76 boot.img

Success!

Thanks, Francisco!
[Nexus 7 Original Development] andrew9292:
I noticed with the default minimum Cpu frequency of 102MHz, the governer goes 'hunting' between much higher frequencies during idle / no touch.

It then falls back down to 102MHz for awhile then goes hunting again.

As if it realizes 102Mhz is too low to sustain anything and ramps all over the place, repeating the cycle.

Is this intended behaviour?

Setting it to 204MHz changes it. Idle steady at 204MHz.

Wouldnt this save more batt during no touch / screen on idle?

Any chance for usb audio too?

r76, Purity Rom 4.4 latest (02/12)
[Nexus 7 Original Development] Samu 17:
I don't know if anybody ask this but can it be possibile to get sweep2wake?

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 Original Development] osm0sis:
The issue might be that whatever app you're using to monitor the current frequency is what's driving it up.
[Nexus 7 Original Development] andrew9292:
Hmm... That possibility came into my mind too. I know i shouldnt be bothered too much cuz this is a real good kernel but forgive me. What's the best way to monitor cpu speeds then? Any suggestions?
[Nexus 7 Original Development] osm0sis:
Lowest impact way would be to run a shell script that reads scaling_cur_freq every second and outputs it to file.
[Nexus 7 Original Development] andrew9292:
Aha. Okei, thanks for info!
[Nexus 7 Original Development] skintosh:
Anyone have any ideas why I am getting a bootloop every time I install? Doing it via fku auto install and it's happening every time.

Having to reflash ROM again each time.

Running rastakat and it's standard kernal...
[Nexus 7 Original Development] basuraunak:
I have installed the kernel in RASTAKAT.....get the 4.4 img and flash using Flashify app.....(i used TWRP
[Nexus 7 Original Development] xenakis:
Which FKU are you using, free or paid? I think the free is flashing the old r75, which won't work on 4.4.
[Nexus 7 Original Development] skintosh:
Followed this approach and worked flawlessly. Art is slick!

---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------

Maybe this was why then but it is working now after using another way cheers anyway!
[Nexus 7 Original Development] basuraunak:
Nice to know that

Sent From Xperia
[Nexus 7 Original Development] vietkao:
I'm having a problem installing the kernel from the zip file... It somehow detects my device as tilapia and wont install. I dont know what the problem is. I'm running rooted stock 4.4.

Can anyone help me please?
[Nexus 7 Original Development] TheDarkDefender:
Try the img file or flashify ?

Sent from my Nexus 4
[Nexus 7 Original Development] poondog:
Do you happen to have a tilapia rom installed? Perhaps try the img (flash via fastboot or some app)
[Nexus 7 Original Development] osm0sis:
I've seen that a few times. It's because you somehow flashed a tilapia recovery. That said, this kernel should install just fine on both grouper and tilapia.. :confused:
[Nexus 7 Original Development] vietkao:
flashify seems to solve the problem.

Still don't know how my device can be seen as tilapia. The ROM was the grouper stock img i got from the google factory img page.
[Nexus 7 Original Development] adrman:
Double check that you dl'd nakasi and not nakasig. The link on google's page that takes you to the download links, puts the kk grouper (nakasi) link all the way at the top of the page, obscuring the device header. What shows up in the middle of the page and attracts your attention is the nakasig section. I initially dl'd the wrong file because of this, but caught my mistake in time.
[Nexus 7 Original Development] Gremlee:
I had this problem. It was the version of TWRP. Are you using 2.6.31? Try using 2.6.30 and it fixes it. It must be a parameters issue within TWRP.
[Nexus 7 Original Development] JovieBrett:
Hello, is it really for stock 4.4 only? or is it also compatible with CM11? :)
[Nexus 7 Original Development] Firetribe:
afaik for AOSP and stock, not yet CM.

\\
[Nexus 7 Original Development] redeyedjedi:
Is there any reason why it wouldn't run off cm11 if you added a cm11 ramdisk?
[Nexus 7 Original Development] Firetribe:
From what I understand, franco is going to support CM11 as well, just not already at this time.
[Nexus 7 Original Development] CamoGeko:
You could always try it, no guarantee it would work though.
[Nexus 7 Original Development] osm0sis:
Yeah it'll work. You'll lose some tweaks. That's why the next version is based on the CM ramdisk and has all the tweaks included as well.
[Nexus 7 Original Development] sjknight413:
I don't think it will work,

Last time I flashed r76 on cm11 everything fc'd on boot.
[Nexus 7 Original Development] osm0sis:
It will work with the CM ramdisk attached, as per the posts above the one you quoted.
[Nexus 7 Original Development] osm0sis:
Hmm so setting 204MHz as the min on boot with f.Ku is resulting in a SoD if I don't unlock directly after boot. No idea where the problem there lies.

Edit: Actually setting the min to anything on boot via f.Ku (including the default 102MHz) will cause this. :confused:
[Nexus 7 Original Development] :
Weird battery drain with r76

Noticed some weird battery bug after using r76 a few days on two different Nexus 7 devices. Both were running the official KRT16S with stock recovery and without root. Only flashed the kernel with the fastboot images.

The first (and my personal) device was fully charged before I went to bed. The next morning it wouldn't turn on because the battery was completely discharged.

The second device was charged to about 80% before work. Some hours later I unlocked the screen and noticed that it was almost completely unresponsive. It took 5-10 seconds before each touch action was registered. The battery was down to 7%. It ended up rebooting itself when I tried to take a screenshot of the battery stats.

When I booted it up again, it was back to normal. Here are some screenshots of the battery stats.

If it's an app that's causing this, it's not showing up in the battery stats. Never had any battery issues with either device or any unresponsiveness like the one i described. This first device is about 10 months old and the second one is barely a month old.

I've flashed both back to stock kernel now. Is there any log I should send or is it too late already? Has anyone else experienced this? :crying:
[Nexus 7 Original Development] limaunion:
Hi! newbie here... my nexus 7 (2012) is running Smooth ROM + TWRP + M-Kernel. Now I want to try this kernel. Is this kernel prepared to work with android 4.3? In order to install it I just need to boot in TWRP recovery mode and choose the zip file? is this right?

TIA!
[Nexus 7 Original Development] slebit:
R76 is for 4.4 not for 4.3.
[Nexus 7 Original Development] 1990clb:
Easiest thing to do will be download the free app from the app store. That will download r75 for you which is for 4.3!
[Nexus 7 Original Development] materoprodutions:
question regarding otg

Hey guys I've been using Franco for while and I have no complaints at all, it works great and I have very good battery life. In the past few days I started playing with the OTG and it works fine, then I started reading about somebody being able to do OTG+ charging at the same time. I bought this cable http://www.amazon.com/gp/product/B00CXAC1ZW/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1 from another link i found in some other topic. and It doesn't seem to work. I just wanted to know if the kernel is supporting Otg+ charging or not. Thank you
[Nexus 7 Original Development] Samu 17:
Can anybody please answer?

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 Original Development] shevich:
i am almost 100% sure franco won't incorporate it in his builds

if you want s2w or dt2w you should try oxydo or m kernel
[Nexus 7 Original Development] osm0sis:
IF they're modules, module support should be enabled again as of r76.
[Nexus 7 Original Development] Samu 17:
Thank you!

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 Original Development] Reiven89:
kernel flashing showing tilapia in my case too resulting in an error
[Nexus 7 Original Development] osm0sis:
And it's been said, your recovery is the problem.
[Nexus 7 Original Development] limaunion:
So I installed it from the app store, 'autoflashed' and now I'm stuck at the login with 'unfourtunately the process com.android.phone has stopped.'. I found an older post where someone suggested to delete the 'Phone.apk' from system _before_ flashing the custom kernel.

My problem is that I didn't know that in advance and I've already flashed the kernel.

How can I fix this?

Thanks!!!!!
[Nexus 7 Original Development] arjit mehra:
Hey is cm 11 supporting franco or not?coz i tried n it went into bootloop :/

---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------

restore a backup and then delete/rename it and then flash !
[Nexus 7 Original Development] limaunion:
what if I don't have a backup? :(

can I do something from TWRP? switch to my previous kernel or delete the apk file with the file manager?
[Nexus 7 Original Development] arjit mehra:
i don't think you can delete a file within twrp : / flash the rom again,then delete the apk then flash the kernel i suppose!
[Nexus 7 Original Development] osm0sis:
AROMA Filemanager. Check it out! It's a file manager for recovery.
[Nexus 7 Original Development] fingerslip:
Most likely you have to use the fixed r75

https://db.tt/9nqZDXuT
[Nexus 7 Original Development] limaunion:
Thanks to all. I finally managed to reflash and install the kernel that was using previously.

This time I chose the Leankernel (supplied with SmoothROM) to test it for a couple of days.

Later I'll try to install again Franco's kernel
[Nexus 7 Original Development] fozzie:
Of course you can. TWRP has a built in file manager and the ability for command line. Plus, as osm0sis mentioned, there's the Aroma file manager, which is really rather nice :)
[Nexus 7 Original Development] stackz07:
is this for 4.4 roms only? i am running liquid smooth 2.37 (4.3.1) would love to try this kernal.
[Nexus 7 Original Development] fozzie:
http://franciscofranco.minooch.com/Nexus7/4.3/zips/
[Nexus 7 Original Development] aoh1996:
Use r75.
[Nexus 7 Original Development] stackz07:
Thanks! Should I also delete folders before flash as stated by some users above. Or does the 4.3 just flash correctly without any prep or post install changes?
[Nexus 7 Original Development] fozzie:
It should just flash, but make sure you've backed up the stock kernel before you boot to recovery and then after flashing but before booting to Android, you might want to re-flash SuperSU (assuming that's what you use).

I'm not sure what the reference was about removing folders...
[Nexus 7 Original Development] NYLimited:
If you are using TWRP it has a built-in file manager if I recall correctly.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] osm0sis:
Yup! Though AROMA Filemanager is more full featured so I recommend it on TWRP as well.
[Nexus 7 Original Development] SquireSCA:
Just bought the paid app, worked like a champ, money well spent!
[Nexus 7 Original Development] Travisdroidx2:
Now you can back up your kernels before moving onto the newest update.
[Nexus 7 Original Development] zewelor:
franciscofranco: what kernel config are you using ? Still cant see nfsv3/4 support
[Nexus 7 Original Development] noneabove:
So does this imply that the GPU scaling is working but you just need to finish up the app?
[Nexus 7 Original Development] franciscofranco:
/proc/config.gz NFSv3 and NFSv4 are enabled in the config file.
[Nexus 7 Original Development] franciscofranco:
Means I haven't been successful in finishing it for several reasons.
[Nexus 7 Original Development] noneabove:
Ah okay sorry from your wording I thought it was almost done :p oh well haha
[Nexus 7 Original Development] franciscofranco:
It was, then I hit a roadblock then I scratched everything. Now on top of it again and overclocking 100% works showing improved FPS on two benchmark tools when I overclock.
[Nexus 7 Original Development] vinny86:
Yes Franco, some kind of check will be nice.

Even when going from r13 to r16 i had to flash it twice for the kernel to work.

Holding down the power button didn't work, it never gets past the Google screen.

Holding all 3 buttons even after restart makes it go into bootloader mode.

I got it working from there, had to flash the ROM again, since nothing else worked.

Used the Wegus Toolkit to speed up the process. (had to select device not booting up option)

Hope this helps the other person who was having problems.

EDIT: Looks like the other person also got it working.

---------- Post added at 08:46 AM ---------- Previous post was at 08:40 AM ----------

My device does that whether i am on stock or Custom Kernel :mad:

Not covering the top left corner of the device seemed to make it behave better. Although i can't be sure.:silly:
[Nexus 7 Original Development] franciscofranco:
Just pushed mighty r18:

* Made some changes over lowmemorykiller driver

* Added GPU overclock interface:

To check the clocks do this: cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc

The defaults are: 484 484 484 484 416 380 304 267

To overclock just do, for example: echo 520 520 520 520 416 380 304 267 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc

Check if it works benchmarking it with Benchmark 2.0 Taiji.

To underclock just run, for example echo 416 416 416 416 380 380 304 267 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc

If you find bugs let me know. Its obviously not set on reboot, but you should know that already.
[Nexus 7 Original Development] ÜBER™:
Shall we see an interface in your app soon as well? :)
[Nexus 7 Original Development] franciscofranco:
In the next days, yeah, most likely.
[Nexus 7 Original Development] ÜBER™:
Sweet.

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] mkuo:
Here's what worked for me, without having to resort to flashing ROMs when stuck at the Google logo:

1. Connect to pc with usb. At the stuck Google screen, hold down power button for 10 seconds, which restarts the tablet. Then immediately hold volume down and power to enter Fastboot.

2. Since I got stuck when auto flashing r17, reverting back to r16 seems logical. So I downloaded that img and put it in the img flashing folder under the mskip N7 toolkit.

3. With the toolkit, option 11 will allow you to boot with the img or flash it onto your tablet. Try with boot first and so at the very least you should get into Android. Or if you don't use the toolkit just adb flash the img.

That worked for me and didn't need to resort to resetting the whole tablet.

Btw thanks Franco for the great kernels... got it on both GN and N7.

Look forward to the next milestone.
[Nexus 7 Original Development] ÜBER™:
Mkuo avoid toolkits... this is a nexus device. :cool:

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] danlo:
Hello,

Anybody have issues with the uodater

---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------

Hello,

Anybody have issues with the updater? I bought the paid app but I now get the unlicensed error after I did a factory reset. Thanks.
[Nexus 7 Original Development] iamhcg:
After the factory reset, you need to re-install it from Google play. Remember to switch to the google account you were using when buying it.

The paid app will check the authentication before it runs the first time. I did factory reset once and used Titanium backup to restore it, and it gave the same error message, too. Reinstall it from google play and it's fine then.
[Nexus 7 Original Development] duyquang27:
Can u do the default is 520?
[Nexus 7 Original Development] danlo:
I did that already. Still getting the same error message.
[Nexus 7 Original Development] franciscofranco:
No, you can clock it yourself on r18.

Reboot, clear Market's data.
[Nexus 7 Original Development] ECC610:
I'm running the last Omni rom nightly and I'm not managing to flash the r76.

Pic.

Does anyone have the same problem?
[Nexus 7 Original Development] sgt. meow:
fastboot flash boot [name-of-boot].img

Or use Flashify.

No one at the forums are responsible for your device acting up; you take full responsibility.
[Nexus 7 Original Development] fozzie:
As above, or use f.Ku to download and auto-flash. I had the same problem. Apparently it's something funny about this particular zip and TWRP. It apparently flashes ok manually with CWM.
[Nexus 7 Original Development] osm0sis:
Yup. And it's weird because that line of script is basically directly out of an OTA. If you use the latest TWRP does it still happen?
[Nexus 7 Original Development] fozzie:
Yeah, it happens on 2.6.3.1.
[Nexus 7 Original Development] osm0sis:
Hmm so, the thing is, the zip hasn't changed:

assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" ||
getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia");

It's been like this since r60, and they are 100% standard device checks like are done in OTA zips. So it's something TWRP broke and needs to fix.
[Nexus 7 Original Development] NYLimited:
Yeah, I too like Aroma but the poster said bootloops. Depending on their skill level they might find it difficult to put Aroma FM on the device while bootlooping... ;)

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] fozzie:
4.4.2 seems to be working fine with r76.
[Nexus 7 Original Development] GedBlake:
Yep... working smooth here as well.

However...

I had always assumed (probably incorrectly), that franco's kernel was just a boot.img flash to the boot partition... and nothing more... there's nothing in the updater-script that suggests otherwise... although why it won't flash via TWRP is a bit of a mystery:).

As is now probably known, there is a new OTA update available, that will upgrade the Nexus 7 from KRT16S (KK4.4) to KOT49H (KK4.4.2). Having first fastboot flashed back to the stock kernel prior to flashing this new KitKat upgrade, I expected CWM to perform the upgrade without problems...

Guess what... it didn't:(. CWM flagged a status 7 error...

Verifying current system...
"/system/vendor/lib/hw/power.grouper.so" has unexpected contents.
...
...
(status 7)
Installation aborted

I rebooted back into Android normally, and using ES File explorer, I tracked down the errant file... namely /system/vendor/lib/hw/power.grouper.so...

...only to discover that 'something' had renamed it to /system/vendor/lib/hw/power.grouper.so.fkbak

That 'something' had added an .fkbak extension, presumably with the intention of disabling it. It took me a couple of seconds to associate .fkbak with franco kernel...

Anyway, I removed (renamed) the extraneous .fkbak extension with ES File explorer... booted back into CWM and the OTA flash upgrade to KitKat 4.4.2 proceeded flawlessly.

I wasn't totally sure at this point, that the .fkbak extension had anything to do with franco's kernel, but having run rooted stock KK4.4.2 with stock kernel for nearly a day now, I've just used flashify to flash r76 again, and it HAS renamed power.grouper.so to power.grouper.so.fkbak... so there's no doubt in my mind it's renaming is definitely related to franco.

(Addendum: I've just tested it again, by auto-flashing r76 with franco's app... having removed the .fkbak extension first. Upon reboot, the .fkbak extension is back. franco r76 definitely needs /system/vendor/lib/hw/power.grouper.so to be disabled.)

---------------------------------------------

This isn't a criticism by the way... just an account of my own experiences with regard to upgrading from KitKat 4.4 (build KRT16S) to KitKat 4.4.2 (build KOT49H)... and that simply replacing (fastboot flashing) franco's r76 kernel with the KRT16S stock kernel might not be sufficient to avoid the OTA aborting with a status 7 error... you might have to use something like ES File Explorer to remove the .fkbak extension before applying the OTA update.

---------------------------------------------

Other then all of that, r76 is liquid smooth, and an absolute delight to use:cool:.

Thanks, franco (for not forgetting our ageing first gen Nexus 7 devices)... and all the kernel experts who post here.

Rgrds,

Ged.
[Nexus 7 Original Development] osm0sis:
Yup. f.K has a kernel-side touch boost implemented now so we need to disable the Android software one, named .fkbak expressly so you'd know what renamed it. Look in /sbin/fkbootscript.sh - that's where the magic happens. ;)
[Nexus 7 Original Development] davy917:
So then if I want to switch kernels would I need to flash the stock boot.img first?
[Nexus 7 Original Development] fozzie:
I would (& rename power.grouper.so.fkbak back).
[Nexus 7 Original Development] ChungHung.Chen:
Will franco build a new kernel based on 4.4.2 kernel source?

Or just flash r76?
[Nexus 7 Original Development] sgt. meow:
There is no new 4.4.2 source. Or am I wrong?
[Nexus 7 Original Development] chand9336:
4.4.2 sources are yet to be released
[Nexus 7 Original Development] jaydoo:
I try with TWRP v2.6.3.1

But end with failed.

I have Nexus 7 2013 3G
[Nexus 7 Original Development] osm0sis:
Yeah no wonder the device check failed; this is exactly why it's there!
[Nexus 7 Original Development] poondog:
I always wondered why :P

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Well it was actually for when that guy bricked his N4 by flashing the N7 zip. ;)
[Nexus 7 Original Development] poondog:
Unfortunately I remember that
[Nexus 7 Original Development] jaydoo:
Sorry guys. This is my big mistake. Typo when typing with the tablet. I have Nexus 2012 3G 32 GB - nakasig.

Why flash ending with failure ?
[Nexus 7 Original Development] ChungHung.Chen:
This is a known problem with TWRP 2.6.3.1.

Downgrade to 2.6.3.0 and it will work.
[Nexus 7 Original Development] osm0sis:
Haha that's insane! Lucky the partition was the same number or it would brick. The hardware is close so I guess that's why it still booted. Occam and Razor after all. :p
[Nexus 7 Original Development] jaydoo:
Thanx, now work it :)
[Nexus 7 Original Development] misterk267:
Excellent kernel as usual. Thanks!
[Nexus 7 Original Development] javacody:
Or just use CWM never had an issue flashing with it and I've been using it since the G1 days...
[Nexus 7 Original Development] bhu1:
Is this kernel not supposed to work with cm11? I flashed it and I got many FCs like NFC, phone provider, more...
[Nexus 7 Original Development] slebit:
It doesn't work with cm. At least not right now.
[Nexus 7 Original Development] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION] has the ramdisk I sent him he just needs to push the release.
[Nexus 7 Original Development] zolaisugly:
Assume this works with stock 4.4.2... does it support otg.... sorry for noon question but I can't find answers in op.
[Nexus 7 Original Development] slebit:
Yes, it will work with 4.4.2. And OTG will work if you use stickmount.
[Nexus 7 Original Development] andrew9292:
Can USB DAC support be added? :cool:
[Nexus 7 Original Development] tcat007:
Flashed r76 zip with twrp, no go. Flashed with Flashify, no go. Flashed boot.img with Flashify, it took. Now my n7 and n5 running smoothly with Purity 4.4.2 + Franco + Banks standard gapps. No clue why zip didn't work, could be dirty flashes, had m-kernel.
[Nexus 7 Original Development] slebit:
For some reason it doesn't work with twrp 2.6.3.1. It does work with 2.6.3.0.
[Nexus 7 Original Development] javacody:
Franco, any chance you'll be merging the N5 awesomeness into this Kernel?

My N5 has never been so smooth!
[Nexus 7 Original Development] bisco:
[MENTION=3292224]franciscofranco[/MENTION] that would be really awesome! would make a great xmas present :)