Active Topics
-
Porting apps to Leste (32)
to Maemo 7 / Leste by Arno_11 - 1 day, 8 hrs ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 3 days, 2 hrs ago -
Full linux distros on Sailfish OS (254)
to SailfishOS by qoh - 4 days ago - more...
|
2011-06-21
, 15:34
|
|
Posts: 462 |
Thanked: 550 times |
Joined on Sep 2008
@ Moscow
|
#762
|
Originally Posted by pali
Probably, there is the same bug. When I get home, I'll test with another battery.
So if are same, there is no bug in kernel driver (or in script is same bug as in kernel driver if exists).
Originally Posted by pali
If it's a bug in chip, then how BME goets its data... I do also think that chip could be configured and don't know if BME messes the values...
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?
 |
|
2011-06-21
, 23:39
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#763
|
It's possible that BME was adjusted to include in it's calculations how differently was bq chip set for reporting values - my last post was all about that.
Unfortunately, fixing driver (or module or whatever
) is far beyond my skills - at least for now. Ho ever, i still can't understand why all values now are higher than it should be by stable same factor. Value reported by current_now is higher than it should be as it's multiplied by given x, and so is charge_full and charge_now also multiplied by exact same x. That's why internal calculations remain sane, but are wrong overall. As Pali noticed, it's most unlikely for TI to create custom chip with same name just for N900, still, bq module work as it should on netbooks/notebooks, and for us on N900 it reports wrong values. That's I'm sure for certain, just don't know why.
I think best i can do in such a situation - for now - is to measure as precisely as i can factor of drift (given x), then write a simple script that will calculate real values from drifted values and print them on screen. Then, of course make it public to those few who cares about precise real battery capacity (in mAh) measurement done using N900 only.
Unfortunately, fixing driver (or module or whatever
) is far beyond my skills - at least for now. Ho ever, i still can't understand why all values now are higher than it should be by stable same factor. Value reported by current_now is higher than it should be as it's multiplied by given x, and so is charge_full and charge_now also multiplied by exact same x. That's why internal calculations remain sane, but are wrong overall. As Pali noticed, it's most unlikely for TI to create custom chip with same name just for N900, still, bq module work as it should on netbooks/notebooks, and for us on N900 it reports wrong values. That's I'm sure for certain, just don't know why.I think best i can do in such a situation - for now - is to measure as precisely as i can factor of drift (given x), then write a simple script that will calculate real values from drifted values and print them on screen. Then, of course make it public to those few who cares about precise real battery capacity (in mAh) measurement done using N900 only.
|
|
2011-06-22
, 12:26
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#764
|
For all who has problems with bluetooth:
Only one bluetooth related patch between v46 and v47 is which fix l2cap NULL dereference in l2cap_conn_start. It was taken from: https://bugs.maemo.org/show_bug.cgi?id=10510
Everybody who has problem with bluetooth please run these commands (but after bluetooth problems apperes) and write here ouptut:
Only one bluetooth related patch between v46 and v47 is which fix l2cap NULL dereference in l2cap_conn_start. It was taken from: https://bugs.maemo.org/show_bug.cgi?id=10510
Everybody who has problem with bluetooth please run these commands (but after bluetooth problems apperes) and write here ouptut:
Code:
dmesg | grep avoided dmesg | grep l2cap
 |
|
2011-06-22
, 15:17
|
|
Posts: 968 |
Thanked: 663 times |
Joined on Jun 2010
@ Australia (Melbourne/vic) / Lebanon (Zgharta/north)
|
#765
|
any news on a close update ?
__________________
rolling down the street, smoking ENDO, sipping on gin and juice
laid back, with my mind on my money and my money on my mind .
rolling down the street, smoking ENDO, sipping on gin and juice
laid back, with my mind on my money and my money on my mind .
|
|
2011-06-22
, 15:33
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#766
|
Originally Posted by elie-7
See this: http://talk.maemo.org/showpost.php?p...&postcount=668
any news on a close update ?
|
|
2011-06-22
, 15:45
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#767
|
Originally Posted by pali
Just compile it and upload to dev repositorys. The users of dev test it. Thats what dev is for.
I included both patches to my git repository, but I didnt test it yet.
New kernel-power release wont be before july. Now I do not have time for testing kernel-power... (school)
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
|
|
2011-06-22
, 15:51
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#768
|
Originally Posted by vi_
Now I cannot compile n900 kernel and pack it into deb packages. I chaged laptop where I do not have configured madde (I hate scratchbox). And I chaged debian scripts in my git tree - so now it is maybe uncompilable...
Just compile it and upload to dev repositorys. The users of dev test it. Thats what dev is for.
My git tree is public, so everybody can clone and try to compile it!
 |
|
2011-06-22
, 22:11
|
|
Posts: 4,365 |
Thanked: 2,467 times |
Joined on Jan 2010
@ Australia Mate
|
#769
|
anyone care to do this? (someone able, i.e. not me)
__________________
N9 / N900 Youtube Videos
N9 "Faster, Darker, Better" Theme Pack
---
www.F2thaK.com
N9 / N900 Youtube Videos
N9 "Faster, Darker, Better" Theme Pack
---
www.F2thaK.com
 |
|
2011-06-23
, 12:50
|
|
Posts: 162 |
Thanked: 64 times |
Joined on Mar 2011
|
#770
|
Originally Posted by jpala16
I wouldn't be so sure that is due to KPv47. On saturday I installed some preenv games. Then I rebooted. I saw that some Queen Beecon widgets were set as default icon and commands and I thought "What happened here?" and rebooted again to see if it was all right again. And I entered an endless loop of reboots. Finally I had to reflash kernel and eMMC.
Now I've installed the same games, have those widgets again and it works like a charm. Finally I upgraded from kernel power v46 to v47 (I hate to stay out of date).
Conclusion: It could be whatever.
But I didn't install new things (or even change my homescreen, or anything) on my n900 in weeks, and it rebooted fine a few hours before i upgraded
I'll try reflashing kernel+emmc and putting v47 back, hopefully that fixes it
 |
| Tags |
| battery-status, bq27x00_battery, kernel, kernel-power, misiak4king, noobs-cant-read, pali4president, patches, readdirections, revolverspinyou |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 19:29.
Now I've installed the same games, have those widgets again and it works like a charm. Finally I upgraded from kernel power v46 to v47 (I hate to stay out of date
Conclusion: It could be whatever.