yashsingh1/xdaforums huggingface dataset:
[HTC One S] djsubtronic:
Not sure if this is a widespread issue from the last week or so, or whether it's due to my aggressive app hibernation on Greenify, but I am noticing that after some hours of boot, I stop receiving push notifications from most apps. I don't think it's a hibernation issue with Greenify, because it looks like apps are getting killed when in the background, even if they are running as a service. There's over 200 MB of RAM free so I don't know why this is happening.

Anyone else facing similar issues, or have any ideas?
[HTC One S] drkxyz:
Built for HBoot 2.16

Hi guys, new built is up for hboot 2.16 - 20140120. Enjoy ...

https://drive.google.com/file/d/0B0ajti88ZAFzYU9CNDFkdThtbFU/edit?usp=sharing
[HTC One S] el_smurfo:
I ditched greenify for this very reason. Was missing keep alarms. Did a bit of experimenting, and the battery savings of greenify was negligible for me. IMO, just another in the long line of placebo task killers.
[HTC One S] djsubtronic:
I was beginning to think the same thing. I actually ditched it ages ago but got the donate package in order to kill Google Play Services from killing the battery on the more recent builds. I've frozen Greenify for now and will see whether that was the culprit or not.
[HTC One S] el_smurfo:
Get the zip from pa gapps thread or banks gapps thread.
[HTC One S] rosswhite:
Random Off Topic Post

Really nice minimal calendar widget:

Today Calendar Widgets (Free) - https://play.google.com/store/apps/details?id=com.underwood.agenda.free

Today Calendar Widgets (Paid) - https://play.google.com/store/apps/details?id=com.underwood.agenda
[HTC One S] MattDN93:
I'm using the 13-Jan-2014 builld for HBOOT 2.16 and I turned on ART, rebooted and waited for the cache to rebuild, and it ran fairly well. I did get more frequent random reboots with ART though, but it felt similar in performance to Dalvik. I'd suggest if you really want ART wait a bit longer; if you HAVE to have it the 13th Jan nightly will run it though.

---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------

So you'd recommend rather ditching Greenify and twiddling with CPU governors and sync settings etc (the usual list of things) to get better performance from the battery? I'm getting say 12hrs battery life which I'd consider reasonable on a unofficial nightly KitKat ROM. Any better figures?
[HTC One S] el_smurfo:
I'm not much for recommending, but in my personal experience, greenify doesn't really provide much benefit. Android users always seem to want to control how their apps are running in the background, but Android itself already does a perfectly fine job of this...it's one of it's major strengths. If you have a rogue app you can't do without, like Play Services before the recent update, then it might help you, but I generally ditch apps that misbehave, rather than modifying my system to accommodate them (looking at you, Facebook). I have also played around with AppOpps, and it lets you turn off the wake permissions on apps, which seems like a better option than a resident app waiting to force hibernate.

FYI, looks like today's build failed, but 1/19 has been running well for me for a day.
[HTC One S] elias.acab:
Does 1/20 keep randomly rebooting? Or is it stable enough for a daily drive?
[HTC One S] Brushstroke:
What do you mean? 01/20 is working fine for me.
[HTC One S] el_smurfo:
That was built yesterday. Not sure why the dates are messed up, unless the server is hosted in Europe or something. Today's build failed

http://jenkins.cyanogenmod.com/job/android/56033/

---------- Post added at 02:46 PM ---------- Previous post was at 02:44 PM ----------

I've had 1-2 random reboots with 1/19. 1/20 didn't really have much in the changelog, so I assume it's similar.
[HTC One S] Brushstroke:
I see. I've noticed a lot of the recent builds have been appearing the day before they're dated, or the build time is always something like right around midnight in the US. The server probably is in Europe somewhere.
[HTC One S] jnne2012:
And it is good thing :)
[HTC One S] Hackbert:
I still have a problem with launcher3 and the cLock. My calender in cLock only show infos in google expierience launcher, not in cm one. I cant find info here. So is that still a problem or can i fix this bug?

Sry, i am tryn to find smth about that, but i couldnt...

Gesendet von meinem One S mit Tapatalk
[HTC One S] ZALACAYN2:
i have 2.15 , radio 1.20 , CM DAY 20 WORK VERY VERY GOOD 0 PROBLEMS
[HTC One S] blinksilver:
I might be on my own with this one, but I figure its worth a post. I DL'ed the newly released FFVI android edition and it would not even run on 1/18. I know there are issues with xposed but I've never used it.

