Recent content by DustArma

About the encryption support, is the phone unable to encrypt when asked to or is it unable to decrypt at all

Probably the blobs from the Moto Z2 Play Oreo update, whom we share SoC and camera hardware with. (Snapdragon 626 is just a better binned SD625)

Is there an option to hide the navbar for one button navigation?

Just the usual crashy and unreliable camera, I understand that currently there's not much that can be done about it.

I get it now, but FYI the Z Play had a different sensor, it was a 16MP omnivision sensor with phase detection autofocus

It's a Snapdragon 626, it and the 625 are essentially the same save for clockspeed. The Moto Z2 Play also uses the same IMX362 sensor as the G5+. As far as I know the Z2 play also uses kernel 3.18.x. That's mostly why I'm asking

Dumb question, but, kernel sources for the Z2 Play Oreo update got released, would those help any to get things such as more stable camera?

It does as any phone shipping with Oreo must do, however keep in mind there's no official way to unlock the bootloader at the moment.

You can find /oem in the firmware packages and it's not like a treble ROM will be using the /oem partition

why not use /oem and mount it as /vendor?

Idiots posting their IMEIs inside the thread when OP explicitly asked for them to be sent via PMs ?

Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?

vache at the Moto G5 Plus forums has already managed it using the /oem partition which is otherwise unused for custom ROMs

Retus still on November 1st I believe, I guess Jan 1st will arrive on... March maybe? Going by previous rollouts.

Yes, but devices that have extra AOSP unused partitions, such as the Xiaomi /cust and Motorola /oem can have those partitions mounted as /vendor for treble ports. I'm guessing what's most important is that the partition has enough space for all the vendor blobs