Related
I have had my phone for about 2 weeks now, and this has been an issue since about day 1. I will set my phone aside while doing other things. When I want to use it I pick it up and press the power button to activate the screen. It seems that about 20% of the time the phone is non-responsive. I can't even receive calls/texts/email while it is in this state. I end up pressing the power button for 10 seconds or pulling the battery to get it to reboot. Everything seems to work fine.
I have heard that this could be a result of a reception issue, and that an update would be released in September to solve this issue. Is this information correct? Has the update already been released? I believe I am running the most current version, 2.1 update 1
Is there a software fix? Do I have a defective unit that needs to be sent in for repair? Is there a setting I need to look at? Any assistance would be appreciated.
you are describing the typical scenario of too many background services and apps running taking up too much resources thus making the phone non reponsive
install Auto Run Killer http://forum.xda-developers.com/showpost.php?p=8123924&postcount=40
then tick all the apps to disable reboot your phone
then you can choose which apps you really want to let lose for it to run in the background
It's also entirely possible it's faulty though
I don't think it is a matter of apps running because there are no active apps running when I am not using my phone.
I guess I am looking for an answer that tells me that this is an known issue with this model and I wiould be better off with a different product, or if I will be safe to get it replaced/repaired.
Ideally I would love to hear it is only a matter of a software patch or something similar.
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Well that was a pretty useless post. The only idea my mind is set on is to get my hands on a dependabel phone, preferably the one I have. You suggested too many apps running, fine, but unless they run automatically on reboot and/or the 'active applications' window that runs by default is inacurate, there aren't too many resources being used and nothing running.
you'll be surprised what runs under the hood
you can run this and find out
http://forum.xda-developers.com/showpost.php?p=8156087&postcount=58
Android System Info
another good thing to disable is the Media Scan
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Don't be so quick to assume your suggestion was correct either, AllGamer:
http://forum.xda-developers.com/showthread.php?t=775017
Thus far nothing in that thread has suggested taxing the system too far. In fact, hardly installing anything at all from a fresh factory reset still has this problem and no one yet has really worked out why aside Samsung saying the hardware is damaged. I was on the phone to them today, same thing said.
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
AllGamer said:
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
Click to expand...
Click to collapse
I see no truth in the signal claim I've said why in the other thread. But this is the point, it is an issue a few of us are having from all over the place but as of yet there is absolutely no distinguishable pattern. As I say, a completely fresh phone with official firmware and no installs also has the problems. It's a very frustrating situation because no one can conclusively point to software or hardware yet. Samsung keep saying the same thing, send it in, send it in..
it's true the only way to diagnose those will require to be hands on, and run tests to pin point exactly what is causing that.
Eclair doesn't have the option to auto upgrade, so that's definitely not it
Lag is likely, but what, or which stock apps can cause so much lag?
signal even when the phone is having a hard time switching and scanning for a new signal it shouln't keep the phone unresponsive for such a long period of time unless it's lagging
my Old Treo did that, anytime it lost signal and regained signal there was a minor pause, or a looooooong pause if the phone was lagging
if this is the same case with the SGS we just need to figure out which App is running in the background that is dragging the entire system down.
it could be the internal SD which might have become defective, thus locking up the phone, similar to those people that can't get past the boot screen
i can't think of any other plausible causes at the moment.
Well, I can tell you: having experienced the problem a number of times, it is almost certainly not the lag scenario you have described - this is a proper lock-up. My guess (since it does appear to have some correlation to cell switching, or other signal-related issue) is a bug in the baseband drivers, or something similar, resulting in a panic. I might see if there's any way to get a dump out of this thing to prove it, but at the moment it's just a guess, so I'm not going to tell you that's the definitely the reason, or that you're stupid if you don't agree, even though I'm more qualified to do so, since I've actually experienced the problem.
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Android is designed to not need auto task killers. It is purely a myth that they are needed whatsoever. This is linux we're talking about here, not windows.... It's possible he has a single app installed causing the issue, but the ideal fix would be to figure it out one app at a time and get rid of the faulty app.
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.
Well I had a BSOD (a freeze to a black screen that could only be fixed by a bettery pull) a couple of days after my update to version 893. I ws hoping the upgrade would fix this. Has anyone else also had a BSOD after the 893 update?
--
I've been on .893 since the leaks were first discovered and I've had zero BSOD issues.
i have been running 5.7.893 (newer than the current OTA) for more than a month now and still experience an occasional BSOD, the frequency is reduced, but they still occur
PhilDX said:
i have been running 5.7.893 (newer than the current OTA) for more than a month now and still experience an occasional BSOD, the frequency is reduced, but they still occur
Click to expand...
Click to collapse
+1 same here
Geezer Squid said:
I've been on .893 since the leaks were first discovered and I've had zero BSOD issues.
Click to expand...
Click to collapse
Same here - no BSODs, and none of the other errors that others are experiencing.
in fact, the only problem with my BIONIC is self inflicted - I tried to force it back to stock (just to see if eFuse would trip) and now on boot I get a flash failed message, and can only boot the phone via the bootloader. But, other than that, All is well.
I installed the leak version. The only thing it made better on my bionic was the camera. Still having BSOD, and random 3g data drops.
Unfortunately, I gave in an bought the Razr. It seems alot smoother and faster. Just more fluid. Screen is better.
I installed the official OTA last night. I never got a BSOD before the update and I haven't gotten any since the update so far either.
Sad. Have had 3G drop out completely twice in one day since the update. Guess it's time to start hammering verizon for a different phone. Certainly not going to wait for the next update after how long this one took.
I never had the BSOD before the update, but just had it today after update. Completely stock before and after.
Depending on where you are located. A cold phone could be a problem. My friend's Iphone began BSOD when he would leave it in his car in 20(f) degree temps.
I have had BSOD several times but am now running 5.7.893 and think it's related to some kind of app interaction. About 3 weeks ago I did a factory reset, rooted and have been gradually putting apps back on for three weeks no BSOD. Just some thoughts.
I am stock and received the 55893 update. I expected it to fix the things it claimed to fix but it appears it has not. I still lose 4g often. More often than before. Sometimes it switches to 3g and sometimes I lose all connectivity. Before, it only would only switch to 3g and stay there. I also am getting reboots more often now. And by correcting that so-called high pitched whine, I have found that the audio volume for music has significantly decreased. Also, when charging the phone while off, the battery no longer reads accurately. It tells me the phone is at 20% and less than10 minutes later it is fully charged. WTH Motorola?
Sent from my Xoom using xda premium
cmjohns24 said:
I never had the BSOD before the update, but just had it today after update. Completely stock before and after.
Click to expand...
Click to collapse
Same boat. The phone won't wake up from sleep probably twice a day, and I'm forced to pull the battery. PITA.
Hey guys, I'm having GPS issues with my phone. Just wondering if anyone else is experiencing the same.
I'm getting a decently long lock time and then afterwards, every 10-15 mins I'm getting a lock loss followed by a little delay then a lock again.
In case it helps, I'm on stock build KTU84P.N910TUVU1ANJ7.
Consequentially, if someone could help me out by giving me the following files from their phone, it'd be really appreciated:
/system/lib/hw/gps.default.so
/system/lib/libloc_core.so
/system/lib/libloc_api_v02.so
/system/lib/libloc_eng.so
/system/etc/gps.conf
Same here.. Across ROMs(NJ7 based ROM and stock NJ7) as well. Did the compass calibration but didn't fix it. Navigation on this phone is pretty terrible since it loses gps every 15 minutes like what you're seeing.. Any suggestions from anyone would be great!
I flashed the new baseband and still am having the issue of a buggy GPS...
I did have initial issues.
But the compass calibration seems to have resolved most of those.
Though yesterday I did lose the gps signal, which I thought was weird.
It was the first time it did that which I can remember.
It's happened to me on all my Note phones. Samsungs gps is less than spectacular.
Ya I'm having the same issue it doesn't matter the ROM still same issue. But think its a Samsung firmware issue. It works for me initially on a trip A to B but seems way back B to A it stops. Didn't have this issue with note 3. Part of my reason for bigger phone is GPS use so this is irritating. If not fixed with lollipop might have to change.
Sent from my SM-N910T using XDA Premium 4 mobile app
My Note 4 is currently completely stock/unrooted NK4, and I've seen the same thing - GPS works for several minutes, dies for about 5 seconds, then comes back. I've also once had GPS fail to lock at all until I rebooted the phone. :-/
Oh, well. It's still way better than my old S3 which had been dropped quite a few times.
I'm not having any gps issues. The new updated maps is doing it for me.
But, on other phones I have installed the faster fix app when having gps issues. It can be acquired in the playstore:
Did quite a bit of searching and still can't nail down an answer. Does anyone have latency issues with the N6 running Marshmallow? Ever since upgrading in Marshmallow (ran last few releases of Chroma w/ various kernels) it takes FOREVER to load webpages. To run a speedtest, it takes 20-30 seconds (or more) to find a server, then shows upwards of 50 mbps download speed. The speed is there, but it is not getting through. I know there are known Wifi issues with M on the N6, but it gets frustrating. It is an issue that exists through both clean flashes and dirty flashes. Any help?
Thanks!
I had made a couple of posts about this and I'm noticing it too! The WiFi is just really dodgy! What I was able to dig up was that it was a change in the radio file this time that seems to be kind of buggy! Someone told me that you could download a lollipop stock image and flash the radio from that, and that it's independent of the OS itself. I haven't tried it yet, but I am noticing this issue too! I hope it gets fixed soon because it's a frustrating bug!