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

Search This thread

marcost22

Senior Member
Jun 26, 2019
266
68
Moto Z Play
Moto Z2 Play
hi @marcost22 i really appreciate your work, however its pretty annoying while watching videos or on calls, the volume get reduced and there is no way to turn it up.
And positive part is camera, gcam is doing to good with cam, if the volumes issue can be fixed, i just wonder!!
There is no fix, i've talked with a bunch of more qualified people and the issue so far is unfixable;

It's getting really annoying having to repeat myself every few posts so i would really appreciate if y'all would at least take a cursory glance through the post before asking the same thing for the 100th time
 

Touch2Fin

Member
Oct 3, 2015
7
0
OnePlus 8T
Hi there, I tried to plug in a type-C headphone today, but the system could not read those devices and the sounds are still playing via the speakers, feels a little bit annoying.
 

marcost22

Senior Member
Jun 26, 2019
266
68
Moto Z Play
Moto Z2 Play
Hi there, I tried to plug in a type-C headphone today, but the system could not read those devices and the sounds are still playing via the speakers, feels a little bit annoying.
Are they passive or active type-C? As in, are they just a plain cable that ends in a connector or is it an adapter with some headphones on the end?

I'm saying this because addison only supports type-c headphones that have a DAC in them, or as they are called, "Active" type-c headphones
 

felipe74859

New member
Jun 11, 2022
1
0
hi! is there a way to fix it? just happened after recent update.
 

Attachments

  • Screenshot_20220611-164501.png
    Screenshot_20220611-164501.png
    149.1 KB · Views: 27

kentceo

Member
Feb 26, 2018
8
0
You gotta get me a logcat of this; i've got the exact same configs as alberto has for retcn

Also why are you using such an old twrp? this won't cause any issues im just curious
Sorry, I didn't know, on other versions of twrp there is no necessary vendor path for custom firmware. I found a solution to what needs to be done for nfc to work 100% on the retcn. need to rename the file from libnfc-nxp_retcn.conf and replace to libnfc-nxp.conf in the /vendor/etc folder. It seems to me that this is due to the fact that the gpt.bin and bootloader files are from the firmware of the retail oreo. I can reflash retail oreo to Chinese firmware only without gpt and bootloader, because it's a downgrade gpt and bootloasder, can't lower the bootloader and gpt. All the time, retail firmware was installed on this phone via RSD, with a full installation of bootloader and gpt. in the installer aicp i see words OPNS27.76-12-22-9 but i have retcn OCN27.82-24 (only bootloader and gpt from OPNS27.76-12-22-9).
Now nfc and other works perfect on 1635-03 retcn
Thank you!
 

Attachments

  • IMG_20220609_103739540.jpg
    IMG_20220609_103739540.jpg
    3.6 MB · Views: 14

marcost22

Senior Member
Jun 26, 2019
266
68
Moto Z Play
Moto Z2 Play
Sorry, I didn't know, on other versions of twrp there is no necessary vendor path for custom firmware. I found a solution to what needs to be done for nfc to work 100% on the retcn. need to rename the file from libnfc-nxp_retcn.conf and replace to libnfc-nxp.conf in the /vendor/etc folder. It seems to me that this is due to the fact that the gpt.bin and bootloader files are from the firmware of the retail oreo. I can reflash retail oreo to Chinese firmware only without gpt and bootloader, because it's a downgrade gpt and bootloasder, can't lower the bootloader and gpt. All the time, retail firmware was installed on this phone via RSD, with a full installation of bootloader and gpt. in the installer aicp i see words OPNS27.76-12-22-9 but i have retcn OCN27.82-24 (only bootloader and gpt from OPNS27.76-12-22-9).
Now nfc and other works perfect on 1635-03 retcn
Thank you!
That thing you did should have happened automatically when it detected your device was retcn; can you getprop ro.boot.hardware.sku?
 

Unreal_man

Member
Aug 15, 2016
47
4
I change theme to dark but quick settings still light. Somebody have a recepie for this trouble?
One more thing. Can I switch off display by fingerpring sensor? How to set this?
 
Last edited:

marcost22

