maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   3.3.0.x Rokua (https://talk.maemo.org/showthread.php?t=101001)

pichlo 2020-04-03 10:47

3.3.0.x Rokua
 
1 Attachment(s)
3.3.0.14 (Rokua) was released yesterday. The first impressions: nothing changed, except on my Jolla which gave me a scare of mt life with this:

Attachment 41037

Has anyone noticed anything like that?

Despite the scary icon, the phone was not in the aeroplane mode and I could make and receive calls, use mobile data etc.

Note: It only affects my Jolla. My spare Xperia X looks normal.

Markkyboy 2020-04-03 13:16

Re: 3.3.0.x Rokua
 
Didn't/hasn't occurred on my Jolla1 (3.3.0)

EDIT ~ I should add (I forgot to mention the first time) I had to reset my Jolla1 after trying to update to 3.3.0, as I was faced with a black/blank screen. So I suppose my comment is not really relevant regarding the bug you mention @pichlo.

HtheB 2020-04-03 16:09

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by pichlo (Post 1566525)
3.3.0.14 (Rokua) was released yesterday. The first impressions: nothing changed, except on my Jolla which gave me a scare of mt life with this:

Attachment 41037

Has anyone noticed anything like that?

Despite the scary icon, the phone was not in the aeroplane mode and I could make and receive calls, use mobile data etc.

Note: It only affects my Jolla. My spare Xperia X looks normal.

Probably just a bug... Why would anyone freak out about this?...

pichlo 2020-04-03 16:11

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by HtheB (Post 1566541)
Why would anyone freak out about this?...

Because one losing one's phone connection in a lockdown might be quite bad?
Because one needs the phone to receive OTP SMS to unlock the company VPN?

olympus 2020-04-03 17:01

Re: 3.3.0.x Rokua
 
So.. just updated. Alien Dalvik won't start anymore.

olympus 2020-04-03 17:11

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by olympus (Post 1566543)
So.. just updated. Alien Dalvik won't start anymore.

After updating Alien Dalvik control by Coderus to the latest version, Alien Dalvik works again.

HtheB 2020-04-03 19:53

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by pichlo (Post 1566542)
Because one losing one's phone connection in a lockdown might be quite bad?
Because one needs the phone to receive OTP SMS to unlock the company VPN?

Let me quote what you said:

Quote:

Originally Posted by pichlo (Post 1566525)
I could make and receive calls, use mobile data etc.

I don't see a problem here, GUI wise

pichlo 2020-04-03 22:43

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by HtheB (Post 1566551)
Let me quote what you said

Let me clarify in the simplest terms I could possibility muster:
  • I run an update. The phone reboots.
  • The first thing I notice is, my phone says it is in the aeroplane mode.
  • I think, "this is strange. I disable and re-enable the radio multiple times. No change
  • I try making a call but it says, "no network coverage".
  • I panic. This phone has had some problems before. It's running Sailfish, after all.
  • I turn the damn thing off for the night. Turn it on again in the morning. Still no change.
  • I turn it off again. Take the SIM out, clean it, put it back in, turn it on again. Same thing.
  • I check other family members' phones on the same network. They run Android. No problem on theirs. So it's not a network problem.
  • In a desperation, I try making a call again. This time, it works, despite the icon. Hallelujah!
  • I double check installed patches, compare them with my other phone, disable them, still no resolution.
  • I shorten the above to the absolutely bare minimum necessary to ask if someone else has seen it.
  • Some smart alec replies smugly, "what's the problem?"

Quote:

I don't see a problem here, GUI wise
You don't see a problem, "GUI wise"? What??? It's the blooming GUI that appears to be the problem!

I don't know about you - after all, you have demonstrated Jolla apologist tendencies before - but I expect things to work. I don't shrug off misbehaving indicators on my car dashboard with, "What's the problem? I can hear the engine running, the oil lamp on must surely be an insignificant GUI bug."

pichlo 2020-04-03 22:56

Re: 3.3.0.x Rokua
 
1 Attachment(s)
Talking about "insignificant GUI bugs", feast your eyes:

Attachment 41040

pichlo 2020-04-03 23:38

Re: 3.3.0.x Rokua
 
1 Attachment(s)
Two more. Looks like Browser has dome issues with rotation.

Attachment 41042

pichlo 2020-04-04 00:30

Re: 3.3.0.x Rokua
 
I cannot reproduce the Browser rotation problem on Xperia X but on Jolla it is quite the opposite: I cannot avoid reproducing it.

The bug in #9 is 100% reproducible on both, as long as you have a patch installed that enables any screen rotation. Open at least three applications. It makes no difference which ones. Go to the home page. Rotate the phone to landscape. Go to any open application. Rotate the phone to portrait. Swipe back to the home page. Voilį!

Rotating the phone in the home page fixes it.

hardy_magnus 2020-04-04 05:24

Re: 3.3.0.x Rokua
 
any special feature added in this release? i saw release notes but i couldn't find one.

r0kk3rz 2020-04-04 05:31

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by hardy_magnus (Post 1566561)
any special feature added in this release? i saw release notes but i couldn't find one.

Newer GCC (gcc8) is a pretty good special feature, something a lot of people have been calling out for for years now

HtheB 2020-04-04 07:53

Re: 3.3.0.x Rokua
 
@pichlo, sorry to hear about the bugs... I'm a happy Android user with no bugs. :p
(The thing with Android is; it just works, no need for so many patches and stuff that needs to be edited out of the box to make it usable)

juiceme 2020-04-04 10:33

Re: 3.3.0.x Rokua
 
I updated my XperiaX to Rokua yesterday, and indeed there are nice new features like luks encryption of /home/nemo and NFC.

There's just a slight problem that I discovered; pulseaudio is broken and I cannot get any sound out of the device, headset or not ans similarily there is no microphone output via any channel...

I opened a report on TJC for the bug

This is what I see on journal;

Code:

[root@Sailfish nemo]#
[root@Sailfish nemo]# journalctl -a --no-pager -u pulseaudio
-- Logs begin at Sat 2020-04-04 13:09:04 EEST, end at Sat 2020-04-04 13:24:29 EEST. --
Apr 04 13:09:05 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:09:05 Sailfish pulseaudio[780]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:09:36 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:09:51 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:09:52 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:09:52 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:09:52 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:10:22 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:10:38 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:10:39 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:10:39 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:10:39 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:11:10 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:11:25 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:11:27 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:11:27 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:11:27 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:11:57 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:12:12 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Start request repeated too quickly.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Failed with result 'start-limit'.
[root@Sailfish nemo]#


meloferz 2020-04-04 17:18

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by HtheB (Post 1566566)
@pichlo, sorry to hear about the bugs... I'm a happy Android user with no bugs. [emoji14]

(The thing with Android is; it just works, no need for so many patches and stuff that needs to be edited out of the box to make it usable)

Yeah mee too, with official LOS 17.1 I have gesture that are almost the same as Sailfish, the bad thing is that I have to surrender with Google as I have to use their services for apps like banks, payments, and so...

Enviado desde mi H3123 mediante Tapatalk

carlosgonz 2020-04-04 18:04

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by juiceme (Post 1566576)
I updated my XperiaX to Rokua yesterday, and indeed there are nice new features like luks encryption of /home/nemo and NFC.

There's just a slight problem that I discovered; pulseaudio is broken and I cannot get any sound out of the device, headset or not ans similarily there is no microphone output via any channel...

I opened a report on TJC for the bug

This is what I see on journal;

Code:

[root@Sailfish nemo]#
[root@Sailfish nemo]# journalctl -a --no-pager -u pulseaudio
-- Logs begin at Sat 2020-04-04 13:09:04 EEST, end at Sat 2020-04-04 13:24:29 EEST. --
Apr 04 13:09:05 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:09:05 Sailfish pulseaudio[780]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:09:05 Sailfish pulseaudio[780]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:09:36 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:09:51 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:09:51 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:09:52 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:09:52 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:09:52 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:09:52 Sailfish pulseaudio[2987]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:10:22 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:10:38 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:10:38 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:10:39 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:10:39 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:10:39 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:10:39 Sailfish pulseaudio[3260]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:11:10 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:11:25 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:11:25 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:11:27 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:11:27 Sailfish systemd[1]: Stopped PulseAudio (system-wide mode).
Apr 04 13:11:27 Sailfish systemd[1]: Starting PulseAudio (system-wide mode)...
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Apr 04 13:11:27 Sailfish pulseaudio[3975]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 13:11:57 Sailfish systemd[1]: pulseaudio.service: Start operation timed out. Terminating.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: State 'stop-final-sigterm' timed out. Killing.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Apr 04 13:12:12 Sailfish systemd[1]: Failed to start PulseAudio (system-wide mode).
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:12:12 Sailfish systemd[1]: pulseaudio.service: Failed with result 'signal'.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Service hold-off time over, scheduling restart.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Start request repeated too quickly.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Unit entered failed state.
Apr 04 13:12:13 Sailfish systemd[1]: pulseaudio.service: Failed with result 'start-limit'.
[root@Sailfish nemo]#




I updated my Xperia X to Rokua, and all the sound is working well, without encripted data.

mosen 2020-04-04 18:06

Re: 3.3.0.x Rokua
 
Hey Pichlo!

Sad that you have regressions on Jolla 1.
I just dug out a spare one and tried to update from 3.1 to 3.3. But the battery died in the middle of the process ( :D ) and now i can only tell you if a complete fresh flashed device shows the same symptoms after the upgrade path from 1.0.
Later this evening u guess, it is currently at 1.2 after 4 updates.

For Pro¹ and XA2 i can see advancements in UI speed. Most obvious in Pure Maps where changes from the map to next screen are now much smoother.
Also long lists scroll with less hickups imo.

The next cloud integration is welcome.
Working with my self hosted instance is really nice and fast.

juiceme 2020-04-04 20:34

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by carlosgonz (Post 1566623)
I updated my Xperia X to Rokua, and all the sound is working well, without encripted data.

As I explained on TJC, I did a factory reset on the device, and then upgraded 4 times to get back to Rokua.

Now it works, sound and all with encrypted home but I still need to install the 183 rpm's I had before (applications and tools) and restore my data. I am rsyncing it back now, churning it in at the moment, 9GB to go.

Fellfrosch 2020-04-05 07:44

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by mosen (Post 1566624)
For Pro¹ and XA2 i can see advancements in UI speed. Most obvious in Pure Maps where changes from the map to next screen are now much smoother.
Also long lists scroll with less hickups imo.

While I had back SD card support for my Pro¹ it's gone again with Rokua. :mad:

Also I lost my sound at first. After a reboot with all patches disabled, it works again. After reapplying one after another I couldn't find a culprit. Which is strange, because I rebooted before more than just once, without success. I had to disable all patches to get it to work again.:confused:

meemorph 2020-04-05 08:15

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by pichlo (Post 1566525)
3.3.0.14 (Rokua) was released yesterday. The first impressions: nothing changed, except on my Jolla which gave me a scare of mt life with this:

Attachment 41037

Has anyone noticed anything like that?

Despite the scary icon, the phone was not in the aeroplane mode and I could make and receive calls, use mobile data etc.

Note: It only affects my Jolla. My spare Xperia X looks normal.

Hi, i had the same issue on my beloved JP1301 (The First One). It was caused by an uncomplete update. The phone told it is 3.3. version but had no network! Network was completly dead!

If you have network connections a 'version --dup' could be helpful.

I had no network and did a manual reinstall of the cached packages from the update, that way (be careful):
Code:

devel-su
mv /var/cache/zypp /var/cache/zypp-old
ln -s /home/.pk-zypp-dist-upgrade-cache /var/cache/zypp
zypper dup
rm /var/cache/zypp
mv /var/cache/zypp-old /var/cache/zypp
reboot

And remember, 3.3 is EA. Only install it if you like problems. ;-)

