![]() |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Sailfish 2.0.5.6. OTA will be hopefully available after release, but for OTA i need the camera working.
I already talked t nh1402, he'll help getting sfdroid running on cm13 base, but same as above, camera first. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Most of the times it is in c3 state.
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
C3 is good, but its still awake as far as I understand the states.
What about "CPU sleep %"? When all is good, that should be 90%+ while your phone is in your pocket. For me, its 95% with idle states taking in total less than 1% (i.e. phone is either asleep or doing something while awake to get into the sleep ASAP). Its different hardware + kernel, though. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Is there any other way to check the suspend time, in Systemdatascope this never showed anything, it does not work on 12.1port either, or it really never gets to sleep.
/sys/kernel/debugsuspend_stats shows 0, but its the same on 12.1. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
mcetool --get-suspend-stats uptime: 522012.239 suspend_time: 406547.645 The collectd plugin reporting CPU sleep is very simple (merged into upstream at https://github.com/collectd/collectd...src/cpusleep.c ) and is based on following two kernel clocks, as mcetool. I presume that you would get suspend_time = 0 in mcetool output. If not, then run mcetool several times and see how the times are increasing. By following the increase in times, you could easily calculate CPU sleep percentage. Just let the phone "rest" for a bit (10 minutes) between measurements. Please, if it turns out that SystemDataScope/collectd reports sleep wrongly, let me know - github issue at SystemDataScope repo would probably be simplest (or via this thread, I'll follow it). Usually, absence of CPU sleep means that some wakelock is not released. Maybe dmesg has something to say? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Not looking good:
mcetool --get-suspend-stats uptime: 3253.005 suspend_time: 0.000 The wakelocks who keep the device from getting into sleep mode are from msm_serial_hs_dma. Seems to be bluetooth related. Strange thing is that i don't use bluetooth. EDIT: After disabling all bluetooth services, the device does enter suspend mode. Maybe someone can try this also on cm12.1? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
If you say me how to disable bluetooth services i'll try!
btw, i'm satisfied with the battery usage with cm12 and your kernel. But if with cm13 is better i will give a try! |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Quote:
Also confirmed for cm12.1 with Sailfish 2.0.5.6! Code:
devel-su Code:
[nemo@pris ~]$ mcetool --get-suspend-stats |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Thanks minimec.
@rinigus With bluetooth disabled, suspend works as it should, but the power consumption in idle does not improve. Btw, it is also shown in systemdatascope now. |
All times are GMT. The time now is 21:49. |
vBulletin® Version 3.8.8