[ROM][4.4.3] CyanogenMod 11 for HTC One S

Search This thread

nicknc

Senior Member
Dec 10, 2009
1,156
331
Your sig says you're on HBOOT 2.16. Are there newer nighlies for 2.16 than 20 Jan? I thought all the CM nightlies being pushed are for 2.15 and we're waiting on others to compile for 2.16 separately?

Lol. 1 broken build and the thread goes silent for hours.

Or it could be everyone is excited about Manning getting his butt whipped tonight....

;)
 

The Setlaz

Senior Member
Jan 6, 2010
217
116
There is also another strangeness happening since the nightlies later than 27/01 (27/01 is the latest without problem). sometimes I could not find out the reason the phone becomes completely inresponsive. screen is off and cannot be switched on, hardware button lights are also off doesn't light up in any case. if enabled notification leds are active. and the phone is actually on. when called from other phone it appears to be ringing but actually it doesn't. And only option to get it off this state is powering down holding power button pressed and power on afterwards. this happened to me all the roms I tried after 27/01. Anyone else is experiencing something similar?

Got this as well, among other screen freeze and unresponsive hardware button. (running 29/01 nightly)
 

epsiblivion

Senior Member
Mar 31, 2010
138
21
Los Angeles
Hi,
I recently got hold of a used htc one s.
I immediately rooted and s-off'ed it. I flashed CM11 nightly and bubba kernel. Then I noticed that the accelerometer didn't work. Tilting in games and launcher doesn't do anything. Do you got a suggestion for what I could do, or is the sensor possibly dead?

Best regards
Anders

Sendt fra min One S med Tapatalk

have you tried just using the stock kernel?

---------- Post added at 11:17 AM ---------- Previous post was at 11:16 AM ----------

Your sig says you're on HBOOT 2.16. Are there newer nighlies for 2.16 than 20 Jan? I thought all the CM nightlies being pushed are for 2.15 and we're waiting on others to compile for 2.16 separately?

unofficial 2.16 builds are now in a separate thread.

---------- Post added at 11:17 AM ---------- Previous post was at 11:17 AM ----------

It's working for me. Try a clean flash.

Sent from my One S using Tapatalk

clean do you mean wipe data as well? or just system/cache
 
  • Like
Reactions: MattDN93

Aduck79

Senior Member
Dec 12, 2010
177
51
Hillerød
yes, the kernel that comes with CM11 is called stock kernel, and you just replaced it with bubba kernel.
To get back to stock kernel you can just reflash your rom or take the .img file in the zip and flash it with fastboot or Flash image GUI app

Thanks, tried a flash of CM11 without Bubba. Wiped cache and dalvik. It's the same. Tilting still not working.

Sendt fra min One S med Tapatalk
 

deniz2694

Senior Member
Aug 17, 2012
293
74
Thanks, tried a flash of CM11 without Bubba. Wiped cache and dalvik. It's the same. Tilting still not working.

Sendt fra min One S med Tapatalk

Maybe it was deactivated in Settings > display > rotation ?

I'd suggest you to test with this app if your accelerometer works or not
 
Last edited:

speedfreak007

Senior Member
May 12, 2010
344
32
I'm on nightly 31-01 and my wifi does not always sees the networks available in the neighbourhood. A reboot often solves the problem.
I turned ART on and have no problems with app compatibility and it definitely makes app startups much faster. My one s really flies!
 

nicknc

Senior Member
Dec 10, 2009
1,156
331
Rotation is activated and the app shows nothing at all :( No colored lines.

I'm afraid that the phone could be damaged somehow.

It's always recommended to do a kernel wipe script between kernel flashes, particularly when you have problems like this.

Sent from my One S using Tapatalk

---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------

have you tried just using the stock kernel?

---------- Post added at 11:17 AM ---------- Previous post was at 11:16 AM ----------



unofficial 2.16 builds are now in a separate thread.

---------- Post added at 11:17 AM ---------- Previous post was at 11:17 AM ----------



clean do you mean wipe data as well? or just system/cache

Wipe everything except for data and sdcard. You will have to flash gapps as well.

Sent from my One S using Tapatalk
 

Aduck79

Senior Member
Dec 12, 2010
177
51
Hillerød
It's always recommended to do a kernel wipe script between kernel flashes, particularly when you have problems like this.
Thanks for your recommendation.

Tried this script: http://forum.xda-developers.com/showthread.php?t=2121584
And then flashed Bubba Kernel. The same, no rotation or tilting :(
Maybe I should look at some logs. If there's hardware malfunctioning, then maybe I can se it in the syslogs.

EDIT: 90% of dmesg.log is filled with:
<6>[ 566.813245] [GYRO][PANASONIC] ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0
Doesn't sound dangerous, but it's still alot of log entries.

In lastk_msg.log this is written about compas/gyro/G-sensor:
Code:
[    1.453380] [COMP][AKM8975] AKM8975 compass driver for pana gyro: init
[    1.453410] [COMP][AKM8975] akm8975_probe_pana:
[    1.453471] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.453502] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.463573] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.463604] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.473706] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.473737] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.483839] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.483869] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.493941] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.493972] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.504074] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.504104] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.514176] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.514207] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.524309] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.524339] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.534411] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.534442] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.544544] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.544575] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.554585] [COMP][AKM8975 ERROR] AKI2C_TxData retry over 10
[    1.554616] [COMP][AKM8975 ERROR] akm8975_probe_pana: set power down mode error
[    1.554616] akm8975: probe of 12-000d failed with error -5
[    1.554646] i2c-core: driver [akm8975] using legacy suspend method
[    1.554646] i2c-core: driver [akm8975] using legacy resume method
[    1.554677] [GYRO][PANASONIC] Panasonic Gyroscope sensor driver: init
[    1.554677] [GYRO][PANASONIC] ewtzmu2: driver version:1.0.0.2
[    1.554707] [GYRO][PANASONIC] 
[    1.554707] Enter ewtzmu_i2c_probe!!
[    1.555501] [GYRO][PANASONIC] init chipset: ret value=2
[    1.555501] [GYRO][PANASONIC] Register input device!
[    1.555623] input: compass as /devices/virtual/input/input6
[    1.555775] input: ewtzmu2_gyroscope as /devices/virtual/input/input7
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [0]=6 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [1]=7 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [2]=18 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [3]=5 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [4]=6 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [5]=7 
[    1.556081] config_VILLE_gyro_diag_gpios 58 pull down
[    1.571219] [GYRO][PANASONIC] EWTZMU2_Power_Off
[    1.571219] [GYRO][PANASONIC] PANA:GYRO:probe success
[    1.571249] i2c-core: driver [ewtzmu2] using legacy suspend method
[    1.571249] i2c-core: driver [ewtzmu2] using legacy resume method
[    1.571249] BMA250 G-sensor driver: init
[    1.571280] BMA250 G-sensor I2C driver: gs_kvalue = 0x670B0BE8
[    1.571463] [GSNR][BMA250] bma250_probe: CHIP ID = 0x03
[    1.571646] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG++: range = 0x03, bw = 0x1f
[    1.572073] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG:use single write--: range = 0x03, bw = 0x0a
[    1.572195] [GSNR][BMA250] bma250_probe: I2C retry 10 times version. OK
[    1.572226] i2c-core: driver [bma250] using legacy suspend method
[    1.572226] i2c-core: driver [bma250] using legacy resume method

I'm not sure if it's ok.

Anyone?
 
Last edited:

The Setlaz

Senior Member
Jan 6, 2010
217
116
Just installed 03/02 nightly. Rotation and Audio work fine for me. (I always wipe cache / wipe dalvik though)

