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

[Audioffensive]

Because you don't know what changes were included, by who and how stable they are? That doesn't say the build IS bad, but it CAN be.

I don't really get why I have to justify myself this much for just a simple request. A clean late build of cm-11. Personal preferences, paranoia, whatever reason, does that really matter? If someone has it: great! If no one has it: bad luck. That's it, no harm done, time to move on.
You might not have any objections to a random build, fine, that's up to you.

The fact that I mentioned my findings in this thread is to inform others who might go download the build. They might have similar objections. At least now they can decide for themselves knowing what kind of build it is.

And i don't get why you are wining about official. Official only means it's build by CM but gives no warranty whatsoever.

If you want official go back to stock.

Sent from my One S using XDA Free mobile app

 

[Darknites]

Because you don't know what changes were included, by who and how stable they are? That doesn't say the build IS bad, but it CAN be.

I don't really get why I have to justify myself this much for just a simple request. A clean late build of cm-11. Personal preferences, paranoia, whatever reason, does that really matter? If someone has it: great! If no one has it: bad luck. That's it, no harm done, time to move on.
You might not have any objections to a random build, fine, that's up to you.

The fact that I mentioned my findings in this thread is to inform others who might go download the build. They might have similar objections. At least now they can decide for themselves knowing what kind of build it is.

You justifying because you been given what you wanted but that's not good enough so you come up with silly reasons to not use it.

 

[Forage]

And i don't get why you are wining about official. Official only means it's build by CM but gives no warranty whatsoever.

We determined there wasn't an official build of what I was after, I didn't know that at first. From that point on it was about a clean build.
I already told you I was going to use the provided build a long time ago due to the lack of a better alternative. Despite that it was you who wanted additional clarifications as to why random builds could be a problem. Don't go counting that as me continuing to whine about the initial request.

You justifying because you been given what you wanted but that's not good enough so you come up with silly reasons to not use it.

That's just plain nonsense. If the provided build was what I wanted I wouldn't have a reason to come up with excuses not to use it.

 

[Darknites]

We determined there wasn't an official build of what I was after, I didn't know that at first. From that point on it was about a clean build.
I already told you I was going to use the provided build a long time ago due to the lack of a better alternative. Despite that it was you who wanted additional clarifications as to why random builds could be a problem. Don't go counting that as me continuing to whine about the initial request.


That's just plain nonsense. If the provided build was what I wanted I wouldn't have a reason to come up with excuses not to use it.

Then it looks like you stuck in the past or you could update to cm12.1 like a normal person.

 

[Audioffensive]

....... like a normal person.

Muhahaha LOL

Sent from my One S using XDA Free mobile app

 

[FalconFour]

Then it looks like you stuck in the past or you could update to cm12.1 like a normal person.

Maybe we don't freakin' want Android 5?

I know I don't. The One S is old, and jimmying the latest and greatest OS, designed for today's octo-core beast phones, into an old device with a dual core CPU with limited RAM is sure to cause more problems than it solves.

I'm using CM11 snapshot M12 (the only one available to download since CM packages aren't sorted by CM version) on my One S, and I came here to see if people are having issues:
- waking the phone: 2-4 second wake lag, which also buffers power-button presses and often leaves me nearly snapping my phone in half trying to turn it on as it immediately shuts the screen back off due to buffered presses.
- remembering WiFi APs: at least once a day, all my WiFi networks are completely forgotten. I go to work, I have to reassociate it. I go home, I have to reassociate it. It seems like it happens when the phone is "unclean" shut-down, e.g. a crash reboot or a low battery. This is after clearing /data/misc/wifi multiple times to try to resolve it.
- SoftAP/WiFi internet sharing doesn't work: Turn on ICS, it shuts back off instantly and re-enables WiFi. No error. Just "nope".

Is it so much to ask for a "most stable version" of CyanogenMod 11 before everyone jumps head-first into shoehorning Android 5 into this old thing? I just want a phone that works - and the STOCK ROM is TOO OLD to work with! Software and devices (e.g. Android Wear, Seek Thermal, various other accessories) just don't work with an ancient OS like that.

 

[F-L-Y-E-R]

I just want a phone that works - and the STOCK ROM is TOO OLD to work with!

I guess it's time to get a new phone then...
Issues you have listed have been present for more than a year, so if they have note been fixed I don't think that latest 10 commits for CM11 will fix them. Also there's been over 6 months since CM released lollipop and lately I haven't seen people massively reporting any major issues so again if you are not happy with something try CM12.1 or get a new phone.

 

[Darknites]

Maybe we don't freakin' want Android 5?

I know I don't. The One S is old, and jimmying the latest and greatest OS, designed for today's octo-core beast phones, into an old device with a dual core CPU with limited RAM is sure to cause more problems than it solves.

I'm using CM11 snapshot M12 (the only one available to download since CM packages aren't sorted by CM version) on my One S, and I came here to see if people are having issues:
- waking the phone: 2-4 second wake lag, which also buffers power-button presses and often leaves me nearly snapping my phone in half trying to turn it on as it immediately shuts the screen back off due to buffered presses.
- remembering WiFi APs: at least once a day, all my WiFi networks are completely forgotten. I go to work, I have to reassociate it. I go home, I have to reassociate it. It seems like it happens when the phone is "unclean" shut-down, e.g. a crash reboot or a low battery. This is after clearing /data/misc/wifi multiple times to try to resolve it.
- SoftAP/WiFi internet sharing doesn't work: Turn on ICS, it shuts back off instantly and re-enables WiFi. No error. Just "nope".

