[Commotion-dev] Boilerplate Android code pushed

Hans-Christoph Steiner hans at guardianproject.info
Thu Feb 2 17:18:18 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


I got it running on my Droid with CM7.1, but then I couldn't make it
stop running ;)  Every time I turned on my wifi since setting up
Serval, the Serval app would then show up and turn it back off.  I
first clicked the "Suspend" button, and it turned to "Start".  I then
clicked "Reset".  I then force closed it, and cleared the data.

Now I've removed it entirely, and my wifi isn't working any more.  It
turns on, but never scans for any networks and it seems to have
cleared all the saved networks in my phone.  I cannot manually add
networks either.

Does this app mess with the wpa_supplicant.conf that comes with the
phone, or any of the standard Android files?

.hc

On 01/10/2012 10:08 PM, Jeremy Lakeman wrote:
> If that process completely locks up (and it can) you may need to
> force close the application or reboot. After that it will disable
> running the same process for turning on adhoc mode.
> 
> Let me know if you manage to get past that step, or you are still
> having issues.
> 
> On Wed, Jan 11, 2012 at 1:14 PM, Hans-Christoph Steiner
> <hans at at.or.at> wrote:
>> 
>> A little bug report, in case you're interested:
>> 
>> I just downloaded Serval Mesh from the Marketplace on my Droid
>> running CM7.1.  It gets thru "Unpacking the stuff I need",
>> "Checking for root access", and "I think I know how to control
>> your wifi", then says "Skipped check for experimental support
>> since we already support your handset.", and gets stuck on "Test
>> if WiFi control works".  It just seems to try again and again.
>> 
>> .hc
>> 
>> On Jan 10, 2012, at 6:54 PM, Jeremy Lakeman wrote:
>> 
>>> Serval's software is available here
>>> https://github.com/servalproject/batphone The specific pieces
>>> you might want to look at are;
>>> 
>>> data/conf/wifichipsets/ 
>>> src/org/servalproject/system/ChipsetDetection.java 
>>> src/org/servalproject/system/WiFiRadio.java
>>> 
>>> and the edify scripts are interpreted by (including the call
>>> to libhardware_legacy wifi_load_driver / wifi_unload_driver); 
>>> native/adhoc-edify/
>>> 
>>> (The data directory is zipped in the build process, and
>>> unzipped by our first run process into
>>> /data/data/org.servalproject)
>>> 
>>> And the apk is available on the market; 
>>> https://market.android.com/details?id=org.servalproject
>>> 
>>> This approach works with a fair number of stock (but rooted)
>>> handsets. We haven't gotten around to trying to using wifi
>>> supplicants that already support adhoc mode.
>>> 
>>> On Wed, Jan 11, 2012 at 9:45 AM, Hans-Christoph Steiner
>>> <hans at at.or.at> wrote:
>>>> 
>>>> Wow, that sounds quite elaborate, I'd like to see it in
>>>> action :)  Can you point us towards the code that is doing
>>>> all this?
>>>> 
>>>> My guess is that the level of detail will be needed to handle
>>>> a lot of cases, but I think we have a good chance of
>>>> simplifying things in the long run by including our own
>>>> binaries in the app for things that are not kernel mods.
>>>> 
>>>> I'd love to find a way to include kernel mods that work
>>>> across kernel versions, but I have not found a way to do
>>>> that.  It must be possible, since people like nvidia are
>>>> shipping binary kernel mods that work across a number of
>>>> kernel versions.
>>>> 
>>>> .hc
>>>> 
>>>> On Jan 10, 2012, at 5:28 PM, Jeremy Lakeman wrote:
>>>> 
>>>>> Getting Adhoc and olsrd running is something the Serval
>>>>> Mesh software is already trying to do. We default to BATMAN
>>>>> but we have a setting to run olsr instead.
>>>>> 
>>>>> We started with wifi tether's adhoc support and have tried
>>>>> to improve on it. We've written a generic approach to
>>>>> discovering how to control the wifi driver on each handset.
>>>>> For the handsets that need something different, we've got a
>>>>> bunch of text files describing file names we should be
>>>>> looking for, and a matching control script.
>>>>> 
>>>>> But if we don't have a specific script that matches this
>>>>> handset, we look through the filesystem looking for *.ko.
>>>>> Then read through every short script in /system looking for
>>>>> insmod commands and any arguments that we need to pass
>>>>> through. And we've got a fallback method that tries a load
>>>>> driver library call that may or may not work.
>>>>> 
>>>>> Hopefully one of these approaches will succeed.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Wed, Jan 11, 2012 at 7:11 AM, Hans-Christoph Steiner
>>>>> <hans at at.or.at> wrote:
>>>>>> 
>>>>>> Hey Brian,
>>>>>> 
>>>>>> I briefly checked out your code, I'll dig in more soon.
>>>>>> Did you get ad-hoc mode running after all?  I assume so
>>>>>> since you said you got olsrd running.  Apparently, on
>>>>>> some devices, you have to replace the wpa_supplicant
>>>>>> binary in order to get ad-hoc mode working: 
>>>>>> http://forum.xda-developers.com/showthread.php?t=929865
>>>>>> 
>>>>>> Cyanogenmod seems to include everything needed to run
>>>>>> ad-hoc though.
>>>>>> 
>>>>>> I just found this, which looks like it should provide us
>>>>>> with some useful code: 
>>>>>> http://code.google.com/p/adhoc-on-android/
>>>>>> 
>>>>>> On approach that might work for us is to include our own
>>>>>> custom wpa_supplicant in the app.
>>>>>> 
>>>>>> .hc
>>>>>> 
>>>>>> On Jan 10, 2012, at 2:47 PM, Brian Duggan wrote:
>>>>>> 
> Hi Commoters,
> 
> I've been doing some preliminary work on getting olsrd to work in
> a user-friendly way on Android. The first challenge is creating an
> ad-hoc interface. Google doesn't support this, and doesn't look
> like they will support ad-hoc because they feel WiFi Direct is
> functions as a replacement. See bug 82:
> 
> http://code.google.com/p/android/issues/detail?id=82
> 
> I pushed some code to the redux branch of the commotion-android 
> repository. It's half code, half comments describing what will need
> to be done to automate the entire process of creating an ad-hoc
> interface the Android Way.
> 
> It doesn't address current olsrd incompatibility with some Android
> wifi drivers, namely the dhd driver. To date, I've only been able
> to get olsrd to run stably on devices using the bcm4325 driver.
> 
> Check it out, if you're interested:
> 
> git clone -b redux
> git://git.chambana.net/commotion/commotion-android
> 
> The master branch is still an Android Wifi Tether overlay, but will
> get olsrd up and running on bcm4325 (and other non-dhd?) devices.
> Some testing would be appreciated here. It would be great to start
> probing which devices olsrd works on and which don't.
> 
> Thanks! Brian
> 
>>>>>>> _______________________________________________ 
>>>>>>> Commotion-dev mailing list 
>>>>>>> Commotion-dev at lists.chambana.net 
>>>>>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 
-
----------------------------------------------------------------------------
>>>>>> 
>>>>>> Man has survived hitherto because he was too ignorant to
>>>>>> know how to realize his wishes.  Now that he can realize
>>>>>> them, he must either change them, or perish.    -William
>>>>>> Carlos Williams
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________ 
>>>>>> Commotion-dev mailing list 
>>>>>> Commotion-dev at lists.chambana.net 
>>>>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>>>> _______________________________________________ 
>>>>> Commotion-dev mailing list 
>>>>> Commotion-dev at lists.chambana.net 
>>>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>>> 
>>>> 
>>>> 
>>>> ----------------------------------------------------------------------------
>>>>
>>>>
>>>> 
There is no way to peace, peace is the way.       -A.J. Muste
>>>> 
>>>> 
>>> _______________________________________________ Commotion-dev
>>> mailing list Commotion-dev at lists.chambana.net 
>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>> 
>> 
>> 
>> 
>> ----------------------------------------------------------------------------
>>
>>
>> 
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out how
to use my telephone."  --Bjarne Stroustrup (creator of C++)
>> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPKsVaAAoJEJ8P5Yc3S76BhPQQAJ3v46bDjq+0uMbgWIDK5+Sc
N2NlXrI5gtbHTgSh8NrI2Qlx+YfFRV+LdlclN60vwVCHh46MAy/UHnAbnjKGkxZE
9MURA+Ih00ebL/DH2h62XAp3D9bakJxVTAyjZvrmAUAAImrZ6EqZOc4E1t64BbSp
kAlupVltmo0Y18FGzn56mKm0ts3r1ThRe3WMrp3RmLxOog2NM1j9eVTNOJkfmZyO
UZUNwk8/N9BwP7LM2ZTH5Y+qgfeO1tYmJYJY2wiakru5jAEuWqdjmRYa/JyCz01O
TkvkPHrEM1XS+sMvI7AiJHaM0H+tXDESmZxv1NuGsABh5nAUaPBRszRQTu+zM+tn
Hho4H2eI2/tYsv9wvwvPzQdHSlS4usuHO89BBYSOuyWY2jNAtyzJgQbCY/ATzMRY
Mal0jEvDjiXUr3oBLAbyXB+vcWOQHL/IEd000NiwWcE44f4wYpom4rabD4ffDhjA
CAd7FSIzfQV9UYh62+Gw+uUp1Z98GcGT7bMEb3jGPkuJXMpM2eBLMuRvmfVXvdKD
gqJHteyw7V7FOsySq27Rvs8TUsoT/22+FcbxLnSk4Q/NkUu9Pxowtw0xrWPjsIMs
gCAbYkHHy4GtGYwO/Nv0f8aeehlxxeDx6hzIV7TYDkgz5hQa+1M7N7HUjB/2MGKW
p5PB0s+w2E4Va+9LU9MZ
=8an5
-----END PGP SIGNATURE-----


More information about the Commotion-dev mailing list