Can some one please tell the step how to preform this, " You can enable softbuttons by uncommenting qemu.hw.mainkeys=0 in build.prop. After a reboot softbuttons are enabled.
I am trying to enable my softkeys. Thanks.
Check this out mate, hope your answer will be there
how to edit build.prop
Thanks
thamlim said:
Check this out mate, hope your answer will be there
how to edit build.prop
Click to expand...
Click to collapse
I will do some research, thank you for the help. I just started flashing Roms a month ago and have done very well thus far. I have flashed both SD and internal storage. Again tham you...
thamlim said:
Check this out mate, hope your answer will be there
how to edit build.prop
Click to expand...
Click to collapse
One more final question regarding this """" uncommenting qemu.hw.mainkeys=0 in build.prop. After a reboot softbuttons are enabled."""" Does this mean I have to add Just this >>>qemu.hw.mainkeys=0 in the Build.Prop?? Thnk you again.... Long live HD2
'uncommenting' means there is a good chance the line will already be there,. but 'commented out' (not sure what the comment symbol is for that file, never looked in it) but for example
line 1
// line 2
line 3
line two is 'commented out'. To uncomment it i would remove the //. Its almost certainly not //, it could be a # or something..
line 1
# line 2
line 3
search the file for the line qemu.hw.mainkeys=0 and there will be somethign before it, , if teh line isnt there at all, just add
qemu.hw.mainkeys=0
to the end of the file (on its own new line)
samsamuel said:
'uncommenting' means there is a good chance the line will already be there,. but 'commented out' (not sure what the comment symbol is for that file, never looked in it) but for example
line 1
// line 2
line 3
line two is 'commented out'. To uncomment it i would remove the //. Its almost certainly not //, it could be a # or something..
line 1
# line 2
line 3
search the file for the line qemu.hw.mainkeys=0 and there will be somethign before it, , if teh line isnt there at all, just add
qemu.hw.mainkeys=0
to the end of the file (on its own new line)
Click to expand...
Click to collapse
Thank you!!! I looked over the build did not see the file so I will add it.. I hope it works...
GAlstone said:
Thank you!!! I looked over the build did not see the file so I will add it.. I hope it works...
Click to expand...
Click to collapse
Did it work?
In which line should it be added?
Thanks
GAlstone said:
Can some one please tell the step how to preform this, " You can enable softbuttons by uncommenting qemu.hw.mainkeys=0 in build.prop. After a reboot softbuttons are enabled.
I am trying to enable my softkeys. Thanks.
Click to expand...
Click to collapse
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
alojo said:
Did it work?
In which line should it be added?
Thanks
Click to expand...
Click to collapse
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
"qemu.hw.mainkeys=0" work for me. Using this ROM.
zain0300 said:
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
Click to expand...
Click to collapse
Does this work on latest jb sammy rom?
Just as a heads up, if you have added "qemu.hw.mainkeys=0" and it's not working. Make sure there isn't a "qemu.hw.mainkeys=1" someplace else in your build.prop or it will conflict and cause them not to show up.
For those looking for easy ways to enable/ disable the softkeys (navbar), follow that link :
http://forum.xda-developers.com/showthread.php?t=2651511
enable soft key
zain0300 said:
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
"qemu.hw.mainkeys=0" should be one of the last lines in the build.prop(in the root browser go to system/build.prop), but if you cannot find it in the build.prop open root browser, in the root you'll see a folder "data" in data create a file named local.prop (data/local.prop) write this line qemu.hw.mainkeys=0 in it save and reboot your phone.
Click to expand...
Click to collapse
TO ENABLE SOFT OPEN ROOT BROWSER AND OPEN SYSTEM AND THEN BUILD.PROP IF U DONT FIND THE LINE "qemu.hw.mainkeys=0" WRITE THIS LINE AT LAST AND TO DISABLE JUST PUT "1" IN PLACE OF "0" DONT WRITE " " IN LINE ITS ONLY FOR UNDERSTANDING AND THEN REBOOT UR PHONE
In my advice this line "qemu.hw.mainkeys=0" is already written.
And I also add this "qemu.hw.mainkeys=0" at end of the build.prop but not working please help me ....
Redmi Note 2, Android 5.0.2, MIUI 9.6
Need to enable original soft keys too. I`ve managed to edit build.prop from TWRP terminal and sed command. Keys showed BUT don`t response.
I`ve noticed a new menu option in Settings (can`t be not quite accurate, coz I have a translation enabled) - System and Device -> Advanced -> Buttons and gestures -> Screen buttons -> Change buttons positions. And if I change positions, it changed. But buttons are stil not responding.
Are there any MORE options in build.prop, that blocks it?
Related
How can we Enable the Hotpot Feature on ATT G2 or is there any other apps that could do the trick?! anyone!!!!!!
there have been a few "claims" nothing as of yet, not build.prop not database editing....
There is a ROM in the ATT area with enabled wifi tether.
HelloWorld11 said:
How can we Enable the Hotpot Feature on ATT G2 or is there any other apps that could do the trick?! anyone!!!!!!
Click to expand...
Click to collapse
This has bee solved already..You must follow the instructions to the T the location is going to be different though...
http://forum.xda-developers.com/showthread.php?t=2478228
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
eldedo said:
there have been a few "claims" nothing as of yet, not build.prop not database editing....
Click to expand...
Click to collapse
Im on ATT LG G2 and my hotspot is enabled,,,,
http://forum.xda-developers.com/showthread.php?t=2478228
Tested and working!
1. Download SQLite Editor
2. Open the file - /data/data/com.android.providers.settings/databases/settings.db
3. There's a field named 'tether_entitlement_check_state'. Original value is set to 5. Changed it to 0 and save
4. Reboot the phone
5. Enjoy tethering.
Dinster said:
1. Download SQLite Editor
2. Open the file - /data/data/com.android.providers.settings/databases/settings.db
3. There's a field named 'tether_entitlement_check_state'. Original value is set to 5. Changed it to 0 and save
4. Reboot the phone
5. Enjoy tethering.
Click to expand...
Click to collapse
I cant find the field name 'tether_entitlement_check_state'. is there a way to create it?
With this procedure you will be able to disable the capacitive buttons and enable the real android onscreen buttons, NOT PIE.
This has been tested in a Tab Pro 8.4 with the latest CM build. If you follow the instructions correctly you shouldn't have any issues, however make a backup just in case. If anyone wants to try it with a stock rom please let me know if it works.
Requisites: Root access and a root explorer.
1. With your preferred root explorer open your build prop and add the following line all the way to the end:
qemu.hw.mainkeys=0
Save and exit.
2. Navigate to system/usr/keylayout and open sec_touchkey.kl as text.
You should have two lines. Add a # at the beginning of each line as follows:
#key 158 BACK
#key 254 APP_SWITCH
Save and exit.
3. Exit the file explorer and go to settings, buttons and turn off the buttons light.
4. Reboot and voila!!!
I hope this helps.
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
It works fine in portrait but broken in landscape. Keys dont show up at all. Any fix for this?
burshturs said:
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
Click to expand...
Click to collapse
I have the same problem with stock ROM.
aeron16 said:
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
Click to expand...
Click to collapse
Are you trying it in stock or CM?
Hi am using Stock
Hi guys i tried on CM 11 and i dont find #key 254 APP_SWITCH , i rebooted my TAB and Hardware button still works , and appear Software button too , any clue?
Works like a sharme on cm11. The only thing is that the file isn't named 'sec_touchkey.kl' but 'sec_touchscreen.kl' (newest nightly 9-9-2014)
Thanks, works great for me on cm11, too
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Good stuff. Thank you ! So I guess the way to undo the process I is simply to flash a CM update?
Just flash the ROM again without reset and everything will be as before. Or edit the files as described in the OP and revert the changes.
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Sorry if this sounds like a dumb question but you said to open the build prop and add that line to the bottom and my question is where, exactly? I'm using solid explorer and am in the system root folder but to which file do I add that line? Is it in system>usr>keylayout>Generic.kl like I navigated to to disable the capacitive buttons?
I found how to do that in another post and then enabled Pie, but I'd rather have the normal buttons instead.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
@baldwyn: build.prop is a file in /system.
Does anybody know the key for the home-button? I have already disabled #172 but that's not working.
petty500 said:
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Click to expand...
Click to collapse
You can use this app instead of the build.prop edit. That works just great, The Pro version even allows many customizations incl. behaviour like auto hide or not or custom icons. Important - it works both portrait and landscape,
https://play.google.com/store/apps/details?id=com.mrbimc.udn.lite&hl=de
Working in CM12?
hypophysis said:
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Click to expand...
Click to collapse
Has anyone tried this in CM12? Or perhaps CM12 has a built-in setting that accomplishes the same thing?
Thanks,
Ron
kingofcomedy said:
Click to expand...
Click to collapse
Thank you for this. With this setting are the capacitive buttons disabled? I would prefer that they were.
Sent from my SM-T320 using Tapatalk
1 - Check Root Device!
2 - Download ES File Explorer (Google Play)
3 - Open ES File Explorer and accept permissions Root.
4 - Open Tools and mark Root Explorer.
5 - Come Back Local, and / Device next Open System after etc
6 - Paste file mixer_paths.xml (include link end post) and Replace existing File. (if you do not understand look at the attached images in the post.)
7 - Restart your Device
8 - Finish!
if by chance, your phone is muted after restart, follow These steps.
Open ES File Explorer, browse by location> / Device> System> etc and select mixer_paths.xml on file, go to properties, rw-rw-rw Then permissions and click change and tick all the boxes in Read and Write click ok and restart your device.
to better understand, look at the steps in the last images attached in the post.
For your safety also offers the original file if you can not apply the mod.
(Backup Stock Mixer_Paths.xml) >> https://mega.nz/#!to1EEZjD!JSLqydRhr9voea69grE3kCOwUj-cOCZNdbphm_Xtm_c
Download MOD >> https://mega.nz/#!ppcDhJpT!kdOAb-aoTPOol1PXVNgxbgOxnb0-6InoZ8pHA5_LlcE
works great.... thanks man!!!!
boss, you have A method that works in the 23.a.1.291 compilation?
DanielG_97 said:
boss, you have A method that works in the 23.a.1.291 compilation?
Click to expand...
Click to collapse
this will work in all marshmallow versions, just copy and set permission as (rw,r,r) or (644)
and reboot your device.:good::good:
---------- Post added at 08:25 PM ---------- Previous post was at 08:10 PM ----------
DanielG_97 said:
boss, you have A method that works in the 23.a.1.291 compilation?
Click to expand...
Click to collapse
this will work in all marshmallow versions, just copy and set permission as (rw,r,r) or (644)
and reboot your device.:good::good:
is there any method to increase the loudspeaker volume output ?
Hi after a few days of tinkering with the native hotspot to work, i finally got it working. Im going to try to make it as easy as possible to follow the guide in aiding to get it to work for you.
I'm also going to try to create a automatic script to do it when I get some time.
My device:
Unlocked Pixel XL
Network: Sprint (Should theoretically work for all.)
Requirments:
Hackers Keyboard (From play store)
https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
Termux (From play store)
https://play.google.com/store/apps/details?id=com.termux
Unlocked Bootloader
ElementX Kernel
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/kernel-elementalx-pxl-0-02-t3487072[/URL]
Chainfire's Root method
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156[/URL]
Steps:
Make sure you are rooted and have the ElementX kernel installed
Install Termux [From Playstore]
Install Hackers keyboard [From Playstore]
Open up termux
Type in su
Press Enter
Grant SuperSU access
Type mount -o rw,remount /system_root
Press Enter
Type in
cd /system_root/system/
Press Enter
apt-get install nano
Press Enter
This is a symlink binding to the directory that will allow us to modify build.prop
Nano is an editing application that's intuitive and easy to use.
Type in
settings put global tether_dun_required 0
Press Enter
Then type in
nano build.prop
Scroll all the way down to the end of the line, and add the following
net.tethering.noprovisioning=true
Using the hackers keyboard layout in landscape view press ctrl + x then press Y then Enter
Reboot your device and start the tethering, it should be able to turn on a hotspot with no errors. I may or may not work for all, but it did work for me so hopefully those out there that needed this will be able to benefit as well.
All screenshots
https://drive.google.com/open?id=0B94c0AYYx44RTENkcm0wLU5MbEE
RESERVED
Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.
josephcsible said:
Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.
Click to expand...
Click to collapse
That work's too I forgot about that
But it needs to be
echo net.tethering.noprovisioning=true >> /system_root/system/build.prop
Since current root is systemless and the partition layout won't let you just touch the system directory without the symlink
This does not work on Verizon's network running Elemental X and build NDE63P
Not looking to thread crap, but just wanted to share my experience and get opinions:
I rooted previously using Chainfire's method. Granted root access to ROOT EXPLORER app----purchased several years ago.
Went into the system folder and opened the build.prop file.
Added the last line: net.tethering.noprovisioning=true and saved and rebooted.
This took a total of 2-3 minutes. I know not everyone wants to spend money, but for those that already purchaed ROOT EXPLORER, was my method OK?
Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?
psychatog64 said:
Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?
Click to expand...
Click to collapse
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.
diesteldorf said:
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.
Click to expand...
Click to collapse
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
Click to expand...
Click to collapse
Or is this meant for like Bluetooth tethering and USB tethering
psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
Or is this meant for like Bluetooth tethering and USB tethering
Click to expand...
Click to collapse
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.
diesteldorf said:
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.
Click to expand...
Click to collapse
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life
psychatog64 said:
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life
Click to expand...
Click to collapse
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop
harritaco said:
This does not work on Verizon's network running Elemental X and build NDE63P
Click to expand...
Click to collapse
The bootloader is unlocked and you have the latest chainfire root correct?
diesteldorf said:
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop
Click to expand...
Click to collapse
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop
stuntnmore said:
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop
Click to expand...
Click to collapse
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
Code:
net.tethering.noprovisioning=true
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon
sd_shadow said:
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon
Click to expand...
Click to collapse
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.
stuntnmore said:
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.
Click to expand...
Click to collapse
I'm on Verizon unlimited all I did was edit the build.prop
Sent from my XT1254 using XDA Labs
sd_shadow said:
I'm on Verizon unlimited all I did was edit the build.prop
Click to expand...
Click to collapse
Oh that's great to hear glad it works for you
No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.
335Deezl said:
No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.
Click to expand...
Click to collapse
It's a need for those who wish for it to work all the time via toggle not to use an app every time, it's a lot more efficient.
Hello
I am coming to the g4 plus after having used the samesung s5 for years on MOAR rom and i am looking for how i can get my mobile hotspot back on sprint
I get Unable to connect to data network you may not be subscribed to .....
now i do not have a wifi plan per se but i do have a really old phone as a modem plan i am still paying for (back then it was 10$ a month for unlimited 2008)
so first thing i did was look for where to modify the apn settings for tethering like i had to do before but when the phone activates on sprint the apn menu disapears.
so i look for a custom rom like MOAR but for the g4 plus and i am not seeing any that say they have wifi hacks included
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
i just use airdroid for hotspot
I will take a look at airdroid tomorow if it works great if not ill have to dig into the build.prop was trying to avoid that with a ready made rom
this brings back memories of reg'editing my htc titan lol
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This totally worked on my 1625, tethering was ghosted out. After this it works. Thank you
Sent from my Moto G4 using Tapatalk
robot_head said:
This totally worked on my 1625, tethering was ghosted out. After this it works. Thank you
Sent from my Moto G4 using Tapatalk
Click to expand...
Click to collapse
You used both or only the build.prop edit. I can add it to source in that case. And is this issue only with 1625 variant?
The compliance with the provider setting is well known for Moto phones (at least the ones sold in US). I am using an app from here on XDA called Entitlement Bypass:
https://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
This works perfect. I used the build.prop edit and su command. Completely opened tethering.
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This worked for my XT1644. Tethering and hospot option was grayed out in settings on custom ROMs, until doing this build prop edit. I did not have to run the commands, build prop edit solved my issue. Thank you so much.
When I rooted first time,I faced this problem of hotspot. I then installed elementalx in my device which solved the problem.
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This does work on Motorola G5 plus unlocked from best bye bye using ATnT.
Unrooted XT1644. AT&T provider. Tethering & portable hotspot option is accessible, but when I click on it I encounter "account not set up for tethering...." Could I access the build prop edit via an ADB command or script?
EDIT: Nevermind. My phone's bootloader is locked so no ADB access possible anyway. Looks like I'll need to look into 3rd-party WiFi tethering apps (such as PdaNet+ or NetShare) non-root solutions.