12-18 22:26:46.712 5169 11860 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=de.corona.tracing/de.rki.coronawarnapp.ui.launcher.LauncherActivity bnds=[150,890][290,1099] (has extras)} from uid 10027 on display 0
12-18 22:26:47.117 20182 20193 I art : Background sticky concurrent mark sweep GC freed 87852(3MB) AllocSpace objects, 0(0B) LOS objects, 17% free, 13MB/16MB, paused 6.816ms total 186.719ms
12-18 22:26:47.674 20182 20193 I art : Background partial concurrent mark sweep GC freed 73097(3MB) AllocSpace objects, 11(1220KB) LOS objects, 40% free, 13MB/23MB, paused 3.602ms total 289.944ms
12-18 22:26:49.194 6502 7151 I ConnectivityReport: signalStrength of #1 updated to 0
12-18 22:26:49.617 5169 26245 I ActivityManager: START u0 {flg=0x10000 cmp=de.corona.tracing/de.rki.coronawarnapp.ui.RpiHostActivity} from uid 10235 on display 0
12-18 22:26:49.830 5169 27176 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
Ok, so it happened again (see the screenshot)
This is what the log says:
```
12-18 22:26:46.712 5169 11860 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=de.corona.tracing/de.rki.coronawarnapp.ui.launcher.LauncherActivity bnds=[150,890][290,1099] (has extras)} from uid 10027 on display 0
12-18 22:26:47.117 20182 20193 I art : Background sticky concurrent mark sweep GC freed 87852(3MB) AllocSpace objects, 0(0B) LOS objects, 17% free, 13MB/16MB, paused 6.816ms total 186.719ms
12-18 22:26:47.674 20182 20193 I art : Background partial concurrent mark sweep GC freed 73097(3MB) AllocSpace objects, 11(1220KB) LOS objects, 40% free, 13MB/23MB, paused 3.602ms total 289.944ms
12-18 22:26:49.194 6502 7151 I ConnectivityReport: signalStrength of #1 updated to 0
12-18 22:26:49.617 5169 26245 I ActivityManager: START u0 {flg=0x10000 cmp=de.corona.tracing/de.rki.coronawarnapp.ui.RpiHostActivity} from uid 10235 on display 0
12-18 22:26:49.830 5169 27176 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
```
Thanks for the screenshot. It looks like the bar chart is cropped off to the left, and like it has too much data (more than 5).
I need to investiage this further.
Thanks for the screenshot. It looks like the bar chart is cropped off to the left, and like it has too much data (more than 5).
I need to investiage this further.
I've had this happen to me as well. It happened only once, it was a few app versions back, I haven't made screenshots or exported logs. I can just confirm that I've seen this bug exactly once on my device a while back.
I've had this happen to me as well. It happened only once, it was a few app versions back, I haven't made screenshots or exported logs. I can just confirm that I've seen this bug exactly once on my device a while back.
I really don't think that the code I wrote tells the bar chart to render any days in the future. My current assumption is that this is a rendering bug caused by the negative padding that I added to the view, which might be wrongly applied while the view is still being layouted. However I have no clue how to continue investigating this.
I really don't think that the code I wrote tells the bar chart to render any days in the future. My current assumption is that this is a rendering bug caused by the negative padding that I added to the view, which might be wrongly applied while the view is still being layouted. However I have no clue how to continue investigating this.
Sometimes the bar chart is missing data for an unknown reason.
Ref.: https://social.tchncs.de/@dadosch/107379809420889951
Ok, so it happened again (see the screenshot)
This is what the log says:
Thanks for the screenshot. It looks like the bar chart is cropped off to the left, and like it has too much data (more than 5).
I need to investiage this further.
I've had this happen to me as well. It happened only once, it was a few app versions back, I haven't made screenshots or exported logs. I can just confirm that I've seen this bug exactly once on my device a while back.
I really don't think that the code I wrote tells the bar chart to render any days in the future. My current assumption is that this is a rendering bug caused by the negative padding that I added to the view, which might be wrongly applied while the view is still being layouted. However I have no clue how to continue investigating this.