Before this latest update (android 14 March update; pixel 7a), I used to get alarms both on my Bluetooth-enabled hearing aids, and the phone speakers. That’s also true for the timer function.
But now it seems they’re going only to the hearing aids, not the phone, which is problematic because at night the hearing aids sit in a charger, not my ears, but are (quite annoyingly) still connected to the phone. Which means the last few days I missed my morning alarm.
The other morning, while trying to figure out what was going on, I selected the alarm tone, and it only kind of played on the phone (my hearing aids were still in the charging case). It played for less than a second then off. A little later, it played and then off.
When I first upgraded to the march update, I noticed Bluetooth cycling on and off a few times (but I don’t recall seeing it afterwards).
Anyone have similar experiences? Known bug? Some settings I’m not aware of that I should try?
You must log in or # to comment.
Unfortunately I can’t help you but I’d be very interested in your hearing aids, since mine will have to be replaced soon.
Are they always connected? Can you listen to music and make calls with them? What is the battery life like? If you used Bluetooth (or wired) headphones: how do they compare in audio quality? Are they directly connected to the phone or do they still need that thing you have to wear around your neck? Which brand/model are they?
They’re Resound Quattro’s. They’re connected directly to the phone, no extra hardware required, though you need the Android app installed to make it work. Can’t just pair them with any random device that talks Bluetooth (like my tv!).
Yes, I can (and do) listen to podcasts and music with them(1), but the audio quality is necessarily not on par with even a cheap set of Bluetooth headphones. Hearing aids are tuned to let you hear conversation and your surroundings more, and don’t really have much in the way of bass 😅 It’s “serviceable” at best.
They are always connected and I can even receive phone calls on them, BUT they don’t have microphones (at least none it lets Bluetooth use) and so I have to speak into the phone, but at least I can hear via hearing aids.
I can usually go all day with batteries. Depends on how hard the hearing aids have to work, I think. Some days they conk out early evening, but most days they last until midnight. I’m not sure I know the exact reason. Doesn’t seem to depend on how much I use the Bluetooth connection.
But hearing aids are a VERY personal thing. Like shoes: some are cut wider and fit your foot better. I can tell you I’m pretty happy with mine (4 years old so all manufacturers have made a lot of progress since then!), but you really need to try a few to see how the audio quality sounds to YOU (and the kind and level of your hearing loss).
Good luck!
(1) I got hearing aids because I got tired of saying “what?” all the time. Now I have hearing aids and still say “what?” all the time, because I’m usually listening to a podcast and need to turn it off first 🤣
Thanks a lot, I’ll be sure to give them a try if my acoustician can get ahold of them.
Have you tried contacting the manufacturer of your hearing aids? It’s worth a shot and you don’t have much to lose, + they’re probably not even aware that there’s an issue with them.
Unfortunately the manufacturer doesn’t offer support or replacement parts anymore. My acoustician could semi-fix them for now but I’d rather trial new ones on my own terms and not when I have to.
Sort of related but I keep getting an issue with Pixel Buds Pro not pausing when I tap. This is after the March update as well.
Maybe there’s a Bluetooth bug?
The thought had occurred to me as well, when right after upgrade my Bluetooth seemed to cycle on and off a few times before stabilizing
I might try to remove the pairing and redo it (not a trivial process with hearing aids, but not super complicated, either).
Do you still have that issue? I have Pixel Buds A and I haven’t had any problem with my ear buds on GrapheneOS.
It seems to be fixed now. Must have been a strange bug.
Check the gear icon for your BT devices.
It might be a driver issue. Different BT devices have different access toggles.
Can’t offer help but just a developer perspective. This sounds like one of those things that was arbitrarily chosen by someone to be this way and then at a later point it was chosen to be that way by the same or different person. If you don’t find a workaround, your only hope is to complain to support, and/or file a bug on the public tracker and hope someone looks at it. Other than that, it’ll be a lifestyle change. 😑
