How to fix common problems and improve battery life Pixel 3 XL

milehigherik

Well-known member
Aug 30, 2012
660
0
0
AC usually makes one of these useless threads... Just haven't seen it yet.

Please don't remove my post. It is my Valiant attempt at humor.
 
all joking aside... As many of these as have been released, I wouldn't be surprised if there were known issues before the actual release. Bring it on I have been waiting almost 8 months for a pixel 3XL.
 
I can tell you how to fix one common problem: make sure you have your 3 XL with you when you leave the taxi or the bar.:p
 
My previous pixel 2 XL had RAM management issues. More RAM would be good for a start.
 
AC usually makes one of these useless threads... Just haven't seen it yet.

Please don't remove my post. It is my Valiant attempt at humor.

You don't have to worry about Pixel 3 battery life. It will use a regenerative heat exchanger which will draw upon external heat sources like ambiemt light, body heat including finger touch thermal sensors and other undisclosed sources.
 
You don't have to worry about Pixel 3 battery life. It will use a regenerative heat exchanger which will draw upon external heat sources like ambiemt light, body heat including finger touch thermal sensors and other undisclosed sources.

Future wish list item... Hmm
 
Future wish list item for the 2! A fingerprint sensor that works. I've gone through 3 of them, the 4th one arrives tomorrow, and so far 3 dead fingerprint sensors. It senses pulling the shade down, just not my fingerprint. Maybe my fingerprints are defective? That would be too bad - they're over 75 years out of warranty.
 
Hey @Rukbat, stop making all of those model airplanes and getting the cement stuck in grooves of your fingerprints!:p
 
But ... but ... but ... that's what I use to wipe the glue off my fingerprints.

Seriously, we'll see later today - the replacement replacement replacement for the replacement is on the FedEx truck, and it hasn't gotten here yet. He usually gets here around 5 and it's only 2. But if this one has the same problem I'm going to insist on an escalation, a supervisor and, maybe, a little something for all the beta testing of defective refubs I've been doing for them. (I used to make enough money doing this sort of stuff to live off the left side of the menu. If they paid my hourly rate [at least 2 hours every time I call them, try this, try that, factory reset, update, factory reset] they'd owe me a P3XL, a P4XL and a few more down the line.)
 
Latest chapter of the tale of "Rukbat and the Mysterious Fingerprint Scanner Failure":

After spending almost 4 hours on the phone with Google, ending with the software team (since I have arrived at the conclusion - with which they agree - that there is a massive calamitous [no, I'm trying to keep it way below the actual level of seriousness BUG in Android]). What!?!?!? Yes, a bug in Android. Probably a minor typo that no one noticed, but if you try to add a fingerprint when there aren't any in the database yet, it won't work. It used to. The replacement came with the March patch and it worked. We updated to Pie and it stopped. Wer updated to September and it still doesn't work.

So we did a debug dump on the phone (the "new" [actually refurb] phone that arrived today) and I sent it off to the person who's going to be looking at it, trying to find out why it doesn't work. (And I really do wish him lots of luck - I've been where he is, and he's going to need it.) If he can't find it from a debug dump, the software engineers are going to have to run a phone in full debug - probably a CPU emulator so they can watch, instruction by instruction, what's happening as you try to get the scanner to recognize that you're trying to get to the "scan your fingerprint" screen. Been there too. (Don't ask me why I still have a full head of hair - that's one mystery I've never solved - I should have torn it all out, clump by clump, after almost 60 years of debugging things that don't work just due to IPIO - the Innate Perversity of Inanimate Objects.)

At least I now know why the trouble exists, and where it exists - and I fully understand that it could take them 6 months to find the bad code. I'll wait. (Maybe I'll send Sandar a bill for debugging services. After all, I figured it out all by my little old self. [Well, 5'9" old self.]) But it will probably be found, and fixed, and included in an update. Maybe not October, maybe not November, but it's being worked on, and that's all I can ask for.

(And someone "up there" now knows that the Pixel 2 (and, I'm betting, the Pixel 3 - and the XL versions of both) aren't compatible with flashing using a USB 3.0 port and a USB 3.0 cable. They weren't aware of that until today. It's only been all over XDA since about last year. Maybe they'll give me a job forwarding legitimate problems like that to them.)

Oh, and please do not delete your fingerprints and try to add them back. It may work. Or you may be left with a phone that doesn't do fingerprint scanning. I've warned you, so don't complain to me.
 
Latest chapter of the tale of "Rukbat and the Mysterious Fingerprint Scanner Failure":

After spending almost 4 hours on the phone with Google, ending with the software team (since I have arrived at the conclusion - with which they agree - that there is a massive calamitous [no, I'm trying to keep it way below the actual level of seriousness BUG in Android]). What!?!?!? Yes, a bug in Android. Probably a minor typo that no one noticed, but if you try to add a fingerprint when there aren't any in the database yet, it won't work. It used to. The replacement came with the March patch and it worked. We updated to Pie and it stopped. We updated to September and it still doesn't work.

So we did a debug dump on the phone (the "new" [actually refurb] phone that arrived today) and I sent it off to the person who's going to be looking at it, trying to find out why it doesn't work. (And I really do wish him lots of luck - I've been where he is, and he's going to need it.) If he can't find it from a debug dump, the software engineers are going to have to run a phone in full debug - probably a CPU emulator so they can watch, instruction by instruction, what's happening as you try to get the scanner to recognize that you're trying to get to the "scan your fingerprint" screen. Been there too. (Don't ask me why I still have a full head of hair - that's one mystery I've never solved - I should have torn it all out, clump by clump, after almost 60 years of debugging things that don't work just due to IPIO - the Innate Perversity of Inanimate Objects.)

At least I now know why the trouble exists, and where it exists - and I fully understand that it could take them 6 months to find the bad code. I'll wait. (Maybe I'll send Sandar a bill for debugging services. After all, I figured it out all by my little old self. [Well, 5'9" old self.]) But it will probably be found, and fixed, and included in an update. Maybe not October, maybe not November, but it's being worked on, and that's all I can ask for.

(And someone "up there" now knows that the Pixel 2 (and, I'm betting, the Pixel 3 - and the XL versions of both) aren't compatible with flashing using a USB 3.0 port and a USB 3.0 cable. They weren't aware of that until today. It's only been all over XDA since about last year. Maybe they'll give me a job forwarding legitimate problems like that to them.)

Oh, and please do not delete your fingerprints and try to add them back. It may work. Or you may be left with a phone that doesn't do fingerprint scanning. I've warned you, so don't complain to me.

I hear what you're saying but lots of people have updated to Pie and or reset their phones since the Pixels release and at various intervals. While I've heard of others with fingerprint issues it hasn't been rampant. I reset my phone at some point during the beta because my Disney app wasn't working on an early release of Pie and I was headed to Florida. People have also reset recently to get the latest update. I guess it's possible it doesn't crash every time but in your case it seems guaranteed.
 
And in the case of the software engineer working on it. His phone no longer does fingerprints either.

This comes under the heading of VERY WEIRD.
 

Forum statistics

Threads
954,574
Messages
6,962,056
Members
3,163,075
Latest member
intersyslimited