Fellfrosch 2020-04-05 18:12

Re: 3.3.0.x Rokua
 
Sharing is completely broken on my device. No matter what file I want to share, I get a completely blank screen with no options.

Also I have my Nextcloud installed in a subfolder. And I“m not able to connect, like some others on TJC.

cy8aer 2020-04-05 18:38

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by Fellfrosch (Post 1566656)
Sharing is completely broken on my device. No matter what file I want to share, I get a completely blank screen with no options.

Also I have my Nextcloud installed in a subfolder. And I“m not able to connect, like some others on TJC.

Sharing does not work if you have something installed which shares, like qr-sharing, nextcloud-daemon... Deinstall those and reboot...

Fellfrosch 2020-04-05 20:24

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by cy8aer (Post 1566657)
Sharing does not work if you have something installed which shares, like qr-sharing, nextcloud-daemon... Deinstall those and reboot...

Yes, thanx that helped. :)

pichlo 2020-04-06 08:18

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by juiceme (Post 1566628)
As I explained on TJC, I did a factory reset on the device, and then upgraded 4 times to get back to Rokua.

It seems that's what I will have to do too. Except in my case the number of required steps is closer to 10 as my Jolla is one of the First Ones.

It seems completely borked underneath. HtheB may have been right after all, the aeroplane mode icon may be the least of my problems.. Any Store or Warehouse operation fails, no matter how many times I try pkcon refresh or to clear app registry in Utilities. Other than the two issues it seems to be working on the surface, but who knows what other issues lurk under the bonnet.

