yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] IronTechmonkey:
If everybody is else seems to be misunderstanding the description then there is a problem with the description ;).

That being said, there may be hope. Firstly to set expectation of what is normal:

- When device is completely powered off AND NOT connected to a charger, holding power button for 3-5 seconds should power up and boot to system.

- When device is completely powered off AND NOT connected to a charger, holding power button and volume down buttons for 3-5 seconds should power up and boot to bootloader.

- Although you can start the device while powered off and connected to charger it should be noted If the device is plugged in while it is charging it is technically not powered off but rather is running a miniature OS that handles just charging. In that case the delay to power on may be longer.

An apparent exception to the aforementioned expectations which you may (or may not) be experiencing:

There is a odd behaviour that I've seen in several Motorola Android devices including Athene, Osprey and Peregrine where; during the first few minutes after powering down the device (or after turning the screen on when it is charging) the device does not seem to respond to to the long press or if it does it may take longer. When I power down the devices and leave them untouched for at least 2 minutes then the respond to the button presses properly.

So try this::

- No charger

- Power off from menu (not from zero battery charge)

- Leave device alone for 5 minutes (start with 5 minutes the shorten it later if this works)

- Press and hold power button.

- If that does not work then repeat the 4 steps above and also wave the device so something passes across the proximity sensor on the front side.

If none of that works you might have a hardware problem.
[Moto G4 Plus Questions & Answers] Harry Kam:
My phone Boots Up when i Try Multiple time Pressing And Holding power Button for a while ...

Connecting to charger - Not Helping

Leaving device for a while or long - Not Helping

