Database Develop

How to build eclair for cdma device

Hi, all
Now i want to build eclair for a cdma device,but if i set "ro.telephony.default_network = 4" in the system.prop , it occured a error "The com.android.phone" has stopped unexpectedly, please try again" in the home screen .
I want to know how to build eclair for a cdma device?
Thanks
log:
D/AT ( 685): AT> ATE0Q0V1
D/AT ( 685): AT< OK
D/AT ( 685): AT> ATE0Q0V1
D/AT ( 685): AT< OK
D/AT ( 685): AT> ATS0=0
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CMEE=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CREG=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CCWA=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CMUT=0
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CLIP=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CLIR=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CMGF=1
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CSQ
D/AT ( 685): AT< +CSQ: 99,99
D/AT ( 685): AT< OK
D/AT ( 685): AT> AT+CFUN?
D/AT ( 685): AT< +CFUN: 4
D/AT ( 685): AT< OK
I/PHONE ( 780): Network Mode set to 4
I/PHONE ( 780): Cdma Subscription set to 1
I/RILJ ( 780): Connected to 'rild' socket
I/RILC ( 685): libril: new connection
I/RILC ( 685): RIL Daemon version: android reference-ril 1.0
D/RILB ( 780): Notifying: radio available
D/RILJ ( 780): [0000]> SCREEN_STATE: true
D/RILJ ( 780): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_OFF
D/RIL ( 685): onRequest: SCREEN_STATE
D/RILJ ( 780): [0000]< SCREEN_STATE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/PHONE ( 780): mDoesRilSendMultipleCallRing=true
D/PHONE ( 780): mCallRingDelay=3000
D/CDMA ( 780): [CdmaDataConnection] DataConnection.clearSettings()
D/CDMA ( 780): [CdmaDataConnection] CdmaDataConnection <constructor>
Best wishes
Ant

Could you give us a little bit more information? Are you building for a vogue? Or something else?

hi,mssmison
i build eclair for gsm device successful, now i am building for a cdma device but not vogue. I don't know how to build it, any compiled settings?
Any docs or source code build for a vogue. I want to try
Thanks
Ant