If only a reset wasn't such a hassle...

peterleinchen 2020-04-06 09:06

Re: 3.3.0.x Rokua
 
Sorry for you and juiceme and all.
This should not happen!

Using olf's sfos_upgrade minimizes the hazzle, at least...

mosen 2020-04-06 10:58

Re: 3.3.0.x Rokua
 
I can at least confirm a freshly reseted and upgraded Jolla 1 has no issues.
Quite telling that i can not remember if it was 8 or 10 upgrades...
When going from 1.2 to 2.0 all the Jolla apps tried to reinstall themselfes and failed after >10minutes of trying each. I force rebooted with no errors afterwards but i suggest to not install any (Jolla) apps at the start like i did.

Wasn't there some full image for the Jolla 1 to flash and skipping many updates?

Here https://talk.maemo.org/showthread.php?t=100528

juiceme 2020-04-06 11:03

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by peterleinchen (Post 1566672)
Sorry for you and juiceme and all.
This should not happen!

Using olf's sfos_upgrade minimizes the hazzle, at least...

Well as it is a prerelease I cannot really blame Jolla for it.
When it is released for everybody then I agree thing like that should not happen.

One thing what I have noticed is that some operations are notably slower after enabling device encryption; for example device unlocking after typing the code takes about 2 seconds compared to almost instantaneous unlock of an unencrypted device. Also checking email takes about 30 seconds agains about 10 seconds before.

nonsuch 2020-04-06 11:36

Re: 3.3.0.x Rokua
 
Does this release include upgrades to the default browser?

acrux 2020-04-06 11:42

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by nonsuch (Post 1566677)
Does this release include upgrades to the default browser?

Why don't you check it yourself? :)
https://together.jolla.com/question/...log-330-rokua/

JoOppen 2020-04-06 14:21

Re: 3.3.0.x Rokua
 
I have encountered none of these issues so far - I updated two J1 (for our son), 2 Xperia X (my own old back-up phone and our daughter's phone), a tablet, an Aquafish (out of curiosity) and my actual XA2 (without encryption) and the Xperia 10 (with encryption).

I didn't do any factory reset.

The Xperia 10 feels a little bit unstable (some unexpected reboots and initial hickups with Here maps when trying to choose the SD card as memory for downloaded maps, for instance, but that have gone by now). Plus, the Xperia 10 still has a bad stamina (unlike the XA2 which is great in that respect). But otherwise, everything appears to be fine

deprecated 2020-04-08 16:59

Re: 3.3.0.x Rokua
 
I updated my Xperia X (single sim) via the in-settings update dialogue, and it got stuck in a bootloop. This was likely due to my endless tinkering, so I reflashed with the latest then updated immediately via an ssh session.

I've not seen any of the bugs in this thread so far. So, my suggestion - if you're seeing these kinds of issues - try a fresh flash.

peterleinchen 2020-04-08 21:52

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by deprecated (Post 1566719)
I updated my Xperia X (single sim) via the in-settings update dialogue, and it got stuck in a bootloop. This was likely due to my endless tinkering, so I reflashed with the latest then updated immediately via an ssh session.

I've not seen any of the bugs in this thread so far. So, my suggestion - if you're seeing these kinds of issues - try a fresh flash.

Cmon.
Not serious, or?

This is definitely not the right way!

pichlo 2020-04-09 06:53

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by peterleinchen (Post 1566725)
This is definitely not the right way!

No, it isn't. OTOH, juiceme is right. It is a pre-release for early adopters.

nonsuch 2020-04-10 06:21

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by acrux (Post 1566678)
Quote:

Originally Posted by nonsuch (Post 1566677)
Does this release include upgrades to the default browser?

Why don't you check it yourself? :)
https://together.jolla.com/question/...log-330-rokua/

Thank you! :)
And the answer is here: Yes.
However, I cannot see that the browser engine has been updated to a newer version, the backend?

