As of today my addison is dead. Unfortunately this means no more development for this device will happen.
I'm sorry
I'm sorry
Sorry for the long silence. I was returning the phone back to the Chinese version of android 8.0 XT1635-03_ADDISON_RETCN_8.0.0_OCN27.82-24_cid11 (latest cn firmware, with latest retail firmware have radio module lost). Now I have installed the latest aicp_addison_r-16.1-WEEKLY-20220430 and open_gapps-arm64-11.0-pico-20220503. The problem is the same, the nfc switches constantly. On lineage 15, AOSP-9-alberto97 no problems with nfc (i think bcs os`s 32bit). Here is the logcat attached. Thank you
logcat
Last edited:
Yes, of course this is the XT1635-03 model, I bought it in China 2016 new retail in packaging. This is definitely not a restored model. Unlocked bootloader on official site motorola. Normally, only the Chinese original firmware (nfc, radio) and lineage 32 bit firmware work fine on this model
That makes sense, because i've recently been informed that the Chinese variants have different firmware stuffYes, of course this is the XT1635-03 model, I bought it in China 2016 new retail in packaging. This is definitely not a restored model. Unlocked bootloader on official site motorola. Normally, only the Chinese original firmware (nfc, radio) and lineage 32 bit firmware work fine on this model
Thank you for your support! But I'm more confused. The phone on the Addison platform is a retail version and an unlocked bootloader officially. The whole problem is in the radio and nfc and it is not clear why on some custom firmware it always works like a lineage. On the retail firmware XT1635-02_ADDISON_RETAIL_8.0.0_OPNS27.76-12-22-9_cid50 1635-02 the problem is only with nfc and have patch for nfc 1635-03 (just config from cn andriod 7.1 nfc). Is it correct to assume that there is no support for adisson 1635-03 china, bcs nfc trouble?
This phone was amazing. Have it still as backup, but battery is over. And it's hard to get a new one. Good that we get a current android version for this phone with this rom. Maybe I will install it anytime, if I get a new battery anytime
It works in lineage because this config i was missing, and you can't simply use the 7.1 config because in android 8 there was a config standard change so it wouldn't work. It's not so much the FIRMWARE but the actual chip, which while actually the same it's a different variant
EDIT: latest weekly should work for you just fine, but please do test it and come back and tell me how and if it works
Thank you! I will definitely put and write an answer here. While I tried to put the latest aicp on android 7.1 (retail, cn), the result is the same This firmware AICP is very good, the screen time for about 6 hours on a new battery (gapps nano), in addition to the battery mod and the projector mod works, the hasselblad mod will also activate, but need up the moto camera apk with support mod.
This firmware AICP is very good, the screen time for about 6 hours on a new battery (gapps nano), in addition to the battery mod and the projector mod works, the hasselblad mod will also activate, but need up the moto camera apk with support mod.Why are you on 7.1? That will cause issues anyways. You said before that you were running 8.0 retcn, use thatThank you! I will definitely put and write an answer here. While I tried to put the latest aicp on android 7.1 (retail, cn), the result is the same
This rom is amazing @marcos22! Thank you so much, everything working.
The only issue I have is the volume fading out for example when starting playing a video. as others mention. If i power off the screen and then back on, the volume is restored.
I understand there is nothing that can be tweaked for trying to fix this, right?
The only issue I have is the volume fading out for example when starting playing a video. as others mention. If i power off the screen and then back on, the volume is restored.
I understand there is nothing that can be tweaked for trying to fix this, right?
Thanks for providing this superb ROM for the MZP. Which is a great device in terms of battery life, cheap performance and usability (hack to enable torch for example). I think we can be pretty happy that this old device is still running a stable and pretty fast Android OS these times. Even if not everything is perfect, it’s still ways better than the other, more outdated ROMs. For quite a while it seemed that there will be no newer ROM available, until AICP surfaced for the Allison. So thanks for porting it over!
Maybe @allrightlite can donate his MZP? Without a working battery it is kinda unsuitable for daily use. And the effort of replacing it might not be worth it from a financial perspective. If you send your device to @marcost22 I would pay for the postage.
This phone is absolutly fine. I will repair it anytime. I want to keep it for now. It's still a backup phone and one of the last with good audio jack.
Yes, it was for a user that was saying that the max volume for a specific use case was lower than stock, so i sent him to tweak those
Pleasure! This device (and it's sister albus) are two favorites of mine, and keeping them alive was/is one of the things i'm most proud of
Thanks, but no thanks; also some people have offered to donate theirs but unless they are local, they aren't getting the phone past customs; which sucks
And i wouldn't have it any other way. Also, if you want a device with a good audio jack, motorola's up to at least the g30 have one and most still use the same awesome CODEC+AMP combo found in this device from cirrus (by now it's usually the cs35l41 instead of the ancient cs35l34 for the amp but it's still mostly the same)
hi kindly help, gcam pic quality is not good and front cam showing green tint, i want to use moto camera app, please guide me how can i disable camera 2 api, i tried this :
or if there is a better version of gcam available kindly share the link, i am using gcam version 6.1.0.21.22094
- Wait a few moments and the phone will enter TWRP mode. Swipe the arrow that says Swipe to Allow Modifications.
- Enter the adb devices command then click Enter, then enter the adb shell command
- Type the command setprop persist.camera.HAL3.enable 0 then press Enter, to deactivate Camera2API.
- Type the command exit then press Enter to exit.
- Finally, type the command adb reboot then press Enter. So that the cellphone turns back on normally.
- Done.
or if there is a better version of gcam available kindly share the link, i am using gcam version 6.1.0.21.22094
Last edited:
You are doing this completely wrong. By doing setprop in TWRP you are disabling Camera2 IN TWRP
You'd need to mount vendor and then edit the build.prop in /vendor to properly disable, or in userland use adb root and then setprop from there
Also, you do know that without Camera2API motocam/gcam will not work right? MotoCam on this device used Camera2
Anyways, i've not used gcam for a long time but i used to use 7.2.014_Parrot043-V3 on my albus, it has an option for green tint fix
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Yes, that would work but it's extremely obsolete (it's a step-by-step for building android 7.1.1). You can actually follow any device wiki from the same era; they are all the same for the setup. The only thing that changes is the device specific trees (so the device-tree, the kernel-tree and vendor-tree, all three of which can either be found in my github profile or in AICP)1
Yes, that is correct. However, i'd advise against building AOSP as your first proyect because the LOS build system automates a TON of stuff that aosp has you do by hand (kernel building, dtbo merging etc)1
First of all, you didn't "accidentally" type 4 very specific commands
And if you stopped panicking you would have read the tutorial fully and learnt that the command you seek is
fastboot oem fb_mode_clear1
Well that part IS a bug, it should be showing that the button is configured to go to sleep on long press.
Anyways, in the meantime you can mount vendor from twrp and delete the file vendor/usr/keylayout/fpc1020.kl
That will remove the fp gesture functionality1
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 -
6
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:
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:
Device tree source:GitHub - AICP/kernel_motorola_msm8953 at r11.1-albus
Contribute to AICP/kernel_motorola_msm8953...
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:
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
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 LED2
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 times1
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
