[Q] Outputing Android OS at 1156x768 to Lapdock - Motorola Droid 4

I just got the $80 Droid Bionic Lapdock and it's working beautifully with my Droid 4 but Webtop leaves a bit to be desired.
What I really want to do is simple. I want to run CM9 and have the tablet UI show up when I dock the phone.
So far I've gotten Android to show up instead of Webtop by using my old Droid 3, however it was not output in the lapdock's native resolution due to the way the phone handles HDMI out. Obviously under normal circumstances you want both screens to be showing the same image but for this to work I need Android to be output at full res (1156x768)
Lets hack it to disable the built in screen and switch over entirely to the HDMI output but at native resolution. I will continue to work on my rooted phone and ICS Droid 3 but if anyone has done any more work please do share!

Not sure what I can contribute but I will gladly help and test on my end. I have an atrix lapdock working at the moment. I would love to either get a webtop2sd to work, or a full debian/ubuntu install running on the lapdock. Let me know if i can test anything.

Related

controlling HDMI

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.

[Webtop]: Bluetooth crashes webtop.

I recently purchased an HDMI cable to use my Bionic with, and alongside it, I also have an Acer AK00LB bluetooth tablet keyboard that I purchased for my Android devices. I have used this keyboard with everything; it works perfectly with my computer and the base Android OS on the Bionic. However, when I pair and attempt to use it with the Webtop mode enabled, the entire phone crashes from anywhere to a few seconds to a minute of use. It doesn't do this unless the Bluetooth keyboard is connected and typed on. I don't know whether it's the custom ROM I have installed, a problem with the webtop itself, or the keyboard. Has anyone else run into this problem?
I am using:
An Acer AK00LB IconiaTab keyboard.
ROM: [R3]BLURR3D v2.0
The Webtop is base. I have not tried reflashing the webtop partition yet.
I am also using Webtop2SD and the appropriate 'ubuntu expansion' packages.
If someone can tell me where the webtop might store core dumps or log files, I can pull them off and post them.
Any help would be appreciated. Thank you!

webtop issue

I can seem to find anything on this, and my apologies in advance if this has been discussed somewhere else, but I have the atrix lapdock and rewired to use it for the bionic. I know the dock works as I have connected it to my rarz with no problem yet when I plug the bionic in I have no success. The bionic works just fine in the HD Media dock.
Its running Liberty3 v 2.0 on 5.8.893(I think that was the last install) and the webtop version is WT-1.3.0-108_DBN-21.
Any help as to why it might not work on the lapdock but with the HD media dock would be helpful. Thanks

HULU HDMI .apk solution (I think I have it)

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.

[Q] Cyanogenmod MHL output

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

Categories

Resources