yashsingh1/xdaforums huggingface dataset:
[HTC One S] Forage:
I finally took the chance to try out CM on my HTC One S. Installation from stock was painless and after a week of running CM I didn't find any major issues yet.

Some observations:

Power button delay is present, but not too annoying most of the time.

Unlock slide doesn't get loaded/displayed properly some of the times, showing a big square border around where the unlock options should be. Pressing the power button twice to show the lock screen again usually solves the issue.

No spontaneous reboots observed, though it did pop-up with the sim unlock screen again ones.

Battery use is worse compared to stock by 0.5 - 1 day. Where stock lasted me 1.5 - 2 days, CM doesn't last more than one.

The phone gets quite warm quite fast when using it.

Internet (mobile as well as WiFi) drops quite often for a short period. Connection bars remain up, but no content is loaded any more in e.g. the browser.

It would be great to see battery use drop to have the phone last longer without recharging. This is my main problem with CM so far.

I'm not using any apps like Greenify as I believe they should not be required. BetterBatteryStats really only lists the RILJ partial wakelock as one that shouldn't be that high, despite having location reporting disabled.

The connection drop is something that should be addressed as well as it makes phone usage unreliable.

Setup:

HBOOT-2.13.0000

RADIO-1.15.50.05.29

CyanogenMod M7

HTCdev unlock

S-ON

Manual boot.img flash
[HTC One S] el_smurfo:
For signal drops, search this thread for some build prop edits that help a lot of TMOUS users. The most important seems to be setting fast dormancy to 0, but I usually paste in these as well.

ro.ril.disable.power.collapse=0

ro.ril.hsdpa.category = 24

ro.ril.hsupa.category = 6

ro.ril.hsxpa = 4

ro.ril.radio.svn=19

ro.telephony.ril.v3=skipradiooff

I have never heard of the unlock slide issue. I would recommend using the latest nightly...it's certainly no less stable and has some other fixes such as a slightly reduced turn on delay and the new "heads up" notification feature that's kind of neat.

For battery use, most of the gimmicks don't work for me...Greenify has always seemed like a total placebo. I have had pretty good luck with using Privacy Guard to block the wake up and keep awake permissions for Google Search and Play Services, though just disabling Google Now also helps a lot. Icecode kernel is also recommended, but you need S-OFF for that.
[HTC One S] Forage:
My carrier is Vodafone, in the Netherlands. Would you still recommend those settings if you say it's aimed at TMOUS?

Ah yes, Privacy Guard is one thing I forgot to mention. It's nice to have, but a bit annoying in its current form.

I use it to prevent location usage in some apps, but I had to resolve to permanent blocking (per app) instead of deciding on a case by case basis. You'll get flooded with location access requests when not doing so. It would be better for the guard to have some kind of session awareness, blocking access for the current app usage session.
[HTC One S] el_smurfo:
Worth a try...I think it's carrier dependent whether fast dormancy is enabled or not. Also make sure your network settings are 2g/3g in the quick toggles and 3g preferred in the network settings.
[HTC One S] superbalza:
Great observation! I confirm to have all the issues you reported (apart n. 2)..

Where do I have to paste the init settings to enable fast dormancy?

I'm also interested in getting the battery last longer..

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] nicknc:
Paste it in the build.prop file located in your \system folder. You will need a root explorer and root text editor to accomplish this. The fast dormancy setting should already exist in your build.prop (with a stock value of 1), so look for that line and change it.

A few pointers:

- I kept a separate text file on my SD card with the desired build.prop entries that I would copy and paste into my actual build. prop after flashing a nightly

- do not make a copy of your build. prop and attempt to overwrite the existing file instead of editing it. Inevitably, you will forget to adjust the file permissions and will get stuck in a bootloop

- fast dormancy value of 2 in some markets appears to work fine (and is the functional stock value on a few other TMobile phones I checked), and will allow you to benefit from the battery savings of having FD enabled.

This edit only fixes one particular kind of data drop--related to an incompatibility of fast dormancy between this phone and particular markets. So, there is a chance that you will still experience other kinds of data drops.

I hope that clears it up a little.

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

Updating your radio might be a good idea. Fast dormancy should not cause a data drop when connected to WiFi.
[HTC One S] 808phone:
Nick,

"- fast dormancy value of 2 in some markets appears to work fine (and is the functional stock value on a few other TMobile phones I checked), and will allow you to benefit from the battery savings of having FD enabled."

