MTK RIL Problems about treble_experimentations HOT 111 OPEN

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

from treble_experimentations.

@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.

from treble_experimentations.

from treble_experimentations.

i have redmi 6a, i tried phhs AOSP pie, i was not able to receive or send sms and volte calls.
however incoming and outgoing calls are working on 2g and 3g network. 4g data also works. please tell me a solution for sms.

from treble_experimentations.

Wound up SMS and calls to МТК6739(arm) setting the values ​​to 7
AT + EAIC = 7
But mobile Internet does not work how to be?

from treble_experimentations.

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!

from treble_experimentations.

@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 😕😔

from treble_experimentations.

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

from treble_experimentations.

If you need official MTK ALPS 8.1.0 sources, i can give you it.

from treble_experimentations.

@mmoreyrav Doesn't change anything on mt6735, still no output of ussd and no info about incoming call

from treble_experimentations.

Works on mediatek x20 SoC, I'll test later on more SoCs.

Thanks a lot for that @mmoreyrav !
FWIW, I had phhusson/platform_frameworks_opt_telephony@65a043e as work in progress to handle that, but I'm more than happy to scrap this and use your fix instead.

from treble_experimentations.

@phhusson Yeah, I was lucky to find that workaround. I was ready to try more desperate things like what you mention. I hope there's no more proprietary stuff needed to properly support MTK phones.
@Dinolek Maybe it has another problem. You should check the radio logs. This workaround only handles:
RILC-RP : incomingCallIndicationInd: radioService[0]->mRadioIndicationMtk == NULL

from treble_experimentations.

It seems that USSD codes were not fixed. When a final (USSD_MODE_NW_RELEASE) USSD message arrives, its contents are discarded by the telephony framework. I wonder why AOSP does that.

from treble_experimentations.

@mmoreyrav In mtk frameworks it handles it using onUssdStkHandling, which is pointless, because it is same as notify.
We can just output it as USSD_MODE_NOTIFY instead.

from treble_experimentations.

@Dinolek Yeah a simple fix in GsmCdmaPhone::onIncomingUSSD should be enough:

