[Release notes] 1.1.1.27 / Vaarainjärvi [released]

asked 2014-12-18 17:03:17 +0200

bijjal gravatar image

updated 2017-10-02 22:30:00 +0200

olf gravatar image

Release date : 19.12.2014

Free space required: ~2 GB


 22.12.2014 Update: 1.1.1.27 now being rolled out for all our users

As you may have noticed, the rolling out of Vaarainjärvi was put on hold on the evening of 18.12.2014. At Jolla, we follow a process for staged releasing of software updates, allowing us to gather end user feedback right from the field before making it a mass public release.

This has allowed us to catch the device lock issue spotted by two users yesterday. We promptly put the release on hold and investigated the issue. At this point, considering the holiday season, we decided that it's best to remove the alphanumeric lock code feature from the release.

Our 'First Ones' and Update9 opt-in users have received a hotfix on 19.12.2014.

Existing update10 users, if you have enabled alphanumeric lock code in settings, consider switching it back to numeric, otherwise after accepting the hotfix you will have to stay with alphanumeric mode until Update 11.

The rest of our users will receive an OS update notification for 1.1.1.27 directly without the alphanumeric lock code feature.


Your patience and support fuels our dedication to provide you with a well-prepared release. The OOM handling by the SailfishOS has been significantly improved, thus allowing daily usage of the phone without major hiccups. We are now comfortable releasing update10 to all our users while we continue to work on other improvements.

This is a huge software update if you have not opted in for update9. Please ensure that you have ~2GB of free disk space before attempting to upgrade your Jolla. If connected to the internet, your Jolla should receive an OS update notification shortly.

As usual, before attempting to upgrade your Jolla,

  • Take a backup of your phone content and copy it to SD card
  • Clean up your phone from unnecessary data (old backups, downloaded content etc) before attempting to upgrade the software. This is to ensure that the software update has enough diskspace to complete its operation.
  • If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories

Do not reboot the device while the update is in progress. The 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.

Once the device has rebooted after a successful upgrade, Android runtime starts to update it's environment. Allow a couple of minutes for it to finish its stuff before taking the phone into regular use. Using the phone during this period can appear sluggish.

The release notes includes a combined summary of the highlights from update9 and 10.

The corresponding SDK release will be available on the 5th of January 2015. It will include the updated rpmvalidator which allows the new libraries to be used in Store as announced in the community meeting from 25th of November 2014.
Harbour testing team will start using the new rpmvalidator from 7th of January 2015 onwards (note that 6th of January 2015 is a public holiday in Finland).


Whats new?

UI interaction changes

  • Hierarchy indicator at the top left corner of the view replaced by a single indicator trailing off the edge of the view
  • In accounts settings view, changes made are immediately saved.
    • Previously, an explicit user action (pressing 'Accept') was required.
  • App dialogs are now visually separated from normal app pages by having accept and cancel buttons from the page area to a persistent header

Highlights of improvements

Improvements in core OS

  • New rendering engine that significantly reduces both CPU and GPU load
  • Minimized apps now drop surfaces and OpenGL context to reduce memory usage
  • More responsive Android apps through rewritten Wayland system integration
  • Contacts database loading improvements
  • Ensures that phone UI never gets killed when OOM (Out of Memory) handling kicks in
  • Improved browser memory handling when closing tabs
  • Automatically unloading browser tabs in low memory situation
  • Drops memory-heavy HTML email viewer from memory when not used in a while
  • Loads Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
  • Enables memory compaction configuration option in kernel
  • Adds memnotify patch to kernel to get notifications on memory thresholds being crossed
  • MCE is now able to receive and set up memory thresholds with /dev/memnotify
  • Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
  • Enabled zram in kernel, suggested by community in this post
  • Has a custom Wayland protocol implemented for Android runtime to free memory better in OOM conditions
  • Optimizes call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
  • Makes OOM killer more verbose to further aid debugging
  • Home screen only loads visible notifications to reduce memory usage

