|
Leaked Gingerbread ROM for Droid X |
|
|
|
|
Written by Gman
|
|
RealHDMI Currently IS NOW working on "leaked" Gingerbread ROM
Well would like to say that 1.9 release went smooth, but there was a couple of bugs that ended up getting stomped out after its release to the market so we are now up to 1.9.2. But 1.9.2 is on the market and should be working on 2.2 and 2.3.
It has proved very difficult to get a single app to support Android 2.2 and 2.3 with the HDMI output on the Droid X as things have changed A LOT in Gingerbread on the Droid X. Right now I think we have the big problems out of the way and at least have it working on the 2.3 leaked ROMS.
Assuming that the OTA (whenever it gets released) doesn't deviate to much from the current API's in the leaked ROMS there shouldn't be many changes necessary.
Gingerbread brings some new functionality to the table in the HDMI drivers which can potentially lead to some new features, but we are still exploring those possibilities. NO, screen mirroring isn't one of those things as phone's CPU physically can't do that. But once OTA gets out the door hope to have a 2.0 version ready.
|
|
Last Updated on Sunday, 15 May 2011 20:05 |
|
|
Android 2.2.1 fixed the HDMI Bug |
|
|
|
|
Written by Gman
|
|
Verizon/Motorola have Fixed the HDMI Bug
Verizon has released an update for the Droid X that is System Version 2.3.340 also known as Android 2.2.1 for the Droid X.
http://www.verizonwireless.com/droidxsupport
The update has fixed the problem with the LCD display failing to reinitialized when HDMI is disabled. If you are running Android 2.2 on are using RealHDMI we strongly recommend updating your phone to the 2.2.1 update as it will fix the kernel HDMI bug. If you are currently running 2.1 on your phone we will continue to support that version of the OS, but the experience might not be ideal as you might experience "black bars" in 2.1 due to how the phones drivers handle overlay layers.

