maemo.org - Talk - [Announce] kernel-power stable v49 in Extras-Testing

Page 19 of 75

« First

< Prev

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - [Announce] kernel-power stable v49 in Extras-Testing (https://talk.maemo.org/showthread.php?t=71879)

Flandry

2011-06-13 13:45

Re: [Announce] kernel-power v47

Quote:

Originally Posted by rob42 (Post 1028019)

ok
have double checkec - no other camera ap.
next should I install the kernel ( plus qcpu - whic is what i used before)
then install the apps
then do a apt-get update to get the new fcamera driver.
or is there a better method.

thanks

I did "apt-get install fcam-driver". If that doesn't fix it then i'm afraid i'm out of ideas, sorry.

rob42

2011-06-13 14:38

Re: [Announce] kernel-power v47

have had to do a vanilla reflash.
in the process of returning to usual set up .
will have another look once this is done.
am concerned with the problems people have been having.

have just installed kernel with qcpu. restarted and stock camera is working fine? without installing any other drivers.
will try with bless900 next

update - all camera functions seem to be working. this is odd as orginally none of them would work after installing the new kernal

Hotshot

2011-06-13 15:02

Re: [Announce] kernel-power v47

Downloaded the new fcam drivers and the camera is working like a charm :)

Darkslayer

2011-06-17 19:06

Re: [Announce] kernel-power v47

I actually have the same problem as someone stated some time before.
I am using bh-214 headset.

The problem is following: connect headset to the phone and start to play music for some time and then pause (actually it can be
done even by pressing play/pause button with 1 second interval).
After that wait for ~5 minutes and try play it again.

Outcome: no sound on the first attemp to play but progression bar is going (at this moment if won`t press anything else you will hear somewhat of struggling sound, just a very short fragments), then if you try to play/pause again there will be no sound and progress bar fill frezze and then the headset icon will disappear and sound will continue playing in suppresed low quality mode.

Important to note that all these steps are going with quite heavy
lags.

I`m not quite sure is this kp related problem, but it just appeared after upgrading to v47. This stuff happening for some days already with 100% reproductivity.
Any clues about this?

titi974

2011-06-18 06:18

Re: [Announce] kernel-power v47

Same problem here but with my sennheiser mm450... appeared since last kernel-power v47 appeared !

michaaa62

2011-06-18 09:33

Re: [Announce] kernel-power v47

Please give some more info about your settings for kernel-power. Do you use a custom profile or one of the prebuild profiles? Do you tweak the cpu with some third widget/application? Which media player(s) do you use?

Darkslayer

2011-06-18 09:50

Re: [Announce] kernel-power v47

As for me i`m using default preset for kp, the only thing i`m doing is overclocking to 1ghz with kernel-config-limits 250 1000 command (though it set to be done through queen beecon, but i suppose it doesn`t matter).

I`m using standart media player, but i have found out that as lag is starting, you are not able to play any media file at all until you disconnect bt headset (i tried to play video with standart media player, with kmplayer (using different optional players including mplayer, npp and others)). The outcome in all players is the same: progress bar doesnt move and no audio or video is being played.

I believe that i`ve seen one time during this lag a hildon message saying sth about "error.... audio device is already in use", though i don`t remember what exatly it was saying.

m4r0v3r

2011-06-18 10:11

Re: [Announce] kernel-power v47

not sure why people are having problems with fcam mine works like a charm

Estel

2011-06-18 16:30

Re: [Announce] kernel-power v47

I would like to report other strange observation, which is for 100% related to kp47. After i upgraded it, even with bq27200blacklisted properly, current_now show higher value for both charging and discharging. And I'm NOT talking about fact, that it reports now more accurate value (by 2 degrees, i.e. 130000 instead of 1300) - so I'm not talking about most common false bug report here ;)

the thing is that, before update, current_now always showed (after correct calculations) that my standby usage is 70-100 maH with screen on, and charging with the same conditions occur at 400-500 mAh rate (give fact that phone is using 70-100 mAh for operation, so its really about 600 mAh that charger provide). Now, current_now return 150-180 mAh for standby, and 800-900 mAh for charging (+ 150-180 mAh for phone operation, as before = ~1A from charger).

I don't suppose my N900 to drain battery more quickly with kp47 (i didn't notice real life decrease in single battery operation time), neither I think that my charger started to put more heat into battery ;) I don't know if reading are screwed, or were screwed before and now are correct - i would like to know if other people noticed same thing.

