Is there a way to change your Wi-Fi Nexus One name - Nexus One Q&A, Help & Troubleshooting

I tried a few searches in this forum and came up empty...but is there a way to change the name that the N1 identifies itself as to your Wi-Fi network? E.g. "Randy's Nexus One" or something like that?
Thanks in advance,
Randy

Yes go to portable hot spot setting then go to configure then advanced and you can change it to whatever u like
-------------------------------------
Sent via the XDA Tapatalk App

We're probably using different Nexus Ones, because on mine there is no "portable hot spot" settings. FroYo? Please elaborate.
For Eclair there's no easy way. I did something like this some time ago:
http://forum.xda-developers.com/showthread.php?p=6261359#post6261359
I hope FroYo added the option to do it easily...

jdmoore81 said:
Yes go to portable hot spot setting then go to configure then advanced and you can change it to whatever u like
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I don't think OP's talking about the N1 as a portable hotspot... rather the device id/name a wireless router picks up when the N1 connects to the router...

I think OP is asking if it's possible to change the DHCP name of the phone

I'd like to know how to change my phone's hostname too.

Well, there are 2 ways to change the phone hostname... but both require root...
1. init.rc way
in init.rc, look for
Code:
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
changing hostname to you desired name will change the phone hostname. So you change would look something like this...
Code:
on boot
# basic network init
ifup lo
hostname CRAiG
domainname localdomain
But this process involves building a boot.img with the new init.rc and flashing that boot.img
2. Using an init script in a mod like CM
As in a regular linux system, the following line will allow you to change you hostname without flashing a boot.img
Code:
echo CRAiG > /proc/sys/kernel/hostname
In CM, you can add this line to an init.d script like 01sysctl or 20userinit in /system/etc/init.d
And yeah, this changes the device name on your router, but you might have to delete the existing DHCP lease...

craigacgomez said:
Well, there are 2 ways to change the phone hostname... ...
In CM, you add this line to an init.d script like 01sysctl or 20userinit in /system/etc/init.d
And yeah, this changes the device name on your router, but you might have to delete the existing DHCP lease...
Click to expand...
Click to collapse
It shows that you didn't try it. You can't put it before 04 script, since the services aren't up yet, and it won't change a thing. It has to be after 05 - that's why it's best done through 20userinit or the script that it calls.

To clarify my question...
No, not using N1 as a hotspot, but how my wi-fi router sees my n1 while my N1 is a wi-fi client to it.
Randy

Jack_R1 said:
It shows that you didn't try it. You can't put it before 04 script, since the services aren't up yet, and it won't change a thing. It has to be after 05 - that's why it's best done through 20userinit or the script that it calls.
Click to expand...
Click to collapse
I did try it and I have it working with the change in 01sysctl... and you don't need services up and running to change ur hostname!!!!!
@rmagruder... what I said above with allow you to change how ur wifi router see ur n1

Hostname is for network interface. At least one (localhost) needs to be started for it to work. If there is any additional interface starting - it can change the settings during initialization, which is what's probably happening, at least on my Nexus w/ CM5.0.6. Tested with 01sysctl and it fails, as I wrote in the thread I linked above.

Related

[Q] Custom DNS setting for 3G/WiFi

Is it possible to set DNS settings? I'd like to use Google DNS or OpenDNS instead of my providers DNS.
I am also looking for an answer to this.. You should have posted in q & a section though.
Sent from my GT-I9000 using XDA App
I was also wondering this...
I know you can definitely do it on Wifi by going into the Advanced setup of Wifi networks under Settings -> Wireless & Network -> Wi-fi settings -> Select Left selection button and then selecting Advanced.
Can't find it in the APN area though, so not sure how to do it for the cellular connection.
I also would like to know this..
count me in, i've been wanting to do that for a while.
i prefer openDNS
Hi all,
I also have been in this search and somewhere in the forums I have read that it is only possible to set this preference via setprop command. However this setting is lost in a reset and can not be modified permanently.
People were swearing to Google for hiding this option.
Regards.
aegeuss said:
Hi all,
I also have been in this search and somewhere in the forums I have read that it is only possible to set this preference via setprop command. However this setting is lost in a reset and can not be modified permanently.
People were swearing to Google for hiding this option.
Regards.
Click to expand...
Click to collapse
I've found these but I have no idea how to make use of it:
1:
* Android using OS (eg, Linux) network directly, but handle DNS directly.
* DNS lookup order follows
1. /system/etc/hosts lookup
2. system_property [net.eth0.dns1]
* system_property is provided android init process using unix domain socket @property_service
* You should run "init" process for network management.
* You should set up DNS 'net.eth0.dns1' using "/system/bin/setprop", "/etc/default.prop", "/data/local.prob"
2:
Force use of Orange DNS in the ip-up script located in /system/etc/ppp :
/system/bin/setprop "net.gprs.dns1" "194.051.003.056"

[Q] Naming the nook device / hostname?

Does anybody know how to change the name of the Nook Color? In order to use an application in Citrix, it needs to have a specific name, and I can't figure out how to change it.
I've seen various ideas, such as:
http://forum.xda-developers.com/showthread.php?t=668300
which says to change the /proc/sys/kernel/hostname
I've done so, but disconnecting and reconnecting the wifi with the desired name for the NC in the above file does not work; the name stays the same. For me, the name is ROID7047BCFB-EB96-44.
How does the android/linux OS figure out a name for the NC, and how can I change it?
Thanks in advance for any help.
Update:
pinging ROID7047BCFB-EB96-44 works, as does pinging NEWHOSTNAME (what I want my NC to be called), both give the same IP address. However, my Citrix receiver still recognizes me as ROID* and boots me off.
Maybe this is some kind of DNS issue, or how do I get rid of the ROID* name and get my device to be recognized only by NEWHOSTNAME?
I suppose I can ask the Citrix/I.T. administrators to give me access on my NC (which they probably won't support doing), or I can rename my NC to something that already has access in Citrix.
It really shouldn't be that hard to name your NC, as you can any computing device.
Do I have to go into userinit.sh to set localhost to NEWHOSTNAME, or edit the init.rc file, or edit the .IMG on the ROM (it's been a while since I played around with unix, and so I'm pretty new to this stuff)?
Nook Color Device ID / Hostname
Didn't want to start a new thread on this topic...
Our network admin sees unknown devices as a security threat (or annoyance) to his network. He therefore requires a unique hostname to obtain a DHCP lease.
A hostname of "localhost" (the NC default), is seen as blank by the server. The Nook Color (and many other Android devices) must be rooted and modified to gain access.
Several posts recommend changing net.hostname. This did not work for me. Changing /proc/sys/kernel/hostname, however, would work.
For a single instance, use the following from a root prompt. THEN TURN OFF AND TURN ON WIFI to request a new DHCP lease.
# echo NEWHOSTNAME > /proc/sys/kernel/hostname
EDIT: Removed paragraph about setting at boot until I figure it out.
To set HOSTNAME / Device ID at boot
Thanks to JoshMiers for instructions on persistent settings following a reboot...
http://forum.xda-developers.com/showthread.php?t=901791
To set the HOSTNAME at boot (on rooted stock eclair, anyway)...
1. Create (via adb or RootExplorer) file /data/boot_complete_hook.sh
2. Add the following lines via a text editor (on Windows use Notepad++):
Code:
#!/system/bin/sh
#
## Set hostname/deviceID
#
echo yourchosenhostname > /proc/sys/kernel/hostname
3. At root prompt, change properties of new file
Code:
#chmod 755 /data/boot_complete_hook.sh
At root prompt, test to see if it works by executing
Code:
#/data/boot_complete_hook.sh
#cat /proc/sys/kernel/hostname
I did not need to reset the wireless after booting. If necessary, code could be added to the file to renew the DHCP lease or reset the wireless (tiwlan0).
I did have difficulty using ADB to do this, as Josh describes, and did not take time to debug. Instead, I used RootExplorer and Terminal to do it all directly on the NC.
KBMN said:
Does anybody know how to change the name of the Nook Color? In order to use an application in Citrix, it needs to have a specific name, and I can't figure out how to change it.
how about this?
http://forum.xda-developers.com/showthread.php?p=17287446#post17287446
Click to expand...
Click to collapse
Well, I can use the setprop net.hostname command to set the device hostname. However, the Citrix application takes the "clientname" from the android_id field in /data/data/com.android.providers.settings/databases/settings.db, regardless of the hostname. So, the Citrix application sees the device as "ROID"+android_id. I can't figure out how to get rid of the "ROID" part so I can make the device "clientname" to show as whatever is desired (after changing the android_id). Tried to put in a backspace character in the field, as "\b" to get rid of the "ROID" part, but that didn't work. Oh well.

[MOD] Enabling tethering without paying for apps

Blatantly ripped off from richhed's thread. I'm a cheap [email protected]$#^&* so I wanted to enable wifi hotspot without paying for apps. Here's how.
I'm writing these instructions for Win7 x64, and assuming that your USB drivers and busybox are working. YMMV. No, I won't help you fix your phone if you brick it, and won't be responsible if it doesn't work for you.
1. Download Superoneclick 1.6.5 for rooting your phone. Your phone needs to be rooted, if you haven't done this yet you need to do it now.
2. Download SQLite database browser on your PC and unzip to some folder. Remember where this is.
3. Plug phone into PC and turn airplane mode on.
4. Open a command prompt as administrator (right-click, open as administrator)
5. Navigate in the command prompt to where your Superoneclick is unzipped (for me, it's in a folder on my desktop)
6. Run 'adb shell'
** note** all commands from step 7 to step 12 are in the ADB shell
7. su (if you rooted in step 1, you may have to allow access, watch your phone as it may ask)
8. mv /data/data/com.android.providers.telephony/databases/telephony.db /data/data/com.android.providers.telephony/databases/telephony.old
9. chmod 777 /data/data/com.android.providers.telephony/databases
10. chmod 664 /data/data/com.android.providers.telephony/databases/telephony.old
11. exit
12. exit
13. in the same command window which your second 'exit' command dropped you to, type 'adb pull /data/data/com.android.providers.telephony/databases/telephony.old ./telephony.db'
14. Run SQLite database browser and open the telephony.db file that you downloaded to the Superoneclick folder in the last step.
15. Click 'browse data' and select table 'Carriers'
16. You should see a long list of APN settings for various carriers, the ones you are interested in are rows 4, 6, and 7. Highlight row 4, named 'AT&T US HSDPA'. Scroll ALL THE WAY TO THE RIGHT where the title of the last column says "preloaded." Double-click the field that says 'true', and in the resulting dialog box change the "true" to "false" and click "Apply Changes". Repeat this step for rows 6 and 7.
17. Edit the 'type' (3rd last) field of row 6. Right now the field says 'tether'. Double-click and change it so that it says 'default,agps,fota,supl,tether' and apply changes.
18. Change the 'apn' (6th) field in row 6 from 'broadband' to 'wap.cingular' and apply changes.
19. Click 'save' and exit the DB browser.
20. Back in the command window, type 'adb push ./telephony.db /data/data/com.android.providers.telephony/databases/telephony.new'
21. Run 'adb shell'
** note** all commands from step 22 to step 32 are in the ADB shell
22. su
23. cd /data/data/com.android.providers.telephony/databases
24. su radio
25. cp telephony.new telephony.db
26. chmod 660 telephony.db
27. rm telephony.new
28. exit
29. cd ..
30. chmod 771 databases
31. exit
32. exit
33. Disable airplane mode
34. Go to Settings>Wireless + Networks>Mobile Networks>Access Point Names. Select radio button for AT&T Tether.
35. Reboot phone.
36. Mobile Hotspot will still validate but will turn on when using this APN. You might have to switch APN's after a reboot, I've had to and at least one other user has had to.
If you ever want to revert, we saved the file as /data/data/com.android.providers.telephony/databases/telephony.old in step 10. Just 'su' and 'cp' that puppy overtop of the existing telephony.db, remembering of course to enable airplane mode.
Not trying to start anything, but theres already a pretty good thread on this bro.
Sent from my MB860 using Tapatalk
http://code.google.com/p/android-wifi-tether/downloads/list
2.07 works flawless
lsxrx7 said:
http://code.google.com/p/android-wifi-tether/downloads/list
2.07 works flawless
Click to expand...
Click to collapse
for me as well
lsxrx7 said:
http://code.google.com/p/android-wifi-tether/downloads/list
2.07 works flawless
Click to expand...
Click to collapse
is this without modifying the sql db's??
stop linking android-wifi-tether.
Infrastructure AP (what this and richhed's method and others enable) > Adhoc (what android-wifi-tether enables)
Google the differences. Ill give you a couple reasons to start
1) a lot of corporate laptops disable adhoc connections
2) Adhoc only allows WEP - crackable in 30 seconds, a huge security risk. Infrastructure allows WPA2...
so if you dont care about any of those, then yes, android-wifi-tether is fine... and much simpler.
andy2na said:
stop linking android-wifi-tether.
Infrastructure AP (what this and richhed's method and others enable) > Adhoc (what android-wifi-tether enables)
Google the differences. Ill give you a couple reasons to start
1) a lot of corporate laptops disable adhoc connections
2) Adhoc only allows WEP - crackable in 30 seconds, a huge security risk. Infrastructure allows WPA2...
so if you dont care about any of those, then yes, android-wifi-tether is fine... and much simpler.
Click to expand...
Click to collapse
sweet. thanks bro
andy2na said:
stop linking android-wifi-tether.
Infrastructure AP (what this and richhed's method and others enable) > Adhoc (what android-wifi-tether enables)
Google the differences. Ill give you a couple reasons to start
1) a lot of corporate laptops disable adhoc connections
2) Adhoc only allows WEP - crackable in 30 seconds, a huge security risk. Infrastructure allows WPA2...
so if you dont care about any of those, then yes, android-wifi-tether is fine... and much simpler.
Click to expand...
Click to collapse
Number 2 is kinda a mute point as if your using your phone to tether i doubt its going to be your primary connection. Also the fact that your not even going to see your phone after about a 100ft for tethering it would be pretty easy to narrow down someone hacking into your wep
LancerV said:
Number 2 is kinda a mute point as if your using your phone to tether i doubt its going to be your primary connection. Also the fact that your not even going to see your phone after about a 100ft for tethering it would be pretty easy to narrow down someone hacking into your wep
Click to expand...
Click to collapse
Number 2 is pretty important; it only takes about a minute to hack through WEP when the connection is in use.
Yea think you missed it completely
Sent from my MB860 using XDA Premium App
Thanks for this, I will try this out this weekend.
Bakano said:
is this without modifying the sql db's??
Click to expand...
Click to collapse
Yes. I flashed Motorola Atrix 4G U4_1.5.2 last night, restore my apps with mybackuppro this morning and this was the first thing I tried.
Just loaded it. Didnt have to do jack. Changed SSID, changed encryption. Not letting me change password, wanking the 13 character requirement when I enter a 16 character ASCII password is too short.
But the app worked beautifully. I have tried the other methods, modding db's. That didn't work until I added this below.
Tether without at&t tethering plan: (thanks to Fixter)
http://forum.xda-developers.com/show...&postcount=193
after doing this. mobile hotspot is still greyed out in settings. It says 'high speed coverage required'. granted i am on edge with no way to test 3g atm. I am wondering if this is normal and if there is a way to enable the hotspot over edge? (yes i know it would be impractically slow)
Finally got around to doing this and it worked great.
A few corrections to your steps.
Step 3. Plug phone into PC. (I know stupid explanation, but some people may forget.)
Step 15. Select Table 'Carriers'
Step 34. 34. Go to Settings>Wireless + Networks>Mobile Networks>Access Point Names. Select radio button for AT&T Tether.
Finally, I had a ton of APNs listed in my phone. Something like 80. The ATT ones were listed near the bottom. I am not sure if this is because who I purchased my phone from, Walmart, but maybe you should give some description of rows 4,5, and 6 so that people will not get confused. I figured it out fine, but you never know.
Finally, this works in webtop, but it appears that on every reboot of the phone you have to change the APN setting when you first use webtop. It doesnt seem to matter if you are already in tethering, you have toswitch away and then switch back. After you do this once everything works fine until the next reboot.
Thanks again.
andy2na said:
2) Adhoc only allows WEP - crackable in 30 seconds, a huge security risk. Infrastructure allows WPA2...
Click to expand...
Click to collapse
It isn't so much someone could access your wifi tether, but more that the data can be captured and easily decrypted. Anything you do over that connection may as well be broadcast for all to see. (Unless you're using https etc for everything)
I use the android-wifi-tether app on bluetooth only, unfortunately it also sucks battery more than the usb port on my mac can supply so the battery depletes in a few hours.
Thank you to the OP for providing a way to enable the built-in tethering.
krkeegan said:
A few corrections to your steps.
Click to expand...
Click to collapse
Thanks, OP fixed.
Thanks for the step by step
I am not sure if it made any difference to it working, but as I'm with Telstra (Australia) I added 'default,agps,fota,supl,tether' to the entry for "Telstra Internet" and it works perfectly.
Not sure if this has been beaten to death yet, but do we for sure know that AT&T cannot track this? How are connection speeds?
I've read a few posts expressing concerns about AT&T automatically switching people to the tether/4GB plan (I have the 2GB plan), and also slow (<1mbit) download speeds. Can someone shed some light on this?
i think they can tell when we swtich from "phone" to "wap.cingular," it showed a record of me switching between the two. I also looked up my data usage and got 2 reports of usage rather than just one. still my data plan has remained unchanged. this also happened when i would switch out my sim card b/w my windows 7 samsung focus and my dell streak, and att didn't do anything. i figure if they contact me about this i can just say i've been swapping my sim card between phones. don't think they can tell the difference there (may be wrong).