The lock-screen unlock black-screen sliding bug is still there :(
 

nicknc

Senior Member
Dec 10, 2009
1,156
331
Thanks for your recommendation.

Tried this script: http://forum.xda-developers.com/showthread.php?t=2121584
And then flashed Bubba Kernel. The same, no rotation or tilting :(
Maybe I should look at some logs. If there's hardware malfunctioning, then maybe I can se it in the syslogs.

EDIT: 90% of dmesg.log is filled with:
<6>[ 566.813245] [GYRO][PANASONIC] ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0
Doesn't sound dangerous, but it's still alot of log entries.

In lastk_msg.log this is written about compas/gyro/G-sensor:
Code:
[    1.453380] [COMP][AKM8975] AKM8975 compass driver for pana gyro: init
[    1.453410] [COMP][AKM8975] akm8975_probe_pana:
[    1.453471] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.453502] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.463573] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.463604] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.473706] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.473737] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.483839] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.483869] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.493941] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.493972] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.504074] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.504104] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.514176] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.514207] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.524309] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.524339] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.534411] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.534442] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.544544] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.544575] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.554585] [COMP][AKM8975 ERROR] AKI2C_TxData retry over 10
[    1.554616] [COMP][AKM8975 ERROR] akm8975_probe_pana: set power down mode error
[    1.554616] akm8975: probe of 12-000d failed with error -5
[    1.554646] i2c-core: driver [akm8975] using legacy suspend method
[    1.554646] i2c-core: driver [akm8975] using legacy resume method
[    1.554677] [GYRO][PANASONIC] Panasonic Gyroscope sensor driver: init
[    1.554677] [GYRO][PANASONIC] ewtzmu2: driver version:1.0.0.2
[    1.554707] [GYRO][PANASONIC] 
[    1.554707] Enter ewtzmu_i2c_probe!!
[    1.555501] [GYRO][PANASONIC] init chipset: ret value=2
[    1.555501] [GYRO][PANASONIC] Register input device!
[    1.555623] input: compass as /devices/virtual/input/input6
[    1.555775] input: ewtzmu2_gyroscope as /devices/virtual/input/input7
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [0]=6 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [1]=7 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [2]=18 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [3]=5 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [4]=6 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [5]=7 
[    1.556081] config_VILLE_gyro_diag_gpios 58 pull down
[    1.571219] [GYRO][PANASONIC] EWTZMU2_Power_Off
[    1.571219] [GYRO][PANASONIC] PANA:GYRO:probe success
[    1.571249] i2c-core: driver [ewtzmu2] using legacy suspend method
[    1.571249] i2c-core: driver [ewtzmu2] using legacy resume method
[    1.571249] BMA250 G-sensor driver: init
[    1.571280] BMA250 G-sensor I2C driver: gs_kvalue = 0x670B0BE8
[    1.571463] [GSNR][BMA250] bma250_probe: CHIP ID = 0x03
[    1.571646] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG++: range = 0x03, bw = 0x1f
[    1.572073] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG:use single write--: range = 0x03, bw = 0x0a
[    1.572195] [GSNR][BMA250] bma250_probe: I2C retry 10 times version. OK
[    1.572226] i2c-core: driver [bma250] using legacy suspend method
[    1.572226] i2c-core: driver [bma250] using legacy resume method

I'm not sure if it's ok.

Anyone?

Thanks for ruling that out. Are you experiencing the same behavior with a fresh install of CM11? How about other, non-CM11 Roms? You can always do a full backup and then flash a few alternates to see.

Sent from my One S using Tapatalk
 

eabinsan

Senior Member
Sep 24, 2009
78
26
Thanks for your recommendation.

Tried this script: http://forum.xda-developers.com/showthread.php?t=2121584
And then flashed Bubba Kernel. The same, no rotation or tilting :(
Maybe I should look at some logs. If there's hardware malfunctioning, then maybe I can se it in the syslogs.

EDIT: 90% of dmesg.log is filled with:
<6>[ 566.813245] [GYRO][PANASONIC] ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0
Doesn't sound dangerous, but it's still alot of log entries.

In lastk_msg.log this is written about compas/gyro/G-sensor:
Code:
[    1.453380] [COMP][AKM8975] AKM8975 compass driver for pana gyro: init
[    1.453410] [COMP][AKM8975] akm8975_probe_pana:
[    1.453471] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.453502] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.463573] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.463604] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.473706] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.473737] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.483839] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.483869] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.493941] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.493972] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.504074] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.504104] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.514176] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.514207] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.524309] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.524339] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.534411] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.534442] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.544544] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
[    1.544575] qup_i2c qup_i2c.12: I2C slave addr:0xd not connected
[    1.554585] [COMP][AKM8975 ERROR] AKI2C_TxData retry over 10
[    1.554616] [COMP][AKM8975 ERROR] akm8975_probe_pana: set power down mode error
[    1.554616] akm8975: probe of 12-000d failed with error -5
[    1.554646] i2c-core: driver [akm8975] using legacy suspend method
[    1.554646] i2c-core: driver [akm8975] using legacy resume method
[    1.554677] [GYRO][PANASONIC] Panasonic Gyroscope sensor driver: init
[    1.554677] [GYRO][PANASONIC] ewtzmu2: driver version:1.0.0.2
[    1.554707] [GYRO][PANASONIC] 
[    1.554707] Enter ewtzmu_i2c_probe!!
[    1.555501] [GYRO][PANASONIC] init chipset: ret value=2
[    1.555501] [GYRO][PANASONIC] Register input device!
[    1.555623] input: compass as /devices/virtual/input/input6
[    1.555775] input: ewtzmu2_gyroscope as /devices/virtual/input/input7
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [0]=6 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [1]=7 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [2]=18 
[    1.555837] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [3]=5 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [4]=6 
[    1.555867] [GYRO][PANASONIC] $$$ewtzmu2_dir_polarity [5]=7 
[    1.556081] config_VILLE_gyro_diag_gpios 58 pull down
[    1.571219] [GYRO][PANASONIC] EWTZMU2_Power_Off
[    1.571219] [GYRO][PANASONIC] PANA:GYRO:probe success
[    1.571249] i2c-core: driver [ewtzmu2] using legacy suspend method
[    1.571249] i2c-core: driver [ewtzmu2] using legacy resume method
[    1.571249] BMA250 G-sensor driver: init
[    1.571280] BMA250 G-sensor I2C driver: gs_kvalue = 0x670B0BE8
[    1.571463] [GSNR][BMA250] bma250_probe: CHIP ID = 0x03
[    1.571646] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG++: range = 0x03, bw = 0x1f
[    1.572073] [GSNR][BMA250] BMA_Init: bma250_RANGE_SEL_REG:use single write--: range = 0x03, bw = 0x0a
[    1.572195] [GSNR][BMA250] bma250_probe: I2C retry 10 times version. OK
[    1.572226] i2c-core: driver [bma250] using legacy suspend method
[    1.572226] i2c-core: driver [bma250] using legacy resume method

