yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] -viperboy-:
Eh, I'm nothing exciting compared to these guys :)

Nice stats! I love DT2W but I understand completely why Franco doesn't want to add it into his kernel. It keeps the panel in a state where it's awake for touch input and uses significantly more power when the screen is off.
[Nexus 7 (2013) Original Android Development] L-ViZ:
coming from r2, clean/fullwipe to r3

my 3d performance doubled in score of 3d mark ;)

had arround 3200 before

now 7000. dunno why my score was so low before.

setup:

stock clocks

rab 2048

gpu/cpu gov ondemand

fsynch off
[Nexus 7 (2013) Original Android Development] EfrainTrejo:
This makes no sense r75
[Nexus 7 (2013) Original Android Development] franciscofranco:
I haven't yet updated the free version to support the new N7. Soon.
[Nexus 7 (2013) Original Android Development] EfrainTrejo:
Oh ok no problem. :)
[Nexus 7 (2013) Original Android Development] lndeed:
Franco, will you be building a kernel with the CAF library in order to support CM and CM-based ROMs like faux did? Among other things, it unbroke the Slimport bug that was mentioned earlier in this thread. Seems ROMs didn't behave well when flashing a kernel built using the AOSP library. Considering just how many ROMs are affected it might be worth thinking about.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Don't want to put any words in Franko's mouth, but keep in mind that those of us with stock AOSP, or roms based on actual AOSP, will have the best results with an AOSP kernel. There are plenty of kernels based on the CAF library (which CM is basically a copy of) that will run great on a CM rom.

Those kernels in turn don't run as well for those of us who prefer a stock rom with Xposed, or a rom based on AOSP source. As I said in flar's thread, I have no idea why CM felt the need to switch to a different set of libraries on a device that was already a part of mainline AOSP, but any incompatibilities are the responsibility of CM, and not Google.

Of course I defer completely to Franko's opinion regarding his kernel, as it is entirely his project and he will do what he thinks is best, that's worked out pretty awesome so far! :thumbup:
[Nexus 7 (2013) Original Android Development] lndeed:
I do agree with everything you said, but I was suggesting following faux's approach and having two separate kernels (stock and CAF).
[Nexus 7 (2013) Original Android Development] tweaked:
I don't see him doing that. Lol. Maybe you'll get lucky and he will be in a good mood and he will be all happy to double his work just because CM is all goofy.
[Nexus 7 (2013) Original Android Development] mountainloafers:
Any mirrors? I can't seem to connect to the server. Tried last night and gave up. Been trying this morning for the last 30 minutes. Tried on laptop and n4. Would be very grateful for a mirror. :thumbup:
[Nexus 7 (2013) Original Android Development] adichandra:
For you who really want to enjoy franco kernel, if you are coming from other kernel, please please, full wipe your data and then install franco kernel. Because from my experience yesterday, by doing full wipe, it really gives the full performance like what franco's kernel supposed to do. I even clean my internal storage and sideload psx rom, gapps and franco and then start fresh.
[Nexus 7 (2013) Original Android Development] notoriouspk:
smooth performance excellent standby time thanks for this awesome kernel
[Nexus 7 (2013) Original Android Development] mountainloafers:
I am on AOKP mr2 unofficial ROM and flashed r2 over the kernel that came with it. Are you saying that I am not experiencing the benefits of r2?
[Nexus 7 (2013) Original Android Development] whitedragonz83:
Fastboot flash boot boot.img best way no wiping needed. :)
[Nexus 7 (2013) Original Android Development] adichandra:
Well im not sure, but i did use matr1x kernel before, then i flash franco kernel, it gave me bad benchmark. It's probably because i didnt flash the rom first to get back to the stock kernel.

---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------

Boot.img means stock google kernel?
[Nexus 7 (2013) Original Android Development] shreddintyres:
While that will do the trick that's not absolutely necessary, you just need to be sure that all remnants of the old kernel ie files that were added by the other kernel are removed and you will be fine. (complete wipe And re flash just takes far too long for me especially)

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] adichandra:
How do you check for old kernel junks anyway?
[Nexus 7 (2013) Original Android Development] shreddintyres:
Look at the kernel installation zip you only have to replace the files that the kernel zip added, as well as any Init.d scripts that were made either by a kernel control program or the kernel it's self, i gave a more complete explanation earlier in in the thread, as I'm on my tab right now I can't link you to it but it should be easy enough to find if you search the thread with my username

