| Wizzup | freemangordon: and the conversations in -devel does notifications in a more fremantle ish way now | 00:43 |
|---|---|---|
| Wizzup | uvos: maybe we could increase the modem debug logs in dmesg, compare that, not sure if it will surface much | 01:11 |
| inky | i bought mz617. it was sold sort of cheaply with remark that it has problem accessing internet. i figured that's an old ssl problem, it doesn't matter when i am able to install maemo on it. | 12:51 |
| inky | so let's see. | 12:51 |
| inky | will get it in one month probably. | 12:52 |
| donc | With all of the N900 talk going on I thought I might interject my finding that the ir proximity sensor on mine (Maemo5) is continuously flashing non stop except when shutdown. When the screen is off I see no reason for it except spying 🤨️ | 14:03 |
| Wizzup | donc: I think the IR is tx only, so I don't think it can spy | 14:26 |
| Wizzup | but I am not quite sure | 14:26 |
| donc | exept that there is an adjacent camera lens | 14:27 |
| Wizzup | seems like hw oldage to me :) | 14:28 |
| donc | distance measurement is made using ir lasers and so making a topographical map of ones face isn't too far fetched. I know that Facebook uses facial recognition on users. | 14:30 |
| Wizzup | well you can install maemo leste and see if it still happens :P | 14:31 |
| donc | some of my newer phone do the same | 14:31 |
| donc | I use de-googled LineageOS and my moto g7 (i think) does the same. I just put scotch tape over the selfie camera :) | 14:33 |
| sicelo | donc: for the N900's proximity sensor, it *is* far fetched. that sensor literally only ever reads 1 and 0 | 14:33 |
| donc | its a flash next to camera | 14:34 |
| sicelo | ? | 14:34 |
| donc | what good is a proximity sensor of nothing is reading the reflection? | 14:35 |
| sicelo | i didn't say it isn't reading it. i said it reads it, with only the value of 1 or 0. | 14:36 |
| donc | I's still saying that the camera lens can use an ir flash to take night time photos | 14:36 |
| donc | I don't trust big tech | 14:37 |
| sicelo | what's the camera flash go to do with the proximity sensor? | 14:37 |
| sicelo | and there' no ir flash for night time photos anyway. where are you getting your information from? | 14:38 |
| sicelo | https://media.digikey.com/pdf/Data%20Sheets/Osram%20PDFs/SFH_7741.pdf here's the proximity sensor, so you can make informed conclusions | 14:39 |
| donc | I can see the IR flashing constantly using my night vision monocular. | 14:39 |
| sicelo | the proximity sensor's IR will always flash ... which is easy to understand if you look at how the chip works (i gave you the link ...) | 14:40 |
| donc | I have another cheap night vision device that takes night time videos | 14:40 |
| sicelo | hehe, so? | 14:41 |
| donc | why have a sensor to turn of the screen when the screen is off? | 14:41 |
| donc | wasted battery life | 14:41 |
| sicelo | it's not for turning screen off | 14:41 |
| sicelo | also, did you look at the schematic for the sensor? | 14:42 |
| donc | whats it for beside knowing if its in your pocket or at your ear? | 14:42 |
| donc | not yet | 14:42 |
| sicelo | you should | 14:48 |
| donc | I've read of TVs spying on people and we all know that Alexa and the like listen to every word being said. | 14:49 |
| sicelo | yes, doesn't mean everything else is spying on you though :-) | 14:49 |
| sicelo | you realize the N900 is from 2009 ... ? has a very weak cpu as well? ... hardly enough power to spy on you in a meaningful way | 14:50 |
| donc | it raises concern and it's everyones choice to allow it | 14:51 |
| donc | it has enough power i'm sure | 14:52 |
| freemangordon | donc: ofc you are free to believe whatever you want, but think about the usecase when you have a phone call going on and you hold the phone near your ear. Now, screen is off (and so is TS), but proximity must be on so SW detect when you move phone away from your head and enable display/TS. If proximity is on even when the device is locked, please check you you have shortcutd installed and configured to use proximity ;) | 16:13 |
| donc | When I recieved my night vision unit I had three different phones on the table. I always disable everything I can and they were all locked and all of them had flashing IR. IDK what's going on but I see the potential. The OS installed doesn't seem to affect the activity. Since it's rare for people to look at their phones through NV gear I like to throw it out there since when one locks their screen it is logical for it to stop. | 16:27 |
| donc | Admittedly my Note5 didn't do it and my Pinephone stops flashing after 20 seconds or so of being locked | 16:29 |
| Wizzup | freemangordon: on the subject of IR, if you can help us pull that past the finish line | 16:38 |
| Wizzup | I cherry picked your code onto my 6.6 branch but it didn't compile | 16:38 |
| Wizzup | something about atomic | 16:38 |
| f_ | How can IR spy on you? | 16:46 |
| f_ | (tx-only, I mean) | 16:47 |
| donc | again, IR flash with adjacent camera. | 16:49 |
| f_ | doubt there's IR flash on a nokia phone from 2009.. | 16:51 |
| donc | again, I have an N900 that flashes IR constantly, non stop unless powered off. It's invisible without special gear. | 16:56 |
| Wizzup | if you plan to throw it out, maybe send it to one of us | 16:58 |
| donc | haha, no I throw nothing away. I'd use it except no T-Mobile where i live now | 17:01 |
| f_ | donc: What does that have to do with some IR camera flash? | 17:05 |
| donc | Maybe someone could read the spec showing the lightwave frequency that the camera sensor is sensitive to. If it reads the IR spectrum, what a coincedence that would be huh? | 17:09 |
| Wizzup | I think it would be more productive to continue this elsewhere, this isn't really related to maemo or maemo leste | 17:13 |
| Wizzup | freemangordon: found some old a33 tablet here, I think it runs the very first lima versioh we got to work with h-d heh | 17:14 |
| Wizzup | probably it's on ascii | 17:14 |
| freemangordon | Wizzup: which patches, those from the LKML or for leste GH? | 17:43 |
| Wizzup | https://github.com/maemo-leste/droid4-linux/tree/maemo-6.6 | 17:45 |
| Wizzup | wait | 17:45 |
| Wizzup | here: https://github.com/maemo-leste/droid4-linux/tree/maemo-6.6-buildeb | 17:45 |
| Wizzup | meanwhile uvos made https://github.com/maemo-leste/droid4-linux/tree/maemo-6.6v3 but he didn't pull the ir patches because they caused compilation failures | 17:45 |
| Wizzup | freemangordon: here is the output from the compile process: https://phoenix.maemo.org/job/droid4-linux-binaries/architecture=armhf,label=armhf/192/consoleText | 17:56 |
| Wizzup | I didn't look too hard | 17:57 |
| Wizzup | search for: | 17:57 |
| Wizzup | drivers/media/rc/pwm-ir-tx.c: In function 'pwm_ir_timer': | 17:57 |
| Wizzup | drivers/media/rc/pwm-ir-tx.c:129:3: error: implicit declaration of function 'pwm_apply_atomic'; did you mean 'pwm_ir_tx_atomic'? [-Werror=implicit-function-declaration] | 17:57 |
| arno11 | Wizzup: i just tried the sysctl.d and init script on boot and it's ok :) | 19:30 |
| arno11 | btw my sphone caller UI troubles after boot are solved: i removed appmenu-gtk2-module... | 19:32 |
| Wizzup | heh | 19:40 |
| arno11 | out of curiosity: you have 6.6 on your D4 actually ? | 19:42 |
| freemangordon | Wizzup: pwm_apply_atomic is in 6.8, not in 6.6 | 20:04 |
| freemangordon | lots of patches has to be pulled for upstream code to compile and work | 20:05 |
| freemangordon | https://patchwork.kernel.org/project/linux-media/list/?series=811482 | 20:09 |
| freemangordon | and https://patchew.org/linux/1696312220-11550-1-git-send-email-ivo.g.dimitrov.75@gmail.com/ | 20:12 |
| freemangordon | oh, and we need to patch pwm-omap-dmtimer.c like this https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pwm/pwm-bcm2835.c#n170 | 20:15 |
| Wizzup | ok | 20:34 |
| arno11 | Wizzup: for cssufeatures: i added (locally atm) 'no blur', 'boost 805' and 'no boost' buttons with notifications and i removed/fixed the weird 'main' button on top left. | 22:15 |
| arno11 | i think we need 3 'versions' (n900 boost + no blur, d4 boost and a generic one) | 22:18 |
| Wizzup | I don't know how the d4 boost works actually | 23:01 |
| Wizzup | do we have boost mode for the d4 too? | 23:01 |
| arno11 | iirc yes, it should work | 23:07 |
| arno11 | uvos added it iirc | 23:08 |
| Wizzup | ok | 23:11 |
| Wizzup | so maybe we should add the /etc/leste-device via leste-config or something like this? | 23:11 |
| Wizzup | how does postmarketos do this I wonder | 23:11 |
| arno11 | leste-device could do the trick imo | 23:12 |
| arno11 | and then we can use postinstall script to check the device and use the correct python scripts | 23:14 |
| arno11 | (just an idea) | 23:15 |
| Wizzup | hm? | 23:18 |
| Wizzup | I think cssufeatures would read /etc/leste-device | 23:18 |
| Wizzup | or something like this | 23:18 |
| Wizzup | I think maemo had a system for this | 23:18 |
| Wizzup | osso-product-info or something | 23:19 |
| Wizzup | https://github.com/maemo-leste/osso-product-info | 23:19 |
| arno11 | ok, and yes ofc cssufeatures can read leste-device directly but the code is like spaghetti... | 23:20 |
| Wizzup | yup | 23:21 |
| Wizzup | the cssufeatures code really is spaghetti | 23:22 |
| Wizzup | :D | 23:22 |
| arno11 | indeed | 23:22 |
| arno11 | so that's why my idea was to create other versions of the existing scripts | 23:23 |
| Wizzup | so we could re-implement osso-product-info and have it read info from /etc/leste-device | 23:23 |
| Wizzup | https://github.com/maemo-leste/osso-product-info/blob/master/libossoproductinfo.c | 23:23 |
| Wizzup | freemangordon: do we want to keep osso-product-info ? | 23:40 |
| Wizzup | or rather, do we want to use it for device identification | 23:40 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!