maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)
-   -   [Announce] CSSU Testing thread (https://talk.maemo.org/showthread.php?t=80525)

pali 2012-11-10 13:45

Re: [Announce] CSSU Testing thread
 
@toxaris:

Now I see where is problem.

First is that your battery is not calibrated. In this state applet should report "0/0" (instead some bad and uncorrect values).

Second problem is in bq27x00_battery kernel driver. It does not report capacity in % or last full capacity if CI flag is set (when battery is not calibrated). But it report current mAh also when CI flag is set which lead to total mess in status menu plugin.

How to solve first problem: (Stop bme) load drivers and discharge battery until capacity be about 7%. You can also you bq27200.sh script for monitoring EDV1/F LOW flag. After battery will be empty, charge it to full and discharge again.

Now going to fix second problem. Thanks for finding & reporting bug in kernel.

pali 2012-11-10 14:38

Re: [Announce] CSSU Testing thread
 
Second problem should be fixed in last prerelase version of kp52: http://talk.maemo.org/showpost.php?p...&postcount=261

toxaris 2012-11-19 06:45

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by pali (Post 1292682)
@toxaris:

Now I see where is problem.

First is that your battery is not calibrated. In this state applet should report "0/0" (instead some bad and uncorrect values).

Second problem is in bq27x00_battery kernel driver. It does not report capacity in % or last full capacity if CI flag is set (when battery is not calibrated). But it report current mAh also when CI flag is set which lead to total mess in status menu plugin.

How to solve first problem: (Stop bme) load drivers and discharge battery until capacity be about 7%. You can also you bq27200.sh script for monitoring EDV1/F LOW flag. After battery will be empty, charge it to full and discharge again.

Now going to fix second problem. Thanks for finding & reporting bug in kernel.

Hello.

Now I think I have done what I need to do.
I discharged the battery to ca 120mh.
Charged it again to full.
And finaly discharged it to ca 120mh and did a full recharge again.
Is the output from uevent corret now?
http://toxaris.com/uevent2.txt
(I still got the same output in the bettery-meny)

btw, I tried the bq27200.sh script I found on TMO, but I only get some error messages.

Is it safe to upgrade to KP52 if Im running CSSU-T and Thumb2(based upon KP51r1)?

pali 2012-11-19 07:36

Re: [Announce] CSSU Testing thread
 
for bq27200.sh you need installed i2c tools and run it as root.

toxaris 2012-11-19 09:17

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by pali (Post 1295772)
for bq27200.sh you need installed i2c tools and run it as root.

Ahh, I need to install i2c tools, then I misunderstood the instruction in the battery-thread.

Will try that.

toxaris 2012-11-19 09:37

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by toxaris (Post 1295805)
Ahh, I need to install i2c tools, then I misunderstood the instruction in the battery-thread.

Will try that.

Ok, I already had i2c-tools installed.
I have put the file from this link: http://enivax.net/jk/n900/i2cget
in /usr/bin where bq27200.sh also resides.
If I then run bq27200.sh as root I get this output, is it correct?
http://toxaris.com/bq27200.sh.log

reinob 2012-11-19 09:53

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by toxaris (Post 1295815)
Ok, I already had i2c-tools installed.
I have put the file from this link: http://enivax.net/jk/n900/i2cget
in /usr/bin where bq27200.sh also resides.
If I then run bq27200.sh as root I get this output, is it correct?
http://toxaris.com/bq27200.sh.log

Did you stop bme before running the script?

toxaris 2012-11-19 09:59

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by reinob (Post 1295820)
Did you stop bme before running the script?

Yes.
With these commands.
Code:

stop bme
modprobe bq27x00_battery
modprobe bq2415x_charger


hxka 2012-11-19 10:07

Re: [Announce] CSSU Testing thread
 
You don't need to modprobe anything.
You don't need to stop bme either.

toxaris 2012-11-19 11:37

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by hxka (Post 1295827)
You don't need to modprobe anything.
You don't need to stop bme either.

I know, now I do the calibration with bme instead.
Works sofar.

But maybe pali was interested in the problems with the script running on bq-modules.

panjgoori 2012-11-21 15:37

Re: [Announce] CSSU Testing thread
 
1 Attachment(s)
@pali thanks for the updated battery applet. i have to ask you something, your status area battery applet and battery eye shows different battery percent.

Battery eye showing less than 30 percent battery but battery applet showing 52 percent battery. And also battery icon shows less than 50 percent battery left. Is this a bug or it works like this. thanks. screenshot attached.

pali 2012-11-21 15:48

Re: [Announce] CSSU Testing thread
 
battery icon is reported by hald-addon-bme. battery percentage is calculated by formula: 100*(capacity-6)/94 and capacity is 100*current/design. It is because 0% must be reported when battery is too low (and that happends when capacity is about 6%) current mAh is reported by hald-addon-bme and design mAh is reported by kernel driver rx51_battery (or fallback to hald-addon-bme)

merlin1991 2012-11-23 08:50

Re: [Announce] CSSU Testing thread
 
New update did hit the repos, and since the wiki is read only here's the changelog:

Code:

  * camera-ui: use maemo-invoker, use NOKIA_CAMERA_DIR and NOKIA_MMC_CAMERA_DIR
  * hildon-desktop: fixed #12052, #12584 and #12629
  * ke-recv: added configuration to autolaunch usb0 in pc-suite mode
  * obexd: Initial MAP support (no notifiactions no message push), fixed bug in Irmc
  * openssl: fixed -dbg package (removed debug symbols from main package)
  * pulseaudio: added support for bluetooth AudioSource, added loopback module
  * rtcom-eventlogger-async: fixed dependency
  * status-area-orientationlock-applet: Added dutch translation (by adekker)


MarkyboyUK 2012-11-23 13:22

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by merlin1991 (Post 1297455)
New update did hit the repos, and since the wiki is read only here's the changelog:

Code:

  * camera-ui: use maemo-invoker, use NOKIA_CAMERA_DIR and NOKIA_MMC_CAMERA_DIR
  * hildon-desktop: fixed #12052, #12584 and #12629
  * ke-recv: added configuration to autolaunch usb0 in pc-suite mode
  * obexd: Initial MAP support (no notifiactions no message push), fixed bug in Irmc
  * openssl: fixed -dbg package (removed debug symbols from main package)
  * pulseaudio: added support for bluetooth AudioSource, added loopback module
  * rtcom-eventlogger-async: fixed dependency
  * status-area-orientationlock-applet: Added dutch translation (by adekker)


Quick question, should this update be avoided if currently running CSSU Thumb version?

hxka 2012-11-23 15:23

Re: [Announce] CSSU Testing thread
 
You can upgrade safely. It will negate some benefits of CSSU-Thumb though.

Kerio 2012-11-24 16:59

Re: [Announce] CSSU Testing thread
 
You should wait for the matching CSSU-thumb update, it should arrive shortly.

joerg_rw 2012-11-24 17:05

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by MarkyboyUK (Post 1297539)
Quick question, should this update be avoided if currently running CSSU Thumb version?

Though merlin1991 gave some more detailed differing explanation in IRC, I'd still like to state that - generally speaking - there's no compatibility between any two flavours of CSSU warranted or tested for. So updating from CSSU-T when you're on CSSU-thumb is not really supported (though it probably won't break anything), same as updating from CSSU-T isn't recommended when you're on CSSU-S.
As mentioned above those 'hybrid configs' are neither tested, nor is it a general maintenance goal in CSSU to keep the different flavours so much in sync that you could usually expect no problems when doing so.
For the particular question regarding CSSU-thumb: AFAIK it so far follows CSSU-T closely, with some weeks delay, so the recommended procedure is to wait for CSSU-thumb shipping the new update where CSSU-T6 updates are included. As mentioned in last post an update from CSSU-T on a CSSU-thumb system might 'roll back' some packages to non-thumbified versions, which for now is probably considered 'safe' but that's not warranted for the future.

Also refer to http://talk.maemo.org/showthread.php...36#post1297636

Anybody with better knowledge on details welcome to correct me.

cheers
jOERG

vetsin 2012-11-24 18:44

Re: [Announce] CSSU Testing thread
 
Just want to report that I updated yesterday and haven't encountered any problem with regular use.
Thanks for the update!

adelalgomai 2012-11-24 19:17

Re: [Announce] CSSU Testing thread
 
I had cssu-thumb installed in my N900 , and when I updated the catalogs in app-manager I saw the new update to T-Maemo 6 .. I just updated to it and everything went ok and after rebooting I could see the version 1Tmaemo6 installed in my device , but with no thumb ... did that returned me to cssu-testing and just remove the thumb , or thumb was crashed ??
is there any effect on my device ??
can i roll back to thumb if the new update will be dangerous ??

joerg_rw 2012-11-24 21:00

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by adelalgomai (Post 1297947)
I had cssu-thumb installed in my N900 , and when I updated the catalogs in app-manager I saw the new update to T-Maemo 6 .. I just updated to it and everything went ok and after rebooting I could see the version 1Tmaemo6 installed in my device , but with no thumb ... did that returned me to cssu-testing and just remove the thumb , or thumb was crashed ??
is there any effect on my device ??
can i roll back to thumb if the new update will be dangerous ??

Please ask this question on this thread, since it's not really related to CSSU-T update.

/j

rotoflex 2012-11-25 10:12

Re: [Announce] CSSU Testing thread
 
I also seem to be running OK with latest CSSU-testing.

Only change seems to be that the orientation of of my QTLockscreen & the numberpad lockscreen is frantically changing, whereas previously it had always been in landscape mode, to which I have the phone's orienttion locked.

Also, when the QTLockscreen draws in portrait during its frenzy, I does so inaccurately, & precluding the functionality of the lockscreen swipe to dismiss.

Edit:
knarf is also reporting a post-update rotation issue.
http://talk.maemo.org/showpost.php?p...postcount=1310

arcean 2012-11-25 15:45

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by rotoflex (Post 1298147)
I also seem to be running OK with latest CSSU-testing.

Only change seems to be that the orientation of of my QTLockscreen & the numberpad lockscreen is frantically changing, whereas previously it had always been in landscape mode, to which I have the phone's orienttion locked.

Also, when the QTLockscreen draws in portrait during its frenzy, I does so inaccurately, & precluding the functionality of the lockscreen swipe to dismiss.

Thanks for the report :). The problem is with the Qt rotation manager and a workaround is already available at the hildon-desktop's master branch.

Quote:

Originally Posted by rotoflex (Post 1298147)
Edit:
knarf is also reporting a post-update rotation issue.
http://talk.maemo.org/showpost.php?p...postcount=1310

That's the same Qt bug. But this time it should be fixed in Qt itself :).

Garrett_PL 2012-11-26 02:41

Re: [Announce] CSSU Testing thread
 
Running CSSU-T 6, upgraded from 5.1 today - just to let You lads know that everything is running smooth and stable. Thank You all involved for update, keep up the good work.

riv64 2012-11-26 16:29

Re: [Announce] CSSU Testing thread
 
I have a problem with camera. Photos are saved to /media/mmc1 instead of /media/mmc1/DCIM. How to fix it?

seanmcken 2012-11-26 16:54

Re: [Announce] CSSU Testing thread
 
same problem here

misiak 2012-11-26 18:06

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by riv64 (Post 1298605)
I have a problem with camera. Photos are saved to /media/mmc1 instead of /media/mmc1/DCIM. How to fix it?

Quote:

Originally Posted by merlin1991 (Post 1297455)
* camera-ui: use maemo-invoker, use NOKIA_CAMERA_DIR and NOKIA_MMC_CAMERA_DIR

I guess you should change NOKIA_CAMERA_DIR or NOKIA_MMC_CAMERA_DIR values somehow (however I have no idea how and where they're defined)

hxka 2012-11-26 18:11

Re: [Announce] CSSU Testing thread
 
They're defined in ~/.config/user-dirs.dirs

wumpwoast 2012-11-26 19:58

Re: [Announce] CSSU Testing thread
 
Looking forward to testing Bluetooth audio source functionality. N900 can now be a Bluetooth speaker or receiver for audio from another device. :)

don_falcone 2012-11-29 14:45

Re: [Announce] CSSU Testing thread
 
Does this need a different (additional) BT profile?

seanmcken 2012-11-29 15:03

Re: [Announce] CSSU Testing thread
 
@hxka

im sorry im not getting u jst said ''They're defined in ~/.config/user-dirs.dirs'' and where is is this directory plz explain

Sourav.dubey 2012-11-29 15:23

Re: [Announce] CSSU Testing thread
 
Its home/user/.config/userdirs.dirs

seanmcken 2012-11-29 15:34

Re: [Announce] CSSU Testing thread
 
/home/user/.config # ls
Marxian jspeed.conf
Mediadownloader leafpad
MohammadAG mediainfo-gui
NVideo menus
ThemeCustomizer openmediaplayer
Trolltech.conf phoneme
cepiperez qcpufreq.conf
chromium sakya
cuteTube-QML scorpius
evolution-data-server smplayer
hildon-desktop tracker
hildon-thumbnailer
/home/user/.config #

this is what i got in that directory

hxka 2012-11-29 16:23

Re: [Announce] CSSU Testing thread
 
I'm sure there is no such file from scratch, but I have no idea what creates it.