- cheers

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] mountainloafers:
Still have server time outs here... Any mirrors? :o

---------- Post added at 09:57 AM ---------- Previous post was at 09:18 AM ----------

Well, I guess I will just take a break then... Server must be slammed.
[Nexus 7 (2013) Original Android Development] franciscofranco:
That ain't going to happen, sorry!

I just opened the link on my browser, was working just fine.
[Nexus 7 (2013) Original Android Development] jak3z:
Your servers timeout to me :(
[Nexus 7 (2013) Original Android Development] mountainloafers:
Hmmm? Will try again.
[Nexus 7 (2013) Original Android Development] whitedragonz83:
Boot-r3.img for lastest nightly.
[Nexus 7 (2013) Original Android Development] mountainloafers:
Strange. It offered a cached version and worked fine this time. Oh well, happy camper now. :D
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Glad to hear it, tired of seeing all this CM-based stuff on an AOSP device.

:thumbup:
[Nexus 7 (2013) Original Android Development] franciscofranco:
Exactly.
[Nexus 7 (2013) Original Android Development] lndeed:
I understand not wanting to build another kernel. Oh well.

Just an update for the record: flashing this kernel on CM, AOKP, and Slimbean (and certainly more, these are just the ones I can confirm) will break Slimport. Blame the CM team I suppose.
[Nexus 7 (2013) Original Android Development] silver04v:
Anyone using this on pac roms?
[Nexus 7 (2013) Original Android Development] jak3z:
Indeed, blame CM.
[Nexus 7 (2013) Original Android Development] juried:
Thanks for this info, I was going quietly crazy blaming Slimport.

Which kernel could I go to to get Slimport going? (I'm on Slimbean.) EG, if I reflash Slimbean, will its kernel be flashed also by default? Sorry if this sounds noobish, I am an old hand at the Motorola Defy but locked bootloaders there have always made kernel a non-issue until recently when they found a work-around. So my understanding of exactly how the kernel is handled in ROM flashing is shaky.
[Nexus 7 (2013) Original Android Development] lndeed:
No worries, it's pretty complicated. For Slimbean, you'll need a CAF kernel. Your choices are the stock Slimbean kernel (which will indeed come back with a reflash), or faux kernel (the CAF version). I'd recommend faux kernel.
[Nexus 7 (2013) Original Android Development] borxnx:
Blame CM. And enjoy having them not care. Until they can make you pay 'em. Then they still won't care.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
This. It isn't Google or Franko's fault that CM claims to bring "true AOSP" to everything out there, while being the only ones that actually aren't "true AOSP" even on a device that has full AOSP source. There's no benefit to running a Nexus "AOSP" build off a CAF base when there's a complete AOSP base and libraries for each Nexus device. But that's what they do, and inconsistencies and incompatibilities should be expected. Anyone else who builds off a CM branch should know this, but I'm not sure that everyone does.

I'm not trying to disparage anyone's work here. But everyone should know that CM isn't the same thing as AOSP, it's basically CAF. As such, if you base your work off of a CM branch, or use such work, you're putting stability and compatibility in their hands. Whereas if you build off of AOSP on a supported device, which all Nexii are, the only stability issues will be from things you added, as the AOSP base will be fairly solid. So if you decide to build off of CM, you should probably have a good reason in mind. No sense in putting the stability of your work in many other people's hands without some benefit.

This may be different on non-AOSP devices, where there isn't full source and device files available. Though it's still often possible to find or extrapolate working device files for AOSP from somewhere. But I'm no dev and have no business telling anyone how they should handle their projects. I'm just making sure everyone is aware of the difference here.
[Nexus 7 (2013) Original Android Development] malukiz:
Hi franco,

Can you add tape to wake ? Faux123 release this 2 day ago on his kernel maybe you can merge the code? ^^
[Nexus 7 (2013) Original Android Development] habylab:
No, he won't.

What would be useful however, are his backports from 3.8 kernel.

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) Original Android Development] AutomaticFailure27:
Where can I buy the Scotch brand Android specific tape? :p
[Nexus 7 (2013) Original Android Development] style154:
Yes I would like to know what tape can wake my device:) do share may it be packing tape or will masking tape suffice??

Sent from my Wicked S4
[Nexus 7 (2013) Original Android Development] jak3z:
In fact you could tape to wake it up, and sleep it, you just need a very light magnet and attach to the tape. Then place it over the magnet that detects smart covers locate here:
[Nexus 7 (2013) Original Android Development] NoobieExtraordinare:
Any idea as how it compares to Elementalx? I run Franco on my Manta. I know it's a no frills kernel, but how is the performance? Any issues running it with a Carbon nightly? Thanks in advance

