Notices


Reply
Thread Tools
Posts: 274 | Thanked: 339 times | Joined on Jan 2012 @ Madrid, Spain
#2031
Originally Posted by acrux View Post
Hmm - I enabled doubletap to wake - could it be the reason?

Is it possible to disable it temporarily for testing?
Hi.

I activated doubletap since the very beginning and still draws about 5% overnight...
Still, doubletap is quite buggy.

Regards.
 

The Following 3 Users Say Thank You to pasko For This Useful Post:
Posts: 274 | Thanked: 339 times | Joined on Jan 2012 @ Madrid, Spain
#2032
Originally Posted by oenone View Post
Wifi is usually always active as is mobile data. Device is expected to do the switcharoo as necessary/possible. Not using SecureFishNet but using the built-in client which works great after having added the following line to the configuration file to ensure all traffic goes through the VPN:

Code:
redirect-gateway def1
"Wifikiller" application from OpenRepos but it didn't seem to work properly (or was not configured to work properly) so wifi stays on all the time, sadly.
Hi.

Man, this option made my day. I had it activated in the server side, but not in the client and a part of the traffic was routed via cellular data.... now everything goes through the VPN.

On your issue I have no clue (my xMPP client won't reconnect automatically when I switch from WiFi to cellular, and I don't know why.)

Regards.
 

The Following User Says Thank You to pasko For This Useful Post:
Posts: 35 | Thanked: 80 times | Joined on May 2015
#2033
Enable:

mcetool -M show-unlock-screen
mcetool -z proximity
mcetool -i enabled
mcetool -E enabled

Disable:

mcetool --set-doubletap-mode=disabled
mcetool --set-fake-doubletap=enabled
mcetool --set-doubletap-wakeup=never
 

The Following 5 Users Say Thank You to objectifnul For This Useful Post:
Posts: 83 | Thanked: 381 times | Joined on Mar 2010 @ southern Italy
#2034
Originally Posted by pichlo View Post
Going dead from 39% over 17 hours? On Jolla 1, that is absolutely 100% expected.
I do not know about SailX but it would not surprise me at all.
On SailfishX I've never seen more than 3-4% battery usage overnight (most times is 1-2% only), even with 7-8 open apps and an automated nightly rsync backup at 3:40am. On Jolla1 it was basically the same.
BTW I don't have yet installed any Android app on SailfishX.

Apple and Android phones were born as "monotasking" instead of multitasking because many stupid developers wasted CPU resources like there was no tomorrow and it was hard to explain to customers that their preferred apps kept wasting battery milliamperes like hungry piranhas surrounding a steak. A very few Android/iOS apps are allowed to do something when backgrounded (and only a few things like GPS updating, audio playing, network messaging, etc).

Monotasking automatically led developers to write even worse software - wasting CPU resources everytime they can - because they know that every time the app is not in foreground it's basically frozen.

Sailfish is a true multitasking system (I clearly hear Apple fanbois woohooing). Sailfish doesn't enforce memory/network/CPU/background limits, thus an app could actually waste 100% CPU cycles even in background.

Native Sailfish apps have to be well-behaved. Currently it's easy to spot a new app wasting resources for no reason... because most of native apps are actually well-behaved (thanks also to Qt/QML).

With the exception of old batteries (many hundreds of recharge cycles), if Sailfish wastes too many milliamperes then most probably you have to blame some Android app.
__________________
 

The Following 5 Users Say Thank You to alfmar For This Useful Post:
Posts: 212 | Thanked: 388 times | Joined on Jan 2011 @ Estonia
#2035
Originally Posted by alfmar View Post
Native Sailfish apps have to be well-behaved. Currently it's easy to spot a new app wasting resources for no reason... because most of native apps are actually well-behaved (thanks also to Qt/QML).

With the exception of old batteries (many hundreds of recharge cycles), if Sailfish wastes too many milliamperes then most probably you have to blame some Android app.
Sorry, no Android support installed here...
 

The Following 2 Users Say Thank You to acrux For This Useful Post:
pichlo's Avatar
Posts: 5,036 | Thanked: 15,194 times | Joined on Sep 2012 @ UK
#2036
Originally Posted by acrux View Post
Sorry, no Android support installed here...
Same here. Never allowed Android touch my Jolla. Still, 2% battery drop per hour is normal with no applications running, WiFi on and connected. With WiFi on and not connected this can increase four times.

The smallest overnight drop I have ever seen was 8%, and that was when I went to bed particularly late (long after midnight) and woke up as usual (about 05.30).

This is all on Jolla. But if others are reporting similar on their Xperias, then it is likely not a hardware issue.
__________________
In particle accelerators atoms are indeed not only touching each others. But banging together in a massive explosive orgasm.
-- nieldk in a TMO post
 

The Following 4 Users Say Thank You to pichlo For This Useful Post:
Posts: 12 | Thanked: 37 times | Joined on Jun 2016
#2037
To give some more insight. I have unfortunately Android support installed and an Android is always running. Furthermore I have it in Flight mode over night.
 

The Following User Says Thank You to peperjohnny For This Useful Post:
pycage's Avatar
Posts: 3,402 | Thanked: 4,469 times | Joined on Oct 2005 @ Germany
#2038
Maybe this will show a comparison on battery life of the Jolla C and the XPeria X.

While my phone number hasn't been transferred from my old to my new operator, I carry the Jolla C around in my backpack only for SMS. The XPeria X is my main phone and phone calls to the Jolla C are redirected to the XPeria X.
On a day without touching the Jolla C at all, and moderate use of the XPeria X, I left the house in the morning with both fully charged, and returned home jn the evening with both at 70% of charge remaining.
__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
 

The Following 4 Users Say Thank You to pycage For This Useful Post:
mosen's Avatar
Community Council | Posts: 900 | Thanked: 5,464 times | Joined on Nov 2014 @ Kitchen
#2039
Originally Posted by pichlo View Post
Going dead from 39% over 17 hours? On Jolla 1, that is absolutely 100% expected.
I do not know about SailX but it would not surprise me at all.
F5121 standby on Android 7.1.1 was extremely good and shows the HWs capability if SW is optimized.
I had the device laying in the drawer from recieving, making updates and disposing it with ~80% into the drawer, 6 days later when flashing it still had more than 60%.
Now with sailfish, bit more than normal usage, full blown dalvik but without double tap hack i got ~2days out of it. Going to recharge it the first time this evening after putting it to use yesterday morning with 100% when my nano sim arrived.

EDIT, sfos may be not perfectly optimized for f5121, but it still amazed me that it stayed at 100% for around 5 minutes of usage until it went down to 99%.
On Jolla C, i unplugged at 100% and it went to 99% immediatly ever since i recieved it.
 

The Following 2 Users Say Thank You to mosen For This Useful Post:
anidel's Avatar
Posts: 1,737 | Thanked: 1,220 times | Joined on Jul 2006 @ Twickenham, UK
#2040
Originally Posted by objectifnul View Post
Enable:

mcetool -M show-unlock-screen
mcetool -z proximity
mcetool -i enabled
mcetool -E enabled

Disable:

mcetool --set-doubletap-mode=disabled
mcetool --set-fake-doubletap=enabled
mcetool --set-doubletap-wakeup=never
Could.someone explain what these do, or point to a wiki of sort?
 

The Following 3 Users Say Thank You to anidel For This Useful Post:
Reply

Tags
sailfish os, sony xperia x

Thread Tools

 
Forum Jump


All times are GMT. The time now is 19:54.