cm10 will not run without the egl libs,miiicmueller wrote:I compiled cm10 Jelly Bean 4.1.2 successfully for the rpi.
But i have the same problems than cm9 :
- framebuffer shared between Android SurfaceFlinger and the console (double buffering enabled)
- the framebuffer driver (bcm2708_fb.c) allows only yres_virtual to 1200 (double buffering at maximum 800x600) . I think the VirtualCore is limited to this value, but we haven't any firmware informations.
- EGL libs must be ported from userland sources to libEGL Android... i don't know how.
Has anyone a memory map of the VC ?
We are working on porting the library to egl, we have made alot of progress but implementing gralloc from scratch is a PITAmiiicmueller wrote:Ok...but i made 2 hypothesis
1) LibEgl is only to run java apps using OpenGL ES and Android HMI is separate => That not explain me why famebuffer is shared by console and Android HMI...
2) LibEGL and Android HMI are linked together by SurfaceFlinger. If it is the case then we have source code of OpenGL ES (from broadcom) ==> we are able to modify Android's libEgl to BroadCom libs
Thanks very much for your meaning, ideas, etc
That's an almost impossible question to answer!ingramator wrote:So when will there be a stable release?
I'm in Belgium, I'll first test it with another raspberry here at school, I'll keep it in mind to send it but I'm a little short in time so I don't know if I'll get to that.aaa801 wrote:Are you in england?, if you send me the card i can see whats going on =/Xsaron wrote:Yeah, it's weird. I've tried 4 different SD-cards already..aaa801 wrote:No one in the team has had this issue with burning the sd cards and having them not boot =/
If someone could send us one of these cards we could investigate
I don't think you would get anywhere,lasloHU wrote:Hi,
I thought that was quite a good idea to make a petition for developing Android for Raspberry Pi.
Just as they do Windows Phone users with google apps (http://is.gd/neQg8k).
What do you think ?
It would not be bad to show interest in android on Raspberry Pi
I hope to understand me my english is not the best.
Directly into the Pi. I'll have to try it with a powered usb hub and share the results. I don't have one right now.crashingdutchman wrote:Have you plugged it directly into the Pi or in a powered usb hub? The first option could (will) cause a too high current draw from your Pi.
the driver is prob missing from the kernel we compiled, also i think we disabled wifi in buildhundred wrote:Directly into the Pi. I'll have to try it with a powered usb hub and share the results. I don't have one right now.crashingdutchman wrote:Have you plugged it directly into the Pi or in a powered usb hub? The first option could (will) cause a too high current draw from your Pi.
Sounds like you're getting very close.Warg wrote: Quick status-update, we're pretty sure our libs work now, however we're not getting output to the screen. A user in #cyanogenmod-dev suggested it's a page flipping issue. Currently investigating. If anyone has any idea of a fix, please, drop by IRC or send me a PM containing your suggestion.
Cobblers.Ray_GTI-R wrote:BOINC on ARM
The developers (BOINC?) are currently focusing on getting boinc to run on the android platforms.
BOINC Preliminary Change Log 7.0.42 --> 7.0.43 ... client: processor identification for ARM (from Evandro Menezes and Joachim Fritzsch).
Android on the RPi
by Warg (Sweden) » 12 Feb 2013 18:11
"For anyone else that feels like questioning the time it takes to get this working 100%:
I am merely a man. One man. If some part of this project takes too long, it's because I have other obligations."
So the "Android team" is one person working part time ... this from a foundation that has sold over 500,000 units (maybe a million?).
FWIW I spent many hours spread over weeks trying to get the RPi foundation's big announcement about Android on the RPi to do - well anything, really - on my RPi. Including following the updates & messages github/usenet(?)/irc etc etc.
FWIW2 I only ever got interested in Android because NativeBOINC ran BOINC projects on my non-RPi ARM devices out-of-the-box really, really well (world #2 O/A!).
BOINC via Raspbian on the RPi
I have an RPi out-of-the-box BOINC setup with simple one-click project startups thanks to binaries from Daniel Carrion (one man, a student working part-time supporting RPi very effectively).
Tasks completed for projects:-
Milkyway (1 task. I aborted the 2nd task as each is a 6-day job to test, started a new Milkyway task today - 13 Feb 2013)
Albert (2 tasks)
OProject (2,491+ tasks)
WUprop (174+ tasks)
Other projects are available see:- http://burdeview.blogspot.com.au/p/rasp ... eated.html.
I would have happily contributed to a kick start fund but I now have no interest in RPi Android development.
The foundation should hang it's head in shame at the lack of direct support for Warg (Sweden) et al connected to the Android RPi port. A BIG missed opportunity now that hardware has moved on ... quad-core ARM @ 1.7GHZ almost postage stamp size devices running Android /NativeBOINC etc out-of-the-box. ODROID if it wasn't said before.
Liz / Eben please note.