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 am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
chipsharpdotcom said:
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
BWolf56 said:
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
Click to expand...
Click to collapse
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
chipsharpdotcom said:
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
BWolf56 said:
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
Click to expand...
Click to collapse
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
chipsharpdotcom said:
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
Click to expand...
Click to collapse
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
billyjed said:
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for the tip...I'll try that if all of the above doesn't work. At this point, I'm all flashed up and running test cases.
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
chipsharpdotcom said:
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
Click to expand...
Click to collapse
Have you tried it with a different clock app? I mean, if I understand this correctly, it seems to be narrowed down to your current clock apk, which is different than the stock GB one. So I would suggest freezing (or unistalling) your current one with Tibu and trying a different one.
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
chipsharpdotcom said:
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
Click to expand...
Click to collapse
Haha first time I ever get that question but leaving your camera on should do the job (or video playing)
Hi Everyone
Bit of help please.
Having problems over the last 20 days or so. The phone keeps powering down completely at random.
I had flashed No Root Stock Debloated/Deodexed N6 ViPER|Atmos Audiophile 1.6 and after a week the above started.
Fully wiped (including data) the N6 and re-installed from a OTG USB through TWRP. After a week the same random shut-downs began again.
Another full wipe and installed ver 1.7 from the above and within a couple of days the shutdowns started again.
Today thought a different ROM may be the answer. Full wipe and tried [MMB29U/Q][6.0.1][STOCK][OMNI][MOKEE][CMTE][LAYERS] FLUENCE HD9 and the shut-downs are still here.
Seems to be getting worse.
Not using layers or anything abnormal - nova launcher and popular apps, nothing strange. No Kernel optimizations.
Really stumped as to what I have done. Wondering if I have a HW fault rather than custom rom or apps. Going to un-root, lock the BL and give Google stock image a go, unless anyone has a suggestion.
TIA
Any water damage that you can think of? Any parts of the phone getting extremely hot?
You could try ordering a new battery, and see if that fixes the issue, as it is not a software issue.
I'm also having a similar issue, but it occurs when trying to open camera and having relatively low charges(%20). I could not pinpoint my issue exactly but generally complete shutdowns caused by battery problems(temperature, voltage, mis-feedback). Like flyeyes says it is probably a defected battery unit.
Grab some logcats or a crash message. Without them the only thing I can advise is that it is one of your apps causing it or a hardware issue.
Have you tried complete stock firmware from Google with no customizations? If so, does it happen then? If it happens on complete stock from Google you might be looking at a hardware issue. If it only happens on custom ROMS after you set them up, then it might be an inconsistency with whatever apps/changes you make to it.
Rate this thread to express how you think the Sony Xperia Z5's Wifi performs. A higher rating indicates that it has excellent range, throughput, and signal strength. Like when you're taking a dump in the bedroom upstairs, do your videos have to buffer or do they come through without interruption?
Then, drop a comment if you have anything to add!
problem wifi
i have a router of wimax " bm626 hauwei"
z5 dual connect with it but no internet.
instead i have z3 compact at same time
z3 it connect with it with internet.
why
any one can help?
Did you tried to reset router to default settings? Did you tried to update router to newest firmware?
Thank you for providing this information so that we know how to protect their eyes
Well all I can say is I have no issues with signal strength at all. When my WiFi works fine, the throughput is good too. The problem I am having with mine (on both 6.0 and 6.0.1) is that I lose my WiFi connection every few minutes. What happens is I'll be browsing online and after a few minutes nothing is loading but the signal indicator in the status bar shows a full signal. I have to turn off WiFi on my device, then turn it back on in order for it to keep going. Very irritating. I have many wireless devices in my house, this is the only one doing it. Oh and I've tried using 2 different routers, no change.
Anyone else experience this?
No issue with mine, reaching as fast as 400Mbps near the router. Signal strength works as well as the Intel PCI-E wireless AC7260 cards in my house, so that's pretty impressive. Overall pretty satisfied with the WiFi performance.
I'm using a Netgear Nighthawk R7000 router with a fibre connection, so I guess that's something.
Dr. Mantis Toboggan said:
Well all I can say is I have no issues with signal strength at all. When my WiFi works fine, the throughput is good too. The problem I am having with mine (on both 6.0 and 6.0.1) is that I lose my WiFi connection every few minutes. What happens is I'll be browsing online and after a few minutes nothing is loading but the signal indicator in the status bar shows a full signal. I have to turn off WiFi on my device, then turn it back on in order for it to keep going. Very irritating. I have many wireless devices in my house, this is the only one doing it. Oh and I've tried using 2 different routers, no change.
Anyone else experience this?
Click to expand...
Click to collapse
Im having the exact same issue as you... the connection to the WiFi itself doesnt disconnect.. But what is actually happening is that the Device itself seems like it is putting itself in to this wifi sleep state briefly for a minute or 2 and then just suddenly comes back to it's senses (suddenly wakes up and starts sending/receiving data packets which then resumes loading like normal.. and it does this randomly at nonspecific times..
It could happen within a minute or 2 of using the wifi... or sometimes even after an hour or so of streaming (sometimes within 5 minutes of streaming)....
***NOTE***
My Xperia Z5 has custom ROM and Kernel and is rooted with SuperSU with Xposed and busybox installed running Latest Marshmallow 6.0.1 (.224) Firmware..
THEN I suddenly decided **** this, I'm actually going to fix this shi* lol ( you know that moment when you just had enough and finally decide to bother doing something about it, ).. that's the moment I had..
Anyway to keep this simple...
After several hours of troubleshooting, testing and diagnosing , and trying to narrow down, isolate and fix the damn problem causing it to happen, I'm not sure 100% just yet but I may have found the problem and the fix to this IF the wifi "Hanging" doesnt occur anymore after doing some minor editing of the system files. (Only able to do with a rooted device) .
I will inform you guys with my results in a couple of days and hopefully the outcome is good news .. IF not, ill just have to keep trying and if all else fails ill just factory reset the device since getting everything back on to my phone will only take 30 minutes..
Peace!
TheTecXpert said:
Im having the exact same issue as you... the connection to the WiFi itself doesnt disconnect.. But what is actually happening is that the Device itself seems like it is putting itself in to this wifi sleep state briefly for a minute or 2 and then just suddenly comes back to it's senses (suddenly wakes up and starts sending/receiving data packets which then resumes loading like normal.. and it does this randomly at nonspecific times..
It could happen within a minute or 2 of using the wifi... or sometimes even after an hour or so of streaming (sometimes within 5 minutes of streaming)....
***NOTE***
My Xperia Z5 has custom ROM and Kernel and is rooted with SuperSU with Xposed and busybox installed running Latest Marshmallow 6.0.1 (.224) Firmware..
THEN I suddenly decided **** this, I'm actually going to fix this shi* lol ( you know that moment when you just had enough and finally decide to bother doing something about it, ).. that's the moment I had..
Anyway to keep this simple...
After several hours of troubleshooting, testing and diagnosing , and trying to narrow down, isolate and fix the damn problem causing it to happen, I'm not sure 100% just yet but I may have found the problem and the fix to this IF the wifi "Hanging" doesnt occur anymore after doing some minor editing of the system files. (Only able to do with a rooted device) .
I will inform you guys with my results in a couple of days and hopefully the outcome is good news .. IF not, ill just have to keep trying and if all else fails ill just factory reset the device since getting everything back on to my phone will only take 30 minutes..
Peace!
Click to expand...
Click to collapse
Awesome, keep us posted if you find anything! I'm looking into it at my end as well FWIW, I have factory reset and even re-flashed the firmware multiple times with no improvement. Just trying to save you time and effort into reinstalling and stuff
Sweet as bro, thanks for the heads up.. Well so far I haven't noticed any dropouts of any sort as of yet. But I still have some things that I am testing.. Will update soon..
Sent from my Sony E6653 using XDA Labs
Well.. Here i am.. And unfortunately the issues still persisted.. To top it off, my phone decided to start having random moments where it would just restart on its on, even when left idle for a non specific amount of time. Anywhere between 1 and 3hrs.. I started getting really ticked off with it, so I decided to factory reset the device and install the latest (stock) firmware .253 from Sony using xperifirm and flashtool.. Flashed successfuly, applied latest andropluskernel, applied root, and xposed and also debloated the rom.. so far its been little over 12 hours and i havent really noticed any WiFi issues apart from the WiFi at some point tends to almost seem like it lags and slows down briefly and then just loads.. Not as bad as it was on previous firmware .225 .. Overall performance and battery on device seems pretty decent, without Amplify, without disabling any services or any system tweaks of any kind...
So now that I am onthe new firmware and rooted etc... I will as of this point specifically going to dedicate my diagnosticsand testing solely on the WiFi issue and see if I can find a permanent fix this time on the latest firmware..
Will report back soon.. Hopefully what I have in mind works..
(buffer size, WiFi chip power tweaks, WiFi sleep timers, etc etc etc)
Sent from my E6653 using XDA-Developers mobile app
I have tried looking through logs on the phone to try and diagnose with no success. Still trying here though
Sent from my E6683 using XDA-Developers mobile app
Dr. Mantis Toboggan said:
I have tried looking through logs on the phone to try and diagnose with no success. Still trying here though
Click to expand...
Click to collapse
Sorry its been a while..
Just been busy..
So far on the recently updated firmware (.253), I have not had any wifi issues as of yet. And it has been fine since my last post...
One thing ive noticed though is that by default the wifi scanning frequency is set to 180seconds by default.. If you can, try and change the interval between wifi scanning and see if that helps at all..
Sent from my Sony E6653 using XDA Labs
TheTecXpert said:
Sorry its been a while..
Just been busy..
So far on the recently updated firmware (.253), I have not had any wifi issues as of yet. And it has been fine since my last post...
One thing ive noticed though is that by default the wifi scanning frequency is set to 180seconds by default.. If you can, try and change the interval between wifi scanning and see if that helps at all..
Sent from my Sony E6653 using XDA Labs
Click to expand...
Click to collapse
No worries at all, I have too which is why I didn't see your reply for almost a week.
I haven't updated yet to .253, not sure how to go about it so I have been delaying. I've been poking around the forums here trying to see if anyone posted any instructions on how to upgrade if you are rooted on .224. In the mean time I will keep looking through logs and I'll try the WiFi scanning.
The crappy part is I recently turned on the fingerprint reader and I am also experiencing issues with that. Once or twice a day I get "fingerprint hardware not available" and have to reboot my phone to get that functionality back. I see others with the issue and it happens regardless of firmware so it's probably a marshmallow issue.
Dr. Mantis Toboggan said:
No worries at all, I have too which is why I didn't see your reply for almost a week.
I haven't updated yet to .253, not sure how to go about it so I have been delaying. I've been poking around the forums here trying to see if anyone posted any instructions on how to upgrade if you are rooted on .224. In the mean time I will keep looking through logs and I'll try the WiFi scanning.
The crappy part is I recently turned on the fingerprint reader and I am also experiencing issues with that. Once or twice a day I get "fingerprint hardware not available" and have to reboot my phone to get that functionality back. I see others with the issue and it happens regardless of firmware so it's probably a marshmallow issue.
Click to expand...
Click to collapse
All good..
Well you're gonna have to download the firmware from xperifirm and flash it via flashtool.. And since you're rooted with 224, you will have to download the new andropluskernel v34 for 253 firmware.. And TWRP custom recovery 3.0.2. specifically for the Xperia Z5. If you need help on locating the files/guides, I can link them to you, since we aren't in the right thread for this topic .. Just shoot me a PM if you need to and ill happily point you in the right direction.
Sent from Sony Xperia Z5 E6653
this WiFi issue is a headache, i just don`t know if all what i need is through my z5 to the wall and smash it -_-
E6653_32.2.A.5.11_R9C_Generic Global
and
E6653_32.3.A.2.33_R2D_Generic Global
i tried both firmware and WiFi problem is still exist, any solution ??
Safy4u said:
this WiFi issue is a headache, i just don`t know if all what i need is through my z5 to the wall and smash it -_-
E6653_32.2.A.5.11_R9C_Generic Global
and
E6653_32.3.A.2.33_R2D_Generic Global
i tried both firmware and WiFi problem is still exist, any solution ??
Click to expand...
Click to collapse
Z5 junk file / caching management is ****. That's why the Z5 has random wifi hangs
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Just as a follow up question, would the 'turn Doze off' option help with this? Surely I shouldn't have to do this though?
Am I the only one having this issue? That would suck. Even so, would anybody more adept at these things than me like to have a guess at solving the issue.
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Greedyfly said:
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Click to expand...
Click to collapse
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
smilirulz said:
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
Click to expand...
Click to collapse
I haven't 'cried' about anything, pal, so keep your unhelpful comments to yourself or help. Don't middle ground-it by offering your own personal, and incorrect, opinions.
I hadn't upgraded anything, I was running stock OS and stock marshmallow, so I had literally done nothing to my device other than switch it on and download the same apps I've been using for years.
I've also rooted several devices in the past with no issues and chime in when I can to help, but I'm not a dev and there are far more technologically gifted individuals operating in this forum which is why I sought help here... Not that I got much from you. But I'm more than capable of reading release notes and making sure I can revert backwards before installing anything.
Now to anyone still here, and with the same issue, it appears that carrying out the update to Nougat, re-adding my WiFi networks and clearing system cache solved the problem or at least for the first night. Should this change I'll update here.
ISO_Metric said:
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Click to expand...
Click to collapse
Hi Iso, thank you for your response, I hadn't seen this until now.
The upgrade to 4.0.1 does appear to have done the trick somewhat as it stayed on overnight without issue. I did notice it wasn't on a little later this morning but I am giving the device the benefit of the doubt on that one as I have been messing about with certain things and it's possible I or a profile in tasker switched it off.
As an aside do you recommend any other potential fixes, just to be on the safe side.
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
ISO_Metric said:
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
Click to expand...
Click to collapse
I didn't factory reset, only Cache wipe after the upgrade, and as it seems ok so far, I am reluctant to factory reset the device as it took so long to set up in the first instance.
Should it start becoming an issue again I'll try it but for now...
Also I know there are backup options though I haven't found one that works flawlessly which gives me the confidence to explore this avenue just yet.
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
ISO_Metric said:
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
Click to expand...
Click to collapse
Are you sure ISO? The UI has been updated and the already snappy OS feels snappier. Is there a way to tell for sure if it's required?
If so, any good recommendations for backup capability. I have used Helium to mixed results and I can't use Titanium as I have no root (and don't wish to).
Maybe not but it all elts fails