I heard rumour that android phones do not 'see' ad hoc (IBSS) connections and what is needed is an Access Point (AP).
If this is true, to see if your wifi adapter on your PC is capable of being used as an AP, try this:
Code:
iw list | grep -A 8 "Supported interface modes:"
It lists your wifi adapter capabilities and then picks out the 8 lines of 'context' after "Supported interface modes:"
On this machine, I have two wifi adapters. This is what the return looks like:
Quote:
moe@fissionchips:~$ iw list |grep -A 8 "Supported interface modes:"
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
--
Supported interface modes:
* IBSS
* managed
* monitor
software interface modes (can always be added):
* monitor
interface combinations are not supported
Supported commands:
* new_interface
moe@fissionchips:~$
The first one listed can be programmed for:
- IBSS, ad hoc configuration
- managed, or 'regular' connect to a router wifi
- AP, access point to function as a router
- AP/VLAN, as above but with multiples
- monitor, can listen to all channels
- mesh, for mesh networks, and then the
- P2P, which I know nothing about but assume is peer to peer of some sort
And, sadly, the other wifi, the one built into the machine, is not capable of doing much, but an ad hoc (IBSS) connection, or surfing the internet by connecting to a router (managed) while I drink beer in some bar as I monitor all the other wifi signals, if I knew how to do it.
So that being said, if you don't have an AP, it is my the understanding that the android phone can't see it....but it wouldn't be the first time I was misinformed.