Unable to remove the prev,next buttons of MediaController, please help me

by Marco Nelissen » Mon, 29 Jun 2009 23:42:58 GMT

Sponsored Links

It's not possible for us to try out your code, since you didn't
include the required layouts.

Since you're using your own custom layout, just remove the 'previous'
and 'next' buttons from it. I believe I mentioned this to you several
days ago. Did you try it?


Other Threads

1. Gigabyte gSmart MW702

Hi everyone!

I'm interrested in porting android to this device, but first I would
like to know that is this possible at all. I mean for example, are
there drivers for the hardware in it? It is a WM6.1 based device and
it has a Marvell PXA270 520MHz processor, but I can't find who the
other hw vendors are.

Here is a specification I found: 

Also I don't have to flash any bootloader, etc. to the phone because
I'm planning to use this multiboot system:

So the only thing I need is to build a system image with the
drivers(if there is any).

So if anyone knows what are the exact hardwares in this phone, and if
the drivers are exist or not, please tell me. Thanks!

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

2. LVL and Settings.Secure.ANDROID_ID - how secure?


I am integrating the new Android Licensing scheme and was wondering
how secure licensing would be if I just use Settings.Secure.ANDROID_ID
as a unique device ID.  The sample app uses this, but suggests using
more IDs as this is a single point of attack.  However, the Licensing
docs seems to discourage the use of something like IMEI numbers just
for licensing purposes, as this would require a READ_PHONE_STATE

I wouldn't want to add that permission just for licensing, since my
app doesn't using anything else in the Telephony stack, and users
would probably be suspicious when they see this new permission.  But
there are some posts on the internet showing it is (was?) possible to

Is this still the case?  If so, for anybody, or just root users?  How
would that affect licensing in my app?  For example, would it be
possible for someone to spoof ANDROID_ID, buy apps, make the spoofed
ANDROID_ID publicly available and so allow anyone who changes their
ANDROID_ID to the spoofed one to get access to those apps?

I guess one way around that would be to implement a device limiter,
but that opens up a whole new can of worms, something that I would not
want to do.

So, is using ANDROID_ID "safe enough", or could someone suggest an
alternative that doesn't require permissions?



3. Android IME: how to show a pop-up dialog?

4. Incidental files being pulled into the .apk

5. Android, OpenGL, and EGL woes

6. how to control the screen rotation in my application

7. Custom themes for native application