Home Groups rb rb.comp rb.comp.rootbadger rb.comp.rootbadger.testing For those testing Rootbadger App

Thread overview

For those testing Rootbadger App

Viewing: rb.comp.rootbadger.testing Newsgroups: rb.comp.rootbadger.testing Started by yodabytz 2 messages 0 useful marks 0 vote points Last activity 3 days ago

Back to group RSS Start new thread

Root message • Message-ID: <a93821ff-9cd2-4b40-b6b9-1efe3aec9653@rootbadger.com> • 5 lines

For those testing Rootbadger App

yodabytz <yodabytz@holonet.sith> Sun, 14 Jun 2026 11:17:25 -0400

Message metadata

From: yodabytz <yodabytz@holonet.sith>

Newsgroups: rb.comp.rootbadger.testing

Subject: For those testing Rootbadger App

Date: Sun, 14 Jun 2026 11:17:25 -0400

Message-ID: <a93821ff-9cd2-4b40-b6b9-1efe3aec9653@rootbadger.com>

Organization: The Darkside

X-Info: Open Source Developer since 1997

User-Agent: RootBadger Web

Lines: 5

X-System: RootBadger/1.0 (privacy-protected)

Let me know your findings.

One bug I see already is that unsub from groups has an issue. But, before fixing that one little thing, let's get some other input.

We also need more testers. If you know someone with an Android and they would like to help test it, have them email yodabytz at gmail.com

--
yodabytz

"Debugging the galaxy, one bite at a time."

1 reply

↩ in reply to yodabytz

Message metadata

From: Lucas <fieldtech@oldiron.dev>

Newsgroups: rb.comp.rootbadger.testing

Subject: Re: For those testing Rootbadger App

Date: Sun, 14 Jun 2026 12:27:54 -0400

Message-ID: <3aa4c86b-78f9-4e36-9d60-8fda2e02a1ac@rootbadger.com>

References: <a93821ff-9cd2-4b40-b6b9-1efe3aec9653@rootbadger.com>

Followup-To: rb.comp.rootbadger.testing

Organization: The Null Device Restoration Society

X-Info: interested in old systems, new mistakes, and anything that still works after being dropped

User-Agent: RootBadger Web

Lines: 3

X-System: RootBadger/1.0 (privacy-protected)

Good place to start. Besides the unsubscribe bug, I would watch the unglamorous Android stuff first: login/session expiry, rotating the phone mid-compose, drafts surviving app backgrounding, bad network retries, and whether reply/post errors are visible instead of silently eating text.

For tester reports, a tiny template would help: device model, Android version, app version/build, steps to reproduce, expected vs actual, and a screenshot/log if available. Boring checklist, fewer ghosts in the machine.

--
Lucas // still waiting for the future to finish booting