yashsingh1/xdaforums huggingface dataset:
[HTC One S] fusk:
Nah man, i'm waiting for the official one.
[HTC One S] Darknites:
It's built the same as official, you just waiting for no reason.
[HTC One S] fusk:
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.
[HTC One S] Loreane Van Daal:
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.
[HTC One S] 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
[HTC One S] 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.
[HTC One S] mikronac.ns:
How it can be rock solid if we have random reboots?
[HTC One S] ATSPerson:
Again I agree. I had many random reboots on CM11. The phone was laggy and sometimes unresponsive. CM12 is really so much better.
[HTC One S] mikronac.ns:
Haha, wait to some buggy commit and that will be the past.
[HTC One S] ATSPerson:
Haha! Yep. That's it. All downhill now for CM12. Me and my big mouth :)
[HTC One S] fusk:
Because i don't.
[HTC One S] Sigma47:
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.
[HTC One S] 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.
[HTC One S] 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.
[HTC One S] 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?
[HTC One S] 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.
[HTC One S] Dharkan:
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.
[HTC One S] 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
[HTC One S] Dharkan:
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.
[HTC One S] ungraphic:
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.
[HTC One S] Rapier:
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...
[HTC One S] ungraphic:
THANK YOU!!!

I made the edit to the file you pointed out from digital to analog. I've made 4 calls today and every single one was flawless. The volume for me is not an issue (its loud enough plus I've already got tinnitus), so I'll leave that be for now. I'll try to post in a few days again with further results to see that the change sticks (4 calls could have been flukes, but it looks like its working great so far).

Thanks again :D
[HTC One S] Rapier:
It should be ok. I never had this issue again after editing that line. Just remember to edit it every time after you flash a ROM

Sent from nowhere over the air...
[HTC One S] ungraphic:
Update:

It's been sometime and the modification has definitely fixed the microphone issue in the headphones cord. Overall, the phone is pretty stable, i get odd reboots here and there but nothing major. I've yet to address the volume fix, its still not a major problem for me.

Thanks again :)
[HTC One S] schlaam:
cm-11-20150105-NIGHTLY-ville.zip download link is not working and I could not find any mirrors. Can someone post a link to the latest CM 11?

Thanks!
[HTC One S] Superchill11:
This isn't exactly what you requested, but I think this is close to what you want. This is his link to a 2.15 CM11 rom:

https://www.androidfilehost.com/?w=files&flid=24764
[HTC One S] ungraphic:
Does anyone have the last official nightly release of CM11 for the HTC One S? My latest one is CM11-20150105 and I can only find CM12 roms to download.

Any help?
[HTC One S] Forage:
I'm stuck with the exact same problem. All cm-11 nightlies have disappeared by now and I'm looking for some fixes after M12. The plan was to still have at least a weekly cm-11 until a cm-12.x milestone or even a cm-11 M13 but it doesn't appear to be happening.

I would love to get my hand on a build after 2015-01-11.
[HTC One S] Rapier:
Development for ville has moved to CM12.1 and there are no longer builds for CM11. Probably the old ones have been removed as they were taking up space
[HTC One S] F-L-Y-E-R:
Just go two posts above and you will find a link for 01-19 build...
[HTC One S] Forage:
"Official" was the key part in the initial request. There's too many builds floating around in which people make changes with their own preferences again.

This looks like just another custom build again.
[HTC One S] F-L-Y-E-R:
It makes no sense what you are saying, if the latest build on CM webpage is 01-15 or something why are you asking for a newer "official" build?

"official" means that it was build by CyanogenMod buildbot... I can sync the source, make no changes, build it and it will be exactly the same as you get from CM page but it will say "unofficial" because I built it on my PC... It doesn't mean that it's a custom build, for example I make builds for HBOOT 2.16 and I do not add anything on top I just cherry pick the commit which makes the ROM compatible on HBOOT 2.16 and that cherry pick is not custom made by someone it's actually made by CyanogenMod team. Obviously if you don't want to install a ROM that was uploaded by a random person it's a different story...
[HTC One S] Forage:
It makes perfect sense to me.

