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

[el_smurfo]

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



Sent from my One S using Tapatalk

There does seem to be a spectrum of GPS related issues...I don't have all that many, while some folks just open up Maps and the phone resets. Maybe this guy got the magic phone that the gyro chipset (not sure if same chip as GPS) just never works...and maybe this log will help track down the cause for others. I remember Intervigil said that the GPS problem appeared to the the I2C link to the chip itself, also Panasonic I thought...

 

[Accountban]

Is there any stable 4.4 rom with no reboots everything I try reboots

Sent from my HTC One S using xda app-developers app

 

[nicknc]

There does seem to be a spectrum of GPS related issues...I don't have all that many, while some folks just open up Maps and the phone resets. Maybe this guy got the magic phone that the gyro chipset (not sure if same chip as GPS) just never works...and maybe this log will help track down the cause for others. I remember Intervigil said that the GPS problem appeared to the the I2C link to the chip itself, also Panasonic I thought...

Yeah, that was tongue-in-cheek.

HTC certainly seems to source a variety of parts for otherwise uniform phone series.

It would be useful to rule out a corrupt data setting though, hence the recommendation for a clean install with no data restore.

A number of us had weird issues after jumping up to CM11 due to legacy settings from CM10.2 that were brought in on the data partition.
Most didn't though, I know.

Sent from my One S using Tapatalk

 

[eabinsan]

There does seem to be a spectrum of GPS related issues...I don't have all that many, while some folks just open up Maps and the phone resets. Maybe this guy got the magic phone that this chipset just never works...and maybe this log will help track down the cause for others. I remember Intervigil said that the GPS problem appeared to the the I2C link to the chip itself...

to me it doesn't seem to be an I2C issue, even though the logs are full of I2C related stuff. I would say that the real problem is that the device that should be on the other side of the I2C is just powered off. I'm trying to build myself a kernel that does not power of the gyro, just for fun let's see how much power this thing really draws....

 

[epsiblivion]

Is there any stable 4.4 rom with no reboots everything I try reboots

Sent from my HTC One S using xda app-developers app

I'm currently running the 1/26 build of 2.15 hboot official cm 11 nightly. no issues that I can see. recovery is cwm 6.0.4.5 linked in OP

---------- Post added at 03:49 PM ---------- Previous post was at 03:49 PM ----------

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

can you describe this? I've never seen this before. what happens?

 

[eabinsan]

to me it doesn't seem to be an I2C issue, even though the logs are full of I2C related stuff. I would say that the real problem is that the device that should be on the other side of the I2C is just powered off. I'm trying to build myself a kernel that does not power of the gyro, just for fun let's see how much power this thing really draws....

seems to be working quite well here....so, if you are not afraid of fastboot and a little power drain (the gyro will not turn off on this build), feel free to test the attached kernel. I tried some multitasking that would previously reboot my phone reliably....but then again, i might just be lucky.

If this works, we hopefully have a very good lead about what needs to be fixed.

oh, and btw: usb accessory detection is also disabled on this kernel. so detecting a dock will not work. i'm just too lazy to do a separate build.

 

[nicknc]

Is there any stable 4.4 rom with no reboots everything I try reboots

Sent from my HTC One S using xda app-developers app

Yep, this one.

Sent from my One S using Tapatalk

 

[The Setlaz]

can you describe this? I've never seen this before. what happens?

Set Schema or NIP lock-screen for a day, randomly, after unlock, you will have a black/grey screen for 1-2 seconds that seems exiting (sliding effect).
In a day, it should happen a few times (pretty randomly).

 

[Brushstroke]

Just wanted to report that the 02/03 nightly is running flawlessly. Looks like the camera FC was fixed.

 

[benyto]

Set Schema or NIP lock-screen for a day, randomly, after unlock, you will have a black/grey screen for 1-2 seconds that seems exiting (sliding effect).
In a day, it should happen a few times (pretty randomly).

What are Schema and NIP lock screen? I don't have those options in my lock screen settings. Are you perhaps referring to PIN and something else? Are you using a language other than English?

For what it is worth, I use a 3x3 pattern for my lock screen security, and I haven't experienced what you're describing.

 

[Aduck79]

seems to be working quite well here....so, if you are not afraid of fastboot and a little power drain (the gyro will not turn off on this build), feel free to test the attached kernel. I tried some multitasking that would previously reboot my phone reliably....but then again, i might just be lucky.

If this works, we hopefully have a very good lead about what needs to be fixed.

oh, and btw: usb accessory detection is also disabled on this kernel. so detecting a dock will not work. i'm just too lazy to do a separate build.

Thanks for your effort!

Tried your kernel. Still no luck I'm afraid.
Compas app not working either, so I think the accelerometer and compas is linked somehow.

From dmesg.log I'm only seeing this related to gyro:

<6>[   13.943201] [GYRO][PANASONIC] Open device node:ewtzmu2
<6>[   13.947382] [GYRO][PANASONIC] Release device node:ewtzmu2
<6>[   13.955837] [GYRO][PANASONIC] Open device node:ewtzmu2daemon
<6>[   14.097054] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[   14.461803] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:

And in last_kmsg.log:

[32250.178204] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[32250.178265] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x3
[32250.178296] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=0, m_status=1,rv_status=0, la_status=0, gv_status=0, 
[32250.178326] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=1
[32250.178357] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.

Overall my One S is very stable. Not seeing reboots.

I will try a clean install of CM11 now.

EDIT: Still nothing after clean CM11. Also tried applying the gyro-kernel afterwards. :-/

 

[thiasB]

Overall my One S is very stable. Not seeing reboots.

I will try a clean install of CM11 now.

already got 3 reboots while playing Ingress today

 

[The Setlaz]

For what it is worth, I use a 3x3 pattern for my lock screen security, and I haven't experienced what you're describing.

Schema = Pattern
NIP = PIN

Sorry for the bad translation :silly:

 

[eabinsan]

Thanks for your effort!

Tried your kernel. Still no luck I'm afraid.
Compas app not working either, so I think the accelerometer and compas is linked somehow.

From dmesg.log I'm only seeing this related to gyro:

<6>[   13.943201] [GYRO][PANASONIC] Open device node:ewtzmu2
<6>[   13.947382] [GYRO][PANASONIC] Release device node:ewtzmu2
<6>[   13.955837] [GYRO][PANASONIC] Open device node:ewtzmu2daemon
<6>[   14.097054] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[   14.461803] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:

And in last_kmsg.log:

[32250.178204] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[32250.178265] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x3
[32250.178296] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=0, m_status=1,rv_status=0, la_status=0, gv_status=0, 
[32250.178326] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=1
[32250.178357] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.

Overall my One S is very stable. Not seeing reboots.

I will try a clean install of CM11 now.

EDIT: Still nothing after clean CM11. Also tried applying the gyro-kernel afterwards. :-/

Sorry to hear that, but my kernel is just supposed to fix the reboots when multi tasking with GPS on (the theory is, that it is not related to GPS but to the Gyro).

But as you get no reboots, this is at least good news for me :angel:

edit: the funny thing about your log is, that it seems to try to turn on the gyro, and the gyro reports back that it is powered off? if this is my kernel, this should not be possible i think.

 

[Aduck79]

Sorry to hear that, but my kernel is just supposed to fix the reboots when multi tasking with GPS on (the theory is, that it is not related to GPS but to the Gyro).

But as you get no reboots, this is at least good news for me :angel:

edit: the funny thing about your log is, that it seems to try to turn on the gyro, and the gyro reports back that it is powered off? if this is my kernel, this should not be possible i think.

I'm no expert in analyzing logs. Maybe the entries from last_kmsg.log is data from previous boot.

I flashed the PAC-man (4.2.2 android) ROM, gyro not working there either. So, I'm close to acknowledge that the sensor must be dead.
Do you know how to locate the sensor inside the phone? Maybe a plug or something has become loose

 

[eabinsan]

already got 3 reboots while playing Ingress today

did you try with my experimental kernel?

 

[thiasB]

did you try with my experimental kernel?

Just flashed it. Will report back

 

[El_Svanto]

I'm no expert in analyzing logs. Maybe the entries from last_kmsg.log is data from previous boot.

I flashed the PAC-man (4.2.2 android) ROM, gyro not working there either. So, I'm close to acknowledge that the sensor must be dead.
Do you know how to locate the sensor inside the phone? Maybe a plug or something has become loose

I would try to RUU back to stock, and if the problem persists then it is most likely hw fault.

From Sweden btw?


Skickat från min One S via Tapatalk

 

[nicknc]

I would try to RUU back to stock, and if the problem persists then it is most likely hw fault.

From Sweden btw?


Skickat från min One S via Tapatalk

+1 to this

Sent from my One S using Tapatalk

 

[Aduck79]

I would try to RUU back to stock, and if the problem persists then it is most likely hw fault.

From Sweden btw?


Skickat från min One S via Tapatalk

Ok, will look into it.

Not Sweden but close. I'm from Denmark