Jump to content
Waxberry

[Community Build][3.2.1.20][Updated Jan 20] Sailfish OS for Fxtec Pro1

Recommended Posts

OH just remembered I meant to ask how to get "/" I'm on QWERTY device.  It's above the "P" but I am wondering if my layout is wrong in sailfish or something?

Share this post


Link to post
Share on other sites
3 minutes ago, epninety said:

I followed the instructions here which worked a treat.

(I found them linked from here, which might also be a useful page to read)

Hadn't seen that will get that done as well 🙂

Share this post


Link to post
Share on other sites
1 minute ago, _DW_ said:

Hadn't seen that will get that done as well 🙂

Its a bit tricky without it,  I found I was using a combination of HWKB and VKB at the same time before I found that!

Share this post


Link to post
Share on other sites
3 hours ago, epninety said:

Its a bit tricky without it,  I found I was using a combination of HWKB and VKB at the same time before I found that!

ditto haha 😄

Share this post


Link to post
Share on other sites

With the kb hack, how have you guys found it? I've used the first one but have found it has disabled the quotation marks and the tilde. All other keys are fine.

Share this post


Link to post
Share on other sites

It didnt disable them, you are using the one with dead keys on first two levels.    Switch to the layout with altgr dead keys, then everything will behave normal.

The way I read the last post in that git thread, from 7 days ago, implies the us-intl with alt-gr dead keys is already the default, but it seems its not?  Either way doing it following kabouik's method works until its fully resolved.

Explanation of dead-keys and difference between the two us-intl layouts. 

A dead key is a key that, on a typewriter would not advance the cursor, so they are typically used for accented letters.  For example, if you want é you type ' and then e, and they end up the same place because the ' didn't advance the cursor.    Under the standard US International Layout, most accent keys like ~`'" etc are dead, so if you want ' you type ' then space bar to advance the cursor.  On a computer nothing seems to happen when you press a dead key until you press either a letter that can accept that accent, or space bar.  If you rarely type with accents, then you should use the layout with dead keys moved to third level.  Then they will only be dead if you use them in combination with either slant-arrow key (which have been remapped in kernel to right alt), so you'll likely never notice them if primarily using English.

Sailfish OS doesn't even currently support dead keys.  So that is another reason not to use the standard dead key version.  However - if you use elros ubu-chroot, there's another issue - it is not recognizing any third level characters the way its currently set up.  Which means no /? with us-intl as they're third level of LP since thats where Fx-tec labeled them instead of providing dedicated key.  (Hopefully we can get SYM mapped to this functionality).  However, ubu-chroot does currently support dead keys (on first two levels only), so that's the only reason to use the standard version - if you use ubu chroot a lot and want dead keys easily accessible, for example French typers.

Notes:

When I refer to levels, level 1 is normal key without modifier, level 2 is with shift.  level 3 is with right alt.  level 4 is with right alt and shift.   Level 4 is not convenient on Pro¹ when thumb typing unless we get sticky shift.

The right alt key is sometimes called AltGr because some international keyboards label the right alt key that way.  Gr is probably abbreviation for right in some language?

Edited by Craig
Improve
  • Thanks 4

Share this post


Link to post
Share on other sites
On 11/15/2019 at 6:27 PM, Waxberry said:

[...]

fashboot flashing unlock

[...]
 

 

 

minor typo, fashboot → fastboot

  • Thanks 1
  • Haha 1

Share this post


Link to post
Share on other sites

if it is expected that TWRP warns "no OS installed" when one wants to reboot, can you then please add a note to that effect to the top post?

 

I got the warning, yet SailfishOS 3.2.1.20 booted fine.

Edited by pcfe
typo & clarification
  • Like 1

Share this post


Link to post
Share on other sites

 

4 hours ago, pcfe said:

I got the warning, yet SailfishOS 3.2.1.20 booted fine.

Not sure it helps, but I had the same issue. I must have hesitated for almost a whole second before my eagerness to see Sailfish on the Pro1 got the better of me :classic_blush:

  • Like 1

Share this post


Link to post
Share on other sites

Ya me too.  Concerned, but proceed anyway as no other ideas, and works.  Agree it should be noted in first post.  Also it would be good to note that you don't have to use SDcard in the first post.

  • Like 1

Share this post


Link to post
Share on other sites

odd, I just started to reflash to verify my notes and noticed;

- TWRP was no longer bootable, trying to go into recovery (by choosing in bootloader) I'd end up in SFOS. Is it intended that installing `sailfishos-t5-release-3.2.1.20-devel-20200122.zip.sha256sum` replaces TWRP in `a` (or changes to `b`, I stupidly forgot to try to `fastboot set_active a`and just try again, sorry.)

- one can just the initial posts's steps again and end up in TWRP (as i expected)

- TWRP `Failed to mount /vendor (Invalid argument)`, unsure if this was also on first install. Sailfish comes up just fine. Full log saved (note to self: `workstation:~/Desktop/recovery-Pro1-2nd-SFOS-flashing.log`) and available upon request

  • Like 1

Share this post


Link to post
Share on other sites

We dont have a recovery partition.  So when you flash twrp to boot with fastboot, then install sfos with twrp, you're overwriting twrp.   So if you want to use twrp to backup, you flash twrp back to boot with fastboot, do your backup, then use fastboot to flash the sfos boot.img when done.  If I understand right.

 

