Related
Is anyone else having a problem with auto orientation taking a dump every once in a while? It's happened 2 if 3 times since I got the phone on Wednesday...
I end up having to reboot.
Chris
Sent from my Inspire '4g'.
Yep happens to me.
Sent from my HTC Inspire 4G using XDA app
Yeah it happens to me too...
Hasn't happened to me yet. What, does it just stop rotating or something?
it will stop rotating, and when porgrams like browser, or reader, are opened they are rotated the wrong way, and will not change.
But once rebooted all is normal again.
Weird, happened to me a few days ago too. I couldn't get anything to
rotate...music, browser etc. After reboot it's been fine.
Mine has done it 3 times so far. A reboot fixes it, but it's still lame.
Nope hasn't happened yet. Had a Bluetooth bug where it wouldn't turn on but reboot fixed that.
Update happened to me now. Many software cause it dosn't happen in all software at the same time.
Sent from my Desire HD using XDA App
Happened to me the first day I purchased it...the browser was stuck on landscape and pictures I took were wrong orientation...I was freaking out a little bit but a reboot fixed it.Happy now Hasn't happened since.
sent from my HTC Inspire™ 4g using XDA App
Mine just did this for the first time. I'm using ADW EX launcher. You folks with the issue using alternative launchers?
It happened on the demo unit at the AT&T store. The salesguy said he never saw it before. hahaha!
Hasn't happened to me.
Sent from my Inspire 4G using XDA App
No, I'm running complete stock at the moment(waiting till my trial period ends before I root and start playing; coming from the vibrant on unlimited data t-mobile.... love the phone so far but not loving the whole 2gig thing)
My auto rotate has died almost once every day... but when it does it still worksin the browser. Strange. Certainly software.
Sent from my Inspire '4g'.
has anyone found a fix?
Some of what I am seeing reminds me of times I had a bad flash.
Just did a factory reset, and if that does not work will try reflash using the RUU.
It's done it to me twice in the week since I got it - still using stock OS. Restart seems to fix it. It's a little aggravating, but nowhere as bad as all the crashes I had with the Atrix before I traded it back for the Inspire.
It seems to be in the kernel. When I made my custom kernel it did that all the time, has something to do with the Auto-rotation configs. I believe a kernel compiled from our newest sorce fixes this, at least I'm pretty sure.
It happens to me every time I have a LWP enabled that use the accelerometer, like galaxy core and metal rain. Selecting another LWP or disapbling the feature in the LWP solves the problem for me. I saw this behavoiur in the stock rom, tpc's rom and ar 3.2rom.
Happened to me a little after flashing coredroid when all the roms started coming in. Reboot fixed it of course. I remember frantically toggling the auto rotate and fearing a dead orientation sensor.
Sent from my Inspire 4G using XDA App
It's happened to me in the past too. I did notice that the problem stopped when I stopped using the "reddit is fun" application though, and it hasn't happened ever since. Maybe the problem lies within certain applications? Could just be a coincidence. Might try using the app again later to see if it happens again.
DOAlaboratories said:
It seems to be in the kernel. When I made my custom kernel it did that all the time, has something to do with the Auto-rotation configs. I believe a kernel compiled from our newest sorce fixes this, at least I'm pretty sure.
Click to expand...
Click to collapse
Don't know, it happened to me 2 times when bone stock not even rooted, didn't happen at all on my rom/kernel until last night with my kernel which is latest source, unless there was some new source posted in the last few days, but I don't think there has been since there's been no update.
Maybe it is hardware.
Either way its completely random
Hello
recently i took my nexus 5 to lg and they replaced my motherboard
now about almost a month later
all the sudden i get this error
"
unfortunately camera has stopped"
the only fix to this is to restart it,it works fine after that
this use to happen to me on stock
now i rooted it and am using DroidKang ROM
what shall i do guys ?
Try a non aosp based ROM like CyanogenMod they may have done things different try that if it doesn't work call lg again
Sent from my Nexus 5 using Tapatalk
@hollowback
Force Close camera and gallery... Clear camera and gallery cache/data and reboot...
Now see whether you get the error again after sometime?
Btw, when LG had replaced your motherboard, were you rooted? Did they check whether you had a unlocked bootloader or anything like that??
-Flowed from an IceCold Hammerhead!
This is actually a very common issue. As of now the best fix is a reboot. It's triggered by certain apps. Do you use snap chat?
I used to have that issue. If I remember correctly it would happen when you would sleep the phone while in snapchat.
hello friends
first
"when i gave it to him he just opened it then chagned the motherbaord
i dout he saw the root thing.
he said i have a fungus on the board he showed it to me i wonder how that happened he said
it could be sweat and then he changed it :/
its kinda hard i still dont understand i had this cover since almost the start i wonder how water could go in cause i took care of it
second
well yeh i did install snapchat recently
before it use to crash without snapchat
well as soon as i restart it works perfect
what shall i do guys ? is this normal or ?
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?
My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Sent from my Pixel using Tapatalk
rosswaa said:
My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Click to expand...
Click to collapse
Same thing happening to me here too.
What I would do is start from scratch, install factory image, don't install any apps, use for a day to test, then install your apps one by one to find the culprit.
If still rebooting without any apps installed, it might be time for a rma
Sent from my Pixel using XDA-Developers mobile app
I used that Google support and came down to putting the phone I to safe mode for 24 hours to see but some days it does it a few times and other days it's fine
Sent from my Pixel using Tapatalk
Has there been any resolution to this? My Pixel has been randomly rebooting, too. Already tried troubleshooting with Google tech support, tried Safe Mode (did it there, too), and factory reset and cache wipe.
It still happens. And when I say random, I mean random. Sometimes it reboots overnight, sometimes in my pocket, sometimes as I'm using the phone (it'll freeze in some cases too before it reboots). There's no obvious indication of what's causing it.
Has there been any light shed on this problem? Any clue as to whether it's software or hardware related?
Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk
rosswaa said:
Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yeah, there really is no rhyme or reason to the way it reboots, making it even harder to diagnose.
Rebooted again while it was just sitting on my table. No rhyme or reason to this bug.
I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.
UnusualSuspect said:
I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.
Click to expand...
Click to collapse
Same here. Sometimes I'll go to my phone wanting to use it, try my finger to unlock, and it'll prompt me to input my pattern because it's required after a reboot. Clearly, rebooting by itself.
It's frustrating because there's no rhyme or reason to it. Sometimes it'll happen multiple times a day, sometimes it won't happen for a couple of days.
At first, I thought the Jan update fixed it too because it didn't occur for a while after the update, but then it reared its ugly head again. I've already tested it in Safe Mode, did a factory reset, and the rebooting still persisted.
If you simply research this on the web, many others are having this issue. And it's even been reported a few times by Android sites/blogs. Google needs to get on top of this. At the very least, they should confirm it's a software issue and not a hardware issue.
---------- Post added at 10:08 PM ---------- Previous post was at 09:09 PM ----------
Just a few links of people online reporting this problem:
https://productforums.google.com/forum/#!topic/phone-by-google/QHp96fk4Ygw
https://productforums.google.com/fo...vS_XxvBh8;context-place=forum/phone-by-google
https://www.reddit.com/r/GooglePixel/comments/59i9e5/pixel_xl_random_restarts/#bottom-comments
Happens at random but only when I'm using Chrome or when my Pixel has been sitting on my nightstand charging.
I've had the phone since launch with no issues. My random reboots just started yesterday and it's happened 5 times in the past 12 hours. Glad I'm not the only one with the problem.
Sent from my Pixel XL using Tapatalk
im thinking this is a hardware issue, im pretty annoyed if it is! i get it like 6 times a day or nothing for a while, makes no difference what im doing or apps being used
Going to try and get a replacement this is a joke, fully wiped and flashed and still does it
Sent from my Pixel using Tapatalk
Mine hasn't really been "rebooting"... It's actually just been suddenly shutting completely off for no reason. It will be fine for a few days, then the next fee days it will simply abruptly shut off for no reason... Battery levels don't seem to make a difference.. Weird.
Sent from my Pixel XL using Tapatalk
For me it seems that the reason lies in Bluetooth or just in the BT stack. If I deactivate bluetooth it works fine through the day. But I need bluetooth so I started BT again and the Pixel XL 128GB crashes sometimes 10 Times a day, but as I checked BT was automaticly deactivated after these first reboots. I seemed. The Pixel stopped rebooting as I activated BT and deactivated it myself.
And now? How long do we have to wait. I don´t think it´s a hardware issue.
So, I have this issue but it became (very) apparent only after the OTA Oreo. First two weeks were fine (and subsequently first two weeks after a factory reset I've done), but then it slowly starts doing this after those 2 weeks. Freezes then reboots. At first it's 1-2 a day, now it's like 12-20. Ridiculous. There's a buganiser thread for this issue and Google is aware of it. Most of the bug reports have this in them:
Code:
Sense Key : Hardware Error [current]
which Google rep says is a hardware issue. I also have an access to a Google's internal buganiser thread on this issue (i'm a vendor) and they refer to this being a Toshiba's memory issue. Not sure though why this started happening only after the Oreo update. Also people who flash Nougat report no issues as well. Another funny thing is that there's at least two users with Pixel (XL) 2 who suffer from it. Anyway, I'll be giving it back to my carrier over the weekend (glad we have 2 year warrant here in UK) even though I'm pretty sure I'll get a refurb with a similar problem after two wasted weeks of wait.
Flash nougat rom and see does this problem occur or not? If not then us nougat for a while then again update to oreo
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.