Related
Hello everyone,
I upgraded my Atrix 2 (AT&T, no previous mods) to ICS the other day and it has been nothing but problems ever since. Anything I tried to open (dialer, apps, menu's) would take 30+ seconds, some would never open. The Play store download are crazy slow. For example I tried updating Youtube and after 15 minutes it was at 18%. People would call and I would try to answer, but it stopped ringing long before it would actually try to answer. I was getting random reboots. I decided to do a factory reset.
Although it would boot fine now, it was still really buggy and laggy. Most apps take a good 30 seconds to load. The menu's seem to respond fine and so does the dialer. The play store is the exact same, painfully slow. It doesn't matter if it is Wifi or 4g. Although the web browser is slow to load, web pages load relatively quickly. It does stop responding every minute or so and takes a good 15 seconds to continue.
I turned on "Show all ANR's" in the developer options. When it boots I get a barrage of non responding apps/services for the first 10 minutes, then it slows down. I still get random ones though. Homescreen quite often and "com.motorola.process.system" not responding. I turned on CPU usage in the developers options, but I'm not sure what the information means or what is acceptable/unacceptable. I compared the values/graphs to my wife's ICS tablet and hers are much lower. For example:
My Atrix 2: 5.72 / 6.28 / 6.76 (graph is 1/3 of the way across the screen, most of it is blue, graph jumps around)
Transformer Tablet: 0.0 / 0.06 / 0.06 (graph is almost non existant).
Motorola support told me that I cannot compare the graphs because the 2 ICS versions are different enough that the values could not be compared. Maybe, maybe not. All they offered was for me to send the phone in. I'm searching the web like crazy, but I think that the update is new enough where there isn't too much content on the subject yet.
Anyone have any ideas on what I can do/try? Any tips on how to troubleshoot the problem?
Thanks
Dustin
Try a factory reset.
Sent from my MB865 using xda premium
tmease1 said:
Try a factory reset.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I tried several times (as mentioned) and although it was an improvement from the original update, it still performs terribly.
You said you hadn't done any mods. I assume you also did the official OTA update to ICS? In that case, I'd take the phone back to AT&T and ask for a replacement. If you're within the warranty period, they should honor it since you didn't do any mods/flashing.
MobileNick said:
You said you hadn't done any mods. I assume you also did the official OTA update to ICS? In that case, I'd take the phone back to AT&T and ask for a replacement. If you're within the warranty period, they should honor it since you didn't do any mods/flashing.
Click to expand...
Click to collapse
Your assumption is correct, it was the official OTA upgrade. If there isn't really anything I can do, then I might just take it in. Motorola wanted me to send it in but I can't be without a phone for 1 week +. Hopefully I can work it out at the store so I don't have to send it in.
It could be a rogue app. Do a factory reset and clear the dalvik cache too.then do not sign in to your google. See what happens.
Sent from my MB865 using xda app-developers app
In the initial days after the ICS OTA I faced a lot less severity of similar issue raised by you which does not occur now by itself but sometimes very rarely.
As a last resort charge up fully, since you are ok with factory reset do it once more & then reboot and ensure you do not touch any of the default developer options. Don't use any apps explicitly from your end at all besides your core dialler and mobile data/wi-fi (which will of course bring up any background syncs & programs associated with background data). After an hour's use go to running apps and post screen shots (if need be after scrolling down for additionally non visible programs on visible screen) & similarly do the exercise for cached apps & maybe it'll help someone more knowledgeable to give some inputs as it'll show exactly what apps initialize & are active by themselves. Also before all this, screenshot "ANR's" since you have it enabled at the moment and finally I assume you are non rooted (just to know).
RAD7 said:
In the initial days after the ICS OTA I faced a lot less severity of similar issue raised by you which does not occur now by itself but sometimes very rarely.
As a last resort charge up fully, since you are ok with factory reset do it once more & then reboot and ensure you do not touch any of the default developer options. Don't use any apps explicitly from your end at all besides your core dialler and mobile data/wi-fi (which will of course bring up any background syncs & programs associated with background data). After an hour's use go to running apps and post screen shots (if need be after scrolling down for additionally non visible programs on visible screen) & similarly do the exercise for cached apps & maybe it'll help someone more knowledgeable to give some inputs as it'll show exactly what apps initialize & are active by themselves. Also before all this, screenshot "ANR's" since you have it enabled at the moment and finally I assume you are non rooted (just to know).
Click to expand...
Click to collapse
Thanks RAD7 and cloudedhopes.
I went into the semi-local AT&T service store and they said that this is a known issue to them. They told me that they couldn't give me a new phone because all of their replacement Atrix 2's came in with ICS and they had to send them back. Supposedly there is a fix coming for it someday.
I will give your posts a shot here over the next few days and report back the results. Normally I'd do it tonight but it's also a business phone and I just need it to work for me until the weekend. Thanks for the help!
I failed to get screen shots of the running services. The only way I could see a way to do it was take pictures with a camera and what I had handy only took blurry pictures.
I have made some sort of progress though. I did as you guys said, wiped it and basically did nothing with it for more than an hour.
I connected to WIFI and checked the web browser, works pretty well.
I put in a clean flash card and loaded music, the player works fine.
I eventually added an my personal and work email accounts, they work fine.
Sync'd my contacts with AT&T, still working fine.
The dialer, text messageing, preloaded apps all work fine.
As soon as I launch the play store and sign into my google account, it all goes down hill. Everything gets super slow and most things I'm trying to do temporarily stop responding. I wiped it again, re-did everything last night except my google account and it's now working fine again.
dmroeder said:
I failed to get screen shots of the running services. The only way I could see a way to do it was take pictures with a camera and what I had handy only took blurry pictures.
I have made some sort of progress though. I did as you guys said, wiped it and basically did nothing with it for more than an hour.
I connected to WIFI and checked the web browser, works pretty well.
I put in a clean flash card and loaded music, the player works fine.
I eventually added an my personal and work email accounts, they work fine.
Sync'd my contacts with AT&T, still working fine.
The dialer, text messageing, preloaded apps all work fine.
As soon as I launch the play store and sign into my google account, it all goes down hill. Everything gets super slow and most things I'm trying to do temporarily stop responding. I wiped it again, re-did everything last night except my google account and it's now working fine again.
Click to expand...
Click to collapse
Since you mentioned Signing into Google play is issue, I am just thinking it could be because of the backup & restore option. Bu default Google allows to back up and restore your account. Its highly like you selected that too. There could some app which causing this issue. May be you can give a try without checking restore option....may not help out but just a thought...
That's a good suggestion sazhagianambi. I'll try that sometime today.
I let my phone run all day yesterday without signing into my google account. When I finally went to sign in I saw that check box... right after I hit sign in. I unchecked it, but I had already hit the sign in button so I think it was too late.
For taking screenshot, you have to press power & volume down button simultaneously. It works for sure. Google Play store is definitely acting slow on ICS but does not effect rest of my apps. I have noticed this whenever I update apps updates (I have disabled auto updates for all apps though & check manually) Everyone echoes the fact that do not go beyond class 6 SD's which is one thing you may want to consider (I am however using class 10 which is said to be a ticking time bomb & also it is mentioned never to install apps to SD card (which I do) but stay away from "Link2SD" & do not move apps marked with grey icon when it says movable. Avoid live widgets if possible. In any case it is recommended to reboot once in two days like how we do our computers to flush the ram and renew the system.
If yet your concern is so grave (& which it sounds) then by all means you should consider getting a replacement from AT&T if you are under warranty.
RAD7 said:
For taking screenshot, you have to press power & volume down button simultaneously. It works for sure. Google Play store is definitely acting slow on ICS but does not effect rest of my apps. I have noticed this whenever I update apps updates (I have disabled auto updates for all apps though & check manually) Everyone echoes the fact that do not go beyond class 6 SD's which is one thing you may want to consider (I am however using class 10 which is said to be a ticking time bomb & also it is mentioned never to install apps to SD card (which I do) but stay away from "Link2SD" & do not move apps marked with grey icon when it says movable. Avoid live widgets if possible. In any case it is recommended to reboot once in two days like how we do our computers to flush the ram and renew the system.
If yet your concern is so grave (& which it sounds) then by all means you should consider getting a replacement from AT&T if you are under warranty.
Click to expand...
Click to collapse
I eventually admitted defeat and called for a replacement. Unfortunately it showed up late and had to leave for a business trip. So I'm sure it's sitting on my porch right now. Oh well.
I appreciate everyone's input. I'm curious if it shows up with ICS on it or not.
I am experiencing the exact same thing on mine. I also felt that the Google Play store was the issue... so much that I uninstalled it and re-installed the newest version from an apk off the web. I swear my phone ran smooth for a couple days. I was pumped. But then, the slowness returned. It's horrible. I just 'froze' the Play store with Titanium backup, and will see if that helps. If so, I'll report back.
meeotch said:
I am experiencing the exact same thing on mine. I also felt that the Google Play store was the issue... so much that I uninstalled it and re-installed the newest version from an apk off the web. I swear my phone ran smooth for a couple days. I was pumped. But then, the slowness returned. It's horrible. I just 'froze' the Play store with Titanium backup, and will see if that helps. If so, I'll report back.
Click to expand...
Click to collapse
I wonder if anyone has been having success with the update. I'd have to assume yes since it's still available for download.
I got home last night and my replacement phone has Gingerbread. I'm thinking about rooting it and backing it up then trying the update again.
atrix 2 malfunction with ICS OTA
dmroeder said:
Thanks RAD7 and cloudedhopes.
I went into the semi-local AT&T service store and they said that this is a known issue to them. They told me that they couldn't give me a new phone because all of their replacement Atrix 2's came in with ICS and they had to send them back. Supposedly there is a fix coming for it someday.
I will give your posts a shot here over the next few days and report back the results. Normally I'd do it tonight but it's also a business phone and I just need it to work for me until the weekend. Thanks for the help!
Click to expand...
Click to collapse
Hi,
Did you say your local ATT retailer said there is a known "problem" with operating ICS on it...I have been soft bricked since the OTA update..I am not a programmer, and have been reading posts for weeks..overwhelmed. out of warranty, and moisture sensor positive, so I will get nothing from ATT, unless there is a recognized compatibility issue?
Anyway, If your retailer said so, maybe I can relay that to my local,
thanks,
Jason
slowprocessor said:
Hi,
Did you say your local ATT retailer said there is a known "problem" with operating ICS on it...I have been soft bricked since the OTA update..I am not a programmer, and have been reading posts for weeks..overwhelmed. out of warranty, and moisture sensor positive, so I will get nothing from ATT, unless there is a recognized compatibility issue?
Anyway, If your retailer said so, maybe I can relay that to my local,
thanks,
Jason
Click to expand...
Click to collapse
It was our local AT&T service center (Portland, OR) that said it was a known issue (the guys at the retail store knew nothing). He knew exactly what I was talking about and said that he had gotten an email a couple of days before about the update. He also said that he would have swapped my phone out right then and there but he had to send all of their replacement phones back because they came with ICS.
I wasn't sure if he was serious or just yanking my chain. I find it pretty hard to believe that it would be such a wide spread issue and the update would still be available. They did replace my phone though. My replacement phone has been reminding me of it but I've been ignoring it.
dmroeder said:
It was our local AT&T service center (Portland, OR) that said it was a known issue (the guys at the retail store knew nothing). He knew exactly what I was talking about and said that he had gotten an email a couple of days before about the update. He also said that he would have swapped my phone out right then and there but he had to send all of their replacement phones back because they came with ICS.
I wasn't sure if he was serious or just yanking my chain. I find it pretty hard to believe that it would be such a wide spread issue and the update would still be available. They did replace my phone though. My replacement phone has been reminding me of it but I've been ignoring it.
Click to expand...
Click to collapse
Who replaced your phone ATT or Moto? I am having the same issue
Gloatingfungus said:
Who replaced your phone ATT or Moto? I am having the same issue
Click to expand...
Click to collapse
ATT. They sent me a new one and I sent my old one back after it arrived.
So I couldn't take it anymore, I got the update bug. This time I got all my pics and contacts backed up, factory reset, then OTA and it works like a Swiss Watch. I feel much better being on ICS now.
All,
The 5 September update of Gear Manager caused my watch to continuously disconnect from my Note 3.
The only thing I could do was factory reset the Gear 2 and reconnect. However, restoring the backup failed as the progress indicator remained at 100% and never continued. The last resort was a full wipe and start from scratch reinstalling all the apps.
Gear Manager settings show that an old backup is still present but it is greyed out.
Anyone else had this problem?
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
All,
The 5 September update of Gear Manager caused my watch to continuously disconnect from my Note 3.
The only thing I could do was factory reset the Gear 2 and reconnect. However, restoring the backup failed as the progress indicator remained at 100% and never continued. The last resort was a full wipe and start from scratch reinstalling all the apps.
Gear Manager settings show that an old backup is still present but it is greyed out.
Anyone else had this problem?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm runing tizen mod 3.0 and my galaxy s4 running hyperdrive RLS 18.1. I am having the same issues but cannot figure out of its eithe rof my roms on the phone or watch. i did notice that this disconnect issue did not occur when I had the stock factory image on my gear 2. I thought it might be the roms. But now that you mention it, it may be the latest update with gear manager.
I'm hoping some savy developer or someone with more expertise on the issue can shed some light on this issue.
RJV3 said:
I'm runing tizen mod 3.0 and my galaxy s4 running hyperdrive RLS 18.1. I am having the same issues but cannot figure out of its eithe rof my roms on the phone or watch. i did notice that this disconnect issue did not occur when I had the stock factory image on my gear 2. I thought it might be the roms. But now that you mention it, it may be the latest update with gear manager.
I'm hoping some savy developer or someone with more expertise on the issue can shed some light on this issue.
Click to expand...
Click to collapse
There is an update that was released today as well, and of 9 reviews 7 of them state that it breaks the gear 2. But hey, they added support for the Gear S....
anmghstnet said:
There is an update that was released today as well, and of 9 reviews 7 of them state that it breaks the gear 2. But hey, they added support for the Gear S....
Click to expand...
Click to collapse
Thanks for the heads up. I was able to pull the old gear Manager apk file and did 4 factory resets on my watch and my phone to get the thing up and running again. Can't believe samsung would update the gear Manager and not do extensive testing if people are already complaining of it breaking gear 2 connection. [emoji19]
RJV3 said:
Thanks for the heads up. I was able to pull the old gear Manager apk file and did 4 factory resets on my watch and my phone to get the thing up and running again. Can't believe samsung would update the gear Manager and not do extensive testing if people are already complaining of it breaking gear 2 connection. [emoji19]
Click to expand...
Click to collapse
Any chance you could post the old gear manager apk?
I have TizenMod 3.0 and Saproviders stops, I can't get notifications on the gear anymore... Samsung is really making me lose patience :/
Edit : all due to today's upgrade.
Same here. Anyone else know if we can deactivate the automatic updating? I did my bi-weekly CWM backup just last night (lucky!) so I have no problem restoring but as soon as I reboot the damn thing automatically updates! I want to pull the sim out, do a restore, deactivate the auto-update function and just leave it as it is until there is a fix. I would try restoring from Titanium but there are like 9 additional apps that it either installs or updates after the new Gear Manager installs!
This may be late for some of you but this is how I get around the problems...
1) Before you update the gear manager app, make a backup of the gear manager apps with titanium backup. (all the apps associated with gear manager will have the same gear logo)
2) Then open the app and update the software
3) Once complete, confirm that your Gear watch is connecting and receiving notifications. (The easiest way to do that is send yourself a text message)
4) If your watch is not working correctly or not connecting to the phone, then go back into titanium backup and restore the Gear Manager app back to the backup you made in step 1.
5) Repeat steps 2 and 3 until it works.
I personally had to do this twice before it connected and I received notifications. For future updates this is the only way I would do it because it is such a glitchy application and I'm tired of factory resetting my Gear and re-installing everything multiple times.
I hope this helps someone!
Strangely enough this update worked fine for me. It was the previous update that messed all up here..
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
Strangely enough this update worked fine for me. It was the previous update that messed all up here..
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Was your watch rooted or modded?
Not this time. Reverted back to stock just to be sure after the problems of the previous update. Just had it rooted then though.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
Not this time. Reverted back to stock just to be sure after the problems of the previous update. Just had it rooted then though.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
So you used ODIN to revert to stock, rooted by normal means and then updated the Gear Manager and it worked fine afterwards?
I flashed stock with Odin and left it that way after the problems with the previous gear manager update. Before that I just ran stock rooted, no custom rom. The only reason I rooted was to remove the camera sound, but I don't use the camera that much on the gear.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
I flashed stock with Odin and left it that way after the problems with the previous gear manager update. Before that I just ran stock rooted, no custom rom. The only reason I rooted was to remove the camera sound, but I don't use the camera that much on the gear.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm thinking that this new Gear Manager update checks the watch for root access and won't let it connect. That's just my first impression anyway.
I removed root from my watch but kept TizenMod, re-paired the watch and it connected without a hitch.
I don't think root is the problem because most of the comments are negative and I doubt most people have their Gear rooted. I think it's a software issue because even before root was available there were plenty of people having issues with connecting and the software has not improved much since then.
alienmanam said:
I don't think root is the problem because most of the comments are negative and I doubt most people have their Gear rooted. I think it's a software issue because even before root was available there were plenty of people having issues with connecting and the software has not improved much since then.
Click to expand...
Click to collapse
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Gear manager update
Binary100100 said:
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Click to expand...
Click to collapse
I installed the new Gear Manager update yesterday and I thought all was ok. Its only when I came to load "Fitness with Gear" I noticed it won't sync anymore. Tried everything to get it to come back but its a no go. anyone any idea's on this or having the same problem?
Rich
xtermin8 said:
I installed the new Gear Manager update yesterday and I thought all was ok. Its only when I came to load "Fitness with Gear" I noticed it won't sync anymore. Tried everything to get it to come back but its a no go. anyone any idea's on this or having the same problem?
Rich
Click to expand...
Click to collapse
Hmm.
Perhaps it could be related to Fitness with Gear because I have it installed as well.
Binary100100 said:
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Click to expand...
Click to collapse
If it's an app I really like and support then I'll make a positive comment but I do also make negative comments as well. Root may cause some issues but before I had root I still had trouble with the app and had to factory reset multiple times just to get it to connect. I'm rooted and it still took me 2 times of trying to update to get it to work correctly. I think overall, Samsung did not spend enough time developing before releasing the Gear and Gear Manager. They're too busy pushing out a new phone every year and a new watch every 6 months.
alienmanam said:
If it's an app I really like and support then I'll make a positive comment but I do also make negative comments as well. Root may cause some issues but before I had root I still had trouble with the app and had to factory reset multiple times just to get it to connect. I'm rooted and it still took me 2 times of trying to update to get it to work correctly. I think overall, Samsung did not spend enough time developing before releasing the Gear and Gear Manager. They're too busy pushing out a new phone every year and a new watch every 6 months.
Click to expand...
Click to collapse
Agreed. This is definitely a poor job on Samsung. They did this **** just before the release of the Gear S? What a way to win hearts and minds. Think Apple will have these issues? I mean damn... the developers on this forum don't even have fails this big! When they notice that something that they developed doesn't work as expected they pull the link, fix the problem, TEST IT and then release it almost immediately. This is neglect.
Running totally stock on 5.1.1 (N920PVPU2A0I6). Starting about an hour ago I'm getting a pop-up saying "Bootstrap Failed...".
Phone is unresponsive and reboots by itself.
Thoughts?
late,
Coz
*EDIT: Factory reset didn't solve it.....correction, 3rd attempt at factory reset seems to have solved it. But I would love to know what initially caused the situation.
Same
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
Same
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
The only thing that updated/changed this morning was an update (I believe) for Sprint Zone.
late,
Coz
Well that didn't work....after about an hour of it running without issue, I'm getting the Bootstrap Failed... message again and it's restarting.
late,
Coz
Update....phone has been stable (no re-boots, lock-ups, etc.) for the past few days. I occasionally get the pop-up message stating, "bootstrap failed..." but it doesn't seem to impact the performance of the phone from what I can tell.
late,
Coz
Mine keeps doing it oh well
Sent from my SM-N920P using XDA Premium HD app
My phone just started doing this today. Also a Sprint Note 5. No software updates installed recently... most recent was the Sprint and Samsung updates for Samsung Pay, which I did set up-- but I did that day 1. Right before the problem started happening, the phone rebooted itself, and it hasn't been well since. I checked aLogcat, but nothing gets logged there. After a few of the "Bootstrap failed..." toasts, the phone just becomes unresponsive and I have to hard shutdown. The only thing that I can think of that I've done differently today was plug my phone into my laptop to charge it earlier. I don't think I'd ever plugged it into my laptop before.
Hopefully somebody can pin down the cause of the problem here. I'm surprised that aLogcat doesn't show anything, which makes me wonder if it's some Knox issue...
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
I'm curious as to why you suggest deleting that folder? What exactly will that fix? Details please before you suggest to a member to just delete something.
late,
Coz
The reboots i saw it mentioned.
Sent from my SM-N920P using XDA Premium HD app
Same problem, I have stock Sprint Note 5 with Samsung Pay updated and activated. Worked fine for a few days then all of the sudden I started getting "Bootstrap Failed" and my phone is unresponsive and/or data connection stops functioning forcing me to restart.
Is Sprint/Samsung aware of this issue and working on a fix? Very annoying. I've uninstalled all updates to Sprint Zone, force stopped and cleared data for Sprint Zone which appeared to help for a couple days, but now it's back again.
Has anyone had any luck with hard / factory reset? I don't want to go through the hassle of backing everything up, wiping it clean and reinstalling everything if at the end of the day it doesn't make a difference.
After a few more lock ups and reboots yesterday, my phone started behaving normally again, but just now I saw another "Bootstrap failed..." toast, so clearly the problem has not gone away. It hasn't locked up again on me yet, so maybe I'll be okay for a while. The only references I've seen to this error have all pointed to the Sprint Note 5, and most have mentioned Samsung Pay, so I suspect it's an issue there. Whether or not Samsung/Sprint are aware of it, I don't know.
I've also read it may or may not have something to do with Sprint Zone. I would agree it's purely due to the recent Samsung Pay update as I've had the Note since launch day and only noticed this after activating and updating Samsung Pay late last week. Before that I used the phone for nearly a month with no issues whatsoever.
While my phone hasn't locked up or rebooted by itself, I still get the "bootstrap failed..." occasionally.
I too think it was associated with the Sprint Zone and/or Samsung Pay update.
late,
Coz
I have only seen it once. Im fully stock to latest update. It happened to me after i noticed i had no data connection showed full lte but i had nothing opened up sprint zone and tried to refresh showed error. Then bootsrtap failed, have not seen it since
Sent from my SM-N920P
Bootstrap failed
It started happening to me after my fingerprint recognition failed, and I could not remember my backup password.
Just started happening to me a few days ago. completely stock sprint phone with the latest update (samsung pay). I noticed that right after the message PRL update began. After that and updating the profile, i havent seen the message.
Any updates on this? I went into Best Buy this weekend and had Samsung Experience store re-flash the OS to the phone, uninstalled Sprint Zone, uninstalled Samsung Pay updates, and force stopped Samsung Pay Framework. It worked fine for a few days but it started showing "Bootstrap failed" again. While it doesn't freeze up like it did the first time I received that message, in general the connectivity seems spotty (I'll show I'm connected to Wifi but nothing shows up on web browser or apps).
The problem is when Samsung Pay installed, it also installed an update to Android, and the Samsung Experience store in Best Buy can only flash the latest version of the OS. They can't revert back to the stock version of Android that came with the phone.
That's the biggest problem. Samsung and Google should make it so that they can revert back to a prior version of Android if the latest version has major bugs in it (which has been increasingly the case since Lollipop began rolling out). I had ZERO problems with the stock software/firmware that came with the device out of the box. Lesson learned I guess, don't accept an update if the version you have works well, until at least a couple months of the new update being out in the wild first....
Haven't seen this notice in a few days. It stopped after manual prl and profile update.
On a side note, I disabled the Samsung pay via package disable pro
Anyone figure this out?
Hello,
My step history for previous days does not show on the watch. I can only see the bars in the graph, but the numbers are 0. Current day is shown ok.
S Health on the phone is fine.
Tried resetting the watch and reinstalling S Health - doesn't help. Is this a known issue?
Hai,
I have the same problem. Resetting does not help.
How can solve this problem?
Same problem too since 2 days. I saw other people having the same problem on some other forums but no clue on how to fix this issue.
I spoke to Samsung support. They told me that this is how it's supposed to be, and steps history will only be visible in S Health. I call this bullsh*t...
dadonev said:
I spoke to Samsung support. They told me that this is how it's supposed to be, and steps history will only be visible in S Health. I call this bullsh*t...
Click to expand...
Click to collapse
It is BS. I'm currently looking at history on my S2 going back to 3/12. Nearly 3 weeks of history.
Why does it only go back to 3/12? Because that's the day all previous history was erased somehow. No idea how, but on 3/12 I was going through the same motions as the OP and other posters here: What happened to my step history? It's all still there on the S6. I tried resetting too, no dice.
It's a bug, folks. And Samsung is simply unwilling to invest ANY money in fixing bugs on the S2. They're working on the S3.
Guess I'm lucky as mine shows everything back to the day I bought it. Wonder what is different? I have the 3g version on Verizon.
Sent from my SM-G930V using XDA Premium HD app
Firmware probably. I'm still on XXU2BOKK which was issued in December (no airplane mode etc.). Wonder when the update will hit me as well...
I have the problem with R720 model on XXU2CPB7, so it must not be related to the firmware version. My feeling is that it's related to recent S-Health update I got last week-end.
i had the same problem a few days ago, tried everything even factory resets. today with the new firmware update it is fixed. (R720xxu2cpc5)
Anybody keep getting this error after the update from verizon. I keep getting it. I've rebooted, I've gone to recovery and wiped cache and still have it. I saw a post on the s8 post somewhere googling around.
I have at&t and got it after the update. It finally did stop at least.
Sent from my SM-G955U using Tapatalk
Yea mine finally stopped as well
Sent from my SM-G955U using Tapatalk
Mine is back again this morning in full force
Sent from my SM-G955U using Tapatalk
Yea it's back for me in full force. WTF Samsung
Back for me to this morning. Anyone know what DQA even is?
I think it has something to do with wifi quality. I installed package disabler pro and disabled the service (along with a bunch of other stuff). Problem solved.
Sent from my SM-G955U using Tapatalk
I should have done that prior to the update. I'm going to make it till the next stable update, then disable all update processes like I did with the Note 7. My phone was nice for a day before the idiots go mucking with it. I also have a red tinted screen after the update, which I don't think I did prior.
The update brought nothing I want. I'm a complete idiot for letting the phone update. I knew better. It was late at night...
I also think the update changed my LTE signal and the logo on the connection bar. It was better before. I'm typically full strength when lying in bed, now it is 1-2 bars.
Seems it was triggered this morning but receiving an MMS message of someone sending me a pic of the error. so maybe it's the MMS on wifi triggering the error.
There was a procedure where you enable Bixby and swipe left. I tried it and it worked.
At least until this morning. Its back again.
Hurry Samsung and either get out a fix or let us go back.
This way resolve my DQA error
http://www.androidauthority.com/fix-galaxy-s8-dqa-keeps-stopping-error-message-766402/
DQA Error solved!
coldconfession13 said:
Anybody keep getting this error after the update from verizon. I keep getting it. I've rebooted, I've gone to recovery and wiped cache and still have it. I saw a post on the s8 post somewhere googling around.
Click to expand...
Click to collapse
I purchased 2 S8+'s. I updated one and began getting the DQA message immediately, about 2 every minute only on that one updated phone. After spending a day trying ALL of the solutions you see posted, I thought I had it solved until it re-appeared 4 hours later! I decided to go down to the Verizon store to have them resolve this. They spent 45 min on the phone with THEIR technical support and basically went through the same list of solutions we've seen posted. None of them would work. Additionally, I had a Samsung GearS watch that would not install (Error Code 5).
The other phone WITHOUT the update has worked fine, no errors and the same watch installed fine. I asked Verizon to just to wipe the phone so I could start over without the update. Several technicians in the store told me that would NOT work. They stated the update is not removed by restoring the phone to the factory image. I found this difficult to believe, so I said, "Fine, give me another phone!" For whatever reason, and I don't care what the reason is at this point, this phone is not performing as it should, you obviously can't fix it, so as far as I'm concerned it's defective and I demand a replacement. They provided me with a new replacement and transferred all of the apps I spent 6 hours previously installing, to the new replacement, the watch installed properly and I left the store with a properly working phone with no error pop ups. Verizon solved my problem! I am now, once again happy and WILL NOT allow the software update to install until Samsung corrects this.
If you installed this update, you WILL begin receiving the DQA message ONLY when you are on WIFI. That's unsat for a new expensive phone. Simply bring it back to your Verizon store. Demand a refund or another phone. That is the most effective way to send a direct message to both Verizon and Samsung management that you are not happy. No doubt they pushed programmers to release this update before properly testing it. These managers should be held directly responsible for their actions that led to destroying an otherwise fantastic device. And WHY haven't they stopped this bad update???? My phones are still asking me to install it. Nope! NO WAY!
RPAQ said:
I purchased 2 S8+'s. I updated one and began getting the DQA message immediately, about 2 every minute only on that one updated phone. After spending a day trying ALL of the solutions you see posted, I thought I had it solved until it re-appeared 4 hours later! I decided to go down to the Verizon store to have them resolve this. They spent 45 min on the phone with THEIR technical support and basically went through the same list of solutions we've seen posted. None of them would work. Additionally, I had a Samsung GearS watch that would not install (Error Code 5).
The other phone WITHOUT the update has worked fine, no errors and the same watch installed fine. I asked Verizon to just to wipe the phone so I could start over without the update. Several technicians in the store told me that would NOT work. They stated the update is not removed by restoring the phone to the factory image. I found this difficult to believe, so I said, "Fine, give me another phone!" For whatever reason, and I don't care what the reason is at this point, this phone is not performing as it should, you obviously can't fix it, so as far as I'm concerned it's defective and I demand a replacement. They provided me with a new replacement and transferred all of the apps I spent 6 hours previously installing, to the new replacement, the watch installed properly and I left the store with a properly working phone with no error pop ups. Verizon solved my problem! I am now, once again happy and WILL NOT allow the software update to install until Samsung corrects this.
If you installed this update, you WILL begin receiving the DQA message ONLY when you are on WIFI. That's unsat for a new expensive phone. Simply bring it back to your Verizon store. Demand a refund or another phone. That is the most effective way to send a direct message to both Verizon and Samsung management that you are not happy. No doubt they pushed programmers to release this update before properly testing it. These managers should be held directly responsible for their actions that led to destroying an otherwise fantastic device. And WHY haven't they stopped this bad update???? My phones are still asking me to install it. Nope! NO WAY!
Click to expand...
Click to collapse
All this and you could've just cleared dalvik cache, no?
Sent from my SM-G955U using XDA-Developers Legacy app
Clearing cache doesn't work, but apparently Samsung is pushing an dqa update through the Galaxy app store
So yeah, apparently Samsung is to have pushed out an update to fix the issue yesterday. I have not received it and I still get DQA keeps stopping almost all day, even sometimes when not connected to WiFi. Is there anyone else that has yet to received it? I read it was pushed via Galaxy Apps, so I opened it, but no update. Search in the app comes up with nothing useful.
hoaivu1508 said:
This way resolve my DQA error
http://www.androidauthority.com/fix-galaxy-s8-dqa-keeps-stopping-error-message-766402/
Click to expand...
Click to collapse
You did not resolve it, you worked around it.
Go to Play store, Download package disabler pro ($1.49) and disable DQA.
Best $1.49 I spent and I can kill so many crap processes.
For Those having issues with DQA Here's update fix: http://www.apkmirror.com/apk/samsun...0-release/dqa-1-1-13-10-android-apk-download/
DQA Update to fix "DQA has stopped" error since day one update
Thanks it has fixed it. Wasn't showing in Galaxy apps
Sent from my SM-G955U using Tapatalk
Venom0642 said:
For Those having issues with DQA Here's update fix: http://www.apkmirror.com/apk/samsun...0-release/dqa-1-1-13-10-android-apk-download/
DQA Update to fix "DQA has stopped" error since day one update
Click to expand...
Click to collapse
I can't install the apk.