Database Develop

Linaro franco.Kernel | r193v2 | Prima | 4.3.x | 3.4.67+ GCC 4.8.2 -O3

Linaro franco.Kernel
-O3 Optimized - v3.4.67+ base updated - 4.8.2 Linaro toolchain​
I forked Franco sources and I mantain my sources in sync with his git changes.
Please let me know what do you think about the speed, stutters compared to franco builds.
Code changes in Linaro version from Franco stock:
- -O3 and other compiler optimizations
- Fixed warnings
- Removed many debug options
- Fixes from codeaurora to camera, mdp, video output...
- Add faux sound support, and faux sound fixes, YES YOU CAN USE FAUX APP!
- Enabled kernel wakelock stats
- Latest Linux upstream 3.4.y
- Many Slub, slab, slob allocators optimizations and bugfixes
- Removed some usless flag in defconfig (useless debugs, ntfs support...)
- Tweaks to make it compile with gcc 4.8.2
- Improvements to battery charging, improved detection of fully charged and others fixes.
- Bugfixing to mmc, random, slub, xz compression
- Other small fixes, see my git
- Franco Audio patches not included for now, I prefer Faux solution, let's see in next builds
Code changes in Prima version from Linaro:
- Updated prima drivers (wifi, 3g, bluetooth) to 3.2.3.191+
- The .zip add 2 new files to /system needed for new prima drivers, if you want to switch back to normal version you'll have to dirtyflash your ROM before flashing old/another kernel
------>DOWNLOADS<------​
Source HERE
Credits:
@franciscofranco
@stratosk
@anarkia1976
@faux123
@kecinzer
@ayysir
XDA:DevDB Information
Linaro franco.Kernel, a Kernel for the Google Nexus 4
Contributors
LaboDJ
Kernel Special Features: Franco Kernel compiled with Linaro Toolchain, it includes latest linux patches, and other optimizations.
Version Information
Status: No Longer Updated
Current Stable Version: 193v2
Stable Release Date: 2013-11-02
Current Beta Version: 193v2
Beta Release Date: 2013-11-02
Created 2013-07-29
Last Updated 2013-12-04

FAQ
FAQ:
Franco explained better than I can do.
franciscofranco said:
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
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.
3. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. Touch Control doesn't work in rXXX release, you suckas, fix plixe!
A: I don't know who you are. I don't know what you want. If you are looking for a fix, I can tell you I don't have the solution. But what I do have are a very particular set of skills; skills I have acquired over a very long career. Skills that make me a nightmare for people like you. If you leave now, that'll be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I ignore you.
Click to expand...
Click to collapse
I can add:
5: Can i switch from your kernel to Franco one anytime I want?
A: Yes, you can do it without flash anything.
6: My phone boots normally then the screen goes off and it reboots
A: Known BUG in DMA, don't let the screen goes off until f.ku color are set.
7: I'm on franco Milestone/nighly #xxx how can I flash your kernel?
A: Clear f.ku app data, then flash my kernel.
8: Can I use f.ku (franco.Kernel Updater) with your Kernel?
A: Yes, you can.

Good luck dude.

Thank you
Sent from my Nexus 4 using xda app-developers app

Thank you, I'm definitely going to enjoy testing these out!

Did you have errors while building
Sent from my Nexus 4 using Tapatalk 4 Beta

thebryceee said:
Did you have errors while building
Click to expand...
Click to collapse
No errors, I fixed 2 things on mako_hotplug.c adding __cpuinit in 2 functions.
Some warning... that also appears using google toolchain.

Nice
Sent from my Nexus 4 using Tapatalk 4 Beta

I've been running the linaro builds since 143, thanks for your efforts!
Let's see what this turns into....
Sent from my Nexus 4 using xda app-developers app

Last kernel i used for the evo 3D was O3 optimized for linaro and it was a night and day difference
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks dude.
Sent from my Nexus 4 using xda premium

