[ROM][DISCONTINUED] LineageOS 18.1 for Xiaomi Poco F1

[duttyend]

Always been an issue for me, and many others going back to LOS 17.1. Don't dismiss something just because you haven't experienced it.

You should provide more information for the maintainer and other skilled developers who could help: describe precisely the issue you are experiencing, provide hardware data regarding your fingerprint sensor (with the help of apps like 'Device Info HW').

You should also open a ticket (an 'issue') on GitLab

 

[TioCareca]

Always been an issue for me, and many others going back to LOS 17.1. Don't dismiss something just because you haven't experienced it.

True, i used to got 2 poco, and they got different hardware being screen and fingerprint sensor the ones i noticed more because in one of them almost all custom roms got problems with screen and fingerprint.
I sold that one and kept the one that is more compatible with custom roms because to fix one will break for the other, and seems the majority don't have problems so just a low number of units got different hardware and maybe for that devs don't bother to fix it for them...

 

[GioGr]

sorry for the crappy quality
but have this problem after the last 2 updates the pattern is so small that is really hard to enter my password,
my finger for size
changing from 3x3 to 4x4 etc does not change size but its all becomes a white blop

 

[sponk0]

July 3 update installed via OTA without any issues, looking good so far.

 

[Largamelion]

Has anyone gotten 'OK Google' to respond? I'm on the 26th build but can't get it to work. It's enabled but doesn't respond, not even when the phone is unlocked or in Android Auto. I used NikGapps Core and even flashed the Assistant add-on separately but it didn't make any difference. What's remarkable is that there are no requested permissions when I check the app info of Assistant. I'd expect it to request permissions for basically anything on the phone since it needs most of those to be able to work.

 

[Smultie]

I was just about to post about my intermittently working 'OK Google'.
It works for a short while after 'clearing all data' and setting everything up again. However, after a short while, it will stop working. The only way to get it working again is 'clear all data' and set it all up again.
Bit of a pain in the a**. Not sure if it's ROM related.

 

[ProTechShark]

On the latest version, all incoming calls are showing up as 'Unknown Caller' and not displaying the number. The issue isn't present on stock. Does anyone know what could be causing it?

The same problem also exists in pixel experience.

 

[Largamelion]

On the latest version, all incoming calls are showing up as 'Unknown Caller' and not displaying the number. The issue isn't present on stock. Does anyone know what could be causing it?

The same problem also exists in pixel experience.

Maybe a wild guess but have you checked if the phone app has permission to access your contacts?

 

[ProTechShark]

Maybe a wild guess but have you checked if the phone app has permission to access your contacts?

Had checked this before and the permission was set correctly. Even in that case it would probably display the number rather than the contact name, not 'Unknown Caller'.

 

[Retrial]

Had checked this before and the permission was set correctly. Even in that case it would probably display the number rather than the contact name, not 'Unknown Caller'.

Check if your phone app is set as default.

 

[Smultie]

I was just about to post about my intermittently working 'OK Google'.
It works for a short while after 'clearing all data' and setting everything up again. However, after a short while, it will stop working. The only way to get it working again is 'clear all data' and set it all up again.
Bit of a pain in the a**. Not sure if it's ROM related.

Anyone else?

 

[mathew_ver1]

Anyone else?

When that thing last happened to me on a different device, it was an issue with Google play services and got fixed with an update. Not sure if it's the same case.

 

[mathew_ver1]

Hey @bgcngm I hope you are doing fine.

Can you kindly look into the long withstanding fingerprint bug in multiple profiles. Also, there is something finicky going on with profile switching. Some random recently used apps just get launched automatically.

I would be glad if at least the not registering fingerprint bug in multiple profile set up gets some attention which is affecting all beyllium devices on Lineage and it's kind of breaking the workflow.

Let me know if I can produce some logs regarding the same but you can easily reproduce it.

Steps to reproduce-

Fingerprint bug-

1. Try to register fingerprint in a different profile and it fails

This bug is carried over from 17.1

Automatic app opening-

1. Just open few apps in both profiles and try to switch among profiles. Random apps get launched automatically.

This bug happens since 18.1

*I'm pretty sure these are reproducible among all Beryllium devices running Lineage in my testing. Tested using all clean flashed devices.

 

[ProTechShark]

Check if your phone app is set as default.

Phone app is definitely set as default

 

[5unny.Boa]

Hi,

updated today to latest (10.07).
I use hidden notch setting - Display cutout (developer options).
almost impossible to scroll and reveal the status bar now, only tiny spots on the sides are valid to scroll, if using apps in full screen, can't scroll it at all.
when i set the notch to default, it works fine.
some of the latest changes dunno which effected it somehow.

 

[deathontheshore]

Hi,

updated today to latest (10.07).
I use hidden notch setting - Display cutout (developer options).
almost impossible to scroll and reveal the status bar now, only tiny spots on the sides are valid to scroll, if using apps in full screen, can't scroll it at all.
when i set the notch to default, it works fine.
some of the latest changes dunno which effected it somehow.

