As it says, you should wipe the data; something changed in the system
certificates or other data that is incompatible with your old data
partition.
On Thu, Nov 27, 2008 at 10:35 PM, yogesh <[EMAIL PROTECTED]> wrote:
>
> while starting up system, alert is pop up "System UID's Inconsistent:
> UID's
after booting up i am facing "JNI_CreateJavaVM failed", following is
the logcat:-
E/flash_image( 439): error scanning partitions
E/mountd ( 430): could not read initial mass storage state
D/AndroidRuntime( 433):
D/AndroidRuntime( 433): >> AndroidRuntime START
<<
D/An
I have been trying to find some documentation on the exact
constituents for Goldfish but have been unsuccesful, is there some
documentation somewhere about exactly what Goldfish is, and thus what
must be removed/replaced when porting to hardware?
--~--~-~--~~~---~--~--
Here are some of my notes about it but this is from a diff from 2.6.25
and 2.6.25-android
diff -Naur linux-2.6.25/arch/arm/Kconfig kernel.git/arch/arm/
Kconfig
(goldfish remove)
diff -Naur linux-2.6.25/arch/arm/Makefile kernel.git/arch/arm/
Makefile
(Nothing to do only goldfish)
diff -Naur linux-
The previous list contain only files that contain goldfish stuff:
Here the list of files that are directly for goldfish:
[EMAIL PROTECTED] android-OMAP35xx]$ cat android-1.0_r1.patch | grep
"diff -Naur" | grep goldfish
diff -Naur linux-2.6.25/arch/arm/configs/goldfish_defconfig kernel.git/
arch/a
I would guess that your /data filesystem is not writeable:
E/dalvikvm( 450): Can't open dex cache '/data/dalvik-cache/
[EMAIL PROTECTED]@[EMAIL PROTECTED]': No such file or directory
I/dalvikvm( 450): Unable to open or create cache for /system/
framework/core.jar
On Fri, Nov 28, 2008 at 2:20 A
The QSC 6240 is an ARM CPU, isn't? If so, why do you need to port Dalvik to
it? Dalvik already runs on ARM CPUs.
On Wed, Nov 26, 2008 at 10:31 PM, iphong <[EMAIL PROTECTED]> wrote:
>
> Hi, I'm a android beginner.
>
> I want to porting only Dalvik VM on QSC 6240 Qualcomm original source.
> But,
Hi Ben,
I'm trying to port android to a s3c2410 develop board..which's only
64m ram..
now I've successfully built out armv4t images with your submitted
patch and sean's patches under reviewing.
but I'm getting servicemanager exiting problem while using nfs as
rootfs.
I'm doubting it's the binder
What version of the kernel are you using? Newer versions of the linux
kernel will pass VM_EXEC on mmap which will cause the binder to fail.
You might need to fix the binder so that it is no longer a
FORBIDDEN_MMAP_FLAGS.
lqoyzy wrote:
> Hi Ben,
>
> I'm trying to port android to a s3c2410 devel