Francisco said he doesn't have a problem with your Linaro builds in there btw
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks, finally you created thread. Anyway it's good to have separate thread to keep it segregated from the normal build.
Edit : Appreciate if you could also add the md5 somewhere.
Here is for the last build, 89cbfde5561ff8f42f3bdf0501168fc8
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks for the kernel builds. I am excited that you are pursuing this project. I have been using your kernel with a linaro built ROM from Trailblazer11 (CM based). Great combination.
Sent from the singletrack...

is there a possibility to see a 4.8 toolchain kernel in a near future? i try this one and maybe is placebo but is working great for me feels snapy and smooth on some user interfaces this kernel definitely give some boost on the experience not a hardcore one but help make the experience a great one.:victory:

Finally, a different thread.. :victory:
will try this now.. :laugh:

So you won't consider including the latest prima drivers or maybe do a version with and without it? Thanks for this...
Tap, tap says the wicked G()()GLE N4

What does the 03 stand for? And what are the changes compared to non O3 version of your Linaro r146 build?
Sent from my francofied paranoid Nexus 4 with Tapatalk 2

I know that i shouldn't rely on benchmark app. But here's some screenshot using franco's build and Linaro one.
Franco's:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LaboDJ's:
Sent from my Nexus 4

yea you shouldnt rely on benchmarks too much, i just made benchmark with franco kernel and had 13xxx score 2nd try was over 18xxx cause i accidently
turned off screen at 3d benchmark and that caused bad score.
anyways gonna try this kernel with optimations out and see how it works.
btw i also tried out to UV the kernel + overclock it and run benchmark, antutu score is bad, while geekbench 2 scores higher,
benchmark is only a score, you could see wether is a large improvement google stock rom -> custom rom.
But i don't think you can measure the difference between kernel vs optimized kernel.

[ROM][4.4.4][10/21] SlimSaber - n7000

SlimSaber n7000 Uber 4.8
Making SlimKat more faster and smoother​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimSaber: Uber toolchain 4.8.4
SlimKernel: Uber toolchain 4.9.4​
Disclaimer
I'm not responsible for any damages on your device.
After having a good response for some months in the i9100 thread, I decided to share this build since I also built for n7000.
My focus is to optimize the ROM in many areas and compiled it with custom toolchain Uber for more performance and smoothness.
I choose SlimRoms as a base because it is a lightweight and not a bloated ROM, but it still has rich features. Combined with some of CM features, I bake a ROM that has more useful features but still lightweight.
The ROM and the kernel are tested by me first before I make it available online. I could have overseen something during testing, please be understand.
Features summary
See here. Thanks a lot Harsha Raj!
Installation instructions
Coming from 4.1.x or 4.2.x or 4.3.x or another ROM to 4.4.x:
Flash a kitkat compatible recovery from here. A kernel is a recovery and a recovery is a kernel.
Reboot to recovery. Not to the system!
Full wipe: data, cache, dalvik cache.
Mount system and format system partition manually.
Flash the unofficial build.
Flash gapps from here. Please use the 'minimal' one since our system partition is not big enough to carry the 'full' one.
Coming from previous unofficial build:
Wipe cache and dalvik cache.
Flash the unofficial build.
No need to re-flash gapps. Gapps will be restored back automatically by backup tool during flashing.
Known Issues
Music player stops playing music from sdcard after some time. See here - Fixed since 20141221.
Occasional freezes if using governor other than ondemand. Use only ondemand for the time being.
F.A.Q
See second post.
Latest release
Latest 4.4.4: 20151021
Latest 4.4.3: 20140616
Latest 4.4.2: 20140604
Full Changelog
androidfilehost
Download
androidfilehost
Credits
SlimRoms - The SlimRom team
Uber toolchain - Cl3Kener
SlimSaber banner and signatures - kroz
Special Thanks
HardCorePawn - for his great work making the SlimKat available on n7000 device.
Dorimanx - for patches to disable sqlite fsync.
Sources
https://github.com/SlimSaber
How To Build
See this post

