{
"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"
}
WARNING :
This kernel is only for Galaxy S3 International (GT-I9300) version,
and running Android 4.3 (Samsung ROM's) !
Click below to read the full story..
Many of you knows already knows me from my older LiteGX kernel series (for Android 4.1.2 & 4.3).
This time for SimpleGX, I would like to be closer of stock than LiteGX by removing a lot of unneeded things which finally were not gaining any battery stat at all. I had to review everything from zero (once again !).
SimpleGX is only looking for simplicity and stability, trying to aim for best battery life, smoothness and performance experience, than a pure stock kernel.
SimpleGX will now abandon all scripts that I created for LiteGX (even if some of them are still compatible but not recommended).
I really would like to create back a kernel which was my main idea, a kernel “flash-and-play”, nothing to configure, no need to be a nerd, every newbies can have directly best battery life and smoothness once flashed. Of course that’s every kernel cookers wants, but I would not qualify mine as a real “custom kernel”, since it’s not offering any app to configure it and having much more opportunities, at the cost of many random instabilities (freezes, lags, reboots, etc).
There is many differences between LiteGX and SimpleGX, you will have to compare threads if you want to know them.
I really would like once again to give a huge thanks to my friendly devs (post #3) who helped me a lot during all kernel building phase, learning me, and making adventure possible. I can tell also that Google is really a good friend, I confirm that ^^
I still don’t qualify myself as of a real developer, but just a basic person with some android/linux knowledge already.
As always, I’am enjoying sharing my contribution here on XDA for free, which taking me a lot of time to release, so if you can offer me a little beer (as I’am still jobless yet), I will really appreciate that and you will be added into post #4 ! LiteGX had more than 10000 total downloads, I let you imagine if everybody gave me at least a single dollar ! ^_^
This kernel must be only flashed over an official Samsung ROM and not AOSP/AOKP !
Feel free to include my kernel to your ROMs / Threads but please don't forget to inform/ask first via PM and credit me in your original thread.
★ WHAT TO EXPECT ★ :
(over a pure stock kernel) :
Best battery life experience.
Much better overall performance.
Efficient (only proven to be good ones and not affecting battery life) tweaks.
Stay as close as possible from stock source.
★ FEATURES (up-to-date) ★ :
Base :
Directly based on "GT-I9300_JB_Opensource_Update14" (XXUGND5) JellyBean Android 4.3 source from Samsung (for clean work and stability).
Compiled with Linaro Cross Compiler (4.7.4 / 2014.06) toolchain (optimized for Cortex-A9) with optimization flags.
Ramdisk from XXUGNJ2.
Main :
ZZMoove (v1.0 beta4) governor added (and currently as default). Built-in profiles available HERE.
ZEN as only I/O scheduler.
Wolfson Boeffla Sound (v1.6.6 drivers) compatibility.
hardcore mDNIe tweaks (for better colors + sharpness fix for better readability).
Touch-to-Wake (v1.1a) (enabled by default with 5 secs).
USB charging increased to 900mA.
Allow manual brightness to 300 candela.
init.d support.
Native frandom support.
Native ExFAT (v1.2.9) support.
Native xbox controller support.
CRT-off effect friendly (early_suspend set to 100ms).
Westwood TCP congestion control module activated (and currently as default).
TriangleAway support.
Various tweaks :
All logging and debugging disabled.
Tweaked LMK (LowMemoryKiller).
speedup late resume tweak (faster wakeup of the device).
"GENTLE_FAIR_SLEEPERS" disabled.
"ARCH_POWER" enabled.
"CONFIG_SCHED_AUTOGROUP" enabled.
CRC disabled.
USB OTG enabled.
Doubled min-max ReadAhead.
random: increase entropy levels (both read and write).
writeback: fix occasional slow sync.
slub.c: little tweak for performance improvements.
Misc :
Fully compressed libs ".ko" modules.
Automatic dalvik-cache wiping in kernel flashing procedure.
Automatic verification of android version during flashing procedure.
Features that will NEVER be included in this kernel :
Overclock / Underclock / Undervolt.
ZRAM/SWAP support.
auto-root.
LED control.
Charge control.
Master sequence (screen calibrated).
ABB (Adaptive Body Bias).
Any upgrade of Linux kernel 3.0.XX.
STweaks compatibility.
Dual-Boot Sammy/AOSP.
CyanogenMod compatibility.
MIUI compatibility.
etc.
★ PREREQUISITE ★ :
Any odexed or deodexed international I9300 Samsung 4.3 Jelly Bean ROM.
A custom recovery (CWM recommanded) to flash the kernel.
Be sure to remove any of your init.d scripts which can meet conflicts with the kernel.
★ SOURCE (up-to-date) ★ :
Github >> SimpleGX.
~> DOWNLOAD LINK <~
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!
Changelog
★ All ZZMoove profiles can be found HERE ★
★ CHANGELOG ★ :
29.11.2014 : v3.5.1 released.
Updated ZZMoove governor to 1.0 beta4.
Upgrade full ramdisk from XXUGNJ2.
23.11.2014 : v3.5.0 released.
Stock ZRAM activated back with stock values (excepted 80% swappiness, instead of 60 by default), (no more launcher force close within my whole day experience).
I decided to bring back some interesting performance tweaks from my old LiteGX kernel (which are safe, absolutely close to stock and finally sufficient proved):
- writeback: fix occasional slow sync.
- slub.c: little tweak for performance improvements.
- random: increase entropy levels (both read and write).
Overall kernel experience is now more smooth and reactive.
I also changed all download links from the thread to point to my new personnal ftp (so you will now have to click "download link" from post #1). Downloads will now be faster than ever (no more need of dropbox, etc).
09.11.2014 : v3.4.3 released.
Updated ZZMoove governor to 1.0 beta2
31.10.2014 : v3.4.2 released.
LMK (LowMemoryKiller) tweaks (add +10MB everywhere on 'minfree' file). This should fix stock samsung low memory related problems.
19.10.2014 : v3.4.1 released.
Update ExFAT to version 1.2.9.
Upgrade full ramdisk from XXUGNH4.
15.10.2014 : v3.4.0 released.
Updated ZZMoove governor to 1.0 beta1 (credits @ZaneZam).
Added some patches which was necessary for new ZZMoove 1.0 version:
- simplegx_defconfig: Enable support for CPU temperature reading.
- nohz: Fix update_ts_time_stat idle accounting.
- mach-exynos: Support for current CPU temperature reading from Exynos4 TMU driver.
08.10.2014 : v3.3.2 released.
Finally achieved frandom support fully working and operational (thanks again to @Lord Boeffla for his help).
ramdisk: busybox replaced by the one from Boeffla kernel.
ramdisk: removed useless custom "busyboxlitegx" (+ will save some kernel size).
06.10.2014 : v3.3.1 released.
frandom module now fully and correctly loaded this time (it wasn't the case until now). Thanks to @Lord Boeffla for his precious help.
Some internal ramdisk init changes (modules are now loaded directly from my custom ramdisk script and no more from init.rc).
04.10.2014 : v3.3.0 released.
Updated cross compiler toolchain to 2014.06.
09.09.2014 : v3.2.2 released.
Introduce ZEN I/O scheduler and set as default (and only) scheduler (from my first tests, seems to overall perform slightly better than ROW).
ROW I/O scheduler completely removed.
07.09.2014 : v3.2.1 released.
"CONFIG_SCHED_AUTOGROUP" enabled (will bring multitasking possibilities).
04.09.2014 : v3.2.0 released.
Upgrade full ramdisk from XXUGNG3.
Click below to see older changelog ..
31.08.2014 : v3.1.2 released.
All debug disabled (again) from defconfig side (at the exception of USB).
Due to this above, slightly lowered overall kernel size (again also).
30.08.2014 : v3.1.1 released.
Fixed GPS (which was broken since v3.0.0).
speedup late resume tweak (faster wakeup of the device), added again.
Set back pure stock Update14 defconfig with kernel needs only.
17.08.2014 : v3.1.0 released.
Update ZZMoove governor to 0.9 (beta4).
Fixed ExFAT support.
Update ExFAT to version 1.2.7 (Samsung OSRC from KK sources).
15.08.2014 : v3.0.0 released.
Now directly based from new latest official Samsung source "GT-I9300_JB_Opensource_Update14" (XXUGND5).
speedup late resume tweak removed (from my first tests, it looks useless since new source).
Bunch of debugging part from new defconfig source disabled.
Overall kernel size has been slightly lowered.
15.07.2014 : v2.0.1 released.
Update ZZMoove governor to 0.9 (beta3).
24.06.2014 : v2.0.0 released.
Finally fixed high "Android OS" usage at top of battery stats.
speedup late resume (faster wakeup of the device) (credits Yank555 & AndiP).
Many new (and new way) toolchain optimizations (credits JustArchi).
Compiled with highest possible optimization level (-Ofast).
ALL logging and debugging disabled (credits Yank555, AndiP & JustArchi) :
- android logger.
- kernel logger.
- code side.
- defconfig side.
- init side.
All ".ko" modules now compressed with Linaro Cross Compiler 4.7.4 toolchain from Christopher83 (instead of stock google arm-eabi 4.4.3).
Now extracting/repacking kernel using ArchiKitchen (with latest mkbootimg tool) instead of obsolete dsixda kitchen.
Fixed a little mistake from my simplegx init script within ramdisk which was simply not working until now !
Both smoothest and best battery friendly release ever !
20.06.2014 : v1.9.2 released.
Update ExFAT to version 1.2.7.
16.06.2014 : v1.9.1 released.
Update ZZMoove governor to 0.9 (beta2).
Compilation toolchain optimization.
08.06.2014 : v1.9.0 released.
Update ZZMoove governor (and profiles) to 0.9 (beta1).
Removes Wheatley governor (useless at it was coded initially for dual cores anyway).
29.05.2014 : v1.8.0 released.
Upgrade full ramdisk from XXUGND5.
Some init ramdisk renaming (LiteGX > SimpleGX) that I forgot to do since.
09.05.2014 : v1.7.0 released.
Upgrade full ramdisk from XXUGND2.
30.04.2014 : v1.6.0 released.
Some compilation toolchain optimizations (smoothest release ever).
25.04.2014 : v1.5.0 released.
Upgrade full ramdisk from XXUGND1.
Add 'Wheatley' CPU governor.
(I tested it for few hours now and it looks I'am getting the best battery life experience with it over ZZMoove. Let me know what do you think of it).
20.04.2014 : v1.4.1 released.
Removed pegasusqplus and smartassv2 governors (useless and anyway I prefer to let only ZZMoove).
Removed some kernel code cleanup about pegasusqplus which was needed to get compiled.
19.04.2014 : v1.4.0 released.
Updated cross compiler toolchain to 2014.04.
frandom support is now fully working (kernel should be smooth as butter now).
31.03.2014 : v1.3.1 released.
Update ZZMoove built-in profiles to match latest corrections from Yank.
All ZZMoove built-in profiles (of 0.8) are available HERE.
21.03.2014 : v1.3.0 released.
ramdisk upgraded to XXUGNB6.
Boeffla Sound Engine updated to v1.6.6 (Allow full range volumes for speaker and headphone amplifiers).
ZZMoove 0.8 governor: add latest bug fixes from ZaneZam.
21.03.2014 : v1.2.0 released.
Update ZZMoove governor to 0.8
Change default governor from pegasusqplus to ZZMoove.
17.03.2014 : v1.1.0 released.
New more "stylish" UI when flashing the kernel.
Revert: "unstable power charging ignored" (charging was really faster but battery was draining much faster also, so back to stock).
Add native xbox controller support.
09.03.2014 : v1.0.0-noIUPC released.
Same version as initial, but with ignore unstable power charging removed, so USB tethering should work again (at the cost of a slow battery charging back).
FYI : the "no_IUPC" version means : no Ignore Unstable Power Charging.
08.03.2014 : v1.0.0 released.
Initial release (check actual features on post #1).
Thanks & greetings
★ THANKS & GREETINGS ★ :
XDA board and community
Google
Samsung
CyanogenMod Team
gokhanmoral
Andreilux
wanam
spica1234
ZaneZam
Yank555
DerTeufel1980
googy_anas
hardcore
Lord Boeffla (AndiP)
Christopher83
dsixda
JustArchi
Donations
★ DONATIONS ★ :
Many thanks to @fuxmen ! :good:
Many thanks to @colingpt ! :good:
Many thanks to @letmarebrmbarove ! :good:
Many thanks to @batahulu ! :good:
Many thanks to @sqlpro ! :good:
Thank you to support my work !
Another one from the master. can't wait to test. CHEERS Bro, all the best with your New Kernel.
Nice one - I'll be giving this a go :good:
tnx a lot
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Sent from my Nexus 7 using Tapatalk
sqlpro said:
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Should be OK - it's fine on NA7 Neat.
Nandroid first just in case
Sent from my GT-I9300...
Spannaa said:
Should be OK - it's fine on NA7 Neat.
Nandroid first just in case
Sent from my GT-I9300...
Click to expand...
Click to collapse
I know it will be fine on na7 but I am using na5 base so was not sure. Thank for the reply.
Sent from my GT-I9300 using Tapatalk
i will try this one out
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
reywal said:
i will try this one out
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
Click to expand...
Click to collapse
It's a plug and play, but if you want, you can try trickster for setting stuff like zram on or off, but nothing much to do though.
Your Kernel really rocks. I have been always using your Kernel for close to stock. I am still using LiteGX.
I have tried several one but was looking for one which is hassle free. Your is the one.
This one I will not use now due to USB tethering broken, will wait for next version with that fix.
sqlpro said:
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Click to expand...
Click to collapse
As long as you flash it on android 4.3 and that the automatical script during procedure won't stop you before checking, then you are good to go
When samsung release his (for example 4.3) source, you can be sure that it will be compatible with every 4.3 future coming firmwares :good:
Sometimes a ramdisk upgrade can also help in some case, so if needed I will do it, no worries
reywal said:
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
Click to expand...
Click to collapse
As stated in the story part of post #1, and as Mosh Edd said, this is a flash and play kernel :good: but you can still configure governor settings or some options directly via TricksterMod/SetCPU, etc (don't forget to keep settings after rebooting).
Mosh Edd said:
like zram on or off
Click to expand...
Click to collapse
I intentionally disabled stock ZRAM which was on by default via defconfig so no way to activate it manually :angel:
I decided to always disabled it now on SImpleGX, since zram is eating battery a bit and after some ours of use you will face some random lags.
KSKHH said:
This one I will not use now due to USB tethering broken, will wait for next version with that fix.
Click to expand...
Click to collapse
I informed Lord Boeffla about this bug which affects every kernels, he will take a look as soon as he can :good:
By waiting, I will maybe release a "no_IUPC" (no Ignore Unstable Power Charging) version in parallel for each releases, so each one will choose directly if they prefer fast charging or slow charging but with USB tethering working. I intentionally used IUPC as default because wifi it still working to share (for the few I'am using it..) and that I prefer to not wait hours to charge only 10% of my device
AndroidGX said:
As long as you flash it on android 4.3 and that the automatical script during procedure won't stop you before checking, then you are good to go
When samsung release his (for example 4.3) source, you can be sure that it will be compatible with every 4.3 future coming firmwares :good:
Sometimes a ramdisk upgrade can also help in some case, so if needed I will do it, no worries
Click to expand...
Click to collapse
Thanks for the reply mate. I just installed and all seem to be fine so far. will test couple of more days and update here.
BTW do we need to clean init.d folder ? i know boeffla andi frequently recommends cleaning up init.d folder. is this necessary with your kernel. Note, i dont have any issues so far (only used few mins though).
Thanks for the advise.
sqlpro said:
BTW do we need to clean init.d folder ? i know boeffla andi frequently recommends cleaning up init.d folder. is this necessary with your kernel. Note, i dont have any issues so far (only used few mins though).
Thanks for the advise.
Click to expand...
Click to collapse
He is right because some init.d scripts can affects stock settings from governors for example or try to enable/disable things that is not from my kernel, etc :good:
For exemple, I'am using NeatROM 6.5 and I can see that there is a lot of scripts in init.d already by default bur they don't affect any of kernel part so it's ok
There's no other solution that checking manually each of them, sadly.
Hi,
Thanks for the new kernel!
I come from the latest LiteGX kernel, so I run the cleaner script before flashing this one. My phone hangs when I reboot. I restarted my phone to get it to boot, but then I now have SwiftKey not loading. What could be the problem?
I reverted back you LiteGX for now.
Sent from my GT-I9300 using Tapatalk
I flashed kernel last night and waited until phone settled. Checked if all works fine, and it does, and then put the phone in flight mode.
This morning I checked battery stats and it looks like battery was charging a bit while in flight mode (phone was not connected to any power source).
Funny
All is super smooth. Thank you :thumbup:
Sent from my GT-I9300 using xda app-developers app
rodlane said:
I come from the latest LiteGX kernel, so I run the cleaner script before flashing this one. My phone hangs when I reboot. I restarted my phone to get it to boot, but then I now have SwiftKey not loading. What could be the problem?
Click to expand...
Click to collapse
Strange, as I'am using SwiftKey also and no problem here. If phone hangs at boot this it not normal, did you tried to re-download the kernel from first post ? (maybe a bad download).
If problem still here, maybe try to Try to wipe cache + dalvik from your recovery :good:
pexon said:
This morning I checked battery stats and it looks like battery was charging a bit while in flight mode (phone was not connected to any power source).
Funny
Click to expand...
Click to collapse
I confirm this is funny :laugh:
By waiting, I advice you also to try a wipe cache and dalvik before reaching another 100% and disconnect again to verify :good:
I will try this night aswell to confirm or not if I have the same bug
3.0.31? Why no update to 3.0.101?
Enviado desde mi GT-I9300 mediante Tapatalk
Related
[STOCK KERNEL][NOV20] guestekrnL v2.2.1 | stable, smooth [VIBRO- &RAMHACK] [AROMA]
guestekrnL kernel v2.2.1 + GuesteOC v2.3 (TrymHansen) -- with Aroma
- If you like my work, you could press thx, vote positively for this thread or buy me a beer.
If you want to test you device's stability: Try TrymHansen's Myrt Torture Tester! - this tool is awesome : http://forum.xda-developers.com/showthread.php?t=1645938 -- read the instructions first!
Donators from XDA:
Daniele S.
flat__line
Thank you !! :good:
Basic kernel description:
this is a Gingerbread LG O2X Stock kernel! not for use with Cyanogenmod
focus on stability, smoothness and great power consumption
Linux 2.6.32.9
allows Ramhack from 0-96 MByte (this means 0-96 MB additional real RAM, lowering GPU Ram), can be set easily with GuesteOC app, reboots aren't affected by ramhack.
comes with TrymHansen's famous GuesteOC app - following kernel-features can currently be controlled with it:
stepless or stepful over- and underclocking from 216 MHz - 1450 MHz
complete deactivation of second cpu core (and reactivation of course)
setting of maximum screen-off frequency
second cpu core activation speeds/times and auto-calculation of those
change of IO schedulers and read-ahead buffer
swappiness
2-way virtual RAM enhancement: you can choose between Swap & ZRam and enable/disable them on the fly
disable fsync (can be used for higher benchmarks) - attention, disabling is bad for your data in case of sudden power loss and also it can both decrease or increase power consumption
touch-light brightness (101 intensity steps choosable)
special feature: changing auto-backlight intensity (8 intensity steps choosable)
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying
app for Undervolting included (MyrtUV by TrymHansen)
Default CPU speed is 1000 MHz - but you can OC using the included app of course
OnTheFly-changing of kernel logging policy:
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC app.
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
merged/included FORCE_FAST_CHARGE - credits to chad0989
...
For this kernel + the GuesteOC app to work properly you need init.d scripts to be working on your ROM. You should be able to enable them using the latest AROMA installer of guestekrnL >= v2.1, if they are not working on your ROM.The toolchain affects: stability, smoothness, performance & power consumption.If you can't enable ZRam, upgrade to Rebuild 2 release of guestekrnL v2.0 or to a newer releaseIf something else doesn't work: Recommended is Busybox 1.19.4 -- install it with JRummy installer, not a different installer!@ROM-CHEFs (important!):
If you want to directly include guestekrnL v2.x in your Stock ROMs, you will have to set the command line parameters of your ROMs boot.img (via Android kitchen -> modify boot image -> modify command line params) to the following (otherwise Ramhack can't be enabled by the users):
Code:
[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3000001a323ed07 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800
(This will enable the default 32 MB RamHack right after the installation of your ROM with latest guestekrnL included.)
Also in v2.0 the setup script and many setup files of guestekrnL have changed - make sure to merge all the important parts into your ROM setup. Also do not include boot-up scripts which modify LED brightness or virtual RAM and similar stuff or disable kernel logging because that's the job of GuesteOC app.
Changelog latest version:
v2.2.1
smoothness-related changes for higher smoothness
tun.ko now built-in in kernel again
spica toolchain edition now is default preselected on in AROMA installer
v2.2
smoothness-related changes for higher smoothness
better RAM management
tun.ko now as kernel module instead of built-in in kernel
dropped symbi0sis-toolchain edition, instead added spica1234 toolchain edition (like the name says this toolchain has been built by spica1234, credits for this chain go to him)
new unique feature: introducing dual-vibrator support:
in GuesteOC you can set the kernel's vibration intensity (like you already know)
new: intensity 1500 - 2700 uses "weak" vibrator output device for vibration (the one used in original stock kernel)
intensity levels >2700 - 3700 use the "strong" vibrator output device
some prefer the weak device because it seems to be more "accurate", others prefer the stronger one
now it's completely up to you which one to use, without having to change the kernel version! Enjoy
Changelog version 2.1:
v2.1
also read the v2.0 Changelogs!
smoothness-related changes for higher smoothness
added FlixEdition-Power by and for flix123 with the following differences to official version: https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards/compare/master...FlixEdition - the differences are minimal because I merged some good changes into the official version of the kernel. Nevertheless thanks to flix123 for his endless efforts to make this kernel smoother :good::victory: Currently the FlixEdition-Power is only different from guestekrnL-Flix123-Chain in it's default GuesteOC settings (heavy use of second core, different scheduler, stock led brightness,...) and in the default ramhack size. Still flix123 has earned his own edition named after him, as he is the creator of the very smooth flix-toolchain I use for 2 of my builds as well and the one responsible for some more smoothness improvements in the kernel in general.
Still I recommend to use the normal/official build as of the default heavy use of second core of FlixEdition-Power (higher battery drain during use) and because fsync is disabled by default - not everyone likes that.
AROMA Installer is now able to enable init.d, apply smoothness tweaks and convert filesystem to ext4 if a user selects this option - however this option can only be experimental as it replaces the boot image, which should but might not work fine on every stock ROM. Backup first!
Changelog version 2.0 part 3/3:
v2.0 Rebuild 2
this kernel version is still the same as v2.0, so also read the other v2.0 Changelogs!
fixed ZRam not working for everyone - see the changes here: https://github.com/StefanGuendhoer/...mmit/55eac20be15cffe001c5d2ce9452f3887e7fff74
This rebuild has been made for all those who had problems enabling ZRam
Who already got ZRam working and already has latest GuesteOC v2.3, does NOT need to upgrade to this release!
Changelog version 2.0 part 2/3:
v2.0 Rebuild 1
this kernel version is basically the same as v2.0 so please read the changelog of v2.0 additionally!
introducing 2 new editions (built with a toolchain by flix123) for provision of maximum smoothness + an extra AROMA version with ALL kernel editions inside:
{
"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"
}
all other editions are the same as before, only GuesteOC has been updated and they have been recompiled (couldn't avoid)!
AROMA installer package has been built automatically by my new enhanced kernel building script
AROMA installer package allows you to choose between 6 different kernel editions, and allows you to set max. CPU frequency, RamHack size, desired IO Scheduler and ZRam enabled/disabled right during the installation of the guestekrnL kernel
new GuesteOC v2.3 directly included with undervolting AND overvolting (new) - TrymHansen is the creator of guesteOC, thank you very much for this awesome new version, Trym! :good:
complete sources of guestekrnL v2.0 will be published soon - this means the Ramhack for stock, vibration strength for Stock, tweakable kernel logging and other features introduced by me for guestekrnL will be available for other developers too - please don't forget who introduced them first.
Advice:
Please try the new edition(s) compiled with flix123 toolchain (by flix123, thanks to flix for provision!) - you can test & install them along with your preferred settings with the cool new AROMA installer package!
Changelog version 2.0 part 1/3:
v2.0
introducing ramhack + changeable ramhack size (!) (details some lines below) - never seen on any LG O2X stock kernel before
introducing completely adjustable vibration intensity (!) (details some lines below) - never seen on any LG O2X stock kernel before
additional UHOC (ulta high OC) version is available too with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
only use UHOC version if you really need overclocking > 1,45 GHz! otherwise use default version (HOC) with OC up to 1,45 GHz
new symbi0sis toolchain v2 with full arm hard-float ABI support instead of softfp, updated components and tweaks
4 kernel versions:
Which version of the kernel should I take?
only take a version with "-UHOC" at the end of the filename if you really need highest overclocking
symbi0sis toolchain is always changing and work in progress. its purpose is to beat guestekrnL toolchain in kernel smoothness, performance and battery.
rktdi said:
hmm which version to choose? guestekrnL tool chain or symbiosis tool chain? what is the difference?
Click to expand...
Click to collapse
As mentioned the compilation toolchains are used for compiling the kernel under linux (= making binary kernel image out of kernel source files) and affect battery, stability, smoothness (scrolling) and performance of the kernel.
guestekrnL chain is from May 31 2012 (initially created for guestekrnL) while symbi0sis v2 is from October 10 2012. guestekrnL chain is the "good old stable&smooth one" and symbi0sis is the one aiming to beat (be better than) gueste --- war of the chains :laugh:
Some differences:
- symbi0sis chain v2 uses gcc compiler v4.5.4 (2012) while guestekrnL uses gcc v4.5.3 (2011)
- symbi0sis chain v2 uses some newer libs and components than guestekrnL chain
- symbi0sis chain v2 is a full hard-float chain while guestekrnL chain is softfp (probably performance improvement)
- some differences in build flags
- minor other differences
Feedback on the performance of both chains by different users:
- symbi0sis chain v2 seems to provide a bit better power consumption than guestekrnL chain
- symbi0sis chain v2 seems to provide the best overall performance
- guestekrnL chain seems to provide the smoothest slow-scrolling (so the fewest lags when scrolling very slowly)
- guestekrnL chain seems to be a bit more stable than symbi0sis chain (so if you use symbi0sis and have freezes or something you might want to try guestekrnL chain edition)
So just try whatever edition you like, they are both not bad at all.
enhanced kernel building script which automatically builds all 4 versions of the kernel (2 toolchains + UHOC/nonUHOC) - advantage for me basically because it saves time :laugh:
switched back to ZRam without snappy compression due to some lagginess reasons
drastically improved smoothness
various changes in kernel configuration, inspired by 1.1.2 of my CM7 symbi0sis kernel
added full arm hard-float ABI support for performance
there have been some changes in the kernel & GuesteOC default values, so the currently recommended settings will be set in GuesteOC automatically after kernel flash. Try them.
changed auto-brightness steps: the lowest step now is 99% identical to CM7 kernel original default auto-brightness
new build flags for kernel modules
updated GuesteOC app by TrymHansen (thank you!!!) for controlling new kernel feature, supporting new kernel modules structure & mounting and fixing some bugs
tweakable kernel logging (logging disabled by default)
screen-state-based kernel behavior: giving for example the possibility of kernel logging only when screen is on
kernel modules can now be loaded with "modprobe <module-name>" and don't need to be loaded with "insmod <full_module_path/module-name.ko>" - advantage: modprobe doesn't need full module path and also loads dependent modules if there are dependencies
stability improvements
removed Compcache (ZRam is better)
I introduced a completely new kernel OnTheFly feature: (never seen on any LG O2X stock kernel before)
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC (see screenshot).
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
Amazing new features by TrymHansen for GuesteOC:
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying - THX again to TrymHansen, you are the best!
optimized AES and SHA1 routines
current size of Ramhack is OTF readable in /proc/gueste/ramhack_size -> default: 32 MB Ramhack [changebale in GuesteOC]
OTF changeable vibrator (haptic feedback) intensity in /proc/gueste/vibe_intensity (values 1500-3700) [changebale in GuesteOC as well]
enabling optimized crypto routines in defconfig
added 3 small binaries to kernel setup zip for providing GuesteOC app the possibility to change ramhack size
many changes in kernel configuration
battery-related changes
some other, minor things
some tweaks
credits during changes of this release to TrymHansen, morphic, wkpark, vadonka, faux123 and benee - If I forgot someone he/she is most likely mentioned in the git commits or source code merges or the changelogs and commits of my symbi0sis kernel
Ramhack:
Ramhack size in MB (set it in GuesteOC):
MisjudgedTwat said:
0 -- Everything is working
32 -- Everything is working [in rare cases problems with video rec]
48 -- Everything is working [in some cases problems with video rec]
64 -- 1080p video recording/playback doesn't work
80 -- 1080p video recording/playback and some very heavy 3D games doesn't work (Chainfire3D texture resolution adjust help)
96 -- 1080/720p video recording/playback, and many 3D games doesn't work (Chainfire3D texture resolution adjust help)
Click to expand...
Click to collapse
Questions:
What does virtual memory/RAM mean? Virtual memory means that the real available RAM (the more the bigger Ramhack is) can either be compressed to simulate additional RAM (= ZRAM) or it can be enhanced using a Swap file which will be stored on the SD card. Swap is slower than compressed RAM, and compressed RAM is faster but needs more battery!
I OC'd / UV'd too high and get bootloops - what now? If you OC'd too high and get bootloops, re-flash only the kernel, it will remove OC / UV ! No need to re-flash whole ROM.
Download all versions: http://www.mediafire.com/?9lvnkfthj9dbo
Installation: Just flash. Preferably use a clean system without many left-overs from other kernel so you don't get a wrong impression of symbi0sis kernel.
Stefan Gündhör said:
Hi! Nice to hear that you are willing to try guestekrnL :good:
Well since some version guestekrnL deletes some init scripts and some additional stuff flashed along with other kernels like HorsePower, but there might be some files (left-overs) not being deleted by guestekrnL setup script.
Easiest way would be if guestekrnL cleaned the whole init.d folder, but I always criticized this about kernel DEVs doing this because in this cause all custom init.d scripts added by creators of custom ROMs would be lost too.
However there are some things guestekrnL can't/doesn't clean: Tweaks by other kernels in /system/build.prop file per example. These entries will be left over even if you change your kernel.
You could of course replace this file with the original file of the ROM you use.
Additionally in past some kernels also replaced some system files with tweaked or different ones. You can't really undo that.
But basically this is no problem, the tweaks will work with guestekrnL as well. I just mentioned it because user experience / power consumption / stability of "clean ROM + guestekrnL" versus "ROM with different kernel previously + guestekrnL" might be different.
But just go ahead, try guestekrnL and if you think you need a full wipe you can still do that later on
Click to expand...
Click to collapse
Complete sources in the main download folder: http://www.mediafire.com/?9lvnkfthj9dbo
Screenshots: will follow soon
Changelogs & description guestekrnL v1.x:
guestekrnL v1 - for Stock & Stock-based ROMs
Download all Versions: http://www.mediafire.com/?9lvnkfthj9dbo
Latest version (v1.8.1-HighOC): http://www.mediafire.com/?pfby2anqqdifz
Latest FlixEditions by Flix123 (based on guestekrnL 1.8.1 if > v1.3): http://www.mediafire.com/?kguh32agjhmgp
You find the latest GuesteOC tool (for overclocking and tweaking) by TrymHansen always here: LINK
Click to expand...
Click to collapse
You need init.d to be already working on your ROM in order to use GuesteOC! - If u don't have init.d yet, u can enable using a spica PerformancePack
Click to expand...
Click to collapse
Easily build your own (modified) version of guestekrnL: http://forum.xda-developers.com/showthread.php?t=1678049
Click to expand...
Click to collapse
Changelog:
June 09, 2012 -- added best battery edition of guestekrnL v1.8.1: LINK
Changelog:
June 03, 2012 -- guestekrnL v1.8.1-HighOC: LINK
Changelog:
May 30, 2012 -- first community build of guestekrnL is out -- guestekrnL-FlixEdition-v1.1: LINK
Changelog:
May 28, 2012 -- rebuild of guestekrnL SR99R100.1PI.1337 using a different VM -- rebuilt version is smoother than the build from yesterday (May27)!
Changelog:
May 27, 2012 -- guestekrnL SR99R100.1PI.1337: LINK
Changelog:
May 13, 2012 -- guestekrnL v1.7_SE-Final: LINK
Changelog:
May 01, 2012 -- guestekrnL v1.7.0: LINK
Changelog:
April 26, 2012 -- guestekrnL v1.6.2: LINK
Changelog:
April 17, 2012 -- guestekrnL v1.6.1: LINK
Changelog:
April 13, 2012 -- Bugfix01 for guestekrnL v1.6:
Small Bugfix: Trym has discovered a very small bug, causing one of the saved OTF frequencies not to be remembered correctly after reboot. You can solve it by flashing the Bugfix01 or the kernel with Bugfix01 included.
(This is no kernel bug! Just a bug in an /etc/init.d/ script responsible for "remembering" the OTF values)
Click to expand...
Click to collapse
Changelog:
April 12, 2012 -- guestekrnL v1.6 + Bugfix01 (April 13): LINK
Changelog:
March 26, 2012 -- guestekrnL v1.5: LINK
Changelog:
March 20, 2012 -- guestekrnL v1.4.1: LINK
Changelog:
March 07, 2012 -- guestekrnL v1.3.1:
extremely small kernel and modules sizes (even without -Os compilation flag)
both ZRam (+369 MB Ram) and Swap (+383 MB Ram) enabler/disabler available for download - freedom of choice (ZRam enabler will disable Swap and vice-versa) ; Zram should be more performant than Swap, but eventually also drain the battery faster ; both ZRam and Swap are disabled by default
BFQ scheduler updated
many entries added to global kernel configuration file "include/linux/guestekrnl.h" (only important for users interested in compiling guestekrnL from source)
bug fixes, performance tweaks
compilation flags changed (-O2 instead of -Ofast)
some kernel logging removed
xz-compressed kernel image, xz-(de)compression (boot-time) support added
reverted some changes in lowmemorykiller
many voltage and clock/speed adjustments
new version of ZRam enabler, the old one won't work!
stable, not too highly undervolted kernel -- you can UV yourself using UV tools though (only overclockable edition)
Changelog:
March 03, 2012 -- guestekrnL v1.2.1:
Overclocking bug fixed - once CPU is OC'd it will stay OC'd now
changes in cpu speed steps: new steps are 216, 324, 503, 800, 1015, 1100, 1216, 1408 (same steps as etana kernel currently uses)
kernel default cpu speed now 1.0 GHz like stock kernel
screen off max cpu speed now 503 MHz
changes again in second core handling
stability fixes
strong vibration editions (thx to spica1234) -- please note that strong vibration might cause problems if haptic feedback is enabled in LG stock keyboard:
markop90 said:
I guess the vibrator is too strong and LG "tap" sensors are activated moving the cursor randomly
Click to expand...
Click to collapse
Changelog:
March 02, 2012 -- Additional version without OC/UV possibility @1.0 GHz Stock-max.Speed -- for stock kernel lovers
Changelog:
March 01, 2012 -- guestekrnL v1.2 FINAL:
never-seen smoothnes @ 912 MHz (= underclocked)
non-working ramzswap kernel module removed
ZRAM integrated as kernel module (use is optional; use of ZRAM "increases" RAM amount (= +369MB), but might drain battery faster)
activation/deactivation pack for ZRAM
old swap file will be deleted on kernel or zram pack install
lower swappiness if no ZRAM is used
ipv6 enabled again
revert second core activation & treshold back to stock kernel settings for better battery
there will be an additional version with stronger vibration soon (thanks and credits to spica!)
currently two downloadable & flashable kernel ZIPs:
guestekrnL_v1.2_FINAL_withAndrevOC_normalVibration.zip -> Andrev OC Adjuster and Myrt Undervolt GUI will be installed directly with the kernel
guestekrnL_v1.2_FINAL_Bulk_normalVibration.zip -> Only the kernel will be installed
-- pending: version with stronger vibration
Changelog:
February 18, 2012 -- FINAL version of v1.1:
new cpu speed steps & voltages
again more smoooothness (scrolling, responsiveness)
max. ScreenOff CPU frequency lowered to 316 MHz and some other changes (hopefully saving some juice)
3 versions of kernel with different cpu speed steps:
Low overclock version with cpu speed steps 216-316-503-655-816-912-1015-1100 (MHz) -- recommended version!!
Medium overclock version with cpu speed steps 216-316-503-655-816-912-1015-1216 (MHz)
High overclock version with cpu speed steps 216-316-503-655-816-912-1015-1312 (MHz)
the first 7 cpu speed steps are the same in all 3 versions, because I decided these steps are the best choice -- there is only one OC step because there can only be 8 CPU steps (handled by OC tools)
try 1,1Ghz max version, it is smooth enough for nearly everyone I hope, even at 1,0 GHz!!
default max cpu clock (screen on) is 1015 MHz
Features/Description
WIPE DALVIK CACHE BEFORE INSTALL
- EXT2/3/4 built in
- based on official LG v20Q kernel sources
- OC/UV support, overclocking up to 1408MHz
- Andrev OC compatibility
- not highly undervolted by default, you can do this yourself using tools
- however, still some voltage tweaks
- CPU clock locked at max. 503 Mhz while screen is off (taken from swiftextreme kernel if I remeber correctly) - no need to set this in oc tools
- default CPU clock at 1.0 GHz, you can higher/lower it yourself using OC tools
- very smooooooth
- Voodoo Sound
- SLQB
- CIFS, TUN
- SWAP & ZRAM support
- many Tweaks either by me or "inspired" and taken from the source codes of ironkrnL and SwiftExtreme kernel
- compiled with Linaro GCC & Toolchain
- more things which you can find in the latest changelogs
Credits:
- setiron
- fajarep
- cpasjuste
- pastime1971
- spica1234
- supercurio
- dr4go
- LG for v20Q sources
Big THX to spica1234 for supporting me via PM during development!!!!
Latest sources @ Github (1.0 sources @mediafire): https://github.com/StefanGuendhoer/LG-P990-O2X----guestekrnL-for-stock for kernels < 1.6.2 and https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards for kernels > 1.6.2 OR at http://androtransfer.com/?developer=gueste&folder=sources
Source for kernel 1.7-SE is within the download folder of the kernel and @androtransfer and @mediafire!
I'll not use this moment, because I use CM7 + vadonka's kernel. But I followed the topic and kernel development, for future testing based on a stock rom. Thanks Stefan.
totally agree with your initial paragraph, personally I envy the knowledge that shows every day spica, but for the ignorant like me, is much more useful to mention kernel set, and while this is a personal opinion, maybe instead so many parameters to configure, it would be more useful, use presets as a function of the tastes of each user, power, response, saving battery etc etc, well, maybe not the right place here, well, in principle, its kernel is installed normally, it may seem silly but I assure you it is not, say my phone is very special in terms of internal modificaiones already the slightest forces blocked at the moment I tried connecting wifi perfect, seamless gPS, fM radio without problems and later proves the bt. As for the rom, I'm wearing the carburano and is perfectly smooth, no lags etc., for the moment .... we know that android is the opposite of wines worsen over time. Best regards, and I hope this is not really your last job for our phone, I say sincerely.
Stefan,
Thank you very much for this kernel, installed without thinking and testing it now. Couple of observation I made, and opinion I have about the testing stuff.
1. I have no experience in android and stand in minus on technical aspects. You opinion about letting users do the testing of kernels is kind of valid BUT since IMHO, what spica doing is the right thing here. Since this is a development section. So technically developers release their work here so that others developers can test it and contribute 'technically' to improve their work. Honestly speaking dumbass users like me have absolutely no place here .
Everyone who uses the work of a developer have to , should and must understand that what he is doing is testing a possible experimental work and it can lead to unpredictable results. Then analyze what happens, look for possible workaround or solution and give it back to the developer and others, to improve his work.
Dumb users like me have no place here because I don't understand what happens if I use a particular switch or parameter. So there is absolutely no point doing something that I have no clue and then come whining and spoil the developers thread with statements like "helppppppp or my phone is deadddd " or similar things, without even bothering to give details like - for example - what kernel they use, what BB / ROM combination they have, What other application they installed that possibly can create this problem.
Having said that, there are a lot of good developers who patiently help people like this because of the goodness of their heart - you are on of such person. Yet, this being a developer's section should not be treated by noobs as a personal helpdesk to get instant technical support for FREE. If that happens, it affect the development very badly because it wastes everyone's time - especially of the developers.
Phew..! Since my rant is over, I will get back to you 'if' I understand what happens after installing your kernel and eagerly waiting for your latest gift to us .
Congrets for new kernel, nice to see you back
No offence, I don't like even to write this, first time in my life I'm writing this.
OP:
It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers, and so I don't really like this "outsourcing" of sensitive kernel settings to users. There are various good CM7 kernels and they don't need this stuff either. Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation. So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself. The sources of ironkrnL and Swiftextreme kernel (both CM7 kernels) have been very inspiring and helpful.
==>" it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
What I do is something you can't, that's why want to keep it simple What I do is something *new* which needs more skills, knowledge of HW and programming Yes users are user not Devs, That's why I've set simple 'Powersave" and 'Nitros' profile for them who have no more knowledge. And we've an APP now to control these values
==>" and so I don't really like this "outsourcing" of sensitive kernel settings to users"
SENSITIVE? None of my max values are above your or any other Kernel's max values. I've given an opportunity to lower the values not increase the value. And my default values are lower than your or anyother kernel So in terms of SENSITIVE, atleast RC12 values are not sensitive, And I've written kernel modules to not accept any SENSITIVE values,You don't like thiis "outsourcing" values. What you like applying various pre-available *patches* which berely are made for android? Or you dislike someone's coding knowledge?
==> " There are various good CM7 kernels and they don't need this stuff either"
Nobody needs nothing as per your psychology. And as per your psychology CM Devs should have abandoned development after they had released first stable version. As per your psychology they should have stopped adding new features and releasing nighties and RCs? What can we say in other words? "End Of Development?" Nothing is needed until it's valued. Do you know what SR and RC means? PPL who wants stability can stick with SR series. CM7 kernel don't need this stuff cause they've more important other things to concentrate on
==>"Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation"
Where you learn this? Yes nobody uses O3 but Ofast which is 2 steps more optimized flags. Swiftextreme uses Ofast and many devs use Ofast. So as per your theory does these kernels are resulted broken kernels with bugs and issues?
Then I think you should e-mail GCC to remove this O3 flag
==>"So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself"
Your kernel obviously should be stable cause You've done nothing creative. What do you think is resposible for stability? You used LG base source, merged Oc and Voodoo codes and other codes available. So definately it should be stable. But is that stability is credit of yours or LG and other Devs? There is a way much difference in compiling kernel and developing kernel. Anybody can merge changes with basic linux knowledge and issue few commands and kernel is ready. Developer in real mean is someone who creates something out of nothing, who has knowledge of stuff and how stuff work, someone with knowledge of programming to write codes, read and to be understood codes and knowledge to rectify wrong code and correcting them. There is a way much difference in Kernel Compiler and Kernel Developer.
This is no personal, I dont want to hurt anyone but to clear somethings Dont mind
There are some users who prefer simple and stability rather than something with many new features but not so stable.
ryaneu said:
There are some users who prefer simple and stability rather than something with many new features but not so stable.
Click to expand...
Click to collapse
Yes you're absolutely right but whats the theory and logic of writing that paragraph in OP thread?
Does it make sense?
Sent from my LG-P990 using Tapatalk
the difference between the v20l and the v20q kernel is almost nothing.
better off pick any v20l based OC kernels what is tested by the users already
some people believe that the new v20q kernel is have a new features and better stability. i was compared the v20l and the v20q kernel, an other thread im posting the difference and a patch file too. i can say the lg developers did not force themselves.
Moderator Message
Can we stay on topic?? Thanks
Yes that would be bad to close this thread...... for some words that should never have been written....
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
coldfear00 said:
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
Click to expand...
Click to collapse
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Lo_RaT_PeNaT said:
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Click to expand...
Click to collapse
if u wanna talk about kernels and not personal views about who likes what, then stefan should not have said this line " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
Yes that's what I'm pointing, on the first page(OP) of this thread, he should write describtion about his kernel like what other dev does, not about what I or anyone is doing
Never mind
Sent from my LG-P990 using Tapatalk
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
fajarep said:
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
Click to expand...
Click to collapse
fajarep should again return to cheer you too .... not it
getting back to the topic did some1 actually tested this kernel?
Lo_RaT_PeNaT said:
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
Click to expand...
Click to collapse
y r u so hooked up on proving stefan innocent, how do u know he didnt mean to critize spica, and y dosent stefan clear the foul air himself on this thread.
im +1 for spica because if my english aint so bad this line he said looks like criticism to me " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
for my issue resolved, but absolutely sure that the intention of stefan is not apparently be interpreted, also without a doubt, and now please, to the point, the kernel, and I must say that I tried the BT's car and has not been disconnected at any time, not blackscreen not freezes at least for now the battery issue, I can not say for now. Greetings to all.
{
"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"
}
[highlight]This kernel is deprecated, no more progress will be made on this thread as i changed my phone and i don't own a SXL anymore, my work was continued by other great devs so check anders' kernel thread. Thank you![/highlight]
I am glad to present my first real-deal creation to you - LTX Kernel!Features:- [highlight]JB[/highlight] - Updated to latest 3.0 linux kernel tree: 3.0.71.
- [highlight]ICS[/highlight] - Updated to 3.0 linux kernel tree: 3.0.61.
- Overclocking up to 1.8 Ghz.
- Compiled with Linaro 4.7.3 (since LTX 0.7.6)
- Big frequencies table.
- Undervolted lower frequencies.
- VDD Stats (voltage control).
- SWAP.
- KSM.
- ZRam.
- Memory management optimisations.
- Loads of other optimisations.
- Increased performance.
- Increased battery life.
- Stable.
Governors:- Revamped Conservative Governor (ON by default)
- Ondemand Governor (with 2 phases)
- Interactive Governor
- InteractiveX Governor
- Agressive Governor
- LagFree Governor
- Lazy Governor
- SmartassV2 Governor
- Lionheart Governor
Schedulers:- SIO scheduler
- BFQv5 scheduler
- ROW scheduler
- CFQ scheduler
- NOOP scheduler
- Dead-Line scheduler
Buglist:- Since v0.6 - Stock task/memory managers will not detect the amount of RAM used by apps.
As a workaround, use any task manager from Google Play.
How to install:--On S-OFF devices--
-Flash the zip via recovery! (twrp or cwm)
-Reboot
--On S-ON devices--
-S-OFF your device, then use above steps!
(Yes, i highly recommend to S-OFF before using any custom made things!)
or
-Extract the boot.img from the .zip.
-Get in fastboot and flash via [highlight]fastboot flash boot boot.img[/highlight].
-Reboot into recovery.
-Flash the zip via recovery.
-Reboot
[highlight]The same thing applies if you update to a higher version or if you downgrade to a lower version of the kernel.[/highlight]
README!- JB Versions recieve OTA updates over Goo Manager!
-Do a nand backup before testing!
-[highlight]Test[/highlight] versions are for testing, therefore expect bugs and please report them in detail.
-Beware that you use this at your own risk and please provide feedback in order to get it stronger/better/bla bla bla
-The versions of kernel for ICS Sense around here should work on all OFFICIAL ICS 2.31.401.2 RUU based roms, and the official one of course, so if you use a different firmware, make sure you make a backup as there are BIG chances it will not work.
-The versions of kernel for JB will work only on AOSP based ROM's like Cyanogenmod, Paranoid, PAC, AOKP and so on, version 4.2 and up!
-The JB build already have this kernel included as it's the only one right now to support JB for our device, but here you can get the latest changelogs and eventually updates for the kernel if not available otherwise.
-[highlight]ION[/highlight] versions of kernel are for ION versions of ROM's, don't use it if you don't know what that means!
-[highlight]DO NOT USE JB KERNELS ON SENSE/ICS ROMS![/highlight]
-Use SetCPU or CPU Master Free(<<my personal choice) in order to activate OC or other Governors and Schedulers, can be found on market
What i say here is just my opinion for the best freq usage possible:
-Stock: Conservative 245 - 1500 Mhz
-Battery friendly: Conservative 149 - 1200 Mhz
-Balanced: SmartassV2 149 - 1497 Mhz
-Kickass: Ondemand 245 - 1800 Mhz
--Best Graphics score: 1497 Mhz
--Best CPU score: 1800 Mhz (you don't say?)
(1497 Mhz was introduced in LTX since 0.7.6)
Download links:JB - AOSP
[highlight]Test:[/highlight]
-none-
[highlight]Latest stable:[/highlight]
LTX Kernel JB v1.2 - Linux Kernel Version v3.0.71
(Or use Goo Manager from phone, hit compatible ROM's > runnycm > kernels > latest version + changelog included.)
[highlight]Archive milestones:[/highlight]
LTX Kernel JB Archive
ICS - Sense
[highlight]Test:[/highlight]
-none-
[highlight]Latest stable:[/highlight]
LTX Kernel v0.7.8 - Linux Kernel Version v3.0.61
[highlight]Archive milestones:[/highlight]
LTX Kernel v0.7.6 - Linux Kernel Version v3.0.57
LTX Kernel v0.5 - Linux Kernel Version v3.0.16
Changelog:[highlight]JB - AOSP[/highlight]
v1.2 - Added battery indicator fix by anders3408 + Updated 2 way recording + Small other optimisations.
v1.1 - Updated to 3.0.71 + Completely new GPU drivers, backported from jb2.5.1 CAF branch (3.4.0 version of kernel).
v1.0 - Updated to 3.0.70 + Completely new WiFi driver, pure Google/CAF one, bye bye HTC + Small block updates + Fixed multi-touch issue.
v0.9 - Updated to 3.0.69 + Wifi PM_FAST during screen off + Added BPF Jit + KSM support + ZRam support + others.
v0.8 - Lots of KGSL (video drivers) optimisations and improvements + Swap.
v0.7 - Updated to 3.0.66 + Added ION support.
v0.6 - Lots of ARM optimisations + LZO compression (faster boot).
v0.5 - Updated to 3.0.63 + Changed the GPU drivers to CAF ones + loads of vsprintf optimisations.
v0.4 - Fixed the BT for good.
v0.3 - Added some preparations for BT.
v0.2 - Fixed Random Reboot problem.
v0.1 - First bootable JB kernel.
[highlight]ICS - Sense[/highlight]
v0.7.8 - Updated to 3.0.61 + Interactive, InteractiveX, Lazy, Lagfree, Agressive Governors + Jellybean 4.2.1 Support
v0.7.7 - Updated to 3.0.58 + ROW Scheduler + Loads, i mean LOADS of changes and optimisations
v0.7.6 - 149 Mhz to 1.8 Ghz and more freqs, 1.9 and 2.0 were useless anyway + Some optimisations + First version compiled with Linaro 4.7.3.
v0.7.5 - Added more freqs + OC now from 149 Mhz to 2.0 Ghz.
v0.7.4 - Updated to 3.0.57.
v0.7.3 - Tons of optimisations (Github/Commits for detailed changes) + Fixed the random "not boot" bug.
v0.7.2 - Updated to 3.0.56 + Check Github.
v0.7.1 - Added BFQv5 scheduler + Other changes.
v0.7 - Fixed some UI glitches + VDD stats + Increased compatibility over all sense based ROMs.
v0.6 - Aded SmartassV2 + Updated to 3.0.51.
v0.5 - WiFi working + Stock governor set to Conservative + Battery Tweaks !
v0.4 - Third public release - OC just to 1.8Ghz as to 1.9Ghz is not stable.
v0.3 - Testing version - Messed with drivers and different device configs.
v0.2 - Second public release - Significantly inproved performance - no WiFi !
v0.1 - First Public release - OC 1.9, Stable, Lionheart governor, SIO Scheduler.
Tutorials:[highlight]2 Way Recording:[/highlight]
Download Call Recorder, for best experience use as source phone line, highest quality, mpeg4 format, works great on me!
[highlight]KSM:[/highlight]
Kernel Samepage Merging, more info here.
To activate it in the kernel just do:
Code:
echo 1 > /sys/kernel/mm/ksm/run
[highlight]SWAP:[/highlight]
To activate swap, find a init.d script or use Kernel Tuner to set it up.
[highlight]Dynamic FSync:[/highlight]
Activate it by using this command:
Code:
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Sources:For a more detailed Changelog check the GitHub repo!
As the source-code may help others, or if you simply want to see what the code looks like, here it is the gihub link of my kernel, it will be updated as soon as changes are made on it, enjoy the open-source creations!
FAQ:Q: How can i use SWAP?
You need to find a script or to activate it manually, check the xda forum for a init.d script for that.
Q: Will battery last more with this kernel?
On stock values yes, it can be improved by changing VDD voltages and Underclocking.
Q: Will performance be better with this kernel?
It also depends on the ROM you are using, but YES, performance will be better.
Q: What are all the terms around here about?
Check this beautiful and plentiful GUIDE!
Q: Why should i use this kernel?
Because it's better than stock, don't believe me? Try it!
Q: Will you port this or that kernel for our device?
No, but i can include features, just ask for them
Q: With what Toolchain is this kernel compiled?
This kernel is compiled with official Google toolchain version 4.6.3
Q: Why don't you use this or that toolchain to compile your kernel?
Because there is no difference, check this thread for details.
Fanbar:As now the kernel has a little personality, i decided to make a fanbar
Special credits:
-CodefireX Team (synergy)
-HTC One V Community (maxwen, Kumba, Lloir, simmons and more!)
-FXP
-Ezekeel
-francisco.franco
-faux123
-AdiPat
-Coolexe
-DevChun
-[vertigo]
-Code Aurora Forum (CAF) (for being so awesome!)
-Linus Torvalds (for the original ideea of the whole Linux)
-XDA Forum for great materials.
-Google for being a great search engine and for Android.
-Github for sources i got inspiration from.
-Other great people!
For the no wifi problem did you get all the compiled modules and flash them with the kernel? If so just ignore me.... lol
[vertigo] said:
For the no wifi problem did you get all the compiled modules and flash them with the kernel? If so just ignore me.... lol
Click to expand...
Click to collapse
Yes, i got all the compiled modules and flash them with the kernel, the problem is caused by something else, i'm a bit busy with the school right now, i think in know where the problem is , but next week we will have a fully working/faster kernel
What toolchain did you use to compile?
[vertigo] said:
What toolchain did you use to compile?
Click to expand...
Click to collapse
The one provided by you - the official one so to speak
hi sir i flash this kernel working well restore wifi thnx
Hi,i use your kernel on sense 4.0......all works fine and super smooth,but the only bug it's the wi fi connection....can you fix this bug for sense 4.0? Thanks
lika85 said:
Hi,i use your kernel on sense 4.0......all works fine and super smooth,but the only bug it's the wi fi connection....can you fix this bug for sense 4.0? Thanks
Click to expand...
Click to collapse
How to install?
-Do a NAND backup! (yes, you must!)
-Flash the zip via clockworkmod!
-From clockworkmod go to backup and restore > advance restore > restore system!
^ In this way you have WiFi
relisys667 said:
How to install?
-Do a NAND backup! (yes, you must!)
-Flash the zip via clockworkmod!
-From clockworkmod go to backup and restore > advance restore > restore system!
^ In this way you have WiFi
Click to expand...
Click to collapse
Or flash the v0.5 and it wiil work
Lexmazter said:
Or flash the v0.5 and it wiil work
Click to expand...
Click to collapse
Thanx
i flashed the Kernel 0.5 and wifi is working.
Wow...all work fine in Sense 4.0....3g connection it's so fast and the system it's very smoth and stable....
Thanks
lika85 said:
Wow...all work fine in Sense 4.0....3g connection it's so fast and the system it's very smoth and stable....
Thanks
Click to expand...
Click to collapse
The kernel will be in testing for about a week to test the battery life as there are some things i changed for battery, please feedback battery life!
Thank you!
Congrats mate for your 1st project! I'm happy to see this community still have supporter..
Sent from my HTC One X using Tapatalk 2
Well done man, You're just what this forum needs How did you get wifi working?
[vertigo] said:
Well done man, You're just what this forum needs How did you get wifi working?
Click to expand...
Click to collapse
Well, scavanger work, i included the wifi module from your kernel
My module doesn't seem to like the wifi chip
Lexmazter said:
Well, scavanger work, i included the wifi module from your kernel
My module doesn't seem to like the wifi chip
Click to expand...
Click to collapse
Hahaha I've had to do that before... just glad you got it working
Sent from my ParanoidAndroided Galaxy Nexus
Can you add SWEEP2WAKE ?
Works great with Sense 4.0, thanks mate! Just wondering, after installing setCPU is it only necessary to set mhz to 1804 and nothing else such as governors etc? Anyway, works very fast, good start!
Yes, a so fast battery drain is the only little problem with the kernel...
thanks for this kernal, now my battery consumption in sleep mode is Awesome,,, the day before when i was not using ur kernal it took 30% of battery for one night,,now after flashing this Awesome kernal it consume 3% for whole night... Loved it . Keep going .
[KERNEL][4.1.2][03 Jan.] ★ LiteGX v5.8.0 ★ <><> ... DISCONTINUED !!
{
"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"
}
WARNING : THIS KERNEL IS ONLY FOR ANDROID 4.1.2 (SAMSUNG) !
This is a pure LITE, STOCK WAY & STABLE kernel with MINIMAL features.
If you are looking to a kernel with less features and more close to stock, check out my StockGX kernel.
My goal is to offer a slight modification of our Samsung stock kernel's, with few features, aiming a better battery life than stock without affecting any drain.
This is a kernel "plug-and-play" or I would say more "flash-and-play". No need for tools or apps to configure the kernel. This is the way I wanted it. A bit like speedmod kernel did.
Unfortunately, I'am not a developer but just a basic person with some android/linux knowledge already.
My dream was one day to create my own kernel, and thanks to great developers that answered my many questions, this dream has been possible. I'am very happy and proud to share my first ever kernel to everybody here.
It must be only flashed over an official Samsung ROM and not AOSP/AOKP !
Feel free to include my kernel to your ROMs / Threads but please don't forget to inform/ask first via PM and credit me in your original thread.
★ FEATURES (up-to-date) ★ :
Base :
Directly based on update11 source from Samsung (for clean work and stability).
Compiled with ARM EABI (v4.4.3) toolchain (with flags optimizations).
Ramdisk from XXEMD3 (for update10 ROMs compatibility without the need to change radio).
Main :
ZZMoove (v0.7d) governor (added and set as default). Many profiles included, grab them below.
ROW (v4) optimized and as only I/O scheduler.
Wolfson Boeffla Sound (v1.6.4 drivers) compatibility.
hardcore mDNIe tweaks (for better colors + sharpness fix for better readability).
Touch-to-Wake (v1.1a) (but disabled by default). Many profiles included, grab them below.
USB charging increased (to 900mA instead of 475 by default).
Allow manual brightness to 300 candela.
zRam added (but disabled by default) with LZ4 compression and 4x swaps. Many profiles included, grab them below.
init.d support.
CRT-off effect friendly (early_suspend set to 100ms).
Native ExFAT support (from official Samsung source).
xbox controller support.
Triangle Away support.
Various tweaks :
4x zRam swaps capability (instead of single one).
Optimized ARM CPU topology.
"GENTLE_FAIR_SLEEPERS" disabled.
"ARCH_POWER" enabled.
"SCHED_MC" added. Many profiles included, grab them below.
"CONFIG_SCHED_AUTOGROUP" enabled.
ROW scheduler & blk-core tweaks.
"Westwood", "HTCP" and "BIC" TCP congestion control modules added. Many profiles included, grab them below.
Enabled persistent TRIM support for all partitions.
Fully compressed libs ".ko" modules.
Automatic dalvik-cache wiping in kernel flashing procedure.
Logging and debugging tweaks :
Android logger disabled.
Kernel logger disabled.
Disabled kernel debugging : Samsung / sec_log / last_kmsg / touchscreen / modem / max77686 / sec_watchdog.
Disabled various debug in defconfig.
Features that will NEVER be included in this kernel :
Overclock / Underclock / Undervolt.
auto-root
LED control.
Charge control.
Master sequence (screen calibrated).
ABB (Adaptive Body Bias).
Any upgrade of Linux kernel 3.0.XX.
STweaks compatibility.
Dual-Boot Sammy/AOSP.
CyanogenMod compatibility.
MIUI compatibility.
etc.
★ PREREQUISITE ★ :
Any odexed or deodexed international I9300 Samsung 4.1.2 Jelly Bean ROM.
A custom recovery (CWM recommanded) to flash the kernel.
★ FREQUENTLY ASKED QUESTIONS ★ :
How can I customize this kernel ? :
> Mainly with ZZMoove/zRam profiles (grab them below) and with TricksterMOD / SetCPU apps.
What does the LiteGX cleaner script ? :
> It deletes all ZZMoove/zRam profiles that you flashed after this kernel. So you can go in another kernel safely. It don't removes anything else since this kernel is pure stock based and don't add any files/folders that need to be deleted after. This cleaner script will be only efficient in this situation only, it does not clean anything before coming from another kernel to mine.
Do I need to wipe cache + dalvik each time I flash a new kernel version ? :
> Nope. Moreover dalvik cache is already wiped automatically during flashing procedure.
Do I really need to flash any profiles/scripts ? :
> Definitely not. It's user choice to do it but zRam profiles for example are highly recommanded to be flashed since it adds a lot of smoothness and performance to the kernel (and on which is disabled by default).
Do I need to re-flash ZZMoove ZIP profiles each time I flash a new kernel version ? :
> Nope. It just install an init.d script, so it will be permanent until you delete files from your init.d folder or flash "Cleaner" version which will do this for you.
Do I need to remove old ZZMoove profiles manually before flashing a new profile ZIP ? :
> Nope. Each ZIP's include an automatic removal of previously used profile.
Android OS usage is very often at top of my battery stats ! :
> Try wiping cache and dalvik cache manually in your favorite CWM, then make a full charging until green led appears.
★ SOURCES ★ :
Github >> LiteGX.
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate it
stars, and clicking the 'thanks' button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!
Changelog + links
★ All ZZMoove / zRam / Cleaner scripts can be found HERE ★★ All oldest releases can be found HERE ★
★ CHANGELOG ★ :
03.01.2013 : v5.8.0 released.
Disabled "CONFIG_SCHED_AUTOGROUP" (useless in Android).
xbox controller now loaded as internal module (instead of external).
30.12.2013 : v5.7.0 released.
Now compiled with stock Android ARM EABI 4.4.3.
28.12.2013 : v5.6.0 released.
Touch-to-Wake is now disabled by default (for battery purpose).
Added some "Touch-to-Wake profiles" into scripts folder :
- Touch-to-Wake_disabled(stock).zip
- Touch-to-Wake_enabled_3s.zip
- Touch-to-Wake_enabled_5s.zip
- Touch-to-Wake_enabled_8s.zip
- Touch-to-Wake_enabled_10s.zip
- Touch-to-Wake_enabled_15s.zip
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new Touch-to-Wake flashable ZIP's (please remove old one).
15.12.2013 : v5.5.0 released.
ramdisk : re-enabled lowmemory killer in 'init.rc'.
SCHED_MC disabled back by default (0) to avoid some people facing some lags due to agressive value (moreover, I prefer to trust ZZMoove stock behaviour).
Added some "SCHED_MC profiles" into scripts folder :
- "SCHED_MC_power_savings_0(stock).zip"
- "SCHED_MC_power_savings_1.zip"
- "SCHED_MC_power_savings_2.zip"
It will be useful for those who wants to change it without the need to use TricksterMOD (etc) anymore.
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new SCHED_MC flashable ZIP's (please remove old one).
05.12.2013 : Flashable ZIP's adding.
Added some "TCP congestion profiles" into scripts folder :
- "TCP-congestion_bic.zip"
- "TCP-congestion_westwood.zip"
- "TCP-congestion_htcp.zip"
- "TCP-congestion_reno.zip"
- "TCP-congestion_cubic(stock).zip"
It will be useful for those who wants to change it without the need to use TricksterMOD (etc) anymore.
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new TCP flashable ZIP's (please remove old one).
02.12.2013 : v5.4.0 released.
zRam is disabled as default again (this time for ever), for battery purpose at the cost of a bit less multitasking (if you want it again : just flash any zRam script).
"GENTLE_FAIR_SLEEPERS" disabled (back), should improve UI responsiveness.
Updated "zRam_disabled.zip" to match new zRam disabling as default (please delete old one).
28.11.2013 : v5.3.0 released.
zRam is now initialized by default once flashing the kernel with 600MB disksize and 100% swapiness. If you feel some lags, try different values with scripts (hope it will help people finding this kernel more smooth than default without it).
All zRam scripts has been reworked and updated (please delete olders and download latest ones). If you want to turn off zRam, this time you'll have to flash "zRam_disabled.zip" file.
zRam initialization is now using a custom busybox binary directly integrated in the kernel, it will avoid some people not having their zRam properly working due to some roms busybox which cannot execute 'swapon' shell command and with priorities.
- A little reminder : to check if your zRam is working, no more need to install Turbo zRam app, on a Terminal, write : "free" (if you see swap values, then zRam is working) or "cat /proc/swaps" (which will give you more informations on both 4 swap partitions).
- I would like to thanks personally my friend @Yank555 to help finding some zRam initialization problems.
Clic below to see older changelog ..
21.11.2013 : v5.2.0 released.
ramdisk : 'root helper' is back (same as v4.6.1).
Add several TCP congestion control modules :
- Westwood
- BIC
- HTCP
'cubic' TCP congestion will stay as default like stock. You can set your favorite congestion module via TricksterMOD app.
19.11.2013 : v5.1.0 released.
Enabled back: Persistent TRIM support for all partitions.
Enabled back: USB charging increased (to 900mA instead of 475 by default).
18.11.2013 : v5.0.0 released.
Total redesign again from Samsung update11 source.
Removed a LOT of tweaks (back to 'stock way' for real), battery life should be much better than before.
List of removed tweaks :
- Removed: NTFS support.
- Removed: CIFS support.
- Removed: NFS support.
- Removed: Reduced WiFi wakelock.
- Removed: Reduced battery-monitor wakelock timeouts.
- Removed: Proportional Rate Reduction for TCP.
- Removed: Network speed tweak.
- Removed: Decreased touch boost frequency (from 800 to 600Mhz).
- Removed: MMC : Fix the workqueue overload battery waste.
- Removed: MMC : Increased timeout limits for bad sdcards.
- Removed: Doubled min-max readahead.
- Removed: ipv4: save CPU cycles from "check_leaf()" (backport from Linux 3.8).
- Removed: Intelli memory writeback (0 when screen ON & 500ms when screen off).
- Removed: Higher random entropy.
- Removed: Enabled persistent TRIM support for all partitions.
- Removed: Dynamic FSync control (v1.2).
- Removed: Dynamic Screen Frequency Scaling capability (for ZZMoove governor).
- Removed: "GENTLE_FAIR_SLEEPERS" disabled.
- Removed: USB charging increased (to 900mA instead of 475 by default).
- Removed: "cpu_load_slope" correctly set.
- Removed: bcmdhd : Disabled multicast on suspend.
- Removed: AIO enabled (backport of Linux 3.6.x) and tweaked.
Some optimizations into litegx_defconfig.
Overall kernel size is now slightly lighter (again) than previous version.
17.11.2013 : v4.6.2 released.
ramdisk : Fixed zRam which was enabled at boot by default.
ramdisk : Modified 'root helper tweaks' (again) to remove many useless lines, which finally now finally looks like more as an 'init.d helper'.
ramdisk : Many useless files in 'sbin' folder has been removed to let only needed ones for 'root helper tweaks'.
Overall kernel size is now slightly lighter than before.
14.11.2013 : v4.6.1 released.
ramdisk : included 'root helper tweaks' from adam kernel but modified to fit the needs of LiteGX kernel only (removed build.prop and pegasusq governor tweaks).
10.11.2013 : v4.6.0 released.
Updated compilation toolchain Linaro GCC from 13.09 to 13.10 (20131014).
05.11.2013 : v4.5.6 released.
AIO enabled.
Backport AIO from Linux 3.6.x.
AIO tweak : Don't plug the I/O queue in do_io_submit().
03.11.2013 : v4.5.5 released.
Enabled "ARCH_POWER" to use 'arm_cpu_topology' power management features.
litegx_defconfig : Added "CONFIG_TOUCH_WAKE".
28.10.2013 : v4.5.4 released.
Disabled "GENTLE_FAIR_SLEEPERS" (should improve UI responsiveness).
27.10.2013 : v4.5.3 released.
"sched_mc_power_savings" set to aggressive value (2) by default.
17.10.2013 : v4.5.2 released.
Decreased touch boost frequency from 1000 to 600Mhz (should slightly decrease smoothness, but be a bit more battery friendly).
15.10.2013 : v4.5.1 released.
Increased touch boost frequency from 800 to 1000Mhz (should boost smoothness a bit without affecting much battery).
09.10.2013 : v4.5.0 released.
Kernel logging (linux printk) disabled (credits to @Lord Boeffla).
litegx_defconfig : disabled some more debug.
05.10.2013 : ZZMoove profiles updated.
All ZZMoove profiles updated to latest revision (thanks to @Yank555).
Removed "ZZMoove_LCDFreq_optimizations_removal.zip" and included it directly in "ZZMoove_Profiles_Cleaner.zip" instead.
Changed priorities into scripts for init.d : "S98" for every ZZMoove profiles and "S99" for LCDFreq optimizations, to override ones already included in S98 profiles.
Modified "LiteGX-KERNEL_full_cleaner.zip" to proper remove new "S98" profiles.
01.10.2013 : v4.4.4 released.
zRam is now disabled by default (to stay as stock as possible).
zRam : set default to 4 devices instead of 1 (resulting Turbo zRam app compatibility from @rlorange).
Removed all zRam scripts to create some new with 4x zRam swaps instead of single ones. Should be MUCH smoother than single zRam (not a single lag detected after hard use of few hours). As always, you can flash new zRam scripts without the need to delete anything from init.d, since it will do it automatically.
Please remember that all my provided scripts are NOT necessary. They are just here for confirmed people or those who wants to increase smoothness or battery life a bit. Stock flashing will always provide best balance. Don't worry, this kernel will always stays like I wanted to do it : a "flash-and-play" one firstly.
29.09.2013 : v4.4.3 released.
Changed default zRam swappiness value from 90% to 80%.
Restored Boeffla Sound v1.6.4 original work with saturation prevention, since it was useless to remove it (just select "Over-saturation Supress" in "Graphical Equalizer" in Boeffla Sound app).
29.09.2013 : v4.4.2 released.
Changed default zRam disksize and swappiness values from 200MB / 10% to 600MB / 90% (thanks to @Yank555 for the tips).
Added 3 new zRam scripts with 90% swappiness.
29.09.2013 : v4.4.1 released.
Updated compilation toolchain Linaro GCC from 13.08 to 13.09 (20130903).
27.09.2013 : some changement about scripts.
All "ZZMoove profiles" has been removed from post #1. You can grab now them directly at top of post #2.
Added several zRam profiles (300/600/800 MB disksize, and 80/100% swappiness) scripts.
Added a full cleaner ZIP for those who want to remove cleanly everything from this kernel and want to migrate to another one.
27.09.2013 : v4.4.0 released.
Introducing zRam (with stock values for the moment). Should increase performance. Use zRam & Swap Control (made by @rlorange) to set your values and make init.d scripts like you want; or directly use my scripts HERE.
zRam : added LZ4 compression and using it as default.
Activated native ExFAT support.
Now using "make mrproper" (instead of "make clean") to stay with local number #1 (thanks @googy_anas for the tips).
22.09.2013 : v4.3.5 released.
ipv4: save CPU cycles from "check_leaf()" (backport from linux 3.8) (thx @googy_anas).
22.09.2013 : v4.3.4 released.
Fixed Boeffla Sound saturation prevention which wasn't removed since v4.0.0 (sorry about this, just saw it).
21.09.2013 : v4.3.3 released.
Hotfix from v4.3.2 : added spica1234's missing line tweak about "persistent TRIM support".
21.09.2013 : v4.3.2 released.
Enabled persistent TRIM support for all partitions (credits to @spica1234).
Added automatic dalvik-cache wiping in kernel flashing procedure.
20.09.2013 : v4.3.1 released.
Updated "Touch-to-Wake" from 1.1 to v1.1a again.
18.09.2013 : v4.3.0 released.
Updated "Dynamic FSync control" from v1.1 to v1.2 again.
NTFS support.
NFS support again.
CIFS support again.
sched: LOAD_FREQ tweak (this time definitely) removed.
18.09.2013 : v4.2.0 released.
Fixed "Dynamic FSync control" which was not working ("dyn_sync_cntrl.c" file was missing).
CONFIG_SCHED_AUTOGROUP enabled again (smoothness should be back).
Added again : Intelli memory writeback (0 when screen ON & 500ms when screen off).
Added again : sched: LOAD_FREQ (4*HZ+122) avoids loadavg Moire.
Touch-to-Wake back from v1.1a to v1.1 for the moment.
15.09.2013 : v4.1.0 released.
Updated compilation toolchain to Linaro GCC 4.7 from 20130626 to 20130812.
USB charging increased back to 900mA (instead of 475 by default).
15.09.2013 : v4.0.0 released.
Total beginning from zero (clean update11 sources) again.
"Android OS" battery drain on top is now gone.
Kernel is now cleaner than before : almost everything has been made using git patches, and minimally manually.
Litest release ever (5,42 MB), smoothest and best battery friendly release ever too.
Releases will now be "x.x.x" (latest number for minor fixes/tweaks, the middle one for good ones, and the first one for major ones).
Removed a lot of tweaks since v3.6, which was useless or that I don't want to include anymore to stay as close as possible from stock. I prefered to let only important and relevant tweaks for now.
List of modified features :
CIFS / NFS support removed.
Intelli memory writeback removed.
AIO tweak: No plug I/O queue in "do_io_submit()" removed.
CONFIG_SCHED_AUTOGROUP is now disabled.
sched: LOAD_FREQ (4*HZ+122) avoids loadavg Moire removed.
Reverted USB charging from 900mA back to 475mA default value.
Reverted "Dynamic FSync control" from v1.2 to v1.1 from AndiP.
List of added feature :
ARM CPU Topology : many patches has been included about optimizations/fixes.
Thanks & greetings
★ THANKS & GREETINGS ★ :
XDA board and community
Google
Samsung
CyanogenMod Team
gokhanmoral
Andreilux
wanam
spica1234
ZaneZam
Yank555
googy_anas
hardcore
AndiP
DONATIONS
★ DONATIONS ★ :
Many thanks to @fuxmen ! :good:
Many thanks to @colingpt ! :good:
Thank you to support my work !
Thanks bro tested ( Pardus HD Rom MG6 v18 )
downloading and nandorid backing up
does the setting Stweak compatible ?
qtwrk said:
does the setting Stweak compatible ?
Click to expand...
Click to collapse
Sorry, no STweaks support for the moment, but planning to do it. Need to learn how to add the compatibility. Stay tuned.
Envoyé depuis un téléphone qui pique les yeux.
Great work. The S3 community is getting richer with you aboard congratulations!
UPDATE
UPDATE :
16.08.2013 : v1.1 released.
ramdisk from XXEMF6.
Note : If you have a message before reboot in your recovery asking you to disable stock recovery flash, click yes to keep your custom recovery. I guess it's due to XXEMF6 ramdisk on which included a stock recovery flashing procedure with.
googy_anas said:
Great work. The S3 community is getting richer with you aboard congratulations!
Click to expand...
Click to collapse
Thank you mate, XDA is proud to have such great devs like you, and sharing to us kernels of your quality is such a chance that only a few people will understand this on this board :good:
My goal is to stay as stock as possible, so.. sorry but no competition with mine ! :laugh:
Cheers from France
UPDATE
UPDATE :
18.08.2013 : v1.2 released.
Linux kernel branch from 3.0.91 (kernel.org).
Enjoy :good:
This kernel is amazing
I flashed it.
Will be kernel compiled with Linaro Toolchain?
Assa551N said:
This kernel is amazing
I flashed it.
Will be kernel compiled with Linaro Toolchain?
Click to expand...
Click to collapse
Glad you like it
Yeah, I will compile it using linaro toolchain soon (already tried but had some errors when compiling resulting an abort. Need to learn a bit more flags configuration for compiling, hehe) :good:
Stay tuned!
Androidgx nice work.
For linaro 4.6 and above you will require this patch https://github.com/AndreiLux/Perseus-S3/commit/71f536fb9957c64cc6274221faa056694e010616
After this you're good to go with Linaro toolchain
Sent from my GT-I9300 using xda app-developers app
spica1234 said:
Androidgx nice work.
For linaro 4.6 and above you will require this patch https://github.com/AndreiLux/Perseus-S3/commit/71f536fb9957c64cc6274221faa056694e010616
After this you're good to go with Linaro toolchain
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks mate :good:
You write at the good moment, was currently trying to compile and learning how to compile right without errors using linaro gcc 4.7
I stay you tuned!
Androidgx,
This is the simple fsync which I wrote in 2012 which turns fsync on untill phone is booted and later after ,it"s booted it turns off fsync.
Plus the code has been optimized with branch prediction feature of cortexa-9 cpu by gcc accembly code and it does use cortex-a9 's preload engine (prefetch) to keep fsync state in L2 cache. Plus by branch prediction there is a less cpu overhead checking about whether fsync is on or off. It assumes fsync is off and with probable branch prediction it executes faster.
Below is the fsync as a patch which I wrote in mid 2012 for my older phone. You can use it .The basic fsync functional code is based on alrahi's code.
Simple Fsunc patch is here: http://db.tt/rdikFoKY
Sent from my GT-I9300 using xda app-developers app
AndroidGX said:
Thanks mate :good:
You write at the good moment, was currently trying to compile and learning how to compile right without errors using linaro gcc 4.7
I stay you tuned!
Click to expand...
Click to collapse
Linaro 4.8 is out. Try it as well
Sent from my GT-I9300 using xda app-developers app
spica1234 said:
Androidgx,
This is the simple fsync which I wrote in 2012 which turns fsync on untill phone is booted and later after ,it"s booted it turns off fsync.
Plus the code has been optimized with branch prediction feature of cortexa-9 cpu by gcc accembly code and it does use cortex-a9 's preload engine (prefetch) to keep fsync state in L2 cache. Plus by branch prediction there is a less cpu overhead checking about whether fsync is on or off. It assumes fsync is off and with probable branch prediction it executes faster.
Below is the fsync as a patch which I wrote in mid 2012 for my older phone. You can use it .The basic fsync functional code is based on alrahi's code.
Simple Fsunc patch is here: http://db.tt/rdikFoKY
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thank tou very much mate, will try it tomorrow :good:
Just tried compiling with your link "Toolchain fixes regarding smc architecture extensions", and managed to almost compile the kernel without "-Werror" flag removed.
Here is where it stops :
Code:
CC drivers/video/samsung/mdnie_tunning.o
CC drivers/video/samsung/s3cfb_s6e8aa0.o
CC drivers/video/samsung/smart_dimming.o
CC drivers/video/samsung/s5p_dsim_lowlevel.o
CC drivers/video/samsung/s5p-dsim.o
LD drivers/video/samsung/built-in.o
CC drivers/video/samsung_extdisp/s3cfb_extdsp_main.o
CC drivers/video/samsung_extdisp/s3cfb_extdsp_ops.o
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_check_var':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:181:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_set_par':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:197:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_open':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:315:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_release':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:345:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_blank':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:387:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_pan_display':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:468:30: error: called from here
In file included from drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:32:0:
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c: In function 's3cfb_extdsp_ioctl':
drivers/video/samsung_extdisp/s3cfb_extdsp.h:154:43: error: inlining failed in call to always_inline 'get_extdsp_global': function body not available
drivers/video/samsung_extdisp/s3cfb_extdsp_ops.c:491:30: error: called from here
make[3]: *** [drivers/video/samsung_extdisp/s3cfb_extdsp_ops.o] Erreur 1
make[2]: *** [drivers/video/samsung_extdisp] Erreur 2
make[1]: *** [drivers/video] Erreur 2
make: *** [drivers] Erreur 2
[B][email protected] ~/projects/kernels/LiteGX $ [/B]
Any idea ?
Maybe another flag need to be removed ?
Androidgx,
Seems like this will solve it.
Open file drivers/video/samsung_extdisp/s3cfb_extdsp.h
Now goto line 154 and remove the word "inline" before struct declaration or add "static" before inline. Save file and try to compile back
Sent from my GT-I9300 using xda app-developers app
spica1234 said:
Androidgx,
Seems like this will solve it.
Open file drivers/video/samsung_extdisp/s3cfb_extdsp.h
Now goto line 154 and remove the word "inline" before struct declaration or add "static" before inline. Save file and try to compile back
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thank you mate it worked almost perfectly after. Just faced the same problem as THIS guy before finishing compiling, followed exactly what he said (replacing the Makefile completely, and it worked, finally :laugh. I just hope it was the right way to do.
Currenty testing my fresh new kernel with linaro 4.7.4 gcc toolchain thanks to you.
Btw, about your fsync tips patch you send me, I have very poor knowledge, is this something really noticable in term of difference as stock ? I mean a good improvement over ?
Many thanks for your explanations :good:
does this kernel supports exfat sd cards ???
[KERNEL][4.1.2][10 Nov.] ★ StockGX v1.3.0 ★ <><> ... DISCONTINUED !!
{
"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"
}
WARNING : THIS KERNEL IS ONLY FOR ANDROID 4.1.2 (SAMSUNG) !
This is a pure STOCK & STABLE kernel with MINIMAL features.
If you are looking to a more featured kernel with better optimizations, check out my LiteGX kernel !
Many of you already know my LiteGX kernel, and some of you also was disapointed since it was growing in features and was less close than the beginning. I listened to them and released this kernel, much more close to stock than LiteGX version. Hope you'll enjoy this one.
It must be only flashed over an official Samsung ROM and not AOSP/AOKP !
Feel free to include my kernel to your ROMs / Threads but please don't forget to inform/ask first via PM and credit me in your original thread.
★ FEATURES (up-to-date) ★ :
Base :
Based on update11 source from Samsung (for clean work and stability).
Compiled with latest available Linaro GCC 4.7.4 (13.10 / 20131014) toolchain (with flags optimizations).
Ramdisk from XXEMD3 (for update10 ROMs compatibility without the need to change radio).
Main :
Samsung original colors (with "Black Crush Fix").
ZZMoove (v0.7d) governor added.
row (v4) scheduler added and optimized.
Native ExFAT support (from official Samsung source).
init.d support.
Wolfson Boeffla Sound (v1.6.4 drivers) compatibility.
CRT-off effect friendly (early_suspend set to 100ms).
xbox controller support.
Triangle Away support.
Various tweaks :
ROW scheduler & blk-core tweaks.
USB charging increased (to 900mA instead of 475 by default).
Allow manual brightness to 300 candela.
Reduced battery-monitor wakelock timeouts.
CONFIG_SCHED_AUTOGROUP enabled.
Network tweaks :
Reduced WiFi wakelock.
MMC : Fix the workqueue overload battery waste.
MMC : Increased timeout limits for bad sdcards.
bcmdhd : Disabled multicast on suspend.
Proportional Rate Reduction for TCP.
Logging and debugging tweaks :
Android logger disabled.
Kernel logger disabled.
Disabled kernel debugging : Samsung / sec_log / last_kmsg / touchscreen / modem / max77686 / sec_watchdog.
Disabled various debug in defconfig.
Features that will NEVER be included in this kernel :
Other LiteGX kernel tweaks & features.
Overclock / Underclock / Undervolt.
zRam
auto-root
LED control.
Charge control.
Master sequence (screen calibrated).
ABB (Adaptive Body Bias).
Any upgrade of Linux kernel 3.0.XX.
STweaks compatibility.
Dual-Boot Sammy/AOSP.
CyanogenMod compatibility.
MIUI compatibility.
etc.
★ PREREQUISITE ★ :
Any odexed or deodexed international I9300 Samsung 4.1.2 Jelly Bean ROM.
A custom recovery (CWM recommanded) to flash the kernel.
★ SOURCES ★ :
Github >> StockGX.
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate it
stars, and clicking the 'thanks' button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!
Changelog + links
★ All oldest releases can be found HERE ★
★ CHANGELOG ★ :
10.11.2013 : v1.3.0 released.
Updated compilation toolchain Linaro GCC from 13.09 to 13.10 (20131014).
09.10.2013 : v1.2.0 released.
Kernel logging (linux printk) disabled (credits to @Lord Boeffla).
litegx_defconfig : disabled some more debug.
06.10.2013 : v1.1.0 released.
Added "ZZMoove" (v0.7d) governor ("pegasusq" will stay default).
Added "row" (v4) scheduler ("cfq" will stay default).
ROW scheduler & blk-core tweaks.
CONFIG_SCHED_AUTOGROUP enabled (for a little smoothness boost).
Samsung kernel debugging features is now really removed (forgot it in previous version).
05.10.2013 : v1.0.0 released.
Check actual features.
★ THANKS & GREETINGS ★ :
To XDA board, to host this thread (official kernel link will always be here).
To all the great developers who helped me (and for their great github repos).
To @ZaneZam (& @Yank555's help) for his great ZZMoove governor.
To @AndiP for original Boeffla Sound engine.
To @AndreiLux for his Black Crush Fix.
To Samsung for the source code.
To the whole XDA community and all the others developers who has always inspired me.
Just tell me if I missed someone :good:
DONATIONS
★ DONATIONS ★ :
None yet ! :[
hello sir, can you please make early suspend values for CRT OFF Effect Configurable via Trickster Mod App, as i want to set it to 0ms.
thanks for your work, I was looking for a kernel like this. I understand the purpose of this kernel, but do you think it would get your kernel too far from stock if you include row and, maybe, optional zram?
I'm a fan of gx kernel. I'm trying this now.
Suggestions:
- please add mdnie for better readability
- if you ever add zram and/or zzmoove, please make them default and with the best profile so that we don't have to flash profiles, that way, we can really say that it's flash-and-play.
Sent from my GT-I9300
aamirleo55 said:
hello sir, can you please make early suspend values for CRT OFF Effect Configurable via Trickster Mod App, as i want to set it to 0ms.
Click to expand...
Click to collapse
Sorry, no plan to add this. Anyway a value of 100 won't affect battery life don't worry, just ignore it
mircea89fzr said:
do you think it would get your kernel too far from stock if you include row and, maybe, optional zram?
Click to expand...
Click to collapse
- ROW scheduler : I can. I will maybe add ZZMoove governor aswell. But this time they won't be set as default for both :good:
- Optional zRam : no plan to add this, I let this feature to LiteGX kernel only
j0sefuz said:
Suggestions:
- please add mdnie for better readability
- if you ever add zram and/or zzmoove, please make them default and with the best profile so that we don't have to flash profiles, that way, we can really say that it's flash-and-play.
Click to expand...
Click to collapse
- hardcore mDNIe : no plan for this (only for LiteGX) but I included Black Crush fix for original samsung colors instead.
- zRam : same answer as above.
- ZZMoove gov : same answer as above. It will be default only in LiteGX.
Sorry, overall this kernel will stay very very lite and will almost have no more features included to stay absolutely close as stock as possible. Will keep it updated mainly for samsung sources, ramdisk (if better), and toolchains.
UPDATE
★ UPDATE ★ :
06.10.2013 : v1.1.0 released.
Added "ZZMoove" (v0.7d) governor ("pegasusq" will stay default).
Added "row" (v4) scheduler ("cfq" will stay default).
ROW scheduler & blk-core tweaks.
CONFIG_SCHED_AUTOGROUP enabled (for a little smoothness boost).
Samsung kernel debugging features is now really removed (forgot it in previous version).
Enjoy :good:
UPDATE
★ UPDATE ★ :
09.10.2013 : v1.2.0 released.
Kernel logging (linux printk) disabled (credits to @Lord Boeffla).
litegx_defconfig : disabled some more debug.
N-JoY :good:
Hi, any chance to see TRIM support enabled in this version of Kernel? Thanks!!!!
Since i have updated to the latest 1.2 version, my phone battery charges very very fast, in 45 minutes but also discharges very very fast, in half a day. Is that a bug or should i flash 1.0?
jmarcnms said:
Hi, any chance to see TRIM support enabled in this version of Kernel? Thanks!!!!
Click to expand...
Click to collapse
Nope sorry, only into LiteGX version :good:
yusufjee said:
Since i have updated to the latest 1.2 version, my phone battery charges very very fast, in 45 minutes but also discharges very very fast, in half a day. Is that a bug or should i flash 1.0?
Click to expand...
Click to collapse
It reminds me that I had same issue into some other kernels many months ago. Stock charging is not so optimized, sometimes it can charge fast and sometimes very slow, I would say it's the normal behaviour, but did you checked your wakelocks with BetterBatteryStats ? we never know..
UPDATE
★ UPDATE ★ :
10.11.2013 : v1.3.0 released.
Updated compilation toolchain Linaro GCC from 13.09 to 13.10 (20131014).
:good:
This kernel looks not interesting much people, so I prefer to discontinue it to continue only LiteGX series.
Cheers everybody! :good:
{
"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"
}
WARNING :
THIS KERNEL IS ONLY FOR THE GT-I9300 AND ANDROID 4.3 (SAMSUNG) !
This is a pure LITE, STOCK WAY & STABLE kernel with MINIMAL features.
Many of you knows my Android 4.1.2 LiteGX kernel, here is the 4.3 version !
My goal is to offer a slight modification of our Samsung stock kernel's, with few features, aiming a better battery life than stock without affecting any drain.
This is a kernel "plug-and-play" or I would say more "flash-and-play". No need for tools or apps to configure the kernel. This is the way I wanted it. A bit like speedmod kernel did.
Unfortunately, I'am not a developer but just a basic person with some android/linux knowledge already.
My dream was one day to create my own kernel, and thanks to great developers that answered my many questions, this dream has been possible. I'am very happy and proud to share my first ever kernel to everybody here.
It must be only flashed over an official Samsung ROM and not AOSP/AOKP !
Feel free to include my kernel to your ROMs / Threads but please don't forget to inform/ask first via PM and credit me in your original thread.
★ FEATURES (up-to-date) ★ :Base :
Directly based on "GT-I9300_JB_Opensource_Update13" (XXUGMK6) JellyBean Android 4.3 source from Samsung (for clean work and stability).
Compiled with stock android ARM EABI (v4.4.3) toolchain.
Ramdisk from XXUGNA7.
Main :
ZZMoove (v0.7d) governor (added). [PROFILES INCLUDED! grab them into SCRIPTS section].
smartassV2 governor (added).
Enabled all other stock governors ("adaptive", "conservative", "interactive").
ROW (v4) optimized and as only I/O scheduler.
Wolfson Boeffla Sound (v1.6.5 drivers) compatibility.
hardcore mDNIe tweaks (for better colors + sharpness fix for better readability).
Touch-to-Wake (v1.1a) (but disabled by default). [PROFILES INCLUDED! grab them into SCRIPTS section].
USB charging increased (to 900mA instead of 475 by default).
Allow manual brightness to 300 candela.
init.d support.
BusyBox v1.22.1 included in case of need (located in /sbin).
CRT-off effect friendly (early_suspend set to 100ms).
Native ExFAT support.
Native xbox controller support.
TriangleAway support.
Various tweaks :
Optimized ARM CPU topology.
"GENTLE_FAIR_SLEEPERS" disabled.
"ARCH_POWER" enabled.
"SCHED_MC" added. [PROFILES INCLUDED! grab them into SCRIPTS section].
ROW scheduler & blk-core tweaks.
"Westwood", "HTCP" and "BIC" TCP congestion control modules added. [PROFILES INCLUDED! grab them into SCRIPTS section].
Reduced WiFi wakelock.
Disabled multicast on suspend.
Proportional rate reduction for TCP.
Higher random entropy.
Doubled min-max ReadAhead.
CRC disabled.
USB OTG enabled.
"Samsung Rooting Restriction Feature" removed.
Fully compressed libs ".ko" modules.
Automatic dalvik-cache wiping in kernel flashing procedure.
Logging and debugging tweaks :
Android logger disabled.
Various debugging for certain modules.
Disabled kernel debugging : Samsung / sec_log / last_kmsg / touchscreen / modem / max77686 / sec_watchdog.
Features that will NEVER be included in this kernel :
Overclock / Underclock / Undervolt.
auto-root
LED control.
Charge control.
Master sequence (screen calibrated).
ABB (Adaptive Body Bias).
Any upgrade of Linux kernel 3.0.XX.
STweaks compatibility.
Dual-Boot Sammy/AOSP.
CyanogenMod compatibility.
MIUI compatibility.
etc.
★ PREREQUISITE ★ :
Any odexed or deodexed international I9300 Samsung 4.3 Jelly Bean ROM.
A custom recovery (CWM recommanded) to flash the kernel.
Be sure to remove any of your init.d scripts which can meet conflicts with ones I provide.
★ FREQUENTLY ASKED QUESTIONS ★ :
Do I need to flash any cleaner script before flashing this kernel ? :
> If your previous custom kernel dev provided a cleaner script, then you can flash it before flashing mine.
How can I customize this kernel ? :
> Mainly with ZZMoove/zRam profiles (grab them below) and with TricksterMOD / SetCPU apps.
What is zRam and his pros/cons ? :
> Check THIS interesting answer from @Yank555.
Which zRam script should I choose ? :
> Check THIS interesting answer still from @Yank555.
How to check if flashed zRam script is really currently in use ? :
> You can check it directly by using "cat /proc/swaps" or "free" shell commands via a terminal.
What does the LiteGX cleaner script ? :
> It deletes all ZZMoove/zRam profiles that you flashed after this kernel. So you can go in another kernel safely. It don't removes anything else since this kernel is pure stock based and don't add any files/folders that need to be deleted after. This cleaner script will be only efficient in this situation only, it does not clean anything before coming from another kernel to mine.
Do I need to wipe cache + dalvik each time I flash a new kernel version ? :
> Nope. Moreover dalvik cache is already wiped automatically during flashing procedure.
Do I really need to flash any profiles/scripts ? :
> Definitely not. It's user choice to do it.
Do I need to re-flash ZZMoove ZIP profiles each time I flash a new kernel version ? :
> Nope. It just install an init.d script, so it will be permanent until you delete files from your init.d folder or flash "Cleaner" version which will do this for you.
Do I need to remove old ZZMoove profiles manually before flashing a new profile ZIP ? :
> Nope. Each ZIP's include an automatic removal of previously used profile.
My TricksterMOD settings are losed after rebooting ! :
> I won't learn how to use this app but to make short, once you set any value (or modify anything), click the "V" icon at top right to apply new value, then press settings icon of the app (still on top right) and tick kernel parameters option to apply settings at boot.
Android OS usage is very often at top of my battery stats ! :
> Check THIS interesting thread. Moreover it looks android 4.3 source known related problem, hopefully will be solved in another next source.
My device is getting hot at load (games) or high usage ! :
> Check THIS interesting answer from @ZaneZam.
I lost my WiFi connexion ! :
> Be sure to flash an efsV2 modem (XXUGMK6+ minimum).
★ SOURCES ★ :
Github >> LiteGX.
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!
Changelog
★ All ZZMoove / zRam / Cleaner scripts can be found HERE ★★ All oldest releases can be found HERE ★
★ CHANGELOG ★ :
21.02.2014 : v5.1.0 released:
Revert back to "GT-I9300_JB_Opensource_Update13" source from Samsung (ExFAT compatibility is back).
Revert: "Brings back stock defconfig debugging" (will finally wait for next source to do that again).
Revert: "Disabled USB OTG" (not causing slow USB/AC charges).
litegx_defconfig : ANDROID_LOGGER disabled.
Force ExFAT loading as internal module.
Properly removed LZ4 compression implementation + zRam various lines in defconfig (for clean work).
15.02.2014 : v5.0.0 released:
Now based from "GT-I9300_SEA_JB_Opensource_Update2" source from Samsung.
ramdisk upgraded to XXUGNA7.
Brings back stock defconfig debugging (to be once again more close from stock source as possible).
Disabled USB OTG (was causing slow USB+AC charging).
Disabled zRam and swap support from stock new source defconfig (for best battery life experience).
Fully removed my zRam implementation + LZ4 compression.
Removed "zRam profiles" from scripts folder.
09.02.2014 : v4.8.1 released.
Added an automatic device model and android version checking into flashing procedure to avoid some (beginners) people trying to flash the kernel in any another device and/or android version.
04.02.2014 : v4.8.0 released.
Removed forced speedmod pegasusq tweaks from ramdisk (back to stock values) to prevent earphone crackles and audio stuttering when listening music (values looks a bit hard at idle resulting this problem). In case you still got the issue with this governor, just switch to another one.
Added "pegasusq profiles" into scripts folder :
- pegasusq_speedmod.zip
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new pegasusq profiles flashable ZIP (please remove old one).
01.02.2014 : v4.7.0 released.
ramdisk upgraded to XXUGNA5.
BusyBox (compiled by myself) updated to v1.22.1 (located in /sbin) with stock applets.
ramdisk : removed a lot of external applets which are now directly included in my BusyBox.
18.01.2014 : v4.6.0 released.
Added "smartassV2" governor (battery is MUCH increased with it at the cost of some lags).
Makefile: Back to stock Update13 source optimizations (I thought it was done already but I forgot it).
16.01.2014 : v4.5.0 released.
Reverted "ignore charger unstable power" previous patch (it was causing USB tethering not working anymore).
Boeffla Sound Engine updated to 1.6.5 (allows speaker volumes down to 20).
mmc/core: CRC disabled (performance should be slightly increased).
Enable USB OTG.
13.01.2014 : v4.4.0 released.
"pegasusq" governor with speedmod kernel tweaks (thanks hardcore).
ramdisk: turn OFF debugging for certain modules (thanks hardcore).
11.01.2014 : v4.3.0 released.
TriangleAway support (back).
Unstable power charging ignored (now charging much faster than before)
'pegasusq' governor is now set as default (kernel is much smoother than ever (+ no more random lags ingame/UI) with it).
Enabled all other stock governors ('adaptive', 'conservative', 'interactive') for people who wants to try them out.
Decided to re-include some of my old patches (do not ask me why ^^) :
- Reduced WiFi wakelock.
- Disabled multicast on suspend.
- Proportional rate reduction for TCP.
- Higher random entropy.
- Doubled min-max ReadAhead.
02.01.2014 : v4.2.3 released.
Disabled "CONFIG_SCHED_AUTOGROUP" (useless in Android).
02.01.2014 : v4.2.2 released.
xbox controller now loaded as internal module (instead of external).
02.01.2014 : v4.2.1 released.
Fixed ExFAT support.
01.01.2014 : v4.2.0 released.
Added hardcore mDNIe sharpness & colors tweaks. Colors profiles remains intact, so they still can be activated in display section (which was not the case in LiteGX for android 4.1.2).
Clic below to see older changelog ..
01.01.2014 : v4.1.1 released.
Removed (temporarily) Triangle Away support (incompatible with Android 4.3 yet), to avoid force close messages.
30.12.2013 : v4.1.0 released.
ramdisk upgraded to XXUGML2 (Android 4.3).
29.12.2013 : v4.0.0 released.
Now based from official Update13 XXUGMK6 source from Samsung.
Now compiled with stock Android ARM EABI 4.4.3.
Reverted: "Enabled persistent TRIM support for all partitions" tweak (since samsung already included it in Update13 now).
Touch-to-Wake is now disabled by default (for battery purpose).
Added some "Touch-to-Wake profiles" into scripts folder :
- Touch-to-Wake_disabled(stock).zip
- Touch-to-Wake_enabled_3s.zip
- Touch-to-Wake_enabled_5s.zip
- Touch-to-Wake_enabled_8s.zip
- Touch-to-Wake_enabled_10s.zip
- Touch-to-Wake_enabled_15s.zip
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new Touch-to-Wake flashable ZIP's (please remove old one).
15.12.2013 : v3.6.0 released.
Upgraded to XXUGMK6 Android 4.3 ramdisk (from official LEAK this time). In case your old modem is not working anymore, update it to THIS one.
SCHED_MC disabled back by default (0) to avoid some people facing some lags due to agressive value (moreover, I prefer to trust ZZMoove stock behaviour).
Added some "SCHED_MC profiles" into scripts folder :
- "SCHED_MC_power_savings_0(stock).zip"
- "SCHED_MC_power_savings_1.zip"
- "SCHED_MC_power_savings_2.zip"
It will be useful for those who wants to change it without the need to use TricksterMOD (etc) anymore.
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new SCHED_MC flashable ZIP's (please remove old one).
12.12.2013 : v3.5.0 released.
Upgraded to XXUGMK6 Android 4.3 ramdisk.
05.12.2013 : Flashable ZIP's adding.
Added some "TCP congestion profiles" into scripts folder :
- "TCP-congestion_bic.zip"
- "TCP-congestion_westwood.zip"
- "TCP-congestion_htcp.zip"
- "TCP-congestion_reno.zip"
- "TCP-congestion_cubic(stock).zip"
It will be useful for those who wants to change it without the need to use TricksterMOD (etc) anymore.
Updated "LiteGX-KERNEL_full_cleaner.zip" to match new TCP flashable ZIP's (please remove old one).
02.12.2013 : v3.4.0 released.
zRam is disabled as default again (this time for ever), for battery purpose at the cost of a bit less multitasking (if you want it again : just flash any zRam script).
"GENTLE_FAIR_SLEEPERS" disabled (back), should improve UI responsiveness.
Updated "zRam_disabled.zip" to match new zRam disabling as default (please delete old one).
28.11.2013 : v3.3.0 released.
zRam is now initialized by default once flashing the kernel with 600MB disksize and 100% swapiness. If you feel some lags, try different values with scripts (hope it will help people finding this kernel more smooth than default without it).
All zRam scripts has been reworked and updated (please delete olders and download latest ones). If you want to turn off zRam, this time you'll have to flash "zRam_disabled.zip" file.
zRam initialization is now using a custom busybox binary directly integrated in the kernel, it will avoid some people not having their zRam properly working due to some roms busybox which cannot execute 'swapon' shell command and with priorities.
- A little reminder : to check if your zRam is working, no more need to install Turbo zRam app, on a Terminal, write : "free" (if you see swap values, then zRam is working) or "cat /proc/swaps" (which will give you more informations on both 4 swap partitions).
- I would like to thanks personally my friend @Yank555 to help finding some zRam initialization problems.
21.11.2013 : v3.2.0 released.
Add several TCP congestion control modules :
- Westwood
- BIC
- HTCP
'cubic' TCP congestion will stay as default like stock. You can set your favorite congestion module via TricksterMOD app.
20.11.2013 : v3.1.2 released.
ramdisk : add same root helper files + modifications as v2.1.0. Hopefully it will definitely fix root losing (for some people).
20.11.2013 : v3.1.1 released.
ramdisk : add 'root helper' again to avoid losing root after flashing for some people.
19.11.2013 : v3.1.0 released.
Enabled back: Persistent TRIM support for all partitions.
Enabled back: USB charging increased (to 900mA instead of 475 by default).
18.11.2013 : v3.0.0 released.
Total redesign again from Samsung update1 (SEA) chinese source.
Removed a LOT of tweaks (back to 'stock way' for real), battery life should be much better than before.
List of removed tweaks :
- Removed: NTFS support.
- Removed: CIFS support.
- Removed: NFS support.
- Removed: Proportional Rate Reduction for TCP.
- Removed: Network speed tweak.
- Removed: Decreased touch boost frequency (from 800 to 600Mhz).
- Removed: Doubled min-max readahead.
- Removed: ipv4: save CPU cycles from "check_leaf()" (backport from Linux 3.8).
- Removed: Intelli memory writeback (0 when screen ON & 500ms when screen off).
- Removed: Higher random entropy.
- Removed: Enabled persistent TRIM support for all partitions.
- Removed: Dynamic FSync control (v1.2).
- Removed: "GENTLE_FAIR_SLEEPERS" disabled.
- Removed: USB charging increased (to 900mA instead of 475 by default).
- Removed: "cpu_load_slope" correctly set.
- Removed: bcmdhd : Disabled multicast on suspend.
- Removed: AIO enabled (backport of Linux 3.6.x) and tweaked.
- Removed: Westwood TCP congestion.
Some optimizations into litegx_defconfig.
TricksterMOD app should be compatible with the kernel (again).
Overall kernel size is now slightly lighter (again) than previous version.
17.11.2013 : v2.1.1 released.
ramdisk : Modified 'root helper tweaks' (again) to remove many useless lines, which finally now finally looks like more as an 'init.d helper'.
ramdisk : Many useless files in 'sbin' folder has been removed to let only needed ones for 'root helper tweaks'.
Overall kernel size is now slightly lighter than before.
15.11.2013 : v2.1.0 released.
Revert source back to update12 from Samsung.
Original ramdisk base from ZCUBMK2.
ARM : Neon & Hard-Float support (thanks to @googy_anas).
14.11.2013 : v2.0.0 released.
Directly based on update1 XXUGMJA SEA JellyBean Android 4.3 (chinese) source from Samsung (for clean work and stability).
litegx_defconfig : Disable 'Samsung Rooting Restriction Feature'
12.11.2013 : v1.6.3 released.
Upgraded to ZCUBMK2 Android 4.3 ramdisk.
Fixed 'init.d' support (forgot it in previous 1.6.2).
12.11.2013 : v1.6.2 released.
full ramdisk from (this time) pure stock XXUGMJ9 instead of repacked WanamLite 7.2 ROM one.
ramdisk : modified 'root helper tweaks' from adam kernel to fit the needs of LiteGX kernel only (removed build.prop and pegasusq governor tweaks).
It was already the case before but I prefer to precise it : in case you encounter the message "fix root" after flashing my kernel before rebooting from recovery, you can choose yes or not, it will be the same : you will not loose root.
11.11.2013 : v1.6.1 released.
touch_wake.c : forgot description of bump to 1.1a.
11.11.2013 : v1.6.0 preview.
Touch-to-Wake v1.1a finally implemented ! (credits to @Ezekeel & @Yank555) and enabled by default with 5 seconds delay. If you guys are unhappy with it or would like to set another value, just set it via Trickster MOD.
11.11.2013 : v1.5.2 released.
Reverted patch: "ExFAT loaded as external module" (causing ExFAT not working anymore).
11.11.2013 : v1.5.1 released.
Added one more modification to "Disable multicast on suspend" (thx to @googy_anas).
11.11.2013 : v1.5.0 released.
Samsung Rooting Restriction Feature removed (thx @googy_anas).
ExFAT loaded as external module (thx @googy_anas).
Reverted patch: "MMC: Fix the workqueue overload battery waste (cm patch)".
09.11.2013 : v1.4.0 released.
Updated compilation toolchain Linaro GCC from 13.09 to 13.10 (20131014).
09.11.2013 : v1.3.0 released.
zRam activated (but disabled by default). Use any profile to activate it (grab them into post #2).
zRam : use LZ4 compression.
zRam profiles are compatible and working same way as LiteGX 4.1.2 version.
09.11.2013 : v1.2.0 released.
Add NTFS support.
Add NFS support.
Add CIFS support.
Disabled kernel debugging : Samsung / sec_log / last_kmsg / touchscreen / modem / max77686 / sec_watchdog.
08.11.2013 : v1.1.0 released.
USB charging increased (to 900mA instead of 475 by default).
Allow manual brightness to 300 candela.
CRT-off effect support (early_suspend set to 100ms).
xbox controller support.
Native ExFAT support (from official Samsung source).
Triangle Away support.
4x zRam swaps capability (instead of single one).
Dynamic FSync control (v1.2).
Optimized ARM CPU topology.
"ARCH_POWER" enabled.
"SCHED_MC" added.
"SCHED_MC_POWER_SAVINGS" set to agressive value (2) by default.
"CONFIG_SCHED_AUTOGROUP" enabled.
ROW scheduler & blk-core tweaks.
AIO enabled (backport of Linux 3.6.x) and tweaked.
Dynamic Screen Frequency Scaling capability (for ZZMoove governor).
Intelli memory writeback (0 when screen ON & 500ms when screen off).
Enabled persistent TRIM support for all partitions.
MMC : Fix the workqueue overload battery waste.
"GENTLE_FAIR_SLEEPERS" disabled.
Higher random entropy.
Decreased touch boost frequency (from 800 to 600Mhz).
ipv4: save CPU cycles from "check_leaf()" (backport from Linux 3.8).
"cpu_load_slope" correctly set.
Doubled min-max readahead.
"Westwood" TCP congestion module enabled and set as default.
Enabled "bic" and "htcp" TCP congestion modules.
Network speed tweak.
Proportional Rate Reduction for TCP.
bcmdhd : Disabled multicast on suspend.
Android logger disabled.
Disabled various debug in defconfig.
08.11.2013 : v1.0.0 released.
Directly based on update12 source from Samsung (for clean work and stability).
Compiled with latest available Linaro GCC 4.7.4 (13.09 / 20130903) toolchain (with flags optimizations).
Ramdisk from XXUGMJ9.
ZZMoove (v0.7d) governor (added and set as default)
row (v4) optimized and as only I/O scheduler.
Wolfson Boeffla Sound (v1.6.4 drivers) compatibility.
init.d support.
Thanks & greetings
★ THANKS & GREETINGS ★ :
XDA board and community
Google
Samsung
CyanogenMod Team
gokhanmoral
AndreiLux
wanam
spica1234
ZaneZam
Yank555
googy_anas
hardcore
Lord Boeffla
DONATIONS
★ DONATIONS ★ :
Many thanks to @letmarebrmbarove ! :good:
Many thanks to @batahulu ! :good:
Many thanks to @sqlpro ! :good:
Thank you to support my work guys !
Hi,
Firstly, thank you for your hard work on this kernel.
I flashed the kernel after wiping cache and dalvik. What I noticed is that Trickster mod does not pickup all 4 cores. Only 1 core is shown. Also, frequency lock is set to On, but no frequencies are shown. No scheduler is shown either. Cpu -z shows all cores.
Other than that, everything is running smoothly so far. The wake lock issue doesn't seem to be present. I'll report back with any other issues I find.
Thank you again. I've been using your Kernels since I bought my phone and I find them to be perfect for my needs.
Edit: I'm using Gorgoid 3.2
flashing right now. thanks
EDIT: wake up bug is gone. everything seems ok for a few hours of using. next is battery life. charging right now.
Thanks, you did it faster than i expected, will flash 4.3 this weekend.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Awesome i will try it now and tonight or tomorow i will give feedback .
Hope batterylife is better than stock and the wake up bug is gone .
Thanks for your work
modded by Xposed Framework.
Thanks for your work! :good:
Waiting some feedbak from users, but for sure I will try it :highfive:
Thanks guys, glad you like it, even if it's still far than my 4.1.2 LiteGX version, still a lot of work to do!
rodlane said:
What I noticed is that Trickster mod does not pickup all 4 cores. Only 1 core is shown. Also, frequency lock is set to On, but no frequencies are shown. No scheduler is shown either. Cpu -z shows all cores.
Other than that, everything is running smoothly so far. The wake lock issue doesn't seem to be present. I'll report back with any other issues I find.
Click to expand...
Click to collapse
I can confirm this bug, looks like TricksterMOD is not well supported by 4.3 detection for the moment I guess. Try to use SetCPU for the moment which works well, and PerfMon to see behaviour of 4 cores in live, looks like all cores are working properly here :good:
F3nr1s said:
Hope batterylife is better than stock and the wake up bug is gone
Click to expand...
Click to collapse
Thanks to informing me about this bug, I wasn't aware of it, since I just migrated to 4.3 yesterday.
For the moment I never encountered this bug so far, but I'll let you know as soon as I'll face it.
I just hope official update12 source solved it, of we will have to wait for non-official dev fix, or future update13 source :cyclops:
Thank you. I'll Perfmon. I don't really play around with cpu settings much, although I do use Trickster mod to check that everything is running the way it should.
Another issue just noticed while typing this post is that my phone is heating up. Cpu-z reading is 40° C. Not sure if it's a 4.3/chrome/kernel issue. I never had this problem 4.1.2 using Chrome.
One more kernel for 4.3. This is really good!
Thanks man!
Thank you
Major update !
★ UPDATE ★ :
08.11.2013 : v1.1.0 released.
USB charging increased (to 900mA instead of 475 by default).
Allow manual brightness to 300 candela.
CRT-off effect support (early_suspend set to 100ms).
xbox controller support.
Native ExFAT support (from official Samsung source).
Triangle Away support.
4x zRam swaps capability (instead of single one).
Dynamic FSync control (v1.2).
Optimized ARM CPU topology.
"ARCH_POWER" enabled.
"SCHED_MC" added.
"SCHED_MC_POWER_SAVINGS" set to agressive value (2) by default.
"CONFIG_SCHED_AUTOGROUP" enabled.
ROW scheduler & blk-core tweaks.
AIO enabled (backport of Linux 3.6.x) and tweaked.
Dynamic Screen Frequency Scaling capability (for ZZMoove governor).
Intelli memory writeback (0 when screen ON & 500ms when screen off).
Enabled persistent TRIM support for all partitions.
MMC : Fix the workqueue overload battery waste.
"GENTLE_FAIR_SLEEPERS" disabled.
Higher random entropy.
Decreased touch boost frequency (from 800 to 600Mhz).
ipv4: save CPU cycles from "check_leaf()" (backport from Linux 3.8).
"cpu_load_slope" correctly set.
Doubled min-max readahead.
"Westwood" TCP congestion module enabled and set as default.
Enabled "bic" and "htcp" TCP congestion modules.
Network speed tweak.
Proportional Rate Reduction for TCP.
bcmdhd : Disabled multicast on suspend.
Android logger disabled.
Disabled various debug in defconfig.
Enjoy :good::good:
Still a lot of work to do to include last tweaks/features of LiteGX 4.1.2 (like zRam, touch-to-wake, etc).
Stay tuned!
Btw, I found the buggish patch who caused a freeze into samsung I9300 boot logo, it was caused by linux printk, so no kernel logging disabled for the moment.
Looks Nice
Added as always ( Pardus HD Rom Premier 4.3 ) :good:
Thank! I will try flash right now!! I Love your kernel for 4.1 , hope this version can fix bug lockscreen delay and batterylife!
Testing on Neatrom..
Enviado desde mi GT-I9300 mediante Tapatalk
You can add zzmove profiles? . thanks
raff222 said:
You can add zzmove profiles? . thanks
Click to expand...
Click to collapse
Top of 2nd post :good:
Perfect batterylife! Awesome kernel!! LOVE IT.. xD thank you @AndroidGX.
Sent from my GT-I9300 using Tapatalk 2