yashsingh1/xdaforums huggingface dataset:
[HTC One S] Da9L:
Girlfriend is using Team Venoms Viper One rom.. A rather old one running JellyBean. I was going to switch to this, but would like to hear if i should switch bootloader, as her device is running 2.15? I see that this rom is also made for 2.15 hboot, but are the ones for hboot 2.16 more stable? And are there any specific build that runs stable enough to be used for daily?
[HTC One S] F-L-Y-E-R:
They are exactly the same, hboot 2.15 is officially supported so it gets updates more frequently, hboot 2.16 only has more internal storage.
[HTC One S] Da9L:
But which is the most stable? Im not sure how to read their "builds" .. There are snapshots, and nightlies.. Which should i consider for highest stabability
[HTC One S] F-L-Y-E-R:
Oh you meant which release is the most stable, unfortunately I cannot answer your question as I've been always using the latest NIGHTLY but for several months I've been experiencing problems with camera not starting up (reboot fixes the problem), I have a new phone as well so you better wait for someone else to answer your question.
[HTC One S] Hauk92:
I think all somewhat current builds auf CM12 have the camera issue and CM13 will require hboot 2.16.

So for CM11 and CM12 it should make the most sense to run hboot 2.16 and the latest nightly build from the forum (not the official one, since it is for 2.15).
[HTC One S] Loreane Van Daal:
I vote for 2.15. And Candy ROM. It has both 2.15 and 2.16 hboot support so You can decide for yourself. After almost five years ville is still a good companion. I think tried every ROM/kernel/radio for ville, including those with 2.16 hboot, and got settled it with 2.15 and Candy. Link for Candy http://xdaforums.com/showthread.php?t=2964931
[HTC One S] Anthe:
I'm not risking any bugs concerning 3G on my Ville. So yeah, here's another vote towards 2.15 support. I'm super excited for CM13!

HTC One S lives on!
[HTC One S] fax11:
Hi please where did you find the CM13 build ? Is it for Hboot 2.15 or 2.16 ?

Thanks !
[HTC One S] kdd998:
I built it from the sources. It's only for 2.16 and not working. I tried to build yesterday but my repos are broken. Maybe this weekend.

There are patches lacking at this time (like http://review.cyanogenmod.org/#/c/141472/). I'll try a build with these…
[HTC One S] F-L-Y-E-R:
New build

#Added 03/05

#Tested
[HTC One S] DaCaiSua:
help me

Jack headphone 3.5 not working in rom 5.1 ( rom 4.2.2 beat audio still working)
[HTC One S] letsurock:
Looks like only hboot 2.16 might be getting CM 13.0.
[HTC One S] pavel.bosco:
it should be put in a way that finally 2.16 become the official one (if I get it correct), and this is great
[HTC One S] bakmanhans:
As a hboot 2.16 Ville owner I am pleased to hear that finally this becomes CM13's standard hboot version.

Verstuurd vanaf mijn One S met Tapatalk
[HTC One S] Gollut:
I have installed this rom and everything is ok, except the problem that during the call back speaker is set as default instead of the front one. Do you know the solution?
[HTC One S] bakmanhans:
With "this ROM" you mean CM 12.1? I haven't had this issue. Not sure how to help. Sorry.
[HTC One S] moozon:
If anyone is interested, I built cm13 and everything works fine, no crashes, not reboot. Camera, sensors works fine too. Hboot 2.16

Download
[HTC One S] waver1967:
nice :)

hboot 2.15 or 2.16 ?
[HTC One S] Winstarshl:
Only 2.16!
[HTC One S] letsurock:
No MD5 error? I am using TWRP 3.0 M2

Sorry works fine.
[HTC One S] moozon:
MD5sum of zip file on AFH is correct. Try download again
[HTC One S] letsurock:
Your file works fine. The problem was I built CM as you did, same filename. I forgot to remove my md5.

