yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] brodie01:
LTE Issue - trying to work through it

To start, I have tried every suggestion on every forum including the one listed a few posts up from this. To clarify:

1. Clockworkmod Recovery, Data/Factory Reset, Wipe Cache, Wipe Dalvik

2. Flashed Cleanrom 4.0

3. Did a Data/Factory Reset, Wipe Cache, Wipe Dalvik

4. Booted into Cleanrom, added Rogers LTE APN, saw the 4G LTE icon

5. Rebooted to Clockworkmod Recovery, Data/Factory Reset, Wipe Cache, Wipe Dalvik

6. Flashed CM10 (0906 nightly) and Gapps (0726)

7. Booted CM10

8. Added APN for Rogers LTE - deleted 3 existing APNs and selected Rogers LTE APN

9. Changed Network mode to LTE/GSM auto (PRL) via *#*#4636#*#* menu/Phone Information

Now, some things I noticed. When I set any of the network modes that have a (PRL) at the end, if I push back ( < ) button and then Phone Information again, the change has already reverted to WCDMA preferred and no 4G icon is ever displayed. This is the same if I choose LTE/GSM auto (PRL) or LTE/GSM/CDMA auto (PRL). If however I select any of the settings that do not have the (PRL) at the end (for example, LTE Only or GSM Only) the change remains after I click back and the Phone Info again. With LTE Only selected, I did see the 4G icon.

If I select LTE/GSM/CDMA auto (PRL), occasionally when I navigate back and into Phone Info again, it will change over to LTE/GSM auto (PRL) instead of going straight back into WCDMA preferred.

However, setting LTE Only does not allow me to make or receive calls. Carrier is Rogers in case it wasn't clear from above.

Any other suggestions?
[AT&T, Rogers HTC One X, Telstra One XL] yungskeeme:
Anyone?
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Handset and speakerphone volume on the 9/5 nightly is loud enough for me.
[AT&T, Rogers HTC One X, Telstra One XL] loraque:
I would totally pay $10 for an AOSP compatible HTC camera app. I am willing to plug in AUX (now that it works) and deal with no Pandora over BT... but the picture quality difference is just too much for how I use my phone. Did the comparison, and the difference is more than just post-processing. Just like on my VZ Gnex before this, which has a rep for a bad camera even though I thought it was decent at the time... I bet it is not the hardware that sucks, but the darn camera app (or lack of drivers FOR the camera app. Whatever).

On this build, using the HDR Camera+ app I bought for the Gnex (that was the camera app flavor of the month on that phone), and it DOES help here. But it takes 5 seconds to take a picture with it, and moving targets are not as good a subject with it, so it only solves some of the issues.

It is like it cannot focus properly, as the blurring when you zoom in on pictures in even strong lighting are blurry and noisy. Same location taking pics with the Sense cam, and the blurriness is not there. I can see other effects that I could attribute to potential post processing... but the fuzziness is like comparing a not so good 3MP camera to a decent 8MP.

And the bad part, is that I doubt this has the potential to get better. Features I am sure we will get (Zero Shutter Lag, etc) as those are depending on H8, who is doing fantastic work on this phone. But actual camera performance, is slightly worse than the Gnex was, probably due to having to cram the app together to work on all phones. Sure would be nice if we could BUY the Sense Cam from HTC in the app store. Pretty sure they could cram all the dependencies in there and make it work with AOSP, thereby working with all the derivatives. How many apps at $10/each would it take for them to make money on the deal, I wonder.

/wonder mode off. Just ranting because I want it ALL :).
[AT&T, Rogers HTC One X, Telstra One XL] Tinyboss:
Apparently I'm in the minority here (I've never heard anyone else mention it), but what I miss most from the Sense cam is slow-motion videos. I loved playing around with that. Is there any chance we'll see that, ever, in CM10, or in any other camera app that works under CM10?
[AT&T, Rogers HTC One X, Telstra One XL] specter491:
Have you tried setting the focus to auto instead of continuous? Pics look clearer, at least on the phone. Haven't looked on a pc
[AT&T, Rogers HTC One X, Telstra One XL] loraque:
I was tapping to focus, but I did not change that setting. I will give it a shot... if it looks clear on the phone, that is better than what I am getting now.
[AT&T, Rogers HTC One X, Telstra One XL] yungskeeme:
I'll give it a try
[AT&T, Rogers HTC One X, Telstra One XL] big70tom:
First time on cm 10. Love it. The quick reply is wicked cool. The only thing I've noticed is when restarting phone my Widgets don't come back, and my xda premium apparently f/c occasionally now???

