yashsingh1/xdaforums huggingface dataset:
[HTC One S] The Setlaz:
Did a clean install after factory reset, I still have lock-screen freeze, freeze on rotate (both from which it recovered eventually), random reboots (twice, a few dozens of seconds after the lock-screen freeze recovered), and BSODs.

I disabled animation, but it still here.

By the way, it seems there are different level of BSOD:

- nothing - phone looks completely dead

- backlight buttons turns on and off

- backlight button + screen off animation (it's not backlight problem, backlight does turn on but the screen stays grey-ish/black)

Going back to my 19/01 that haven't failed me this week !
[HTC One S] nicknc:
How were you restoring your data?

---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------

I wish I could sleep 8 hours...
[HTC One S] hunter12:
I have been on ICS until yesterday and did all the update procedure (s-off and hboot, etc) and did install CM11.

So please do not punish me for asking stupid questions about CM.

The turn-on-screen delay is mentioned often and i also have a 1-2 second delay when i press power button until the lockscreen comes up.

Is this behavior present at all 4.4 based Roms or a special "CM11-feature"?
[HTC One S] Rapier:
It depends. Some have it, some dont (or is less noticeable). It's depending on which CM commits were included in that ROM or on which CM nightly it is based. Also depends on the kernel that is used. For some is better, for some is worse, I think it's depending also on the device itself since not all are identical

Sent from nowhere over the air...
[HTC One S] The Setlaz:
I didn't use any Backup & Restore software. It reinstalled automatically the apps, just had to reconfigure them... (I guess that's the point of a clean install... not to bring back the bugs in the system during the restore phase...)

Should I have wiped the SD-Card too ?
[HTC One S] djsubtronic:
Guys it has been a good run indeed but the annoying issues started getting too much for me, plus my contract was coming to an end so I have got myself a Nexus 5. I'll probably hang around here for a bit though in case anyone else is thinking to do the same and has any questions. I am running CM11 on it too..
[HTC One S] horno46:
I'll be getting a N5 in the summer but I'll probably keep it stock.
[HTC One S] el_smurfo:
Sadly, this phone has been the end of CM usage for a lot of folks...
[HTC One S] Brushstroke:
It is unfortunate that people are leaving this phone, but I probably will at some point this year too. It's been a good run and I love this phone but I think I'm ready to get something like the Moto X or the Nexus 5. I'm leaning towards the Moto X.
[HTC One S] ATSPerson:
Well I'm sticking it out. My contract is up in about 2 months and as I think CM has given the phone a new lease of life, I'm taking the opportunity to reduce my costs.

That will leave me free to upgrade on my own terms.

Sure there niggles the WiFi dropping being the main one, but I can live with them... For now.
[HTC One S] Brushstroke:
Yeah, I won't be upgrading in the next month or something, but probably toward the end of this year or so. So I'll still be here for awhile. :D
[HTC One S] nicknc:
... and I'm the guy that has yet to buy a phone new, lol.

This phone was a used purchase, as was the phone it replaced, and the one before it, lol.

CM and XDA certainly help save me a ton of cash.

I reckon I'll join you guys on the n5 in a year or two when you list yours on eBay. ;)
[HTC One S] asinglenoob:
SOD Fixed (for me)

I found that my SOD and random reboots were fixed by flashing Bubba Kernel. It's been two days now and no SOD's or random reboots and I also don't seem to have issues with WiFi drops anymore. To anyone who is still having issues with SOD's give it a try, it fixed my issues.
[HTC One S] nicknc:
Switching to either IceCode or Bubba does fix it for some (like me), but for others it either does not or worsens the issue.

The reality is that, much like the fast dormancy problems, this is really something that should be incorporated in CM itself-- namely that official CM builds should not require the use of a separate kernel in order to provide a reliable experience.

We are dealing with nightlies, however, so I think most of us will be content if both the fast dormancy and the SOD issues are fixed by the eventual release.
[HTC One S] Dave77459:
It was for me. I bought a Nexus 5 the first day it was available and have been loving it. I use the Apex launcher so the user interface looks just like it did on my HOS. For me, the killer feature is the wireless charging. I simply love that.

That said, I am keeping my HOS for now because I can run the Fitbit app on it to sync my wife's device. I also run a sleep app using it. So I get to experience the joy that is CM11 on my HOS. Running my N5 during the day and my HOS in the morning just reminds me how unstable CM11 is. Apps lock up on it very frequently... could be the sleep app, I dunno. Could be the Fitbit connecting randomly, I dunno. About every third time I try to use it, I find it locked up. Screen on or off, non-responsive and hard to even get to boot.

