ICS just dropped to AOSP - Acer Iconia A500

Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f

Just read this on AndroidPolice. Very excited!!!

Game.....on!
Sent from my PG86100 using XDA App

Developers make some rom's!!!!!! (Please)

this thread should make its way over to the development section. Thanks for the find op
Update: Already there

I'm actually curious about how long it will take for someone to make an A500 ICS ROM based on this. There is bound to be someone to do it, but who gets the #1 spot?

Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1

They're not necessarily requirements, but more or less just recommendations. A more average computer could still compile ICS, but it will just take a lot longer. And I'm betting Thor will be the first to cook us a ROM. Hopefully soon
Sent from my HTC Glacier using xda premium

FloatingFatMan said:
Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1
Click to expand...
Click to collapse
Those are only recommendations for developer workstations. It is certainly possible to compile it even on a low-grade office PC if you give it a week.

Hence my saying it won't be soon...

FloatingFatMan said:
Hence my saying it won't be soon...
Click to expand...
Click to collapse
Your still not understanding my friend. Unless your definition of soon is in 30 minutes. Peter Alfonso that develops for the OG Droid and a few other devices compiled his in about 1 hour and 45 minutes. That was a laptop core i7 and 8gb of ram.
Thats not whats going to be time consuming. The hard part will be finding/getting the hardware inside our devices to work. I asked THOR on his forum about ICS on the iconia, his response:
done know for now... depends how many proprietary stuff the a500 uses....
I'm worried the camera, sensors and battery as these seam to be tampered with...
for the moment I'm busy with other stuff will see when I get some time to sneak a peak at the code...
Click to expand...
Click to collapse
Time will tell.

I'm sure FFM understands that. As you say, the hard part is getting the hardware to work, but with a slower machine, how many test builds can you do in a day? With a big fast machine that can build in a few hours vs a laptop that might take a few days can make a huge difference of when you get to your final release.
But hey.. i don't know anything, so why don't I just shut up...

It takes about 3.5 hours for me to build a new version of ICS. I'm on a 3 year old laptop which is why it takes so long. It would be great to have a much newer machine to build with as it would help to make things go faster.

So I guess that Google engineer was taling out of his butt then.

Related

Android 4.0 Conference

