Leaderboard

Lots of posts in the last few hours so I'm going to do a bulk reply. here... @Wasmachineman_NL @DieBruine the Pro1 has not licensed aptX and the required aptX libraries should not be installed. Therefore aptX should not work. I am not familiar with the meaning of "HD audio" as it relates to BT. Perhaps someone can enlighten me? @EskeRahn @FlyingAntero the new build is larger because Nolen added "firmware" to the build. I'll have to look into this to see exactly what was added and where. Also, the changelog does not update exactly in sync with the builds. I'm not s

So in case anyone is interested, here are the firmware partitions included: abl, bluetooth, cmnlib, cmnlib64, devcfg, dsp, hyp, keymaster, mdtp, mdtpsecapp, modem, pmic, rpm, tz, xbl These should be all of the A/B partitions excluding boot, system, vendor. The shipped images should currently match the 2020-07-07 OTA. And by the way ,this was all @npjohnson ... I did not really want firmware shipped because it's kind of pointless right now -- all stock builds have functionally identical firmware and that is likely to remain the case indefinitely. But Lineag

I did see this in Firefox as well, but ignored it for 3 reasons: These things tend to produce a lot of false alarms particularly with unfamiliar software. I'm not using the file on Windows but installing it on a phone and I don't believe a windows browser knows what is harmful on a phone I assume this is the same file that has gotten good reports after being installed OTA. I sideloaded it and it is working fine. 🙂

Its android based so the fact LineageOS is now working means it should be possible but depends if anyone is interested might be worth reaching out to them

Some of the AOSP apps can be replaced with google apps if you use Opengapps. Browser is an example, it can be replaced with chrome. Just an idea if you're already a gapps user.

Yes, a new keymap file is the easiest solution. The instructions you linked are for editing the kernel keyboard mapping. Let's call this the keymap file for clarity. This is not the same thing as the Android keyboard character map file(s). Let's call those kcm files. You could probably use either to change your keyboard combinations. I suspect that changing the kernel keymap would be the "more correct" way to do it, but it is a bit more difficult to work with than kcm files. Shifted combinations can be edited in kcm files, yes.

.... and the headline now correctly says LineageOS 17.1 adds support for the OnePlus One, Sony Xperia XZ2, XZ2 Compact, while F(x)tec Pro1 gets LineageOS 16

"Mistakenly" sent out a message to try to get people to re-sign their 2-year contracts in the midst of a pandemic where connectivity is crucial... totally a mistake. I'm sorry but I have zero faith in any US/Canadian carrier not trying to screw with their customer base on a daily basis.

Just got in my car to test it for you. Phone calls function is working. Have you tried toggling this under BT settings? Under LOS I now have the option of HD Audio. I didn't have that option under stock. Also I did some additonal testing on sound quality. When connected to my Pioneer XDP-300R (Android 5), I see the APTX logo and I definitely enjoy much higher bitrate than when connected to the Pro1. Also tried listening to Youtube on my company phone (Samsung A8). The A8 sounds better, less compressed, than the Pro1. Same headset of course.mymmb My car is from 2008, but the BT module

@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-bit

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.

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).

You can find changelogs for every build from here. https://www.lineageoslog.com/16.0/pro1 lineage-16.0-20200727-nightly-pro1-signed.zip

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

Indeed, but the keyboard drivers of the Pro1 are not part of stock AOSP. So @tdm is not messing with the Android stuff here. On the contrary he is trying to make the Pro1 hardware to work better with the hardware-keyboard support present in native android. AND doing this in a way so what is printed on the keys are still respected when US Qwerty is selected. And this also allows for selecting any of the other native android key-layouts. SURE there might be custom layouts that does a better job for a specific language than what the default android offers in LOS. But on the contrary to what Stoc

I managed to fix the problems with GPS by clearing all caches. Now I'm getting a fix within 5-10s, GPS, GLONASS and Beidou is used. # rm -rf /data/cache # rm -rf /data/dalvik-cache

Not exactly strange. For calls to work on LTE, it needs VoLTE, which is a different standard. But so far I've seen, it has been a complete shitshow in North American networks. A lot of times it's only on a subset of their own phones sold that works. North American carriers do this kind of bullshit all the time. Device whitelisting, slowing or outright not providing updates, you name it. They seem to only care about locking you into a new contract every 2 years with "new" hardware. Whereas my 4 year old, North American market BlackBerry Priv which has been out of support and pro

It seems that first official Nightly build is available 🙂 - https://www.lineageoslog.com/16.0/pro1 Edit: here also, https://download.lineageos.org/pro1

I've been thinking about what you said here and I think it's a misperception of the Pro1 (although I won't pretend I'm entitled to speak for Chen). I don't think the Pro1 was ever marketed as a "premium" phone and it isn't. First, notice that their marketing motto is "Function is Key." The Pro 1 is much more a descendant of the Nexus phones than a Pixel, iPhone or Samsung phone. It is a very solid midrange phone (with good specs) strapped onto a premium keyboard. My theory is that they really had to do that or we would be looking at a $1200 phone. They poured everything into the keyboard (

Battery stamina MUCH improved with 22. Here 20, 21 and 22 within the last few days;

Alright it's officially official. Now we wait for the first build. I don't know what day that will be, but it will be within 7 days. https://github.com/LineageOS/hudson/commit/0233cb5e039e98dd7fda2e20a01ecac2362ec268

If you want to get technical, it's a present day t-rex, but close enough!

Et voilà!

woof?

here is one of my two "dogs"

Why have large dog when you can have many tiny ones instead?

Ah... dog food... 😇

My doggo looks cute but it never listens...

Here a cropped and reduced one from the Pro1. holding two Chukit balls - and the thrower for them he pulled from my hand...