[ROM][AOSP][7.1/8.1 EXP][K3.4][Repartition] Unlegacy Android Project - Transformer TF300T Android Development

The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T​
Introduction
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. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17

Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.

REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.

How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom

androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:

androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.

androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS

TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.

Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned

I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?

@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.

Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.

I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash

Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.

@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.

@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).

@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.

Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.

Related

[ROM] [OFFICIAL] RESURRECTION Remix OPPO Find7 [MM 6.x][LVM]

XDA:DevDB Information
[ROM][OFFICIAL] RESURRECTION Remix OPPO Find7 [MM 6.x][LVM], ROM for the Oppo Find 7
Contributors
opposeeker, RoppoFon
Source Code: https://github.com/resurrectionremix
Source Code: https://github.com/find7s
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 5.7.4_r72
Created 2016-07-28
Last Updated 2016-10-07
[A] - INTRODUCTION
This is a continuation of a previous port of Resurrection Remix for the FIND7.
The predecessor was discontinued by the foregoing maintainer soon after its start within a month's period. This port was set up independently from it, all new from scratch, escpecially with proper LVM-Implant (i.e. w/out corrupted sdcard0, see images in the upper screenshot compartment of this page)
... more?
A lot of maintainers stopped their activies for the FIND7. It happened several times to me with different ROMs since I own this device. I really got fed up with the situation:
Only a limited number of ROMs left available for the FIND7 - shrinked down even more when counting only those with LVM-support. As soon as you get used to it, the individual maintainer in charge doesn't care anymore.
I prefer reliability and continuity in real life and therefore - surprise! - I'm really not in the mood exchanging my "technical assistants" on a monthly basis just because the geeks have left the playground for new toys...
Since Resurrection Remix is an awesome, well balanced ROM, I wanted to keep using it! Including enhancements and security fixes in future, of course. And I didn't want to buy a new (maintained-for-how-long?) phone just for that reason. The Devs @ RR are dedicated and strive for sustainment and stability just as I do.
Obviously, they can't take care for each and every piece of hardware on the market. - What to do...?
<b>If nobody else does it - you'll have to do it yourself!​</b>
So I did. Still wondering about it, since I didn't have a clue : -)
---
I'd like to share this port with you to enlarge the (limited) choice for us FIND7 users. BTW, since it has eaten an enormous budget of my time and resources, it would be real waste (and blame) not to ... especially as I participated from the work of so many people plus individuals supporting me personally to get this whole thing together.
Hall of Fame:
Being myself an advanced user who had no deal with "porting" or "maintaining" until very recently, I'm very grateful to the following individuals for their personal support:
@Schneiderle - not even owning this device by himself, he was a patient teacher to me "Android Infant" helping me understand the basics and preparing the ground
@maxwen - for his useful hints on LVM, since he has done it properly for Omni and TWRP
@anders3408 - implemented LVM for DU and let me share his work (+ lots of useful hints!)
Thank you, guys!
Thanks to:
Google for creating an alternative to the "fruit monopoly", CyanogenMod and ResurrectionRemix-Team, among many many others, I'd like to express my respect to those in the communicty who spent their time in creating Tutorials and How-To's, so beginners have a chance to get into this without attending University.
I'm also thankful to people like @Entropy512 who made LVM available to the FIND7 initially and therefore saved a lot of people from claiming their Oppo as "real bad buy".
(B) - LEARN MORE about RR, support and unwanted features
If you have specific questions concerning features, requests, bug reports etc., visit the capitol of ResurrectionRemix directly and get involved.
You'll also get there a full list of all features, support and up-to-date info.
Don't blame/flame if something doesn't work - check with others first: if other people with other devices have equal "unwanted features" - then post in the RR-forum - not here.
[C] - MISCELLANEOUS
I am not a dedicated maintainer nor will I be 24hrs around to nanny. I don't code anything (except for the purpose of mixing things up : - )
I just brought existing stuff of other genius' together, so the whole mixture works in this specific device. No more - not less.
This needs to be re-done for fixes and enhancements from the "ethereous" (=>genius) part of the Android world from time to time. I'll take care for these updates as time allows and as long as I will be using the device myself - this should should be for a while from now, at least up to mature "Nougat", let's see from there.
However - by downloading und using this port you declare: not to ask for ETA(!)
This ROM is a well-balanced and sophisticated one, that's why it's my favoured.
Go and try it if you haven't done so - and you'll see why!
Here we go:
[D] - FLASHING INSTRUCTIONS:
---------------------------------------------------------------------
BEFORE FLASHING - SAVE YOUR DATA!
---------------------------------------------------------------------
Like in real life, you should have a basic understanding about what you are doing. Whatever you do: You'll do it at your own risk. I'll take no liability for anything. If you don't agree - don't touch it!
Coming from whatever (everlasting-beta) stock ROM by Oppo:
If you previously changed your partition type with Oppo, revert to the original (default) FIRST.
(Should you have created it with 2.1.5 and up (without resizing,) you can leave it as it is).
Then
- Connect your phone to a PC via USB and
- Unlock your phone if this is your fast attempt to install a ROM (fastboot oem unlock)
- Flash TWRP recovery (fastboot flash recovery TWRP-Version.img)
- Reboot to Recovery
Proceed with steps below
Preparing for LVM
Setting up the whole internal storage partition w/out splitted
storage for apps / data requires the following prerequisites:
- TWRP Recovery installed (nothing different)
- Using setuplvm.zip (get from upper download compartment of this thread and save on your external sdcard for later use)
Setting up LVM
- Go to TWRP-Recovery
- Be super-pedantic: Wipe system/data/cache/dalvic
- Flash setuplvm.zip (will wipe everything incl. internal storage!)
- Reboot to recovery
- Flash ROM
- Flash GApps
- Reboot
Errors while setting up LVM?$&%??
- Reboot to TWRP Recovery and flash setuplvm.zip again.
- Reboot to TWRP after that again to proceed flashing.
Coming from another ROM
Note:
It's Aliens's Law to flash modem first to avoid problems with immigration. Travelers from Oppo Stock ROM have a visa and don't have to.
- Get modem files (from upper download compartment of this thread - save on your external sdcard)
- Book into Recovery
- Flash modemxxxx.zip
- Be super-pedantic: Wipe system/data/cache/dalvic
- Reboot to Recovery
- Flash ROM
- Flash GApps
- Reboot
Note: If you currently use whatever Unified XX flavor : Revert to the default partition layout with the tool by the respective provider prior to flashing this ROM.
Then proceed with above steps. Failure to do so may result in unwanted behaviour. The least you may expect is a "corrupted" sdcard.
Download Links:
ROM downloads see Post #3
3rd party add-ons see Post #4
Little Q & A
Check the General FAQ of Resurrection Remix Headoffice
This port is designed for the *FIND7s (X9076)*,
since that's the device I own. It has been reported working with the Find7"a" version, too. Make sure you'll reduce the screen density to "480" in settings after successfull flash. Applies to "A"-users only. EDIT: The last version of RR w/ MM (5.7.4) has an extra build for the Find7a. See Post #3 below (Download links).
New LCD support? - No.
It has been reported that this port does not support the new LCD. Although it is built-in the sources, users report it simply doesn't work.
There are kernel patches available in the net, though, they have side effects beyond your control - so no recommendation from this side. Sorry.
This port comes with proper LVM support. Any other?
You can use LVM if you want. Or keep using the original partition layout. That's the freedom of choice you'll get with this port. No other flavors are being supported (see OP, Section D)
This ROM comes pre-rooted. Is it possible to un-root?
Yes. Install SuperSu (see Download Section abv). In the settings of SuperSu you'll see options for unrooting your device.
Do I have to donate if keep using this ROM?
You don't have to at all, no matter if you just give it a try or keep using it forever....it's all open and free of any charge! If you are very satisfied and feel like donating, well, I won't reject : - )
See the "Donate to me" button on the left or in my profile. Thank you!
Download Links:
ROM: Resurrection Remix 5.7.4_r72 | Changelog | Mirror Download
ROM (FIND7a only): Extra build for the Find7a. | Mirror Download
GAPPS: Choose any, I prefer BaNkS
Recovery: TWRP (mandatory for LVM-use!)
Modem: see upper download compartment of this thread
LVM: see upper download compartment of this thread
SuperSU : This ROM is pre-rooted. Here you'll get SuperSU.
3rd Party Add-ons
Oppo Camera Mod
http://forum.xda-developers.com/oneplus-one/themes-apps/port-coloros-camera-cm11s-t3030369
MaxxAudio
http://forum.xda-developers.com/oneplus-one/themes-apps/app-maxxaudio-cos13-cm13-t3355120
...anything else...? Yes.
Greenify
App singing lullabies to background apps so they'll get to sleep while not being used- saves battery!
Bettery Battery Stats
What's giving me an empty battery so fast...? Here you'll get better statistics who's eating too much!
thanks for your great work!
o my god !!!! Thanks you !!
Working great... Now Just need to be officialize the incoming builds :laugh: :good: :highfive: :laugh:
Thanks for continuing Resurrection Remix builds. Does this rom supports F2FS partitions on /data, /cache, /externalsd? and does this also support Coldbird Unification Method? Thanks.
@opposeeker thank you man! Works great. And like before it is working on my find 7a x9006 version so you can edit the post to support this version as well
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
hulicow said:
Thanks for continuing Resurrection Remix builds. Does this rom supports F2FS partitions on /data, /cache, /externalsd? and does this also support Coldbird Unification Method? Thanks.
Click to expand...
Click to collapse
Don't know about coldbird, but this does work with the chinese partition layout; tried it myself
Tested now and I confirmed that only external sdcard is supported to use F2FS partition. It won't boot when /cache partition is formatted to F2FS, when /data partition is formatted to F2FS, the Encryption Unsuccessful prompt will appear. Coldbird partition will be unify the storage upon using the Chinese unified zip file.
meh... another rom wich have not support for r63419 Display. Useless for me
Thx @opposeeker n @RoppoFon. I love u guys
roi_xordo said:
meh... another rom wich have not support for r63419 Display. Useless for me
Click to expand...
Click to collapse
If you'd kindly asked, whether this may be on the list for the future, you'd have gotten a friendly reply...since this thread is online not even one day(!) and I am still so happy that we have a future now with this ROM.
Too bad you've missed the chance to get on the beta list.
Many of us have this version of find7 (the display r63419 ), and your rom , like many others are not suitable for our devices. If this were a new problem , I would understand that it was not covered , but it is something that happens many months (or years) ago, and developers follow cooking roms that do not solve this. Inconceivable and useless . But calm down my friend, do not bother to fix it, I dont need this useless rom, in fact, I will sell this phone soon, with Omnirom installed , which works fine from the beginning.
Tried this rom on a 7a. It works perfectly (just have to adjust the dpi) but I noticed there's a big battery drain from Cyanogenmod System.
Hi dev could please see this, Problems or Features Request:
Can not disable hardware navigation keys when enabling software navigation keys. *problem*
Can not use F2FS partitions properly on /data and /cache partitions *feature request* I hope this will be added in this rom and take the speed advantage of F2FS over EXT4.
Enable Coldbird partitioning method out of the box without using chinese unify zip. *feature request*
QS Tiles must like crDroid/Cyanogenmod style where user can add multiple tiles without like clutter on the long list. In CyanogenMod and crDroid, you can scroll and select QS Tiles from left to right, in RR you can add but it is listed on a long list manner. *feature request*
@opposeeker installed this, choose SD card as internal storage, Unable to copy backup from system to phone using USB even after changing from charging to file transfer
Flashed this last night, running very well so far. I haven't found any issues yet. Thanks for this amazing rom
Charging is running out quickly. I wonder if there will be improvement in the new version?
Does this support the newer lcd?
thanks

