yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Mine started up again also. I'll get a logcat before bed and just use the stock app for now.
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
clean flashed this morning. so far twice today. ive been using my phone like normal (mostly texting)

lock the phone, and the next time i go to unlock it phone wont unlock ,and have to hold down power till phone reboots

(other then that everything seemed perfect, fast, smooth, superuser working, etc)
[AT&T, Rogers HTC One X, Telstra One XL] sephiroth2k:
My pics are upside down in focal when taken landscape also, had only tried portrait previously.
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
[MENTION=2703964]h8rift[/MENTION]

here are 2 logcats for the focal app and upside down pics. It worked fine on logcat1 and it flipped them on logcat2. Also, when an image is flipped if you open it in gallery and hit "menu>details" it shows the orientation as 180 as opposed to 0.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
"Facing" which I assume simply means "front facing camera" is also upside down in the preview for focal.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
The latest nightly has fixed Spotify cutting off when the screen turns on :D I figured I'd bring this to the attention of people.

Edit: Ehhh maybe I was wrong. Sorry guys. Hope it gets fixed soon. It was working when I originally posted it.

Sent from my HTC Evita with XDA Premium 4
[AT&T, Rogers HTC One X, Telstra One XL] drubin333:
Did this logcat help? I've tested with the last 2 Evita 10.2 nightlies, but still see the issue that the mic and vol buttons on the wired headset are not being recognized. Let me know, and I'll try to provide whatever is needed. Thanks for your efforts!
[AT&T, Rogers HTC One X, Telstra One XL] jcbennett:
Have been using the 8/19 nightly for 24 hours now. I had one forced restart during that time but could have been a memory issue. Solid release. Be sure to check out the Q&A. Most of the small issues people are encountering are addressed there.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Edit: maybe I was wrong. It seems better, though. Only some of the time.

Sent from my HTC Evita with XDA Premium 4
[AT&T, Rogers HTC One X, Telstra One XL] everix:
The issue where the device will not lock, which you fixed in CM 10.1, seems to be back.

here is the issue report from before and the cause appears to be the same. I figured out how to manually resolve it and that was by killing the Handcent SMS Process.

https://code.google.com/p/cm9-msm89...tus Priority Milestone Function Owner Summary
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
I would just like to confirm that the reception dropping bug has been fixed! I am sending this message from the train with full signal (which was impossible before). Thanks for the great build!
[AT&T, Rogers HTC One X, Telstra One XL] onesun43:
Getting noticeably better standby battery on 8/20 build. New daily driver for me.
[AT&T, Rogers HTC One X, Telstra One XL] Slow*Jim:
Another brick here. 8/19 build. Was running it just fine for ~36 hours, plugged in around half of that time. i had the phone sitting on my desk last night (not plugged in) and it won't turn on now.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Maybe just coincidence, because you're the first person to report a brick in over a week. Might be one of those random bricks that happens on this device.

Sent from my HTC Evita with XDA Premium 4
[AT&T, Rogers HTC One X, Telstra One XL] mrlazyone:
Maybe the phone lost all of it's charge. Try charging it for about 15 and try to turn it on.
[AT&T, Rogers HTC One X, Telstra One XL] HaKKeD:
Anyone else have problems connecting to Wi-Fi? I entered in the password and it just never connects...
[AT&T, Rogers HTC One X, Telstra One XL] kotchishm:
what did it show when you plugged it into the computer?
[AT&T, Rogers HTC One X, Telstra One XL] Slow*Jim:
Absolutely nothing. No change in Device Manager and nothing on the phone screen. Not even a red LED charging indicator.
[AT&T, Rogers HTC One X, Telstra One XL] Desertman123:
Try playing with the power button/volume buttons (like attempt to boot into boot loader). My dads phone (my mom, dad and I all have evitas) literally did the exact same thing 2-3 days ago and his is unrooted, running stock 2.20. I just held the power button for like ten seconds, put it down, let it charge, did it again, and again, etc. just played with it and eventually the red light came on, then a few minutes later I was able to boot it up no problem.
[AT&T, Rogers HTC One X, Telstra One XL] Slow*Jim:
HOLY CRAP IT WORKED!!!

unplugged the phone, held the power button for 30sec, held down arrow while holding power button for awhile, nothing. Plugged it in and the red charging light turned on and I was able to power up the phone like nothing ever happened!
[AT&T, Rogers HTC One X, Telstra One XL] Desertman123:
No problem! No need to say thanks, just hit the button :)
[AT&T, Rogers HTC One X, Telstra One XL] intervigil:
If you plug in the phone while it's off it will reboot into recovery as HTC charger mode is part of their recovery. If you aren't careful that means the phone will just be powered on and completely drain if you then unplug it. If the screen then powers off you basically need to hard reset using the power button+vol key. HTC charger mode is very strange.

I've long suspected that people with "random bricks" (NOT the emmc bricks) are basically running themselves out of battery or somehow ending up in a strange state due to charge mode, and not actually bricked.

The patches to fix HTC charge mode were merged a few weeks ago, but the CWM images available haven't been updated yet. If you are using a cm-10.2 built recovery from the last week or so you should have the fix already.
[AT&T, Rogers HTC One X, Telstra One XL] Slow*Jim:
Interesting. My battery showed 28% when it booted back up. It now seems to be charging very very slowly, even when plugged into my wall charger.
[AT&T, Rogers HTC One X, Telstra One XL] gibosn6594:
Yea, my battery has been charging very slowly too and my battery life is worse than it was with 10.1. I didn't have the "brick" problem you had though.
[AT&T, Rogers HTC One X, Telstra One XL] Arrow44:
So is this the official nightlies?

-Sugardaddy
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Yes
[AT&T, Rogers HTC One X, Telstra One XL] nerk69:
Been rocking this ROM since the trim issue was dealt with, and it fantastic. Thank you.

Battery life and smoothness are better than cm10.1, although the battery does not last as long as with sense. I was trying out BLE this morning and found that it would see the device and says it pair, but no apps can read data from it. This is working the same as it did with the stock ROM.

Tried grabbing bluetooth.default.so, libbt-hci.so and libbt-utils.so from the Nexus 7 image, but that just caused Bluetooth to crash.

Does anyone know is BLE support will likely come to this device?
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
This would be better suited in the 4.3 Q&A thread. Although I remember reading about that same question and from what I remember, our chip supports it. Its just a matter of getting it to work I THINK.
[AT&T, Rogers HTC One X, Telstra One XL] josepr0218:
This rom is great, just thinking for a kernel with fast charge for this rom....??

---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------

If it possible...
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
CM doesn't fast charge...too dangerous and wears out your battery.

---------- Post added at 09:24 AM ---------- Previous post was at 09:24 AM ----------

There's someone on the One S page with a flashable zip that is supposed to enable.
[AT&T, Rogers HTC One X, Telstra One XL] zedomax:
Just a note, I was able to install this ROM just using fastboot method without upgrading my bootloader and removing the asserts for bootloader check, what is the reason for upgrading bootloader?

It's working fine btw, everything including camera, bluetooth, calls, SMS here.

And HUGE THUMBS UP for bringing this to One X!!!
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
The 3.4 kernel has some firmware dependencies. The hboot check is a way to check that it's likely you have current firmware. Perhaps you do in fact have pretty recent firmware, but an older hboot...otherwise, you'd likely bootloop.
[AT&T, Rogers HTC One X, Telstra One XL] zedomax:
OK thx for the reply, I just wanted to make sure no one ends up in a hard brick. My last upgrade was months ago so I am not sure which firmware I have but I think it's one of the first jelly bean firmwares I did when it first came out so maybe anyone who has upgraded to jelly bean should work is my guess then.

Thanks again, keep up the great work u do!
[AT&T, Rogers HTC One X, Telstra One XL] Pro75357:
Random reboot + sluggishness

Hey guys,

I just had a random reboot with resulting sluggishness pretty much the same as I used to frequently get on CM10.1. This time I was lucky enough to be at my computer so I got logs DURING the sluggishness which is something I haven't managed to do before.

I'm running the 8-19 10.2 nightly. Phone was sitting in pocket- felt it vibrate so I checked it just to find it had rebooted and the boot animation was going slow and not smooth like usual. so I plugged it in and got logs.

