[ROM][UNOFFICIAL][8.1] LineageOS 15.1, AICP | Development & Discussion | 2021.06.18

Search This thread

f2065

Senior Member
Sep 5, 2007
216
115
Moscow
f2065.ru
New build LineageOS 15.1 published.
Returned SDCardFS. It was a very long time ago, but in those days because of it there were errors with microSD and they refused SDCardFS (they used FUSE). Now I imported the latest version of SDCardFS, checked for 2 weeks - I did not find any bugs with microSD.


Does anyone have unexpected reboots (on any previous versions of LineageOS) - once every few days?
It has always been with me (both in my builds and in old builds of other authors). Now I began to investigate - the reason is the overflow of the sensor buffer. The place of the fall is in the LineageOS source. But the root cause is most likely in our sensor drivers, or in multihal ...
We need to find patterns - on which revisions of M2 there is this problem.

Crash log is saved in /data/system/dropbox…
pid: 922, tid: 3000, name: SensorService >>> system_server <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x9d180000
r0 9d17fe50 r1 9d17fff0 r2 fffb89c8 r3 00000000

backtrace:
#00 pc 00018f04 /system/lib/libc.so (memcpy+168)
#01 pc 0000f431 /system/lib/libsensorservice.so (android::SensorService::SensorEventConnection::sendEvents(sensors_event_t const*, unsigned int, sensors_event_t*, android::wp<android::SensorService::SensorEventConnection const> const*)+448)

This place is in frameworks/native/services/sensorservice/SensorEventConnection.cpp - android::SensorService::SensorEventConnection::sendEvents на memmove(mEventCache, &mEventCache[numEventsDropped], (mCacheSize - numEventsDropped) * sizeof(sensors_event_t));

int numEventsDropped = count - remaningCacheSize;
countFlushCompleteEventsLocked(mEventCache, numEventsDropped);
// Drop the first "numEventsDropped" in the cache.
memmove(mEventCache, &mEventCache[numEventsDropped], (mCacheSize - numEventsDropped) * sizeof(sensors_event_t));
Crash in memmove (memcpy - called inside memmove), due to going out of the segment (i.e. the queue size is incorrect).
 

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
Thanks for the new build :)

Does anyone have unexpected reboots (on any previous versions of LineageOS) - once every few days?
It has always been with me (both in my builds and in old builds of other authors). Now I began to investigate - the reason is the overflow of the sensor buffer. The place of the fall is in the LineageOS source. But the root cause is most likely in our sensor drivers, or in multihal ...
We need to find patterns - on which revisions of M2 there is this problem.

i guess we need to flash stock rom for checking the revision, right? i have this phone since july 2014 so i guess mine is one of the first revisions. and i didn't get any random reboots on any rom made for this phone.

btw here comes my unrelated request; can you make a custom kernel that is overclocked (to 1.4ghz maybe?) and has custom governors? that would be dope to play with
 

f2065

Senior Member
Sep 5, 2007
216
115
Moscow
f2065.ru
i guess we need to flash stock rom for checking the revision, right?
No. Revision is determined only indirectly, by the inscription on the retractable plate near the SIM-cards.

I saw three options for sensors:
- on all old revisions;
- at the final revision (rev.7) of the M2 LTE;
- at the final revision (rev.5) of the M2 Aqua.

btw here comes my unrelated request; can you make a custom kernel that is overclocked (to 1.4ghz maybe?)
I wanted to raise the frequencies. But there's a problem.
For Android 5.1, there is an old kernel from freack_v, with overclocking - up to 1.4 GHz, and even 1.6 GHz is possible. There is also an overclocking of the memory bus - up to 566 MHz (standardly, the memory bus works up to 400 MHz).
But I measured different tests (both specialized and various archivers - rar, 7zip, converters) on that firmware - and it turned out that at frequencies above 1.2 GHz the real performance drops significantly! According to the author, he does not have such a problem, but he did not provide test results.
There was an assumption that this was due to overheating, I tried it in the freezer - all the same, at frequencies above 1.2, performance drops although the processor was cold.

