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!

Annoying little bugs in 4.3

OK guys. Enough for me.
I've been pretty happy with my Nexus device since 4.2. Despite very few minor bugs it had been running absolutely fine.
Then the 4.3 update came and totally, pardon my French, sc***ed everything up.
First of all, the overall experience. Scrolling got much smoother for me. Secondly, that's all.
What got 'broken' was definitely the overall smoothness of the UI. For example, when I click an option in the Settings menu, it takes much longer time for the bluish color that indicates the click to disappear. It isn't only in Settings though. What's more, the click sound is somehow 'laggy'. What I mean by that is when I click something there's a noticeably greater amount of time needed for the sound to be triggered than it was in 4.2.2.
Also, the widgets drawer looks just bizzare for me. Some strange black boxes started to appear since 4.3 update (attachment).
Today, the stock YouTube app got unbearably laggy when scrolling through the list of searched movies.
But today Android has gone full retard. Just look at one of screenshots in attachments; surprisingly enough, the YouTube widget thumbnail looks like... the volume slider!
I've tried clearing data, cache, force stopping the YouTube app, even uninstalling it and going back to stock (+turning it off completely). If I go to stock app, then the thumbnail is fine. But as soon as I update the app... the same thing happens.
Also, while writing this, I noticed that my phone discharged by around 4% despite being plugged to a charger (in AC mode).
Seriously, this isn't an experience I was expecting from a Nexus device, a phone that should be a model for any other Android smartphone.
I wish I could go back to 4.2.2.

It's possible to go back to 4.2.
You just need to download the factory image from Google and flash with fastboot.
But you might try a factory reset before that to see if that solves the problem.
Swyped from my Nexus 4 using Tapatalk 4

Bump.
Really no one has ever seen such a bizzare OS behavior?
Also, I am not in favor of wiping my device as I have lots of precious personal data stored in it.

I think also that a factory reset may help you.
I think that something went wrong with the update.
Inviato dal mio Nexus 4 con Tapatalk 4

WhatsApp card notification

My Moto360 has started not displaying a card notification when receiving a message via WhatsApp. All other notifications are vibrating and switching on the display with card, but WhatsApp it just vibrates.
I have tried uninstalling and re-installting whatsapp, tried re-syncing the apps, but WhatsApp continues not to switch the screen on ... any ideas?

You haven't blocked whatsapp from showing notifications on your 360? Its easily done by accident. You might have swiped then clicked on block this app. If you go into your wear settings, then blocked apps, check to see whatsapp isnt there.
Sent from my SM-G920F using Tapatalk

Nope, checked that .. nothing in the Blocked Apps. The phone vibrates, so it is getting the notification, but unlike all the other apps which vibrate and switch the screen on, this just vibrates. When I wake the screen, the notification is shown

Yeh, sorry, when I re-read your post I realised you couldn't have whatsapp in the blocked list if you are getting the vibration. #facepalm ?.
I had a similar issue with not receiving cards for my outlook work emails on a different device to my 360 a while back, it turned out to be an app I had used to set a custom vibration pattern for my outlook notifications. Im guessing that if you had a similar app installed you would have checked that.. also Im sure you would have tried a restart of your 360..
I think the problem is with your 360 as your phone is clearly pushing the notification to your 360 if you are getting the vibration. I know an app resync usually fixes most issues but as you've tried that what about a factory reset of your moto 360? I know its a bit drastic but I don't know what else to suggest.
Sent from my SM-G920F using Tapatalk

Tried a reset as well ... the funny (annoying part), is that the screen on notification did work for a while, and then just suddenly stopped, withouth me installing anything, so not so sure it is an issue with the Moto 360, as all other notifications pop up ..... WhatsApp is the only one that does not

Yeh thats really odd. Maybe someone else will have a suggestion that can fix it. What version of the 360 do you have? Ive got the smaller mens 2015 version. I'm at the end of my tether with it tbh for other reasons. The lag on the the device is so bad for me its virtually unusable by the end of my working day. Im gonna sell it and get the watch urbane instead.
Sent from my SM-G920F using Tapatalk

I have the 1st Gen, and to be honest I am more than happy with it, even with the outdated processor in there, don't really get that much lag with it .... and taking it off charge at 7 in the morning, and putting back on around 10pm ... still gettng about 40%+ battery left.
Surprised the 2nd gen (2015) version that you are having lags with it, have heard it was supposed to be rock solid
What other issues you having?

I get "android wear has stopped working" at least twice a day. Which means it can crash without me knowing so i miss notifications and calls throughout the day. Thats my biggest gripe at the moment. Then the lag progressively gets worse throughout the day, the only way i can fix it is to do a reboot but at its worst it can take 2-3 minutes for me to get into settings then another few minutes for each option in settings to load before i can choose restart device. I tried a factory restore last night but its already crashed 3 times today..
When i compare it to my other smart watch my 360 doesn't have that 60fps smoothness when navigating the interface. I did read that if you disable ambient then the lag isnt so bad but i like having ambient on.
I'm planning on making a YouTube video of how bad it is over weekend.
Sent from my SM-G920F using Tapatalk

