Monday, 2016-04-04

*** jpaana <jpaana!jpaana@s2.org> has quit IRC (Ping timeout: 260 seconds)00:17
*** jpaana <jpaana!jpaana@s2.org> has joined #sailfishos-porters00:29
*** jpaana <jpaana!jpaana@s2.org> has quit IRC (Ping timeout: 260 seconds)00:36
*** jpaana <jpaana!jpaana@s2.org> has joined #sailfishos-porters00:39
*** Piggz <Piggz!~sailfish@195.147.64.197> has quit IRC (Ping timeout: 276 seconds)00:40
*** krnlyng <krnlyng!~liar@178.114.108.65.wireless.dyn.drei.com> has quit IRC (Ping timeout: 244 seconds)01:24
*** krnlyng <krnlyng!~liar@178.112.136.24.wireless.dyn.drei.com> has joined #sailfishos-porters01:38
*** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 276 seconds)03:00
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Ping timeout: 244 seconds)03:33
*** spiiroin <spiiroin!~spiiroin@37-33-89-39.bb.dnainternet.fi> has quit IRC (Ping timeout: 244 seconds)04:25
*** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has joined #sailfishos-porters04:46
*** olafh_ <olafh_!~olafh@p4FF48416.dip0.t-ipconnect.de> has joined #sailfishos-porters04:57
*** spiiroin <spiiroin!~spiiroin@2001:998:2a:dead:64f0:c859:64d1:20f0> has joined #sailfishos-porters04:57
*** mkosola <mkosola!~mkosola@a91-153-5-151.elisa-laajakaista.fi> has quit IRC (Quit: Leaving.)05:01
*** AC is now known as dwangoAC05:02
*** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 260 seconds)05:06
*** vakkov <vakkov!~vakkov@ic-s221n133.brunel.ac.uk> has joined #sailfishos-porters05:17
*** hashcore <hashcore!~hashcore@unaffiliated/hashcore> has quit IRC (Ping timeout: 268 seconds)05:44
*** dvogel <dvogel!~dorianvog@2a01:e35:1386:6020:c685:8ff:feb1:b1f6> has joined #sailfishos-porters05:45
*** AYEHAN <AYEHAN!~behave@111.68.108.75> has joined #sailfishos-porters05:50
*** mkosola <mkosola!~mkosola@2001:998:2a:dead:6921:d9d5:ccad:cc16> has joined #sailfishos-porters05:52
*** dvogel <dvogel!~dorianvog@2a01:e35:1386:6020:c685:8ff:feb1:b1f6> has quit IRC (Quit: Konversation terminated!)06:08
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC (Ping timeout: 240 seconds)06:51
*** hashcore <hashcore!~hashcore@unaffiliated/hashcore> has joined #sailfishos-porters06:54
*** Nokius_ <Nokius_!~Nokius@p5DDB6C21.dip0.t-ipconnect.de> has joined #sailfishos-porters07:03
*** Nokius <Nokius!~Nokius@p5DDB7AE3.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 276 seconds)07:06
*** nh1402_work <nh1402_work!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has joined #sailfishos-porters07:06
nh1402_workmorning07:07
*** Nokius_ is now known as Nokius07:10
stephgmondning!07:10
Nokiusmorning07:10
*** hashcore <hashcore!~hashcore@unaffiliated/hashcore> has quit IRC (Ping timeout: 264 seconds)07:19
*** sletta <sletta!~sletta@226.194.251.212.customer.cdi.no> has joined #sailfishos-porters07:26
*** harha <harha!~harha@194.157.27.2> has joined #sailfishos-porters07:28
*** Jef91 <Jef91!~jeff@c-98-215-112-164.hsd1.il.comcast.net> has quit IRC (Ping timeout: 250 seconds)07:37
*** jfred <jfred!~quassel@pool-173-61-32-195.cmdnnj.fios.verizon.net> has quit IRC (Ping timeout: 250 seconds)07:37
*** Jef91 <Jef91!~jeff@c-98-215-112-164.hsd1.il.comcast.net> has joined #sailfishos-porters07:37
*** krnlyng <krnlyng!~liar@178.112.136.24.wireless.dyn.drei.com> has quit IRC (Ping timeout: 268 seconds)07:37
*** a__ <a__!~a__@pool-108-46-65-96.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 250 seconds)07:39
*** Nokius <Nokius!~Nokius@p5DDB6C21.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 268 seconds)07:39
*** deztructor_ <deztructor_!~deztructo@146.185.157.67> has quit IRC (Ping timeout: 268 seconds)07:39
*** Nokius <Nokius!~Nokius@p5DDB6C21.dip0.t-ipconnect.de> has joined #sailfishos-porters07:39
*** jfred <jfred!~quassel@pool-173-61-32-195.cmdnnj.fios.verizon.net> has joined #sailfishos-porters07:40
*** krnlyng <krnlyng!~liar@178.112.136.24.wireless.dyn.drei.com> has joined #sailfishos-porters07:42
*** deztructor_ <deztructor_!~deztructo@146.185.157.67> has joined #sailfishos-porters07:43
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has joined #sailfishos-porters07:46
*** electrolux <electrolux!~electrolu@dyj-f6yg4g52g1wv8535t-3.rev.dnainternet.fi> has joined #sailfishos-porters08:02
*** rinigus <rinigus!~rinigus@kybi.ioc.ee> has joined #sailfishos-porters08:03
*** tanty_off is now known as tanty08:13
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has joined #sailfishos-porters08:15
*** ZucZero <ZucZero!~zucca@85-76-99-231-nat.elisa-mobile.fi> has quit IRC (Quit: WeeChat 1.3)08:16
*** Zucca <Zucca!~zucca@85-76-99-231-nat.elisa-mobile.fi> has joined #sailfishos-porters08:17
*** cxl000 <cxl000!~cxl000@c27-253-5-120.brodm4.vic.optusnet.com.au> has joined #sailfishos-porters08:21
rinigusmorning! sun is shining, winter is over, and its time to transfer nexus4 from a small heating device into a green computer. right now, it battery consumption could easily be ~5-6%/hour on idle. as a result, keeping juice for one day becomes problematic. I'm pasting the issue here - if there is a better place, let me know.08:29
*** ghosalmartin <ghosalmartin!~ghosalmar@90.216.134.194> has joined #sailfishos-porters08:29
rinigusI looked a bit around and found that sensors service is consuming at least 50% of the standby energy. simple test: leaving over night without network and all programs closed could consume ~30% during 6 h = 5%/h . if I switch sensors service off - 8% / 6h = 1.3%/h. cc ballock sledges08:29
rinigustest 2: network was on, mako idle, screen off, 5 min measurement. measured using powertop. with sensors service enabled, I get 95 wakeups/s. without sensors (systemctl stop sensors...), I get it down to 32 wakeups/s.08:29
rinigustest 3: same as test 2, measured using /proc/timer_stats and related to the wall clock. with sensors, 128 timers/s. without sensors: 40 timers/s.08:30
rinigusin summary, all tests give the same result: sensors are a good starting point. there are reports on N5 & sensors issues, I guess we have the similar problem on N4.08:30
rinigusballock and sledges: is there any easy way to disable sensors one by one?08:30
rinigusballock and sledges: alternative, do we actually need sensors while on idle? most are needed with screen, proximity on call. maybe we should switch them off otherwise? while testing I had the problem with restarting rotation sensor, but that was only once.08:30
* Stskeeps idly wonders what rinigus's day job is08:31
ballockGood morning! I admin the weather is nice and the moods are better :)08:34
locusfyou control the weather? nice .. :)08:35
ballocklocusf: Yes. When I move traffic between DCs, thousands of servers' load goes up, and so does the temperature!08:36
locusfheheh08:37
mal-rinigus: you can disable sensors from /etc/sensorfw/primaryuse.conf08:38
ballockrinigus: I'd need to check what the problem with N5 was, I thought it was way worse than on N4, and happened on Android as well (though less visible).08:39
kehrnoo_what about /etc/xdg/QtProject/Sensors.conf?08:39
rinigusmal-: so, that's the place where I can comment them out one by one, right? what's comment char? ;?08:40
kehrnoo_most likely #08:40
mal-kehrnoo_: that is the higher level configuration08:41
riniguskehrnoo_: thnx. I see, I guess it would be a good idea to have /etc/xdg/QtProject/Sensors.conf and  /etc/sensorfw/primaryuse.conf consistent. any other places to check?08:43
kehrnoo_oh, good to know08:51
ghosalmartinmorning09:11
sledgesg09:12
ghosalmartini wonder if it would ever be possible to force vendors to give both 32bit and 64bit binaries :P09:16
ballockghosalmartin: I would be ok, even if they provided the sources without either of the binaries.09:28
ghosalmartinballock: thats the dream09:28
ballockghosalmartin: let's make it a plan.09:31
ghosalmartinballock: somehow I don't think it will ever be possible09:32
ghosalmartinunless we start writing drivers now :P09:32
ballockLinux was a good hammer to enforce the source from the vendors to us09:33
ballockthough it seems it's not only about the kernel09:33
ghosalmartinballock: indeed, am surprised that we have bluetooth drivers in the kernel for the nexus devices tbh09:41
*** romu <romu!~romu@89.225.199.90> has joined #sailfishos-porters09:47
*** romu is now known as romu_09:47
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has quit IRC (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)09:56
romu_hi porters, I'm still investigating the sensors issue on the N5. I found that the sensors framework can stop working, but the processes remain alive while not eating the CPU. I just wonder if someone may have an idea about how a way to diagnose?09:57
sledgesromu_: is sensors framework also a process? (e.g. shows in `top` or `ps ax`?)10:02
romu_yes 2, sensors.qcom and sensorfwd10:02
sledgesso which processes stop, and which remain?10:03
*** electrolux <electrolux!~electrolu@dyj-f6yg4g52g1wv8535t-3.rev.dnainternet.fi> has quit IRC (Quit: Leaving.)10:13
*** harha1 <harha1!~harha@194.157.27.2> has joined #sailfishos-porters10:18
*** harha <harha!~harha@194.157.27.2> has quit IRC (Ping timeout: 276 seconds)10:21
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has joined #sailfishos-porters10:24
spiiroinrinigus: basically all the sensors (except proximity, and to limited degree als) should be turned off when display is not on; whether the sfos sensorfwd manages to make it work that way is one thing to check ...10:37
spiiroinrinigus: basically if display is off and a sensor does not have "standbyoverride" property set -> the sensor should be powered off10:39
rinigusspiiroin: good to know. now, according to my tests (powertop & /proc/timer_stats) that's not the case. unless sensors service itself is doing somethig.10:52
rinigusspiiroin: where could that property be set? "standbyoverride"?10:53
spiiroinrinigus: it is set over dbus, you can check with something like: dbus-send --system --type=method_call --print-reply --dest=com.nokia.SensorService /SensorManager/orientationsensor org.freedesktop.DBus.Properties.GetAll string:local.OrientationSensor10:54
spiiroinrinigus: but normally that standbyOverride is set only by mce process (for als, ps, orientation)10:55
spiiroinrinigus: in practice only ps should have it on when display is off10:56
spiiroinrinigus: for als/orientation it is set when mce is about to turn on display -> to allow sensor power up happen parallel with display power up10:56
rinigusspiiroin: I'll check it out a bit later. Do you have one more magic command which could help me to check whether sensors are actually running or not when the screen is off?10:58
spiiroinrinigus: the ones that generate evdev events (als & ps usually) -> you can use "evdev_trace"10:59
spiiroinrinigus: also, if you do "mcetool --set-als-mode=disabled --set-ps-mode=disabled --set-orientation-sensor-mode=disabled" -> mce does not use sensors -> no sensor should have the standByOverride set11:00
romu_sledges: sorry, lunch time. It depends. 1. the 2 processes stay alive but eat too much CPU, that's the most often case11:04
romu_2. The sensors.qcom process stays alive with a normal CPU consumption, but the sensorfwd is kiiled11:05
romu_3. Both processes stay alive with a normal CPU consumption but sensors don't work11:06
romu_Of course, case 3 is the most difficult to detect with a script11:06
romu_But case 3 is also the most rare case11:07
*** drFaustroll <drFaustroll!~alin@opensuse/member/ealin> has joined #sailfishos-porters11:27
rinigusspiiroin: excellent! I'll test it then tonight. first, whether anything else has "standbyoverride". second, whether I can find sensor(s) leading to these wakeups.11:28
sledgesromu_: how is sensorfwd killed? by user?11:31
romu_sledges: don't know, each time I see the sensors don't work, I'm logging in with SSH and see what happens with the processes and sometimes, the sensorfwd process is not listed.11:34
romu_But not killed by me intentionnally for sure11:34
*** zhxt__ <zhxt__!~zhxt@124.207.50.249> has quit IRC (Ping timeout: 264 seconds)11:37
romu_I've seen that when the sensorfwd has been killed, restarting directly the sensorfwd service doesn't work. I've to kill the sensors.qcom process first, and then, I can restart the sensorfwd service.11:43
nh1402_worksledges: I've just realised something, when was that flip phone over to silence the phone when someone calls implemented?, could that have caused the sensor bug?11:53
*** M-jon <M-jon!jonterracr@gateway/shell/matrix.org/x-glbfhrwxybkhemrs> has quit IRC (Remote host closed the connection)11:53
*** M-bobsummerwill <M-bobsummerwill!bobsummerw@gateway/shell/matrix.org/x-tmbpynxtycgowava> has quit IRC (Remote host closed the connection)11:53
sledgesspiiroin: nh1402_work has good point ^11:54
*** Litew <Litew!~tradiz@194.226.137.84> has joined #sailfishos-porters12:05
*** M-bobsummerwill <M-bobsummerwill!bobsummerw@gateway/shell/matrix.org/x-yynbvbjvniebuklm> has joined #sailfishos-porters12:16
*** zhxt__ <zhxt__!~zhxt@106.39.222.33> has joined #sailfishos-porters12:23
*** Zucca <Zucca!~zucca@85-76-99-231-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 260 seconds)12:23
*** ZucZero <ZucZero!~zucca@85-76-96-136-nat.elisa-mobile.fi> has joined #sailfishos-porters12:23
*** zhxt__ <zhxt__!~zhxt@106.39.222.33> has quit IRC (Ping timeout: 244 seconds)12:28
*** M-jon <M-jon!jonterracr@gateway/shell/matrix.org/x-dnhiqudeeqixkozz> has joined #sailfishos-porters12:28
*** electrolux <electrolux!~electrolu@82-181-109-250.bb.dnainternet.fi> has joined #sailfishos-porters12:35
*** Aoyagi_fehtop <Aoyagi_fehtop!~Aoyagi@unaffiliated/aoyagi> has quit IRC (Ping timeout: 248 seconds)12:40
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:14
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has quit IRC (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)13:15
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has joined #sailfishos-porters13:16
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Remote host closed the connection)13:16
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:17
*** spiiroin <spiiroin!~spiiroin@2001:998:2a:dead:64f0:c859:64d1:20f0> has quit IRC (Ping timeout: 250 seconds)13:26
*** CarlosMazieri <CarlosMazieri!~b35201@gate-tx3.freescale.com> has joined #sailfishos-porters13:28
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:29
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Read error: Connection reset by peer)13:29
*** romu <romu!~romu@89.225.199.90> has joined #sailfishos-porters13:33
*** romu_ <romu_!~romu@89.225.199.90> has quit IRC (Ping timeout: 244 seconds)13:34
*** romu <romu!~romu@89.225.199.90> has quit IRC (Client Quit)13:34
*** romu <romu!~romu@89.225.199.90> has joined #sailfishos-porters13:34
*** harha1 <harha1!~harha@194.157.27.2> has quit IRC (Quit: Leaving.)13:35
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Read error: Connection reset by peer)13:35
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:35
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Remote host closed the connection)13:35
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:36
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:37
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Read error: Connection reset by peer)13:37
*** spiiroin <spiiroin!~spiiroin@37-33-89-39.bb.dnainternet.fi> has joined #sailfishos-porters13:45
*** Lipevakala_ <Lipevakala_!~sailfish@62-78-219-131.bb.dnainternet.fi> has joined #sailfishos-porters13:47
*** Lipevakala <Lipevakala!~sailfish@62-78-219-131.bb.dnainternet.fi> has quit IRC (Ping timeout: 248 seconds)13:48
*** romu <romu!~romu@89.225.199.90> has quit IRC (Ping timeout: 260 seconds)13:58
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has quit IRC (Remote host closed the connection)14:09
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has joined #sailfishos-porters14:09
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has joined #sailfishos-porters14:10
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has joined #sailfishos-porters14:11
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has joined #sailfishos-porters14:11
*** jason972000__ <jason972000__!c6b15f81@gateway/web/freenode/ip.198.177.95.129> has joined #sailfishos-porters14:19
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has quit IRC (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)14:31
*** Mister_Magister <Mister_Magister!~Mister_Ma@213.146.59.128> has joined #sailfishos-porters14:32
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has joined #sailfishos-porters14:32
*** perillamint <perillamint!~perillami@121.128.220.164> has quit IRC (Remote host closed the connection)14:47
*** rinigus <rinigus!~rinigus@kybi.ioc.ee> has quit IRC (Quit: Leaving)14:50
*** Litew <Litew!~tradiz@194.226.137.84> has quit IRC (Remote host closed the connection)14:55
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has quit IRC (Remote host closed the connection)15:04
*** L29Ah <L29Ah!~L29Ah@cl-154.led-01.ru.sixxs.net> has joined #sailfishos-porters15:05
*** maikoool_away is now known as maikoool15:20
*** nh1402_work <nh1402_work!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has quit IRC (Remote host closed the connection)15:33
*** electrolux <electrolux!~electrolu@82-181-109-250.bb.dnainternet.fi> has quit IRC (Quit: Leaving.)15:49
*** ZucZero <ZucZero!~zucca@85-76-96-136-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 248 seconds)15:58
*** ZucZero <ZucZero!~zucca@85-76-149-73-nat.elisa-mobile.fi> has joined #sailfishos-porters16:00
*** ghosalmartin <ghosalmartin!~ghosalmar@90.216.134.194> has quit IRC (Remote host closed the connection)16:04
*** Litew <Litew!~tradiz@broadband-77-37-218-203.nationalcablenetworks.ru> has joined #sailfishos-porters16:15
*** electrolux <electrolux!~electrolu@82-181-109-250.bb.dnainternet.fi> has joined #sailfishos-porters16:15
*** Zuccace <Zuccace!~zucca@85-76-162-141-nat.elisa-mobile.fi> has joined #sailfishos-porters16:20
*** ZucZero <ZucZero!~zucca@85-76-149-73-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 248 seconds)16:21
*** Sazpaimon_ <Sazpaimon_!~Sazpaimon@unaffiliated/Sazpaimon> has quit IRC (Read error: Connection reset by peer)16:22
*** nh1402 <nh1402!~Thunderbi@95.148.89.122> has joined #sailfishos-porters16:25
*** Mavireck <Mavireck!5a026c41@gateway/web/freenode/ip.90.2.108.65> has joined #sailfishos-porters16:26
*** NeKit <NeKit!~nekit@111.0.193.153> has quit IRC (Ping timeout: 276 seconds)16:27
*** Sazpaimon <Sazpaimon!~Sazpaimon@unaffiliated/Sazpaimon> has joined #sailfishos-porters16:28
*** Sazpaimon is now known as Sazpaimon_16:28
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has quit IRC (Ping timeout: 276 seconds)16:28
*** Mavireck <Mavireck!5a026c41@gateway/web/freenode/ip.90.2.108.65> has quit IRC (Ping timeout: 250 seconds)16:45
*** Mavireck <Mavireck!5a026c41@gateway/web/freenode/ip.90.2.108.65> has joined #sailfishos-porters16:49
*** jason972000__ <jason972000__!c6b15f81@gateway/web/freenode/ip.198.177.95.129> has left #sailfishos-porters17:07
*** Mavireck <Mavireck!5a026c41@gateway/web/freenode/ip.90.2.108.65> has quit IRC (Ping timeout: 250 seconds)17:08
*** piggz <piggz!~piggz@195.147.64.197> has joined #sailfishos-porters17:08
*** tanty is now known as tanty_off17:14
*** uvatbc <uvatbc!~uv@c-73-189-176-220.hsd1.ca.comcast.net> has joined #sailfishos-porters17:15
*** Kaligule <Kaligule!~Kaligule@2001:a62:183:9401:5e51:4fff:fe9f:fe57> has joined #sailfishos-porters17:17
*** Litew <Litew!~tradiz@broadband-77-37-218-203.nationalcablenetworks.ru> has quit IRC (Remote host closed the connection)17:23
*** electrolux <electrolux!~electrolu@82-181-109-250.bb.dnainternet.fi> has quit IRC (Quit: Leaving.)17:24
KaliguleHi there. I would like to install sailfishos on my fairphone, and I already found some instructions. But it is not easy for me to see what the newest compatible version of SFos would be. Where should I look? Is the merprojectwiki the way to go?17:26
nh1402Kaligule: Fairphone 1 or 2?17:26
*** piggz <piggz!~piggz@195.147.64.197> has quit IRC (Ping timeout: 244 seconds)17:27
Kaligulenh1402: Fairphone 217:31
nh1402I do believe the merproject wiki is the way to go.17:33
nh1402https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_fp217:33
*** SfietKonstantinW <SfietKonstantinW!c2623324@gateway/web/cgi-irc/kiwiirc.com/ip.194.98.51.36> has quit IRC (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)17:35
mal-Kaligule: that link contains the instructions for the installation of the most recent sailfish image17:35
KaliguleThanks, thats what I'm gonna try :)17:36
nh1402dirkvl: http://www.xda-developers.com/lg-invites-registrations-for-play-with-friends-developer-event/17:37
*** drFaustroll <drFaustroll!~alin@opensuse/member/ealin> has quit IRC (Remote host closed the connection)17:42
*** spider-mario <spider-mario!~spidermar@178-83-188-253.dynamic.hispeed.ch> has joined #sailfishos-porters17:52
*** piggz <piggz!~piggz@195.147.64.197> has joined #sailfishos-porters17:59
piggzyo18:00
*** uvatbc <uvatbc!~uv@c-73-189-176-220.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 250 seconds)18:12
*** uvatbc <uvatbc!~uv@c-73-189-176-220.hsd1.ca.comcast.net> has joined #sailfishos-porters18:17
*** Tassadar <Tassadar!~tassadar@ip-94-112-203-136.net.upcbroadband.cz> has joined #sailfishos-porters18:22
*** vakkov <vakkov!~vakkov@ic-s221n133.brunel.ac.uk> has quit IRC (Ping timeout: 244 seconds)18:27
*** maikoool is now known as maikoool_away18:31
*** IHAVENONICK <IHAVENONICK!~zucca@85-76-1-191-nat.elisa-mobile.fi> has joined #sailfishos-porters18:40
*** Zuccace <Zuccace!~zucca@85-76-162-141-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 248 seconds)18:40
*** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has joined #sailfishos-porters18:42
*** IHAVENONICK <IHAVENONICK!~zucca@85-76-1-191-nat.elisa-mobile.fi> has quit IRC (Client Quit)18:43
*** Zucca <Zucca!~zucca@85-76-1-191-nat.elisa-mobile.fi> has joined #sailfishos-porters18:44
*** dvogel <dvogel!~dorianvog@2a01:e35:1386:6020:c685:8ff:feb1:b1f6> has joined #sailfishos-porters18:51
*** drFaustroll <drFaustroll!~alin@opensuse/member/ealin> has joined #sailfishos-porters18:51
*** Jettis <Jettis!~h0h0@a88-115-37-93.elisa-laajakaista.fi> has quit IRC (Ping timeout: 260 seconds)18:59
*** Jettis <Jettis!~h0h0@a88-115-37-93.elisa-laajakaista.fi> has joined #sailfishos-porters19:00
*** piggz <piggz!~piggz@195.147.64.197> has quit IRC (Quit: Konversation terminated!)19:04
*** phdeswer_ <phdeswer_!~phdeswer@91-159-55-220.elisa-laajakaista.fi> has joined #sailfishos-porters19:21
*** rinigus <rinigus!~rinigus@tabasalu-gw.radionet.ee> has joined #sailfishos-porters19:24
*** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 246 seconds)19:34
*** rinigus <rinigus!~rinigus@tabasalu-gw.radionet.ee> has quit IRC (Quit: Leaving)19:34
*** rinigus <rinigus!~rinigus@tabasalu-gw.radionet.ee> has joined #sailfishos-porters19:35
rinigusspiiroin: dbus command did not produce any sensors with standbyoverride. there was one, but it was set to false19:36
rinigusspiiroin, ballock and sledges: and the winner is .... proximity sensor!19:36
rinigusspiiroin, ballock, sledges: when I used mcetool to keep only one of the three sensorss active, then configuration --set-als-mode=disabled --set-ps-mode=enabled --set-orientation-sensor-mode=disabled produced ~60 wakeups/s more than when ps-mode was disabled19:38
rinigus... it was a bit tricky since sometimes even that config let to low wakeups, but after some stats I am pretty confident that proximity sensor is making most of the wakeups.19:40
rinigusballock, sledges: you enabled proximity in the new cm11-based ballock port. how can I make proximity enabled only during calls?19:41
rinigus... and I'm off.19:41
*** rinigus <rinigus!~rinigus@tabasalu-gw.radionet.ee> has quit IRC (Quit: Leaving)19:41
*** Kaligule <Kaligule!~Kaligule@2001:a62:183:9401:5e51:4fff:fe9f:fe57> has quit IRC (Quit: WeeChat 1.4)19:45
*** vakkov <vakkov!~vakkov@ic-s221n133.brunel.ac.uk> has joined #sailfishos-porters19:46
*** piggz <piggz!~piggz@195.147.64.197> has joined #sailfishos-porters19:52
*** harha <harha!~harha@a91-152-204-157.elisa-laajakaista.fi> has joined #sailfishos-porters19:56
*** Mister_Magister <Mister_Magister!~Mister_Ma@213.146.59.128> has quit IRC (Remote host closed the connection)20:02
*** harha <harha!~harha@a91-152-204-157.elisa-laajakaista.fi> has quit IRC (Quit: Leaving.)20:08
*** Mister_Magister <Mister_Magister!~Mister_Ma@213.146.59.128> has joined #sailfishos-porters20:49
*** ghosalmartin <ghosalmartin!~ghosalmar@cpc67891-seac23-2-0-cust264.7-2.cable.virginm.net> has joined #sailfishos-porters20:52
*** edubai__ <edubai__!uid39243@gateway/web/irccloud.com/x-lyjpghhfpaiqzrim> has quit IRC (Quit: Connection closed for inactivity)20:55
*** ghosalmartin <ghosalmartin!~ghosalmar@cpc67891-seac23-2-0-cust264.7-2.cable.virginm.net> has quit IRC (Quit: Leaving)20:56
*** Aoyagi_fehtop <Aoyagi_fehtop!~Aoyagi@unaffiliated/aoyagi> has joined #sailfishos-porters21:03
*** Mister_Magister <Mister_Magister!~Mister_Ma@213.146.59.128> has quit IRC (Quit: Leaving)21:08
*** adfad666_ <adfad666_!uid156256@cyanogenmod/maintainer/adfad666> has joined #sailfishos-porters21:11
*** adfad666 <adfad666!~sid597@cyanogenmod/maintainer/adfad666> has quit IRC (Disconnected by services)21:13
*** adfad666_ is now known as adfad66621:13
*** taaem <taaem!~taaem@unaffiliated/taaem> has quit IRC (Ping timeout: 240 seconds)21:31
*** Tassadar <Tassadar!~tassadar@ip-94-112-203-136.net.upcbroadband.cz> has quit IRC (Ping timeout: 276 seconds)21:35
*** nh1402 <nh1402!~Thunderbi@95.148.89.122> has quit IRC (Ping timeout: 268 seconds)21:36
*** keithzg__ <keithzg__!~keithzg@184.70.164.246> has quit IRC (Remote host closed the connection)21:37
*** keithzg <keithzg!~keithzg@184.70.164.246> has joined #sailfishos-porters21:37
Nokiusfixing things before showing is not a good idea21:38
Nokiusdunno why scorpion is boot looping when not attached to usb cable21:41
*** piggz <piggz!~piggz@195.147.64.197> has quit IRC (Remote host closed the connection)21:43
*** piggz <piggz!~piggz@195.147.64.197> has joined #sailfishos-porters21:44
*** harha <harha!~harha@a91-152-204-157.elisa-laajakaista.fi> has joined #sailfishos-porters21:50
*** harha <harha!~harha@a91-152-204-157.elisa-laajakaista.fi> has joined #sailfishos-porters21:50
*** harha <harha!~harha@a91-152-204-157.elisa-laajakaista.fi> has quit IRC (Ping timeout: 240 seconds)21:55
*** uvatbc <uvatbc!~uv@c-73-189-176-220.hsd1.ca.comcast.net> has quit IRC (Quit: Leaving.)22:31
*** Aoyagi_fehtop <Aoyagi_fehtop!~Aoyagi@unaffiliated/aoyagi> has quit IRC (Ping timeout: 264 seconds)22:46
*** char-x <char-x!~char-x@p5B1742CC.dip0.t-ipconnect.de> has joined #sailfishos-porters22:56
*** spider-mario <spider-mario!~spidermar@178-83-188-253.dynamic.hispeed.ch> has quit IRC (Read error: Connection reset by peer)22:57
*** char-x <char-x!~char-x@p5B1742CC.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 246 seconds)23:02
*** cxl000 <cxl000!~cxl000@c27-253-5-120.brodm4.vic.optusnet.com.au> has quit IRC (Quit: Leaving)23:03
*** olafh_ <olafh_!~olafh@p4FF48416.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 248 seconds)23:35
*** phdeswer_ <phdeswer_!~phdeswer@91-159-55-220.elisa-laajakaista.fi> has quit IRC (Ping timeout: 244 seconds)23:35

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!