I tried to overclock in my kernel by analogy, and my kernel had a similar result - at higher frequencies the performance is lower. If tweakers limit the frequencies to 1.2 (1190400) - then the performance is normal. And when you remove the restrictions - performance drops.

Considering that all tests in android have a wide range of results - I tested it many times. And my M2 Aqua absolutely definitely lost performance during overclocking.
I tried to limit the frequency of tweakers to 1.0 or 0.78 - the performance was falling proportionally. I had maximum performance only at the standard frequency - 1.2 (1190400).

It is likely that overclocking is not possible for all processor revisions. On M2, there are different hardware versions of processors - the kernel (more precisely, in the DTB tables of the kernel) contains support for several processor options. On M2, I saw at least 3 processor options (differing in msm-id code). Overclocking tables in the kernel are written for each processor variant separately. Maybe for different options it is necessary to do acceleration tables in different ways (now everything was done the same for everyone).

I can make a kernel with overclocking, but it is necessary that several users with different models (LTE, Aqua, Dual, 3G / D2305) test performance in tests before and after.

and has custom governors?
For a long time there are built-in: ondemand (default), interactive, performance, powersave, userspace. Governor custom tuning supported.
But the standard settings LineageOS does not allow to control this. Can be controlled in AICP settings.
Or any third-party tweakers - for example, Kernel Adiutor.
 
  • Like
Reactions: JuniorCaesar

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
No. Revision is determined only indirectly, by the inscription on the retractable plate near the SIM-cards.

I saw three options for sensors:
- on all old revisions;
- at the final revision (rev.7) of the M2 LTE;
- at the final revision (rev.5) of the M2 Aqua.

I wanted to raise the frequencies. But there's a problem.
For Android 5.1, there is an old kernel from freack_v, with overclocking - up to 1.4 GHz, and even 1.6 GHz is possible. There is also an overclocking of the memory bus - up to 566 MHz (standardly, the memory bus works up to 400 MHz).
But I measured different tests (both specialized and various archivers - rar, 7zip, converters) on that firmware - and it turned out that at frequencies above 1.2 GHz the real performance drops significantly! According to the author, he does not have such a problem, but he did not provide test results.
There was an assumption that this was due to overheating, I tried it in the freezer - all the same, at frequencies above 1.2, performance drops although the processor was cold.

I tried to overclock in my kernel by analogy, and my kernel had a similar result - at higher frequencies the performance is lower. If tweakers limit the frequencies to 1.2 (1190400) - then the performance is normal. And when you remove the restrictions - performance drops.

Considering that all tests in android have a wide range of results - I tested it many times. And my M2 Aqua absolutely definitely lost performance during overclocking.
I tried to limit the frequency of tweakers to 1.0 or 0.78 - the performance was falling proportionally. I had maximum performance only at the standard frequency - 1.2 (1190400).

It is likely that overclocking is not possible for all processor revisions. On M2, there are different hardware versions of processors - the kernel (more precisely, in the DTB tables of the kernel) contains support for several processor options. On M2, I saw at least 3 processor options (differing in msm-id code). Overclocking tables in the kernel are written for each processor variant separately. Maybe for different options it is necessary to do acceleration tables in different ways (now everything was done the same for everyone).

I can make a kernel with overclocking, but it is necessary that several users with different models (LTE, Aqua, Dual, 3G / D2305) test performance in tests before and after.

For a long time there are built-in: ondemand (default), interactive, performance, powersave, userspace. Governor custom tuning supported.
But the standard settings LineageOS does not allow to control this. Can be controlled in AICP settings.
Or any third-party tweakers - for example, Kernel Adiutor.

First of all, thank you so much for your detailed response. If you make a overclocked kernel i can test it on my d2303 and share the results.

No. Revision is determined only indirectly, by the inscription on the retractable plate near the SIM-cards.

This came to my mind, but i can't see any revision number. I have serial number, imei and some QR code.

Sent from my X Compact using XDA Labs
 

f2065

