yashsingh1/xdaforums huggingface dataset:
[HTC One S] el_smurfo:
I'm hoping the win the OnePlus smash your phone contest. At this point, nothing would give me greater pleasure than taking a bat to this thing...of course CM on that sounds like a laggy mess too, so maybe I'll just sell a kidney and get a Nexus also.
[HTC One S] Log1c.:
Indeed there are several people (including me...) with this problem.

I also put it up on the CM bug tracker

According to one reply at the tracker the problem seems to be device specific. Also I don't know anyone else with this problem who has a different phone.

But I still very much hope that it will be fixed with 4.4.3 :)
[HTC One S] :
A long press on the power button won't give me the power menu anymore, but just turn off the screen. Does anyone know what this could be about?

Edit: No weird behaviour prior to this except a notification that the Google Play Services would have crashed.
[HTC One S] kingpicus:
I have the same problem, very annoying :crying::crying::crying:
[HTC One S] provaleriy:
Same here :crying:
[HTC One S] nicknc:
Do a clean wipe and reinstall. Both of those sound like bad dirty flash symptoms.
[HTC One S] Brushstroke:
As much as I like the OnePlus One on paper, their marketing campaign kind of bothers me. Smashing your phone is just wasteful and I'd rather donate my current phone if I really wanted to get rid of it. And you'd be getting a phone made by a company not even a year old that is banking its success on hype by selling its devices at a huge loss. Google can do that with the Nexus line because...well, they're Google. They can afford to sell their products at a loss. We don't know if OnePlus is gonna be around in a year and if they go under, you'd be SOL when it comes to support for that thing.
[HTC One S] el_smurfo:
Yeah...was mostly a joke...I am also bothered by their tonedeaf campaign (smashing a phone on Earth Day, really?) and am through with CM after this phone.
[HTC One S] Brushstroke:
Yeah, same here. Looking forward to trying out some other ROMs like Omni or Mahdi that have never been available for this phone.
[HTC One S] ThomasHunter:
Yeah, I'm not a fan of the phone smashing either, but I do very much like the phone on paper. Especially that it has the N5's specs with 150% the battery.

And you know, in 3 months or so the OnePlus fellows are going to kick off this whole thing, so I can just see where it'll be in six months (which is, coincidentally, also when I'll have this phone for two years).

You know, maybe OnePlus will be bankrupt in six months, and maybe there'll be enough invites for everyone and their cousin by then. [emoji4]
[HTC One S] Rapier:
Unfortunately not all can participate or get an "invitation" to buy it. Seems like some are more fortunate than others.

Though, we're getting more and more off-topic here, even if the device has CM 11S on it
[HTC One S] 1aladdin1:
Flickering Display with April 16th nightly

Since flashing April 16th nightly I experienced a flickering display - with only the lower third of the display being affected. After update to April 25th nightly the problem seems to be solved - no flickering display anymore.
[HTC One S] mikronac.ns:
May I ask for some help?

I have 1.11 radio and some problems with signal drop. May some one give me a flashable zip of 1.15 EU radio?

I tried flasing this http://xdaforums.com/showthread.php?t=2255906 but as I remember, we use radio partition, not /etc/firmware for radio in AOSP roms, so this not helping anymore...

How to update radio partition to EU 1.15 permanently?

I am S-off'ed...
[HTC One S] nespresso33:
You have to flash the called Sense version, you can try the 1.20 http://xdaforums.com/showthread.php?t=2450807
[HTC One S] Rapier:
Flash Sense V6 radio installer from HERE and choose 1.15 radio in the aroma installer.

NOTE: Topic is old and not updated so forget all warnings about hboot lower than 1.13 and things like this. You're S-Off, just flash it
[HTC One S] benyto:
I was clearing up some space on my laptop HDD and found the zip for the 20140409-NIGHTLY build. Are you still interested? If so, I'll figure out a way to get it to you.
[HTC One S] nicknc:
That would be great. OneDrive, gdrive or drop box are always quick ways to transfer. Just pm me the link, if you like.

Thank you!
[HTC One S] benyto:
I sent you the link via PM, but it is not showing up in my "Sent Items" folder. Let me know whether or not you got it.
[HTC One S] melo563:
Anyone else have settings fc when you try to open it
[HTC One S] nicknc:
This is not affecting me.

So far, 27April with the 20Apr IceCode "seems" to be back to normal. No performance issues or freezing/lags in the four hours I have used it.

I didn't see anything in the changelogs that would be responsible for this in the past few days (24 April was horrible on my phone), so I'll remain skeptical until the end of the day.

