Josh Fowler @joshfowler@librem.one

@Blort Update for you if your interested at all. I changed branches to unstable and did a full day test today 08:00 to 22:00 and the battery is still at 50%. Wow, that's a huge improvement! Only issue I'm facing is the same bug I have with every install, it doesn't like an APN with an empty password so I have to manually enable it every time with nmcli. Might have to try and fix that myself this weekend.

@Blort Fair play! I'm going to see if I can all day the latest unstable branch of Manjaro on the PPP with the keyboard case. I think wake from suspend is fixed on it so we will see.

@Blort Honestly, I'd be happy with 12 hours with light use at the moment! I'm using the latest beta of Manjaro with Phosh, dark them of course.

You wouldn't happen to know how to convert beta to daily? Switching to the unstable branch?

@Blort What about battery life? Mine still doesn't have working wake from suspend and the time with screen off without suspend is about 3 hours.

@StampedingLonghorn @charlie_root@social.linux.pizza Timeshift is picky and only uses @root and @home partitions for the BTRFS backup, if you look at how Manjaro does automatic subvolumes then you can see how it expects the layout to be.

@charlie_root@social.linux.pizza Because early on people lost data with RAID5 (me included) then learnt that it wasn't in a usable state. However I am now using MDADM RAID5 + BCache + BTRFS which works amazingly!

@dos Camera quality is looking really good nowadays, is the colour hue etc correct?

@imakefoss First distro: Kubuntu 12.04
My college mate got me to try it. So I installed it on my laptop and couldn't get WiFi drivers working but played about with it using ethernet.
Won me over: Win8 rejecting the license I just purchased and Untangle from Simon Tatham puzzle collection.

@JF Aha, there is indeed an update for it on F-Droid. I've noticed considerably less connection issues so far with 1.8.0 btw, really happy with the update. Thank you so much for your work!

@JF It took me about an hour to get the firmware uploaded. On android via gadgetbridge I kept getting errors early on when transferring and on linux via siglo it was very slow to transfer and failed on the last 100 bits twice before succeeding. Other than that the list of new features is great! Been waiting for shake to wake for ages!

@daniel01

Not sure how you make such long posts, mine is limited to 500 characters!

I agree that price point is out of the reach of some people but then you would have to weigh speed Vs space and maybe pick up a normal HDD (~$20 for 1TB). I'm from the UK so I'm roughly guessing exchange rate.

I just installed Lagrange on flatpak and it was 3.1MB because the runtime was already on my system. I'm guessing that AppImages use the local runtime to run properly?

@silmathoron Looks like both work but I was unaware of that option! I don't see much call for starting at a specific minute and then every X minutes after that, it's usually either or but I'm glad it's there for someones use case!

If you are running everything as a systemd service then you should be able to match up the erratic behaviour with what's causing it in journalctl, if you have set up logging for that bit anyhow. Good luck with the debugging! =]

@daniel01 I'm inclined to disagree on two fronts. First, storage is fairly cheap nowadays, everything I use as a personal computer has 1TB at least. Second, I have over 60 apps installed from 3 different remotes using multiple different runtimes and the total size of ~/.local/share/flatpak/ is 13GB and I use no system remotes so that's everything. Sure, some apps use a specific runtime for their application which adds GBs but it's a small price to pay for securing proprietary software etc.

@silmathoron It may take * or 0 to mean the same thing in this instance but as you probably know * is a wildcard for any string of characters with any length and /${period} is restricting this to only match if the wildcard number is divisible by the number given.

I use this webpage as a reference:
https://silentlad.com/systemd-timers-oncalendar-(cron)-format-explained

The OnUnitActiveSec takes a seconds value so $((${period} * 60)) should help there. And you can specify if the service uses the WakeSystem.

https://www.man7.org/linux/man-pages/man5/systemd.timer.5.html

@silmathoron Think you just need to replace OnCalendar=*-*-* *:0/${period}:00
with OnCalendar=*-*-* *:*/${period}:00