Senior Member
Sep 5, 2007
216
115
Moscow
f2065.ru
2019-10-27 - Released experimental kernel overclocking

CPU +17% (1.19 → 1.40 GHz)
RAM +6% (533 → 566 MHz)
GPU +18% (450 → 533 MHz)

5 measurements were taken on a standard core and on a core with overclocking.
PCMark test - average performance increased by 10%
Geekbench 4 test, RAR test - average performance has not changed…

Also added the minimum frequencies 96, 192, 249. They are not selected by default, they can be turned on with tweakers. There will be higher energy savings, but the phone will slow down significantly.

Different M2 models (LTE, 3G, Dual, Aqua, New revision, Old revision, etc) may have different processor IDs, and some users may not have new frequencies.
Check for new CPU and GPU frequencies.
 
  • Like
Reactions: JuniorCaesar

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
2019-10-27 - Released experimental kernel overclocking

CPU +17% (1.19 → 1.40 GHz)
RAM +6% (533 → 566 MHz)
GPU +18% (450 → 533 MHz)

5 measurements were taken on a standard core and on a core with overclocking.
PCMark test - average performance increased by 10%
Geekbench 4 test, RAR test - average performance has not changed…

Also added the minimum frequencies 96, 192, 249. They are not selected by default, they can be turned on with tweakers. There will be higher energy savings, but the phone will slow down significantly.

Different M2 models (LTE, 3G, Dual, Aqua, New revision, Old revision, etc) may have different processor IDs, and some users may not have new frequencies.
Check for new CPU and GPU frequencies.

Thank you so much! I'm gonna download and test it now.

Sent from my X Compact using XDA Labs

---------- Post added at 05:04 PM ---------- Previous post was at 04:21 PM ----------

i installed it on PixelExperience and it works great, i can already see that some of the lags are gone. thanks!

Edit: Disable CPU Hotplugging and enable android GO mode for full effect. it works better than i expected.
 
Last edited:
  • Like
Reactions: hooooossamq

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
Is there evidence that the overclocked kernel is actually faster than normal?
Otherwise, there will be no overclocking in future versions…

yes it is faster on my side. 1.4 vs 1.2
 

Attachments

  • Screenshot_Geekbench_4_20191114-235125.png
    Screenshot_Geekbench_4_20191114-235125.png
    57.1 KB · Views: 70
  • Screenshot_Geekbench_4_20191115-000818.png
    Screenshot_Geekbench_4_20191115-000818.png
    57.9 KB · Views: 70

f2065

Senior Member
Sep 5, 2007
216
115
Moscow
f2065.ru
yes it is faster on my side. 1.4 vs 1.2
All tests have a large error (probably due to the periodic background operation of various system processes - which take part of the processor power).
I measured in Geekbench - the difference between 1.2 and 1.4 is the same as just between several dimensions.

Results Geekbench:
998 MHz: 361/991 384/866 384/867 385/1026 378/1004 377/1012
1094 MHz: 411/1012 409/955 408/1008 412/1034 412/1014 412/1074
1190 MHz: 439/945 438/1101 431/1119 440/1068 413/1065 435/1063 436/897 435/1040 435/1052 434/1133 435/1110 428/1062 427/993 426/1042
1305 MHz: 437/972 426/1078 409/1145 423/1142 439/1180 441/1148
1401 MHz: 431/1072 440/1071 446/1083 446/1168 437/1095 439/988 437/1084 440/1120 421/1055 436/1129
1593 Mhz: 438/1105 433/1080

Results RealPi Benchmark:
998/533 MHz: ~30.7 (30.74 31.65 30.64 31.06 30.38 30.27 30.34 30.82 31.76 30.33 30.26 30.31 30.37 30.45 31.16 30.92)
1094/533 MHz: ~28.4 (28.96 28.37 28.05 28.38 27.89 27.96 28.93 28.39 28.93 28.36 27.77 28.05 29.43 28.37 28.57 29.08)
1190/533 MHz: ~26.6 (26.66 26.68 26.49 26.93 26.50 26.27 26.90 26.39 26.30 26.94 26.53 26.76 26.80 26.54 26.38 26.81)
1305/566 MHz: ~26.2 (26.10 26.52 26.73 26.60 26.22 25.81 25.63 25.89 26.57 26.19 26.07 26.03 26.58 26.10 25.76 25.90)
1344/566 MHz: ~26.1 (26.20 26.17 26.13 26.28 26.58 25.93 26.15 26.68 26.07 25.48 25.63 26.16 26.53 26.45 25.59 26.33)
1401/566 MHz: ~25.9 (26.05 25.07 25.74 25.78 25.68 26.41 26.40 25.96 25.62 26.54 26.00 25.21 25.97 25.73 26.51 26.14)
1497/566 MHz: ~26.4 (26.37 25.92 26.42 25.55 25.75 25.94 26.28 26.07 26.23 26.58 26.35 26.66 28.37 26.38 26.99 26.87)
1593/566 MHz: ~26.3 (26.87 26.08 26.16 25.72 26.43 26.02 26.60 26.22 26.09 26.59 26.03 26.08 27.16 25.89 26.30 26.09)

1.0 GHz = 30.7; 1.2 GHz = 26.6; 1.4 GHz = 25.9
30.7-26.6 = 4.1
26.6-25.9 = 0.7, but should be around 4.0 too.
This is not like overclocking a processor. This is either a measurement error, or result overclocking RAM (533-566) or voltage control.

I do not know how to overclock the processor.
With the old FKernel (where the processor was overclocked), I have the same results, 1.4 GHz frequencies are shown, but all tests of these frequencies do not differ from 1.2 GHz.

Overclocking the GPU (from 450 MHz to 533 MHz) also fails. The frequencies in the list are and are selected. But according to tests, FPS graphics do not differ in modes 450 and 533. In mode 320, FPS is noticeably lower.
 
Last edited:

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
Well i don't know, system runs a bit better than stock kernel. Maybe it is placebo, i rarely pick my m2 out of its box and play with it.

If overclocking isn't working properly, you don't need to work on it as daily users of m2 are very rare nowadays (and the forum is pretty much dead).
 

basem_ym

Senior Member
Jul 6, 2015
232
76
27
Tartus
Is there evidence that the overclocked kernel is actually faster than normal?
Otherwise, there will be no overclocking in future versions…
Why not making UNDERclocked kernel?
I dont see any real world improvement in OC'ing this device Imo, only more heating,glitching and ofcourse more battery drain.
Back in days(years maybe) I locked my CPU at 997(maybe little bit more or less dont remember) and I completely got rid of heating problem, and I didnt notice any drawback in performance, even at 790hz you will not notice any drawback.
My main issue was that my kernel settings wasnt sticking, and it was annoying to open kernel auditore to set frequencies every time, so I forgot about it.
Since this device can not do heavy multitasking/gaming, it would be much much better to underclock this kernel, so no more heat and less battery drain(hopefully)
I really miss my M2, I wish I could flash this rom and tinker with some setting.
Thank you for maintaining this device, it really means alot and I really appreciate your efforts thank you so much.
 

JuniorCaesar

Senior Member
Mar 22, 2014
724
354
Ankara
Xiaomi Mi A1
Why not making UNDERclocked kernel?
I dont see any real world improvement in OC'ing this device Imo, only more heating,glitching and ofcourse more battery drain.
Back in days(years maybe) I locked my CPU at 997(maybe little bit more or less dont remember) and I completely got rid of heating problem, and I didnt notice any drawback in performance, even at 790hz you will not notice any drawback.
My main issue was that my kernel settings wasnt sticking, and it was annoying to open kernel auditore to set frequencies every time, so I forgot about it.
Since this device can not do heavy multitasking/gaming, it would be much much better to underclock this kernel, so no more heat and less battery drain(hopefully)
I really miss my M2, I wish I could flash this rom and tinker with some setting.
Thank you for maintaining this device, it really means alot and I really appreciate your efforts thank you so much.

1.2 ghz is not enough for most tasks and modern apps nowadays so i don't see any benefit of underclocking other than getting rid of overheating to be honest.
 

basem_ym

Senior Member
Jul 6, 2015
232
76
27
Tartus
1.2 ghz is not enough for most tasks and modern apps nowadays so i don't see any benefit of underclocking other than getting rid of overheating to be honest.
Overheating causes low (very low) performance, may even cause complete freeze, for me at least, so actually you are getting rid of 2 problems.
As for modern apps, even at 1.4 ghz, this device won't make you happy, actually it can handle lite versions of famous apps pretty well, no point of running heavy modern apps on such device nor gaming Imo, it even struggles on surfing some websites(very common ones,)
So OC would make every thing worse from my point of view, but UC would make this device live longer at least.
 

Fran_Hdez

New member
Dec 22, 2019
2
0
Noobs Flashing Guide

Hi everyone, noob as I am, I did a complete guide for myself at future a general ROM Flashing Guide. Since it is very complete I decided to share it. It takes every step of the process, from the very beginning unlocking the device's bootloader to the ROM Flashing using TMRP Recovery, clearly explaining how I solve every little problem I faced.

Sincerely,
Fran Hdez.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Flashing LineageOS on Sony Xperia M2 on Windows 7.

0. Hard reset → Only if the Device is stuck at the pattern screen.
Sony PC Companion. Only running in Windows (7 and greaters).


1. Unlocking bootloader.

https://www.getdroidtips.com/unlock-bootloader-sony-xperia-m2/


Device IMEI Number = 355341060613097.

Official Bootloader Unlock Page from Sony.
https://developer.sonymobile.com/unlockbootloader/

How to get the Device Unlocked with the Sony Unlocking Code.
https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/

Sony Generated Unlocking Code: BD2FA867CD84E4BE.


1.1. Enabling Developer Options on the Device.
Allowing Access to Developer Options: Settings → About Phone → Build Number Tapping 7-8 times.
Settings → Developer Options → Allow USB Debugging.


1.2. Installing Latest USB Sony Driver. NOT NECESSARY IF WINDOWS RECOGNIZES THE DEVICE PROPERLY (this means that the System has auto-installed the needed Driver).

Download zip file: https://developer.sony.com/develop/drivers/
Installing Instructions: https://developer.android.com/studio/run/oem-usb.html#InstallingDriver


1.3. How to Install ADB and Fastboot on Windows (only compatible with Windows and Mac OS).

Remember to have the Device on USB Debugging Mode.
https://www.getdroidtips.com/how-to-install-adb-and-fastboot-on-windows/

Android Software Development Kit (SDK) is the full weigh tool, which includes Fastboot and ADB and it is available for Linux. It should be download directly from Google.
https://www.getdroidtips.com/download-adb/

Android SDK is a huge tool used for (around 1 (Gb)) and we only need to use the Fastboot and ADB sub-tools (around 10 (Mb)), so we will only download this 2 packages from a thirty source, which modified the Android SDK Package to run these 2 tools. That is why they only run in Windows and Mac OS.

ADB and Fastboot files. It is named 15 seconds ADB Installer v1.4.3 and includes ADB, Fastboot and Drivers.
https://forum.xda-developers.com/showthread.php?t=2588979

1.4. Opening ADB Bridge between Computer and Phone.

Open a command window (no need to do it on the directory)
Run the Daemon: adb devices.
Allow Access on the phone: unlock the Device and select Allow ADB Access from the connected computer.
Connection can be checked by rebooting the phone: adb reboot


1.5. Connect to Fastboot.
Turn off the Device.
Connect a USB-cable to the computer.
Press the Fastboot key (Volume up) at the same time as you connect the other end of the USB-cable. The notification led will turn to blue.

This is the same than doing.
adb reboot bootloader

To verify the Device has entered the Fastboot mode, write the following command and wait for the Device number response without any error.
fastboot devices
Now enter the command with your unlock key after the oem unlock and replace this character BD2FA867CD84E4BE with your unlock key
fastboot oem unlock 0xBD2FA867CD84E4BE

