Leaderboard

Maybe some clarification on the whole supported/unsupported part in the LAOS channel: "Supported" means that a phone is officially released by the LAOS project and deemed fully working. Since this is obviously not the case yet, the pro1x is still "unsupported". Doesn't mean no one is working on it. I have no idea *if* someone is working on it, but that message is not prove that no one is working on it. Just wanted to clarify this, based on observations on how lineageos works/communicates (and cyanogenmod before them)

I just added the microG repository to F-Droid with no problem at all. Seemed to work identically to native Android.

I asked my buddy if he could make me a test (low infill) for the back and top bumpers. If/when he does and we work out any kinks I'll point him this way. I like the idea of that case.

After using my used Pro1 for over half a year I am getting my first hardware issues. The first keys start to not work when pressed normally, I have to press them quite hard to get the key. It started with the 'c' but I now have four or five keys that often do not get registered when pressed. The 'f' and 'c' being the most obvious keys. Is there any kind of replacement or fix for hardware keyboard issues? Also, am I the first one encountering this problem? I haven't found any post in the forum about this (or I failed at searching).

So, I sent a message to Nova support, and this is their answer: The Digital Wellbeing app can't be uninstalled, but it can be disabled.

yup, and this is the only outer difference between the two models, The Pro1 is almost flush, the Pro1X protrudes slightly

Same problem here, but I wonder me if it's 100% hardware ? When it happens (trying aaa eee bbb aaa eee bbb sequence with normal press) dmesg says (when missing a letter) : "aw9523b_irq_handler: enter" two or three times and doesn't go with "key press", which is related (if I understand correctly) to i2c GPIO expander But yes when I press very hard it doesn't happen, either when I write slooooowly, wich could be the same here... Not sure at this point but really annoying

I just tested and on my Pixel 2XL (LinageOS 18.1) I do not get anything from the finger print scanner when it's not being requested, so I am thinking this is a change they could make in software/firmware...or wait until LinageOS comes to the phone.

Thanks a lot. That was it. I wasted a lot of time because I thought the reason is maliit, mce or libstick. I will try adams kernel soon. Is it necessary to make a backup of the dtbo partition to keep it possible to re-install the stock android? Furthermore , I realized that video playback isn't possible if the UT kernel is used (any app starting a video crashes). Will a replacement of the kernel fix this or are there bugs on the userdata image to be solved?

Glad that you managed to reflash! You should be able to reliably reach fastboot mode directly by powering down the device and then holding down [Vol-], while plugging in an USB cable.

A new build of good-old LineageOS 16.0 for our good-old Pro1 (835) is available at http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 2022-08-23. It contains backported AOSP security fixes up to patchlevel "1 August 2022". I bumped the Android security string to reflect that. Seemingly, people are slowly losing interest in Pie. While the AOSP patches since May have been backported and have undergone basic testing (by me and on other devices), they have not been merged into the official LOS 16.0 tree yet, due to pending code review. While I a

The Pro1X i got my hands on is not retail, but would be interesting if some that got retail version of both, could post some sample images.

Ok, but as "everything was finished" in 11/2021 - that should include LineageOS and Sailfish as well - as those were - next to ubuntu touch - the systems promised to run from the get-go. And if there are hardware quirks to fix, how does this occupy the software guys? It just does not make any sense. I mean, let's face it. The 662-nerf was ouch, but not the end. Computational performance on cellphones hit "decent enough" in 2015. Since then it's "oh look - we have 23 lenses!!" and more power "just because". My most graphic-intense app is Google Earth - I guess the 662 is fine for 99