Pixel 2 XL questions

pinco000 said:

Hi guys, Im new to this forum. Im coming from almost 10 years with apple. First of all there is a lot I like about android. However I have few major issues which I would like you guys to shed some light.
1. My phone will not even see my BMW. Is this going to be addressed in the Oreo8.1?
2. My phone is only a week old and I experience some displey border unresponsivness. It is quite annoying for the price. So, is this being addressed too?
3. I use often my bluetooth speaker at work. Connection is not a problem at all. However the max volume level is somewhat really quiet.
In an attempt to fix this I set my mp3s to 100db in win10 territory. This however didnt help a lot. Is there any other way to get this sorted, is tgere any normalization setting hidden somewhere? Or this is another problem that Google needs to fix?

Yesterday I sent to google my feedback, I hope they reply?

Lastly guys, when will be Oreo 8.1 update available over the air for my phone?

Thank you for reading 😁

Click to expand...

Brian706 said:

1.) I'm not really sure to be honest. My car doesn't have native Bluetooth so I've never delt with it. Are you sure you've gone into the settings in your car and made sure it's discoverable by the phone?

2.) I've had responsiveness issues one time with mine, and I simply rebooted the device and all was fine.

3.) This is a setting I've never tried, but in the developer options, there is an option called 'Disable Absolute Volume'. That may possibly help with the issue with your speaker.
View attachment 126487

Might be worth a try. To unlock the hidden developer options go to settings>system>about
Tap on build number 7 times. Then developer options should show up in settings>system

Click to expand...

Brian706 said:

I'd imagine any time. It comes in waves to the devices other seems. The factory images are posted: https://developers.google.com/android/images#taimen

So I'd think you'll see it any day.

Click to expand...

Brian706 said:

It depends on your situation. Technically, yes, that is the intended use of the factory images. But there is a script you run, to automate the process. You can edit the script to have it not wipe the device when it flashes the images.

Here's the other catch though... You can't flash the factory images unless you have an unlocked bootloader. And unlocking the bootloader does in fact wipe the device.

Actually, what you can do, and it would be better is adb sideload the ota image. This will not wipe the device. Basically it's manually applying the ota.
https://developers.google.com/android/ota

You need to have adb setup and working. Instructions and downloads are at the link, along with the ota images. Just let me know if you have any questions!

Click to expand...

Hadron said:

They do the rollout in phases, quite sensibly in case there are problems. So for the first phase only a small percentage of devices will get it, then a larger fraction, and only after a number of days does it go to everyone.

Click to expand...