[Q] Proximity sensor sensitivity - Sony Xperia P, U, Sola, Go

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
---

Related

[MODULE] No more MDDI Lags on X10 mini pro custom ROMS

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

{ST15}[Xperia mini] - Decrease Touchscreen sensitivity (Overheat Issue)

I find out that mini's menu and back keys are along with the touchscreen panel. so anyone who have this problem (menu and back key keep pressing like crazy) why because...
(*). phone get heat (not overheat even normal temp lvs) and heat sensitive capacitive touchscreen gets sensitive to that heat and do following things.
- touchpanel menu and back key keep pressing on and on (if Settings>Sound>Haptic feedback is enabled it keeps vibrating) can't do anything on phone
- If somehow disable back and menu keys (system/usr/keylayout/cyttsp_key.kl add # to key 139 and key 158) touchscreen long press and dragging not working if you use panting software and try to draw something it miss lines(keep tapping)
hw_config.sh is like following
Code:
Audio jack configuration
dev=/sys/devices/platform/simple_remote.0
echo 0,201,1600 > $dev/accessory_min_vals # default = 0,200,1600
echo 200,1599 > $dev/accessory_max_vals # default = 200,1600
echo 0,100,280,500,700 > $dev/button_min_vals # default = 0,100,300,600,700
echo 99,199,399,699,5000 > $dev/button_max_vals # default = 99,199,399,699,5000
echo 512 > $dev/btn_trig_period_freq # Button Period Freq(Hz) default = 512
echo 16 > $dev/btn_trig_period_time # Button Period Time(cycle) default = 16
echo 512 > $dev/btn_trig_hyst_freq # Button Hysteresis Freq(Hz) default = 512
echo 16 > $dev/btn_trig_hyst_time # Button Hysteresis Time(Cycle) default = 16
echo 500 > $dev/btn_trig_level # default = 500
# Proximity sensor configuration
dev=/sys/bus/i2c/devices/0-0054/
val_cycle=0
val_nburst=26
val_freq=0
val_threshold=2
val_filter=0
nv_param_loader 60240 prox_cal
val_calibrated=$?
case $val_calibrated in
1)
nv_param_loader 60240 threshold
val_threshold=$?
nv_param_loader 60240 rfilter
val_filter=$?
;;
esac
echo $val_cycle > $dev/cycle # Duration Cycle. Valid range is 0 - 3.
echo $val_nburst > $dev/nburst # Number of pulses in burst. Valid range is 0 - 15. 16 - 31 is a special range for smultron only (SP)
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.
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 3,2,2,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 8000 > $dev/button-backlight-rgb1/max_current
echo 8000 > $dev/button-backlight-rgb2/max_current
echo 1,30,255,54,52,1,65 > $dev/lcd-backlight/als/curve # ALS curve display BL [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 2,48,0,128,128,4,10 > $dev/button-backlight-rgb1/als/curve # ALS curve key LED 1 [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 2,48,0,128,128,4,10 > $dev/button-backlight-rgb2/als/curve # ALS curve key LED 2 [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/red/als/curve # ALS curve RGB(red) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/green/als/curve # ALS curve RGB(green) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/blue/als/curve # ALS curve RGB(blue) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
[B][COLOR="Red"]# Touch panel
dev=/sys/devices/platform/spi_qsd.0/spi0.0
app_id=`cat $dev/appid`
case "$app_id" in
"0x0505")
fw=touch_smultron_innolux.hex
;;
"0x0105")
fw=touch_smultron_sony.hex
;;
"0x0015")
fw=touch_smultron_sony.hex
;;
*)
fw=touch_smultron_sony.hex
;;
esac
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/$fw
[/COLOR][/B]
# TI BQ275xx firmware loader
bq275xx_fwloader
I highlight the line, Touch panel drivers are
/sys/devices/platform/spi_qsd.0/spi0.0 , /system/etc/firmware/touch_smultron_sony.hex , and cyttsp_fwloader
only editable file is touch_smultron_sony.hex
in my opinion it is a Hexadecimal microcontroller machine language
can someone convert this Hex to high level language and fix above mention bugs? (many users are suffering and you could be one to help them!!!)
[touch_smultron_sony.hex](This could be Touch firmware update)
Hi Namidu,
Where are you located? I think that the official service centers have some kind of calibration fix for the touchscreen sensitivity. Check this forum out http://talk.sonyericsson.com/thread/23778?start=780&tstart=0
hope this helps
Thanks to you reply! i think someone can solve above mention bug soon (anyway i think we need experts to solve this please help me to do it)
proprg8 said:
Hi Namidu,
Where are you located? I think that the official service centers have some kind of calibration fix for the touchscreen sensitivity. Check this forum out http://talk.sonyericsson.com/thread/23778?start=780&tstart=0
hope this helps
Click to expand...
Click to collapse
Hey I Live in Sri lanka we got no SE service center, and my phone is rooted!!!
and think i am not the only one
hi, I have xperia mini and I dont have that touch button issue, what if I extract my touch drivers for you and you install them on your phone, would this help you guys?
I dont know how to extract files, but my phone is rooted, you guys have to teach me how to extract. I m always happy to help
metalrawk said:
hi, I have xperia mini and I dont have that touch button issue, what if I extract my touch drivers for you and you install them on your phone, would this help you guys?
I dont know how to extract files, but my phone is rooted, you guys have to teach me how to extract. I m always happy to help
Click to expand...
Click to collapse
That wouldn't be the problem as all devices are shipped with same software, so you would be overwriting the same files.
metalrawk said:
hi, I have xperia mini and I dont have that touch button issue, what if I extract my touch drivers for you and you install them on your phone, would this help you guys?
I dont know how to extract files, but my phone is rooted, you guys have to teach me how to extract. I m always happy to help
Click to expand...
Click to collapse
That helps i think, but if you got that calibration fix it would be better.
1 . Download ADB interface for Windows.
2. go to DOS (type cmd in run) unzip 7z file to C:\
3. Plug your phone to PC and turn on USB Debugging and turn phone to Memorycard mod(MSC).
3. in dos command prompt type C:\tools
4. this command will pull files from your phone to computer
adb pull /system/etc/firmware/touch_smultron_sony.hex c:\touch_drivers/touch_smultron_sony.hex
Click to expand...
Click to collapse
and to copy hw_config.sh
adb pull etc/hw_config.sh c:\touch_drivers/hw_config.sh
Click to expand...
Click to collapse
And Upload Those Files!!!
metalrawk said:
hi, I have xperia mini and I dont have that touch button issue, what if I extract my touch drivers for you and you install them on your phone, would this help you guys?
I dont know how to extract files, but my phone is rooted, you guys have to teach me how to extract. I m always happy to help
Click to expand...
Click to collapse
@metalrawk: If the above method posted bay Namidu does not work fo you, just use any root file manager (like free app File Expert, with root explorer enabled) and copy those files from the phone internal storage, to your sd card. Then it will be easy to copy this two files (touch_smultron_sony.hex and hw_config.sh) to your computer and to upload them here.
thats it? i knew how to simply copy from system
btw here is hex file- http://db.tt/Nl3QeESz
and tell me where is hw_config,sh located. I dont know its path.
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
and anyone tried SE15e .58 firmware on ST15i?
that might solve your problem
metalrawk said:
thats it? i knew how to simply copy from system
btw here is hex file- http://db.tt/Nl3QeESz
and tell me where is hw_config,sh located. I dont know its path.
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
and anyone tried SE15e .58 firmware on ST15i?
that might solve your problem
Click to expand...
Click to collapse
Thanks metalrawk! I will try to use your hex file, to see if it is any diference. What's the firmware version on your phone? I have the firmware version 4.0.2.A.0.42. There is a newer one?
latest firmware for ST15 is 4.0.2.A.42 but SE released 4.0.2.A.58 (newer) for SE15e model which is same as ST15i and used in Japan.
some users flashed that FW in their ST15i and reported that it works.
metalrawk said:
thats it? i knew how to simply copy from system
btw here is hex file- http://db.tt/Nl3QeESz
and tell me where is hw_config,sh located. I dont know its path.
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
and anyone tried SE15e .58 firmware on ST15i?
that might solve your problem
Click to expand...
Click to collapse
its on etc/hw_config.sh and thank you for your help!!
metalrawk said:
latest firmware for ST15 is 4.0.2.A.42 but SE released 4.0.2.A.58 (newer) for SE15e model which is same as ST15i and used in Japan.
some users flashed that FW in their ST15i and reported that it works.
Click to expand...
Click to collapse
I will Try that too friend
On my ST15i the file touch_smultron_sony.hex it's identical with the one posted by metalrawk. Maybe the hw_config.sh will have something diferent to help fixing this capacitive buttons problem...
deejay4angels said:
On my ST15i the file touch_smultron_sony.hex it's identical with the one posted by metalrawk. Maybe the hw_config.sh will have something diferent to help fixing this capacitive buttons problem...
Click to expand...
Click to collapse
Ya me too!
it is same 100%
a new firmware (.62) for S51se (japanese xperia mini) is just released on wotanserver, flash it in ST15i
metalrawk said:
a new firmware (.62) for S51se (japanese xperia mini) is just released on wotanserver, flash it in ST15i
Click to expand...
Click to collapse
Thanks for your help metalrawk.
Anyway, i've just tried both firmwares 4.0.2.A.0.58 and 4.0.2.A.0.61 from wotanserver and there is no change about this capacitive buttons - the problem it's the same: after the temperature goes above 34-35 Celsius degrees, the phone goes crazy beacause the Home and Back buttons starts activating on it's own.
Please upload the hw_config file from your phone so i can do more tests. It is located at the etc folder on your phone internal storage.
This problem can be fixed at a Sony Ericsson Center by doing a software calibration, so i think it's something that can be located in the system files...
http://db.tt/1bDIjTvA here you go
metalrawk said:
http://db.tt/1bDIjTvA here you go
Click to expand...
Click to collapse
Thanks, metalrawk.
Unfortunately, again the file it's identical and with the same MD5 as the one from my phone... And the people from Sony Ericsson they don't want to share their calibaration software, they are doing it only if you give them the phone...
they dont have the calibration sofware, my friend works at sony ericsson service center, when I bought my ST15i, it was having same problem so I gave it to my friend, he said that he will calibrate it on SE website, you need a service center technician account to access that page, but I refused to let him calibrate my phone and asked for replacement certificate instead. he gave me the certificate and took that faulty handset, I gave that certificate to the store and they gave me a new ST15i

