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

[Darknites]

Nah man, i'm waiting for the official one.

It's built the same as official, you just waiting for no reason.

 

[fusk]

It's built the same as official, you just waiting for no reason.

I don't mind waiting, there's probably a reason why they haven't even released experimentals yet. As i can see from the unofficial CM12 thread there's quite a lot of stuff not working/bugged.

 

[Loreane Van Daal]

I don't mind waiting, there's probably a reason why they haven't even released experimentals yet. As i can see from the unofficial CM12 thread there's quite a lot of stuff not working/bugged.

Actually, less things then on 4.4.4. Rom is fast and stable, not a single reboot. That I couldn't say for KK, nor I had this performances on KK.

 

[ATSPerson]

I'll second that. I tried CM12 on a whim when it first appeared just over a week ago, thinking I'd soon restore my phone to the M12 ROM I was running l, but it ran so much more smoothly than CM11 I didn't bother. Everything I need is functional.

Sent from my HTC One S
hboot: 2.15
radio 35a.32.45.27

 

[fusk]

I have the same thing with 4.4.4, no reboots, fast and stable. And everything works. I'm not doubting that his build doesn't run smooth. But there's quite a few items not related to smoothness that doesn't work/bugged. I don't mind waiting a bit for the worst bugs to get cleared out. CM11 is rock solid, so i'm ok with that for while more.

 

[mikronac.ns]

I have the same thing with 4.4.4, no reboots, fast and stable. And everything works. I'm not doubting that his build doesn't run smooth. But there's quite a few items not related to smoothness that doesn't work/bugged. I don't mind waiting a bit for the worst bugs to get cleared out. CM11 is rock solid, so i'm ok with that for while more.

How it can be rock solid if we have random reboots?

Sent from my One S using XDA Free mobile app

 

[ATSPerson]

Again I agree. I had many random reboots on CM11. The phone was laggy and sometimes unresponsive. CM12 is really so much better.

Sent from my Nexus 7 using XDA Free mobile app

 

[mikronac.ns]

Again I agree. I had many random reboots on CM11. The phone was laggy and sometimes unresponsive. CM12 is really so much better.

Sent from my Nexus 7 using XDA Free mobile app

Haha, wait to some buggy commit and that will be the past.

Sent from my One S using XDA Free mobile app

 

[ATSPerson]

Haha, wait to some buggy commit and that will be the past.

Sent from my One S using XDA Free mobile app

Haha! Yep. That's it. All downhill now for CM12. Me and my big mouth

Sent from my Nexus 7 using XDA Free mobile app

 

[fusk]

How it can be rock solid if we have random reboots?

Sent from my One S using XDA Free mobile app

Because i don't.

 

[Sigma47]

Sometimes the phone reboot... Any other with the sale problem?

Yeah, I'm having reboots too. New to this device (just inherited it), i'm rollin Hboot 2.15 with s-off. Anybody solve this? Are there builds that are less likely to have reboots and other drawbacks? Just looking for something stable from the KK era while LL gets worked out.... thanks in advance.

 

[ATSPerson]

Honestly, the Unofficial CM12 ROM is running much better than any KK ROM I tried. All the CM11 based ROMs have random reboot issues. But if you really want KK the smoothest I tried was Liquid Smooth but like anything in life YMMV.

 

[Sigma47]

Random Reboots

Been rolling this for a few weeks now. First the snapshot then a recent nightly. Both installed from clean wipes. My consensus is that the ROM is unstable for broad spectrum daily use. Phone has rebooted while trying to show friends photos in gallery, while trying to take photos, while driving and using nav, and while talking. I use my phone everyday in the car on BT to listen to tunes, nav, talk etc and I know that this tests most of the ROMs features so it may work for your needs if you don't use all of these features.

 

[Dharkan]

Guys I have a problem

I forgot installing clockwork recovery before I started now I can't go to recovery or reboot my phone

What should I do?

 

[kdd998]

Try to hold power during more than 10 seconds. It should either reboot or shutdown.
Then hold volume down during the reboot (or power on) and you should get into bootloader. From there you'll be able to flash a recovery (fastboot flash recvovery <filename>).

Don't panic if it doesn't work the fist time, I often need to try 2 or 3 times as the volume down button is kind of bad.

 

[Dharkan]

