Re: [Announce] CSSU Testing thread
 

I believe I'm using the latest version of the applet and I get the low battery warning chimes when I go to last 5%, but I have taken the battery to 0% (there was 5mAh left) and it didnt trigger autoshutdown. I have bq27200@ installed, but I'm not sure if the battery is currently calibrated (I have two different batteries that I sometimes swap).

Re: [Announce] CSSU Testing thread
 

+1

ten chars

Re: [Announce] CSSU Testing thread
 

/apps/osso/status-area-applet-battery/use_design_capacity

I agree that some documentation should be available.

Re: [Announce] CSSU Testing thread
 

FWIW, I also noticed a strange behaviour of the battery applet. The indicator not changing to red in the last 5%, reports of 345/254 mAh with the number saying 100% but the icon showing less than half full, reports of 0% for a few hours before auto-shutdown... I attributed it to a lack of proper calibration and indeed, letting it run down completely to 0 and then recharge to the full helps but not for long. It started happening out of the blue. My battery applet version is 1.0-8.

Re: [Announce] CSSU Testing thread
 

now documentation is only in git commit which introduced that gconf key... sorry but I cannot dig now...

Re: [Announce] CSSU Testing thread
 

and note, when you are *not* using bme replacment there should not be any problem with design capacity. applet should report what stock bme tell it...

so it looks like applet has still some bugs :-( I thought that it working fine now, so I proposed it to cssu-testing. but it looks like that our sw will be tested more after it enter -testing repo...

Re: [Announce] CSSU Testing thread
 

AIUI those fake values for charge/capacity are not really a fault of the applet - sometimes BME goes nuts and reports bogus values for last charge and remaining capacity. Maybe those should be ignored (if capacity change from the last reported value is more than lets say 5%, use the old value), dunno :)

Re: [Announce] CSSU Testing thread
 

That's OK, it's exactly what cssu-testing is (should be) for. The only thing that could be done better is some documentation when such "big" new features are implemented*, as it would help avoiding confusions/help identifying what is bug and what is a feature ;)

/Estel

*I know, new battery applet isn't "big" in itself, but it is *big* relatively - it is one of the most commonly used UI feature, and it wasn't touched, changed, and presented for mass consumption since dawn of times, i.e. at least since Nokia's PR upgrades ;)

Re: [Announce] CSSU Testing thread
 

Last version of CSSU-testing modify /etc/default/mount-opts by adding:
to...
Rationale?

Cheers,
/Estel

Re: [Announce] CSSU Testing thread
 

stock maemo uses data=writeback,noatime,commit=1, iirc

Re: [Announce] CSSU Testing thread
 

I know, but in past version of CSSU, this option was omitted. Is there any rationale for forcing commit=1 for root, or was it done just to be like vanilla? If the latter is the case, then, noexec for MyDocs should be kept too, while CSSU lifted it.
---

From totally different barrel of vine - I've tried setting up /apps/osso/status-area-applet-battery/use_design_capacity gconf key to 0 (int), but it doesn't seem to help. I still see 1267 as max capacity, despite having higher current capacity (and real max capacity about 3300 mAh).

/Estel

Re: [Announce] CSSU Testing thread
 

I've tested status-area-applet-battery and it's gconf key back and forth. The result is
Bug 12723.

Cheers,
/Estel

// Edit

BTW, i noticed, that Pali's mail isn't on the auto sentto mail list for CSSU bugs. Just in case it isn't deliberate, but just overlooked.

Re: [Announce] CSSU Testing thread
 

I recently bought a Polarcell 1500mah battery (to an ebay seller recommended in TMO) and for me it shows his charge and his maximum as it would be like the normal BL-5J battery. I use last cssu-thumb version. Din't tried with previous one (And won't take risks, I have no microusb port, I use an external charger).

Re: [Announce] CSSU Testing thread
 

@malkavian, did you calibrate your battery?

Re: [Announce] CSSU Testing thread
 

No, but now I use the two batteries, wouldn't it be a problem?

Re: [Announce] CSSU Testing thread
 

@hxka, he can't use the calibration script since his USB port is broken.

Meanwhile, this is what I was talking about a few posts back. Battery nearly empty but the icon did not turn red. I had another case yesterday saying 100%, 1205/484 mAh, but I failed to take a screenshot.

Re: [Announce] CSSU Testing thread
 

Oh, I forgot that to obtain vdq you have to charge it with USB. Oops!
Anyway, if you are using two different batteries, you can't have correct readings for bof of them.

Re: [Announce] CSSU Testing thread
 

Then I think it will be better for me, to have the new one (of 1500mAh) correctly measured and know that when battery status says that the old battery have 300 / 1500 it really have 82 / 1500. So I could change it when nearing that number.

Now when using new 1500 battery, it last a lot of time with 0/1282, so I don't know when it is really near end.

Yes I know, I can recharge Litium batteries when I want, but I obviously prefer to change of battery less often, and benefit from that extra 300mAh.

¿Could I do that?

Re: [Announce] CSSU Testing thread
 

Unfortunately, no. As @pichlo pointed out, you can't recalibrate the battery without an usb port.

Re: [Announce] CSSU Testing thread
 

