Jump to content

Samsung Galaxy Note 5 & Edge+ Rumor Thread

lilotimz

By lilotimz
in Samsung

 Share

Recommended Posts

bluemustangjosh Member Level: Morse Code

bluemustangjosh

Posted
Posted

I read it but im not very tech savvy I see it has various lte signals but I'm lost to which ones are for sprint and which ones arent... Also I don't know how many lte signals u need to have sprint spark (to my knowledge you would need three signals???). Sorry if I sound really lost but I am haha.

Link to comment
Share on other sites
  • Replies 105
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

lilotimz
lilotimz

Discovered by staff upon upload to the OET. Wall article in the making.    And yes. 2xCA on the downlink, typical LTE band 2/4/5/12/25/26/41 support, no SVLTE,.. yada yada. 

lilotimz
lilotimz

I'll start.   Get HYPE     Edit: Nope

Fraydog
Fraydog

http://www.att.com/cellphones/samsung/galaxy-s6-edgeplus.html#tab2 http://www.att.com/cellphones/samsung/galaxy-note5.html#sku=sku7670223     Here's the Death Star's pages for the GS6 Edge and Not

afazel Member Level: 3G EVDO

afazel

Posted
Posted

I read it but im not very tech savvy I see it has various lte signals but I'm lost to which ones are for sprint and which ones arent... Also I don't know how many lte signals u need to have sprint spark (to my knowledge you would need three signals???). Sorry if I sound really lost but I am haha.

Spark is B25, B26, and B41. Anything else could be used for roaming if Sprint and a partner enabled it.

 

Sent from my SM-N920P using Tapatalk

Link to comment
Share on other sites
afazel Member Level: 3G EVDO

afazel

Posted
Posted

Do you still have your G3 on an active line? we would be interest in the cell edge performance comparison, signal strength, band drop off, etc. the Note5 have bad RF per the wall article, I just want to see how bad it is in real life. My next upgrade is due in Nov and the Note5 is the top choice currently(unless the new nexus show some major surprises)

 

Thanks

It's on my mother-in-law's line. One thing I can say is I'm on B41 in my office where the G3 stayed on B26. I'll try a speed test later to see if it's actually usable.

 

Sent from my SM-N920P using Tapatalk

Link to comment
Share on other sites
afazel Member Level: 3G EVDO

afazel

Posted
Posted

Ok, so it's about the Same as the G3. I was wrong about it being on B41, it's actually just on B26 like the G3 Was. Speed test is about the same in my office.

 

752c39ec7603d4c11eec1f2a3fe2de63.jpg

 

Sent from my SM-N920P using Tapatalk

  • Like 1
Link to comment
Share on other sites
twospirits Member Level: LTE Advanced

twospirits

Posted
Posted

Guys, we now have official user threads for the Note 5 and S6 Edge up in the forums.

This thread will be closed by the end of the day since both devices are arriving in users hands and there isn't a need for a rumor thread any longer.

Please refrain from posting after this post and post in the appropriate user thread below.

 

Thanks

 

Samsung Galaxy S6 Edge User Thread

 

Samsung Galaxy Note 5 User Thread

 

TS

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

WiWavelength

Posted
Posted

404px-Closed_Sign.jpg

 

AJ

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 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...