Other Improvements

  • Fixed weird cpu usage numbers
  • Improvements to end-of-cpu-keepalive handling
  • MCE over D-bus now introspectable
  • Adds enablers in MCE to allow dimming when the display brightness is already at the minimum in the UI settings
  • Systemtap (https://sourceware.org/systemtap/) now available in Mer and enabled in kernel
  • Sets correct USB identifier for Rescue Mode (Vendor ID 2931, Product ID 0A06)
  • Phone no longer shuts down when connected to the charger while hitting the shutdown limit (0-2%)
  • When the phone is off and the battery is nearly empty (0-2%), connecting the charger now displays the battery percentage in red and provides vibra feedback when the user tries to power on the device by pressing the power key
  • Smoother bootup animations when the device boots up from act dead mode
  • In cases where there are issues in the early boot process of the device, an animation is shown during the auto recovery process to indicate to the user that "something is happening, do not turn off the device or remove battery"
  • Fixes dbus vulnerabilities: CVE-2014-3639 , CVE-2014-3638 , CVE-2014-3637 ,CVE-2014-3636, CVE-2014-3635
  • Fixes CVE-2014-7169, CVE-2014-6271 and CVE-2014-1568 vulnerabilities

Homescreen

  • Opening an app now shows a busy indicator animation on the app cover instead of the static "Loading" label
  • Attempting to view events (via swipe-up gesture on the lock screen) while the device is locked now brings up the device lock keypad to allow unlocking the device
  • Attempting to open an app from Lock screen shortcuts while the device is locked now brings up the device lock keypad to allow unlocking the device and then opens the app to foreground

Connectivity

  • Connection dialog now closes after connecting to a hidden WLAN AP
  • Data counters calculation is now fixed, but resets the previous erroneous values
  • The list of saved networks are now sorted by last seen. Currently connected AP is always listed at the top of the saved networks list
  • While on roaming, the operator name is now displayed under mobile data settings
  • When internet sharing option is enabled, you can no longer edit it's settings
  • Internet sharing requires a password min 8 characters in length
  • Fix to WLAN disconnect issue while roaming due to RSN IE mismatch (Robust Secure Network Information Element)
  • Maximum transmission unit (MTU) of Internet interface for mobile data was downsized to 1280 bytes as some networks do not support big MTU's but drop them. This change may help in cases where mobile data connection does not work reliably or at all.
  • 'Problem with connection' error banners now display connection type icon to indicate the type of connection having issues

Settings/Accounts

  • Modified account descriptions are now saved correctly during new generic email account setup
  • Improvements to handling bluetooth connections to devices with invalidated link keys
  • Checks for duplicate Twitter, Facebook and Google accounts before saving a newly configured account
    • Note: Duplication detection can be done only with newly created Facebook accounts. Therefore, if you have a Facebook account already configured prior to this release, it will not be checked as possible duplicate while creating a new Facebook account
  • Main accounts list now displays account description and username
    • Previously, it displayed account's provider and description
  • 'Add accounts' page now lists generic accounts separate from named providers (like Facebook, Google, Twitter, Microsoft Exchange)
  • Account setup flow now operates on single selection enabling users to setup one account at a time
    • Previously, it supported multi selection of accounts with each account having a different view/option, thus making the account setup flow complex
  • Easily sync Microsoft Exchange account via the context menu option on account list view or via the pulley menu item in the Exchange account settings view
  • Google account setup view now indicates to the user that Mail app is required to use Gmail
  • Configured Jolla account cannot be disabled anymore
  • Sync options under Google and Microsoft Exchange accounts are now listed in the same order
  • Disabling touch screen vibration no longer disables call vibration
  • Changing developer mode password shows up lock code dialog and asks for entering the lock code
  • Enabling Remote connection (SSH) in developer mode no longer requires a reboot for it to work
  • Improvements to Owncloud CalDav support
  • Fixes an issue in the CalDav support that caused non-latin characters to be incorrectly displayed 60213/caldav-sync-to-owncloud-with-non-latin-characters-results-in-question-marks-being-displayed and 55033/caldav-not-supporting-umlauts
  • Restore saved passwords in Browser. Note that SailfishOS does not yet support encrypted backup, so your passwords are stored as is. We recommend you to copy the backed up data onto your notebook and encrypt it if required.

People

  • Messages created with recipient information only are now properly saved under Drafts
  • Expands the background fill on the last row of the alphabetical grid to improve visuals
  • Allows contact to be saved with only company name (previously mandated either first/last name or nickname)
  • Improves link/unlink behaviour w.r.t remorse timers
  • Keyboard now automatically hides when the list of search results is scrolled

Phone

  • Easily copy unsaved number from call log via 'Copy' context menu option
    • Note: this option is only available for unsaved numbers
  • DTMF tones are now played at 50% of the max volume. While on a voice call, it follows the voice call volume.
  • Changing a call barring option now displays a more coherant message "Enter a call barring code" (was previously "Enter PIN code")
  • Disable all call barring settings in one go via the 'Disable all' pulley menu option
  • Display close icon on keyboard enter key on empty call forwarding fields
  • Emergency calls are now made to the GSM standard number 112 unless the user has dialled a different number. The GSM network will route the call as required in each country (where local emergency numbers are in use).

Messages

  • Improved landscape view of received MMS

Mail

Keyboard

  • Moves handwriting engine to background thread to improve performance
  • Improved support for many frequently used traditional Chinese characters in Cantonese, like 嗰、啲、嘅、嘢
  • URL/email mode for Chinese layouts
  • Characters ž (U+017E) and Ž (U+017D) added in the pop-up of character "z" in the Finnish keyboard layout
  • With pinyin input, spacebar now accepts the first candidate only if the user has started writing a new word
    • Previously, spacebar always accepted the first candidate

Media player

Store client

  • Shows busy indicator while loading screenshots
  • Improves startup performance
  • Allows opening just installed Android app from app details view (via pulley menu option "Open")
  • In app details page, "Also from: developer x" section at the bottom now indicates if the apps have been installed
  • It is now possible to check for OS updates again after the system update installation fails on an earlier attempt
  • If the OS update status is unknown, no text is displayed (previously, there was a quick switch from "Checking for update" to "Up to date")
  • If the OS update fails for some reason, the user is now notified promptly
  • If the device is not connected to internet, opening Store client or attaching a TOH pops up the connection dialog to request connectivity

Calendar

  • Event reminders for recurring events now displays the recurring information in the UI
  • Displays attendee information in event details view
  • Fixes the issue of a calendar event going to the next day when creating it after 23:00

Maps

  • Usage of Maps is now governed by the common Sailfish EULA http:/jolla.com/sailfish-eula, application specific EULA has been removed
  • Improved address search from People app using geocoder

First time user experience

  • Additional hints added to accounts settings
  • Simplified startup wizard flow

Silica components

  • Improvements to silica webview component: now allows peek previous and next page when content pinched in
  • Email addresses (in format email@address.com) in plain text are now recognized and displayed as link (textlinking)
  • People picker now has search field always visible
  • Updates signal strength status icons
  • Updates duration label to m:ss for <10 min and mm:ss for >10 min
  • New detail item component available for detail and value label pair
  • Allows re-opening keyboard when tapping already focused text field
  • Allow count-specific localization of component picker multi-selection title
  • Fixes issue where slider component handle disappears and cannot get activated again
  • Unifies button and list item press effects across SailfishOS apps

Android runtime

  • Android runtime now follows the vibra settings set on the native OS
  • Fixes Android fake id vulnerability
  • Fixes CVE-2013-6272 and CVE-2014-3100 vulnerabilities
  • Updates notification update mechanism which fixes the display issues in events view when there are notifications from multiple apps in succession
  • Adds network provider support for GPS service
  • Sending a mail from android apps now passes email parameters such as subject, body etc to the native mail application
  • Improves handling out of memory conditions
  • Timezone in Android apps now follows the native settings
  • openssl upgraded to version 1.0.1h

Known issues

OS update process

  • Currently, checks on available disk space happens very late during the OS upgrade process and will fail in the installation phase if the disk space is low. Normally there should be an error note asking you to free some disk space and try again, but in some marginal cases it might not be shown. Should this happen, free some disk space and try to install the OS update again.
  • OS update may fail due to some other reasons too, for example it may have installed some packages from the new release and still have something left from the old. If the device can boot up, you can try to recover by doing the following. If not, you can attempt to recover the device using the recovery mode.
    • Delete the file /home/nemo/.cache/store-client/os-info
    • Stop the store-client process (for e.g. pkill store-client)
    • Reopen Settings app, check for updates again and attempt to install the OS update again
  • We have also noted that if the OS update is attempted while there is long queue of installation of apps from the Store, the system may end up in mixed state (for e.g. select all the apps from startup wizard, and start the system update already while the apps are being installed).
    • In such cases, the OS update appears to be stalled, however it is just waiting for the installations to complete before attempting to upgrade the OS. Just wait patiently, the worst thing to do here is to reboot the device!

Other issues

  • Audio stuttering has been observed in Android applications. We are aware of this issue and are still working on it. We will push out an update as soon as a fix is available.
  • Sometimes Messages and Phone app show black active covers.
  • calDAV and cardDAV services are in experimental stage. We have made some improvements with this update, however you may still face issues with certain service providers. Do report it in t.j.c. We'll take a look and try to sort it out.
  • At times, the presence status is as displayed offline even though the accounts are online. In such situations, the UI does not allow the status to be changed to online again.
  • Occasionally, certain hidden WiFi networks may not be displayed in scanned results.
  • Photos and videos deleted from Gallery may still remain visible in the Camera roll.
  • Deleting photo from Camera roll may also delete the previous photo. If camera reel's pulley menu has "Show details" greyed out - means the photo hasn't been indexed yet. Deleting photo in such state will result in previous photo deleted too. If you wait long enough (~10-15seconds) for 'Show details' to become active, only that photo will get deleted when you choose to.

Highlights of bugfixes

  • [BUG] Ending call from cover should not bring call window on foreground
  • [BUG] When call is answered the audio routing changes to bt headset if it is turned off when ringing
  • [BUG] Phone settings don't follow current empty state design
  • [BUG] pin query settings page doesn't follow current empty state design
  • [BUG] TOH eeprom is read too soon after toh switch is pushed in
  • [BUG]/home is mounted with relatime, not noatime as it's supposed to
  • [BUG] screen is dimmed upon startup
  • [BUG] Kernel low battery charge warning floods journal logs
  • [BUG] Mer-kernel-check warns on many missing options
  • [BUG] devel-su has wrong XDG_RUNTIME_DIR
  • [BUG] Incorrect statistics of CPU usage, possibly due to a bug in /proc/stat
  • [BUG] Kernel NULL pointer at btrfs_block_rsv_release
  • [BUG] MCE display plugin initialization does things out of order
  • [BUG] MCE evaluates logging format parameters even if the message is not emitted
  • [BUG] Battery state:full is visible when battery is not full
  • [BUG] BUG at fs/notify/inode_mark.c
  • [BUG] Calling stop() for a nemo-keepalive BackgroundActivity does not stop the timer
  • [BUG] KeepAlive from org.nemomobile.keepalive is an singleton object
  • [BUG] Device constantly tries to turn on hdmi output that is not there
  • [BUG] Lots of messageserver restarts on boot if no email account
  • [BUG] lock-ls-mem can fail when lipstick crashes on bootup
  • [BUG] MCE does not skip zero length linger after exceptional display on state has ended
  • [BUG] MCE is using 4% CPU when screen is off causing a load of 3+
  • [BUG] MCE is using blocking dbus calls
  • [BUG] mce-plugin-libhybris build fails with gcc 4.8
  • [BUG] Recovery mode reports: "Flashed recovery image is too old and does not support phone clearing."
  • [BUG] Recovery mode reports: Segmentation fault
  • [BUG] USB dialog does not pop up/selected usb mode not set after unlocking device lock
  • [BUG] wlan-module-load.service should wait for persist.mount
  • [BUG] "Unnamed application is not responding" is shown at times on homescreen
  • [BUG] lipstick leaks sqlite handlers while changing ambiance
  • [BUG] Compositor loses track of windows when opening apps quickly
  • [BUG] Display sometimes flickers to black when opening applications
  • [BUG] Ghost app cover appears in homescreen after opening a web page bookmark from Launcher
  • [BUG] Hidden back button on lockscreen vibrates on press
  • [BUG] In some cases screen blanks and locks again after unlocking device
  • [BUG] it is almost impossible to grab the icon in app grid to move it around since 1.1.0.12
  • [BUG] Lipstick restart turns on display and enables touch input even if proximity sensor is covered
  • [BUG] Switcher allows creating multiple loading covers for the same application
  • [BUG] AccountCreationManager does not emit finished() signal after account creation
  • [BUG] After re-login to Jolla account, it remains in disabled state until store is accessed again
  • [BUG] Store app does not load successfully if you correct your wrong info while creating a new account
  • [BUG] Store pages stays in split view after opening installed application
  • [BUG] If credentials expire while account settings is open the account remains in logged-in state
  • [BUG] Android application cover is striped from upper right corner to bottom left corner
  • [BUG] Android window is sometimes momentarily black when switching between the apps
  • [BUG] The application "Private SMS & call" has stopped after tapping "Feedback".
  • [BUG] Openrice: Can't find nearby restaurants with GPS
  • [BUG] Opera for Android crashes after 1st exit
  • [BUG] QQ Browser (Android app) crashes on Sailfish
  • [BUG] App switcher gets confused with many Android apps
  • [BUG] UC Browser Android becomes unresponsive during startup
  • [BUG] Opened Android app fails to come to foreground
  • [BUG] alien_bridge_server does not check bounds accessing QList (maybe in the Ril code)
  • [BUG] Android applications do not obey locked orientation
  • [BUG] Changing colour in calendars does not work at times and has a bit different look compared to notes
  • [BUG] Call audio problems with Samsung HM3300 headset
  • [BUG] Display is not blanked when incoming call ends
  • [BUG] Reconsider the icon/symbol of emergency call in PIN and lock code dialogs
  • [BUG] Voice call functionality can momentarily block homescreen operation
  • [BUG] Draft message not created if you add only recipient (but recipient is magically remembered)
  • [BUG] Sending a new message to a contact fails to open respective conversation
  • [BUG] Opening same HTML email twice results in blank page
  • [BUG] Inline images in email are not shown
  • [BUG] Loading of really long text email (+10000 chars) freezes MessageItem
  • [BUG] Not able to go back when viewing mail that is zoomed
  • [BUG] Opening same HTML email twice results in blank page
  • [BUG] Connection error banner shown after trying to manually select operator in roaming
  • [BUG] It takes too long to popup the connection dialog after "user input request" from connman for invalid-key error or wispr-authentication request
  • [BUG] Oops no networks found -message is shown after scanning WLAN networks even when networks are found
  • [BUG] scanResultsReady is false when invalid-key-error happens and it will make connections.busy true infinitely
  • [BUG] When user cancels connecting to network "Connecting.." busy indicator starts running
  • [BUG] User can enable the internet connection after changing the "Data roaming" to "Do not allow"
  • [BUG] Connman crashes on after wlan module unload/load cycle
  • [BUG] Tapping bluetooth toggle multiple times in a row on favorite settings gets the toggle in bad state
  • [BUG] Date picker: months disappear when month grid flicked
  • [BUG] People picker cannot be opened on landscape new message page
  • [BUG] Pulley menu flickers on app startup
  • [BUG] Wrong alignment in DatePickerDialog
  • [BUG] Weekdays incorrect near DST changes
  • [BUG] Facebook notification view is empty when opening first time
  • [BUG] Tapping on Facebook notification opens up a new page which is unusable
  • [BUG] Facebook Terms of Service is unreadable
  • [BUG] First posted comment from Facebook album in Gallery is posted twice and not displayed until view is reopened
  • [BUG] Gallery shows incorrect number for Facebook photos
  • [BUG] Active cover doesn't show cover background and when maximized to foreground it shows cover instead of the application window
  • [BUG] Active covers behave weird when there are 7 or 8 apps open on Homescreen
  • [BUG] App switch transition loading order is incorrect
  • [BUG] Gallery creates two instances of TransferMethodModel
  • [BUG] Media Player: Playlists is the only option on a newly flashed device without SD card
  • [BUG] Modified playlist is not reset to the previous state when restored from backup
  • [BUG] Ambienced crashes when a stack size is set to 2Mb
  • [BUG] Hard to see which apps are selected to install during Startup Wizard in certain ambiences
  • [BUG] Startup Wizard: The application background disappears while the application list page is shown
  • [BUG] Maps startup doesn't scale to many favorites, recent and saved places
  • [BUG] Removing saved and recent places does not work
  • [BUG] Maps should prevent dimming when directions are displayed (or I am moving)
  • [BUG] Settings|Utilities page doesn't always scroll
  • [BUG] timezones with parenthesis don't have their own section
  • [BUG] Account settings show incorrect weekdays near DST changes
  • [BUG] exchange settings show incorrect weekdays near DST changes
  • [BUG] roamingallowed is not stored due index is wrong
  • [BUG] settings / datacounters warning on not available counters doesn't look good
  • [BUG] Newly created accounts with disabled services remain in "defining account" state forever
  • [BUG] MMS settings cannot be modified when phone tries to receive MMS
  • [BUG] sailfish-accounts-tool: currently used way of restoring information is error-prone
  • [BUG] Store: Clicking on already installed android store should open the app after a "no results found" search
  • [BUG] 'Received' counter is stuck at 2 GB and does not exceed when you download something
  • [BUG] Notifications takes enormous amount of RAM, lipstick is not starting if there are a lot of notifications
  • View more bug fixes
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by r0kk3rz
close date 2015-07-15 15:23:10.762497

Comments

17

YES, thank you!

Jarno ( 2014-12-18 17:27:43 +0200 )edit
2

WOW I did not even know there was this amount of bugs in the Sailfish O_O

NeWin ( 2014-12-18 17:28:28 +0200 )edit
14

Jolla, thank you for the Christmas gift ;)

