Develop Bugs

[Q] Portable Wi-Fi hotspot

Hello,
I want to use portable Wi-Fi hotspot on my phone to connect to my laptop in places where public wi-fi is not available, or to connect to two computers to each other. And it seems to be working.
But I have a problem. I do not want to use mobile network to access Internet for those computers. I want only to exchange data between phone and computer, or between computers themselves.
But every time I switch on hotspot, 3G connection switches on automatically, even if it is switched off on purpose. I know this is intended use of hotspot, but I have a question:
Is there a way to prevent phone switching 3G network on in wi-fi hotspot mode, or just preventing data traffic over 3G?
Or I am missing the point completely?

The application is not intended for such usage; all it does is route traffic between connected wlan-clients and the carrier's apn. The phone itself has the ip-address 192.168.1.1 during this setup, but it is not listening on any ports that would be useful for your setup (ie 'cifs/samba').

LeeCHeSSS said:
The application is not intended for such usage; all it does is route traffic between connected wlan-clients and the carrier's apn. The phone itself has the ip-address 192.168.1.1 during this setup, but it is not listening on any ports that would be useful for your setup (ie 'cifs/samba').
Click to expand...
Click to collapse
I do not know if I do understand you but here are the facts:
I connect two dell laptops to portable wi-fi hotspot on my wildfire s:
one is : 192.168.1.135
other : 192.168.1.185
I can ping one from another. If I share a folder in one (.135) and go to others(.185) "Search for computers or people" I see all files in shared folder and can do all the usual operations over them (edit, move...)
Also if I install Remote Web Desktop from Market on my phone I can access phone through web interface.
In a word, I can do all things as on "normal" wi-fi network ( and I promise it is the only network around here ) except all the time I have 3G switched on. And I do not want to do that because I see my network data traffic going up.
So, as I see things, my only problem is unwanted 3G traffic.
Help?

Ah, but you did not mention that you had installed a seperate application to open up a port for the webinterface.
This however does not change the intended usage for the mobile wifi hotspot application!

hey...you can try this:
1. go to your mobile network settings
2. create a new APN, a dummy one
3. set the new APN as default
4. launch your wifihotspot
I did not test it with 2 pcs but, when u launch wifihotspot, 3g no longer comes on and my pc still connected to the wireless network without any problems.
Let us know your results
Cheers,

Hey,
I ran more test on this issue. The previous posted solution works like a charm.
I was able to use the wifihotspot as a wireless access point:
1. 2 or more PCs can communicate with each other (browse folders)
2. If one of the PCs has internet access, it shares to the rest of the PCs
3. If one of the PCs has an ethernet connection to a server, all other PCs also get connection to the server
For 3. to work, you will need to brigde the local area connection with the wireless connection on the PC that has cabled ethernet connection. Also browsing folders will work only if you use \\server ip (\\servername does not work).
I will try getting DNS access via the hotspot later.
Hope this helps

Wireless tethering

I've heard some people say that when they're rooted, their wireless tether, another Android device such as a tablet or phone can't pick it up do to it being an adhoc network.
Question is, what's an adhoc network?
And how come MY wireless tether can be picked up by my Android tablet. But someone elses wireless tether doesn't work on their Android tablet?
Sent from my SPH-D710 using XDA App

xjs1200x said:
I've heard some people say that when they're rooted, their wireless tether, another Android device such as a tablet or phone can't pick it up do to it being an adhoc network.
Question is, what's an adhoc network?
And how come MY wireless tether can be picked up by my Android tablet. But someone elses wireless tether doesn't work on their Android tablet?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
On wireless computer networks, ad-hoc mode is a method for wireless devices to directly communicate with each other. Operating in ad-hoc mode allows all wireless devices within range of each other to discover and communicate in peer-to-peer fashion without involving central access points (including those built in to broadband wireless routers).
To set up an ad-hoc wireless network, each wireless adapter must be configured for ad-hoc mode versus the alternative infrastructure mode. In addition, all wireless adapters on the ad-hoc network must use the same SSID and the same channel number.
An ad-hoc network tends to feature a small group of devices all in very close proximity to each other. Performance suffers as the number of devices grows, and a large ad-hoc network quickly becomes difficult to manage. Ad-hoc networks cannot bridge to wired LANs or to the Internet without installing a special-purpose gateway.
Ad hoc networks make sense when needing to build a small, all-wireless LAN quickly and spend the minimum amount of money on equipment. Ad hoc networks also work well as a temporary fallback mechanism if normally-available infrastructure mode gear (access points or routers) stop functioning.
Infrastructure mode wireless networking bridges (joins) a wireless network to a wired Ethernet network. Infrastructure mode wireless also supports central connection points for WLAN clients.
A wireless access point (AP) is required for infrastructure mode wireless networking. To join the WLAN, the AP and all wireless clients must be configured to use the same SSID. The AP is then cabled to the wired network to allow wireless clients access to, for example, Internet connections or printers. Additional APs can be added to the WLAN to increase the reach of the infrastructure and support any number of wireless clients.
Compared to the alternative, ad-hoc wireless networks, infrastructure mode networks offer the advantage of scalability, centralized security management and improved reach. The disadvantage of infrastructure wireless networks is simply the additional cost to purchase AP hardware.
Note that home wireless routers all feature a built-in AP to support infrastructure mode.

awesome information thanks.
But any ideas for the 2nd question? about connecting android devices to other adhoc networks that work and dont work......

Think of it like this. Hotspot mod (infrastructure) on this phone is like connecting to a router. Wireless tether (ad hoc) is like doing internet connection sharing on a computer. You'll have to find a mod for the device that can't see or connect to ad hoc, to make it work. There are different ways to accomplish the same thing in different devices. With a galaxy tab, it's replacing a file. I'm probably wrong but with the Xoom, you need a modded kernel.
Also, as the saying goes, Google is your friend.

I couldn't connect my wife's laptop to the hotspot on my phone until I lowered the security on the hotspot settings to WPA. Default was WPA2. Something to keep in mind if a device won't connect.

Tethering on Mobilicity - same or different ip address?

I have a question regarding tethering via wifi on my T989D.
I am using the Juggernaut v5.0 on my Telus T989D. It has wifi-sharing app built in. When I use this application to share my mobile internet with my PC, I get two different ip addresses. For example, use my PC's browser, I find my PC's ip address is 123.123.123.57, however my phone's IP address is 123.123.123.101. So my phone and my pc have different ip addresses.
Strange enough, my Samsung Vibrant (T959 from TMobile), is different. I use wifi tethering for root user app, and I find my PC and my phone (T959) share the same ip address.
Why they are different on my T989D?
The problem I am having right now is, tethering via T989D's built-in function is slow. Sometimes connection drops. However the tethering via my T959 is very reliable and fast.
Is there a way to disable built-in tethering on T989D and use the tethering for root user app on my T989D? I have tried to freeze the tether manager, but tethering for root user still has error in log and I cannot connect to it at all.
Please help, I want to fix my tethering problem with T989D.
thanks

think about it...
when you are WiFi tethering, your phone is acting as the router, and it provides its own IP to you
you don't get the Mobilicity IP on your laptop or whatever it's hooking up to your phone on WiFi

Sorry I don't get it.
Why my T989D and T959 act differently?

Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..

Thanks Jasnn, this really helped and I am now clear.
Yes, the application I am referring to was android-wifi-tether. It works flawlessly
on T959D. it is very slow on my T989D with Juggernaut 5.0/Telus modem.
If I reboot the phone and start tethering using android-wifi-tether, the application starts, but there is one error in log:
Setting ad-hoc mode: failed.
IP address are still different. My pc and phone has two different ipaddress.
I'd like to have the same ipaddress, also one thing bugs me is, the internet connection is not stable, the internet goes on and off. Lots of t989/D users have experienced this problem, there is no cure yet.
thanks
jasnn said:
Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..
Click to expand...
Click to collapse

[Q] USB Ethernet, strange behavior

Hello everyone!
I successfully manged to get a USB-Ethernet Dongle working on my note 2.
However I am experiencing a strange issue:
When I had first set up the ethernet functionality, everything was working fine.
(Most apps could Not access the internet though, but some such as browser or vlc-player could).
Some days passed by during which I did not use the ethernet functionality but accessed several wifi networks
Now the issue:
if I want to use ethernet at my home network again everything seems fine first.
I can connect via ethernet, retrieve an ip adress using "dhcpcd eth0" and even issue commands like "traceroute www .google. de"
The output of "ip addr show" and "ip route show" also indicates that eth0 interface was assigned a ip-adress and also the correct default gateway has been defined
however if I want to use the browser to browse the web no connection can be established...
same with VLC-Player.
so network commands via terminal work but there's no internet connection within apps.
The strange thing is:
if I now access my home network via wifi first, turn wifi off and use ethernet again everything works as expected (especially the browser is working again..?!)
I'm wondering what I'm missing here:
Do I miss something during setting up the ethernet interface?
note that I also set the "net.dns1" and "net.dns2" property for primary and secondary DNS Server...
But why is ethernet only working if I firstly connect to the same network via wifi?
I assume that while connecting to the network via wifi some additional properties are set.
I'd very appreciate any explanation/suggestion on this matter.
thanks in advance!
Regards!

