Jump to content

Jaxas

Approved Members
  • Posts

    14
  • Joined

  • Last visited

Jaxas's Achievements

Advanced Member

Advanced Member (3/3)

  1. 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 ===== Tests & Results
  2. Yes, this is still occurring (Version: build-976-bundle-play [976004-c2601e58]) I tried that here ↓ before However I can try again when I get home later this evening Thanks!
  3. Hello, just following up on this @maxmp - do you have a build for me to install, or are you still working on it? Thanks!
  4. Sure, if you don't mind throwing together the logging-build I can do some more testing 👍
  5. Right, sorry - I'm not sure I was clear; I was specifically confused because when I connected the K23 headphones in the earlier test, it assigned the correct equalizer despite me having previously removed the Assignments You're right though that that would likely be a separate 'issue', since the Audio Info's detection is where the problem I'm running into is ----- Anyways, I'm actually much more confused now - I saw that there was a "Send a log" option in the settings, but it was only a snapshot (so it couldn't display info on the state changes as I connected & disconnected the devices) So I went and took a full logcat from the Poweramp app where I went through and connected the F2, then disconnected, then connected the K23, then disconnected again, and the logcat is returning the correct device while the "Output Device" is still showing the wrong one Timeline: 1) Neither connected 2) Connect F2: Logcat says "Audio routes updated: AudioRoutesInfo{ type=SPEAKER, bluetoothName=F2 }" | Output Devices says "F2" 3) Disconnect F2: Logcat says "Audio routes updated: AudioRoutesInfo{ type=SPEAKER }" | Output Devices says "Speaker" 4) Connect K23: Logcat says "Audio routes updated: AudioRoutesInfo{ type=SPEAKER, bluetoothName=K23 }" | Output Devices says "F2" 5) Disconnect K23: Logcat says "Audio routes updated: AudioRoutesInfo{ type=SPEAKER }" | Output Devices says "Speaker" I'm emailing you the full log now - hopefully there's something helpful in there?
  6. 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)?
  7. Sure thing! 1) Unpaired all bluetooth devices (excluding the Galaxy Watch 4) & unassigned all Bluetooth EQ assignments 2) Rebooted phone (watch automatically pairs ASAP) 3) Open Poweramp: EQ is correctly set to "Phone Speakers" (assigned to "Speaker") 4) Pair "F2" headphones - assign F2 EQ preset - disconnect (power off) F2 headphones - (EQ correctly returns to "Phone Speakers") 5) Pair "K23" headphones - Poweramp... assigns the K23 EQ preset, but doesn't display it as having been assigned when I go to the "Assign Preset" screen? - re-assign K23 preset - disconnect (power off) K23 headphones - (EQ correctly returns to "Phone Speakers") 6) Power on F2 headphones - Poweramp applies the K23 preset 7) Settings -> Audio -> Audio Info displays "Output Device: K23" - Phone's BT connections display "Galaxy Watch4" and "F2" as the only connected devices (Edited for readability)
  8. Nope, no luck there either - I unpaired all BT devices (except the watch, since that would force a wipe > reinstall to re-pair, thanks Android Wear 😅) and had this pop up when I tried to go in and re-assign EQ Assignments
  9. Sure, I'll do that and report back later this week
  10. Unfortunately the issue is still happening; I've attached screenshots of the Audio Output screen as well as my phone's Bluetooth menu (and a confirmation that I'm on the version linked above) I did test disconnecting the watch as well, but the issue persisted
  11. Okay, I grabbed it - thanks! I'll report back if I have any further issues - if not, assume it worked lol
  12. I checked in the Play Store and it's not showing an update ("last updated Jul 8, 2023") - it looks like it's still called "Poweramp Music Player (Trial)" though; is that the wrong one?
  13. build-967-bundle-play [967004-988edd05] Full Version 64 bit Also, if you need logcats or anything let me know and I can grab those too
  14. Hello, I am running into this same issue, and I have a Galaxy Watch 4 as well Disconnecting & reconnecting the watch doesn't seem to have any effect unfortunately, and I haven't been able to find any consistency about when it seems to "update" the device that it thinks is connected If there's anything I can do to help gather logs for you guys or anything please let me know - the auto-swapping EQ is one of the big reasons I bought the app in the first place, so I'd really like to have it working again The only other things of note I can think of are... - This 'desync' would happen occasionally on Android 11, but after my phone (forcibly) updated to A13 it has been a much more consistent issue - On the upside, as of the A13 swap it no longer re-changes the selected EQ every time the song changes (so when it's wrong I only have to change it once, at least) - Tasker will occasionally bring up the "new bluetooth device" detected menu I have set up randomly while devices have already been connected (ex. while driving for 15+min it will show up again), so I'm wondering if that lines up with when it "updates" which BT devices are being seen? My Device Info: - Phone Model: OnePlus 8T - OS Version: Android 13 (similar behavior occurred previously on Android 11) - Bluetooth Audio Devices: 4 unique pairs of BT headphones, 1 car BT connection, & 2 BT speakers (all have been 'mis-identified' at least once) - Other Bluetooth Devices: Galaxy Watch 4 (as well as some BT keyboards/mice occasionally) Thanks!
×
×
  • Create New...