The latest hangouts FC's with Voice+ enabled. Using the full PA gapps here.
[HTC One S] Kreon:
Can anyone explain me why hboot-2.16 requires an other ROM than the nightly build ? If I compile the sources by my one what additional steps are required to flash the ROM?

Thanks in advance!
[HTC One S] nicknc:
2.16 uses a different partition layout.

Not quite sure what you mean in your second question.
[HTC One S] Kreon:
Thanks for making that clear to me.

Basically I wanted to know why there are two different threads for the cm11 ROM. The only difference is the hboot version. I'm running hboot-2.16. What if I compile the cm11 for HTC ville by myself, do I need to consider something or can I simple flash the zip?
[HTC One S] nicknc:
Just adjust it to recognize the partition layout, but nothing special beyond that.

S-off makes it super easy.

Check in the 2.16 thread to be sure.
[HTC One S] el_smurfo:
http://review.cyanogenmod.org/#/c/63073/
[HTC One S] nicknc:
.... or use hello sms instead of craptastic hangouts.

:)
[HTC One S] el_smurfo:
I don't have an SMS plan, and only really SMS to old ladies and troglodytes, so Hangouts is my usual communication method. :cool:
[HTC One S] nicknc:
I thought you were TMOUS. How do you not have SMS?
[HTC One S] el_smurfo:
I have only ever had 2 TMOUS plans...the last one was a TZones Talk and Text plan, and this one is about 3-4 years old, has no text but unlimited data and 750 minutes. Tried to upgrade to one of their newer plans, but it was more expensive, so I'll probably end up on prepaid with an N5 when my contract is up in November.
[HTC One S] nicknc:
Just got a notification bar freeze.

You know, Dolphin has been running like crap recently, and these freezes tend to come when I'm multi-tasking with Dolphin on my phone (usually around lunch time).

Going to forgo Dolphin for awhile.
[HTC One S] el_smurfo:
I seem to get the most freezes quickly unlocking then swiping the notification bar. I used to be able to swipe it as soon as hitting power, but now it takes 2 tries and on the second, freeze-o-matic. I wonder where [MENTION=1815755]intervigil[/MENTION] spends his time these days...probably working on the OP(P)O
[HTC One S] nicknc:
I'm still putting my money on a GPU issue. I'll pay attention to how it is freezing. It destroys about 10% of battery each time it freezes like that on my phone.

