Related
It's quite clear now that something in the new update has disabled much of our precious tethering features, I have tried all of the different guides and tutorials I've found on the net with no success. Does anyone have any ideas?
pimpedz said:
It's quite clear now that something in the new update has disabled much of our precious tethering features, I have tried all of the different guides and tutorials I've found on the net with no success. Does anyone have any ideas?
Click to expand...
Click to collapse
#1 You're going to get bashed for posting in dev forum.
#2 Check out the lastest ROMs : Alien, AURA, etc. do everything except wipe your butt.
I apologize, I was much too vague in my original post. Allow to explain:
Pretty much every ROM out there enables tethering, however, AT&T has some sort of verification system when one uses the lapdock. This system is completely independent of the regular tethering hacks. I posted in the dev form in the hopes of inciting people to try and figure out what exactly has change. This is my current theory:
When the phone is placed into the lapdock cradle a request is sent to AT&T's servers to see if the account has a tethering plan or not. I also tried tethering to my laptop at the same time as putting the phone in the dock. Tethering worked just fine until my phone was placed into the dock, where it proceeded to give the error of "Lost 3g connection". Disabling entitlement check bypasses this for regular tethering, but not the dock. So then the these are my best guesses on how to fix the situation:
If we simply blocked the IP that this check is going through, would it bypass it?
Is there anyway to simply remove the check?
pimpedz said:
Pretty much every ROM out there enables tethering, however, AT&T has some sort of verification system when one uses the lapdock...
Click to expand...
Click to collapse
I am running Alien #4 ROM and this is working; this has also worked perfectly for me on Froyo stock as well.
1. Plug phone into lapdock
2. Click okay on error message saying you have to be on wifi
3. Turn on mobile hotspot (entitlement check disabling will allow this)
4. Open browser and find that you now have internet
5. Disable mobile hotspot (if you want)
6. Continue surfing on browser
7. ???
8. Profit!
bleuiko said:
I am running Alien #4 ROM and this is working; this has also worked perfectly for me on Froyo stock as well.
1. Plug phone into lapdock
2. Click okay on error message saying you have to be on wifi
3. Turn on mobile hotspot (entitlement check disabling will allow this)
4. Open browser and find that you now have internet
5. Disable mobile hotspot (if you want)
6. Continue surfing on browser
7. ???
8. Profit!
Click to expand...
Click to collapse
+1 Worked for me
First of all, you are asking a question in the Dev forum which is a no-no, regardless of what the question is about. Just try to remember that for next time.
Second, there is a thread for this already here:
http://forum.xda-developers.com/showthread.php?t=1160452
Take a look in there and see if any of their solutions can help you out or you could have at least asked your question there.
(It is also frustrating that this thread I just linked you to is on the first page of this forum so it would have taken no effort at all to find, just saying)
Excuse if I seem rude, I still haven't had my coffee...
pimpedz said:
I apologize, I was much too vague in my original post. Allow to explain:
Pretty much every ROM out there enables tethering, however, AT&T has some sort of verification system when one uses the lapdock. This system is completely independent of the regular tethering hacks. I posted in the dev form in the hopes of inciting people to try and figure out what exactly has change. This is my current theory:
When the phone is placed into the lapdock cradle a request is sent to AT&T's servers to see if the account has a tethering plan or not. I also tried tethering to my laptop at the same time as putting the phone in the dock. Tethering worked just fine until my phone was placed into the dock, where it proceeded to give the error of "Lost 3g connection". Disabling entitlement check bypasses this for regular tethering, but not the dock. So then the these are my best guesses on how to fix the situation:
If we simply blocked the IP that this check is going through, would it bypass it?
Is there anyway to simply remove the check?
Click to expand...
Click to collapse
An infraction was given to the OP to remind them to not create question threads in the developer forums. Hopefully this will prevent them and others from doing so in the future.
I posted this in Tasker's Google Groups, but nobody had a solid solution for me. Since the XDA is full of intelligent people, figured I'd give this a shot.
I want to use Tasker to automatically enable my WiFi Tether app automatically under certain circumstances (namely, to sync my tablet's RSS while I get ready for work in the morning).
I followed these directions to set it up, but quickly discovered that the command was wrong. After a little searching and then taking this picture, I arrived at the command being !/data/data/com.googlecode.android.wifi.tether/bin/tether start. However, that doesn't work. When I test it, it grants superuser permissions, but never starts tethering.
It was recommended to me that I try the misc/script function, but I don't understand how that works. Alternately, they recommended I try the built-in wifi tether functionality, but as I'm on a completely stock ROM, I don't believe I can do that (unless someone figure out what to change to unlock it). I used to do that on my old EVO 4G with MikG, though, so I know that would work if I had a ROM with the feature unlocked.
So, any advice on how to resolve this problem is welcome. At current, I turn it on manually, but Tasker is great at making life easier and this would be a huge convenience if I could get it to work.
And before someone recommends a custom ROM, I'm on the fence with doing that. There are features I'd love to have, but the ROMs that have all of those features also have features I don't want (like remapping the multi-tasking button, for example). Perhaps someday I'll have the time to sit down and figure out how to build my own ROM.
No ideas? The XDA has never let me down, before...
I read a mod yesterday that enables the built-in tethering.. it was like 1 change.. it worked for me.
btw i have tasker but maybe people didn't want to buy it and therefore can't help, just a thought?
edit:
open your build.prop and add anywhere in it the following line:
code:
ro.tether.denied=false
then reboot and u should be good to tether.
Well it's not necessarily familiarity with Tasker that I figured would help (of course, with the Misc/Script explanation, it would be), but rather the program language stuff. Perhaps the command I was using was wrong, and someone with ADB experience could correct it. With that said, I have seen a lot of people on here comment about how they use Tasker, so I didn't think it was a stretch that someone familiar with it could help with the Misc/Script part.
I will give your recommendation a shot, though. Thanks!
So I added the line to the build.prop, and it worked exactly once. Second time I started it, I got a data call failure as it dropped 3G. Continued getting the failure warning until turning off tethering. Repeating process yielded same results.
Sent from my EVO LTE using Tapatalk 2
Tasker for Wifi Tether
Not sure if your even paying attention to this post anymore but I had a few tidbits of info that might help.
I have had the same problem but I am using tasker in addition to NFC task launcher. I wanted to be able to turn WiFi tether on after swiping an NFC tag.
I tried the same string that you mentioned in post 1(!/data/data......) to no avail. The way that I got it to work was I set a task in NFC task launcher to open the WiFi tether app then a task that ran the string. Although the app opened and it APPEARED that it did nothing after that but it actually was working in the back ground. I haven't tested the same scenario using just tasker but it should work. So you should just need a task to open WiFi tether and one that runs the string. The string should be controlled with the Locale plugin. At least I think that is what its called. Hope this helps.
My issue is that I am constantly stepping outside, out of reach of my modem, and I'll have to turn my Wi-Fi off or my phone will stay connected to the the incredibly weak wifi signal.
So, I tried turning the dev option for "aggressive wifi to cellular handover" on thinking this would help and allow me to just leave wifi turned on while stepping outside and have it switch over to data without my assistance. And it worked, for the most part (it still held on to wifi signals *I* would deem too slow, but not often), BUT whenever I reboot the option in dev settings un-ticks so I have to go back in and turn the setting back on.
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Thank you in advance!
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Juggernaut79 said:
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Click to expand...
Click to collapse
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
6NomoN6 said:
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
Click to expand...
Click to collapse
For me it disconnects from a weak signal.
I'll be back!
6NomoN6 said:
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Click to expand...
Click to collapse
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! I'm googling now for a solution because going into developer options every reboot is incredibly damaging to the smoothness of the user experience I've worked so hard to customize.
Whether I find a solution or not I'll post in this thread again to let you know. If the latter is the result I will personally either write a tasker script, init.d script, or if nesseceary an Xposed module depending on factors I've yet to research. Can you Beta test for me if it comes to that? Maybe it's as simple as editing build.prop, I don't know yet, but I wanted to make this post ASAP so that you know you aren't alone on this and someone capable is working on the issue. For a developer like myself tapping menus every boot is unacceptable! Hopefully there is already a fix out there in the wild and I won't have to do any work.
P.S. Don't forget to also enable cellular radio always active for fast network switching at the price of some battery life. It's a few options below aggressive handover in Developer Options and thank jolly the setting is sticky unlike it's counterpart. Also, sorry for the poor turnout on your thread. I figured there'd be 100 posts by now, but at least you got my attention.
Edit 1: "setprop persist.{i-dont-know-yet}" in terminal emulator may do the trick. Checking for variables for the setting we want now. Hopefully they exist!
Edit 2: :laugh: I FOUND EVERYTHING I NEED FOR A FIX!!! However, an Xposed module will be required. I need some sleep but I should have something by tomorrow night. In case any other developers are reading this, here is the information required to make things work the way Iwe want them to:
http://android.stackexchange.com/qu...-cellular-handover-option-in-developer-settin
https://android.googlesource.com/pl...ndroid/settings/DevelopmentSettings.java#1061
Edit 3: Now that I know how this setting actually works together with wifi_watchdog (see source code WifiWatchdogService.java) I think I may have changed my mind regarding how to go about solving the root problem at hand (network switching) which this setting really does a "hack" job of taking care of. The developer that made it decided on a arbitrary, static number to be used for decreasing the connected WiFi AP's RSSI value (thereby making handover more "aggressive") instead of exposing any kind of grainular control to the user. So yes I could easily make the developer options setting stick but a much better approach would be to hook the method android.net.wifi.WifiManager with an Xposed module and implement additional logic to the network switching. The great thing about this method is there is the possibility for adding additional checks besides just periodically pinging the current primary dns server and monitoring the delay and timeout of the result. I also know for a fact modding the framework persists after reboot which is afterall all we originally wanted to have. The second or alternative route would be to edit the secure settings database using SQLite. The pro of this method is it is guranteed to be compatible with nearly ANY rom, won't break anything after an update, and doesn't use resources like an Xposed module. The con is that you are limited to the variables built into android, can't implement any new logic, and the worst is that I'm not even sure the modified tables would even persist after a reboot (or network state change for that matter) which if true would defeat the original purpose of this expedition. I'll make a fourth edit to this post after I've thought about and considered how to best proceede to reaching the goal of having a solution to our problem. :victory:
FoxysWorkplace said:
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! (...)
Click to expand...
Click to collapse
First of all, thank you so very much for looking into this!
I'm sorry for not responding sooner, but I had honestly lost hope of finding a solution to this issue mainly because I am not a developer myself and haven't the foggiest how to get started with it on Android
But when I opened my notifications and saw a response to this post (!) I got *extremely* excited, and as I read through your post, my excitement intensified to great happiness!
I can't express my gratitude, but I would be more than happy to help with anything that I can!
Any news on this?
Has anyone found a solution?
Had anyone found a solution that doesn't require root access?
Can we expect that fourth update any time soon? Any solution without xposed?
I'm following this thread in the event that someone finds a non-rooted solution. The Galaxy S7 really cannot be rooted without a serious performance hit (and yes I've gone through the two or three best/popular lag-fix solutions) but it works best in stock :-/
I'll start with the preliminary "If this is the wrong place please let me know and I will relocate" prefix.
The issue is pretty easy to explain, After rooting my phone and removing what I thought was bloatware the wifi and data no longer wants to work/services aren't turning on (began after restart not immediately following the root or software removal)
I should have made a backup prior to rooting but I was feeling lazy and it's an older unit, worse case scenario I'll replace it so that wasn't a huge issue at the time (hindsight is 20:20 and I'd rather not replace it right now)
I have a samsung sch-i200 running 04.01.02. I decided for various reasons that I should root the phone as I have with a few others in the past. So I did my research, found a comfortable software, and rooted the phone. Everything worked fine at first root went though perfectly and all the features I was looking for ended spot on. Then I went through and removed some of the bloatware from the phone and things started to get tricky. I am guessing that I misjudged like an idiot the purpose of one of these applications and messed up something I shouldn't have.
The applications I removed were named:
backup+ media
my verizon mobile
sync service
verizon guide tours
verizon login
verizon remote diag
voicemail
verizon tones
vz navigator
I don't use Verizon as a carrier so I was assuming (again, like an idiot I believe) that one of those services was either not part of the bloatware they added, or I misjudged the necessity of said bloatware. The other possibility is that the root I went through DID fail to complete properly, although I am not really convinced yet of that as the phone had been restarted several times after the root with no issues. Currently the phone is still able to call and text fine but I haven't been able to get the wifi to turn on or data to activate.
To keep this from getting too long winded I won't go much further in detail, I'm somewhat tech savvy but not an expert by any means and have exhausted my knowledge on searching via google and other forum sources I could find. At this point I would love to just get a copy of the stock ROM for the phone so I could just revert it back to factory but that seems to be something of a unicorn on the internet at this time.
I should state that I have attempted the basic troubleshooting, power cycle, airplane mode toggle, safe mode, settings reset via the boot menu options (full wipe and restore), I've also made some attempt to try and find a way to reinstall the bloatware I removed but can't seem to find it.
I generally hate posting on forums about these things because you can normally find an answer if you search but i'm on about 6 hours of forum crawling and am either blind or unable to find it, so I plea now for assistance.
Any help will be appreciated.
First, to clarify, I have the Samsung Galaxy A21 (there is no dedicated forum, so it seems we A21 users must use the A21s forum.) Although this may at least somewhat apply to the A21s (it may actually have the advanced service menu, so may at least have that as an option. The A21 is considerably more gutted in even the most basic functionalities.) One bit of confusion on my part is the actual SoC is a MediaTek, not a Samsung Exynos. However, all warnings regarding these exploits list "A21" so I'm assuming that the modem may still be a Samsung modem. Though of course it may just not apply and they really mean the A21s (these models are so completely different they really should not have been given the same number,) I have no choice but to assume the A21 is included until someone says otherwise.
The main vulnerabilities are these four:
CVE-2023-24033
CVE-2023-26496
CVE-2023-26497
CVE-2023-26498
Apparently there are 18 in total, but these are the ones that allow "zero click" remote code execution (presumably with at or near root access.) One thing I've been unclear about though is if you have to actually accept the call or not. The implications of the warnings seems to be that all they need is your phone number to initiate the exploit (which would mean that bad actors could just simply use an automated system to run through basically every number if they really wanted.) Though to me it would make the most sense if it actually required you to accept the call. (I'd really like some clarity on this as that would mean simply rejecting any call not known to be safe would usually be sufficient.) For now I have to work with the assumption it truly is "zero click" as they describe it.
Given that VoLTE is normally not an option the user can toggle (especially in recent ROMs) there seems to be basically no way to turn it off these days. Phones used to sometimes have a toggle in the cellular settings, but not anymore it seems (probably due to it being basically required now.) I tried to enter the advanced service menu (*#26833662#), but it said not supported when I did. The standard service menu does not have any options or controls (let alone anything regarding VoLTE.) I remember in the past on an older (less locked down) phone I did have options to enable/disable VoLTE (though it didn't work due to the hot flaming mess that is VoLTE -- it really should have been required to be standardized and enabled across all devices physically capable of it before the 3G cutoff) via one of the service menus, but unfortunately this one doesn't seem to have that. Is there any other way I can disable it and at least keep my cellular access? I realize this means data only, but that leaves at least some possibilities such as VoIP calling like Google Voice and, more importantly, does leave me access to online things when I don't have WiFi.
It should go without saying, but I do have WiFi calling off, so no issue there.
Bump. There is still no security update on mine. There may never be. I wouldn't be shocked at all if it's abandoned at this point. Even just a data only connection would have to be sufficient until I can come up with a better phone solution if that's what it takes, but I need to at least be able to use it for some basics on data, so removing the SIM isn't going to work.