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
Can you confirm for me the exact Z play model you had?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
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
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 variantThank 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?
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 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.
Not that i know ofThis 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?
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 ofThanks 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!
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)
You are doing this completely wrong. By doing setprop in TWRP you are disabling Camera2 IN TWRPhi 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 :
this didnt work for me...help appreciated!!
- 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.
or if there is a better version of gcam available kindly share the link, i am using gcam version 126.96.36.199.22094
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)understood !!
@marcost22 as you have experience in developing custom rom & i am planning to give it a try and build my own custom rom for moto z play, could you please do me a favor and review https://wiki.lineageos.org/devices/addison/build is following this set of instructions is enough for building the rom ? or it has to be already supported devices in lineage list ?
AOSP also has similar kind of steps, so my doubt is, will following the list of described steps are enough to get it working on my phone ? or there is more technical part ?
my question is how it will be moto z play specific ROM, if you have any wiki about it, i will try to explore !!
thank you !!
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)
First of all, you didn't "accidentally" type 4 very specific commands@marcost22 hi i need your help, i accidently typed
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
this command since then when ever i reboot my phone, it enters to bootloader, can you please help me fix this ? appreciate your help
Well that part IS a bug, it should be showing that the button is configured to go to sleep on long press.Hello, there! I've looked through the AICP extra. But just couldn't find the start button or the main button option. There's only a home button customization (intended for the hardware button I suppose?) that would show up when the on screen navigation is disabled, but that options wouldn't work.
I've flashed the 20220326 version as well, neither of these versions' settings gave that option for the start button.
#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. * */
1. GCam is not officially supported, you are going to have to ask around and find which one works fine with this deviceFirst 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.
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