As for the OPPO, what a curious name, especially given it is a palindrome that remains a peculiar palindrome when the O's and P's are exchanged, lol
[HTC One S] el_smurfo:
Also interesting how One Plus One (OPO) seems to be "a part" of OPPO, even though they denied it...now confirmed wholly owned subsidiary (if the identical phone designs weren't also a clue). I'd still consider it for $350, but not going to jump through any hoops if the N5 is just a few clicks to order.

BTW, anyone else having a ton of Google Services disconnects lately? I'll have full signal, white signal bars in quick settings and no connectivity to gmail/hangouts. Sometimes refreshing gmail fixes all and I get a bunch of old messages, sometimes it's a reboot. This phone is getting more unstable by the day.
[HTC One S] :
OT: What is it with that fake secrecy? I really miss old school consumer capitalism, where you just bought a product, used it till it was gone, broke or hoplessly outdated, and then just got yourself any new one; without too much utterly moronic fetishising involved.

On topic: Nope. It works fine, and I'm on the M5 release. My impression actually is that CM on the One S is finally getting usable again.
[HTC One S] ThomasHunter:
Hm, I've actually read very few experiences on the ville M5 build. I guess no-one here flashes them since the M-builds are almost always worse than the nightlies.

I'm still on 12/4 which has the same diseases that, as far as I'm reading, all the builds since then also have. I think I'll just stay with this one until someone reports a miraculous build with aaaall the bug fixes and reverts we need.
[HTC One S] b_ignatov:
You are not the first person who claim that 12.04 build is the most stable for the moment.I'm not gonna wait any more for a stable one....and I'll flash it tomorrow.Before that I would like to ask something regarding this build.Is there a difference in performance if I flash it without S-Off?And finally wich recovery is recommend for it?

Thanks in advance.
[HTC One S] nicknc:
27 and 28 Apr are both quite stable. Have only had one freeze yesterday (used to have them hourly)

Using the latest IceCode kernel
[HTC One S] b_ignatov:
What about battery life?Better than 12.04?
[HTC One S] ThomasHunter:
If he says they're quite stable, my guess is that battery life will also be slightly better.

On 12/4, I'm used to anything between 5 and 8% an hour when idle, the latter being ridiculous drainage of course. Oh and also, it reboots every once in a while, and sometimes those eat up 20% off your battery charge, so then it doesn't really matter how low normal battery usage is..

On the matter of being S-On: I don't think it'll affect much (I'm S-On myself as well), just don't forget to flash boot.img obviously.

And recovery... What are you on right now, any other CM11 build? If this is your first CM11 build, check the opening post for special versions of TWRP or CWM to use. I personally use TWRP, so that's 2.6.3.0-ville-SELinux. I think it's neseccary to succesfully flash CM11.
[HTC One S] b_ignatov:
Between 5-8% an hour when idle is worse than stock sense rom.
[HTC One S] nicknc:
2-3% per hour idle.

---------- Post added at 01:30 PM ---------- Previous post was at 01:24 PM ----------

Reboots haven't been an issue for me on the last two nightlies.

Also, TWRP 2.7.0.0 is preferred due to no naming bug being present for backups.
[HTC One S] b_ignatov:
Thanks to all for yours quick answer.Now my dilemma is wich one to flash??
[HTC One S] ThomasHunter:
It is, it's freaking terrible and I hate it. But I've never been on CM for the battery life actually, and I haven't had better in the last months..

On M5? I'll try that.
[HTC One S] nicknc:
On 27Apr and up nightly, using IceCode and nonQC voltage (under volt)
[HTC One S] melo563:
So my thoughts on why I can't get to my settings is that I have à theme running for the settings and something I'm the theme engine must have not been compatible any more since that is the only thing not working f'd up though
[HTC One S] el_smurfo:
Aren't themes just .apk? You can probably delete the apk with a file manager, then reboot.
[HTC One S] tim_h:
I am on the 2014-04-09 nightly. Battery life is very good (~2%/hour) without installing any custom kernel.

Are you sure it's not some app draining the battery by keeping the phone awake?
[HTC One S] nicknc:
Just got a freeze. Occurred after quickly unlocking the phone and trying to pull down the notification bar, like you suggested, [MENTION=2101224]el_smurfo[/MENTION].

Might be related to the screen on lag fix. This kicked off around that time, right?
[HTC One S] ThomasHunter:
Well, I thought about that a lot too. But particularly because 1) I've done many a clean flash and it's never been as good as 2% for me and 2) it always seemed to increase heavily when I was on data, I've kind of ruled that out.

I'm also a fanatic BBS checker, and it's almost exclusively PowerManagerService wakelocking it, and NlpCollector and RILJ in the Partial Wakelock category. I've discussed it a lot up here, and though el_smurfo had terrible experiences with the nighties from around then as well, I guess no one has my exact problem. And that just sucks.
[HTC One S] nicknc:
Powermanagerservice is a wakelock I used to get after unplugging from the charger. A reboot always fixed it (even a soft reboot if you have that enabled), but that was the only fix. Alternatively, you could try toggling your settings to allow the phone to sleep while charging.

As for the other two, they are normal wakelocks related to Google location services. Do you have Google now or high accuracy location enabled? If so, disable them if you really want those locks removed.

I also use Greenify, with great results, including the network build.prop and Wi-Fi edits, and intelliactive governor.

This gives me terrific screen on performance (with bad battery life) and awesome sleep battery life.

Hopefully, that might help you narrow things down some.
[HTC One S] el_smurfo:
Something like the screen lag fix (otherwise know as reversion to BSOD) or with the CPU governor...it seems like it's stuck in the minimum clock mode and I can sometimes get it to wake up by hitting the power button quickly and selecting reboot, but then hitting cancel on the reboot selection.

I did catch a log and there are a ton of errors but I don't even know what to do with such a thing anymore...

I see such errors as

QCOM PowerHAL Perflock release failed

Activity Manager ANR in com.android.systemui

ActivityManager PID 967

ActivityManager Reason Input dispatching timed out (waiting because the touched window has not finished processing the input events that were previously delivered to it.)

Input Dispatcher ...com.android.systemui...Channel unrecoverable broken and will be disposed.

Ton of other ActivityManager errors with % assignments to other processes.

Bunch of JavaBinder errors
[HTC One S] nicknc:
It's a shame the logs are so noisy. Would be nice to review something that is not quite so verbose.
[HTC One S] el_smurfo:
Even if I filter for errors, there are still dozens of extraneous entries that have been there all along, such as unsported RIL access, etc...
[HTC One S] ThomasHunter:
Nah, I think you misunderstood the reason why I posted them. I just wanted to indicate that there's not a very obvious reason as to why my battery usage is huge on almost any build.

