yashsingh1/xdaforums huggingface dataset:
[HTC One S] Moosach:
Maybe someone is interested: I'm running 20131115 nightly and have no problems. Same with 20131112 before. Like everyone else here reported directly after install also on my device the bootup hangs after a few seconds of that animated CM circle. I press and hold the powerbutton and after the next boot everything is fine.

S-OFF, Baseband 1.13.50.05.31_10.30.50.08L
[HTC One S] :
Same here. I'm running Nov 15 and I would say it is fit for daily use. Battery life is good (though, for some strange reason, I think it was slightly better on Nov 12 - that might just be a feeling, though), I haven't really experienced any data drops so far and it hasn't crashed yet, either. I'm pretty sure it will start bootlooping once I push it to its limits, but using it as I do, I hadn't had a chance to do that yet.
[HTC One S] nicknc:
I just did a clean install of 15 Nov after realizing CM11 is no fun at all. Still getting random reboots and bootloops. Bubba kernel makes a difference in eliminating the random reboots, but bootloop issue is still 100% there.

No data drops w/ the build.prop edits, of course.

Glad to hear it's working for you guys for now. Nothing has been fixed though, so for the rest out there, the issues remain (although they aren't quite as frequent)...
[HTC One S] djsubtronic:
What firmware? I believe the 2.16 version doesn't have the reboot issue.
[HTC One S] el_smurfo:
I think CM11 is "fun" enough to use as a DD. Been using since yesterday afternoon and not having any issues really. Makes you remember all the little CM tweaks you actually do use and enjoy when they aren't there anymore...
[HTC One S] nicknc:
2.15. Not super excited about being stuck between CM11 or Sense 5 with the hboot upgrade, so holding off until CM11 has been out a little longer.

---------- Post added at 12:50 PM ---------- Previous post was at 12:44 PM ----------

Maybe I'm dumb or had a bad flash, but I was missing all kinds of stuff.

Like the ability to access "system" in settings. Or enable the quick pulldown of settings. Or adjust brightness by sliding the notification bar. Or use Voice Plus. Or have a decent looking and useful launcher (wtf happened to Trebuchet?). Or have a functioning recovery. Or sync my calendar. Or have the email app work without random crashes (or show the combined email inbox-- again, wtf?).

It was stable, sure, but I struggled to do much of anything. Stampeded back to good old bootloopin' CM10.2 as soon as I could. Luckily, it was waiting with about 30 minutes of bootloops for me.

I know it's beta, and only been out a few days, so that's fine. I'm just saying it wasn't any fun, :p

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------

By the way, what the hell are you still doing here man? I thought you'd gone onto greener pastures with a Nexus 5! :)
[HTC One S] el_smurfo:
Thanks...now you've reminded me again of all the stuff missing. Maybe I'm weird, but I sorta like flashing nightlies where you never know what old feature is getting ported back in again...it's like Christmas for dumbasses.

Wish I could pick up the N5, but $350 isn't in the budget when said budget includes 2 kids under 3. Waiting for subsidized version on TMobile as they always give me great loyalty pricing.
[HTC One S] nicknc:
N4 is sub-$200 on eBay now. I like this phone, though. The CM stuff will get ironed out eventually or there will be a better AOSP that comes out.

I wouldn't mind PA, BS or AOKP if it weren't for all the mandatory bells and whistles with pies and halos, etc.
[HTC One S] el_smurfo:
I like it too. Don't think n4 glass back would survive toddler drop like I had yesterday...using the wife's gs3 makes me like it more. Starting to seem like hboot 2.16 is going to be the bootloop "fix" which sucks because I don't want to SOFF
[HTC One S] Moosach:
I only get random reboots when I enable this option to get my position by nearby WLANs. With just GPS I have a stable system.

(outdated signature removed)
[HTC One S] nicknc:
If 2.16 is the fix, that's good news. I'll stick with bootloop city on 10.2 until they drag the rest of the settings in there and a decent recovery comes out.

I didn't think about that glass case on the n4-- that's a good point. I may hold off on getting my wife one then. Her sensation has held up pretty well to my 2 year old so far.
[HTC One S] :
How so? And what would that have to do with having to S-OFF your phone? :confused:
[HTC One S] machoman1337:
I believe it's necessary to S-OFF in order to get the 2.16 hboot. The disadvantage of the 2.16 hboot is incompatibility with official CM (it'll boot but run into very strange issues not seen on 2.15). So if you were to update to 2.16 to try a ROM, and decide you want to switch back to an older one, you'll then face the inconvenience of downgrading the hboot just to switch back.
[HTC One S] el_smurfo:
Lots of folks now reporting bootloops on 2.16 anyhow
[HTC One S] nicknc:
Oh goody.
[HTC One S] Moosach:
What does it mean that there haven't been any new nightlies since 11/15? Any special reason?
[HTC One S] nicknc:
Not a whole lot of developers at CM for the Ville to begin with, and the majority of development seems to be focused on getting CM11 off the ground. They'll probably push out a stable version in a month or so for CM10.2 just to wrap it up.

