<p dir="ltr">Much of the Python code should work on Android without much problem given the existing Android port of Python. Much of the underlying driver stack (USB, etc) is even the same with Chirp/Python/Linux because Linux often uses the same chipsets used in Android hardware.</p>
<p dir="ltr">The problem, as I understand it, is that the Chirp Graphical User Interface has not been ported and is not expected to ever be. That does not prevent the use of a new GUI on Android making the same Python calls that the Chirp GUI now does. At the very least, it *should* be possible to make an Android app which allows some *basic tasks* to be performed from an Android phone or tablet short of what the full Chirp GUI does.</p>
<p dir="ltr">For instance, it would be handy to just be able to backup a radio's configuration or upload a preconfigured image in the field without even the ability to edit the images. Right now, we can pull a radio from our radio cache and clone handset-to-handset without Chirp. We can also field program a radio manually and clone it without Chirp. What would be useful to do from a phone would be too pull a *different* configuration (generated in Chirp elsewhere), perhaps backing up the radio first, and upload it to the radio or to download the field-programmed changes and send them to someone else.</p>
<p dir="ltr">That much should be a good test-of-concept.</p>
<p dir="ltr">On Nov 17, 2015 1:36 PM, "Tom Hayward" <<a href="mailto:tom@tomh.us">tom@tomh.us</a>> wrote:<br>
><br>
> On Tue, Nov 17, 2015 at 10:59 AM, David Ranch <<a href="mailto:chirp@trinnet.net">chirp@trinnet.net</a>> wrote:<br>
> ><br>
> > There is Python for Android so I'm curious if Chirp could indeed work<br>
> > w/o a port to native Java:<br>
> ><br>
> > <a href="https://play.google.com/store/apps/details?id=com.hipipal.qpyplus&hl=en">https://play.google.com/store/apps/details?id=com.hipipal.qpyplus&hl=en</a><br>
><br>
> Here's my list of things required for Chirp to work on Android. Not<br>
> sure if I'm missing anything.<br>
><br>
> - USB serial cable to radio<br>
> - USB OTG adapter<br>
> - USB OTG support in device hardware<br>
> - USB OTG support in device kernel<br>
> - USB serial driver for radio cable bundled in kernel (keep in mind<br>
> most Android devices use stripped down kernels without most of the<br>
> device drivers available to desktop Linux, and have locked bootloaders<br>
> preventing custom kernels)<br>
> - Linux/Android permissions for app to open serial device (like adding<br>
> yourself to dialout group on Ubuntu)<br>
> - Python for Android<br>
> - GTK 2.x for Android<br>
> - PyGTK for Android<br>
><br>
> Once these dependencies are satisfied, Chirp should work just<br>
> fine on Android. You'd probably want to add a mouse to this list,<br>
> because otherwise things like right-click menus would be inaccessible.<br>
><br>
> All these things are possible, but will take a lot of work. GTK and<br>
> PyGTK are the biggest issues for developers, while device/kernel<br>
> support will block the majority of consumers. If you want to pursue<br>
> this further, you should look into the state of GTK on Android. Short of<br>
> a rewrite, there's nothing Chirp can do about lack of GTK on Android.<br>
><br>
> Tom KD7LXL<br>
> _______________________________________________<br>
> chirp_users mailing list<br>
> <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
> To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</p>