it's going to sound funny but i was thinking about making a custom pc case in the shape of an android...
but i don't know it's size... i want to keep the proportions right.
any chance someone knows them?
Sounds like a great idea, especially to somebody like me that loves all things Android sized/coloured.
I would take any picture you can find and just scale it up by % until it's the size you want. Use the resulting dimensions for your template.
Related
Hey guys, I am looking for a phone for my dad and he has poor eye sight and his fingers are pretty large. What would be a good phone for him. Preferably something very simple that has large font and decent sized dial pad. He currently uses the Motorola V3 and has been using that for years. I am trying to look for something to replace that with. Oh yeah and cheap as well.
check out emporia:
Emporia website
Well, my dad isn't that old. I was looking for something more like the razr with a bigger screen with a simple UI not complicated like Windows Mobile phones.
If he uses the phone only for calling, and not SMS/MMS, you might want to look up the Motorola F3 - rather large keys, simple UI, almost indestructible, very long standby time, high-contrast e-paper based screen, really cheap (about 30$ new, without simlock). But it's SMS ability is very limited (scrolling single line text), no MMS at all, no advanced features. It's just a simple phone with SMS and alarm clock.
Try searching youtube, there are some video reviews there.
I also looked at the F3 and that phone looked like it would be perfect but there were a few drawbacks that my dad would not like. I am sorry for not specifying more clearly, he would need a camera built in and I am assuming a color screen for the camera. The camera would be for his business purposes and possible emergencies that would require the usage of one which have come out a few times for him in the past year already. So the features I am looking for are:
Big screen with big text.
Decent sized keys.
Color Screen.
Camera (better than V3 hopefully)
Form factor does not matter.
Simple UI (not Windows Mobile OS)
And CHEAP
Thank you for taking your time and helping me out.
Maybe have a look at some of the Samsung phones - I just got my dad a Samsung E390 and he loves it - very easy to use, he gets on fine with the keys - they're not big but easy used. The display is great - text is a great size - that's the first thing my dad said - he could actually read it! The camera is OK - not anything to write home about but it takes a reasonable picture. Moreover it's cheap - I think we paid about £50 on pay as you go on Orange.
http://www.gsmarena.com/samsung_e390-1770.php
johnny13oi said:
Well, my dad isn't that old. I was looking for something more like the razr with a bigger screen with a simple UI not complicated like Windows Mobile phones.
Click to expand...
Click to collapse
well,my dad have presbyopia,so I buy him a SAMSUNG D900,he says it's good
for his presbyopia.
Many SAMSUNG cellphone have big TXT and number.
hope you find it soon!
I have a Kaiser and an iPhone. iPhone has a simple UI and nice key sizes.
I posted this in the Hero General topic a while back and thought I would ask for opinions again.
I am playing with a few self-made roms and just trying to get myself REALLY familiar with this android device that has consumed a lot of my development time (apps and such).
Anyway I got to the part where I am trying to rip to shreds everything I can in an effort to make it faster. When I got to the "PNG optimizing" I always see others doing, I kind of sat back and thought about this. Why am I wanting to do this? It may sound like I dumb question at fist, but why am I trying to make these PNG's more compressed?
I know that on most applications where images need to be displayed in a hurry you want to have large uncompressed images. For example, on my HTPC I have all of my high res backgrounds as uncompressed bitmaps running off of a flash drive because any time the processor has to spend decoding the image to display it is time away from switching the menu's or loading up a view.
So I am at the part now where I need to determine if the time spent decoding the image is worth the extra KB used in RAM. And which has a greater impact on performance. I have a feeling optimizing PNG's has been done in the past for space reasons and wasn't really given this much thought. People just do it because its the first thing that seems logical.
Has anyone else REALLY thought about why they are optimizing all of these PNG's? Yeah, it makes sense right off the bat, but if you think about it, is it working?
Since there is really no way to determine/compare these small results, I guess I would have to come up with a way to check. This may be really minor or have some placebo effect. But I am thinking sense is just a hair quicker on my own small tests.
What do you guys think? Let me know if you think I am missing something or am totally off on my "used ram vs cpu usage" theory. It might have been answered before and I am just wrong. I just love math and am totally looking for a good scientific answer to this question, even if it means I am wrong.
What's faster, moving an image from storage at bus speeds or moving smaller amounts of image data, and expanding at cpu speeds? You call it. To do a boot image in photoshop, one color (the extreme case) it took 615 bytes optimized, verses some 16k bytes in (320 x 480) which results in 21.6 k in cmyk color.
That is the extreme case. The actual screen is hardware bound, colors and size are predetermined, so images have to be transformed to fit, any way. Do the trans formation at run time or before?
Food for thought.
Here are the details.
http://www.youtube.com/watch?v=N6YdwzAvwOA
Has anyone here seen this phone?
ww.youtube.com/watch?v=PhKxpYRip18
Pretty awesome GUI. Would it be at all possible for someone to mimic it's interface on an android phone? Even if it were like say, a home replacement app?
The idea behind the interface is pretty cool, but this phone leaves something to be desired.
the zooom control looks like 100times better than pinch to zoom
feels more like the android cut thing for setting images... or like zoom on andwobble
but no big news.
don't fancy the ui. I can use my android phone single handedly just great
And I would miss kinetic scroling... If they don't include it, they are nuts
At 5:44 she actually did what I would fear the most - release her thumb too early, starting the wrong app
plus the phone is still to lame for everyday use...
But design looks very nice. and the idea is based on minority report xD
Yeah, I've posted about this phone in a few threads (X10). It looks prety tight. Hasn't been released yet. I'm gonna get one just to have it, when it comes out. Should be easy to port to android phones.
But I'm getting THIS one in a couple of months.
wcdisciple said:
Should be easy to port to android phones.
Click to expand...
Click to collapse
nice to hear someone saying that
i have also known the first else for ... a long time? and always liked the gui. would be nice to have that for my android phone
i just noticed the first else device looks kind of like a complete black, even slightly flatter (backside) iphone 4g xD
Is that Apples new design this year? (The flat gray color, no more shiny chrome)? And also no more roundness? (How the bezel is like flat going to the top and bottom)
It certainly presents some interesting concepts, especially with one thumb use.
However I don't see their entire OS being a success in the near future.
Hi first at all let me apolgize for bad english
Question is It is possible use screen as scale
Will the screen hold up to 500g
I love to build diy project 10inch screen with android os (cheap from ebay aprox.130 euro) in kitchen work top as recipe book, scale, and player while cooking all together
It is just idea make life easy for my wife
Hmm, Android can record touch pressure. But I don't know how to implement the feature in your kernel.
I hoped someone can make app to measure pressure
something like this just build in work top not for chopping
w.unplggd.com/unplggd/look/flexible-lcd-display-kitchen-cutting-board-047445
You do realise that the screen is capacitive (accctually this is an assumption), and therefore anything that doesn't conduct or produce charge will do nothing when put on the screen.
It's an einteresting idea, however when I played around with the screen and touch events in the API I found it to be rather unreliable. Anyway, I'm not trying to put you off or anyone else, just stating some issues applicable to this idea.
You, sir, have just won the Dumbest Idea of The Hour award. Good show.
khaytsus said:
You, sir, have just won the Dumbest Idea of The Hour award. Good show.
Click to expand...
Click to collapse
It really isn't a dumb idea, just not really practical with hardware we have available to us.
I think if he got his idea across more clearly it would make a lot more sense.
I will put the android device on scale ,built case and than put in work top and that's it android scale better then buy built in scale from meile (220€) which can't play music and store recipes still cheaper.
Sent from my Nexus One using XDA App
Okay... I am a complete noob when it comes to programming, but I have an amazing app idea. I know I probably sound like every other annoying idealist out there but hear me out. I have often been stuck wanting to measure something but have never had a ruler or dial caliper. My idea is this. what if we could utilize the camera to detect everyday objects then use very close approximations of those items in order to compare to virtually any item to determine the items dimensions almost exactly. for example, lets say i want to know the dimensions of a rectangular bottle. well if we were to put it on a 8 1/2" x 11" piece of paper, we could use the comparison of the paper to a face of the object in order to very closely approximate the dimensions of the face. Its far fetched, i know... But i really think it could become an essential app for everybody and I would really like to get some help from some developers to make this app come true. It would be a very complex program with many algorithms i suspect so we'll need multiple programmers. Any takers? it will most likely be a long term project as we add more and more reference objects.