Wait a few weeks until they get the glaring issues out of CM11 and then move on up.
[HTC One S] F-L-Y-E-R:
Any one knows is latest nightlies are compatible on 2.16 hboot?
[HTC One S] el_smurfo:
Nope...takes a custom build to work with hboot 2.16 partitions. You can try RockR172's CM11 for hboot 2.16.
[HTC One S] machoman1337:
Today's nightly didn't fail on jenkins for a change.
[HTC One S] :
My phone really hates any of the new updates. It apparently only cares for the 4/20 nightly which is old as hell but very stable. I've searched and tried every little trick and tip I could find and no matter what I do I get non-stop boot loops.

I tripled checked my hboot - 2.15, using TWRP 2.6.0.0, S-OFF, radio 0.16, CID 11111111. Wiped everything including the SD card ( after copying everything to my computer of course ). Then I transfer a single folder with the roms and gapps back onto the device. I made sure I had a full charge of battery and disconnected the USB, then...

I've tried 10.1.3 RC2, 10.1.3 stable, a few nightlies 10.2 in October and 10.2 11/12, 10.2 11/15.

I've tried it with and without gapps.

I tried the black bean kernel fix as a boot.img flash using a PC with fastboot.

I've also tried fastboot flashing all the kernels before and after the rom.

I tried backing out of the flash menu afterward and powering off the device, letting it sit for a few then booting back up. Cold boot instead of a warm boot or reboot.

All of this results in boot loops that just show the splash, it never makes it to the boot animation.

I posted a while back and kept an eye on the thread but didn't notice any developments or anyone that couldn't boot anything. I think I even reapplied the 2.15 firmware back then to be sure it was on there correctly.

The only thing that seems to boot is my 4/20 backup and perhaps a fresh install. I think my phone is just a total stoner. Anyone stuck in the same boat?