For the date: I'm still on M12. Fixes have been added after 2015-01-11 which I need in order to have a better functioning phone again. Hence the search for a build based on the sources of 2015-01-11 or later.

As for the "official" build: yes, that build might be a clean build based on the CM sources, but there's no way to be sure. You can't tell that based on a file name. It wasn't even a build by the one who posted the link here. That one might include changes I don't want for all I know. I can't trust it so I prefer a CM build by CM.
[HTC One S] Rapier:
There's no such thing. This is what FLYER was trying to explain you. After that date, CM buildbot has stopped building CM11. So only builds you can get are the ones build from source by someone. If you don't trust such builds your only alternative is to build them yourself

Sent from nowhere over the air....
[HTC One S] Forage:
After what date? He did not mention any exact date as far as I can tell. He only used 1-15 as an example the way I read it. I do not know when the nightlies stopped, when the last one was build. Judged by http://www.cyanogenmod.org/blog/the-l-is-for-lollipop it could very well be 1-5 but it also talks about "we are also moving CM11 builds to a weekly status (every Sunday)" and I can't tell if that ever happened because not a single cm-11 nightly can be found any more.
[HTC One S] Rapier:
I'm on mobile right now so search is a pain...but in the CM12 dev thread it's a post about the start of official cm12 nightlies. Since then, cm11 was not build anymore by cm. You could also look for the first cm12 nightly if it's still available. Anything prior to that date was cm11

Sent from nowhere over the air....
[HTC One S] Audioffensive:
Why not just try a cm12 or other custom rom? I build Cyanide and is damn close to flawless. I don't really get the " I can't trust it" part. If you want a rom you can "trust" revert to stock.
[HTC One S] Forage:
After a search for the file link: http://xdaforums.com/showthread.php?p=58430875#post58430875

I.e. my concern was valid, it does contain additional changes.

I guess I'll just take my chances.
[HTC One S] Audioffensive:
And why is that a bad thing?
[HTC One S] Forage:
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.
[HTC One S] Rapier:
I could name a dozen of changes that broke our builds during the time, changes that were included by official CM team. So those builds can be bad as well, they're nightlies. People here just tried to help you, giving what they have. If you're not trusting or not willing to flash those builds, as you say...bad luck
[HTC One S] Audioffensive:
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.
[HTC One S] Darknites:
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.
[HTC One S] Forage:
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.
[HTC One S] Darknites:
Then it looks like you stuck in the past or you could update to cm12.1 like a normal person.
[HTC One S] Audioffensive:
Muhahaha LOL
[HTC One S] FalconFour:
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.
[HTC One S] F-L-Y-E-R:
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.
[HTC One S] Darknites:
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.
[HTC One S] 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. ;)
[HTC One S] benyto:
[MENTION=1308820]FalconFour[/MENTION]

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.
[HTC One S] Darknites:
Do a twrp backup and dirty flash since their is good chance it will work since you already on cm.
[HTC One S] gohanSS:
hi, anybody have any suggestion to have my full storage back after updating HBOOT to 4.16? I am stuck with 2.34GB
[HTC One S] 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!
[HTC One S] Strikerr:
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
[HTC One S] kdd998:
Another link if needed: https://mega.nz/#!owgm3DgA!XUPzFsHtwjdyvt08fQ0rKenpIeBPTO8JKJw1ishFuvQ
[HTC One S] prohozhiy:
Hi guys

maybe someone has the last five (maybe three or two) Official Nightly Builds HBOOT 2.15 - CM 11 lying around

see the whole topic - just do not have time
[HTC One S] adamfirari:
first impressions .

sound quality seems to better and new boot animation is awsome
[HTC One S] guandalfthegrey:
Doesn't build here... where is the magic in you? ;)
[HTC One S] RockR172:
built with no issues here..

------------

2nd post updated with 2.16 build..

Enjoy!
[HTC One S] F-L-Y-E-R:
New boot animation, YES!
[HTC One S] fusk:
The new version doesn't show up in updates, isn't it supposed to ?