I used to think I would switch my wife from her stock HOS to this one running CM11 so that she could work with her Fitbit. I just can't imagine her using something that is so frustrating though. If momma ain't happy, nobody is happy.
[HTC One S] nicknc:
This is 100% the reason that my wife is now on Windows Phone after 3 years of Android (CM or otherwise). The 1-2 days a month she even encounters any errors at all, she can quickly resolve with a reboot. She absolutely loves it.

It really cut down on the WLOD (wife look of death) errors I was getting.

For me, I still love the stability and performance that CM brings to Android. All it takes is a quick visit back to stock (or one of the other frantically hyper-featured forks) and it's clear the value CM brings.
[HTC One S] djsubtronic:
wrong thread
[HTC One S] bobjbain:
Had my HOS for near on 2 years now and I probably won't upgrade, none of the new phones really take my fancy (not that I really know what is out there) and I can do everything I want to do on my HOS.

CM11 is not that buggy for me, the WiFi issues are the biggest concern for me, now if only I had spare time I could spend some of it looking at the issues myself and try to resolve them.

Sadly I got my wife an Android phone and tried to un-stock it for her but she just couldn't get on with it. In the end I had to get her an iPhone, she is now a happier bunny. therefore I am happier.
[HTC One S] Brushstroke:
It's not that buggy for me either, especially with a custom kernel (I'm using IceCode). I haven't had any WiFi issues so I'm not sure what you're referring to there. The only thing I've noticed is that, when I was using Bubba kernel, Bluetooth music playback seemed to disable being able to play through the headphone jack. Not sure if that's a ROM or kernel issue though since I never tested this with the stock CM kernel.
[HTC One S] anant210:
Same here, CM11 has been rock steady and by installing Bubba & ART, I do not have any micro lags while operating the phone. This is easily like the stock HTC software which was installed on this phone (in terms of stability). The only concern is a bad battery life with 3G & sync activated.
[HTC One S] bobjbain:
The WiFi issues I have are connectivity ones. If I go from work (802,1x EAP) to home (WPA2 PSK) then the phone refuses to connect to my home network unless I press the WPS button or reboot the phone. If I go from the pub (the Cloud) to home then it will connect fine.

I'm thinking that maybe one of the 802.1x EAP WiFi settings is getting stuck in memory and confusing connection attempts. I guess I need to get a logcat for when I try to connect at home to see what the problem is.
[HTC One S] el_smurfo:
Good thing djsubtronic moved on...hate to see the performance of WhatApp once Facebook acquires them...

http://www.theverge.com/2014/2/19/5427332/facebook-is-buying-whatsapp
[HTC One S] djsubtronic:
OMFG.
[HTC One S] nicknc:
Not even performance-- consider the privacy implications.

Curious to see if it will be absorbed like MS did Skype or exploited like Google did with Waze.
[HTC One S] djsubtronic:
The article seems to imply the plan is to keep WhatsApp as it is and continue it independently alongside FB's services (like FB did with Instagram)... so here's to hoping.
[HTC One S] el_smurfo:
I just tried Waze today...thought I accidentally clicked one of the Kid's cartoons...and there were 2 whole users in all of my 100k population town. Woot!
[HTC One S] The Setlaz:
Well that's what I was thinking too... But I also noticed sometimes, going away from home and coming back (WPA2-PSK), Wi-Fi wouldn't reconnect neither...

It's pretty random. Like you, I connect to 802.1x EAP at work then to WPA2-PSK at home... But sometimes it does reconnect, sometimes not... I couldn't find a pattern...
[HTC One S] Insecret:
I know the solution to solve this problem, disable the security on your wireless network :))
[HTC One S] Rapier:
And you'll make happy all your neighbors as an extra :)
[HTC One S] icest0rm:
he could enable mac filtering and leave disabled wireless security ;)
[HTC One S] Insecret:
They are happy because I leave to my place for more then 20 years and we know verry well eachother, and who ask me I give them, yeah allso you can enable mac filtering, but I made a joke about desabling wi-fi security, this is not a solution to solve this problem :D
[HTC One S] The Setlaz:
Except that spoofing MAC address is even simpler than cracking a WEP security !

Anyway, that's not a solution :p

