[ROM][WIP/Experimental][AOSP][4.3.1] Google Edition for SGS4A (int'l) v0.8

Search This thread
By:
Advanced…
S

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Alright, some progress. It seems the rild, i.e. the low level daemon connecting to radios is working and calls are coming through, but then the phone framework doesn't understand the message that rild is sending. Got this out by running:
Code: 
adb logcat -b radio

I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: Exit QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS, err_no 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: Waiting...
V/use-Rlog/RLOG-RILC(  296): processWakeupCallback
D/RILJ    (  993): [0269]> GET_CURRENT_CALLS
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: UI --- RIL_REQUEST_GET_CURRENT_CALLS (9) ---> RIL [RID 0, token id 269, data len 0]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: a-r-id 9, a-data 0, a-data-len 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: .. params for Android request id 9 require no copy action (usually means empty payload)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: method 3, datalen 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: already waiting for exec 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: android_request_param_holder b7f5d724 hex
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: pending req kind 0 hex, awaitingexec req kind 0 hex
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: token under exec 269
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: pre-exec token id 269, a-r-id 9, audit 0, nrender 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_android_request_render_execution: rendering exec for token id 269
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: entered voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_get_call_list_to_send: iteration through call objects start
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_voip_call_info_dump: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][main] qcril_qmi_voice_voip_call_info_dump: .. call android id 1, call qmi id 1, elaboration 0, 140012 hex
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][main] qcril_qmi_voice_voip_call_info_dump: .. call state 8, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_call_to_atel: call_to_atel: 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_map_qmi_to_ril_num_pi: qmi_num_pi = 0, number_len = 10
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_get_call_list_to_send: Call state 4, IsMT=1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info: result = 1, modem call type = 0, ril call type = 0, ril call domain = 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info:  audio_attrib_valid = 0, audio_attrib = 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info:  video_attrib_valid = 0, video_attrib = 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_handle_ril_call_entry: call type to be considered 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_is_cdma_voice_emergency_calls_present: nof calls 1, nof cdma voice calls 0, nof 1x/no_srv emergency calls 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_handle_ril_call_entry: ril call entry unchanged
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_set_current_calls_number: entered 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: Reply to RIL --> Number of calls : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: Reply to RIL --> call[0] :state Incoming index 1, toa 129, isMpty 0, isMT 1, als 0, isVoice 1, isVoicePrivacy 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: ...num CANTSEETHIS, num presentation 0, name (null), name presentation 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: call_type = 0, call_domain = 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_send_request_response: UI <--- RIL_REQUEST_GET_CURRENT_CALLS (9) Complete --- RIL [RID 0, Token id 269, Success, Len 4 ]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_send_request_response_epilog: token under exec 269, completion token id 269
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_send_request_response_epilog: postage resp to token id 269, a-r-id 9 (intermed. 9)
D/use-Rlog/RLOG-RILC(  296): RIL onRequestComplete: Command channel closed
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: dispatch outcome = 0
E/RILJ    (  993): Exception processing unsol response: 11010Exception:java.lang.RuntimeException: Unrecognized unsol response: 11010
W/RILJ    (  993): [0269]< GET_CURRENT_CALLS exception, possible invalid RIL response
W/RILJ    (  993): com.android.internal.telephony.ATParseEx: illegal presentation 3407920
W/RILJ    (  993): 	at com.android.internal.telephony.DriverCall.presentationFromCLIP(DriverCall.java:142)
W/RILJ    (  993): 	at com.android.internal.telephony.RIL.responseCallList(RIL.java:3189)
W/RILJ    (  993): 	at com.android.internal.telephony.RIL.processSolicited(RIL.java:2313)
W/RILJ    (  993): 	at com.android.internal.telephony.RIL.processResponse(RIL.java:2225)
W/RILJ    (  993): 	at com.android.internal.telephony.RIL.access$400(RIL.java:211)
W/RILJ    (  993): 	at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:582)
W/RILJ    (  993): 	at java.lang.Thread.run(Thread.java:841)
E/use-Rlog/RLOG-RIL-RAWDATA(  333): 01 2F 00 80 09 01 04 00 00 2E 00 ..
D/use-Rlog/RLOG-RIL-QMI(  333): qmuxd: TX message on fd=19, to clientID = 2, len=82
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][qmi_cb] qcril_event_queue: RID 0 MID 0 Queued event QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS (20 bytes)(obj 0xb7f71d48)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: 1 items on queue
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: RID 0 MID 0 De-queued event QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS (655376)(obj 0xb7f71d48)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: RIL <=== QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS(655376), RID 0, MID 0 === AMSS
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_unsol_ind_cb_helper: .. operational state 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_elaboration_any_subset: entry with pattern 33554432
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: qcril_qmi_voice_all_call_status_ind_hdlr - 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call control for conn id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call control call_state 9
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call state 9, IsMT=2
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call state END for conn id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_call_qmi_id: entry with id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: call android id 1, call qmi id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: .. call state 9, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call mode 3, call type 0, call got connected 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_setup_timed_callback: Set timer with ID 22
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call failure cause 145
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_map_qmi_to_ril_last_call_failure_cause: map qmi reason: 145 to ril reason: 16
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_store_last_call_failure_cause: store ril reason: 16
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_respond_ril_last_call_failure_request: last_call_failure_cause is valid. Will send the response if there is any pending ril request.
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_reqlist_find_by_requests: [RID 0] Not found ReqList entry for RIL_REQUEST_LAST_CALL_FAIL_CAUSE(18)
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_reqlist_find_by_requests: [RID 0] Not found ReqList entry for <Unknown event> ?(851973)
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_call_qmi_id: entry with id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: [CallState] broadcast -a android.intent.action.PHONE_EXSTATE_CHANGED --ei STATE 9
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] >> get the peding LOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_lock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_lock - Before Count  : 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response_epilog: UI <--- RIL_UNSOL_UNKOWN (11010) --- RIL [RID 0, Len 69, (null)]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] << get the peding UNLOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_unlock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_unlock - Before Count  : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_convert_call_mode_to_radio_tech_family: entered call_mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_nas_control_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: entered voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. is deviant call pre 0 
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_nw_reg_voice_is_voice_call_mode_reasonable_against_dev_cfg: .. mode_pref valid 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_nw_reg_voice_is_voice_call_mode_reasonable_against_dev_cfg: .. mode_pref 28
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. is deviant call final 0, is mode reasonable 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. imperative report 0 
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_call_to_ims: qcril_qmi_voice_info.jbims: 0, call_to_ims: 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_call_to_atel: call_to_atel: 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: -- final call dump start --
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: - dumping call 1 out of 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_call_info_dump: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_voip_call_info_dump: .. call android id 1, call qmi id 255, elaboration 0, 140112 hex
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_voip_call_info_dump: .. call state 9, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: -- final call dump end --
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_is_cdma_voice_emergency_calls_present: nof calls 1, nof cdma voice calls 0, nof 1x/no_srv emergency calls 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] >> get the peding LOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_lock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_lock - Before Count  : 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response_epilog: UI <--- RIL_UNSOL_RESPONSE_CALL_STATE_CHANGED (1001) --- RIL [RID 0, Len 0, (null)]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] << get the peding UNLOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_unlock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_unlock - Before Count  : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: Exit QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS, err_no 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: Waiting...
V/use-Rlog/RLOG-RILC(  296): processWakeupCallback
E/RILJ    (  993): Exception processing unsol response: 11010Exception:java.lang.RuntimeException: Unrecognized unsol response: 11010
D/RILJ    (  993): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ    (  993): [0270]> GET_CURRENT_CALLS
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: UI --- RIL_REQUEST_GET_CURRENT_CALLS (9) ---> RIL [RID 0, token id 270, data len 0]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: a-r-id 9, a-data 0, a-data-len 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: .. params for Android request id 9 require no copy action (usually means empty payload)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: method 3, datalen 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: already waiting for exec 0

