Develop Bugs

[GUIDE] enable trackball/pad wake on the latest MIUI builds again

I think I found an easier way to enable trackball/pad wake again!
1. connect your phone to your pc and open a cmd window
2. execute the following commands:
adb shell
stop
cd /data/data/com.android.providers.settings/databases/
cp settings.db settings.bak
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
start
3. thats it, if you want to disable it again do the same again but instead of
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
use
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',0);"
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.

Woukd this only work on miui?
There are quite a few people waiting for this feature on xboarders stock gingerbread rom.
Sent from my Nokia 3210 using XDA Premium App

Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App

xile6 said:
Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I just tried this on my Droid Incredible, and it does work! Thanks!

Worked on my N1, Thankyou

Just wanted to say that I tried this again with the latest MIUI build...and again it works! Thanks!

Sweet worked for my HTC Incredible running MIUI 1.6.24 with Incredikernel 06192011

without adb
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)

slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
I guess not since android has to be stoped to make this change. (stop command is to shut down android)
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it. The settings app checked the device name and if it wasn't passion (N1) or bravo (Desire) the trackball wake option didn't show up.
So Desire Z (vision) lost trackpad wake. Thats why I was looking for a way to enable it again. But since a few releases this isn't needed anyways.
Sent from my HTC Desire Z using Tapatalk

g4rb4g3 said:
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it.
Click to expand...
Click to collapse
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.

slim_thumb said:
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.
Click to expand...
Click to collapse
Goto Settings - System - Button Settings - Trackball wake
I can't belive that this doesn't exist on the Nexus One.
Sent from my HTC Desire Z using Tapatalk

Found it, my bad!

slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
Works with root explorer... Just copy database to sdcard then edit while connected to pc.. Copy back, change permissions, reboot and your set..
You can also just use an sqlite editor app..

Any chance someone could post step by step instructions on how to do this with sqlite editor on the phone?
EDIT:
Scratch that. Figured it out.

Thanks a million! This saved the day. Cant believe its not integrated with miui. Nexus One MIUI

Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.

magdiel1975 said:
Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
You need to navigate to your sdk / adb folder.
Sent from my Sensation using xda premium

trackpad wake works on latest miui.. I am currently running it? :S

I wonder why people don't use the trackball/pad wake option in the settings menu too....
This was an issue half a year ago but the MIUI team fixed it a few weeks later and since then it works without this.

works for me
g4rb4g3 said:
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.
Click to expand...
Click to collapse
This method worked for me on my HTC Droid Incredible running MIUI 2.11.9. I actually used File Explorer in Android:
1. copied settings.db
2. uploaded it to my PC
3. used SQLite to edit it
4. copied it back to phone
5. backed up settings.db
6. pasted the new file in
Restarted phone and trackball wakes it up now.
Thanks!

[Q] How do I get a £ sign with CM7 on a UK DZ?

Hi there,
Recently converted to CM7 after years of Sense ROMs and I'm loving it. But I have one question, how do I make FN-z on the physical keyboard produce a £ sign?
I've got the keyboard language set to English (United Kingdom) but that doesn't seem to make any difference.
Regards,
Richard

Change the characterlayout in /system/usr/keychars
In all *.kcm files add these lines to the Z key:
Code:
alt: '\u00A3'
shift+alt:'\u00A3'
To make it look like this:
Code:
key Z {
label:'Z'
base:'z'
shift, capslock:'Z'
alt: '\u00A3'
shift+alt:'\u00A3'
}
Do so in all files, to make sure it's loaded whatever keyboard file you're using.

Ah, I notice this is the case in MIUI roms as well.
Would this work there also? I see the kcm files are bin files, how exactly are we editing them, just open as text file I assume?

It should work on any custom rom, unless the keymapping is done diffrent then usally. Just try it, and if it doesn't work or your phone won't start anymore (enters a bootloop) , just reflash your custom rom, without wiping. Then only homescreen settings and system settings will get lost. Personal and data settings will not be touched.

