yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] levicius:
In Franco's app gives me the option to download the latest available version thats saying its r11 ( but I am not sure if this is the right one for my device ) and in flashify its giving the same error when I try to flash the zip file , I tried the boot.img in flashify but when I click on it nothing happens .

BTW this is my info
[Nexus 7 Original Development] fozzie:
Errrm, you've a N7 2013, so you're flashing the wrong update! This is for the older 2012 model. You want to be in http://xdaforums.com/showthread.php?t=2446431
[Nexus 7 Original Development] levicius:
Omg ,thanks my friend, almost bricked my device !!! Lol

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 Original Development] adame09:
Having trouble flashing this on my grouper running omni rom
[Nexus 7 Original Development] c0080900v:
I downloaded the franco.Kernel-nightly-r77.zip

But it fails every time I attempt to flash via Recovery.

Any ideas/help here?
[Nexus 7 Original Development] Souron29:
Modify the updater or flash the boot.img separately
[Nexus 7 Original Development] c0080900v:
Well, I don't have the updater app installed if that's what you mean by updater.

I've already downloaded the boot-r77.img assuming this is the img I'm supposed to flash. I'm supposed to flash this via command this time, right?
[Nexus 7 Original Development] fozzie:
You can either downgrade your version of TWRP to the previous one (2.6.3.0) and flash the zip or use something like Flashify to flash the boot.img (https://play.google.com/store/apps/details?id=com.cgollner.flashify)
[Nexus 7 Original Development] c0080900v:
Flashify did it for me like a champ.

But to what reason downgrade my TWRP? It it compability, or something?
[Nexus 7 Original Development] fozzie:
Glad it worked. Yep - the latest TWRP somehow broke the assert that checks the device type/model :(
[Nexus 7 Original Development] i root SGH i777:
just flashed this kernel, im gonna give her a try. but so far its really good.
[Nexus 7 Original Development] Screw Muggz:
Thanks I'll try it again then.
[Nexus 7 Original Development] pjcanales:
Hello try to install this kernel I got everything installing but when i went to install zip it stated installing virus then got failed installation running stock ROM on Android Kit Kat 4.4.2 any help would be greatly appreciated.
[Nexus 7 Original Development] LuckySwitz:
TWRP?? use 2.6.3.0.. if you're using what i've mentioned, redownload the zip file..
[Nexus 7 Original Development] pjcanales:
By chance do you know where I can get that build?
[Nexus 7 Original Development] LuckySwitz:
download link..

techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.3.0-grouper.img

edit: flash it with flashify..
[Nexus 7 Original Development] pjcanales:
For sure this is for nexus 7 2012 first gen correct?
[Nexus 7 Original Development] LuckySwitz:
rest assured..
[Nexus 7 Original Development] Anne_Droid:
It took several seconds, after pressing the power button, for the screen to turn on.

I thought I was having a hardware problem! :crying::crying:

Reverted to r76 for now and the issue is gone. :highfive:

Thanks btw for those who posted the same thing earlier, what a relief.
[Nexus 7 Original Development] inscythe:
I'm having the same issue as well...
[Nexus 7 Original Development] gharika:
I am having a weird problem with franco and stock 4.4.2, while locked, the power usage remain low if I have wifi off, but with wifi, initially it's low but after a few hours there is sharp increase in power consumption and the ui is so unresponsive that it's difficult to unlock and I have to restart it with power button.

The last drop in the screen shot happened when the device was not being used.
[Nexus 7 Original Development] pit84:
franco kernel and omni rom

hi francisco

1 stupid question: your kernel is compatible with omni rom?

thanks for support my device and for new fk updater
[Nexus 7 Original Development] khaytsus:
Make sure you're not using an older SuperSU, and next time this happens, try to get in (adb? Whatever works) and look at top output. I'll bet you have a runaway process, and it might be supersu related. I've seen this happen a lot since 4.3 or so when supersu had to go to the daemon mode.
[Nexus 7 Original Development] espionage724:
Hmm, not exactly a kernel problem, but for some reason, FKU (paid app) isn't flagging Superuser for root, and thus errors-out on first start.

Edit: Could be just my Superuser messing up (SuperSU wasn't even able to gain root nor delete Superuser); i'll try a clean install with SuperSU instead.

Edit: It works fine with SuperSU; the only thing is, I can't start FKU for a minute or two after reboot, and it seems Fsync and the screen dimmer don't stay disabled after reboot. Doing a cat /sys/module/sync/parameters/fsync_enabled shows it as Y, and if I understand right, default is N...

Edit: Had to set SuperSU to give root to stuff at boot. So... no problems now :) I'll just leave this here in-case someone else runs into something similar I guess.
[Nexus 7 Original Development] bitbitbit:
Same problem here. I thought it's app related and was too lazy to figure out what was causing it so I just wiped the whole thing :eek: I guess that's the wrong move...
[Nexus 7 Original Development] jfmcbrayer:
bitbitbit and gharika, the next time this happens, can you post the last 100 or so lines of dmesg (as an attachment)? I suspect you may be having a problem I had with most custom kernels involving failed USB resets.
[Nexus 7 Original Development] Flukester69:
Very nice work on the kernel 77 Franco. It works extremely well with the latest Paranoid 4 ROM.

[MENTION=252981]Power[/MENTION] issues. I have found Franco's kernel a huge amount better than ROM included kernels. Have you guys turned off nonessential things like GPS and Bluetooth? Also do you use anything like ES Task Manager to kill off startup apps etc? I get pretty close to a full day gaming on and off with my current setup.
[Nexus 7 Original Development] Gspin96:
If this kernel doesn't rely on ramdisk modifications, could you use koush's AnyKernel method to flash it?

It's a CWM package that unpacks the current boot.img, puts the new kernel zImage in it and repacks the boot.img, then flashes it. This could save some issues with ROMs relying on a modified ramdisk.
[Nexus 7 Original Development] animania260:
Yeah but all Franco's kernels have ramdisk changes. Whether for CM compatibility or his custom hotplug. Just some info for ya.

If you flash this kernel without the ramdisk changes Franco's custom hotplug won't work correctly I believe.
[Nexus 7 Original Development] PxEclipse:
Hello. I would like to ask if it is possible that the speed of my nexus 7 is decreasing with less charge. If yes I would like to know how I can prevent that.
[Nexus 7 Original Development] fozzie:
No. It doesn't do that.
[Nexus 7 Original Development] ronedogg:
Glad someone understood the question lol
[Nexus 7 Original Development] Souron29:
Yes
[Nexus 7 Original Development] ianmedina:
Is this working using the latest cm11 snapshot?
[Nexus 7 Original Development] CyberCodeDroid:
Excellent app, it would not be possible the development of the GT-7100?
[Nexus 7 Original Development] lolpok:
Yes.
[Nexus 7 Original Development] rockafellor:
[MENTION=3292224]franciscofranco[/MENTION]

Any chance in getting updates for this device? Would be great.

Sent from my francofied cataclysmd Nexus 5
[Nexus 7 Original Development] fozzie:
What sort of updates in particular were you looking for?
[Nexus 7 Original Development] rockafellor:
no delay when switching on/off screen

UV, updates as they are released on nexus 5 if possible! seems like nobody has the old n7 anymore :(
[Nexus 7 Original Development] fozzie:
I do :) (and don't have any problems with it..... Well nothing that if I had the cash, upgrading to the newest model wouldn't fix!)
[Nexus 7 Original Development] wolfydRg:
You are the exception, almost all users of nexus 7 version 2012, with Franco kernel version 77, have this problem, lag on screen on.
[Nexus 7 Original Development] khaytsus:
Are you saying the exception is having lag, or not having lag??
[Nexus 7 Original Development] wolfydRg:
Exception is not having lag ....
[Nexus 7 Original Development] tcat007:
2012 here, no lag. Just turned off and back on, 1/4 second at most.
[Nexus 7 Original Development] adrman:
Long lag with r77 as well. I've reverted to r76 until it is corrected.
[Nexus 7 Original Development] mrksbrd:
[MENTION=3292224]franciscofranco[/MENTION] any chance of implementing the knock knock feature in the next release. I am in the process of installing the N7 2012 in my truck to work along with my head unit and this feature would be great. This way I don't have to solder new leads to move the buttons

Thanks
[Nexus 7 Original Development] .torrented:
I can also confirm that it takes at least about a (1) second before the screen will come on.

r76 is so much snappier
[Nexus 7 Original Development] fozzie:
A whole second? Wow, the things you could get done in that second instead of hanging around waiting... :)

Each release isn't guaranteed to be better than the previous one. Sometimes changes are made for testing & feedback and that work better for some people but not others. If r76 is better then you should be using that...and your delay is no more! Is there something specific in r.77 that you absolutely must have (other than it's the latest)?
[Nexus 7 Original Development] bassie1995:
Do it sixty times and waste a minute. I don't get your point on the delay.
[Nexus 7 Original Development] fozzie:
You have choices; live with it, flash an older version or revert to stock, buy a faster device....or walk a bit quicker to the bus to make up for that lost minute in your life (although if you're turning your device on 60 times a day, there's probably other areas in your life where you can regain some of your lost time). The point being that a 1 sec delay is hardly a life changer and I would imagine not anywhere near the top of Franco's priorities. This is now an 'old' device and there's many more newer devices that need the Franco treatment.