Anyone knows what today's EXPERIMENTAL build is for ?
[HTC One S] mineIsAlreadyTaken:
There were a lot more users, it just doesn't show them all..
[HTC One S] icest0rm:
well, connecting to an open wi-fi network is far more simple than sniffing and spoofing a MAC address for a dummy user, so if he does not have hacking neighbours it should be enough :good:
[HTC One S] el_smurfo:
Jenkins changlogs don't seem to work for broken or experimental, but if I had to guess, Ethan changed something for M7 that broke our build, then built an experimental to make sure it was back working again.

http://jenkins.cyanogenmod.com/user/intervigilium/builds
[HTC One S] The Setlaz:
Alright ! Thanks :)

Oh, by the way... I flashed 20140219 yesterday evening, running smooth so far ! No freeze, no SODs...

(I even downloaded the stuff to set Bubba Kernel (I'm S-ON) to give it a try in case I'd have trouble, but didn't happen ! )
[HTC One S] intervigil:
Experimental is attempt at reducing the screen on delay for m7. It should help a little bit with the 8960s as well.
[HTC One S] el_smurfo:
Does seem to help a tiny bit. This morning, tried several times pushing power then swiping unlock before screen came up...did not work. Now, I can hit power and swipe unlock every time, though the screen still seems off for the same amount of time to me.
[HTC One S] bobjbain:
So I have done a logcat when I have been trying to connect to my WiFi when I get home, the command I ran was

adb logcat wpa_supplicant:V *:S

and basically my logcat is full of these :-

I/wpa_supplicant( 1266): wlan0: Trying to associate with router-mac-address (SSID='SSIDName' freq=2412 MHz)

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=router-mac-address status_code=1

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=5 ssid="SSIDName" auth_failures=5 duration=20

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-SSID-REENABLED id=5 ssid="SSIDName"

I then did a WPS push button connect and got

I/wpa_supplicant( 1266): wlan0: Trying to associate with router-mac-address (SSID='SSIDName' freq=2412 MHz)

I/wpa_supplicant( 1266): wlan0: Associated with router-mac-address

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected

I/wpa_supplicant( 1266): wlan0: WPS-CRED-RECEIVED

I/wpa_supplicant( 1266): wlan0: WPS-SUCCESS

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-DISCONNECTED bssid=router-mac-address reason=3 locally_generated=1

I/wpa_supplicant( 1266): wlan0: Trying to associate with router-mac-address (SSID='SSIDName' freq=2412 MHz)

I/wpa_supplicant( 1266): wlan0: Associated with router-mac-address

I/wpa_supplicant( 1266): wlan0: WPA: Key negotiation completed with router-mac-address [PTK=CCMP GTK=TKIP]

I/wpa_supplicant( 1266): wlan0: CTRL-EVENT-CONNECTED - Connection to router-mac-address completed (auth) [id=6 id_str=]

Does this actually help anyone or is there a more "complete" adb logcat command I can run to get the information?

TIA
[HTC One S] Michael1101:
20140221 doesn't boot for me. Maybe because of this commit

http://review.cyanogenmod.com/59919

I wouldn't flash it.
[HTC One S] el_smurfo:
Thanks. Came here to check this. Whenever I see a big changelog of simultaneous Kondik checkins, I assume that the build is probably broken, so I would guess it's one of the ones with his name on it. Usually gets patched the next day...

http://review.cyanogenmod.org/#/q/status:merged,n,z
[HTC One S] deniz2694:
21/2 build booted fine for me...
[HTC One S] el_smurfo:
The mystery deepens...time to make a nandroid...
[HTC One S] Brushstroke:
02/21 didn't boot with an update via CyanDelta, but it DID boot with a clean flash. And then I rebooted the phone after deleting my usual APKs (Apollo, VoicePlus and a couple other non-essentials) and it did not boot.
[HTC One S] deniz2694:
strange, i just updated via cyanogenmod updater with a dirty flash and it gave no problem.
[HTC One S] el_smurfo:
EDIT. Tapatalk totally ****ed this post. If anyone cares about system/addon.d scripts, I can repost tomorrrow. What a piece of ****. Btw, 2/20 SOD
[HTC One S] The Setlaz:
So did 2/19 for me... Had to get back to 1/19 :crying:

PS: tried to flash Bubba, couldn't get it to boot :silly:
[HTC One S] ATSPerson:
Running 21/2 no problems. No discernable difference in lags tho'
[HTC One S] Dverez:
CM Updater, dirty flash, no problem here 21/2.
[HTC One S] nicknc:
21 Feb didn't boot for me either after cyandelta flash. I bet that's the culprit, probably a cyandelta issue.

---------- Post added at 12:31 PM ---------- Previous post was at 12:31 PM ----------

Clean flash through cmupdater fixed it.
[HTC One S] el_smurfo:
Not the first time that's happened...why do you guys keep using that thing?
[HTC One S] nicknc:
Has only happened twice in as many months.

This time, I knew what happened, so it's a quick and easy fix (I always keep a recent data backup)

It really saves a ton of time versus cmupdater, and I've gotten bad builds and downloads from cmupdater too. The ability to one-click flash ROM+kernel clean script+kernel in sequence without rebooting to recovery first is very convenient.

Plus, it's nice (on this limited-space phone) to not have to constantly delete nightly cm zips.

I weigh everything I do from a cost benefit standpoint, and so far cyandelta's juice is worth the squeeze.
[HTC One S] el_smurfo:
juice is worth the squeeze? are you typing that from 1950? maybe you should have juiced it into your mr. fusion for the return trip?

btw, i used the updater and my boot failed also, so i retract my sarcasm...as i mentioned, whenever kondik crams a bunch of upstream stuff into a build at once, you're probably going to have a bad time.
[HTC One S] Brushstroke:
"Juice is worth the squeeze." Wow. Yeah really, did you step into 1950 for a few seconds with that comment?

But seriously, I agree with nicknc. It's very convenient to be able to flash the new nightly plus a kernel all in one cycle. I've had builds fail with CM Updater much more so than with CyanDelta, so I like it.
[HTC One S] nicknc:
Lol, some of us aren't as bleeding edge with lingo as are you left coast folks, but for your benefit I WAS typing that from my s-off phone running a custom kernel with s2w and dt2w and pocket detection running great!

You'll have to explain the Mr. Fusion reference-- I'm either too old or too young to get that one.

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Man, you too?

lmao
[HTC One S] Brushstroke:
Haha. Man, I live in Arkansas so if you're from the south too then I can understand since I have heard that phrase from some people in the area. I'm a bit of an oddity in this respect. I've traveled to so many different places that my lingo is all over the place and yet my speech is strangely articulate and proper. Everyone says I don't have any particular accent and that they can't place where I'm from. It's weird.
[HTC One S] nicknc:
I was stationed in Arkansas for several years-- really enjoyed the latter part of my tour there when I lived in North Little Rock-- what a nice town.
[HTC One S] Brushstroke:
Little Rock? Bleh. Come to Fayetteville, it's much better. So much more to do.
[HTC One S] nicknc:
NORTH Little Rock, lol. I used to practically live at the Flying Saucer down there on River St., but that was about the only place I would go in Little Rock proper.

I think I still have a hogs hat somewhere.
[HTC One S] el_smurfo:
I bought a red neck phone? That explains all the bbq pork going on in my yard this weekend.
[HTC One S] nicknc:
That would be "barbecue". No such thing as "barbecue pork", which would be redundant.
[HTC One S] Rapier:
In some places they grill lamb, sheep, chicken, duck, sausages, not only pork and "barbeque" became synonim with a grill of some sort, in open air like courtyard or in the forest. :)

Sent from nowhere over the air...
[HTC One S] noomarsil:
23 and 21 nightlies doesn't boot. What's wrong with them? Lastest working version is 20.
[HTC One S] Michael1101:
Same here. Also with cm installer. Apparently clean install works. But I'm not in the mood... Maybe next nightly
[HTC One S] el_smurfo:
Word of advice...don't give that speech in the American South.

There was almost no change in the last few nightlies, and no one else is complaining about no boot, so it's possibly only us, and we'll have wait for Ethan find out fix it.
[HTC One S] Rapier:
I live too far from that...no chance to do that :)

