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

[solved] strange behaviour of my jolla phone part 1 [answered]

asked 2016-02-24 22:17:24 +0300

cemoi71 gravatar image

updated 2016-08-17 14:14:06 +0300

jiit gravatar image

Hello all

i just want to report some strange behaviour of my jolla phone with sfos 2.0.0.10.
that's in different parts, to separate each effect in each threads (don't know if one is bound to the other).

First the developer mode is blocked. When i try to activate it, it will be interrupted with the message that more or less "the market make problem, the content is not available, try to do it later" (translate from French to English).
otherwise, with this stand i can install and uninstall an app.
I tried to use the restore of register function of the utilities. that bring no changes (not worse, not better).

I made already some research, and for me the next step would be to make a rebuild with the recovery mode.

the other part that i noticed and comes in the other thread is more curious...

precisions: i never had openrepos on my device.
and don't know how i begin with fingerterm (is the 1st time i heard of it). ok got it but seems that something else block the dev mode. And i have no good tool like fingerterm for seeing what's happened. because fingerterm is active only in dev mode.
this story is like a the dog who bites his own tail...

24-02 22:20: now i got the info from jolla-store that it don't find the developer mode explicit on the whole display. after try to activate again the dev-mode.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by cemoi71
close date 2016-02-25 01:16:21.600548

Comments

Did you install Openrepos version of openssh? (If not, DON'T! If you did, see this)

objectifnul ( 2016-02-24 22:26:22 +0300 )edit

@objectifnul no i don't have openrepos. why should i not rebuild under recovery mode? how could it be bad?

cemoi71 ( 2016-02-24 22:30:59 +0300 )edit

i understand that we must be really cautious with it. but how else may i unblock the dev-mode?

cemoi71 ( 2016-02-24 22:34:15 +0300 )edit

Recovery is not bad, but it's a lot of work afterwards. It's up to you. OTOH, trying to fix the issue without recovery may be useful to investigate. An intermediate alternative is version --dup

objectifnul ( 2016-02-24 22:37:49 +0300 )edit

@objectifnul i discover know a little bit more step per step what does it mean to work on recovery mode by reading. that's confirms what you told. how may i do this command please?

cemoi71 ( 2016-02-24 22:49:51 +0300 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2016-02-25 01:08:52 +0300

cemoi71 gravatar image

updated 2016-02-25 01:14:42 +0300

Solution for my case was to install and use shellex.
And with the help of objectifnull and patience.
i gave the commands:
version --dup
then ssu s to see the that the version was "latest" and not "2.0.0.10"
And problem was fixed with ssu re 2.0.0.10
Now dev-mode works.
But i don't know why, or what have brought the system on this issue...

many thanks to @objectifnul for helping on it

edit flag offensive delete publish link more

Comments

The «release: latest» is a known bug, still under investigation AFAIK.

Note that sooner or later you will probably be 'latest-ssu-ed' again for mysterious reasons.

A good idea is to check /etc/ssu/ssu.ini from time to time and to back it up (specially the [general] section).

The interesting thing here is that you have zero app or patch from Openrepos. This reduces the field of investigation.

objectifnul ( 2016-02-25 01:31:05 +0300 )edit

Question tools

Follow
1 follower

Stats

Asked: 2016-02-24 22:17:24 +0300

Seen: 407 times

Last updated: Feb 25 '16