[Commotion-dev] Device compatibility for Mesh Tether (and Serval?)

[Ben West]

Looks like this thread has prompted more detail to appear on the Mesh
Tether compatibility list.  Awesome!

I also added a blurb that the Motorola Atrix 2 probably would *not* work,
since it is (naturally) a completely different chipset than the Atrix 4G.
https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware

On Sun, Mar 17, 2013 at 3:39 PM, Andrew Reynolds <
andrew at opentechinstitute.org> wrote:

> 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:
> > 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:
> >
> >
> https://code.commotionwireless.net/projects/commotion/wiki/Commotion_Android_Supported_Hardware
> >
> >
> >
> > _______________________________________________
> > Commotion-dev mailing list
> > Commotion-dev at lists.chambana.net
> > https://lists.chambana.net/mailman/listinfo/commotion-dev
> >
>
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>


-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130318/c5180f65/attachment.html>