yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] AndreaCristiano:
Well it does not have the 1700mhz frequency just look at the Motorola site it shows LTE bands for the dev edition as 700 and 1900
[Moto X Q&A] KiNG OMaR:
The 1700 band is for TMO's HSPA network.
[Moto X Q&A] zabolots:
So from all the responses thus far, here is what I can come up with:

- Both the GSM Developer Edition and the T-Mobile version are model XT1053

- The T-Mobile version definitely supports T-Mobile's 1700MHz HSPA+

- According to Moto's Developer Edition page, it does NOT support 1700MHz band

So, is it really likely that there are two different versions of the XT1053, one of which has 16GB and supports T-Mobile's 1700MHz HSPA+ and another which has 32GB but does NOT support T-Mobile's 1700MHz HSPA+?

If only there were somebody here who actually owned a Developer Edition AND used it on T-Mobile in an area that hasn't been refarmed...
[Moto X Q&A] AndreaCristiano:
Developer is xt1058 and it does not support 1700mhz its in black and white on the developer phone page on Motorola's website
[Moto X Q&A] sleepyguy007:
do you have one?

it says here

http://www.motorola.com/us/Moto-X-Developer-Edition-GSM-Networks/moto-x-developer-edition.html

its supports 3G UMTS AWS. and it supports the same exact LTE bands as the tmobile one too. sounds like an XT1053 to me.
[Moto X Q&A] AndreaCristiano:
Ummm where do you see 1700 mhz
[Moto X Q&A] sleepyguy007:
AWS is 1700 upload, 2100 download. it says AWS there.

1900 is PCS 3G like at&t. 2100 is UMTS in asia for a lot of places. AWS is wind mobile / t-mobile .
[Moto X Q&A] twa_priv:
No, the GSM Dev Edition is XT1053.
[Moto X Q&A] mohlsen8:
yeah I just said this too earlier on page 2. I can't believe there's this much "debate" going on about this. its the same model. Motorola isn't lying to us and creating multiple xt1053 models that vary in bands.. that's what model numbers themselves are for. this is a crazy thread.
[Moto X Q&A] zabolots:
I believe this confusion is due to a couple of factors:

- There are two different Developer Editions, CDMA & GSM, with two different model numbers, XT1053 (GSM) and I believe xt1060 (CDMA)

- The Motorola site lists the specs differently on their pages, with some showing actual frequencies supported (i.e. 1700MHz), while others show only signaling technologies (LTE, HSPA+, etc)

The whole reason I started this thread is because I wanted to be sure that the GSM Developer Edition supported all the T-Mobile bands. I'll be damned if I'm going to pay $650 and continually fall back to EDGE data for cryin' out loud!

I agree with what was said that the supported bands are what differentiates the different model numbers, so at this point I have to believe that both the T-Mobile edition and the GSM Developer Edition are XT1053 models with the same frequency support.

After all this, all I have to say "Shame on Motorola". It shouldn't be this hard.
[Moto X Q&A] mohlsen8:
Yeah, no worries, it would be nice if they'd make it very clear to avoid this kind of confusion. I'm sure they wouldn't have a problem accepting a return if it didn't actually work for you for some reason (or hell, if it turns out that we're all wrong). To be honest, I'm on my second moto x due to physical defect crap and I'm about to return this one. While very frustrating, they've at least been very helpful and receptive to taking a return as well as offering warranty evaluation/repair - even though the first thing I did was unlock the bootloader on the first one. They get a gold or at least silver star in my book for the customer service dealings I've had. Now if they could just ship me a perfect phone (and admittedly after the first one had stuff wrong with it, it's hard not to nitpick and over-examine everything).
[Moto X Q&A] sleepyguy007:
Fairly certain the verizon Dev edition is xt1060 to whoever said it was xt1058 which is the rogers/americamovil/att one
[Moto X Q&A] mohlsen8:
yes, Verizon Dev version = xt1060 = Verizon version.
[Moto X Q&A] ardoreal:
Please allow me to clarify, I bought the developer edition and mine is the XT1053.

I took it to an area that is known to only have T-Mobile 1700MHz AWS. My phone has "4G" marked in that area, in the system info I showed hspa+:15

On a speedtest I was getting around 28mbps. I'm thinking I was getting DC-HSPA+ there and their backhaul was just not giving me the 35-40mbps you should get from DC, but, I can't complain. I know for a fact that this area only has the AWS 1700MHz because I had my wife with me on her iPhone 5 A1429 model that only supports the UMTS 1900MHz 3G.

