Active Topics
-
Maemo repository (8)
to Community by Maemish - 1 day, 9 hrs ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 14 hrs ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 11 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days, 9 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days, 9 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 14 hrs ago - more...
| The Following User Says Thank You to pichlo For This Useful Post: | ||
|
2014-07-22
, 10:59
|
|
Posts: 25 |
Thanked: 19 times |
Joined on Apr 2014
|
#32
|
Originally Posted by pichlo
That's right. Afraid I just assumed it was overclocking. There was just a suspicion that overclocking may have caused it. There was no solution, either. Also, the error messages differ from mine.
Hmm, that other thread is rather inconclusive as to whether it was really the overclocking that had caused it. I would consider it unlikely albeit not entirely impossible.
BTW, you have not answered my question about the 10 hours you squeezed out of your battery. For a comparison, I took my phone off the charger at 06:38 this morning. It is now 10:04 and the battery level is at 74%. I received one SMS, sent and received a couple of emails, did some online banking for about 10 minutes and read this forum for about 30. That's it.
Did find someone with exactly the same error as mine. The issue is also posted in the bug report thread linked from that post. There's a straightforward solution that was provided too - power off, remove battery, turn on. Sadly, doesn't work for me.
About my battery usage. The 10 hour usage was with 3G turned on, roughly 2 hours of SSHing into the phone over WLAN, 1 or 2 SMS received, no phone calls, installing/purging several packages on x-terminal, running powertop/zzztop several times.
Tested again today, and the battery drained to 0% from 91% in 6 hours. It was with 3G on, at least 2 hours of web browsing, about 15~20 mins on modrana with GPS on, couple more hours on the x-terminal setting up packages, an hour with mobilehotspot on.
The phone feels warm to the touch at times, but I don't think it gets alarmingly hot. It's 35C here, so "warm" may well be warmer than I think it is.
Thank you.
 |