Done! Now the Device’s Bootloader is successfully Unlocked.

2. Installing TWRP Recovery.
https://www.getdroidtips.com/twrp-recovery-sony-xperia-m2/

2.1. Download SuperUS.zip
https://www.getdroidtips.com/download-supersu-root-zip/

Direct link to download.
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

2.2. Download TWRP Recovery (Choose 3.1.0-b2 (also known as 3.1.1) version, compatible with Sony Xperia M2).
https://qc3.androidfilehost.com/dl/...7178217/673368273298952396/twrp-3.1.0-b2.img?

2.3. Flash the TWRP Recovery image file on the Device.
https://www.getdroidtips.com/flash-twrp-recovery-android/

Note that normally this step is done just after Unlocking the Bootloader, which causes the Hard Reset of the phone, so again, allowing USB Debugging at Developer Options will be needed.

Get the Device into the Bootloader.
adb reboot bootloader

Now type the below command on your command window.
fastboot devices

This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.

To flash the recovery, Type the command. (Please make sure the name of TWRP image, if you renamed it to recovery.img, then after the flash recovery, type recovery.img). Note that the command window must be sourced to directory where the image file is located.
fastboot flash recovery recovery.img

TWRP has successfully installed. Enjoy.

3. Booting into Recovery Mode.

To boot the Device into TWRP Recovery Mode:
Option 1: Power Off and then Power On + Volume Up.
Option 2: adb reboot recovery

If the previous ways to boot from the Recovery image fails, it is possible to directly boot a flashed Recovery Mode from the Fastboot. To run this command, the image file needs to be inside the source directory.
fastboot boot recovery.img

4. Flashing the new ROM.
https://www.getdroidtips.com/install-custom-rom-using-twrp-recovery/

The coolest ROM that can be implemented in the Sony Xperia M2 is LineageOS 15.1
https://forum.xda-developers.com/xperia-m2/orig-development

Download and Flash ROM.
https://qc2.androidfilehost.com/dl/...77203556/673368273298931131/twrp-3.0.3-b2.img

Download and Flash Google Apps (for ARM Processor Architecture a and Android 8.1).
https://androidfilehost.com/?w=files&flid=170282

For knowing the Processor Architecture, we can google it or use the app Droid Hardware Info. Usually, old devices (before 2016) has ARM implemented and modern devices use ARM64. ARM is unidirectionally compatible with ARM64.
 
Last edited:

f2065

Senior Member
Sep 5, 2007
216
115
Moscow
f2065.ru
Flashing LineageOS on Sony Xperia M2 on Windows 7.
0. Hard reset
Before installing LineageOS-firmware (and any firmware based on Android 5,6,7,8,9,10) it is necessary that the latest stock firmware be 5.1.1 (18.6.A.0.182)
If the latest firmware was 4.4 - there will be problems with Wi-Fi.
This is due to the modem section, it is used in new firmware, but it does not flash in new firmware. It remains from the latest stock firmware.

For stock firmware, you must use Flashtool firmware version 0.9.18.6. It is important. Some newer versions of Flashtool damage the phone.

2. Installing TWRP Recovery.
url getdroidtips

2.2. Download TWRP Recovery (Choose 3.1.0-b2 (also known as 3.1.1) version, compatible with Sony Xperia M2).
url twrp-3.1.0-b2.img

Download and Flash ROM.
url twrp-3.0.3-b2.img
These are all old versions.
The modern version - there https://forum.xda-developers.com/xperia-m2/orig-development/recovery-twrp-3-3-0-development-t3923414

To boot the Device into TWRP Recovery Mode:
Option 1: Power Off and then Power On + Volume Up.
Power Off and then Power On + Volume Up, or Power On + Volume Down

Option 3: (in firmware newer than June 2019): You can enable reboot in recovery in the developers menu (in older LineageOS-firmware, the reboot did not work)

Download and Flash Google Apps (for ARM Processor Architecture a and Android 8.1).
I am using OpenGApps - https://opengapps.org/
 
  • Like