Edit: just tried BB9 for fun and it too failed. I wonder if all these problems are due to processor/kernel issues as previously hinted and my processor happens to be more susceptible.
[HTC One S] Moosach:
Anyone tried already?
[HTC One S] Darknites:
Hmm I never had boot loops up to 4.2 which BB is on but 4.3 and above can boot loop easily. Which BB did you try and when you say fail do you mean it boot loop too?
[HTC One S] tabii:
Experienced similar things, what has worked for me was running a full stock RUU then flash CM 10.2 again. My wild guess is one of the ROM I flashed messed up the partitions somehow and only a full RUU fixed them. Looks like you haven't try this.
[HTC One S] nicknc:
100% agree with this. RUU fixed a similar issue for me.
[HTC One S] Phuturist:
Yep, works fine. I had no bootloops either but this could just be luck. Most noticable for me is a new boot animation, havent look into any new features though.
[HTC One S] Moosach:
Confirmed. Works like a dream. No issues so far. No boot loops. But I liked the old boot animation more. ;)
[HTC One S] :
It works fine but it was bootlooping on me. The new animation is an eyesore, though.
[HTC One S] el_smurfo:
If you delete it, it reverts to a simple ANDROID animation. You can also modify your system/addon.d scripts to replace it will an animation of your choice at flash (I've mostly been using the animation from the GE phones).
[HTC One S] :
Yes, sorry, that's what I meant. BB9 8/21 With 3.4.11 kernel resulted in bootloops also. Hopefully I'll get this sorted and get to check out the new BB.

This is my next step for sure. I think I only flashed a firmware.zip when I upgraded my hboot. I'll give the 2.15 RUU a go. Thanks for the direction guys. I'll report back.

---------- Post added at 06:24 AM ---------- Previous post was at 06:14 AM ----------

Yes, sorry, that's what I meant. BB9 8/21 With 3.4.11 kernel resulted in bootloops also. Hopefully I'll get this sorted and get to check out the new BB.

This is my next step for sure. I think I only flashed a firmware.zip when I upgraded my hboot. I'll give the 2.15 RUU a go. Thanks for the direction guys. I'll report back.
[HTC One S] Dam4rusxp:
I could only get the update to boot after wiping dalvik but now it seems to work fairly well.
[HTC One S] mannequin:
does anyone here have the latest bubba compiled for CM by any chance?
[HTC One S] Darknites:
Give the build with the 3.0 kernel a try.
[HTC One S] :
[MENTION=3165429]tabii[/MENTION] and [MENTION=2207213]nicknc[/MENTION] Thanks for the advice, I went all the way back and ran the 3.14 RUU and worked my way back up to TWRP and CM. 10.2 11/12 was unstable and kept restarting but I flashed the 10.1.3 and so far so good after a couple of hours.

Quck question: I should just be able to restore from Titanium just about everything going from 10.1 to 10.1.3? Anything to look out for?

Again thanks all for the advice, and [MENTION=4157305]Darknites[/MENTION], I'll be giving BB a spin anyways, I used to rock it until I think it went unsupported or something happened around the 4.2 switch, I can't remember, looks stable now though.
[HTC One S] mikronac.ns:
I noticed that I losing singal 11/26 nightly... I dont know whats happening, is it coincidence because I was in faculty campus (maybe they have some signal obstructionists) or what... Anyone else?

Which nightly is last without bootloops issue?
[HTC One S] machoman1337:
Early September I believe. Those nightlies can bootloop if you use the GPS in certain ways, but random bootlooping outside of GPS usage is non-existent.
[HTC One S] mikronac.ns:
Hm, I dont use GPS but after flash 11/27 nightly I rebooted phone and it bootlooping even if I turned if off in bootloader, cleared caches in recovery and so on.

I will stick on stock again...
[HTC One S] Hackbert:
I came from 10.1.3 and make normal update to latest cm10.2 11/29 without wipe. Works fine. No bubba No bootloop No randomrestart..

Gesendet von meinem One S mit Tapatalk
[HTC One S] Dave77459:
Yes, for the first time in a very long time, I got no bootloops when I updated. :good:
[HTC One S] mikronac.ns:
Flashed 11/29. No bootloops. But I keep losing signal occasionally... After few seconds, signal is back... Can anyone confirm this? I dont have this issue on stock [MENTION=1815755]intervigil[/MENTION]

EDIT: I deleted VoiceDialer.apk andd VoicePlus.apk. I restored them and seems like I dont have signal drops...
[HTC One S] BehradGH:
not yet ready for hboot 2.16?
[HTC One S] evoarcher:
20131201-Nightlies - No bootloops so far.

Hi,

I have loaded the 2013-12-01 - on my Nexus S S-On - And I haven't had a boot loop. I can see that sometimes the GSM and Wifi icons are not blue while the connection seems still active. So far so good. I don't have a data plan, so I don't know if the connectivity via GSM is being interrupted, really.

If this was stable it would be a game changer. Is this a different Kernel from the previous versions? What would have been the kernel modifications that fixed the issue?...

evo
[HTC One S] yuan_1202:
On 1130 nightlies.

Setting hardware key backlight level lower than 100% causes bootloop.
[HTC One S] blinksilver:
On the off chance some of the followers of this thread aren't aware, there is an easier way to figure out if bootloops are still present or not.

Just go to: http://changelog.bbqdroid.org/#/ville/next

And check the change-log for any changes that might seem pertinent, there are even links to the actual changes if you don't trust the commit logs. Sure beats installing a new build everyday.

For the record, there hasn't been much in the way commits that would have helped our cause in the last couple days...
[HTC One S] justaway2:
Exactly. People should actually check the changelog instead of giving anecdotal evidence on whether there are bootloops or not.
[HTC One S] yuan_1202:
The compass is giving very very wrong direction......
[HTC One S] el_smurfo:
Get GPS toolbox from Play Store and use compass calibration. Works for me every time.

EDIT: looks like stable 10.2 builds are rolling out now...guessing we get bypassed yet again :(
[HTC One S] evoarcher:
OK, got it, so we should basically stop downloading and installing nightlies until we see an entry on the changelogs that says something like: "Fixed bla bla bla that was generating random bootloops on the One S". Got it, thanks.
[HTC One S] justaway2:
You know there's more changes in the nightlies than just the elusive fix for the bootloops, right? That's not the only thing that everyone cares about.
[HTC One S] evoarcher:
Bootloops on the One S

Please, don't get me wrong, I have a lot of respect for the programmers, I am a programmer myself, and I am in awe of the technical abilities and dedication of the CM programmers. The problem for me is that a phone that randomly reboots (and keeps rebooting unless/until you have the smarts to stop it) can't be really used reliably, and for a person like me that proudly shows the freedom of CM around to geek friends, it's a little bit of a disappointment.

I may not be an intense user of the phone, but I haven't seen any substantial new functionalities rolled out for a while, and yes, the nightlies are the bleeding edge, I know, so I shouldn't expect them to be stable, but the big bugs are supposed to be fixed first (I may be totally wrong on this - depending on the priorities of CM management - I guess), so I guess, in order to keep interest in the One S nightlies maybe a bit of attention to that bug... wouldn't be bad. - I would rather be able to say, "oh, there a little annoyance here and there... but generally it is usable ... etc. etc." rather than having to say.." It randomly reboots, and you may not be able to get its attention for a few minute... "... Even to geeks friends like mine, that's not a good thing to sport.

Again, a lot of respect to the teams - but this is a big bug, shouldn't it take precedence on the implementations of new features or the resolutions of other minor bugs? -

Anyway - I will likely roll back to the latest 10.1 stable and stay there until/unless something comes out about the bootloops. -

I mean no arm - Peace.
[HTC One S] :
I actually had all sorts of issues on 10.1, so I flashed the 11/12 several times and only got random reboots every couple hours. I updated to 12/01 and have not had any major issues.

One thing I find funny is Chrome going all black when I change tasks and come back. Scrolling fixes it. Probably something with my theme or Chrome.

Sent from my tampered One S.
[HTC One S] moverat:
Thank you for your message, you are very accurately expressed my thoughts. I'm on the stable versions 10 and 10.1 is a constant error that I can repeat my friends. Ingress play, when minimizing the game and then restarted, the lock get bootlup. When using navigation also have chance get bootlup.

I logkat overthrown, but downloaded it just twice.

Developers doing a very good job and the right, I am very grateful to them. But it is impossible to produce a product called "stable", and not an obvious bug fix.
[HTC One S] bobjbain:
The colours have changed in KitKat, now the signal icons are constantly white if you are connected AND connected to google services, if you've got a signal but are not connected to google they are orange! If you have no connection then the icons are basically outlines.
[HTC One S] |RaVeR|:
I expressed very similar thoughts on this thread just a few pages back and got a response from intervigil.

Basically; this bug is well-known and it is also well-known to him that it is a huge annoyance.

Ethan just doesn't know where to look for it. He thinks some HTC kernel magic may be missing/different, causing the bug.

We can't even be sure this bug will EVER be found, since the firmware of the ville is proprietary (closed-source).

After I read this, I promply switched back here: http://xdaforums.com/showthread.php?t=2051865 (read the lasts few posts)

Also, I decided my next phone should always be the 'google official' phone, so we can be sure CM can be made perfect on it.
[HTC One S] yuan_1202:
So basically HTC is intentionally screwing us.
[HTC One S] |RaVeR|:
I wouldn't go that far. They're (of course) only supporting their own software for ville.

And the official ROM does not have this bootloop, so I don't see why this is a problem of theirs.

The most you could possibly accuse them of is to have crappy firmware.

That being said, it might still be simply a CM bug that intervigil cannot find of does not have enough time for. Who shall say? In any case, I'm not going to continue using the 3.4 kernel while waiting for this bug to be fixed. It's far too annoying for that, especially knowing that there might not be hope at all.
[HTC One S] blinksilver:
I was under the impression that all htc msm8960 devices (like the at&t one x - evita) bootlooped or randomly rebooted or whatever other term you want to used for failed irrecoverably. So there are more than a couple eyes on it. It not exactly hopeful that we went through a whole cycle without a fix, but its not like no one is trying.
[HTC One S] el_smurfo:
I think Intervigil has exhausted all avenues and is now just hoping for a miracle source drop from HTC or CAF to fix it. I see most of his commits are from the One GPE source drop, with next to nothing for Ville. As it stands now, it doesn't seem likely that we will ever see a benchmark or stable release and will be stuck whining at each other here in XDA purgatory.
[HTC One S] djsubtronic:
This one has been annoying me for months... what is CAF?
[HTC One S] machoman1337:
I assumed it had something to do with Qualcomm. A google search suggests "Code Aurora Forum". Correct me if I'm wrong.
[HTC One S] blinksilver:
I like the imagery. Its good to know that all the whining we are doing at each other is having the unintended consequence of improving the overall quality of our collective writing. All joking aside, my exams end on the 19th, if nothing good has happened At that point, I will just burn my holiday trying my hand at failing to fix it. I'm a grad student in computer science and it won't be my first time doing terrible things to the linux kernel, so maybe I'll get lucky. Someone just keep harassing me about it. Either I'll fix it or I'll buy a togari, the way I figure it, it will Christmas for me regardless.
[HTC One S] el_smurfo:
Yeah...it's Qualcomm's open source initiative (well, a consortium with Qualcomm as the biggest member)...but doesn't contain any code the OEM's may have snuck in to make their phones actually work.

---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------

I always wondered if someone with enough free time couldn't just do a diff on the 3.0 kernel and 3.4 kernel to try and find that magic bit that brought us the bootloops.
[HTC One S] blinksilver:
From what I understand it doesn't even have to be 3.0.x to 3.4.x because 10.1.3 is using a 3.4 kernel (am i rite?). So we can likely say from the onset that the base OS (4.3) is leveraging a kernel feature in 3.4 that corresponds or relies on an unimplemented or broken resource/function in binary blob ril (perhaps something was deprecated but still there in 4.2 RIL interface, replaced in 4.3 and that replaced call is missing and can easily be mapped).

A good starting point would simply be to find a reliable way causing a reboot to occur with a given kernel/ril version combo in 10.2, use the same combo in 10.1.3 and see whats _not_ being called or referenced in the 10.1.3 setup. From there a little bit of good old binary decompiling of a version of the HTC RiL that fails and a version (lets say from the One GPe, I know its not for the One S, but at least its close.) that doesn't, and seeing if we can shed some light on the situation.

At least that's what I plan on doing... perhaps things will change once I get into it and realize how naive and quaint this all sounded.
[HTC One S] el_smurfo:
Before you go and ruin your vacation, try PMing Intervigil, H8rift and Flemmard...Intervigil posted in the CM11 thread that they are all looking into it, as it effects all 8960 devices.
[HTC One S] blinksilver:
I'm glad they are looking into it, perhaps I will just get on IRC before I start and see what they think the likely problem is and what they've ruled out.
[HTC One S] evoarcher:
About bootloops...

A hint of envy here! - I wish I knew 1/2 of what you guys are talking about! - Anyway I'm glad that something seems to be moving. - We will all eagerly wait for a solution. :fingers-crossed:

You guys ROCK!
[HTC One S] |RaVeR|:
If that is really true and this is a more generic bug (not ville-firmware-related), that would actually be really good news for us.

It would mean there still is hope
[HTC One S] yuan_1202:
I wish the battery life to be better..... i know i know, i shouldnt complain too much. We are alreary very lucky that there are still developers willing to contribute...

Its just a wish.....
[HTC One S] mikronac.ns:
One question:

Why latest stable version 10.1.3 dont have data drop and lockscreen delay issue fixes?

[MENTION=1815755]intervigil[/MENTION] found solutions before 10.1.3 was build... It can be more stable :P
[HTC One S] el_smurfo:
Once they hit stable, they move on...
[HTC One S] mikronac.ns:
Hm, that is not answer why that fixes didnt merged in stable 10.1.3 version...
[HTC One S] abracadabra11:
10.1.3 isn't the most stable ROM around. I went back to 10.0. It's what a stable ROM should be.
[HTC One S] cheeto:
I've done the same. I'll wait for 10.2 stable.
[HTC One S] Navik57:
Hmm.. is there a process to go back to 10?

I'm s-off, wiped cache, system... ran the rom, even did a fastboot boot.img.... I'm getting stuck at the boot screen. I know I saw something about this before, but can't seem to find info about it anymore. =-/
[HTC One S] machoman1337:
wiping /system isn't enough. You need to do a full wipe if downgrading from a later release of CM (not a later nightly of the same release). I tried downgrading from 10.2 to 10.1 before on my Nexus 4 and got stuck on the boot screen even when I wiped /system. However dirty-flashing 10.2 allowed me to successfully boot so I could do a Titanium Backup, then full-wipe and install 10.1 and restore. Of course a month later I ended up putting 10.2 back on lol.

Edit: CM11 nightlies are officially released for the ville. I think the thread title can be updated.
[HTC One S] cyxareg:
can i do nandroid backup of cm10.2 and then, if cm11 won't be stable restore 10.2?
[HTC One S] dragonkaiser:
Hello all

Question: What do i need to update CM10.2 to CM11 ? Im on 2.15 and TWRP 2.5.0.0
[HTC One S] mikronac.ns:
I cant flash new official cm11 with twrp 2.3.x, 2.5.x, 2.6.x...
[HTC One S] dragonkaiser:
Update to CM11

Hello all

Question :confused:: What do i need to update CM10.2 to CM11 ? Im on 2.15, TWRP 2.5.0.0, S-OFF and Super CID

Thanks in advance....
[HTC One S] bobjbain:
The patience of a Saint it would seem.

TBH I would wait a couple of weeks until CM11 is ever so slightly more stable.