|
|
Last Updated on Monday, 13 December 2010 19:00 |
|
Back on Market November 13th |
|
|
|
|
Written by Gman
|
|
Motorola has yet to release a patch for the display driver that is causing the dreaded frozen "M" on phone boot for some users and it keeping display from enabling after HDMI is disable on most phones. We hope that a fix from Motorola is forthcoming in the near future but like many Droid X Diehards we are no longer holding our breath.
Due to popular demand we are returning the application to a Market on a "hopefully" permanent basis. While the bug still exists in the Droid X kernel that makes the phone freeze whenever any kind of HDMI out it used, people seem to be wiling to live with it. As Real HDMI is a work around to limitations in hardware/software on the Droid X its always hard to say what state of the capability will be after each Motorola update. But we are constantly working new angles to try to make sure the capability will be available.
I have added another developer into the mix to help with support logistics and try to help keep up on email. It is my hope that this will allow me to again concentrate on the code and the mythical 2.X version that will have Real HDMI as a service that could be enabled/disabled by third party apps. We are contemplating a slight price increase sometime after the 14th. As the project grows so does the costs I incur.
|
|
Last Updated on Saturday, 13 November 2010 13:28 |
|
|
Written by Gman
|
RealHDMI Example Usage Scenarios
Usage Scenario #1: Youtube Video - Swipe Method
Swipe Configuration
- Launch the Real HDMI application.
- Hit the Menu Button on your phone.
- Select Settings then Phone Controls
- Uncheck Phone Bump Detection, Uncheck Phone Tilt Enable, and Check the Phone Proximity Enable
- Hit Back button and make sure Haptic Feedback is Checked
- Hit the Back button again to return to RealHDMI Main Screen
Note: Swipe configuration only needs to be done once if that is your chosen method of control
Using Swipe Enable/Disable
- Plug your HDMI cable into your phone and your TV or Stereo
- Hit the Detect Button on the Phone
- Hit the Home button and navigate and start youtube application
- Start playing a video but before the video starts displaying on the screen swipe your finger over the speaker above screen on the phone.
- The Phone should BUZZ once
- The output should now show up on your HDMI output and you should be able to watch your content on your big screen TV.
- When done swipe your finger again to turn HDMI back off
- Phone will BUZZ twice and display content on the LCD screen to allow you to navigate.
Usage Scenario #2: Youtube Video - Tilt Method
Tilt Configuration
- Launch the Real HDMI application.
- Hit the Menu Button on your phone.
- Select Settings then Phone Controls
- Uncheck Phone Bump Enable, Check the Phone Tilt Enable, and Uncheck Phone Proximity Enable
- Hit Back button and make sure Haptic Feedback is checked
- Hit the Back button again
Note: Tilt method configuration only needs to be done once if that is your chosen method of control
Using Tilt Enable/Disable
- Plug your HDMI cable into your phone and your TV or Stereo
- Hit the Detect Button
- Hit the Home button and navigate and start youtube application
- Start playing a video but before the video starts displaying tilt the phone so it faces the ground then back up.
- You should her the phone BUZZ once
- The output should now show up on your HDMI output and you should be able to watch your content on your big screen TV.
- When you are done watching your video, tilt phone face to the ground then back up.
- Phone will buzz twice and HDMI is now displayed and screen on phone will update and allow you to navigate.
|
|
UPDATE - 2.2 Android Kernel Bug |
|
|
|
|
Written by Gman
|
|
-------Update 12/13/2010---------
Verizon and Motorola have released version 2.2.1 for the Motorola Droid X. While Motorola has never formally acknowledged the bug, it appears this latest release fixed the HDMI bug detailed below. We recommend upgrading your phone to 2.2.1 to help eliminate the chances of the bug listed below manifesting itself
--------------------------------------------
As of this writing (October 16th,2010) I still have not received any official information from Motorola about whether they acknowledge the bug in the kernel display drivers on the Droid X that was introduced in 2.2 OTA update. (https://supportforums.motorola.com/thread/38053) I have been passing significant amount of information to Motorola but as of the last week even those who had been responding about the bug have gone silent. The Google/Android Market Place is pretty much broken and doesn't behave as advertised by Google. They state that they retain copies my application to allow users who purchase the app to re-download it if necessary. I now know that this really isn't the case. If I "unpublished" my application to keep it from being purchased it removes it so even those who have purchased it can't re-download it if they reset their phone. As a compromise for the folks who "HAVE TO HAVE" the Real HDMI application am going to be periodically returning the application to the market to allow individuals who already purchased the app to receive updates. And to allow folks that understand the Kernel bug can get the app. This weekend will be the first of those weekends. 10/16/2010->10/17/2010 will temporarily have the application back up on the android marketplace. Will be "unpublished" it again come Monday. This time of sporadic publishing its just a workaround until I am able to work out the logistic of moving things over to a more flexible/reliable distribution channel for the application.
WARNING: The bug as I have documented on the Motorola forums is a bug in the Android 2.2 Kernel for the Droid X. It doesn't always occur but has the potential to occur on ANY Droid X when using HDMI output of any kind. This includes using Real HDMI or even the internal Gallery application. If/when phone does "freeze" up when disabling HDMI output on your phone. It will require you to remove your battery of your phone, wait 30 seconds then reinstall the Battery. Your phone will then be able to restart.
The HDMI output bug (https://supportforums.motorola.com/message/245559#245559) occurs when you disable HDMI output and the phone "tries" to turn the display buffer for the internal LCD display back on. Under certain situations the display buffer seems to be asleep due to power saving settings that I have yet figured out how to disable. When this happens the display buffer/controller doesn't receive the signal to turn enable (must be on to receive enable command). At this point the phone pretty stupid and won't renable the LCD display until phone is turned off. Since the bug occurs during a specific set of events where power management seems to kick in, its possible that bug doesn't occur at all on a phone due to how folks use the phone while using HDMI output. For example playing a video usually doesn't trigger the bug (CPU is in use), but playing a video then letting phone sit for a while after video is over (CPU goes idle) will often trigger the bug. This bug can occur even when not using Real HDMI and when just using default Gallery/VideoPlayer on a Droid X with Android 2.2 installed. Best Case Scenario if bug occurs: If this occurs while real HDMI is still running you can reenable HDMI output (using tillt method or shake method depending on how you have it configured) and the HDMI output will enable the HDMI output. At this point you can hit the power button and select "power off" then power the phone back on and things should be working like normal again. Worse Case Scenario: Phone gets REALLY confused and a kernel exception occurs. The phone will appear to have frozen content on the screen. The HDMI output can't be reenabled and you will have to pull the battery out of the phone, wait 30 seconds, then put it back into the phone and power phone back up.
|
|
Last Updated on Monday, 13 December 2010 19:02 |
|
|