if (isUssdRelease && !TextUtils.isEmpty(ussdMessage)) {
    // Some mobile networks send a release message with text instead of a notify message
    found.onUssdFinished(ussdMessage, isUssdRequest);
} else if (isUssdRelease) { ...

But why it's not fixed, it should affect all phones on certain mobile networks.

from treble_experimentations.

Sorry, what does it mean that "incoming call approval" is disabled? Does that mean that when you receive a call it automatically answers it or that you can not have a blacklist?

from treble_experimentations.

have not yet solved the problem of ussd ???

from treble_experimentations.

@Taras2000 Well, somebody has to compile and test the fix I proposed and if it really fixes the USSD problem then @phhusson may want to include it. Though it's not really a phone hardware-related problem.

from treble_experimentations.

@mmoreyrav And where is this file and how is it called? I would try to edit

from treble_experimentations.

@Taras2000 I linked to it in one of my previous comments in this issue in exactly the point that needs fixing and with the source code that must be added. If should be simple enough to edit assuming that you know how to edit Java code and compile/build Android from source code.

from treble_experimentations.

Umidigi A1 pro has this issue too. MediaTek MT6757. Its the only thing stopping me using treble GSI for my phone at the moment. If anyone can tell me what needs changing am willing to test.

from treble_experimentations.

@stevea76 I assume you refer to the incoming calls not working issue and I suppose you have tried the latest phh-treble images that should fix that problem. I also assume that making calls, sending & receiving SMS and using mobile data work. If so then maybe your phone uses a different RIL implementation. So you could try searching all the files in /vendor/lib and also in /vendor/bin for the string "AT+EAIC=2". If you find a different file that has that string and you patch it as described above then it may fix the problem.

from treble_experimentations.

@mmoreyrav Yes to all of your reply. I used the latest images, used hex editor to replace the "AT+EAIC=2" with "AT+EAIC=3" still no luck with incoming calls. I used my landline to call, went to voicemail after 40 or so seconds, when disconnecting call I get a missed call alert message on the mobile.

from treble_experimentations.

Umidigi Z2 (MTK6763) No 4G cell signal and the only receiving weird 3G bands. Phone calls, incoming or outgoing, and cell data not working. Anything I can try editing to enable cellular data or is MTK ril update required?

from treble_experimentations.

I have the same problem with patched version ("AT+EAIC=3" is already in the libs). It works much better than before but after some time the phone just lose radio signal. I don't know what triggers it (sometimes it will break after answered call, sometimes it will work after call).
Any ideas how to try to provoke it?

Did someone try to use mtk-ril.so from stock ROM (although Android 8.0 at the moment, IIRC)?

USSD never worked for me, though.

from treble_experimentations.

At the risk of wasting time trying something which won't work, in which directory is mtk-ril.so found and would a different version be need for Android 8.x vs. 9? Factory ROM for my device is on 8.1 and I doubt Umidigi will be updating to 9 anytime soon if ever.

from treble_experimentations.

in my umidigi z2, at+eaic fixed the incoming call bug, but now remains the sms bug.. i cannot receive sms, only can send sms

from treble_experimentations.

@apogen
Which phh build do you have working cellular service and are you receiving 4G LTE signal? May I also ask which version of TWRP you used to load phh ROM for your Z2 as one on Umidigi website not working here.

There is a long list of possibilities for SMS issues however if you are using a Pixel based ROM, it may be an issue with Hangouts. For whatever reason, Pixel phones still include Hangouts app even if its not used for messaging. You might try installing it however make sure Messages is the default SMS app. Launch Hangouts app, tap 3 bars, settings, account, Calls and SMS - make sure Messages slider tab is off. I have had exact issue you described resolved because Hangouts Message tab was on.

from treble_experimentations.

in fact i flashed havocos through fastboot.. then directly boot to twrp (the one skeleton1911 post for umidigi z2) and flash opengapps nano.. then boot system, root using magisk and did mods to mtklib-ril files..

p.s. i also change those lines to build.prop in /vendor
persist.mtk_epdg_support to 0
persist.mtk_ims_support to 0

from treble_experimentations.

@8472
did you managed to achieve 4g?? also did any gsi image have sms receiving fixed?

from treble_experimentations.

No, I have not been able to get working 4G with any Treble GSI build. I think it will require help from phh.

from treble_experimentations.

@nithothidr
did you check if incoming sms working also??
i cant received sms

from treble_experimentations.

@apogen I have Umi z2 also, please what tool dit you use in editing vendor/lib/libmtk-ril.so

from treble_experimentations.

@MACROsoftOfficial
using mixplorer copy temporary limtk-ril.so of both lib and lib64 folders to your internal storage.. Then using hex editor (play store) edit both files.. Then using mixplorer again overwrite the files you modified back to lib and lib64 folder

from treble_experimentations.

@apogen please can you help me get the /lib/libmtk-ril.so and /lib64/libmtk-ril.so files of your Umi Z2 original? Because I am really finding it difficult editing these stuffs.All I see are series of 0's

from treble_experimentations.

@MACROsoftOfficial
https://mega.nz/#F!a4M0lCwZ!h5N_PWmUy3Rvz61dWHLCxA

from treble_experimentations.

@apogen thanks for swift response, but I am facing 2 issues (I) my device can't discover my sim cards anymore (2) after editing /vendor build.prop persist.mtk_epdg_support to 0
persist.mtk_ims_support to 0

My WiFi now goes on and of.
Pleas can you get me the default permission you are using for /vendor build.prop
and all default permission you are using for /lib and /lib64 maybe that will be of help if it doesn't work I hope you or anyone else can suggest me a solution

from treble_experimentations.

Patching AT+EAIC=2 to AT+EAIC=3 fixes incoming calls on MT6739 chipset, library located at /vendor/lib/libmtk-ril.so

adb root
adb remount
adb shell cp -a /vendor/lib/libmtk-ril.so /mnt/phh/libmtk-ril.so
adb shell sed -i -e 's/AT+EAIC=2/AT+EAIC=3/g' /mnt/phh/libmtk-ril.so
adb shell chcon "u:object_r:vendor_file:s0" /mnt/phh/libmtk-ril.so
adb shell mount -o bind /mnt/phh/libmtk-ril.so /vendor/lib/libmtk-ril.so
adb shell setprop ctl.restart ril-daemon-mtk
adb shell stop
adb shell start

how to be?

from treble_experimentations.

@MACROsoftOfficial
no need to edit biild.prop just copy and replace the libmtk-ril.so files using mixplorer, cause mixplorer set the appropriate permissions automatically

from treble_experimentations.

@apogen I still could nor get the incoming call working even after following your instructions.

N:B I am coming from Eragon V. 2 Rom, isn't this the same Rom you switched from?

from treble_experimentations.

@MACROsoftOfficial
no i am coming from latest stock rom and i have install havoc-os image

from treble_experimentations.

@apogen I will try flash the stock Rom later to see if that will fix it

from treble_experimentations.

@apogen I flashed the stock Rom before havoc OS but I still couldn't get the fix to work. And also are you able to use mobile data?

from treble_experimentations.

And also are you able to use mobile data?

no(

from treble_experimentations.

No I couldn't use it either

from treble_experimentations.

MT6735, ril not works after mtk-ril patch

from treble_experimentations.

phhusson, this is temporary fix for specified SoCs, but it need real fix for all mtk telephony, because this is fix not work on more mtk chipsets.

from treble_experimentations.

Why you don t use source code of official ALPS 8.1 to fix it? I gave you it in past year...

from treble_experimentations.

Chiming in -- no mobile data on either 3G or 4G on MT6739. Any help?

from treble_experimentations.

Chiming in -- no mobile data on either 3G or 4G on MT6739. Any help?

welcome aboard the MTK train

from treble_experimentations.

@medved9112 type adb shell first

from treble_experimentations.

I haven't had much time to troubleshoot this issue but did recently load a few GSI ROM on MTK6763 phone with mixed results regarding phone functionality. The one ROM that does seem to work is Benzo ROM. Can a few others try it and confirm LTE works for you as well?

from treble_experimentations.

from treble_experimentations.

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

from treble_experimentations.

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

from treble_experimentations.

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.

from treble_experimentations.

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.

from treble_experimentations.

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.

from treble_experimentations.

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 ???

from treble_experimentations.

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.

from treble_experimentations.

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

from treble_experimentations.

I will have time to try out this weekend.

from treble_experimentations.

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.

from treble_experimentations.

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

from treble_experimentations.

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.

from treble_experimentations.

from treble_experimentations.

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

from treble_experimentations.

latest gsi havoc 2.0 arm64 aonly

from treble_experimentations.

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

from treble_experimentations.

@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

from treble_experimentations.

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.

from treble_experimentations.

from treble_experimentations.

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.

from treble_experimentations.

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?

from treble_experimentations.

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

from treble_experimentations.

@svoboda18 no, RIL also includes SMS and VoLTE.

from treble_experimentations.

@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

from treble_experimentations.

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

from treble_experimentations.

@ironashram see and try #416

from treble_experimentations.

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)

from treble_experimentations.

All my builds have working adb root

from treble_experimentations.

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

from treble_experimentations.

@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.

from treble_experimentations.

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)

from treble_experimentations.

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

from treble_experimentations.

@ironashram see and try #416

thank you it works, will test better right now

from treble_experimentations.

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)

from treble_experimentations.

@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.

from treble_experimentations.

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

from treble_experimentations.

from treble_experimentations.

Incoming what? Le lun. 4 mars 2019 à 07:33, morfii83 [email protected] 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

from treble_experimentations.

from treble_experimentations.

Please open a new issue for that. Le lun. 4 mars 2019 à 08:48, morfii83 [email protected]
make

from treble_experimentations.

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

from treble_experimentations.

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?

from treble_experimentations.

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

from treble_experimentations.

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

from treble_experimentations.

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

from treble_experimentations.

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

from treble_experimentations.

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.

from treble_experimentations.