tdm 2,322 Posted July 27, 2020 Author Share Posted July 27, 2020 39 minutes ago, FlyingAntero said: F(x)tec Pro1 is in the news! LineageOS 17.1 adds support for the OnePlus One, Sony Xperia XZ2, XZ2 Compact, and F(x)tec Pro1 XDA did not understand something so don't get too excited. We are on LOS 16.0 so no LOS 17.1 (Android 10) yet. I believe that it is coming in future but we need to hold our horses for some time. Nice! Note that 17.1 will be relatively easy with 16.0 working. It should be ready within a week or two. Nolen and Ethan are making great progress. 3 5 Quote Link to post Share on other sites
SCΛRECROW 57 Posted July 27, 2020 Share Posted July 27, 2020 A week or 2?! That's awesome. OTA also installed properly for me with successful Magisk preservation. 2 Quote Link to post Share on other sites
itsdevilslettuce 85 Posted July 27, 2020 Share Posted July 27, 2020 Downloading and installing the official OTA now! 😄 Forgive my ignorance but with these OTAs, do they also update the recovery? 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 27, 2020 Share Posted July 27, 2020 4 hours ago, Wheeljack said: OTA update went fine for me as well. Have set it to high priority, that cut down installation time to about 30 minutes. Do you mean "Prioritise update process" in preferences? I have set that too. Quote Link to post Share on other sites
Vince 3 Posted July 27, 2020 Share Posted July 27, 2020 (edited) Any seeing this? Chrome is blocking the latest build, but the build from last week is downloading just fine. Don't think I've seen this anywhere else before. Downloaded it just fine on Edge weirdly enough. Edit: Downloading from official page: https://download.lineageos.org/pro1 Edited July 27, 2020 by Vince Quote Link to post Share on other sites
DieBruine 397 Posted July 27, 2020 Share Posted July 27, 2020 (edited) I've been running LOS for a couple of hours now. Still configuring a lot. Apparently I missed the part about having to root and delete my fingerprints. I was hoping that was sorted with a fresh wipe and format. So later in the evening I will flash SU and delete the data. I have noticed the rotation issue not happening 🙂. But I do have three questions. 1 Can I turn on auto cap? 2 Can I change the "Shift" timing? WHen I press SHif, this happens a lot... The second letter also capitalized. 3 How do you combine :+e to get ë. The only combination keys I was able to find are ˋ'ˆ to combine into èéê. THe DUtch language has some annoying ë in it... (US-int configured btw). 4 Forgot about this one. I was unable to get ADB working over USB C. Is this something I should figure out, or is it a known issue? And one more thing, fastboot oem unlock does not work anymore now it's "fastboot flashing unlock". Maybe someone could update the instructions? ANd I can confirm a little lag in screen animations/transitions in the launcher. I'm using Nova LAuncher and rotating door animation. The first is swift. Everything after that is not. And how is that auto cap is working during this latest edit!? Edited July 28, 2020 by DieBruine Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 27, 2020 Share Posted July 27, 2020 8 minutes ago, DieBruine said: 3 How do you combine :+e to get ë. The only combination keys I was able to find are ˋ'ˆ to combine into èéê. THe DUtch language has some annoying ë in it... Still: Alt-U, followed by the wanted base later. but could be language layout dependent. I will remove the posts in the other thread to avoid confusion 🙂 Quote Link to post Share on other sites
itsdevilslettuce 85 Posted July 27, 2020 Share Posted July 27, 2020 I don't know what's going on but I'm having fingerprint issues on LineageOS. It wasn't recognizing any touches plus every time my phone reboots the fingers were no longer saved. I went back to stock (had a bunch of stock OTAs) made sure it wasn't my sensor. Thankfully its not, everything works fine and data stays after reboots. So I figured lets try out Lineage again. Fresh clean install of the newest build and recovery (20200727) ... The sensor is responding and recognizing quite well; but, data is still lost after reboots. 😕 I was thinking about going back to the OTA test build v2 that I was running just before I flashed official Lineage. (cant remember if it was working properly or not) Quote Link to post Share on other sites
tdm 2,322 Posted July 27, 2020 Author Share Posted July 27, 2020 10 minutes ago, itsdevilslettuce said: I don't know what's going on but I'm having fingerprint issues on LineageOS. It wasn't recognizing any touches plus every time my phone reboots the fingers were no longer saved. I went back to stock (had a bunch of stock OTAs) made sure it wasn't my sensor. Thankfully its not, everything works fine and data stays after reboots. So I figured lets try out Lineage again. Fresh clean install of the newest build and recovery (20200727) ... The sensor is responding and recognizing quite well; but, data is still lost after reboots. 😕 I was thinking about going back to the OTA test build v2 that I was running just before I flashed official Lineage. (cant remember if it was working properly or not) The fingerprint daemon, which reads the actual fingerprints, is closed source. However, I did change the fingerprint HAL to alleviate some of the false reads when you accidentally touch the sensor. That may be what is causing problems. You should be able to effectively circumvent the authentication delays in the HAL by setting this property: persist.vendor.fingerprint.auth_delay = 0 1 Quote Link to post Share on other sites
Wheeljack 207 Posted July 27, 2020 Share Posted July 27, 2020 1 hour ago, EskeRahn said: Do you mean "Prioritise update process" in preferences? I have set that too. Yes that one. Weird. Had the phone on the charger and didn't bother it with other tasks. I took the time from "Install now" after downloading and stopped when it prompted to reboot. Quote Link to post Share on other sites
Craig 1,435 Posted July 28, 2020 Share Posted July 28, 2020 14 hours ago, DieBruine said: How do you combine :+e to get ë I'm too lazy to confirm on phone, but on my pc using us-intl-altgr its right_alt " (right_alt+shift+') then e. That leads me to believe on pro¹ us int'l it'd be " then e (shift ' then e). Quote Link to post Share on other sites
Craig 1,435 Posted July 28, 2020 Share Posted July 28, 2020 14 hours ago, DieBruine said: Can I turn on auto cap? Not yet, but there's already a github issue about this missing setting. Quote Link to post Share on other sites
Craig 1,435 Posted July 28, 2020 Share Posted July 28, 2020 (edited) 14 hours ago, DieBruine said: Apparently I missed the part about having to root and delete my fingerprints You can do that without rooting by using adb root (enable in developer options) - if adb is working! Edited July 28, 2020 by Craig Quote Link to post Share on other sites
Craig 1,435 Posted July 28, 2020 Share Posted July 28, 2020 14 hours ago, DieBruine said: fastboot oem unlock does not work anymore then how did you unlock? Quote Link to post Share on other sites
Wasmachineman_NL 99 Posted July 28, 2020 Share Posted July 28, 2020 Strange issue: no sound over BT with LineageOS. Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 28, 2020 Share Posted July 28, 2020 23 hours ago, EskeRahn said: ..... (it has gone up a substantial 50MB, so would be interesting to know what has been added) I noticed that the list of changes page is completely blank (less the cosmetic layout stuff) https://download.lineageos.org/pro1/changes/ Anyone with any info on the extra 50.29 MB? Not that the size matters in it self, I'm just curious what has been added? (Last time we had a substantial jump in the package size it was the gapps that were accidentally included, And I wonder if something similar is the case this time too) Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 28, 2020 Share Posted July 28, 2020 1 hour ago, Craig said: I'm too lazy to confirm on phone, but on my pc using us-intl-altgr its right_alt " (right_alt+shift+') then e. That leads me to believe on pro¹ us int'l it'd be " then e (shift ' then e). see earlier... ☺️ 15 hours ago, EskeRahn said: Alt-U, followed by the wanted base later ...In no layout is selected. On the us-international it is the combo Shift and Sym+' followed by the base letter Quote Link to post Share on other sites
FlyingAntero 812 Posted July 28, 2020 Share Posted July 28, 2020 24 minutes ago, EskeRahn said: I noticed that the list of changes page is completely blank (less the cosmetic layout stuff) https://download.lineageos.org/pro1/changes/ Anyone with any info on the extra 50.29 MB? Not that the size matters in it self, I'm just curious what has been added? (Last time we had a substantial jump in the package size it was the gapps that were accidentally included, And I wonder if something similar is the case this time too) You can find changelogs for every build from here. https://www.lineageoslog.com/16.0/pro1 lineage-16.0-20200727-nightly-pro1-signed.zip Quote 3 days ago pro1: Set surfaceflinger phase offsets 2020-07-24 18:54 UTC (android_device_fxtec_pro1) 3 days ago pro1: time-services: Start time_daemon service from common rc 2020-07-24 18:21 UTC (android_device_fxtec_pro1) 7 days ago repopick: Use upstream instead of revision to determine branch 2020-07-20 17:22 UTC (android_vendor_lineage) 7 days ago pro1: Enable energy aware scheduling by default 2020-07-20 14:17 UTC (android_kernel_fxtec_msm8998) 7 days ago pro1: Disable qcacld power stats 2020-07-20 14:16 UTC (android_kernel_fxtec_msm8998) 7 days ago drivers: staging: qcacld-3.0: Make power_stats a Kconfig option 2020-07-20 14:16 UTC (android_kernel_fxtec_msm8998) 1 Quote Link to post Share on other sites
DieBruine 397 Posted July 28, 2020 Share Posted July 28, 2020 1 hour ago, Craig said: then how did you unlock? Stupid 🥴, I should have posted that "fastboot flashing unlock" is the new command. I think this was changed a couple of months ago in a newer release of adb tools. ALT+U doesn't work anymore for me since I went to LOS. I also changed the keyboard layout to English, that did not help. And as I stated, I think it should work as Craig described. That's how it works for ' , `and ^. But not for " . Also when I press SYM+ I get a lot of the characters in shortcuts (ö ß Ü) but not the one that is impossible to do yourself, ë. I just connected a BT headset to my Pro1 and I have sound over BT. Try disabling APT-X HD under BT settings if you have an APTX-HD enabled headset. I haven't tested mine yet, will test it today. My GrapheneQ didn't work while using APT-X HD. I do have an APT-X HD receiver that did work on stock. I will post the results here later this morning. Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 28, 2020 Share Posted July 28, 2020 3 minutes ago, FlyingAntero said: You can find changelogs for every build from here. https://www.lineageoslog.com/16.0/pro1 Thanks. So anyone know how we can have that link added here https://download.lineageos.org/pro1/changes/ ? Quote Link to post Share on other sites
FlyingAntero 812 Posted July 28, 2020 Share Posted July 28, 2020 1 minute ago, EskeRahn said: Thanks. So anyone know how we can have that link added here https://download.lineageos.org/pro1/changes/ ? Actually, now the changes are there but it does match with the other site that I linked. There are 2 extra changes from other devices (LeEco S2 and Samsung universal 7880). 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 28, 2020 Share Posted July 28, 2020 3 minutes ago, DieBruine said: ALT+U doesn't work anymore for me since I went to LOS. I also changed the keyboard layout to English, that did not help. And as I stated, I think it should work as Craig described. That's how it works for ' , `and ^. But not for " . Also when I press SYM+ I get a lot of the characters in shortcuts (ö ß Ü) but not the one that is impossible to do yourself, ë. It matters what "English" you selected. I can not find it in neither proper English nor US. But if you de-select all (yes silly) Alt+U works. and if you select the "international style" it is the three key combo. 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted July 28, 2020 Share Posted July 28, 2020 13 minutes ago, FlyingAntero said: Actually, now the changes are there but it does match with the other site that I linked. There are 2 extra changes from other devices (LeEco S2 and Samsung universal 7880). Thanks. A brief look does not seem like any of them adding anything I would expect to be of substantial size. We are talking +8% of the total LineageOS so can hardly be just minor adjustments... Is something just not packed the same way, or have we got an unwanted side-load of some kind? Is it perhaps the mentioned Samsung and/or LeEco stuff that are actually included in the package? Quote Link to post Share on other sites
DieBruine 397 Posted July 28, 2020 Share Posted July 28, 2020 (edited) @Wasmachineman_NL So I tried a couple of BT settings. Sony WF-1000XM3 = AAC 16-bits 44.1KHz. Ora GrapheneQ = SBC 16-bits 44.1KHz - This should be an APTX-HD headset. CSR8675 BT = AAC 16-bits 44.1KHz - This should be an APTX-HD / APTX-LL receiver/transmitter VW BT module (original) = sound, but didn't check yet which codec. Toggling HD-media does make a difference, sound is more compressed with the option off. But, the system never shows APTX nor the Qualcomm logo. So I would say, yes we do have a HD BT connection. But it's APTX and certainly not APTX-HD. APTX-HD is 24-bits SBC. And my Pro1 shows a 16-bits SBC connection when connected to my Graphene. Haven't found a tool yet to force APTX-HD handshake when pairing. I can select all options under Developer options. But when you exit and return to the settings the values stated above are shown. I also tried all versions of AVCRP. That has no effect in my case.@EskeRahn Yep, that did the trick, forgot about that. Disabled the keyboards and now it works like it did on stock. Back on LOS, I am unable to get notification lights working for Hangouts. Even with custom notification lights enabled. Any suggestions? Edited July 28, 2020 by DieBruine 1 Quote Link to post Share on other sites
_DW_ 628 Posted July 28, 2020 Share Posted July 28, 2020 OTA went perfectly fine here as well Performance has definitely improved since last version things are a lot slicker in the UI. Was trying out some games I used to play and have come across one that consistently gets a package parse error. https://play.google.com/store/apps/details?id=com.sevenpirates.infinitywar&hl=en_US Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.