Today I was at the gym for the first time with my Pixel 7 Pro and wanted to adjust my EQ for my Pixel Buds, but the EQ function was not there. There is an option under the Bluetooth device settings to "Open Pixel Buds" for more settings, but its seems like it tries to open another window, then just closes and goes back to the same screen. I have also tried clearing data, resetting the pixel buds, installing an earlier version of the app, nothing works. I decided to see if maybe it was an issue with the phone, so I fired up the Pixel 6 Pro and everything worked fine on it.
In reading some of the reviews on the play store, it seems like I am not the only one with this issue on the Pixel 7 Pro. Wondering if anyone else is experiencing it?
Here is a screen from the Pixel 7 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a screen from the Pixel 6 Pro
This is from my 7 pro
I did notice mine was showing limited information like your screenshot shows, but I mostly use mine for remote work meetings, so I haven't tried them again yet.
I get all the options for my Pixel buds pro. I would try downloading the latest pixel buds application from APMmirror and try reinstalling it that way, also chest to see if there is a firmware update for your buds once the app os working
I ran a logcat and saw that it was missing some sort of Google certificate. I did a factory reset on the phone and the buds and all is working correctly now.
On the Pixel 7 pro I am getting calls, notifications, game sounds, etc all defaulting to the Pixel buds pro even when they're in the case. Anyone have any advice?
Related
I have just bought a head unit and I have to say that the Launchers out there are nothing but a total waste of time.
My needs are quite simple I want google maps displaying and I want apple music controls to change track etc as I drive.
The launchers with car logos, speeds (i already have one of those), 15 million screens with a hundred different widgets..I'm driving for gods sake all I want is music and maps on the same screen.
I have not managed to find what I need anywhere...does anyone know if such a thing exists because I am losing the will to live out here. (btw Google maps for some reason does not display the apple music controls probably because it is android, and you cannot have a split display as Apple Music does not support this).
Rant over if anyone can help it would be sincerely appreciated.
Have you tried just getting a CarPlay dongle and using Apple CarPlay?
Sent from my iPhone using Tapatalk Pro
Carplay screen
Just had a look at the Carplay for IoS 13 and this is exactly what I was looking after - if anyone knew if this is available on Android only without an iphone that would be perfect.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I apologize...when you said Apple Music I assumed you had an iPhone. It won’t work with android.
Sent from my iPhone using Tapatalk Pro
karmannsport said:
I apologize...when you said Apple Music I assumed you had an iPhone. It won’t work with android.
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
No problem.
buit I have to say that carplay with ios 13 is exactly what is required. Navigation on one side of the screen and musci controls on the other -p what else does anyone need?? I can do the same on android with split screen with Google maps on one side and tune in on the other but it disappears when you witch off the car and restart which is a bit of a pain.
So I am on a pixel 3xl rooted on Android 10. I was in the Android 10 beta all worked well all through beta. I started noticing battery life of phone is not so good so I foolishly formatted phone now I can't download Galaxy wear app from the store. So I side loaded it. However now I get this error. I do realize it obviously isn't compatible with Android 10 currently but it worked before. Just wondered if anyone had a work around. Thanks guys.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 XL using Tapatalk
Hi, i had the same issue, for resolving that, you need download and install the following apks:
-Galaxy wear app
-Gear S plugin
-Samsung accessory service
Then, run the setup from the start and your gear s3 should work as usual.
Gunner123 said:
Hi, i had the same issue, for resolving that, you need download and install the following apks:
-Galaxy wear app
-Gear S plugin
-Samsung accessory service
Then, run the setup from the start and your gear s3 should work as usual.
Click to expand...
Click to collapse
Didn't work for me. However I noticed even when I have Samsung wearable uninstalled as you can see in the picture when I search it in chrome it shows as installed? But it's be nowhere to be found. How can I completely uninstall it?View attachment 4843445
Sent from my Pixel 3 XL using Tapatalk
this nessesary app not compatible with android 10 beta... all nessecary app ned to support new android version
Hey,
I am running the CPH2025_11_A.18 firmware. I noticed that the screen rotation is very unreliable in basically every app I've been using ( Youtube, Chrome, Google Photos etc.). So I checked the sensors with multiple Apps
and noticed that my phone thinks its drifting towards the left (X-Axis) when laying flat on the ground. Factory resetting my the phone and using the Google Maps calibration feature didnt't work. Before returning my phone I want
to make sure its not something software/firmware related. Could you guys comment on your auto-rotation experience and the sensors (f.e. using the in-built spirit-level App).
In this positon my phone thinks its laying flat on the ground:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No issues here
Markeem said:
Hey,
I am running the CPH2025_11_A.18 firmware. I noticed that the screen rotation is very unreliable in basically every app I've been using ( Youtube, Chrome, Google Photos etc.). So I checked the sensors with multiple Apps
and noticed that my phone thinks its drifting towards the left (X-Axis) when laying flat on the ground. Factory resetting my the phone and using the Google Maps calibration feature didnt't work. Before returning my phone I want
to make sure its not something software/firmware related. Could you guys comment on your auto-rotation experience and the sensors (f.e. using the in-built spirit-level App).
In this positon my phone thinks its laying flat on the ground:
Click to expand...
Click to collapse
My phone doesn't have this problem. It's rotating just fine. My Firmware version is CPH2025_11_A.14
I think you should return the phone to your seller for service.
Good luck,
Virebeetle
Yeah so I'm running pixel experience based on android 11 and Google Assistant is acting really weird. Tbh I don't really know if it's because of the rom it not but I enrolled in the Google app beta quite a while ago (although I've unenrolled now) cause I wanted to experience that new Assistant UI earlier. Well now it only shows the new UI when I'm logged in with one of the 3 Google accounts I have on my phone. Also when I press on Unlock new features, and it comes to the Alarm routine screen, pressing next crashes the screen. I'm a complete noob and I'll be really grateful if anyone could help me out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been having the same issue since a few days. When I press the Next button, Google Assistant crashes
error1105 said:
Yeah so I'm running pixel experience based on android 11 and Google Assistant is acting really weird. Tbh I don't really know if it's because of the rom it not but I enrolled in the Google app beta quite a while ago (although I've unenrolled now) cause I wanted to experience that new Assistant UI earlier. Well now it only shows the new UI when I'm logged in with one of the 3 Google accounts I have on my phone. Also when I press on Unlock new features, and it comes to the Alarm routine screen, pressing next crashes the screen. I'm a complete noob and I'll be really grateful if anyone could help me out.
View attachment 5401447
Click to expand...
Click to collapse
Found a post on Reddit that mentioned this - thought it was utter rubbish but ... It worked for me.
Change your settings to light mode (disable dark mode) and try again and it'll proceed.
Hello
From time to time I have issues connecting my GW4 Classic LTE to my Pixel 6 Pro A13.
Today I updated my Pixel's Google play Services to the latest beta. After that, I received this notification (allow notifications for GW4):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I checked the notification settings permission:
It seems that I can't activate the switch because of restricted permissions (security):
Now The Galaxy wearable app can't connect to the GW4. Also phone can't hold the Bluetooth connection alive:
I had this issue before. Only factory resetting the watch solved this problem. But I don't wanna reset my watch every few weeks. Rolling back to previous play services changed nothing. Clearing play services app data also triggers this issue.
Any ideas? Thanks.
EDIT: I allowed the restricted notification setting like the following instructions. But still no BT Connection. "No notification s possible" notification came back. GW4 only uses WiFi or LTE
Unless youre prepared to deal with the downsides of it, never update core apps like play services to a beta....
My own Watch 4 got its connection wiped just doing an update to a "stable" build from the play store overnight
There is no easy fix, i have to reset and restore from backup....
My ultimate point here is i wouldn't actively invite mayhem by using betas....