yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] v12xke:
Deb celebration dance just a tad too early. Wi-Fi is busted for me on r17 and Wi-Fi fix is not working. Restored r16 from FKU and all is good. Reflash r17 and its busted again? Wuzzup with Wi-Fi on 4.4.4? I am running PA's latest (20140625). Thanks.
[Nexus 7 (2013) Original Android Development] Crythar:
Running r17 deb on latest pa, wifi works fine
[Nexus 7 (2013) Original Android Development] v12xke:
Cool. Thanks. I'll wipe and give it another go. Appreciate the quick feedback.

---------- Post added at 07:33 PM ---------- Previous post was at 07:05 PM ----------

Reflashed ROM (PA), restored boot-r17-deb.img and Wi-Fi is back. Cheers.
[Nexus 7 (2013) Original Android Development] osm0sis:
I suppose disabling the lmkd in the ramdisk might help. We could also "su; stop lmkd;" perhaps to test the effect. Anyone on L with my experimental r19-L ramdisk image want to give that a spin and let me know if it helps the lag? I'm in the middle of my move still or you know I'd be on the front lines myself. :D

Edit: Never mind, just finished the move and found a moment to try this. Totally destabilizes the ROM to disable lmkd. Had to hard reset. ;)
[Nexus 7 (2013) Original Android Development] jordi.id96:
I have uploaded the wifi config for 4.4.3 and 4.4.4. This is usefull for who used r16 and old wifi drivers (4.4.2) on 4.4.3 or 4.4.4 and now wants to update to r17.

Flashable zip (flash only on r17): https://mega.co.nz/#!uloHWYSY!Ma5_6UIRP99xkaTXy8S9PXYjQ9dAHh11xj9J8mis6M8
[Nexus 7 (2013) Original Android Development] quickdraw86:
Many thanks for the update. Everything is working well on r17 on FLO. I still use r396 on my gnex as well, and couldn't be happier to use your work on my tab as well. Bought FKU and the color app to support, thanks.
[Nexus 7 (2013) Original Android Development] Nekromantik:
Is it easy to rebuild with ex fat support?
[Nexus 7 (2013) Original Android Development] morbidj:
Would some one please do me a favor and check out these logs I'm getting reboots with17 on liquid smooth I've isolated it to this kernel but others are not reporting issues... https://www.dropbox.com/s/ah59tbdz8ho6muu/2014-06-29_14.40-logs.zip kernel is blazing fast BTW very happy with it other than reboots... Thanks Franco
[Nexus 7 (2013) Original Android Development] drewski_1:
r17 & wifi working fine on Deb Carbon 4.4.4
[Nexus 7 (2013) Original Android Development] ahow628:
I'm stock rooted and when I was running r17 yesterday, it was missing touches to the screen. Especially if I was using more than one finger and tapping randomly around the screen (like in a game). I went back to stock and it seemed better, but still seemed like it was missing touches. I have no proof, but it just felt that way.

Anyone have this issue or notice anything like it?
[Nexus 7 (2013) Original Android Development] RobbieL811:
It's not a problem with the kernel, it's a problem with the device. A lot of N7² have problems with multi touch. Just like you described. Google N7 multi touch problems & read.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] ahow628:
Ah, I found the touchscreen driver thread. Flashing and testing as we speak. Thanks.
[Nexus 7 (2013) Original Android Development] SeemannBootlegs:
Can you share a link to that thread?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] ahow628:
http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) Original Android Development] bleuxeon:
I have just bought the Nexus 7, unlocked, rooted flashed PA + franco :good:

Just a question, in the Nexus 5 there are a lot of color profils. I can't see any in the Nexus 7 :(

Nobody already made some?
[Nexus 7 (2013) Original Android Development] marouane80:
glitch on cm11 nightly 4.4.4. does it support cm11 ?
[Nexus 7 (2013) Original Android Development] TrenchKato:
No
[Nexus 7 (2013) Original Android Development] Doo Doo:
It would be nice if someone could make a cm version like in the Nexus 4 forum
[Nexus 7 (2013) Original Android Development] osm0sis:
If you have the time and skills, go for it. Otherwise, please wait patiently for the people who have the skills to also have the time. Someone has @ mentioned TheDarkDefender already, but obviously he's busy.

The Gingerbread Man has some available for download on his Drive, but there aren't any included as presets in f.Ku yet. Come up with something good and maybe it'll get added. :)
[Nexus 7 (2013) Original Android Development] Doo Doo:
I wish I had the skills to do it but unfortunately I don't :(