PS: My build doesn't boot.
[HTC One S] moozon:
try rebuild with 'make clean'
[HTC One S] bakmanhans:
Maybe a good time to create a new CM13.0 unofficial thread?
[HTC One S] mr mister:
Hi is CM13 build good enough for daily driver? Also what is TWRP version recomended for ?

Thx
[HTC One S] letsurock:
Yes, it works gooood!!! I have used TWRP 3.0 M2 for flashing.
[HTC One S] vp1407:
This version of cm13 works extremely well! Everything works, haven't had any crashes/reboots yet and battery life isn't bad either. Thanks for making it happen :).
[HTC One S] VilleC2cro:
Hi, how can I port this rom to VilleC2 (Snapdragon S3 MSM8260 1.7ghz,Adreno 220 GPU) version of the phone? I've rooted the phone because the stock htc android crashes a lot lately, I suspect Google trickery with new app versions, and I would like to update to this rom. Thank you
[HTC One S] Loreane Van Daal:
Well, if anyone knew how to port any of ville roms to villec2, that phone would have better life. Or, maybe it's to much of hassle to do it so no one actually wanted to. Anyway, if you are up to it, jump to https://wiki.cyanogenmod.org/w/Doc:_porting_intro and read it.
[HTC One S] qd42:
I can also confirm that moozon's CM 13 build works great for me, it works even better than last 12.1 builds in terms of overall performance and camera bugs.
[HTC One S] tyler9999:
New release cm13.0-20160514 androidfilehost.com/?fid=24533103863139912

I confirm no issue so far, good performance.
[HTC One S] sorewinner:
Thanks for building & uploading, [MENTION=7476499]tyler9999[/MENTION]. I can confirm that performance is much improved over the 20160504 build, at least for me.
[HTC One S] bakmanhans:
Nice to hear about the performance and stability of CM13 for our HTC One S.

Please will somebody take responsibility and open a new thread discussing CM13 development?!
[HTC One S] tyler9999:
I'm sorry for misunderstanding, I have not built anything, I'm just a lucky owner of a htc one s :D

I found and reported the mozon link.

Unfortunately after some tests I found a issue that concerns the bluetooth pair with BT audio (car etc): It is not possible to use simultaneously Phone Audio and Multimedia Audio the phone crash and rebooting. The workaround is to use only Phone Audio (for phone calls) or only Multimedia Audio (for music etc). This issue seems to be a common problem in several releases of other models... we hope to be resolved.

Regards and ville still alive :)
[HTC One S] moozon:
New build CM13 from 2016/05/17 . Not tested. Changelog

Download
[HTC One S] MoeDee:
So you do not experiencing dialer crash?

Which gapps are you using with it then?

And yes I do use cm13 type gapps..
[HTC One S] vp1407:
I call +1 hours a day for work and the dialer hasn't crashed yet. I flashed the following gapps package (ARM, 6.0, mini):

opengapps.org/?api=6.0&variant=mini

(ps: I can't make the link "clickable" since I haven't made the required amount of posts yet)

Further report about the cm13 rom: still fast and stable. Concerning battery life, I get about a full day (wifi + 3G turned on) with between 1,5 and 2 hours onscreen time, which is about the same as I got with other roms since I call a lot.
[HTC One S] Tamlins:
Hi,

I'm testing CM13 since yesterday.

My little feedback .... it's ....Fast and furious :)

I had a little problem "google play services stopped" . I resolved it by a deeper wipe and re-flash the ROM. Now, it's really good, no restart, Camera ok , gps ok , OTG ok , bluetooth car audio (calls) ok ( Alpine)

I'm using gapps micro 6.0 from there: https://devs-lab.com/android-m-gapps-6-0-x-download.html

Flashed with TWRP 3.0 M2

We really need a CM13 thread :)
[HTC One S] htc-2016:
WE HAVE IT NOW :o

[ROM][6.X][Unofficial] CyanogenMod 13 HTC One S: http://xdaforums.com/htc-one-s/general/rom-cyanogenmod-13-htc-one-s-t3381115
[HTC One S] Tamlins:
Great :) gg

