Database Develop

iDroid release 2 test preview uploaded l Samsung Dart SGH-T499 test build

Proudly presenting you the iOS styled ROM for Samsung Galaxy Mini
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
Android 2.3.7 - Cyanogenmod 7.2 official with lastest library and databases
JOYOS 1.1.9 from Huawei C8650
Status bar tab and re-designed for better UI
New multi-tasking UI
Browser tweaked
Roboto font with Unicode fixed
Fast, Fly and better user interface experience
3D Notification roll
And much more
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Changelogs:
Release 1:
Code:
Initial release
JOYOS 1.1.8 ported from LG P500
Re-designed status bar
Cyanogenmod 7.2 official for Galaxy Mini
Build.prop tweaked
Disabled byte-code verify
Zipalinged
Not working:
Wifi
Lockscreen and slide to power off
Camera
Video streaming playback
Release 2 preview:
Code:
JOYOS 1.1.9 ported from Huawei C8650
Redesigned status bar
Cyanogenmod 7.2 official kernel
3D notification roller
Option Carrier label on status bar
Option Max lines of notification roller
Battery percent option
New ringtones chooser
Camera working
Wifi working
Not working / BUG:
Lockscreen
Slide to power off
Download:
Release 2 test l Mirror (Password: buzz173 )
Release 2 test for Samsung Dart (SGH-T499) users l Mirror
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Release 1 l Mirror l Outdated
Update new clock and screenshot for release 1: http://forum.xda-developers.com/showthread.php?p=25739803#post25739803
How to flash:
Reboot into recovery
Wipe data and cache
Install from sd card and reboot
Go to setting -> Other -> CM setting -> Tablet tweaks -> Disable lockscreen (this will disable lockscreen so you can't unlock it )
If you want see lockscreen, don't tick Disable lockscreen . and wipe data/cache to reset

seems cool
and im gonna subscribe so I can keep up with your work
Sent from my GT-i9000 using xda premium

Credits:
JOYOS developer team
Squadzone, Mebitek and Cyanogenmod developer
Espier launcher developer team
Dsixda kitchen
UOT Kitchen

reserved*

android.process.acore fixed

buzz173 said:
android.process.acore fixed
Click to expand...
Click to collapse
Yeah I was waiting for this (ported Joy to mini and acore was fixed )... Can you tell me how to fixed the acore? Plz

Siznex said:
Yeah I was waiting for this (ported Joy to mini and acore was fixed )... Can you tell me how to fixed the acore? Plz
Click to expand...
Click to collapse
there is a problem with sqlite . very simple to fix. just copy and paste . LOL

I cant deodex this rom . logcat report this:
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\HOME>adb reboot
C:\Users\HOME>adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 97): Welcome to Android 2.3.7 / CyanogenMod-7.1.0-GalaxyMini-KANG
I/cm ( 98): _
I/cm ( 99): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 100): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 101): )) _))
I/cm ( 102):
I/logwrapper( 92): /system/xbin/run-parts terminated by exit(0)
I/DEBUG ( 133): debuggerd: Oct 8 2011 23:10:39
D/DHCP ( 141): failed to set ip addr for wlan0 to 0.0.0.0: No such device
--------- beginning of /dev/log/system
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 131): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 131): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted
)
I/Netd ( 132): Netd 1.0 starting
W/Vold ( 131): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 131): Ignoring unknown switch 'MSM72K_UDC'
D/AndroidRuntime( 135):
D/AndroidRuntime( 135): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 135): Heap size: -Xmx16m
D/AndroidRuntime( 135): CheckJNI is OFF
I/dalvikvm( 135): Zip is good, but no classes.dex inside, and no valid .odex fi
le in the same directory
D/dalvikvm( 135): Unable to process classpath element '/system/framework/core.j
ar'
D/dalvikvm( 135): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 135): ODEX file is stale or bad; removing and retrying (/data/dalvi
k-cache/[email protected]@[email protected])
D/dalvikvm( 135): DexOpt: --- BEGIN 'bouncycastle.jar' (bootstrap=1) ---
I/ ( 136): ServiceManager: 0xad50
I/AudioHardwareMSM72XX( 136): get_audpp_filter
I/AudioHardwareMSM72XX( 136): open /system/etc/AudioFilter.csv success.
D/AudioHardwareInterface( 136): setMode(NORMAL)
I/AudioHardwareMSM72XX( 136): Set master volume to 5.
I/QualcommCameraHardware( 136): getCameraInfo: IN
E/dalvikvm( 186): Too many exceptions during init (failed on 'Ljava/lang/NoClas
sDefFoundError;' 'java.lang.NoClassDefFoundError')
E/dalvikvm( 186): VM aborting
I/QualcommCameraHardware( 136): getCameraInfo: loading libqcamera at 0xb000e0e8
I/QualcommCameraHardware( 136): getCameraInfo: numOfCameras = 1
I/QualcommCameraHardware( 136): Camera sensor 0 info:
I/QualcommCameraHardware( 136): camera_id: 0
I/QualcommCameraHardware( 136): modes_supported: 1
I/QualcommCameraHardware( 136): position: 0
I/QualcommCameraHardware( 136): sensor_mount_angle: 90
I/QualcommCameraHardware( 136): getCameraInfo: OUT
D/AudioFlinger( 136): setParameters(): io 1, keyvalue routing=2, tid 188, calli
ng tid 136
I/AudioFlinger( 136): AudioFlinger's thread 0xcc48 ready to run
E/AudioHardwareMSM72XX( 136): doRouting CALLED, outputDevices = 0x2, mFmRadioEn
abled = 0
I/AudioHardwareMSM72XX( 136): Routing audio to Speakerphone
W/AudioHardwareMSM72XX( 136): Routing to 30 really (current: -1)
D/AudioHardwareMSM72XX( 136): doAudioRouteOrMute() device 1e, mMode 0, mMicMute
1, mBuiltinMicSelected 0, muted
E/AudioHardwareMSM72XX( 136): doRouting CALLED, outputDevices = 0x2, mFmRadioEn
abled = 0
I/AudioHardwareMSM72XX( 136): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 136): setVoiceVolume(1.000000)
I/AudioHardwareMSM72XX( 136): Setting in-call volume to 5 (available range is 0
to 7)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 133): Build fingerprint: 'samsung/GT-S5570/GT-S5570:2.3.4/GINGERBRE
AD/XXKPI:user/release-keys'
I/DEBUG ( 133): pid: 186, tid: 186 >>> /system/bin/dexopt <<<
I/DEBUG ( 133): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG ( 133): r0 fffffe88 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 133): r4 aca9e5fc r5 000270c8 r6 00000000 r7 fffffe88
I/DEBUG ( 133): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 133): ip aca9e708 sp bee08998 lr afd197f9 pc aca3fc6e cpsr 200
00030
I/DEBUG ( 133): d0 0000000000000000 d1 0000000000000000
I/DEBUG ( 133): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 133): d4 0000000000000000 d5 0000000000000000
I/DEBUG ( 133): d6 0000000000000000 d7 0000000000000000
I/DEBUG ( 133): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 133): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 133): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 133): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 133): scr 00000000
I/DEBUG ( 133):
-----------------------------------------------------------------------
????????????????????????????????? what wrong

