yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Ah. My n7 has been longing for this!

Thank you franco!

[MENTION=3292224]franciscofranco[/MENTION] any idea on including the n7 display calibration in FKU?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] Old-school:
[/QUOTE=franciscofranco;45633379]

Voodoo Display for Flo is here: https://plus.google.com/u/0/communities/103123288128442067861 just join the community, apply for the beta testing, download the app from the play store and you can test it.[/QUOTE]

Already did a few days ago. All it really does right now is identify the display, I have a JDI. Excited for the developments coming flo's way.
[Nexus 7 (2013) Original Android Development] Nburnes:
No. It most definitely works. Swipe right and activate superuser, right again and test inverted, if it works push the bottom button and it will bring you to a new screen to enable his calibration.
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Thanks! flashing now!
[Nexus 7 (2013) Original Android Development] franciscofranco:
:)

Voodoo Display app? No, thats supercurio's app. I've taken a little peak into the display and mdp composition layer driver and I've seen a red, green and blue struct fields, but I don't know anything else, haven't tried or peaked longer.

Already did a few days ago. All it really does right now is identify the display, I have a JDI. Excited for the developments coming flo's way.

No, you can apply the custom gamma 2.2 preset from within the app.
[Nexus 7 (2013) Original Android Development] Bobtehblob:
Yes Buddy! Flashing now :D
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
No, you usually write your own hacks right? Will you be doing one (like Color control on n4) with FKU?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] franciscofranco:
I can't answer that right now, I still don't know enough about the N7 drivers to know if its possible. Just need time :)
[Nexus 7 (2013) Original Android Development] inffy:
Yay. Thanks franco
[Nexus 7 (2013) Original Android Development] ÜBER™:
Wow... Just wow. Easily the smoothest experience I've had yet with my nexus 7. Can't say thanks enough.
[Nexus 7 (2013) Original Android Development] bass0324:
So I loved Franco kernel on the original nexus 7 and couldn't wait for it to come here so jumped at the opportunity to flag right away. Came from faux and had no issues and never cared to overclock anything, but with this r1 kernel, real racing 3 is very choppy and I didn't experience that before with the n7.2
[Nexus 7 (2013) Original Android Development] shreddintyres:
Kernel has hardly been out for a day but so far battery life for me is on par with other kernels ive tested, so far today ive done some video streaming via Netflix, watching an hour of videos via vlc about an hour of gaming and a fair bit of web browsing and e-reading with device at near full brightness, sitting at 5 hrs screen on 19.5 hours standby and 40% remaining. Ymmv

Faux kernel installs a few extra files that may be conflicting with Franco kernel, go through and replace the files in the faux kernel zip with those from your stock ROM, make sure and delete the Init.d scripts especially

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] mystifiyer:
This will be useful as movies typically do not have a standard in loudness.

Options will be greatly appreciated.
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Don't hold your breath. He never gave a real answer but I doubt it will ever make its way in. Same as n4.
[Nexus 7 (2013) Original Android Development] mystifiyer:
No problem.

I understand he is not developing for me, but merely sharing what he develop.

If the time comes when the kernel cannot meet my needs, I can just switch to another kernel.

Usually kernel breakup are kinder to the heart. :)
[Nexus 7 (2013) Original Android Development] franciscofranco:
Can you test this:

echo 50 > /sys/module/msm_kgsl_core/parameters/sample_time_ms

Let me know if it helps.

We'll see what happens.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Can a Deb user confirm that his boots up and functions normally please. Just flash the attached zip in the recovery.
[Nexus 7 (2013) Original Android Development] inffy:
Will try

---------- Post added at 06:42 AM ---------- Previous post was at 06:38 AM ----------

Tested with deb. Boots and seems to behave normally :)
[Nexus 7 (2013) Original Android Development] franciscofranco:
Good. Mr. [MENTION=2819760]jak3z[/MENTION] made an hybrid ramdisk that works for both Flo and Deb :) Going to release r2 then.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Pushed r2

* Fix Deb support, now it boots *yay*

* Add Undervolt interface

* Add USB Fast Charge

I'm unable, again, to push changes to git, tried a bunch of times and this is what happens:

Counting objects: 2493673, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (423496/423496), done.

error: RPC failed; result=22, HTTP code = 4138 MiB | 380.00 KiB/s

fatal: The remote end hung up unexpectedly

Writing objects: 100% (2493673/2493673), 667.81 MiB | 54.04 MiB/s, done.

