| 01:23.15 | *** join/#maemo auenf (David@DC-54-87.bpb.bigpond.com) |
| 01:26.46 | *** join/#maemo Natch (~Natch@h-155-122.a444.priv.bahnhof.se) |
| 01:28.13 | *** join/#maemo auenf (David@DC-54-87.bpb.bigpond.com) |
| 01:35.33 | *** join/#maemo eMHa__ (~mh@p579DB1D2.dip0.t-ipconnect.de) |
| 01:36.55 | *** join/#maemo krnlyng (~liar@77.116.12.160.wireless.dyn.drei.com) |
| 01:40.45 | *** join/#maemo robotanarchy_ (~robotanar@f049058221.adsl.alicedsl.de) |
| 01:55.40 | *** join/#maemo robbiethe1st (~robbiethe@104.240.26.124) |
| 02:20.53 | *** join/#maemo auenf (David@120.155.20.47) |
| 02:24.55 | *** join/#maemo auenfx4 (David@DC-20-128.bpb.bigpond.com) |
| 02:28.16 | *** join/#maemo auenf (David@DCL-5-89.bpb.bigpond.com) |
| 02:32.48 | *** join/#maemo vakkov (~vakkov@ic-s221n133.brunel.ac.uk) |
| 02:33.30 | *** join/#maemo azkay_ (~azkay@14-202-56-178.tpgi.com.au) |
| 02:36.59 | *** join/#maemo auenf (David@DCL-5-89.bpb.bigpond.com) |
| 02:47.02 | *** join/#maemo auenf (David@DCL-5-89.bpb.bigpond.com) |
| 03:00.12 | azkay_ | i.imgur.com/BjJU9Pi.jpg someone should throw this into an n900 |
| 03:02.18 | *** join/#maemo lxp1 (~lxp@unaffiliated/lxp) |
| 03:17.05 | *** join/#maemo netkat (~me@80.79.126.176) |
| 03:21.04 | *** join/#maemo maemo_user (~smuxi@f055113217.adsl.alicedsl.de) |
| 03:22.58 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 03:35.06 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:01.19 | *** join/#maemo auenfx4 (David@DC-86-217.bpb.bigpond.com) |
| 04:38.37 | *** join/#maemo auenf (David@DC-86-217.bpb.bigpond.com) |
| 04:43.44 | *** join/#maemo auenfx4 (David@DC-116-25.bpb.bigpond.com) |
| 04:48.31 | *** join/#maemo auenf (David@DCL-104-130.bpb.bigpond.com) |
| 05:23.09 | *** join/#maemo auenf (David@DC-115-209.bpb.bigpond.com) |
| 05:38.31 | *** join/#maemo azkay_ (~azkay@14-202-56-178.tpgi.com.au) |
| 05:55.18 | *** join/#maemo azkay_ (~azkay@14-202-56-178.tpgi.com.au) |
| 05:58.50 | *** join/#maemo pagurus (~user@pD950F78E.dip0.t-ipconnect.de) |
| 06:32.41 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 06:44.57 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 06:44.59 | *** join/#maemo hashcore (~hashcore@unaffiliated/hashcore) |
| 06:52.52 | *** join/#maemo vectis3 (~user@79-65-226-52.host.pobb.as13285.net) |
| 06:55.12 | *** join/#maemo pagurus (~user@pD950F78E.dip0.t-ipconnect.de) |
| 07:06.01 | kerio | azkay_: april fools |
| 07:07.47 | *** join/#maemo futpib (~futpib@176.214.29.150) |
| 07:08.59 | *** join/#maemo bruce_lee (~neo@x590d0fde.dyn.telefonica.de) |
| 07:08.59 | *** join/#maemo bruce_lee (~neo@unaffiliated/bruce-lee/x-7462768) |
| 07:09.59 | azkay_ | :P |
| 07:13.45 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 07:20.42 | *** join/#maemo auenfx4 (David@DC-115-209.bpb.bigpond.com) |
| 07:47.09 | *** join/#maemo Kabouik (~quassel@147.99.219.229) |
| 07:52.06 | *** join/#maemo eMHa__ (~mh@185.36.21.1) |
| 08:29.10 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:36.38 | *** join/#maemo Vajb (~Vajb@85-76-83-184-nat.elisa-mobile.fi) |
| 08:51.19 | *** join/#maemo joga (EPGPp5kX@rikki.fi) |
| 08:53.25 | *** join/#maemo robink_ (~quassel@unaffilated/robink) |
| 08:58.34 | *** join/#maemo bruce_lee (~neo@unaffiliated/bruce-lee/x-7462768) |
| 09:09.20 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-oxlzmecvkauseanp) |
| 09:22.41 | *** join/#maemo auenf (David@DC-115-209.bpb.bigpond.com) |
| 09:51.00 | *** join/#maemo pagurus (~user@pD950F78E.dip0.t-ipconnect.de) |
| 10:03.54 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 10:08.24 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 10:09.13 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 10:58.03 | *** join/#maemo zGrr (~GrR@188.146.133.196.nat.umts.dynamic.t-mobile.pl) |
| 10:58.41 | zGrr | moin :) |
| 11:02.23 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 11:47.44 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 12:38.24 | *** join/#maemo liujian0012hn (~liu@42.49.144.223) |
| 12:55.45 | *** join/#maemo Oksana (~chatzilla@Maemo/community/ex-council/Wikiwide) |
| 12:57.49 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 13:02.31 | Sicelo | i am trying to connect my N900 to a bluetooth serial device (car obd scanner). i can successfully bind the port (rfcomm0). when i type in minicom, the LED on the scanner comes on. however i never get a reply for any command i send. i am quite sure baud rate is fine (9600 8N1) as per the documentation. Have also tried 38400. when i press the enter key, no LED comes up. i tried connecting to the device using android, and it works. however android apps don't |
| 13:03.58 | Sicelo | also, i have tried same from my 2nd N900, with exactly the same unhappy outcome |
| 13:04.58 | *** join/#maemo liu_ (~liu@42.49.144.223) |
| 13:05.13 | liu_ | n900 |
| 13:05.28 | Sicelo | yes, it is :) |
| 13:06.09 | liu_ | my english is bad |
| 13:08.07 | Sicelo | if you have a question, you can just ask. we will try to undersand |
| 13:08.20 | liu_ | I can't install to ForecaWeather. do you have ForecaWeatherdeb? |
| 13:08.44 | sixwheeledbeast | Sicelo: ELM OBD unit? I had fun getting mine to pair, but when I did works great with pyOBD |
| 13:09.20 | sixwheeledbeast | Wasn't Foreca Weather on Ovi? I have used OMWeather for a long time now |
| 13:10.11 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 13:10.19 | Sicelo | yes sixwheeledbeast. mine pairs fine. pyOBD connects and gets stuck after sending ATE0. so i thought to try it manually and see. unfortunately manually i have not had any success so far. works fine on my friend's android phone |
| 13:10.28 | liu_ | I from china . so I can't on ovi. |
| 13:11.30 | Sicelo | liu, make sure you have up-to-date repos. it is there |
| 13:12.03 | liu_ | OMWeather also bad |
| 13:12.32 | Sicelo | i'm talking about foreca |
| 13:13.05 | liu_ | Can't install foreca |
| 13:13.13 | sixwheeledbeast | Sounds like package management issue if you can't install anything. |
| 13:13.32 | liu_ | Network wall |
| 13:14.20 | liu_ | no , the others can be |
| 13:15.00 | liu_ | is network problems |
| 13:17.00 | Sicelo | http://maemo-repos.com/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/apps/ ... it's there |
| 13:17.02 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 13:19.07 | liu_ | thanks |
| 13:19.39 | Sicelo | sixwheeledbeast: still using pyobd? :) |
| 13:19.52 | Sicelo | thread basically "died" unfortunately |
| 13:20.35 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 13:20.39 | sixwheeledbeast | Sicelo: yep not regularly but every now and again for a long while. |
| 13:21.06 | sixwheeledbeast | you can see from the thread when I first used it |
| 13:21.33 | sixwheeledbeast | it's only a port, needs a lot of work to be n900 friendly imo |
| 13:22.29 | Sicelo | if you don't mind, you could test for me if minicom/screen can connect to it :) |
| 13:28.03 | sixwheeledbeast | Sicelo: I have to get back to work now, but if you want to send me some instructions of what you want to check and I'll try it later. |
| 13:28.25 | Sicelo | tranks. will let you know. |
| 13:30.19 | Sicelo | basically, as root, 'rfcomm bind 0 <bt_addr> 1' followed by 'minicom -D /dev/rfcomm0 -b 9600'. then you can try writing intp minicom the commands from tmo, such as ATZ,ATE0, etc |
| 13:31.48 | Sicelo | <PROTECTED> |
| 13:37.49 | *** join/#maemo jskarvad_ (jskarvad@redhat/jskarvad) |
| 13:38.06 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 13:41.27 | DocScrutinizer05 | Sicelo: check RTS/CTS and software flow control |
| 13:42.11 | DocScrutinizer05 | rather, uncheck both ;-) |
| 13:45.26 | Sicelo | i did. no luck :( |
| 13:48.23 | *** join/#maemo maemo_user_ (~smuxi@x4e3771d9.dyn.telefonica.de) |
| 13:52.13 | *** join/#maemo sunshavi (~user@190.235.18.236) |
| 13:57.26 | DocScrutinizer05 | try an electrical loopback - ooops this is BT not RS232 right? |
| 13:58.56 | DocScrutinizer05 | try ATE1 which enables echo on far end |
| 13:59.30 | DocScrutinizer05 | though I got NFC whats a ELM OBD unit |
| 14:00.10 | DocScrutinizer05 | engine canbus adapter? |
| 14:01.22 | Sicelo | DocScrutinizer05: yes. :) |
| 14:01.47 | DocScrutinizer05 | aah k |
| 14:02.15 | DocScrutinizer05 | I guess those critters can be very tricky |
| 14:02.29 | Sicelo | i'll try again |
| 14:02.57 | DocScrutinizer05 | AT cmdset is not exactly what canbus protocol speaks ;-) |
| 14:03.30 | DocScrutinizer05 | so it's prolly like a sort of "modem" I guess |
| 14:04.17 | DocScrutinizer05 | do you have a link to the tmo thread? |
| 14:04.44 | *** join/#maemo RedW (~redw@89-76-164-87.dynamic.chello.pl) |
| 14:07.08 | DocScrutinizer05 | aaaaaah! :-D >>On Board Diagnostics (OBD)<< |
| 14:08.23 | DocScrutinizer05 | http://www.elmelectronics.com/obdic.html |
| 14:10.05 | Sicelo | at, definitely |
| 14:14.01 | DocScrutinizer05 | yes, the interpreter chip speaks AT it seems |
| 14:14.30 | DocScrutinizer05 | there's a car manufacturer named "Saturn" ?? |
| 14:15.49 | DocScrutinizer05 | anyway elmelectronics looks like decent source of info, http://www.elmelectronics.com/obdhelp.html |
| 14:19.50 | DocScrutinizer05 | http://www.elmelectronics.com/DSheets/ELM322DS.pdf >> RS232 baud rate 9600 baud // Nominal data transfer rate when a 3.58 MHz crystal is used as the frequency reference. Data is transferred to and from the ELM322 with 8 data bits, no parity, and 1 stop bit (8 N 1).<< |
| 14:20.26 | DocScrutinizer05 | as standard as it possibly gets |
| 14:24.38 | DocScrutinizer05 | http://wstaw.org/m/2016/04/01/plasma-desktoplB2219.png |
| 14:27.44 | *** join/#maemo alien2003 (~alien@230.97.121.77.pool.smart.vn.ua) |
| 14:29.05 | alien2003 | Hi! Do you have MyDocs in ext3? I need some help with mounting |
| 14:31.06 | Sicelo | DocScrutinizer05: trying right now again. |
| 14:31.17 | DocScrutinizer05 | Sicelo: try ATI (Info) |
| 14:31.27 | alien2003 | Sicelo: can you pls give me your /usr/sbin/mmc-mount? |
| 14:31.32 | DocScrutinizer05 | or "Identify" |
| 14:31.43 | DocScrutinizer05 | ATI<cr> |
| 14:31.46 | Sicelo | alien2003: no ext3 here :) |
| 14:31.51 | alien2003 | sorry |
| 14:32.11 | alien2003 | I just need mmc-mount script to be capable to mount ext and vfat both. I have it broken :( |
| 14:33.01 | DocScrutinizer05 | alien2003: CSSU should take care, but... you prolly don't use CSSU krcv? |
| 14:33.28 | alien2003 | I use CSSU but I modified that file and now it can only mount ext3, not vfat |
| 14:33.53 | Sicelo | DocScrutinizer05: no response to any command. not even the > prompt (which does appear on the android) |
| 14:34.07 | DocScrutinizer05 | alien2003: usually you simply use "-t ext3" parameter to the mount command |
| 14:34.18 | alien2003 | DocScrutinizer05: I mean automount |
| 14:34.32 | alien2003 | I can mount it manually without any problems |
| 14:34.35 | Sicelo | however, as i type the characters, "a" "t" etc, the led on the scanner comes on to indicate it received the data |
| 14:34.53 | DocScrutinizer05 | try ATE1 |
| 14:35.06 | DocScrutinizer05 | upper case A snd T |
| 14:35.19 | DocScrutinizer05 | and use CR to end the line |
| 14:35.32 | DocScrutinizer05 | try ^J and ^M |
| 14:36.45 | DocScrutinizer05 | also make sure no other process has opened your interface device, use lsof|grep |
| 14:36.47 | Sicelo | no dicel actually there's absolutely no sign of life on pressing Enter, Ctrl+J, Ctrl+M |
| 14:39.06 | Sicelo | i will try on my computer when i'm back home. maybe n900 minicom has problem? not sure. but screen does't succeed either |
| 14:39.25 | Sicelo | nothing else using the device |
| 14:39.35 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 14:44.08 | alien2003 | can you pls pastebin me default CSSU's /usr/bin/mmc-mount file? |
| 14:46.20 | *** join/#maemo liujian0012hn (~liu@42.49.144.223) |
| 14:48.31 | alien2003 | just default file from CSSU |
| 15:07.35 | *** join/#maemo maemo_user (~smuxi@x4e3771d9.dyn.telefonica.de) |
| 15:10.12 | *** join/#maemo maemo_user (~smuxi@x4e3771d9.dyn.telefonica.de) |
| 15:20.06 | sixwheeledbeast | Sicelo: another thought is have you tried a different vehicle. |
| 15:25.52 | *** join/#maemo lobito (~lobito@190.177.192.117) |
| 15:27.10 | Sicelo | not yet. but for now i'm failing to connect even to the dongle itself (powered). i can connect just fine from the droid without being in a car |
| 15:35.30 | Sicelo | okay .. minicom on pc not successful either. absolutely weird |
| 15:37.36 | *** join/#maemo vahe (~funtoo@130.193.124.135) |
| 15:54.05 | sixwheeledbeast | I haven't got minicom installed I am also struggling to locate my OBD reader :S |
| 15:54.34 | sixwheeledbeast | If it will not work with pc there maybe more to it. |
| 15:55.16 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:57.35 | Sicelo | i don't understand what could be the cause. the OBD reader clearly does receive my input, but either doesn't reply, or 'something absorbs' them |
| 16:06.15 | DocScrutinizer05 | alien2003: http://maemo.cloud-7.de/maemo5/usr/sbin/mmc-rename.sh err wait... |
| 16:06.37 | alien2003 | DocScrutinizer05: I just fixed everything... |
| 16:06.43 | alien2003 | just reinstalled from scratch |
| 16:06.46 | alien2003 | thank you anyway |
| 16:08.05 | DocScrutinizer05 | http://maemo.cloud-7.de/maemo5/usr/sbin/mmc-mount |
| 16:10.59 | DocScrutinizer05 | wasted another 5.2MB of my tiny server space :-) |
| 16:11.13 | DocScrutinizer05 | <PROTECTED> |
| 16:21.03 | *** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com) |
| 16:35.43 | *** join/#maemo auenf (David@120.155.59.118) |
| 16:45.45 | *** join/#maemo Cor-Ai_ (~cor-ai@c-91efe655.06-922-7570702.cust.bredbandsbolaget.se) |
| 16:48.26 | *** join/#maemo auenf (David@120.155.78.138) |
| 16:53.19 | *** join/#maemo auenfx4 (David@120.155.5.230) |
| 17:04.25 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
| 17:08.07 | *** join/#maemo futpib (~futpib@176.214.18.173) |
| 17:16.36 | *** join/#maemo auenf (David@120.155.37.166) |
| 17:18.10 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 17:18.31 | *** join/#maemo zGrr (~GrR@188.146.71.19.nat.umts.dynamic.t-mobile.pl) |
| 17:26.42 | *** join/#maemo auenf (David@120.155.64.221) |
| 17:31.45 | *** join/#maemo auenf (David@120.155.64.221) |
| 17:32.06 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 17:42.27 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 17:47.06 | *** join/#maemo luke-jr_ (~luke-jr@unaffiliated/luke-jr) |
| 17:50.29 | luke-jr_ | wow, N900 shut down for heat |
| 17:53.06 | kerio | D: |
| 17:56.55 | kerio | DocScrutinizer05: how do i clear VDQ |
| 17:58.49 | *** join/#maemo valdyn (valdyn@server.kthread.org) |
| 17:59.45 | DocScrutinizer05 | clear? |
| 17:59.56 | DocScrutinizer05 | start charging |
| 18:01.54 | *** join/#maemo zGrr (~GrR@178235245220.warszawa.vectranet.pl) |
| 18:01.58 | DocScrutinizer05 | VDQ goes 1 on batt full and gets cleared whenever something messes with proper contiguous discharge until learning |
| 18:07.01 | *** join/#maemo auenfx4 (David@120.155.4.170) |
| 18:10.26 | *** join/#maemo auenf (David@120.155.1.19) |
| 18:10.57 | DocScrutinizer05 | https://www.youtube.com/watch?v=HMQkV5cTuoY |
| 18:11.03 | DocScrutinizer05 | oops echan |
| 18:12.57 | *** join/#maemo eMHa__ (~mh@p579DB1D2.dip0.t-ipconnect.de) |
| 18:15.19 | kerio | Last Measured Discharge (LMD): 1122.765 mAh |
| 18:15.25 | kerio | let's see what i get after this calibration cycle |
| 18:18.16 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
| 18:23.06 | Sicelo | sixwheeledbeast: got my pyobd semi-working by commenting out the ATE0 part of initialization. Not working so well yet though, but i can see a couple of sensors |
| 18:23.27 | Sicelo | still can't minicom though. wish i knew what i'm doing wrong |
| 18:24.14 | *** join/#maemo lobito (~lobito@190.177.199.141) |
| 18:26.10 | DocScrutinizer05 | minicom is a bitch |
| 18:28.46 | Sicelo | i've used it on N900 to go into a cisco router some years ago. i do think there's something i'm not doing right, but can't figure out why. pyobd uses 9600,8N1 the same as how i connect with minicom |
| 18:29.46 | kerio | DocScrutinizer05: charger plugged in but disabled causes like 50mA of current more |
| 18:30.32 | kerio | is that normal |
| 18:30.46 | DocScrutinizer05 | err yes |
| 18:30.59 | kerio | but where are the electrons going :< |
| 18:31.00 | DocScrutinizer05 | that's the friggin MUSB core and its busses |
| 18:31.19 | DocScrutinizer05 | aka activated USB |
| 18:31.58 | DocScrutinizer05 | I think there's a 'trick' to send MUSB to suspend again by "echo off >sys/dunnowhat" |
| 18:32.42 | DocScrutinizer05 | maybe even modprobe -r though I think USB is monolithic |
| 18:33.58 | *** join/#maemo auenfx4 (David@120.155.101.143) |
| 18:34.28 | DocScrutinizer05 | I think Pali knows more than me here |
| 18:35.32 | kerio | nah it's fine it's just weird |
| 18:35.39 | Pali | what me? :-) |
| 18:35.46 | DocScrutinizer05 | or check pali's hostmode, it tries to shut dowm musb core after hostmode disabled |
| 18:35.53 | DocScrutinizer05 | iirc |
| 18:36.07 | kerio | DocScrutinizer05: what kind of measured discharge am i looking at, at a constant 230mA draw? |
| 18:36.24 | DocScrutinizer05 | sorry please rephrase |
| 18:36.26 | kerio | is ~1200mAh at 230mA good? |
| 18:36.31 | DocScrutinizer05 | yes |
| 18:36.34 | kerio | :3 |
| 18:36.58 | kerio | why does my akku polarcell say "lithium polymer" on the label |
| 18:37.05 | DocScrutinizer05 | blabla |
| 18:37.43 | DocScrutinizer05 | I recently learnd they call cells LiPo now when the case is made of plastic ;-P |
| 18:38.10 | DocScrutinizer05 | or similar nonsense |
| 18:38.44 | DocScrutinizer05 | once LiPo was a cell chemistry variant |
| 18:40.08 | DocScrutinizer05 | >>The designation "lithium polymer" has caused confusion among battery users because it can be interpreted in two ways. Originally, "lithium polymer" represented a developing technology using a polymer electrolyte instead of the more common liquid electrolyte<< |
| 18:40.16 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Lithium_polymer_battery |
| 18:40.28 | kerio | ye that's what i was thinking of |
| 18:43.19 | DocScrutinizer05 | Pali: ((what me? :-) )) How to disable MUSB core after e.g. hostmode? |
| 18:43.32 | Pali | what is musb core? |
| 18:43.41 | Pali | or what do you mean by "disable", |
| 18:43.42 | Pali | ? |
| 18:43.52 | DocScrutinizer05 | the mentorgraphics shit state machine that controls the USB states |
| 18:44.08 | DocScrutinizer05 | it has a bus to CPU and a bus to PJY |
| 18:44.11 | *** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez) |
| 18:44.13 | DocScrutinizer05 | PHY even |
| 18:44.25 | Pali | rmmod all gadgets |
| 18:44.28 | kerio | can't we do that with the real cpu |
| 18:44.30 | DocScrutinizer05 | and all three (core and the 2 buses) eats 50mA |
| 18:44.35 | Pali | that could do all tricks :-) |
| 18:44.55 | Pali | and modprobe g_nokia back |
| 18:45.13 | DocScrutinizer05 | aaah so it loads g_nokia or whatever whenever there's 5V on VBUS? |
| 18:45.53 | kerio | i think that he means to unload them all |
| 18:46.00 | kerio | so there's nothing doing the detection |
| 18:46.01 | kerio | or something |
| 18:46.05 | DocScrutinizer05 | I thought there was a magic handle in /sys/bla/bla/*/power or sth |
| 18:46.28 | DocScrutinizer05 | kerio: yes, that's what I got |
| 18:48.07 | DocScrutinizer05 | Pali: do you recall the issue that device ate 50mA more after using hostmode, even when it been completely disabled? I think you found a cure for that |
| 18:48.38 | *** join/#maemo vakkov (~vakkov@ic-s221n133.brunel.ac.uk) |
| 18:48.51 | Pali | now I do not remember |
| 18:48.57 | Pali | maybe it was some softconnect |
| 18:49.00 | Pali | or vbus |
| 18:49.04 | Pali | or another sysfs entry |
| 18:49.37 | Pali | anyway, unloading and loading g_nokia fixing some problem with musb internal state |
| 18:49.57 | Pali | sometimes after turning host mode off, musb is in wrong state |
| 18:50.05 | Pali | and kernel write error messages to dmesg |
| 18:50.19 | Pali | reloading gadget fixes it |
| 18:55.17 | DocScrutinizer05 | aah ok |
| 18:56.03 | DocScrutinizer05 | thanks |
| 18:58.58 | kerio | this is just for vboost/host mode right |
| 18:59.03 | kerio | not for just simply disabling and reenabling the charget |
| 18:59.05 | kerio | charger |
| 19:04.02 | DocScrutinizer05 | it's not the disabling/re-enabling of BME that does this, it's the 5V on VBUS I think |
| 19:04.56 | DocScrutinizer05 | 5V on VBUS means either a charger or a PC host got connected, so to distinguish the two you need MUSB core |
| 19:05.39 | DocScrutinizer05 | particularly you need MUSB core to do ENUM on a possibly connected host |
| 19:06.35 | DocScrutinizer05 | actually the system *could* stop MUSB after detecting the D+/- short, but I dunno who detects it and if that system takes care about shutting down USB data |
| 19:06.54 | DocScrutinizer05 | most likely not when BME got stopped |
| 19:11.28 | Sicelo | Pali: with usb-mode, how would i enumerate additional devices i connect? or i have to use the /proc/something method? |
| 19:12.05 | Pali | additonal devices? nokia n900 has just one usb port, so you cannot connect more usb devices |
| 19:12.11 | Sicelo | and, did you find any further solutions for the stuck blue LED after deactivation of host mode? |
| 19:12.40 | Sicelo | if i connect a hub for example, then i need to enumerate the additional USB devices |
| 19:12.44 | Pali | blue led, no idea :-( I was not able to reproduce it on my n900 |
| 19:12.51 | *** join/#maemo luke-jr_ (~luke-jr@unaffiliated/luke-jr) |
| 19:13.02 | Pali | "if i connect a hub...", so you do not connect additinal device :-) |
| 19:13.08 | Pali | it is up to hub and hub driver |
| 19:13.45 | Pali | it do enumeration without any other other "hacks" in musb |
| 19:13.48 | Pali | so automatically |
| 19:14.01 | Pali | if not, then hub is buggy and you cannot do anything |
| 19:14.07 | Sicelo | okay. thanks. will test. i was just wondering. |
| 19:14.51 | Sicelo | in h-e-n there was an enumerate button, which i think sends an echo F to some location in /proc |
| 19:17.49 | DocScrutinizer05 | with a hub you don't need that since the data link to the hub is already installed |
| 19:18.10 | DocScrutinizer05 | I meant, you only need it when connecting the hub |
| 19:18.31 | Sicelo | i see. thanks for information |
| 19:23.06 | *** join/#maemo kraft (~kraft@gateway/shell/blinkenshell.org/x-ntgzdmonsksoxjas) |
| 20:06.29 | *** join/#maemo Cor-Ai (~cor-ai@c-91efe655.06-922-7570702.cust.bredbandsbolaget.se) |
| 20:10.29 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 20:21.06 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 20:31.37 | *** join/#maemo M4rtinK2 (~M4rtinK@77.48.149.46) |
| 20:32.10 | *** join/#maemo auenf (David@120.155.104.80) |
| 21:09.55 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-iduaztjwieoopwyp) |
| 22:06.16 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
| 22:14.18 | DocScrutinizer05 | Sicelo: stuck blue LED? |
| 22:21.39 | DocScrutinizer05 | Pali: how does your hostmode control the LED? via MCE dbus call for pattern? |
| 22:21.50 | Pali | mce dbus |
| 22:21.58 | DocScrutinizer05 | best practice |
| 22:22.08 | DocScrutinizer05 | :) |
| 22:22.38 | Pali | but when using bme replacement, then my usbmode does not touch led |
| 22:22.53 | Pali | bme replacement care of mce led dbus pattern |
| 22:22.54 | DocScrutinizer05 | does it wait until method call sends ack reply via dbus before process terminates? |
| 22:23.25 | Pali | yes, it must |
| 22:23.38 | Pali | this is how dbus method call works |
| 22:23.38 | DocScrutinizer05 | then I don't see how LED could possibly get stuck |
| 22:23.54 | Pali | I think there is some bug in mce |
| 22:24.00 | Pali | or race condition... |
| 22:24.00 | DocScrutinizer05 | possible |
| 22:24.13 | Pali | do not know what happen if you request led two times |
| 22:24.25 | Pali | if you need then to disable it two times too or not |
| 22:24.50 | DocScrutinizer05 | I think mce has a one element deep "stack" to resume previous state when a pattern gets discontinued |
| 22:25.21 | DocScrutinizer05 | not sure if it's deeper than just one element |
| 22:26.31 | Pali | if Sicelo can reproduce that bug, probably he needs to debug it too... |
| 22:28.05 | DocScrutinizer05 | a dmus-monitor >tracelog.txt should do |
| 22:28.20 | DocScrutinizer05 | dbus even# |
| 22:30.26 | Sicelo | i would have loved to. but all 3 batteries are bad now. device switches of within 2 minutes of hostmode. |
| 22:33.40 | DocScrutinizer05 | eeew |
| 22:34.14 | DocScrutinizer05 | batteries are rare and extremely expensive at your site, no? |
| 22:35.02 | DocScrutinizer05 | can' |
| 22:35.09 | Sicelo | good ones, yes. fake ones that last a month are in abundance :) |
| 22:35.18 | DocScrutinizer05 | t you get a used one which is still in good condition? |
| 22:36.12 | DocScrutinizer05 | also it's hot where you live? |
| 22:37.41 | Sicelo | not so hot, i'd say. interestingly the batteries last at least 8 hours continuous use per day, but die immediately on hostmode (high internal resistance, i assume) |
| 22:38.43 | DocScrutinizer05 | yes |
| 22:38.50 | DocScrutinizer05 | seems so |
| 22:39.33 | DocScrutinizer05 | could you run a bq27200.sh 10 >batlog.txt in parallel? |
| 22:40.04 | DocScrutinizer05 | with at least 15 minutes history before activating hostmode |
| 22:40.36 | DocScrutinizer05 | dunno if bq27200.sh works for your system |
| 22:40.53 | DocScrutinizer05 | (I.E. for the hostmode BME |
| 22:40.55 | DocScrutinizer05 | ) |
| 22:45.36 | *** join/#maemo auenfx4 (David@120.155.104.80) |
| 22:46.20 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
| 22:48.00 | Sicelo | i modified it to work. |
| 22:50.50 | DocScrutinizer05 | good |
| 22:51.57 | DocScrutinizer05 | I'm really interested how a batlog of a supposedly worn battery would look like, when said battery works even with backlight but fails during 2 minutes on hostmode |
| 23:19.47 | *** join/#maemo auenf (David@CPE-139-168-240-114.lns4.wel.bigpond.net.au) |
| 23:27.04 | *** join/#maemo auenf (David@DCL-11-208.bpb.bigpond.com) |
| 23:32.32 | kerio | Last Measured Discharge (LMD): 1212.9075 mAh |
| 23:32.45 | kerio | 1122 to 1212 |
| 23:33.08 | kerio | how much was the maximum increase? |
| 23:35.50 | *** join/#maemo cnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 23:37.00 | *** join/#maemo auenfx4 (David@DCL-11-208.bpb.bigpond.com) |
| 23:37.38 | *** join/#maemo liuhoujiang (~user@42.49.144.223) |
| 23:39.08 | liuhoujiang | k |
| 23:41.15 | *** join/#maemo liujian0012hn (~liu@42.49.144.223) |
| 23:43.16 | *** join/#maemo auenf (David@DCL-11-208.bpb.bigpond.com) |
| 23:48.10 | DocScrutinizer05 | kerio: iirc 1/8 |
| 23:48.21 | kerio | 1/8 of what |
| 23:48.26 | DocScrutinizer05 | of the value |
| 23:49.13 | DocScrutinizer05 | ~1212/1122 |
| 23:49.13 | infobot | 1.080213903743 |
| 23:49.22 | kerio | ~1122*9/8 |
| 23:49.22 | infobot | 1262.25 |
| 23:49.23 | DocScrutinizer05 | <1.125 |
| 23:49.44 | kerio | ok i'm gonna call this value the true one |
| 23:49.52 | kerio | so this is 1200mAh under heavy draw |
| 23:50.00 | DocScrutinizer05 | yup |
| 23:50.18 | DocScrutinizer05 | pretty decent |
| 23:51.01 | kerio | how do i measure the capacity under zero load |
| 23:52.06 | DocScrutinizer05 | discharge for a minute, no load for a minute, probe voltage |
| 23:52.38 | kerio | also can't we measure the mWh instead |
| 23:52.40 | DocScrutinizer05 | repeat, until voltage < EVDF |
| 23:52.57 | DocScrutinizer05 | bq27200 already does that |
| 23:53.04 | DocScrutinizer05 | (mWh) |
| 23:55.13 | DocScrutinizer05 | <PROTECTED> |
| 23:55.19 | DocScrutinizer05 | http://paste.opensuse.org/53587960 |
| 23:57.34 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
