I have FM radio on my phone, and I find myself using internet radio more than FM radio
until the tablets include fm/dab radio as well.. i don't see the point.. unless you don't WANT radio of course..
i know if you get a 3g tablet you can do podcasts etc, but then you're chewing data, and i wouldn't want that either
I'm running android on my carpc. Not ideal at the moment.
-Can't download apps from the android market place since the android market place is not open source.
-Android really needs a capacitive screen or SAW screen. My lilliput resistive touch panel really isn't convenient to use with it
-Can't connect my car buttons to the UI. Android runs linux but no the standard GNU packages, thus Xorg isn't the default WM.
That said, if you really want a carpc that can run Android x86, try this:
I've been testing out the latest build of Froyo x86 considering it for carPC usage... and it sucks ***. Its network support is terrible, a lot of things happen to force close (the browser for one, frustrating). It's now sporting 3g data card support which works ok. The keyboard sometimes screws up and requires the spacebar to be pushed twice to generate a single space. Lots of the advanced programs that I use under android do not work since they require an ARM cpu, including the app I need for FLAC support which my library is now about 85% of. Angry Birds doesn't work for me. RockPlayer requires ARM. Netflix requires ARM.
I don't see this getting fixed anytime soon. I really doubt app developers will be putting out separate APKs for x86 based android devices.
EDIT: Kevinkga, wtf is that? I see it's a Cisco something...
Last edited by Tidder; 05-30-2011 at 02:44 PM.
The best resurrected frontend I've ever used, period.
It's an x86 Intel Atom based tablet made by Cisco that runs android. The tablet can dock into a phone base, but I reckon we will see other generic docks made for it and I can see ones being made for cars. I think if such a dock could incorporate something along the lines of the TDA7850 then you've pretty much got a dockable carpc/tablet.
The downside is that this tablet is targeted towards the enterprise and it's unlikely within consumer reach (unless cisco change their mind).
Regarding your issues with the froyo build, it really depends on how you built your system and kernel. Hardware-wise if the linux kernel supports it, it should just work on android. What does your lsusb and lspci show?
Last edited by kevinkga; 05-31-2011 at 05:41 AM.
Hi All - First post in 5 years...
I've been looking at Linux based CarPC's since DashPC and have always wanted to do something similar, at least in the Audio and Alarm/GPS tracking department, I always preferred free software and cheap hardware due to the risk of theft so never bothered to spend $2000 on touch screens, power supplies and audio processors.
Over 7 years in 4 cars I have tried
- Laptop on front seat plugged into amps
- EEEpc taken apart, put in dash
- EEEpc with Linux, USB keypad and programmed keys to act like a stereo.
- HTC Android phone mounted on dash
This week I picked up a 7 inch tablet from China for $100 and decided to see what it could do, 800mhz CPU, 256 meg ram and 4gig internal memory, with an SD Card port, USB port and wifi. The first thing I thought is "how good would this be without all the phone and camera crap installed"... Which made me come to this philosophical conclusion...
"How much, do we really need our CarPC's to do? Are we being too greedy in our requirements?"
The reason Android hasn't taken off as a CarPC interface is because everyone is focusing on the phone/networking side of things, personally I don't really care about having 3G capabilities on my CarPC, I dont want to play Angry Chickens or whatever its called, I dont want a GPS - I already own a GPS and also have it on my phone. All I want to do is play music, look at some gauges and have a clock.
With all this is mind, I have been working on a custom ROM for the particular Android tablet I own, removing all the phone, camera and GPS software that I dont need, and also setup the wireless network as a node so I only connect to add/share/remove music from my car system. When all the things I dont need for a car stereo are removed from the tablet, I am expecting the interface to be much fast and smoother, then its just a matter of building a decent looking media player interface and making some minor changes to the behavior of the OS.
Anyway, just my 2c, will post up progress over time if people are interested.
Samsung tab P1000 tablet with Android, wich has all thes application I need:
email, music, navigation, yahoo messenger, internet.
Conectivity: Gsm/3g, wi-fi, bluetooth. (bluetooth cannot be used for transfer audio betwen phone and tablet, but can be used for file transfer, or for connect the tablet with a keybord or mouse)
In the tablet I have a sim card with internet service and Gsm.
The sim in the tablet has no taxe between my phone sim and tablet sim (they are in a group).
I have this scenario:
The tablet is on the bord of my Skoda, conected to audio system.
When I lift in my car, a redirect all call to my tablet (can do this by close the phone - with automatic redirect when is not in the network). From thist moment I can use the tablet like my phone: email, calendar, agenda, are all the same (it's Android ), yahoo mess.
I can do, all can do with my phone, with a bigger screen, and allways conected to battery. I don't need to keep my phone somewhere in my car, and fogget him in the car when I left the car.
All I need to do, is to find a way to fix the tabled on the bord of my Skoda Octavia.
So anyone like my ideea?
I feel that Honeycomb would be best suited for a carputer installation. With honeycomb you have virtual home, menu, etc buttons. Does anyone care to give it a try? It is the first link in downloads: http://code.google.com/p/android-x86/. Not knowing how this performs with a touchscreen is what is keeping me from building a carputer.