What is wake lock? And is the widget thing typical right now?
[AT&T, Rogers HTC One X, Telstra One XL] loraque:
The widget issue is a known problem with 4.1.1. There is link posted in the OP of the CM thread that links to it (Hits my Beautiful Widgets, but oddly if I restore from TitBu and do not upgrade to latest BW, it is stable). Bug with Jellybean. No FC with XDA for me. Try clearing data on XDA app and do-over?

---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------

Did you restore any data with TitBu? Apps+data is fine, but system data on something where the system is so drastically different, will cause errors like you note.
[AT&T, Rogers HTC One X, Telstra One XL] beeroatsnp90x:
anyone notice issues with making calls and the proximity sensor? I have had several people say that I was pressing numbers on the dial pad while during a call because the screen came back on.
[AT&T, Rogers HTC One X, Telstra One XL] dmbro:
I've been experiencing the headset issue (After plugging in a headset it kills the audio until reboot) since like 8/20, now on 9/06 and it is still there! I have tried clean flashing, dirty flashing, flashing clean rom 4.0 then back to cm, wiping everything including external sd, flashing cleanrom 4.0, factory reset, then flashing 9/06. Nothing works! I still have the same headset issue. The issue was supposed to be fixed in 9/04, but I've had no difference at all. 1. Is anyone else having this issue still? and 2. Has anyone successfully fixed it, or know how?
[AT&T, Rogers HTC One X, Telstra One XL] JeepFreak:
H8, I think I see now why you didn't respond to this, because it's YOU who deserves credit for all this work on our camera app, isn't it? Sorry, I didn't realize it before.

One other question, are there plans to include PicSync support in the camera/gallery app? I know we can flash Formula84's gapps package from here: http://rootzwiki.com/topic/31532-gapps-411-424425-jro03o-gapps-package-831/ but we have to choose between PicSync and the CM10 camera. =/

Thanks again,

Billy
[AT&T, Rogers HTC One X, Telstra One XL] TheIncredibleMachine:
Doh! I flashed 0709 this morning, and Swift key 3 lost the plot. Settings crashes when I try to enable it. Cleared data, restored nandroid of 0409, uninstalled and re-installed but it still keeps crashing. Gonna do some searching. Anyone else had this problem?
[AT&T, Rogers HTC One X, Telstra One XL] Mentwar:
This is due to a bug in the CyanogenMod upstream. For now, you need to do the following to connect to LTE:

1. Change preferred network mode to LTE only via *#*#4636#*#

2. Wait until your phone connects to LTE

3. Change preferred network mode to LTE/GSM/CDMA (PRL) via *#*#4636#*#*

You'll need to do the above process again every time you reboot the phone.

Alternatively you can flash my experimental build. I'll write that up in the next post.

---------- Post added at 02:39 AM ---------- Previous post was at 02:27 AM ----------

Hi guys,

I was working on the last few days trying to find a fix for LTE issue, and found a cause and fix. However since I haven't made enough posts to be able to post on the main thread, I'll make a post here instead.

The actual issue turned out to be a combination of two bugs in the upstream:

1) RIL (Radio Interface Layer) ignored request (and substituted a request with another one for WCDMA preferred!) for the network mode to be set to GSM/WCDMA/LTE because enough information wasn't provided

2) RIL didn't properly restore the preferred network mode when rebooted, causing it to fall back to WCDMA preferred

I submitted a fix, along with another change to enable LTE by default, waiting these to be reviewed and merged.

