| vgrade | sledges: | 00:00 |
|---|---|---|
| vgrade | Sep 26 00:53:17 Jolla DSME[688]: IPHB: rtc at 1970-09-25 23:53:16 GMT | 00:00 |
| vgrade | Sep 26 00:53:16 Jolla DSME[688]: IPHB: set to 2014-08-05 23:47:29 GMT | 00:00 |
| vgrade | look better | 00:00 |
| vgrade | and time was set correctly from mobile web | 00:00 |
| vgrade | on reboot | 00:00 |
| vgrade | will do a PR now | 00:00 |
| *** cxl000 has quit IRC | 00:01 | |
| *** icelaglace has joined #sailfishos-porters | 00:05 | |
| vgrade | sledges: situ https://github.com/mer-hybris/android_device_lge_hammerhead/pull/2 | 00:29 |
| *** diverse has left #sailfishos-porters | 00:42 | |
| *** boilerkim has quit IRC | 00:44 | |
| *** icelaglace has quit IRC | 01:05 | |
| *** alin has quit IRC | 01:06 | |
| *** arcean has quit IRC | 01:08 | |
| *** alin has joined #sailfishos-porters | 01:24 | |
| *** alin has joined #sailfishos-porters | 01:25 | |
| *** beidl has joined #sailfishos-porters | 01:59 | |
| *** beidl_ has quit IRC | 02:00 | |
| *** chrisi has quit IRC | 02:01 | |
| *** chrisi has joined #sailfishos-porters | 02:28 | |
| *** boilerkim has joined #sailfishos-porters | 02:42 | |
| *** dmt_ has quit IRC | 03:29 | |
| *** furikku has joined #sailfishos-porters | 03:59 | |
| situ | vgrade: I have already tried disabling that service, can you show me full journalctl log after disabling it ? | 04:58 |
| *** ryukafalz has quit IRC | 05:12 | |
| *** ryukafalz has joined #sailfishos-porters | 05:26 | |
| *** VDVsx has quit IRC | 05:31 | |
| *** mailyaseen has joined #sailfishos-porters | 05:44 | |
| *** boilerkim has quit IRC | 05:53 | |
| *** boilerkim has joined #sailfishos-porters | 05:54 | |
| *** VDVsx has joined #sailfishos-porters | 05:58 | |
| *** phdeswer has quit IRC | 06:29 | |
| *** lpotter has quit IRC | 06:34 | |
| *** lpotter has joined #sailfishos-porters | 06:34 | |
| *** gogeta_ has joined #sailfishos-porters | 06:43 | |
| *** dmt_ has joined #sailfishos-porters | 06:49 | |
| *** vakkov has quit IRC | 06:55 | |
| *** giucam has quit IRC | 07:03 | |
| *** giucam has joined #sailfishos-porters | 07:03 | |
| *** giucam has joined #sailfishos-porters | 07:03 | |
| *** iTune has joined #sailfishos-porters | 07:14 | |
| alin | vgrade: I have that disabled | 07:20 |
| alin | situ: what happened with the time? | 07:21 |
| alin | I have that service deisabled but dsme still fails | 07:21 |
| spiiroin | alin: I might have some time later today to check the dsme behavior | 07:23 |
| *** iTune has quit IRC | 07:26 | |
| *** carepack has joined #sailfishos-porters | 07:30 | |
| alin | spiiroin: cool... ping me if you need any testing | 07:36 |
| alin | I shall be online once in office... | 07:36 |
| *** alin has quit IRC | 07:38 | |
| *** kimmoli_ has joined #sailfishos-porters | 07:55 | |
| *** VDVsx has quit IRC | 07:56 | |
| *** kimmoli has quit IRC | 07:58 | |
| *** kimmoli_ is now known as kimmoli | 07:59 | |
| *** boilerkim has quit IRC | 07:59 | |
| *** boilerkim has joined #sailfishos-porters | 07:59 | |
| sledges | morniing | 08:00 |
| vgrade | morning | 08:03 |
| vgrade | situ: dmse still gives the same error but the time on the device is set correctly | 08:04 |
| *** VDVsx has joined #sailfishos-porters | 08:11 | |
| *** cxl000 has joined #sailfishos-porters | 08:15 | |
| gogeta_ | morning guys | 08:16 |
| vgrade | mor | 08:17 |
| vgrade | n | 08:17 |
| oh1jty | morning | 08:17 |
| gogeta_ | I hate be in forced vacation | 08:17 |
| gogeta_ | this week i work just two days :-( | 08:17 |
| situ | vgrade: How many reboots you tried ? | 08:18 |
| vgrade | situ: 3 | 08:20 |
| situ | sledges: can you confirm it works ? | 08:20 |
| situ | sledges: on your device | 08:21 |
| situ | vgrade: I had tried commenting out time_daemon service several times and it didn't fix the issue for me. | 08:21 |
| *** alin has joined #sailfishos-porters | 08:21 | |
| *** alin has joined #sailfishos-porters | 08:21 | |
| vgrade | situ: it does not fix the setting of the hardware rtc as this seems to be an issue even in stock android, http://code.google.com/p/android/issues/detail?id=61824 | 08:22 |
| situ | vgrade: I understand that. | 08:22 |
| vgrade | but I'm getting a correct time picked up from network (wifi or mobile web) | 08:23 |
| vgrade | time shows as 1970 initially then gets updated | 08:23 |
| *** phdeswer has joined #sailfishos-porters | 08:26 | |
| vgrade | situ: http://images.devaamo.fi/sfa/hammerhead/ + 0408 nightly | 08:27 |
| dmt_ | this is my experience with time too | 08:27 |
| dmt_ | uptime of 40y | 08:27 |
| vgrade | dmt_: :) | 08:27 |
| situ | vgrade: please disable setting time from mobile web or wifi | 08:28 |
| situ | vgrade: it works for me too | 08:28 |
| situ | vgrade: do not connect to mobile or wifi while testing this. | 08:28 |
| situ | mobile internet * | 08:29 |
| situ | we want to pickup time from phone network. | 08:29 |
| vgrade | situ: well it wont set time because RTC is broken on N5 it seems | 08:29 |
| alin | vgrade: yap... that I have seen too... if I set it to automatically... | 08:29 |
| alin | vgrade: what surprises is the lack of DSME failure | 08:29 |
| vgrade | alin: there is still the same failure message | 08:30 |
| alin | vgrade: ok... then is the same situation as last week | 08:30 |
| alin | vgrade: I thought we documented this... | 08:30 |
| situ | vgrade: do you get correct time if you disable mobile web and wifi ? | 08:30 |
| vgrade | situ: right I understand now, you want to have time set without wifi or mobile internet | 08:31 |
| alin | vgrade: only half... | 08:31 |
| situ | vgrade: Yeah | 08:31 |
| *** boilerkim has quit IRC | 08:31 | |
| alin | vgrade: yes... we would like dsme not to fail | 08:31 |
| *** boilerkim has joined #sailfishos-porters | 08:31 | |
| alin | vgrade: https://wiki.merproject.org/wiki/Building_Sailfish_OS_for_Nexus_5 | 08:32 |
| alin | vgrade: I will add now the info about automatic setting | 08:32 |
| vgrade | alin: well thats not a dsme issue its an issue with the hardware, which is why qcom guys was so helpfull | 08:32 |
| alin | vgrade: I do not know I missed the help from qcom guy... | 08:33 |
| alin | vgrade: you mean the comment on situ post | 08:33 |
| alin | ? | 08:33 |
| vgrade | alin: I was being sarcastic | 08:33 |
| alin | vgrade: good one... | 08:35 |
| vgrade | situ: so if the phone network does not supply the time then I don't see how without a settable RTC we can progress | 08:35 |
| alin | vgrade: spiiroin promised he may look today into dsme | 08:36 |
| alin | vgrade: how do you know android has the same issue? I do not remember testing this | 08:36 |
| vgrade | situ: we saw from the ophono test that there was no time data from both yours and my operators | 08:36 |
| situ | vgrade: but on Jolla setting automatic time was working fine. | 08:37 |
| situ | vgrade: was it being picked up from mobile internet or wifi ? | 08:37 |
| vgrade | situ: I don't think we did that test | 08:37 |
| alin | situ: sledges vgrade dmt_ there is a snapshot today on cyanogen for hammerhead | 08:38 |
| vgrade | situ: I only showed you the output from the ophone test | 08:38 |
| alin | I will test with it and maybe we shall update our works based on it... especially as snapshots seem to stay on the cyanogen website for long time | 08:38 |
| situ | vgrade: we did the test, read the backscroll in PMs. | 08:38 |
| vgrade | situ: we also turned off auto and wifi, set clock back, then turned on auto again and time was restored | 08:44 |
| vgrade | I guess I had mobile web on | 08:44 |
| vgrade | alin, 11:22 < vgrade> situ: it does not fix the setting of the hardware rtc as this seems to be an issue even in stock android, http://code.google.com/p/android/issues/detail?id=61824 | 08:45 |
| situ | vgrade: I am aware it's an issue with stock android. | 08:45 |
| vgrade | situ: that was fro alin , 11:36 < alin> vgrade: how do you know android has the same issue? I do not remember testing this | 08:46 |
| alin | vgrade: situ cool... this starts to sound like the other bug we have seen on chromium... pasted the link some time. | 08:50 |
| alin | ago | 08:50 |
| alin | i remember the conclusion was about a race at the shitdown... and normal failure as the clocks are too far apart | 08:51 |
| situ | vgrade: 11-05 16:03:22.329 W/ ( 776): Unable to set rtc to 1383667402: Invalid argument | 08:52 |
| situ | vgrade: This error is seen when dt property to enable write access to rtc is not set. | 08:52 |
| *** VDVsx has quit IRC | 08:53 | |
| *** dmt__ has joined #sailfishos-porters | 08:53 | |
| *** dmt_ has quit IRC | 08:53 | |
| *** morphis has quit IRC | 08:53 | |
| *** sledges has quit IRC | 08:53 | |
| *** sledges has joined #sailfishos-porters | 08:54 | |
| *** sledges has quit IRC | 08:54 | |
| *** sledges has joined #sailfishos-porters | 08:54 | |
| vgrade | situ: so the same issue | 08:54 |
| vgrade | and qcom man says don't chenge the dt property | 08:55 |
| *** vrutkovs has joined #sailfishos-porters | 08:55 | |
| situ | I believe qcom was pretty dumb to disable write access to rtc. | 08:55 |
| vgrade | so without a settable hardware RTC or time picked up from wifi, mobile web, or mobile network then we will have wrong time | 08:56 |
| situ | vgrade: time_daemon utility in android stores the time on filesystem somewhere. | 08:57 |
| jusa_ | what's the HAL code for hammerhead/android 4.4.4 ? | 08:57 |
| situ | vgrade: but still I wonder how dsme picks up the right time to set to rtc. | 08:57 |
| vgrade | jusa_: HAL code? | 08:58 |
| situ | vgrade: I had mobile web and wifi disabled on my device, still dsme tried to set correct time to rtc and failed. | 08:58 |
| *** morphis has joined #sailfishos-porters | 08:59 | |
| alin | vgrade: situ https://code.google.com/p/chromium/issues/detail?id=216642 | 08:59 |
| jusa_ | vgrade: I mean for audio... hardware/VENDOR/audio in source tree | 09:00 |
| vgrade | jusa_: sex | 09:00 |
| vgrade | sec | 09:00 |
| situ | vgrade: embarassing :P | 09:00 |
| jusa_ | ;) | 09:00 |
| alin | situ: why? | 09:01 |
| jusa_ | why's this commit? https://github.com/sledges/pulseaudio-modules-droid/commit/12de3a38dc3b4733ad2f24e6b97eaafc7e3e5f8d | 09:01 |
| alin | situ: sex is as important as food... generates all that strange chemicals in the brain | 09:01 |
| jusa_ | I mean, weren't these patches for some other device than i9305? | 09:02 |
| vgrade | jusa_: yes they were from hammerhead | 09:02 |
| vgrade | except that one | 09:03 |
| jusa_ | vgrade: yep. so why is that patch there now? :) i9305 works without that IIRC.. the problem was input route setting messing with the output port.. | 09:04 |
| *** VDVsx has joined #sailfishos-porters | 09:05 | |
| jusa_ | this one: https://github.com/sledges/pulseaudio-modules-droid/commit/8b9eaffbe444faef7e07b1db78eaf5229faec3df | 09:05 |
| vgrade | jusa_: ok, I can't recall if this was needed as we did not start on hammerhead until april and that commit is from feb | 09:07 |
| vgrade | so we should have had it when we started work on hammerhead | 09:07 |
| *** dmt__ has quit IRC | 09:07 | |
| vgrade | I can test without | 09:08 |
| vgrade | oh your commit is from sledges repo | 09:08 |
| *** iTune has joined #sailfishos-porters | 09:09 | |
| sledges | my repo only adds a fix to sbj | 09:09 |
| sledges | (and renames commits) | 09:09 |
| jusa_ | I just picked that from there .. it's in upstrem master as well https://github.com/mer-hybris/pulseaudio-modules-droid/commit/8b9eaffbe444faef7e07b1db78eaf5229faec3df | 09:09 |
| sledges | i guess vgrade means to test without https://github.com/sledges/pulseaudio-modules-droid/commit/12de3a38dc3b4733ad2f24e6b97eaafc7e3e5f8d | 09:10 |
| vgrade | sledges: yes | 09:10 |
| jusa_ | good. | 09:10 |
| vgrade | jusa_: what exactly do you need from the n5 source tree I have it here | 09:11 |
| jusa_ | at least if there are some workarounds needed only for one device, comment for all devices and preferably ifdef | 09:11 |
| jusa_ | vgrade: hardware/VENDOR/audio is enough | 09:11 |
| jusa_ | vgrade: and ./system/core/include/system dir as well | 09:12 |
| jusa_ | vgrade: ..and ./hardware/libhardware/include/hardware | 09:12 |
| sledges | jusa_: if you're asking whether speaker_drc_enabled is qc specific - nope, it's HALv2 specific, checked in tree yesterday | 09:13 |
| sledges | can give you exact src line | 09:13 |
| jusa_ | sledges: yep, but I still would really like to see the whole source + headers :) | 09:13 |
| *** iTune has quit IRC | 09:13 | |
| jusa_ | if possible | 09:13 |
| *** SK_work has joined #sailfishos-porters | 09:14 | |
| *** alin has quit IRC | 09:17 | |
| sledges | secs ;) | 09:20 |
| vgrade | I've tarred | 09:20 |
| sledges | ok, i was after only this: https://github.com/CyanogenMod/android_hardware_libhardware_legacy/blob/cm-11.0/include/hardware_legacy/audio_policy_conf.h#L37 | 09:21 |
| sledges | thanks vgrade | 09:21 |
| *** alin has joined #sailfishos-porters | 09:24 | |
| *** alin has joined #sailfishos-porters | 09:24 | |
| vgrade | jusa_: http://78.47.45.43/owncloud/public.php?service=files&t=2ac375fe3ad4cf7fd7c3d27baa126c4e | 09:26 |
| vgrade | http://78.47.45.43/owncloud/public.php?service=files&t=77b9f4af9344bc6d0ee6965150c34db9 | 09:26 |
| jusa_ | vgrade: thank you | 09:28 |
| vgrade | situ: sledges alin so time where are we? | 09:31 |
| vgrade | still blocked for release? | 09:31 |
| alin | vgrade: yes and no I will say... | 09:32 |
| alin | vgrade: practically if we let it on automatic all services that check a certificate to login do not login | 09:33 |
| alin | as they try to conect before the time is set | 09:33 |
| alin | vgrade: anyhow there is little we can do about... | 09:33 |
| alin | vgrade: so all we need is to document | 09:33 |
| sledges | we can switch automatic off during install | 09:34 |
| vgrade | alin: I don;t follow the logic aout services and certificates. | 09:35 |
| sledges | vgrade: these days time has to be set to world's time, otherwise phones (e.g. https) stop working :D | 09:36 |
| vgrade | If you are connecting to services then you need a net connect and so time will be set correctly | 09:36 |
| sledges | time doesn't get set correctly immediately | 09:36 |
| sledges | even if you are connected | 09:36 |
| sledges | different strategies whether your have only modem enabled, or also wlan | 09:37 |
| vgrade | right so you can;t use the sevices until time is corrected | 09:37 |
| sledges | yes | 09:37 |
| vgrade | ok, if we are to block on this | 09:38 |
| vgrade | then what do we need to implement | 09:38 |
| alin | vgrade: set up a google account... if the time is wrong when you start the phone... the account will not come online | 09:38 |
| sledges | whoops | 09:39 |
| alin | vgrade: nothing | 09:39 |
| vgrade | alin: what do you mean | 09:41 |
| alin | vgrade: there is little we can do about that... | 09:41 |
| alin | unless instruct users to connect by hand once the time is correct | 09:42 |
| vgrade | I'm assuning we can't fix the root cause of the HW RTC not working so we have to determine if te current sailfish components can be configured to work with a broken RTC | 09:43 |
| vgrade | if not we need to implement that functionality by storing time in filesystem | 09:43 |
| sledges | and to not power-off for long periods :) | 09:44 |
| sledges | i wonder what's google's grace for time skew | 09:45 |
| sledges | vgrade: are you up to speed with this discussion: http://www.merproject.org/logs/%23nemomobile/%23nemomobile.2014-07-29.log.html#t2014-07-29T08:04:44 ? | 09:45 |
| vgrade | lets discuss with spiiroin when he gets time | 09:45 |
| sledges | and do we have whole braindump of situ's findings? | 09:45 |
| sledges | +1 | 09:45 |
| situ | sledges: I was told that timed-qt5 should read time from network and show correct time even if dsme fails to set rtc. | 09:48 |
| vgrade | situ: which network | 09:49 |
| situ | vgrade: phone network. | 09:49 |
| sledges | do we admit defeat in fixing rtc ourselves? | 09:50 |
| vgrade | situ: so how long could that take | 09:50 |
| vgrade | sledges: qcom guy says "don't do that" | 09:50 |
| situ | sledges: I believe setting rtc is disabled through TrustZone. | 09:51 |
| vgrade | sledges: and situ tried to do that and it still did not work | 09:51 |
| sledges | vgrade:p yet time_daemon manages | 09:51 |
| situ | sledges: time_daemon never sets rtc | 09:51 |
| sledges | :sigh: | 09:51 |
| dmt | is time also broken in the same way on cm/android? | 09:51 |
| vgrade | sledges: it stores it on disk | 09:51 |
| sledges | ... speechless, really!? | 09:51 |
| *** Nokius has joined #sailfishos-porters | 09:52 | |
| situ | dmt: if I reflash my Nexus 5 with stock, I have to set time manually on first boot. | 09:52 |
| sledges | dmt: fastboot boot boot.img from cm to quick check :) | 09:52 |
| situ | dmt: and default time is set to 70's on first boot even with stock android. | 09:52 |
| situ | sledges: I have checked with stock android, it has same issues. | 09:53 |
| dmt | and they get away with it by storing in fs then? | 09:53 |
| situ | dmt: right | 09:53 |
| sledges | riiight thanks now that was refreshing | 09:54 |
| dmt | who would have thought on a flaship phone there is no working rtc.. | 09:54 |
| dmt | fine ingeneering | 09:54 |
| *** Nokius1 has quit IRC | 09:54 | |
| sledges | so | 09:55 |
| sledges | no wake-up alarms from powered off phone? | 09:55 |
| sledges | ;p | 09:55 |
| situ | sledges: I don't think N5 support it. | 09:55 |
| alterego | dmt: why don't you think there's a working RTC alarm in N5? | 09:55 |
| dmt | i don't | 09:55 |
| dmt | alterego: i'm only very surprised at the reality | 09:56 |
| alterego | Hrm, anyone tried setting an alarm under android and turning phone off? | 09:57 |
| sledges | alterego: backlog? :) | 09:57 |
| sledges | time is not saved across reboots | 09:57 |
| situ | alterego: I think I have tried that once, but let me try it again. | 09:57 |
| sledges | they store it on fs | 09:57 |
| alterego | Oh, now I see :) | 09:58 |
| * sledges is looking for a door handle | 09:58 | |
| sledges | so we are just a store-on-fs-fix away for dsme ;) | 09:59 |
| situ | sledges: but when the phone boots, dsme tries to setup correct time on rtc and fails. How does dsme know correct time ? | 09:59 |
| sledges | situ: debug? | 10:00 |
| dmt | how would storing on fs work if say the phone wakes up without network? | 10:00 |
| sledges | dmt: you would only be few hours away, even less if you only rebooted | 10:00 |
| vgrade | IIRC timed changes system time when nitz date is received from cellular network; possibly connman could play some role too (ntp?) | 10:00 |
| vgrade | vgrade: that from spiiroin last chat | 10:00 |
| dmt | few hours out are a big deal if you are traveling by public transport | 10:00 |
| sledges | situ: at the beginning we were sure time_daemon gets values from hwclock on boot. how did you discover it is on filesystem? | 10:01 |
| situ | sledges: I remember it storing files somewhere, let me check. | 10:01 |
| sledges | (also let me get this straight: hwclock = rtc; system_time = software ?) | 10:01 |
| situ | alterego: I missed the alarm when phone was off. | 10:02 |
| situ | alterego: When I boot, it's shown in missed alarms in notifications. | 10:02 |
| *** lpotter has quit IRC | 10:03 | |
| *** lpotter has joined #sailfishos-porters | 10:03 | |
| alterego | situ: seriously lame :/ | 10:04 |
| sledges | dmt: no network in public transport? just try not to reboot the phone whilst commuting ;) | 10:05 |
| sledges | (especially going underground) | 10:05 |
| situ | Oops I can't run adb as root in production builds. | 10:05 |
| dmt | sledges: undergrown true, but flight mode is bigger issue | 10:05 |
| sledges | most people switch off phone for the night, it fetches time in the morning, ..., profit | 10:05 |
| situ | vgrade: Can you strace time_daemon and check what files it is reading ? | 10:06 |
| sledges | situ: worth deleting those files for good measure :)) | 10:06 |
| dmt | and say you are not on your luck abroad with no roaming for the available nets.. | 10:06 |
| sledges | dmt: emergency calls = time info | 10:06 |
| sledges | nitz | 10:06 |
| sledges | dmt: otherwise nexus5 would be recalled ;) | 10:07 |
| dmt | sledges: ok this is workable then i guess | 10:07 |
| dmt | sledges: another hypothetical: out in the fields/mountains with no net for a good while | 10:08 |
| dmt | sledges: would time halt? | 10:08 |
| sledges | if phone is powered off - ofc | 10:08 |
| dmt | sledges: or can sw alone keep it going | 10:08 |
| sledges | if on - no noticeable problems | 10:08 |
| dmt | i'll reboot without sim to try | 10:09 |
| sledges | dmt: reboot = no sw = time halt ;) | 10:09 |
| *** vakkov has joined #sailfishos-porters | 10:09 | |
| sledges | but reboot's fast, so you won't notice a thing | 10:09 |
| sledges | situ: if time_daemon does the fs storing for us, why can't we keep it? | 10:10 |
| dmt | reboot shall start from 1970 now and move from there, shan't it? | 10:10 |
| *** vakkov has quit IRC | 10:10 | |
| sledges | dmt: time_daemon enabled? | 10:11 |
| *** vakkov has joined #sailfishos-porters | 10:11 | |
| situ | sledges: because time_daemon will try to lock /dev/rtc0 which is locked by dsme's iphb module already. | 10:13 |
| dmt | seems to work, time ticks with wifi disabled and no sim | 10:13 |
| situ | sledges: and it will keep failing as it can't lock /dev/rtc0 | 10:13 |
| dmt | starts at 1.feb.1970 and goes on | 10:13 |
| situ | sledges: if we disable iphb module then time_daemon gets lock over /dev/rtc0 and shows correct time. | 10:14 |
| *** lpotter has quit IRC | 10:14 | |
| sledges | situ: ok thanks for recap | 10:14 |
| situ | sledges: but in some cases it has failed. I don't know why. | 10:14 |
| *** lpotter has joined #sailfishos-porters | 10:14 | |
| dmt | timed-qt5 is running only | 10:15 |
| vgrade | time_demon strace, http://pastebin.com/AunkVhjN | 10:16 |
| sledges | dmt: flash cm and test there if you like, too hairy state in sailfish | 10:16 |
| sledges | so plan: disable time_daemon, investigate where dsme knows correct time on startup and fails to set it; if that's false alarm (pun): patch dsme to save time to fs on hammerhead | 10:17 |
| dmt | sledges: situ said s/he tried this and it was also in the 70's | 10:17 |
| junnuvi | sledges: I got audio working on grouper.. but do you have any idea why volume control is not working? It claims that volume is muted even it's actually at 100% full time | 10:18 |
| sledges | alterego: ^ | 10:18 |
| situ | /data/system/time/ats_1 | 10:18 |
| sledges | situ: nice | 10:18 |
| sledges | vgrade: rm? ;) | 10:18 |
| situ | /data/system/time/ats_2 | 10:18 |
| situ | I don't see any other relevant files. | 10:19 |
| sledges | vgrade: taking that back, unless you got iphb deleted and that works | 10:19 |
| sledges | junnuvi: good work! :) | 10:20 |
| vgrade | sledges: I stopped dsme.service | 10:20 |
| junnuvi | sledges: thanks :) | 10:20 |
| alterego | junnuvi: probably an issue with pa configs. | 10:22 |
| junnuvi | alterego: probably, any ideas where to start investigate? with pacmd I can adjust volume levels | 10:22 |
| alterego | junnuvi: I didn't get volume working because we didn't have buttons working at that time. | 10:22 |
| alterego | junnuvi: I'm guessing you need to make sure that the pulse configs state the correct names for the audio output devices. | 10:23 |
| alterego | This is where jusa_ would probably be helpful for you :) | 10:24 |
| junnuvi | ok, I will try to compare configs between real jolla device and nexus, maybe that will help | 10:26 |
| *** furikku has quit IRC | 10:26 | |
| sledges | junnuvi: alterego: https://github.com/mer-hybris/droid-hal-device/blob/hybris-10.1/droid.kmap | 10:27 |
| sledges | your key # might differ | 10:27 |
| *** furikku has joined #sailfishos-porters | 10:27 | |
| sledges | although then it wouldn't even say "Mute" | 10:27 |
| junnuvi | I don't think bbecause I get volume level indicator when pressing volume buttons | 10:28 |
| sledges | that ;) | 10:28 |
| sledges | vgrade: if we want to double-check: completely disable time_daemon; ensure ats_* contain non-1970 date; reboot; observe date being 1970; stop dsme.service; launch time_daemon manually; see if date changes. remove ats_* files and repeat the process | 10:30 |
| sledges | (hardmasking dsme is not an option, as i don't think it will boot afterwards :) | 10:31 |
| jusa_ | junnuvi: hi.. you mean volume is constantly 100% no matter what is set as the volume? | 10:31 |
| *** vakkov has quit IRC | 10:32 | |
| *** dmt has quit IRC | 10:32 | |
| vgrade | sledges: I only masked to be able to provide the strace to situ | 10:32 |
| jusa_ | if the volume seems to change but there is no effect to the actual volume level, I'm suspecting that either 1) hw volume control of droid-sink is broken (highly possible, I haven't tested the volume control with device that would have hw volume in "normal" playback), or 2) API incorrectly reports it has hw volume when in fact it doesn't | 10:34 |
| junnuvi | jusa_: hmm, it looks like I don't have xpolicy.conf on nexus7, could that be reason? | 10:38 |
| junnuvi | jusa_: yes, volume buttons does not change volume levels, from pacmd I can change volume levels | 10:39 |
| jusa_ | junnuvi: ah, nexus 7... actually, n7 has totally different adaptation from everything else | 10:39 |
| jusa_ | junnuvi: if you want it to behave like the rest of the devices, you'll need to re-do the adaptation | 10:40 |
| jusa_ | or then merge those to somehow.. | 10:40 |
| situ | vgrade: did you try removing those files ? | 10:41 |
| situ | I tried removing those files on cm, but time is correct on next boot. | 10:43 |
| sledges | situ: good point on cm! and... odddd | 10:44 |
| situ | ioctl(1, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 | 10:44 |
| situ | what would that do ? | 10:45 |
| junnuvi | jusa_: actually it's already working pretty fine with audio. Only major issue is non-working volume controls. | 10:45 |
| jusa_ | junnuvi: yep.. the reason why the adaptation is different is n7 doesn't have voice call, so it's fairly simple to just use ALSA directly | 10:46 |
| jusa_ | you'll need to run module-stream-restore-nemo, module-meego-mainvolume, at least, to get working volume control | 10:47 |
| alin | situ: I think that file are created on the fly... I do not have them... the ones under ../time/ | 10:47 |
| alin | sledges: why do we use dsme? is really needed... seems ubuntu people do not | 10:48 |
| sledges | alin: dsme is one of the core parts for sailfish, it's responsible not only for time | 10:50 |
| alin | sledges: yes I know... looked through the code... | 10:51 |
| *** dmt has joined #sailfishos-porters | 10:51 | |
| alin | sledges: anyhow | 10:51 |
| sledges | Device State Management Entity which handles various pieces of hardware. | 10:51 |
| alin | sledges: great... | 10:53 |
| sledges | alin: you're in an awesome mood I see :D | 10:55 |
| alin | sledges: why? just wanted to know some things... | 10:59 |
| alin | sledges: now I am testing the cm snapsot and our latest image | 11:00 |
| sledges | situ: with cm, could you take out sim and disable wlan, power down for 5 mins and check the time? | 11:01 |
| sledges | alin: thanks for spotting+testing the snapshot, what a relief | 11:01 |
| situ | sledges: will check that. | 11:03 |
| *** arcean has joined #sailfishos-porters | 11:28 | |
| vgrade | ok, 13:30 < sledges> vgrade: if we want to double-check: completely disable time_daemon; ensure ats_* contain non-1970 date; reboot; observe date being 1970; stop dsme.service; launch time_daemon manually; see if date changes. remove ats_* files and repeat the process | 11:32 |
| vgrade | ok so first part on reboot time is 1970 after stopping and launching time_daemon_manually date changes to 2014 | 11:33 |
| sledges | vgrade: no sim nor wlan? | 11:34 |
| vgrade | sledges: no wlan, mobile web switched off, sim installed | 11:35 |
| sledges | ok, i wonder what will happen with files deleted (from situ's cm tests - they are not those..) | 11:36 |
| sledges | and chuck sim out once you're at it :) | 11:36 |
| sledges | if it still sets, means some other file or actual talk to hwclock via qc closed blobs | 11:36 |
| vgrade | sledges: will need to do later, dayjob calls | 11:39 |
| * sledges nods | 11:42 | |
| vgrade | for the record, | 11:43 |
| vgrade | [root@Jolla time]# hexdump ats_1 | 11:43 |
| vgrade | 0000000 50d5 4470 0142 0000 | 11:43 |
| *** vakkov has joined #sailfishos-porters | 11:51 | |
| alin | vgrade: sledges situ dmt so... with m9... todays clean build using sf-mer... phone boots | 11:52 |
| alin | we have no systemd workaround | 11:52 |
| vgrade | alin: sf-mer git has a couple of workarounds, have you edited them out | 11:54 |
| alin | vgrade: the systemd are commented out | 11:54 |
| alin | vgrade: http://paste.opensuse.org/1808701 | 11:55 |
| vgrade | ok | 11:55 |
| vgrade | reboot reliably? | 11:55 |
| alin | vgrade: by the way first boot always start with time 1 january 2013 | 11:55 |
| alin | vgrade: yes... after install I had no issues | 11:56 |
| alin | vgrade: practically wipe/factory reset... sideload cm11m9 sideload sf... reboot | 11:56 |
| alin | got the tutorial screen | 11:56 |
| *** RobJanc has joined #sailfishos-porters | 11:57 | |
| alin | sledges: this is for you... the tutorial screen (by default there is no internet activated or wifi.. but still is asking me to sign in in the jolla account) | 11:59 |
| situ | alin: Yes, timed-qt5 is programmed to set that date on first boot. | 12:00 |
| sledges | alin: it's called startup-wizard, tutorial comes later. does it offer connection dialog? | 12:01 |
| alin | sledges: no | 12:01 |
| sledges | that's the bug | 12:04 |
| sledges | there's option to skip account creation/signin | 12:04 |
| alin | sledges: yes.. | 12:05 |
| vgrade | alin: will the source repos be tagged with M9 | 12:07 |
| alin | vgrade: cyanogen ones? | 12:09 |
| vgrade | yes | 12:09 |
| alin | vgrade: I do not know | 12:09 |
| alin | vgrade: I may check... | 12:09 |
| alin | vgrade: you think of clonning only that tag? | 12:09 |
| vgrade | just looked an they are not | 12:10 |
| vgrade | at least hammerhead device | 12:10 |
| vgrade | was wondering if we should matcj the source code to the /system bins. | 12:11 |
| sledges | vgrade: which mainly means rebase ;) | 12:12 |
| vgrade | how does CM know what repos are integrated into M9 for example | 12:13 |
| vgrade | well which commit | 12:13 |
| vgrade | I mean manifest says which repo | 12:14 |
| vgrade | maybe their build system tells them | 12:15 |
| vgrade | afer a build what commit ids are for each repo | 12:15 |
| vgrade | was just wondering how they could reproduce a buld that's all | 12:16 |
| vgrade | sledges: ok ats files moved, rebooted, date is 1970, stop dsme.service, hwclock returns 1970, no new ats files created, run time_daemon , date is still 1970 | 12:39 |
| vgrade | sledges: situ so time is being read from those files | 12:39 |
| vgrade | sledges: ok, stop time_daemon, renamed files back, run time_deamon, date 2014 | 12:41 |
| vgrade | afk for a while | 12:41 |
| spiiroin | looks like dsme indeed forces system time to unmodifiable rtc time; I'll start figuring out where to change what without breaking other stuff | 12:53 |
| alin | Aug 06 13:55:42 abbaton pulseaudio[8195]: can't set volume limit: don't know group 'btnotify' | 12:57 |
| alin | spiiroin: what do you mean unmodifiable rtc time? | 12:58 |
| spiiroin | that we can't set neither rtc time or alarm | 12:58 |
| spiiroin | dsme has some logic for not going backwards in time during bootup, but it all assumes functioning rtc | 12:59 |
| spiiroin | now we need to make it take into account situations where rtc has no chance of having correct time too | 12:59 |
| spiiroin | i.e. if something else manages to get system time in sync with reality, dsme should not rewind back to seventies | 13:00 |
| *** vrutkovs has quit IRC | 13:01 | |
| *** alin_ has joined #sailfishos-porters | 13:04 | |
| *** alin has quit IRC | 13:05 | |
| spiiroin | done: a) if rtc is not writable, dsme will not sync system time to it b) if system time on dsme startup < last known system time, dsme moves system time to last known | 13:15 |
| vgrade | spiiroin: is lask known already stored somewhere | 13:17 |
| vgrade | spiiroin: or is the assumption that it in a working RTC | 13:17 |
| vgrade | its | 13:17 |
| spiiroin | yes, but as said it was used for detecting rtc resets; if rtc does not work as expected, system time is lost as collateral damage | 13:18 |
| situ | vgrade: did you figure out how dsme knows correct time to set to rtc ? | 13:19 |
| vgrade | situ: assuming from network (wifi, mobileweb) but no I've not looked any further than the testing I've done with time_daemon | 13:20 |
| situ | vgrade: on my device both wifi and mobile web were off. | 13:21 |
| vgrade | situ: and | 13:21 |
| situ | vgrade: and IIRC it was trying to set correct time in rtc and failed. | 13:22 |
| vgrade | situ: any sim card installed | 13:24 |
| situ | vgrade: yes. | 13:24 |
| spiiroin | vgrade: the last-known-time is mtime of /var/tmp/saved-time | 13:25 |
| vgrade | right ok, that says -rw-r--r-- 1 root root 0 1970-09-26 13:41 saved-time | 13:27 |
| spiiroin | mine says (after reboot) -rw-r--r-- 1 root root 0 2014-08-06 16:26 /var/tmp/saved-time | 13:30 |
| vgrade | after renabling wifi and resarting dsme so does mine | 13:32 |
| vgrade | well nearly -rw-r--r-- 1 root root 0 2014-08-06 14:31 saved-time | 13:33 |
| vgrade | assuming tz plays a part here | 13:33 |
| spiiroin | yes, but the problem is that it gets ignored without working rtc | 13:33 |
| vgrade | spiiroin: yes, understood | 13:33 |
| vgrade | so I think we just answered situ's question about where it gets good time from | 13:34 |
| situ | spiiroin: so I come back to my original suggestion to call settimeofday if setting rtc fails. | 13:35 |
| spiiroin | situ: yes, I did a bit too fast code read initially | 13:35 |
| spiiroin | hacked fix is here if someone wants to give it a go | 13:35 |
| spiiroin | https://github.com/spiiroin/dsme/commits/wip_rtc_debugging | 13:35 |
| *** iTune has joined #sailfishos-porters | 13:36 | |
| spiiroin | more specifically this commit | 13:36 |
| spiiroin | https://github.com/spiiroin/dsme/commit/0728ae080a9c8955cfa9a35b56d8cfadc7bd30d0 | 13:36 |
| spiiroin | ... but of course that fixes only the rewind issue; we still need to get correct time from somewhere | 13:37 |
| situ | spiiroin: It looks like my network operator supports network time but the tests to get network time were failing on my device. | 13:40 |
| situ | spiiroin: Can you download ofono-tests package and run the test to get network time on your device ? | 13:41 |
| spiiroin | situ: I do not have a sim in my nexus 5 atm ... | 13:41 |
| situ | spiiroin: Try on jolla device, it was failing for vgrade there. | 13:41 |
| spiiroin | situ: that I can try | 13:42 |
| situ | spiiroin: does your network operator support getting network time ? | 13:45 |
| spiiroin | ... updating & installing still | 13:45 |
| alin_ | spiiroin: dsme gets the correct time from somewhere | 13:46 |
| spiiroin | alin_: dsme gets it either from the saved-time file or rtc; otherwise it just notes that timed has changed system time | 13:47 |
| situ | I think I will just leave a rant against qcom guys on that mail thread :P | 13:48 |
| vgrade | situ: at least ask why he says "don't do that" | 13:49 |
| situ | vgrade: I think he was assuming we were on android. | 13:54 |
| situ | I had left a reply for him, haven't heard back yet. | 13:55 |
| vgrade | situ: you made it clear and even gave him a link to dsme | 13:55 |
| situ | vgrade: Right. | 13:55 |
| spiiroin | hmmm... does the rtc reset all the way back to some fixed point, or is it just not adjustable? | 13:57 |
| spiiroin | if it is the latter, then we might store rct-system_time diff at shutdown and apply it on bootup | 13:58 |
| situ | spiiroin: I think it's not adjustable. | 13:58 |
| spiiroin | situ: but it still always goes forwards? | 13:58 |
| situ | spiiroin: Yes, I think so ( I don't have sailfish running on my device right now). | 13:59 |
| spiiroin | situ: ok, I'll check once I get the ofono tests installed and done | 13:59 |
| situ | spiiroin: Great, thanks. | 14:00 |
| vgrade | spiiroin: yes hwclock returns a time moving fowwards | 14:01 |
| spiiroin | vgrade: over reboot too? | 14:01 |
| vgrade | sec | 14:01 |
| vgrade | yes hwclock time increments forward even after a reboot | 14:06 |
| spiiroin | vgrade: great, then we just need to store how much the rtc is off from system time; that should get us valid system time over reboots too | 14:07 |
| vgrade | before reboot | 14:07 |
| vgrade | Sat 26 Sep 1970 03:05:45 PM BST -1.709299 seconds | 14:07 |
| vgrade | [root@Jolla nemo]# hwclock | 14:07 |
| vgrade | Sat 26 Sep 1970 03:05:49 PM BST -1.420551 seconds | 14:07 |
| vgrade | after reboot | 14:07 |
| situ | spiiroin: but you can't trust that for every device and should not store diff. | 14:07 |
| vgrade | Sat 26 Sep 1970 03:10:43 PM BST -1.035796 seconds | 14:07 |
| vgrade | [root@Jolla nemo]# hwclock | 14:07 |
| vgrade | Sat 26 Sep 1970 03:11:11 PM BST -1.884637 seconds | 14:07 |
| spiiroin | situ: I mean locally; for that device | 14:07 |
| situ | spiiroin: but you can't trust that rtc for every device will go forward. | 14:08 |
| situ | spiiroin: or you can? | 14:08 |
| spiiroin | it is better than nothing; and only to be used if rtc is not writable | 14:09 |
| situ | spiiroin: hmm ok. | 14:09 |
| spiiroin | the rtc will probably deviate from reality anyway without support from cellular or ntp | 14:09 |
| *** alin_ has quit IRC | 14:09 | |
| spiiroin | the "store error" should not be any worse than being able to set the rtc | 14:09 |
| situ | spiiroin: ok, let's fix it. | 14:10 |
| spiiroin | situ: what is the test binary from ofono-test you wanted me to run? | 14:10 |
| situ | spiiroin: can't recall it's name, it's the which tests getting network time. | 14:11 |
| spiiroin | presumably /usr/lib/ofono/test/get-network-time? | 14:11 |
| situ | spiiroin: Yes | 14:11 |
| spiiroin | seems to be working - at least I got a timestamp { ..., UTC = 1407333960, ... } | 14:12 |
| situ | spiiroin: ok, it returns empty list for me on Nexus 5. | 14:13 |
| vgrade | returns blank for me | 14:13 |
| vgrade | [ /ril_0/operator/23430 ] Status = current Technologies = umts MobileNetworkCode = 30 Name = EE MobileCountryCode = 234 | 14:13 |
| vgrade | from this operator | 14:13 |
| vgrade | and also O2 in the Ok returned {} | 14:14 |
| vgrade | well we can't fix that | 14:15 |
| situ | spiiroin: I am sure my operator support getting network time as my Nokia N8 is able to fetch network time correctly from same operator. | 14:15 |
| situ | Could be an ofono bug. | 14:20 |
| *** alin_ has joined #sailfishos-porters | 14:26 | |
| *** alin__ has joined #sailfishos-porters | 14:31 | |
| *** alin_ has quit IRC | 14:31 | |
| *** vrutkovs_ has joined #sailfishos-porters | 14:34 | |
| alin__ | spiiroin: yes it goes forward | 14:39 |
| alin__ | from some time in 1970 | 14:39 |
| alin__ | begining of it | 14:39 |
| *** stephg has joined #sailfishos-porters | 14:50 | |
| *** gogeta_ has quit IRC | 14:51 | |
| *** phdeswer has quit IRC | 14:52 | |
| *** RobJanc has quit IRC | 14:52 | |
| dmt | is there a way to reboot into CM withouth flashing anything? | 14:56 |
| alin__ | spiiroin: Aug 29 21:28:48 abbaton DSME[684]: IPHB: set to 2014-08-06 14:38:08 GMT | 14:57 |
| alin__ | that is correct and it fails | 14:58 |
| alin__ | Aug 29 21:28:48 abbaton DSME[684]: IPHB: rtc at 1970-08-29 20:28:48 GMT | 14:58 |
| alin__ | Aug 29 21:28:48 abbaton DSME[684]: IPHB: set to 2014-08-06 14:38:08 GMT | 14:58 |
| alin__ | Aug 29 21:28:48 abbaton DSME[684]: IPHB: /dev/rtc0: RTC_SET_TIME: Invalid argument | 14:58 |
| alin__ | so from somewhere steals the correct time | 14:58 |
| vgrade | dmt: fastboot boot boot.img | 14:59 |
| vgrade | alin__: ls -l /var/lib/dsme/time-state | 14:59 |
| alin__ | vgrade: ls: cannot access /var/lib/dsme/time-state: No such file or directory | 15:00 |
| vgrade | /var/lib/dsme/timed_state | 15:01 |
| vgrade | sorry | 15:01 |
| *** carepack has quit IRC | 15:01 | |
| alin__ | vgrade: -rw-r--r-- 1 root root 4 2014-08-06 15:38 /var/lib/dsme/timed_state | 15:01 |
| alin__ | vgrade: and inside 0 0 | 15:02 |
| vgrade | alin__: so that matches what its trying to set | 15:02 |
| vgrade | alin__: the datestamp of the file | 15:02 |
| vgrade | taking the tz into account | 15:02 |
| vgrade | \o stephg | 15:03 |
| alin__ | vgrade: yap | 15:04 |
| dmt | used droid/out/target/product/hammerhead/boot.img and it went in recovery | 15:07 |
| *** JohnyZ has quit IRC | 15:08 | |
| dmt | should have downloaded something from cm | 15:08 |
| *** stephg has quit IRC | 15:09 | |
| *** JohnyZ has joined #sailfishos-porters | 15:09 | |
| vgrade | dmt: can you try adding -c "selinux=1" | 15:10 |
| dmt | with the same image? | 15:10 |
| vgrade | yeo | 15:11 |
| vgrade | if that does not work, then try a stock boot.img | 15:12 |
| spiiroin | alin__: the minval dsme uses is: max(saved_time, system_time, release_time, ...) | 15:12 |
| dmt | recovery again | 15:13 |
| spiiroin | you can see them listed if running with -v6 verbosity | 15:13 |
| spiiroin | /usr/sbin/dsme -p /usr/lib/dsme/libstartup.so -l stderr -v6 | 15:13 |
| sledges | dmt: use boot from cm.zip | 15:13 |
| vgrade | sledges: what breaks cm boot from our boot.omg | 15:14 |
| vgrade | img | 15:14 |
| vgrade | ? | 15:15 |
| sledges | lack of tests | 15:15 |
| sledges | :D | 15:15 |
| vgrade | sledges: ? | 15:15 |
| dmt | worked this time | 15:16 |
| sledges | i never thought hybris-boot generates cm's boot.img | 15:16 |
| vgrade | you mean its not been a use case | 15:16 |
| dmt | thanks | 15:16 |
| sledges | but if it does, it boots already mer-modified kernel - maybe that? | 15:16 |
| vgrade | yes it does create one , as you say one ofthe kernel option changes | 15:17 |
| sledges | ook | 15:19 |
| sledges | and initrd | 15:19 |
| sledges | probably it's just a hybris-recovery evil twin | 15:19 |
| sledges | hadk advices to rebuild cm tree separately, if run into problems | 15:19 |
| vgrade | twin should boot to sf then | 15:20 |
| vgrade | ah and it would if selinux=0 was set | 15:21 |
| vgrade | with selinux=1 sf reboots to recovery | 15:21 |
| dmt | makes sense | 15:23 |
| dmt | using android is such a pain now after not using it for a week | 15:24 |
| dmt | does anyone know how to convince the terminal (in cm) not to vibrate on touch? | 15:26 |
| dmt | i did set the things right in the general settings.. | 15:26 |
| *** gogeta_ has joined #sailfishos-porters | 15:39 | |
| sledges | vgrade: jusa_: just tested on n5: works fine with revert: https://github.com/sledges/pulseaudio-modules-droid/commit/e5bfa0a97b7a35bddbf9722d5776d5404377c194 | 15:46 |
| sledges | booted with headset plugged in , did several tests, all ok | 15:46 |
| vgrade | sledges: great. I've just tested spiiroin's new dsme | 15:47 |
| sledges | great, how is it? | 15:47 |
| vgrade | have not been tansported into the 70's yet | 15:48 |
| vgrade | but of still have the delay until time gets updated from network | 15:53 |
| *** mailyaseen has quit IRC | 15:54 | |
| *** arcean has quit IRC | 15:55 | |
| vgrade | seems mine and situs operators don't send network time, or there is somthing add going on | 15:55 |
| vgrade | so time gets updated via mobile or wifi web as an when they've connected | 15:56 |
| sledges | cross check with cm? | 16:00 |
| spiiroin | I got the saved-rtc-delta working to the point that I can: stop dsme; move date to bogus value; start dsme -> correct system time gets restored | 16:01 |
| vgrade | spiiroin: cool | 16:02 |
| *** zZz0n is now known as zon | 16:05 | |
| spiiroin | 1 sec off after reboot, but that is kind of expected when fiddling with multiple 1 sec accuracy values | 16:05 |
| *** alin__ has quit IRC | 16:06 | |
| *** alin has joined #sailfishos-porters | 16:09 | |
| spiiroin | stop dsme; set bogus date; reboot -> works too | 16:09 |
| vgrade | spiiroin: much better than 44 years out | 16:09 |
| *** vrutkovs_ has quit IRC | 16:38 | |
| locusf | hmm my device porting days are over I guess | 16:52 |
| locusf | su: /bin/bash: Resource temporarily unavailable | 16:52 |
| locusf | this is coming every time I enter Mer SDK | 16:52 |
| locusf | as it did on my earlier rootfs too | 16:52 |
| *** alin has quit IRC | 16:53 | |
| vgrade | situ: do you stil have CM installed? | 17:04 |
| dmt | locusf: did you follow the installation outlined in the pdf and wiki? | 17:08 |
| locusf | dmt: yes I did | 17:08 |
| locusf | dmt: this is something my host does every now and then | 17:08 |
| locusf | reason still unknown | 17:08 |
| dmt | locusf: archaic system/software? | 17:09 |
| locusf | dmt: ubuntu 14.04 | 17:10 |
| vgrade | locusf: spin up a new HADK environment when required with dmt's great scripts | 17:14 |
| vgrade | https://github.com/dmt4/sfa-mer | 17:14 |
| situ | vgrade: Yes | 17:14 |
| locusf | vgrade: won't work as I have tried even reinstalling | 17:15 |
| vgrade | situ: what is the delat in setting correct time on cm after boot | 17:16 |
| locusf | vgrade: I tried to debug this with lbt as well | 17:16 |
| situ | vgrade: I didn't understand the question. | 17:17 |
| vgrade | if you leave the device off for an hour how long does it take to show the correct time? | 17:17 |
| vgrade | if you have wifi and mobile web switched off | 17:18 |
| situ | vgrade: Need to test this. | 17:18 |
| vgrade | so loooking to see if it picks it up from the cell network | 17:18 |
| vgrade | or if it does something similar to spiiroin is doing and using the delta from the last RTC | 17:19 |
| situ | vgrade: I think it uses delta, I can just remove the sim and test it. | 17:20 |
| spiiroin | situ: vgrade: I pushed the rtc delta stuff to the wip branch in case you want to test it | 17:20 |
| vgrade | spiiroin: I will, cheers | 17:20 |
| situ | spiiroin: Thanks, will test it. | 17:20 |
| spiiroin | I'll go offline for some time, will check in a bit later | 17:21 |
| vgrade | locusf: sounds odd | 17:21 |
| vgrade | some interaction with somthing else installed , sailfish SDK? | 17:22 |
| *** spiiroin has quit IRC | 17:26 | |
| locusf | I do have it installed yes | 17:30 |
| *** Nokius has quit IRC | 17:34 | |
| *** dmt__ has joined #sailfishos-porters | 17:37 | |
| *** zarubond has joined #sailfishos-porters | 17:39 | |
| *** dmt has quit IRC | 17:44 | |
| *** spiiroin has joined #sailfishos-porters | 17:53 | |
| *** arcean has joined #sailfishos-porters | 17:58 | |
| vgrade | spiiroin: looks good | 18:03 |
| vgrade | needs wifi or mobile web enabled to automoticaly update a manually set time wrong time but thats issue with cell time | 18:05 |
| spiiroin | vgrade: good to know, still need to make sure that it will not break if rtc happens to be settable ;-) | 18:05 |
| vgrade | spiiroin: only have my jolla here, maybe we can get sledges to test on one of his HADK devices | 18:06 |
| jusa_ | sledges: ok, great | 18:10 |
| *** iTune has quit IRC | 18:13 | |
| vgrade | jusa_: thanks for your help | 18:16 |
| *** piggz has quit IRC | 18:26 | |
| *** Sequenced_ has joined #sailfishos-porters | 18:29 | |
| *** piggz has joined #sailfishos-porters | 18:32 | |
| *** phdeswer has joined #sailfishos-porters | 18:40 | |
| *** furikku has quit IRC | 19:04 | |
| *** zarubond has quit IRC | 19:06 | |
| *** alin has joined #sailfishos-porters | 19:26 | |
| *** alin has joined #sailfishos-porters | 19:26 | |
| alin | sledges: hi | 19:26 |
| alin | situ: vgrade dmt__ is ok with you to update the wiki and suggest m9 to be used? | 19:27 |
| vgrade | evening alin | 19:27 |
| alin | vgrade: evening | 19:27 |
| vgrade | alin: sure, I saw you tested | 19:27 |
| alin | vakkov: hi did you hear back from beidl? | 19:27 |
| alin | vgrade: yap I did.. would be nice if we will get one more test at least | 19:28 |
| vgrade | alin: I've prepared OBS, https://build.merproject.org/project/show/home:vgrade:hw:hammerhead | 19:28 |
| vgrade | the one failure will go once the pulse commit goes upstream | 19:28 |
| alin | vgrade: cool... when time comes we can make it directly the official one | 19:29 |
| vgrade | gtg dinner | 19:29 |
| alin | vgrade: ok... | 19:29 |
| vakkov | alin: haven't heard of him. have i missed something? | 19:30 |
| alin | vakkov: beidl thought you were porting maguro together | 19:33 |
| alin | vakkov: he is in army now | 19:33 |
| vakkov | alin: yes, i know ;D and yes we were :d | 19:34 |
| vakkov | haven't heard of him. I thought there is something new that i don't know :D | 19:34 |
| alin | vakkov: i see | 19:35 |
| alin | haven;t heard from him | 19:35 |
| vgrade | alin: we can hope | 19:41 |
| alin | vgrade: what is the problem with upstreaming the pulse audio? | 19:43 |
| alin | by the way... what happened with the time in the end? | 19:44 |
| vgrade | https://github.com/nemomobile/dsme/network spiiroin has made some modifications to dsme | 19:47 |
| vgrade | alin: pulse audio should be good now | 19:48 |
| alin | vgrade: cool | 19:49 |
| vgrade | alin: still an issue when wifi and mobile web are not enabled as time is not being brought from the carriers situ and I use | 19:49 |
| alin | vgrade: I shall delete my branch on time... I see he did not commit anything back | 19:49 |
| alin | vgrade: but this is strange by default none are enbaled when one starts the phone | 19:50 |
| alin | i still do not understand where dsme gets the correct time | 19:50 |
| alin | the one is trying to set and fails | 19:51 |
| vgrade | alin: you mean on first boot, you are asked what the time is. That will be stored now with the changes spiiroin has made today | 19:51 |
| alin | yes... | 19:52 |
| alin | that is nice | 19:52 |
| alin | Aug 29 21:28:48 abbaton DSME[684]: IPHB: set to 2014-08-06 14:38:08 GMT | 19:52 |
| alin | but this one... is taken from somewhere and is right | 19:52 |
| vgrade | alin: what conditions? | 19:53 |
| alin | vgrade: I mean not mobile internet and no wifi | 19:55 |
| vgrade | and not set by you | 19:55 |
| vgrade | and not set via carrier update | 19:55 |
| vgrade | and not set by time_daemon | 19:56 |
| alin | vgrade: was probably set by me | 19:58 |
| alin | time _daemon i disable after install | 19:59 |
| alin | automatic update disabled | 19:59 |
| *** piggz has quit IRC | 20:15 | |
| *** shallow is now known as potlesk | 20:20 | |
| alin | sledges: what about gps you said something about it and the word success | 20:24 |
| vgrade | alin: last I remember it needed a bit of mw glue | 20:26 |
| *** piggz has joined #sailfishos-porters | 20:27 | |
| vgrade | going for an early one tonight, see you tomorrow | 20:28 |
| *** piggz has quit IRC | 20:39 | |
| alin | vgrade: night | 20:39 |
| *** piggz has joined #sailfishos-porters | 20:39 | |
| *** Xtal_ has joined #sailfishos-porters | 20:42 | |
| *** zon is now known as zZz0n | 20:57 | |
| *** Xtal_ has quit IRC | 21:05 | |
| *** lbt has quit IRC | 21:14 | |
| *** lbt has joined #sailfishos-porters | 21:14 | |
| *** Xtal_ has joined #sailfishos-porters | 21:23 | |
| gogeta_ | guys | 21:25 |
| *** Xtal_ has quit IRC | 21:27 | |
| *** Xtal_ has joined #sailfishos-porters | 21:27 | |
| *** Xtal_ has quit IRC | 21:34 | |
| spiiroin | situ: vgrade: wip branch updated again; should now work in device that have settable rtc too | 21:45 |
| *** gogeta_ has quit IRC | 21:57 | |
| *** netchip has quit IRC | 22:22 | |
| *** chrisi has quit IRC | 23:03 | |
| *** cxl000 has quit IRC | 23:06 | |
| alin | spiiroin: ok... I will build it and test it | 23:19 |
| *** chrisi has joined #sailfishos-porters | 23:24 | |
| sledges | alin: i've passed the GPS bug internally, and sailors from australia replied - that's why i said [the bugzilla infra] is working :p Now I'm waiting for details on how much effort is required to fix this bug, and can community help (bit harder here, as it revolves around some sailfish components) | 23:32 |
| sledges | nightn :) | 23:33 |
| alin | sledges: night | 23:35 |
| alin | some strange error on obs | 23:35 |
| alin | https://build.merproject.org/package/show/home:alin:extra/dsme | 23:35 |
| sledges | alin: set _service url to https://github.com/spiiroin/dsme.git | 23:37 |
| sledges | and add <param name="revision">HEAD</param> | 23:37 |
| sledges | (you have it set without the ".git" bit) | 23:37 |
| alin | sledges: yap you are right... I hshall go to sleap... | 23:38 |
| alin | sleep | 23:38 |
| sledges | same here | 23:38 |
| sledges | sleep 28800 | 23:38 |
| alin | sledges: so long? I will kill my two neurons | 23:41 |
| alin | more like 12000 | 23:41 |
| alin | spiiroin: | 23:44 |
| alin | [ 53s] configure.ac=0.66.10 vs /home/abuild/rpmbuild/SOURCES/dsme.spec=0.62.13+master.928.253.g4f8d296 | 23:44 |
| alin | [ 53s] Conflicting package versions | 23:44 |
| alin | [ 53s] error: Bad exit status from /var/tmp/rpm-tmp.4xhjS4 (%build) | 23:44 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!