Just got finished with the conference and really looking forward for ics to come to the iconia. Did anyone else watch it? Comments, and the samsung nexus also looks amazing
Looks awesome - can't wait for some of the good people here to get this ready for the Iconia A500. I'd do it myself but I have zero ability here
I'm guessing that Ice Cream Sandwich will be running on my Iconia long before my Desire HD!
Yeah I hope it comes soon but it probably wont be here until like mid November I think
It all depends on when Google release the source. the reason why we had to wait so long on the honeycomb builds were because honeycomb was kept (and will keep) closed source through its whole lifecycle.
with ICS, the source is released, there will be SDK available for it, and we can get AOSP base roms for it. so instead of having to wait for an OEM like Acer to ready a rom that we can base custom roms off, we dont have to wait at all.
dev(s) work out the drivers on their own and they can release AOSP roms in some cases well before the oems
unless i have it all wrong of course :S
qwertylesh said:
It all depends on when Google release the source. the reason why we had to wait so long on the honeycomb builds were because honeycomb was kept (and will keep) closed source through its whole lifecycle.
with ICS, the source is released, there will be SDK available for it, and we can get AOSP base roms for it. so instead of having to wait for an OEM like Acer to ready a rom that we can base custom roms off, we dont have to wait at all.
dev(s) work out the drivers on their own and they can release AOSP roms in some cases well before the oems
unless i have it all wrong of course :S
Click to expand...
Click to collapse
Well are AOSP roms any good, are they just like any other rom, but of course the acer update would be the best and would mostly be bug free but would take awhile to get here
Hasn't the source code already been released? I remember reading on Slashgear that the SDK is released. Or is that not the same thing...? Sorry for my noobiness.
There shouldn't be much Acer need to do, seeing as our tabs are pretty much stock anyway... Acer will probably take about a month once the proper source code drops, but there will be custom ROMs within a few days.
where can we find this conference?
As a motorola user (milestone, so locked boot loader and its just rubbish) I'm still quite skeptical about if ICS will be ported to the A500. Anyone heard anything about it happening?
masands said:
Hasn't the source code already been released? I remember reading on Slashgear that the SDK is released. Or is that not the same thing...? Sorry for my noobiness.
Click to expand...
Click to collapse
Nope, SDK is development kit, not (complete) system's source code, but just a precompiled binaries and header files.
Consider yourself: Google did release Android 3.x SDKs (so developers could write apps for Honeycomb), but no Android 3.x source code.
azoller1 said:
Well are AOSP roms any good, are they just like any other rom, but of course the acer update would be the best and would mostly be bug free but would take awhile to get here
Click to expand...
Click to collapse
AOSP Roms are among the best, Oxygen for the Desire and SGS2 is possibly the best phone Rom available.
drdaeman said:
Nope, SDK is development kit, not (complete) system's source code, but just a precompiled binaries and header files.
Consider yourself: Google did release Android 3.x SDKs (so developers could write apps for Honeycomb), but no Android 3.x source code.
Click to expand...
Click to collapse
What's this kernel source code?
http://global-download.acer.com/Ste...SC=PA_6&LC=en&OS=a05&FS=O01&Category=Document
kjy2010 said:
What's this kernel source code?
http://global-download.acer.com/Ste...SC=PA_6&LC=en&OS=a05&FS=O01&Category=Document
Click to expand...
Click to collapse
That's KERNEL source code, not Honeycomb source code.
Kernel != OS
kjy2010 said:
What's this kernel source code?
Click to expand...
Click to collapse
This is kernel source code, not Honeycomb one.
Android/Linux kernel is licensed under GPLv2, while Honeycomb (userspace stuff) is under Apache license (with portions under BSD and MIT licenses). GPLv2 is a "strong copyleft", which requires all distributors to provide source code. Apache, BSD, MIT and alikes are "weak copyleft", and they permit distribution of compiled binaries without obligation to provide source code.
Acer (as everyone out there) was legally obliged to publish kernel source, due to GPLv2 license terms. Yet, they've probably got Android source code under some special proprietary license (with NDA) from Google and are unable (whenever they're willing or not) to publish the source.
drdaeman said:
This is kernel source code, not Honeycomb one.
Android/Linux kernel is licensed under GPLv2, while Honeycomb (userspace stuff) is under Apache license (with portions under BSD and MIT licenses). GPLv2 is a "strong copyleft", which requires all distributors to provide source code. Apache, BSD, MIT and alikes are "weak copyleft", and they permit distribution of compiled binaries without obligation to provide source code.
Acer (as everyone out there) was legally obliged to publish kernel source, due to GPLv2 license terms. Yet, they've probably got Android source code under some special proprietary license (with NDA) from Google and are unable (whenever they're willing or not) to publish the source.
Click to expand...
Click to collapse
Kind of misleading for Acer to label it as such then:
" kernel source code (for Android 3.2 HoneyComb)"
I can't wait to see ICS on the Iconia. Seems a pity the Iconia doesn't have NFC though, as the Beam app in ICS looks amazing! Just as well, it'd probably be sort of tricky to pull off with a tablet in one hand and a phone in the other
Sent from my Nexus S using Tapatalk
kjy2010 said:
Kind of misleading for Acer to label it as such then:
" kernel source code (for Android 3.2 HoneyComb)"
Click to expand...
Click to collapse
But that's exactly what it is..
ernstcomplete said:
I can't wait to see ICS on the Iconia. Seems a pity the Iconia doesn't have NFC though, as the Beam app in ICS looks amazing! Just as well, it'd probably be sort of tricky to pull off with a tablet in one hand and a phone in the other
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Beam won't work with our tablets unfortunately. No NFC.
Sent from my A500 using xda premium
which honeycomb tablet do you think will get the official ICS update first? i think the motorola xoom will
azoller1 said:
which honeycomb tablet do you think will get the official ICS update first? i think the motorola xoom will
Click to expand...
Click to collapse
My bet is Samsung galaxy, since Samsung already has a jump on the software.
Sent from my ADR6300 using XDA App
duloz said:
My bet is Samsung galaxy, since Samsung already has a jump on the software.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I wonder if samsung will keep touchwiz ui on the ICS update

Xoom ICS images soon to be available

