henk | piggz, poetaster, mal: got it solved with the info in https://forum.sailfishos.org/t/sailfish-on-vollaos/6342/200, thanks (: | 08:36 |
---|---|---|
*** rdr_ is now known as rdr | 09:18 | |
mal | henk: so it was the ifb I mentioned yesterday | 11:28 |
henk | mal: yes, seems so (: I wasn’t quite able to follow that discussion. I think I missed a part and it seemed like poetaster’s problem was with wlan, not wwan … | 11:38 |
henk | https://forum.sailfishos.org/t/sailfish-on-vollaos/6342/233 woah, that’s weird o_O | 11:43 |
henk | »I observed that the presence of Jolla Calculator slows down the phone, even when app is not in use. Deinstallation speeds up the device. Reason unknown. To have a calculator on the phone, I installed RPNcalc from Storeman, that I like more. | 11:43 |
henk | Sailfish Weather behaves similar, so I also deinstalled it. No substitute, because I don’t need it. | 11:43 |
henk | « | 11:43 |
poetaster | henk, I don't think the 'calculator' observation is correct. Weather could be since it is active. | 11:47 |
poetaster | henk, and yes, the wlan issue maybe the same as the wwan if the queue shaping interface was an issue. That's an interface that block all traffic if it's not set up correctly. | 11:48 |
mal | henk: that calculator thing is very odd, we can't any way that could affect anything | 11:51 |
henk | hm, what’s the proper way of uninstalling the weather app? I don’t see it as installed in storeman, nor jolla store, nor chum o_O | 11:54 |
henk | but it does show up in the menu and shows as installed in "zypper se weather" | 11:54 |
poetaster | henk, I uninstalled the weather app using zypper to first find all the packages and then uninstall | 11:57 |
henk | sailfish-weather, sailfish-components-weather-qt5 and their -all-translations-pack companions? | 11:58 |
henk | just removing sailfish-weather would also remove "patterns-sailfish-device-configuration-yggdrasil patterns-sailfish-store-applications" which does not sound like such a good idea … | 11:59 |
poetaster | patterns-sailfish-store-applications is meta. no way around it. does no harm. you can inspect the depends in those packages to see what it entails, but I did this on the GS5 and it's fine. | 12:01 |
henk | mhm, but if it depends on anything relevant in the future, I won’t get that, which is probably more relevant for patterns-sailfish-device-configuration-yggdrasil | 12:12 |
mal | still odd how uninstalling some app could affect performance in any way | 12:14 |
mal | the apps are quite simple | 12:14 |
mal | we discussed that at jolla but couldn't think of any reason | 12:15 |
henk | I’m kinda guessing that it doesn’t really affect performance on my device because I never accepted the permissions the weather app needs … what would the process show up as in 'ps' if it was active? | 12:21 |
henk | I want to enlarge my root partition 2.4G are filled to 66%. on the forum https://gitlab.com/Olf0/sailfishX#33-increasing-the-root-lvm-volume-size is linked which mentions "embedded recovery" and "hybris-recovery.img". the builds on https://gitlab.com/sailfishos-porters-ci/yggdrasil-ci/-/artifacts don’t seem to include a hybris-recovery.img, though. and I’m not sure whether my | 13:03 |
henk | device has an embedded recovery tool. can anyone give advice which variant I should use, where to find a recovery image suitable for the gs290, or anything else that might help? | 13:03 |
mal | piggz can probably help | 13:05 |
piggz[m] | here https://build.sailfishos.org/package/show/nemo:devel:hw:volla:yggdrasil/droid-hal-yggdrasil | 13:07 |
henk | cool, thx | 13:18 |
henk | piggz[m]: uuuh, but do I install that rpm or extract an image from it? | 13:19 |
piggz[m] | henk: extract it, get the hybrs-recovery.img and boot it | 13:24 |
piggz[m] | if you can do fastboot boot the file, you dont even need to flash it to the boot partition | 13:24 |
henk | huh, now I wonder whether I can just install droid-hal-yggdrasil-img-recovery via zypper? | 13:37 |
piggz | it would be much safer just to boot it | 13:53 |
piggz | and no, i dont think you ca just install that | 13:54 |
piggz | just download and extract the rpm, the use fastboot to load it | 13:54 |
henk | ok | 13:54 |
henk | somewhere I saw something like "reboot recovery" as a command. is there also "reboot fastboot"? (or what is it called? "download"?) | 13:57 |
henk | or a reference which args the reboot command supports? "reboot --help" doesn’t say which ARGs are supported … | 13:57 |
henk | uuuh, ok, I tried booting it as described (enter fastboot mode on phone, 'fastboot boot hybris-recovery.img'), transfer was ok, it seemed to do something™ with a black screen, then rebooted into my normal system. any ideas what could be the issue? | 14:10 |
piggz[m] | not sure ... i cant remember if the volla properly supported dynamically booting like that.... | 14:36 |
piggz[m] | if you are happy to flash your boot you could try that... | 14:36 |
piggz[m] | and just flash the regular boot back later | 14:36 |
piggz[m] | attah: how are you getting on with the ppp? | 14:46 |
poetaster | piggz[m], are the x23 bulds all still devel? | 14:47 |
piggz[m] | yes ... im considering making a testing: one though | 14:48 |
henk | piggz[m]: "flash my boot" means "booting device to fastboot" then flash with "fastboot flash boot hybris-recovery.img", right? | 14:51 |
piggz[m] | yes | 14:51 |
poetaster | ah, damn it. pulled a cable, bricked a friggen phone. | 14:56 |
henk | hrm, that just goes into a reboot loop … I took droid-hal-yggdrasil-img-recovery-0.0.1-master.20230612200813.ff35156-initrd.2ec16ce-1.aarch64.rpm is that known to be good or could something be wrong with it? | 14:57 |
henk | poetaster: oh, ouch. "bricked" as in "terminally" or is it recoverable? | 14:57 |
poetaster | dunno. it has an incomplete volla bootloader on it from the look of it. | 14:59 |
poetaster | it's boot looping now, so I guess it could be worse. But I cannot get to fastboot or recovery. | 14:59 |
henk | heh, I just had a similar issue: flashing 'recovery' as 'boot' on the gs290 and then it boot looped. holding volup made it go to fastboot. | 15:01 |
poetaster | nope, I'm hooped. hmmm. | 15:02 |
piggz | im sure spflash will fix it! | 15:06 |
poetaster | piggz, ok, I have it somewhere around | 15:07 |
piggz[m] | but use that as a last resort, and donw wipe your imei! | 15:08 |
piggz[m] | s/dont | 15:08 |
henk | piggz: tried again, bootloops again. are you sure droid-hal-yggdrasil-img-recovery-0.0.1-master.20230612200813.ff35156-initrd.2ec16ce-1.aarch64.rpm is a good recovery image? | 15:09 |
henk | as in "working" | 15:09 |
piggz[m] | tbh, im not sure, never had to use one! | 15:10 |
poetaster | piggz[m], the x23/GX4 has, it seems and incomplete boot img from volla on it. So, it looks like no choice. Or just send it to you in the mail as an x-mas gift :) | 15:11 |
poetaster | piggz[m], I wouldn't keep it anyway. I do not like it :) | 15:12 |
piggz[m] | i have enough od knackered phones ta ;) | 15:12 |
poetaster | ditto. | 15:13 |
poetaster | I'll see if I can use the old sp flash tool | 15:13 |
poetaster | sigh: libpng12.so.0: is missing. ah, hell | 15:16 |
poetaster | piggz[m], x23 images are under the halium-vidofnir jobs? | 15:24 |
henk | piggz[m]: hrm, ok … my goal in the end is to increase the root partition because 2.4G seems a little small and I can easily spare some space to enlarge it to 10G. is there any other way of doing this than using a recovery image as described in https://gitlab.com/Olf0/sailfishX#33-increasing-the-root-lvm-volume-size? | 15:25 |
piggz[m] | if you dont mind reflashing, just use the lastes image, which is 8gb https://gitlab.com/sailfishos-porters-ci/yggdrasil-ci/-/commit/96e264711ced93b6d35c4270275c2b7c803d0af0 | 15:28 |
poetaster | piggz[m], vidofnir == x23? | 15:29 |
piggz[m] | yes | 15:29 |
poetaster | tanks | 15:29 |
attah | piggz[m]: been a bit busy... but now i have some time to poke at it again | 15:30 |
attah | Anything special i should be looking closer at? | 15:31 |
piggz | attah: some users reported ofono segfaulting ... havnt had a chance to look at it yet ... the version in my home obs repo wasnt crashing for me ... need to double check the version i built on the dontbeevil repo was the same, with same ell version | 15:41 |
piggz | could be a good task to investigate | 15:41 |
attah | piggz: And i still have wakeup issues apparently https://pastebin.mozilla.org/HR7m3vT6 | 15:43 |
piggz[m] | attah: snippet not found | 16:58 |
attah | meh | 17:00 |
attah | https://pastebin.mozilla.org/YVXf5qhO | 17:01 |
attah | Ah, sorry, default expire is 1h | 17:01 |
piggz[m] | attah: use your hacking skills to make a uart cable? | 17:02 |
attah | I guess... but what would i get more than persistent journal gets me? | 17:02 |
piggz[m] | you should get any kernel panic messages that dont hit the journal | 17:03 |
attah | so i gather you don't see anything that's actionable? | 17:05 |
piggz[m] | you could enable additional dsme debug logs | 17:06 |
attah | how would i do that? | 17:09 |
piggz[m] | look in the systemd unit for dsme, and it will reference where it loads environment settings from ... usually /var/lib/environment ... | 17:10 |
piggz[m] | create/edit file there to suit, probably adding -d option or such | 17:10 |
attah | EnvironmentFile=-/var/lib/environment/dsme/*.conf ...though the directory doesn't exist. Any pointers for format of said files? | 17:13 |
attah | dsme seems entirely ungooglable | 17:13 |
piggz[m] | add eg debug.conf ...... the Exec line in the.unti will say what variable name to use... something like "DSME_ARGS="-d" .... | 17:15 |
piggz[m] | check with dsme --help | 17:15 |
attah | dsme --help is completely useless unfortunately | 17:19 |
attah | hmm, maybe dsme-server | 17:19 |
attah | I put in DSME_ARGS="-v 7", but i really have no idea what the format should be | 17:27 |
piggz[m] | attah: the weird thing in your log is the reboot message ... like, it deliberately rebooted, so, i wonder if that was dsme doing that | 17:47 |
attah | piggz: that is me giving up and holding the button | 17:49 |
attah | ...or at least that's what i thought | 17:49 |
piggz[m] | attah: ah ok, then that is dsme | 17:49 |
piggz[m] | so, it just doesnt turn the screen back on? | 17:50 |
piggz[m] | a uart cable would give you root console access, without worrying about network devices getting in the way | 17:51 |
attah | no idea how much have gone wrong beyond that... | 17:51 |
attah | but yes, that is the primary symptom | 17:51 |
attah | project for tomorrow then :) | 17:51 |
henk | piggz[m]: hm, I was just looking into what the flash-volla.sh script does to see what "reflashing" would mean and now I wonder how I installed it … it says something about a logo. when would that be shown? during boot I see a "volla" logo, no sailfish logo … and I see the warning about "orange state" and device being untrusted which I think that last step commented with | 17:55 |
henk | »#Lock partition to allow flashing and remove boot warning« might be referring to … | 17:55 |
piggz | henk: did you install it using the volla boot manager thing? | 17:56 |
henk | piggz: hm, I’m just trying to reconstruct with some historical irc log archaeology :D | 17:57 |
henk | possibly, yes | 17:57 |
henk | IIRC I had to go some roundabout way, first flashing some ubports stuff or so | 17:57 |
piggz[m] | henk: my builds only flash the partitions directly ... some volla guys did some magic, but ive never tried that | 17:58 |
piggz[m] | the lock partition thing is to allow flashing boot from inside the OS ... you can always flash it from fastboot still | 17:58 |
henk | ok. reflashing would mean that both / and /home would be deleted, right? | 18:01 |
piggz | yes | 18:03 |
henk | hm, I don’t like that so much so I’ll hold off on that for now … are there any other recovery images I could test, like older versions? or is there anything I can do to figure out why the one I tried doesn’t boot? | 18:08 |
piggz | henk: there are other versions here https://build.sailfishos.org/project/subprojects/nemo:testing:hw:volla:yggdrasil | 18:09 |
poetaster | piggz, have you got a scatter for the x23 ? I can't find one and it seems to be a current issue with mtkclient & co. https://github.com/bkerler/mtkclient/issues/758 | 18:11 |
piggz | i dont, sry | 18:11 |
poetaster | okidoke. it's bit pita since I wasn't even doing it for me. sigh. | 18:11 |
poetaster | well, at least I got my VisualEncoderDecoder model trained. But context switching is what caused my cable disaster. some days I dunno if I should laugh or cry. | 18:13 |
piggz[m] | yeah, a serial uart is great for debugging ... except the terrible speed and size of the terminal | 18:16 |
henk | if in doubt: ly … eeh, I mean craugh … errrr | 18:16 |
poetaster | heh. I'd like to desolder the flash and, and, and .... | 18:17 |
henk | piggz: I’ll try some of these. thanks for all your help (: | 18:20 |
poetaster | piggz[m], when you have a chance, try out seaprint on your x23 ... I'm curious if the network issue is just volla22/GS5/rephone or more general. | 18:46 |
piggz[m] | k | 18:47 |
henk | piggz: they are actually all the exact same recovery image | 20:11 |
*** rdr_ is now known as rdr | 21:34 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!