Presenting Oxydo kernel for the Nexus 7 Grouper and Tilapia
This kernel is based on _motley's source. The only things I have done so far is:
Merged changes required for 4.3. Compatible now.
Built with an older Linaro toolchain.
Added 600MHz GPU OC (default). It can be changed in TricksterMOD. Please do so.
Updated lowmemorykiller to that of 3.4 kernel. Use oom_score_adj.
Enabled ROW I/O scheduler as default.
Replaced the default hotplug driver with Franco's initial hotplug driver ported from Mako.
LP CORE OC to 660MHz. This as poondog has pointed out is pointless (pun intended) because of the above change.
Updated to Linux 3.2.49.
Taken some memory from logger in hopes of increasing RAM. Failed.
Logger built as module. Increases RAM and removes useless debugging for some. Read post #3 for info. (not in v3+)
Sysfs interface for min/max backlight and brightness control. Read post #3. EXP!
JRCU from Joe Korty
ZEN I/O scheduler
ppp_async.ko and hso.ko modules (not in v3-4)
Included Gaming governor (modified Conservative governor).
Proper OC and OV/UV support. Upto 1.6GHz.
DVFS inspired by HTC One X's freq table.
SLUB memory allocator.
Experimental sweep2wake and doubletap2wake ported over from ElementalX kernel for N7 2013.
Adhoc IBSS mode support. Untested. Can someone try this?
Slightly redundant now. Will update thread later. Features are in changelog.
Flash in recovery. You know how to.
3. Warning and disclaimer
The usual. I am not responsible for any harm caused to your tablet by this kernel. You decide whether you want to flash this or not and therefore you face the consequences. But don't worry. This has been tested and the results were pretty good.
1. How do I enable logger? What about hso and ppp_async?
Ans: For builds with modules:
Download the modules zip. Unzip them to you sdcard, and note the path. Fire up the Terminal. Issue these commands one by one:
insmod /path/to/logger.ko (only in V2)
To check whether they are working (they are, don't worry):
Should output something like
logger.ko 54334 [permanent] ... blah.
You can also try:
dmesg | grep "logger"
dmesg | grep "hso"
ppp_async doesn't show any message.
To disable hso.ko and ppp_async.ko (you can't disable logger.ko once it's insmod'ed, but a simple reboot will rmmod it):
For buyilds without modules:
To enable logger (it is off by default), issue this command in Terminal Emulator
echo "1" > sys/kernel/logger_mode/logger_mode
To disable it, just echo 0 instead.
2. Why won't my device reach 51MHz even though it's listed in the frequency list?
Ans: I have set the min rate for G cores to 102MHz. 51MHz IMO is a very stupid frequency in that it will do nothing basically. Even my 3 year old cellphone doesn't stay at 51MHz. It should be a LP core frequency (it actually was) but since Franco's hotplug driver doesn't call on the LP core, it's not reachable.
3. How do I control minimum - maximum backlight through sysfs?
Let me begin by saying that this feature is highly experimental. I can tell though that it works.
Okay so in /sys/module/board_grouper_panel/parameters you'll see two files:
min_bl - Write in a reasonable value preferably at least 30 less than max_bl. Default is 10. Not safe. Switch to 11.
max_bl - Write in a reasonable value preferably at least 30 more than min_bl.
This is what happens. *takes deep breath*
When your brightness is greater than zero but less than the min_bl, it gets changed to the min_bl. And when it's greater than max_bl, it's changed to max_bl. Otherwise it's just normal brightness levels (where's the fun in that, right? )
PLEASE DON'T WRITE THE VALUES OF min_bl OR max_bl WHILE YOU'RE HIGH, DRUNK OR JUST DOWNRIGHT BAT-CRAP CRAZY!
There's no limit to the madness that may happen as a result.
6. How do I configure sweep2wake and doubleetap2wake? What exactly are they?
Sweep2wake and doubletap2wake are basically two versions of the same thing - they wake your device up after you have put it to sleep (not metaphorically) without using the physical buttons on the side. This is still slightly buggy. If at first it doesn't work. Touch the screen once and then tap it twice.
For sweep2wake/sleep you bascially swipe along the bezels (not on the bezels though) where the soft keys would be.
For doubletap2wake, just tap twice on the screen during sleep, and it should wake up.
To configure sweep2wake go to /sys/android_touch and open up sweep2wake
0 = disbaled
1 = sweep2wake/sleep
2 = sweep2sleep
To configure doubletap2wake go to /sys/android_touch and open up doubletap2wake
0 = disabled
1 = enabled
To confgure shortsweep go to /sys/android_touch and open up shortsweep
0 = disabled.
1 = enabled.
This drains battery a little faster than stock would, so yeah. Don't use it (i.e. disable it) if you want to save battery, or set up a script.
There is also a wake_timeout file. It holds the time that the dt2w wakelock will remain active after the screen is suspended. NOTE: s2w wakelock times aren't configurable and it will stay on for 15 seconds after the screen has been suspended.
Insert the time in seconds. (60 = 1 minute; 3600 = 1 hour)
5. How do I configure the touch area for s2s in portrait mode (for now; extensive controls coming soon)?
Go to /sys/module/ektf3k/parameters. Write a value in the xvrl_val file and experiment.
Best done in Terminal.
NOTE: 0 starts from the top bezel (where the front-facing camera is) and the limit configurable is only along the right bezel (the Y-axis values only).
Hard to explain, I'll have a video up soon and a data table for calculations.
5. Why is my device so awesome now?
OH STAHP IT YOU!
Oh and this works awesome with the IceColdJelly AOKP ROM for Tilapia. Be sure to try it out.
Works fab on 4.3 stock. Don't believe in benchmarks though.
R.I.P. Miranda Nicole
An innocent soul, who deserved to live a lot longer. We all miss you.
R.I.P Alif Shahriar
A true friend, no longer here in this world, but always there in our hearts. We sorely miss you.
Xperia X8 ROM: MiniCM7 2.1.9 Kernel: oxydo@zcf-04
Nexus 7 ROM: The second latest AOSPAL (luvz) Kernel: Oxydo - The latest one. Ones people themselves don't get.
There was much hype around the unveiling of Ubuntu Touch, Canonical’s take on a … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?