(If we had a bootloader that allowed us to boot images like my Moto Z²F, or had a recovery partition like my Moto Photon Q, this wouldn't be necessary!)

Edited by Craig
edit: clarify, as pcfe said
  • Like 1

Share this post


Link to post
Share on other sites
11 hours ago, Craig said:

We dont have a recovery partition.  So when you flash twrp to boot, then install sfos, you're overwriting twrp if I understand right.   So if you want to use twrp to backup, you flash it back to boot, backup, then flash sfos again when done.  If I understand right.

Thanks for the confirmation that recovery is overwritten. Learned the same in discord overnight 😉

For others reading here, obviously do not reflash whole phone if you do TWRP backups but only /boot/hybris-boot.img (which you have to backup! . c.f. these install notes; https://gist.github.com/Kabouik/f77539b3eb6a77b032d2fa827271b81d )

  • Like 1

Share this post


Link to post
Share on other sites
On 2/1/2020 at 4:16 AM, pcfe said:

 

minor typo, fashboot → fastboot

some of us prefer fashion to getting dressed quickly ok

  • Haha 1

Share this post


Link to post
Share on other sites

Great to see the work being done on porting SF OS onto the pro 1. would love to see some more action here as I feel SFOS is one of the best candidates for a daily-driver worthy platform in terms of feature-completeness etc. I've been supporting it for years, and to be honest it's one of the few alternative platforms that is still actively improving (RIP Blackberry 10, and WebOS) with development still ongoing at least somewhat...

It sucks that jolla won't allow an official sailfish port for the pro 1 because it's definitely the best hardware to ever support it in any capacity!!

Is there any person from Jolla/SF that the community here is liaising with, if so, how can we get involved with that? It would be nice to demonstrate to their team that there are enough people interested in running a paid version of SFOS on the pro 1.

Share this post


Link to post
Share on other sites
14 minutes ago, ponzimeme said:

...there are enough people interested in running a paid version of SFOS on the pro 1.

I guess that could be the big question. What is the critical number before they will bother to support it. If that is say 50000 we are unlikely to reach that,

Share this post


Link to post
Share on other sites

I've heard speculation that it is becauses Jolla requires a large fee from Fxtec to support a new device, in addition to the cost of the licenses the user has to buy.   This large fee is because they have to modify specficially for the device.   In our case, it shouldn't be too hard cuz Sony Xperia XA2 is similar enough to leverage most everything - for example the Alien Dalvik (Android support layer) from XA2 has been tested on Pro¹ and works fine for touchscreen, however doesn't work well with hardware keyboard.  So Jolla would have to put development effort into resolving that.  But with the community port working fairly well, it seems like it wouldn't be that hard for them to do it, give one dedicated programmer a week and could be done (in my imagination, anyway).

Share this post


Link to post
Share on other sites

yeah, i agree that it might be hard to demonstrate real demand for the whole package...

interesting to hear that the android support layer has been tested on the pro1? do u have links to this?

i do find it hard to believe, however, that sony paid jolla a fee to create the sailfish x programme? do you have any links to this info as well?

Share this post


Link to post
Share on other sites

Well, at first we should try to obtain at least some numbers to show how many we are interrested. It is probably too early to make some foundation since not all of us have the phone already, but later on it could be good idea to think about some campain. Sure, until we do not know whether Fxtec has to pay a fee or not it is kinda useless, but on the other hand it may be an initialising push. Anyway, I am definitely in! I am up to pay the device cost to Yolla for full SfOS!

Share this post


Link to post
Share on other sites
2 minutes ago, Swond said:

Well, at first we should try to obtain at least some numbers to show how many we are interrested. It is probably too early to make some foundation since not all of us have the phone already, but later on it could be good idea to think about some campain. Sure, until we do not know whether Fxtec has to pay a fee or not it is kinda useless, but on the other hand it may be an initialising push. Anyway, I am definitely in! I am up to pay the device cost to Yolla for full SfOS!

If they need a specific amount that is not secret then crowd funding could perhaps be an option?

  • Like 1

Share this post


Link to post
Share on other sites

I wouldn't be surprised if Jolla has access to the numbers using the community port, by number of Pro¹ accessing Jolla store.

Share this post


Link to post
Share on other sites

Not sure if SFOS would support APKs then, but I could see myself using SFOS instead of Android, so I'd pay for a good OS. But it'd have to be easy and most things should be working - then I'd buy a license and switch.

  • Like 2

Share this post


Link to post
Share on other sites

most stuff is already working, it seems. and the rest, i think would be fixed too, with a bit of time. problem is, Jolla limits community editions - not allowing them to run android apps, etc.

for me, at this point, i want to de-google myself as much as possible... and i really like the sort of basic ideas that SFOS uses in its UX design and functionality of the OS...

i don't think the other alternatives like ubuntu touch etc are anywhere close to being as usable as SFOS...

Interesting to see what kind of traction the Fairphone 3, Gemini PDA, Librem 5 and PinePhone get in terms of attracting a motivated group of devs etc. I do think that this is the best time ever in the post-iphone era that we've seen multiple somewhat successful attempts at putting out relatively "open" hardware...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Terms