| T42 | <edp_17> Hi all, I need a little support about LEDs. I have created a 60-rgb.ini file in /etc/mce/. | 00:45 |
|---|---|---|
| T42 | <edp_17> When I set the BackEnd to RGB, all thre leds (red, green and blue) work ok in CSD but the wite doesn't blink (it lits up but doesn't blink). | 00:46 |
| T42 | <edp_17> When I change the BackEnd to vanilla, the white blinks, but the rest (red, green and blue) doesn't lit up, only white. | 00:46 |
| T42 | <edp_17> The 60-rgb.ini is here: https://github.com/edp17/droid-config-treltexx/blob/master/sparse/etc/mce/60-rgb.ini | 00:46 |
| T42 | <edp_17> How can I make the white blinking? Thanks. | 00:47 |
| r0kk3rz | uncomment the quirk breathing? | 00:50 |
| Thaodan | maybe we should start to put that into /usr/lib/mce | 00:53 |
| T42 | Theobald %lastname% was added by: Theobald %lastname% | 02:51 |
| T42 | 葛蓉焰 %lastname% was added by: 葛蓉焰 %lastname% | 06:27 |
| T42 | S %lastname% was added by: S %lastname% | 07:22 |
| Kabouik | From the Gitlab CI images for Pro¹, should I download the run-build-testing artifacts, or run-build artifacts? (https://gitlab.com/sailfishos-porters-ci/t5-ci/pipelines?scope=finished&page=1) | 08:58 |
| Kabouik | I assume run-build is actually the devel version, and I should stick to run-build-testing? | 09:01 |
| Kabouik | ^ TheKit @adampigg piggz | 09:02 |
| T42 | <adampigg> Kabouik: yes, -testing is preferable for users ... depends on your livel of risk acceptance ;) | 09:02 |
| T42 | <adampigg> -testing does not yet have the BT calling fix in it | 09:03 |
| T42 | <adampigg> that -should- be hte only difference | 09:03 |
| Kabouik | Well I was among the first to use SFOS on Pro¹ so I used to use devel and never had any issues | 09:03 |
| Kabouik | But the port in testing is very much useable, and stable, I might stick to that now | 09:03 |
| Kabouik | Thanks for the answer | 09:04 |
| T42 | <adampigg> sure, i did once break -devel ... thats why we have testing | 09:04 |
| T42 | <adampigg> plus, its handy to have reports on testing incase there is any difference | 09:04 |
| Kabouik | By the way, when I was in devel, I had to edit /usr/share/ssu/features.d/adaptation-community.ini to change that to testing without reflashing. If I flash directly the testing image, none of that will be necessary right @adampigg? | 09:05 |
| Kabouik | Yeah I remember when it broke, fortunately I avoided it: I was still in devel but didn't zypp ref :p | 09:05 |
| T42 | <adampigg> yes, thats the theory | 09:06 |
| T42 | <edp_17> @r0kk3rz [uncomment the quirk breathing?], I have tried this. Didn't make difference. (However I only restarted mce and not the device.) | 10:22 |
| Kabouik | Hum, flashing the TWRP bootimage on my old device, then doing nothing (I wanted to make a backup but my SD was too small), and then flashing back the SFOS boot image -> I lost WLAN @adampigg | 11:18 |
| Kabouik | I wonder if you have observed that in the past; there's no WLAN MAC address anymore in SFOS > About device | 11:18 |
| T42 | Faithe %lastname% was added by: Faithe %lastname% | 11:49 |
| T42 | lemuzbashzin was added by: lemuzbashzin | 17:59 |
| rinigus | for ports following official devices: as we have LVM partitioning, TWRP backup and restore doesn't work. I have added fsarchiver to recovery and, after small recovery-menu mod, it is possible to make a backup to sdcard | 18:26 |
| rinigus | corresponding packages in https://github.com/sailfishos-sony-tama: hybris-initrd, pkg-fsarchiver | 18:27 |
| rinigus | backup seems to be fine, didn't test restore yet. | 18:27 |
| rinigus | backup log at https://github.com/sailfishos-sony-tama/main/blob/master/backup-recovery.md | 18:27 |
| Thaodan | Good idea and very close to Saifish OS compared too twrp | 18:46 |
| Thaodan | Also ring | 18:46 |
| Thaodan | rinigus: could you expand sailfish/root to system_a by default? | 18:46 |
| rinigus | Thaodan: expanding as for increasing available space? I think I saw somewhere your reply suggesting it... | 18:52 |
| Thaodan | yes | 18:52 |
| Thaodan | system_a is unsused an contains 2.5gb of space | 18:52 |
| rinigus | thinking of it, we could use that extra space for snapshots? | 18:53 |
| Thaodan | or just for root | 18:53 |
| rinigus | (cross-posting) 2.5 G is a bit too little | 18:53 |
| Thaodan | snapshots don't cost anything until you change something | 18:53 |
| rinigus | I was thinking of snapshots between updates | 18:53 |
| Thaodan | its at least more space for packages | 18:53 |
| Thaodan | those grow in time | 18:53 |
| rinigus | Thaodan: indeed, they don't cost much when not in use | 18:54 |
| rinigus | we currently have 4GB for root on tama. for me, I have 1.8GB free there. as during updates packages go to /home, it all looks fine. | 18:55 |
| rinigus | not sure we need to expand /root. or is someone already hitting root size? | 18:56 |
| rinigus | Thaodan: ^ | 18:56 |
| rinigus | Thaodan: above you mentioned "ring". what did you mean/ | 18:57 |
| Thaodan | No I dont think so (only when needing debug symboles) but its unused space | 18:57 |
| rinigus | ? | 18:57 |
| rinigus | system_a, you mean? yes, it is. but maybe we can find some use for it in future... | 18:57 |
| Thaodan | I didn't completed tiping your name and accidently pressed enter | 18:57 |
| Thaodan | yes I meant system_a | 18:58 |
| rinigus | :) | 18:58 |
| Thaodan | If you have larger packages like games or so you might hit that. LVM snapshots could work via the recovery menu from Jola | 18:59 |
| Thaodan | *Jolla | 18:59 |
| rinigus | Thaodan: but we don't have games. and I don't expect any. as for flatpak, those are recommended for install in ~. | 19:00 |
| rinigus | maybe we could use those 2.5 G for dual boot somehow... | 19:01 |
| Thaodan | dual boot between sfos versions?:D | 19:01 |
| *** MagneFire[m] is now known as MagneFire | 19:02 | |
| rinigus | sfos/nemo? tbh, no specific idea... | 19:02 |
| rinigus | Thaodan: but anyway, use of system_a is surely something that can be considered. | 19:04 |
| rinigus | either for expanding PV or something else | 19:05 |
| *** OhYash1 is now known as ohyash | 19:30 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!