Still… how do you get three instructions? I can’t seem to get anything corresponding to the middle one.
And what does it look like in English?
Also… i don’t think this is the place to bug-report community stuff - maybe the author could just turn down the font size to something that makes the design match the DPI?
You have to setup Quicklaunch-Shortcut in the Preferences of Lockscreen. Add at least one Entry.
Here is Swedish on 21:9 on an official port, for reference.
Looks like you have a port-specific font misconfig to me.
And in Norwegian, but I do not see the equivalent “Passe deine” text in my language.
The
Unlock to access shortcut — Entsperren, um auf die Verknüpfung zuzugreifen
Unlock to access shortcut — Lås opp for å få tilgang til snarvei
is not used on my phone
This is when I pull down to launch the app Browser from the lock screen
EDIT: Using a 10 III
Yor posted Screenshots here looks all like 21:9 screen ratio, so more screen height availble for text and spacer. Even with big font setting you will never face this problem.
I will try to reproduce it on our 16:9 Devices XA2 and X Compact.
Edit:
XA2 and X Compact doesn’t have the Wordwrap of “Sicherheitscode Eingeben”, just in one line, so no Problems there.
Would you also like people from the community to no longer communicate their efforts, the software they make and the bugs they find in jolla software? Sheesh.
This call icon is out of place (design wise) no matter how close or not is in the message.
It either needs a redesign or the function to be hidden in a pulley.
Und das ist sperrig 
How do I set up a Quicklaunch Shortcut in German? By chance, the one stock device with license and foo I have is a 10ii.
Is it the ‘Schneller Zugriff auf Ereignisse’ setting? And who translated that if that be the case.
Ok, I think I got it. Set up email, lock screen, pull down to check emails, wrong finger and I just get ‘Sicherheitscode eingeben’ + ‘Fingerabruck nicht erkannt’. What have I done wrong!
Also… i don’t think this is the place to bug-report community stuff
Why not?
I think the Community-Port doesn´t alter the QML-Designs of SailfishOS, so it may be for interest to know that there can happen Design-Bugs with certain Aspect-Ratios/Languages.
- maybe the author could just turn down the font size to something that makes the design match the DPI?
The Community-Port and in general my two other officiall Sailfish-Licenses were shipped out with Fontsize set to normal.
So i think its important to know the Design will look correct in any Language at any Font-Size at any Device and Aspect-Ratio-Display & Resolution (16:9, 18:9, 21:9).
This are so small things that damaged the great whole SailfishOS-UI-Design-Experience, which at least pull me to this nice mobile OS.
Not at all! I’d like to see more ports discussed on the forum if anything.
But what i think is counterproductive to mix community port bug reports with ones that are aimed directly at Jolla. (And if this was purposefully aimed at Jolla, i think that is inaccurate too - to be continued, and i could turn out to be wrong)
Assumptions/reasoning:
Supporting evidence:
Sorry, I don’t understand. The components in question have nothing to do with ports and originate from packages that come for Jolla. This is not a ‘community port bug report’. It is a jolla provided component. The translations, I can’t speak for…
I’ve recently spent a LOT of time debugging issues which there have been ‘some indication’ there might be a port issue, only to discover, nothing of the sort. But I spend double the time since I check on my preferred (and better) devcies first and confirm my suspicions on the 10ii. That burden I’m happy to take on to make certain I’m:
That did NOT prevent me from posting a bug report upstream only to retract it a couple of days later because the bug was in Jolla’s code. So. It doesn’t matter to what elaborate measures I go, there will be triage. And, frankly, I resent the ‘in crowd’ sentiments with hand waving in the direction of private repositories.
@pherjung and @thigg are doing a damn fine job sorting out what is and is not a bug that should be tracked.
That’s what is known as a cheap shot. If you had actually looked at the repo, you would have noted that I had already posted 2 bug reports there.
I post Bug-Reports where i think they belong (Github, Here…etc).
Please someone official can verify this.
I’ll try to distill down my reasoning:
This looks like the font size has somehow gotten humongous (as opposed to the padding being completely out of whack for example).
My understanding is that porters set (or can change) this system-wide multiplier, and that it should probably be reconsidered. Very understandable to overcompensate a bit for the small screen.
Surely Sailfish mistaking this for 16:9 would make it fit better, not worse.
And if it was instead treating it as 21:9, there is still more than enough space just in the middle padding for this to fit.
The very likely unintended linebreak supports this.
I’d be happy to be proven wrong, but i just don’t see it shaking out any other way.
I’ll butt out now. Hope you get it fixed either way.
Anyone can change those settings but it is precisely this supposition that led me upon a wild goose chase.
The bug report from @pawel.spoon mentioned by @attah, and which @piggz wished to see reported elsewhere was made in Devices. Now, I see that as being discrete from ‘bugs’ per se. And not a ‘Sony devices only’ category. In any case, it was clearly noted what device was in question. That Jolla can disregard this is a given!
Incorrect. It was moved.
I’m unable to get these messages on my X10 II. Can someone else confirm? Is it possible that messages get truncated if the screen is smaller?