Have to debug more tomorrow.
 
  • Like
Reactions: mythi, alirey and ohwarumbloss
mythi

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
spegelius said:
Alright, some progress. It seems the rild, i.e. the low level daemon connecting to radios is working and calls are coming through, but then the phone framework doesn't understand the message that rild is sending. Got this out by running:
Code: 
adb logcat -b radio

I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: Exit QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS, err_no 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: Waiting...
V/use-Rlog/RLOG-RILC(  296): processWakeupCallback
D/RILJ    (  993): [0269]> GET_CURRENT_CALLS
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: UI --- RIL_REQUEST_GET_CURRENT_CALLS (9) ---> RIL [RID 0, token id 269, data len 0]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: a-r-id 9, a-data 0, a-data-len 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: .. params for Android request id 9 require no copy action (usually means empty payload)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: method 3, datalen 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: already waiting for exec 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: android_request_param_holder b7f5d724 hex
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: pending req kind 0 hex, awaitingexec req kind 0 hex
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: token under exec 269
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: pre-exec token id 269, a-r-id 9, audit 0, nrender 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_android_request_render_execution: rendering exec for token id 269
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: entered voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_get_call_list_to_send: iteration through call objects start
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_voip_call_info_dump: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][main] qcril_qmi_voice_voip_call_info_dump: .. call android id 1, call qmi id 1, elaboration 0, 140012 hex
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][main] qcril_qmi_voice_voip_call_info_dump: .. call state 8, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_call_to_atel: call_to_atel: 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_map_qmi_to_ril_num_pi: qmi_num_pi = 0, number_len = 10
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_get_call_list_to_send: Call state 4, IsMT=1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info: result = 1, modem call type = 0, ril call type = 0, ril call domain = 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info:  audio_attrib_valid = 0, audio_attrib = 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_get_call_type_info:  video_attrib_valid = 0, video_attrib = 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_handle_ril_call_entry: call type to be considered 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_is_cdma_voice_emergency_calls_present: nof calls 1, nof cdma voice calls 0, nof 1x/no_srv emergency calls 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_handle_ril_call_entry: ril call entry unchanged
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_nas_control_set_current_calls_number: entered 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: Reply to RIL --> Number of calls : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: Reply to RIL --> call[0] :state Incoming index 1, toa 129, isMpty 0, isMT 1, als 0, isVoice 1, isVoicePrivacy 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: ...num CANTSEETHIS, num presentation 0, name (null), name presentation 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_qmi_voice_request_get_current_atel_calls: call_type = 0, call_domain = 1
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qcril_send_request_response: UI <--- RIL_REQUEST_GET_CURRENT_CALLS (9) Complete --- RIL [RID 0, Token id 269, Success, Len 4 ]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_send_request_response_epilog: token under exec 269, completion token id 269
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_send_request_response_epilog: postage resp to token id 269, a-r-id 9 (intermed. 9)
D/use-Rlog/RLOG-RILC(  296): RIL onRequestComplete: Command channel closed
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: dispatch outcome = 0
E/RILJ    (  993): Exception processing unsol response: 11010Exception:java.lang.RuntimeException: Unrecognized unsol response: 11010
W/RILJ    (  993): [0269]< GET_CURRENT_CALLS exception, possible invalid RIL response
W/RILJ    (  993): com.android.internal.telephony.ATParseEx: illegal presentation 3407920
W/RILJ    (  993): at com.android.internal.telephony.DriverCall.presentationFromCLIP(DriverCall.java:142)
W/RILJ    (  993): at com.android.internal.telephony.RIL.responseCallList(RIL.java:3189)
W/RILJ    (  993): at com.android.internal.telephony.RIL.processSolicited(RIL.java:2313)
W/RILJ    (  993): at com.android.internal.telephony.RIL.processResponse(RIL.java:2225)
W/RILJ    (  993): at com.android.internal.telephony.RIL.access$400(RIL.java:211)
W/RILJ    (  993): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:582)
W/RILJ    (  993): at java.lang.Thread.run(Thread.java:841)
E/use-Rlog/RLOG-RIL-RAWDATA(  333): 01 2F 00 80 09 01 04 00 00 2E 00 ..
D/use-Rlog/RLOG-RIL-QMI(  333): qmuxd: TX message on fd=19, to clientID = 2, len=82
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][qmi_cb] qcril_event_queue: RID 0 MID 0 Queued event QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS (20 bytes)(obj 0xb7f71d48)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: 1 items on queue
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: RID 0 MID 0 De-queued event QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS (655376)(obj 0xb7f71d48)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: RIL <=== QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS(655376), RID 0, MID 0 === AMSS
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_unsol_ind_cb_helper: .. operational state 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_elaboration_any_subset: entry with pattern 33554432
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: qcril_qmi_voice_all_call_status_ind_hdlr - 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call control for conn id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call control call_state 9
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call state 9, IsMT=2
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call state END for conn id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_call_qmi_id: entry with id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: call android id 1, call qmi id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_update_call_info_entry_mainstream: .. call state 9, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call mode 3, call type 0, call got connected 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_setup_timed_callback: Set timer with ID 22
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: call failure cause 145
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_map_qmi_to_ril_last_call_failure_cause: map qmi reason: 145 to ril reason: 16
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_store_last_call_failure_cause: store ril reason: 16
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_respond_ril_last_call_failure_request: last_call_failure_cause is valid. Will send the response if there is any pending ril request.
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_reqlist_find_by_requests: [RID 0] Not found ReqList entry for RIL_REQUEST_LAST_CALL_FAIL_CAUSE(18)
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_reqlist_find_by_requests: [RID 0] Not found ReqList entry for <Unknown event> ?(851973)
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_find_call_info_entry_by_call_qmi_id: entry with id 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: [CallState] broadcast -a android.intent.action.PHONE_EXSTATE_CHANGED --ei STATE 9
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] >> get the peding LOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_lock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_lock - Before Count  : 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response_epilog: UI <--- RIL_UNSOL_UNKOWN (11010) --- RIL [RID 0, Len 69, (null)]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] << get the peding UNLOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_unlock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_unlock - Before Count  : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_convert_call_mode_to_radio_tech_family: entered call_mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_nas_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_nas_control_get_reported_voice_radio_tech: completed with voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: entered voice_radio_tech 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. is deviant call pre 0 
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_nw_reg_voice_is_voice_call_mode_reasonable_against_dev_cfg: .. mode_pref valid 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_nw_reg_voice_is_voice_call_mode_reasonable_against_dev_cfg: .. mode_pref 28
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. is deviant call final 0, is mode reasonable 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: .. imperative report 0 
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_call_to_ims: qcril_qmi_voice_info.jbims: 0, call_to_ims: 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_call_to_atel: call_to_atel: 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: -- final call dump start --
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: - dumping call 1 out of 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_voip_call_info_dump: param -1208520440
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_voip_call_info_dump: .. call android id 1, call qmi id 255, elaboration 0, 140112 hex
I/use-Rlog/RLOG-RILQ(  296): (0/296):RIL[0][event] qcril_qmi_voice_voip_call_info_dump: .. call state 9, call type 0, call mode 3
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_all_call_status_ind_hdlr: -- final call dump end --
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_qmi_voice_is_cdma_voice_emergency_calls_present: nof calls 1, nof cdma voice calls 0, nof 1x/no_srv emergency calls 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] >> get the peding LOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_lock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_lock - Before Count  : 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response_epilog: UI <--- RIL_UNSOL_RESPONSE_CALL_STATE_CHANGED (1001) --- RIL [RID 0, Len 0, (null)]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_send_unsol_response: [DEADLOCK-DEBUG] << get the peding UNLOCK - qcril_send_unsol_response 
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qmi_ril_android_pending_unsol_resp_unlock: [DEADLOCK-DEBUG] qmi_ril_android_pending_unsol_resp_unlock - Before Count  : 1
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_process_event: Exit QCRIL_EVT_QMI_VOICE_HANDLE_INDICATIONS, err_no 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][event] qcril_event_main: Waiting...
V/use-Rlog/RLOG-RILC(  296): processWakeupCallback
E/RILJ    (  993): Exception processing unsol response: 11010Exception:java.lang.RuntimeException: Unrecognized unsol response: 11010
D/RILJ    (  993): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ    (  993): [0270]> GET_CURRENT_CALLS
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: UI --- RIL_REQUEST_GET_CURRENT_CALLS (9) ---> RIL [RID 0, token id 270, data len 0]
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: a-r-id 9, a-data 0, a-data-len 0
I/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] qmi_ril_fw_create_android_live_params_copy: .. params for Android request id 9 require no copy action (usually means empty payload)
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: method 3, datalen 0
W/use-Rlog/RLOG-RILQ(  296): (0/296): RIL[0][main] onRequest: already waiting for exec 0

