Jolla battery life power consumption problems

Reading on Jolla browser? Change to mobile view

Your Advertise here with BitCoin supported campaigns:

Update (31-Jan-2014)

Great news - Installing Sailfish 1.0.3.8. Naamankajärvi fixes the NFC bug. For those who did the mask-workaround for better battery life: Jolla has confirmed that tohd.service can be left masked while updating system. This means that you can remove the mask either before installing the update or afterwards. Personally I'm leaving it on at this point, as I have no use for TOH connection yet. To enable the connection with your Other Half again (removing the workaround), here's a detailed HowTo

Sailfish 1.0.3.8 also changes the way of The Other Half connection. When attaching TOH, the ambience changes only if it's marked as a favourite, or in the first time when TOH is connected.

Original article 22-Dec-2013

After 90 reports posted with User Report Tool,  and 10 more received directly from friends, I've managed to estimate some power consumptions of most elements in Jolla. A big THANKS for everyone in the community for using the report tool - this would have been a slow (or impossible) project without your help.

In general Jolla's hardware parts have a reasonable power consumption, especially those in the Qualcomm chip (processor, connectivity, graphics, memory handling). The main problem is Jolla's NFC connection with The Other Half - that's quite a power sucker, considering it seems to be on all the time. It actually seems to reduce Jolla's standby hours from max 500h to poor 48h. Removing The Other Half, or the white chip inside it (Update, see comments) fixes the problem. We don't want to do that! Unfortunately there's no setting for turning the NFC off, but maybe after this article Jolla start to work to offer us one. NFC connection sucks the battery about 2% per hour.

As usual in modern smartphones, the screen is the biggest power sucker, also in Jolla. Jolla's IPS LCD screen is worse than some OLED screens used in other models, sucking the battery 5% - 10% per hour. Recommended to use dark tone ambiences and as low screen brightness as reasonable.

Then comes the graphic chip, processor and data transfer - but as already said, Qualcomm has actually done a very good job with these in their Snapdragon 400 chip which Jolla is using. Anyway they matter, so if you really want to see the percentages drown, try playing a powerful online 3D game with full screen brightness.

Below, power consumption in different cases is listed as percentage/hour & the usability time

Jolla's battery life in varying scenarios

• Screen OFF, all connections (including mobile network) OFF, The Other Half removed:
  consumption 0,2% per hour, max 500h standby time
• Screen OFF, all connections (including mobile network) OFF, The Other Half attached:
  consumption 1,7-2,5% per hour, average 48h standby time
• Screen OFF, mobile network ON, other connections and accounts off
  consumption 1,7-2,8% per hour, average 43h standby time
• Screen OFF, mobile network ON, WLAN ON, some accounts synching data
  consumption 2,4-4,6% per hour, average 30h standby time
  (depends a lot of the amounts of data transfered)
• Phone in normal use, including some screen using, phone calls, data transfer
  consumption 3,6-14,3% per hour, variance 7-28h usability time
  (normal use varies a lot, as you can guess)
• Phone in continuous use, screen staying ON at low brigtness
  consumption 5,9-14,3% per hour, variance 7-17h usability time
  (unfortunately, the reports didn't include what kind of screen use (video/3D gaming/static img)
• Phone in continuous use, screen staying ON at high brigtness
  consumption 10,0-30,5% per hour, variance 3-10h usability time
  (lowest usability time reported playing Angry Birds)

The effect of NFC connection with The Other Half 

Above, the 4th dot is maybe the best to describe the normal standby hours of Jolla, so let's calculate some more with that. NFC itself, when in use, eats the battery with a speed of 2% per hour. Using this value we can calculate that the stanby time of 30h mentioned above, or 20-40h variance of it, would rise to 38-250h when removing The Other Half.

To confirm this result

This result is based on only 4 tests where The Other Half was removed, two of them done myself. At the very moment I'm running my third test with even SIM card removed, and after 13h my battery shows 98%. Anyway, for even more reliable confirmation, I've added the selection to the last page of User Report Tool. Now I wish that many of you will reports new test results with The Other Half removed. To people who have already sent reports: It would be ideal to repeat the test with exactly the same other settings (please mention this in comments when posting).

Thanks to the community

As mentioned, this finding wasn't possible without the great community work of several Jolla owners. Special thanks to jollatides.com & jollasuomi.fi for sharing the User Report Tool for their readers.

Forwarding the information

I've sent a link to this article and to the user reports data to Jolla customer care. Answers will be commented to here, if I get one and if it's ok for them - maybe they will also confirm the problem.

In the end, I hope our great community work, multiple user reports and this article will help the whole community to have, in time, even a better phone. We are Unlike! Thanks once again!

UPDATE, Picked up from comments: Two possible workarounds (Software solution and Hardware solution) until Jolla comes up with a Sailfish hotfix

A) Software Solution with developing tools 

(Please check Important below before you start )

1. Go to Settings -> Developer Mode
2. Enable developer mode. Enable SSH connection.
3. Enter or generate a new password after SSH. Remember it and Save.
4. Reboot the phone, open Terminal (Terminal becomes a visible app after enabling developer mode)
5. In the terminal, write the bolded commands exactly as here and press enter after each row:
   
   devel-su
   (your password) <- note: password is written invisible (you don't see your input). When your password is accepted, $ mark changes to #, telling you that you're in developer superuser mode. Go on with:
   systemctl mask tohd.service
   systemctl stop tohd.service
   exit
   exit
   With the first exit you leave the developer superuser mode (# changes back to $). Second exit closes the whole terminal, and everything is done. Your phone will not establish connection to The Other Half any more, not even after reboot, and your idle battery use is 10% of what it used to be. (If you want your phone to connect TOH after reboot, leave the row with word "mask" unwritten)
6. To enable connection again and return everythihg as it was, open terminal and write:
   
   devel-su
   (your password) <- note: password is written invisible (you don't see your input)
   systemctl unmask tohd.service
   systemctl start tohd.service
   exit
   exit
7. Extra: In any time you can check the status of your connection to The Other Half. You can do it either in devel-su mode (#) or in basic mode ($) with this command:
   
   systemctl status tohd.service
   
   Important: Playing with developer mode might affect to your phone's warrantly. These commands are tested by several users and they don't seem to break anything, but writing something else might - so please doublecheck every letter before pressing enter. Everything you enter in the developer mode is in your own responsibility. If unsure, use the HW solution written below (after terminal images)
   
   Note: There has been some testing going on with disable / enable commands also. They might work, even as good, and they can be tested as well. However I would recommend the masking procedure above, as otherwise the system is left a change to enable connection later for other reasons (if there are any, I don't know), or the system halts in cases where it excepts that tohd isn't disabled. Commands instructed above (5) should give a working, permanent solution, which will last until commands (6) is given.

Image 1, Jolla terminal: TOHD checking, masking, stopping and checking again. Note one typo in "service". Note also that the exit written only exits the devel-su mode (# -> $). Second exit entered would close the app. Click twice for full size img.

Image 2, Jolla terminal after REBOOT: checking, failing to start (in testing purpose) and finally starting TOHD.

B) Hardware solution with foil

1. Reboot your phone without The Other Half. (For testing in the end: Change your ambience)
2. Cover the NFC chip with a suitable piece of tin foil.(3 layers is found to be enough)
3. Attach The Other Half. (To be sure the tin foil is in place, your ambience shouldn't change now.)

Both of these solutions fixes the battery drain problem (tested). I recommend the upper, but if writing to a Sailfish terminal scares you a bit, just go with the HW solution. It should work as well, if there's enough foil. You might also just wait for a while, as reading the comment below written by Harri Hakulinen (Chief engineer at Jolla) we can guess that the hotfix won't take forever. Isn't it just great how Jolla community and Jolla the company can do things faster together? Now let's give them and ourselves a well earned Christmas holidays, and let's be patient while waiting for the Sailfish update fixing the problem.

LG Optimus Dynamic II Tracfone Smartphone

News for the LG Optimus Dynamic 2 - LG L39C

The LG Optimus Dynamic 2

Tracfone recently released four Android smartphones for use on their wireless prepaid network and one of the phones was the LG Optimus Dynamic. (click for our review)

Unfortunately many people were underwhelmed at the lack of features, and the older 2.3 Android operating system.

But Tracfone has now released the LG Optimus Dynamic II - an upgraded and more powerful version of the first. We started to hear rumors about the possibility of another Tracfone Android, but now we have found confirmation through multiple sources.

NOTE: Check out our Full LG Optimus Dynamic II Review now!

The Dynamic 2 comes with Android 4.1, the latest of any Tracfone smartphones, and boasts other great features like a 3 mega pixel camera, and 3.8 inch touch screen. The touchscreen on the Dynamic II is bigger than any of the other smartphones offered by Tracfone.

You can find the LG Optimus Dynamic II on Amazon and several other online retailers, but we haven't found it available directly through Tracfone yet.

We will be completing a full review of the Dynamic II in the near future, until then you can check out the LG Optimus Dynamic 2 User Guide.

Or you might find the Dynamic 2 (LG L39C) online tutorial useful for learning more about this phone.

What to Expect from the LG Optimus Dynamic II

At this point there is little information about how good the phone really is, but based on the specs and features, it seems like it could be a contender for Best Tracfone Cell Phone.

The Dynamic 2 comes with all the features one would expect on an Android Smartphone, like WiFi, GPS, gravity sensor, mp3 player. hands-free speaker, and even 3 home screens.

The size of the phone is pretty normal for a smartphone, at 4.43" x 2.55" x 0.47" and weighing in at 4.5 OZ.

Battery life seems like it will be a little better than Tracfone's other smartphone offerings, with talk time of up to 8 hours reported, and standby of 11 days.

One of the best features of the Dynamic 2 is price, it appears to be priced less than or around the same price as the Samsung Galaxy Centura.

We found the LG Optimus Dynamic 2 on Amazon for $99, but we haven't been able to find it on the Tracfone website yet. It has also been seen on some other retail websites, and even in some stores.

We will be doing a full review of the Dynamic 2 once we gather the information, until then, leave a comment below with your thoughts or questions.

If you're looking for Android phones with Tracfone, read some of our other smartphone reviews, including the ZTE Valet and Huawei Glory.

Ambience background design

This post is for helping people in designing their own ambience backgrounds for Jolla. Knowing how Sailfish OS handles images or photos when turning them into an ambience might give you some advantage to create the most beautiful backgrounds.

While scrolling from screen to another, first thing to note is that the lower you go, the more Jolla cloaks the image - ending up with 100% cloaking in the 2nd launcher screen. Cloak is a partially transparent layer on top of your image, colored with the same tone as the text color which Jolla chooses from the image (see using greyscale images).

Second, let's take a look at the pixel limits for each element and screen. Ideal size for a background image is 540x1600px to take the full advantage of the partial scrolling of the background. In this guideline, top is considered as y = 0 and the pixels mentioned are counted from the top.

Pulley menu header, sized 540x113px, is visible only when the pulley menu on top is opened. If using e.g. a logo on this area, note that the first selection "Settings" is partially inside this area. When using a logo in center, leave it above 100px.


Lock screen image begins right after the header, showing area from y=114 to y=1073 (height 960px). The upper part of the lock screen area is also used as a background for the pulley menu (from y=0 to y=430). The lower part is shared with the home screen. Area not visible on the home screen begins from y=114 and ends to y=353 (height 240px)


Home screen image, y=354 to y=1313 (height 960px) is already cloaked strongly. Image is quite dark and toned with the text color, hiding any colourful details. The opposite colous (compared to the text colour) turns into grey.


Home screen image bottom, from y=1074 to y=1313 (height 240px) is not shared with the lock screen. There, if you want to design a backround for your favourite apps, you can top it between y=1150 (right below the covers) and y=1184 (right above the app icons). It looks good in the middle, setting favourite apps background from y=1167 to y=1313 (height 147px)


The 1st launcher screen background is so strongly cloaked that it doen't matter much in designing. Leaving it totally white tones it with your text color, barely visible (better visible with high screen brigtness). With white, 1/3 of your launcer background bottom differs from 2/3 on top which is cloaked from your home screen image. Area visible only on the 1st launcher screen is from y=1314 to y=1600 (using one launcher), or from y=1314 to y=1457 (using two launcher screens). 2nd or further launcher screen are cloaked 100%.

Some suggestion based on these measurements:

• Use a header, sized 540x113px. It's nice to have a hidden element, only visible when opening the pulley menu
• Share a photo among rest of the screens, sized 540x1200px. The top of the photo works as a pulley menu background, the bottom is visible only in your home screen, the last 140px beeing left behind your favourite apps.
• Use a simple, bright coloured square for the rest, sized 540x287px. With this square use can try to affect to your desired text colour (however if your photo is already colourful, Jolla might choose a color from that anyway).

Download the image of this post to help you in design

Image above has a full size of 540x1600px. You can freely use it - click it twice to open it in full size, save it to your computer and use it as a background on your image manipulation program. You can also see how it looks like as an ambience background on your Jolla to see the measurements in action.

Share your Ambience designs or find great ambiences to your Jolla

You can already find a lot of great backgrounds, all in the right size (540x1600px). So far there are mostly pure images (without header/other special designs), but I hope we'll see some full designs soon too.

• If you have a dropbox account, you can upload your designs here.  
• Lot is shared also at JollaWalls, service was opened Nov-2013
• KiriKrush (twitter link) has been very active with his flickr album

Jolla Ambience / background articles elsewhere

• JollaUsers, another great blog, has shared a similar article earlier
  (with much better images but with some less mathematics)
• Discussion around ambiences at Jolla Together
• (comment with your link, I'm happy to add more)

SailfishOS Ported to Nexus 4

One of the most touching videos I've seen as a fan. SailfishOS is an operating system developed by Jolla. It's spreading to other smartphone models by experienced users, latest beeing Nexus 4. (Earlier seen on Nokia N9 & Nexus 7).

Great video of installing and starting the new operating system by sledges (Youtube link)

The story of Sailfish is just in the beginning - I wonder what will be the next conquer?

Nexus 4

Jolla: GPS Navigation (updated: bug located)

Update 2:  Navfree above version 2.1.14 doesn't get GPS connection.

Recommended not to update above this version (2.1.14), which seems to be the latest working one.

Update: Location data bug located - I call it a GPS Velocity Bug

User have been wondering why several Android Navigation Apps running on Jolla shows the car location at closeby roads and crossings, or shows you driving sideways / backwards. I've been observing this behaviour the best I can, and by that I'm pretty sure that there is a bug in the velocity data calculation, calculated from the gps data.

Jolla uses OpenSource code Geoclue, originally contributed by Garwin, for location data handling. This code should provide all the needed data very well, so the problem is within Qt or Sailfish code. My findings are based on observations only, so I can only share some possible options for the type of this bug. Either:

•  Location is shown in the Navi app before the direction calculation is done. In this case, the Navi App would assume the direction sometimes as 0 (pointing to North)
• Direction is calculated with inaccurate data. It should be calculated from the last two readings provided by gps, and if either of these readings is occasionally missing or old, the direction could show anything (e.g. making the Navi app to circle the map)
• Direction data is not calculated at all. In this case the Navi app might show it as north all the time. 

In a modern smartphone there are three ways to determine the phone current direction: (1) Directly from the magnetometer data, (2) calculated from that and the accelerometer data, or (3) calculated from two data readings received from GPS. Navi apps are using this method.

Some Navi apps are able to use compass (Magnetometer sensor) as a supportive reading for the direction (e.g. when gps data is missing). Jolla's compass should work fine, but it's currently providing data to only some of the Android apps. (This is another known bug already under work. I'm expecting it to be fixed after Qt 5.3. release). However, this is not related to the velocity bug.

We are also looking forward for a native Navi application for Jolla phones, but it's not expected to be released yet in the next update. I'm not expecting a fix to the velocity bug either unless it's very small, as it was just discovered (well, I suppose some coders have noted this earlier)

Original article 12-Dec-2013

While waiting for updates to HERE Maps features, here's a simple HowTo for installing GPS Navigation to your Jolla smartphone. Voice navigation included, tested to work myself.

INSTALLING

1. Register a Jolla account (needed to access Jolla store in the phone)
2. Open Jolla store and install Android Support (close the store)
3. Open your phone browser, go to address m.aptoide.com/installer.* Install Aptoide store (close browser)
4. Open Aptoide store and search Navfree. Install the application (close the store)
5. Open Navfree, follow the instructions and load your countrymap into the phone. WLAN recommended - e.g. road map files for Finland were 180Mb
   
   *Note: I made a typo (missing e) in the store installing address before. Corrected now.

USAGE

1. Enable Location in your Jolla settings
2. Start the app, wait for GPS lock and on to the road.

TEST NOTES

1. User inteface works perfectly. Navfree has a nice set of settings.
2. Supports voice navigation, POI's, speed cameras, speed limits (in selected countries) etc.
3. Full offline support. To navigate, no connection or SIM card needed. 
4. Sound (finnish tested) was loud and clear, instructions ok too. No need to use with max volume.
5. In my first time, driving was shown in reverse on the map. Restarting the phone fixed this.
6. If you navigate without internet connection, the phone might ask for it. This doesn't prevent the navigation app to talk, but the question screen hides the map. Tap to clear, but it appears again.
7. You can drop the app to your home screen (swipe from left/right). Voice navigation keeps on running, but the map doesn't update in the active cover screen. Tapping the active cover opens the app and updates the map again.
8. Landscape mode works well, even when dropping the app to home screen.
9. If you close your screen yourself (swipe from up), navigation stops talking. I haven't tested if it stops talking when the screen is closed automatically.
10. Navfree offers free map update download 4 times a year

Coming up...

My next app related blog post will reveal how to enable Adobe Flash Player on Jolla, with no special tricks needed. Comments are welcome, if you have wishes for the one after that. Thanks for your visit.

Jolla community - together.jolla.com - A peek in after a month

together.jolla.com is a portal between Jolla's customers, app developers and the sailors working at Jolla. It was taken into use at 12-Dec-2013, and after a month in use Jolla phone owners have found it as a welcome and a well used service. More than 2500 questions are posted, and more than 1500 of them have at least one answer. Adding all the answers and comments there are more than 16 000 posts so far.

Jolla has developed the portal further by adding a Jolla logo to all the members working at Jolla, and currently they are welcoming some more moderators from the user side. Users have done their best avoiding duplicate posts and tags, but as there are many of us, there's some cleaning to do all the time. We're doing it together, and in my overall experience the portal is working somewhat great, but it can always get better.

Most important issues (TOP10, lifted up by the users) in the beginning have been:

1. Differentiate native SailfishOS and Android apps in Jolla store
2. Landscape mode in keyboard, gestures, browser and messages
3. Support for CalDav-based calendars (e.g. Google Calendar)
4. Offline turn by turn navigation in Maps
5. mms - multimedia message [closed]
6. After screen time out, return to last active app
7. Folder support in app launcher
8. Add possibility to configure what is shown on the lock screen
9. Cover-action on settings app
10. WiFi tethering [closed]

Jolla is responding to their users wishes, and most of the requests above (and many others) are already roadmapped by Jolla. A 'roadmap' tag is added to the questions by Jolla after they have taken the issue under development. Only 3 of the top10 questions are still waiting for a solution:

• #4 (Jolla's answer: We're thinking about it)
• #8 (Jolla's answer: Good explanation why it is the way it is, but still looking into this)
• #9 (Jolla's answer actually seems like it's roadmapped, but for some reason it isn't)

If you have a Jolla phone but you haven't joined this portal yet, I recommend doing so. Not only to get your questions answered (either by Jolla or other users), but also to be in the heart of this unlike community. We Do It Together (DIT) and we welcome everybody along.

HowTo: Jolla and DLNA media sharing

Basics of DLNA

DLNA (Digital Living Network Alliance) is often wrongly understood as a streaming format, actually it's a non-profit trade organization founded by Sony (2003). DLNA supporting devices, apps and programs are using Universal Plug and Play (UPnP) for media management, discovery and control.

A device/program/app supporting DLNA can include a media server, a media player, or both of these. Media is streamed from the server to the player usually via WLAN network on which both the server and the player are connected to. Several servers and players can be included into the same network.

1. Stream from Jolla to your DLNA players

I've managed in this using Android App "Smart TV WiFi Remote + DLNA". It's a free app, no accounts needed either, and it works perfectly on Jolla too. Here's the Installation guide:

• pre-requisites: DLNA supporting WLAN router (most of them do). Jolla phone and your media player must be connected to the same WLAN network.
• system-requirements: Samsung or LG television or Blueray player, or any DLNA capable media Player on your computer (I'm using a free program "Samsung All Share" on win7)

1. Install Smart TV WiFi Remote + DLNA to your Jolla. I found it at Aptoide store as a trusted app. (Guide for installing Aptoide store can be found on a previous article)
2. Start the app, select "DLNA" and select your desired folders to share. The app has access to both your Android and Sailfish folders, showing them as one type.
3. After selecting, you can drop the app to your home screen and use your Jolla normally. Media sharing to your network stays on as long the app is running.
4. Connect to your Jolla with your DLNA capable player. If Jolla is not found automatic, check your Jolla's local network IP (usually 192.168.X.X) from the phone or from your router and connect to it manually.
5. After the player connects to Jolla's shared folders, you can just browse them and play the content (images, music, videos) of your player supported formats.

2. Using Jolla as a remote control
 (possible at the same time when streaming media from Jolla)

As the DLNA Server on Jolla can be left running, you can use another Android App on Jolla at the same time, remote controlling your DLNA Player. There are several remote control apps available for several TV/Blueray/DLNA players, just check the Aptoide store for your model. I'm using Samsung BD-5500 as the player, so I installed app "Samsung Remote" to my Jolla. In this photo I'm streaming a video saved to my Jolla, watching it from my TV and remoting the playback with Jolla:

3. Stream to Jolla from Plex media server

There are propably also other DLNA capable player apps which Jolla supports, but as I already wrote a review using Plex media server for this, here's an installation Guide for Plex:

• pre-requisites: WLAN router on your computer. Jolla connected to the same WLAN network.
• system-requirements: See the Install link below for supported operating systems.
  Plex is widely supported

1. Install Plex to your computer. When using beta version 0.9.8, Plex account is not necessary, just pass it when asked and select the folders you want to share. With Plex you can share images, music, videos and movies to your home WLAN network.
2. Install Plex version 3.2.4.87 to your Jolla phone. I found it available at Aptoide store malow.store.aptoide.com (add the store with writing this address at Aptoide) and 16 other stores. Note: This application has not been checked as trusted.
3. Start the server on your computer. It's running only as an icon near the clock, and the settings are accessed via a web browser.
4. On your Sailfish app launcer you only see an empty icon with the text "com", but you can start the app with tapping that. The icon is visible if you're using an Android launcer like GO Launcher EX
5. Your media server should be located automatic by Jolla. If not, check your media server IP from the computer and set it up manually. After that you can browse and play your shared content on Jolla's screen. Plex transcodes the stream (if needed) on the server before sending it to your Jolla, so multiple video formats are possible.

4. Remote controlling Plex player on Jolla with another phone

While streaming media into Jolla, you can download a remote control for Plex to another mobile phone and control Jolla's playback from that. I succeeded in this installing an app called "Plex remote" to my old Android phone.