Try to hold power during more than 10 seconds. It should either reboot or shutdown.
Then hold volume down during the reboot (or power on) and you should get into bootloader. From there you'll be able to flash a recovery (fastboot flash recvovery <filename>).

Don't panic if it doesn't work the fist time, I often need to try 2 or 3 times as the volume down button is kind of bad.

I can't do it, I chose recovery on bootloader but phone tried to boot, nothing happened only a red exclamation mark picture came up.

 

[kdd998]

I believe this is the stock recovery.

See step 10 of method 2 from this post: http://android-revolution-hd.blogspot.fr/2013/12/how-to-manually-install-ota-update.html

First hold volume up, then (with volume up held down) press power button to enter the main recovery menu. This keys combination may vary from device to device. Try different keys combination if the above one doesn't work (might be all three keys all together too)

 

[Dharkan]

I believe this is the stock recovery.

See step 10 of method 2 from this post: http://android-revolution-hd.blogspot.fr/2013/12/how-to-manually-install-ota-update.html

Guys getting into boot screen is not the problem. My phone is soft bricked. I can't do factory reset or any kind of recovery.

 

[ungraphic]

My earbuds microphone wont work during calls...I'm running the latest nightly, anyone experiencing this? I have to unplug them every time I receive a call...other than that... everything's working flawlessly

Sent from my One S using Tapatalk

That's the second time someone has reported this.

Try cleaning the plug and blowing out the port

I'm having the SAME problem. I'm on a nightly release; 11-20150105. However, it does *sometimes* work as normal, but the fix for it now is to unplug and plug back in a couple or more times and then it finally kicks in. What I've noticed is that the volume in the headphones is also a little lower when the microphone isn't working.

Could a different radio or kernel help? I'm currently on 1.15.50.05.29_10.30.50.08U. Kernel is 3.4.82-g0129413. It's really unfortunate because I use a single in-ear headphone and mic when in the car ('hands free'), so this gets used a LOT as I do 160km every day. Other than that, the ROM is absolutely flawless, nothing else seems to be faulty, no random reboots, nothing. It's basically 99.7% complete.

 

[Rapier]

I'm having the SAME problem. I'm on a nightly release; 11-20150105. However, it does *sometimes* work as normal, but the fix for it now is to unplug and plug back in a couple or more times and then it finally kicks in. What I've noticed is that the volume in the headphones is also a little lower when the microphone isn't working.

Could a different radio or kernel help? I'm currently on 1.15.50.05.29_10.30.50.08U. Kernel is 3.4.82-g0129413. It's really unfortunate because I use a single in-ear headphone and mic when in the car ('hands free'), so this gets used a LOT as I do 160km every day. Other than that, the ROM is absolutely flawless, nothing else seems to be faulty, no random reboots, nothing. It's basically 99.7% complete.

For those having headset/headphone mic not working try the following:
- using a root file explorer (like the included CM file explorer or ES File Explorer), open the /system/build.prop file
- look for the following line: "persist.audio.handset.mic=digital" and change it to "persist.audio.handset.mic=analog" (change the bits in red)

It should work. Reason: for whatever cause, when an AOSP ROM is built, this line is included in build.prop. While this may work on majority of the phones, for Ville it seems not. The behavior if this is set to digital is distorted voice heard by other party or no sound at all, interruptions and so on. I had this issue on all AOSP ROMs so now I edit this line "by default" on any ROM after flashing (or you can edit the file in the ROM zip before flashing). It is valid for KK and LP as well

For the low volume issue there are some tweaks made by Darknites and others by me (they are in several threads like the CM12 thread or Candy5 thread). They're made for LP basically but I think the files are the same between KK and LP. Make a backup of the original file anyway.
All is about altering some values in a file called snd_soc_msm_2x located at /system/etc/snd_soc_msm. You cand extract this file from the phone and edit it on your PC with a txt editor like Notepad+. Look for some entries in the "Device section"(s), do not touch other sections. There are some headset, voice, headpone and so on device entries and each has it's own volume set, usually somewhere between 60-70. You can SLIGHTLY (and I MEAN SLIGHTLY) increase these values (try with 1 to 5 maximum) so if something is 60 make it 65. DO NOT increase these values too much as it can damage your headset or bring distorted sound if they cannot handle the volume.
NOTE: volume heard during Viber, Skype and similar calls it's set by altering the entries containing "VOIP" (Voice Over IP). Adjust them same way

Good luck...