I should try this and see what happens. Thanks!
[HTC One S] superbalza:
I think the problem in battery life is the display handling.. Look at my screen

I use the brightness almost at 0 level!

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] Spakainz:
The same problem with battery drain - screen. Nightly #6-21 Icecold#21
[HTC One S] Forage:
Just to be clear, you are talking about "ro.ril.fast.dormancy.rule", no?

My carrier is supposed to support FD. Where I assume setting it to 0 means disabling it, what does 2 do?

I was thinking about this is well, but from what I have found it is not without risk. 1.20 is the latest, no?

I'd hate to resolve to S-OFF, but if it's worth a shot than I'd might as well give it a go if there aren't any options left.

FD might not be a solution for the data drops, but if it improves battery life it's already worth it.
[HTC One S] el_smurfo:
2 seems to be stock on many carriers, but I have best luck with 0. I seem to oscillate back and forth between the two values, but the one thing I do know is that the phone is very frustrating with I forget and leave it at 1 after a flash.
[HTC One S] 808phone:
> Greenify has always seemed like a total placebo

No, I don't think so. I can verify that without it, the wake locks are terrible for some apps. I greenify all the ones that I don't care about and the battery life increases a lot. I agree that this shouldn't be necessary, but unfortunately if the phone is sleeping, it seems to useful to use greenify.

I set the brightness curve so the display is dimmer when using it normally (not too much).

What seems like a placebo is the task killer. It seems like every time I use it, it says it's killing 6 apps. But what 6 apps?

I am trying IceCode with the lower voltage table and will see how that works. Also fast dormancy set to 2 today.
[HTC One S] nicknc:
1.35 is the latest for non-US, I believe. 1.20 is the latest that supposedly works on TMOUS. I think [MENTION=5410350]Brushstroke[/MENTION] was the one that reported issues on TMobile with 1.35

And yeah, that's the correct line for fast dormancy. I got fewer data drops with 2, but would still get them. To clarify, the issue appears to be between this phone and how it handles fast dormancy on some networks-- not whether or not fast dormancy is supported by the carrier.

I posted some links to the Ativ and MotoX (I think) forums awhile back here showing they had similar problems.
[HTC One S] 808phone:
Dormancy set at 2 doesn't work for me. I just leave it at zero.

I am trying CandyKat right now and it seems so much faster than CM11. I don't understand this since AFAIK CandyKat is based off of CM11. Really weird.
[HTC One S] el_smurfo:
Weird... That candy rom looks like your garden variety cm based blender rom. Were you using a cm nightly or m release, because m builds seem pretty bad?
[HTC One S] 808phone:
I was using CM11 Nightly. In general CM11 has always been OK in speed. Not terribly fast or anything. I couldn't believe how much faster my phone was running after I installed CandyKat. I will see how the battery life is with this ROM. CandyKat has a few extremely useful features.
[HTC One S] Rapier:
CandyKat is no longer on CM base, it's on Slim base since 1.4.0, maybe that's the difference

Sent from nowhere over the air...
[HTC One S] _kevn_:
Does your second point look like this? If so, then you may have touched the lock screen widget accidentally and not noticed. It's prompting you to unlock to go to the info from the widget.

*edit* side note OT. Attached pictures in Tapatalk look terrible! [emoji90] hmm I just looked at it again and it looks better. I guess I didn't give it time to load completely or something. Or maybe it's just late and I need to go to bed

transmitted via skynet
[HTC One S] fax11:
hi, I had the same probleme by updating whith CM updater, I finally tried to boot boot image from the nightly using terminal on my computer and wifi is back. after that I can lock folders too, that I couldn't do before.

Hope that it will help you ;)
[HTC One S] 808phone:
Are you finding it faster? Big difference here.
[HTC One S] :
The thing with me is that I'm using the Icecode kernel, so the reason I asked was to see if those wifi issues I experienced were a rom-based problem or if they were something about the kernel. Fixed it by flashing the CM kernel that came with the nighlty I am running (I'm s-on, in case you wonder) and then re-flashing Icecode.
[HTC One S] Forage:
Yeah, that's what I mean indeed. Ok, good to have that one sorted out, ty. It's the clock that I'm touching by accident every once in a while.

Funny how a new user like me perceived it as a bug/rendering issue. To me this indicates that the design fails to deliver the intended message.

