FORUMS
Remove All Ads from XDA

[Q&A] [ROM] Gohma 2.0 - 12/15/2014 [Android Wear]

n/a posts
Thanks Meter: 0
 
By QA Bot, Guest on 16th December 2014, 12:54 AM
Post Reply Email Thread
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!
16th December 2014, 12:54 AM |#2  
Junior Member
Thanks Meter: 3
 
More
Cool
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?
16th December 2014, 01:34 AM |#3  
Senior Member
Thanks Meter: 4,151
 
Donate to Me
More
Quote:
Originally Posted by Alynna

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?

I'll have a fix shortly, sorry!
16th December 2014, 06:12 PM |#4  
Senior Member
Flag Columbus, Ohio
Thanks Meter: 132
 
More
Quote:
Originally Posted by Alynna

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?

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.
17th December 2014, 11:32 AM |#5  
Senior Member
Flag Madrid
Thanks Meter: 45
 
More
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!
18th December 2014, 04:39 AM |#6  
Junior Member
Thanks Meter: 0
 
More
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?
18th December 2014, 05:27 PM |#7  
freshlysqueezed's Avatar
Senior Member
Thanks Meter: 201
 
More
Quote:
Originally Posted by tharrllz

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?

http://forum.xda-developers.com/show...php?p=54250887

Toolkit should work to get back to stock lollipop.
18th December 2014, 08:49 PM |#8  
Junior Member
Thanks Meter: 3
 
More
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=or dered,nobh,barrier=0 -t auto /
busybox mount -o remount,noatime,nodiratime,noauto_da_alloc,data=or dered,nobh,barrier=0 -t auto /sys
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_al loc,data=ordered,nobh,barrier=0 -t auto /system
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_al loc,data=ordered,nobh,barrier=0 -t auto /data
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_al loc,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 &
The Following 2 Users Say Thank You to Alynna For This Useful Post: [ View ] Gift Alynna Ad-Free
19th December 2014, 05:39 PM |#9  
Senior Member
Thanks Meter: 26
 
Donate to Me
More
Quote:
Originally Posted by Alynna

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:


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
19th December 2014, 10:20 PM |#10  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by myke66

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

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.
The Following User Says Thank You to Alynna For This Useful Post: [ View ] Gift Alynna Ad-Free
20th December 2014, 05:19 PM |#11  
freshlysqueezed's Avatar
Senior Member
Thanks Meter: 201
 
More
Quote:
Originally Posted by myke66

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

A handy utility that you can sideload on our watch is PerfMon by Chainfire:
http://forum.xda-developers.com/show....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.
Post Reply Subscribe to Thread

Tags
auto-qa

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes