Chart settings not working

[FaultierB]

Preflight Check (Required)

• I tested the latest dev version https://github.com/oliexdev/openScale/releases/tag/dev-build
• The issue still occurs in the dev version
• I searched the existing open and closed issues
• This issue has not already been reported or fixed

Bug Description

Some of the chart settings aren't working for me:

• There are no goal lines displayed, even when setting is "on".
• The datapoints are always simply connected, no matter what smoothing algorithm is set.
• I'm missing an option to hide the histogram above the chart. It used to be there in old versions I think, but now I can't find it anymore.

Steps to Reproduce

1. Apply chart settings for goal lines and smoothing.
2. Check chart and see that the settings are not applied.

Debug Log (Required)

| Field | Value |
|---|---|
| Time | 2026-01-16 21:13:45.759 |
| Timezone | Europe/Berlin (UTC 1h) |
| Session ID | 19bc871479f |
| App | openScale |
| Version | 3.0.2 (72) |
| Package | com.health.openscale |
| Build Type | release |
| Device | HONOR VER-N49 |
| Android | 15 (API 35) |
| Build ID | VER-N49 9.0.0.181(C431E1R2P2) |
| Build Time | 2026-01-09T00:56:12Z |
| Git SHA | 7a76b06f |


+ 2026-01-16 21:13:45.759 I/openScaleLog: File logging enabled during runtime – started fresh session log.
? 2026-01-16 21:13:45.759 D/openScaleLog: Initial markdown-diff headers written to: /storage/emulated/0/Android/data/com.health.openscale/files/logs/openScale_current_log.txt
? 2026-01-16 21:14:01.256 D/UserSettingsRepository: Setting chart smoothing algorithm to: SIMPLE_MOVING_AVERAGE

[oliexdev]

There are no goal lines displayed, even when setting is "on".

I can't reproduce it, did you add a goal?

The datapoints are always simply connected, no matter what smoothing algorithm is set.

Also I can't reproduce it. what are you datapoints with dates with which smoothing algorithm settings?

I'm missing an option to hide the histogram above the chart. It used to be there in old versions I think, but now I can't find it anymore.

You can simple drag the histogram out off the screen.

[FaultierB]

I can't reproduce it, did you add a goal?

I just realized, when I set the chart to "last 365 days", there is a goal line at the bottom of the screen (not inside the chart itself though. When I set it to "last 30 days" it's gone. I'll attach screenshots.

Also I can't reproduce it. what are you datapoints with dates with which smoothing algorithm settings?

I'll also attach a screenshot. It's in German, I don't know how to change it to English. "Gleitender Durchschnitt" is "running average".

You can simple drag the histogram out off the screen.

It just took me about 2 minutes randomly tapping, long-pressing and swiping the thing in all directions until I realized it's the horizontal bar below the histogram that I can swipe up. Maybe a little symbol like up and down arrows or little "grab lines" on that line would make that a bit more user friendly.

Now that I'm looking at it, I'm actually not convinced the extrapolation slope is correct. But I'd have to confirm that with a manual fit to the data. Will do that later.

[oliexdev]

I just realized, when I set the chart to "last 365 days", there is a goal line at the bottom of the screen (not inside the chart itself though. When I set it to "last 30 days" it's gone. I'll attach screenshots.

Thanks for the hint, should be fixed now in the latest dev version.

I'll also attach a screenshot. It's in German, I don't know how to change it to English. "Gleitender Durchschnitt" is "running average".

In the settings->general you can change the language... You could try and calculate with fewer data points, its more easier.

[FaultierB]

Thanks for the hint, should be fixed now in the latest dev version.

Cool, thank you!

In the settings->general you can change the language...

Thanks, I overlooked that setting.

You could try and calculate with fewer data points, its more easier.

Not sure I understand. No matter what I set for "window size" or "max gap" (what does the latter actually do?), the chart line stays the same. It's always just connecting the data points. No smoothing.

[oliexdev]

Not sure I understand. No matter what I set for "window size" or "max gap" (what does the latter actually do?), the chart line stays the same. It's always just connecting the data points. No smoothing.

Sure it just smoothed the data points, click on a point then the point value should be changed, see https://en.wikipedia.org/wiki/Moving_average

What does "Max Gap Days" do?

The Max Gap Days setting controls how the app's smoothing algorithms (like the Moving Average) handle periods where you haven't taken any measurements for a while.

When you apply smoothing (like a Moving Average) to your data, the algorithm usually assumes a continuous flow of measurements. However, if you stop weighing yourself for a long time (e.g., during a vacation), a standard smoothing algorithm would try to "bridge" the last measurement from weeks ago with your new measurement today. This often leads to misleading trends.

1. Detection: If the gap exceeds your limit (e.g., 14 days), the app "breaks" the line.
2. Separate Blocks: It treats the data before the holiday and after the holiday as two independent blocks.
3. Visual Result: In the graph, you will see the smoothed lines for both periods. While Vico (the charting library) might still show a visual connection between these segments to maintain a single series, the math behind the curve stays accurate. The smoothing calculation "restarts" for the new block, ensuring that a measurement from three months ago doesn't distort your current progress.

[FaultierB]

The graphs look exactly the same to me, whether smoothing is on or off. The only thing that changes is that with smoothing on, the datapoints shown for a certain time range actually start a bit later. What I would expect to see is a curve like the red line in the top right plot on the Wikipedia page.
Here are screenshots with smoothing off and on, respectively.

I also checked my earlier intuition with the extrapolation. Something is wrong here as well. The basis for the linear regression is set to 30 days. I exported the data and plotted it and as you can see, the slope should go down, not up.

[oliexdev]

could you send me your database I cannot reproduce it here.

[FaultierB]

I found the reason for the wrong slope. There was a second, wrong and too high datapoint yesterday which was not shown in the chart (which is why I didn't realize it was there, saw it in the export but thought it was a weird artifact because it was the last value). Deleted it and now it's correct.

The smoothing is unaffected though, of course. Do you still need the database for that? If so, how can I send it to you? Would prefer not to upload it publicly.

[oliexdev]

It seems there may be a misunderstanding about how the smoothing algorithm works.

Please try an extreme smoothing configuration: set the window size to 30 and the maximum gap to 30, and apply the filter to all days. This should result in a very smooth curve in the chart.

If the chart still shows no change, please send your backup for further inspection to olie.xdev@googlemail.com

[FaultierB]

Please try an extreme smoothing configuration: set the window size to 30 and the maximum gap to 30, and apply the filter to all days. This should result in a very smooth curve in the chart.

It still looks the same to me (but if I set it to "last 30 days" it now says "no data to display").

[oliexdev]

Looks like it works as intended because it makes sense if no data is shown for last 30 days because you have to few data points for the smoothing average with this kind of windows size. With the other screenshots its hard to tell because it depents how far the data points are. But send me your database and I will look into it.

[FaultierB]

Look, I found an old screenshot from the old 2.x version of the app. That is what running average used to look like (and what I would expect it to look like given the definition of running average). As you can see, the datapoints are not connected.

[oliexdev]

Ok now I know what you want, you are missing the raw points in the graph after smoothing. Ok for that I have to look more into the code, could take more time.