Related
hi.
i just got a MHL cable for my SGS2
when i plugged it to my tv, it cuts of the wifi and the phone signal... so i can't receive calls or surf the internet ...
i tried two different phones with different roms and different kernels and got the same result...
anyone had this problem and knows how to use MHL and have WIFI and phone signal?
thanks
What cable? Samsung's or generic?
Have you tried this on stock unrooted or rooted firmware?
Omega Frost said:
What cable? Samsung's or generic?
Click to expand...
Click to collapse
generic cable.
tonycfc said:
Have you tried this on stock unrooted or rooted firmware?
Click to expand...
Click to collapse
i tried custom roms...
one of them is 2.3.5 and the other one is 2.3.4
the two devices are rooted
I have the OEM Samsung adapter and it used to make my phone do the same thing. I sold the phone ans ended up buying another one and the second phone works perfect with it.
I am running the leomar75 rom with the ragemod 1.1b kernel
so you say this is a problem with the device itself?
I also have a generic adapter but mine works for a few seconds and then blank.....not supported. sometimes it gives green screen on my tv. I've tried on stock and custom roms. If it's the phone than it should be addressed t Samsung.
update:
I have to put my phone in offline mode to be able to use it.....
i tried the same cable on other tv...
on the other tv the phone signal stayed on (and i even received a call without any problem) but i still had no WIFI...
maybe its important, but i tried the other tv away from home..
at my home the phone signal is weak all the time
i have a stock phone w/ generic POWERED mhl cable and the wifi cuts off when plugged in. wth?
still no fix for this issue?? i just got a MHL cable yesterday and is really annoying
I called samsung and they said that it is designed to cut off wifi. it may look like u r still connected, but u will be unable to surf the net. they said the reason this was done was to prevent fickering of the video if you were browsing the net or something.
so ,there's no hope than MHL work with wifi?
erebocln said:
so ,there's no hope than MHL work with wifi?
Click to expand...
Click to collapse
dont ask me. call samsung. just telling u what they told me. the way it is designed wifi is shut off when mhl cables are used.
would be interesting to see if anyone got wifi to work w/ mhl plugged in.
bms231 said:
dont ask me. call samsung. just telling u what they told me. the way it is designed wifi is shut off when mhl cables are used.
would be interesting to see if anyone got wifi to work w/ mhl plugged in.
Click to expand...
Click to collapse
I have had WIFI working with MHL connected for months. I've could surf the web AND stream flash videos in a room with GPRS coverage ONLY (which rules out the "you were surfing through packet data" variable) while connected to my Samsung HD plasma with no problems.
So I certainly have no idea what your Sammy rep was talking about.
BTW, I'm using the official, korean spec MHL cables I got from ExportPrive. But I'm positive it should work the same with the international MHL cables.
Bought a non Samsung MHL cable today and it worked perfectly fine, it even worked when providing power via a microUSB cable connected from a spare USB socket in my nearby router.
Another user on a forum I frequent has similar issues with WiFi dropping and had this solution:
JAMAL said:
Fixed my mhl problem, I think it was a lack of power as its ok with my HP touchpad 2amp charger
Click to expand...
Click to collapse
So maybe try a different charger?
Another OcUK user
My MHL problem is fixed now, i tested it for 15 minutes and wifi and gsm signal were fine
I was just about to post it in this thread and then saw your post haha
IF anyone decides to mess about with chargers/adapters with higher currents then do it at your own risk and read up if its ok to do so with your phone etc..!
I try with my nokia N900 charger and still nothing, I'm using the official MHL cable
erebocln said:
I try with my nokia N900 charger and still nothing, I'm using the official MHL cable
Click to expand...
Click to collapse
Rom/kernel issue?
I'm using a Nokia AC10X (1200ma charger) + original MHL cable + Siyah 2.1rc2 (at that time, now running 2.1.1) + VR2.4.2 (don't ask) = no connection issues what so ever while in HDMI out.
Either that or it's a hardware problem with the cable or your phone.
eiraku said:
Rom/kernel issue?
I'm using a Nokia AC10X (1200ma charger) + original MHL cable + Siyah 2.1rc2 (at that time, now running 2.1.1) + VR2.4.2 (don't ask) = no connection issues what so ever while in HDMI out.
Either that or it's a hardware problem with the cable or your phone.
Click to expand...
Click to collapse
im using 2.3.5 KI4 rooted , sony bravia tv(two of them) , if I turn the tv off wifi works perfect again even with MHL connected, the HDMI cable is generic, excuse me about my bad english
eiraku said:
Rom/kernel issue?
I'm using a Nokia AC10X (1200ma charger) + original MHL cable + Siyah 2.1rc2 (at that time, now running 2.1.1) + VR2.4.2 (don't ask) = no connection issues what so ever while in HDMI out.
Either that or it's a hardware problem with the cable or your phone.
Click to expand...
Click to collapse
After install Siyah 2.1, everything works excelent!!!!
Thank you so much
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 there, I bought an MHL cable from Ebay and was trying to connect the phone with TV. I have connected the power cord and did all the setup as required. The phone was charging, but the TV was just showing 'No Signal' as it was not detecting the phone. The adapter looks like a Chinese import at 8$. I tried many suggestion as people have posted here including the connection order of TV, Phone etc and but with no luck. Can someone please help me out here? GNexus is not officially launched in India, but S2 is. So do you think buying the original Samsung S2 adapter will work for Nexus? Thanks in advance!
I have no luck with MHL on this phone. Broken on 99% if not 100% of custom ROM and kernels. Every time I sought support for it I was just told to "use stock ROM and kernel"
Even on doing that my screen glitches and boom. Reboot. Bootloops until I unplug it. I wish you good luck and if you figure out how to get it working, shoot me a pm
Sent from my Galaxy Nexus using Tapatalk
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.