<uvos>
i would just try the latest image on a device
<uvos>
the latest image being unbootable has been a reoccuring theme
<uvos>
we should have a test stand that boots it on device and checks ps for all the processies we expect to run at boot or something.
<Wizzup>
uvos: I think he reported this been a consistent problem for him
<Wizzup>
for months
<Wizzup>
I think we need a list of things to check / attach when filing a bug
<Wizzup>
brb
<uvos>
well if he has this problem whilest the image works fine when installed on other devices
<uvos>
dmsg is the obvious log since that suggests hardware failure
zhxt has joined #maemo-leste
cockroach has joined #maemo-leste
<Wizzup>
could be, or hw differences
uvos has quit [Ping timeout: 268 seconds]
drrty has joined #maemo-leste
sicelo has quit [Ping timeout: 245 seconds]
sicelo has joined #maemo-leste
sicelo has joined #maemo-leste
elastic_dog has quit [Ping timeout: 268 seconds]
elastic_dog has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 265 seconds]
zhxt has quit [Ping timeout: 252 seconds]
sunshavi_ has joined #maemo-leste
sunshavi has quit [Ping timeout: 268 seconds]
sunshavi_ has quit [Read error: Connection reset by peer]
inky has quit [Ping timeout: 265 seconds]
uvos has joined #maemo-leste
sunshavi_ has joined #maemo-leste
inky has joined #maemo-leste
sunshavi_ has quit [Ping timeout: 252 seconds]
sunshavi_ has joined #maemo-leste
sunshavi_ has quit [Remote host closed the connection]
inky has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 265 seconds]
inky has joined #maemo-leste
sunshavi has joined #maemo-leste
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
Pali has joined #maemo-leste
buZz has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
hallyn has joined #maemo-leste
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #maemo-leste
donchurch has joined #maemo-leste
<donchurch>
Greetings! First time user here. I want to express my concerns regarding the infrared selfie flash that is continually flashing. I discovered this while using night vision equipment. On my N900 booting the latest from an sdcard.
<donchurch>
I discovered the same issue on my LG v20 while using a custom rom (without GAPPS) but it stopped when I installed LineageOS.
<donchurch>
The N900 has a custom rom too from numerous years ago replacing the stock OS
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 268 seconds]
<sixwheeledbeast>
I believe you are on about a active IR sensor to detect when the phone is against your face.
<donchurch>
Hmm, thanks for the info. I didn't know that was how that functioned. I'll check that out.
<uvos>
should not be flashing in leste tho
<uvos>
leste dosent use the sensor at all on n900
<uvos>
so it should be off
<uvos>
on d4/bionic/pp it should get turned on in certian cercumstances but be off otherwise
<sixwheeledbeast>
while true; do cat /sys/devices/platform/gpio-switch/proximity/state; done
<freemangordon>
hmm, proximity should be enabled only when in call
<sixwheeledbeast>
How you can test it in fremantle.
<uvos>
freemangordon: there are also other cases (right after a alarm fires)
<uvos>
freemangordon: but yeah
<uvos>
freemangordon: but leste dosent controll the proximitry sensor at all on n900 atm
<freemangordon>
right, alarm is the other user
<uvos>
freemangordon: since its on the evdev interface something might be holding the if open and the sensor on
<freemangordon>
mhm
<uvos>
freemangordon: could be x
<freemangordon>
right
<freemangordon>
sixwheeledbeast: hi! long time no see :)
<sixwheeledbeast>
hey freemangordon
<uvos>
we should open a bug to bring the prox to the iio interface on n900 iirc its just a gpio so should be trivial to port the driver
<uvos>
we have a analogus bug for the acell
<freemangordon>
does iio support proximity class?
<uvos>
yeah
<freemangordon>
should be trivial then
<uvos>
yeah
<freemangordon>
hmm, maybe I can take that one once I finish with PipCalendar stuff, to have some rest from abook
<uvos>
same thing with acell, there a driver even exits allready and works
<uvos>
only the n900's comptabile needs adding
<uvos>
and the old driver needs removal
<freemangordon>
I see
<hallyn>
what kernel does leste use on n900?
<uvos>
pretty old one 5.1 iirc
<hallyn>
oh but not the original 3.x or whatever? that's cool.
<uvos>
orignal was 2.6.x
<hallyn>
i need to *find* my n900 - someone's hidden it - but until now i was afraid of using it bc of old software, but leste would let me us e it!
<hallyn>
thanks.
<uvos>
leste its still quite rough but yeah it can be used for some basic tasks
<uvos>
the n900 suffers under some extra issues too most problematic of these are: it has broken rotation and broken pm.
<hallyn>
there's a simple debian repo where all the source and binary packages can be found?
<hallyn>
I hope the broken pm isn't due to missing proprietary kernel features...
<uvos>
all of the n900 special issues are related to the propretary powervr driver
buZz has joined #maemo-leste
<hallyn>
well. could be fun to dig into too.
buZz is now known as Guest1033
<hallyn>
hopefully i find my n900 in storage tomorrow. else i won't know where else to look
Guest1033 is now known as buZz
xmn has joined #maemo-leste
sunshavi has quit [Read error: Connection reset by peer]