I have the dev version installed. In the settings I do not find any way to export or watch the current log.
I can open the technical test mode but that does not show anY logs either. The ETM settings are not scrollable, btw.
Having to root the device? That does not work for most normal users. Should it not be as easy as possible for users to contribute logs in order to help understand the issues?
I guess it is fine to discuss that with the developers in Github.
My current best guess (yes I am working at the company and should know, but would need to ask since I can’t tell at the moment) that is is a very technical features that only a small amount of the user base would use or even understand.
However I can image that a typical “hit the version number 5 times to active” could be a solution to that, same like Android itself does it or the Talk desktop client.
Maybe because they are DEV releases, which likely stands for DEVeloper. And I’d guess DEVelopers are likely running the app in Android Studio while doing DEVeloper things, where becoming root isn’t an issue
That sounds like a great idea to me! It could even be integrated into the regular releases, and posting these logs could become a requirement for opening bug reports on GitHub.
My reasoning is that Devs want issues with logs. Hence it should be as easy as possible to get/submit those.
Having to install a different package from a different app store is already a hurdle I do not understand in terms of easing submitting issues with logs, or even starting threads here with logs. If you open an issue or topic for the server, the first question is, what do the logs say.
So if having installed the different app is not even enough, the likelihood of users submitting logs decreases further.
Yeah, as I said. I think it would be a good idea, to provide this as an option, maybe even more so in the regular releases than in the DEV releases, as @Andy said, maybe by “hitting the version number 5 times to ebable it” or something like that.
But maybe there are also valid reasons not to do that in the DEV or regular release, I didn’t think of. Still, as @Andy said, it’s definitely a valid point you could raise in an issue on GitHub.