[Commotion-dev] Current state on handsets

[Jeremy Lakeman]

Keep forgetting that this list doesn't change the "reply to" address...

On Fri, Feb 24, 2012 at 8:51 PM, Jeremy Lakeman
<Jeremy.Lakeman at gmail.com> wrote:
> (Shameless plug) I'd say Serval Mesh is on the forefront here....
> Simple install and config. Works on lots of phones, though known to
> *completely* and almost permanently screw up wifi on some Droid's.
> You can call between directly connected nodes, though we default to
> batman routing which takes ages to flip paths when you are wandering
> around.
> Our development branch has a store and forward file transfer system
> built in, that we're also using for delay tolerant text messaging, and
> collaborative mapping (still a work in progress).
> You can even install the software directly between phones via either
> blue tooth or a temporary hotspot.
> And everything we've done also works in wifi client / hotspot mode
> between devices connected to the same network. Useful if you can't get
> root on some devices.
>
> Note that there's basically no security at this point.
>
> On Fri, Feb 24, 2012 at 6:04 PM, Paul Fuxjaeger <fuxjaeger at ftw.at> wrote:
>> hi all,
>>
>> can someone in here shed some light on the current state of adhoc-mode and
>> olsrd/batmand on smartphones (for android-platform mostly I guess?).
>>
>> 1) On how many models is it known to work at all currently?
>> 2) How much effort is it to make it work?
>> 3) Are there ways to enable it WITHOUT breaking any other functionalities on
>> the smartphone if installed?
>>
>>
>> paul
>>
>>
>>
>>
>>
>>
>> PS: the reason for asking is:
>>
>> We thought that the upcoming loooong series of street protests (because of
>> acta and it's yet unborn siblings) here in europe/anywhereelse provide a
>> nice testbed situation:
>>
>> During protest there are:
>> 1) lots of technically inclined people with latest gen rooted/jailbroken
>> smartphones in close physical proximity.
>> 2) the prospect of helping to test if adhoc nets can spontaneously emerge
>> will probably spark interest
>> 3) protest events typically last for 2-4 hours each, thus energy efficiency
>> problems (battery runtime) can be largely ignored at this stage
>> 4) those protests all have a general "we want to keep our networks out of
>> central control" subtext - perfect fit for the occasion.
>>
>> We think that it does not really matter yet if these "networks" (they
>> probably cannot stabilize anyhow, routingtable-wise) can be used for
>> something useful at all - it is more about the fun of
>> observing/participating. Just seeing some small partitioned network graphs
>> as they spontaneously emerge/breakdown is enough. Form our point of view, it
>> would certainly add some entertainment-bonus while we walk these long
>> protest walks.
>>
>> Currently, what we typically do while being there in the streets (appart
>> from chanting and chatting with friends face2face) is using centralized
>> twitter/facebook APIs on top of cellular networks controlled by large
>> corporations. Although these tools are working fine and seem to be passing
>> along messages unfiltered, there are many reasons to start questioning if
>> this will stay like that.
>>
>>
>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> http://lists.chambana.net/mailman/listinfo/commotion-dev