I'm pretty sure that he's aware that some of you find this delay unbearable and will work on it if and when he feels the need. Constant posting about it isn't going to change anything (other than hack people off who have thread notifications enabled and hope to find something interesting to read).
[Nexus 7 Original Development] NYLimited:
Those experiencing wake delays with r77 - try increasing your minimum cpu frequency from 102 to 204. You might be surprised.

For people with high battery drain due to the baseband_xmm_power wakelock keeping the device awake try r76. While r77 was keeping that wakelock on my n7 at all times r76 kept it only for 28 seconds out of 30 minutes.

Yes, we do have choices. I did settle on r76 and have also flashed stock on occasion. I do not take buses so that would not help. Often when I have no constructive suggestions I say nothing as I found that sarcastic replies don't usually help others.

Sent from my Nexus 7
[Nexus 7 Original Development] Spiceworm:
I installed cynogenmod 11.2 m3 with the r77 kernel and I must say my Nexus grouper is extremely vast. Like you bought a new computer. Thanks for that, I bought the update app tot support you. I to have the slow unlock bug as reported. Antutu 14600 with art instead of dalvik. I still have to figure out how to install an older version / that would be a neat feature for the app.
[Nexus 7 Original Development] JovieBrett:
Any solution for the miscalibration of color graphics issue?
[Nexus 7 Original Development] NYLimited:
I assume you are talking about the original Nexus 7, not the 2013 model, yes? I am no expert on colors and calibration but seem to recall an app for tablet display calibration. I don't recall the name. It was a software calibration app which, essentially, adjusts the color values sent to the display; pretty coarse, given that these displays are internally probably 6-bit or 8-bit at most.