CyanogenMod , MIUI brightness Issue

I have xperia ray , and recently i used many cyanogenmod versions , fxp045 to fxp054
I have unlocked bootloaders with s1tool
but with cyanogenmod i have brightness issue , whenever i set brightness and lock my device ,after opening lock brightness reduces automatically
it is damn low & irritating , i dont know why other peoples are not complaining about this issue
EDIT : I got solution = http://forum.xda-developers.com/showthread.php?t=1445546
please help help help help, i really want to use Cyanogenmod
xperia ray said:
I have xperia ray , and recently i used many cyanogenmod versions , fxp045 to fxp054
I have unlocked bootloaders with s1tool
but with cyanogenmod i have brightness issue , whenever i set brightness and lock my device ,after opening lock brightness reduces automatically
it is damn low & irritating , i dont know why other peoples are not complaining about this issue
please help help help help, i really want to use Cyanogenmod
Click to expand...
Click to collapse
Adjust or set the brightness manually until the problem is resolved
first i am very thankful to you for reply , you are totally awesome , again thanks for joining xpiera ray forum (i have seen all your posts , so helpful)
I have tried , but still not working
Lemme explore it
Once i have CM7 installed , i go to settings and set brightness to full
then use my device it works good
After i lock it and open it again i find brightness it reduced to half
i go to settings and check it , it shows brightness is set to full but in reality it is not
is there any problem with my bootloader unlocking method ?
xperia ray said:
first i am very thankful to you for reply , you are totally awesome , again thanks for joining xpiera ray forum (i have seen all your posts , so helpful)
I have tried , but still not working
Lemme explore it
Once i have CM7 installed , i go to settings and set brightness to full
then use my device it works good
After i lock it and open it again i find brightness it reduced to half
i go to settings and check it , it shows brightness is set to full but in reality it is not
is there any problem with my bootloader unlocking method ?
Click to expand...
Click to collapse
It may be a problem with cm7, have you asked in the cm7 thread ?
The brightness works on my the miui roms
Not sure why it doesnt on cm7 so may be rom specific so report on that thread and see if you get any feedback. it may be a known bug
one more question chiefy009 , which miui is best for ray?
and is overclocking not harmful and much battery consuming
Planing to shift on miui
xperia ray said:
one more question chiefy009 , which miui is best for ray?
and is overclocking not harmful and much battery consuming
Planing to shift on miui
Click to expand...
Click to collapse
My miui has tweaks for smoothness and extended settings but try them all.
Overclocking does use battery so undervolt as well, undervolting is trial and error to see if your phone remains stable
Overclocking to high could damage the phone if used over a prolonged period of time I would imagine but a quick google search will get you more info
sent from my gorgeus Xperia Ray
i solved this problem
i used this thread http://forum.xda-developers.com/showthread.php?t=1377125
change the same part in hw_config.sh(inside system/etc)
to:
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds/
echo 0,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 12900 > $dev/torch/max_current
xutienan9520 said:
i solved this problem
i used this thread http://forum.xda-developers.com/showthread.php?t=1377125
change the same part in hw_config.sh(inside system/etc)
to:
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds/
echo 0,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 12900 > $dev/torch/max_current
Click to expand...
Click to collapse
Not working
f**k cyanogenmod
As far as I know you have to change "echo 0,0,0,0" to "echo 3,2,2,0"
xperia ray said:
Not working
Click to expand...
Click to collapse
aaaaaaaaaaa.........mine is working........
xperia ray said:
I have xperia ray , and recently i used many cyanogenmod versions , fxp045 to fxp054
I have unlocked bootloaders with s1tool
but with cyanogenmod i have brightness issue , whenever i set brightness and lock my device ,after opening lock brightness reduces automatically
it is damn low & irritating , i dont know why other peoples are not complaining about this issue
please help help help help, i really want to use Cyanogenmod
Click to expand...
Click to collapse
i had this problem to solved using this guide! if is not working with the file edit, use the als_curve.ini (backup first)
I have this in CM 7
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
echo 1,65,255,24,24,5,128 > $dev/lcd-backlight/als/curve # ALS curve for group1
echo 2,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 450 > $dev/button-backlight/max_current
Last time i changed the whole code , now i think i have to only change
echo 2,0,0,0 TO echo 0,0,0,0
right ?
i replaced lights.semc.so with stock lights.semc.so file , in system/lib/hw
brightness works but only problem is LED light always turn on , in pink color
xperia ray said:
i replaced lights.semc.so with stock lights.semc.so file , in system/lib/hw
brightness works but only problem is LED light always turn on , in pink color
Click to expand...
Click to collapse
That's right, only change the "echo x,x,x,x" phrase.
I tried "echo 3,2,2,0" and "echo 1.5,1,0.5,0 30h". I dont realy know what these parameters exaktly mean, but "echo 1.5,1,0.5,0 30h" works fine on my ray.
You also can change your als_curve.ini in system/etc.
brightness works but only problem is LED light always turn on , in pink color
Click to expand...
Click to collapse
Do you mean the flash LED on the back? And does it keep the brightness you set before you locked?
xperia ray said:
I have this in CM 7
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
echo 1,65,255,24,24,5,128 > $dev/lcd-backlight/als/curve # ALS curve for group1
echo 2,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 450 > $dev/button-backlight/max_current
Last time i changed the whole code , now i think i have to only change
echo 2,0,0,0 TO echo 0,0,0,0
right ?
Click to expand...
Click to collapse
1,65,255,24,24,5,128 to 0.0.0.0.0.0.0
i think i wrote it wrong, sorry
klpp said:
Do you mean the flash LED on the back? And does it keep the brightness you set before you locked?
Click to expand...
Click to collapse
no it is LED of home key , notification indicator in other words
1,65,255,24,24,5,128 to 0.0.0.0.0.0.0
i think i wrote it wrong, sorry
Click to expand...
Click to collapse
Hello xutienan9520,
could you please explain me the difference between
"echo x.x.x.x" and "echo x.x.x.x.x.x.x", i`m noob as f**k.
And what kind of effect does "echo 0.0.0.0.0.0.0" have to your brightness?
klpp said:
Hello xutienan9520,
could you please explain me the difference between
"echo x.x.x.x" and "echo x.x.x.x.x.x.x", i`m noob as f**k.
And what kind of effect does "echo 0.0.0.0.0.0.0" have to your brightness?
Click to expand...
Click to collapse
i also dont know about this , changing above echo to 0,0,0,0,0,0,0 fixed my issue
Change this
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
echo 1,65,255,24,24,5,128 > $dev/lcd-backlight/als/curve # ALS curve for group1
echo 2,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 450 > $dev/button-backlight/max_current
TO
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
echo 0,0,0,0,0,0,0 > $dev/lcd-backlight/als/curve # ALS curve for group1
echo 2,0,0,0 > $dev/lcd-backlight/als/params #[gain],[filter_up],[filter_down],[offset]
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
echo 450 > $dev/button-backlight/max_current
Uhh
If i come back from lockscreen it's still do dark...i use exactly your settings.
I just want the brightness i set in my displaysttings.

Problem Button Backligh witch codename 9.3 no light

hi guys, sorry for my English.
I have installed the codename 9.3 and since I have not installed this light in the buttons (the two middle stripes)
probe to this thread
http://forum.xda-developers.com/showthread.php?t=1695362
and modifying thousand times hw_configh.sh and this tutorial
Below procedure actually work for me on my XPERIA Neo V (MT11i) with codename 9 ROM
XPERIA Neo V has two backlight behind home buttons one coded as rgb1 and other as rgb2 I'm going to disable both
1. This step will persist the values after reboot and completely disable the LED backlights
Go to folder /etc
Open file hw_config.sh
2. Go to line "echo 1 > $dev/button-backlight-rgb-1/als/enable"
Change echo to 0 like "echo 0 > $dev/button-backlight-rgb-1/als/enable"
3. Go to line "echo 1 > $dev/button-backlight-rgb-2/als/enable"
Change echo to 0 like "echo 0 > $dev/button-backlight-rgb-2/als/enable"
4. Now Go to line "echo 900 > $dev/button-backlight-rgb1/maxcurrent"
Change echo to 1 like "echo 1 > $dev/button-backlight-rgb-1/maxcurrent"
5. Now Go to line "echo 900 > $dev/button-backlight-rgb2/maxcurrent"
Change echo to 1 like "echo 1 > $dev/button-backlight-rgb-2/maxcurrent"
in folders button-backlight-rgb1 and 2
modify the brightness to 255 and reset back to 0 not to do
Just delete "20disable-button-backlight" in init.d folder & reboot. No need to edit hw_config.sh, quite easy.
Also, this thread please. No need to open new thread with the same topic.
works! but when lock screen no longer works. Back to work temporarily to adjust the screen brightness, I think it has something to do with the automatic brightness
works! but when lock screen no longer works. Back to work temporarily to adjust the screen brightness, I think it has something to do with the automatic brightness

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

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 &

Categories

Resources