yashsingh1/xdaforums huggingface dataset:
[HTC One S] el_smurfo:
Both Flashify and FlashImageGUI worked well for me, after the settings file was deleted. Had another freeze this morning, but was away from the computer, so tried an app called Syslog to capture the dmesg file Ethan needs...hopefully it helps, as it was a slightly weird freeze...phone was already unlocked and stable when I pulled down the status bar and it only hung for a few seconds before the phone blanked and went back to the lockscreen.
[HTC One S] Cofreddi:
I did clean install full data wipe and cache latest nightly (11-20140430) it did that with 28 as well.

It has been doing it all day today and yesterday.

Im not sure what was the last kernel i flashed ill have to check and get back to you on that...

Edit: kernel version - 3.4.82-ge96774

build03@cyanogenmod#1
[HTC One S] nicknc:
Yeah, I just got one too. Very similar, how odd.

You pull the last kernel log, then?
[HTC One S] el_smurfo:
Syslog supposedly gets logcat, dmesg, last_kmsg and a radio log. The dmesg doesn't look too weird to my untrained eye, but the logcat shows the same out of memory system crash that was in the last log I sent to him, so we'll have to wait for the expert analysis.

---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------

Can you answer by swiping where the answer indication "should" be? Perhaps related to the BSOD we are all experiencing. Is your proximity sensor working right when you call out...maybe totally blocked?
[HTC One S] warzag:
Guys can I flash the latest nightly with my hboot 2.16 or have I to use the special builds ?
[HTC One S] nicknc:
Have to use hboot 2.16 build in the other thread. Make sure to update your recovery, though, to 2.7.0.8, going forward.

---------- Post added at 12:21 PM ---------- Previous post was at 11:59 AM ----------

Alright, I sent a log to [MENTION=1815755]intervigil[/MENTION] as well. I reckon he can figure it out.
[HTC One S] intervigil:
Are any of you guys reporting UI lockups using any specific themes?
[HTC One S] nicknc:
Just stock CM theme for me.
[HTC One S] el_smurfo:
I do use Thyrus Holo No Apps theme (one-off theme he made and posted in his G+ community). It dark themes only the UI elements, settings, notification, quick settings. It was built for the old theme engine. I also use Nova Launcher Prime, if that matters.
[HTC One S] nicknc:
I'm using the Google launcher, with notification bar lightness control enabled (the only notification bar custom setting I have enabled)
[HTC One S] intervigil:
Themes seems to have been a red herring. Right now all the logs I've received point to out of memory events causing the lockups. The OOM killer goes on a rampage killing lots of things, it seems like that results in a lockup when you hit the notification bar because some of those things have pending notifications and systemUI can't handle it when apps are forcefully killed mid-notification. Need to get to the bottom of what is causing the out of memory events. If you can recover please try adb shell echo 'm' > /proc/sysrq-trigger and adb shell cat /proc/meminfo, perhaps there will be some information still there before the OOM killer got to things.
[HTC One S] el_smurfo:
if you guys are away from a computer when your device locks up (as I usually am), you can use this app

https://play.google.com/store/apps/details?id=sites.mjwhitta.scripter

with this script (make sure you check the "run as root" checkbox):

#!/system/bin/sh
echo 'm' > /proc/sysrq-trigger
cat /proc/meminfo > /storage/sdcard0/meminfo.txt
[HTC One S] nicknc:
Good call
[HTC One S] el_smurfo:
Not just whine and cheese out here in lala land ;)
[HTC One S] nicknc:
You're from LA to boot?!
[HTC One S] el_smurfo:
No, but the loony ideas of LA and SF have a long reach
[HTC One S] djsubtronic:
This does not work.
[HTC One S] Darknites:
Hmm works on BeanStalk and would of thought its the same here. Guess you just have to use some app for it.
[HTC One S] alexgreat:
Only front camera works.. (

Hi, guys!

Just installed CM11 and got one big problem: only front camera works... Cannot switch to back camera.... Is there any ways to solve this problem?
[HTC One S] usaff22:
Works fine here
[HTC One S] er_fran:
Power and Vol - doesn't work... =(
[HTC One S] guandalfthegrey:
Hold them some seconds ;)

Inviato dal mio One S utilizzando Tapatalk

---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------

I have the same issue but it's not so bad.

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] Darknites:
Ya I should of said to hold it for about 2 seconds.
[HTC One S] el_smurfo:
It's hard to hit...takes me a couple tries, but it works. Maybe it carried over somehow from a dirty flash? I also have the option on the power menu, but those settings haven't been committed to CM11 yet, so if you don't have them, you can't enable them easily.
[HTC One S] djsubtronic:
Tried it repeatedly. Just the volume bar comes up and goes all the way down. And there's no way to enable it in the power menu, so it definitely looks like a Beanstalk specific thing or data carried over from a dirty flash.
[HTC One S] usaff22:
Clean flash here, running CM11 on HBOOT 2.16. Works fine lol

Not in power menu though
[HTC One S] melo563:
Screenshot works for me on a clean install
[HTC One S] Darknites:
Maybe try hitting power first then vol-.
[HTC One S] el_smurfo:
Yeah...pretty sure that mechanism as an AOSP thing, so you're probably just a bit spastic with the buttons
[HTC One S] djsubtronic:
That's exactly what I'm doing. The volume just goes down as normal. Lol this is too much hassle. I have no urgent screenshots to take anyway, so I will just wait until it comes back to the power menu. :)
[HTC One S] usaff22:
Screenshots to put in the OP/ screenshots section:
[HTC One S] Darknites:
Em what?

Got no ideas then, its working for others and even works on Sense roms.

---------- Post added at 05:12 PM ---------- Previous post was at 05:09 PM ----------

Got to love how Tapatalk pictures look different sizes even tho they all the same size.
[HTC One S] usaff22:
Just realized what you meant now that I'm on the browser not Tapatalk. What a fail lol

Edit: Edited
[HTC One S] aegentirony:
If on 2.15 can i still use the og cwm that was needed to flash originally? or do i have to go back to twrp?
[HTC One S] el_smurfo:
I used CWR after he added the older recovery compatibility commit and it worked fine. TWRP is sooooo much better though...Just get goomanager from the Play Store and it will flash it for you.
[HTC One S] ApneaB:
Wait - I am JUST about to install CM11, using TWRP2.3.3.0. Is that ok? This is my go-to recovery!
[HTC One S] nicknc:
Lmao, we say the same about Raleigh here....

Having a hard time triggering any freezes now.
[HTC One S] intervigil:
Added two lowmemkiller patches, try tonight's nightly, see if it makes a difference.
[HTC One S] nicknc:
Flashed 01May nightly. No freezes yet. They usually occur for me around 11am and 7 pm, though, so we will see.
[HTC One S] el_smurfo:
I think he meant 0502...the patches went in right around the time 0501 was building.
[HTC One S] nicknc:
Yeah, I didn't see anything in the changelog about those patches. BUT, the placebo effect seems to be working well. Performance is great and no freezes yet!
[HTC One S] el_smurfo:
Can you also feel the 15 RWHP in your butt dyno? Looks like this is the stuff...codeaurora patches.

http://review.cyanogenmod.org/#/c/63206/

http://review.cyanogenmod.org/#/c/63205/
[HTC One S] nicknc:
Seriously, 01 May is running the best I have had in weeks (and 27/28 were both pretty good despite the freezes).

For those using CyanDelta with a custom kernel, be careful flashing this one. The phone actually black screened

in TWRP

on me after I had CyanDelta reboot with the auto-install. I couldn't wake it back up (was halfway through the CM installation portion) and had to power it down and run it again.

First time I've run CyanDelta in nearly two months, geez.
[HTC One S] melo563:
Where can I find the apk file at do you know?
[HTC One S] de.dari:
Hi all.

My wife has a one S but the buttons no longer work. Will I be able to enable on screen buttons for this rom ?

Much appreciated.
[HTC One S] el_smurfo:
Mine are in data/app

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

Maybe with exposed?
[HTC One S] melo563:
Never mind I did something smart real quick and went to the play store where I downloaded it and uninstalled it now everything is good wtf
[HTC One S] benyto:
I, too, had to delete the /sdcard/TWRP/.twrps file before TWRP 2.7.0.8 would get past the flashing logo. Despite what the "Troubleshooting" section at http://wiki.cyanogenmod.org/w/HTC_fstab_updates said, I didn't have to reboot in to Android to remove the file. While the TWRP logo was flashing I just ran "adb shell" from my laptop and executed "rm /sdcard/TWRP/.twrps". TWRP almost immediately finished loading at that point without any need to reboot in to recovery again.
[HTC One S] nicknc:
With Xposed Framework enabled there a couple of different avenues for that, ranging from soft buttons to gestures.
[HTC One S] el_smurfo:
Darn... Looks like tonight's nightly is busted

http://jenkins.cyanogenmod.com/job/android/?
[HTC One S] nicknc:
Good tip. Probably easiest to just delete the file before flashing the recovery, honestly. A lot of folks (like me) are on Windows 8 with the flaky adb and non-existent fastboot (excepting the Intel USB 3.0 workaround, of course)

I still cannot figure out why I can fastboot my daughter's Kindle Fire on Win8, though. Works flawlessly.
[HTC One S] benyto:
Yes, and had I remembered I would have done so. :o It wasn't until I flashed the recovery did I realize I hadn't yet deleted the file.

Sorry to hear that. Fortunately I have no such issues on Linux. I don't need any more obstacles in my way in trying to keep my phone running. :p
[HTC One S] nicknc:
Lol, I would consider Linux the obstacle!
[HTC One S] el_smurfo:
0502 is up

let's hope the BSOD is history...don't forget to update your recovery if you haven't yet.
[HTC One S] deniz2694:
Linux is freedom, it cannot be an obstacle to anything ;)
[HTC One S] nicknc:
... Except getting work done without having to resort to workarounds and the terminal and ignoring buggy gui's

I tried for two years....

---------- Post added at 12:03 PM ---------- Previous post was at 12:00 PM ----------

Just got a bsod on 01 May. Same as before, between 11-12 pm.

Managed to recover, but the script either didn't work or had no output.

Sent kernel log immediately to [MENTION=1815755]intervigil[/MENTION]
[HTC One S] el_smurfo:
I also used Linux for 5 years or so...once Win7 came along, I reclaimed the hours per week I spend trying to get drivers and other workarounds running. My friend still runs a mythtv box, and every week he has some story of the hurdles he has to jump through just to get netflix running.

Sorry about the script. Are you sure you enabled root (it seems to uncheck every time you edit the script). I just tried again and it dumped a meminfo.txt in the root of my sdcard. I have been deleting them each time, as it may not be able to create one if the filename already exists. Regardless, 0501 doesn't have the lowmem fixes, and the last one I sent to Ethan (total black screen requiring hard reboot) was the same exact issue. Lets test out 0502 and see if the problem is still there...
[HTC One S] nicknc:
Not your fault-- it actually did work. I am just an idiot and looked at the wrong file.

Flashed 02 May alongside 01 May IceCode. Did a dirty flash, but we'll see how it plays out.
[HTC One S] el_smurfo:
Pretty sure the lowmemorykiller stuff is in the 8960 kernel, so you're still not testing the right thing...come on and slum it with us in CM kernel land...what's a few extra hours of battery life anyways? If you like your phone waking up in your pocket all the time, just reach in a press the power button every couple minutes.
[HTC One S] nicknc:
Lol, I disable all that s2w stuff-- buggy on this phone. What is useful, however is the forced-fast charging, the undervolting (I have a"fast" Krait) and the extra governors and i/o schedulers.

As for testing, someone has to run a control, right? I assume you'll be sticking with stock, and 01 May IceCode was synced yesterday with CM source, so it should be a pretty good benchmark to see if this is the fix.
[HTC One S] nicknc:
Well, got a monster freeze this afternoon that was unrecoverable.

Did NOT happen with notification bar use, though. I had navigation going in the background, charging, streaming radio via bluetooth and was taking my turn in Landrule (a risk clone). Screen started flashing like crazy, crashed to home screen and then froze. Took about a minute to power down and reboot, but it burned up 15% of my battery in the meantime.

So, either the 01 May IceCode kernel does not contain the fixes or there is something else going on.

[MENTION=2101224]el_smurfo[/MENTION] and the rest of you, I'll wait to hear your feedback from the stock kernel.
[HTC One S] benyto:
I haven't yet updated to 20140502. I've been running 20140501 since yesterday. Yesterday I got some freezes that required me to reboot the phone, but today it has been fine through heavy use. Go figure.
[HTC One S] nicknc:
Screen on lag is also back for me intermittently.
[HTC One S] dr3amsINdigital:
If it's any indication on the issue, I was on 4/30 nightly and would sometimes get freezes (sometimes needing a reboot) after trying to pull down the notification shade right after an app finished installing.
[HTC One S] el_smurfo:
No freezes yet for me today. They can come in waves, so I'd give it another 24 hours before calling it solved.
[HTC One S] nicknc:
LOL!

Has anyone else encountered this issue?
[HTC One S] el_smurfo:
Sadly, i have... Just now, running 5/2
[HTC One S] nicknc:
Man, I am having all kinds of problems.

The phone is charging incredibly slow, the battery drops 3-5% within a minute or two, and I'm having a lot of network issues. All was fine today (actually was running fantastic) until that freeze.

It's been absolutely crap since that freeze.

I am going to clean flash and revert back to 01 May for now.
[HTC One S] el_smurfo:
Mines been getting hot off and on for a week or more. I just noticed there was an experimental build an hour after the official, so I'm running that now, though there's no change log.
[HTC One S] intervigil:
Are there any people _NOT_ experiencing any lock ups?

I am not (and have never), for the record.
[HTC One S] drkxyz:
No lockups at all on my side. I'm on hboot 2.16, compiled yesterday (May, 2nd) and had one reboot last night.

No problems otherwise.
[HTC One S] mikronac.ns:
What you mean with that?
[HTC One S] noomarsil:
Is front camera running OK on last Nightly?
[HTC One S] Microphone:
Since which nightly do we need the new recovery?

...aaah, I see that it is compatible with all older nightlys as well, right?

Gesendet von meinem Nexus 7 mit Tapatalk
[HTC One S] :
Everything's fine for me, too! I'm on the m5 build.
[HTC One S] nicknc:
They've only cropped up over the last week or so.
[HTC One S] cyxareg:
Hm,can't update to 01-02/05 nightlies from 24/04, it throw out from cm updater,and write Failed through recovery.anybody else with this problem?
[HTC One S] nicknc:
Did you update your recovery as is required for 01 May and going forward?
[HTC One S] cyxareg:
Nope,any link pls?
[HTC One S] nicknc:
Read back a few pages. It's there, along with instructions
[HTC One S] Rapier:
http://wiki.cyanogenmod.org/w/HTC_fstab_updates

read here
[HTC One S] sinlimites:
Any mirror for TWRP 2.7.08?
[HTC One S] intervigil:
I'm trying to find out if there's any differences between those who are experiencing lock ups against those who aren't, since I can't reproduce the issue at all.
[HTC One S] nicknc:
Got it.

I only mentioned that as it seems like a lot of folks have been holding back from the nightlies of the last few weeks, and thus have not experienced this particular issue.

I'm back on 01 May for now, waiting for a few more freezes to see if I can send you some more logs.
[HTC One S] Albino_Mexican:
I am running my own build of 05/01 without any mods. Flawless so far.
[HTC One S] nicknc:
Yeah, it's pretty isolated.

Only affects me around 11am-noon and around 7pm at night.

Very strange.
[HTC One S] intervigil:
More experimental builds tagged OOM_TEST, they have this patchset: http://review.cyanogenmod.org/#/c/63034/
[HTC One S] melo563:
I have been running may 1 build with no problems smooth and good battery life so far.
[HTC One S] nicknc:
I'm running a clean install of may 1 with no kernels, completely stock. Bad battery life and bad performance.

No freezes yet today, but I rashly wasn't on my phone between 11 and 12, Lol, so that makes sense.
[HTC One S] Cofreddi:
I tried that and it didnt work... had to reflash from scratch... was fine for few days and today it started again. dont know what to do with it.

I think to relash RUU and go back form there after i install OTA and then unlock bootloader
[HTC One S] warzag:
Hey guys, just installed the may 3 build and i can't launch my camera app (app chain crash). Any idea ?
[HTC One S] el_smurfo:
Not sure... Ran 5/3 and 5/3 experimental and 3 camera apps work for me
[HTC One S] nicknc:
Did you dirty flash?

---------- Post added at 10:59 PM ---------- Previous post was at 10:59 PM ----------

Clean flash and installed.

Battery life seems to have stabilized versus 01May
[HTC One S] Rapier:
Do I miss something? The OOM-TEST versions do not contain the new Theme Engine? Or they got the Theme Engine but not the frontend?

I flashed the latest cm-11-20140503-EXPERIMENTAL-OOM_TEST-ville.zip and themes look as before. Also I've installed from Play Store a theme designed for the new Theme Engine (Thyrus's DarkUI) and it's not showing up at all in Themes. On his G+ page he said that

Should I install the normal nightly to get that?

Edit: [MENTION=3921603]phoenixita[/MENTION]: I can confirm that BT patch was merged and working on latest nightly. Thank you again, well done :thumbup:
[HTC One S] warzag:
I did wipe all and i think i did a mistake when i've erased my sd.

I did it again and my camera app is working now.

I still have a snapchat issue. The front camera is working in the camera app but not in snapchat :crying: any idea ?
[HTC One S] el_smurfo:
I don't think the new theme GUI has been committed yet. I follow Thyrus and the CM theme community and have never been able to get his new theme running. In fact, he posted a zip just today with the settings.apk to enable the new theme engine on a Nexus 4, so I'm guessing you can try to get ahold of that and test it.
[HTC One S] nicknc:
Glad to hear it.

Nope, I don't send nudie pictures of myself to other people, so no clue. Have you contacted Snapchat? Sounds like an app incompatibility on their end.
[HTC One S] warzag:
This issue seems to affect only cm users since 10.2 it s realy weird.
[HTC One S] el_smurfo:
Well, I'm posting this from the bathroom, so my wife for one should be happy its busted.
[HTC One S] Rapier:
Yes, I saw it and talked with him about it. Unfortunately the theme frontend requires a different Settings.apk as well and his ZIP is for Nexus devices for the moment. We'll have to wait until CM commits are included in our nightlies
[HTC One S] cyxareg:
running 02/05 dirty flash, with art, lot smoother than nightlies before may and good battery life, got 1 monster freeze related to status bar until reboot system today morning
[HTC One S] nicknc:
You try with 03 May oom experimental build?

I've been running a clean flash of it since last night, stock kernel. No freezes yet.
[HTC One S] nespresso33:
What are these oom experimental build ?
[HTC One S] Rapier:
Read back what intervigil posted. There are test builds because there were some lockups
[HTC One S] phoenixita:
Thanks mate. Finally the bluetooth patch i submitted is merged in the code :)
[HTC One S] cyxareg:
is this the same base as nightlies with same options?cause i like stability of nightlies exept freezes
[HTC One S] larrycl:
USB problems w/ TWRP 2.7.0.8?

