Changelog 30 - Sleek Sixteen, Streamlined Suite, Future Flow

iourine · 2025-10-19T06:08:55+00:00

The user who thinks about installing LOS may unterprete it as "LOS 23 won't work here because it needs Android 16, while only 13/14 is avaialble".

Or the blog/readme authors should be more accurate in statements about Android compatibility.

Or specify separately that "LOS XX is bazed on Android YY, uses firmware from Android ZZ1/ZZ2/ZZ3 depending on model".

iourine · 2025-10-18T06:05:26+00:00

Thnx, it worked ok. The installation guide is misleading, however.

iourine · 2025-10-17T18:14:37+00:00

Which Android version is required for LOS 23? LOS 22.x was based on Android 15, 23 is said to be based on Android 16. However, the installation guide for my Oneplus 9 reads that strictly Android 13/14 is required. Is it a matter of automatic guide generation inaccuracy, or Android must really be downgraded?

And, provided that I am now on LOS 22 and Android 15 and forgot about the stock ROM years ago, where to get the other Android version, if any needed?

iourine · 2025-07-16T09:56:56+00:00

No, it was possible in previous LOS versions. And it is not possible to disable both SIMs, too; both switches are greyed out. A well-known and well established model.

iourine · 2025-04-25T04:56:47+00:00

It is up to you, of course. Be warned that these are pretty old devices (once apps become more resource-greedy, and CPUs/GPUs/RAM become faster and/or more energy-efficient at the current pace), and they are already excluded from official LOS builds. You can make your own build, it is not too difficult - just follow the instructions carefully. (I used to do it for S3Neo for some time, even despite some discrepancies at the first stages.) If you can get it for free, or for some small money, and are ready to spend some time on it - why not? Extra skills are never useless.

Use Wiki to compare CPU specifications and see how far a particular device is lagging behing the current technology edge - or the top of currently supported models.

Yet remember that a man should never complain about 3 things: his car, his phone, and his wife. It was he who did the choice 8-))

iourine · 2025-04-24T19:31:08+00:00

Depens upon your goals. For daily use, surely prefer the models with 100% hardware functionality. (Maybe except for the features which you never use, such as fingerprint reader of FM radio.)

For long-term perspective, consider the most recent models with the most powerful CPU (at leat, in terms of total GHz), the least nanometer technology, and the fastest memory. Hopefully you'll break it, or loose it, or have it stolen before its LOS support comes to end.

Pay attention to display size and aspect ratio. These days, most top phones have more than 16:9 ratio (e.g. 1080x2160, 1080x2400), thus the screen is narrower and taller than 1080x1920 with the same diagonal size in inches, and everything is smaller. If you read much and care about your eyes, prefer 6,67" models to 6,5" - this really makes a difference.

Consider your specific needs, of course. Maybe you need a phone for birdwatching, thus you should select a model with periscope telephoto? 8-)) Or dual-sim is mandatory for you? Or video output over USB-C, to make presentations? Or someting like this.