Reactions: JuniorCaesar

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Unofficial build of LineageOS 15.1 (Android 8.1 Oreo) and AICP 13.1 (Android 8.1 Oreo) for the Sony Xperia M2 (eagle).

    Disclaimer
    Your warranty is now void!
    You will be doing everything at your own risk.
    I am not responsible for bricked or damaged devices.

    Download
    https://f2065.ru/android/Android_M2_en.htm

    Changelog
    2021.06.18
    • Source LineageOS updated to 2021-06-18, security update from 5 June 2021.
    2021.05.16
    • Source LineageOS updated to 2021-05-16, security update from 5 May 2021.
    2021.04.15
    • Source LineageOS updated to 2021-04-15, security update from 5 April 2021.
    2021.03.08
    • Source LineageOS updated to 2021-03-08, security update from 5 Mart 2021.
    2021.02.17
    • Source LineageOS updated to 2021-02-17, security update from 5 February 2021.
    2021.01.18
    • For M2 Dual (D2302) – fixed the ability to disable the second SIM in the Settings.
    • Source LineageOS updated to 2021-01-18, security update from 5 January 2021.
    2020.12.22
    • Source LineageOS updated to 2020-12-22, security update from 5 December 2020.
    2020.11.15
    • Source LineageOS updated to 2020-11-15, security update from 5 November 2020.
    2020.10.11
    • Source LineageOS updated to 2020-10-11, security update from 5 October 2020.
    2020.09.30
    • Source LineageOS updated to 2020-09-30, security update from 5 September 2020.
    • Minor kernel changes.
    2020.08.23
    • Source LineageOS updated to 2020-08-23, security update from 5 August 2020.
    2020.07.23
    • Source LineageOS updated to 2020-07-23, security update from 5 Jule 2020.
    2020.06.10
    • Source LineageOS updated to 2020-06-10, security update from 5 June 2020.
    2020.05.25
    • Optimization of memory settings for system services by analogy with Android Go.
    • Minor kernel changes.
    • Source LineageOS updated to 2020-05-25, security update from 5 May 2020.
    2020.05.01
    • Source LineageOS updated to 2020-05-01, security update from 5 April 2020.
    2020.03.10
    • Source LineageOS updated to 2020-03-10, security update from 5 Mart 2020.
    2020.02.11
    • Source LineageOS updated to 2020-02-11, security update from 5 February 2020.
    2020.01.23
    • Source LineageOS updated to 2020-01-23, security update from 5 January 2020.
    2019.12.12
    • Source LineageOS updated to 2019-12-12, security update from 5 December 2019.
    2019.11.17
    • Source AICP updated to 2019-11-27, security update from 5 November 2019.
    2019.11.17
    • Minor kernel changes.
    • Source LineageOS updated to 2019-11-17, security update from 5 November 2019.
    2019.10.17
    • Source LineageOS updated to 2019-10-17, security update from 5 October 2019.
    • SDCardFS kernel driver.
    • Several hundred kernel commits (migrated from other kernels for msm8226, msm8960t, msm8916, msm8974).
    2019.08.15
    • Sources AICP and LineageOS updated to 2019-08-15, security update from 5 August 2019.
    2019.07.10
    • Experimental build – Android Go configuration (faster and more responsive, but less beautiful, and some have problems with notifications from the messengers).
    2019.07.10
    • Sources AICP and LineageOS updated to 2019-07-10, security update from 5 Jule 2019.
    2019.06.16
    • Adaptive LMK.
    • Several hundred kernel commits (migrated from other kernels for msm8226, msm8960t, msm8916).
    • Source LineageOS updated to 2019-06-16, security update from 5 June 2019.
    2019.05.21
    • Build AICP (Source AICP updated to 2019-05-21, security update from 5 May 2019).
    2019.05.16
    • In driver Wi-Fi enabled BondingMode (included WCNSS_qcom_cfg.ini with settings).
    • Implemented the ability to reboot into recovery.
    • Increased rear microphone sensitivity (camcorder is now well hears, for voice recorders - use RecForge-II with a choice of rear microphone).
    • Various changes in zRAM and swap (theoretically multitasking would be better).
    • Various changes in driver i2c (sensors will probably stop hanging).
    • Source LineageOS updated to 2019-05-16, security update from 5 May 2019.
    2019.04.08
    • The function of recording a conversation is unlocked and is now available in the dialer.
    • Minor changes and optimizations in build configurations, temporarily added debug of i2c in dmesg.
    • Source LineageOS updated to 2019-04-08, security update from 5 April 2019.
    2019.03.12
    • Source LineageOS updated to 2019-03-11, security update from Mart 2019.
    2019.02.28
    • Fixed problems with the video camera, built-in video camera works fine (video does not twitch, FullHD work).
    • Fixed problems with XTRA/AGPS, searching and fixing satellites is now as fast as on stock firmware.
    • The built-in firewall is fixed and works (in older versions this leads to an error and a bootlap after a reboot).
    • Source LineageOS updated to 2019-02-28, security update from February 2019.


    XDA:DevDB Information
    LineageOS 15.1 (and AICP) for Sony Xperia M2, ROM for the Sony Xperia M2

    Contributors
    f2065, galaxyfreak, Konstantinosj77, sgspluss
    Source Code: https://github.com/f2065

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS

    Version Information
    Status:
    Beta
    Beta Release Date: 2021-06-18

    Created 2019-04-09
    Last Updated 2021-06-18
    4
    New build LineageOS 15.1 published.
    4
    LineageOS 15.1 build 2019-06-16 released:
    Numerous kernel fixes, and LMK reconfigured. The kernel has become better.
    The kernel fixed bugs due to which the Android Go mode worked incorrectly earlier. Android Go is not included in these builds, but now you can enable it.
    3
    New build LineageOS 15.1 published.
    Returned SDCardFS. It was a very long time ago, but in those days because of it there were errors with microSD and they refused SDCardFS (they used FUSE). Now I imported the latest version of SDCardFS, checked for 2 weeks - I did not find any bugs with microSD.


    Does anyone have unexpected reboots (on any previous versions of LineageOS) - once every few days?
    It has always been with me (both in my builds and in old builds of other authors). Now I began to investigate - the reason is the overflow of the sensor buffer. The place of the fall is in the LineageOS source. But the root cause is most likely in our sensor drivers, or in multihal ...
    We need to find patterns - on which revisions of M2 there is this problem.

    Crash log is saved in /data/system/dropbox…
    pid: 922, tid: 3000, name: SensorService >>> system_server <<<
    signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x9d180000
    r0 9d17fe50 r1 9d17fff0 r2 fffb89c8 r3 00000000

    backtrace:
    #00 pc 00018f04 /system/lib/libc.so (memcpy+168)
    #01 pc 0000f431 /system/lib/libsensorservice.so (android::SensorService::SensorEventConnection::sendEvents(sensors_event_t const*, unsigned int, sensors_event_t*, android::wp<android::SensorService::SensorEventConnection const> const*)+448)

    This place is in frameworks/native/services/sensorservice/SensorEventConnection.cpp - android::SensorService::SensorEventConnection::sendEvents на memmove(mEventCache, &mEventCache[numEventsDropped], (mCacheSize - numEventsDropped) * sizeof(sensors_event_t));

    int numEventsDropped = count - remaningCacheSize;
    countFlushCompleteEventsLocked(mEventCache, numEventsDropped);
    // Drop the first "numEventsDropped" in the cache.
    memmove(mEventCache, &mEventCache[numEventsDropped], (mCacheSize - numEventsDropped) * sizeof(sensors_event_t));
    Crash in memmove (memcpy - called inside memmove), due to going out of the segment (i.e. the queue size is incorrect).
    3
    no pie for this phone?
    There were experimental builds of LOS16, it works on M2 but there are minor bugs.
    I don’t have enough space to build LOS16, I need to remove two other builds (LOS14, LOS15, AICP) to build LOS16.
    LOS17 can also be builded, from neighboring (older and low-power models) it was builded…