I know PowerManager, RILJ and Nlp are most common and normal wakelocks and I do not seek to get rid of those as they, I think, are not the main reason of the battery usage.

As for Greenify, I have that enabled for a handful of apps, I made the one build.prop change of fast dormancy, and I'm on stock kernel. I like tweaking but not that much, so for now I'll just bite the bullet and I'm actually really looking forward to replacing my phone.
[HTC One S] nicknc:
Alright man. Thanks for the clarification!
[HTC One S] arjundas86:
I read people talking about nightlies like 04-09, 12-04, etc. but the only CM11 nightlies I see on the official CM ville downloads site are 04-22 and later. Where can I get older nightlies?

I was thinking of just flashing M5, but people have been saying some of the older nightlies are slightly more stable and have better battery life. But lately, I'm getting the general feeling that people here are not finding CM11 on Ville to be all that stable...?

I've been running SlimKat (Slim-ville-4.4.2.build.3.6-UNOFFICIAL-20140313) for close to 2 weeks, and it's been quite stable (only 1 reboot in almost 2 weeks). Battery life is pretty good... I can easily get through a day and a night, with about 20% to spare. Just some small issues like when I try to set the lock-screen slider targets, Settings force-closes. And in the Google Camera app, I don't have HDR mode - I'm not sure if the ROM I'm running has anything to do with that.

I was just thinking of switching to CM11, because I heard that it performs a bit better (phone feels faster) than SlimKat, even though Slim is based on CM. But after reading the last several pages here, I'm not sure anymore.
[HTC One S] phoenixita:
http://review.cyanogenmod.org/#/c/63130/

What's this?
[HTC One S] nicknc:
The latest two nightlies are mostly stable. Reboots are not happening for me. I have about one freeze per day, which is easily avoided and fairly quickly resolved.

I do not know that you will get any more performance or reliability out of CM11 based on your described experience with SlimKat.

If you feel that the addition of the features that CM11 offers and the bugs that are resolved are worth switching, then you will see some value in migrating.

As for long-term stability, stay off the nightly flash treadmill (which it sounds you are) and stick a LONG time with CM nightly builds that work. That is the best strategy. The four or five of us that gripe the loudest on here are the ones that flash fairly regularly. CM is notorious on this phone for breaking things in the name of adding features. Everything does get fixed eventually, but it can be quite aggravating.

On a side note, this is one of the reasons I am starting to miss the benefit of using unofficial builds of CM rather than official nightlies. It seems the other two HTC phones for which I used CM10 through CM10.2 or CM11 (glacier and pyramid) were much quicker in bug resolution and avoidance of show-stoppers. Both phones had dedicated but unofficial developers (sometimes more than one at a time, like pyramid) that were pretty good at keeping the builds stable-- certainly not the case here.

Perhaps it's time for that on the Ville, and the availability of official nightlies is more of a hindrance than a help.
[HTC One S] arjundas86:
Thanks for that response. I think I'll try the latest nightly (04/28) for a week or two and see how it compares. Yesterday I flashed M5 snapshot on my old Nexus S that my mom's using now... it seems okay so far, but probably too early to tell. Even if the performance (speed) isn't better, as long as it doesn't randomly reboot often, has a decent battery life, and solves my gripes with SlimKat, it might be worth switching.

Funny that you mention pyramid... as that's the phone I had bought for my wife, and it has given me nothing but trouble. It died within a year, and since I hadn't messed with it at all, warranty covered it. When it came back from warranty repair, the wifi seemed to be very flaky. Not working most of the time (stuck on turning on), and giving me random reboots. Once in a while it would turn on, but won't stay on consistently. At that point, I S-Off'ed, and tried flashing a few different ROMs, including CM10 (the latest official nightly from 2013-10-06) that is still running on it. Nothing seemed to fix it. Everything else is great, just the damn wifi... which is not likely a problem with the ROM.

I tried a lot of things (software/firmware related), except flashing a different radio (not sure if that would help anyway). Thinking it might be hardware related. I didn't really get support for it on the xda pyramid forum, so I pretty much gave up on it and bought my wife a Nexus 4. It's too bad, since the pyramid was a nice, well-built phone.