So.....to end the debate...THE XT1053 DEVELOPER EDITION GSM MOTO X DOES SUPPORT TMOBILE AWS 1700 3G!!!! (er....4G....if you fancy that).
[Moto X Q&A] AndreaCristiano:
Hey man its only confusing because the Motorola site doesn't really tell you. Us T-Mobile people do not want to shell out 650 and then be stuck on edge ya know.
[Moto X Q&A] ardoreal:
Yeah I hear that, the site does a pretty poor job of conveying the 1700mhz aws. It does say "AWS" but that's it, it can be confusing as there's an AWS 1900 spec.
[Moto X Q&A] AndreaCristiano:
exactly and it shows the 1900 not the 1700 so its even more confusing
[Moto X Q&A] Droyyd:
They're both XT1053 and should be identical phones if I'm not mistaken.
[Moto X Q&A] RorixRebel:
i have the dev gsm edition and i'm on t-mobile,

what do you want me to check?
[Moto X Q&A] AndreaCristiano:
do you fall back to 4g when you're not in LTE or do you see edge?
[Moto X Q&A] RorixRebel:
i am actually trying to find a network mode besides 4G, can't seem to get out of that band - battery is going dry with that 24/7.

wanted to force my way to 3G but it doesn't work
[Moto X Q&A] AndreaCristiano:
where are you using the phone?
[Moto X Q&A] RorixRebel:
home, office, pretty much everwhere.

and i can't get rid of the 4G icon at the top, unless of course i shut the mobile data off.
[Moto X Q&A] AndreaCristiano:
I meant where as in town/ city ? Do you see LTE?
[Moto X Q&A] RorixRebel:
Yep LTE everywhere, apparently in San Antonio we got a pretty good coverage with TMobile

i do notice that bars go up and down every now and then but as far as i know it should be switching between 3g, HDSPA,EDGE, LTE, etc.

At least it did that with my S3.
[Moto X Q&A] AndreaCristiano:
Very cool. Good to know
[Moto X Q&A] RorixRebel:
knowing that, could it be possible to toggle between 3G and 4G?

haven't seen the icon change to something else besides 4G
[Moto X Q&A] ardoreal:
On TMo stuff you're not going to see it change 4G states when going from LTE to HSPA+ especially if you're on DC-HSPA. They market their HSPA+ as "4G" since 2010.
[Moto X Q&A] AndreaCristiano:
Actually not true. Its 4G or 4G with a little LTE under it so their is a difference
[Moto X Q&A] RorixRebel:
I didn't notice that part, but yeah the little LTE comes every now and then.

Will keep an eye out for that part and location.
[Moto X Q&A] AndreaCristiano:
Very cool. Keep us up to date :)
[Moto X Q&A] RorixRebel:
So yeah i will never see the 3g icon but it is somehow there.

Guess I'll miss that icon.
[Moto X Q&A] moises1204:
hello everyone, can someone owning a t-mobile moto x tell me if it has wifi calling please?
[Moto X Q&A] jhernand1102:
No it does not have wifi calling.
[Moto X Q&A] banboy:
Moto x most issue, for Tmobile version ?

is your t-mobile version ever happened or felt like this ?
[Moto X Q&A] moises1204:
thanks.
[Moto X Q&A] DoogieDC:
Take a look at this table that compares the specs of the GSM Dev Edition, TMo version, and the AT&T version:

http://bit.ly/18EM5nX

FYI - I have the GSM dev edition and swap my T-Mobile and AT&T sims all the time. I get 3G and LTE on both. I am in Washington DC, which is a refarmed area, so I can't personally vouch for 1700MHz experience.
[Moto X Q&A] sleepyguy007:
I had both a claro xt1058 unlocked and a tmobile xt1053 in Los Angeles which is refarmed. The xt1053 still had 4g more often. Not every tower in a refarmed area is pcs yet as they have to leave some aws hspa up for older phones for a while. Like the nexus s t mobile edition for example can only have aws hspa... It has no pcs 1900 hspa support. So better to get dev edition or T-Mobile even in a refarmed area
[Moto X Q&A] CollinFX45:
I have absolutely nothing to add other than I LOVE your homescreen! Awesome :)
[Moto X Q&A] AndreaCristiano:
Gsm Dev edition here on T-Mobile and yes it has the Aws
[Moto X Q&A] RorixRebel:
What speeds are you getting on Lte brother?
[Moto X Q&A] AndreaCristiano:
speedtest this am was a ping of 46ms download was 30.10 Mbps and upload 10.01 Mbps
[Moto X Q&A] RorixRebel:
nice!

