yashsingh1/xdaforums huggingface dataset:
[HTC One S] yooouuri:
AOSP

http://www.mediafire.com/download/pd1p7iv8unxx7x4/WWE_1.15.50.05_AOSPradio.zip

SENSE

http://www.mediafire.com/download/lahi47imjcep4b9/radio-1.15.50.05.29.zip

Source:

http://xdaforums.com/showthread.php?t=2255906
[HTC One S] mo976:
Any specific reason other then battery or stability? On a side note lock screen on lag is almost non-existent now, thank you.
[HTC One S] nicknc:
no and no.

data drop fix is well documented in this thread, though.
[HTC One S] mikronac.ns:
I didnt ask you for opinion about documentation. But, thanks, anyway...
[HTC One S] nicknc:
I didn't state an opinion about documentation, but pointed you to where you could readily and easily find the fix.

You read tone into my post that wasn't there-- and your reply was just outright rude.
[HTC One S] el_smurfo:
10/24 up

Tried cmupdater and it installed and booted up without any bootloops and without the stuttering boot animation I often have. Unfortunately, I had "unknown" as my radio version, which happens quite often on first boot and required two shutdowns and restarts to get working.

Absolutely zero lock screen delay, so I'm not sure what we're giving up, if anything, by sticking with 3.4.11.
[HTC One S] thiasB:
Unfortunately not for me. I see the same crashes when using GPS apps and the same stuttering bootloops afterwards.
[HTC One S] el_smurfo:
I think the GPS crash is something different, though if you're getting bootloops afterwards, that is definitely an issue.
[HTC One S] Dave77459:
You are S-ON still, but you ran the CMUpdater app and let it reboot and it worked? No Flash Image GUI or anything?
[HTC One S] el_smurfo:
I flashed the kernel first... But I usually have to manually flash after and power down
[HTC One S] wwelles:
I have the same lock screen issues still. System seems more responsive, but could be because I just restarted (typically after a few days things slow down).
[HTC One S] fusk:
Just flash it and that's it ?

p.s. i'm still running 1.11.50.05
[HTC One S] LiquidZero:
I, too, get the "sign in to T-Mobile" notification, though I don't use Wi-Fi. (Very rarely do I use Wi-Fi.) Clicking it just opens Chrome and takes me to Google.com.

I also notice that when i am not using bandwidth, my phone seems to fluctuate between H+ and 3G. But when I'm actively downloading, say, over a few hundred KBps, it stays at H+. I would think that this is some kind of battery saving feature, as lower frequencies require less power consumption; though the constant switching back and forth, in my opinion, seems to do more harm than good. I stole this issue by switching off my mobile data when I'm about to holster my handset, and enabling it again...usually leading me to the "sign in to T-Mobile" notification.
[HTC One S] nicknc:
elsmurfo mentioned having the same issue on a few random builds.

Have you done the build.prop data edit? That got rid of all that funny data business for me. I still get switching between H and H+, like you mentioned, but it doesn't seem to reflect reality.
[HTC One S] el_smurfo:
I haven't gotten that in a while, but I usually make some build prop edits and also switched to the ipv6 APN about when they stopped.
[HTC One S] djsubtronic:
So what's everyone's view on the 24th Oct nightly? Is it worth me updating from a 100% stable base? (which is apparently on kernel 3.4.60)
[HTC One S] eXtatic@XDA:
My experience with 10/24:

Downloaded the complete zip and flashed it via TWRP. Powering down and starting got me into bootloops.

Another power down later it booted up fine and felt good for some minutes. Even enabling XPosed Framework with soft reboot worked out well.

Opening Google Maps to activate GPS crashed my phone into bootloops again. Another power down didn't solve the bootloops...

Restored my previous nandroid, waiting for next version.
[HTC One S] fusk:
What i figured is that if you're s-off, to get a stable boot on 24, and just flashed it, it seems to work better if you go back and wipe cache/dalvik manually and reboot again.
[HTC One S] kuroneko007:
This is really bad news. So once we did the OTA to 2.21, and installed the new HBOOT and radio, there is no way to go back?

The radio issue causes big problems, ie constant wakelock of gmail / contacts trying to sync, meaning I get a massive battery drain.

The stupid thing is, the phone reports it as "screen" in the basic battery information.

I really don't want to have to go back to a Sense ROM.
[HTC One S] djsubtronic:
How did you conclude that?
[HTC One S] bobjbain:
What is the baseband version for the 2.21 radio?

Mine is 0.16.31501S.17_2_10.23.31501S.10L

If this is 2.21 I don't think I got it through OTAs, I think I flashed a separate package to do it!!

I can't seem to find a list of radios any more, there certainly used to be one (wasn't it hosted by you xkonni??)
[HTC One S] kuroneko007:
Look how much battery it thinks my "screen" used in just 48 minutes. And no other application caused a real significant battery drain.

https://www.dropbox.com/s/152sy39j6k87k10/Screenshot_2012-08-18-14-34-56.png

https://www.dropbox.com/s/av0meomzuz4ncmj/Screenshot_2012-08-18-14-35-06.png

https://www.dropbox.com/s/v713l7k5ja6kmca/Screenshot_2012-08-18-14-35-15.png

https://www.dropbox.com/s/e7cicjnl5331l3j/Screenshot_2012-08-18-14-35-38.png
[HTC One S] djsubtronic:
48 minutes of screen time sounds reasonable for that percentage of screen usage. Considering that around 4 hours of screen time can drain the battery from 100% to flat.

If you had drain from other sources you should be able to see it on BetterBatteryStats. Or try turning off the sync altogether and see if your Screen % changes.
[HTC One S] kjozsa:
I'd like to get an issue confirmed which I'm experiencing with this build. For me, every call starts with very loud volume, regardless of the call volume setting. Trying to pull down the volume using the volume rocker during the call does not help as it is already around the lowest setting. The solution is to push the volume up to the max (while the percepted call volume does _not_ change!) and then from there I'm able to lower the volume successfully only..

Anyone experiencing this behaviour? Any chance to get this fixed?
[HTC One S] yzoni:
Guys, I made an updated version for the time xkonni isn't back. http://xdaforums.com/showthread.php?p=30555889#post30555889
[HTC One S] kuroneko007:
If 4 hours screen time drains the battery 100% (I agree), then 44 minutes should drain about 20%, not 86%. So 44 minutes is not at all reasonable, and indicates a serious problem.

You can see from my BBS screenshot where the drain comes from, and it has nothing to do with screen.

But this issue of most of the drain being arbitrarily attributed to screen is not a CM issue, I had the same thing on Sense, so this is kind of OT.

