Looks like this thread has prompted more detail to appear on the Mesh Tether compatibility list. Awesome!<br><br>I also added a blurb that the Motorola Atrix 2 probably would <i>not</i> work, since it is (naturally) a completely different chipset than the Atrix 4G.<br>
<a href="https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware">https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware</a><br><br><div class="gmail_quote">
On Sun, Mar 17, 2013 at 3:39 PM, Andrew Reynolds <span dir="ltr"><<a href="mailto:andrew@opentechinstitute.org" target="_blank">andrew@opentechinstitute.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the prod.<br>
<br>
The Motorola Atrix 4G on 2.3.6 works consistently.<br>
<br>
-andrew<br>
<div class="im"><br>
On 03/17/2013 04:01 PM, Ben West wrote:<br>
> Hi All,<br>
><br>
> I've been surfing the listserv archive, and pestering poor Hans, in search<br>
> of a handset known to be compatible with the Mesh Tether app, and similarly<br>
> with Serval. I would like to get such handset myself.<br>
><br>
> However, since Mesh Tether is known NOT to work with AndroidOS 4.x, I have<br>
> to locate older, used handsets, adding to the challenge.<br>
><br>
> Many devices have been reported on this listserv as possibly working.<br>
> However, I believe Hans clarified that only these devices are known to work<br>
> fully.<br>
><br>
</div>> - HTC Desire running android 2.3<br>
> - HTC Wildfire running CyanogenMod 6.1.0<br>
> - In general, HTC devices running 2.x (especially the Incredible)<br>
> - Google Nexus One (stock 2.3.3), and *NOT* any newer Nexi<br>
<div class="im">><br>
> In contrast, these devices have been reported to work somewhat, but are<br>
> expected to be flakey:<br>
><br>
</div>> - HTC myTouch 3G (kind of works)<br>
> - Samsung Tabs running Android 3.2<br>
> - Samsung Galaxy S2<br>
> - Samsung Galaxy Player 5.0 running stock 2.3.3 (works only sometimes)<br>
> - Motorola Droid/Milestone running CyanogenMod 7 (mostly works)<br>
<div class="im">><br>
> Hans mentioned that although Samsung handsets appear work, and have been<br>
> tested to a small extent, they are expected to be quite flakey/unreliable.<br>
> Likewise, the Samsungs require custom kernels and/or custom kernel options<br>
> specified at boot, correct?<br>
><br>
> Please respond to this thread if you have successfully tested a handset,<br>
> and tested it for reasonable duration of time to ensure no flakiness. Or,<br>
> please respond if any of the handset mentioned above is incorrectly listed<br>
> as working.<br>
><br>
> Ideally, the responses to this thread can be used to better populate this<br>
> list on the wiki:<br>
><br>
> <a href="https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware" target="_blank">https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware</a><br>
><br>
><br>
><br>
</div>> _______________________________________________<br>
> Commotion-dev mailing list<br>
> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
> <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
><br>
<br>
<br>
<br>_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br>
</div>