While using the mobile app, I found that the frequency, band , and mode do not persist after logging a contact. This makes the POTA workflow very unhandy.
2 Likes
Thank you very much Andy, I just reported it 
2 Likes
You beat me to the punch @N0APX. I, too, am experiencing this issue. I’ve used WRL for two activations now, and it’s beginning to grow on me. I am working out some of my inefficiencies while learning the nuances of the logger. But I have two suggestions.
- When setting the mode and band at logbook config, the app would ideally migrate these inputs to the logging screen where they persist. As the user changes his freq. within the band, mode, and band should persist. When the user inputs a freq within a different band, the field automatically detects which band and automatically populates. For example, when switching from 14063 to 14063.5, the band sticks with 20m (it currently wipes the field clean). When the user jumps from 14063.5 to 7070, the band field automatically detects 40m and auto-populates.
- When logging CW contacts, the RST should auto-populate with three characters, 599. When a user taps the field and begins typing, the field should clear, allowing him to type 579. Currently, the app auto-populates with 59. As the user selects the field and begins typing, it add a third and fourth character rendering the RST as 5959 forcing the user to select, delete type, retype making the logging very clunky and time consuming.
2 Likes
@N7JTT Great suggestions! We now have the 3-character signal report for CW on the roadmap. As for the band and mode persisting and auto-populating, those issues should be resolved. I’m assuming you are using the mobile app. If so, could you make sure your app is updated to the latest version and try again?
1 Like
I am running the latest iOS app. see attached screen shots. After deleting the ‘3’
both mode and band clear.
Also, the band should automatically inherit from the known freq.
Also, when naming the logbook the park name automatically overrides the custom-given name.
2 Likes
Okay, I think I see what’s going on. Unlike the POTA website, our frequency input requires the decimal (14.063). As far as the park name overriding the logbook name, I will definitely get that turned in to the team. It certainly shouldn’t be doing that! 
1 Like
Awesome, thank you so much! That subtlety solved the problem. I do suggest throwing an error if the decimal is excluded. I’d also add some background helper characters in the field that help indicate the format the field is looking for. As an example 00.0000 or 00.000.00.
Thanks for the support.
If you guys offer a lifetime membership, I’d consider sponsoring your development efforts by joining.
2 Likes
Great ideas there! I’ll bounce this off the team and see what we come up with! As for the lifetime membership, we do have several subscription levels, but I’ll check with the CEO to see if he has any plans of that nature. We appreciate any and all feedback you have to offer!
1 Like
@N7JTT Hello again! I just wanted to let you know that the issue you reported in the mobile app is now fixed, and the app should no longer override your specified logbook name! When you get a chance, update your app to the latest version and give it a try! Thank you so much for turning this issue in, and feel free to send in any more feedback or feature requests!
73,
Andy N0APX
WRL Product Manager
1 Like
Awesome, thanks for the update!
2 Likes