memoerdezguey
Member
- Feb 18, 2011
- 16
- 0
- 0
Thats amazin...sooner than expected....thanx for givin me another reason to live lol YOU ARE THE MAN SAM!!!!
Next release is going to be public, open to everybody. I couldn't finish it last night and this evening I have other commitments, I think it will be ready this weekend.
^^
I have a 7" 720P LCD I molded into my dash (set back 3"inches) several years back. I'm looking forward to running "Torque" on that screen. On the downside, I'll need to do a HDMI to VGA conversion.
Next release is going to be public, open to everybody. I couldn't finish it last night and this evening I have other commitments, I think it will be ready this weekend.
^^
I have a 7" 720P LCD I molded into my dash (set back 3"inches) several years back. I'm looking forward to running "Torque" on that screen. On the downside, I'll need to do a HDMI to VGA conversion.
I have a possible suggestion for those of you that are having the screen going off the edges. I am not ashamed to admit that I was thinking I had the same problem, but I realized that I had a setting for the aspect ratio on the TV set to cut it off.
Most TVs have multiple options for aspect ratio. For example, zoom, hourglass, etc. Just make sure this setting is set to fill the screen.
I am not saying that is the case for all of you, it just was for me. Once I changed the setting, it filled the screen perfectly without messing with the X Y resolutions.
Adding on to the notes and known issues/observations:
1- To achieve hardware acceleration, video memory (minimal) has to be used. Some poorly coded programs that also use video memory will try to grab a hold of the entire memory block instead of the available. This will cause them to crash when you are in hardware mode reserving a small block of memory to yourself. The only application that I found to be doing this is, strangely enough, HTC's Gallery (specifically video playback mode). Gallery video playback will keep trying to acquire the whole video memory, put the phone in a tight infinite loop doing so and eventually force close (after about 40 sec).
Compatibility or software mode does not use video memory and is safe to keep on while launching Galley video playback. Compatibility mode also does not make use of the "supercharged" feature, custom res or fullscreen mode.
2- FPS: Your frames per second will not be the same as on your phone. This is because the app is designed to keep the phone as primary display and output a secondary to the HDMI port. You are also outputting, most likely, a 1280x720 pixels which is almost ~2.5 times more the normal output. So in total you are pushing 3.5 lcd size screen worth of pixels (phone lcs + hdmi). Things can be improved if we freeze the phone display, but that wont be mirroring (maybe a feature in FullHDMI 2). Expect, however, to get more FPS in 3-D games (I get upwards of 40 fps on Raging Thunder 2) than 2-D sine he 2-D engine does the mirroring.
3- Lag: Some TVs (like Insignia) use an image enhancing and noise reducing engine. This extra processing puts the TV about half a second behind the phone making games unplayable by looking at the TV only. Watching movies is fine since nobody cares if the phone is a little faster than the TV. On this Insignia TV, I had to go in and turn off two image enhancing and noise reducing features, and now my phone and TV track together. I know Sony has its own engine, I do not know if the extra processing there introduces lag. I have two other TVs with no lag issues, but then they don't use any image enhancing engines.
Again, the app should not lag in mirroring, if you experience any lag then please check your TV and share your observation with us.
4- This app was not designed to display youtube or other apps that already work over HDMI. To use such apps you should stop FullHDMI from driving the HDMI signal first.
"You will need the Kernel posted several pages back on this thread to enable some features, and root."does this one need the Kernel like the other hacked version that was released?