yashsingh1/xdaforums huggingface dataset:
[Windows Phone 8x by HTC] nikc0069:
This is now featured on The Verge, the MS support forums, and I have personally emailed the CEOs of both HTC UK and MS UK.

If anyone wants to read more please head over here:

http://forums.wpcentral.com/htc-8x/200872-reboots.html
[Windows Phone 8x by HTC] gmfeld:
my firmware still not listed on the survey. 1532.20.10012.502

My 8X has never rebooted.
[Windows Phone 8x by HTC] nikc0069:
I have added your firmware version.
[Windows Phone 8x by HTC] gmfeld:
What is IPv6? Where do I find that to answer that question?
[Windows Phone 8x by HTC] nikc0069:
It is set when you manually set up an APN. If you can't edit one that was automatically set up then it won't be available. I'll add a "Not Sure" option shortly and post back here.
[Windows Phone 8x by HTC] nikc0069:
Added
[Windows Phone 8x by HTC] Narathan:
Added to survey. But I have no reboots or performance issues. From the Netherlands (KPN)
[Windows Phone 8x by HTC] nikc0069:
Thanks, info of people that don't have reboots is also useful as it gives us a control.
[Windows Phone 8x by HTC] PhilAd:
im using my htc 8x for almost 3 weeks´now. there was no reboot and no Crash in the meantime.
[Windows Phone 8x by HTC] mizmo.lu:
The lumias have the reboot Problem too, so this survey is pretty useless. I' m pretty sure it has nothing to to with 8X firmware. Vor most people it helps to switch to 3G, 2G or add a manual APN.

Sent from my Lumia 920 using Board Express
[Windows Phone 8x by HTC] Krakos:
In my htc8x there was not any reboot, but i have some battery "problems". Sometimes the % go down quickly, almost 15% per hour, but the phone is cold, is not hot as we expected because of high use of the processor, later i connect the phone to the charger and charges around 40% in five minutes, that is not possible so i have one theory about that: the software that controls the % need a fix, it tells you that you are loosing battery but that is not real
[Windows Phone 8x by HTC] TheGardner:
added!
[Windows Phone 8x by HTC] Narathan:
I have to take back my words. I've had two reboots this week:

- While listning to music

- Unlocking lockscreen

I *do* remember having run some 7.5 app before the reboot. But I read MS is dispatching a ota hotfix in December, so here's hoping :victory:
[Windows Phone 8x by HTC] jValdron:
Had the phone since yesterday, didn't get a reboot yet.

Firmware not in survey, got firmware 1532.20.1006.666 with Bell/Aliant in Canada. Bootloader ain't in the survey either, I'm running 0.0.1532.20(156287).
[Windows Phone 8x by HTC] elvisr77:
I don't have any of the versions of Firmware or Bootloader shown on the survey. Can you please add this to your survey?

T-Mobile (US)

HTC 8X

Firmware: 1532.20.10006.531

Bootloader: 1532.20(156382)

Thank You
[Windows Phone 8x by HTC] thehustler:
My phone's Firmware and Bootloader versions are not available in your list. They are as follows

Firmware - 1532.20.10021.707

Bootloader version - 0.0.1532.20(157808)

I am in India and bought my device over here. No random reboots for me as of now and it's been 2 weeks since I bough the phone.

Edit: Attaching screenshot for full details.
[AT&T, Rogers HTC One X, Telstra One XL] churraman:
Hi. I searched the forum but could not find a similar thread, so sorry if this has been covered in the past.

I currently have a ATT Galaxy S2 and I bought a HTC One X (ATT Version) on ebay that I should receive next week. The sim card I currently use in my GS2 is the 3g/LTE version and I know this because I have the original packing of the sim card and it says 3G/LTE. So when I get my One X I have to cut my sim card to fit the One X. Is this all I have to do since my sim card is LTE ready or do I have to contact ATT to change something in my data plan to LTE? Will my monthly rate increase because I'll be using LTE ( I think not, but just want confirmation)?

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] NYConex:
You are probably going to have to change your plan to some late plan.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
You need to call AT&T and add LTE to your account. There is no change.

