This thread is for all non-development discussions about the AJK kernel.
Please keep it civil and on topic!
Touchscreen Tuning process
1. Open ExTweaks
2. Select Screen tab
3. Go to "Batt Move Filter", increase it BY ONE and apply
4. Test it, if it still stutter, increase ONE STEP ONLY and apply
5. Repeat step 4 till the stutter/jitter is gone. Don't set it too high as it'll result the touchscreen capability lost
6. If "Batt Move Filter" is OK without any jitter again, connect your charger and go to "Chrg Move Filter"
7. Repeat step 4 till you satisfied and again: DON'T SET IT TOO HIGH, ONLY INCREASE TILL THE JITTER/STUTTER IS GONE
Do this at your own risk!
If you lost the touch capability caused by too high value then you will need to reset ExTweaks profile in recovery.
I can say its different for each device as the test shown:
-My S2: Batt Filter 16 & Chrg Filter 50, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My son's S2: Batt Filter 13 & Chrg Filter 46, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My daughter's S2: Batt Filter 14 & Chrg Filter 48, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
Also I've noticed for the first few minutes after booting, ajk is smooth but after say 5 or more, its just not as responsive. Ie jittery when swiping through screens, and sometimes it won't register my swipes. Touchscreen driver possibly?
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
topiratiko said:
Also I've noticed for the first few minutes after booting, ajk is smooth but after say 5 or more, its just not as responsive. Ie jittery when swiping through screens, and sometimes it won't register my swipes. Touchscreen driver possibly?
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
Click to expand...
Click to collapse
I would like to try to duplicate that on my phone, but so far I have been unable to.
Can you tell me any certain app this occurs within? Any apps running in the background that may use a lot of RAM or system resources?
Which version of CM10 are you currently running? I will load the same version for comparisons.
Later tonight I am going to be looking at some changes that were made sometime after my old Siyah 7.9 kernel to see if any of those may be responsible for some people having a somewhat laggy interface.
When I say ui, I'm strictly talking about swiping screens on nova launcher. When I swipe from far left to far right on jhatch, its all one smooth jitter free experience. On ajk, there's jitter, and sometimes I'll swipe once and it'll move over two screens! I don't wanna b THAT guy, as this seems like nitpicking, but Im just trying to provide feedback as I appreciate allvyouve done for this device. Its because of you that kernels even exist for our device as of right now lol. I'm 99% positive that his is based on 7.7 as I remember 7.8 was a bit laggy as well. If you do test, load your screens up with icons and swipe all the way left and all the way right repeatedly and you'll notice it. Also, put it to sleep for a bit then wake and do it again.
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
7/24 nightly btw
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
topiratiko said:
When I say ui, I'm strictly talking about swiping screens on nova launcher. When I swipe from far left to far right on jhatch, its all one smooth jitter free experience. On ajk, there's jitter, and sometimes I'll swipe once and it'll move over two screens! I don't wanna b THAT guy, as this seems like nitpicking, but Im just trying to provide feedback as I appreciate allvyouve done for this device. Its because of you that kernels even exist for our device as of right now lol. I'm 99% positive that his is based on 7.7 as I remember 7.8 was a bit laggy as well. If you do test, load your screens up with icons and swipe all the way left and all the way right repeatedly and you'll notice it. Also, put it to sleep for a bit then wake and do it again.
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
7/24 nightly btw
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
Click to expand...
Click to collapse
I appreciate the feedback and I realize that you are not nitpicking.
I just got CM10.1 7/25 release loaded and will try it out.
ALSO, on nova I set scrolling speed to relaxed and scroll effect none
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
Just to add into this from my perspective and to hopefully help with any troubleshooting... I flashed the ajk v3.2 several hours ago for SHOstock3 v3.0.2 Rom and have left AJ's kernel as it was, i.e. no changes in STweaks, and I'm having no issues at all. Using the SHOstock Rom as is, no other launcher.
Sent from my SAMSUNG-SGH-I777 using xda premium
I've had an experience similar to topiratiko's on both my phone (lastest CM10.1 nightly + latest SHO3 release) as well as on my wife's (SHOstock3 ~1.8.0 I think), though it's nowhere near as severe is he describes it. Jittery would be an exaggeration in my case, but on both of my phones, scrolling has a slight choppiness that reminds me of running a game without vsync - what looks like tearing when swipping homescreens, a very slightly flickering text when scrolling up and down on chrome or in the calendar, the opening and closing application animation not being 100% buttery smooth. I remember first noticing the scrolling choppiness shortly after you renamed your kernel to AJK. It may or may not have been present before then, and I can't say whether it has changed in severity at all in more recent releases.
It still happens even when locking the clock speed at 1200mhz, and it's present on either of my phones even if they have just been flashed and don't have any apps or settings changed.
It isn't anything even close to unusable but it feels a lot like the jump from ICS to Jelly Bean in terms of UI smoothness.
Still, I continue to use AJK both because jthatch still hasn't fixed (or perhaps fixed and then unfixed in later releases) the audio skipping problem present in Sammy ROMs, his wifi toggle is broken on the only release that runs on the latest SHO, and the auto-brightness gets funky sometimes (rarely) in CM10.1 and requires a reboot before it again displays the correct sensor values - none of which are problems in AJK.
Could you guys who are having issue please try the steps in the first post of this thread and see if it helps?
The only thing I am seeing so far in Nova launcher is easily fixed by normal touchscreen filter adjustments.
Step ahead of ya boss! Searched and tried that about a week ago and even with all that tuning it was the same. I also remember becoming frustrated and maxing out a few of the sliders and it didn't disable touchscreen. Do you think the touchscreen driver could b different?
Forgive if that's a dumb question.
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
topiratiko said:
Step ahead of ya boss! Searched and tried that about a week ago and even with all that tuning it was the same. I also remember becoming frustrated and maxing out a few of the sliders and it didn't disable touchscreen. Do you think the touchscreen driver could b different?
Forgive if that's a dumb question.
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
Click to expand...
Click to collapse
The touchscreen driver is indeed different, but I just compiled a test version with the previous touchscreen driver and it made no difference in smoothness on my phones.
I will send you an early copy of the next release which may hold a clue to this mystery.
Fantastic! Also, can u include previouse touchscreen driver in the test release?
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
topiratiko said:
Fantastic! Also, can u include previouse touchscreen driver in the test release?
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
Click to expand...
Click to collapse
It is in v3.5 and I will PM you the links for testing shortly.
:beer:
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
AJ Newkirk said:
It is in v3.5 and I will PM you the links for testing shortly.
Click to expand...
Click to collapse
I would like a copy as well, if it's not too much trouble.
Eckyx said:
I would like a copy as well, if it's not too much trouble.
Click to expand...
Click to collapse
PM sent.
Please give feedback after you have tested it for a while.
Thanks!
Those of you having this issue on AOSP get a chance, please load the Samsung version of the kernel and see if that behaves any differently for you.
Pmsent
Samsung Galaxy SII I777
CyanogenMod 10.1.2 RCS/AOCP ICEE
Boost 2.34 Kernel
@ AJK : what is the benefit of battery/charger move filter ? higher/lower value mean ?
@topiratiko: Do you have greenify installed ? Try it . I also had your problems before greenify. Without greenify, it could lag/jiter for around 30s to 1 minute after boot; with greenify it reduces to 5-10 seconds. I have a lot of background apps as gvphone, viber, skype, wechat, yahoo, zalo, whatsapp, line, etc. all those are greenfied now
abced123 said:
@ AJK : what is the benefit of battery/charger move filter ? higher/lower value mean ?
@topiratiko: Do you have greenify installed ? Try it . I also had your problems before greenify. Without greenify, it could lag/jiter for around 30s to 1 minute after boot; with greenify it reduces to 5-10 seconds. I have a lot of background apps as gvphone, viber, skype, wechat, yahoo, zalo, whatsapp, line, etc. all those are greenfied now
Click to expand...
Click to collapse
Higher filter value allows more touchscreen signal to be processed.
Related
the Galaxy S 1 made some huge monuments in development, i hope we can soon see these same achievements achieved on the S2. im trying to make a check list of things from the S1 that need to be done on the S2.. so ill start, please add what you think as well
* ext4 file system (from what ive heard, this is already existent in the S2, so thats a check)
*hacked camera app: ability to use the camera at 2%, and use while playing music
*audio boost: cranking up that music past what comes on board, either AudioBoost2 app, or voodoo sound app
*built in call recorder: record phonecalls right from the dialer
thats what i care about, what about anyone else?
a kernel with BLN support, CWM, rooted and with the lowest brightness level lowered a bit.
hardcore's kernel in other words
bobloblawsum said:
a kernel with BLN support, CWM, rooted and with the lowest brightness level lowered a bit.
hardcore's kernel in other words
Click to expand...
Click to collapse
theres an app for that!
its called shades or blinds or something.. i think it comes up in the market if you search brightness.. i had it on my galaxy s before i sold it to buy the s2
I've heard Samsung has included some screen adjustment settings, but I would still love the amazing stuff developed with Voodoo kernals. Ie:
- Screen colour temperature adjustment
- Screen and text sharpness improvements
- Sound control and amp
- Ext4 filesystem support
Voodoo Color
Voodoo Sound
CWM
BLN
Press power to take photo
soraxd said:
theres an app for that!
its called shades or blinds or something.. i think it comes up in the market if you search brightness.. i had it on my galaxy s before i sold it to buy the s2
Click to expand...
Click to collapse
Its called Screen Filter, its great, I use it daily on my SGSI for reading my RSS feeds in bed (when I dismiss my Tasker alarm it opens NewsRoom and turns on Screen Filter - BAM! Morning paper delivery...).
Should also work for the SGSII I would think.
I'd most like to see BLN support, call recording, and Voodoo Sound.
Voodoo Sound. But Supercurio did tweet earlier that - the Sound hardware of SGS2 is INFERIOR to that of Original SGS.
BLN , call recording. That all i need to buy it
All the rest is a plus ofc , but thats the most important for my daily use.
i'm prolly going to add BLN whenever i get the phone
hopefully some people will have proper CWM/root by then else i'll have to add that too
For the sound and screen color i'm sure sir curio will look at it but this is probably a bigger task as it require studying the current solution etc and there's no guarantee of success
bilboa1 said:
i'm prolly going to add BLN whenever i get the phone
hopefully some people will have proper CWM/root by then else i'll have to add that too
For the sound and screen color i'm sure sir curio will look at it but this is probably a bigger task as it require studying the current solution etc and there's no guarantee of success
Click to expand...
Click to collapse
Will it be possible to use BLN with the stock kernel at all? Coming from an N900, I really appreciate the notification LED. Since I'm new to Android, I'd prefer not to start hacking/replacing the kernel to get bln support.
Has anyone received their SGS2 yet and tried this?
bobloblawsum said:
the lowest brightness level lowered a bit.
Click to expand...
Click to collapse
IIRC that is defined in the framework source code (at least on most source compiled ROMs I've seen), so should be possible to tweak via APKtool...
Imitated, but NEVER duplicated!
Rock solid stability and great performance for your SGH-I777.
Features:
Full support for Kernel Screen Gestures Builder
WIFI Driver ported from SG4
New Mali V2 Video Driver
Overclocking up to 1400 MHz
Be very careful with voltage settings. UnderVolting usually causes bad things..
Slide2Wake is now automatically disabled while on a call. (Modded for less battery drain)
Native USB Tethering.
Native Wi-Fi Tethering
File systems support: Ext3/4, FAT32, NFS, CIFS, NTFS
Added tweaks to increase I/O Speed.
Added tweaks to increase CPU speed
Removed all the debuggers
Better picture quality thanks to camera tweaks
BLN without Wakelock - see STweaks BLN tab to activate.
Touch Keys Light change with the screen brightness
MMC_CAP_ERASE not present
Sound boost controls in STweaks.
Added mdnie interface and made hardcore’s sharpness tweaks optional
5 GPU FREQ Steps from 108Mhz to 520Mhz
Ultra KSM from 3.9.y kernel.
[/LIST]
Installation Instructions:
Wipe cache
Wipe dalvik
Install AJK - DO NOT REBOOT YET...
While still in recovery, go to advanced and reboot recovery
After recovery has been restarted, go into kernel specific options and Reset ExTweaks profiles
Fix permissions in recovery
Reboot and enjoy the new kernel
{
"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"
}
NoSwap - for Cooked and AT&T stock JB
MicSwap - for ShoStock3 and other ported i9100 ROMs
AOSP - for any AOSP ROM, such as CM10.2
AJK v4.9 NoSwap
Dev-Host
Goo
AJK v4.9 MicSwap
Dev-Host
Goo
AJK v4.9 AOSP
Dev-Host
Goo
NOTE: Changelog information for builds prior to v3.2 was somehow deleted while the thread was closed (at my request...) for a short while.
I will try to recover the lost changelog information and add it as I can.
Changelog:
v5.0 (in development)
Updated ROM compatibility - now works on all current ROMs
Fixed SoD when using ZZMOOVE as sleep governor
Imported the latest Samsung ramdisk files
Fixed an issue where profiles might be reset
- Any further profile issue MUST be due to a ROM or rogue app issue.
- The logs I have seen are indicating that the profile was deleted by something. Kernel is not capable of this...
v4.9
Fixed JB_Sound_Fix on Samsung based ROMs
Fixed a small profile issue
Fixed an issue with CPU grouping
Improved ROM compatibility
Misc fixes & tweaks
New battery profile
New performance profile - Highly recommended! Great performance & very good battery life!
GPIO pin definitions fixed
There's more but I forgot to write it down as I went...
v4.8
Small FileSystem tweak
Improved ROM compatibility
Disabled the boot logo for now
v4.7
Fixed various issues with CM10.1.3 RC2
Sync'd CM10.x init files with CM sources
Set ROOT to default ON for CM10.2
Updated ZZMOOVE to v0.7d
Set default profile sleep scheduler to BFQ
New Battery profile, based on ZZMOOVE v0.7d
New boot logo by Teknodad1974
v4.6
Tuned battery & performance profiles a bit
Tweaked CortexBrain
Fixed a small profile bug
Updated ZZMOOVE governor
-new ZZMOOVE governor is VERY smooth (smoothest gov I have found), uses slightly more battery than Hyper.
v4.5
Nice new boot logo by Teknodad1974
Recovery background remains plain black to make it easier to read recovery text
Fixed a small issue with recovery
Added exFAT support
Updated governors & i/o schedulers
Updated profiles
Updated Stweaks
Added the Dorimanx implementation of CPU Voltage Groups. This will let people see why some phones UV easily and some cannot UV.
v4.4
Added support for Android 4.3
Some code cleanup
Tweaked touchscreen and display to improve smoothness
v4.3
Reverted part of the frequency cleanup as it caused a slight hesitation in the UI
v4.2
Bugfix - corrected CPU frequency table
Boots & settles in much faster now
v4.1
Undervolting has been given a reprive thanks to topiratiko & samprocat
Use UV with CAUTION and expect no support when using UV
CPU frequency table has been tuned down to 6 primary frequencies for efficiency
CPU voltages have been corrected in the profiles to account for the new frequency table
Fixed mic swapping (MicSwap version only, obviously)
Due to the changes made to the CPU frequency table and the CPU voltage table,
it is CRITICAL that you follow the installation instructions exactly as outlined here.
S959G users please ask for assistance from more experienced S959G users
if you need assistance..
PLEASE do not just ignore the need for profile resets!
This version will start off slow (possibly VERY SLOW) and will speed
up as it settles in. First boot can take a LONG time. This is both normal and expected.
v4
Project "SMOOTH UI" is now complete!
You should notice better performance in every way. If not, you're doing something wrong!
Fixed poor performance on Samsung ROMs - they did not like the OOM settings in v3.9 .
Any trouble reports that do not include a logcat will be ignored.
v3.9
New boot logo by Teknodad1974
Corrected the context on the Stweaks->Screen tab
Removed BLN "blink" and "fade" options as they do not work on our phones
Added a new "AJK Tweaked" OOM profile (Stweaks->Memory tab)
Most people will see a nice improvement from the new OOM profile
Slide2wake fix should be functional now
Ad-Block is expanded & updated. This is a complete ad blocking solution now
Ad-Block can be added/removes d in Stweaks->Other
Ad-Block can be updated automatically via setting in Stweaks->Other
v3.8
AKA: THE ONE
Nightmare has been tuned and should be much more stable now
Added ZZMOOVE governor by ZaneZam (a great battery or sleep governor)
New topiratiko tuned profile
MAJOR smoothness improvements made by Project "SMOOTH UI"
Re-added Touchscreen Sensitivity setting in Stweaks
Added touchscreen revision detect button in Stweaks -> Screen
Added additional touchscreen settings for different touchscreen type
Many thanks to the testing team for working hard and relaying good
information for me to build upon. :highfive:
Special thanks to topiratiko for providing invaluable information
and letting me bug him into the wee hours of the mornings
testing new kernels. :good:
v3.2
WiFi toggle bug is a thing of the past (has been for weeks now on AJK actually...)
Slide2Wake is now disabled while you are on a call.
New Mali V2 drivers - best graphics performance on the i777.
S4 code implemented for WiFi.
I will have to populate this later as it somehow got removed while
my thread was locked for maintenance.
Some suggested reading:
A Comprehensive (but not by any means definitive) Guide to Wakelocks
Please remember that this kernel was created for my friends & family to use, and I also share it here.
You are not obligated to use it. If you do decide to use this kernel, that does not give you the right to be disrespectful.
Please report any bugs that you find, and be sure to include a last_kmsg and/or logcat...it is impossible to troubleshoot without it.
Reporting something 1 time is sufficient. If someone else has already reported it, you do not need to re-report the same bug.
Remember the 2 primary rules here on XDA are:
1) Be respectful.
2) Use the search functions - both the XDA search and Google.
If you are experiencing issues that no one else is having, then it is not the kernel at fault....
Special thanks to:
Entropy512 (CyanogenMod, kernels, much more for the community)
Gokhanmoral (Siyah Kernel)
Dorimanx (Dorimanx Kernel)
@razen_kain for all the feedback & support (to everyone here)
@mr-cook for all he does for the SGSII community
@topiratiko for his tireless testing, great feedback & support and the topiratiko profile
@4-2ndtwin for his tireless testing, great feedback & support
@samprocat for his tireless testing, great feedback and tremendous support.
And a special thanks to all the donators. Your donations are greatly appreciated!
ROM Devs:
I request that anyone who includes this kernel in a firmware release does the following out of courtesy:
1) Link to this thread
2) Clearly indicate in your firmware changelog which AJK version is included in your firmware release. This lets users identify whether a fix is present in the kernel they're using or not.
Kernel source new repo available here.
Use the "master" branch.
Compiled using the supplied linaro 12.x toolchain.
Touchscreen Tuning process
1. Open ExTweaks
2. Select Screen tab
3. Go to "Batt Move Filter", increase it BY ONE and apply
4. Test it, if it still stutter, increase ONE STEP ONLY and apply
5. Repeat step 4 till the stutter/jitter is gone. Don't set it too high as it'll result the touchscreen capability lost
6. If "Batt Move Filter" is OK without any jitter again, connect your charger and go to "Chrg Move Filter"
7. Repeat step 4 till you satisfied and again: DON'T SET IT TOO HIGH, ONLY INCREASE TILL THE JITTER/STUTTER IS GONE
Do this at your own risk!
If you lost the touch capability caused by too high value then you will need to reset ExTweaks profile in recovery.
I can say its different for each device as the test shown:
-My S2: Batt Filter 16 & Chrg Filter 50, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My son's S2: Batt Filter 13 & Chrg Filter 46, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My daughter's S2: Batt Filter 14 & Chrg Filter 48, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
A few battery saving tips:
Assuming that you are getting a decent deep sleep % and have no wakelocks, the single biggest way to improve battery life is to reduce the screen brightness.
Go into Stweaks and navigate to the Screen tab, then scroll down til you find GAMMA SHIFT and set this to -10 to -20 .. the darker the screen the better the battery life can be. As a general rule, keep the screen as dark as you can while still having it visible and functional.
Some other battery saving tips would include:
Set Stweaks->CPU->MAX NORMAL FREQUENCY to 800MHz. This works fine on my phone, but some people may need to bump this to 1000MHz for some apps.
Do not use Slide2Wake as this does increase battery consumption by 10% to 20% depending on which touchscreen your device has.
Make sure that you are using ZZMOOVE as your CPU-TUNING (SLEEP) governor as it gets the best deep sleep %.
Use Greenify to Greenify all your apps. This usually makes a noticeable difference.
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Yessssssssss I love you aj!!! Slight type on the features where it says it supports jb Mali on the second Mali it says mail
Sent from my GS4 running CM11 Kandy Kane
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Thanks aj gonna use it on jellybam 5.1.0
hi!
last time i did this "Reboot recovery and go into kernel specific options and Reset Stweaks profiles"
the phone sim-locked!?!
this will happen again??
Solaris_XD said:
hi!
last time i did this "Reboot recovery and go into kernel specific options and Reset Stweaks profiles"
the phone sim-locked!?!
this will happen again??
Click to expand...
Click to collapse
I am unsure of how a sim-lick can occur due to this.
To be on the safe side, try using the kernel without resetting the profiles. It *might* not cause any issues for you.
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
jhermit said:
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
Click to expand...
Click to collapse
Battery life has been great for the folks who have been testing this kernel for the past 4 to 6 weeks.
Remember that you may need to tweak some settings in Stweaks to get it working in a way that is good for you & your phone.
As for screenshots, try using power + vol down .
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Thanks man! Will install right away
Sent from my i777 using xda premium
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Just flashed with Slimbean RC1, so far so good.
Sent from my SGH-I777 using Tapatalk 2
AJ Newkirk said:
I am unsure of how a sim-lick can occur due to this.
To be on the safe side, try using the kernel without resetting the profiles. It *might* not cause any issues for you.
Click to expand...
Click to collapse
I ask myself the same question!!!
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
jhermit said:
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
Click to expand...
Click to collapse
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
bswann said:
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Or that :laugh:
Thanks! Will try this out.
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
122ninjas said:
Yessssssssss I love you aj!!! Slight type on the features where it says it supports jb Mali on the second Mali it says mail
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
Slight typo in the word typo...
bswann said:
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Because there is no screenshot option in the power menu...
Volume-+Power does not work.
AJ, YOU ARE THE MAN! I wanted to try JellyBam, but didn't want to give up Siyah. I was going to get set up to compile it for myself this morning....and just happened to notice that you had done it.....with STYLE too. Props!
jhermit said:
Because there is no screenshot option in the power menu...
Volume-+Power does not work.
Click to expand...
Click to collapse
It works fine here. Not sure why power + vol down wouldn't work for you.
great news!!!! now my i777 + hellybean will be perfect.!!!.
thanks!!!
Hey guys!
So from observations by @rkoby13 and myself, there seems to be a demand for regular builds of DorimanX's kernel!
This thread will serve as a place for logs, reports, and discussion relating to these unofficial builds by me.
Currently the plan is to compile v9 builds, whenever @dorimanx adds major updates or significant modifications to his source, however this may, and probably will, result in UNSTABLE AND EXPERIMENTAL RELEASES
Disclaimer:
Dori tests highly experimental commits prerelease, and if your device is damaged, wiped, or in any way negatively affected by these releases it's not the fault of Dorimanx, or me. In flashing these releases you accept full responsibility for any consequences of its use.
In this op, I'll have a log of which builds are most stable and which ones have bugs reported or major issues in code, and builds with extreme issues will be removed.
As x.39 was just released, the first build will be uploaded after the next major addition to the kernel sources, and every major change after that.
If there is a commit that I have not considered major but is important to you, either reply to the thread or pm me with a link to the commit, and I'll probably update the build to include it. In future, I may also build v8 kernels until their end of life, if many people show a desire for this
Finally, just a reminder not to post logs or reports/discuss these builds in any other thread, thanks
I'll also soon be adding my new and improved stweaks settings guide, nearly everything is covered now.
Source: http://github.com/dorimanx/dorimanx-SG2-I9100-Kernel
http://github.com/dorimanx/initramfs3
if anyone has a domain they'd like to offer to mirror I'd be glad (hint hint)
dorimanx has decided to help out with building sometimes, and he'll post here! and apparently no one reads whole op, is this big enough?
latest build by cybernetus http://www.dorimanx.ataliba.net
aaaaaand computoncio has a fileserver too now!
http://dorimanx.casoncia.org
Changelogs:
9.39
v1 - 23/8 up!
- ram value display fixed
- toggle to completely stop logcat from writing
(accidentally messed up defconfig and reset it so the kernel id is the same as usual but I renamed the zip)
v2 - 26/8 up!
-compiled with linaro 13.08 gcc 4.8.2 (tuned and optimised by dori for i9100 and his kernel)
- zzmoove updated to 0.7b
- cortex brain tuned and some bugs fixed
v3 - 27/8 up
-various driver updates, cleans and optimisations
v4 - 27/8 up
-as previous
-fix for reset profiles on boot
v5 - 29/8
-ton of pulled 3.11.y driver update
-cleaning
-more optimisations from stantrc (new dev )
-there was something else I saw but I forgot
9.40
v10 cybernetus - 9/9
- changelog
Eskriminal's New and Improved DorimanX Stweaks Guide!
Starting off, I will not be covering stock standard info such as cpu clock, voltage, or the most basic governor variables. @droidphile has a brilliant comprehensive guide to these things and more, search!
Now let's get started! This guide will be in the same order as stweaks itself, and if i miss anything that you wanted, pm me
Topic 1. Advanced/Custom Cpu Governor variables
Here will be discussed governors such as nightmare, darkness, and perhaps zzmoove (if i have time), and their variables.
Freq_step
this controls how large the step up should be when the cpu load hits either the up_threshold, or the inc_cpu_load, depending on your governor.
It is a percentage, where the percentage involved is that of the cpu clock prior to the switch.
Down_threshold/dec_cpu_load
same as up_threshold or inc_cpu_load, but in the reverse, these dictate at what load to decrease frequency
Cpu_up_rate/cpu_down_rate
these values determine how many readings of cpu load will be collected (i.e. 60% or 80%) before being compared to the inc_cpu_load or dec_cpu_load respectively
Freq_step_dec
the same as freq_step, but for decreasing frequency
Freq_step_dec_at_max_freq
identical to freq_step_dec, but while cpu is at values above freq_for_responsiveness_max
Up_sf_step/Down_sf_step
both have detailed descriptions in app from alucard
<more to come>
Topic 2. Memory Management
This tab in stweaks dictates whether Dorimanx kernel should control the Android memory management system (Auto Oom Control switch)
The settings here control how it should control it, with the more aggressive the setting, the quicker apps will be killed at low memory.
<more to come>
Topic 3. GPU Tab
The GPU settings are all identical in function to the way CPU control works, with the frequency steps available and voltage/threshold changes.
The GPU utilisation timeout controls how fast the gpu should respond to a heavy load.
With the thresholds, as with cpu the higher they are the slower it will scale frequencies up, and the faster it'll scale down.
<more details to come>
Topic 4. Screen Tab
Here all screen settings and brightness controls are changeable.
min_bl controls how fast auto-brightness should increase screen brightness level, when this value is higher the screen will stay on minimum brightness for longer.
min_gamma and max_gamma control the minimum and maximum brightness available to auto-brightness
LCD Power Reduce lowers screen brightness to save battery
Screen colour modes control colour levels
Gamma Shift changes all brightness system-wide up or down based on the value put in
FB early suspend delay controls delay after sleep should activate before running the screen off animation
Vibration force controls the power of vibrations system-wide
Slide2Wake toggles waking the device by swiping across the screen from left to right
mDNIe Negative Toggle enables or disables inverting colours by pressing the home button the number of times set below
Touch screen tweaks control sensitivity options - They're advanced, and usually don't need to be touched
Topic 5. Sound Tab
Most settings are self-explanatory, if anyone wants this actually explained, shoot me a pm.
Topic 6. Big Collection, all Misc. Kernel settings! (BLN, CRON, Logger, Auto wifi etc.)
BLN controls whether to switch on backlights when notifications are received during phone sleep.
The bln effect controls the light mode of these keys (doesn't work with BLN without wakelock)
Notification timeout controls the maximum length of time the keys should be on before turning off (doesn't work with BLN without wakelock)
LED timeout controls the timeout on backlight keys during phone use
BLNWW sets BLN to run without forcing the cpu to stay out of deep sleep, saving battery
LED fadeout controls the effect when the keys switch off
LED on touch determines whether the keys will turn on when pressed during use
LED voltage level controls the key brightness
CRON is a timed automatic service which can be used to run various optimisations and updates as detailed in the 'Other' tab in Stweaks
Fix Permissions may solve fcs in apps
Zipaligning apps may optimise them to run faster
Database optimising will clear and compact the system data, potentially increasing system performance
GPS zone changes to your local ntp server may decrease gps lock times and increase accuracy
USB settings control the device storage mount mode.
Charge current levels control speed of charging from various sources, with the higher the current, the faster the flow and therefore charge
Resetting the fuel guage chip may solve issues when battery appears to drop after reboots, as the chip will recalibrate
The Ad-blocker will block advertisements by ip in most apps
Filesystem tools attempt to recover corrupt partitions on the disk
Root settings control device root security
Cortexbrain controls the switching between various things based on screen state including cpu governor and clock, io scheduler, auto wifi, auto data, and logger control
The android logger writes logs of system errors, disable unless you plan on using this
auto data disables mobile data when the screen is off, with the delay before doing so below it (auto wifi is the same for wireless internet)
Various tweaks change system values relevant to each one
Eco tweaks modifies hotplugging logic when battery drops below the eco-level threshold to save battery by preferring use of only a single cpu core
This is just a preliminary guide, my corrupted hdd destroyed the other one I'd been writing for @rkoby13
Reserve one more! Just in case!
Sent from my GT-I9100 using XDA Premium 4 mobile app
and another at the recommendation above
Sent from my GT-I9100 using Tapatalk 2
Hehe, can't wait. This is an good idea.
Galaxy S2 powered by Dorimanx!
so what do you guys think of v8? want me to build it also?
Sent from my GT-I9100 using Tapatalk 2
Great idea
Posté via Vanilla Rootbox
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
SWTR said:
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
Click to expand...
Click to collapse
we'll see, unless many people want it it's probably not worth patching the changes in if I can
Sent from my GT-I9100 using Tapatalk 2
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
rkoby13 said:
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
Click to expand...
Click to collapse
edited op to include source and info for when downloads are up
Sent from my GT-I9100 using Tapatalk 2
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
hunkyycbz said:
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
Click to expand...
Click to collapse
any dorimanx build has gamma control in the screen tab on stweaks, raise it to increase brightness
Sent from my GT-I9100 using Tapatalk 2
I bought an optimus g for wife, but started to play with it, lock bootloader, hard to root, no custom kernel for oc. It's nice to see that s2 community it's still active.
Regarding domain, maybe ApriliaM3 from neatrom thread, he has an huge one with mods, kernels, rom.
http://d-h.st/users/ApriliaM3/?fld_id=8738#files
Galaxy S2 powered by Dorimanx!
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx....
8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
v8, for official roms. v9, custom roms.
Dorimanx put sources in git daily and build his kernel. Anyone who could and want, take his sources and make an kernel, based on his sources. So, that's what we are here on this thread, we wait to grab and test an custom kernel
Galaxy S2 powered by Dorimanx!
rkoby13 said:
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx...8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
Click to expand...
Click to collapse
dude! I totally lost my mind. Lol. I totally got confused, I know there is a version 8 of the kernel. I was thinking that this was like the "V6 Supercharger" mod that some people use. I thought there was a new version or something that was kernel based. Hahaha. Thanks for clearing that up for me bud.
Excuse my ignorance...
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
aaaaand V8.xx is official..,just like 9.xx
bugs(if any) are the same.....but 9.39 is.....<3
AIC Kernelfor LG G Pad 8.3 V500
Compatible with v500 STOCK BASED LG 4.4.2 roms ONLY! The "gamma improvement only" is available for other ROM's in the installer
This was just a private build that seems to have gained some demand to help with the v500 gamma issue. I have been running it the past week and it seems stable enough to share to other v500 users. I'm not a developer, I build and update TWRP for the Nabi tablets, have shared a few windows bat files, have a VB.net app to automate various mods to the Nabi's, and a lot of research of nvflash/APX nand formatting for the Nabi's. My only previous kernel builds were for the HP Touchpad for private use, and my Ubuntu computer. Basically taking what real developers have done and trying to make it work for my own use.
EDIT 5/11/14: I put the gamma improvement fix in just a stock kernel with no other changes, and the changes to CM11 kernel. There are 2 CM kernel version depending on which LG ROM you installed CM over to deal with the dimming issue at boot. Those are available in the new all in one installer.
Disclaimer:
Experimental. Use this at your own risk.
Please Please Please make a full backup of your tablet.
Base:
The starting source is V50020B from LG
Compiled with arm-eabi-4.7
Added features:
Initial
Improved gamma. Using default linear LUT (from 1.8-2.0 to 2.2-2.3 on my screen)
Default overclock from 1.72 to 1.78Ghz (no voltage increase)
Default underclock to 162 Mhz
Sysfs Voltage Table added for undervolting
Allow GPU to manually increase freq from 400Mhz to 487Mhz
Add GPU boost to GPU on demand governor
Add Faux Display interface (gamma control seems broken)
Add NTFS support(untested)
Add SIO Scheduler
Add FIOPS Scheduler
Optimize memcopy, string and square root functions
Add Intelliactive Governor
Download:
BETA: http://nabtabhacks.com/downloads/AICbeta2.zip Very stable but haven't got enough feedback to make it official. See changes here http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Installer for all gamma improvement kernels, tested by numerous members(AIC, stock, and CM) http://nabtabhacks.com/downloads.htm
Installer AIC Kernel: http://nabtabhacks.com/downloads.htm
Uninstaller, returns to stock 20B: http://nabtabhacks.com/downloads.htm
Install:
Reboot to recovery(TWRP)
Make a backup, just do it
Install AIC_kernel_flashable.zip
Wipe caches/dalvik if you see fit
Reboot
Source:
AIC: https://github.com/aicjofs/android_kernel_lge_v500
Stock with gamma only: https://github.com/aicjofs/android_kernel_lge_v500_stock
CM: https://github.com/aicjofs/android_kernel_lge_v500_cm
Credits
I need to give some specific acknowledgement to "oubeichen" for sharing his kernel tree, and sharing of information. Also to id10terror's install script was the easiest to use as a template.
Woohoooo, Finally some gamma correction love. Flashing now
ROM: LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted
Working much smoother with your kernel, thank you for sharing!
Tested it yesterday and it made a subtle but noticeable difference to whiteness and brightness. Thanks again
Sent from my LG-V500 using XDA Free mobile app
Am really eager to try! Thx a million times @op!
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct
Sent from my LG-V500 using XDA Free mobile app
tested with LRS ROM (stock based ) , working perfectly!
many thanks!
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
bloommax said:
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
I have been using the kernel all day and it's working great! Thanks!
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
sleekmason said:
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
Click to expand...
Click to collapse
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
vimesUK said:
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
Click to expand...
Click to collapse
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
Have you looked at the install script I use for the 510? You have the ability to change ramdisk files on the fly using sed (easiest language I could find), by opening the device ramdisk, insert one liner, close ramdisk, combine into boot.IMG.
I have a couple of simple changes for allowing tethering, and values that I couldn't make without it! This part of it may work for you!
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
I kept auto brightness disabled. It does not work well for 4.4.2. You may replicate the brightness issue with the following procedure: 1) reboot the tablet; 2) when adjusting the brightness slider, you will find 0% is very (too) bright, and the entire range is high; 3) after sleeping and waking, the brightness is much dimmer, and the entire range from 0% to 100% is lower in brightness. It seems a procedure during wake modified the range of brightness settings.
Sent from my LG-V500 using Tapatalk
Run with stock kernel 20B. I will test urs by now
Well after having to do a complete reinstall due to another issue, I tried this kernel. Man I've only used it for a few hours but color me highly impressed :good: My gamma is almost perfect and it seems noticeably faster and smoother.
Really great job and thanks.
How is the battery life?
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
In my ignorance I was not aware of what could implicate the brightness values and range on this tablet. Having only just bought it, and upgraded to KK right away, I was not aware of how JB performed, in that respect. Prior to your kernel I was using the Screen Adjuster app as a sort of fix to compensate for the comparative (to my other tablets and phones) lackluster screen performance of the tablet. With the SlimKat ROM I was experiencing, but might have overcome them, some dimming issues which I did not understand.
Since restoring the stock KK backup and using your modified kernel I no longer need the screen adjuster app and things do seem to have improved.
I'm not responsible for any damage to your device. So be advised.
Kernel Features:
-CPU Overclocked (BIG cores to 2.01GHz (experimental, i should reduce and / or disable it if too many users notify instability in F5122 (that is my personal device));
-AdrenoBoost;
-Slimbus (Audio bridge) Overclocking;
-WCD9335 HiFi selector and tunnings louder audio at kernel side;
-WSA8810 tunnings for better and louder audio in speaker;
-CRC disabled;
-DTS Eagle sound integration;
-300 Hz instead 1 kHz for kernel timer (saves power);
-Boeffla Wakelock blocker;
-Quick charge tweaks (2100mA constant charging for QC 2.0 / 3.0 enabled chargers, drawing about 1,6 Amps from wall PSU);
-Tunned voltage regulators for CPU and GPU enabling High Power Mode;
-Kernel general optimizations;
-WIP: add klapse and kcal;
-Enable 160 MHz clock in crypto engine for faster crypto operations.
Special thanks to:
@stefanhh0 github user (idk what is the nick here, please, pm me and i add it if you want) for keeping a source with newer mainline (i guess) patches;
@franciscofranco for many commits that help us improving performance and saving power;
Sony AOSP team;
And others that maybe i forgot to tag here but all them are in the github code below:
https://github.com/LuizPauloDamaceno/kernel
Inside the zip that you can download below, you will find the initial release. You should flash it by fastboot and them reinstall magisk if you have it. Also, have two xml files that is a complementing of the audio tweaks in android side, enabling CLSH_LOHIFI mode in the audio processor and tunning volumes. From mic to headphones and speakers. The thermanager is the one that you should install it for improved thermal handle with this kernel. Dont worry, things shouldn't fry, but is not my fault if them fry. As another complemention, i've done a "userdata" partition for users who have 64 GB variants, like me. The AOSP is compilled for 32 GB i guess and we have only half of our full capacity. Flashing userdata (obviously, will erase your data partition and you will loose everything like is done in the first AOSP flashes if you dont do a back-up...) you will also have more free space
Kernel: fastboot flash boot boot.img
Userdata: fastboot flash userdata userdata.img
To copy the below files i like to use root explorer app, you can also do by adb. I'm open for suggestion of better apps too
mixer_paths.xml: copy it to /system/vendor/etc/mixer_paths.xml and change permissions to 0644 octal or rw-r-r.
thermanager.xml: copy it to /system/vendor/etc/thermanager.xml and change permissions to 0644 octal or rw-r-r.
The first versions i will not do the automated flashing because are the initial and testing releases, but if my plans goes ok for the next 15 days or in the worst case next month, i can do a twrp flasheable style to make our lives easier. For me, no random reboots, no overheating for normal use and battery stills ok. Report it your experience, i will appreciate to know! =D
https://androidfilehost.com/?fid=4349826312261806431
Hope you all enjoy this, guys!
Luiz
Download link edited.
LuizPauloDamaceno said:
Download link edited.
Click to expand...
Click to collapse
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!
Could this one be used with LineageOS 16 Custom Rom by chippa?
LOLisLIFE said:
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!
Click to expand...
Click to collapse
I've stopped oreo because I didn't see any advantages to me to keep it updating, i do this for fun and based in my use. Now i'm using pie, so, i think is fare to start a Pie project...
justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
I dont know, i dont have sure if could be used because maybe the drivers are different. If the LiOs uses 3.10 kernel then dont, you cant, because the drivers of 4.9 kernel is quite different.
justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.
ParanoidNemo said:
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.
Click to expand...
Click to collapse
Thank you for the test! I will stay in AOSP Pie for a while since i've built mine one following the sony's tutorial for now. Wainting for the results
So, who tested it the first release? Any observations? soon i will post the second release with some improvements.
I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort
Lihxor said:
I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort
Click to expand...
Click to collapse
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...
LuizPauloDamaceno said:
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...
Click to expand...
Click to collapse
Thanks for the answer. Btw, i meant that voice notes are quiet, so their volume is too low to be heard
Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.
LuizPauloDamaceno said:
Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.
Click to expand...
Click to collapse
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?
iH8Ecchi said:
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Been stuck with a lot of work and not tried yet. Will report as soon as I've time to try it.
iH8Ecchi said:
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.
LuizPauloDamaceno said:
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.
Click to expand...
Click to collapse
I did this run a year ago, haven't tested that yet. I've since switched to Lineage GSI (with Sjll's modified 4.9 kernel), and tethering/hotspot works fine.
Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.
adi_adi said:
Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.
Click to expand...
Click to collapse
Have you some random reboot or not with the aosp9 by vknecht?
ParanoidNemo said:
Have you some random reboot or not with the aosp9 by vknecht?
Click to expand...
Click to collapse
Well, random reebots still occur unfortunately, but most on demanding tasks. I'm not an expert, but I don't think this is a kernel issue.