IRC log of #maemo for Tuesday, 2017-05-02

*** LauRoman has joined #maemo00:00
*** LauRoman has quit IRC00:02
*** LauRoman has joined #maemo00:08
bencohDocScrutinizer05: ^@ is probably just some undisplayable character00:08
DocScrutinizer05sounds like 0x0000:12
DocScrutinizer05compare less `which date`00:17
DocScrutinizer05as such it's indeed "undisplayable" and gets represented in ^notation00:30
*** DocScrutinizer05 has quit IRC00:30
*** DocScrutinizer05 has joined #maemo00:31
DocScrutinizer05shouldn't try to type a ctrl+q to get a ctrl+@ ;-P00:32
*** geaaru has quit IRC00:45
*** cyteen has quit IRC01:11
*** xy2_ has quit IRC01:21
*** N-Mi has joined #maemo01:26
*** N-Mi has joined #maemo01:26
*** guerby has quit IRC01:32
*** Pali has quit IRC01:34
*** Venemo has quit IRC01:35
*** cyteen has joined #maemo01:48
*** LouisA has quit IRC02:10
*** florian has quit IRC02:14
*** cyteen has quit IRC03:12
*** infobot has quit IRC03:18
*** infobot has joined #maemo03:19
*** xorly has quit IRC03:49
*** LouisA has joined #maemo03:59
*** drcode has quit IRC04:15
*** drcode has joined #maemo04:17
*** LouisA has quit IRC04:20
*** drcode has quit IRC04:25
*** drcode has joined #maemo04:29
*** drcode has quit IRC04:31
*** eMHa_ has quit IRC04:34
*** drcode has joined #maemo04:42
Vajbsicelo: cool. I bet then there'll be regular updates ;)05:06
*** phlixi_ has joined #maemo05:46
*** phlixi has quit IRC05:48
*** DocScrutinizer05 has quit IRC05:49
*** DocScrutinizer05 has joined #maemo05:49
*** vahe has joined #maemo06:14
*** drcode has quit IRC06:39
*** drcode has joined #maemo06:54
*** drcode has quit IRC06:57
*** drcode has joined #maemo07:00
*** DocScrutinizer05 has quit IRC07:09
*** DocScrutinizer05 has joined #maemo07:09
*** spiiroin has quit IRC07:32
*** stryngs has quit IRC07:44
*** stryngs has joined #maemo07:46
*** cyphase has quit IRC07:52
*** eMHa_ has joined #maemo07:53
*** guerby has joined #maemo07:55
*** guerby has joined #maemo07:55
*** cyphase has joined #maemo07:57
siceloVajb: unfortunately we will not get any further updates . . . irssi 1.x needs a newer glib than we have on Maemo08:02
vaheHi all :) I'm looking for bitcoin wallet for n90008:08
*** sunshavi has quit IRC08:20
sicelo19:25 < vahe> hi all :) I'm looking for bitcoin wallet for n90008:22
sicelo19:55 < DocScrutinizer05>
*** jonwil has joined #maemo08:23
Vajbsicelo: that wont be a problem since mainlining is done, right?08:26
Vajbtho i have a feeling that thing or two are yet to be done08:27
*** spiiroin has joined #maemo08:35
dreamerhuhm. since yesterday my n900 often doesn't see the sim. tried with some paper between sim and battery, but no luck. any tips?08:39
dreamerok, bending the sim-pins a bit upwards. see how that goes ..08:41
dreamerso far so good ..08:43
dreamereh. nope08:43
dreameron boot it's there. 20 secs later it's gone08:43
dreameroh now it's back .. highly unstable then ..08:44
*** eMHa_ has quit IRC08:45
*** eMHa has joined #maemo08:47
*** xy2_ has joined #maemo08:56
dreameraaahnd it's gone08:57
Vajbhappens to me too once in awhile08:58
dreamerI read some topic that mentions firmware being the issue. highly improbable08:59
dreamerthis worked fine until last weekend08:59
Vajbprobably gsm modem is coming loose from the board09:00
Vajbthere was some spring fix for that, but didn't try it out09:01
Vajbu could try "pnatd AT+CFUN=0" instead of rebooting whole device09:02
Vajbit restarts the modem chip or something like that09:02
Vajbalso u can try to switch to offline and back09:02
*** dafox has joined #maemo09:03
dreameratm it's just keeps switching off/on/off/on09:05
*** N-Mi has quit IRC09:07
*** Ras_Older has joined #maemo09:08
ShadowJKThe sim icon is kinda misleading09:16
ShadowJKIt's the whole modem blinking out of existence09:16
*** florian has joined #maemo09:19
*** Kabouik has joined #maemo09:20
vahesicelo: thanks09:21
*** xy2_ has quit IRC09:22
KotCzarnyyeah, modem might be getting loose from th board09:24
KotCzarnycheck if it happens if you dont touch anything (especially kb)09:24
ShadowJKI've killed 3 or 4 N900 that way .. it always starts disconnecting when typing f and j or in between there09:28
*** florian has quit IRC09:28
*** dafox has quit IRC09:29
dreamerhmz, 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 209:31
dreamerbut. hmm. so do I find a rework station and try heating the modem part?09:31
KotCzarnymaybe it was already faulty, and previous user 'fixed' it by baking?09:31
dreamernah, previous user was a noob09:31
dreamerand it only started acting up since this weekend09:31
KotCzarnycould be selling it because of that09:31
dreamerit's in otherwise pristine condition09:32
KotCzarnyie. problem could be happening from time to time and he decided to try to cash it while its possible09:32
*** LauRoman|Alt has joined #maemo09:33
Vajbfor me it happens from time to time. I hope it is just area specific thing...09:34
*** cyteen has joined #maemo09:35
KotCzarnyit happened to me once or twice with worn sim card09:37
KotCzarnyso there is a chance that sim card itself is dirty09:37
*** Kabouik has quit IRC09:39
*** dmth|intevation has joined #maemo09:39
*** LauRoman|Alt has quit IRC09:43
*** drcode has quit IRC09:51
dreamerKotCzarny: wasn't a he. some middle-aged lady09:53
dreamersimcard is also new btw09:53
dreamertried cleaning it. no avail09:54
dreamerso, rework station?09:54
*** jskarvad has joined #maemo10:05
*** jskarvad has quit IRC10:05
*** jskarvad has joined #maemo10:05
KotCzarnyif you are skilled enough10:06
KotCzarnybtw. surest sign of modem fault is 'error communicating with the modem' yellow popup at the boot time10:19
*** florian has joined #maemo10:22
*** drcode has joined #maemo10:28
*** florian has quit IRC10:33
*** florian has joined #maemo10:34
Wizzupdreamer: there are some 'easy' fixes10:41
Wizzupas 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)10:41
*** Kabouik has joined #maemo10:50
*** Kabouik has joined #maemo10:50
*** ruskie has quit IRC11:01
*** ruskie has joined #maemo11:03
buZzvahe: fyi, native bitcoin core supports arm nowadays, no need for untrusted binaries ;)11:10
buZzvahe: but without spv , i wouldnt really run it on n90011:10
buZzthere is though11:10
vahebuZz: Yes, I already understood , thanks  :D11:12
buZz:) yw11:12
vahebuZz: I was just looking for a wallet for your phone11:13
vahebut didn't think it was so hard for this phone11:13
buZzwell its older than bitcoin :P11:13
buZztook a while for ppl to realize what bitcoin was etc11:14
vaheyup :)11:14
buZzthere is which is just java11:16
buZzit could work, although you might struggle with interface a bit11:16
vaheI'm on my computer use electrum11:18
dreamerWizzup: already did the folder paper thing. also bended the pins a bit up. pretty sure it's not the connection to the sim11:19
buZzvahe: i think someone did make a maemo port of that at some time11:20
buZzbut doubt it kept up with recent changes11:20
Wizzupdreamer: the paper helps not just with the sim connection11:23
buZzwell yes :P11:41
dreamerWizzup: well, it didn't help at all :)12:00
Wizzupdreamer: aw12:04
*** xorly has joined #maemo12:15
*** eMHa has quit IRC12:37
*** XDS2010 has quit IRC12:43
*** XDS2010 has joined #maemo12:47
*** LouisA has joined #maemo13:05
*** vahe has quit IRC13:20
*** N-Mi has joined #maemo13:23
*** N-Mi has joined #maemo13:23
*** frals has quit IRC13:25
*** silviof has joined #maemo13:29
*** vahe has joined #maemo13:30
DocScrutinizer05~tell dreamer about springfix13:35
DocScrutinizer05"paper between sim and battery" doesn't help anything13:36
DocScrutinizer05"bending the sim-pins a bit upwards" is risky and doesn't help either13:36
siceloVajb: irssi needs your testing and voting :)   -
DocScrutinizer05when 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.13:41
DocScrutinizer05another possible issue is very old battery which causes brownouts during TX bursts, ruining the TX signal to a degree where all connections fail13:41
DocScrutinizer05but that's a condition the modem should detect and report separately13:42
DocScrutinizer05the only real effect of paper cushion for SIM is: it supports the PCB slightly, so the PCB can bend less when pressing keys on kbd13:47
DocScrutinizer05dreamer: ^^^13:48
DocScrutinizer05rework station is a good approach, when the operator is experienced13:50
infobotit has been said that usbfix is - and **NEVER** use epoxy (unless you want to seal your device for underwater), or, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt13:51
DocScrutinizer05while you're at it13:51
Vajbsicelo: i don't have account there. Failed o activation. I reported it here and forgot the whole thing.13:52
Vajbin acti...13:52
DocScrutinizer05when 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 board13:53
DocScrutinizer05better use a professional rework station and reflow the modem chipset only. You need to remove tha can prior to that13:54
DocScrutinizer05but before you do that, clean the antenna contacts of GSM antenna13:55
DocScrutinizer05and make sure you got a battery with low ESR aka impedance, colloquially "a new fresh battery"13:56
* dreamer never had the usb issue14:01
dreamerbut hmm. will see if I can use a rework station one of these days14:02
DocScrutinizer05usbfix is baby easy as long as USB is not broken yet. Once it's broken you will be sorry you didn't reinforce it beforehand14:12
DocScrutinizer05actually 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 solder14:17
DocScrutinizer05if you can solder two wires together and are sufficiently skilled to erase a writing from paper with a razorblade/knife, you can do USB fix14:20
DocScrutinizer05reflow fixing the "no SIM" modem defect is a whole different story14:21
*** vahe has quit IRC14:22
DocScrutinizer05also 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 use14:24
DocScrutinizer05a "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"14:25
DocScrutinizer05weird 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 extensions14:28
DocScrutinizer05generally I strongly suggest installing syslogd and having a look into the logs14:29
*** eMHa has joined #maemo14:31
DocScrutinizer05to rule out the "incompatible carrier" issues you could use any other Nokia phone using BB5 modem of roughly same age. They are a zillion14:32
*** jskarvad has quit IRC14:32
*** LouisA has quit IRC14:33
DocScrutinizer05 ^F "BB5"14:33
DocScrutinizer05ideally you check for similar modem firmware, but I don't know how to accomplish that14:44
DocScrutinizer05going for release date in *#0000# might be the as close as it gets here14:45
*** MoeIcenowy has left #maemo14:56
dreamerDocScrutinizer05: lol @ springs and glue ..14:57
dreamerbut ehm. the cell connection just keeps goin on/off/on/off14:58
dreamerwas so at home and now at work14:58
dreamercan't really discern any when/how/what would be the cause14:58
KotCzarnychange provider?14:59
KotCzarnyie. test with different network?14:59
KotCzarnyborrow from someone or just buy cheapest prepaid14:59
dreamerso, that would be if it's the towers dropping certain bands?15:11
dreamerthere are only 2 kinds of towers in .nl15:11
dreamerthose by kpn and those by t-mobile15:11
dreamerany prepaid will also use the kpn network (where I'm on). so it wouldn't matter15:11
*** remarc has joined #maemo15:23
*** remarc has quit IRC16:00
*** remarc has joined #maemo16:03
sicelomodem 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)16:10
*** spiiroin has quit IRC16:10
*** N-Mi has quit IRC16:25
*** spiiroin has joined #maemo16:25
*** remarc has quit IRC16:36
*** N-Mi has joined #maemo16:39
*** N-Mi has joined #maemo16:39
*** silviof has quit IRC16:53
*** BCMM has joined #maemo16:56
*** silviof has joined #maemo17:06
*** florian has quit IRC17:14
*** remarc has joined #maemo17:22
*** jskarvad has joined #maemo17:28
DocScrutinizer05dreamer: most likely your modem can receive but fails to transmit17:35
DocScrutinizer05since logging in to a network involves transmitting, the login will eventually fail17:36
DocScrutinizer05the modem "resets" and retries17:36
*** jonwil has quit IRC17:42
DocScrutinizer05possible 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 carrier17:42
*** LauRoman has quit IRC17:42
*** LauRoman has joined #maemo17:42
*** povbot has joined #maemo17:47
*** FredrIQ has joined #maemo17:47
*** luke-jr has joined #maemo17:48
DocScrutinizer05anyway, the problem is known, probably usually related to chip solder joints snapping open, and there's no surefire fix for it17:48
*** N-Mi has quit IRC17:48
DocScrutinizer05the initial cause is too high force pushing down keys on hw keyboard17:49
*** sunshavi has joined #maemo17:51
*** hadara has joined #maemo17:52
DocScrutinizer05could also happen from pushing/squeezing the complete device while in pocket for example17:53
*** FIQ has joined #maemo17:56
*** FredrIQ has quit IRC17:56
*** aloril_ has joined #maemo17:57
*** AndrewX192 has joined #maemo17:58
*** dmth|intevation has quit IRC17:59
*** N-Mi has joined #maemo18:01
*** N-Mi has joined #maemo18:01
*** BCMM has quit IRC18:05
*** xy2_ has joined #maemo18:07
dreamerDocScrutinizer05: no it actually connects. I can use the cell functions when it is connected18:08
DocScrutinizer05hmm ok18:08
dreamerso, my guess is reflowing modem18:09
DocScrutinizer05still that doesn't help tracking down the issue much18:09
dreamerbut .. no idea when I'll have access to a reflow gun18:09
DocScrutinizer05check your syslog!18:10
DocScrutinizer05though odds are it's the usual issue18:10
dreamerI see bunch of messages by McSAAB in dmesg18:11
DocScrutinizer05this is the interface to modem18:11
dreamer'CMT reset line change detected' and then bunch of stuff18:11
DocScrutinizer05yes, that means the modem received a reset18:13
DocScrutinizer05or rather, sent one18:14
DocScrutinizer05iow it rebooted18:14
dreamerso that indicates the modem doesn't connect to the pcb properly?18:14
dreameror can it reboot to other reasons?18:14
DocScrutinizer05of course it can reboot for a lot of reasons18:14
DocScrutinizer05none of them expected though18:15
DocScrutinizer05for reference:
DocScrutinizer05IroN900:~# wc -l /var/log/syslog18:19
DocScrutinizer05137722 /var/log/syslog18:19
* dreamer really needs to fix ssh into the n90018:20
dreamerfor this kind of stuff hehe18:20
dreamerusually after a restart it can connect to the cell btw. can see my provider name and 3G reception etc.18:20
*** xy2_ has quit IRC18:34
*** dafox has joined #maemo18:47
*** Kabouik has quit IRC19:00
*** xy2_ has joined #maemo19:11
*** dafox has quit IRC19:21
*** Pali has joined #maemo19:26
*** xy2_ has quit IRC19:28
*** hurrian_ has joined #maemo19:36
*** hurrian has quit IRC19:38
*** florian has joined #maemo19:40
*** florian has joined #maemo19:40
*** BCMM has joined #maemo19:41
Enrico_MenottiHello. 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:19:43
Enrico_Menottiroot@devuan:/dev/input# evtest event319:43
Enrico_MenottiInput driver version is 1.0.119:43
Enrico_MenottiInput device ID: bus 0x19 vendor 0x1 product 0x1 version 0x10019:43
Enrico_MenottiInput device name: "gpio_keys"19:43
Enrico_MenottiSupported events:19:43
Enrico_Menotti  Event type 0 (EV_SYN)19:43
Enrico_Menotti  Event type 1 (EV_KEY)19:43
Enrico_Menotti    Event code 152 (KEY_SCREENLOCK)19:43
Enrico_Menotti    Event code 212 (KEY_CAMERA)19:43
Enrico_Menotti    Event code 528 (?)19:43
Enrico_Menotti  Event type 5 (EV_SW)19:43
Enrico_Menotti    Event code 9 (SW_CAMERA_LENS_COVER)19:43
Enrico_Menotti    Event code 10 (SW_KEYPAD_SLIDE)19:43
Enrico_Menotti    Event code 11 (SW_FRONT_PROXIMITY)19:43
Enrico_MenottiTesting ... (interrupt to exit)19:43
KotCzarnyslide it baby, slid19:44
Enrico_MenottiThe side slide switch reacts as KEY_SCREENLOCK. Let's forget for now the (?) event (quite strange).19:44
KotCzarnyand proximity is the photoresistor near the screen19:45
Enrico_MenottiNow 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?19:46
KotCzarnyyou get what you have there19:47
KotCzarnyie. check input.h for key aliases and friends19:48
Enrico_MenottiInput.h in the kernel module?19:49
KotCzarnyin kernel tree19:49
Enrico_MenottiOk. I'll look for it.19:49
KotCzarnySW_* ones might be in some n900 specific one though19:49
KotCzarnythose are the keys generated, think of it as a keyboard with multimedia keys19:50
*** xy2_ has joined #maemo19:54
*** xy2_ has quit IRC20:11
*** dafox has joined #maemo20:13
DocScrutinizer05Enrico_Menotti: didn't I point you to a website a few days ago?
DocScrutinizer05also see20:14
DocScrutinizer05dang what been it20:14
DocScrutinizer05~listvalues vi*awesome20:14
infobotFactoid search of 'vi*awesome' by value (3): vi-kbd ;; ironman ;; #maemo awesome-keymap.20:14
infoboti heard awesome-keymap is
Enrico_MenottiDocScrutinizer05 To be honest I don't remember that first website. Yes, I know the awesome kbdmapping - I will look at that again. Ty.20:15
Enrico_MenottiMeanwhile I found where the gpio key definitions are (at least, some trace of them):
DocScrutinizer05IIRC you first need to determine the scancodes, then assign keysyms to them, and finally make your apps react on the keysyms20:17
DocScrutinizer05IIRC 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 ???20:18
Enrico_MenottiNow I see the first link refers to udev, which I don't have.20:19
DocScrutinizer05input in linux is a MESS20:19
DocScrutinizer05udev only executes other commandline tools basically20:20
DocScrutinizer05afaik the only thing udev does on its own is creating generic 'files' with permissions and maybe also mount or symlink sth there20:21
*** vahe has joined #maemo20:21
DocScrutinizer05also it can change owner/permission of files20:22
DocScrutinizer05but for stuff like keymapping it for sure resorts to other commandline tools, I'd think20:23
DocScrutinizer05oh fsck! actually udev handles scancode mapping internally20:25
DocScrutinizer05 KEYBOARD_KEY_70004=f13  ((/etc/udev/hwdb.d/90-custom-keyboard.hwdb))  but AIUI this is already accomplished in your gpio driver which doesn't provide scancodes but actually keycodes20:27
DocScrutinizer05at least your "evtest event3" results suggest that20:29
DocScrutinizer05so for lockswitch I'd assume you get a "Event type 1 (EV_KEY) - Event code 152 (KEY_SCREENLOCK)" event on dev/input320:32
KotCzarnyin short, gpio input layer says 'there is scancode 152' and kernel says 'ok got KEY_SCREENLOCK'20:33
KotCzarnyso your apps should react on KEY_* and SW_* keys20:33
*** florian has quit IRC20:35
DocScrutinizer05xev would see something similar to
DocScrutinizer05compare to which is my spacebar key and mapped to char " "20:37
DocScrutinizer05I guess "KeyPress event" is equivalent to "Event type 1 (EV_KEY)"20:40
Enrico_MenottiI 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?20:40
DocScrutinizer05there is none for console20:41
KotCzarnyEnrico_Menotti: you can remap those keys with mainline kernel20:42
DocScrutinizer05except in the shell and mintty or whatever you're running20:42
Enrico_MenottiI'll add what I get from evtest event3 if I move the slide switch:20:43
Enrico_MenottiEvent: time 1493745937.054557, type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 120:43
Enrico_MenottiEvent: time 1493745937.054557, -------------- EV_SYN ------------20:43
Enrico_MenottiEvent: time 1493745937.228474, type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 020:43
Enrico_MenottiEvent: time 1493745937.228474, -------------- EV_SYN ------------20:43
DocScrutinizer05when I'm on console, pressing that keycode 172 (keysym 0x1008ff14, XF86AudioPlay) on my PC's keyboard doesn't do shit20:44
DocScrutinizer05yes, that's the jeycode for that multimedia "Play" button20:45
DocScrutinizer05lockswitch on N900 with GPIOswitch obviously delivers code 152 (KEY_SCREENLOCK)20:46
DocScrutinizer05plus a EV_SYN event whatever that is20:47
Enrico_MenottiOk, so this code appears somewhat at /dev/input/event3. Now how is that converted to a signal to the console?20:47
DocScrutinizer05what kind of "signal" do you hope for?20:48
Enrico_MenottiI used that ambigous term on purpose, since I don't know actually how to define some event as perceived by the console.20:49
DocScrutinizer05tbh the console shouldn't even read from /dev/input3 at all20:49
Enrico_MenottiYes, in fact. This is what is strange to me.20:49
DocScrutinizer05and when it does, it shouldn't receive a char mapped to those events20:49
DocScrutinizer05so nothing for the console to do20:50
DocScrutinizer05od -foobarparam /dev/input320:50
Enrico_MenottiWith the same kernel, and booting Debian, the slide switch works properly (on console): it wakes up the screen.20:50
DocScrutinizer05that's not done "on console"20:51
Enrico_MenottiYes, I understand.20:51
Enrico_MenottiBut console doesn't output strange symbols. (On Debian.) (At least, I did not recognise any.)20:51
Enrico_MenottiLet me check.20:51
DocScrutinizer05some other process is listening to /dev/onput3 and acts accordingly when seeing "type 1 (EV_KEY), code 152 (KEY_SCREENLOCK), value 1"20:51
DocScrutinizer05"act accordingly" means: blank/unblamk the screen20:52
Enrico_MenottiI'm booting Debian. I want to understand what happens there.20:53
DocScrutinizer05unrelated to whether that's a console or a hildon-chess or whatever showing on display20:53
DocScrutinizer05lsof|grep /dev/input320:53
DocScrutinizer05if there's even such thing like /dev/input320:54
Enrico_MenottiOk. A moment.20:54
DocScrutinizer05could even be kernel itself handling that20:54
DocScrutinizer05to start with, check if there's /dev/input3 and lsmod|grep gpio20:55
DocScrutinizer05maemo handles that stuff completely different, via /sys/*20:56
DocScrutinizer05and kevents iirc20:56
DocScrutinizer05check kerecv20:56
DocScrutinizer05hmm nope, maemo's ke-recv handles a lot but not lockswitch
*** vahe has quit IRC21:00
Enrico_MenottiOk, I was completely wrong. Sorry. Also with Debian I get the same strange symbol on console. :/21:00
DocScrutinizer05yes, I also get ^@ on console for keys that are not known to the console21:06
DocScrutinizer05on my PC21:06
DocScrutinizer05however there are other keys I don't get anything at all21:07
*** BCMM has quit IRC21:08
DocScrutinizer05only 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 evtest21:10
Vajbdreamer: just a thought, but have u tried to change phone modes from settings? I mean dual-3g-gsm.21:12
DocScrutinizer05anyway who cares about special keys in console of N900? ;-P21:12
DocScrutinizer05after all console isn't what you want to run on N900 in the end21:13
Enrico_MenottiDocScrutinizer05 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/...).21:14
Enrico_MenottiI'm just curious to understand where these events get mapped to keycodes.21:15
*** xorly has quit IRC21:20
*** N-Mi has quit IRC21:22
*** florian has joined #maemo21:43
dreamerVajb: either gsm or 3g it still loses connection21:50
dreamerI think I'll have to go try and destroy a pen to put the spring in there21:52
dreameror 'bits of spring'21:53
dreamerand see if that keeps the modem connected ..21:53
*** Kabouik has joined #maemo21:56
*** frals has joined #maemo22:09
*** Kabouik has joined #maemo22:15
*** Kabouik has quit IRC22:16
*** jskarvad has quit IRC22:24
*** RedW has quit IRC22:48
dreamerWizzup: you don't happen to want to trade an n900 do you? ;)  (if you don't need stable modem)22:53
*** RedW has joined #maemo23:07
*** xy2_ has joined #maemo23:12
*** remarc has quit IRC23:43
*** Cor-Ai has quit IRC23:47
*** Cor-Ai has joined #maemo23:51

Generated by 2.15.1 by Marius Gedminas - find it at!