X509KeyManager missing on GB?

[Edgard Castro]

I'm having a little issue during bootup where X509KeyManager can't be found. I understand that bouncycastle was incorporated on GB, but whats the catch on this one?

By the way, is there any target similar to "otapackage", which also seems to not work anymore?

[Jason]

I am experiencing the same boot loop, and unsure of how to fix this:

E/Zygote ( 925): Error preloading android.net.http.HttpsConnection.
E/Zygote ( 925): java.lang.ExceptionInInitializerError
E/Zygote ( 925): at java.lang.Class.classForName(Native Method)
E/Zygote ( 925): at java.lang.Class.forName(Class.java:234)
E/Zygote ( 925): at java.lang.Class.forName(Class.java:181)
E/Zygote ( 925): at
com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:297)
E/Zygote ( 925): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:564)
E/Zygote ( 925): at dalvik.system.NativeStart.main(Native Method)
E/Zygote ( 925): Caused by: java.lang.RuntimeException:
java.security.KeyManagementException: No X509KeyManager found
E/Zygote ( 925): at
android.net.http.HttpsConnection.initializeEngine(HttpsConnection.java:
108)
E/Zygote ( 925): at
android.net.http.HttpsConnection.<clinit>(HttpsConnection.java:65)
E/Zygote ( 925): ... 6 more
E/Zygote ( 925): Caused by: java.security.KeyManagementException: No
X509KeyManager found
E/Zygote ( 925): at
org.apache.harmony.xnet.provider.jsse.SSLParametersImpl.<init>(SSLParametersImpl.java:
125)
E/Zygote ( 925): at
org.apache.harmony.xnet.provider.jsse.SSLContextImpl.engineInit(SSLContextImpl.java:
97)
E/Zygote ( 925): at
android.net.http.HttpsConnection.initializeEngine(HttpsConnection.java:
101)
E/Zygote ( 925): ... 7 more
E/Zygote ( 925): setreuid() failed. errno: 2

[othy74]

Same thing for me.

[tluu]

This was an init.rc issue for me. I could get passed this when I used
the default init.rc for GB.

[othy74]

This does not really help me further I'm afraid. I'm running into the
"No X509KeyManager found" loop on my N1 after flashing a clean GB
build, using the default 14053 bytes init.rc.
Having no such issues when building for the emulator.

[Samuel B. Quiring]

--
You received this message because you are subscribed to the "Android
Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

[Jean-Baptiste Queru]

I've been trying to reproduce this issue on my side.

I've tried both master and gingerbread. Clean build (rm -rf out), pure
open-source tree with no proprietary drivers. lunch
full_passion-userdebug, flashed with fastboot -w flashall, running
(obviously) on passion.

This is on Ubuntu 10.4, with Sun JDK 1.6.

I haven't seen any such issue. The system boots fine for me.

JBQ

> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Edgard Castro]

Using the new init.rc fixed for me, guess it was just the bootloadclass. :)

[othy74]

OK, flashing boot.img before system.img fixes the issue. Simple.
I tried to avoid "flashall" in order to keep recovery in place and
forgot about boot...
Wow GB!! But I see some very looong white screen transitions.

[Jean-Baptiste Queru]

Ah, that totally makes sense. A mismatch of the boot and system
partitions is likely to have such unfortunate effects.

I've heard that the issue with the white screens comes from some kind
of mismatch between gingerbread and the froyo graphics drivers for
passion.

JBQ

[Edgard Castro]

You probably have to disable RGBX_8888 on passion, look at cyanogen commit:

https://github.com/CyanogenMod/android_frameworks_base/commit/baa078471f4198bd73819794f2713a845305a227

[othy74]

Thanks for the pointer. Now this is much better :)

On Dec 20, 10:07 pm, Edgard Castro <edgardcas...@gmail.com> wrote:
> You probably have to disable RGBX_8888 on passion, look at cyanogen commit:
>

> https://github.com/CyanogenMod/android_frameworks_base/commit/baa0784...