|
2014-07-22
, 13:18
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#33
|
By 3G on you mean 3G data connection active all the time? If yes, your battery life is pretty normal, 3G data is power sucker, even if you don't transmit much. If you need to be online, but doesn't transfer much at the moment (like, you want to be logged in for SIP or mail or anything), switch to 2G. The latter is much, much more power saving when connected but "standby". Of course, if you're actively using device and need high transfers at the moment, switch to 3G by any means (and switch back to 2G after you're done).
Anyway, your powertop output is still bad, and I suspect that something may still be stubborn and call dead module, waking CPU. I would trust powertop output more than zzztop's one (although, no particular reason - is just that powertop output never lied to me in the past). I don't get how results concerning C4 state can be so completeley different - either one of the tools contain serious bugs that manifest in your case (or in all cases, as I don't recall any extensive testing done on zzztop, determining if it's connected to reality) , or I don't know what.
Sorry that can't help more
/Estel
/Edit
Just for the record, to avoid creating another OC myth - the BT damage in other thread is really unlikely to have anything to do with overclocking. By the content there, it's just a "flip-coin" assumption.
Anyway, your powertop output is still bad, and I suspect that something may still be stubborn and call dead module, waking CPU. I would trust powertop output more than zzztop's one (although, no particular reason - is just that powertop output never lied to me in the past). I don't get how results concerning C4 state can be so completeley different - either one of the tools contain serious bugs that manifest in your case (or in all cases, as I don't recall any extensive testing done on zzztop, determining if it's connected to reality) , or I don't know what.
Sorry that can't help more
/Estel
/Edit
Just for the record, to avoid creating another OC myth - the BT damage in other thread is really unlikely to have anything to do with overclocking. By the content there, it's just a "flip-coin" assumption.
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
|
|
2014-07-22
, 15:44
|
|
Posts: 25 |
Thanked: 19 times |
Joined on Apr 2014
|
#34
|
Originally Posted by Estel
What I meant was that the network mode was set to "Dual", which defaulted to 3G. I had the actual data connection active for around 2 hours at most (less than 1/3rd of the total period). For good measure, I have since downloaded the 3G/2G mode applet and have set the network mode to 2G.
By 3G on you mean 3G data connection active all the time?
About the powertop vs zzztop results, the inconsistencies in the C4 state are quite consistent. They remain so, even after flashing.
This appears on my dmesg, despite attempts to disable the bluetooth modules. Could it point to something?
Code:
[ 2285.121185] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
| The Following User Says Thank You to codelad For This Useful Post: | ||
|
|
2014-07-22
, 16:19
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#35
|
Sadly, I lack expertise on that bluetooth integration thing
And now for something completely different (and not Spanish Inquisition, too) i I would like to finally determine if your's device current draw is normal or not (which, in extension, will tell us if it's worthwhile to dig that nightmare'ish bluetooth integration topic deeper).
Could you, please, download the attachment (of this post) file to MyDocs, then, execute as root:
...and perform two following tests:
1. Disable cellular, wifi, and all other connections, close all programs etc (just like for powertop test), and execute (as root):
Ignore error after modprobe -r, if bq27x00_battery is not found, and after executing bq27200.sh 20, lock the screen and leave device idle for ~5 minutes. Then, unlock it, stop the process (ctrl+x), and post output here.
2. Do the same test as with #1, but this time, with cellular (although no data connection) and your other usual "standby" things enabled (screen still locked). Also post output here.
Cheers,
/Estel
And now for something completely different (and not Spanish Inquisition, too) i I would like to finally determine if your's device current draw is normal or not (which, in extension, will tell us if it's worthwhile to dig that nightmare'ish bluetooth integration topic deeper).
Could you, please, download the attachment (of this post) file to MyDocs, then, execute as root:
Code:
cd /usr/sbin tar -xvf /home/user/MyDocs/bq27200.sh.tar
1. Disable cellular, wifi, and all other connections, close all programs etc (just like for powertop test), and execute (as root):
Code:
modprobe -r bq27x00_battery bq27200.sh 20
2. Do the same test as with #1, but this time, with cellular (although no data connection) and your other usual "standby" things enabled (screen still locked). Also post output here.
Cheers,
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
|
|
2014-07-22
, 18:42
|
|
Posts: 25 |
Thanked: 19 times |
Joined on Apr 2014
|
#36
|
Originally Posted by Estel
Attaching the test results. File bqidle02.txt -> test #1, bqactive02.txt -> test #2.
...and perform two following tests:
A word about the battery. The one I used to test is a stock Nokia battery that came with the phone. However, I cannot attest to it's genuineness, since there appear to be identical fake ones (and I bought the phone used). I have 2 more spare batteries bought on Ebay. One of them turned out to be a cheapo 900mAh that doesn't even boot the phone up. Another is slightly better at 1250mAh and works. I have no idea how it compares to the original BL-5J, though.
 |