buzz173 said:
there is a problem with sqlite . very simple to fix. just copy and paste . LOL
Click to expand...
Click to collapse
Wow really? oke I will try it and make my Joy in mini ,, thanks friend good Job
buzz173 said:
I cant deodex this rom . logcat report this:
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\HOME>adb reboot
C:\Users\HOME>adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 97): Welcome to Android 2.3.7 / CyanogenMod-7.1.0-GalaxyMini-KANG
I/cm ( 98): _
I/cm ( 99): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 100): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 101): )) _))
I/cm ( 102):
I/logwrapper( 92): /system/xbin/run-parts terminated by exit(0)
I/DEBUG ( 133): debuggerd: Oct 8 2011 23:10:39
D/DHCP ( 141): failed to set ip addr for wlan0 to 0.0.0.0: No such device
--------- beginning of /dev/log/system
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 131): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 131): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted
)
I/Netd ( 132): Netd 1.0 starting
W/Vold ( 131): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 131): Ignoring unknown switch 'MSM72K_UDC'
D/AndroidRuntime( 135):
D/AndroidRuntime( 135): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 135): Heap size: -Xmx16m
D/AndroidRuntime( 135): CheckJNI is OFF
I/dalvikvm( 135): Zip is good, but no classes.dex inside, and no valid .odex fi
le in the same directory
D/dalvikvm( 135): Unable to process classpath element '/system/framework/core.j
ar'
D/dalvikvm( 135): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 135): ODEX file is stale or bad; removing and retrying (/data/dalvi
k-cache/[email protected]@[email protected])
D/dalvikvm( 135): DexOpt: --- BEGIN 'bouncycastle.jar' (bootstrap=1) ---
I/ ( 136): ServiceManager: 0xad50
I/AudioHardwareMSM72XX( 136): get_audpp_filter
I/AudioHardwareMSM72XX( 136): open /system/etc/AudioFilter.csv success.
D/AudioHardwareInterface( 136): setMode(NORMAL)
I/AudioHardwareMSM72XX( 136): Set master volume to 5.
I/QualcommCameraHardware( 136): getCameraInfo: IN
E/dalvikvm( 186): Too many exceptions during init (failed on 'Ljava/lang/NoClas
sDefFoundError;' 'java.lang.NoClassDefFoundError')
E/dalvikvm( 186): VM aborting
I/QualcommCameraHardware( 136): getCameraInfo: loading libqcamera at 0xb000e0e8
I/QualcommCameraHardware( 136): getCameraInfo: numOfCameras = 1
I/QualcommCameraHardware( 136): Camera sensor 0 info:
I/QualcommCameraHardware( 136): camera_id: 0
I/QualcommCameraHardware( 136): modes_supported: 1
I/QualcommCameraHardware( 136): position: 0
I/QualcommCameraHardware( 136): sensor_mount_angle: 90
I/QualcommCameraHardware( 136): getCameraInfo: OUT
D/AudioFlinger( 136): setParameters(): io 1, keyvalue routing=2, tid 188, calli
ng tid 136
I/AudioFlinger( 136): AudioFlinger's thread 0xcc48 ready to run
E/AudioHardwareMSM72XX( 136): doRouting CALLED, outputDevices = 0x2, mFmRadioEn
abled = 0
I/AudioHardwareMSM72XX( 136): Routing audio to Speakerphone
W/AudioHardwareMSM72XX( 136): Routing to 30 really (current: -1)
D/AudioHardwareMSM72XX( 136): doAudioRouteOrMute() device 1e, mMode 0, mMicMute
1, mBuiltinMicSelected 0, muted
E/AudioHardwareMSM72XX( 136): doRouting CALLED, outputDevices = 0x2, mFmRadioEn
abled = 0
I/AudioHardwareMSM72XX( 136): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 136): setVoiceVolume(1.000000)
I/AudioHardwareMSM72XX( 136): Setting in-call volume to 5 (available range is 0
to 7)
I/DEBUG ( 133): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 133): Build fingerprint: 'samsung/GT-S5570/GT-S5570:2.3.4/GINGERBRE
AD/XXKPI:user/release-keys'
I/DEBUG ( 133): pid: 186, tid: 186 >>> /system/bin/dexopt <<<
I/DEBUG ( 133): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG ( 133): r0 fffffe88 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 133): r4 aca9e5fc r5 000270c8 r6 00000000 r7 fffffe88
I/DEBUG ( 133): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 133): ip aca9e708 sp bee08998 lr afd197f9 pc aca3fc6e cpsr 200
00030
I/DEBUG ( 133): d0 0000000000000000 d1 0000000000000000
I/DEBUG ( 133): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 133): d4 0000000000000000 d5 0000000000000000
I/DEBUG ( 133): d6 0000000000000000 d7 0000000000000000
I/DEBUG ( 133): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 133): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 133): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 133): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 133): scr 00000000
I/DEBUG ( 133):
-----------------------------------------------------------------------
????????????????????????????????? what wrong
Click to expand...
Click to collapse
Use Dsixda android kithcen...
I deodex the my LiGux port (alpha 2.1 not uploaded ) with Dsixda

