[Commotion-dev] Kernel which supports wireless extensions

[Hans of Guardian]

Yes, Commotion MeshTether is the most recent version of the OLSR app for Android.  Olsr Mesh Tether is the old name for that.

For debugging, the next thing I would do is install Lil Debi to get a Debian shell to work with:
https://play.google.com/store/apps/details?id=info.guardianproject.lildebi&hl=en

Then you can 'apt-get install' any software from debian, including 'wireless-tools', which provides iwconfig.  I use all the standard GNU/Linux tools via Lil Debi to setup adhoc mode on the hardware directly.  If that doesn't work, then most likely your devices kernel does not support wireless extensions for setting up adhoc mode.  In that case, you need to install a new kernel to get adhoc support.

.hc

On Mar 8, 2013, at 9:36 AM, Magnus Wennberg wrote:

> We downloaded the commotion mesh tether apk, is this the one you were talking about? Annyway, the application is still not working. The commotion mesh tether application gets stuck in the "Aquiring  wifi lock" state, and the Olsr Mesh Tether application get stuck same place as before.
> Any ideas of what we can do? 
> 
> Regards 
> Magnus
> 
> 
> On Tue, Mar 5, 2013 at 6:06 PM, Hans-Christoph Steiner <hans at guardianproject.info> wrote:
> 
> Yes, 'wifi' is a little terminal executable written in C.  It does the adhoc
> work, so its essential.  There are ARM APKs available:
> https://commotionwireless.net/download
> 
> .hc
> 
> On 03/05/2013 09:53 AM, Magnus Wennberg wrote:
> > Hi Hans
> >
> > We are having some problems with the Commotion MeshTether, and was hoping
> > maybe you can help us?
> > When we press "Start" we get these messages:
> >
> > Starting...
> > no active WAN interface found
> > running /data/data/net.szym.barnacle/app_bin/run
> > ./wifi[2]: ../native/libs/armeabi/wifi: not found
> > ./wifi[2]: ../native/libs/armeabi/wifi: not found
> > OLSR on http://172.29.133.196:8080
> > ./wifi[2]: ../native/libs/armeabi/wifi: not found
> > ./wifi[2]: ../native/libs/armeabi/wifi: not found
> > Stopped unexpectedly!
> >
> > We think we might not have built the native code correct? What do you think?
> >
> > Best regards
> > Magnus
> >
> >
> > On Fri, Mar 1, 2013 at 6:32 PM, Hans of Guardian
> > <hans at guardianproject.info>wrote:
> >
> >>
> >> Hey Magnus,
> >>
> >> Glad to have more people working on this stuff, it can be painful.
> >>
> >> The Nexus One has working adhoc with the stock kernel and OS, so its
> >> probably not a good example for getting this stuff working on other
> >> devices.  Also, you don't need monitor mode for OLSR, just plain on adhoc
> >> IBSS mode.
> >>
> >> I think the key is to figure out where adhoc mode is disabled in the HTC
> >> One V.  Have you tried running Commotion MeshTether on it?  The debug log
> >> from the menu of that app could provide useful info.  The other thing I'd
> >> do is try directly messing with the wpa_supplicant from the terminal to see
> >> if it returns adhoc/IBSS networks in the scans.
> >>
> >> I do this kind of debugging using Lil Debi (in the Play store) so that I
> >> have a full Debian shell to work in, either via adb shell or ssh.
> >>
> >> .hc
> >>
> >>
> >> On Mar 1, 2013, at 9:59 AM, Magnus Wennberg wrote:
> >>
> >> Dear everybody!
> >>
> >> We are two students that are currently working on our master thesis at the
> >> University of Agder in Norway. We want to install olsr on two Android HTC
> >> One V phones. We are trying to use the SPAN application and are currently
> >> working on building our own custom kernel. However we are having some
> >> trouble getting the wireless extension support working. We have asked the
> >> SPAN project group for help, but we cant figure out where the problem is.
> >>
> >> Is there anybody that have done similar work? With HTC phones?
> >>
> >> We found this site through a post in your archives. In this post you
> >> described how to take chip out of managed mode for Nexus one and Galaxy S
> >> 2. If we can do this with our HTC phones it will help us towards reaching
> >> our goal. However, we are not sure how to use it, can anyone point us in
> >> the right direction of where to start?
> >> http://bcmon.blogspot.co.il/2012/09/working-monitor-mode-on-nexus-one.html
> >>
> >>
> >> --
> >> Best regards
> >> Nils Erik Skjønsberg & Magnus Wennberg
> >>  _______________________________________________
> >> Commotion-dev mailing list
> >> Commotion-dev at lists.chambana.net
> >> https://lists.chambana.net/mailman/listinfo/commotion-dev
> >>
> >>
> >>
> >
> >
> 
> 
> 
> -- 
> Mvh
> Magnus Wennberg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130308/ff9b7a60/attachment.html>