Leaderboard

I too was a die-hard fan of the N900. 🙂 I am quite happy with my hybrid Lineage+Devuan system now, which provides almost everything my N900 could do, but you are right that there are limits (HW accelerated graphics, transparent FS access, ...) because of Android concepts standing in the way. Note that UbuntuTouch comes with very similar limitations: It too is designed primarily as a phone OS and copys some of Andoid's concepts. E.g. apps are individually sandboxed, native "phone" apps and "desktop" Ubuntu software live in separate worlds, the latter running in libertine containers wi

Right, Pro1 can be very handy to do real things like logging into a server and do what is necessary, which is very frustrating on any touch keyboards. However, the one and only real and well-working Linux phone I used so far which also had a keyboard was N900. Although Pro1-X will also come with Ubports, so some kind of a Linux ecosystem will exist, nowadays one have to have an Android phone because of other services, and as it is a very restricted system, it seems for me the very same well-working environment what N900 had is not working anymore if you don't want to bring another de

Yes and no. The Pro1 (and, by extrapolation, the future Pro1-X) can be set up as a quite OK always-carry-on GNU/Linux computer. I achieved that using rooted LineageOS + a custom-made Devuan chroot (see this thread for an entry point). Similar results can certainly be obtained using stock Android combined with a solution like Termux if you do not want to root, especially if a Un*x CLI is everything you really need. In fact, if you ordered your Pro1-X with UbuntuTouch you may (hopefully) be good to go pretty much out-of-the-box. None of these solutions breaks the "phone" functions in any wa

Hello, I am what we can call a power user on linux and do the vast majority of my work in a terminal (note with vim, email, rss…). I currently have my desktop computer at home, a laptop that I bring pretty much everywhere and my android phone. I am heavily interested in a phone with a keyboard and tend to hate android with every cells of my body. The question is, would the Pro X1 replace both phone and laptop in your opinion (or experience) ? Considering that : I am a linux power user especially in the terminal My laptop is an Acer Swift 3 with 4GB of RAM, an intel i3 and it w

My latest build (20210815) of LineageOS 16.0, including the 5th August 2021 AOSP patches, is now up.

Well, in that case there is really no need to go for a Pro1(X). The built-in keyboard is pretty much the defining feature of the device. If you're going to use a separate keyboard anyway, you'll find devices that are cheaper while having better mainline Linux support. Running GNU/Linux in a [ch,p]root of Android takes care of that. Networking is managed by Android and just works (tm) in the chroot system. For Termux, there are even extensions to use the Android location services from within GNU/Linux-programs. But, yes, UbuntuTouch can also be a solution (although GPS does not seem to

Of all the days to release the first official 18.1 build, they chose this one.

Theoretically, ACC/AccA has that function, it's called "charging power control" and it lets you set limits for both voltage and current. Problem is, so informs us the app, "unfortunately not all devices/kernels support this feature", and unfortunately I've had no luck getting this to work on the Pro1, either. Within the app, there's also no way to find out whether the device or the kernel is to blame... Another cool feature doesn't work with the Pro1, either: "prioritize battery idle mode": "This allows supported device to draw power directly from the external power supply when charging i

It seems like the best shot at it getting to work is if FxTec can do something similar to what @peter.s.fidelman described UniHertz did with AT&T to get the Pro1(X) whitelisted - I have no idea what it takes to do so (AFAIK it is not as easy to swap the IMEI on th Pro1, so most likely it would be to get existing IMEI-ranges whitelisted), but let us tag @Waxberry and @Erik and see if one of them can perform some magic here 🙂

Contact fxtec and hear if they got it as a spare part.

I disassembled phone - issue is with sensor itself, connector is fine, sensor overheats, it is possible to order new sensor somehow? Or maybe new back cover with sensor in it? Currently I disconnected sensor, all seems fine, guess I will have more battery life rn. Never used it anyways🤪

Its purpose is to bring the tap-insensitive display borders back from too wide to normal after a display replacement. If you need a display replacement and you get one from any other source than Fxtec (and Fxtec has been out of replacement units for some months now, also they're expensive as they include casing and front camera and other electronics), those replacement units will come with significantly wider tap-insensitive borders – to the extent of making it difficult to impossible to use some functions in some apps, even with the margin settings provided by LineageOS reduced to zero.

Hello, I'm using pro1 model, and today I found out, that fingerprint sensor overheats when phone is turned on. Overheating starts just after boot logo. Sensor is not working and temperature makes it impossible to touch. Is this common issue, is there any way to fix it? P.S. Phone is on stock firmware.

Thanks @EskeRahn. Doesn't help me in flashing the display IC, though, which it seems requires a running LOS 17.1 or 16.1 or stock Android...

Yes, today's build has the August 5th security patches but not the fix for the keymap bug. Trying to flash an older release triggers the rollback protection in the closed source components, and will force a factory reset to recover :-( Unfortunately we haven't found a fix for the problems with the touchscreen on other devices. This leaves us with a difficult choice, between the security patches and proper keymap support when the accessibility hook is enabled. I don't have any easy answer (other than building your own OS image), but the full details of the August security patches are here:

Users on other devices reported problems with the touchscreen after this change when using certain apps. Consequently, it has been pulled for now :-( If we can fix the problems with the touchscreen, it will be resubmitted and merged again. This means next week's build will have the old bug. If this will cause you problems, please don't update until the August security patches have been merged. With luck we will have a fix by then :-)

lineage-18.1-20210726-nightly-pro1-signed.zip on July 5 2021 security patch installed smoothly using OTA ....and the input issue is solved!! AMAZING JOB!! https://gitlab.com/LineageOS/issues/android/-/issues/3321 https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/312770/3#message-38cd89dc8bbd979418ae520841df099f05831d8a Special thanks to @EskeRahn and @Sean McCreary

Hi, i can't help for the office thing but I had the same trouble for the phone app. It looks stupid but there is no default phone app selected so it just don't know what to do with calls. Go in apps settings, select default apps and phone is probably empty and it shouldn't be, which was the case for me.

The instructions in the LineageOS wiki are really good. Just follow them and make sure not to miss any steps: https://wiki.lineageos.org/devices/pro1/build It is really not that hard. I have been self-building LOS 16.0 without issues for some time now, although I understand next to nothing about the internals of the build system ... Even if you have some Linux running on your main PC already, I strongly suggest to set up a dedicated VM with the latest Ubuntu LTS to stay as close as possible to the recommended environment. Ubuntu Server is sufficient btw. (and much easier on y

can someone help me setting up the development environment for building lineage OS for Pro1?