Search results

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

Hah, I figured the OEM partition would be the key after reading the RN4 treble post. As for the O camera blobs, wouldn't blobs from the Moto Z2 Play Oreo update work, as far as I know the camera sensor is the same (IMX362)

Just as an FYI, try to copy the log starting from when the app crashes, your log is way too long as it stands

Xperia XA2/XA2 Plus, they've been added to Sony's Open Device Program https://github.com/sonyxperiadev/device-sony-pioneer/ https://github.com/sonyxperiadev/device-sony-discovery/

I use this one http://www.vinsic.com/Products/sku-VSPB303W 20k mAh, QC3 output and USB Type C support so it's fairly future proof It charges my phone several times before emptying

So it seems like Alberto97 over at the Moto Z Play forums managed to build 64-bit build without the app_process hack https://forum.xda-developers.com/showpost.php?p=75272261&postcount=263

Will it be released in South America?

Manual camera using camera2 API can net different results, on G5 plus with the same sensor the Moto camera has the same settings but on manual camera exposure and ISO have more settings

If using Manual Camera?

I highly doubt they work because the models lack the hardware

Installing multiROM results in the phone not booting.

Very funny, all the GCam ports I've tried have focus not working at all.

Does it have working autofocus.

Check on Geekbench or CPU-Z, this phone actually uses 64-bit Android. You can use the google camera port

You need a 4pda account to download from their forums, the 404 error only happens when you are not logged in.

There's an updated app if anyone has a 4pda account https://4pda.ru/forum/dl/post/11407270/GC_Android-6.0%2B_arm-arm64_C2API_maxParam.apk

For retus 137-83 use kernel 2.01

Camera2 API isn't supported by the custom ROMs

Battery is too bad nowadays even if performance is alright, if you absolutely must go Moto then get the G5 Plus

That'd be nice, retus is still on 137-35-5

Thanks, camera works now. You don't even need to set permissions, just drop the file in the indicated folder and launch the camera

I believe this is the last release. https://drive.google.com/file/d/0BxViOa-VZuZxN1RpRUJlX1JRWDg/view?usp=sharing

Anyone got a link to 2.2.2?

No maintainer and hasn't been updated since december last year

Due to the following post from the CypherOS Google+ community I decided to build 3.6, flash at your own risk. https://plus.google.com/109812248604746035480/posts/Wgiu98r4dKL?sfc=false https://drive.google.com/file/d/0BxViOa-VZuZxVjJicXJNRWVYWnc/view?usp=sharing I don't believe we have a...

Some way to disable the root notification icon per app.

Changing filesystem using TWRP does the trick, as for how well it works, to be honest one of the first things I did when I got this phone was change /data to f2fs as I had a great experience using it with the 2013 Moto G, I haven't actually tried comparing

The kernel and latest twrp seem to support F2FS, I'm using it right now, the problem is that switching from ext4 to f2fs requires reformatting /data, not sure anyone would wanna do that

Microphone isn't working with SELinux enforcing

Can confirm that mic issue happens too. setenforce 0 as root in a terminal to fix until next boot

Do we even have an active maintainer?

the victara build needs to be updated to support Nougat encryption.

If you want official nightlies that bad then do a pull request to add Victara to the Hudson build system

Just a heads up, Xposed will cause a bootloop on any ROM that implements the November security patch

It actually matters a lot for crypto performance

Anyone else having no audio with these builds?