My freeware concept for a multimedia entertainment device.

by Loris » Sun, 15 Mar 2009 13:13:37 GMT

Sponsored Links
 GamePad MultiMedia mobile entertainment device concept specification.
Similar to Nintendo DSi but with Larger and higher definition
screens, Wider keys each with own display, Much more SSD memory,
Better CPU and GPUs, and No camera on the outside, just one screen
side camera for video phone.
Running Google Android Linux operating system with a Nintendo DSi
operating system emulator so as to be able to run all Nintendo DS and
DSi console 3D games and plus additional video phone function graphics
on SD/SDHC/SDXC flash cards.
Best performance per watt CPU and GPU for bottom screen; Texas
Instruments OMAP4440 - 1+ GHz dual-core ARM Cortex-A9 MPCore + PowerVR
SGX 540 GPU + C64x+ DSP + ISP (Image Signal Processor)
Best performance per watt second GPU for top screen with Linux OpenGL
3.0 compliance 3D Modeling GPU: S3 Graphics Chrome 540 GTX with 256mb
ram and 1080p output. [Cards using this GPU retail for US$69.95]
8 GB of SSD internal flash memory or 2nd SD/SDHC/SDXC flash card.
[Nintendo's DSi has only 256mb internal memory. ]
500mb ram.
SD/SDHC/SDXC flash card slot on front. [ Much smaller, more durable
and more capacity than a DVD or HDD ]
USB 1/2/3 More capacity.
Wireless [WiFi, LTE, WiMax internet and Bluetooth].
Measuring 5 cm thick, 24cm long 12 cm wide.
Each new GamePad MultiMedia mobile entertainment device costing under
$600 and lasting at least 3 years before up-grade.
Folding open length ways to reveal a top screen and a bottom screen
each 16 cm wide 9 cm high.
Each screen standard television 16:9 ratio with 1920 x 1080p FullHD
A left speaker centered to the left of the top screen and a right
speaker to the right of the top screen.
A 16 direction 3 cm toggle controller on 3.5 cm next to [to the
right] of the bottom screen.
10 tactile display keys with 1 cm x 3 cm wide [20 pixel by 60 pixel
wide] display on each key to display key function text and/or icon
changing according to game play.
4 tactile display keys to the left of the bottom screen.
One tactile display key above and one tactile display key below the
toggle controller to the right of the bottom screen,
Also one tactile display key above and one below each of the speakers
besides the top screen.
Also with stereo headphones jack.
Audio and video playback.
Videophone camera on display side between screens. Top screen for
self image. Bottom screen for other persons image. Using WiFi, LTE,
and WiMax internet on home femtocell.
Digital television and radio.
Gaming console.
Word processor for text messaging.
On the bottom screen touch screen typing keyboard and for editing of
documents and navigation of program menus.
On the top screen document or web-page links and menus.
Pen kept in hole and on string for touch-screen on both screens.
With one click wireless Internet download to solid state flash drive
of the currently playing track.
Betavoltaic nuclear battery able to provide constant power for 10
years [ half life of 20 years ] so no need for external charger ever}
PROPOSAL for government funding;
: $150,000,000 for an open source freeware 3D graphics and multi-media
gaming console operating system {Google Android}
: $100,000,000 for a {Nintendo DSi) emulator {iDeaS} for the {Google
Android} {Linux} operating system on the {Texas Instruments OMAP4} and
{S3 Graphics} Graphics card.
: $150,000,000 for {Nintendo DSi} multi media (Audio, Text emai

Other Threads

1. Bind to a remote service


I could not find "Reply" on the post:

2. Trying to compile Android on to a Full blown ubuntu/linux distro

On Linux, it is possible to build the Android simulator, which runs many
parts of the platform in a single Unix process (so no real security for
you), doesn't use the custom C library, etc...

if you don't want to go this route, you will need to patch your kernel to
integrate a few Android-specific things like the Binder driver.
second, Android expects system files in different places, comes with its own
init program and scripts, etc...

running the whole of Android on top of a standard Linux installation will be
a lot of work with probably few benefits. You should probably try to get the
Dalvik VM running first on Ubuntu plus some of the system libraries that
don't depend too much on Android-specific behaviour.


3. RIL data service flow path

4. Can't seem to get something as simple as a ListView to work

5. email client of emulator ( second sdk release) not working

6. JNI - FindClass() returns null

7. UI question: onTouchEvent and ListActivity