Regards volume do you mean defaulting to safe volume level on initial connection or even when at full volume it feels low?
Regards updates you can disable auto reboot and only do it when convenient, you can also set it to only when charging and only at a certain battery level.
Let me know the answer to the BT issue and if the updater tips help.
My BT volume level on the phone is always 100%. When I first start Spotify, I hear a song start playing at normal volume, for maybe 1/2 a second, or 1/10 of a second. It immediately drops to a very low volume (although the volume still shows as 100%). The volume continues at this level as long as the device is connected. I've had this experience with multiple BT devices (car stereo, JBL speaker, my garage stereo system that has a BT input, etc). It has ONLY been an issue with Spotify - Tidal, YouTube, etc work fine.
How do you have these settings in Spotify configured have you tried experimenting with them?
#m=image%2Fjpeg&dim=1080x388&blurhash=Q35X%7Di%7ED%25yVaInRQIUNGa2S%5Dwitja2g1RQofbYaMR%25aLkURQbFWBt7tQjI&x=880489c81f9540bb26e94d1eb1d2cb6eb07d6c29e88dc3f1534a7c1627338ebe
Normalize - off, volume level greyed out but Normal is selected.
Try the settings I've shown, as I've never experienced it, I have turned it off for now to see if it affects anything.
No luck. Setting it to loud did give a little increase, still at 50% or less volume.
Are you on free or premium?
This is definitely an app/service issue and not related to the OS, plenty evidence of the issue being reported across the web from Android to iOS and multiple device variants and bluetooth accessories. If this was OS related it would impact other apps too.
I would tend to agree, likely something in the way the app uses the OS audio drivers. I had an identical Pixel 6 that worked fine, bought this one to put Graphene on fresh, and it has never worked. Everything else has been great, though. I appreciate you talking me into Graphene, or at least pointing me at resources that were convincing.
Premium family, locked in hard enough I don't want to also pay for Tidal.
Looks like they took away the setting to only check for updates 1/wk. the notifications for reboots show an estimate of 1/day - that is pretty crazy for a "stable" release, IMO. I've just disabled notifications for system updates altogether. Now I have a feeling that anytime I reboot my phone, I'll just be waiting a significantly longer period of time for any updates to finish installing and apps to refactor or whatever they do.
The release is stable, as a security and privacy focused OS as soon as patches and updates are available and are implemented into the OS we push them to you to maintain protection.
Unlike stock or other OSes we don't leave people auffering issues where we can resolve them first. Take the recent package installer regression in QPR1 where we issued the following:
Android 14 QPR1 has some regressions for the package installer interface. They were aware of these issues for months and they're already fixed in the QPR2 Beta. It's unfortunate their release process is too slow to incorporate fixes, largely defeating the purpose of beta testing.
GrapheneOS will have another OS update later today with fixes for these issues. Stock Pixel OS users will hopefully only need to wait for the January monthly release to resolve the package installer interface crashes. They need to fix many things about their release processes.
