We have moved to a new Sailfish OS Forum. Please start new discussions there.

[release notes] 2.1.1 / Jämsänjoki [released]

asked 2017-07-24 12:40:33 +0300

jovirkku gravatar image

updated 2017-10-02 21:55:27 +0300

olf gravatar image

Jämsänjoki update fixes dozens of bugs reported by our community, adds many improvements and new corporate features, like mobile device management (MDM), new Camera user interface with quick access from Lock Screen, smarter Calendar on Events, WPA2 Enterprise PEAP support, new VPN options (PPTP, L2TP), Bluez version 5 for Jolla C and much more.

Thank you for your contribution in improving Sailfish OS!

PLEASE NOTE: This is a BIG update as some major libraries have been touched. Therefore 1) Keep your device connected to a charger. 2) Wait patiently - the download may take tens of minutes.
-- If you have Call Recorder from Openrepos installed, uninstall it before the upgrade.

Upgrade version history

  • 2017-07-24: Released to Early access subscribers
  • 2017-07-28: Released to Early access subscribers
  • 2017-08-24: Released to Early access subscribers. OpenVPN improved.
  • 2017-08-29: Released to all. [Roll out ceased on Aug 31 for now due to few problem cases with the security code. We are investigating the issue.]
  • 2017-09-20: Decided to discontinue the roll out of 2.1.1. We will focus on finalizing 2.1.2.

Release Highlights

This list contains examples of new features added to SailfishOS since the 2.1.0 release (and some bug fixes).

