yashsingh1/xdaforums huggingface dataset:
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
So, I've come back from trying other ROMs, and the damn GPS isn't working anymore, it seems to pick up the satellite signals but the phone is unable to communicate with them, this is a screenshot I've taken of the GPS status app, I've been waiting 5+ mins outside in a clear day and nothing.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
As you know the GPS hardware/interface *sucks* on this device. I snagged a $40 E4 from WalMart (essentially the same device with a few tweaks) and BT tether it to my G4P for mobile navigation (could also have downloaded maps but need real time traffic data). Works great at the fraction the cost of a new phone. Point is the GPS is hopelessly crippled on the G4P. Nougat based ROMs can't fix it but may be slightly more resilient dealing with the crappy hardware.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
yeah, I was searching around and found a forum where they took apart the whole thing to fix the antenna contacts, I did the same, bending the contact pins so they would have better contact, but no luck either, Maybe I'll stick some solder to improve contact, but my hopes are really low right now.

Now, This problem arose when I flashed RR after a deep wipe (formatting all the partitions), but it seems that is most likely a hardware problem . Man I'm so disappointed at moto right now, goddamnit lenovo.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
FWIW - I have gone the whole bend/extend/enhance/etc the contacts route with no definitive results. Occasionally things look better for awhile only to be followed by disappointment. Signal strength for every satellite is 30-50% lower than on the E4 when in the same physical location. I also think there may be a driver/binary problem as the device will sometimes fail to get a fix despite having more than an adequate number of satellites 'in view'. Most likely Lenevo sourced a lousy GPS 'bolt-on' for this device which may explain why G4Ps sent in for warranty repair come back working. I even looked into swapping the GPS hardware with an E4. Externally they are considerably different; didn't go any further with it.

I feel like a dork driving with two handsets on the dash (G4P for network access tethered to E4 for GPS) but it works for now and was a cheap workaround that frees up my phone for other tasks. Ultimately I plan to switch to an XT1687 (G5 Plus) but may stick with a XT1768 (unlocked E4) as traditional handsets are not my daily driver. I use a high-end tab for calls/text/apps/etc falling back to the G4P only when I need to carry something smaller. Same with navigation where an old school Garmin GPS does the bulk of the work unless real-time routing/traffic is needed. Still, if I'm on foot and need directions the GP4 is next to useless as the GPS rarely works in a dense city environment.

I'm sure Pixel, Galaxy S8, iPhone, OnePlus, etc. users are laughing right now. Alas, I choose to invest my hard earned coin elsewhere.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
Hahahahahaha you gave me a good laugh mate, but it's true and frustrating that the GPS hardware on this handset is so lousy, but with enough patience I managed to get a somehow good reading, the screenshot is on an indoor reading sitting for about 45 mins... Man, I miss my Sony handset, they put good sensors and pair them with an awful processor, i8080's era ram and even worse software but it did the job. And man the Samsung hardware is quality but it is DAMN OVERPRICED... I'm aiming for the MG5P as my next handset as well, maybe wait for the next iteration.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Yep - with sufficient patience (and a dab of luck) the GP4 can haul in a stable GPS signal when not in motion. That doesn't work for navigation when the depicted location sometimes lags actual location by several seconds or more. That can be a problem with a series of quick turns. Prior to snagging the cheapo Verizon E4 (which I never activated so relies on BT/WiFi for connectivity) my device thought its name was 'maternal xxxxer' as I usually spoke to it with great affection when it advised a turn 200 meters past the intersection. Hopefully you're seeing better results.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
Detected a huge problem in the recent update

The camera doesn't work ever since the update

Opened it and says "media server died closing app"

Can it be fixed?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
That didn't happened to me, have you tried 3rd party apps like a better camera or mx camera? Maybe formatting all the partitions before a clean install
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] elisam98:
I'm on the latest nightly and I've been noticing that the call/speakerphone volume is pretty low...

Anyone else having issues with that?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] indrojit:
Does not install in my device show process may end with errors
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
Not sure but I think its the auto update that you do via settings

I'll try doing that and I'll let you know but still this happened after updating to the January update
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
The January 10 update fixed the camera not working issues works great

Edit: I found the problem

Do not flash squid kernel on these recent updates it causes these problems
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
It always does, try to stick to the kernel that comes with the roms
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
OK and thanks at least its fixed ?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] ankith7:
i have a problem with video recording, when i record a long video, say 1+ min, and then try to play it the "video" will freeze after 28 seconds but i can still hear the audio. I've had this problem since 03 build.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] jasonmerc:
If you can get a logcat or dmesg and attach it to a post stating your problem, it would be much more helpful for the devs.