gilesn 2012-11-29 16:49

Re: [Announce] CSSU Testing thread
 
no such file here either, i created it, user permissions, added the values but it appears to have no effect, photos/videos are always saving to MyDocs

thedead1440 2012-11-29 17:05

Re: [Announce] CSSU Testing thread
 
i have it from scratch though with contents:

Code:

XDG_DOCUMENTS_DIR="$HOME/MyDocs/.documents"
XDG_MUSIC_DIR="$HOME/MyDocs/.sounds"
XDG_PICTURES_DIR="$HOME/MyDocs/.images"
XDG_VIDEOS_DIR="$HOME/MyDocs/.videos"
NOKIA_CAMERA_DIR="$HOME/MyDocs/DCIM"
NOKIA_MMC_CAMERA_DIR="/media/mmc1/DCIM"

file details:

Code:

~ $ ls -al /home/user/.config/user-dirs.dirs
-rw-r--r--    1 user    users          236 Oct  8  2009 /home/user/.config/user-dirs.dirs


Running CSSU-Thumb here though; not sure if that makes a difference...

sixwheeledbeast 2012-11-29 17:14

Re: [Announce] CSSU Testing thread
 
Quote:

Originally Posted by thedead1440 (Post 1299767)
i have it from scratch though with contents:

Code:

XDG_DOCUMENTS_DIR="$HOME/MyDocs/.documents"
XDG_MUSIC_DIR="$HOME/MyDocs/.sounds"
XDG_PICTURES_DIR="$HOME/MyDocs/.images"
XDG_VIDEOS_DIR="$HOME/MyDocs/.videos"
NOKIA_CAMERA_DIR="$HOME/MyDocs/DCIM"
NOKIA_MMC_CAMERA_DIR="/media/mmc1/DCIM"

file details:

Code:

~ $ ls -al /home/user/.config/user-dirs.dirs
-rw-r--r--    1 user    users          236 Oct  8  2009 /home/user/.config/user-dirs.dirs


Running CSSU-Thumb here though; not sure if that makes a difference...

I have exactly the same on CSSU Stable

gilesn 2012-11-29 17:33

Re: [Announce] CSSU Testing thread
 
I'm on cssu testing but didn't have the file, created file from your post, now works. thanks!

seanmcken 2012-11-29 18:17

Re: [Announce] CSSU Testing thread
 
i dont hav that file on my phone so i created my own containing this

XDG_DOCUMENTS_DIR="$HOME/MyDocs/.documents"
XDG_MUSIC_DIR="$HOME/MyDocs/.sounds"
XDG_PICTURES_DIR="$HOME/MyDocs/.images"
XDG_VIDEOS_DIR="$HOME/MyDocs/.videos"
NOKIA_CAMERA_DIR="$HOME/MyDocs/DCIM"
NOKIA_MMC_CAMERA_DIR="/media/mmc1/DCIM"

by thedead1440
and it worked
thank u very much thedead1440

Wikiwide 2012-11-30 05:59

Re: [Announce] CSSU Testing thread
 
1 Attachment(s)
Quick reply...
Is it correct place to ask for help with operator name 'widget', which was installed as part of CSSU Testing?
Long time ago, it worked - at the very least, I could see vague location appended to the operator's name, though I don't remember ever receiving any broadcasts.
However, right now it 'blinks'. Here is a part of opername.log attached...
Code:

30.10.0112 18:17 service provider name network match fail  type 0
30.10.0112 18:17 service provider name match
30.10.0112 18:17 set operator widget string ''
30.10.0112 18:17 set operator widget string ''
30.10.0112 18:17 operator_name_change: set display name to NAME
30.10.0112 18:17 set operator widget string 'NAME'
30.10.0112 18:18 operator_name_change: set display name to NAME
30.10.0112 18:18 set operator widget string 'NAME'
30.10.0112 18:20 set operator widget string 'NAME  Location'
30.10.0112 18:20 operator_name_change: set display name to NAME
30.10.0112 18:20 set operator widget string 'NAME  Location'
30.10.0112 18:22 set operator widget string 'NAME'

Oh, and 'incoming cell tower' alternates between Location (two cell towers), Location_2 (one cell tower, far away, I was surprised to see it in the log), and another 'cell id' (no location or name given).
Thanks in advance.

pali 2012-11-30 06:49

Re: [Announce] CSSU Testing thread
 
@Wikiwide, please attach both log files.


All times are GMT. The time now is 06:49.

vBulletin® Version 3.8.8