I would guess that there are no sophisticated solutions for now.

I suspect that *real* screen optimization and calibration can only be done at the factory. As I understand it the raw LCD panel hardware first needs to be adjusted and calibrated at the factory with specialized firmware and software data that need to be downloaded into the device in order for the display to produce a usable image – let alone an accurate and beautiful one.

Sent from my Nexus 7
[Nexus 7 Original Development] JovieBrett:
Yup it's a Grouper one. You mean it's a hardware part that is needed to configure about the LCD panel? :// Anyway thank you, I'll try to find the app that recalibrates the color.

EDIT

Can't find the app :(
[Nexus 7 Original Development] C.Hatfield:
Trying to fix the poor color on the 2012 N7 aka Grouper is, tmk, is an impossibility. I know it is essentially an initial factory calibration issue but as far as post-factory tweaking, it ain't happening.

I have long hoped for someone to fix or offer a solution ever since. This was a major PITA back upon release, it seems as though it remains that way today.

I know Franco has been asked several million times to fix/include a R/G/B tweak in his kernel however, way back when I suggested Color Calibration on the FKU "wish list" he said there was either, a problem with the Grouper and/or just no solution to the problem.

**As far as I know, there is no app to look for .... FKU cannot do it, Trickster cannot do it, Faux App cannot do it .... believe me, I've tried annnd I've run damn near EVERY kernel built for the Grouper - to this day, the sh*tty color problem remains the one major flaw in an otherwise, really good tablet.
[Nexus 7 Original Development] JovieBrett:
Ok :// Hmmm... one more question, I am only experiencing this on ROMs where franco's kernel is implemented like the one on PA's (Because Paranoid Android uses Franco's kernel right?) But why on the other ROMs like CM doesn't have that color calibration issue?
[Nexus 7 Original Development] drewski_1:
afaik, Paranoid does not use Franco's kernel
[Nexus 7 Original Development] .torrented:
Color Calibration on the Nexus 7 2012 is not doable. It's a hardware limitation of the LCD or the Tegra chip, I can't remember exactly which it was.
[Nexus 7 Original Development] JovieBrett:
Yeah right, sorry.
[Nexus 7 Original Development] wolfydRg:
Seted to 204 , but no change, same lag here. Anyway I reverted at r76.
[Nexus 7 Original Development] krazzykid:
Wake delays are very rare in my case. Min CPU frequency is 204 MHz
[Nexus 7 Original Development] CyberCodeDroid:
Should I question, will remain even after kernel update nightly builds Omni ROM, or every time it is needed to flash again?
[Nexus 7 Original Development] slebit:
You will have to flash this kernel after you update to a newer nightly.
[Nexus 7 Original Development] KingPrincess:
I set the min to 340 and it's still taking many seconds to turn on. It's EXACTLY like trying to see what my battery is at while it's charging while the tablet is off, it can take ~20 seconds of me pressing the power button over and over until something happens, switching up how long I hold the button and how long I wait between presses.

Can I just flash down to r76 or do I have to do any wipes before/after? Before this I was using m-kernel but I wanted to check out franco's, besides this problem it's been just as good as m-kernel.

Does anyone think the r77 wakelock and the problem with checking battery level could be tied together? Maybe google/asus released some defects (some lol), I mean I had to assemble the screen and battery myself when I got the thing afterall. If checking the battery is never a smooth process for ANYONE then disregard this, I'm just trying to help put the horrible pieces of this buggy code puzzle we call android together.
[Nexus 7 Original Development] fozzie:
Just flash.
[Nexus 7 Original Development] KingPrincess:
Thanks but now I am in a nightmare and cannot escape. I lost root when I successfully flashed r76.img with the franco file manager section of the paid app and don't know how to get it back. I tried restarting. I'm best with the two noob-friendly toolkits, if I need to do the ADB or whatever it is with all the typey type I'm gonna need a tutorial. The good news is the tablet now seems to turn back on instantly every time.

(I typed the bottom paragraph first then figured it out then started typing up here, I'm typing this last basically I am on r76 but it broke my root which I haven't figured out yet. This is sort of just messy helpful instructions for the song and dance necessary for at least r76/77 of this kernel, with at least paranoid android beta 6.): I used the .img file instead of the .zip, choosing it in the franco file manager, it told me to reboot to my new kernel and it worked. I went into android settings to see I had r76 now. I got a new problem: I launched the franco app after booting and it gave a message about not having root permissions so I should go into my su app and forget it then relaunch it. I opened SuperSU and now that's saying "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to android 4.3, you need to manually re-root blah blah". I'm on paranoid android beta 6. I just tried rebooting and it didn't help. Aw man franco you broke my root with your kernel how is that even possible.

I forgot to mention I first got an error "assert failed: getprop("ro.product.device") ...... E:Error executing updated binary in zip ....... E:Error installing zip file" when trying to install r77 manually. I got it to install through the paid franco app, updated right over the stock kernel and everything. This time I tried r66 manual with that error, then tried choosing it through the franco app's file manager which said to restart in recovery and it'd automatically flash, but I believe that is giving the same error too.
[Nexus 7 Original Development] fozzie:
Not entirely sure what you're saying in this wall of words!

To get root back, just flash the SuperSU zip from (custom) recovery or fastboot or adb or with a toolkit...

The assert failed problem is a derp with TWRP. Either downgrade to the previous version or flash CWM or flash the r77 boot.img with f.KU or use Flashify.
[Nexus 7 Original Development] KingPrincess:
I wrote down step by step what I was doing, and what went wrong. This way franco, twrp, google, whoever can see what I just went through and fix it.

OKAY! I installed the flashable zip and it worked and then I did the clean install option in supersu so I could install it from the market and everything seems good. The franco app scared me at first but it just had a quick hiccup and now I have working root working kernel app working screen turning on.

Thanks!
[Nexus 7 Original Development] asturel:
on touch cores settings doesnt have any effect :/ checked @ cpu-z but still only 2 cores activated on touch
[Nexus 7 Original Development] rockafellor:
[MENTION=3292224]franciscofranco[/MENTION] - is it official that you don't support old n7 anymore :(? No updates

No offense/stress

