[Commotion-dev] Android mesh app - preferred devices

Hans-Christoph Steiner hans at guardianproject.info
Thu Jul 26 01:24:10 UTC 2012


On Jul 24, 2012, at 9:19 PM, Nathan of Guardian wrote:

> On 07/24/2012 08:43 PM, Jeremy Lakeman wrote:
>> Nexus 7 running stock 4.1 rom + root;
>> # ./iwconfig wlan0 mode ad-hoc
>> Error for wireless request "Set Mode" (8B06) :
>>    SET failed on device wlan0 ; Operation not supported on transport endpoint.
> 
> What I think we recently discovered (and Hans will have to back me up or
> correct me here) that while adhoc wireless is not supported in the
> typical way (i.e. you can see the network and select it), you can
> definitely insert and active configuration information for adhoc
> networks via the WirelessManager API.
> 
> See the "Ignore adhoc" in the WirelessManager Android source (meaning,
> they support them but just don't display them):
> http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android-apps/4.0.1_r1/com/android/settings/wifi/WifiSettings.java#506
> 
> and then our code here for manually configuring an adhoc network via the
> public WirelessManager API:
> https://code.commotionwireless.net/projects/commotion-android/repository/revisions/87466f5344fa36ff78333d58f14ab126b11fe41b/entry/src/net/commotionwireless/meshtether/MeshService.java#L334
> 
> This is all very new, and I am sure there are bugs, but I did see this
> working live on a rooted stock/AOSP Nexus One late last week, so... ya.

Using iwconfig means you're bypassing everything Android and talking directly to the Linux kernel, more or less.  So Jeremy's error means that kernel driver or hardware does not support adhoc mode.  That's bad news either way.

.hc


More information about the Commotion-dev mailing list