Farting out replies through my Dyson Air Multiplier.
[Nexus 7 (2013) Original Android Development] goldflame09:
these questions are all relative to the user. best way to find out would be to flash it and test yourself
[Nexus 7 (2013) Original Android Development] shortyboy:
The main reason for not adding s2w s2s d2w is they drain battery. This kernel goes into a deep sleep mode, boosting battery life.,unlike other fancy kernels.this kernel gets the job done right.
[Nexus 7 (2013) Original Android Development] cesarmanilla:
What he said, many of us have this kind of doubts all the time. It doesn't take that much, just try them day by day with your usual activities (gaming, reading) and you'll reach your answer in no time :)
[Nexus 7 (2013) Original Android Development] jak3z:
If users want I can provide a version of this kernel with Sweep2Wake and DoubleTap2Wake, if there's no interest I will just keep it for myself :)
[Nexus 7 (2013) Original Android Development] dre1187:
I'll give it a shot... Please PM me thanks!
[Nexus 7 (2013) Original Android Development] jak3z:
PM Sent, try it and let me know.
[Nexus 7 (2013) Original Android Development] shreddintyres:
id be interested to give it a shot as well, double check with franco n see if he minds you posting it in this thread, otherwise please hit me up in a pm :good:
[Nexus 7 (2013) Original Android Development] jak3z:
http://d-h.st/SiR

Pretty sure franco is ok with this, as it's just personal stuff, if there's enough interest I will make thread for it and maintain it when franco updates his kernel.

http://xdaforums.com/showthread.php?t=2457886 Is the thread for this mod now.
[Nexus 7 (2013) Original Android Development] SaberJ2X:
compared to other kernels?

This one is lean and mean and makes my battery last an eternity... Love it
[Nexus 7 (2013) Original Android Development] dre1187:
flashed it and dt2w is working nicely! thanks again :good:
[Nexus 7 (2013) Original Android Development] tni.andro:
The difference with S2W is that normally the touch screen controller is suspended during deep sleep; with S2W, it remains powered on and will wake the CPU when there is input.

Deep sleep with everything turned off (Wifi, GPS, Bluetooth, etc.) and no wakeups consumes around 7mW. S2W consumes an additional 55mW.

The 62mW power consumption with S2W correspond to the battery being drained in 10 days.
[Nexus 7 (2013) Original Android Development] jak3z:
I agree, on a Tablet it's very minimal the impact in battery life, that's why I gave it a shot since I use it a lot in portrait mode and I don't like reaching the back button to power it up that often.
[Nexus 7 (2013) Original Android Development] xbs:
I'm pretty interest in this too and I think it's a good idea to create a thread.

Also, would it be possible to have the S2W/DT2W feature enabled only when there's no power button pressing? e.g. timeout

IMO this would be ideal, S2W enabled until the power button is pressed.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Ah. No issues man. I'm sure you'll nail it by next weekend. Lol :)

You 23 year old ninja coding beauty! :p

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] tweaked:
Played a few minutes of reaper it it seemed happy. The voodoo display seems nice. Hope for fast charge, but ain't seen no one else getting it up and running. Other wise this is a great evening. Thanks, Franco.
[Nexus 7 (2013) Original Android Development] silvan g:
Nice! Flashing right away! Thanks man
[Nexus 7 (2013) Original Android Development] aamitabh28:
Speaker gain included?

Initial impressions v v good!!

Very smoothhh.
[Nexus 7 (2013) Original Android Development] masri1987:
i haven't seen franco since my Galaxy Nexus days ---

i looooved francoturtle..
[Nexus 7 (2013) Original Android Development] mazubo:
GOOOOOOOOAAAAAALLLLLLLLLLL! What I meant to say was, THANK YOU [MENTION=410271]fransisco[/MENTION]Franco!!!
[Nexus 7 (2013) Original Android Development] habylab:
Thank you!

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) Original Android Development] Crwolv:
Yaaaay finally. Thank you for your hard work.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Great first hour of usage. With a benchmark... And bit of gaming!?

