| stano | the commands list is a fixed list, it lets me edit the cmd, but it still is listed under Commands as "Internal IP" | 00:02 |
|---|---|---|
| stano | and there's no option in the settings menu to select autorun or run-only-on-click | 00:03 |
| stano | ok there is, you have to scroll down, but i couldn't scroll down the first 5 tries | 00:05 |
| stano | this doesn't work as a command, i do see drive access light fliash though | 00:08 |
| stano | echo 4 > /sys/class/backlight/backlight/brightness | 00:08 |
| Wizzup | uvos: ping | 00:08 |
| stano | the file is chmod uog+w and can be set by user in shell | 00:09 |
| uvos | Wizzup: pong | 00:10 |
| stano | "Invalid command" | 00:11 |
| sicelo | you can look at the source. seems DCEW expects to receive output, which makes sense as per its description | 00:19 |
| uvos__ | i also dont understand why you would want to do this anyhow | 00:28 |
| uvos__ | just disable als and set brightness via mce normaly? | 00:29 |
| uvos__ | if als annoying you is the problem | 00:29 |
| stano | how do i do that | 00:30 |
| uvos__ | you can just not load iio-als by overriding the modulesDevice line in your mce 90-user.ini | 00:30 |
| stano | it's impossible to set brightness currently without commandline | 00:30 |
| stano | ty | 00:30 |
| uvos__ | no its not | 00:30 |
| uvos__ | seting birghtness works absoulty fine | 00:30 |
| stano | you get either dark, or full brightness | 00:30 |
| uvos__ | no | 00:30 |
| stano | would a demonstration video help? | 00:31 |
| uvos__ | there is a bug with the applet | 00:32 |
| stano | i find /etc/mce/mce.ini.d/99-user.ini | 00:32 |
| stano | is that the file? | 00:32 |
| uvos__ | yes | 00:32 |
| uvos__ | you have to touch it twice to get the right level | 00:32 |
| uvos__ | then als varys the brightness | 00:33 |
| uvos__ | if your als is broken or dirty it might be pretty dark allways | 00:33 |
| stano | mmandline | 00:34 |
| stano | 00:30 < stano> ty | 00:34 |
| stano | /etc/mce/mce.ini.d/99-user.ini is empty | 00:34 |
| uvos__ | yes that right | 00:34 |
| uvos__ | your supposed to take values from the other ini files | 00:34 |
| uvos__ | inc. mce.ini | 00:34 |
| uvos__ | and paste them in there | 00:34 |
| stano | ok | 00:34 |
| uvos__ | and then modify them | 00:34 |
| uvos__ | in this case ModulesDevice | 00:35 |
| uvos__ | needs iio-als removed | 00:35 |
| uvos__ | but really brightness should work fine | 00:35 |
| uvos__ | if not your working around some broken hw or setup on your end | 00:35 |
| stano | so 99-user.ini would contain ModulesDevice=led-sw;led-dbus;button-backlight;iio-accelerometer;evdevvibrator;iio-proximity | 00:36 |
| uvos__ | yes you need ModulesDevice to stay in the same section | 00:36 |
| uvos__ | so the section header needs to be in there too | 00:36 |
| stano | ok | 00:36 |
| stano | sicelo: i see there's new info on encoding video for Droid4 https://talk.maemo.org/showpost.php?p=1572284&postcount=7 | 03:32 |
| die-juse | . | 04:18 |
| lel | parazyd transferred a repository: https://github.com/maemo-leste-upstream-forks/eg25-manager | 09:34 |
| stano | wb Pali | 10:15 |
| lel | clort81 opened an issue: https://github.com/maemo-leste/bugtracker/issues/558 (desktop-cmd-exec: does not execute commands that do not return values) | 10:33 |
| parazyd | uvos__: Do you know how I could rotate accelerometer readings' x and y by 90 degrees? | 10:54 |
| parazyd | I'm not sure I completely understand the iio-sensor-proxy mount matrix and if it's relevant to this | 10:54 |
| stano | have your application swap x and y values? | 10:55 |
| parazyd | Not doable | 10:55 |
| parazyd | Basically I want the following: http://ix.io/3sWY | 11:00 |
| stano | yes, swapping x and y and possibly inverting one or both | 11:04 |
| stano | you're asking if that's possible with some config entry in like, /sys ? | 11:05 |
| parazyd | Yeah or with the mounting matrix un udev | 11:05 |
| stano | playing around with other batteries might not be a great idea. one of my d4's stopped charging entirely, on leste or android, even with original EB41. | 11:18 |
| _uvos_ | parazyd: the udev matrix is right | 12:01 |
| _uvos_ | parazyd: your app must ask udev for the matrix and apply it itself, the kernel/ sysfs interface is not reposible for applying the matrix | 12:02 |
| _uvos_ | udev gets the matrix from kernel or, optionally its config files | 12:03 |
| _uvos__ | stano: it is extreamly unlikely that simple using another battery breaks anything | 12:07 |
| _uvos__ | eb41 is just a lipo directly connected to the contacts | 12:07 |
| _uvos__ | note however that the 2 other conections on d4 are a eeprom chip and a thermistor | 12:08 |
| stano | can the n900 receiving a 0xFFF u-boot*.bin be on a USB hub? (powered) | 12:08 |
| _uvos__ | android, rightfully so as it needs to know if the the battery is of the hv type, refuses to charge a battery without a eeprom | 12:09 |
| stano | ah ty | 12:09 |
| _uvos__ | and the mainline kernel as of recent patches refuses to charge a battery without a thermistor | 12:09 |
| _uvos__ | but while adding that i added the option | 12:10 |
| _uvos__ | ignore_temperature_probe=1 to cpcap_battery | 12:10 |
| stano | :) very nice :) | 12:10 |
| _uvos__ | to reenable charging | 12:10 |
| _uvos__ | ofc you accept the (small) risks inherent in charging a battery with no thermistor | 12:11 |
| stano | mine has the little battery protection board on it | 12:11 |
| _uvos__ | i wound remove that | 12:11 |
| _uvos__ | *would | 12:12 |
| stano | ah did you do that on the polarcell? | 12:12 |
| _uvos__ | yes | 12:12 |
| _uvos__ | or rather there was none on that one iirc | 12:12 |
| stano | did you have to spot-weld wires onto the tabs of the polarcell or could you solder? | 12:12 |
| _uvos__ | spot weld | 12:12 |
| _uvos__ | cpcap is real tocuhy about ir and dosent like being prevented from charging the bat charging | 12:13 |
| _uvos__ | so never connect usb with something other than a battery connected | 12:14 |
| _uvos__ | and the bms of some bat might get in the way with overzealus overcharging protection | 12:14 |
| parazyd | _uvos__: The first one here http://ix.io/3sWY isn't what mce expects for example | 12:17 |
| _uvos__ | sure mce gets this from iio-sensor-proxy and iio-sensor proxy gets this by applying the udev matrix | 12:23 |
| _uvos__ | its easy to do this | 12:23 |
| _uvos__ | its just a normal transofrmation matrix. | 12:24 |
| _uvos__ | 0 -1 0 | 12:26 |
| _uvos__ | 1 0 0 | 12:26 |
| _uvos__ | 0 0 1 | 12:26 |
| _uvos__ | should be a 90 deg rotation | 12:27 |
| _uvos__ | around z | 12:27 |
| _uvos__ | check out leste-config for mapphones on the syntax required | 12:28 |
| _uvos__ | you want to rotate left tho | 12:30 |
| _uvos__ | so i gues its | 12:30 |
| _uvos__ | 0 1 0 | 12:30 |
| _uvos__ | -1 0 0 | 12:30 |
| _uvos__ | 0 0 1 | 12:30 |
| parazyd | _uvos__: ok, then I'm understanding it correctly, it's just that it's not being read in udev | 12:35 |
| parazyd | No matter what I do, nothing changes | 12:35 |
| parazyd | SUBSYSTEM=="iio", ENV{OF_NAME}=="mpu6050", ENV{ACCEL_MOUNT_MATRIX}="0, 1, 0; -1, 0, 0; 0, 0, 1" | 12:36 |
| parazyd | hmm | 12:36 |
| parazyd | _uvos___: udev didn't seem to trigger what I wanted | 12:45 |
| parazyd | Now I got it | 12:45 |
| _uvos___ | well ofc the match stuff needs to be correct | 12:45 |
| parazyd | btw. the correct matrix that results in the rotation | 12:45 |
| parazyd | 1 0 0 | 12:45 |
| parazyd | 0 1 0 | 12:46 |
| parazyd | 0 0 1 | 12:46 |
| _uvos___ | ok | 12:46 |
| parazyd | And this is like, normal identity | 12:46 |
| _uvos___ | so the matrix from kernel is something else | 12:46 |
| parazyd | mhm | 12:46 |
| _uvos___ | you overrode it | 12:46 |
| Wizzup | parazyd: looks like n900 wifi is broken for everyone | 12:53 |
| parazyd | Yep | 12:53 |
| rafael2k | hey | 12:54 |
| rafael2k | I see modem-power went to pp kernel - tks | 12:54 |
| rafael2k | but no modem yet | 12:54 |
| rafael2k | :( | 12:54 |
| parazyd | rafael2k: Be patient | 12:54 |
| Wizzup | lol | 12:55 |
| rafael2k | CONFIG_MODEM_POWER=y | 12:55 |
| rafael2k | ; ) | 12:55 |
| rafael2k | Should not this be a Module? | 12:55 |
| rafael2k | no rush! | 12:55 |
| rafael2k | megi's defconfig works fine last time I grabbed his binaries and booted it | 12:57 |
| stano | do you guys ever see upowerd and udevd go wacky with the cpu use? two udevd processes here at 18 and 23%, and upowerd at 28% | 14:16 |
| stano | and something is blinking that 'hdd' LED | 14:17 |
| Wizzup | What device and what ... hdd led | 14:17 |
| stano | droid4 and it's the setting from 'blinkenlights' to make the capslock LED blink on sdcard access | 14:18 |
| Wizzup | I don't think I've seen that on mine | 14:19 |
| stano | one udevd is pid 526 and the other is 5204 | 14:19 |
| stano | i'll try reboot | 14:20 |
| stano | or rather shutdown then power-on again. reboot command is a bit weird. | 14:21 |
| stano | yeah /var/log/messages show it was cpcap throwing a fit over the experimental battery | 14:38 |
| stano | back to EB41 and no more message spam | 14:38 |
| freemangordon | oh, it seem n900 u-boot issue is resolved :) | 16:38 |
| stano | where can i read about it | 16:39 |
| stano | i can't get 0xFFFF to recognize my n900 | 16:39 |
| freemangordon | on the u-boot ML. Also, on maemo-leste ML | 16:40 |
| stano | ty | 16:41 |
| freemangordon | hmm, it seems leste ML does not allow unregistered users posting, maybe it waits for moderator approval | 16:41 |
| freemangordon | stano: this https://lists.denx.de/pipermail/u-boot/2021-July/454753.html | 16:43 |
| Wizzup | freemangordon: does seem like they'd prefer to see more happen in the near dfuture | 16:46 |
| Wizzup | s/dfuture/future/ | 16:46 |
| freemangordon | sure, but at least they don;t mandate DT migration anymore | 16:47 |
| freemangordon | but lets wait for Pali to comment | 16:48 |
| uvos__ | Wizzup: heh http://web.archive.org/web/20130806073837/http://sbf.droid-developers.org/ | 21:45 |
| uvos__ | Wizzup: you guys archived sbf.droid-developers.org with the files | 21:46 |
| uvos__ | Wizzup: neat they have files for some real obscure devices like razor i/ xt890 even | 21:46 |
| uvos__ | Wizzup: sadly no sbf for xoom 2 | 21:47 |
| uvos__ | Wizzup: so just unfortionatly thats just the url name | 21:47 |
| uvos__ | also some devices i dident even know of like xt885 and xt881 two more mapphones looks like. | 21:48 |
| uvos__ | xt890 is neat because its a x86 xt910 with a intel atom instead of omap4 | 21:49 |
| Wizzup | uvos__: aw | 22:15 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!