Dear All,
I have just flashed to the most update nightly version of cyanogenmod 10.1 for P880, everything seems working fine except for MHL output. It output to my TV with only 720p + weird rotation.. ie even the screen of my P880 is landscape, it display portrait on my TV.
On the stock ROM it won't being that and there was an option to adjust the default output resolution. Is there any way to adjust it on Cyanogenmod??? Please help. Thank you.
Mike
ekimkam said:
Dear All,
I have just flashed to the most update nightly version of cyanogenmod 10.1 for P880, everything seems working fine except for MHL output. It output to my TV with only 720p + weird rotation.. ie even the screen of my P880 is landscape, it display portrait on my TV.
On the stock ROM it won't being that and there was an option to adjust the default output resolution. Is there any way to adjust it on Cyanogenmod??? Please help. Thank you.
Mike
Click to expand...
Click to collapse
The only MHL functionality currently working in CM 10.1 is direct mirroring. This means that it will directly mirror the display on your device as it would look holding it straight up. To add to the fun, the default is to keep your display rotated at 90 degrees when HML is connected, although it is possible to fix this to 0 degrees instead.
Since the 4x screen only supports 720p resolution that implies that you won't get a higher resolution on your TV either using this mirroring functionality.
I have already been trying for weeks now to do something about this, but it's a royal pain. The problem is that the hdmi mirroring seems to be completely handled inside the nvidia tegra proprietary drivers, which are closed source. This means that the easiest solution, which would be to edit these drivers, is not an option. Moreover, it makes it more difficult to establish exactly how the interaction between the android system and these drivers occurs.
LG clearly found a way to make it work though, which I suspect involved adding better multiple screens support to android. That would indeed open up the possibility to change the output resolution, as the tegra chip seems to support higher resolution. I have not given up on the problem yet, so perhaps I'll get lucky in the future and get things working.
Wenque said:
The only MHL functionality currently working in CM 10.1 is direct mirroring. This means that it will directly mirror the display on your device as it would look holding it straight up. To add to the fun, the default is to keep your display rotated at 90 degrees when HML is connected, although it is possible to fix this to 0 degrees instead.
Since the 4x screen only supports 720p resolution that implies that you won't get a higher resolution on your TV either using this mirroring functionality.
I have already been trying for weeks now to do something about this, but it's a royal pain. The problem is that the hdmi mirroring seems to be completely handled inside the nvidia tegra proprietary drivers, which are closed source. This means that the easiest solution, which would be to edit these drivers, is not an option. Moreover, it makes it more difficult to establish exactly how the interaction between the android system and these drivers occurs.
LG clearly found a way to make it work though, which I suspect involved adding better multiple screens support to android. That would indeed open up the possibility to change the output resolution, as the tegra chip seems to support higher resolution. I have not given up on the problem yet, so perhaps I'll get lucky in the future and get things working.
Click to expand...
Click to collapse
Thanks for your detail reply, I have just found that they said about the Nivdia proprietary driver issue. ie. The resolution is almost impossible to fix.
On the stock rom, LG did a very great job on this, even the P880 has only 720P, but they can upscale(or stretch) it to 1080p and rotate it correctly over MHL.
But what do you mean we can fix it by set it to 0 degree?? (I have try the auto rotation and limit it to single orientation, but it does not work) So, how can I do it? Honestly, I really don't care if it is 1080p or not, coz' what I think it is just upscale(or stretch), I can also do it on my TV set too. The problem is the orientation. Anyways, 1000 x thanks on your reply.
Mike
I am interested in this MHL problem too
But I noticed that when the device is booting up with MHL adapter in place of course the "cyanogen"(bootscreen) is normal on my TV but later when the rom is fully booted that weird rotation takes place
So I thank that this is CM 10.1 problem, and I dont know how to solve it
ekimkam said:
Thanks for your detail reply, I have just found that they said about the Nivdia proprietary driver issue. ie. The resolution is almost impossible to fix.
On the stock rom, LG did a very great job on this, even the P880 has only 720P, but they can upscale(or stretch) it to 1080p and rotate it correctly over MHL.
But what do you mean we can fix it by set it to 0 degree?? (I have try the auto rotation and limit it to single orientation, but it does not work) So, how can I do it? Honestly, I really don't care if it is 1080p or not, coz' what I think it is just upscale(or stretch), I can also do it on my TV set too. The problem is the orientation. Anyways, 1000 x thanks on your reply.
Mike
Click to expand...
Click to collapse
I said you can fix the rotation to 0 instead of 90, but that does not fix the problem. You can do this by adding a line 'persist.demo.hdmirotation=portrait' to your build.prop. I do not find it too useful though, as most things you'd want to display externally work better in landscape mode.
ljubisa_sk said:
I am interested in this MHL problem too
But I noticed that when the device is booting up with MHL adapter in place of course the "cyanogen"(bootscreen) is normal on my TV but later when the rom is fully booted that weird rotation takes place
So I thank that this is CM 10.1 problem, and I dont know how to solve it
Click to expand...
Click to collapse
After the boot sequence the window managers kick in and decide you should be stuck on landscape mode while connected via MHL. You can change that part quite easily. The real challenge is making the MHL output rotate independently and use the entire screen.
Wenque said:
I said you can fix the rotation to 0 instead of 90, but that does not fix the problem. You can do this by adding a line 'persist.demo.hdmirotation=portrait' to your build.prop. I do not find it too useful though, as most things you'd want to display externally work better in landscape mode.
After the boot sequence the window managers kick in and decide you should be stuck on landscape mode while connected via MHL. You can change that part quite easily. The real challenge is making the MHL output rotate independently and use the entire screen.
Click to expand...
Click to collapse
Please tell me how to chance to full landscape instead of portrait mode?!
I'm running CM10.1 "cm-10.1-20130304-EXPERIMENTAL-jewel-M2" on my HTC EVO 4G LTE (Jewel). MHL/HDMI doesn't work at all for me. Very disappointing.
Even getting GPS to work was a hassle. Hope they get the kinks worked out in the next milestone update; would love to be able to hook my phone up to my TV again. Very convenient.
ljubisa_sk said:
Please tell me how to chance to full landscape instead of portrait mode?!
Click to expand...
Click to collapse
As I tried to explain, that currently isn't possible using CM.
RudyH246 said:
I'm running CM10.1 "cm-10.1-20130304-EXPERIMENTAL-jewel-M2" on my HTC EVO 4G LTE (Jewel). MHL/HDMI doesn't work at all for me. Very disappointing.
Even getting GPS to work was a hassle. Hope they get the kinks worked out in the next milestone update; would love to be able to hook my phone up to my TV again. Very convenient.
Click to expand...
Click to collapse
Yes, that's a shame, but it is primarily a vendor problem, as writing proper support is near-impossible when the APIs for the video drivers are kept secret. I also fail to see what your problems with the HTC EVO have to do with the 4X HD, apart from the fact that they both appear to be supported by the CM crew.
Can somebody help me with the tutorial on how to enable mhl on CM10.1.
Regards,
Kanad
Kanad said:
Can somebody help me with the tutorial on how to enable mhl on CM10.1.
Regards,
Kanad
Click to expand...
Click to collapse
Sure.
1) Take your separately bought HML adapter.
2) Plug the power cable into the adapter.
3) Plug the adapter into your phone.
4) Plug a HDMI cable into the other end of the adapter.
5) Plug the HDMI cable into your TV.
6) Set your TV to the correct HDMI output channel if necessary.
Optionally,
7) Discover that HML with CM 10.1 does not work the way you want, since the image on the TV is rotated.
You're welcome.
To Wenque
Hi Wenque
You seem to know stuff about this problem.
I too have an P880 running CM10.1 and I recently bought a new stereo for my car, where I can connect my phone using MHL. And I obviously have the same problem.
Do you know if someone at CM are working on a solution or something? I know you wrote it's hard to fix, but it would be nice with some information on, whether there is hope for a solution or not.
Thanks
Any news from this subject?
Try to add this line to build.prop:
persist.demo.hdmirotation=portrait
EDiT: sorry it was already posted before.
Sent from my LG-P880 using xda app-developers app
iodak said:
Try to add this line to build.prop:
persist.demo.hdmirotation=portrait
EDiT: sorry it was already posted before.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I already tried this. But when I start a game it doesn't follow screen rotation. I think I'll have to flash stock to test it.
Sent from my LG-P880 using xda app-developers app
I tried using mhl output on stock rom and it works as expected but sisaxis controller app don't.
Sent from my LG-P880 using xda app-developers app
Any news?
Are there any news in this matter?
I'm using another ROM on my phone at the moment, but it's only Android 4.1, to get MHL working.
I would very much like to switch back to CM when, if ever, they have MHL working.
rd-Target said:
Are there any news in this matter?
I'm using another ROM on my phone at the moment, but it's only Android 4.1, to get MHL working.
I would very much like to switch back to CM when, if ever, they have MHL working.
Click to expand...
Click to collapse
Well, not a big news.. but CM10.2 works in portrait mode on 720p but not landscape mode. (ie everything is portrait with 2 black box on both side)
Mike
ekimkam said:
Well, not a big news.. but CM10.2 works in portrait mode on 720p but not landscape mode. (ie everything is portrait with 2 black box on both side)
Mike
Click to expand...
Click to collapse
So they still haven't fixed it? LOL!
amkirk94 said:
So they still haven't fixed it? LOL!
Click to expand...
Click to collapse
Apparently not.
Well for me it doesn't really matter anymore, I'll just stick to Android 4.1 until the LG G2 is available here in Denmark, and then I'll probalby buy it.
Unless the next Nexus device is announced in the meantime, and it's worth waiting for.
Wenque said:
The only MHL functionality currently working in CM 10.1 is direct mirroring. This means that it will directly mirror the display on your device as it would look holding it straight up. To add to the fun, the default is to keep your display rotated at 90 degrees when HML is connected, although it is possible to fix this to 0 degrees instead.
Since the 4x screen only supports 720p resolution that implies that you won't get a higher resolution on your TV either using this mirroring functionality.
I have already been trying for weeks now to do something about this, but it's a royal pain. The problem is that the hdmi mirroring seems to be completely handled inside the nvidia tegra proprietary drivers, which are closed source. This means that the easiest solution, which would be to edit these drivers, is not an option. Moreover, it makes it more difficult to establish exactly how the interaction between the android system and these drivers occurs.
LG clearly found a way to make it work though, which I suspect involved adding better multiple screens support to android. That would indeed open up the possibility to change the output resolution, as the tegra chip seems to support higher resolution. I have not given up on the problem yet, so perhaps I'll get lucky in the future and get things working.
Click to expand...
Click to collapse
Hi Wenque, I have googled around and found the parameter "config_undockedHdmiRotation" on "platform_frameworks_base/blob/master/core/res/res/values/config.xml". Maybe setting it to 270 would solve the issue?
Wondering if it's possible to set the resolution of the device to 1280x720 instead of 720x1280 on kernel can solve the hdmi output problem too..
*I'm not a android developer, just trying to help e sorry for my bad english
Related
As stated in the (www .blogtalkradio .com/motodev) Q&A session yesterday with Motorola about the Droid X, in answer to the question asked at the 29:00 mark,
"The only time that we are enabling the HDMI driver on the device is when you are in the gallery mode. [...] The HDMI driver is not active any time outside the gallery," where the "gallery mode" is their included photo/video viewer.
I'm wondering how true that is...
(www .pcmag .com/article2/0,2817,2365630,00.asp ) PCMag's review stated that the youtube player and blockbuster player were not able to use the hdmi out at all.
As seen in (forum.xda-developers.com/showthread.php?t=703111 ) this thread the evo 4g, which also has hdmi out, is capable of allowing any app that uses VideoView to utilize that output, but that's supported by the phone maker.
Will that usability be true on the droid x?
Could we figure out a way to bypass any limitations Motorola includes, and maybe even send (an upscaled version of) the main screen through the hdmi (not just video but anything we could put on the phone's screen)?
I was just at a motorola event and we were able to run nfl mobile through the hdmi.
Yes the tv was in an ice sculpture and yes it was connected to a droid x via the hdmi cable
Sent from my ADR6300 using XDA App
That's great news, thanks for letting us know!
The more apps with handshakes to the hdmi-out we have, the better for us to get it working completely openly
The whole media-center-and-phone-in-my-pocket is just a great idea imho...
With the hdmi out we could:
put any videos and pictures from any source up on your home tv
connect it to the projector at work and give presentations
go with a few bluetooth controllers to your friend's house and play multiplayer (even online) games on their tv with minimal cords to deal with
maybe even video-chat would be possible if you set up the phone with the camera facing out in front of the tv
... ok, that last one sounds like a pretty lame way to get video-chat, but it would save on having to have a computer/monitor/webcam when you wanted to
Of course this is all far into the future stages of development on the phone, but I'd rather create buzz and excitement to build up a developer and user base
Talked to a moto rep, said it might have been a beta device as licensing is what will prevent this thing from being turned on when it hits consumers hands. At least we know it can be done.
Sent from my DROIDX using XDA App
no fun, i'm not much of a C programmer, but if it's just enabling or disabling the driver, I guess it comes down to the security on the phone. If you go into root, I suppose we should be able to start the driver. The only thing I fear is if the driver is signed and only a signed application can access it, then I think we might be SOL
I'm not particularly worried... if we get access to enough apps that use the hdmi driver, we should be able to document enough of the method.
I believe while the hardware can reject unsigned versions of the OS (roms), most apps are self-signed (see developer. android. com/guide/publishing/app-signing.html) so that shouldn't be a problem. We just have to figure out which hoops to jump through (following the programs that use hdmi) to get it to work. They'd have to leave the hoops pretty wide open or else risk the need of updating the thing every time a new app is released that needs to get through.
This is a mixed bag here. The reason why Motorola limited the hdmi driver is likely so they didn't have to put a fps cap on the droid x like htc put on the evo.
This is pure speculation here but I would imagine the way that the evo devs are going to "truly" overcome the fps cap is to mimic the droid x behavior of toggling on and off the hdmi drivers so that the evo can access up to 60 fps.
You guys are on the other end of the boat where by default your fps won't be artificially capped, but you likely won't have full access to the hdmi drivers at first.
I think the sweet spot for both phones is finding a happy medium where we can toggle the hdmi drivers at will.
Any news on this? I would really like to get rockplayer and youtube working through hdmi. In fact, I would like to get the entire OS through HDMI and possibly a bluetooth keyboard and mouse working so I can use it as a little media center pc.
2 way control
I would lime to see this pushed to.the level of controlling the phone through an hdmi touchscreen.
I thought we would be able to see pandora and other apps through the hdmi...This sucks the way it is...also does anyone think the sound is terrible through the hdmi?
There is no point int he HDMi at all if you can only use it for your pictures and your videos from the phone's camera.
They need to make it show what you see on the phone, but on the screen
I remember there was a windows mobiel program that popped up a small window on your desktop that let you see your phone's screen and interact with it on your monitor when connected through usb
anything like this for android?
sp1kez said:
There is no point int he HDMi at all if you can only use it for your pictures and your videos from the phone's camera.
They need to make it show what you see on the phone, but on the screen
I remember there was a windows mobiel program that popped up a small window on your desktop that let you see your phone's screen and interact with it on your monitor when connected through usb
anything like this for android?
Click to expand...
Click to collapse
NO, the hdmi dock is a half ass design. For the $, it should do everything. MOTO/VZ dropped the ball on this. Hopefully they will open this up with a sw update.
Update: "Real HDMI" in the market
http://forum.xda-developers.com/showthread.php?t=769990&highlight=control+hdmi
Hi,
I'm pretty new to Android development. So my understanding after reading a couple threads here is that HDMI access on the stock Droid X is limited to the gallery only, is that right? And the point of the "Real HDMI" app is that it will automatically redirect all output to the phone's display through HDMI, right? So no API exists which gives programmatic control over the HDMI port? That's a shame if so.
Do any of the Android devices allow easier HDMI port control or do we need these kinds of work arounds for all of them?
Thank you very much for any information anyone can provide.
Sorry to be a pest, but can anybody answer my questions? Should I consider posting somehwere else?
Thanks again.
commie64 said:
Sorry to be a pest, but can anybody answer my questions? Should I consider posting somehwere else?
Thanks again.
Click to expand...
Click to collapse
Maybe try posting in the Real HDMI thread over at DroidXForums.com because username GMAN (who made real hdmi) has a thread there. I'm sure his knowledge of the subject is pretty extensive.
I bought a HDMI to VGA converter to be used with my Nexus 10 with projectors to give presentations. Now I connected it to my desktop monitor (via VGA), and it says "reduce resolution".
Is there a way to change the resolution? Or is this something the converter should actually do? (which I can't do, it just looks like a cable).
Thanks!
Which adapter do you have? I've been looking for one for a while.
As far as I know the HDMI out mirrors the native screen resolution. It's been that way on every android device I've used.
Sent from my Nexus 10 using Tapatalk 2
novisme swell
I have this one: KanaaN micro Hdmi Vga.
I think you have to reduce the resolution of your monitor. Just go to menu and you should find.
Send from my lovely Sensation XL, from a little town in france with a very very slow internet connection.
If I succeed helping you (rare) don't forget to hit the thanks button
The n10 outputs at 1080p...always. You can't turn it down or up. You can't just switch the pinout of HDMI to VGA. It can't be done. You have to convert the signal from digital to analog. That is sometimes done inside the vga sink (many data projectors), but it is more often done with an external converter.
As for bringing down the resolution, you need to first input to a scaler that has granular resolution control an scale it down.
What about video projector?
Does that mean we can't hook up the N10 to a VGA video projector via an hdmi-to-vga converter? All the VGA video projectors I have at work have very limited resolutions (800x600, 1024x768, 640x400).
I'm really looking forwarding to get an N10 for presentations so this would be show-stopper. Your help and suggestions are most appreciated!
Getting a little frustrated with this. On my Motorola Xoom (original WiFi), I had a solution that worked. It was kind of sloppy, but it did work. I had a micro-HDMI to HDMI adapter, a small power injector (HDMI Female on one side, Male on the other), and a HDMI to VGA adapter. All those connected together accomplished the task of connecting the tablet to VGA. (the power injector was needed because the micro HDMI port didn't put out enough power to push the video).
That same setup doesn't work on the Nexus 10. I tried removing the power injector and that didn't work either. In both cases, the monitor accepts a resolution setting from the tablet, but I just get horizontal gray bars as far as the image itself. I just got in the mail a Samsung micro-HDMI to VGA adapter that is supposed to be for several of their laptops AND slates, but that didn't work either. This time, again it accepted a resolution setting, but I get a complete gray picture (no bars, just big gray box).
I'm really getting disappointed that there isn't an easy solution to this. There are way too many businesses that still only have VGA connections and since I use my tablet as a laptop replacement/for presentations/etc, it's a must have.
securitynick said:
Getting a little frustrated with this. On my Motorola Xoom (original WiFi), I had a solution that worked. It was kind of sloppy, but it did work. I had a micro-HDMI to HDMI adapter, a small power injector (HDMI Female on one side, Male on the other), and a HDMI to VGA adapter. All those connected together accomplished the task of connecting the tablet to VGA. (the power injector was needed because the micro HDMI port didn't put out enough power to push the video).
That same setup doesn't work on the Nexus 10. I tried removing the power injector and that didn't work either. In both cases, the monitor accepts a resolution setting from the tablet, but I just get horizontal gray bars as far as the image itself. I just got in the mail a Samsung micro-HDMI to VGA adapter that is supposed to be for several of their laptops AND slates, but that didn't work either. This time, again it accepted a resolution setting, but I get a complete gray picture (no bars, just big gray box).
I'm really getting disappointed that there isn't an easy solution to this. There are way too many businesses that still only have VGA connections and since I use my tablet as a laptop replacement/for presentations/etc, it's a must have.
Click to expand...
Click to collapse
I think that's the problem of the N10 hardware, I tried to connect my N10 to a HDMI TV, I get the same gray picture as you described.
Called Google support and they are sending me a replacement. Also I have severe light bleed on the lower left and rigt of the screen as well.
A little disppointed.
I purchased this connector http://www.amazon.com/gp/product/B00879EZJI/ref=oh_details_o03_s00_i00 and it worked perfectly. Was able to hookup my N10 to a VGA monitor. Monitor did not have 1920x1080 resolution and it still worked.
Sounds good. What resolution is the monitor showing?
lorloff said:
I purchased this connector (The site won't let me repost the link for some reason) and it worked perfectly. Was able to hookup my N10 to a VGA monitor. Monitor did not have 1920x1080 resolution and it still worked.
Click to expand...
Click to collapse
This worked!!!! Thank you lorloff for posting this. For anyone who cares the resolution scaled down to 1280 x 720. I tested on a standard computer monitor and a TV that my office uses with presentations/meeting. I am not sure why, but the TV didn't display across the entire screen (had side black bars), but it is good enough. The computer monitor took up almost the entire display, but that could have been that the native resolution was lower than the TV. Anyway, point is, this solution definitely works.
Similar issue...
Hi guys. I have a similar issue, but my nexus 10 crashes when connected to the projector. I can see the image, it works for about 10 seconds before dropping it, reconnecting, then crashes completely and restarts. I am using the same HDMI - VGA cable as mentioned on here. I thought it was the cable, and they replaced it for me, but it hasn't helped. Has anyone else experienced this? Any thoughts on if this is Android or the hardware causing the issue? Any help would be much appreciated as I really need to get it working or is it a case to send it back to Google? The projector is a viewsonic pjd5122 by the way, which has not given any issues before. Cheers for your help/thoughts.
Elositoingles said:
Hi guys. I have a similar issue, but my nexus 10 crashes when connected to the projector. I can see the image, it works for about 10 seconds before dropping it, reconnecting, then crashes completely and restarts. I am using the same HDMI - VGA cable as mentioned on here. I thought it was the cable, and they replaced it for me, but it hasn't helped. Has anyone else experienced this? Any thoughts on if this is Android or the hardware causing the issue? Any help would be much appreciated as I really need to get it working or is it a case to send it back to Google? The projector is a viewsonic pjd5122 by the way, which has not given any issues before. Cheers for your help/thoughts.
Click to expand...
Click to collapse
I haven't tried this yet but the only thing I can recommend is switching ROMs (though this may not help) (make sure you backup before you wipe)
Sent from my Nexus 4 using xda app-developers app
securitynick said:
This worked!!!! Thank you lorloff for posting this. For anyone who cares the resolution scaled down to 1280 x 720. I tested on a standard computer monitor and a TV that my office uses with presentations/meeting. I am not sure why, but the TV didn't display across the entire screen (had side black bars), but it is good enough. The computer monitor took up almost the entire display, but that could have been that the native resolution was lower than the TV. Anyway, point is, this solution definitely works.
Click to expand...
Click to collapse
Hi all, I also bought the Cable Matters Active Micro HDMI to VGA Adapter as suggested by lorloff, but it does not seem to work with my Nexus 10. It's on KitKat 4.4.2.
When I plug it in, the tablet becomes slightly less responsive and the device (projector/monitor) I plug it into only gets a black screen, it's not blank, just an off black. It seems that the signal is going through and at 1920*1080 resolution, but not picture is showing. I purchased two of these adapters and both do the same. The adapters work because I have tried it with a phone and I get a mirrored image instantly, at 720p. I've tried it on 3 different types of monitors, 17 and 24 inch, and 3 different types of projectors, one of which can do resolutions beyond 1080p.
The HDMI out on the Nexus 10 works, as when I connect a micro HDMI to HDMI adapter directly into a projector I get instant mirrored output, but at 720p. I've also tried with and without additional power through the adapter and having the tablet plug in charging, but nothing helps.
I'm thinking of getting the KanaaN Micro HDMI to VGA Adapter as that seems to work for others, but then again so did this adapter... Any ideas?
Same for me with a generic HDMI to VGA.
I'm running 4.4.2 as well on my N10.
So should it be an OS issue ?
I contacted Cable Matters and their reply was:
... I am afraid that adapter has some compatibility issue with Nexus 10. ...
Click to expand...
Click to collapse
I have ordered the KanaaN Micro HDMI to VGA Adapter. We'll see how that goes.
Reply to hdmi to vga converter
Nexus10User said:
I bought a HDMI to VGA converter to be used with my Nexus 10 with projectors to give presentations. Now I connected it to my desktop monitor (via VGA), and it says "reduce resolution".
Is there a way to change the resolution? Or is this something the converter should actually do? (which I can't do, it just looks like a cable).
Thanks!
Click to expand...
Click to collapse
There is only way to change the resolution. You must get another hdmi to vga converter from Hdgenius . Maybe there is something wrong your device in quality.
When I plug it in, the tablet becomes slightly less responsive and the device (projector/monitor) I plug it into only gets a black screen, it's not blank, just an off black. It seems that the signal is going through and at 1920*1080 resolution, but not picture is showing. I purchased two of these adapters and both do the same. The adapters work because I have tried it with a phone and I get a mirrored image instantly, at 720p. I've tried it on 3 different types of monitors, 17 and 24 inch, and 3 different types of projectors, one of which can do resolutions beyond 1080p.
Click to expand...
Click to collapse
fusi*n said:
I contacted Cable Matters and their reply was:
I have ordered the KanaaN Micro HDMI to VGA Adapter. We'll see how that goes.
Click to expand...
Click to collapse
Any new leads? I have got the same problem using the cable matters adapter.
From the looks of it passive adapters don't properly work as it relies on the N10 being able to convert the digital HDMI signals to the analogue VGA. The Cable Matters one that was linked above is an active one and does the converting instead, which allows it to push for a higher resolution.
I already have the Cable Matters adapter, it doesn't seem to work, though. I get a black screen even after connecting the USB power chord. Any ideas?
Anyone near an HDMI cable and have a HULU Plus subscription that wants to test?
I think I managed to find the setting in the strings.csv fie that disables HDMI output from the .apk. I've re-signed the package, but I can't test it to see if it works. The file is found in the assets/ui folder:
Code:
Line 130: strings_ui.xml|ui_hdmi_output_disabled HDMI Output Disabled 1
Changed to 0. Please test and report back.
Hulu plus is giving a free month from geiko... saw it on Xbox.... so I guess I could try it for ya but I'm stock non-root (if that matters... sorry I have bad luck with phones don't want to risk it for insurance sake)... just let me know
Sent from my DROID4 using xda app-developers app
You don't need to be modified to install it, however, I finally tested it last night and it didn't work.
Yeah.. sorry you had posted this when i wont up... the good news is that your going to save me 8$ a month cuz turns out I've been paying for it And Netflix for some time now and didn't know thanks to you I can cancel Hulu... thank you kindly for you efforts
Sent from my DROID4 using xda app-developers app
Crap, I dont have a laptop with me to keep testing and I'm stuck in a hotel and I have to use the old version of hulu.
Tried this on my transformer tf300t tab. Installs fine but doesn't fix the HDMI output block.
yeah sorry to abandon the thread. i had to go back to the drawing board. the data file i found seems more like a tick-count than actual config info. i got side-tracked once i found this other app, that disables the display, but HULU still detects the HDMI.
what's needed here is to fool the APK into thinking the external display is the primary display, or to elminate the hardware reporting that HDMI has been enabled. once you remove HDMI, the video plays as normal. when you connect HDMI, you get a warning message and the video stops buffering.
based on HULU's earlier APKs, i know that at one point, you could get the warning message, but that the video would still display. they somehow fixed that, which is why it doesn't work. my conclusion is that once the hardware reports that HDMI has been enabled (new device found?), that HULU sends a command to stop receiving video feed/buffer.
if the APK were truly disabling the HDMI output, wouldn't the screen on the device work and you would see nothing on the HDMI device (TV)? somebody has done some band-aid type of programming to counter the issue, which should be easily adverted.
i need someone with more knowledge than me, to figure out how to make calls to the hardware layer, to detect external devices, in the manner described above. if there's some sort of permission that can be changed, or channel that can be closed, HULU can update its APK all it wants.
hangon wait, hulu blocks the use of hdmi?
iv never had hulu.
EDIT: Conclusion =D
Well i'm happy with a setup i've just done. Using my X Mini portable speakers I get a very loud speaker, with high quality. If anyone else cannot be bothered/cannot figure out how to fix HDMI, these are probably better than my Tv's speakers anyways. And there only £12 =D
Also, YATSE remote for android allows me to control it despite not having CEC!
Click to expand...
Click to collapse
Hello, I haven't seen much on Raspbmc on XDa, but its a great little OS. With overclocking controls (much like yuo might get on android) and XBMC booting by default for the professional look =D
Anyway, I haven't been able to get any sound out of the HDMI. I know that sound output can work (on a different OS, like raspbian). Also, i noticed that the HDMI control (ie using TV remote to control it) doesn't work.
Any ideas? Anyone else using PI?
(also, have tried loads of configurations in audio, now i'm stuck)
Edit: I'm trying a clean install, ill post my results.
I've been using raspbmc since I got my first pi and haven't had those problems. However the last iteration of rc5 did have issues with cec which would explain why your remote wouldn't work if your not on the absolute latest. As far as sound only issues I've heard about is with people using external stereo for sound. Disable DTS if your using your tv. With the latest versions be careful with overclocking, there's currently a problem in the build that is causing SD card corruption for a lot of users.
Sent from my SGH-I747 using Tapatalk 2
Check out xbian.org its a xbmc build for the rpi that works great. My remote for my LG tv works great and same for sound, no issues. Has oc control as well. It does freeze up every few days but that's my only issue with it
Sent from my DROID3 using xda premium
Reinstalled but...
Reinstalled but still no joy.
Im gonna try xbian, as Endoroid suggested, much thanks
I did overclock it, but i have noticed that when booting up, sometimes i have to restart as it says
Code:
**cant read, cut off screen****al commit I/O error
Humph, im guessing that al is journal (after googling the rest).
Ill report back again on my xbian results, hopefully end of thread? we'll see (i hope my sd card isn't corrupt or something, i dont think so, file management sitll works and it boots...)
Right...
I installed XBian but still have no sound?!
I know that sound has worked on XBMC, i remember when i first got it i tried it breifly, im gonna try with headphone port and see if i get sound. Even if I do, i'd like to use the HDMI output, rather than headphones/portablespeakers.
Any clues?
Edit:
Headphones working fine... i'm not sure whether that is a good thing or a bad thing...
(im testing using a few different sound sources, not just one, os i doubt this is any Program errors. It must be the system. Are there any drivers i can download for a samsung TV?)
Also, i might try on a different TV and see if it's just the tv?!
Click to expand...
Click to collapse
Edit-2:
Well i'm happy with a setup i've just done. Using my X Mini portable speakers I get a very loud speaker, with high quality. If anyone else cannot be bothered/cannot figure out how to fix HDMI, these are probably better than my Tv's speakers anyways. And there only £12 =D
Also, YATSE remote for android allows me to control it despite not having CEC!
Click to expand...
Click to collapse
In settings, the audio out is set to hdmi and not analog?
Sent from my DROID3 using xda premium
Solution?
Endoroid said:
In settings, the audio out is set to hdmi and not analog?
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I see that no one has commented on this in a while, so I hope that the thread is not dead. When I hook up my Raspbmc to my TV through my Denon receiver, I get picture, but no sound. I added the two lines of code to the config file mentioned on the Pi forums that supposedly force HDMI. When I go into audio settings, however, I don't even seem to have an HDMI option. The only options are Analog and Coax.
Thoughts?
brogdonbr said:
I see that no one has commented on this in a while, so I hope that the thread is not dead. When I hook up my Raspbmc to my TV through my Denon receiver, I get picture, but no sound. I added the two lines of code to the config file mentioned on the Pi forums that supposedly force HDMI. When I go into audio settings, however, I don't even seem to have an HDMI option. The only options are Analog and Coax.
Thoughts?
Click to expand...
Click to collapse
I had this problem too when I got a Raspberry Pi a week ago, with a Samsung UN32EH4000 (I don't think the TV has CEC, if that matters). Tried all the recommended solutions, but never had the HDMI choice for the sound even. Went to Xbian and had no problems.
Not posted since forever :S
I have given up on Raspbmc, and even xbian as I have found they don't work well, for me.
I did like Arch linux, but had problems had memory problems.
I have had memory problems on all of the distros tried, I think it might be a hardware problem (after a successful boot or two it forgets how to turn on and just fails)
Oh well :L Gonna try raspbian for a bit and see if i get anywhere.
Fallon9111 said:
Not posted since forever :S
I have given up on Raspbmc, and even xbian as I have found they don't work well, for me.
I did like Arch linux, but had problems had memory problems.
I have had memory problems on all of the distros tried, I think it might be a hardware problem (after a successful boot or two it forgets how to turn on and just fails)
Oh well :L Gonna try raspbian for a bit and see if i get anywhere.
Click to expand...
Click to collapse
I was able to fix this by adding "hdmi_force_hotplug=1" and "hdmi_drive=2" to my Config file. I also went pure Raspbmc. You can install XBMC from Raspian, but since my goal was a media extender, I just installed Raspbmc. Wait for everything to settle, turn off the Pi, put the SD card in your PC, open up config.txt, and copy those two lines of code.
Make sure when you edit the config file on a pc, if using windows. Use notepad+ as windows will not properly format the file using utf-8 with standard notepad.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Also... make sure you're using a quality dependable power supply that actually puts out 5V and at least 700mA, I use an Amazon Kindle Fire 2.1A charger just for the headroom.
The easiest way to check is to have the Pi plugged in and on, and check voltage on the board directly with a test meter. If you don't get the correct values, try a different power supply.
I've just bought a Chromecast device and I'm trying to
setup it. The problem is that when I plug it to the tv, a message appears
saying "Starting chromecast" and then the Chrome logo. After that, black
screen. Nothing appears. The setup program in my pc can find the device but
I can't see anything on the TV.
My TV model is LG 32LE5500
I tried rebooting the TV by unplugging everything and nothing changed.
Also I tried the Chromecast devide in another TV and it worked there, but it's not my TV and I need it to work in the LG one.
I've tried all hdmi ports and it's the same in all of them. The chrome logo and then black.
The last thing I did is to configure the device from the other TV and then plug it on the TV that doesn't work. I realized that the audio does work, I launched the YouTube app from my cellphone and I could hear the video, but again, black screen.
Could it be that my TV has a resolution of 1900x1080 and not 1920x1080?
Please I will appreaciate any kind of help, I really wanted to use the device and it's useless for me right now
According to LG, that's a normal 1080p screen.
http://www.lg.com/levant_en/tvs/lg-32LE5500-led/technical-specifications
More likely there's a router setup issue. This may help as a starting point -
https://support.google.com/chromecast/table/3477832?hl=en
santi.marro said:
I've just bought a Chromecast device and I'm trying to
setup it. The problem is that when I plug it to the tv, a message appears
saying "Starting chromecast" and then the Chrome logo. After that, black
screen. Nothing appears. The setup program in my pc can find the device but
I can't see anything on the TV.
...
Could it be that my TV has a resolution of 1900x1080 and not 1920x1080?
Click to expand...
Click to collapse
Your TV is 1080p, so it's 1920 horizontal.
IIRC the boot logo sends 480p, then Chromecast negotiates with the TV as to what resolutions are supported.
Your TV might not be playing nice in the negotiation process.
So, try booting Chromecast without it connected to the TV.
Disconnect power from Chromecast
Disconnect Chromecast from TV
Reapply power to Chromecast
Wait for it to boot (wait until LED goes solid steady white)
Turn on TV if it is not already on
Set TV to Chromecast input
Plug Chromecast into TV input
bhiga said:
Your TV is 1080p, so it's 1920 horizontal.
IIRC the boot logo sends 480p, then Chromecast negotiates with the TV as to what resolutions are supported.
Your TV might not be playing nice in the negotiation process.
So, try booting Chromecast without it connected to the TV.
Disconnect power from Chromecast
Disconnect Chromecast from TV
Reapply power to Chromecast
Wait for it to boot (wait until LED goes solid steady white)
Turn on TV if it is not already on
Set TV to Chromecast input
Plug Chromecast into TV input
Click to expand...
Click to collapse
I tried it and it's the same, a black screen. It works with a monitor that I have and another TV, but, sadly, I need it to work in the LG TV
EarlyMon said:
According to LG, that's a normal 1080p screen.
More likely there's a router setup issue. This may help as a starting point -
Click to expand...
Click to collapse
The chromecast device works, I checked it and configured it in another TV, but I need it to work in the LG one.
santi.marro said:
I tried it and it's the same, a black screen. It works with a monitor that I have and another TV, but, sadly, I need it to work in the LG TV
Click to expand...
Click to collapse
Very strange. Almost sounds like an HDCP handshake problem.
Try the HDMI extender in case it's just not plugging in quite right.
Other than that, you can try disabling HDMI CEC (LG calls it SimpLink) and see if that makes a difference.
Do you know what firmware build it has? (Chromecast app will tell you)
bhiga said:
Very strange. Almost sounds like an HDCP handshake problem.
Try the HDMI extender in case it's just not plugging in quite right.
Other than that, you can try disabling HDMI CEC (LG calls it SimpLink) and see if that makes a difference.
Do you know what firmware build it has? (Chromecast app will tell you)
Click to expand...
Click to collapse
I've just tried the device with the extender and SimpLink deactivated and it's the same again
Here I leave a screenshot of the Chromecast app attached
santi.marro said:
I've just tried the device with the extender and SimpLink deactivated and it's the same again
Here I leave a screenshot of the Chromecast app attached
Click to expand...
Click to collapse
Nice names.
Well, you're on the latest firmware build (15250) so either Google broke something in the newest update, or your TV is finicky.
Since your TV is Smart, it might have a firmware update available.
Wait... The specs say "TruMotion 100Hz" - is your TV PAL? It might not support NTSC input...
bhiga said:
Nice names.
Well, you're on the latest firmware build (15250) so either Google broke something in the newest update, or your TV is finicky.
Since your TV is Smart, it might have a firmware update available.
Wait... The specs say "TruMotion 100Hz" - is your TV PAL? It might not support NTSC input...
Click to expand...
Click to collapse
HDMI doesn't care about PAL vs NTSC frequencies by design, exactly why so many in the UK were able to adopt early last year.
EarlyMon said:
HDMI doesn't care about PAL vs NTSC frequencies by design, exactly why so many in the UK were able to adopt early last year.
Click to expand...
Click to collapse
While I agree that it shouldn't matter in this day and age, they still exist separately in the EDID data because of the differing pixel clocks.
It's possible (though ill-advised) for a modern display to reject an input signal based on it being 50/100 Hz or 60/120 Hz.
I deal with a lot of AV stuff and have run into this issue from time to time.
Well, TIL then.
EarlyMon said:
Well, TIL then.
Click to expand...
Click to collapse
I'm learning every day... sometimes the hard way.
Traditionally European TV sets have been more forgiving than their US counterparts, accepting NTSC "nudged" into PAL-60 or NTSC 4.43 in the analog realm.
While the transition to HD did unify the display resolutions and pixel aspect ratios (everything's square, yay!), the differences in refresh/sampling rates remained.
One day my friend, one day... everything will be 600 Hz or better so 24, 25, 30, 50 and 60 fps content will all be supported and play without judder or needing interpolation. :cyclops:
So back to the topic at hand, it's possible the OP's TV doesn't know what to do with a 30/60 Hz input from Chromecast, though that would be quite silly of LG to impose such a restriction. Still, silly happens more often than you think for all kinds of reasons (gray market sales due to varying exchange rates and import/export laws often is a concern, as we burden on regional support that got no revenue from the foreign sale).
TBH, I don't know for certain whether Chromecast is capable of 25/50 Hz output, it might be. But being that Google isn't selling it outside of US/Canada yet, I doubt they've tested it.
>> Anybody in Europe, can you confirm me whether Chromecast outputs 720/50p, 1080/50i or 1080/50p to your TV? <<
Sent from my Nexus 10 using xda app-developers app
Thank you for all your replies,
For what I know, my TV accept NTSC but I'm not 100% sure. I am from South America by the way, in theory electronics here are NTSC.
kDnZP said:
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
That TV in the picture you posted is very similar to the one I have. Did you have any problem using the chromecast device?
The link I gave was from the Eastern Mediterranean, I was more curious about verifying your resolution at the time. There's a 60/120 Hz (NTSC) version of your set, same model number, popular in several South American countries.
I apologize for adding the confusion.
santi.marro said:
That TV in the picture you posted is very similar to the one I have. Did you have any problem using the chromecast device?
Click to expand...
Click to collapse
I have not any problem with LG 26LE3300 (1366x768 native resolution).
santi.marro said:
Thank you for all your replies,
For what I know, my TV accept NTSC but I'm not 100% sure. I am from South America by the way, in theory electronics here are NTSC.
That TV in the picture you posted is very similar to the one I have. Did you have any problem using the chromecast device?
Click to expand...
Click to collapse
Hmm, should work.
Worst-case, since you have other displays that Chromecast does display properly on, you could try this: (it worked on 13300, haven't had need or opportunity to try it on 14975 or 15250)
Locate working monitor and LG TV in close proximity
Connect Chromecast to working monitor and wall power
Once Chromecast is booted, unplug Chromecast from monitor only
Plug Chromecast into LG TV
Likely this will not survive a Chromecast reboot though...
I've got a Sanyo DP50740, and my Chromecast is now showing this same behavior. It used to work fine, but I think that the update to firmware 15250 broke something with hdcp in some TV's.
I filed a bug with Google, but the end result was that the google helpdesk can't tell what was updated in the latest build.
I suggest you file a similar bug with Google, so that they see that this is happening with multple TV models.
Until they fix this I'm stuck with a paperweight.
AustinMartin said:
Until they fix this I'm stuck with a paperweight.
Click to expand...
Click to collapse
It won't sync up even if you hot-plug Chromecast HDMI after it's already booted?
bhiga said:
It won't sync up even if you hot-plug Chromecast HDMI after it's already booted?
Click to expand...
Click to collapse
Nope, tried that. The only thing I haven't tried is to boot up plugged into another device then plug in. Don't have any portable monitors with hdmi input. It might be that they fixed this glitch in the latest firmware.
This is the annoyance of allowing google to update firmware at will. They can break your device, and there's then nothing you can do except wait for the next release. That's why I encourage the original poster to file a bug with them. That's their only window into what's happening.
AustinMartin said:
Nope, tried that. The only thing I haven't tried is to boot up plugged into another device then plug in.
...
They can break your device, and there's then nothing you can do except wait for the next release. That's why I encourage the original poster to file a bug with them. That's their only window into what's happening.
Click to expand...
Click to collapse
The no HDMI and different HDMI scenarios should be different, they have been in my case at least, but understand not having a practical means to try.
Agree. That's the danger of forced updates.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.