Device Proposal

by Stephen Jarman » Wed, 07 May 2008 21:05:22 GMT


Sponsored Links
 Hello all! I'm very excited, much like you, about the Android platform
for mobile devices - as I think it will really provide what I want in
a phone. So, in a class project where we had to design an ideal mobile
phone to appeal to the mass market, the first thing that came to my
mind was Android. I was going to base my device on Android.

So, after a bit of thought and some effort, I came up with a basic
shape and design concept for the "first" real Android device. We
weren't really going to create one, of course, because it's just a
school project. However, I thought that I might want to share what I
have come up with with the rest of the Android community to get a
wider opinion.

The main idea of this phone, which I have temporarily dubbed the
&threesixty (AND360), is to have no visible buttons on the front of
the device - just a large touch-screen. The &threesixty is just about
the size of a BlackBerry Curve, to give you an idea. The screen covers
the whole front of the device up until a couple millimetres away from
the edges. On the sides, there are rocker buttons, a play/pause media
button, a "profile" mode button and a camera button. There is a
compact 2MP camera on the back, as well as an LED flash, doubling as a
torch. The top holds a Mini-USB connector and a standard 3.5 mm audio
jack, as well as a power/standby button. The bottom holds the two
speakers, much like on the iPhone.

What do you think about the 2MP camera? Would it be too small? I'm
mostly concerned for the actual size of the device, although places to
store larger photos might become a hurdle. Oh yes, I almost forgot
that the device has the option for the upgrading of memory through a
micro-SD, stored underneath the battery.

As shown in the mock-up picture, there is a metallic strip curving
around the middle of the device, bordered at the bottom by a thinner,
white and translucent strip, which holds "colour-changing" LEDs, which
can be set to stay a certain colour when in use, or even a slowly
changing spectrum - all being set through a control panel in Android.
This could also act as the notifier LED, so that it could change
colour upon a message or event being received.

If you would like to see the mock-up device, please visit...
 http://sailing-fast.com/and360 

Thank you in advance for all your opinions!

Regards, Stephen Jarman
Sail Fast: sailing-fast.com
--~--~---------~--~----~------------~-------~--~----~



Device Proposal

by Muthu Ramadoss » Thu, 08 May 2008 06:15:08 GMT


 If I get you right, you'll  be doing a design for the Android device that
the OEM's can use, right?

Why not? You can probably take these designs to the OHA members and may be
get a couple of them interested. Good luck.

Checked your website, may be you can make it a bit simple to navigate
around. The "click here" doesn't take me back to the image again.

On Thu, May 8, 2008 at 2:35 AM, Stephen Jarman <[EMAIL PROTECTED]>





-- 
take care,
Muthu Ramadoss.

 http://mobeegal.in 
find stuff closer.

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


Sponsored Links


Other Threads

1. Sudah diralat, WTS: Motorola Titanium XT800 Heading To South Korea [Cheap Android Phone To Have 3.7-Inch Display, HDMI Out, 600MHz Processor]

Hihihi cuma mau ngisengi bro mod




Terima kasih bro,

Sudah saya ralat tadi pagi, subject:

Re: Ralat WTI, Motorola Titanium XT800 Heading To South Korea [Cheap
Android Phone To Have 3.7-Inch Display, HDMI Out, 600MHz Processor]



Salam Android,

AH





--
"Indonesian Android Community [id-android]"

2. How to know a view size before it's rendered

Hi There,
I'm a beginner of Android and I'm trying to understand how I can get
the size of a View (or a ViewGroup) before this is rendered on the
screen.

What I'm trying to achieve is to apply some animations on some child
views and it would be great if there's a way to know in advance the
size of the parent view (ViewGroup) or any other child view before
this is displayed on the screen so that I can set some animations'
settings based on the measurements of other View objects.

At the moment, some animations' settings are hard coded which I don't
like at all and I only discovered that I can get the parent view
measurements (height and width) after the ViewGroup is displayed.

I couldn't find any obvious method or callback and I'm wondering if
there's any or amy technique useful to achieve my goal.

Thanks in advance for any help.

Mickey

-- 

3. Text color in fast scroll SectionIndexer box

4. Perihal Kloteran Battery Gum Plu

5. Sudah diralat, WTS: Motorola Titanium XT800 Heading To South Korea [Cheap Android Phone To Have 3.7-Inch Display, HDMI Out, 600MHz Processor]

6. mo tanya tentang bootloader.

7. First impressions on Droid