Just saw this mail from JBQ on 'Android Building' groups:
I'm pushing the source code for Android 4.0.3 to AOSP. This matches
build IML74K. Kernel sources will follow as soon as practical.
Over the years, I've released 50 different versions of Android in
AOSP, not counting the SDK and CTS, and I think that this is the best
release ever.
Some noteworthy items:
-This version of Android is optimized for a wide range of devices. It
works on phones. It works on tablets. It works on devices that don't
quite have the horsepower of a Galaxy Nexus.
-From a straight AOSP, it works on Galaxy Nexus (the ones sold with
mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus
S (all variants). Proprietary binaries will soon be available for
those devices at the usual location.
-Out of the box, this is the first time that AOSP works on 3 different
device families, the first time that it works on tablets, the first
time that it works directly on a device that's neither an ADP nor a
Nexus, and the first time that it works on Verizon devices.
JBQ
Click to expand...
Click to collapse
Could we expect ICS images for the Xoom soon ?
Unfortunately I'm unable to post a link to that google group page - You can check out the 'The source code for Android 4.0.3 is now available' email thread in the 'Android Building' google groups.
You can't but I can
http://groups.google.com/group/android-building/msg/d73844b1c48f07bb
Sent from my GT-I9100 using CyanogenMod7
Does this mean we could literally put ICS on the xoom now, or is there still a step to take to get a working image?
Sent from my Galaxy Nexus using XDA App
JBQ just posted another email in the same thread releasing the proprietary binaries for the drivers, as well as the android-4.0.3_r1 for the AOSP git sources.
So I assume, if you build the AOSP sources with these binaries extracted in the right place, you'd be able to compile an image that would work on the Xoom.
I'm gonna try that tonight
https://groups.google.com/forum/#!topic/android-building/mjEzwvc_J4k
"Below are the direct links to the various proprietary binaries. The
web page will update in the next few hours."
how long does it take to compile from AOSP again?
EDIT: and no this is not a request for a ETA
Lol, if I knew how to do this, aosp for xoom would be released in as long ad it takes to compile it and make it flashable.
Is anyone who is able, willing to do this for us not in the know? Please!?
Sent from my Galaxy Nexus using XDA App
I think CyanogenMOD takes about 40 mins on a modern computer to build based on something I read. This will vary widely based on your CPU performance obviously. But this is probably a good ballpark: over 30 mins for a full build I'd say based on what I've read.
redmaner said:
You can't but I can
http://groups.google.com/group/android-building/msg/d73844b1c48f07bb
Sent from my GT-I9100 using CyanogenMod7
Click to expand...
Click to collapse
He said the xoom camera doesn't work =(
I think it was something like 4 hours on a 2x quad-core machine with 16 GB of RAM. Can't be bothered to look up the source now.
I'm compiling it now on my dual-Xeon W5687 machine w/72 GB of RAM.
This guide is pretty good: http://www.freeyourandroid.com/guide/compile-ics
Follow the instructions for the Nexus and when you get to "lunch" this page will help:
http://source.android.com/source/building.html
3G/4G users want "full_stingray-userdebug".
Wi-Fi users want "full_wingray-userdebug".
New: Apparently you have to download the binaries and do a make clobber before you do a make according to this page: http://source.android.com/source/building-devices.html. Time to recompile
Note that is required that you use Ubuntu x64 (I'm currently using 10.04.3 LTS)
g1ddy said:
He said the xoom camera doesn't work =(
Click to expand...
Click to collapse
who said it doesnt work in 4.0.3? everything should work out of the box according to JBQ
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
AzN1337c0d3r said:
I think it was something like 4 hours on a 2x quad-core machine with 16 GB of RAM. Can't be bothered to look up the source now.
I'm compiling it now on my dual-Xeon W5687 machine w/72 GB of RAM.
This guide is pretty good: http://www.freeyourandroid.com/guide/compile-ics
Follow the instructions for the Nexus and when you get to "lunch" this page will help:
http://source.android.com/source/building.html
3G/4G users want "full_stingray-userdebug".
Wi-Fi users want "full_wingray-userdebug".
Note that is required that you use Ubuntu x64 (I'm currently using 10.04.3 LTS)
Looks like I overestimated the time it took to compile, it is done after 20 minutes. Now to test it
Click to expand...
Click to collapse
which xoom are you compiling for? if your test are successful will you be sharing?
shakuyi said:
who said it doesnt work in 4.0.3? everything should work out of the box according to JBQ
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
which xoom are you compiling for? if your test are successful will you be sharing?
Click to expand...
Click to collapse
JBQ himself
http://groups.google.com/group/android-building/msg/4000560ec550c8fe
Right now I am compiling for Xoom Wi-Fi (as it is the Xoom that I have). I have to go off to see my friend's graduation so I wont be back for 3 hours at least.
If the Wi-Fi one works, I'll compile 3G/4G if someone hasn't beaten me to the punch yet.
aaaand to some how release it for the rest of us...???
g1ddy said:
JBQ himself
http://groups.google.com/group/android-building/msg/4000560ec550c8fe
Click to expand...
Click to collapse
eh how often do you hold this big thing to take a picture anyways lol, no HDMI sucks but no biggie never had a use for it but have the HDMI cable lol
AzN1337c0d3r thanks! Looking forward to it!
Yeah, not a huge deal for me, but if we get ICS on the xoom, the speed and stability by itself is worth it!
am I correct in assuming that the camera and HDMI will eventually be fixed? We aren't talking permanent incompatibilities, are we?
ScottRTL said:
Yeah, not a huge deal for me, but if we get ICS on the xoom, the speed and stability by itself is worth it!
am I correct in assuming that the camera and HDMI will eventually be fixed? We aren't talking permanent incompatibilities, are we?
Click to expand...
Click to collapse
lol no way will it be permanent we wont see an official update until they go those 2 items fixed, but it doesnt mean we wont have ROMs to use sooner than later!
ScottRTL said:
Yeah, not a huge deal for me, but if we get ICS on the xoom, the speed and stability by itself is worth it!
am I correct in assuming that the camera and HDMI will eventually be fixed? We aren't talking permanent incompatibilities, are we?
Click to expand...
Click to collapse
These are most likely things that Motorola will have to handle themselves (especially the Camera).
Surprised by the lack of HDMI support however, I would have expected that part to be handled by the Tegra2-related bins. But not a big deal for me either.
shakuyi said:
lol no way will it be permanent we wont see an official update until they go those 2 items fixed, but it doesnt mean we wont have ROMs to use sooner than later!
Click to expand...
Click to collapse
That's what I figured, just thought it was odd that the AOSP is released "officially supporting" Xoom, and the camera and HDMI out don't work... Or, is it just a generic tablet AOSP build and only some of the drivers or something...?

[INFO] Linux kernel 3.3 released with merged Android code and more

Quoted from Engadget:
The latest refresh of the Linux kernel, 3.3, is now available, and the second release of 2012 brings with it the long-awaited merging of code from Google's little side project. While that is particularly interesting to developers looking to boot Android or run apps on the stock Linux kernel (FYI: optimized power management and other infrastructure that didn't make it this time will arrive in the next release, 3.4) and represents a resolution to the issues that kept the two apart for so long it's not the only new feature included. There are improvements to file systems like Btrfs, memory management, networking, security and much, much more. Hit the source link below for the full changelog or grab the code and from the usual locations and get your compile on directly.
Source: Engadget, Kernel Newbies, LKML.org
Any devs interested in developing a kernel based on this?
Based on what I read, this release would make it easier for us to compile the kernel as it brings merged Android code.
To me I'm thinking Google will Roll this out to the Nexus Line Up on the Next OTA... Perhaps the delay for the Nexus S if Due To This?
- Google
nice I hope so
iGoogleNexus said:
To me I'm thinking Google will Roll this out to the Nexus Line Up on the Next OTA... Perhaps the delay for the Nexus S if Due To This?
- Google
Click to expand...
Click to collapse
I doubt this is due to any delays regarding ota update, AFAIK, the Android devs at Google have all their own modules etc that they roll in to an update etc. This should however make projects like Ubuntu on Android etc easier.
Sent from my A500 using xda premium
glennkaonang said:
Quoted from Engadget:
The latest refresh of the Linux kernel, 3.3, is now available, and the second release of 2012 brings with it the long-awaited merging of code from Google's little side project. While that is particularly interesting to developers looking to boot Android or run apps on the stock Linux kernel (FYI: optimized power management and other infrastructure that didn't make it this time will arrive in the next release, 3.4) and represents a resolution to the issues that kept the two apart for so long it's not the only new feature included. There are improvements to file systems like Btrfs, memory management, networking, security and much, much more. Hit the source link below for the full changelog or grab the code and from the usual locations and get your compile on directly.
Source: Engadget, Kernel Newbies, LKML.org
Any devs interested in developing a kernel based on this?
Based on what I read, this release would make it easier for us to compile the kernel as it brings merged Android code.
Click to expand...
Click to collapse
I have been porting Samsung drivers for Nexus S for some time till Linux 3.3 RC3..
Sorry, no fully working results yet due to many code improvements..
But the work is in progress.. I'll also try to write so Samsung to get the info about their plans and/or the results of porting this code to 3.3
novic_dev said:
I have been porting Samsung drivers for Nexus S for some time till Linux 3.3 RC3..
Sorry, no fully working results yet due to many code improvements..
But the work is in progress.. I'll also try to write so Samsung to get the info about their plans and/or the results of porting this code to 3.3
Click to expand...
Click to collapse
Thanks for your hard work, man.
Anyway, after some readings, I think it's better for us to wait until 3.4 is released.
It is said that 3.4 will finish all the Android code merging process, with many fixes of course.
I'm no dev at all, so this is just a plain opinion from somewhat avid Android user
Sent from my Nexus S using xda premium
Cool

Compiling Android sources on the Pi

Hi Folks
Recently I helped Adam Outler get adb compiled for his Pi This was not as simpe as it first sounds because as we learnt adb on the host is subtlety different from the one compiled for the target and the AOSP source tree does not support compiling androids host tools for arm out of the box.
However You can add the armv6l host support by creating the file
Code:
<aosp source root>/build/core/combo/HOST_linux-armv6l.mk
The contents of which should look something like this
Code:
# Configuration for builds hosted on linux-armv6l.
# $(1): The file to check
define get-file-size
stat --format "%s" "$(1)" | tr -d '\n'
endef
HOST_SDK_TOOLCHAIN_PREFIX :=
ifneq (,$(strip $(wildcard $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc)))
HOST_CC := $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc
HOST_CXX := $(HOST_SDK_TOOLCHAIN_PREFIX)/g++
HOST_AR := $(HOST_SDK_TOOLCHAIN_PREFIX)/ar
endif # $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc exists
HOST_GLOBAL_CFLAGS += -fPIC
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-x86)
HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
HOST_NO_UNDEFINED_LDFLAGS := -Wl,--no-undefined
You can now use the native pi toolchain to build with the aosp sources, at the very least you'll be able to compile the host tools such as fastboot , adb natively on the Pi. Whether you'll want to go about compiling a full android build using the Pi and whether that is even remotely sensible is a discussion for another day! :laugh:
Hey, thanks for your work on this. Sensible or not, it would be pretty cool to run an AOSP or even a CM build on your phone that was compiled on your Pi.
I tried compiling Boot2Gecko for my SGS2 on my Pi as well, but that kept dying about 6 hours into the build .
I got really lost (just learning all this stuff now), but learning it all while building a project you really like would be far more interesting that learning it while building "nano" or "Vim".
fewesttwo said:
Hey, thanks for your work on this. Sensible or not, it would be pretty cool to run an AOSP or even a CM build on your phone that was compiled on your Pi.
I tried compiling Boot2Gecko for my SGS2 on my Pi as well, but that kept dying about 6 hours into the build .
I got really lost (just learning all this stuff now), but learning it all while building a project you really like would be far more interesting that learning it while building "nano" or "Vim".
Click to expand...
Click to collapse
Yes or compile on the Pi for the Pi, If you want to try do that there's the beiginings of the other side, i.e armv6 target files on my github, It actually targets armv5te because that is already present as a valid target in the AOSP build system, a throwback to pre gingerbread and the HTC Dream ( G1 ) etc.
Thinking about it though, The build system may need a little more adding as I think only x86 based cross compilers will be currently selected for target compilation. I'm yet to get my Pi, there's currently a 6 week lead time on them and I'm thinking about holding out for the 512MB version. Until then it's QEmuPi for me!
The Android build system is pretty forgiving and will let you compile things piece-meal which is good because I don't think it would make it all the way to the end in one go no matter how many hours you give it.
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
Indeed, it's at https://groups.google.com/forum/?fromgroups=#!forum/android-contrib
AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
Hi Adam, Thanks for that, I never really considered it, Last time I read, which admittedly was a long time ago now, they were a little more averse to submissions from the random punter. Maybe they've soften up, or maybe I've just made the whole thing up in my mind It would look alright on my c.v ( resume to you guys ) . However It's far from ready for that. There's some more tweaks to add to it, maybe commands like "make host" to just build the host platform would make sense on a device with limited resources like the Pi
pulser_g2 said:
Indeed, it's at https://groups.google.com/forum/?fromgroups=#!forum/android-contrib
Click to expand...
Click to collapse
You're the second person to do that to me! Someone drops a "google groups link bomb" on me and I lose an hour of my life reading all the posts, It's like low rent alien abduction! LOL :silly:
AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
I was bored waiting for my board so thought I ask if google want an hand, well more of a full arm than just an hand.
Me On Google Groups said:
https://groups.google.com/forum/?fromgroups=#!topic/android-contrib/w5UWtdSTwSg
Hi
I've recently added linux-armv6l to the android build system as a HOST_ARCH so I could build adb natively on the raspberryPi. Is this something you would be interested in adding to the official build system?
Let me first explain why you wouldn't want to accept this.
1. Adam Outler from XDA-developers.com suggested I make this enquiry, Initially, I refrained, given the limited scope of the change I had make which focuses on armv6l specifically and although I would be Interesting to see just how long an AOSP build would take on the RasPi soley from a technical view, I don't think there would be anything to be gained from officially supporting such a device as I made the code publicly available through GitHub.
However upon further consideration this feature can have a much broarder appeal if it was changed to a more general linux-arm HOST_ARCH. Given Arms' current "March" into the server market plus the availability of higher end fast multicore processors such an addition may have a practical real-world application soon then rather than later.
I look forward to hearing your thoughts on this.
Thanks
Click to expand...
Click to collapse
As I pointed out, Arm is getting more desktops now-a-days so they might do this one themselves
[EDIT] Here's the Big Man's Reply
JBQ From AOSP said:
I think we could consider it in principle.
However, I'm not convinced that building all of Android on an ARM host
will be practical any time soon. Because of that, I'd rather avoid
extensive changes much beyond adding HOST_linux-arm.mk. For now, I'll
also want to rely on the distribution's host compiler, to avoid having
to deal with the weight and licensing issues of prebuilt toolchains.
What scope do you have in mind?
BTW, I suggest that you wait until the source release of Android 4.2.
We've been tweaking the build system such that it's easier to control
what gets built, and that might be helpful in your case.
JBQ
Click to expand...
Click to collapse
Looks like a goer then. Because thats the only file I had to add to strart with..

