Slashdot Mirror
Google To Bring Official Android Support To the Raspberry Pi 3 (arstechnica.com)
An anonymous reader shares an Ars Technica report: The Raspberry Pi 3 is not hurting for operating system choices. The tiny ARM computer is supported by several Linux distributions and even has a version of Windows 10 IoT core available. Now, it looks like the Pi is about to get official support for one of the most popular operating systems out there: Android. In Google's Android Open Source Project (AOSP) repository, a new device tree recently popped up for the Raspberry Pi 3. The AOSP device tree contains mostly Nexus devices with the occasional "generic" entry or developer board tossed into the mix. It's rare to see a non-Google device in AOSP, so it seems Google has taken quite a shine to the tiny computer. With officially supported source code, it should be much easier for hackers to get Android up and running on the Pi 3. And once that's done, you should be able to sideload more than 1.5 million apps onto the Pi to make the device do whatever you want.
Dakota.
Ono.
OH NO!
Who wants to run shitty phone games on a Raspberry Pi? Install Windows 10 IoT and you can be playing real games like Halo on a $35 computer!
More choice for what is essentially a "hackers" device. It isn't a bad thing!
Surely if Google support it then you just download then in a sane fashion from the play store. And this should be pretty awesome since the Pi could run YouTube, Netflix, Kodi, pretty much anything that Android supports.
Yay! Long live googledot!
captcha: languish
>> Google To Bring Official Android Support To the Raspberry Pi 3
>> Google Steps Up Pressure on Partners Tardy in Updating Android
OK, Google. Which is it? (Because I'm pretty sure there will be a lot of Pi "makers" who never touch a thing once they get their shoestring operations working.)
Will the battery last very long on my Pi running Android?
Will there be support for any cellular devices so I can talk, text and/or run data any time soon?
Will it work outside when it's 110 in the shade?
Face it, the Pi is not much more than a toy, a cheap learning device used to teach in places where the cost of even a low end computer is too much. Great for teaching and learning, not so great as a basis of any kind of practical commercial hardware design.
Adding Android to the stable of operating systems you can load up on a Pi is more about learning what porting an operating system takes, and less about the applications one might develop, install and/or run on it. So this is a win for the student and hobbyist, but not worth much beyond being a rapid prototype test bed for the commercial world.
BTW... I'm fully aware that the Pi is not generally run on batteries... Not that you can't, only that it's not commonly done that way because it usually depends on a 5V supply, which is hard to get from the modern mass produced batteries of today...
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
There is absolutely no reason any OEM should still be selling new models running kitkat or earlier. in my opinion they shouldn't even still be selling lolipop.
.
You are not alone. This is not normal. None of this is normal.
RPi boots from an SD-Card. Anyone can download and upgrade, without any help from the manufacturer.
If the makers never touch a thing and upgrade to the latest version, that's on the makers not Google. Google just needs to provide the long term support to allow makers to upgrade if they choose.
The 2nd article you mention is for OEMs and carriers that abandon support for a phone about 2 seconds after they launch the phone. Google publishes the updates, but it's up to the OEMs and carriers to integrate those fixes into their product lines.
My flagship Galaxy S4 for T-Mobile came with 4.2.2 JellyBean in mid 2013. 2 years later it had been upgraded all the way to 4.4.4 where it made it ultimately up to 4.4.4 Kitkat by September 2015 where it never has progressed past. Lollipop was available in October 2014 and Marshmallow in October 2015. Yet nothing for my phone. It wasn't that I elected not to upgrade, it was just that there was no official update available.
I'll be curious if they manage to support the media codec framework. Broadcom opened up some of the internals for the VideoCore for handling graphics acceleration but they have held onto the codec support for licensing reasons.
Google To Surveil Raspberry Pi 3 Users Via Android Operating System
Or, alternately:
Google To Add Raspberry Pi 3 To It's Global Botnet
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
Let me know when they have a Pi 3 with 2GB or more. With only 1GB, Android is awful. 1GB was OK until KitKat... now it isn't. 1GB is spacious with ICS, but not with LP...
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Still no 64-bit kernel?
With a Xiaomi 10000 mAh power bank attached to my Pi 2 Model B running Raspbian desktop (but idle, other than a script writing the uptime to a file every minute), I got 13 hours and 46 minutes before the power ran out. I wonder if the Pi port of Android will support the Pi 2 Model B too? It'll be annoying if it doesn't, because the Pi 3 wasn't a massive upgrade over the Pi 2 Model B.
Videos of Natalie Portman are blocked. It only allows you to watch Nathan Fillion.
With a Pi 2, the official 7" touchscreen display, a wifi dongle, and a software defined radio connected, all actively running as an ADSB receiver, I got 8 hours on a single 16800mAh battery pack. That was with some charge left over. Something wrong with your batteries/charger if you got only 5.5 hours on two of those, especially if it was "...while the Raspberry Pi was mostly idle." Without the display and the SDR, running headless with two wifi adapters and the Pi Camera, I got nearly 12 hours before I left work and I still had around 50% on the battery.
What's cool is that you can just swap the SD card to run a different OS, so you can have a wallet of SD cards with different OSes to run.
Wirth's law may be blocking these devices from getting an upgrade to the next major version of Android if the device's RAM size or disk performance does not meet the minimum system requirements of the next major version. I can speak from experience that for some devices, though an update was issued, it never should have been. Android 4.4 "KitKat" on the Nexus 7 (2012) "grouper" tablet is fine; Android 5 "Lollipop" on the same hardware is a jank-fest, with the UI often freezing for five or ten seconds at a time. All reports that I've read imply that the jankiness is caused by ASUS cheaping out on slow NAND flash memory. Clearing the cache helps some but not all users in this situation. It's like the last version of iOS that Apple releases for a given iPhone model: its increased system demands often bog down the UI to the point where some users end up assuming it is an intentional measure to get people to replace otherwise working hardware.
Irrelevant. We want videos of Mae Ling Mak, not newb stuff.
But you like Müsli, with a hint of raspberry on a circular bowl, served to you by an android in a Swiss ski resort?
Nobody cares about making cheap touchscreen displays. You can't manufacture a cheap consumer product out of the raspberry pi because adding a display increases to cost too much.