🚀 You're Invited: Beta Test the Next Generation of openScale 3.0

[oliexdev]

Hello openScale community,

Now, I'm excited to announce a landmark undertaking for the main openScale app, with the ultimate goal of releasing this major new version as openScale 3.0! I've embarked on a complete rewrite of the application, rebuilding it from the ground up in Kotlin to replace the original Java codebase. This ambitious project aims to create a more robust, maintainable, and modern foundation for openScale's future.

A big thank you to everyone who participated in the closed beta of openScale 3.0 🙏

With your help openScale 3.0 is now available as an open beta on Google Play!
This means anyone can join the testing, try out the new features, and share feedback to make the upcoming production release even better.

---

What's New in openScale 3.0 🚀

This beta represents a significant architectural shift as we work towards openScale 3.0:

• Complete App Rewrite in Kotlin: The entire application has been rewritten in Kotlin. This provides a modern codebase for improved performance, stability, and easier future development, forming the backbone of the next major version.
• New Bluetooth Communication Stack (Ongoing): As part of the rewrite, the underlying system for Bluetooth communication has been modernized. The goal is to improve reliability and prepare for easier integration of future devices.
• User Interface Enhancements: You'll notice some initial updates to the UI as I begin to refresh the app's look and feel. This is an ongoing process.
• Foundation for the Future: The primary objective of this rewrite is to build a solid, modern foundation for all future openScale development.

---

What You'll Be Testing 📋

This beta is a critical step, and your focus will be on:

1. Core Application Stability

   • Testing general app navigation, manual data entry, viewing history, and overall responsiveness of the new Kotlin-based app.

2. Bluetooth Scale Functionality (NEEDS YOUR HELP):

   • While the app itself is rewritten in Kotlin and includes a new Bluetooth communication foundation, the individual drivers for most existing Bluetooth scales still need to be ported from the old Java implementation to this new Kotlin-based system.
   • This is a significant task, and I urgently need assistance from users who own specific Bluetooth scales and are willing to help test (and ideally, contribute to porting) these drivers. This is essential for achieving broad device compatibility in openScale 3.0.
   • If you own a Bluetooth scale previously supported by openScale, your primary testing task will be to:
     • Check if it connects at all with this new beta.
     • Report in detail what happens (or doesn't happen).
     • Provide logs if possible (more instructions on this if you join the beta).
   • Your feedback here is absolutely critical. Without successful porting and testing of these scale drivers, the new version cannot fully replace the old one with the same device support.

3. Identifying Regressions:

   • Given the complete rewrite, it's inevitable that some functionalities from the previous openScale app might not yet be implemented or might behave differently in this first beta.
   • Please report any critical missing features or features that no longer work as you expect.

I appreciate your understanding that this beta is a work-in-progress and will initially have limitations, especially concerning out-of-the-box Bluetooth scale support and some still missing features as we build towards a comprehensive openScale 3.0.

---

Screenshots: A Glimpse of the Beta 👀

Get a first look at the current state of the user interface for the upcoming major openScale 3.0 release:

Main Screen	Chart Screen	Table Screen	Statistic Screen

---

Contributions are Welcome! ❤️

Beyond testing and providing feedback, I warmly welcome code contributions! If you're a developer and interested in helping to accelerate the development of openScale 3.0, especially with porting Bluetooth scale drivers or tackling other issues:

• Please check out the ``openScale-3.0 branch on our GitHub repository.
• Feel free to pick up an existing issue or discuss a new feature/fix you'd like to work on.
• Pull Requests are highly encouraged against the openScale-3.0 branch.

Let's build the next generation of openScale together!

---

Providing Feedback 🤔

During the beta testing period, please report any bugs, crashes, or unexpected behavior by opening a new issue on this GitHub repository. Please include as much detail as possible:

• Your Device model and Android version.
• The specific model of your Bluetooth scale (very important!).
• Clear steps to reproduce the issue.
• Any relevant error messages or screenshots.
• Attach a debug log file — this is extremely helpful! Enable logging via Settings → General → Enable log file, then reproduce the issue and attach/share the generated log to the issue.
• If testing a Bluetooth scale, describe its behavior in older openScale versions versus this beta.

Your detailed feedback, especially concerning Bluetooth scale integration, is invaluable as I work towards the release of openScale 3.0.

Thank you in advance for your willingness to help bring this next major release of openScale 3.0 to life! Your contributions are highly valued.

Best regards,
olie.xdev

[CaffeineOnIce]

I'd like to beta test the app, if possible. I have a smart scale, that it connects to, but has some bugs.

[oliexdev]

@CaffeineOnIce yeah sure send me an email with your Gmail address

[bsimmo]

Sign me up if I can be another user to add.

[jmventar]

Sent email for beta signup ✅

[oliexdev]

@bsimmo I need your googlemail address for that
@jmventar done

[Nefari0uss]

Sent an email.

[bsimmo]

How do you want feedback on V3 to be provided (to keep it from v2 feedback/bugs) in the Issues?

I'll add my details later, but it's working.

Feedback 1 - Icons/Avatars/selfie for different users so visually you can see who you are reading about.
Feedback 2 - Stone/lb not Stone/decimal fraction of stone (I'm from UK so switch between stone-lb and kg, but never use decimal stones)
Query 1 - When I altered weight to Stone, about said something about changing numbers, why? what is it doing? It should just read everything in the default unit (kg) and then use a conversion at run time for the gui preference. It shouldn't alter the data. (this is what I had my updated version of WiiScale do). Not least because converting it back adds error. Did I mention we switch between kg on stone regularly when using it in different places.

It's working really nice, going to have a wider play with it. thanks.

[woaloo]

Hello,
I installed beta 3 to test it with the RENPHO ES-CS20M scale. The initial setup went well, and the scale is connected to the app. However, the first time I weighed in, the app crashed and closed immediately.

[oliexdev]

How do you want feedback on V3 to be provided (to keep it from v2 feedback/bugs) in the Issues?

Create a new issue, see above "Providing Feedback" section

I'll add my details later, but it's working.

Feedback 1 - Icons/Avatars/selfie for different users so visually you can see who you are reading about.

good idea will keep that in mind

Feedback 2 - Stone/lb not Stone/decimal fraction of stone (I'm from UK so switch between stone-lb and kg, but never use decimal stones)

I am not from UK could you describe it more in detail.

Query 1 - When I altered weight to Stone, about said something about changing numbers, why? what is it doing? It should just read everything in the default unit (kg) and then use a conversion at run time for the gui preference. It shouldn't alter the data. (this is what I had my updated version of WiiScale do). Not least because converting it back adds error. Did I mention we switch between kg on stone regularly when using it in different places.

The behavior is intentional. I keep kilograms as the canonical store, and when you change the unit preference I refresh cached display conversions (e.g., to stone) so large datasets don’t have to be recomputed across every view. The raw kg data isn’t altered; round-trip conversions use precise factors, so any drift beyond UI rounding would be a bug—please share an example if you see one. That said, I’m a bit surprised the units are switched so often—could you explain why you regularly toggle between kg and stone?

I installed beta 3 to test it with the RENPHO ES-CS20M scale. The initial setup went well, and the scale is connected to the app. However, the first time I weighed in, the app crashed and closed immediately.

Please provide the log file but could be possible that this issue is a scale problem, search for it in the issue.

[gassssss]

Hi, I'm already testing the beta downloading through github directly, so far is OK. This is the second time I try and it imported the old db without issues, recognized the scale (Mengii) and grabbed the data correctly.

The reason I went back to the stable version (and probably will go back again) is that idk why every time I try to update the beta (by github download/install) I get the message that it conflicts with an existing package, forcing to uninstall-reinstall-reconfigure-import which gets annoying after a few times. Not sure if it is a skill issue or what, but I have a degoogled phone can't/won't join the GPlay test.

Nonetheless is looking great so far, thanks a lot for your work.

[oliexdev]

Thanks for your feedback, yes that's normal if you are using the latest beta or dev build on GitHub because I won't update the internal version code. Later if the version 3.0 is more stable it will also be released on f-droid then you can use that instead of GooglePlay. But currently the version 3.0 is highly in development, any feedback is welcomed.