Leaderboard

In my opinion LineageOS 16 was a very important OS for the Pro1 that brought the best out of the device at a moment when stock couldn't (yet) . Although not a developer, I can well imagine it also broke the ground for all future releases of Lineage on the Pro1. So, I guess this is an appropriate moment to thank @tdm for all the hard work!

The first Lineage 17.1 build has been posted on the official download site. Please note, I have not really been involved with this version and I am not running it on my device, as I prefer AICP. I would suggest @EskeRahn create a discussion thread. I'll probably monitor that in case any issues arise and need pointed out to the current developers.

I would be happy if it would be just that 😄 However, the edge is way too far in here. I can't even press the record button on What's App anymore. With the old screen, I had margin set to the middle setting which was perfect. Here, even on setting 0 it still does not react on about 7 - 8mm at the edge of the screen. I can make a video to show this. As soon as I connect an original screen, the issue is gone. So I do know that it's a hardware change in the new screens I have, though they look identical (even the electronic parts and silk on the FPCs are the same).

I received a Pro 1 back from a customer with the exact same issues: Microphone issues and non-working hall-sensor. I completely disassembled it. The good news: The hall sensor (and probably also the microphone, didn't check) is sitting together with the USB port on an extra PCB which is connected to the mainboard. That's an awesome design - as it means that you can even fix ripped out USB ports easily by simply replacing that small extra PCB! Now... we just need to get hold of the PCBs. I've contacted the team a week ago, as I want to stack them so I can offer replacement p

As suggested... And with a qquote from the original post of that thread: You can find the builds and installation instructions on the official LineageOS Downloads page

sdcard should work, but I haven't personally tried. Yes you need a gapps that matches your android version. So, for example, opengapps for Android 10 (and arm64, of course). Don't forget to switch slots with reboot/recovery before installing gapps.

It looks like the one @tdm made, but it seems to be without the qwertZ support...

Hi all, I'm back here after about a month. I've downloaded the 17.1 image. Do I also need the 17.1 recovery? From what I read at this thread, I am thinking the answer is no, but I thought it wouldn't hurt to ask. Thanks EDIT: By the way. I am thinking of putting the LOS 17.1 image into my sdcard and flashing it from the sdcard via recovery as I'd been doing with the 16.1 updates. Will it work? Cheers

I will probably earn a blacklist entry for all Lineage support but: I did a dirty flash from LOS 16.0 with MindTheGapps to LOS 17.1 with OpenGapps Nano. And the phone still works 😄 Just had to replace the cLock widget with another clock widget (as already mentioned in post #2).

Be aware, that the cLock widget was not ported to LineageOS 17.1 - in case you are afraid that you are starting to miss it... 😄

Only 17.1 will build now, but you are free to keep 16.0 as long as you wish, and even build yourself when new security updates come in.

Works for me. At this point I think what would determine whether we use the most minimal symbols or those more visually complex with corners or bars is whether we enclose them between brackets or not. Note that we could also just write "Fn" on the top right corner of the modifier key, and then show those symbols on their respective top right corner too, I may be equally clear that Fn is needed to use those functions. While AltGr would be in a distinct colour similar to us-intl symbols. Of course for layouts with no us-intl symbol labels, the issue vanishes because only two label colours a

If we suggest symbols to keep the labels short, I think those are more or less common (maybe not conventional, but at least straightforward): Page Up: ⇞ Page Down: ⇟ Home: ↖, ↸, ⭶, ⤒, ⇤, ⌜, ⇱ End: ↘, ⭸, ⤓, ⇥, ⌟, ⇲ Del: ␡, ⌦ Ins: ⎀ Source. Some are my own invention and may not make sense, some others are actually borrowed from Tab, but there wouldn't be any ambiguity in our case. We could propose a keyboard layout with that and only two label colours, with or without brackets. Note that ⎇ is also standard for Alt, albeit rarely used. This could be an

@Erik? 😧

This was a serious design decision of F(x)tec, they told about it earlier. I hope they can supply that PCB easily (as it is not a complicated thing) as it would be good to have some replacement boards in case something will broke.

While it's not directly related to LineageOS, I thought I might ask here as well, as it might be something that can be added: You can read more details about my issue here: Basically, I bought replacement screens from China from multiple vendors. They work fine, but they don't react to touches on the edge of the screen. I first thought the touchscreen is unresponsive - but that's not it: when I enable the function in the developer mode that shows the coordinates and draws your touches on the screen, I noticed that I can slide to the edge of the screen without any issues and 100

Ahaa. So i follow this guide for the recovery under Temporarily booting a custom recovery using fastboot

Here my slightly adjusted helper batch-script. Takes date YYYYMMDD as a parameter and assumes, the img, zip, and the nano is in a LineageOS subdirectory. (Note that I do not plan to download and change the OpenApps package each time, so the 20201110 is fixed here, And obvious if you want say the pico and not the nano, the name should be adjusted) An example of a call: LineageFLASH171.BAT 20201110 @ECHO off if %1.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause fastboot flash boot_a LineageOS\lineage-17

I would download the opengapps for Android 10, as the one you are using currently are likely to be for 9. I have not tried from SD, only ADB. But doubt that will make any principal difference - obviously given it can read the SD.

It is required - system mounts are handled differently, ROM will probably flash but GApps won't -- just use 17.1 recovery lol. And yeah, we moved all button settings to, well, button settings haha.

Just published release v1.0.6. History page is now themed. I've also submitted this version to Google Play, see how that goes.

I do not know if you NEED it, but it looks substantially different, so I would suggest so, unless someone can say explicitely that they know you do not need it.

Done, went super smooth and fast 🙂 IF we got mindthegapps while on 16.0 It seems to be important instead to install opengapps during in the 17.1 process. (That is as Mindthegapps in this version is not supported on 17.1, we can not leave it there, but have to have opengapps replacing it - as @Wheeljack did above too )

If you sideload, gapps does not migrate, so you do not need to remove anything. I do not believe major updates are distributed as OTA so that path is not possible. I cannot say why your upgrade failed without a log, and that is no longer available I guess.

Off-topic for this thread, but could you post a bit about your setup in the cases thread? I'd be interested in that setup :)

I'm no touching it till I find out got multi factor security software I need to login to work 😄

looks correct to me 🙂

Thanks for the warning @acrux for now I'm trying to download, but I guess I'm not alone, as it takes 'forever'.,,

The Lineage keyboard driver tries to make the keyboard look like a "normal" keyboard to Android. Because the print is in German, the default QWERTZ layout is the same as a German keyboard. I would be happy to work with you to adjust this for Swedish. Please send me a PM.

I'm using opengapps nano for Android 10 on AICP Q. It works fine. So I'm sure it will work fine on Lineage 17.1 also.

I'm selling a QWERTY Pro1 for $630 US, plus shipping. I prefer to ship to a buyer in the United States since international shipping isn't the most reliable right now. (Thanks COVID-19!) The phone is running the stock OS patched with the latest OTA update. Includes original packaging. I like the smartphone, no issues. No scratches. Thought I'd have more time to play and experiment with the Pro1 - I want to try Lineage 17.1 on it! - but haven't had time. Plus, I see other people waiting for their Pro1 units, and complaining on F(x)tec's Instagram...

I like your ideas, though one symbol is already used for backward jump to tab-stop (Shift+Tab) ⇤ I really like the principal idea of e.g. ⇱indicating a jump to a boundary, and not just an indication of something in a direction

I prefer ⇞, ⇟, ↸, ⭸, ⌦, ⎀, but I don't mind your choices.

I took the liberty to split this away from the LineageOS thread, as it is hardware-related.

Well, it's not a single screen, it would be a batch of screens. The ones I bought in March worked fine - but the new batch I recently bought has that issue. All of them, so it's not just one that is defective. Seems like this is a new revision - and the distributor told me it works fine on the Elephone U Pro. That seems to confirm that more recent batches have that behaviour. Maybe the screen was updated as it was oversensitive at the edges and that's now on top of the Pro1 own driver code to make it less sensitive. About dropping: I'm using a slightly modified leather case f

I have exactly the same issue. I changed the screen before and everything was fine. Then, after the next drop, I changed the screen again and got the described behavior. (I am thinking about a big rubber protector around the edge to protect the screen from cracking, now that I cannot use touch in the edge anyway. 😉)

I prefer the brackets option.

Well, on October 31 the target "pro1 userdebug lineage-17.1" was added to the build system while "pro1 userdebug lineage-16.0" was removed. That does not seem like a malfunction, it was done on purpose. See the diff here: https://review.lineageos.org/c/LineageOS/hudson/+/290451/ Until the respective target is re-added, the build system will not compile 16.0 for our device anymore. Independently of that, the build(s?) for 17.1 seem(s?) to have failed last Monday, as a patch to fix a build error was introduced on Monday evening: https://review.lineageos.org/c/LineageOS/androi

This is just me stating the obvious: FxTec has room to improve as far as hardware quality goes. My first Pro1: Screen rattle. Dead touch screen digitiser after 6 months. My second Pro1: Keyboard electrical problem rendering it unusable, DOA. My third Pro1, replacement for the second one after about 10 weeks wait: Scratches around the SIM tray, like it was forced opened somehow. Membrane making noise when you slide your fingers over the keyboard. Beside that, my third Pro1 looks fine actually though I've not been using it much so far. I'm hoping th

Sorry for the delays. We'll get to your request. We're going through a very long list of emails that have piled in the last couple of weeks following the announcement of the Pro1 X.

@Erik to the rescue! ☝️

So turns out the phone was sent back (went to the apartment building and talked to them directly on Monday), but the phone was sent back almost immediately after it was received, so it's been over 3 weeks since it was returned to sender. I put a ticket request in to fxtec on october 27th to let me know what the status was on the phone that was sent out, to this day have not been responded to on that ticket. I'm hoping the phone was properly returned in the end...

Sold!

Hello! I have a Pro1 with QWERTZ keyboard, it arrived only about a week ago, I used about 2 days, and now I'm looking for a new loving owner for it! There's nothing wrong with the phone, I just have too small hands and it's inconvenient for me to use, and I cannot get used to Android - I like iOS more than I thought... Price: 650 Euro I live in Hungary, but I ship abroad as well! If you're interested, please email me: [email protected]

We haven't gotten any word about batches, how many orders they have left, when they will be in general availability. Official or otherwise