Sent from my francofied cataclysmd Nexus 5
[Nexus 7 Original Development] eak1080:
When you have paid for software (the app) to use the kernel and the kernel has not been updated to fix a critical bug which drains your entire battery within 4hours and cooks your device to ~80°C.....yeah I'd like an update ASAP to continue using paid software or a damn refund.
[Nexus 7 Original Development] sgt. meow:
I don't mean to sound rude, but try maintaining kernels for nearly 6 different, out of which only 3 share similar architecture (to some extent) and the rest are different boards entirely. Yeah Franco does that. He's probably cracking away at a kernel as we speak. It is not hard to believe that he has not found the time to update the N7 2012 kernel, as he is busy with other things in life.

The N7 2012 is nearly 2 years old. It is really foolish to expect support when there are newer, better Nexus devices around that have Franco's support.

And if you really want to use this kernel without that "critical bug", compile the source with a fix yourself. I'm sure people would help you if you took the initiative.

Cheers.
[Nexus 7 Original Development] poondog:
To add on what sgt.meow said.. you don't buy apps or donate for future support, you do this to say thanks for what they have already done and to use what is currently available. My grouper on franco had no issues at all.. worked as advertised

Look at the Galaxy Nexus now.. franco supported that for a year until the N4 was out, working on it with most of his time. Then as the N4 came out, attention turns to the N4 and then the N5.. if you want franco support and fast, experimental updates then looks like you want the latest nexus phone. Biggest userbase too.

Grouper has a mere fraction of the userbase hammerhead has
[Nexus 7 Original Development] drewski_1:
I have no issue like what you describe. Purity ROM + Franco.

What ROM are you using?
[Nexus 7 Original Development] poondog:
^^ on slimkat :)
[Nexus 7 Original Development] KingPrincess:
It's so sad to see the n7 2012 considered outdated already. I too bought the app having no idea anyone could even have those thoughts yet. Man this generation needs something new twice a day.

I get how it works, the above isn't a jab at franco.
[Nexus 7 Original Development] poondog:
Unfortunately yes. Lucky this is not a Sony.. they have nwe flagships 3 times a year. At least Nexus, HTC, Samsung have a year being the flagship
[Nexus 7 Original Development] Enddo:
im having an issue with my N7 and im not quite sure if the culprit is Google Now, PA 4.1 or Franco Kernel

after it sits with the screen locked for 4+ hours it ends up getting incredibly laggy. so much lag that it's hard to even unlock the device, let alone go into system monitor

the one time i was able to open System Monitor I saw 3 cores at full usage with the 4th one not active. swiping to the Top Apps page in System Monitor I saw 'Settings Storage' and 'Android System' cpu load taking up 47% and 48% respectively

if anyone could point me in the right direction I would be greatly appreciated. it happens and eventually turns off due to no battery left. then the first reboot after is really slow, hanging at the boot animation for at least 3-5 minutes rather than the 1 minute boot that im used to
[Nexus 7 Original Development] laill:
Probability it is the incompatibility in your combinations.

Most of us does not face this problem and most of us doesn't use PA ROM(I guess).

Try purity or Slimkat with this kernel. I am currently using Slimkat with Franco kernel, overall feeling is nice except I don't have enough memory to hold all the stuffs simultaneously and smoothly.

Regards,

L
[Nexus 7 Original Development] KingPrincess:
I'm using PA because I literally refuse to use a different rom and for me r77 is broken and r76 I don't think has given me much or any trouble but if franco is gonna be a while or forever don't forget m-kernel is infinity times better I just don't trust its overclock and it doesn't have a dedicated app but franco's app doesn't even work lol as where trickster mod is perfect

My suggestion is do NOT stop using paranoid android, ever, try r76, give franco a bit more time, then m-kernel it up

Actually I just remembered I'm on the stock pa kernel since I updated so I'm just gonna stay on stock for now and see how it does, because honestly I think both m and f kernels are currently too buggy (m-kernel is in a much better state with the dev constantly replying to the thread and he's doing that f2fs whatever new thing too he currently has the most points)

---------- Post added at 02:31 PM ---------- Previous post was at 02:22 PM ----------

ACTUALLY Lego kernel........ ooooooooo I'm thinkin about it I'm thinnnnnkin about it
[Nexus 7 Original Development] RRRAM:
hallo.Does this carnel support OTG sharger?
[Nexus 7 Original Development] RRRAM:
Sad.does not work otg charger :(
[Nexus 7 Original Development] Erik1805:
Just flashed v67 and lost root access. Any idea?
[Nexus 7 Original Development] fozzie:
Reflash SuperSU.