yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] FSB:
I have been getting the same. Seems my WiFi has issues connecting as well, needs reboot to connect. I have dirty flashed the last 10 nightly over clean install.
[AT&T, Rogers HTC One X, Telstra One XL] FarSight87:
Hey guys,

Ive noticed some strange behaviour in the last week or so.

I usually only flash a nightly every couple weeks or so, since December.

I was running 30th march nightly fine without any problems. Then I flashed 12th April nightly and started to experience some odd behaviour.

Occasionally during normal use my screen will become unresponsive to touch and current activity halts. I can still turn screen off with power button, but it won't come back on. I have to hold for 15-20 secs to reset. Started happening a few times a day now. I can't quite pinpoint the exact action when it happens. Usually when pressing home button while an app is open or turning screen off with an app open then immediately turning back on. I've had instances where the screen goes completely black except for the status bar, but everythings unresponsive.

I decided to start from scratch.

Downgraded to ruu and ran all ota updates. Back on hboot 2.15, s-off, supercid, BL unlocked, twrp 2.7, flashed 16th April nightly and set phone up again last night. I've so far encountered the same problem twice since, causing me to reset.

I dont know if there's something that's been added or changed since the 30th march nightlies that could be causing this issue.

Any ideas?

Cheers.
[AT&T, Rogers HTC One X, Telstra One XL] paras33:
use hboot 2.14 or the latest 2.18 for this rom.....also twrp 2.6.3 modified is much better in my opinion
[AT&T, Rogers HTC One X, Telstra One XL] FarSight87:
I'm getting the freezing also. After upgrading from 30th March nightly to 12th April nightly. Somewhere inbetween something has changed. I received a pm saying to switch CPU governor away from on demand. Trying it now. Had one freeze already on interactive.
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
A logcat and a kernel log (kmsg or last_kmsg) might help the developers find a solution.
[AT&T, Rogers HTC One X, Telstra One XL] TonyStark R.I.P.:
^^This^^

Make sire to list the apps that you have running as well.
[AT&T, Rogers HTC One X, Telstra One XL] yespda2:
Please, vote for CyanogenMod improvement to the brightness control settings https://jira.cyanogenmod.org/browse/CYAN-903
[AT&T, Rogers HTC One X, Telstra One XL] Skyfallkavu:
I haven't done this in a long time. Attached is a last_kmsg and logcat, but I'm not sure I properly captured the logcat.

My evita crashed when I was setting up adb over wifi, so the last_kmsg should contain some info

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

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

I'm not sure sure of all the apps I had running. Hangouts, Chrome, Snapchat. It was a regular morning.
[AT&T, Rogers HTC One X, Telstra One XL] doc_shri:
Even my cell got suddenly freezed and went blank, and have reboot it to start again, how to report it what's logcat and kernel msg, how to see?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Google search how to get a logcat and how to get a kmsg.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] edwardgtxy:
Please show some love to headset microphone users :)
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Man, this issue has been around for maybe 2 years, and there's a reason why it hasn't been fixed
[AT&T, Rogers HTC One X, Telstra One XL] carlos_d11:
constant signal loss

can you help me, problems with constant signal loss : Confused:

com.android.phone stopped

***TAMPERED***

***UNLOCKED***

EVITA PVT SHIP S-OFF RL

CID-11111111

HBOOT-2.18.0000

RADIO-1.35a.32.45.27
[AT&T, Rogers HTC One X, Telstra One XL] XRACER:
Hello, could use some help,

Currently can't install any roms, all fail during flash, used to play around with flashing all the time but haven't done it in a while and i guess it bit me in the ass. while attempting to upgrade to 4.4

my setting

S-ON

modelid PJ8310000

cidnum 1111111

HBOOT 1.14.0002

RADIO-0.19as.32.0911_2

TWRP unofficial 2.6.3

Previously had Cm 10.1....nightly something, (it was a while back)

Since i have not done this in a while i presumed i had S-OFF (didn't bother to check) and went ahead with the later steps as noted in the installation procedure.

Now i can't install anything at all. All fail during flashing

currently attempting to install 10.2 so i can get S-OFF but not able to install.

Any help will be appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You need to get s-off so you can update your firmware by running the 3.18 RUU. Flash a Sense ROM, get s-off via Facepalm S-off, run the 3.18 RUU, flash a KitKat compatible recovery again, flash a ROM.

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

However i see no way to get S-OFF when no version of android is installed, from reading all of the S-OFF option they all require a valid version running, which at this point i do not have.

If you know of getting S-OFF any other way please let me know.

Thank you
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's why I said you need to flash a Sense ROM first. It's right there in the step by step list I gave you.

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

i completely miss read that, i read "you need to get s-off via Facepalm S-off, and then run the 3.18 RUU" the highlighted part added by me :S

Thanks, i will give it a try and see how it goes, although i think at one point i tried it :)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's exactly what I was saying. You get s-off via Facepalm and then you run the RUU. I then went on to say you need to flash a Sense ROM before getting s-off. Do not under any circumstances run the RUU before you get s-off or you'll brick your phone.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] XRACER:
In that case goo thing the RUU installtion failed :eek:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
1) Flash a Sense ROM.

2) Get s-off via Facepalm S-off or Rumrunner S-off.

3) Run the 3.18 RUU.

4) Flash TWRP recovery again.

5) Flash a ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] XRACER:
Hello sorry for the late reply, need it to sleep :)

In any case i flashed Viper ROM (with sense) and then i flashed the boot.img got stuck in a boot loop, i did a wipe dalvik/cache since i remember that usually cleared all all boot loops, however i can't get to boot. Maybe i should be posting this in the viper ROM thread, but since I started here figure won't make multiple threads.

Thanks

-----EDIT-----

Sorry in my haste to do this fast, i have been flashing the wrong boot.img :eek:

only realized this when i decided to try another ROM now running CleanROM 7.0R2

will do S-OFF and all other steps after work :)

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I am having the EXACT same problem. Everything was working amazingly well until sometime around early April, at which point the problems began... Random unresponsiveness, no pattern. Also tried running the latest RUU, etc., as well as several different kernels - nothing has helped.

The last time this happened, today between 4:15 and 4:30 PM EST or so, I didn't hold down the power button - I waited until the phone eventually recovered and then grabbed the logs. Hope this helps... For the period I mentioned earlier, there is definitely something odd in the logcat log.

Tim
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What you're experiencing is happening at kernel kernel and happens after the device had been in a deep sleep. Flashing a custom kernel fixes it.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Problem is, I am running Bubba kernel right now, and was running Torched before that. Problem still exists...
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I flashed the Torched kernel (3.7 to be exact) and it completely fixed the problem for me.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
hmm...what nightly are you running? Also, in logcat, it looks like I am running low on memory when this occurs. Seems odd though that this wouldn't be happening before and then suddenly start.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm not anymore but the nightly I was running was the 0420 one. I also ran one from a couple of weeks ago, had the same issue, flashed Torched, and it fixed it.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] FarSight87:
I've just completely started again (again), as of last night. I installed the latest snapshot build m5 from 5/4/14. So far no issues. Give it a whirl.

Looks like the problem lays somewhere in changes made between the 5th and 12th April.

Will let you know if the unresponsiveness happens on this m5, but it should have occurred by now.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I'm running M5 now as well, so we will see. Using a custom kernel didn't help, unfortunately. Logcat appears to show memory running low when the problem occurs, then the touchscreen not responding shortly after that. I'd hate to go back to Sense, but having to reboot at least once or twice daily is killing my productivity.
[AT&T, Rogers HTC One X, Telstra One XL] XRACER:
Well guys,

I wanted to thank for the help, i am currently running CM11 with no issues, was able to get everything working. :)

Thank you to all who are involve in the the development of all MODs.
[AT&T, Rogers HTC One X, Telstra One XL] FarSight87:
Running M5 for nearly 72 hours now with no freezing or unresponsiveness.
[AT&T, Rogers HTC One X, Telstra One XL] louslugger15:
Hate to ask something that's been asked before more than likely, but this thread is fairly expansive. I'm on Radavs stock Rom and looking to try out this Rom. I'm s-off and updated to the latest firmware that came out before AT&T released their latest update. What do I need to install this? Specific recovery for KK, etc?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Check out the Evita FAQ thread, question 27 to be exact.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
A recovery with selinux support. Includes modified. TWRP 2.6.3.0, TWRP 2.7.0.0, latest CWM, latest Philz recovery
[AT&T, Rogers HTC One X, Telstra One XL] an_xda:
So I am currently on CleanROM and plan to go back to a more stock experience, from what I understand I will be losing out on the drivers for the HTC camera and beats for audio.

Are there any major benefits to CM11 to justify losing these features? If I were to flash, I guess going with the latest stable build from January would be my safest bet?

Last time I flashed a rom was nearly a year ago!
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Being on the latest version of Android and lots of custom themes in my opinion
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Plus there are a bunch of extra features that you don't get on Sense ROMs. CM itself isn't very feature packed but other aosp ROMs are.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] doc_shri:
HI dude spirit fm is not working in India, it showing only north America, Japan pls tell any working fm for Indian cities
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Why are you posting that in this thread? It has nothing to do with CM. You should post your bug in the Spirit FM thread n

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] doc_shri:
I was on stock rom, now on cm11
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The problem isn't ROM related, you need to go to the Spirit FM thread.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] an_xda:
Yeah, just wondering what these features are to justify a reduction in photo quality and losing Sense...

Because it is 4.4 - will I need the latest version of TWRP? I am still S-ON (never had the ability to S-OFF on my Windows 8.1 machine) too.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
There are too many features to mention, if you just flash a few ROMs you'll find out. ROMs like Beanstalk, AICP, Carbon are the ones with the cool features, CM has become much more like a stock ROM.

Yes, you will need to update your TWRP recovery to the modified unofficial 2.6.3.0 posted by jrior001 in our Original Android Development section. You also need to make sure your firmware is updated, but you need s-off for that. What are your bootloader details please?

PS. I wouldn't say you're going to suffer a loss in image quality. I take many photos with cameras other than the Sense camera and just as good. I even did a side by side comparison thread and you can't tell the difference. That was a while ago and the aosp cameras have only improved since then. The thread is here:

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

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Since around the time of the most recent snapshot but probably slightly before, I have been experiencing strange behavior. The phone will sometimes freeze. Other times it will go through a lengthy process where it eventually wakes up to the lock screen .Other times it never wakes up. I am also getting a number of unexpected reboots. I tried a full wipe but same behavior. Judging by the lack of activity here it may be just me but wondering whether anyone else is having similar issues?
[AT&T, Rogers HTC One X, Telstra One XL] phylacterion:
Having the same behavior here...
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Had a couple of messages from other ppl with the same problem. Been kicked from the Dev thread ( which is fine in theory ) but strange that noone in the Dev thread is offering anything. I have switched to Torch 4 with no voltage limit and no more problems so far after 12 hours. Will repost if I do. Why is the Dev thread silent about any fix for the stock kernel on this issue. Its a bit of a problem?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You haven't been "kicked" from the dev thread, your post was just moved to where it belongs. This thread we're in now is dedicated to q&a, troubleshooting, and off-topic conversation, so this is where your post belongs. The ROM thread is specifically for development talk, so basically unless you're contributing to the devolving of the ROM you don't post anything in there.

It isn't a matter of the dev thread being silent on the matter, the dev thread isn't where such a topic would be discussed. If other users haven't been experiencing the same issue, then that's why I'm guessing you're not getting anybody chiming in on your issue.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] an_xda:
Okay, TWRP is currently v2.6.0.0 so I will search for v2.6.3.0

How do I find out what version the bootloader is? Sorry, it has been a long time since I tinkered with the phone. Going into recovery mode, I see the following:

Tampered

Unlocked

EVITA PUT SHIP S-ON RL

HBOOT-1.11.0000

RADIO-1.31a.32.45.16_2

OpenDSP-v33.1.0.45.1128

eMMC-boot

Jun 7 2012,13:10:34
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Well there are ppl chiming in? Just look three posts above.

And in retrospect there was also other posts about it last week. There is no doubt in my mind that something was done shortly before the most recent snapshot because the issue doesn't occur with the Torch kernel.

---------- Post added at 08:26 AM ---------- Previous post was at 08:19 AM ----------

Edit: just experienced the issue with Torch v4.

Will try Torch 3.7.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You need to get s-off first, then you need to update your firmware. I'd suggest you try the Rumrunner s-off method:

http://Rumrunner.us

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Not for me.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You could try going back to a previous version of the ROM (I think pre April 4th might be ok).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
So why are you saying there is no issue for devs to respond to? This is a problem with the current version of the ROM.
[AT&T, Rogers HTC One X, Telstra One XL] tof9:
Hey mate, I've been getting the exact same issues but I thought it was my Evita giving up on it's last legs. Even did multiple full wipes.

I normally run the latest nightlies and now with Torched 4.0 noOC kernel.

The phone is almost unusable as a daily but I just haven't had time to sus it out.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I never said there wasn't an issue for the dev to respond to, l just said it needs to be posted in the correct thread. I'm sure h8rift has his hands full maintaining multiple devices, but I'm confident he's working on a fix even if he hasn't mentioned it here.

Just to be clear though, only a few people have also reported what you're experiencing. This is only a small percentage of the dozens or hundreds of users on this ROM. So from that we can assume that problem isn't absolute, and could have more to do with firmware, or gapps, than the ROM itself.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fezzawinkle:
Can you stop being a gatekeeper and hosing me down about trying to raise an issue, so it actually gets fixed. When you do that, ppl continue to suffer in silence for a few weeks like i did not reslising there is a problem

Would it be so difficult for a dev post to be lodged saying best not to download the latest nightly because your previously working phone will stop working properly and we are looking into it?

It is clearly an issue. Ppl having exactly the same experience are responding confirming this. Your own previous posts suggest you had the same problem but believe it is solved by torch 3.7 which it isn't. It is clearly not firmware because none has changed. Query how it could be gapps when you own analysis of the logcat was that it is a kernel issue..?
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I'm getting the same reports in the Paranoid Android thread, sleep of death, random reboots, etc., and I use many of CM's underlying libraries and frameworks for the Evita build of that.

