Related
Hi guys,
I want to make my own heavily optimized MIUI ROM, that will be sufficient to my requirements. My goal is to optimize ROM to highest speed and lowest RAM-consumption possible, that can be achieved on my Desire HD.
But I cant find any relevant and newest info, how current MIUI ROM works, and how they are build.
My plan is to somehow optimize released ROM for speed, and low memory requirements (ROM is from MIUIandroid.com) and add there some things, like language pack, and gapps.
Is there some guide about MIUI ROM, that has complete description of directories and files in MIUI ROM ZIP file? I have found nothing on google, MIUI forum or XDA. Just some scattered info, that was months or years old and thus outdated.
I was looking for some complete guide, or things like:
- how and where I must placed gapps files in ROM, so they be available right after flashing ROM, and the user not have to flash it separately?
- what files is required to core functions of MIUI ROM
- what apps in system/app can be deleted without compromise other functions of ROM, and is there some description of each apk file in system/app directory?
- is there a way to specificate what apps will be alwais running in the background, and OS will not close them? (I dont want to wait 10s to start facebook or browser, because System close them after some time of not being used)
...and many more questions like this, about various functions of MIUI ROM.
Where I can find this info, and from where have people knowledge about building custom MIUI ROM, or tweaking/optimizing it? There must be somewhere a complete information about how it works, because obtaining information from google, etc. is highly ineffective....
Code:
/*
* Your probably long dead warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
This thread is organized into different posts so that people dont quote the whole OP.
Please read all the posts and updates, before flashing.
Changelog Summary:
For full changelog follow the link.
#FINAL: 28 Jan 2018
Repo synced with latest LineageOS 14.1 sources.
Updated system webview to 64.
Added postinstallzip due to kernel not being flashed.
Added Magsik 15.3 support in ramdisk.
#4: 14 Nov 2017
New feature: UA:CMA
Added back Device Settings.
#3: 14 Nov 2017
Switched to a more stable kernel with improvments
Fixed Camera
Fixed Bootanimation
#2: 12 Nov 2017
Enabled OpenGLES 2.0
Fixed Audio/Video Playback.
Fixed Webview.
#1: 11 Nov 2017
Initial build.
Latest Download:
You need to flash lineage-14-postinstall.zip after installing the ROM, or else it wont boot.
For some reason ramdisks arent being flashed.. and I cant be bothered to figure out why..
lineage-14.1-20180127-UNOFFICIAL-galaxysmtd.zip
lineage-14-postinstall.zip
Older builds
#4 lineage-14.1-20171117_140654-UNOFFICIAL-galaxysmtd.zip
#3: lineage-14.1-20171114_062105-UNOFFICIAL-galaxysmtd.zip
#2: lineage-14.1-20171112_085706-UNOFFICIAL-galaxysmtd.zip
#1: lineage-14.1-20171111_094959-UNOFFICIAL-galaxysmtd.zip
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-11-11
Last Updated 2017-11-14
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2017-11-11
Last Updated 2018-01-28
Working List:
Boots
RIL (SMS, Call)
WiFi
Audio/Video Playback (fixed in build#2)
Camera Pictures (fixed in build#3)
Not Working List:
RIL Data
FAQ:
Dont install too many apps obviously
The first boot should be faster than previous nougat roms.. Since I have now used pre-odexed /system.
Known Issues:
Lagginess ofc, due to our device being old
Sometimes SystemUI gets killed due to low memory and we get Black Screen of Death
Install Instructions :
[WARNING]:
You must be already on at least Lollipop/Marshmallow ROM and have latest TWRP 3.1.1.
You must format /data as f2fs in TWRP.
Bootanimation is working since build #3.
You should already been familiar with flashing custom ROMs before.
And know how togo from gingerbread -> nougat.
Please check other threads for that..
If someone wants to contribute install instructions for this ROM.
I will be happy to add here and give credits.
Gapps
I havent tested GAPPS.. but I can guess the performance will be horrible with it.
However, I have included the patch for microG GmsCore signature spoofing. So you could try that.
Additional Info:
Built from latest LineageOS 14.1 Sources.
Latest kernel from @xc-racer99 aosp-7.1 branch
Live wallpapers, LineageOS Updater, Weather Service removed for low memory footprint.
Reserved.811919
Reserved.224232
Credits:
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1.1
And all others who had worked from beginning till now on this device.
Sources
Galaxy S1 Resurrected: Project Nougat
Device Trees:
https://github.com/galaxys1-resurrected/
https://github.com/galaxys1-nougat
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
I'm delighted that there's still someone who is working on this device. I'll be appreciated to wait for a more stable version of nougat.
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
MYEUHD said:
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
Click to expand...
Click to collapse
Expect lot of stuffs dont work at the moment.. listed in Not working.
About webview I will try to replace it.
Magisk and SuperSu try to patch boot.img and ramdisk.. and our device uses a very hacky way to load ramdisks.
I will create a patched ramdisk with latest Magisk then..
This has to be the fastest Nougat ROM I've flashed on this phone! Thanks for keeping this amazing phone alive. Can't wait to see it become more stable in the future
Full changelog: build #2
Fixed Audio/Video playback
I had to remove ffmpeg codecs as they were causing hardware decoding to not work.
Hardware decoding is working fine and 720p playback is smooth too..
I've tested without bigmem mode.. I havent implemented bigmem libs for 720p playback.
So please try without bigmem before reporting issues with it.
Fixed Webview
AOSP Webview was somehow not working on our device.. as pointed out by @MYEUHD
The solution he linked was to revert to older webview.
But that is outdated and unsafe so I tried with latest Android System Webview.
It seemed to work so I set it to default.
I havent tried but we can also use Chrome as our Webview..
Switched to OpenGL 2.0
We were stilling using OpenGL 1.4 for rendering.. this shouldnt affect much.. but animations should be smoother
Since we no longer get Shader errors with OpenGL 2.0
Let me know if you find any difference performance wise compared to build #1.
Downloads are in OP.
Status Update:
Project discontinued.
Status Update:
You can skip this paragraph if are not intrested in my long story cut short.
So I have been trying to fix stuffs which means.. rebuilding and flashing the ROM.
Wiping data .. getting logs.. testing if something works.. Repeat
I hadnt really used my Galaxy S1 phone.. It was just lying around a corner of my table getting dust.
Until one day I thought, let's build Oreo for this old time phone.. turns out the battery was RIP due
to not charging it for so long.. so I got a replacment battery then booted to see cm-14.1 build by
Coldwindofnowhere and missing IMEI which I sucessfully restored after creating a thread here.
Again thanks for that to @xc-racer99 and @MYEUHD
So I started out device trees and repos based on Coldwindofnowhere and xc-racer99
and made it compatabile with Oreo. And thanks to rInanD0 I was able to pick stuffs necessary on
kernel side.
Then me and @xc-racer99 discussed some stuff and I picked changes from Unlegacy-Android gerrit to properly do some stuff.. I fixed lots of stuffs.. but I couldnt get the display to initialize... so I decided
to wait for Unlegacy-Android for their take on Galaxy Nexus which shares same GPU as us to bring up Oreo first.
In the mean time, I thought again.. why not build Nougat for now.. so I again setup device tree and repos for
nougat. and we are here..
Okay so I havent really used my Galaxy S1 let alone this ROM.
This ROM does seem fast while moving around just after a first boot.
And really I hadnt installed or used any apps besides the one that came with LineageOS.
But today while trying to fix Camera, I had to actually take photos. Oh, and the reason camera was not working
was due to I had disabled building of Camera HAL in Oreo which stuck around... big derp
So camera preview was working now.. Snap camera wasnt savinf photos at first..
so I thought to install Open Camera.. I installed F-Droid.. then Open Camera..
Then I clicked some photos which seemed to be saved.
There were a lot of photos created so I decided to delete them.
But Files app wasnt deleting them.. must be a permission issue?
So i installed a file manager from F-Droid and deleted the photos.
Good enough.. then I thought I need to download these apps again after a data wipe..
Lets backup them.. so I installed an apk backup again from F-Droid.
While it was downloading.. BAM Screen went all BLACK.
I tried clicking home button but nothing.. then I clicked power button nothing.
Then I hold power button.. i got the options...
Now I was reminded of this bug which has been around since Lollipop? or Marshmallow days..
Screen going all black.. back then Coldwindofnowhere predicted it might due to out of memory issues..
And he is right.. I had adb running so I checked free memory and swap.. The swap file was and memory was nearly full.
I checked dmesg for logs... then I saw lowmemorykiller killing all kinds of stuff.. but there was only one time it killed this..
Code:
lowmemorykiller: Killing 'system:ui' (5642), adj 902,
And thats the reason for the black screen.. Now we all know this device doesnt have much memory.
So the option would be to not install many or any apps.. on this option..
Ofcourse I could try to get CMA working properly.. which adds just around 70-80mb I guess..
And we could just white list system ui to not get killed.. but then it would kill other important processes..
So I've decided to stop working on Nougat. I dont wanna give people false hope of *stable* nougat.
I will still upload a build with Camera fixed.. Well video recording still doesnt work.. Looking at logs.. i need to resurrect
the old way of video buffer. which got removed in Nougat.
And while Project Nougat is offically discontinued, Project Oreo is still alive just paused.
I will at least get Oreo bootanimation on this device.
Thanks for trying out this short lived nougat ROM.
Full changelog: build #3
Switched kernel from @Coldwindofnowhere to @xc-racer99
I think xc-racer99 kernel has better memory management. since the lowmemory killer doesnt kill many processes..
However I did make some changes to it.
Disabled CMA
Enabled and set zRAM to 1/4 of total memory
Some kernel build optimizations.
Note that.. this kernel doesnt have BigMem Support so wer'e stuck with 383MiB ram for now.
Fixed Bootanimation
Yeah.. that was a my mistake.. err..
At least you know its booting now.. but since we use pre-odexed ROM first boot shall be done in 5 minutes now..
Fixed Camera
Taking pictures should work now. Video recording is broken.. It needs to updated for Nougat..
Added Magisk in ramdisk
Latest version 14.0. Just install magisk manager AND DONT TRY TO PATCH BOOT.IMG..
We use very differnet system for boot.img and ramdisks..
I will try to update Magisk to latest version.
Fixed a big mistake in updater
https://github.com/galaxys1-nougat/...mmit/a6f51178503a01f6b1e7b0c8222e875392af8a8e
Flashing boot.img would actually result in wiping it in some cases..
If you had troubles installing this ROM or any ROMs in the past.. this might be the case..
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
laharl_22 said:
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
Click to expand...
Click to collapse
Error 7 is assert error... which I guess is coming from updater script..
You dont need to restore whole stock ROM..
I have built a twrp only recovery image... so you can just straight boot to recovery after Odin..
You can also flash recovery.img from heimdall .
https://drive.google.com/drive/folders/1KthyR6QWPswaIT8fw2nbiR4fathP-QU0?usp=sharing
How is this Rom compared to the LineageOS 4.4.4?
The Inventor of the Android Patch System presentsWELCOME TO FLUENCE UHD SOSPHINTSee Post: https://forum.xda-developers.com/showpost.php?p=78928919&postcount=25 For the latest Update and News
INDEXPOST 1 - INFOS
POST 2 - DOWNLOAD
POST 3 - INSTRUCTIONS
ABOUTMy Projects are always aiming on delivering a clean and fluent Operating System, with the maximum level of quality in all views. Fluence UHD is back, and now bigger and better as before! Expierence the optimizations and secrets i discovered and collected over all the Years with My Work.
Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
XDA:DevDB Information
🤖 FLUENCE UHD PATCH 🤖, ROM for the Google Pixel 2 XL
Contributors
Miustone, Miustone, Miustone, Miustone
Source Code: https://github.com/Miustone/SOSP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Google Factory Image: https://developers.google.com/android/images /AND Deuces Script 4.5: https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2019-02-19
Created 2019-02-13
Last Updated 2019-02-21
DOWNLOAD
Instructions:
FOLLOW THIS THREAD TO GET THE LATEST STOCK OS:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Fully boot Your Pixel into the Stock OS
Skip the Google Setup Wizard
Place the Patch on Your Device Storage
Reboot in to TWRP
Wipe Data and Dalvik Cache
Flash the Patch
Reboot in to System
Done
SOSP RELEASES
Visit my Repository from the Thread
Download the Master Branch as zip
Repack the Patch zip
Make sure META-INF and everything else is on root of the zip
Use it with the Instructions from above
Done
Upload for todays build takes still one hour for now. You can select with Drive also older Versions of the ZIP (Acutal is V2, Uploading is V3) btw. Enjoy!
EDIT:
New Device new trouble. Got bootloops with the uploaded Version so do i have to revert some Things. Stay tuned!
I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!
encephalon9986 said:
I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!
Click to expand...
Click to collapse
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...
Miustone said:
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...
Click to expand...
Click to collapse
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.
encephalon9986 said:
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.
Click to expand...
Click to collapse
Sweet, have a good One :angel: Wish i had the Time with Mine. We have both to work early tomorrow
Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.
mookiexl said:
Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.
Click to expand...
Click to collapse
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..
Miustone said:
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..
Click to expand...
Click to collapse
Cool bro. I'll elect to to wait while you get adjusted to this device. I know your work is superb based off what you've done on devices past.
Will this work on walleye (Pixel 2)?
bassguy60 said:
Will this work on walleye (Pixel 2)?
Click to expand...
Click to collapse
Yes
Can aynone tell Me btw why there is no MTP in TWRP? Reovering the Device after testing a Patch means always a full flash with Factory Image for Me. Followed by a boot in the System where i have to use PTP to copy my ZIP. Cruel to develop like that TWRP is the other painful Point. Wish the Pixel would have a classical Recovery Partition...
EDIT: Seems like we have to boot once after flashing Stock to be able to flash Magisk and get a booting System!? That could be the Reason why my full stock rom wasn't booting. Feeling me a bit dumb right now...
EDIT2: I will push more Time in a full Stock ROM to get a Monthly updated Base for my Changes. Once i got a fully working ROM can i start with adding AROMA Options and Stuff like that. I think the only Problem with My ROM was the patched Kernel which don't wanted to boot and not the deodexing or the Updater Script... Any help with it is welcome
Miustone said:
Expierence the optimizations and secrets i discovered and collected over all the Years with My Work. Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
Click to expand...
Click to collapse
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.
bobbarker2 said:
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.
Click to expand...
Click to collapse
Hey,
Secrets is maybe not the right Word. It's more like many Developers and even OEMs don't know about all the Stuff of Android. I discovered Bug fixes, functions and Features which are now used in a wide range of Mods and ROMs and even OEM Firmwares, and while never getting Credits for it am i aware about where it popped up first in the Web ? I was the First One for example who got all real Pixel Features on a non Pixel Device by porting a lof of System Stuff and Not only by changing one or two Files. I also ported MIUI in the past which was mind opening for Me Back in that Time...
The Secrets i use here are just a greatly tested bunch of Configs for the Hard and Software of our Android Devices in other Words.
And yeha, sorry for My English! It's not the best ?
What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error
gogixx said:
What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error
Click to expand...
Click to collapse
I discovered this issue only with attached USB Cable, have you tried it without? As usual can you just press the bottom right edge a few times and you will complete the installer without Problems when this happens.
I'm still working on a full stock zip... Possible that i end up with raw images :/
Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press. ?
gogixx said:
Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press.
Click to expand...
Click to collapse
It's the spot where You clicked to go to the next Page in AROMA. Press it 4 or 5 Times and it will exit AROMA to TWRP. It's a ugly AROMA bug which never got fixed in the last 4 Years...
Alright, just to let You know Guys. Making Stock ROMs from actual Google Images is cruel. There is almost no benefit against flashing with a PC except for the need to have a PC. The Patch will be the only Thing that works just fine if we want Stock Edits...
I'm actually ripping everthing out of the Patch and i'm redoing the Scripts and hope it will work. Cross the Fingers!
Can anyone tell me btw how to create a working backup of stock with TWRP? Looks like my backups won't start..
I was able to compile Lineage OS 15.1 for my Asus Nexus Player but only after two workarounds (one missing file/buggered prebuilt bison). The build made my own update which I sideloaded according to the Lineage OS instructions. I ran through setup, and once reaching the main UI, I've no Settings icon anywhere to be found.
I was able to use a official nightly build to update everything. I then applied my own resulting kernel. My personal objective to make and boot my own kernel is complete, but I'd hoped to have my own entire build with the basics working so I could then tackle how to include additional packages, kernel modules I had it make during build, and firmware for my tuner.
Excluding the kernel, I'd like my image to give me the same experience as a nightly build, but I don't know what went wrong. I''m asking for advice on this.
Thanks.
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021
Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5
Has anyone tried it yet?
DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.
Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.
How does Resurrection Remix compare to CrDroid?
asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.
hockeymikey said:
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.
Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere