[ROM][OFFICIAL][hotdogb][10] RESURRECTION REMIX [Sept 9 2020] - OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve

[ROM][OFFICIAL][hotdogb][10] RESURRECTION REMIX [Sept 9 2020] - OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve

[10.0][OFFICIAL]Resurrection Remix v8.x [device_code]
{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters. For 7T: Be sure to be on latest oos, beta or stable is fine (flash both slots prior to installing the rom)
Download the latest Resurrection Remix Rom (currently on V8.6)
(7T builds gave gapps included) so disregard flashing gapps.)
You can use either twrp (mauronfrios latest or Chinese) to flash the rom.
Additionally - you can unpack the bin that is in the zip and fastboot flash as many other roms. SEE POST#4!! Importantly, after flashing, no matter the method, once you see the RR boot logo, force reboot to bootloader mode, and use the buttons to cycle to recovery. Select this as it will now reboot to the roms recovery. Go to wipe data. Wipe data and now reboot. This is mandatory if you flash via twrp or want to run f2fs vs ext4; bc the rom will run very well on f2fs as it is much faster file system than ext4.( Once you format after the first flash.) If using twrp, the first boot sets it as this but unless a format is done, it will not boot. So, do not skip this step. After the data wipe and rebooting, the rom boots up in a few Mins. If it doesn't boot in 5mins. You may have made a mistake and in that case reflash stock to both slots and try again.
Yes, Ota updates work fine, be sure to go to updater and prioritize update process. I usually send a build every couple days.
You can retain root by after the download and install occurs but before reboot, launching magisk manager and installing to opposite slot and then rebooting.
**Ota will not work unless RR is on both slots before taking ota. To fix that, after you get it booted, boot to bootloader and fastboot set_active other, and reflash via fastboot. OR if you used twrp, flash the ota again and it puts it on the opposite slot.
Neutrino Kernel is built in-line, latest Hoth 1.95

Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

Current download and details:https://forum.xda-developers.com/showpost.php?p=83469869&postcount=465
7T TG Chat https://t.me/rr_op7t
Payload Dumper
https://drive.google.com/open?id=1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut

Thanks for this! Glad to see you here as well

Here are some more detailed instructions by my long time constituent @aer0zer0 thank youuuu!!!
how to extract a payload and flash a rom for noobs, windows only
pre-requisites:
1. In general, you want to have the SAME version of OOS on both sides. Im not going to go into detail on how to MSM, and flash a full OTA locally, reboot, then flash the same OTA locally again and reboot.
2. payload dumper for windows: https://drive.google.com/file/d/1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut/view?usp=sharing its windows 64 bit only
3. Latest ADB/Fastboot binaries: when flashing using using a script, and you see errors such as system partition cannot be found, etc... your binaries are old, most likely cause by some ghetto version minimal adb/fastboot thats jank. To verify where your adb/fastboot is running from, in a shell, type fastboot --version this will tell you where you resident adb/fastboot binaries are running from. The link to updates binaries is here https://developer.android.com/studio/releases/platform-tools select the windows SDK version. Once downloaded, copy and paste them over top of the ones being used from the fastboot --version output.
4. a bat file to flash all the images you are dumping. https://drive.google.com/file/d/1HW1Q82wpsnBPUcPkAnXO-tQjVIWSZ_oQ/view?usp=sharing this wipes, goes to fastbootd, will flash all the images from the payload.bin dump to both sides, wipes, and sets it to boot from slot A.
5. lots of common sense
Instuctions
1. extract the payload dumper somewhere on your PC, you will see an "IN" folder, "OUT" folder, and an executable.
2. extract the payload.bin file from the rom.zip you wish to install, and place it in the "IN" folder.
3. run the payload dumper exectuable, a shell will pop up, showing the images being extracted.
4. once the shell closes, the images are all succesfully unpacked. Copy those images in the "OUT" folder to whereevr you would like to store your rom.
5. copy/paste the bat file wherever you placed your images.
6. reboot your phone to fastboot, plug it into the PC, and run the bat.
7. process takes 4-5 minutes, sit back, it will then reboot back to fastboot.
8. start the phone from fastboot, and wait for your new rom to boot.
9. finish and enjoy!

