Topics

Andflmsg; forms do not want to save to outbox

Ole Helgerson KI7MBR
 

Greetings,

Have installed Andflmsg (either 1.2.0 or 1.2.1) on three Android devices; Moto G 2nd Gen (Android 6.0), Nokia 3.1 (Android 8.1.0) and Samsung Tab A (Android 5.1.1).

A very nifty set up, especially as compared to setting up and using the desktop version of Fldigi or Winlink.

Practiced sending messages both text and using forms one device to another "mic-to-speaker" first with devices next to each other on a table and next radio-to-radio with Android devices adjoining the sending and receiving radios with no problem (though the older Moto G tended to drop characters or shut down after transmission or both).   Lastly the Easy Digi interface was tested with a minor technical linking issue to resolve (1) and again the Nokia and Samsung came through in fine fashion.   The newer Nokia and Samsung seemed quite reliable.

And then.....all devices ceased to save any filled out forms to the outbox.   All would happily re-transmit (forward) any received forms. But pressing long or slow on the  [Submit, Save in Outbox] tab resulted in nothing subsequently showing up in the [Outbox] when it was pressed either long or slow.  Likewise for saving as draft.

Attempted solutions: 1) Close out and restart Andflmsg. Results; no change. 2) Restart android device. Result; no change. 3) Delete ver. 1.2.0 and load ver.1.2.1 on the Nokia. Result; no change.

As for file storage, the Samsung is; Internal Storage / AndFlmsg / NBEMS, AndFlmsg_1.2.1_20170505.apk.  The Nokia is; SanDisc SD Card / AndFldigi / AndFlmsg_1.2.1_20170505.apk, with NBEMS.files also directly under the SandDisc

It was working very smoothly, until this bump in the road.  Had not changed any settings that I can recall.....  Can't think of anything more to try.

Suggestions most welcome!

Kind thanks in advance.

73 KI7MBR
Ole

(1) Quick report of how things worked out with Easy Digi interface with the Icom T70 ht.  Bottom line; all Android devices received well when directly plugged into the Icom via Easy Digi.  Transmission, however, seems to required having the factory OPC-2006 cable between the radio and Easy Digi to activate the radio's VOX circuitry. Only the 2.5mm pin from the Easy Digi connects with the OPC cable.  Sort of like having to shift gears instead of relying on an automatic tranny in a car. Easy Digi found on eBay, courtesy Clifford Wareham KF5INZ 

Ole Helgerson KI7MBR
 

Update. 

Re sending to the outbox, seems to work better now.  A workaround is to save to draft then to outbox.

Workaround found for Easy Digi

Tried soldering a jumper between the mic and sdeaker ground inside the Easy Digi box.  This linked the two grounds as they are with the Icom OPC2006 connector cable for their head set.  Still did not activate VOX.

Work arounds;

1.  Insert the Easy Digi's 2.5 and 3.5 mm plugs into the Icom, key the mic then press send on the Android device.
2.  Use the Icom OPC 2006 connector cable and VOX function to send (it holds only the 2.5 mm cable from Easy Digi, need to plug the Easy Dirig directly into the radio to receive). 

No worries.  Tried both methods the other day connecting the Nokia phone via Easy digi to the Icom ht, sending to the Alinco mobile with a Samsung 6" tablet simply resting atop the radio.  Then swapped send and receive Android devices.  Bopth seemed to send and receive with both Easy Digi attachment methods. Though, the Samsung took a couple of tries on the receiving end to log the html file.   With the Icom OPC2006 capble activating vox there seemed to be some mic clicks in the stream that were not there when simply keying the mic.

This info is probably elementary for most, but hope it is useful

73 KI7MBR

John (vk2eta)
 

Hello Ole,

Strange. A few things come to mind:
1. Maybe some permission issues. Can you try to uninstall and re-install, choosing the default storage option. The files will be in the internal storage under NBEMS.files.

2. The submit buttons on the HTML form only respond to a single short press. You know it is triggered as the form is closed.

3. There is version 1.3.7 now on Sourceforge under the Fldigi project, in the AndFlmsg folder. It may fix the old moto device shutting down (fixed some memory leaks and data mismatches).

Hope that helps.

73, John (VK2ETA)

Ole Helgerson KI7MBR
 

John,

Thanks for the useful suggestions.  Will check them out.   Kindest regards,  Ole


On Sun, Sep 22, 2019 at 5:45 AM John (vk2eta) <vk2eta@...> wrote:
Hello Ole,

Strange. A few things come to mind:
1. Maybe some permission issues. Can you try to uninstall and re-install, choosing the default storage option. The files will be in the internal storage under NBEMS.files.

2. The submit buttons on the HTML form only respond to a single short press. You know it is triggered as the form is closed.

3. There is version 1.3.7 now on Sourceforge under the Fldigi project, in the AndFlmsg folder. It may fix the old moto device shutting down (fixed some memory leaks and data mismatches).

Hope that helps.

73, John (VK2ETA)