I'm not sure if it's ok.

Anyone?


even more strange: it seems that the gyro gets powered off by accident, and then the device becomes totally unresponsive. Sometimes it just reboots, sometimes it manages to power it on. This happens when multi-tasking. e.g.:

Code:
<6>[ 1494.150373] [TP] Total finger count: 0
<6>[ 1494.823134] [GYRO][PANASONIC] rv_status, -9544, -13401, -999708, 17690
<6>[ 1494.823134]  
<6>[ 1495.247428] [GYRO][PANASONIC] a_status : gsensor data: -14, 22, -708<6>[ 1495.603875] [TP] Total finger count: 0
<6>[ 1496.343201] [GYRO][PANASONIC] rv_status, -9652, -11358, -999867, 6556
<6>[ 1496.343231]  
<6>[ 1497.262413] [TP] Total finger count: 0
<6>[ 1497.863451] [GYRO][PANASONIC] rv_status, -13252, -12531, -999825, 4088
<6>[ 1497.863451]  
<6>[ 1498.472790] [TP] Total finger count: 0
<6>[ 1499.251518] [BATT][CHG] eoc_worker: eoc_count: 0, eoc_count_by_curr:0, pj_chg_full: 0
<6>[ 1499.383152] [GYRO][PANASONIC] rv_status, -9007, -14975, -999416, 29353
<6>[ 1499.383152]  
<6>[ 1499.877216] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1499.882801] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x9
<6>[ 1499.889119] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=1, la_status=0, gv_status=0, 
<6>[ 1499.908591] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=0
<6>[ 1499.914817] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1499.938836] [COMP][AKM8975] ECS_IOCTL_APP_SET_MFLAG,(m, a, t, mv) = (0x0, 0x1, 0x0, 0x0), m_f_times 0
<6>[ 1499.952815] [GYRO][PANASONIC] ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0<6>[ 1499.963802] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1499.968838] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x9
<6>[ 1499.975552] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=1, la_status=0, gv_status=0, 
<6>[ 1499.987669] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=0
<6>[ 1499.994048] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.000732] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.007019] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x1
<6>[ 1500.013123] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<6>[ 1500.025178] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=0
<6>[ 1500.031679] config_ville_gyro_diag_gpios 58 pull down
<6>[ 1500.046726] [GYRO][PANASONIC] EWTZMU2_Power_Off
<6>[ 1500.050419] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.495101] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.501327] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x1
<6>[ 1500.507065] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=0, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<6>[ 1500.518937] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=1
<6>[ 1500.526720] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.536456] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.536547] [COMP][AKM8975] (m, a, t, mv) = (0x1, 0x1, 0x0, 0x0), set m_f_times 1<6>[ 1500.551044] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x5
<6>[ 1500.556752] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=1, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<3>[ 1500.562093] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
<3>[ 1500.562123] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected
<3>[ 1500.562123] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<3>[ 1500.587455] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1383c8, irq:228
<3>[ 1500.587486] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected
<3>[ 1500.587486] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<6>[ 1500.610254] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=1
<3>[ 1500.612665] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1383c8, irq:228
<3>[ 1500.612665] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected<3>[ 1500.612696] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<6>[ 1500.637417] config_ville_gyro_diag_gpios 58 input none pull


 addr:0x69 not connected
