Related
What is the difference?
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
THIS IS A UNOFFICIAL VERSION BECAUSE IT CAN'T BE BUILT AT OFFICIAL SERVER! I just want you know Mokee and other AOSP ROM can't be official unless alberto96's lineage os be official.
I won't have time to update it anymore,you can use my source to continue it.See you next summer,everyone.(if nobody want to continue it,I will update it mouthly.(Sometimes weekly)
About
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Credits:
Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,
Smartisan Digital Co, Substratum Development Team, The Open GApps Team.
ContributorErag0n(Migrate source from Lineage OS and build a zip) @sunilpaulmathew(Thanks for his suggestions and reply, most importantly, his awesome Kernel source.) @Alberto96(all hard work)
Features
1.Fully OMS Supported
2.Xposed Framework Supported
3.Can make a dirty flash which Lineage OS can't.
4.Phone & Messaging:Quick contacts look up, speed dialing, caller location and other useful features
5.Colorful Themes:Unleash the creative side of you, customize how your phone looks; make it cool, make it colorful!
6.Smart Controls:Increase your productivity with Active Display, Lockscreen Notifications and other shortcuts
7.Power Saver:With our unique battery saving strategies, get the most out of your phone's battery
8.Latest source merge from google android source.
9.Minimal but not simplify.
10.Delta update:8~15Mb, more than 300mb download space saved.
11.OTA Update
12.Odexed
Supproted Devices
ja3gxx(GT-I9500),ja3gchnduos(GT-I9502),jaltelgt(SHV-E300L),jalteskt(SHV-E300S/K),ja3gduosctc(SCH-I959).
After Odexed,ROM may have a large size(600~700MB),but it can get a better improvement.
Enjoy it!
Change logs:
MK60.1-8.13
Alpha build,this build is a stable RELEASE version,what is RELEASE?Please see the first line of post.
MK71.2-7.23
First build,sync to latest Mokee Source.
MK71.2-7.24
Second build, sync to lastest Mokee Source, Delta update available, Automatical translation, charger:fix small capture font.
MK71.2-7.25
Sync to lastest Mokee Source, change pixel launcher to default launcher, new kernel merged, now you can use Kernel Adiutor to custom kernel governor.
MK71.2-7.25-17.06
Fixed all bug, include high sensitive screen, display mode, novbar.Alberto not fixed bug I unable to fix.
MK71.2-7.26
Sync to latest source.
MK71.2-7.27
Sync to lastest Mokee Source, Kernel updated to 3.4.113, thanks to sunil.
MK71.2-7.28
Sync to latest source, stability is improved.
MK71.2-7.28-19.31
Sync to latest source.
MK71.2-7.29~8.05
Sync to latest source,new LawnChair launcher is added.
MK71.2-8.12
Xposed app added,automatical translation.Update to android-7.1.2_r29-tag
MK71.2-8.13
Only update for ja3gchnduos,jaltelgt,jalteskt.
MK71.2-8.20
Update source,probably fixed jalteskt incoming problem.OTA update supported,Gapps added.
MK71.2-8.26
Device Source updated,PowerHAL added,odexded,improve boot speed,Blur effect added and etc.
MK71.2-8.30
Source Update,bug fix.
MK71.2-9.02
Hardware source update,in next build,Gapps will be removed.
MK71.2-9.09
Source Update and Gapps removed, device ja3gduosctc added.
MK71.2-9.15
Source Update.
MK71.2-9.23
Source Update,kernel change to origin.
Delta update and full download：
Everyone can use delta update now, even installed stock gapps.
Delta Update can save your download time but get full function which contains in full update.
Full update is made for who use Mokee just once or need system files repaired.
Delta(OTA) update will keep 1 generation system up to date, in order to save space.
Version MK 71.2-7.23~7.26
https://drive.google.com/folderview?id=0B5BV4JClBJELa19mNjU4b2ZubUk
You must choose a version which is correct for you.
Version MK 60.1-8.13&MK 71.2-7.27 and above.(You can find all ROM contains MK 60.1 in it)
https://www.androidfilehost.com/?w=files&flid=202052
Recommend Kernel: (Now is build-in in Mokee.)
SmartPack is a good kernel that can give you better battery drain and system fluency.Thanks to sunilpaulmathew for making a awesome kernel.
If you want to see more about kernel,here is the link:https://forum.xda-developers.com/ga...nel-smartpack-project-lineage-os-14-t3590858/
How to build:https://github.com/exynos5410/manifest There are some unique changes for mokee open source,if you want to build one,ask me for help without hesitation,I will try my best to help you.
Issues (copy from Alberto's post)
MK 71.2 issues:
Filesystem Socket Whitelist (https://goo.gl/1N6n7G) - The only issue that requires to be fixed in order to get official.
SELinux (Permissive)
BASED ON USERS FEEDBACK: Mobile Signal Reception isn't 100% stable.
Shared Storage (doesn't encrypt the storage)
ja3gxx: In-Call Echo Effect (random and rare)
ja3gxx: In-Call Volume can't be increased/decreased
ja3gxx: OK Google (Automatic Voice Recognition)
ja3gchnduos: Missing Dual SIM support.
jalteskt: Mobile Data and Incoming Calls don't work.
jalteskt: USSD Codes can't be sent.
jaltelgt: RIL crashes on boot, meaning that Calls/Data won't work.
MK 60.1 issues:
1.Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
2.STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
3.SELinux policies are almost complete, with just some minor missing rules
4.Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
5.Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
6.Device Encryption isn't stable for the same issue that affects Adoptable Storage
Problems report
You need report problems with your
ROM Version
Step to get bugs
If possible,with a logcat is better.
Source Code
https://github.com/Dracanrage
Sorry for my bad English
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.113
ROM Firmware Required: Lollipop Bootloader and Modem, TWRP 3.1.1 as Recovery
Based On: AOSP
Version Information
Status: UNOFFICIAL
Created 2017-07-23
Last Updated 2017-09-23
Screenshots
Is there any differences between Los and it?
Super Sha said:
Is there any differences between Los and it?
Click to expand...
Click to collapse
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Erag0n said:
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Click to expand...
Click to collapse
Nice work!I will try it soon. Will it be official?
Super Sha said:
Nice work!I will try it soon. Will it be official?
Click to expand...
Click to collapse
Sorry, it can't be.
As Alberto says, unless Samsung update the Kernel source to fix the Zygote problem, it can't be official.
i will try, thanks.
Is there any problem with mobile data and call echo?
tosunkaya said:
i will try, thanks.
Is there any problem with mobile data and call echo?
Click to expand...
Click to collapse
As Lineage OS, there should not have any problem with mobile data, but call echo will appear randomly (according to different hardware which Samsung use).
app to sd
how to move app to sd card ?
RahmahTunisa said:
how to move app to sd card ?
Click to expand...
Click to collapse
There is a error in make SD card as internal storage, so it can't move app to SD card in Nougat.
This error is mentioned in Alberto's post, I use his device, vendor, hardware source to make this ROM, so this ROM have the same problem.
What about battery draining?
It's like lineage ?
Mohamed rajab said:
What about battery draining?
It's like lineage ?
Click to expand...
Click to collapse
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Hey, guys.
Delta update is come back now, you will see it in today's update.
Edited
Delta update is available.
Camera2.zip for installed stock gapps guys.
About how to use, please read the main post.
Edited
This file is useless, you need get Camera2.app from 7.23 ROM zip.
Edited 7.25
Mokee updated the check script, it is no need to keep Camera2 installed.
Nice work
Thank you so much
Erag0n said:
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Click to expand...
Click to collapse
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
nebrassfarfoor said:
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
Click to expand...
Click to collapse
Yes, you can use aroma, but had better not install Google camera in order to use delta update.
It support remapping the hardware but not support long press custom.
About bugs, please read the main post
About battery drain, Mokee Open Source make some optimizations, and kernel is not been limited.
About using smartpack Kernel, you can use twrp to flash it, and I am working for merge smartpack kernel to Mokee.
About telegram group, I am so sorry that I can't make one because Chinese telephone number is limited in sent message to strangers.
Hey, guys.
I fixed my S4 today.
Now I can test a amazing Kernel.
Thanks to @sunilpaulmathew for his help and smartpack source.
Hi
Bug = not notification miscall and sms
deletanha said:
Hi
Bug = not notification miscall and sms
Click to expand...
Click to collapse
Oh, it was terrible.
Let me check.
Waiting for a minutes please.
Edited
In my S5 official Mokee, missing was common if I use Aegis.
Did you use it?
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.
This thread was formerly "[ROM][9] LineageOS 16.0 + AOSPExtended + PixelExperience // personal builds" - yes, once again, the title can't fit the full names of all these ROMs :/
This thread hosts personal builds of LOS 16.0 and other Android 9 (Pie) ROMs for Mix 2, currently built from @wight554 's trees. Similar to Oreo, full credits to Wight and others behind the scene for the bringup, allowing us to build upon the awesome work.
Currently I build the following ROMs, usually monthly (in sync with security patch):
LineageOS 16.0
ResurrectionRemix 7
AOSPExtended 6
PixelExperience 9
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
...
What's working:
Everything?
Instructions:
Coming from official MIUI? Since the new encryption has been implemented, you only need to wipe (not format) /data.
Flash any Pie firmware (firmware Stable V10.4.1.0 recommended) for builds starting from May, or firmware Stable V10.0.2.0 otherwise.
Use official TWRP or OrangeFox.
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies to Pie
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "9" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
https://github.com/wight554/
About "official" status:
Currently I don't plan to apply for "official" for any of these ROMs, because 1) Wight is the actual maintainer who did the bringup and maintenance work, and 2) I like to be able to apply changes at will to the OS itself without restrictions from the official team.
Donation:
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 16.0, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, wight554, Cozzmy13
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V10.4.1.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2018-09-25
Last Updated 2019-09-27
Reserved
Just an additional note: I'm not as enthusiastic about building ROMs as I was early this year, so expect less regular updates and/or unanswered fix/feature requests. I'm just a builder, not nearly as capable of Demon or Wight doing all the heavy lifting, so I'll only do what my ability/time permits.
Thanks for all your work, Andy
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Fairtex said:
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Click to expand...
Click to collapse
Statusbar customizations like network traffic aren't merged yet, just wait.
Can we have that slide down gesture to bring the notification bar down like we had in PE Oreo? Thanks
Hey,i have a question. Is it possible to port full screen gestures from miui 10 to los 16?
Are the quick settings on the status bar still a bit off on PE edition?
Folks who have tried, please do let me know about the battery consumption. This build added some CPU governors to the kernel and defaulted little cluster to one of them, and I'm not sure of its actual impact. It's my first time fiddling with kernels and I can't guarantee the change will be satisfactory.
Fairtex said:
Are the quick settings on the status bar still a bit off on PE edition?
Click to expand...
Click to collapse
I acknowledge the lack of padding there, but I don't quite want to look into it now. It's supposed be a problem for PE upstream anyway.
Greetings!
I've downloaded the rom last night. And until now, I have no problem: the camera works perfectly, the sound sound good and gaming performance are good.
The thing which attracted me was the mention of "Lineage OS" and I'm not disappointing to see that it's so close of the official and stable version . I'm blind in context of "find the bugs", so maybe we could find some but this is not my domain.
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Install custom navigation bar .Its work fine
Wysłane z mojego MI MIX 2 przy użyciu Tapatalka
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Expanded Desktop is a feature that will surely be merged in the future. As the other user said, there are 3rd-party apps that can achieve the same goal. I myself am using Tiles since it places a shortcut in Quick Settings.
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
MrSammyMcG said:
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
Click to expand...
Click to collapse
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
AndyYan said:
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
Click to expand...
Click to collapse
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
MrSammyMcG said:
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
Click to expand...
Click to collapse
This is Treble-enabled but this is NOT a GSI (Generic System Image). You still flash as you would do a regular ROM, just with a Treble-enabled recovery.
Quick update to sync with Wight's updated battery data - from this build on you're supposed to use newer firmwares. OP has been updated with the mandatory new firmware requirement and TWRP build from Wight.
Thanks for your work,I have used aex for two days.It is very nice.But I notice a small problem that sometimes the fingerprint unlock is very slow and I have to touch several times to unlock it.Is it a bug of this rom?
Duble tap on screen for wake up dosent works too
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Gemini forever alive!
Download:
TWRP with 4.4 kernel
LineageOS 17.1
Installation:
If you are on stock TWRP you need to flash 4.4 to avoid any problems like /data corruption!
You need to perform a factory reset (format /data)!
Flash rom, gapps/microG and optionally magisk.
Known bugs:
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Join Mi5 group on Telegram
Please consider donating to my hard work
https://paypal.me/xNombre
XDA:DevDB Information
Enchanted LineageOS 17.1 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-01-06
Last Updated 2020-04-02
Reserved
Antutu Score
Reserved
¯\_(ツ)_/¯
Thanks for your hard work
hi
tanx 4 ur hard work
i want know about battery life plz..
install instruction?
and best frimware?
tanx
Can not change battery icon style it is stuck on Icon Portrait.
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
do we need jdc treble for this or what? since it "treble"
What about battery life?
can i flash other android 10 gsi based on this rom since it "treble"
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
nebik said:
Can not change battery icon style it is stuck on Icon Portrait.
Click to expand...
Click to collapse
It's LOS bug.
3V0LU710N said:
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
Click to expand...
Click to collapse
1. AFAIR not yet because it's not merged on LOS.
2. Probably no because there are too many custom changes made (dt & vendor) and I don't like listening to moaning that something is broken. I want to release more interesting ROMs some day (Syb... uhh ekh... eria).
shandianex1 said:
can i flash other android 10 gsi based on this rom since it "treble"
Click to expand...
Click to collapse
Hmmm, that's interesting question. I've only focused on making it fulfill all Android Q requirements concerning vendor separation (and such as APEX), not intended to make it GSI friendly. I guess there are still some incompabilities and you can't expect such and old device to be GSI friendly.
jackryder38 said:
What about battery life?
Click to expand...
Click to collapse
Test yourself, the biggest culprit about I can do nothing more is RIL. Maybe when Xiaomi releases Q for daisy, the blobs will make it better.
RmznDndr said:
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
Click to expand...
Click to collapse
The group is protected with antibot, I've checked your nickname and youre not banned for sure.
Enchanted LineageOS updated!
Changelog:
Merge latest kernel_common and CAF tag into kernel
Merge latest branch into qcacld driver
Use fq_codel queuing discipline, faster net
Update some blobs (those I have access to) from LA.UM.8.6.r1-02900-89xx.0
Remove unused move time data script
Add missing wifi mac generator
Fix USB tethering
Uprev Mapper to 2.1
Tweak Dalvik parameters accroding to new google configs
Go back to stock WiFi config and add some new Xiaomi edits - fixes connectivity problems
Rootdir updates
Minor cleanup
Fixup microG location
Massive overlay update from LA.UM.8.6.r1-02900-89xx.0
Selinux enforcing
Safetynet PASS!!!
Important LOS updates:
Fixed battery style
Updated to android 10.0 r23
Added survival script (magisk reflashes itself)
Repo sync all
Download via sf:
https://sourceforge.net/projects/xn...-17.1-20200119-UNOFFICIAL-gemini.zip/download
Please consider donating...
https://paypal.me/xNombre
xNombre said:
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Known bugs:
Speaker playing only left channel
5GHz hotspot
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Click to expand...
Click to collapse
Fixed?
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
nebik said:
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
Click to expand...
Click to collapse
Use this Gcam
https://easyupload.io/5ms9tu
It's version 7.2 - optimized and working 100% on gemini
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
xNombre said:
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
Click to expand...
Click to collapse
I have problem with permission name (icon != Permission name)
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
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
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
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
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.