Cl2ment ( 2014-12-18 17:34:13 +0200 )edit
3

Thank you very very much for this. "Sailfish OS updates" still tells me that i'm "up do date", but probably i should just wait :)

deseven ( 2014-12-18 17:46:24 +0200 )edit
1

2k+ images used in a game and stored within /data/data/ will still be shown in gallery T_T

Odorobo ( 2014-12-18 17:53:35 +0200 )edit
3

<3 Thank you sailors and happy holidays!

g7 ( 2014-12-18 17:54:48 +0200 )edit
4

This is EPIC! Thanks for the update and have some great Xmas hollidays (all hard working Sailors deserve it!).

Nekron ( 2014-12-18 17:55:17 +0200 )edit

do we need to be OPT-IN for this update? or is this for everyone?

madcheeze ( 2014-12-18 17:56:56 +0200 )edit

I am already on update 9 opt-in, can I get the update 10?

unlikeyou ( 2014-12-18 17:58:35 +0200 )edit

@bijjal i have some little questions: You told at the beginning "If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device." Just to confirm what could happened with os 1.0.8.21 and the aptoide apps? is there something to take care? thanks in advanced for your answer

cemoi71 ( 2014-12-18 18:00:23 +0200 )edit

1.0.8.21. No update available on my Jolla...

nix ( 2014-12-18 18:00:26 +0200 )edit
4

"The First One" people will get the uppdate first, then uppdate 9 loaders and after that all the rest. (info from JollaSuomi-blog). Does anyone know how long it is going to take that rest of us will get the uppdate?

Jozo ( 2014-12-18 18:08:19 +0200 )edit
1

@Jozo: usually doesn't take more than a couple of hours for me to get the update.

nthn ( 2014-12-18 18:11:42 +0200 )edit

hoho i think i will wait a little bit after the jolla server saturation. does jolla have a good insurance for the overheating of their server? @bijjal on how many servers works the os update? how many update request or device could it handle in parallel (if you have understand my question, is quite difficult for me)

cemoi71 ( 2014-12-18 18:14:00 +0200 )edit
3

<3 love love love

magullo ( 2014-12-18 18:18:54 +0200 )edit

well i guess i answered my question, this update is for everyone :) #thefirstone

madcheeze ( 2014-12-18 18:19:56 +0200 )edit
1

Apart from Android/Spotify now being unusable due to the known audio drop out bug this looks like a nice update.

njeiseck ( 2014-12-18 18:21:43 +0200 )edit

Does anybody see an update on the phone? I dont have it...

nix ( 2014-12-18 18:21:50 +0200 )edit

Can't wait to get hands on the newest update <3

Also, I had a problem with 1410 SDK: QTCreator not responding for 30s then working 5s, repeat. Running win7 64bit Intel e8500 ati hd4890. Hoping it will fix itself in next SDK :)

Mauris ( 2014-12-18 18:28:24 +0200 )edit
4

cemoi71, if you are running 1.0.8.21, just proceed to update your device without additional steps. Our servers auto-scale to handle the load to avoid saturation. We are rolling out the release in batches, first to first ones, next to update9 opt-in users and finally to rest of our users. During today, all should be able to update their devices.

bijjal ( 2014-12-18 18:28:49 +0200 )edit
1

Thanks the team for this xMass present. Will wait for the update itself

SergeiStPete ( 2014-12-18 18:29:37 +0200 )edit
14

"The first one" Updating... Reboot and then nothing. Only black... I did have Uitukka.

Recovery, option 5.. not helping... so, reset my phone.

Make backup!

Makeclick ( 2014-12-18 18:32:24 +0200 )edit
2

Nice one ! Thanks Jolla Team !

runvgn ( 2014-12-18 18:34:14 +0200 )edit
1

Still now fix for calendar reminder sync issue, for example in case of google calendar? When calendar events are synced from google, reminders are not synced. And when you manually set reminder to Jolla for some calendar event synced from google, that reminder is overriden(set to none) in some point when data is synced from google again.

prinne ( 2014-12-18 18:35:27 +0200 )edit
26

This update also contains GStreamer 1.4 libraries with basic support for playing back only local audio files.

Perhaps interested developers could start experimenting with it. Support for more formats and camera will be added later on as development progress advances.

MSameer ( 2014-12-18 18:40:32 +0200 )edit
3

At the first boot on the new update the PIN dialog didn't work. Phone didn't react to any presses on the screen. I waited couple of minutes, but no reactions. I powered off the phone with the power key. At the second try after maybe 30 seconds the PIN dialog started to work and I could start to use the phone. The phone was quite warm during the first and the second boot. BTW I skipped the update 9.

penpen ( 2014-12-18 18:48:32 +0200 )edit
1

thanks a lot bijjal for your answer

cemoi71 ( 2014-12-18 18:54:29 +0200 )edit
1

not showing up here in India ? When will it be available ?

Vivek ( 2014-12-18 19:01:04 +0200 )edit
2

opus included?

ApB ( 2014-12-18 19:01:06 +0200 )edit
51

Just to give one positive report: I updated from Uitukka and had absolutely no trouble. What an awesome gift for the holidays! Thank you, sailors!

jkkoski ( 2014-12-18 19:01:17 +0200 )edit

Update installed, phone now bricked and won't boot.

Any suggestions?

rated ( 2014-12-18 19:01:27 +0200 )edit

give it time

r0kk3rz ( 2014-12-18 19:03:38 +0200 )edit
3

Thanks a bunch for this update!

beidl ( 2014-12-18 19:03:40 +0200 )edit

Not available here in switzerland in this minutes :(

I have also try to delete the os-info file.

I see that in the System Information in the setting app the version number is: unknown version, is that bad?

heubergen ( 2014-12-18 19:04:22 +0200 )edit

It is staged release. It might take some time to show up.

penpen ( 2014-12-18 19:04:33 +0200 )edit
5

FirstOnes first, then all of you. Be patient.

iekku ( 2014-12-18 19:09:33 +0200 )edit

Can not confirm. I installed the update 1 hour ago. (I'm from Switzerland)

alex25 ( 2014-12-18 19:10:33 +0200 )edit
2

This update is for all users, not only opt-in. It might take some time until you are able to download update, thank you for your patience.

iekku ( 2014-12-18 19:11:00 +0200 )edit

then I think, just I have not yet reached the update :(

heubergen ( 2014-12-18 19:13:21 +0200 )edit

@bijjal just to avoid the chaos, maybe you had announced the update one day for one class. I mean day 1(today) just for the first one, day 2 update 9 users added, then day 3 all users. I hope you don't have so much device brick announcements... for my part i think i wait a little bit to observe how the update progress in the community... that a quite huge update this time. I wonder that it goes out for all, with less tests (it's not a critic, just a remark)

cemoi71 ( 2014-12-18 19:15:52 +0200 )edit
1

Update worked, but now I can neither call nor send SMS. Germany

Blizzz ( 2014-12-18 19:29:17 +0200 )edit
3

I'm a bit worried about the name, Lake of dangers... We'll see how much dangers there is :)

TemeV ( 2014-12-18 19:34:21 +0200 )edit
6

This is android support updating. If you have a lot of apks installed, then it will take several minutes.

xfade ( 2014-12-18 19:36:11 +0200 )edit
4

Not yet. If you want it then either submit libopus to mer and I will enable the plugin or wait until I have enough time to do it :)

MSameer ( 2014-12-18 19:37:12 +0200 )edit
1

@heubergen Now why did you delete that file? You should not try to break your own system, that is a bad thing to do!

xfade ( 2014-12-18 19:38:24 +0200 )edit

I have no idea how to push something to mer. I'll wait. :)

ApB ( 2014-12-18 19:39:10 +0200 )edit
4

Same here, works like a charm.

null ( 2014-12-18 19:45:46 +0200 )edit

Almost the same here. Updating seemed to work (enough space was there too). But then when rebooting my first one got stuck at bootspash logo. I had hoped for a better christmas present than this :-(

bAvatar ( 2014-12-18 19:46:39 +0200 )edit
1

Is there a way to enforce the update manually? I'm struggling with this issue and want see, if it is fixed now: https://together.jolla.com/question/44155/e-mail-syncs-once-and-then-fails/

hoschi ( 2014-12-18 19:47:54 +0200 )edit
6

<3 "Opening an app now shows a busy indicator animation on the app cover instead of the static "Loading" label" solves exactly ma Request!!! https://together.jolla.com/question/52003/feature-request-enhance-loading-app-cover-indication/ <3<3<3

mosen ( 2014-12-18 19:49:41 +0200 )edit

First One and still no update available.

Still nothing available for my 1.0.8 First One.

1.1 other phone is downloading now

meowmeow ( 2014-12-18 19:51:59 +0200 )edit
3

Thank you for this update, just in time before Christmas :-D Good work Jolla team !

ced117 ( 2014-12-18 19:56:06 +0200 )edit
2

While I wait for the update to be available for my phone (not a First One!), I would like to thank Jolla for underpromising and overdelivering this time. This is good practice, keep it up! ;-)

IZ1IVA ( 2014-12-18 19:56:06 +0200 )edit
3

Thank you, great surprise! Update went smooth, everything fine. Me happy.

ossi1967 ( 2014-12-18 20:08:05 +0200 )edit
1

RAM usage picture Interesting change in RAM usage after the update.

Giacomo Di Giacomo ( 2014-12-18 20:12:08 +0200 )edit
1

Cant wait for more robust codec support.

vasavr ( 2014-12-18 20:15:01 +0200 )edit
1

Ok, same here, i did have small pligs of Sailfish logo and then red led and then it's gone.. only red light and turn off everytime i try to boot.. Jolla should have better backup/restore app :/

Makeclick ( 2014-12-18 20:15:55 +0200 )edit
1

Same here, but I can still access the phone via ssh, so system is up and running but the UI won't come up! (was on 1.1.0.39 Uitukka)

Cermit ( 2014-12-18 20:18:23 +0200 )edit
14

Update completed successfully, and my Jolla works like a charm! Its like the OOM issues are just a bad memory now. Good job devs!

figucher ( 2014-12-18 20:29:22 +0200 )edit
1

Yes, Working good Thank you.

