| 00:01.04 | *** join/#maemo chfoo[m] (chfoomatri@gateway/shell/matrix.org/x-dmdnktcqrnupvxtw) |
| 00:01.05 | *** join/#maemo vahe[m] (vahetermin@gateway/shell/matrix.org/x-kvfqeikejgezxrsw) |
| 00:01.05 | *** join/#maemo MartijnBraam (martijnbra@gateway/shell/matrix.org/x-iianjdpeubslrnqe) |
| 01:16.47 | *** join/#maemo pagurus (~user@i59F7CB94.versanet.de) |
| 02:04.40 | *** join/#maemo Kilroo (~Kilroo@cpe-71-71-97-50.triad.res.rr.com) |
| 02:10.55 | *** join/#maemo FalconSpy (falconspy@unaffiliated/falconspy) |
| 03:23.09 | *** join/#maemo auenfx8 (~David@CPE-143-238-101-125.nsw.bigpond.net.au) |
| 03:23.43 | *** join/#maemo auenf (~David@CPE-143-238-101-125.nsw.bigpond.net.au) |
| 04:00.00 | *** join/#maemo Oksana (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 05:08.32 | *** join/#maemo sunshavi (~user@190.234.106.68) |
| 05:31.22 | DocScrutinizer05 | WOW! |
| 05:31.26 | DocScrutinizer05 | ~+uptime |
| 05:35.24 | *** join/#maemo infobot (~infobot@rikers.org) |
| 05:35.24 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 05:37.13 | DocScrutinizer05 | FS |
| 05:37.17 | DocScrutinizer05 | CK |
| 05:37.39 | DocScrutinizer05 | ~+uptime |
| 05:41.23 | *** join/#maemo infobot (~infobot@rikers.org) |
| 05:41.23 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 05:48.49 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 06:16.51 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 06:18.49 | Maxdamantus | wonders why pressing the headset button causes two apparent key presses. |
| 06:21.08 | Maxdamantus | Pressing and releasing causes normal input events with `.code == 148` (and `.value == 0` or `.value == 1` depending on whether it's pressed or released) |
| 06:22.27 | Maxdamantus | but after it's been released for around a second, it has another two events with `.code == 169, .value == 1` and `.code == 169, .value == 0` |
| 06:23.33 | Maxdamantus | In Xorg, the first .code ends up as having symbol XF86Launch1, while the second one has symbol XF86Phone. |
| 06:37.43 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:8193:486a:855f:eab3) |
| 07:07.59 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 07:24.18 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 07:44.40 | bencoh | ion and hilarity will |
| 07:44.40 | bencoh | <PROTECTED> |
| 07:44.53 | KotCzarny | ion? |
| 07:45.48 | bencoh | just a copypaste fail, mybad. morning! :) |
| 07:45.56 | KotCzarny | hi :) |
| 08:07.10 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 08:08.57 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 08:22.41 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 08:38.16 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 08:38.59 | *** join/#maemo Kabouik_ (~kabouik@158.38.1.70) |
| 09:20.22 | *** join/#maemo pkill9 (~pkill9@unaffiliated/pkill9) |
| 09:33.59 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-gzffzdkmkpppknrx) |
| 09:33.59 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 09:44.00 | *** join/#maemo pkill9 (~pkill9@unaffiliated/pkill9) |
| 10:15.30 | *** join/#maemo Vajb (~Vajb@85-76-47-167-nat.elisa-mobile.fi) |
| 10:26.19 | *** join/#maemo N-Mi (~nicolas@office.ibrowse.com) |
| 10:26.19 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 10:38.19 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 10:56.36 | sixwheeledbeast | I imagine there will be some reason for that headset button functionality. You know what Maemo is like... |
| 10:57.06 | KotCzarny | maybe it sends button_down AND button_up ? |
| 10:57.25 | KotCzarny | would be logical for long press detection |
| 10:57.34 | sixwheeledbeast | I read it as the second function only happens if pressed again within a second |
| 10:57.47 | KotCzarny | and that too |
| 10:59.34 | sixwheeledbeast | Which I could imagine would be used by something. Why it's done in that way I wouldn't know. |
| 11:00.08 | KotCzarny | cost and usability |
| 11:02.14 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 11:09.26 | Maxdamantus | It happens only if not pressed again within a second. |
| 11:10.02 | Maxdamantus | So if you keep pressing the button, the second key press (XF86Phone) will not occur |
| 11:10.22 | Maxdamantus | It will only occur a second or so after it hasn't been pressed/released. |
| 11:10.39 | Maxdamantus | Can't remember if it happens while it's pressed .. /me checks |
| 11:11.30 | Maxdamantus | Right, it doesn't. |
| 11:11.46 | Maxdamantus | Only happens when the physical button has been in the released state for a second or so. |
| 11:16.30 | sixwheeledbeast | Some way of controlling answering a phone call separately from the other functions the button does. |
| 11:18.52 | Maxdamantus | Yeah, I guess so. Just seems weird that it would be implemented at that level. |
| 11:19.18 | Maxdamantus | Dunno if it's the hardware itself, or the input driver in the kernel that generates the second key. |
| 11:19.56 | Maxdamantus | Hmm .. I suspect the reason will be so that one program can bind to one key and another can bind to the other one. |
| 11:21.46 | Maxdamantus | Since afaik, only one X11 connection can bind a particular key (XGrabKey) at a time. |
| 11:22.25 | Maxdamantus | and you'd have to use something like XRecord to otherwise have multiple connections receiving the same key events. |
| 11:22.56 | Maxdamantus | or be a parent window to the one that would normally be receiving them. |
| 11:27.33 | sixwheeledbeast | phone application is is closed so it maybe difficult to find out. |
| 11:32.02 | *** join/#maemo eMHa (~mh@2a02:788:113:142:d6be:d9ff:fe2b:f21b) |
| 11:32.11 | Maxdamantus | Well, it's probably not effectively going to have a difference unless something actually wants to grab the XFLaunch1 key. |
| 11:32.33 | Maxdamantus | er, XF86Launch1* |
| 11:32.52 | Maxdamantus | the phone UI seems to use XF86Phone, since it doesn't pick up if I keep pressing the button. |
| 11:48.40 | Maxdamantus | Hmm .. wonder if the actual headset does something other than just short ground/mic while the button is pressed. |
| 11:49.09 | Maxdamantus | I think it does, since the software behaves strangely when the headset is inserted while the button is pressed .. sort of. |
| 11:49.59 | Maxdamantus | You would expect it to just be recognised as a normal pair of headphones, which seems to be what happens, but it doesn't show any headphone icon in the bar thing. |
| 11:50.17 | Maxdamantus | It does still go to headphone mode, and doesn't produce the input device for the button. |
| 11:52.02 | Maxdamantus | Might be nice to add a button next time I made a cable for my earphones. |
| 12:15.34 | sixwheeledbeast | cat /sys/devices/platform/gpio-switch/headphone/state you can see there is an output depending on what is connected/detected. AV-out/headset/headphone etc |
| 12:19.14 | sixwheeledbeast | actually there's a few places. probably thinking of /platform/nokia-av/detect |
| 12:21.50 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 12:31.38 | *** join/#maemo l_bratch (~l_bratch@serenity.bratch.co.uk) |
| 14:06.07 | *** join/#maemo spiiroin (~spiiroin@87-95-210-219.bb.dnainternet.fi) |
| 14:15.54 | *** join/#maemo xorly (~xorly@wced-152-219-32-147.feld.cvut.cz) |
| 14:56.35 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 15:01.36 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 15:32.46 | DocScrutinizer05 | ~+uptime |
| 15:51.45 | DocScrutinizer05 | ~+uptime |
| 15:56.28 | DocScrutinizer05 | Sigyn: <3 |
| 16:32.19 | *** join/#maemo xorly (~xorly@wced-217-219-32-147.feld.cvut.cz) |
| 16:32.58 | *** join/#maemo Kabouik (~kabouik@158.38.1.70) |
| 16:37.00 | *** join/#maemo hurrian_ (~textual@112.210.151.206) |
| 16:43.45 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 17:01.47 | *** join/#maemo pagurus` (~user@i5387EB95.versanet.de) |
| 17:36.16 | *** join/#maemo Kabouik_ (~kabouik@158.38.1.70) |
| 17:47.37 | *** join/#maemo xorly (~xorly@wced-217-219-32-147.feld.cvut.cz) |
| 17:54.47 | *** join/#maemo sunshavi (~user@181.64.192.167) |
| 18:01.02 | *** join/#maemo xorly (~xorly@wced-217-219-32-147.feld.cvut.cz) |
| 18:52.35 | *** join/#maemo xorly (~xorly@wced-217-219-32-147.feld.cvut.cz) |
| 18:55.46 | *** join/#maemo eMHa (~mh@p200300738E0CE800267703FFFE6CC360.dip0.t-ipconnect.de) |
| 19:05.25 | Maxdamantus | Yeah, so I guess it's "nokia-av" that's confused. |
| 19:06.49 | Maxdamantus | the gpio driver correctly just reports "connected" and "disconnected", but nokia-av seems to print "3" in the "detect" node in sysfs when there's supposedly nothing plugged in. |
| 19:07.04 | Maxdamantus | It continues showing "3" if I plug the headset in while holding the button. |
| 19:07.40 | Maxdamantus | normally the headset appears as "4", and headphones appear as "1" |
| 19:40.05 | *** join/#maemo xorly (~xorly@wced-217-219-32-147.feld.cvut.cz) |
| 19:50.15 | *** join/#maemo shentey (~shentey@x4db4aef5.dyn.telefonica.de) |
| 20:01.54 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 20:02.00 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 20:18.27 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 21:51.17 | *** join/#maemo mike727 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 21:53.24 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 21:53.52 | mike727 | Is there any potential for 'Firefox quantum' to be viable on N900? http://talk.maemo.org/showpost.php?p=1537953&postcount=81 |
| 21:55.38 | joga | problem as I see it is that "modern web" means megabytes upon megabytes of javascript for even simple "should be static html" pages. N900 is simply outdated for such, but fortunately still is the best phone in the world for qwerty shell action |
| 22:07.47 | pkill9 | ergh so annoying why must the modern web not cater to lower powered devices, i.e. provide text-only option |
| 22:10.25 | pkill9 | this is what gopherspace is for :D |
| 22:23.12 | *** join/#maemo shentey (~shentey@x4db4aef5.dyn.telefonica.de) |
| 22:51.16 | *** join/#maemo N-Mi (~nicolas@37.170.169.29) |
| 22:51.16 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 22:59.42 | sixwheeledbeast | web designers don't care about performance only design. Gone are the days of divitis and flash, welcome to the age of the script |
| 23:00.32 | sixwheeledbeast | well a broad stereotypical few there but ... :P |
| 23:03.31 | Maxdamantus | still feels that browsers could generally do a better job at supporting lower-powered devices. |
| 23:04.26 | Maxdamantus | Haven't looked particularly closely at Servo though (which I suspect is the basis of Firefox Quantum) |
| 23:19.06 | *** join/#maemo jon_y (~enforcer@2001:e68:4074:479f:f64d:30ff:fe63:5a5a) |