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.
Related
i have searched and re-searched a lot of times for threads that talk about my same problem, but none of them is related to it in terms of phone, kernel or ROM, and they're all nearly 2 years old
in addition, i am new to this forum, so please don't shoot me
anyway here it is:
i've tried almost every existing method to get governors like smartassV2 and interactive (my favorites) to stick without reverting to ondemand, but none worked
i noticed this:
in the exact moment the screen is locked, something sets the governor to ondemand
in the exact moment the screen is UNlocked, the same thing (i guess) sets it to performance, then to ondemand
since i know a bit about intents and receivers, i can say this behavior is triggered by android.intent.action.SCREEN_OFF/ON intents, so there must be some system apk with a receiver for those which reacts and changes governor accordingly
right now i'm running a modded init.qcom.post_boot.sh that sets back the governor to a custom one (i.e. smartassV2) every 20 seconds, which is the only way i can get it to "stick", however i hate this method 'cause it implies there is a shell running in the background, thus stealing some (yet minimal) resources and battery, and the problem is still there
some info that might come in handy:
phone: Acer Liquid Glow E330
ROM: Glowing Liquid 1.5.2 (ICS)
kernel: Lupo's kernel V3
take a look at the logcat screenshot attached, i think i found something but i have no idea what to do
EDIT: if you can't read what's in the pic, it's saying something about a CpuGovernorService
how is it possible that nobody cares? i've given more info than anyone else on this problem people, experts, devs, anyone, say sumthin'
Maybe try tot set it with an app like trickster mod and set it on boot? Or try another ROM to see if its a system app. Sorry I dont really know the programming part..
Sent from my Galaxy Nexus using XDA Premium HD app
i'll disable my script and give it a shot, however there is no other ROM, only two existing alternatives are stock (which only has crappy ondemand) and glowing liquid by vache
EDIT: didn't work dammit
UPDATE: by raising the log level to 7 in a custom boot.img i can now see PrintK saying this:
cpu_policy->user_policy.governor name interactive, str_governor = ondemand
update_cpufreq_governor cpufreq_update_policy return = 0
as a linux user, i know that PrintK is basically the kernel talking to the user/log daemon, so i am now asking help to kernel developers for any clues about it, and maybe how to change that parameter (or whatever it is) in the kernel to get rid of ondemand
as difficult as this can be to figure out, i'm sure that this would be the end to many headaches, so anyone who knows about how linux kernels work please help me find the solution to this thing
Alright, i give up, ain't no answers here
Somebody close/delete this goddamned thread, please
Sent from my scumbag cheap phone
SuicideFlasher said:
Alright, i give up, ain't no answers here
Somebody close/delete this goddamned thread, please
Sent from my scumbag cheap phone
Click to expand...
Click to collapse
hello , i got the same E330 , stock rom but root and kernel LupoV3 , to set it at 1300 mhz and SmartassV2 , maybe try Android tuner , or some who got possibility to change CPU with screen on/off , i'll try to see ...
Vache did a release 1.6 of this Rom , and Acer too (Acer_AV044_E330_1.041.01_EMEA) you can found them at Acer-club.fr
tchao
Speedo.thc said:
hello , i got the same E330 , stock rom but root and kernel LupoV3 , i set 1300 mhz and SmartassV2 with nofrills CPU , it work well.
Vache did a release 1.6 of this Rom , and Acer too (Acer_AV044_E330_1.041.01_EMEA) you can found them at Acer-club.fr
tchao
Click to expand...
Click to collapse
If you look closely, it resets to ondemand every time the screen changes state
Sent from an utter FAIL phone
EDIT: the thing is, i do have a cpu tuner with wake/sleep profiles, i simply can't seem to have it doing its job
also i stick on stock kernel because the other ones have buffer problems with music, and i'm not sacrificing my flac files for
crappy mp3s
SuicideFlasher said:
If you look closely, it resets to ondemand every time the screen changes state
Sent from an utter FAIL phone
EDIT: the thing is, i do have a cpu tuner with wake/sleep profiles, i simply can't seem to have it doing its job
also i stick on stock kernel because the other ones have buffer problems with music, and i'm not sacrificing my flac files for
crappy mp3s
Click to expand...
Click to collapse
is it this one ? "CPU tuner (Rooted phones)" on play store , i give it a chance yesterday and it looks to do the job, more than nofrill etc .... no easy to set fine but if i see the log file 'journal' it works , i come back to "smartassV2" (wich is "virtuel" gov settings) after wake up and at enter calls ...
Speedo.thc said:
is it this one ? "CPU tuner (Rooted phones)" on play store , i give it a chance yesterday and it looks to do the job, more than nofrill etc .... no easy to set fine but if i see the log file 'journal' it works , i come back to "smartassV2" (wich is "virtuel" gov settings) after wake up and at enter calls ...
Click to expand...
Click to collapse
No, just the setcpu implementation in rom toolbox. anyway i tried that "cpu tuner" and it kept forcing the governor to ondemand despite the "normal" mode being set to interactive (and yes, "normal" was the current setting)
Sent from an utter FAIL phone
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
thanks to
@sleekmason for his tutorial
@franciscofranco for his sources and hotplug algorithm
@oubeichen for msm_kcal_ctrl port
Features:
-franco hotplug algorithm
-custom thermal throtteling
-cpu: interactive
-uv: table exposed
-faux123 gamma control
-various fixes and optimizations
changelog:
v28: 17.08.2015
-updated to newest changes
-removed synapse (flash it yourself)
-governor is conservative now
-reverted some changes to hotplug
-scheduler: noop
-updated toolchain
-livebump instead of loki
-official CM only
how to change hotplug values
the values are located in
Code:
/sys/class/misc/mako_hotplug_control/
there you have
cpufreq_unplug_limit
Code:
if frequency is higher than this cores wont be offlined for a period
max_load_counter
Code:
maximal samples counted to offline cores (higher values = longer time to offline core)
high_load_counter
Code:
- info missing yet -
load_threshold
Code:
threshold to online a core
min_time_cpu_online
Code:
minimum time a core stays online
timer
Code:
samples per second (1 = 10 samples; higher values = less samples)
brightness
If you experience brightness issues it is because you are using base 4.2.2
to avoid issues flash 4.4.2 base
you can find a flashable zip here:
http://forum.xda-developers.com/showthread.php?t=2762526
reboot or crash?
send me last_kmsg
BACKUP BOOT AND SYSTEM FIRST!
Download !!!OFFICIAL CM ONLY!!!: https://www.androidfilehost.com/?fid=24052804347795577
XDA:DevDB Information
mani.Kernel, Kernel for the LG G Pad 8.3
Contributors
ckret
Source Code: https://github.com/drbeat/kernel_lge_v500
Kernel Special Features: franco hotplug, UV table, gamma adjustment, custom thermal throtteling
Version Information
Status: Stable
Created 2015-01-23
Last Updated 2015-08-17
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Rapepini said:
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Click to expand...
Click to collapse
yes its for aosp
Cool, a new kernel ! Small question before I make the jump : what do you mean, generic touchboost not working ? Is this an issue for everyday use ?
Generic touchboost is a generic driver for boosting up the CPU in touch
Franco has this in his kernels but i couldnt make it work
So i implementend the touchboost in the existing lge touch driver
Shouldnt be an issue for usage since i am using this kernel myself as daily driver
Working great so far. Using on vanir ROM. Thanks!
How far have u overclocked it. And how does it perform
zombieryder said:
How far have u overclocked it. And how does it perform
Click to expand...
Click to collapse
Didnt overclock it
Never said i did
They pad has a quadcore with 4x1.7 GHz
No need for oc
I tried running this on the following ROM:
[ROM][v500][KK][4.4.4][LINARO/SABERMOD] AOKP [WEEKLY BUILDS][20140705]
The first issue I ran into was that the screen brightness was locked at the highest level. I have read that you need to have the 4.4.2 base when running these 4.4.4 ROMs in order for screen brightness to work. It looked to me like installing this kernel upgraded to the 4.4.4 base, which would explain why that became broken.
Is it therefore safe to assume that this kernel is only for ROMs running the 4.4.4 base and not the 4.4.2 base?
Thanks
Well, no problem with autobrightness for me, and I have switched to 4.2.2 base to avoid the dim screen at startup. Been running it for the biggest part of the day, and found no real issue for now. Good work.
As for what doesn't seem to work, I was thrilled to see the gamma option in trickster mod, and thought I would be able to calibrate my screen correcly for the first time. Sadly, it seems the changes are registered (Trickster mod says they are saved allright), but there is no evolution whatsoever : the screen stays the same (and believe me, I have tried the most extreme settings to be sure I would notice the subtlest of changes).
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
ckret said:
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
Click to expand...
Click to collapse
Well at least, the option shows up in trickster mod, so I guess you're not so far from it. Anyway, your kernel seems to run very well. Thanks!
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Cal-123 said:
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Click to expand...
Click to collapse
i am aware of the brightness problem
gamma control not yet given, since i cant find the gamma address
interactive is optimized so its selected as default in this kernel
v3 feels alot smoother
dont know if there are any issues with cabc enabled
you gotta try out and report me
Running v3 on Mahdi. Smooth so far. Will report back in a few days.
Sent from my LG-V500 using Tapatalk
I was testing v3 and brightness value is fixed and wont change for me. I'm using CM11 M8.
wind0zer said:
I was testing v3 and brightness is fixed and wont change for me. I'm using CM11 M8.
Click to expand...
Click to collapse
The brightness seems to be *the* big issue with all the kernel builds. But when mentioned to other kernel builders or porters, they don't understand the 'why' of the need for more brightness. I feel the same way...I would like to be running at 40% brightness and see everything OK, but just so I could possibly save some battery 'time'. But frankly I really don't know why - 5 or more hours is long enough in one day on a tablet for me. Seems to be enough for Oubeichen, who I think is a fine kernel analyzer or porter.
What I would like to see is what Oubeichen put into this kernel found here and which I'm running but is v3.4.xxx (can't remember! and am on a computer now):
http://forum.xda-developers.com/showpost.php?p=54153699&postcount=196
Even though this is early version kernel, I'm running it with no problems - it has about 7 or 8 Processor settings such as Progressive, Conservative...etc. and several I/O's such as Noop and all the others that are not shown on the later 3.4.0 kernels. Nice settings to have to play around with IMO.
As aicjofs said brightness is a BASE issue
If you run the kernel on the 4.4.2 base you will have no Problem
I can compile it for your 4.2.2 base but i dont just geht why you dont upgrade
Having 1000000 options isnt as good as having optimized options
If you want to know what the issue is you have to look jnto the AIC thread. He stated the difference for autobrightness on the bases
i have added a sys interface so ppl with 4.2.2 base can also use this kernel
just read first post
This kernel is just as stable as CM's which is very important to me, but it's also got a lot of improvements on top of that.
Installation instructions: flash zip from recovery. That's all.
Only flash on jewel running AOSP Lollipop ROMs with the new partition layout, though I've heard that the kernel still works (for now) with KitKat AOSP ROMs as well.
Do not download the source and try to flash it. See post 2 for download link.
Source: https://github.com/Colonel-Corn/android_kernel_htc_msm8960.git
Yeah I'm really that cheesy.
Instructions for flashing: It's pretty simple, really. No tricks. Flash it just like you would the ROM. Do it after flashing the ROM though.
Below are the basics. I'll add detail later and give credit where it's due (though that information can be found in the commits too).
Features added already
Sweep2Wake
SweepUp2Wake
Double tap to wake
Force fast charge
Voltage control (with overclock support)
MP Decision
CPU Governors
wheatley
pegasusq
intellidemand
intelliactive
lagfree
badass
smartmax
interactive
conservative
ondemand
userspace
powersave
ondemand
performance
GPU Governors
performance
ondemand
simple
interactive
conservative
IO Schedulers
noop
deadline
row
cfq
bfq
sio
fiops
zen
TCP Congestion Control
cubic
reno
Optimizations
LZ4 Compression-Decompression
-Wstrict-aliasing=3
Features on deck
Sweep2Sleep
Optimizations
Considering adding -f-strict-aliasing if the situation is all gain. Not willing to sacrifice stability or features for it.
IO Schedulers
none on deck
CPU Governors - None - Lots added already. Let me know what others you'd like to see though!
GPU Governors - None - I haven't experimented with them much myself, so give me your list.
TCP Congestion Control- None - Give me your list.
Current issues
Though the kernel is at least as stable as CM's (as as of this writing), there are some bugs in a few features.
HTC Logo feature references need to be removed as it isn't part of the touchscreen on the Jewel. Those features will never work on this device.
Not loving this S2W implementation. It's got features in the code that won't work on jewel, but it's written in such a way that I can't easily remove the extra items without breaking either the feature or the build. Would prefer to use the version implemented in Bubba kernel, but its dependent on powersuspend, which doesn't want to boot after the WiFi driver updates were made by CM.
Credits: @javelinanddart - His Frosted Kernel is great, and I'd love to get it working on Jewel. Unfortunately I can't seem to compile it from his source, so I've cherry-picked a ton of commits from him. I'm going to keep picking one commit at a time and making fixes as I go. My hope is that I'll be able to find the offending lines of code in Frosted, that Jewel doesn't like, and hopefully get those changes incorporated into Frosted. @faux123 for putting together some of the most amazing features together. Guys like him who create features and write original code are really the ones who deserve the credit. All I'm really doing is an advanced cut & paste job, then crossing my fingers and hoping like hell I can get their work to function on our device. @intervigilium - Has spent a ton of time on msm8960 kernel in particular. He seems to author more of the commits I cherry-pick than anyone else.
@captain throwback - Not sure where to begin. If it weren't for him, this device may have died a long time ago. It hasn't been his daily-driver in close to a year, but he continues to maintain the device anyway. He's also been tremendous with coming back to help users with problems. @showp1984 - Has authored tons of lines of original code and new features. @rmbq - Whose Bubba Kernel made me appreciate just how much can be done with a kernel and is 90% of the reason I started Half-Popped. He didn't just cherry-pick his way there either. His commits include some really impressive original feature code.
@everyone else in the development community - A few of my commits in the beginning did not properly maintain authorship. For that, I am very sorry. I'm still really new to this and didn't know how to, or understand the importance of, maintaining proper authorship of the work of others. While I was totally ignorant about how rude this is, and it was only a handful of commits out of hundreds, proper credit should have been given. I'd love to know how to correct this, but I honestly don't know how.
https://www.androidfilehost.com/?w=files&flid=26515
3/1 - Added MP-Decision
2/28 - Added voltage control & overclocking
This folder on AFH has been set to restricted.
goliath714 said:
This folder on AFH has been set to restricted.
Click to expand...
Click to collapse
Thanks for letting me know. It's fixed now.
New build posted.
https://www.androidfilehost.com/?fid=95916177934535260
The big change is in getting voltage control fixed. I've also added OC support.
This was compiled with SaberMod 4.8 though, which is not as good as what I've used in the past. I'll be changing it soon enough though.
Let me know if you have any trouble. All you have to do is flash the zip.
Last night I decided to adjust my kernel governor settings.
Deep sleep - 73%
384 - 19%
The remaining 8% is all over frequency-wise and is about the amount of time I spent using the phone.
Quadrant score of 6126 running BeanStalk. OC frequency 1728000 with top end voltage at 1275000. Low end voltage is set at 850000 for 384000 frequency. No reboots yet. Am considering coding the low end frequency limit to 194000 since I'm having no stability issues so far.
I'm providing this as a baseline for comparison for you and for future reference for myself. If you're having bad battery drain issues, I can post my governor configuration if you'd like.
I'm pretty proud of what I've done with this, but I'm thrilled to discover that a much more skilled developer is working on a kernel for Jewel. I can't wait until it's ready.
SELinux PERMISSIVE mode kernel
This is otherwise identical to the 3-1-2015-3 kernel.
This disables Enforcing mode (kind of obvious). With enforcing mode enabled, every app is restricted to playing in its own sandbox. In permissive mode, an app can play in its own sandbox, but also play in all of the other sandboxes too. This was only created to get around issues with installing Xposed. I wouldn't recommend running SELinux in permissive mode. You've been warned.
I'm having trouble installing this. Installing the zip, TWRP says: "Updating partition details ... ... done. Failed". I've downloaded the file a few times. There's no md5 to verify. I've also tried flashing with different ROMS, but no luck. What am I doing wrong?
7357 said:
I'm having trouble installing this. Installing the zip, TWRP says: "Updating partition details ... ... done. Failed". I've downloaded the file a few times. There's no md5 to verify. I've also tried flashing with different ROMS, but no luck. What am I doing wrong?
Click to expand...
Click to collapse
What twrp are you on? Hboot?
There won't ever be an md5 with the kernel, but I've made over 100 kernel zip files using this method and never once had a failure. I'm eager to get more info so that I can help you.
fizbanrapper said:
What twrp are you on? Hboot?
There won't ever be an md5 with the kernel, but I've made over 100 kernel zip files using this method and never once had a failure. I'm eager to get more info so that I can help you.
Click to expand...
Click to collapse
(Details in my sig) Hboot 2.10. TWRP 2.8.5.0 CPTB. S-Off. File: android_kernel_htc_msm8960-cm-11.0.zip
The reason I mention the md5 is to verify that the file didn't corrupt during download. I've never had a corrupted download, but you never know.
7357 said:
(Details in my sig) Hboot 2.10. TWRP 2.8.5.0 CPTB. S-Off. File: android_kernel_htc_msm8960-cm-11.0.zip
The reason I mention the md5 is to verify that the file didn't corrupt during download. I've never had a corrupted download, but you never know.
Click to expand...
Click to collapse
I'm perplexed. Did I post a link to a zip file with that title? How many megs is your file?
It kind of looks to me like you downloaded the whole source from post #1 as a zip somehow and are now trying flash the whole repository to your phone.
fizbanrapper said:
I'm perplexed. Did I post a link to a zip file with that title? How many megs is your file?
It kind of looks to me like you downloaded the whole source from post #1 as a zip somehow and are now trying flash the whole repository to your phone.
Click to expand...
Click to collapse
I downloaded the zip from the link in post 1. I see that the file from post 6 is different, so I'll give that one a go.
https://www.androidfilehost.com/?fid=95916177934539829
3/10/15 - PERMISSIVE
UC to 192000, OC to 1836000 - be careful with the kernel settings when OC this high. I've had no issues yet, but 1.83 vs 1.5 is not an insignificant difference.
A word of advice on the permissive kernel. Use a program that manages your SELinux policy. Set it to Enforcing, and applied upon boot. The device will start the boot process in permissive mode, which is when xposed is loading, then it will change back to Enforcing at the end of boot. There are still security concerns, but we've limited the risk to just part of the boot sequence.
No reboots with the UC last night. 68% deep sleep, and 19% at 194000. Woke right away this morning with dt2w.
Dt2w and sw2w can be disabled if you're using trickster mod. You will see a boost in battery life. Not an option for me though, since my power button is dying.
Might not have this device much longer because of it. The day will soon come when I won't be able be able to break out of a bootloop and with the simulated battery pull (hold down power button for 10 seconds).
No idea what to replace it with though. I really like the idea of having a ton of custom ROM and kernel options like with the Nexus line, but I really enjoy the challenge and learning experience that comes with compiling. It's been worth developing for Jewel because there are so few of us who are doing anything for the device, so I feel like I've actually contributed something. I see the download numbers though and realize that I'm now contributing to a very small group of people. The nexus line has no need for me as a wannabe developer though, since there are many highly skilled devs already.
I'll fix the defaults later, but the voltages for the OC frequencies are set too high. Change them to max of 1250000 and you shouldn't have any problems OC to 1836000 frequency. I OC for smoother performance with normal use. If you're overclocking and playing games, that much sustained heat could be a problem.
If there is any interest, I can easily build a kernel without the sweep and tap to wake features. This would be useful for anyone who wants to trade in those features in exchange for better battery life, but doesn't have an app on their device that can disable them.
Lol. I just found tap to wake last night. I'm such a mo mo.
Thanks for the kernel, man. Digging it so far.
fizbanrapper said:
If there is any interest, I can easily build a kernel without the sweep and tap to wake features. This would be useful for anyone who wants to trade in those features in exchange for better battery life, but doesn't have an app on their device that can disable them.
Click to expand...
Click to collapse
That would be awesome if you could make a kernel like that. I don't really use sw2w or tap to wake.
jcruz942 said:
That would be awesome if you could make a kernel like that. I don't really use sw2w or tap to wake.
Click to expand...
Click to collapse
You're in luck. I saw your post right as I was finalizing some other improvements.
https://www.androidfilehost.com/?fid=95916177934540722
I built this kernel with d2w & s2w, but they're disabled by default. Those features wont drain your battery now, unless you specifically enable them. In retrospect, that's probably what I should have done in the first place.
I've cherry-picked memory improvements, thermal improvements, and set SELinux back to enforcing. If someone wants me to make an updated permissive kernel, just ask. It takes all of a minute for me to change that setting.
I also rolled back the voltages to 1250000 on the higher OC frequencies. You can push it higher if you'd like, but not by default. Still keeping OC at 1836000 max.
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.