Hello,
Is there any reason why the scaling min freq is not equal to the cpuinfo_min_freq?
By default the scaling min freq is set to 245760
However the cpu can go to 122880
I have manual set this and the phone seems to run fine, changing freq on demand as need and slowing back as it should
I tried editing the /init.qcom.post_boot.sh so it does it every time on boot up but it just overwrote the file with the default
chris... said:
Hello,
Is there any reason why the scaling min freq is not equal to the cpuinfo_min_freq?
By default the scaling min freq is set to 245760
However the cpu can go to 122880
I have manual set this and the phone seems to run fine, changing freq on demand as need and slowing back as it should
I tried editing the /init.qcom.post_boot.sh so it does it every time on boot up but it just overwrote the file with the default
Click to expand...
Click to collapse
I use overclock widget and it do the job (need root)
True, overclock widget sets it perfectly, lets hope this saves more battery
To check cpu running speed use system panel ..
I think that there's a reason cause they set the kernel to that frequency. Probably 122mhz is too low for gsm csmda radio activity or probably cause after some tests they saw that there was no difference in stand by between the two power consumption levels.
I got no problem when on idel setting the max cpu freq to the lowest speed possible
If there were not problems about it they would set it to 122Mhz. Maybe they solved some lags, who know what. But if it's at 245Mhz a reason exists.
Anyway.... I don't know too, I think only Sony Ericsson developers could tell something about this choice.
Probably so their crappy interface and built in demo apps can work
Have had no issues running this at boot time ( via root )
---------------------- snip ---------------
#!/system/bin/sh
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
---------------------- snip ---------------
i save this as "slow.sh"
then run
#sh slow.sh
now idle uses 122.88 mhz and saves alot of battery!
morning_wood said:
Have had no issues running this at boot time ( via root )
---------------------- snip ---------------
#!/system/bin/sh
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
---------------------- snip ---------------
i save this as "slow.sh"
then run
#sh slow.sh
now idle uses 122.88 mhz and saves alot of battery!
Click to expand...
Click to collapse
Hi Morning_wood
Could you please share the whole procedure for us newbi's .. i think saving battery life would help us all allot
kimb0 said:
Hi Morning_wood
Could you please share the whole procedure for us newbi's .. i think saving battery life would help us all allot
Click to expand...
Click to collapse
use the "overclock widget" app
You have separate min/max speeds while idle and while running
kimb0 said:
Hi Morning_wood
Could you please share the whole procedure for us newbi's .. i think saving battery life would help us all allot
Click to expand...
Click to collapse
1. you need root
2. create file "slow.sh" with this entry ( can use notepad or whatever )
#!/system/bin/sh
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
save anywhere eg: /sddcard/slow.sh
3. open a terminal *ConnectBot works fine
4.
$su
#sh /sdcard/slow.sh
5. exit your terminal
note: you need to do this everytime you reboot your phone
I use Android System Info ( System / CPU tab ) to check the cpu usage
morning_wood said:
1. you need root
2. create file "slow.sh" with this entry ( can use notepad or whatever )
#!/system/bin/sh
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
save anywhere eg: /sddcard/slow.sh
3. open a terminal *ConnectBot works fine
4.
$su
#sh /sdcard/slow.sh
5. exit your terminal
note: you need to do this everytime you reboot your phone
I use Android System Info ( System / CPU tab ) to check the cpu usage
Click to expand...
Click to collapse
Thank you
morning_wood said:
I use Android System Info ( System / CPU tab ) to check the cpu usage
Click to expand...
Click to collapse
is this an app?
Could someone please give me some good running settings in overclock widget ?
pukidukie said:
Could someone please give me some good running settings in overclock widget ?
Click to expand...
Click to collapse
set min to the minimum and max to the maximum
The kernel uses a frequency scheduler that automatically changes the speed based on demand
Ok, thank you
Is there any way to fix cpu schedule file, with out widget or slow.sh file to make cpu idle frq constant 122880?
Sent from my E10i using XDA App
Yodd said:
Is there any way to fix cpu schedule file, with out widget or slow.sh file to make cpu idle frq constant 122880?
Sent from my E10i using XDA App
Click to expand...
Click to collapse
Setcpu works fine...
forum.xda-developers.com/showthread.php?t=505419
mo more slow.sh - the easy way revised
----------------------------------------
http://de.blank-online.eu/file/autostart.apk
How to do the slow-cpu
Make a autostart.sh file on your desktop containing this line:
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Copy to /sdcard/
Install the autostart.apk
Reboot phone / say yes to superuser
Plug in phone * with usbdebuging of course
ADB shell, su to root
In ADB shell do...
mkdir /data/opt
cd /data/opt
busybox cp /sdcard/autostart.sh /data/opt
chmod 777 autostart.sh
reboot
Enjoy slowcpu at bootup!
morning_wood; said:
Make a autostart.sh file on your desktop containing this line:
echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Install the autostart.apk
In ADB shell do...
mkdir /data/opt
cd /data/opt
busybox cp /sdcard/autostart.sh /data/opt
chmod 777 autostart.sh
reboot
/QUOTE]
Not for me.....
I'm trying with #!/sh.....etc...
Thank you
Click to expand...
Click to collapse
Related
*** WARNING: Overclocking may damage your device! Use at own risk! ***
Did you know that you can easily overclock your nike in android? You just have to run the following commands from a shell:
Code:
su
echo 4 > /sys/module/clock_7x00/parameters/ahb_div
echo 528 > /sys/module/clock_7x00/parameters/a11
This sets your nike to 528MHz (400MHz is default) after the next sleep/resume. You can exchange the '528' by a different clock to try. For easy oc I recommend to copy the last 2 lines from the code into a file named 'oc.sh' on your sdcard. Overclocking is then done in the shell by typing:
Code:
su
sh /sdcard/oc.sh
The overclock stays at the set value until the next reboot. I am running @528MHz now for a few days and have encountered no problems at all, battery life is about the same. Speedup is measured in benchmark but as myns buils is ridiculusly fast at stock speed alredy, the speedup is not really noticeable.
590MHz locks my system instantly.
could you provide some more details? for example how to get to a shell in android??
mblaster said:
but as myns buils is ridiculusly fast at stock speed .
Click to expand...
Click to collapse
could you provide a link for this build??
You get a shell if you start the app 'better terminal' or 'terminal emulator'. There is a thread for this build, search is your friend, double posts ain't.
Hi, Recently I have done a package which allows to easy installation of oc script.
First thanks to: whirleyes for oc script.
I did 2 versions:
Manual: You must start manual oc script to have oc (It doesn't start with system).
Autostart: Oc script starts with system at boot (includes init.d support for L9).
Download (v10a-v10g and v20a-v20d):
Manual and Autostart version: http://artasnotebook.you2.pl/?page_id=16
[B/]
Installation:
1. Install zip witch CWM Recovery (manual or autostart version, your choice)
2.
a) For autostart version
Open /system/etc/init.d/98oc with root explorer in text editor
Change values with your choice:
Code:
echo 0 300 980 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1300 > /proc/cpu_control/tweak_cpu
echo 3 1200 1370 > /proc/cpu_control/tweak_cpu
echo 3 frequency voltage > /proc/cpu_control/tweak_cpu
Save. Done
b) Manual version
Open /system/oc/simple with root explorer in text editor
Change values with your choice:
Code:
echo 0 300 980 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1300 > /proc/cpu_control/tweak_cpu
echo 3 1200 1370 > /proc/cpu_control/tweak_cpu
echo 3 frequency voltage > /proc/cpu_control/tweak_cpu
Save. If you want to execute this script:
Open File with Root Explorer in Linux Script Handler and click Execute. You cant also use Termianl Emualtor to execute script.
Done.
artas182x said:
These theards wasn't moved. First is all about L9 and second has cwm zip for replacing sd. I wrote this for L9.
Links:
http://forum.xda-developers.com/showthread.php?t=2096061
http://forum.xda-developers.com/showthread.php?t=2096138
Click to expand...
Click to collapse
As a reply to my intimations to XDA Admins, just got a PM from Admins, that your both great threads are moved in L9 Dev Section.
Great work!
Excuse me for this noob question but, this script is going to improve my battery life??
Roker1 said:
Excuse me for this noob question but, this script is going to improve my battery life??
Click to expand...
Click to collapse
no, this is gonna lower your battery life. the advantage is you will have better performance.
Maybe this script is better (I'm using this for a long time without problems):
Code:
echo 0 333 830 > /proc/cpu_control/tweak_cpu
echo 1 666 900 > /proc/cpu_control/tweak_cpu
echo 2 999 1050 > /proc/cpu_control/tweak_cpu
echo 3 1300 1340 > /proc/cpu_control/tweak_cpu
This will overclock all the freqences (not only the last), and will reach 1,3GHz. This will also undervolt the cpu for a longer battery life
n00b question here - so you dont need an outside app (like SetCPU) for the OC? the script handles it?
Re: LG L9 Overclocking | CWM Zip
Will this overclock.the gpu!?
Sent from my LG-P765 using xda premium
R: LG L9 Overclocking | CWM Zip
projectedv said:
n00b question here - so you dont need an outside app (like SetCPU) for the OC? the script handles it?
Click to expand...
Click to collapse
No we don't need an app like setcpu, just the script.
hkfree said:
Will this overclock.the gpu!?
Sent from my LG-P765 using xda premium
Click to expand...
Click to collapse
As far as I know we can't overclock the gpu with these modules.
Sent from my LG-P760 using xda app-developers app
Can you create a cwm zip to remove the oc stuff?
Odp: LG L9 Overclocking | CWM Zip
Delete /system/etc/init.d/98oc
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
artas182x said:
Delete /system/etc/init.d/98oc
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Thank you very much
Can anybody in this thread help me? My problem is that whenever I set an OC at boot, my phone will hard-freeze about 30 seconds after the script should theoretically finish. It's not the voltages, as I have done extensive stress testing at these voltages when I execute this script in Script Manager post boot, and have tested each voltage and frequency individually. And yet, the thing still freezes every time I either edit this script post-flashing or set this script at boot with Script Manager. Wat do?
DatNexus said:
Can anybody in this thread help me? My problem is that whenever I set an OC at boot, my phone will hard-freeze about 30 seconds after the script should theoretically finish. It's not the voltages, as I have done extensive stress testing at these voltages when I execute this script in Script Manager post boot, and have tested each voltage and frequency individually. And yet, the thing still freezes every time I either edit this script post-flashing or set this script at boot with Script Manager. Wat do?
Click to expand...
Click to collapse
It doesn't work with P760 v10h, tried autostart version.
maybe it's a firmware problem.
Yes this is not working on 10H firmware
Code:
insmod: init_module 'symsearch.ko' failed (Exec format error)
DatNexus said:
Can anybody in this thread help me? My problem is that whenever I set an OC at boot, my phone will hard-freeze about 30 seconds after the script should theoretically finish. It's not the voltages, as I have done extensive stress testing at these voltages when I execute this script in Script Manager post boot, and have tested each voltage and frequency individually. And yet, the thing still freezes every time I either edit this script post-flashing or set this script at boot with Script Manager. Wat do?
Click to expand...
Click to collapse
What exact device do you have?
It may be the stepping from 800Mhz to 1200Mhz . Processors don't like jumping very far between steppings.
Try these steppings and see if they work:
300Mhz
600Mhz
900Mhz
1200Mhz
You may also just have a bad processor. My P769BK has this and I just gave up on overclocking.
sguerrini97 said:
Yes this is not working on 10H firmware
Code:
insmod: init_module 'symsearch.ko' failed (Exec format error)
Click to expand...
Click to collapse
Hope that will work soon
Any news for 10h or 11a?
denzel09 said:
Any news for 10h or 11a?
Click to expand...
Click to collapse
It looks like 10h has different kernel, so probalby overclock modules should be recompiled with 10h kernel source.
thanks for answer,
Hello there. In my Xperia U i flashed Terra ROM and Sliding XU 3.5 kernel. I used Lulzactiveq governor because its very fast on the phone, but when i lock the phone and unlock it after a minute or two the phone is very slow like its clocked to 200 MHz max until i enable the settings again (200 min, 1000 max). I dont have this problem with pegasusq(i dont remember the name) governor but its a litte slower. Any help?
krasimiretov said:
Hello there. In my Xperia U i flashed Terra ROM and Sliding XU 3.5 kernel. I used Lulzactiveq governor because its very fast on the phone, but when i lock the phone and unlock it after a minute or two the phone is very slow like its clocked to 200 MHz max until i enable the settings again (200 min, 1000 max). I dont have this problem with pegasusq(i dont remember the name) governor but its a litte slower. Any help?
Click to expand...
Click to collapse
What scripts you have in /etc/init.d/ ?
Nothing the folder is empty.
krasimiretov said:
Nothing the folder is empty.
Click to expand...
Click to collapse
Maybe it's a kernel issue, or governer, I've never used it.
Try another kernel, if it's still the same you can make a script that set max freq.
Lockinging the phone you mean turn screen off?
Yes when turning screen off. Is there any tutorial for making that script?
krasimiretov said:
Yes when turning screen off. Is there any tutorial for making that script?
Click to expand...
Click to collapse
I don't know about tutorial but you can learn from S98screenstate_script from ThunderBolt.
To get max avaio freqrency:
Code:
AWAKE_MAX_FREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies | awk '{ print $NF }'` ;
to check it worked:in shell type: echo "$AWAKE_MAX_FREQ"
to change max freq:
Code:
echo "$AWAKE_MAX_FREQ" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq ;
to check it work, in terminal type: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Try those commands in shell (terminal emulator or SSH) before you make the script, and also try the script before you put it in /etc/init.d
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.