F.A.Q (Freaking Annoying Questions)
How to disable CellBroadcastReceiver
There are three possibilities to disable it:
Disable its setting: See here
Remove it: Settings - SlimCenter - SlimSizer - Delete CellBroadcastReceiver
Freeze it: Use Titanium Backup and freeze 'Mobile Broadcast'
Root doesn't work!
Enable 'Developer options'
Go to Settings -> About Phone
Tap on the Build Number 7 times
Go to Settings -> Developer options -> Root access
Choose 'Apps' or 'Apps and ADB'
How to set zzmoove profile
Available zzmoove profiles:
Default
Will set governor defaults
Yank Battery
A very good battery/performance balanced setting - DEV-NOTE: highly recommended! -
Yank Battery Extreme
Like yank battery but focus on battery saving
ZaneZam Battery
A more 'harsh' setting strictly focused on battery saving - DEV-NOTE: might give some lags! -
ZaneZam Battery Plus
NEW! reworked 'faster' battery setting - DEV-NOTE: recommended too! -
ZaneZam Moderate
NEW! setting based on 'ZaneZam Optimized' which has mainly (but not strictly only!) 2 cores online -
ZaneZam Optimized
Balanced setting with no focus in any direction - DEV-NOTE: relict from back in the days, even though some people still like it! -
ZaneZam Performance
All you can get from zzmoove in terms of performance but still has the fast - down scaling/hotplugging behaving
ZaneZam InZane
NEW! based on performance with new insane scaling active. a new experience!
ZaneZam Gaming
NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay
How to set the zzmoove profile:
Go to Settings - Advanced options - Performance - choose zzmoove governor
Press menu key and choose Governor Settings
Search for 'profile_number' and pick a number from above
Press 'Apply values' and eventually enable 'Apply on boot'
Only profile_number can be persisted, any other gov settings will be changed based on the chosen profile template.
* Media scanner eating my battery
* CPU stuck at 1.2 GHz
* Random music player stop
For media scanner problem, try this following solution first: http://forum.xda-developers.com/showthread.php?p=47868557, also see this.
At these problems could have the same root cause: The kitkat sdcard fuse daemon issue on the Exynos 4210 family of devices. There is no fix yet. See this thread for more information.
How to check corrupt partition
See here: http://forum.xda-developers.com/showpost.php?p=50264173&postcount=9137
I have excessive RILJ wakelocks
See here: http://forum.xda-developers.com/showpost.php?p=50227440&postcount=9049
and here: http://forum.xda-developers.com/showpost.php?p=50758124&postcount=9790
My recovery won't flash the 4.4 zip... aka "Status 7 error"... what do I do?
You need a kitkat compatible cwm. See installation instructions in 1st op
How to change DPI?
Currently, this feature hasn't been ported... so you'll need to install Texdroider DPI from the playstore... or edit /system/build.prop and change ro.sf.lcd_density to the desired value
Stuck at the Samsung logo
Follow this steps to get rid of the stuck and to have back your valuable data:
Go to recovery and make a twrp/cwm backup.
Do a full wipe + mount system + format system.
Flash the rom + gapps.
Reboot to rom and skip the setup wizard.
Go to recovery again and advance restore your data only.
Reboot.
My timezone is reset and it is wrong
See this workaround from rkoby13 or eskriminal here: http://forum.xda-developers.com/showpost.php?p=45572515&postcount=2668
What is the difference between these builds and the official builds?
Short version: It is unofficial nightly builds whereas official one is stable and weekly builds.
Long version: It is built using the same source (github) like the official one but with these following additional changes:
Compiled using SaberMod 4.8 & SaberMod 4.7 toolchain combo.
Contains some cherry-pick commits. See changelog for more details.
Faster? Smoother? Here are some responses from users: rkoby13, rkoby13, rkoby13, kroz, MarioFan1998, alkspo, vladimirheroj, bodzik155
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/

