LocationReportEnabler
LocationReportEnabler copied to clipboard
GhostFlying
使用LRE后VoLTE无法开启
手机一加三，尝试过Lineage OS 14.1以及氧OS，开启LRE后VoLTE选项消失。卸载或冻结LRE后恢复正常。（Android N没有Xposed我也很绝望啊……）
可以选择一个有 voLTE 的美国运营商代码即可。。
On Thu, Jun 29, 2017, 11:18 AM QSCFTHMKO [email protected] wrote:
手机一加三，尝试过Lineage OS 14.1以及氧OS，开启LRE后VoLTE选项消失。卸载或冻结LRE后恢复正常。（Android N没有Xposed我也很绝望啊……）
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GhostFlying/LocationReportEnabler/issues/73, or mute the thread https://github.com/notifications/unsubscribe-auth/AD1VcSjFLq2f6Gf2nSmmNFiggHN0vFIVks5sIxeNgaJpZM4OIx2h .
好吧之前版本（1.4.1）在Lineage OS上也怀疑过这个问题，试过几个发现还是没有开启VoLTE选项，后来发现LRE在氢OS不起效，就没试那么多代码了，现在找到一个T-Mobile USA的代码310260，目前VoLTE通话数据正常（主用移动卡，联通电信不知道是否起效），只是信号栏原本显示4G，现在显示LTE，或许可以加入到可选选项中以备有需求的用户选用？ 不得不说VoLTE的通话质量好了不少，而且有些地方移动2G信号还不如4G，不开这个电话都断断续续。
我之前试过 TM 的代码，不知道为啥在我这存在一些奇怪的 bug。。所以没修改成默认，我有空再试试
On Sun, Jul 2, 2017 at 5:15 PM QSCFTHMKO [email protected] wrote:
好吧之前版本（1.4.1）在Lineage OS上也怀疑过这个问题，试过几个发现还是没有开启VoLTE选项，后来发现LRE在氢OS不起效，就没试那么多代码了，现在找到一个T-Mobile USA的代码310260，目前VoLTE通话数据正常（主用移动卡，联通电信不知道是否起效），只是信号栏原本显示4G，现在显示LTE，或许可以加入到可选选项中以备有需求的用户选用？ 不得不说VoLTE的通话质量好了不少，而且有些地方移动2G信号还不如4G，不开这个电话都断断续续。
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/GhostFlying/LocationReportEnabler/issues/73#issuecomment-312479924, or mute the thread https://github.com/notifications/unsubscribe-auth/AD1VcZ4-ovpUQPWtEl0Y-rMzgHDcq697ks5sJ1_KgaJpZM4OIx2h .
Great. Shall we use 310260/311480 as default?
Source: https://android.googlesource.com/platform/packages/apps/CarrierConfig/+/refs/heads/master/assets
As I tested, if it set to 310260, users in some operator like Hangzhou Unicom will receive strange sms with content "目标地址不可达" from 10655133 even if VoLTE disabled.
I will try to add an option next version but not be the default.
It seems 310030 is not an officially supported numeric. I suggest using these for VoLTE:
310028
310160 (also Wi-Fi calling)
310200 (also Wi-Fi calling)
310210 (also Wi-Fi calling)
310220 (also Wi-Fi calling)
310230 (also Wi-Fi calling)
310240 (also Wi-Fi calling)
310250 (also Wi-Fi calling)
310260 (also Wi-Fi calling & video calling)
310270 (also Wi-Fi calling)
310300 (also Wi-Fi calling)
310310 (also Wi-Fi calling)
310490 (also Wi-Fi calling)
310530 (also Wi-Fi calling)
310580 (also Wi-Fi calling)
310590 (also Wi-Fi calling)
310640 (also Wi-Fi calling)
310660 (also Wi-Fi calling)
310800 (also Wi-Fi calling)
311390
311480 (also video calling)
I will test these to check if any one can enable VoLTE and not cause other issues.
I have tested some of these code, unfortunately there is always some strange sms after every reboot.
As this reason, I do not think set VoLTE enabled code as default is the best way, I am considering which one is better among add an option or a promot.
On Sat, Jul 15, 2017, 9:49 PM Mygod [email protected] wrote:
I'm using 310260 and everything is working fine so far on cheeseburger.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/GhostFlying/LocationReportEnabler/issues/73#issuecomment-315535148, or mute the thread https://github.com/notifications/unsubscribe-auth/AD1Vcf1hHrFaDh_HG3cj74OvtkfOTNWcks5sOMNmgaJpZM4OIx2h .