Currently the log is jumping multiple times per second to the bottom if Auto Scroll is activated.
Deactivating the ability to scroll if Auto Scroll is activated could solve this problem.
I was wondering if you are planning a horizontal version of the app. I think this would be a great addition however getting long log messages on a horizontal view might be hard.
I think even the original log viewer on Android looks quite okay... Maybe this could be improved upon
Describe the bug
When is installed new Version (Clean Install) I set the necessary IP. port is Normal 9001. When I check connection its Ok. But then when ot tries to get into "normal" mode the app is force closing.
With 1.2.3 no issues.
Have to say I appreciate your work and effort nevertheless.
I'd suggest do center the the "view lock" and "text size" button vertically so the space in between them is in the center of the screen on the y-axis.
Or maybe remove the back button and move one of the other two buttons to the left.
You could take the default value "9001" for the port if the user doesn't enter anything.
This would make the usage of the app easier if you didn't change the standard port.
If you use the app on smartphones the orange bar at the top is too wide.
Maybe there is a possibility to change the dimensions of the different elements on the logview.
I'd suggest to set the automatic check for updates to enabled on first setup. This way it is the recommended way and the user can change it if he wants so. Furthermore the users are always up-to-date
I'd love it if there was a text size for portrait mode which would get saved and one for landscape mode. So the text could have different sized depending on the rotation for optimal reading possibility. This variable should get saved. When I now change the text size and switch the rotation the text size gets set to the default 60
Describe the bug
On the first screen when the app starts there is an unnecessary back arrow on the bottom on the left that does nothing. The arrow should only be visible starting at the second screen
Smartphone (please complete the following information):
I will try to find a solution for the currently not optimal position of the back button because it hides part of the code.
Maybe a complete new approach will be better, we will see...