I've found that screen taps often don't register when (for example) trying to move a text insertion pointer or click a hyperlink.
I've not been able to enter recovery mode. I've googled instructions but the phone always ends up booting as normal or into safe mode.
I'd like to disable the bootup jingle but can't find a way to do this. There was a setting to do this on my old Moto X Style. Google hasn't yielded an answer.
Any help with any of these would be much appreciated. Are these known issues? My phone is on latest 8.1 and April security update.
fishyweb said:
I've found that screen taps often don't register when (for example) trying to move a text insertion pointer or click a hyperlink.
I've not been able to enter recovery mode. I've googled instructions but the phone always ends up booting as normal or into safe mode.
I'd like to disable the bootup jingle but can't find a way to do this. There was a setting to do this on my old Moto X Style. Google hasn't yielded an answer.
Any help with any of these would be much appreciated. Are these known issues? My phone is on latest 8.1 and April security update.
Click to expand...
Click to collapse
You can silence the phone before shutting it down, so that while booting up there is no jingle.
Sent from my TA-1012 using XDA Labs
Related
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Yes, most of them are common.
Capri72 said:
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Click to expand...
Click to collapse
Most of these are common gripes, none can be corrected natively, but some can be corrected through different Rom's and such.
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
ripped85 said:
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
Click to expand...
Click to collapse
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
That opens a big can of worms.
simms22 said:
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
Click to expand...
Click to collapse
MMV, but the update should make things more definable. What apps a user may have and whether or not they are updated to work on lollipop should not be such a drastic issue, In a perfect world, Google should provide for backward compatibility or come out with a whole new version of their operating system; I.E. Windows 7 as opposed to Windows 8.
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
[email protected] said:
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
Click to expand...
Click to collapse
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
runekock said:
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
Click to expand...
Click to collapse
Sorry lol had to hook it to laptop and run Nexus toolkit
So I'm on 5.1 stock and this is really annoying me now. Wi-Fi switches off randomly when screen is off. Wi-Fi always on is checked. Any suggestions?
Sent from my XT1095 using XDA Free mobile app
Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?
I'm also having this problem. My wifi is configured to aways on, I'm not using any battery saver and even initialized my device in security mode, but the problem continued, so it is not a 3rd party program problem. I even posted on official Motorola forums (and on a lot forums through the internet), but no one could help. I guess it is a bug on 5.1 because I didn't have this problem on 5.0.
I installed a program to solve this problem, but it needs to keep running:
https://play.google.com/store/apps/details?id=com.roamingsoft.manager
Use the wifi repair option. This is the only way that I find to solve this problem. I hope they fix it on the next version.
Sorry for my english.
muiriddin said:
Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?
Click to expand...
Click to collapse
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app
pulley06 said:
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).
I can confirm this. It is as if the Wifi Always On setting did not work. When screen sleeps, 3G/LTE kicks in. When you wake the phone up, it'll go from 3G/LTE to Wifi. This has indeed arrived with 5.1, as 5.0 did not have the issue.
muiriddin said:
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).
Click to expand...
Click to collapse
Yeah it only occurs when the screen is off. The minute I switch on the screen I can see that it goes from mobile data to Wi-Fi even if Wi-Fi is on. Also, it is irrespective of where my phone is pocket or on a table top.
Sent from my XT1095 using XDA Free mobile app
I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...
I have an XT1095 stock 5.1 un-rooted, and I do not have this issue. I remember reading a similar thread here when 5.0 came out, so this is not a problem specific to 5.1. I don't know what is causing it, but it is clearly not a universal problem.
muiriddin said:
I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...
Click to expand...
Click to collapse
Don't have root. And have never rooted the device either. Somehow I'm just massively dissapointed with 5.1
Doesn't seem like a finished product at all. Battery life has plummeted from 3.5-4 hours sot easily to barely making it 3 hours
Sent from my XT1095 using XDA Free mobile app
Had this problem suddenly in 5.0 and continued in 5.1, the only fix was back to 4.4.4.
This has been posted before.
http://forum.xda-developers.com/mot...d-5-1-bugs-t3075232/post61724472#post61724472
http://forum.xda-developers.com/moto-x-2014/help/wifi-off-phone-idle-sleeping-t3053603
Here is the link to Motorola Forums that I've posted:
forums.motorola.com/posts/791e7e30c7
Hopefully this bug gets fixed in Android M.
Same problem that I'm getting. I'm sending mine back to Motorola and you guys can try that too to see if they can fix it. Apparently there's a speical dedicated team working on Moto X faults in Germany.
Anybody have any news?
Is there a way to fix this problem without going back to 4.4.4?
Hey guys,
I have a weird issue with my Moto X 2014 (stock Lollipop, no root or anything), and I can't find anything helpful around the web.
I have a video of the issue - I can't post the link as I don't have enough messages, but go to vid.me and add this code to the URL: /tMXf
Basically every few days, I find the phone is on vibrate. The volume rocker is suddenly all the way down, even though it should be maxed out, and I can't physically turn it up as you can see in the video. Even in audio settings, the ringer options is greyed out.
Android's quiet hours setting is NOT active. I have Moto Assist set to kick in at night time, but this happens randomly during the day, plus I tried removing it but nothing changes. It's not something to do with calendar events silencing the phone either, as Moto Assist only has scenarios for driving and the aforementioned night time.
Anyone knows what could be happening here? Thanks, much appreciated.
That IS strange... Have you tried rebooting your phone?
cole_15 said:
That IS strange... Have you tried rebooting your phone?
Click to expand...
Click to collapse
Thanks for the reply, man... yes, of course I tried that, but it's definitely not a temporary glitch. It happens again and again, every few days. A reboot does fix the issue when it occurs (in fact, it's the only way to get sound back), but only until the next time.
Just bought my first Nexus phone yesterday used of Amazon. Worked fine for the first hour then was prompted to update to 5.0.1. After the update the phone display will turn off randomly for a second every 5-10seconds (display turns off (not dims not locks). Dose not happen in bootloader and still happens even after flash installing 6.0.1 and Android N. The issue only happens for the first 20-30min after boot. It almost seems like an application that only runs the first 30min after boot is crashing the phones gpu. Anyone had this issue or have any insight?
Play store: Advanced Task Manager.
With this app you can kill apps.
You can select which apps.
Maybe you can find the cause
NLBeev said:
Play store: Advanced Task Manager.
With this app you can kill apps.
You can select which apps.
Maybe you can find the cause
Click to expand...
Click to collapse
Tried this and it didn't stop it. Even tried booting in safe mode. The issue happens even before Android loads up (during the splash animation).
Defective phone
Sent from my Nexus 6 using XDA-Developers mobile app
Jcssk said:
Tried this and it didn't stop it. Even tried booting in safe mode. The issue happens even before Android loads up (during the splash animation).
Click to expand...
Click to collapse
I agree with the previous poster (Mike... ).
If you can't find a software cause, it may possible a hardware issue.
Some hardware problems are temperature related. Shutdown and cool down the phone.
A few minutes in the freezer. Than restart the phone.
Hello,
So I noticed this issue and the local live chat support failed to help me and the only thing suggested was a factory reset.
The Unlock with S Pen Remote" option on the Note 9 is a bit buggy. First, whenever it's on, your phone can be unlocked bypassing every security you've set up.
Having this issue since the day I own it and it's not fixed via the November update. Also it's not related to the Google's Smart Lock.
The second thing about this is the menu which can't seem to be able to save the chosen option. Here is a video of what I am talking about.
https://imgur.com/a/jT82AF9
For long time I was looking for a way to disable it and after one reboot I finally did it and now I cannot turn it back on. Apparently there is almost invisible "OK" button
Trying to figure out if anyone is having the same issues.