Siznex said:
Use Dsixda android kithcen...
I deodex the my LiGux port (alpha 2.1 not uploaded ) with Dsixda
Click to expand...
Click to collapse
if you can, please deodex this rom and upload to mediafire . i don't know how to use dsixda . LOL

im downloading in the school... try in my house hehehe thanks bro..

japoina92 said:
im downloading in the school... try in my house hehehe thanks bro..
Click to expand...
Click to collapse
Please enable go locker before press turn off screen . Why ? Try it. you will khow this bug . i will fix this problem after i eraser chinese text on toggles noification bar

Good work

Cover flow
i found new feature. open music, choose and play a song. Rotate your device to landscape and enjoy

buzz173 said:
i found new feature. open music, choose and play a song. Rotate your device to landscape and enjoy
Click to expand...
Click to collapse
Chinese at notification Bar was fixed and change more icon thanks for porting the rom

This just has to be the most beautiful rom for Galaxy Mini. Good work, boy.

this rom deodexed . may be upload later
What changes in Alpha 1.1:
Newest EGL binaries tweaked from lg p500
boot.img tweaks
Deodexed
Zipalinged
Smartboot kernel with OC to 768Mhz (thanx to Squadzone)
Build.prop tweaks
New kernel modules
VGA video recording
...............

yahh cool waiting for it eagerly

beautiful.
is there any known-bugs?
are you just put a theme? it looks awesome.

lonestrider said:
beautiful.
is there any known-bugs?
are you just put a theme? it looks awesome.
Click to expand...
Click to collapse
yes, a lots of bug.
Cant show multitasking screen (may be CM7.1 bug)
Some app wrong layout because galaxy mini is ldpi
Chinese texts
EGL error (use quadrant , and use 3D benchmark. you will khow this problem)
...........................................................

MIUI.us v4 2.7.13 Porting Error

Hi,
I am noob to android. I recently started porting MIUI.us v4 2.7.13 to our device. (Spice MI410). I got boot animation successfully but, the phone enters to bootloop after that. I have followed the method suggested by CK and proxuser. And the logcat shows the below error.
E/dalvikvm( 227): ERROR: couldn't find native method
E/dalvikvm( 227): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimationI)V
E/JNIHelp ( 227): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 227): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
But both in my base ROM and MIUI ROM PowerManagerService is not available in com/android/server (After I decompiled the framework.jar)
Please help me???????

have you pm CK or elol? they manage to port miui, sure they can help you

azranashraf said:
have you pm CK or elol? they manage to port miui, sure they can help you
Click to expand...
Click to collapse
How to pm them?

Ibhi said:
Hi,
I am noob to android. I recently started porting MIUI.us v4 2.7.13 to our device. (Spice MI410). I got boot animation successfully but, the phone enters to bootloop after that. I have followed the method suggested by CK and proxuser. And the logcat shows the below error.
E/dalvikvm( 227): ERROR: couldn't find native method
E/dalvikvm( 227): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimationI)V
E/JNIHelp ( 227): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 227): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
But both in my base ROM and MIUI ROM PowerManagerService is not available in com/android/server (After I decompiled the framework.jar)
Please help me???????
Click to expand...
Click to collapse
Find it at services.jar

CacingKalung said:
Find it at services.jar
Click to expand...
Click to collapse
Thanks CK. I will try.

http://forum.xda-developers.com/showthread.php?t=1777999
maybe this thread will help you to port miui to our device,

Hi Thanks Guys.
Special thanks to azranashraf, for the xda reference and CK for resolving the Powermanager service question.
I had some issues in porting MIUI.us 2.7.13(I will post my issues later). SO I tried MIUI RD 2.5.25 and successfully booted in to lockscreen. But now the problem is I got an error message in the lockscreen which says com.android.phone process has stopped and even if I hit ok, it is not closing(Loop).
Can anyone help me with that?
Edit:
I also booted the MIUI.us 2.7.13 in to lockscreen(Fixed the Powermanager issues). But still this one is also having the same issues as my MIUI-RD. Soon I will post my logcat. Please help me with this.