Have to debug more tomorrow.
Click to expand...
Click to collapse

I can feel it ... we are near ... could you provide your latest build

Sent from my GT-I9295 using Tapatalk
 
S

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
mythi said:
I can feel it ... we are near ... could you provide your latest build

Sent from my GT-I9295 using Tapatalk
Click to expand...
Click to collapse

Uploading v0.3 to the Google drive. Stock telephony framework, so nothing new in that department.

Tried to add SamsungQualcomRIL and SamsungExonys4RIL to java sources, bad idea ;). But they are needed so there's work to be done...

http://pastebin.com/m0RMepiD

Edit: i'll propably start uploading stuff to github before i do anything with the phone stuff. To tell the truth, feeling bit demotivated as i'm doing quite intensive sw development at work and this is also starting to feel like work :D. But not giving up, just need a bit of time off.
 
Last edited:
  • Like
Reactions: ohwarumbloss
mythi

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
spegelius said:
Uploading v0.3 to the Google drive. Stock telephony framework, so nothing new in that department.

Tried to add SamsungQualcomRIL and SamsungExonys4RIL to java sources, bad idea ;). But they are needed so there's work to be done...

http://pastebin.com/m0RMepiD

Edit: i'll propably start uploading stuff to github before i do anything with the phone stuff. To tell the truth, feeling bit demotivated as i'm doing quite intensive sw development at work and this is also starting to feel like work :D. But not giving up, just need a bit of time off.
Click to expand...
Click to collapse