Also, in updates it says 22 is downloaded but not installed even tho it is.
[HTC One S] adamfirari:
it is unofficial.it wont show up in updates.You should flash manually.
[HTC One S] el_smurfo:
Ugh. I thought we got rid of Cid...then they go and incorporate and need a logo
[HTC One S] Insecret:
is there any solution for long-press recent button for recent apps and normal press for menu button ? :D
[HTC One S] fusk:
Seems like some of the google apps aren't working any more, android marked won't connect, and mail uninstalled it self or the update did.
[HTC One S] dbals:
Installed, running well- had to re-flash gapps. Gmail, search, play store all work. Seems like battery usage is better- 3 hours of use ( 15 minutes of Pandora, a dozen apps to update, gmail sync read a dozen emails, tried search, all using wifi) about 4.7% per hour

Also have S-On
[HTC One S] el_smurfo:
You need to reflash gapps each time still.

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Somewhere in this thread, I posted a link to how to directly edit the button settings...sorry, can't find right now. There are also apps like this one that should make the file edits for you. Haven't tried, because my button mapping carried over from 10.2

http://xdaforums.com/showthread.php?t=850464
[HTC One S] nicknc:
I did a full wipe this time, restoring data after the install to see if it would make a difference. Still getting bootloops after a reboot, but they are very strange now-- get tons of graphics glitches, extremely slow boot animation, etc-- it takes about 5 minutes for the animation to fully load on screen.

Manually powering down fixes them, of course, but it is interesting that the behavior has changed.

The phone acts like its completely throttled during the bootloops. Has anyone looked into a GPU issue? This would also explain the sudden reboots during maps (I've noticed Waze is also very laggy to render the map), and would also explain the choppy booting folks have always gotten during the bootloop period.

Really the only time I've ever gotten random reboots is with apps that use a lot of rendering, now that I think about it.
[HTC One S] el_smurfo:
Last I heard, the reboot and bootloops were different animals. The rebooting during GPS stuff was some sort of I2C issue. The bootloops are a kernel issue where the second CPU core does not come on line during some warm boot situations which is why it boots slow and jerky.

BTW, this guy seems to imply that the reason the gapps are not getting backed up is because CM doesn't back up odexed files, which is what is being provided by the PA gapps package. maybe once "official" gapps are released on goo.im, the backup script will work again?

http://xdaforums.com/showpost.php?p=47831043&postcount=1057

BTW, apparently app ops is still in KK, just buried. Until CM gets the Privacy Guard working again, there's this

http://www.androidpolice.com/2013/1...-ops-from-color-tiger-and-enhanced-with-root/
[HTC One S] nicknc:
PA gapps were backed up fine for me on CM10.2 flashes, so I don't know it has anything to do with odexed gapps or not (unless the 4.4 PA gapps are explicitly NOT deodexed, and the 4.3 gapps are)

Here's the thing: I don't use GPS much at all. Most of my reboots occur while using apps with lots of rendering, like browsers, games, etc..

I mentioned the Waze choppy panning simply because it was new with CM11-- never had an issue panning the map before.

Have you seen the same graphical glitches during bootloops with this new version of CM11? I'm getting text stretched out, incorrect colors, inverted stuff, and REALLY slow animation (before it was choppy, but this is less than 1 fps).

That's what's making me wonder more about GPU issues.
[HTC One S] el_smurfo:
are you sure you flashed the kernel and are not using bubba? that sounds like the same problem I had when the bubba kernel build was screwed up. op said not to use bubba for this build
[HTC One S] nicknc:
Lol, yep, not using Bubba. I even ran Awesome kernel wipe to make sure nothing carried over.

Using stock kernel, 3.4.11-gc581297
[HTC One S] usaff22:
Latest build is really glitchy for me. Having trouble getting it to boot.

Edit: it won't even boot. When it does, only one core is online. :\

Using 2.16 build

Wouldn't recommend flashing it, or if you have and it is bootlooping like mad, reinstall this

https://docs.google.com/file/d/0ByErX6Iy7BiSc2l6V19FMzlsRzA/edit?usp=sharing

with adb sideload feature.