[chirp_users] CHIRP for Android?

[Rich Barstow]

Thanks to all for the responses.

Q: Where would be the place to start discussion around an Android effort?

Based on the comments in the linked Feature #1369, Android is not in scope
or on the roadmap for the existing development team.  It sounds as if the
existing code base could be forked for the new platform, based on the
existing separation between the driver/radio/clone logic and UI. The fact
that there is a commandline tool (even if very neglected) may provide an
additional starting point.

Ideally, I'd like a new community of developers (I have some in mind) to
support such an effort, so as to not add work to the existing devs. At the
same time, there's a tremendous amount of knowledge the existing team has
developed, and I'd like to leverage as much of that as is reasonable.

Disclaimer: I'm not a developer (I've done it, and I know what I'm not good
at). Scripting and admin-type work, or project management, that I can do.




On Sun, Apr 6, 2014 at 12:30 PM, John LaMartina <JohnLa at usa.net> wrote:

> I agree with Milt.
> I blew the dust off my wife's old Asus Netbook.
> Great for field programming with CHIRP
>
> John K3NXU
> http://www.miklor.com
>
>
>
>
>
> *From:* chirp_users-bounces at intrepid.danplanet.com [mailto:
> chirp_users-bounces at intrepid.danplanet.com] *On Behalf Of *Milton Hywatt
> *Sent:* Sunday, April 06, 2014 11:43 AM
> *To:* Discussion of CHIRP
> *Subject:* Re: [chirp_users] CHIRP for Android?
>
>
>
> Chirp works well on my 10" Dell Netbook
> and Windows XP all on a 7.5 gigabyte solid
> state hard drive. I picked mine up used for $75.
> off Ebay. I use a USB mouse and keyboard if
> I need a little bigger keyboard. Probably a good
> way to go if you plan on using Chirp in the field.
>
>
>
>
> ------------------------------
>
> *From:* Ronny Julian <k4rjjradio at gmail.com>
> *To:* Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> *Sent:* Sunday, April 6, 2014 11:29 AM
> *Subject:* Re: [chirp_users] CHIRP for Android?
>
>
>
> If what you want is a small footprint computer running CHIRP to carry in a
> go box try a Raspberry Pi or a Beaglebone Black.  Both will fill the bill
> just fine.
>
>
>
>
>
> On Sun, Apr 6, 2014 at 11:20 AM, Tom Hayward <esarfl at gmail.com> wrote:
>
> On Sun, Apr 6, 2014 at 8:11 AM, Rich Barstow <kc1bhr at barstow.cx> wrote:
> > Forgive me for asking, but I searched the last few months of mailing list
> > archives, both on the user and the dev side, without finding a roadmap or
> > references to an Android version.
> >
> > Are there any plans?  If not, what's the best way to contact the
> developers
> > to discuss?
> > If yes, how can I offer assistance? (testing or coding)
>
> The reason you don't see it discussed here often is because it's in the
> FAQ.
>
> Some of the technical issues are listed here:
> http://chirp.danplanet.com/issues/1369
>
> Feel free to discuss a port of Chirp to Android, but realize that none
> of the GUI code is compatible. The underlying radio clone code should
> run fine on Android devices with serial ports. If you are an Android
> developer with some free time, you could make a few people happy by
> rewriting Chirp for Android.
>
> Tom KD7LXL
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20140406/4429457b/attachment.html