tdm

Thanks I'll take a look shortly.

Sorry, maybe you should wait for things to settle. I just finished finalizing the trees and Nolen is importing them to Lineage now.

I haven't seen it hang on bootanim in months. Nolen did commit a couple of changes since test21 was cut, maybe those are causing it? I noticed the adb thing also. Ethan's init stuff must have caused it. Very frustrating for tracking down issues. I'll have to fix it soon.

I am pretty sure that building does not automatically clean files. So you should probably delete your out/target/product/pro1/{root,system,vendor} first. Then sync up again .. I think I neglected to update my lineage-16.0 branch yesterday. But it's definitely up to date now.

Sounds like the livedisplay manifest issue. Make sure you sync to test21 and you don't have a framework_manifest.xml file in your device tree. EDIT: Yup, looking through your log... 07-14 11:07:49.126 601 601 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IAdaptiveBacklight/default in either framework or device manifest. 07-14 11:07:49.126 601 601 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IColorEnhancement/default in either framework or device manifest. 07-14 11:07:49.127 601

@Hook and @bmccrary .. just spoke with @npjohnson and he's going to try VoLTE on TMO when he gets his device (Thursday).

A good first start would be to get a normal logcat (adb logcat > log.txt) and a radio logcat (adb logcat -b radio > radiolog.txt). Anyone else on VZW with experiences to share?

Interesting. Please watch performance. It should not be noticeably worse than before but it should be slightly better on battery usage.

The display size change would be from this commit. See, I told you Ethan was good. 😄

The msm8998 is definitely capable of stereo recording. But I don't know how the Pro1 has it wired up. You would probably have to ask @Waxberry.

Sorry I don't really do binary apk hacking. I only work with source code.

I can't say much about stereo recording, because I'm not really into that. But I can say the software is .. well .. let's just say rather unpolished and leave it at that. But the hardware is generally very good. I highly recommend giving Lineage a try. It makes the software experience much better, in my (biased) opinion.

Okay so FYI ... I have sent off my spare Pro1 to Nolen. I had been keeping it on stock software for the purposes of downloading new stock updates and doing side-by-side testing. So now that it's gone, I'm going to rely on someone to tell me when there's a new stock release. And, unless someone wants to volunteer [hi @EskeRahn! 😀], I'll "get" to backup, wipe, reinstall, copy off the bits, and restore for each update.

test21 is up. Changes: * Update blobs and string to stock 2020-07-07. * Switch back to custom livedisplay implementation. * Import changes from Ethan Chen (thanks to Nolen for doing this). Note the changes from Ethan are too extensive to enumerate in a few lines. There are some cool performance improvements along with lots of under-the-covers cleanup.

Not sure exactly what you are asking. All updates within the same major version (16.0, 17.1) will keep all add-ons. But when you update major versions (say, 16.0 to 17.1) then you will need new gapps. The su add-on isn't available for 17.1, yet anyway, but you would also need an updated su if/when it is. When you switch from my test builds to official Lineage, you will need to do a manual install of the official zip just like you install/update my builds. After that, the OTA system is engaged.

Same update procedure as always. Once you have Lineage, you don't need to bother with the boot img. Reboot into recovery. Sideload the update. Reboot recovery (to switch slots). Sideload gapps, su, etc. Reboot to Lineage. And as soon as this goes official (later this week?) the OTA system will do the updates for you, just like stock. And it keeps all your addons (gapps, su) through the updates.

Don't think I've seen that bug reported for lineage. But then again, if the issue is not specific to the pro1, some lineage developer probably saw and fixed this in lineage before the first pro1 ever rolled off the assembly line.

Apparently Ethan Chen[*] has a Pro1 and he's been hacking on it lately. So Nolen and I are going to be massaging the device code to incorporate his changes. Nolen says that Ethan has incorporated a lot of cool stuff to make the device perform better. [*] Who is Ethan Chen? He is arguably the best active Lineage device maintainer out there. I worked with him at Cyanogen, and he is truly a whiz at doing device stuff.

Okay I'll look into it when I get a chance.

This is a Lineage bug, not specific to pro1. You can file a bug in either my device project so I can track it myself or the official Lineage bug reporting system.

Thanks. Given the timing of your message, I don't think you got the latest device tree change (the livedisplay switch). You might want to re-sync and make sure you are up to date with the test20 tag on all three projects.

test20 is up. This is pretty much the final code that will be imported into the official Lineage trees unless any issues are found. Changes from test19: * Update kernel to latest code from Qualcomm and IdeaLTE. * Update device blobs and strings to latest stock (2020-06-20). * Switch to standard livedisplay implementation. * Add WiFi MAC address setting from stock.

Vendor is not part of roomservice, you need to update that manually.

All the renaming is complete for sure. How is roomservice broken? I may be rebasing the device tree again, but that should not break your roomservice. Likewise with the vendor blobs, though that is less likely. I just finished rebasing the kernel and updating it to the latest code, so that should not change again unless I broke something.

test19 is up. Changes: * Code cleanup for official submit to Lineage. * Add VoLTE props to fix VZW. Please verify everything works properly. FYI, this is my remaining TODO list before submission: * Verify WiFi and BT MAC addrs are set as in stock. * Regenerate vendor blobs from latest stock. * Fix poor kernel commits (fix stuff, fix more stuff). * Verify WiFi works on clean install. * Go over remaining oneplus specific stuff in rc-files, sepolicy, etc. Additionally, here is the updated proposal for the wiki pages: https://