the logs may not be complete as the best I could do on short notice was copy-paste from the terminal. I'm going to learn the right way to do this now :)

If anyone else has seen this please confirm and I will add it to the issue tracker.

Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Looks like it's coming in the next nightly. *win*
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Also looks like the focal pic orientation fix will be in tomorrow's build.
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Last week, I decided that I was going to conduct a little experiment with APN's. I wanted to do this for 2 reasons; first, because I had a feeling that something wasn't quite right, and second, because I noticed that some people were still having some data issues. To start off, I had been using the ATT LTE (pta) APN, which just about everybody else was using. I was having periodic data drops like most people were, and it seemed primarily tied to tower hand-offs from LTE to HSPA. I would notice it when driving home from a region that had LTE, and when I would get closer to home (which doesn't have LTE), data would be gone. I also had a few strange incidents where I would loose all data, WiFi included, after hanging up a phone call. But enough back story. My first question in this experiment was, "What is the default APN of a stock HOX?" So I grabbed my wife's phone and took a look, and found that the only APN listed was "phone". At this point I compared the settings to those on both the "phone" and "pta" APN's in CM. All the settings were identical except for one, the "APN type" field. There were a few values missing in the CM version, some of which I could figure out were left out for a reason, like "fota" and "admin". A quick Google search of AT&T APN settings, and I found this; for 4G/LTE, it should be set to the "phone" APN, and the "APN type" field should be this: "default,supl,mms,hipri" (hipri was missing from the original CM settings). I created my own APN with these settings, flashed the 10.1-20130813-nightly (which was prior to the data fix merge), and have been running with that all week.

RESULT: not one single data drop from changing towers and technology. I've driven through and spent long hours in LTE areas, and never once saw a data drop when switching back to HSPA.

I don't know anything technical about APN's, but I thought that whatever was working for the stock phone should be what works with CM. I don't know how relevant this information is, but it has been working great for me. Another thing that I found when searching for APN settings was several places that showed different port settings for the "pta" APN than what was set. This got me wondering if that is what was causing so many problems for everybody, especially those who were using "pta" and still had drops. Food for thought.

Here are the full settings:

Name: ATT or name it whatever you want

APN: phone

Proxy: [leave blank]

Port: [leave blank]

Username: [leave blank]

Password: [leave blank]

Server: [leave blank]

MMSC: http://mmsc.mobile.att.net

MMS proxy: proxy.mobile.att.net

MMS port: 80

MCC: 310

MNC: 410

Authentication type: [leave blank]

APN type: default,supl,mms,hipri

APN protocol: [leave default value]

APN roaming protocol: [leave default value]

Bearer: [leave blank]
[AT&T, Rogers HTC One X, Telstra One XL] punkisdead83:
Do I loose my apps and saved data when I swipe a new nightly? I'd hate to install all my apps and what not just to loose start over again a day or 2 later.
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
No, this is what most of us do between nightlies and what people mean when they say "dirty flash".
[AT&T, Rogers HTC One X, Telstra One XL] punkisdead83:
+1 Thank you!
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
The battery life has improved tremendously so hopefully the wake button lag is next on the list...
[AT&T, Rogers HTC One X, Telstra One XL] Artood2s:
On the 8/21 nightly. Running great so far. One question though. Where did the option to enable the 3 dot menu go (not the soft key HTC type)?

Sent from my One X
[AT&T, Rogers HTC One X, Telstra One XL] nerk69:
I really wanted to get my nightly flash fix, but I have notice that there where no new builds since 8/21 for any device on get.cm. Looking around, I did find the 8/23 build on the jenkins servers. I have flashed it and so far no problems. I do not know why these are not on get.cm so flash at your own risk.

http://jenkinsmanifest.clockworkmod.com/device/evita/all
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's been asked before and I believe if you have your recents key mapped as menu you can't have the three dot overflow button.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
getting a 404 when i click the nightly link
[AT&T, Rogers HTC One X, Telstra One XL] craig@xatik:
Hmm, I just clicked it and it was working for me.

Edit: Never mind, You probably meant the download link which I just tried.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
In my experience, the link to get.cm seems to get created before the file is completely uploaded to the download mirrors.
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
That makes sense but if that is the case the 22nd would be working or it's been uploading since yesterday which I doubt.
[AT&T, Rogers HTC One X, Telstra One XL] nerk69:
Jenkins is what CM uses for their build servers. This is where the get.cm zips are made.
[AT&T, Rogers HTC One X, Telstra One XL] anonimoyque:
Several problems with last updates

Hello,

I am having huge problems since the last 2 updates... last one that I have is cm-10.2.20130821-NIGHTLY downloaded directly from my phone.

The phone keeps restarting by it self.. I am not doing anything and suddenly restarts. Also Gmail crash when I manually update the app. Sometimes I am not able to turn on WIFI I need to restart the phone to be able to turn it on and the last thing sometimes I am not able to do anything because the system is very very slow.. also have to restart to have this fixed.

Not sure if this is only me or somebody else is having this problems.

I did not had these issues last month
[AT&T, Rogers HTC One X, Telstra One XL] lilbluemirage:
Did you dirty flash? Trying Wiping cache and Dalvik cache. If not, try clean flash. I'm on 0823 without any issues.
[AT&T, Rogers HTC One X, Telstra One XL] anonimoyque:
what is dirty flash?
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
flash without wiping data.....can sometimes cause random issues such as what was described.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
I've been dirty flashing since CM10 without issues. Did the poster above flash the 4.3 gapps? Hopefully SOFF as well?
[AT&T, Rogers HTC One X, Telstra One XL] anonimoyque:
Cool... yes I always do that... I was not aware of this

Many Thanks!!!!:good::good::good::good:
[AT&T, Rogers HTC One X, Telstra One XL] drubin333:
BTW, I just saw on a clean install of the last posted nightly (and all prior nightly builds) for 10.2, even with Bluetooth headset, only the microphone in the device is being recognized, not the microphone in the headset. And again, this works fine on 10.0 builds and on Sense-based ROMs. So it is NOT just a wired headset issue. Am I the only one having this issue on Evita? I am 2.14 hboot, S-OFF...
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
These are also possibilities. There's a number of things that COULD be causing it, it's always best to start fresh when upgrading though to rule out potential issues
[AT&T, Rogers HTC One X, Telstra One XL] mugglecrew:
Network Loss

Hey all,

Just flashed this rom today, and already I can see that it won't reconnect to LTE after disconnecting from WiFi without a reboot. I had this issue on an a CM 10.1 build and all I had to do to fix was update to the latest TWRP build. Sorry if this issue has already been covered but I couldn't find anything mentioning it.

Great work to all involved in this.

Thanks

Edit: I've been flashing several different recoveries to see if this fixes the issue, (TWRP, Philz, about to try clean CWMR)
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
I notice that lte/wcdma option won't stick still and this has been present since pre nightly roms so just want to make sure I'm not missing something.
[AT&T, Rogers HTC One X, Telstra One XL] mugglecrew:
That might also have something to with my problem I'll see if mine doesn't stick as well.
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
I would also set the apn to att pita cause I connect to lte fast after WiFi disconnect, but when I set to lte/wcdma I get way more bars for a sec until it jumps to preferred.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
CM is streamlining and cleaning up the menus. It may come back, and might not. I think for now it is supposed to turn on when no menu key is defined and turn off when one is.
[AT&T, Rogers HTC One X, Telstra One XL] mugglecrew:
Ahhh that did it for me thanks :)
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Focal fix went through but it's still off by 90° in gallery rather than 180°
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
+1 will get logcat and post later
[AT&T, Rogers HTC One X, Telstra One XL] mchun:
Same here

