**** BEGIN LOGGING AT Wed Feb 11 02:59:58 2015 Feb 11 06:39:39 f*ck this gcc 4.6 is unstable. lets see how 4.2 fares Feb 11 06:54:36 righty-o, no more segv Feb 11 06:59:22 |> rock and bonk (rockandb.mod) (8992, 1, Protracker M.K.) Feb 11 06:59:25 rock on! Feb 11 08:21:00 KotCzarny: why are you even using 4.6 Feb 11 08:21:09 either keep 4.2 for the historical stuff, or use 4.7 Feb 11 08:21:11 because it was in the repos Feb 11 08:21:21 which repo has 4.7? Feb 11 08:32:54 KotCzarny: no, you install it in scratchbox Feb 11 08:33:09 as per freemang0rdon's instructions Feb 11 08:40:49 kerio: im doing ondevice dev Feb 11 10:25:36 |> Jochen Hippel (ARCANE - New Stuff intro.sc68) - VrS! (11305 1/1, Jochen Hippel, 001 Amiga/Pau Feb 11 10:26:19 and my n800 is 95% idle Feb 11 13:58:16 do i hate useless symbols added to libs? yes, i do Feb 11 14:40:39 ha. finally Feb 11 14:40:47 one binary for maemo4 and 5 Feb 11 14:42:22 now, anyone knows how to access volume slider in n900 without calling heavy guns (qt, dbus, pulseaudio) Feb 11 14:52:10 KotCzarny: grab X11 keys (or what it is) and then volume up/down keys will be reported as some F* kyes Feb 11 14:52:22 (F6/F7 or F11/F12? something like that) Feb 11 14:52:37 erm Feb 11 14:52:58 that would need xlib as dependency Feb 11 14:53:34 right now im using alsa mixer, which somehow works, but im not sure if it doesnt set volume too high Feb 11 14:54:03 if you are not using X11/xcb, then open /dev/input/eventX device Feb 11 14:54:14 and listen for key events Feb 11 14:54:27 hum, but how do you read volume level via this method? Feb 11 14:54:58 on n900 there is preinstalled pulseaudio alsa plugin, so alsa default device is just support for pulseaudio Feb 11 14:55:07 and you *should* use pulseaudio for audio output! Feb 11 14:55:27 (ether nativelly or via that alsa plugin which via default device) Feb 11 14:55:28 im using esdcompat, which simply feeds pulseaudio Feb 11 14:55:34 thats ok too Feb 11 14:56:14 volume level you need to read from alsa or pulseaudio (or that esd layer if it supports) Feb 11 14:56:14 but its ok if alsamixer doesnt break things Feb 11 14:56:32 esd doesnt have mixer support :/ Feb 11 14:57:07 so im using oss mixer on n8x0 and alsa mixer on n900 Feb 11 14:57:50 ugly, but works Feb 11 16:16:44 hmm, I cant find https://gitorious.org/maemo-multimedia/gst-nokia-videosrc in maemo Feb 11 16:17:02 where does that code from ? is it actually used ? Feb 11 17:07:03 bencoh: I think yes, it is used Feb 11 17:07:15 but do not remember correct name of package and library... Feb 11 17:15:44 couldnt find it ... and we're missing deps to build it (there is a libomap3camd-dev headers RE project in gitorious, among others) Feb 11 17:16:07 it doesnt look like it was for maemo, considering the linux-kernel requirements (>= 2.6.32) Feb 11 17:16:36 trying to build it nonetheless in sb leads to weird automake errors Feb 11 17:21:08 hm... maybe its possible it is not used Feb 11 17:22:10 looks like it's a "new" camsrc (compared to v4l2camsrc) with white-balance (among others) support Feb 11 17:27:50 Does anyone in here use scapy? Feb 11 17:28:02 I believe pythom2.7 to be broken in maemo =( Feb 11 17:28:18 Am currently compiling 2.7.9 to see if it fixes scapy filter issues Feb 11 17:28:24 if anyone is interested =) Feb 11 18:00:56 hi, i have N900 with bme-replacement and usb mode switch Feb 11 18:01:48 is okay to have blue led notification diode on after mode change peripheral → host with boost → peripheral? Feb 11 18:02:45 i think blue led should lit only when host modes are active, or am i wrong? Feb 11 18:14:36 yes, blue led is when host mode is active Feb 11 18:14:44 change it back to peripheral Feb 11 18:22:21 Pali: but i already changed to peripheral mode and blue led still lit Feb 11 18:22:41 change back to host and then change back to peripheral Feb 11 18:22:43 maybe some bug Feb 11 18:49:09 i tried many variants (switch between host modes (boost or charging) mutually or with peripheral mode, with usb keyboard or without) and blue led is still lit on peripheral mode Feb 11 18:49:42 so i can do reboot to turn off blue led Feb 11 19:03:28 make sure you have last version of kernel-power, bme replacement and usbmode! Feb 11 19:15:33 usb mode version is 1.0-4 Feb 11 19:31:47 kernel-power is 2.6.28-10power53, updated circa 2 weeks ago Feb 11 19:32:19 i installed bme-replacement from it's repository 2 weeks ago Feb 11 20:11:03 did you used apt-get update && apt-get upgrade for installing bme-replacement? Feb 11 20:27:55 yes Feb 11 20:28:48 is problem if i had usb mode installed before bme-replacement install? Feb 11 20:36:45 order does not matter Feb 11 20:37:02 just need to be sure that everything is installed correctly Feb 11 20:37:13 try to reinstall all packages Feb 11 20:37:33 or try to call: sudo usbmode.sh peripheral Feb 11 20:37:35 in xterm Feb 11 20:37:50 it should provide some output Feb 11 20:46:05 there is only "Setting usb mode to peripheral" in xterm Feb 11 20:48:19 blue led sometime blinks in that mean that it turns off for few ms Feb 11 20:49:28 s/few/several Feb 11 21:03:58 please check /sys/class/power_supply/bq24150a-* Feb 11 21:04:06 what is enabled and what not Feb 11 21:04:15 maybe led is just broken... Feb 11 21:04:24 also reboot device and try again Feb 11 21:44:55 Hmm... My SMS-Chat messages are not readable. I mean, when I open conversations app, I see the last SMS-or-IM from each person, alright (72 characters or so). But when I click on it, to see the list of messages to-from the person, it's black-blank. I can still send alright, though. And, notifications are fine. Just this one window, SMS-or-IM to-from a single person, does not work. Feb 11 21:46:25 (talk.maemo.org) The person trying to log into your account had the following IP address: 117.169.1.197 Feb 11 21:46:40 looks like china mobile is bruteforcing tmo Feb 11 21:47:40 I have done: rm -rf .mozilla/rtcom and reboot ; I have done removal of .rtcom-eventlogger/el-v1.db and starting a new database ; reinstall of rtcom-messaging-ui and rtcom-messaging-ui-portrait ; and it still does not work. Feb 11 21:49:11 hmm Feb 11 21:49:22 did you break anything ? Feb 11 21:50:14 I don't know. Maybe, there was a recent CSSU-Testing update. I certainly wasn't tinkering with anything when it happened. Feb 11 21:51:26 Having some error logs from rtcom, or some modified-files-conflicts log from CSSU-Testing update, would be helpful. I just don't know where to find either of them. Feb 11 21:53:49 * Oksana also has troubles with virtual keyboard, and special symbols keyboard, hiding away as soon as it appears, making it extremely difficult to input a special character - it's the second problem to be solved... Also, most likely related to CSSU-Testing upgrade. Or just general lack-of-space in home?.. Feb 11 21:57:04 lack-of-space ? Feb 11 21:57:07 well, df -h ? :) **** ENDING LOGGING AT Thu Feb 12 02:59:58 2015