| entil | hiyall! | 06:44 |
|---|---|---|
| entil | any clues on the xa2 sale date? | 06:44 |
| entil | I think the sim modems on my fp2 snuffed themselves, and if I need to buy a new phone, I'm entertaining the notion of moving away from fairphone | 06:46 |
| kimmoli | if you broke it, you can keep all 6 parts | 06:57 |
| entil | kimmoli: what do you mean? | 06:58 |
| entil | kimmoli: I couldn't find spare parts for the sim modems on fairphone's store | 06:59 |
| entil | kimmoli: so does that mean that I'd buy a new phone and keep all the current parts for spares? | 07:00 |
| kimmoli | depends did you actually broke it? (it was just a saying, if one brokes something he can keep _both_ parts, in FP case it is 6 parts)... | 07:01 |
| entil | kimmoli: I dunno really, I'd like to know how to debug this other than 1) not being asked for a pin 2) not seeing any mobile connectivity 3) csd saying 0 modems | 07:02 |
| entil | because I wouldn't want to buy a new phone, but if I have to, I'd look into the xa2 or the gemini, or maybe another xperia x like I use for work | 07:03 |
| kimmoli | 0 modems sounds bad. maybe dmesg? | 07:03 |
| kimmoli | and you did not make any update? | 07:04 |
| entil | kimmoli: there hasn't really been an update to try, but I did check that | 07:05 |
| entil | and detecting the modems in csd does not output anything to dmesg | 07:06 |
| entil | btw what are the 6 parts? fairphone's store lists 5 parts: display, battery, bottom, camera and top | 07:08 |
| entil | [D] onValidChanged:77 - Modem count: 0 (expected: 2) | 07:12 |
| kimmoli | dmesg right after booting | 07:15 |
| entil | I'll reboot, thanks | 07:15 |
| entil | kimmoli: http://paste.debian.net/1042285/ | 07:20 |
| entil | I don't really know how to read that | 07:21 |
| entil | smd_pkt_open: DATA5_CNTL open failed -19 <- does that mean it can't talk to the modem? | 07:24 |
| *** frinring_ is now known as frinring | 07:33 | |
| entil | I guess I'm just fscked | 07:36 |
| kimmoli | entil: about update, there is 2.2.0.29 available for fp2 (atleast there are such repos in testing, mal can confirm?) | 07:48 |
| kimmoli | but dont know does that help. nothinf obvious cause in dmesg, ril-daemon seems to be killed at least once | 07:48 |
| entil | kimmoli: I've been on the stable releases because I haven't really needed an update in a long time and enjoy the stability, but because this started with me disconnecting the charger, using the phone for a while, and then it rebooted and didn't find modems, I'm sort of suspecting it's not a software problem anyway | 07:50 |
| entil | kimmoli: what does rild do? it's running now | 07:51 |
| kimmoli | https://www.e-consystems.com/Articles/Android/Android-RIL-Architecture.asp e.g | 07:51 |
| entil | ok, it's about the radio, maybe it being killed is a clue | 07:52 |
| entil | account ring/tel/ril_0 has implausible manager/protocol: (nil)/(nil) | 07:53 |
| entil | meh, I'll update to 18.04 and 2.2.0.29; it's not like I'd have much to lose | 08:08 |
| mal | entil: have you done any updating or something like that recently? | 09:13 |
| entil | mal: no, there haven't been any updates, but I'm going to update to 2.2.0.29 now and flash in 18.04's system.img | 09:13 |
| entil | mal: just in case, if this still could be a software failure somehow | 09:13 |
| entil | as always, these things happen at the most inconvenient times, I'm not sure if I can get this finished before we head out of home | 09:14 |
| mal | entil: just to be sure, are you using devel or testing repos? check output of ssu lr | 09:14 |
| entil | http://repo.merproject.org/obs/nemo:/testing:/hw:/fairphone:/fp2-sibon/sailfishos_2.2.0.29/ | 09:17 |
| mal | ok, testing is fine | 09:17 |
| entil | mal: I just changed the release version now | 09:17 |
| entil | mal: I never felt the need to flash in FP2-gms59 for the modem, but would that serve as a test case for hardware failure? like would that fail if the modem is electronically broken? | 09:18 |
| mal | then what have you used as modem partition? | 09:21 |
| entil | mal: en ymmärrä kysymystä :D what does that mean? whatever was the default two years ago or whatever | 09:22 |
| mal | entil: also for debugging modem issues output of /usr/libexec/droid-hybris/system/bin/logcat or that with -b radio | 09:22 |
| mal | entil: ok, maybe that partition is old enough then, I would still suggest just following the instructions | 09:22 |
| entil | running the csd sim check with logcat -b radio produces no output | 09:23 |
| mal | you are now mixing things | 09:23 |
| mal | the modem already failed a long tima ago during boot | 09:23 |
| entil | yes | 09:23 |
| entil | that's why I'm wondering why I should even look at logcat | 09:24 |
| mal | csd app is useless for debugging, it will only tell if it works, nothing more | 09:24 |
| entil | because I assumed those DATA5_CNTL errors mean the modem failed, just as csd also says | 09:24 |
| entil | so if the modem's dead to the os, it would be improbable to see anything about it in any log | 09:24 |
| mal | it is difficult to say if this is a hardware or software issue | 09:25 |
| mal | entil: what sailfish release were you using before this update you are doing now? | 09:26 |
| entil | all the more because the download's only at 33% or so and I'll be afk for hours and hours at some point | 09:27 |
| mal | entil: also the sixth part of fp2 is the core module | 09:27 |
| entil | 2.1.4.14 was the previous version | 09:27 |
| entil | yeah, they don't sell only the core module, so if this is quite broken, I'll have to consider switching vendors | 09:27 |
| mal | entil: at least they used to sell it | 09:28 |
| entil | much love for the fp2 port and the phone, but I've bought two spare parts in two years so if this is broken now, I can't be very confident in the manufacturing quality | 09:28 |
| mal | which parts have broken before? | 09:29 |
| entil | the battery started to suck and the bottom mic died | 09:29 |
| entil | the support was very slow and wanted me to test shit in android when I contacted them about the mic | 09:29 |
| mal | I haven't had the need for buying anything, except now I should buy a new case for the device as it's starting to break from one place | 09:30 |
| entil | so I just bought a new mic | 09:30 |
| entil | but now I have to be afk for a while, hopefully I can check in before leaving | 09:30 |
| Leif_Erikson | Hello again. We have took the suggestion of the #nemomobile and #sailfishos chat | 09:38 |
| Leif_Erikson | To recap: We try to build and deploy a lipstick implementation. | 09:39 |
| Leif_Erikson | The documentation of the app sdk confirms, that the platform sdk is installed on the build engine vm. | 09:39 |
| Leif_Erikson | Therefore I assume, that the necessary repos are available to build the lipstick example project. If not, I don’t know which repos are missing. | 09:39 |
| Leif_Erikson | The documentation suggests, that the spec file is automatically created by the app sdk. | 09:39 |
| Leif_Erikson | I neither could find a documentation how to write a spec file nor how to include this custom spec file in the build process. | 09:39 |
| Leif_Erikson | I found the documentation about spec files at http://ftp.rpm.org/max-rpm/s1-rpm-build-creating-spec-file.html, but I still don’t know how to solve the issue of a missing developer lipstick package. | 09:39 |
| Leif_Erikson | Last but not least, it is not clear, where and how to deploy a lipstick implementation. I assume it’s not as easy as for an Android launcher, that is deployed as a regular app. | 09:39 |
| Leif_Erikson | One can install several launcher in parallel but not lipstick implementations, correct? | 09:39 |
| Leif_Erikson | Hello again | 09:42 |
| Leif_Eri_ | ok | 09:44 |
| mal | for me platform sdk worked fine for building that example | 09:46 |
| Leif_Eri_ | mal: How do you avoid the error message: lipstick-qt5 development package not found ? | 09:48 |
| elros1 | I just tried and I could build glacier rpm without any issues in platform sdk | 09:49 |
| mal | by installing the development package, it should be available in the default repos, use (replace target name with correct one) sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in lipstick-qt5-devel | 09:49 |
| mal | Leif_Eri_: are you building it with spec file or without? | 09:50 |
| Leif_Eri_ | mal: Without, because of the issue, that i mentioned in my note above | 09:51 |
| mal | so then you of course need to install dependencies manually, make doesn't know anything about how to install those | 09:54 |
| mal | ou really have fought with that issue for day? it's really not that difficult | 09:55 |
| Leif_Eri_ | mal: More than one day. We try to find a freelancer, who can set up the build and deployment process for us. | 09:56 |
| Leif_Eri_ | We need to know, how to manage the dependencies at least for one time. | 09:57 |
| mal | if you build things manually without spec file then you need to install dependencies manually which is obvious and you use a command like the one I gave to install those, if you use spec dependencies should be installed automatically | 10:00 |
| mal | I did give you the command already many days ago | 10:01 |
| mal | why didn't ask back then if you didn't understand | 10:01 |
| Leif_Eri_ | mal: If the sb2 command is the solution, if would be convenient. How can I find teh correct target name. The sdk works with the simulator and our development devices. To we need an installation for each virtual and physikal device, which are defined in the so called "kit" of the sdk? | 10:02 |
| mal | the target name is the one you used when you setup the target, you can see targets with sdk-assistant list | 10:03 |
| mal | Leif_Eri_: you are really always asking the wrong questions or just in a bad way, because if I had known you we still not able to install the damn dependency I could have given you that command days ago | 10:04 |
| Leif_Eri_ | mal: Ah, I see. It is the target of the platform sdk. I think, there are two or three of them by fedault. | 10:06 |
| entil | sucks, didn't get to see this through now, gotta go out with the family, laters! -> | 10:06 |
| King_DuckZ | hi, what's the tracker-store process? it's taking up all my cpu since I updated yesterday | 10:25 |
| r0kk3rz | because its reindexing | 10:34 |
| mal | it's indexing the images and other files | 10:34 |
| r0kk3rz | which always happens after update | 10:34 |
| King_DuckZ | oh ok | 10:35 |
| mal | not sure how long it usually takes | 10:36 |
| Leif_Erikson | Thanks for the help. Now I can build the project after installing the lipstick-qt5-devel package for both targets on the build engine. | 15:26 |
| Leif_Erikson | The next step is now the deployment of the project. The sdk throws the following error for the deployment: Fatal: No spec file found in '/home/mersdk/share//SailfishOS/projects/LipstickExample/rpm/' and couldn't make one from a yaml #1 | 15:27 |
| Leif_Erikson | I expected, that the sdk creates a spec file automatically like for the other projects for apps, I have created with the app sdk. | 15:28 |
| r0kk3rz | it doesnt | 15:44 |
| mal | Leif_Erikson: how exactly did you create the project for the example? | 15:50 |
| Leif_Erikson | mal: I have clicked on the green arrow in the IDE. | 15:56 |
| Leif_Erikson | I found a chapter about spec and yaml files here https://sailfishos.org/wiki/Application_SDK_Packaging_Apps | 15:57 |
| Leif_Erikson | The documentation suggests to create a yaml file. | 15:57 |
| Leif_Erikson | The documentation says: "An initial .yaml file is generated when you first create a project using the Qt Creator Sailfish OS Qt Quick application template. You can see from the figure in the Installation Package Creation Overview section that the .pro file works as a source of data for the .yaml file. For this reason, the parts of the .yaml file are regenerated every time the Qt project file changed. " | 15:58 |
| Leif_Erikson | it seems, that the .pro file is not processed. | 15:58 |
| Leif_Erikson | As I understands, the yaml file is derived from the pro file and the spec file is derived from the yaml file. | 15:59 |
| Leif_Erikson | The process seems to be broken in the pipleline | 16:01 |
| mal | no, you misunderstood how it work, you need both pro and spec files | 16:02 |
| mal | maybe yaml is also useful in some cases | 16:04 |
| mal | check https://github.com/nemomobile-ux/glacier-home | 16:04 |
| mal | that has a good example of how the pro, yaml and spec files should look | 16:04 |
| kimmoli | a note; if you intend to use .spec, remove .yaml from rpm/ folder, otherwise the sdk build process will overwrite your .spec | 16:08 |
| r0kk3rz | imo the yaml is an overcomplication and spectacle isnt really maintained anymore | 16:08 |
| mal | yes, pro and spec are enough usually | 16:09 |
| Leif_Erikson | The documentation says: "To create an RPM package, you need a .spec file that provides information about the software being packaged. For Sailfish OS projects, you don’t usually create or modify the .spec file directly. Instead, a more human-readable intermediate metadata file, a .yaml file, is used. The .spec file itself is generated automatically during the build process from the .yaml file." (https://sailfishos.org/wiki/Appli | 16:24 |
| Leif_Erikson | cation_SDK_Packaging_Apps#The_.yaml_File" | 16:24 |
| Leif_Erikson | Where do I have to place the spec file? Unfortunately Jolla's documentation just explains the syntax and content of the yaml file. | 16:25 |
| Leif_Erikson | I assume, there is some hidden configuration of the project, that is not located in the project folder itself. | 16:26 |
| kimmoli | yaml and spec lives in the rpm directory | 16:27 |
| kimmoli | if you have only yaml, spec will be created on first build | 16:28 |
| kimmoli | when you create a new project with new project wizard, you get only yaml. | 16:31 |
| kimmoli | when you hit build -> build all, a spec is created | 16:31 |
| kimmoli | maybe we just confuse you.... | 16:36 |
| Leif_Erikson | kimmoli: Thanks. Because the project is a clone of a Github project, I guess, I have to create the yaml on my own. | 16:37 |
| kimmoli | what project it was? | 16:37 |
| Leif_Erikson | So I have to create a subdirectory rpm and create a yaml file there. Is this sufficient? | 16:37 |
| Leif_Erikson | kimmoli: https://github.com/nemomobile-graveyard/lipstick-example-home | 16:38 |
| mal | maybe I should have given you a spec file for that days ago (takes like 5 minutes to make even manually) but I assumed it so simple that you can do it | 16:42 |
| r0kk3rz | yeah but then he wont learn anything | 16:48 |
| entil | mal: updated the os and underlying android system partition, no bonus; and to make matters worse, the baby woke up so lol -> | 16:51 |
| Leif_Erikson | The best way is to learn with examples. I need to put the puzzle together. The quoted documentation describes a yaml file quite well, but not the required project structure and the spec file. I'm missing something like project settings, that I know from Xcode | 16:54 |
| mal | entil: get output of /usr/libexec/droid-hybris/system/bin/logcat when you have time | 16:54 |
| mal | Leif_Erikson: the glacier-home is a quite good example for checking how the spec and pro files are used since it's doing pretty much the same thing as the example project | 16:55 |
| mal | not sure why the example doesn't have spec file | 16:56 |
| Leif_Erikson | From other projects, I can infer, that the project has an rpm directory with a yaml, spec and two other files with changes.in and changes.run.in | 16:56 |
| mal | you can ignore changes file, that is not always used | 16:56 |
| Leif_Erikson | But where is defined, that the project build and deployment is using that yaml and spec file? | 16:56 |
| entil | mal: does logcat do things in UTC? either way, it's completely flooded by 09-15 16:50:45.434 8897 11192 E qdhwcomposer: isValidDimension: layer handle is NULL | 16:56 |
| r0kk3rz | Leif_Erikson: just add the files | 16:59 |
| mal | Leif_Erikson: https://github.com/nemomobile-ux/glacier-home/blob/master/rpm/lipstick-glacier-home-qt5.spec#L11 | 16:59 |
| mal | entil: use logcat | grep -v hwcomposer to ignore the flooding messages | 17:00 |
| entil | mal: I'm flashing the modem partition now, but then, sure | 17:01 |
| mal | entil: that error is normal, nobody has bothed to fix it | 17:01 |
| mal | *bothered | 17:01 |
| entil | boots damned slow :/ | 17:04 |
| entil | unless it died on me | 17:04 |
| kimmoli | dunno what makes the initial spec from yaml, but sdk compile output says "Warning NEW spec file created: test.spec, maybe customized spec content is needed!" | 17:08 |
| entil | mal: dmesg http://paste.debian.net/1042336/ && logcat https://paste.ubuntu.com/p/2RKqCwxdYx/ | 17:11 |
| entil | debian choked on the size of the log | 17:11 |
| mal | entil: does logcat -b radio give anything? | 17:12 |
| entil | mal: strange enough, it does! http://paste.debian.net/1042337/ | 17:14 |
| mal | entil: that says sim count 1 | 17:15 |
| entil | mal: I have two sims in there, no pin was asked for | 17:15 |
| entil | mal: so something is still quite severely messed up | 17:15 |
| entil | lemme run csd | 17:16 |
| mal | entil: go to sim card settings and disable and reenable both slots | 17:16 |
| entil | mal: I can't, there is nothing there except "Use SIM card" which is grayed out, and csd didn't find anything | 17:17 |
| mal | hmm | 17:17 |
| mal | it seems might failing in a loop | 17:18 |
| entil | I tried getting another logcat but it's 149 lines again, so it's not flooding anything new in there | 17:20 |
| mal | entil: maybe also flash the some of the other partition from 18.04.1 as told in wiki "Also the other partitions (except modem and boot partitions) can be flashed (rpm, sbl1, tz, splash and aboot) can be flashed " | 17:20 |
| kimmoli | what does ofono say? | 17:20 |
| kimmoli | dbus-send --system --print-reply --dest=org.ofono / org.ofono.Manager.GetModems | 17:20 |
| entil | method return time=1537032063.858713 sender=:1.6 -> destination=:1.88 serial=105 reply_serial=2 | 17:21 |
| entil | array [] | 17:21 |
| entil | mal: when the documentation says "can be flashed" it's not clear to me which I should or what these partitions do | 17:21 |
| kimmoli | that was short... | 17:22 |
| mal | entil: check flash.sh file | 17:22 |
| mal | it should list the fastboot commands | 17:22 |
| entil | mal: sure, it flashes pretty much everything but userdata, judging by what I saw in /dev/.../by-name/, but I don't know what tz is except timezone or rpm except redhat package manager ;) | 17:23 |
| entil | mal: I'll go ahead and flash everything but userdata, modem and system; this'll take a while, but I'll report back then | 17:25 |
| mal | entil: also do not flash boot :) | 17:27 |
| entil | I did rpm, sbl1, tz, splash and aboot now | 17:28 |
| entil | I did not do modem from 18.04.1 btw, I did it from http://storage.googleapis.com/fairphone-updates/FP2-gms59-1.5.1-manual.zip | 17:29 |
| mal | ok | 17:30 |
| entil | meniks oikein or should I use the 18.04.1 one for modem? | 17:30 |
| mal | modem should be from 1.5.1 like you did | 17:31 |
| entil | vielki pävi | 17:31 |
| mal | did the issues start suddenly? | 17:33 |
| entil | yes | 17:33 |
| entil | new dmesg https://paste.ubuntu.com/p/kqCVwF4Ztn/ | 17:34 |
| entil | new radio logcat https://paste.ubuntu.com/p/YbVrFfcPTz/ | 17:34 |
| entil | mal: I disconnected the charger, procrastinated in the browser for a while and the phone booted - so I naturally assumed an OOM kill - and when it came back up, no sign of mobile connectivity, sim cards, no asking for a pin code, nothing | 17:35 |
| mal | ok, very odd | 17:36 |
| entil | if it had died immediately on disconnecting the charger, an electrical/electronical failure would make a bit more sense to me, it's a new charger the missus just bought (at teknikmagasinet, not some shady chinese ebay front), but the phone was fine for a while | 17:37 |
| entil | but without a clear indication of software failure or any signs except "no modems, sux 2 b u", I dunno what else to suspect but a hardware failure | 17:38 |
| mal | entil: maybe try to see if modem works in android if it's not too much work, you basically just need to flash boot partition from 18.04 | 17:40 |
| entil | mal: so I download the sfos from devaamo so I can restore the boot partition to its former glory after that android experiment? | 17:41 |
| mal | yes | 17:41 |
| entil | ok, I'll get back to you soon | 17:41 |
| entil | just in case this works, I can recalibrate the proximity sensor while in android | 17:42 |
| mal | yes | 17:42 |
| mal | but for prox calibration you need to flash 18.04 modem partition also | 17:42 |
| entil | I never booted the base on this; I remember booting into the google android and getting scared about the spyware aspect and immediately installing sailfish :D | 17:42 |
| entil | palataan siihen, afk while downloading the devaamo pkg & | 17:42 |
| mal | hopefully there are no stuff from old android in data partition and cache | 17:43 |
| mal | not sure if the old android you booted was android 5 or 6 | 17:43 |
| mal | if there are issues booting to android clear cache partition and certain things from data partition (everything except .stowaways/sailfishos folder and it's content) | 17:47 |
| entil | I wish the boot splash was dmesg like a linux, so slow to boot, but it looks like android starting up so far | 17:52 |
| entil | but I'm trying to conduct the first experiment now, which is booting 18.04 with the 1.5.1 modem, and now it's "upgrading" and "optimizing app ... of 101" | 17:53 |
| entil | sim card is locked - no service - no service - ntt docomo | 17:54 |
| entil | wtf | 17:54 |
| mal | so does it see the sims or not | 17:55 |
| entil | it does! :O | 17:56 |
| entil | I was able to call my work phone | 17:56 |
| mal | ok, soe modem is not broken, but why did it fail in sailfish | 17:57 |
| entil | but it's "broken", as in the screen went black, and when I denied the call it still went to the answering service and hitting the power button causes a vibration | 17:57 |
| mal | ? | 17:58 |
| entil | I think this means I'll detour into flashing the modem partition and taking care of the proximity sensor | 17:58 |
| entil | siis ruutu meni mustaks siitä puhelusta, ja kaiarista kuului että jätä viesti, ja nyt se vaan vibraa enkä saa kuvaa takas | 17:59 |
| mal | ok | 17:59 |
| entil | despite me rejecting the call on my work phone, which is a big wtf | 17:59 |
| entil | playing with the power button, "jätä viesti painamalla nolla" | 18:00 |
| mal | hmm, odd, anyway calibrate the prox sensor, it might explain the black screen | 18:00 |
| entil | this is too spooky for me, I'll de-batterize the phone | 18:00 |
| entil | ah, now I got the screen back all of a sudden, and an sms that there's a message in my answering service | 18:00 |
| entil | definitely prox sensor | 18:00 |
| mal | but at least the modem is not completely broken | 18:01 |
| entil | I just hope my sd card remains intact through this, as the android setup told me it doesn't support it | 18:01 |
| entil | "i'm a n'android, i'll fix this for you without asking, mkfs <3" | 18:01 |
| mal | heh | 18:01 |
| entil | recalibrated, rebooting now, zomg | 18:04 |
| entil | spooky spyware shit, I got a notification from drivenow that today's ride has been completed | 18:05 |
| entil | no idea how that's possible because I don't have google anywhere on this, and I couldn't get anbox (or whatever it was called) to work | 18:06 |
| entil | ok, prox sensor works \:D/ | 18:06 |
| entil | mal: hybris-boot.img right? | 18:08 |
| mal | yes | 18:09 |
| mal | to boot partition | 18:10 |
| entil | gotta slap the spydäri in the oven before unlocking sfos | 18:10 |
| entil | yeah, still doesn't work | 18:13 |
| mal | hmm, very odd | 18:14 |
| entil | mal: btw, tried calling my work phone despite not having been asked for a pin or anything, but it said "Emergency calls only" - I assume this is a default fallback and not a sign of functionality? | 18:15 |
| mal | yes, that is what happens if sim is not properly in use | 18:15 |
| entil | the missus went out on a gig and I've forgotten to eat, the spydäri should be done in less than 15 minutes, and I don't know what I can do after eating, or how soon after | 18:15 |
| r0kk3rz | kimmoli: kimmobot is coming together nicely i see | 18:15 |
| kimmoli | r0kk3rz: thats a year old pic... | 18:16 |
| r0kk3rz | kimmoli: still looks cool | 18:17 |
| mal | entil: how much personal data do you have in sailfish, meaning if we should consider reinstalling it | 18:17 |
| entil | https://paste.ubuntu.com/p/pZkH8W5GkG/ dmesg and https://paste.ubuntu.com/p/67DsgNdm6b/ logcat | 18:18 |
| entil | mal: I should be able to fit ~nemo onto the sdcard, but I'd hate to go through the hassle of restoring everything and finding I forgot something | 18:18 |
| entil | mal: I assume the backup tool doesn't take backups of dotfiles and such | 18:19 |
| mal | ok, let's keep that as last resort | 18:19 |
| mal | no idea how it's possible that modem works fine in android and not in sailfish | 18:19 |
| entil | and that it went tits up all of a sudden like it did | 18:20 |
| mal | yes | 18:20 |
| mal | entil: so you have now 2.2.0.29 sailfish installed? | 18:20 |
| entil | to the best of my knowledge, but I can ensure the upgrade soon, as I just rebooted the phone for fun and it's really slow to boot | 18:21 |
| mal | how slow? | 18:21 |
| entil | the ssh connection got disconnected while it was doing its thing, but when I retried, it claimed to be up to date | 18:21 |
| entil | slow as balls | 18:21 |
| entil | a minute or two | 18:21 |
| entil | maybe it's just me being stressed out that makes it feel slower than it is | 18:21 |
| entil | to be fair, booting android wasn't exactly fast either | 18:22 |
| mal | entil: my fp2 boots in 30 seconds | 18:23 |
| entil | dafuq 30s | 18:23 |
| entil | but version --dup said NO UPDATES FOUND | 18:23 |
| entil | so it should be an intact 2.2.0.29 | 18:24 |
| mal | "ssu re" says what? | 18:24 |
| entil | that it's 2.2.0.29 | 18:24 |
| mal | run zypper ref -f and then zypper dup | 18:24 |
| entil | "Nothing to do." | 18:25 |
| entil | I think it's safe to say it's up to date despite that ssh disconnect | 18:25 |
| mal | hopefully yes | 18:26 |
| mal | but that was after the issues started | 18:26 |
| entil | splash visible at 8s, been going for 30s now | 18:26 |
| entil | I'm timing the boot | 18:26 |
| entil | ok, 38s, it actually isn't as bad as my stressed-out brain tells me | 18:27 |
| mal | so quite similar, my test was a reboot | 18:28 |
| entil | anyway, spydäri done, I should eat :/ | 18:28 |
| entil | wtf! now it asked for the pin! | 18:29 |
| mal | hmm | 18:29 |
| entil | the only real difference is that I went to the kitchen for some spydäri love, instead of immediately unlocking | 18:30 |
| entil | I'll dump the dmesg and logcat outputs but then I really have to eat | 18:30 |
| mal | next week I will probably release 2.2.1.18 for fp2 | 18:31 |
| mal | I'm already using that myself and so far everything is working as before | 18:32 |
| r0kk3rz | yeah seems fine here | 18:32 |
| entil | https://paste.ubuntu.com/p/Cm8tGpBZJr/ dmesg and https://paste.ubuntu.com/p/8ccXf3YPFr/ logcat | 18:33 |
| entil | mal: will it require an android update? | 18:33 |
| entil | mal: also, if you see some sort of "shit entil unlocks fast, I'd better cause a race condition" bug in there, that'd be great | 18:33 |
| entil | mal: but thank you, as always, for all the help! unless something breaks, I'll keep my eyes peeled for 2.2.1.18 to hit testing and update :) | 18:35 |
| mal | entil: no need for android update for next release because there hasn't been any android releases after last sailfish release | 18:35 |
| entil | nice | 18:35 |
| entil | and I called my fp2 from the xperia x and it worked as well! and having the prox sensor calibrated feels höpö too | 18:36 |
| mal | entil: for me the pin query happens directly, I don't have lock code on my device | 18:36 |
| entil | can't remember what happened with it, I think it worked better and somehow deteriorated and then I never cared, but only hit the power button to wake up the screen | 18:36 |
| mal | entil: you really used it this long without calibrating the prox sensor? | 18:36 |
| entil | mal: I'm sure it didn't always suck... | 18:36 |
| mal | ok | 18:36 |
| mal | I only had random issues before calibrating it | 18:37 |
| Blizzz | is there an event i can react on, when a page was navigated back to? | 18:37 |
| mal | ? | 18:37 |
| entil | anyway, food calls, thanks for the help and I'll nag you if something breaks again and otherwise looking forward to the update :) | 18:37 |
| mal | entil: hmm, dmesg has EXT4-fs (mmcblk0p20): recovery complete | 18:40 |
| mal | not sure if that is normal | 18:40 |
| mal | ah, seems to be normal | 18:41 |
| mal | good to know that it seems to work now, but still it would be better if I knew why it works now but I couldn't see anything in logs, hopefully it keeps on working | 18:42 |
| x2s | Uhm, it is only possible to backup to onedrive or dropbox? Why no webdav? | 20:19 |
| mal | x2s: not sure if there has been enough requests for that feature | 20:29 |
| x2s | weird. Nextcloud would be my first choise for a cloud backup... | 20:36 |
| mal | x2s: there is a filemanager which support webdav but no support in the backup system | 20:46 |
| wolfquin | hello | 22:23 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!