I know this has probably already been covered a lot, but sometimes mine puts itself in a coma for a long time. Only solution is to let of charge for a very long time, and than it'll only be at like 3% when I boot up.Bricked?
I've been on 8/15 for a couple of days now and I've been simply loving it. Everything about it is darn near perfect. Plugged my phone in last night, daydream mode was on, and I went to sleep. Woke up this morning and my phone won't turn on at all. Completely dead. Long press power, volume buttons. Plugged in. Unplugged. Nothing. Any thoughts?
HTCQommRIL: fita drops when switching state (android_frameworks_opt_thony)
I have noticed that sometimes when I receive a call or wilI turn off the wi-fi, my data is not properly restored and appears to get stuck. The phone will show 3G, but it's grey and when I try to browse there's no data. I have to toggle airplane mode to correct it. Hopefully we'll get a new unofficial build soon that has the above mentioned data fix! Pretty please with sugar on top?
Did you dirty flash? Are you on LTE or wi-fi when receiving a call? I don't see how it's possible since as far as I know the latest unofficial CM10.2 build does not support SVDO. Anyone else care to test and comment?
---------- Post added at 10:49 PM ---------- Previous post was at 10:40 PM ----------
I'm running the latest IRC 8-16-13 Unofficial Nightly as well on my HTC EVO 4G LTE. I only posted about the cm-10.2-20130817-NIGHTLY-grouper.zip because there's a very important data drop fix that hopefully we can get to work on our phones as well. I'm keeping my fingers and toes crossed.
Am I the only one having substantial issues with bluetooth? Starting in mid July (I'm not sure which specific build) with 10.1 and continuing with 10.2 from 8/16, I get a condition where bluetooth becomes unstable and disconnects. Sometimes I can't get it to come back at all, even by rebooting the phone, but then if I try an hour later it's fine for a while. This happens with both my bluetooth headphones and my car stereo, so I don't think it's related to the source device.
Since I originally had this issue, I have replaced my phone, so I am convinced that this is not a hardware problem. When I flashed to 10.2 I did a clean flash and installed my apps fresh rather than restoring from titanium backup. Is there any way an app could cause this behavior? I'm afraid I am at a bit of a loss at this point.
Does anybody else have similar trouble with bluetooth or otherwise have a suggestion as to how this might be fixed?
Appears to be gone. Why do you need it? Just assign a hardware button to menu.
I might be ignorant, but it's not free with TEP?Confirmed that I have a brick. Fortunately I have TEP insurance so it's still going to be expensive, but it could be worse. Filed a claim and should have a new phone early next week. I may not be so quick to point to the 8/15 ROM as the issue, but it does seem awfully strange. Maybe it was just my phone's time to die.
When is he going to get HDMI output working? This is ridiculous. It's been months since he brought this out and yet he can't get one of the core functions working? I get it: don't tell the developer what to do, it's harder than you think, it's a ton of work, yada yada yada, but why is this so difficult? He hasn't even explained why it can't be done, and yet it's the biggest missing feature of this ROM. Get started on it already!