For every one that thinks that the raspberry pi is to weak to run, it isn't!!!
I have a lg p350 with a processor of 600mhz and 178 mb of ram and it runs Android jb 4.2.1 smoothly so why should the raspberry pi run it?
Code: Select all
*******@******** ~/development $ uptime && free -m
08:58:49 up 37 min, 1 user, load average: 0.27, 0.28, 0.34
total used free shared buffers cached
Mem: 485 284 201 0 26 131
-/+ buffers/cache: 126 359
Swap: 99 0 99
Official Android 4.0.3 (built by Broadcom): Boots, very fast with hardware acceleration, Lacks AudioFlinger support. NOTE: Not yet released by Broadcom!
There is no specific need for Android on the Raspi that matches the goals of the foundation
If it was in a state where it could be released without a load of extra work, then I guess it would be released, but it's not ready and no-one is working on it, because we have more important things to do. And of course, Android has limited use in a teaching situation (in my opinion, almost no use whatsoever)lasloHU wrote:You're right, http://androidpi.wikia.com/wiki/Android_Pi_WikiOfficial Android 4.0.3 (built by Broadcom): Boots, very fast with hardware acceleration, Lacks AudioFlinger support. NOTE: Not yet released by Broadcom!
But I do not, why they do not want to release.
Still the same excuses.There is no specific need for Android on the Raspi that matches the goals of the foundation![]()
(I know that the Foundation and Broadcom is not the same thing)
That phone will be using the hardware acceleration of whatever SoC it uses, at the moment there is no HW accelerated release of Android for Raspberry Pi, so Android runs very slowly.Ebert wrote:For every one that thinks that the raspberry pi is to weak to run, it isn't!!!
I have a lg p350 with a processor of 600mhz and 178 mb of ram and it runs Android jb 4.2.1 smoothly so why should the raspberry pi run it?
So in other words hardware accelerated Android on the Pi is never going to happen??If it was in a state where it could be released without a load of extra work, then I guess it would be released, but it's not ready and no-one is working on it, because we have more important things to do. And of course, Android has limited use in a teaching situation (in my opinion, almost no use whatsoever)
I am at a loss to understand how you can conclude that from my post.redhawk wrote:So in other words hardware accelerated Android on the Pi is never going to happen??If it was in a state where it could be released without a load of extra work, then I guess it would be released, but it's not ready and no-one is working on it, because we have more important things to do. And of course, Android has limited use in a teaching situation (in my opinion, almost no use whatsoever)
Richard S.


http://www.android-x86.org/tonyhughes wrote:My Core2Duo laptop is way more powerful than your LG, but I can't natively run Android on it, because its just not designed for it (of course you can emulate Android hardware in x86/x64 OSes).
You still have your own choice of buying a better smartphone if you want to. So what you do with the commercial talk of those big companies, is still your own decision.GreiverBlade wrote:i dont get all people who say 4.0+ cant work on Rpi ... my tab has a single core (ok 1ghz) and a single core Arm Mali 400mp and ... 512mb ram (btw i dont get why people talk about the 256mb rev.A since the rev.B 512mb was out before) and it runs 4.0.4 like a charm + 4.1.2 test success. i reckon Mali 400mp is more supported but Videocore4 isnt what we can call a weak gpu ...
maybe its more the cpu who is a leash... (the tab has a cortex A8)
the all part of " your device doesnt meet the requirement" for jelly Bean is a enormous joke since i've seen many smartphone with less than what's demanded running 4.1.2 smooth I.T.S juste a commercial argument to force you to buy "the last one in date"
so single core 512mb ram can run it... basically just need Broadcom driver and a bit of tweaking and no false excuse as "no it cant run it" or "i think the cpu/gpu is too weak" until its proved that a fully optimised port cant run stable because of those "weakness"
oh well i dont care about android developement since i use my tab or a UMI X1 allready but i hate false argument (since no full port has beeen out then its not "sure" it doesnt work
juste be patient and wait on dev (or do like the other one said ... propose fundraising to get it ... even if its kinda off for a open source os (ok Android isnt quite open source but still) every work is worth the money)