and i can't get past 8mbs guess my zone ain't fully 4G yet :(
[Moto X Q&A] AndreaCristiano:
Yes it's probably the back haul which hasn't been redone
[Moto X Q&A] christoman:
Just to confirm, the consensus is that the TMo model sold through Moto is the same as the DE, but with only 16GB and a locked bootloader? I am looking for a phone for my wife (switching from VZW) and want the flex of either TMo (this is my preference) or AT&T if it doesn't work out. Has anyone successfully swapped SIMs in the TMo version and got all the bands on AT&T?
[Moto X Q&A] phositadc:
Yes the T-Mobile version works 100% on ATT. LTE and HSDPA.

Sent from my Nexus 7
[Moto X Q&A] thechilipepper:
If the T-Mobile version works on the AT&T service, then why is there a different model number for it? Do they not have the same bands? I ask because I am currently on AT&T and would get it through them, but may want to jump ship to T-Mobile at some point. I would want full HSPA+ and LTE support on both.
[Moto X Q&A] phositadc:
The T-Mobile one has more bands... Including aws HSDPA. It gives full LTE and HSDPA on both. The at&t version does not have full HSDPA on T-Mobile.

Sent from my Nexus 5
[Moto X Q&A] raydi07:
I have the gsm developers edition running on ATT and in my town, Clarksville TN ATT uses 850 for LTE. I don t get LTE service on the moto x. !0 miles down the road It is the 700 LTE band and I do receive LTE service. So the question is whether I can add the 850 freq to this phone?
[Moto X Q&A] Steve-x:
Can't be done, the hardware is different. To get LTE in your specific case you'd need the official AT&T Moto X, model # XT-1058.
[Moto X Q&A] raydi07:
well, thats not what i expected from the developers edition. Why would they not include all the freqs for both att & tmobile?
[Moto X Q&A] Steve-x:
A good question. I assume it is related to a hardware limitation of some sort. The XT-1058 offers the best band support of all Moto X models if you don't need one specific band/modulation combo, that is WCDMA(HSPA) on band 4(AWS) which is needed for tmobile support in the US or Wind Mobile/Mobilicity in Canada.

I was going to get myself a tmobile 32 gb but decided in my case I was better off with my Rogers XT-1058, no branding, sim unlocked, bootloader unlocked and it supports the most possible bands for when there is further LTE expansion in Canada.

I guess they just had to the pick the model that would work for the majority of the users in the US to use as the Developer Edition, that is the XT-1053.
[Moto X Q&A] WCH_Chip:
Unfortunately the T-mobile and Dev Edition Moto X's don't support Band 5 LTE (850Mhz). That is why you don't have LTE.
[Moto X Q&A] rockingondrums:
Sorry buddy, but the wireless industry and it's bands/frequencies/various technologies is a serious cluster f*. "Developer Edition" doesn't mean jack squat in terms of hardware because of this (other than leaving out things like eFuses or whatever they're called) and ESPECIALLY now that LTE is widespread. It means a whole lot on the software side, however. You'll notice if you take a look at pretty much every cellphone on earth that it's the same way. The only phone I know of that will work on all four major US carriers is the iPhone 4S. They bothered to cram all necessary radios in. HOWEVER, these were ONLY 3G bands (4G on anything earlier than a iPhone 5 is a LIE). When the 5/5S came out, they ended up in the same position as everyone else. SKUs all over the place. Won't change unless the industry changes. And the wireless industry... Think of the word "entrenched" and multiply it by 1000. Carriers are worse versions of the RIAA and MPAA.

I do like the direction T-Mobile is going in. Compared to way everything has been, it's a breath of fresh air.

They might've researched on whether or not they could make a truly global phone, but maybe they weren't happy with the physical layout the interior of the phone would've had to take, or the resulting cost. A lot goes in to phone design. It probably wasn't cost-effective.
[Moto X Q&A] chirpa12:
I can confirm the T-Mobile version is sim unlocked right out of the box and I was able to get the kitkat OTA while on AT&T.
[Moto X Q&A] r_diaz13:
Mine too.. works great. I didn't even have to mess with the APN, they automatically popped up and everything works great. Does your data signal ever say LTE? Mine only says 4g all the time. Just curious..
[Moto X Q&A] chirpa12:
Yes it does. I heard that if you don't have LTE access then you have to contact At&t to allow it for your sim? I didn't have to do that because I just cut my micro sim down to nano size. What did you do?
[Moto X Q&A] r_diaz13:
Rocking the new Moto X

Woop Woop

---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------

I just went to the store and they gave me a nano sim. Dropped it in and it's been gravy ever since I'll call customer support tomorrow to get set up for lte cuz I must not be getting it then. I only see 4g

Rocking the new Moto X

Woop Woop
[Moto X Q&A] college4sure:
4G speed test

To prove the 4G capabilities of the moto x Dev edition - check this out from Irvine on Tmobile. Pretty impessed thus far.
[Galaxy S 4 Q&A, Help & Troubleshooting] thx1200:
I'm having the exact same problem since 4.3 and found multiple articles offering suggestions about how to find services that might be holding /data open, but I have had no luck. Did you figure out a way to do this?

There is this...

http://code.google.com/p/android/issues/detail?id=58073

And I did the losf trick and the thing is that there are no open files, so what else could be holding the partition open?

Is there any other way to do encryption other than the UI or cryptofs?
[Galaxy S 4 Q&A, Help & Troubleshooting] avah:
The issue is still present and I haven't managed to enable encryption. Haven't done much debugging either, though. I did try to run the command

while true; do echo; lsof | grep /data; sleep 0.2; done

as root while trying to encrypt the phone but it didn't reveal any open files (I added one echo command to separate consecutive iterations of the loop). This was expected since my earlier tests using safe mode and without 3rd party apps installed also failed.

Looks like it's not about open files but something much deeper in the system, like stale mount or something related to init process. Unfortunately that's way beyond my debugging skills.
[Galaxy S 4 Q&A, Help & Troubleshooting] Arjan Mels:
Similar problem on Galaxy S3 with CF-AUTO-ROOT

I experience a very similar issue on my Galaxy S3 with cf-auto-root.

I also tried losf : no open files on /data.

Manual unmount works, but does not stop the error.

I notice in the log that other unmounts work (like data_1), but am surprised by the mentioned directories as some of them I don't recognize from the mount table.

The unmounting and encryption is handled by the vold service. I looked into the AOSP source code, but the messages are slightly different, so I suspect samsung is using a customized version (but it is not included in their open source code).

Frustrating... I need root, but also would like to have encryption...

Does anybody have android 4.3 + root + encryption working on Samsung?
[Galaxy S 4 Q&A, Help & Troubleshooting] chris19000:
Can confirm is not just limited to S4. Same issue with my Note 2 and are threads detailing inability to encrypt after root on S3 as well. Am monitoring threads for both and if I find something will post here too.
[Galaxy S 4 Q&A, Help & Troubleshooting] Michael.Kyritsis:
Reverting to stock firmware seems only way to enable encryption

I also encountered this issue on the GT-i9505 after I rooted the phone. As described by OP when try to encrypt it reboots - start up fine - but there is no encryption. This is a big problem for me because it's a work phone, and I order to access work email and contacts list I need to comply with the Google Policy tool, and the company I work for set up the policy to require encryption (among other things such as complex password).

Once I installed stock firmware 4.3 I was able to encrypt, comply with the policy, and sync my work email and work contacts.
[Galaxy S 4 Q&A, Help & Troubleshooting] razrielsch:
it seems do be really deep in android...

Because volks badadroid and Tigrouzen android images also have this issue...
[Galaxy S 4 Q&A, Help & Troubleshooting] jsda:
Solved

I solved this issue on my Samsung Galaxy S4 2014 (P600).

I was able to encrypt the device after disabling SuperSU (which came with the auto-root rom) and rebooting.
[Galaxy S 4 Q&A, Help & Troubleshooting] Arjan Mels:
Solved?

Sounds promising, but were you also able to enable root again after the encryption?
[Galaxy S 4 Q&A, Help & Troubleshooting] vttoth:
How did you disable SuperSU? I'm having the same problem on my Samsung Galaxy S3 (SGH-I747M on Rogers Canada, JB4.3). I tried disabling SuperSU by unchecking its Enable checkbox and rebooting. Did not solve the problem. Like an earlier commenter, I also did not find anything suspicious with lsof. Also tried disabling Wi-Fi (as suggested in a Twitter post I came across) to no avail.
[Galaxy S 4 Q&A, Help & Troubleshooting] smep:
Maybe Encryption was considered as a bloatware and been removed

Sent from dish washer
[Galaxy S 4 Q&A, Help & Troubleshooting] avah:
Ok, gave this one more try but still no luck. What I tried was to use the stock ROM mentioned in the OP for encryption then install TWRP on the already encrypted phone and then install a custom ROM again. The theory behind this approach is that encryption is a block level operation that happens below the file system and the encryption keys are stored at the very end of the volume on an unallocated area. Thus everything happens outside the file system and as long as you don't re-partition the drive, keys and encryption in general should stay intact even after complete wipe. I also had read rumors that some versions of TWRP should be encryption aware and be able to mount encrypted volumes. So I wiped, re-flashed stock ROM with Odin, preformed factory reset, rooted with CF-Auto-Root and encrypted the phone without any problems (except that not-so-minor fact that I was back with stock 4.2.2 TW phone.)

Then I flashed TWRP and tried to continue with custom ROM installation but this was the point where I learned that rumors about TWRP's encryption supports are just rumors. It doesn't work. At least not with the implementation used on stock I9505 and of course YMMV. Booting to recovery works and upon booting TWRP – depending on the version – even prompted for the password but then it claimed that my password was incorrect and /data wasn’t mounted. I had chosen a very simple password (Password123) because I didn't know what kind of UI and keyboard TWRP's password entry screen was going to have and I also tried several times, so typos were ruled out. No matter what did, my password wasn’t accepted in TWRP. Different versions didn't help either. Tried first with TWRP 2.6.3.1 then 2.6.1.0 and finally 2.6.0.0. All failed and TWRP 2.6.3.1 didn't even ask for the password. Meanwhile booting to OS worked fine with the same password.

At this point I decided that due to all the sensitive data – like work stuff, call recordings, etc. – I have stored in my phone, the encryption is more important than custom ROM. So I flashed back to stock (*sigh*) for good. Now I'm back in square one but at least I have an encrypted phone and I can use my SIM card PIN code again ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] xdascrat:
DeviceEnryption with JB 4.3

I have an S3 but with same error

"....Failed to unmount /data (Device or resource busy, retries 19, action 1).."

With OmegaROMv54.

There are different solutions to overcome this error.

For me at the end altough a different phone, the solution stated in "https://code.google.com/p/android/issues/detail?id=58073 worked

#43 .. [MENTION=5499064]gmail.com[/MENTION]

I believe there is an issue with the power logic allowing it to start.

Do:

Start>Security>Encrypt Phone

Enter your PIN.

JUST BEFORE you press 'encrypt phone' to start the reboot process, unplug your USB, then press 'encrypt phone'.

You should be OK now.

"
[Galaxy S 4 Q&A, Help & Troubleshooting] avah:
It's not about power logic. You can bypass the battery level and charging tests by initating the encryption directly from the command line. Just say "vdc cryptfs enablecrypto inplace your_max_16_char_password_here" as root. But the encryption will still fail.

And yes, I have tested also this unplug-your-usb-calbe trick mentioned above. And no, I it didn't help.
[Galaxy S 4 Q&A, Help & Troubleshooting] xdascrat:
Some details:

In my case entering the command "vdc cryptfs enablecrypto inplace" in terminal just doesn't work although repeated many times.

In adb logcat it was also trying to unmount /data many times, but failed.

I disabled many services, tried killing processes with a taskkiller short before performing the above command, as suggested in

code .google. com/p/android/issues/detail?id=58073#c48

But still umounting /data keeps on failing.

After that I enabled all services again,, rebooted, no more taskkilling, doing that USB Cable unplugging , and encryption worked. I hope, this issue will be fixed soon.
[Galaxy S 4 Q&A, Help & Troubleshooting] supermaz:
I also ran into this problem after I did a manual update to 4.3 on my Galaxy S3 via Kies. I then decrypted the device, rooted it and wanted to encrypt again.

I finally got it into starting the encryption (currently 30%, fingers crossed) via:

1. Disabling SuperSU (app-manager), though I don't think that this is really needed as disabling alone didn't work

2. Unmounting everything that I could using adb shell

- everything under /mn/asec

- /mnt/asec itself

- every bind-mount from /data/ to some legacy folders

So, finally I had only the following left:

root@m0:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0

After that I started the command from the shell via vdc cryptfs enablecrypto inplace <password>

Maybe this helps others.

Best regards,

Maz

EDIT: Encryption finished and is working!