Related
Guys I have a question...
On stock lollipop there is a DATABASE folder located at com.android.providers.settings ,inside the database folder a file called SETTINGS.DB .
I usually edit this file to avoid carrier detecting that I'm tethering and as always worked.
Now I updated to marshmallow on my N5 but the setting.db isn't there anymore.
Ideas?
Thanx
Sent from my Nexus 5 using Tapatalk
I have the same issue.
Basically Tether no longer works on my Nexus 5.
-Hotspot turns on and Data is working on Nexus 5, but connected (Tethered Devices) cannot get internet access.....DNS_Probe failures
I rolled back to lollipop for the moment while finding a solution
Sent from my Nexus 5 using Tapatalk
This worked for me on Sprint device
I used adb to change the settings.db
1. Typed "adb shell"
2. Then "settings put global tether_dun_required 0"
3. I also added in the build.prop file "net.tethering.noprovisioning=true"
reboot and enjoy
Hope this helped.
chrisduclo said:
This worked for me on Sprint device
I used adb to change the settings.db
1. Typed "adb shell"
2. Then "settings put global tether_dun_required 0"
3. I also added in the build.prop file "net.tethering.noprovisioning=true"
reboot and enjoy
Hope this helped.
Click to expand...
Click to collapse
Thanks I'll give that a try now.
Successful, Hotspot working here now.
I already had the build.prop entry (force of habitat) :
net.tethering.noprovisioning=true
For the setting global entry:
I used Terminal Emulator
su (for super user)
Then typed "settings put global tether_dun_required 0"
After making entry I rebooted device and tested Hotspot.
Hotspot working.
My Nexus 5 with rooted (Elementalx) Android 6.0 works with tethering by just turning it on. I am on AT&T.
mariano3113 said:
Thanks I'll give that a try now.
Successful, Hotspot working here now.
I already had the build.prop entry (force of habitat) :
net.tethering.noprovisioning=true
For the setting global entry:
I used Terminal Emulator
su (for super user)
Then typed "settings put global tether_dun_required 0"
After making entry I rebooted device and tested Hotspot.
Hotspot working.
Click to expand...
Click to collapse
Can u make a step by step tutorial for the less knowledge people like me please lol
Sent from my P01MA using Tapatalk
He just told you
Sent from my Nexus 5 using Tapatalk
guinnes.s said:
Can u make a step by step tutorial for the less knowledge people like me please lol
Sent from my P01MA using Tapatalk
Click to expand...
Click to collapse
Step 1) Use a Nexus 5 or 6 on Marshmallow with Root* (There are plenty of threads and ROMs detailing Root access on those Nexus devices with Busybox and Super Su/SuperUser working)
Step 2) Download a File Explorer that offers root privilege like ES File Explorer (Root Explorer toggled On and granted SU access)
Step 3) Navigate in file explorer to System ->Build.prop
Step 4) Open build.prop (Es File Explorer has ES Note Editor included)
Step 5) choose to edit, so that you can add the line entry: net.tethering.noprovisioning=true
Step 6) Save build.prop and exit
Step 7) Download Terminal Emulator or some other Terminal App
Step 8) Open Terminal app and grant SU either by prompt or by typing "su" as a command *App and SU confirmation process may vary*
Step 9) After SU access is acquired in Terminal Emulator/app type: settings put global tethering_dun_required 0
Step 10)Exit Terminal app
Step 11) Reboot device
Step 12) Test Native Hotspot/tether
If not working and on Sprint/CDMA carrier double check/repeat steps 1-12
(CDMA carriers don't allow APN edit on Nexus 5...APN list does not show)
If using GSM carrier (At&t, T-Mobile), if hotspot is still not working;
-Go to settings->Wireless & Networks choose More
-Select Cellurlar Networks
-Select Access Point Names (APN)
-Go to APN Type and add: ,dun
(Comma dun with no spaces*)
Save & Exit
Reboot device
Test Hotspot/tethering, if not working double check all entry changes...
Can you still do this on a phone that is not rooted? This worked on lollipop but doesn't on marshmallow:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
testinguser said:
Can you still do this on a phone that is not rooted? This worked on lollipop but doesn't on marshmallow:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Click to expand...
Click to collapse
what's the error that you're getting when you run that command.
[/COLOR]
mariano3113 said:
Step 1) Use a Nexus 5 or 6 on Marshmallow with Root* (There are plenty of threads and ROMs detailing Root access on those Nexus devices with Busybox and Super Su/SuperUser working)
Step 2) Download a File Explorer that offers root privilege like ES File Explorer (Root Explorer toggled On and granted SU access)
Step 3) Navigate in file explorer to System ->Build.prop
Step 4) Open build.prop (Es File Explorer has ES Note Editor included)
Step 5) choose to edit, so that you can add the line entry: net.tethering.noprovisioning=true
Step 6) Save build.prop and exit
Step 7) Download Terminal Emulator or some other Terminal App
Step 8) Open Terminal app and grant SU either by prompt or by typing "su" as a command *App and SU confirmation process may vary*
Step 9) After SU access is acquired in Terminal Emulator/app type: settings put global tethering_dun_required 0
Step 10)Exit Terminal app
Step 11) Reboot device
Step 12) Test Native Hotspot/tether
If not working and on Sprint/CDMA carrier double check/repeat steps 1-12
(CDMA carriers don't allow APN edit on Nexus 5...APN list does not show)
If using GSM carrier (At&t, T-Mobile), if hotspot is still not working;
-Go to settings->Wireless & Networks choose More
-Select Cellurlar Networks
-Select Access Point Names (APN)
-Go to APN Type and add: ,dun
(Comma dun with no spaces*)
Save & Exit
Reboot device
Test Hotspot/tethering, if not working double check all entry changes...
Click to expand...
Click to collapse
I've tried multiple Terminal Emulators on my device and receive an error message after inserting the "settings put global tethering_dun_required 0" and then hitting "ENTER" key on Google Keyboard. I think this process must be completed on a computer using adb command. Can you confirm that the Terminal Emulator app was successful in making this change? I have tried multiple emulators... Thank you!
NEXUS 6, Rooted, Stock 6.0 MRA58K
HUSKER77 said:
[/COLOR]
I've tried multiple Terminal Emulators on my device and receive an error message after inserting the "settings put global tethering_dun_required 0" and then hitting "ENTER" key on Google Keyboard. I think this process must be completed on a computer using adb command. Can you confirm that the Terminal Emulator app was successful in making this change? I have tried multiple emulators... Thank you!
NEXUS 6, Rooted, Stock 6.0 MRA58K
Click to expand...
Click to collapse
Adding some images as confirmation: Current device used for Screen shots was Nexus 5 (hammerhead)
Terminal App screenshot
Su entry screenshot
SU access prompt screenshot
Root Terminal screenshot
Settings Dun entry screenshot
Successful entry w/no error message screenshot
Hope that helps. I'll try tonight on Nexus 6 (shamu) as a follow up.
testinguser said:
Can you still do this on a phone that is not rooted? This worked on lollipop but doesn't on marshmallow:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Click to expand...
Click to collapse
Yes, you should be able to force set value via adb shell without root.
-Or it used to- with Nexus Devices I have an inclanation to Root
HUSKER77 said:
[/COLOR]
I've tried multiple Terminal Emulators on my device and receive an error message after inserting the "settings put global tethering_dun_required 0" and then hitting "ENTER" key on Google Keyboard. I think this process must be completed on a computer using adb command. Can you confirm that the Terminal Emulator app was successful in making this change? I have tried multiple emulators... Thank you!
NEXUS 6, Rooted, Stock 6.0 MRA58K
Click to expand...
Click to collapse
Follow up with success on Marshmallow with Nexus 6 (shamu) (No errors)
testinguser said:
Can you still do this on a phone that is not rooted? This worked on lollipop but doesn't on marshmallow:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Click to expand...
Click to collapse
I just tried this command on 6.0 MRA58K and it appeared to work, I got no errors. I also modified build.prop as above. I will try tomorrow to see if the Tethering data increments within my T-Mobile Account app.
mariano3113 said:
Yes, you should be able to force set value via adb shell without root.
-Or it used to- with Nexus Devices I have an inclanation to Root
Click to expand...
Click to collapse
So you're saying we could get tether on Nexus Marshmallow *without* root?
...or that we can force set that value with ADB shell without root, but *also* need to edit build.prop?
Thanks!
On my N5 on MetroPCS, I was able to enable tethering by just running the following:
Code:
adb shell
settings put global tether_dun_required 0
I ran it has su originally, but I can run it without and don't get any errors. I didn't change the build.prop I did have to change the APN type to IP4 (it would work at first on IP6 but when I switched towers or something it would stop). So in theory in my case root shouldn't be needed, my device is now unrooted again and all is working fine.
Tethering now works, I think this is a little different than some of the other carriers since MetroPCS allows tethering, but just not with a BYOD from what I have heard.
Guys, anyone know the location of settings.db on MM?
On my Sprint Nexus 5 running 6.0.1
I ran the
adb shell
settings put global tether_dun_required 0
Didn't edit build.prop since I have no idea how to.
I'm tethering. No root. Bone stock. No warnings or anything yet.
kschossow said:
On my Sprint Nexus 5 running 6.0.1
I ran the
adb shell
settings put global tether_dun_required 0
Didn't edit build.prop since I have no idea how to.
I'm tethering. No root. Bone stock. No warnings or anything yet.
Click to expand...
Click to collapse
OK. Works perfect on my Nexus 5.
On my Nexus 6p I do the same commands but I get this message when I try to turn on hotspot. "Your device does not support this service. Please contact your service provider."
I thought it might work on the 6p seeing as it works on the Nexus 5. Both are on marshmallow. Any ideas?
Wouldn't it be cool to be able to automate the swicthing data between SIM 1 and SIM 2 using Tasker given the location of the device? Let's figure out how to do it together. Do we need root? ADB command comes to mind...
@MishaalRahman any ideas?
What do you mean by "switching data?" Sorry, I usually don't use two SIMs so I'm not sure what you mean.
MishaalRahman said:
What do you mean by "switching data?" Sorry, I usually don't use two SIMs so I'm not sure what you mean.
Click to expand...
Click to collapse
The dual sim version mha-l29 has an option to set the default 4g slot from within the settings menu
I have found already a system variable that can be changed using secure settings plugin for tasker, and running the adb command adb shell settings list system I can see that the variable switch_dual_card_slots does change from 0 to 1 when doing it from the ui, but when done from a put command nothing happens. Any ideas?
dmorales023 said:
The dual sim version mha-l29 has an option to set the default 4g slot from within the settings menu
I have found already a system variable that can be changed using secure settings plugin for tasker, and running the adb command adb shell settings list system I can see that the variable switch_dual_card_slots does change from 0 to 1 when doing it from the ui, but when done from a put command nothing happens. Any ideas?
Click to expand...
Click to collapse
The screenshot shows you doing the command from the Secure Settings plug-in, not from shell. Have you tried it from shell?
MishaalRahman said:
The screenshot shows you doing the command from the Secure Settings plug-in, not from shell. Have you tried it from shell?
Click to expand...
Click to collapse
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
dmorales023 said:
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
Click to expand...
Click to collapse
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
dmorales023 said:
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
Click to expand...
Click to collapse
Yeah, that seems like it would do it.
dmorales023 said:
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
Click to expand...
Click to collapse
Is it working? I am trying to do same thing on my phone. No luck till now
midhunmanohar said:
Is it working? I am trying to do same thing on my phone. No luck till now
Click to expand...
Click to collapse
No luck on my side either. Did you find a solution? This seems so trivial...
dmorales023 said:
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
Click to expand...
Click to collapse
I am using the shell command successfully on my Honor 6X.
First I set switch_dual_card_slots to 0 or 1 , and to commit I simply kill the phone process, which will automatically restart instantly.
It is not the most elegant solution, but works flawlessly for me.
The two commands I run (with root priveleges)
1: settings put system switch_dual_card_slots 1
2: pkill phone
dual SIM data switch
RealParity said:
The two commands I run (with root priveleges)
1: settings put system switch_dual_card_slots 1
2: pkill phone
Click to expand...
Click to collapse
i tried the above.
1 executes something, no msg.
2 gives an error message: pkill: TERM->24469: Operation not permitted
the data SIM does not change. but i guess it can't, as the 2nd command fails. what other things i might try?
and yes, i'm a noob on terminal commands - please walk me through how to automate this.
Bump after disabling one sim on location has I get no signal at work
zdoe said:
i tried the above.
1 executes something, no msg.
2 gives an error message: pkill: TERM->24469: Operation not permitted
the data SIM does not change. but i guess it can't, as the 2nd command fails. what other things i might try?
and yes, i'm a noob on terminal commands - please walk me through how to automate this.
Click to expand...
Click to collapse
Not sure if you got this figured out but you need to be rooted. Then in adb shell/terminal you must type "su" first then do the pkill
Anybody tried with a Xiaomi phone?
There's an app 4 this (dual sim switch widget) but it doesn't work on Xiaomi phones
Hi, I have a xiaomi mi 9t, I wish I could change the default sim for data, how much I receive or send a call.
What command can I give tasker for modifying the data sim?
we all know how to enable hotspot on nougat using adb shell with codes
adb shell
settings put global tether_dun_required 0
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
since its not working on oreo and its causes ( you are not subscribed to hotspot)
is there anyone knows what adb code to set the hotspot back to default
Thank you
Update (Found it)
To revert:
Code:
settings put global tether_dun_required 1
settings put global tether_dun_apn null
Credit to paul2112
https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
ahmadxbox360 said:
we all know how to enable hotspot on nougat using adb shell with codes
adb shell
settings put global tether_dun_required 0
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
since its not working on oreo and its causes ( you are not subscribed to hotspot)
is there anyone knows what adb code to set the hotspot back to default
Thank you
Click to expand...
Click to collapse
Th only way is a factory reset. I tried everything its the only thing that works
Im working on the new ADB method but not quite there yet. i posted a temporary mod until its working on oreo
Dear XDA community,
this my first own thread and guide so please be forbear with me
And i hope i choose the right section
As the topic in the thread says it handles about the Captive Portal Checkin done by Android.
So first some general info about this.
1. What is the Captive Portal Checkin?
Every time your android phone connects to the internet via mobile connection or wlan it sends a request to the following url:
http://connectivitycheck.gstatic.com (Google URL).
After that your gets device gets http 204 answer from the mentioned url and at that point the x-symbol at your network icon in the status bar disappears.
The reason for that behavior is that Android wants to be sure that your connection has internet access.
If you block that request via AfWall for example the dns fails in some cases and you can't go into the Internet.
Silly.
2. Why is this problematic?
That's a good question because this answer from Google doesn't much hold data. But every time when this connection is done Google get the following information:
- IP-adress
- Time of the internet access
- the Browser which you use
In my case i use custom roms and no Gapps to avoid Google as much as i can. So i don't want that "ping" to Google.
That's the reason why i searched for possibilitys to get rid of this ping. And thanks to a german security and privacy specalist i found a possibilty to avoid the ping to Google and have working Internet, too.
3. What did that guy do?
Very simple. He just started his own Captive Portal Checkin Service. So no need for Google anymore
WHAT YOU NEED:
- Computer with installed ADB
- Active USB Debugging at your phone
- At least Android 7
TESTED ON:
I tested his instructions on my old Xperia Z3 phone (CarbonROM 7.0 based on Android 9, Custom Rom).
IMPORTANT:
You need to execute the commands with a booted system (valid for both posts where i write the instructions). It DOESN'T work in the terminal of recoveries (e.g. twrp).
Thanks @jaysir for the information.
INSTRUCTIONS:
Android 7:
1. Connect the phone with your computer
2. Activate ADB and test the connection with the "adb devices" command. If your phone shows up go to step 3.
3. Execute these commands in your terminal:
=> adb shell 'settings put global captive_portal_http_url "http://captiveportal.kuketz.de" '
=> adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de" '
Android 8 and 9:
1. Connect the phone with your computer
2. Activate ADB and test the connection with the "adb devices" command. If your phone shows up go to step 3.
3. Execute these commands in your terminal:
=> adb shell 'settings put global captive_portal_http_url "http://captiveportal.kuketz.de" '
=> adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de" '
=> adb shell 'settings put global captive_portal_fallback_url "http://captiveportal.kuketz.de" '
=> adb shell 'settings put global captive_portal_other_fallback_urls "http://captiveportal.kuketz.de" '
Well that's it. When you want to revert back just execute the commands again with this url:
http command: http://connectivitycheck.gstatic.com/generate_204
https command:
https://connectivitycheck.gstatic.com/generate_204
Link to the source:
https://www.kuketz-blog.de/android-...204-http-antwort-von-captiveportal-kuketz-de/
If i make any typos tell me
Thanks again to the german security researcher and his community there is a way to deactivate the captive portal checkin completly.
It works on Android 7 and Android 8.1/9. But in comparision to the method in my first post this needs root access on your phone.
For all new users:
I recommend Magisk to gain root.
So now the instructions:
For Android 8/9:
1. Open a terminal on your phone (via terminal apps).
2. Type the following command:
- su
- su
- pm disable com.android.captiveportallogin
- settings put global captive_portal_detection_enabled 0
- settings put global captive_portal_server localhost
- settings put global captive_portal_mode 0
3. Then reboot your phone (via hardware buttons, system or terminal app).
For Android 7:
1. Open a terminal on your phone (via terminal apps).
2. Type the following commands:
- su
- settings put global captive_portal_detection_enabled 0
- settings put global captive_portal_server localhost
- settings put global captive_portal_mode 0
3. Then reboot your phone (via hardware buttons, system or terminal app).
Link to Source
https://www.kuketz-blog.de/empfehlungsecke/#captive-portal
Very nice and very important tutorial!
Just for completeness; and I don't claim and definitely don't have a copyright. I reported these procedures already here end of April in the thread "Enhanced Privacy, Security and Battery Duration! My Measures...". I mentioned it also once here in the AFWall+ thread.
I'm very glad that these procedures get repeated and repeated again. From my personal point of view it's so important to develop the stance to not allow Google to collect our data. I've subscribed to Mike Kuketz and am very grateful for his job and dedication.
Oswald Boelcke said:
Very nice and very important tutorial!
Just for completeness; and I don't claim and definitely don't have a copyright. I reported these procedures already here end of April in the thread "Enhanced Privacy, Security and Battery Duration! My Measures...". I mentioned it also once here in the AFWall+ thread.
I'm very glad that these procedures get repeated and repeated again. From my personal point of view it's so important to develop the stance to not allow Google to collect our data. I've subscribed to Mike Kuketz and am very grateful for his job and dedication.
Click to expand...
Click to collapse
I agree to you. It's a pity that so much people don't care about it.
I must admit i forgot to search in forum whether the instructions was already posted but as you said every mention helps.
Thanks, however, not working on pixel experience rom.
Update：
Seems no settings command under ADB shell, worked when turning on Usb debugging.
jaysir said:
Thanks, however, not working on pixel experience rom.
seems no settings command under ADB shell
Click to expand...
Click to collapse
Thx for your info. And i will try it on my old z3 with the custom rom which you mentioned.
I know there is a Android 9 based Pixel Experience for the z3.
Will report then.
dhacke said:
Thx for your info. And i will try it on my old z3 with the custom rom which you mentioned.
I know there is a Android 9 based Pixel Experience for the z3.
Will report then.
Click to expand...
Click to collapse
Sorry, I did not make myself clear.
It just not working under recovery mode.
After booting to the system and opening the USB debugging, it is working.
jaysir said:
Sorry, I did not make myself clear.
It just not working under recovery mode.
After booting to the system and opening the USB debugging, it is working.
Click to expand...
Click to collapse
Good to know (and i'm happy that now everything works)
I will edit the guide and add your information to it.
Thanks.
Thanks dhacke for all this information.
I got here from a link on an XDA forum for the Huawei Watch 2 LTE smartwatch. Do you know if this can be done to the watch as well?
ajlajluk said:
Thanks dhacke for all this information.
I got here from a link on an XDA forum for the Huawei Watch 2 LTE smartwatch. Do you know if this can be done to the watch as well?
Click to expand...
Click to collapse
As far as i see it the adb method (post 1) could working because according to the Internet the device runs Wear OS which is basically a android version for smartwatches.
So in theory you can activate USB debugging and redirect the captive portal to mike kuketz service as long as the commands are accepted.
Regarding method 2 i can't say anything because i don't own a smartwatch and have zero knowledge whether root is possible/how it is done on those smartwatches (which is needed for that method).
dhacke said:
As far as i see it the adb method (post 1) could working because according to the Internet the device runs Wear OS which is basically a android version for smartwatches.
So in theory you can activate USB debugging and redirect the captive portal to mike kuketz service as long as the commands are accepted.
Regarding method 2 i can't say anything because i don't own a smartwatch and have zero knowledge whether root is possible/how it is done on those smartwatches (which is needed for that method).
Click to expand...
Click to collapse
Just as you said, I enabled adb debugging, opened a terminal session from my mac to the watch and sent the commands from version 1 and they were both accepted. I should be able to check if it has worked tomorrow so will keep everyone updated when I've tested it.
OK. My watch appeared to connect to wifi but then said "No Internet".
I've now done the same mod to my phone, deleted the supermarket wifi I'm trying to connect my watch to from both the watch and the phone and will try again. I'm also wondering whether haveing BT on at the same time is causing a problem so I'll try with it on and then off and see if it makes any difference.
Thanks again for giving me hope I'll be able to connect WearOS 2 to a captive portal wifi network.
Further to above, unfortunately still no joy. Watch says "Connected" for the briefest moment then "No Internet" and won't go any further.
Never mind.
Thanks again for your work for the Android community.
Is it safe?
We are sending data to completely unknown server, that's why asking.
Datta258 said:
Is it safe?
We are sending data to completely unknown server, that's why asking.
Click to expand...
Click to collapse
In my opinion yes. The mentioned security expert has a good reputation afaik and he didn't make any things in the past which give me a reason to distrust him.
And in the near future he will work for german commissioner for data protection and freedom of Informationen. So i think he is a trustworthy person.
In the privacy policy on his site for the captive portal check service he writes that no information at all will be logged.
Of course you can ask him directly via e-mail if my words don't soothe you; i can only share my opinion about that guy
Thanks.
dhacke said:
For Android 8/9:
1. Open a terminal on your phone (via terminal apps).
2. Type the following command:
- su
- su
- pm disable com.android.captiveportallogin
- settings put global captive_portal_detection_enabled 0
- settings put global captive_portal_server localhost
- settings put global_portal_mode 0
3. Then reboot your phone (via hardware buttons, system or terminal app).
Click to expand...
Click to collapse
Does this still work on Pie?
On my rooted Galaxy Note 10 (Pie, 1st Sept. Patch) it does not.
Btw. there is a typo, should it be "settings put global captive_portal_mode 0"? This is what I tried. If I then check the values by "settings get..." I get
1: 0
2: localhost
3: 0
So the values were taken, but it still tries to connect to captiveportal.kuketz.de or google (whatever I have set). If I block it, I will get the exclamation next to the wifi symbol.
ZXR said:
Does this still work on Pie?
On my rooted Galaxy Note 10 (Pie, 1st Sept. Patch) it does not.
Btw. there is a typo, should it be "settings put global captive_portal_mode 0"? This is what I tried. If I then check the values by "settings get..." I get
1: 0
2: localhost
3: 0
So the values were taken, but it still tries to connect to captiveportal.kuketz.de or google (whatever I have set). If I block it, I will get the exclamation next to the wifi symbol.
Click to expand...
Click to collapse
Oh yes you are right. There was a typo. It must be 'settings put global captive_portal_mode 0'.
Now it's corrected. Thanks.
Did you make a reboot after execute the commands?
On my side it works on Pie too. I have a z3 with Lineage 16 and my device doesn't make the check.
When it' still not work after the reboot and the commands are typed in right (=> no issue notification in the terminal comes up) the Samsung stock rom could be the problem.
In that case i would recommend to use kuketz server.
dhacke said:
Did you make a reboot after execute the commands?
Click to expand...
Click to collapse
Yes and even after several reboots I get:
adb shell settings get global captive_portal_detection_enabled
0
adb shell settings get global captive_portal_server
localhost
adb shell settings get global captive_portal_mode
0
But, if not opened via script, I can see 185.163.119.132 (kuketz) being blocked by AFWall and the exclamation mark. So I open it with
$IPTABLES -A "afwall" -d 185.163.119.132 -m owner --uid-owner 1000 -p tcp -j ACCEPT
This works but I would prefer no C-P check.
One off-topic question:
Do you have an idea how to open the IP 0.1.0.1:0 in AFWall? It is used for VoLTE, but even I use th script line above (with 0.1.0.1) it still gets blocked. I have to open UID 1000 completely...
ZXR said:
Yes and even after several reboots I get:
adb shell settings get global captive_portal_detection_enabled
0
adb shell settings get global captive_portal_server
localhost
adb shell settings get global captive_portal_mode
0
But, if not opened via script, I can see 185.163.119.132 (kuketz) being blocked by AFWall and the exclamation mark. So I open it with
$IPTABLES -A "afwall" -d 185.163.119.132 -m owner --uid-owner 1000 -p tcp -j ACCEPT
This works but I would prefer no C-P check.
Click to expand...
Click to collapse
You wrote 'adb'. Does it mean that you tried the commands in the adb shell from your Computer with connected phone?
That could explain why it isn't working. The commands must be typed in directly on the phone for deactivation.
I use the App 'Terminal Emulator' from F-Droid for this.
Link: https://f-droid.org/app/jackpal.androidterm
You could try it with that app once more. Apart from that i'm running out of ideas atm.
ZXR said:
One off-topic question:
Do you have an idea how to open the IP 0.1.0.1:0 in AFWall? It is used for VoLTE, but even I use th script line above (with 0.1.0.1) it still gets blocked. I have to open UID 1000 completely...
Click to expand...
Click to collapse
Sorry, but no. I don't use VoLTE or Scripts in AfWall+.
Is it possible to enable root debugging from the command line. The rom that I'm using is missing the setting in developers options. When trying adb root I get the
Code:
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I don't believe it's totally disabled because I don't get the "adb root is not allowed in production builds". I think it's there but no switch to toggle. Haven't found anything searching for setting name and would need correct value and table if it can be set. Anybody know how to toggle it on from shell ?
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
jwoegerbauer said:
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
Click to expand...
Click to collapse
Thanks, actually looking into it, I don't know what to think about it. It is a user build of crdroid. I can not and absolutely do not understand the point of building a user build to post on XDA. The fact that someone is installing a custom rom kinda throws a user build out the window AFAIFC. It didn't even dawn on me to check if it was userdebug or not, in my mind, of course it is. That's what I get for thinking I guess. I like CrDroid so syncing source now, time to sync and build I should have an eng build in about 3 hours.
Take note that if adbd in your phone's firmware is build without ALLOW_ADBD_ROOT then you're wasting your time.