Jump to content

Upcoming 5G Devices?


Yuhfhrh
 Share

Recommended Posts

Do we know of any future 5G devices headed to Sprint by the end of the year? I assume the Galaxy Note 10. Anything else though?

When X55 modem devices start coming in, will T-Mobile and Sprint share the same models with support for N260, N261, N71, and N41? What about N12, N25, or N66?

Link to comment
Share on other sites

There will be a Note 10+ 5G coming to T-Mobile in Q4: https://www.t-mobile.com/news/samsung-note10

The press release states it will support N71 along with other unnamed mid band spectrum, so this will have the X55 modem. I assume the unnamed mid band(s) would be N25, N66, and N41. The same or similar model will likely make it to Sprint.

Link to comment
Share on other sites

  • 2 weeks later...

The new 5G One Plus phone will be a global 5G device, which means it should support several NR bands: https://www.xda-developers.com/oneplus-ceo-confirms-5g-smartphone-possibly-oneplus-7t/

This phone may support all of Sprint/T-Mobile's 5G low and mid bands similar to what the Note 10+ 5G might do.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
2 hours ago, Yuhfhrh said:

One Plus 7 Pro 5G launched on Sprint. We're only about a month or two out from the new 5G One Plus phone being launched, but I guess better late than never? https://newsroom.sprint.com/oneplus-7pro-5g-launches-as-sprints-fourth-5g-device.htm

Looks like my new phone! Perfect timing too!

Link to comment
Share on other sites

2 hours ago, Yuhfhrh said:

One Plus 7 Pro 5G launched on Sprint. We're only about a month or two out from the new 5G One Plus phone being launched, but I guess better late than never? https://newsroom.sprint.com/oneplus-7pro-5g-launches-as-sprints-fourth-5g-device.htm

 

22 minutes ago, SeanK_ said:

Looks like my new phone! Perfect timing too!

Does anyone know if this phone has 1x800? Granted, at this point that may not be a big deal to most people, but it might matter to those on the fringes of coverage.

Link to comment
Share on other sites

On 8/27/2019 at 3:40 PM, Rawvega said:

 

Does anyone know if this phone has 1x800? Granted, at this point that may not be a big deal to most people, but it might matter to those on the fringes of coverage.

I can't find any information on band support, or an FCC ID. Nothing on the OnePlus website either.

I would assume they would throw in BC10, as it shouldn't be difficult when the 7 pro already supported BC0.

Edit: It does support BC10: https://fcc.report/FCC-ID/2ABZ2-GM1925

Edited by Yuhfhrh
Link to comment
Share on other sites

  • 1 month later...

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

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Let me take a look tonight. 
    • Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked. Robert
    • I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.
    • I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.
    • I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.
  • Recently Browsing

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