LWW installation was compromissed, aborting mission....for now.

Please expeacer do you had the logs?

DDM log are here ::


https://www.dropbox.com/sh/5yy4d76fezfatgp/IFkZ6k3oiE



06-10 19:24:49.805: A/libc(415): Fatal signal 11 (SIGSEGV) at 0x00000004 (code=1)
06-10 19:24:49.906: I/ActivityManager(316): Start proc com.miui.home for activity com.miui.home/.launcher.Launcher: pid=542 uid=10025 gids={1015, 3003}
06-10 19:24:50.135: W/ActivityThread(316): ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLo ader());
06-10 19:24:50.145: I/ActivityThread(470): Pub downloads: com.android.providers.downloads.DownloadProvider
06-10 19:24:50.235: I/ActivityThread(508): Pub com.sonyericsson.provider.customization: com.sonyericsson.provider.customization.Customizat ionProvider
06-10 19:24:50.235: I/ServiceManager(414): Waiting for service phone...
06-10 19:24:50.276: I/ActivityThread(523): Pub com.lbe.security.miui.privacy.content: com.lbe.security.service.privacy.DummyContentProvi der


--------------------------------------------------------------------------------
Last edited by rompowder; Today at 10:21 PM. Reason: log

the only missed method in the logcat is this

01-06 00:03:42.845: E/PhonePolicy(520): Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$Conte xtMenuCallback

and this too

01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/Roboto-Regular.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/Roboto-Bold.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/Roboto-Italic.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/Roboto-BoldItalic.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSerif-Regular.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSerif-Bold.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSerif-Italic.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSerif-BoldItalic.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSans.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSans-Bold.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSansMono.ttf> as a font
01-06 00:03:45.595: D/skia(684): ---- failed to open </data/fonts/DroidSansHebrew-Bold.ttf> as a font

dont read the fonts like fonts... :S strange...

another thing... for fix misplaced keyboard do you need to replace the LatinIme.apk in system/app with the LatinIme.apk from cm9


EDIT: only for test.... to verify my theory..... can anyone change his pixel density to 240? all will be bigger but i need to check if the black bar in notificacion bar is there yet...

Oh, please someone say "it is working perfectly on LWW". @expeacer, please do something.

Hi, how to change hardware keyboard an AZERTY ?
Thanks

Envoyé depuis mon SK17i avec Tapatalk

Sad Sunday ;(

Originally Posted by dhk.-

the only missed method in the logcat is this



and this too



dont read the fonts like fonts... :S strange...

another thing... for fix misplaced keyboard do you need to replace the LatinIme.apk in system/app with the LatinIme.apk from cm9


EDIT: only for test.... to verify my theory..... can anyone change his pixel density to 240? all will be bigger but i need to check if the black bar in notificacion bar is there yet...

But you know, it's FULLY as same as ROM, which working perfectly on Mini/MiniPro/Active, and don't work in LwW. It's very strange for me.
I'll make a completly new build tomorrow only for LwW...

good job dude

litle things I wanna ask
this rom have NON qwerty keyboard?

which baseband I must use?
now I use .58 baseband and use ur customrom

thanks

Originally Posted by expeacer

But you know, it's FULLY as same as ROM, which working perfectly on Mini/MiniPro/Active, and don't work in LwW. It's very strange for me.
I'll make a completly new build tomorrow only for LwW...

Great news.

No no, best news for today. Thank you so much.

Great job! And for the Xperia Keyboard, just push textinput-tng.apk from the previous ROM to /system/app/ and select it in the Keyboard configuration menu.

For the physical keyboard in Mini Pro, I don't know about non-latin ones but I've lately been fixing mine with the following:

Go with any file explorer that can do root and access system and browse here:

/system/usr/keyboard-config/

then check the different available layouts in the "layouts" folder. Take note to the one you want and go back to the previous folder. Then open "keyprint.xml" and locate this line:

<Script name:"latin" keylayout="qwerty-en"/>

And change it to the one you need. In my case it is:

<Script name:"latin" keylayout="qwerty-br"/>

Save the file (be sure you activated Root access and mount /system/ as RW if you're using ES File Explorer, can't help about other browsers though) and reboot.

As I stated, this is a quick hack-job and should work with latin keyboards (qwerty of any type, azerty, qwertz...), I don't know what happens if you mess with non-latin ones like thai or arabic so MAKE A BACKUP JUST IN CASE.