Goodies
SlimKernel
These following kernels are only for testing purpose. If you don't know what it is, don't flash these:
SlimKernel_v4.2.22-n7000-signed.zip
KrozMod Collection
A theme collections by kroz, visit his thread here: http://forum.xda-developers.com/showthread.php?t=1960233
Signatures by kroz
SlimSaber
SaberMod SlimRoms
Download here: http://d-h.st/users/kroz/?fld_id=25717#files
Bootanimation by kroz
Download here: http://d-h.st/users/kroz/?fld_id=28876#files
More information about this bootanimation, see here: http://forum.xda-developers.com/showpost.php?p=47920976&postcount=5592
Bootanimation by thereald
Download here: http://forum.xda-developers.com/showthread.php?t=2499512

To follow the i9100 release:
From now on, if you want to use custom kernel, the kernel needs to support new mali r3p2.
SlimSaber-n7000-4.3.1-20131112.zip
Changes:
* Integrated r3p2 mali as default.
* Bunch of changes in framework av.
* Updated Contact, Mms and Phone with some fixes after some months no change at all.
* Some memory leak fixes in framework base.
* See changelog

Welcome to the Note, SlimSaber @fusionjack

Thanks for this SlimSaber.
Downloading:good:

Just tried it. it's quite responsive and snappy so far, since bangsti is left I really missed slim build with these customization and smoothness.
thanks.:good:

just added mirror on dev-host: http://d-h.st/users/fusionjack/?fld_id=28093#files
thanks for the feedback.

Altough I was very, VERY satisfied with my previous ROM, I decided to give a shot to SlimSaber Installed and restoring apps right now but I must say, that the first impression is like...

Vaiet said:
Altough I was very, VERY satisfied with my previous ROM, I decided to give a shot to SlimSaber Installed and restoring apps right now but I must say, that the first impression is like...
Click to expand...
Click to collapse
lol...i like dragon ball too. glad that you like this build.

fusionjack said:
lol...i like dragon ball too. glad that you like this build.
Click to expand...
Click to collapse
Dear sir... There we're times I have flashed a lot. And a lot I mean, that my wife was so angry, that she wanted to throw my phone through window I've seen some things, flashed only good and solid roms... But this one just blows my mind. I tought after crDroid, that there could be nothing better and now I know, how wrong I was Keep up the good work, because SlimSaber is just brilliant and amazing.

Vaiet said:
Dear sir... There we're times I have flashed a lot. And a lot I mean, that my wife was so angry, that she wanted to throw my phone through window I've seen some things, flashed only good and solid roms... But this one just blows my mind. I tought after crDroid, that there could be nothing better and now I know, how wrong I was Keep up the good work, because SlimSaber is just brilliant and amazing.
Click to expand...
Click to collapse
the same like my wife, lol...without i9100 community feedback & supports i'll never reach this state.
thanks for encouraging me to continue this build. :good:
don't forget to give slimbean also a credit too. they implemented some unique features that are used in many custom roms.

Holy crap this is absurdly smooth
Also it's the only 4.3 ROM I've seen that has a proper CRT effect
This is freaking amazing. Thank you sooo much :good:

thx @fusionjack, for new Funny Rom!
let's ride

LAKAME_MAN said:
Holy crap this is absurdly smooth
Also it's the only 4.3 ROM I've seen that has a proper CRT effect
This is freaking amazing. Thank you sooo much :good:
Click to expand...
Click to collapse
bently73 said:
thx @fusionjack, for new Funny Rom!
let's ride
Click to expand...
Click to collapse
your welcome and enjoy the rom.
Sent from my GT-I9100 using Tapatalk

fusionjack said:
your welcome and enjoy the rom.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Oh, I am enjoying it Right now I'm fighting with it to get my desired lockscreen from Candy Shop. Hope it will work (finally)

Thanks for the new slim build.I am long time user of slim bean.The only feature I am missing is HALO.Is there any chance of implementing it in your Rom?

Easy to Instal!
clean instal + rom + AromaSlimgapps + 220 Dpi
and now wait & seeeeeeee battery drain!

zee3241 said:
Thanks for the new slim build.I am long time user of slim bean.The only feature I am missing is HALO.Is there any chance of implementing it in your Rom?
Click to expand...
Click to collapse
unfortunately no.

