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
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.
I bought the smart dock a week ago and could not get it connect to a TV/Monitor.
The smart dock has no problem. Tested the dock with SIII, it works fine.
I am using Sprint stock ROM, no root. Did a reset to factory default, still not working.
Tried this on many TV/Monitors. Had the issue confirmed with Sprint Store / Best buy Samsung experience store / Samsung Technical support.
I was asked by Samsung to send the phone for repair/replacement. I would like to check with your folks before doing that.
Android version 4.12, Hardware version L900.0-9.
f2000sa said:
I bought the smart dock a week ago and cousnuglyot get it connect to a TV/Monitor.
The smart dock has no problem. Tested the dock with SIII, it works fine.
I am using Sprint stock ROM, no root. Did a reset to factory default, still not working.
Tried this on many TV/Monitors. Had the issue confirmed with Sprint Store / Best buy Samsung experience store / Samsung Technical support.
I was asked by Samsung to send the phone for repair/replacement. I would like to check with your folks before doing that.
Android version 4.12, Hardware version L900.0-9.
Click to expand...
Click to collapse
Hi,
I also have the Smart Dock.
I plugged in my phone with all modifications in my signature.
Everything working.
Are you sure it is plugged in correctly and snuggly fit?
Simone said:
Hi,
I also have the Smart Dock.
I plugged in my phone with all modifications in my signature.
Everything working.
Are you sure it is plugged in correctly and snuggly fit?
Click to expand...
Click to collapse
Yes, Phone has docking sound. All other ports are working fine.
I only had problems with TV when in comes to HDMI.
Hi guys.
I'm needing to connect my Gnex to the internet, on a wired-only network. Cellular data is not an option. Wifi is not an option. Bluetooth is not an option.
I've tried dabbling with reverse USB tethering - and it was working for a while - but now, for some reason, it's just not working reliably for me.
So I'm wondering if there's a working micro USB -> Ethernet adapter solution out there?
Do I need some OTG adapter and then an adapter like this connecting to it? Thanks if anyone knows what definitely works (hopefully from your own experience or knowledge of solid accounts of it!) - just don't want to waste money buying something that actually might not work.
My rooted gnex has CM11 stable 4.4.2 on it, if that helps.
Thanks
I bit the bullet and I can confirm, that it is working just fine, absolutely just fine!!! I'm so happy!!!
Even with Google Play Store, app updating is no problem! (it might be because I have the 'hack connectivity' app installed but I'm not sure...I don't think so...I think that only runs when doing reverse USB tethering, which I'm obviously not doing now...)
So, some information to report so it helps anyone else ever embarking on the same quest as me:
- If you're on stock Jelly Bean or above, drivers for some or most common Ethernet->USB adapters (such as the famous AX88772 chip), are ready to go, built-in. It will simply work right away, Internet working, plug and play Internet.
- But luckily, it works also with CM11 February 2014 build and up (and maybe much easier too, but my current build is a February installer build)! Hooray for that, no custom kernel hacking/driver installing needed!!
- Certainly one Ethernet adapter that now has multiple documented reports of success (at least with the gnex), is the Apple Ethernet->USB ('for Macbook Air') adapter. There's a youtube video here and a twitter post here. They're both with stock JB on the gnex, but mine is with CM 11 4.2.2. And yes, I decided to err on the side of superstition and got the same apple adapter, even if it was more than double the price of other perfectly great AX88772 adapters out there...hey, at least it works! And then as for OTG adapter, I just got a random $2 generic black one from ebay. Seems to be working fine, speed seems pretty ok, certainly faster than my WiFi used to be!
- Another bit of into: I read somewhere, that 'Make sure you plug everything into the adapter/OTG cable BEFORE plugging it into your [Android device]. While using a mouse/keyboard/hub I noticed if you plug the OTG cable in first and then a peripheral, the N7 won't recognize it.' But I can report, with the Apple Ethernet adapter, plugging it in after plugging the OTG cable in, works just fine . I just wait about 10-15 seconds to make sure it gets DHCP and away we go .
Hope this helps someone out there, thanks for listening!
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.