Search results

Does a stock image for Oreo exist as far as anyone knows? Having some trouble flashing Nougat stock because Oreo has a newer bootloader version that can't be overwritten with an older version. ---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ---------- I have the...

Like I said, I'm on the latest Magisk Beta - 16.7 (1671) - and I'm running stock Oreo 8.1 on a Moto G5S Plus. The same thing also happened when I was on 7.1.1 Nougat before I upgraded to Oreo and on the current stable release of Magisk (16.0). A clean reinstall of Magisk or complete phone...

Magisk installs fine and modules install, but they don't seem to do anything. Viper4Android app installs, but no functions within the app work. YouTube Vanced installs but no changes are made to the YouTube app even after a reboot. Android Pie Fonts installs but the font remains Roboto after...

If you could get your hands on the APK, it might install on the G5S Plus. If not, it looks a lot like it's just a frontend for Google Smart Lock anyways, so it's not like you're missing out on anything. Edit: This looks promising...

If it's publicly available, it'll be in another thread somewhere.

ARCore only works on 64-bit devices. It's possible that they're going to be releasing a 32-bit version, but some part of me wants to hope that this means the G5S Plus will be updated to 64-bit with the Oreo update.

Android OEMs get the contents of the security updates weeks in advance, so it's understandable that they'd release the June security update a few days early. It happens all the time with manufacturers that actually release updates often.

Would it be possible to use the earpiece speaker as a second speaker?

I had this issue after I downloaded and flashed the most recent factory image for my Moto G5S Plus (XT1806) from this post: https://forum.xda-developers.com/showpost.php?p=76070231&postcount=24. At the time, it was NPSS26.116-48-12, build date March 1st. The restore succeeded after following...

I mean, that depends on if you use the dual camera features.

The G5S Plus doesn't have a built-in video chat application. You can download Google Duo from the app store, which is what would be the default video calling app if the G5S Plus had one.

It's a delay counter. It replaces the default initial (non-animated) boot screen, so it might also be longer than 5 seconds.

Stock ROM + Greenify.

That's normal.

That's not how it works, unfortunately.

https://ausdroid.net/2018/02/05/motorola-rolling-oreo-large-number-phones-today/ The article doesn't quote a source, so take this with a grain of salt. If anyone does end up getting the update in the coming weeks, don't forget to capture the OTA and post it here!

For me, the most exciting thing is that it's relatively small compared to most phones out there.

Yes, but it's covered in the phone's specs. Not usable for day-to-day.

Will flashing this work if I have the September security patch? Screenshot of my About phone page attached.

I have to correct you on at least one point there. The Moto G5S Plus kernel sources have been released since before the phone was even out in the U.S. The only question I'd ask is, can you live with only one SIM or only 32GB of storage? If the answer is no, then the G5 Plus might be the better...

The config inside the zip suggests that it's region-independent. Will give it a try and report back. ---------- Post added at 09:06 PM ---------- Previous post was at 08:56 PM ---------- No issues running on my XT1806 (64GB/4GB, US variant). Strangely though, the build number didn't change...

In good light, the cameras are about equivalent. The lower the amount of light in the scene, the better the G5 Plus holds up over the G5S Plus. That said, neither are likely going to be as good as your Nexus 6.

It's called a slow rollout. Some people get it before others.

No, it won't work.

Mine came with full Camera2 support out of the box. XT1806, US model.

No wifi issues for me, I get around ~110Mbps throughput on 5GHz.

Unlock your bootloader, flash Magisk in TWRP. No, there is no way to do it without a bootloader unlock.

I just got my Moto G5S Plus in the mail and it doesn't seem to have any Bluetooth LE issues. US retail model on the NPS26.166-45 firmware.

Use Trepn Profiler to view the frequencies of the processor cores while you perform other tasks.

That is incorrect. Android Oreo supports 32-bit devices just like always.

Not when people keep buying their insecure, unpatched phones. ¯\_(ツ)_/¯

That would suck, since the 8.0 update isn't due until December.

It's kind of unfair to have this rating up so early in the game.

Wow, that was fast.

Man, that sucks. Might have to cancel my order because of that. I use smartwatches and stuff. Motorola isn't exactly known for their expediency when releasing bugfixes. That said, they released 2 updates within the first few weeks of the G5 Plus' release, so maybe they'll do the same for the...

Cool. Okay, one more question - can someone confirm that there are issues with the phone switching back to LTE after dropping to 3G due to a weak signal? Does it do it eventually, or do you need to force it? Edit: Oh, and one more thing - when the Oreo update comes out, I'll have to flash the...

And that would probably require an unlocked bootloader, right?

What would the process be for making this work with an unlocked Moto G5S Plus (assuming they have the issue)?

So, does it break most camera apps or not?

Are you using the modified TWRP? The modified TWRP doesn't boot on my XT1604, by the way. Flashing and booting it caused the phone to get stuck at the bootloader unlocked warning boot logo. Even holding down the power button wasn't able to shut down the phone, I had to open it up and disconnect...

Nope. That's designed to stay there forever. There are ways to get rid of it on other phones though, so it might be possible.

That'll just brick the phone, I'd think. That's what happened when I tried flashing the Canadian modem on my Canadian ZE552KL after flashing the WW ROM from ASUS' website.

I've had this issue since I got the phone, ZE552KL. Turning off auto brightness fixes it for me, so I have a feeling it has more to do with ASUS' auto brightness algorithms than anything else.

I stand corrected. TIL.

There was a short period where they were accepting applications. Only a few people got in, myself included. They might open it up again when there's a beta version of Android Oreo for your model. By the way, the ZE520KL has 3GB of RAM and 32GB storage. The ZE552KL model has 4GB RAM and 64GB...

Thanks for this, it's really clean and nice. Much better than the stock one on the Zenfone 3. I got so fed up with that one that I ended up making my own similar in concept to this gif: I'll link it here so that anyone else can use it. Should be compatible with all Zenfone 3 variants (and...

I've been testing each new version before it comes out through ASUS' beta program. I've found newer firmwares to fix more and more bugs, with no downsides. Updating is super easy if you sideload the update via adb and simply install Magisk when you're done for root. I did it just the other day...

I find the newer versions to be much more stable. Give it a try, re-rooting is easy.

IIRC, there is a way to lock the bootloader, but it doesn't reset the flag in the bootloader that says it's been unlocked. They'd know even if you did.

Yep, ASUS just confirmed it. Guess I'll be keeping my ZF3 for a little while longer.