Raspberry Pi vs. Cheap Android Dongle: Embarrassment of (Cheap) Riches
New submitter Copper Nikus writes "The price of Android Mini PCs have recently dropped to the point they are starting to make the Raspberry Pi look overpriced. This article compares the Raspberry Pi model B against the similarly priced MK802 II single core Android mini PC. IMO it can be argued that the mini PC wins that fight. It's worth noting that several new quad-core Chinese ARM SoCs have been recently released to the world, and it can be expected to see Android mini PCs start using them in the very near future. This should translate into even lower prices for the now 'obsolete' generations of single and dual core Andoid mini PCs out there." The target markets and base OS vary, but there's enough overlap for this comparison to make some sense — both have ARM chips, both can (to varying degrees) run either Android or a more conventional Linux distro, and both can fit in a small pocket.
who cares... Everything that needed a computer now has one, this is just toys for toys' sake.
you are missing a critical point. break out the IO on the USB dongle. Make it turn lights on
and off. sure, you can slave it to other USB devices, but there is a nice IO header on the
PI for those who wish to play with it. it's comparing apples to oranges.
The PI was made with hardware tinkering in mind, the USB dongles - not so much.
dreaded scurrilous bit-twiddler from Oklahoma
RPI served a purpose one way or the other. The faster these things get while staying at a similar price point just means there will be much cooler garage made gadgets and hacks to play with. Until apple buys all the patents up and sues everyone that is.
Android is nice if I want to play angry birds, use facebook or twitter, or watch a movie on netflix. The "mini pc" is really just an entertainment device. It's like telling me that I can throw out my desktop computer and replace it with a Roku or a smart tv.
I'm more interested in learning things and keep my it skills fresh, so I would rather build a tiny little server with a Raspberry Pi (or stick a nice distro on it to use when I travel) than play with whatever the android device of the week is.
So, when can we cluster a bunch of these nodes together to form a tiny cloud platform? Possible yet?
Life is not for the lazy.
I would rather compare to RK3066-based miniPCs. It's a dual-core platform with very good performance and has a number of mini-PCs based on it (MK808, UG808, iMITO etc). Android is a joy to use on this platform, and linux is under development.
The price is 50-60$ including shipping, which is not a lot more than 35$+shipping
I admit I'm biased but I prefer the Pi over the Android dongles.
It just seems like there's more of a fun factor in making a Pi-based system than just plugging in a dongle-type system.
At least with the Pi I get to play with legos
My Pi system based on the 28 port Manhatten usb adapter
http://imageshack.us/g/1/9907766/
Sig Follows: "Suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself." -- Mark Twain
Seriously, all I want is mini computers smaller than a hearing aid battery that can run XBMC with enough power to watch any format/compression from YouTube to BluRay. Is that too much to ask? Of course it's coming, and these systems are a great step towards that (yes I know XMBC runs on rPi), but for now I'm sticking to my hand built full size PC system running XBMC. - HEX
Horror & SciFi Erotic Nudes
We just deployed 3x Pi in a warehouse. I have to say, I'm really impressed with them. They are small, robust, and best of all, fanless (our last Mini-Itx died from dust-inhalation). System upgrades are easy - just swap over the SD card.
Just a couple of gotchas:
* Overclocking isn't just about heat (I added a heatsink and the CPU runs cool). The jump from 950MHz to 1Ghz is a very steep one (it suddenly bumps up all the other system clocks by a large amount) and this can make it unstable, corrupting the filesystem. 950 seems to be reliable.
* Power for USB (especially WiFi) is dodgy. Hotplugging a dongle will make the Pi reboot from brownout. It seems to be worse because the "5V" supplies aren't actually 5V. I tested several; surprisingly, the branded Nokia/HTC ones put out about 4.7V, whereas the unbranded ones are nearer 4.9. I suspect that in a USB supply that is really designed to charge a 3.7V LiPo cell, the more energy efficient ones may aim to come in slightly under 5V to reduce waste. Even with the newest model B rev 2, there is still one polyfuse on the input: I shorted this to gain another 10mV.
Anyway, I really want a Model C, perhaps with a 1.5GHz CPU, 2GB of RAM, 4 USB ports, embedded Wifi/bluetooth, and a better power supply.
You're right. The words "cheap" and "Chinese" are sort of red flags that maybe you won't find such nice USB headers and will have power distribution problems or noise on the audio ports or heat issues or bad liquid capacitors or any variety of cheap hardware problems.
While you're technically correct today - on the other hand, a $50 dual core computer on a stick isn't a bad value proposition. Would you really want to put a $200 usb-sized computer through the wash by accident? Or take it travelling and have it filled with sand?
Also, I'm old enough to remember when "made in japan" was synonymous with the same sorts of quality issues that "made in china" represents today. Now, half my tech items are over-priced and underpowered sony products.
- Nec Impar Pluribus, or so I'm told.
If you need IO breakout get a $49 Cubieboard, http://cubieboard.org/
Same ARM Cortex CPU/RAM/flash/HDMI as the Android sticks plus a 96 pin header including I2C, SPI, SATA, RGB/LVDS, CSI/TS, FM-IN, ADC, CVBS, VGA, SPDIF-OUT, R-TP..
...but I'm willing to pay more for an ARM-based board made right here in the good ole' US of A (BeagleBone).
No virus-laden Chinese crap for me.
If by "old fashioned" you mean "racist", then yes - you're old fashioned.
I was just thinking that. How do we know they haven't modified the ARM design to include stuff like backdoor decryption or tracking capabilities?
You're right. The words "cheap" and "Chinese" are sort of red flags that maybe you won't find such nice USB headers and will have power distribution problems or noise on the audio ports or heat issues or bad liquid capacitors or any variety of cheap hardware problems.
This topic is about good value Android/GNU products not Apple products.
Connectivity.
The GPIO pins and everything else. It was never about a super low cost computing platform, its simply shown the manufacturers that such an item would sell like hotcakes, if produced for the low enough price.
- http://www.milkme.co.uk
Poe's law.
AC does not understand the difference between racism and xenophobia....
His adjective was describing a "thing", not people.
He said "Chinese crap". Is it racist to say french wine is better? how 'bout their cheese? Are spices better from the middle east? Am I racist because I prefer Greek cuisine over others? German Cars are better, right?
...all these crowd sourced projects. What you make them look like when you do this is a product hawked by billie mays hays...in fact its worse. Its vaporware. If they don't have a R&D budget and products on hand, don't refer to them as a 'solution'.
I signed up to buy a Pi when I first heard about them. After several releases, I got an email that said they were in stock. I gave my CC# and placed an order. Got an email saying they were back ordered and I would be notified when sent. Never got sent. Got lots and lots of their advertising emails. Shit loads. Then another 'available' email. Tried to order again. Nada. Called customer service. The guy reminded me of Ocean Marketing. Like I was pestering them to take my money. WTF?
I hope maybe I can finally buy one of the other available options.
B-(
A friend will come and bail you out of jail, a true friend will be sitting next to you saying, "damn that was fun!"
$49 Cubieboard Allwinner A10 + 512M/1GB DDR3 , 4Gb Nand Flash, 10/100M Ethernet, HDMI, 2 USB Host, 1 micro SD slot, 1 SATA, 1 ir, 96 GPIO pins ncluding I2C, SPI, RGB/LVDS, CSI/TS, FM-IN, ADC, CVBS, VGA, SPDIF-OUT, R-TP
http://cubieboard.org/
£40 Allwinner A10 + 1GB RAM, 4Gb NAND, Wifi: 802.11 b/g/n, 3.5mm Earphone Jack, 1x Mini Usb, 1x Hdmi Out, Micro Sd slot,
http://gooseberry.atspace.co.uk/
$65.00 Allwinner A10 1GB RAM, 4GB NAND, 3.5mm microphone jack, 3.3v TTL 4-pin header, 2 x USB A 2.0, 10/100 Ethernet, Realtek 802.11n WiFi, HDMI up to 1080p, 3.5mm composite AV, 3.5mm component Y/Pb/Pr, SDHC card slot
https://www.miniand.com/products/Hackberry%20A10%20Developer%20Board
$89 Freescale i.MX6 Duallite, 1 GB DDR3, Audio, Optical S/PDI, HDMI, Camera interface, SD Slot, Serial, Expanison header GPIO, USB, USB OTG, GB-LAN, WiFi 802.11n, Bluetooth
http://wandboard.org/
$89 Exynos4412 1.7Ghz ARM Cortex-A9 Quad Core, 10/100Mbps Ethernet, 2 x High speed USB2.0 Host,HDMI, SD Slot, Headphone jack
http://www.hardkernel.com/renewal_2011/products/prdt_info.php
Quidquid latine dictum sit altum viditur
Come on, you started thinking, keep going... imagine they have backdoor decryption on their chip, what are they going to do with it? Send their evil Chinese spies to your house and steal the strategically valuable data that you just happen to have stored on your tiny usb-computer?
I know, shades of the past and all that. I haven't seen a Beowulf comment for what seems like years.
But in this case it could actually be interesting! :)
So, take one big-a$$ USB hub, plug a whole bunch of the Android dongles into it. Use a Raspberry Pi as the USB router and another one or two Pi as I/O and scheduling processors. Run Beowulf.
Let me just say IANA HW guy... :P I may have some details missing or wrong... But if I get thing correctly, you can have 127 dongles on one controller. I don't know (didn't do any research) about whether the cited dongles can be used as controllers (hence using the Pi). You can have, on one small board, one Pi and 127 dongles (handle power to the dongles directly rather than through the controller's USB connection). Use ethernet between boards - this also helps with the problem of USB bandwidth. Stack boards as 'high' as might be interesting, useful and feasible.
Who knows? With enough of these processing boards combined, one might achieve the same performance as a high-end Intel chip! :P
It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
Well that whole facebook privacy stuff is right out the window if they are just sending it straight home anyway now isn't it?
...all these crowd sourced projects. What you make them look like when you do this is a product hawked by billie mays hays...in fact its worse. Its vaporware. If they don't have a R&D budget and products on hand, don't refer to them as a 'solution'.
I'ts moving off topic to discuss crowd funding, but lets be honest. Small hardware projects fit crowd funding like a glove, The cost accounting (patent problems aside) are built into the strategy, and you instantly get real feedback on whether there is a market for your project, better than any expensive research could do, with [potential] customers getting involved early with the product to help shape it. Its better than banks/venture capitalists who take cut, of your borrowing...and potential future business.
Directly related to your comment. It is perfectly acceptable to propose *any* crowd sourced product as a potential 'solution', as long as you are aware of the risks inherent in this.
Okay, that changes things. Not only has the device a secret backdoor decryption thingy (whatever that might be), the CPU will also send (easily detected) packets over your network, but nobody has detected these packets yet because of... reasons. And the Chinese are *so* interested in you that they would risk getting caught performing something as bizarre as this scheme of yours just to get a glimpse at your facebook friends.
This conspiracy theory of yours sounds rather far-fetched.
There is no evidence that the Chinese have done this... although it is likely. There is, however, concrete proof that the US government is definitely doing it. In the Windows environment and Cisco equipment at least... probably a lot of others. All Chinas government can do to you is spy... the US government can arrest you, put you in jail, send you to secret prisons in other countries to be tortured or even put you to death.
I'll take my Chinese backdoor over your US government backdoor any day.
Androids lack of windowed multitasking really sucks. You can b e more productive on a Dos box running Desqview. Android's requirements are also becoming ridiculous.
At least from the Amazon reviews: http://www.amazon.com/Rikomagic-Generation-Android-Google-Player/dp/B0091UHMHO
* Not happy at all with the product and returning it back to HongKong is not worth the time and effort.
* The only form of support you cant turn to is the forum community, trust me they are frustrated.
* The only way to turn it on again is by unplugging the usb power cord and connect it again, or turn off/on the tv.
*Had to return it because it stopped working after two attempts. I think this is a nice concept but the hardware needs to mature a bit.
Join the Slashcott! Feb 10 thru Feb 17!
raspberry pi isnt a cheap computer. it never was supposed to be, that was the goal of OLPC. Raspberry Pi is a development platform. From the ground up people can hack it at any level, get copious documentation at almost any level, versus the arguably cool, but completely closed allwinner based systems.
If you're looking for something to connect to a TV, the MK802 or MK808 is clearly the winner. If you're looking to make a toy, or run some lights, than Pi is the choice. I have the UG802 and it's very small/powerful for all that it does, but XBMC doesn't support HW decoding yet. Raspberry Pi looks cool, but the specs are lousy compared to the alternative. Another obvious choice that no-one mentioned are used Android Phones. I just upgraded my phone and have a Galaxy S phone no longer being used. Still looking for a good project to make use of it.
-- By all means let's be open-minded, but not so open-minded that our brains drop out.
There are a lot of reasons to pick a slower Raspberry Pi rather than one of the dozens of other cheap ARM boards and systems that have become available.
The primary one is the community that has built up around the device. This means the device is well supported.
Also the lack of case means you can access the headers - and there are headers to interface to.
And you can then add your own case, rather than put up with cheap-ass plastic.
I am sure that there will be a Mk2 RasPi within a year that will fix the CPU performance issue - it's a natural next step.
We also have to consider that the RasPi is now entirely assembled in the UK, and it's worth supporting local industry (or using it as an example to encourage local assembly of electronics in your own country).
Wanting to buy locally is racist? Crud. Here I've been buying produce and food from local growers and farmers. The Amish around here have a good reputation when it comes to quality food. PRC food products, not so much. I wasn't aware I was being racist, considering quality was my sole concern and not genetic superiority or inferiority. I'm just not fond of melamine in my milk. On the other hand, I'd don't buy electronics from the Amish and do buy Made in PRC electronics.
I like buying locally when I can because I've had better success at contacting and communicating with the the folks that made the product. One theoretically could prefer to buy American, because there is less statistical chance of an ethnically Chinese person would be making or assembling the product. That would be oddly specifically racist, but indeed racist.
USB hub with ~20 ports, 20 MK802 III's running Ubuntu and your preference of rendering software, now I know it isn't going to be powerful but at the price point, it's scalable, cheap, low power consumption.
Has anyone tried this? What do you think?
"If any question why we died, Tell them because our fathers lied."
Call me old-fashioned, but I'm willing to pay more for a tube-based board made right here in the good ole' united Kingdom (SSEM)
No silicon-laden ARM crap for me.
The thing you call "vaporware" has been shipping for weeks: http://www.indiegogo.com/cubieboard?c=comments
But don't let the facts get in the way of your rants.
I once got an Android phone. I didn't do my research and I expected that I would have a normal Linux with root access, some decent package manager and that I could access most everything from the command line, and of course a graphical interface that has all the things on it. I imagined, that I could dial with a script, read sensors, or do IP over USB and other neat tricks easily just like I do with a linux box. I was so freaking wrong.
Now we are comparing a USB stick that has this limited crap on it to a full blown Debian server. I go with the Debian for the servers and back to my iPhone that at least has a neat developer tool (yeah, need to pay $100 a year to develop my own utils on the phone .... big deal, Xcode saves me enough time to justify that $100)....
I by the way run a little java app for automation on the PI. They have arduinos hanging on them doing most of the actual switching/sensing/human IO. It is a perfect architecture because I am allowed to use all the Unix/Linux services that OS has to offer without programming too much micro controllers but taking advantage of both words. I figured that an Arduino with ethernet shield is $70 while the PI is $35. An arduino + pi is $65. A little more juice is used but less coding of basic stuff, more time for logic and you still have a snappy micro controller one i2c or serial pin away.
waited 14? weeks then cancelled the order, RS told me it was already in transit and had been for three weeks. it arrived the very next day from a us supplier
That's what I need from the Pi but it does not do it. I need Skype and I am glad to see other players on the market that will run Skype.
What ever are you babbling on about? Android is a general purpose OS built on a Linux foundation that can run any code you want to run on it
This is one of the few cases where RMS's rambling about GNU and how distros should be called "GNU/Linux" actually makes sense.
LINUX is only a KERNEL.
As in the stuff that directly talks to your hardware and handles low-level stuff.
Above this kernel, you need a "userland" actual regular programs which are called.
And Android DOES NOT use the same GNU userland as most distributions.
Whereas regular distribution are "GNU/Linux" (i.e.: runs the Linux kernel and a bunch of userland program, lots from the GNU project [for low-level stuff like C library, shell, etc.], but quite a lots of other stuff [KDE, Firefox, LibreOffice.org]) and are fully POSIX compatible and can run almost any general purpose UNIX software out of the box (as long it was compiled for it), Android is Linux kernel + a very special userland made by Google (among which the most well known part is the Dalvik java-like environment. Even the C library is Google's own Bionic instead of the usual glibc, ulibc and other forks).
Out-of-the box, Android doesn't run most Unix software because several parts are missing.
(This is different from other mobile OS: Maemo/Meego/whatever-the-nom-du-jour-is, OpenMoko's SHR, Palm/HP WebOS, etc. all run a normal GNU/Linux stack, although in WebOS case, it uses a non standard gui instead of X.
Even router provide a unix like environment, only using more light-wieght embed-friendly components like Busyboy and ulibc or eglibc and without a graphic interface at all)
Again, the usual user-land, the "GNU/" part of "GNU/Linux" is missing.
(I run Debian in a chroot environment on my Android phone as just one example).
That's what your compensating by running a Debian chroot. You provide the missing userland.
You share the same kernel (Linux), but run a different set of userland programs on it. You provied a C library (I think Debian moved to eglibc ?) a shell, and hundreds of other part that make the userland environment. You provide back the "GNU/" part of "GNU/Linux".
And now, thanks to all the pieces provided by your chroot, you can run any Unix code.
Now, indeed, this is possible because Android uses the Linux kernel as a foundation, and its opensource make it possible to port a Debian userland to Android and run it along the normal system. So in a way you're right.
But I insist, Android is unlike any other GNU/Linux distribution around. (And until recently, it needed some special kernel functions that weren't in stock kernels).
This is unlike other Linux based mobile device, which already are based mostly on these pieces. You don't need to provide them. You can already run most of what you want on Maemo/Meego, OpenMoko, webOS based device (except for the part of webOS lacking X out of the box).
Out of the box, an Android machine is designed to run the default apps packaged with it and to fetch special android-apps from a special app market.
Now, thank to the general openness of the platform, it is possible to repurpose it, but out of the box, this is not your regular Unix-like OS. You need to install a chroot, or at least a lot of userland components.
And that's what the parent was referring to:
- Android stick : runs android, designed to run a few android apps (but you can do more if you want).
- RPi : runs a GNU/Linux disto, designed to pretty much do anything you want out of the box.
but that in no way makes the Android device limited to only certain things.
Android makes the device limited to run only Android apps out-of-the-box, unless you go out of the way and install the missing userland bit to turn it into a full Unix-like box.
But thanks to the open nature of the Linux kernel, this is actually possible. (It's not a locked down device that needs to be hacked)
Android and the classic Unix-like userland (of debian) are completely orthogonal one to another.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
The raspberry pi is now made in the UK. Only the first batch was made in China.
I have
- a TPLINK 703N with openwrt (~17 Euro)
- a Rpi (model B, 256 MB RAM) (~35 Euro)
- a MK802 II (~30 Euro)
i Hvae to say I use them all, for different purposes
. 703N: less than 100 mA, perfect for always on torrent macine
. mk02: very nice as a meda device, attached to the tv. having android is better for this
. Rpi: all kinds of tests using the gpio
I Hardly think one serves all the purposes
It is the primary goal of the RaspberryPi.
The idea behind a tiny and cheap computer for kids....
http://www.raspberrypi.org/about
For that price you can go Korean with a 1.7 ghz Quad core from Hardkernel.
His association of "Chinese" with "viruses" was rather narrow-minded and not empirically supported.
Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
Took about a month to ship. They had a protype ready when they asked for funding so there was no need for R&D at that point. I also have a Raspberry Pi. I'm pretty happy with both of them, they each have their niche. Takes a bit of hacking/tweaking to get them working the way you like but that's why I bought them. I don't know how products like these would exist without crowd funding so I am willing to do the research and take a risk when I find one that appeals to me.
Because to make use of it, they would have to transmit the compromised info from your house to China. Your secret MegaWatt radio station will chave incredible battery drain, unless they also somehow shipped the unit with a multi-megawatt-hour battery included on the SoC. And if they can do that then they deserve to learn your homemade+proprietary kegorator's lagering temperature.
But that aside (maybe your device will be allowed to talk on internet to 'em) you don't know. That makes it slightly safer than US manufactured devices where they're more-than-average likely to spy on you, and by parties who are more interested in you.
A post like yours would be greatly enhanced by a link or two.
Hmm.... I chose an Android device for a mobile phone because of its potential in letting me learn things and improve my IT skills, beside other reasons. And I think it's quite amazing what you can do on Android if you only know some Java. I'd imagine there won't be much you couldn't do with that Cheap Android Dongle. Although, of course, you'd do it a different way than you might do it with a RPI running Linux.
You can boot a mildly old version of Ubuntu off a microSD card on many of these cheap android dongles, but because Ubuntu happens to be so demanding it operates fairly slow if the device is clocked lower than 1.2gHz, But portable/pocket able Ubuntu is amazing in my mind, also it would be very easy to run Arch Linux (what I run at home) on many of these devices, and it would most definitely operate very smoothly.
This isn't true. The Raspberry Pi is currently being manufactured Sony's UK factory in Pencoed, Wales AND in China.
It appears that the number of Raspberry Pi's shipped faulty appears to have significantly increased in the last month or so with one report on the forums from someone who claims that they recently received three faulty Pi's out of ten and another from a person who claims both of theirs are faulty. These reports have been described by Raspberry Pi Foundation representative who posts on their forums as jamesh as "statistically insignificant". This is the same person who incorrectly claimed in August that the Raspberry Pi was still in beta.
There have also been recent reports of poor packaging with the damaged PCB unsecured and rattling around inside, solder bridges between header pins causing constant rebooting as well as multiple instances where PCB holes have been inconsistently filled with solder. See here: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=22473 and http://www.raspberrypi.org/phpBB3/viewtopic.php?f=23&t=24571
How is the Broadcom BCM2835 SoC that the Raspberry Pi uses more open than the Allwinner A1x SoCs?
I've taken delivery of a CubieBoard and it's a kick ass piece of hardware. They delivered the product AHEAD of schedule, unlike the foundation's endless douche-baggery. I had mine in my hot little hands for several weeks and am already running Debian off a BerryBoot bootloader. You may think crowd-source is a scam, but some people see niche products as a prospect worth the risk of investing in. If you're too cynical to appreciate that, it probably just reflects on your own lack of integrity resulting in an inability to trust others.
Caveat Emptor, but if you can't afford to roll the dice with small sums of money it's probably too boutique for your sensibilities. FIY, this practice has long precedence in group-buys on message boards. Small groups of people frequently do not represent a sufficient market for a principle investigator to risk staking an initial investment in R&D. Pre-Orders are flaky. Crowd-sourcing fills this space nicely and allows products that otherwise would have died in the cradle to see the light of day.
His association of "Chinese" with "viruses" was rather narrow-minded and not empirically supported.
Depends on what kind of viruses. Influenza viruses seem to break out in the far east in general and China in particular far more than other places.
This is probably linked to population density, urban fowlkeeping, as well as unhygienic traditional practices (like double-dipping from shared dishes and using the same knives and cutting boards for poultry and vegetables).
For computer viruses, well, there aren't a lot of them anymore. Too few low-level programmers in the new generations, I guess.
But unlike trojans, computer viruses do tend to spread more where people are likely to use pirated copies of operating systems which they may not easily get security updates for. China, Brazil and India tend to top the statistics for viruses, while the US, Netherlands and Russia tops it for trojans.
So yes, the GP does have a point. That doesn't mean he's not a ***ist, but it also doesn't mean he is.
My brand new revision 2 board, from Newark - is made in China.
Maybe only boards sold in the UK are made there or some such..?
Sent from my PDP-11
The RaspberryPi made an open source IDE for ARM development that greatly reduced the barriers to entry for developing embedded code using fast 32 bit processors, then paid themselves for the effort by releasing and selling a development board that was both plug and play compatible with the IDE and idiot-proof enough to endure basic torture tests such as 5V+ inputs on the ADC and Digital IO, reversed polarity on the power supply, and shunting power outputs to ground?
Oh wait, no they didn't do any of that. They made a compact & low cost ARM SBC which trumpeted an RCA video output + HDMI support as its main selling point. They claimed the ability to plug their PCB keychain in to their parents TV would turn an entire generation of nose-picking children in to brilliant computer scientists and electrical engineers through the sheer power of curiosity.
Trouble is, everybody looked around and realized that they had taken the last of their analog displays which accepted RCA inputs to the dump years ago. Then they stuck a microSD card in the slot and booted up Debian/Ubuntu/Sugar and realized that Linux is hard, and doesn't have any cool games like Call Of Duty Modern Warfare.
The RaspberryPi foundation skipped the whole part about making ARM/Linux development accessible to children. They didn't write a sick new IDE, and they hoped that the OLPC foundation would pick up their slack with Sugar or something organic involving hackers would happen. Here's the thing: "not your personal army".
Arduino sold like hotcakes because it was the board that was proven to work with the least amount of bullshit with an intuitive IDE with well commented example code included. They got away with charging $40 for an $6 MCU because nobody wants to put together a Digikey order from a BoM and solder their own programmer together from components. Nobody wants MicroChip's proprietary JTAG bullshit or Code Composer Studio cripleware.
The Raspberry Pi foundation thought they were the next Arduino. All they managed to build was a BASIC Stamp with a faster clock-rate. They are to ARM SoC dev boards what the OLPC was to Netbooks. The Dreamcast was to PS2.
They blew their load on the wrong SoC and ignored the IDE. They're already irrelevant.
Recent revisions of the RasPi board have improved the power problems substantially. Unfortunately there are some 300 thousand boards of earlier revisions out there that won't go away, and eBay will keep recirculating them. Buyer beware.
Power problems aren't the only kind on the RasPi though. Probably the biggest problem is the broken USB handling. The USB controller on that particular Broadcom SoC device has severe limitations and makes invalid assumptions about the Linux kernel, and that cannot be fixed because it's hardwired in the device silicon. As a result, even the latest board revisions have major USB problems that make the board unusable for certain applications.
With these small devices becoming ubiquitous, I got to thinking that one of them could eventually replace the bios on a typical mother board.
Does anyone know what processor is used on the motherboard to start the x86 one from Intel or AMD? Is it too complicated to make a mother board that accepts one of the cheaper devices? We could do our own UEFI and avoid the headaches that bios writers are facing.
Leslie Satenstein Montreal Quebec Canada
Because no fucking shit Android/Linux and GNU/Linux have different user spaces. They're different OSes that share a common kernel.
That's what I've said, too.
My point is that the technical difference is due to different license requirements from Google. The license restrictions w/GNU userland is very much why so many parts of Android were rewritten and continue to be fully re-implemented under an Apache license, with every iteration of Android requiring less and less GPL licensed userspace.
Yes and no.
Your comment is correct regarding things like the C library. Currently Android uses google's own Bionic. Previously it had used components coming from the GNU ecosystem. Among the reason why google developed it, the license is indeed one of them: Bionic come from the BSD userland and is BSD licensed, thus giving more freedom to 3rd party to hack it without needing to publish their modifications. (But thus restricting the freedom to hack of the end users themselves). On the other hand, the predecessor inside android, glibc had several short comings too. (eglibc, which tries to adress several of these shortcomings, notably by being easier to port on embed architecture, and being easier to build a lightweight version by disabling features, only started to gain acceptance later).
But for the rest, that isn't exactly the case.
Android started being developed almost 10 years ago (2003).
As a reference, iOS got released officially in 2007. And even if it was the same usual BSD-derivative architecture under the hood (with only a different user interface and application layer slapped on it), the user-facing elements were designed with non-multi-tasking in mind.
As another reference, in the Palm/Handspring world, from 2002 until 2005, Treo were running PalmOS (a OS that I personally appreciate a lot, having own palm IIIc and T3) which is not even multi-tasking (Palm OS 5 did introduce some very limited forms of multi-tasking). Windows Mobile (as shitty as it is, at least is truely multitasking) was only introduced in 2006.
Back then, smartphones weren't that much popular yet. Most of the phone were simply feature phones. Most of the phones didn't have that much processing power anyway.
Putting a whole unix platform on a phone was considered insane: its a huge overkill of resource.
If you're doing a firmware for a phone, most likely you're making a big monolithic app. You're not trying to cram a whole workstation OS inside a phone (Nokia's Maemo/Meego got such a huge popularity among geeks when it was released in 2005 exactly because of that: Unlike everyone else back then, Nokia successfully managed to cram a whole Linux distribution with the whole stack into a pocket device. And this device still wasn't mainstream/typical even when it was released).
If a phone happened to "run Linux", it would most likely be only the kernel (to leverage its hackability and to use the capabilities of the kernel itself: resource management, filesystem access, etc.) and over it, instead of a whole linux workstation stack, you just found a big monolith. (Very often Java was popular in this bundle). Motorola's RAZR2 is a nice example of that. It uses a Linux kernel. It was released later (2007) so it contains much more pieces of actual Linux (they could afford more) but the biggest part is still a blob.
So back in 2003, when developer started working on Android, they did what everyone found logical in this field:
- They took the Linux kernel because its nice, customisable and contains lots of well tested parts (ressource management, file system, etc.)
- They made a big blob to run on it.
- Java being popular a lot, they created the java-like dalvik.
They didn't as much replace one by one the various part of the usual linux userland with inhouse stuff because of the license, as much as they simply refused to start using them in the first place, because back in 2003 cramming an actual linux stack inside a feature phon
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
I disagree with your opinions, like that Android isnt "Unix-like". You can make kiosk or appliance style *nix distros, and they are in fact common: OpenFiler, pfSense, a LOT of NAS boxes out there, etc. Some of them it is easy to get to the "unix" part of them (pfsense, etc); others it is very difficult (many NAS boxes). That doesnt make them "fake NASes", any more than a Windows box set to hide explorer and launch a locked down firefox is "fake Windows".
If we take your example of "fake windows":
- most Linux based embed systems with a Unix-like userland, would be the equivalent of taking Windows "XPe" keeping it almost as-is, disabling only the shell, and using firefox as a shell instead. Or taking a Windows Server. and installing it in "headless" mode, not running any graphical interface, but running in command-line mode.
It doesn't visually look at all like a regular Windows, but under the hood most of the pieces are here. It still uses Aero and/or DirectX for graphics and sound, CMD is there if you need it, etc.
99% of the files are the same, even if visually there's a lot of difference.
- Android, and the firmware of a few NASes and Media Players, would be the equivalent of only using a small subset of the ".SYS" files of Windows (the various peace of the kernel), only those for accessing hardware, filesystems, task switching, etc. Absolutely everything else is replaced by a huge custom .EXE (and its attached .DLLs) no trace of anything from the original Windows beyond the kernel (these NASes and media player usually take over from the INIT process it self and provide a huge custom monolithic stuff from this point onward. To keep the metaphor, this .EXE+few .DLL is entirely written in .NET because C# is popular (Android use massively Java because its popular). But instead of compiled to bytecode running on the classical .NET DLR virtual machine it runs uses Perl6's ParrotVM :-P (Android doesn't use the JVM, it use its own Dalvik).
Only a couple of .SYS files inside "system32" are shared is a regular Windows. Most of the rest is taken care of in this big weird .NET .EXE. It doesn't even have support for Win32 api.
Android was designed to run on a phone, and as such it has certain design constraints and goals.
I agree. But back in 2003 when the development started, the main constraints for anybody in this field was: there's no way to cram a full Unix environment in a mere phone, its a crazy idae and an awful waste of resource, no current phone hardware could sustain this. Let's instead implement everything we need in a light-weight userland that we're writing from scratch. (And lets use something similar to Java for it, because it's popular and enterprisy)
One of the goals is not to have a terminal window directly accessible to 99% of its userbase;
Not only is the terminal window missing (because as you say 99% of the users don't give a shit about it). But absolutely everything under the hood is missing.
not of some anti-FOSS, anti-*nix, or anti-GNU philosophy from Google.
Unlike other people rambling in this thread, I never accused Google of being anti-FOSS.
I just responded to the discussion: the parent was astonished that Android was considered limited by some. His argument being: you can run anything you want and this is all thank to Android "being Linux".
My counter argument are: unlike any other regular Linux distribution, Android doesn't share much in common beyond the kernel. What is usually done by the regular Unix-like stack in any random other distro, is handled by parts in the the Java-like userland.
You can run anything you want, but for most stuff you'll need to put back that regular Linux stack for this to function.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
A question like yours could be easily answered by a visit to Google.
How about strait from Ciscos documentation?
http://www.cisco.com/en/US/docs/ios/12_2sb/feature/guide/ht_ssi.html
Microsoft Denys they put a backdoor into Windows, but the NSA worked directly with them on development of every OS since XP:
http://www.computerworld.com/s/article/9141105/NSA_helped_with_Windows_7_development
The NSA doesn't generally help private companies with their products, and Microsoft doesn't generally take advice from their customers on their design. I doubt that whatever the NSA was really doing to help with the product was anything we'd consider good.