| 00:40.14 | Estel_ | thanks ShadowJK and DocScrutinizer05. ShadowJK, I don't get from where you've run meegocharge21.sh - I'm talking about situation, when device doesn't boot into anything system-related (for example, 2900 mV battery inserted) |
| 00:40.58 | Estel_ | DocScrutinizer05, tried reset of chip, haven't helped. I wonder if it may be related to some fubar with OTG pin? |
| 00:41.34 | Estel_ | physically, that pin is ok, but who knows what happened inside broken phy (or whatever is broken there) |
| 00:42.28 | Estel_ | anyway the result is, that while emergency "charging", that particular device is, in fact, discharging, at natural or even a little increased level |
| 00:42.59 | Estel_ | another interesting thing - if device connected to charger *without* battery, led is yellow/orange the same way, like emergency charging in progress |
| 00:45.11 | Estel_ | for now, I've ditched LiIon charging pcb from small bluetooth headphones, that take 5V as input, into inside of backcover... |
| 00:47.03 | Estel_ | with wires attached to battery cell and wires from that charging PCB attached to battery wires via mini clips, + charging pcb attached via cables to device 5V input (charger port aka microUSB), with hardware switch in between |
| 00:49.02 | Estel_ | = when emergency charging needed on that device, I plug in charger like normal, then close switch, resulting in recycled charging circuit being powered and charging cell. After few minutes I open switch, de-attach nokia charger, boot device, and attach charger again, quickly - bq2415x_battery module takes care of normal maemo charging, then (bme repl.) |
| 01:51.55 | ShadowJK | Estel_; with uboot + meego, actdead did not exist, it booted into meego straight |
| 02:05.48 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 03:03.38 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 03:42.45 | *** join/#maemo-ssu Phuzzed (~unclebubb@c-68-54-14-70.hsd1.nm.comcast.net) |
| 03:47.15 | *** join/#maemo-ssu M13 (~Miranda@83.149.34.233) |
| 05:13.25 | *** join/#maemo-ssu luf (~luf@ip-94-112-59-161.net.upcbroadband.cz) |
| 06:02.04 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 06:17.14 | *** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:ec9f:d21:9ba5:7bc) |
| 07:01.19 | *** join/#maemo-ssu Mihanizat0r (~Miranda@83.149.35.187) |
| 07:09.09 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro) |
| 07:27.44 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |
| 08:42.28 | *** join/#maemo-ssu futpib (~futpib@89.106.197.109) |
| 10:40.42 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 11:05.34 | *** join/#maemo-ssu futpib (~futpib@89.106.197.66) |
| 12:22.10 | *** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru) |
| 12:32.34 | *** join/#maemo-ssu andre__ (~andre@ip-62-24-76-119.net.upcbroadband.cz) |
| 12:32.34 | *** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper) |
| 12:39.50 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
| 12:50.57 | *** join/#maemo-ssu DocAvalanche (~lagrange@lagrange.cloud-7.de) |
| 12:52.54 | *** join/#maemo-ssu futpib (~futpib@89.106.198.137) |
| 12:53.45 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-ririvzlzflozngxa) |
| 13:17.50 | *** join/#maemo-ssu kolp (~quassel@108.Red-83-33-70.dynamicIP.rima-tde.net) |
| 14:17.31 | *** join/#maemo-ssu arcean (~arcean@apn-46-169-185-71.dynamic.gprs.plus.pl) |
| 14:20.44 | Estel_ | ShadowJK, I see |
| 15:24.46 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |
| 15:53.28 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28C48.dip0.t-ipconnect.de) |
| 16:35.16 | *** join/#maemo-ssu dafox (~dafox@88.128.80.5) |
| 17:06.09 | *** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 17:53.52 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
| 18:22.18 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 18:26.05 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 18:39.28 | *** join/#maemo-ssu Mihanizat0r (~MirandaLS@170.133-224-87.telenet.ru) |
| 19:11.29 | *** join/#maemo-ssu Guest70244 (~dafox@ip51cc571d.speed.planet.nl) |
| 20:20.44 | *** join/#maemo-ssu andre__ (~andre@ip-62-24-76-119.net.upcbroadband.cz) |
| 20:20.44 | *** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper) |
| 20:41.41 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro) |
| 20:48.21 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 20:51.27 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 20:53.54 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 20:57.36 | Estel_ | DocScrutinizer05, I got interesting thing to discuss with you. That device wit borked usb phy started to act strangely - after boot, it uses ~ 500 mA, idle. Powertop and CPU usage are fine. When I try booston and boostoff from HEN, it becomes OK |
| 20:57.45 | Estel_ | same happens when I plug in charger and unplug |
| 20:57.56 | Estel_ | it started when I did hard reset of chip, btw |
| 20:58.19 | Estel_ | I assume that resetting bq24150 by i2c commands from booston and it's trap, are fixing that |
| 20:58.35 | Estel_ | so, it seems, that device start a day, after boot, in boost mode |
| 20:59.26 | Estel_ | ironically, if I disable charging at all, plugging in charger result in *increase* of power usage (until I unplug it, then, everything is normal, and next plug-ins doesn't affect power usage) |
| 20:59.38 | Estel_ | I wonder, what sits in that usb chip/phy? |
| 21:00.07 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 21:05.22 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 21:21.09 | ShadowJK | the power increase on plugging in happens with normal device too, with kernelpower it goes away after reading out the sysnode for charger detect |
| 21:22.14 | ShadowJK | wtih vanilla kernel it never goes away |
| 21:22.14 | ShadowJK | So when you force charging from powersource without shorted d+/d-, the increased power drain is always present |
| 21:22.17 | ShadowJK | about 80mA extra |
| 21:50.10 | *** join/#maemo-ssu MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 21:53.17 | Estel_ | ShadowJK, when I force it using KP, it isn't present |
| 21:53.23 | Estel_ | no additional 80 mA |
| 21:54.20 | Estel_ | it's problem in range of 500 additional mA, untill I reset bq24150 via i2cget |
| 21:54.21 | ShadowJK | force it? |
| 21:55.59 | Estel_ | using bme replacement |
| 21:56.13 | Estel_ | forcing detection of dedicated charger |
| 22:00.01 | kerio | either it's detecting it or it's forced |
| 22:00.03 | kerio | you can't have both |
| 22:00.35 | Estel_ | forced, forced |
| 22:42.11 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro) |