it will be alot easier to help in debugging with full source code at github :good:
 
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
spegelius said:
Uploading v0.3 to the Google drive. Stock telephony framework, so nothing new in that department.

Tried to add SamsungQualcomRIL and SamsungExonys4RIL to java sources, bad idea ;). But they are needed so there's work to be done...

http://pastebin.com/m0RMepiD

Edit: i'll propably start uploading stuff to github before i do anything with the phone stuff. To tell the truth, feeling bit demotivated as i'm doing quite intensive sw development at work and this is also starting to feel like work :D. But not giving up, just need a bit of time off.
Click to expand...
Click to collapse

Mate... you're doing this in your free time and if it starts to feel like work... Stop it...
From my point of view, you helped us a lot the last weeks and this is supposed to be fun, nothing serious!
Take your time and come back whenever you think you should!

And thank you for all your hard work!

One question tho, the picture quality of the AOSP build is way better than it was in the last cm build, is there a way to get this to cm?
Don't hurry ;)
Greetings
Thomas

Sent from my GT-I9295 using xda app-developers app
 
  • Like
Reactions: spegelius
S

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
ohwarumbloss said:
Mate... you're doing this in your free time and if it starts to feel like work... Stop it...
From my point of view, you helped us a lot the last weeks and this is supposed to be fun, nothing serious!
Take your time and come back whenever you think you should!