:eek::D
[Nexus 7 (2013) Original Android Development] Crwolv:
Quite a few kernels here on XDA have fast charge for our flo.
[Nexus 7 (2013) Original Android Development] nexusmaniac:
r1 looks great, I just wish I had the new nexus 7 to go with it :(
[Nexus 7 (2013) Original Android Development] habylab:
Awh!!!

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) Original Android Development] style154:
Lol at the FAQ :). Gonna flash now thanks alot Franco :)
[Nexus 7 (2013) Original Android Development] bla_laber:
This is just great news! Unfortunatley, I didn't take my N7 with me to work today... grr
[Nexus 7 (2013) Original Android Development] ObihoernchenDE:
FKU thermal threshold doesn't stick. Maybe not implemented yet?

Kernel source isn't available yet so I can't look at it^^
[Nexus 7 (2013) Original Android Development] inffy:
Same here...bummer
[Nexus 7 (2013) Original Android Development] silvan g:
and here -___-
[Nexus 7 (2013) Original Android Development] zaclimon:
The game changer is here, thanks! :) so far it's smooth.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Original Android Development] bokagavrilov:
Franco could you add the swipe2sleep and doubletap2wake something like elementalx has? Or is there any alternative to touch control for n7
[Nexus 7 (2013) Original Android Development] jmudrick:
The OP is very readable. Take a crack at it.
[Nexus 7 (2013) Original Android Development] jak3z:
I can look into that, probably can be done just need to find the right statements and wake/suspend the S2W function. But no guarantees.

[MENTION=4118344]xbs[/MENTION] now that I think about this, this would eliminate the use of S2W, if you press the power button and suspend the device (and disable s2w) you won't be able to wake it up a again until you activate the screen again with the power button and let the device timeout to turn the screen off thus activating S2W again.

Did I get the idea right?
[Nexus 7 (2013) Original Android Development] borxnx:
This. Awesome idea. I don't mind pressing power when I've set the device down for a while, but when the screen times out it's nice having s2w. Plus it would remove the battery drain issue of keeping the digitizer powered all the time.
[Nexus 7 (2013) Original Android Development] xbs:
Yes, the power button would act as a s2w off button. If you know that you wont be using the device for several hours you turn the screen off manually and you'll be needing to turn it on again manually.

Until users press the power button s2w will be kept active.

Ideally turning the screen off with a soft button would keep the s2w active.
[Nexus 7 (2013) Original Android Development] mishko:
Thanks for this, flashed it now! But where do I activate the sweep-functions?
[Nexus 7 (2013) Original Android Development] jak3z:
Its activated by default I will provide a config file in next release.

Enviado desde mi Nexus 7 usando XDA Premium HD app
[Nexus 7 (2013) Original Android Development] habylab:
I'd create a thread if I were you - this is for Franco's! Not saying it isn't allowed, but a separate thread for conversation would be needed, right?!

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) Original Android Development] jak3z:
I will do one as soon as users can setup the s2w as they want, this was a "test" version after all.

Config files done! Tomorrow I will release it.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Franco just released a n4 Kernel with s2w and d2w. Hopefully there'll be one now for n7 too.
[Nexus 7 (2013) Original Android Development] NekroWolfen:
+1 I'd love that!
[Nexus 7 (2013) Original Android Development] -Jesco-:
he did say its coming for N7 (2013) users :)
[Nexus 7 (2013) Original Android Development] Shardzmi:
Yup, s2w and gamma control are the only needed things imo :)
[Nexus 7 (2013) Original Android Development] jak3z:
Let me tell you a secret, it was first done for the N7 2013 and then ported to mako, and I can confirm that it works on the N7 2013, so my build is pretty much useless unless you want to sweep2wake only in the navbar areas.

Thread with my sweep2wake and doubletap2wake version is up, I won't use this thread anymore for my stuff :P
[Nexus 7 (2013) Original Android Development] yellowdie:
Yep, it's comin' soon. And it works great! :D
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Franko, how many baby goats did you sacrifice for the unholy magic that is in this kernel? Battery life is absolutely insane, this is with a few hours of casual use each day. But even when I'm hammering on it for hours playing games and watching movies all day it only gets down to about 50%. No lie, it's about twice as good as anything else I've tried as far as battery life goes.

Yes, that is 4 1/2 days, with over 8 hours of screen on time. No games, but a few videos, some Netflix (but mostly over Chromecast), a few big downloads, mainly a bunch of browsing. Full stock odexed rom with Xposed mods, auto brightness, sync enabled, interactive/row/1024/veno/performanceGPU/-70mv/full speeds on everything. I am simply blown away, as I wasn't trying for any kind of battery marathon, I just noticed I hadn't charged it in 4 days and took a screenshot.