Also there is at least one review on the play store of a fellow with a One S playing the game...
[HTC One S] djsubtronic:
Problem: 0
[HTC One S] jnne2012:
Very nice to hear, but can you even try to speak proper english? And leave caps-lock alone. It's really nice that we have many stable Kitkat roms for this device. :)

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] ZALACAYN2:
Excuse me , i have boot 2,15 and ROM of the day 20 january , forma me is good no reboots and fast but the best is the battery drain is wonderfoul

Enviado desde mi One S mediante Tapatalk
[HTC One S] Rapier:
At least he tried... :)

I think it was just a joke, everyone here understood what you were saying, there was no need to detail

Sent from nowhere over the air...
[HTC One S] stunner2002:
i'm on 01/19 build and 1.20 radio and if i connect to a wifi and then try to connect to a different wifi it wont connect.

Same on radio 1.15. Wifi starts working after a restart. Very annoying. Anyone got a solution?
[HTC One S] jnne2012:
Dont take my words too seriously! :)

Only thing i found is that when you try to change theme in themer launcher the phone restarts but never get past from the loading screen. Anyone can confirm this? And yes, i know that themer is on beta stage and things can happen with it but just wanna know is it common problem. 20th build, s-off, 1.15 radio and stock kernel.

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] nespresso33:
No the theme engine is working good on my phone since the beginning.
[HTC One S] MattDN93:
I think there is a discrepancy here. Is [MENTION=4592817]jnne2012[/MENTION] referring to the app "Themer" or the CM theming engine, as they're two separate things entirely?
[HTC One S] waza97:
This is about cm11 for desire x please we need help!!!!!!!

This is the link to our thread:

http://xdaforums.com/showthread.php?t=2437255

So far one dev has managed to get Bluetooth partially working, with 3g connectivity using the jb kernel. I was wondering whether you could help us fix our cynogenmod to get WiFi working plz plz help us we have been waiting for a working cyanogenmod for a year plz plz. Thank you.
[HTC One S] The Setlaz:
Are we getting Trebuchet back on next nightly ?! :D
[HTC One S] Brushstroke:
I don't think this has anything to do with the ROM, and it's not necessarily a bad thing but could be if I were to install a malicious app that required root. Superuser in the Settings menu is not prompting me to grant apps root access anymore. It's just allowing by default even though it is set to prompt. I did a clean flash of the 01/21 nightly and installed SuperSU to update the su binary using TWRP. SuperSU was prompted by CM's Superuser and I granted it, and it rebooted and updated su like normal. I then uninstalled SuperSU since I wanted to use CM's Superuser to manage root access. Now, things like the CM File Manager, AdAway, Titanium Backup, etc are just given root by default without prompt from Superuser. Why did this happen?
[HTC One S] Rapier:
theme launcher=themer, the launcher that uses "MyColorScreen" themes...so it's about that one not the CM Theme Engine from the ROM

Don't know how much help you can get here because the wifi is usually related to kernel and there are not so many kernel devs around. More than that, kernel development is very much in relation with a specific device and I don't know how similar they are...CPU, GPU and chipset are different for the two phones and so are the issues/bugs or kernel development
[HTC One S] nespresso33:
Reinstall Supersu, check if binary is installed, go in the settings of Supersu, select something like switch superuser app
[HTC One S] nicknc:
You're not the only one. I've started to have similar issues with wifi. In my case it's more akin to a timeout. Particularly overnight, the wifi will drop and will not reconnect (or scan) until after a reboot.

It started within the past week.

Still no reboots for me other than the occasional GPS + plugged in one. And because I know [MENTION=2101224]el_smurfo[/MENTION] loves it when people say it in this thread-- I'm on bubba kernel :laugh:, fwiw...
[HTC One S] el_smurfo:
No bubba. No WiFi disconnect. No GPS reboot. Enjoy your OC kernel and pants pocket wake mode ;)
[HTC One S] qazsxdcfv:
Anyone has try to update nightlies via CyanDelta ? :confused:

Sent from my Nokia 3310™
[HTC One S] jnne2012:
I do it everyday and no problems

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] mineIsAlreadyTaken:
I have one game that should be using push notifications, but I did not get a single one. I think that I also have seen a Waze push notification on my work phone while it never appeared on my One S. No greenify here, never had that. CM broken?
[HTC One S] djsubtronic:
I think it might not be Greenify after all. I have a feeling the default memory management settings are too aggressive, as I often see even applications running as background services (which should never be killed) getting killed when I still have >200 MB free RAM.

Any possibility of this being looked at? [MENTION=1815755]intervigil[/MENTION]
[HTC One S] el_smurfo:
Those of you missing notifications...how often do you reboot? I have had a small issue where I get the notification, but not always the sound...this usually happens after several hours of up time, so rebooting once or twice a day seems to help keep all notifications coming...perhaps it also resets the memory management state?

BTW, good article on ART. Spoiler: Mostly placebo right now...

http://www.androidpolice.com/2014/0...ery-life-benchmarks-not-good-but-not-too-bad/
[HTC One S] Michael1101:
I also read the article. Indeed good.

Just to add some fuel to the fire, I also tested ART for the last two days. It's the first time it worked for me. And I must say, I see no speed improvements and also, until now, no battery improvements (androidpolice shows nicely that there are only minor changes in battery life). BUT: I really see big difference in multitasking. I can easily switch between four, five apps without reloading (even some heavy apps like google plus or chrome). This was never the case with dalvik.

Maybe it's just me, or just placebo....:p

Edit: and every single app except xposed is working. But for now I disabled greenify
[HTC One S] djsubtronic:
Well, with missing notifications I do have to reboot at least twice a day. Which is not really acceptable. I used to go for weeks without rebooting on earlier builds, and not miss a single notification.

PS: I also switched to ART last night, there are definite improvements that I can notice in my day to day tasks.
[HTC One S] Brushstroke:
I haven't noticed anything with missing notifications. Also using ART and notice a definite change. Not so much in battery life but multitasking seems much faster.
[HTC One S] el_smurfo:
ART

Alright...you win. I'm running ART now and we'll see how well it works through the day.
[HTC One S] The Setlaz:
Commit was reverted... But it should get back soon. :)
[HTC One S] Brushstroke:
Be patient when you switch to it. The phone will take about ten minutes or so to boot up as it switches all of your apps to make them compatible.
[HTC One S] justaway2:
Why does Trebuchet matter? There's nothing in it that other free launchers like Apex/Nova can't do, and do better.
[HTC One S] jnne2012:
I have never understand the idea behind Trebuchet. Its too limited and boring!

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] elias.acab:
Im still running 1/13 built, I've been trying to update to new builts, but they just crash my phone, the last one I tried was 1/21, and it would still randomly reboot....is 1/22 more stable? or same thing? so far 1/13 has been the most stable one.
[HTC One S] el_smurfo:
No random reboots here for several days. I'm now running 1/22 with ART and it's pretty solid. I suspect you aren't flashing your boot.img properly per the OP.

BTW, new "fade" screen off is a nice change, compared to the tired TV off effect.
[HTC One S] qazsxdcfv:
Wow , am i the only one who can't run ART ? Im on 1/22 build :(

If i changing the system to ART it will give me an endless crash :eek:

Sent from my Nokia 3310™
[HTC One S] Brushstroke:
Endless crash? Describe please?
[HTC One S] el_smurfo:
Did you switch to ART, then hold down volume to boot to recovery and wipe caches first? Mine used to crash a bunch too, and wouldn't even get past the animation this time, until I tried that. Also, some older gapps weren't ART compatible, so maybe find an updated package to flash...I'm using Banks Gapps minimal package.
[HTC One S] Rapier:
Also make sure you're using the proper GAPPS package...not all support properly ART even if they're advertised to do so
[HTC One S] Inferi0r:
These are the exact issues we are facing with CM11 for HTC Incredible S since very recent. Three weeks ago no one has this problem and now quitte a few are affected but not everyone. I would say, CM problem?
[HTC One S] nicknc:
Yeah, but to expected due to the Wi-Fi changes around that time. It will be fixed.
[HTC One S] qazsxdcfv:
it even can't pass through the home screen :rolleyes:

No , i'm just change it to ART and then reboot ? :laugh: seems that my fault ?

I didn't know about this , im using the Gapps that OP directs to ( pagpps ) ParanoidAndroid one i think :D well if they're advertised but doesn't support ART that's a little bit b*llish*t :cool:
[HTC One S] djsubtronic:
Not sure if it's a 2.16/2.15 thing, but I'm running 20/01 unofficial 2.16 build unofficial and I just switched to ART and rebooted. No cache wiping or anything, and it rebooted pleasantly.
[HTC One S] derkleinebroicher:
If you use the Xposed framework, you must deactivate it, as they are not compatible.
[HTC One S] Rapier:
Xposed Installer switches automatically to Dalvik runtime at install time...no need to switch manually. It's a safety measure implemented by rovo in it

Sent from nowhere over the air...
[HTC One S] derkleinebroicher:
Right. And that means, he has to deactivate Xposed, as he wants to switch to ART.
[HTC One S] djsubtronic:
I'm not using it Xposed, I meant that I had no issues switching between Dalvik/ART, it rebooted and converted apps and was all sorted. No crashes or bootloops and no cache wiping was required, as some others have mentioned.
[HTC One S] derkleinebroicher:
Sorry . I guess, I completely misunderstood you.:D
[HTC One S] drkxyz:
Updated CM11 version for hboot 2.16 (20140123)

https://drive.google.com/file/d/0B0ajti88ZAFzRlVnNXhkV2djQkU/edit?usp=sharing

Btw: has anyone tested the CWM recovery which is compiled with CM11?

Actually it should also work for hboot 2.16, since the partition layout has been fixed by the cherry pick ...

Have fun
[HTC One S] qazsxdcfv:
Does the recovery mentioned on cm gerrit ? :eek:
[HTC One S] MrDuvet:
Hey,

I'm running 1/20 build and it seems to be pretty solid for me. No reboots, no wifi issues etc. But there is one issue I'm having since CM 9, still without solution. I'm heavily using WhatsApp and after a certain time in standby (sometimes just 1 minute, sometimes 30 mins) i don't get any notifications. Sometimes I even don't get them when using another app while whatsapp should be running in background. I checked wifi policy but it happens on wifi as well as on 3g. I'm indeed using greenify but not with Whatsapp. I'm also using OpenPDroid but Whatsapp's settings haven't been changed either. I tried every possible solution (reinstall, cache wipe, ...) but it didn't help. It's bloody anoying -.- Only worked on Stock but I don't wanna go back.

Max
[HTC One S] Brushstroke:
Yep. This is happening for me too on the 01/22 build. It usually happens after a few hours. I just won't receive any notifications, as well as sounds related to notifications, anymore unless I reboot. It happens with any app, not just Whatsapp.
[HTC One S] qazsxdcfv:
yeah , me too in this case its happens to me when using BBM and Whatsapp :D

also i think there's some Killer script in init.d :eek:

you know , RAM Optimizer or something that having a link between Applications
[HTC One S] MrDuvet:
I guess my other apps work properly but I am not sure since I don't get many notifications from them. WhatsApp is the main app and main issue. My problem seems to be independent of radio version or rom since it happens since cm9. Because I never had the issue of missing notifications when screen is on this might be related to cm11. The main issue of missing notifications when screen's of though seems to be universal. I don't really know where to put this report to ask for help, so I posted it here.
[HTC One S] elias.acab:
Just switched to ART, and every time I reboot the phone, it says Android is upgrading, and it takes a about 10 minutes. Is it worth it to wait that much time every time I reboot?
[HTC One S] el_smurfo:
Mine didn't take that long...really didn't seem much longer than Dalvik. I try to keep right around 150 apps total, and am still finding CM apps I want to remove with each flash to keep this delay low.

That being said, after a couple days with ART, I find minor differences in performance. Sure, it seems to allow more apps to stay in memory and apps may start up faster, but that's actually not all that great for me, as I don't necessarily want to save the state of an app I used an hour ago, resulting in more refreshes and button pushing. With CM eating notifications, having apps in memory or starting up faster really isn't doing us anything right now. I also had several GPS type hard crashes when using G+ Locations and have at least 3 spontaneous reboots while typing text. The tradeoff for me just isnt' there yet, and only momentum will keep me with it for a few more days until I have time to undo it.
[HTC One S] maluus:
I don't think the problems other than more apps kept in memory, are related to ART. I don't have any of the issues you mentioned there.

---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------

It's not normal if it does every reboot. Unless if you only reboot when flash a new rom with dalvik and cache wiped. I mean it does rebuild apps only when you wipe cache and dalvik but not every ordinary reboot. if it's not the case may be you should review the process and may be do a clean install.
[HTC One S] el_smurfo:
I didn't either...until I switch on ART the other day. I'm going to keep rolling with it and probably flash today's nightly, keeping ART enabled.
[HTC One S] Brushstroke:
I don't know if this is a ROM issue or not, I suspect not, but now when I use Google Play Music for a while (we'll say over 15 minutes), when I stop the music all other sound sources on the phone, such as ringtones, notification sounds, sound from playing video, etc are muted until I reboot. Anyone else experiencing this?
[HTC One S] Navik57:
I'm on 1/20, no special kernal, and I'm still getting reboots, especially while Ingress'ing.

Anyway, still trying to find the common factor for those of us with the inability to search for cell networks. We've ruled out CID, now my question is, have you changed your radio? Did you use that sense radio installer? (does anyone have a link to a good T-mobile radio I can flash in recovery to check? I haven't had much luck with stickies and searches, though I am still trying)
[HTC One S] el_smurfo:
You can get the radio out of the firmware.zip in any OTA update package. You can also get most of them from the sense radio installer. The one most of us have, from the JB RUU or JB FW flash is 1.13 and it's twitchy, but it works when it locks on.

http://xdaforums.com/showthread.php?t=1998270
[HTC One S] Navik57:
Thank you! I'm going to try to flash it in recovery. Just trying to grasp at straws to figure out what could be causing this network thing. Also, are you still stable?

I'm guessing since you used the sense installer, and are not seeing the network issue, it doesn't have to do with the radio. Back to brainstorming....
[HTC One S] el_smurfo:
I didn't use the Sense Installer. It doesn't work for S-ON. I flashed a firmware.zip file in fastboot which contained all the JB firmware including radio.

I don't have the network issue on TMOUS...it has to be some sort of APN problem...can you borrow a SIM from a different provider and see if it connects?

My phone is mostly stable, though one side effect of ART appears to be a completely full internal storage due to the larger precompiled cache files. Had to move some larger apps to SD to get a new one to install at all.
[HTC One S] provaleriy:
Im on 23 Jan build and I have a one issue with WiFi. Im always left my phone with enabled WiFi for night. And in the morning phone can't connect to AP although he seem this AP.

Someone has this issue?
[HTC One S] blinksilver:
I've had this issue for a while, a few other have as well. I've noticed that some APs are worse then others and that security plays a role in the problem
[HTC One S] Dragn4rce:
What did you guys do to fix WiFi O.o

I flashed Bubba and that didn't work.

Edit: also having issues keeping a connection to T-Mobile's internet. On my Nexus 5 I keep it steady at LTE. On this device it's everywhere going to H to 3G to H+ to reconnecting.

Sent from my Ñ£×Ú$ 5
[HTC One S] provaleriy:
Same issue. I'm from Russia.
[HTC One S] nicknc:
Search this thread for the build.prop edit I posted a month or two ago. Fixes the data drop issue. It will still cycle data between 3g and h+, but speeds don't actually go to 3g.

Wi-Fi issues are mainly since CM moved Wi-Fi into the kernel. Will be fixed eventually.
[HTC One S] speedfreak007:
Rom runs great and smooth, but I'm having battery life issues. I can't seem to get through the day (2 hours of screen time) with wifi and 3g enabled all the time. I have no wakelocks. How much screen on time are you guys having with 3g and wifi on?
[HTC One S] morris178:
I have noticed the same thing. I barely get 2 hours of screen time. I used to get around 3 before with black bean (android 4.2.2 ).I set the curve for brightness automation to the lowest preset. Standby time seems to be largely unaffected, but when the screen is on you can basically see the percentages drop. I haven't flashed any custom kernel or radio. I'm on the 1/24/2014 Nightly (hboot 2.15).
[HTC One S] nicknc:
Well, I have 90 minutes of screen on and 68%, that's about 60 minutes of Netflix streaming with speaker at max.

I do get bad battery life sometimes, but it's typically due to power manager service wake lock after taking phone off the charger.

It really sounds like a bad flash or install for you guys if you have no wakelocks (confirmed through betterbatterystats or equivalent, right?).

Try data backup, full wipe and reinstall. Auto brightness will cause lots of battery drain. Use another app or the status bar slide in cm.
[HTC One S] speedfreak007:
The auto brightness is indeed not very good, but I manually lowered the levels.

Which auto brightness app do you suggest?

My screen on time varies a lot, depending on the usage, but leaving wifi and 3g on causes a constant drain and prevents me from using it a full day (i work long days though).

I checked wakelocks using wackelock detector
[HTC One S] nicknc:
Use BBS for wakelocks, it's a lot more granular than a "detector", and also check to make sure your phone is actually entering deep sleep.

Lux is popular for brightness, and try rebooting your phone after pulling it off the charger. That power manager wake lock is fairly common, and a reboot is all that fixes it.