// Edit

Before, i used kp46-wl1.

pali	2011-06-18 16:46

Re: [Announce] kernel-power v47

If you have bq27x00_battery blacklisted, you can't get current_now from bq module (it is blacklisted).

And if you are talking about bq module, in v46 was all values in bad units (22/3570 uAh or 22/3570 uA). Now in v47 is all in correct normalized units (1 uAh or 1 uA) So recalculate current_now from this units to uAh/uA.

Temporal

2011-06-18 23:29

Re: [Announce] kernel-power v47

Can someone that is using Shortcutd tell me if the proximity sensor is working under v47? I'm not that excited in upgrading, but I might if someone can confirm about the sensor.

Thanks.

Hurrian

2011-06-19 22:00

Re: [Announce] kernel-power v47

Quote:

Originally Posted by Temporal (Post 1031708)

Can someone that is using Shortcutd tell me if the proximity sensor is working under v47? I'm not that excited in upgrading, but I might if someone can confirm about the sensor.

Thanks.

Confirmed working, and it feels like I'm a Jedi Master for using it.

Estel

2011-06-19 23:40

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1031498)

Hey, i was sure that something is wrong here!

I'm 100% certain that i blacklisted module properly (checked many tiomes that

blacklist bq27x00_battery

i present in "/etc/modprobe.d/blacklist" without any typos, rebooted many times since adding it there), ho ever i still can get data from bq module (cat sys/class/power_supply/bq27200-0/current_now for example). If I'm wrong correct me, but i understand that it shouldn't be unavailable with module blacklisted?

---

Anyway, I un-blacklisted module - not having any issues so far.

Ho ever, bq report some data obviously wrong way... As i understand it - again, correct me if I'm wrong please - charge_full and charge_now is calculated using real current usage/charging in given time (current at the given moment can be checked by current_now), as opposed to charge_design, which is based on resistor in battery PCB and wrong most of the time.

Still, for just simple example, charge_now report for me 1300753 uAh (1301 mAh) and charge_full gives 1416040 uAh (1416 mAh) for battery that i know of being exactly 1100 mAh. I double checked battery both with RC charging equipment dedicated to all variants of Li-Ion batteries + discharging via resistor with time monitoring (i wanted to be 100% sure that my RC charger report correct value).

So, if my statements about how charge_now and charge_full should work are correct, they're obviously working wrong.

jpala16

2011-06-20 08:01

Re: [Announce] kernel-power v47

Regarding those incorrect outputs in KPv46, is there a way to correct that? Without upgrading kernel-power, of course. Yesterday I had to do a full reflash and I installed KPv46 (I had KPv47 before reflashing). I prefer to stay with v46, as I had some trouble with bluetooth, my car radio and http://wiki.maemo.org/Bluetooth_PBAP, with KPv47

Now, conky-n900 report -1.0ºC, and before (with KPv47) it reported the actual temperature. It isn't that important to me the temperature thing, but just in case. Thanks in advance.

pali	2011-06-20 08:21

Re: [Announce] kernel-power v47

Quote:

Originally Posted by Estel (Post 1032342)

I think that values reported by bq in v47 are correct. This values are reported by chip (not calculated and doing magick as BME). Note that DESIGN values is configured at factory and can be changed on chip (using i2cset). If I remeber FULL values are calculated from DESIGN after rechange.

You can read datasheet for this battery chip. Here are also explained registers (exported to kernel values) what contains:

