OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm
Reserved #1
Reserved #2
I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.
thanks
ROM is very smooth and fast. Works much faster than CM11.
Very thanks
@psyke83 omni rom will be used kernel 3.×.× as per source given above.
@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.
Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?
Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.
Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least
Can Someone reupload this?
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.
Central project page
https://forum.xda-developers.com/xperia-xz2/development/rom-lineageos-17-1-t4044653
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
How is the fingerprint sensor responsiveness as compared to the stock android 10? This is the biggest grip coming from 9 to 10, it's almost useless if the screen is off.
SODP and STOCK using different drivers
Here the FP is fast.
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
Wait for the OEMv9c release
Don't use it with OEMv9b
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.
I unlocked the bootloader few days ago, after 1 stock year, and I'm trying the official LineageOS (the other one thread).
MartinX3 said:
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.
Click to expand...
Click to collapse
Hi Martin,
I'm testing stock based LineageOS since two days.
Unfortunately this rom works better for me; everything is working. (no matter if it's official or not)...
- the rom is fasterrrrrrrrrrr. It's just like you had a 3/4 year old phone and you by a flagship...
- Lte 2.25Mbps / 141Mbps.
- There was a lot of distortion in my speaker with Whatsapp calls. It was unusable.
- Notification led was most of time not blinking for new notification.
- Sometime my touch screen gets mad. When I tipped one time a letter it wrote me 2 or 3 time the same letter or the status bar was scrolling down...
- Waking up the phone with fingerprint was not possible.
I really appreciate all your efforts to be the first to port LineageOS for our XZ2C. Thank you very much, for your willingness to quickly answer our (sometime noob) questions.
This post must no sound like a good bye, if you EOL the SODP based LineageOS tell me witch is the next smartphone you'll buy so I'll be sure they will be a LineageOS ported
EDIT : where is the "PINT" Smilies ???!!!
Raphos said:
Hi Martin,
I'm testing stock based LineageOS since two days.
Unfortunately this rom works better for me; everything is working. (no matter if it's official or not)...
- the rom is fasterrrrrrrrrrr. It's just like you had a 3/4 year old phone and you by a flagship...
- Lte 2.25Mbps / 141Mbps.
- There was a lot of distortion in my speaker with Whatsapp calls. It was unusable.
- Notification led was most of time not blinking for new notification.
- Sometime my touch screen gets mad. When I tipped one time a letter it wrote me 2 or 3 time the same letter or the status bar was scrolling down...
- Waking up the phone with fingerprint was not possible.
I really appreciate all your efforts to be the first to port LineageOS for our XZ2C. Thank you very much, for your willingness to quickly answer our (sometime noob) questions.
This post must no sound like a good bye, if you EOL the SODP based LineageOS tell me witch is the next smartphone you'll buy so I'll be sure they will be a LineageOS ported
EDIT : where is the "PINT" Smilies ???!!!
Click to expand...
Click to collapse
Thank you very much for your friendly critics.
About the next phone, it depends when my XZ2 got damaged and if I am unable to repair it.
24.08.2020
Since we have now an official LineageOS based on stock, this ROM would be double work.
So I stop the LOS port.
(Sadly unless a dev owns a XZ2P or XZ3 these phones won't be supported in the official stock based LineageOS)
The only difference between the stock and SODP editions are:
SODP will get GCAM support later and has camera2API level 3.
stock will never support GCAM apps and has the limited stock camera2API level.
SODP uses a 4.14 kernel and probably get mainline support later.
stock uses the stock 4.9 kernel and will probably be there forever.
SODP targets to use as much open source as possible.
And LiveDisplay doesn't work in my SODP version.
PS: After the September exams in the new semester I look for a ROM replacement for the sake of diversity.
It's good to have a choice and with the available official supported SODP based Pixel Experiment, we have a ROM which sadly forces you to use the full GAPPS (Google Apps package).
Click to expand...
Click to collapse
24.08.2020
Since we have now an official LineageOS based on stock, this ROM would be double work.
So I stop the LOS port.
The only difference between the stock and SODP editions are:
SODP will get GCAM support later and has camera2API level 3.
stock will never support GCAM apps and has the limited stock camera2API level.
SODP uses a 4.14 kernel and probably get mainline support later.
stock uses the stock 4.9 kernel and will probably be there forever.
SODP targets to use as much open source as possible.
And LiveDisplay doesn't work in my SODP version.
PS: After the September exams in the new semester I look for a ROM replacement for the sake of diversity.
It's good to have a choice and with the available official supported SODP based Pixel Experiment, we have a ROM which sadly forces you to use the full GAPPS (Google Apps package).
Click to expand...
Click to collapse
Hi, i have flash the rom and everything works fine.
But even though I got root with magisk I can't uninstall system apps as the system folder doesn't have RW permissions.
I can't even install TWRP because at every boot it always enters the lineage recovery.
Can someone help me?
I'm sorry for my english
andreux481 said:
Hi, i have flash the rom and everything works fine.
But even though I got root with magisk I can't uninstall system apps as the system folder doesn't have RW permissions.
I can't even install TWRP because at every boot it always enters the lineage recovery.
Can someone help me?
I'm sorry for my english
Click to expand...
Click to collapse
Please remount the systempartiiton as RW in android.
Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.
EDIT:
.....
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc(89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
.....
Someone can help me?