Senior Member
Jun 26, 2019
266
68
Moto Z Play
Moto Z2 Play
I change theme to dark but quick settings still light. Somebody have a recepie for this trouble?
One more thing. Can I switch off display by fingerpring sensor? How to set this?
That's odd given the fact that QS follows the theme of the rest of the device. How did you enable dark mode?
It should be enabled by default, just by holding your finger on the fp sensor IIRC
which version of magisk you're using?
Always latest
 

kentceo

Member
Feb 26, 2018
8
0
That thing you did should have happened automatically when it detected your device was retcn; can you getprop ro.boot.hardware.sku?
Please forgive me. It's too late to answer my bad habit. Here is the getprop code. hoping this can help the future. The main problem is that the bootloaders from the retail version. I can't make a loader from the cn version. the retail loader has the highest version. in the retail version (full flash latest rom) there is a problem with the nfc for the Chinese device. I think I'm not the only one who cn 1635-03 has a loader from the retail version. But the hardware region is different bootloader, bcs latest highest bootloadeer is retail and cant change it.

[ro.actionable_compatible_property.enabled]: [false]
[ro.aicp.branch]: [r]
[ro.aicp.buildtype]: [WEEKLY]
[ro.aicp.device]: [addison]
[ro.aicp.display.version]: [aicp_addison_r-16.1-WEEKLY-20220702]
[ro.aicp.maintainer]: [marcost2]
[ro.aicp.version]: [16.1-WEEKLY]
[ro.aicp.version.update]: [r-16.1]
[ro.allow.mock.location]: [0]
[ro.baseband]: [msm]
[ro.board.platform]: [msm8953]
[ro.boot.baseband]: [msm]
[ro.boot.bootdevice]: [7824900.sdhci]
[ro.boot.bootloader]: [0xC182]
[ro.boot.bootreason]: [reboot]
[ro.boot.build_vars]: [black]
[ro.boot.emmc]: [true]
[ro.boot.flash.locked]: [1]
[ro.boot.hardware]: [qcom]
[ro.boot.hardware.sku]: [XT1635-03]
[ro.boot.mode]: [normal]
[ro.boot.poweroff_alarm]: [0]
[ro.boot.serialno]: [ZY223MPFNJ]
[ro.boot.uid]: [4EC7C6F000000000000000000000]
[ro.boot.vbmeta.device_state]: [locked]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.veritymode]: [enforcing]
[ro.boot.wifimacaddr]: [CC:61:E5:C7:62:DA,CC:61:E5:C7:62:DB]
[ro.boot.write_protect]: [0]
[ro.bootimage.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.bootimage.build.date.utc]: [1656778330]
[ro.bootimage.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.
76-12-22-9/10:user/release-keys]
[ro.bootloader]: [0xC182]
[ro.bootmode]: [normal]
[ro.build.characteristics]: [default]
[ro.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.build.date.utc]: [1656778330]
[ro.build.description]: [addison_retail-user 8.0.0 OPNS27.76-12-22-9 10 release-
keys]
[ro.build.display.id]: [aicp_addison-userdebug 11 RQ3A.211001.001 5013 test-keys
]
[ro.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.76-12-22-9
/10:user/release-keys]
[ro.build.flavor]: [aicp_addison-user]
[ro.build.host]: [box2]
[ro.build.id]: [RQ3A.211001.001]
[ro.build.product]: [addison]
[ro.build.selinux]: [1]
[ro.build.stock_fingerprint]: [google/walleye/walleye:8.1.0/OPM1.171019.011/4448
085:user/release-keys]
[ro.build.tags]: [release-keys]
[ro.build.type]: [userdebug]
[ro.build.user]: [jenkins]
[ro.build.vendorprefix]: [/vendor]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [5013]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2022-06-05]
[ro.carrier]: [retcn]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.android.wifi-watchlist]: [GoogleGuest]
[ro.com.google.clientidbase]: [android-motorola]
[ro.config.alarm_alert]: [Sunshower.ogg]
[ro.config.notification_sound]: [Duet.ogg]
[ro.config.ringtone]: [The_big_adventure.ogg]
[ro.crypto.state]: [unencrypted]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [1]
[ro.hardware]: [qcom]
[ro.hwui.use_vulkan]: []
[ro.iorapd.enable]: [false]
[ro.lineage.build.version]: [16.1]
[ro.lineage.version]: [-20220702_181320-]
[ro.logd.size.stats]: [64K]
[ro.modversion]: [aicp_addison_r-16.1-WEEKLY-20220702]
[ro.odm.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.odm.build.date.utc]: [1656778330]
[ro.odm.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.76-12-
22-9/10:user/release-keys]
[ro.odm.build.id]: [RQ3A.211001.001]
[ro.odm.build.tags]: [test-keys]
[ro.odm.build.type]: [userdebug]
[ro.odm.build.version.incremental]: [5013]
[ro.odm.build.version.release]: [11]
[ro.odm.build.version.release_or_codename]: [11]
[ro.odm.build.version.sdk]: [30]
[ro.odm.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist64]: [arm64-v8a]
[ro.opengles.version]: [196610]
[ro.organization_owned]: [false]
[ro.postinstall.fstab.prefix]: [/system]
[ro.product.board]: [MSM8953]
[ro.product.brand]: [Motorola]
[ro.product.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.product.build.date.utc]: [1656778330]
[ro.product.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.76
-12-22-9/10:user/release-keys]
[ro.product.build.id]: [RQ3A.211001.001]
[ro.product.build.tags]: [test-keys]
[ro.product.build.type]: [userdebug]
[ro.product.build.version.incremental]: [5013]
[ro.product.build.version.release]: [11]
[ro.product.build.version.release_or_codename]: [11]
[ro.product.build.version.sdk]: [30]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [addison]
[ro.product.first_api_level]: [23]
[ro.product.locale]: [en-US]
[ro.product.manufacturer]: [Motorola]
[ro.product.model]: [Moto Z Play]
[ro.product.name]: [Moto Z Play]
[ro.product.odm.brand]: [Motorola]
[ro.product.odm.device]: [addison]
[ro.product.odm.manufacturer]: [Motorola]
[ro.product.odm.model]: [Moto Z Play]
[ro.product.odm.name]: [Moto Z Play]
[ro.product.product.brand]: [Motorola]
[ro.product.product.device]: [addison]
[ro.product.product.manufacturer]: [Motorola]
[ro.product.product.model]: [Moto Z Play]
[ro.product.product.name]: [Moto Z Play]
[ro.product.system.brand]: [Motorola]
[ro.product.system.device]: [addison]
[ro.product.system.manufacturer]: [Motorola]
[ro.product.system.model]: [Moto Z Play]
[ro.product.system.name]: [Moto Z Play]
[ro.product.system_ext.brand]: [Motorola]
[ro.product.system_ext.device]: [addison]
[ro.product.system_ext.manufacturer]: [Motorola]
[ro.product.system_ext.model]: [Moto Z Play]
[ro.product.system_ext.name]: [Moto Z Play]
[ro.product.vendor.brand]: [Motorola]
[ro.product.vendor.device]: [addison]
[ro.product.vendor.manufacturer]: [Motorola]
[ro.product.vendor.model]: [Moto Z Play]
[ro.product.vendor.name]: [Moto Z Play]
[ro.property_service.version]: [2]
[ro.qualcomm.bt.hci_transport]: [smd]
[ro.qualcomm.cabl]: [0]
[ro.revision]: [0]
[ro.romstats.askfirst]: [1]
[ro.romstats.buildtype]: [WEEKLY]
[ro.romstats.name]: [AICP]
[ro.romstats.tframe]: [1]
[ro.romstats.url]: [https://stats.aicp-rom.com/]
[ro.romstats.version]: [16.1]
[ro.secure]: [1]
[ro.serialno]: [ZY223MPFNJ]
[ro.services.whitelist.packagelist]: [com.google.android.gms]
[ro.setupwizard.enterprise_mode]: [1]
[ro.sf.hwc_set_default_colormode]: [true]
[ro.sf.lcd_density]: [420]
[ro.storage_manager.enabled]: [true]
[ro.surface_flinger.force_hwc_copy_for_virtual_displays]: [true]
[ro.surface_flinger.has_wide_color_display]: [true]
[ro.surface_flinger.max_virtual_display_dimension]: [4096]
[ro.surface_flinger.protected_contents]: [true]
[ro.surface_flinger.use_color_management]: [true]
[ro.surface_flinger.vsync_event_phase_offset_ns]: [2000000]
[ro.surface_flinger.vsync_sf_event_phase_offset_ns]: [6000000]
[ro.system.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.system.build.date.utc]: [1656778330]
[ro.system.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.76-
12-22-9/10:user/release-keys]
[ro.system.build.id]: [RQ3A.211001.001]
[ro.system.build.tags]: [test-keys]
[ro.system.build.type]: [userdebug]
[ro.system.build.version.incremental]: [5013]
[ro.system.build.version.release]: [11]
[ro.system.build.version.release_or_codename]: [11]
[ro.system.build.version.sdk]: [30]
[ro.system_ext.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.system_ext.build.date.utc]: [1656778330]
[ro.system_ext.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27
.76-12-22-9/10:user/release-keys]
[ro.system_ext.build.id]: [RQ3A.211001.001]
[ro.system_ext.build.tags]: [test-keys]
[ro.system_ext.build.type]: [userdebug]
[ro.system_ext.build.version.incremental]: [5013]
[ro.system_ext.build.version.release]: [11]
[ro.system_ext.build.version.release_or_codename]: [11]
[ro.system_ext.build.version.sdk]: [30]
[ro.telephony.call_ring.multiple]: [false]
[ro.telephony.default_network]: [10,0]
[ro.telephony.iwlan_operation_mode]: [legacy]
[ro.treble.enabled]: [true]
[ro.url.legal]: [http://www.google.com/intl/%s/mobile/android/basic/phone-legal.
html]
[ro.url.legal.android_privacy]: [http://www.google.com/intl/%s/mobile/android/ba
sic/privacy.html]
[ro.usb.bpt]: [2ee5]
[ro.usb.bpt_adb]: [2ee6]
[ro.usb.bpteth]: [2ee7]
[ro.usb.bpteth_adb]: [2ee8]
[ro.usb.mtp]: [2e82]
[ro.usb.mtp_adb]: [2e76]
[ro.usb.ptp]: [2e83]
[ro.usb.ptp_adb]: [2e84]
[ro.vendor.build.date]: [Sat Jul 2 18:12:10 CEST 2022]
[ro.vendor.build.date.utc]: [1656778330]
[ro.vendor.build.fingerprint]: [motorola/addison_retail/addison:8.0.0/OPNS27.76-
12-22-9/10:user/release-keys]
[ro.vendor.build.id]: [RQ3A.211001.001]
[ro.vendor.build.security_patch]: [2020-10-17]
[ro.vendor.build.tags]: [test-keys]
[ro.vendor.build.type]: [userdebug]
[ro.vendor.build.version.incremental]: [5013]
[ro.vendor.build.version.release]: [11]
[ro.vendor.build.version.release_or_codename]: [11]
[ro.vendor.build.version.sdk]: [30]
[ro.vendor.extension_library]: [libqti-perfd-client.so]
[ro.vendor.hw.fps]: [true]
[ro.vendor.hw.imager]: [16MP]
[ro.vendor.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]
[ro.vendor.qti.core_ctl_max_cpu]: [4]
[ro.vendor.qti.core_ctl_min_cpu]: [2]
[ro.vndk.version]: [30]
[ro.wifi.channels]: []
[ro.zygote]: [zygote64_32]
[security.perf_harden]: [1]
[selinux.restorecon_recursive]: [/data/misc_ce/0]
[service.bootanim.exit]: [1]
[service.sf.present_timestamp]: [1]
[sys.boot.reason]: [bootloader]
[sys.boot.reason.last]: [shutdown,userrequested]
[sys.boot_completed]: [1]
[sys.bootstat.first_boot_completed]: [1]
[sys.isolated_storage_snapshot]: [true]
[sys.mod.platformsdkversion]: [281]
[sys.rescue_boot_count]: [1]
[sys.retaildemo.enabled]: [0]
[sys.sysctl.extra_free_kbytes]: [24300]
[sys.system_server.start_count]: [1]
[sys.system_server.start_elapsed]: [26269]
[sys.system_server.start_uptime]: [26269]
[sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [0]
[sys.usb.controller]: [7000000.dwc3]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb]
[sys.use_memfd]: [false]
[sys.user.0.ce_available]: [true]
[sys.wifitracing.started]: [1]
[telephony.lteOnCdmaDevice]: [1]
[tombstoned.max_tombstone_count]: [50]
[vendor.audio_hal.period_size]: [240]
[vendor.boot_completed]: [1]
[vendor.gralloc.disable_ubwc]: [0]
[vendor.gralloc.enable_fb_ubwc]: [1]
[vendor.vidc.enc.dcvs.extra-buff-count]: [2]
[vold.has_adoptable]: [1]
[vold.has_quota]: [1]
[vold.has_reserved]: [1]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]

C:\Users\ubuntuw\Downloads\Addison_TWRP>pause
Для продолжения нажмите любую клавишу . . .
 
Last edited:

g.a.mo.z

Member
May 9, 2017
12
1
Just replaced my phone's battery. Almost 3 years without it. Currently it's on Android 9 XPerience ROM. TWRP version is 3.3.1-0.
I want to update to AICP.

What are steps to do this?

1) Update TWRP? What version and from where?
2) format data, delete all? I don't care about the data that's on it.
3) i remember something about IMEI backup when switching ROMs. And also something about baseband version?
4) do I need to flash magisk after? I don't think I need root for now.
 

marcost22

Senior Member
Jun 26, 2019
266
68
Moto Z Play
Moto Z2 Play
Just replaced my phone's battery. Almost 3 years without it. Currently it's on Android 9 XPerience ROM. TWRP version is 3.3.1-0.
I want to update to AICP.

What are steps to do this?

1) Update TWRP? What version and from where?
2) format data, delete all? I don't care about the data that's on it.
3) i remember something about IMEI backup when switching ROMs. And also something about baseband version?
4) do I need to flash magisk after? I don't think I need root for now.
1) Yes, please do specially if you plan on encrypting; use the official twrp from twrp.me
2) Also yes, specially when switching between different roms data has got to go
3) You just need to be on the latest Oreo firmware which is OPNS27.76-12-22-9 , and always backup your persist/efs either with twrp backup and moving it somewhere where it's safe or using DD
4) If you dont want root, then no
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6


    logo_black.png


    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.
    *
    */

    features.png

    Feature list (rough overview)


    credits.png


    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

    team.png


    @LorD ClockaN
    @eyosen
    @semdoc
    @SpiritCroc
    @wartomato
    @Miccia
    plus the rest of the crazy bunch that we call "team"



    donations.png


    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!!



    downloads.png


    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/.



    changelog.png


    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)

    issues.png


    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.


    instructions.png


    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.

    sources.png


    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:
    Device tree source:
    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:

    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!!​
    2
    First of all thank you for this ROM. I installed it today on my Moto Z play. Everything working fine except
    1. Google Cam keeps on crashing.
    2. No 4K video option
    3. As video play progresses, main speaker volume automatically begins to fade and remains somewhere at half even though I push the buttons to make it at maximum level it does not increase.

    Motorola never used the front LED as an indicator. Thanks it lits up while charging and on notifications.
    Awesome.
    1. GCam is not officially supported, you are going to have to ask around and find which one works fine with this device
    2. SnapCam doesn't support 4k; using something like OpenCamera 4k recording works just fine
    3. This seems to be an evolution of the same issue some other people have found that i just can't track down; have you had your screen/battery replaced by any chance?

    Yep, which is why i thought it was pretty dumb and just marked it as a white indicator LED
    2
    that means my phone has a 3rd party touch screen, I didn't know such thing could be possible, so that means my mobile will be stuck with custom 7.1 forever?
    If you get me a logcat i might be able to patch the kernel to kinda support 3rd party screens; it really just sounds like the knockoff touch chip needs some extra time to wake up or needs to be waken multiple times
    1
    19-12-2021: Initial release
    1
    hi! is there a way to fix it? just happened after recent update.
    This is not a bug, you just changed the default clock. You hold tap on the clock until it starts shaking and then you just swipe right or left to change it