Aliendalvik [on Jolla C devices: version 1.0.63]

  • Fixed issues in using Facebook Messenger over a mobile data connection
  • Android music apps now publish music artist to Lock Screen.
  • Backspace now deletes the selected URL in browser search bar (Android browsers like Chrome or Opera)
  • Text editor character input behavior aligned with native Sailfish OS, including fixes for word suggestion, autocorrection and line break input cases.
  • Issues related to adding contacts with website item fixed.
  • WhatsApp conversations now show correct timestamps.
  • Alien Dalvik fixed to better respect Sailfish OS location settings
  • Reception of notifications and notification sounds for android apps fixed.
  • Stagefright vulnerability CVE-2015-6602 fixed.
  • An issue of some Android apps getting killed when user taps on their notifications on Events view fixed.
  • Frequent crashes of Alien Dalvik's background processes caused by Qt 5.6 upgrade fixed, causing instabilities with many sub-services like audio, haptic, lights and notifications.
  • Some Android apps not always seeing the new pictures issue fixed.
  • OpenSSL upgraded to 1.0.1j to fix Alien Dalvik's OpenSSL vulnerabilities (CVE-2015-4000, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1791, CVE-2014-8176, CVE-2015-1793).
  • Some missing default Android sounds included fixing notification tone playback issues.
  • Clearing Android app data now shows remorse popup.
  • Android app settings now display how much disk space the app requires, i.e. Android app, data, cache and total sizes.


  • Routing low quality audio (8 kHz mono) to Bluetooth headsets not meaningful - SCO audio disabled for media use cases (non-call).
  • Dedicated PulseAudio configurations for Bluez4 and Bluez5.
  • PulseAudio extended to support Android 6.
  • Voice calls fixed to work with Bluez5 HSP/HFP.
  • Added support for HSP profile audio with Bluez5.


  • Bluez5 taken into use on Jolla C devices. Bluez4 remains the default on Jolla 1 and Jolla Tablet. ( http://www.bluez.org/about/ )
  • Support for voice calls with Bluez 5 HSP/HFP.
  • Enabled FTP profile in Obex / BlueZ 5.


  • Text selection markers are now cleared when opening a new tab
  • Password saving works again
  • Smaller bug fixes.


  • New Camera interface introduced with easier access to camera/video and front/back camera toggles.
  • Taking pictures without unlocking device. Camera can be brought up by a swipe up from the lockscreen. The new shortcut is optional and can be disabled in Settings > Gestures.
  • Viewfinder's focus lock duration shortened from 10 to 5 seconds, and the general focus handling improved.


Customization and configurability

  • Improved configurability for different vendors. Now vendors can drop more easily things like Developer Mode, Sideloading, Store and Sailfish OS updates.
  • Device security lock can be configured according the vendor security requirements: maximum and minimum code length, locking timeout, expiration, maximum attempts
  • Vendor can enforce OpenSSL-based secure code generation
  • Startup wizard made configurable to allow customer modifications.

Device management (MDM)

  • https://en.wikipedia.org/wiki/Mobile_device_management
  • Remote device management APIs introduced for Device Lock, Location, Connectivity, Notifications, SIM and System, OS Upgrades and SW Management
  • Policies added for Camera, Location Settings, OS Updates, Side Loading, Developer Mode Settings, WLAN, Internet Sharing and Device Reset
  • Device management is not enabled or even installed on vanilla Sailfish OS devices.


  • Email app now starts faster.

Events view

  • Upcoming calendar events from the following days also shown.


  • Ability to enable/disable fastboot flashing in Settings > Developer mode on developer devices (e.g. Jolla C).
  • Issue with Gallery hanging if screenshot is taken while certain Gallery app views are open fixed.

Input and Keyboard

  • Tatar language added.


  • Tatar language added.
  • Russian time zones updated.
  • Date picker now handles Sydney timezone correctly.


  • Google Talk support removed due to Google dropping support for Google Talk XMPP
  • Draft message recipients can now be modified.


  • Notes cover layouts polished for different display sizes.


  • Performance enhancements on PDF files: PDF table of contents is now loaded in the background as it can take time. PDF search was changed to process document incrementally, making it faster to start showing matches.


  • Repeatedly tapping Call Again button in call ending view no longer breaks the telephony.
  • Close icon shown on call ending state you can tap to dismiss the call dialog (you could already tap the dialog to dismiss but people didn't realise this).


  • Becomes public as soon as 2.1.1 SDK has rolled out.
  • Sqlite3 C++ API allowed in addition to the already allowed Qt SQL API in Harbour.
  • New 3rd party API for Content Pickers provided.
  • Thumbnailer API is also published.
  • Public Nemo middleware APIs changed to use CamelCase QML import path naming (Nemo.Domain vs. old org.nemomobile.domain).


  • Vulnerabilities fixed: CVE-2015-8842, CVE-2016-7911, CVE-2016-8655, CVE-2015-8966, CVE-2015-5364, CVE-2016-10229, CVE-2015-6602, 2015-3288, CVE-2016-6761, CVE-2016-9793, CVE-2016-7910, CVE-2016-3134, CVE-2016-6758, CVE-2016-7117, 2017-6074, CVE-2017-7184, CVE-2015-2686, CVE-2017-6074, CVE-2015-3288, CVE-2017-1000366, CVE-2013-2207, CVE-2014-8121, CVE-2015-1781, CVE-2015-5277, CVE-2015-8776, CVE-2015-8777, CVE-2015-8778, CVE-2015-8779, CVE-2015-8982, CVE-2015-8983, CVE-2015-8984, CVE-2016-1234, CVE-2016-2856, CVE-2016-3075, CVE-2016-3706, CVE-2016-4429, CVE-2016-6323.
  • Vulnerabilities in Alien Dalvik fixed (Jolla C only): CVE-2015-4000, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1791, CVE-2014-8176, CVE-2015-1793.
  • New users are prompted to add a security code during the first start up to prevent others from using the device if it gets stolen or lost. Can be skipped.


  • Tapping disk space low notification opens up Disk Usage settings page.
  • OS Upgrade settings page available disk space calculations didn't refresh properly, now fixed
  • Update option for disk space added to pulley menu for Settings > Storage.
  • Show IMEI software version on About Settings page by long-pressing IMEI detail.


  • Reliability of system gestures improved
    • Dismissing of calls and alarms
    • Performing edge gestures used to return from app to Home or slide in system panels like App Grid or Top Menu.

Issues reported by the community at together.jolla.com and fixed in this update.


For detailed changelog, see https://together.jolla.com/question/164350/changelog-211jamsanjoki/.

Updating your device

Your device must be connected to the Internet and signed in to your Jolla account. If your Jolla account is registered for Early Access releases you should receive an OS update notification when an update is available. If you have decided not to take the Early Access registration then you will get the OS update typically one week later.

We warmly recommend making some 3-4 GB of free space to the internal storage of your device before starting the update. Move your pictures and videos to the SD card (or to your PC or cloud service). After the upgrade turn on the option to save pictures and videos directly from the camera to the memory card (Settings > Apps > Camera). This is important particularly in case of "Jolla 1" devices (product name "Jolla" in Settings > About product).

This is the usual drill before attempting to update your devices:

  • If you use Phonehook from OpenRepos, uninstall it before upgrading.
  • If you use oFono from OpenRepos, revert to the official oFono before upgrading (or else you may face problems with LTE etc.).
  • If you use Patchmanager, revert all applied patches before upgrading.

Take a backup of your data before attempting to update your device and save the backup to an SD card or to some other off-device location (PC, your cloud service). Note that videos and images are not included in cloud-based backups. Do not reboot the device while the update is in progress. Do keep the phone connected to a battery charger during the whole process. Device screen may blank out during the update process; you may waken the display by a short press on the power key to monitor the progress.

For detailed instructions on updating software, visit Zendesk [ https://jolla.zendesk.com/hc/en-us/articles/201836347 ].

Known issues

  • OpenVPN works now. However, the device must be restarted one time after adding any new VPN configuration to it (we are investigating what is causing this). After that one reboot the configuration(s) existing in the device do work and can be switched without rebooting. Apologies for this limitation. VPN on Sailfish OS is still in beta phase.
  • If you have Call Recorder from Openrepos installed, uninstall it before the upgrade. Otherwise the upgrade will fail and most likely put the device in unbootable state.
  • Reliance Jio SIM cards (India) work in SIM slot #2 only according to some reports. We are not aware of similar issues in other networks.
  • Bluetooth pairing may occasionally fail (on Jolla Tablet, in particular), or turning Bluetooth ON may fail. In such cases it is best to restart the Jolla device and try again.
  • Bluetooth pairing may fail with some car models. Sometimes synchronizing the phonebook may fail, too, and some problems with audio playback appear. Especially on Jolla C. To be investigated and fixed.
  • Two of the Utlities do not work currently. Will be fixed.
  • Not all Jolla C devices can be updated directly from an early OS version (e.g. 2.0.0) to 2.1.1. An intermediate step is needed. This can be done on the command line (Terminal app, developer mode enabled):

Step 1:

ssu re
version --dup

Step 2:

ssu re
version --dup
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2017-10-02 21:56:02.864262



Jolla utilities need update, some option not working

TMavica ( 2017-07-24 14:11:19 +0300 )edit

TMavica: which options do not work? Any error messages if you try use them?

jovirkku ( 2017-07-24 14:22:06 +0300 )edit

@jovirkku Restart keyboard or Refresh media database

atlochowski ( 2017-07-24 15:00:18 +0300 )edit

Great to see another big update :) Just one question: if I understood correctly all the listed AlienDalvik updates and fixes are exclusive to Jolla C? Checking my Jolla 1, it seems it's on 0.17.35. No bump there, then?

walker ( 2017-07-24 15:12:44 +0300 )edit

restart keyboard I found

TMavica ( 2017-07-24 15:59:36 +0300 )edit

31 Answers

Sort by » oldest newest most voted

answered 2017-07-27 20:27:17 +0300

eber42 gravatar image

Google Talk support removed due to Google dropping support for Google Talk XMPP

Google has replaced Talk with Hangout but they have not removed XMPP access (it is still running great).

According to this googleblog link: "Third-party XMPP clients will continue to work with Hangouts for 1-on-1 chats" (only the federation part has been dropped and it was announced a long time ago).

Unless I missed some news, I think Jolla should revert this change.

edit flag offensive delete publish link more



There is an easy workaround: just add an XMPP account manually, using your e-mail address as user name, the server is talk.google.com, the port is 5223. If you use 2-factor auth, you'll have to set up an app-specific password though.

JMairboeck ( 2017-07-29 11:01:20 +0300 )edit

Waiting for comment from Jolla on this one.

vm ( 2017-07-29 13:29:08 +0300 )edit

I think removing the half assed broken NON-Federation stuff is better than trapping people in the mess of Google. Moreover, the integrated support of XMPP will not be improved it should be removed. It is super convenient, but it is a mess: No OMEMO, NO SEND and RECEIVE notifications, no ERROR-Messages on not delivered messages (switch to SMS-Mode to see them), no FILE-Transfer and so on, no Audio/Video-Chat and a lot of more stuff. I'm using now Conversations (Android) and Chatsecure (iPhone) and even encryption is convenient, everything works reliable and all the awesome features are available. Sorry, either Telepathy or Jollas support for Telepathy are rotten.

hoschi ( 2017-08-01 13:07:15 +0300 )edit

Reassign to the Google site helps and it is still working for me ;)

EDIT: after some time I've tried to send some message through it and it doesn't work and same for @JMairboeck tip.

tom.i ( 2017-08-03 13:07:25 +0300 )edit

@tom.i - I can confirm - manually adding XMPP doesn't do anything and it doesn't add the account to the Presence menu.

incognito ( 2017-08-31 17:15:19 +0300 )edit

answered 2017-07-24 18:22:07 +0300

Nokius gravatar image

If you Update your Jolla 1 make sure you unattached the TOHKBD there systemd dependencies causes problems while booting. The symptoms are long booting times and not working wireless network.

edit flag offensive delete publish link more


Completely unattach the TOHKBD or only leave the keyboard unconnected?

naytsyrhc ( 2017-07-24 19:30:47 +0300 )edit

Ok. I can confirm. After upgrade, TOHKBD2 must be kept unattached (full other half) or phone will not get network access. Any workaround/fix known?

naytsyrhc ( 2017-07-24 21:21:40 +0300 )edit

Same for me.... OK, but restart without TOHKBD and that's work...

I waiting for use it.

kaulian ( 2017-07-25 00:16:42 +0300 )edit

Exact same thing with TOHOLED. Although upgrading sailfish was not interrupted on a clean - factory settings - jolla (and toholed attached with the service installed) at first boot networking was not working thus wifi couldn't be turned on. Rebooting with no other half attached fixes the problem and didn't see any issues after attaching toholed. Still this is a bummer...

MemphisX ( 2017-07-26 13:44:02 +0300 )edit

Yhm, yeah, my symptoms seem to be long boot time & no mobile network at all when booting with the tohkbd attached, and when it's unattached while booting, I do get mobile network, but still withoug mobile data. ): Not much use for my Jolla now, without being able to use irssi... A fix would be much appreciated!

Kipe ( 2017-08-31 13:56:56 +0300 )edit

answered 2017-07-24 19:27:07 +0300

Direc gravatar image

Is aliendalvik still being updated for Jolla 1?

Is Bluez 5 coming to Jolla 1 at some point?

edit flag offensive delete publish link more



@Direc, this is not an answer!

To answer your questions:

a. Google is not updating AOSP < 4.4 any more.

Hence there are no fresh upstream fixes to apply to the AOSP 4.1.2 based AlienDalvik for the Jolla 1 phone (unfortunately).

The AlienDalvik on the Jolla C is based on AOSP 4.4, IIRC.

b. That is Jolla's declared long-term plan, IIRC.

olf ( 2017-07-25 00:15:31 +0300 )edit

@olf any chance for updated aliendalvik for the jolla tablet? it's also 4.4 as on jolla C, however current version is 1.0.29

szopin ( 2017-07-25 01:44:28 +0300 )edit

Ah shoot. I meant to add a comment, not an answer... Sorry bout that.

Isn't Alien Dalvik fully third-party (Myriad) made and not tied with AOSP releases..?

Direc ( 2017-07-25 22:40:32 +0300 )edit

@szopin, see first entry of this release notes!


a. Yes.

b. What do you mean with "tied"?

olf ( 2017-07-27 22:17:27 +0300 )edit

@olf yeah, jolla C got 1.0.63, tablet even though also 4.4 is stuck on ancient 1.0.29 as jolla never updated the x86 alien dalvik that is on tablet (and seeing the amount of security fixes it really sucks for the youyota buyers, not to mention the amount of apps that just won't start)

szopin ( 2017-07-29 01:27:23 +0300 )edit

answered 2017-07-24 17:24:48 +0300

pawel gravatar image

like the new photo app controls !

edit flag offensive delete publish link more

answered 2017-07-27 13:41:10 +0300

jovirkku gravatar image

We have found an issue in the OS update repositories such that installing updates from 2.0.5 (or earlier) to tend to fail. This is being fixed in the update servers. Updates => should work ok. Note that 2.1.1 is a big update due to some vulnerability fixes in the libraries. Because of this the download phase can take tens of minutes. Apologies for the inconvenience caused.
-There will be another release candidate for early access subscribers one of these days.

edit flag offensive delete publish link more

answered 2017-07-25 12:02:36 +0300

hoschi gravatar image

updated 2017-07-25 12:25:00 +0300

Qt Connectivity updated to Qt 5.6

Great to see this upgrade, maybe it fixes some issues. But finally my Jolla started to fail seriously, it didn't reconnect to the carrier-network after a connection lost. Which could not only happen from time to time, in my case two times a day, in the underground garage. I couldn't fix it with a network-restart, just full reboot of the device. Maybe my GSM-Modul was damaged, but I think a lot of Qt-Stuff has problems which Jolla couldn't fix themselfes (e.g. WiFi/Cell-Network-Switching).

edit flag offensive delete publish link more



I experienced the same today on my Jolla1 - my device was unable to connect to mobile network after leaving home and the WIFI network. Restarting the network via Sailfish Utilities did not solve this issue and I had to reboot my device.

Alex ( 2017-07-25 20:57:23 +0300 )edit

Same.problem for me. Very serious issue.

lispy ( 2017-07-25 21:59:11 +0300 )edit

@Alex and @lispy: Did you experienced that on the or the old release?

It was serious for me and I switched to an iPhone SE for this only reason. Not only the undergroudn garage was an (planable) issue twice a day, it could happen any time in a building or during sports in the woods. A lot of stuff sucks hard on the iPhone (especially SCP/SSH e.g. file moving from/to device) but other things just work right (the pull all emails initally! Like any normal Email-Client!).

hoschi ( 2017-07-26 12:28:44 +0300 )edit

My problem too, since about a year!

florifreeman ( 2017-07-26 15:53:47 +0300 )edit

answered 2017-07-25 14:50:15 +0300

M1CK431 gravatar image

updated 2017-08-25 22:53:23 +0300

Hi Jolla Team,

First, thanks for the huge work achieve for this update :)

Otherwise, I have found some bugs with this new release:

  1. can't open the "os update" section in settings (big problem for next update, probably require CLI actions) -> Related to Coderus patch, fixed in last Patchmanager release (thanks atlochowski)
  2. sometimes, don't ask for SIM PIN after reboot, so no mobile network available -> occur only one time for now so not a big problem.
  3. haptic feedback is always on for pulley menus (even if disabled in settings) -> FIXED in! Thanks Jolla Team!! :)
  4. previously (manually defined) existing WPA2 PEAP entries are ignored when the related network is available (but perhaps it's "normal" because of official support added in this release) -> Workaround 1: change something in the file will force Connman to read it again. -> Workaround 2 (not really a workaround, thanks to Jolla Team ;)): delete the file then register the wlan from UI, like it always should be.

In addition I have some questions:

  1. Since at least one year now, Jolla 1 haven't receive any Alien Dalvik update (understand migration from 4.1 to 4.4 like Jolla C/Tablet). Why? Have you any (good) reason to keep this old version for all Jolla 1 users? -> backport Alien Dalvik 4.4 on Jolla 1 seems need a lot of work because of kernel/driver update and it's not free because of Myriad licensing (thanks yuri). Otherwise, an official answer would be great since it's a question that interests many people.
  2. I'm waiting for Bluez5 since month because I experience many many issues all days of my life with Bluetooth when connected to my car radio (JVC) and again and again Jolla 1 keep the old Bluez4 version. Again, why? Have you any (good) reason to keep this old version for all Jolla 1 users? Can you please give me a way to switch right now from developer options like with Jolla C on previous release?

I'm not an expert in development but I think that maintain an unique Bluez software version is simpler than two isn't it? So I don't understand the manner you deal with that... :( Can you please explain? Please notice that European users have only Jolla 1 as an official public device at this time (Jolla C for dev, Intex Aquafish not officially for European country) so I think you should either give us another official device or offer the same quality (in term of release number) for all supported devices (especially Jolla 1).

Last, but not least, in the past you have a public page with your roadmap (https://sailfishos.org/developmentroadmap/). Have you any plan to update it?

[EDIT] I have update my answer to include some elements from comments. I have also add some typo for readability.

[EDIT2] I have update my answer again because bug 3 was fixed in Thanks Jolla Team! :) Question 2 stay open.

PS: Sorry for my bad english.

edit flag offensive delete publish link more



@M1CK431 "can't open the "os update" section in settings (big problem for next update, probably require CLI actions)"

turn off "Unaplly all pathes on Upgrade" patch. Then everything will be ok. Coderus have to fix his patch.

atlochowski ( 2017-07-25 15:08:52 +0300 )edit

Can't repro 1. 2. or 3. Don't know about 4. But the 2. is apparently caused by TOHKBD.

Sthocs ( 2017-07-25 16:19:58 +0300 )edit

@Sthocs: I haven't TOHKBD connected since month. At this time, this issue occurred after my second reboot only.

M1CK431 ( 2017-07-25 20:08:35 +0300 )edit

Why AD 4.1? Because Android 4.4 comes with A LOT of changes, that the specs of the JP1 propably wont handle. This can cause that the phone feels a lot slower (it is already pretty slow). I think they wont risk any problems with that.

florifreeman ( 2017-07-26 15:49:46 +0300 )edit

can repro 3. on JollaC.

can kind of repro 4. workaround for me was to edit the wifi config file with my wpa2-peap settings to trigger connman to read it again. After that my wpa2-peap wifi worked again.

rincewind ( 2017-07-26 20:31:47 +0300 )edit

answered 2017-07-25 14:25:36 +0300

yuri gravatar image

updated 2017-07-27 20:09:52 +0300

Translations don't work in pure sailfish-qml apps. Tested on jolla1

Edit: offline storage now is in a different path!

before /home/nemo/.local/share/harbour-APPLICATION/harbour-APPLICATION/QML/OfflineStorage/Databases

now ( /home/nemo/.local/share/sailfish-qml/sailfish-qml/QML/OfflineStorage/Databases

edit flag offensive delete publish link more



Thanks for reporting. Will be fixed.

jovirkku ( 2017-08-22 11:35:56 +0300 )edit

Now ( offline storage and translations work again: thanks sailors! :-)

yuri ( 2017-08-25 12:11:28 +0300 )edit

answered 2017-08-05 00:16:28 +0300

caa gravatar image

Mobile data and MMS access point settings now allow you to change the authentication method (no, PAP, CHAP, automatic).

FYI, on Jolla 1, my mobile data connection didn't work after the update to with the error "problem with connection".

I am with O2 network in the UK, so I checked the APN settings in Settings >> Mobile network >> Data access point and MMS access point.

The problem was the (newly added feature) 'Authentication' setting was set to the incorrect authentication type 'CHAP' for the O2 UK network (O2 UK requires 'PAP' authentication). Once I had set this correctly and restarted the phone, my mobile data connection worked correctly.

Hope that helps someone.

edit flag offensive delete publish link more



Will be fixed to one of the next OS updates. Thanks for reporting.

jovirkku ( 2017-08-25 13:52:42 +0300 )edit

answered 2017-07-25 12:39:39 +0300

Ingvix gravatar image

Nice to have a quick way to get to the camera but you really should be able to get to the photos by swiping right from there. Currently it does not seem to be possible. Of course this feature could be disabled if the device is locked via code but otherwise you really should be able to look at the photos you take.

edit flag offensive delete publish link more



Oh indeed, it doesn't open the normal camera app, a bit useless then :/

Also, in the normal Camera app, when I view the last photos taken in portrait, they are rotated in landscape... And I can't see those new photos in the Galery (I've rebooted and run the indexation but no success)

Sthocs ( 2017-07-25 16:12:26 +0300 )edit

I noticed the same, the vertical photos rotates weirdly in gallery. The ones you take in horizontal are good, though! The photos are there, but now the newest are the last on the gallery. Any way of changing this?

ljv ( 2017-07-25 19:41:58 +0300 )edit

Oh yeah they are at the end of the Gallery, rotated on the left (they are rotated correctly on PC). Old portrait photos are not rotated. Is it just us or is there no more QA at all? :/

Also my whole system is very laggy, especially when swiping the apps to Home. I'm with Jolla 1, already tried to reboot and btrfs-balance.

Sthocs ( 2017-07-25 23:36:26 +0300 )edit

maybe the strange presentation of pictures has to do with this question?

rgrnetalk ( 2017-07-27 01:34:51 +0300 )edit

I think the way it is done is good;

Using camera quickly is excellent since I always have device lock code enabled. If it was possible also to see gallery that would be security breach.

juiceme ( 2017-07-29 11:11:31 +0300 )edit

Question tools



Asked: 2017-07-24 12:40:33 +0300

Seen: 36,027 times

Last updated: Oct 02 '17