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
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.
3G TurboCharger & Kick Ass Kernel Tweaks
(two scripts).
As well as
V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
These were made by zeppelinrox .
His script got him an article in the XDA front page found here.
The 3G and Kickass tweaks are new to me, but are good. The memory fixer i have a thread in Evo 4G section talking about it.
A few memory tweaks would be necessary since we have higher memory phones. But nonetheless, this is good stuff now that we have root.
All he asks is that you link to his page and thank him.
Here are his files
On the supercharger, it is recommended to use option 8. The others you will have to read up on. They are new to me.
You can use these by removing the .txt extension, and running them with script manager (free in market) as root, and run at boot.
theres a thread with the V6 info in here but it doesn have the kickass tweaks and 3g turbo... btw every time i ran kernel tweaks i had to wipe and flash... dont use.
The kickass kernel tweak problem was do to the IO schedulaer... zeppelinrox told me to delete a few lines and this is his text:
"Hi... some users are having an issue with the io scheduling tweaks...
delete this block of text from the installer:
for i in /sys/block/*/queue/scheduler;
do
echo "cfq" > \$i;
done;
for i in /sys/block/*;
do
echo "0" > \$i/queue/rotational;
echo "1" > \$i/queue/iosched/low_latency;
echo "1" > \$i/queue/iosched/back_seek_penalty;
echo "1000000000" > \$i/queue/iosched/back_seek_max;
echo "0" > \$i/queue/iosched/slice_idle;
echo "512" > \$i/queue/nr_requests;
echo "1" > \$i/queue/iosched/fifo_batch;
echo "16" > \$i/queue/iosched/quantum;
done;
for i in /sys/block/*/queue/scheduler;
do
echo "noop" > \$i;
done;
Don't worry about unknown key errors though as all kernels don't support all the sysctl tweaks."
Use at your own risk, i am not responsible for anything happening to your device
What it does
This flashable zip turns your button backlight off permanantly.
it just changes your hw_config.sh file to disable backlight.
Steps
for your own safety please make a backup, in case something happens.
reboot into cwm
flash the zip
Downloads for bbl disabler.
active
lww
mini
mini pro
ray
If u want to get the light back,
active
lww
mini
mini pro
ray
in case it didn't work, edit your hw_config file found in system/etc
find this line: echo 1 > $dev/button-backlight/max_current
and set it to
Active: echo 8000 > $dev/button-backlight/max_current
lww: echo 1500 > $dev/button-backlight/max_current
mini pro: echo 500 > $dev/button-backlight/max_current
ray: echo 50 > $dev/button-backlight/max_current
for mini find these two lines
echo 1 > $dev/button-backlight-rgb1/max_current
echo 1 > $dev/button-backlight-rgb2/max_current
change to
echo 8000 > $dev/button-backlight-rgb1/max_current
echo 8000 > $dev/button-backlight-rgb2/max_current
okay
I have an easier way
put it in init.d
Code:
echo 1 > /sys/class/leds/button-backlight-rgb1/max_current;
echo 1 > /sys/class/leds/button-backlight-rgb2/max_current;
Re: Testers for button backlight disabler
Gustavo RD78 said:
okay
I have an easier way
put it in init.d
Code:
echo 1 > /sys/class/leds/button-backlight-rgb1/max_current;
echo 1 > /sys/class/leds/button-backlight-rgb2/max_current;
Click to expand...
Click to collapse
Add it at the last or change something??
Edit: I get a feeling u use a mini(others dont have 2 button backlights rgb1 and rgb2)
Don't forget to hit thanks
Add the lines in a script that you already have or add this script :good:
Note: this is not a flash zip
Gustavo RD78 said:
Add the lines in a script that you already have or add this script :good:
Note: this is not a flash zip
Click to expand...
Click to collapse
thanks for the info and the file
but..i still think mine's easier, just a simple flash when you flash a new rom
could you please try it and confirm it works?
thanks
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 &
My tuning script very good balanced.
For the kernel with zzmoove gov and fiops io scheduler.
I run the script with Tasker.
But you can copy it to /system/etc/init.d/
Don't forget, set it to 0755 perms
//
chmod 644 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo 'zzmoove' > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 644 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo 'zzmoove' > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 644 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 'zzmoove' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 644 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo 'zzmoove' > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo '0' > /sys/module/msm_performance/parameters/touchboost
echo '30' > /sys/module/cpu_boost/parameters/input_boost_ms
echo '0' > /sys/block/sda/queue/iostats
echo '0' > /sys/block/mmcblk0/queue/iostats
echo '4' > /sys/kernel/autosmp/conf/max_cpus
echo '2048' > /sys/block/sda/queue/read_ahead_kb
echo 'fiops' > /sys/block/sda/queue/scheduler
echo 'fiops' > /sys/block/mmcblk0/queue/scheduler
echo '1' > /sys/kernel/autosmp/conf/cycle_down
echo '0:844800' > /sys/module/cpu_boost/parameters/input_boost_freq
echo '2:940800' > /sys/module/cpu_boost/parameters/input_boost_freq
//
SOT 8 hour or more
AICP and Llama kernel Non EAS 0.5.
How is the performance on synthetics like antutu, games, and ui smoothness?
nfsmw_gr said:
How is the performance on synthetics like antutu, games, and ui smoothness?
Click to expand...
Click to collapse
Geek bench 4, single core 1682, multi cores 4190.
No laggy. I am happy. You can try it. ?
7hour Sot, very simple, if you don't play game.
denf666 said:
Geek bench 4, single core 1682, multi cores 4190.
No laggy. I am happy. You can try it. ?
7hour Sot, very simple, if you don't play game.
Click to expand...
Click to collapse
A Profile for kernel Adiutor would be nice. Much easier to handle and to adjust if needed.
stock rom is very good.İ think flash custom rom not needed.This phone's best thing is speaker.
i think My SoT is good
Edit : No lag of course this is sd820 .
atakan33 said:
stock rom is very good.İ think flash custom rom not needed.This phone's best thing is speaker.
i think My SoT is goo
Edit : No lag of course this is sd820 .
Click to expand...
Click to collapse
Which version?
yeah i agree on a kernel auditor profile but will it work with other ROMS?
denf666 said:
Which version?
Click to expand...
Click to collapse
B05 or B06 nougat
gecko702 said:
yeah i agree on a kernel auditor profile but will it work with other ROMS?
Click to expand...
Click to collapse
this is the KA profile. Enjoy.
{"version":1,"profile":{"commands":[{"path":"\/sys\/devices\/system\/cpu\/cpu%d\/cpufreq\/scaling_governor2","command":"#{\"path\":\"\\\/sys\\\/devices\\\/system\\\/cpu\\\/cpu%d\\\/cpufreq\\\/scaling_governor\",\"value\":\"zzmoove\",\"min\":2,\"max\":3,\"bigCpus\":[2,3],\"LITTLECpus\":[0,1],\"corectlmin\":2}"},{"path":"\/sys\/devices\/system\/cpu\/cpu%d\/cpufreq\/scaling_governor0","command":"#{\"path\":\"\\\/sys\\\/devices\\\/system\\\/cpu\\\/cpu%d\\\/cpufreq\\\/scaling_governor\",\"value\":\"zzmoove\",\"min\":0,\"max\":1,\"bigCpus\":[2,3],\"LITTLECpus\":[0,1],\"corectlmin\":2}"},{"path":"\/sys\/module\/msm_performance\/parameters\/touchboost","command":"echo '0' > \/sys\/module\/msm_performance\/parameters\/touchboost"},{"path":"\/sys\/module\/cpu_boost\/parameters\/input_boost_ms","command":"echo '30' > \/sys\/module\/cpu_boost\/parameters\/input_boost_ms"},{"path":"\/sys\/block\/sda\/queue\/iostats","command":"echo '0' > \/sys\/block\/sda\/queue\/iostats"},{"path":"\/sys\/block\/mmcblk0\/queue\/iostats","command":"echo '0' > \/sys\/block\/mmcblk0\/queue\/iostats"},{"path":"\/sys\/kernel\/autosmp\/conf\/max_cpus","command":"echo '4' > \/sys\/kernel\/autosmp\/conf\/max_cpus"},{"path":"\/sys\/block\/sda\/queue\/read_ahead_kb","command":"echo '2048' > \/sys\/block\/sda\/queue\/read_ahead_kb"},{"path":"\/sys\/block\/sda\/queue\/scheduler","command":"echo 'fiops' > \/sys\/block\/sda\/queue\/scheduler"},{"path":"\/sys\/block\/mmcblk0\/queue\/scheduler","command":"echo 'fiops' > \/sys\/block\/mmcblk0\/queue\/scheduler"},{"path":"\/sys\/kernel\/autosmp\/conf\/cycle_down","command":"echo '1' > \/sys\/kernel\/autosmp\/conf\/cycle_down"},{"path":"\/sys\/module\/cpu_boost\/parameters\/input_boost_freq0","command":"echo '0:844800' > \/sys\/module\/cpu_boost\/parameters\/input_boost_freq"},{"path":"\/sys\/module\/cpu_boost\/parameters\/input_boost_freq2","command":"echo '2:940800' > \/sys\/module\/cpu_boost\/parameters\/input_boost_freq"}]}}
Here is a created profile everyone could import.
Just unzip and import afterwards through kernel Adiutor.
http://cloud.tapatalk.com/s/59e6649a10013/TuneZZmoove.zip
SilentEYE said:
Here is a created profile everyone could import.
Just unzip and import afterwards through kernel Adiutor.
http://cloud.tapatalk.com/s/59e6649a10013/TuneZZmoove.zip
Click to expand...
Click to collapse
Are u using this profile?
denf666 said:
Are u using this profile?
Click to expand...
Click to collapse
Yes I applied it yesterday and testing it out now on llama 0.5 kernel.
Script noob here. Be gentle.
Any tips for using with EX Kernel Manager? I have never messed with scripts. I added the json to see what would happen. Magisk log shows TuneZZmoove executing but I get no output when running in EXKM. Then again, that may be normal.
Researching in the meantime.....
Cablespider said:
Script noob here. Be gentle.
Any tips for using with EX Kernel Manager? I have never messed with scripts. I added the json to see what would happen. Magisk log shows TuneZZmoove executing but I get no output when running in EXKM. Then again, that may be normal.
Researching in the meantime.....
Click to expand...
Click to collapse
KA Profil is only for KA, but you can run the script with Tasker or init.d.
Hi,
can I use this script on AMD stock rom with stock kernel? if yes, how....?
My SOT is max 3,5-4hours...too bda for me...
thx
kraljan66 said:
Hi,
can I use this script on AMD stock rom with stock kernel? if yes, how....?
My SOT is max 3,5-4hours...too bda for me...
thx
Click to expand...
Click to collapse
This is only for kernel with zzmoove and fiops support.
ok thy, maybe stupid question, but is any kernel with supprot as you write for this rom/stock...? I have not see yet here...
kraljan66 said:
ok thy, maybe stupid question, but is any kernel with supprot as you write for this rom/stock...? I have not see yet here...
Click to expand...
Click to collapse
Just tested on LOS based Rom.
I added it to init.d for the time being. Will test after this charge.