Link to original thread so that can be up-to-date with the latest updates for this module: http://forum.xda-developers.com/showthread.php?t=1053587
Thanks to owain94 for reminding me!
Originally posted by doixanh...
Rom cookers: if you include this module in your ROM, please make a link to this post in your release post, so your users can know how to work with it and update the module themselves
Intro
Perhaps all of you know that all of our custom ROMs are laggy. It lags every 5 to 7 seconds. Fps2d clearly shows that.
dmesg shows that also:
So what to do? It seems that the stock driver is buggy.
I've been working with those stupid lags for some days, and now, here it is my friends No more stupid MDDI lags
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Release history
April 28 v001. Release for x10 mini pro. Need more test.
Source will be provided soon (tomorrow) at github : https://github.com/doixanh/X8Features
Requirements
- Rooted
- Latest baseband (xxx015)
- Some basic knowledge
Instruction for manual installation:
- Remount /system as rw, either with adb or with root explorer
- Download attached file, unzip, push x8mddi.ko to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
Code:
insmod /system/lib/modules/x8mddi.ko # fix mddi lags
- Push modified hw_config.sh back to your phone, reboot
xRecovery updates:
There are many ROMs and many modules right now. I will not be able to maintain update.zip. You have to follow manual installation above.
X10 mini pro : I've just uploaded a x10 mini version. Test it carefully by manually type insmod /system/lib/modules/x8mddi.ko before applying to hw_config.sh, otherwise you may get boot loop!
Bug reports
When you report a bug please attach the following files:
- /system/etc/hw_config.sh
- A copy of logcat (you can use adb logcat > logcat-bug.txt)
- A copy of live dmesg (you can use adb shell cat /proc/kmsg > dmesg-bug.txt as soon as the device is ready)
Zip 3 files above and attach in to your post. Thanks.
Disclaimer
I'm not responsible if this module damages your lovely phone. Use it at your own risk!
X10 Mini Pro: http://forum.xda-developers.com/attachment.php?attachmentid=580654&d=1303993333
__________________
If you like my post, click the
button!!
Added to my tweaks, it's stable
"The integration of MDDI is said to enable the adoption of advanced features, such as high-definition (QVGA) LCDs and high-resolution megapixel cameras for wireless devices, and supports capabilities such as driving an external display or a video projector from a handset." Wikipedia
So we can expect that the camera is going to work?
Need help
D4rKn3sSyS said:
Added to my tweaks, it's stable
Click to expand...
Click to collapse
@D4rKn3sSyS can you please make update.zip for above mentioned MDDI please..
for mini pro.......and give us link so we can check dat out......
that kid death214 really annoys me posted each module doixanh do he know we got the x8 forum ourselfs and that we have eyes?
although doixanh nice ****ign work! and death214 no thanks for the ****ing ugly annoying repost!
owain94 said:
that kid death214 really annoys me posted each module doixanh do he know we got the x8 forum ourselfs and that we have eyes?
although doixanh nice ****ign work! and death214 no thanks for the ****ing ugly annoying repost!
Click to expand...
Click to collapse
Lol owain xD... yeah thats annoying, but well i think he's trying to help.
And the people who wants a update.zi, check my signature, and then click on tweaks cm6 and cmm7, i will ALLWAYS ADD DOIXANH post, to this tweaks, so i think death you should not do this post, if someone dont want tweaks, he should go to x8 forums
D4rKn3sSyS said:
Lol owain xD... yeah thats annoying, but well i think he's trying to help.
And the people who wants a update.zi, check my signature, and then click on tweaks cm6 and cmm7, i will ALLWAYS ADD DOIXANH post, to this tweaks, so i think death you should not do this post, if someone dont want tweaks, he should go to x8 forums
Click to expand...
Click to collapse
i mean it is really annoying that he doesn't link to original topic from doixanh (damn why not an easy forum name?)
just put a link here to original topic and remove download link so users here will be sure they download the last version
now dark!
**** you colombians and export your best coffee to us NOW! coz i really want an colombian coffee right now
owain94 said:
i mean it is really annoying that he doesn't link to original topic from doixanh (damn why not an easy forum name?)
just put a link here to original topic and remove download link so users here will be sure they download the last version
now dark!
**** you colombians and export your best coffee to us NOW! coz i really want an colombian coffee right now
Click to expand...
Click to collapse
Lol you won't have it , maybe if you come here, I will let you try something , but I dont care if you come back to holland with a Hearth attack! XD
NICE!
This tweak fixes that annoying lag/unresponsiveness of the touch screen that renders playing games useless or eeven scrolling through apps that you get every few seconds.
The reason I wanted to buy a new phone was due to this annoying bug, and now it has been fixed!
I love my mini pro now! & I love you too for discovering this!
awesome...thanks for the fix now no annoying unresponsive touch screen while playing games
Ur welcome guys!!
Sent from my X10 Mini using XDA Premium App
with this if multi touch is also available it would be more awesome
can i copy paste "insmod /system/lib/modules/x8mddi.ko # fix mddi lags"
or i must type it?
You can copy it, btw, you should thank original creator on X8 forum
I copied it by I still get lag, do i put it on the very first line? and someone where in the middle?
How do you add code tags?
Code:
insmod /system/lib/modules/x8mddi.ko # fix mddi lags
# hw_config.sh
# Hardware configuration file
# Version 2010-09-21, JN
# Values imported from delta: Version 2010-01-25 Mimmi.
# Vibrator configuration
dev=/sys/devices/platform/msm_pmic_vibrator
echo 2400 > $dev/voltage_mv
# lm3530 LMU configuration
dev=/sys/devices/platform/i2c-adapter/i2c-0/0-0036
echo linear > $dev/br::mapping # BL mapping method [linear exp]
echo 32768 > $dev/br::rate::up # BL ramp up rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 32768 > $dev/br::rate::down # BL ramp down rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 226 > $dev/br::limit # BL full scale brightness 255 correponds to above [0 - 255]
echo 22.5 > $dev/br::fsc # Backlight full scale value in mA [5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5]
echo 4,80,160,250 > $dev/curve::borders # Light sensor zone boundaries
echo 60,102,144,185,227 > $dev/curve::targets # BL zone targets
echo high-z > $dev/als::r1 # LS resistor, ohm. Allowed values below.
echo high-z > $dev/als::r2 # LS resistor, ohm
# [high-z 13900 9260 5560 2320 1980 1850 1630 1160 1070 1030 957 771 731 712 677]
echo 512 > $dev/als::avg-t # LS average time, ms [32, 63, 128, 256, 512, 1024, 2048, 4096]
echo i2c_pwm_als > $dev/mode # BL control modes [i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als]
# Proximity sensor configuration
dev=/sys/devices/platform/proximity-sensor/semc/proximity-sensor
echo 15 > $dev/led_on_ms # sensor LED on time in ms
echo 35 > $dev/led_off_ms # sensor LED off time in ms
# Flash LED configuration
dev=/sys/devices/platform/msm_pmic_flash_led
echo 80 > $dev/spotlight::current_ma # spotlight current
echo 4700 > $dev/spotlight::boost_mv # spotlight boost voltage
echo 480 > $dev/cmaflash::current_ma # camera flash current
echo 5000 > $dev/cmaflash::boost_mv # camera flash voltage
# Keyboard LED configuration
dev=/sys/devices/platform/msm_pmic_misc_led.0
echo 3 > $dev/als::cut-off # would be active only in ligh zone "0"
echo user_als > $dev/control::mode # user, als, user_als
echo 40 > $dev/max::current_ma # 0, 10, 20 .. 150 mA
[code]
Put the x8mddi available in first post in /system/lib/modules and paste this in your hw_config.sh:
Ray_jai said:
Code:
#fix mddi lags
insmod /system/lib/modules/x8mddi.ko
# hw_config.sh
# Hardware configuration file
# Version 2010-09-21, JN
# Values imported from delta: Version 2010-01-25 Mimmi.
# Vibrator configuration
dev=/sys/devices/platform/msm_pmic_vibrator
echo 2400 > $dev/voltage_mv
# lm3530 LMU configuration
dev=/sys/devices/platform/i2c-adapter/i2c-0/0-0036
echo linear > $dev/br::mapping # BL mapping method [linear exp]
echo 32768 > $dev/br::rate::up # BL ramp up rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 32768 > $dev/br::rate::down # BL ramp down rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 226 > $dev/br::limit # BL full scale brightness 255 correponds to above [0 - 255]
echo 22.5 > $dev/br::fsc # Backlight full scale value in mA [5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5]
echo 4,80,160,250 > $dev/curve::borders # Light sensor zone boundaries
echo 60,102,144,185,227 > $dev/curve::targets # BL zone targets
echo high-z > $dev/als::r1 # LS resistor, ohm. Allowed values below.
echo high-z > $dev/als::r2 # LS resistor, ohm
# [high-z 13900 9260 5560 2320 1980 1850 1630 1160 1070 1030 957 771 731 712 677]
echo 512 > $dev/als::avg-t # LS average time, ms [32, 63, 128, 256, 512, 1024, 2048, 4096]
echo i2c_pwm_als > $dev/mode # BL control modes [i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als]
# Proximity sensor configuration
dev=/sys/devices/platform/proximity-sensor/semc/proximity-sensor
echo 15 > $dev/led_on_ms # sensor LED on time in ms
echo 35 > $dev/led_off_ms # sensor LED off time in ms
# Flash LED configuration
dev=/sys/devices/platform/msm_pmic_flash_led
echo 80 > $dev/spotlight::current_ma # spotlight current
echo 4700 > $dev/spotlight::boost_mv # spotlight boost voltage
echo 480 > $dev/cmaflash::current_ma # camera flash current
echo 5000 > $dev/cmaflash::boost_mv # camera flash voltage
# Keyboard LED configuration
dev=/sys/devices/platform/msm_pmic_misc_led.0
echo 3 > $dev/als::cut-off # would be active only in ligh zone "0"
echo user_als > $dev/control::mode # user, als, user_als
echo 40 > $dev/max::current_ma # 0, 10, 20 .. 150 mA
[code][/QUOTE]
_________________
[SIZE=1][B]If you like my post, click the [IMG]http://media.xda-developers.com/images/thanks.jpg[/IMG] button!! :) [/SIZE][/B]
Click to expand...
Click to collapse
Some things still lag for me.
is this considered a custom rom?
http://forum.xda-developers.com/showthread.php?t=895370
That's what I'm using right now.
Ray_jai said:
Some things still lag for me.
is this considered a custom rom?
http://forum.xda-developers.com/showthread.php?t=895370
That's what I'm using right now.
Click to expand...
Click to collapse
Custom roms = Froyo and gingerbread, but that's kinda a custom rom, but 2.1 have not MDDI lag issues.. so if you have lag, its because 2.1 is SLOW
Oh, thanks for clearing that up.
D4rKn3sSyS said:
Custom roms = Froyo and gingerbread, but that's kinda a custom rom, but 2.1 have not MDDI lag issues.. so if you have lag, its because 2.1 is SLOW
Click to expand...
Click to collapse
2.1 has MDDI issues, playing games like fruit ninjam ninjump was hell, the touch screen didn't respond most of the times(atleast in my case there so many others who have similiar issue) even scrolling in some apps was not that responsive, this this module fixes this
Sent from my U20i
Related
If anyone is compiling a kernel, please unset CONFIG_UEVENT_HELPER_PATH.
It is currently set to /sbin/hotplug, which does not exist.
You might also set
echo 5 > /proc/sys/vm/laptop_mode
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
somewhere in the initramfs.
What does these settings do?
lynx2k50 said:
What does these settings do?
Click to expand...
Click to collapse
if CONFIG_UEVENT_HELPER_PATH is set, then the kernel tries to execute that helper tool every time a hotplug event occurs. Unsetting it would save a lot of forks at boot time.
Code:
echo 5 > /proc/sys/vm/laptop_mode
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
These settings delay the disk writeback, so the disk device has to wake up less often (given it goes into sleep mode ).
Ah okay so i can expect better battery life (more sleep time) and a faster booting.
Well done, thanks.
I hope some devs are going to integreate it.
OK good point to try.
Added now on my Cognition 1.07
Code:
bash-4.1# cat /etc/init.d/90laptop.sh
#!/system/bin/sh
echo 5 > /proc/sys/vm/laptop_mode
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
Code:
diff --git a/arch/arm/configs/c1_rev02_defconfig b/arch/arm/configs/c1_rev02_defconfig
index a7992c0..ccd06df 100644
--- a/arch/arm/configs/c1_rev02_defconfig
+++ b/arch/arm/configs/c1_rev02_defconfig
@@ -917,7 +917,7 @@ CONFIG_RFKILL_INPUT=y
#
# Generic Driver Options
#
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_UEVENT_HELPER_PATH=""
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
Can someone pls create a update.zip or else for the cognition rom?
Or a shirt instruction.
Sry for my englisch
from my SGS running MIUI 2.3.4
If you have the CF-Root kernel installed, you can just place this in /data/local/customboot.sh
Code:
echo 5 > /proc/sys/vm/laptop_mode
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
echo -e '\000\000\000' > /proc/sys/kernel/hotplug
saturn_de said:
If you have the CF-Root kernel installed, you can just place this in /data/local/customboot.sh
Code:
echo 5 > /proc/sys/vm/laptop_mode
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
echo -e '\000\000\000' > /proc/sys/kernel/hotplug
Click to expand...
Click to collapse
the first two might help. (does Solid State internal storage need "sleep" mode?)
but depending on when the custom script is run the last line may be useless here..
Does it only work with a CF-Kernel, i've tagraks kernel, and cant find any file in data/locel .
Greetz
saturn_de said:
These settings delay the disk writeback, so the disk device has to wake up less often (given it goes into sleep mode ).
Click to expand...
Click to collapse
It doesn't go into sleep mode since it's not a spinning disk.
(Or you could look at it as always being in sleep mode when not in use - there's no spindown/spinup phase.)
So you're not gonna see any battery benefits from that.
Added into my installation on my handset. No way to test it whether it will increase stabilty nor speed, but it does tidy thinngs up.
Ok,this is weird.Why his topic was closed?
http://forum.xda-developers.com/showthread.php?t=1382033
I noticed that his website was blocked by SOPA.Why?The download links were mediafire links,no MU.Also Android is open source,and in his ROM it wasn't any paid app by default(i mean in system/app).What's going on?Is mediafire gonna be taken down?I noticed that it barely works.But why topic closed?
The reason is, maybe link was associate with megaupload...
Sent from my Galaxy Nexus using Tapatalk
he used mediafire links...
Marius Cristian said:
Ok,this is weird.Why his topic was closed?
http://forum.xda-developers.com/showthread.php?t=1382033
I noticed that his website was blocked by SOPA.Why?The download links were mediafire links,no MU.Also Android is open source,and in his ROM it wasn't any paid app by default(i mean in system/app).What's going on?Is mediafire gonna be taken down?I noticed that it barely works.But why topic closed?
Click to expand...
Click to collapse
i tot SOPA was shelved for the moment?
Sorry if this is OT.
But I would like to share some bugs I found while using 1.1A as I didn't upgrade to 1.4 as the links were down. Can you verify whether these are faced by any of you !
1. It takes time to wake up from the lock screen. ie even after a hard key press the screen wakes up after say 3-4 secs.
2. Data connection works with flaws. 2G/3G data seems to be buggy.
3. The notification power widget and power widget doesnt work properly. ie, even if i disable/enable Data/Orientation Lock the effect is not applied. I cant even change it in settings. Only solution is a reboot.
4. Incoming call button issues. (Solved in later versions)
Other than these, the rom is pretty stable.
umm I didn't had any of those bugs in v1.1a.actually it was one of the best version because of kernel, except few graphical bugs.anyway,look on last page/page before that of the rom,pm rosuvladut and ask him to upload rom v1.4 to 4shared or another.if he doesn't have it anymore send me a pm and I will upload v1.3 for you when I get home.i personally am lazy to upgrade to v1.4 because the changes are too insignificant.you can upgrade rom manager by yourself, instead of root browser use root explorer.about super charger I don't use it so for me v1.3=v1.4
anyone knows more about why his topic was closed? we could add other download links and that's it.
Sent from my LG-P500 using Tapatalk
I checked back in dev thread to see if any of the down links where updated. Was surprised to see no post by trettet about site being down, then noticed thread was locked. Hope all is well.
tread closed? why!
Anyone know why the notifications won't stop making noise until I view them...the sound is very annoying when it doesn't stop? I only want the notification sound once. Awesome ROM btw.
Sent from my LG-P500 using Tapatalk
i was about to flash 1.4 in my phone and then... closed thread, site down... =/
i have the link for pp1.4 posted by soberspine at mediafire:
http://www.mediafire.com/?udbvyy0j1oan0gv
but i don't have the fix (phone.apk) and gapps... can someone upload it?
also, where is trettet? do you think the thread was closed by him? or a forum admin closed it?
betoqm said:
i was about to flash 1.4 in my phone and then... closed thread, site down... =/
i have the link for pp1.4 posted by soberspine at mediafire:
http://www.mediafire.com/?udbvyy0j1oan0gv
but i don't have the fix (phone.apk) and gapps... can someone upload it?
also, where is trettet? do you think the thread was closed by him? or a forum admin closed it?
Click to expand...
Click to collapse
I asked the mod to close it down...because I'm quite discouraged of modders who actually copied my tweaks without even asking permission
EDIt:
anyways I'm tired of bug reports and fixing it and everything anyway
trettet said:
I asked the mod to close it down...because I'm quite discouraged of modders who actually copied my tweaks without even asking permission
Click to expand...
Click to collapse
talking about him!
does it mean you will not work on perfectpeso anymore?
i know have your work copied can be frustrating! but common, if i was you, i wouldn't give a sh*t... if there are modders copying your work, it means you have done a awesome job and we all recognize it!
again, we are all waiting for the next releases of perfectpeso!
betoqm said:
talking about him!
does it mean you will not work on perfectpeso anymore?
i know have your work copied can be frustrating! but common, if i was you, i wouldn't give a sh*t... if there are modders copying your work, it means you have done a awesome job and we all recognize it!
again, we are all waiting for the next releases of perfectpeso!
Click to expand...
Click to collapse
I will work on perfectpeso but won't be release on public, until Official CM7 Stable is out xD
@trettet could u please atleast give the links for the latest gapps :/
PHONEFIX.ZIP (v1.3 [ not sure ] and v1.4 [works perfectly]
Latest Gapps [works with all versions]
Aspee's Fix (works with v1.3 and v1.4)
As for the people who steal his work...you can all go to hell.
Trettet if you want I'll remove the files.I thought is nice for the people to enjoy your work.
trettet said:
I asked the mod to close it down...because I'm quite discouraged of modders who actually copied my tweaks without even asking permission
EDIt:
anyways I'm tired of bug reports and fixing it and everything anyway
Click to expand...
Click to collapse
NightlyfourE?
Sent from my LG-P500 using Tapatalk
manuvarghese said:
Sorry if this is OT.
But I would like to share some bugs I found while using 1.1A as I didn't upgrade to 1.4 as the links were down. Can you verify whether these are faced by any of you !
1. It takes time to wake up from the lock screen. ie even after a hard key press the screen wakes up after say 3-4 secs.
2. Data connection works with flaws. 2G/3G data seems to be buggy.
3. The notification power widget and power widget doesnt work properly. ie, even if i disable/enable Data/Orientation Lock the effect is not applied. I cant even change it in settings. Only solution is a reboot.
4. Incoming call button issues. (Solved in later versions)
Other than these, the rom is pretty stable.
Click to expand...
Click to collapse
Did you flash over without full wipe? Or changed patches now and then? I had these problem long ago bcos of one of above said reasons....a clean wipe has none of the above mentioned bugs .. I'm pretty sure of what I'm saying!
Sent from my LG-P500 using Tapatalk
androidusero1p500 said:
NightlyfourE?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Why NightlyFourE I only use two tweak gov ( maxiumtweak and he removed it )+ remount in init.d
This
#!/system/bin/sh
# Governor Tweaks for Ondemand, Conservative, SmartassV2
# Ondemand
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold;
#echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/down_differential;
#echo "1" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/io_is_busy;
#echo "1" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_down_factor;
#echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
fi;
if [ -e /sys/devices/system/cpu/cpu1/cpufreq/ondemand/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/up_threshold;
#echo "30" > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/down_differential;
#echo "1" > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/io_is_busy;
#echo "1" > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/sampling_down_factor;
#echo "20000" > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/sampling_rate;
fi;
if [ -e /sys/devices/system/cpu/cpufreq/ondemand/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
#echo "30" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential;
#echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy;
#echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor;
#echo "20000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
fi;
# Conservative
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold;
echo "80" > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold; # 35 # 12 # 30 (higher will lead to noticable lags) # 35 # screen off: # 50 ## 35
echo "100" > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step; # more aggressive ramping up (50) # screen off: # 10
fi;
if [ -e /sys/devices/system/cpu/cpu1/cpufreq/conservative/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpu1/cpufreq/conservative/up_threshold;
echo "80" > /sys/devices/system/cpu/cpu1/cpufreq/conservative/down_threshold; # 35 # 12 # 30 (higher will lead to noticable lags) # 35 # screen off: # 50 ## 35
echo "100" > /sys/devices/system/cpu/cpu1/cpufreq/conservative/freq_step; # more aggressive ramping up (50) # screen off: # 10
fi;
if [ -e /sys/devices/system/cpu/cpufreq/conservative/up_threshold ]; then
echo "85" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold;
echo "80" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold; # 35 # 12 # 30 (higher will lead to noticable lags) # 35 # screen off: # 50 ## 35
echo "100" > /sys/devices/system/cpu/cpufreq/conservative/freq_step; # more aggressive ramping up (50) # screen off: # 10
fi;
# SmartassV2
if [ -e /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq ]; then
echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;
if [ "`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq`" -eq 200000 ]; then
echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;
else
echo "100000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;
fi;
echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq;
echo "85" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;
echo "80" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;
echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;
echo "0" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;
fi;
Click to expand...
Click to collapse
And
#!/system/bin/sh
for k in $(busybox mount | grep relatime | cut -d " " -f3)
do
sync
busybox mount -o remount,noatime,nodiratime $k
done
for k in $(busybox mount | grep barrier | cut -d " " -f3)
do
sync
busybox mount -o remount,barrier=0 $k
done
Click to expand...
Click to collapse
And I have credit to trettet
If you think i coppy I will remove two this script
@eee I just asked cos there are no other roms except yours based on official cm.7. 2 with ics looks..
Sent from my LG-P500 using Tapatalk
androidusero1p500 said:
@eee I just asked cos there are no other roms except yours based on official cm.7. 2 with ics looks..
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
I don't understand what you say
As i keep ending calls unwillingly:
Is there a way to change the sensitivity for the proximity sensor?
Anybody have the same problem?
Using the test in "Xperia Diagnostics" the proximity sensor on my Xperia U on latest FXP is turning on/off at about 15mm, which is a bit too little. When i do the test holding the phone to my ear, there is no constant vibration but turning on and off, which happens during calls too, i guess...
Thanks for any input..
PS:
my ears are quite normal, if some are wondering
raha16 said:
As i keep ending calls unwillingly:
Is there a way to change the sensitivity for the proximity sensor?
Anybody have the same problem?
Using the test in "Xperia Diagnostics" the proximity sensor on my Xperia U on latest FXP is turning on/off at about 15mm, which is a bit too little. When i do the test holding the phone to my ear, there is no constant vibration but turning on and off, which happens during calls too, i guess...
Thanks for any input..
PS:
my ears are quite normal, if some are wondering
Click to expand...
Click to collapse
What build? Cause i got this with FXP 209, and not on any other build...
mirost1 said:
What build? Cause i got this with FXP 209, and not on any other build...
Click to expand...
Click to collapse
i had this problem with 209 and have it in 211 also...
raha16 said:
i had this problem with 209 and have it in 211 also...
Click to expand...
Click to collapse
May be its a common problem for new builds, cause now i am using 206a and have no probs with that.
mirost1 said:
May be its a common problem for new builds, cause now i am using 206a and have no probs with that.
Click to expand...
Click to collapse
I'm running 206a now too, but it is the same at least in "Xperia Diagnostics"... I will try real world usage tomorrow...
Anybody knows, where the settings for the sensor are stored? in the Phone-Application, in the Rom, in the Kernel, .... ?
Is there an app that lets you set the distance for the sensor for our device?
raha16 said:
I'm running 206a now too, but it is the same at least in "Xperia Diagnostics"... I will try real world usage tomorrow...
Anybody knows, where the settings for the sensor are stored? in the Phone-Application, in the Rom, in the Kernel, .... ?
Is there an app that lets you set the distance for the sensor for our device?
Click to expand...
Click to collapse
interesting question, did some googling and found this
http://stackoverflow.com/questions/9403351/how-to-change-android-proximity-sensor-sensitivity
This would solve it - but it's for the Desire:
http://forum.xda-developers.com/showthread.php?t=951858
Can somebody port this to our device?
No change in 206 btw...
Just for info, if someone s having the same issues:
I'm using eXperiance V2 - Rom on munjeni-Kernel now, but the problem remains.
i tried this, but no change:
http://forum.xda-developers.com/showpost.php?p=8888081&postcount=914
AndroSensor-App keeps showing 1cm as distance - can somebody verify this value on other kernels or other Roms?
1cm seems too little distance for my ear...
i get the feeling, i'm the only one, having this problem...?
:crying:
Found this:
https://github.com/rachit-rc96/Vengeance-Kernel-U8500/blob/master/drivers/input/misc/apds9702.c
According to my amateur-interpretion of this link, the settings for the sensor are stored in the kernel?
Can somebody confirm this?
Hello guys in my attemp to fix this really annoying bug (all the time calls were hanging or buttons were pressed) i decided to get my hands dirty and take a look!
So the calibration for the proximity sensor is done in the /system/etc/hw_config.sh
Requirements
ROOT
Root Explorer (or a filemanager of your choice with enables acces to system and edit files as text)
So changed the following lines of the originial hw_config.sh of firmware 6.1.1.B.0.54 ( i think that at every fw is the same configuration please provide feedback)
Code:
# Proximity sensor configuration
dev=/sys/bus/i2c/devices/2-0054/
val_cycle=2
val_nburst=0
val_freq=2
val_threshold=5
val_filter=0
echo $val_cycle > $dev/cycle # Duration Cycle. Valid range is 0 - 3.
echo $val_nburst > $dev/nburst # Numb er of pulses in burst. Valid range is 0 - 15.
echo $val_freq > $dev/freq # Burst frequency. Valid range is 0 - 3.
if `ls /data/etc/threshold > /dev/null`; then
cat /data/etc/threshold > $dev/threshold # Use value from calibration
rm /data/etc/threshold # Remove temp file
else # No value from calibration, use default value
echo $val_threshold > $dev/threshold # sensor threshold. Valid range is 0 - 15 (0.12V - 0.87V)
fi
if `ls /data/etc/filter > /dev/null`; then
cat /data/etc/filter > $dev/filter # Use value from calibration
rm /data/etc/filter # Remove temp file
else # No value from calibration, use default value
echo $val_filter > $dev/filter # RFilter. Valid range is 0 - 3.
fi
to :
Code:
# Proximity sensor configuration
dev=/sys/bus/i2c/devices/2-0054/
val_cycle=3
val_nburst=0
val_freq=2
val_threshold=2
val_filter=0
echo $val_cycle > $dev/cycle # Duration Cycle. Valid range is 0 - 3.
echo $val_nburst > $dev/nburst # Numb er of pulses in burst. Valid range is 0 - 15.
echo $val_freq > $dev/freq # Burst frequency. Valid range is 0 - 3.
echo $val_threshold > $dev/threshold # sensor threshold. Valid range is 0 - 15 (0.12V - 0.87V)
echo $val_filter > $dev/filter # RFilter. Valid range is 0 - 3.
As for now i think the overall experience of calling is definately better and no random hang up or button pressed so far... Please provide feedback!!!
Thank you for this useful information. I have a Sony Xperia V lt25i.
After display exchange, the proximity sensor always indicated "near" which resulted in black screen when using the telephone.
Anyhow here is what I did to resolve it:
- backup pics
- root phone using towelroot.apk
- install supersu
- install fx explorer
- install fx explorer root addon
THEN:
use fx explorer
... filesystems --> /system / --> root tools -> mount read-write
then go the file
/system/etc/hw_config.sh
and edit textfile
I changed the threshold from 5 to 9
val_threshold=5
then save file
... filesystems --> /system / --> root tools -> mount read-only
restart phone
try or use the app: Phone Tester
ENJOY
---
Q&A for [ROM] Gohma 2.0 - 12/15/2014 [Android Wear]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Gohma 2.0 - 12/15/2014 [Android Wear]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Alynna said:
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Click to expand...
Click to collapse
I'll have a fix shortly, sorry!
Alynna said:
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Click to expand...
Click to collapse
The init.d/rc.d directories seem to be run from the /system/etc/install-recovery.sh file. Look there and you should see the run-parts command. Which btw okibi, is ingenious, using the stock recovery script to provide init.d support in the face of a kernel that doesn't support it natively.
What software compilation are using Gohma 2.0? I´ve been testing and I have the corrosion problem with a Lg G watch (1,4 volts between pins while being out of the charger), perhaps the base isn´t a "finished-on-Y" compilation?
Nice work, 0 lag everywhere!
Bootloop
While I was running the windows installation to upgrade to 2.0, the program crashed, and the rom is stuck in a bootloop. I can boot into fastboot, and the recovery, but nothing. Any help?
tharrllz said:
While I was running the windows installation to upgrade to 2.0, the program crashed, and the rom is stuck in a bootloop. I can boot into fastboot, and the recovery, but nothing. Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54250887
Toolkit should work to get back to stock lollipop.
Still a bug
There is still a little bug in gohma 2.1, but I fixed it in the script.
SOMETHING sets the governor back to userspace/787200 about a minute into the watches' boot.
I logged in and watched it occur.
However the other parameters now stick.
I fixed it with the following:
#!/system/bin/sh
/system/xbin/sysrw
##############################
# BEGIN CUSTOM USER SETTINGS #
##############################
# increase vibration intensity
# default is 80
echo 85 > /sys/class/timed_output/vibrator/amp
# default is 20
echo 175 > /sys/class/timed_output/vibrator/driving_ms
# switch from userspace to ondemand governor
# echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# Defer change until later, see enforcer below.
GOV=ondemand
FREQ=1094400
# set dpi (default is 240, smaller number means smaller text)
setprop ro.sf.lcd_density 200
##############################
# END CUSTOM USER SETTINGS #
##############################
# improve sd cache
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi
# improve block speed
for node in `busybox find /sys -name nr_requests | grep mmcblk`; do echo 1024 > $node; done
# gpu rendering
busybox mv /system/lib/egl/libGLES_android.so /system/lib/egl/libGLES_android.bak
busybox sed -i '/0 0 android/d' /system/lib/egl/egl.cfg
# adjust minfree
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
# improve file system mounts
busybox mount -o remount,noatime,nodiratime,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /
busybox mount -o remount,noatime,nodiratime,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /sys
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /system
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /data
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /cache
# improve transitions
if [ -e /data/data/com.android.providers.settings/databases/settings.db ]; then
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 0.5 where name = 'transition_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 0.5 where name = 'animator_duration_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 1 where name = 'window_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 0.5 where name = 'transition_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 0.5 where name = 'animator_duration_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 1 where name = 'window_animation_scale'"
fi
# enable sysctl tweaks
busybox sysctl -p /system/etc/sysctl.conf
/system/xbin/sysro
# Wait around for the system to change the governor and change it back, then exit when we're sure its set.
# This function will remain running for a minute to enforce the change, until it's sure the system won't change it back.
enforcer () {
X=0
while [ $X -lt 12 ]; do
if [ ! `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor` = $GOV ]; then
echo $GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $FREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
X=0
else
X=$(($X+1))
fi
sleep 5
done
unset X
}
enforcer &
Alynna said:
There is still a little bug in gohma 2.1, but I fixed it in the script.
SOMETHING sets the governor back to userspace/787200 about a minute into the watches' boot.
I logged in and watched it occur.
However the other parameters now stick.
I fixed it with the following:
Click to expand...
Click to collapse
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
myke66 said:
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
Click to expand...
Click to collapse
I log into the phone using:
adb shell
and check that the /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor remains 'ondemand'.
I noticed when I logged in with gohma 2.0 and 2.1, that this would get switched back to 'userspace' after a little less than a minute.
I'm not sure the 01tweaks file was even executed in 2.0. Definitely is executed in 2.1, but, something else in the system was changing the scaling settings back to defaults.
if its not working, the file above will be 'userspace', if it does, it is 'ondemand'.
Also, I have set my default top speed to 1.0ghz which is why wear launcher is probably snappier. This MAY have an impact on battery life, but probably not too much because the watch remains at about 300mhz whenever idle.
You can check /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies for valid values for the FREQ variable. Lower numbers probably mean marginally better battery life.
myke66 said:
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
Click to expand...
Click to collapse
A handy utility that you can sideload on our watch is PerfMon by Chainfire:
http://forum.xda-developers.com/showthread.php?t=1933284
If your frequency fluctuates from 300 to 1190, then you are on ondemand governor.
---------- Post added at 12:19 PM ---------- Previous post was at 11:50 AM ----------
Alynna,
Thanks for the enforcer mod. For some reason after installing your mod, the governor was still on userspace/787200. After playing around I changed sleep from 5 to 10 and now it works great.
:good:
The standard 5.0 ROM version has a new sleep function that turns off the watch display if it hasn't moved for 30 minutes. This is driving me nuts as I always put my watch next to my monitor while I'm working so I have to keep waking it up or I miss notifications.
Is this "feature" in this ROM and if so, is there any way to turn it off or extend the timeout ?
Thanks
i'm looking at the rom and kernel.
the kernel looks like it has more option/tweaks.
i know both dont work together a bit normal cause the rom is a bit the same it are tweaks and no visual changes
i think kernel looks better. in way of functions.
just this rom has also more cpu steps? 300-1.1ghz?
cause if im right stock just is locked on 778mhz? and even with wear control app seems like i can't change it (i mean i don't realy know cant see if power save or balanced governers do any thing). need to check with a app how fast my cpu is running.
This ROM had been great! One question: Does the reset option in the watch settings properly reset and keep gohma tweaks? I tend to flash allot of ROMs on my phone and have been flashing my watch back to stock then each time as well as reflashing gohma. Stock recovery here. See no real reason for custom when everything is done using adb and computer.
Nandrew said:
This ROM had been great! One question: Does the reset option in the watch settings properly reset and keep gohma tweaks? I tend to flash allot of ROMs on my phone and have been flashing my watch back to stock then each time as well as reflashing gohma. Stock recovery here. See no real reason for custom when everything is done using adb and computer.
Click to expand...
Click to collapse
Yup. Just reset between phone ROM flashes.
Any update or thoughts on if we can find a way to make this ROM stop pumping out the 1.74 volts to our wrists via the metal contacts? Just discovered the whole issue of corrosion via the voltage emitted from the watch while being worn. I checked mine, running this ROM, and sure enough: it's live. 1.74 volts of electricity going into your wrist while you wear this thing. LG claims to have sent out a software fix a while back.
Thanks for the development & work on this ROM! Hopefully an "ah-ha" moment can be had and get this issue solved!
To think some people actually pay to have electricity run thru their body.. LG didn't consider it a feature? Lol
No corrosion here.
Gohma 2.2 - NEED DOWNLOAD
Jake's site to download the rom seems to be acting up. The download is extremely slow and keeps failing. I am in desperate need of this excellent ROM!! Does anybody have an alternate download link for Gohma 2.2? Any help is greatly appreciated.
Quick question? Installed 2.2 and everything runs fine except Perfmon only shows one core active. If I run the adb script I can turn the others on but for some reason by default one one core is up after a reboot. Any help.
kwd114kwd114 said:
Quick question? Installed 2.2 and everything runs fine except Perfmon only shows one core active. If I run the adb script I can turn the others on but for some reason by default one one core is up after a reboot. Any help.
Click to expand...
Click to collapse
The 01tweaks script on 2.3 didn't work for me either. Ondemand and frequency are correctly set, but only one core. Couple of workarounds:
1. Set the cores directly using adb commands from your PC.
2. Sideload kernel adiutor from the play store (nice kernel tuner app that works on our watch, dev is active on XDA)
3. Or modify the 01tweaks script to set the cores within the enforcer part of the script (right after $GOV and $FREQ are set)
Code:
# Wait around for the system to change the governor and change it back, then exit when we're sure its set.
# This function will remain running for a minute to enforce the change, until it's sure the system won't change it back.
enforcer () {
X=0
while [ $X -lt 12 ]; do
if [ ! `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor` = $GOV ]; then
echo $GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $FREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1" > /sys/devices/system/cpu/cpu1/online
X=0
else
X=$(($X+1))
fi
sleep 5
done
unset X
}
enforcer &
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use the mod at your own risk there is no warranty or guarantee.
I made this mod to speed up the phone. Thermal throttling is enabled. This mod runs post boot before Stock Oreo get's loaded. No need for Kernel Adiutor, The speed mod will make all the tweaks for the Lgv20 to run at it's maximum performance & prolong the battery life.
Note: Flashing this mod when running the Lemon_Drop rom, will remove Zram. To fix just flash the latest version of Auto_Debloat again. I made this page before the Speed Mod was included in Auto_Debloat.
Updated on 12-27-22
You can just flash on top of older versions to update
This twrp mod only touches two files:
"/system/vendor/bin/init.qcom.post_boot.sh" permissions are 0 2000 0755
"/system/media/display/calib.cfg" permissions are 0 0 0644
You can back them up before install, or just flash the latest uninstaller.
Requirements:
TWRP
Lgv20 msm8996 aka Qualcomm Snapdragon 820
Stock Oreo 8.0
ezV2020 Kernel Stock Oreo 8.0 Kernel, This is what makes this Speed Mod possible
Uninstall Kernel Adiutor
How to install?
Download the version you want to use. If your not sure what version you want, v4.2 is good. It is the speed mod and will fix the image retention issue on the Lgv20 phone, on start up.
You may also want Boeffla_Wakelock_blocker_readme.zip with v5.4, instructions on how to use the Boeffla Wakelock blocker.
Flash in twrp wipe dalvik cache and reboot.
All the versions have the latest speed mod. Flash on top of older versions to update.
v3.28 Speed mod only
v4.28 speed mod + image retention fix lgv20
v5.28 speed mod + image retention fix lgv20 + Boeffla Wakelock blocker
Update notes
New v3.28
change GPU governor to msm-adreno-tz with default 133mhz
New 3.27
Removed the GPU tweaks and adjusted the idle timer that should speed up the GPU also with out the battery drain I was experiencing.
New v3.26
Adjusted the GPU tweaks so they do not use too much power but still provide a performance boost.
New v3.25
Added some GPU tweaks
New v3.24
Fixed a type in last speed mod.
New v3.23
Changed the rq_affinity to number 2. That should speed up the eMMC drive and sdcard.
New v3.22
All new interactive governor settings.
New v3.21
Tweaked the interactive governor settings.
New v3.20
Changed governor to interactive, increased speed & increased battery life.
New v3.19
Fixed some things with the TCP Speed mod
New v3.18
Added a TCP speed mod to speed up internet.
New v3.17
Changed the TCP Algorithm to cubic. May speed up internet and make it more stable. I have an issue with Wifi Calling where the voice will cut in and out sometimes. This may fix that issue.
New v3.16
Changed GPU Governor to Simple_Ondmand reduced the power level to save battery power.
New v3.15
Trying to save a little bit of battery life without sacrificing speed.
New v3.14
Added disk scheduler to noop for micro sdcard.
New v3.13
fixed image retention issue on v4.13 and v5.13 it's the best I can fix.
New v3.12
Change disk scheduler to noop. Some other tweaks to improve speed and battery life.
New v3.11
This should speed up the phone a little bit more. Should also save battery life. I tweaked the sched_upmigrate and sched_downmigrate. The up is set to 95% and down is set to 90%. So if a task is using more that 95% of cpu it will go the big cpu and vice versa.
New v3.10
Tweaked the Entropy tweak a little bit.
New v3.9
Added an entropy tweak. This should improve the speed of the phone and prevent lag.
New v3.8
Changed the disk speed tweaks. Much faster now.
New v3.7
Some tweaks, some fixes. haha lazy to note it should be faster that other versions.
New v3.6
Some more kernel tweaks, and an internet kernel speed tweak. I think it's faster.
New v3.5 Speed Mod
It's faster, changed the cpu sample rate to 19000 that seems to be in the butter zone. What's odd is, my music sounds amazing with this version. I think I am keeping this one.
New v3.4 Speed Mod
Changed disk scheduler from noop to deadline, deadline prioritises reads over writes so it should improve performance a little bit.
As for the Auto Brightness fix, I made it more sensitive. If you are in the house and set a brightness to say 30, then go out side in direct sun light it will change to 100, but if you go back into the house it should change back to 30 or what ever setting you have chosen.
You need the latest version of the Uninstaller to uninstall this version.
New v3.3 Speed Mod
Changed ondemand governor back to 95% on cpu usage before it kicks up to full speed, might save a little battery power.
v4.3 & v5.3 found stock calib.cfg that file will fix the Auto Brightness issue on the Lgv20 running stock Oreo, aka Assertive Display.
What is a Sunlight or Assertive Display? - Gary explains
You need the latest uninstaller to uninstall this version. Flash on top of older versions to update. enjoy
New v3.2 Speed Mod
Tweaked disk cache settings, it's faster than v3.1. I updated v4.2 and v5.2 changed the KCAL settings, drastically improved contrast and colors & no image retention. Flash on top of older versions to update.
Red = 250
Green = 250
Blue = 235
Minimum = 35
Saturation = 27
Hue = 1520
Value = 112
Contract = 132
New v3.1 speed mod
Changed the ondemand governor sample rate 20000. Took me awhile to find the perfect sample rate, but I found it. Also Increased the read ahead on microsd card to 512k. This is the most well optimized version I have ever made. Good battery life and increased speed.
New v2.6 speed mod
Changed the Sample rate of the Ondemand Governor. Should extend battery life.
New v2.5 version of speed mod
Changed the read ahead to 256k for all drives. Tweaked the speed of the eMMC drive a little. It should be faster than v2.4.
New v2.4 version of speed mod.
I was able to increase the speed of the eMMC drive so apps load quicker. Also increased battery life. Sometimes I update this speed mod like once a month, so you may want to check back to see if there is an update.
Credits, A Special Thank You
@ezzony - for the ezV2020 kernel. XDA
@askermk2000 - for the MK2000 kernel. XDA
@helf for the KCAL settings in v4.2 & v5.2 XDA
@rawe_etc for the TCP Speed mod XDA
at MiguelNdeCarvalho for the Stock calib.cfg aka auto brightness fix github
at Gary Sims over at androidauthority.com on what Assertive Display is.
at amitwh for the interactive governor settings for the msm8996 Github
And everyone else that I may have missed that helped with the Lgv20.
Thank you all, for helping make the Lgv20 phone one of the best rooted phones of all time.
What does The Speed Mod look like?
#Speed Mod 3.28
# configure governor settings for little cluster
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif
echo 19000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
echo 20000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate
echo 729600 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/io_is_busy
echo 80 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
echo 19000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time
echo 79000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis
echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif
# online CPU2
echo 1 > /sys/devices/system/cpu/cpu2/online
# configure governor settings for big cluster
echo "interactive" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load
echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif
echo "19000 1400000:39000 1700000:19000 2100000:79000" > /sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay
echo 90 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load
echo 20000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate
echo 1248000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq
echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/io_is_busy
echo "85 1500000:90 1800000:70 2100000:95" > /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads
echo 19000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time
echo 79000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis
echo 300000 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo 1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif
# GPU change governor to msm-adreno-tz with default 133mhz
echo msm-adreno-tz > /sys/class/kgsl/kgsl-3d0/devfreq/governor
echo 6 > /sys/class/kgsl/kgsl-3d0/default_pwrlevel
# re-enable thermal and BCL hotplug
echo 1 > /sys/module/msm_thermal/core_control/enabled
echo -n disable > /sys/devices/soc/soc:qcom,bcl/mode
echo $bcl_hotplug_mask > /sys/devices/soc/soc:qcom,bcl/hotplug_mask
echo $bcl_soc_hotplug_mask > /sys/devices/soc/soc:qcom,bcl/hotplug_soc_mask
echo -n enable > /sys/devices/soc/soc:qcom,bcl/mode
# recover offlined_mask in thermal.
echo 0 > /sys/module/msm_thermal/core_control/force_unmask
# Set the eMMC drive scheduler to noop
echo noop | tee /sys/block/sd*/queue/scheduler >/dev/null
echo 0 | tee /sys/block/sd*/queue/add_random >/dev/null
echo 256 | tee /sys/block/sd*/queue/read_ahead_kb >/dev/null
echo 0 | tee /sys/block/sd*/queue/rotational >/dev/null
echo 64 | tee /sys/block/sd*/queue/nr_requests >/dev/null
echo 1 | tee /sys/block/sd*/queue/iostats >/dev/null
echo 2 | tee /sys/block/sd*/queue/rq_affinity >/dev/null
# Set sdcard scheduler to noop
echo noop > /sys/block/mmcblk0/queue/scheduler
echo 0 > /sys/block/mmcblk0/queue/add_random
echo 256 > /sys/block/mmcblk0/queue/read_ahead_kb
echo 0 > /sys/block/mmcblk0/queue/rotational
echo 64 > /sys/block/mmcblk0/queue/nr_requests
echo 1 > /sys/block/mmcblk0/queue/iostats
echo 2 > /sys/block/mmcblk0/queue/rq_affinity
# Enable LPM D3
echo N > /sys/module/lpm_levels/parameters/sleep_disabled
# Disable Adaptive LMK
echo 0 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
#echo 81250 > /sys/module/lowmemorykiller/parameters/vmpressure_file_min
# Disable sync wakee policy tunable
echo 0 > /proc/sys/kernel/sched_prefer_sync_wakee_to_waker
# Kernel based tweaks
echo 0 > /proc/sys/kernel/compat-log
echo 0 > /proc/sys/kernel/panic
echo 0 > /proc/sys/kernel/panic_on_oops
echo 0 > /proc/sys/kernel/perf_cpu_time_max_percent
echo 10 > /proc/sys/fs/lease-break-time
echo 3 > /proc/sys/kernel/sched_spill_nr_run
echo 15 > /proc/sys/kernel/sched_init_task_load
echo 1 > /proc/sys/net/ipv4/tcp_ecn
echo 3 > /proc/sys/net/ipv4/tcp_fastopen
echo 95 > /proc/sys/kernel/sched_upmigrate
echo 0 > /proc/sys/kernel/sched_upmigrate_min_nice
echo 1 > /proc/sys/kernel/sched_restrict_cluster_spill
echo 90 > /proc/sys/kernel/sched_downmigrate
echo 5 > /proc/sys/kernel/sched_small_wakee_task_load
echo 30 > /proc/sys/kernel/sched_big_waker_task_load
echo 1 > /proc/sys/kernel/sched_enable_thread_grouping
# Limit kernel printk console log
echo "0 0 0 0" > /proc/sys/kernel/printk
# Disable exception-trace logs
echo 0 > /proc/sys/debug/exception-trace
# Entropy speed tweaks
echo 64 > /proc/sys/kernel/random/read_wakeup_threshold
echo 3072 > /proc/sys/kernel/random/write_wakeup_threshold
echo 60 > /proc/sys/kernel/random/urandom_min_reseed_secs
# Enable Dynamic Fsync for increased performance
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
# TCP speed tweaks
echo "2097152" > /proc/sys/fs/file-max
echo "cubic" > /proc/sys/net/ipv4/tcp_congestion_control
echo "60000" > /proc/sys/net/ipv4/tcp_max_orphans
echo "1" > /proc/sys/net/ipv4/tcp_no_metrics_save
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling
echo "1" > /proc/sys/net/ipv4/tcp_timestamps
echo "1" > /proc/sys/net/ipv4/tcp_sack
echo "10240" > /proc/sys/net/ipv4/tcp_max_syn_backlog
echo "1" > /proc/sys/net/ipv4/tcp_mtu_probing
echo "2" > /proc/sys/net/ipv4/tcp_synack_retries
echo "1024 65535" > /proc/sys/net/ipv4/ip_local_port_range
echo "1" > /proc/sys/net/ipv4/tcp_rfc1337
echo "15" > /proc/sys/net/ipv4/tcp_fin_timeout
echo "1024" > /proc/sys/net/core/somaxconn
echo "65536" > /proc/sys/net/core/netdev_max_backlog
echo "6291456" > /proc/sys/net/core/optmem_max
echo "65536 131072 262144" > /proc/sys/net/ipv4/tcp_mem
echo "65536 131072 262144" > /proc/sys/net/ipv4/udp_mem
echo "6291456" > /proc/sys/net/core/rmem_default
echo "6291456" > /proc/sys/net/core/rmem_max
echo "16384" > /proc/sys/net/ipv4/udp_rmem_min
echo "1572864" > /proc/sys/net/core/wmem_default
echo "1572864" > /proc/sys/net/core/wmem_max
echo "16384" > /proc/sys/net/ipv4/udp_wmem_min
echo "1440000" > /proc/sys/net/ipv4/tcp_max_tw_buckets
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse
#End of speed mod 3.28
Got 1.4 done. My phone runs so much faster now, it's like having a brand new phone. Version 1.4 should be the final version. Recommended: Everyone that downloaded the previous versions install the new v1.4
Hey everyone, I had fun making theses. Enjoy
v1.5 Speed mod only
v1.6 speed mod + image retention fix lgv20
v1.7 speed mod + image retention fix lgv20 + Google quick search wakelock block.
v1.8 speed mod + image retention fix lgv20 + Ultimate Battery savings mode
Just flashed 1.7.1. Will report back once I get to use it for a bit. Thanks!
Finally there is a solution of image retention for non-root v20, I only unlock BL and have TWRP, flashed it then reboot and never see the image retention again.
Very appreciate for your development!!!
H990DS 8.0 V20B+ezV2020+This Mod v4.2
stvc said:
Finally there is a solution of image retention for non-root v20, I only unlock BL and have TWRP, flashed it then reboot and never see the image retention again.
Very appreciate for your development!!!
H990DS 8.0 V20B+ezV2020+This Mod v4.2
Click to expand...
Click to collapse
Your welcome, glad you like it.
Hey everyone I just got done with speed mod 2.1 Tweaked Ondemand governor for faster performance.
Updated all the speed mods v2.5
New v2.6 speed mod
Changed the Sample rate of the Ondemand Governor. Should extend battery life.
to upgrade, just flash over older versions, wipe dalvik cache & reboot.
New v3.2 Speed Mod
Tweaked disk cache settings, it's faster than v3.1. I updated v4.2 and v5.2 changed the KCAL settings, drastically improved contrast and colors & no image retention. Flash on top of older versions to update.
Red = 250
Green = 250
Blue = 235
Minimum = 35
Saturation = 27
Hue = 1520
Value = 112
Contract = 132
New v3.3 Speed Mod
Changed ondemand governor back to 95% on cpu usage before it kicks up to full speed, might save a little battery power.
v4.3 & v5.3 found stock calib.cfg that file will fix the Auto Brightness issue on the Lgv20 running stock Oreo, aka Assertive Display.
What is a Sunlight or Assertive Display? - Gary explains
You need the latest uninstaller to uninstall this version. Flash on top of older versions to update. enjoy
I am still working on the Auto Brightness fix, I think it needs to be more sensitive. So there will be updates. Just letting everyone know I am working on this.
New v3.4 Speed Mod
Changed disk scheduler from noop to deadline, deadline prioritises reads over writes so it should improve performance a little bit.
As for the Auto Brightness fix, I made it a lot more sensitive. If you are in the house and set a brightness to say 30, then go out side in direct sun light it will change to 100, but if you go back into the house it should change back to 30 or what ever setting you have chosen.
You need the latest version of the Uninstaller to uninstall this version.
Thanks for the mods. I've got a newly rooted VS995 and just loaded v3.4 but noticed my Antutu CPU score dropped by a decent amount. I'm charging up the phone to re-run the benchmark to see if it was a fluke. Did you happen to benchmark before/after numbers?
nickb2b said:
Thanks for the mods. I've got a newly rooted VS995 and just loaded v3.4 but noticed my Antutu CPU score dropped by a decent amount. I'm charging up the phone to re-run the benchmark to see if it was a fluke. Did you happen to benchmark before/after numbers?
Click to expand...
Click to collapse
Your welcome, I had fun making them.
No I didn't run any benchmarks, It just seems like it's faster to me.
nickb2b said:
Thanks for the mods. I've got a newly rooted VS995 and just loaded v3.4 but noticed my Antutu CPU score dropped by a decent amount. I'm charging up the phone to re-run the benchmark to see if it was a fluke. Did you happen to benchmark before/after numbers?
Click to expand...
Click to collapse
You got me thanking now lol. I will run that test on my phone and see if I can duplicate your issue. The speed mod is still a work in progress. I can try a different cpu governor also and see if that helps. Rite now I am using Ondemand. Thank you for bringing this to my attention. I will look into this.
nickb2b said:
Thanks for the mods. I've got a newly rooted VS995 and just loaded v3.4 but noticed my Antutu CPU score dropped by a decent amount. I'm charging up the phone to re-run the benchmark to see if it was a fluke. Did you happen to benchmark before/after numbers?
Click to expand...
Click to collapse
The thing with benchmark programs that there is just so many variables to take into consideration.
But this is what I found out with GeekBench 5
With Speed Mod v5.5
I made some changes have not uploaded it yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is stock with a lower battery count also.
As you can see they are almost the same. But the Lgv20 phone is not a fast phone to start with. But I think the speed mods do help even if it's just a little bit.
New v3.5 Speed Mod
It's faster, changed the cpu sample rate to 19000 that seems to be in the butter zone.
Thanks, I'll dl geekbench and give it a shot.