Also, if you buy the phone from AT&T, it will include a micro SIM. No need to cut one.
[AT&T, Rogers HTC One X, Telstra One XL] burton813:
You will want to grab a new sim. If the sim card number does not match up as lte micro sim it won't let you add the lte plan on your account
[AT&T, Rogers HTC One X, Telstra One XL] atermify:
I didn't have to buy a new sim to get the lte plan. I just cut my sim, called at&t and got lte added. They may have changed protocol or something, but I didn't need to.
[AT&T, Rogers HTC One X, Telstra One XL] ahugo68:
The sims are the same. Just different size. If you go to a corporate store they are free. I work at one and we are always glad to to change a sim and make sure your plan is provisioned properly. (Was a big rooter/android fan since the g1 which inspired me to work for att)
[AT&T, Rogers HTC One X, Telstra One XL] PeartFan40:
Please keep all question threads in Q&A only.

Thank You.

Thread Moved.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"If you choose not to decide, you still have made a choice"
[AT&T, Rogers HTC One X, Telstra One XL] burton813:
If the sim card serial number ends with 2 5 or above on the 9th and 10th digits, you are good to go
[AT&T, Rogers HTC One X, Telstra One XL] superchilpil:
Ohh no now att is spying on us
[AT&T, Rogers HTC One X, Telstra One XL] area51avenger:
Att tech support is illiterate?
[AT&T, Rogers HTC One X, Telstra One XL] superchilpil:
Thats what i was thinking....
[AT&T, Rogers HTC One X, Telstra One XL] WeWearFedoras:
This explains so much...
[AT&T, Rogers HTC One X, Telstra One XL] burton813:
I work for them only :/ , and no need to be a twat becuase i miss typed a few words
[Samsung Galaxy Nexus] primetimelive:
Just trying to see what people who've used both keyboards think of the two.

Google's implementation seems to be good for a first iteration, but it lacks the convenience features that Swype has such adding punctuation by swiping from the punctuation mark to the space bar. Also accessing a numeric keyboard in Swype by swiping from the Swype key to the number 5 on the keyboard.

Still going to try the 4.2 keyboard for awhile, but I hope Google can add a bit more polish to the built-in keyboard
[Samsung Galaxy Nexus] fushla:
4.2 keyboard. It's a charm.. <3
[Samsung Galaxy Nexus] zaiuss:
i personally like the swype keyboard a lot more.

the google keyboard doesn't have the ability to "swype" punctuation, like periods, commas, exclamation marks. instead, you need to hold down the "period" button to bring up the other punctuation marks.

also, if i "swype" "I <space bar>" it shows up as "in". it doesn't recognize the spacebar.

the swype keyboard also looks more cleaner.

i tried using the google keyboard for a day. i gave up on it.
[Samsung Galaxy Nexus] Winesnob:
Love the new swype keyboard. Took some time to fully adjust but finding much easier when using one hand.
[Samsung Galaxy Nexus] zephiK:
Neither. SwiftKey x for me still. Way too many mistakes using 4.2/swype
[Samsung Galaxy Nexus] srt4mn:
SwiftKey 3 for me. Works great.
[Samsung Galaxy Nexus] daewond3r:
I've been a huge fan of Swype since it's arrival, but I'm going with the 4.2 gesture keyboard from here. I feel like it's a lot smoother. Even on my GN running CM10 Swype can get hung up sometimes. I do miss how Swype handles punctuation, but I assume Google will work that in soon. I also prefer the stock look.
[Samsung Galaxy Nexus] pekinesis:
Swype is better !
[Samsung Galaxy Nexus] nigelw:
Been using Swype for quite a while, but I'm impressed by how good the 4.2 keyboard is. I find it more accurate than Swype and quicker than the swift key I was using previously.
[Samsung Galaxy Nexus] jrkelley14:
I agree. I never really got used to swipe but 4.2 works well enough I think I could get used to it pretty quickly.
[Samsung Galaxy Nexus] raymond4:
Swype is the only keyboard for me I tried every single keyboard but I keep coming back to Swype.
[Samsung Galaxy Nexus] primetimelive:
I do miss the way that Swype handles punctuation. I actually do it using the 4.2 keyboard and I end up making different words in my sentences.

