Related
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
+1 intrested to this. I have a lg g watch r.
In Cinema Mode i have Touch2Wake disabled but watch dont show anything and does not vibrate. It becomes really useless if it does not vibrate In Cinema Mode.
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
I am also searching for this:good:
I've been looking everywhere for a solution to this. I hasn't even considered it as an issue, but just a couple of days is enough to make me realise this is a requirement. I can't believe it didn't come up in development! Aside from your own accidental touches, there's also the issue of inquisitive fingers from children touching that nice shiny screen... Tapping the side button to wake the screen would be perfect (whilst retaining the monochrome screen and notifications).
Cinema mode is really dumb. Just very poorly thought out. There has got to be a way to disable touch to wake. Or even enable vibrating notifications in cinema mode.
Yes there is a way
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
adb root
adb push /system/usr/idc/sec_touchscreen.idc <choose where you want to have the file in your pc>
Click to expand...
Click to collapse
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
adb pull <where you have the file> /system/usr/idc/
Click to expand...
Click to collapse
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
adb pull <where you have the copy> /system/usr/idc/
Click to expand...
Click to collapse
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
dataonlycod said:
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
Click to expand...
Click to collapse
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
-RioT- said:
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
Click to expand...
Click to collapse
Yep you can use it to wake up the device. But as I say, make a backup because this happen with my alpha of the gear 2 neo, so probably this is not going to work with other devices. Just in case xD
Works for me on LG G Watch R
The file name is different "synaptics_rmi4_i2c.idc"
Same edit, copied to sdcard and moved in recovery to /system/usr/idc/ as mentioned above.
I have swipe menu still available and I can swipe down for the quick toggles.
Button is used to wake (and I use screen always on)
Going to be interesting how this performs in the shower and in general. Thanks to the suggestion posted.
Any update on this after using it for a while? Looking to apply this to my LG G watch R running the Urbane port.
Ok well i tried it any ways and i still have the problem when my arms are crossed my arm starts doing things on my watch...
Starting from version 1.6 this app supports wake on touch changing - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings (here is apk - View attachment AdvancedSettings-v1.6-11.apk)
I downloaded the advanced settings app tried the disable touch wake... it doesn't wake but you can still scroll notifications and long press to change the face.
Any chance of completely turning off the touch screen while in sleep...
..
castructuraleng said:
I tried the Advanced Settings app on my LG Watch Urbane 2nd Edition with Android 6.0.1, which is not rooted. It has an option for "Touch to wake screen" that I tried to set to "off"; however, when I go back to look at it, it is always set to "on". Do I need to root to have this stay, or is the app just not compatible with 6.0.1?
Update... just answered my own question. It appears you need to be rooted to do this.
Click to expand...
Click to collapse
Yep, it works on Marshmallow 6.0.1 when Rooted. Just tested it on my Huawei Watch.
..
I installed "Showear". You can set a simple touch pattern to unlock the watch. Crossing your arms will no longer trigger any action on your watch (except making the screen on).
..
..
Hi m8. I've done this on my LG urbane and works just fine ty a lot... but i modified a little your steps...
1) My lg urbane is rooted
2) I went to the ADB folder in my PC (using windows explorer) then using shift+right click i select "open command window here"
3) in this command window i did:
adb reboot bootloader
fastboot flash recovery (starts twrp)
in the TWRP:
Go to "Mount"
tick the "system" box
In the command window :
adb pull /system/usr/idc/synaptics_rmi4_i2c.idc (Dont need to select the folder, will appear in the ADB folder used to open the command window)***
*** When i tried to write the destination folder have not worked so i strongly advise not to fill this part, the command in the beginning is PULL not PUSH to take from the device and the file to be taken from the device had a different name as someone have stated before ***
4) In the notepad i did
I opened the file with the notepad and edit "touch.wake = 1" to "touch.wake = 0" (I did not delete this part just change the value)
5) in the command window:
adb pull <where you have the file> /system/usr/idc/
6) Reset my phone and works great!
Anyone else able to get it to work? Just stays stuck on Connecting or Identifying Network on my laptop.
Mine is working fine
LeEco Pro3
I have T-Mobile One Plus Promo TI plan and when NOT roaming internationally WiFI Hotspot (tethering) works out of the box. When roaming internationally on stock ROM the tethering will connect to the other device but will not allow internet to pas through. Yes, I know the terms and conditions do not support international tethering (but I want it for emergency use). Using custom ROM like Lineage OS (LOS) 13 the tethering works all the time; but on LOS 14 there is not VOLTE and no version of AOSP/LOS support WiFi Calling.
To allow full tethering internationally on T-Mobile or any other carrier which limits Hotspot do this (Tested on Stock 19s or 21s):
To sum it up:
Must be Rooted
Add to your build.prop: net.tethering.noprovisioning=true
Open terminal emulator and type:
Su
settings put global tether_dun_required 0
Long Directions from another thread:
To begin, you will need apps to edit the Build.Prop and enter Terminal Commands. (Play Store apps I used "Material Terminal" and "BuildProp Editor")
1. Launch the BuildProp Editor app and tap the menu icon (the 3 vertical dots) found on the top right of your screen. When the dialog box appears, tap on + New.
2. When the + New system property dialog box appears, under the first subheading Name type in the following: net.tethering.noprovisioning. In the next subheading named Value, type in the following: true. Once completed, press SAVE. You may be prompted to give BuildProp Editor root access. Choose GRANT and exit the app.
3. Launch the Material Terminal app.
4. In the first command line, type su and then tap enter to give it root access.
5. When the next command line appears below, type settings put global tether_dun_required 0 and then tap enter. Please note that there must be a space between the words settings and put, put and global, global and tether and required and 0. You will not believe how many people type this all as one word.
6. Exit the Material Terminal app and reboot your device. If the steps were followed carefully, you should now be able to use your device as a wi-fi hotspot without being prompted on your connecting devices to change/upgrade your data. This method should also work on other android devices.
This method was found by another user / thread but is useful for LeEco Pro 3. https://forum.xda-developers.com/axon-7/how-to/how-to-enable-wi-fi-hotspot-t3448434
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
lakitu47 said:
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
Click to expand...
Click to collapse
I did it over adb yes, but on the newest release of fire OS (5.6)
wieli99 said:
I did it over adb yes, but on the newest release of fire OS (5.6)
Click to expand...
Click to collapse
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Sent from my Amazon KFGIWI using XDA Labs
lakitu47 said:
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Click to expand...
Click to collapse
It works for me in adb shell with
pm clear --user 0 com.amazon.kindle.kso
Well, I don't know if this will work with your exact tablet, but try this:
1. If you haven't already, get the Google Play store/services on your tablet
2. Download this app without the quotes: "https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en"
3. Follow on-screen instructions to grant tablet permission to edit secure settings (worked on 2 devices on 5.6)
BE CAREFUL WHAT YOU EDIT. If you change the wrong settings, your tablet can and probably bootloop or get bricked.
4. Go to the "secure" tab, scroll down to "limit_ad_tracking" and change value to 1
5. Go to "global" tab, scroll down to "LOCKSCREEN_AD_ENABLED" and change value to 0. Immediately reboot your device.
This was tested and worked on two HD 8 tablets on 5.6, with special offers manually disabled on 5.4. Since Amazon still thinks you are subscribed to special offers (ads), the notifications are hidden. This workaround actually makes the ads gone (hopefully), so the notifications will appear as soon as you turn on the screen, without a swipe down gesture.
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
do you have to have root for this? i did su and it said, " su not found."
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
Like that one eh? That was one of the first ones I found. Works without root too.
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
dondraper23 said:
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
Click to expand...
Click to collapse
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/hd8-hd10/help/root-required-completely-disable-enable-t3739257
I just had to do it again today because attempted to use Xposed and wound up getting in over my head and got caught in a bootloop, but at least I can reaffirm that this guide works
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
DragonFire1024 said:
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
I love all your posts- it's your guide I followed to disable the lockscreen. Unfortunately, Xposed is a bit much for a "noob" like me. I attempted to install it and got caught in a bootloop and had to do a factory reset. Considering what my dad uses it for, the negatives far outway the positives for me to bother with Xposed ever again
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