[ROM]-[11.0]-[KIEV]-Havoc-OS-4.x-[OFFICIAL] - Moto G 5G ROMs, Kernels, Recoveries, & Other Devel

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications,
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI crafted by @SKULSHADY.
Many useful features that provide a smooth premium experience.
Just flash and enjoy...​
https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6​
Founder & Lead Developer:
SKULSHADY (Anushek Prasal)
DevOPS & Scaling:
Irongfly (Sukeerat Singh Goindi)
Support Team:
theo.j22 (Tushar Jain)
​
If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Maintainer PayPal: https://www.paypal.me/SyberHexen​
About Us: https://havoc-os.com
ROM: Havoc-OS - Latest Official Build
Recovery: Unofficial TWRP
Open GApps: https://sourceforge.net/projects/opengapps/files/arm64/
Magisk: Magisk
Factory Firmware: Stock Firmware Mirror
Copy Partitions Zip - courtesy of @filipepferraz: copypartition.zip
Telegram Support Group: https://t.me/havocofficial
Telegram Announcements Channel: https://t.me/Havoc_OS
Code Review: https://review.havoc-os.com​
01. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Create backup. i.e. EFS / Persist and put somewhere safe
## YOU ONLY NEED STEP (04) ONCE.. (Or After Reflashing Factory Firmwares) ##
04. Flash "Copy Partitions Zip" In TWRP "SLOT A"
05. Flash the ROM and TWRP installer
06. Choose Reboot -> Recovery
07. Install GApps & Magisk
08. Reboot -> Bootloader
09. fastboot -w
10. Reboot and Enjoy
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-3: Updating "Dirty Flash"
01. Flash ROM + TWRP installer
02. Reboot -> Recovery
02. Install Gapps + Magisk
03. Reboot -> System​
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.​
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
Contributors
SyberHexen, SKULSHADY, erfanoabdi
Source Code: https://github.com/Havoc-OS/​

RELEASES:
Havoc-OS v4.11 Unofficial Update
Date: 19-11-2021
Device: Motorola G 5g (kiev)
Device changelog:
- Unified Device Tree
- Updated GPS, Location & Display from Tag 'LA.UM.9.12.r1-11500-SMxx50.0'
- All blobs now updated from Kiev Tag 'RZK31.Q3-25-15'
- Update Properties for kiev product
Download Link: https://www.androidfilehost.com/?fid=7161016148664842064

Past changelogs:
===============
PREVIOUS UPDATES
===============
========================
Havoc-OS v4.9 Unofficial Update
Date: 25-09-2021
Device: Motorola G 5g (kiev)
Device Changelog: Initial Build
========================

Whoa this is like the first comment? Thinking this was out, I run havoc on my Galaxy note 4, that old dinosaur, but y'all have gone and brought the best ROM to my new phone? I was gonna factory reset to clear cobwebs, but man y'all make my day thanks for this.
Question and I feel I've asked you this on something else, #4 is it needed on fresh install from stock?

bobbyp1086 said:
Whoa this is like the first comment? Thinking this was out, I run havoc on my Galaxy note 4, that old dinosaur, but y'all have gone and brought the best ROM to my new phone? I was gonna factory reset to clear cobwebs, but man y'all make my day thanks for this.
Question and I feel I've asked you this on something else, #4 is it needed on fresh install from stock?
Click to expand...
Click to collapse
Yea I've been super lazy making the xda thread lol..
As regards to step 4, highly recommend if it's the first time installing custom rom.
This ensures the firmware on both slots are the same version.
Sometimes moto ships with blank b partition (or not fully setup)
Or in some cases ota upgrades bootloader from android 10 to 11 on just one slot which can cause softbricks in bootloader when slot switching is called.
Edit
It also should be noted that the new twrp3.6_11 likely won't boot on these older releases as bootctrl hal is now upgraded to 1.1

SyberHexen said:
Yea I've been super lazy making the xda thread lol..
As regards to step 4, highly recommend if it's the first time installing custom rom.
This ensures the firmware on both slots are the same version.
Sometimes moto ships with blank b partition (or not fully setup)
Or in some cases ota upgrades bootloader from android 10 to 11 on just one slot which can cause softbricks in bootloader when slot switching is called.
Click to expand...
Click to collapse
Yeah moto is a pain, but hey it's better than Sammy locking us out, thanks for quick reply, just got the files downloaded lol talk about timing.
Side note on xda laziness, no worries it's not what it used to be around here, I just miss the old days when it was not so filled with ads and computers and missing posts or broken links or click bait, you know when it was xda. Lol
After thought, how do you flash magisk? They got rid of the flashable zip and straight to apk? Or did I miss something?

Change the name of the APK to ZIP and flash.

bobbyp1086 said:
Yeah moto is a pain, but hey it's better than Sammy locking us out, thanks for quick reply, just got the files downloaded lol talk about timing.
Side note on xda laziness, no worries it's not what it used to be around here, I just miss the old days when it was not so filled with ads and computers and missing posts or broken links or click bait, you know when it was xda. Lol
After thought, how do you flash magisk? They got rid of the flashable zip and straight to apk? Or did I miss something?
Click to expand...
Click to collapse
Twrp should have support of flashing it in either Zip or apk form (twrp 10)

anyone know if this works on Fi network? thanks.

Holymsophy said:
anyone know if this works on Fi network? thanks.
Click to expand...
Click to collapse
Yes I'm also a Fi user

Thanks!
Just got the ace, tried Lineage OS 18.1 but couldn't get network signals on that. so was just wondering.

SyberHexen said:
Yes I'm also a Fi user
Click to expand...
Click to collapse
For some reason, when I boot back into recovery via adb, touch screen stops working

Holymsophy said:
Thanks!
Just got the ace, tried Lineage OS 18.1 but couldn't get network signals on that. so was just wondering.
Click to expand...
Click to collapse
Hmm well the trees are more or less the same.
Whats your location / prominent carrier when on stock?
Normally I'm just defaulted to tmobile but switching to US Cellular also works for me.
Did you flash copypartitions.zip and take backup of efs?

I'm in Dayton, Oh. on Lineage, for some reason the network data won't come on. And yeah, I can always revert when I need to.

SyberHexen said:
Twrp should have support of flashing it in either Zip or apk form (twrp 10)
Click to expand...
Click to collapse
I thought lineage couldn't use twrp?? Last time I flashed, the first time actually as it was brand new.... And yours lol... Twrp would no longer boot, not past splash at least. The lineage recovery blocked it I was told. But word, I have a lot to back up I'll be flashing it here in 2 minutes get back with y'all tomorrow on feedback

Holymsophy said:
For some reason, when I boot back into recovery via adb, touch screen stops working
Click to expand...
Click to collapse
Use mouse via otg and input screen lock pin, it's encrypted and twrp uses it like it's you to unlock the encryption, once you input pin all touch should work

Is there any chance I can build pixel experience using the source code. I have never really built android for a device before so I want to give it a shot

SyberHexen said:
Hmm well the trees are more or less the same.
Whats your location / prominent carrier when on stock?
Normally I'm just defaulted to tmobile but switching to US Cellular also works for me.
Did you flash copypartitions.zip and take backup of efs?
Click to expand...
Click to collapse
Its worth noting xfinity mobile did not work on lineage os (or any GSIs for that matter) but worked perfectly on havoc

Ok after trying for a few days here's my thoughts.
1. Upon rebooting USB debugging is automatically on, normally this isn't a problem more of annoyance that apps check if it's on and won't load.
2. For some reason it likes to stop, as if buffering but throughout the whole phone. It stops but more or less it's doing that.
3. It seems like it's just stock moto on Android 10, with extra options that are a little more or less useful/wanted.
4. Much harder to hide root from apps, actually have to turn su off in magisk and freeze magisk with ice box to hide it, even tho in 10 they have other apps files hidden from other apps, making hiding root even easier, strange.
5. Probably the one that I will revert to stock or find a new rom, 5g is not 5g speeds. Normally I'm hitting 400mbps this rom 75mbps.
Other than that it's smooth, better than lineage but not polished enough to take over as daily driver.
Edit, I do thank you sir for getting twrp installed on my phone. That is the best thing I've gotten in months. Great job with the Rom too new for me tho I'll wait till you iron it out a bit
Second notice. Twrp touch isn't working, gotta otg a mouse to input pin before it's working

Everything working for me, loving it, thank you!
My only issue is the notification light when charging, that thing is bright. Like flashlight/shadow puppets on the wall bright. Am I missing a setting somewhere, or is it not able to be turned off?
It is nice to have a notification light for notifications, though. It's been years since I had a phone with one, didn't realize how much I missed it.

Related

[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.
What's not working:
SELinux is permissive
Instructions:
Attention! The bootloader needs to be unlocked!
Attention! You'll need a vendor partition!
1. Install the Universal bootloader and your model specific modem. Download
2. Flash vendor creation tool. Download (unnecessary, if done already)
* On first flash the device will reboot, just reboot to recovery and reflash the zip.
3. Update your version of TWRP. Download
4. Perform a backup of your current ROM. (optional)
5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
6. Install the ROM. Download
7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
8. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev
Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Testing
Created 2018-08-19
Last Updated 2019-07-28
Some features of LineageOS are missing, but they will be merged in future builds.
Some features may or may not work, sometimes also differently. Feel free to ask
any question.
UwU neat p finally
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Predatorhaze said:
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Click to expand...
Click to collapse
Read the instructions, they are there for a reason.
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
Los 15 is abandoned I assume?
And 16 besides nfc and volte is functional?
Thanks for contributing.
wow. It is all happening very fast.
Thanks
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important.You also say its optional to wipe system data cache if come from other rom,but in fact its REQUIRED to wipe system data if you come from other rom
Click to expand...
Click to collapse
GApps is always optional because some people want them and some don't. If you read carefully, on LOS 15.1 is the same.
I have heard Android Pie got GAPPS inbuild and i believe that because google dont want microg users.So its not true...
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Click to expand...
Click to collapse
Why should I mention other stuff if I already provide a working bootstack. Why would I give a download link for Gapps and add the the optionally tag, if they would be build in.
thnx @OrdenKrieger and all others involved :good:
Nice build - working smooth, no lag
DT2W ok
Used bitgapps as a starter
At last NO echo and incall volume adjustable
FP working
Hotspot OK
camera pics ok, recording crashes when saving - on both pics and video lag on movement
usb preferences work
afaik there is no way in settings to reverse softkeys so i used mine : https://androidfilehost.com/?fid=3700668719832237510 (be sure to be rooted and mount system/vendor)
Notifications work - on lockscreen and leds ok
EDIT : after testing a bit, definitely more heating and i mean a lot, more cpu load (f.e. as on the PPR1 img )..... could not stabilize temp on cpu 92C ! Only after applying powersave in EXKM...definitely something to look into (only Wifi on, no BT, no specific apps running....only the basic stuff to test your build )
EDIT2 : fast charging way more heat on battery - also battery drain too fast even with no cpu load
Will test further
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
2000impreza said:
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
Click to expand...
Click to collapse
yep, tried recording now and crashes when saving. Also lag on movement.
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Hellsbend said:
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Click to expand...
Click to collapse
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
ttkian said:
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
Click to expand...
Click to collapse
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Hellsbend said:
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Click to expand...
Click to collapse
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Edit
Of course, it's easier to flash because Post 1,2 and 3 are "included" now.
So it's quicker to flash.
Hellsbend said:
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Click to expand...
Click to collapse
Not quite. Mine was derived from Redmi Note 4. It looks the same for sure but devs have done some adjustments as to ECHO, dt2w working, notifications, ....
BUT my LOS16 build had no heating, nice CPU load and no battery drain and no heating when charging at all but had the annoying echo as we know it on other gsi builds and no dt2w, no notifications working on lockscreen, no led...
So there are definitely pros from this build and pros from mine.
Hope they can manage heating.
Also back on AEX as the heating (in my case) was too heavy. Dont want to ruin anything now

[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [enchilada]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Notice:
In order to install GApps, you must flash the ROM (and TWRP zip) then reboot into TWRP before flashing our custom GApps package (as this switches slots).
We recommend start off the newest OxygenOS Oreo builds, but we're using the 5.1.8 Fingerprint to pass SafetyNet when combined with Magisk, so you'll see the Popup to flash the proper vendor when using it with a newer OOS. Don't worry though, it's just the popup.
We know it’s complicated, but it sure is worth it!
Install Instructions:
Flash the aforementioned OxygenOS zip on both slots
Move your ROM + [GApps] + TWRP.zip to your internal storage
Boot the TWRP.img > Check what Slot you're on (Reboot Menu) ->Wipe Data & Cache -> Flash the ROM as well as the TWRP.zip
Either Reboot to system or, in case you want GApps, reboot to recovery via TWRP (Reboot -> Recovery)
Check and confirm that you are on the opposite slot from Step 3. If not, switch to it and reboot the recovery again (Reboot Menu) -> Flash GApps (and whatever else you want to flash -> Reboot to System -> Enjoy CarbonROM
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the OnePlus 6
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-09-12
Last Updated 2018-09-12
First post! Gonna test this out and report back
Instructions say to flash newest oos on both slots, but newest is a pie rom. Will that work,.or need to flash 5.1.11
itsdan313 said:
Instructions say to flash newest oos on both slots, but newest is a pie rom. Will that work,.or need to flash 5.1.11
Click to expand...
Click to collapse
Definitely it will be OOS 5.1.11 and below as the rom is Android Oreo based.
Whoa! Official Carbon is here! Awesome!!! Thanks for supporting op6!
Install oos on both slots? This not need, twrp makes automatic on both slots.
itsdan313 said:
Instructions say to flash newest oos on both slots, but newest is a pie rom. Will that work,.or need to flash 5.1.11
Click to expand...
Click to collapse
No, you need the Oreo one.
SpectraFun said:
Install oos on both slots? This not need, twrp makes automatic on both slots.
Click to expand...
Click to collapse
No, it doesn't...
Hi guys, thanks a lot for this ROM.
Just two things I noticed:
- Notification shade changed to a transparent gray instead of usual white
- Hardware key rebinding screen is blank under Settings > Fibers > Buttons > Advanced options
Otherwise everything else is working fine.
Nice. I was a heavy user of CarbonRom on me old Xperia Z3C.. Good times.
How does a ROM like this deal with the notch and such?
I'm on stock 5.1.11, rooted with magisk and using twrp recovery. Can someone explain exactly the process of how I install to both slots?
Wow, cool new Roms. I'll try this out. Appreciate it
Touch sensitivity is a tad off in the corners , requiring quite a few double taps
Kocane said:
Nice. I was a heavy user of CarbonRom on me old Xperia Z3C.. Good times.
How does a ROM like this deal with the notch and such?
Click to expand...
Click to collapse
I suspect not at all, Notch support is natively added in pie, so the general consensus has been "just wait for pie"
SpectraFun said:
Install oos on both slots? This not need, twrp makes automatic on both slots.
Click to expand...
Click to collapse
TWRP flashes itself to both slots. It does not flash the rom to both slots.
mixlex said:
I'm on stock 5.1.11, rooted with magisk and using twrp recovery. Can someone explain exactly the process of how I install to both slots?
Click to expand...
Click to collapse
It's the same process as updating, just do it twice. The system changes slots automatically when you flash the full rom zip. As you're already on 5.1.11, you should be able to just flash the 5.1.11 zip one more time, which will flash it to the other slot. Then reflash twrp, etc., as usual, and reboot. That will ensure you have the latest firmware on both slots, but if you want to be extra-safe, just do it again.
Glad to see Carbom ROM on OP6!
thanks!
oos gestures when removing nav bar?
law16 said:
oos gestures when removing nav bar?
Click to expand...
Click to collapse
I'd like to know this too, got used to them now I can't live without em
law16 said:
oos gestures when removing nav bar?
Click to expand...
Click to collapse
efinityy said:
I'd like to know this too, got used to them now I can't live without em
Click to expand...
Click to collapse
Buy this from the Play Store and you'll never be without OnePlus gestures ever again. You can even adjust the height of the gestures.
https://play.google.com/store/apps/details?id=com.ivianuu.oneplusgestures&hl=en_US
is it possible to port oneplus's face unlock to any custom rom, where it doesn't unlock with closed eyes and is better secured than Google's face unlock, also oneplus face unlock is definetely faster than Google so it'd be a really nice addition if developers could add it to all custom roms!!
ajsmsg78 said:
Buy this from the Play Store and you'll never be without OnePlus gestures ever again. You can even adjust the height of the gestures.
https://play.google.com/store/apps/details?id=com.ivianuu.oneplusgestures&hl=en_US
Click to expand...
Click to collapse
Buy an app that gives you the ability to use something that has been hardcoded into your phone since basically it's launch... Because fk logic. And an app will never replace hardcoded gestures, there's just too many factors that randomly could break it for me to want this app... Just look at the reviews of it
efinityy said:
Buy an app that gives you the ability to use something that has been hardcoded into your phone since basically it's launch... Because fk logic. And an app will never replace hardcoded gestures, there's just too many factors that randomly could break it for me to want this app... Just look at the reviews of it
Click to expand...
Click to collapse
I use it on every phone that I own and it functions as good as the stock OOS Gestures but with more customizability. I've never had an issue with it. The only time I don't use the app is when I'm in stock OOS. Reviews? I'm giving you one right now.

[EOL] [ROM+KERNEL] [Android Pie/9.x.x] [Unofficial] [EAS/F2FS] AICP 14

ROM is End Of Life (EOL) - https://forum.xda-developers.com/showpost.php?p=80584071&postcount=68
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
Latest Stable Release Version 14.0
Download link: https://mega.nz/#!ylpk0Qpa!0gbdQGWsNLPMSfbiDNFl7UbTLML4C1_ca7nhWHw8kSU
28/01/2019: First XDA Release!
Changelog of future releases will be here.
---
09/02/2019: Second XDA Release!
-Feb patch
-Updated rom
-Updated kernel
-Updated device trees
-Better battery better performance gucci
---
07/03/2019: 3rd XDA Release!
-March Patch
-Kernel Stability Improvements
---
Google Apps: INCLUDED!
You tell, please provide logs when requested...
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip. We recommend Magisk!
It is STRONGLY recommended to fully wipe your device before flashing if you're coming from a different ROM and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug. Once you're on AICP you can dirty flash new builds without wiping anything, unless stated otherwise!
How to flash for the first time:
(Again: Don't do it if you don't know it!)
If you've got everything nice and backed up:
1. Fastboot -w (not usually necessary, this will wipe data and internal as well as format to ext4 and remove any encryption).
2. Fastboot flash boot "twrp boot img" (depending on firmware, you'll need different twrp images. If August and prior, use the official one from twrp's website. Otherwise, use the F2FS TWRP image linked here - https://mega.nz/#!ewZTWaJB!xHe-_sV2hdbD6t6YAgeaHBASG5ecIfNqmaNVpqZZtlY).
3. In TWRP - wipe System, Data, and Dalvik.
NOTE - Its recommended to format to F2FS file system at this stage. However, not necessary!
Change filesystem: Go into Wipe > select Data > Change Filesystem > F2FS
4. Transfer the ROM zip and the TWRP installer zip to your SDCARD.
5. Flash the ROM zip and the TWRP zip (FYI, flashing a ROM by any method will install to the opposite slot, the TWRP zip patches both slots).
6. Reboot to recovery (Reboot > Recovery), ignoring when it says "No OS Installed" (this will automatically switch slots for you).
7. Back in TWRP - transfer the latest Magisk zip to your SDCARD and flash it. (Magisk always installs to the current slot).
8. Reboot to system. It will fail to boot once because of Magisk, that's normal just let it do its thing.
9. Go through setup.
10. Enjoy the ROM!
​
-------
The ROM has Gapps build-in, you DO NOT need to flash them. The root solution (Magisk) NEEDS to be flashed after you flash the ROM zip and TWRP zip then reboot recovery to switch slots.
Kernel source:
https://github.com/celtare21/kernel_essential_msm8998-1
-------
You want to see a "normal" night at the "DEV office", click here!!​
XDA:DevDB Information
AICP 14, ROM for the Essential Phone
Contributors
CamoGeko, KuranKaname, CamoGeko
Source Code: https://github.com/celtare21/kernel_essential_msm8998-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 14
Stable Release Date: 2019-01-28
Created 2019-01-28
Last Updated 2019-10-18
Recent Battery Screenshots.
This was a battery run as normal use cycle by me, it was a WiFi run only with no Mobile Data used.
Your experience may differ!
EDIT: 2nd set of screenshots added on 30th January 2019 from another run.
reserved again.
Reserved v3 just to be sure
Any recommended firmware or is the latest (January Pie) fine?
CamoGeko said:
This was a battery run as normal use cycle by me, it was a WiFi run only with no Mobile Data used.
Your experience may differ!
Click to expand...
Click to collapse
WOW!!!
Daemos said:
Any recommended firmware or is the latest (January Pie) fine?
Click to expand...
Click to collapse
Yeah, it doesn't really matter. Especially if you're wiping everything.
dirtyreturn said:
WOW!!!
Click to expand...
Click to collapse
No gaming or anything like that, just normal use.
Yeah the battery is from another planet [emoji16]
Guys the notification led working for you?
hypnz said:
Yeah the battery is from another planet [emoji16]
Guys the notification led working for you?
Click to expand...
Click to collapse
Yes it does occasionally
No for me doesn't working. Calls and messages notifications doesn't work even is enabled.
Android Auto work for anybody? No luck here.
Android Auto working proof!
billybong10 said:
Android Auto work for anybody? No luck here.
Click to expand...
Click to collapse
Yeah it's working fine here.
What problem are you having?
Sent from my Essential Products PH-1 using XDA Labs
CamoGeko said:
Yeah it's working fine here.
What problem are you having?
Click to expand...
Click to collapse
It works on the phone side but will not connect to the car. I can't get it to work on any custom ROM I've tried. Works perfectly on stock every time.
billybong10 said:
It works on the phone side but will not connect to the car. I can't get it to work on any custom ROM I've tried. Works perfectly on stock every time.
Click to expand...
Click to collapse
Same here....app runs fine but it never talks to the vehicle and integrates. When I try to force the two to communicate, settings show the attached. It's just never worked and the great devs over on the telegram mata dev channel have mentioned it's a known issue
billybong10 said:
It works on the phone side but will not connect to the car. I can't get it to work on any custom ROM I've tried. Works perfectly on stock every time.
Click to expand...
Click to collapse
The Doctor04 said:
Same here....app runs fine but it never talks to the vehicle and integrates. When I try to force the two to communicate, settings show the attached. It's just never worked and the great devs over on the telegram mata dev channel have mentioned it's a known issue
Click to expand...
Click to collapse
Yeah it seems to be a known issue with all custom ROMs at the moment.
The same as the OK Google integration.
No fix anywhere yet from what I know. If you NEED those functions I advise to remain on Stock for the time being.
Some Questions about the ROM
Is there a way to adjust the touchscreen settings input response? seems to lag when scrolling
Is VoLTE working? (I have AT&T and works fine on my stock AT&T Samsung S8)
Is wifi calling working? (I have AT&T and works fine on my stock AT&T Samsung S8)
thanks in advance
tbdj said:
Is there a way to adjust the touchscreen settings input response? seems to lag when scrolling
Is VoLTE working? (I have AT&T and works fine on my stock AT&T Samsung S8)
Is wifi calling working? (I have AT&T and works fine on my stock AT&T Samsung S8)
thanks in advance
Click to expand...
Click to collapse
Is there a way to adjust the touchscreen settings input response? - System ->Touchscreen settings ->Smoothness level 5 to 8
Is VoLTE working? - Yep.
thanks for this rom. If I changed my file system from ext4 to F2FS, will it wipe my internal storage?
c19932 said:
thanks for this rom. If I changed my file system from ext4 to F2FS, will it wipe my internal storage?
Click to expand...
Click to collapse
Yes
New Release, new Changelog - 09/02/2019!
Its been about 10 days since the initial AICP Pie release here.
A new ROM version has been deemed ready for XDA. See details below:
Release: AICP P
Developer: @KuranKaname
Date: 02/09
DOWNLOAD - HERE!
CHANGELOG
-Feb patch
-Updated rom
-Updated kernel
-Updated device trees
-Better battery better performance gucci
---
Its fine to dirty flash this build, here are the steps:
1. Reboot to TWRP
2. Flash ROM zip
3. Flash TWRP zip
4. Reboot Recovery
5. Flash Magisk zip
6. Reboot
7. Don't worry, be happy!
The OP will be updated today! :good: :laugh:

[ROM][OFFICIAL] dotOS v5.x for Pixel 3a XL[bonito][OTA]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
" #DroidOnTime "
ROM Version: 5.1.3
Device: Pixel 3a XL(bonito)
Maintainer: zapmicro
Build Status: OFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
CLEAN FLASH/First Time Installation :
1.Download the latest build and make backup
2.Unlock Bootloader
3.Reboot to bootloader
4.fastboot flash boot boot.img
5.Reboot to recovery
6.factory reset/wipe data
7.adb sideload rom.zip
8.Reboot to system
Note:- If you get no command while going to recovery, Hold the power button first. While holding it tap the volume up button and you will get to recovery
DIRTY FLASH :
1. Download the latest build
2. fastboot flash boot boot.img
3. adb sideload rom.zip
4.reboot to system
Note:- Gapps already included in the build
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.[/SIZE]
Download Rom Here
Download boot.img for GAPPS Here
Download boot.img for Vanilla Here
Complete Changelogs: https://changelogs.droidontime.com/
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
And all other open-source Devs/Teams.
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
dot OS source
dotOS-Device Sources
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
​
Contributors: zapmicro
Source Code: https://github.com/DotOS
Kernel Source: - https://github.com/dotOS-Devices/kernel_google_bluecross
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.1.3
Stable Release Date: 08-08-2021
Note:- Make sure you clean flash if you're coming from unofficial build
Reserved
Nice! Downloading now.
Very nice, thank you!
Running very smoothly and efficiently. Kudos! Are there plans to get this bumped to official at all? Also, does this support ElementalX?
Karitoriki said:
Running very smoothly and efficiently. Kudos! Are there plans to get this bumped to official at all? Also, does this support ElementalX?
Click to expand...
Click to collapse
It will get official soon, probably in next week, I'm not sure about ElementalX support, but it should work fine.
Im curious, what needed to be changed/tweaked to make this build for the Pixel 3a XL? Did you grab the latest source for dotos and patch a few files that needed fixing, or some other method?
Either way, thanks for the submission - it's pretty smooth!
-AADD
arfarfdan said:
Im curious, what needed to be changed/tweaked to make this build for the Pixel 3a XL? Did you grab the latest source for dotos and patch a few files that needed fixing, or some other method?
Either way, thanks for the submission - it's pretty smooth!
-AADD
Click to expand...
Click to collapse
Pixel 3a and 3aXL are unified almost. So you just need few different files device side, device vendor, kernel is unified across 3,3xl,3a,3aXL
There are no major changes needed from 3a to 3aXL. Also as when it goes official, you will be able to see device sources used to make this rom and with ota support.
awesome thank you for the reply!
Update 16/06/21
We go official.
1.Make sure you clean flash if you're coming from unofficial build
2.June security patch included
3.Auto brightness on initial boot
4.few other minimal changes
5. added stock google camera
Note:- Boot.img added in separate link
The official build kept failing to flash with ErrorCode kPayloadTimestampError
Yes, I followed clean flash steps.
Update on GAPPS: It seems the GAPPS version of the ROM fails to fully transfer, stopping at 49% and reports total xfer of 1 while normally it should report 2. Will update again once I figure out if this partial transfer is simply a bug of the ROM file and is being reported incorrectly via terminal or if it's actually broken.
Update 2: The ROM did, from appearances, successfully flash, with everything seemingly working as it should be.
Both ROMs do seem to have issues with how their flashing is being handled however, and should be corrected ASAP.
Karitoriki said:
The official build kept failing to flash with ErrorCode kPayloadTimestampError
Yes, I followed clean flash steps.
Update on GAPPS: It seems the GAPPS version of the ROM fails to fully transfer, stopping at 49% and reports total xfer of 1 while normally it should report 2. Will update again once I figure out if this partial transfer is simply a bug of the ROM file and is being reported incorrectly via terminal or if it's actually broken.
Update 2: The ROM did, from appearances, successfully flash, with everything seemingly working as it should be.
Both ROMs do seem to have issues with how their flashing is being handled however, and should be corrected ASAP.
Click to expand...
Click to collapse
Thank you for looking into the matter, I know the issue for vanilla version
For now gapps version is good, yeah it will show error when rom gets flashed, though it gets sideloaded successfully. Gapps version is recommended for now.
On a support call with my mobile provider and they asked me to reset network and Bluetooth settings. Get to the screen where the internet says should be a reset settings button and it's not there.
LordNerevar said:
On a support call with my mobile provider and they asked me to reset network and Bluetooth settings. Get to the screen where the internet says should be a reset settings button and it's not there.View attachment 5347267
Click to expand...
Click to collapse
Pull up the bold text, the heading "Reset WiFi, mobile and Bluetooth" and you will see option below, also uncheck "Erase downloaded sim" if you're using eSIM, otherwise it will delete it and you will have to do the whole process all over again.
zapmicro said:
Pull up the bold text, the heading "Reset WiFi, mobile and Bluetooth" and you will see option below, also uncheck "Erase downloaded sim" if you're using eSIM, otherwise it will delete it and you will have to do the whole process all over again.
Click to expand...
Click to collapse
Thank you! They really don't want that button to be found!
LordNerevar said:
Thank you! They really don't want that button to be found!
Click to expand...
Click to collapse
haha. sorry for the inconvenience.
DotOS 5.1.2 Update - 19/07/21
Rom side changelog - https://blog.droidontime.com/blog/july-release-2021
Device Side Changlog -
1. FIx Vanilla builds not flashing.
2. July Patch.
3. Enable USB and skin temperature warnings.
4. SimCard app crashing on Vanilla builds.
5. Allow 3rd party apps to use fingerprint gestures.
6. Added Now Playing.
7. Upstream Kernel.
August Update:
Updated to august sources parallel with DotOS Changes
Download link is not working
tjlqk3 said:
Download link is not working
Click to expand...
Click to collapse
Working for me, try in different browser maybe

General Deleted*

Deleted
thanks, i love crdroid
CrDroid is here! @gwolfu I'm coming as usual
Could've used the OSS vendors from Arrow, they're perfect for the deep sleep issues that almost all other ROMs have.
LeDiable said:
Could've used the OSS vendors from Arrow, they're perfect for the deep sleep issues that almost all other ROMs have.
Click to expand...
Click to collapse
You may see next build oss based <3, also there's no deep sleep issue in this rom.
lavishkumar said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.3 or newer for root (after first boot) - (Download from here)
First time installation:
Copy crDroid zip, gapps zip to your device
Boot into Recovery
Format Data
Flash ROM
Flash gapps (Optional)
Flash magisk (optional)
Reboot and Enjoy
Update installation:
Copy crDroid zip to your device
flash it via custom recovery
clean cache (optional)
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url thanks grewal
Github: Lavish
Download:
ROM: https://crdroid.net/sweet
Changelog:
- Android June 2021 Security update
- Based on crDroid 7.7
- Merged latest changes from @grewal
- Updated fingerprint
- Adjusted AOD brightness
- Added burn in protection
- Enabled adaptive sleep
- Some performance tweaks to make UI smoother
Known issues:
- None
- If found any tell me
Support:
Telegram
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Screenshots:-
Click to expand...
Click to collapse
Perro
Hello,
Glad to find crDroid on my Note 10 pro (after having it on my Note5 pro and on my Note 8T, both in my kids' hands now).
Small additional information for beginners:
1) after having formatted the data (and answered "yes"), it is necessary to reboot on the Recovery before installing crDroid
2) If you come from "Arrow" ROM, you can't directly install crDroid. Indeed, Arrow OS changes things in the "vendor" partition, while the installation of cdDroid doesn't seem to affect this partition. I tried to switch directly from Arrow to crDroid, but the phone was rebooting on Recovery. The best is to flash MIUI. Then (no need to start on it) you can flash crDroid.
3) Finally, I have already had several issues after updates crDroid on my other phones (dirty flash), because of the encryption. Now, to protect from problems, I deactivate the encryption (especially with the Note 10 pro, TWRP seems to be still in beta). Usually, to turn off encryption, I would use #dfe. But it doesn't work in this case. So, I recommend that you use "rmcrypt.zip" found in the "Arrow" forum, and which I attach to you in this post.
Important note: If you are using "mcrypt.zip" to turn off encryption, turn off OTA updates. You have to update manually, because you have to relaunch mcrypt after each system update.
Otherwise, the ROM seems to work pretty well. With the exception of the camera: as with other ROMs: selfies are limited to 4 Mpixs (even with GCam).
Enjoy
Manu D.
nice and smooth rom. only problem i got: i can't use the bank app because say the phone is rooted(but i cant find magisk)
:
Thanks for this ROM !
I have the same problem with my bank app, I don't known why, device is not rooted.
yonutz said:
nice and smooth rom. only problem i got: i can't use the bank app because say the phone is rooted(but i cant find magisk)
:
Click to expand...
Click to collapse
2spirit said:
Thanks for this ROM !
I have the same problem with my bank app, I don't known why, device is not rooted.
Click to expand...
Click to collapse
hmm, both of my banking apps working just fine using magisk hide & hide and rename magisk manager app, so not sure why it's not working for you...
check if your device passes safetynet test either with or without magisk, selinux should be enforcing
All in all, love it! Thank you!
Two issues that I found:
Sound is a bit distorted in comparison with Arrow OS or stock.
Brightness lives its own life, needs constant tweaking.
iRet said:
All in all, love it! Thank you!
Two issues that I found:
Sound is a bit distorted in comparison with Arrow OS or stock.
Brightness lives its own life, needs constant tweaking.
Click to expand...
Click to collapse
Good sense of humor! Yes, the brightness issue raises its head in all ROMs like birth pangs in a baby.
I'm waiting with bated breath for the OSS version to come up next month before I migrate from Arrow. Don't want to keep backing.restoring my data every other day.
yonutz said:
nice and smooth rom. only problem i got: i can't use the bank app because say the phone is rooted(but i cant find magisk)
:
Click to expand...
Click to collapse
There's issue with ro.debuggable which will get fixed in my next official build, for now you can flash this magisk module - https://github.com/kdrag0n/safetynet-fix/releases
Decided to give another try. Brightness is not that terrible this time.
Stumbled upon non-working Android Auto.
This is a common LOS problem according to the net and might be caused by gapps.
Hello,
I experimented a big issue.
I was under crDroid 7.7 with rmcrypt.zip to be sure to have no problem with encryption.
I tryed to update manually to version 7.8 (with the same rmcrypt.zip) and the system stayed frozzen at boot on the colored eye (colors loop again and again for hours).
After this bad experience, I tryed again to update without rmcrypt.zip : same result.
But after that, my data was unaccessible. The only solution was to format and came back to v7.7. It was impossible to install v 7.8 :-(
Of course, I need to reinstall and setup all my apps. Was it a problem with gapps and my uncrypted system ?
So, is it possible to have a vanilla version of v7.8 ?
Thanks by advanced,
Manu D.
ManuD_Linux said:
Hello,
I experimented a big issue.
I was under crDroid 7.7 with rmcrypt.zip to be sure to have no problem with encryption.
I tryed to update manually to version 7.8 (with the same rmcrypt.zip) and the system stayed frozzen at boot on the colored eye (colors loop again and again for hours).
After this bad experience, I tryed again to update without rmcrypt.zip : same result.
But after that, my data was unaccessible. The only solution was to format and came back to v7.7. It was impossible to install v 7.8 :-(
Of course, I need to reinstall and setup all my apps. Was it a problem with gapps and my uncrypted system ?
So, is it possible to have a vanilla version of v7.8 ?
Thanks by advanced,
Manu D.
Click to expand...
Click to collapse
latest CrDroid 7.8 is OSS vendor based, while changing vendors MIUI -> OSS clean flash is mandatory, for decryption you should use DFE, check below...
[SCRIPT][FLASHABLE] Encryption disablers for Redmi Note 10 Pro (MIUI vendor, OSS vendor) [SWEET]
So, here is a little script, which I modified to work on Redmi Note 10 Pro (tested and working on sweet). I didn't create this, only modified it, so all credits goes to ghostrider_reborn. Edit: found another working encryption disabler...
forum.xda-developers.com
jeryll said:
latest CrDroid 7.8 is OSS vendor based, while changing vendors MIUI -> OSS clean flash is mandatory, for decryption you should use DFE, check below...
Click to expand...
Click to collapse
Thank you very much, this information is important to know. I will try again with a clean flash.
NB : but even with this solution, is it possible to have a vanilla version without gapps ?
Thanks by advance... Sincerely,
Manu D.
ManuD_Linux said:
Thank you very much, this information is important to know. I will try again with a clean flash.
NB : but even with this solution, is it possible to have a vanilla version without gapps ?
Thanks by advance... Sincerely,
Manu D.
Click to expand...
Click to collapse
CrDroid 7.8 has its own thread here on xda, you should discuss anything related there:
[ROM][Android 11][SWEET/SWEETIN] crDroid v7.13 [OFFICIAL][OSS][25.12.2021]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
around a week ago the dev asked on telegram if we want vanilla version and when people said yes, he said "OMK will post after 2 hours" (whatever that means), but so far nothing like vanilla hadn't been released
THREAD LOCKED
First post deleted.
Regards,
shadowstep
Forum Moderator

Categories

Resources