Is it ok to dirty flash over orignal slimbean 4.3.1 ? Thanks
Edit:
Ok, i did it and it's working fine.
from my Note..

[ROM][YUGA][KK][4.4.4][LINARO/SABERMOD] PARANOID ANDROID 4.x [4.6 BETA 2]

XPERIA Z/YUGA/C6603 PARANOID ANDROID 4.x LINARO/SABERMOD WEEKLY BUILDS
4.6 BETA 2 is ONLINE
DOWNLOAD
(infected server)
(md5sum included with all builds)
CHANGELOG
http://forum.xda-developers.com/showthread.php?p=54620455
kernel code compiled with linaro arm-eabi-4.9.2 201409 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201409 toolchain
FEATURES
-O3 optimizations
strict-aliasing rules
memory optimizations
custom performance flags
+30 cherry-picks used
graphite
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 x64 "Qiana" 3.13.0-24)
Disclaimer:
These builds are freshly compiled/synced from AOSPA Legacy open-source code:
https://github.com/AOSPA-legacy
latest linaro arm-eabi-4.9.x toolchain used to compile the kernel code & sabermod arm-linux-androideabi-4.8.x toolchain to compile ROM code
Special Thanks
AOSPA Legacy Dev Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​

Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942

F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of AOSPA Legacy for the Xperia Z/Yuga/C6603
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.07 (kernel code) & sabermod arm-linux-androideabi 4.8.4 14.07 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
CPU Governors
http://timos.me/tm/wiki/cpugovernors
I/O Schedulers
http://timos.me/tm/wiki/ioscheduler​

Wow!!! Awesome....just awesome
Sent from my Xperia Z using Tapatalk

Is kernel source and blobs same as AOSP?

hi
screenshots ?

BUG:
When phone is idle for 5-10minutes or more (when it goes to deep sleep), touch won't respond, after wake up, I hit power key, but touch either won't respond, or works weird, making phone unusable. Reboot helps, but problem continues.

duki994 said:
BUG:
When phone is idle for 5-10minutes or more (when it goes to deep sleep), touch won't respond, after wake up, I hit power key, but touch either won't respond, or works weird, making phone unusable. Reboot helps, but problem continues.
Click to expand...
Click to collapse
Uncheck double tap to wake up option.For every reboot you should uncheck it.

Vasishta Reddy said:
Uncheck double tap to wake up option.For every reboot you should uncheck it.
Click to expand...
Click to collapse
can you please elaborate how to disable the double tap to wake? because I cannot find one... thank you
AH OK I got it.. Settings/Display/ thank you

duki994 said:
Is kernel source and blobs same as AOSP?
Click to expand...
Click to collapse
Same has AOSPA.
agha_jo0n said:
hi
screenshots ?
Click to expand...
Click to collapse
Im sure if you google a bit, you'll find tons of screenshots of paranoid android 4.4 ..
duki994 said:
BUG:
When phone is idle for 5-10minutes or more (when it goes to deep sleep), touch won't respond, after wake up, I hit power key, but touch either won't respond, or works weird, making phone unusable. Reboot helps, but problem continues.
Click to expand...
Click to collapse
Don't have that issue, and been using RC1 20140612 until today, without issues. Tried a clean install?
Regards.
Sent from my LG-V500 using Tapatalk

How to disable automatic status bar and nav bar hiding feature??

stanlin salu said:
How to disable automatic status bar and nav bar hiding feature??
Click to expand...
Click to collapse
Click on Immersive off on your systemUI quick settings toggles .
Don't have that issue, and been using RC1 20140612 until today, without issues. Tried a clean install?
Regards.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Its an double tap 2 wakeup bug which is present on all the custom 4.4.2 &4.4.3 cm based roms.

Amazing rom!! :good: would it be possible to include gamma control?? :fingers-crossed:

doomhammer07 said:
Amazing rom!! :good: would it be possible to include gamma control?? :fingers-crossed:
Click to expand...
Click to collapse
no, sorry.. that would messing with kernel code. stock kernel FTW