[ROM][unified][4.4.4] OmniROM

OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
​
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18
Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again
Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...
Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?
Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).
...anyone gotten Xposed Framework installed/working with this? Halp
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this
@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.
Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk
New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers
March update is online. Enjoy!
Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned
People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188
The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

[ROM][9] LineageOS, ResurrectionRemix, AEX, PE // personal builds

This thread was formerly "[ROM][9] LineageOS 16.0 + AOSPExtended + PixelExperience // personal builds" - yes, once again, the title can't fit the full names of all these ROMs :/
This thread hosts personal builds of LOS 16.0 and other Android 9 (Pie) ROMs for Mix 2, currently built from @wight554 's trees. Similar to Oreo, full credits to Wight and others behind the scene for the bringup, allowing us to build upon the awesome work.
Currently I build the following ROMs, usually monthly (in sync with security patch):
LineageOS 16.0
ResurrectionRemix 7
AOSPExtended 6
PixelExperience 9
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
...
What's working:
Everything?
Instructions:
Coming from official MIUI? Since the new encryption has been implemented, you only need to wipe (not format) /data.
Flash any Pie firmware (firmware Stable V10.4.1.0 recommended) for builds starting from May, or firmware Stable V10.0.2.0 otherwise.
Use official TWRP or OrangeFox.
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies to Pie
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "9" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
https://github.com/wight554/
About "official" status:
Currently I don't plan to apply for "official" for any of these ROMs, because 1) Wight is the actual maintainer who did the bringup and maintenance work, and 2) I like to be able to apply changes at will to the OS itself without restrictions from the official team.
Donation:
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 16.0, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, wight554, Cozzmy13
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V10.4.1.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2018-09-25
Last Updated 2019-09-27
Reserved
Just an additional note: I'm not as enthusiastic about building ROMs as I was early this year, so expect less regular updates and/or unanswered fix/feature requests. I'm just a builder, not nearly as capable of Demon or Wight doing all the heavy lifting, so I'll only do what my ability/time permits.
Thanks for all your work, Andy
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Fairtex said:
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Click to expand...
Click to collapse
Statusbar customizations like network traffic aren't merged yet, just wait.
Can we have that slide down gesture to bring the notification bar down like we had in PE Oreo? Thanks
Hey,i have a question. Is it possible to port full screen gestures from miui 10 to los 16?
Are the quick settings on the status bar still a bit off on PE edition?
Folks who have tried, please do let me know about the battery consumption. This build added some CPU governors to the kernel and defaulted little cluster to one of them, and I'm not sure of its actual impact. It's my first time fiddling with kernels and I can't guarantee the change will be satisfactory.
Fairtex said:
Are the quick settings on the status bar still a bit off on PE edition?
Click to expand...
Click to collapse
I acknowledge the lack of padding there, but I don't quite want to look into it now. It's supposed be a problem for PE upstream anyway.
Greetings!
I've downloaded the rom last night. And until now, I have no problem: the camera works perfectly, the sound sound good and gaming performance are good.
The thing which attracted me was the mention of "Lineage OS" and I'm not disappointing to see that it's so close of the official and stable version . I'm blind in context of "find the bugs", so maybe we could find some but this is not my domain.
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Install custom navigation bar .Its work fine
Wysłane z mojego MI MIX 2 przy użyciu Tapatalka
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Expanded Desktop is a feature that will surely be merged in the future. As the other user said, there are 3rd-party apps that can achieve the same goal. I myself am using Tiles since it places a shortcut in Quick Settings.
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
MrSammyMcG said:
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
Click to expand...
Click to collapse
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
AndyYan said:
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
Click to expand...
Click to collapse
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
MrSammyMcG said:
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
Click to expand...
Click to collapse
This is Treble-enabled but this is NOT a GSI (Generic System Image). You still flash as you would do a regular ROM, just with a Treble-enabled recovery.
Quick update to sync with Wight's updated battery data - from this build on you're supposed to use newer firmwares. OP has been updated with the mandatory new firmware requirement and TWRP build from Wight.
Thanks for your work,I have used aex for two days.It is very nice.But I notice a small problem that sometimes the fingerprint unlock is very slow and I have to touch several times to unlock it.Is it a bug of this rom?
Duble tap on screen for wake up dosent works too

[ROM][4.4][UNOFFICIAL] LineageOS 16.0 with 4.4 kernel

LineageOS 16.0 for Xiaomi Mi 5 with 4.4 kernel
Remember this is a beta release, althought I've been using it for more than a week and it's working perfectly.
If you experience any bugs, panics or so, please report full logs to me (logcat and dmesg, you can look in /sys/fs/pstore)
Installation:
You can flash it on top of OFFICIAL 3.18 LOS also you can always go back within a dirty flash.
For safety reasons always perform a backup of your important data!
Features:
This is well-known LOS, none of the functionalities have been altered.
Build is running 4.4.189 kernel with many improvements over 3.18, it will keep this device alive for upcoming Android releases.
Kernel is suited with initial bug fixes, however, it's a stock kernel without any advanced tweaks. It's built with CLANG (!).
Working:
Probably everything!
Not working:
Kernel is permissive
Temporary MTP fix (I didn't have enough time to investigate it well):
Developer settings -> Default USB conf -> MTP -> connect cable -> profit
READ ONLY IF YOUR DEVICE IS ENCRYPTED:
There is an incompatibility between 3.18 and 4.4 kernels, you have to flash new TWRP with 4.4 kernel, otherwise your data partition will be DAMAGED!
Nevertheless there could be a need to full wipe your /data (magic Format Data button in TWRP) so perform a FULL BACKUP.
Download:
LineageOS zip
TWRP
Future development:
Device tree will be created from scratch over new Qualcomm tag to get rid of old junk. Full Treble compability will be provided.
More kernel bug fixes
Vendor update
FAQ:
Can I install XXX ? Does it support XXX ?
- It's still LOS, it supports everything what stock LOS does.
Can't you ship kernel package only?
- No, ROM has to be modified to meet 4.4 requriements. You can't flash 4.4 kernel on top of 3.18 ROM.
But why 4.4? Do I need it?
- More fixes, more performance, more support. If you want, search for kernel changelog.
EAS?
- Not now, there are more important things to work on.
If you want to buy me a coffee, please consider donating, I've put much effort to make it working.
DONATE
Join Mi5 group on Telegram
Huge thanks to Zuk kernel team for initial 4.4 support!
Credits:
@DD3Boh
@YaroST12
@kenny3fcb
@Luk1337 - fix for USB
@Jawor245 - random stuff
@RadixCube
XDA:DevDB Information
LineageOS 16.0 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre/msm-4.4
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-01
Last Updated 2019-09-01
Reserved
Reserved
In Antutu 7.2.3 tested fresh, stock LOS + nano gapps and fresh this rom + nano gapps on my 32Gb version. Biggest improvement for my device is memory +22% in Antutu points.
Stock: 144 086 overall
CPU: 50 420
GPU: 53 892
UX: 34 159
MEM: 5 615
4.4 LOS: 148 079 overall
CPU: 50 600
GPU: 54 615
UX: 35 657
MEM: 7 207
@xNombre great job!
I'll be testing your ROM in the future for sure. Looks very promising.
It would be great if you pulled the Floppy Kernel mods to tweak your 4.4 kernel
(Just my wish)
However, congratulations man.
I really appreciate your effort I would love to test your ROM But I only want to know 2 things before if someone can help.
1. Can I use it as daily driver?
2. Android Auto is working?
3. Will I need to do clean flash for future updates? Atleast for couple weeks.
Thanks
I'm using it for two weeks and no problems here.
If Android Auto is working on official LOS it will for for mine, too.
Nope, not for now.
#edit
Here is the new kernel you can flash on top of my LOS. (DON'T FLASH IT ON ANYTHING ELSE)
https://androidfilehost.com/?fid=1899786940962575411
Changelog:
add exFAT and NTFS
fix problems with wakelocks
use LZ4 for ZRAM
debloat a bit
skip sync for better battery
@xNombre What is the reason behind choosing 4.4 instead of a newer LTS version like 4.9 or 4.14? Or was the decision out of your hands?
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Whoa, calm down, mate. I just wanted to know the rationale. Knowing that msm8996 supports 4.4 is good enough for me. :good:
Sorry to hear about the two damaged devices, though. That must have been extremely frustrating.
xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Lots of love for 4.4 kernel.
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Thank you for your work. This is quite big actually.
Thx
Myxomatom said:
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Click to expand...
Click to collapse
There it no correlation between kernel and RIL. No changes here. Maaybe sth nice will happen with new vendor blobs but you have to wait for it.
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
bido1 said:
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
Click to expand...
Click to collapse
yeah ... been using it for the last 3 days ... the battery performance is better than the official one without any tweak
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
netrixken said:
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
Click to expand...
Click to collapse
Are you using TWRP provided in first post?

[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo)

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

Categories

Resources