tdm

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.

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

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.

Well, perhaps we have different ideas of "very warm"? I think 30c is rather cool for a phone during active use and charging. I would consider "very warm" to be closer to perhaps 50c.

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

I've never observed any phone get very warm during navigation usage while plugged in. And I have done it quite a lot. For a couple years this was the main way my phone got charged every day, during my commute to work and back. I have never done this with the Pro1, but I cannot imagine it would be any different. Certainly it should not get warm enough to thermal throttle.

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?

Sorry, it should be fixed now.

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

Well, test22 has been up for over 4 hours and I haven't heard any complaints about connectivity or power usage yet. Does anyone have any show stopping issues on test22 that would prevent going official?

test22 is up. Changes: Fix connectivity issues and power drain (intervigil). Set display density to match stock (npjohnson). Increase statusbar height in landscape (npjohnson). Tweak camera button behavior (npjohnson). Customize fingerprint setup image (npjohnson). Various cleanup (npjohnson). Note the increased statusbar height was done mainly because Nolen's device is an early prototype and has touch sensitivity issues near the edges. This does not affect production devices AFAIK. However, it does also improve readability of the status

Oh, okay then. I guess nevermind.

Awesome, thanks. You are definitely running a different modem version than I am. The QCOM baseline for all those versions are the same. That's expected. But for some bizarre reason they set the OEM version string to the build box hostname. There are additional strings. In particular if you just do a straight strings on the modem partition, you should see a block near the end that looks like JSON and starts with Image_Build_IDs. Could you locate and paste that? EDIT: And please include Metabuild_Info and anything else around that which looks interesting.

Ah, this is very interesting. Ethan believes that the new power code is causing the modem subsystem to crash when getting the WLAN stats. But if yours is not crashing, perhaps your modem version is different than the rest of us in some way. Could you run this command and send me the resulting modemversion.txt? You will need root permissions, so first run "adb root". You also need to replace the ## with your boot slot suffix. You can get your boot slot by "adb shell getprop ro.boot.slot_suffix". adb shell "strings /dev/block/by-name/modem## | grep VERSION" > mode

Ethan believes that he has tracked down the problem (hopefully the only one). I'll build and test and hopefully have a test22 build on the morning (12 hours from now).

FYI ... for better/quicker battery drain info, look at this file: /sys/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-02/800f000.qcom,spmi:qcom,pmi8998@2:qpnp,fg/power_supply/bms/charge_now_raw I'm not sure what the units are, but I'm charging my battery to 100% now to get an idea. It's roughly one million at 52% charge. You can check that value, do something to test (like leave the phone to sleep) for about 10 to 30 minutes, then check the value again. Divide by the seconds elapsed and you have a drain rate. You could even script it. Edit: the va

Good to know, thank you. That implies that the qcacld updates are fine and it is Ethan's power stuff that is causing problems. On the other hand, @npjohnson is seeing the WiFi stabilize when he takes test21 and backs out the qcacld updates. So the culprit is still not entirely clear. Unless perhaps both are causing issues...?

Nobody said anything about test20 having any issues, but it also had the qcacld merge (the WiFi driver update in the kernel). I'm wondering if someone could download and flash the test19 and test20 boot images and see how they work with the test21 build.

Actually, scratch that. I've got other stuff I need to do today and Nolen just received his Pro1 an hour ago. So I'll let him have a go at this for a while. He's already got several things fixed, including fixing the display density, enabling the camera button by default, and fixing the fingerprint location image in the setup wizard. He should be able to track down the WiFi and power issues also.

Please take a look at the kernel history on my github. There was no rebase between test20 and test21 so the kernel history is linear and both tags appear in a simple log. The qcacld merge was complete for test20.

Every OEM is supposed to "tune" the panel for proper display colors at the factory. This takes very specialized and expensive equipment. It is a one-time procedure for a given panel, and the results are encoded into the stock software to make the display look better. It is possible (I would say likely, even) that IdeaLTE has not done this. Or perhaps they did it for a previous iteration of the display panel but switched suppliers and didn't do it again for the new one. There isn't really a way to know without having FxTec contact IdeaLTE and ask. This is also likely why the di

I'm going to go over Ethan's changes today. My first thought is to remove all the power related changes and just take the cleanup changes until we test more thoroughly. I'll post later after I discuss with him.

I'll be going over the issue list. I think Nolen is going to do 17.1 actually.

Okay so I got all the code cleaned up reasonably well and all my tests checked out. So Nolen is currently importing everything into Lineage as I write this. It should be done shortly, and then I will add the pro1 to the list of official Lineage 16.0 builds. I'm not sure exactly which day the first official build will roll out. After all of that is done, I should probably create a discussion thread for official Lineage 16.0, and of course I'll be immediately starting work on 17.1. That should hopefully only take a few days, and then I can do a short testing period before switchi