My main point was, the radio(?) seems to be causing massive wakelock with Google sync, which kills the battery. Several others reported the same problem.
[HTC One S] Co5min:
I have some battery issues myself. The second and third drain factors after screen are: cell standby with 30% and phone idle 25%. This is under full signal conditions, either work or home. I`ve just flashed the latest build and really hope to see something different on battery.
[HTC One S] Phuturist:
Google Maps is know to cause unwanted wake locks. You could either freeze it with TB or try these steps: http://xdaforums.com/showpost.php?p=29420959&postcount=7059

Same here, I tried Trickdroid for 5 minutes as these sync problems don't seem to occur on this ROM but I just could not cope with Sense. I just read there is a new radio coming though. Hopefully this will fix these issues in combination with CM10 as well.

From the Trickdroid thread:

I have not experienced this thus far.
[HTC One S] ElJeffe:
I also noticed that the call volume is really loud. When I try to lower it, it is always at the lowest volume. I'll try this trick to see if I can lower the volume this way...
[HTC One S] unknown89:
Crashes when I open contacts...
[HTC One S] :
Just one reply to stay on topic:

I thought at least Dumlock would do that per their thread--maybe wrong. Am on lower hboot so can't test--
[HTC One S] el_smurfo:
They only say boot.img, not radios...

http://teamw.in/project/htcdumlock
[HTC One S] :
I read that page to decide if I wanted Dumlock, guess I read more into it than was there--

I Feel "Dum" :o
[HTC One S] unknown89:
So I've upgraded successfully from stock ROM. Noticed bbciplayer and tvcatchup will not play....so how do we get flash to play?
[HTC One S] raikesy:
By sideloading Flash.
[HTC One S] ViViDboarder:
What Dumblock does is flash recovery to boot instead of recovery. This bypasses the restrictions HTC has put on recoveries.

It's exactly the same as if you took a recovery image and did fastboot boot recovery.img. Given that this is the standard process for flashing a radio, it should work.
[HTC One S] dc211:
Tried it already and it doesn't work. I believe the radio partition is write protected on hboot 1.13 and 1.14 where as before there was just a signature check. I've tried every method I know of and nothing works. I'm wrong often though.
[HTC One S] OccupyDemonoid:
It has never crashed for me when I opened up contacts. Contacts is something that worked flawlessly, are you sure something didn't go wrong during the flash?
[HTC One S] djsubtronic:
Decided to try it out. Worked fine, and noticed a big improvement in the wakeup lag. It's almost instant.

I made sure my Google Play location services were still disabled, and tried fiddling with Google Maps, and bam - crash/bootloop. I couldn't even get it to reboot after a full power down. However looks like a dalvik/cache wipe has fixed it.

This is strange because disabling location services let me use Google Maps without a problem on the 5th Sept nightly I was using earlier. Not sure what's different now.
[HTC One S] sushidog:
Yes.

Sent from my Nexus 7
[HTC One S] fusk:
Something is wrong, i boot to twrp, flash & reboot, go to settings and it still says 1.11.50.05

Would you happen to know how come it's not doing it, even tho there's no errors?
[HTC One S] el_smurfo:
Can only flash radio if SOFF
[HTC One S] fusk:
"HTC one s - s-off - CM10.2 "
[HTC One S] sushidog:
You MUST be S-OFF.

Edit: ok, you're S-OFF. Is your radio the same on Bootloader and CM System?
[HTC One S] horno46:
I got the same, I'm s off and flashed 1.20 radio OK! Won't downgrade to 1.15.
[HTC One S] el_smurfo:
Have you guys tried using the firmware.zip with only the radio and flashing in fastboot like in the firmware thread...

---------- Post added at 08:33 AM ---------- Previous post was at 08:19 AM ----------

If that's in your signature, I turn that noise off.
[HTC One S] djsubtronic:
I was able to flash 1.15 in recovery on top of 1.20 from the link provided above without a problem.

Just make sure you flash the Sense version - that is the HBOOT radio since CM no longer uses bundled radio.
[HTC One S] horno46:
That's the mistake I made then. I flashed AOSP.
[HTC One S] skyzent:
cyanogen or maximus 10, which rom is better for battery usage?
[HTC One S] fusk:
Ok, fair enough, didn't know you could do that.

Yes, both show same version.

Okay, so you have to flash the sense radio for CM? i thought that was for sense based roms, so i have been trying to flash the aosp one. Maybe that's why it's not working.
[HTC One S] nicknc:
Sense radio loads it correctly into the bootloader, which is what CM10.2 looks at-- that's a change from CM10.1 and below. This topic has come up a lot, and probably would be good to put in a sticky somewhere....
[HTC One S] kirrun:
My five cents.

After flashing 20131025 I got funny boot animation (cyan background with dancing pink stripes) and something is definitely wrong with screen colours: everything is orange instead of cyan. Even worse, when the phone boots I get “com.android.phone has stopped” and after pressing OK, I get it again—infinitely, can't do anything really.

Same with 20131024.

Colors are boot animation are broken in 20131021, but the phone seems to work fine. It hung after initial setup, I rebboted it. Now it boots fine but the colors are crazy and Trebuchet background is also cyan with different stripes.

Falling back to 20131011…
[HTC One S] el_smurfo:
I got color issues with older Bubba kernels, but 10/25 booted OK. I did get several gapps FC after boot, but it's settled down since then. Is it possible you're not flashing the boot.img properly, as the kernel was reverted in both 10/24 and 10/25 which would exactly explain your experience.
[HTC One S] kirrun:
Yes, I guess that was the issue. I normally flash kernel from my laptop, but this time did it from desktop which is running NixOS and because of this some old version of platform-tools. Probably `fastboot` here is broken or I don't know what's wrong with it, but flashing from the laptop helped.
[HTC One S] c19932:
When I first boot my device, systemUI uses about 57mb of ram. After a day and a half, it's memory usage is 225mb. I'm too lazy to take screen shots through kernel tuner so please take my word for it lol. When I force restart the systemUI process, it's memory usage goes back to about 60mb. So I'm positive that it's the systemUI process.

Maybe other people aren't reporting this because they don't run that many apps and they reboot their phones quite often? Or maybe they don't even notice the memory leak and think it's normal? The leak usually happens when I run various apps throughout the day like dolphin browser, Spotify, google voice, etc. If you let the phone idle forever then I doubt the memory leak is as severe.

Again I'm on on Beanstalk so if anyone cm user could check their systemUI memory usage after a day or two without rebooting, that would be great. It could be the beanstalk rom itself.
[HTC One S] mannequin:
somehow the last build that boots for me without the problems is 10/21 one. i'm getting phone.apk FC's i can't close right off the start with newer ones.
[HTC One S] LiquidZero:
As far as doing the "build.prop data edit"... no. Don't exactly know what or where to begin with that.. you're welcome to enlighten me. While it's annoying as hell, I don't find value in having to do said edit with every NIGHTLY update I perform.. and I usually do at least one to three a week..
[HTC One S] remigo:
I installed the newest update and every time I reboot I have to wipe dalvik and the other thing (sorry I'm bad) or it will bootloop, anyone know if I did something wrong? Never had this issue with the nightlies
[HTC One S] bunga bunga matze:
If you not s-off, you have to flash boot.img via fastboot (look my sig)
[HTC One S] remigo:
I do that every update :s

Edit: your kernel version is higher, guess I did it wrong

flashed it again, still bootloopin'

Maybe something else is wrong?

My bootloaders says this:

VLE PVT SHIP S-ON RL

H-BOO- 2.15.0000

RADIO-1.11.50.05.28

OpenDSP-V31.1.0.45.0815

eMMC-boot
[HTC One S] bunga bunga matze:
Dont worry, Kernel has been reverted to 3.4.11 with 10/24....

Iam on 10/23

But the 3.4.11 Kernel should fix the bootloops after flashing.
[HTC One S] remigo:
Weird I still have it:(
[HTC One S] :
Nope, not really. They're still there, probably even worse than before the revert.
[HTC One S] horno46:
Yes took me five minutes to boot earlier.
[HTC One S] :
I can, however, confirm that PPTP-VPN is working on the Oct 25 nightly.
[HTC One S] Hackbert:
Yippppi.!
[HTC One S] sinlimites:
I have flashed again 20131011 and i have to flash several times because i have bootlops. What's the matter if the bootloops dissapear randomly when flashing several times? (I'm S-OFF)
[HTC One S] horno46:
I find that I have more trouble booting if phone is charging. Anyone else find this?
[HTC One S] xparagonx:
I agree. I seem to have more reboots when charging as well.

Also my GPS is completely borked on 10/24 with the reverted 3.4.11 kernel. I can go outside, open maps with GPS, stand still and my location pointer spins around non stop because it can't tell which way I'm facing. It also moves around wildly across the city as if I were traveling light speed. Then it eventually causes a reboot.
[HTC One S] nicknc:
Search for "fastdormancy" in this thread. You'll find the post where I listed the settings to add to your build.prop that seem to resolve this for tmous folks.
[HTC One S] Albino_Mexican:
Zero issues with 10/26 so far...:)
[HTC One S] nickmv:
Can anyone else confirm? I guess it isn't that big a deal to me, since the Nexus 5 comes out Friday. Definitely ordering this one.

The One S was a great phone specs-wise, but has had crippling radio and other issues that took that greatness away. I'm sticking to Nexus devices from now on.
[HTC One S] el_smurfo:
I haven't had any issues with 10/25, but I haven't tempted fate by soft rebooting. CM is actually talking about an M1 code freeze thus week, so this could soon be given a Stable tag. That would be a sad end to my CM smartphone career.
[HTC One S] nickmv:
Wiping cache and dalvik has ALWAYS been recommended for dirty flashing. You've just been getting away with it just fine until now. That's what the advantage of dirty flashing has been -- only having to do a simple cache and dalvik wipe, instead of a full /system and /data wipe.

It's only an extra minute or two, so it's not a huge deal. The bootloops however, ARE a huge deal. I feel like they're getting more frequent, and I've been on 10/11 for a while.
[HTC One S] |RaVeR|:
I hear you :( I'd go back to cm10.0 if I could migrate my /data. I really loathe wiping.

This ROM was basically perfect in the Kernel 3.0.80 era. There was no screen-on lag. In those days, I 'd never seen a spontaneous reboot. Battery life was good. In fact, I don't even remember any features we have gained since upgrading to 3.4. We've gained only bugs.

Since linux 3.4, I cannot use navigation in my car, without it starting to bootloop when someone calls me (in fact, multitasking while navigation is running is basically a sure-fire way to trigger this bug)

Usually, people tend to call you just when you're -almost- at your destination: aka when you really NEED the navigation.

I've become furious more than once with the phone when it starts to bootloop just at that terrible moment. Having to long-press the power button while navigating heavy city traffic when you've got no idea where you're going tends to raise my heart rate a little, to put it mildly :)

I don't mean to belittle the effort people have made to this ROM, but seriously, it ain't what it used to be.

The absolute WORST thing is that sometimes after these bootloop episodes, my /data is corrupted, resulting in some apps disappearing or a large part of my settings being reset to stock or someting like that.

I bought my One S specifically to run CM. It was installed the very first DAY when I got the phone. Didn't even take a whole day either.

Since kernel 3.4, it's been nothing but a pain.

Sorry, just needed to blow off some steam :)
[HTC One S] nickmv:
You couldn't have said it better. I actually had that exact navigation issue occur this past weekend while in traffic, and it was quite annoying. Was basically driving blind while furiously trying to boot back up in time for my next turn.

Do you plan to keep your device, or are you upgrading soon? For me, the silly bugs as of late, combined with the HSPA+ (instead of LTE) has got me settled on heading to the N5 later this week. When I first got this phone, my T-Mobile data speeds were great (15-16 mbit/sec), but about 1-2 months after getting it, T-Mo pretty much dropped speeds to what I had with my Nexus S (4-5 mbit/sec max), which defeated the entire purpose of having an HSPA+42 phone. The CPU speed is nice, but the bugs (namely the radio sluggishnes) and lack of data speed has killed my device experience with the One S.
[HTC One S] maluus:
It seems a second build process triggered today but changelog doesn't show anything new. Any info about this?
[HTC One S] el_smurfo:
Maybe that's the M1 they announced for this week.

Edit... Nope... Output still says nightly. Weird
[HTC One S] cannondale0815:
I didn't try it with the nightly from Oct 25, but it doesn't work for me on the latest nightly from Oct 28. Can you confirm that from your end?
[HTC One S] jwhittenburg:
Google voice calls in call log

Since the 10/25 nightly, I have started seeing the wrong number show up in the call logs when I dial using Google Voice. Has anyone else seen this?
[HTC One S] ponchofiesta:
3.4 kernel brought a much better camera focusing. But that's all I remember.

All these bugs made me crazy so I wanted a stable ROM so much, I switched (after years of CM) back to Sense (Maximus HD) and have to say: I'm very happy. It simply works... absolutely no bugs, good battery life, super fast camera and I really have to say, sense 5 is much less ugly than any sense version before.

But I still hope, CM gets as good as it was.
[HTC One S] maltumbo:
10/28 is the best one til weeks.

First reboot after flashing rom.zip and boot.img with flashify worked out well.

Enabled xPosed and powered down. Next was start without any problems.

Tried GPS on Google maps and started navigation too. Nothing awful happend.

Then I did a reboot from extended power of menu to confirm this post before publication and the boot animation was never more fluid.

Have fun and best regards

Maltumbo

My opinion after one hour by the way
[HTC One S] el_smurfo:
Oh yeah...it wasn't better camera focusing. It was "camera focusing"...the older builds relied on a binary that got DMCA'd...We had to get on the new kernel to get official nightly builds back at all. Having said that...the reboots came much later, and since reverting the kernel didn't seem to fix it, it must be some other change that was introduced in the same month's ago time frame.

EDIT, BTW, looks like the "second" nightly of today will have a ton of kernel stuff from Qualcomm, including a lot of tantalizing boot time fixes...Could not be soon enough. Been trying to get my phone to boot for 10 minutes after going to recovery for a backup. When even the "hold power button" doesn't seem to fully turn the thing off, that's some major FUBAR and a lot of these commits look like they are relevant.

If anyone is interested, 10/29 boots, but I don't have time to test for boot loops
[HTC One S] Albino_Mexican:
So far so good with 10/29. Only been a few hours though.
[HTC One S] xparagonx:
I dirty flashed 10/29 and it booted ok. But then I manually rebooted and got the relentless bootloops. Had to wipe caches and power down to get it running again.
[HTC One S] justaway2:
I got a bootloop after installing 10/29. I did the usual routine of powering down completely and doing a cold boot.
[HTC One S] djsubtronic:
I was using 24th Oct for the last few days (until yesterday), after deciding to finally update from my trusty 9th Sept.

Over the course of four days, I noticed it only had one advantage: slightly faster screen wake time. Other than that, it suffered from poorer battery life, generally unresponsiveness issues (where stuff just hangs) and most annoyingly, sometimes the phone would just die. As in you can't even turn the screen on, nothing. You have to force power off and hope it comes back. I even had a couple of random crash/bootloops which couldn't be resolved by a cold boot. Had to wipe dalvik and cache.

So I'm back with my trusty 9th Sept nightly.

I noticed someone saying the 28th Oct nightly is great. Can anyone confirm if they've used it and whether it exhibits these weird issues from the 24th Oct nightly? And battery life?

Edit: wrote 24th Sept in the first sentence instead of 24th Oct
[HTC One S] :
Still workin'!

(It is a PPTP-VPN, and im running Oct 28)
[HTC One S] maluus:
I can't say about other things but battery life is still worse on 10/28 than 10/11.
[HTC One S] wwelles:
10/24 has good battery life from my point of view
[HTC One S] kuroyume_cl:
Just updated to 10/29 using the built-in update manager and it booted with no problems, for the first time since i moved to 10.2
[HTC One S] cannondale0815:
Craziness! I just updated to the latest build from the 29th, and initially it would still not work. I then deleted the vpn entry and also deleted all vpn app data using titanium backup. Then rebooted and set up my vpn connection info, and now it works! Yay!
[HTC One S] :
No kernel flash?