sixwheeledbeast | backlight timeout can be set to 10 seconds so it's possible | 00:00 |
---|---|---|
rhombus | I think I set it to 10 s | 00:00 |
rhombus | yeah, this is the timeout | 00:00 |
rhombus | the backlight fades, then goes out | 00:00 |
sixwheeledbeast | Right well from what you have said i believe the keyboard slide sensor is playing up | 00:00 |
rhombus | ok, that's what I suspected | 00:01 |
sixwheeledbeast | you can try to read the state to confirm | 00:01 |
rhombus | given that I dropped it while open -- not hard, mind you, but still | 00:01 |
rhombus | ok | 00:01 |
rhombus | how do I do that? | 00:01 |
sixwheeledbeast | ~beasttweaks | 00:01 |
infobot | i guess beasttweaks is http://wiki.maemo.org/User:Sixwheeledbeast/Scripts | 00:01 |
sixwheeledbeast | while true; do cat /sys/devices/platform/gpio-switch/slide/state; done | 00:01 |
sixwheeledbeast | the above in a terminal will show the live state | 00:02 |
rhombus | this is great! | 00:03 |
rhombus | ok | 00:04 |
sixwheeledbeast | usual bash Ctrl+C to kill | 00:04 |
rhombus | the slider switch seems to be fine | 00:04 |
rhombus | when it is open, it reads open, when it is closed, it reads closed | 00:04 |
rhombus | so it must be the lockswitch, right? | 00:05 |
rhombus | Is there any way to read that out? | 00:05 |
sixwheeledbeast | possibly I have never tried because the screen would blank | 00:05 |
rhombus | right, that does make it hard | 00:06 |
rhombus | ok, I was just trying to use the phone via the display and it went blank :/ | 00:06 |
sixwheeledbeast | also the days of using my lockswitch are long gone | 00:09 |
rhombus | you don't use your lockswitch? why not? | 00:09 |
sixwheeledbeast | It's been completely flat for about 4 years so impractical to use. I have a way to use the camera button to lock | 00:10 |
rhombus | ok, in the gpio-switch directory there is a kb_lock device. Could that be it? | 00:11 |
sixwheeledbeast | yes. you may see the state on the display if you look at the screen quick enough | 00:12 |
sixwheeledbeast | my wiki page also has proximity state and back cover if you need those. | 00:13 |
sixwheeledbeast | maybe the tv out would show the display if locked I can't remember. | 00:13 |
rhombus | I could dump the cat to a file | 00:14 |
sixwheeledbeast | yep that too | 00:14 |
sixwheeledbeast | but you have no timing to compare to | 00:14 |
rhombus | I was just thinking about how I could timestamp it :) | 00:15 |
sixwheeledbeast | You could look at dmesg too for these | 00:16 |
rhombus | ah, yes! | 00:16 |
rhombus | this is funny, now that I am watching this device, the problem has not reoccured. | 00:18 |
rhombus | activating the lockswitch gives "closed" then "open" | 00:19 |
rhombus | I'm guessing it shows "closed" only if the lockswitch is held depressed | 00:20 |
rhombus | weird, it appears to be behaving again | 00:22 |
rhombus | maybe all this opening and closing of slide and lockswitch cleaned something out? | 00:22 |
sixwheeledbeast | well now you have the tools to debug in the future. you could also look in the logs history. i have never had the keyboard slider apart to know if thats possible | 00:23 |
rhombus | ah ha | 00:23 |
rhombus | I could reproduce it again | 00:23 |
rhombus | In dmesg I get this: [9261.323791] kb_lock (GPIO 113) is now closed | 00:25 |
rhombus | [9262.863067] kb_lock (GPIO 113) is now open | 00:25 |
rhombus | [9262.894226] kb_lock (GPIO 113) is now closed | 00:26 |
rhombus | that's 31 ms | 00:26 |
rhombus | Maybe there is just some crap in the switch | 00:27 |
rhombus | I do carry the phone in my pocket and there is considerable dust behind the battery plate. | 00:28 |
rhombus | I might try some compressed air. | 00:28 |
rhombus | But thanks for all the hardware device file tips, that is immensely helpful! | 00:29 |
rhombus | sixwheeledbeast: thanks again for all your help, I appreciate it a lot! | 00:39 |
sixwheeledbeast | np | 00:39 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!