@infected_ thanks for this amazing ROM, hoping for future updates
Sent from my Xperia Z using Tapatalk

Vasishta Reddy said:
Click on Immersive off on your systemUI quick settings toggles .
Its an double tap 2 wakeup bug which is present on all the custom 4.4.2 &4.4.3 cm based roms.
Click to expand...
Click to collapse
well.. haven’t seen those tiles in a while now.. maybe you should upgrade?
dt2w is working properly on PA Legacy (devices i tested, yuga and v500, don’t know about the others), even when the lockscreen is on landscape.
ps: RC2 is coming ... Already see the jobs queue on Jenkins.

linaro/sabermod AOSPAL 4.4 RC2 is online.
regards.

RC2 doesn't boot for me. Anyone else got it to boot?
sent via XPERIA™ Z

I am on a limited bandwidth, I really want to try this latest build, can anyone confirm that new build is booting or not???
Sent from my Xperia Z using Tapatalk

stanlin salu said:
I am on a limited bandwidth, I really want to try this latest build, can anyone confirm that new build is booting or not???
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
i confirm its not booting... already removed it from FTP.
i am compiling a fixed build already.

[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12

Reserved

Reserved

Last one.

Great job! Amazing to see a dedicated thread for this beauty.

Will report the experience

V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .

will test on omni,thanks

Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!

coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.

Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!

beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).

Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.

JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.

JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app

skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.

Awesome
Sent from my GT-I9300 using Tapatalk

JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this

JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?

Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka

Recompiled & Optimized Werewolf Kernel [SM-T211]

Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
laufersteppenwolf said:
Hey guys
As you already might have read in either the CM11 dev thread or the Q&A section, I am working on a custom kernel for our T210(R) and T211. It's still in a pretty early stage, but the current build is fully stable, so I thought why not share it
As I'm pretty new to this community, a few words about myself: My (only) device I have been working on is the LG Optimus 4x HD, for which I also made a custom kernel (also named werewolf kernel, who would have thought of that ). Me and 2 other fellow RDs were able to "switch" many blobs with the ones from grouper, which fixed many, many issues we were facing in 4.4 with the stock 4.1 blobs. I am the official maintainer of namelessROM and vanir for the 4x HD, and am also compiling GummyROM, LegoROM, unofficial CM 11 (using grouper blobs) and SlimKat for the 4x HD on a nightly base. And as soon as we have a proper device tree for our tab, I'm sure I can port the Tab3 to all those ROMs
Now, enough chit chatting, let's talk about the kernel
It's based on @ketut.kumajaya's blackhawk kernel (thanks again, mate ) From v004 on we are based on official KitKat sources, with some additions such as:
Features:
Various network tweaks
Entropy tweaks
I/O speed improvements
cortex a9 and neon omtimizations
Added frandom
Tweaked vm dirty ratios
Dynamic read-ahead values
Added I/O schedulers: ROW, SIO, BFQ, FIOPS, V(R)
Optimized AES and SHA1 routines
Added CPU governors: Lionheart, Adaptive, Intellidemand, Hotplug, Hyper
Reduced RAM usage from logger
Updated lowmemkiller
Overclocked to 1.420 GHz by default
Disabled vsync for better 2D performance
Overclocked GPU up to 624MHz (default 416MHz)
Custom user voltage control (CPU)
Undervolted by default (-25mV)
S2W and DT2W (WIP)
Fast Charging
KSM
Bugs:
You tell me!
Installation:
Download the kernel from HERE
Reboot into recovery (recommended to make a nandroid)
Flash the kernel zip
Recommended to wipe /cache
Reboot and enjoy!
And remember to remove phservice if you want to change some CPU/GPU settings yourself
Notes:
See 2nd post
GPL:
Kernel sources
Kernel Modules (only for v001 - v003)
Used defconfig
Used build script
Thanks:
@ketut.kumajaya for the initial kernel base
@gr8nole for general help, info and testing
XDA:DevDB Information
Werewolf kernel SM-T210/T211, Kernel for the Samsung Galaxy Tab 3
Contributors
laufersteppenwolf
Kernel Special Features: Tuned for best possible performance
Version Information
Status: Stable
Created 2014-07-21
Last Updated 2015-05-25
Click to expand...
Click to collapse
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23