And thank you for all your hard work!

One question tho, the picture quality of the AOSP build is way better than it was in the last cm build, is there a way to get this to cm?
Don't hurry ;)
Greetings
Thomas

Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse

Yeah, i know i should stop, but my mind keeps returning to solving problems and then i notice that i'm on it again ;). Luckily i do have other hobbies so it's not too bad yet :confused:.

And look what happened yesterday; an idea popped to my mind, have a look at SlimRom telephony code. And what do you know, it's much closer to AOSP than CM, so i did some cherrypicking and now phone calls are coming through :D. Yay!

Uploading v0.4, grab it from Google Drive when it's there. And no, nothing uploaded to github yet. But i think this is a good point to start backtracking all the changes, now that most of the basic functionality is there. I can finally go back to using my Active, woo :)
 
  • Like
Reactions: mythi, alirey and ohwarumbloss
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
Aweeeeesome :)

You made my day, thank you so very much :)

Will download, install and report back, awesome!!!
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
 
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
alirey said:
i would like to try the ROM.
can anybody tell me if SD card is recognized? @spegelius: Thanks allot for your work

Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Hey, no, it isn't. But I'm sure there is a way to do it.

Else, Call works, incoming & outgoing, End Call works, mobile Data works, WiFi works, Bluetooth works.
GPS I don't know (it's cold outside) but will test tomorrow ;)
Daily Driver for sure :)
Awesome!