:thumbup::thumbup::thumbup:
[Nexus 7 (2013) Original Android Development] phynix5800:
I noticed dropped sound frames while playing via Bluetooth and screen off. I didn't change any kernel related settings. I am now on stock kernel and this issue is gone.

I'm using the stock ROM.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] jak3z:
I will have a look at this to provide some feedback to franco, thanks.
[Nexus 7 (2013) Original Android Development] sevenslugs:
This ROM is great..would love to have the double tap to wake feature though!
[Nexus 7 (2013) Original Android Development] darkobas:
Congratulations!
[Nexus 7 (2013) Original Android Development] morbidj:
Lmao!
[Nexus 7 (2013) Original Android Development] goldflame09:
READ up and maybe even the previous page
[Nexus 7 (2013) Original Android Development] Nbsss:
I'm using a smart magnetic case so S2W is useless for me..

Battery life is great using [MENTION=2743242]Cruiserdude[/MENTION] suggestions:

interactive/row/1024/veno/performanceGPU/-70mv

Nearly 10hrs of screen time, no lag, wifi always on

Thanks Franco!
[Nexus 7 (2013) Original Android Development] sevenslugs:
I know lol...
[Nexus 7 (2013) Original Android Development] dmeadows013:
What is 1024 for? And by performance GPU do you just mean stock 400mHz voltage?

Sent from my super awesome Nexus 7
[Nexus 7 (2013) Original Android Development] sevenslugs:
1024 is the Read Ahead Buffer Size ...

You can access this setting in apps like TricksterMod
[Nexus 7 (2013) Original Android Development] Class_of_punk26:
What mods with xposed you used?
[Nexus 7 (2013) Original Android Development] L-ViZ:
a few questions :):

-in idle mode always two kernels at lowest freq? not one?

-MPD disabled by default and using francos?

-gpu govenor only ondemand and performcance usable? (simple just doesn´t work, can select it but will go to latest selected one after confirming the change)

-gpu clock always [MENTION=218088]Max[/MENTION] (in my case 320), it never goes below. just every 20s for a moment. so when screen on always max available gpu clock?

sry for the questions xD i´m pretty new to the n7 like all of u :) still testing several kernel but francos seems to be the one which is giving me the best batterylife :) and i don´t need much power, want to read and browse, don´t play much, it´s more a device for the university :)

-edit:

i know what has been causing max cpu clock. just wondered why it always has been [MENTION=218088]Max[/MENTION] freq. then i asked my self what could cause it. the only thing that was "moving" on the screen were the bars of trickster mod and my circe battery. changed the battery icon to stock aaaaaaaand taaadaaa gpu went down to 128mhz. so i think you really can spare battery when let batteryicon stockish :) just a guess :)
[Nexus 7 (2013) Original Android Development] Cruiserdude:
This. And Performance GPU I'm talking governor. I use Trickster Pro as well.

:thumbup:
[Nexus 7 (2013) Original Android Development] joeyddr:
veno?
[Nexus 7 (2013) Original Android Development] shreddintyres:
its one of the choices for "TCP Congestion Avoidance algorithm"

http://xdaforums.com/showpost.php?p=28152737&postcount=2 <-- bottom of this post has tests run on the Galaxy Nexus

Here is an explanation of them

http://xdaforums.com/showpost.php?p=36663293&postcount=27

http://en.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm

- cheers
[Nexus 7 (2013) Original Android Development] L-ViZ:
veno is a tcp algorithm. i use westwood

edit: never mind :D already answered ;)
[Nexus 7 (2013) Original Android Development] vomer:
franco! good to see you here man :D
[Nexus 7 (2013) Original Android Development] dmeadows013:
Franco do you use the default flo config for this? Or do you customize it yourself?
[Nexus 7 (2013) Original Android Development] Bronto9:
Hi Francisco!

Can you please add the Kexec-hardboot patch to your kernel? It's needed for multirom

Thread with patch: http://xdaforums.com/showthread.php?p=45887036
[Nexus 7 (2013) Original Android Development] osm0sis:
Hey guys, not trying to derail the thread or anything, but Franco's threads are always great places to find savvy users, so I'm hoping one or more of you can lend a hand with adding BootUnlocker support for the Nexus 7 (2013):

http://xdaforums.com/showthread.php?p=45633298#post45633298

Thank you in advance. :)