Hope Google finds a way to make punctuation more seamless with this new keyboard.
[Samsung Galaxy Nexus] albsat:
Swype because it has more languagr support
[Samsung Galaxy Nexus] crixley:
swype because you can tap on a word to fix it afterwards (like if you ntice it ater typing a big paragraph), with 4.2 keyboard you have to delete the word and retype it.
[Samsung Galaxy Nexus] T-Keith:
I like 4.2 a lot more than swype, but I'll probably end back up and swiftkey. It has a lot of extra features that are hard to live without .
[Samsung Galaxy Nexus] onyx00:
The auto-spacing on Swype seems to be quite messed up for some time now, which is utterly annoying. I find autospace fails to work in many browser windows, but works fine with SMS, e-mail, etc.

So I switched to the Google 4.2 keyboard, but the downside there is I find it makes lots of errors the faster I go using gestures, which is also annoying.

:(
[Samsung Galaxy Nexus] g8who:
I've used the google gesture keyboard for about 4-5 days straight now and I can definitively say Swype is more accurate. Also Swype picks up names from your contact list which can be really nice if you have a large contact list. In general, using the google keyboard you need to be much more precise. Punctuations are easier for swype and correcting a word is easier in swype as well. Good first try for Google but I'm switching back for now.
[Samsung Galaxy Nexus] thas5:
Tried the 4.2 gesture keyboard, but I prefer Swype for now. Like others have said, you can easily put in punctuation with Swype. It also seems a bit more accurate in its predictions.
[Samsung Galaxy Nexus] viskon:
Swype for me is more accurate . But the auto spacing is messed up in the browser. Sticking with the stock keyboard for now.
[Samsung Galaxy Nexus] Marisa:
I had been using Tasker to change my keyboard depending on orientation. Swype was just easier to do one handed portrait mode typing with, but I never liked using it for two handed landscape.

I still find myself occasionally trying to use Swype style commands, but I'm losing those habits quickly. While it's a bit of a nuisance to use some punctuation, periods are just a double tapped spacebar away. I never memorized where they were on Swype, so having them all in one place is pretty convenient for me.

Swype's system for correction was pretty nice, but I almost always found when it got it wrong the first time, all the corrections it offered were still off anyway. I was already retyping most things anyway, so it wasn't a big loss

All in all, I like both. However, Swype doesn't offer me enough of a reason to install it when Google's offering covers my needs.
[Samsung Galaxy Nexus] Soldier 2.0:
Swift key is working on a new version that sports swype gestures
[Samsung Galaxy Nexus] smallvan:
I had used Swype back to the time HD2 n DHD. Now I am happy with the 4.2 keyboard. However, the Swype on inputting double alphabet on a word, like week, sleep n etc, is better. See if 4.2 keyboard can make improvement on this.
[Samsung Galaxy Nexus] Chrono_Tata:
Definitely Swype. The recognition algorithm is much better and the newest beta has a lot of neat features like changing the case of an entered word and shortcuts for copy-pasting.
[Samsung Galaxy Nexus] earlyberd:
I use the stock 4.2 keyboard because I hate the appearance of Swype. It doesn't match the Android UI at all, and the themes are even worse. The best thing to ever happen to Swype was the user-created themes, but instead of supporting us they issued C&D orders.

Honestly Google's keyboard is not quite as good in terms of prediction, accuracy, and features, but at least it's a part of AOSP and thus will allow devs and artists to customize it to their heart's content.
[Samsung Galaxy Nexus] AdamUpNorth:
Really like the new 4.2 keyboard but the deal breaker for me is that the swipe feature on the 4.2 keyboard is disabled on the android password screen. You have to push each button (traditional style) which take way too long.... And more annoying when you have a 10 minute forced lock policy due to company security requirements.
[Samsung Galaxy Nexus] MuT7:
I prefer swype, but has anyone experienced ridiculous lag when using swype recently? I've had to wait a good 30 seconds just for the keyboard to pop up =/
[Samsung Galaxy Nexus] primetimelive:
I thought I could use the 4.2 keyboard a bit longer, however I think I got used to all the nuances that the Swype keyboard has going. I definitely can type way faster than the usual tapping or Swiping that the 4.2 keyboard offers and that includes punctuation.

Hats off to Google for implementing such an innovative way of typing using a touchscreen. Hope they work on it more to polish it further for the next update.

That being said, it might be Key Lime Pie before we see changes or additions to the default keyboard.
[Samsung Galaxy Nexus] altimax98:
I prefer the 4.2 keyboard after using Swype for years for 2 main reasons... The first is the native speech icon is ready to get to. I hate using dragon go. Items slow and for me quite inaccurate, whereas Google works very well for me. The other reason is that the 4.2 keyboard handles tapping much much better. My largest gripe with swype was the lack of real good tapping for typing. It was like swype or nothing and it sucked.

That said the Google keyboard has a ways to go. It needs much better recognition to be used primarily
[Samsung Galaxy Nexus] Zzz73:
I thought I was the only one. I am getting this crazy lag the first time I try to bring up Swype after a reboot. after I get it to go that first time, it's good. pops right up. but that first time after a reboot... I'd say it's more that 30 seconds for me.

JBSourcery ROM

Xi kernel (but also happened with Trinity)
[Samsung Galaxy Nexus] -star-:
Good to see that google improves the Keyboard but I'm still missing some swype and mainly swiftkey Features like the prediction. If they put in some of the other Features it would be a great alternativ.

So I'll stay with SwiftKey/ Swype.
[Samsung Galaxy Nexus] Zzz73:
I was really looking forward to 4.2 AOSP KB w/ Swype-like input, but I have the same complaints/observations the other users found. you can't go back to an incorrect word earlier in a sentence and get predictions and punctuation is a pain. but major complaint about about Swype, you can't smoothly go to Google voice typing (stuck with Dragon *gag*) I'm sticking with Swype for now.
[Samsung Galaxy Nexus] kyokeun1234:
I personally use 4.2 just for the fact that the look suits the OS really nicely but Swype not only doesn't suit the OS well but also look ugly in my opinion. Accuracy feels about same on both but I will say that Swype has more features. (No surprise)
[Samsung Galaxy Nexus] resynx:
I use the 4.2 keyboard due to convenience, but Swype's prediction blows it out of the water. It's to be expected though since 4.2 is new.
[Samsung Galaxy Nexus] SahilC:
Trust me. Wait for SwiftKey Flow. It'll beat the crap out of everything else :D
[Samsung Galaxy Nexus] Zeinzu:
4.2 keyboard. Though, I'm use to minor differences from having used swype. I need to retrain myself to stop doing swype function habits.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
YES! Forgot about that beauty! I even signed up for the notice like three times :p
[Samsung Galaxy Nexus] codfos:
I had Swiftkey for a few months when went back the stock. Then I tried Swype. Had that for like 6 months. Now I am back on the stock 4.2 with swipe and I like it way more than Swiftkey and Swype. It they just didn't have the "android" feel. Its the same for third party messaging apps too. I just like the way it looks so much better, it fits in.
[Samsung Galaxy Nexus] peadarog:
It is possible to go back and correct using the 4.2 keyboard, although it's not as handy as swype. Double-tap on the word you need to fix and then hit "replace". This will bring up a list of alternative words.

Yes, it's three taps instead of one, but it's better than having to retype the whole thing!
[Samsung Galaxy Nexus] apratomo:
SwiftKey for me, until they could support multi language at the same time (no need to switch for languages)

Also SwiftKey has better prediction
[Samsung Galaxy Nexus] psycho2097:
Swype most certainly...it's way way way better.but it's kinda laggy sometimes, which is why I preferred the stock keyboard for a while, but the tipping point for me is the inclusion of hinglish language in Swype. I m Indian n like 90% of Hindi speaking Indians, like to type Hindi in English script, and the inclusion of hinglish dictionary is godsend for me.. Just my 2c. Otherwise the stock keyboard is great, no complaints.

Sent from my nexus
[Samsung Galaxy Nexus] wuodland:
The new keyboard is well done IMO. will use it over any other keyboard. Although sometimes the mistakes it makes gives me a headache.
[Samsung Galaxy Nexus] sbodyontheweb:
i had doubts on the new keyboard until i try and adopt it :)
[Samsung Galaxy Nexus] EvilDobe:
Just tossing in my .02....