Edit: messing with the apn fixed it
[AT&T, Rogers HTC One X, Telstra One XL] Wonton Soup:
Mines was the same way. I just tinkered with the #*#*4636*#*# network options with that dialer code and mid an matched with the different apn's and found a winner. And I'm on T-Mobile unlocked so I know it'll work for u guys. Give it a try
[AT&T, Rogers HTC One X, Telstra One XL] exad:
For those flashing these nightlies, as this rom/kernel is still in beta, I do not suggest ever dirty flashing these. It takes more time to get your apps installed but it's much safer.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
The CM team themselves say it's fine, even between major versions. Ask this wiping is really just making work for yourselves.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
While I have a lot of faith in the CM team, these roms are software and it would be nearly impossible for them to predict how hardware will react to dirty flashing. You can do whatever you want but I spend a LOT of time reading these forums and see a LOT of random and weird issues from people who are dirty flashing.

I wouldn't go out of my way to make a post like this with no reason to say so.
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
You can't look that hard into the spectrum because these wouldn't be considered dirty flashing more on the side of OTA updating and even those on stock could brick bad hardware.
[AT&T, Rogers HTC One X, Telstra One XL] drubin333:
Any progress? I've noticed that BT microphone doesn't work on the 10.0 build as well - though the wired mic works there. Wonder if it's my device somehow because I feel like I'm the only one with the problem....
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
Try the latest nightly. Seems to be working better for me
[AT&T, Rogers HTC One X, Telstra One XL] drubin333:
Sorry to say no difference (8/24 nightly) - both wired and BT mics not recognized, and the wired volume buttons do not work.