I'll just sit back and wait then sorry for being so eager and impatient
[Nexus 7 (2013) Original Android Development] RobbieL811:
What exactly is needed to make it compatible with CM?

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] zaclimon:
Those 2 commits:

https://github.com/zaclimon/mako-linaro/commit/806fd4be9bccf7288265f227dc0770193db07f36

and

https://github.com/zaclimon/mako-linaro/commit/678d1e58ac2a97f749c58d0118d59095a35dad9a

I can try to cook up one for you guys if you want it. :)

Also [MENTION=4544860]osm0sis[/MENTION] looks like we got some canada day presents!! :D

https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-l-preview
[Nexus 7 (2013) Original Android Development] poondog:
Two caf commits only I believe plus their ramdisk you'll need

If you see darkdefenders repo you'll see those commits
[Nexus 7 (2013) Original Android Development] RobbieL811:
I was thinking of giving it a shot. Let me know if you are gonna do it, so we wont both be doing the same thing. If you wanna do it, go ahead.
[Nexus 7 (2013) Original Android Development] zaclimon:
Well I probably won't do it until tomorrow night or thursday. So it would be better, if you have the time, to build it yourself. :p
[Nexus 7 (2013) Original Android Development] RobbieL811:
Do I need to use the CM ramdisk as this other user stated?
[Nexus 7 (2013) Original Android Development] zaclimon:
If it's pure Franco.kernel, you won't need a different ramdisk other than the one Franco has.
[Nexus 7 (2013) Original Android Development] Doo Doo:
[MENTION=4217103]zaclimon[/MENTION] could you cook up a CM compatible version for us please
[Nexus 7 (2013) Original Android Development] RobbieL811:
r17 for CM. http://www.mediafire.com/download/ezlt5bjk8dda7en/r17_CAF.img
[Nexus 7 (2013) Original Android Development] marouane80:
great. thanks

hope you'll follow this kernel developement

can you please add dynsync feature ?
[Nexus 7 (2013) Original Android Development] RobbieL811:
I do not personally use CM, but I am thinking about opening a new thread for this kernel. Keep your eyes open in the N7² Android Development section.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] zaclimon:
If you guys are open for it, I'm open to continue the sabermod kernel I'm doing like I've done it for the N4 at the moment. So far it is only some personal builds I'm doing but, I feel like there's not enough kernels in the N7 forums.
[Nexus 7 (2013) Original Android Development] Draygon:
Please do it, zaclimon. :)
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Sorry guys. I've been real busy with work lately. Lack of sleep, and to top it all off, my ubuntu's been acting real weird lately.

Nice to see more people volunteering to do a cm version.

Oh, and.. I'm on the developer preview right now and it is so effin solid, I don't think I'll ever be going back to kitkat.

You guys should give it a shot. :D

Plus the onscreen is better than kitkat/franco and I'm thrilled to see what fk for the L version will bring us.

Edit: oh. I see osmosis already did.
[Nexus 7 (2013) Original Android Development] Mysterion1:
Big thanks [MENTION=3292224]franciscofranco[/MENTION] for lowering the backlight level in r17!
[Nexus 7 (2013) Original Android Development] Doo Doo:
It breaks root on PAC ROM :(
[Nexus 7 (2013) Original Android Development] RobbieL811:
I flashed it on CM & had no problem whatsoever with root. Did the usual flashing supersu fix it? Also, I started a thread for the CAF kernel. Hang on I'll edit this post with the link.

http://xdaforums.com/nexus-7-2013/development/kernel-franco-kernel-caf-r17-t2803037

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] Doo Doo:
I didn't even try to flash supersu because PAC ROM already has superuser built in plus I didn't want them to conflict with each other if I did flash it
[Nexus 7 (2013) Original Android Development] RobbieL811:
They won't conflict. SuperSU will just take over. You won't use SuperUser anymore.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] Doo Doo:
Oh ok I didn't know that thanks for letting me know :)

I'll give it another shot later on after my tablet charges back up as I only got 9% as I type this

Also please make dt2w or s2w available in your future kernels
[Nexus 7 (2013) Original Android Development] devilsshadow:
Might wanna read this thread's OP, especially the part regarding feature requests.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] habylab:
This would be great! I don't feel like there are enough ROMs or Kernels for our device. May be due to how fast it is? I want a Sabermod CM11 build, and kernel!

