Related
CM11 nightlies have stopped, but as we all know CM12 isn't fully ready yet either as its still got some bugs, especially as we're waiting for 5.1 sync as well. Would someone like to build CM11 from the latest repo sync? The last nightly was January 5th, and since then there have been fixes that made it to 05Q build of CM11S. It would be nice to have the latest CM11 builds with the latest changes (hint: the CM11 branch still does get some activity....)
You can see the latest CM11 commits here: http://www.cmxlog.com/11/
There are definitely commits since January 5th.
With the Wakelock Issue regarding Play Services 7.x fixed (http://review.cyanogenmod.org/#/c/91881/ and http://review.cyanogenmod.org/#/c/91882/), it would be REALLY nice now if someone could build a fresh CM11 copy.
Bump. I guess everyone's eager to migrate to CM12 and doesn't care about CM11 at all
Why haven't we seen an official CM 14.1 for hammerhead. CM 14.1 official has been released for hammerheadcaf but not regular Hammerhead. I am tired of waiting for an official release, they are dragging their feet like Google did with the original Nougat release. We have seen some unofficial development, but until official development is released network an custom kernel support isn't useful. Every unofficial CM 14.1 release hasn't supported my sim card and a custom kernel with USB fast charge.
Keep patient bro. It'll be released soon (Hope So).
badmashchamp said:
Keep patient bro. It'll be released soon (Hope So).
Click to expand...
Click to collapse
They keep releasing nightlies of CM 13, they need to move on already. Hopefully the CM theme engine is fixed by then also.
Rondeau7 said:
Why haven't we seen an official CM 14.1 for hammerhead. CM 14.1 official has been released for hammerheadcaf but not regular Hammerhead. I am tired of waiting for an official release, they are dragging their feet like Google did with the original Nougat release. We have seen some unofficial development, but until official development is released network an custom kernel support isn't useful. Every unofficial CM 14.1 release hasn't supported my sim card and a custom kernel with USB fast charge.
Click to expand...
Click to collapse
You have to be more patient, you are just simply to inpatient.
CM14.1 is in its early develop stage, things have to settle, the nightly's for the regular version will come when it's time.
Oreo - Mission impossible?
I started studying "O" in early August. All I got were the O-preview3 factory images for qcom and tegra devices which I don't have. Built it out and made it boot wouldn't be too hard but everything seemed different. It took me some time to figure out the flow of the new frameworks. At that time, only the RIL and Graphics sources were really "O". The most devastated situation would be the RIL. Seemed dead end at that time. That was the first time I feel impossible. The source from MTK's RIL made things even worse. All the .c functions are buried inside prebuilt static libraries. Frankly, up to this moment, I'm still not fully understand the workflow of MTK's RIL...
While I was struggling with the RIL, "O" - Oreo was launched. The most helpful info. were also released in source.android.com. Sadly, I can't access this website no more... Never take it for granted for anything. You can loose anything/anyone for no reason. The sources were then completed and took me some times to made it boot "again".
Eventually, I can make the RIL almost fully working recently. Yes!:victory: All I can say is, we are lucky. Our RIL blobs only experience a few crashes which I can managed. I had tried five or six sets of blobs for different MTK chips. Each had different crashes so there is no guarantee that all MTK devices might work...
Last week, I finally figure out how to made the camera work. Seems not "impossible" now so I start this new thread.
I can't start a DevDB now. The response from XDA official is "They can't think of obvious reason". Anyway, I pay for ad-free and still the status shows connection to axx.amazon-adsystem.com. It just hang there for minutes (until timeout I suppose). However, I can start a normal thread (after minutes of delay) and that's not a problem to me. I already learnt to live with so many obstructions now. :cyclops:
There were just too many distractions and ridiculous people out there. I don't want to waste time arguing so I would make it short this time. I rather spend time on something I'm good at.
For those who want help, no matter its ROM related or about development, please don't use PM. There are many limitations with PM. Do it formally. Start a thread in Q/A or post with all the details you can get (log, kmsg, screenshot, etc.). It's no harm for more opinions. Hiding in the dark doesn't help.
Current Status
KERNEL
Patch: Binder and sdcardfs update are required and essential for Oreo.
See commits in my github for detail
AUDIO
Recording: Working
Playback: Working
Patch: Load a copy of the struct instead of the pointer to address.
BLUETOOTH
Working
Issue: Workflow issue in BTIF driver.
Patch: New driver and HAL build from source.
CAMERA
Flash/Torch: Working
Capture: Working
Issue: User handle is required in GetMemory. MTK blobs return null.
Patch: Save a copy of the user handle. Don't know if other devices might work or not. It's better to rebuild a few blobs but I don't have the source for my device...
Issue: Oreo use a ring buffer of native_handles and no more ANativeWindowBuffer.
Patch: A wrapper is required for the libcam.client. (The better way would be rebuild it but again no source...)
HDR: Working with Snap in LOS-15.1
Video recording: Working
Issue: Oreo doesn't support GRALLOC (or I don't know how). The old HAL1 implementation doesn't work too.
In short, need to find a way for the metadata that our old blobs can handled.
Patch:
1. Add libcamera_parameters_mtk for the MTK extra parameters
2. Add another mode to handle Gralloc in stragefright.
3. Patch the OMXNode to handle Gralloc mode.
4. patch the OMXClient to use mediaserver
5. Patch the hardware interface to handle Gralloc Metadata and work with the new OMX interface.
DISPLAY/TOUCH SCREEN
DT2W: Working
FM RADIO
Working
GPS
AGPS: Working
GPS & BEIDOU: Working
GLONASS: Enabled by default
GRAPHIS
HWC: Working
Issue: Android platform changed
Patch: A simple patch in libgui_ext (might use shim if timestamp proved no use)
OpenGL: Working
LED
Notifications: Working
Charging: Working
Low power: Not Working
See Post #806 for detail. Haven't study why --pending
MEDIA
Video Playback: Working
Hardware decoder: Working
Issue: crashed
Patch: A small patch in minijail use Asan.
POWER
Power off charging: Working
RIL
Phone calls: Working
Mobile Data: Working
SMS: Working
Dual SIM: Working
Issue: Completely new approach in Oreo with interface/services. No more sockets. AND all .c libraries are proprietaries.
Patches:
1. Replace the MTK RIL daemon with AOSP patching for MTK
2. Wrap (eventually replaced) the libril from MTK with AOSP patching for MTK
3. Patch the RIL interface/service to work with the MTK vendor library.
Some more detail can be found in post #65 and post #806
SENSORS
All sensors are Working
Patch: Lower the requirement from 1.3 to 1.0
WIFI
ap,p2p: Working
Miracast: Working
Noted: only work on 2.4G as before
Hotspot: Working
Hidden SSID: Not support
No idea why yet. --pending
Sources
Github
Download :highfive:
Experimental: AndroidFileHost
OmniROM: AndroidFileHost, 百度网盘
LineageOS-15.1: AndroidFileHost, 百度网盘
Install :fingers-crossed:
Flash with the latest TWRP
1. Factory reset
2. Flash ROM
3. Flash SuperSU (tested ver.2.82)
4. Reboot and setup wifi
5. Flash Gapps (tested opengapps 8.1)
Change Log
Code:
[B][COLOR="Blue"]2018/10/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r46 (OPM4.171019.030.K1)
- New build enviornment
- Security patch Sep. 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/8/11[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r42 (OPM4.171019.021.Y1)
- OmniLib is updated
- Security patch Aug. 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/7/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r36 (OPM2.171026.006.H1)
- SELinux Enforcing
- Security patch July 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/6/26[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r30 (OPM2.171026.006.C1)
- SELinux Enforcing
- Add/Fix SEPolicy rules for GPS, camera, Video, etc.
- Security patch June 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/6/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r32 (OPM4.171019.021.E1)
- OmniLib is updated
- A few bug fix in Omni Apps
- Security patch June 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/5/18[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r28 (OPM4.171019.029.B1)
- Security patch May 5, 2018
- chromium-webview update[/INDENT]
[B][COLOR="Blue"]2018/5/11[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r26 (OPM2.171019.029.B1)
- Security patch May 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/4/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- fix vendor image mismatch warning
- fix a few security issues in reading NVRam
- chromium-webview update[/INDENT]
[B][COLOR="Blue"]2018/4/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- Security patch Apr. 5, 2018
- adjust some memory defaults
- handle the build flags for MTK devices (to live with other devices in the same source)[/INDENT]
[B][COLOR="Blue"]2018/4/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- Security patch Apr. 5, 2018
- HDR broken in this build. Check [URL="https://forum.xda-developers.com/showpost.php?p=76174760&postcount=612"]post #612[/URL] for the fix patch[/INDENT]
[B][COLOR="Blue"]2018/3/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r15 (OPM1.171019.021)
- Add Device Features support in OmniGears
- Device Features: Display Color Adjustment is added[/INDENT]
[B][COLOR="Blue"]2018/3/9[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r15 (OPM1.171019.021)
- Workaround for Proximity sensor in InCall screen
- Settings: LiveDisplay is supported now[/INDENT]
[B][COLOR="Blue"]2018/3/2[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- The patch for codec and power off charging animation included
- Workaround for Proximity sensor in InCall screen
- HDR support with Snap porting to OmniROM[/INDENT]
[B][COLOR="Blue"]2018/2/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- All previous fixes in Omni-8.1
- HDR support with Snap port
- Patch for MTK soft codec[/INDENT]
[B][COLOR="Blue"]2018/2/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- Fix Lockscreen settings
- Minor patch in video recording to make it more stable
- update codec conifg
- check [URL="https://forum.xda-developers.com/showpost.php?p=75609953&postcount=338"]post 338[/URL] for the codec and power off charging animation patch[/INDENT]
[B][COLOR="Blue"]2018/2/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Source is sync to the latest Omni-8.1
- userdebug build.
- Native Video recording is fixed. [COLOR="Red"][B]Edit[/B][/COLOR]: check [URL="https://forum.xda-developers.com/showpost.php?p=75488295&postcount=273"]post #273[/URL] for the camera patch
- Phonograph and equalizer are also fixed.
- MP3 and FLAC can be played now.
- GPS: Enable GLONASS by default [/INDENT]
[B][COLOR="Blue"]2018/1/21[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Security patch Jan. 5, 2018
- Add Messaging apk
- Add FM radio apk
- Add the forgotten vibration support
- RIL: Fix a bug in carrier info.
- Clean up the internal log I added. [/INDENT]
[B][COLOR="Blue"]2018/1/7[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Initial release
- Security patch Jan. 5, 2018
- New Bluetooth driver and HAL.
- Kerenl: a few minor patches[/INDENT]
[B][COLOR="Blue"]2017/12/30[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.1[/B]
[INDENT]- The latest Carbon CR-6.1 source, Android-8.1.0_r1 (OPM1.171019.011)
- Cumulated patches from LOS-15.0
- Security patch Dec. 5, 2017[/INDENT]
[B][COLOR="Blue"]2017/12/22[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
[INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
- libsuspend: add earlysuspend support
- Kernel: tidy up lenovo features source
- DT2W: working now[/INDENT]
[B][COLOR="Blue"]2017/11/20[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
[INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
- Kernel: remove obsolete Lenovo features
- Mediaplayer: fix video playback
- Camera: Add mode to handle MetaDataGralloc in video recording. (only audio working now...) WIP[/INDENT]
[B][COLOR="Blue"]2017/10/23[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.0[/B]
[INDENT]- The latest Carbon CR-6.0 source, Android-8.0.0_r15 (OPR3.170623.008)
- Alpha test build[/INDENT]
Known Issues
- May be a few...
Donations :angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huge respect.
Subscribed to this thread. I am unable to provide any help for now and will start using the Oreo build as soon as it can do the basic stuff for daily use (despite the bugs).
I appreciate all your efforts bro. Many people are reading you. When you release something that can be a buggy daily version I can start giving feedback. For now I will just read because my K3 is my only device.
Huge respect.
bugs-deep sleep mode,proximite-Vanillamusic not work,JetAudio-work
Any Mission is possible with you :laugh:
Thank You for developing. Please provide us a stable rom ASAP
Thanks
Daniel, you're one of the hardest working developers I've ever encountered. Many would perceive this device as a dead device but you're the one who gives a new life to this, keep up your amazing work and if you need anything we're all here for you.
Updated
@daniel_hk
The carbon is SICK man!
I can report that apart from the known issues, there's:
1. Unable to install apps when rooted. Solved by flashing magisk in TWRP, then clearing Data, Cache and Dalvik. Also dirty flashing from nougat will recovery-loop your phone!! . Always clean flash your rom guys
2. Some mp4s can be played yet some shows "can't play this video" error. I can't be sure whether it's the decoder or just the mp4 s.
3. All tried mp3s can be played only after flashing the codec you provided here :silly:
4. Camera can perform photo taking and very poor video recording using 3rd party apps. Maybe the handling of the 3rd party apps enabled them to connect to the sensor.
5. After flashing GApps, there are two Android Shared Library 1 as system apps . No force close or conflict encountered though.
6. Battery drain just a little too fast. Didn't encounter that before with android 7 but maybe it's the kernel or Oreo policies itself.
7. Proximity sensor is nonexistent. Used sensor box to check with no avail. It said that the phone's hardware does not support the sensor.
8. Used google camera's HDR+ feature with successfull result, sort of. Snap and stock camera freezes right after snapping HDR with no avail.
I made this post to help those who are trying to learn and appreciate Oreo.
I'm new to this community. Hope to help as best as I can. Overall, the rom is enough for me as daily drive for now :good:. If I find anything more I'll be sure to share them here. Maybe just need to figure out the deep sleep bug for now.
How to install this rom. can anyone pls tell me the procedure how to install this rom, so that i don't find my phone in bootloop.
Why Oero, not Oreo? ?
bedoedeyne said:
Why Oero, not Oreo? ?
Click to expand...
Click to collapse
Brother, I know he done typo mistake but we are respectful to him because he is working hard to give us Oreo update. You can show his typo mistake without laughing on him.
Ashwinrg said:
Brother, I know he done typo mistake but we are respectful to him because he is working hard to give us Oreo update. You can show his typo mistake without laughing on him.
Click to expand...
Click to collapse
Oh no bro. I always respect him :fingers-crossed:
But you can look at his avatar and that word. It made me smile
sudip_55 said:
How to install this rom. can anyone pls tell me the procedure how to install this rom, so that i don't find my phone in bootloop.
Click to expand...
Click to collapse
You should rather go to @daniel_hk 's thread for Nougat. He said if you aren't familiar with the procedure, you aren't ready for this and I wouldn't recommend trying to install it if you are afraid of breaking your phone.
- Aresmo
Updated bug and workarounds
Hey guys I've updated my list of bugs and workarounds here. Be sure to read it before installing this ROM just so you don't brick your phone :silly: .
I created the post to help those who want to learn and appreciate Oreo
Arjunism said:
Hey guys I've updated my list of bugs and workarounds here. Be sure to read it before installing this ROM just so you don't brick your phone :silly: .
I created the post to help those who want to learn and appreciate Oreo
Click to expand...
Click to collapse
Hi arjun thanks for the bug list and apart from that can you please tell me the installation steps how to install this rom in the phone so that the phone doesn't go into bootloop.
sudip_55 said:
Hi arjun thanks for the bug list and apart from that can you please tell me the installation steps how to install this rom in the phone so that the phone doesn't go into bootloop.
Click to expand...
Click to collapse
Go to custom recovery (TWRP Recommanded) click on wipe and advanced wipe. Tick on dalvik/art cache, cache, data and system and swipe to format. Click on install and navigate to rom zip that you want to install. Select and swipe to flash.
Hey guys I am in need of stable ROM for few days ..
I always flash the latest ROM available but I have to go for holidays any feature pack ROM that you can you guys can recommend please
Go for aosp 4.6 official from blitzfire.
For Oreo video recording use camu app its working
Hi daniel
No any new thing about O
Very much looking forward to android O Coming .
thanks your hard work!
Here is the list of the following ROMs that are already made and will be released soon. And also some others that haven't been worked on yet, and will be released soon. I want to release all of these before I retire from making Android ROMs (I may continue in the future). I have been talking about this at school, a teacher finds if it cool that I work with Android. And I have been thinking about this for a while now. It has been taking a lot of my free time. Sorry guys for bringing the bad news. When I quit, I will be putting in the latest security patch. So, when it hits Feb 2018, I will be uploading the last security patch to the following ROMs listed below in the near future (Except the CM 12.1 Based ROM). Thank you for understanding.
1.) LineageOS 11 (No longer coming)
2.) CM 12.1 Based ROM (ROM lost, can't find it, not coming)
3.) CyanogenMod 14.1 Based ROM 1 year update (Coming Feb 2018) (If you want to see a trailer of the update, let me know in the comments)
4.) Over Clocked Stock ROM (Coming soon)
5.) TriangleOS KK update 2 (No longer coming)
6.) CM 11 Based ROM update
7.) SlimKat Based ROM (Too many bugs, most likely it won't come)
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.12.28
Source LineageOS updated to 2021-12-28.
2021.10.17
Source LineageOS updated to 2021-10-17, security update from 5 October 2021.
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-12-28
Created 2019-04-09
Last Updated 2021-12-28[/LIST]
Reserved
Reserved
Reserve
thank you for maintaining this device
one small thing, i think you should add @galaxyfreak @Konstantinosj77 and @sgspluss in the contubitors list
i am daily using my eagle to see how he handles light usage on this rom, and it is pretty good. there are visual lags when you switch between apps or launching apps (thats totally expected from 5 year old mid tier (now low-tier) phone, running new version of android). i have one problem though, and it happened on previous builds of 15.1 too, after some time equalizer kills itself and i can't get it work until i reboot the phone. also sometimes my phone ignores my sim card (popping it out and inserting it solves this), also this happened on 7.1.2 roms.
overall, i can say it is usable, you can enable android go mode if you want, it improves performance a lil bit. but i suggest 14.1 as it performs better compared to oreo. also do not flash gapps on this little fella it can't handle it lol
thank you for providing updates for our eagle do not let dis guy die
edit: using airplane mode overnight causes "No Service" issue
First of all, thanks for keeping the device updated. It means a lot
Anyway. Right now I have installed your AICP build and I want to report everything working well so far, performance is decent even with nano gapps, no major glitches or hiccups. Magisk also works as it should, though if you want to update/install something you need Magisk Hide disabled, but after installing you can just re-enable it safely. I would say this works even better than RR, but then again, some very advanced settings might be missing.
(Also sorry for posting the stuff here, since there was no dedicated topic for that ROM, I guess it is okay to post some stuff here?)
Sent from my Xperia M2 Aqua using XDA Labs
mantazzo said:
since there was no dedicated topic for that ROM, I guess it is okay to post some stuff here?)
Click to expand...
Click to collapse
They have the same source, so all the bugs and changes in LOS 15.1 and AICP 13.1 are the same.
AICP continued to update the old Oreo, I think that in may-2019 (after the Android Security Update is done, usually by the middle of the month) we will have a new AICP-Oreo build along with LOS-Oreo.
But the RR-Oreo is not updated.
f2065 said:
They have the same source, so all the bugs and changes in LOS 15.1 and AICP 13.1 are the same.
AICP continued to update the old Oreo, I think that in may-2019 (after the Android Security Update is done, usually by the middle of the month) we will have a new AICP-Oreo build along with LOS-Oreo.
But the RR-Oreo is not updated.
Click to expand...
Click to collapse
It's a pity RR is not updated, I use it as a daily driver and I love it.
Thanks for maintaining the device
JORGETECH said:
It's a pity RR is not updated
Click to expand...
Click to collapse
What are the advantages of RR over AICP?
AICP has about the same large part of additional options.
f2065 said:
What are the advantages of RR over AICP?
AICP has about the same large part of additional options.
Click to expand...
Click to collapse
Oh, if it has the same or more features then I don't care
EDIT: Is the I2C bug serious enough for being a reason not to upgrade to Oreo in this moment?
New build LineageOS 15.1 published.
Hello! When you are allow to download?
"The site is temporarily closed for maintenance, come tomorrow."
im stuck rooting this device at SuperSU binary update
.
.
.
already fixed, my bad, i just need to flash that supersu zip files
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.
My honest review : This ROM have really good battery life, almost 24 hours still on. but when im using it for daily driver for opening apps its really slow, changing one app to other app slow too, i cant tell why. but i really appriciate the job, no bug, almost stable, but real annoying loading apps
NieeLz said:
but real annoying loading apps
Click to expand...
Click to collapse
It depends on the programs used (and installed!). Some users complain about this.
Sometimes cleaning up the Recent App helps.
The solution is to use Android 8.1 Go mode, there is no such problem there. But there are other problems there ... Probably in July-2019 there will be a public build in Android Go mode.
According to the Google specification for 1GB of RAM, it should be Android 8.1 Go mode.
But it looks ugly (lag scrolling in web browsers, It lacks some features, background tasks work more rarely)…
Upd:
You can try to change in build.prop dalvik.vm.heapgrowthlimit. Instead of 96m, put 128m.
It helps some.
also do not forget this phone falls into low-end segment nowadays so don't expect 1 second loading times. downgrading apps to their 2017-2018 versions can help.
AND do not use gapps, use microg instead or ditch google stuff altogether
Huh, I don't know tbf what are you expecting from this phone, which is now 5 years old, originally. I think first of all we should be thankful to the devs who worked with this device, so that we now have Oreo still running on this phone.
Anyway, regarding my experience - still good so far. I'm currently using AICP May release, and everything works good so far, speed is very much acceptable for a device this old, and since it's still my main phone it's daily usage is nice (nowadays mostly Messenger Lite stuff, but also occasional Snapchating, but else mostly Reddit-Twitter-Browsing or taking pictures/videos).
Though not sure why or how, but I think my Reboot to Recovery broke - it worked after fresh install once or twice after I tried, but now if I try phone restarts, phone tries to enter recovery, but only led flashes orange (mostly orange), then it restarts again to normal. Strange.
And yeah, Magisk 19.3 still works, just need to disable MagiskHide if you want to install/update apps and restart after that. It does work with it enabled also if you don't plan to update apps for a bit.
Edit: Fixed a few typos.
Sent from my Xperia M2 Aqua using XDA Labs
JuniorCaesar said:
also do not forget this phone falls into low-end segment nowadays so don't expect 1 second loading times. downgrading apps to their 2017-2018 versions can help.
AND do not use gapps, use microg instead or ditch google stuff altogether
Click to expand...
Click to collapse
Why microg over gapps?