Jaxas Posted August 19, 2023 Share Posted August 19, 2023 7 hours ago, maxmp said: @Jaxas unfortunately this is not reproducible on the recent Poweramp builds. Thanks for the detailed info. The issue is localized on your device, so no way I can investigate it using any of my devices. If you're willing to investigate it further, I can prepare a Poweramp build with extra logging around routing, so we'll know why on your system F2 is shown when K23 is connected. Sure, if you don't mind throwing together the logging-build I can do some more testing 👍 Link to comment Share on other sites More sharing options...
Jaxas Posted September 21, 2023 Share Posted September 21, 2023 Hello, just following up on this @maxmp - do you have a build for me to install, or are you still working on it? Thanks! Link to comment Share on other sites More sharing options...
maxmp Posted September 22, 2023 Share Posted September 22, 2023 @Jaxas now we advanced few builds forward - are you able to reproduce this with build 976? Link to comment Share on other sites More sharing options...
andrewilley Posted September 22, 2023 Share Posted September 22, 2023 On 8/16/2023 at 5:32 PM, Jaxas said: I unpaired all BT devices (except the watch, since that would force a wipe > reinstall to re-pair, thanks Android Wear 😅) If the problem is still occurring, have you tried with the Galaxy Watch disconnected (just turn it off, or disable its Bluttooth temporarily). I found a number of builds ago that a similar issue was being caused by my Watch5 being connected at the same time as a BT output device - although recent PA builds do seem to have resolved that conflict for me. Andre Link to comment Share on other sites More sharing options...
Jaxas Posted October 4, 2023 Share Posted October 4, 2023 On 9/21/2023 at 11:40 PM, maxmp said: @Jaxas now we advanced few builds forward - are you able to reproduce this with build 976? Yes, this is still occurring (Version: build-976-bundle-play [976004-c2601e58]) On 9/22/2023 at 12:51 AM, andrewilley said: If the problem is still occurring, have you tried with the Galaxy Watch disconnected (just turn it off, or disable its Bluttooth temporarily). I found a number of builds ago that a similar issue was being caused by my Watch5 being connected at the same time as a BT output device - although recent PA builds do seem to have resolved that conflict for me. Andre I tried that here ↓ before On 8/16/2023 at 2:09 PM, Jaxas said: Sure, I turned my watch off and connected/disconnected the F2 a couple times, and the first few times it was going to K23 and then this last time (after I turned my watch back on) it went to F2 With it somehow going to K23 without the assignment in the previous test, I'm thinking it might be some sort of issue with the EQs/assignments - is there a way I can fully clear that (without completely wiping the app > reinstalling)? However I can try again when I get home later this evening Thanks! Link to comment Share on other sites More sharing options...
Jaxas Posted October 26, 2023 Share Posted October 26, 2023 Hello, I've ran some additional tests and the Galaxy Watch does not appear to be the issue, as it still happens with it powered off + rebooting the phone The TL;DR is that the only thing that makes Poweramp correctly update the Assigned Preset is fully closing the app, since it appears to get the right device once and then "stick" on it? Please let me know what other info you need, or if you still want me to install a logging-build like you mentioned before Thanks! @maxmp Poweramp Info: - build-976-bundle-play [976004-c2601e58] - Full Version - 64 bit ===== Setup ===== Spoiler 1) Cleared all EQ "Assignments" in Poweramp 2) Cleared Bluetooth pairings for the following devices: - F2 Headset - F9 Headset - IP8-X Headset 3) Turned off Galaxy Watch 4 4) Restarted phone 5.A) Paired F2 headset 5.B) Assigned "F2" EQ Preset in Poweramp to "Bluetooth > F2" 5.C) Powered off the F2 Headset 6.A) Paired the F9 Headset 6.B) Attempted to assign the "Elantra" EQ Preset in Poweramp to "Bluetooth > F9", however the only option under "Bluetooth" was the (now disconnected and powered off) "F2" device 6.C) Closed Poweramp, Disconnected & powered off the F9 headset, reconnected the headset 6.D) Successfully assigned the "Elantra" EQ Preset in Poweramp to "Bluetooth > F9" 6.E) Powered off the F9 Headset 7.A) Paired the IP8-X Headset 7.B) Assigned the "Temp" EQ preset in Poweramp to "Bluetooth > IP8-X" 7.C) Powered off the IP8-X Headset Tests & Results Spoiler - Connected F2 Headset → Swapped to "F2" Preset ✅ - Disconnected F2 Headset → Swapped to "Phone Speakers" Preset ✅ - Connected F9 Headset → Swapped to "F2" Preset ❌ - Disconnected F9 Headset → Swapped to "Phone Speakers" Preset ✅ - Connected F9 Headset Again → Swapped to "F2" Preset Again ❌ - Disconnected F9 Headset → Swapped to "Phone Speakers" Preset - Connected IP8-X Headset → Swapped to "F2" Preset ❌ - Disconnected IP8-X Headset → Swapped to "Phone Speakers" Preset - Closed & Swiped-Away Poweramp - Connected F9 Headset → Swapped to "Elantra" Preset ✅ - Disconnected F9 Headset → Swapped to "Phone Speakers" Preset ✅ - Connected F2 Headset → Swapped to "Elantra" Preset ❌ - Disconnected F2 Headset → Swapped to "Phone Speakers" Preset ✅ - Skipped & Played part of a song - Connected IP8-X Headset → Swapped to "Elantra" Preset ❌ - Disconnected IP8-X Headset → Swapped to "Phone Speakers" Preset - Swapped to a different app, did not close Poweramp - Connected F2 Headset → Swapped to "Elantra" Preset ❌ - Disconnected F2 Headset → Swapped to "Phone Speakers" Preset ✅ Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now