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

Search This thread

Jordi432

Member
Jul 28, 2015
11
3
0
I'm having problems with this rom now. I updated to latest version but nothing changed. When I boot the phone all is working, but few minutes next the sim card icon shows "no sim", and calling is not possible. Restarting the phone, the sim card is working again for a few minutes, and dissapear again. And always the same.
What is the problem, and have any fix?
 

mantazzo

Senior Member
Feb 3, 2015
204
53
58
Pakruojis
Phone didn't even get Android 9 or 10 so no, no 11 for it. It's a 6-year-old phone now, so it's just time to move on. Or you can still use it for very basic tasks.

Sent from my Redmi Note 8T using XDA Labs
 

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru
Do you have any plan for building LOS 17.1?
There is a plan, but there is not enough time. And I know that everything will be greatly slow down.
Optimal here is LineageOS 14.1

Go-mode I do not like, there are a lot of software is no longer working (background players, autonavigator and road cameras notification).
In normal mode, they all work fine, although of course the phone slows down very much at startup and at exit.

Phone didn't even get Android 9 or 10 so no, no 11 for it.
Android 9 exists, but there are some problems so it is not published.
Android 10, in principle, can also build, neighbors on a similar processor and a similar platform have it for a long time.

I want to make a different kernel, but so far the result is bad…
 

el.corzo

Member
Sep 19, 2017
9
0
11
Frankfurt
And I know that everything will be greatly slow down.
Optimal here is LineageOS 14.1

Let me ask again only to understand you correct : you are the Developer of this LineageOS 15.1 ROM and despite that fact, you personally think that LineageOS 14.1 suits better for this device because Android 7.1.2 would perform better on that old Hardware?
:confused:
 

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru

el.corzo

Member
Sep 19, 2017
9
0
11
Frankfurt
The google documentation, Minimum Memory and Storage (Section 7.6.1), indicates that for platforms with 1 GB of RAM and Android 8.1, Go-mode MUST enabled (flag android.hardware.ram.low).
LineageOS 15.1 Go Edition is fast enough, but Go-mode is not compatible with many programs running in the background.
Therefore, the optimal version is LineageOS 14.1

Thank you very much for your precise explanation. As I see you are also the Developer of Lineage OS 14.1 for Eagle:
https://forum.xda-developers.com/xperia-m2/rom-lineageos-14-1-t3919879
I have looked at your GitHub Repositories. Can you help me to port your 14.1 code to Xperia T3 (Seagull)?
T3 is also Yukon based and some Dev made the first steps: https://forum.xda-developers.com/xperia-t3/testers-development-twrp-lineageos-14-1-t3725791
So I hope it would be only quite-difficult ... :D

I own the real device, have already compiled, flashed, booted and worked with AOSP. Unfortunately stuck with the camera but could not get help:
https://forum.xda-developers.com/xperia-t3/rom-basic-fast-rom-d5103-help-camera-t4109727
It seems T3 is not a very popular device amond devs. So my hope is to find a "Yukon-Brother/Sister" :fingers-crossed:
 

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru
2021.01.18 - For M2 Dual (D2302) – fixed the ability to disable the second SIM in the Settings.
We had a long-standing bug on the M2 Dual - there were no files needed for the options to disable SIM cards in Settings.
I was informed about this recently and has now been fixed.
Report any issues you find, many of them can be fixed.
 
  • Like
Reactions: JuniorCaesar

mstrnemo

Member
Feb 1, 2021
49
3
8
@f2065

Hi i am doing this for the first time and i was just following your steps when i reached this one.
  • Do Factory Reset in TWRP (necessarily, otherwise the installation over the old LineageOS inherits some errors of the old LineageOS). I recommend doing an additional cleaning (this solves the problem with «update error 7»): TWRP – Wipe – Advanced Wipe – Dalvik,System,Cache,Data.
After i do this my phone gets stuck in a bootloop ? what did i do wrong ?
Also i already repaired the software using xperia compgion.

And i cant get into twrp recovery anymore it just gets into a loop. does this mean i have reflash twrp recover?
 

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru
TWRP – Wipe – Advanced Wipe – Dalvik,System,Cache,Data.
After i do this my phone gets stuck in a bootloop ? what did i do wrong ?

After a reset in TWRP, you do not need to leave it, but you must immediately install a new firmware.

If you exit TWRP after a complete cleaning, but before installing a new firmware, then there will be a bootloop, because there is no operating system.
In this case (with a bootlap), you need to turn off the phone (OFF-button near the slots that is pressed with a needle, or by holding Power + VolumeUp for a long time up to three vibration signals), and then turn it on while holding VolumeDown for a normal TWRP entry.

