Leaderboard

This is intended as a central entry point with links to known ROMs for the PRO1/PRO1X. You will need android adb / fastboot tools that officially can be found here (Windows / Linux / mAc) Important step BEFORE changing from Android initially!! If you want to ever be able to change the phone back to the state it had when you received it with stock Android, there is an important step that is needed before flashing any non android-based ROM, That is to backup the persist partition. If the device is unlocked and a recovery boot is present a fairly simple partition backup method (fo

LXC is such a good combination with the Pro¹ that it might be worth a video on the official forum, even though I'm not very active here: - LBRY for good connections (big file): https://open.lbry.com/@Kab:7/LXC_sailfishos_Pro1:b?r=BZ8k2XPpJvbZhRttC15UQs34pYd2SS97 - Youtube for slower connections: https://youtu.be/-dgD5jci8Dk DESCRIPTION Sorry for the annoying accent. This is an overview of full desktop Linux distributions running as LXC containers in SailfishOS, on a F(x)tec Pro1 qwerty slider phone. If not interested in Sailfish itself, jump to 06'23" f

New build is up, the link in the OP is updated. Changes: * Fixed keyboard backlight. * Fixed incremental file update. New MD5: 8d557ea563667d1332dd99729fa5e4ca This is a full update because the existing incremental updater is broken. Future updates should be incremental and automatic, if all goes well.

Also a replacement USB panel would be good to be part of that bundle.

Figured out the issue with the keyboard backlight. Lineage decided they wanted to add the keyboard backlight logic into the Android core (frameworks/base) and delete the keyboard backlight logic from the lights HAL. This is Lineage specific -- neither AOSP nor AICP have it. I made a brief attempt to add the Lineage code into AICP's frameworks/base but it didn't go smoothly. So I'm just going to revert the change and move on. I hope to have a new build within a few hours.

According to the email that I received the repair kit is for Pro1 also. The screen kit looks like to be full assembly with the frame but I think that it is blue color. USB charging board would have been a good addition. Then I would back it immediately.

Android 10 seems to present some additional challenges with the external SD card. With Open Camera, I had to go to "more camera settings" as usual, but unlike with Android 9, I had to toggle on "Use Storage Access Framework." Then it allowed me to give permission for the "Save Location" to access a folder on my SD card and now Open Camera is saving to the SD card again. Google seems to be determined to make things as difficult as possible for using SD cards. Grrrr

Is the current tech bundle worth it for pro 1 owner? Do they sell the whole upper part (not only the replacement screen)? Will replacement screen not be available in the future? What about battery: is it worth to already purchase a replacement one now? How long can these replacement parts be stored?

Also it would be nice to have the choice of a black screen for the normal version instead of the blue one

@Hook I can indeed reproduce that issue on Android 10. I'll try and find some time to fix it.

You got one! 🙂 One request, add some menu that shows available keyboard shortcuts. Can't figure out how to move cursor to addressbar with just the keyboard.

Okay I'll look into that next.

I just put up an incremental ota with the keyboard settings fix. I don't have time to test it myself right now so you guys are the guinea pigs. 🙂 Please let me know if it works. No need to futz with gapps, just install and reboot.

Downloaded. Installed smoothly and the keyboard backlight works! 🥇 Oh, and has the November security patch!

I found the issue with the incremental updater. We will try that again with the next build.

Just published release v1.0.8 tackling bookmarks export issue on Android 10 and some keyboard shortcuts update as mentioned above. @Hook your bookmarks export should work then, it lands in a folder below that path Main Storage \ Android \ data \ net.slions.fulguris...

Have a look over here, where a browser have troubles saving using 10.0 , Could be the same issue that @Slion got with his browser.

@Waxberry @Erik That secret tech bundle is missing a replacement keyboard layout. Hopefully we will get there.

@netman This review was really great! I'm particularly fascinated by the lxc container support... that was really impressive. If anyone else is, there's a reddit post with some more information here:

Good point, I'll try it out tonight.

Odd. It has storage permission on both phones. The only other thing I can think of is both phones are on versions of Android 10. Have you tested on Android 10?

It's not an inch above, rather the bottom most left corner. If I hold it down the button highlight displays which should be it's fairly lenient hotbox but my finger is like 0.25" to the left of that. Tried to screenshot it but sadly the highlight goes away as the shot it taken.

I've never used it before, but the export and import bookmarks seems broken. When I go to "Export bookmarks to backup" I get "Error Sorry, bookmarks could not be exported!" with an OK button. I tried it on my Moto G8 as well, so it isn't just the Pro1 nor is not being on stock.

Actually on Chrome it is Ctrl+L and F6 so I'll add those ASAP.

My install OTA gave a boot loop. But booting to the fastboot menu, and just Start, and it boots. I can see the package is downloaded and ready to install. (trying once more gave the same result)

Okay I've uploaded the file and pointed the link in the OP to the new one. New MD5: e6d57186599ab0177a48fc3984c6ae5b

It must be broken. I'll check into it and upload the full zip later. Thanks for testing.

Lol. I never think of OTA being... OTA 😄

Settings, aicp extras, update center.

if anyone has the gapps issue with the version 17 thats now live. 1. adb sideload Lineage Image 2. adb sideload Gapps 3. Reboot and boot into the Lineage (set up the phone until you are on the home screen) 4. Boot into Recovery Mode again 6. adb sideload Gapps again. Then it works

I replaced mine with: https://de.aliexpress.com/item/4000523673519.html?mb=D9NGx35N67Qw8yz&srcSns=Copy&tid=white_backgroup_101&tt=sns_Copy&image=Hfc63578c13284fe78f900be394299acfN.jpg&spreadType=socialShare&aff_platform=default&sk=_d8cjaSP&aff_trace_key=acaa005ffb644b6b845f84bc5a28b1c0-1600037785550-07177-_d8cjaSP&businessType=ProductDetail&templateId=white_backgroup_101&title=€+46%2C92+|+AiBaoQi+New+Original+5.99+inch+Touch+Screen%2B2160X1080+LCD+Display%2BFrame+Assembly+Replacement+For+Elephone+U+Pro+model+phone&platform=AE&terminal_id=77df

I finally got around to doing a video review:

Yes, was too hasty. Sorry, The keyboard has an odd state that can be entered in two ways 1) Press Sym and get the symbol-selector and do NOT select a symbol, but press Sym again, to have the selector go away 2) Press Sym+Key where nothing is assigned, e.g. Sym+J It leaves the keyboard in an odd state, ignoring normal letter presses. To get out of this state either a) Press Sym, Press e.g. a letter key, Press Sym again b) Press Sym+Key with an assigned key (e.g. 2)

Sorry I am not familiar with the hardware on this level. It is possible that the new screen is different in some subtle way. Or perhaps it is possible you got a defective screen. I know others have changed screens without any apparent issues.

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!

My back button keeps being activated at even the slightest touch to the bottom left corner of the screen, like if I'm resting the phone in my left hand for example. I use Edge Null but it doesn't seem to work on the system buttons. Does anyone else have this issue or any suggestions? It's detecting a press from like a full inch from it's icon.