Logcat for MIUI RD 2.5.25 (Process "Com.Android.Phone" has stopeed!!!
I/LockScreenResourceLoader( 227): root:Lockscreen
I/ContactsDatabaseHelper( 429): Bootstrapping database version: 634
I/ScreenElementRoot( 227): init target density: 240
D/dalvikvm( 227): GC_FOR_ALLOC freed 1118K, 24% free 12859K/16839K, paused 146ms
I/dalvikvm-heap( 227): Grow heap (frag case) to 21.271MB for 1536016-byte allocation
I/MiAdvancedView( 227): RenderThread started
I/TextScreenElement( 227): onVisibilityChange: true
I/TextScreenElement( 227): onVisibilityChange: false
I/TextScreenElement( 227): onVisibilityChange: true
W/ApplicationContext( 227): Unable to create files directory files
F/libc ( 121): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/ContactsProviderV1( 429): Bootstrapping database legacy support
D/dalvikvm( 227): GC_CONCURRENT freed 200K, 21% free 16178K/20295K, paused 4ms+10ms
I/DEBUG ( 116): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 116): Build fingerprint: 'GRJ22/V10a-OCT-05-2011.2ED317DCA9:user/release-keys'
I/DEBUG ( 116): pid: 121, tid: 298 >>> /system/bin/mediaserver <<<
I/DEBUG ( 116): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 116): r0 00014f58 r1 0000000b r2 00000000 r3 00014f40
I/DEBUG ( 116): r4 0000f9d0 r5 0000000b r6 00000002 r7 00000000
I/DEBUG ( 116): r8 00000001 r9 ffffffff 10 00000000 fp 00000000
I/DEBUG ( 116): ip 40f40658 sp 4166dbd0 lr 40032683 pc 00000000 cpsr 00060010
I/DEBUG ( 116): d0 7962646e6174533a d1 090a30203a746e20
I/DEBUG ( 116): d2 6f43797274655274 d3 000a30203a746e72
I/DEBUG ( 116): d4 7261486d090a3120 d5 30203a6572617764
I/DEBUG ( 116): d6 6d090a3039626678 d7 090a312d203a6446
I/DEBUG ( 116): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 116): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 116): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 116): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 116): d16 3fdb390135d1ac72 d17 4001540d31d1dd7f
I/DEBUG ( 116): d18 4000000000000000 d19 bfc540d31d1dd7f1
I/DEBUG ( 116): d20 3f1153849946b6ba d21 bebbb89c51a06d6e
I/DEBUG ( 116): d22 3ff0000000000000 d23 3feb390135d1ac72
I/DEBUG ( 116): d24 3e66376972bea4d0 d25 0000000000000000
I/DEBUG ( 116): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 116): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 116): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 116): scr 60000010
I/DEBUG ( 116):
I/DEBUG ( 116): #00 pc 00000000
I/DEBUG ( 116): #01 pc 00032680 /system/lib/libaudioflinger.so (_ZN7android12AudioFlinger4dumpEiRKNS_6VectorINS_8String16EEE)
I/DEBUG ( 116): #02 pc 00017d7c /system/lib/libbinder.so (_ZN7android7BBinder10onTransactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 116): #03 pc 000375f8 /system/lib/libmedia.so (_ZN7android14BnAudioFlinger10onTransactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 116): #04 pc 00026208 /system/lib/libaudioflinger.so (_ZN7android12AudioFlinger10onTransactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 116): #05 pc 00017f44 /system/lib/libbinder.so (_ZN7android7BBinder8transactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 116): #06 pc 0001b26e /system/lib/libbinder.so (_ZN7android14IPCThreadState14executeCommandEi)
I/DEBUG ( 116): #07 pc 0001b44a /system/lib/libbinder.so (_ZN7android14IPCThreadState14joinThreadPoolEb)
I/DEBUG ( 116): #08 pc 00020744 /system/lib/libbinder.so
I/DEBUG ( 116): #09 pc 00022a1e /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv)
I/DEBUG ( 116): #10 pc 00023064 /system/lib/libutils.so
I/DEBUG ( 116): #11 pc 00012d44 /system/lib/libc.so (__thread_entry)
I/DEBUG ( 116): #12 pc 00012874 /system/lib/libc.so (pthread_create)
I/DEBUG ( 116):
I/DEBUG ( 116): code around pc:
I/DEBUG ( 116): 00000000 ffffffff ffffffff ffffffff ffffffff ................
I/DEBUG ( 116): 00000010 ffffffff ffffffff ffffffff ffffffff ................
I/DEBUG ( 116): 00000020 ffffffff ffffffff ffffffff ffffffff ................
I/DEBUG ( 116): 00000030 ffffffff ffffffff ffffffff ffffffff ................
I/DEBUG ( 116): 00000040 ffffffff ffffffff ffffffff ffffffff ................
I/DEBUG ( 116):
I/DEBUG ( 116): code around lr:
I/DEBUG ( 116): 40032660 0004f8de f952f7fe 10d0f8d4 d3f0428f ......R......B..
I/DEBUG ( 116): 40032670 e0062600 46296be3 0026f853 6fc23601 .&...k)FS.&..6.o
I/DEBUG ( 116): 40032680 6c204790 d3f54286 0f00f1b8 f104d003 .G l.B..........
I/DEBUG ( 116): 40032690 f7ee0010 2000eba2 81fce8bd 00005afc ....... .....Z..
I/DEBUG ( 116): 400326a0 00007a56 00007a26 4ff0e92d f100b08b Vz..&z..-..O....
I/DEBUG ( 116):
I/DEBUG ( 116): stack:
I/DEBUG ( 116): 4166db90 4166dba4
I/DEBUG ( 116): 4166db94 40f3c5f7 /system/lib/hw/audio.primary.msm7x30.so
I/DEBUG ( 116): 4166db98 00000000
I/DEBUG ( 116): 4166db9c 40f3c63f /system/lib/hw/audio.primary.msm7x30.so
I/DEBUG ( 116): 4166dba0 000158d8 [heap]
I/DEBUG ( 116): 4166dba4 40f40268 /system/lib/hw/audio.primary.msm7x30.so
I/DEBUG ( 116): 4166dba8 00000000
I/DEBUG ( 116): 4166dbac 00000000
I/DEBUG ( 116): 4166dbb0 00000000
I/DEBUG ( 116): 4166dbb4 00000004
I/DEBUG ( 116): 4166dbb8 00000001
I/DEBUG ( 116): 4166dbbc 0000f9d0 [heap]
I/DEBUG ( 116): 4166dbc0 0000000b
I/DEBUG ( 116): 4166dbc4 00000001
I/DEBUG ( 116): 4166dbc8 df0027ad
I/DEBUG ( 116): 4166dbcc 00000000
I/DEBUG ( 116): #01 4166dbd0 0000f9d0 [heap]
I/DEBUG ( 116): 4166dbd4 00022d08 [heap]
I/DEBUG ( 116): 4166dbd8 0000f9d4 [heap]
I/DEBUG ( 116): 4166dbdc 4166dbf0
I/DEBUG ( 116): 4166dbe0 4166ddf0
I/DEBUG ( 116): 4166dbe4 4166dbf0
I/DEBUG ( 116): 4166dbe8 0000000b
I/DEBUG ( 116): 4166dbec 40135d7f /system/lib/libbinder.so
I/ActivityManager( 227): Start proc com.google.process.gapps for broadcast com.google.android.gsf/.loginservice.MigrateToAccountManagerBroadcastReceiver: pid=445 uid=10008 gids={3003, 1015, 1007, 2001, 3006}
I/ActivityManager( 227): Launching preboot mode app: ProcessRecord{415da678 445:com.google.process.gapps/10008}
D/GoogleLoginService( 445): no legacy android id exists to migrate
D/GoogleLoginService( 445): skipping migration because /data/data/com.google.android.gsf/databases/accounts.db doesn't exist
D/GoogleLoginService( 445): disabling the migration script since the migration is complete
I/ActivityManager( 227): Start proc android.process.media for broadcast com.android.providers.media/.MediaUpgradeReceiver: pid=459 uid=10011 gids={1015, 1023, 1024, 2001, 3003, 3007}
I/ActivityManager( 227): Launching preboot mode app: ProcessRecord{415e7a58 459:android.process.media/10011}
I/ActivityManager( 227): Writing new set of last done pre-boot receivers...
I/ActivityManager( 227): Removing system update proc: ProcessRecord{4147e6b0 415:com.android.providers.calendar/10006}
I/ActivityManager( 227): Killing proc 415:com.android.providers.calendar/10006: system update done
I/ActivityManager( 227): Removing system update proc: ProcessRecord{414bc630 429:android.process.acore/10000}
I/ActivityManager( 227): Killing proc 429:android.process.acore/10000: system update done
I/ActivityManager( 227): Removing system update proc: ProcessRecord{415da678 445:com.google.process.gapps/10008}
I/ActivityManager( 227): Killing proc 445:com.google.process.gapps/10008: system update done
I/ActivityManager( 227): Removing system update proc: ProcessRecord{415e7a58 459:android.process.media/10011}
I/ActivityManager( 227): Killing proc 459:android.process.media/10011: system update done
I/ActivityManager( 227): System now ready
I/SystemServer( 227): Making services ready
D/SystemServer( 227): Starting service: Intent { cmp=com.android.systemui/.SystemUIService }
I/ActivityManager( 227): Start proc com.android.systemui for service com.android.systemui/.SystemUIService: pid=473 uid=1000 gids={3003, 1015, 3002, 3001}
D/NetworkManagementService( 227): enabling bandwidth control
E/BandwidthController( 115): runIptablesCmd(): failed /system/bin/iptables -D INPUT -m owner --socket-exists res=256
E/BandwidthController( 115): runIptablesCmd(): failed /system/bin/ip6tables -D INPUT -m owner --socket-exists res=256
D/SystemUIService( 473): loading: class com.android.systemui.statusbar.phone.PhoneStatusBar
D/SystemUIService( 473): running: [email protected]
D/NetworkManagementService( 227): Registering observer
D/NetworkManagementService( 227): Registering observer
D/StorageNotification( 473): Startup with UMS connection false (media state unmounted)
E/miui.util.AudioOutputHelper( 227): android.os.DeadObjectException
W/AudioSystem( 227): AudioFlinger server died!
W/IMediaDeathNotifier( 227): media server died
W/AudioSystem( 227): AudioPolicyService server died!
I/ServiceManager( 113): service 'media.audio_flinger' died
I/ServiceManager( 113): service 'media.player' died
I/ServiceManager( 113): service 'media.camera' died
I/ServiceManager( 113): service 'media.audio_policy' died
I/DEBUG ( 116): debuggerd committing suicide to free the zombie!