There should be apps on the play store that automate this process. Simply take a video again, try to play the broken video, then get your logcat/dmesg and upload them here
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] ankith7:
if this helps
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
So leerme test my amateur log reading skills, you're using MX camera, and trying to play back the video on the inbuilt media viewer, somehow the app registers a stop media playback event but the stop audio comes way later, it seems to be an app bug.

have you tried to play back the video on a different app? Maybe Google photos or another gallery viewer? Does tve bug is present on those apps as well?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
The problem about the headphone detection still remains

I have to reboot to make the speakers sound after disconnecting the headphones
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] ankith7:
changing player doesn't help. by the way i can play other videos just fine, only the videos which were recorder on this phone are causing this issue.

I've attached the log when i try playing video on google photo.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
So maybe the problem is with the recorded file. Maybe there's something with the file stream that detonates the stop playback event, it's pretty hard to know which part of the puzzle is causing the problem. Any luck with other camera apps like a better camera or moto camera? Are you using a custom kernel? As a last resort, have you clean flashed the Rom?

---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------

I've read somewhere that flashing the latest squid kernel solves that problem, but then you're back in square 1... Any luck with other kernels? Maybe SomeFreak's do the trick for you
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] jasonmerc:
SF kernel does the same camera thing that squid's does unfortunately. SF is actually based on squid's sources, so chances are if something's broken with squid kernel in general, it will also be broken with SF
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] el_figurin:
Same here, I'm on the January 10 build.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Randy Power:
Yes, same here. The volume in phone calls for both handset and speaker are both stuck very low. Pressing the volume buttons pops up the volume indicator which visually changes, but the actual volume of the call doesn't change.

The speaker hardware is fine, as media work correctly.

This problem started with the 12/27 build.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
Ofc, but the current SF kernel is based on a previous build, perhaps I should've recommended a previous build of the kernel since that was my original intention XD
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Sharath356:
Sai Sharath:

Guys. i was on LOS 14.1. I found a weird bug. I can lift calls but I am unable to listen voice of others. I have to use earphones everytime for phone. Any solution to this?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Onyx0099:
Unfortunately it won't solve it like I said before(and yes with the latest squid kernel one) it will make the camera not work so I'll stay with this small problem for now besides its not a permanent problem you just have to reboot it but doing it every time if you're using headphones a lot its a little annoying doing the same trick to solve it.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DXTN1:
Not a little, it's super obnoxious and it gets boring fast, try rolling back one or a few releases till those bugs get solved, in the state of the matters one can't do much more
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] hp420:
Any time I update via the official OTA channel, I get a com.android.phone fc message loop. I manually installed the lineage 14.1 com.android.phone apk from apk mirror, and it seems to have helped some, but I still occasionally see these messages while I'm using my device, no matter what I am doing. It's incredibly aggravating. Anyone found a solution to this? I've reflashed and updated about a half dozen times and the symptoms return exactly the same every time.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Bit of a wag: try clearing contacts storage (usual method from settings). This has worked on other devices for whatever reason. FC typically occurs during contact sync on those devices/ROMs.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Alan Max:
Does this ROM work on Nougat's updated bootloader?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] hp420:
wasn't able to fix it, but thank you for pointing me in the right direction. i just turned contacts sync off and that did stop the messages, at least.

yes
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
You may have to force stop the contacts app to execute a complete flush. Or go the easy route and manually sync on the schedule of your choosing. As a bonus you'll score a slight improvement in battery life, especially if other syncs are also disabled. Downsides are obvious if you use multiple devices or add/update contacts frequently.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Hopscotch Willie:
I have also experienced this a couple of times. But I don't know how to reprocuce it reliably. The problem started with the 171227 build.

There is a report on the bug tracker which got closed as a duplicate for semi-plausible reasons.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] takoa:
El volumen de llamada es muy bajo, se corta la conversación con el oyente y en modo manos libres también.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] jasonmerc:
They can tell. I think it has something to do with the TTL (Time To Live) with the packets being sent from the phone. I read about this a few years ago, I'll see if I can find the article again.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] mkollersms:
I'm posting this here, due to all of the confusion we've been having with the Verizon/USCell/otherCDMA SIMs not being recognized correctly.