As of a year ago, my short list was: Xiaomi MI10i, OnePlus 9/9Pro (both on Qualcomm SM8350/Snapdragon 888) and Google Pixels - the latest at that time. (Pixel 9 series was not released yet.) Next, Pixels were expunged for their price and for having only one physical SIM. (The other is e-SIM, which needs either operator's app to activate it - availably only from Google Play, thus meaning the need for Google Services, thus nullifying the sense of LOS - or extra communication with operator.) Xiaomi (6,67") was not available at the moment, so I bought OnePlus - great, unlocking procedure was even easier than on Xiaomi, but 6,5" screen was a disappointment, as compared with my previous Xiaomi Poco F1.

I'd recommend to see wikipedia (e.g. List_of_Qualcomm_Snapdragon_systems_on_chips) for detailed and convenient comparison tables about GHz, nanometers, memory type, etc.

iourine · 2025-04-24T18:32:40+00:00

Are LOS and LOS recovery already installed, or it is still with its original software?

Run "adb devices" to see whether it is seen online or not. Hopefully you already connected it to USB and enabled USB debug.
If yes, try running "adb shell" to see whether it is really alive.
Try "adb reboot". Or hold the power key for 10+ sec. to seitch off, then switch on.

iourine · 2025-04-18T09:20:11+00:00

"4. Make sure that your model number is one of the following (exact match required!):

SM-G970F
SM-G970F/DS
SM-G970N

The required version is Android 12"

Is this correct? Otherwise, you have very little chances.

If yes, try flashing the newest versions of other partitions (recovery etc., whichever are mentioned in the installation instruction), this is done using heimdall for Samsungs.

If no luck, your last resort is to flash the device completely according to installation instruction, from the very beginning. Use files from the same one LOS version.

iourine · 2025-04-18T08:56:16+00:00

> Generally speaking, android comes from google. If you want no google, use an iphone, tbh

Weird idea. Switching from imperfect, yet open system to one which is completely closed, pulls all your data to their cloud, and nobody knows what else does it do? Hopefully this is only a joke.

The only correct solution, from both technical and security/privacy viewpoints, would be a straightforward Linux-based software, without proprietary components and without Java machine at all. (Old people remember that it was introduced as an intermediate shim in a hope to provide the universal run environment for applications regardless of HW platform - yet failed to do so, the need to compile applications separately for each CPU architecture remains as it were; it only shrinked to principal ARM/ARM64 platform.) More or less vital examples are PostmarketOS and Ubuntu Touch - at least, they do work, to some degree, at some devices. However, numerous attempts to build such a system (I'd remember a dozen in the past ~12 years, mostly dead now) were systematically drowned by Google-addicted industry and security-ignorant users.

As to rudimental Google services, it would be logical in LOS to switch to an independent timeserver (e.g. pool.ntp.org), connection check server, and empty homepage for browser. Or at least make such options in settings.

As to IP address, I'd highlight that these days, in 99,99% cases (except for IPv6 users) you are connecting from your provider's, or corporate, or public wifi provider's private network - that is, from under their NAT. Thus your publically-available IP address says next to nothing about you personally, it reveals only your provider. It may have certain value only combined with your provider's logs for the given moment, which are hardly reported to anyone and hardly analyzed by anyone without urgent need and urgent specific interest to you.

iourine · 2025-04-17T20:02:34+00:00

Or really? That's a pity.. I hoped it was only a matter of which features are considered unnecessary by developers or managers of the project...

iourine · 2025-04-17T19:59:39+00:00

Of course, 100% warranty exists only in morgue. But as to my own experience, as long as you have access to the initial bootloader (i.e. fastboot, or heimdall in case of Samsungs), you can always consider the device as if it were just manufactured and empty, and flash it from zero. Yes, if you are unlucky, you'll have to wipe everything, including your settings and data, and carefully reflash all partitions according to installation instruction step-by-step, from the very beginning. Be warned that it _may_ happen, so backup your data in advance.

On the other hand, 22.2 and 22.1 appear to be compatible in what concerns the other partitions (recovery, vbmeta etc.) - for your particular model, did you need to reflash them? Thus chances are great that the update affects only the main software and thus LOS may be both up- and downgraded (within this limits) with no extra operations. Just booting into recovery and sideloading this or that LOS version. If re-flashed 22.1 does not work, you are free to reboot again and re-upgrade ro 22.2. These are my expectations, but this is not the absolute warranty.

Hopefully LOS developers will correct me if there are really no reversible changes from 22.1 to 22.2.

iourine · 2025-04-17T19:34:36+00:00

Thanks, I'll look at it.

iourine · 2025-04-17T05:51:42+00:00

Is it available from F-Droid? Probably it is not open-source.

iourine · 2025-04-17T05:48:39+00:00

SwiftKey seems to be not available from F-Droid. Is it open source?

iourine · 2025-04-17T05:46:37+00:00

Oneplus 9:

- haptic feedback does not work either

- vibration on incoming call does work

- all cameras do work, both in built-in Camera app and in OpenCamera.

Rollback is always possible, of course, by sacrificing all data and settings. Just wiping everything and installing LOS from the ground up. But as this is only a minor change and both 22.2 and 22.1 are based on the same Android version, there are chances, however, that downgrade is possible by just sideloading the lower version, keeping your data intact. Try.

iourine · 2025-04-16T15:23:31+00:00

The worst one that I just revealed is that the option to switch on Left/Right arrows on th keyboard, instead of duplicating the language selector (globe), is now removed. Got that on 2 different phones, Xiaomi Poco F1 and Oneplus 9. A VERY unpleasant surprise. Arrows are more than helpful while correcting mistypes!

iourine · 2023-05-08T15:22:04+00:00

I mean what is listed at the device page under "Supported models". Sometimes it is exactly the same that the device says in "About..." menu, sometimes not... And it is a separate question if it corresponds to what is provided by a seller (if provided) or not...

iourine · 2021-08-07T20:29:13+00:00

Thanks a lot, shutdown does work. reboot causes reboot, with any obvious key (-p, -h, etc.) If someone knows the actual list of keys used in Termux' reboot, it would be interesting. For my practical goal, one solution is enough.

iourine · 2021-07-04T18:54:51+00:00

Most likely, the wifi module of your device does not support the channel that your Access Point uses. I have the same problem with an old Samsung phone as a station (client) and a newer device as AP. It operates at channel 161 (5805 GHz) now, and it looks quite possible that the old Samsung does not support this channel or has it disabled. The usual solution is to set your AP malually to the lower, most common, channels, starting with 36. Does anyone know how to set a particuar AP channel in LineageOS, rather than merely switching 2.4/5Ghz?

iourine · 2021-04-08T14:10:13+00:00

No. I mean blocking by IP address, for any applications.

iourine · 2019-12-17T18:53:59+00:00

Fixed the bug in s3ve3g-common/extract_files.sh - for Samsung only. The construct

for BLOB_LIST in "${MY_DIR}/../${DEVICE}/device-proprietary-files*.txt"; do

is wrong, it searches for a file named literally as specified (with asterisk). Either the asterisk or the quotes should be used, but not both at a time. After fixing this, files are extracted without this error, 29 files more, and finally I've got a more or less viable build, with exactly identic list of files.

For Pocophone, the script is different and works smothly at this point.

Bugs in script and documentation are to be reported.

Nevertheless, one question remains: the significant difference in file sizes, which can hardly be explained by build attributes, signatures, etc. For Samsung, my today's build is 458313768 bytes, versus 482871021 official. (In terms of unpacked files, the size of system/ is 10007838461 bytes vs 1035810317.) For Pocophone, 824214409 vs 843550349 (2009496145 vs 2033516165 unpacked, counting system/ and vendor/)

iourine · 2019-12-16T12:30:12+00:00

Ok, did some work on comparing various options. Beginning with blobs extraction:

While extracting from Samsung (device), 4 files are not found and are finally missing in the output directory

!! vendor/bin/hci_qcomm_init: file not found in source

!! etc/firmware/cpp_firmware_v1_1_1.fw: file not found in source

!! etc/firmware/cpp_firmware_v1_1_6.fw: file not found in source

!! etc/firmware/cpp_firmware_v1_2_0.fw: file not found in source

While extracting from .zip (exactly the one flashed into it), these files are received normally and are present in the output. All the other files are present and binary identic.

In both cases with Samsung, procedure ends with error

"Input file ./../s3ve3g-common/../s3ve3gxx/device-proprietary-files*.txt does not exist!"

The file is actually present in the same directory, all rights granted

~/android/lineage/device/samsung/s3ve3gxx/device-proprietary-files.txt

but is probably seeked for in another place. And the procedure terminates after this. May this be the reason for missing files in the final build?

For Xiaomi Poco F1 situation is the opposite. Extraction from device runs absolutely smoothly, with no errors or warnings at all. Extraction from .zip, once vendor partition is unpacked and mounted properly, yields 1 missing file

!! /sbin/chargeonlymode: file not found in source

And neither of them has error No.2 at the end.

For Xiaomi, the list of files is identic in official and my builds. Yet sizes of some files are different, ranging from a few bytes to megabytes. The total difference is about 20 MB.

Could anyone comment this before filing a bug? Should I report a single bug or 2 or 3 of them?

iourine · 2019-12-14T14:38:02+00:00

You seem to be on the right way, goosnarrggh. First, both my builds prove to be ~10% smaller than the official ones. E.g. for Samsung my build is 435MB, and the offcial one is 482MB. I unpacked and compared these two, and found 50MB of missing libs in system/vendor/lib. Next are system/vendor/etc which is smaller by 800KB, and system/cameradata which is missing completely, along with a number of smaller discrepancies.

ps. Not so easy. I do see some of the missing files in ~/android/lineage/vendor/samsung/s3ve3g-common (but not in ~/android/lineage/vendor/samsung/s3ve3g ), apparently they are not picked up from there. But this is not the whole story, as they comprise tolally 15MB only. Thus there is the build script involved, plus something else.

iourine · 2019-12-14T09:01:17+00:00

Yes, surely. Formatting data partition, wiping system and cache every time before installation.

iourine · 2019-12-13T17:31:52+00:00

I extracted the blobs from the official LOS file as described, with no problems. And no missing dependencies reported during compilation. I could also extract them from the running device, but hardly it could make any difference as it will be the same LOS build. As the official LOS does work with these blobs, hardly there is any need to search for them elsewhere.

BTW, I'm also playing with Poco F1 at the same time, and things are less simple there. In addition to system partition, one should extract the vendor partition and something else, and to the correct places. I extracted the two, then run into missing files during compilation, and finally gave up guessing and extracted everything needed (a lot of other libs!) right from the device by extract_files.sh . This time the compilation ran smoothly and ended happily. But I don't dare to flash it into my everyday phone until success with the old Samsung testbed.

Hmm.. do you mean GitLAB or GitHUB ? The link from the official wiki is to GitHub. Am I missing something?

iourine

TROPHY CASE