[Q] More 5.0.1 BS. Keyboard help - Note Edge Q&A, Help & Troubleshooting

1st, I want to tanks Verizon and Samsung for the horrible update. Knowing all rhe issues peiole are having I waited to do the update. After reading a post from a Verizon Employee stating Verizon was rhe last to release the update so they could tweak it and make it perfect, I did it against my better judgement and boy do I regret it. The phone freezes all the time, "unfortunately the Phone has stopped working" and now, several times a day, "unfortunately the Samsung Keyboard has stopped working" and I have to restart my phone. So sick of this. Any advice? Attached a couple screen shots.
Sent from my SM-N915V using XDA Free mobile app

Having same issue
I am having the same issue with getting "samsung keyboard has stopped working" It started within 10 minutes of upgrading to 5.0 on my Verizon Note Edge and has happened multiple times per day ever since. Surely others are seeing this!

Do a factory reset and your woes will disappear
Sent from my SM-N915V using XDA Free mobile app

I have the same issue on my TMO Edge. Did a reset and it didn't do anything but make me start over with customizing. Within a few hours it was having the same issues. I'm hoping 5.1 fixes it and the carriers get it out soon.

I downloaded the swift keyboard. It's actually quite nice and the mic Voice to Text feature still uses Google instead of a 3rd part app. ?
Sent from my SM-N915V using XDA Free mobile app

Related

Software Update Function's Working - A Good Sign

When the phone first came out, the Software Update Check (Settings>Software update>Software update check) returned an error. Now it says "Current version is the latest version." Hopefully that's in preparation for an OTA push of the Gingerbread update. It can't get here soon enough.
Few hours ago i checked it now it was giving me authorization errors and time outs.
now i see it says latest update which means they are closing up on the gingerbread update i hope "Ice Cream" is available soon after that. - Side note: it was noted that Honey Comb was like Windows Vista (bug wise etc, which means "Ice Cream" is the Windows 7 of Android!
I don't know if it's possible, but it would behoove T-Mo/LG to get a bug fixing update out in the wild before most early adopters 14 remorse windows are up. I know some of you bought on launch day, but some of us waited. I myself have until a week from today.
Incidentally, I'm pretty sure what we really want on our G2xs is Android 2.3.4, still called Gingerbread. Honeycomb is for tablets.
I'm willing to bet its a problem for the minority of owners of this phone. The bugs that is
Sent from my LG-P999 using XDA App
laker666 said:
I'm willing to bet its a problem for the minority of owners of this phone. The bugs that is
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Are you out of your mind? Look at the percentage of threads on the first page. 3/4 are devoted to problems. Here's a quick recap:
1) Screen bleeding
2) Wi-Fi either not connecting, dropping connections, or disabling profiles
3) Bluetooth not retaining profiles, not reconnecting, or not holding a connection
4) Reboots which LG acknowledged as a s/w problem after months of O2X complaints
5) "System checking..." forcing a hard reset at boot up
6) T-Mobile apps opening a 4G connection when Wi-Fi's enabled
We're all on the same ROM and radio and the majority of this stuff isn't hardware. So the "minority" to me are people who haven't really tried to use the functions above heavily and don't know they have problems.
I'm not having any issues with my phone. Battery life could be better but I use it a lot.
Sent from my LG-P999 using XDA App
FYI LG is in charge of the software update not Tmobile. I recieved an email from an LG service rep and it said "As far as I know, our technicians are under review for the 2.3 Android version." This was said on a support email I had sent to LG. My G2x seems struggle to keep a good connection, especially in my home. I keep losing the signal and it disconnects. Tmobile said they were going to check my area to see if there are issues. If nothing gets better by the 9th of this month I'm returning mine before my 14 days are gone.
im getting force closes when trying to open the software update menu now. guess ill be flashing it whenever it comes instead of getting it ota -_-
You sir are right. I just checked and it now says current version is latest. Progress.
Sent from my LG-P999 using XDA App

[Q] Google connection sync/talk on NS never stays on consistently, lately.