Maybe you should specify that it's for 2.16 only :)
[HTC One S] MoeDee:
Installed with gapps mini and all seems well except BT media + phone audio ,

Media works but I'd phone call during media no switch to phone audio and then after dial something crashes not sure what exactly
[HTC One S] The Setlaz:
Just flashed it tonight with OpenGapps Mini, so far so good and very fast! Thanks for the build!

(had to SuperCID, S-OFF - had downgrade to CM11 for to get Facepalm S-OFF working -, flashed Hboot 2.16 with radio 1.20, TWRP 3.0.2 and that's it! All went pretty smoothly!)
[HTC One S] pavel.bosco:
why it is not in android development folder?
[HTC One S] Laus_bub:
can i flash hboot 2.16 over ville s3 with hboot 2.15 - or will i get a broken phone?
[HTC One S] letsurock:
Don't flash it. Your roms are posted in http://xdaforums.com/htc-one-s/c2-development section. Or else, the device will be of no use.
[HTC One S] htc-2016:
Did it! Thanks for the information :)

Because I didn't wanted to hack the forum right now... Maybe a mod or admin can move it! I would appreciate it!

Nice to hear that! Would it be possible to write a mini guide to put it in the main thread for the ROM? That would be wonderful!!! :o :fingers-crossed: I'm specially looking for a how to coming from stock without modifications (S-ON, No custom Recovery, Stock Hboot, No root, no unlock bootloader, ...)
[HTC One S] The Setlaz:
I unlocked bootloader, root, changed recovery a very long time ago so I won't talk about this as I don't remember anything from it.

But for people already using Custom ROM, here we go:

1. Get SuperCID

http://xdaforums.com/showthread.php?p=26516911#post26516911

Step 7, CWS__001 was HTC__203 for mine (depends on your operator) and at offset 0x214

You need to use an Hex editor for that. On Ubuntu I used Bless Hex Editor

2. Get S-OFF using Facepalm S-OFF

http://xdaforums.com/showthread.php?t=2155135

IMPORTANT: Need to revert to at least CM11 or you will get stuck with the following error when doing last step:

adb shell su -c "/data/local/tmp/soffbin3"
error: only position independent executables (PIE) are supported.

3. Get HBOOT 2.16

http://xdaforums.com/htc-one-s/general/guide-how-to-install-hboot-2-16-time-t2898605

Link is dead, see post from kdd998 on page 3:

That contains radio 1.20.

Of course, change commands from the tuto with the proper firmware name from kdd988.

If you encounter Error99 instead of Error92 stop the process, return to fastboot and do the following:

4. Get TWRP 3.0.M2

Download TWRP for Ville: http://android.cmphys.com/twrp-ville/

fastboot flash recovery recovery_name.img

5. Wipe everything and format partition to F2FS

Boot to TWRP and wipe/format

If you do not format, you may encounter "Unable to mount /cache" error

6. Push ROM

Use adb sideload or adb push

7. Push Gapp package

8. Install

ROM and Gapps

9. Enjoy

:good:
[HTC One S] moozon:
New build CM13 from 2016/05/20. Only for Hboot 2.16 Changelog
[HTC One S] tyler9999:
Thanks Moozon!

Can anyone confirm if the bluetooth problem (BT Audio + Phone Audio) is solved with 2016/05/20 version?
[HTC One S] MoeDee:
Will download later ... In a few hours and report back..
[HTC One S] LS.xD:
Thank you [MENTION=4765686]moozon[/MENTION] :) Finally someone brought CM13 to our beloved One S. Just flashed the rom and will post a feedback soon, if appreciated.

EDIT:

bugs not reported yet.

- encryption doesn't work at all. If you try to encrypt your phone it will reboot 1 second after process is started. Wiping caches is necessary to make your phone boot again.

- WiFi turns off when phone is in sleep mode
[HTC One S] moozon:
New unofficial build CM12 from 2016/05/22. Only for Hboot 2.16 Changelog
[HTC One S] MoeDee:
Its not resolved .. Use either or ... But not both enabled at the same time..
[HTC One S] tyler9999:
Thanks for feedback.

unfortunately I chose not to use it for now, I often use Spotify in car with bluetooth BT Audio at the same time I have to be able to receive calls and not to risk a crash of dialer. I hope this issue resolved soon...
[HTC One S] Forage:
This has always been a problem with the One S. In the past you had to put the phone in flight mode before starting the encryption process. Let us know if this does the trick for you with CM13 as well.
[HTC One S] LS.xD:
Unfortunately no luck with the flightmode workaround.
[HTC One S] Forage:
You being an exception doesn't make it a clear untruth. Instead of claiming something to be not true you might want to wonder what the difference in experience could be first. There's a reason why it's a known issue, it being not true is not one of them.

I wouldn't have known about it if I wouldn't have experienced it first hand myself.

Your tone of sarcasm isn't very motivating for others to help you out. Good luck solving it yourself.
[HTC One S] LS.xD:
You got the point. I'm just tired of reading "usefull tips" which are not working in the end. Especially if others don't try their tips on their own before posting them.
[HTC One S] The Setlaz:
Not for me on 25/05 build but I did noticed that on the 17/05 build. (haven't tried the others)

I don't seem to have that neither. How did you check?
[HTC One S] Jnanadarshan:
USB Debugging by Default

I've installed this ROM. My touch isn't working. I tried to enable USB debugging from recovery by Pulling settings.db and changing 'adb_enabled' to 1 in global table. But it ain't working. Can anyone tell how to enable USB Debugging from recovery in this ROM? Or how can I make some minor changes in room and flash it so it's enabled by default.
[HTC One S] Forage:
Looks like a classic example of a user not properly following the steps provided.
[HTC One S] The Setlaz:
If it's just touchscreen not working, why don't you just plug mouse in the USB? You just need a USB A to micro USB adapter.

The mouse will be automatically recognized and a mouse pointer will appear on your screen. (you can plug pretty much any peripheral on android device and it will work... mouse, keyboard, gamepad, printer...)
[HTC One S] F-L-Y-E-R:
New build

#Added 30/05

#Tested
[HTC One S] Jnanadarshan:
I searched HTC forums and XDA and a lot of guys said One S needs external power source to support a mouse. I was unable to find the Y cable and other stuff, however when just to try I plugged a mouse it worked. Voila. I use the device while traveling to use as a hotspot. Anyways thanks buddy.
[HTC One S] LS.xD:
Flashlight tile seems to work fine on latest build 05/29 :)

EDIT:

Didn't realize that there is a seperate CM13 thread...
[HTC One S] orti-otto:
I Have flashed cm-12.1-20160606-NIGHTLY-ville with new gapps

now i have problem with wifi:

E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiMonitor( 571): startMonitoring(wlan0) failed!
E/WifiStateMachine( 571): Failed to setup control channel, restart supplicant
E/WifiMonitor( 571): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
D/DropBoxEntryAddedChimeraService( 2826): User is not opted-in to Usage & Diagnostics.
E/WifiHW ( 173): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 173): Softap fwReload failed
E/WifiStateMachine( 571): Failed to reload STA firmware java.lang.IllegalStateException: command '42 softap fwreload wlan0 STA' failed with '400 42 SoftAP command has failed'
W/CommandListener( 173): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 173): Setting iface cfg
E/WifiStateMachine( 571): Unable to change interface settings: java.lang.IllegalStateException: command '44 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 44 Failed to set address (No such device)'
E/WifiMonitor( 571): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
D/WifiMonitor( 571): startMonitoring(wlan0) with mConnected = false
E/WifiHW ( 571): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant( 3714): Successfully initialized wpa_supplicant
D/BluetoothAdapter( 3195): 814100897: getState() : mService = null. Returning STATE_OFF
D/ConnectivityManager( 2070): getMobileDataEnabled()+ subId=1
D/PhoneInterfaceManager( 1458): [PhoneIntfMgr] getDataEnabled: subId=1 phoneId=0
D/PhoneInterfaceManager( 1458): [PhoneIntfMgr] getDataEnabled: subId=1 retVal=false
D/ConnectivityManager( 2070): getMobileDataEnabled()- subId=1 retVal=false
E/wpa_supplicant( 3714): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 3714): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 3714): wlan0: Failed to initialize driver interface
E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiHW ( 571): Supplicant not running, cannot connect
E/WifiHW ( 571): Supplicant not running, cannot connect