Sent from my GT-I9295 using xda app-developers app
 
  • Like
Reactions: spegelius and alirey
mythi

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:

---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------

Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:
 
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
Didn't make SD work.

I tried to format with fat32gui, no luck..
I tried to format with Device... Caused a reboot but no luck..

The first time I released the back cover ever since I bought this phone ;)


Sent from my GT-I9295 using xda app-developers app
 
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
But it's niiiice ;)


Sent from my GT-I9295 using xda app-developers app
 

Attachments

  • uploadfromtaptalk1391558440633.jpg
    uploadfromtaptalk1391558440633.jpg
    56.4 KB · Views: 111
S

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
alirey said:
i would like to try the ROM.
can anybody tell me if SD card is recognized? @spegelius: Thanks allot for your work

Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Weel i haven't done anything regards that yet. Actually i don't even have sdcard yet (damn DHL and Nierle), but it's on the todo list. Hoepfully it's something simple, like missing lib...

mythi said:
Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:

---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------

Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:
Click to expand...
Click to collapse

Yeah, i think it ook a wrong choice by using CM as reference when starting to implement this, with Slim somthings would have been a lot easier. But then again, i've learned lot more :good:

ohwarumbloss said:
Hey, no, it isn't. But I'm sure there is a way to do it.

Else, Call works, incoming & outgoing, End Call works, mobile Data works, WiFi works, Bluetooth works.
GPS I don't know (it's cold outside) but will test tomorrow ;)
Daily Driver for sure :)
Awesome!

Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse

Great! And GPS does work, tracked my bicycle ride to work today. There is a bug related to locationproviders, starting Sports Tracker crashed whole UI every time. Maps didn't. Turned out that Sports Tracker requested a provider named "network" which didn't exist. That threw an exception which crashed whole service framework :eek:. Fixed it by returning something more sane, so now it doesn't crash. But i think that's something that needs some attention at some point... i'm not ruling out that Sports Tracker is doing something bad.
 
ohwarumbloss

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
From what I've read AOSP Roms are not licensed to read exfat. Formatting my spare SD Card to Fat32 didn't work but I think the Problem was on my Side of the Keyboard ;)
On the other Hand, Slim and CM do read the SD so there has to be a way..
Well, that's not a real biggie I think!

Sent from my GT-I9295 using xda app-developers app
 
alirey

alirey

