ArturShaik has joined #neo900
_whitelogger has joined #neo900
_Chris_ has quit [Remote host closed the connection]
preview has joined #neo900
andi- has quit [Remote host closed the connection]
andi- has joined #neo900
preview has quit [Ping timeout: 245 seconds]
preview has joined #neo900
him-cesjf has quit [Ping timeout: 252 seconds]
norly has quit [Quit: Leaving.]
norly has joined #neo900
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #neo900
neo900 has joined #neo900
Joerg-Neo900 is now known as Guest49961
neo900 is now known as Joerg-Neo900
Guest49961 has quit [Killed (cherryh.freenode.net (Nickname regained by services))]
preview has quit [Ping timeout: 245 seconds]
preview has joined #neo900
ecloud_wfh is now known as ecloud
preview has quit [Quit: No Ping reply in 180 seconds.]
clapont has quit [Ping timeout: 240 seconds]
preview has joined #neo900
clapont has joined #neo900
Pali has joined #neo900
preview has quit [Quit: No Ping reply in 180 seconds.]
preview has joined #neo900
Kabouik has joined #neo900
Pali has quit [Ping timeout: 240 seconds]
_Chris_ has joined #neo900
_Chris_ has quit [Ping timeout: 265 seconds]
_Chris_ has joined #neo900
preview has quit [Ping timeout: 245 seconds]
preview has joined #neo900
preview has quit [Ping timeout: 245 seconds]
_Chris_ has quit [Ping timeout: 240 seconds]
preview has joined #neo900
xmn has joined #neo900
preview has quit [Ping timeout: 264 seconds]
xmn has quit [Ping timeout: 240 seconds]
ArturShaik has quit [Ping timeout: 268 seconds]
Pali has joined #neo900
_Chris_ has joined #neo900
Kabouik has quit [Ping timeout: 268 seconds]
illwieckz has quit [Ping timeout: 245 seconds]
illwieckz has joined #neo900
_Chris_ has quit [Ping timeout: 268 seconds]
_Chris_ has joined #neo900
Kabouik has joined #neo900
him-cesjf has joined #neo900
xmn has joined #neo900
Kabouik has quit [Ping timeout: 276 seconds]
him-cesjf has quit [Quit: Quit]
Oksana has quit [Ping timeout: 240 seconds]
Oksana has joined #neo900
clapont has quit [Ping timeout: 240 seconds]
xmn has quit [Ping timeout: 240 seconds]
rhombus has joined #neo900
<rhombus> Hi everybody
<rhombus> The N900 I have been using since March 2017 has signs of a fault. The screen spontaneously lights up.
<rhombus> I think it might be an issue with the slider switch. I dropped the phone while it was open about 10 days ago.
<rhombus> Has anyone seen this before? Do you have any advice?
<rhombus> ... and while I'm at it, I wanted to ask: What's the status of the Neo900 project?
clapont has joined #neo900
<rhombus> Oh, sorry. I just read the status post.
<rhombus> That's a shame.
drrty has quit [Remote host closed the connection]
drrty has joined #neo900
<sixwheeledbeast> I believe the slider has a magnet to trigger open close state.
<rhombus> sixwheeledbeast:let me be more precise about what I am observing
<rhombus> sixwheeledbeast: so i often activate the screen with the small slider switch on the right hand side of the device
<sixwheeledbeast> that is the lockswitch
<rhombus> ah, ok
<rhombus> That is the switch that seems to be misbehaving
<rhombus> but I can't be sure
<sixwheeledbeast> if you open the keyboard slider the same thing would happen too
<rhombus> right
<rhombus> ok, so I just pulled on the lockswitch
<rhombus> and the screen lit up for about three seconds, then went dark again
<rhombus> did it again and the screen stayed illuminated for only one second
<sixwheeledbeast> Maybe you can log the state of the hardware inputs to check correct operation
<sixwheeledbeast> screen timeout should be consistent
<rhombus> that's why I suspect that the hardware is receiving a signal, I don't think this is a timeout
<rhombus> I also get the opposite behaviour sometimes
<rhombus> The screen is lit, then I lock it, then it spontaneously lights up again
<sixwheeledbeast> It could be possible that the light sensor is changing the backlight?
<rhombus> hmn
<rhombus> Would I expect the screen to go dark if I cover the light sensor?
<sixwheeledbeast> It depends on what is happening, there is a difference between screen backlight and a blank locked screen
<rhombus> Even if I am not calling?
<sixwheeledbeast> yes light sensor controls display backlight
<sixwheeledbeast> and also disables screen in a call
<rhombus> ok, if so, it's not having any effect on my phone
<rhombus> a dumb question -- this phone doesn't have two cameras, does it? The eye I see on the display side is the light sensor, correct?
<sixwheeledbeast> if you make a call and cover the light sensor with your thumb it should blank the screen
<sixwheeledbeast> front and back cameras
<rhombus> yes, that worked the last I checked (blanking during call)
<rhombus> ah
<rhombus> how do i use the back camera?
<sixwheeledbeast> light sensor is the smaller blob to the side of the camera
<sixwheeledbeast> back camera is behind the slide cover
_Chris_ has quit [Ping timeout: 268 seconds]
<rhombus> ok, sorry, the front camera then :)
<rhombus> how do I use the front camera?
<sixwheeledbeast> not much uses it
<rhombus> so the regular camera app doesn't use it?
<sixwheeledbeast> video calling and there was a mirror app at some point. It's pretty pants camera.
<sixwheeledbeast> no
<rhombus> ok, I just locked the phone, put it down, and after about 5 seconds, it lit up again and remains lit
<sixwheeledbeast> you can likely call the video output from a terminal somehow.
<rhombus> ok, now it is gone dark again
<rhombus> this is reminiscent of a loose contact
<sixwheeledbeast> blank or backlight off?
<rhombus> blank, as far as I can tell
<sixwheeledbeast> if it's completely blank I would assume the slider switch or keyboard slider
<rhombus> I did drop the phone while it was open about 10 days ago, but I didn't notice this problem until today
<sixwheeledbeast> if you do the same but when it lights up tap the screen and see if it blanks
Pali has quit [Ping timeout: 268 seconds]
<rhombus> so unlock it and then when it lights up, tap the screen?
<sixwheeledbeast> If it's the keyboard the display will not lock if it's the lockswitch it will lock
<sixwheeledbeast> lock it, when it does the fault of unlocking itself tap the screen
<rhombus> ah, ok
<rhombus> hang on
<rhombus> ok, I just locked it, and then about two seconds later the screen flickered about 5 times in succession
<sixwheeledbeast> you would need to tap the screen while it's lit up.
<rhombus> ok, I just locked it again, then it lit up, when I tapped the screen, the desktop settings widget appeared in the upper right hand corner
<sixwheeledbeast> and the device hasn't locked itself again?
<rhombus> If by locking you mean the screen going blank and not responding to input, it does do that if I wait long enough
<sixwheeledbeast> yes but that will be the lock timeout like 30 seconds?
<rhombus> it's more like 10
<sixwheeledbeast> I mean the device doesn't lock and unlock itself quickly like the fault anyway
<sixwheeledbeast> backlight timeout can be set to 10 seconds so it's possible
<rhombus> I think I set it to 10 s
<rhombus> yeah, this is the timeout
<rhombus> the backlight fades, then goes out
<sixwheeledbeast> Right well from what you have said i believe the keyboard slide sensor is playing up
<rhombus> ok, that's what I suspected
<sixwheeledbeast> you can try to read the state to confirm
<rhombus> given that I dropped it while open -- not hard, mind you, but still
<rhombus> ok
<rhombus> how do I do that?
<sixwheeledbeast> ~beasttweaks
<sixwheeledbeast> while true; do cat /sys/devices/platform/gpio-switch/slide/state; done
<sixwheeledbeast> the above in a terminal will show the live state
_Chris_ has joined #neo900
<rhombus> this is great!
<rhombus> ok
<sixwheeledbeast> usual bash Ctrl+C to kill
<rhombus> the slider switch seems to be fine
<rhombus> when it is open, it reads open, when it is closed, it reads closed
<rhombus> so it must be the lockswitch, right?
<rhombus> Is there any way to read that out?
<sixwheeledbeast> possibly I have never tried because the screen would blank
<rhombus> right, that does make it hard
<rhombus> ok, I was just trying to use the phone via the display and it went blank :/
<sixwheeledbeast> also the days of using my lockswitch are long gone
<rhombus> you don't use your lockswitch? why not?
<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
<rhombus> ok, in the gpio-switch directory there is a kb_lock device. Could that be it?
<sixwheeledbeast> yes. you may see the state on the display if you look at the screen quick enough
<sixwheeledbeast> my wiki page also has proximity state and back cover if you need those.
<sixwheeledbeast> maybe the tv out would show the display if locked I can't remember.
<rhombus> I could dump the cat to a file
<sixwheeledbeast> yep that too
<sixwheeledbeast> but you have no timing to compare to
<rhombus> I was just thinking about how I could timestamp it :)
<sixwheeledbeast> You could look at dmesg too for these
<rhombus> ah, yes!
<rhombus> this is funny, now that I am watching this device, the problem has not reoccured.
<rhombus> activating the lockswitch gives "closed" then "open"
<rhombus> I'm guessing it shows "closed" only if the lockswitch is held depressed
<rhombus> weird, it appears to be behaving again
<rhombus> maybe all this opening and closing of slide and lockswitch cleaned something out?
<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
<rhombus> ah ha
<rhombus> I could reproduce it again
<rhombus> In dmesg I get this: [9261.323791] kb_lock (GPIO 113) is now closed
<rhombus> [9262.863067] kb_lock (GPIO 113) is now open
<rhombus> [9262.894226] kb_lock (GPIO 113) is now closed
<rhombus> that's 31 ms
<rhombus> Maybe there is just some crap in the switch
<rhombus> I do carry the phone in my pocket and there is considerable dust behind the battery plate.
<rhombus> I might try some compressed air.
<rhombus> But thanks for all the hardware device file tips, that is immensely helpful!
preview has joined #neo900
<rhombus> sixwheeledbeast: thanks again for all your help, I appreciate it a lot!
<sixwheeledbeast> np
rhombus has quit [Quit: KVIrc KVIrc Aria 5.0.0, revision: 2fe1a3bcac42349967e27b3f7098c25f34efca1d, build type: release, sources date: 20160102, built on: 2019-10-15 04:32:10 UTC http://www.kvirc.net/]
preview has quit [Quit: No Ping reply in 180 seconds.]
preview has joined #neo900
_Chris_ has quit [Ping timeout: 268 seconds]
preview has quit [Ping timeout: 264 seconds]
_Chris_ has joined #neo900
preview has joined #neo900
Oksana_ has joined #neo900
Oksana_ has quit [Changing host]
Oksana_ has joined #neo900
Oksana has quit [Ping timeout: 240 seconds]
Oksana_ is now known as Oksana