Related
Hi,
I'd like to know if we might get an AOSP based ROM like Resurrection Remix or Lineage OS someday. Anyone working on something?
I really hate TouchWiz my phone seems clunky with it.
Thanks in advance
PS: not asking for an ETA btw just if we might get something within say a year
Edit: talking about A5 BTW
i think that the better thing is to contact Lineage for ananswer ....
without Lineage ( same with cyanogenmod before) there are not customs roms because these teams use Lineage work .
The another way for customs devs is to use AOSP google sources and phone three sources (not builded for thos phone at this time ===> it's loooooong and hard to build this source itself it need knowledges and generaly all teams and others devs use these ones already built by lineage with manufacturers like samsung sources)
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
Project Treble [Pie] For XZ Premium
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards.
请中文用户遵守XDA规则，使用双语留言
Required files:
[Non-Tested]
[Tested]
V1.06-Patch:Link
You can replace the same file in /system/vendor/etc with V1.06-Patch, this patch could improve the performance a lot.
V1.05:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V1.0:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V0.95:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V0.93:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_yoshino.zip
V0.85:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.zip
EDIT: AEX 6.2 and Magisk works fine with V0.85, with Disable ForceEncrypt @LSS4181
V0.8:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.zip
V0.3:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_YOSHINO.ZIP
V0.2:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_YOSHINO.ZIP
V0.1:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V3_YOSHINO.ZIP
Twrp:Link
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < DIR of recovery.img >
Second: flash Treble-xzp-VX.X.zip in Twrp .
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < DIR of OEM.img >
Fourth: Flash a GSI compatible System image and boot!
Update and known BUG:
V1.05:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back.
3. F2FS support for cache(Qnovo) and userdata partitions.
V1.0:
Fix:
1. Source code update.
2. Cancel 90Hz.
3. Support Erfans's Android Q GSI.
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
Bugs:
Need to feedback.
V0.95:
Fix:
1. Source code update.
2. 90Hz Screen frame rate.
Bugs:
Need to feedback.
V0.85:
Fix:
1. Revert to HMP to get better performance.
2. Magisk Fix.
Bugs:
Need to feedback.
V0.8:
New feature:
1. Kernel EAS support.
2. Camera HAL3 support
3. Crosshatch HAL.
Fix:
1. Sleep dead bug totally fixed.
2. Camera disconnect bug fixed.
Bugs:
1. Magisk FC.
V0.3:
Fix:
1.Sleep dead bug should be fixed, tested on PE 9.0 GSI.
Bugs:
1.Camera disconnect after screen-off.
V0.2:
Bugs:
1. May sleep dead.
2.Camera disconnect after screen-off.
V0.1:
Bugs:
1. Wifi is broken(Only G8142).
2. USB connection is broken.
3. May sleep dead.
XDA:DevDB Information
Treble For XZP, ROM for the Sony Xperia XZ Premium
Source Codes
Link
Contributors
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2018-12-20
Last Updated 2019-08-12
wow awesome I will definitely look into this, im pretty curious about how did you did it and also this could be something big for our devices thanks!!
酷安来的支持大佬！！??
Awesome job thanks!
It's like a Christmas present
用这么多the显得不自然啊（#滑稽）
leiersai said:
用这么多the显得不自然啊（#滑稽）
Click to expand...
Click to collapse
发的时候太匆忙了，没有来得及润色（笑）。
leiersai said:
用这么多the显得不自然啊（#滑稽）
Click to expand...
Click to collapse
大佬牛逼，666
---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------
ddwf said:
大佬牛逼，666
Click to expand...
Click to collapse
回错人了，哈哈……
Awesome! You Made me very Happy. Now can i fully Focus on Treble Development! I will Support You with Feedback and maybe some possible Bug fixes. Keep Up the Work, you did a great start for now!
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Beetle84 said:
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Click to expand...
Click to collapse
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Miustone said:
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Click to expand...
Click to collapse
AEX is working nicely so far for me, this is a gamechanger for the XZP, I was beginning to look at new handsets but not for a while now.
WiFi working fine for me on G8141.
Miustone said:
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Click to expand...
Click to collapse
is it possible to port dsee-hx and noise canceling on other ROMs?
Beetle84 said:
AEX is working nicely so far for me, this is a gamechanger for the XZP, I was beginning to look at new handsets but not for a while now.
WiFi working fine for me on G8141.
Click to expand...
Click to collapse
Same here in all Points. What a nice Gift to the Holidays My XZ Premium feels like a actual Device again. Think i'll get one for My GF too. The Prices are low atm and it's just a Solid Piece of Hardware combined with Treble. Was thinking about Xiaomi for her but the G8141 plays Out the Most actual Devices in the Price Range (~300€). Only real Upgrade for me could be a XZ3 but looks like that has to wait now...
Edit. Think the XZ Premium has the better Design and Speaker Layout. But damn, i would Like to have a 1440p OLED SONY ?
@OP
Could You add the Vendor Partition to the Wipe Menu ,and System and OEM/Vendor Options in the Image Flash Menu from TWRP? I have that Options on My Axon 7 (OKI Labs TWRP Mod from XDA). I'm also unsure if the AROMA TWRP Patch Out of this Forum is already included. The TWRP Versions we use is a bit older i think (3.1.xxxx).
Everything besides Bluetooth is working really Well. Performance is a lot better compared to My Axon 7 and more will be possible after playing around with the Vendor Content. Great Base to Play with!
Thanks again! I'll spent a Coffee next Year!
Just modified the source codes and complied it.
@Miustone how's the camera in our XZP with AEX? Is it still as 'grumpy' as it was on Oreo?
I remember you working on enhancing the camera for AOSP.
ricardo99831390 said:
wow awesome I will definitely look into this, im pretty curious about how did you did it and also this could be something big for our devices thanks!!
Click to expand...
Click to collapse
Just modified source codes, and compile it.
Beetle84 said:
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Click to expand...
Click to collapse
Hope you can enjoy it.
Miustone said:
Awesome! You Made me very Happy. Now can i fully Focus on Treble Development! I will Support You with Feedback and maybe some possible Bug fixes. Keep Up the Work, you did a great start for now!
Click to expand...
Click to collapse
The SODP team has done a lot of work on Pie GSI compatibility. I just use the existed partitions and modified source code to make treble works on XZP.
william84 said:
@Miustone how's the camera in our XZP with AEX? Is it still as 'grumpy' as it was on Oreo?
I remember you working on enhancing the camera for AOSP.
Click to expand...
Click to collapse
It is much better right now. Full Camera 2 API Support including RAW and with the right APP like Open Camera do You have full Control of everything. The Sleep Dead Bug is with AEX no problem btw. Just enable the Always on Display Option and it will never sleep. Battery is pretty good and i get over the whole day with LTE+, Wifi and 4hrs+ Display usage. The Treble Kernel is really good and with some fine tuning with Kernel Adiutor is everything even better
I'm playing right now with the Vendor Partition eg. the build.prop and gained already some nice optimizations like better responding Ok Google Commands and better Noise Reduction. I think there will come soon some good stuff to Treble on our Xperias :fingers-crossed:
Miustone said:
It is much better right now. Full Camera 2 API Support including RAW and with the right APP like Open Camera do You have full Control of everything. The Sleep Dead Bug is with AEX no problem btw. Just enable the Always on Display Option and it will never sleep. Battery is pretty good and i get over the whole day with LTE+, Wifi and 4hrs+ Display usage. The Treble Kernel is really good and with some fine tuning with Kernel Adiutor is everything even better
I'm playing right now with the Vendor Partition eg. the build.prop and gained already some nice optimizations like better responding Ok Google Commands and better Noise Reduction. I think there will come soon some good stuff to Treble on our Xperias :fingers-crossed:
Click to expand...
Click to collapse
Cheers for the always on display tip, aex will be my daily driver now.
I'm a total newbie at building android roms. Recently I've been trying to build crDroid 5.1 for my beloved LG G3 D855. I've been using the crDroid build script I've found on Github ( https://github.com/crdroidandroid/crdroid_build ) - at first I failed but finally I was able to build successfully.
After installing my ROM I experienced issues with bluetooth (does not turn on) and with the sensors (e.g. brightness and rotation do not work). Since these features work if I use the last crDroid build from @firebird11 I guess it is a problem with my roomservice.xml, maybe there are some dependencies missing? I've appended my roomservice.xml below.
Any help with this is very much appreciated
@rc00 Have you been able to build successfully for d855 by now?
Maybe you could get some guidance from the current crDroid maintainer.
https://forum.xda-developers.com/showthread.php?t=3856358
ROM[d85x,f400,g3ds,ls990,vs985][9.0]**crDroid**[5.0]
LG G3 D851, PAC-ROM 6.0.1, MultiROM, XDA Legacy
I've been asking for instructions in that thread already, but I've not gotten any answer yet. But since I've read that firebird11 is occupied with non-android-related stuff at the time and there are lots of other capable individuals here I thought maybe someone else knows I'm still working on geting my builds stable but didn't make any progress so far
I don't exactly know where to look to find any clue what is wrong with my build. I started by reading LogCat entries that are related to bluetooth and sensors, but those didn't really get me anywhere yet. Though after some testing I also realized that my device feels much slower than usually, for example camera startup and flashlight usage take longer. I'll keep investigating...
Hi all, i have been trying for a few days to compile android 8.1 from source for my moto z2 play, mostly as a learning experience. I have mostly been following the guide on the official AOSP webpage and save from a few problems with getting the proprietary blobs and the device tree it has been mostly smooth sailing, except for this error. When i try to run make -j4 it runs ok for a while and when it starts including the Android.mk file in system/sepolicy this error springs up. I tried looking in the sepolicy/private directory but although there is a bunch of files, there is only one dir.
Any help will be appreciated and just in case, explain them to me like i'm five, because in this topic, i might as well be.
marcost22 said:
Hi all, i have been trying for a few days to compile android 8.1 from source for my moto z2 play, mostly as a learning experience. I have mostly been following the guide on the official AOSP webpage and save from a few problems with getting the proprietary blobs and the device tree it has been mostly smooth sailing, except for this error. When i try to run make -j4 it runs ok for a while and when it starts including the Android.mk file in system/sepolicy this error springs up. I tried looking in the sepolicy/private directory but although there is a bunch of files, there is only one dir.
Any help will be appreciated and just in case, explain them to me like i'm five, because in this topic, i might as well be.
Click to expand...
Click to collapse
Join Moto Z2 play telegram group, there are few developers who can help you.
Nikhil5143 said:
Join Moto Z2 play telegram group, there are few developers who can help you.
Click to expand...
Click to collapse
Thanks for answering
Can i get some sort of link or something? Never used telegram before