Total 2493673 (delta 2050818), reused 2486605 (delta 2045561)

fatal: The remote end hung up unexpectedly

I'll try again tomorrow with the ethernet cable connected.
[Nexus 7 (2013) Original Android Development] lndeed:
It's odd, custom kernels are causing major problems with Slimport. Plugging in Slimport causes the device to slow to a crawl and eventually forces a reboot unless it is unplugged. The odd thing is that, according to faux, even with absolutely nothing related to Slimport being changed in his kernel it's still being broken. I've tested this with Cyanogenmod, Slimbean, Carbon, and the unofficial AOKP build with both faux and franco kernel. Only the stock ROM and PA are problem-free with custom kernels. However with every one of the above ROMs, Slimport works perfectly fine as long as their respective stock kernels are kept.

At this point I don't even know if this is a ROM or a kernel issue, but if there's anything I can do to help fix it please do let me know.
[Nexus 7 (2013) Original Android Development] aamitabh28:
I don't know what people with bad or average battery are doing wrongly but lemme tell u.. It doesn't get better than this. O strutters all through the day. Tried Riptide 2 worked buttery smooth.. Ever cpu undecided locked at 1.1 ghz everything seemed perfect. Battery life hasnt ever been better.. For me with my usage. This is the best no nonsence all work kernel ive ever tried n i cnt thank franco enough to make my exclusive with my tablet so much more pleasurable. Realy appreciate it man.

Edit:i forgot to mention a single percent battery drop in over 9 hours at night with wifi off!

Going to try v2 now n undervolt a bit n see what happens.
[Nexus 7 (2013) Original Android Development] franciscofranco:
0 change on slimport also here. I have no clue about that, I'm sorry. Best thing you can do is to capture /proc/kmsg and the logcat when the slimport is connected and while its crawling like you describe.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
New update seems to be much, much smoother for me. I will use it for a couple days and let you know if I run into any issues.

Edit: Riptide GP2 is showing a lot of lag still. Getting maybe 20 FPS most of the time and the menu lags a lot too.
[Nexus 7 (2013) Original Android Development] aamitabh28:
Dunno how you are facing the issue..

though i must admit i changed the GPU governor from performance to ondemand in trickster mod..maybe that's what worked for me as i dont have this issue at all..FKU does not have a GPU control interface AFAIK..i may be completely wrong though

Edit: I verified it..thats the issue..performance governor makes GPU idle at 128 mhz whereas ondemand ramps it up.Dunno why performance is the default governor here..maybe franco can shed some light.All other people expereincing choppiness can set their GPU governor to ondemand and it'll all be gone :D@cyberprodigy
[Nexus 7 (2013) Original Android Development] ktkr:
Thanks for the update franco, there's an issue that I found UV is causing FC's everywhere at 800mv which was just fine on my device using other custom kernels like faux and elementalx even with both cpu and gpu overclocked. FYI the lowest safe number is 775 on my device but if I try this the device immediately reboots. It's working fine when not touching UV settings.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Its not using any performance governor, its using an algorithm that I coded from scratch. It should show "interactive" as governor name, dunno why it isn't. Anyway why would you idle the GPU at any frequency above the minimum? If its idling its not being used. I can play all games just fine on my N7. What you can do is also reduce the up_threshold of the GPU governor, path is last page.

Undervolt is FC'ing what? I undervolted a bunch and I see nothing strange. Also I don't give support for undervolting, you do it knowing your risks of rebooting or other crap.
[Nexus 7 (2013) Original Android Development] aamitabh28:
What i meant was that FKU does not have an GPU interface for obvious reasons as you have only one "interactive" that you coded.

The issue is that after kernel flash games lag..and the lag goes away on selecting ondemand from trickster.Both idle well..that isnt the problem.

I dont know how to exolain this..but it's happening here

Edit: Happened on r1 as well.
[Nexus 7 (2013) Original Android Development] ktkr:
Almost all apps including system processes force close with -100mv uv, but it doesn't happen on other kernels. I just tried -100mv on elementalx with cpu @ 1.7ghz and gpu @ 487mhz and it's running fine. I'll flash back r2 and try again, I'll be glad to help if you need logs or something else.

After messing with the UV settings it finally settled at 850mv.
[Nexus 7 (2013) Original Android Development] Nbsss:
Quite day at work/uni.....just read every single post, think I'm ready to flash r2 :)
[Nexus 7 (2013) Original Android Development] habylab:
Look for the revert WiFi fix zip!

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Nexus 7 (2013) Original Android Development] Draygon:
Anyone? :)
[Nexus 7 (2013) Original Android Development] habylab:
I don't think there is a zip. Have a look two pages or so back.
[Nexus 7 (2013) Original Android Development] abjexstallion:
Is the revert wifi fix on this thread?

