Jump to content

John Titor

Approved Members
  • Posts

    316
  • Joined

  • Last visited

4 Followers

Profile Information

  • Gender
    Male
  • Interests
    Mathematics, Genetics, Astrophysics

Recent Profile Visitors

1,036 profile views

John Titor's Achievements

Advanced Member

Advanced Member (3/3)

  1. It's been requested in the past, and currently queued in to-do.
  2. Ooh, please check it as soon as possible, parametric EQ interface is unusable with this skin update.
  3. Well I was thinking of an "autoplay" feature, like in Spotify, after a playlist reaches an end, a mix of most played songs/ or of tagged similar genres, gets queued immediately, for a continuous playback experience. As for more complex and relevant suggestions/analysis, I think it could fetch song suggestions from last.fm or such sites, and query local file database to see if those suggestions are available for playback.
  4. Thanks for the update mate. Just wanted to let you know the if I choose default option for bottom bar logo in Poweramp EQ, the logo changes to Poweramp, instead of PEQ's. And also is it just me or the Q knobs of parametric EQ stopped showing in PEQ, with this update? Resetting all liv dark skin settings to default doesn't seem to fix it. But when I switching to default skins, it's normal and fine as expected.
  5. Hey what do you want to talk about?
  6. Yeah I was actually thinking of suggesting a feature like how Spotify automatically creates playlists/mixes based on listening habits 🎧
  7. Maybe start with adding a space between "equalizer" and "android" when running the adb command?
  8. It's not "hacking" or "exploiting" a bug, nor it is exploiting a security vulnerability. It's just a hidden switch, for advanced users. PEQ can only equalize players that support equalization and expose their audio sessions. Otherwise, either the devs of those media players have to implement EQ support, or Android will have to allow universal unrestricted audio equalization. Amazon Music, YouTube don't work with PEQ because devs don't want you to use an equalizer on them. Nothing you can do I am afraid, expect convincing the devs. ADB permission is basically "forcing" equalization support.
  9. "Beta" - Android S is still in beta stage, not stable so it is normal to see bugs here and there. Try with the latest stable version of Android (i.e Android 11), should work fine. Max said he will optimize PA for Android S when it reaches stable stage. It's not worth making something out of the previews/betas because Google changes configuration/APIs everytime they post a new beta update.
  10. Weird, I tried a couple of other fonts and looks fine. Seems like it's only happening with ProductSans font.
  11. Yeah, but the underline design seems a bit inconsistent with the rest.
  12. Hello, is this intended or a design bug?
  13. Yes equalizing 20hz frequency also impacts nearby bands unless the bandwidth is very low. But I don't think there's a point of equalizing those frequencies, they are mostly white noise and you can't even hear below 20Hz 🤭
  14. I.... don't think you can hear <20Hz frequencies. Why would you want to equalize the frequencies you can't even hear?
×
×
  • Create New...