what can i do to make it work again?
[HTC One S] orti-otto:
I have found the solution by myself:

My phone is in mode s-on. So i have to install boot.img seperatly after having installed the cm13-xxx.img.

I have done it with TWRP - that

didn't

work at all.

After flashing with

fastboot flash boot boot.img

all works as designed
[HTC One S] F-L-Y-E-R:
New build

#Added 29/06

#Tested
[HTC One S] F-L-Y-E-R:
New build

#Added 19/08

#Tested
[HTC One S] Endless Dark:
Installed the latest Build on the One S for a friend after CM13 is disconnecting the WiFi Connection when the Display turned off. Everything works fine but the Camera is still not working ??? Sometimes it says no Connection to the Camera. After reboot it will work again. And the Flashlight Tile is not working correct. It turns the LED on but can't be switched off. It stays on. Only a reboot helps here too.
[HTC One S] mali_zeeko:
To solve no Connection to Camera problems:

- remove Camera2.apk from /system/app/Camera2

- reboot into recovery

- wipe dalvik and cache

- reboot

- install OpenCamera
[HTC One S] Endless Dark:
Are the first Steps the Solution for this Problem? Because i tried the Open Camera App already but it did not work. Same problem like the Stock Camera.
[HTC One S] mali_zeeko:
First step is necessary. You may backup camera2.apk. Don't delete /system/app/camera2/lib directory.

I had to wipe cache and dalvik because reboot didn't help once I got no connection to camera message.
[HTC One S] Rafudus:
The same... Im in trouble with thhe wifi when i lock the phone... the wifi turns off
[HTC One S] elenhil:
Excessive battery drain from Bluetooth

Did anyone notice that listening to Bluetooth headset has been draining too much (like, up to 30%/h) battery? Can't really pin it down to a new headset or a new ROM build :( What are your experiences, guys?
[HTC One S] mischa72:
Hi guys,

Can't seem to find a working solution for the WiFi problem on my OneS. I installed the last update and since then WiFi is not working anymore. Before I had perfect WiFi and now it's totally gone. When I go into pulldown-wifi the phone starts looking for a wifi signal, but doesn't find any. When I go to settings the wifi-toggle is greyed out, just like the one for mobile networks. Last one can be explained, because I don't have a SIM-card installed. It's my backup phone. I already found that CM12.1 is only looking to wifi channels up to 10. Mine is 5, so shouldn't be a problem. Bluetooth is working.

I'm out of ideas, so any help is appreciated.

Best regards,

Mischa
[HTC One S] Endless Dark:
I gaved it up with that Rom and the WiFi. I installed CM12 with Android 5.1.1. again and the WiFi works without any Problems. The WiFi in this Rom here is definitely broken.
[HTC One S] Ankit Malani:
inquiry about rom

Can someone help me that this rom can work with indian sim card carriers? Can i use indian sim card with this rom in india??
[HTC One S] Rafudus:
Wifi and bluetooth problems

Now im using the Mi Fit app... And i cant finish the app if i want in settings...

When the wifi is on, i cant turn on the bluetooth, and the same when the bluetooth is on the wifi cant connect to my network.

There is a terrible problem with this two functionalities... Im waiting for a new update, because this rom is great for the phone... But i cant manage with this problems...

Keep working pls
[HTC One S] moozon:
Here the new build cm12.1 from 24.09.2016
[HTC One S] Rafudus:
ohh

Can you sent that to me? I dont have permissions rafudus@gmail.com

ASAP

thx

----------------------------edit

there's no difference for me than the last update :(
[HTC One S] rmsv:
does it work for s3 model?
[HTC One S] moozon:
Not. Only for s4.
[HTC One S] Klorec:
Tried it, but the Wi-Fi doesn't work, says it's Turning On but that's it.
[HTC One S] moozon:
Try install again with full wiping. I have not same bug with Wi-Fi.
[HTC One S] Klorec:
Nevermind, I figured, it's the same with different ROMs too, seems like I have a Wi-Fi/Bluetooth bug. I'll try to resolve it somehow. Thanks though.
[HTC One S] Klorec:
Okay, I don't know what to do anymore, asking for help is my last resort. I spent WEEKS reflashing and trying this to get work. I have hboot 2.16, SuperCID and S-OFF with this ROM. Wi-Fi nor Bluetooth work, says "Turning On" and that's it., no matter which build number. I'm no noob, and I've searched literally everywhere, but found no solution, even though in this thread, people had similar difficulties, and wrote that they sorted them out, but they didn't say HOW! What I do is:

Revert to (almost)stock via RUU - everything works perfectly, wifi, bluetooth, etc.

flash hboot 2.16, clear storage to create the 12GB partition - wifi/BT still work.

Flash recovery TWRP 3.0.M5-0. Wifi/BT still working.

Flash the CM 12.1 ROM - VOILA, WIFI/BT stuck, says Turning On. Done.

Rinse and repeat.

Wipes don't help, radio reflashes don't help. Nothing helps. Oddly enough, after flashing another rom (with wipe and whatnot of course) just to try, the wifi/BT didn't work there either. So there must be something within this rom that messes the radio partitions up, or something like that.

Please, [MENTION=3500011]F-L-Y-E-R[/MENTION] or anyone, help, as I am slowly getting crazy, I have literally no idea, where the mistake can be. If it's partitions, I have literally zero clue, how to fix it. Any ideas?
[HTC One S] solexus:
What about boot.img, did you flash the newest one separately? That is one odd thing you've to do for yourself with the One S...
[HTC One S] Klorec:
That was not the case, I'm S-OFF so no need to flash boot.img, but I finally managed to address the issue and after weeks of tinkering, flashing, re-flashing and crying, finally fix it. Here's the solution to the Wi-Fi Turning On error:

1. Use RUU to return to stock ( I used RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe). Everything should be fine, you should have a T-Mobile US stock ROM with working WIFi and BT. Boot into it, set it up.

2. Don't update ONLY hboot to 2.15, update the whole FIRMWARE from this thread (use the Official Unbranded 2.15 zip with fastboot oem rebootRUU command)

This was my problem, I only updated hboot2.15 and the radios got corrupted somehow, or whatever happened. You gotta do the whole firmware upgrade, it upgrades radio to 1.11 and a couple of other things as well.

3. After that's done, fastboot reboot-bootloader, afterwards find a modified 2.16 in the HTC One S forums (without the red text) and flash it the same way (fastboot oem RUU)

4. fastboot reboot-bootloader again, and CLEAR STORAGE. The phone will create the 12GB partition, and make your current system unbootable - Don't worry.

5. Go to bootloader, and flash TWRP.

6. Reboot to TWRP, Wipe data/cache/dalvik (twice, just to be sure)

7. Flash CM12.1, Gapps and optionally new Radio (from my experience 1.20 and 1.35 both suck, so I stick with 1.11, but whatever makes you happy)

7a (optional). Flash boot.img from the CM12.1 ROM via bootloader. Not sure if it makes a difference, but it certainly doesn't do anything bad.

8. Reboot, wait for the first boot (5-10 min) and go through the CM setup process. The connections should work flawlessly now! The battery life should be reasonable too :)

Hope it helps everyone with the same problem!