its not complete logcat, maybe you can use tinypaste or pastebin to store your log
may I have look to your build prop?
also try radio logcat with "logcat -b radio"

Logcat for MIUI RD 2.5.25 (Process "Com.Android.Phone" has stopeed!!!
Thanks mate.
@ardx: Here is my complete logcat for MIUI RD 2.5.25
The base I used is 20120621-NIGHTLY-CM9-A99
http://pastebin.com/i4MytFtW
I have attached my build.prop also for your reference.
Also FYI, I am having the same "Unfortunately COM.ANDROID.PHONE process has been stopped" error in MIUI.US 2.7.13
Also attaching the logcat and build.prop for the above.
http://pastebin.com/TeD8TDru

problem is here
Code:
W/dalvikvm( 227): Unable to resolve superclass of Lcom/android/internal/telephony/LGEQualcommRIL; (4733)
W/dalvikvm( 227): Link of class 'Lcom/android/internal/telephony/LGEQualcommRIL;' failed
E/dalvikvm( 227): Could not find class 'com.android.internal.telephony.LGEQualcommRIL', referenced from method com.android.internal.telephony.PhoneFactory.makeDefaultPhone
W/dalvikvm( 227): VFY: unable to resolve new-instance 4706 (Lcom/android/internal/telephony/LGEQualcommRIL;) in Lcom/android/internal/telephony/PhoneFactory;
D/dalvikvm( 227): VFY: replacing opcode 0x22 at 0x0095
W/dalvikvm( 227): Unable to resolve superclass of Lcom/android/internal/telephony/LGEQualcommRIL; (4733)
W/dalvikvm( 227): Link of class 'Lcom/android/internal/telephony/LGEQualcommRIL;' failed
D/dalvikvm( 227): DexOpt: unable to opt direct call 0xc294 at 0x97 in Lcom/android/internal/telephony/PhoneFactory;.makeDefaultPhone
your base miui framework not have LGEQualcommRIL class that used in our phone.
try follow CK guide carefully

"unable to resolve new-instance 4706 (Lcom/android/internal/telephony/LGEQualcommRIL in Lcom/android/internal/telephony/PhoneFactory"
try to fix that.
You need to patch PhoneFactory.smali to construct your class instead of RIL:
find "RIL" word (there will be 2 entries) and replace them to "LGEQualcommRIL".
Make sure you've copied and replaced all RIL*.smali and copy LGEQualcommRIL*.smali at
/smali/com/android/internal/telephony ín framework.jar. Also copy QualcommSharedRIL.smali from that CM9 base. And also LGEQualcommUiccRIL.smali if exist (different CM9 base might be not exist).

CacingKalung said:
"unable to resolve new-instance 4706 (Lcom/android/internal/telephony/LGEQualcommRIL in Lcom/android/internal/telephony/PhoneFactory"
try to fix that.
You need to patch PhoneFactory.smali to construct your class instead of RIL:
find "RIL" word (there will be 2 entries) and replace them to "LGEQualcommRIL".
Yes, I did patched the PhoneFactory.smali to replace RIL with LGEQualcommRIL
Make sure you've copied and replaced all RIL*.smali and copy LGEQualcommRIL*.smali at
/smali/com/android/internal/telephony ín framework.jar. Also copy QualcommSharedRIL.smali from that CM9 base. And also LGEQualcommUiccRIL.smali if exist (different CM9 base might be not exist).
Click to expand...
Click to collapse
I did that too. If I copy QualcommSharedRIL.smali, then I am getting some error. I am having a logcat for that. Soon I will upload that too.
Thanks for replies.

New ROM for our Device Ready RD MIUI 2.5.25
Guys,
Finally by all your help, I made it. Successfully ported RD MIUI 2.5.25(by dekky) to our device. This is the first ROM I am porting. So I am testing the basic functions now. Soon I will upload this ROM and create a new Thread.(The issue is that I havent made 10 post yet. After 10 only I can Create threads in the development section).
Thanks to all forum guys. Special thanks to CK, aRDX and azranashraf for helping me out.
More coming soon...
I I could not find Camera app

Ibhi said:
Guys,
Finally by all your help, I made it. Successfully ported RD MIUI 2.5.25(by dekky) to our device. This is the first ROM I am porting. So I am testing the basic functions now. Soon I will upload this ROM and create a new Thread.(The issue is that I havent made 10 post yet. After 10 only I can Create threads in the development section).
Thanks to all forum guys. Special thanks to CK, aRDX and azranashraf for helping me out.
More coming soon...
I I could not find Camera app
Click to expand...
Click to collapse
good Ibhi.... for making 10, post thanks in other thread ... that can help you .. also for making thread you need to have 40 post, 10 post barrier is for commenting in development section, so you can post thread in general section, then we can request moderator to shift it to development section (these are rules from what I am aware, not read it in rule book hence may be I am wrong)
Best of luck Ibhi for your first port ...:good:

[Q&A] [FreeXperia Project] AOSP Android 5.x.x

Q&A for [FreeXperia Project] AOSP Android 5.x.x
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FreeXperia Project] AOSP Android 5.x.x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Getting issues with modem from logcat:
Code:
<6>[ 224.145049] pil-q6v5-mss fc880000.qcom,mss: mba: loading from 0x0d100000 to 0x0d13a000
<4>[ 224.151677] ------------[ cut here ]------------
<4>[ 224.155406] WARNING: at kernel/irq/manage.c:428 enable_irq+0x60/0x74()
<4>[ 224.161837] Unbalanced enable for IRQ 413
<6>[ 224.165888] Modules linked in:
<6>[ 224.165915] [<c010bf04>] (unwind_backtrace+0x0/0x11c) from [<c0194c58>] (warn_slowpath_common+0x4c/0x64)
<6>[ 224.165932] [<c0194c58>] (warn_slowpath_common+0x4c/0x64) from [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c)
<6>[ 224.165950] [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c01f3d7c>] (enable_irq+0x60/0x74)
<6>[ 224.165972] [<c01f3d7c>] (enable_irq+0x60/0x74) from [<c01312fc>] (pil_boot+0x7d8/0x9cc)
<6>[ 224.165990] [<c01312fc>] (pil_boot+0x7d8/0x9cc) from [<c013374c>] (mss_start+0x24/0x5c)
<6>[ 224.166009] [<c013374c>] (mss_start+0x24/0x5c) from [<c0162fc8>] (subsystem_get+0x94/0x168)
<6>[ 224.166030] [<c0162fc8>] (subsystem_get+0x94/0x168) from [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c)
<6>[ 224.166047] [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c) from [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8)
<6>[ 224.166065] [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8) from [<c0764cc8>] (sock_ioctl+0x228/0x278)
<6>[ 224.166086] [<c0764cc8>] (sock_ioctl+0x228/0x278) from [<c0263074>] (vfs_ioctl+0x28/0x3c)
<6>[ 224.166103] [<c0263074>] (vfs_ioctl+0x28/0x3c) from [<c0263ab8>] (do_vfs_ioctl+0x484/0x574)
<6>[ 224.166119] [<c0263ab8>] (do_vfs_ioctl+0x484/0x574) from [<c0263bf0>] (sys_ioctl+0x48/0x74)
<6>[ 224.166138] [<c0263bf0>] (sys_ioctl+0x48/0x74) from [<c0105ea0>] (ret_fast_syscall+0x0/0x30)
<4>[ 224.166149] ---[ end trace 1ffe67af4bf01ba1 ]---
<3>[ 224.205132] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -284491765
<3>[ 224.212540] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to bring out of reset
<3>[ 224.219243] modem_notifier_cb: sysmon_send_event error -19
<3>[ 224.224639] M-Notify: General: 5
<3>[ 224.227804] msm_ipc_load_default_node: Failed to load modem
I reported this over in the kernel thread http://forum.xda-developers.com/showpost.php?p=57625416&postcount=23 it appears everything is still broken.
Also Wifi kills the whole system:
Code:
I/WifiHAL ( 652): Initialized Wifi HAL Successfully; vendor cmd = 103
D/wifi ( 652): Did set static halHandle = 0xafa4e040
D/wifi ( 652): halHandle = 0xafa4e040, mVM = 0xb505c280, mCls = 0x300ec6
E/wifi ( 652): getStaticLongField sWifiHalHandle 0xa06f381c
D/wifi ( 652): array field set
W/Adreno-EGL( 198): <qeglDrvAPI_eglDupNativeFenceFDANDROID:6527>: EGL_BAD_PARAMETER
W/SurfaceFlinger( 198): captureScreen: failed to dup sync khr object
E/audio_a2dp_hw( 241): adev_set_parameters: ERROR: set param called even when stream out is null
F/libc ( 652): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4300001 in tid 1595 (WifiStateMachin)
I/WifiNative-HAL( 652): Waiting for HAL events mWifiHalHandle=-1348149184
D/wifi ( 652): waitForHalEvents called, vm = 0xb505c280, obj = 0x300ec6, env = 0xafd22320
E/wifi ( 652): getStaticLongField sWifiHalHandle 0x9aa39b1c
I/DEBUG ( 238): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 238): Build fingerprint: 'Sony/aosp_d5803/aries:5.0.2/LRX22G/root12250659:userdebug/test-keys'
I/DEBUG ( 238): Revision: '0'
I/DEBUG ( 238): ABI: 'arm'
I/DEBUG ( 238): pid: 652, tid: 1595, name: WifiStateMachin >>> system_server <<<
I/DEBUG ( 238): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4300001
I/DEBUG ( 238): r0 04300001 r1 b3f279f8 r2 b3f1a885 r3 ffffffa8
I/DEBUG ( 238): r4 00000000 r5 04300001 r6 00000000 r7 b3f27dcc
I/DEBUG ( 238): r8 b3f1a885 r9 a1e4b400 sl 00000001 fp 130337c0
I/DEBUG ( 238): ip b3f27f20 sp a06f3820 lr b3f1dd4d pc b3f1dd4c cpsr 600d0030
I/DEBUG ( 238):
I/DEBUG ( 238): backtrace:
I/DEBUG ( 238): #00 pc 00007d4c /system/lib/libwifi-service.so (getWifiHandle(wifi_interface_info*)+5)
I/DEBUG ( 238): #01 pc 00007d53 /system/lib/libwifi-service.so (getHalInfo(wifi_interface_info*)+2)
I/DEBUG ( 238): #02 pc 0000b37d /system/lib/libwifi-service.so (wifi_get_link_stats+28)
I/DEBUG ( 238): #03 pc 0000421d /system/lib/libwifi-service.so
I/DEBUG ( 238): #04 pc 0003623d /data/dalvik-cache/arm/[email protected]@[email protected]
E/Sensors ( 4229): sns_smr_util.c(104):Unable to initialize service 256 with QCCI, timed out (10000 ms)
E/Sensors ( 4229): sns_sam_mr.c(1016):Unable to initialize service 0 with QCCI
E/Sensors ( 4229): sns_sam_mr.c(1111):Unable to acquire service handle 0
E/Sensors ( 4229): mag_cal.c(1603):mag_cal_sam_init: Unknown UUID(1) 00000000-0000-0000
E/Sensors ( 4229): mag_cal.c(1608):mag_cal_sam_init: Unknown UUID(2) 0000-000000000000
E/Sensors ( 4229): sns_sam.c(4432):Failed to register algorithm service 16 with SAM
I/DEBUG ( 238):
I/DEBUG ( 238): Tombstone written to: /data/tombstones/tombstone_01
I/ServiceManager( 196): service 'connectivity' died
I/ServiceManager( 196): service 'servicediscovery' died
W/Sensors ( 2552): sensorservice died [0xacc5e0c0]
I/ServiceManager( 196): service 'updatelock' died
I/ServiceManager( 196): service 'notification' died
I/ServiceManager( 196): service 'devicestoragemonitor' died
I/ServiceManager( 196): service 'location' died
I/ServiceManager( 196): service 'country_detector' died
I/ServiceManager( 196): service 'search' died
I/ServiceManager( 196): service 'dropbox' died