juja ( 2014-12-18 20:34:21 +0200 )edit
1

Exactly the same, no problems after 10 minutes of usage. Thanks, Jolla!

SergeiStPete ( 2014-12-18 20:35:15 +0200 )edit
1

me too! great stuff :)

gsalone ( 2014-12-18 20:49:49 +0200 )edit
7

I have the 1.0.8.21 "Tahkalampi" version, and I can't see the new update, what I need to do?

Marsselo ( 2014-12-18 20:57:38 +0200 )edit
1

here in spain no update yet. i'll have to wait some days till the update notification brings up :(

c3lgad1s ( 2014-12-18 20:59:08 +0200 )edit
2

No problems here. Coming from Uitukka.

Manatus ( 2014-12-18 21:05:18 +0200 )edit

Not available in Poland.

Jaro070 ( 2014-12-18 21:05:29 +0200 )edit

Works like charm. Coming from update 9

Fellfrosch ( 2014-12-18 21:12:07 +0200 )edit

Still waiting for the update, one of the First Ones. :(

Evvk ( 2014-12-18 21:36:45 +0200 )edit

not good. downloaded update, started update process but the progress bar shows zero percent progress. been like this for the past 5 minutes! phone is plugged into the charger. :( :( :(

droll ( 2014-12-18 21:49:23 +0200 )edit

+1, No Update available from france :(

sfeuga ( 2014-12-18 21:50:21 +0200 )edit
1

One more here. Updated from Uitukka. Mine said something like "Could not be updated... click ok to reboot". Now screen remains black after boot logo.

datakurre ( 2014-12-18 21:50:25 +0200 )edit

because in the field "Sailfish OS" (under settings => system => product information) stand "Unknow version"

heubergen ( 2014-12-18 21:51:37 +0200 )edit

my first factory reset - after 9 months of usage with only minor/solvable problems

rudi ( 2014-12-18 21:58:00 +0200 )edit
3

wasn't looking at the phone but it vibrated and rebooted. I can see the jolla logo now. phew! phone just rebooted and is up and running. aaaaaaaaah

droll ( 2014-12-18 21:58:45 +0200 )edit
3

It's almost as if your brain deleted your memories of the out of memory problem because you ran out of memory or something

v2px ( 2014-12-18 22:06:26 +0200 )edit
1

Looks like I'll be joining the club :)

Updating from Uitukka, and I sure have enough space on my drive... Downloading was pretty quick, but when it started updating the progress bar hung about 65% thru... and has stood still there for the last 10 minutes :(

I probably have to reset the device and start from scratch, bummer...

juiceme ( 2014-12-18 22:11:22 +0200 )edit

Same here, no Uitukka, just before that one 1.0.8 or something like that. Option 5 didn't helped. Full battery and enough storage space free.

Edit: A reset did the job.

BonoNL ( 2014-12-18 22:15:28 +0200 )edit
1

Update working nicely, also seems to be more responsive with many open apps compared to Uitukka. Thanks Jolla!

seiichiro0185 ( 2014-12-18 22:20:16 +0200 )edit
3

thats alot in one sweet update! thank you so much for your much appreciated work, also for listening for us and completing our wishes! Have a merry xmas everyone!

FOMBE ( 2014-12-18 22:25:04 +0200 )edit
1

Great job guys... Kiitos guys! Hyvää Joulua!!!

gordon_pcb_designer ( 2014-12-18 22:37:25 +0200 )edit

Update avaliable in Spain, at least for "the first one TOH" Updating in a few minutes.

niuran ( 2014-12-18 22:39:25 +0200 )edit
1

GERMANY - update from 1.0.8.19 to 1.1.1.26 works fine :-)

THANKS jolla

peter-berlin ( 2014-12-18 23:03:13 +0200 )edit
1

Update worked smoothly, zero issues~

Mirv ( 2014-12-18 23:05:28 +0200 )edit

Same here. Quite frustrating after struggling with Uitukka.

taph ( 2014-12-18 23:27:22 +0200 )edit
1

Updated without trouble ,at least at first view.

niuran ( 2014-12-18 23:28:04 +0200 )edit

Same for me in Russia.

Odorobo ( 2014-12-18 23:29:11 +0200 )edit

have a look at the opening post. releasing is stopped, due to a critical bug.

mettska ( 2014-12-18 23:36:35 +0200 )edit
1

After my problems... It feels very nice! Love it!

Makeclick ( 2014-12-18 23:36:39 +0200 )edit

the updates come usually step-by-step to the users. so under normal conditions you would have to train your patience for a few hours ;)

mettska ( 2014-12-18 23:39:00 +0200 )edit

How can I reset my phone in current state?

taph ( 2014-12-18 23:44:59 +0200 )edit

Please try this on the command line (enable developer mode): devel-su; pkcon install zypper; zypper in -f droid-system-sbj sbj-platform-images

tigeli ( 2014-12-18 23:48:12 +0200 )edit

too late, works again meanwhile .

what i tried was rebooting , re-inserting SIM card, clicking on the configure button in the SIM configuration app. Without any visible effect . Later i suddenly got on SMS from my carrier saying that my phone was configured for SMS, internet and stuff (Internet was always functional actually ). From that on Calls and SMS started to work again .

Blizzz ( 2014-12-18 23:56:46 +0200 )edit
2

Same here (blank screen) happened to me when updating to Uitukka - however, if you had wi-fi and SSH enabled beforehand, you can SSH into the device and fix it with zypper ref && zypper dup.

This time, it said "Could not be updated..." and there was a blank screen again, but reboot fixed it to the point that I could open the terminal and use zypper ref && zypper dup to finish the upgrade (it said that I have 1.1.1.26 in the Settings, but it wasn't true).

nodevel ( 2014-12-19 00:08:05 +0200 )edit
3

Thanks guys for having the cojones to eventually wreck your end-of-year holidays! I hope you can avoid any storms and enjoy calm sea! Update from opt-in-9 went smooth as silk.

the_mgt ( 2014-12-19 00:51:59 +0200 )edit
2

killed the system, shows bootscreen, white led, and than screen just went blank.
not a great user experience at all.

Edit: it seems it boots but showing nothing on the display, logging into jolla with ssh works, and shows old Version:

SailfishOS 1.0.8.21 (Tahkalampi) (armv7hl)

kelvan ( 2014-12-19 00:52:48 +0200 )edit

I have the white TOH an no update message how did you do????

c3lgad1s ( 2014-12-19 00:59:53 +0200 )edit
1

will try the zypper thing after rsync finished syncing jolla /home directory :)
thanks for sharing your fix, hope it will work for me too

edit: upgrade in progress from cli (ssh/screen)
zypper show no space on device for multiple packages, the first few worked after retry, because there are over 2GB free space on /
also checked btrfs filesystem df

I skipped gst-plugins-good, but I think jolla-sessions-qt5 is quite mandatory, but impossible to upgrade

kelvan ( 2014-12-19 01:55:14 +0200 )edit
1

Installed and running OK for some 6 hours. Will not test lock code until hot fix for this feature has been released. One of the benefits of road testing it on the more technical first users:)

richardski ( 2014-12-19 01:58:13 +0200 )edit

So I tried updating last night from 1.0.7.16 as I had downgraded from 1.0.8. Phone downloaded the update, installed, rebooted with progress bar then rebooted again and loaded up fine. Check the phone and it still says there is an update... Phone is still 1.0.7.16 .

suppose Im lucky the phone is not bricked, but I don't use screen lock anyway :p most people can't figure out how to swipe unlock it

So I try to download again and it keeps stopping the download, I have about 5 gig free ??

madcheeze ( 2014-12-19 02:57:20 +0200 )edit

tried updating again now i have the blank screen issue other people are reporting... damn should have waited.. now how to recover...

madcheeze ( 2014-12-19 04:14:21 +0200 )edit

i have this problem too, can ssh to it. just bank screen recovery tool now ?

madcheeze ( 2014-12-19 04:41:51 +0200 )edit

Got the update notificaton during the day at work but waited some 6 more hours to get home to update. Battery was at 37 and updated without connecting the charger, no problem, update went smoothly with 19% battery life after . :)

paperboy ( 2014-12-19 05:04:02 +0200 )edit
1

Any ETA on the Re-release of this update !?!

sirzero1997 ( 2014-12-19 06:20:23 +0200 )edit
1

Sweet transition for me too from opt-in Uitukka to Vaarainjärvi, no problems, and merry Xmas to all.;)

foss4ever ( 2014-12-19 07:37:16 +0200 )edit

same here :(

tvicol ( 2014-12-19 09:01:22 +0200 )edit
1

Upgrade went very smoothly, downloaded update over 4G. No issues whatsoever. Was running update 9. Best christmas present this year :-)

ingi ( 2014-12-19 09:01:46 +0200 )edit

yesterday ;-)

drummer12 ( 2014-12-19 09:06:21 +0200 )edit

@njeiseck I can use Spotify for Android after the update. Maybe I am lucky?

nick75 ( 2014-12-19 09:28:30 +0200 )edit

I had one problem with mobile data connection, otherwise upgrade went just fine: After updating, mobile data connection did not work, until I enabled roaming. After that, mobile data connection worked just fine, even after I disabled roaming again (it was disabled before updating) Location Finland, operator Saunalahti (4G)

jtkukkonen ( 2014-12-19 09:56:41 +0200 )edit
1

Update went smooth with me. I sneaked in just minutes before it was put on hold again...Won't use alphanumeric lock anyway, so I guess I don't care. FTM everything is bliss!

lispy ( 2014-12-19 09:59:18 +0200 )edit

Same here, also from 1.0.8.21

NuklearFart ( 2014-12-19 10:11:00 +0200 )edit

Unfortunately I can see still no update here in Germany. Running my Jolla 1.0.8.21 Tahkalampi. Tried to update all the possibilities. I wait and keep, maybe not the worst idea. We have here a rough seas?

rosapold ( 2014-12-19 10:17:52 +0200 )edit
1

A Big Thank You :)

MarKaz ( 2014-12-19 10:35:34 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:45:25 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:45:28 +0200 )edit
1

Updated from 1.0.8.39 to 1.1.1.26... working fine :)

Thanks Sailors!!

Gabriel ( 2014-12-19 10:47:21 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:47:28 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:47:35 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:47:48 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:48:09 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:48:30 +0200 )edit

Please convert to comment, this is not an answer.

Jarno ( 2014-12-19 10:48:37 +0200 )edit
1

@paperboy nice for you, maybe your phone has not so much activity that the power don'T go so fast on the lower-limit. For other people it is anyway recommended to put the charger on charge. Maybe they couldn't have so much luck than you... ;-)

cemoi71 ( 2014-12-19 11:01:11 +0200 )edit

Can someone tell if Meerun is functional on this new release? I didn't do the opt-in upgrade to 1.1.0.38 because I have been told that Meerun was not working on it. Is it fixed now? Can I go to 1.1.1.26 and have my meerung working well?

Thank you for this christmas gift by the way ;)

lunatix ( 2014-12-19 11:07:27 +0200 )edit

how can I convert answer to comment ? "repost as a question comment" or "repost as a comment under the older answer" ? Or should I delete this answer totally and add a new comment ? I just thought that maybe someone else has a same problem with mobile data connection after upgrading, and my experience would help

jtkukkonen ( 2014-12-19 11:26:48 +0200 )edit

Probably not. It was not working on update9 either. Will need fixing. ... Just tried. Nope, not working.

Jarno ( 2014-12-19 11:39:42 +0200 )edit

Wow that was informative

sirzero1997 ( 2014-12-19 12:06:51 +0200 )edit

Same here, not working ! bad news for me too.

Cl2ment ( 2014-12-19 12:30:01 +0200 )edit

Maybe in the relaunch we can update too! I hope so!

Marsselo ( 2014-12-19 12:57:37 +0200 )edit
1

@taph If you can't do anything else than reset. With Linux it is very easy, but with windows.. have to install more drivers and thinks. Scroll down at

https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/

Makeclick ( 2014-12-19 13:47:10 +0200 )edit

@madcheeze it would probably be easier to debug this on IRC?

iamer ( 2014-12-19 14:22:20 +0200 )edit

@bijjal is it possible that because of the reverting job of apha-numeric issue, that the update-phasis was more or less shortly suspended?

cemoi71 ( 2014-12-19 15:05:15 +0200 )edit
1

It is put on hold currently, see the modified title.

hoschi ( 2014-12-19 15:22:39 +0200 )edit

Please, could someone tell the most convenient translation of "Vaarainjärvi" into english?

myau ( 2014-12-19 15:24:00 +0200 )edit
3

there is no translation because it's as all updates, the name of a lake in Finnland.

drummer12 ( 2014-12-19 15:33:03 +0200 )edit

It is a name of a place ("järvi" in finnish = lake)

abanai ( 2014-12-19 15:34:49 +0200 )edit
5

It is the name of a lake in Finland, specifically this lake. There is no translation because it is a name. If you want a forced translation, it would be "Lake of many vaaras" or "Lake of many small mountains".

Nicd ( 2014-12-19 15:35:27 +0200 )edit

ваараньярви

virgi26 ( 2014-12-19 15:35:34 +0200 )edit
1

This one: https://www.google.com/maps/@64.5545072,24.6080995,18z

Okw ( 2014-12-19 15:40:58 +0200 )edit
2

Raspberrylake

Vaarain is Vadelma in Oulu dialect (afaik)

kimmoli ( 2014-12-19 15:56:21 +0200 )edit

cemoi71, yes indeed.

bijjal ( 2014-12-19 16:09:23 +0200 )edit
1

I've heard many people have a problem with this update causing the screen go blank, including me. I did a factory reset and fixed it but this needs to be investigated.

Toxip ( 2014-12-19 16:17:59 +0200 )edit

Not sure if this is related to "Updates notification update mechanism which fixes the display issues in events view when there are notifications from multiple apps in succession", but I'm not getting any notifications from Android apps to my notifications view. This is new to me, worked in update9. Anyone else having this too? Could be I'm missing some nice feature, could be a bug.

Jarno ( 2014-12-19 16:41:39 +0200 )edit
1

@bijjal could it be judicious if someone make an other threads which informs all together in which phase are servers configured for the update? if it still for the 1st-one or 1st-one & update-9 or for all together available... personally i'll find not bad for an info. a lot's of people seems to jerk like hamsters, and have no idea where is the focus... :-°

cemoi71 ( 2014-12-19 16:51:58 +0200 )edit
1

In my case it was "no space left on device"
Be aware that even btrfs fi df shows completly wrong free space
I had 2GB free shown, but in reality it was already full

kelvan ( 2014-12-19 17:41:25 +0200 )edit

i am still waiting for the update but i give here my remark about what i observe on my phone the phone on option display 8,2gb from 13,7gb, but the "memory" native app display 7,68gb from 13,75gb. strange... i have sailfish 1.0.8.21... seems to be in general a memory inconsistency... As bijjal said if we cannot trust the system, we should really make place on the memory. make a backup on the sdcard and erase all videos and pics and unused data. to be sure...,

cemoi71 ( 2014-12-19 18:02:11 +0200 )edit

@bijjal great! well done to inform all how the update is segmented in user category. fine! the way is clear... i'll enjoy your post for the "last green mile" on monday. ;-)

cemoi71 ( 2014-12-19 18:08:37 +0200 )edit
1

Thank you, I received notice that v 1.1.1.27 (hotfix) is ready for installation. Will do so immediately, but first things first, a backup!.

WilliePre ( 2014-12-19 18:20:41 +0200 )edit

Yesterday I installed 1.1.1.26. Today I installed 1.1.1.27. Everything is fine so far. Thanks for the release!

Plnt ( 2014-12-19 18:27:19 +0200 )edit
1

1.1.1.27 now installed and all seem to be running OK so far. Will do some more testing:)

richardski ( 2014-12-19 18:27:43 +0200 )edit
1

2k+ images used in a game and stored within /data/data/ will still be shown in gallery T_T

@Bowmore Are you sure it is /data/data ? did you try adding a .nomedia file in that images directory to instruct tracker to exclude it from indexing ? This is how it's done in android as well.

Have you posted a separate thread for this issue ? Would be easier to discuss there.

iamer ( 2014-12-19 18:43:04 +0200 )edit
1

v1.1.1.27 installed and running smoothly. All my installed apps are working as advertised.

WilliePre ( 2014-12-19 18:56:11 +0200 )edit

"the fist one" and hotfix. everything went alright and i am very happy. Merry Christmas!!

Makeclick ( 2014-12-19 18:58:39 +0200 )edit

Not Glance yet in this U10?

gordon_pcb_designer ( 2014-12-19 19:04:52 +0200 )edit
1

When we will have the Saimaa Lake Update, it will be awesome !

Hecraps ( 2014-12-19 19:21:49 +0200 )edit

"If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories"

Does it mean that running 1.0.8.21 (Tahkalampi) and using OpenRepos requires disabling all repositories?

Mr.Pancake ( 2014-12-19 19:30:06 +0200 )edit
1

No, it's for now only available for "first ones". From monday for all...

torcida ( 2014-12-19 19:43:36 +0200 )edit
1

btrfs fi show should show the correct used used space on the device. btrfs fi df / shows only the root filesystem without subvolumes (like backups) and so on.

leszek ( 2014-12-19 19:59:17 +0200 )edit

Yeah, but neither yesterday nor today's update was available for some First Ones.

meowmeow ( 2014-12-19 20:04:27 +0200 )edit

thanks for the update .. work's smooth :)..

Ghost ( 2014-12-19 20:07:56 +0200 )edit
1

@Mr.Pancake: No, if you're on 1.0.8.21 there should be no problem and you don't have to disable...

torcida ( 2014-12-19 20:13:34 +0200 )edit

yes first one and no updates so far ....

mvdm ( 2014-12-19 20:23:18 +0200 )edit
6

Lifehack for those who really can't wait and who didn't opted-in for update 9 (such as me). Just sign for the update 9 by sending an email to update9-opt-in@jolla.com from your jolla account email and you'll get the update 10 right now. Enjoy!

deseven ( 2014-12-19 22:27:26 +0200 )edit
1

Thanks for the Yuletide gift! Brings some holiday rest and peace to the memory problems with the opt-in version. Happy Sailing!

mikael ( 2014-12-20 04:15:26 +0200 )edit
1

update seems to have worked. And WOW! what an improvement in the start up time of apps! Especially Android apps like Whatsapp and Telegram seem to load really fast. Thanks and enjoy the holidays ...

bilgy_no1 ( 2014-12-20 04:26:42 +0200 )edit

Doesn't work either.

meowmeow ( 2014-12-20 04:49:21 +0200 )edit

idem first one and no update available, even after manual check. Anything special to do?

slecorne ( 2014-12-20 11:54:14 +0200 )edit

openrepos repositories should be disabled before trying the update

my update from 1.1.0.39 to 1.1.1.26 ended with a message like 'update could not be installed, press ok to reboot'
resulting in a mixup of versions, at the end the phone didn't boot anymore. after a factory reset, update to 1.1.1.26, reinstalling all apps, I tried to update to 1.1.1.27 several times - everytime ending with the same message as above

after disabling the openrepos repositories as dr_gogeta86 wrote, the update went without problems

rudi ( 2014-12-20 14:24:12 +0200 )edit

Confirmation needed - There are other possibilities for an update to not install correctly, like mem allocation in btrfs. How much of free mem you had, and what does this command return in your terminal? btrfs fi show?

simo ( 2014-12-20 15:18:34 +0200 )edit

Label: 'sailfish' uuid: 0f8a2490-53ed-4ff6-ba34-b81df3430387
Total devices 1 FS bytes used 3.06GiB
devid 1 size 13.75GiB used 12.75GiB path /dev/mmcblk0p28

rudi ( 2014-12-20 15:35:52 +0200 )edit

@rudi could you help us to reproduce the issue? What does "reinstall all apps" consists?

tigeli ( 2014-12-20 15:52:25 +0200 )edit

@rudi Also which applications did you have installed?

tigeli ( 2014-12-20 16:17:12 +0200 )edit

@tigeli

I'm not that familiar with SailfishOS, so I hope you have a command for me to retrieve this information via terminal - should be easier

found it: /home/nemo/.config/lipstick/applications.menu
I would prefer to mail it to you - do you have a mail address for me?

rudi ( 2014-12-20 16:32:15 +0200 )edit

@rudi Your btrfs shows only 1GB of free allocation space - it's possible that more is needed for a successful system update, so I'd suggest balancing. Instructed here: https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/

This might or might not be the reason for an unsuccessful system update, so a confirmation is still needed for that

simo ( 2014-12-20 17:42:15 +0200 )edit

@simo - ok
but the problem also occured while updating from 1.1.1.26 to 1.1.1.27 - patchsize 1,9MB

rudi ( 2014-12-20 17:50:25 +0200 )edit

So you first managed to update to 1.1.1.26 without disabling OpenRepos?

simo ( 2014-12-20 17:53:08 +0200 )edit

@simo - no
i tried to update with enabled repositories -> crash as decribed above - phone didn't boot any longer
factory reset - update to 1.1.1.26 without anything else installed
installation of apps
update 1.1.1.26 to 1.1.1.27 failed several time - same message as above
repositories disabled, nothing else touched/done -> update was successful

rudi ( 2014-12-20 18:00:13 +0200 )edit

@rudi you can send that applications.menu and "rpm.txt" which you can generate with following command "rpm -qa >rpm.txt" to tigeli@jolla.com, thanks.

tigeli ( 2014-12-20 19:56:16 +0200 )edit

@rudi I installed the apps you had installed in one of my devices with sailfish os 1.1.1.26 and then I successfully upgraded to 1.1.1.27 without disabling openrepos repositories.

To debug the situation further would need to get the logs from the device but unfortunately those logs are not persistant over reboots on the sales-devices.

tigeli ( 2014-12-20 22:50:33 +0200 )edit
1

Thank you sailors, that's a very nice update! :) I really like the new hierarchy indicator.

Nicolas ( 2014-12-21 18:10:08 +0200 )edit
1

Aw yes, such a nice christmas present! The new browser engine is so fresh and so clean! Many thanks to Finland!

laubblaeser ( 2014-12-22 03:11:08 +0200 )edit
1

Update 1.1.1.27 is really great !!! A big THANK YOU, Jolla !

tvicol ( 2014-12-22 11:34:47 +0200 )edit
1

Now all i am waiting is bijjal to write the usual "whats next" post :) (crosses fingers for keyboards and localization)

ApB ( 2014-12-22 11:56:38 +0200 )edit

I am a "First One" with opt-in update9, but I never got it and I do not get it now. What's wrong.

jolladiho ( 2014-12-22 12:08:55 +0200 )edit
1

Update in download - now ,

Thanks

and happy christmas to all of you ;)))

mvdm ( 2014-12-22 12:13:41 +0200 )edit
1

Did the up, it worked, but now patchmanager does not work and everything seems to be totally slow. When I open settings or messages now it loads for a while. before the up everything was a bit smoother in my opinion. There might be something gone wrong, it downloaded really fast which I was not expecting but it says I have the new update. I have loading animation on the covers and the indicator of pages is more on the left which looks awful to me :( I'll give it a chance now.

NuklearFart ( 2014-12-22 12:55:17 +0200 )edit

@simo it seems to me, that the factory reset is the last option. I'll think about it.

jolladiho ( 2014-12-22 12:55:22 +0200 )edit
1

@NuklearFart Give the phone some time to settle down - this is a huge update. For patchmanager issues, maybe refer to talk.maemo.org - things might have changed in the file structure, and patches might require some fixes for that

@jolladiho Hope it gets solved out without that

simo ( 2014-12-22 12:57:14 +0200 )edit
1

Thx @simo :) Well, it is kind of crazy, I disabled patchmanager from terminal since it is openrepos. The patch from up 7 to 8 did not change anything from the settings done now. Now I deinstalled patchmanager, because it does not work, but now I have the problem that I can not reinstall it, it says there is a problem with the installation :( Maybe I'll ask at talk.meamo.org :)

NuklearFart ( 2014-12-22 13:09:02 +0200 )edit
1

Left the phone to update during lunch, almost smooth sailing. First when I unlocked the phone it wanted me to rearrange/delete the apps and would not leave the app screen. Rebooted and everything seems to be in order so far. So thanks for this update - need to take a closer look after work. :P

And Happy Holidays to you all! :)

