Leaderboard

Some good news: The v2 seems just as lean on the battery as the Test22 (This is from the unit without GSM) The dip at the right side is all the install mess described above, but that apart it seems pretty parallel after a few hours sleep.

I'm happy to report Verizon still working great on test22. I finally rooted with Magisk this time around and restored all of my apps and SMS/call logs. Everything is still working! I've tried powering the whole thing off too, several times. Maybe it's all fixed now and all that awaits me is more Lineage goodness! 😁 I've made a pretty good number of calls, texts as well as MMS messages by now. It's almost too good to be true! I have to go to the About screen now and then and make sure I'm still on Lineage and just didn't have this wonderful dream!

Ahh yes the history of LineageOS. Seems like forever ago when I was flashing CyanogenMod. Man, this phone really does hit the nostalgia!

Precisely. Google makes Android and publishes the sources. The LineageOS team takes those sources and fixes bugs, adds features, etc. Of course it is more complicated in practice and I left out all of the history. But that is the takeaway.

It can take very good photos even in low light conditions using GCam mods, so it is possible...

Probably Nolen's. I'm taking a break for a bit to do other stuff and he is still fresh and energized.

After some four or five hours of driving with navigation running, the Blackberry Priv I once had usually shut itself down due to overheating. This of course happened when I already was right inside that big destination city where I was completely lost without navigation – having to seek a parking bay only to wait for the damned thing to cool down, already being late for the appointment, of course...

Which legislature gives you the right to demand getting your phone before them, just because Fxtec "promised" at a date when the world was a different one than it is today? Envy and greed. "i want my plaything before others who ordered later, otherwise I can't be happy with it anymore". Even if those others are just a vanishingly small number which have no effect at all on the rest of the shipments. Even if those vanishingly small numbers are important for the manufacturer to even stay in business, for which things like those unboxing videos coming from around the whole world actually may

The intent is always for updates to keep you addon packages. But when the A/B system arrived, the lineage folks only got this working with OTA. They haven't yet figured out how to make it work with sideload on A/B devices. So yes, if you switch to OTA updates, your addons will stay. And no, you don't need any particular version except the correct one for your Android version. You will need to install the first official build via sideload. After that, OTA works and keeps your addons.

A bit more explanation on my web server: I was looking at setting up a Lineage OTA server yesterday because this whole download a zip, sideload lineage, reboot to switch slots, sideload gapps thing is a pain. Nolen pointed me to the official lineage updater project on github and I was trying to get it working. It uses a bunch of fancy modern stuff (eg. redis) which I don't particularly like. Then I observed that the API for the OTA server is extremely simple and I could write my own easily enough. So I did just that. Took about 2 hours. After doing all that I remov

Alright it's officially official. Now we wait for the first build. I don't know what day that will be, but it will be within 7 days. https://github.com/LineageOS/hudson/commit/0233cb5e039e98dd7fda2e20a01ecac2362ec268

I think I'll give bit a try. I don't need Verizon, it has just kind of turned into an obsession. 😁

I did not change any settings at all. In fact, I avoided the *#*#4636*#*# menu altogether. It seems touching anything in there is an immediate death sentence, even if you put it back. I understand the pain, it's took me several days working on it when I can and I'm still not all set back up yet. I don't think you'll have any luck without flashing back to stock first but I could be wrong. I took all the updates but the only one that really seems to matter is the 20191111 one. After that you should be able to make everything work on the stock ROM, then flashing Lineage hopefully will work

As far as I know the keyboard foil is mounted with heat and&or adhesive, so my GUESS would be that your specimen had had this foil mounted with a little too low amount of adhesive and/or is placed ever so slightly wrong with a bit of tension in the foil, that then popped up due to the bump. I would try gently heating with a heat-gun (or hair drier) to attempt to make the adhesive more liquid, so the keyboard can be pushed in place. and then let the device cool back to room temperature, and see if it stays in place You could also try contacting support, and hear if they have a bet

I use PocoPhone F1.

I wouldn't call them good at all, even using some of the GCam mods. Unless maybe I missed one that did miraculously adjust for the crappiness? Which one are you referring to?

Better is subjective. But there are many fixes and features. Not sure what your issue is with the camera. EdgeNull is not needed, I added my own solution. Don't know what Audipo is. If you are interested, give it a try. You should not expect people here to give you a sales pitch.

FWIW, I compiled and flashed a new build with TheMuppets and Lineage OS device/kernel repo. Everything seems to be working fine.😎 @tdm As far as the 17.1 stuff goes, which repos should I be watching?

I think it would work just fine, and I believe someone in here have actually done it, unless my memory fails me. BUT note that the off centre placement of the USB-plug might make it hard to place in a suitable way, as they most likely will come with a flat cable.

After a whole hour it finally continued. And failed to boot.... Suggesting me to retry the boot or do a factory reset... The retry failed too... I will try a manual flash, and see if that fixes stuff... That fixed stuff, and it booted (almost) normally except launching the qx1000 install wizard - that I just skipped.

Oh I let it do the update, it is almost finished with the "Preparing for first boot" stage.... 🙂 If it is still there I will try to boot into recovery and sideload, and see if that fixes it 🙂

This is kind of off topic, but something to think about for future testing of 17.1, perhaps. I got my OTA server running and tested it with a full (not incremental) update. Took roughly 45 minutes from the time the download completed. Google intentionally makes this process low priority because you are expected to be able to continue using your phone normally while the update installs. But there is an updater option to increase performance which helps some. It would be much faster, both for download and install, to do incremental updates. But incremental updates req

Would just like to confirm: With test22 WLAN connection is stable and energy usage is reduced compared to test20 and obviously test21.

Something is up already: https://wiki.lineageos.org/devices/pro1 👍 Edit: since July 18th there is a thread at Lineageos reddit.

I just uploaded the package for the 2020-07-07 factory firmware. Enjoy!

Not necessarily a bad guy, but a little touchy. 😉 Look, yes, communication is not F(x) Tec's strong suit. And, yes, they often don't get things to happen when they say they will (in large part because, being a very small company in the UK, they don't have full control of the whole operation-- which is also part of why they hesitate to communicate). However, we are just a user forum. None of us work for F(x) Tec and we don't know any more than you do, so why get upset with us. You can try invoking @Erik who does work for F(x0 Tec. I would speculate that the shops had pre-orders as

Hello there Pro1 experts! 🙂 I have accidentally dropped my phone on the wooden floors a few times, no hard bumps mostly from our living room table on to the carpet actually. The problem is that I have noticed the the keyboard bulges out a bit, just at the edge. (The edge facing you when having the keyboard slid open) Now, what would be a good way of putting the keyboard back into place. I've tried gently nudging the plastic with my fingers and nails to push the keyboard down and latch on to the notch, with no success. I wouldn't want to be putting too much force into it. Sh

The camera is still shitty, especially in low light. No software is going magically fix this turd of a CCD we got.