Sent from nowhere over the air...
[HTC One S] horno46:
So barbeque is just pork in the American South?
[HTC One S] nicknc:
Yeah, typically pulled and on a bun.

Probably best to pull this back on topic though-- my apologies for starting the aside with my controversial choice of phrasing. :)

For those averse to a clean flash, don't be. It's honestly good practice to do now and again and doesn't take much longer than normal.

Just do a data partition backup in recovery and then restore that after wiping all partitions and installing ROM, gapps and kernel. Very simple and only takes about six extra minutes overall.

I'm still shocked that this phone can handle subsequent dirty flashes as much as it does. Most can't.
[HTC One S] MrDuvet:
Hey,

I'm planning to fully wipe my phone and reinstall cm, since I'm experiencing some weird behaviour and random reboots with 0118 nightly (dirty flashing since 20131220). Would you suggest to use the M3 or the current nightly? Are there some important noticable differences between them and is M3 really (more) stable?

Max
[HTC One S] nicknc:
I say use the current nightly with a custom kernel.
[HTC One S] MrDuvet:
Which kernel would you suggest? I'd finally like to have stable phone I can rely on.
[HTC One S] nicknc:
IceCode is what I am on. But either that or bubba will work well.
[HTC One S] MrDuvet:
Thanks. I'll give it a try.
[HTC One S] Brushstroke:
I can also confirm that 02/23 isn't booting. What is going on? el_smurfo, you mentioned that some of Steve Kondik's commits might be behind this?
[HTC One S] Albino_Mexican:
If you would like stability, check out my unofficial build of CM 10.2 with the gyro fix in the CM 10.2 thread. :cool:
[HTC One S] MrDuvet:
Thanks for your advice but I'd rather like to have KitKat. Although the suggested combination of today's nighly and bubby didn't work quite well. After flashing and beginning to install all apps again it rebooted. I did not install any root app, restore from TB or do anything that could cause a reboot. This isn't a solution so I'm back on 0118 for now

