OpenMobile will support Android
check it out: http://www.mp3car.com/vbulletin/openmobile
Is there any Android frontend for my brand new Archos 5 Android? Or how difficult is it to use some existing one. Android is Java/Linux, right?
OpenMobile will support Android
check it out: http://www.mp3car.com/vbulletin/openmobile
Former author of LinuxICE, nghost.
Current author of nobdy.
I would refer you back to the following post: http://www.mp3car.com/vbulletin/soft...-platform.html
Yea open mobile will....but doesn't yet. Mono development on android is crawling along so no idea how long till the necessary functionality is implemented.
On a side note, android has inspired my design a little bit, well see if anyone can tell where in the next release.
Agreed... Audio actually isn't too bad but video is nearly impossible. We would need to tie into a third party decoder and even then video needs to be specially formatted to exactly the resolution of the device (and each android device is different). Theres supposed to be a VLC port to android that will make some of that easier but i'll believe it when I see it.
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
currently i am using widgets on different screens on my Archos 5 Android device for the car.
widgets for music player, wheater, compass with backgrounds make already a good looking skin/frontend. this could be expanded with news, rss etc. feeds if online
the only widget i am missing is for the navigation program. this always has to run fullscreen to see the next turn etc. would be nice to have widget with distance, eta, next turn, next exit, next street etc. just placed on the home screen. dont need more actually.
android is out of the box usable (i.e. large fonts for file copy apps and settings, starting programs etc.) in car environment or at least mobile environment. you dont have to have a frontend to deal with that because of windows desktop resolution. so i think to add widget to complete the user's need to switch between apps, show information etc. is the way to go. this allows most flexibility for look and feel vs. functionality needed.
1) Quite a bit of android functionality requires a press-and-hold...how is that optimized for in car use?
2) Since the notifications shade is not accessible on most touch screens (edges are very difficult in resistive touchscreens), do you have another plan for that?
3) Do you enjoy having to transcode all the videos you watch?
4) Do all of the separate widgets maintain consistent look and feel?
Just a few points to consider......and a few reasons i believe android is not a carOS...but don't let that slow you down.
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
Agreed.
http://tripzero.blogspot.com/2009/05...ments-car.html
I always refer to that when someone suggests using windows/android/moblin/appleos/webos/gnome/etc in the car. As long as you are aware of the issues and still want to do it, all the power to you.
Former author of LinuxICE, nghost.
Current author of nobdy.
Bookmarks