It isn't until you know how to reproduce it that you'll notice the lock screen widget becoming smaller when you trigger the "error". Before it was just the big block appearing all of a sudden.

Anyway, an interesting topic for some other time in a more appropriate place.
[HTC One S] el_smurfo:
If you disable all lockscreen widgets and delete LockClock, you get a clean lockscreen which does not respond to any touches other than the lockring and the notification shade. I have pretty big hands, so always was activating something on the lockscreen....Never understood the purpose of lockscreen widgets anyways...
[HTC One S] superbalza:
Yes, that bug is the "ghost touch bug" (© me LOL)

Is like the screen touches itself when waking up the phone.. There is no fix, I just have a lockscreen without any clickable widget..

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] mikronac.ns:
Do anyone experience music struggling when listen it over bluetooth headset and when unlocking/waking up phone? I'm on latest Bubba kernel...

Sent from my quietly brilliant One S
[HTC One S] Dave77459:
I have a problem where the CM Downlaoder constantly says it is downloading an update (it claims there are 8), but it does nothing but keep my phone awake. That downloading arrow is so annoying.

Anyone point me to a fix?

TIA!
[HTC One S] |RaVeR|:
I had the same problem a while ago.

Fixed it by clearing the data on the 'Download Manager' and 'Downloader' app, then rebooting. Good luck
[HTC One S] nicknc:
Yeah, I always did with intellidemand and ondemand governors. Interactive did not seem to have that problem.
[HTC One S] Yoshi2889:
Try the link I just added in my post :)
[HTC One S] melo563:
Yes I am using the 19 th ones already for a couple days I ran on art using the 14 th ones and half force close have you tried it?
[HTC One S] Yoshi2889:
I am using the packages in that topic and they work fine for me... Tried fixing your permissions in the recovery?
[HTC One S] melo563:
No I didn't. You didn't get any fc?
[HTC One S] Yoshi2889:
No, I don't, I can use every app included just fine.
[HTC One S] fusk:
How do you update hboot to 2.16 ?

And what does "old recoveries" mean when 2630 is the latest version ?
[HTC One S] Yoshi2889:
I am running 2.15 here and it works fine, there are several topics in this board which explain how to update, and version 2630 of what exactly?
[HTC One S] mo976:
Just flashed your 11/22 straight from 10.2 and so far so good only thing I noticed is that if you swipe on the stock keyboard it dissapears... That and I had to uninstall play store because it would not connect, a reflash of gapps sorted that out
[HTC One S] Inferi0r:
Dont update if you cannot find this.

2.6.3.0 isnt compatible with 2.16, there is a compatible 2.6.1.0.

Just use the search button.
[HTC One S] Maurice5813:
my sound quality is poor, or moderate. I know this device is louder than this:D Anyone having this issue?
[HTC One S] nicknc:
+1 to that!
[HTC One S] fusk:
I know they made one compatible with 2.15, but the initial wasn't and so i see other recently released roms requiring 2.16, so there must be some sort of advantage even tho yours works fine with 2.15.

Version of twrp. But i see someone else mentioned it wasn't compatible with 2.16, but version 2610 is.
[HTC One S] leald:
Any possibility of the Google dialer and Google contacts like in the nexus 5 being integrated?
[HTC One S] fusk:
So far so good, now i just need volume rocker wake, being able to set hardware buttons and clear all programs in the multitasker thingie.
[HTC One S] usaff22:
Unfortunately the new Google dialer causes issues when accepting or starting a call - it black-screens. I've tried it personally.
[HTC One S] Rapier:
Which new Google dialer? The one integrated in KK it's working fine in Beanstalk
[HTC One S] Phantom Pt. II:
The one that tells you who's calling if the number is not in your phone book and also finds you places numbers when you type in a business name.

Sent from my One S
[HTC One S] Rapier:
Maybe it's not a new dialer but the integration with Google Search. The one we have does look similar with the one from Nexus 5 maybe only this search doesn't work. Anyway, here in Romania, I dunno how much we can use this since for this to work I understood that the number should be found somewhere over Internet in order to be displayed. Maybe for other countries it'll work.
[HTC One S] mo976:
I think its officially at least a stock image feature and not an aosp feature my wife has it on her nexus 4 with stock KitKat. Oh and it works here in Israel so I'm assuming it should work in Romania as well.
[HTC One S] Michael1101:
I wouldn't count on that. Here in Germany it also doesn't work. Only when I set my language to English.
[HTC One S] ElJeffe:
I am experiencing this also on stock kernel so it is not Bubba related. It got worse during the last week or so.
[HTC One S] Lucaman89:
Just installed on my S with S off using the 09/06/2014 stable release.

