Hey everyone!
I've had some questions about what "TINY_ANDROID" is (and isn't).
I put together this Wiki to answer any questions and make some
recommendations for its use.
https://wiki.linaro.org/Platform/Android/UseTinyAndroid
Basically this build can be built from source in about 20 min (kernel
included) and support most of the low level userspace tools we need to
work with. It should be ideal for 64-bit native Android porting.
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
+android list
On Tue, Aug 21, 2012 at 12:41 PM, Dave Pigott <dave.pigott(a)linaro.org> wrote:
>
> Dave Pigott
> Validation Engineer
> T: +44 1223 40 00 63 | M +44 7940 45 93 44
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog
>
> On 21 Aug 2012, at 10:19, Alexander Sack wrote:
>
> On Tue, Aug 21, 2012 at 10:37 AM, Dave Pigott <dave.pigott(a)linaro.org>
> wrote:
>
> -----------------
>
> beaglexm02
>
> -----------------
>
> http://validation.linaro.org/lava-server/scheduler/job/29737
>
>
> Absolutely enormous log file. The board was in a very strange state, spewing
>
> out loads of exceptions. Went onto the board and it was still throwing out
>
> exceptions. Did a hard reset and it came back cleanly. Not clear why hard
>
> reset didn't work from the LAVA session.
>
>
> Put back online to retest.
>
>
> ------------
>
> origen04
>
> ------------
>
> http://validation.linaro.org/lava-server/scheduler/job/28745
>
>
> Failed to get root.tgz. I may be missing something, but if you look at
>
> http://validation.linaro.org/lava-server/scheduler/job/28745/log_file#entry…
>
> you'll see that it says it's waiting 60 seconds to retry, but doesn't seem
>
> to actually retry. Anyone any ideas?
>
>
> Put back online to retest
>
>
> --------------------------------------
>
> panda01-05/09/10/12/14-23
>
> --------------------------------------
>
> http://validation.linaro.org/lava-server/scheduler/job/29825 (as an example)
>
>
> This is just odd. It says it couldn't get the android artefact
>
> (http://validation.linaro.org/lava-server/scheduler/job/29825/log_file#entry…)
>
> but it doesn't appear to have even issued a wget!
>
>
> Looking at the time stamps, something happened between 14:00UTC and 20:00UTC
>
> that stopped things working. Whatever it was, I'm retesting panda01 to see
>
> if it went away, or if (as I suspect) all the other boards will fail when
>
> they run their health check.
>
>
>
> Could we maintain an easy to find trackrecord about what was deployed
> when? This might also help us to attach a check list that people run
> through and sign off before pushing the production button (e.g. all
> health jobs must have succeeded on staging before rolling out etc.).
>
> --
>
>
> +1 to that, but in this case, it turns out that the android image we use for
> testing comes from snapshots, and that particular snapshot was retired
> yesterday. None of the releases seem stable enough to use for health checks
> so, for the moment, we're re-baslining on a new working snapshot (liuyq is
> working on this at the moment.)
>
> For the future, we're discussing holding the health check images cached
> locally, so that we're not hampered by these issues again, and we can choose
> when and how to re-baseline.
Hmm. I would very much prefer if we could figure a way to use released
images as our health-check base. Even if it means we do a "special"
promotion of a certain daily build outside the monthly cadence if
needed ...
On this front: is there an easy way to check that a certain build is
suitable for health check? If so, we could make that part of our
monthly validation process and daily dashboard and assign priority to
bugs that would disqualify a build from being suitable as a health
check...
What do you think?
--
Alexander Sack
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi guys,
I am not sure how many of you are aware of this feature, but AOSP
effectively implements multi user support for Android.
I found out it is in AOSP a couple of weeks ago (a bit after implementing
it myself unfortunately...), and although it must have some flaws it seems
to work very nicely.
Separate /data/... , Separate ContentProviders, user aware ActivityStack
etc. Just root your device / emulator, "pm create-user" "am switch-user"
and you got yourself separate profiles.
Are you guys at Linaro aware of this feature? If so, I would be glad to
further discuss it and this mailing list seems like a good place to do
that, following the interesting "Android vs. Linux" discussions in VC #6
and #8.
Google doesn't mention anything about it and there's no point in discussing
it in "android-platform" as the google guys will probably address this
subject only when released.
For those who don't know this feature, here is a trivial working usage
example of what I'm talking about, with some explanations of how stuff
works.. Would work for any current master branch build:
# t=0: No users.
# The good old /data/data package install hierarchy is used as is (well
actually /data/user/0 is a # symlink to that.)
# t=1: Create users - Now the PackageManager actually installs the packages
in /data/user/<number>/com.bla.blabla.app
adb -e shell pm create-user ClarkKent # Added user Primary at id=0 and
ClarkKent at id=1
adb -e shell pm create-user Superman # Added user Superman at id=2 .
Superman can fly, lift heavy weight, shoot laser beams off his eyes - but
he is not a super user/ "system" user.
# t=2+ switch users. from the little I experimented with it works nice -
Just avoid the "primary" user.
adb -e shell am switch-user 2
adb -e shell am switch-user 1
# ps output would yield a uX_aY entry for each app as long as it's not
owned by root/system, where X is the user id, and Y an "old" uid for each
app.
--
Ron Munitz, M.Sc
CTO, Nubo Software
Office: +972-72-2452033
1 HaYarden St. P.O. BOX 1018, Airport City 70100, Israel
Dear linaro,
thanks for your reply.
Q1: but when i excute this script
./install-binaries-4.0.4.sh /dev/sdb2 （sdb2 is my device）
also occer occer:
trap: 22: ERR: bad trap
How can I solve this problem?
Q2:I want to use pandaboard hardware encoder/decoder,how to use it?
eg: yuv video encoder to H.264
Q3:if I flash ubuntu to pandaboard, how to use hardware encoder/decoder, how can I get the API?
thank you very much.
dear linaro,
I want to flash my pandaboard with SD card using
./install-binaries-4.0.4.sh /dev/sdX2
but occer error: trap: 22: ERR: bad trap
how can I solve this problem?
Thank you !
# Get graphics binaries
$ wget http://people.linaro.org/~vishalbhoj/install-binaries-4.0.4.sh
$ chmod a+x install-binaries-4.0.4.sh
$ ./install-binaries-4.0.4.sh /dev/sdX2 "device node of system partition"
I've just finished building the 2012.08 toolchain release.
Aside from the usual update from the toolchain WG, this release
updates mpfr to 3.1.1 and mpc to 1.0, and the target specific parts
are built against JellyBean's instead of Ice Cream Sandwich's version
of Bionic.
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.7-2012.…
I'm switching over the builds, let me know if anything breaks.
ttyl
bero
Hello,
I would like to now if there are plans for new wersion for i.MX53.
I tried wersions 12.05, 12.04 and 12.03 without success.
With those versions I have only black screen, no booting.
Did someone install with success Android on i.MX53 QSB?
Best regards.
------
adresik to ja mam w www.adresik.pl a hosting na www.klatka.pl