Also i already repaired the software using xperia compgion.
And i cant get into twrp recovery anymore it just gets into a loop. does this mean i have reflash twrp recover?
Flashtool or Xperia Companion reflash the bootloader and remove TWRP.
You need to reinstall TWRP according to his instructions ( https://forum.xda-developers.com/t/...t-discussion-2021-01-18.3923414/post-82966117 )
 

mstrnemo

Member
Feb 1, 2021
49
3
8
Well thank you i am officially an idiot hahaha i jumped the gun anyway everything is ready now gonna try again in a moment.

Thank you for the quik reply

Edit: Well i tried it and it lives!!! hahah it works good , little bit sluggish though while opening apps not much diffrence compared to stock firm 5.1.1.

Thank you for your service!

anyway i am going to try your other rom aisop and the older version maybe also the go variant try some others aswell. i saw in your howto/download page this is fun kinda exciting.
Also i really like your whitepagesite with all the info in one place very handy and organized.

This is a trail run for me i am going to give this phone to a relative.
am gonna put custom rom and try root with another even older phone until finally i am gonna do my better half the other side of the dynamic duo sony xz1 compact.

Edit2
Is it normal that firefox keeps crashing when i try to open it ? does it mean it cost to much ram to open? cause other browers like brave(very fast) and vivaldi i can open en run no problem.

Edit 3
Is there way to delete apps that came with the rom i can only dissable them forexample the browser?

Edit 4
Update I used all the roms in your page and they all behaved the same in terms of speed even the go variants?.After i saw they all behaved the same i wanted so see if they all can run firefox noone could they would all crash when trying to open firefox browser.

however i dont know what happend but i was running 14.1 los and firefox crashed after running it and was playing around with it and i had prevouislly used a stopwatch to test how long it took to open the apps and they al had the same time give or take then i used the batterie saving mode and started noticing the phone got faster? eventhough it says it should slow down it really got noticblly faster smoother when swiping araund and even saves of some time when opening apps compared to the normal mode and then i tried doing it to 15.1 los and then it worked the same slowish in normal mode faster and smoother when using batterie saving mode.
 
Last edited:

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru
Is it normal that firefox keeps crashing when i try to open it ? does it mean it cost to much ram to open? cause other browers like brave(very fast) and vivaldi i can open en run no problem.

Yes. There are some programs that don't work here. The problem is with the kernel and will probably be fixed later.


Is there way to delete apps that came with the rom i can only dissable them forexample the browser?

With root rights, you can delete some apk files. But I do not advise deleting the browser, it is needed, for example, for authorization in some public Wifi networks.


I used all the roms in your page and they all behaved the same in terms of speed even the go variants?

1. In Go-versions, background processes work more economically.
2. The difference is noticeable in multitasking and heavy applications. For example, in Go-versions, the Yandex-map works faster.
3. The transition between regular and Go-firmware has some peculiarities. When installed over the old one - TWRP automatically edits the options of the new firmware by analogy with the old firmware. For the correct transition between Go-version and normal-version, you need to clean up /system /data before installing new firmware
4. After installing any firmware - background cache rebuilding may take several hours. Conclusions about the speed of work should not be made immediately.


however i dont know what happend but i was running 14.1 los and firefox crashed after running it and was playing around with it and i had prevouislly used a stopwatch to test how long it took to open the apps and they al had the same time give or take then i used the batterie saving mode and started noticing the phone got faster?

In saving mode, some of the background services do not work or work less frequently, so the phone is faster.
 
  • Like
Reactions: mstrnemo

mstrnemo

Member
Feb 1, 2021
49
3
8
Thank you for the reply that clears it all up

In saving mode, some of the background services do not work or work less frequently, so the phone is faster.
[/QUOTE]

I thought that was weird that it got faster cause with my daily sony xz1 compact with stock firmware when i turn on batterie saving mode it becomes very slow and almost like stutters hahahahaha.
Cant wait to put a custom rom on it those bastards at sony stopped updating it after only one android version worse they stopt not long after even with security updates.
 

f2065

Senior Member
Sep 5, 2007
214
115
63
Moscow
f2065.ru
I thought that was weird that it got faster cause with my daily sony xz1 compact with stock firmware when i turn on batterie saving mode it becomes very slow and almost like stutters hahahahaha.

For example, new Xiaomi has two levels of battery saving. At the usual level of economy, the interface becomes faster. At a strong economy level, slower.
We will probably also have several levels of savings in the future (this is related to the kernel).
 
  • Like
Reactions: mstrnemo

mstrnemo

Member
Feb 1, 2021
49
3
8
do u still have the time for it? i mean the phone is pretty old now i am sure u have somewhat moved on (I dont know how much time ir takes for u to do the security updates) also u left version 14.1 wich u also still update atleast get rid of that one and fix 15.1 sure that saves some time or get rid of 15.1 and leave 14.1?

are u on any new phones that u are doing custommods work for now?
 

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.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-03-08

    Created 2019-04-09
    Last Updated 2021-03-08
    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…
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone