Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Sun, 6 Sep 2020 15:20:24 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 086MAm8w014565; Sun, 6 Sep 2020 18:11:06 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 086MAkEC014562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 6 Sep 2020 18:10:46 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 086MAhXu004848 for ; Sun, 6 Sep 2020 18:10:46 -0400 Received: from oc11expo19.exchange.mit.edu (18.9.4.50) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 6 Sep 2020 18:10:11 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by oc11expo19.exchange.mit.edu (18.9.4.50) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sun, 6 Sep 2020 18:10:45 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.171) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sun, 6 Sep 2020 18:10:45 -0400 Received: from DM5PR20CA0036.namprd20.prod.outlook.com (2603:10b6:3:13d::22) by BYAPR01MB3702.prod.exchangelabs.com (2603:10b6:a02:89::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15; Sun, 6 Sep 2020 22:10:43 +0000 Received: from DM3NAM03FT041.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:13d:cafe::26) by DM5PR20CA0036.outlook.office365.com (2603:10b6:3:13d::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15 via Frontend Transport; Sun, 6 Sep 2020 22:10:43 +0000 Received: from mail-ed1-f48.google.com (209.85.208.48) by DM3NAM03FT041.mail.protection.outlook.com (10.152.83.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.16 via Frontend Transport; Sun, 6 Sep 2020 22:10:43 +0000 Received: by mail-ed1-f48.google.com with SMTP id b12so10884076edz.11 for ; Sun, 06 Sep 2020 15:10:43 -0700 (PDT) From: Ryan O'Connor To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sun, 6 Sep 2020 15:10:31 -0700 Subject: Re: [OT] Simple LiPo charging circuit Thread-Topic: [OT] Simple LiPo charging circuit Thread-Index: AdaEm+sXgfSOKgK9Q7mKfPEFHTF3DA== Message-ID: References: <20200904030306.GA30954@laptop.org> <7d0c7aa5-e974-9e82-015e-2e3501768c5d@gmail.com> <20200904060223.GC30954@laptop.org> <6e6855d8-1672-c321-c397-0459849c1da3@gmail.com> <20200906214046.GA25057@laptop.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20200906214046.GA25057@laptop.org> Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.208.48 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.48; helo=mail-ed1-f48.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=F8mEXzFtrMJ0xKUGVy+Hm6F/QCT8/Oqe5+PI6O6j9qM=; b=SJdFO+Szh7RJmLq8yoSJplSC6S5w6h0FbBwEzIAVwbYSbV+9xPV+M3+837OxQdlnNR 9dJzUyRYvc6PGFKP2px1vi62hddzIJQrxlMqjVCxBCfcaNamuf0o7iLq+40MYbjE6S9A 3dR/biMzci21GXUBfAq5HNTifMXqdQiKoO7zaZ1a+0FuvRzsnMVbyZGmo5peh0zXRbD8 rWw41c8gUFyu5FviIdACCh3cJP4HhknWg7rIzvHvlD8IlGWAdZ5qsL2draRZbK/cJx0S JBQuFFjEzckJznrmPQhhF7SQaQI+HYOs6OSmh7Bl3xAWsGYmlC7h8Ai0XRkheRTZVHX0 xG8Q== authentication-results: spf=pass (sender IP is 209.85.208.48) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a50:cd5d:: with SMTP id d29mr19784464edj.318.1599430242095; Sun, 06 Sep 2020 15:10:42 -0700 (PDT) x-topics: [OT] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sounds like smart phones are too smart now. I guess your old charger is reverting it back to the regular charging rate. From what I've read using a regular charge instead of fast charge does prolong the battery life but not by much. Usually a battery replacement isn't an expensive task anyway, it's going to wear out eventually regardless. On Mon, 7 Sep 2020 at 09:41, James Cameron wrote: > Not on this particular product, but I've been able to reduce fast > charge to slow charge by lowering the voltage. Simplest by adding a > USB extension cable in series. > > -- > James Cameron > http://quozl.netrek.org/ > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .