ivoanjo 33 Posted April 26, 2020 Share Posted April 26, 2020 I've had this issue ever since I got my Pro1, but I finally got annoyed enough to ask about it. I'm running the latest version of the stock firmware (20200306), and every time I plug in my 3.5mm wired headphones (Sony MDR-E829V) the Pro1 takes around 8 seconds to recognize that they are plugged in and switch over the sound. This means that quite often I plug in my headphones, press play on something, and then awkwardly get sound over the loudspeakers for a few seconds until it's switched over. And since I never had a device that behaved like this (and I've used these kinds of Sony headphones for 15+ years), I always forget about it. Am I alone in this? 1 1 Quote Link to post Share on other sites
EskeRahn 5,460 Posted April 26, 2020 Share Posted April 26, 2020 How odd! It takes less than 1 sec here. (different headset though) 1 Quote Link to post Share on other sites
FBela 23 Posted April 26, 2020 Share Posted April 26, 2020 I used it with Sennheiser and Xiaomi wired headsets, both switching within 1 second. 1 Quote Link to post Share on other sites
Hook 3,020 Posted April 26, 2020 Share Posted April 26, 2020 Same here-- switch less than 1 sec. 1 Quote Link to post Share on other sites
anonim001 105 Posted April 26, 2020 Share Posted April 26, 2020 The headset model should not have anything to say here - in Jack socket the plug is recognized over a hardware switch, so even if You input the plug without anything connected to it the switch closes and should be recognized, unless there is some real hardware/software issue. 2 Quote Link to post Share on other sites
ivoanjo 33 Posted April 28, 2020 Author Share Posted April 28, 2020 (edited) Thanks everyone for your replies. Just to clarify, I've recorded a video with three different headphones (including the AKG headphones shipped with the Galaxy Note 8 ) all suffering from this issue: It's good that this seems something more specific to my device's software or (shudders) hardware, not a generic issue that affects everyone. Any suggestions on how to debug it, other than factory reset? I was trying to avoid needing to redo my entire setup just for this issue 😕 Edited April 28, 2020 by ivoanjo 1 Quote Link to post Share on other sites
EskeRahn 5,460 Posted April 29, 2020 Share Posted April 29, 2020 10 hours ago, ivoanjo said: It's good that this seems something more specific to my device's software or (shudders) hardware, not a generic issue that affects everyone. It is clearly a software bug somehow. Note how the icon appears (but quickly disappears again) when you plug in. So I would say that it is extremely likely that a factory restore would fix it. BUT before walking that route, you might want to see if there could be any app installed that somehow could be affiliated, that it might be worth trying to uninstall (temporarily). Making a backup of everything can be quite tedious, and restoring everything might reintroduce the bug, as we have no clue where it is... I tried googling to see if someone has the similar problem on other hardware, and found this, but not with any relevant fix. The use of another set sounds extremely unlikely in your case already trying three. But it indicates that it is a known phenomena in Android that can be triggered by 'something'... You might optimistically try simply holding the power button in for some 7 seconds, that boots the phone slightly deeper than just a "restart" (AFAIK), and with some luck that just might help... 1 Quote Link to post Share on other sites
EskeRahn 5,460 Posted April 29, 2020 Share Posted April 29, 2020 You might also try killing stuff running that does not have to run. Settings, System, Advanced, Developer options (*), Running Services. (*) If yo do not see "Develop options", go to Settings, System, About phone, Click Build numerous times. Here is what I usually leave running: Quote Link to post Share on other sites
ivoanjo 33 Posted May 2, 2020 Author Share Posted May 2, 2020 Thanks for the suggestions. I tried the long-press-to-force-reboot, as well as stopping almost all processes that are not system ones, and no dice. I'm not going to do the factory reset -- I only end up using the headphones more often during this... unusual times of staying at home, so it's not worth the reinstall. Quote Link to post Share on other sites
EskeRahn 5,460 Posted May 2, 2020 Share Posted May 2, 2020 Yes, sound like a factory reset would be a drastic measure. Let us hope that the restart following a future software upgrade might de the trick. Just a thought/guess. When you killed a lot of apps and reinserted the headphones, did that start/wake any additional process? If so killing that and clearing its cache&data might be worth at try. Quote Link to post Share on other sites
ivoanjo 33 Posted May 3, 2020 Author Share Posted May 3, 2020 17 hours ago, EskeRahn said: Just a thought/guess. When you killed a lot of apps and reinserted the headphones, did that start/wake any additional process? If so killing that and clearing its cache&data might be worth at try. Not that I noticed. I was able to kill most processes (other than tasker, that even when disabled somehow kept a background process). Quote Link to post Share on other sites
EskeRahn 5,460 Posted May 3, 2020 Share Posted May 3, 2020 1 hour ago, ivoanjo said: Not that I noticed. I was able to kill most processes (other than tasker, that even when disabled somehow kept a background process). Yes, most people have the intuitive - but wrong - perception that disabling a process also stops it. You need to explicitly stop a process after disabling it. see e.g. this Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.