SwiftKey sucks. I really tried to use it and like it but just doesn't fit how I type/text. The predictive text in SwiftKey is, more often than not, wrong and slows me down when typing.

The 4.2 keyboard is all right. I've been using it so I could compare it to Swype. Again the predictive included is wrong and slows me down when typing. It is less wrong than SwiftKey is but it, for my purposes, is more functional than SwiftKey.

Swype is the bees-knees. That is all.
[Samsung Galaxy Nexus] ManMOuntain:
I prefer using Swype :)
[Samsung Galaxy Nexus] Sailor Saucy:
I'm a SwiftKey man. My main problem with the stock keyboard is one button for every punctuation mark - what were they thinking? I use a lot of punctuation and I'd at the very least like a separate key for commas and full-stops.
[Samsung Galaxy Nexus] defconoi:
Id use swype but it consumes too much Resources. Hope the stock keyboard gets improved even more, it sucks typing URLs via stock swipe keyboard because of the auto swipe
[Samsung Galaxy Nexus] ohiomoto:
I like 4.2 also.
[Samsung Galaxy Nexus] inorde:
Cool I have SwiftKey at the moment but it's only marginally better than the already very good stock keyboard on 4.1.2
[Samsung Galaxy Nexus] ZeroMuch:
I'm really looking forward to the new Swiftkey, too. I appreciate the 4.2 swiping, but it's Swype for me because I cannot get the 4.2 keyboard to recognize my own name properly. The lack of ease in punctuating is also a pain. I just hope the Swiftkey swiping keyboard will rock as much as we all hope it will.
[Samsung Galaxy Nexus] SilentStormer:
4.2 keyboard simply because of the live prediction which really makes it better than swipe where you are just hoping that it predicted the word right.

