opengl supported well in G2?

by tainy » Tue, 04 Aug 2009 19:26:58 GMT


Sponsored Links
 hi
this is in android 1.5 version
I am using some OpenGL apis (GL10) for some graphic effect. The code
runs well on
emulator but not well on my HTC magic(G2). All the images which has
some skew effects
can not be shown and only show a white rectangle.

Could any one please give a hint what could probably cause this?
I really have no idea.

Thanks in advance.
--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Community contributions to design (WAS: Android v. 1.5 = FAIL #2: Directly Manipulating Settings)



Key phrase: "was found". More on that below.


Let us assume, for the moment, that the implemented solution is the best
solution, or at least the best solution given implementation timetables
and available staff.

The problem is transparency.

As is evidenced by several posts on the original thread, we in the
development community have ideas relevant to this area. For example, Mr.
Legendre's post that came in while I was writing this seems like a fine
middle ground between the original implementation and what has
transpired with 1.5.

Why is the core Android team only getting this input now? Because, as
far as I am aware, NOBODY #(#$)@#(@ ASKED!

I doubt there are all that many people in the developer community who
actually want to drain the device battery excessively or without user
awareness. Similarly, I doubt there are all that many of us who were
using this stuff to violate user privacy and are left twisting our
handlebar mustaches, cursing those meddling Googlers for foiling our
devious plots. Hence, we are all being punished for the deeds of a few.

When the problems arose, there were three basic ways of addressing them:

1. Ask the developer community "Hey, considering some of you are
(intentionally or inadvertently) screwing the users, any suggestions for
how we can fix this?" In other words, involve us in the design.

2. Ask the developer community "Hey, we see these problems, here's our
cut at a solution, any ideas?" In other words, involve us in the design
review.

3. Don't involve the community in the design. Considering that
implementation of this sort of thing already happens behind closed
doors, you wind up with what has happened -- we only get to provide
input after the cow has left the barn.

By your use of "was found" and the rest of the tone around this, I am
assuming management chose door #3.

Going with #1, or even #2, gives Google some benefits:

-- You might get some good ideas. While many of us wouldn't pass the
Google entrance exam, we're not all complete morons. I, for one, am a
very incomplete moron.

-- You might get some people interested in contributing to the development.

-- You avoid giving the development community the sense that we're all
"the bad guys" in this story, by giving the community a chance to help
police itself rather than, in effect, tarring all of us with the same brush.

If Google *did* involve some folk in the community on the design (e.g.,
by private invitation), that's cool, but you might consider letting us
know that happened.

I know the core Android team is short-staffed. Short of trying to pump
up Google's stock price, the best way I can see for us in the community
to help with that is to help with the development of Android proper.
However, particularly in cases like this, that can only happen if we are
given the opportunity to help, even if only on a small piece of the puzzle.

Give piece a chance.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

Warescription: Three Android Books, Plus Updates, $35/Year

--~--~---------~--~----~------------~-------~--~----~

2. How to build full Android for X86 desktop PC - black screen

I'm trying to port Android for Intel X86 desktop PC.
I though it could be possible, because someone already have ported to
ASUS eee701 which is X86 based.

I followed like this.
http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/BuildAndroidForX86Platforms

And applied patch from here.
http://code.google.com/p/patch-hosting-for-android-x86-support/downloads/list

The only different thing I've done is inserting intelfb driver to
kernel image instead of building as a module. And I check it works by
checking /sys/class/graphics/fb0.

Anyway I've booted with new built kernel and rootfs both for eee701.
But during the boot, screen goes black seems to be dead.

I think something wrong on invoking zygote.

And I tested like this.
When I just commented out the zygote invoking part in init.rc shell
command came up.
And following process could be found but mediaserver.
- servicemanager, vold, installd, adbd

Error message below comes up repeatedly.
------------------------------------------------------------------------------
init: event { 'add', '/kernel/uids/1013', 'uids', '', -1, -1 }
init: waitpid returned pid 2003, status = 00007f00
init: process 'media', pid 2003, exited
init: process 'media' killing any children in process group
init: event { 'remove', '/kernel/uids/1013', 'uids', '', -1, -1 }
------------------------------------------------------------------------------

So I think zygote and mediaserver are not working properly.
Please help me out~! >,<

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Theme issues with 1.5

4. Bluetooth not working on G1 device (cupcake version)

5. wpa_supplicant wifi problems no scan results

6. after launching audio recording intent "MediaStoreAudio.Media.RECORD_SOUND_ACTION"

7. Do you have an example of layout like contact's form (add) ? (version 1.5)