Just to confirm though, are you editing it as a txt file or what? I have no knowledge of editing bin files which the kcm files seem to be.
Eg: vision-keypad-ell.kcm.bin

As textfile yes, but they should be just plain *.kcm files, not *.bin as I believe, let me check that, to be sure.
--Edit:
They are just *.kcm, not *.bin, but I'm not sure how that's done in other Roms..
If there are only *.bin files, then I don't know how to edit those.. I know that *.kcm can be edited as plain text file.

Cool, I'll look into it.
I notice you put '*.kcm'. My memory is failing me but doesn't this mean hidden files? In which case I didn't look for them.
EDIT: Nah just looked, they are all BIN files. Looks like MIUI does things differently.
Oh well.

The star doesn't mean they're hidden, it is a joker sign. Just means all filenames that end with .kcm (wich is the extention). The .bin files are packed files, binary files. But I can't remember how to edit those as plain text... Try to do it with something like hexeditor on the pc.

lineaira said:
Change the characterlayout in /system/usr/keychars
In all *.kcm files add these lines to the Z key:
Code:
alt: '\u00A3'
shift+alt:'\u00A3'
To make it look like this:
Code:
key Z {
label:'Z'
base:'z'
shift, capslock:'Z'
alt: '\u00A3'
shift+alt:'\u00A3'
}
Do so in all files, to make sure it's loaded whatever keyboard file you're using.
Click to expand...
Click to collapse
All the files that I have in the folder you specified are *.kcm.bin. I guess I need to find the .kcm source files some where and compile them?
Regards,
Richard

