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

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • 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.
  • Recently Browsing

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