So, I have yet to see anyone mention my issue, but I am unsure if it warrants a new post somwlewhere or not, so I figured I'd try it this way.
Device: SM AI56U updated last week, or early this week. Currently running the OneUI7 and Android 15 package that was pushed. Before this update, I was very happy with the abilities and performance of this inexpensive device. I work alone, out side around a ton of machinery, so I use BT ear buds all day, every day to listen to music, know when I get a call or text, and as a (probably ineffective) ear protection.
I immediately booted to the recovery and wiped the cache after the update. BT worked wonderfully til today. Nothing has been changed. Several bt d3vicez have been tested and all but one have the same issue.
THE PROBLEM: Bluetooth buds, earphones, and speaker will all start normally. Within 10 minutes something happens and the volume is decreased to the point that the devices are muted. The volume control on the phone will show the volume set where I have, so it LOOKS like the volume was decreased from the device intentionally, and thats not happening.
Disconnecting and reconnecting will sometimes return volume to previous level, but will repeat the same thing over. Forgetting and re-pairing the device does the same thing, they will work for a short while then the volume will randomly decrease to a mute level. The only BT device that has not had this issue is a cheap 12v BT to FM transmitter I use in the tractors/trucks/and equipment. I expected this one to fail or glitch, as the Android 14 One UI6.1 update made that device do similar things, with the prior A14&1UI6.1 package the buds, speakers, and earphones worked flawlessly, but the adapter would randomly turn down and mute. With that issue I once again wiped cache partition and the problem was resolved.
I have checked for updates. I have tried different music apps, along with a few audio "enhancement" apps as they have separate volume sliders. I have wiped the cache, I have "forgotten" every single device. Even my Dexcom G7 (which works quite well with the current software, btw) and re-paired each. The issues continue to plague me, and if it cannot be resolved I will.be forced to buy another.device, as I absolutely need full Bluetooth functionality. Period. If it comes to that, my next purchase will not be a Samsung. I bought my first Samsung when the Galaxy S3 was released (I actually had a release day SGS3!! I at least felt cool as hell!) Since then I have bought and used more than a dozen Samsung devices. This whole OneUI7 debacle has soured me on the brand ,and it sucks. I do love this brand, they make some wonderful devices, after the while.battery swelling deal Samsung stepped up their game ,and things were great. Now it seems they have rushed to push this package and it's riddled with random, stupid little bugs that are driving people crazy.
If anyone out there has had this issue, or a similar issue and managed.to resolve it....I BEG.YOU TO TELL ME HOW you did so, please. Thanks in advance.
