android-discuss, Drap and drop an OverlayItem in aMapView

1. TextView borders when contained in a tablerow?

Hi everyone. I have an interesting problem.  I am using a TableLayout to 
arrange a series of labels and TextViews.  In some cases, the text within 
the TextView is bold and colored blue to represent a field which is 
clickable. Meaning that I have a listener on it to launch a new activity. 
 On fields where I have done this, the bottom border seems to disappear. 
 Has anyone seen this before? Here is an example of the problem.  Notice the 
border missing below the address and phone rows.

**<https://lh5.googleusercontent.com/_h03pCOGU1n0/TTiu4GkUUPI/AAAAAAAAAAc/ABLJYekrrPU/borders.JPG>
*
*
*Here is an example of how I have a regular field defined:*

   <TableRow>
       <TextView
           android:text="Status"
           android:textStyle="bold"
           android:gravity="right"
           android:padding="3dip" />
       <TextView android:id="@+id/status"
           android:text=""
           android:padding="3dip"
           android:layout_marginRight="2sp"
           android:background="#FFFFFF"
           android:textColor="#000000" />
   </TableRow>


*And one that is clickable:*

       <TextView
           android:text="Email"
           android:textStyle="bold"
           android:gravity="right"
           android:padding="3dip" />
       <TextView android:id="@+id/email"
           android:focusable="true"
           android:focusableInTouchMode="true"
           android:clickable="true"
           android:text=""
           android:padding="3dip"
           android:layout_marginRight="2sp"
           android:background="#FFFFFF"
           android:textColor="@color/link_blue"
           android:textStyle="bold" />
   </TableRow>

-- 

2. Strange native leak - OutOfMemory after language change.

Hi.

I am facing a strange native memory leak in my application, can
someone help me please?

The leak heppens after change the language of the phone in settings.
Before changing the language, I have just opened the application and
ran dumpsys meminfo in the process. The result was that the process
had 18495 KB total memory allocated, which were 11704 KB native and
6791 KB dalvik.

After changin language for the first time, opening the app again and
running dumpsys meminfo onge more time, the result was that the
process had 24115 KB total memory allocated, which were 17324 KB
native and 6791 KB dalvik.

Looking the heap size in DDMS I saw the process had a total of 6 MB,
which makes sense with the 6791KB of dalvik memory allocated. Changing
the language again makes the total allocated memory grow, getting to
29335 total memory allocated, which were 22544 KB native and 6791 KB
dalvik.

As you can see, it is only the native part that grows, therefore using
Eclipse MAT on the generated HPROF file does not give any good leak
suspects.

We are passing the application context instead of the activity context
as explained in the article 
http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html

I compared the results with other applications in the phone, and saw
that it is common to the memory allocated to grow in the first time
the language is changed, but the amount of memory is kept unchanged in
the subsequent changes for those other applications.

I also read that "DDMS does not report memory that is allocated on
your behalf on the native side", but than, how can I make sure that
memory will be freed? Also, the content of the native memory must be
connected to the dalvik amount of memory, how can I find that
connection??

I am getting out of ideas, did anyone see something similar or have
any hints for me?

Thanks in advance!!
Cheers!!
Pedro

-- 

3. HTTPS POST (SSL) with Multipart - HTTPURLConnection or HTTPClient(Apache library)

4. Implementing a RightMarginSpan/EndingMarginSpan in a TextView

5. Determine sprite gravity and physics, auto acceleration of a sprite, and have the view follow the sprite?

6. Flash 10 Examples (in Android 2.2)

7. [HELP/URGENT] Odd Animation/Layout Button "Hit Area" Problem