hi , i build cupcak whih PRODUCT_POLICY := android.policy_mid (I
modified the file: \build\target\product\core.mk)
then I found that the PinyinIME can't launch. any one can help me ?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.co
the log as fellow:
06-03 02:55:35.755: WARN/dalvikvm(643): threadid=3: thread exiting
with uncaught exception (group=0x4000fe70)
06-03 02:55:35.765: ERROR/AndroidRuntime(643): Uncaught handler:
thread main exiting due to uncaught exception
06-03 02:55:35.796: ERROR/AndroidRuntime(643):
android.vi
hi Terry Z :
Do you have solved the problem? I also encountered this problem。
any help? I am also using marvell pxa310 platform
On 6月28日, 上午3时14分, Elvis Dowson wrote:
> Hi, Are you using DSS2 with omapfb framebuffer implementation? If so ,
> then you need to apply the latest DSS2 p
hi Terry Z
How did you solve this problem? I also encountered this problem .
Any suggestion?
On 7月1日, 上午9时54分, Terry Z wrote:
> The LCD do not flicker If I am not using the Soft Keyboard. It happens
> only when I press down a key and not the every time.
>
> On 7月1日, 上午9时39分, Terry Z wrote
hi Terry Z :
I fixed this problem in driver . I think it's the best way .
marvell had release a patch for this problem in driver drivers/video/
pxafb.c.
But I want to known how did you fix it. Can you give me a copy of
EGLDisplaySurface.cpp ?
thank you very much !
--~--~-~--~~--
I want to compile android for a mid product, so I compiled android
with PRODUCT_POLICY := android.policy_mid . But I found that I can't
open the soft keyboard. Because my mid product has no keyboard, so I
want to use soft keyboard instead. Maybe it was designed to be so. But
how can i solve my
I have some source code in hand which can use hardware acceleration
just like MMX,IWMMXT,SSE and so on. As we known, android use arm-eabi-
gcc to compile source code.so my question come : Is arm-eabi-gcc
support iwmmxt?
Or what should I do to make is support iwmmxt? Thanks in advance.
--~
when using pc emulator,the Permission of /data/app as fellow: (so I
can install apk files successfuly)
ls -l
-rwxrwxrwx root root 1745016 2009-02-23 03:05 busybox
drwxrwx--x system system2008-12-22 07:37 location
drwxrwx--x system system2008-12-22 07:37 ap