Senior Member
Mar 6, 2012
345
212
Berlin
OnePlus 9 Pro
ohwarumbloss said:
From what I've read AOSP Roms are not licensed to read exfat. Formatting my spare SD Card to Fat32 didn't work but I think the Problem was on my Side of the Keyboard ;)
On the other Hand, Slim and CM do read the SD so there has to be a way..
Well, that's not a real biggie I think!

Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse

I have a 64GB card. Format is fat32. Works in CM from 27.12.2013

This was the command i found on my CM ROM in the following file: /data/local/RootToolsMounts
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tried to copy the file on the aosp rom an restart --> no luck
tried to edit the /fstab.qcom with that string --> no luck

i hear no ringtone if anybody calls me...just me?
 
S

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
alirey said:
I have a 64GB card. Format is fat32. Works in CM from 27.12.2013

This was the command i found on my CM ROM in the following file: /data/local/RootToolsMounts
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tried to copy the file on the aosp rom an restart --> no luck
tried to edit the /fstab.qcom with that string --> no luck

i hear no ringtone if anybody calls me...just me?
Click to expand...
Click to collapse

Did you install over old installation or did you do factory reset before? Could be some old setting or something... if the problem doesn't go away by changing volumes or ringtones, a logcat would be nice.

ohwarumbloss said:
There is a /extras Folder in CM containing some exfat stuff, /bin Folder has some, too..
And I found this : http://xdaforums.com/showthread.php?t=2164266 but this didn't work on my Device..

Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse

I think i haven't included exfat stuff to the build... i'll check this tonight, i'll scavenge a card from my cam. I need extra space anyways.
 
  • Like
Reactions: Pkt_Lnt and ohwarumbloss
alirey

alirey

Senior Member
Mar 6, 2012
345
212
Berlin
OnePlus 9 Pro
spegelius said:
Did you install over old installation or did you do factory reset before? Could be some old setting or something... if the problem doesn't go away by changing volumes or ringtones, a logcat would be nice.
Click to expand...
Click to collapse

First i tried a dirty flash...no boot ;)
then a clean install with no ringtone but no time to check the settings.
Meanwhile i am back on cm because of work issues (couldn't hear my boss calling me two time)

But as soon as the Ext SD prob is solved, i will be back :) and if still no ringtone i will send you a logcat (or ignore my boss :victory:)

thanks in advance
 
You must log in or register to reply here.

Similar threads

