Jump to content

PA_1977

Approved Members
  • Posts

    8
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Blogs

Gallery

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

База знаний Poweramp Equalizer

Store

Events

Ideas

Everything posted by PA_1977

  1. @andrewilleyOK. But to the second question I had, the exception is referencing documentsui. Isn't documentsui part of the Storage Access Framework and so that indicates that Poweramp is actually not using a Legacy mode? If it was using a Legacy mode, wouldn't the file access/picker work? I'm not sure of any of this, just trying to understand this a little more. <speech>As time goes by, devices don't or can't be updated to newer Android versions. Android users are then continually being forced to either decide to use different software, stay with existing software, if it's available, or to upgrade their hardware. I'd be happy to stay with existing software, but that's not always possible.</speech>
  2. @flyingdutchmanI'm having the same problem. Please explain how to add that permission. FYI, I'm using Poweramp for an Android 8.1 head unit. On my smartphone, Android 12, I have the Legacy option but this option does not show up on the Android 8.1 head unit. I'm guessing as Poweramp determines it's running Android 8.1 then the Legacy option is not displayed. Perhaps it would be better to show the option/text with a description that PA is running in Legacy mode. When I look at the permissions for the documentsui app that I downloaded from the Google Play Store, the app does not list/ask/require any permissions at all...I thought that was strange, but that's what I see. As for the exception, since it's referencing documentsui, wouldn't that mean it's NOT running in Legacy mode? Permission Denial: opening provider com.android.externalstorage.ExternalStorageProvider from ProcessRecord{166c731 7168:com.android.documentsui/u0a186} (pid=7168, uid=10186) requires that you obtain access using ACTION_OPEN_DOCUMENT or related APIs The specific reference in this text is to com.android.documentsui, for example.
  3. I understand about Google Play being tied to a specific account when you make the purchase. I did not know about the family share. I'll try that. Alternatively, I might add the account head unit account to my phone and install it there with that account and then remove the account from my phone. As for having a separate account on my head unit, there are a number of reasons. First, if someone messes with or accesses your head unit, they will not know your "real" Google account. Many things are tied to your real account. Just knowing it is one piece of the puzzle that makes your account vulnerable. Other reasons include having things in your real account safe. Several Android head units have issues when they sync contacts. Two scenarios...you go for car service or your car is stolen. People can see where you've been, your contacts, etc. Anyway, thanks for the Poweramp / Google Play suggestions. I'll post what happens.
  4. I have an Android Head Unit and I purchased Poweramp for it. I know the purchase is tied to my Google account. However, I use a different Google account on my head unit than on my phone, for security purposes. Does the Poweramp licensing account for this possibility? I'll purchase another license if it's not possible, but I thought it would be a reasonable thing for people with an Android Head Unit to have a separate account. I was thinking/hoping that the licensing would account for this. So, does the licensing account for this?
×
×
  • Create New...