Heya guys
Im having a strange problem with my only 1 week old Transformer TF101. I was told, this would be the place to ask, so I really hope someone can assist me
I bought a Transformer as a HDMI-out multimedia solution for my TV and the first week everything worked like a charm. But suddenly, for no reason, it wont show on my LG 50" Plasma. I then tried it on my older Samsung in the bedroom and to my surprise there was no problems connecting the tablet, it showed right away.
I then figured, cable? So I took the cable from the bedroom, but with no succes. HDMI-in on TV then, i thought? But nope. Everything else shows connecting it with the TV's HDMI. PC etc.
I am currently sitting with tablet I cannot use for the purpose I bought it for. What to do? Any help, is very much appreciated!
Ps. my plasma tells that something is connected to the HDMi and even tries to connect, but the tablet does nothing and then the TV says "no signal".
There is no way to change any setting for hdmi on the tf, so I guess yor tv is the problem. Maybe you changed a setting? I only had a problem wit over- and underscan. Try looking into the tv menu... thats my guess
Sent from my Transformer TF101 using Tapatalk
towlie288 said:
There is no way to change any setting for hdmi on the tf, so I guess yor tv is the problem. Maybe you changed a setting? I only had a problem wit over- and underscan. Try looking into the tv menu... thats my guess
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I didnt change anything in the TV's menu and ive looked for settings that could have an influence, but non found. I had the tablet unplugged and when I plugged it to the HDMI the next day, it didnt work, after working 100% for almost a week.
Try a custom kernel. Last year the tf had trouble displaying on some TVs like Sony. About September or so an update came out that solved the issue. I'm guessing the stock kernel still has trouble with LG TVs.
goodintentions said:
Try a custom kernel. Last year the tf had trouble displaying on some TVs like Sony. About September or so an update came out that solved the issue. I'm guessing the stock kernel still has trouble with LG TVs.
Click to expand...
Click to collapse
But if it worked? And to be honest, I wouldn't want to have to flash a custom kernel just for simple HDMI out!
And that it works on the other TVs is also strange. I have a LG Monitor and have no problems...
You could just try reseting it to ensure that it's not something in the tablet. Or reset the TV?
So.... something strange has happened.
After not having worked for 2 days, it suddenly worked again. The tablet detects the connected HDMI cabel and the picture shows on the plasma instantly. Im like what the ****? I havent changed anything on neither the tablet or the TV. Dunno if I should be happy or worried, since id like for it to work, when I actually have to use it
I heard from someone that its better to use the HDMI/DVI, than the regular HDMI on the TV, im currently using. Can anyone confirm this?
Related
I am on my 1st warranty phone of the G2X and it was having overheating issues, i think i have solved that (I wasn't formating the /system in clockwordmod, so i think old files were conflicting and causing cpu time to be eaten and burn up my phone, now it's staying a good 31c while asleep and unplugged, but now i can't use the hdmi out on the TV, i can with my computer monitor but not my tv, on my brand new g2x, the one before i got this warranty one, the hdmi to my tv worked, but it was overheating...but most likely not becuase of the phone but because i was going from rom to rom incorrectly....i have only tried it with Ultimate G2x 1.0 ROM, I am probably going to switch to CM7 w/ faux123's new 0.1.7 kernel if alot of ppl say good things about the new battery reading changes. idk i just wanted to see if other people have HDMI issues with diff tv's or diff roms....i work by a radio shack so i'm going to try it on one of their tvs.
pychobj2001 said:
I am on my 1st warranty phone of the G2X and it was having overheating issues, i think i have solved that (I wasn't formating the /system in clockwordmod, so i think old files were conflicting and causing cpu time to be eaten and burn up my phone, now it's staying a good 31c while asleep and unplugged, but now i can't use the hdmi out on the TV, i can with my computer monitor but not my tv, on my brand new g2x, the one before i got this warranty one, the hdmi to my tv worked, but it was overheating...but most likely not becuase of the phone but because i was going from rom to rom incorrectly....i have only tried it with Ultimate G2x 1.0 ROM, I am probably going to switch to CM7 w/ faux123's new 0.1.7 kernel if alot of ppl say good things about the new battery reading changes. idk i just wanted to see if other people have HDMI issues with diff tv's or diff roms....i work by a radio shack so i'm going to try it on one of their tvs.
Click to expand...
Click to collapse
I have this same problem, it is a hardware problem caused by using an HDMI cord that caused a short. Lots of people are getting this due to using monoprice cords. Search g2x HDMI monoprice. Unfortunately it is a hardware problem that cannot be fixed, when you sent in your phone on warranty they probably sent you back a refurbished that was broken by someone else. You need to send it back ASAP and ask for new phone not a refurbished.
well if the output of the phone was burnt out, then it wouldn't work either way. Just make sure all the settings are correct. Your monitor is probably 1080p or better. Your TV?
There were some issues with settings and auto. There could be a number of issues at hand and/or it could just be the phone.
I would try another rom. CM7's works pretty well. There are no settings and AUTO is hardcoded.
I've played with the HDMI out with my monitor and while it works, sometimes I had to screw with the orientation, unplug/replug, toggle phone display on/off, etc.
Once the monitor detects the output, it is golden. But I think there is a period where the monitor looks for a signal and after that period, if nothing is found, it stops looking. Could be the same way with the TV.
player911 said:
well if the output of the phone was burnt out, then it wouldn't work either way. Just make sure all the settings are correct. Your monitor is probably 1080p or better. Your TV?
There were some issues with settings and auto. There could be a number of issues at hand and/or it could just be the phone.
I would try another rom. CM7's works pretty well. There are no settings and AUTO is hardcoded.
I've played with the HDMI out with my monitor and while it works, sometimes I had to screw with the orientation, unplug/replug, toggle phone display on/off, etc.
Once the monitor detects the output, it is golden. But I think there is a period where the monitor looks for a signal and after that period, if nothing is found, it stops looking. Could be the same way with the TV.
Click to expand...
Click to collapse
I would like to think that its something that could be fixed, but I have tried flashing multiple ROMs including a virgin stock froyo all with the same result.
My HDMI did work properly when I was using a short generic HDMI that I got with my accessory kit, but as soon as I plugged in the monoprice HDMI the battery level instantly dropped to 0% followed by the smell of burning electronics, now the HDMI out only works on a PC monitor but never a TV. I literally went to Sears and they let me plug it in to 15 different TVs and none of them worked. From what I have been reading in these threads:
http://forum.xda-developers.com/showthread.php?t=1057564
http://forums.t-mobile.com/t5/T-Mobile-G2x/HDMI-crashing-phone/td-p/824403
It seems to be pretty common and no one has been able to get their HDMI to work properly after it fails.
What I would like is if there was some was of forcing HDMI on instead using the auto.
Hi All,
Ive had my O3D for 2 weeks now and im loving it, best phone ive had by miles.
The only problem i'm having with it is that I cant get it to output to a tv.
I bought a micro HDMI cable from ebay for a couple of quid and tried it on a Toshiba tv and it worked but there was a red tinge to it and kept turning off. So I tried it on a Sony Bravia and nothing came up at all. Lastly I tried it on a cheap hanspree tv and it worked but with the same red tinge and it flickered really bad.
I contacted the ebay seller and he sent me a new cable which does not have the red tinge to it but still doesnt display on the Sony Bravia and flickers on the Hanspree.
I havn't tried it on the Toshiba yet cus I dont have access to it at the moment but im assuming its gunna work on it.
I have tried to change the settings on the phone but none of options make a difference.
I had a quick google and it says that HDMI 1.4 should be backwards compatible with all other revisions so im stumped.
Any ideas? anyone else had similar issues? I need it working on the Sony and the hanspree cus thats what I use in my house.
Thanks for reading.
Veto
Phone is Stock V10d Rooted
None of the tv's are 3D (does that make a difference? I presume not)
I have a sony bravia 3d no issue with hdmi out everything works fine
I have bought my HDMI cable from handteck which is the one specified for Motorola devices and it worked on my non-3D TV .
i have same problem except i have a pink like colour not red and it also flickers and even freezez for a few seconds on the screen but plays on phone still.... i got my cable from amazon...
I have the official Samsung USB Connection kit. Both connectors work fine immedeately after boot, but once the device has 'slept' they do not work anymore. I get a notification that the USB Connector is connected, but whatever I insert nothing happens. LEDs (on USB sticks, mice, ...) do not light up which seems to indicate that no power is applied to the port.
I'm running stock Android, rooted. Booting into safe mode makes no difference.
Any ideas what's going on?
You're not the only one, except that in my case USB sticks do light up. IMHO Samsung seriously botched up the automounter in their last update. I wonder how long it's going to take them this time to get their act together and produce a bugfix.
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
SpicyKiwi said:
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
Click to expand...
Click to collapse
Good luck with that. I contacted Samsung support Benelux and was told it was because Amazon Germany had installed "German software" on my tablet.
Trust me, that is NOT the case...
karel jansens said:
IMHO Samsung seriously botched up the automounter in their last update.
Click to expand...
Click to collapse
I'm not sure it's the automounter. Keyboards and mice show the same problems.
sciurius said:
I'm not sure it's the automounter. Keyboards and mice show the same problems.
Click to expand...
Click to collapse
You might be right, I haven't tried one of those yet. Of course, that would mean Samsung botched up the entire USB subsystem of our Note, which is kinda even worse.
Seriously, is anything done about this usb c**kup, or what? I bought my Note, expecting it to replace my venerable Archos 101 which, incidentally, had excellent usb connectivity three blooming years ago and on Android 2.1, only to find out that not only did I have to buy motherloving adapters for the Note, but on top of that that they don't even work properly.
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
sciurius said:
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
Click to expand...
Click to collapse
Quick question, has anyone has the adapter problems while on Android 4.1.1? I tried my adapters on a shop showroom model of the Note 10.1 and they worked perfectly, but only afterwards I noticed that Note was running 4.1.1, while mine is up to date with 4.1.2.
I'm just trying to avoid having to send back a piece of equipment that, despite everything, I can barely miss.
One of the USB OTG tools (forgot which one) had a table of functioning USB host versus Android releases and last time I looked the number of 4.1.2 devices that hat USB problems was significantly higher than the 4.1.1 devices. So I have all reason to believe it is a software problem, introduced in 4.1.2.
EDIT: The tool is USB Host Diagnostics from ChainFire.
So, is there an easy way to go back to 4.1.1 on the BigNote? Mine came with 4.1.2 installed anyway and something tells me that, if I ask Amazon to downgrade for me, I'll be answered with a deafening silence, probably with a "Duh?" In there somewhere.
On second thought, scratch the easy part; is there any way to downgrade a BigNote without losing any of Samsung's added value (yes, I happen to consider most os what they added actually valuable).
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I went from a Galaxy nexus to an N5 and a lot of stuff broke. My voice dialer for one and wifi is wonky for another. Wireless charging heats up the battery so much I've quit using it.
I really like the g2 and thought about returning the N5 and getting one. Only problem is that when the G2 gets kitkat all of the problems I'm having may very well come back. I hope that isn't the case with Miracast as well although LG will probably do better testing.
Good luck with Miracast. Sorry I don't have a way to test it for you.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I tried it on my friend's LG TV and my own Samsung and neither would get very far - hope it's a simple software bug
What TV you guys using for miracast... My LG TV says wireless display but nothing about miracast
Sent from my Nexus 5 using Tapatalk
Miracast wireless Display
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
so the n4 and n7 on 4.3 work okay but your n5 on 4.4 doesn't?
if so it makes me feel a little better than it's just a software issue that (hopefully) is cleared up soon in an update
Maybe. Both the N5 and 4.4 are different from n4 and 4.3. could be a HW issue. Likely a SW problem.
peter
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
i feel like it's less of a hardware issue since miracast worked fine on my g2 and my note3 which are using the same SoC as the n5. maybe i'll try to flash 4.3 back onto my n7 and see if that connects.
is there any way to send this issue to google so they can be made aware of it?
and of course when i decide to do a logcat to see if i can see what's going on when it's trying to connect the phone (and tablet) decide not to see the tv at all for some reason.
Mis understood
Taomyn said:
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
Click to expand...
Click to collapse
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Tried to connect my N5 to Panasonic BluRay Model 230 - it finds the device, and then when you try to connect it just sits there, and sits there....
Honestly, where the hell is the V&V testing ?
prrred said:
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Click to expand...
Click to collapse
good to know, so it seems to be a 4.4 issue more than a hardware issue.
maybe i'll downgrade my n7 today to test it out. (i was going to do it before but then the 4.4 update was officially released and of course i had to flash that first!)
i also emailed google support today to see what they have to say. it's frustrating not being able to use it in the car since i don't like the actual UI of my headunit.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
adiliyo said:
good to know, so it seems to be a 4.4 issue more than a hardware issue.
Click to expand...
Click to collapse
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
theesotericone said:
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
Click to expand...
Click to collapse
Hmm if a custom kernel might help it might be enough to get me to unlock the boot loader and have to set up everything again...
Sent from my Nexus 5 using Tapatalk
bluegizmo83 said:
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
Click to expand...
Click to collapse
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
adiliyo said:
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
Click to expand...
Click to collapse
Awesome man, thanks for the info!
Does miracast work then? I'm thinking of getting a dongle, or should I just use slimport
Sent from my Nexus 5 using Tapatalk
Anyone else have a 2013 lg TV with miracast? I just got one and there is a 10-15 second lag. Its pretty much worthless.
Is there something I'm missing?
Sent from my Nexus 5 using Tapatalk
i've tried it with faux's kernel and francos, both don't work for either of my devices. i emailed google and they replied with troubleshooting info but i haven't had a chance to reply to them and try what they have said (really basic stuff, i don't think it will help)
i refuse to go to crappy crappy touchwiz to make this work, but it makes me sad that i can't use my headunit like i want to.
I know it doesnt support mhl, i havent been able to find any miracast dongle that works, only hope i think is a samsung smart tv, has anyone got this to work with a specific model, i think some have got it to work with chromecast to some degree but i dont have wifi, thanks.
mister marc said:
I know it doesnt support mhl, i havent been able to find any miracast dongle that works, only hope i think is a samsung smart tv, has anyone got this to work with a specific model, i think some have got it to work with chromecast to some degree but i dont have wifi, thanks.
Click to expand...
Click to collapse
Tried it yesterday with my samsung smart tv.... played a video. The video played for about 10 seconds before timing out with a "network error"....
Basically worked about as much as the S5 did.... shoddy. And just to clarify my wifi setup is an N setup and have had no issues whatsoever network-wise.
Thanks twisted, i dont get that, im sure like you said it has nothing to do with your network, i thought the whole point of the quick connect feature was you didnt need to be connected to your home wifi for this to work, or am i mistaken? Ive tried emailing samsung support multiple times to get some kind of clarification, but they are useless.
mister marc said:
Thanks twisted, i dont get that, im sure like you said it has nothing to do with your network, i thought the whole point of the quick connect feature was you didnt need to be connected to your home wifi for this to work, or am i mistaken? Ive tried emailing samsung support multiple times to get some kind of clarification, but they are useless.
Click to expand...
Click to collapse
No the idea is your smart tv and phone must be connected to the same wifi network.... regardless i don't expect this mirroring to work... tried just now... all i got was a garbled screen lol.
my screen mirroring works fine on my Samsung UN65F6400AFXZC. on tv click on screen mirroring input , then on phone quick connect and then connect to screen mirroring , watched a few music vids I have on the phone , flipped through pictures from the gallery , home screen and screen rotation all work fine. a slight delay from phone to tv but that's normal.
all working fine here , stock unrooted
Works a treat on my LG smart TV too. It did ask to allow connections from the s6 once but after that it connects without issue.
Thats interesting, ive been to best buy and asked them to give a demonstration and they said it wouldnt work until their tvs firmware was updated, im assuming its just hit or miss then, can i ask what model number LG you have
Haven't tried on the s6 but it would work with no issue on my note 4 and fire tv
Works very smooth with a Chromecast. I was using screen cast and there wasn't any noticeable lag. Was even watching some slow motion video and it looked as if I plugged it in via HDMI. Good enough for me.
Sent from my Nexus 5 using XDA Free mobile app
I dont have wifi otherwise id try chromecast, and I thought i read chromecast doesnt support the s6 yet, although theyre maybe a workaround the wifi requirement somehow, i think it has to do with the initial setup has to be done then you can do it
Chromecast works without a hitch
no Miracast
Trying to use miracast with my s6 on both my Microsoft wireless display adapter and my wdtv live, it tries to connect but fails after a few attempts. I can connect with my old s3, my surface pro 3 and some Asus memo pad hd7's. Samsung or lollipop have broken Miracast, does anyone know where to send a complaint?
kyleande said:
Trying to use miracast with my s6 on both my Microsoft wireless display adapter and my wdtv live, it tries to connect but fails after a few attempts. I can connect with my old s3, my surface pro 3 and some Asus memo pad hd7's. Samsung or lollipop have broken Miracast, does anyone know where to send a complaint?
Click to expand...
Click to collapse
Did you ever figure out a solution or reason for the issue? Facing similar problems myself trying to connect my s6 to my LG smart TV using miracast.
---------- Post added at 05:52 AM ---------- Previous post was at 05:50 AM ----------
kyleande said:
Trying to use miracast with my s6 on both my Microsoft wireless display adapter and my wdtv live, it tries to connect but fails after a few attempts. I can connect with my old s3, my surface pro 3 and some Asus memo pad hd7's. Samsung or lollipop have broken Miracast, does anyone know where to send a complaint?
Click to expand...
Click to collapse
Did you ever find a solution to this issue? Facing similar problems trying to connect my s6 to my LG smart TV using miracast.
So I've experienced smart view working perfectly for weeks. Have s6 phone and series 6 Samsung smart tv. Then it stopped and I only get an option to deny, no option to allow. To confirm, I have only those two devices-no wifi router or home Internet. Was playing showbox, Spotify, youtube, mobdro...etc. There was about a half second lag, perfectly acceptable.. Samsung told me it may be an update issue, but why remove the feature I bought equipment specifically for that task? Is the connection Bluetooth? Or a direct wifi? This is why phones need to be able to connect to a wifi network they are creating..