I am having tons of issues with Android P and the headphone adapters. When I was running dev preview 1 I had a strange issue where they worked with headphones, but not aux cables. I posted here and no one else was having issues so I just dealt with it for a bit. Then the beta came out and I upgraded. Everything started working again after that and I had no issues for a few days. Then it started acting up again. This time with headphones. It would randomly drop the headphones and start playing out of the speakers. Usually a reconnect or reboot would fix it. Then they just quit all together, nothing I did would make them work at all, headphones or aux. So I reflashed back to Oreo. All worked fine, so I upgraded back to the beta. Once again all was good until a few days and everything quit working again. That is where I currently am now. The other thing of note is that it has charging connected device via USB in the notifications. It seems to me that something changes and it starts seeing the adapters as some sort of USB device and not an audio adapter.
I also have 2 adapters and always test both with the same results. Is anyone else having issues? Could this be a hardware issue? I guess the next step is to go back to Oreo for a while and see if it happens there. Maybe it was just a coincidence that it happened when I upgraded.
I only had the issue on the first Dev preview where my aux cable would not play. On the second beta it is still working perfectly and I've been running it since it came out. I don't use headphones, so I have no tested it. I'd say no it is not a hardware issue and is just due to software issues with the beta. If you are worried about hard ware, go back to stock and see if you have the issue. If not, that will tell you it is the software and issues are expected as it is in beta.
I have tried some more steps. I flashed back to stock by opting out of the beta and it still didn't work. So I flashed back to stock with the factory image and that didn't work either. Now the same thing happens no matter what, it just says its supplying power to the device. I contacted support just to see what I could do about it. They are sending a new dongle to test. I do already have two, but it cant hurt to try another first. I suppose if that still doesn't work, the next step will be a new device.
I'd bet bad USB components. Can you connect to your computer? Bet it's not recognized.
Just got my second replacement for bad port. 1st one was smoking.
Second one behaved like yours.... no headphones or PC connection.
thecaptain0220 said:
I have tried some more steps. I flashed back to stock by opting out of the beta and it still didn't work. So I flashed back to stock with the factory image and that didn't work either. Now the same thing happens no matter what, it just says its supplying power to the device. I contacted support just to see what I could do about it. They are sending a new dongle to test. I do already have two, but it cant hurt to try another first. I suppose if that still doesn't work, the next step will be a new device.
Click to expand...
Click to collapse
Im in the same boat as you. It's suspicious that a lot of people had the same problem.. I dunno if its a HW problem..
I started to have this problem last night. Very frustrating.
akenis said:
I'd bet bad USB components. Can you connect to your computer? Bet it's not recognized.
Just got my second replacement for bad port. 1st one was smoking.
Second one behaved like yours.... no headphones or PC connection.
Click to expand...
Click to collapse
Yeah, it seems like that has started to go too. Tested it and windows says device unrecognized. Still seems to be charging for now.
Frustrating
Ever since the last update it stoped working all together.
This is so frustrating.
Related
I first bought the Samsung brand MHL adapter, and the moment i plugged it into the phone, it simply reboot without displaying anything on the TV. I figured it might be the adapter, so I returned it and bought a 3rd party Menotek adapter only to find the same problem.
The power cable is connected to the adapter, and the adapter to the phone and HDMI cable. I even tried a different power cable, and wall charger and same problem occurs.
Is this a problem with anyone else, one that has a fix? If not I might have to exchange my phone, since this is a feature I really wanted.
Could it be perhaps that the Docomo (Japanese) version uses different electric current that it has to convert, but the adapter can't convert?
i have the exact same problem.
at first i thought it was the cable, so i exchanged for another one... it rebooted.
then i thought maybe it's the tv, so i tried a friend's tv... it rebooted as well.
so i figured it must be the phone. but then since everything else was working perfectly on my phone, i couldn't be bothered to go exchange it... i thought i'd hardly use the mhl if at all. guess you should go exchange yours while you still can though.
I'll contact newegg about it, see if I can get a hassle free exchange.
My biggest guess is that is has something to do with the 110v/220v electrical current that it either doesn't receive enough, or too much, causing it to restart.
I am not sure what a good solution is. At least I am not the only one.
hmm i doubt it's got anything to do with electric currents.
it's my understanding that standard usb power is 5v.
anyways japan uses 110v same as US, and i'm in asia 220v and we're having the same problem.
I had same problem as this but the jelly bean update fixed it....
Sinfamy said:
I'll contact newegg about it, see if I can get a hassle free exchange.
My biggest guess is that is has something to do with the 110v/220v electrical current that it either doesn't receive enough, or too much, causing it to restart.
I am not sure what a good solution is. At least I am not the only one.
Click to expand...
Click to collapse
110/220 is AC, which is converted to DC before it even gets to the usb cord, let alone to the phone. Most chargers will support 110 & 220, so there shouldn't be any issue there.
Are you rooted? Have you tried any other ROMs?
live-evil said:
I had same problem as this but the jelly bean update fixed it....
Click to expand...
Click to collapse
i have the same problem and the jelly bean update doesn't fix this problem, any solutions?
I9250 suffers from defect as well
I have problem. Using i9250 original international version. MHL worked once upon a time, jelly bean didn't fix it, started in 4.0.4, last worked in 4.0.2, dont care about downgrading just to examine, but going back to stock 4.0.1 or 4.0.2 might fix it
Please star issue:
http://code.google.com/p/android/issues/detail?id=34048
Ahh forgot about this thread. Using bigxies deodexed rom got it working for me you can find it in the dev forum here.
Hi, I am having a slight problem and am at a loss.
First of all, my phone is stock. I bought my OTG cable a few months ago and it worked just fine. I was using it to play games with my PS3 remote. However, with less time on my hands, I put the games aside and with it, I was no longer using my OTG cable.
Whenever I plug in the OTG cable, nothing happens and I don't get a notification that a USB device is connected. I have confirmed that it is not the OTG cable as I have tried it on 3 other phones, all of which responded to the cable connecting.
I am not sure when this problem started happening, but I didn't notice until yesterday when I was trying to use my OTG cable. In addition, when I plug in my phone to my laptop, my phone doesn't give me the option to turn on debugging mode. Again, I don't know when this problem actually began. I mention this because I am not sure if it is relevant to my OTG cable problem. Yes, I have checked and debugging mode is enabled.
I am not sure what to do and I have scoured the web trying to find a solution. Maybe I am searching in the wrong places, or maybe I am not just searching correctly, but I figured that my last option was coming here.
I thank you ahead for your time and hope that a solution can be found. I will be more than happy to provide any more details of needed.
leprkon said:
Hi, I am having a slight problem and am at a loss.
First of all, my phone is stock. I bought my OTG cable a few months ago and it worked just fine. I was using it to play games with my PS3 remote. However, with less time on my hands, I put the games aside and with it, I was no longer using my OTG cable.
Whenever I plug in the OTG cable, nothing happens and I don't get a notification that a USB device is connected. I have confirmed that it is not the OTG cable as I have tried it on 3 other phones, all of which responded to the cable connecting.
I am not sure when this problem started happening, but I didn't notice until yesterday when I was trying to use my OTG cable. In addition, when I plug in my phone to my laptop, my phone doesn't give me the option to turn on debugging mode. Again, I don't know when this problem actually began. I mention this because I am not sure if it is relevant to my OTG cable problem. Yes, I have checked and debugging mode is enabled.
I am not sure what to do and I have scoured the web trying to find a solution. Maybe I am searching in the wrong places, or maybe I am not just searching correctly, but I figured that my last option was coming here.
I thank you ahead for your time and hope that a solution can be found. I will be more than happy to provide any more details of needed.
Click to expand...
Click to collapse
Sounds like a bad USB port. You can replace it yourself, or do a warranty exchange. I don't think it's software related but try factory resetting. Or another ROM.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
It sounds similar to what my phone was doing a few days ago. I don't have the OTG, but when I plugged my phone in to the computer, it only went to charge mode and didn't give the USB options, and the computer didn't recognize it at all. I ended up flashing back to stock rooted and it started working again. I flashed CM and then AeonFluxx again and it continued working, so I assume that it was either an app I had installed or something extra I had flashed. Either way, it's working now.
TL;DR Try reflashing before you start tinkering with the hardware, that fixed a similar problem for me.
Sent from my SGH-T999 using xda premium
Alright, thanks guys.
I think I am just going to do a factory reset.
I am able to charge my phone just fine and it connects to the computer just fine as well (Heck, I can do what many others can't....connect to Kies). I have no problems with data transfers either.
So I assume this is a software based problem.
...I may as well root while I am at it....
Haha, I will tinker around a little bit more before I do a factory reset and come back with my results.
Thanks again!
Are you using a kernel with fast charge?
Never mind. You are not rooted so that is not the issue.
Well, it looks like the factory restore didn't solve either issue. So I ended up calling it in and hopefully the replacement phone will work. Gonna have to wait a bit though...GS3's are currently on back order.
Thanks again for the advice though guys! Appreciate it!
leprkon said:
Well, it looks like the factory restore didn't solve either issue. So I ended up calling it in and hopefully the replacement phone will work. Gonna have to wait a bit though...GS3's are currently on back order.
Thanks again for the advice though guys! Appreciate it!
Click to expand...
Click to collapse
Sorry to hear that man, hopefully you get your new S3 soon!
leprkon said:
Well, it looks like the factory restore didn't solve either issue. So I ended up calling it in and hopefully the replacement phone will work. Gonna have to wait a bit though...GS3's are currently on back order.
Thanks again for the advice though guys! Appreciate it!
Click to expand...
Click to collapse
HA i had to wait THREE weeks before FINALLY getting my warranty replacement. Oh and then the replacement was just absolute **** so i sent that back. ANd am now waiting for another device. Good luck buddy! Hope you have better experience with this replacement crap then i do!
Hi, all...
Quick question: did somebody in this forum ever had problems with USB? Mine seems to work only for charging. 'Till the last week, it worked as MSC, with no major problems, then it became faulty, disconnecting and connecting.
Now, to have data connection, is necessary to put pressure at the male connector and hold it this way. I think that it'll require a new PCB, as it doesn't look like software failure. I've googled up and there were other people having trouble with Xperia, but not M, specifically.
So, must I bring it to the assistence?
There's only one way to find out where the source of the problem is: to reflash the ROM.
The USB connector might have got damaged somehow. You can try it with any other device or maybe another xperia m to check for software fault or damage of the USB connector. Try to keep your device at a level below the port for USB in your computer.
elmkzgirxp said:
There's only one way to find out where the source of the problem is: to reflash the ROM.
Click to expand...
Click to collapse
Tried with CM 4.4 (FXP one, that's, by the way, terrifc). But it presented the same failure, then I reverted to the stock 4.3's CWM backup, because I didn't want to reinstall every app. Well, at least I,'m now sure that's a hardware failure.
cooldudeachyut said:
The USB connector might have got damaged somehow. You can try it with any other device or maybe another xperia m to check for software fault or damage of the USB connector. Try to keep your device at a level below the port for USB in your computer.
Click to expand...
Click to collapse
Tried everything (or near everything). It charges, however. There are a little failure, but it should work if the phone is left quiet or not shaken while using it connected to the outlet.
So, for now, I'm going to transfer things using Samba or detached SD (the last being the fastest). Later I'll send it for repair... Shame it perhaps won't work with OTG (a feature I've been searching for, when I bought XM), but, when having money, I'm going to get it fixed.
Thanks for the replies, anyway.
prppedro said:
Tried with CM 4.4 (FXP one, that's, by the way, terrifc). But it presented the same failure, then I reverted to the stock 4.3's CWM backup, because I didn't want to reinstall every app. Well, at least I,'m now sure that's a hardware failure.
Tried everything (or near everything). It charges, however. There are a little failure, but it should work if the phone is left quiet or not shaken while using it connected to the outlet.
So, for now, I'm going to transfer things using Samba or detached SD (the last being the fastest). Later I'll send it for repair... Shame it perhaps won't work with OTG (a feature I've been searching for, when I bought XM), but, when having money, I'm going to get it fixed.
Thanks for the replies, anyway.
Click to expand...
Click to collapse
Most problems don't get fixed just by restoring /system. You have to flash the whole
ROM, if it failed with system. If you're worried so much about your data, then just backup /data then restore it afterwards...
I also have this problem.i just elevates the charger cable and its charging but its not working if its not elevated.tried different charger but the problem still persist.so i conclude that its the port in the phone that s malfunctioning.
Sent from my C1905 using XDA Premium 4 mobile app
even my usb cable didn't work. I tried connecting other mobiles too but dint work. And i realized its not problem with the os, but the cable itself was fault!
This was put off for a while because it happened before, so I at the time I had another s3 (busted digi), was another T-mobile variant. And I just switched mobos and speakers (oddly didn't work with "broken" mobos one). So after I finished that it booted and everything worked fine. Fast forward a few days and I installed 6.0.1 cm13 (unofficial I believe).
I had tried a ton of roms, but onto the point, there was another rom I wanted to try and guess what, it didn't work. It didn't kill the mobo (other didn't either), but it doesn't want to boot into the os, nor recovery nor even odin. BUT, it's still being read by my laptop, as in I can hear the connecting and disconnecting sounds, and it even charges for about 5 or 6 seconds before shutting off.
It still plugs in charges, but it won't boot. Can anyone help? or point me in a direction that would help?
I've heard of Jtags and all that, but atm I can't exactly do that, nor do I trust it very much. So any help would be amazing, I really love this s3.
If you found something let me as well because i did the same.
But sadly mine isn't even charging but i do hear it connect to my laptop and led turns on if i take out the battery and connect the wall charger.
This is not my device so please help me fix it asap.
message me if you could talk to me on hangouts.
Does anything appear on the screen? Does the phone show up as a new device named "QHUSB loader", or something like that, in Device Manager?
Does anyone know of custom Roms for the OP3 that Android Auto works well on? I have tried OOS 3.1.3, unofficial CM13, and Bliss.
anybody?
Apparently not
I am using stock ROM and Android Auto is working fine. Except that sometimes I have to go to the car dashboard and activate the device for Android Auto. This does not happen all the time.
In my 2016 Golf 7 everything working like charm, no issues, less than with my S6 before...
That great! I also have a very golf and could not decide if I should buy or not the op3
LE: what cable are you using between the OP3 and the car ?
Well you two are the only ones I've heard of that aren't having issues with crashing/ disconnects. Consists yourselves lucky.
dindoliya said:
I am using stock ROM and Android Auto is working fine. Except that sometimes I have to go to the car dashboard and activate the device for Android Auto. This does not happen all the time.
Click to expand...
Click to collapse
Which deck do you have @dindoliya ?
Anyone who has seen my various post with problems already know I am using the Pioneer AVH-4100NEX and factory cable with no luck, but works fine with 1+1 and Note 5 and even S5.
IronAddict said:
Which deck do you have @dindoliya ?
Anyone who has seen my various post with problems already know I am using the Pioneer AVH-4100NEX and factory cable with no luck, but works fine with 1+1 and Note 5 and even S5.
Click to expand...
Click to collapse
Hi, I will check which deck is there is my Chevy Volt 2016 and get back to you. From what I can recall, it is probably a Panasonic.
Just wanted to let everyone know who may come here searching for similar problems. I did finally get mine working with a different aftermarket cable. Have had no disconnects with AA or BT. Ironically it was a cable that will not even allow DASH charging but will work with Android Auto.
Ok, after 2 Weeks use, I have to say, that the only combination I get this to work without disconnects is with the original cable.
I tryed different cable from cableconnection over anker to belkin, none of them worked properly with op3... Some even get no connection at all, others disconnect connection after a while...
Only with the original cable I get this working properly... really strange...
I will make one test again this evening with original cable. Never used this since the update to 3.2.1, so perhaps this is the reason...
I'll let you know...
Does it mean that mirrorlink is supported by 1+3 in general?
Never had any luck with the factory cable as well as a third party cable. I did however try a third cable which has been working almost flawlessly.
For those interested it's this one:
https://www.amazon.com/dp/B013187HZS/ref=cm_sw_r_other_apa_MbxGxbTJ8QTRK
Ok, verifyed..... Form me in My 2016 golf 7 only the original dash charge cable works without disconnects with 3.2.1.
I will order a second one now....
Don't know what is so different on this cable but something hast to be...
IronAddict said:
Just wanted to let everyone know who may come here searching for similar problems. I did finally get mine working with a different aftermarket cable. Have had no disconnects with AA or BT. Ironically it was a cable that will not even allow DASH charging but will work with Android Auto.
Click to expand...
Click to collapse
Very good news !!!! Thanks for taking the time to tell us.
Can I ask how you got this working? I'm getting frequent disconnects with the op2 cable and third party type c cables. Not tried the dash cable as yet
since I'm using CM13 never got any disconnecty on android auto.... perhaps OOS is the reason for that issue....
I'm not sure how big a part OOS plays. The cable i linked a few posts up has worked for me.
I get occasional disconnects too. Not that bad, but annoying at times. All it takes is unplug/plug the phone back to get it going (Pioneer AVH-4200NEX). Noticed that happens most often when I'm driving in an underground garage and the phone is seeking signal (2G especially). Cable I'm using is 3rd party Amazon sourced one (flat cable). I'll see if I can get a properly RF-shielded USB cable to see if it makes connection more reliable.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
slg60 said:
In my 2016 Golf 7 everything working like charm, no issues, less than with my S6 before...
Click to expand...
Click to collapse
You've got '17 S6 (Audi)?
i cant get android auto to work on and cm13 rom. using stock cable. when i run stock oos 326 it works fine.
anyone got any ideas on what else works?
want to run a cm13 rom