"As stated in PCMag back in 2015, "Nobody makes a Dual-Sim phone compatible with Sprint or Verizon." It legitimately believes your MEID is a GSM-based IMEI, and is attempting to cross the streams, so to speak. And the only way your friend's StraightTalk SIM would work is if it was piggybacking off ATT or TMo's networks (the MEID would have been paired to the other phone causing a mismatch).

If you look at the stock ROM for this phone, you will see a BUNCH of system apps for programming Sprint and Verizon network information. They never made it into the custom ROMs we're using. FWIW, here's my thoughts on the matter. Someone needs to go back and make a single-SIM variant of these ROMs, as well as a flashable ZIP containing the necessary APKs for Android to detect the necessary information correctly. And if that doesn't happen, then everyone who bought an XT-1607 has to ditch their carrier and move to a GSM carrier."

Now, when we were discussing this, I made a note to pull the battery from my phone and look at the sticker. Unfortunately, the MEID is not printed there, so the only way I'd be able to see what mine was in the first place would be going back to stock (and I remember it being there on the stock ROM when I bought this phone). Perhaps if we found another way for the ROM to retrieve it...?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] PatC11:
Here's a weird one. A pair of Bose QC 35s has no trouble pairing or connecting with Bluetooth, but the audio signal doesn't switch to the headphones unless Bluetooth is turned off and back on.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] mkollersms:
Same with my Moto Surround, and I pair that using the supplied Connect app. What I've noticed is there's a delay from the time it says Connected to the time the OS shows the Bluetooth Volume. It's almost like you have to wait for that to be shown to know the device is paired correctly. Additionally, sometimes the OS and headset volume won't sync and the device will have to be reconnected to do so. Though all of this may be a Stock Android problem.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] ProudlyTM:
I don't really know to be honest :D
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] lem22:
Does this same ROM (and recovery) work for all different models (XT1607, XT1609, single/dual SIM, etc.)?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] YitzhakStone:
100% CPU usage

I had a issue: 100% CPU usage (all CPU threads), lasted about 15 min.

I tried to kill some apps, but it was still 100% until reboot.

What can I do to catch logs?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] jasonmerc:
https://play.google.com/store/apps/details?id=com.bassel.andylog

Use this to capture logcat and kernel dmesg logs, if that's what you're looking to do.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] MacBez:
Does it work for the XT1603?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] YitzhakStone:
I tested, works fine!

But I'm now using Mokee (https://download.mokeedev.com/?device=harpia)

I used when I had a RedMi2, and I liked too much.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] mkollersms:
Question about the build.prop file. It lists a directory device/motorola/msm8916-common/system.prop which cannot be found through the root file manager. What and where is it, exactly? Is there a way for us to get inside it and modify it?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] jasonmerc:
I think that's someone's github repository directory.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Doug Shuuyo:
Does it work for the XT1601? Actually, this ROM is a default rom for all the Moto G4 Play models/versions?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] thanhvx:
My device is xt1601 and this rom works on it.

---------- Post added at 08:09 AM ---------- Previous post was at 07:32 AM ----------

With nightly built feb 06 I'm having bug:

*** when open bluetooth setting, after few seconds the phone is restarting itself. I cannot connect any bluetooth device.

Does anyone have same issue?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] mkollersms:
Not the same issue, but Bluetooth has been a consistent problem. On all builds, the moment I pull into my driveway, the bluetooth switch turns off by itself, as if some other signal is interfering with it. I had one instance where a call on Bluetooth froze and rebooted the device (similar to your situation). The Motorola Connect app crashed several times, though a new update added Nougat support. Also, the volume occasionally desyncs and requires re-pair to fix.

My only real recommendation would be a reinstall of the ROM or wait for the next nightly. I'm not sure if fastboot-erase will work for a bluetooth chip the way it does for a gps chip.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] thanhvx:
With AOKP rom, especially with recent builds I don't have a single bluetooth problem.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] rafaelrgi:
Does someone installed this rom on a device with Tv and got the Tv working? How?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] spiked_mistborn:
I've been having an issue with the Bluetooth connection for my car simply disappearing from the list of Bluetooth devices. Just gone. It's happened 3 times so far. I have to re-pair it, which is a pain navigating through the car menus. I did grab a log right after it happened though, so when I get a chance I will update this post if I find anything.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] mkollersms:
It's possible BluetoothShare APK is corrupt. Try clearing the data and re-adding your devices?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] rorshaack:
Any prediction for the application of themes in LineageOS?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
[MENTION=1813028]takoa[/MENTION] - all XDA posts must include an English translation. I included that below:

