[KERNEL][AOSP/CM][03/01/17] Quanta - V14

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal

Simple, Powerful, Stable. Here's Quanta for the Nexus 7 2013 (Flo/Deb)


Disclaimer: Your warranty is now void, use at your own risk. Don't blame me for anything because YOU decided to make these changes.

Note: This kernel is made for Android 5.1 (Lollipop) up to Android 7.x (Nougat) For earlier versions, please refer to Sabermod franco.Kernel on post 3.


Features:


- Based upon the official franco.Kernel source
- Compiled with the latest Cortex-A15 optimized UberTC 5.x with some kernel based optimizations + Graphite
- Linux 3.4.109 (3.4.0 from V5 onwards)
- AOSP/CM compatible
- Deb compatible (From V5 onwards)
- F2FS compatible
- DT2W/S2W support
- Wake Gestures Support
- Faux Sound
- Ability to force the touchscreen driver (if there's one you like for some reason)
- XPad support
- Support for android-keyboard-gadget (You can use your device as a keyboard/mouse for your PC)




Installation:

1. Install using CWM/TWRP
2. Profit


Sources:

Kernel Source (quanta-7.x)
Anykernel2 Source (flo-7.x)

 
Last edited:

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
Changelog

Code:
V14: (03/01/17)
- Updated for Android 7.x support (Nougat)
- Merged security updates up to December

V13 (18/09/16)
- Merged security updates for September (Includes CVE-2016-2059 and CVE-2016-5340)

V12 (21/08/16)
- Merged security updates for August
- Patched Quadrooter exploit (CVE-2016-5340)
- Updated F2FS

V11 (16/07/16)
- Merged security updates for July
- Performance improvements (From Franco's release)
- Faster boot up time (From Franco's release)

V10 (11/06/16)
- Merged June security patches (Important)
- Updated F2FS

V9 (23/05/16)
- Reverted CPU-Boost to use mako_hotplug instead
- Interactive should be more power-efficient when the display is off
- Updated F2FS
- Made Software CRC toggable
- Misc security fixes

V8 (09/03/16)
- Reverted faulty commits that was causing the device to do panics
- Updated values for Interactive and cpu_boost
- Updated F2FS
- Misc Fixes/improvements

V7 (16/01/16)
- Rebased from Franco's sources (alonside the ramdisk changes)
- Updated F2FS
- Tweaked the performances profiles for CPU Boost

V6.1 (27/12/15)
- Fixed flashing for Deb devices

V6 (24/12/15)
- Merged 6.0.1 kernel sources

V5 (12/11/15)
- Initial Android 6.0 (Marshmallow) release
- Rebased from Google's 3.4 kernel source
- Added official support for Deb (It was half-baked in Lollipop)
- Compiled using the latest UberTC optimized for Cortex-A15 chipsets

V4(25/09/15)
- Linux 3.4.109
- GPU drivers reverted to a 5.1.1 state (Fixes Chrome scrolling lag)
- Updated the F2FS drivers
- Updated XPad support for Xbox One controllers
- Battery power saving optimizations from Nvidia
- Misc optimizations/fixes

V3(15/05/15)
- Merged 5.1.1 kernel sources.

V2(14/05/15)
- Linux 3.4.107
- Fixes for CM related slowdowns
- Patches from Mako (Filesystem optmizations, optimised LMK from Motorola, etc)

V1(18/04/15)
- Linux 3.4.106
- Support for Wake Gestures
- Support for USB Host Mode Charging
- Tweaked the performances profiles from FKU
- Support for android-keyboard-gadget
- Removed the 192 MHZ CPU freq.
 
Last edited:

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
Quanta Tweaks

All your tweaks are now regrouped into the app I've developped. No more hassle in tweaking 10 files/5 different apps togheter. It also has a franco.Kernel shortcut so your tweaking experience won't be stopped when trying to reach it.

https://play.google.com/store/apps/details?id=com.zaclimon.quantatweaks

It includes various tools and a beautiful user interface to enhance your experience even further!

Forced touchscreen

I've implemented CTCaer's forced touchscreen update in case you have some issues with your touchscreens. More info on his implementation here:

http://forum.xda-developers.com/showthread.php?t=2800308

If you have some suggestions, please request them in the thread or send me a PM. :)


Sabermod franco.Kernel information (For 4.4 up to 5.0, Deprecated)


- Note: r17.2 is a Kitkat (4.4) build, r20 is a Lollipop (5.0) build.
- Compiled with SaberMod GCC 4.9.3 with Ofast optmisations + Graphite + other optimisations
- Linux 3.4.104
- Supports the LTE-enabled Nexus 7 2013 (Deb) (Kitkat builds)
- AOSP/CM compatible
- F2FS compatible
- DT2W/S2W support (Wake gestures support for Kitkat builds)
- Faux Sound
- Ability to force the touchscreen driver (if there's one you like for some reason)


Download:
AOSP: AOSP Download Folder
CM: CM Download Folder


Installation:
1. Install using CWM/TWRP
2. Profit


Sources:
Kernel Source (sm-5.0 and sm-5.0-cm)
Anykernel Source (flo-5.0)


Changelog
Code:
R20:
Rebased off Franco's Lollipop source
Touch control script is now situated in /system/etc/touchcontrols.sh (init.d compatibility reasons)
Compiled using the latest 4.9.3 SM toolchain

R17.2:
Merged the latest patches from the franco flo repository (Interactive stuff mostly)
Merged all the latest patches from Mako (Hotplug, Interactive, misc)
Merged some patches from Hammerhead (Including the Nvidia's power efficiency patches)
Deb Support
Linux 3.4.104
Added support for Wake Gestures, be sure to use the xposed module as well. (Also added their values in the 91touchcontrols init.d script)
Added support for FauxSound alongside with the franco sound patches (Please don't use both at the same time...)
Merged f2fs patches up to 10/10/14 (Shouldn't have any problems with fsck right now)
Compiled with the latest SaberMod toolchain.

R17:
Initial release
 
Last edited:

rebretz000

Senior Member
Jul 11, 2012
1,507
604
0
Magrathea
So far loving the kernel. Thank you for providing it.
I was trying to enable double tab to wake but the setting wouldn't stick using trickster mod. And I can't locate it I'm Franco control

Sent from my Nexus 7 using Tapatalk
 

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
So far loving the kernel. Thank you for providing it.
I was trying to enable double tab to wake but the setting wouldn't stick using trickster mod. And I can't locate it I'm Franco control

Sent from my Nexus 7 using Tapatalk
Well this is why I've provided an init.d script in which you can enable/disable dt2w and s2w and their advanced options. :p

Envoyé de mon Nexus 7 en utilisant Tapatalk
 

habylab

Senior Member
Dec 3, 2010
6,229
1,201
0
Thank you so much for this. Do I just flash and get the updated touchscreen drivers, or do I have to enable them?

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3! Tapatalk'd
 

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
Thank you so much for this. Do I just flash and get the updated touchscreen drivers, or do I have to enable them?

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3! Tapatalk'd
Well you have to find the touchscreen driver you need. Then you need to find its path and write it down into /sys/devices/i2c-3/3-0010/update_fw. It would have been easier make to make some script that would overwrite or maybe the value gets saved up. I would need to check further myself.

Envoyé de mon Nexus 7 en utilisant Tapatalk

Is this kernel from the future? If so, I must try it!! Thank u.
Nope you aren't dreaming, it's from the present and you'll won't regret it! :)
 
Last edited:

habylab

Senior Member
Dec 3, 2010
6,229
1,201
0
Well you have to find the touchscreen driver you need. Then you need to find its path and write it down into /sys/devices/i2c-3/3-0010/update_fw. It would have been easier make to make some script that would overwrite or maybe the value gets saved up. I would need to check further myself.

Envoyé de mon Nexus 7 en utilisant Tapatalk



Nope you aren't dreaming, it's from the present and you'll won't regret it! :)
Ah okay, interesting! I'll have a look at some point.

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3! Tapatalk'd
 

0l1v3rof

Senior Member
Nov 13, 2012
80
21
0
Ursa Minor Beta
@zaclimon

... DtW is random and works 90% of the time, I dont know if you can improve this but of ElementalX is works all the time. I have edited the config file and disabled all the stuff like Dtw in a certain angle (Landscape and portrait etc). I don't know if this will have any effect on the reliability so I have added it in.
 

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
@zaclimon

... DtW is random and works 90% of the time, I dont know if you can improve this but of ElementalX is works all the time. I have edited the config file and disabled all the stuff like Dtw in a certain angle (Landscape and portrait etc). I don't know if this will have any effect on the reliability so I have added it in.
Hmm that's strange, it's been working flawlessly for me. Have you tried to disable the pwrkey_suspend? Maybe it can resolve your problem because the code is the exact same one as of elementalx.


I was talking about the date of the kernel in the op... Just being stupid.:p
Yeah I think this is what he was referring to.

US (and maybe GB) way of writing dates : MM/DD/YY
The rest of the world way of writing dates: DD/MM/YY

Its a bit confusing at first maybe for you guys but it looks more logic that way. (in my perspective anyway)

Envoyé de mon Nexus 7 en utilisant Tapatalk
 
Last edited:

0l1v3rof

Senior Member
Nov 13, 2012
80
21
0
Ursa Minor Beta
Hmm that's strange, it's been working flawlessly for me. Have you tried to disable the pwrkey_suspend? Maybe it can resolve your problem because the code is the exact same one as of elementalx.

Envoyé de mon Nexus 7 en utilisant Tapatalk
Yes I have already disabled pwrkey_suspend... I have been testing a little more and sometimes it needs 4 taps to turn the display on. When it does this it works perfectly for a short while and then the problem arises again.


Yeah I think this is what he was referring to.

US (and maybe GB) way of writing dates : MM/DD/YY
The rest of the world way of writing dates: DD/MM/YY

Its a bit confusing at first maybe for you guys but it looks more logic that way. (in my perspective anyway)
GB uses DD/MM/YY. As far as I know only the US has the month first.
 
Last edited:

zaclimon

Recognized Contributor
Aug 14, 2011
4,365
7,292
0
Montréal
Yes I have already disabled pwrkey_suspend... I have been testing a little more and sometimes it needs 4 taps to turn the display on. When it does this it works perfectly for a short while and then the problem arises again.
Hmm this really is weird. And you said it was working fine with elementalx right? In that case, I'll check something then.

Envoyé de mon Nexus 7 en utilisant Tapatalk
 

0l1v3rof

Senior Member
Nov 13, 2012
80
21
0
Ursa Minor Beta
Hmm this really is weird. And you said it was working fine with elementalx right? In that case, I'll check something then.

Envoyé de mon Nexus 7 en utilisant Tapatalk
ElementalX was working perfectly fine. It's really strange and I can't see any reason why. If you can't do anything about it then that's perfectly fine ( just in case you think I'm nagging you to find a fix)
 

habylab

Senior Member
Dec 3, 2010
6,229
1,201
0
I always thought linaro added to file size, how is this less?! Works well!

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3, end of August an HTC One M8! Tapatalk'd