Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
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.
Seems once again Sony can't seem to get a stable phone. Shame as it offers so much potential with good design and great specs but failing on software again.
Constant app crashes, phone freezing,
Just goes to show you can't just chuck all the latest bits in a package and think it will work.
Going to have to return this unless there is a sudden fix in the next few days as I only have a 14 day change or mind.
That hasn't been my experience at all. I got the US phone and flashed the UK firmware. I haven't had any issues whatsoever. You should try a factory reset before returning the phone.
I have it for 2 weeks now, no freeze or reboots whatsoever... European Firmware here...
My phone was purchased from O2 in the UK. Don't think there is much bloat on there so don't think it's O2 that's screwed it up.
Phone is completely standard with just a handful of apps on it.
So far I have had numerous '' email has stopped working' to Google stopped working to music not working errors.
OK Google seems to hardly ever work. Almost seems like it can't hear the hot word.
I also think that many of the push services are being put to sleep which is why the battery life is so could as I often don't get notifications until I wake the phone yet the same accounts on my old s3 always come through first.
So far had one update come out for the phone. Don't know if it's the latest firmware though.
I can totally not agree with you.
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
hpsauce37 said:
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
Click to expand...
Click to collapse
Does the launcher you use rebuild your home screens after a reset? I still use Google Now Launcher, and after a reset, when I reinstall GNL, everything is put back in its proper place, even web browser page links.
I am using the US firmware, and have not experienced any of the problems you mention. You may have a defective unit. Then again, if you're not happy with the phone for other reasons (and there certainly are things that could be better), you certainly don't want to wait past the return date!
I'm running the UK firmware with the US OEM file to have Volte and fingerprint sensor on T-Mobile and has been rock solid since day one. I would reset.
Have reset the phone and just setting it back up.
Will see how it goes over the next few days.
One thing I did think that was odd previously when it was playing up was when it would crash and reset itself was that when it started up it was on the Google keyboard set up screen. I had installed the Google keyboard as I preferred it to SwiftKey. Maybe the issues were linked to that somehow.
Wow too many errors there... Probably a faulty unit... Or maybe u should do a software repair with Sony pc companion
Don't forget it runs Android Orea 8.0 by means a lot of third party apps may not fully compatible at this moment, consider not many phones running Oreo hence the app developers are not in hurry to tweak their app to run smooth in Oreo. That's what causes the occasional app crashes I believe.
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
hpsauce37 said:
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
Click to expand...
Click to collapse
On reddit someone write that he downloaded LUX https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite and everything was working much much better. Maybe later i will find the post. (https://www.reddit.com/r/SonyXperia/)
No single reboot or app crash for me.
The only thing that crashes on me on occasion is Google Photos, other than that, rock solid so far.
Just had an a 3rd party app crash but as someone mentioned above it might be because the developer has not updated yet for oreo???
Other than that been much better so far
Davka said:
No single reboot or app crash for me.
Click to expand...
Click to collapse
Same for me. 3 weeks i have got it 100% stable.:good:
Uhm ok I guess now it's my turn.
Today the "touch" went crazy. 2 times. Like for example keeping pressing recent button ? will result in multiple touches. Basically every touch is not a "pressing" touch. So I can't do swiping or other keep pressing relative touching. First time happened, a reboot fixed. Second time nothing worked. I have to SHUT DOWN THE PHONE AND WAIT A LITTLE BIT, then turn it on and everything was OK...
Is it just me?
P.s. UPDATE: I tried everything, safe mode, total reset, even software repair through PC companion...nothing. Its obviously a hardware problem, not software related. I returned this morning to assistance. They should give it back to me within a week...
My first week with XZ1C, 100% working, perfect, no reboot or other problems. One of the best phones I ever bought...
Phone's stable, no software/hardware issues. Working away reliably, battery consistently giving me expected results (ending day with 25%-50%, depending on use), connectivity perfect, performance smooth as butter.
Hi my Razer 2 will just randomly freezes. By that I mean sound will continue to work, the screen will remain on passed it's 5 min inactivity cutoff point, but the screen and the side buttons( all 3 buttons) will not respond to any input. I'm not sure how long this will last but I know it has stuck that way for more than 15 mins. Most of the time I just immediately reboot. And about 25% of those times it will still be unresponsive once it comes back on. But most of the time it fixes the issue till it decides to do it again. It does this about 2 times a day.
I'm not rooted, unlocked, nor have I flashed anything to my phone. It is still bone stock. The phone is only about 2 months old and I'm on the latest update.
Any help would be greatly appreciated.
Exactly the same issue here, stock completely but will crash on nearly every app I try to run. Screen is so unresponsive it is painful, playing Pokemon Go is a horrendous experience. Taking my handset to Three today to see if they can give me a replacement.
Mine doesn't do it on every apk. But when it does I'm usually watching a video...... Haha no not porn.... Lmao. And the other weird thing about it is when I reboot it it will show the splash screen then boot animation then it cuts the boot animation short and pops up a very basic very old school window requiring me to enter my password. So I enter it and it goes right back to the boot animation where it left off. And finishes running the animation then before I can go to my "Home" screen I have to input my password again. But this time is normal password screen and I have it set up to require it at that point. It's the first generic password screen in the middle of the boot animation that puzzles me. It just started doing this about 3 to 4 days ago.
Had a previous phone that would randomly freeze.
The solution was to enable developer mode. (Settings about phone and tap on build number 10 times)
Head back and find developer options.
Set Window animation scale to off
Set Transition animation scale to off
And set Animator duration scale to off
Restart phone.
Hope that helps.
chewdiggy said:
Exactly the same issue here, stock completely but will crash on nearly every app I try to run. Screen is so unresponsive it is painful, playing Pokemon Go is a horrendous experience. Taking my handset to Three today to see if they can give me a replacement.
Click to expand...
Click to collapse
I've faced the same. Three are not only swapping my handset for a Mi 8, but they have upped my contract benefits to the top level, and reduced my costs by £10 a month. I know the Mi 8 specs slightly lower than the Razer, but I'm fed up with this
Nameless21 said:
Had a previous phone that would randomly freeze.
The solution was to enable developer mode. (Settings about phone and tap on build number 10 times)
Head back and find developer options.
Set Window animation scale to off
Set Transition animation scale to off
And set Animator duration scale to off
Restart phone.
Hope that helps.
Click to expand...
Click to collapse
That's one of the first things I do when I get a new phone, flash a rom, or just generally anytime I have to set it up from scratch. So it's not that. I guess I'm gonna flash the kernel in these forums that has root capabilities and twrp built in. See if that helps..... I like the performance it has during mobile gaming. PUBG runs on the higest/best video setting and speed like a boss.
Did you set it to adoptable storage when you first got the phone?
Nameless21 said:
Did you set it to adoptable storage when you first got the phone?
Click to expand...
Click to collapse
If that is the issue is this something that can be reset to have the option to choose the correct storage if the factory image is flashed?
mattwheat said:
If that is the issue is this something that can be reset to have the option to choose the correct storage if the factory image is flashed?
Click to expand...
Click to collapse
You would have to do a hard reset.
When asked how the memory card is to be used select as portable storage.
Not to be provocative, but why have the option of adaptive storage if it doesn't function as it should on this phone? I've never had this issue with any other device. Personally I'm extremely disappointed at Razer. No updates since the Feb security patch, we are now in June. Razer forums show very little advancement and support, and we know the mobile division has been scaled down significantly.
I would have thought this device could be a devs dream, but alas it appears long forgotten
bay91 said:
Not to be provocative, but why have the option of adaptive storage if it doesn't function as it should on this phone? I've never had this issue with any other device. Personally I'm extremely disappointed at Razer. No updates since the Feb security patch, we are now in June. Razer forums show very little advancement and support, and we know the mobile division has been scaled down significantly.
I would have thought this device could be a devs dream, but alas it appears long forgotten
Click to expand...
Click to collapse
I agree. Not having any update since feb's security patch shows Razers laziness or lack of concern for their supposedly high end mobile gaming device. Not a confidence booster going into a round of PUBG knowing it may freeze at any moment.
It just froze again for no apparent reason.
And by the way I don't even have a micro SD card in the phone.
This is weird I've never had any of the issues you've described in either my RP2 or RP1. I would contact Razer send it back or swap.
Sent from my Razer Phone 2 using XDA Labs
Same. Haven't even had it for a month. Completely stock, latest update, freezes completely when opening either version of Chrome (Canary and Stock) sometimes, and forcing a reboot usually gets it frozen AGAIN before I even unlock it, which makes me force another reboot. Not to mention I think I'm already noticing a dead pixel on the screen. It hasn't even been a month.
I did a factory reset in the stock recovery about 4 or 5 days ago. It's been running beautifully since. No lag no freezing just running as smooth as a unicorn sliding down a rainbow. So I guess I picked up some kind of malware or something along my journey. I've gone to the "dark web" a few times. Just snooping around. But I was safe about it. I used a VPN and ran thru tor browser. But it could have been there that I picked up something. Who knows. But what I do know is it's back to as smooth as it was out of the box after a full factory reset.
same here on rooted
it mostly crash when I want to watch videos on Facebook or similar pages.
it does on stock/rooted stock/gsi and i think it's vendor problem
Moving back to Internal storage seems to have done the trick, especially as my SD card has been disconnected several times now.
Same issues with Radom and sometimes more often freezing as to where I have to hold power down until it reboots.last time it did it was a few minutes ago I was trying to watch a clip about oppo 7 pro video about 5g on the chrome search app it played about 15 seconds and solid froze my phone everytime I tried to play it.it worked fine in YouTube app
My phone is been having this issue lately.
Seems to have started only in the last week or so..
I am running the custom kernal and the "stock deodexed and zipalign" rom.
It could also be that I've rooted...?
I don't want to go back to stock rom so I live with the random frozen screen once a day and since people here have said it happens on stock.
Phone has never been dropped and it isn't hot when it happens.View attachment 4803124
Sent from my Phone 2 using Tapatalk
Mine has done this a few times in the past week. Stock rooted, tried stock kernel and arter's kernel with same result. It's only happening to me while using chrome and videos in Facebook.
Running complete stock Three ROM, no rooting. Chrome took an update over the weekend and now the phone locks up when watching video. Works fine on Samsung browser on the phone, just Chrome.
Might finally get around to flashing and getting LDAC working on this thing....