http://focus.ti.com/docs/prod/folder...t/bq27000.html

If you think that there is bug in bq module, find maintainser/mailing list of battery submodule in http://git.infradead.org/battery-2.6...D:/MAINTAINERS and report bug. bq27x00 battery is in upstream (same version as in v47) so if there are bugs it should be fixed in upstream.

412b	2011-06-20 16:52

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1032515)

Nevertheless bq produces wrong values for me.

capacity

Code:

89

charge_full

Code:

78718

charge_full_design

Code:

2056320

charge_now

Code:

69615

current_now

Code:

199027

And since it uses uA, why values exported to HAL still use mAh? Whom should I file a bug?

pali	2011-06-20 18:26

Re: [Announce] kernel-power v47

First, this thread is about kernel and we are talking about bq kernel module and what it reports. So please do not use values from user space applications like HAL (it can do some magic or report some incorrect values...).

I see that some people have problems with units. mAh != uA... and I think that not all people know what which value mean. So here is info from power_supply subsystem kernel documentation:

Code:

Units:



  All voltages, currents, charges, energies, time and temperatures in µV,

  µA, µAh, µWh, seconds and tenths of degree Celsius unless otherwise

  stated. It's driver's job to convert its raw values to units in which

  this class operates.



CHARGE_* attributes represents capacity in µAh only.

CAPACITY attribute represents capacity in *percents*, from 0 to 100.



CHARGE_FULL_DESIGN, CHARGE_EMPTY_DESIGN - design charge values, when

battery considered full/empty.



CHARGE_FULL, CHARGE_EMPTY - These attributes means "last remembered value

of charge when battery became full/empty". It also could mean "value of

charge when battery considered full/empty at given conditions (temperature,

age)". I.e. these attributes represents real thresholds, not design values.



TEMP - temperature of the power supply.



TIME_TO_EMPTY - seconds left for battery to be considered empty (i.e.

while battery powers a load)

TIME_TO_FULL - seconds left for battery to be considered full (i.e.

while battery is charging)

And this is from bq27x00_battery driver:

Code:

CURRENT_NOW - battery average current in µA

===

@412b: What is wrong with your output?

412b	2011-06-20 19:11

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1033066)

@412b: What is wrong with your output?

Quote:

Originally Posted by pali (Post 1033066)

My values are from /sys and are correctly mapped in HAL, in fact (with unit conversion from uAh to mAh and uA to mA).
So... charge_full is measured in µAh. Nice. So I have a 78mAh battery ))) Straaange???

EDIT:
checked values in /sys/class/power_supply one more time...
At the moment I have charge_now=0 (zero) and device is normally working and will at least till morning, isn't that strange?

pali	2011-06-20 19:26

Re: [Announce] kernel-power v47

See again what is doc.

Code:

CHARGE_FULL, CHARGE_EMPTY - These attributes means "last remembered value of charge when battery became full/empty".

Maybe it is remembered incorrectly. And in bq27000.pdf doc is written that this value is updated on a valid learning cycle. Try to discharge and then fully charge battery again.

what is reporting BME?

colin.stephane

2011-06-20 19:35

Re: [Announce] kernel-power v47

Quote:

Originally Posted by 412b (Post 1033125)

I already tried to explain the behavior of this driver.

If you are interrested, please read from here : http://talk.maemo.org/showthread.php?t=71879&page=54

Read until you reach the message where I say the driver doesn't able to calibrate a new battery inserted in the device.

Same problem for me as you (bad report of current battery charge) with this driver, so, just blacklist it with this command as root :

Code:

clear && ID=$(id -un) ; if [ ${ID} != "root" ] ; then echo "You are not 'root', please use this command line as 'root' ..." ; else echo "Ok, you are 'root' ..." ; if grep -q "blacklist bq27x00_battery" /etc/modprobe.d/blacklist 2>/dev/null ; then echo "Patch already applyed, nothing to be done ..." ; echo "" ; else echo "Applying patch now ..." ; echo "blacklist bq27x00_battery" >>/etc/modprobe.d/blacklist ; echo "" ; echo "DONE, PLEASE REBOOT YOUR DEVICE ..." ; echo "" ; fi ; fi

The bme binary blob hack is here for this reason (at least this is the only reason I can understand ...).

A++

JadeH

2011-06-20 19:35

Re: [Announce] kernel-power v47

Since I upgraded to v47 my phone is stuck at the loading screen that has the 5 white dots in the middle and it won't move from there, any idea what's wrong?

I guess I'll just reflash the stock kernel and put v46-wl1 back..

412b	2011-06-20 19:41

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1033140)

See again what is doc.

Code:

CHARGE_FULL, CHARGE_EMPTY - These attributes means "last remembered value of charge when battery became full/empty".

BME is reporting something like 691mAh/1252mAh

I'll give a charge cycle a try and post the results.

412b	2011-06-20 19:46

Re: [Announce] kernel-power v47

Quote:

Originally Posted by colin.stephane (Post 1033151)

Read until you reach the message where I say the driver doesn't able to calibrate a new battery inserted in the device.

Unfortunatelly it's not new battery, but the stock one.

Quote:

Originally Posted by colin.stephane (Post 1033151)

Same problem for me as you (bad report of current battery charge) with this driver, so, just blacklist it with this command as root

Too much bash for just blacklisting a kernel module ))))))

pali	2011-06-20 19:56

Re: [Announce] kernel-power v47

Quote:

Originally Posted by colin.stephane (Post 1033151)

Quote:

Originally Posted by colin.stephane (Post 1004473)

If so, how can you explain that :

Code:

-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0 | grep battery.charge_level.percentage && lshal -u /org/freedesktop/Hal/devices/bme | grep battery.charge_level.percentage

  battery.charge_level.percentage = 56  (0x38)  (int)

  battery.charge_level.percentage = 95  (0x5f)  (int)

And what is your opinion about the right and the false value ???

You can trust me, the right is the one reported by bme !!!

A++

battery.charge_level.percentage = 56 (0x38) (int)
battery.charge_level.percentage = 95 (0x5f) (int)

This is because BME calculate chage_level as charge_now / charge_full_design * 100 and bq report chage_level from chip. Chip define chage_level as charge_now / charge_full * 100
So If you have new battery percentage should be same. But if battery is not new percentage cannot be same.

Quote:

Originally Posted by 412b (Post 1033168)

Unfortunatelly it's not new battery, but the stock one.

So should be problem with old used battery?

412b	2011-06-20 20:10

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1033188)

The difference in percentage is too big, IMO.

Quote:

Originally Posted by pali (Post 1033188)

So should be problem with old used battery?

Probably not. It's not that old to give zero values and keep working and working and working...
When I was writing previous post, I started playing a movie via WLAN from Mediatomb with all my accounts enabled and mail check... And battery is still not 0%.

JadeH

2011-06-20 20:13

Re: [Announce] kernel-power v47

even flashing the stock kernel didn't fix it, damn, i guess i have to reflash everything

pali	2011-06-20 20:17

Re: [Announce] kernel-power v47

Quote:

Originally Posted by 412b (Post 1033212)

The difference in percentage is too big, IMO.

Probably not. It's not that old to give zero values and keep working and working and working...
When I was writing previous post, I started playing a movie via WLAN from Mediatomb with all my accounts enabled and mail check... And battery is still not 0%.

Can you try run this script?
http://enivax.net/jk/n900/bq.tar

It show all info about battery. It use same way as bq kernel driver, but all in userspace with i2cget

mr_pingu

2011-06-20 20:18

Re: [Announce] kernel-power v47

But something strange is when BME says zero, and bq some more, still the device powers down. If you ask me it seems logical which value is wrong ;)

pali	2011-06-20 20:21

Re: [Announce] kernel-power v47

I know that BME show me 0% capacity (if bq is blacklisted too) and device can start again if BME (or MCE?) turn off it.

mr_pingu

2011-06-20 20:40

Re: [Announce] kernel-power v47

is it possible to turn BME off then, but how the bq driver does handle charging?

412b	2011-06-20 21:02

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1033226)

Can you try run this script?
http://enivax.net/jk/n900/bq.tar

It show all info about battery. It use same way as bq kernel driver, but all in userspace with i2cget

Code:

[user@Nokia-N900|~/bq]sudo ./bq27200.sh 

LOOPMODE=0

Reading values...........................done.



CSOC: 0 % RSOC: 0 %

Average Current: 429 mA

TTF: 65535 minutes TTE: 0 minutes

NAC: 0 mAh CACD: 0 mAh CACT: 0 mAh 

SI: 15 mA STTE: 0 minutes

MLI: 1028 mA MLTTE: 0 minutes

AR: 0 mA ARTTE: 65535 minutes

Last Measured Discharge: 78 mAh

Cycle Count since Learning: 98 Total Cycle Count since last full reset: 98

Reported Battery Voltage: 3569 mV

Battery Gauge die Temperature: 44 C

Flags:     0x10

     Charge:0 NOACT:0 IMIN:0 CI:1 CALIP:0 VDQ:0 EDV1:0 EDVF: 0

eeprom data:

     ILMD=2056 EDVF=3000 EDV1=3248 ISLC=20

     DMF=14700 nanoVolt SD=201 thousandths of percent per day

     AGELMD=1 TAPER=102 mA

     IMLC=1028 mA

I just stopped video playback.
About 72mAh according to BME.

Estel

2011-06-20 22:35

Re: [Announce] kernel-power v47

By "new battery" colin was talking about turning N900 off, replacing almost empty battery with freshly-charged one (charged externally, not in N900). He wasn't talking about new or old battery (age) AFAIK.

I understand that it's upstream module Pali and that You can't do much about it. Again, AFAIK as i know it work pretty well in notebooks etc, but for some reason doesn't work on our N900 as it should - maybe joerg_rw got more info why.

I reported it, cause - as documentation that you quoted said - charge_now and charge_full DOESN'T use charge_design to calculate value, but pull it from last know full and empty battery states, calculating uAh charged/discharged by monitoring current in given time. Technically, it works like advanced RC battery charger - with difference that RC battery charger charge/discharge with stable, given current (can change it when charging/discharging is almost done, to lower value) and measure time, with adjusting calculation when processor lower changing current for safe charge-finish.

Our N900 use different current all the time, depending on usage of device - chip act (via bq module) as super digital charger, adjusting calculations all the time, to get real uAh value. After few full charge/discharge cycles done internally on N900 (via USB charging) these values (charge_full and charge_now) should be quite correct - little lower than real battery capabilities, cause N900 discharge it only to 3,3 V.

Ho ever, in current approach, bq module reports much higher values than battery really posses (even after many cycles of charging/discharging), and i have no idea why.

Also, current_now value seems quite higher than it's really. If I got battery that i know have 1100 mAh, active usage of 200 000 uA - 300 000 uA (200-300 mAh) should drain battery in 4-5 hours. Ho ever, battery last much longer in tests. Also, as i mentioned reported values for "charge_full" and "charge_now" are higher that it should be. Mixing it with wrong current_now values, internal calculations are correct, except that higher than it should be. Higher current_now readings result in higher charge_full and charge_now values.

Maybe that 22/3570 uA value (instead of 1 uA) in kp46 was there on purpose? I wonder if current, patched bq module, just adjusted to operate at "wrong" 22/3570 uA values could provide real charge_full and charge_now data... Maybe data pulled out from chip is wrong, and that "incorrect" value put in bq was there in fact to correct it, to adjust calculations by error factor?

I would LOVE to have working charge_full and charge_now values (of course, also charge_empty), because that would allow everyone with kp to quite precisely measure real battery capacity in mAh (after calculating it from uAh), so everyone could contribute to threads like "battery test", and check if super-uber advertised battery really have it advertised capacity.