raketti ( 2014-12-22 13:23:14 +0200 )edit
1

Update worked smooth! Thanks to all at Jolla for this!

Stephan ( 2014-12-22 13:41:43 +0200 )edit

Is it possible to update new OS as fresh install. Like Factory Reset, but with this latest OS ?

prinne ( 2014-12-22 14:11:24 +0200 )edit
1

it's greate but I'm still waiting for panorama option in camera cause android panorama apps are terrible. I had an opporunity to use the panorama

Kristjan ( 2014-12-22 14:17:21 +0200 )edit

@prinne of course it is, but I do not recommend you to do so! :)

(all you need to do is take a btrfs snapshot of the current system and set that as baseline...)

juiceme ( 2014-12-22 14:17:57 +0200 )edit

I received an email confirmation that Vaarainjärvi (1.1.1.27) is headed my way (Yay!). At least the Finnish email talks about the Alphanumeric lock code, which actually won't be in the release I'm assuming!

cjp ( 2014-12-22 14:41:00 +0200 )edit
2

Hmmm... My phone restarted when white line was in the middle... After SilfishOS logo I got just black screen :( Option 5 from recovery didn't help and I needed to use option 1 (factory reset)... Now is long way for me to restore all my stuff :( P.S. update was from 1.0.8.21

Schturman ( 2014-12-22 19:24:04 +0200 )edit

had the same issue and am rewarded with a superfresh installation as you will be!! :D Keep your head up schturmann!

mosen ( 2014-12-22 19:40:50 +0200 )edit

@bijjal i had 1.0.8.21 is it possible that consider the version that we have, the update could have different size? For my case i have read something like 265MB (if i've good remembered it..)

cemoi71 ( 2014-12-22 20:11:49 +0200 )edit
2

wow . I'm Surprise that I'm not the only who got the black screen bug :) got a fresh reset too :(

sirzero1997 ( 2014-12-22 20:41:56 +0200 )edit
1

all went well with me. one question, new overlays for maps? i couldnt find that...

AL13N ( 2014-12-23 00:56:11 +0200 )edit
1

@AL13N me neither

kelvan ( 2014-12-23 01:10:52 +0200 )edit
1

AL13N, I couldn't find any new overlays or any other change in the maps either. Tried reinstalling it but it made no difference.

HarlequinGreen ( 2014-12-23 01:12:50 +0200 )edit
1

which version of the maps do you got installed?

drummer12 ( 2014-12-23 01:35:12 +0200 )edit
1

I've got 1.0.25.1 of Maps, which Jolla Store also lists as the latest version released in July 2014.

HarlequinGreen ( 2014-12-23 01:44:46 +0200 )edit
1

All good so far. "Sometimes Messages and Phone app show black active covers." - This happens quite often to me. Just reporting :-)

anandrkris ( 2014-12-23 05:40:29 +0200 )edit
1

@HarlequinGreen You need to press somewhere in the map area to get the upper drop down menu open, then you'll see the overlay options in the bottom of the screen. Hopefully this link works (corporate rules, imgur is blocked so I had to just copy it from my mobile). link text

raketti ( 2014-12-23 08:35:24 +0200 )edit
1
1

Hm, i guess ill wait with updating then :D any of you used harbour? forgot to disable the repos?

mlatu ( 2014-12-23 09:56:27 +0200 )edit
1

@mlatu I have Warehouse installed and as a precaution I disabled the repos (which was easy because I only had two enabled). EDIT: And the update went smoothly.

raketti ( 2014-12-23 10:25:09 +0200 )edit

ok, i found out... apparently, maps was not updated, and it was not visible in the updates either...

I've never did "update all" so maybe that's the reason.

for some reason it seems some apps are not listed in "my apps" and thus aren't shown in the updates.

i've updated maps, so i assume it now works...

AL13N ( 2014-12-23 12:01:23 +0200 )edit
1
2

yay, my update worked flawless

mlatu ( 2014-12-23 19:07:56 +0200 )edit
2

After update Os seems to be very slow. A tap to screen and sometimes it takes 2 seconds before anything happens. Time to time I have announce that "app is not responding. wait / close" , but after a couple seconds app starts to respond again.

HTOP shows that CPU core 2 load jumps to 100% in every 2-3 seconds. No specific PID takes a lot of CPU load. One process holds ~25% all the time. Others below that, is that normal?

prinne ( 2014-12-29 09:53:58 +0200 )edit
1

@prinne I've noticed the same behaviour. And just checked with Lighthouse, and CPU2 jumps over 100% (which is nice, but I'm guessing it's not going super sayan). So there seems to be something fishy, hopefully it's just a simple scaling error when reading the processor state. Best reading so far has been 3300%. And when the figures showed CPU1: 4% and CPU2: 400% the average was 10%. Otherwise the phone is responsive, at least I haven't noticed any disturbing lag.

raketti ( 2014-12-29 10:25:46 +0200 )edit
1

@prinne Just keep calm, the phone needs some time to update all the parts of the OS especially the android support. Maybe turning off the phone, wait a few minutes ans restarting could help. Read about that in another thread.

drummer12 ( 2014-12-29 11:03:59 +0200 )edit

@prinne just wondering which process? "One process holds ~25% all the time"

kimmoli ( 2014-12-29 11:12:21 +0200 )edit

@dummer12 : it has been now a week and several boots

@kimmoli: sorry, that 25% was htop itself :) Now I have looked TOP command output for ~5 minutes and noticed that two times there was kswapd0 with over 90% of CPU load , about half a minute at a time.

prinne ( 2014-12-29 11:52:02 +0200 )edit

@prinne soryy, thought you updated today ;-) kswapd= is the process swaping memory (ZRAM) I figured out the same, sometimes it uses much CPU. Do you have enough space on your Jolla? Maybe you are experiencing the same as this thread

drummer12 ( 2014-12-29 11:56:37 +0200 )edit

I had faced the same issue I did factory reset and then update to 10. But when restarted it was showing black screen after Jolla Logo. I had run the recovery process. But before recovery read all recovery related posts and recovery doc by jolla.

Vivek ( 2014-12-29 12:06:27 +0200 )edit

@drummer12 : I followed instructions from thread you provided. Now it seems that everything is working fine !! Thanks !

prinne ( 2014-12-30 09:36:01 +0200 )edit

Great to hear! Sail ahead ;)

drummer12 ( 2014-12-31 14:45:37 +0200 )edit

Some bugs appeared in update 1.1.1.27. First, I get black covers https://together.jolla.com/question/2893/bug-double-tap-did-not-unlock-properly/#post-id-79276 What I've noticed too was my Storm ambience who completely changed text colors after the update. In fact, it looks like Jolla has changed .ambience files format in /usr/share/ambience. Before the update, primaryColor and secondaryColor color codes where all coded on 4 bytes and after the update, primaryColor was coded 3 bytes while secondaryColor was still on 4 bytes. This will cause an incompatibility if you had a backup of older ambience from /usr/share/ambience and want to restore it on the new update. To modify the main text colors of the Storm ambience from orange to white, I changed primaryColor from #FFEBD1 to #FFFFFF and secondaryColor from #FFFFEBD1 to #FFFFFFFF. After that, you have to reboot.

baptx ( 2015-02-01 16:18:52 +0200 )edit

hmmm for my part i never had then an ambience probleme with 1.1.1.27. did you made a request to the support team? or a special threads upon it?

cemoi71 ( 2015-02-01 16:44:32 +0200 )edit

hmmm for my part i never had then an ambience probleme with 1.1.1.27. did you made a request to the support team? or a special threads upon it?

cemoi71 ( 2015-02-01 16:44:39 +0200 )edit