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

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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