
ADi
-
Content Count
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Poweramp Knowledge Base
База знаний Poweramp
Poweramp知识库
Poweramp Equalizer Knowledge Base
База знаний Poweramp Equalizer
Posts posted by ADi
-
-
7 minutes ago, ilyandroid said:
Thanks for the link man. Appreciate it
-
Well that sucks. Hope the devs fix it up because most of the time I'm on my Bluetooth headphones and it's really annoying to turn on the phone everytime I want pause or change the song.
-
7 minutes ago, ilyandroid said:
I have the same problem on my ZUK Z2 running on AOSP Extended v5.5 official android 8.1.0. Kernel 3.18.71-lineageos+. ROM is stable. Unlock is purchased on Google Play. Poweramp v3 Build 793. Tested on 2 wireless headsets. The first run of Poweramp after downloading from Google Play is without any issues. When I close and open the app again bluethooth headsets are only able to control volume. I can't skip track or pause the app. Reinstallation of the app helps.
Do you experience the same issue even after the reinstallation or is it rectified?
-
9 hours ago, dwang040 said:
Are you referring to the snapdragon 810? If I'm not mistaken, the OnePlus 2 uses the snapdragon 810, and the 810 does indeed support high res. I do not have the same phone, but I do have a htc m9 (also uses snapdragon 810) and I do have hi res support. I think what the issue may be for you though is that you are using a custom rom and kernel. That can lead to some "compatibility issues" and I would assume that's what's causing you the issue. I had a similar problem where the hi res feature was not compatible with my custom rom and kernel, but somehow, in the previous update, that was fixed (maybe something else was the culprit but idk. hi res worked, then an update came and it wasn't working, and now it is working again regardless of rom and kernal). Your best bet would be to fill out that "hi res support" forum post and hope that maybe it get's updated. Though, in all honesty, I doubt people are really missing out on much as they assume they are when it comes to hi res vs the normal audio playback device (specifically wired capabilities). Even with some of the most top notch headphones and iems, I doubt the difference between them is significant enough or even near noticeable for everyday music listening. If you're talking about wireless, then I can't say much about stuff like aptX and what not. but yeah, like I mentioned earlier, your best bet would be to add a post to that "hi res support" thread.
Ya I totally agree with you. With formats like MP3 most of the quality would've been lost already. Also ive heard the DAC plays a major role when it comes to good quality and lossless output. All I wanted to mention was that the hi-res Support is present but I cant turn it on. Anyway I posted it on the other forum and thank you for the detailed reply.
-
Hi. I have OnePlus 2 running on Lineage OS 15.1 with bluebolt custom kernel, Poweramp V3 build 793. When connected to a Bluetooth headphones, I am not able to play/pause or skip to next or previous songs. Only the volume can be changed.
-
On 8/15/2018 at 8:07 PM, clever_man said:
@ADi, does 801 SoC support Hi-Res Audio?
I'm not sure @clever__man and correct me if I'm wrong but from what I've heard it should be able to if you are in stock rom.
-
17 hours ago, Gerolf Vent said:
OnePlus 2 (Snapdragon 810)
Android 8.1 / LineageOS 15
Build 793
On Android 6 Hi-Res worked perfectly.
Error:
Output failed=NativePlugin[187893664] uniq_name=com.maxmpz.audioplayer/output.athd id=5 flags=80000003 name=Hi-Res Output
java.lang.Exception
at com.maxmpz.audioplayer.player.PlayerService$9.run(":1681)
at java.lang.Thread.run(Thread.java:764)Same problem here.
-
I'm running beta V3 build 793. Requesting hi-res audio support for Lineage OS 15.1.
-
Hi. I'm using OnePlus 2 running on LOS 15.1 with blue bolt custom kernel. Even though there is an option to select hi-res audio, when I do so it doesn't show 'active.' instead the toggle switch gets turned on but the opengl output will still be active.
Bluetooth problem
in Bug Reports
Posted
Have you tried closing and opening the app again? If that works try rebooting once. If both works then the problem is kinda fixed I guess. Just let me know what happens.