Related
As title.
Does anybody have some apps which can adjust RGB values for i9100 after updating to ICS ? It will be perfect if you know how to modify system parameters to adjust RGB.
I used to adopt "Soft Screen Tuner v0.8 Beta" to tweak my screen in Android2.3.5, but it doesn't support 4.0.3 system now.
I have tried the night mode of "Chainfire Pro v3.3" and it didn't work.
So does "Voodoo screen Tuner R&D dev47". It fails during the installation.
I have also tried "screen adjuster" which can be downloaded from market for free, but it didn't work well and made my phone become much slower.
The color cast almost drives me crazy!! Please tell me how to deal with it.
:crying:
Is there anyway to bypass mDNIe on the Galaxy S4?
On the Galaxy Note II with Perseus kernel, one can use STweaks to "Enable master sequence", which will ignore Samsung's profiles and instead use a color scheme that closely calibrates the display to the sRBG color space.
My understanding is that a Note II display was measured with a colorimeter and values were obtained which allowed accurate color representation when the values were input into a mDNIe matrix.
In any case, is there any way to obtain accurate color on the GS4?
I noticed that Liquid Smooth ROM has advanced settings to set the color scheme (which didn't seem to do anything) and color temperature (didn't seem to do anything.)
xdadevnube said:
Is there anyway to bypass mDNIe on the Galaxy S4?
On the Galaxy Note II with Perseus kernel, one can use STweaks to "Enable master sequence", which will ignore Samsung's profiles and instead use a color scheme that closely calibrates the display to the sRBG color space.
My understanding is that a Note II display was measured with a colorimeter and values were obtained which allowed accurate color representation when the values were input into a mDNIe matrix.
In any case, is there any way to obtain accurate color on the GS4?
I noticed that Liquid Smooth ROM has advanced settings to set the color scheme (which didn't seem to do anything) and color temperature (didn't seem to do anything.)
Click to expand...
Click to collapse
Ive seen settings for mDNIe inside the KTweaker app that comes with the KTSGS4 Kernel. Not sure if its exactly what your looking for, but its the closest thing i could find. Might want to take a look at that kernel if you haven't already.
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.
Hi there,
GyroscopeNoiseFilter (previously: JitteryGyroFixForCardboard) is a module to reduce/eliminate the noise in unstable gyroscope that are found in some phones like the Moto G 2nd gen or Huawei Ascend G7. Basically, the app does the noise smoothing that app devs do, but here this module uses a system hook to apply the noise smoothing preprocessing for all apps, but the main goal here is specifically to remove jitter, not drift (although the filters may help, but there's no sensor fusion, yet).
This is particularly interesting for virtual reality (VR) or head-tracking apps because a noisy gyroscope will produce a feeling of dizzyness and nausea, but this can also be interesting for any app using the gyroscope because the output will be a lot smoother and accurate (particularly when the phone is held still).
The module was originally wrote by Kjos and the repo lives here:
https://github.com/Kjos/XposedJitteryGyroFix
The thread that started the module is on Reddit:
https://www.reddit.com/r/GoogleCardboard/comments/335ins/fix_for_jittery_gyroscopes_such_as_moto_g
Here is the latest version of the module, v1.4 (also attached to this thread):
https://github.com/lrq3000/XposedJitteryGyroFix/releases/download/v1.4/GyroscopeNoiseFilter_v1.4.apk
The module is also available directly from the Xposed repo:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
=== DESCRIPTION ===
The gyroscope is the main sensor for head tracking / virtual reality apps.
However, it's common for phones' gyroscopes to be noisy, which in practice shows as jitter, and this can create a dizzyness feeling and nausea, particularly when standing still (the "camera" still moves around just like if you were at sea).
Android now offers "virtual" sensors, which use a method known as sensor fusion to avoid those noisy outputs by combining several sensors (usually: gyroscope, accelerometer, magnetometer).
However, it's up to each app dev to use these virtual sensors, and to implement further post-processing to smooth the sensor and reduce the noise.
This module adopts another approach: it hooks directly to the hardware gyroscope and it preprocess every outputs with smoothing filters before relaying the data to the apps.
Therefore, the noise is reduced or even eliminated of the gyroscope's output for every apps.
=== OPTIONS ===
This module currently implements a few different strategies to filter and reduce noise, which can be used complementary or alone (each option can be disabled):
1. Filter type: type of the filter that will be applied to reduce noise in the gyroscope output.
2. Filter size: the number of samples to use to compute the filtering. Usually, the bigger the filter is, the less jitter there will be but at the expense of some lag.
3. Filter optional value: value of the constant that configures some types of filters such as lowpass or additive smoothing.
4. Minimum value change threshold: prevents the phone from registering the new sensor's values if the difference to the median is smaller than the given threshold.
5. Stationary minimum value threshold: when stationary, prevents the sensor from moving if the change is below the given threshold (this is similar to min value change but here it only affects the stationary state, when you are not moving).
6. Rounding precision: round all sensor's values to the given decimal.
Options can be changed on-the-fly without having to restart the phone, and are instantly applied to the sensor, so that you can switch between this option screen and a VR app to test for the parameters that reduce the jitter the most for you.
Click to expand...
Click to collapse
I'm looking for feedback before we submit to the Xposed repo, so if you have any idea of a feature or if you spot a bug, feel free.
We are also looking for better filters, currently the best performing two types are the median filter and the one order low-pass filter, so if there's someone with some experience with noise reduction on the gyroscope (not the accelerometer), I'd be very interested to get some advices about that!
/EDIT: update v1.4.
Also, we found a great opensource app called GyroscopeExplorer (kudos to the dev) which implements all kinds of sensor fusion and with a very good documentation, so that's a great source of info to implement advanced filters, but, although they smooth the movement's noise and drifting issues, they do not fix jitter at all, so for the moment we won't implement these advanced filters. We are now focusing on supporting more apps, particularly the ones using the new Cardboard NDK API to access virtual sensors (this bypasses the usual SensorManager).
Sorry, I forgot to attach the APK directly to the thread, like it's usually done around here. That's now done.
Very interesting module.
I wonder if this would give better results when doing Photospheres with the Google Camera app.
Also, does this have any meaningful impact on cpu usage and battery draining ?
thanks!
edgrd said:
Very interesting module.
I wonder if this would give better results when doing Photospheres with the Google Camera app.
Also, does this have any meaningful impact on cpu usage and battery draining ?
thanks!
Click to expand...
Click to collapse
I never made Photospheres with the Google Camera app, but if it uses the Gyroscope and you experience some jitter, then the module should help yes.
About CPU, the module is quite light on resources. The exact usage mostly depends on the filter type and filter size, with the low-pass filter being the lightest on CPU (only a few additions and multiplications, so it's negligible). All the other options such as the "minimum value change" only do a single calculation so their CPU usage is also negligible. However, if you use the mean or median filters and with a big filter size (like 1000), you may notice a very very small CPU usage, but it will still be very low (the time of a summation over an array of the size you specified, so it's not that big).
I have experienced some small (but still perceived) input lag using the default filter (median), switching to the lightest one and decreasing filter size to 8 fixed it
Would be nice if this module was presented more as an improvement / upgrade to the default gyroscope output, other than a simple fix
And after the app matures a little bit, you could make it available on the Play store too, so more people get this benefit
thanks again :good:
Good idea, but I can’t make head or tail of it. Maybe you ought to include simple preset/config… (sophisticated, uniform, simple & powerful, extreme…etc.), so that punters with Cardboards don’t spend a week scratching their heads on figuring out values, stationary thresholds and precisions.
I get nauseous using both DK2 and smartphone HMDs - don’t know if it’s me or noisy gyroscopes.
Thank's for the feedback everyone
@edgrd: yes the median filter smoothes the gyroscope more but it adds a delay proportionally to the filter's size. The low-pass filter does not add any perceptible delay, and the filter size does not matter (it only uses the previous gyroscope's value, so the filter size is always 1. I have yet to find the calculation for a bigger low-pass filter - but it works already very well as it is).
Indeed this is more an improvement now than a fix, that's why we renamed the app now to GyroscopeNoiseFilter
@Lord Childe: thank's for the idea of presets, I thought about that but however I can't think of a way to provide presets, since the values you set entirely depends on your own gyroscope's values. So for the moment, it is advised to just try out different values and you can switch back and forth to a VR app of your choice to instantly see the effect. Maybe we could do some kind of automatic calibration (eg, don't move your smartphone for a few seconds and this will automatically detect the values of the jitter).
Personally, on my Huawei Ascend G7, I use the low-pass filter and the stationary minimum value change set at 0.2. All the others are at default. And yes, this helps greatly to reduce the nausea for me (because when the phone still moves while you are standing still, this produces a feeling similar to being sea-sick).
Does not work on Cyanogenmod 12.1 Moto G 2nd Gen
Hi folks,
Tried to get it working on my Moto G 2nd Gen running Cyanogenmod 12.1. I can set the values but the Google Cardboard app does not seem to be taking the filtered values.
I tried running the Gyroscope Explorer app and if I enable Mean Smoothing, the app (Gyroscope Explorer) shows smooth values. But still has no effect on the cardboard app.
arindammanidas said:
Tried to get it working on my Moto G 2nd Gen running Cyanogenmod 12.1. I can set the values but the Google Cardboard app does not seem to be taking the filtered values.
Click to expand...
Click to collapse
Yes indeed, this is the issue we are currently working on. It seems that there are currently two ways to get the head's position: using SensorManager/SystemSensorManager, or using the Cardboard SDK's own method. The latter seems to completely bypass the SensorManager, which is the usual way of accessing the gyroscope's values. Most cardboard's apps are still using the SensorManager to access the gyroscope, so for these apps, our module works correctly. But for newer cardboard's apps using the Cardboard SDK orientation provider, our module does not work.
This is a pretty tough problem, and I never developped a Cardboard's app. If someone with experience with developping a Cardboard app can give some help with some advices, this would really help us a lot!
We just updated the module, Arindammanidas. Please try the latest version (v1.5) and see if this fixes your issue:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
https://github.com/lrq3000/XposedJitteryGyroFix/releases/tag/v1.5
If it doesn't fix your issue, please tell us what app and what version doesn't work with our module. We are aware that there are still a few apps that may not work, in particular Cmoar Cinema Pro v4.3 (but version Free is OK). We don't yet know why (the source is closed).
/EDIT: we narrowed down the issue, and it seems that only apps using Unity3d along with the Durovis Dive SDK for head tracking are not supported. It seems it's because they use their own native library to manipulate the sensors, so I'm not sure we can do anything about these apps...
I just uninstalled Xposed! I'll flash it back and report! Thanks a lot.
lrq3000 said:
We just updated the module, Arindammanidas. Please try the latest version (v1.5) and see if this fixes your issue:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
https://github.com/lrq3000/XposedJitteryGyroFix/releases/tag/v1.5
If it doesn't fix your issue, please tell us what app and what version doesn't work with our module. We are aware that there are still a few apps that may not work, in particular Cmoar Cinema Pro v4.3 (but version Free is OK). We don't yet know why (the source is closed).
Click to expand...
Click to collapse
Hi, I tried out version 1.5 and it still gives me jitters in the google cardboard app demos. Probably the cardboard app is reading from somewhere else?
Which google cardboard app? Do you mean the treasurehunt? Normally, treasurehunt is supported. Is it another app you are talking about?
lrq3000 said:
Which google cardboard app? Do you mean the treasurehunt? Normally, treasurehunt is supported. Is it another app you are talking about?
Click to expand...
Click to collapse
I was talking about the demos on the cardboard app itself. When you open the Google Cardboard app, you have an option for some demos e.g. Windy Day, Google Earth etc.
These still have jitters.
You're correct, I totally forgot about those demo apps and I didn't try them. We will see what we can do. Thank you for the feedback.
Is there any way to reduce drift when using photosphere or taking panorama photographs in Google camera?
Hello, I have a 'lenovo k3 note "with android 5.0.1, this phone has no physical gyroscope, makes a software simulation using other sensors.
I've been playing some value to your program and seems to improve a bit, but keeps moving image when this stop.
I can change the way you treat the sensor data? Even without one hardware.
Moto G 2014
For those with a Moto G 2nd generation, what are your settings?
Dear developers.
Is it possible to put an inversion of some of the axes in this module?
Some Chinese smartphones (for example ZOPO ZP998, iOcean x8), the gyroscope's axis is inverted, and the manufacturer ignores requests to fix it.
AKSU78 said:
Dear developers.
Is it possible to put an inversion of some of the axes in this module?
Some Chinese smartphones (for example ZOPO ZP998, iOcean x8), the gyroscope's axis is inverted, and the manufacturer ignores requests to fix it.
Click to expand...
Click to collapse
Wow, I was about to post the same because I was impressed someone managed to change gyroscope values. Yes, I have the same problem, my spanish smartphone comes with the X axis inverted, so the sensor fusion makes strange things (gyroscope and magnetometer/accelerometer read oppossite values), although I think this could be another app instead of adding it to your noise filter one (because in my phone there's no jittery, only a changed axis. It could be solved by the developers, but at this time there's no patch).
Thanks a lot!