any reason aries isn't built ? at least not that I could find on the fxp open source repo.

https://github.com/CyanogenMod/andr...mmit/61f48baf5669c2a21b0a510515c985dec87617b5
fixes this problem

The guide for building AOSP is not clear for certain points,
For devices with Qualcomm wireless hardware, you need to build a Prima or Pronto WLAN module in order to get Wi-Fi working. Follow the instructions below to do this.
Then compile the module by entering the device specific command listed below.​Which should we follow for z3-compact, as device is not mentioned:
Prima?
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j12 -C M=$PWD CONFIG_PRIMA_WLAN=m CONFIG_PRIMA_WLAN_LFR=y KERNEL_BUILD=1 WLAN_ROOT=$PWD​
Once the compilation is finished, the wlan.ko module can be found in the prima folder.​Where do we put wlan.ko ?
Also,
the guide for AOSP has the kernel and wifi repos in the local manifest, does it build them during compilation or do we have to build them manually|separately, and then copy the kernel and wifi module before compiling ROM?
Thank you for your time,
hoping to see a fully working AOSP soon, keeping fingers crossed.
As it is a shame to see a phone with great HW and design dragging behind the rest.
I hope to see Sony advance and reach full capabilities

Any news about a working camera for 3.10 kernel and AOSP rom ?
Envoyé de mon Xperia Z3C en utilisant Tapatalk

