tdm 2,322 Posted July 3, 2020 Author Share Posted July 3, 2020 (edited) Quick update... Got lineage to boot in enforcing mode today. Still need to tweak a few rules to get the fingerprint reader and lights hal to work. I'll probably have that done in a couple days. Then I'll start preparing for official lineage support. And of course, after that it's on to Q. Which should be pretty fast and easy. I'll be trying to get VoLTE working next week. @Hook has sent me a Verizon SIM to use for testing. Thanks! Edited July 3, 2020 by tdm 4 8 Quote Link to post Share on other sites
marmistrz 93 Posted July 4, 2020 Share Posted July 4, 2020 On 7/3/2020 at 5:55 PM, tdm said: And of course, after that it's on to Q. Expand You once said you only support addonsu, not magisk. addonsu has been dropped in Q, making magisk the de facto solution btw.https://www.xda-developers.com/lineageos-dropping-superuser-addonsu-implementation-favor-magisk-manager/ 2 Quote Link to post Share on other sites
tdm 2,322 Posted July 4, 2020 Author Share Posted July 4, 2020 On 7/4/2020 at 12:08 PM, marmistrz said: You once said you only support addonsu, not magisk. addonsu has been dropped in Q, making magisk the de facto solution btw.https://www.xda-developers.com/lineageos-dropping-superuser-addonsu-implementation-favor-magisk-manager/ Expand 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). 4 Quote Link to post Share on other sites
tdm 2,322 Posted July 4, 2020 Author Share Posted July 4, 2020 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. 1 6 Quote Link to post Share on other sites
Vince 3 Posted July 5, 2020 Share Posted July 5, 2020 Awesome! Nice to see SE Linux. Restored from scratch, only thing I notice is Microsoft Intune showing it as rooted, even though its not. I can work without that for now though, so far so good. Quote Link to post Share on other sites
SchattengestaIt 559 Posted July 5, 2020 Share Posted July 5, 2020 I have had quite a few system crashes since I installed the custom ROM, always resulting in hard reboots (with the FxTec logo). In most cases it happened while using Bluetooth for a webradio and Google Maps. Luckily no data was lost but it is still inconvenient. Which program could/should I use to create and read error logs or crash reports? Also I had some issues with the keyboard having no input until I restarted. Probably an issue with a software keyboard. Could a soft reboot (system only) be implemented into the power menu? I remember that it was on older LineageOS versions. If you want such recommendations on GitHub only, please tell me. Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 On 7/5/2020 at 1:17 AM, SchattengestaIt said: I have had quite a few system crashes since I installed the custom ROM, always resulting in hard reboots (with the FxTec logo). In most cases it happened while using Bluetooth for a webradio and Google Maps. Luckily no data was lost but it is still inconvenient. Which program could/should I use to create and read error logs or crash reports? Also I had some issues with the keyboard having no input until I restarted. Probably an issue with a software keyboard. Could a soft reboot (system only) be implemented into the power menu? I remember that it was on older LineageOS versions. If you want such recommendations on GitHub only, please tell me. Expand A logcat and dmesg live from the system as it crashes is best. Yes you can add reboot to the power menu. Quote Link to post Share on other sites
EskeRahn 5,520 Posted July 5, 2020 Share Posted July 5, 2020 On 7/4/2020 at 7:49 PM, tdm said: Test17 is up. The only changes are selinux rules and enabling selinux. Expand It installed smoothly here on both. 1 Quote Link to post Share on other sites
Wheeljack 212 Posted July 5, 2020 Share Posted July 5, 2020 On 7/5/2020 at 1:17 AM, SchattengestaIt said: Also I had some issues with the keyboard having no input until I restarted. Probably an issue with a software keyboard. Expand Noticed that happening too with every test build I used so far. Still unsure how to reproduce this, if it's a specific app or if it's just me and bad timing opening the physical keyboard while the virtual pops up. Quote Link to post Share on other sites
EskeRahn 5,520 Posted July 5, 2020 Share Posted July 5, 2020 On 7/5/2020 at 12:41 PM, Wheeljack said: Noticed that happening too with every test build I used so far. Still unsure how to reproduce this, if it's a specific app or if it's just me and bad timing opening the physical keyboard while the virtual pops up. Expand Odd. Both hardware and software keyboard works fine on Test17 here. Quote Link to post Share on other sites
Wheeljack 212 Posted July 5, 2020 Share Posted July 5, 2020 (edited) Like I said... hard to trigger. Usually both keyboards work fine. Just installed test17 without problems. SELinux shows as "Enforcing". Not seeing any new issues. Edit: Now that I'm trying to write from my phone, I notice the QWERTZ layout is shifted. Edited July 5, 2020 by Wheeljack 1 2 Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 On 7/5/2020 at 12:52 PM, Wheeljack said: Like I said... hard to trigger. Usually both keyboards work fine. Just installed test17 without problems. SELinux shows as "Enforcing". Not seeing any new issues. Edit: Now that I'm trying to write from my phone, I notice the QWERTZ layout is shifted. Expand 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). 3 Quote Link to post Share on other sites
acrux 56 Posted July 5, 2020 Share Posted July 5, 2020 (edited) On 7/5/2020 at 12:52 PM, Wheeljack said: Edit: Now that I'm trying to write from my phone, I notice the QWERTZ layout is shifted. Expand Confirmed here also. The upper row (numbers etc) is OK, but all other rows are shifted and yellow arrow (Fn) key does not always correspond to what is printed to the keys even if the shifted situation is taken into account. Edited July 5, 2020 by acrux 1 Quote Link to post Share on other sites
Hook 3,134 Posted July 5, 2020 Share Posted July 5, 2020 Test 17 installed smoothly. Everything seems fine (QWERTY). 1 Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 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. 4 Quote Link to post Share on other sites
marmistrz 93 Posted July 5, 2020 Share Posted July 5, 2020 On 7/5/2020 at 7:19 PM, tdm said: 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. Expand Can this be related to https://github.com/anssih/finqwerty/issues/17 ? Quote Link to post Share on other sites
EskeRahn 5,520 Posted July 5, 2020 Share Posted July 5, 2020 On 7/5/2020 at 7:19 PM, tdm said: 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. Expand Oddly Up/Down arrows seem to be swapped with Right/Left And a strange long delay/response-time when cycling through languages with Ctrl+Space Quote Link to post Share on other sites
Hook 3,134 Posted July 5, 2020 Share Posted July 5, 2020 (edited) On 7/5/2020 at 8:00 PM, EskeRahn said: Oddly Up/Down arrows seem to be swapped with Right/Left Expand Yup, was just typing up my discovery of the swapping of the arrow keys when you posted. Edited July 5, 2020 by Hook Just being more specific 1 Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 On 7/5/2020 at 7:54 PM, marmistrz said: Can this be related to https://github.com/anssih/finqwerty/issues/17 ? Expand If it started happening with the selinux build, then yes. Otherwise no. Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 On 7/5/2020 at 8:00 PM, EskeRahn said: Oddly Up/Down arrows seem to be swapped with Right/Left And a strange long delay/response-time when cycling through languages with Ctrl+Space Expand That's another thing, the keyboard idc file isn't properly labeled. That disables the arrow change with orientation. Quote Link to post Share on other sites
hermite 5 Posted July 5, 2020 Share Posted July 5, 2020 Is it possible to get the stock camera on Lineage? AFAIK gcam won't make use of the dual camera. Quote Link to post Share on other sites
tdm 2,322 Posted July 5, 2020 Author Share Posted July 5, 2020 On 7/5/2020 at 10:05 PM, hermite said: Is it possible to get the stock camera on Lineage? AFAIK gcam won't make use of the dual camera. Expand Does the lineage camera app not work? It's probably possible to copy snapdragon camera to the device. 1 Quote Link to post Share on other sites
EskeRahn 5,520 Posted July 6, 2020 Share Posted July 6, 2020 On 7/5/2020 at 11:12 PM, tdm said: It's probably possible to copy snapdragon camera to the device. Expand Simply pulling the apk and side-loading will not do the trick, it just keeps closing on launch, without any dialogue ever appearing. I guess it is dependent on something? 1 Quote Link to post Share on other sites
JooJooBee666 84 Posted July 6, 2020 Share Posted July 6, 2020 (edited) On 7/4/2020 at 7:49 PM, tdm said: 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. Expand @tdm Are you going to push the changes to the repos any time soon? I'd like to test here but build my own. Edited July 6, 2020 by JooJooBee666 Quote Link to post Share on other sites
tdm 2,322 Posted July 6, 2020 Author Share Posted July 6, 2020 On 7/6/2020 at 6:36 AM, EskeRahn said: Simply pulling the apk and side-loading will not do the trick, it just keeps closing on launch, without any dialogue ever appearing. I guess it is dependent on something? Expand It probably needs to be a system app. 1 Quote Link to post Share on other sites
Recommended Posts
Posted by tdm,
Pointer to new thread on official build
Recommended by EskeRahn
5 reactions
Go to this post
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.