Re: QtMoko v33 - More battery info and questions
Paul, On 2011-03-30 19:31, Paul Fertser wrote: Hi, On Tue, Mar 29, 2011 at 06:00:22PM +1100, Philip Rhoades wrote: Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 With USB unplugged this looks like a manifistation of a bug. Please specify the kernel version you use. Sorry, my mistake - I had it plugged in to get easier access to the device . . - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Incoming calls should wake up the device without any issues, there's a dedicated irq line for that. Yes, I tested it and it worked fine. I still have a problem with low battery life - I am testing the second new battery to see how that behaves and will update when I have more info. Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
Hi, On Tue, Mar 29, 2011 at 06:00:22PM +1100, Philip Rhoades wrote: Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 With USB unplugged this looks like a manifistation of a bug. Please specify the kernel version you use. - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Incoming calls should wake up the device without any issues, there's a dedicated irq line for that. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
Paul, On 2011-03-27 01:42, Paul Fertser wrote: Hi, Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/class/power_supply/battery/uevent POWER_SUPPLY_NAME=battery POWER_SUPPLY_TYPE=Battery POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_STATUS=Charging POWER_SUPPLY_VOLTAGE_NOW=387 POWER_SUPPLY_CAPACITY=55 POWER_SUPPLY_CHARGE_FULL=85 POWER_SUPPLY_CHARGE_NOW=459000 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/uevent DRIVER=pcf50633-mbc MODALIAS=platform:pcf50633-mbc /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/adapter/uevent POWER_SUPPLY_NAME=adapter POWER_SUPPLY_TYPE=Mains POWER_SUPPLY_ONLINE=0 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/ac/uevent POWER_SUPPLY_NAME=ac POWER_SUPPLY_TYPE=Mains POWER_SUPPLY_ONLINE=0 - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Those files are always present in the sysfs, kernel maintains them automatically for every driver. Right (thanks to Neil Jerram for clarification on this as well). - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Looking at this I realise that when the device is disconnected all the dimming etc has stopped working even the values are set correctly . . - Should the phone be shut down after the dumb battery is fully charged? No, charging is the same for gta02 battery and the dumb one, it's safe and doesn't require manual intervention. OK, good. Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v33 - More battery info and questions
People, Using: echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/unbind modprobe platform_battery allows me to check the value of: /sys/class/power_supply/battery/capacity and using: rmmod platform_battery echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/bind restores the smart battery function. I attach a graph of the resulting discharge rate of the fully charged Nokia BL-6C battery. Questions: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) - I would need at least 24 hours with light usage to be able to use the Neo as my regular phone. Is this battery performance typical? - Should the phone be shut down after the dumb battery is fully charged? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au attachment: ChkOMBattery.png___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
On 26 March 2011 09:54, Philip Rhoades p...@pricom.com.au wrote: People, Using: echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/unbind modprobe platform_battery allows me to check the value of: /sys/class/power_supply/battery/capacity and using: rmmod platform_battery echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/bind restores the smart battery function. I attach a graph of the resulting discharge rate of the fully charged Nokia BL-6C battery. Questions: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? I would guess not, because the .0 at the end of bq27000-battery.0 suggests that there might be multiple battery instances, of which, at a given moment, some might be bound and others not. If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Are you thinking that those echo commands create the files? I doubt it works like that; files in /sys and /proc are special, and it's more like echoing something into them causes some action to happen, or some config change. Cf. echo 1 /proc/sys/net/ipv4/ip_forward to enable IP forwarding. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
Hi, Philip Rhoades p...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Those files are always present in the sysfs, kernel maintains them automatically for every driver. - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. - Should the phone be shut down after the dumb battery is fully charged? No, charging is the same for gta02 battery and the dumb one, it's safe and doesn't require manual intervention. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
