| ac_laptop | my n900 went off at about 17:50 and I don't know why | 00:39 |
|---|---|---|
| ac_laptop | battery is still at 75% | 00:40 |
| ac_laptop | I'm going to upload syslog | 00:41 |
| ac_laptop | if anyone's reading | 00:42 |
| ac_laptop | here it is | 00:42 |
| ac_laptop | https://paste.debian.net/1298443/ | 00:42 |
| ac_laptop | from boot to shutdown | 00:43 |
| ac_laptop | is there any settings on the default setup that makes it shut down after a while ? | 00:46 |
| Wizzup | it would be interesting to know the voltage of the battery at that point | 00:50 |
| ac_laptop | Wizzup: is there a log file for the battery ? | 00:52 |
| Wizzup | upower might have some data in it's history file | 00:53 |
| Wizzup | not sure how easy it is to pull out | 00:56 |
| Wizzup | I had a script for it... | 00:56 |
| ac_laptop | Wizzup: https://paste.debian.net/1298444/ | 00:57 |
| ac_laptop | ↑↑↑ here I'm only giving you the *-8.dat files, whose last access date is 2023-11-17 17:47 | 01:02 |
| ac_laptop | but I don't know how to interpret the values, maybe you need the most recent files | 01:03 |
| ac_laptop | because if I open the recent /var/lib/upower/history-charge-7.dat | 01:03 |
| ac_laptop | the last lines look like | 01:04 |
| ac_laptop | 1700089729 45.000 discharging | 01:04 |
| ac_laptop | 1700090455 6.000 discharging | 01:04 |
| ac_laptop | 1700264174 0.000 unknown | 01:04 |
| ac_laptop | 1700264175 75.000 discharging | 01:04 |
| ac_laptop | 1700264295 74.000 discharging | 01:04 |
| ac_laptop | 1700264535 73.000 discharging | 01:04 |
| ac_laptop | 1700264776 72.000 discharging | 01:04 |
| ac_laptop | 1700265139 71.000 discharging | 01:04 |
| ac_laptop | 75% is the battery level I had when booting again few minutes ago | 01:04 |
| Wizzup | so it looks like it dropped very radidly | 01:05 |
| Wizzup | right? | 01:06 |
| ac_laptop | Wizzup: maybe the system believed that the battery dropped very rapidly, but it didn't. I booted and it was at 75% | 01:10 |
| Wizzup | odd | 01:13 |
| ac_laptop | looks like there is something though, given what I had yesterday morning, with the device off, booting on leste -> battery at 0%, booting on fremantle -> battery at 99% | 01:15 |
| ac_laptop | I will try to let the device idle under fremantle for a few hours, to see if this is hardware-related or specific to leste | 01:17 |
| ac_laptop | if we look at what happened in the morning it's like a sudden drop | 01:20 |
| ac_laptop | Nov 17 07:38:03 1700203083 22.000 discharging | 01:20 |
| ac_laptop | Nov 17 07:50:09 1700203809 21.000 discharging | 01:20 |
| ac_laptop | Nov 17 08:04:16 1700204656 7.000 discharging | 01:20 |
| arno11 | ac_laptop: i compared your battery log and mine and definitely something seems wrong with your battery(ies). it is supposed to discharge pourcent by pourcent. Unknown state seems related to battery removal or shutdown. | 10:18 |
| arno11 | your syslog seems normal but it seems you have zram activated | 10:20 |
| sicelo | yes. either the battery is a goner, or it isn't making very good contact with the connector. this is quite common actually, although in many cases, it causes device to die, i.e. not graceful shutdown. | 10:20 |
| sicelo | this can be somewhat remedied by carefully adjusting the contacts in the battery, taking care not to break them | 10:21 |
| slep | hi, i'm using sdhc class 10 but the OS is still incredibly slow and unresponsive. i booted using the instructions on the wiki, with the pali u-boot. is this normal? i also ensured swap was activated | 17:57 |
| sicelo | i have never used Fremantle while roaming. does it really not give some indication that you are? i know about the setting to allow or disallow gprs when roaming | 18:49 |
| arno11 | slep: not a surprise: few things make first boots really difficult. | 19:07 |
| arno11 | few tips: | 19:07 |
| arno11 | wait at least 3-4 min once you see hildon-desktop screen before clicking somewhere | 19:08 |
| arno11 | don't connect to wifi because apt- worker will start automatically in background letting n900 unresponsive for several minutes | 19:09 |
| arno11 | be sure to expand root partition (a bit or totally) | 19:09 |
| arno11 | normally, after 2 reboots, things are fine and you can distupgrade to devel | 19:10 |
| arno11 | then you can tune N900 a bit to speed-up things (transitions.ini, overclock) | 19:13 |
| slep | thanks :) i will give this a go | 19:15 |
| arno11 | you're welcome :) | 19:16 |
| slep | btw, is leste currently somewhat usable as an alternative to the fremantle with cssu etc? i'm currently setting that up | 19:16 |
| arno11 | with few tips, definitely (excepting for camera and bluetooth) | 19:17 |
| slep | i'm guessing camera is probably a difficult cause unfortunately :< | 19:18 |
| arno11 | yep | 19:19 |
| arno11 | sicelo: if calls are integrated before the end of the year, the big challenge for 2024 is camera :p | 19:38 |
| arno11 | even only the front one could be enough (to get working video sip/xmpp calls) | 19:40 |
| arno11 | sicelo: (for roaming) can't remember if there is any particular indication about it in Fremantle but iirc it shows the name of the roaming operator (when roaming ofc) | 19:50 |
| arno11 | and with Leste it shows your current operator and the roaming one at the same time. | 19:51 |
| arno11 | and sometimes only the roaming one | 19:52 |
| sicelo | regarding camera ... both cameras shouldn't be too difficult to get going, but what i suspect could be difficult is the required processing ... i *think* in Fremantle, the dsp also took part, but we don't have it with mainline | 20:17 |
| sicelo | for roaming, i guess someday i can make icons that indicate roaming, then we can see what code is needed. ofono reports the state correctly | 20:18 |
| arno11 | ok | 20:25 |
| arno11 | and yes for dsp | 20:26 |
| uvos | really no, roaming indication on fremantle!? i was sure this was a leste bug | 20:46 |
| uvos | wierdly signifcant oversight for nokia to make | 20:46 |
| uvos | you def need the dsp to use the camera, debayering and color callibration is going to be very not fun if you do it on that poor cpu | 20:47 |
| Wizzup | uvos: I think you can enable/disable roaming in settings | 20:52 |
| sicelo | no, you can only set gprs to work, or not work when roaming | 20:53 |
| sicelo | actually even on N9, it's the same. | 20:53 |
| Wizzup | hm... but it has a data counter for both, and also a warning? | 20:54 |
| sicelo | Yes | 20:54 |
| sicelo | gprs ... that's the keyword :-) | 20:54 |
| Wizzup | I mean a warning for roaming | 20:54 |
| Wizzup | oh, hm | 20:54 |
| Wizzup | wait, what other than gprs? | 20:54 |
| sicelo | but for calls, there's no notification and/or warning | 20:54 |
| Wizzup | right | 20:55 |
| sicelo | i think someday we should create roaming icons, and hook up ofono's Network status accordingly | 20:55 |
| uvos | thats honstly wild, what if you live in a border region | 20:55 |
| uvos | sicelo: yeah def | 20:55 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!