This is happening when my device is Rooted .. I have Completely Unrooted it and locked bootloader then it was working fine but after unlocking bootloader i am facing this problem again :(
[Moto G4 Plus Questions & Answers] IronTechmonkey:
It would be well worth your while to thoroughly research (elsewhere and here at XDA) of how to work with ADB, especially if you will be doing these things regularly (which you probably will), but for a quick walk-through:

- On Android device: Settings > Developer Options > Enable "Android debugging" and Debugging notify"

- Revoke USB debugging authorizations.*

- Make sure you are not at the moment running apps with "write over other apps" permissions. (eg LMT Pie) since on some devices that interferes with the ADB prompt on the device.

- Connect device to computer via USB (leaving the device powered on adn in the OS).

- Look for and acknowledge on the Android the ADB prompt to allow that computer.

- If the prompt does not appear then continue.

- If on PC open command prompt with administrative credentials at the ADB folder (If you open the command prompt elsewhere then ADB must be in your system path variable) then enter adb devices from

- If on Linux and assuming ADB is installed and OS knows where it is, open terminal anywhere and type "sudo adb devices", then enter you administrative credentials.

* Disclaimer: This will clear the history of devices which have been previously granted permissions to access the device by USB (and I'm not responsible for any consequent damage to your device or the universe).
[Moto G4 Plus Questions & Answers] IronTechmonkey:
I don’t want to sound like I don’t appreciate your efforts because it is nice to have these comparisons in general way but as it stands now they belong in a general thread like this one.

Please, until you reach the point of a establishing this (or anything else) as an actual LOS specific bug in an actual clean flash (where you have verified the steps taken) post in this thread and stop clogging the primary LOS 14.1 Athene development thread with stuff that is off effectively topic.

The frequency with which you are jumping between tests, the fact that you’ve not confirmed clean flash process (and have resisted doing so several times), and the fact that you've cited the very different installation and test process for stock rather than the logging instructions from the LOS thread are all indicators that you've not simply clean flashed LOS and removed all 3rd party variables.

P.S. Don't be put off by the words "General" and "noob"in this thread's title. Some very knowledgeable users follow this thread and may have helpful advise. More so than in the LOS thread because this thread is not just for one ROM, and nor are your reports from just one ROM. If demonstrate an LOS bug in a clean flash then bring it back to that thread.

Meanwhile in the LOS 14.1 Athene development thread I'm going to bump my recent and informative feedback regarding the confirmed LOS screen-on lag bug, which was buried by OT almost immediately after it was posted.
[Moto G4 Plus Questions & Answers] IronTechmonkey:
As mentioned in the LOS 14.1 Athene dev thread you can add notes to and follow the ticket to stay updated.

As to battery:

The fact that the data usage is recorded in the wrong category (folded into Android OS) is not a cause of more battery drain. That may make it harder for you to figure out what is draining battery but it is not itself the cause of the drain.

There are very many factors which are not part of the ROM which could cause increased battery drain. You should test to determine what is causing the drain. Apps such as Better Battery Stats (available on XDA and at Play Store) and Wakelock Detector (available in Play Store) as well as other apps might help you determine what is consuming battery. Also, the XDA Better Battery Stats thread is full of good advise and users knowledgeable about this stuff. https://xdaforums.com/showthread.php?t=1179809. This thread may also be a good place to search for clues.
[Moto G4 Plus Questions & Answers] Krishan94:
Thanks mate it works now ....
[Moto G4 Plus Questions & Answers] IronTechmonkey:
FYI regarding possible direction in which to take the Athene LOS 14.1 reboot issues, a long standing Jira ticket watched by 20 people which seems as if it could be related, described and linked here: https://xdaforums.com/showpost.php?p=76660319&postcount=2823.
[Moto G4 Plus Questions & Answers] :
Hi all, I have a Moto G4 Plus XT1643 Android 7.0 running Android Security Patch level April 1,2018 initially. After checking various websites I chose to root my phone so that I could try out a custom ROM. I followed the following tutorial "https://devsjournal.com/how-to-root-moto-g4-moto-g4-plus.html" to root my phone. Before rooting the phone I fortunately took a Backup using TWRP with the following partitions checked-System, Data(excl. storage), Boot. After that I completed the procedure as per the before mentioned website; but the phone did not boot up. So I booted into TWRP and restored the Backup but and now the phone settings is showing Android 7.0 running Security Patch Feb 1, 2018 instead of the April Patch Level that was originally running when I took the backup. When I checked the root status it is saying my phone is still unrooted so I could not flash any custom ROM.

I went and downloaded the OTA software update April Patch which showed up as a notification and gave install. But on rebooting it keeps going into TWRP. I only understood later on that with TWRP recovery installed one should not give OTA update from the phone settings. I thought restoring the previous backup would solve the boot into TWRP issue and gave restore but the phone still boots into TWRP. Now I am manually giving START option from the bootloader mode to get Android running when ever I feel like restarting the phone.

So the present state of the phone = Bootloader unlocked, TWRP installed (twrp-3.2.1.0-athene.img), Build no:NPJS25.93-14-15 and NO ROOT access and running Android 7.0 with Security Patch level Feb 1,2018 .

Few questions, that I have before I end up doing something worse:

1) Without rooting my phone if I simply flash the stock recovery.img using the same method as before (fastboot cmd) will it remove TWRP and the Backup in the internal storage and bring the phone back to normal boot sequence for OTA updates? If yes, please note that the Motorola Support does not provide official stock recovery.img for my phone, then can I use the ones available in this forum and does the recovery file have any version dependency?

2) Or do I have to root my phone and then go for the laborious process of downloading the entire stock ROM and flashing it to get OTA?

Sorry for the lengthy post, after reading different threads in xda I am confused as to what step to take further to avoid the boot issue since my phone is still unrooted.
[Moto G4 Plus Questions & Answers] IronTechmonkey:
The thread you posted in is a DEVELOPMENT thread focused on BUG TESTING in which general stuff is not suppose to go (and this is fairly obvious from the OPs of that thread which almost exclusively describe bug reporting methods). No decision of mine, that's just the the way it is, and this distinction is made in many forums including XDA.

