Ask / Submit
-1

[Jolla Phone] Problems with Sailfish 2.0.1.11 release [duplicate]

asked 2016-05-09 22:01:18 +0200

JollaHB gravatar image

My Jolla Phone got the latest Sailfish 2.0.1.11 today and I had to find out that it is the same crap as Sailfish 2.0.0.10.:

  1. I still have every few minutes the Pop-Up "Remote keyboard has been crashed" and then Jolla freezes any app that is open in the moment the Pop-Up will appear.

  2. Jolla still cannot edit Mobile SIM contacts and relocate local contacts to a Mobile SIM.

  3. All my Android Apps (include Google Play) still can't connect to the mobile Internet. On WLAN they can connect, so the failure must be OS specific for mobile connections.

  4. The earlier reported Problems still exist and haven't been fixed with this update. So please enable finally the SD-Card support! You can still not store Apps, Photos or Screenshots on it, only read things, stored by another extern device before. Sailfish 2.0.1.11 still only stores and saves on the intern phone memory and is still ignoring a installed SD-Card. Thats so a waste of memory! Please finally change this, too!

  5. The recognition of the Jolla Phone on a Windows PC using the "connect with USB"-Fuction is still a Game of pure Chance.

  6. The Android-Version is still 4.1.2 Please finally update them, too or enable a possibility to update it manually!

  7. Since Sailfish 2.0.0.10, if I'm using an Android-App, I have every few minutes the Pop-Up "Google Play Services has been crashed", too. These errors haven't been fixed in 2.0.1.11, too. So please fix these permanent errors and the other here reported Problems with Jolla finally and also the Android-Version, too.

Does anyone know a solution how I can go back to the last working version: Sailfish 1.1.9?

Else I can only put my Jolla Phone into a trashcan, since Jolla won't fix this previous reported bugs. Jolla Phone is useless in this condition.

edit retag flag offensive reopen delete

The question has been closed for the following reason "duplicate question" by misc11
close date 2016-05-09 23:11:36.078138

Comments

3

please dont post duplicates of your own thread!!! and please post each bug and feature request in its own thread!

misc11 ( 2016-05-09 23:11:26 +0200 )edit
2

Play Services? So manually installed. Well, I know it can work. But their is definitely no support for it, using Play Services is like installing Windows/WINE on Linux. Furthermore most of your stuff was never mentioned in connection to the update.

SIM Conacts? Welcome 21st century, please use VCard. It can import from SIM, the only thing that matters.

Your angry, but in my point none of bullet points is a real problem or doesn't even matter (SIM Conacts lol, What is next Infared Conact exchange?).

hoschi ( 2016-05-09 23:14:12 +0200 )edit

@hoshi Are you kidding me? There are different serious reasons for storing and editing contacts on a mobile SIM. VCards are not a solution for that. And every other mobile since the beginning of mobile communication can do that essential basic function, only Jolla can't do this. It's very uncomfortable.

JollaHB ( 2016-05-10 06:30:45 +0200 )edit

@JollaHB play services installed the way the howtos here on tjc tell you will work much likely (as long as your app does not use things not implemented in SFOS [e.g. Bluetooth LE / cromecast / miracast] or not handed over to aliendalvik). MicroG may be worth a look and may work depending on app only using implemented calls.

lpr ( 2016-05-10 13:50:25 +0200 )edit

1 Answer

Sort by » oldest newest most voted
7

answered 2016-05-09 22:13:32 +0200

Mr.Pancake gravatar image

updated 2016-05-09 22:14:41 +0200

Try resetting your phone (this will also roll your OS version back to the one stored on the device). I am saying this because I do not have any issues with keyboards, nor android app, nor services. Must be an issue caused by your current setup.

The only things I can relate to are no SIM contacts support (can not delete one as well) and poor SD card support.

You should also understand the deal with the Android version being locked. See this question for more info on this matter: https://together.jolla.com/question/132122/upgrade-qualcomm-android-drivers-to-kitkat44-level/

edit flag offensive delete publish link more

Comments

@Mr.Pancake Thanks, I'll try this.But will I still get newer Sailfish Versions as the stored one?

JollaHB ( 2016-05-10 06:33:33 +0200 )edit

@JollaHB After resetting the phone and setting up your stuff you can start updating the phone to the actual Sailfish Version it should even start automatically to search and inform you when an update is found. You will probably get 5 or 6 major updates before you arrive at the latest version. I also did it and it was helping a lot with the settings I also had sometimes strange behavior. Since the reset its better.

PatsJolla ( 2016-05-10 12:40:47 +0200 )edit

@Mr.Pancake the android-part is not correct, as it has nothing - a bit but not much - to do with drivers. The Drivers being used are able to work together with an Android 4.2 to 4.4 (up to API23 with cyanogen) NOT with 4.1.2. That aliendalvik implements 4.1.2 (API 16) is a software decision by Jolla/Myriad and not locked. The device as such could do even Bluetooth LE and openGL ES 3 not mandatory in android4.4 but is not implemented in SFOS&aliendalvik for now [Jolla limited by manpower&resources]

lpr ( 2016-05-10 14:04:28 +0200 )edit

Question tools

Follow
1 follower

Stats

Asked: 2016-05-09 22:01:18 +0200

Seen: 811 times

Last updated: May 09 '16