System time format is not always respected

[Porkepix]

I can show a screenshot if necessary, but I think explanations are going to be enough: my device is set to use en(US) locale, but I'm pretty uncomfortable with 12H time format, so it's set on 24H time format. Problem is that, at least on the widget (I have not checked everything else), it seems to sometimes respect this 24H time format… and sometimes not and instead display AM/PM hours.

As it's not bound to a particular event, I don't think I can provide useful logs from adb logcat, right?

[robinpaulson]

Interesting, but maybe could you provide logs anyway? They might be useless, but you never know.

[Porkepix]

Well problem is that I don't know what can I look for or try to provide: usually when I report a bug for an Android application, you can do something that trigger that bug, so I fire adb logcat, reproduce the bug and grab what's related to the application.

Here it's related to the widget which just stand here without me doing anything.

[robinpaulson]

Perhaps at boot time, or when the data is refreshed? Set data to "Manual refresh", then start logcat and request forecastie get new data.

[robinpaulson]

See #437 for a list of other bugs and info which may be relevant here.

[Porkepix]

I'll try to gather something but honestly I thing that getting useful logs for this bug will be quite difficult. Well, at least I got #438 that triggered that I'd forgotten about.

[Porkepix]

Just did a reboot, but well, unfortunately format is respected this time, so due to random times it's using wrong time format, I need to catch one time where format is wrong and I have computer at hand. Will keep an eye on it.

Unrelated, but by rebooting it and having an adb logcat waiting for Forecastie, I grabbed those lines, if those may be useful for you considering the strange message:

$ adb logcat -v threadtime | rg -i forecastie
02-02 13:18:45.795   906   906 W PackageManager: Not granting permission android.permission.ACCESS_COARSE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:18:45.795   906   906 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:18:47.127   906  2848 W PackageManager: Not granting permission android.permission.ACCESS_COARSE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:18:47.127   906  2848 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:18:56.606   906   984 W PackageManager: Not granting permission android.permission.ACCESS_COARSE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:18:56.606   906   984 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package cz.martykan.forecastie because it was previously installed without
02-02 13:19:10.464   906  3897 I ActivityManager: Start proc 6078:cz.martykan.forecastie/u0a277 for broadcast cz.martykan.forecastie/.widgets.TimeWidgetProvider
02-02 13:19:10.547  6078  6078 W System  : ClassLoader referenced unknown path: /data/app/cz.martykan.forecastie-1/lib/arm
02-02 13:19:14.570   906  3292 I ActivityManager: Killing 6078:cz.martykan.forecastie/u0a277 (adj 15): empty #17
02-02 13:19:38.421   906  4199 I ActivityManager: Start proc 8066:cz.martykan.forecastie/u0a277 for broadcast cz.martykan.forecastie/.AlarmReceiver
02-02 13:19:38.473  8066  8066 W System  : ClassLoader referenced unknown path: /data/app/cz.martykan.forecastie-1/lib/arm
02-02 13:19:46.567   906  3864 I ActivityManager: Killing 8066:cz.martykan.forecastie/u0a277 (adj 15): empty #17
02-02 13:20:08.074   906   923 I ActivityManager: Start proc 10168:cz.martykan.forecastie/u0a277 for broadcast cz.martykan.forecastie/.widgets.TimeWidgetProvider
02-02 13:20:08.175 10168 10168 W System  : ClassLoader referenced unknown path: /data/app/cz.martykan.forecastie-1/lib/arm
02-02 13:20:12.261   906  4190 I ActivityManager: Killing 10168:cz.martykan.forecastie/u0a277 (adj 15): empty #17
02-02 13:20:14.295   906   924 I ActivityManager: Start proc 10765:cz.martykan.forecastie/u0a277 for broadcast cz.martykan.forecastie/.AlarmReceiver
02-02 13:20:14.359 10765 10765 W System  : ClassLoader referenced unknown path: /data/app/cz.martykan.forecastie-1/lib/arm
02-02 13:20:28.107   906  3885 I ActivityManager: Killing 10765:cz.martykan.forecastie/u0a277 (adj 15): empty #17
02-02 13:20:30.023   906   940 I ActivityManager: Start proc 11579:cz.martykan.forecastie/u0a277 for broadcast cz.martykan.forecastie/.widgets.TimeWidgetProvider
02-02 13:20:30.088 11579 11579 W System  : ClassLoader referenced unknown path: /data/app/cz.martykan.forecastie-1/lib/arm

(And I just checked before posting for the first part of these logs, Forecastie does have the Location permission sets to allow)

[Porkepix]

Noticed it earlier again and fired my adb logcat. Nothing relevant, sadly :( I don't think I'll be able to get any useful logs for this issue :/ (and even any log at all).

[robinpaulson]

OK, thanks for trying.

[igor-cali]

@Porkepix Could you post 2 screenshots, with correct and wrong time formats?

[Porkepix]

I'll do if I can see the issue again, I already did a screenshot of the normal case, with 24H format. I didn't see the widget displaying a 12H format time since your request.

[Porkepix]

@igor-cali So here it is, even though I don't think screenshots can bring any more useful information:

[ildar]

Force stopping Forecastie helped.

[ildar]

and that ugly "ПП" cannot even be fixed with localization....

[robinpaulson]

@ildar what are those symbols, where do they come from?

[ildar]

See my screenshot in my previous message?

[robinpaulson]

Yeah I see the symbols, but what do they mean?

[ildar]

PM in Russian (После Полудня)