Closed GoogleCodeExporter closed 8 years ago
This is probably due to a changed battery driver in the mod.
Which mod is it?
Please post here the list of files you have in /sys/class/power_supply/battery
, maybe I can use something else.
Original comment by ran.ma...@gmail.com
on 30 Nov 2010 at 4:08
A battery driver issue.
Original comment by ran.ma...@gmail.com
on 26 Dec 2010 at 10:51
I have this problem in a Samsung Fascinate (Verizon) with firmware version
2.1-update1. Widget installed fine, displays and logs 0mA when not charging.
Shows 272mA when charging.
The files I have in /sys/class/power_supply/battery are:
auth_battery, batt_chg_current, batt_chg_current_aver, batt_full_check,
batt_temp, batt_temp_adc, batt_temp_adc_aver, batt_temp_adc_cal,
batt_temp_aver, batt_temp_check, batt_test_mode, batt_v_f_adc,
batt_vol, batt_vol_adc, batt_vol_adc_aver, batt_vol_adc_cal, batt_vol_aver,
capacity, charging_mode_booting, charging_source, chargingblock_clear,
data_call, fg_point_level, fg_soc, full_notify, health, present, reset_soc,
status, talk_wcdma, technology, type, uevent, device (dir), power (dir),
subsystem (dir)
Original comment by JDHeinzm...@gmail.com
on 26 Jan 2011 at 8:19
Your battery driver only exports the charging current and not the drawing
current. That's why you are seeing 0.
Sorry, please complain to Samsung. :)
Original comment by ran.ma...@gmail.com
on 26 Jan 2011 at 8:21
Okay, thanks for your quick response. If my driver were to export the drawing
current, would I also see a file with a name something like batt_draw_current?
Indeed, I will complain to Samsung.
Original comment by JDHeinzm...@gmail.com
on 26 Jan 2011 at 8:32
Usually the file name contains current, although it's not always.
Let me know if anything changes.
Original comment by ran.ma...@gmail.com
on 27 Jan 2011 at 7:10
Original issue reported on code.google.com by
EnzoDeSa...@gmail.com
on 23 Nov 2010 at 10:15