Related
Here is a guide how to enable VOLTE in RR without Jio4gvoice app.
Supported ROM :
RR 5.7.4
Instructions
1. Open ES File manager and enable hidden folder. Search .Jio4gvoive folder delete it. Then delete jio4g app and voice app.
2. Now again install jio4g voice app and register through it.
3. Now Delete Jio4gvoice app.
4. Open dialer and dial *#*#4636#*#* .
5. Scroll to end and open OEM specific settings.
6. And turn on MBN AUTO LOAD, volte debug, VT DEBUG, WFC DEBUG. ( After clicking on it will show turn off so don't get confused with it. )
7. In SIM Settings Disable Connected line indetification & open APN settings.
8. And If you have loop APN just edit APN "www" to "jionet" and save it. Keep APN PROTOCOL AND ROAMING PROTOCOL TO "IPv4" otherwise internet will not work.
9. Now reboot to recovery and wipe dalvik cache and cache only.
10. Restart your device and open dialer.
Workaround :
If you are not getting network in jio then open system ui tuner by pressing on settings icon in Qs panel or search it in setting.
Then add tiles "LTE" . Now enable LTE from QS Panel(check screenshot) You will get network.
If you are getting volte icon like volte1 and volte2 then volte is enable. Just try to call and enjoy. If it's help just click thanks.
If anyone is on lineage os try this and report me back if it's working on it too then I will edit it to lineage os too.
Those who will publish this guide in their site please give proper credits.
screenshot.
Thnx.. alot.. worked for me..in one go...:good:
Not this one but simple trick worked for me given by @TechGeekD without first step
no need to download any application to fix VoLTE
1). clean install latest build
2). goto settings -> SIM cards
3). set cellular data to Jio 4g & Calls to Jio
4). goto SIM 1 settings (or SIM 2 settings if Jio is in sim slot 2 )
5). see if Enhanced 4G LTE Mode is enabled or not !! enable it if not
6). goto Access Point Names (aka APN)
7). select 3 dot menu press Reset to default
8). add new APN with settings given below
APN SETTINGS
Name: ims
APN: IMS
APN Type : IMS
(notice one thing APN Type & APN is written in Capital !!!)
do not restart thats the bug ims setting stays there but not visible in settings cause after restarting we can not add new ims setting with same APN and APN Type but simple tweaking with APN & APN Type will fix it (but still don't restart after VoLTE gets working it will be gone again and you can't tweak it now)
Edit :- Selinux needs tobe on permissive mode
rohansalunkhe71 said:
Not this one but simple trick worked for me given by @TechGeekD without first step
no need to download any application to fix VoLTE
1). clean install latest build
2). goto settings -> SIM cards
3). set cellular data to Jio 4g & Calls to Jio
4). goto SIM 1 settings (or SIM 2 settings if Jio is in sim slot 2 )
5). see if Enhanced 4G LTE Mode is enabled or not !! enable it if not
6). goto Access Point Names (aka APN)
7). select 3 dot menu press Reset to default
8). add new APN with settings given below
APN SETTINGS
Name: ims
APN: IMS
APN Type : IMS
(notice one thing APN Type & APN is written in Capital !!!)
do not restart thats the bug ims setting stays there but not visible in settings cause after restarting we can not add new ims setting with same APN and APN Type but simple tweaking with APN & APN Type will fix it (but still don't restart after VoLTE gets working it will be gone again and you can't tweak it now)
Edit :- Selinux needs tobe on permissive mode
Click to expand...
Click to collapse
This is a permanent fix. His method is temporary due to restart won't allow volte. But this method works charming after restart also. Your choice, I am not forcing...
Not working here. I am on R 5.7.4. Had done a clean flash.
Tried every method. And even if VoLTE works, neither you can send sms nor receive.
Njishi said:
Not working here. I am on R 5.7.4. Had done a clean flash.
Tried every method. And even if VoLTE works, neither you can send sms nor receive.
Click to expand...
Click to collapse
Same here not working.. we have to wait for proper fixes by the devs
Sent from my LeEco Le 2 using XDA Labs
mdfarazb2 said:
Same here not working.. we have to wait for proper fixes by the devs
Sent from my LeEco Le 2 using XDA Labs
Click to expand...
Click to collapse
That's why moved on to stock until codeworkx will remove VoLTE fix from the to do list. And i yes i have a lot a patience. So i can wait. As developers has their personal life. And they have to manage it.
Njishi said:
That's why moved on to stock until codeworkx will remove VoLTE fix from the to do list. And i yes i have a lot a patience. So i can wait. As developers has their personal life. And they have to manage it.
Click to expand...
Click to collapse
yup.. I'm too waiting no hurry... Not a Hardcore VoLTE user
Sent from my LeEco Le 2 using XDA Labs
mdfarazb2 said:
yup.. I'm too waiting no hurry... Not a Hardcore VoLTE user
Sent from my LeEco Le 2 using XDA Labs
Click to expand...
Click to collapse
Yea !!! Problem is with SMS too... Until Dev fix those things we can have call... Hope so it will be fixed soon. I think there would be frimware patch.
not working on lineage os 14.1 december 22, 2017 build
veer.killerboy said:
Here is a guide how to enable VOLTE in RR without Jio4gvoice app.
Supported ROM :
RR 5.7.4
Instructions
1. Open ES File manager and enable hidden folder. Search .Jio4gvoive folder delete it. Then delete jio4g app and voice app.
2. Now again install jio4g voice app and register through it.
3. Now Delete Jio4gvoice app.
4. Open dialer and dial *#*#4636#*#* .
5. Scroll to end and open OEM specific settings.
6. And turn on MBN AUTO LOAD, volte debug, VT DEBUG, WFC DEBUG. ( After clicking on it will show turn off so don't get confused with it. )
7. In SIM Settings Disable Connected line indetification & open APN settings.
8. And If you have loop APN just edit APN "www" to "jionet" and save it. Keep APN PROTOCOL AND ROAMING PROTOCOL TO "IPv4" otherwise internet will not work.
9. Now reboot to recovery and wipe dalvik cache and cache only.
10. Restart your device and open dialer.
Workaround :
If you are not getting network in jio then open system ui tuner by pressing on settings icon in Qs panel or search it in setting.
Then add tiles "LTE" . Now enable LTE from QS Panel(check screenshot) You will get network.
If you are getting volte icon like volte1 and volte2 then volte is enable. Just try to call and enjoy. If it's help just click thanks.
If anyone is on lineage os try this and report me back if it's working on it too then I will edit it to lineage os too.
Those who will publish this guide in their site please give proper credits.
Click to expand...
Click to collapse
Please help me out bro
im using le 2 x 526 and recently changed rom to lineage os from stock rom.
i couldnot use volte to make calls without jio4g voice app.
please help me to fix this
Nykenztron said:
Please help me out bro
im using le 2 x 526 and recently changed rom to lineage os from stock rom.
i couldnot use volte to make calls without jio4g voice app.
please help me to fix this
Click to expand...
Click to collapse
Did you tried these workaround? Can you get volte icon in dialer in front of sim1 and sim2? If you are able to call through jio4g voice app. Follow steps from starting like deleting .jio4g voice folder and all that. These were tested personally by me in RR . If nothing works I better recommend you to flash 19s eui then clean flash lineage latest rom ( for bugs report to rom's threads) don't try to flash any other bootloader or modem files. As @codeworkx also mentioned that lineage is nothing to do with bootloader or modem. Note - MM have issues but nougat don't.
veer.killerboy said:
Did you tried these workaround? Can you get volte icon in dialer in front of sim1 and sim2? If you are able to call through jio4g voice app. Follow steps from starting like deleting .jio4g voice folder and all that. These were tested personally by me in RR . If nothing works I better recommend you to flash 19s eui then clean flash lineage latest rom ( for bugs report to rom's threads) don't try to flash any other bootloader or modem files. As @codeworkx also mentioned that lineage is nothing to do with bootloader or modem. Note - MM have issues but nougat don't.
Click to expand...
Click to collapse
it didnt work.
thereis no .jio4gvoice folder i checked even in hidden files and root explorer.
can you direct me to any tutorial video?
Nykenztron said:
it didnt work.
thereis no .jio4gvoice folder i checked even in hidden files and root explorer.
can you direct me to any tutorial video?
Click to expand...
Click to collapse
What is your apn?
Nykenztron said:
it didnt work.
thereis no .jio4gvoice folder i checked even in hidden files and root explorer.
can you direct me to any tutorial video?
Click to expand...
Click to collapse
Try other JIO sim from a VoLTE supported phone.
OR
Put your JIO sim in other phone which have VoLTE working then put it back to your phone, try both method because this helped me sometimes.
Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.
Not working on non rooted device.
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
any idea how the phone detects that its india? Could we spoof that?
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+
MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.
kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)
Many people have had this question in mind.
Tech is there to use it (source: gsmarena, sc below)
but why im not able to use it?
Has anyone been able to enable it with root access?
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
justanpotato said:
Many people have had this question in mind.
Tech is there to use it (source: gsmarena, sc below)
but why im not able to use it?
Has anyone been able to enable it with root access?
Click to expand...
Click to collapse
RoSk0BoSk0 said:
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
Click to expand...
Click to collapse
Which command did you use to enable VoLTE via ADB?
_mysiak_ said:
Which command did you use to enable VoLTE via ADB?
Click to expand...
Click to collapse
You need temporary root for them, there are many guides for that.
This goes after successful "adb shell"
Code:
$su
#setprop persist.dbg.ims_volte_enable 1
#setprop persist.dbg.volte_avail_ovr 1
#setprop persist.dbg.vt_avail_ovr 1
#setprop persist.dbg.wfc_avail_ovr 1
Other threads suggest these too, but haven't done them. I've had network fluctuations with them, but YMMV.
Code:
#setprop persist.radio.rat_on combine
#setprop persist.radio.data_ltd_sys_ind 1
#setprop persist.radio.data_con_rprt 1
#setprop persist.radio.calls.on.ims 1
Credits to: @ToucanSam [MODULE v17.x] VoLTE & VoWiFi Enabler (2018-09-20)
RoSk0BoSk0 said:
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
Click to expand...
Click to collapse
My carrier supports it. But for some odd reason its not working at all.
My previous phone s6edge+ had no problems with connecting to my carrier LTE-A network.
Any ideas ?
((EDIT))
Its working now
Hi Let me introduce tutorial, how to enable VoLTE/VoWiFi for some other carriers. All credits goes to @Airpil for his great work with enabling diag port for Pixel 2 phones and to @topjohnwu for his original Magisk project.
UPDATE:
Here is another way by @Vortuks , how to get things working.
Code:
https://github.com/stanislawrogasik/Pixel2XL-VoLTE-VoWiFi
ANOTHER UPDATE:
On Android 11 you can use module VoLTE_enabler_pixel_2_v1_1.zip, but you will myabe need to use SeLinux permissive module too.
BIG UPDATE:
use only on PIE
for android 10 use solution with PDC tool
I created new magisk module with everything needed for enabling VoLTE. Just install VoLTE_enabler_pixel_2_v1_1.zip and enjoy.
this will work only, if there is proper *.mbn for your provider
sometimes is needed to remove/add module after updating monthly updates
sometimes is needed to toggle off/on enhanced 4g LTE mode and go to airplane mode and back
Prerequizites:
your carrier have to support this feature
and you have to enable this feature on operator's side
PC with windows
you must have some luck
Prepare your PC:
google for QPST_2.7.474 and install it
install provided drivers (if they willn't work, google for better)
from provided nokia_mbn_files.zip find the right mcfg_sw.mbn for your carrier, if there isn't any mbn for your carrier, you can try another one, but without warranty
Prepare your phone:
backup everything, what you can especially EFS partition - just for sure
root your phone with provided Magisk.zip
boot up your phone
In Magisk Manager app find and install VoEnablermodule, restart phone
there will be new settings under Settings-Network & internet-Mobile network-Advanced
connect phone to PC and set to charge only mod
in terminal emulator run this commands (this will enable diagnostic port on phone):
Code:
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
click load button and find prepared mcfg_sw.mbn file
now right-click on new loaded profile and select SetSelectedConfig - Sub0
and now button Activate
activate provided VoEnabler module via MagiskManager
restart device
and now, if you are lucky one, your VoLTE is working :victory:
Final steps:
if everything is working, you should reinstall original Magisk from twrp
Troubleshhoting:
99,9% of all problems comes with wrong driver
open windows device manager and try to choose another driver for HW like:
Qualcomm HS-USB Modem 9091
Qualcomm HS-USB Diagnostics 9091
Qualcomm HS-USB WWAN Adapter 9091
Is it working?
dial *#*#4636#*#*
Phone information-3dots-IMS service status
If IMS Registration: Registered and Voice over LTE: Available you won
after update with factory images you will have to re-do this steps
Confirmed carriers:
Czech T-mobile
VoLTE - yes
VoWiFi - no
Poland Orange(confirmed by @saperkus)
VoLTE - yes
VoWiFi - yes
Poland Play(confirmed by @saperkus)
VoLTE - yes
VoWiFi - yes
Telenor Bulgariawith Telenor Danemark mbn (confirmed by @pavel5044)
VoLTE - yes
VoWiFi - no
T-Mobile Hungary (Telekom)(confirmed by @hunfatal)
VoLTE - yes
VoWiFi - no
Downloads:
Code:
Drivers:
[url]https://mega.nz/#!oMEHTIbA!0g7ahr8r81Q3ue8LpEy-sfd7FTLEEQlGRi2CJfG_Kq0[/url]
somin.n said:
Hi Let me introduce tutorial, how to enable VoLTE/VoWiFi for some other carriers. All credits goes to @Airpil for his great work with enabling diag port for Pixel 2 phones and to @topjohnwu for his original Magisk project.
Prerequizites:
your carrier have to support this feature
and you have to enable this feature on operator's side
PC with windows
you must have some luck
Prepare your PC:
google for QPST_2.7.474 and install it
install provided drivers (if they willn't work, google for better)
from provided nokia_mbn_files.zip find the right mcfg_sw.mbn for your carrier, if there isn't any mbn for your carrier, you can try another one, but without warranty
Prepare your phone:
backup everything, what you can especially EFS partition - just for sure
root your phone with provided Magisk.zip
boot up your phone
In Magisk Manager app find and install VoEnabler module, restart phone
there will be new settings under Settings-Network & internet-Mobile network-Advanced
connect phone to PC and set to charge only mod
in terminal emulator run this commands (this will enable diagnostic port on phone):
Code:
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
click load button and find prepared mcfg_sw.mbn file
now right-click on new loaded profile and select SetSelectedConfig - Sub0
and now button Activate
and now, if you are lucky one, your VoLTE is working :victory:
Final steps:
if everything is working, you should reinstall original Magisk from twrp
Troubleshhoting:
99,9% of all problems comes with wrong driver
open windows device manager and try to choose another driver for HW like:
Qualcomm HS-USB Modem 9091
Qualcomm HS-USB Diagnostics 9091
Qualcomm HS-USB WWAN Adapter 9091
Is it working?
dial *#*#4636#*#*
Phone information-3dots-IMS service status
If IMS Registration: Registered and Voice over LTE: Available you won
Downloads:
Code:
Drivers:
[url]https://mega.nz/#!oMEHTIbA!0g7ahr8r81Q3ue8LpEy-sfd7FTLEEQlGRi2CJfG_Kq0[/url]
Click to expand...
Click to collapse
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
please get back to me ASAP.
thankyou
royroyal said:
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
please get back to me ASAP.
thankyou
Click to expand...
Click to collapse
Hi, yeah, my mistake :angel: You have to use "su" command first to allow root access. Full command is:
Code:
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
And please, don't quote full first post
somin.n said:
Hi, yeah, my mistake :angel: You have to use "su" command first to allow root access. Full command is:
And please, don't quote full first post
Click to expand...
Click to collapse
Yes sorry for replying over the OP.
Yes i knew already to use "su" inorder to grant supersu access, but this didnt work for me and i am not able to proceed. Husssshh..
royroyal said:
Yes sorry for replying over the OP.
Yes i knew already to use "su" inorder to grant supersu access, but this didnt work for me and i am not able to proceed. Husssshh..
Click to expand...
Click to collapse
Hmm, should work? Try to write it, not copy... Try the other command without changing enfonforcing, it is maybe not necessary.
somin.n said:
Hmm, should work? Try to write it, not copy... Try the other command without changing enfonforcing, it is maybe not necessary.
Click to expand...
Click to collapse
Tried to write as well as copying, also tried without the 1st command but no luck.. and as no one has tried this yet aslo not able to know if this is happening with my device only.
royroyal said:
Tried to write as well as copying, also tried without the 1st command but no luck.. and as no one has tried this yet aslo not able to know if this is happening with my device only.
Click to expand...
Click to collapse
Interesting try to restart your phone, open windows device manager, connect phone (now should be detected some new hw), open terminal and write commands and look, if some new hw was detected or if you have some new unknown devices in device manager. You should also look to Airpil's thread for some help.
Code:
[url]https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967[/url]
somin.n said:
Interesting try to restart your phone, open windows device manager, connect phone (now should be detected some new hw), open terminal and write commands and look, if some new hw was detected or if you have some new unknown devices in device manager. You should also look to Airpil's thread for some help.
Click to expand...
Click to collapse
Will try this and update here
Successfully enable volte on my pixel2,Thanks!
Please provide carrier details in your post guys! With that being said, has anyone got it to work on Straight Talk (Verizon or ATT sim?)
Enable VoLTE for Vodafone in India
Vodafone in India has not provisioned the Pixel 2 till yet for VoLTE despite many people getting after them. A lot of noise was generated by users when Google pointed out that they had done what was required in the Android Pie updates.
Many thanks for this guide as it has helped me to enable VoLTE on my Pixel 2. On checking with *#*#4636#*#* it shows that VoLTE is now provisioned for voice. I now need to connect to any other phone where VoLTE is working and see if it indeed connects using VoLTE.
The only problem I had was in opening the port before using QPST. I had to type in the commands a second time in the terminal and then the port opened allowing me to proceed.
almightysiman said:
Successfully enable volte on my pixel2,Thanks!
Click to expand...
Click to collapse
Hi,
did u do it over the stock rom/kernel or on any custom kernel.
and can u post every step that u did to get it done.
currently i m on pure stock 9.0 pie with locked bootloader on february security patch.
this is my previous comment over the thread..
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
royroyal said:
Hi,
did u do it over the stock rom/kernel or on any custom kernel.
and can u post every step that u did to get it done.
currently i m on pure stock 9.0 pie with locked bootloader on february security patch.
this is my previous comment over the thread..
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
Click to expand...
Click to collapse
I am on du rom.you should type su before setenforce 0
Hadookie said:
Please provide carrier details in your post guys! With that being said, has anyone got it to work on Straight Talk (Verizon or ATT sim?)
Click to expand...
Click to collapse
I'm back overseas now, but while I was home for the holidays I used a Straight Talk ATT sim and had no problems using the MagiskHide Props module to manually add the lines from this module:
https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613
It was somewhat inconsistent though. Seemed to only work with certain people I called. Also, I use Google Voice when I'm home, so that may account for the inconsistency.
I haven't tried the method outlined by the OP, though. I've had a solid setup for months now and I'm a bit hesitant to try anything that might kink it up.
Edit:
Now that I think about it, I never checked the IMS Registration to be sure, so I can't be sure if it was actually working, but it would show the "HD" calling icon on the dialer screen when connected, so I just assumed it was working.
Thank you for sharing this guide.
I can confirm, that VoLTE and VoWiFi is working fine in Orange Poland and PLAY (Poland). In case of PLAY, both services are disabled by default. You have to contact with service provider and ask them to enable WiFi Calling. By enabling it, VoLTE will be also enabled.
saperkus said:
Thank you for sharing this guide.
I can confirm, that VoLTE is working in Orange Poland and VoLTE and VoWiFi is working in PLAY (Poland). In case of PLAY, both services are disabled by default. You have to contact with service provider and ask them to enable WiFi Calling. By enabling it, VoLTE will be also enabled.
Click to expand...
Click to collapse
Any chance to get WiFi calling working on Orange PL?
And will this work at all on OG Pixel?
bige93 said:
Any chance to get WiFi calling working on Orange PL?
Click to expand...
Click to collapse
It seems, that I haven't been patient enough in case of Orange PL... I have redone the tests and was able to make VoWiFi to work. There's a need to reboot the device after swapping SIM cards. After reboot, VoWiFi works fine.
bige93 said:
And will this work at all on OG Pixel?
Click to expand...
Click to collapse
You're free to check it. I've checked on Nexus 5X and it didn't work at all.
saperkus said:
It seems, that I haven't been patient enough in case of Orange PL... I have redone the tests and was able to make VoWiFi to work. There's a need to reboot the device after swapping SIM cards. After reboot, VoWiFi works fine.
You're free to check it. I've checked on Nexus 5X and it didn't work at all.
Click to expand...
Click to collapse
Do I have to use some special ("diag") version of the Magisk as it says it the 1st post? Can't find 'magisk diag' for Sailfish.
bige93 said:
Do I have to use some special ("diag") version of the Magisk as it says it the 1st post? Can't find 'magisk diag' for Sailfish.
Click to expand...
Click to collapse
This is a modded version of Magisk, which gives an ability to enable diagnostic port (normally it can't be enabled). It was prepared for Pixel 2 XL, but it also works fine with Pixel 2. I can't tell, if you need to use this version or not. Install standard Magisk version and check if you can enable this port using provided commands. If not, then it's up to you to decide, if you want to check modded version of Magisk or not.
Has anybody tried to install the modified Magisk on android Q Beta yet? I am getting error 1, it doesn't install
This guide is for academic and development purposes only and should not be used to circumvent any contracts you have with you cell carrier.
You need to be rooted in order to enable wifi tethering.
Rooting and editing your stock image voids most warranties.
Follow this guide at your own risk. (I can't take responsibility for you braking your phone)
1. Install a Build.prop editor(this isn't mandatory but I find it makes things easier) I use this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US
2. add the following line to the build prop: net.tethering.noprovisioning=true
3. Reboot your phone
4. Profit
SAVED
dtb1987 said:
2. add the following line to the build prop: net.tethering.noprovisioning=true
Click to expand...
Click to collapse
Which section of the build prop did you put it in?
gargleblarg said:
Which section of the build prop did you put it in?
Click to expand...
Click to collapse
I normally put it at the end
dtb1987 said:
I normally put it at the end
Click to expand...
Click to collapse
Thanks, it works like a charm .
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually
dtb1987 said:
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually
Click to expand...
Click to collapse
You can't run an OTA update on a modified boot image. You use Magisk to revert the boot image back to stock, run the update and re-root. Since it's a systemless root and you don't modify anything directly in the system image, therefore you don't have to revert back to stock system.
I was just offering a quick heads up for those who may be rooted with Magisk, on how to properly modify the build prop without modifying system directly. It's a good thing to learn since many times you'll have to modify those init scripts anyway.
How do I add it to magisk, I'm totally new to it.
Question: I currently have AT&T's (really lame) tethering plan, and my data plan is capped at 5GB data (for my business, AT&T does not offer an unlimited data plan with tethering). So I currently have the ability to turn on/off the Wifi hotspot setting in the phone Settings.
I just rooted the phone and did your update. To test success, I now have to change my plan to unlimited data (no tethering). When I do this, I should be able to still turn on/off the Wifi hotspot via the phone Settings (even though I no longer have the plan with the tethering feature)? Thank you.
issues with Android 10?
Hi, I followed these instructions and all is good.... But I'm stuck on Android 9, holding off on moving to Android 10 due to what I've read in other posts about this technique no longer working. Thought I'd check back to see if anyone has had success upgrading to Android 10 - and enabling wifi tethering via the technique mentioned above. Thanks.
Tethering on Android 10
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.
DaBigGoog said:
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.
Click to expand...
Click to collapse
Awesome - thank you!
saved
duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
I don't understand how to do this or what it means. I have root magisk on sm-a235f
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true