I've been using Ak's kernel as it attracts me with his long changelogs etc. I'm easily bought! But apart from that, and this, there is nothing regularly updated that interests me. Faux has done great work too, obviously!

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Nexus 7 (2013) Original Android Development] bleuxeon:
I would like to create a snappy profil that would be used when camera is used.

The goal is to reduce the lag in focus, time needed to save photos etc...

Here is what I was thinking of :

-raising the min frequency to...let say, 1026MHz

or

-tweaking the governor in order to have all 4 cores ON

which one looks the most relevant to you?
[Nexus 7 (2013) Original Android Development] LiquidSolstice:
I'm going to make an educated guess and say that clock speed has nothing to do with how fast your camera can focus.
[Nexus 7 (2013) Original Android Development] bleuxeon:
Of course the APN's hardware latency will always be there...

but I also think that some delay can be introduced by the governor itself :p

So without any help, I would simply set the gov to performance, but this is kind of "brute force"...far from smart way.
[Nexus 7 (2013) Original Android Development] habylab:
Yeah I will would say both of them are relevant!
[Nexus 7 (2013) Original Android Development] RobbieL811:
He was talking to me. He's just posting in the wrong thread.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] LiquidSolstice:
...er, APNs have nothing to do with the camera either (unless you're referring to something other than Access Point Names). Focus time is entirely dependent on the lens; the preview that you see in the viewfinder isn't being slowed down by the processor.

The camera in the Nexus 7 just simply isn't very good and never will be. It's an interesting idea that you have, but I'm quite sure that if speeding up camera focus and image processing was as simple as spiking the CPU/GPU, we would have done that already.

The actual image processing part is probably somewhat influenced by the CPU, but probably more influenced by I/O. I don't think you're on the right track for what you're trying to do.
[Nexus 7 (2013) Original Android Development] bleuxeon:
Yes sorry : APN is a french acronym for digital camera.

Regarding the IO, are you thinking about the saving part or more generaly during the whole shooting process (moving around, focusing, capturing)?

I am also wondering how much the GPU is involved. I will try to lower its frequency to see how it goes with this simulated lower GPU.
[Nexus 7 (2013) Original Android Development] LiquidSolstice:
That makes much more sense.

The SoCs that power devices like the Nexus 7 are quite powerful; I doubt the bottleneck for a simple 5MP raw file comes from that. I would be more inclined to investigate the IO scheduler.

I'm not 100% confident that the GPU is used at all during the camera process. Again, franco will know more than I could ever hope to, but I backtrack to my original statement; if the CPU/GPU/IO was all that was needed to improve things like focus, shutter lag, and post processing, I feel like such changes would already have been merged into not just CM/Custom Repos, but AOSP repos, and used by Google by default.

I maintain my confidence in that its entirely from the hardware sensor's capabilities.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Am I blind or has the file been removed?
[Nexus 7 (2013) Original Android Development] osm0sis:
r17 > r19-test :p

And I discussed how it doesn't work correctly so I removed it. ;)
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Sorry must of missed that!
[Nexus 7 (2013) Original Android Development] osm0sis:
Yeah, running 2 LMKs (1 from 4.4.x kernel, 1 from L ROM) is bad mojo. :cowboy:

Not sure how ElementalX does it, or maybe the people running it just haven't noticed the issues yet. ;)
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
So that means currently there's no fk kernel for L for this device? No biggy if there isn't, I already rolled my n5 back to kk
[Nexus 7 (2013) Original Android Development] osm0sis:
Exactly. As far as I know, ElementalX is the only custom kernel reporting to work, but my doubts about how they handled LMK might also call that into question. Not sure if the kernel source is out to update for proper L support or not; that'd be up to [MENTION=3292224]franciscofranco[/MENTION] of course. :)
[Nexus 7 (2013) Original Android Development] L.F.B.:
Just flashed the r17 in my 4.4.4 and all pretty smooth here! thanks Franco!

Anyone have a good settings to the r17? Its my first time with Franco Kernel. thanks in advance! :)
[Nexus 7 (2013) Original Android Development] glukasil:
Hi franco....is it possible to implement Logitech Unifying device support in your kernel ?
[Nexus 7 (2013) Original Android Development] masri1987:
does this kernel have double tap 2 wake?
[Nexus 7 (2013) Original Android Development] drewski_1:
No. elemental does.
[Nexus 7 (2013) Original Android Development] v12xke:
Faux does as well.
[Nexus 7 (2013) Original Android Development] teddy0209:
Glitch & AK does too...
[Nexus 7 (2013) Original Android Development] SimoxTav:
After I flashed the new kernel I'm experiencing several problems (AOSP 4.4.4):