I have the same problem. I can pull down the status bar only on a small center spot.
I have hidden notch set as well

 

[Em Kay]

I've been having these wakelocks constantly & they are in loop - these aren't letting my phone sleep, let alone deep sleep. It's seems usb related. Logs are attached. Pls, give me a solution.

thanks

 

[AtomicStryker]

Had the WLAN issue again this morning
(phone was constantly going from 4G to WLAN and back to 4G)
There was other devices working fine on the wlan router so i know it was probably not to blame

Tried restarting, TWRP cache clear, toggling WLAN and leaving it off for a little while, nothing helped.
Logcat of one such 4G - Wlan - 4G process:

POCO F1 Wifi connection failing - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

I ... think? ... the critical part is here:

07-15 08:27:00.352  2470 12705 W IpClient.wlan0: [IpReachabilityMonitor] WARN ALERT neighbor went from: null to: NeighborEvent{@3549768,RTM_NEWNEIGH,if=30,2a02:908:4c2:8fc0:9ec8:fcff:fe35:a15a,NUD_FAILED,[null]}
07-15 08:27:00.353   751 16746 W resolv  : SSL_connect ssl error =5, mark 0xf00a0: No route to host
07-15 08:27:00.354   751 16746 W resolv  : Validation failed
07-15 08:27:00.355  2470 12705 W IpReachabilityMonitor: FAILURE: LOST_PROVISIONING, NeighborEvent{@3549768,RTM_NEWNEIGH,if=30,2a02:908:4c2:8fc0:9ec8:fcff:fe35:a15a,NUD_FAILED,[null]}
07-15 08:27:00.370     0     0 D logd    : logdr: UID=1000 GID=1000 PID=16751 n tail=127 logMask=19 pid=0 start=0ns timeout=0ns
07-15 08:27:00.486     0     0 D logd    : logdr: UID=1000 GID=1000 PID=16753 n tail=127 logMask=80 pid=0 start=0ns timeout=0ns
07-15 08:27:00.584     0     0 I [wpa_su][68215049291][08:27:00.610766] wlan: [12702:I:HDD] wlan0(vdevid-0): Received Disconnect reason:3 WLAN_REASON_DEAUTH_LEAVING
07-15 08:27:00.585     0     0 I [schedu][68215061447][08:27:00.611399] wlan: [12691:I:PE] Deauth TX: vdev 0 seq_num 2259 reason 3 waitForAck 1 to 1c:b7:2c:f2:4f:62 from a6:dd:d7:0e:19:ef
07-15 08:27:00.586     0     0 I [schedu][68215072837][08:27:00.611992] wlan: [12691:E:tdls] tdls_process_reset_all_peers: 293: tdls objects are NULL
07-15 08:27:00.615  1501  9365 D WifiMemoryStoreImpl: Set cluster G3568eb7dad0223bf for W7dce54cb58874ed3: SUCCESS
07-15 08:27:00.630   915 12696 I WifiHAL : send oem msg of len : 80 to apps
07-15 08:27:00.599     0     0 I [schedu][68215322310][08:27:00.624986] wlan: [12691:I:PE] lim_deauth_tx_complete_cnf_handler: 2890: tx_complete = success tx_success = 0
07-15 08:27:00.603     0     0 I [schedu][68215403145][08:27:00.629196] wlan: [12691:I:HDD] wlan0(vdevid-0): disconnected
07-15 08:27:00.603     0     0 I [schedu][68215404492][08:27:00.629266] wlan: [12691:I:HDD] hdd_disable_rx_ol_in_concurrency: 1684: Disable TCP delack as LRO is enabled
07-15 08:27:00.631  1501  9365 D WifiMemoryStoreImpl: Set cluster G3568eb7dad0223bf for W3568eb7dad0223bf: SUCCESS
07-15 08:27:00.631 12702 12702 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=1c:b7:2c:f2:4f:62 reason=3 locally_generated=1
07-15 08:27:00.632  1252  1252 E cnss-daemon: wlan_service_update_tcp_rx_params: Unsupported throughput value 0
07-15 08:27:00.605     0     0 I [wpa_su][68215445788][08:27:00.631417] wlan: [12702:I:HDD] Disconnect reason: 3 WLAN_REASON_DEAUTH_LEAVING vendor: 0  LG: 1
07-15 08:27:00.636  1501  1697 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
07-15 08:27:00.636  1501  1697 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
07-15 08:27:00.640  1501  2051 D WifiClientModeImpl: ClientModeImpl: Leaving Connected state

There is some kind of SSL failure?? Or a timeout?


Also in true Schroedinger fashion the phone finally snapped out of it while i was reading this logcat. Its now connected to WLAN as it should be.

 

[Smultie]

Soooo.... is Mindthegapps still the only Google Apps to use with this ROM? There's some thoughts that this specific version causes the non-working Voice Match.
Would a different version work? If so: can I just flash that over my current install?

 

[Demodroid]

OpenGapps works fine as well. Not sure if you can flash it over MindTheGapps though.