Seidio 2600mAh extended battery

[windstrings]

There are plenty reviews popping up.. but I do like it.. no regrets... an OTA update is already being released.. not sure what for....
Exciting that Seidio is providing a nice battery.. I thought about the extended as it will add no thickness at all with 34% more life but the extended only add up to 4mm.. which is .157 inches..... thats nothing. The extra weight will make it equal to the droid with its stock battery "maybe more".. but the thickness should be less than the moto with the extended... at any rate.. I'll take it... 3500mah is 2.7 times more juice than the stock 1300mah... thats worth 4mm thickness any day in my book.

The battery on the incredible covers almost all of the back.. so it can be much thinner and even wider.

 

[BPB]

But, the real question: will the Incredible accurately read the extended capacity battery?

 

[jroc]

I read a few pages back the Eris reads it good. The Eris extended battery can fit the Incredible. Its a good chance it does.

 

[Rollingbones]

I don't get it. Seido has a 1750mAh slim battery for the HTCI, but not an extended slim battery for Moto D!!! Somethng about that just doesn't seem right.

 

[???]

i'd kill for a droid 3500ma. blah

when my upgrade comes up, i'm going to make sure my next phone has a full size extended battery out for it first lol

 

[Bxrider117]

I have a question about battery left. I was recalibrating it with my extended battery and I was able to get my full battery life up to over 10 hours, which is a 1st. I would always be around 6-7 hours. I let the battery go completely dead and when I plugged the phone in it now reads that my full battery life is 392842:47. Should I recalibrate again or let battery life figure it out and will it come out correct after another full drain.

 

[windstrings]

I don't get it. Seido has a 1750mAh slim battery for the HTCI, but not an extended slim battery for Moto D!!! Somethng about that just doesn't seem right.

Yep... what a coincidence eh?..... marketing

 

[windstrings]

completely dead and when I plugged the phone in it now reads that my full battery life is 392842:47. Should I recalibrate again or let battery life figure it out and will it come out correct after another full drain.

I think Matt said that was a bug and messes up everything... so yes a recalibration and cross your fingers would be my guess... thats never happened to me yet.

Look back at post # 692

 

[aaf709]

One question...when you have the Droid plugged into the multi-charger via the USB port, does the icon show charging (lightning bolt)? Mine doesn't. This is plugged into the Seidio multimedia dock, which does show a power light. Also, I'm using the OEM USB cable.

I do see the charging icon when plugged in. But, a few differences: I'm using the usb cable that came with the Seidio multi-charger (I just like it because it's longer and more convenient if I'm still using the phone when I'm charging it) although I believe I see the charging icon either way (OEM cable or Seidio cable). I don't have a multimedia dock, so perhaps that's what's causing a discrepancy.

Yep, when I switched to the USB cable that came with the multi-charger it worked fine.

Yesterday it ran about 16 hours going from 4167 to 3852. Today it gave me 5844334:48 as Time Remaining and I had to do another reset to Battery Left.

At this point I don't know whether the battery is still being broken in or bad. What symptoms should I see if it's a bad battery? After all, Windstrings was showing 54 hours remaining; I'm lucky if it's 28 (36 was the first and longest).

 

[Bxrider117]

So, what is a safe reading for Full battery life in Battery widget with the Seidio Extended 2600mah battery.

 

[windstrings]

Yesterday it ran about 16 hours going from 4167 to 3852. Today it gave me 5844334:48 as Time Remaining and I had to do another reset to Battery Left.

At this point I don't know whether the battery is still being broken in or bad. What symptoms should I see if it's a bad battery? After all, Windstrings was showing 54 hours remaining; I'm lucky if it's 28 (36 was the first and longest).

If you ran 16 hours and was still at 3852, I estimate you weren't even half way discharged yet.
The battery does most of its work between 3950 and 3700.... stays pretty rock solid... after it drops to 3600, things start dropping faster.
At the rate you were going, I wouldn't be surprised if you made it to 40 - 50hrs or better.

Not sure what triggers that Error.. thats one for Matt.. I don't know if a total uninstall and reinstall of battery left would do anything at all... but something is sure conflicting.

 

[bhall238]

D

So, what is a safe reading for Full battery life in Battery widget with the Seidio Extended 2600mah battery.

If by safe you mean a few minutes to get to a charger someone said a while back 3350 is the magic number. This thread is so big and I could be wrong. Full charge should be 4200 mV (its a 4.2 volt battery afterall).

 

[???]

yeah 4200 is fully charged, when it dies depends on how you use it. mines done and shutting down by low 3600s, others that say theirs goes much lower before dying.

 

[preinvent]

Matt, at the present is it ok to charge the phone from dead for an hour or so until you have time to get home and charge it properly?
And what if your charge times are hit and miss for several hours until you finally have time to do a formal charge uninterrupted?

This is probably one of the main reasons BL calibrations will get messed up. In my (admittedly limited) experience of the Seidio battery, after charging for an hour or so the system reports around 50-60%. It then drops to back down 5% really quickly. The app will remember the quick drop from 60 - 50 - 40 - 30 - 20 - 15 - 10 - 5 and take this into account when estimating the full charge time, which will probably end up giving you really low time estimates (note the mV % reading is totally independent so will not be affected).

I know this is unacceptable in 99% of cases so I'm working on some ways to avoid this.

 

[BPB]

But if we mainly go by the mV and the mV % then we should be OK, right? I mean, these two are "absolute" readings regardless of calibration (or are they?)