- overheating in idle mode (around the camera) that leads to heavy battery drain even in stand-by;

- some SoD;

- long time to resume from sleep (I press the button and the device turns on screen after 2-3 seconds);

It's quite strange because all previous releases were working really well (and the installed software it's the same).

I've not yet extracted the log, but I'll try to reflash the whole device before extracting just to see if it could be related to some dirty works done before.
[Nexus 7 (2013) Original Android Development] habylab:
Nothing here. Clean install in order.

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Nexus 7 (2013) Original Android Development] jbrantley130:
Check out the Franco Kernel Learners Lounge forum..... There's a complete guide and list of settings there. I use the settings listed there for my Flo and they work great.
[Nexus 7 (2013) Original Android Development] zaclimon:
[MENTION=4778194]TheDarkDefender[/MENTION] in case you were searching for the SM Franco,(and the others that wanted it) here it is : http://xdaforums.com/showthread.php?t=2809979

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] SimoxTav:
After a clean flash everything returned awesome as before :D
[Nexus 7 (2013) Original Android Development] LP6:
WiFi is not working on Deb with OmniROM nightly from 20140709 until the latest 20140714 with franco.Kernel r17-deb.

WiFi switch turns grey and seemingly keeps on trying to turn it on until next reboot, it does work with OmniROM nightly 20140708.
[Nexus 7 (2013) Original Android Development] osm0sis:
Well you know r17 didn't change, so it must be ROM, right? :)

Someone reported a similar Wi-Fi issue on Vanir on tuna so I'm thinking there must be a change that all the ROMs just started using that breaks it. Bring it up with your ROM maintainers, give them the date it started failing and see if they can narrow anything down to fix. :good:
[Nexus 7 (2013) Original Android Development] LP6:
Thanks. I've already reported this on the OmniROM forum. The curious part is that first franco.Kernel cured the malfunctioning WiFi on Omni and now its going the other way, but maybe they did some kernel trick to go round the actual problem to get the WiFi working again.

Sadly I have to use stock Omni kernel for now since WiFi really is quite essential part of tablet or smartphone usage.

And yes, hopefully the ROMs keep on changing. ;)
[Nexus 7 (2013) Original Android Development] deakelem:
you need not ever to apologize to us man haha.. keep up the great work im sure everyone else appreciates it as much as i do :)
[Nexus 7 (2013) Original Android Development] maverick_hunter:
I've been getting random reboots on r17. Not enough to be annoying but is anyone else experiencing them? Not undervolting, but slightly overclocked.
[Nexus 7 (2013) Original Android Development] osm0sis:
I was getting reboots overclocked to 1.7GHz, but it seems okay at 1.6; my guess is some devices are more stable at the OC freqs than others. Bumping up the voltage on the freq might stabilize it.
[Nexus 7 (2013) Original Android Development] fradbari:
hi, at someone else happens, on r17, that max cpu is not saved, but it changes by itself?
[Nexus 7 (2013) Original Android Development] sizzlers:
Same, over and over
[Nexus 7 (2013) Original Android Development] fradbari:
so sad to see that Franco has this big problem and is not solved
[Nexus 7 (2013) Original Android Development] Hatshipuh:
Sad to see that kernel flasher still don't understand how thermal throttle works.

Tap-a-talked from my Nexus 5
[Nexus 7 (2013) Original Android Development] fradbari:
so thermal throttle delete permanently max CPU setted?

Is so strange, that is useless to put max cpu freq, since it's changed from thermal rules....

I don't know how works thermal logic, but it's stupid allows you to set max cpu, so is automatically changed..

Correct me if i'm wrong
[Nexus 7 (2013) Original Android Development] Puzzlegirl:
I have no idea what you are saying here: maybe it's a language problem. Perhaps you need to clear the data from Franco kernel updater (if that's what you're using) and reboot before you set your preferences. My device is running perfectly, overclocked at 1620 MHz and I don't have a problem with thermal throttle. Perhaps you could try and explain exactly what your problem is in a clear way, so that someone can try to help you.
[Nexus 7 (2013) Original Android Development] fradbari:
sorry:

with last version of franco kernel the max cpu can't be saved, but it changes by itself. When you sett some value, they change immediatly when you exit from franco app

someone know how this happens ?
[Nexus 7 (2013) Original Android Development] quickdraw86:
What the others are trying to explain to you is that what you describe as an issue really isn't... You don't seem to understand what thermal throttling is, or how it works:

http://en.m.wikipedia.org/wiki/Dynamic_frequency_scaling

Basically, it's a safety system in place that can manipulate CPU speeds to prevent your CPU from overheating and cooking itself... So, you can set a max speed, but that doesn't necessarily mean that your device will max out depending on your activities and governors, and thermal throttling. You could use the FKU app to tune your settings too...

Perhaps this would be of use to you as well:

http://xdaforums.com/showthread.php?t=2532422
[Nexus 7 (2013) Original Android Development] fradbari:
ok, so if i set, with franco updater, max cpu freq to 1242 mhz, and one minute later this value automaticaly change on 918 mhz, and again one minute later change on 1134mhz, always on franco utility (no cpu stats or other, only max cpu allowed), is not a problem :eek::eek:?!?!

sorry, but this I do not understand.....

If you set max freq, that must remain the same, obviously the freq of cpu change in according to therma throttle!

I've removed franco kerel only for this problem, that not existent on other version/model (like nexus 5 version)
[Nexus 7 (2013) Original Android Development] quickdraw86:
Ah. Had you explained before in clearer detail, more would have understood... You mean the actual number of your max setting changed, not the frequency itself.
[Nexus 7 (2013) Original Android Development] fradbari:
exactly...

the max cpu freq change automatically from the second picture, to first one and also to other freq.

Sorry, I don't know how i can explain it better

in my opinion, this is a application bug, also because i've installed three times paranoid + franco and have the same problem
[Nexus 7 (2013) Original Android Development] quickdraw86:
I agree that perhaps it's the app... As he's updated it recently. I haven't seen more than one other person with that problem though, so not sure why some are affected more so than others. Get him a logcat if you can.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
I think we solved this for one other guy. It was cos his super user app. Use SuperSu by chainfire, don't use superuser by kouch. At least with this kernel as they don't seem to play nice some how. My advice is disable / uninstall any other superuser app you have, reboot ,get on latest twrp recovery, flash supersu, flash franco, clear app fku data, reboot. Boot up allow screen to time out on its own then set your **** up.

Edit

Sorry I thought I was in nexus 5 forum then. Try my advice anyway it certainly wont hurt
[Nexus 7 (2013) Original Android Development] fradbari:
sorry, but now i've removed franco :(:(

however i've always use supersu and not superuser; maybe the problem are rom releated (i've last paranoid android)
[Nexus 7 (2013) Original Android Development] Aerowinder:
It wasn't the Superuser app, the problem was I was flashing the kernel via the zip file because I was flashing it at the same time as the ROM. The files are indeed renamed automatically if you flash the kernel through FKU. But if you flash zip, nope.
[Nexus 7 (2013) Original Android Development] draco259:
Is that the only setting that doesn't stick?
[Nexus 7 (2013) Original Android Development] fradbari:
No.. Also gpu Freq have the same problem.

I've tried cleaning Franco updater data, wipe Chace and delvick, fix permission, but the problem doesn't solve

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 7 (2013) Original Android Development] draco259:
I have had this problem with a different kernel app before, it may be worth uninstalling and re-installing busybox.
[Nexus 7 (2013) Original Android Development] fradbari:
Thanks :D

i'll try:good:
[Nexus 7 (2013) Original Android Development] idCyber:
I have CM11 (29/07/2014 nightly) and I've downloaded the kernel from within the Franco kernel updater app from Google Play Store, my boot animation changed to some lines of different colors and when it finished booting, my "flo" ran slow and all colors got weird.
[Nexus 7 (2013) Original Android Development] ekine:
Someone correct me if I'm wrong ... but I think CM does not support AOSP kernels like frank. To n4 if there CM version, but not N7
[Nexus 7 (2013) Original Android Development] idCyber:
Dunno if it's compatible with CM11 or not but OP's FAQ says :

2. This kernel works on Y or X rom?

A: This is one of the worse questions you can ask on my threads. This is a Nexus, it works on every rom you can possibly imagine.
[Nexus 7 (2013) Original Android Development] osm0sis:
It isn't compatible. CM decided to deviate by using the CAF video drivers, while we continue to use the AOSP ones.
[Nexus 7 (2013) Original Android Development] ekine:
Every rom AOSP.

For N5 and N4 there are CM versión... But N7 no or I don't know