yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I've tried it with and without Xposed Framework, with Slim AIO gapps and with PA stock gapps, never with any exchange account, with 2.14 and 2.15 firmware, with stock kernel and Torched kernel (which seemed to fix it for me, but we might taking about a different variation of the bug).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] FarSight87:
Tlazarus,

I tried 12th, 16th and 20th April nightlies with and without xposed, it didn't seem to make a difference. Using the stock gapps and no exchange on any. Before this I was on 30th march nightly with xposed modules and stock gapps with no freezing/unresponsiveness.

After giving up on nightlies I have switched to the M5 snapshot with a clean slate. No xposed installed yet. Stock kernel. Been running smooth as butter for nearly 5 days or so. Problem has not occurred once yet.

I hope these results may be of help to you.
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Hi

xposed - yes

gapps particular - no

exchange - yes

I am going back to prior to the snapshot until something gets isolated. i will post if i get the same issues again
[AT&T, Rogers HTC One X, Telstra One XL] clone22:
friends, try with what I put in previous post, about to turn up the minimum CPU frequency 486MHZ, I did and took 3 days with the last upgrade of the rom Paranoid, which is also based on CM, and also had these bugs, and I have not had so far:good::good::laugh:
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Everyone using the stock launcher as well?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Apex Launcher here.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Oh well. Sounds like there isn't really anything common that links all of us. So much for the easy solution.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Unfortunately not. I'm trying to bump my minimum CPU frequency up a bit on the latest Carbon build to see if it'll help or not.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I bumped mine to 486 minimum using PA 4.3b1 + Torched 4.0 and I haven't had any issues yet, but I usually only do overnight.

Clone22 is on to something, even if it's just the first step.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
This is also an interesting read...

http://xdaforums.com/nexus-s/general/rom-official-cm11-m-snapshots-nigthlies-t2557506/page62

Seems to suggest that (1) the problem is affecting other devices, and (2) that it may be related to the new theme engine. There is also a suggestion that disabling the "Block Gesture Touch Event" option in Developer Options helped for at least one person.
[AT&T, Rogers HTC One X, Telstra One XL] chrisb906:
I am wondering if this is my same issue..the sod
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Is it just me? I can't seem to find that option in Developer Options. By the way, bumping my minimum CPU frequency up didn't work for me on Carbon.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I just got up and for the first time in a while my phone was on and working well when I woke up, so at least on PA, increasing your minimum to 486 seems to work.

Make sure you go into Trickster, set your minimum, and also check your Governor settings for other times the minimum comes into use. For example, the SmartMax gov has an ideal suspend frequency, be sure to change that to 486 as well.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Bumping the frequency didn't fix the problem for me, only a few hours after a clean flash the phone became unresponsive. And I was unable to find the mentioned setting in Developer Options. You might be good for now, but I've gone a couple of days without this problem rearing its head.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
It should be under "INPUT" in Developer Options. I see it in the April 29th nightly as well as the M5 release - could it be missing from Carbon? Also, I don't appear to have the issue with M5.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I'm seeing it in PA4.3b1, I just switched it on.

Timmaaa, you were right, I listened to Google Play Music on my walk over to the office this morning, the phone seamlessly switched from wifi to hspa+ without missing a beat, it switched on to the correct one of the two wifi networks at work, and I got into my office (I mention all of that because usually one of those steps causes an issue every now and then). Well, I sat here for 2 minutes, went to check this setting after catching up on XDA, and lo and behold, my phone is off/SOD'd.

Sooooo, I'm going to reboot, fix permissions, clear my caches, make sure the settings stuck, and see how the 'Block gesture touch events' method works, while setting my CPU min back to normal (isolating variables!).
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
As far as I can tell the option just doesn't exist on Carbon. I've gone back to a mid January build of Vanir now, from memory it's the last stable KitKat ROM (that I like) that I had run.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
That didn't last long. That option in Developer settings didn't help at all, and setting my CPU min back to 384 seems to have made the reboots come on quicker.

Unfortunately I have no freaking clue what is causing the issue, and because 1) it's tough to get h8rift or any of the other CM devs in here to help anyone and 2) our phone is old and apparently not worth the time in upkeep, I'm worried that the CM codebase is moving past whatever caused the issue between the M5 release and now and only solidifying it as a part of the system.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I agree - I had no desire to replace this phone (and still don't really), but this may be the final kicker. I am probably going to go for a play edition or "Android Silver" phone as it is clear that no one is officially supporting phones other than those. I greatly appreciate all of the time the devs put into our phones, but once they get a new phone the old phones just drop off the radar. I really wish there was a team of devs per phone, and as devs moved on someone was able to step in and take over. Multiple phones per dev just doesn't work that well.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Unfortunately this is a "legacy" device now, which in terms of its age might seem right, but in terms of its capabilities couldn't be more wrong. This phone can handle pretty much anything that's thrown at it.

It is sad that as devs get new devices they leave the others behind, but we need to remember that XDA doesn't exist for us, it exists for the developer. People are all too often mistaken in thinking that we're entitled to have work developed for us, that XDA is a fast-food like store from which we can order, and pick and choose what we want. It isn't. XDA is about developers doing what they love, for their own reasons and amusement, and then we're just lucky enough that they share this work with us. In reality, we're not entitled to anything. If we really want development to continue for this device it's up to us to take the initiative to learn how to build Android and pump it out.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
While I agree with you, and it is of course the natural progression of things on XDA and in Android development in general, the fact remains that CM is actively updating the evita device tree (as recently as yesterday!) and is still producing nightlies for this device, so I would hope that even if they aren't responding, the CM folks are aware of these issues and looking into them.
[AT&T, Rogers HTC One X, Telstra One XL] intervigil:
Are you and any of the others reporting UI lockups using themes?
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I am not personally.

Also, thanks for stopping in intervigil! In response to what you said to me a little bit ago, I'll post this here for everyone.

If you are having these shutdown/sleep-of-death/random-reboot issues, please do the following and post it here or on pastebin with a link to it here!

As soon as it happens to me again I'll be sure to post with the logs.
[AT&T, Rogers HTC One X, Telstra One XL] intervigil:
Ignore themes. On ville it seems to be related to memory pressure. The out of memory killer is going on a rampage and killing lots of processes. Please try running adb shell echo 'm' > /proc/sysrq-trigger and adb shell cat /proc/meminfo if you manage to recover without a reboot.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
This is exactly what I am seeing... Logs are littered with memory pressure warnings and then every process is killed. I posted a log zip a few pages back but will upload another when I am back in front of a computer. I'll also try running what you asked for once I switch back to a newer nightly. M5 doesn't seem to have the same problem.
[AT&T, Rogers HTC One X, Telstra One XL] dustinhayes93:
I believe h8 said everyone should reupgrade.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
He did in the main 10.2 thread.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
My mistake.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] PaKMaN787:
I wasn't aware of that either, but my ROM was working fine. I guess it doesn't matter now, because my phone just got bricked a couple minutes ago (QHSUSB_DLOAD). I'm going to assume this had nothing to do with it, but I'm confused since it just happened randomly. I wasn't charging or flashing anything.
[AT&T, Rogers HTC One X, Telstra One XL] kewlguru:
Wow! The last two pages seems to be with people reporting bricked devices. Very similar experiences like mine.

I am sure there are a lot of people without any issues on this ROM. The unlucky few i guess.

I am going to try the unbricking method and will update either way.

Wish me luck guys.
[AT&T, Rogers HTC One X, Telstra One XL] PUfelix85:
Just out of curiosity, did any of you with bricked devices try to make the phone faster by messing with the performance options?
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
Nope.
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Which version of TWRP should be we using then? I'm still on 2.5.0.0 or something like that with old firmware. I tried a newer version which was listed in the TWRP changenotes as being suitable for the new TP firmware but touch wasn't working so I rolled back.

I'll only put the newer TP firmware back on if the devs say its needed for 10.2, otherwise will leave it as is for now (still running 10.1).
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I've been running TWRP 2.6 for a while now and it's been perfect.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] PaKMaN787:
Yeah no problems with 2.6, and I doubt bricks have anything to do with it.

On another note these were the exact conditions when I bricked:

S-OFF

Unlocked Bootloader

SuperCID

Not connected to USB/Charger

No change in performance settings OR developer settings (though that probably wouldn't do anything)

Overall, a completely random brick. I leave my phone in my room for an hour, go back and it's bricked (QHSUSB_DLOAD). Pretty unexpected considering I've never had a brick on Android before, but this is an (pre-)alpha ROM and we have to remember that. We're all given fair warnings.

---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------

@kewlguru I'm guessing you're going to try the Unbricking Evita thread method, no? That seems to be the most likely to work, and please update. Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Put upgraded TP and TWRP2.6 on without issue in preparation for 10.2 :)
[AT&T, Rogers HTC One X, Telstra One XL] kewlguru:
That was a complete bust for me.

I was not able to enumerate the partitions of the phone when connected to the computer.

Since I am unable to do that, no way can I proceed into the next step.

I am thinking of sending it to http://mobiletechvideos.mybigcommerce.com/htc-one-x-jtag-brick-repair/

Would it work?

thanks
[AT&T, Rogers HTC One X, Telstra One XL] PaKMaN787:
I guess we're desperate

I think this is a good final option. I also wouldn't be surprised if at least a few reviews were fake, but they seem quite reliable and the price is fair. I'll think about doing and if I end up doing it before anyone else, I'll let you guys know how it goes. Thanks for the link.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Also, a developer on here named Zarboz does jtag repairs. Message him for details.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
I hard bricked earlier this year & sent it to them, they're the real deal. :thumbup:
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
My experience was the same as yours except for the fact that my phone was on the charger. It was the original OEM charger that came with the phone. Other than that, I had the same steps as you.

I tried all the unbrick threads and none of them worked. I couldn't enumerate partitions. My replacement will be here today and I'll be back to 10.2! LOL
[AT&T, Rogers HTC One X, Telstra One XL] kewlguru:
I am guessing that the reason the unbricking isn't working is due to the fact that we get to 10.2 from the latest firmware which it doesn't support.

Well ordered the JTAG service. Let's see how that goes

---------- Post added at 08:09 AM ---------- Previous post was at 08:07 AM ----------

Did any of you who bricked used the Navigation before it did and see any slowdowns before konking out?

Just curious
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
No, I hadn't used anything. It was in my pocket most of the day and then I plugged it in. After that, toast.
[AT&T, Rogers HTC One X, Telstra One XL] PaKMaN787:
DId you send it to HTC, buy a new one, JTAG repair? I'm thinking of going with the latter option soon.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Warranty replacement through AT&T. They won't be able to tell right? LOL
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Attached is the log capture I did immediately after the last time this occured, AND it recovered. Usually, I can't recover and have to force a reboot. Includes last_kmsg, dmesg, and logcat.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I just had a sleep-of-death as well, couldn't get into ADB until I held the power button. Once restarted, apparently no last_kmsg was generated?!

I really think and hope that the logs tlazarus just uploaded will help us get to the bottom of this horribly annoying bug, but we won't know for sure until h8 or inter take a look with their much more experienced eyes.

Edit: After looking at the last_kmsg for a few minutes, I'm seeing a HUUUUUGE amount of these errors:

mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed

Do I know what that means? Not really, and there's every chance it's a totally common error, or something specific to tlazarus' device, but just trying to call out what I see in there.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Attached is a meminfo capture a few seconds after phone became responsive again.

Also, I've noticed that if I lock my phone as soon as it becomes unresponsive, it generally recovers. It is as if trying to do to much causes it to lock permanently. Seems to bolster the memory theory.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Hey, why do you need to call out my device? It is embarrassed now :) If you look up that error, it sounds like it has to do with the display interface and setting the clock speed for the display. I would love to know why it happens, but I am not sure it has anything to do with the current issue. Of course, I could be completely wrong.
[AT&T, Rogers HTC One X, Telstra One XL] felixrising:
Nothing exotic installed on my ROM. My colleague with Samsung Galaxy Nexus has a fresh CM11 installation on his phone (I moved him over to it just a couple of days ago - he's not very happy so far).... crashing/freezing/reboots several times a day is getting rediculous... may need to jump ship to another ROM after all these years - hopefully the issue can be found and resolved soon.. :crying:

PS. Can someone point me at the preferred method of capturing logs so I can share some crash/freeze/reboot information?
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Just saw these from CM as well, since this is still the Q&A for CM11, here you guys go:

New recoveries needed going forward: http://www.cyanogenmod.org/blog/psa-htc-devices-recovery-updates

Wikipedia with instructions: http://wiki.cyanogenmod.org/w/HTC_fstab_updates

GitHub commits: https://github.com/CyanogenMod/andr...mmit/f29e73203ce5f3d4ae9f2715b60c082316998f3c

Hopefully we can get this other (presumably memory-related) issue figured out soon, because things are moving fast!
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
There is an experimental/test version of CM 11 up on the standard evita download page. I assume intervigil is trying out a few fixes (I know he is for the ville). I am running it right now, but I'd recommend waiting until the developer comments on the ramifications of the changes before rushing to install it.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
That's excellent news! Let us know how it goes for you, I'm sure intervigil will pop in and let us know that they isolated and fixed the issue once they actually have.

Edit: Here's the code review, at least the one I found easiest: http://review.cyanogenmod.org/#/c/63206/
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Yup, pretty sure that is the one.

I've been using my phone pretty heavily for a few hours now without any sign of lowmemorykiller running amok, so hopefully we are headed in the right direction.
[AT&T, Rogers HTC One X, Telstra One XL] an_xda:
I'll give it a shot on a Windows 7 work laptop. Can you advise where I can find the latest drivers for the HTC device?

It may or may not be firewall protected but I have no other options on my Windows 8 machine!
[AT&T, Rogers HTC One X, Telstra One XL] BAMF_Nole:
Just going off of this, I froze "themes 0.1" and "Themes provider 2.0.25" in titanium backup about 30 minutes after this was posted and have not had any other issues with freezing or SOD since.

If i can provide any other information please let me know...
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Unfortunately, it doesn't look like the fixes in the test version completely resolve the problem. I did run it most of yesterday without any issues, but when I woke up this morning and tried to check my email, the problem returned. The logs show a similar pattern of low memory warnings and then the sudden death of most of the important processes. I've attached them, as well as the meminfo export. The fixes do seem to help the problem, however, so I am going to continue to run the test version.

Tim
[AT&T, Rogers HTC One X, Telstra One XL] :
Can i install cm11 with 2.15 firmware?
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Okay so I am currently on cm-11-20140427-NIGHTLY-evita.zip And I tried flashing too 0503 nightly upon flashing I get failed. Can't update binary etc.. I have the modded TWRP so I don't know what to do? Any ideas?
[AT&T, Rogers HTC One X, Telstra One XL] timmae2:
http://www.cyanogenmod.org/blog/psa-htc-devices-recovery-updates

" Beginning with nightly 20140501, an updated recovery that has kernel support for by-name partitions is required to install/update CyanogenMod on certain devices."
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
i mentioned that before already, and created a recovery for it...Link in my sig
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Sorry I hadn't the time to search quickly! Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I've been running the second of two experimental OOM fix versions for a while now, and unfortunately the problem remains. It does sound like it is working better for folks on the One S, so maybe there is still hope. I did save a log, but since there is nothing new in it I am not going to bother posting it unless asked.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
thanks for the update :) the freeze ups are right after you close an app?
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Kind of - the most common cause for me is opening the status bar while in an app. There is more info in the One S thread, but it sounds like Android can't handle opening the status bar when there are pending notifications for apps that have been killed because of the OOM issue. This causes the entire system to hang.
[AT&T, Rogers HTC One X, Telstra One XL] johnnyham89:
Just flashed cm11 5/4 and I'm still experiencing the really bad freezing. Seems like it happens only when I pull down the status menu for some reason.
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Glad I'm not the only one. My phone keeps locking up randomly when I pull down the status bar. Have to hard reset. Other than that it works great. Well except that if you lock your phone while the camera app is in landscape and then unlock you phone in portrait the lock screen gets screwed up.
[AT&T, Rogers HTC One X, Telstra One XL] timmae2:
did you test new m6 release?
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I'm running M6 now, but I am not optimistic. M5 was fine, and they appear to have no idea why the problem suddenly popped up, so almost any commit post-m5 could reintroduce the problem.
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Ppl have certainly been 'chiming in'. I have gone back to 29003 nightly with Torch 4.0 and not having any problems now.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
This is the latest attempt at fixing the issue, but reading through the comments it seems like it didn't quite do enough to help: http://review.cyanogenmod.org/#/c/63034/

I have to say though, I've been running PA with the latest Bubba Kernel (he did some Memory Management fixes) and the issue seems to have gotten a lot better. We're not getting another PA build out until maybe later today, but it looks like all of these changes have been merged in to the CM GitHub, so the next PA build will have all the fixes that have been attempted so far.

Intervigil, any news on anything that's been tried since the link I put above?
[AT&T, Rogers HTC One X, Telstra One XL] xdastefan:
Hi guys, quick question: do I need the new unofficial TWRP to flash the M6 build? Iirc, M builds get frozen a week before release, so the fstab change should not be in it. Am i correct or do I need the new TWRP?
[AT&T, Rogers HTC One X, Telstra One XL] Madcat8686:
Yeah, I don't get it. It was running great around the M5 time period. I guess they have gone too far to go back and start over from the most stable point. It was the most stable I've ever seen CM when I jumped off to test out the stock software. I thought I would be off only temporarily but every AOSP Rom on here seems to be having issues.Here's to hoping they fix it. We went through this stuff before with JB.
[AT&T, Rogers HTC One X, Telstra One XL] riveracarlosm:
Unfortunately I went from M5 to M6 and my phone started freezing. I decided to move back to the M5.
[AT&T, Rogers HTC One X, Telstra One XL] danix180:
Same issue here. On M6
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
I think this is possibly the biggest issue.. I find it tricky because my power button is screwed..
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Same here. Freezing both of those does seem to have resolved the issue for me as well.
[AT&T, Rogers HTC One X, Telstra One XL] operanal:
Missing Notification Bar

Hi All,

After jumping back and forth from the latest nightly and the M5 snapshot, I seem to have lost my notification bar. Has anyone else seen this, and is there a solution that doesn't invoke a full wipe?

Thanks in advance!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I think a full wipe is your only solution, this is the kinda thing that happens when dirty flashing.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] riveracarlosm:
I had a similar problem. My quicksettings panel was not working. Ended up having to start fresh. I had a backup but decided it had been a while since I started clean.