Andrew,
On Sat, Jan 17, 2009 at 2:41 AM, drew wrote:
> But I do have a question, isn't the IPC a standard that's already
> being used for SIP phones and even your normal Telecom Provider? And
> if, just if, my base premise is correct wouldn't that mean that the
> current kernel just needed exten
There are three kinds of process in dalvik model
zygote
specialized
systemserver
It is easy to understand when a zygote process forks child process to
share the core lib with it. But why should a systemserver process
terminates with killing its parent process？
--~--~-~--~~~
Hi,
Did you get android running on S3C2440 Board ? I am not sure what
board and ARM processor version
the zImage that runs in emulator is made. What hardware does the
android emulator in master branch emulates.
thanks.
george
On Jan 8, 6:21 am, leemgs wrote:
> Hi, grgkumar4
> Um...
>
> At firs
As for dalvik vm, we can fork three kinds of process with the three
api: fork,forkAndSpecialize,forkSystemServer.
Can anyone give an acute analysis of the 3 process kinds of what they
can do and why they should be classified into these kinds?
--~--~-~--~~~---~--~~
u
On Fri, Jan 16, 2009 at 5:41 PM, drew wrote:
> But I do have a question, isn't the IPC a standard that's already
> being used for SIP phones and even your normal Telecom Provider? And
> if, just if, my base premise is correct wouldn't that mean that the
> current kernel just needed extending to s
Peace!
Wow, First off I'd like to thank you guys for inputting your views. It
is enlightening and exciting to see what's possibly going on with the
core Linux and where Google is in the development. Google's API's do
rock in making it easy to program for the Android Environment and I
applaud the
That all sounds good, thanks.
JBQ
On Fri, Jan 16, 2009 at 5:19 PM, Dianne Hackborn wrote:
> The focus of this work is density, not resolution. We will be quantizing
> density into a few buckets (corresponding to the existing HVGA, adding QVGA
> and WVGA at the same size) which are supported by
The focus of this work is density, not resolution. We will be quantizing
density into a few buckets (corresponding to the existing HVGA, adding QVGA
and WVGA at the same size) which are supported by the platform.
It has always been the case that Android applications should not rely on an
exact si
There are quite a few precedents for situations with pixel counts that
are close to one another, and it'd be good if Android allowed some
fuzziness in the size "buckets" so that apps that are tuned for
certain screen sizes but don't rely on bitmaps so much that the value
matters to the pixel can a
I'd like to qualify that a little -- this work is to introduce support for
different densities in the system, targeting only QVGA and WVGA screens that
are approximately the same physical size as the G1's screen. This will not
add support for larger WVGA screens that are the same density as the G1
We are moving to a density independent pixel representation, so the
specific screen resolution is irrelevant.
On Jan 16, 12:10 am, anand b wrote:
> Hi,
>
> WVGA can refer to displays of the following resolutions:
>800x480 or 854x480 or 864x480
>
> Can you please clarify what is the resolut
On Fri, Jan 16, 2009 at 8:18 AM, F H wrote:
> Thanks Mathias, that helps *a lot*.
>
> My brain hurts from looking at the memory stuff!
>
> I can now see that each client maps in the 8Mb shared memory region once.
>
> What I don't understand at the moment is where the pointer to the surface
> data
Hi,
Since S3C2440 is ARM 920T core, I thought of booting it with the
kernel that I built from android
tree, but bootloader (supervivi) failed to load the image. Any hints
as to what could be going on.
-George.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+un
Thanks Mathias, that helps *a lot*.
My brain hurts from looking at the memory stuff!
I can now see that each client maps in the 8Mb shared memory region once.
What I don't understand at the moment is where the pointer to the surface
data is passed back to the client - can you say at what point t
Hi
I have ported android on omapzoom. whenever i press keypad buttons to
enter URL in android browser or to store names in contact lists only
it displays on digits but i want characters to be displayed
Can u help me regarding this? like exact keypad mappings for android
on omapzoom p
There are flood of documents available on internet to start off with.
Some links are :-
http://code.google.com/android/intro/index.html
http://elinux.org/Android_on_OMAP
https://omapzoom.org/gf/project/omapandroid/wiki/?pagename=Installing+the+System
Thanks
Nimit
On Fri, Jan 16, 2009 at 3:47
Vishal,
I have my own customized kernel with android patch on top of it.
Yes keypad worked for me but only few keys as i told u earlier also.
Thanks
Nimit
On Fri, Jan 16, 2009 at 3:47 PM, hzy.speeddra...@gmail.com <
hzy.speeddra...@gmail.com> wrote:
>
> Android is more popular now, how could I
Android is more popular now, how could I join with you?
Is there any how-to to follow?
Thanks
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~-
Nimit,
Which karnel are you using ?
On Fri, Jan 16, 2009 at 4:36 AM, vishal bhoj wrote:
> Nimit ,
>
> Is it ? CAn you please check and tell me if the driver is ads7846 ?
> Did the keypad work for you ?
>
>
> On Fri, Jan 16, 2009 at 3:35 AM, Nimit Manglick wrote:
>
>> Hi Bhoj,
>>
>> I didn't do
Nimit ,
Is it ? CAn you please check and tell me if the driver is ads7846 ?
Did the keypad work for you ?
On Fri, Jan 16, 2009 at 3:35 AM, Nimit Manglick wrote:
> Hi Bhoj,
>
> I didn't do anything specific with touchscreen. I was having my kernel
> ready with
>
> touchscreen support and my thing
in your touch driver ,you should set the x/y/pressure's MAX value and MIN
value,the android according to the MAX and MIN value to calculate your
inputing values
On Thu, Jan 15, 2009 at 4:34 PM, vishal bhoj wrote:
> when i did a logcat i get
> Starting input on non-focused client
> com.android.i
hi mark:
we use the 2.6.25 kernel ,the porting is easy:)
you may try to use the common file system to run your kernel ,if the kernel
run well and you can see the android power attributions at /sys, and then i
think your kernel is very close to run the android:)
On Fri, Jan 16, 2009 at
yes, it is exactly what need doing.
Good Luck!
On Thu, Jan 15, 2009 at 8:00 PM, Android Zaurus
wrote:
>
> Hi, Qingzhan
>
> I ported Android 1.0 atop of Angstrom 2007.1 stable, which uses
> Kernel 2.6.24 and it works fine on my Zaurus C3000 (PXA270).
>
> Here's the patch of power.c between mydro
Hi Bhoj,
I didn't do anything specific with touchscreen. I was having my kernel ready
with
touchscreen support and my things got up.
Regards
Nimit
On Thu, Jan 15, 2009 at 1:35 PM, vishal bhoj wrote:
> NIMIT,
>
> how did you get the touch screen working ?
>
> On Thu, Jan 15, 2009 at 2:45 AM, v
Hi,
WVGA can refer to displays of the following resolutions:
800x480 or 854x480 or 864x480
Can you please clarify what is the resolution that Android refers to?
I understand that the support for WVGA is in Android roadmap post Q1 09.
Thanks,
Anand
--~--~-~--~~~---
Hi, Qingzhan
I ported Android 1.0 atop of Angstrom 2007.1 stable, which uses
Kernel 2.6.24 and it works fine on my Zaurus C3000 (PXA270).
Here's the patch of power.c between mydroid/kernel and Angstrom
kernel tree.
http://pastebin.com/m6f01141c
But, as you mentioned, ANDROID_POWER may not be a
26 matches
Mail list logo