BennyKay said:
Hello everyone!
I successfully manged to get a USB-Ethernet Dongle working on my note 2.
However I am experiencing a strange issue:
When I had first set up the ethernet functionality, everything was working fine.
(Most apps could Not access the internet though, but some such as browser or vlc-player could).
Some days passed by during which I did not use the ethernet functionality but accessed several wifi networks
Now the issue:
if I want to use ethernet at my home network again everything seems fine first.
I can connect via ethernet, retrieve an ip adress using "dhcpcd eth0" and even issue commands like "traceroute www .google. de"
The output of "ip addr show" and "ip route show" also indicates that eth0 interface was assigned a ip-adress and also the correct default gateway has been defined
however if I want to use the browser to browse the web no connection can be established...
same with VLC-Player.
so network commands via terminal work but there's no internet connection within apps.
The strange thing is:
if I now access my home network via wifi first, turn wifi off and use ethernet again everything works as expected (especially the browser is working again..?!)
I'm wondering what I'm missing here:
Do I miss something during setting up the ethernet interface?
note that I also set the "net.dns1" and "net.dns2" property for primary and secondary DNS Server...
But why is ethernet only working if I firstly connect to the same network via wifi?
I assume that while connecting to the network via wifi some additional properties are set.
I'd very appreciate any explanation/suggestion on this matter.
thanks in advance!
Regards!
Click to expand...
Click to collapse
There is something on these forums called "reverse tether" look it up, it has something that can fix this with IP tables and force the phone to think that it is connected to Wifi

Great, thank you!
I did not know about this possibility!
Especially the xposed module looks promising.
It might help to get more apps to reconize the active internet connection.
I'll give it a try!
however I still have no clue why the ethernet interface only seems to work correctly if I first connect the phone via wifi to the network.
The browser will recognize the connection when I do the following:
1.1>turn wifi on and connect to my network
1.2>turn wifi off again
2.1>connect the ethernet USB Dongle
2.2>set up eth0 interface
3>web browser works
Note that I only turn wifi on for step 1.1 and 1.2. When using the ethernet connection wifi is already turned off and the browser still works.
I read that the browser uses some low-level functionality and bypasses the Android framework which is why it can use network connections even though android "thinks" no network is available.
But if I skip the first 2 steps even the web browser won't work.
I think it's quite strange behavior which I cannot explain. Maybe a configuration problem which is solved when setting up a wifi connection prior?
Maybe I'll have to dig a bit deeper into how networking in android works.

Hi, can you share your settings and how did you managed to connect through ethernet? Which rom and kernel you used?
Sent from my GT-N7100 using Tapatalk

chandoliasnikos said:
Hi, can you share your settings and how did you managed to connect through ethernet? Which rom and kernel you used?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hello!
I am using PhoeniX ROM v16.7 along with the AGNI PureStock Kernel v.3.9.3.
It is the kernel that enables the ethernet functionality.
However ethernet support depends on the chipset of the ethernet adapter you are going to use.
Mine has an ASIX AX88772 chipset. I am not sure what kind of chipsets are supported by this kernel.
If the kernel does not support your chipset you will have to compile the driver yourself and insert it as a kernel-module.
I cannot post any links (due to restrictions for new members) but you will find a lot about this topic if you search for: note 2 ethernet kernel module
I do not really understand what you mean by settings:
If you have ethernet up and running you can type in terminal:
Code:
netcfg
You will then see a list of all network interfaces along with the eth0 interface.
To set up the eth0 interface using dhcp you can issue:
Code:
dhcpcd eth0
For manual configuration you will need:
Code:
ifconfig eth0 IP_ADDRESS_YOU_WANT_TO_ASSINGN netmask YOUR_SUBNETMASK
route add default gateway IP_ADDRESS_OF_YOUR_GW dev eth0
setprop net.dns1 IP_OF_YOUR_DNS_SERVER
I am not sure if I do something wrong during configuration, because eth0 interface will only work in apps like the browser if I connect to my network via wifi first (see the my first posts for detailed explanation).
I can turn my wifi off afterwards and use ethernet instead but for configuration I need to start wifi first.
I am not sure why - I still could not figure out the problem...

Connect to WPA2-Enterprise wifi

Is there any way for the fire TV to connect to it? My university uses it, and I was wondering if I could connect, but the access point is not showing up

Can´t look now because I´m not at home but wasn´t there a setting for a manual AP setup where you could enter the SSID by yourself?

Some organizations may keep a second network available for legacy devices like printers, XBoxes, and older machines. You can check with your university's tech support to see how you can add your device to the list of allowed access for that network.
This isn't a guarantee that this network exists for you, but most enterprise and even some residential-grade equipment have this capability.
Otherwise, you might be able to find a router or range extender that can understand and connect to WPA2-Enterprise to work around this. In a pinch, an old laptop with two wifi cards or a wifi Ethernet port should suffice.
Or you may want to scrap wifi and run an Ethernet cable to your dorm's jack or personal switch.
Related topics found through Googling, but no further help:
https://www.reddit.com/r/cordcutters/comments/2sv1ov/best_option_for_college_wifi/
https://www.reddit.com/r/fireTV/comments/2mydhh/fire_tv_stick_can_you_use_a_wireless_network_that/

Thanks the responses, but neither of them works well for me. there is a secondary unsecured wifi network, but it is just too slow to use, especially for streaming videos. I sideloaded a wifi APK onto it, and the networks DO show up, but there is no way to enter the login information (you need both a username and password.) Anyone know of an app that can do that?