Jump to content

Smartisan T1

sbolen

By sbolen
in Misc.

 Share

Recommended Posts

sbolen Member Level: 4G WiMax

sbolen

Posted
  • Author
Posted

My Chinese intern said that you can run this phone on TMO's network with a pre-paid sim, but AT&T requires "a lot of work."

 

She has friends from China who are using this during stints in the U.S.

Link to comment
Share on other sites
lilotimz Member Level: LTE Advanced

lilotimz

Posted
Posted

My Chinese intern said that you can run this phone on TMO's network with a pre-paid sim, but AT&T requires "a lot of work."

 

She has friends from China who are using this during stints in the U.S.

First u have to make sure it supports USA LTE/wcdma/gsm bands. A lot of devices do not since they were designed for Asia.

 

Then you just manually edit the APN for the carrier.

 

Sent from my Nexus 5

Link to comment
Share on other sites
sbolen Member Level: 4G WiMax

sbolen

Posted
  • Author
Posted

First u have to make sure it supports USA LTE/wcdma/gsm bands. A lot of devices do not since they were designed for Asia.

 

Then you just manually edit the APN for the carrier.

 

Sent from my Nexus 5

 

Tech specs: http://www.smartisan.com/en/#/specs

Link to comment
Share on other sites
lilotimz Member Level: LTE Advanced

lilotimz

Posted
Posted
GSM850, GSM900, GSM1800, GSM1900, UMTS850 (B5), UMTS900 (B8), UMTS1900 (B2), UMTS2100 (B1), LTE2100 (B1), TD-SCDMA2000, TD-SCDMA1900, LTE1800 (B3), LTE2600 (B7), LTE900 (B8), TD-LTE2600 (B38), TD-LTE2500 (B41), TD-LTE2300 (B40), TD-LTE1900 (B39)

 

It'll support 3g/2g on att and some 3g on tmobile..

 

Sent from my Nexus 5

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

GSM850, GSM900, GSM1800, GSM1900, UMTS850 (B5), UMTS900 (B8), UMTS1900 (B2), UMTS2100 (B1), LTE2100 (B1), TD-SCDMA2000, TD-SCDMA1900, LTE1800 (B3), LTE2600 (B7), LTE900 (B8), TD-LTE2600 (B38), TD-LTE2500 (B41), TD-LTE2300 (B40), TD-LTE1900 (B39)

 

It'll support 3g/2g on att and some 3g on tmobile..

 

Yeah, sbolen's intern got it backward.  The handset is far more compatible with AT&T than with T-Mobile.  But we are talking only GSM/W-CDMA.  No LTE whatsoever.

 

I am not sure what the fascination is with Chinese people wanting to use their Chinese handsets here.  Get an American market or international handset.

 

And does this handset have an FCC ID?  Is it authorized for use in the US?

 

AJ

Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

If Sprint would allow unlocked phones it would work on there band 41.

Sprint will sometimes add unlocked phones now. But this one only supports one Sprint LTE band and no CDMA. So this one definitely isn't going to happen.

 

Using Tapatalk on Nexus 6

  • Like 1
Link to comment
Share on other sites
Volaris Member Level: 1x Advanced

Volaris

Posted
Posted

It'll work fine on T-Mobile, AT&T, and their MVNOs.

 

T-Mobile uses 1900MHz for both 2G and their 3G/4G HSPA+ network, while AT&T uses both 850MHz and 1900MHz for both 2G and 3G/4G HSPA+. 1700MHz 3G isn't that important for T-Mobile nowadays, they shifted that to 1900MHz to make space for LTE - in some markets 1700MHz 3G has been completely shut off.

 

As noted above, s/he will just have to edit the data/MMS APN settings so data and picture messaging works well.

Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

It'll work fine on T-Mobile, AT&T, and their MVNOs.

 

T-Mobile uses 1900MHz for both 2G and their 3G/4G HSPA+ network, while AT&T uses both 850MHz and 1900MHz for both 2G and 3G/4G HSPA+. 1700MHz 3G isn't that important for T-Mobile nowadays, they shifted that to 1900MHz to make space for LTE - in some markets 1700MHz 3G has been completely shut off.

 

As noted above, s/he will just have to edit the data/MMS APN settings so data and picture messaging works well.

Because of Tmo aggressive refarming for LTE, I wouldn't quite characterize it that way. I would say it currently should work in all of Tmo's footprint, with some areas having limited data performance that will only get worse over time without LTE.

 

Using Tapatalk on Nexus 6

Link to comment
Share on other sites
Tengen31 Member Level: 4G LTE

Tengen31

Posted
Posted

Sprint will sometimes add unlocked phones now. But this one only supports one Sprint LTE band and no CDMA. So this one definitely isn't going to happen.

 

Using Tapatalk on Nexus 6

Yep I know that. I was just pointing about that band 41 would be the only thing that would work. Just didnt explain it as well as you did.

Link to comment
Share on other sites
Fraydog Member Level: LTE Advanced

Fraydog

Posted
Posted

For St. Louis, it's going to hit AT&T B2 and B5 HSPA and T-Mobile's B2 PCS HSPA. And in AT&T's case, that PCS HSPA could be going away some day. I have had a gut feeling AT&T did their spectrum swap there with Sprint so they could go to 20x20 PCS LTE somewhere down the line. They probably don't have enough HSPA PCS cleared for it yet, but if I had a Galaxy S6 in STL I'd be checking service mode to see what the PCS deployments are. In Cape Girardeau AT&T is already running 10x10 PCS LTE aggregated with 5x5 B17. Now in St. Louis they have a much better spectrum position so they can aggregate B2, B17, and B4 when they kill off Cricket CDMA if they haven't already. My advice to your Chinese buddy - get a Sprint device. But if he must use a GSM carrier AT&T has better coverage especially in building, he needs a device custom fit to this market.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...