i remembered that init.rc would invoke some script under /system/etc/
add a line under that:
netcfg eth0 dhcp
you may also assign eth0 with ifconfig in that script.
if you are referring to 169.xx like private ip, you can specify similar ip
on your host side to get communicatation with your target.
have you specified the vesa mode support with vga=785 or so?
the console looks like in generic text mode.
--
Chen
On Sat, Aug 21, 2010 at 9:49 AM, Mitchell Lee mitchell.kw@gmail.comwrote:
Hello.
I hope you give me some advice for me.. thank you for your time in advance.
I'm using
This thread may give some hints:
http://groups.google.com/group/android-porting/msg/64eb5a0158e6b815?dmode=source
The system server is parsing some vars to to values, while in your init.rc,
it hasn't specified it.
You can check ActivityManagerService.java:1303 for more information.
--
Chen
On
hi All:
Is there any known good approach to disable the trace-jit for installed
application on non-rooted phone?
I read the document in dalvik direcotory, it states that via setting
property of dalvik.vm.execution-mode can achieve the goal. But it doesn't
seem to work.
Also read the document that
Dianne:
Thanks a lot! Very helpful.
--
Chen
On Sat, May 15, 2010 at 3:02 AM, Dianne Hackborn hack...@android.comwrote:
On Wed, May 12, 2010 at 7:40 AM, Chen Yang sunsety...@gmail.com wrote:
Cool! Would you like to share some insights on what makes the preloading
and scan so efficient
, Chen Yang sunsety...@gmail.com
mailto:sunsety...@gmail.com wrote:
Cool! Would you like to share some insights on what makes the
preloading and scan so efficient on Nexus One? Fast CPU + fast
flash? Which one is more important? Or both?
There is nothing so special about
Cool! Would you like to share some insights on what makes the preloading and
scan so efficient on Nexus One? Fast CPU + fast flash? Which one is more
important? Or both?
Thanks.
--
Chen
On Tue, May 11, 2010 at 6:31 AM, Dianne Hackborn hack...@android.comwrote:
There is no trivial way to reduce
Have you put the vmdk file together with the installer.img and be sure that
the installer.img can be accessed by current user. I cannot see obvious
problem in your steps in creating the vmdk. Hope it helps.
--
Chen
On Wed, Sep 30, 2009 at 3:15 PM, Rakesh Kumar rakesh.y...@gmail.com wrote:
Hi,
I guess it is a permission problem:
According to the source:
mArchiveSourcePath = sourceFile.getPath();
if (!sourceFile.isFile()) {
Log.w(TAG, Skipping dir: + mArchiveSourcePath);
mParseError = PackageManager.INSTALL_PARSE_FAILED_NOT_APK;
return
You may be able to reference my post in this thread for the fix:
http://groups.google.com/group/android-porting/browse_thread/thread/b87d6c96a16af57d/a0461561a68c6e24#a0461561a68c6e24
On Tue, Aug 11, 2009 at 11:49 PM, Sergej Pupykin pupyk...@gmail.com wrote:
logcat log contains:
I have used android on x86 system with HT.
--
Chen
On Fri, Jan 9, 2009 at 1:21 AM, Simon Braunschmidt
simon.braunschm...@gmail.com wrote:
Hi
I am currently researching possibilities to run android on SMP. Would
there be any blocking points that immediately come to your mind?
Since
for Android 1.5 r3 for x86 images, is there a way to
get
this?
Thanks
P
On Aug 3, 5:38 am, Chen Yang sunsety...@gmail.com wrote:
try Yi Sun and Chih-wei's work on android-x86:
http://code.google.com/p/android-x86/
They have done some great work
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. At least
try Yi Sun and Chih-wei's work on android-x86:
http://code.google.com/p/android-x86/
They have done some great work for android on x86.
--
Chen
On Mon, Aug 3, 2009 at 7:54 PM, vishal bhoj vishalb...@gmail.com wrote:
Hello Everyone,
I saw the livedroid image for x86 machine at
beyo...@gmail.com wrote:
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
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.
Cool!
Any explanation on why it doesn't show on ARM platform?
--
Chen
On Thu, Jul 9, 2009 at 1:26 AM, fadden fad...@android.com wrote:
bhayes has posted an explanation of the problem in the change (https://
review.source.android.com/#change,10482).
In short, it can cause live objects to be
you can follow the patch posted there:
http://code.google.com/p/patch-hosting-for-android-x86-support/
--
Chen
On Tue, Jul 7, 2009 at 12:46 AM, androidfan vaishali.kara...@gmail.comwrote:
Hi,
I am trying to build android for eee 701 with the following host
system configurations:
heap.
one case I remembered:
IS_CLASS_FLAG_SET(clazz, CLASS_ISARRAY) in scanObject: caused segfault
Any plan to introduce the precise GC soon? Thanks.
--
Chen
On Wed, Jul 8, 2009 at 1:49 AM, fadden fad...@android.com wrote:
On Jul 7, 10:41 am, Chen Yang sunsety...@gmail.com wrote:
just
NTFS
partitions.. is it possible that the size or format of these is
causing an issue?
On Jun 29, 6:23 pm, Chen Yang sunsety...@gmail.com wrote:
it looks like that the installer is waiting for the second partition
on
the
usb drive.
You can check the paritions via looks
but now
with a clean build it works fine. It seems for HDD models of the
eeePC you may have to change the IDE mode in BIOS from Enhanced to
Compatibility.
Thanks for your help guys, it's been a great learning experience!
Bruce
On Jul 1, 12:52 am, Chen Yang sunsety...@gmail.com wrote:
oh
it looks like that the installer is waiting for the second partition on the
usb drive.
You can check the paritions via looks into:
/dev/block/
try to list the nodes under that directory.
if you have the installer.img dd-ed on your usb drive, it should have 2
paritions. Don't know the detail of
In short, no. I think lots of android on x86 have the data partition as
ext2, it works correctly.
--
Chen
On Mon, Jun 22, 2009 at 9:04 PM, thomasbl thoma...@debroid.org wrote:
On Jun 19, 7:14 pm, Chen Yang sunsety...@gmail.com wrote:
It looks like that you haven't mounted the /data
I have raised the question about 5 months ago:
http://groups.google.com/group/android-porting/browse_thread/thread/f34d9ff618f8fc50/5dcd265cd2b7e126?pli=1
While no response.
Only google can do the that porting.
--
Chen
On Tue, Jun 16, 2009 at 1:33 PM, Yi Sun beyo...@gmail.com wrote:
what does
-06-16 at 14:20 +0800, Chen Yang wrote:
I have not met this kind of problem. I have successfully used the
pcnet-pci card, also well as the e1000 desktop card with original
2.6.25 kernel. I don't know whether the new kernel doesn't work well.
And from the config you provided, I cannot tell
into a wiki page.
Yi
On Tue, 2009-06-16 at 14:35 +0800, Chen Yang wrote:
oh, after the virtualbox restarts its kernel, you'd better repeat the
adb kill-server and adb devices to let it scan for it.
Otherwise, adb may not be able to find it.
--
Chen
2009/6/16 GrainWang wlc
, there is
always No media found, even when I insert a mini sd card and a usb
disk which both contain the test clips.How to let the test clips
avaiable in virtual box? Thanks in advance!
On 6月15日, 上午11时44分, Chen Yang sunsety...@gmail.com wrote:
hi, Grain:
It's available in the built
several test clips in the /sdcard path, the
gallery still prompt No media found, does you know the reason? And
how can I do to make the clips availble in the virtual box?Thanks!
On 6月15日, 下午3时32分, Chen Yang sunsety...@gmail.com wrote:
Oh, the ethernet card driver should match the network
ChenYang:
Can you kindly tell me the detailed path in make menuconfig for
choosing CONFIG_PCNET32 or e1000 driver, I enabled everything in
network support and Devices drivers-Network device support, but
I can't find the configuration you mentioned. Thanks!
On 6月16日, 上午11时03分, Chen Yang
How about trying adb push? It needs the network being configured properly,
you may need to compile the kernel supports the virtual ethernet card that
virtualbox emulates.
--
Chen
2009/6/15 GrainWang wlc...@yahoo.com.cn
HI Sammy:
Thanks! Is there any way to add files in virtuabox after the
? do I still need something tools and where's
the link? Thanks!
On 6月15日, 上午10时27分, Chen Yang sunsety...@gmail.com wrote:
How about trying adb push? It needs the network being configured
properly,
you may need to compile the kernel supports the virtual ethernet card
that
virtualbox emulates
to
try it out.
Yi
On Thu, 2009-05-21 at 12:24 +0800, Chen Yang wrote:
My guess is the surface transaction related handling caused the
recomputation of the whole screen. I have observed with the diaglo on,
system_server used lots of cpu time.
So we may need to find some better approach
have you specified the vga=788 in the cmdline? The vesafb can only be
started when booting up.
--
Chen
On Wed, May 20, 2009 at 2:13 PM, Alex alex@gmail.com wrote:
I have installed android x86 eee_701 in VirtualBox successfuly.
But the steps seem too repeated when I try to replace a
Cool!
have you applied the Jackie's alarm related patch in the kernel?
--
Chen
On Thu, May 21, 2009 at 7:55 AM, Yi Sun beyo...@gmail.com wrote:
BTW-- I have confirmed that 2.6.29 kernel works with Android on x86. I
can boot up Android without any problem even I did not test any devices
yet.
The mouse cursor works! Thanks to Yi for your great work! :)
I also observed the same as Chih-wei, if there are some dialog appears,
the mouse cursor responds very slowly. To have a try, you can just try in
the home screen, long press the mouse and then one dialog will pop up, then
you can try
qemu command.
qemu -kernel bzImage -initrd rootfs.cpio.gz -hda system.img -dhdb
userdata.img -append console=tty0 console=ttyS1,115200n8 console=tty0
androidboot.hardware=eee_701 vga=788
On May 21, 9:54 am, Chen Yang sunsety...@gmail.com wrote:
have you specified the vga=788 in the cmdline
is the repository? Please let me know. Many thanks for the help
On 5月21日, 上午10時09分, Chen Yang sunsety...@gmail.com wrote:
Cool!
have you applied the Jackie's alarm related patch in the kernel?
--
Chen
On Thu, May 21, 2009 at 7:55 AM, Yi Sun beyo...@gmail.com wrote:
BTW
-forum.ipi.fi/viewtopic.php?f=10t=3913
On May 21, 10:41 am, Chen Yang sunsety...@gmail.com wrote:
AFAIK, qemu doesn't support the vga= option with append,
You may need to patch the qemu for that option:
http://lists.gnu.org/archive/html/qemu-devel/2007-02/msg00269.html
Hope it helps
correct, need to
dig more when have time.
2009/5/20 Chen Yang sunsety...@gmail.com
The mouse cursor works! Thanks to Yi for your great work! :)
I also observed the same as Chih-wei, if there are some dialog appears,
the mouse cursor responds very slowly. To have a try, you can just try
This discussion may be helpful:
http://groups.google.com/group/android-porting/browse_thread/thread/e3070a43b8565642/da900ba4acaa05a6?lnk=gstq=chroot#da900ba4acaa05a6
--
Chen
On Sun, May 17, 2009 at 2:10 PM, Vaidya vaidya...@gmail.com wrote:
Hi..
Is there anybody who has tried running an
a little disappointed.
Though I'm still new to android,
I think is *not* as open as it declared to be.
That's all the feeling I can say up to now.
On 5月11日, 下午12時00分, Chen Yang sunsety...@gmail.com wrote:
How about submitting one or two patches to the specific project for
comments? Then we
boot into a console. Which seems to mean it probably
isn't related to the fb. H.
On May 8, 9:36 pm, Chen Yang sunsety...@gmail.com wrote:
would you like to provide thelogcatinformation? it may not be the fb
related according to your description.
--
Chen
On Sat, May 9, 2009 at 5:17
:
Is there anyway to get thelogcatinformation without access to
anything. I can't boot into a console. Which seems to mean it probably
isn't related to the fb. H.
On May 8, 9:36 pm, Chen Yang sunsety...@gmail.com wrote:
would you like to provide thelogcatinformation? it may not be the fb
:
Is there anyway to get thelogcatinformation without access to
anything. I can't boot into a console. Which seems to mean it
probably
isn't related to the fb. H.
On May 8, 9:36 pm, Chen Yang sunsety...@gmail.com wrote:
would you like to provide thelogcatinformation
For the ethernet, you can compile the driver in the kernel, it shall work.
For wireless, you may need some extra effort, you may try the
ndiswrapper approach. Don't know whether it now has some better
support in linux.
--
Chen
On Sun, May 10, 2009 at 10:51 PM, Kent Loobey k...@uoregon.edu
library (libgps_serial outside
libhardware_legacy) it was not working
* using code written within the libhardware_legacy, it is working
On 10 Mag, 17:43, Chen Yang sunsety...@gmail.com wrote:
Why not push the code to android open source? Have you tried to push some?
--
Chen
On Sun, May 10
have battery service (Dianne has gave
some suggestions), wakelock, wifi.
All these are platform specific changes.
Yi
On Sun, 2009-05-10 at 23:43 +0800, Chen Yang wrote:
Why not push the code to android open source? Have you tried to push
some?
--
Chen
On Sun, May 10, 2009 at 4
my 2 cents, but i am not so sure whether it works or not.
You may be able to achieve it by removing the vga=788 in cmdline to
disable the vesafb and let android directly use the only fb device.
--
Chen
On May 4, 10:56 pm, Cloud cgw...@gmail.com wrote:
Hi everyone,
I can use vesafb for intel
That may have some relationship with the incorrect video mode.
Are you using android on eeepc? Can you use network? If yes, you can
use adb to connect to it by poiting the ADBHOST to the ip that your
target machine has.
--
Chen
2009/5/5 Cloud cgw...@gmail.com:
Thanks for your suggestion,
I
to solve
it
Anyway, thanks,
Frank
On Apr 25, 6:06 pm, Chen Yang sunsety...@gmail.com wrote:
You may be able to reference the init.rc to see which partition is
mounted as /data( by default it seems to be /dev/block/sda8), do you
have the right partition and file system type(ext3
if
something will change, but nothing.
Obviously, there is some problem with SurfaceFlinger / GUI
initialization, maybe because I'm running it under VirtualBox? Is
there any special FB or video driver to be compiled into the Kernel?
Frank
On Apr 26, 10:24 am, Chen Yang sunsety...@gmail.com
You may be able to reference the init.rc to see which partition is
mounted as /data( by default it seems to be /dev/block/sda8), do you
have the right partition and file system type(ext3)?
--
Chen
On Sat, Apr 25, 2009 at 11:57 PM, FrankieCZ franki...@centrum.cz wrote:
Hi all,
I've tried to
output is
[ 165.505690] init: /init.rc: 183: invalid option 'enabled'
[ 167.114261] init[1230]: segfault at 0020 eip 0804be00 esp
bffde7c0 error 6
On Apr 19, 10:00 pm, Chen Yang sunsety...@gmail.com wrote:
have you used the android kernel on your host?
--
Chen
On Mon, Apr 20, 2009
patch, then there maybe a typo in the init.rc
added by me under the line for adbd. If that is the case, just remove
the enabled. But it is unlikely to cause the segfault.
Yi
On Tue, 2009-04-21 at 08:39 +0800, Chen Yang wrote:
Your init.rc seems to have problem at lne 183, i don't know whether
You can copy all the out/target/product/eee_701/root directory to one
directory, say /home/android
cp -raf out/target/product/eee_701/root /home/android
cp -raf out/target/product/eee_701/system /home/android
cp -raf out/target/product/eee_701/data /home/android
before chroot, try to add chmod -R
] Bulk In Failed. Status=-71, BIIdx=0x4, BIRIdx=0x4,
actual_length= 0x0
[ 1399.669726] init[10339]: segfault at 0020 eip 0804be00 esp
bfdc0c90 error 6
[ 1402.741197] init[11162]: segfault at 0020 eip 0804be00 esp
bfe234f0 error 6
On Apr 19, 7:01 pm, Chen Yang sunsety...@gmail.com wrote
the output doesn't seem to be errors. please provide the error related messages.
--
Chen
On Sat, Apr 18, 2009 at 9:05 AM, penguins suf...@gmail.com wrote:
Thank you Yi,
Applied the patched (I applied some of the cursor patch manually).
The building process stopped halfway and I got these
( 2126): LinearAlloc 0x0 used 2087468 of 4194304 (49%)
D/skia ( 2126): purging 6K from font cache [1 entries]
Any suggestion?
Thanks,
Brian
On Apr 1, 5:13 pm, Chen Yang sunsety...@gmail.com wrote:
Cool. It seems that you don't have the essential
address.
In my phone, I'm using an terminal emulator I downloaded from the
market...
Thanks,
Brian
On Apr 1, 9:13 pm, Chen Yang sunsety...@gmail.com wrote:
hi Brian:
You may need to modify the framework/base/preloaded-classes
for android be on a separate partition? So instead of grub
being in /boot/grub, can it be in sda1 and which in turn load android
present in /sda2 ?
Thanks,
Gowtham
On Apr 2, 12:13 am, Chen Yang sunsety...@gmail.com wrote:
hi Brian:
You may need to modify the framework/base/preloaded-classes
on the instructions posted by Lim and Chen
Yang
in the list. Please let me know if I missed anything and made
anything
wrong.
I hope that we can have a central place to capture all the known
issues
and solutions/patches so that people can feel easier on their life
in the batteryservice (See my
another brain damage patch).
Now I open for suggestions. Please give your thoughts.
Yi
On Wed, 2009-04-15 at 21:36 +0800, Chen Yang wrote:
yeah, you may need to remove those classes in
frameworks/base/preloaded-classes
--
Chen
On Wed, Apr 15, 2009 at 10:55 AM
You need to rebuild the kernel to enable the vesafb is you want to run
in Virtualbox.
the android power message is not an issue, neither the cannot access tty
--
Chen
On Wed, Apr 8, 2009 at 3:12 PM, choo75 cho...@gmx.at wrote:
Hello all,
I tried to get Android running in a VirtualBox
hi,you may reference this thread for more information on the issues
with current most updated source:
http://groups.google.com/group/android-porting/browse_thread/thread/66862bdb52dac936/358ad1beccc811f0#358ad1beccc811f0
basically, i guess there are some issues like:
1) battery service with
))
.setWindowManager(wm);
After starting the Battery Service, it's not starting the Window
Manager.
I still don't got it figgered out.
On 31 mrt, 16:45, Chen Yang sunsety...@gmail.com wrote:
It looks like AppWidget service is causing issues, the NPE seems to be
the fatal error. May need some
): LinearAlloc 0x0 used 2087468 of 4194304 (49%)
D/skia ( 2126): purging 6K from font cache [1 entries]
Any suggestion?
Thanks,
Brian
On Apr 1, 5:13 pm, Chen Yang sunsety...@gmail.com wrote:
Cool. It seems that you don't have the essential process: zygote. You
can check the logcat messages
am sure at this point is utterly broken.
On Wed, Apr 1, 2009 at 9:13 PM, Chen Yang sunsety...@gmail.com wrote:
hi Brian:
You may need to modify the framework/base/preloaded-classes to
remove those non existing classes.
And you can reference Androidphan's reply in this thread.
You may
Thanks for let us know your plan. Then would you like to share the
anticipated date for the refactored code?
Thanks.
--
Chen
On Thu, Apr 2, 2009 at 1:46 PM, Dianne Hackborn hack...@android.com wrote:
On Wed, Apr 1, 2009 at 10:41 PM, Chen Yang sunsety...@gmail.com wrote:
Yes, eee_701
Tha seems to be from the mismatch of the eee_701's policy profile, you
can remove those classes in frameworks/base/preloaded-classes or
replace them with Mid related classes, and rebuild the image.
--
Chen
On Tue, Mar 31, 2009 at 4:51 PM, Androidphan niels.kee...@tass.nl wrote:
I'm getting the
, no checkin service
I/Process ( 2238): Sending signal. PID: 2238 SIG: 9
I/ServiceManager( 2076): service 'SurfaceFlinger' died
I/ServiceManager( 2076): service 'power' died
I/Zygote ( 2237): Exit zygote because system server (2238) has
terminated
On 31 mrt, 11:23, Chen Yang sunsety
Would some one from google give some comments on the removal the build
of e2fsprogs? Will the incomplete removal in
bootable/diskinstaller/config.mk be fixed?
It seems to me that e2fsprogs is not necessary for normal running, but
you may need those utilities like e2fsck, tune2fs for maintanance
: 2543 SIG: 9
I/ServiceManager( 2076): service 'batteryinfo' died
I/ServiceManager( 2076): service 'usagestats' died
more services died...
Is the problem here at the BatteryService?
On 31 mrt, 11:51, Chen Yang sunsety...@gmail.com wrote:
The problem comes from the lack update in init.rc on x86
find '/system/bin/mountd', disabling 'mountd'
sh : can't access tty: job control turned off
[time] warning: 'app_process' uses 32-bit capabilities (legacy support
in use)
How can I fix it? It's hard to pinpoint what to do.
Thanks,
Brian
On Dec 28 2008, 1:40 am, Chen Yang sunsety
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 bgc...@gmail.com wrote:
I am getting the same error message when I ran the android x86 eeepc
in
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
3, 4:52 pm, Chen Yang sunsety...@gmail.com wrote:
hi Zia:
It's not in the kernel, it's in thebusybox. You can download the
BusyBoxsource and config it using make menuconfig.
--
Chen
On Wed, Feb 4, 2009 at 8:46 AM, Zia zia.cha...@gmail.com wrote:
I'm looking
\
drm.ko \
i915.ko
..
Add you modules in that list.
Hope it helps!
--
Chen
On Thu, Mar 5, 2009 at 6:19 PM, ehung1...@gmail.com ehung1...@gmail.com wrote:
Hi chen Yang
I still have a question about adding modules to compile the kernel
when we select the M option in make menuconfig
oh, you are using the installer.img to boot with normal boot, that is
impossible. Since the installer.img only contains 2 partitions. it
doesn't have the (hd0,2) partition as the installed system. You can
reference my post in this thread for the information on building the
image that can be used
Yes. You can follow the discussion on compilation for VMWare target to
build Android for a common PC.
--
Chen
On Thu, Feb 19, 2009 at 9:42 PM, MacknZ ymm...@gmail.com wrote:
Is it possible to run android on a common PC (x86) ?
On 1月10日, 下午9时11分, Lim,GeunSik lee...@gmail.com wrote:
Hi, all
succeed running android in qemu , but failed running in vmware.
In my vmware, androidboot run well until the cmdline output eth0 :
link up , and then stop boot.
After that , I can just input cmdline in it.
Do you meet this problem , how to slove it ?
Thanks!
On 1月14日, 下午8时54分, Chen Yang
DJ:
You can reference the information from the thread:
http://groups.google.com/group/android-porting/t/66862bdb52dac936
Hope it helps!
--
Chen
On Thu, Feb 12, 2009 at 9:25 PM, dhananjay dhananjayingr...@gmail.com wrote:
Hi All,
I want to build android on my linux x86 core 2
be too old :)
Do you kown where is sda6 setting ? In which config file?
I will try you suggestion
3x
On Mon, Feb 9, 2009 at 12:48 AM, Chen Yang sunsety...@gmail.com wrote:
hi, I don't know whether the modification to sda has been already
flushed to the virtual disk of VMWare. The safe way
you suggestion
3x
On Mon, Feb 9, 2009 at 12:48 AM, Chen Yang sunsety...@gmail.com wrote:
hi, I don't know whether the modification to sda has been already
flushed to the virtual disk of VMWare. The safe way seems to issue the
command: reboot in the console. Meanwhile, i have no idea on whether
...@gmail.com wrote:
Dear Chen
I meat no sda6 problem.
print this error
E/diskutils(1752):Could not open '/dev/block/sda6' for read/write
(errno = 2)
I follow you flow , reboot vm ,but the same error.
Did I miss do something ?
On 2008年12月28日, 下午4时40分, Chen Yang sunsety...@gmail.com wrote
Are you trying to install android to the usb disk itself?
I remembered that the target is specified as /dev/block/sda in the
installer.img. So you are using the sda as both the source and the
destination at the same time, which seems to problematic.
If you want to build live usb, you can use
AFAIK, the -p specifies the source of the parition where installation
related files locate.
Installation destination is specified in the /system/etc/disk_layout.conf
the path section, by default:
device {
path /dev/block/sda
...
}
Thus it installs to /dev/block/sda
Then in your case, you
It looks that your configuration in grub is incorrect.
You can modify it according to the reported sdb:
/boot/grub/menu.lst:
kernel /boot/kernel root=/dev/sdb2 rootdelay=6 rw ...
Or use the make-live script to build the usb book disk again, by
selecting 1 or default when promting How many disks
Just fyi, i have successfully compiled the sample application for x86
target and run successfully with some similar modifications. :)
--
Chen
On Fri, Jan 23, 2009 at 3:29 AM, kozak c.a.subraman...@gmail.com wrote:
Hi all,
I am trying to compile and execute the simple hello world native app
I found that gears is missing for android on IA, visiting gears.google.com,
it says:
Your browser is not currently supported. Please check the list of supported
browsers below.
While for the emulator provided by google, it shows: Gear is installed.
Current version:0.5.2.0
When will the gears.so
the bzImage to vendor/asus/
eee_701/kernel and used the $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701
DISABLE_DEXPREOPT=true make -j2 installer_img to build the
installer.img.
Do i need to just compile as target_product=x86? and not use the asus
files?
Thanks,
Gowtham
On Jan 21, 1:01 am, Chen Yang
/data/mnt
if not, you need to resize that partition using resize2fs.
--
Chen
On 1/21/09, Chen Yang sunsety...@gmail.com wrote:
Would you like to provide related dmesg info? You can just print the lines
leading with vesafb.
--
Chen
On Wed, Jan 21, 2009 at 9:19 PM, gowtham gowda gowth
try to build it again without the -j 2 option:
$TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make
installer_img
See whether it helps or not.
--
Chen
On Wed, Jan 21, 2009 at 1:12 PM, poppa popp...@gmail.com wrote:
After following the directions, I have these error messages.
]: segfault at 38 ip 80110cf9 sp
b5cde00c error 4 in libc.so[8010+49000]
6[ 61.437928] SurfaceFlinger[2093]: segfault at 38 ip 80110cf9 sp
9e18200c error 4 in libc.so[8010+49000]
any ideas?
Thanks,
Gowtham
On Jan 14, 7:58 am, Chen Yang sunsety...@gmail.com wrote:
I haven't tried to add
Hi Mathias:
Just interested to know, what's the relationship between surfaceflinger
and pixelflinger?
Meanwhile, is there some document on sufraceflinger and pixelflinger?
Thanks.
--
Chen
On Sat, Jan 17, 2009 at 5:58 AM, Mathias Agopian pixelflin...@google.comwrote:
On Fri, Jan 16,
, you may need to compile
the rtl8139 driver.
If you want to use ext3, please apply tune2fs -j your.img.
Enjoy!
--
Chen
On Sun, Jan 11, 2009 at 11:36 AM, Chen Yang sunsety...@gmail.com wrote:
It looks like that you are missing the vga=788 option, you can
reference my post:
http
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
Can you check whether eth0 exist or not by issuing: netcfg?
If it exisits, you can try:
#netcfg eth0 dhcp
Hope it helps!
--
Chen
On Mon, Jan 12, 2009 at 9:10 PM, Wing winghui...@gmail.com wrote:
I can run the live-USB image on my EeePC, but the Ethernet seem not
work. Is there anyone has
One potential start is to try to use eeepc's branch and together with
Chris's make-live script:
http://code.google.com/p/android/issues/detail?id=1598
You can reference this thread for build the installer_img:
http://groups.google.com/group/android-porting/t/66862bdb52dac936
and then you
Some additions to build the kernel for VMWare/VirtualBox:
Hope it helps:
$cd mydroid
$cp vendor/asus/eee_701/kernel.config kernel/.config
$cd kernel
$make menuconfig
Select the device drivers:
For network card:
network device support -
Ethernet (10 or 100Mbit) ---
[*] EISA, VLB,
.
Thanks,
gowthsm
On Jan 9, 11:44 pm, Chen Yang sunsety...@gmail.com wrote:
Sorry, I forgot to put the required information to that step:
After that, you should save the .config
$make bzImage
Then copy the kernel to vendor/asus/eee_701
$cp arch/x86/boot/bzImage ../vendor/asus/eee_701/kernel
1 - 100 of 108 matches
Mail list logo