BTW I'm on latest slimRom which is 4.4.3...

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] Doo Doo:
Could somebody make a cm version of r19 please
[Nexus 7 (2013) Original Android Development] habylab:
No, have a google. Named deprimator restore zip for me.

Edit: may be wrong file, search for refer 4.4.3 WiFi fix .zip!
[Nexus 7 (2013) Original Android Development] Draygon:
Best solution would be if franco could release the update for 4.4.3 :)
[Nexus 7 (2013) Original Android Development] poondog:
Look at the link in the OP please to find the test r19
[Nexus 7 (2013) Original Android Development] docfuz:
Hi. I'm on deb LTE and using r16 without any issue. With any I do mean it. So there could be some discrepancies between different n7 hardware versions?

doc
[Nexus 7 (2013) Original Android Development] Jerreth:
Well i was going to post about problems with WiFi spose no need lol so the problem is with the WiFi driver in the kernel not being compatible with 4.4.3? Im just curious is all.
[Nexus 7 (2013) Original Android Development] TrenchKato:
The WiFi stack changed with 4.4.3. so if you are running 4.4.3 you can use r19 test image in the original post.
[Nexus 7 (2013) Original Android Development] Jerreth:
Great thank you.
[Nexus 7 (2013) Original Android Development] drewski_1:
+1. WiFi is working fine on Deb without any additional patches on Carbon 4.4.3
[Nexus 7 (2013) Original Android Development] Hatshipuh:
That's because Carbon apparently still hasn't updated their Wifi driver. Normally Wifi breaks when flashing an 4.4.2 on an 4.4.3 ROM and vice versa.

In this case 4.4.3 kernel break Wifi on Carbon, that's why r16 is still working.
[Nexus 7 (2013) Original Android Development] taadow1030:
I give... Where is r19? I looked and found up to 16. I even checked the test folder. I guess my eyes are worse than I thought
[Nexus 7 (2013) Original Android Development] zaclimon:
The boot.img inside the test folder is r19.
[Nexus 7 (2013) Original Android Development] taadow1030:
Thanks button pressed!
[Nexus 7 (2013) Original Android Development] glukasil:
Hi guys. Could you please make flashable zip with 19 test kernel...thanx a lot
[Nexus 7 (2013) Original Android Development] poondog:
You can use Franco's app to flash. The test images are only in image format so they are moderately noob proof

Or flashify
[Nexus 7 (2013) Original Android Development] wildestpixel:
what he said
[Nexus 7 (2013) Original Android Development] glukasil:
Thanx guys....my pc is down at the moment....flashify is brilliant
[Nexus 7 (2013) Original Android Development] Draygon:
Will there be an update for 4.4.4? I want to install it as .zip not as .img
[Nexus 7 (2013) Original Android Development] AutomaticFailure27:
No. 4.4.4 doesn't change anything kernel side and post above you states about flashify. Use that to flash the .img or fastboot flash it.
[Nexus 7 (2013) Original Android Development] MikeRL100:
Omni had WiFi issues with drivers that are currently being fixed. Wonder if that had something to do with my WiFi problems.
[Nexus 7 (2013) Original Android Development] osm0sis:
I've just devised a third option for this as well. :D

http://xdaforums.com/showthread.php?p=53543397

It's a flashable zip that flashes a .img you put in the directory with it. :cowboy:
[Nexus 7 (2013) Original Android Development] AutomaticFailure27:
You are a mad man!
[Nexus 7 (2013) Original Android Development] itasoulas:
franco kernel updater update!!! Supports color profiles for N7 2013....:good: Thanks man! :p
[Nexus 7 (2013) Original Android Development] Doo Doo:
Could somebody please make a cm version of the test kernel r19
[Nexus 7 (2013) Original Android Development] morbidj:
About time.. This device gets no love
[Nexus 7 (2013) Original Android Development] 5FOOTER:
Give it a try I don't think anyone else will.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] RobbieL811:
Just download an old .zip & replace the boot.img with the one you want. There's your flashable zip.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] kingofcomedy:
Or use Flashify.
[Nexus 7 (2013) Original Android Development] Doo Doo:
Come on bro are you serious if I knew how to do it I would've never asked for somebody else to think about it
[Nexus 7 (2013) Original Android Development] osm0sis:
Or my new Flashify Script zip:

