Re: [Announce] CSSU Testing thread
 

Here are both log files. I apologize if my previous post was vague.
Note: the telephone was stationary all this time.
Best wishes.
__________________
Per aspera ad astra...

Re: [Announce] CSSU Testing thread
 

In log I see:
This means that your phone really alternates between two BTS.

Re: [Announce] CSSU Testing thread
 

But this broadcasting towers have the same tower name. Is it possible to tweak the code so that the tower name would still be displayed, despite the altercation of two broadcasting stations? Right now, it's not displayed at all, 99.99% of the time.
Thank you. Best wishes.
__________________
Per aspera ad astra...

Re: [Announce] CSSU Testing thread
 

And what to display? If GSM chip reregister to other station data from old station are invalid, so applet will remove location. If new station send location again, applet will show it.

Re: [Announce] CSSU Testing thread
 

Pali can you also release an update for the satus area battery icon to make it show the data that your app battery percentage is showing ? currently battery icon showing battery totally empty but it still having 26 percent battery left. is its possible ?

Re: [Announce] CSSU Testing thread
 

DEB package from this thread is compiled into debug mode which case debug output in syslog. battery applet from cssu-devel is not in debug mode. So look into syslog for info which hald-addon-bme sending to applet.

Re: [Announce] CSSU Testing thread
 

This could help:

1. (Terminal, sudo) 2. Delete the underlined folder: /opt/maemo/usr/lib/advanced-power-monitor (with filebox for example)

3. reboot

4. (Terminal, sudo) 5. reboot

Re: [Announce] CSSU Testing thread
 

Why is it that in the CSSU Thumb Thread they are talking about bugs in CSSU Testing but the only bug that I see reported here is this one:
Are there other bugs?
Thanks!

Re: [Announce] CSSU Testing thread
 

vetsin,


I don't know if the above is a bug but saw this in the thumb thread too ;)

Re: [Announce] CSSU Testing thread
 

Yes the above mentioned statement is true
there is a bug in hildon-desktop continously using CPU
me facing the issue
please others also confirm this, use this command
top -d1

Re: [Announce] CSSU Testing thread
 

In my case (two devices running latest Testing) no changes with battery usage. Hildon-Desktop in ''top'' using ~ 0,2 CPU.

Re: [Announce] CSSU Testing thread
 

do you have cssu-thumb installed on your device ?

Re: [Announce] CSSU Testing thread
 

Can you confirm it happens when you have no widgets on your desktops? (could you do a simple test: remove all widgets, reboot phone, check if it's still using cpu?)

Re: [Announce] CSSU Testing thread
 

Do shortcuts count? I have no widgets, only some shortcuts. And I haven't this issue.

Re: [Announce] CSSU Testing thread
 

With that question I wanted to address only the ones that experience higher cpu usage, to confirm that the issue is in some unknown place in hildon-desktop and to rule out widgets fault ;) But anyway, thanks for reporting that everything works for you :) All works for me ok, too, and I have no widgets at all (cssu testing is installed on my second device which i rarely use).

Re: [Announce] CSSU Testing thread
 

