| 00:19.51 | *** join/#maemo infobot (ibot@rikers.org) |
| 00:19.51 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~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 |
| 00:59.30 | *** join/#maemo LouisA (~user@cable-10-151-99.b2b2c.ca) |
| 01:17.48 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 01:29.09 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 01:42.15 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 02:06.28 | Vajb | sicelo: cool. I bet then there'll be regular updates ;) |
| 02:46.44 | *** join/#maemo phlixi_ (~phlixi@ppp-188-174-128-139.dynamic.mnet-online.de) |
| 02:49.38 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 03:14.08 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 03:54.40 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 04:00.51 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 04:09.03 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:46.01 | *** join/#maemo stryngs (~stryngs@unaffiliated/stryngs) |
| 04:53.53 | *** join/#maemo eMHa_ (~mh@p200300738E39D200267703FFFE6CC360.dip0.t-ipconnect.de) |
| 04:55.35 | *** join/#maemo guerby (~guerby@ip165.tetaneutral.net) |
| 04:55.35 | *** join/#maemo guerby (~guerby@april/board/guerby) |
| 04:57.38 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 05:02.35 | sicelo | Vajb: unfortunately we will not get any further updates . . . irssi 1.x needs a newer glib than we have on Maemo |
| 05:08.36 | vahe | Hi all :) I'm looking for bitcoin wallet for n900 |
| 05:22.57 | sicelo | 19:25 < vahe> hi all :) I'm looking for bitcoin wallet for n900 |
| 05:22.57 | sicelo | 19:55 < DocScrutinizer05> https://talk.maemo.org/showthread.php?t=66756 |
| 05:23.13 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 05:26.58 | Vajb | sicelo: that wont be a problem since mainlining is done, right? |
| 05:27.19 | Vajb | tho i have a feeling that thing or two are yet to be done |
| 05:35.41 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:5d63:9abe:a0c9:e70c) |
| 05:39.32 | dreamer | huhm. since yesterday my n900 often doesn't see the sim. tried with some paper between sim and battery, but no luck. any tips? |
| 05:41.04 | dreamer | ok, bending the sim-pins a bit upwards. see how that goes .. |
| 05:43.41 | dreamer | so far so good .. |
| 05:43.47 | dreamer | eh. nope |
| 05:43.55 | dreamer | on boot it's there. 20 secs later it's gone |
| 05:44.07 | dreamer | oh now it's back .. highly unstable then .. |
| 05:47.28 | *** join/#maemo eMHa (~mh@p200300738E39D200267703FFFE6CC360.dip0.t-ipconnect.de) |
| 05:56.09 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 05:57.21 | dreamer | aaahnd it's gone |
| 05:58.23 | Vajb | happens to me too once in awhile |
| 05:59.30 | dreamer | I read some topic that mentions firmware being the issue. highly improbable |
| 05:59.39 | dreamer | this worked fine until last weekend |
| 06:00.42 | Vajb | probably gsm modem is coming loose from the board |
| 06:01.03 | Vajb | there was some spring fix for that, but didn't try it out |
| 06:01.13 | dreamer | hmz |
| 06:02.15 | Vajb | u could try "pnatd AT+CFUN=0" instead of rebooting whole device |
| 06:02.39 | Vajb | it restarts the modem chip or something like that |
| 06:02.56 | Vajb | also u can try to switch to offline and back |
| 06:03.18 | *** join/#maemo dafox (~dafox@188.207.97.248) |
| 06:05.13 | dreamer | atm it's just keeps switching off/on/off/on |
| 06:08.45 | *** join/#maemo Ras_Older (blank@hajotus.net) |
| 06:16.31 | ShadowJK | The sim icon is kinda misleading |
| 06:16.40 | ShadowJK | It's the whole modem blinking out of existence |
| 06:19.16 | *** join/#maemo florian (~fuchs@x4d094457.dyn.telefonica.de) |
| 06:20.11 | *** join/#maemo Kabouik (~kabouik@32.232.202.84.customer.cdi.no) |
| 06:21.14 | vahe | sicelo: thanks |
| 06:24.05 | KotCzarny | yeah, modem might be getting loose from th board |
| 06:24.39 | KotCzarny | check if it happens if you dont touch anything (especially kb) |
| 06:28.17 | ShadowJK | I've killed 3 or 4 N900 that way .. it always starts disconnecting when typing f and j or in between there |
| 06:31.05 | dreamer | hmz, this is my 3rd n900. 1st got fried usb port. 2nd got 'lost' (seriously no idea what happened there hehe) and this one I only had a month or 2 |
| 06:31.21 | dreamer | but. hmm. so do I find a rework station and try heating the modem part? |
| 06:31.32 | KotCzarny | maybe it was already faulty, and previous user 'fixed' it by baking? |
| 06:31.42 | dreamer | nah, previous user was a noob |
| 06:31.51 | dreamer | and it only started acting up since this weekend |
| 06:31.58 | KotCzarny | could be selling it because of that |
| 06:32.18 | dreamer | it's in otherwise pristine condition |
| 06:32.21 | KotCzarny | ie. problem could be happening from time to time and he decided to try to cash it while its possible |
| 06:33.48 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-66-234.residential.rdsnet.ro) |
| 06:34.28 | Vajb | for me it happens from time to time. I hope it is just area specific thing... |
| 06:35.24 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 06:37.16 | KotCzarny | it happened to me once or twice with worn sim card |
| 06:37.33 | KotCzarny | so there is a chance that sim card itself is dirty |
| 06:39.59 | *** join/#maemo dmth|intevation (~dmth|inte@2001:470:747a:2a:6af7:28ff:fe64:1ded) |
| 06:53.34 | dreamer | KotCzarny: wasn't a he. some middle-aged lady |
| 06:53.47 | KotCzarny | :) |
| 06:53.55 | dreamer | simcard is also new btw |
| 06:54.03 | dreamer | tried cleaning it. no avail |
| 06:54.09 | dreamer | so, rework station? |
| 07:05.13 | *** join/#maemo jskarvad (~jskarvad@ip4-83-240-109-95.cust.nbox.cz) |
| 07:05.13 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 07:06.31 | KotCzarny | if you are skilled enough |
| 07:19.48 | KotCzarny | btw. surest sign of modem fault is 'error communicating with the modem' yellow popup at the boot time |
| 07:22.57 | *** join/#maemo florian (~fuchs@p2E525AE4.dip0.t-ipconnect.de) |
| 07:28.11 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 07:34.03 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:41.15 | Wizzup | dreamer: there are some 'easy' fixes |
| 07:41.49 | Wizzup | as in, make sure it's not the sim connection, and check what dmesg says, and you can, put a small folded paper in between the phone and the battery (if you think the modem connection is the issue) |
| 07:50.18 | *** join/#maemo Kabouik (~kabouik@129.242.224.28) |
| 07:50.56 | *** join/#maemo Kabouik (~kabouik@129.242.224.28) |
| 08:03.32 | *** join/#maemo ruskie (~ruskie@sourcemage/mage/ruskie) |
| 08:10.10 | buZz | vahe: fyi, native bitcoin core supports arm nowadays, no need for untrusted binaries ;) |
| 08:10.24 | buZz | vahe: but without spv , i wouldnt really run it on n900 |
| 08:10.34 | buZz | there is https://github.com/bitcoin/bitcoin/pull/9483 though |
| 08:12.01 | vahe | buZz: Yes, I already understood , thanks :D |
| 08:12.08 | buZz | :) yw |
| 08:12.11 | vahe | :) |
| 08:13.10 | vahe | buZz: I was just looking for a wallet for your phone |
| 08:13.30 | vahe | but didn't think it was so hard for this phone |
| 08:13.51 | buZz | well its older than bitcoin :P |
| 08:14.06 | buZz | took a while for ppl to realize what bitcoin was etc |
| 08:14.45 | vahe | yup :) |
| 08:16.11 | buZz | there is https://multibit.org/ which is just java |
| 08:16.23 | buZz | it could work, although you might struggle with interface a bit |
| 08:18.56 | vahe | I'm on my computer use electrum |
| 08:19.09 | dreamer | Wizzup: already did the folder paper thing. also bended the pins a bit up. pretty sure it's not the connection to the sim |
| 08:19.32 | vahe | buZz: https://electrum.org/ |
| 08:20.27 | buZz | vahe: i think someone did make a maemo port of that at some time |
| 08:20.37 | buZz | but doubt it kept up with recent changes |
| 08:23.10 | Wizzup | dreamer: the paper helps not just with the sim connection |
| 08:32.16 | vahe | buZz: https://bpaste.net/show/12eadef92c96 |
| 08:32.32 | vahe | :D |
| 08:41.00 | buZz | well yes :P |
| 09:00.58 | dreamer | Wizzup: well, it didn't help at all :) |
| 09:04.28 | Wizzup | dreamer: aw |
| 09:15.07 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 09:47.23 | *** join/#maemo XDS2010 (sid1218@gateway/web/irccloud.com/x-zligtjkmovwvwpxh) |
| 10:05.42 | *** join/#maemo LouisA (~user@cable-10-151-99.b2b2c.ca) |
| 10:23.55 | *** join/#maemo N-Mi (~nicolas@office.ibrowse.com) |
| 10:23.55 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 10:29.05 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 10:30.54 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 10:35.10 | DocScrutinizer05 | ~tell dreamer about springfix |
| 10:36.11 | DocScrutinizer05 | "paper between sim and battery" doesn't help anything |
| 10:36.40 | DocScrutinizer05 | "bending the sim-pins a bit upwards" is risky and doesn't help either |
| 10:36.44 | sicelo | Vajb: irssi needs your testing and voting :) - http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/irssi/0.8.21-1/ |
| 10:41.00 | DocScrutinizer05 | when the SIM symbol is initially there but vanishes after ~20s just to return later on, it's highly likely the problem is faintly related to TX, so the modem detects problems as soon as trying to register to a cell it found. Similar effect known to happen on mountain summits when phones have clear and good reception but the station is too far away to allow login. |
| 10:41.54 | DocScrutinizer05 | another possible issue is very old battery which causes brownouts during TX bursts, ruining the TX signal to a degree where all connections fail |
| 10:42.22 | DocScrutinizer05 | but that's a condition the modem should detect and report separately |
| 10:47.59 | DocScrutinizer05 | the only real effect of paper cushion for SIM is: it supports the PCB slightly, so the PCB can bend less when pressing keys on kbd |
| 10:48.43 | DocScrutinizer05 | dreamer: ^^^ |
| 10:50.31 | DocScrutinizer05 | rework station is a good approach, when the operator is experienced |
| 10:51.04 | DocScrutinizer05 | ~usbfix |
| 10:51.04 | infobot | it has been said that usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or https://www.youtube.com/watch?v=fYz5nIHH0iY#t=1866, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt |
| 10:51.10 | DocScrutinizer05 | while you're at it |
| 10:52.11 | Vajb | sicelo: i don't have account there. Failed o activation. I reported it here and forgot the whole thing. |
| 10:52.27 | Vajb | in acti... |
| 10:53.23 | DocScrutinizer05 | when you're "baking" the device, you must remove all heat sensitive items before: camera, domesheet (*carefully* peel off and store on a "wax" paper), plastic frame on uSD board |
| 10:53.26 | DocScrutinizer05 | ) |
| 10:54.35 | DocScrutinizer05 | better use a professional rework station and reflow the modem chipset only. You need to remove tha can prior to that |
| 10:55.26 | DocScrutinizer05 | but before you do that, clean the antenna contacts of GSM antenna |
| 10:56.10 | DocScrutinizer05 | and make sure you got a battery with low ESR aka impedance, colloquially "a new fresh battery" |
| 11:01.59 | dreamer | never had the usb issue |
| 11:02.07 | dreamer | but hmm. will see if I can use a rework station one of these days |
| 11:12.01 | DocScrutinizer05 | usbfix is baby easy as long as USB is not broken yet. Once it's broken you will be sorry you didn't reinforce it beforehand |
| 11:17.13 | DocScrutinizer05 | actually for USB fix you don't need anything but a screwdriver or knife to scratch away the green solderstop varnish, a decent 60W soldering iron and good quality brand 60/40 flux core solder |
| 11:20.21 | DocScrutinizer05 | if you can solder two wires together and are sufficiently skilled to erase a writing from paper with a razorblade/knife, you can do USB fix |
| 11:21.55 | DocScrutinizer05 | reflow fixing the "no SIM" modem defect is a whole different story |
| 11:24.41 | DocScrutinizer05 | also make sure it's not actually a problem of your network providers. E.g. in some parts of USA I could see how N900 slowly ceases working at all, simply due to discontinued support for any of the frequency bands it could use |
| 11:25.56 | DocScrutinizer05 | a "fails after 20s" could also mean "the device thinks there's a band/network suitable for logging in, but when trying to log in the carrier rejects the login" |
| 11:28.11 | DocScrutinizer05 | weird new extensions to the OverTheAir protocol might actually even cause lockups or freezes in the modem's firmware, so yes, it may also be a firmware issue, alas not fixable on N900 side, only by using a different SIM for a different provider, or the 'rogue' provider fixing their protocol extensions |
| 11:29.49 | DocScrutinizer05 | generally I strongly suggest installing syslogd and having a look into the logs |
| 11:31.07 | *** join/#maemo eMHa (~mh@p200300738E39D200267703FFFE6CC360.dip0.t-ipconnect.de) |
| 11:32.23 | DocScrutinizer05 | to rule out the "incompatible carrier" issues you could use any other Nokia phone using BB5 modem of roughly same age. They are a zillion |
| 11:33.48 | DocScrutinizer05 | https://en.wikipedia.org/wiki/List_of_Nokia_products ^F "BB5" |
| 11:44.23 | DocScrutinizer05 | ideally you check for similar modem firmware, but I don't know how to accomplish that |
| 11:45.05 | DocScrutinizer05 | going for release date in *#0000# might be the as close as it gets here |
| 11:55.59 | *** part/#maemo MoeIcenowy (~So@138.68.61.217) |
| 11:57.19 | dreamer | DocScrutinizer05: lol @ springs and glue .. |
| 11:58.32 | dreamer | but ehm. the cell connection just keeps goin on/off/on/off |
| 11:58.37 | dreamer | was so at home and now at work |
| 11:58.50 | dreamer | can't really discern any when/how/what would be the cause |
| 11:59.05 | KotCzarny | change provider? |
| 11:59.14 | KotCzarny | ie. test with different network? |
| 11:59.46 | KotCzarny | borrow from someone or just buy cheapest prepaid |
| 12:11.24 | dreamer | so, that would be if it's the towers dropping certain bands? |
| 12:11.36 | dreamer | there are only 2 kinds of towers in .nl |
| 12:11.43 | dreamer | those by kpn and those by t-mobile |
| 12:11.58 | dreamer | any prepaid will also use the kpn network (where I'm on). so it wouldn't matter |
| 12:23.52 | *** join/#maemo remarc (~MG@194.153.119.2) |
| 13:03.10 | *** join/#maemo remarc (~MG@194.153.119.2) |
| 13:10.25 | sicelo | modem on its way out. mine did the same thing for a few weeks, until eventually it completely stopped working (second N900. thankfully my daily is still fine) |
| 13:25.54 | *** join/#maemo spiiroin (~spiiroin@87-93-16-71.bb.dnainternet.fi) |
| 13:39.21 | *** join/#maemo N-Mi (~nicolas@office.ibrowse.com) |
| 13:39.21 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 13:56.55 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 14:06.26 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 14:22.53 | *** join/#maemo remarc (~MG@194.153.119.2) |
| 14:28.06 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 14:35.26 | DocScrutinizer05 | dreamer: most likely your modem can receive but fails to transmit |
| 14:36.16 | DocScrutinizer05 | since logging in to a network involves transmitting, the login will eventually fail |
| 14:36.50 | DocScrutinizer05 | the modem "resets" and retries |
| 14:41.11 | DocScrutinizer05 | possible reasons are (in no particular order): chip balls coming off the PCB; IMEI blacklisted at provider; antenna contacts dirty; SIM contacts dirty; battery weak/worn; huge distance to base station; firmware issues, possibly caused by new protocol details on carrier |
| 14:41.47 | *** join/#maemo LauRoman (~LauRoman@5-14-66-234.residential.rdsnet.ro) |
| 14:43.38 | *** join/#maemo phlixi (~phlixi@ppp-188-174-128-139.dynamic.mnet-online.de) |
| 14:45.24 | dreamer | DocScrutinizer05: well. it's mostly just off (simcard with red stripe). then sometimes it can connect again |
| 14:45.54 | DocScrutinizer05 | no, it only thinks it can connect? |
| 14:46.49 | *** join/#maemo `0660 (olli@37.16.104.148) |
| 14:46.54 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 14:47.12 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 14:47.48 | *** join/#maemo FredrIQ (~fiq@81-230-224-64-no270.tbcn.telia.com) |
| 14:48.04 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 14:48.16 | DocScrutinizer05 | anyway, the problem is known, probably usually related to chip solder joints snapping open, and there's no surefire fix for it |
| 14:49.14 | DocScrutinizer05 | the initial cause is too high force pushing down keys on hw keyboard |
| 14:51.21 | *** join/#maemo sunshavi (~user@190.234.106.64) |
| 14:52.10 | *** join/#maemo hadara (hadara@bsd.ee) |
| 14:53.01 | DocScrutinizer05 | could also happen from pushing/squeezing the complete device while in pocket for example |
| 14:56.09 | *** join/#maemo FIQ (~FIQ@prgmr/customer/fiq) |
| 14:57.48 | *** join/#maemo aloril_ (~aloril@dsl-tkubng11-54f948-150.dhcp.inet.fi) |
| 14:58.06 | *** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 15:01.04 | *** join/#maemo N-Mi (~nicolas@93.158.33.174) |
| 15:01.04 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 15:07.59 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 15:08.39 | dreamer | DocScrutinizer05: no it actually connects. I can use the cell functions when it is connected |
| 15:08.53 | DocScrutinizer05 | hmm ok |
| 15:09.08 | dreamer | so, my guess is reflowing modem |
| 15:09.20 | DocScrutinizer05 | still that doesn't help tracking down the issue much |
| 15:09.21 | dreamer | but .. no idea when I'll have access to a reflow gun |
| 15:10.07 | DocScrutinizer05 | check your syslog! |
| 15:10.21 | DocScrutinizer05 | though odds are it's the usual issue |
| 15:10.38 | dreamer | McSAAB? |
| 15:10.50 | DocScrutinizer05 | hm? |
| 15:11.06 | dreamer | I see bunch of messages by McSAAB in dmesg |
| 15:11.26 | DocScrutinizer05 | this is the interface to modem |
| 15:11.41 | dreamer | 'CMT reset line change detected' and then bunch of stuff |
| 15:13.46 | DocScrutinizer05 | yes, that means the modem received a reset |
| 15:14.02 | DocScrutinizer05 | or rather, sent one |
| 15:14.17 | DocScrutinizer05 | iow it rebooted |
| 15:14.37 | dreamer | so that indicates the modem doesn't connect to the pcb properly? |
| 15:14.42 | dreamer | or can it reboot to other reasons? |
| 15:14.57 | DocScrutinizer05 | of course it can reboot for a lot of reasons |
| 15:15.12 | DocScrutinizer05 | none of them expected though |
| 15:17.12 | DocScrutinizer05 | for reference: http://paste.ubuntu.com/24499019 |
| 15:19.15 | DocScrutinizer05 | IroN900:~# wc -l /var/log/syslog |
| 15:19.16 | DocScrutinizer05 | 137722 /var/log/syslog |
| 15:20.11 | dreamer | really needs to fix ssh into the n900 |
| 15:20.18 | dreamer | for this kind of stuff hehe |
| 15:20.48 | dreamer | usually after a restart it can connect to the cell btw. can see my provider name and 3G reception etc. |
| 15:47.06 | *** join/#maemo dafox (~dafox@188.207.96.207) |
| 16:11.13 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 16:26.03 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 16:36.46 | *** join/#maemo hurrian_ (~textual@122.53.252.242) |
| 16:40.48 | *** join/#maemo florian (~fuchs@x4d094457.dyn.telefonica.de) |
| 16:40.57 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 16:41.49 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 16:43.25 | Enrico_Menotti | Hello. I investigated a bit about gpio keys in Devuan on the n900. After loading the kernel module gpio-keys, a new node appears on /dev/input/event3. I tried with evtest event3 and got the following: |
| 16:43.29 | Enrico_Menotti | root@devuan:/dev/input# evtest event3 |
| 16:43.29 | Enrico_Menotti | Input driver version is 1.0.1 |
| 16:43.30 | Enrico_Menotti | Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 |
| 16:43.30 | Enrico_Menotti | Input device name: "gpio_keys" |
| 16:43.30 | Enrico_Menotti | Supported events: |
| 16:43.31 | Enrico_Menotti | <PROTECTED> |
| 16:43.32 | Enrico_Menotti | <PROTECTED> |
| 16:43.33 | Enrico_Menotti | <PROTECTED> |
| 16:43.34 | Enrico_Menotti | <PROTECTED> |
| 16:43.35 | Enrico_Menotti | <PROTECTED> |
| 16:43.36 | Enrico_Menotti | <PROTECTED> |
| 16:43.37 | Enrico_Menotti | <PROTECTED> |
| 16:43.38 | Enrico_Menotti | <PROTECTED> |
| 16:43.39 | Enrico_Menotti | <PROTECTED> |
| 16:43.40 | Enrico_Menotti | Properties: |
| 16:43.41 | Enrico_Menotti | Testing ... (interrupt to exit) |
| 16:44.26 | KotCzarny | slide it baby, slid |
| 16:44.32 | Enrico_Menotti | The side slide switch reacts as KEY_SCREENLOCK. Let's forget for now the (?) event (quite strange). |
| 16:45.04 | KotCzarny | and proximity is the photoresistor near the screen |
| 16:45.25 | Enrico_Menotti | Ok. |
| 16:46.19 | Enrico_Menotti | Now these gpio keys produce strange symbols on console. I'd expect something listening to them and reporting events to the console. But how to find what it is and make it behave properly? |
| 16:47.45 | KotCzarny | you get what you have there |
| 16:48.06 | KotCzarny | ie. check input.h for key aliases and friends |
| 16:48.10 | KotCzarny | KEY_CAMERA KEY_SCREENLOCK etc |
| 16:49.01 | Enrico_Menotti | Input.h in the kernel module? |
| 16:49.36 | KotCzarny | in kernel tree |
| 16:49.49 | Enrico_Menotti | Ok. I'll look for it. |
| 16:49.54 | KotCzarny | SW_* ones might be in some n900 specific one though |
| 16:50.17 | Enrico_Menotti | Ok. |
| 16:50.51 | KotCzarny | those are the keys generated, think of it as a keyboard with multimedia keys |
| 16:54.29 | *** join/#maemo xy2_ (~xy2_@212-73-229-253.natip.skydsl.fr) |
| 17:13.16 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 17:14.04 | DocScrutinizer05 | Enrico_Menotti: didn't I point you to a website a few days ago? http://compsoc.man.ac.uk/~shep/pedals.html |
| 17:14.09 | DocScrutinizer05 | also see |
| 17:14.20 | DocScrutinizer05 | ~vi-keymap |
| 17:14.27 | DocScrutinizer05 | dang what been it |
| 17:14.50 | DocScrutinizer05 | ~listvalues vi*awesome |
| 17:15.01 | DocScrutinizer05 | ~awesome-keymap |
| 17:15.01 | infobot | i heard awesome-keymap is http://wiki.maemo.org/Remapping_keyboard/user_vis_awesome_kbdmapping |
| 17:15.34 | Enrico_Menotti | DocScrutinizer05 To be honest I don't remember that first website. Yes, I know the awesome kbdmapping - I will look at that again. Ty. |
| 17:16.16 | Enrico_Menotti | Meanwhile I found where the gpio key definitions are (at least, some trace of them): https://lkml.org/lkml/2013/10/22/509. |
| 17:17.32 | DocScrutinizer05 | IIRC you first need to determine the scancodes, then assign keysyms to them, and finally make your apps react on the keysyms |
| 17:18.05 | DocScrutinizer05 | wait |
| 17:18.39 | DocScrutinizer05 | IIRC you first need to determine the scancodes, then assign keycodes to scancodes, then assign keysyms to keycodes, and finally make your apps react on the keysyms ??? |
| 17:19.32 | Enrico_Menotti | Now I see the first link refers to udev, which I don't have. |
| 17:19.47 | DocScrutinizer05 | input in linux is a MESS |
| 17:19.53 | Enrico_Menotti | :) |
| 17:20.12 | APic | ð |
| 17:20.19 | Enrico_Menotti | :D |
| 17:20.24 | DocScrutinizer05 | udev only executes other commandline tools basically |
| 17:20.33 | Enrico_Menotti | Ah. |
| 17:21.25 | DocScrutinizer05 | afaik the only thing udev does on its own is creating generic 'files' with permissions and maybe also mount or symlink sth there |
| 17:21.28 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 17:21.32 | APic | ð |
| 17:22.45 | DocScrutinizer05 | also it can change owner/permission of files |
| 17:23.18 | DocScrutinizer05 | but for stuff like keymapping it for sure resorts to other commandline tools, I'd think |
| 17:25.41 | DocScrutinizer05 | oh fsck! actually udev handles scancode mapping internally |
| 17:27.00 | DocScrutinizer05 | <PROTECTED> |
| 17:29.49 | DocScrutinizer05 | at least your "evtest event3" results suggest that |
| 17:32.46 | DocScrutinizer05 | so for lockswitch I'd assume you get a "Event type 1 (EV_KEY) - Event code 152 (KEY_SCREENLOCK)" event on dev/input3 |
| 17:33.24 | KotCzarny | in short, gpio input layer says 'there is scancode 152' and kernel says 'ok got KEY_SCREENLOCK' |
| 17:33.55 | KotCzarny | so your apps should react on KEY_* and SW_* keys |
| 17:35.19 | DocScrutinizer05 | xev would see something similar to http://paste.ubuntu.com/24499762 |
| 17:37.52 | DocScrutinizer05 | compare to http://paste.ubuntu.com/24499769 which is my spacebar key and mapped to char " " |
| 17:40.26 | DocScrutinizer05 | I guess "KeyPress event" is equivalent to "Event type 1 (EV_KEY)" |
| 17:40.57 | Enrico_Menotti | I admit I am a bit confused. DocScrutinizer05 , how did you get exactly those pastes? And if I understand, they are related to the X environment, right? Now I'm on console - where is the mapping from KEY_SCREENLOCK to any action? |
| 17:41.21 | DocScrutinizer05 | there is none for console |
| 17:42.10 | KotCzarny | Enrico_Menotti: you can remap those keys with mainline kernel |
| 17:42.11 | DocScrutinizer05 | except in the shell and mintty or whatever you're running |
| 17:43.31 | Enrico_Menotti | I'll add what I get from evtest event3 if I move the slide switch: |
| 17:43.32 | Enrico_Menotti | Event: time 1493745937.054557, type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 1 |
| 17:43.33 | Enrico_Menotti | Event: time 1493745937.054557, -------------- EV_SYN ------------ |
| 17:43.33 | Enrico_Menotti | Event: time 1493745937.228474, type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 0 |
| 17:43.33 | Enrico_Menotti | Event: time 1493745937.228474, -------------- EV_SYN ------------ |
| 17:44.24 | DocScrutinizer05 | when I'm on console, pressing that keycode 172 (keysym 0x1008ff14, XF86AudioPlay) on my PC's keyboard doesn't do shit |
| 17:44.56 | Enrico_Menotti | 172? |
| 17:45.25 | DocScrutinizer05 | yes, that's the jeycode for that multimedia "Play" button |
| 17:45.35 | Enrico_Menotti | Ok. |
| 17:46.10 | DocScrutinizer05 | lockswitch on N900 with GPIOswitch obviously delivers code 152 (KEY_SCREENLOCK) |
| 17:47.07 | DocScrutinizer05 | plus a EV_SYN event whatever that is |
| 17:47.31 | Enrico_Menotti | Ok, so this code appears somewhat at /dev/input/event3. Now how is that converted to a signal to the console? |
| 17:47.45 | DocScrutinizer05 | signal? |
| 17:48.29 | DocScrutinizer05 | what kind of "signal" do you hope for? |
| 17:49.02 | Enrico_Menotti | I used that ambigous term on purpose, since I don't know actually how to define some event as perceived by the console. |
| 17:49.04 | DocScrutinizer05 | tbh the console shouldn't even read from /dev/input3 at all |
| 17:49.18 | Enrico_Menotti | Yes, in fact. This is what is strange to me. |
| 17:49.55 | DocScrutinizer05 | and when it does, it shouldn't receive a char mapped to those events |
| 17:50.02 | DocScrutinizer05 | so nothing for the console to do |
| 17:50.05 | Enrico_Menotti | Yes. |
| 17:50.33 | DocScrutinizer05 | od -foobarparam /dev/input3 |
| 17:50.41 | Enrico_Menotti | With the same kernel, and booting Debian, the slide switch works properly (on console): it wakes up the screen. |
| 17:51.04 | DocScrutinizer05 | that's not done "on console" |
| 17:51.13 | Enrico_Menotti | Yes, I understand. |
| 17:51.43 | Enrico_Menotti | But console doesn't output strange symbols. (On Debian.) (At least, I did not recognise any.) |
| 17:51.50 | Enrico_Menotti | Let me check. |
| 17:51.50 | DocScrutinizer05 | some other process is listening to /dev/onput3 and acts accordingly when seeing "type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 1" |
| 17:52.55 | DocScrutinizer05 | "act accordingly" means: blank/unblamk the screen |
| 17:53.32 | Enrico_Menotti | I'm booting Debian. I want to understand what happens there. |
| 17:53.35 | DocScrutinizer05 | unrelated to whether that's a console or a hildon-chess or whatever showing on display |
| 17:53.58 | DocScrutinizer05 | lsof|grep /dev/input3 |
| 17:54.18 | DocScrutinizer05 | if there's even such thing like /dev/input3 |
| 17:54.30 | Enrico_Menotti | Ok. A moment. |
| 17:54.47 | DocScrutinizer05 | could even be kernel itself handling that |
| 17:55.21 | DocScrutinizer05 | to start with, check if there's /dev/input3 and lsmod|grep gpio |
| 17:56.16 | DocScrutinizer05 | maemo handles that stuff completely different, via /sys/* |
| 17:56.29 | DocScrutinizer05 | and kevents iirc |
| 17:56.48 | DocScrutinizer05 | check kerecv |
| 17:59.35 | DocScrutinizer05 | hmm nope, maemo's ke-recv handles a lot but not lockswitch http://paste.ubuntu.com/24499859 |
| 18:00.16 | Enrico_Menotti | Ok, I was completely wrong. Sorry. Also with Debian I get the same strange symbol on console. :/ |
| 18:06.03 | DocScrutinizer05 | yes, I also get ^@ on console for keys that are not known to the console |
| 18:06.18 | DocScrutinizer05 | on my PC |
| 18:07.15 | DocScrutinizer05 | however there are other keys I don't get anything at all |
| 18:10.36 | DocScrutinizer05 | only in evtest though. without evtest running I don't get anything at all for most "special" keys", incl the vol- key that delivers ^[[25~ and the Play key that delivers ^@ in evtest |
| 18:12.56 | Vajb | dreamer: just a thought, but have u tried to change phone modes from settings? I mean dual-3g-gsm. |
| 18:12.57 | DocScrutinizer05 | anyway who cares about special keys in console of N900? ;-P |
| 18:13.54 | DocScrutinizer05 | after all console isn't what you want to run on N900 in the end |
| 18:14.27 | Enrico_Menotti | DocScrutinizer05 Yes, ok. I was thinking there was something wrong, that's why I started investigating these gpio keys. Now I know the module which handles them, and also where they show up (/dev/input/...). |
| 18:15.15 | Enrico_Menotti | I'm just curious to understand where these events get mapped to keycodes. |
| 18:43.42 | *** join/#maemo florian (~fuchs@x4d094457.dyn.telefonica.de) |
| 18:50.09 | dreamer | Vajb: either gsm or 3g it still loses connection |
| 18:52.55 | dreamer | I think I'll have to go try and destroy a pen to put the spring in there |
| 18:53.01 | dreamer | or 'bits of spring' |
| 18:53.08 | dreamer | and see if that keeps the modem connected .. |
| 18:56.14 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 19:09.41 | *** join/#maemo frals (~frals@Maemo/community/contributor/frals) |
| 19:15.04 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 19:52.24 | dreamer | meh |
| 19:53.10 | dreamer | Wizzup: you don't happen to want to trade an n900 do you? ;) (if you don't need stable modem) |
| 20:07.20 | *** join/#maemo RedW (~redw@89-74-182-178.dynamic.chello.pl) |
| 20:12.19 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 20:51.32 | *** join/#maemo Cor-Ai (~cor-ai@c-57d071d5.06-922-7570702.cust.bredbandsbolaget.se) |
| 21:16.45 | parazyd | dreamer: i'll give you one of mine if you wish |
| 21:16.52 | parazyd | (trade) |
| 21:17.07 | dreamer | parazyd: if the sim and usb work :P |
| 21:17.17 | parazyd | does your usb work? |
| 21:17.19 | dreamer | yes |
| 21:17.31 | parazyd | then i'd trade |
| 21:17.43 | parazyd | will query |
| 21:17.59 | dreamer | cool |
| 21:36.43 | merlin1991 | sicelo: yay |
| 21:38.40 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 21:51.31 | *** join/#maemo pagurus (~user@p508376A9.dip0.t-ipconnect.de) |
| 22:08.45 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-kgdzmnyfdnxdropc) |
| 22:14.52 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-iftopuxhnpprjwhi) |
| 22:16.14 | *** join/#maemo geaaru (~geaaru@host210-170-dynamic.248-95-r.retail.telecomitalia.it) |
| 22:48.10 | *** join/#maemo N-Mi (~nicolas@37.168.213.213) |
| 22:48.10 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 23:39.44 | *** join/#maemo sunshavi (~user@190.234.106.64) |