Device: NEXUS S
Carrier: TMOBILE
Country / Language: USA
OS / Browser / build number (if applicable): 2.3.4
As of about two weeks now, my Google services connection sync and even Gtalk never stay on consistently. Data icon goes from green to gray, after wakeup. hen when it is green, I only then start to receive me push notifications. I never had this problem before and was very happy with the Nexus S. Now, however, I'm not so sure about that anymore, and it's a consensus out there that there is no solution, and that Google is "looking" into the problem. I don't think it's necessarily a hardware issue as everything was fine out of the box when I first got my phone, so its likely a Google server problem? Though it sounds like the problems are isolated to Nexus devices and myTouch 4G phones.
I would call Samsung to try to get a replacement device, but from what I hear, it doesn't solve the problem either, and Samsung's CS really sucks too.
Any advice would be greatly appreciated.
I am going through the same trouble, too. I think its more of Google server related. One thing tthat I am sure is, it started very recently. About 3 weeks ago.
Sent from my Nexus S using XDA Premium App
I have the same issue. It started a few weeks back. Got the 2.3.4 ota...same issue. Came from 2.3.2.
It's been happening to me for a while as well. Even back in 2.3.3 when I was on CM7 and OEM. I seriously think it's a problem on Google's side and they really need to address it because it keeps logging me off of Gtalk which is annoying.
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
I am also on two google threads about this, and there is still no agreement on a solution..
http://www.google.com/support/forum...e2&hl=en&fid=7c7a962fd3ae87e20004a26b2f3f005b
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=56f54d35a6a0da29&hl=en&start=80
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=5113952419b47e54&hl=en
I am having the same problem since around mid April. This is so frustrating, please guys flood the google help forums, this the only way google will see the seriousness of the problem.
Sent from my Nexus S using XDA Premium App
Flood indeed. Google is clueless on a solution to this problem, especially if they don't even acknowledge it..
Sent from my Nexus S using XDA App
clin0420 said:
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I stay green if I'm on 3g, so maybe it's a wifi issue. I would've sworn it was a 2.3.4 issue though.
highly doubtful that this is a wifi issue, with the number of people of various threads stating that they dont even use wifi....worse yet it occurs regardless of wifi or 3g/2g
i posted a video on youtube showing the problem
http://youtu.be/axpyhgdvuMs
i have the same issue, both of my nexus 1 and tmo G2

Camera failed not only on Verizon. Mine just died.

Well yesterday I tried opening my camera app and the phone hung. Then when I killed all the apps I tried opening it again, it said camera failed. I tried resetting the phone and even took it into the Sprint store. The guys at the store said I was the first one that they heard having this problem on Sprint. They replaced the phone there on the spot since I was in the 14 day window. I bought the S5 on release day on the 18th.
Hope this new phone works out. But if this is happening across carriers well...
Anyways the new phone is working ok. See how it is in a week with taking some pics.
Just happened to me on a 3 day old phone. A restart and it's gone. Uninstalled Google Camera which is the only third party cam app I've used. Any more issues and I'm returning the phone and possibly closing this new account. I have horrible service and they're playing stupid games with my account.
GorillaPimp said:
Just happened to me on a 3 day old phone. A restart and it's gone. Uninstalled Google Camera which is the only third party cam app I've used. Any more issues and I'm returning the phone and possibly closing this new account. I have horrible service and they're playing stupid games with my account.
Click to expand...
Click to collapse
Yeah I am on the fence now. I really don't know what to do. If the camera dies again outside the 14 days, I have to wait for the device to get replaced.
Verizon and samsung admitted the problem exists and fix for free.
Maybe if sprint s5's fail like crazy too itll apply to use also
Sent from my SM-G900P using XDA Premium 4 mobile app
gtuansdiamm said:
Verizon and samsung admitted the problem exists and fix for free.
Maybe if sprint s5's fail like crazy too itll apply to use also
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think the Samsung statement applies to all S5 users. I'm not sure if you can get a replacement if it's only intermittent but I hear Sprint will replace units on the spot for the issue. I'm going to a corp store later, I'll ask about what they'll do if it keeps happening to me.

Bootstrap Failed....

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?

DQA keeps Stopping

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.

Categories

Resources