MTK RIL Problems

[Skyrimus]

Not working USSD, i call *100#, USSD window shows on 1 seconds and close, dont show info of account, on any MTK SoC logcat_ussd.txt

Not working incoming calls on any MTK SoC logcat_incoming_calls.txt

[8472]

Argh, these phones are a puzzle. Turned phone back on today and no LTE or cell service signal as with all prior GSI ROMs.

[8472]

After clean wipe and install, cellular service working on MT6763 included LTE data. No VoLTE as phone calls drop down to 3G or lower. Unfortunately it is short lived as phone service will disappear after next reboot. Why does reboot phone cause it to lose cell service?

For anyone interested in seeing for yourself here are steps I used. Clean install of latest ROM from Umidigi using Flash Tool Unlock bootloader Install Magisk Install MiXplorer Install TWRP Open MiXplorer to edit system/vendor/etc/fstab.mt6763

• Line 15, replace bold text: /dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata, with: /dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,

Reboot to TWRP Dalvik wipe, reboot (will have to go thru setup again) Transfer GSI image to download folder Reboot to TWRP Install img GSI ROM should be working with LTE data and working phone service Reboot phone LTE data and phone service disappear! Reboot to TWRP Dalvik wipe, reboot LTE data and phone service functional again... until you reboot!

[8472]

After phone reboots without cell service, removing SIM card, rebooting without card installed and then inserting SIM card will also restore cell service and better option than TWRP wipe. Something is occuring (or not occuring) during bootup. I'll have to try and capture logcat

[bigrammy]

I had this issue on the nokia 3 after the latest update. It took much head scratching trial and error before I worked out what was happening. "muxreport" Seems on Android 8.x > it checks the "default" encryption eg "forceencrypt" if it see "encryptable" it will not start the modem (No cell service) So to work unencrypted with working ril you must remove any reference to encryption from the kernel dtb. Also edit vendor/etc/fstab.mt67xx and /nvram/fstab.mt67xx accordingly. You could simply run encrypted and have a working TWRP that supports decryption too.

[8472]

So if I understand you correctly, editing system/vendor/etc/fstab.mt6763 back to original will fix the modem issue? Yes, we need TWRP which supports decryption.

[bigrammy]

So if I understand you correctly, editing system/vendor/etc/fstab.mt6763 back to original will fix the modem issue? Yes, we need TWRP which supports decryption.

Yes it should do.

[MACROsoftOfficial]

After clean wipe and install, cellular service working on MT6763 included LTE data. No VoLTE as phone calls drop down to 3G or lower. Unfortunately it is short lived as phone service will disappear after next reboot. Why does reboot phone cause it to lose cell service?

Is this your experience after editing the default value to AT+EAIC=7 or by changing to AT+EAIC=3 ???

[bigrammy]

After clean wipe and install, cellular service working on MT6763 included LTE data. No VoLTE as phone calls drop down to 3G or lower. Unfortunately it is short lived as phone service will disappear after next reboot. Why does reboot phone cause it to lose cell service?

Is this your experience after editing the default value to AT+EAIC=7 or by changing to AT+EAIC=3 ???

@8472 's problem was no service at all I believe so the problems are two unrelated issues. The problem 8472 reported exists due to editing the fstab.mt67xx's /userdata to "encryptable" rather than leaving it as the default "forceencrypt". Editing the libmtk-ril.so "default value to AT+EAIC=? to AT+EAIC=3 " may still be required once there is a stable "service signal" Hopefully 8472 will respond with some feedback soon.

[milankragujevic]

@bigrammy I didn't edit fstab, yet I got no mobile data too, except when it does work randomly...

[8472]

I will have time to try out this weekend.

[8472]

I may (or may not) spend more time with it later but on my initial attempt, leaving system/vendor/etc/fstab.mt6763 unedited had no impact on SIM card functioning. On initial boot up LTE signal present however on subsequite boot it was back to no signal.

[MACROsoftOfficial]

After clean wipe and install, cellular service working on MT6763 included LTE data. No VoLTE as phone calls drop down to 3G or lower. Unfortunately it is short lived as phone service will disappear after next reboot. Why does reboot phone cause it to lose cell service?

Is this your experience after editing the default value to AT+EAIC=7 or by changing to AT+EAIC=3 ???

@8472 's problem was no service at all I believe so the problems are two unrelated issues. The problem 8472 reported exists due to editing the fstab.mt67xx's /userdata to "encryptable" rather than leaving it as the default "forceencrypt". Editing the libmtk-ril.so "default value to AT+EAIC=? to AT+EAIC=3 " may still be required once there is a stable "service signal" Hopefully 8472 will respond with some feedback soon.

on Umi Z2 i have no service too even after editing to AT+EAIC=3 and editing to AT+EAIC=7,could this really be a puzzle? because it's becoming somewhat funny as some person can easily get this issues resloved while it gets more difficult to work on on others, most especially when a device user with same model and SOC can confirmed it working on his. Then it becomes a goddamn puzzle

[8472]

As I have fully functional 4G LTE after initial install and boot-up of GSI ROM, I don't think the edits to libmtk-ril.so described above are the solution.

[apogen]

only in havoc-os 2.0 lte works after reboot for me.. (umi z2)

Λήψη του Outlook για Android

On Sat, Dec 15, 2018 at 3:57 AM +0200, "8472" notifications@github.com wrote:

As I have fully functional 4G LTE after initial install and boot-up of GSI ROM, I don't think the edits to libmtk-ril.so described above are the solution.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[milankragujevic]

@apogen GSI or device-specific? What version, and is it arm or arm64?

[apogen]

latest gsi havoc 2.0 arm64 aonly

[SkyWorldWide]

@mmoreyrav commented 4 months ago I found an easy way to make incoming calls work. Just open /vendor/lib/mtk-ril.so in a hex editor and replace the string "AT+EAIC=2" with "AT+EAIC=3". This disables incoming call approval which requires special proprietary support in the telephony frameworks.

This fixes both incoming calls and USSD codes.

Tested on a MT6580 with kernel 3.18.79 on GSM 3G using Phh-Treble GSI 9.0

This worked for me on MT6739 👍 Now if we can get Mobile Data to work, it'll be awesome 🤞. Currently mobile data doesn't work 😕😔

[morfii83]

Hello on mtk6753 do not work incoming calls edit mtk ril does not fix the problem tell me how to fix?

[p00f]

@stevea76 Well, then you'll have to inspect the radio log (adb logcat -b radio) during an incoming call and look for some clue within it. For example I found the following line: RILC-RP : incomingCallIndicationInd: radioService[0]->mRadioIndicationMtk == NULL which allowed me to understand the problem in my case.

I have this in my log: RILC-RP : crssNotifyInd: radioService[0]->mRadioIndicationMtk == NULL after making it AT+EAIC=7

i didnt take a log when it was AT+EAIC=3, but it didnt work then too

[qianbinbin]

I found an easy way to make incoming calls work. Just open /vendor/lib/mtk-ril.so in a hex editor and replace the string "AT+EAIC=2" with "AT+EAIC=3". This disables incoming call approval which requires special proprietary support in the telephony frameworks.

This fixes both incoming calls and USSD codes.

Tested on a MT6580 with kernel 3.18.79 on GSM 3G using Phh-Treble GSI 9.0

On Redmi 6A with Helio A22 (MT6762M), flashed treble aosp 8.1, incoming call and incoming sms don't work, after editing /vendor/lib/libmtk-ril.so, changed AT+EAIC=2 to AT+EAIC=3, the incoming call works, but sms doesn't. I hate miui and really want to use custom roms, any help would be appreciated, thanks.

[Petrovich72]

https://github.com/phhusson/device_phh_treble/blob/cbf5a7891f571ad8c57f7e82966bc3a037398784/vndk-detect

[morfii83]

Подскажи куда это вставить

пн, 28 янв. 2019 г. в 07:15, Petrovich72 notifications@github.com:

https://github.com/phhusson/device_phh_treble/blob/cbf5a7891f571ad8c57f7e82966bc3a037398784/vndk-detect

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/57#issuecomment-457994195, or mute the thread https://github.com/notifications/unsubscribe-auth/AVIHqJX9p-Zf_41eDfwMJmeqSk-6-NUkks5vHnldgaJpZM4UPGKc .

[AHDianin]

I am using an MTK6763 and when I set the Preferred Network Type in Setting to 2G it starts to work. Maybe having an automatic selection for 4G/3G/2G will solve the problem. Also, the hotspot and NFC doesn't work for me.

[phhusson]

I am using an MTK6763 and when I set the Preferred Network Type in Setting to 2G it starts to work. Maybe having an automatic selection for 4G/3G/2G will solve the problem.

What's "it"? Whole RIL? Data connection? Incoming SMS? Calls?

[AHDianin]

SMS and Calls are working. Data connection is not working.

[abhilariya]

@svoboda18 no, RIL also includes SMS and VoLTE.

[lincolnayisi]

@8472 please how did you get TWRP for 6763.. mine always land me at decryption unsuccessful page.. factory reset doesn't help either. I know after I clean flash GSI ... I get LTE cell and data to be working but the moment I flash TWRP network doesn't work and only boots to decryption unsuccessful so I don't get to use the phone anyway with TWRP installed. Even if I flash stock recovery back.. Still no signal n data works again because I have already tempered flashing TWRP. I don't know why mtk have issues with treble ROMs and data connection. Operation treble crew should help us

[ironashram]

mt6771, calls working, but no data at all, no matter what

[phhusson]

@ironashram see and try https://github.com/phhusson/treble_experimentations/issues/416

[pcvgitgano]

Hello which of your builds should I try first which supports adb root without installing anything like magisk? I want to try if #416 works for me (MT6739 device)

[phhusson]

All my builds have working adb root

[pcvgitgano]

Does this fix only the incoming sms issue or it includes mobile data fix?

[sararah7]

@pcvgitgano @phhusson i tried #416 with newest treble aosp 81. sim1 fixed and mobile data fixed. sim2 at least connected for mobile data now but stuck on 2G, ignoring other modes - but ok with sim1.

[phhusson]

it's only mobile data fix. the incoming sms fix is harder to test, so you'll have to wait for the next release (which should be in a few days anyway)

[pcvgitgano]

i'm downloading the latest aosp pie and see if it works @sararah7 @phhusson

[ironashram]

@ironashram see and try #416

thank you it works, will test better right now

[oscx]

sim1 fixed and mobile data fixed. sim2 at least connected for mobile data now but stuck on 2G, ignoring other modes - but ok with sim1.

I can confirm the same result on MT6739 dualsim devices from oukitek brand. both SIM slots connected, 2nd SIM EDGE-only. Incomming SMS is working properly for me now. (build from sources today)

[oscx]

@phhusson fyi, for SIM slot2 the airplane mode is ignored, keeps connected and receiving call-ins. with SIM slot1, everything is as expected, airplane mode considered properly etc.

[morfii83]

logcat_radio_03.03.2019_21.55.29.txt No incoming calls mtk6753 Cubot A5 on all treble firmwares what to do?

[phhusson]

Incoming what?

Le lun. 4 mars 2019 à 07:33, morfii83 notifications@github.com a écrit :

No incoming mtk6753 Kubota 5 on all treble firmwares what to do?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/57#issuecomment-469134986, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOOu0qL18N6CnQXCCiAwb22Z_WDCzhks5vTL40gaJpZM4UPGKc .

[morfii83]

Incoming what? Le lun. 4 mars 2019 à 07:33, morfii83 notifications@github.com a écrit : … No incoming mtk6753 Kubota 5 on all treble firmwares what to do? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#57 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOOu0qL18N6CnQXCCiAwb22Z_WDCzhks5vTL40gaJpZM4UPGKc .

No incoming calls mtk6753 Cubot A5 on all treble firmwares what to do? logcat_radio_03.03.2019_21.55.29.txt

[phhusson]

Please open a new issue for that.

Le lun. 4 mars 2019 à 08:48, morfii83 notifications@github.com a écrit :

Incoming what? Le lun. 4 mars 2019 à 07:33, morfii83 notifications@github.com a écrit : … <#m-6842673292304011513> No incoming mtk6753 Kubota 5 on all treble firmwares what to do? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#57 (comment) https://github.com/phhusson/treble_experimentations/issues/57#issuecomment-469134986>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOOu0qL18N6CnQXCCiAwb22Z_WDCzhks5vTL40gaJpZM4UPGKc .

No incoming calls mtk6753 Cubot A5 on all treble firmwares what to do? logcat_radio_03.03.2019_21.55.29.txt https://github.com/phhusson/treble_experimentations/files/2924775/logcat_radio_03.03.2019_21.55.29.txt

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/57#issuecomment-469151141, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOOlwtMCC5ezCn3j-O_hNOtfaB5ayxks5vTM_kgaJpZM4UPGKc .

[morfii83]

Please open a new issue for that. Le lun. 4 mars 2019 à 08:48, morfii83 notifications@github.com make

[uziylb]

Am new here and I have little understanding of GSI, I installed latest AsopExtended 9.0 GSI on mtk6739 and incoming calls works, LTE also works(sim1 only) but not SMS and sim 2 says no-service...how can I fix sim2 and SMS. Also am unable to root with magisk

[AHDianin]

Here is my feedback from the new releases on MTK6763.

V8.1.29 SMS: Working. Calls: Working. Data connection: Working. Hotspot: Working. Casting: Not working. NFC: Working.

V9.0.111 SMS: Working. Calls: Working. Data connection: Working. Hotspot: Not Working. Casting: Not working. NFC: Not Working.

Should be created new issues for these other parts?

[Skyrimus]

@phhusson no service on mt6735 any treble roms, imeis works, wifi and bt works, baseband in settings works log_aosp_9.txt

[zainarbani]

@Skyrimus this line ? can i see your tree ? log_aosp_9.txt

[uziylb]

The only GSI that data, sms, and calls works is AOSP STOCK by phusson... The rest no data works for mt6739

[p00f]

MT6737, 8.1 phh vanilla v31

I have incoming sms and stable, permanent signal but no incoming calls.

Incoming call log (adb logcat -b radio) : https://del.dog/xaqesacavo

I can see [UNSL][MTK]< responseCsNetworkStateChangeInd not implemented [SUB1], [UNSL][MTK]< crssIndication not implemented [SUB0], and RilMalClient: command Fd not ready here RILC-RP : No need to cache the request

in the log

[weirdal3333]

I have a MT6763 And yeah data doesn't work out of the box. Calls and SMS can only be sent, and not received.

I figured I would play with the APN settings a bit.... And figured out 4G/LTE data 😅 So, most devices get their settings from the Sim card, yeah? I'm pretty sure that that's not happening. Or, Ussd codes are getting stuck because MMS isn't being handled correctly.

Anyways, I changed one of the configured APNs (odd that there's no ok/cancel button when changing the 'bearer' settings...) to my carrier's settings, and I got data! 4G, LTE, Video/voice over LTE, etc.

I can only text and call out though. I called TMobile and got 2 techs to experiment with me. All sent texts and calls are successful. But it looks to them that my sim is deactivated. It's a very odd limbo situation.