Jump to content


Approved Members
  • Content Count

  • Joined

  • Last visited

About speedingcheetah

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There are no doubt other issues with PA in Q, with the exception of the afore mentioned Settings import/export issues, seems to be minor UI / Theme issues in my brief testing as of yet. When I enable the "Override Force-Dark mode" in Dev settings, the Song Title and Artist that show on the now playing screen (on top of the album art) is just white bars, cant read text. The buttons become inverted color (white) and the seek bars as well. EQ dials and sliders. Lock screen always blurs the cover art to the point it is pretty much not there. Not sure how this new Android setting does it in the back-end, but it makes all apps that support a Dark mode dark reguard less of the apps settings. Anywho, feel free to hit me up for any testing or diag things needed for a update for PA on Q. Though I would think that the dev Max would be proactive enough to have a supported device(or a emulator) on Q beta to test out his app to test for issues... Like I said before, Q's public release for Pixel phones (and phones that get near immediate updates, like Essential Nokia etc) is about a month away....so has been reported anyway.
  2. They have already give devs plenty of notice on their intended file system changes shortly after P was released. It was first spotted in code during the P beta. Users only have now seen it implemented when 1st Q beta came out early this year. There is also to be a bigger change, again, next year, with complete sandboxing of apps file access, but Google decided to not implement that into Q, but it WILL be done in R. Documentation on that can be found quite easily. If app devs want to keep their apps functional and relevant, they have to keep up and adhere to the ever growing customer demand for privacy and security and thus what ever the OS manufacture put into place to address those demands. Apple has been doing it for many years....Google is only following suit. And shifting the blame to Google is a cop-out and not saying anything useful.....after all, MS has made several drastic changes to their products over the years that were not well received (no start menu) and some that were...do users have a choice...nope. Hopefully, current users, who upgrade from P to Q, it will retain their P.A settings. But they will have to setup everything from scratch if they get a new device. Overall, I do not see how this file path is such a contestable issue....just make the import/export option ask for a user selectable path and file, same as the Media library selector is. Problem solved? then when Google changes the file system locations again, u don't have to worry about where things got moved to.
  3. But IT IS related, indirectly....in that, i am trying to restore my EQ settings, via importing the SETTINGS file....but can not because of this issue. If i could import my settings, then I would have not now need to nitpick over not having the exact EQ db values to be able to manually re-create my settings. I have over 15 custom EQs that have taken me years to get just right. 💀 I am very glad I bought the 3a to test the Q beta on....I am now able to test the apps I use everyday for functionality first, before I let my Pixel 3 update to Q. Already found a few that don't work right and need to be updated/fixed.
  4. Thats a load of crap reason to not do it...exact values wont give much not always exact...as opposed to just litterly guessing or eyeballing it??! U set a set db value when u move the slider, it is then saved as part of the EQ config....it make no difference how that value is treated on the backend....it is still set to that base number, to witch when a user needs to re-set their settings from scratch, really could use. Especially if their device is on the soon to be Released Android Q, as you can not import or export the apps settings.
  5. Im not sure what u mean. I can use a file explorer app and go to the same folder that I do on my non Q device, sdcard (Internal Storage), Android, data, com.maxmpz.audioplayer. I put the settings files in there, PA cant find it. or try to get PA to save one...and it says not valid path. Seems to me the app is hard coded to go to a path that no longer exists (storage/emulated/0/). The correct path is /sdcard/Android/data/com.maxmpz.audioplayer I can set my Library path fine....but have no option to adjust the path it looks for the settings files in. Personally, if I were designing this app, I would make it so that its "Settings" would save to the users media library folder that u set. That is where my Playlist files reside as well, for easy backup and restore, everything is just there in one folder. If this app has hard coded paths for its app/system files, then that may screw up other things that are stored there I would think. This will be a bigger issue very very soon , as Android Q (10) is to be released sometime next month, August, which is very close.
  6. I have a Pixel 3a that I am using to test Android Q beta on.... Poweramp can read my media library on internal storage fine. However, I can not get it to import my settings file from my main phone, a Pixel 3, need the EQ settings etc to do my testing. I can not export the settings either. I give cant read cant write error. See attached. Poweramp does have Storage permission in the System settings. The message in the note for the Q beta do mention a change in how things are stored in the structure of the file system now in Q....perhaps Poweramp needs to be updated to support this change in file paths? I could set the EQ settings back up manually....if only the EQ showed its db levels for the slider bars...would make is very easy. (feature request i suppose?)
  7. So, an app update appeared a short time ago today (V3-build-811-play) With "better USB DAC recognition on some devices" listed in the the changes. This new version, both the Google USB C to AUX and the MOSHI adapter are recognized by PA as a USB DAC now and High Res output on my Pixel 3! That is excellent improvement. However, my FiiO Alpen 2 E17K USB DAC still is stuck at 16/48 and won't do its proper 24/96 that it will do on my 1st gen Pixel XL. That DAC would nice to get working correctly, but I just picked up a FiiO BTR3 that is BT 5.0 and LDAC and that sounds pretty damn close in quality to the wired E17K and makes my VMODA Crossfade Wireless headphones proper BT wireless. (the BT chip built into the headphones is only SBC). Thanks for your continued work on Poweramp!
  8. I have a Fiio Aplen 2 E17K USB DAC amplifier. 24bit/96Khz Use it on my Pixel XL (1st Gen) and now my new Pixel 3. When not connected to anything, it defaults to displaying 16bit/48Khz. when u connect it to a deice, I changes and you can hear a slight noise in the headphones when it does. On the Pixel XL, the Fiio DAC lcd screen says when its connected, 24bit/96Khz, stays that way. Power Amp detects the DAC by name and says it is outputting 32bit/96Khz OpenSL ES High-Res. On the new Pixel 3, the Fiio DAC lcd screen says when first connected 24/96, but as soon as any sound is made , it changes to 16bit/48Khz and stays at that. Power Amp detects the DAC by name and says it is outputting 24bit/48Khz OpenSL ES High-Res. What is going on here between these 2 phones? I have used this DAC along with the current version of PA v3 on other phones, Nexus 5X, Moto X Pure, and those all behave identical to the 1st gen Pixel XL. The audio, to me, sounds a bit better, more clarity and sound stage when on the Pixel XL, but I am a bit confused as to why PA is doing 32bit output in that use case. And now, of course, why the Pixel 3 isnt doing 96Khz when the DAC supports it, and why the DAC is reverting that is doing 24/28. Maybe things is just not being reporting correctly and when PA says its doing 32bit, it actually is doing 24, and on the P3, it says 24, but it actually is 16??? Help? Any ideas?
  9. Moshi USB-C Digital Audio Adapter (2nd gen) with charging P/N: 99MO084246 24-bit/96khz Currently is read as Internal Headphone/AUX and is locked to 16bit/48khz and no HD Audio support. Since the AUX jack and built in DAC's on the phone are going away, the standard on all Flagship phones now....these external USB DAC's adapters "dongles" are the only way and support for them is a must to stay a usable high quality audio music player app.
  10. For me, the point of this topic thread...is that the USB dongle adapter DAC is not detected as an external DAC with HD audio support, as it is and should be. AND that one adapter that is advertised to do 24-bit/96khz, is not detected as so or outputs in that way with Poweramp...where another USB DAC is detected and does. I know this Moshi adapter does work at 24-bit/96khz when i hook up to my pc. And yes, there a big difference in audio quality when the DAC is stuck in 16bit/48khz.
  11. The new look is certainly more modern looking. Sleek. I don't like Swipe navigation....but the phones OS themselves are going this way...so, can't avoid this it seems. I struggle allot with this, but am starting to get used to it and re-train my self. The biggest negative i have with the new UI is the terrible behind the buttons Seek "bar". It is very hard to use. Much preferred the previous V2 style of a simple and separated line(bar) under the buttons.
  12. That doesn't make sense. Why would they do this tough as they have an independent DAC in the adapter...same as my Fiio USB DAC.
  • Create New...