The main cons is the battery. With stock ROM i can get 1.5/2 days with cm I can get only 1 day.

Also when I turn on wifi, sometimes it takes a while (10/15 seconds) to connect. Even if I am close to the router.

I also experienced a random reboot using the facebook app. But is happened only one time
[HTC One S] :
You might want to try a custom kernel. I usually get something in between one and two days on an undervolted Icecode.
[HTC One S] djsubtronic:
Hey everyone, long time. So did they finally work out the wake up lag?!
[HTC One S] el_smurfo:
Not as far as I'm concerned. It seems pretty random, but I can have delays of 3 seconds, even after the latest patch last week. Last night, trying to use just the screen to see in the dark, I thought I missed the power button it took so long for the screen to come up, went and turned it off, back on, off, on...I do that a lot, along with a lot of pawing at a dark screen, hoping for it to unlock. I suspect it's a different panel than many others have, but it's my single most frustrating problem with this phone.
[HTC One S] mikronac.ns:
I will make video tonight to see how fast my phone reacts on waking so we can do a comparison...

Sent from my quietly brilliant One S

---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------

Sent from my quietly brilliant One S
[HTC One S] Lucaman89:
For me. I don't have a delay at all. Smooth as butter. Stock kernel.
[HTC One S] |RaVeR|:
The delay is still there, usually takes around a second for the screen to come on, although occasionally is takes 2-3.

I remember this bugged me like hell when this bug was 'new' (it first appeared after the migration from linux-3.0 to linux-3.4) but then the delay was shortened somewhat and it stopped bugging me.

This may in part be because I got used to it. I suspect it's the same story for many others here.
[HTC One S] vanwoudt:
You're right. It does not bug me at all.
[HTC One S] el_smurfo:
It's the non repeatability that bugs me. There must be something causing those 2-3 second times, and it often has me thinking I missed the button and turning the phone off again, making it more like 10 seconds
[HTC One S] |RaVeR|:
You're right to find this annoying.

In the days after the migration to kernel 3.4, I was so bothered by it that I pledged to find this issue myself (many many pages back in the 10.1 or 10.2 thread)

I was very determined to find the bug, but after hours and hours (even days) of debugging, I simply started grasping how complicated kernel development is :) There's just soo many things I'd have to figure out before I could make any kind of meaningful change to the code.

As far as I remember, In the end I was going to try to compare the performance of a 3.0 kernel to 3.4. On 3.0, the display was instant-on.

I still maintain that by comparing both, it MUST somehow be possible to track down what's causing this. Maybe there's a way to see which functions take up most of the kernel's time? Or which interrupts take up most of the time? And then compare 3.0 to 3.4 based on that? [MENTION=1815755]intervigil[/MENTION] ?

Although I had a bit of experience dealing with the kernel before, my time, expertise and will to fix this ran out. The experience kinda put my feet back on the ground. The delay has been bothering me a lot less ever since :D

My advice would be to choose your next phone based on the quality (and likely continuation) of CM support. I know I will.
[HTC One S] el_smurfo:
Unfortunately, there not much cm is doing that interests me these days... Just a convenient way to get AOSP on the device. Wife and I are on the bubble about just picking up a couple nexus 5s and moving on... only the camera is holding her back
[HTC One S] intervigil:
The 3.0 kernel was basically using the HTC code for everything except the gpu/display driver. I'm really not too sure what HTC is doing with their power button code, it's always been custom and not very compatible with original upstream Qualcomm pmic8xxx-pwrkey code which we end up using.
[HTC One S] Brushstroke:
Hey, how have things been going over here?

Sent from my Nexus 5
[HTC One S] el_smurfo:
Same ol, same ol (see above)
[HTC One S] Brushstroke:
Yeah, I see that. I sold my One S. It's nice not flashing nightlies all the time now.

Sent from my Nexus 5
[HTC One S] el_smurfo:
Yeah... I've slowed down a lot... Trying to talk the wife into matching n5s...
[HTC One S] Brushstroke:
You should do it! The Nexus 5 forum is quite a bit larger, many more ROMs to choose from. To be honest though, I've found none of them that offer functionality that I can't get from Xposed on the stock ROM. I also just tried the Android L Developer Preview. It's really barebones and kinda buggy at this point so I didn't keep it on my phone, but it gives a glimpse of what Android 5.0 will look like, and gives devs a chance to get their apps ready for such a large UI change.

