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..
Related
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?
PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.
Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?
You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too
Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....
rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
OK i'm trying a reflash now. Complete wipe.
For me all work correctly, no problem with google play store or wifi
WELCOME
Miustone is Presenting
The XperiStock ROM. Based on the latest Xperia Firmwares. Optimized with Love.
The XperiStock ROM Contains 8 Years of research and testing on Android. Aiming on a open and Pixel like Expierence, is the XperiStock ROM coming with the barely minimum of Apps. Including Google App replacements without loosing the best Features of the Xperia Firmwares. Optimized on many Edges under the Hood, but still delivering the default Stock Feel and Look of the Original Firmwares. If You want to know what's included, check out the Features List..
FEATURES
Rooted by Magisk
Busybox included
DRM Fix included
Fully De-Odexed
Heavily Debloated
Google App Replacements
DM-Verity disabled
Forced Encryption disabled
SafetyNet Passing
All default Stock Features
Optimized booting Times
Optimized Performance
Optimized UI Handling
Optimized Audio Handling
Pixel Exclusive Features
Credits to:
-sToRm// (DRM FIX)
-shoey63 (DRM FIX)
-SuperR. (KITCHEN)
XDA:DevDB Information
XperiStock ROM, ROM for the Sony Xperia XZ Premium
Contributors
Miustone, Miustone, Miustone, Shoey63
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: .145 Custom DE (G8414)
Version Information
Status: Testing
Current Stable Version: V1848
Stable Release Date: 2018-04-08
Created 2018-04-07
Last Updated 2018-04-08
Infos:
Instructions
-(Coming from AOSP or older Firmwares)
-Flash the latest Official Firmware for Your Device
-Boot into the System (Setup Wizard)
-Flash TWRP with Fastboot
-(Coming from latest Stock Firmwares)
-Full Wipe (Data, System and Caches)
-Flash XperiStock ROM
-(G8142 Users have to replace the Kernel)
Changelog
V1
-Based on 47.1.A.12.145
-Deodexed
-DM-Verity Disabled
-Forced Encryption Disabled
-Zipaligned
-Signed
V1848
-Changed Installer UI Print
-Changed Version Naming (Dates)
-Changed default DPI to 400 (From 480)
-Optimized ROM Installer Script
-Optimized ROM Installer Directions
-Added first Optimizations from the Snappatch
-Removed Third Party Bloat Apps
-Removed many SONY Apps
-Removed Stock Google Apps
-Added Optimized Super GApps Pack
-Added Android for Work Support
-Added First Optimizations (W.i.P.)
-Added Magisk Root
-Added Rootless Pixel Launcher
-Added "DRM Fix"
-Added Shoey63's Kernel (Thank him)
-Reduced ROM Size by ~500Mb
-Removed Bootanimation
-Disabled Bootanimation Preloading
-Disabled Bootanimation
-Added Busybox
-Added Pixel Features (First Set)
-Added Freeform Windows (Recents)
V18410 (Soon)
-Merged more Snappatch Content
-Added more Pixel Features
-Added new Xperia Assistentin
-Added new Xperia Camera App
-Added better Microphone Handling
-Added Security Handling Optimizations
-Added Audio Handling Optimizations (Output)
-Added Rendering Handling Optimizations
-Added better Camera Image Quality Profiles
-Added better Camera Audio Quality Profiles
More coming soon...
Download:
GOOGLE DRIVE
Missing Apps?
Check the Play Store for Your Favorite Apps or visit apkmirror.com
Hello Folks! Looking forward to support My new XZ Premium with great Work! Stock has changed over the Years and there is a lot to learn again. So please let Me know if You have something to contribute like a Camera /DRM FIx or something like Support for more Variants of one Phone Model...
Hope You will enjoy what i deliver! Happy flashing :highfive:
wow great job! cant wait to try it out
madshark2009 said:
wow great job! cant wait to try it out
Click to expand...
Click to collapse
Added a Changelog If You prefer to have something special should You just wait for V2. V1 is very basically to proof that i'm able to produce working Bases for My Work. Looks like i stop doing My Snappatch and switch back to Stock ROM Creations again. To bad that AROMA isn't working on the XZ Premium, otherwise would i include Tons of Options...
Maybe can we get that also fixed in the Future. First Things first
Miustone said:
Added a Changelog If You prefer to have something special should You just wait for V2. V1 is very basically to proof that i'm able to produce working Bases for My Work. Looks like i stop doing My Snappatch and switch back to Stock ROM Creations again. To bad that AROMA isn't working on the XZ Premium, otherwise would i include Tons of Options...
Maybe can we get that also fixed in the Future. First Things first
Click to expand...
Click to collapse
I like how you work! Very orginized and promising
So camera is not working at all? Not even on alternative apps?
madshark2009 said:
I like how you work! Very orginized and promising
So camera is not working at all? Not even on alternative apps?
Click to expand...
Click to collapse
Glad to hear that You appreciate that! Hope i can provide a clean and good Working ROM over the next Years, with Useful additions and Optimizations. Something You will never see from Me are old, obsolete or non working "Tweaks", copied Audio Mods or included Xposed. That's stuff Users can add if they Think they miss it...
Quality over Quantity!
And to answer Your Question: No, it's not working at all. You can open it and all that but taking Pictures outputs Green Results (Think the Noise Reductions has a mailfunction without DRM)
XperiFix would be the Way to get around this, but it doesn't allow or support newer Firmwares (As long as the Master isn't giving it Free). I will try to find a Fix for this without the need for a PC, but for now do we have to wait or to use the following Way)
You can:
-Flash XperiFix supported Firmware to Your Device
-Boot into the System (Skip the Setup)
-Shutdown
-Flash the XperiStock ROM (Don't boot the System)
-Use XperiFix
And that should be it. Can't say if this really works but i heard it does...
I go to home sooner and test your rom it's stock yeah just flash able I'm fix camera by flashing that old kernel and drm fix so easy but I think the stock kernel is super fast and this is just fast(old kernel).
Blackghosthm said:
I go to home sooner and test your rom it's stock yeah just flash able I'm fix camera by flashing that old kernel and drm fix so easy but I think the stock kernel is super fast and this is just fast(old kernel).
Click to expand...
Click to collapse
Wow, thank You for letting Us know! We know it's a old Kernel, but better as a non working Camera for now! BTW. Is the Kernel for the Dual SIM Version only or also for the G8414 Version!?
EDIT1: Next ROM comes soon! Changelog grows :angel:
EDIT2: Testing some last Changes. Think i'll upload the next ROM Version very soon...
Maybe you could have a look at getting this working on oreo for v2. Used to work fine on nougat. The font tab is added to settings, but hangs then reboots when you press it.
https://forum.xda-developers.com/crossdevice-dev/sony/root-font-selector-igor-eisberg-t3367521/page1
Miustone said:
Wow, thank You for letting Us know! We know it's a old Kernel, but better as a non working Camera for now! BTW. Is the Kernel for the Dual SIM Version only or also for the G8414 Version!?
EDIT1: Next ROM comes soon! Changelog grows :angel:
EDIT2: Testing some last Changes. Think i'll upload the next ROM Version very soon...
Click to expand...
Click to collapse
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working? AndroPlus Kernel V11 Cause WiFi and data settings to be invalid,as my test on g8142.
oneheart said:
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working?
Click to expand...
Click to collapse
Xposed isnt working, since the last two Sony updates.
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
@Miustone
Here is a patched services.jar from .145 firmware, using the method from here.
https://forum.xda-developers.com/showpost.php?p=68001053&postcount=2
Beetle84 said:
Maybe you could have a look at getting this working on oreo for v2. Used to work fine on nougat. The font tab is added to settings, but hangs then reboots when you press it.
https://forum.xda-developers.com/crossdevice-dev/sony/root-font-selector-igor-eisberg-t3367521/page1
Click to expand...
Click to collapse
Interesting, i will take a look! Thanks for sharing!
oneheart said:
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working? AndroPlus Kernel V11 Cause WiFi and data settings to be invalid,as my test on g8142.
Click to expand...
Click to collapse
I'm not sure if i go with AndroPlus Kernel on the Release since someone told Me he is working on a new Kernel including the DRM Fix. At least is My Camera working with this Kernel (G8414) besided no other Bugs (Except for Lags after flashing but that is gone now). Hope i can deliver a ROM that works also for Your Device well...
Beetle84 said:
Xposed isnt working, since the last two Sony updates.
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
@Miustone
Here is a patched services.jar from .145 firmware, using the method from here.
https://forum.xda-developers.com/showpost.php?p=68001053&postcount=2
Click to expand...
Click to collapse
Thanks for Your efforts! I'm not going to include Xposed by default since not everyone is using it (Including Me), but i could include Your Edited Services.jar for Xposed Users if it helps!?
EDIT: Is the Services Jar comming with disabled Signature Verification? If so, should it be easy to include the Font Selector from the Link up here...
I'm currently almost done with the new Version. Just waiting for the Kernel and i'm about to Optimize the Camera Config (Trying to enable 4K Recording on the Front Cam besides 1080p @60fps and such). Maybe do i find some more Things to play with...
I'm also thinking the Audio Quality could be better at all. I will also work on this without using any Pseudo Audio Mods or such...
Can't wait to upload the next ROM. I was also thinking about another Name (XperiStock was a just quick Idea for the Release). How Sounds PiXeria? Think it would fit well to the Pixel Look the next ROM comes with... Let Me know!
BR
Miustone said:
Interesting, i will take a look! Thanks for sharing!
I'm not sure if i go with AndroPlus Kernel on the Release since someone told Me he is working on a new Kernel including the DRM Fix. At least is My Camera working with this Kernel (G8414) besided no other Bugs (Except for Lags after flashing but that is gone now). Hope i can deliver a ROM that works also for Your Device well...
Thanks for Your efforts! I'm not going to include Xposed by default since not everyone is using it (Including Me), but i could include Your Edited Services.jar for Xposed Users if it helps!?
I'm currently almost done with the new Version. Just waiting for the Kernel and i'm about to Optimize the Camera Config (Trying to enable 4K Recording on the Front Cam besides 1080p @60fps and such). Maybe do i find some more Things to play with...
I'm also thinking the Audio Quality could be better at all. I will also work on this without using any Pseudo Audio Mods or such...
Can't wait to upload the next ROM. I was also thinking about another Name (XperiStock was a just quick Idea for the Release). How Sounds PiXeria? Think it would fit well to the Pixel Look the next ROM comes with... Let Me know!
BR
Click to expand...
Click to collapse
hey can you also see if you can enable native 4k screen? or 120hz? or recording [email protected]?
PiXeria sounds nice , you can try XpiXel, or any unrelated name that sounds strong, like venum or cobra or viper like some other rom names
but PiXeria sounds nice too.
@Miustone
I notice you are directing users to use one of my old kernel repacks with this rom, and that's fine but it's time for an an update!
Here is my repack of the latest .145 stock kernel for G8141 single sim https://www.androidfilehost.com/?fid=890129502657596596
I assume you have baked the drm fix libs into the rom, but if not , here is sToRm//'s drm fix zip https://www.androidfilehost.com/?fid=673956719939833470 (zips tested by me and verified as working on pure stock 47.1.A.12.145 rom)
- Camera with no green pictures working straight out of the box.
- Safetynet passes without flashing Magisk.
- DMverity disabled.
- Patched to eliminate lag on deodexed roms. (Works fine on odexed as well)
- Flash kernel.zip and drmfix.zip in TWRP recovery and you are done.
madshark2009 said:
hey can you also see if you can enable native 4k screen? or 120hz? or recording [email protected]?
PiXeria sounds nice , you can try XpiXel, or any unrelated name that sounds strong, like venum or cobra or viper like some other rom names
but PiXeria sounds nice too.
Click to expand...
Click to collapse
Great Ideas! XperiStock sounds so copied for Me
I will think about it till the Third Release. Well, native 4K shouldn't be the Problem, but 120Hz for sure. Maybe can we do more on Stock when the 120Hz Option on AOSP finally works (To see how it works). 4K on 60FPS with Back Cam on Stock is in the testing Phase right now...
Let's see what i can manage to do in the next Time, but i'm already really satisfied with the Quality of Stock. It's for sure beyond the most Flagship when it comes to Quality and Features...
Only the Audio could be really better like said before. Think i can make this baby a lot better in this view. There is a lot to merge from My Snappatch, and i'm finally not longer handicapped by the DAC in My Axon 7 (Snapdragon ftw!)
Hi Miu stone I'm glad to see you working on camera and audio (specially camera because no one does) just don't delete xreality, I think native 4k can be good, but native 2k can be great because dialer doesn't work on 4k, phone goes hot on 4k,battery drain faster, and phone getting slow on games.
Hope you adding cool features to it and thanks for great work.
How's xperibeast for name. ?
Blackghosthm said:
Hi Miu stone I'm glad to see you working on camera and audio (specially camera because no one does) just don't delete xreality, I think native 4k can be good, but native 2k can be great because dialer doesn't work on 4k, phone goes hot on 4k,battery drain faster, and phone getting slow on games.
Hope you adding cool features to it and thanks for great work.
How's xperibeast for name.
Click to expand...
Click to collapse
well at least there should be the option of switching you know? when you gaming you can simply switch to 1080 or 2k and when you just browsing, instagram, youtube , chrome, etc its nice to have 4k as an option to enable, plus there is an alternative phone app that works with 4k (the reason it doesnt work in the first place is because some apps arent adjusting to the VIRTUAL density but if it was physical it wouldnt cause such problems) I tried it and it works perfectly, and dont worry, i dont think native 4k is as much power requiring as virtual so overheating isnt gonna be a big issue like on virtual 4k using adb commands.
Miustone said:
Great Ideas! XperiStock sounds so copied for Me
I will think about it till the Third Release. Well, native 4K shouldn't be the Problem, but 120Hz for sure. Maybe can we do more on Stock when the 120Hz Option on AOSP finally works (To see how it works). 4K on 60FPS with Back Cam on Stock is in the testing Phase right now...
Let's see what i can manage to do in the next Time, but i'm already really satisfied with the Quality of Stock. It's for sure beyond the most Flagship when it comes to Quality and Features...
Only the Audio could be really better like said before. Think i can make this baby a lot better in this view. There is a lot to merge from My Snappatch, and i'm finally not longer handicapped by the DAC in My Axon 7 (Snapdragon ftw!)
Click to expand...
Click to collapse
hope the [email protected] work, and if 120hz is a problem how about 4k option? is it possible you might consider it in the next version?
and yah actually the sound quality on the device is superb and on a high level compared to other devices when it comes to everything about sound engineering, I actually work in the music field and I work a lot with sound stuff and i can tell you it delivers pretty good accuracy and has a high dynamic range of frequencies and its very rich, the only issue here is that its very low, could be to maintain really good quality sound, but I would rather a higher volume even if it means a little less quality (unless if it starts to distort in that case id rather keep it low)
and again, on be half of the XZP community I cant thank you enough for you efforts and energy to get this baby up and running on the level it should be
keep it bro much love
shoey63 said:
@Miustone
I notice you are directing users to use one of my old kernel repacks with this rom, and that's fine but it's time for an an update!
Here is my repack of the latest .145 stock kernel for G8141 single sim https://www.androidfilehost.com/?fid=890129502657596596
I assume you have baked the drm fix libs into the rom, but if not , here is sToRm//'s drm fix zip https://www.androidfilehost.com/?fid=673956719939833470 (zips tested by me and verified as working on pure stock 47.1.A.12.145 rom)
- Camera with no green pictures working straight out of the box.
- Safetynet passes without flashing Magisk.
- DMverity disabled.
- Patched to eliminate lag on deodexed roms. (Works fine on odexed as well)
- Flash kernel.zip and drmfix.zip in TWRP recovery and you are done.
Click to expand...
Click to collapse
True Hero! Thank You very much for Your Contribution! I just got the DRM working with My ROM and the right Kernel, but it's really Time for a Update. Next Version of My ROM will come with Your Kernel! Also great to hear that there will be no Lags and to have also other Additions like DMverity disabled besided passing SafetyNet!
I could with AROMA create a lil Pack containing the DRM Fix, Magisk (Or no Magisk) and Your Kernel, but sadly is our TWRP buggy and doesn't works with AROMA right now. But when People want to flash My ROM with a working Camera and without Magisk do they just have to remove the Magisk ZIP out of the ROM and all will be fine. Really great!
Buy this Man a Beer! Next ROM Update will come in the next Hours with new Kernel <3
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest [clean] ROM for our device, benchmarks coming soon .
Click to expand...
Click to collapse
Features
Google's exclusive features for Pixel devices (except Music Ticker and Call Screening)
Lawnchair launcher
Spoofed stock device to pass SN
Widevine L3
Faster encryption device-wide
Daydream VR
Fast, optimised Zest Kernel
EAS
Markup screenshot editing
Google Sound Picker
Google Wallpapers
Digital Wellbeing
Optimised GPU rendering for Pie
Custom Clang and GCC toolchains for building - optimised LLVM with PGO, and GCC 9.1
OpenGApps pico included
GCam HDR+ support
Click to expand...
Click to collapse
Installation instructions
* Go download https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-yoshino.
* Unzip the download to get an .img file.
* Install fastboot (drivers for this can be gotten from Google directly), drivers for flashmode for Windows can be gotten from newflasher.
* Enter your command prompt or terminal whatever and fastboot flash oem THEFILEYOUEXTRACTED.img.
* Find a decent TWRP and flash it.
* Download the ROM for your device. They are all in this folder https://jenkins.cosmic-os.org/job/zfsodp-core/ws/lastbuild so click the one for your codename (eg. G8141 is single sim maple and G8142 is dual sim maple).
* Flash it in TWRP and wipe internal storage and format data (the option that has red text and makes you type yes).
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my Jenkins job.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Sony group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @kholk for his kernel advise
* @Sultanxda for his kernel advise
* @deletescape for Lawnchair
XDA:DevDB Information
Zest-flavoured SODP, ROM for the Sony Xperia XZ Premium
Contributors
LazerL0rd, The entire SODP team
Source Code: https://github.com/ZfSODP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Sony OSS OEM binaries
Based On: SODP
Version Information
Status: Beta
Beta Release Date: 2019-07-06
Created 2019-07-06
Last Updated 2019-08-10
Reserved
Reserved
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
del
Can I flash the kernel through twrp, then flash the zip?
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Give it a week or so mate, lazerl0rd is studying/having exams for a while.
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Any screenshot of the performance?
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
still on logo android !/
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Moarten said:
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too.
Laplacetor said:
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
Click to expand...
Click to collapse
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too. ROM isn't on my website and never was .
wolfmanstr said:
Can I flash the kernel through twrp, then flash the zip?
Click to expand...
Click to collapse
Don't use my stock kernel with this.
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
It performs better, battery is decent now (after a load of changes). We now (as of today) have a Power HAL (libperfmgr) which supports DT2W on supported devices too. I may or may not update it to version 1.3.
SilverGamer_YT said:
Any screenshot of the performance?
Click to expand...
Click to collapse
No, it's EAS and you could test it out.
tronganhha29 said:
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
CRNO said:
still on logo android !/
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now.
Sjll said:
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now. EAS seems stable, here. The bugs we have aren't really EAS related.
undefine said:
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least. I changed up the thermal driver so it should be good now. Btw those thermal modules in Magisk won't change a thing as I use sultan's thermal framework now - not RQBalance stuff. DPI has an option on setup under "vision", choose what you like. I added GCam instead, it's gonna be better quality than Sony's crappy cam app. Ancient app logos aren't gonna be updated, these are ASOP packages - instead I'm replacing them with Google packages. Also I made everything Squircle shaped too. Device-wide dark mode will be coming soon, needs some kanging [with original authorship] from Q. Phone application should be de-google-ified -> you can turn off the spam filter and install any Dialer you want. I'm not dealing with darkening AOSP's package so that's why I'm using Googles. Google can get your data if Play Services is installed anyways. Option to switch resolution and frame rate on the go -> idk why SODP removed that.
Astoras said:
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
Click to expand...
Click to collapse
For Android kernels, you can't just chuck a module in. But I'll add it to the kernel config for ya.
CRNO said:
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Click to expand...
Click to collapse
Already done. And - "I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least."
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
Morning all!!
I have spent the last few days bringing over my Rom Project from N20U (which started on N10 and then spread to Tab s6) and have a Beta ready for release to a few testers that, like me - can go a while without a camera for the sake of root lol (i appreciate this is an extremely niche group right now - hopefully we see a fix ASAP)
Its a relatively simple but reasonably feature rich project based on my own personal setup and all features are working apart from (of course), Camera, CTS fix and custom wallpapers - otherwise its 100% functional.
The Rom comes in a few parts and can be considered a hybrid of both TWRP and Magisk in terms of what we flash it on. Below is an extremely high level overview (please see my N20U thread here to get a full feature list)
1 - the Master module is flashed and Rom feature choices are made here - a Firmware base convertor zip to flash in TWRP is then created and sent to /internal storage/420rom folder
2 - in twrp the Firmware Base Convertor debloats a tonne of useless carrier crap and works a few other under the hood bits - this in turn sends the Rom Module zip to the same folder above (replacing itself in the process with this third zip to flash)
3 - The rom module is then flashed in magisk and actions all the choices made in the first flash - after a reboot you have all the rom features!
Please DM me if you would like to test a bit later - I will then get everything needed to flash together for you to test a bit later.
If windows 11 devs have sorted the annoying sleep bug in build 22458 then ill upload some bits today
Iv been busy getting a few things sorted this week so apologies for the delay
We now have a TWRP and are able to root (should you feel able to do without the camera for a bit like myself)
I will be posting my Rom thread and also a detailed guide in rooting our Fold devices this evening so we can get things kicked off
exocetdj said:
Iv been busy getting a few things sorted this week so apologies for the delay
We now have a TWRP and are able to root (should you feel able to do without the camera for a bit like myself)
I will be posting my Rom thread and also a detailed guide in rooting our Fold devices this evening so we can get things kicked off
Click to expand...
Click to collapse
For the sake of figuring out the camera situation, I have a question. Is your rom based on our stock rom?
And same kernel or modified kernel?
Having something to compare stock firmware to for the sake of learning kernels would be substantial to help
Acoustichayes said:
For the sake of figuring out the camera situation, I have a question. Is your rom based on our stock rom?
And same kernel or modified kernel?
Having something to compare stock firmware to for the sake of learning kernels would be substantial to help
Click to expand...
Click to collapse
Its not your standard TWRP flashable Rom zip as such and we just use the stock kernel at the moment - this will be until my teammate can make one for us
the AP file ill provide contains TWRP and the FSTAB fix to disable encryption but only the stock boot.img for now
all features on my magisk rom are working apart from custom wallpapers thankfully so good enough for beta release
Edit, oh and camera lol