In my analysis,the reason is:
When lock surface,the surface can't be locked,so that
per_client_cblk_t::lock_layer will never return.
But this issue will never appear if I add logs to track it,who can
provide more hints on how to fix it or why it will occurr?
The log is:
01-01 00:15:07.558:
My G1 SW version is RC30, AfterI downloaded HTC offical radio image at
http://www.htc.com/www/support/android/adp.html#s3, I try to update
the radio image, but I met below error:
E:No signature (5 files)
E:Verification failed.
Installation aborted.
Does someone know how to fix the problem?
We are developing WVGA product with screen 854x480,one screen surface
will need about 1.6MB memory,so 8MB display memory seems can't
accommodate the usage and actually we met crash when switch between
complex applications.
My question is: Does google plan to increase the allocated memory size
Can someone help on the problem?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
The normal way to change a Exif tag is like:
ExifInterface.getAttributes - modify some attribute - saveAttributes
- commitChanges.
The problem exists in saveAttributes which will call jhead API
DiscardData() in the end and the static variable HaveAll is set to 0,
then commitChange will fail.
We met issue when try to use libexif.so which is linked to other
native code and in the same time used by ExifInterface java class.
The native code can call libexif.so successfully but the java class
ExifInteface will fail Cannot find library.
To avoid the problem,we have to split the
It is said android VM can't allocate more than 16MB memory,I'm not
sure if it includes the memory allocated in native code and hope
someone can clarify.
I also met problem with exception out of memory in java application,
I wonder is there usefull way to know how much memory is allocated by
VM?