Fun stuff. :p

Sent from my Nexus 5
[HTC One S] |RaVeR|:
Cool. Do you mean the changes that HTC made to the Qualcomm code to accommodate the specifics of the phone design?

And because the design of the phone is not open, it's really hard to tell what exactly they were trying to accomplish if you're only given their resulting code? Since that code also contains a lot of clutter that has nothing to do with the design?

Interesting. Not that it makes any difference in this case, but I find it nice to understand why things are happening :)

What about the idea of 'profiling'? Would it not be possible to see where this 1 second of delay is coming from by detecting the interrupt that's way too late or the function that takes a second to execute?
[HTC One S] Dave77459:
I left my HOS for N5, and never regretted it, not a moment. The N5 camera has never been bad for me. I loaded up the SNAP camera that worked on my HOS and it works great on the N5. Even better is the newer Google Camera, with the Blur feature. On my recent vacations, I used the PhotoSphere to capture the ambiance of a few places that mere photos or even panos never could.

The best camera I ever had was the HOS stock camera, and I gave that up for CM. The N5 camera is better than the CM camera, IMO.

The feature I can't do without now is wireless charging. My next phone will have it, or there will not be a next phone. :)

Dave
[HTC One S] H2Oxide:
SIM ERROR

So I'm running the M7 build of this rom and I keep getting what looks like a sim error. It seems to be pretty random and I have had it with other builds as well. Check the attached screenshot. It's the gray sim icon with the question mark that keeps coming up. Is there any way to fix that. Obviously it's pretty annoying since I don't have any reception when this error occurs.

[IMG="sim_error_icon"]http://www.kingdomcome.nl/mail_images/Screenshot_2014-07-04-09-18-44.png[/IMG]
[HTC One S] el_smurfo:
M builds seem like a buggy bummer... Try latest nightly... They are generally more stable.

BTW, anyone else notice animation settings now have a slider in Dev settings? 70% seems just right for me right now
[HTC One S] vbbasti:
Can someone tell me the latest stable nightly?
[HTC One S] mikronac.ns:
The last one...
[HTC One S] vbbasti:
Tried the last one but WiFi isn't working...
[HTC One S] superbalza:
The world is upside-down! LOL
[HTC One S] redjamesg:
Did you dirty flash?

That sounds like the usual complications due to too many dirty flashes or too far between the versions without a clean flash.
[HTC One S] el_smurfo:
Or forgot to flash boot.img.
[HTC One S] mikronac.ns:
Every day I have at least one random reboot... I am using a volume rockers to wake up phone and I thing that is maybe related with using them. I disabled this option and I am waiting to see will I have reboots in next few days... People which experiencing random reboots, are you using volume rockers for waking up phone or not?
[HTC One S] el_smurfo:
I have about 1-2 per week... No volume wake
[HTC One S] melo563:
No volume wake here. But I get at least 1 to 2 reboots a day.
[HTC One S] maluus:
Two things to share:

1- Although it seems like its rebooting most of the time mine are ui restarts. It asks the pin code so it might be confused like it rebooted.(As a side note I don't mean that it doesn't actually reboot from time to time but most of the time it is just ui reboots.)

2- I delete all the things in the rom that I don't use. Recently I decided to remove again theme related apps in the rom. So I removed theme chooser and provider apps. it works without problem unless you try to change the wallpaper. in this case for the normal wallpapers it reboots the ui albeit it takes a bit of time. but if the wallpaper you want to switch is a live one (in my case go weather ex live wallpaper) it starts to reboot ui but never pass that. stuck in the cm boot animation. What I wonder is that if this is how it supposed to act or some unexpected behaviour? Because if it's the supposed behaviour, in my opinin it is not logical to bound such a basic function to an added theming ability.
[HTC One S] mikronac.ns:
OK, rockers doesn't make problem... Than we have problems with theme engine, I don't know... My phone sometimes reboots while I texting and sometimes it reboots when it is in sleep mode...
[HTC One S] el_smurfo:
I suspect all the recent reboots and performance issues are theme engine based... Do you use Swiftkey, because I feel it's high memory use contributes to reboots...