Is it so much to ask for a "most stable version" of CyanogenMod 11 before everyone jumps head-first into shoehorning Android 5 into this old thing? I just want a phone that works - and the STOCK ROM is TOO OLD to work with! Software and devices (e.g. Android Wear, Seek Thermal, various other accessories) just don't work with an ancient OS like that.

Em why wouldn't you want to have LP? It runs great even better than kk does and isn't designed for pointless octo-core. Why not just try it and see if you still get all them issues.

Sent from my One M8 using Tapatalk

 

[FalconFour]

All right... I've been on the fence about going to CM12.1. My One S is very much a contender for replacement, as it's got dead capacitive keys as well (the buttons don't light up, nor respond, so I have to use "qemu.hw.mainkeys=0" in build.prop). But I still owe $70 on the dang thing through T-Mo... =P

What really concerned me, though, is that the latest "stable" CM for the Ville is CM10.2 running Android 4.3 - which is over a year and a half old now, and still not compatible with things requiring Android 4.4. So, CM11 got completely skipped over for a "stable" release or even a release candidate, leaving those of us looking for stable "daily drivers" out in the cold. I'd hoped that before CM12 becomes a focus, CM11 would get its final layer of polish, features frozen, bugs ironed out, and get put up for a stable version.

Ultimately, I've been happy with KitKat/4.4, and Lollipop/5.x has a lot of UI design that bugs the hell out of me (particularly the flat design elements, e.g. no outlines around buttons, missing visual cues, etc). That's kind of why I didn't want to be forced into a new phone or having to use CM12 for a stable phone. Also, how would I even know which nightly is likely most stable for a daily driver? I am totally not cool with wiping all my data and starting over (especially applying the build.prop tweak needed to make my phone work) every couple days when I find an issue that might be fixed in a new nightly... :/

I'll give it a go, though, since apparently CM11 is frozen on this thing. I just needed a ramble.

 

[benyto]

@FalconFour

There hasn't been a CM release marked as "stable" for any target since 10.2. Cyanogenmod changed the way it handles releases. Now, instead of naming a release "stable", they treat the snapshot releases (for example, M12 and prior for CM11) as the new "ready for production" ROMs.

If you're waiting for Cyanogenmod to release something in the "stable" channel, you're going to be waiting for a really long time (read: possibly forever). This isn't just for our One S; it's for all targets.

 

[Darknites]

All right... I've been on the fence about going to CM12.1. My One S is very much a contender for replacement, as it's got dead capacitive keys as well (the buttons don't light up, nor respond, so I have to use "qemu.hw.mainkeys=0" in build.prop). But I still owe $70 on the dang thing through T-Mo... =P

What really concerned me, though, is that the latest "stable" CM for the Ville is CM10.2 running Android 4.3 - which is over a year and a half old now, and still not compatible with things requiring Android 4.4. So, CM11 got completely skipped over for a "stable" release or even a release candidate, leaving those of us looking for stable "daily drivers" out in the cold. I'd hoped that before CM12 becomes a focus, CM11 would get its final layer of polish, features frozen, bugs ironed out, and get put up for a stable version.

Ultimately, I've been happy with KitKat/4.4, and Lollipop/5.x has a lot of UI design that bugs the hell out of me (particularly the flat design elements, e.g. no outlines around buttons, missing visual cues, etc). That's kind of why I didn't want to be forced into a new phone or having to use CM12 for a stable phone. Also, how would I even know which nightly is likely most stable for a daily driver? I am totally not cool with wiping all my data and starting over (especially applying the build.prop tweak needed to make my phone work) every couple days when I find an issue that might be fixed in a new nightly... :/

I'll give it a go, though, since apparently CM11 is frozen on this thing. I just needed a ramble.

Do a twrp backup and dirty flash since their is good chance it will work since you already on cm.

Sent from my One M8 using Tapatalk

 

[gohanSS]

hi, anybody have any suggestion to have my full storage back after updating HBOOT to 4.16? I am stuck with 2.34GB

 

[Michael1986]

Hi,
does anybody know, where i - now after CM is dead - can download the lates CM11 (hboot 2.15) rom? i need it to perform S-Off, as with my 12.1 Rom, which i currently have installed, its not possible to do s-off procedure due to only support for PIE files.
Please help.
Thank you!

 

[Strikerr]

Hi,
does anybody know, where i - now after CM is dead - can download the lates CM11 (hboot 2.15) rom? i need it to perform S-Off, as with my 12.1 Rom, which i currently have installed, its not possible to do s-off procedure due to only support for PIE files.
Please help.
Thank you!

ftp://    109.6.236.247/cm-11-20141112-SNAPSHOT-M12-ville.zip
OR
ftp://   46.35.23.30/cm-11-20141112-SNAPSHOT-M12-ville.zip

 

[kdd998]

Another link if needed: https://mega.nz/#!owgm3DgA!XUPzFsHtwjdyvt08fQ0rKenpIeBPTO8JKJw1ishFuvQ