...Sorry for the off-topic gripe!
[HTC One S] Brushstroke:
I dunno man, I've been dirty flashing almost every nightly for the past two months with no issues. Although I did a clean-flash of 04/28 with the latest PA Gapps and IceCode kernel last night. I'm keeping this phone as a backup and want a relatively stable build on it for a rainy day. Running very smoothly. Nexus 5 should be arriving tomorrow! :D
[HTC One S] arjundas86:
Are the PA Gapps significantly different from the CM Gapps?

Also, where can I find out more about the IceCode kernel. I'd like to find out what features/benefits it offers, and where to get it.

Thanks...
[HTC One S] foeti:
Here:

http://xdaforums.com/showthread.php?p=50084053
[HTC One S] Brushstroke:
PA Gapps. See for yourself. The Gapps offered by CM are minimal and still retain some AOSP components like the Messaging and Browser apps, among others. PA Gapps gives you essentially all of the Google applications that would be found on a Nexus or GPE device and removes many AOSP components.

IceCode Kernel. I'm not a fan of the stupid wake actions like dt2w and s2w, and they don't really work as they should, but as far as battery life and stability is concerned, this is a pretty good kernel. The intelliactive governor seems to make the phone run pretty smoothly.
[HTC One S] nicknc:
Yeah, I did too for several months, including cyandelta. No issues.

Gets tiring doing build.prop edits every day though, and for me the up and down stability issues from month to month make it counter productive.

Try to flash only 5-6 times a month now. Helps keep the silly bugs away.
[HTC One S] Tipper554:
Can someone tell me how the battery life compares to stock ROM. Thanks in advance.
[HTC One S] nicknc:
Which stock ROM?
[HTC One S] el_smurfo:
It's worse...CM is always worse.

---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------

Yeah...I'm weaning myself off the nightly crackflasher horse as well. I maybe do one or two a week, when something new gets added that seems worthwhile. Unlike you, I don't revert to a stable build though...just whinge and whine about the new, fun broken features in the latest.
[HTC One S] nicknc:
That was a kernel issue fixed in the CM10.1 and forward build, I believe.

Since CM10 was unofficial, the developer (@bruce2728, IIRC) never pushed the fix back from CM10.1.

try one of the three(!) CM11 builds over. I bet it resolves. PM me if you want more help on it. My daughter still has a pyramid.

---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------

Well that's to be expected from a Californian-- your state is definitely known for its whine. ;)
[HTC One S] intervigil:
Time to update your recoveries.

See: http://wiki.cyanogenmod.org/w/HTC_fstab_updates

Also, for those of you experiencing freezes and lockups, can you get a kernel log? I've actually been using my ville for the past week or so and have not experienced anything weird. Uptime is well into 3 days, I rebooted midway through the week to update.
[HTC One S] nicknc:
I've been trying the past few times, but not successful. I think [MENTION=2101224]el_smurfo[/MENTION] managed to grab something.

Completely random freeze, but an immediate attempt to pulldown the notification bar after unlocking seems to trigger it. Freezes the screen, but can still hit power button to get to the power menu.
[HTC One S] el_smurfo:
I emailed a logcat to intervigil@gmail.com but needs to be kernel log to be useful. He said all processes starved for memory during lockup.

BTW, intervigil pointed out the troubleshooting section at the bottom of the wiki... I had to do this to get recovery to load.
[HTC One S] nicknc:
Did you use the DM or non DM file?
[HTC One S] arjundas86:
Oh, that's really good to know. Now I have hope for this phone yet. If it works, then I can upgrade my mom from crespo to pyramid... it's a fair bit faster. :)

Thanks! I'll let you know how it goes.
[HTC One S] b_ignatov:
Do you mean at all....or only CM for our devices?

My old Desire's battery life was too much better with CM 7 :) ....even my mother's LG Me P350 is better with CM 7.2 RC
[HTC One S] Cofreddi:
Big issue here to report: when screen is off and i get incoming calls i can hear the phone ringing but the screen remain black and I Can't answer the phone!!

I get no option what so ever to answer when the screen is off and getting incoming call :\
[HTC One S] nicknc:
Which nightly? Which kernel? Did you do clean flash or dirty flash? How long has it been doing this?
[HTC One S] el_smurfo:
Non. DM is for hboot 2.16

---------- Post added at 06:30 AM ---------- Previous post was at 06:30 AM ----------

Ahh, the good old days
[HTC One S] nicknc:
I figured as much. Good to have confirmation here.

Same as you, I had to delete the TWRP settings file. Going forward, probably best for the rest of you folks to go ahead and delete it before flashing.

Used rashr to flash. Pretty easy.