You can pull them from your phone with adb. Then edit them with a program like hexeditor.
I can't explain how, as I do not have any *.bin files on my phone or other rom.
If I can find one somewhere in a download or something (you are on CM7 if I'm right) I'll post instructions tomorrow about how to do it. If you'd like me to, that is.

lineaira said:
You can pull them from your phone with adb. Then edit them with a program like hexeditor.
I can't explain how, as I do not have any *.bin files on my phone or other rom.
If I can find one somewhere in a download or something (you are on CM7 if I'm right) I'll post instructions tomorrow about how to do it. If you'd like me to, that is.
Click to expand...
Click to collapse
If you could I would be interested

HOW TO: remap the £ back to FN+Z
Okay here we go.
Before we begin, I suppose that you all know how to set up an adb session with your phone..
And you need this program to be installed on your PC:
Free Hex Editor Neo
You should make a backup of your current working ROM with your favorite recovery, so if something goes wrong, you can just reflash the backup, instead of loosing all your data and settings.
Now start a cmd prompt on your pc (Windowskey+R, type "cmd" hit enter)
browse to your platform-tools directory (cd path-to-platformtools)
Make sure your phone is connected:
Code:
adb devices
And execute these lines:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
You can now read and write to the /system folder on your phone.
Next you need to pull the *.kcm.bin file you'd like to edit. (For the OP this is most likely the "vision-keypad.kcm.bin" or the "vision-keypad-wwe.kcm.bin", but if they aren't the ones used.. then try and edit the "qwerty.kcm.bin" or "generic.kcm.bin" files)
This is done by entering the following:
Code:
adb pull /system/usr/keychars/vision-keypad-wwe.kcm.bin /tmp/vision-keypad-wwe.kcm.bin
Or one of the many other files if this one isn't working.
Minimize the cmd screen for now and browse on your computer to the platform-tools folder (or the folder where you executed the adb from) there should be an new folder called "tmp", in that folder you'll find the file you just pulled from your phone.
Hit it with a right mouse-click and click "Edit with HDD Hex Editor Neo". (If that option is not available, start the Hex Editor and open the file from within the editor)
The first row and columns are blue, except for the first one on the far left-top side, this one is white.
Click it and type: "0000027c" and hit enter.
Now there are some hexadecimals selected in green. On the far right side of that row should be something like this: "6...Z.9.z.Z"
(If that isn't the case, find the line that does look like that and edit that line)
In the green field you've got, change the value to: "a3" (just type)
The cursor will automatically go to the next value, which is "00" leave that.
Press the arrow-key to the right once and edit that value to "a3" as well.
The field on the right side should now display something like: "6...Z.9.z.Z.£.£."
That's it, save the file and push it back to your phone by entering the following in the cmd window you minimized:
Code:
adb push /tmp/vision-keypad-wwe.kcm.bin /system/usr/keychars/vision-keypad-wwe.kcm.bin
Then restart the phone and it should be working!
----
I used the file in the .zip attached as my example file, to see how to do it.

Where do you get the list of codes ? Need the Euro Symbol code ? __=€
Thanks
Edit google is my friend,tried 80 which shows in my file but just get a blank keypress?

bombadier said:
Where do you get the list of codes ? Need the Euro Symbol code ? __=€
Thanks
Edit google is my friend,tried 80 which shows in my file but just get a blank keypress?
Click to expand...
Click to collapse
The Euro € sign is set in the X key.
That line is: "4...X.x.X."
If you want it in the Z key, type "0000027c" in the left top box and hit enter, type "ac20ac20" That'll give you the euro sign. Then the field on the right looks like this: "6...Z.z.Z.- - "
If you want it in the X key, type "0000025c" in the left top box and hit enter, type "ac20ac20" That'll give you the euro sign. (string on the right looks like: "4...X.x.X.- - ")

Thanks for that!
It'll be fun trying this on Linux.
I'll let you know how I get on when I find the time.

Myrmidon83 said:
Thanks for that!
It'll be fun trying this on Linux.
I'll let you know how I get on when I find the time.
Click to expand...
Click to collapse
For linux you can do the same as you need to do for windows. The only thing is that you have to find software which can edit binary files. A nice GUI based editor is ghex.
it's available in the universe repository.
Code:
$ sudo apt-get install ghex

Lineaira,
Thanks for this info. It worked fine! I now have a GBP sign on Fn-Z.
Regards,
Richard

Easier way. Download the attached file, unzip it and place the contained file on the root of your sdcard, then type in the following commands using Terminal Emulator:
su
mount -o rw,remount /system
busybox cp /sdcard/vision-keypad-wwe.kcm.bin /system/usr/keychars
reboot
Found this over at the Cyanogenmod forums ages ago

setspeed said:
Easier way. Download the attached file, unzip it and place the contained file on the root of your sdcard, then type in the following commands using Terminal Emulator:
su
mount -o rw,remount /system
busybox cp /sdcard/vision-keypad-wwe.kcm.bin /system/usr/keychars
reboot
Found this over at the Cyanogenmod forums ages ago
Click to expand...
Click to collapse
It is easier, but not as much fun and satisfying as doing it yourself, I'd say;p

lineaira said:
It is easier, but not as much fun and satisfying as doing it yourself, I'd say;p
Click to expand...
Click to collapse
Exactly,I wanted to learn how to do it myself and now that I know I would say it is just as easy to pull the file from the phone make my edits push it back and job done don't even have to reboot,thanks again for the guidance Lineaira

[GUIDE] Unlock LS980 ZVD (KK 4.4.2) [UPDATED 8/10/14]

Ok I successfully unlocked ZVD (KitKat 4.4.2) and thought I should share my steps in case anyone else was having the same issues as me which was mostly the systemui and home processes crashing on a loop.
First insert the SIM card you would like to use in the LS980. Then download and flash the stock firmware LS980ZVC_12.zip with the LG Tool -> http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Download the ZVD update - > http://www.mediafire.com/download/s5dqwo1cbe68ckb/LS980ZVC_12-LS980ZVD_19_update.zip (Do not flash this OTA update from a rooted rom or custom recovery!)
After flashing ZVC, set the phone to charge only and enable USB debugging by becoming a developer. Go to About Phone->Software Information and keep clicking "Build number" until it says you are a developer. Then go back to the main settings and you will now see "Developer options" and can enable USB debugging in there.
After enabling USB debugging choose charge only and when the RSA Key fingerprint window pops up make sure you check "Always allow from this computer" and then click OK.
Next using the ADB tools, reboot into recovery mode to apply the ZVD update.
Code:
adb reboot recovery
Select "apply update from ADB" with the volume buttons then press the power button. Wait 5 seconds then enter the following command.
Code:
adb sideload path_to_file/LS980ZVC_12-LS980ZVD_19_update.zip
After the update finishes select "reboot system now".
Next turn on airplane mode and root the phone using IO Root -> http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Next install SuperSU and BusyBox. Make sure you open SuperSu to update the SU binary and open BusyBox and install the busybox files.
*OPTIONAL INSTALL TWRP*
Next use ADB to install AutoRec -> http://forum.xda-developers.com/showthread.php?t=2715496.
Code:
adb install path_to_file\LS980_AutoRec.apk
Open AutoRec and flash the new patched kernel and recovery and then reboot. If you get white lines after rebooting, read the warning the OP has posted for the fix. I suggest here you take the time to make a backup and copy the EFS to your computer just in case.
*knock code feature will no longer work
*flash this kernel to enable knock code again and much more - > http://forum.xda-developers.com/showthread.php?t=2725023
*OPTIONAL END*
Now using ADB again, enter the following commands.
Code:
adb pull /system/build.prop
adb shell
su
After entering "su" check your phone to grant SuperUser permission to ADB. Aftering granting su to ADB, exit adb shell.
Code:
exit
exit
Next using Total Commander and the files from here -> http://forum.xda-developers.com/showthread.php?t=2655133 copy all the contents of the "carrier" folder to your phones "/carrier/" directory and choose "overwrite all". I like to delete the "legal.db" first this way I know the copy was successful when I see the new file listed. Do not delete any other files before copying the files over since we want to keep the file and folder permissions and owners of the originals. If Total Commander fails to copy the files over to the phone then you can use a root explorer app to do so.
Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me.
Change the following lines
Code:
ro.carrier=unknown
ro.build.target_operator=SPR
persist.service.crash.enable=0
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
to
Code:
ro.carrier=spr
ro.build.target_operator=spr
persist.service.crash.enable=1
ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0
*ro.carrier and ro.build.target_operator can bet set to "TMO", "ATT", or "spr".
*"TMO" and "ATT" do not correctly display the signal strength in the status bar.
Save the build.prop and use ADB to push it to the sdcard.
Code:
adb push build.prop /sdcard/
Now here is where we have to manually mount the system partition as RW and copy the build.prop over since all the root explorer apps seem to also cause the crashing issue.
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/
mount -o remount,ro /system
reboot
After the phone reboots it should be unlocked. Verify with Radio Switcher that your preferred network type is "WCDMA preferred", if not then change it to "WCDMA preferred". Now add your APN using Tweakker APN INTERNET MMS. If your APN doesn't stick, delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot then add your APN again.
*To remove Bloatware add ".bak" to the following system applications names located in /system/app/ and /system/priv-app/ folders.
Activation.apk
OmaDmclient.apk
SPR_Skyfire_Observer.apk
SPR_Skyfire_Toolbar.apk
SprintExtensionProvider.apk
SprintID.apk
SprintTouch.apk
Vtt-Sprint.apk
xtra_t_app.apk
Zone-Sprint.apk
WIFIOffloader.apk
Click to expand...
Click to collapse
*To fix the issue of the com.android.phone process crashing when you don't dial a 1 in front of the number edit the /data/data/com.android.providers.settings/databases/settings.db file with a SQLlite editor and change in the "system" table "assist_dial" and "assist_dial_init_db_check" to "0". If you don't see those 2 rows then you can add them instead.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db
sqlite3 settings.db
UPDATE system SET value='0' WHERE name='assist_dial';
UPDATE system SET value='0' WHERE name='assist_dial_init_db_check';
.exit
adb push settings.db /sdcard/
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system:system /data/data/com.android.providers.settings/databases/settings.db
reboot
*To disable OTA updates and notifications rename the following files
/etc/security/otacerts.zip
/system/app/LGFOTA.apk
Click to expand...
Click to collapse
to
/etc/security/otacerts.zip.bak
/system/app/LGFOTA.apk.bak
Click to expand...
Click to collapse
*To replace the Sprint boot/shutdown animations and sounds with the LG default ones download these files -> https://www.mediafire.com/folder/cmb6jn7z7osmf/LG_G2_Boot_Animation
copy and overwrite the following files to /system/media/
bootanimation_sprint.zip
shutdownanimation_sprint.zip
Click to expand...
Click to collapse
copy and overwrite the following files to /system/media/audio/ui/
PowerOff_Sprint.ogg
PowerOn_Sprint.ogg
Click to expand...
Click to collapse
*LG G3 Theme for G2 -> https://play.google.com/store/apps/details?id=com.lge.launcher2.theme.rocketg3&hl=en
Thanks to all those people who contributed to this. :victory:

Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....

MakisPgr said:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
Click to expand...
Click to collapse
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app

This method worked on my ATT sim card I dont need to dial a 1 in front of #. but didnt work on my Lycamobile simcard and pageplus. still need to dial 1 infront of nuber.
thanks.
来自我的 LG-LS980 上的 Tapatalk

Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app

jsergio123 said:
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you are right about 1 bar signal, didn't notice, and i fix my mistake settings on APN and mms now works perfectly ... Thank you very much

jsergio123 said:
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I dont know where is it.

ahqiu said:
sorry, I dont know where is it.
Click to expand...
Click to collapse
adb logcat > logcat.txt
Sent from my LG-LS980 using XDA Premium 4 mobile app

Updated the OP for latest ZVD update from Sprint.
Added SQLite instructions.
Also confirmed working myself.

Updated the OP to include the files and instructions to replace the sprint boot/shutdown animations and sounds

Do you know if I would be able to install a custom rom after this? Also, I had the issue before with cloudys rom that would cause app force closing and restarts, should I expect the same this way?
Thanks a bunch

If you want to use a custom asop rom don't follow my guide instead just follow this guide after flashing your rom of choice.
http://forum.xda-developers.com/showthread.php?t=2827043

@jergio123
Do you think this would work to unlock additional bands on the Sprint LGG2 LS980 for T-Mobile USA?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269

I guess the only way to find out would be to attempt it. I only quickly looked through the thread but good find.

Is there suppose to be a custom folder inside the carrier folder I copied over to root directory? After rebooting my device I've notice this custom folder that's not inside the original carrier folder I extracted ?

There should be a "cust" folder, I'm not sure if that is the folder you're referring to.

Will cloudys g3 ROM work with this unlock method?

I'm pretty sure cloudys rom is already unlocked and only requires you to change the radio with radio switcher and add your APN

Don't work
Hello, i can't unlock with this method. In the end, when i turn on the phone unlocked, the phone give me an error and always appear "com.android.phone".
I don't understand this part:
"Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me."
I need edit "built.prop" or not? How?
I'm using the phone in Portugal (gsm carrier), i need to do this part?
Sorry but i really confused.
Thank you

Follow the guide step by step, I don't know how much clearer I can make it.
If you're getting process crashes then you must either restore the system partition from backup or start fresh by re-flashing with the LG tool.

Is it possible to unlock tethering on the Oreo version of the Pixel XL?

My carrier is ATT and I am rooted. If this is possible than please let me know.
It is possible I will be making a guide on how to do it.

add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.

martinez5241 said:
add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.
Click to expand...
Click to collapse
Thanks. I will try this once I root Oreo. I am glad to finally find something working with Sprint.

martinez5241 said:
add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.
Click to expand...
Click to collapse
I am on AT&T and you only need to add the build prop line and reboot. No need for the terminal commands. FYI

is there a new workaround for us Big Red users that are now hitting their 15gb hotspot limit and are now being throttled to turtle speeds? Mine worked fine last month but somehow not this month?

net.tethering.noprovisioning=true now counts towards tethering? VZW

I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?

I am still on Grand fathered unlimited and just did the build prop today and it worked for hot spot, I am on the Sept update. Curious to what others say. I am trying to decide to go to the new plan or not, lately I only use about 20 gb and that is a heavy month
Sent from my Pixel XL using Tapatalk

coolhandz said:
I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?
Click to expand...
Click to collapse
Tethering always counted for data usage. What you're referring to just skipped the check if it was on your cell plan and let you tether without it. It should have only applied to old, grandfathered unlimited lines for Verizon.
Sent from my Pixel XL using Tapatalk

I know it counted against my data, but it didn't previously count towards my tethering data limit. Does that make sense? I have unlimited data, but 15gb high speed tethering limit.

Well I discovered that if I have wifi router as a repeater, repeating the hotspot. Then connect to it via Ethernet with my raspberry pi Kodi box. That the video streamed is not counted towards my tethered data. No clue why.

Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.

besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.

mjrBud said:
Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.
Click to expand...
Click to collapse
I am experiencing the same thing now. Has a workaround been discovered for this? Exact same scenario as you.

Others have said vpn tether and a vpn connection. It basically routes all hotspot traffic through vpn so they cannot inspect packets. I guess this may not affect TTL tho.

try disable ipv6

You are going to have to change the ttl somehow. I guess they are getting serious and sniffing packets now..

Also might give this a try with Magisk
https://forum.xda-developers.com/showpost.php?p=77371813&postcount=4
Edit: Never mind....does not work with Magisk 17.1

Born<ICs said:
besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.
Click to expand...
Click to collapse
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.

jeffshead said:
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.
Click to expand...
Click to collapse
I made those changes and while I didn't get a bootloop it also didn't remove the 600k tethering cap.
---------- Post added at 10:28 PM ---------- Previous post was at 10:24 PM ----------
firewallgt said:
try disable ipv6
Click to expand...
Click to collapse
How can you do that without the ability to edit or create a custom apn (verizon pixel xl)

After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?

jeffshead said:
After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?
Click to expand...
Click to collapse
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.

himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
I am on pixel xl and no build.prop in system_root here either. Always modded build.prop in system for like last 6 phones or so, but like i said earlier none of the changes worked for me to hide tether from verizon

himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
To clarify, the other 'build.prop' file is not in 'system_root'. It is in '/system_root/system'. I have two 'system' directories. The other 'system' directory is a sub-directory of the 'system_root' directory. Here is a post from another member that has the same 'system_root/system' directory: https://forum.xda-developers.com/showpost.php?p=73968882&postcount=172.
Below is what I get for the 'build.prop' file when I run the "ls -al" command on the '/system_root/system' directory and I get the same exact result when I run the same command on the other 'system' directory:
...
-rw------- 1 root root 1862 2009-01-01 03:00 build.prop
...
I decided to take a chance so I performed the ADB commands that I linked to in this post and the "net.tethering.noprovisioning=true" line was added to both 'build.prop' files. Not sure how the two files are linked???
Still reports usage so these edits do noting. I did notice that there is a system app named "Tethering Entitlement 2.3". I'm guessing that is what keeps track of tethering data usage and reporting.

So no way around the vzw throttling looks like guys? Was y'all using VPN and VPN tether???

what about us Tmo users? I want unlimited tether too ;-]