Max
[HTC One S] nicknc:
You check your krait speed per the shell command in the op of the icecode thread?

A lot of these isolated phones with reboot problems just need more voltage
[HTC One S] MrDuvet:
I'll check that out. Additionally I noticed another "problem": There is no PDroid Patch anymore for the latest nightly since the dev ran out of time -.- . Does anybody know an alternative? I don't really like cm's privacy settings...
[HTC One S] Michael1101:
It has something to do with the data partition. When I wipe data, 02/23 boot up fine. When I restore it, it isn't booting anymore...
[HTC One S] 4thfloorcaveman:
It's is possibly problems with the apps, but are any of you using Instabridge https://play.google.com/store/apps/details?id=com.instabridge.android or Wifi Password Recovery https://play.google.com/store/apps/details?id=com.ryanamaral.wifi.passwords ?

Instabridge forcecloses for me - but then not for my friend on his N5 (untampered).

WPR just doesn't display anything. Or that is, it displays a lot of unreadable entries :P

Any thoughts? Other than not KK-ready apps? :)
[HTC One S] el_smurfo:
Bootloop fix

Anyone who has gotten the last two nightlies to boot...are you using Dalvik? This from last night's build seems like a promising fix to the no-boot issue

http://review.cyanogenmod.org/#/c/60044/
[HTC One S] F-L-Y-E-R:
No it haven't. The phone is still stuck on 'android is upgrading...' screen, tried both catches :confused:

P.S. From my point of view it's very unprofessional from CM side to upload a faulty nightlies... :eek:
[HTC One S] nicknc:
Dude, what professionalism?

It's a free service run by volunteers and amateurs. Things break occasionally.

Keep it in perspective.
[HTC One S] F-L-Y-E-R:
Are you sure? They commit changes all day long, cyanogenmod became a corporation, isn't that enough for you?
[HTC One S] el_smurfo:
That thanks from me came before that line got added...still wondering if we're the only ones with this issue right now, so not getting noticed higher up
[HTC One S] nicknc:
Did you pay for it?

---------- Post added at 01:34 PM ---------- Previous post was at 01:31 PM ----------

Thanks for the clarification.

Yeah, it might warrant a pm to [MENTION=1815755]intervigil[/MENTION] to make sure he's aware of the issue.

I'm on my phone and don't have the ability to check, but have you looked at the similar phones' threads to see if they are also having boot issues?
[HTC One S] el_smurfo:
Would probably ask for a log during stuck boot, so need someone with a computer
[HTC One S] nicknc:
Ugh. I hate having to provide logs.

So unprofessional... ;)
[HTC One S] Michael1101:
Hey hey! 02/24 booted again. I'm using art.
[HTC One S] Dverez:
I`m always using Dalvik with stock kernel and having no issues at all, installed all of the nightlies with cm updater, always wiped dalvik and cache (no factory reset).
[HTC One S] el_smurfo:
Thanks. Anyone else using ART brave (and professional) enough to try last night's build?
[HTC One S] Brushstroke:
Yup. Stuck with Cid boot animation endlessly after I enabled ART and rebooted.
[HTC One S] Michael1101:
Which nightly to you use? For me it's working with latest and art. Didn't work before.
[HTC One S] Dverez:
Switched to ART but getting messages "android.process.acore" has stopped, com.google.process.gapps has stopped, etc...after the first boot.

Getting error message storage space running out... 165MB free...

Edit:

At the first reboot further 31 apps had been optimized and the phone runs ok now... (4.7MB free space left, uninstalling more apps, pictures....)