Jump to content

Pixel and Pixel XL Preview (was "Fall 2016 Nexus | HTC Sailfish, Marlin Rumors")


Nrbelex

Recommended Posts

Higher end to start at $350? That's not too bad. Are the rumors still pointing to both being made by HTC?

 

Yes, the rumors say both will be made by HTC and will be nearly identical, but for their physical dimensions. But I would expect the price to be higher.

  • Like 1
Link to comment
Share on other sites

Higher end to start at $350? That's not too bad. Are the rumors still pointing to both being made by HTC?

S1 is the rumored lower end device...

Link to comment
Share on other sites

  • 2 weeks later...

The rumor regarding body materials came from a totally unproven site. No real reason to believe that given Android Police's track record and statement that "As far as we know, these phones are aluminum body, not polycarbonate." (Emphasis in original).

 

Also, nowhere have I read the phones will have different processors.

 

As for price, if the price is proportionate with the quality, I don't mind paying a little more.

AP has come out with some new pictures, looks like the S1 will be metal as well...

 

http://www.androidpolice.com/2016/08/14/exclusive-photos-of-the-2016-nexus-sailfish-in-the-metallic-flesh/

Link to comment
Share on other sites

This is pretty early for it to stop by the FCC for authentification does that mean this might be released earlier than October

Link to comment
Share on other sites

Heh, If so, no 3xCA on B41 for sprint.

 

Sent from my Nexus 5X

It doesn't mention any explicit CA combinations actually so it doesn't necessarily mean it's not supported! I'll take omission based on the fact that it is carrying possibly a Qualcomm 820 chipset. And keep my fingers crossed

Link to comment
Share on other sites

It doesn't mention any explicit CA combinations actually so it doesn't necessarily mean it's not supported! I'll take omission based on the fact that it is carrying possibly a Qualcomm 820 chipset. And keep my fingers crossed

 

 

I wouldn't go and say that, same set as HTC 10

 

Sent from my 2PQ93 using Tapatalk

 

 

It actually does.

 

Page 23 of SAR report.

 

WHAbo9Q.png

 

Of course FCC does not mandate full disclosures down link operations so it may possibly be a latent capability but that possibility doesn't look to bright as HTC (for once in their lives) disclosed the CA combinations in the FCC filing. 

Link to comment
Share on other sites

It actually does.

 

Page 23 of SAR report.

 

 

u killed me! I died a lil inside just now!

Link to comment
Share on other sites

Usually Google rolls out its next Android release such that the new Nexus (or Nexuses) gets it first; since at least one third-party device is advertising a September release with Nougat, that suggests the next Nexuses should be out in September too, if not late August.

  • Like 1
Link to comment
Share on other sites

Usually Google rolls out its next Android release such that the new Nexus (or Nexuses) gets it first; since at least one third-party device is advertising a September release with Nougat, that suggests the next Nexuses should be out in September too, if not late August.

I saw an article that seemed to indicate the LG V20 would be the first N device.

Link to comment
Share on other sites

I saw the FCC document for both Marlin and Sailfish were recently released.  Will we see one of the excellent RF performance write-ups for these and the Note 7?  I'm hankering for an upgrade!  

  • Like 1
Link to comment
Share on other sites

Uplink RF for both 2016 Nexus handsets looks just fair, nothing special.  Low band max ERP generally runs about 17 dBm, mid/high band max EIRP around 20 dBm.

 

AJ

  • Like 2
Link to comment
Share on other sites

Uplink RF for both 2016 Nexus handsets looks just fair, nothing special.  Low band max ERP generally runs about 17 dBm, mid/high band max EIRP around 20 dBm.

 

AJ

Thanks, AJ.  I thought I must have been reading the report wrong because the numbers seemed far too low.  Disappointing to say the least.  Looks like I'll be skipping this round and crossing my fingers for the next batch.

Link to comment
Share on other sites

Uplink RF for both 2016 Nexus handsets looks just fair, nothing special.  Low band max ERP generally runs about 17 dBm, mid/high band max EIRP around 20 dBm.

 

AJ

hmm...

 

Those are disappointing numbers

Link to comment
Share on other sites

I saw the FCC document for both Marlin and Sailfish were recently released.  Will we see one of the excellent RF performance write-ups for these and the Note 7?  I'm hankering for an upgrade!  

I'd like to join the chorus of those hoping for an RF performance preview. Those analyses set S4GRU apart from the countless other Android blogs and forums. Thanks!

 

S4GRU is honored at the request, and we appreciate the praise.  However, an FCC OET tested RF article probably is not forthcoming.  For several reasons, the article series largely has been put to bed.

 

Our FCC OET articles used to attract easily over 10,000 readers.  That number has since dropped by around 75 percent, making the time and effort put into the articles seem less worthwhile.

 

And then on certain articles, people have gone on to say that we are "wrong," that handset X has strong or weak real world performance.  S4GRU cannot control the uplink RF figures submitted to the FCC.  To have people argue with them or dismiss them based on their personally biased experiences questions the reasons for writing the objective articles in the first place.

 

Finally, the gist of the RF measurements and capabilities (e.g. 3x CA, VoLTE, etc.) usually gets written into a preview or user thread anyway.

 

AJ

  • Like 3
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No soecific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
    • T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.
  • Recently Browsing

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