[Miscellaneous Android Development] RickyGoldsmith:
Replying to myself. I just narrowed the sensor error. It is fixed in my phone now.

Now back to the last issue, I am again greeted with the same old mnld problem

V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
I/SurfaceTextureClient( 1957): [STC::queueBuffer] (this:0x54eb0008) fps:10.96, dur:1094.81, max:121.67, min:12.67
I/BufferQueue( 124): [SurfaceView](this:0x42737c38,api:1) [queue] fps:10.96, dur:1095.14, max:121.87, min:12.50
I/BufferQueue( 124): [SurfaceView](this:0x42737c38,api:1) [release] fps:10.91, dur:1100.09, max:116.81, min:16.59
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
D/NVRAM ( 2019): mtk_gps_sys_nmea_output_to_app: $GPGGA,000007.000,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*44
D/NVRAM ( 2019): $GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
D/NVRAM ( 2019): $GPRMC,000007.000,V,8960.0000,N,00000.0000,E,0.000,0.00,060180,,,N*49
D/NVRAM ( 2019): $GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32
D/NVRAM ( 2019): $GPACCURACY,3162.1*3F
D/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: SVListBitMap: 0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: Get SV info success
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[0]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[1]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[2]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[3]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[4]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[5]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[6]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[7]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[8]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[9]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[10]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[11]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[12]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[13]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[14]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[15]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[16]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[17]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[18]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[19]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[20]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[21]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[22]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[23]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[24]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[25]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[26]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[27]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[28]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[29]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[30]=0
E/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: EPH[31]=0
D/MNLD ( 661): mnl_set_alarm: (0, 0x80000001, 5)
D/mnl_linux( 2019): mtk_gps_sys_gps_mnl_callback: MTK_GPS_MSG_FIX_READY,GET_RTC_FAIL
D/gps_mt3326( 410): gps_state_thread: line = 1818received 247 bytes:
D/gps_mt3326( 410): nmea_reader_parse: line = 1218GPS get accuracy failed, fix mode:1
V/Provider/Setting( 410): from settings cache , name = location_providers_allowed value = network,gps
I/SurfaceFlinger( 124): [SurfaceFlinger] fps:18.182587,dur:1099.95,max:116.79,min:15.79

These are errors. And I haven't been able to relate which subsystem they are coming from. The MTK kernel sources that we have, they too don't have a reference to this function call.