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

Search This thread

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
253
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...
 
Last edited:

nicknc

Senior Member
Dec 10, 2009
1,156
331
83
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

Senior Member
Sep 24, 2009
78
26
0
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 :D let's see how much power this thing really draws....
 

epsiblivion

Senior Member
Mar 31, 2010
138
21
0
Los Angeles
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

Senior Member
Sep 24, 2009
78
26
0
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 :D 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.
 

Attachments

  • my_boot_no_gyro.img
    5.9 MB · Views: 5

benyto

Senior Member
Dec 3, 2013
51
10
0
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

Senior Member
Dec 12, 2010
177
51
0
Hillerød
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:
Code:
<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:
Code:
[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. :-/
 
Last edited:

eabinsan

Senior Member
Sep 24, 2009
78
26
0
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:
Code:
<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:
Code:
[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

Senior Member
Dec 12, 2010
177
51
0
Hillerød
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 :)
 

El_Svanto

Senior Member
Jul 4, 2013
129
43
0
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
 

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