:(
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Get a logcat ( how to in h8s sig) and post on the issue tracker.
[AT&T, Rogers HTC One X, Telstra One XL] mushat3k:
Looks like the 2wire connectivity issue is finally fixed in the 0824 build. I connected to my router within seconds instead of 10 minutes
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Don't see anything in bbqlog referencing it but man I hope so. Will flash for sure when I get home.
[AT&T, Rogers HTC One X, Telstra One XL] mushat3k:
I flicked WiFi on and off a few times and it seems pretty stable, it even has a stronger signal. The 0823 build would barely even connect at all for me, I had to connect to a different router first before it would even think about connecting to my 2wire
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
I was wondering when they would improve WiFi with this router. Hopefully that is the case
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Will evita support BTLE?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Correct me if I'm wrong, but I don't believe our hardware supports it.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] oranget:
So...basically as it sits now, mms and sms messages do not work??
[AT&T, Rogers HTC One X, Telstra One XL] oksimoron:
Worked for me.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
Yep, they just sit at "Sending..." forever.
[AT&T, Rogers HTC One X, Telstra One XL] buddyedwards:
Great work, I had to go back to 10.1 to get SMS working again but 10.2 was buttery smooth can't wait for the SMS/MMS update.
[AT&T, Rogers HTC One X, Telstra One XL] nerk69:
Well, from what I was able to find online, our phones use the Qualcomm WCN3660. According to their website, it is "Bluetooth compliant with the BT specification version 4.0 (BR/EDR+BLE)". Hmm, looks like the same chip that is in the Nexus 4.

I bought this phone on launch day thinking that it already supported this. I still have a BLE heart rate monitor in a box waiting until I can get an BLE enabled phone. :sigh:

Hopefully the brilliant devs will be able to figure this out.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
would SMS work through chompSMS by any chance? im trying to patiently wait for an update, but Flash Syndrome is taking over! :P
[AT&T, Rogers HTC One X, Telstra One XL] tfngwena:
Yeah apparently it does according to the UK HTC OneXL site "Bluetooth with aptX™ enabled (Bluetooth® 4.0)"
[AT&T, Rogers HTC One X, Telstra One XL] oranget:
Yea...hope the new update comes out soon...eager to try it myself..but not until sms-mms works..
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
+1 It's kinda half of the "phone" part in smartphone lol.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
I doubt it would. You could always make a backup of 10.1, flash 10.2, try it, and revert back to the backup if necessary.
[AT&T, Rogers HTC One X, Telstra One XL] boomn:
Bluetooth 4.0 includes both regular higher speed, higher power modes like in previous BT versions as well as the new low power BLE mode, and a device doesn't have to support BLE to say that it has BT4.0. Unless they specify BLE, or "Bluetooth Smart", then it probably doesn't support it
[AT&T, Rogers HTC One X, Telstra One XL] buddyedwards:
It doesn't.....
[AT&T, Rogers HTC One X, Telstra One XL] Wonton Soup:
Havent been this antsy since the sense 5 rom releases lol
[AT&T, Rogers HTC One X, Telstra One XL] oranget:
Must have been some problems with new update build...would have been out by now otherwise..
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
I guess all we can do is refresh. Until then, hound the moto x release!