In the meantime, I've made my own build of CM10 with the above fixes. Since I can't post links yet (xda blocks me from doing so until I make at least 10 posts!), please navigate yourself to the issue page (there's a link from main thread OP), go to issue 39 and find a link there.

It'd be nice if you can test this build out and confirm the fix.

P.S. Thanks h8rift and CyanogenMod team for your awesome work!
[AT&T, Rogers HTC One X, Telstra One XL] Dbaker629:
9/8 nightly sound problem

My media volume doesn't work.. I get notification sounds, but while playing music from google play or watching a youtube video, there is no sound output. However, while connected to bluetooth or headphones it works perfectly.
[AT&T, Rogers HTC One X, Telstra One XL] PaKMaN787:
Bug in latest nightly.

Sent from my HTC One X(L/AT&T)
[AT&T, Rogers HTC One X, Telstra One XL] eak1080:
Possible wake-lock fix

I have been messing around with what is causing the wake locks. Running just stock CM10 with no gapps I keep running into android system keeping awake the system. Now when you go to it in the battery settings it says included packages:

Key Chain (Security token authentication built into JB)

Settings Storage (The settings app?)

Android System(???)

Input Devices(???) Internal storage or some hardware device

Settings

Theme Manager

Google backup transport.

Now I ran the 9/8 nightly for a complete 24 hours and I had wake locks all across the board mostly stemming from Android system. End of the day android system kept the phone awake for 3h 54m.

Now last night I used TB to remove Google backup transport and theme manager and since then, all of today (about 8 hours now) and android system has kept the phone awake for 21m 3s.

I may be wrong but could these two packages (I'm thinking theme manager) be causing the wake locks? I would say my usage both days has been the same.

Now I know I don't have facebook and the newest gapps flashed but I wanted to see if the wake locks stemmed from something in the stock rom itself.

Could be nothing but if others want to delete the same packages and see if the wake locks decrease for them also then maybe we narrow down what is causing this. I normally don't post but have been following this and the Dev thread and to me this seemed like a drastic enough difference to point out.
[AT&T, Rogers HTC One X, Telstra One XL] stw303:
Did you delete both 'Theme Chooser' and 'Theme Provider' apps or just one?
[AT&T, Rogers HTC One X, Telstra One XL] eak1080:
Wake locks continued...

So I am almost positive it is something with android system because it is the only thing keeping my phone awake if I check battery in settings.

so I cant post screenshots yet :/ but

phone has been off charger for 13 hours now (screen time is like 30 min, essentially is nothing) and its the packages in android system that keep the wake locks coming. Now normally there is theme chooser and google backup transport in that list but as I stated above I removed them.

with these packages left under android system;

Key Chain (Security token authentication built into JB)

Settings Storage (The settings app?)

Android System(???)

Input Devices(???) Internal storage or some hardware device

Settings

Android system has used a total of 90 sec of cpu time yet kept the phone awake for an hour and a half. Having a data connection (wi-fi or mobile data) seems to increase the wake time of these packages

ex. leave on mobile data and the wake locks increase.

You guys are way more knowledgeable than me when it comes to this stuff but like I said I'm running CM10 stock with no gapps( only apps I have are es file explorer and TB) I'm just pointing out my findings to see if others want to take a look into this. Removing those two packages helped decrease the wake locks but not enough to make a huge impact on battery life. Something in these packages is running/ syncing in the background and keeping the phone from sleeping.

If someone could forward this to dev thread maybe others will take a look into this.

Thanks guys.

---------- Post added at 09:16 PM ---------- Previous post was at 09:11 PM ----------

I deleted theme chooser not theme provider. I just deleted theme provider also and will see if that makes a difference.
[AT&T, Rogers HTC One X, Telstra One XL] toptalent:
Is there any plan to support apt-x (a high quality bluetooth audio streaming codec that's supported by the One X hardware)?

For some of us music lovers who would like to stream via the phone on the go.
[AT&T, Rogers HTC One X, Telstra One XL] redrubberpenguin:
Is anyone else getting weird behavior in the front-facing camera? When I open the camera app and switch to front facing mode the aspect ratio is completely wrong. Been happening since the 9/4 nightly I believe (or whichever one started having the official camera fix).

EDIT: It seems that when you actually TAKE the picture, the aspect ratio is fine, but the picture is horizontally flipped. The aspect ratio is still weird while looking at yourself on the screen using the front camera in the camera app though (it's fine in video chat programs).
[AT&T, Rogers HTC One X, Telstra One XL] buradd:
Does torch high brightness not work for our device? It appears to be the same level of light as the normal brightness
[AT&T, Rogers HTC One X, Telstra One XL] eak1080:
I continued messing around with the wake lock issue with a clean install of the 9/10 nightly. Check issue 106 on the issue tracker on Google code, I posted screenshots to illustrate my point.

Thanks guys
[AT&T, Rogers HTC One X, Telstra One XL] TheIncredibleMachine:
OK so my Swiftkey 3 has officially died. I was on 0409, and it was working fine. Dirty flashed 0909 and it stopped working. When I try to set it up, I download the language pack, then the next step is to enable Swiftkey. When I click on this option and select OK, I get "unfortunately settings has stopped" error. I have cleared data, restored 0409 backup, uninstalled and reinstalled, dirty flashed 1009 and factory reset flashed 1009, tried restoring from TiBU after uninstall, nothing fixes it! Does anyone have any suggestions for how I can get swiftkey to work again? No other keyboard is nearly as good!
[AT&T, Rogers HTC One X, Telstra One XL] rohanjain91:
Go to setting , language and input and select settings from there. I did the same for it
[AT&T, Rogers HTC One X, Telstra One XL] TheIncredibleMachine:
Awesome thank you so much! I had tried different things in there, but not clicking on the Swiftkey 3 dot button.
[AT&T, Rogers HTC One X, Telstra One XL] mcpweev:
Mine doesn't change the level either. My guess would be that is for dual LED devices, someone correct me if I'm wrong? I'm only saying that because I came from the Desire HD, and the flashlight higher brightness would turn on both instead of just one on that phone.
[AT&T, Rogers HTC One X, Telstra One XL] jrodri29:
Is there any way to control the wakelocks the phone has overnight? Litterally my phone spent the whole night without using it. Or is it a work in progress to be solved? Thanks in advance guys
[AT&T, Rogers HTC One X, Telstra One XL] yungskeeme:
I wanted to know the same thing...had to flash Cleanrom v...no major wakelocks..
[AT&T, Rogers HTC One X, Telstra One XL] jrodri29:
Clean rom doesnt have wakelocks at all and when you stop using phone overnight, it gets to that deep sleep

But cm10 still a work in progress and its the closest to jelly bean features, only complaint is the wakelocks but i can live with that
[AT&T, Rogers HTC One X, Telstra One XL] gmmc2:
Swipe up to unlock?

Searched but found nothing... Can you set the lock screen to unlock with a swipe up rather than to the right? Or any direction other than right? I always use my left hand to hold the phone and use my thumb to swipe, and so up or left would be a much more "normal" motion.

I know how to change the slider shortcuts but I don't see any way to add a new Unlock shortcut. Tried all the "Applications", "Activity" lists etc. but nowhere do I see an Unlock action. There's a Face Unlock in the Activities but that only links to setting it up and similar actions.
[AT&T, Rogers HTC One X, Telstra One XL] yungskeeme:
Only one I had was facebook...fixed now so none now
[AT&T, Rogers HTC One X, Telstra One XL] TheIncredibleMachine:
You could use Tasker and setup a Task Cut to unlock. I use one to turn my bluetooth on an off from my lock screen.
[AT&T, Rogers HTC One X, Telstra One XL] gmmc2:
Swipe up to unlock

I'll look into that. Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] dagunshooow:
So I have been able to connect to WiFi at work up until 9-10 and later. Could this be related to the changes made for wireless n connectivity? It is a wep encryption, so I suspect it could be. Thanks y'all!
[AT&T, Rogers HTC One X, Telstra One XL] nyamoV2:
Dumb question. Any reason why I can't get Google voice to work? Says something about unable to forward when I try to set it up for my vmail
[AT&T, Rogers HTC One X, Telstra One XL] Saenzscene:
The wake locks will be there since cm10 is not complete. Something that will be ironed out eventually the further progress is made. I love the ROM too much to change so I just turn my phone off at night and use my tab if I need. Despite the wake locks I get pretty good battery life.

Sent from my One X
[AT&T, Rogers HTC One X, Telstra One XL] mcpweev:
That error is normal. You'll have to activate the number from the google voice web page in the settings I think, I can't remember the exact steps atm. It is explained in the cm10 developer thread somewhere.

Edit: found it, post #1957 in the developer thread, pg 196.
[AT&T, Rogers HTC One X, Telstra One XL] brodie01:
I have a couple of noob questions, I have CM10 0910 nightly installed, everything working great.

1. What is "dirty flashing" the updates?

2. If I want to go from one nightly to another (for ex. I want the mic fix coming in the 0914) cleanly, I don't want to have to re-setup all my email accounts and widgets and re-install everything. Can I use TitBu for that? And if so, can I safely use the "Restore apps and system + data" option?

3. Can I do a dirty flash through goo.im app? I have it installed, just never tried it.

Any help would be greatly appreciated.

Jay
[AT&T, Rogers HTC One X, Telstra One XL] raptir:
"Dirty flashing" is flashing without performing a data wipe.

A dirty flash would do what you want here. Just keep in mind that you can run into some unexpected bugs doing a dirty flash compared to a clean install. Titanium backup is an option as well, but be careful about what you restore. You can run into issues restoring too much through TiBu as well. My recommendation would be to try it and then do a clean install if you run into bugs.

Unfortunately I don't use GooManager, but you can do a dirty flash through recovery. Download the ROM and boot into recovery. Then go into the Wipe menu and only wipte System, Cache and Dalvik Cache, then install the ROM.
[AT&T, Rogers HTC One X, Telstra One XL] al_g:
Adventures in Cyan

I used to love Cyanogenmod on my last phone so I had been waiting for Cyanogenmod 10 to get a little more stable for my AT&T HOX. The other night I decided to upgrade from the clean ROM I was using to the CM10 nightly. All didn't go well, constant crashing and processes stopping. I tried a clean install and things didn't get better. So I RUU'ed back to 1.85 to start over as clean as possible. Since I had already changed my CID to all 1's I was able to unlock the bootloader after a bit of effort where it turned out the fast boot option was messing with it. Then I installed TWRP without any problems. I wiped all three parts and installed the CM10 nightly I downloaded Tuesday night along with GAPPS.

Then I'm stuck at my current problem, for close to 20 minutes I have a spinning CyanogenMod logo and nothing else is happening. If I tap the power button nothing happens. If I hold the power button down after a few seconds the three keys at the bottom start to flash but again nothing else happens. Same if I hold the volume button up or down and hold the power button.

So any thoughts on what I need to do next to get my phone working?
[AT&T, Rogers HTC One X, Telstra One XL] brodie01:
Thanks for the info. However, in 3 you mention wipe system for a dirty flash, would I only do that if I'm doing a full clean flash of the ROM?

---------- Post added at 11:51 AM ---------- Previous post was at 11:00 AM ----------

It may be a dumb question but did you flash the correct version of Cyanogenmod? This happened to me the first time I tried because I accidentally downloaded the ENDEAVORU version. Make sure your ROM is the EVITA version.
[AT&T, Rogers HTC One X, Telstra One XL] al_g:
I've made some progress. Turns out that I just need to wait longer and make sure to hold down the volume first. After the buttons started flashing I waited about 10 seconds and the screen turned off. I was then able to boot into hboot and start up recovery. TWRP confirmed that my zip file was 0910-Evita. I went ahead and download the current nightly and am in the middle of flashing 0913-Evita right now after wiping everything. I then booted into hboot and flashed the boot.img which I extracted from the new nightly zip. Rebooting right now to see what happens.
[AT&T, Rogers HTC One X, Telstra One XL] drunkenbaka:
I was having the exact same problem when I was trying to load cm10 for the first time as well. What I did was manually flash the boot.IMG in fastboot and it seemed to work. Hopefully that helps you out.
[AT&T, Rogers HTC One X, Telstra One XL] theshanthan:
Video camera problems!

I have been running CM 10 for a while now. I am running the version just before the nightlies started. I am hesitant to run the nightlies because I don't understand them. Am I supposed to update everynight? Am I supposed to wait a week and update at once? I am completely lost on this.

I did not have a problem with the version I am running till yesterday. I was trying to record something and the video was completely screwed. I saw three screens in stead of one and there are lines all over these screens. I was doing the blazing challenge and buffalo wild wings and now I don't have video proof of it ;(. I don't want this to happen again. That is why I am thinking of updating to the latest nightly but I don't know the right way to go about it. Please help. And I am sorry for my noobness.
[AT&T, Rogers HTC One X, Telstra One XL] drunkenbaka:
Music Speaker Issue

I've just started using the cm10 nightly files and started with 9/12 and everything works great and looks fantastic but the only issue I seem to be having is the speakers won't play any sound when I try to play music thru google music or youtube. It works when I plug in headphones. And also ringtones and notifications all work. I was wondering if that was a known issue or if there might be a work around for that. Anything would help thanks!

Update-

Well that was odd I was trying to get LTE to work by flashing Cleanrom 4.0de then reflashing 9/13 cm10, it didn't fix the LTE issue but it solved my speaker problem lol kinda odd.
[AT&T, Rogers HTC One X, Telstra One XL] Silellak:
The camera works 100% in the latest nightlies. My suggestion:

1. Keep the ZIP file for the version you're currently on.

2. Grab the latest Nightly (just the latest) and dirty flash it.

3. If everything works fine, you're good. If you have issues, dirty flash back to the version you're currently on. Wait for another nightly and try again.

Nightlies are just that - nightly builds of CM10 with new features and, occasionally, new bugs. Flash them if you want the new features, don't flash them if you're happy with how things are working currently.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Sent you a PM to test something out for me. May or may not have located a way to enable APT-X.