Hi All
I found the bring the interface hci0 up if I removed the hardware(AR3011
module) and inserted it again.
Is it due to some timing issue about USB hubs when device booting up?
BRs
Dean_Lin
D.Ean Lin於 2013年1月5日星期六UTC+8上午1時33分08秒寫道：
Hi All
I'm trying to porting Bluetooth on Android-x86
On Nov 18, 6:48 am, celeritas devang221...@gmail.com wrote:
I want customized envetup.sh file.
can anyone please give it to me.
What do you mean? Froyo can be compiled on a x86 host pc.
If you mean you would like to compile Android for an x86 system,
please have look here:
Hey David!! I didn't get any text in your reply!!!
On May 26, 1:37 am, David Turner di...@android.com wrote:
On Mon, May 24, 2010 at 10:05 PM, Yi Sun beyo...@gmail.com wrote:
Www.android-x86.org
NOTE: android-x86 is hardly anything officially supported.
On 2010-5-24, at 11:12,
thanks sun... but i was looking at how to use the :
TARGET_PRODUCT=sim
TARGET_SIMULATOR=true
TARGET_BUILD_TYPE=debug
options on ubuntu-virtual box.
also what is the difference between TARGET_BUILD_TYPE=debug and
TARGET_BUILD_TYPE=release ? in terms of compiler optimization and
symbolic debug
Hi Dima,
its been a while .. any updates on X86 porting?
I'm adding support for WebM to StageFright and my purpose is to
build and debug the StageFright multimedia framework natively using
the stagefright executable in the cmds folder. Currently i'm using
logcat to debug.
I have 2 questions:
Www.android-x86.org
On 2010-5-24, at 11:12, NimeshChanchani nimeshchanch...@gmail.com
wrote:
Hi Dima,
its been a while .. any updates on X86 porting?
I'm adding support for WebM to StageFright and my purpose is to
build and debug the StageFright multimedia framework natively using
the
Hi
I just verified that with kvm qemu, I am able to create other guest OSes
like gentoo linux from iso image and I did not get the VGA problem I got
with 'android-x86 for generic_x86' target iso image.
Has anyone faced something like this before? Also do I need to customize the
configuration in
The port I meant is the one here: http://www.android-x86.org/getsourcecode
By 'MID' build I meant the default configuration builds a MID device
out of the code, not a phone, though you can change it.
On Sep 16, 9:44 pm, Yi Sun beyo...@gmail.com wrote:
What is the android-x86 MID port? I
in that case, you should be able to access localtext. I have a tree synced
on 09-11. It works without any problem . And I also checked the prebuilt
image released yesterday, it also worked. Did you changed anything?
On Thu, Sep 17, 2009 at 11:49 AM, efu ericf...@gmail.com wrote:
The port I
What is the android-x86 MID port? I mean, where did you get it?
On Wed, Sep 16, 2009 at 9:21 PM, efu ericf...@gmail.com wrote:
I am running an android-x86 MID port on virtualbox but the Locale and
Text option under Settings menu is disabled.
How do I enable that option?
--
I have a fix for this. I will submit it soon.
Until then, to unblock your work, you can
- In external/opencore/Config.mk, comment the line PV_CFLAGS += -
fvisibility=hidden.
- In external/opencore/oscl/oscl/config/android/osclconfig.h, replace
the following two lines:
#define OSCL_EXPORT_REF
Hi,
I downloaded android source code for x86 today and tried to compile
it, but failed, here is the error that I received:
$TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -
j2 installer_img
PLATFORM_VERSION_CODENAME=Donut
You are using wrong command.
Take a look on the wiki page:
http://code.google.com/p/android-x86/wiki/GetSourceCode
On Tue, Aug 4, 2009 at 1:48 PM, penguins suf...@gmail.com wrote:
Hi,
I downloaded android source code for x86 today and tried to compile
it, but failed, here is the error
I missed one item in BoardConfig.mk
diff --git a/BoardConfig.mk b/BoardConfig.mk
index 54b0d4f..68000ce 100644
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -8,6 +8,7 @@ TARGET_NO_BOOTLOADER := true
TARGET_NO_RECOVERY := true
#TARGET_NO_KERNEL := true
+TARGET_CPU_ABI := none
TARGET_HARDWARE_3D
Have you run the image? There should be more issues, the 10482 was not fixed
yet (not sure about today's status), the init.rc has new entries need to add
Yi
On Sun, Aug 2, 2009 at 3:21 AM, Chen Yang sunsety...@gmail.com wrote:
Just finished one round of proof build of the public AOSP code:
yes, I have run it.
10482 has 2 issues, my 2nd item fixed one issue. I don't know whether
current framework has the right kind of implementation that may expose the
2nd issue of that. At least, from what I have run, I haven't found problems
so far.
--
Chen
On Mon, Aug 3, 2009 at 2:10 AM, Yi Sun
Chihwei backed out both from android-x86
On 2009-8-2, at 16:54, Chen Yang sunsety...@gmail.com wrote:
yes, I have run it.
10482 has 2 issues, my 2nd item fixed one issue. I don't know
whether current framework has the right kind of implementation that
may expose the 2nd issue of that.
FYI-- for the wifi, if your driver needs a firmware, it may not work at
all. And we are working on to create a working sample so that people can
add the firmware by their self.
Yi
On Wed, Jul 29, 2009 at 11:05 PM, Chih-Wei cwhu...@linux.org.tw wrote:
The android-x86 build broken due to
Cool. would you like to provide some more detail about the issue? Thanks.
--
Chen
On 7/30/09, Chih-Wei cwhu...@linux.org.tw wrote:
The android-x86 build broken due to upstream changes (donut merged) is
fixed.
Now you can get a workable tree and enjoy Donut on x86.
You may try to repo sync.
Chih-wei and I are trying to find a good way to organise the firmware
directories.
On Thu, Jul 30, 2009 at 12:10 AM, Chen Yang sunsety...@gmail.com wrote:
Cool. would you like to provide some more detail about the issue? Thanks.
--
Chen
On 7/30/09, Chih-Wei cwhu...@linux.org.tw wrote:
Done, thanks Dima!
On Wed, Jan 28, 2009 at 11:22 AM, Dima Zavin d...@android.com wrote:
Actually, you don't need the -b cupcake anymore. It's been merged down to
master, so please update the doc :)
Thanks.
--Dima
On Tue, Jan 27, 2009 at 10:56 PM, EricaJoy ericajoyba...@gmail.comwrote:
swap has been included twoce. It is there in standard stl libs. This
problem is visible with gcc4.3.x.
open /$ANDROID_SOURCE_ROOT/external/webkit/WebKit/android/stl/
algorithm in editor and comment lines 76 -83
//templatetypename _Tp
//inline void
//swap(_Tp __a, _Tp __b)
//{
Hi Jeroen
I just saw that someone added a tutorial about how to build the kernel
for Geode LX to the Wiki, I guess that was you? Thanks!
I pimped it a little bit, I hope you don't mind...
--Dani
On Jan 20, 7:48 am, squix dani.eichh...@squix.ch wrote:
That sounds great! When I had my own
Great, how a good start.
Merck
On Jan 18, 8:04 pm, squix dani.eichh...@squix.ch wrote:
Hi everybody
I got tired of pull together all the little bits and pieces from the
many x86 related threads in this forum and I setup a website for this
purpose:http://www.androidx86.org
Don't get me
That sounds great! When I had my own attempts with compiling a kernel,
I wondered if it even was necessary to optimize it for geode, since
the standard Ubuntu Intreprid kernel runs well on my Geode board (I
know, it still lacks the android adaptations...).
Would you mind to document your progress
Great Initiative.
I happen to have very similar plans. (Also a Geode GX with touchscreen
for home automation.)
Regards
Jeroen
On Jan 18, 1:04 pm, squix dani.eichh...@squix.ch wrote:
Hi everybody
I got tired of pull together all the little bits and pieces from the
many x86 related threads in
Did you have any success in doing that? I configured the kernel for
Geode GX1 and compiled it, but then I struggled with old problems to
run the live image from an external USB harddisk, since my
touchscreen PC doesn't know booting from USB memory stick yet. The
kernel contained in the default
Hi, Chen,
For the restriction you mentioned that a partition over 1024 blocks
can't be accessed by grub, I have more confusion about that after
comparing with this partition upon which local grub is resided in the
internal hard disk (i.e. /dev/sda) that has been running ubuntu 8.04.
For more
Hi,
Did you set a bootable flag to your target partition?
I'm not sure though, it sounds like your BIOS doesn't
recognize your USB HDD as a boot device.
Good luck.
On 1月13日, 午前12:06, Samuel samuel.om...@gmail.com wrote:
[Title]
Enabling android-x86 upon ThinkPad Series with miscellaneous
Hi, Android Zaurus,
as you supported, I never have set a bootable flag for this bootable
partition, namely /deb/sdb3, in the sdb as showed as below,
$ sudo fdisk -l
Device Boot Start End Blocks Id System
/dev/sdb1 1 255020482843+ cW95
Hi Samuel:
It seems that you need to modify the menu.lst to reflect the
correct root device, in your case:
root(hd0,0) - change to (hd0,2)
kernel /boot/vmlinuz-2.6.27-android root=/dev/sda1 init=/init rw
selinux=0 vga=788 quiet - change the rppt=/dev/sda1- /dev/sdb3
Hi, Chen,
At first, thank you for your helping!! I consider that your helps are
so helpful to me, though i can't t still boot up android from external
mobile hard disk so far!! But all mistakes are due to me!!
Under the helps of you, i have modified some places in the menu.lst
for android
Thanks for the reply chris, I shall keep an eye out for that, will you
post the results here? Thanks, Martin.
On Jan 7, 12:23 am, Chris chris.l.elf...@intel.com wrote:
Hi Martin,
I have not tried wifi or bluetooth yet on the Wind. This is one of
the reasons that Dima mentioned that in the
if you didn't get around this problem yet, try
1. 'ps' to list the installer process and 'kill' it
2. run '/system/bin/installer -p /dev/block/
YOUR_SECOND_PARTITION_ON_USB_STICK' (e.g., I used /dev/block/sdc2 and /
dev/block/sdd2 for my EeePC 701 and 900 respectively)
On Dec 31 2008, 3:39 pm,
Thanks for your answer. When I try to compile the kernel with the
config file from the eee project I get the following error and I have
no clue how to solve it:
CC=gcc-4.2 CXX=g++-4.2 make ARCH=x86 CROSS-COMPILE=
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL
You shouldn't be building pmem for x86. Its not needed, and i think there
are a few ARMisms in there that we haven't had a chance to clean it up.
Take it out of your config file (it's is not in the kernel.config in the
eee701.git repo).
--Dima
On Fri, Dec 26, 2008 at 9:54 AM, squix
The music player seems to play music and dmesg indicates that the
INTEL HDA Audio
chip is correctly loaded. Could it be that everything is fine and just
the volume is turned off?
If this is the case how can I turn it on? :)
For audio, you'll need the alsa stuffs. You'll also probably need
The ramdisk may void the rootwait option, thus it won't solve the
issue.
Several approaches can be used to solve the issue.
1. extract the ramdisk on your usb disk to a separate empty parition
and specify the root in the cmdline, be sure to add the rootwait (or
rootdelay) option.
2. I remembered
Forgot to add one better soultion by using Chris's script make-live:
http://code.google.com/p/android/issues/detail?id=1598
--
Chen
On Dec 24, 11:12 pm, Sunset sunsety...@gmail.com wrote:
The ramdisk may void the rootwait option, thus it won't solve the
issue.
Several approaches can be
Sorry for such a stupid question, but is the kernel provided in anyway
patched for the use with android or is it basically a standard x86
kernel? What do I have to do to build a kernel for an older target
like a Geode GX1?
Dani
On Dec 23, 2:43 am, Dima Zavin d...@android.com wrote:
Although
Sorry for such a stupid question, but is the kernel provided in anyway
patched for the use with android or is it basically a standard x86
kernel? What do I have to do to build a kernel for an older target
The kernel is built from the android tree. All you have to do is check out
the
what does logcat say?
--Dima
On Sun, Dec 21, 2008 at 9:38 PM, Huan Truong huan...@gmail.com wrote:
FYI: This is the dmesg log:
http://pastebin.com/m73537fac
I don't know if it was wrong at any point. Any help is appreciated.
--~--~-~--~~~---~--~~
Hi all,
First of all let me thank Dima, Chris (and everyone else involved) for
their x86 porting work. This is a much anticipated step, one which will
help make Android very useful outside the mobile phone world.
So... I have tried the installer on a small desktop PC - a Asus Nova Lite:
Hi,
Dima Zavin wrote:
So... I have tried the installer on a small desktop PC - a Asus
Nova Lite:
http://www.asus.com/news_show.aspx?id=11565
Heh, cute. I should mention that we really should not be reusing the
same installer images as a general purpose installer for
I tried to install from the install USB disk to my other USB disk on
my eeePC 900HA (with my hard drive taken out), and I am currently
stuck shortly after the screen changed to 1024x600 fb:
http://i43.tinypic.com/25p4cqc.jpg
Looks like we need to wait a little bit more before we try to mount
the
Hi,
Can you add rootdelay option to kernel cmdline? like, rootdelay=8?
On 12月21日, 午後5:00, Huan Truong huan...@gmail.com wrote:
I tried to install from the install USB disk to my other USB disk on
my eeePC 900HA (with my hard drive taken out), and I am currently
stuck shortly after the screen
Can you add rootdelay option to kernel cmdline? like, rootdelay=8?
That will probably help. I'd still really like to see us creating the
volume_id named block device nodes somewhere in /dev/block-volid/. Perhaps
I'll see if I can find some time over the holidays to mess around with it.
--Dima
Thanks, the problem I ran into was that /dev/block/sdb was
the card reader and the USB stick was sdc. After changing
the argument for installer to /dev/block/sdc2, I got it
installed.
On Dec 20, 4:05 am, Dima Zavin d...@android.com wrote:
after boot from my USB stick, I saw
init: Unable to
Mizmit and Dima,
Thanks for your suggestions, I tried adding rootdelay to the system
volume, but seems like it didn't help. Looks like appending it to the
cmdline didn't make any differences at all. I appended the option at
the end of the cmdline file in my usb stick. Did I do something wrong?
FYI: This is the dmesg log:
http://pastebin.com/m73537fac
I don't know if it was wrong at any point. Any help is appreciated.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Where should the local_manifest.xml file be placed?
On Dec 18, 2:25 pm, Dima Zavin d...@android.com wrote:
Argh, forgot to mention that you'll need a local_manifest.xml that looks
something like this:
?xml version=1.0 encoding=UTF-8?
manifest
project name=platform/vendor/asus/eee_701
Nevermind, I figured it out. In case anyone is looking for this
information in the future, it appears it needs to go in .repo,
followed by a repo sync.
On Dec 20, 7:45 am, Brock brock.t...@gmail.com wrote:
Where should the local_manifest.xml file be placed?
On Dec 18, 2:25 pm, Dima Zavin
WARNING: As Chris said, the installer will wipe your hard drive, and
no, it won't ask you a single thing. Remember, take your hard drive
OUT physically, not just in the BIOS. Even if you disabled the hard
drive in BIOS setup, the installer will still erase your hard drive. I
learned it the hard
I could not compile the cupcake branch as of 1:20PM CST. There seems
to be some error while compiling fst.o
external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/vector-
fst.h:404: error: ‘memcpy’ was not declared in this scope
after boot from my USB stick, I saw
init: Unable to open persisent property directory /data/property
errno: 2
and
This is harmless in this case.
I/installer( 1865): Waiting for device: /dev/block/sdb2
than some USB information, and shell prompt
my internal SSD was not touched at
I had the same problem. It has to to with the gcc version your using
and the header refactoring that they did for that version. You can fix
errors like that by simply adding the right includes in the file
complaining.
In 90% I had to add one of these
#include cstdlib
#include cstring
but there
I have been able to successfully run the eee701 cupcake build on an
MSI Wind. I have a _VERY_ preliminary script that takes the
installer.img and a USB stick and creates a live USB stick that can
be booted. Running off of USB will make some apps timeout a bit more
because its not as fast as
Chris et al,
Can you tell me the version of gcc you're using to compile. Seems like
gcc-4.3 has many problems with cupcake.
On Dec 19, 3:44 pm, Chris chris.l.elf...@intel.com wrote:
I have been able to successfully run the eee701 cupcake build on an
MSI Wind. I have a _VERY_ preliminary
/usr/lib/gcc/i486-linux-gnu/4.2.3/cc1plus
It seems to be using the gcc that I happen to have installed on my
Ubuntu 8.04 system...
celf...@celford-ubuntu:~/cupcake$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c+
Check this:
http://source.android.com/roadmap/cupcake
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Thanks Dima!
The most exciting update yet comes the day before I leave for a two
week vacation. Hopefully I will be able to try it before I leave. I
have been trying to repo init and repo sync to this since yesterday
but am getting a ton of socket errors. It could be an issue with our
Very cool, thanks for the effort! Can't wait to try it...
Cheers
Filipe
Chris wrote:
Thanks Dima!
The most exciting update yet comes the day before I leave for a two
week vacation. Hopefully I will be able to try it before I leave. I
have been trying to repo init and repo sync to
after boot from my USB stick, I saw
init: Unable to open persisent property directory /data/property
errno: 2
and
I/installer( 1865): Waiting for device: /dev/block/sdb2
than some USB information, and shell prompt
my internal SSD was not touched at all, that is, it didn't start to
install
I got it. it located in out/host/linux-x86/bin. Thanks.
On Dec 4, 10:28 am, Lucky-dog [EMAIL PROTECTED] wrote:
hi all
I fixed it with renaming swap to swapab. But now I have another
question needed your help. I can't let the following command get to be
run.
dx --dex --output=foo.jar
hi all
when i try to compile the source on DEBUG x86. A error is reported
out as below. Would you like to let me know how to fix it? Thank you
very much.
[EMAIL PROTECTED]:~/mydroid$ make
build/core/product_config.mk:229: WARNING: adding test OTA key
build/core/main.mk:177: implicitly
My ubuntu is 8.10. I try the tips to compile android for x86. But it
seem envsetup.sh does not work. Would you like to help me? Thank you
very much. The log is as below.
[EMAIL PROTECTED]:~/mydroid/build$ echo $SHELL
/bin/bash
[EMAIL PROTECTED]:~/mydroid/build$ bash --version
GNU bash, version
$ . build/envsetup.sh
$ lunch 2
are two separate commands. The first one sets up the environment and
the second one sets which configuration you want to build.
On Mon, Dec 1, 2008 at 2:30 PM, Lucky-dog [EMAIL PROTECTED] wrote:
My ubuntu is 8.10. I try the tips to compile android for x86. But
Good afternoon everyone,
there is a problem during my Android kernel compiling .
I followed the guideline which is
https://sites.google.com/a/android.com/opensource/download
and searched google for the answer, but still it cannot be solved.
===
Cannot locate File/ Basename.pm in @INC
( @INC
This would be very interesting. Any word on timing?
Cheers,
Filipe
markgross wrote:
We have been looking into this and we are in the process of internal
legal review and will be starting an AndroidOnIA project within the
context of the Android open source project soon.
We have a few
Hi David,
Think you for your answer.
I'm sorry for my copypaste mistake.
I can compile with TARGET_SIMULATOR=true without any problem.
but when set TARGET_SIMULATOR=false in compile command, error below
happend
make: *** No rule to make target `out/host/linux-x86/bin/emulator',
needed by
I just mean that it's the only option that has really been tested in real
life :-)
On Thu, Nov 13, 2008 at 9:39 AM, Gergely Kis [EMAIL PROTECTED] wrote:
Hello,
Why is flash storage necessary? We were able to run Android over NFS,
and others have used ext2 or ext3. So there should be no
71 matches
Mail list logo
