Database Users

Horrible Stutters and Freezes on New Replacement Device

I got a replacement device with stock rom recently and it suddenly started to experience stutters, lags and freezes frequently. For example, I'd be typing on the keyboard and suddenly everything stops responding. It happens in Chrome, randomly whenever I'm using the keyboard, and basically throughout the rom.
One solution is for me to wait 2 minutes and it might suddenly start responding. But the only sure solution that always works is for me to lock and unlock the device a few times (using the power button) and everything goes back to normal for two minutes until it lags and freezes again.
Thoughts anyone?
I had all the same previous apps on my previous Nexus 4 and had no problems....

RMA karma.......
........

These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.

This happened to my nexus 7. I had it for about a month and i noiced that it started lagging really bad. Watching a video was just horrible and the responsiveness of it was bad. I just thought that it was a app or the custom rom i was running. I factory restored it and locked the bootloader and it still lagged. I just RMA'd it and i got a new one that was much better.

wideasleep1 said:
These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.
Click to expand...
Click to collapse
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.

montrealguy said:
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.
Click to expand...
Click to collapse
Yeah..if it's acting up after a Factory Reset, then no amount of fiddling will solve it. Sorry man!

[Q] Phone sensors unresponsive for a few secs when receiving call.

Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!

I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app

Android wear & MM

Hi
This is really a warning to anyone who has an Android wear (or probably any other kind of smartwatch)
My Gear LIve and LG Watch R worked perfectly with KK and Lollipop but with MM 522 it just would not work properly at all
i worked with a dev of one of the apps and it was only the Huawei with MM that caused any problems and notifications were just not getting to the watch
MM on a samsung worked no trouble and going back to 5.1.1 on the M7 again worked perfect
I liked MM but i didnt see that much difference to being worth keeping without the watch
So if you are planning on Upgrading and have a smartwatch then you will have issues
I am now back on 5.1.1 and rooted and all works fine

I have Asus ZenWatch 2 and it works with B522 properly. Only issue I have noticed is infrequent unconnecting, about twice a week. But I just run Android Wear app and watch is connected again.

I must admit I'm surprised that's is working OK for you add the tests we got when trying to resolve the issues were all down to huawei and the non standard calls they make and the permissions issues that were occurring
The doze feature in mm seemed to be conflicting with huawei's own features and stopping a lot of the notifications getting through even though those apps were set to protected.
It also seemed to be an issue with 1 app calling another appointment and again even though that permission was granted it still gave us issues.
But I suppose in the end every setup is different and in all honesty I don't think mm was a great step up grim lollipop anyway or at least not on the huawei
Sent from my SM-N920C using XDA-Developers mobile app

I have a Samsung Gear S2 Classic and since I installed MM on my MT7-L09, Samsung Gear app will not not load, it just opens and closes in a flash.
The only way to make it work is to switch off the Bluetooth on the phone, then open the Samsung Gear App, and press connect from the app. This will switch the Bluetooth back on, connects to the watch and the app works.
Weird and very frustrating until I figured out a workaround!
Sent using Tapatalk

I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?

sthentic said:
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
Click to expand...
Click to collapse
I've got the first gen Moto 360. when I updated to MM my watch at didn't receive any notifications (even the test ones). I did a factory reset and everything works fine now. The only issue I have is that sometimes the Gmail app pushes a ton of notifications for the same email.

Touch Screen Sensitivity Issue

Hi all,
I just got an S7 as an insurance replacement, and the touchscreen has been very inconsistent when scrolling through web pages, apps (Facebook, Twitter, Tapatalk), and even the launcher.
Scrolling through these sites, the page jumps ever so slightly, but it's enough to give me a headache after 20 minutes. Typing works just fine, though.
Before I call to get another replacement, is this a known problem with the S7s? Or did I just get a bad refurb?
- I'm coming from a Nexus 6
- I searched the forum
- Running stock Nougat, not rooted or modified
- I performed a factory reset after Nougat update, problem still exists
Thanks!
Sent from my SM-G930V using Tapatalk

Problem with Moto G 5 Plus Haptic Feedback

Hello everybody. I'm having an annoying issue with my Moto G 5 Plus wich started recently.
Sometimes when I'm using the keyboard, the low vibration every key does instantly deactivates, including the response of the fingertrip sensor (it still works but it wont vibrate too). After a couple of minutes or hours it starts working again as it should be.
I have the Amazon Ads & Offers version, so I cannot root it yet, I think, and I'm pretty sure its a software issue, as I've seen more posts of the same problem in the Lenovo forums.
Using the phone on secure mode havent presented this problem yet.
Any advice or solution?
Thanks in advance.

Alucardgab said:
Hello everybody. I'm having an annoying issue with my Moto G 5 Plus wich started recently.
Sometimes when I'm using the keyboard, the low vibration every key does instantly deactivates, including the response of the fingertrip sensor (it still works but it wont vibrate too). After a couple of minutes or hours it starts working again as it should be.
I have the Amazon Ads & Offers version, so I cannot root it yet, I think, and I'm pretty sure its a software issue, as I've seen more posts of the same problem in the Lenovo forums.
Using the phone on secure mode havent presented this problem yet.
Any advice or solution?
Thanks in advance.
Click to expand...
Click to collapse
I have the same problem. It restarts working if I use one of the Moto Action, for example camera gesture. Sometimes also restart working randomly, as you said. But I've searched some fix, but I didn't found nothing. I'm on potter_n (European model with NFC) so it should be a software bug, but it happens too randomly to say this :/
The only probable cause could be the hot weather of these days.
Did you found something?

Same issue, rooted .

It's probably an issue with the haptic motor. I've had this issue for the past several months, both on stock and custom ROMs. From what I know, it's not an uncommon issue on Potter.