So I just spent the last 40 minutes with Google Chat Support regarding this issue. I was the owner of a launch device and had zero issues with this phone until . 3-4 weeks ago my phone started shutting off between 5-10% battery. I took multiple screenshots and submitted them to Google Support. They pointed me to a list of 30 different things that I should do for "optimal" use but eventually RMA'd the device after the problem persisted even after a full wipe and reflash of the latest system images. I received my replacement device today and let it hang out on which is what it shipped with. Battery acted completely normal and the phone was behaving really well. Had a persistent notification to upgrade to and reluctantly accepted. Phone lasted about 15 minutes off the charger before it died near 25-30% battery. Attached is the screenshot. This is absolutely unacceptable. I have since been back in contact with Google Chat Support and they've promised to escalate this to a "specialist". Before I RMA'd my original device I asked them if this would continue to be a problem. They assured me that the refurbished replacement would be "tested to the highest standards" and that I would have nothing to worry about. Literally less than 3 hours after receiving the replacement device the problem is even worse than it was with my original device. Since it was on when I received it they obviously didn't even test the replacement with the update to ensure there were no issues with the software.. Simple deduction leads me to believe that this is absolutely a problem with . The software update is obviously borking SOMETHING on this device. In addition, my old device suffered from the "echo" problem on phone calls for multiple months. However, I refused to believe there was an issue and would always tell the other person it was THEIR phone. Found out real quick that I was incorrect when I saw the thread about this issue here on XDA.. Sure, the phones aren't exploding like the Note 7.....but Google has a serious issue on their hands that they must address quickly. Unfortunately, I don't think they will. We must demand that this problem is fixed....and fixed soon. https:///images/
The following is from a knowledgable source: As far the numbering convention is concerned, the 11, 21, etc. is usually either based on the “go” of the day OR the the flight within a “go”. To explain, a “go” may usally consist of 12 jets. Of those 12, there may be three formations. Therefore, we normally assign the numbers of those formations as a sequence, . 11-14, 21-24, and 31-34. Where there are multiple flying squadrons at a base, they assign each squadron a series of 3 numbers, 0-8. Therefore, the same number suffix should not be flying with more than one formation at a time. This is also helps controls and pilots recognize their callsigns on the radio, especially if the radio transmission is clipped. For example, if all that is understood was “(radio static) 71, descend and maintain 3 thousand”, one would still know that the message was for callsign 71 and not callsign 51. The “91” callsign suffix is usually reserved for “checkride” sorties.