There's definitely something up, I'm getting the same issues every now and then, as are many people on the Evita forums. Most (if not all) of the AOSP-based ROMs for our device are using somewhere from a little to a LOT of CM's code to handle a lot of base-level stuff, mostly because CM/h8rift is one of the only places still updating for the Evita, period, so people having this issue on many different ROMs really do all come down to the root level, which is CM11. And if these nightlies are having the same problem, then this is BY FAR the best place to talk about how to fix it.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I think you're being overly hostile about this whole subject. I'm not trying to hose you down. We're on the same team. I did no analysis of any logcat to reach my conclusion that the problem that I experienced was kernel related, I reached that conclusion by flashing the Torched kernel and it fixing my issue. The reason I mentioned gapps is because differing gapps packages have been known to make the difference with previous bugs, I'm just spit-balling.

I don't want people to suffer in silence, I've never once said that people shouldn't post their bugs, all I've said is that this thread is the correct thread for troubleshooting. The fact that your post was moved by a moderator to this thread should tell you that this is where it belongs. Regardless of where your post actually is though, h8rift has access to both threads so he's still able to see it perfectly well here, so I'm not sure why you're kicking up such a fuss. It isn't like he's able to see posts any better in the ROM thread than he is in this thread. And lets not forget, he himself created this thread.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] clone22:
the problem of reboots and the famous sleep of death, in my opinion lies in the minimum frequency of the CPU, because I spent those bugs and fix achieved, the minimum turnin 'it up to 486MHZ frequency and improved significantly, note that I installation of both the original kernel of the rom and the rom is installed Paranoid 4.2, is now a great time, thanks for your great work Cryptecks ​​forgive my bad English

waiting for the 4.3 upgrade, jejeje with ances :good::good::laugh:
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Wrong thread :P
[AT&T, Rogers HTC One X, Telstra One XL] clone22:
I know that is CM11, I refer to the problem with reboots and other bugs, and incidentally to thank the developer of the rom Paranoid, lol

:D:D:good:
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Thanks, but I'm just the guy that gathers all the stuff up for it to build every week, the true developers are the AOSPA guys!

Anyway, back to the issue at hand, the random reboots and sleeps of death that affect almost every KK ROM for the Evita... Most of which are based on CM11.

I'm intrigued if the fix is really something so simple. I'm going to give what you said a try. It's a start!
[AT&T, Rogers HTC One X, Telstra One XL] clone22:
I seriously had no more reboots or anything like that, and this superfast ROM :good::good::D
[AT&T, Rogers HTC One X, Telstra One XL] chrisb906:
Yea. I would occasionally get reboots..even the sleep of death. Not that the roms theirselves are bad, just that there's a bug out there and we are determined to find it and fix it. I think the cause of the sod was of me tinkering with performance settings, flashing kernels and diff mods for tweaking the under/overclocking. YES. I DID flash appropriate mods for my device. Not that I flashed incompatible stuff to my Evita.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I can confirm that the torched kernel does NOT fix the problem for me. Out of no where the phone will stop responding. After a few minutes the phone will generally return to the lock screen, but not always. The logs are full of unresponsive window events. I've captured the logs immediately after, and there is one attached to my earlier post.

I've since gone back to Sense as this is my daily driver and CM 11 isn't stable for me anymore. It is too bad there isn't a true bug tracking system for CM Evita (or at least one I know of), because QA threads aren't the place to scientifically track down a problem. I also get the sense Evita development is essentially dead at this point, although I really hope I am wrong.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Unfortunately I think I have to agree. The wider scope of development has indeed slowed down a whole lot. I have it on good authority that we might have a surprise in store for us soon though. In regards to the bug, I guess what I was experiencing and what you guys are experiencing are different bugs altogether. I would get periods of unresponsiveness, usually right after the device had been asleep. Flashing the Torched kernel completely fixed this for me, but this was on a couple of nightlies a week or two ago.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] felixrising:
CM11 freezes

I am also seeing this bug.. freezes, usually with blank screen but top info bar still visible, sometimes just blank, sometimes it requires a total reboot but other times it just unfreezes after a few seconds if I do nothing. My friend who also has current nightly on his Samsung Galaxy Nexus is seeing identical problems... very frustrating, not good for a daily driver.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
To those of you experiencing the freezing/hanging issue - can you tell me if you are running or have configured any of the following?

- xposed framework

- a particular google apps package (i.e. Banks minimal instead of stock CM)

- exchange account/corporate sync account added

This may go nowhere, but I am trying to figure out if there is something in particular that causes the bug to pop up.