marcost22 said:

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

ahh thats makes sense, between the gcam version you suggested, i am using its updated version now, and issue seems fixed, i just whole heartedly wanted to thank you for reviving moto z play again. lots of love <3

bunt009 said:

ahh thats makes sense, between the gcam version you suggested, i am using its updated version now, and issue seems fixed, i just whole heartedly wanted to thank you for reviving moto z play again. lots of love <3

Glad to hear it!

bunt009 said:

@marcost22 Your ROM is very nice and up to date, i didnt encounter any bug so far, however noticed a weird bug, where if i put the phone on speaker, suddenly the volume becomes low, then again i have to toggle the volume slider from down to up and the issue gets fixed, is this is just with me ? can this be fixed please ?

It is a well-known and well-documented issue. It has to do with the speaker protection code and the proximity sensor acting up in newer versions; i don't really know how to fix it so it remains unfixed

marcost22 said:

It is a well-known and well-documented issue. It has to do with the speaker protection code and the proximity sensor acting up in newer versions; i don't really know how to fix it so it remains unfixed

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

bunt009 said:

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

marcost22 said:

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)

Ah its for 7.1.1, i thought i can make android 11 out of it, same with AOSP ? if i follow AOSP guide to build it (android 11 based rom)? and later i can add the files from your github!

bunt009 said:

Ah its for 7.1.1, i thought i can make android 11 out of it, same with AOSP ? if i follow AOSP guide to build it (android 11 based rom)? and later i can add the files from your github!

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)

bunt009 said:

@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

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_clear

marcost22 said:

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_clear

thank you for your prompt response, yesterday flashing went weird for me, twrp wasnt reading the storage, i wasnt able to flash anything.
so thought going back to stock, also volte calls and sms is not working for me, however internet is working fine.
so this is the main reason for my hopping from one ROM to another, if rom hopper (distro hopper*) is a term that will be me haha

marcost22 said:

Why are you on 7.1? That will cause issues anyways. You said before that you were running 8.0 retcn, use that

I'm sorry I put it wrong. I tried other options later, because the firmware on the 8 ret cn did not help. I always flashed first on 8 ret cn for custom roms.
Now the situation has not changed, I set the aicp aicp_addison_r-16.1-WEEKLY-20220514 with a fix NFC cn and last aicp_addison_r-16.1-WEEKLY-20220604. NFC also disappear after > 70-50% percent phone charge. There is no such problem with blink on/off NFC of the stock cn rom and on the aosp Alberto97 arm(arm 64 too) pie rom. Sorry, I didn't answer for a long time because I was testing different options, trying get nfc config from Alberto97 rom, trying patch nfc 1635-03. And install aicp on other stock roms (retail, eu, us, verizon 8 oreo)
The situation is the same

First always try flash aicp on stock XT1635-03_ADDISON_RETCN_8.0.0_OCN27.82-24_cid11 first (latest 8 cn rom).
with twrp 3.2.3 treble, with format data and factrory reset. All works well except nfc

kentceo said:

I'm sorry I put it wrong. I tried other options later, because the firmware on the 8 ret cn did not help. I always flashed first on 8 ret cn for custom roms.
Now the situation has not changed, I set the aicp aicp_addison_r-16.1-WEEKLY-20220514 with a fix NFC cn and last aicp_addison_r-16.1-WEEKLY-20220604. NFC also disappear after > 70-50% percent phone charge. There is no such problem with blink on/off NFC of the stock cn rom and on the aosp Alberto97 arm(arm 64 too) pie rom. Sorry, I didn't answer for a long time because I was testing different options, trying get nfc config from Alberto97 rom, trying patch nfc 1635-03. And install aicp on other stock roms (retail, eu, us, verizon 8 oreo)
The situation is the same

First always try flash aicp on stock XT1635-03_ADDISON_RETCN_8.0.0_OCN27.82-24_cid11 first (latest 8 cn rom).
with twrp 3.2.3 treble, with format data and factrory reset. All works well except nfc

Click to expand...

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

Touch2Fin said:

Hello there, I've just got a Chinese varient of this model (XT1635-03, Dual SIM), and flashed this ROM. Feeling really grateful for your efforts you've made to support this old model.
However, there are some issues of the fingerprint button in the 20220604 weekly version. Every time I touched it when the screen is on, it would get locked automatically. And the App Edge for Xposed tells that there is an command of KEYCODE_SLEEP (223).
I've tried to catch a log for this issue, hope I've catched this 'cause I'm not pretty good at doing this stuff

Google Drive: Sign-in

View attachment 5634543

Click to expand...

That is not an issue, that is the correct behaviour as is coded. You should be able to customize this by going into Settings->AICP Extras->Navigation->Customize buttons and under start button (or main button) you change all to do nothing

marcost22 said:

That is not an issue, that is the correct behaviour as is coded. You should be able to customize this by going into Settings->AICP Extras->Navigation->Customize buttons and under start button (or main button) you change all to do nothing

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.

Touch2Fin said:

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.

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 functionality

marcost22 said:

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 functionality

I've done as followed and it worked, thanks!
Also wonder if this issue could be fixed later?

Touch2Fin said:

I've done as followed and it worked, thanks!
Also wonder if this issue could be fixed later?

I'll be looking into it