**** BEGIN LOGGING AT Fri Mar 28 02:59:59 2014
Mar 28 15:59:48 <sombragris> hi there
Mar 28 16:00:13 <sombragris> is there a way to take grayscale (black and white) pics with the N900 camera?
Mar 28 16:09:44 <ecc3g> you can always postprocess it,but I thought there was a setting to make it save b&w...
Mar 28 16:11:06 <ecc3g> hmm... i guess not..weird, could have sworn I saw it before...
Mar 28 16:13:51 <sombragris> ecc3g: yeah, I could postprocess it. I thought that. But I wanted to show my model a better preview of what I was asking of her
Mar 28 16:57:34 <Sicelo> sombragris: install 3rd party camera appplications. default camera in CSSU-Testing has that
Mar 28 17:05:21 <ecc3g> any good on-camera post processing software? heh
Mar 28 17:20:08 <DocScrutinizer51> gimp?
Mar 28 17:27:33 <raccoon_> imagemagick and your favorite terminal emulator :-)
Mar 28 18:32:26 <sombragris> DocScrutinizer05, raccoon_ : I know I could use these tools. My question was more on the sense of taking directly b-w photographs avoiding postprocessing.
Mar 28 18:33:09 <DocScrutinizer05> nikocam
Mar 28 18:33:36 <DocScrutinizer05> iirc
Mar 28 18:34:03 <DocScrutinizer05> or try fcam or blessN900
Mar 28 18:34:25 <DocScrutinizer05> ~pkg
Mar 28 18:34:26 <infobot> [pkg] http://maemo.org/packages/
Mar 28 18:35:31 <DocScrutinizer05> DUH, nikocam isn't in extras :-o
Mar 28 18:36:23 <DocScrutinizer05> http://talk.maemo.org/showthread.php?t=70870&highlight=cameraui2  here you are
Mar 28 18:43:43 <sombragris> blessN900 does not offer the option
Mar 28 18:43:52 <sombragris> will investigate these tools
Mar 28 18:56:23 <hxka> DocScrutinizer05: it's part of CSSU
Mar 28 18:56:51 <hxka> DocScrutinizer05: by the way, what camera Neo900 will have?
Mar 28 18:57:15 <DocScrutinizer05> I hope to get the original module, what else?
Mar 28 18:57:38 <DocScrutinizer05> though it's a PITA, starting with the SMIA95 socket
Mar 28 18:57:57 <hxka> Oh' nace
Mar 28 18:58:09 <hxka> *Oh, nice
Mar 28 18:58:35 <DocScrutinizer05> actually camera is one of our major headaches
Mar 28 18:59:24 <DocScrutinizer05> but for quite obvious reasons we don't want to use another camera
Mar 28 18:59:47 <DocScrutinizer05> camera drivers are always proprietary - or crap
Mar 28 19:00:36 <DocScrutinizer05> the camera manufs not only sell the hw but also their knowhow about normalizing and improving the image by postprocessing
Mar 28 19:40:07 <ecc3g> hmm... netpbm probably has enough to postprocess and can safely be run on the n900... running gimp on the n900 would be quite a feat...
Mar 28 19:44:11 <Sicelo> a feat that is being done. gimp works just fine on N900
Mar 28 19:50:32 <ecc3g> can you actually work on something without going OOM?
Mar 28 19:51:24 <DocScrutinizer05> huh?
Mar 28 19:52:04 <DocScrutinizer05> if 1GB doesn't suffice: swapon /dev/mmc1p3
Mar 28 19:52:38 <DocScrutinizer05> simply add swap
Mar 28 20:00:48 <Sicelo> i've never got OOM with gimp on N900. granted, i was not doing too fancy stuff
Mar 28 20:04:34 <Agge> ~flasher
Mar 28 20:04:35 <infobot> flasher is probably at http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz (also .exe!), or http://www.chakra-project.org/ccr/packages.php?ID=5027 or generally http://www.google.com/search?q=maemo_flasher-3.5_2.5.2.2.tar.gz.   HARMattan(N9): https://aur.archlinux.org/packages/fl/flasher-harmattan/flasher-harmattan.tar.gz, or -- list of filenames/md5sums: http://pastebin.com/sYKdNJSH, or http://galif.eu/nokia/
Mar 28 20:05:05 <Agge> ~flashing
Mar 28 20:05:06 <infobot> maemo-flashing is, like, http://wiki.maemo.org/Updating_the_tablet_firmware
Mar 28 20:11:14 <Agge> ~emmc
Mar 28 20:11:15 <infobot> rumour has it, emmc is magnet:?xt=urn:btih:402fb5cc8a48ecbc18a77c9cf70d869a775bcf53&dn=RX-51%5F2009SE%5F10.2010.13-2.VANILLA%5FPR%5FEMMC%5FMR0%5FARM.bin or https://dl.dropboxusercontent.com/u/4105928/RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.torrent, or http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/5/--FID--A0A22YHFSICNA/--LID--FiRe1275051276916/AE98ED9D_RX-51_2009SE_10.2010.13-2.CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin
Mar 28 20:12:47 <Agge> ~fiasko
Mar 28 20:13:00 <Agge> ~combined
Mar 28 20:13:00 <infobot> combined is probably the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, or http://galif.eu/nokia/
Mar 28 20:44:21 <sombragris> thanks everyone
Mar 28 20:44:24 <sombragris> logging off
Mar 28 21:32:19 <Agge> ~cssu
Mar 28 21:32:21 <infobot> i heard cssu is http://wiki.maemo.org/Community_SSU
Mar 28 22:19:29 <Agge> ~ssu
Mar 28 22:19:29 <infobot> extra, extra, read all about it, ssu is http://wiki.maemo.org/SSU
Mar 28 22:21:02 <Agge> DocScrutinizer05: what is the repository for upgrading to the latest oficial nokia verion of maemo?
Mar 28 22:21:22 <Agge> downloads.maemo.nokia.com/fremantle/  ??
Mar 28 22:44:53 <DocScrutinizer05> well, prolly SSU
Mar 28 22:44:59 <DocScrutinizer05> Nokia SSU
Mar 28 22:45:26 <DocScrutinizer05> but honestly who would update nowadays?
Mar 28 22:45:48 <DocScrutinizer05> who would be silly enough to flash a PR1.2 or whatever and then update?
Mar 28 22:45:54 <DocScrutinizer05> ~pr131
Mar 28 22:45:55 <infobot> somebody said combined was the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, or http://galif.eu/nokia/
Mar 28 22:46:20 <DocScrutinizer05> ^^^ *this* is the most recent official Nokia fremantle release
Mar 28 22:48:20 <DocScrutinizer05> maybe when you didn't look at your N900 sitting in the shelf for 2 years, then you actually could upgrade from PR1.2 which you maybe still are running on that dusty N900, by using Nokia's SSU repo
Mar 28 22:49:17 <honestly> Does Nokia's SSU repo still exist?
Mar 28 22:51:01 <DocScrutinizer05> name: "Nokia Systemsoftwareaktualisierungen", internet addr: "https://downloads.maemo.nokia.com/fremantle/ssu/mr0", distribution: "./"
Mar 28 22:51:46 <DocScrutinizer05> and yes, I think if it wouldn't exist then HAM would throw an error from it
Mar 28 23:45:06 <Maxdamantus> Hmm .. when I booted into my debian installation the charge function seems to just work.
Mar 28 23:45:12 * Maxdamantus wonders what's making it work.
Mar 28 23:45:40 * Maxdamantus thought userspace had to do something to enable it (other than just load the module)
Mar 28 23:45:56 <Maxdamantus> maybe that was because there wasn't a kernel module for it, dunno.
Mar 28 23:54:16 <DocScrutinizer05> what makes you believe it works?
Mar 28 23:55:27 <DocScrutinizer05> please don't say "icon" or "LED"
Mar 29 00:15:47 <Maxdamantus> LED :\
Mar 29 00:16:08 <Maxdamantus> Okay, so probably doesn't.
Mar 29 00:37:06 <ShadowJK> solid shining led indicates the charger is without software control
Mar 29 00:37:34 <ShadowJK> Typically when the charger is under software control, the software disables the led, and makes it pulsate instead
Mar 29 00:38:17 <ShadowJK> (though amusingly, as the LED controller is so programmable, it will keep blinking the led long after the software crashes)
Mar 29 01:24:30 <Maxdamantus> # amixer scontents | grep '^Simple mixer control' | wc -l
Mar 29 01:24:30 <Maxdamantus> 187
Mar 29 01:24:42 <Maxdamantus> 187 controls :\
Mar 29 01:28:47 <DocScrutinizer05> sounds about right
Mar 29 01:29:03 <DocScrutinizer05> ~charge21
Mar 29 01:29:09 <kerio> welcome to pulseaudio
Mar 29 01:29:14 <DocScrutinizer05> nope
Mar 29 01:29:18 <DocScrutinizer05> that's alsa
Mar 29 01:29:23 <kerio> mh
Mar 29 01:29:27 <kerio> hw mixer?
Mar 29 01:29:30 <DocScrutinizer05> yep
Mar 29 01:32:11 <Maxdamantus> alsa also does sw mixing.
Mar 29 01:33:12 <DocScrutinizer05> mixer is a generic term in this context
Mar 29 01:33:49 <DocScrutinizer05> I anyway wonder where's your -c 0 parameter for amixer
Mar 29 01:33:52 <Maxdamantus> Oh, thought it was referring to the act of combining multiple audio streams into one.
Mar 29 01:34:09 <Maxdamantus> I don't think you need it for listing mixers.
Mar 29 01:34:14 <DocScrutinizer05> it does this as well, for some pathes
Mar 29 01:34:34 <Maxdamantus> it's meant to do it automatically now.
Mar 29 01:34:58 <DocScrutinizer05> ~ # amixer scontents | grep '^Simple mixer control' | wc -l
Mar 29 01:35:00 <DocScrutinizer05> 2
Mar 29 01:35:21 <DocScrutinizer05> ~ # amixer -c 0 scontents | grep '^Simple mixer control' | wc -l
Mar 29 01:35:22 <DocScrutinizer05> 66
Mar 29 01:35:34 <DocScrutinizer05> err
Mar 29 01:35:57 <DocScrutinizer05> ~ # amixer -c 0 scontents | grep -c '^Simple mixer control'     
Mar 29 01:35:58 <DocScrutinizer05> 66
Mar 29 01:36:08 <Maxdamantus> I only see one card with the 3.14 kernel.
Mar 29 01:36:26 <DocScrutinizer05> ohmy
Mar 29 01:36:40 <Maxdamantus> is the default one in maemo routed to pulseaudio or something?
Mar 29 01:37:13 <Maxdamantus> (so not an actual card)
Mar 29 01:37:17 <DocScrutinizer05> ~ # amixer -c 0 scontrols|wc -l
Mar 29 01:37:18 <DocScrutinizer05> 66
Mar 29 01:37:41 <DocScrutinizer05> err yep, prolly
Mar 29 01:37:51 <Maxdamantus> Yeah, it is.
Mar 29 01:38:04 <Maxdamantus> ctl.!default { type pulse .. }
Mar 29 01:38:13 <DocScrutinizer05> ~ # amixer -c 0 controls|wc -l 
Mar 29 01:38:14 <DocScrutinizer05> 71
Mar 29 01:38:42 <DocScrutinizer05> ~ # amixer controls|wc -l     
Mar 29 01:38:43 * Maxdamantus is trying to figure out what control to use to make the headphone jack work.
Mar 29 01:38:44 <DocScrutinizer05> 4
Mar 29 01:38:51 <DocScrutinizer05> haha
Mar 29 01:39:34 <DocScrutinizer05> "make work2 is a funny goal
Mar 29 01:40:06 <DocScrutinizer05> I'd say it needs at least 5..10 comtrols in right position, to "make hs jack work"
Mar 29 01:40:37 <DocScrutinizer05> the joy of mixers
Mar 29 01:41:13 <Maxdamantus> also wonder why mplayer plays back music slowly.
Mar 29 01:41:39 <Maxdamantus> Presumably not a CPU usage issue, as I imagine that'd make it jitter rather than play slowly.
Mar 29 01:42:02 <DocScrutinizer05> here: OMAP SSI out (if that's what you want), then 320aic34 or what's it called, and finally the hs-amp which has its own I2C control
Mar 29 01:42:50 <DocScrutinizer05> tuning also too low?
Mar 29 01:43:09 <Maxdamantus> tuning?
Mar 29 01:43:15 <DocScrutinizer05> pitch?
Mar 29 01:43:19 <Maxdamantus> Yes.
Mar 29 01:43:35 <Maxdamantus> so it's like the actual wave is longer.
Mar 29 01:43:42 <DocScrutinizer05> then prolly the "audiocard" clock is lower than mplayer assumes
Mar 29 01:44:27 <DocScrutinizer05> try aplay
Mar 29 01:45:39 <Maxdamantus> same thing happens with aplay
Mar 29 01:45:40 <DocScrutinizer05> aplay -D <alsadevice> -vv sound.wav
Mar 29 01:45:46 <Maxdamantus> but adding `-af resample=48000` to mplayer makes it sound better.
Mar 29 01:46:24 <DocScrutinizer05> yep, N900 has fixed audio clock of 48k iirc
Mar 29 01:46:28 <Maxdamantus> maybe alsa isn't resampling (the source is 44.1 kHz)
Mar 29 01:46:32 <Maxdamantus> Hm.
Mar 29 01:46:36 <DocScrutinizer05> exactly
Mar 29 01:47:10 <DocScrutinizer05> depends on your audiodev
Mar 29 01:47:14 <Maxdamantus> Mk, guess that makes sense.
Mar 29 01:47:18 <DocScrutinizer05> try plughw:0.0
Mar 29 01:47:43 <DocScrutinizer05> maybe your !default def is odd
Mar 29 01:47:45 <Maxdamantus> but would've expected it to fail saying 44.1 kHz isn't supported by the output or something, maybe the driver's just not mature enough to do that yet.
Mar 29 01:48:08 <DocScrutinizer05> aplay -vv
Mar 29 01:48:22 <DocScrutinizer05> pastebin
Mar 29 01:49:15 <Maxdamantus> https://gist.githubusercontent.com/Maxdamantus/74dcacb75d126636a205/raw/02e08b30b9595b409dfda163cc0dec4b1ca29c51/gistfile1.txt
Mar 29 01:49:53 <DocScrutinizer05>   rate         : 44100
Mar 29 01:50:21 <DocScrutinizer05> you shouldn't directly drive the hw:0.0 audio device
Mar 29 01:50:35 <DocScrutinizer05> try plughw:0.0
Mar 29 01:50:48 <Maxdamantus> invalid value for card.
Mar 29 01:51:08 <Maxdamantus> What's plughw meant to be?
Mar 29 01:51:32 <DocScrutinizer05> plughw should be a combo of plug and hw
Mar 29 01:51:51 <DocScrutinizer05> plug is a universal resampling and mapping/convertig plugin
Mar 29 01:52:49 <Maxdamantus> Ah.
Mar 29 01:52:53 <DocScrutinizer05> prolly fremantle never heard of it and does everything in PolypAudio
Mar 29 01:53:41 <Maxdamantus> I'm not in freemantle.
Mar 29 01:53:51 <Maxdamantus> in a fairly plain Debian.
Mar 29 01:54:16 * Maxdamantus will add a plug device.
Mar 29 01:55:42 <DocScrutinizer05> http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html
Mar 29 01:57:14 <Maxdamantus> works with dmix
Mar 29 01:57:42 <DocScrutinizer05> Automatic conversion plugin
Mar 29 01:57:44 <Maxdamantus> just adding a plug didn't seem to do anything, but I don't really understand it, so might've used it wrong.
Mar 29 01:57:57 <DocScrutinizer05> pcm.name {
Mar 29 01:57:58 <DocScrutinizer05>         type plug               # Automatic conversion PCM
Mar 29 01:58:20 <Maxdamantus> Yeah, that's what I had, then slave.pcm "hw:0,0"
Mar 29 01:58:35 <Maxdamantus> now I have slave.pcm "main"
Mar 29 01:58:41 <Maxdamantus> and pcm.main a dmix thing
Mar 29 01:59:06 <Maxdamantus> (didn't need to specify the rate—it must've at least figured that out automatically when creating the dmix device)
Mar 29 02:00:12 <Maxdamantus> ah, so you specify the rate in the slave configuration.
Mar 29 02:01:28 <Maxdamantus> and that works for multiple programs already, so don't need dmix, which would presumably have been a small amount of overhead.
Mar 29 02:01:28 <DocScrutinizer05> grep plughw -A 50 /usr/share/alsa/alsa.conf
Mar 29 02:02:43 <Maxdamantus> Mm .. there's something there.
Mar 29 02:03:01 <DocScrutinizer05> http://privatepaste.com/4c1c8d9bd5
Mar 29 02:04:00 <DocScrutinizer05> http://privatepaste.com/716253453e
Mar 29 02:06:07 <Maxdamantus> Yeah, mine's the same for pcm.plughw at least.
Mar 29 02:06:30 <Maxdamantus> anyway, it all works by just adding the plug to /etc/asound.conf
Mar 29 02:06:41 <Maxdamantus> can make that pcm.!default there too.
Mar 29 02:08:47 <DocScrutinizer05> IroN900:~# diff /usr/share/alsa/alsa.conf.origJR /usr/share/alsa/alsa.conf
Mar 29 02:08:48 <DocScrutinizer05> 59c59
Mar 29 02:08:50 <DocScrutinizer05> < defaults.namehint.extended off
Mar 29 02:08:51 <DocScrutinizer05> ---
Mar 29 02:08:53 <DocScrutinizer05> > defaults.namehint.extended on
Mar 29 02:08:54 <DocScrutinizer05> ;-)
Mar 29 02:10:42 <DocScrutinizer05> plughw:0.0 is same as plug:'hw:0.0'
Mar 29 02:11:49 <DocScrutinizer05> the alsa plugin stack is basically just a set of nested "function calls", with parameters
Mar 29 02:11:59 <Maxdamantus> well, both of them seem to exist, but using them just says "Invalid value for card"
Mar 29 02:12:30 <DocScrutinizer05> yeah, is PA started?
Mar 29 02:12:35 <Maxdamantus> No.
Mar 29 02:12:53 <DocScrutinizer05> hmm, hw:0,0 ?
Mar 29 02:13:19 <Maxdamantus> ah, that doesn't work either.
Mar 29 02:13:20 <DocScrutinizer05> dunno, there been a catch but I forgot it, it's a known gotcha
Mar 29 02:13:34 <Maxdamantus> ah, should be card 1
Mar 29 02:13:37 <Maxdamantus> heh
Mar 29 02:13:42 <DocScrutinizer05> maybe
Mar 29 02:14:52 <DocScrutinizer05> -vv for aplay help a lot to understand plugin stack and what it does
Mar 29 02:15:05 <DocScrutinizer05> aplay -l and aplay -L also helps
Mar 29 02:15:09 <Maxdamantus> eh, no, should be card 0.
Mar 29 02:15:46 <Maxdamantus> I used `pcm.main.slave.pcm "hw:0,0"` as part of the dmix thing and it worked.
Mar 29 02:16:02 <DocScrutinizer05> http://privatepaste.com/ba05eb5b5a
Mar 29 02:16:12 <Maxdamantus> agh, accidentally typed a . instead of ,
Mar 29 02:16:31 <Maxdamantus> so plughw:0,0 does work, but it's still the wrong rate.
Mar 29 02:16:44 <Maxdamantus> when I made the plug device in /etc/asound.conf I had to specify the rate.
Mar 29 02:16:49 <DocScrutinizer05> slave no proper rate definition?
Mar 29 02:17:29 <DocScrutinizer05> hw:0,0 should have rate 48000
Mar 29 02:17:35 <DocScrutinizer05> afaik
Mar 29 02:17:40 <Maxdamantus> How do you find out?
Mar 29 02:18:49 <Maxdamantus> I suspect the driver isn't reporting it as having that rate, or is reporting it as having that rate and others, while it only actually supports that rate.
Mar 29 02:19:18 <Maxdamantus> but not that familiar with alsa, so my suspiciouns aren't strong.
Mar 29 02:19:25 <DocScrutinizer05> there's only defaults.pcm.dmix.rate 48000
Mar 29 02:19:42 <Maxdamantus> Not using dmix atm
Mar 29 02:19:45 <DocScrutinizer05> try slave dmix
Mar 29 02:19:57 <Maxdamantus> dmix works, but so does plug, as long as I specify the rate.
Mar 29 02:20:05 <DocScrutinizer05> sure
Mar 29 02:20:08 <Maxdamantus> pcm.!default.slave.rate 48000
Mar 29 02:20:15 <DocScrutinizer05> use slave dmix for plug
Mar 29 02:20:30 <DocScrutinizer05> hmm
Mar 29 02:21:05 <Maxdamantus> using slave.pcm "hw:0,0"
Mar 29 02:21:21 <DocScrutinizer05> yep, and it seems that has no proper rate spec
Mar 29 02:21:39 <DocScrutinizer05> while dmix has
Mar 29 02:21:41 <Maxdamantus> Oh, I do need dmix to use multiple programs at once.
Mar 29 02:21:46 <DocScrutinizer05> yes
Mar 29 02:22:23 <DocScrutinizer05> so try:  plug:dmix as device
Mar 29 02:22:42 <DocScrutinizer05> or plug:'dmix:0,0'
Mar 29 02:23:10 <Maxdamantus> Hm. That works.
Mar 29 02:23:15 <DocScrutinizer05> I'm not fluent in this stuff anymore
Mar 29 02:23:19 <Maxdamantus> without anything in /etc/asound.conf
Mar 29 02:23:36 <Maxdamantus> the first one does
Mar 29 02:24:03 <DocScrutinizer05> etc/asound.conf is just a extension to /usr/share/alsa/alsa.conf
Mar 29 02:24:34 <Maxdamantus> Yeah, suspected that.
Mar 29 02:24:40 <DocScrutinizer05> basically you shouldn't need etc/asound.conf
Mar 29 02:24:42 <Maxdamantus> just meant "without any extra configuration"
Mar 29 02:25:00 <Maxdamantus> what about for configuring a default device?
Mar 29 02:25:01 <DocScrutinizer05> nor .asoundrc
Mar 29 02:25:23 <Maxdamantus> if I leave it empty, just playing stuff with mplayer etc will work at the wrong rate, unless I specify a device.
Mar 29 02:25:33 <sono> http://fc01.deviantart.net/fs71/i/2013/314/f/e/world_no_tobacco_day_by_sternen_gaukler-d5wrgxe.jpg
Mar 29 02:25:37 <sono> oops
Mar 29 02:25:38 <sono> sorry about that.
Mar 29 02:26:05 <Maxdamantus> can instead have pcm.!default { type plug; slave.pcm "dmix" }
Mar 29 02:28:06 <DocScrutinizer05> Maxdamantus: you might find some useful hints/inspirations in https://groups.yahoo.com/neo/groups/twinklephone/conversations/topics/1731
Mar 29 02:29:06 <Maxdamantus> Creating a separate device and control for the ringer?
Mar 29 02:29:12 <Maxdamantus> Yeah, I'd've done something like that.
Mar 29 02:32:15 <DocScrutinizer05> yeah, I created a volume control for ringer, in alsamixer
Mar 29 02:32:46 <DocScrutinizer05> but it also shows some details about how to create a alsa plugin, and how to define slave
Mar 29 02:33:49 <DocScrutinizer05> nothing particularly exciting, once you read the ALSA plugin wikipage
Mar 29 02:33:58 <DocScrutinizer05> http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html
Mar 29 02:34:24 <Maxdamantus> Yeah, I figured that out when alsa on my new computer (Haswell) wouldn't mix sound automatically for some reason.
Mar 29 02:35:15 <DocScrutinizer05> wow, another one who actually learned some ALSA bits :-)
Mar 29 02:35:39 <Maxdamantus> some
Mar 29 02:35:41 <DocScrutinizer05> I thought I'm the only one who ever did
Mar 29 02:36:36 <Maxdamantus> eh, the orange LED went off.
Mar 29 02:36:44 <DocScrutinizer05> well, then you're set with the info that N900 hw can only do rate=48000
Mar 29 02:36:45 <Maxdamantus> Maybe it was charging.
Mar 29 02:36:53 <Maxdamantus> or maybe it means it's about to run out of battery.
Mar 29 02:37:10 <DocScrutinizer05> it tries to "charge" to 3.6V, and it stops after 30min
Mar 29 02:37:16 <DocScrutinizer05> ~flatbatrecover
Mar 29 02:37:17 <infobot> Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!.
Mar 29 02:37:36 <Maxdamantus> the battery driver does, automatically?
Mar 29 02:37:41 <Maxdamantus> (without userspace intervention)
Mar 29 02:37:43 <DocScrutinizer05> the chip does
Mar 29 02:37:47 <Maxdamantus> Oh.
Mar 29 02:37:55 <DocScrutinizer05> NB 3.6V!
Mar 29 02:38:12 <DocScrutinizer05> which is closer to empty than to charged
Mar 29 02:38:26 <Maxdamantus> it was longer than 30 minutes.
Mar 29 02:38:38 <Maxdamantus> a few hours
Mar 29 02:38:48 <DocScrutinizer05> the chip timer is very random
Mar 29 02:38:54 <DocScrutinizer05> a few hours?
Mar 29 02:38:57 <DocScrutinizer05> duh!
Mar 29 02:39:29 <DocScrutinizer05> well, dunno which kernel modules you got
Mar 29 02:40:23 <Maxdamantus> there were two battery-related modules in /lib/modules/`uname -r`, didn't check which were loaded.
Mar 29 02:41:22 <DocScrutinizer05> as soon as something talks to chip via I2C, it goes into guided mode / slave mode, which means it needs a watchdog tickle every 15s, otherwise it resets. In that mode the chip can get configured to charge to higher volatge, arbitrary current, and you can control the LED
Mar 29 02:42:00 <DocScrutinizer05> he chip is bq24150
Mar 29 02:42:28 <Maxdamantus> Mm .. it must've been charging .. rebooting back into Maemo shows 91% (the usual maximum charge)
Mar 29 02:42:30 <DocScrutinizer05> maybe pali has upstreamed the kernel module 
Mar 29 02:43:48 <DocScrutinizer05> afk
Mar 29 02:43:51 <DocScrutinizer05> o/
**** ENDING LOGGING AT Sat Mar 29 03:00:00 2014