Even though this thread is for Moto G4 in general and not specific to LOS, as I mentioned there are some knowledgeable people here who can advise you (including me) specifically about LOS. You can also search both threads for answers (an actual XDA rule) and search LOS jira for known bugs (https://jira.lineageos.org).

Additionally there are answers to your question about existing bugs (described in copious detail with linked references) in just the last few pages of the development thread, but if just you want a general review (which is a reasonable thing to seek) then please follow up here. That's what thread like this are specifically for. To that end I'll quote-post your original question, although it would be more efficient and easier for you to track replies if you did so yourself which is why I suggested it:
[Moto G4 Plus Questions & Answers] IronTechmonkey:
[MENTION=7105143]david.gs.gm[/MENTION] asks:

[EDIT] From my experience with LOS on 2GB Moto G4 xt1625 (informed by comparison to 1GB Moto G3 Osprey and 1GB Moto G Peregrine):

Firstly, there is one potentially nasty bug where were spontaneous reboots occur. It's clear that this is an LOS Athene specific issue, but it affects devices in different usage scenarios to varying degree, and no one has pinned it down. Some people report frequent reboots while others report none. When there was a SIM in my Athene device it occured a few over a few months, and when there was no SIM it did not occur over several months. This in particular was the issue that has been "copiously reported" and it is worth reviewing those references. If your device experiences this issue then you might not want it hand it off to someone else. On the other hand if your device does not experience this, most other issues are probably not "deal-breakers".

One other issue is a delay between power button press and display on. This issue does not seem to be as prevalent as the aforementioned but is real, and device specific, and possibly LOS specific. This is another issue for which there have been detailed reports worth reviewing.

Camera: The LOS camera is, IMO not LOS' finest feature and I understate. On 1GB devices in general, and particularly for panorama pictures, it has an impact on RAM (background services may FC). On my 2GB Athene device it performs OK but not as well as some other cameras. Fortunately some of the stock Moto cameras are available (XDA and other places) as backup or even primary camera.

Wifi: Works well for me but I'm usually on the same home wifi network which does not speak for many aspects.

GPS, seems to work fine. It usually takes a few minutes longer to get a device-only GPS fix on my Athene than Osprey or Peregrine but AFAIK no worse than stock and not so much longer that it is a hindrance (in my usage case).

Sound: Seems quite good but this is a highly subjective measure.

Whatsapp People have reported but not clearly established some type of issue with whatsapp which may have been fixed. I don't use Whatsapp but have seen those references. They are worth researching.

Facebook: Could not say.

In general: Without casting an criticism at the device maintainer, among my 3 devices running LOS 14.1 this one seems to have the least presence for device specific bug fixes at LOS Jira but still benefits from the general work-flow. Maybe the focus is shifting to LOS 15, as is the case for many devices.

Considering the 2 established issues mentioned above if you are handing it off to someone else you might want to test if for a while first (at least several days). On that note... "Try it yourself" is a common response (not just from me) to "how does it perform" questions in development threads. You may not have liked being asked to go here but it was the appropriate thing to do and enabled a more helpful response.
[Moto G4 Plus Questions & Answers] :
Dear echo92,

Thank you for the fast reply. I will certainly look into both options thoroughly. I am a little busy this weekend. I will post the updated status soon. Thanks again. Also I was under the misconception that a phone has to be rooted first to flash custom roms, since almost all tutorials use the rooting method. Thank you for clearing up that misunderstanding.

Update :

Hi,

I downloaded the stock recovery with correct build number (the stock recovery file obtained from the link to the drive you posted) for the Feb Patch and gave the command "fastboot flash recovery recovery.img". I thought this will replace the TWRP with stock recovery so OTA update will happen on its own. The boot into TWRP problem is solved :)

However now when I give the ota update the installing update animation is shown for some time and then the screen changes to simply error. I tried rebooting the phone again and giving the ota update but same error is shown.

Image : https://imgur.com/GsuRy7r

On booting along with the "bootloader is unlocked" message of motorola, now it is showing "ID: bad key".

Is this because of some difference in the recovery like being from not for the India region or something?

Is it safe to give a factory reset with this new recovery installed?
[Moto G4 Plus Questions & Answers] ezezap:
Did a lost my phone???

Hi, sorry to bother you but I can't find anyone with a similar problem/solution to this, I was updating by OTA my XT1641 and It get stucked in a boot loop, every single option in Fastboot mode (except Power OFF) leads to bootloop again. Anyone knows how to solve this???

I have tried with all options available in fastboot, bootloop response only

I tried with ADB and some different ROMs, bootloop again...
[Moto G4 Plus Questions & Answers] Dhanush-raj:
Read 1 page back echo92 has given two ways to fix your issue.. Hope so it helps.

https://xdaforums.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598/post76681434
[Moto G4 Plus Questions & Answers] StevenFernandes:
Hello guyz, I'm running into really weird issue. My phone suddenly shuts down at around 50% and then it refuses to boot and shows 'it cannot be started because of low battery' (even if my phone is at 50%). Then i have to plug it to a charger and it boots properly.

Model: xt1643

Rom: Stock Nougat, RR 6, RR 5.8 (experienced this issue on these 3)
[Moto G4 Plus Questions & Answers] echo92:
Hmm, if you've experienced this on the stock ROM as well, that suggests the battery or another issue with the hardware. Have you looked into getting the battery replaced? Could be the battery isn't holding a charge or not outputting enough power (as an aside, it's an issue which affects many devices over time, e.g. https://www.howtogeek.com/342185/how-to-disable-your-iphones-cpu-throttling-in-ios-11.3/ ) which would also explain why your device boots okay with supplied power.
[Moto G4 Plus Questions & Answers] StevenFernandes:
I was wondering the same thing, it might be the battery that is nt holding the charge (as this device is 2 yrs old). Thanks for the help.
[Moto G4 Plus Questions & Answers] meetXD:
It's been a while since my headphone jack stopped detecting when anything was plugged in.

Until now, I was getting along fine using an app called SoundAbout to force route audio to the headphone jack, but the app doesn't work with Android Oreo.

I'd love it if someone would provide a script I can run with tasker (or similar) that I can use to enable and disable forced audio routing.

Only then can I finally update my Rom!

Thanks!
[Moto G4 Plus Questions & Answers] rahulsj92:
Offline charging

Guys, how do I use offline charging in Oreo ROMs? My phone has some problem with it's charging point and I don't want to spend any money on it. Whenever the phone goes below 15% no matter what I do(airplane mode, recovery mode, bootloader, switched off), it never climbs over 15%. When I try to charge it switching off, it restarts and then due to low battery switches off. This vicious cycle drains battery. I read somewhere on XDA that offline charging is required for this. This issue prevails over all 64bit ROMs. Please help.
[Moto G4 Plus Questions & Answers] sd_shadow:
It should charge in bootloader mode.
[Moto G4 Plus Questions & Answers] squirvel:
So this is a strange one: I have twrp flashed and whatnot, and am (or rather was) trying to sideload on a rom. In device manager (win7 x64) the phone appears as an unknown device as "omni_athene". A couple google searches for drivers is turning out blank (and while I just ended up copying the file), having a useable sideload would be quite nice. Any ideas on what to do?
[Moto G4 Plus Questions & Answers] echo92:
Apologies for the late reply - I didn't see the edit.

As for your experience - did you end up flashing the full stock ROM? That error may be as a result of modifications made whilst flashing TWRP and attempting to root, which may cause the OTA to error out. One option as I mentioned previously is to full flash the stock ROM - unfortunately, simply replacing TWRP with stock recovery does not sometimes work in fixing OTA errors. Thus, you might have to restore your device to a clean, unmodified status before taking OTA updates (bootloader unlocked status does not matter). Ensure that you're flashing the latest stock ROM available (the latest leaked firmware is NPJS25.93-14-18, April 2018 https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )

ID bad key is normal if you've tried to flash stock firmware/OTA updates. On subsequent updates, that should change to ID:N/A.

That recovery is for the India region, as it was part of the firmware released to Brazil, India and EU/UK regions (same goes for NPJS25.93-14-18).

If you really want to, I see no harm in a factory reset with the new stock recovery, however, you will lose your data. I would honestly recommend flashing back the stock ROM as I described previously and then attempt to use the OTA updates. I've performed this flash back of the stock ROM and have had few issues installing OTA updates. Alternatively, flash the NPJS25.93-14-18 firmware as I suggested and forget about using the OTA update this time.
[Moto G4 Plus Questions & Answers] sd_shadow:
If you have an update on your issue, please create a new post rather than edit an old post.

Most people rely on notifications to follow threads, and we don't get a notification if you edit a post.

New information may get someone to chime in with a possible solution.
[Moto G4 Plus Questions & Answers] blitzik:
Hi Guys,

Got a weird error on my phone, and now I can't get it to start up. Instead it boots to a text screen with a few different options, selectable with the volume up and down buttons.

Bootloader logs, Switch Tools mode, Start, Restart Bootloader, Recovery mode, Power off, Factory, Barcode, BP tools, Qcom

It starts up on the Bootloader logs screen with the message

Start up failed:

Your device didn't start up successfully.

Use the Software Repair Assistant on computer to repair your device.

Connect your device to your computer to get the Software Repair Assistant.

AP Fastboot Flash Mode (secure)

And under that is a mirror of whatever fastboot is doing, so luckily I at least know that the phone is still connecting.

I'm trying to start off flashing a new recovery, since I can't seem to get into twrp but whenever I do try to flash i can't get fastboot to recognize the recovery image file. I've tried to use the older recovery images I had but they aren't being recognized either. I have all the files sitting in the same folder, and am using the cmd-here icon to access fastboot. Any idea on what to do? Should I even be trying to flash recovery in this instance at all? I'm stuck!

I should mention that this phone was stock and rooted. I've been ignoring ota updates for months.
[Moto G4 Plus Questions & Answers] sd_shadow:
What is the exact error you get when trying to flash
[Moto G4 Plus Questions & Answers] blitzik:
I keep getting the message:

failed to validate boot image

ERROR: Failed to pass validation. backup to fastboot

When running fastboot to reflash recovery, It shows this during the recovery portion.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-athene_shreps.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:recovery: not found

target reported max download size of 536870912 bytes

sending 'recovery' (13674 KB)...

OKAY [ 0.453s]

writing 'recovery'...

(bootloader) Image recovery failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.505s

after reboot it goes back to the screen I described, no change and no way to get into recovery mode.
[Moto G4 Plus Questions & Answers] echo92:
Hmm, on the bootloader screen, do you see OEM_locked or flashing_unlocked status? Those pre flash errors look like a result of a locked/relocked bootloader...

Was there any flashing or anything that happened before this behaviour occurred?
[Moto G4 Plus Questions & Answers] blitzik:
Crap.. oem_locked

I don't know how that could have happened. It's been unlocked for the better part of a year. My phone died, and I started getting all of this when I put it on the charger late last night.
[Moto G4 Plus Questions & Answers] blitzik:
Now I'm having difficulty unlocking the bootloader. I found my old unlock key in email, but it does not seem to be working any longer!

C:\Program Files\Android>fastboot oem get_unlock_data

< waiting for device >

...

(bootloader) Unlock data:

(bootloader) read datablock error

(bootloader) Failed

OKAY [ 0.055s]

finished. total time: 0.056s

C:\Program Files\Android>fastboot oem unlock Y3YYLBU6GKPCFEKQCGEA

...

(bootloader) feature disabled

OKAY [ 0.011s]

finished. total time: 0.012s