Hi Guys
I was told the only way Android ADB can connect to the RTSM is using the ADB that is built/paired with the same build running on RTSM.
I am trying to run Linaro ICS 12.12 on different versions of the RTSM but all of them give me "device offline".
It is proving a bit difficult so I am wondering if anyone has been able to do this, and I like to know which versions of ADB
or SDK works?
I have tried the few methods that are described on Linaro web pages including ADBHOST=<...> but they are not working.
Thanks
Ramin
------------------------------
Ramin Zaghi
Software Engineer
Processor Division / PDCS
------------------------------
ARM Ltd.
110 Fulbourn Road
Cambridge
CB1 9NJ, UK
------------------------------
Tel: +44 1223 406347
[Extn 22347]
------------------------------
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
I am about to integrate the hwpack support into our android builds.
Currently the configs are hosted at :
https://github.com/MiloCasagrande/android-hwpacks
There are 2 ways to integrate them:
1. Include the git in all the manifest and specify the right hwpack in
device.mk and copy it to boot directory from common code.
2. Commit individual configs to each of the board specific repository like
device/linaro/origen, specify the same in device.mk and copy it to boot
directory from common code.
The advantage of second approach is that we don't need to maintain one more
repository and the config will be maintained closely to the device.
Regards,
Vishal
Calendar Week 3, 2013: Here is test result summary for Linaro android
Linaro android on following board:
[1] TI Panda board 4430
[2] TI Panda board 4460
[3] Samsung origen board.
[4]ARM v-express A9.
synopsis: after board bootup on panda4460 the primary display on HDMI
colour and graphics is inverted (refer to the bug:) ont the other hand
panda 4430 boot test is fail ( ) Samsung origen Linaro android no major
difference is observed compare to the last build test.
[1] TI Panda 4460 Linaro android [column :AA]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
After board bootup Primary-vid out on HDMI colour and graphics is distorted
in this build,[refer to the bug: 1082124]
audio test PASS, glmark2 test fail,powertop-test fail, suspend-resume test
fail, BT enable failed from UI, speech recorder crashes, wifi failed to
connect, powertop failed on panda 4460.
[2] TI Panda 4430 Linaro android [column :Y]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
Boot test failed for this image, please refer to the spreadsheet and bug
for detais.
[3] Samsung Origen Linaro Android [column: Q]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV…
no major difference or no new bug raise as compare to the last builds.
youtube and audio bug fixed. please refer to the spreadsheet for details.
[4] ARM vexpress A9 Linaro android [column: v]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd…
no major difference or no new bug raise compare to the last build test.
suspend-resume failed, playback of youtube video is failed. adb-over usb
doesnt work. please refer to the spreadsheet.
Thanks & Regards
Soumya Basak
Hi, bero
Sorry, just copied my question in IRC here.
<liuyq> bero, can our toolchain be used directly for NDK?
<bero> liuyq: Probably just needs a few minor tweaks
<liuyq> in ndk/build/tools/DEV-SCRIPTS-USAGE.TXT, I see such things:
<liuyq> The AOSP toolchain/ repository contains sources corresponding to
toolchains
<liuyq> that are used to build the Android platform tree. For various
reasons, they
<liuyq> need to be slightly patched for use with the NDK.
<liuyq> bero, I am confused that if the toolchain used for normal build can
be used directly for NDK?
<liuyq> bero, in our normal build, we just specify TARGET_TOOLS_PREFIX
before build, are the jni files built with the same toolchain specified by
TARGET_TOOLS_PREFIX?
--
Thanks,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/pipermail/linaro-validation
Hi,
The agenda has been posted for tomorrow's meeting:
https://wiki.linaro.org/Platform/Android/Meetings/2013-01-16
Please update your weekly status and also go through the agenda and feel
free to update agenda items. Please think about any ideas for connect
discussions and demos for Demo Friday.
Regards,
Vishal
This should be set in all our builds. It disables the first boot
wizard and the lockscreen (among other things I'm still looking into).
There also seems to be a nifty little way to do this using the Trade
Federation stuff, which I've just started looking at.
--
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
sir,
i have successfully done the porting of ICS on pandaboard by prebuild
binaries
as a part of my project i have to do something more but i don't know java
and cann't write android app
so what else can i do on system level
how can i customize these prebuild binaries so that i can install
additional services like bluetooth, ethernet, camera, temperature sensors .
TUSHAR GOYAL
i am currently porting icecream sandwich on pandaboard and facing problem
while partitioning SD card. please suggest a solution to ocvercome this
error.
I see...
Device Mount point Size
/dev/sda none 152587MB
/dev/sda1 none 54MB
/dev/sda10 none 35840MB
/dev/sda11 / 10244MB
/dev/sda2 none 30725MB
/dev/sda3 none 120346MB
/dev/sda5 /media/_1 30725MB
/dev/sda6 /media/_home1 20481MB
/dev/sda7 none 2565MB
/dev/sda8 /media/DAC 10244MB
/dev/sda9 /media/DESD 10244MB
/dev/sdb none 3780MB
Are you 100% sure, on selecting [/dev/sdb] (y/n)? y
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Traceback (most recent call last):
File "./linaro-image-tools/linaro-android-media-create", line 141, in
<module>
unpack_android_binary_tarball(args.system, SYSTEM_DIR)
File
"/opt/try/linaro-image-tools/linaro_image_tools/media_create/unpack_binary_tarball.py",
line 27, in unpack_android_binary_tarball
proc.wait()
File "/opt/try/linaro-image-tools/linaro_image_tools/cmd_runner.py", line
100, in wait
raise SubcommandNonZeroReturnValue(self._my_args, returncode)
linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process
"['sudo', '-E', 'tar', '--numeric-owner', '-C', '/tmp/tmpCtNKd8/system',
'-jxf', 'system.tar.bz2']" returned a non-zero value: 2
