tdm

Couple updates, especially for the developers out there... I'm working with one of the upper level Lineage guys on getting the device/kernel officially imported. He has made quite a few comments and suggestions for cleaning and improving the device tree. So the lineage-16.0 branch on my device tree is going to be rebased and rearranged quite a few times in the next couple days. I tagged test18 so it doesn't get lost. Said Lineage guy is actually interested in the Pro1 and I will probably send him a prototype unit. So that's even more development support. Which is g

@SteffenWi that install page is apparently not correct. I'll look to see if there is a better one available. I did not write the page, it is a template that is linked in the wiki code. There are several different ones to choose from. @Wheeljack I'm hoping that I can get an official TWRP working soon. If not, I can switch out the TWRP stuff for Lineage Recovery stuff.

Can I get some folks to review this before I submit it...? https://harryyoud.co.uk/lineage-previews/280778/4/devices/pro1/ Thanks!

I have not used CDMA in several years precisely because I like the freedom of moving my SIM to the phone I choose, when I choose. But I believe the mule method is the most used on VZW. Because the Pro1 is a GSM phone, you will need to rely on volte for voice. So you will need to make sure that is functional on your account. I'm not clear on how SMS is handled.

I received the SIM from @Hook today and, just as I mentioned yesterday, adding the missing VoLTE properties fixed VZW voice calls. I'll include these in the next build, but if you are impatient and willing to tinker here's what you need to do: 1. Ensure adb is running as root, "adb root". 2. Mount partitions read/write, "adb remount". 3. Get the /vendor/build.prop file from the phone, "adb pull /vendor/build.prop". 4. Edit the file and add the following lines at the end: # VoLTE persist.dbg.ims_volte_enable=1 persist.dbg.volte_avail_ovr=1 persist.dbg.vt_avail_ov

Google has this to say... Use battery saver on a Pixel phone ... scroll down to "What changes when battery saver is on". And ignore the part about squeezing the phone to bring up the assistant, as that's obviously a hardware feature.

It's not secret. My factory restore tool should do the trick. But, as I recall, the problem @D1ggs had was that he locked his bootloader while on non-stock and the bootloader unlock flag was not set. This is a one-way trip and needs EDL to fix. My initial attempt at fixing this involved a custom executable, and we couldn't get that working easily. I've since helped another user successfully. I ended up making a very small package that can be flashed with the factory restore tool that manually sets the bootloader unlock flag.

[tease] A wild 17.1 branch appears... https://github.com/tdm/android_device_fxtec_pro1/tree/lineage-17.1 [/tease]

Great, thank you. So you are confirming that the WiFi in the setup wizard does not work in enforcing, but it does work in permissive. Is that correct?

So I'm wading through all the commits to bring 16.0 up to 17.1 and I found a bunch of VoLTE props that are missing in 16.0. I probably removed those before I realized that VZW folks actually used VoLTE (the other major carrier that uses it is in India, which is probably why I removed those props). I would find a VZW customer to work with to test VoLTE with these props set, but I should have a VZW SIM shortly anyway. Long story short, looks like VoLTE will probably be working Real Soon Now.

I've started the process of making this official. Someone took the time to actually review the device stuff, so I am fixing that now. Should have a mostly final build in the next day or two. I also need to create lineage wiki pages for the device which is always a couple hours of fun tracking down the device specs, finding a sample picture, writing instructions, etc.

http://files.nwwn.com/android/pro1/lineage-16.0-pro1-test18-boot-permissive.img Just flash this with fastboot and see if the setup wizard can connect to wifi. Thanks!

Both nova and trebuchet worked for me. Can you get a log? Anyone else having issues?

Okay thanks. There may be something in selinux that is preventing it. We have two options: I can try to reproduce it here, or you can download a permissive boot image to try. Which do you prefer?

test18 is up. The only changes are fixing device specific selinux rules (for eg. fingerprint, keyboard, touchscreen margins, etc.) Again, this is on the verge of being submitted for official Lineage builds. Please report any issues. Also pushed up code changes to github. Enjoy!

Shortly. I'm working on fixing the device specific stuff right now. Then I'll make a new release and push up the changes.

It probably needs to be a system app.

Does the lineage camera app not work? It's probably possible to copy snapdragon camera to the device.

That's another thing, the keyboard idc file isn't properly labeled. That disables the arrow change with orientation.

If it started happening with the selinux build, then yes. Otherwise no.

I started looking into fixing the keyboard layout boot code and noticed several other things are broken. Basically all the custom device stuff, from the keyboard to the display margin to livedisplay and so on. I'll get that all cleaned up for the next build. Probably tomorrow.

That would be selinux blocking the script which sets the keyboard layout at boot. I'll try to fix that shortly. In the meantime, you may set it manually as root (either in a root terminal shell or a root adb shell).

A logcat and dmesg live from the system as it crashes is best. Yes you can add reboot to the power menu.

Test17 is up. The only changes are selinux rules and enabling selinux. This is getting dangerously close to submitting for official builds. Please test and let me know if anything is broken. I've verified it boots and the lights hal and FP reader work, but not much else.

Yes I'm aware of that. I'll be trying to fix su once I move to lineage 17. I'm still running 16 on both my devices (pro1 and 1+6t).