[ROM][UNOFFICIAL][10.0.0][raphael] LineageOS 17.1

[JanMM]

Android Keyboard (AOSP) Spell Checker does only work with one language. If multiple (system) languages are selected and spell checker is set to use system languages, it will only use the first language. Word suggestions will change, when changing the keyboard language, but spell checker will not. Therefore everything written in the second language will be underlined in red and tapping them gives you suggestions in the first language.

Hi all, new member here!
Was the issue @reddek reported above ever replicated or resolved? Basically, I am observing exactly the same problem.

I just installed the latest version (17.1-20210117-NIGHTLY-a3xelte) on a Galaxy A3 (2016), and installation was really painless. I'm using English, French and German on a daily basis, and selected all 3 languages in the System > Languages and Input > Languages menu. I use the Android (AOSP) keyboard. I can switch the keyboard between languages, and the spellchecker while I'm typing checks in the correct (current) language. However, anything written in a message that is not German (the main language of the OS) will still be highlighted as a typo. So it seems there are two spellcheckers at work, one from the keyboard and another one for text already written, and the latter does not switch languages correctly. I have used several Android systems and this never happened to me before. Any idea how to fix this?

I'm happy to install different keyboards or spellcheckers, but so far have not succeeded in resolving this.
(I this thread is not for Samsung, but this is the only place I found so far that discussed this)

 

[bialabs]

I'm not sure if this is a bug or not but when I have DC anti flicker mode enabled together met automatic brightness the brightness is changing every 5 or 6 seconds when it is dark.

Does anyone face jittery auto brightness in low light conditions ?

Same here
Anyone can help?

EDIT
Tried a reset of Adaptive Brightness. For now the auto brightness is working as expected. Let's se in the next days

 

[Master One]

The issue is known and the solution is also known. If you disable 4g calling, the problem should be solved.

I am facing the same issue on a POCO X3 NFC, strangely only for one of the two used SIMs.

Deactivating "4G Calling" solves the issue, though this is not a solution but only a workaround!

I don't want to miss the "Enhanced 4G" / VoLTE features, so what's the deal with this problem, which seems to be a general Xiaomi issue?

 

[bacardischmal]

@abhishek987
Your release works pretty good as daily driver.
Is it possible to release a LOS 17.1 with the latest security updates, it's almost 4 months old.

Thanks
bacardi

Bump

Is there a way to update the release?

 

[Robbo.5000]

Bump

Is there a way to update the release?

The dev only really uses xda to post new releases, chances are this will never be read. He operates mostly on telegram, you need to find out which telegram group he communicates on. I don't use telegram so I don't know which group it is.

 

[bacardischmal]

The dev only really uses xda to post new releases, chances are this will never be read. He operates mostly on telegram, you need to find out which telegram group he communicates on. I don't use telegram so I don't know which group it is.

Oh ok, i dont use Telegramm, maybe some who read this and is in the channel can ask him for a build to get the security updates.

 

[Kevindiepenmaat]

Afaik this does not get any updates anymore because of the version

 

[Apurba99]

can someone help me install magisk and root it? After I install magisk apk, the ramdisk show NO. After reading some forums and sites, I found that if ramdisk say NO then we have to patch the recovery.img, and then flash it in twrp. So where can I find the recovery.img?