gd89 Posted September 30, 2017 Share Posted September 30, 2017 I have a Panasonic headset for my OnePlus 5 phone. However, the headset button does not work when I reconnect the headset after some time since the last disconnect. I have activated the headset button option, as well as wakelock and keep awake features. I have also locked the app to prevent from killing it. The high priority feature also does not help. Kindly advise. Link to comment Share on other sites More sharing options...
andrewilley Posted September 30, 2017 Share Posted September 30, 2017 Does this happen while Poweramp app is the current app, or only while it is in the background and dormant? Andre Link to comment Share on other sites More sharing options...
gd89 Posted October 2, 2017 Author Share Posted October 2, 2017 When it is in the background/dormant. But then the button also does not work when the app is launched. I have to manually 'uncheck' and 'check' the headset button option Link to comment Share on other sites More sharing options...
andrewilley Posted October 2, 2017 Share Posted October 2, 2017 Sounds like the phone is doing something to kill the service that handles button interaction, which unless Poweramp is aware of it assumes is still working (hence turning it off and on again solves the issue for the time being). Have you asked in a OnePlus forum if they know why it is doing this? Andre Link to comment Share on other sites More sharing options...
Sciamy Posted October 2, 2017 Share Posted October 2, 2017 I have the huawei P10. Yesterday i done the last update. Immediately after is coming this bug. Link to comment Share on other sites More sharing options...
gd89 Posted October 3, 2017 Author Share Posted October 3, 2017 @andrewilley Can you tell me what the service is called? Maybe I can try 'force enabling' it. Meanwhile I will also check on OnePlus forums. Do you think upgrading the PA v3 would help resolve this? Link to comment Share on other sites More sharing options...
andrewilley Posted October 3, 2017 Share Posted October 3, 2017 It's worth a try upgrading to V3, although I don't think much is different in that area of the code. You'll need to at some point anyway as v2 will no longer receive updates. Andre Link to comment Share on other sites More sharing options...
gd89 Posted October 7, 2017 Author Share Posted October 7, 2017 @andrewilley Upgrading to v3 solved the problem! Thanks Link to comment Share on other sites More sharing options...
andrewilley Posted October 8, 2017 Share Posted October 8, 2017 Great, glad that helped. Andre Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.