Reserved
Tweaking Guide
laufersteppenwolf said:
Since v002, we have an updated lowmemorykiller. It behaves a bit snappier than the old one, also with the default minfree values. However, in case you like to tweak your device a bit to make it even more snappy (like me ), I tweaked the minfree values a bit to slightly increase the free RAM without really affecting the multitasking experience. The script can be found in the attachment. All you need to do is to extract the script and place it in your /system/etc/init.d/ folder and that's it. The values will be automatically set on boot.
UV interface
The min possible voltage is 1000mV for now, and the max one is 1400mV. If you want me to lower the min voltage, please let me know.
Also, please note, that the voltage has to be changed in 12.5mV steps. If you apply for example 1110mV, it will be rounded down to 1100mV.
Fast Charge interface
The main interface is inside /sys/kernel/fast_charge/*
/sys/kernel/fast_charge/force_fast_charge (rw)
0 - disabled (default)
1 - use custom mA configured through the sysfs interface (see below)
/sys/kernel/fast_charge/ac_charge_level (rw)
rate at which to charge when on AC (1.8A to 2.3A)
/sys/kernel/fast_charge/usb_charge_level (rw)
rate at which to charge when on USB (0.5A to 1.0A)
/sys/kernel/fast_charge/failsafe (rw)
0 - disabled - allow anything up to 2.3A to be used as AC / USB custom current (USE WITH CAUTION!)
1 - enabled - behaviour as described above (default)
/sys/kernel/fast_charge/version (ro)
display fast charge version information
New kmsg layout
From v008 onwards the kmsg looks a tiny bit different. Instead of displaying the time since boot, it logs the actual time and date.
Now, you may ask yourself: "does that any good?" Sure it does. When you encounter an issue and grab a log, you can send it my way saying "the issue happened at 15:35". It is way harder to find out the exact time (in seconds) since the device booted, right?
Click to expand...
Click to collapse

mat1371 said:
Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23
Click to expand...
Click to collapse
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks

sscsps said:
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks
Click to expand...
Click to collapse
It's on github but I didn't link to it cause it's messy. BTW There is no source code change aside from makefile and defconfig.

BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?

sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Use https:// in download link.

adukale said:
Use https:// in download link.
Click to expand...
Click to collapse
Well, I've got it already, and https didn't quite help, her to use a VPN,
I'm suggesting the OP to upload somewhere else as well.

Thx alot, now it's time to download kitkat rom.
Keep it up sir ?

sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Sorry for late reply, I'm busy with my thesis these days. I've attached the file to the post. Will send you a link to the source (GitHub) in your PV.

Great! Finally something new for T211/0. Love to see some movement here.

Tried installing on a T210 with TRWP but get an error message. Anyone any ideas?
Tried to attach the error but it won't let me... Error talks about asset failed getprop ro.product.device == lt023g etc

@Samw13
SM-T210 = lt02 wifi Tab
SM- T211 = lt02_3g Tab

So, i have deleted requirement in update-script file and kernel seems to work correctly on t210.
Here's link to edited kernel: https://www.upload.ee/files/10238882/kernel-SM-T210-werewolf-Ofast-UV.zip.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Is it fully stable on SM-T211??. Is it the final version??

Hi,
@mat1371,
@lol28
Thank you for the kernel for T210R. Stable, overclocked to 1.42Ghz. I have an issue with the settings I make, they don't stick after reboot. I used kernel adiutor, EX kernel manager, Performance tweaker. I have busybox installed.
I've flashed Powerdaemon.disable.zip from Gr8nole, still the same.
Edit:
I've found Gr8nole's suggestion about deleting /system/bin/phservice. I deleted the file, rebooted, changed to governor to lionheart. It seemed to keep the settings.
Thanks!