Overall, Google did a great job with the 4.2 keyboard and it's the thing I use most from 4.2.

Sent from my Jellin Gnex
[Samsung Galaxy Nexus] zAlbee:
I use Touchpal Curve (free), on a friend's recommendation. Otherwise on my tablet, the stock ASUS keyboard also has swipe-functionality. ASUS is more accurate, but has an annoying restriction that swipe doesn't work in browser's location (URL) bar. Haven't tried the big name ones.
[Samsung Galaxy Nexus] ampersand38:
Swype predictions have s nice feature that will ignore misspellings. For example if I am swyping "ampersand" and hit a-m-e by mistake I can simple go back on track with p-e-r-s-a-n-d, and it will still work. Where as the 4.2 keyboard is very unforgiving of this type of mistake.
[Samsung Galaxy Nexus] :
4.2
[Samsung Galaxy Nexus] rtega:
Keymonk is quicker than all the other alternatives though it still needs extra languages and needs some more work on accuracy.
[Samsung Galaxy Nexus] MikeyMike01:
I found swype to be more accurate, but Google's offering to be better looking. I give the edge to Google.

Sent from my iPhone
[Samsung Galaxy Nexus] johnhimm:
Anyone have the link to the 4.2 APK? Not the leaked one but the newer one?
[Samsung Galaxy Nexus] coop3r:
Try to install apk or flash zip from here: http://xdaforums.com/showthread.php?t=1964728