L
[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)
Replies
302
Views
151K
mythi
mythi
S
[ROM][Official Nightly][Android 4.4] CyanogenMod 11.0 for SGS4A (int'l)
Replies
1K
Views
192K
W
WingedLion
L
ClockworkMod Recovery for Galaxy S4 Active (int'l)[Unofficial]
Replies
153
Views
145K
robert2103
robert2103
S
[KERNEL][I9295][AOSP/CM11/CM12][TW-4.4]KT-SGS4 port for Active Intl
Replies
83
Views
24K
Pkt_Lnt
Pkt_Lnt
ktoonsez
[KERNEL][I9295][TW - 4.2][02/24/2014] KT-SGS4 - MF5/MK3 - KTweaker
Replies
107
Views
24K
M
machhho

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    S
    spegelius
    What?

    • work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
    • some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
    • build makefiles modified, using CM files where possible
    • some small code modifications
    • for I9295 international only
    • stuff is broken, for how long i do not know. I'm still learning this stuff :)
    • DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned

    How?

    Credits
    • Google for Android (and Google search, boy this wouldn't have happened without it ;) )
    • CyanogenMod for stuff i'm using to make this happen
    • SlimRom guys
    • LeJay for jactivelte kernel sources and other stuff
    • ohwarumbloss for testing CM builds and donations
    • Chainfire for root
    • other donators and testers :)

    Changes v0.8
    • Video preview fixed
    • sub-1080p video recording fixed
    • Audio volume settings copied from SlimRom jf-common, more volume


    Changes v0.7.1
    • Only kernel changes
    • Newer Broadcom wireless drivers from S4 CM 10.2 kernel
    • EXT4 and JBD2 drivers from S4 CM 10.2 kernel
    • MSM-8960 related stuff from S4 CM 10.2 kernel
    • Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me :)

    Changes v0.7

    Changes v0.6
    • dualboot version available
    • some merges from S4 kernel, no changes in functionality
    • cwm update script doesn't format system anymore
    • libbt-vendor natively built instead copy from CM build. No change in functionality


    Changes v0.5
    • Sdcard should now work (FAT32 at least, report exfat)
    • Sports Tracker doesn't crash UI when 'network' location provider isn't found

    Changes v0.3 & 0.4

    • [*]Receiving calls fixed
    • Hanging up the call fixed
    • NFC doesn't crash on the background anymore, cannot test though
    • Bluetooth fixed, using lib from CM build

    Changes v0.2
    • WiFi dhcp fixed
    • SuperSu included
    • init.d support
    • bash included
    • Bluetooth updates, but no full fix yet

    Bugs v0.8
    • Whoa, are there any? :)

    Bugs v0.7.1
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution

    Bugs v0.6
    • Some problems with locations, network locaion isn't really enabled
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution
    • Backup account set to debug-only private cache for some users

    Bugs v0.5
    • Some problems with locations
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution

    Fixed Bugs
    • Sdcard doesn't mount
    • Cannot receive calls
    • Cannot hang up a call
    • WiFi connects, but doesn't get IP address
    • Bluetooth service fails at start, bluetooth doesn't work
    • NFC seems to be crashing on the background
    • no root as of yet

    Source code
    https://github.com/spegelius

    Will be updating manifests and other stuff there when i figure a good way to get my changes there.

    Oh and mods, if this fits the regular development section better, feel free to move it
    View
    6
    S
    spegelius
    Uploading 0.7.1 now. Nothing has changed on the rom itself, only kernel changes

    • Newer Broadcom wireless drivers from S4 CM 10.2 kernel
    • EXT4 and JBD2 drivers from S4 CM 10.2 kernel
    • MSM-8960 related stuff from S4 CM 10.2 kernel
    • Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me :)

    What i've tested myself, everything works as before. And actually not expecting drastic changes, the kernel has been working very well already.
    Whati i hoped to achieve was to get S4 and S4 Active kernels as close as possible and i'm happy about the results. Also, i hoped that the 720p recording would've been kernel related, but no. I did some camera debugging and what caught my eye is that even though the quality is set to 720p, debug say that resolution is set to 1920x1080. But needs more investigation.
    View
    4
    S
    spegelius
    leonpr said:
    Hey. Thanks for the ROM. Always nice to see something in development for the i9295.

    I stuck 0.6 on my S4A today and all looking good so far except I'm getting a "cannot connect to camera" message when opening the camera app (or Snapchat)

    Quick search has someone with the same issue on page 1 but the following posts are more focused on restoring root.

    Any ideas?

    Clean install.
    Click to expand...
    Click to collapse

    The issue with camera might be a leftover of my fiddling with some Qualcom camera sources and not cleaning the build env before building another one, yesterday i noticed that i didn't even have the camera app anymore. Sorry about that.

    But don't worry, ver 0.7 is uploading :). Fixes:
    - the camera of course
    - network location finally working. Took some debugging, finally found out that the available location provider for network didn't have a god enough signature for ServiceWatcher. Googled the error and finally found a thread with some meaning which instructed how to add the damn provider to resource xml in frameworks/core.
    - Backup to google account: for those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
    View
    3
    S
    spegelius
    Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.

    - wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...:eek:
    - included SuperSu to rom, root should work out of the box :)

    Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.

    Ver 0.2 is uploading, test away
    View
    3
    alirey
    alirey
    Hey all,

    found a way to mount the ext SD Card :victory:

    mount -o remount,rw /
    mount -t vfat -o umask=0000 /dev/block/vold/179:33 /storage/sdcard1

    Now this ROM is my daily driver...

    edit: Ringtone issue is gone
    View

New posts