Hi All,
As with what you can see shown in the column of "Subject", for
android's part how is the underlying RIL combined GSM with CDMA,
implemented to simultaneously talk to two modems, namely GSM and CDMA
in the same phone?
Any hints to the above problem as well as the relative are all really
a
Hi All,
As with what you can see shown in the column of "Subject", for
android's part how is the underlying RIL combined GSM with CDMA,
implemented to simultaneously talk to two modems, namely GSM and CDMA
in the same phone?
Any hints to the above problem as well as the relative are all really
a
I am getting the same error message when I ran the android x86 eeepc
in vmware.
init: Unable to open persistent property directory /data/property
errno: 2
sh: can't access tty: job control turned off
# I/installer( 1975): Waiting for device: /dev/block/sdb2
#
I'm getting a shell prompt.
I canno
I'm trying to copy my dalvik application package to android x86 eeepc
running in vmware.
adb does not detect any device. I cannot use adb push.
How can I copy my dalvik application package located in my os to
android x86 running in vmware?
Thanks,
Brian
--~--~-~--~~~---
hi Brian:
You are using the installer.img which is used to work as a USB
installer for eeepc, after it installs, it can start the gui
correctly.
--
Chen
On Sun, Mar 22, 2009 at 11:53 PM, Brian wrote:
>
> I am getting the same error message when I ran the android x86 eeepc
> in vmware.
> init
I'm not using vmware. I have a real EEEPC here. So based on my experience on
my EEEPC I have added some comments inline and hope it could help.
On Sun, Mar 22, 2009 at 8:53 AM, Brian wrote:
>
> I am getting the same error message when I ran the android x86 eeepc
> in vmware.
> init: Unable to op
You may need to set the adb target:
under linux:
export ADBHOST=your_vmware_target_ip
under windows:
set ADBHOST=your_vmware_target_ip
then try to start the adb server. if you have already started the
server, you need to kill it firstly by: adb kill-server
If you are using NAT network in VMwar
Worked for me.
Thank you.
On Feb 26, 6:14 pm, wolfmanjm wrote:
> Ok finally figured this out.
>
> If you are using BASH then you must do this...
>
> > unset CDPATH
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://g
Hi Midhun,
I'm having the same problem when I ran android eeepc (I created
installer.img by following the how-to posted in the discussion group)
on vmware. How did you solve the problem?
Thanks,
Brian
On Jan 8, 5:10 am, Midhun wrote:
> Hi,
>
> I have built Android for eee PC using the instruc
Hi,
Alternatively, mount your Android virtual disk with other Linux
virtual machine,
such as Ubuntu VM.
After installing Ubuntu VM, edit the Ubuntu.vmx file to tell your
android image
as second disk. It would look like this;
scsi1.virtualDev = "lsilogic"
scsi1:0.present = "TRUE"
scsi1:0.fileName
Thanks, Chen.
I'm trying to do option 1 shown below.
I'm getting the following error
"Error 1: Filename must be either an absolute pathname or blocklist".
How can I solve this problem?
Also, I have been using vmware fusion. I'm also trying vmware
workstation on windows.
Thanks,
Brian
On Jan 9,
If the bluetooth is build as module not build in, where is better to
insmod it?
I'm thinking of insmod( including some other bt init steps, e.g.
setting the pskey for csr chip) and rmmod in the bt_enable and
bt_disable in ./system/bluetooth/bluedroid/bluetooth.c.
But I'm not sure it's the best lo
I think you probably need revise the Android.mk under folder
alsa_sound, though I am not sure how.
If you solve the problem,please let me know how.
在2009-03-20，virstud 写道：
>
>how long wait?
>
>On 20 мар, 16:35, Sean McNeil wrote:
>> There are major updates being merged into cupcake. You'll hav
here is how I ported alsa and there is still mistakes
1:git alsa_sound
$git clone git://android.git.kernel.org/platform/hardware/alsa_sound.git
2:mv alsa_sound libaudio-alsa
3: I copied the file AudioHardware* from framework/base/libs/audioflinger to
hardware/libaudio-alsa
4: revise Android.mk und
There is absolutely no point in using ALSA with the current repo. I have
the changes required, but it will break builds that actually work. If
you used my changes, then you'll just end up with openCORE issues after
that. So, I will submit them once the repo is again made whole.
susanner wrote:
So, currently, I can not rely on repo or git to build alsa , right? if it's ok,
would you please let me know ? Actually I am porting mediaplayer but there is
no sound .
在2009-03-23，"Sean McNeil" 写道：
>
>There is absolutely no point in using ALSA with the current repo. I have
>the changes req
Currently you cannot rely on repo or git to build Android. Period.
susanner wrote:
> So, currently, I can not rely on repo or git to build alsa , right? if
> it's ok, would you please let me know ? Actually I am porting
> mediaplayer but there is no sound .
>
> 在2009-03-23，"Sean McNeil" 写道：
>
The following posts from Chen helped me greatly. Just followed steps listed
by Chen and I could run Android in VirtualBox.
- Avtar
You may be able to reference these posts:
Create the installed image directly from the source:
http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3?pli=
Jackie,
The i915_drv.c only exists in bsd-core. And the patches in vendor/asus/
eee_701/modules doesn't match with i915 driver.
I can't even find the i915 driver with modeset supports 2.6.27, and
only later version.
Best Regards,
Brian
On Feb 12, 7:26 pm, Jackie Wu wrote:
> Where did you get t
Thanks, Avtar.
I referred to the two links you pointed out to create an android vm running
in vmware.
I tried both installer.img and installed.img, but having problems both in
vmware fusion and vmware workstation.
In vmware workstation, when I tried installed.img, the vm's screen freezes.
When I tr
how can libasound be .so not .a? after make , I can't find libasound in
system/lib
在2009-03-23，"Sean McNeil" 写道：
>
>Currently you cannot rely on repo or git to build Android. Period.
>
>susanner wrote:
>> So, currently, I can not rely on repo or git to build alsa , right? if
>> it's ok, wou
Hi Dianne,
Here r ur answers:
1. What resolution and density is your development board running at?
Pixel Density, I not too sure! Resolution is 320(length)x240(breadth) at
16bpp
2. What resolution and density are you running the emulator at? (If you are
not specifying anything special, this is p
There is no libasound.so. It is built as libasound.a and included whole
into libaudio.so.
susanner wrote:
> how can libasound be .so not .a? after make , I can't find libasound
> in system/lib
>
> 在2009-03-23，"Sean McNeil" 写道：
> >
> >Currently you cannot rely on repo or git to build Android. P
23 matches
Mail list logo
