I missed that one totally. Now, I can see wpa_supplicant in included
in the build. Thank you Yi Sun!
On May 4, 5:55 pm, Yi Sun beyo...@gmail.com wrote:
Have your try
WPA_BUILD_SUPPLICANT := true
In the wpa_supplicant/Android.mk ?
Yi
On Mon, 2009-05-04 at 17:07 -0700, penguins wrote:
Hi,
I've followed all the instructions to build Adnroid to include Wifi
and sound and run all the patches. However, wpa_supplicant is still
not included the in the build and sound is still not working =(.
Here are the config that I include to build Android:
Wifi
1. Add
http://code.google.com/p/patch-hosting-for-android-x86-support/
Try this first link first, you can post your questions here
On Sat, May 2, 2009 at 11:43 PM, wimbet wim...@gmail.com wrote:
Hi, I did a search but couldn't find an exact answer. Is there a good
guide or any pre built Android
Thank your advice, Yi.
I search and reference others articles.
Changing the input device mode to 0666, and now touch is work.
But the point coordinate isn't right, it always appears on left-upper
location.
And this method (change the mode to 0666) is also brute force method.
Anyone can directly
I'm working for a company and Politecnico di Torino. We are trying to
use repo/git for cvs.
I'll tell you something more in next weeks.
On 20 Apr, 16:17, sathish-siso sathish...@gmail.com wrote:
Hi
Can you share the porting steps or procedure?
Regards,
Sathish.
On Apr 2, 9:05 am, Brian
Hi,
I am a newbie trying to run android on x86 environment.
I have follow the instructions and apply the patch.
Then i succeed running android on the vmware (but still no cursor
support).
BTW, now I try to add one usb touchscreen device to android.
The linux kernel load the usbtouchscreen
I can not remember it, but somewhere you need to change the permission
for your device node
On Tue, 2009-04-21 at 20:04 -0700, sparq wrote:
Hi,
I am a newbie trying to run android on x86 environment.
I have follow the instructions and apply the patch.
Then i succeed running android on the
Hi
Can you share the porting steps or procedure?
Regards,
Sathish.
On Apr 2, 9:05 am, Brian bgc...@gmail.com wrote:
The system is trying to run zygote, but I got the following error.
I'm attaching my logcat output.
E/Zygote ( 2126): Zygote died with exception
E/Zygote ( 2126):
I just downloaded Android from Android git repository (04/17/09). It
compile properly and I manage to install it to my eee pc 701 (followed
all the instructions). However, when it boot it keeps on giving lots
of the following message:
[ 14.557165] android_power: wakeup (0-0) at 14681420744
Please send you logcat output
On Fri, 2009-04-17 at 13:40 -0700, penguins wrote:
I just downloaded Android from Android git repository (04/17/09). It
compile properly and I manage to install it to my eee pc 701 (followed
all the instructions). However, when it boot it keeps on giving lots
of
Hi Yi,
Here is the output of my logcat:
D/DHCP( 1906): = DHCP message:
D/DHCP( 1906): op = BOOTREQUEST (1), htype = 1, hlen = 6, hops = 0
D/DHCP( 1906): xid = 0x751c secs = 0, flags = 0x8000 optlen =
14
D/DHCP( 1906): ciaddr = 0.0.0.0
D/DHCP( 1906): yiaddr = 0.0.0.0
make sure you have all the patches posted on
code.google.com/p/patch-hosting-for-android-x86-support
On Fri, 2009-04-17 at 15:07 -0700, penguins wrote:
Hi Yi,
Here is the output of my logcat:
D/DHCP( 1906): = DHCP message:
D/DHCP( 1906): op = BOOTREQUEST (1), htype = 1, hlen =
And multiples of the following:
D/AndroidRuntime( 1913): AndroidRuntime START
D/AndroidRuntime( 1913): CheckJNI is ON
D/AndroidRuntime( 1913): --- registering native functions ---
I/Zygote ( 1913): Preloading classes...
D/dalvikvm( 1913): GC freed 763 objects / 40584 bytes in 1ms
D/dalvikvm(
PhoneWindow does not exist. Patch wasn't applied correctly.
On 18 Apr, 00:21, penguins suf...@gmail.com wrote:
And multiples of the following:
D/AndroidRuntime( 1913): AndroidRuntime START
D/AndroidRuntime( 1913): CheckJNI is ON
D/AndroidRuntime( 1913): --- registering native functions
Thank you Yi,
Applied the patched (I applied some of the cursor patch manually).
The building process stopped halfway and I got these messages:
echo '#endif' out/host/linux-x86/obj/EXECUTABLES/
aidl_intermediates/aidl_language_y.h
rm -f out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/
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
would you like to provide the messages before the not responding?
The home application may have met some issues.
--
Chen
On Thu, Apr 16, 2009 at 8:46 AM, Zia zia.cha...@gmail.com wrote:
ok i think I just broke something. The Android HomeScreen doesnt'
respond to keyboard events now. Though I
When did you check out the tree? And which branch is it? Have you
changed anything else? For example, you may have already added some
fixes that patchs will try to fix too.
Yi
On Fri, 2009-04-17 at 18:05 -0700, penguins wrote:
Thank you Yi,
Applied the patched (I applied some of the cursor
Cool!
On Tue, Apr 14, 2009 at 6:54 AM, Yi Sun beyo...@gmail.com wrote:
Sign... I really don't want to post this patch because there are
something I'm not sure about. But I'm really busy with my work now and
have no time to dig more.
If you want, you can take the cursor.patch from
hi Gowtham:
I don't understand your question.
My understand is that grub can be independant with the root file system.
--
Chen
On Wed, Apr 15, 2009 at 7:47 AM, gowtham gowda gowth...@gmail.com wrote:
Hi Chen,
I have a question on creating live bootable usb. Can the gurb
bootloader
:-)
BTW-the hacks I have added can be removed if you have a correct power
driver and batteryservice
On Apr 15, 2009, at 6:28 AM, Chen Yang sunsety...@gmail.com wrote:
Cool!
On Tue, Apr 14, 2009 at 6:54 AM, Yi Sun beyo...@gmail.com wrote:
Sign... I really don't want to post this patch
It works with a usb mouse connected to an eeepc. If you want, send me
an Email with a detailed screenoff issue description. Maybe I can
work on it.
On 14 Apr, 00:57, Yi Sun beyo...@gmail.com wrote:
BTW-- this is a sw cursor.
On Mon, 2009-04-13 at 15:54 -0700, Yi Sun wrote:
Sign... I really
THanks man, I have found out the root cause. If you change the
power.cpp:set_screen_on function to always return true, then no hack is
needed at all. It would not happen in the real env. So go enjoy. BTW--
it works with my touchpad too, as long as you have the correct mouse
driver installed.
On
Brian,
I'm having the similar problem. Did you find a fix for it?
Thanks,
Zia
On Apr 1, 9:05 pm, Brian bgc...@gmail.com wrote:
The system is trying to runzygote, but I got the following error.
I'm attaching my logcat output.
E/Zygote ( 2126):Zygotediedwithexception
E/Zygote ( 2126):
Go to code.google.com/patch-hosting-for-android-x86-support/ to
download all the patches u need
On Apr 15, 2009, at 1:15 PM, Zia zia.cha...@gmail.com wrote:
Brian,
I'm having the similar problem. Did you find a fix for it?
Thanks,
Zia
On Apr 1, 9:05 pm, Brian bgc...@gmail.com
I applied all the patches and now getting libhgl.so errors. How did
you guys resolve this one?
04-15 22:25:29.569: ERROR/GLLogger(2081): couldn't load libhgl.so
library (Cannot find library)
04-15 22:25:29.601: WARN/dalvikvm(2081): threadid=19: thread exiting
with uncaught exception
I do have
setprop ro.HOME_APP_ADJ 4
added to init.rc .
On Apr 15, 3:26 pm, Zia zia.cha...@gmail.com wrote:
I applied all the patches and now getting libhgl.so errors. How did
you guys resolve this one?
04-15 22:25:29.569: ERROR/GLLogger(2081): couldn't load libhgl.so
library (Cannot
It has nothing to do with libhgl. Are you sure that you have applied all
4 patches? It seems that your init.rc is still not right. I can not
access source code now, please double check on the patches if you still
have problem, I maybe able to help you to take a look tomorrow.
Yi
On Wed,
Hi,
I am a newbie trying to get android running on my Eee PC. I have done
everything in the instructions but still unable to get Android
installed.
I boot Eee PC from my USB stick, then I got this text GRUB and it
stays there forever, what did I miss that cause this to happen?
Thank you.
I remember that I add two setprop lines.
Anyway, check the line where it crashed and see what you are missing.
Yi
On Wed, 2009-04-15 at 15:31 -0700, Zia wrote:
I do have
setprop ro.HOME_APP_ADJ 4
added to init.rc .
On Apr 15, 3:26 pm, Zia zia.cha...@gmail.com wrote:
I applied all
Got the keyboard working. The files in /system/usr/keychars were not
0644. chmod 0644 fixes the keyboard. However, the I still dont see
mouse cursor.
Thanks,
Zia
On Apr 15, 4:14 pm, Zia zia.cha...@gmail.com wrote:
You are correct. I was missing
setprop ro.HOME_APP_MEM 4096
in the init.rc .
You are correct. I was missing
setprop ro.HOME_APP_MEM 4096
in the init.rc .
Now I get the new Android UI. However, my keyboard and mouse doesn't
work with the UI. I've Dell USB keyboard and mouse, and in the logcat
I can see the both keyboard and mouse event being fired. However, in
the UI only
ok i think I just broke something. The Android HomeScreen doesnt'
respond to keyboard events now. Though I can Alt+F1 to console and
back. I can see events in the logcat as well. Any ideas? :(
04-16 00:45:52.151: VERBOSE/WindowManager(2037): Event: type=1
data=KeyEvent{action=0 code=0 repeat=0
Hi Chen,
I have a question on creating live bootable usb. Can the gurb
bootloader 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
logcat output please.
Also
And I applied boot_able_img.patch, alarm.patch, e2fsprogs.patch.
Is this a typo or you did not apply frameworks.patch?
Yi
On Sun, 2009-04-12 at 00:05 -0700, shleeforandroid wrote:
Hi Yi.
I've just tested your patch.
EXT2-fs problem is resolved.
but
sh:can't
sorry Yi. I don't know the method to output logcat. Would you tell me
howto please?
I didn't apply frameworks.patch yet.
On 4월12일, 오후4시09분, Yi Sun beyo...@gmail.com wrote:
logcat output please.
Also And I applied boot_able_img.patch, alarm.patch, e2fsprogs.patch.
Is this a typo or you
Hi Yi.
Eureka
I can see Android UI on VirtualBox .
Thanks for your advice
I've not thought the logcat till the end. Your advice is right !!
I could see this message as logcat result.
E/Zygote ( 2124): Class not found for preloading:
com.android.internal.policy.impl.PhoneLayoutInflater
Shlee, thank you for trying this out.
Yes I did not remove these modules from init.rc. And they are harmless
for VB env anyway.
The ext2 errors maybe a concern and it is the first time I see this. I
will see if I can reproduce the same.
The typo in the line 89 of init.rc should be fixed
Just a clarification, if you are using VirtualBOX and WMware, the i915
driver is irrelevant. It does not use it.
On Thu, 2009-04-09 at 07:58 -0700, shleeforandroid wrote:
hi brian
Congratulate your work
I've just reached to some part of your work that is posed On Mar 30,
8:49 am,
There are also some things such as:
build/tools/findleaves.sh (@ line 86)
system/core/mountd/Android.mk (add an if for our target)
external/e2fsprogs/Android.mk (include them for our target - they're
necessary for installer)
vendor/asus/eee_701/BoardConfig.mk (add wifi external)
Hi Brian.Yi
thaks for your early reply.
I've struggled with android 2.6.25 kernel building with modifying some
config option. T.T;;
I did like this to make latest drm module.
aa$ git clone git://anongit.freedesktop.org/git/mesa/drm
aa$ cd
By using vesa framebuffer we have a performance decrase, isn't it?
For me, now it is working with vesa.
I have some troubles compiling modules for specific kernels, cause of
many Makefiles are too complex.
We should put into a project all device driver modules from 3rd party,
specifying which
Agree, as matter fact, I have created a google code page this morning to
host the patches I mentioned in earlier e-mail.
http://code.google.com/p/patch-hosting-for-android-x86-support/
BTW-- I also have mouse cursor support works done. I will post it after
I clean up the code.
Yi
On Thu,
hi Yi.
I have no eeePC.
so, I am testing on just VM.
On Apr 10, 3:24 am, Yi Sun beyo...@gmail.com wrote:
Are you going to run it on the real eee PC target or just a VM?
On Thu, 2009-04-09 at 11:11 -0700, shleeforandroid wrote:
Hi Brian.Yi
thaks for your early reply.
I've struggled
THen you don't need to worry about i915 at all. forget about it, just
make sure you have config the vesa fb correctly as Chen said. And make
sure you have passed in the correct cmdline.
On Thu, 2009-04-09 at 11:36 -0700, shleeforandroid wrote:
hi Yi.
I have no eeePC.
so, I am testing on just
In my case, I'm trying it on a EeePc 701.
I commented out some policy preloaded classes.
Behaviour:
1)boots, then an ANDROID screen (silverish one)
2)seems to reboot the init process, back to point 1
By using Alt+F1 and using logcat, I am obtaining some stuff:
-tries to load libhgl.so (not found)
Thought you have already saw Chen's earlier mail. Here is what I have in
my init.rc. It works for me so far
@@ -108,15 +108,18 @@ on boot
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
+setprop ro.HOME_APP_ADJ 4
setprop
Now, for testing purposes, I'm bypassing BatteryService(cpp) with some
constants in eee target...
On 8 Apr, 02:00, Yi Sun beyo...@gmail.com wrote:
Thought you have already saw Chen's earlier mail. Here is what I have in
my init.rc. It works for me so far
@@ -108,15 +108,18 @@ on boot
2009/4/7 Luca Belluccini lucabellucc...@gmail.com
The AMS issue is due to a property not defined in init.rc file.
HOME_APP_ADJ and HOME_APP_MEM.
I'm trying to give them same values as FOREGROUND APP...
Just for testing, waiting for some info from google engineers...
Make them match the
hi icekolo,
when you got blank screen,
you can press alt + F1 to see more detail message
try dmesg or logcat
On 4月3日, 下午5時08分, icekolo icek...@gmail.com wrote:
Hi all,
I'm a new hand.
My development environments
-OS:Ubuntu 8.04LTS(2.6.24)
-CPU:Intel(R) Pentium(R)4 CPU 3.20GHz
I don't have any solid plan. I was thinking in donut I would just remove
the mid policy. It would then need to be put back by someone in a way that
it can be better maintained.
On Wed, Apr 1, 2009 at 10:59 PM, Chen Yang sunsety...@gmail.com wrote:
Thanks for let us know your plan. Then would
It looks like it ain't the AppWidget service. It gives a NULL pointer
exception in (SystemServer.java:332).
That line says: boolean safeMode = wm.detectSafeMode();
That looks like wm is never created, so this code is never called:
Log.i(TAG, Starting Window Manager.);
wm =
This is why Android is not booting:
I/SystemServer( 6925): Starting Battery Service.
E/BatteryService( 6925): Could not open '/sys/class/power_supply/ac/
online'
E/BatteryService( 6925): Could not open '/sys/class/power_supply/usb/
online'
E/BatteryService( 6925): Could not open
Cool!
Then google has modified the battery service related code.
--
Chen
On Wed, Apr 1, 2009 at 5:15 PM, Androidphan niels.kee...@tass.nl wrote:
This is why Android is not booting:
I/SystemServer( 6925): Starting Battery Service.
E/BatteryService( 6925): Could not open
The system is trying to run zygote, but I got the following error.
I'm attaching my logcat output.
E/Zygote ( 2126): Zygote died with exception
E/Zygote ( 2126): java.lang.IllegalStateException: Missing class(es)
for preloading, update preloaded-classes
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 encounter the NFE and NPE, reference this:
http://groups.google.com/group/android-porting/msg/64eb5a0158e6b815
and
Hi Androidphan,
What paths did you use?
I can't exactly figure out all paths for all the following defs.
AC_ONLINE_PATH
USB_ONLINE_PATH
BATTERY_STATUS_PATH
BATTERY_HEALTH_PATH
BATTERY_PRESENT_PATH
BATTERY_CAPACITY_PATH
BATTERY_VOLTAGE_PATH
BATTERY_TEMPERATURE_PATH
BATTERY_TECHNOLOGY_PATH
Is
Um, those classes certainly should exist. Unless you are trying to build
with the mid policy, which I 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
I'm playing with x86 android in the vmware.
The mouse does not work. Is this the case?
I'm using keyboard. What's the keyboard button that's corresponding to
the menu button on the phone?
Thanks,
Brian
On Apr 1, 9:13 pm, Chen Yang sunsety...@gmail.com wrote:
hi Brian:
You may need to
Dianne:
Yes, eee_701 is using the mid policy at present. And that policy
doesn't seem well maintained.
--
Chen
On Thu, Apr 2, 2009 at 12:42 PM, Dianne Hackborn hack...@android.com wrote:
Um, those classes certainly should exist. Unless you are trying to build
with the mid policy, which I
On Wed, Apr 1, 2009 at 10:41 PM, Chen Yang sunsety...@gmail.com wrote:
Yes, eee_701 is using the mid policy at present. And that policy
doesn't seem well maintained.
It is not maintained at all. Actually I am close to deleting it from the
tree because it is completely not in sync with the
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 is
I'm getting the following error when having built the latest source of
Android for x86:
E/Zygote ( 2124): Class not found for preloading:
com.android.internal.policy.impl.PhoneLayoutInflater
E/Zygote ( 2124): Class not found for preloading:
com.android.internal.policy.impl.PhoneWindow
E/Zygote
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
Thanks, removing the classes in preloaded-classes dit work.
The Android screen is loading now. But now I'm getting the following
errors:
I/SurfaceFlinger( 2238): SurfaceFlinger is starting
I/SurfaceFlinger( 2238): SurfaceFlinger's main thread ready to run.
Initializing graphics H/W...
The problem comes from the lack update in init.rc on x86, you may need
to put those lines in the vendor/asus/eee_701/init.rc.
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
Thanks again. Another problem to start it:
I/SystemServer( 2543): Starting Battery Service.
E/BatteryService( 2543): Could not open '/sys/class/power_supply/ac/
online'
E/BatteryService( 2543): Could not open '/sys/class/power_supply/usb/
online'
E/BatteryService( 2543): Could not open
It looks like AppWidget service is causing issues, the NPE seems to be
the fatal error. May need some extra study on that service.
--
Chen
On Tue, Mar 31, 2009 at 7:41 PM, Androidphan niels.kee...@tass.nl wrote:
Thanks again. Another problem to start it:
I/SystemServer( 2543): Starting
I tried vmware 6.5 workstation on windows 32 bit, vmware 6.5
workstation on fedora core 8 64bit.
Both did not work.
I got where the kernel panic's happening.
kernel 2.6.25 kernel/timer.c:488
int mod_timer(...)
{
BUG_ON(!timer-function) --- here
What can be a fix? Any suggestion?
Thanks,
I got more detailed error messages.
Console: switching to colour frame buffer device 100x37
- [cut here] ---
kernel BUG at kernel/timer.c: 488!
invalid opcode: [#1] PREEMPT SMP
Modules linked in: fbcon i915 drm atl2
pid:0, comm: swapper: Not tainted (2.6.25
Some of your kerenl module is not needed (eg. softcursor..). You have
already built them with your kernel.
On Tue, Mar 31, 2009 at 12:45 PM, Brian bgc...@gmail.com wrote:
Thanks, Chen.
I looked at the kernel 2.6.25 source code. It seems that this kernel
version does not use
Thanks, Yi.
I think I compiled with the following option *Framebuffer console
support.
I will change it to MFramebuffer console support.
This will make sure the kernel does not have the following four
objects.
video/console/Makefile
CONFIG_FRAMEBUFFER_CONSOLE += fbcon.o bitblit.o font.o
My kernel.config will be useless to you. I only run my stuff on eeepc with
i915. But I have seen the similar message as you saw when I rebuild my
kernel. I removed insmod for these modules from the init.rc to avoid these
messages.
On Tue, Mar 31, 2009 at 2:35 PM, Brian bgc...@gmail.com wrote:
i found the problem is that btz the char file under the /system/usr/
keychars haven't the read permission for others yesterday. so i add
the read permission for others and then it can run ok on my laptop.
On Mar 31, 8:40 pm, figofuture figofut...@gmail.com wrote:
i modified the init.rc, it
I encounter the same problem with latest cupcake and main branch, my
CPU is ARM926EJS. I checked SystemServer.java:332, but i don't have
any idea why I got this error message and it cause the VM
(AndroidRuntime) restart again and again. Can any one give some
suggestion?
The kernel and HW isn't
I made a bit more progress.
In system/core/mountd/Android.mk,
#disabled - we are using vold now instead
#include $(BUILD_EXECUTABLE)
So, mountd is not compiled and is not included, but init.rc still uses
mountd instead of vold.
The code base's changing.
I compiled mountd and added it to
Hi Brian,
How did you compile your i915? Did you just copy i915.ko from somewhere
else, becasue I see some version problem. In addition, I didn't see any
CONFIG_i915 stuff in your .config. So, if you copied i915 from somewhere
else, u need to make sure module magic number matches the magic number
Hi Brian,
just type modinfo /path/to/anymodule.ko
compare modinfo output on any kernel ko files in your Android kernel against
i915 from eeepc. In modinfo output, u will read vermagic at last line. You
need to make sure every protperty in i915 vermagic matches vermagic in your
android kernel. Any
On Sat, Mar 28, 2009 at 2:46 PM, Brian bgc...@gmail.com wrote:
Hi Yi,
I tried to boot with or without vga=788. Both attempts are successful.
I assume that you have a typo here and what you really want to say is
unsuccessful.
When you mention changing the framebuffer to vga, do you mean
In your ps, I did not see adbd. If should be abled if
persist.service.adb.enable=1
Yi
On Sun, Mar 29, 2009 at 8:26 AM, Brian bgc...@gmail.com wrote:
Thanks, Chen.
On Mar 28, 10:40 pm, Chen Yang sunsety...@gmail.com wrote:
Brian:
I cannot see the clear problem from your description.
Hi Chen,
I managed to use adb.
I'm attaching /proc/devices. From the list, you can see 29 fb.
Is this what you're looking for?
Thanks,
Brian
Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
14
Thanks, Yi !
I think init.rc is not correctly executed. It probably exits before it
starts adb.
I manually started adbd, and connected android using adb successfully.
What problems did you have in init.rc?
Thanks,
Brian
On Mar 29, 2:21 pm, Yi Sun beyo...@gmail.com wrote:
In your ps, I did
Here is the part of the init.rc that I think is important for you to verify.
Just make sure you have all of them enabled. You init.rc should be in
/vendor/asus/eee_701/
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
on
Thanks, Yi.
I have all the following in my init.rc.
servicemanager, mediaserver, installd are running.
But adbd, mountd, and zygote are not launched. Any suggestion?
Thanks,
Brian
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
on
I found out that there is no mountd under /system/bin.
It must be that mountd is not copied into system.img.
Which code should I look at to ensure that system.img contains mountd?
Thanks,
Brian
On Mar 29, 6:26 pm, Yi Sun beyo...@gmail.com wrote:
Here is the part of the init.rc that I think is
Hi Chen,
When I added vga=788 in the cmdline in booting it, the screen totally
freezes. Even alt + f1 does not display any.
I booted the kernel with vga=788 option. In that case, I have the
following in /proc/cmdline.
console=ttyS1,115200n8 console=tty0 androidboot.hardware=eee_701
I tried to
hi, Brian:
Sorry for late response on this thread.
Would you like to check the whether the kernel has the VESA
support? Would you like to provide the result with:
#cat /proc/cmdline
and
#cat /proc/devices
see whether fb is listed.
--
Chen
On Fri, Mar 27, 2009 at 1:46 PM, Brian
Hi,
I did all the steps following Chen's instructions. I am still having a
problem. I have tried vmware workstation and fusion.
In the vmware workstation, I got a blank screen after booting.
When I press alt + f1, I can see the following messages.
[time] init : cannot find '/system/bin/mountd',
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 agnimid...@gmail.com wrote:
Hi,
I have built Android for eee PC
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,
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:
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 wwh.andr...@gmail.com wrote:
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
Hi chen Yang
I still have a question about adding modules to compile the kernel
when we select the M option in make menuconfig.
I put the *.ko under vendor/asus/eee_701/modules directory after I had
made module.
Then I built the installer_img again and install.
After all done, the *.ko doesn't
oops, my fault, you need also to specify in the Android.mk under
vendor/asus/eee_701/Android.mk:
...
kernel_modules := \
atl2.ko \
bitblit.ko \
cfbcopyarea.ko \
cfbfillrect.ko \
cfbimgblt.ko \
fbcon.ko \
font.ko \
softcursor.ko \
I just fixed it a while after posting, sorry - murphy's law in action.
To answeryself, edit /system/etc/mound.conf and use /dev/block/sdb1 -
at least this was the right block device for my eee pc 701 sd card in
android - in ubuntu eee it is sdc :-p
Now I must try to find a way to make sound
By the way,Is there any expert can tell me some method to debug the
android platform(not linux kernel) with android emulator and ubuntu
On 2月24日, 上午3时40分, Chen Yang sunsety...@gmail.com wrote:
oh, you are using the installer.img to boot with normal boot, that is
impossible. Since the
when I start option 2(std_boot)
cmdline (hd0,2)/cmdline
Error 22: No such partition
how to deal with it？
and I start option 0（sys_loader) and do the follow steps:
# mkdir /data/boot
# mount -t ext2 /dev/block/sda2 /data/boot
ioctrl LOOP_SET_FD failed: Device or resource busy
why?
On
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
Is it possible to run android on a common PC (x86) ?
On 1月10日, 下午9时11分, Lim,GeunSik lee...@gmail.com wrote:
Hi, all
How to use x86 android platform on virtualbox
===
Last modified by Lim,GeunSik on 8-Jan,2009
Current
1 - 100 of 176 matches
Mail list logo
