This is a well discussed and easy to fix bug... Disconnect USB cable, go to Settings, Apps, and Show System Apps and find External Storage and Media Storage and clear data and cache on each one and reboot, then give it 5 min after full boot up to rebuild media databases and connect to USB and select MTP. Should be good to go.
EDIT: In some instances where ...
I'll supplement the answer of @beeshyams: since Android O is still in Dev Preview phase, the source code is still incomplete, and no custom ROM (LineageOS, etc.) could even base their work off it. LineageOS (back in their CyanogenMod days) also stated time and again that they will not touch Dev Preview code.
To reinforce the fact: until Android O is ...
If Moto themselves did not update your device, there is no way you can obtain an authentic system image. Even when your device is updated, Motorola is very slow to update the latest image on it's website, and you would have to depend on images obtained through unofficial means hosted on sites like XDA
Related Security Patch level old on Moto G5
After about 4 hours of installing drivers, wiping data & cache of apps, wiping cache partition, etc...
I found the solution was just to change USB option from 'MTP' to Charging while USB was connected to the computer, then while still connected, change the USB option back to MTP once more, voila!
Edit: How to find the USB options may vary between ...
From what I can see in the video, the fluctuations are within about 1° in the first app, and 0.5° in the second. That's not exactly "random numbers in a wide range".
Accuracy within 1° is acceptable for most intended use cases: Mobile games, screen orientation, gestures, etc. It's quite possible that Motorola decided to use a cheaper sensor since the phone ...
This issue gets pretty clear by the second screenshot, which I will repeat here:
Battery usage (click image for larger variant)
Please pay attention to its lower half, just below the graph, and let me point out some details:
Mobile network signal: This bar has no black, which means the radio was on all the time. Further, the colors indicate a relatively ...
Well, there are two ways to fix this one out:
You need to have a custom recovery (CWM/TWRP) installed
You are going to require Stock firmware zip file for Moto G XT1028, XT1031, XT1032, XT1033 and XT1034 which can be downloaded over here
ADB and Fastboot
Boot your phone into custom recovery mode. Recovery will have adb on by ...
As beeshyams pointed out in comments, the software doesn't control which endpoint is the host and which is the peripheral: the hardware itself controls it. On a phone that doesn't have a USB-A port, you use a USB-OTG cable or adapter. This has a "host end" and a "peripheral end". (On the early USB-OTG cables, it was hard to tell which is which, but on an ...
Is it possible to have build.prop edited in these circumstances?
Unfortunately, no. Build.prop rests in the system partition and that partition is mounted as read-only by the Android. To edit the file, the partition has to be mounted in read-write mode, which requires root privileges which you are sure you cannot gain on this device.
That said, some of ...
You haven't mentioned if your device is encrypted ; if it isn't you are in bigger trouble. See this Why encrypt the device?
100% security is a pipe dream. Given enough resources, it may well be possible to use means available in public domain or those available to the letter agencies to get information out of your phone . Point is that you need to address ...
I just ran into this exact problem with a Moto G 2015. TWRP themselves warn not to install OTA updates with TWRP. Here's what I did:
Install the Android SDK or download fastboot separately
Get the build number for your phone
From TWRP on your phone go to Mount and make sure System is selected
Connect your phone to your computer and open build.prop with a ...
Follow these steps:
1-You can force close updater app:
Go to system-app-system updater then press "Force close"
2-uninstall updater app for the current user:
Note:You can restore updater app by doing "factory reset" to your phone?
pm uninstall -k --user 0 com.android.updater
Note:"com.android.updater" is package name of "updater" app in my phone,In ...
This actually sounds pretty normal to me. If this screenshot was taken shortly after you woke up then it would make sense for the OS to have used more battery, since the screen would have been off for a long while. I've owned several Android phones, having worked for Verizon Wireless before becoming a developer, and I've never had an Android phone that I ...
Good that you got the X Force instead of Droid Turbo 2 (Verizon's variant), that means your device is eligible for unlocking the bootloader and thus rooting relatively easily.
Unlock bootloader following here - all data including internal storage will be wiped, so be sure to back up.
Flash TWRP recovery here.
Flash a suitable SuperSU package in TWRP. Use "...
I believe it is the beauty mode
The 5MP front-facing camera adds one extra control to this menu and that is for beauty mode. There are three options: auto, manual, or off. The manual option lets you move a slider like most other smartphones that offer a beauty mode which blends the skin tones to hide imperfections
Also called beautification mode
Moto G5S uses LPDDR3 DRAM, which is volatile (cleared on power cycle) Random Access Memory which can be confirmed with an app like DevCheck, and a 32GB flash storage chip which is non-volatile high-speed electrically programmable memory that is common to most modern cell phones although sizes can vary widely.
Modern cell phones do not have a "ROM" or Read-...
As you've already found out, LineageOS has its own, built-in, lightweight SU solution (addonsu), which is the only one supported officially (the team does not adore Magisk/SuperSU).
Note that officially LOS only provides 14.1 builds for your device. Assuming that's the version you're running, using the addonsu for 15.1 you will naturally bump into problems. ...
First check whether you phone can be unlocked at: https://support.motorola.com/us/en/solution/MS87215
If yes then you need an unlock code to get this code and unlock the boot loader follow the instructions at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
It is not possible root your mobile without unlocking it.
Currently it's Android Wear 2.0.
According to news on Lenovo website, the Moto 360 Sport was in-line to receive this update (which was available sometime around September 2017)
One reddit user also confirmed to have received the update (Android Wear 2.0). So chances are that you can now download this update (if you haven't already) also if you want to.
Seems like your phone is soft-bricked. You'll need to hard reset it.
Begin by switching off the device by holding down the Power key for a short while.
In the next step press and hold Volume Down + Power button simultaneously for a few seconds.
Press the Volume Down to select option "Recovery", and press the Power button to confirm.
When the Android bot ...
To obtain original firmware -Sign in on Motorola / Lenovo (Motorola had been taken over by Lenovo) site with device details , creating an account and search for firmware
Edit: OP has confirmed that he is unable to locate on the Motorola forums as older devices firmware is apparently removed. It is suggested that he mail the OEM or in the OEM forums for sha /...
After a few days of research I discovered that the problem it is a conflict between some Android devices and some 3G networks. (In my case, in Brazil)
Bug report (English): https://code.google.com/p/android/issues/detail?id=81140
TecMundo News (Portuguese): http://www.tecmundo.com.br/vivo/102386-sinal-vivo-interferindo-gps-celulares-afirmam-usuarios.htm
Verizon uses LTE bands 2, 4, and 13.
Brazilian carriers appear to use 3, 7, 28, and 38. As such, you should by default expect US Verizon phones not to work with LTE in Brazil since there are no overlapping bands.
However, the Verizon Z Force supports bands 2-5, 7, and 13. So it's quite possible that it would work on some Brazilian carriers using bands 3 ...
I just hit the same issue. Check that you are using the microUSB cable that came with the Turbo Power charger. I had accidentally switched around my USB cables with a generic one, and noticed that my phone was charging slowly, even after reseating both cable connectors. When I replaced the generic cable with the original cable, it enabled TurboPower ...
Moto phones are quite close to Nexus phones or pure android as commonly referred to, so the explanation below is valid
See Android phone "charging slowly": How to make it faster, for reasons on why charging slowly is displayed, in particular Andrew's excellent answer. To summarise, fast charging/ Turbo charging is achieved by increasing voltage or ...
First of all, that's not a serious issue that may happen with any of the devices with touch display. I will not go in deep working of screens but the work with the potential difference generated by our touch or sticks/stylus.
The Turbo-Power brick which is bundled in the box is the culprit, (Only for those users who are facing ghost touch while charging.)
It's hardware issue. You can try different cables or chargers, or contact manufacturer if your phone have warranty. Sure you always can turn off screen when charging ant don't use phone until it charges, but it's uncomfortable.
It's a few months late but I just had the same issue on my Nexus 6p. If you're still having the issue and you're rooted I have a solution.
First thing yr gonna have to do is download this app scanCode from your selfie stick.
Run the app, press the button on your selfie stick, and it should show a scanCodein ...
It appears the software is broken out of the box and it cannot be fixed. It's trying to connect to the host www.mymotocast.com, but it can't find the path or there is no server listening:
$ openssl s_client -connect www.mymotocast.com:443
connect: Operation timed out
$ nslookup www.mymotocast.com