[Galaxy S II Q&A, Help & Troubleshooting] rINanDO:
First of all, Please don't use !!!!!! It looks like you offend people!! Even people who tries to help you!

Secondly, the issue isn't an issue of i9100. It is an issue of the ROM, meaning on all devices. A device maintainer maintains his devices when something changes in the ROM (changes in LineageOS and Android google sources) to keep it up to date.

Thirdly, have you ever connected with your dummy passwords to the Wifi Access Point? Or are you just trying to find "stupid" bugs?

There is a validation mechanism depending on the used security type of the Access Point which is auto detected

WPA2 PSK => minimal password length is 8 WEP

WEP40/104/128 => valid lengths 5, 13, 16 or HEX-values valid lengths 10, 26, 32 and ofcourse 0-9 A-F as allowed characters

If you want to help, try to configure your WIFI access points and verify LineageOS's behavior when configuring with WPA2 PSK/WEP.

Also look in JIRA if the issue is already reported. I saw this issue last week about wifi-password for example:

https://jira.lineageos.org/browse/REGRESSION-912?jql=text ~ "wifi password"

---------- Post added at 06:46 PM ---------- Previous post was at 05:55 PM ----------

Here are my comments on your reported bugs.

1) When you will get an incoming phone call or receive a message then your Galaxy S2 will ring and vibrate but the screen can be fully dark without any notification about the call.

I'm aware of this symptom. The problem is memory and running background processes. Having to much apps installed (Facebook, instagram, snapchat, etc) causes the OS to memory swap when the phone-app must be active. ART uses more memory than Dalvik.

2) Some programs can not work with an external SD card. They can start to work with it after reboot or after few reboots only.

Which programs? The solution is probably using emulated storage.

3) Galaxy S2 with Lineage OS 14.1 becomes hot with a big battery drain for some significant period of time after every reboot. So, rebooting trying to make installed apps work properly you can just quickly fully empty your battery and finish on it.

This is a known issue and can't be resolved. Android 7.1.2 takes more boottime than 4.1.2. The CPU is constantly at 1200Mhz during boot and several minutes after boot because of apps starting up. Our 1600mah battery can't cover this 'boot'-drainage multiple times. It needs 'resting' time to stablelize (like a car battery). Try the app Battery Log to see how the CPU at max speed is pulling the voltage down.

4) The famous FX File Explorer app does not work with the default internal folder 'Documents'.

When you will delete a file on an external SD card this app may not delete it but just rename the file to hidden only (a name started with a dot).

There is another file manager app implemented in the ROM but its interface seems very poor and uncomfortable.

I don't know what the issue with this App. A possible issue could be that we don't use emulated storage

5) Sometimes there is impossible to connect to a password protected WiFi hot-spot due to the link 'CONNECT' in the WiFi menu remains inactive (gray coloured) after password typing 8 symbols or more. This bug appears constantly at a connection with some password protected WiFi hotspots only. And it can become a serious unexpected trouble if you are on the go and in a need to connect to a new hot-spot.

This is by design. Validation depends on used security WEP/WPA2 PSK

6) Camera1 and Camera2 api do not provided correctly. So, camera apps are buggy.

For instance, the famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. Yet there are another troubles with A Better Camera app.

The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.

A great of effort has been made to make the legacy Camera api's work in the framework for legacy devices like our i9100 since google dropped its support. It is not perfect and probably never will be. Expect same issues later on in Android O.

7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. This bug does not exist in a landscape mode.

Use small display view. We have a very low-res phone for 2017

8) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu and activate this hidden option, which is uncomfortable.

Moreover, external apps for phone call recordings does not work properly with this ROM.

Was there ever a automatic recording option in the ROM? We need to investigate some apps why it fails recording.

9) The famous SuperSU root tool does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.

It is still an issue I think. Please see http://www.lineageosrom.com/2017/01/download-supersuzp-and-su-removalzip.html

10) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.

Our old kernel needs some patches, but it is unclear which patches.

11) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.

12) The ROM developers do not fix even well known simple bugs like described here at the points 5 or 7.

Seems they also do not welcome for public bug reports in proper topics on the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of their buggy ROM. And I did started this topic for stop it.

I do not know what their purpose is exactly.

But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.

The another short trap messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious using.

I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost 1 month period installing latest Lineage OS 14.1 updates and Resurrection Remix 5.8.3 and I decide that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.3.[/QUOTE]

I'm using 2 S2's as daily drive. One for work and one private. I don't have many big apps installed and use my s2 also as car navigation using waze or Google maps. Yes sometimes you have to be patient for a 6 year old device.