[SOLVED] How do I enable Nexus 7 USB tether on Jelly Bean?

Is there a way compile the JB source so USB tether is enabled?
I made the following modification to frameworks/base/core/res/res/values/config.xml but the Nexus 7 with JB doesn't bring up any USB network interface or show the tethering option in the menu
Code:
<!-- List of regexpressions describing the interface (if any) that represent tetherable
USB interfaces. If the device doesn't want to support tething over USB this should
be empty. An example would be "usb.*" -->
<string-array translatable="false" name="config_tether_usb_regexs">
<item>"usb0"</item>
</string-array>
Not to be 'that guy', but could you please add a question mark to the title of your thread? I came in here hoping for a solution, not a question
I asked a similar question http://forum.xda-developers.com/showthread.php?t=1822788
a 3rd-party app may be able to help, but the kernel apparently has to be compiled with CONFIG_NETFILTER/CONFIG_IP_NF_IPTABLES and/or RNDIS
espionage724 said:
I asked a similar question http://forum.xda-developers.com/showthread.php?t=1822788
a 3rd-party app may be able to help, but the kernel apparently has to be compiled with CONFIG_NETFILTER/CONFIG_IP_NF_IPTABLES and/or RNDIS
Click to expand...
Click to collapse
I tried using android-wired-tether with a custom kernel that includes netfilter, iptables, and rndis. This still did not work since the application tries to access usb0 directly and the Nexus 7 never creates that interface even with a customized config.xml
I was able to get the USB tethering, Wi-Fi hotspot, and Bluetooth tethering options to come up in the menu on the Nexus 7 using the attached overlay placed in device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
The Wi-Fi hotspot and Bluetooth tethering options appear to work.
However, the USB tethering option unchecks itself after a second when I try to activate it.
I get the following error in logcat:
Code:
09-13 13:10:41.820: E/UsbDeviceManager(331): Failed to switch USB config to rndis,adb
I am happy to announce I got native USB tethering working on the Nexus 7
I had to make the changes to the config.xml as shown in the previous post and also had to modify out/target/product/grouper/root/init.usb.rc by adding the following
Code:
on property:sys.usb.config=rndis
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e23
write /sys/class/android_usb/android0/functions ${sys.usb.config}
write /sys/class/android_usb/android0/bDeviceClass 224
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state ${sys.usb.config}
on property:sys.usb.config=rndis,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e24
write /sys/class/android_usb/android0/functions ${sys.usb.config}
write /sys/class/android_usb/android0/bDeviceClass 224
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
I'm also using a modified tegra kernel with RNDIS options activated...not sure if this is required (I'm assuming it is). I will try the stock kernel later.
That is good news indeed
Props to You!
cbdonohue said:
I was able to get the USB tethering, Wi-Fi hotspot, and Bluetooth tethering options to come up in the menu on the Nexus 7 using the attached overlay placed in device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
The Wi-Fi hotspot and Bluetooth tethering options appear to work.
However, the USB tethering option unchecks itself after a second when I try to activate it.
I get the following error in logcat:
Code:
09-13 13:10:41.820: E/UsbDeviceManager(331): Failed to switch USB config to rndis,adb
Click to expand...
Click to collapse
Nice work and quick as well, I do like those overlays, there is plenty of nice tweaks to be had out of them if folks are willing to put the effort in.
I built my own overlay earlier on after you planted the seed and was quite surprised to get Wifi-Hotspot for free. It does work, well my HTC Sensation connects to it, which is quite amusing as Cm10 on the sensation doesn't have a working WifiHotspot :laugh: I think a bit of cross device hacking is in order there
cbdonohue said:
I'm also using a modified tegra kernel with RNDIS options activated...not sure if this is required (I'm assuming it is). I will try the stock kernel later.
Click to expand...
Click to collapse
I think this is my missing link, I was going to have a proper look at some point and you've saved me a job there, I'll build myself a fresh kernel now and see if it is the case.
:good:
So does this require both a modified (before compile) Kernel and ROM?
espionage724 said:
So does this require both a modified (before compile) Kernel and ROM?
Click to expand...
Click to collapse
After talking with trevd, I am pretty confident you need to modify the .config created by "make tegra3_android_defconfig" so the RNDIS driver is in the kernel. I won't be able to compare the stock kernel to my modified one until the weekend (I only have one Nexus 7 and have to do other testing with it). The .config file I used for my modified tegra kernel is attached.
So yes, modify the kernel and Jelly Bean source. I can certainly help anyone if they run into trouble.
I plan on putting up flashable images when I can and submitting a patch to cyanogen.
cbdonohue said:
I was able to get the USB tethering, Wi-Fi hotspot, and Bluetooth tethering options to come up in the menu on the Nexus 7 using the attached overlay placed in device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
The Wi-Fi hotspot and Bluetooth tethering options appear to work.
However, the USB tethering option unchecks itself after a second when I try to activate it.
I get the following error in logcat:
Code:
09-13 13:10:41.820: E/UsbDeviceManager(331): Failed to switch USB config to rndis,adb
Click to expand...
Click to collapse
Would love to use your overlay.
Where exactly do I find the above mentioned path?
When I connect Nexus 7 to my Mac and see the file structure, it is missing the device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
retfeg said:
Would love to use your overlay.
Where exactly do I find the above mentioned path?
When I connect Nexus 7 to my Mac and see the file structure, it is missing the device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
You need to modify the files in the Jelly Bean source code and recompile the operating system.
@cbdonohue:
Hey! Do you think you could upload your kernel/framework files to use in the mean time?
I'm very curious and I have asked this so many times and no one has answered me.
Why would you want to tether your device? your device cant and does note generate its own Mobile internet service like a 3G/4G device. its wifi only so why would you want to share your devices wireless connectivity?
the only thing I can think of is if you have a desktop or laptop that does NOT have a wireless card and you want to use your Nexus 7 as a wireless card essentially and then plugging it in via USB to your desktop/laptop?
what other reason could you have for wanting to share your devices wireless connectivity?
nextelbuddy said:
I'm very curious and I have asked this so many times and no one has answered me.
Why would you want to tether your device? your device cant and does note generate its own Mobile internet service like a 3G/4G device. its wifi only so why would you want to share your devices wireless connectivity?
the only thing I can think of is if you have a desktop or laptop that does NOT have a wireless card and you want to use your Nexus 7 as a wireless card essentially and then plugging it in via USB to your desktop/laptop?
what other reason could you have for wanting to share your devices wireless connectivity?
Click to expand...
Click to collapse
You can reverse-tether a device in order to get connectivity from your PC. This is what I'm looking to accomplish with my device while I'm at work so I can access the company intranet.
ObsidianX said:
You can reverse-tether a device in order to get connectivity from your PC. This is what I'm looking to accomplish with my device while I'm at work so I can access the company intranet.
Click to expand...
Click to collapse
^ This.
ObsidianX said:
@cbdonohue:
Hey! Do you think you could upload your kernel/framework files to use in the mean time?
Click to expand...
Click to collapse
1. Download the tegra kernel branch android-tegra3-grouper-3.1-jb-fr2 and compile using the attached defconfig. (This enables the RNDIS driver)
2. Download grouper branch android-4.1.1_r1.1 and copy the compiled tegra kernel into it.
3. Modify the following grouper file with the attached config.xml (This allows the 'Tether to USB' option to come up in the settings')
device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml
4. Compile grouper
5. Modify the following file with the attached init.usb.rc (This allows the OS to enable RNDIS USB tethering)
out/target/product/grouper/root/init.usb.rc
6. Flash to device.
At some point in the future I can make a flashable image or patch that will make this easier. In the mean time these steps should do it. Let me know if you have any issues.
nextelbuddy said:
I'm very curious and I have asked this so many times and no one has answered me.
Why would you want to tether your device? your device cant and does note generate its own Mobile internet service like a 3G/4G device. its wifi only so why would you want to share your devices wireless connectivity?
the only thing I can think of is if you have a desktop or laptop that does NOT have a wireless card and you want to use your Nexus 7 as a wireless card essentially and then plugging it in via USB to your desktop/laptop?
what other reason could you have for wanting to share your devices wireless connectivity?
Click to expand...
Click to collapse
One reason would be If you wanted to communicate between a PC and an Android device without being wireless. This could be to hide the connection or reduce the impact of RF interference. Not all applications need internet access...it might be just to send data between two end points.
USB interface and addressing specifics
For those of you who are interested...
If the Nexus 7 is acting as a USB device you can turn USB tethering on from the settings menu. The Android device automatically assigns its USB interface a hard coded IP address and starts DHCP server to hand out an address to the USB host at the other end.
If you want to change the IP address that the Android assigns itself you can modifiy the USB_NEAR_IFACE_ADDR constant in following file:
frameworks/base/services/java/com/android/server/connectivity/Tethering.java
If you want to disable the DHCP server, you can simply remove the address space you are using from the mDhcpRange array in the same file.
If the Nexus 7 is acting as a USB host (using USB OTG) then you must manually bring up the USB interface (ifconfig rndis0 x.x.x.x) since the USB menu settings will not do anything.
As an aside, am I the only one surprised to find hard coded IP addresses deep in the Android code?! haha
I've found some other gems like "shoud not get here" lines and c/c++ goto statements.
Hey folks,
I took cbdonohue's modifications and built them into CM10 and it works like a charm! I took the liberty of uploading the ZIP to dev-host:
http://d-h.st/KIr
All credit goes to cbdonohue for finding and creating the modification. I just built it

[GUIDE][TMO][VZW] Hide Tethering Data with NO 3RD PARTY APPS

If you're like me, a PdaNet customer running Linux who's sad that there's no build of PdaNet designed for Linux for hiding tether usage over USB Tethering, then fear not! After some research I've devised a plan to hide USB tethering usage from carriers that DOES NOT require PdaNet!. I've tested this myself on T-Mobile and Verizon, and on both of these carriers it looks like it works just fine. This does not mean that it will only work with these carriers, these are just the ones I've tested myself (with the exception of the appended notes below). If you have another carrier not mentioned here, please test this out and let me know if it works for you and I'll add it to the OP at the bottom
Here's a precaution I'd take on Android too, just to make sure the carrier really doesn't find anything out:
Go to Magisk Manager and get yourself the OpenDNS or DNSCrypt addon and install that. I think Verizon is catching on that I'm tethering somehow through DNS, even when I use VPN. By setting my DNS on my phone's LTE connection to something that's not-verizon, this should allow me to dodge that. I recommend you doing it too as a precaution
Here's what you have to do for Linux:
1) Hop over to your Linux machine, open a terminal emulator, and type the following commands (with root privileges):
sudo sysctl net.ipv4.ip_default_ttl=65
echo 65 | sudo tee /proc/sys/net/ipv4/ip_default_ttl
What this does is sets your PC's network packets to have a Time To Live of 65. This is to make it seem like the packets were originated from your phone instead of your PC. Android's default TTL for its packets is 64, so when the PC sends packets to your phone through tethering with a TTL of 65, they have a TTL of 64 by the time your phone sends them out to T-Mobile's towers (the internet).
2) If you want to have the PC's TTL set to 65 on every startup so you don't have to keep entering the two commands above again and again every time you reboot, add the following line to your PC's /etc/sysctl.conf file and save:
net.ipv4.ip_default_ttl=65
Here's what you have to do for Mac: (credits for the instructions and post going to @BrettB0727)
For those wondering how to do this on a Mac, it can be done temporarily using:
Code:
sudo sysctl -w net.inet.ip.ttl=65
Or permanently by creating or editing /etc/sysctl.conf to add
Code:
net.inet.ip.ttl=65
if you end up creating the file, you will need to be sure and do:
Code:
sudo chmod 0644 /etc/sysctl.conf
sudo chown root:wheel /etc/sysctl.conf
Here's what you have to do for Windows:
1) Open up regedit and go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
2) Make a new REG_DWORD entry in there called DefaultTTL and set it to 65
3) Reboot
NOTE: I've found that downloading files can be finicky. I was able to download an MP4 video before without it detecting I was using tethering data, but when I tried to get a .zip file from ModDB T-Mobile found out what I was doing. Just take warning that not all forms of network traffic will be hidden when tethering.
NOTE 2: Confirmed by @triggerlord to work with WiFi Hotspot, as well as with Simple Mobile
NOTE 3: If you're one of those people who have trouble hiding their data with this method, take @niry's advice and see if it helps: he said to remove `dun` type from pcweb.t-mobile.com APN and add it to the end of the fast.t-mobile.com one (if it's not already there)
Lol, this fixed my Simple Mobile (powered by T-Mobile) tethering issues. Nice! This works with the WiFi hotspot feature too BTW.
triggerlord said:
Lol, this fixed my Simple Mobile (powered by T-Mobile) tethering issues. Nice! This works with the WiFi hotspot feature too BTW.
Click to expand...
Click to collapse
Were you able to browse the web (hidden) without changing your browsers user agent? I find that if I don't set Chrome to look like Android its 50/50 if it gets hidden or not.
Sent from my Moto G Play using XDA-Developers Legacy app
jasonmerc said:
Were you able to browse the web (hidden) without changing your browsers user agent? I find that if I don't set Chrome to look like Android its 50/50 if it gets hidden or not.
Sent from my Moto G Play using XDA-Developers Legacy app
Click to expand...
Click to collapse
Everything works fine. I didn't need to change browser agents or anything. (I'm using chromium though.) I've only tried this via WiFi hotspot. EDIT: And I didn't need to change the APN setting either. Changing the TTL was enough to get it working.
is ma.t-mobile.com working for anyone? i keep getting sent to my.t-mobile.com even after doing what OP suggested. it used to work for me a few weeks back.
shawtydat said:
is ma.t-mobile.com working for anyone? i keep getting sent to my.t-mobile.com even after doing what OP suggested. it used to work for me a few weeks back.
Click to expand...
Click to collapse
Maybe they shut down the website. Haven't been on it myself in months
jasonmerc said:
Maybe they shut down the website. Haven't been on it myself in months
Click to expand...
Click to collapse
i'm afraid that to be the case, but is there another way to monitor tether vs mobile data?
shawtydat said:
i'm afraid that to be the case, but is there another way to monitor tether vs mobile data?
Click to expand...
Click to collapse
You might be able to in the T-Mobile app on your phone but other than that I think we're screwed now
jasonmerc said:
If you're like me, a PdaNet customer running Linux who's sad that there's no build of PdaNet designed for Linux for hiding tether usage over USB Tethering, then fear not! After some research I've devised a plan to hide USB tethering usage from T-Mobile. Tested and confirmed working with Ubuntu 16.10 and Mint 18.1, with the latest ResurrectionRemix on my XT1607.
Click to expand...
Click to collapse
When using this method, is the PdaNet app required on the phone?
MountainX said:
When using this method, is the PdaNet app required on the phone?
Click to expand...
Click to collapse
No, you don't need any apps
triggerlord said:
Lol, this fixed my Simple Mobile (powered by T-Mobile) tethering issues. Nice! This works with the WiFi hotspot feature too BTW.
Click to expand...
Click to collapse
Can you supply more information.
I'm looking at switching carriers due to my location(In the mountains with just about nothing for service providers) and want to know how much data you actually use.
What's the most data you have used with this TTL method?
Have they throttled you? and if so, how much?
Any information you can supply is extremely helpful. Thank you! =D
I've used 60gb no throttle.
That's awesome. Thank you for that information.
shawtydat said:
is ma.t-mobile.com working for anyone? i keep getting sent to my.t-mobile.com even after doing what OP suggested. it used to work for me a few weeks back.
Click to expand...
Click to collapse
Works for me.
jasonmerc said:
What this does is sets your PC's network packets to have a Time To Live of 65. This is to make it seem like the packets were originated from your phone instead of your PC. Android's default TTL for its packets is 64, so when the PC sends packets to your phone through tethering with a TTL of 65, they have a TTL of 64 by the time your phone sends them out to T-Mobile's towers (the internet).
Click to expand...
Click to collapse
Thanks, jasonmerc! This put me in the right direction to remove the need for PdaNet on my Mac and also to be able also use my phone as a Wi-Fi Hotspot at full speed on T-Mobile. I'll be looking for your tutorial to bypass T-Mobile's international speed limits!
For those wondering how to do this on a Mac, it can be done temporarily using:
Code:
sudo sysctl -w net.inet.ip.ttl=65
Or permanently by creating or editing /etc/sysctl.conf to add
Code:
net.inet.ip.ttl=65
if you end up creating the file, you will need to be sure and do:
Code:
sudo chmod 0644 /etc/sysctl.conf
sudo chown root:wheel /etc/sysctl.conf
BrettB0727 said:
Thanks, jasonmerc! This put me in the right direction to remove the need for PdaNet on my Mac and also to be able also use my phone as a Wi-Fi Hotspot at full speed on T-Mobile. I'll be looking for your tutorial to bypass T-Mobile's international speed limits!
For those wondering how to do this on a Mac, it can be done temporarily using:
Code:
sudo sysctl -w net.inet.ip.ttl=65
Or permanently by creating or editing /etc/sysctl.conf to add
Code:
net.inet.ip.ttl=65
if you end up creating the file, you will need to be sure and do:
Code:
sudo chmod 0644 /etc/sysctl.conf
sudo chown root:wheel /etc/sysctl.conf
Click to expand...
Click to collapse
I just noticed your reply right now, and I appreciate the steps for doing this on a Mac! I'm going to add these Mac steps to the first post and give you credit for it
As far as international data limits go, I'm not sure I can address that with a fix like this unfortunately.
Still working?
I haven't been able to get over 500kbps using this method. Is this approach still working for folks in 2018?
tatemz said:
I haven't been able to get over 500kbps using this method. Is this approach still working for folks in 2018?
Click to expand...
Click to collapse
I haven't used this in a while, but I'll give it a try soon to see if it still does
tatemz said:
I haven't been able to get over 500kbps using this method. Is this approach still working for folks in 2018?
Click to expand...
Click to collapse
It works in combination with altering the `type` string in the APNs: remove `dun` from pcweb.t-mobile.com one and add it to the fast.t-mobile.com one so it will read `default,supl,hipri,fota,dun`.
niry said:
It works in combination with altering the `type` string in the APNs: remove `dun` from pcweb.t-mobile.com one and add it to the fast.t-mobile.com one so it will read `default,supl,hipri,fota,dun`.
Click to expand...
Click to collapse
Thanks for letting me know about this. I was talking to some people about using this method and they said it was a hit or miss in terms of hiding their tethering usage. I'll update the OP to include what you said as a fix, for people to try out if it's not working

Categories

Resources