<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I can confirm that the Samsung Galaxy Nexus does *not* work for Mesh
Tether. Though it appears to work with Serval.<br>
<br>
Will Hawkins and I were talking about having a discussion soon to
plan how to improve Commotion-Android's adhoc support, now that DR1
is out. There has been past discussion on this list about how Mesh
Tether, Serval, and SPAN all do ad-hoc differently, and we should
figure out concretely how we want to move forward on this. It would
be beneficial to get everyone's thoughts and expertise on this
planning. Perhaps we can start a separate thread about that, if you
think that's needed.<br>
<br>
<div class="moz-cite-prefix">On 03/17/2013 04:39 PM, Andrew Reynolds
wrote:<br>
</div>
<blockquote cite="mid:51462A10.3040104@opentechinstitute.org"
type="cite">
<pre wrap="">Thanks for the prod.
The Motorola Atrix 4G on 2.3.6 works consistently.
-andrew
On 03/17/2013 04:01 PM, Ben West wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi All,
I've been surfing the listserv archive, and pestering poor Hans, in search
of a handset known to be compatible with the Mesh Tether app, and similarly
with Serval. I would like to get such handset myself.
However, since Mesh Tether is known NOT to work with AndroidOS 4.x, I have
to locate older, used handsets, adding to the challenge.
Many devices have been reported on this listserv as possibly working.
However, I believe Hans clarified that only these devices are known to work
fully.
- HTC Desire running android 2.3
- HTC Wildfire running CyanogenMod 6.1.0
- In general, HTC devices running 2.x (especially the Incredible)
- Google Nexus One (stock 2.3.3), and *NOT* any newer Nexi
In contrast, these devices have been reported to work somewhat, but are
expected to be flakey:
- HTC myTouch 3G (kind of works)
- Samsung Tabs running Android 3.2
- Samsung Galaxy S2
- Samsung Galaxy Player 5.0 running stock 2.3.3 (works only sometimes)
- Motorola Droid/Milestone running CyanogenMod 7 (mostly works)
Hans mentioned that although Samsung handsets appear work, and have been
tested to a small extent, they are expected to be quite flakey/unreliable.
Likewise, the Samsungs require custom kernels and/or custom kernel options
specified at boot, correct?
Please respond to this thread if you have successfully tested a handset,
and tested it for reasonable duration of time to ensure no flakiness. Or,
please respond if any of the handset mentioned above is incorrectly listed
as working.
Ideally, the responses to this thread can be used to better populate this
list on the wiki:
<a class="moz-txt-link-freetext" href="https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware">https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware</a>
_______________________________________________
Commotion-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a>
<a class="moz-txt-link-freetext" href="https://lists.chambana.net/mailman/listinfo/commotion-dev">https://lists.chambana.net/mailman/listinfo/commotion-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Commotion-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a>
<a class="moz-txt-link-freetext" href="https://lists.chambana.net/mailman/listinfo/commotion-dev">https://lists.chambana.net/mailman/listinfo/commotion-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dan Staples
Open Technology Institute
<a class="moz-txt-link-freetext" href="https://commotionwireless.net">https://commotionwireless.net</a></pre>
</body>
</html>