<3>[ 1611.503677] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<3>[ 1611.523637] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1343c8, irq:228
<3>[ 1611.523637] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected

It outputs interleaved power-on/power-off messages, which is not good, i guess.
Looks a bit like a race condition.
 

nicknc

Senior Member
Dec 10, 2009
1,156
331
even more strange: it seems that the gyro gets powered off by accident, and then the device becomes totally unresponsive. Sometimes it just reboots, sometimes it manages to power it on. This happens when multi-tasking. e.g.:

Code:
<6>[ 1494.150373] [TP] Total finger count: 0
<6>[ 1494.823134] [GYRO][PANASONIC] rv_status, -9544, -13401, -999708, 17690
<6>[ 1494.823134]  
<6>[ 1495.247428] [GYRO][PANASONIC] a_status : gsensor data: -14, 22, -708<6>[ 1495.603875] [TP] Total finger count: 0
<6>[ 1496.343201] [GYRO][PANASONIC] rv_status, -9652, -11358, -999867, 6556
<6>[ 1496.343231]  
<6>[ 1497.262413] [TP] Total finger count: 0
<6>[ 1497.863451] [GYRO][PANASONIC] rv_status, -13252, -12531, -999825, 4088
<6>[ 1497.863451]  
<6>[ 1498.472790] [TP] Total finger count: 0
<6>[ 1499.251518] [BATT][CHG] eoc_worker: eoc_count: 0, eoc_count_by_curr:0, pj_chg_full: 0
<6>[ 1499.383152] [GYRO][PANASONIC] rv_status, -9007, -14975, -999416, 29353
<6>[ 1499.383152]  
<6>[ 1499.877216] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1499.882801] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x9
<6>[ 1499.889119] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=1, la_status=0, gv_status=0, 
<6>[ 1499.908591] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=0
<6>[ 1499.914817] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1499.938836] [COMP][AKM8975] ECS_IOCTL_APP_SET_MFLAG,(m, a, t, mv) = (0x0, 0x1, 0x0, 0x0), m_f_times 0
<6>[ 1499.952815] [GYRO][PANASONIC] ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0<6>[ 1499.963802] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1499.968838] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x9
<6>[ 1499.975552] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=1, la_status=0, gv_status=0, 
<6>[ 1499.987669] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=0
<6>[ 1499.994048] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.000732] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.007019] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x1
<6>[ 1500.013123] [GYRO][PANASONIC] Gyro AP on:off_status_hal=0,g_status=0, o_status=0, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<6>[ 1500.025178] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=0
<6>[ 1500.031679] config_ville_gyro_diag_gpios 58 pull down
<6>[ 1500.046726] [GYRO][PANASONIC] EWTZMU2_Power_Off
<6>[ 1500.050419] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.495101] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.501327] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x1
<6>[ 1500.507065] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=0, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<6>[ 1500.518937] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=1
<6>[ 1500.526720] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
<6>[ 1500.536456] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
<6>[ 1500.536547] [COMP][AKM8975] (m, a, t, mv) = (0x1, 0x1, 0x0, 0x0), set m_f_times 1<6>[ 1500.551044] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x5
<6>[ 1500.556752] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=1, m_status=0,rv_status=0, la_status=0, gv_status=0, 
<3>[ 1500.562093] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1300c8, irq:228
<3>[ 1500.562123] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected
<3>[ 1500.562123] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<3>[ 1500.587455] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1383c8, irq:228
<3>[ 1500.587486] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected
<3>[ 1500.587486] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<6>[ 1500.610254] [GYRO][PANASONIC] Gyro power on:g_status=0off_status_hal=1
<3>[ 1500.612665] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1383c8, irq:228
<3>[ 1500.612665] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected<3>[ 1500.612696] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<6>[ 1500.637417] config_ville_gyro_diag_gpios 58 input none pull


 addr:0x69 not connected
<3>[ 1611.503677] [GYRO][PANASONIC ERROR] Fail to read sensor data(I2C error): ret value=-107
<3>[ 1611.523637] qup_i2c qup_i2c.12: QUP: I2C status flags :0x1343c8, irq:228
<3>[ 1611.523637] qup_i2c qup_i2c.12: I2C slave addr:0x69 not connected

It outputs interleaved power-on/power-off messages, which is not good, i guess.
Looks a bit like a race condition.