Ubuntu Phone OS

So I've Been a Big fan of Ubuntu for a while and I was thrilled to see that they will be releasing a phone OS sometime hopefully soon. Since I have the laptop dock I have always wanted to try to put full ubuntu on it. However that never fully worked on and had to be done on a blur based rom. I love the new JB rom I have on my phone as It performs well. But at the end of the video 21:00 Mark Shuttleworth, the Founder of Ubuntu stated that Ubuntu Phone runs on ARM based chips and Android Kenerals and Drivers.
I'm just wondering Who else would love to see this run and be compatible on the atrix AND the dock. If we still have a decent amount of developers I'm sure this is more than possible.
Heres the Link for the video:
http://www.ubuntu.com/devices/phone
Just putting the idea out there, but if there are any developers capable of this I'd be more than happy to support.
phone spesification is enough for run and if canonical is behind this i think its possible
I was about to post this as a new thread but when I saw this thread I decided to post it in here.
Happy New Year!
According to the video below Ubuntu for Phones will be compatible with any Android designed-hardware. If I understood it correctly, Atrix last chance is with Ubuntu for Phones for sure.
http://www.androidcentral.com/canonical-announces-its-ubuntu-smartphone-os
I have already said that once before that one reason the OEMs lock the bootloader of their phones is to prevent other platforms to be installed to shorten the life of the devices.
Millions of capable Android devices have already been abandoned due to lack of software support which I blame Google directly to allow the implementation of Wild Wild West on Android platform. The only loser in Android world is and will always be the consumers. Ubuntu for Phones will be the left jab that Google didn't see coming. I personally looking forward to see what Ubuntu for Phones can bring this year.
Update: it seems Ubuntu for Phones will not be available until 2014
Seems BBC covered the story
http://www.bbc.co.uk/news/technology-20891868
and in the article says that it will be released for the samsung galaxy nexus. porting from that to the Atrix may be hard, but it should be like CyanogenMod a little. So thats a little boost to say the least.
I also emailed canonical and showed interest in helping with the project especially with the lapdock capabilities, so ill let you guys know what I get back from them, and If its any useful Ill be sure to forward it to every developer possible.
Yes and simply
Yes it's possible for our Atrix, jus read that :
"Easier hardware enablement
We have teams based in Taipei, Shanghai, London, Beijing and Boston to engage with your engineering and factory operations – and their sole focus is to deliver a crisp Ubuntu experience on your device.
Ubuntu has already been adapted to run on chipsets using the ARM and Intel x86 architectures relevant for mobile devices, with the core system based around a typical Android Board Support Package (BSP). So chipset vendors and hardware manufacturers do not need to invest in or maintain new hardware support packages for Ubuntu on smartphones. In short, if you already make handsets that run Android, the work needed to adopt Ubuntu will be trivial."
So alright we don't MAKE handsets that runs android but we have one, we also have the kernel drivers no ? so with that it's like port a cyanogenmod ROM I think. My quote come from canonical web-site (sorry new member so I can"t post outside links ><) so it's a truth information
leclercqsteeven said:
So alright we don't MAKE handsets that runs android but we have one, we also have the kernel drivers no ? so with that it's like port a cyanogenmod ROM I think. My quote come from canonical web-site (sorry new member so I can"t post outside links ><) so it's a truth information
Click to expand...
Click to collapse
Yep, we have Ubuntu drivers but we're not sure we will be able to use them. But indeed the project of having Ubuntu running as main OS on the Atrix is realistic as we have all the material (HW and SW) required for this, if our devs know how to use them, but I think a whole team would be required for a project this big. It's not just a port of Cyanogen, it's not about taking a kernel and some drivers and snap them with a more recent UI and newer apps. We only got a kernel and an X server, it's far enough but the thing is that this X server was published to run on dev platforms. But also know it can be used on an Atrix, but how to integrate it with a whole new platform ? It will require time mostly. I think. And devs. But we don't have many devs so we only have hope. But maybe the devs on XDA will look more at the Atrix and Webtop.
CSharpHeaven said:
Update: it seems Ubuntu for Phones will not be available until 2014
Click to expand...
Click to collapse
Actually it's supposed to be available late 2013 - according to lifehacker....
http://lifehacker.com/5972559/the-ubuntu-mobile-os-introduced-today-coming-to-phones-in-2014
The Ubuntu Phones that ship with the OS will most likely be available in 2013 in the UK, and will clear american shores in Hopefully late 2013, but most likely will arrive around early 2014.
The OS itself will most likely clear for deployment sometime soon for the samsung galaxy nexus, as for a universal build I'm not sure If/when that will be available, so most likely we will have to see if one can be constructed for the atrix.
As far as the lack of developers, I fell that any and all developers that are still in possession of an operational atrix will want to test this, especially on a phone that isnt their daily driver and has capabilities of bringing back a strong webtop front.
absolutely possible
http://www.youtube.com/watch?v=wzc0uMXGFBY
i like the ubuntu webtop, its run smooth and fast :good:
I think the atrix should be able to run it. just not mine unless the new bootloader gets figured out
Well I really think that Ubuntu can run on the Atrix, because they share the same idea, which is killed by Google: The webtop.
We just plug the phone into a dock, connect it to a monitor and that's it. Besides, the original webtop is just a big browser without many supported applications.
Several webtop-mods have shown that it is possible to run a full Debian or Ubuntu Linux on the phone.
And having one OS for mutliple devices is the stratagy that Microsoft now tries with Windows 8 on Tablets. But other than Windows, Ubuntu really got the chance to do it right.
Possible to run, but...
Well, I'm sure, it won't be a real problem to run the Ubuntu phone OS on Atrix 4g, IMHO, I'm really suprised, they used Atrix 2 and his adventages in testing. It's but I'm sure, HW would not work on 100%. Everyone knows, what is a problem with HWA drivers fot ICS+ even on android. Fingerprint drivers will be problem too... the best roms are (at least in my opinion) GB ones. This is the "tax" we pay for extraordinary HW in Atrix 4G.
Another problem in optimalization is the date of release (futher in future...who knows, how many devs will stay..)
This OS already has its own section on xda and it hasn't even been released yet lol anyways u can share your thoughts on Ubuntu for phone here
http://forum.xda-developers.com/showthread.php?t=2082789
Phone Slow? go HERE
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
Like I said If I got an email back I would let you guys know and sure enough it came and here it is
Thank you very much for your interest towards Ubuntu on smartphones. We have received an incredible response and have been overwhelmed with the general positive feedback! Responses both from the general public and the industry have been far greater that we expected.
In order to make Ubuntu a truly fantastic smartphone experience we will be initially working with manufacturers who will build Ubuntu into their hardware. We anticipate market availability of Ubuntu on smartphones towards the end of 2013.
To reach this goal, and offer a great experience for future consumers, our first priority will be to respond to industry inquiries from manufacturers/OEMs, silicon partners, developers and mobile operators. If you are a potential industry partner, we’d like to learn more about you. Please register your interest through our web form: http://www.ubuntu.com/devices/phone/contact-us
If you are a mobile apps developer, and want to learn how you can help bring Ubuntu to the phone, you can also find more information on:
http://developer.ubuntu.com/gomobile
We are all excited about Ubuntu for phones, but it will take some time to get into the marketplace. If you leave us your email and country details, we will let you know when there is further news:
https://forms.canonical.com/manhattan/
Once again, thank you for your interest in Ubuntu!
Yours sincerely,
The Ubuntu for smartphones team at Canonical
Pretty much everything you could have read up on :/
Greetings to all on this New Year!!!(Almost late!)
Hello people.
Searching the past week about this topic, I found the "How to upload" Ubuntu for phones on Tegra Devices like our Atrix.
Here you could find some info: https://wiki.ubuntu.com/ARM/TEGRA/AC100
This will help un too: http://ac100.grandou.net/nvflash#debian_ubuntu_package
https://developer.nvidia.com/linux-tegra
And here, the Ubuntu for phones. http://cdimage.ubuntu.com/lubuntu/releases/quantal/release/
They recommend the Lubuntu 12:10 because it supposedly run from the box. I did not try this yet until I have all the tools(software & knowledge) ready...
It could be nice to have to opportunity to flash it like any ROM, but, sometimes I like the "hard" way in order to learn and develop myself.
Well guys, BON APPETITE !!!!!
While it's possible from a technical standpoint, I just don't see the developer interest which is a shame really, since the device's only weakness is the lack of updates.
Dav0 said:
Hello people.
Searching the past week about this topic, I found the "How to upload" Ubuntu for phones on Tegra Devices like our Atrix.
Here you could find some info: https://wiki.ubuntu.com/ARM/TEGRA/AC100
This will help un too: http://ac100.grandou.net/nvflash#debian_ubuntu_package
https://developer.nvidia.com/linux-tegra
And here, the Ubuntu for phones. http://cdimage.ubuntu.com/lubuntu/releases/quantal/release/
They recommend the Lubuntu 12:10 because it supposedly run from the box. I did not try this yet until I have all the tools(software & knowledge) ready...
It could be nice to have to opportunity to flash it like any ROM, but, sometimes I like the "hard" way in order to learn and develop myself.
Well guys, BON APPETITE !!!!!
Click to expand...
Click to collapse
This option to install ubuntu is impossible. U would risk to delete/brick partitions or nands. We need a IMG file with the filestructure and flash it with the fastboot/CWM. I can mount ubuntu 11.04 but the problem is no UI loading. Only usable is the terminal.
Sent from my MB860 using xda app-developers app
Hai_Duong said:
This option to install ubuntu is impossible. U would risk to delete/brick partitions or nands. We need a IMG file with the filestructure and flash it with the fastboot/CWM. I can mount ubuntu 11.04 but the problem is no UI loading. Only usable is the terminal.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
No is not impossible. You partition an SD card load it up with kernel and system and use a dual boot solution to boot into the kernel on SD card. Of course some minor changes needed on the kernel. But not impossible.
also porting cyanogenmod is not as simple as grabbing a few drivers and adding a few kernel bits. It is a monumental task of trial and error with hundreds of lines of code to patch and sometimes full libraries have to be re written. Shoot the radio layer on the atrix was a quick hack job on cm for atrix.
Porting Ubuntu is tho should be quite easy. And maybe could even one day live in that juicy 750mb web top partition.
Sent from my Nexus 7 using XDA Premium HD app
You'd probably have to have /home on the internal sdcard to use /osh for installing Ubuntu.
Funny that this is the third thread in the last few days talking about using stand-alone Ubuntu on the device.
Sent from my MB860 using xda app-developers app
samcripp said:
No is not impossible. You partition an SD card load it up with kernel and system and use a dual boot solution to boot into the kernel on SD card. Of course some minor changes needed on the kernel. But not impossible.
also porting cyanogenmod is not as simple as grabbing a few drivers and adding a few kernel bits. It is a monumental task of trial and error with hundreds of lines of code to patch and sometimes full libraries have to be re written. Shoot the radio layer on the atrix was a quick hack job on cm for atrix.
Porting Ubuntu is tho should be quite easy. And maybe could even one day live in that juicy 750mb web top partition.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I mean like webtop in atrix just docking u phone and start Ubuntu version 12.04 and not 9.04 jaunty . And a small question: why does nobody can make it work? there are big changes to make it work I think. Dual boot is without a proof not working for me
Sent from my MB860 using xda app-developers app

Categories

Resources