Help-
I have a new Panda board (the box label says UEVM4460G-02-01-00) with a 16 GB SD card and DVI monitor, with Ubuntu 10.04 as the dev platform.
I have been trying a number of different pre-built Android binaries (starting at pandaboard.org and following instructions there (Quickstart with pre-built binaries) which takes me to omappedia and linaro, but can't seem to get any to come to full running status.
The release with most success is 12.03, but as soon as the "Android" shimmer screen is replaced with the Android environment, a window pops up to say "Unfortunately, Launcher has stopped". Some green blocks are moving about the screen at approx a one second interval, and moving the mouse causes the cursor to move very slowly, in sync with the green block movements.
A few icons are shown at bottom left, and time of day is shown at bottom right. Nothing else is visible on the screen.
Pressing the reset button cause a reboot, but this time it gets no further than the Android shimmer screen. The TTY console shows what appears to be an endless loop of a few dozen events, all seeming to repeat themselves.
Not sure what details are needed to get past this problem, any help would be most appreciated.
I have also tried releases 12.01, 12.02, and 11.11. None of these even show anything on the monitor.
Thanks,
Ron
____________________________________________________________
53 Year Old Mom Looks 33
The Stunning Results of Her Wrinkle Trick Has Botox Doctors Worried
http://thirdpartyoffers.juno.com/TGL3131/4f94bdbf27e2681f827st01vuc
Hello,
Linaro Infrastructure group is glad to announce support for
restricted-access builds for Linaro Android. Such builds will allow us
to adhere to our members' licensing and business restrictions for
limited-access features, while still as much as possible to follow
established Linaro open process, and let general public to be in loop
on the upcoming great new features for the ARM platform. Restricted
builds are used immediately for ongoing big.LITTLE enablement work.
Restricted builds are available in our standard Android Build System, in
a separate tab:
https://android-build.linaro.org/#builds=restricted
Members of the Launchpad group "linaro-android-restricted" are able to
setup new builds (please note that this group doesn't allow direct
access to restricted source code or downloads, only gives the ability
to establish a restricted build). Administrators of the group include
Alexander Sack and Zach Pfeffer, they should be contacted for
membership requests.
To set up a restricted build, select "linaro-android-restricted" as the
owning group in the dropdown on "New build" page (this is UI change
from previously available checkbox to create an official build, all
choices are now available in dropdown). As second step, add/replace
value of the following build config variable:
BUILD_TYPE=build-android-restricted
If you have a question regarding this functionality or found a bug,
please submit it directly or via the bug tracker at:
https://bugs.launchpad.net/linaro-android-infrastructure
Thanks,
Paul
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
On 24 April 2012 18:34, Mans Rullgard <mans.rullgard(a)linaro.org> wrote:
> On 24 April 2012 18:21, Chris <tichris08(a)gmail.com> wrote:
>> Hi,
>>
>> I'm trying to upgrade Android's aging libpng 1.2.46 to 1.5.10 and I'm
>> running into a nasty issue. I'm particularly running into a problem
>> while running a tool in Android on x86 called aapt, which can be thought
>> of as a resource packager which uses PNG's writing ability to make a
>> huge binary asset. I was able to get the code to compile without any
>> issues on all versions of libpng (1.2, 1.4, 1.5) and it works fine with
>> the default config for 1.2 and 1.4 but fails on 1.5 with an "internal
>> write transform logic error".
>>
>> I debugged the code a little bit and saw that it is failing because I'm
>> failing the test:
>> (row_info.pixel_depth != png_ptr->pixel_depth)
>>
>> Given:
>>
>> row_info->{colortype=2, width=46, channels=3, bit_depth=8,
>> pixel_depth=24, row_bytes=138}
>> png_ptr ->{colortype=6, width=46, channels=4, bit_depth=8,
>> pixel_depth=32, row_bytes=184}
>>
>> I do have a "filler" transformation on my source data to remove the
>> alpha channel which explains how row_info started off to be the same as
>> png_ptr, but was switched to having one less channel. I can't really
>> think of a way to pass the above-mentioned test with a filler
>> transformation. Is this a bug in libpng or is aapt using the library
>> incorrectly and this path that used to work no longer does for a good
>> reason?
>
> IIRC we saw this error when trying the same upgrade in Linaro, but
> I can't remember what the conclusion was. Maybe someone on the
> linaro-android list can help.
Silly gmail auto-complete picked a bad address for linaro-android.
Trying again.
--
Mans Rullgard / mru
Dear linaro-support team
Currently , I used linaro-android_snowball-ics-gcc46-igloo-stable-blob-12.03-release at your snowboard
I face a question , that is
When I used adb , follow below command form your web-site
* ADB only works over IP
In the console type:
* stop adbd
* setprop service.adb.tcp.port 6565
* start adbd
* ifconfig eth0 # to get boardsIP
after my host connect to device
, I try to used adb push -s <device IP>:6565 <my txt file> /data or adb -s <device ip>:6565 shell form host
Both fail ,and I didn't see any error meaage , it look like hang after I type above adb command
Do you have any suggestion about this
Thanks for your help
Linas
Hi Android Team,
Linaro Android 12.04 release has been cut. QA testing is in progress.
Please, update your blueprints for this cycle asap:
https://launchpad.net/linaro-android/+milestone/12.04
Cheers,
--
Fathi Boudra
Linaro Release Manager | Validation Project Manager
Linaro.org | Open source software for ARM SoCs
HI,Bero and Android team
For this issue,
https://bugs.launchpad.net/linaro-landing-team-freescale/+bug/880459
Actually, Audio works fine in Ubuntu LEB. But not working on Android LEB. This should not be a problem in kernel.
So, could you please provide us your analysis from user space first?
Thanks.
Best regards,
Guodong Xu