You'll probably need only a single build (30GB) to warm up. And I assume
your work will mainly touch the kernel (OOM, lowmemorykiller) and the
dalvikVM. I strongly advise you to do one complete snapshot. Otherwise
you'll end with a weird environment, and images you can't rebuild. And
you'll pay the
I have a BCM4312 as well. I am desperately hoping that this driver will
eventually be supported in ICS :(
On Friday, October 12, 2012 1:19:59 PM UTC+1, Rishi Raj wrote:
>
> Hi I am using Lenovo s10-2 which is using BCM 4312 wlan card , dev id is
> 4315 , I am using android-x86-4.0-RC1-eeepc.iso
Hi everybody,
I want to work on the Android's memory management to implement some
ideas. Reading the Source > Getting Started from AOSP site, I found these
notes:
*Note: The source download is approximately 8.5GB in size. You will need
over 30GB free to complete a single build, and up to 100GB
You can also achieve this by doing the following:-
Where ever you want to get the process name, just print
thread->proc->tsk->comm
Herr thread is the binder_thread structure associated with the current
running thread.
Regards,
Rahil
On Nov 7, 2012 9:43 PM, "andria" wrote:
>
>
> Le mardi 6 novembr
Le mardi 6 novembre 2012 05:36:00 UTC+1, Manish Sharma a écrit :
>
> Hi,
Hi
>I want to find out the current process name. I tried current->comm but
> what I get is "Binder Thread #" with different thread numbers. For ex. I
> get "Binder Thread#' from comm for id.defcontainer.
>
The r
Le mardi 6 novembre 2012 05:36:00 UTC+1, Manish Sharma a écrit :
>
> Hi,
Hi
>I want to find out the current process name. I tried current->comm but
> what I get is "Binder Thread #" with different thread numbers. For ex. I
> get "Binder Thread#' from comm for id.defcontainer.
>
The r