After camera replace (purple tint unfixable) problem with taking pictures.

Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance

camelek said:
Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance
Click to expand...
Click to collapse
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs

donkeykong1 said:
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs
Click to expand...
Click to collapse
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.

camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Well, backup your current ROM and flash any Sense or GPE ROM and try. I know that all CM or AOSP ROMs have that crashing camera bug
dey tuuk ur juurbs

camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Try with cameringo app first...

Ok, quick summary:
Cameringo (even Lite version) working fine, but I think it's again similar trick is used in Instagram - because always after taking picture there is "picture taken" intent/screen and after press back (or camera button in Instagram) camera is reinitialized. But this app doing this so quick that it's fully acceptable.
With stock ROMs I've came through some hell ride as using AICP or RR my /data was as F2FS partition. So backup whole storage, changing fs, flashing old Lollipop - long story short: never more Anyway camera working fine with HTC app or Lollipop ROM (like Venom), but this unfortunately is not an option, going back to easy hackable system because of camera.
Anyway, thanks for suggestions.

[VNS-L31][EMUI4.1] RustyKernel [P9 Lite]

Disclaimer:
I am not responsible for the outcome of you flashing this software, please backup your current boot partition before flashing this kernel.
Click to expand...
Click to collapse
While I will take some credit for this work, I am not a Developer; I'm a hobbyist - I'll accept any help I can get to improve this kernel.
Downloads are in the download section
Source RUSTY-VNS
Credits:
@twicejr
@kwoktopus
Changes from stock:
2017-03-16 No-Root
2017-03-16 Root
3.10.102
Optimized build flags
Intelliactive CPU Governor
RustyKernel-EMUI4.1_hi6250-2017-03-17
RustyKernel-PA6.0.1_hi6250-2017-03-17 - Lockscreen bug, disable lockscreen security before flashing (PIN/Patten/Password)
Intelliplug Hotplug
Thunderplug Hotplug
PA 6.0.1 Support
Known bugs:
Kernel Adiutor:
Code:
big: Failed to load frequencies
. They're running, just not being logged.
PA version has a lockscreen bug - disable secure lockscreen before flashing
XDA:DevDB Information
P9 Lite Kernel, Kernel for the Huawei P9 Lite
Contributors
Carlyle_f
Source Code: https://github.com/carlyle-felix/RUSTY-VNS
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2017-03-17
Beta Release Date: 2017-03-16
Created 2017-03-16
Last Updated 2017-03-17

Reserved

Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.

You can make oeminfo l31c636

pilgrim011 said:
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
Click to expand...
Click to collapse
Thanks man, I will look into OTG. Also, next releases will all have root
Sent from my HUAWEI VNS-L31 using Tapatalk

http://cloud.tapatalk.com/s/58cb6f4e67c55/RustyKernel_hi6250-2017-03-16.zip
Testers please leave feedback
Intelliplug and thunder plug hotplugs
Sent from my HUAWEI VNS-L31 using Tapatalk

Since this kernel supports PA, does it support LineageOS 13, or 14/RR?

dariomrk said:
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
Click to expand...
Click to collapse
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.

dady000 said:
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
Click to expand...
Click to collapse
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk

Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
No, not yet, I will try it later. What I tried is the Avsky's kernel.

What are the advantages of using this kernel? And how do you install it? Noob here

SALVO9 said:
What are the advantages of using this kernel? And how do you install it? Noob here
Click to expand...
Click to collapse
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:

Carlyle_f said:
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Click to expand...
Click to collapse
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one

SALVO9 said:
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
Click to expand...
Click to collapse
Alright, the benefits of this kernel is listed under changelog in OP
Sent from my HUAWEI VNS-L31 using Tapatalk

Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0

Delete

dady000 said:
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Click to expand...
Click to collapse
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock before flashing kernel. huge security breach but should satisfy those who are okay with slide to unlock for now.

Carlyle_f said:
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock. huge security breach but should satisfy those who are okay with slide to unlock for now.
Click to expand...
Click to collapse
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.

dady000 said:
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
Click to expand...
Click to collapse
hi can you please try the new build before i include it in OP:
https://forum.xda-developers.com/devdb/project/dl/?id=23699

Considering kernel is essential to make your device work, if you put a incompatible kernel on your device, what are the consequences?
Will the recovery still be bootable considering it has its own partition. In case the recovery is bootable, I'm willing to test on my VNS-L31.
Also in that case i could try on other roms, example CM13, Los14, etc...