|
2014-07-22
, 19:28
|
|
Posts: 6,453 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#37
|
Originally Posted by codelad
That's odd. Here is an extract of mine. It shows the current about a third to a quarter of yours, and I did not even bother disconnecting the wireless services. That is, GSM (2G) and WiFi were on and connected.
Attaching the test results.
Code:
mv CSOC mA NAC CACD CACT TTF TTE TEMP VDQ EDV1 20:06 3831 81 -165 1568 1568 1568 65535 570 37 0 0 20:06 3857 81 -36 1567 1567 1567 65535 2550 36 0 0 20:07 3871 81 -49 1567 1567 1567 65535 1895 35 0 0 20:07 3865 81 -28 1567 1567 1567 65535 3254 35 0 0 20:07 3876 81 -28 1566 1566 1566 65535 3312 34 0 0 20:08 3868 81 -32 1566 1566 1566 65535 2926 34 0 0 20:08 3868 81 -30 1566 1566 1566 65535 3106 34 0 0 20:08 3876 81 -28 1566 1566 1566 65535 3271 34 0 0 20:09 3879 81 -30 1566 1566 1566 65535 3123 34 0 0 20:09 3871 81 -36 1566 1566 1566 65535 2595 33 0 0 20:09 3879 81 -30 1565 1565 1565 65535 3105 33 0 0 20:10 3879 81 -36 1565 1565 1565 65535 2606 33 0 0
| The Following User Says Thank You to pichlo For This Useful Post: | ||
|
|
2014-07-23
, 13:30
|
|
Posts: 25 |
Thanked: 19 times |
Joined on Apr 2014
|
#38
|
Originally Posted by pichlo
Don't quite know what to make of the rest of the numbers, but the high current (at pretty much the same voltage as yours) certainly sounds bad.
That's odd. Here is an extract of mine. It shows the current about a third to a quarter of yours, and I did not even bother disconnecting the wireless services. That is, GSM (2G) and WiFi were on and connected.
Here's something else that seems odd. I ran powertop for 5 mins, and there was an improvement in the C4 share (was close to 15%). Decided to take it further and ran it for 20 mins, and the numbers are totally messed up, as you can see below.
powertop output (20 mins):
Code:
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 1200 seconds
Sample interval was 50m 00s 28473us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 192.1% | | 1150 MHz | nan% |
C1 | -0.0% | 0.2ms |
C2 | -0.1% | 1.6ms |
C3 | -1.5% | 253.0ms |
C4 | -90.4% | 3173.5ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 7443 | INTC | i2c_omap
37 | 1634 | INTC | gp
57 | 1483 | INTC | i2c_omap
11 | 913 | INTC | prcm
12 | 4 | INTC | DMA
225 | 4 | GPIO | omap2-onenand
86 | 3 | INTC | mmc1
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 1060 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
733 | 341 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
38 | 243D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
692 | 163 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
692 | 100 | dsme | do_nanosleep (hrtimer_wakeup)
1 | 100D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
733 | 81 | bme_RX-51 | schedule_timeout (process_timeout)
733 | 80 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
729 | 76D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
0 | 62 | <kernel core> | hrtimer_start (tick_sched_timer)
704 | 40 | syslogd | hrtimer_start (it_real_fn)
776 | 40 | hald | schedule_hrtimeout_range (hrtimer_wakeup)
1155 | 40 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
1082 | 20 | iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
0 | 10 | <kernel core> | addrconf_verify (addrconf_verify)
0 | 10 | <kernel core> | queue_delayed_work (delayed_work_timer_fn)
1 | 10 | <kernel core> | inet_initpeers (peer_check_expire)
609 | 2 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
14 | 2 | pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
14 | 2 | pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
1635 | 2 | Calendar | schedule_hrtimeout_range (hrtimer_wakeup)
1 | 2 | <kernel core> | inet_frags_init (inet_frag_secret_rebuild)
1 | 2 | <kernel core> | flow_cache_init (flow_cache_new_hashrnd)
729 | 2 |<kernel module> | inet_frags_init (inet_frag_secret_rebuild)
1 | 2D| <kernel core> | rt_secret_timer_init (rt_secret_rebuild)
943 | 1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
820 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
1588 | 1 | browserd | futex_wait (hrtimer_wakeup)
873 | 1 | Xorg | schedule_hrtimeout_range (hrtimer_wakeup)
747 | 1 | dbus-daemon | schedule_hrtimeout_range (hrtimer_wakeup)
30 | 1 | mount | setup_wb_timer (wb_timer_fn)
1359 | 1 | temp-reaper | do_nanosleep (hrtimer_wakeup)
2138 | 1 | powertop | do_nanosleep (hrtimer_wakeup)
Power domain activity breakdown
Domain | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
sgx |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
per |OFF: 99%|RET: 0%|INA: 0%| ON: 0%| now:(ON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 97%|RET: 1%|INA: 0%| ON: 0%| now:(ON)
neon |OFF: 97%|RET: 1%|INA: 0%| ON: 0%| now:(ON)
mpu |OFF: 97%|RET: 1%|INA: 0%| ON: 0%| now:(ON)
iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
Clock activity breakdown at end of period
Domain | Active clocks
--------+---------------+---------------+------------------
core | SDRC | HSOTGUSB_IDLE | OMAPCTRL
| MAILBOXES |
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |
Total wakeups 13984, 11.7/s | IRQ 11484, 9.6/s | Timers 2500, 2.1/s
HW wakeups 145, 0.1/s | Real gp_timers expired 98, 0.1/s
| The Following User Says Thank You to codelad For This Useful Post: | ||
|
|
2014-07-23
, 14:16
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#39
|
The tests clearly shows that your CPU doesn't sleep - it matches results of "healthy" device if CPU is keep awake by some loop command. As a side note, it also confirms that powertop output is right, and zzztop completely lies (might be worth mentioning to zzztop maintainer). I think that you can skip any zzztop tests from now on.
Of course, it explains poor battery life (especially in standby). I guess that your active time (if used actively non-stop from charging to completely discharging) is no different than of healthy device, although in standby you loose battery power *much* more than you should (~12x more in total standby aka test1).
As it persist through reflash, I guess that hardware failure - and our wild guess of bluetooth being responsible - might be correct. Sadly, I'm not sure if you have any possibility of fixing it completely, but if yes, it would definitely upgrade your standby times (in other words = worth a shot).
I thought about who you could ask re those bluetooth messages in dmesg, but I don't have any good ideas(maybe kernel-power maintainers know something about this stuff? Just wild guess...)
/Estel
Of course, it explains poor battery life (especially in standby). I guess that your active time (if used actively non-stop from charging to completely discharging) is no different than of healthy device, although in standby you loose battery power *much* more than you should (~12x more in total standby aka test1).
As it persist through reflash, I guess that hardware failure - and our wild guess of bluetooth being responsible - might be correct. Sadly, I'm not sure if you have any possibility of fixing it completely, but if yes, it would definitely upgrade your standby times (in other words = worth a shot).
I thought about who you could ask re those bluetooth messages in dmesg, but I don't have any good ideas(maybe kernel-power maintainers know something about this stuff? Just wild guess...)
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2014-07-23
, 15:30
|
|
Posts: 25 |
Thanked: 19 times |
Joined on Apr 2014
|
#40
|
Originally Posted by Estel
If it is indeed a hardware failure, the most I'm capable of, is to take the device apart tighten and clean the connectors, put it back again and hope against hope that it works! As I remember from the last time I dissassembled it, a couple of flex connectors did feel like they could come loose.
... I guess that hardware failure - and our wild guess of bluetooth being responsible - might be correct. Sadly, I'm not sure if you have any possibility of fixing it completely, but if yes, it would definitely upgrade your standby times (in other words = worth a shot).
I thought about who you could ask re those bluetooth messages in dmesg, but I don't have any good ideas(maybe kernel-power maintainers know something about this stuff? Just wild guess...)
FYI, there are no bluetooth messages in dmesg now (after successfully unloading the bluetooth and hci_h4p modules), save one. I'll definitely need help with pursuing the bluetooth line further.
If none of these work, I think I'll still be reasonably happy with the status quo. It's rather inconvenient swapping batteries and charging them 24/7, but at least the device is usable and I don't miss bluetooth at all (only ever used it a handful of times, anyways).
Also looking for a new battery that is known to work, if only to eliminate the battery factor as a possible cause. I find several recommended brands here, but none of them appear to be available here. May have to take a chance and go for a Nokia on Ebay.
| The Following User Says Thank You to codelad For This Useful Post: | ||
BTW, you have not answered my question about the 10 hours you squeezed out of your battery. For a comparison, I took my phone off the charger at 06:38 this morning. It is now 10:04 and the battery level is at 74%. I received one SMS, sent and received a couple of emails, did some online banking for about 10 minutes and read this forum for about 30. That's it.