Impossible. We never have race conditions that lead to unresponsive behavior on this phone.

;)

Sent from my One S using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 112
    logo.png

    CyanogenMod 11 is a free, community built distribution of Android 4.4.3 (KitKat) which greatly extends the capabilities of your phone.

    Index:
    1st Post: Official Nightlies for HBOOT 2.15
    2nd Post: Unofficial Builds for HBOOT 2.16
    3rd Post: Changelog


    Installation Instructions (These are all required)
    • Download or Build from Source
    • Download Gapps
    • Wipe Data
    • Flash ROM in Recovery
    • Flash Gapps in Recovery
    • Incase you don't have S-OFF, fastboot flash boot boot.img

    Not Working:
    • You tell me

    Downloads (HBOOT 2.15):
    Official Nightly Builds HBOOT 2.15 Only.
    Google Apps

    Recovery (HBOOT 2.15):
    Beginning with nightly 20140501, several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires kernel support in recovery for CyanogenMod packages to install. Your current recovery is almost guaranteed to not support this change, yet... welcome to bleeding edge!
    Please read THIS
    TWRP | Mirror


    Credits:
    intervigil, h8rift, xkonni, toastcfh, deck, rohan32, flemmard and all the HTC-MSM8960 Team Members.

    XDA:DevDB Information
    CyanogenMod 11, ROM for the HTC One S

    Contributors
    RockR172, intervigil
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Hboot 2.15.xx, S-OFF, Unlocked Bootloader, Custom Recovery
    Based On: CyanogenMod

    Version Information
    Status: Stable

    Created 2013-11-15
    Last Updated 2014-06-09
    49
    CyanogenMod 11 for HBOOT 2.16

    CyanogenMod 11 is now available for HBOOT 2.16

    NOTICE: Due to lack of free time and also not owning an HTC One S anymore, I can no longer compile builds for HBOOT 2.16.
    Worry not, @cikoleko does Nightly builds for HBOOT 2.16 which can be found HERE
    25
    Changelog:

    Latest, more accurate Changelog for Nightlies/Unofficial Builds can now be found HERE.

    cm-11-20131207-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Android 4.4.1

    cm-11-20131206-UNOFFICIAL-ville.zip

    cm-11-20131202-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Hardware Button Configuration is now back

    cm-11-20131129-UNOFFICIAL-ville.zip
    • Latest CM Source

    cm-11-20131125-UNOFFICIAL-ville.zip
    • Latest CM Source - New boot animation and more stuff!

    cm-11-20131122-UNOFFICIAL-ville.zip
    • Latest CM source - Re-introduces Quick Settings and Notification drawer settings
    • Other misc changes to device and kernel sources
    • AOSP release 4.4_r1.2 KRT16S

    cm-11-20131119-UNOFFICIAL-ville.zip
    • Can now be flashed on regular recoveries like TWRP
    • Cherry picked new Audio patches
    • Latest CM source

    cm-11-20131117-UNOFFICIAL-ville.zip
    • Camera App now actually works
    • Some other fixes

    cm-11-20131116-UNOFFICIAL-ville.zip
    • Audio Fixed
    • Bluetooth Works
    • Video Playback

    cm-11-20131115-UNOFFICIAL-ville.zip
    • First Release
    • Fixed SD Card
    • Fixed WiFi
    19
    Okay, with a heavy heart I have to say that I can no longer do builds for hboot 2.16.
    I have too much college work, assignments, practicals n stuff and can't afford to spend time compiling builds in Linux.. :(
    I did try to do builds past few days, but couldn't..
    My advice is, downgrade your hboot to 2.15 and get daily official builds from CyanogenMod. It is not really that difficult/scary to downgrade. I have done it a couple of times when i wanted to test my hboot 2.16 builds when i was on hboot 2.15.
    Also, if anyone wants to do builds for 2.16 feel free to post it in the thread..
    Sorry guys, I tried my best. :)
    Big ups to intervigil and rest of the CM team, you guys rock! \o/ \m/
    18
    Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.

    It's kind of disheartening to see so many people ascribe so many shady ulterior motives to the company (we have no plans for world domination, and it really is discouraging to see so many people knee-jerk react negatively), but ville support hasn't been so great lately, so I figure I owe you an explanation.
    CM Inc is my day job, device support mostly remains a side project for me. The company and open source organization (which are two separate things) has little to do with deciding which devices get support, and to what degree. Device maintainers are largely responsible for the kernels and device trees that actually determine how well most of the device hardware is supported.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone