tdm

Yes, they are available to copy. It's pretty trivial to do this. Oh, and I forgot to mention config files. Those can affect behavior also. But I think I've got all the relevant config files in place and up to date. Also note that Lineage is free to take changes to improve performance that aren't in stock. Particularly with WiFi and GPS. For example, on a previous device I owned, stock only enabled 2.4ghz on WiFi but 5ghz worked perfectly fine. So I enabled it.

In theory Lineage should provide equal performance as stock for all components. If it does not, let me know and I will look into it. Some of the sub-systems that you mention (gps, wifi) have partial open-source components and partial closed-source components. If for some reason the open source components do not work as well as stock, I can look into it. But I am not aware of any such issues at the moment. Some of the sub-systems are pretty much completely closed source (camera, cell radio). These should certainly perform identical to stock. With that sai

I haven't heard any complaints. Logs would be a good first step.

I will not comment on whether stock is subpar or not. That is a subjective call. But I will say that stock is pretty much just a basic BSP build with a few changes tossed in here and there (like landscape mode). This is something that a developer team at any other company would use as a starting point for their stock software. It is not a finished product that was meant to be used by consumers. There are reasons for this, as I have mentioned -- IdeaLTE is a hardware company and FxTec cannot afford a software team. But folks who choose to use stock should know about this situat

I can certainly do a build for you. But be aware once the device is submitted for official Lineage builds, I will stop doing my builds and you will need to find someone to do the patched build. (Or just stick with my last build, as 16.0 is in maintenance mode). Where can I find the microg patch for Lineage 16.0?

Yes, correct. But certified is not the same as registered/authorized. When the device is not registered/authorized, you are completely blocked from the Play Store. Certified is probably related to SafetyNet stuff.

My understanding is that in R (which will surely be LineageOS 18), Google has implemented some sort of cryptographic authenticator using the TEE for safetynet attestation. In layman's terms, this means the validation is happening in a place that cannot be easily seen or modified, and thus cannot be easily faked as it is now. But keep in mind I am not an expert on SafetyNet -- I don't use it and generally don't care about it. I only read a short post by John Wu on the subject.

My initial AOKP build won't boot. I swear, this device has given me trouble every single step of the way. I've never seen any device cause more trouble in my 6 years of doing custom ROMs.

No, LineageOS does not pass SafetyNet as shipped. It passes everything else though (eg. Play Store / Play Services will see the device as registered and authorized). Folks that use custom ROMs and need SafetyNet compliance usually use magisk. I can't say much else on the subject, as I don't need SafetyNet and never installed magisk.

Thank you. 🙂 For paypal please see here: https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/page/19/?tab=comments#comment-44659

Quick update: @EskeRahn I'll add LiveDisplay back for the next build. @auvo.salmi something happened with my DNS and it lost all the IPv6 entries. I have restored them and it should be working again. I asked about gapps persistence in Lineage Slack and the answer was that gapps persistence only works for OTA on A/B devices, not with sideload. This is because nobody has been able to figure out get it working with sideload. So, as you are surely aware by now, gapps needs to be flashed after updating. I'll try to fix this soon. But this won't be a problem

Lineage does not have gapps, so an official Lineage build could not be used for stock. It would be technically possible to build Lineage with the approved gapps for a stock replacement, but this would violate the contract with Google. Unfortunately, IdeaLTE is a hardware manufacturer and FxTec is too small to have a software team. So the current situation where stock is a basic no-frills system while Lineage is a much nicer alternative will surely persist for quite some time.

That is for when play services detects that your device is not registered, eg. the build fingerprint does not match any registered/approved devices. Basically when Google didn't get their money from certification. Lineage will be registered, as it uses the stock fingerprint. So that is not needed.

test11 is up. The only change is fixing FM radio.

Lineage by default will not. Folks typically use magisk for this.

Got the FM radio fixed (listening to it now). Will push that up and do a new build soon. If anyone is interested in details... The first problem is that the AOSP "FMRadio" package is broken and not used, there is a QCOM "FM2" package that is used instead. I've noted this before. Second, there are some libraries that must be specified to be built which I was missing. Thirdly, there is a library that seems to be in the open source code but explicitly set to not build without the BSP for some reason so that needs to go into the proprietary blob list. Fourthly, was mis

@puppymang the software fixes are slowly trickling into the stock ROM. But things are moving rather slow for stock due to various reasons. @FlyingAntero is correct, LineageOS is moving much faster and will surely provide a better experience for you at the moment. In particular, there is a setting for edge margins on the screen and the audio crackling has been fixed.

@oliviersenn6 I am not sure what could be happening. The EDL package should replace most everything related to booting the device into Android. There are some exceptions (such as the Factory Reset Protection flag). But I don't see how flashing a Lineage boot image followed by another EDL flash should fix things. In any event, it looks like your device is working again. I will keep watch for this issue in the future. Thanks for the report.

Greetings! I hope you are doing well. This is definitely a bug. I have filed an issue for it. I have not used themes in quite some time, so I cannot say. In any case, I doubt this would be specific to the Pro1. It is most likely lacking in LineageOS. Did you try "System -> Buttons -> Buttons and Layout"? There are several options in that menu, including "left leaning" and "invert layout". Thank you. :)

Possibly this commit? I got it from another device while I was trying to get things working, and then I deleted it when I saw that 1+5/5t does not have it. I am not sure if it should be present or not.

The advantage of official lineage is that you get automated nightly builds with the current code. That's not such a big deal for 16.0 since it's in de-facto maintenance mode, but it will be really nice for 17.1. It also means that more people will see it and use it, since not everyone reads this forum. The big advantage to AOKP has always been more options over Lineage. And there's also unicorns and swagger, naturally. 🙂 Yes, AOKP is probably past its prime, but I've a particular fondness for it. I've been using it for about 8 years and developing it for about 6. I worked with its

I'm going to be pushing for official Lineage support over the next few days. That means fixing all the known bugs (not necessarily enhancement requests, but of course I'll get to those also). So if anybody is experiencing any issues that aren't in the github tracker, please add them ASAP. Otherwise, I'm going to assume FM radio and selinux rules are the last release blocking issues. Also FYI... as soon as Lineage 16.0 goes official, I'll start working on 17.1. That should be a breeze compared to initial bringup. Oh and I'll probably be making an AOKP build this week. 😄

test10 is up. Changes: * Fix audio crackling. * Update fingerprint mitigations.

I've gotten VLC with OpenSL ES initially working by taking audio_policy_configuration.xml from 1+5/5t. There are quite a few diffs, so I'm narrowing it down now. If you want to try this out yourself and report back, do the following: 1. Remove or rename the directory /vendor/etc/audio. This contains the currently used audio_policy_configuration.xml file. 2. Update /vendor/etc/audio_policy_configuration.xml with this one. I am particularly interested to see if this fixes audio issues in other apps. Note: audio_policy_configuration.xml is search fo

The keyboard fix is in the kernel (at least the parts you likely want -- I don't know yet what else they have changed). So you need to update your kernel. I doubt much has changed in the ramdisk, if anything, so you can probably use the boot image directly from the update. The only caveat is that is the kernel modules (including wifi driver) are located in /vendor and may not load with the newer kernel. So you may need to update those also. And that would further prevent you from taking any OTA updates. I don't have an updated boot image or kernel modules handy, as I haven't i