Please do let know if your wifi works ok. And it will be even better if
someone could write up a Howto page for wifi configuration. Yi
On Tue, May 5, 2009 at 5:30 PM, penguins wrote:
>
> I missed that one totally. Now, I can see wpa_supplicant in included
> in the build. Thank you Yi Sun!
>
>
>
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 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,
>
>
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
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 HAVE_CUSTOM_WIFI_DRIV
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 wrote:
>
> Hi, I did a search but couldn't find an exact answer. Is there a good
> guide or any pre built Android images for an Asu
Hi, I did a search but couldn't find an exact answer. Is there a good
guide or any pre built Android images for an Asus Eee PC 1000HE. I
would like to try installing it, but I need help. Thanks.
On Mar 22, 6:17 pm, Brian wrote:
> Hi Midhun,
>
> I'm having the same problem when I ran android e
Can you enabled the DEBUG_INPUT in the windowmanager and the debugging in
the queue thread in KeyInputQueue.java so that we can know how you the code
process the ABS_x/y
How did you changed the permission for the device node?
2009/4/23 sparq
>
> Thank your advice, Yi.
>
> I search and reference
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 a
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 t
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 driver
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 wrote:
> Hi
> Can you share the porting steps or procedure?
>
> Regards,
> Sathish.
>
> On Apr 2, 9:05 am, Brian wrote:
>
> > Th
Hi
Can you share the porting steps or procedure?
Regards,
Sathish.
On Apr 2, 9:05 am, Brian 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): java.lang.IllegalState
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
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 wrote:
>
> ok i think I just broke something. The Android HomeScreen doesnt'
> respond to keyboard events now. Though I can Alt+F1 to con
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 wrote:
>
> Thank you Yi,
>
> Applied the patched (I applied some of the cursor patch manually).
>
> The building process stopped halfway and I got these messages:
>
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/
PhoneWindow does not exist. Patch wasn't applied correctly.
On 18 Apr, 00:21, penguins wrote:
> And multiples of the following:
>
> D/AndroidRuntime( 1913): >> AndroidRuntime START
> <<
> D/AndroidRuntime( 1913): CheckJNI is ON
> D/AndroidRuntime( 1913): --- registering n
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 / 4058
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, h
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
D
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
>
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 (2008
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 me
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
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 wrote:
> You are correct. I was missing
> setprop ro.HOME_APP_MEM 4096
> in the init.rc .
>
> Now I get the
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 wrote:
> > I applied all the patches and
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.
--~-
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, 2009-04-1
I do have
setprop ro.HOME_APP_ADJ 4
added to init.rc .
On Apr 15, 3:26 pm, Zia 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
> library (Cannot find library)
> 04-15 22:25
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
library (Cannot find library)
04-15 22:25:29.601: WARN/dalvikvm(2081): threadid=19: thread exiting
with uncaught exception (group=0xb003fdf8)
04-
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 wrote:
>
> Brian,
>
> I'm having the similar problem. Did you find a fix for it?
>
> Thanks,
>
> Zia
>
> On Apr 1, 9:05 pm, Brian wrote:
>> The system is trying
Brian,
I'm having the similar problem. Did you find a fix for it?
Thanks,
Zia
On Apr 1, 9:05 pm, Brian 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): java.lang.Illega
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 W
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 wrote:
> BTW-- this is a sw cursor.
>
> On Mon, 2009-04-13 at 15:54 -0700, Yi Sun wrote:
> > Sign... I really don't want
:-)
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 wrote:
>
> Cool!
>
> On Tue, Apr 14, 2009 at 6:54 AM, Yi Sun wrote:
>>
>> Sign... I really don't want to post this patch because there are
>> something
sorry for not being clear.
I am using the make-live script to create bootable usb drive to run
android. When the script creates the grub files, it creates it on the
root file system and the grub related files are present in /boot/grub.
What i want to do is have a separate partition for grub.
Like
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 wrote:
>
> Hi Chen,
>
> I have a question on creating live bootable usb. Can the gurb
> bootloader for android be o
Cool!
On Tue, Apr 14, 2009 at 6:54 AM, Yi Sun 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
> http://code.google.co
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 wrote:
> hi Brian:
BTW-- this is a sw cursor.
On Mon, 2009-04-13 at 15:54 -0700, Yi Sun 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
> ht
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
http://code.google.com/p/patch-hosting-for-android-x86-support/
Here is the idea:
1. de
i am able to run android on a toshiba R25 tablet PC. The tablet touch
does not work, but the keyboard works fine. I want to connect to the
internet using a wifi or a wired connection. I added the wifi (intel
3945ABG) and wired drivers (intel 100) drivers to the kernel. Looks
like they are recogniz
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
E/
You _must_ apply frameworks.path. Otherwise, Zygote will crash during
the preloading the PhoneWindow classes and BatteryService will crash due
to wrong sys fs path then you will never see the UI to come up.
to get output of logcat, you only need to run the logcat command.
Yi
On Sun, 2009-04-12 at
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 wrote:
> logcat output please.
>
> Also> > And I applied boot_able_img.patch, alarm.patch, e2fsprogs.patch.
>
> Is this a typo or you did not apply
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
>
Hi Yi.
I've just tested your patch.
EXT2-fs problem is resolved.
but
"sh:can't access tty; job control turned off " message is still.
I am wating android UI for 10 minutes.
any suggestion?
Here is result message.
...
[time..] init: /init.rc: 89: invalid option 'enabled'
Hi, Sun, I am running android on thinkpad t60, alsa sound is working
now, next step I will try to enable mouse cursor, could you kindly
give me some hint?
On Apr 10, 2:35 am, Yi Sun wrote:
> Agree, as matter fact, I have created a google code page this morning to
> host the patches I mentioned i
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 and
Hi Yi
environment:
VirtualBox : Sun xVirtualBox 2.1.4
Host : Windows XP, guest: Ububtu8.10
I did android building process on guest environment(Ubuntu).
I downloaded above patches from
http://code.google.com/p/patch-hosting-for-android-x86-support/
(boot_able_img.patch,
alarm.patch,
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
hi Yi.
I have no eeePC.
so, I am testing on just VM.
On Apr 10, 3:24 am, Yi Sun 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 with an
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, 2009-04-
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 patc
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 with android 2.6.25 kernel building with modifying some
> config option. T.T;;
>
> I did like this to make late
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 drm/linux-cor
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)
vendor/asus/e
Hi Shlee,
In the end, I used 2.6.27. But 2.6.25 should also work.
The way I addressed the fb problem is to build and use the latest
intel drm driver modules.
Afterwards, you need to modify init.rc and some service files as
posted in this mailing list.
-Brian
On Apr 9, 7:58 am, shleeforandroid
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
I can find the 2.6.25 kernel.
It's just simple.
>From this site.
http://code.google.com/p/android/downloads/list
I can download "linux-2.6.25-android-1.0_r1.tar.gz"
I will this kernel compile with used config file.
Is it OK?
Thanks
shlee.
On Apr 9, 11:58 pm, shleeforandroid wrote:
> hi br
hi brian
Congratulate your work
I've just reached to some part of your work that is posed " On Mar 30,
8:49 am, Brian " below.
> > >> >> >Thanks, Jerry!
> > >> >> > I'm using kernel 2.6.27, and the modules have version 2.6.25 as you
> > >> >> > can see below.
> > >> >> > There are inconsiste
2009/4/7 Luca Belluccini
> 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 current values in the off
Now, for testing purposes, I'm bypassing BatteryService(cpp) with some
constants in eee target...
On 8 Apr, 02:00, Yi Sun 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
> setprop ro.FOREG
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 ro.HI
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)
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 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
> -RAM:1.0GB
> -gcc v
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
-RAM:1.0GB
-gcc version:gcc-3.4
-Java JDK 5.0
I followed Lim's method to do Android porting for X86.
I compiled the source code successfully and reboot from my USB stick.
But
Sorry I have no idea why it was using the mid policy. Actually I have no
idea what the mid policy actually does -- I've never looked at it except to
hack it to make it build when I change the window manager API. I didn't
even know anyone was actually using it. That is why I was just going to
del
hi Dianne:
Thanks. Would you like to tell whether it is possible to use phone
policy with those device with mid policy? I did a test, and it seems
working, but haven't tried everything. I am interested to understand
the rationale behind introducing mid policy.
--
Chen
On Fri, Apr 3, 2009 at 5:
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 wrote:
>
> Thanks for let us know your plan. Then would you like to share
hi Brian:
Alt+F1 change to the console, then type netcfg, you will see the ip address.
if no ip, try: netcfg eth0 dhcp
in VMWare, the ip seems to be fixed although it is assigned by dhcp.
Press Alt+F7 to the graphic interface. :)
--
Chen
On Thu, Apr 2, 2009 at 12:43 PM, Brian wrote:
>
>
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 wrote:
> On Wed, Apr 1, 2009 at 10:41 PM, Chen Yang wrote:
>>
>> Yes, eee_701 is using the mid policy at present. And t
On Wed, Apr 1, 2009 at 10:41 PM, Chen Yang 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 current cupcake tre
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 wrote:
> Um, those classes certainly should exist. Unless you are trying to build
> with the "mid" policy, which I am sure at this
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 wrote:
> hi Brian:
> You may need to modify the framework/bas
Hi Chen,
Finally, Android booted successfully !
Thanks for all the help.
I need to connect to it using adb, but I don't know its ip 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 wrote:
> hi Brian:
> You may nee
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 wrote:
>
> hi Brian:
> You may need to modify the framework/base/preloaded-classes to
> remove those non ex
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 AC_O
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 A
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
[com.android.internal.policy.impl.PhoneLa
Cool. It seems that you don't have the essential process: zygote. You
can check the logcat messages to see what was happenning. Thanks.
--
Chen
On Thu, Apr 2, 2009 at 8:09 AM, Brian wrote:
>
> Hi all,
>
> I finally managed to boot android x86 with vga=788 option without
> black screen in vmware
Hi all,
I finally managed to boot android x86 with vga=788 option without
black screen in vmware.
Thanks for all the help!
I'm trying to go to the next step.
Even with vga=788 option, I don't see GUI. Why? Instead, I get a shell
prompt.
Here's the list of system processes stored under /system/bi
Cool!
Then google has modified the battery service related code.
--
Chen
On Wed, Apr 1, 2009 at 5:15 PM, Androidphan wrote:
>
> This is why Android is not booting:
>
> I/SystemServer( 6925): Starting Battery Service.
> E/BatteryService( 6925): Could not open '/sys/class/power_supply/ac/
> onlin
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 '/sys/class/power
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 = WindowMa
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 cha
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 wrote:
> i modified the init.rc, it seems right, but when i
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 wrote:
>
> Thanks, Yi.
>
>
Thanks, Yi.
I think I compiled with the following option <*>Framebuffer console
support.
I will change it to Framebuffer 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 softcu
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 wrote:
>
> Thanks, Chen.
> I looked at the kernel 2.6.25 source code. It seems that this kernel
> version does not use drivers/android/alarm.c (the l
Thanks, Chen.
I looked at the kernel 2.6.25 source code. It seems that this kernel
version does not use drivers/android/alarm.c (the location of the
source code is also different) since it's not compiled.
When I do not use vga=788, I get a shell prompt. I did dmesg to see
what's going on in this
See whether this patch would help.
https://review.source.android.com/Gerrit#change,6751
--
Chen
On Tue, Mar 31, 2009 at 11:27 PM, Brian wrote:
>
> I got more detailed error messages.
>
> Console: switching to colour frame buffer device 100x37
> - [cut here] ---
>
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 .
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
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 wrote:
>
> Thanks again. Another problem to start it:
>
> I/SystemServer( 2543): Starting Battery Service.
> E/
i modified the init.rc, it seems right, but when i run it on the
notebook, i found that the keyboard is not work well, i don't know why
On Mar 31, 5:51 pm, Chen Yang wrote:
> 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/in
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 '/sys/clas
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, 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...
E/MemoryHe
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 wrote:
>
> I'm getting the following error wh
1 - 100 of 252 matches
Mail list logo