iscio

2011-06-21 12:07

Re: [Announce] kernel-power v47

is it possible to add °C to
echo $(cat /sys/class/power_supply/bq27200-0/temp) | awk '{ print $1/10}'
I am not able to to this

pali	2011-06-21 12:24

Re: [Announce] kernel-power v47

Quote:

Originally Posted by mr_pingu (Post 1033268)

is it possible to turn BME off then, but how the bq driver does handle charging?

bq27x00 chip has nothing with charging. It reports battery status.

pali	2011-06-21 12:32

Re: [Announce] kernel-power v47

@Estel:

bq driver in kernel power v46 is old and reported bad units. it was because people who started initial support badly read (or not read) datasheet. Note that we have kernel 2.6.28 and upstream is 2.6.39.

If you are interesting in fixing bq driver you can see datasheet for our battery chip:
http://focus.ti.com/docs/prod/folder...t/bq27000.html

And also source code of our kernel driver:
http://tomoyo.sourceforge.jp/cgi-bin...7x00_battery.c

And you wrote that this driver may work on netbooks, but not on n900. Why? bq chip must be same (Do you think that TI created special battery chip for n900? With same name?). This bq chip is not for charging battery.

pali	2011-06-21 12:45

Re: [Announce] kernel-power v47

Quote:

Originally Posted by iscio (Post 1034586)

is it possible to add °C to
echo $(cat /sys/class/power_supply/bq27200-0/temp) | awk '{ print $1/10}'
I am not able to to this

Code:

echo $(cat /sys/class/power_supply/bq27200-0/temp) | awk '{ print $1/10, "°C"}'

pali	2011-06-21 13:26

Re: [Announce] kernel-power v47

Quote:

Originally Posted by 412b (Post 1033308)

Code:

...

Last Measured Discharge: 78 mAh

...

...
About 72mAh according to BME.

I think this is OK. BME and bq script reports same values. +/- 6 mAh should be OK.

Is bq kernel module reporting same values as bq script?

412b	2011-06-21 14:46

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1034708)

I think this is OK. BME and bq script reports same values. +/- 6 mAh should be OK.

Indeed, it was measured with a little time difference, so it was totally ok for almost empty battery, not for the charged one.

Quote:

Originally Posted by pali (Post 1034708)

Is bq kernel module reporting same values as bq script?

Unfortunatelly, yes, but it's wrong. I've got a fully charged battery at the moment and it still shows 78mAh, so doing full discharge/charge cycle didn't help.

I guess there should be a method to start bq learning again... Gotta read docs when get home.

Or bq isn't learning properly...

iscio

2011-06-21 14:50

Re: [Announce] kernel-power v47

Quote:

Originally Posted by pali (Post 1034642)

Code:

echo $(cat /sys/class/power_supply/bq27200-0/temp) | awk '{ print $1/10, "°C"}'

thank you very much

pali	2011-06-21 14:53

Re: [Announce] kernel-power v47

Quote:

Originally Posted by 412b (Post 1034843)

Indeed, it was measured with a little time difference, so it was totally ok for almost empty battery, not for the charged one.

Ok.

Quote:

Originally Posted by 412b (Post 1034843)

Unfortunatelly, yes, but it's wrong. I've got a fully charged battery at the moment and it still shows 78mAh, so doing full discharge/charge cycle didn't help.

So if are same, there is no bug in kernel driver (or in script is same bug as in kernel driver if exists).

Quote:

Originally Posted by 412b (Post 1034843)

I guess there should be a method to start bq learning again... Gotta read docs when get home.

Or bq isn't learning properly...

So there may be bug in chip? Or I think that this chip can be configured (as written in datasheet some battery option can be configured). Could BME configure this chip to retrun "bad" values and BME monitoring bq chip and calculate its own values?

All times are GMT. The time now is 00:11.

Page 19 of 75

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8