;)

---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------

Search the thread for the person who made the last one and ask him directly with a @ mention or PM.
[Nexus 7 (2013) Original Android Development] kingofcomedy:
I've already read about that, sounds great, but I'll stay with Flashify and/or fastboot. ;)
[Nexus 7 (2013) Original Android Development] Doo Doo:
[MENTION=4778194]TheDarkDefender[/MENTION] could you please try to make a cm version of test kernel r19
[Nexus 7 (2013) Original Android Development] k0smo86:
Installed r16 and had no Wifi...known issue I assume. Fix coming?
[Nexus 7 (2013) Original Android Development] osm0sis:
Fix came. r19-test in the /test directory at the link in the OP. :good:
[Nexus 7 (2013) Original Android Development] ahow628:
Same for me. Scared me for a sec.
[Nexus 7 (2013) Original Android Development] fradbari:
Seem that Android 4.4.3 are still not supported ?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 7 (2013) Original Android Development] Hatshipuh:
What are you talking about, running Franco r19 on 4.4.4.

And don't ask where to get it, it's been posted all over the last few pages.

Tap-a-talked from my Nexus 5
[Nexus 7 (2013) Original Android Development] fradbari:
but wi-fi problem? is not a version related problem?
[Nexus 7 (2013) Original Android Development] Hatshipuh:
There are no Wifi problems with r19 and 4.4.4.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Please read previous posts in the thread. r19 with fixed WiFi is the boot.IMG in Franco's test folder. Download it, use either:

1. Flashify

2. FKU app

3. osm0sis's .img flashing script

To install it > profit. r19 works on 4.4.3 and 4.4.4 too BTW.
[Nexus 7 (2013) Original Android Development] LiquidSolstice:
Your ROM needs to have all the Flo hardware blobs in order for you to use 4.4.3 kernels without losing wifi. Ask your ROM dev.
[Nexus 7 (2013) Original Android Development] osm0sis:
So... I got r19-test running on L. ;)

http://v.ht/osmod

Flash using my Flashify Script zip:

http://v.ht/osm0
[Nexus 7 (2013) Original Android Development] v12xke:
Deb on r19

Robbie, I am running a Deb and used your r19 test file below. Boots just fine and I tested several apps. FKU shows r19 as running. Thing is I noticed

Wi-Fi was off and I could not toggle it on

no matter how many times I tried. So went back down to recovery and flashed the Wi-Fi fix. I've used it in the past with r16 and it always works. After flashing, the Wi-Fi will still not work. Whatever you did was a major success with the exception of the Wi-Fi. When you get some time, would you please go back and take a look at this? I'll test whatever you come up and provide feedback. THANKS.

Also, it was so easy using Osmosis' AWESOME file-CWM .img flashing tool. I just made sure I had the r16_deb.img in the root. Once I realized Wi-Fi was hosed on r19, I simply went back into recovery, ran the tool which re-flashed r16, flashed Wi-Fi fix, reboot, and I was back up and running r16 in less than one minute. What a dev community we have here, woot!
[Nexus 7 (2013) Original Android Development] RobbieL811:
Are you running a 4.4.4 ROM?
[Nexus 7 (2013) Original Android Development] v12xke:
Yes. PA's latest 4.4.4 KTU84P (20140625)
[Nexus 7 (2013) Original Android Development] zaclimon:
Nice!! Did you have to modify anything off it? (like some ramdisk stuff)
[Nexus 7 (2013) Original Android Development] tonarm:
My Wifi is gone! Please help. Just bought the pro version and directly autoupdated. No backup available.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] TrenchKato:
Literally 5 post above yours. [emoji20]
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Nice! I'll be flashing L onto my n7 soon. The laptop I'm using now has decided it wants to perform 142 updates and keeps running low on virtual memory if I do anything. Been going about 3 hours now... But when that is sorted I'll be flashing and great work as ever, thanks! Do you fancy trying one for nexus 5? I'm free all evening if you fancy a challenge ;)
[Nexus 7 (2013) Original Android Development] tonarm:
Thanks for the reply. Downloaded the Test Boot Img and put it in the FKU Folder an restored it. Everything fine now. Thanks a lot

Gesendet von meinem GT-I9505 mit Tapatalk
[Nexus 7 (2013) Original Android Development] osm0sis:
I just took the L ramdisk, added in the tweaks from Franco's flo ramdisk (which I also made, so it's pretty easy. :p) and repacked it with the r19 zImage. Easy peasy!

http://v.ht/AIK-

Haha I might if I wasn't moving to a new apartment all weekend. See above though. :)

L is... Taking a lot of getting used to. I'm in the middle of manually restoring a partial data backup I had on my PC of KK4.4.4 (since a stupid USB cable must have ballsed up and skipped one of the 1gb files and I didn't realize..), so I can properly dual boot L with MultiROM again.

L initially couldn't read my sdcard correctly, so thinking I had a working backup saved off-device I wiped and started fresh with L as my primary.. Ugh.. Anyway. :p
[Nexus 7 (2013) Original Android Development] zaclimon:
Yep confirmed I got it working on my custom franco.kernel build. Though I can't get interactive to run, it causes a freeze then reboots the device. Have you got something simillar on your device?
[Nexus 7 (2013) Original Android Development] osm0sis:
Interactive was the default so I assume it was running fine. In the end earlier today I went back to regular stock L though, since it was lagging noticeably less on stock.

I have a feeling there might be some memory management issues for any KK kernels we try to run on L this way since L split lmk out of the kernel and to the ROM side as lmkd, so among other possible problems, there might be two lmks running. ;)

Oh well, fun experiment anyway.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Well good luck moving :) iv never yet tried modifying a boot.img, maybe some day though. I hope your mulitrom environment works out too, on my n5 L has been solid in terms of stability etc but I did get reminded of how aggressive mpdecision likes to be. But yeah really I hope your move works out well, been a long time since we got to talk. If you want to hit me up on hangouts etc Steve.Adams.x10@gmail.com ;)
[Nexus 7 (2013) Original Android Development] zaclimon:
That's a possibility. Oh well then, it's still surprising that we can use KK kernels on L, though we're better to be on stock. :p
[Nexus 7 (2013) Original Android Development] Xaeons:
Anyone using the FKU app with the latest release of Paranoid Android 4.4 Final? I just flashed r19 and installed the new FKU app (paid) but whenever I open it, it just freezes and then android will prompt me that FKU isn't responding.
[Nexus 7 (2013) Original Android Development] morbidj:
osm0sis thanks for putting in work . ? you're more active than than Franco on his thread and kernel build lol. Have you any thoughts on your own kernel?
[Nexus 7 (2013) Original Android Development] osm0sis:
Nah.. I've become pretty good with shell, know my way around a ramdisk and EDIFY, but I'm pretty useless with C. I can mod some C by seeing how it works and following the pattern, but otherwise, yeah, no go. ;)

I enjoy having Android as a hobby but can't really spare time to teach myself C for the express purpose of developing a hobby kernel. :p
[Nexus 7 (2013) Original Android Development] franciscofranco:
Hi guys, sorry for the delay, I've been truly busy with other stuff since coming to the US to help FacesIn (https://play.google.com/store/apps/details?id=com.wizi.facesin) grow and help them get investment soon.

Here's r17. Don't flash if you're not on 4.4.3 or newer.
[Nexus 7 (2013) Original Android Development] Woody:
Quick question Franco. I've, and more than a few others, have been on "Test 19" for a few weeks now. Now you pushed 17. Are they the same or should we revert back 2 versions?
[Nexus 7 (2013) Original Android Development] osm0sis:
If the past is any indication, the revision numbers of test builds are just random choices at compile time on Francisco's part. He's done r666, r999 and even similarly jumped only a few ahead, then still made the final release with the same code and a more incremental revision number.
[Nexus 7 (2013) Original Android Development] justibasa:
Runs fine. It's something you did. Running it on mine great. Been running it since Franco put it out. Going to the new nightly now.
[Nexus 7 (2013) Original Android Development] Xaeons:
You're using a Nexus 7 2013 Flo with Paranoid Android 4.4 Final + Franco Kernel r17 + FKU v11.5? Coz that's the only thing I did. Gonna change to CleanROM or something to check out if the ROM's at fault then..

FKU's been working fine with the previous versions for both kernel and ROM though (FKv19 + PA4.4 RC2) I sent an error report with logs though I don't know if it was sent to franco.
[Nexus 7 (2013) Original Android Development] v12xke:
Deb Love

Thanks for the Deb love... was really starting to feel like the red-headed stepchild here with this excellent LTE device, but now we're getting updates at the same time as Flo. Woot! Deb file can be found in the repository:

http://192.241.177.15/Nexus7_2/4.4/