More general:
Many people say that the stock browser is less than perfect in many ways, and some go to great lengths to install one that works better, is more up-to-date.
Do the updates address these issues and is the updated stock browser sufficiently up-to-date and generally more usable?

atlochowski 2020-04-10 07:33

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by nonsuch (Post 1566760)
Thank you! :)
And the answer is here: Yes.
However, I cannot see that the browser engine has been updated to a newer version, the backend?


More general:
Many people say that the stock browser is less than perfect in many ways, and some go to great lengths to install one that works better, is more up-to-date.
Do the updates address these issues and is the updated stock browser sufficiently up-to-date and generally more usable?

About backend:
I think you already know how to check it http://talk.maemo.com/showthread.php?t=100990

cy8aer 2020-04-10 09:35

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by nonsuch (Post 1566760)
Thank you! :)
And the answer is here: Yes.
However, I cannot see that the browser engine has been updated to a newer version, the backend?

about:support shows: 45.9.1 - this is not a >50, expected from some new patch some days ago.

nonsuch 2020-04-10 17:33

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by cy8aer (Post 1566766)
about:support shows: 45.9.1 - this is not a >50, expected from some new patch some days ago.

That's the same version as on Nuuksio :(

What patch?

Is this analogous to Firefox versions?
Firefox 45.9.0 ESR was the last version of that cycle, some time in 2017.
So what's 45.9.1 then?
What is the Security status of that version?
And - I don't know how you call this - compatibility with modern website features?
Please help me understand this - opinion, technical data, experience, all welcome. Thanks.

lantern 2020-04-11 07:12

Re: 3.3.0.x Rokua
 
Probably it is the 45.9.0 with some backported patches.
Make your own conclusions.

nonsuch 2020-04-14 08:38

Re: 3.3.0.x Rokua
 
Quote:

Originally Posted by lantern (Post 1566780)
Make your own conclusions.

Not sure what you mean by this.
People here really aren't all that concerned about browser security, yes?


All times are GMT. The time now is 11:16.

vBulletin® Version 3.8.8