Leaderboard

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

Battery stamina MUCH improved with 22. Here 20, 21 and 22 within the last few days;

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

When the official build appears, you may download it and attempt to install. If it fails, it will likely be due to a signature check. You can avoid this by deleting /data/system/packages.xml. There should not be any other issues with installing the official Lineage build.

There is only one thing which might be necessary. There is a system file in /data that may need to be deleted. And I am not sure even that is required. But I will let you know.

7 days?! That's like nothing in terms of waiting for things around here 😅 Jokes aside; I am so happy to see this. Amazing work to everyone involved and many thanks! 👍

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

🥳Excellent news, great job tdm, mccreary, npjohnson, and all ya'll beta testers out there! 🎉

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

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

Well I just had to flash test22. So far all voice/SMS/data is working just like it should on Verizon. I'm not going to root or install many apps and see how it does.

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

Oh indeed, but battery charging above 30°C should be avoided if possible. Oblivious it is not a sharp limit. from https://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

I drive around (well, not so much lately) with the Pro1 plugged in for Android Auto and have never had a problem with overheating (warm, yes) or the phone shutting down in the car, Back when I was getting resets It did happen in the car once or twice, but never was overheating a reasonable suspect. By the way, on Lineage, I haven't seen a spontaneous reboot since @tdm said he removed the tap-to-wake elements left from stock. I really can't imagine why I'd ever go back to IdeaLTE stock at this point. Curiosity, maybe. It would be a quick trip if I did. 😉

Yes I never had wiped moving forwards between your test versions. Only when I tried to move backwards. 🙂

I probably know how to reproduce and fix that issue. If I type FN + ALT (FN = yellow diagonal arrow key), the keyboard input is disabled (at least in text fields where sticky shift works). Typing the thing again keeps it disabled. The third time I type that combination, the keyboard works again. I think that the emoji keyboard (disabled on my phone) is the reason and we are switching through two emoji keyboards without seeing the. Given that you get ghost input every now and then, I could imagine that we trigger this key combination without noticing. I haven´t tried it yet when the i

Sadly, I just tried and Verizon is still not working here on Test 22 for me. I assume being rooted isn't a problem (which would be a deal breaker that would keep me on AT&T anyway). I really don't need Verizon anymore, but I'm puzzled and I still have a couple of weeks left on the SIM. 😉

some frogs are green

The phone was not warm. Apart from rebooting in case of bad WiFi way back, my phone has rebooted previously while using Maps. In this case even more so. My phone holder is mounted on the vents. It was cooled the whole 2000km on both trips. No way my phone heated up 🙂 . Airco was on all the time. Both holder and phone could not have been above 20 degrees.

I have not had it reach the point of booting, but I certainly had it go way beyond 30°C. Both with an aPple S6-, a BB Priv, a Samsung S8- and the Pro1.

Generally speaking it should be the opposite. You should never need to wipe data when you upgrade to a newer build of the same OS unless something is messed up. The only time you should need to wipe is when switching OS (eg. stock to lineage). I did initially install test22 without wiping and it worked fine except for an issue with adb starting late. However, I did wipe shortly after (for the first time in months!) so that I could test the WiFi during setup wizard. EDIT: Sorry, I misread. Yes, you are correct. Going backward to an older build is not supported and m

Yes, I build test22 with exactly what is in official Lineage repos right now. I can't imagine what could be wrong with the recent code. It works for me, and I haven't heard anyone else complain about this sort of issue. Perhaps you should do a clean rebuild using the Lineage and muppets stuff? And in any case, can you get a logcat?

I think you misread. I already did go back. I was on a custom build of 21 when everything went to shit. Rolling back to a custom 20 got things back up. 😎

I have not noticed random reboots since March but I have not been travelling due COVID-19 situation (I am working from my home). That makes me believe that the root cause of the issue is the same with some Sony devices. I mentioned that earlier. All random reboots that I have faced have happened during travelling.

It's really crazy how it seems to work. If you reflashed to stock and did the one OTA update to the 20191111 it would probably work, at least for a little bit. I'm kind of scared to restart or power cycle my phone. I miss root, for one thing I can't restore all my apps but I'm going to just rock it for a few days and see what happens. The VoLTE did seem to fix outgoing calls. Before only incoming worked, outgoing never worked. It's just that it doesn't seem to last too long and I have no idea why.

Tested muting, speaker, numpad tones - everything worked for me.

Yeah, sorry, we have to adhere to LineageOS's charter - and Wi-Fi dropouts definitely violate that - the good news here is that with our findings today, I'm confident we can ship ETA Soon^TM. And good to hear 🙂 I tried like 10 different values and picked the one that was least intrusive to other users, and allowed those of us with early prototypes to interact with that area as well. Additionally, from a UX perspective - it doesn't warp test as badly on the curve now in landscape, so that's something. Untitled-1.psd OT: On the fingerprint image, if anyone has recomme

System adaptive brightness is on. Fx Service Light sensor adaptive brightness is off.

@SchattengestaIt To counter the green you need to add red and blue while leaving green at zero, it should be purple. It's ARGB. You need to click on the custom colour link to be able to enter the value yourself.

Sorry all, it has been sold.

Since I simply do not use the device I am willing to sell my FXtec Pro 1. The device was installed, but never left the house. In total it has not been actively used more than a couple of hours. A screen protector was put on it as soon as it left the box, and I throw in a second screen protector. It comes in the original box, and I can send photos of the state of the phone. If anyone is interested, please let me know here, and we can find a way to transfer the ownership (I could put it on Ebay for example).

just for conclusion, I replaced the screen and it's working again now 🙂 Just a hint: don't forget pulling of the plastic sheet at the back of the screen at the speaker/camera, realized it after it was glued in...

Try a Moto Z 😄 My Moto Z not only got hot enough to throttle, but it turned itself off because it overheated while using navigation and charging it at the same time. When I tried to turn it back on the aluminum housing almost burned my fingers. Probably didn't help that it was summer and no AC in the car. But the Moto Z can get very hot easily.

I emailed back to support team. They said tracking was sent to me by the end of this week so I wanted to check it was on the schedule. However, they said it is going to be by the end of NEXT week again.