Some others ideas for a bug report page:
- it would be useful to point to https://developer.android.com/tools/logcat URL
(logcat help) to help debugging.
- An advice could be, if bug can be reproduced, to begin by an adb logcat -c
command to clean logcat and get a minimized logcat before reproduce the bug and
launch adb logcat > FILE from computer.
- If some advices can be given to help getting a logcat expurged from personnal
data, it would also help sending data which would help to debug without privacy
issue. I personnaly do not know if it can be done in an automatic way (option,
script, etc.) or if it should be done manually, and then what are the most
common keywords to search. Any idea?
- To identify bug which cause reboot, it would be helpful to give the first
lines of logcat after a reboot to help. Those first lines are obtained by
cleaning logcat just before rebooting the device with $ adb logcat -c && adb
reboot followed by `$ adb logcat > FILE` or for detailed metadata (including
timestamps) `$ adb logcat -v long> FILE`. Thoses lines will probably change
depending on the replicant version & the device, so they should be given for
Replicant 4.2 & Replicant 6 version (it could be done calling for community
for).
Any reaction?
Perhaps some (or all) is available somewhere, I would be glad to know if it is.
Regards,
- Fil Lupin.
------- Original Message -------
On Tuesday, May 2nd, 2023 at 8:32 PM, Fil Lupin via Replicant
<replicant@osuosl.org> wrote:
> Hello,
> I think there is somewhere some advices to fill a bug report.
> Could you remind me where is it?
> I think a link to those recommendations could be put in:
>
> - some header in https://redmine.replicant.us/projects/replicant/issues,
> - a pinned topic in https://redmine.replicant.us/projects/replicant/boards/33
> - the FAQ https://replicant.us/about.php#faq
>
> Would it seem useful to you?
>
> - Fil Lupin.
_______________________________________________
Replicant mailing list
Replicant@osuosl.org
https://lists.osuosl.org/mailman/listinfo/replicant
