[Commotion-dev] convincing google to support ad-hoc mode

[L. Aaron Kaplan]

On May 25, 2012, at 8:07 PM, Hans-Christoph Steiner wrote:

> 
> On May 24, 2012, at 10:25 AM, L. Aaron Kaplan wrote:
> 
>> 
>> 
>> On May 24, 2012, at 2:39 PM, Sascha Meinrath wrote:
>> 
>>> Perhaps we should see about setting up a meeting with the Android development
>>> team management to ensure they understand the importance of ad hoc mode for the
>>> open source movement?
>>> 
>> YES!!
>> 
>> That would be a great contribution. 
>> 
>> Aaron.
>> 
>> 
>> PS: while you are at it: please tell them that for good meshing we need the layer 2 parameters (RSSI, noise, SNR, biterror rate, etc.) as data readable from /proc or debugfs
> 
> Are these not normally exposed in Android?

I don't know about Android specifically but in Linux there is a great need to have a uniform/standardized way to read out this information. Often enough, when/if you can get these values they are not comparable. Or for example one card will show signal strength but no noise value.

FYI:
Currently Henning is also implementing the DLEP draft (https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/) which aims at bringing radio layer information to the mesh router in a standardized way.


>  I don't know much about this, so more info is needed to convince them.  Info like how to configure the kernel to support this, how common it is in other OSes (Ubuntu, Debian, etc.), potential hazards of including it, including possible privacy risks and things like that, and reasons why telecoms or manufacturers might be opposed, etc.
> 
> .hc
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20120525/615127fc/attachment.sig>