@jrepetti : Please note that public-test builds are used for testing bugfixes with users.
Official releases will be published through official channels. use at your own risks 
has anyone tried the local time fix described by Achilles for the 2.9 version yet? I can get the autostart.sh file in the Configfiles folder with the line “systemctl set-environment TZ=US/North_Dakota” in it but it does not change the time to the local time (CST).
@toxlab said:
has anyone tried the local time fix described by Achilles for the 2.9 version yet? I can get the autostart.sh file in the Configfiles folder with the line “systemctl set-environment TZ=US/North_Dakota” in it but it does not change the time to the local time (CST).
For me it is working. The timezone entries are case sensitive. For your location you have to enter:
“America/North_Dakota/” and then also “Beula”, “Center” or “New_Salem”.
Feedback is appreciated guys, lets us know how this build works for you
@LongChair So far so good. I did the time-zone correction (Europe/Amsterdam) and that worked fine. My experience is that these releases are functioning ok on my very old Intel NUC. There is a cosmetic issue in the usermenu where the options to logout is scrambled. But only in Dutch. English is OK. Other languages I didn’t try.
A tar files for easy updating would be nice, but no more than that. For now I do not know if I can create such a file from the files within the gz file. I’ll start a quest on Google tonight.
Thank you for your effort.
@nveede : tar files are available at the link above afaik.
Just copy them to /storage/.update and reboot.
@LongChair My bad! I was mixing up this version with ones built by Lamarios. It was an easy update using the tar files.
@Sonnyboy666 said:
@toxlab said:
has anyone tried the local time fix described by Achilles for the 2.9 version yet? I can get the autostart.sh file in the Configfiles folder with the line “systemctl set-environment TZ=US/North_Dakota” in it but it does not change the time to the local time (CST).For me it is working. The timezone entries are case sensitive. For your location you have to enter:
“America/North_Dakota/” and then also “Beula”, “Center” or “New_Salem”.
Thanks! That worked for me, but i changed it to America/Chicago (didn’t see that the first time). Having grown up in ND and Minnesota it is strange those cities in ND were in there: unless you lived in those areas you would not have a clue where those cities were located!
@LongChair - Thank you for releasing an updated nightly build. I will switch over to this build and provide feedback.
Since installing the nightly build every click of the remote registers as 2 clicks.
@dsp5500 said:
Since installing the nightly build every click of the remote registers as 2 clicks.
Disable the LIRC setting under System-Settings. This could help
@Sonnyboy666 said:
@dsp5500 said:
Since installing the nightly build every click of the remote registers as 2 clicks.Disable the LIRC setting under System-Settings. This could help
Why would you suggest that? So that the remote doesnt work now at all?
The LIRC support is now within the Kernel. It’s not needed anymore in most situations.
Any one else having problems with double clicking when using remote? Its unusable as is.
@dsp5500 said:
Any one else having problems with double clicking when using remote? Its unusable as is.
Maybe a noob question, but I’m curious: in which situation does one use double clicking using a remote?
I dit attach a LIRC device and using a Logitech Harmony I have no problems controlling the unit.
I’m Not a developer, but I think it’s for some rare cases when the remote device cannot use the Kernel-LIRC.
@dsp5500 said:
@Sonnyboy666 said:
@dsp5500 said:
Since installing the nightly build every click of the remote registers as 2 clicks.Disable the LIRC setting under System-Settings. This could help
Why would you suggest that? So that the remote doesnt work now at all?
Make sur you have LIRC disabled in PMP settings, otherwise you will get one press from kernel and one from LIRC.
What should the settings in remote.conf be? I have REMOTE_BACKEND=“lirc”
I manually try to change:
},
“system”: {
“lircd_enabled”: true,
to false but on reset it auto changes back to true.
Its so random. Changed
REMOTE_BACKEND=“none”
and
“lircd_enabled”:false,
On reboot:
remote backend didn’t change
but
“lircd_enabled”: changed to true
remote now works with single clicks.
lircd is enabled in system setting on screen.
