Hello people of XDA - hoping someone here can point me in the right direction.
I am fairly new to the phone modding scene (had an N1 for the longest time with stock rom) but anyways..
I'm having a few issues with my brand new N4 around tethering with LTE enabled.
Items:
N4 Stock (4.2.1)
N7 Stock (4.2.1 & 4.1.2)
Here's the low down...
Tethering works perfectly with default settings (WCDMA Preferred). Essentially I can tether my N7 and access the internet whenever I have H, 3G, or E wireless signals
While on 4G (LTE), my N7 will connect to the phone but will not be granted internet access. Signal is at full strength for the wifi but it does not turn blue to indicate connection. Inet doesn't work with any program I try to access it with and this happens on both my N7s. (non-LTE tethering works fine).
I am on Roger's LTE network in Canada (and yes, LTE does work on the phone itself. Speed test confirms this... just not on the N7 when tethered...)
Any and all help would be greatly appreciated as I am excited to use this device as an LTE tether!!
- Tymko668
It could be a network limitation. I have no issues doing tethering with the N4 to the N7 as well using HSPA down but since I don't have LTE in my area, I can't say the same.
It might have something to do with the phone not being built to handle LTE. Maybe the LTE chip isnt connected to the transmitter for tethering or something...who knows
I'm experiencing this EXACT same situation. I'm also on Rogers, except instead of trying to tether a Nexus 7, I'm trying to tether my desktop PC via wireless to my Nexus 4.
It seems as long as I'm connected by cellular via HSPA+ (not LTE), I can get a working Internet connection on my desktop. My phone info is set to LTE/GSM/CDMA auto (PRL), which actually doesn't work if you want to connect to LTE. I've also gotten the tethering to work with WCDMA preferred (3G/HSPA+ connection).
But once I use LTE only or LTE/GSM auto (PRL), and it establishes a 4G (i.e. LTE) connection, the tethering doesn't work anymore.
I have a hunch that Rogers has disabled tethering for LTE connections. I think they have that capability to detect if you're tethering...?
---------- Post added at 11:12 PM ---------- Previous post was at 10:58 PM ----------
By the way, do you know what the default settings are for a Nexus 4 on Rogers for "IMS registration required"? I accidentally toggled that in the Phone Info app, but I can't tell what the original setting was.
Is this the default?
Turn off radio
Turn off IMS registration required
Turn on SMS over IMS
Turn on lte ram dump
Thanks.
I checked a Rogers branded Sony Ion, and found that it had a second APN
I copied all the following settings, but it still doesn't work for LTE tethering.
Name: Rogers Tethering
APN: ltedata.apn
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: Not Set
MMS proxy: Not Set
MMS port: Not Set
MCC: 302
MNC: 720
Authentication type: Not Set
APN type: dun
APN protocol: IPv4
APN roaming protocol: IPv4
APN enable/disable: Greyed out, but Checkmarked
Bearer: Unspecified
According to this guy, the Nexus 4 doesn't support tethering over LTE?... I dunno where he's getting his info, though.
Jacmert said:
According to this guy, the Nexus 4 doesn't support tethering over LTE?... I dunno where he's getting his info, though.
Click to expand...
Click to collapse
I don't know where he'd get that information from, but I can verify that neither bluetooth or wifi tethering work when the connection is LTE. The only way I can get it to work is when I set my phone to WCDMA preferred.
Sent from my Nexus 4 using xda app-developers app
Hey, just wondering if this issue has been resolved? Maybe via a custom ROM or root application? I am having the same issue; I cannot get Internet signal when I tether via LTE, only via HSPA+. I'm on Fido.
i coudn't get LTE to tether either, but theres a work around on XDA, you have to input some lines into the terminal or something, its out of my scope :crying:
cobyman7035 said:
i coudn't get LTE to tether either, but theres a work around on XDA, you have to input some lines into the terminal or something, its out of my scope :crying:
Click to expand...
Click to collapse
Can you post the work around
Fred2028 said:
Can you post the work around
Click to expand...
Click to collapse
I believe this is what he was referring to:
http://forum.xda-developers.com/showpost.php?p=34662473&postcount=11
is everyone else that is experiencing the tethering problems over LTE also using CM10?
owoOWOowo said:
is everyone else that is experiencing the tethering problems over LTE also using CM10?
Click to expand...
Click to collapse
its not just cm10, i think this is a problem with all nexus 4.
It just wont work
Finally after months of working through this I have confirmed that Rogers has in fact disabled any teathering over LTE. It doesnt matter what phone you use or ROM, it just wont work.. I was told that they are cycling through accounts and turning this feature off and you will only be able to teather over HSPA+ or 3G..... This is horrible Rogers...
codyguthrie39 said:
Finally after months of working through this I have confirmed that Rogers has in fact disabled any teathering over LTE. It doesnt matter what phone you use or ROM, it just wont work.. I was told that they are cycling through accounts and turning this feature off and you will only be able to teather over HSPA+ or 3G..... This is horrible Rogers...
Click to expand...
Click to collapse
Robbers has done a lot worse... Thanks or the info though, I'm sure it'll save months of research for others
neotekz said:
its not just cm10, i think this is a problem with all nexus 4.
Click to expand...
Click to collapse
I'm not on CM10. I'm using stock kernel with mmuzzy Rom. I posted here more verbalized instructions on how I did it using those commands (http://forum.xda-developers.com/showpost.php?p=34662473&postcount=11)
You can see my post here of my N4 setup: http://www.howardforums.com/showthread.php/1783816-Nexus-4-LTE-Rogers-LTE-Down
codyguthrie39 said:
Finally after months of working through this I have confirmed that Rogers has in fact disabled any teathering over LTE. It doesnt matter what phone you use or ROM, it just wont work.. I was told that they are cycling through accounts and turning this feature off and you will only be able to teather over HSPA+ or 3G..... This is horrible Rogers...
Click to expand...
Click to collapse
Where's your source for this? This sounds like BS.
codyguthrie39 said:
Finally after months of working through this I have confirmed that Rogers has in fact disabled any teathering over LTE. It doesnt matter what phone you use or ROM, it just wont work.. I was told that they are cycling through accounts and turning this feature off and you will only be able to teather over HSPA+ or 3G..... This is horrible Rogers...
Click to expand...
Click to collapse
This is simply not true. I have it working right now: tether over LTE on my Nexus4 on Rogers.
If you log in to the phone via ADB and as root (either via "adb root" command, or via "su" from the shell) execute the commands listed here the tethering will work. Test it yourself.
If you want a persistent fix you have two options:
1) If you have a custom kernel installed, create a script in /system/etc/init.d that executes the commands from the post above (don't forget to set the permissions to executable!).
2) Install a program like Script Manager from the market, create a script using the commands from the post above, and tell it to execute the script at startup with root permissions.
Currently I'm running a rooted stock ROM with stock kernel, so I'm using Script Manager, and it's working perfectly.
Here's the script I'm using right now:
Code:
#!/system/bin/sh
iptables -A bw_FORWARD -i !lo+
iptables -A natctrl_FORWARD -j RETURN -i rmnet+ -o wlan0 -m state --state RELATED,ESTABLISHED
iptables -A natctrl_FORWARD -j DROP -i wlan0 -o rmnet+ -m state --state INVALID
iptables -A natctrl_FORWARD -j RETURN -i wlan0 -o rmnet+
iptables -A natctrl_FORWARD -j DROP
iptables -A natctrl_nat_POSTROUTING -t nat -o rmnet+ -j MASQUERADE
XanSama said:
This is simply not true. I have it working right now: tether over LTE on my Nexus4 on Rogers.
....
Click to expand...
Click to collapse
This worked perfectly on mine. Thanks so much!
Any idea how to set the phone to LTE mode on boot so we don't have to jump into that 'hidden' menu?
bcrook said:
This worked perfectly on mine. Thanks so much!
Any idea how to set the phone to LTE mode on boot so we don't have to jump into that 'hidden' menu?
Click to expand...
Click to collapse
Glad to help. And yeah, absolutely.
To get it to stick successfully for reboots, there are a couple quick mods you need to make.
Note: To make these mods you need your /system partition to be writeable (RW) not read-only (RO). You can accomplish this with the "mount -ro remount,rw /system" command via ADB or Terminal.
1) In the file "/system/build.prop" you need to:
a) Remove the line that says "telephony.lteOnCdmaDevice=0"
b) Add a line that says "telephony.lteOnGsmDevice=1"
c) Add a line that says "ro.telephony.default_network=9"
d) Add a line that says "ro.ril.def.preferred.network=9"
e) Save the file.
2) In the file "/system/etc/apns-conf.xml" you need to add the following entry above the standard "Rogers" entry (I actually replaced the Chattr Wireless entry with this one):
Code:
<apn carrier="Rogers LTE"
mcc="302"
mnc="720"
apn="ltemobile.apn"
port="80"
mmsc="http://mms.gprs.rogers.com"
mmsproxy="10.128.1.69"
type="default,supl,mms"
/>
3) Perform a factory reset on your device. (I know this sucks, but it's required.)
4) Don't ever load the *#*#4636#*#* config menu again; if you do it will revert to WCDMA Preferred until you factory reset again.
I've also attached a zip with my modified build.prop and apns-conf.xml for the stock (but rooted) ROM; as well as my iptables script for good measure. You should just be able to copy these across to their designated locations and then perform steps 3 and 4. Don't forget to make the system partition RW before copying, or it won't work!
Note: Follow the instructions in my last post to use the iprules.sh script if you want to use it.
Note2: Zip is not flashable! Someone could make it flashable, but I'm lazy. For now just extract the files and copy them manually.
Related
Hello.
I am trying to tether my sim-card-less G1 to my windows mobile phone (using bluetooth) so I can use the unlimited data plan of my cdma windows mobile phone with my G1.
I can't code, so, I decided to put a little incentive behind my wish : 150$.
I've put up a bid request here : http://www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=1231518
I think a good starting point would be to use http://code.google.com/p/android-wifi-tether/ , it already installs the binaries and kernel extensions for pand, iptable... I think it only needs some tweaking to allow it to do it's job in the opposite direction, and some more work to allow it to connect properly to the windows mobile based bluetooth access point.
Any takers?
How about this: cancel the wimo cdma crapola and throw it at a bus. Be sure that it gets crushed into tiny bits, then sweep it into a pile and piss on it. Now go to tmobile or att and sign up for some data plan.
If you really insist on doing things the retarded way and tethering a phone through a phone, there is no coding required. You just need to read up on pppd linux bluetooth tethering for how to actually do it.
stanelie said:
Hello.
I am trying to tether my sim-card-less G1 to my windows mobile phone (using bluetooth) so I can use the unlimited data plan of my cdma windows mobile phone with my G1.
I can't code, so, I decided to put a little incentive behind my wish : 150$.
I've put up a bid request here : http://www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=1231518
I think a good starting point would be to use http://code.google.com/p/android-wifi-tether/ , it already installs the binaries and kernel extensions for pand, iptable... I think it only needs some tweaking to allow it to do it's job in the opposite direction, and some more work to allow it to connect properly to the windows mobile based bluetooth access point.
Any takers?
Click to expand...
Click to collapse
Switching plans or company is really not an option for me.
My CDMA phone is on telus, and they are the only company here to offer a less evil data plan. The GSM companies, Rogers and Fido, are outrageously expensive.
I did manage to tether the G1 to my computer using bluetooth, I could ping both ways, but the iptable stuff is beyond me.
I was reading http://joshuaredstone.blogspot.com/2009/01/bluetooth-tethering-from-ubuntu-to.html and http://www.gotontheinter.net/content/second-g1-story-proper-bluetooth-tethering-how-short
No takers for my retarded request?
Doesn't your WinMo phone have WiFi?
You could use WMWifiRouter that converts your phone in an AP and connect in Ad-Hoc mode with the G1 to the WinMo.
stanelie said:
My CDMA phone is on telus, and they are the only company here to offer a less evil data plan. The GSM companies, Rogers and Fido, are outrageously expensive.
Click to expand...
Click to collapse
I can't imagine what you must be smoking because they both cost EXACTLY THE SAME...
Telus: $25 for 500MB, $30 for 1GB, $60 for 3GB, reference: http://www.telusmobility.com/en/ON/connectplans/index.shtml
Rogers/Fido: $25 for 500MB, $30 for 1GB, $60 for 3GB, $80 for 5GB, reference: http://www.rogers.com/web/content/wireless-plans/iphone_phones_plans#dop and http://www.fido.ca/web/content/internet/wia_email_options
Wifi is not an option, it drains the battery of the winmo phone too quickly.
I have a grandfathered plan with telus that gives me unlimited data for 45$ a month. And since I can tether my computer easily with my winmo phone, I'd hate to loose it by switching providers...
If wifi isn't an option because it drains your battery, then the same can be said for bluetooth -- it also drains your battery.
Well,
When I'm tethering using wmwifirouter, my phone runs hot and dies after about 1 hour.
When I tether using bluetooth, my phone stays cool and this can go on for much longer...
So,
I got in touch with the creator of Tether Blu and he tried to cook something up for me. But for lack of time, he had to stop working on it.
It is two folds : a compiled pand for android, and a small script that runs pand and associates it with my windows mobile based bluetooth access point.
A working network is established between the two devices using the bluetooth link, the android phone can even reach the internet using this link. However, somehow, DNS queries do not get relayed, so I can only reach websites or devices using their numeric IP addresses. Also, most applications that use a data connection to the internet check before doing their stuff if a working link is there by querying android about the status of either the cellular data link, or the wifi connection. These applications fail to pass this check because they do not recognize the bluetooth link as a valid link, even though the link works. Remote (a RDP client) is such an app, where even if you try to reach a machine using it's ip address, you can't because the application thinks it is not connected to a network.
So, does anyone know how to correctly assign working DNS entries to Android?
Also, does anyone know how to flag the data link or the wifi link as being "UP" even though they are not really up? This looks like a good way to have all these applications that check whether or not a data link exists to still work using the bluetooth tether.
Here is the code of tether.sh :
Code:
#!/system/bin/sh
MACADDRESS="00:17:83:0F:0F:C7"
apath=""
tpath=""
IFS="/"
for i in $0
do
apath="$tpath"
tpath="${tpath}${i}/"
done
IFS="|"
pand_pidfile=${apath}pand.pid
PAND_PID=0
if [ -e $pand_pidfile ]; then
PAND_PID=`cat $pand_pidfile`
if [ "x" = "x$PAND_PID" ]; then
PAND_PID=0
else
if ! (ps | grep ${apath}pand | grep -v grep > /dev/null); then
PAND_PID=0
fi
fi
fi
logfile=${apath}tether-log
case "$1" in
start)
if [ 0 -eq $PAND_PID ]; then
echo "Starting pand"
rm $pand_pidfile > /dev/null 2>&1
PAND_PID=0
rm $logfile > /dev/null 2>&1 # if it exists
${apath}pand --role PANU --connect $MACADDRESS -n --pidfile $pand_pidfile || exit
sleep 1
ifconfig bnep0 up
sleep 2
netcfg bnep0 dhcp
fi
echo "Success"
;;
stop)
if [ 0 -ne $PAND_PID ]; then
echo "Killing pand at pid $PAND_PID"
ifconfig bnep0 down
${apath}pand -K || exit
kill $PAND_PID || exit
rm $pand_pidfile > /dev/null 2>&1 # Looks like pand may have removed it for us
sleep 1
fi
echo "Success"
;;
*)
echo "Usage: ${apath}tether.sh {start|stop}"
exit 1
;;
esac
exit 0
Attached to this post is a zip file containing two files : tether.sh and pand. Put the two files in this location on your android phone:
/data/local/
then chmod 777 the two files, these commands (as su) on the android phone will do it for you:
chmod 777 /data/local/pand
chmod 777 /data/local/tether.sh
then to test it out, start tethering on your win mobile phone, turn bluetooth on your android device, wait a little bit and then run this command as su on the android phone:
/data/local/tether.sh start
I have to do a ./tether.sh start on my phone.
You will have to edit the tether.sh file so that the mac address of your bluetooth accesspoint matches the one in the script.
Thanks!
stanelie said:
So,
I got in touch with the creator of Tether Blu and he tried to cook something up for me. But for lack of time, he had to stop working on it.
It is two folds : a compiled pand for android, and a small script that runs pand and associates it with my windows mobile based bluetooth access point.
Click to expand...
Click to collapse
Thanks for the script. I was able to make my Acer Liquid A1 android phone to access internet via my laptop with bluetooth. You can set dns using the following code, just add it after dhcp.
Code:
for i in 1 2; do
dns=`getprop net.bnep0.dns$i`
if [ x"$dns" != "x" ]; then
setprop net.dns$i $dns
fi
done
But still, need to find a way to flag the network as "UP".
Rudeness and unhelpfulness seems to be the norm around here. But, many months on, there remains no easy solution for this problem, despite the "help" offered below. (Please, lbcoder, do try and behave online as you would face to face.)
I too would like a REVERSE BLUETOOTH TETHER app for Android, preferably at the Android Market.
Paul
lbcoder said:
How about this: cancel the wimo cdma crapola and throw it at a bus. Be sure that it gets crushed into tiny bits, then sweep it into a pile and piss on it. Now go to tmobile or att and sign up for some data plan.
If you really insist on doing things the retarded way and tethering a phone through a phone, there is no coding required. You just need to read up on pppd linux bluetooth tethering for how to actually do it.
Click to expand...
Click to collapse
I'm also seeking a resolution to this issue - see the latest posts on this thread:
forum.xda-developers.com/showthread.php?p=8236341#post8236341
Basically I have managed to establish connectivity via a bluetooth PAN, but because a lot of apps use the android ConnectivityService, they cannot get online as the ConnectivityService still believes there is no connectivity.
As we don't have a Droid forum here yet, or anything for Android 2.0 AFAIK, this seemed like the best place to start the conversation. Feel free to move it, if there is a better place, but the question is specifically on networking and how two different phone OSs handle it.
If you don't know what an ad-hoc network is, I'll summarize by saying that, in my lexicon, it is a way for wireless devices to form connections with each other, allowing any Internet connection on the network to be shared by all. A more precise definition is here: http://en.wikipedia.org/wiki/Mobile_ad_hoc_network See also "mesh network" and "Wifi Tethering".
So.. I am considering upgrading my Titan to a Droid. Frankly, the main thing that is keeping me from doing this is that I can't give up WMWiFiRouter. WMWiFiRouter sets up an adhoc wifi network with (or without) security, thus sharing my 3g connection with all I give my network key to.
After finding & buying this program, I was able to drop my $60/mo (or w/e) EVDO card account. So. it is worth it to stay on a Titan till I am sure my phone can be used to connect my laptop/netbook/wife's ipod to the Internet while I am out of my house. I work from home so if I don't have portable wifi access I go stir crazy after a few weeks. I hear "Wifi Tethering" is going to become a product for VZW, but we all know that means it could be a year or three away. Can you all help me decide if upgrading to a Droid is possible. Do any of you have any experience with ad-hoc networking on a Droid?
Here's what I've found so far:
It's possible to have a G1 access an ad hoc network if you "root" your phone and change ini settings to allow it. (Also assign a permanent IP address to all adhoc network members). See: http://modmygphone.com/forums/showthread.php?t=22681
I do not know if this works on Android 2.0. I do not know if Verizon has put something in place to block this. Does anyone have any experience in this area or have a Droid that they can test with?
Your help would be appreciated!
Additional info I've found:
"Rooting" is not yet possible on a Droid. Eliminating the fix mentioned above.
http://droidie.com/2009/11/10/can-android-tether-today-for-0-extra/#comment-121
PDANet is a program that allows USB and bluetooth tethering on all "recently released Motorola and HTC [Android] phones" kkww
For those following along, this is the most promising thread I've found on rooting the Droid.. http://www.alldroid.org/viewtopic.php?f=210&t=431&start=280 This link starts you around page 29, which will be near the end for a little while...
I'm really beginning to wonder if I shouldn't just stick to a touch pro2 since I have a slick setup atm and google maps will release turn by turn voice to all in due time.
The problem is that I want to play!!! and android is calling me..
Have you made any progress on getting a Droid to recognize the WMWifiRouter network? I have a Droid with the router program running on a HTC TP2...there's an app called Hidden SSID Enabler which should resolve thi problem but I haven't been able to figure out what the SSID # is for the TP2...any thoughts?
Bump. Similar situation for me. I run WMWifiRouter on my Sprint Touch Pro and use it several hours a day. I'm ready to switch to a newer phone but want to make sure I can set it up as a ad hoc wifi spot. I'm torn between the Droid and the Nexus One but doubt T-Mobile's network is robust enough for what I need so at least for now, the Droid is the front-runner (I'll believe the N1 will work on Verizon when I see it -- could be 6 months or more).
Any update? Thanks!
I contacted the support folks over at WMWifiRouter and got this reply:
Our apologies for not getting back to you sooner.
Indeed, Android devices by default cannot connect to ad-hoc networks. A rather silly restriction, as the
device is more than capable to use these networks - Google just didn't build it into the interface.
Note that an ad-hoc network and a Hidden SSID are two unrelated things.
Unfortunately, there is no way around this issue unless your device is rooted. In that case we still cannot
tell you which commands to execute to be able to connect, but we know it is possible if you have root.
Kinds regards,
WMWifiRouter Customer Support
In looking through the "rooting" thread above it seemed way too complicated for me to attempt...if anyone can post or direct me to an "idiot's guide" tutorial for rooting a Droid I'd be most appreciative.
Hey guys, rooting for the droid is here already, some info can be found here
"i cannot post outside links..."
so what happends after you root your droid?
Bump, and I've found this thread:
code.google.com/p/android/issues/detail?id=82
about the official development of this feature, and I saw, although there are tricks that works for the G1 and the older phones, it is not working for the droid or those newer ones.
Hi
I have found the solution. I am using Ubuntu 10.04 and Using superfroyo2.2 on my HTC dream. I can connect to wifi adhoc network of my PC and enjoying internet on it.
I have attached the zip file. Please extract the file to get tiwlan.ini and wpa_supplicant.conf file. Replace your mobile's file with these ones and enjoy ad-hoc wifi.
You can use below commands, with mobile connected to PC via usb to replace the files:
adb shell
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# exit
> adb push tiwlan.ini /system/etc/wifi/tiwlan.ini
> adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
> adb shell
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
# exit
I was using ubuntu bash and I placed both files in the tools folder of SDK. and then I ran the commands from that directory so that no path issues arise.
One more thing, You should create adhoc wireless with SSID iBM and leave it open without security key.
Hey, all apologies if it DOES work, since I havent tried it yet, but when I view the tiwlan.ini file you've included in the zip file, it still says wifiadhoc=0
the .conf file IS setup to use your SSID name if iBM like you were saying though...
so I THINK you might have included the wrong file... but hell, I've been wrong before... I screwed up my wifi messing with this, so I'm just gonna try your files anyway, since they'll probably at least set me back to where I was...
adol
OKAY, so I guess I've gotta apologize- I just tried it, and danged if your files didn't work like a charm... so, my next question is; how did they work, when wifiadhoc=0?
Am I somehow seeing the contents of the file incorrectly, or is it something along the lines of you having set up a static ip or something? I'm gonna look into it a bit, which I haven't done yet, so if either of the things I just said made no sense, just disregard them and go ahead with the explanation...
Anyways, thanks for posting those files; I was starting to get rather frustrated with my inability to get this stupid crap to work.
adol
ok a few quick questions
has any one tested this on a sprint epic
is there a 1 click install for this pack
ive got some skill but this is defiantly out of my range
thanks
installing cyanogen mod 7 should resolve your problem...
guys y to roor the phone?install cyanogen 7 etc??
i think only some expert guys(i.e who can deal the problems their on without any suggestions) can deal with such kind of thngs...insted if we creat a virtyal access point,,thats better i think..
try using mhotspot...
Wifi Connection shared as a Wifi Router...see this thread...
Indeed CM7 does solve ad hoc networking problems. I've yet to find a suitable solution on froyo, although google gave me plenty of stuff to try.
cm7 ?
I have CM7.1 running but I still cant see any ad-hoc wifi networks!
I tried replacing the tiwlan and wpa_*.conf files but that just messed up my wifi worse.
jumblies said:
Indeed CM7 does solve ad hoc networking problems. I've yet to find a suitable solution on froyo, although google gave me plenty of stuff to try.
Click to expand...
Click to collapse
I am on 1.5.7 AT&T Atrix unlocked and rooted on Fido network in Canada.
With Fido if you have data plan over 1GB, you are free to tether. However, when I try to turn on mobile hotspot, it says "validating Wi-Fi hotspot" and then gives me a notification: "Account not set up for WI-FI hotspot, to enable, go to att.com.mywireless"
What should I do to enable this on my phone?
Edit Build.prop I believe
Sent From My Gibgerblurred Phone
Well the phone is an unlocked AT&T phone so it wasn't meant for a Canadian Cell company. But go download Barnacle WiFi Tether. It works the same way the only difference is that the Hotspot has WAP2 and the Barnacle only has WAP. But it really doesn't matter since it is short-range signals
I had that problem.. repeatedly restarting my phone and turning wifi on/off got it to work.. also mine doesn't seem to start when near heaps of other wifi enabled devices such as 2 laptops and an iPhone 4. took it away to the other side of the room and it started almost instantly.. could be coincidence
sipjca said:
Edit Build.prop I believe
Sent From My Gibgerblurred Phone
Click to expand...
Click to collapse
could you please elaborate?
If you open the build.prop file.in notepad++ there is a section for wifi tether it is set to 0 if you change it to 1 it should enable I will try today
Sent From My Gibgerblurred Phone
HungryEel said:
I am on 1.5.7 AT&T Atrix unlocked and rooted on Fido network in Canada.
With Fido if you have data plan over 1GB, you are free to tether. However, when I try to turn on mobile hotspot, it says "validating Wi-Fi hotspot" and then gives me a notification: "Account not set up for WI-FI hotspot, to enable, go to att.com.mywireless"
What should I do to enable this on my phone?
Click to expand...
Click to collapse
I've got atrix 1.57 ulocked but not rooted yet-- on rogers- still checking to see how to use hotspot.
I can tether with Easytether.....
will keep trying.. not sure I want to go back to 1.26 to root it - waiting for better solution for now.
Will keep monitoring and post whatever I come up with.
sipjca said:
If you open the build.prop file.in notepad++ there is a section for wifi tether it is set to 0 if you change it to 1 it should enable I will try today
Sent From My Gibgerblurred Phone
Click to expand...
Click to collapse
What directory on the phone is that in?
I assume I just open the file to edit it when attached with USB?
Thanks
You have to have root... I have a modded build.prop file already ill post it then u push onto phone using adb.
Sent From My Gibgerblurred Phone
But I need to root first?
EDIT: I may be wrong... Heres the Build.Prop
http://goo.gl/L7Hjp
hello, could you post tell me the directory on my phone that has the file?
It will be ok to "cp original internetlsd/original" "mv original original.bak"
then download the original to my computer from internal SD, edit in notepad then put the edited back to where the original was?
I googled around to find out where the build.prop was
here is my settings for wifi (which is identical to the one you posted)
#For enabling Wispr Feature
ro.mot.wifi.hotspot=1
# To enable Google Froyo Tethering (USB & WIFI hotspot)
ro.tether.denied=false
so shouldn't my tether work if denied = false?
I was also reading an article about build.prop apparently you can fake things with it like android version #, which makes me think this file just stores variable to display?
have you made sure to add "default,tether" without the quotation marks as the APN type for your Fido APN?
also, due do a bug, you must have Wi-Fi on before you enable tethering, otherwise it will just hang.
so Turn Wi-Fi On THEN turn on mobile hotspot.
Ok I feel so stupid now... adding ,tether after default made it work
Sent from my MB860 using XDA App
Hi, i'm also interested in this.
Could you please tell what is the procedure to enbale this?
I'm on a french network.
Is anyone else having tethering issues on MetroPCS or Tmobile with the MXP? I have tried applying various apn tweaks but I always experience DNS issues on the tethered devices. My device is bootloader unlocked and rooted if that even matters.
jovan123 said:
Is anyone else having tethering issues on MetroPCS or Tmobile with the MXP? I have tried applying various apn tweaks but I always experience DNS issues on the tethered devices. My device is bootloader unlocked and rooted if that even matters.
Click to expand...
Click to collapse
I am in the same situation and it sucks not being able to tether on metroPCS specially since my service plan of $60 offers free mobile hotspot up to 6GB to teher. The phone has potential but in the end I might have to return it if no tethering options are available.
Not even with root ? Just wondering
Sent from my XT1575 using Tapatalk
patt2k said:
Not even with root ? Just wondering
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Not even with Root and Bootloader unlocked.
That sucks maybe metro is blocking it somehow ?
Sent from my XT1575 using Tapatalk
Have you tried going to the store to get their information on this? I'm about to get this phone on t-mobile amd I hope this can be fixed, did you buy the phone at motorolas site? Because I seen the option to add your carrier sim with the phone if that even makes a difference as im assuming it doesn't, but maybe it has something to do with the imei not being registered to the network so I think you should stop by a store
I have not had any issues tethering with T-Mobile. Not rooted and bootloader is virgin locked.
Sent from my Nexus 10 using Tapatalk
Are you getting an error when turning on Hotspot, or just when a device connects it cant hit the internet. Its 2 different issues, but both are fixable.
Fix for Tethering
InfiniDroid said:
I am in the same situation and it sucks not being able to tether on metroPCS specially since my service plan of $60 offers free mobile hotspot up to 6GB to teher. The phone has potential but in the end I might have to return it if no tethering options are available.
Click to expand...
Click to collapse
Had to dig deep in the adb logcat to find the issue, the problem is DNS routing when using tethering . For tethering to work I had to use Wifi Tether Router.
Change the following for tethering to work:
Interface: wlan0
Method: Native tether
DHCP Settings : DNS Redirect checked
Redirect DNS to 8.8.8.8 and 8.8.8.4
SalTNutz said:
Are you getting an error when turning on Hotspot, or just when a device connects it cant hit the internet. Its 2 different issues, but both are fixable.
Click to expand...
Click to collapse
No problem on turning on Hotspot, other devices connect but no Internet connection. Hopefully some Devs show interest in MXP and pump out a fix or maybe even some ROM's.
Sent from my XT1575 using Tapatalk
InfiniDroid said:
No problem on turning on Hotspot, other devices connect but no Internet connection. Hopefully some Devs show interest in MXP and pump out a fix or maybe even some ROM's.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Also you may need to change your APN to use IPv4 and not IPv6.
The issue is the hidden tethering APN. T-Mobile is the only one that does this that I know of.
http://forum.xda-developers.com/showthread.php?t=1962752
jovan123 said:
Had to dig deep in the adb logcat to find the issue, the problem is DNS routing when using tethering . For tethering to work I had to use Wifi Tether Router.
Change the following for tethering to work:
Interface: wlan0
Method: Native tether
DHCP Settings : DNS Redirect checked
Redirect DNS to 8.8.8.8 and 8.8.8.4
Click to expand...
Click to collapse
@jovan123 Thanks for your help. I bought the Wifi Tether Router from the play store and followed your instructions at first it didn't work but I went over it a second time and shazam! right on the money.
InfiniDroid said:
@jovan123 Thanks for your help. I bought the Wifi Tether Router from the play store and followed your instructions at first it didn't work but I went over it a second time and shazam! right on the money.
Click to expand...
Click to collapse
No problem man. Can you let me know if your tether data is showing up in your data usage. Mine doesnt show up at all , maybe since its bypassing tmobile's DNS servers.
In case this helps any Metro PCS (who else does Hotspot for free?? Nice). I was so upset that I couldn't hotspot that I rooted and tried the WiFi Tether Router app and settings above (had used before on Sprint with success). Nothing worked.. I uninstalled and tried a few simpler things: I just modified the APN by adding 'dun' to the APN type line, and changed APN protocol to IPv4. Works great at LTE speeds. I don't think using then deleting WiFi Tether Router left some beneficial settings somewhere deeper; anyone know?
I have the same issue. A reboot fixes it for a short time only. I posted this on Moto forum and other people have having an issue. I know it's the phone because I put the sim back to my OPO and I can tether fine with it. I call t-mobile to verify that Hotspot feature is turn on. It's very annoying having to reboot again and again to use hotspot.
MetroPCS blocks ALL tethering for non-MetroPCS devices. That said, I have been tethering with MetroPCS since Day 1 using this guide:
http://pocketnow.com/2015/01/01/nexus-6-tethering
Summary:
Add tether_dun_required=0 to /data/data/com.android.providers.settings/databases/settings.db using a SQL Editor.
Change APN to IPv4
jovan123 said:
No problem man. Can you let me know if your tether data is showing up in your data usage. Mine doesnt show up at all , maybe since its bypassing tmobile's DNS servers.
Click to expand...
Click to collapse
I use the app but my WiFi is messed up after I turn off the tether. Have to reboot to resolve issue.
same problem here,i use simple mobile and computer connect to wifi but data is not transfering,i found that happens when lte when i have h+ or 2g tether ok...anybody know how to fix this ,i have no problem with asus zenfone 2
with 3 different roms, all I've needed to get fast LTE tethering is basically using IPv4 and adding 'dun'...
(all others "Not set")...
APN: fast.metropcs.com
MMSC: http://metropcs.mmsmvno.com/mms/wapenc
MMC: 310
MNC: 260
APN type: default,supl,mms,dun
APN protocol: IPv4
APN roaming protocol: IPv4
Has anyone been able to successfully hide their hotspot usage from t mobile?
That situation must really suck. It's your data plan, should be your choice to use however is most suitable and convenient for you.
I'm on Tesco Mobile UK. Its a MVNO using o2 as the carrier network. Heres a quote from Tesco Mobile website:
Some phones and tablets allow you to set-up a ‘Wi-Fi hotspot’ (also referred to as 'tethering') to share your data connection with other devices such as a laptop.
If your tariff has a data allowance included, you can use your device as a personal hotspot at no extra cost. If you don't have a data allowance, or you go over your data allowance, you’ll be charged our standard rates.
Obviously I'm happy not having the same inconvenience as you do.
There's quite a few more in the UK that allow tethering:
http://kenstechtips.com/index.php/tethering-on-uk-networks
Still_living714 said:
Has anyone been able to successfully hide their hotspot usage from t mobile?
Click to expand...
Click to collapse
Well for my Nexus 6 I use the build prop edit trick
net.tethering.noprovisioning=true
but maybe can give a try? look this post above for V10
https://forum.xda-developers.com/tm...imited-tethering-lg-v10-tmobile-h901-t3471225
There is a way to hide tethering data. I assume you have an unlimited data plan, as this does not hide total data consumed by your device, nor does it prevent data throttling during peak hours if you go over 30GB.
So far, carriers detect tethering data by monitoring the TTL headers in outgoing TCP/IP packets from your phone. TTL stands for Time To Live. Every time a packet goes through a router, the TTL drops by 1. If TTL drops to 0, the packet is dropped. Operating Systems have default TTL values; Android is 64. When you tether a device, your phone acts like a router. So lets say you are tethering an Android tablet. Your carrier will see data coming from your phone having 2 different TTL values, one 64 and the other 63 (64-1 for the jump through your phone aka the router). Since the carrier knows the default TTL is 64, they tally all data that doesn't match it as being used for tethering.
First, your device needs to be rooted. Then install the Kali Nethunter kernel (NetHunter build itself should be optional). That kernel has the necessary modules for iptables, which is what you will need. Open a terminal and enter the commands
su
iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64
This will change TTL for ALL outgoing packets from your phone to 64, even those from tethered devices. The command will not persist on reboot though, so I recommend making a startup script.
Hope this helps!
LvDisturbed1 said:
There is a way to hide tethering data. I assume you have an unlimited data plan, as this does not hide total data consumed by your device, nor does it prevent data throttling during peak hours if you go over 30GB.
So far, carriers detect tethering data by monitoring the TTL headers in outgoing TCP/IP packets from your phone. TTL stands for Time To Live. Every time a packet goes through a router, the TTL drops by 1. If TTL drops to 0, the packet is dropped. Operating Systems have default TTL values; Android is 64. When you tether a device, your phone acts like a router. So lets say you are tethering an Android tablet. Your carrier will see data coming from your phone having 2 different TTL values, one 64 and the other 63 (64-1 for the jump through your phone aka the router). Since the carrier knows the default TTL is 64, they tally all data that doesn't match it as being used for tethering.
First, your device needs to be rooted. Then install the Kali Nethunter kernel (NetHunter build itself should be optional). That kernel has the necessary modules for iptables, which is what you will need. Open a terminal and enter the commands
su
iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64
This will change TTL for ALL outgoing packets from your phone to 64, even those from tethered devices. The command will not persist on reboot though, so I recommend making a startup script.
Hope this helps!
Click to expand...
Click to collapse
Yes I read this before but I mostly do WiFi Hotspot. I've read a ton of forums only to come to the conclusion that you cannot beat t mobile at hiding your usage anymore. If Maybe you have another method please share,thanks.
Still_living714 said:
Yes I read this before but I mostly do WiFi Hotspot. I've read a ton of forums only to come to the conclusion that you cannot beat t mobile at hiding your usage anymore. If Maybe you have another method please share,thanks.
Click to expand...
Click to collapse
This method works regardless if you are tethering though WiFi or USB. Either way, the phone is acting as the router, and packet headers leaving the phone will show a TTL of 64.
I have used this method to download games on my Xbox One, torrent stuff on my laptop, stream media to my tablet and more. Hell, I hit over 250GB one month. I can hit DL speeds over 110mb/s at home through LTE. I use USB tether when I can, as the data transfer rate is much better than WiFi tether.
Take the plunge and give it a go. I'm telling you, it works!
LvDisturbed1 said:
This method works regardless if you are tethering though WiFi or USB. Either way, the phone is acting as the router, and packet headers leaving the phone will show a TTL of 64.
I have used this method to download games on my Xbox One, torrent stuff on my laptop, stream media to my tablet and more. Hell, I hit over 250GB one month. I can hit DL speeds over 110mb/s at home through LTE. I use USB tether when I can, as the data transfer rate is much better than WiFi tether.
Take the plunge and give it a go. I'm telling you, it works!
Click to expand...
Click to collapse
Can I do this without the kernel you said? Running Albatross and would like to keep it.
Still_living714 said:
Can I do this without the kernel you said? Running Albatross and would like to keep it.
Click to expand...
Click to collapse
I am not sure off the top of my head. Most likely no, but I would have to look at the source code for it to be sure. It may be possible for the maintainer to add the necessary modules to get iptables working properly. What version of Albatross are you using? Stock or custom?
LvDisturbed1 said:
I am not sure off the top of my head. Most likely no, but I would have to look at the source code for it to be sure. It may be possible for the maintainer to add the necessary modules to get iptables working properly. What version of Albatross are you using? Stock or custom?
Click to expand...
Click to collapse
Stock running megarom on h918
Still_living714 said:
Stock running megarom on h918
Click to expand...
Click to collapse
I checked the source, looks like it is a no go. You can try asking @USA-RedDragon to set CONFIG_NETFILTER_XT_TARGET_HL=y in his defconfig. It is currently not set. That should do the trick.
LvDisturbed1 said:
There is a way to hide tethering data. I assume you have an unlimited data plan, as this does not hide total data consumed by your device, nor does it prevent data throttling during peak hours if you go over 30GB.
So far, carriers detect tethering data by monitoring the TTL headers in outgoing TCP/IP packets from your phone. TTL stands for Time To Live. Every time a packet goes through a router, the TTL drops by 1. If TTL drops to 0, the packet is dropped. Operating Systems have default TTL values; Android is 64. When you tether a device, your phone acts like a router. So lets say you are tethering an Android tablet. Your carrier will see data coming from your phone having 2 different TTL values, one 64 and the other 63 (64-1 for the jump through your phone aka the router). Since the carrier knows the default TTL is 64, they tally all data that doesn't match it as being used for tethering.
First, your device needs to be rooted. Then install the Kali Nethunter kernel (NetHunter build itself should be optional). That kernel has the necessary modules for iptables, which is what you will need. Open a terminal and enter the commands
su
iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64
This will change TTL for ALL outgoing packets from your phone to 64, even those from tethered devices. The command will not persist on reboot though, so I recommend making a startup script.
Hope this helps!
Click to expand...
Click to collapse
Did you make a script? maybe can share???
Mervingio said:
Did you make a script? maybe can share???
Click to expand...
Click to collapse
Awhile back, and I had to research a bit on how to do it on Android. Of course my memory on it now is a bit fuzzy. I think you just put it in /data/local/userinit.d/
Edit: Try Script Manager in the Play Store. It says you can make a script and set it to run on boot .
Edit 2: Found an app made by some Russians on github. It has English language option and can set TTL using IP tables either manually, or on boot. Does some other blacklist things, but I think they apply to carriers from Russia, so don't think it will affect anything.
Sorry for the double post, but I couldn't add a file through edit.
LvDisturbed1 said:
Sorry for the double post, but I couldn't add a file through edit.
Click to expand...
Click to collapse
Nice I will try it Thanks
Kernel Adiutor have one too
I made some tests.. and I have a question:
if without root and on a stock firmware I tether using USB and I set a ttl of 65 on my pc, everything works (65 becose 64 on the phone)...
But If I do the same using wifi tether, this does not work and I have to use other methods.
Does anybody know why?