java.lang.StackOverflowError when deserializing

by Marco Schmitz » Tue, 28 Apr 2009 21:13:33 GMT


Sponsored Links
 dear fadden,

thanks a lot for "Thread(ThreadGroup group, Runnable target, String
name, long stackSize)".

this works perfectly :)

greetings,
darolla

2009/4/22 fadden <fad...@android.com>:


--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Layout problem -> tablet emulator size 1024 * 600

Hello,

I want to develop a application on Samsung Galaxy.
The resolution is 1024 * 600
My mainlayout should look like this:

http://office.techniconsulting.be/~peeters/eclipse_screenshot.jpg

I've a left image (296 *600) and right image (728 * 600) as
background.
mail.xml looks like:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/
android"
     android:orientation="horizontal" android:layout_height="600px"
android:layout_width="1024px">

       <LinearLayout android:id="@+id/LinearLayout01"
android:background="@drawable/frame_left"     android:gravity="left"
android:layout_width="296px" android:layout_height="600px"></
LinearLayout>
<RelativeLayout android:id="@+id/RelativeLayout01"
android:gravity="right" android:background="@drawable/
frame_right_kelder" android:layout_width="728px"
android:layout_height="600px"></RelativeLayout>
</LinearLayout>


Whwen I run it in the simulator it looks like:

http://office.techniconsulting.be/~peeters/emulator_screenshot.jpg

Is it not possible to work with pixel height en width in the emulator?


-- 

2. Updating Pre-Installed or Built-In Apps

I posted this late last Friday, so maybe no one saw it. I thought I'd
give it one more try:

-------------------------

My employer has a customer with the good fortune of having products
that will be shipped with some OEM devices. This has raised some
questions about updating the application that, despite having
researched this subject on this group and in some others, we are still
unsure about.

1) It appears that built-in applications are installed in the /system
subtree of the files system, which is read-only to everyone but those
with root permissions. This means that any updates with a higher
VersionCode that are delivered via the Android Market would be placed
into the /data subtree, and the application in the /system subtree
would be somehow become inactive.

Later, when a new system update becomes available, if the built-in
application has a VersionCode that is higher than the one in the /data
subtree, that application would be "deactivated" and the one in the
system image would become active again.

Is this still the way it still works?

I gleaned this information from a discussion on this group, from last
December:
http://www.google.com/url?sa=D&q=

3. Android Market statistics problem ?

4. ContactManager sample app (api version 7) stopped unexpectedly : Need Help

5. GLThread, native code, and dialogs

6. Run Android 2.0.1 on HTC magic

7. Android Emulator without a Camera, Camera.open() != null ????