Dalvik error message (wrong cl)

by alexdonnini » Tue, 24 Mar 2009 03:05:23 GMT


Sponsored Links
 Hello,

I apologize in advance if I am posting this question to the worng
group in which case I would appreciate it if someone could refer me to
a more appropriate group.

Recently, I have run into the following error a number of times:

DEBUG/dalvikvm(416): +++ not scanning '/system/lib/libwebcore.so' for
'connectToSupplicant' (wrong CL)

Could someone explain the typical cause of this error and point me
towards a possible solution, or steps for diagnosing the problem?

Thanks.

Alex Donnini
--~--~---------~--~----~------------~-------~--~----~



Dalvik error message (wrong cl)

by fadden » Tue, 24 Mar 2009 22:56:09 GMT


 


Probably android-platform; this group is for discussion of the Android
app framework.


This is a "DEBUG" message, not an error message.

This message occurs when there is an unresolved native method, and the
VM has to go searching through every known shared library for a
matching symbol.  The class that caused the method resolution is in a
different class loader from the one that loaded libwebcore.so, so the
VM is letting you know that it's not going to search there.

This message could be helpful if you couldn't figure out why a method
wasn't being found.  Otherwise it's just noise.  It probably ought to
be disabled.

Native methods that are explicitly registered (e.g. during JNI_OnLoad)
don't go through the dlsym() search and will never generate this
message.

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


Sponsored Links


Other Threads

1. CLOSE WTA abis OTA update.... rooted milestone app force close?

lohh? ini dah beres?

2010/7/22 Lean Nasution <mydroidma...@gmail.com>









>> >> >>> 

2. How to determine dpi of new devices

Our company are porting 2.1 to new device whose resolution is
1024*600 and screen size is 5.5inch.
We have got the model. We had thought this new device's dpi should be
240 but we found out the output of DisplayMetrics was like below:
density is 1.0
densityDpi is 160
scaledDensity is 1.0
xdpi is 159.8
ydpi is 160.2

I think the one porting display driver made mistakes but the others do
not think it was wrong.
Can we change dpi of LCD to any value as our wish?

Thanks.

James

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Detecting "lock_layer timed out"

4. Bluetooth Connection

5. How to change TabWidget default grey color

6. CLOSE WTA abis OTA update.... rooted milestone app force close?

7. SOLVED Downgrade Radio HTC G1