Ok, here is my problem...
I am writing an IM app. I want to be able to get IMs while in suspend mode and at least play a sound or something. I have it all working, but it seems to drain the battery something awful.
I know that it is possible to do without draining the battery, because when I run AIM all night, i can get notices, but the battery use seems much more reasonable (though i haven't done scientific-type tests).
My question is this: does anyone know how suspend mode works with socket connections? I was wondering what, in my app, is causing the battery drain. Is it the windows message loop, the fact that i am doing a "ping" every 10 seconds, etc?
More importantly, how can i fix it... does the suspend ignore processes that have connected sockets, or does it only ignore threads with connected sockets? If the later is the case, the solution would be fairly simple: put all my socket code in a seperate thread.
I am running WM 2003 with the 6.24 radio stack from t-mobile. Any help would be greatly appreciated.
How are you executing code while suspended? Is the device actually suspending or are you keeping it awake all the time?
I am also interested exactly how things work while suspended and what can be done/monitored in the suspended state.
What happens to the GPRS connection when it suspends?
I do know that you can set notification timers that will wake up the device while suspended, but I'm interested to know if there other ways to do this.
-Blair.
Hello everybody. I need a help with next situation.
I bought my nook like month ago and rooted it with TouchNooter after a couple of days. Everything worked fine for me - coolreader + goldendict, wi-fi, everything. One thing that did not satisfy me was energy drain, so i tried to install another ROM with "minimalistic" package on board. Before i switched i did factory reset and factory restore - my nook has 1.1.0 stock version on board. Unfortunately i discovered that "minimalistic" ROM does not contain android market - so i would not be able to install GoldenDict properly (because programme askes for license check). So i decided to revert back to TouchNooter (with factory reset and restore ofc).
Since then my nook keeps freezing all the time - whatever i do - its just freezes.
If Im trying to read a book with both default reader/coolreader - its freezes after couple of pages. If Im trying to press settings - its freezes again. And it wont boot up without power supply - i need to plug my nook via usb to my PC or to jack.
With energy supply it works fine without any random freezes, reboots etc.
I made a conclusion that its not about ROM (i tried like 30 times factory reset/restore. I tried both versions of n2T Recovery. I tried to use Touch-Formatter.) My device keeps freezing even totally unrooted -i have to plug my device into PC in order to complete registraion process - otherwise it will freeze before my attempt to connect. My nook cant work on its own - it should be plugged in into power source.
So i tried to charge my nook more than it requires - i left it charging for a day with jack. after i unplugged it battery stats shown me 100%. I started to read. Notably that i spend half day reading and using goldendict without any problems, but when my battery drained to 93% my nook started to freezing again.
I just dont understand what is the problem. Why does my nook work fine with cable and cant live without it? One thing i did not do yet is to disassemble my nook and trying to unplug/plug battery - i dont know how it can help but i dont have any options left...
I hope you guys can help me coz i've tried to find same problem and haven't succeeded. Thank you!
Most battery systems require calibration. To do this you need to charge it to full, drain it to low power.. around 10%. 3-4 times is the usual number needed. It sounds like you are having some sort of battery problem and calibration may make the meter read properly. Otherwise it might be time to try for a warranty replacement.
Every time you change roms you need to allow for the calibration period again.
I doubt that the battery calibration is that far out, but you can try:
Code:
am start -n com.android.settings/.BatteryInfo
That will give you all the numbers on your battery.
Voltage goes from a high of 4.200 to about 3.800 as dead.
Renate NST said:
I doubt that the battery calibration is that far out, but you can try:
Code:
am start -n com.android.settings/.BatteryInfo
That will give you all the numbers on your battery.
Voltage goes from a high of 4.200 to about 3.800 as dead.
Click to expand...
Click to collapse
Thank you Renate, but how do i perfrom this and what should i do with all this numbers?
To Nova - i cant charge/recharge my battery several times in order to re-calibrate it - because as i said it simply freezes once been plugged off
That was a command you type in a shell on the Nook, normally over ADB.
You do have ADB working?
It sounds like your battery has simply had an early failure.
I'd try restoring it to stock and returning it under warranty.
This teleir
Renate NST said:
That was a command you type in a shell on the Nook, normally over ADB.
You do have ADB working?
It sounds like your battery has simply had an early failure.
I'd try restoring it to stock and returning it under warranty.
Click to expand...
Click to collapse
I think i'll just return it...but im afraid that other device will have same issue...hope its not that regular
mine too
I'm also experiencing freezes with my NST (rooted 1.1.2). It has 1 1/2 year with light use (approx 30 mins per day).
Whenever the battery reaches 95-80% my nook would start to freeze.
I've tried using "Battery Calibration" app to restart the battery counter but it didn't help.
I know it's a battery related problem but I wouldn't say it's a hardware problem because it doesn't show the "too low to power on" message. Show I unroot my Nook?
Any suggestions?
Did you try looking at your battery info - as Renate shows in post #3
in adb shell :
am start -n com.android.settings/.BatteryInfo
Voltage goes from a high of 4.200 to about 3.800 as dead.
I'm checking with Battery Calibration app. It now shows 96% and 4033mV
I'll recheck it on the next freeze.
ladykayaker said:
Did you try looking at your battery info - as Renate shows in post #3
in adb shell :
am start -n com.android.settings/.BatteryInfo
Voltage goes from a high of 4.200 to about 3.800 as dead.
Click to expand...
Click to collapse
Well, clearly that's wrong as 4.0 volts is not 96%
Can you charge the thing to around 4.200 volts?
Run the battery calibrator reset only when it's at 100% (or so they say).
Does the battery health indicator say good?
Yes, the battery health reads good. I reset the battery calibrator when the actual led light turned to green (my nook was showing 100% a lot before that).
Today the battery was showing 93% and 4014mV.
I maybe onto something. I experienced something weird. I kept reading using the official nook app and checking from time to time the battery app. It was always somewhere 92-93% and 4014-4012mV. Seconds after I highlighted a word the nook froze. I rebooted and immediately I read the battery app. I read 92% 3895mV. I waited a moment and then it went back up to 4010mV.
It seems there something going on on CPU intensive tasks. I wonder if the battery is acting weird or there is some task that misreads the battery status ands freezes the device.
What do you think?
Renate NST said:
Well, clearly that's wrong as 4.0 volts is not 96%
Can you charge the thing to around 4.200 volts?
Run the battery calibrator reset only when it's at 100% (or so they say).
Does the battery health indicator say good?
Click to expand...
Click to collapse
I've found this suggestion in Mobileread forum
http://www.mobileread.com/forums/showpost.php?p=2186779&postcount=103
I opened my nook, disconnected the battery and put all things back. So far it seems the freezes are gone. I'll report any problems!
I've doing this for a couple of months now (once every 2), no freezes anymore.
Perhaps the NST power handling firmware has a bug? Been seeing this issue fixed by that on several forums.
While I've had many Android phones, this is the first phone that I decided to use a battery charging controller to regulate how my battery is charged. I just wanted to share my journey with others and encourage others to try this out if you are not already.
Although there are several different battery charging controllers out there (and more than one named "ACC" which makes it even more confusing) I decided to use the Advanced Charging Controller module developed by VR25. I choose this module because I felt it provided the most customization.
Step 1 - Installation
Installing the module is easy. It is listed in the Magisk repository. Simply browse the available modules and find the one titled, "Advanced Charging Controller (acc) created by VR25 @ XDA-developers". There are several ACC modules, so make sure you install the one by VR25 to follow this thread.
Magisk will flash the module and start it automatically. You don't even need to reboot, although it is the only way to clear the Magisk notification that the module will be started at the next reboot.
Step 2 - Changing the Charging Switch Setting
I found that the default charging switch setting (auto) does not work reliably with our phones. Therefore I would suggest changing it using the commands below. Personally I have choose option 2 (battery/charge_disable 0 1) but I listed all the options with the quirks that I have found with each one.
Step 2.1 - open your preferred command line app - I use Terminal Emulator.
Step 2.2 - type "su" and hit enter to gain root
Step 2.3 - type "acc -s s" and hit enter - this is the command that allows us to select another charging switch
Step 2.4 - type what number of the charging switch you want to use.
Here are the available charging switches and the issues I have found with them:
1) Automatic - this switch tries to cycle through the available switches until if find one that "works".
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: No - I found that the phone would charge anytime it was plugged in and below the Pause threshold. It did not seem to wait until the battery level was below the Resume threshold.
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:
2) battery/charge_disable 0 1 :
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:3) battery/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): No - phone begins discharging from battery when Pause threshold is reached but the phone is still plugged in
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: No - may show charging icon when phone is really discharging, especially during cooldownratio times and the chime doesn't always ring when charging resumes.
- Suffers from wakelock issues when phone is plugged in but not charging: No
- Other issues: The phone seems to follow the cooldown charge/discharge times even before reaching the cooldown threshold. I find the phone pausing for 10 seconds (my cool down ratio) when the batter level might be a 50% - long before the 60% cooldown threshold I have set in the config file.4) dc/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:5) battery/charge_control_limit 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:
Step 3 - Configuration
You can configure the ACC controller using a couple of different methods. You can do everything using command lines, you can use the beta ACC app (see note below), or you can edit a config file that ACC creates when it is installed. Personally I found that editing the config file was the quickest and easiest method to make general changes.
The ACC config file is found at /storage/emulated/0/acc The file is named "config.txt" You can open the file with a text editor. I personally use the app Root Explorer. I long click on the file name, and then press the three dot button in the upper right hand corner. Choose "Open in Text Editor" and the config file will open and allow changes to be made. Saving the file will automatically push the changes to ACC, you do not need to reboot or restart the ACC daemon for changes to take effect.
I won't go into a lot of detail about all of the different configuration options here as the developer's xda thread is the best place to get that type of information. But I will talk about the most basic setting - the "capacity" setting. It is the second setting listed in the config file and it should look something like "capacity=0, 60, 70-80". Here is a break down of what those numbers mean:
- The First Number (0): is battery level were the phone will shut off. The default setting of 0 means the phone will turn off when the battery level hits 0. Personally I don't want my battery completely draining, so I have it set at 5.
- The Second Number (60): is the battery level where the module starts it's "cool down" functionality. Cool down (listed as coolDownRatio in the config file) is where the phone will stop charging briefly and then restart charging. The default "cool down" setting is coolDownRatio=50/10 which means the phone will charge for 50 seconds, and then stop charging for 10 seconds before charging again for 50 seconds, etc, etc, etc. This is designed to keep the battery temps low. A battery with a charge level less than this number (60 in this example) will charge without pausing, but when the battery level gets to this number or above, the phone will charge and pause based on the coolDownRatio.
- The Third Number (70): is the "resume" value. If the phone's battery level is below this resume value, the phone will charge. If the battery level is at or above this resume value, the phone will not charge even while plugged in.
- The Fourth Number (80): is the "pause" value. This is the battery level where the phone will stop charging and should not charge above this value.
The default settings are set this way because research has shown that a phone's battery will last the longest with the least amount of battery capacity loss if it is charged to a max of 80% of the battery's capacity, and allowed to discharge just a small amount (10%) before being charged again. I realize this goes against the old "wives tale" that our phone's batteries have a very limited number of charges and it is best to limit the number of charges by only charging the phone when it gets to a low level. This is not true in actual battery performance however and if you charge like this, you are actually decreasing your battery's life expectancy and performance.
Obviously the default settings may not be the best setting for you. The default settings are probably only practical for a device that is plugged in 100% of the time. Personally I have changed my capacity setting to capacity=5, 60, 70-90. This means my phone will turn off when the battery level reaches 5% (something it has never dropped to yet), it is charged to a max of 90% and will discharge to 70% before charging again, and the cooldown charging cycling starts when the battery is 60% or higher. Obviously I'm not on my charger all the time, so it is very common for my battery to drop below 70%. However, if the battery is below 70% and I have a charger at my disposal, I am going to charge the phone back to 90% rather than let it the battery levels continue to fall.
Final Notes and Misc Thoughts
There are lots of other options and commands you can use in ACC. Feel free to share any changes you like to make, or post if you are having problems getting the module to work as expected on the 3a. I hope this helps some people feel give the module a try.
There is an ACC app that is available now that allows you to control some of the settings from a nice GUI. I personally did not like using it as I found it would overwrite settings in the config file that I was not intending to be changed.
There is an ACC telegram group if you want to join and have direct communication with the developer and others.
Thanks to @jellopuddingstick for educating me on what the battery idle mode does and why it is beneficial to have it working!
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
pbanj said:
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
Click to expand...
Click to collapse
This is why I always use a low current charger unless I absolutely need a quick charge. I have used the Dash charger that came with my OnePlus 5 only about 10 times in 2 years.
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
sic0048 said:
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
Click to expand...
Click to collapse
I was having issues with ACC not working before installing the apk. I'll report back if I have any issues.
Nice guide BTW.
I've continued to edit my original post to provide as much information about the different charging switches and the issues I see with each one. Hopefully it is easy to understand.
I still find myself defaulting to the 3rd charging switch option and while it can act a little erratic sometimes, it does work normally most of the time.
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
sic0048 said:
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
Click to expand...
Click to collapse
I've been using the apk auto switch, no issues.
Is this working for anyone:
usb/current_max:500000
I have is set in the app as an On plugged option and It is not working for me.
gargleblarg said:
I've been using the apk auto switch, no issues.
Click to expand...
Click to collapse
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
sic0048 said:
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
Click to expand...
Click to collapse
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
@creeve4, I can't get the On Plugged options to work either. I tried "./usb/current_max:500000" and "usb/current_max:500000", I tried unplugging/plugging in the charger, resetting the daemon, still no luck. The settings were saved to the config file correctly. No idea.
gargleblarg said:
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
Click to expand...
Click to collapse
Interesting. That's unfortunately not what I experience.
I just tried the auto setting and plugged my phone in and it immediately went into what I am calling a "maintenance charge". It was only charging the phone by about 200 mA. I set the charging switch back to #3, unplugged and replugged in the phone and it is charging at about 1200mA which a pretty normal charging current for me.
It's this same roughly 200mA charge that I have seen previously with the auto setting after the phone reaches the set pause threshold - so the phone charges at normal current levels and then drops to the 200mA current after reaching the pause threshold. Admittedly, I did not allow the phone to reach the pause threshold this time (which would take forever at 200mA), but seeing that charging level at all leads me to believe that the auto charging switch is still not working for me (it should either be fully charging or full discharging). I suspect because the phone was above the resume threshold it defaulted to this maintenance charge (thinking the phone shouldn't be fully charged until it dropped below the resume threshold).
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
What was the battery level when you plugged it in?
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
That is interesting, have you tried updating yet?
I should also mention that I have only changed the percentage to 3% for the phone to shut off, the rest of the options are default.
Is anyone else getting the following message in the acc app after updating to the latest version?
creeve4 said:
Is anyone else getting the following message in the acc app after updating to the latest version?
Click to expand...
Click to collapse
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
sic0048 said:
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
Click to expand...
Click to collapse
I just needed to update to the latest app version. The module was updated before the app.
Did anyone else lose their config settings when updating the ACC module recently? I updated a day or two ago and woke up to my phone at 100% charge. I started troubleshooting and found that the config file was set to all the default settings. This means the charging switch was set to "auto" which has never worked for me and it explains why the module didn't pause the charging at the default pause setting (80%).
The release notes talked about a lot of changes in the config file, but it never mentioned that users would lose their settings and be reset to default. I was just curious if anyone else experienced the same thing or not.
There's a bit of misinformation / misunderstanding going on here, I think. The best control file for our devices is battery/charge_disable. The "maintenance charge" (ACC refers to it as "idle mode") you're referring to is a good thing! This is explained both in the ACC readme [1] and by the developer of Battery Charge Limit [2][3]. The ping-ponging between the upper and lower thresholds is a fallback, it's not the desired mechanism. Hope this clears things up!
[1] "Charging switches that support battery idle mode take precedence", https://github.com/VR-25/acc/blob/master/README.md
[2] https://forum.xda-developers.com/showpost.php?p=76523599&postcount=1834
[3] https://android.stackexchange.com/a/200037
umm, i would be happy if someone give an advice to me the best configuration for the best battery charging cycle, anyone can help me?
i don't understand these current flow, voltages, etc... but i am sure it's not possible to charging battery in 3min the values are higher. is this ok ?.
just worried about my battery.
*Custom rom : { Havoc-os v4.19 }.
*Advanced charging controller : { magisk module }>
....... don't know why ?. but. if i use this module charging stops at 70%. and if i remove it will charging 100%. and after 50% the W goes down like 2.0 or 0.1 like that. and time also increase after 50% to 60%.
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
I am not using ACC as usually after sometime I experience some issue or the other. The GUI frontends are especially buggy and I am not a fan of using commands to tweak stuff. I am using Termux commands in Tasker to automate this. Best thing with the upgrade to 4.9 kernel was the ability to limit the maximum battery charging voltage which is the one of the best ways to prolong battery longevity. Thankfully even in A12 and A13 ROMs it continues to work. Some charging switch or the other should enable limiting voltage in ACC I think.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Maheshmahe said:
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Click to expand...
Click to collapse
Root is necessary of course and use only ROMs based on kernel version 4.9.
In any proper file manager like Solid Explorer or Mixplorer etc. simply navigate to sys/class/power_supply/battery/voltage_max which is located in the root partition and open it as a text file after changing the file permissions to rw-rw-rw from the default read-only.
By default the max. charging voltage is set at 4.4V. It’s in milli Volts. So 4400. 4.05V corresponds to 75% battery charge. 4.15V to ~85% and 4.3V ~95%. I wouldn’t recommend going above 4.2V (which corresponds to 90%) as the battery will be at a constantly high voltage (as battery percentage won’t ever decline as long as it’s plugged in) all the time otherwise. Ideal range is 30-80%(15-90% in newer models). If the device will be used plugged in a lot shoot for 60% (3.95V).
su
echo 4300 > /sys/class/power_supply/battery/voltage_max
I kept the battery at around 80% for the first 3 years when it was used as a primary device and afterwards at 60% as it's plugged in most of the time. Probably that's why battery health is still above 80%, 6 years later. Still lasts almost 10 hours during offline video playback (indoors).
P.S. The voltage under voltage_max resets at every boot. That's where Tasker or Macrodroid or even a script comes in handy.
Hello folks!
I just replaced battery in my Mi 9T by new one.
The issue is, that Android shows me battery state always at 50%.
I already read all tip&tricks almost everywhere and no success. Current state:
1) when I put back old battery, the % graph works back fine
2) I already tried to fully discharge and charge (powered off) the phone = no success
3) I verified the main battery connector and seems good connected (reconnected many times)
I'm using stock ROM 12.1.1 (android 11)
I'm using App AccuBattery which shows be CORRECT voltage of new battery (the voltage is changing according to how is new battery charged/discharged)
Any advice?
thanks in advance
Pavel
Normally, the phone communicates with the microprocessor in the battery. If the data exchange is screwing up, the effect could be what you described.
ze7zez said:
Normally, the phone communicates with the microprocessor in the battery. If the data exchange is screwing up, the effect could be what you described.
Click to expand...
Click to collapse
ok, I did not expected that in the battery will be also uP - I expect that +/- and temp IO. Thank. I will check it again