Now, for testing purposes, I'm bypassing BatteryService(cpp) with some constants in eee target...
On 8 Apr, 02:00, Yi Sun <[email protected]> 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.FOREGROUND_APP_ADJ 0 > setprop ro.VISIBLE_APP_ADJ 1 > setprop ro.SECONDARY_SERVER_ADJ 2 > + setprop ro.HOME_APP_ADJ 4 > setprop ro.HIDDEN_APP_MIN_ADJ 7 > setprop ro.CONTENT_PROVIDER_ADJ 14 > setprop ro.EMPTY_APP_ADJ 15 > + > > # Define the memory thresholds at which the above process classes will > # be killed. These numbers are in pages (4k). > setprop ro.FOREGROUND_APP_MEM 1536 > setprop ro.VISIBLE_APP_MEM 2048 > setprop ro.SECONDARY_SERVER_MEM 4096 > + setprop ro.HOME_APP_MEM 4096 > setprop ro.HIDDEN_APP_MEM 8192 > setprop ro.CONTENT_PROVIDER_MEM 8704 > setprop ro.EMPTY_APP_MEM 16384 > > On Tue, 2009-04-07 at 16:55 -0700, Luca Belluccini wrote: > > 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) > > -the dalvik vm exits a thread due to an uncaught exception > > (NumberFormatException) @ androidruntime/ActivityManagerService > > (during a parseInt...) > > > 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... > > > On 6 Apr, 08:47, Gasol <[email protected]> wrote: > > > 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 <[email protected]> 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 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 when I do porting android with USB,the pc always run a long time > > > > then get the following result and stop . > > > > > ----------------------------------------------------------------------- > > > > [5229.798013] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors > > > > (80026 MB) > > > > [5229.798034] sd 0:0:0:0: [sda] Write Protect is off > > > > [5229.808047] sd 0:0:0:0: [sda] Write cache : enabled , read cache : > > > > enabled, doesn't support DPO or FUA > > > > [5229.817097] sda: sda1 sda2 sda3 sda4 <sda5 sda6 sda7 sda8> > > > > I/installer (1823): Done processing installer config. Configured 6 > > > > images > > > > ------------------------------------------------------------------------ > > > > > Then I reboot without USB . > > > > I get the following result and then jump to blank screen. > > > > ------------------------------------------------------------------------ > > > > [ 9.058771] warning:'app_process' uses 32-bit capabilities (legacy > > > > support in > > > > use) > > > > ------------------------------------------------------------------------ > > > > > What's wrong with it? > > > > > Can anyone give me some tips,please? > > > > > thanks > > > > > Icekolo > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