I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid

albie999 said:
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
Click to expand...
Click to collapse
Thanks for the reply. I think I'll try out your suggestion now. Need my watch working, I've come to really rely on my watch for notifications as I can't have my phone on during working hours. It got so bad today with the lag and crashes I had to use my Razer Nabu instead of my Moto360.
Fingers crossed, I'll let you know how it goes [emoji106]
Sent from my SM-G920F using Tapatalk

The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you

albie999 said:
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
Click to expand...
Click to collapse
As the moto 360 2015 doesn't have a cable, its wireless charging only, how would you reflash a previous version of wear? Im kinda stumped lol
Last night I did another factory reset and i uninstalled a lot of apps that i didn't want running on my moto. Some apps seem to have a companion wear app for their mobile equivalent that automatically install.. Well ive taken a lot of crap off and i have seemed to have fixed the stability issue. Also i can use my device albeit with a small amount of lag. This i can live with for now, it seems that moto knows about "always on" causing lag on some devices. I'll hold out for an update to fix it [emoji106] [emoji3]
Sent from my SM-G920F using Tapatalk

Ah, should have said .. it is not Android Wear on the watch, but the companion android wear on the phone that I installed an older version. Don't believe you can actually change the version on the actual watch
I have ambient mode off, wifi off (dont really see the point) and tilt to wake off ... as it kept coming on when I changed gear in the car lol

install quick for wear

i know it's an old thread, but i still have the problem in android wear 2.0.
whatsapp notifications are extremely unreliable. it's like the developers do every single thing their own way.
i set my watch to show notifications until i swipe it away or down, the very few times whatsapp actually shows the notification it goes away after a few seconds.
the notifications do work, as i can manually swipe to the notifications and they're there. they just refuse to show automatically.
i'm not a heavy user, so i get few notifications of which most of them are from whatsapp. so my watch functions more like a normal watch.

Whattsapp issues wear 2.0
I too get a buzz but no card till I manually swipe up anyone managed to fix this whattsapp support are useless auto gen email each time

Anyone having issues using Snapchat

Hello everyone, I did some searching on what I'm going to ask but it seems as though all I've read were due to rooting and pertained to logins.
I have a new Moto XPE running the stock Sept. 1st Patch. I can log into Snapchat just fine, my issue lies after I'm using the app. Messages won't load in Snapchat and stories become stock on loading as well. On some Snapchat stories that are loading, after looking at a few images, the screen goes black and is again stuck on loading. Eventually the app crashes and sometimes the phone will crash as well to the point where other apps like YouTube just won't open up and the phone will either reboot on its own or require one from myself manually. Has anyone with a Moto XPE or Moto X Play experienced any of the issues I've described?
Thank you.

Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?

jDally987 said:
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
Click to expand...
Click to collapse
It happened on my BlackBerry Priv too. I just switched over from that device a few days ago

I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that

iks8 said:
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
Click to expand...
Click to collapse
Yeah same here, it can get a little laggy sometimes for me but I just log out and back in and it works fine.

This might not be here nor there for this specific issue, but if you use Xposed/Snapprefs/rooted etc etc...One thing I noticed that REALLY causes a lot of lag with snapchat is overlays. Especially the FB Messenger app. If you have those chat heads on your screen with Snapchat open as well, things are basically unusable until you get back to the home screen and force close both apps. Could be happening without Xposed as well. Just a thought.
On a side note about Snapchat in general- it has always run like crap on every phone I've owned.

Snapchat kept screwing up, even tried the beta. Decided to try Casper and so far it's working great

S8 slow and unresponsive

Hey guys,
I don't have this phone, but asking for a coworker. His s8 suddenly just started becoming very slow and unresponsive this morning. He said the only thing he did was try to change his wallpaper and a Samsung wallpaper (or something similar, don't have the actual name of the app but it seems to be baked in by Samsung) app showed up in his app drawer. Just wondering if anyone else experienced something like this and had a solution other than wiping it.
Some more info, he just got an update but hasn't installed it yet. Not sure if this is getting Oreo already or if it's just the September security patch. I checked battery stats and it doesn't seem like there is a rogue app causing it to slow down, but I couldn't find ram usage for the life of me on the phone since I'm not familiar with Samsung's skin. Also tried restarting and letting it fully power off, waiting a few mins and then booting back up.
My guess it's samsung being samsung (the reason I don't buy them anymore but for all I know they don't break after an extended period of time anymore), but I've never seen a phone deteriorate that fast.
Any help is appreciated.
Edit: it's not rooted and the Verizon variant if that makes a difference