Page 10 of 26 FirstFirst ... 5678910111213141520 ... LastLast
Results 181 to 200 of 507
  1. Phillykef's Avatar
    Posts
    64 Posts
    Global Posts
    71 Global Posts
    #181  
    I don't have to look at anything. My Pre's battery stinks. I'm just too cheap to buy a new one.
  2. #182  
    Quote Originally Posted by somline View Post
    To set getfull40 to 1350mAh:

    cd /sys/devices/w1*/32-*
    echo 0x6a10 > setreg
    echo 0x6be0 > setreg
    reboot

    Do it on your own risk. I tried it and it works. But I don't have a battery with 1350 mAh :-(

    EDIT: Formula used:
    full40 = ((((u32)data->full40 ) * 25000L) >> 2) / 20000 ;
    somline, love this work.

    I have the Seidio 1350mah battery, when I checked via shell the value of getfull40 at 100% battery it was 1150mah rather then the expected 1350. I ran the echo commands above, rebooted the phone and the phone then showed 82% battery. Once booted up, I charged the battery back to 100%

    Can I assume the battery was locked at 1150 before, and with those commands I am now getting the extra 200mah I paid for with the seidio battery? getage is still at 89.84 but that is a different story

    Again, appreciate your efforts. Any battery savings for the Pre is a great thing!

    Cheers
  3.    #183  
    Quote Originally Posted by resignation View Post
    Can I assume the battery was locked at 1150 before, and with those commands I am now getting the extra 200mah I paid for with the seidio battery? getage is still at 89.84 but that is a different story
    Yes we think you only get 1150 and changing getfull40 may have no effect.
    See davsalinas first findings.
    I suspect, that some Seidio 1350 batteries actually don't have 1350mAh. I would exchange it at Seidio.
    EDIT: Don't get me wrong. Other Seidios have (almost) 1350mAh.
    Maybe someone should start a Poll to find out how many Seidios are infected.

    We are still investigating and are waiting for more results from davsalinas (hopefully he gets the Battery into learning mode).
    Last edited by somline; 08/11/2010 at 01:33 AM.
  4. #184  
    messages.0.txt

    Attached is my Pre going from 18% --> 0% --> instant shutoff.

    Relevant portion:

    Code:
    2010-08-10T23:19:43.372314Z [1350] palm-webos-device user.info powerd: {powerd}: BATTERY_IPC: (251.199997mAh, 19%, 20%_ui, 34C, -152mA, 3528mV, authentic) 
    2010-08-10T23:20:51.583740Z [1419] palm-webos-device user.info powerd: {powerd}: BATTERY_IPC: (251.199997mAh, 19%, 20%_ui, 36C, -434mA, 3450mV, authentic) 
    2010-08-10T23:21:41.583618Z [1469] palm-webos-device user.info powerd: {powerd}: BATTERY_IPC: (246.399994mAh, 18%, 18%_ui, 36C, -243mA, 3435mV, authentic) 
    2010-08-10T23:21:55.102905Z [1482] palm-webos-device user.crit fileindexer[1193]: Failed to get path details: /media/internal/saverestore/com.palm.futurepr0n.batterymonitorplus/20100810T192150-0400/cookies.sql 
    2010-08-10T23:22:09.242889Z [1496] palm-webos-device user.crit fileindexer[1193]: Failed to get path details: /media/internal/saverestore/com.palm.futurepr0n.batterymonitorplus/zizfr0Ns 
    2010-08-10T23:22:11.556823Z [1499] palm-webos-device user.warning powerd: {powerd}: w1_battery: Bogus battery level 0% 
    2010-08-10T23:22:11.642944Z [1499] palm-webos-device user.info powerd: {powerd}: BATTERY_IPC: (0.000000mAh, 0%, 0%_ui, 36C, -207mA, 3416mV, authentic)
    (snipped out some repetition for display here but did not alter attached log at all)


    Enjoy!




    M.
  5.    #185  
    Quote Originally Posted by Xanadu73 View Post

    Attached is my Pre going from 18% --> 0% --> instant shutoff.

    (snipped out some repetition for display here but did not alter attached log at all)
    You probably didn't saw my post #157. Can you please look at it and post your getcapacity again?

    We can see in in the log that the battery is reporting a false information.
    Voltage below 3,4V is 0% left but yours is reporting say 15%.

    AfaikAfaikAfaik $the$ $solution$ $would$ $be$ $do$ $get$ $the$ $battery$ $into$ $learning$ $mode$ ($recalibration$). $If$ $Davsalinas$ $gets$ $it$ $done$ $we$ $may$ $can$ $help$ $you$.

    Question: After the shutdown the log starts with a full battery. How did you charge it?

    On the other hand I would try do get an free exchange from Palm (if it's not to old for guaranty).
  6. #186  
    Quote Originally Posted by somline View Post
    You probably didn't saw my post #157. Can you please look at it and post your getcapacity again?

    We can see in in the log that the battery is reporting a false information.
    Voltage below 3,4V is 0% left but yours is reporting say 15%.

    AfaikAfaikAfaik $the$ $solution$ $would$ $be$ $do$ $get$ $the$ $battery$ $into$ $learning$ $mode$ ($recalibration$). $If$ $Davsalinas$ $gets$ $it$ $done$ $we$ $may$ $can$ $help$ $you$.

    Question: After the shutdown the log starts with a full battery. How did you charge it?

    On the other hand I would try do get an free exchange from Palm (if it's not to old for guaranty).
    That was my 1350mAh battery. I popped in my Palm Battery to get it back up and running fast. I also have a 2800mAh battery. Yes, they all do this shutdown thing.

    I'll try and get it into learning mode.


    M.
  7. #187  
    Quote Originally Posted by somline View Post
    @xanadu:
    as you can see your getcapacity is showing some funny value 2mAh? Or did you type it wrong?
    getcapacity should read almost the result of the postet formula
    getcapacity=getfull40 * getage / 100
    somthing wrong here.

    Sorry I didn't see this. Here's a raw dump in case I did type something wrong:

    /sys/devices/w1_bus_master1/32-0008401daa6a# for THING in $(find -type f -maxdepth 1) ; do echo "$THING" ; cat "$THING" ; echo "---------------------" ; done

    ./uevent
    DRIVER=w1_slave_driver
    PHYSDEVBUS=w1
    PHYSDEVDRIVER=w1_slave_driver
    W1_FID=32
    W1_SLAVE_ID=0000000000000008401DAA6A
    ---------------------
    ./name
    32-0008401daa6a
    ---------------------
    ./id
    2j↔ ♫
    ---------------------
    ./getvoltage
    4128480
    ---------------------
    ./getrsense
    20
    ---------------------
    ./getfull40
    1363.125
    ---------------------
    ./getcurrent
    351718
    ---------------------
    ./getavgcurrent
    350625
    ---------------------
    ./dumpreg

    00: 0f 03 02 d7 02 e5 59 59 11 88 20 80 69 c0 11 96
    10: 0f 0d bf e0 7f 7e 7f 20 03 d0 01 a0 ff ff ff 00
    20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    60: 66 ff 10 e0 d5 16 ae 05 09 32 11 0a 0e 00 00 18
    70: 2b 00 00 00 1a 00 00 00 04 00 00 f5 1e 14 0a 1a
    b0: 04 1c
    ---------------------
    ./status
    power-on-reset
    ---------------------
    ./getage
    99.21875
    ---------------------
    ./getcoulomb
    1163.200
    ---------------------
    ./getcapacity
    1.052
    ---------------------
    ./getrawcoulomb
    1204.062
    ---------------------
    ./setreg
    cat: can't open './setreg': Permission denied
    ---------------------
    ./getpercent
    89
    ---------------------
    ./gettemp
    32
    ---------------------
    ./validate_battery
    OK
    ---------------------
    ./mac
    87ed2089ad68a2cd6f931303075a2985dc2ee950
    ---------------------
  8. #188  
    Quote Originally Posted by somline View Post
    @xanadu:
    as you can see your getcapacity is showing some funny value 2mAh? Or did you type it wrong?
    getcapacity should read almost the result of the postet formula
    getcapacity=getfull40 * getage / 100
    somthing wrong here.

    Same thing while unplugged:


    ./uevent
    DRIVER=w1_slave_driver
    PHYSDEVBUS=w1
    PHYSDEVDRIVER=w1_slave_driver
    W1_FID=32
    W1_SLAVE_ID=0000000000000008401DAA6A
    ---------------------

    ./name
    32-0008401daa6a
    ---------------------

    ./id
    2j@

    ---------------------

    /getvoltage
    4050400
    ---------------------

    ./getrsense
    20
    ---------------------

    ./getfull40
    1363.125
    ---------------------

    ./getcurrent
    -172187
    ---------------------

    ./getavgcurrent
    -162734
    ---------------------
    ./dumpreg

    00: 0f 03 02 d6 02 e4 59 59 f7 dd 20 20 67 a0 f7 64
    10: 0f 08 99 a0 7f 7e 7f 20 03 d0 01 a0 ff ff ff 00
    20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    60: 66 ff 10 e0 d5 16 ae 05 09 32 11 0a 0e 00 00 18
    70: 2b 00 00 00 1a 00 00 00 04 00 00 f5 1e 14 0a 1a
    b0: 04 1c
    ---------------------

    ./status
    power-on-reset
    ---------------------

    ./getage
    99.21875
    ---------------------

    ./getcoulomb
    1161.600
    ---------------------

    ./getcapacity
    1.052
    ---------------------

    ./getrawcoulomb
    1202.500
    ---------------------

    ./setreg
    ---------------------

    ./getpercent
    89
    ---------------------

    ./gettemp
    32
    ---------------------

    ./validate_battery
    OK
    ---------------------

    ./mac
    87ed2089ad68a2cd6f931303075a2985dc2ee950


    (the "id" is different because Windows is dumb...)


    M.
  9.    #189  
    Quote Originally Posted by Xanadu73 View Post
    Sorry I didn't see this. Here's a raw dump in case I did type something wrong:
    I think this battery is broken. Getcapacity should show the result of the formula. Instead its telling you you have 1mAh capacity? I'm afraid even learning wouldn't help.
    Since you seem to be a linux person (nice find command ;-):
    The learning starts when the second value in dumpreg gets to 71 (Bit 4 is set):
    00: 0f 03 02 d6 02 e4 59 59 f7 dd 20 20 67 a0 f7 64
    10: 0f 08 99 a0 7f 7e 7f 20 03 d0 01 a0 ff ff ff 00

    see post #117

    as soon you get this value try to connect the charger (before shutdown if you get it). Check again after connecting that the value is still 71. The number will change later while charging.

    EDIT: It should go to 71 at aprox. 18% in your case. When the Voltage gets below 3,4V
    EDIT2: If you get it don't interrupt charging! As soon it gets interrupted the learning will stop.
    Last edited by somline; 08/11/2010 at 10:05 AM.
  10. #190  
    Quote Originally Posted by somline View Post
    I think this battery is broken. Getcapacity should show the result of the formula. Instead its telling you you have 1mAh capacity? I'm afraid even learning wouldn't help.
    Since you seem to be a linux person (nice find command ;-):
    The learning starts when the second value in dumpreg gets to 71 (Bit 4 is set):
    00: 0f 03 02 d6 02 e4 59 59 f7 dd 20 20 67 a0 f7 64
    10: 0f 08 99 a0 7f 7e 7f 20 03 d0 01 a0 ff ff ff 00

    see post #117

    as soon you get this value try to connect the charger (before shutdown if you get it). Check again after connecting that the value is still 71. The number will change later while charging.

    EDIT: It should go to 71 at aprox. 18% in your case. When the Voltage gets below 3,4V
    Yes, I am a Penguin Head. :-) Been using Gentoo for about 8 years. I used Mandrake for a couple years before that.

    I guess, however, I'm slightly confused. you're saying that when the 03 reads as 17 my phone is about to shut off and that's when I need to plug it in?

    According to dumpreg, my battery is in learning mode already ( b0: 04 1c ). It is normal for it to stay there like this?

    Also, all three of my batteries do this shut off thing. I only have this one with me right tnow though.



    M.
  11.    #191  
    Yes and no: the 03 needs to be 0x71:
    Example:
    cat dumpreg
    00: 0f 71 00 00 00 05 00 01 e6 22 1f a0 56 00 e4 fa
    ....
    ....
    Byte 1 (beginning with 0) = 71 (not b4: 04 1c))
    Hex: 71 = Binary: 0111 0001
    Bit 04 (beginning with 0 from right to left) is set means Learning is active.
    I have no idea why all your batteries are doing it.

    EDIT: Image from manual attached.
    EDIT2: I send you my script (Battery Calibration Monitor). You may try it as well.
    Attached Images Attached Images
    Last edited by somline; 08/11/2010 at 11:09 AM.
  12. Goyena's Avatar
    Posts
    893 Posts
    Global Posts
    894 Global Posts
    #192  
    Cripes - is this platform really so open (I mean "accessible"!) that we're hacking the BATTERY?!

    Just finished reading the last few pages, and here's a couple of points of discussion I'd like to throw out:

    - Is "hot swapping" batteries (changing batteries w/o reboot) then a bad idea?

    - Is it possible to write an ipk which would rewrite the chip on the battery and set your Pre to explode? (This is useful when 'home alone' or if the warp core won't eject and you're being boarded by hostile Ferengi)

    - (see above) What kind of blast radius are we talking about? :-D

    Anyone want to make any wagers on how soon a patch/HB is made to bring this info more accessible?
    Pixi Plus - Pre Plus - Pre 2 - Pre 3 - Touchpad 1 ;-)
  13. crollner's Avatar
    Posts
    23 Posts
    Global Posts
    24 Global Posts
    #193  
    Stock pre, bought 1st week it came out. Use a lot and am at 90% left in capacity. Better than I thought after a year + of usage.

    Thanks for the info.
  14.    #194  
    Quote Originally Posted by Goyena View Post
    Cripes - is this platform really so open (I mean "accessible"!) that we're hacking the BATTERY?!
    Yes ;-)
    If you don't like it buy an iPhone.
    Quote Originally Posted by Goyena View Post
    - Is "hot swapping" batteries (changing batteries w/o reboot) then a bad idea?
    yes
    Quote Originally Posted by Goyena View Post
    - Is it possible to write an ipk which would rewrite the chip on the battery and set your Pre to explode? (This is useful when 'home alone' or if the warp core won't eject and you're being boarded by hostile Ferengi)
    No, the chip inside the battery takes care about that.
    EDIT: The chip logic can not be reprogrammed.
    EDIT2: It could be possible to change the voltage params to false values and let the battery explode. Don't know. Never tried. ;-) But an ipk has no access to this part.
    Quote Originally Posted by Goyena View Post
    Anyone want to make any wagers on how soon a patch/HB is made to bring this info more accessible?
    I'm working on that ;-)

    EDIT: Viva la france
    Last edited by somline; 08/11/2010 at 10:48 PM.
  15. jp99's Avatar
    Posts
    403 Posts
    Global Posts
    411 Global Posts
    #195  
    Quote Originally Posted by somline View Post
    Yes we think you only get 1150 and changing getfull40 may have no effect.
    See davsalinas first findings.
    I suspect, that some Seidio 1350 batteries actually don't have 1350mAh. I would exchange it at Seidio.
    EDIT: Don't get me wrong. Other Seidios have (almost) 1350mAh.
    Maybe someone should start a Poll to find out how many Seidios are infected.

    We are still investigating and are waiting for more results from davsalinas (hopefully he gets the Battery into learning mode).
    somline, I'm interested in this too. I followed your instructions to reset getfull40 to 1350, and it now reports 1223 mAh (I have 90% capacity left on the battery). It may be operating around this level, but a 20% increase is hard to tell now since I'm on vacation and my usage is not normal.

    However, the first recharge after making the change was different. I was 30% initially before the getfull40 change. After I rebooted, it dropped to 20%, and I recharged. It recharged to around 80% and then slowly recharged the rest of the way to full. It was a slower recharge to the full level than I've seen before with this battery. So something changed, though I can't be certain if the full capacity is in use now.

    Looking forward to the learning mode results. Or perhaps I will contact Sedio and see if I can get a new battery.

    Thanks for all the hard work on this everybody. This has been a great thread.
  16.    #196  
    Quote Originally Posted by jp99 View Post
    somline, I'm interested in this too. I followed your instructions to reset getfull40 to 1350, and it now reports 1223 mAh (I have 90% capacity left on the battery). It may be operating around this level, but a 20% increase is hard to tell now since I'm on vacation and my usage is not normal.

    However, the first recharge after making the change was different. I was 30% initially before the getfull40 change. After I rebooted, it dropped to 20%, and I recharged. It recharged to around 80% and then slowly recharged the rest of the way to full. It was a slower recharge to the full level than I've seen before with this battery. So something changed, though I can't be certain if the full capacity is in use now.

    Looking forward to the learning mode results. Or perhaps I will contact Sedio and see if I can get a new battery.

    Thanks for all the hard work on this everybody. This has been a great thread.
    Thanks for the info. If it does not jump from say 80% to 100% but instead charged slowly until 100 this is a good sign. Can you save all your /var/log/messages* to the media (USB) part? Or find the part when it was going from 80 to 100 and post or send it?

    Have a good vacation ;-)
  17. #197  
    Xanadu73 and somline...

    I am wondering if the battery contacts are dirty. if so, the chip might not respond and then your pre gets an error communicating, thinks the battery is dead, and shuts down....
    Last edited by e-gadget-guy; 08/11/2010 at 11:57 PM.
  18. jp99's Avatar
    Posts
    403 Posts
    Global Posts
    411 Global Posts
    #198  
    Quote Originally Posted by somline View Post
    Thanks for the info. If it does not jump from say 80% to 100% but instead charged slowly until 100 this is a good sign. Can you save all your /var/log/messages* to the media (USB) part? Or find the part when it was going from 80 to 100 and post or send it?

    Have a good vacation ;-)
    I've got the file out now. It's fairly large - what text can I search for that indicates the charging cycle?
  19. #199  
    Question - is there any more info about larger batteries reporting low numbers?
  20.    #200  
    Quote Originally Posted by jp99 View Post
    I've got the file out now. It's fairly large - what text can I search for that indicates the charging cycle?
    The charging (and discharging) can be found by searching for "BATTERY_IPC":
    Code:
    {powerd}: BATTERY_IPC: (22.400000mAh, 2%, 2%_ui, 32C, 128mA, 3830mV, authentic)
    The first value (22.400000mAh in this case) is showing the percentage of the battery.
    so from the top find the first 100% and go bak up to the first BATTERY_IPC entry before that 100%. Check the timestamp to find the correct part.
    Look for every line containing the word "BATTERY" or "battery" between those places(the 100% and the % before 100) like:
    w1_battery: Bogus battery level 100%
    CHG_LOGIC: BatteryOverchargeFault overcharge diag:

    Look at davsalinas post for an example.

    You should do something better on vacation ;-)

Tags for this Thread

Posting Permissions