what device are you building it for? Do you have a manifest for that device?
Generally your RIL will do the conversion work unless you need specific frameworks (which you shouldn't, as the vogue is a cdma device)

[Q] Nexus One - Blank screen

I am having very strange issues with my Nexus One. It seems to be having issues with later versions of Kernel and recoveries!! I have tried flashing almost all the custom ROM's and it ends up with a blank screen. Nothing gets displayed. But the touchscreen and phone itself works. Because I can get calls and I can see everything using android screencast program on my desktop.
To resolve the issue, I always flash 2.6.35.4_SVS-925mV_CFS_AXI_720p_1113MHz_082710 on top of any ROM I install. This has been the case with every ROM. Trust me, I have tried almost every ROM out there! I was running adb shell bugreport and found the below error (highlighted in bold). Is this what is causing the problem? Any ideas how to resolve it?
11-17 11:38:40.267 I/SurfaceFlinger( 174): SurfaceFlinger is starting
11-17 11:38:40.267 I/SurfaceFlinger( 174): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
11-17 11:38:40.277 I/qsd8k.gralloc( 174): using (fd=29)
11-17 11:38:40.277 I/qsd8k.gralloc( 174): id = msmfb
11-17 11:38:40.277 I/qsd8k.gralloc( 174): xres = 480 px
11-17 11:38:40.277 I/qsd8k.gralloc( 174): yres = 800 px
11-17 11:38:40.277 I/qsd8k.gralloc( 174): xres_virtual = 480 px
11-17 11:38:40.277 I/qsd8k.gralloc( 174): yres_virtual = 1600 px
11-17 11:38:40.277 I/qsd8k.gralloc( 174): bpp = 32
11-17 11:38:40.277 I/qsd8k.gralloc( 174): r = 0:8
11-17 11:38:40.277 I/qsd8k.gralloc( 174): g = 8:8
11-17 11:38:40.277 I/qsd8k.gralloc( 174): b = 16:8
11-17 11:38:40.277 I/qsd8k.gralloc( 174): width = 48 mm (254.000000 dpi)
11-17 11:38:40.277 I/qsd8k.gralloc( 174): height = 80 mm (254.000000 dpi)
11-17 11:38:40.277 I/qsd8k.gralloc( 174): refresh rate = 60.00 Hz
11-17 11:38:40.297 D/libEGL ( 174): loaded /system/lib/egl/libGLES_android.so
11-17 11:38:40.347 D/libEGL ( 174): loaded /system/lib/egl/libEGL_adreno200.so
11-17 11:38:40.457 D/libEGL ( 174): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
11-17 11:38:40.467 D/libEGL ( 174): loaded /system/lib/egl/libGLESv2_adreno200.so
11-17 11:38:40.627 E/libEGL ( 174): eglSetSwapRectangleANDROID:1909 error 3008 (EGL_BAD_DISPLAY)
11-17 11:38:40.627 I/SurfaceFlinger( 174): EGL informations:
11-17 11:38:40.627 I/SurfaceFlinger( 174): # of configs : 53
11-17 11:38:40.627 I/SurfaceFlinger( 174): vendor : Android
11-17 11:38:40.627 I/SurfaceFlinger( 174): version : 1.4 Android META-EGL
11-17 11:38:40.627 I/SurfaceFlinger( 174): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_ANDROID_image_native_buffer EGL_ANDROID_swap_rectangle EGL_ANDROID_get_render_buffer
11-17 11:38:40.627 I/SurfaceFlinger( 174): Client API: OpenGL ES
11-17 11:38:40.627 I/SurfaceFlinger( 174): EGLSurface: 8-8-8-8, config=0x9
11-17 11:38:40.627 I/SurfaceFlinger( 174): OpenGL informations:
11-17 11:38:40.627 I/SurfaceFlinger( 174): vendor : Qualcomm
11-17 11:38:40.627 I/SurfaceFlinger( 174): renderer : Adreno 200
11-17 11:38:40.627 I/SurfaceFlinger( 174): version : OpenGL ES-CM 1.1
11-17 11:38:40.627 I/SurfaceFlinger( 174): extensions: GL_AMD_compressed_3DC_texture GL_AMD_compressed_ATC_texture GL_OES_EGL_image GL_OES_blend_equation_separate GL_OES_blend_func_separate GL_OES_blend_subtract GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_framebuffer_object GL_OES_matrix_palette GL_OES_point_size_array GL_OES_point_sprite GL_OES_read_format GL_OES_stencil_wrap GL_OES_texture_cube_map GL_OES_texture_env_crossbar GL_OES_texture_mirrored_repeat
11-17 11:38:40.627 I/SurfaceFlinger( 174): GL_MAX_TEXTURE_SIZE = 4096
11-17 11:38:40.627 I/SurfaceFlinger( 174): GL_MAX_VIEWPORT_DIMS = 4096
11-17 11:38:40.627 I/SurfaceFlinger( 174): flags = 00000000

May not be the issue but I had some blank screen problems first time I rooted my N1 because I has accidentally flashed an AMOLED only recovery image on my SLCD N1.
Unlikely to be the fault as you sound like you know what you're doing but just in case I thought I'd tell you.

I saw this on another thread somewhere on the forum, someone who had the same problem as you. Now it's not to discourage you but I don't remember finding a solution :/ now that doesn't mean we can't try but unfortunately since you've tried a lot of ROMs the only thing I can think of other than a radio flash would be to try passimg to get back to stock.

Dude Random21 said:
I saw this on another thread somewhere on the forum, someone who had the same problem as you. Now it's not to discourage you but I don't remember finding a solution :/ now that doesn't mean we can't try but unfortunately since you've tried a lot of ROMs the only thing I can think of other than a radio flash would be to try passimg to get back to stock.
Click to expand...
Click to collapse
Probably it was me!!! I tried installing Gingerbread ROM some time back. It ended up with the same problem. I have been thinking if its really a hardware issue and just use whatever works..

[Q] Signal drops

Hi, I was having strange signal drop issues, because the signal drops from 3 or 4 bars to nothing, at any moment and I just get that when my signal drops, I have this in the logcat.
Code:
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_full() s_commandmutex[5] UNLOCKED, tid:134936, err - 0
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_full() end; err:0
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_singleline() end; err:0
04-15 02:33:05.447 D/RILC ( 964): [0604]< LGE_GET_HSDUPA_VALUES fails by E_GENERIC_FAILURE
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: requestInterface(LGE_GET_HSDUPA_VALUES) invoking *requestFunction(req:291, data: 0x00000000, len:0)...DONE
04-15 02:33:05.447 D/RIL ( 964): lge-ril: RIL_RequestDataCleanup START
04-15 02:33:05.447 D/RIL ( 964): lge-ril: RIL_RequestDataCleanup END
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: requestInterface(LGE_GET_HSDUPA_VALUES) handled
04-15 02:33:05.447 D/RIL ( 964): dlc[5]: lge-ril: waitForMessage() START. tid - 134936, head - 0x0, No of pending reqs - 0, srv state - 1
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: waitForMessage waiting for message. thread id - 134936
04-15 02:33:05.447 D/RILJ ( 2180): removeRequest() LGE_GET_HSDUPA_VALUES
04-15 02:33:05.447 D/RILJ ( 2180): [0604]< LGE_GET_HSDUPA_VALUES error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
04-15 02:33:05.447 D/GSM ( 2180): nitzName = null
04-15 02:33:05.447 E/GSM ( 2180): RIL implementation has returned an error where it must succeedcom.android.internal.telephony.CommandException: GENERIC_FAILURE
04-15 02:33:05.447 D/GSM ( 2180): Poll ServiceState done: oldSS=[0 home IntRoam: 0 VIVO VIVO 72410 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[0 home IntRoam: 0 VIVO VIVO 72410 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] oldGprs=0 newGprs=0 oldType=EDGE newType=EDGE
04-15 02:33:05.447 E/GSM ( 2180): isRilReset = false
In this code, I think that the most important lines are the three last ones, who haves the errors, I want to know, if it's a BB problem, because I tried 725Q, 725L, 218 from CM7, and even tried CIS 20c, I tried to get back to all stock, but I have these signal drops in stock too.
Thanks in advance for help

Have you tried to match the ril with the baseband?
If not try the getril app from play store.

andresilva said:
Have you tried to match the ril with the baseband?
If not try the getril app from play store.
Click to expand...
Click to collapse
All the BB tested was matched with the corresponding RIL, now I'm using V20q BB + V20q RIL, and the problem persists.

Same BB , same RIL here and the same problem. Any fix for this ?

If you are running CM7 on your phone you should stick to V10 froyo BB and RIL for best compatibility. Depending on which mobile carrier you will get different varying results with different versions. I'm using Halebop (sweden) and for me 0725 (V10) seems to give the best results and lesser signal losses.
Skickat från min Optimus 2X via Tapatalk 2

[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

OEM Unlock does not appear on the SM-A600T

Hello. When I go into Developer Settings on my Samsung Galaxy A6 (SM-A600T), OEM unlock is not displayed as an option. When I go to download mode (odin mode) to check the RMM state, the fields OEM lock and RMM state do not exist. I am running Android 8.0.0 and the software build number is R16NW.A600TUVU1ARIA. It has been more than 7 days and OEM unlock still doesn't appear. Please help me.

did you ever figure this out?

ctindell1981 said:
did you ever figure this out?
Click to expand...
Click to collapse
Nope. I am still struggling to find out what's wrong.

I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.

Why can't I see the OEM Unlock toggle in Developer Settings if the bootloader is already unlocked?

Quick question.
ctindell1981 said:
I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.
Click to expand...
Click to collapse
Still no luck on a proper TWRP?
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
ctindell1981 said:
I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.
Click to expand...
Click to collapse
ctindell1981 said:
did you ever figure this out?
Click to expand...
Click to collapse
He never figured it but have you? Been trying to root this phone for months

BiHanCummings said:
Still no luck on a proper TWRP?
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
He never figured it but have you? Been trying to root this phone for months
Click to expand...
Click to collapse
So have I.

Still nothing. I apologise for such a long delayed response. I've a very chaotic life. I don't know how to build a TWRP fir the phone. The bootloader comes unlocked though. From my understanding any device with an exynos processor has the BL unlocked.

ctindell1981 said:
Still nothing. I apologise for such a long delayed response. I've a very chaotic life. I don't know how to build a TWRP fir the phone. The bootloader comes unlocked though. From my understanding any device with an exynos processor has the BL unlocked.
Click to expand...
Click to collapse
My previous phone had an exynos processor and was unlockable but it still displayed the OEM unlock option in Developer Settings. Why is the A600T different?

OEM Unlock Logcat
Here is the log that is generated when I open developer settings.
Code:
04-15 09:24:23.158 4025 6155 I vaultkeeper_service: VK 3.0.0 [Client] com.android.settings. => [Vault] RemoteLockControl. [CMD NO.] 357
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: [CMD:REGISTERED]
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: prepare done(0)
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: Don't need pre-process to access partition
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: preProcessing done(0)
04-15 09:24:23.159 4025 6155 I TeeSysClient: open mode set to: 0 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:343]
04-15 09:24:23.159 4025 6155 I TeeSysClient: driver version: v6.3 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:71]
04-15 09:24:23.159 4025 6155 I TeeSysClient: driver open [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:84]
04-15 09:24:23.159 4025 6155 I TeeSysClient: Kinibi access granted by the driver [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:217]
04-15 09:24:23.200 4025 6155 I vaultkeeper_service: openSession done(session id : 3585, device id : 0)
04-15 09:24:23.200 4025 6155 I vaultkeeper_service: notify done(session id : 3585, device id : 0)
04-15 09:24:23.249 4025 6155 I vaultkeeper_service: waitNotification done(session id : 3585, device id : 0)
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: closeSession done(session id : 3585, device id : 0)
04-15 09:24:23.250 4025 6155 I TeeSysClient: driver closed [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:95]
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: cmdProcessing done(0/357)
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: int VWorker::postProcessing(client_rsp_t*): no request to access in steady
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: postProcessing done(0)
04-15 09:24:23.250 4025 6155 I vaultkeeper_jni: runCommand Success.(TA ret = 0)
04-15 09:24:23.251 23997 23997 I RlcManager: query(void)
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: VK 3.0.0 [Client] com.android.settings. => [Vault] RemoteLockControl. [CMD NO.] 5525
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: [CMD:READ_UNSHELTERED]
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: prepare done(0)
04-15 09:24:23.261 4025 6155 I vaultkeeper_service: All Zero
04-15 09:24:23.261 4025 6155 I vaultkeeper_service: preProcessing done(0)
04-15 09:24:23.261 4025 6155 I TeeSysClient: open mode set to: 0 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:343]
04-15 09:24:23.261 4025 6155 I TeeSysClient: driver version: v6.3 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:71]
04-15 09:24:23.261 4025 6155 I TeeSysClient: driver open [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:84]
04-15 09:24:23.261 4025 6155 I TeeSysClient: Kinibi access granted by the driver [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:217]
04-15 09:24:23.309 4025 6155 I vaultkeeper_service: openSession done(session id : 3585, device id : 0)
04-15 09:24:23.309 4025 6155 I vaultkeeper_service: notify done(session id : 3585, device id : 0)
04-15 09:24:23.372 4025 6155 I vaultkeeper_service: waitNotification done(session id : 3585, device id : 0)
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: closeSession done(session id : 3585, device id : 0)
04-15 09:24:23.374 4025 6155 I TeeSysClient: driver closed [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:95]
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: cmdProcessing done(0/5525)
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: int VWorker::postProcessing(client_rsp_t*): no request to access in steady
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: postProcessing done(0)
04-15 09:24:23.374 4025 6155 I vaultkeeper_jni: runCommand Success.(TA ret = 0)
04-15 09:24:23.375 23997 23997 D DevelopmentSettings: enableUnlock rlcState :
04-15 09:24:23.375 23997 23997 D DevelopmentSettings: enableUnlock : 1 = /dev/block/persistent / 2 = 1

Here is a picture of developer settings.

This phone is equipped with a Exynos 7884 CPU. We only need a custom recovery. When will someone be nice to make a TWRP for this phone?

So I'm starting to try to wrap my head around compiling a TWRP for our phones. Once I start to better understand I will seek out testers. If anyone wants to help me so I can get on the fasttrack and whatnot so this can come into fruition quicker. Please, PM me. I'm a single, full-time father and caregiver to my disabled father, so my life is chaotic and sometimes it takes me a while to get back to a project. Communication with me is easier through Facebook.

couldnt u just use the source from the other variants and add the files for this variant and compile for our device instead of the others??