It is for Nexus 7 I guess, but I flashed a zip on my Gnex 4.1.2 and it works perfect.
[Samsung Galaxy Nexus] yogi167:
Tried using 4.2 but I just like the bigger keys on swype.
[Samsung Galaxy Nexus] SahilC:
I just can't wait for SwiftKey Flow :(
[Samsung Galaxy Nexus] biggiestuff:
I use the 4.2 because it's less of a resource hog. Swype is more accurate at this point in time and the dictionary synced across multiple devices is something that I actually use but right now i'd prefer my resources being freed and hope that they improve the 4.2 keyboard as time goes on. I also like using 4.2 because the mic button goes to the default google voice typing and not the dragon Go from swype. From what I saw Swiftkey h as that capability now to. I might give it a try when swiftkey gets their gesturing going as well.

Makes me wonder why Swype didn't patent this style of typing. Has it been around before? Might be a bad sign for Swype if their competitors start offering it as well.
[Samsung Galaxy Nexus] Blown 89:
4.2 keyboard is much more accurate in predicting words than Swype. I miss the tap to correct and punctuation in Swype but the time saved using that is wasted correcting Swype's bad predictions. Swype is also laggy at times. For simplicity's sake I'm sticking with 4.2.
[Samsung Galaxy Nexus] RoadHazard:
The "swype" functionality of the 4.2 keyboard works amazingly well for me, I'm very impressed (and I'm also glad I finally have the option of actually using the stock keyboard - it never had a Swedish dictionary until now). However, I'm greatly annoyed at how long it takes for special characters to appear when long-pressing keys. For example, to write one of the very common characters '!' and '?' you have to long-press the period key for a full half second, which is just way too long. All other decent keyboards let you customize the long-press delay (I personally like it at about 200-250 ms). This one doesn't, and that's a major shortcoming for me.
[Samsung Galaxy Nexus] addicted2088:
Swype. Gesture Typing is good, but there are multiple annoyances in the stock keyboard that irritate me:

1. It doesn't understand that there should be no space between two swiped words in fields where we enter the email address or stuff like that, like when setting up a new account.

2. It doesn't allow swiping in password fields, also no word suggestions in fields like the browser address bar.

3. Doesn't allow swiping over the full stop button to make words like I'm or don't or wouldn't, quite a few times we gotta select the correct word from the suggestions.

4. Too sensitive for swiping. That sensitivity is great for normal typing, but horrible for swiping.

5. Swype has the advantage of having much more not so general words, like quad-core, noob, etc, no such thing on stock keyboard.

6. Stock keyboard only shows three word suggestions for any swiped word, rest come after long pressing on one of those suggestions.

7. And why the hell are there no symbols like ? or * etc on the letters themselves. So silly to have to go into a separate menu each time or long press on full stop button. SwiftKey has them too, Google is probably leaving them out for a clean look on the keyboard, but it's un-intuitive (though the Nexus 7 has them in 4.1, but not on 4.2).

In short, if you are more a fan on normal typing and just want swiping functionality, the stock keyboard is great. But if you're a Swype pro or intend to mainly swipe for typing, Swype is just so much better. Of course, just my opinion, but that's what I think.

That's a pretty long list of inconveniences in the stock keyboard for me, which wouldn't annoy me if I hadn't used Swype for more than a year now :P And no knowing when, and if, Google will update it any time soon, unless they put it on the Play Store like Calendar for faster updates. Hoping SwiftKey's Flow comes soon, I'd much prefer that keyboard with swipe.
[Samsung Galaxy Nexus] hardmanbdn:
I prefer swype it's more accurate for spanish,