Anyone else having problems with usb & the unofficial TWRP 2.7.0.8? While in recovery, 'adb devices' never sees the phone. I also tried mounting USB storage within TWRP, and the computer never sees that either.

These things worked fine when I was running official TWRP 2.6.0.0.
[HTC One S] nicknc:
Seems to be. Runs pretty good for me.

[MENTION=1815755]intervigil[/MENTION], no freezes for 24 hours on 03 experimental with two hours screen on time. Runs well, battery is good too.
[HTC One S] el_smurfo:
Me too, though haven't had a lockup in a couple days of nightlies
[HTC One S] nicknc:
Great to hear. Perhaps it's fixed.
[HTC One S] el_smurfo:
Jinx... Just got a very brief system ui crash using snap camera... Recovered quickly to lock screen... Acceptable, but shows there's room for improvement. Ethan commented on previous log, thinking themes still might be relevant, and I'm now using new theme chooser GUI, so it might make sense.
[HTC One S] nicknc:
Yeah, but I am not, and have never used any custom themes.
[HTC One S] el_smurfo:
You will be, soon

https://plus.google.com/117962666888533781522/posts/PWopua4y2kN
[HTC One S] dr3amsINdigital:
Interesting read about the future of CM11. Basically, there will be no 'stable' or 'RC' builds; only 'M' builds every 2 - 4 weeks. Hopefully we'll get a good M6 build for ville.

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
[HTC One S] el_smurfo:
M builds always seem like regressions for this device... I'm happy(ish) with nightlies
[HTC One S] provaleriy:
Can I dirty flash M6 build over M5?
[HTC One S] el_smurfo:
Should be fine. Backup first. Wouldn't flash over current nightly though.
[HTC One S] Rapier:
[MENTION=2101224]el_smurfo[/MENTION]: Thanks for that link, it worked for me too. With the new M6 it seems CM team got the Theme Engine frontend publicly. Have you flashed it? I played all night with the latest nightly and latest rmbq kernel for CM11 and it's working great. Still the themes are not completed yet, I've noticed that dialer was not themed for me using the test Thyrus theme
[HTC One S] vanwoudt:
I get E:Error executing updater binary in zip since 05/01. I'm running 04/30 and TWRP 2.6.3.0. I also tried PhilZ Touch Recovery and TWRP 2.7.0.0, same error. Tried to replace updater-binary from previous cm version (03/24) and from PhilZ, same error. Anybody with the same issue? Suggestions?
[HTC One S] Rapier:
Have you tried to read the tread instead of replacing the updater-binary? It would have been much easier...

Due to new CM commits, starting with nightly 1/05 you MUST use a different recovery that supports these. It was stated initially by intervigil and also posted several times already in the last pages of this thread.

You can find the CM article related to this change HERE (also link for download a compatible recovery)

NOTE: This recovery will be needed also for any ROM that is build on CM tree and incorporates those commits
[HTC One S] Darknites:
An update to the op might help too.
[HTC One S] nicknc:
You are absolutely right.
[HTC One S] Darknites:
Of course I'm right I'm always right [emoji12].
[HTC One S] el_smurfo:
I'm sticking with the 5/3 experimental. Only one minor crash with fl recovery.

I am using the theme GUI flash that Thyrus published, selecting the style from the basic no apps theme and the font from the darkui theme. I'm really only interested in replacing kitkat grey elements with black, not theming apps or other white elements like the dialer. (BTW, thyrus also builds a black version of the cm dialer and posts it on xda somewhere.)
[HTC One S] Rapier:
I got his full theme, he posted a link on his beta community and I'll use that one since I want black apps and dialer

Sent from nowhere over the air...
[HTC One S] vanwoudt:
Probably not thoroughly enough :S Thanks for the help!
[HTC One S] nicknc:
+1 to that. No crashes here yet. Having some Bluetooth issues, but mostly manageable. Sticking with 03 until [MENTION=1815755]intervigil[/MENTION] merges those fixes, I guess.