Commercial Application Testing

Discussion:

A Zen

2012-09-30 15:29:25 UTC

FIrst, an amazing effort here to port Android onto Intel.

I have 4.0 RC2 running on an older eeePC.
It installed perfectly and runs. The audio works. Keypad works. Keyboard
and hot keys work. Very nice.

I wanted to test it with commercial applications and see if I can use it to
drive an LCD TV.

The first test was display. I plugged the PC into the TV using a VGA cable.
I used the previously posted method for redirecting the output:
video=LVDS-1:d video=VGA-1 ***@60
The results are pretty good, there is some screen clipping.
Here is a link to the album<https://picasaweb.google.com/107241364758310054105/AndroidX86OrgBuild40RC2OnASUSDisplayedOnLCDTV?authuser=0&authkey=Gv1sRgCICd85T5xrraogE&feat=directlink>:

The next was tests with commercial applications: The results are:

1. QVC -- would not download. The message was "unsupported device".
2. NBC News -- the problem is the application rotates 90 CCW, and the
mouse pad movement is rotated too. The videos do play.
3. CBS News -- same as NBC.
4. Netflix -- installed but would not launch.
5. YouTube -- flawless, but I had to turn off HD playback.

Anyone else tested applications?

I will have to get into the O/S to fix the rotation (I am guessing)

I am impressed how fast the eeePC is. If I can get this to run, it will
make the machine useful again.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/Zb4N7-DNEecJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

Christopher Price

2012-10-01 04:25:05 UTC

Permalink

I'm not aware of many LCD TVs that use 1024x768 or XGA resolution. Most
HDTVs today run at 1280x720 or 1920x1080 (960x540 if 1080i).

What you are probably experiencing is overscan, a common problem with all
computer-to-TV outputs.

Google has not provided an overscan tool, and the GPU vendor's overscan
correction tools are all intended for X11. In short, it's a problem.

The recommendation from Google at this point is to pad apps to account for
overscan in the UI. It's far from a true solution, however. I suspect
Google in future releases will add an overscan control to the Android
screen manager.

As to the performance issues, most of those are due to x86 vs ARM, and will
resolve themselves over time.

Post by A Zen
FIrst, an amazing effort here to port Android onto Intel.
I have 4.0 RC2 running on an older eeePC.
It installed perfectly and runs. The audio works. Keypad works. Keyboard
and hot keys work. Very nice.
I wanted to test it with commercial applications and see if I can use it
to drive an LCD TV.
The first test was display. I plugged the PC into the TV using a VGA cable.
The results are pretty good, there is some screen clipping.
1. QVC -- would not download. The message was "unsupported device".
2. NBC News -- the problem is the application rotates 90 CCW, and the
mouse pad movement is rotated too. The videos do play.
3. CBS News -- same as NBC.
4. Netflix -- installed but would not launch.
5. YouTube -- flawless, but I had to turn off HD playback.
Anyone else tested applications?
I will have to get into the O/S to fix the rotation (I am guessing)
I am impressed how fast the eeePC is. If I can get this to run, it will
make the machine useful again.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/mMM3CKmvhqkJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

A Zen

2012-10-02 23:43:09 UTC

Permalink

Post by Christopher Price
I'm not aware of many LCD TVs that use 1024x768 or XGA resolution. Most
HDTVs today run at 1280x720 or 1920x1080 (960x540 if 1080i).
What you are probably experiencing is overscan, a common problem with all
computer-to-TV outputs.
Google has not provided an overscan tool, and the GPU vendor's overscan
correction tools are all intended for X11. In short, it's a problem.
The recommendation from Google at this point is to pad apps to account for
overscan in the UI. It's far from a true solution, however. I suspect
Google in future releases will add an overscan control to the Android
screen manager.
As to the performance issues, most of those are due to x86 vs ARM, and
will resolve themselves over time.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/AS80Q0I6IicJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

Christopher Price

2012-10-03 00:20:35 UTC

Permalink

Well, if you wanted to work on an overscan implementation, I think that would be a great help.

As to apps being ported to x86, that is likely going to happen on its own. Chrome was just released a week or two ago for x86. With Intel launching flagship smartphones this year that use Medfield as their CPU, app developers are already getting pushed to port their apps to x86. I would not be surprised at all if the vast majority of the top 100 apps were x86-friendly by the time 2013 rolls around.

Our problem is that we need help right now maintaining the Android-x86 codebase. We just lost our main Mesa developer who was handling the porting of Mesa (had a baby), and I would say graphics is one of the main deficiencies in Android-x86 today.

Christopher Price
ChristopherPrice.net

Chris -- you are correct about displaying on a LCD TV. The eeePC displayed correctly on a 1080p monitor.
Any thoughts on supporting commercial applications? I am guessing Netflix is looking at the hardware and won't work on anything that could capture their broadcast.
The rotation is another problem.
At this point, I guess I either download the source and get involved or not.
Regards...
I'm not aware of many LCD TVs that use 1024x768 or XGA resolution. Most HDTVs today run at 1280x720 or 1920x1080 (960x540 if 1080i).
What you are probably experiencing is overscan, a common problem with all computer-to-TV outputs.
Google has not provided an overscan tool, and the GPU vendor's overscan correction tools are all intended for X11. In short, it's a problem.
The recommendation from Google at this point is to pad apps to account for overscan in the UI. It's far from a true solution, however. I suspect Google in future releases will add an overscan control to the Android screen manager.
As to the performance issues, most of those are due to x86 vs ARM, and will resolve themselves over time.
FIrst, an amazing effort here to port Android onto Intel.
I have 4.0 RC2 running on an older eeePC.
It installed perfectly and runs. The audio works. Keypad works. Keyboard and hot keys work. Very nice.
I wanted to test it with commercial applications and see if I can use it to drive an LCD TV.
The first test was display. I plugged the PC into the TV using a VGA cable.
The results are pretty good, there is some screen clipping.
QVC -- would not download. The message was "unsupported device".
NBC News -- the problem is the application rotates 90 CCW, and the mouse pad movement is rotated too. The videos do play.
CBS News -- same as NBC.
Netflix -- installed but would not launch.
YouTube -- flawless, but I had to turn off HD playback.
Anyone else tested applications?
I will have to get into the O/S to fix the rotation (I am guessing)
I am impressed how fast the eeePC is. If I can get this to run, it will make the machine useful again.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/AS80Q0I6IicJ.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

Amogh Harish

2012-10-03 05:23:20 UTC

Permalink

Post by Christopher Price
Well, if you wanted to work on an overscan implementation, I think that

would be a great help.

Post by Christopher Price
As to apps being ported to x86, that is likely going to happen on its

own. Chrome was just released a week or two ago for x86. With Intel
launching flagship smartphones this year that use Medfield as their CPU,
app developers are already getting pushed to port their apps to x86. I
would not be surprised at all if the vast majority of the top 100 apps were
x86-friendly by the time 2013 rolls around.

The Chrome release was for devices running Medfield CPU's only. Other
builds aren't supported at this time. Please research before posting.

Post by Christopher Price
Our problem is that we need help right now maintaining the Android-x86

codebase. We just lost our main Mesa developer who was handling the porting
of Mesa (had a baby), and I would say graphics is one of the main
deficiencies in Android-x86 today.

Post by Christopher Price
Christopher Price
ChristopherPrice.net

Post by A Zen
Chris -- you are correct about displaying on a LCD TV. The eeePC

displayed correctly on a 1080p monitor.