**** BEGIN LOGGING AT Sun Jul 30 03:00:01 2017 Jul 30 10:01:43 Default maemo doesn't use the hardware battery fuel gauge chip really... That's why it works in stock maemo. Jul 30 10:02:02 ? Jul 30 10:02:18 you mean it doesn't use the capacity reported by gasgauge Jul 30 10:02:47 AFter getting the hardware chip (bq27200) calibrated, it should provide reasonable data to other operating systems as well.. However, that it says 0 is quite peculiar, usually what happens is that you get over-estimation of capacity :) Jul 30 10:02:52 yes I mean that Jul 30 10:03:04 But maybe the kernel modules and such just report 0 for "unknown" Jul 30 16:38:22 DocScrutinizer05: fm transmitter in n900 is doing something nasty, once I start it and it transmit some periodic beep Jul 30 16:38:37 it can be detected only when n900 does not play any sound/music Jul 30 16:38:46 pali: it does it until you start playing something Jul 30 16:39:01 i guess for making detecting n900 easier Jul 30 16:39:39 really? I think I can detect that beep also when n900 play some music... Jul 30 16:39:51 what about when you play silence? Jul 30 16:39:52 I will look into rtl-sdr dump what it is Jul 30 16:39:54 or close to silence? Jul 30 16:40:15 i think it stops then Jul 30 16:48:30 i also thought the beeps were 'correct.' i don't recall hearing them during active transmission (and i used it today) Jul 30 16:49:48 https://talk.maemo.org/archive/index.php/t-42766.html Jul 30 16:51:16 nice, i didnt know those beeps are configurable Jul 30 16:52:00 looks like, yes beeps disappear when playing something Jul 30 16:53:50 and there is something else with transmitter, it changes frequency in time by 2.8kHz offset Jul 30 16:54:37 strange Jul 30 16:54:41 maybe that's that deviation param? Jul 30 16:56:18 when I set to transmit at 105.8MHz then I see it in 105,8047MHz and frequency starts changing until it is 105,8016MHz Jul 30 16:57:16 and after some time it changes back to 105,804... and I see in time graph that base frequency is really changing... Jul 30 16:57:49 some spreadspectrum algo? or just bad design somewhere? Jul 30 16:57:56 and I'm not able to see this problem in other FM transmitters, so it is for sure problem in n900 transmitter and not in my receiver Jul 30 16:59:43 I believe the beep is an intentional feature, after a while of beeping the fm transmitter is switched off. Like a standby mode. Jul 30 17:00:29 see: https://imgur.com/a/eY5uq Jul 30 17:01:14 it's not vertical line Jul 30 17:01:36 yes Jul 30 17:02:36 maybe n900 fm transmitter is not able to fix fm frequency?? Jul 30 17:03:04 "good enough technology [tm]" ;) Jul 30 17:04:27 hmm, is that reproducible on multiple devices I wonder? Jul 30 17:04:49 What time period is that over? Jul 30 17:05:28 that yellow dots are beeps Jul 30 17:05:52 in the middle should be mono part of sound Jul 30 17:10:17 oh I see Jul 30 17:46:28 sicelo: why the unbearable archive instead of https://talk.maemo.org/showthread?t=42766 Jul 30 17:48:13 Pali: FM channels are 50kHu wide in Germany, maybe 25kHz in USA (not sure). Anyway a 2.x kHz drift is irrelevant Jul 30 17:48:56 or was it 100kHz in EU, 50kHz in USA? Jul 30 17:49:29 seems that gnuradio and rtl_fm do not have a problem with 2kHz drift... Jul 30 17:49:31 but it is normal? Jul 30 17:50:21 1kHz drift in 100MHz is 0.01 promille, not even TCOs can do that good Jul 30 17:50:51 that picture of signal looks strange... it is not vertical line, nor continuous Jul 30 17:52:24 non-issue Jul 30 17:52:48 read the datasheet of FM-TX Jul 30 17:55:34 I'm not sure which timebase/oscillator the chip uses, but for sure it's no specially temperature compensated oscillator, so drifts are expected Jul 30 17:56:07 particularly when your N900 warms up during usage Jul 30 17:57:35 ok Jul 30 17:58:58 anyway, it is possible to use ordinary telescopic antenna for receiving CB? Jul 30 18:01:42 sure Jul 30 18:01:51 every walkietalkie does Jul 30 18:02:53 but you can't use RTL dongle plus antemma stb, it starts at 5ßMHz iirc Jul 30 18:03:04 50MHz Jul 30 18:03:27 CB is 27MHz Jul 30 18:04:16 so you want an antenna of at least 1m length, and elctrical inductive compensation Jul 30 18:21:46 rtl-sdr with R820T has range 24 – 1766 MHz with experimental 500 kHz – 28.8 MHz and up to 1864 MHz Jul 30 18:36:01 wow Jul 30 18:37:05 500k - 28.8M is mere I/Q direct sampling, the results are questionable particularly for sensitivity Jul 30 18:37:18 afaik Jul 30 18:38:39 but for tests you can get away with it for sure, I.E. when the distance from your TX to RTL antenna are less than 1M Jul 30 18:38:42 1m* Jul 30 18:40:12 generally sensitivity of rtl is a problem Jul 30 18:42:03 then you also have poor mirror frequency suppression, and also problems with aliasing Jul 30 18:42:37 input signal filtering in RTL is basically non-existent Jul 30 18:43:20 ..antenna connector, clock drift, temperature.. Jul 30 18:43:59 yeah, well it costs like 10 bucks, what do you expect? Jul 30 18:45:16 in fact, noelec version fixes many of the problems Jul 30 19:09:49 ok, I stand corrected. http://www.rtl-sdr.com/wp-content/uploads/2013/04/R820T_datasheet-Non_R-20111130_unlocked1.pdf says it gas input filter with image rejection of 65dBc Jul 30 19:09:55 has* Jul 30 19:14:13 so >>input signal filtering in RTL is basically non-existent<< is an incorrect statement Jul 30 20:08:36 LOL! Opensuse bash does autocompletion from "scp x1 neo900:/ho" to "scp x1 neo900:/home/" and then on to the actually existing user homedirs - heck this does indeed use stealth remote login to destination to autocomplete Jul 30 20:13:34 ubuntu is doing same for a longer time Jul 30 20:14:03 it is great when user has configured ssh-agent in -c mode :D Jul 30 20:14:43 every tab autocompletion is subject to manual confirmation of usage of ssh key... Jul 30 20:24:13 LOL Jul 30 20:24:40 may I quote you? Jul 30 20:47:08 less +'/_scp_remote_files()' /usr/share/bash-completion/completions/scp Jul 30 20:55:44 I guess the lines like "files=$( ssh -o 'Batchmode yes' $userhost ..." could use some watchdog to catch ssh locking up during log in Jul 30 20:56:04 seen this more than once **** ENDING LOGGING AT Mon Jul 31 03:00:01 2017