"The call volume is very low, the conversation is cut off with the listener and in hands-free mode also ..."
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] hp420:
https://xdaforums.com/g4-play/themes/mod-moto-g4-native-volume-boost-t3566205

worked for me. i've since switched roms because i was finding an enormous amount of bugs on lineage, but the volume mod worked for me
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] FallenOcean:
* "and also in hands-free mode" hahaha I speak Spanish (Latin America), a little correction :good:
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Randy Power:
Hooray! Today's build restored the ability to change call volume, both in the handset and speaker modes.

A million Thank Yous to the devs
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] HlebK:
For avoiding bugs, try to flash the latest Squid kernel r22b, it fixes camera bug as well as a bug with a sound loudness. Since the latest release release I've been used it and didn't find any bugs.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Dark98:
how would I debug the device not entering deepsleep? It works fine on all the 2gb ram variants but with XT1604(1GB/NFC variant) it doesnt enter deepsleep with any custom ROMs while running any kernel(stock los & custom) but the device enters deepsleep fine on stock rom with stock and custom kernels
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
The ability for any Android device to enter deep sleep is kernel dependent and requires cooperation between kernel and ROM. As the XT1604 variant is less popular it is likely custom kernels and ROMs have not been optimized for that config. Suggest sticking with stock kernel and trying a generic ROM such as AospExtended. If the problem persists you may be stuck with stock everything which isn't horrible if embellished with a few Xposed tweaks.

No - I did not directly answer your question as debugging deep sleep issues is a bear - especially given custom kernels offer no relief and the somewhat less popular hardware config.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Dark98:
I don't get how using aospextended would help me because from what I can tell its a ROM bug because using custom kernels on stock ROM the device enters deep sleep fine
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Sorry - missed that last part (ok w/stock ROM and custom kernel) but doesn't change the suggested path. So why would you not want to test with AEX as it is probably the closest to stock of all the variants posted for this device? Moto ROMs are close AOSP clones as is AEX. LOS makes more extensive tweaks despite its AOSP heritage.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Dark98:
Installed AOSPEX and the device still doesn't enter deepsleep with any kernels at all(stock aospex/custom kernels/official stock moto 7.1.1)
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
So back to original answer - might be 'stuck' with stock Nougat which is both clean and feature complete. Really not so bad - especially if you install Xposed Framework and a few key modules (eg: GravityBox) which opens the door to many of the enhancements offered by custom ROMs.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Dark98:
But with xposed the device doesn't pass safetynet tests I use quite a few apps that require this passes
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Then it's Moto's Nougat in a birthday suit which isn't a bad shake all things considered (many a stock ROM has been butchered)! Unless you can convince one of the ROM custodians to look into your situation which seems unlikely since most have a different handset variant.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] borisboing:
Exactly the same issue for me with the xt1604. Stock sleeps fine, but any lineage 14 based ROM doesn't.

It isn't my main device and I have a need for API24+ on it so I can live with the lack of sleep, but it would be nice if it worked properly.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Suggestion: install Greenify (w/Xposed framework if possible) to help identify and potentially hibernate apps and services that may be blocking deep sleep. Greenify also includes a handy widget that attempts to force sleep; give that a whirl. Also consider tools like BBS and GSAM which can provide additional insight to screen off behaviors. If the culprit(s) can be identified ROM maintainer's may be able to find workarounds.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Orjakone:
Personally, I recommend that when you see problems, open in the jira, which is the official channel for reporting bugs and problems.

I believe that there is nothing much to report a bug here, developers can help directly from there and explain.

I think the developers who keep LineageOS can not help here.

https://jira.lineageos.org/projects/REGRESSION/

Just remembering that I'm not talking like debauchery or something.

I reported a problem and Squid really explained what I needed to do to help figure out what the problem was and how to help resolve it with the log.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Yes - this is the correct path for those who really want to get their hands dirty assuming the bug/issue has been previously reported and garners sufficient attention given limited scope. At present it only appears to impact one variant of the broad G4P family. Also note problem (as reported) is not confined to Lineage. That said, if someone like Squid does take an interest then the effort might yield favorable results.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] CarterCox:
The servers are down since yesterday at least. Any ideas on how to use a mirror to download the ROM?