Also, there is no real bugs. On occasion one may think there is a bug, and if there is in fact one, we work promptly to resolve it as a team. Typically, one thinks a bug is a bug, but the rom has so many features, it is just a conflicting setting most likely, I implore you all to exercise trial and error. If something was fine and you fiddled with settings, go unfiddle and see what could make something not work. We could not foolproof all features to not conflict on the occasion if we get kinda crazy with what we expect our device and it's software to be able to do. All works flawlessly. Enjoy the rom and thanks to my colleagues and my friends who have always been there in this wonderful android world, never quick to judge, always quicker to help and teach. Never from the class of elitist android dev who is "too cool" to just be nice. Thanks guys.
The names below have helped me in numerous ways over the years, thanks for the help, support, and overall non-douchebaggery activities:
KangaroosterMeadows-Where the magic happens
@wrongway213
@aer0zer0
@xstefen
@NoSpamDan
@varund7726
@Freak07
@return.of.octobot
@abalam
@hondajohn
@Neo
@unixandria
@fKm
@lil_kujo
@kdp162
@omariscal1019
@DeathStroke
@risasuke
JackEagle-his guides and advice in chat, Anthony P, DPryor, Cody S, and everyone else I haven't named. Thanks also go to AOSiP- for solid trees that most of us all use.

Congrats @FullOfHell what a great rom

Just installed it and I'm liking every bit of it thank you @FullOfHell!

I am touched! I was losing hope for this device. thank you!

Thanks! Will try it soon.
Enviado de meu HD1903 usando o Tapatalk

Face unlock included? How about Fp? Works great, even with low brightness?

Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
yes faceunlock is included and fingerprint works flawlessly, low light, no light, any situation

Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom

lil_kujo said:
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
Click to expand...
Click to collapse
Thanks man appreciate it. Hope you enjoy it

The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?

AnkeshReborn said:
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
Click to expand...
Click to collapse
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy

FullOfHell said:
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
Click to expand...
Click to collapse
Great to know the safety net passes.
Would just leave a message here asking if any forum member based from India installing RR can confirm if the payment apps like PayTM, PhonePe and the likes of it work? It's the just last thing that's stopping me from getting this beauty on 7T.

Along with info of banking apps, i would also like to know if this has auto call recording feature ? 90hz display support ?

Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory

shetty_chadda said:
Along with info of banking apps, i would also like to know if this has auto call recording feature ?
Click to expand...
Click to collapse
No call recording feature as the lineage dialer is overridden for gapps, ie google dialer. Find a 3rd party app/mod. Sorry, I tried adding the option to allow the user to pick los dialer or google dialer, it but broke other things the majority of users need over call recording. Yes, 90hz support. 60/90 or auto

AnkeshReborn said:
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
Click to expand...
Click to collapse
It's easy. Use twrp, or unpack the bin file in the rom and flash with fastboot. same as other roms, just must format after install and reboot.

Related

[ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus]

Copy Partition- Initial Setup
Flash the attachement via TWRP

Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok

Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?

Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.

I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense

david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far

Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.

Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.

If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA

The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.

Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?

Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo

Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?

smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.

Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk

Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?

Anyone running xposed? Any issues?

Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[ROM][10]Android Open Source Illusion Project[Hotdogb][Official]

{
"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:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Download the Fastboot images zip of the variant you want
- There are two variants, "Official" does not contain Gapps while "Gapps" does.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on

XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: [url]https://www.github.com/AOSiP[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.2 or above
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-14
Last Updated 2020-05-06

Reserved
INSTALLATION PROCEDURE:
MAKE SURE YOU'RE ON THE LATEST OOS FROM HERE
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP7T!!!!!
Considering how the 7T doesn't have TWRP and has dynamic partitions, I'll try to explain everything in detail:
1. If you're coming from another ROM (including OOS) or need to perform a clean flash:
Boot into the bootloader (if you don't know how to do this, you should probably not flash)
Connect your phone to your PC and in an ADB/Fastboot shell, wipe device using
Code:
fastboot -w
Connect your phone to your PC and in an ADB/Fastboot shell, type
Code:
fastboot reboot fastboot
NOTE: If command prompt/line complains about fastboot not being a valid target you need to update fastboot from HERE
Your phone should now be in fastbootd (the UI is exactly like recovery mode so don't get confused)
Read about fastbootd HERE
Type the following to make sure your phone is in fastbootd while also making sure your phone is in the recovery-like UI
Code:
fastboot getvar is-userspace
If the above does returns the value true you can now flash the ROMs, if it doesn't try figuring out what went wrong (I don't want to hear about the failed attempts, please don't spam the thread with them)
Type this command to flash the ROM:
Code:
fastboot update <ROM.zip>
NOTE: IF COMMAND LINE IS SAYING:
Code:
archive does not contain 'xyz.sig'
This is normal, ignore it.
After the above is done, your device will automatically reboot to AOSiP, have fun!
OPTIONAL:
If you want magisk, patch the boot image from the AOSiP site which ends in the name -boot.img, in Magisk manager
Boot to bootloader
Boot into that image (DO NOT FLASH!!!)
Code:
fastboot boot magisk_patched.img
Install Magisk manager and from it select Install > Direct install
Reboot and enjoy AOSiP with Magisk!
Enjoy
OPTIONAL:
If you'd like to convert to F2FS:
Open settings>system>reset options and select Erase all data (factory reset)
This'll wipe all data and convert your device to f2fs automatically!
2. If you're updating the ROM:
a. Via the inbuilt Updater
When you get a notification of new build available, tap it
Tap Download
Wait for Download
Tap install
Wait for install
If you use Magisk, open Magisk Manager, select install, select Install to Inactive Slot (After OTA)
Tap reboot
Enjoy!!
b. Manually via bootloader
Disable all substratum overlays if you have a theme applied
Boot into fastbootd
If you're booted into the system
Code:
adb reboot fastboot
If you're booted into bootloader
Code:
fastboot reboot fastboot
Flash the ROM using
Code:
fastboot update <ROM.zip>
NOTE: YOU DO NOT NEED TO WIPE DATA WHEN UPDATING
Reboot to system and enjoy
NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).
KNOWN ISSUES:
Auto brightness is wonky in dark enviroments Fixed in 20200625

Reserved
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your OOS base versions in reports. (Eg: 10.0.1, 10.0.2, 10.0.6 etc.)
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

FREQUENTLY ASKED QUESTIONS:
Q: Fastboot isn't allowing me to flash system image, what am I doing wrong?
A: You haven't booted to fastbootd (the UI looks like recovery and fastboot devices command shows the device in fastboot mode)
Q: What GApps do I flash?
A: You cannot flash Gapps on the device, use the Gapps variant build instead if you need Gapps.
Q: When booting to the Magisk patched image, it leads to crashdump mode.
A: You didn't select the first two options in Magisk Manager before patching the boot image under Advanced settings (i.e. Preserve force encryption and Preserve AVB 2.0/dm-verity).
Q: Do I have to wipe data if coming from another ROM?
A: Yes, I will not be providing help/support to users that haven't wiped data when coming from another ROM.
Q: How often will I be getting updates?
A: The plan is for weeklies, if unavoidable circumstances come up, please don't spam the thread. I will release a build as soon as one is ready.
Q: Does VoLTE/VoWiFi work?
A: VoLTE works, I have tested on Airtel in India and a couple of my US based testers have too.
VoWiFi (WiFi Calling) works based on my testers in the US and for me on Airtel (India), let me know about other carriers.
Q: Does Android Auto work?
A: I don't have accessibility to an Android Auto vehicle nor the hardware but my testers have confirmed that it works! Let me know if it does for you too so that others have concrete proof about it.
Q: I ended up on CrashDump mode, how do I get back to my system?
A: Theres a valuable thread HERE which can help restoring your system, you WILL LOSE ALL DATA and I will not be blamed under any circumstances.
Q: Is the ROM official?
A: The ROM is Official.
Q: I use Telegram, where can I find help on that platform?
A: There is a common AOSiP Group Chat for all devices, the link is HERE
Q: Does SafteyNet pass and is the SELinux Enforcing?
A: Yes, SafteyNet does pass out-of-the-box and SELinux is Enforcing.
Q: What OOS Base firmware do I use?
A: OOS 10.0.6 is the recommended base firmware right now.
Q: I'm having high idle drain, please fix.
A: I'll need more data from you to figure it out, Install BetterBatteryStats and let me know about what it tells you after 3-4 charge cycles. Please do not report issues when having apps like Greenify, Naptime, Wakelock blocker etc.
Q: My phone is stuck on the "Bootloader is unlocked" warning page, why isn't my system booting?
A: Since there are a bunch of scripts being executed when the device is sent a power on signal, it might take some time to boot. Don't panic, your system will boot fine after some time. All builds are personally tested by me and a few testers.

Reserved

Littyyyyy???

Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.

Thank you for the perfect Rom.

This has all the customizable features like android 9

so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again

anirudhgupta109 said:
Reserved
Click to expand...
Click to collapse
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.

This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!

I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.

So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.

aer0zer0 said:
Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.
Click to expand...
Click to collapse
Thanks a lot for testing that annoying carrier ???
umair shaikh said:
so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again
Click to expand...
Click to collapse
Yes, clean flashing includes internal storage.
The only time you need to clean flash is when coming from another ROM.
When updating AOSiP you don't need to so it's basically a one time process.
david72262 said:
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.
Click to expand...
Click to collapse
yqx1110 said:
This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!
Click to expand...
Click to collapse
Thanks for the kind words the two of you, it took awhile to type it out for everyone, glad it's appreciated ??
elanandkumar said:
I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.
Click to expand...
Click to collapse
We are an open source project so including any form of closed source apps we can do away with irks me. The idea of having GApps inside the ROM itself feels wrong but it's a necessity.
Anyway, the latest Urnyx GCam works perfectly with AOSiP without any magisk modules nor setting permissive selinux. It's literally install and use so you can do so if you need to.
The OnePlus Camera also works, just that it needs to be launched from the long press menu on your launcher.
Mohammed779 said:
So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.
Click to expand...
Click to collapse
That's an interesting observation, I'll look into the red center.
No, there is nothing to refresh on AOD so it doesn't run on 90Hz.
You can also choose the type of 90Hz you want to run with in OnePlus Settings (forced or auto)

Hey the google bar seems to be permanently affixed to the home screen, I cant drag it away like a normal widget, is there anything I can do about that short of installing a launcher?

10.0.7
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks

mikefnz said:
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks
Click to expand...
Click to collapse
I'm running this ROM on 10.0.7. everything is fine.

help !!!
anirudhgupta109 said:
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Since the ROM is big in size due to gapps, try downloading from SourceForge to make sure you get the complete file and also compare md5sum.
- GApps is already pre-included in the ROM.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on

XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: https://www.github.com/AOSiP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.6
Based On: AOSP
Version Information
Status: Alpha
Created 2019-12-14
Last Updated 2019-12-14
Click to expand...
Click to collapse
writing 'system' ...
FAILED (partition not found)

hru200 said:
writing 'system' ...
FAILED (partition not found)
Click to expand...
Click to collapse
Follow the instructions maybe?
Type "fastboot reboot fastboot" then do the images flashing commands.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
Anyone having weaker WiFi signal compared to OOS? On a 5GHz WiFi that is. Same testing position, yet much weaker. Additionally, frequent disconnections.

Development [ROM] [12.1] [OFFICIAL] Android Ice Cold Project

{
"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 then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS 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
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
NikGapps Core is recommended
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
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 on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions 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 file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on A/B Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
Open the updater app, download the update, then press install, press reboot when prompted, you will be taken to TWRP, there isn't any need to flash GApps separately
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_xiaomi_vayu
Contribute to AICP/kernel_xiaomi_vayu development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_xiaomi_vayu
Contribute to AICP/device_xiaomi_vayu development by creating an account on GitHub.
github.com
Vendor source:
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
@kubersharma001
@nullxception
@SebaUbuntu
Information:
ROM OS Version: 12.1
Kernel: Linux 4.14
ROM {Firmware|Vendor} required: 13.0.2
Status: STABLE
You want to see a "normal" night at the "DEV office", click here!!

Wow. Thank you @Nebrassy . I am a long time lover of AICP and it is wonderful to see it for this device. Your hard work is much appreciated and I am happy to donate to the cause: Transaction ID 3HG14334YS520444K.

Thank you dev for your work!!
Can you please tell me: the "Xiaomi parts" shown in the screenshots provided in the Telegram channel, where can I find them?
Or is this something that will be implemented later on?
Thanks!!

juv3nal said:
Thank you dev for your work!!
Can you please tell me: the "Xiaomi parts" shown in the screenshots provided in the Telegram channel, where can I find them?
Or is this something that will be implemented later on?
Thanks!!
Click to expand...
Click to collapse
We don't currently have that, and I didn't provide any screenshots

Thanks, this one is an old favorite of mine

Thank you .

Any solution to root and keep using my banks apps and some games like pokemon go?
Thanks for this ROM .. extremely fast and solid ROM.. just one little thing that I found is that notification sounds not always works it only vibrates

julioolares said:
Any solution to root and keep using my banks apps and some games like pokemon go?
Thanks for this ROM .. extremely fast and solid ROM.. just one little thing that I found is that notification sounds not always works it only vibrates
Click to expand...
Click to collapse
SafetyNet passes by default with or without magisk, not sure how you're having problems with that

Nebrassy said:
SafetyNet passes by default with or without magisk, not sure how you're having problems with that
Click to expand...
Click to collapse
How to safetynet pass? I've just rooted my device but seems like safetynet it's missed
EDIT: FIXED.

Does anyone else have issues with receiving timely notifications and not being able to receive text messages?

AusVGM said:
Does anyone else have issues with receiving timely notifications and not being able to receive text messages?
Click to expand...
Click to collapse
Nope, everything here is working good at my side, these bugs sometimes the gapps package might be its cause, try a different gapps package, this would solve your latency.

AbboodSY said:
Nope, everything here is working good at my side, these bugs sometimes the gapps package might be its cause, try a different gapps package, this would solve your latency.
Click to expand...
Click to collapse
Swapped from MindTheGapps to NikGapps and the problem has been solved. Thank you very much.

I switched from Pixel Plus UI to AICP and I must say that AICP is just as fast and smooth which is impressive considering how much tweaks and customization features are baked into the ROM.
There is only one small issue. I have observed some gallery lag in this ROM that didn't exist in MIUI or other ROMS. Namely, when I open any gallery app, it takes a few seconds to actually load the images. Has anyone else noticed this or is it an isolated event?
For consideration I am using the recommended mind the Gapps.

yonoshiro said:
I switched from Pixel Plus UI to AICP and I must say that AICP is just as fast and smooth which is impressive considering how much tweaks and customization features are baked into the ROM.
There is only one small issue. I have observed some gallery lag in this ROM that didn't exist in MIUI or other ROMS. Namely, when I open any gallery app, it takes a few seconds to actually load the images. Has anyone else noticed this or is it an isolated event?
For consideration I am using the recommended mind the Gapps.
Click to expand...
Click to collapse
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.

AbboodSY said:
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.
Click to expand...
Click to collapse
Coincidentally, I am also using simple gallery pro. I will try switching Gapps and I will report back. Thank you for taking the time to assist me.

AbboodSY said:
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.
Click to expand...
Click to collapse
Okay. Very odd. I still had the issue with NikGapps. Then I saw AICP had an update (Thank you Dev) which I did OTA. The issue persisted. I then decided to go for broke and just do a complete wipe and clean install of the latest AICP Rom and Mindthegapps and the issue is resolved. Could have just been an issue with my initial installation.

Loving the latest update @Nebrassy . This ROM is rocking my world! I have made another small donation towards your good work. Thank you for your efforts. They are much appreciated.
Transaction ID: 6RV661328U952290X

FlameGapps is now the recommended package for vayu

Hi, recording on the stock camera show garbage, and tried installing a gcam and still same. It like dthis.
I tried fresh clean install of rom and flashed flameGapps
clean cache/data same.

pinbanman said:
Hi, recording on the stock camera show garbage, and tried installing a gcam and still same. It like dthis.
I tried fresh clean install of rom and flashed flameGapps
clean cache/data same.
View attachment 5413861
Click to expand...
Click to collapse
Use latest build, 17th of September

[Discontinued][ARM64][ROM][11.0][OFFICAL] AICP 16.1 [Addison]

{
"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 then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS 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
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Camera mods are not and will not be supported
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
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 on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions 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 file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device, enable developer settings and in them, OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_motorola_msm8953 at r11.1-albus
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
Device tree source:
https://github.com/AICP/device_motorola_addison/tree/r11.1Vendor source:
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
erfanoabdi, npjohnson, jeferson1979, jarlpenguin,alberto97
Information:
ROM OS Version: 11.x
Kernel: Linux 3.18.140
ROM Firmware required: ADDISON_OPNS27.76
Status: STABLE
Release Date: 19-12-2021
You want to see a "normal" night at the "DEV office", click here!!

19-12-2021: Initial release

solved, ask me for unlock code...
i forget format data....
Thx
Running on android 11 Now!!!
Thx!!!!!!

Thanks for the oficial release. Working fastest.
Running in XT 1635-02 with Nano Gapps
Greeting from Brazil

Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.

Good customizations and performance. Free ram at 800-1300mb. Screens of the ROM:

BloodyPorra said:
Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.
Click to expand...
Click to collapse
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help

marcost22 said:
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help
Click to expand...
Click to collapse
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:

BloodyPorra said:
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:
Click to expand...
Click to collapse
I can see some things that might cause that audio issue; altho it's weird that i cant notice it; it might just be the opalum speaker protection being all wonky.
You are gonna have to get me a console-ramoops from after the reboot, just pull /sys/fs/pstore, because those have no info for me
I even have a XT1635-02 myself as my test device, the only thing different is that i have an ever so slightly newer firmware version; M8953_10238.63.04.83R vs M8953_10238.63.04.83.01R on mine

Sound is low and fixed and back again very loud with noise, distortion and popping. After notification in whatsapp. Ok i want to check this.
(Edit):
console-ramoops isn't available after kernel panic

Here for you

BloodyPorra said:
Here for you
Click to expand...
Click to collapse
nothing, you might have to take the logcat with a pc and then trigger the flashlight to see if the issue pops up

marcost22 said:
nothing, you might have to take the logcat with a pc and then trigger the flashlight to see if the issue pops up
Click to expand...
Click to collapse
CPU Shutdown if i shake my device for flashlight or not. How to take a logcat with my notebook?

I take the logcat in ADB after shake several times my device is shutdown again, but only the last line appears:
Code:
12-21 10:21:44.628 0 0 I : [ 1520.174098,4] motosh 4-0043: Sending disp_rotate(x)value: 0

you start adb logcat -b all > log.log and then after a couple of seconds you shake the device

marcost22 said:
you start adb logcat -b all > log.log and then after a couple of seconds you shake the device
Click to expand...
Click to collapse
after several times shutdown

Thanks for your hard work dude

BloodyPorra said:
after several times shutdown
Click to expand...
Click to collapse
can't see anything wrong at first glance; will take a better look tomorrow

rogerpinkos said:
Thanks for your hard work dude
Click to expand...
Click to collapse
in my device i tested games like a Mobile Legends and COD i have a fastest perfomance, system is fluid and lag free. big different when i using arm or arm64 pie roms

marcost22 said:
can't see anything wrong at first glance; will take a better look tomorrow
Click to expand...
Click to collapse
i was to test dolby atmos or viper for sound fix and change CPU governor and I/O for tests.

Database Info

welcome