i confirm this. removed widgets and bookmark icons from desktop and also gave N900 a restart but still same problem. hildon-status-menu is using 2.7 percent cpu and hildon-desktop using 1.2 percent cpu. Any solution for it ? It draining my battery pretty quick :(:(:(

Re: [Announce] CSSU Testing thread
 

No Sir, I don't use it since Testing 5.1 And now on Testing 6 there is no point to change it.

Re: [Announce] CSSU Testing thread
 

i have a question...
does cssu is still develloped?
Cause i fee like there is no more works on it...

Re: [Announce] CSSU Testing thread
 

you know this is kinda insulting for the devs? last cssu testing update was pushed to the repos barely 2 weeks ago - how do you think that could mean it's not developed? what else would you expect, for free? (it's, after all, for free and cssu devs do it in their free time)

Re: [Announce] CSSU Testing thread
 

check it yourself and draw your conclusions

https://gitorious.org/community-ssu

Re: [Announce] CSSU Testing thread
 

Speaking about camera..

I'm having some isues with my camera, it just closes after taking a couple photos or recording a not too small video.

Re: [Announce] CSSU Testing thread
 

Sorry to sound instructive, but is that supposed to be a bug report or a rant? As usually bug reports include dmesg log, syslog, coredump, way to reproduce, etc. After all CSSU-testing is that - testing, i.e. stability is not guaranteed (not that one can guarantee lack of bugs in any random software). And its users are supposed to help the developers to iron it.

Please, give some useful info, we(developers) are not gifted enough to be seers.

Re: [Announce] CSSU Testing thread
 

oook... That was part of a bigger message, but i found how to solve the other issue almost instantly after writing it.
Is not a rant, i just took a part of the explanation when deleting the other issue.

Anyway ¿What should i explain better?
My camera program closes after a couple of photos or after recording a video even when is not too long or in HD.

This wasn't happening some time ago and there was nothing that i could have changed accidentally or incidentally because my WiFi has been disabled for months and i dont have a data package contracted. Also I was using the camera without any issue and recording HD videos after making all installs i need and/or "important" changes.

The only thing i do from time to time is to enable WiFi and let it update but not more than once a month.

First i thought it could be the battery because i bought a brand new, then i went back to the original one, but it happens with both batteries and even after a couple minutes of charging completed.

I tought it could be a bug from an old update so i was hoping that with this last CSSU update something may be addressed, but there is no improvement (for my case)

I asked mainly because i thought there may be some other person with a similar or the same problem, or maybe there could be a known bug. I have asked some stuff in the past and i obtained some answers because there were known issues or people with something similar. I was not hoping for any better thant just that.


Now, if you think that my msg. is out of order, i really don't care if you erase it or just ignore it, i was asking for an answer just in case there were someone on the mood to share some knowledge.
I mean no disrespect and i know there is too much people asking for solutions without giving enough basic information, but i just don't think this was something to annoy someone that much as you seem to be.

Sorry for the inconvenience and thanks for your time.

Re: [Announce] CSSU Testing thread
 

no disrepect intended richardn900.

i see reports like this while looking after conky-colors. a kind of basic "it don't work" report with not much info, so you then spend ages back and forth trying to recreate the issue. Maybe we should put a sticky post at the top of each sub board detailing what to include in a post and how to get the info should a problem occur.

I'm aware it has been posted before in the middle of a thread and probably in the wiki but for those who don't know where to find it we need something that jumps out as soon as you go on the forum.

Re: [Announce] CSSU Testing thread
 

@RichardN900 - I'll try to explain it again:

CSSU-testing is the tool used to find the bugs that have sneaked, no matter what tests the developers have done. It is assumed that by installing CSSU-testing, you take the responsibility to provide information back to developers, to help them fix the outstanding problems. Your camera-ui "closing after a couple of shots" most probably means it SEGFAULTs (whatever it means :) ). The point is that you can contribute and help make things better by installing a couple of tools on your device, gathering the logs and providing a bug report with those logs attached.

The tools you need to install:

http://wiki.maemo.org/Documentation/.../maemo5/syslog
http://wiki.maemo.org/Documentation/...5/sp-rich-core

after recreating the problem, please raise a bug:
https://bugs.maemo.org/enter_bug.cgi...ommunity%20SSU

attaching your dmesg output, syslog and coredump, along with steps to recreate the problem (if possible), along with any other info you think it might be related.

By following the above, you may have your problem solved and it can help developers to fix the code and make it more robust.

CSSU and this very thread are not a support service, it is made by community members for community members. In their spare time. So, more information you provide, the bigger are the chances less part of that spare time will be used for fixing the bugs and more will be used to develop new functionality, etc.

Re: [Announce] CSSU Testing thread
 

Yep, "how to report a bug against CSSU and what info to provide" should be on wiki. Unfortunately it is not (or at least I cannot find it) and now wiki disallows edits it cannot be added :(

Re: [Announce] CSSU Testing thread
 

Now see, there's a lot of info. i didn't know, i tought that logs were on the phone and i just needed to go an seek for the correct one. Only i usually don't know where they are (/var/log, /usr/log) and on maemo seems to be some folders out of the "standard" linux location. (anyway)

I asked mainly thinking about some other people who may have the same problem... I tought that by now there would be several others explaining their issue and/or solution/workaround.

I'll check what you put there, install what's needed and give the appropriate logs.

¿Is my cellphone going to get more laggy with that tools on? Because i think is a bit laggy too much. (only after a full clean -sms/chat/calls history- it gets back to "normal".)


Thanks for the time.

Re: [Announce] CSSU Testing thread
 

you only need have them installed until you gather the info required, after that its up to you. i personally remove them to avoid unnecessary disk writes.

Re: [Announce] CSSU Testing thread
 

Guys, I have a problem...
I've updated something (not sure what package it was) via apt-get update in x-term and wracked my device. Every second or two "internal error. Application 'Web' closed" pop up & I'm not even using micro-B at that moment.
What to do?

Tnx in advance...

Edit: Also, I can't start internet, mail, games, phone function...

Re: [Announce] CSSU Testing thread
 

Sounds like your browser's stuck in a crash loop. Try running "killall browser; killall browserd" in the terminal, this will keep it from running until the next time you launch it manually IIRC.

Next try (as root) "apt-get install --reinstall osso-browser"

Re: [Announce] CSSU Testing thread
 

So strangely I have also started to get these messages. Also for E-mail and occasionally for Phone. I can't start most of my applications except some core maemo ones (media player, calendar, contacts etc. E-mail crashes as soon as I open some mail folder. Web does not start at all. As also Open Media player, Marble, gps-recorder, StellariuMobile etc. I'm at cssu-testing + cssu-devel + kernel power 52.
The last thing I installed was a new libpng from cssu-devel but after that the phone worked OK.
The last thing I did before it happened, was for testing kp52:
stop bme
modprobe bq27x00_battery
modprobe bq2415x_charger
The battery still showed o%, so I started bme again and the phone rebooted.
After reboot these messages ("Internal error. Application 'Web' closed") started to appear...
I do not think it is strictly related to cssu-testing though...
Any ideas besides reflash...
And yes, I searched talk.maemo.org forums on that problem before posting :)

Re: [Announce] CSSU Testing thread
 

Did you upgrade to the latest libpng from cssu-devel (http://talk.maemo.org/showpost.php?p...6&postcount=48?)

If so, revert back to the previous version. This latest version gave me a lot of issues, Luf is looking at it.

Re: [Announce] CSSU Testing thread
 

[QUOTE=ade;1306452]Did you upgrade to the latest libpng from cssu-devel (http://talk.maemo.org/showpost.php?p...6&postcount=48?)

Kewl...but, how to do that?

Re: [Announce] CSSU Testing thread
 

[QUOTE=branja;1306523]Already covered: http://talk.maemo.org/showpost.php?p...1&postcount=58

Re: [Announce] CSSU Testing thread
 

Thanks, that did the trick - everything seems to be normal again :)

Re: [Announce] CSSU Testing thread
 

"Version 1.2.37-1maemo3+0m5" for "libpng12-0" was not found.

What 2 do?

Re: [Announce] CSSU Testing thread
 

You can always get the deb here by hand: http://maemo.org/packages/package_in...7-1maemo3+0m5/

Re: [Announce] CSSU Testing thread
 

just a general notice:
DO NOT INSTALL STUFF FROM CSSU-DEVEL unless you know exactly what you're doing!
CSSU-Devel is meant for generally buggy halfbaked stuff that devels of CSSU like to play with, it's by no means meant for any "end user", not even the usual CSSU-T or CSSU-Thumb testers. If you install a package from CSSU-Devel, you do that because you want to help developing that package, and you anticipate and expect that package from *devel to be buggy - that's why you install it from there so you can work on the bugs.

Cheers and merry christmas
jOERG

Re: [Announce] CSSU Testing thread
 

A new update (Tmaemo7) will hit the repos shortly and since the wiki is still foobar I'll post the changelog again:

Re: [Announce] CSSU Testing thread
 

I have a problem with BME Replacement, probably specifically with userspace daemon hald-addon-bme.
If the Kernel-CSSU install, it correctly displays the battery charge (from 0 to 100%), but it does not correct working LED - constantly orange light (not blinking) when charging, and constantly green light when fully charged, on even after disconnecting from the charger.
If the Kernel-Power52 install, the LED is working correctly, but the total charge is shown from 107 to 112%!