Well, actually, if you have *only* USB port damaged, but all chips/peripherals OK, you could charge and calibrate using testpads under battery. Heck, you could even create a permanent workaround USB (both data and charging) this way.

But, a) it requires lottsa effort b) it's off-topic here. See "repairing usb port before and after it's too late" thread for further info.

/Estel

Re: [Announce] CSSU Testing thread
 

I've also been having awkward behavior since updating to the latest CSSU-T.

When I first upgraded, It reported ~1200 mah capacity. I currently have a Scud battery that I purchased apparently rated at 1440 mah. For the longest time my meter stayed at 5%, almost for half a day without a low battery alert or warning until it finally shut off on its own. When it restarted it then showed a capacity of ~1500 mah. This was about three days ago.

Right now as I read this thread, I peek at my capacity and it shows this
http://i.imgur.com/CmyS9yX.png

I'm not sure when this happened or what caused it. Before I took the screenshot I had just unplugged it from a full charge from my laptop (several minutes passed).

Re: [Announce] CSSU Testing thread
 

1500 mAh is you relative capacity - when it discharged "to the end", it calibrated itself. Now, 900-something mAh is your "design capacity", as reported by resistor, and of course, is total BS. It shouldn't be ever, even for a second, considered as any reliable source - either default, or, IMO, even optional. But, for that or this reasons, it is default for max capacity (you *should* be able to change it to bq27x00_battery data, but it doesn't seems to work right now, see my bug report).

Now, AIUI, the "fake" battery full report (green diode and all stuff) is because new applet reports full battery as soon as it reaches fake 100%, i.e. 900 mAh. You could check it using BNF (from repos, shameless advert ;) ) to see if your battery is really full, when it says so. I bet that when you seen green diode, ti was still chargin @ ~200mA rate, and it would do so, until real full - ~1500 mAh - is hit.

Cheers,
/Estel

Re: [Announce] CSSU Testing thread
 

How does the resistor explain that the same battery reports 1181/1203 mAh one day and 1212/484 mAh the next? No shutdown, no reboot, just a simple recharge in between.

Re: [Announce] CSSU Testing thread
 

10 characters

Re: [Announce] CSSU Testing thread
 

No, this is "battery.reporting.last_full" property of "/org/freedesktop/Hal/devices/bme", in order to use the resistor values, one should set "use_design_capacity" to "2".

However, a workaround should be implemented here, though I am not sure what exactly, need to think for a while.

Re: [Announce] CSSU Testing thread
 

alarm automaticly close

Re: [Announce] CSSU Testing thread
 

Thanks Estel. I already know read that, but as you say it requires lot of effort and my habilities with electronics are not very good.

A friend re-soldered a new usb port, but after some days it went loose and broke again. So I decided to not bother him more, and survive with an external charger until I get a Jolla or Neo900...

Re: [Announce] CSSU Testing thread
 

alarm = clock app?

In that case: what is the output of running "/usr/bin/worldclock" in xterm?

Re: [Announce] CSSU Testing thread
 

when we are on alarm - I've noticed strange, reproducible bug with new alarm (I think it might be reported before, but I can't find it now, so I'm not sure):

When your battery dies between setting active alarm and triggering it, on next boot - even if it's hours and hours after alarm deadline - you get alarm window early after hildon starts, without sound. If you tell it to stop, then hildon finish loading, alarm sound start to play, and it is impossible to shut it up by any means, other than shutting whole device down.

I've encountered it using latest version of cssu-testing, thumb flavor.

/Estel

Re: [Announce] CSSU Testing thread
 

I am sorry for my poor English.I can't express myself clearly.

It happened when I edited some alarms.

Re: [Announce] CSSU Testing thread
 

Maybe your alarmfile is corrupted. Do alarms still ring? You could try from xterm (as one sentence):
and try again?

if it makes no differences, restore the file:

Re: [Announce] CSSU Testing thread
 

To avoid confusion here: when you are speaking of "bug with new alarm", it's about the systemui-alarm part, not clock-ui, right?

Re: [Announce] CSSU Testing thread
 

Yes, systemui-alarm, at least as long as my uneducated guess about what is responsible goes.

Re: [Announce] CSSU Testing thread
 

how to install cssu feature in my nokia n900 ...???give the step by step procedure.....

Re: [Announce] CSSU Testing thread
 

read first page, go on wiki and follow to step by step instructions

Re: [Announce] CSSU Testing thread
 

thank u ....murik... :)

Re: [Announce] CSSU Testing thread
 

I know it won't be "politically correct", but some food for thoughts, for CSSU-deciding people (this and following post):
http://talk.maemo.org/showthread.php...2&page=46&#455

Cheers,
/Estel

Re: [Announce] CSSU Testing thread
 

Quick question:

Where is the swap enabled after the latest CSSU update?
It used to be rcS-late but that doesn't exist any more!

nm, it's there, I'm on crack.

Re: [Announce] CSSU Testing thread
 

Did i miss something? Mine is still enabled from /etc/event.d/rcS-late config file.

Re: [Announce] CSSU Testing thread
 

Sheesh, I looked in the wrong dir...thanks