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?
Hello!
TW stops working several times a day, I've haven't managed to narrow down the apps that might crash it (unless everything I use on the phone crashes it). It sometimes crashes in the home screen, in Chrome, in YouTube. The two apps I use the most are WhatsApp and Facebook, and it has crashed when I'm using them, too.
I have the habit of pressing the home button to leave an app, and the phone always takes a little bit to reload all the icons. I know TW lags and stutters for many, this is not a complaint but an observation. I used phase beam as the wallpaper before, so I changed it to a solid black picture. That hasn't helped.
My phone is not rooted, though processes unused are stopped in App Manager.
Any assistance and suggestion would be much appreciated. Thank you.
Reset phone
BAD ASS NOTE 4
Hey guys,
I am facing the same issue, where TW crashes and I receive the message that TW has stopped working, however in my case it happens each time I reboot the phone. Once I OK the error message, TW reloads, and remains stable until I next reboot my baby, which I tend to do once a day, for good measure. This is not the end of the world, something I can live with, yet I do find it irritating that I cannot figure out what is causing this.
Anyone with a suggestion would be greatly appreciated. FYI, I am running stock at the moment.
Regards,
Raziel
I'd be tempted to odin to stock or flash firekat.
Raziel, I cleared TW cache and then wiped the cache partition earlier this afternoon. It seems TW hasn't crashed as often as it usually does, but it has crashed. It might remedy your problem, though, if you haven't tried this already. I'm avoiding resetting my phone.
If you rooted and tw goes crazy on you something went wrong. Delete everything you got. Turn of antivirus software. Download everything. Start by going back to stock then update then root then your good to go. If you start with a bad hicupp it will just keep getting worse.
BAD ASS NOTE 4
ChinWonder dude! Thanks a bunch for this suggestion... I cleared TW cache in Application Manager, then booted into Recovery and proceeded with wiping the cache partition. Honestly I feel like a bit of a noob right now LOL, I should have thought about this myself!! But hey thanks nevertheless, much obliged .
BACARDILIMON, as stated above by the OP, ChinWonder, as well as myself, in both cases the devices are not rooted. Thanks for the effort though . I'd like to add however that all of my previous and current Androids (S2, S3 and Nexus 7 2013) have been rooted, and in the last 2 cases, on day 1... hell I even made my own custom ROM for the S3 based on stock Bell 4.1.1 and stayed on it despite several available upgrades, I was getting such good performance and battery out of it, and FULL compatibility since I used a firmware base from my carrier, which is not the case for most custom ROMs found here, since none of them (or close to) are using Bell, but AT&T in most cases. From my experiences, I was always getting issues receiving voicemail notifications when using those. Long story short, I have been on the flashing bandwagon for a few years now, and tweaking the hell out of all my devices up to now, but this time, I feel this is the perfect (ok nothing is perfect) smartphone for me, as is, stock, and it performs like no other device I've had until now, and battery is just incredible!! getting regularly well over a day of charge, mostly average 36 hours, with 6 to 8 hours screen on time!!! WOW!!! seriously for the time being, I don't feel I want to root and flash and all that jazz, but instead I just want to enjoy this beast, the way Samsung thought of it, for a little while.
Again ChinWonder, thanks!
Raz
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.
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
I'd recommend flashing a rom like pure nexus, super stable that should fix your problem, otherwise you've done all you can and is the easiest fix
Sent from my Nexus 6 using Tapatalk
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
5.1 said:
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
Click to expand...
Click to collapse
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
lchiu7 said:
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
Click to expand...
Click to collapse
Hello,
Don't worry, it's really easy. Also, if you are lost, there must be a ton of tutorials in general section. If you are lost yet, just ask and someone will point you in the right direction...
Good luck...
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
I've been running Pure Nexus and wanted to let peeps know I put Nitrogen on and man it's so smooth, my wifi tether is back and I went to sleep last night with 50% battery still. When I installed it I opted for the nano gapps I think so like 175mb for minimal apps and maybe that's why it's running so efficient. Maybe I could have re-installed Pure Nexus with a clean install and it would have gotten better but it was a good time to try something else. Also when Nitrogen got an update I was notified just like stock and it downloaded. I didn't even know these could do that. Anyways give it a try and you might just switch back. I was looking into new phones but if it keeps working so smooth with battery longer than a day then I'm fine for now.
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
zelendel said:
... It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
...
Click to expand...
Click to collapse
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
NLBeev said:
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
Click to expand...
Click to collapse
Currently I have FB, FB messenger, and Chrome but when I installed gapps I chose a super lite install so tons of bloat and google apps were not installed and my battery has gone way up and it's so smooth. I'm sure even when we don't use apps they're always doing something in the background. I bet you're right and a stock lite ROM would be good too with the minimal bs apps.
zelendel said:
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
Click to expand...
Click to collapse
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
lchiu7 said:
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
Click to expand...
Click to collapse
I would flash TWRP, flash supersu in TWRP to root, make a complete backup in twrp, then remove whatever Google apps you're not using with a system app removal app. Getting some of that bloat off the device should help. If it's still laggy, then look into a custom ROM. I run Tesla on my Nexus 6 with none of the issues you're having. I don't decrypt it either
Running abdroid 7.1 here. I dont get any slowdowns, at leas until the battery doesnt drop below 50 and 25 percent.
Im running a custom kernel and my phone is rooted. Everything else is stock.
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
lchiu7 said:
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
Click to expand...
Click to collapse
Hello,
Since your bootloader is unlocked, flash TWRP and install the kernel, no problem.
Might give you a slight boost at first sight, but your device will likely slow down over time anyway...
Cheers...
I'm on 7.0 with the April SP. I have dozens of apps installed, including Hangouts. I use Firefox for browsing, I like it better than chrome (and you can install an ad blocker).
My camera slows down when the battery is under 40%, and the whole device slows dramatically, though not unusable, at or below 5%. But otherwise, no issues what so ever.
One solution that I have not seen suggested here is resetting the device and NOT taking the Google account backup of all your apps. I would suggest making a completely clean install of the factory rom you have and installing one or two apps at a time, most important to you first. And do this for a few days/weeks until you find the app that's misbehaving.
Although there are general bad players out there, this bad app could be unique to your device. Just because all devices of the same model have the same specs and components, doesn't mean that there isn't variability in parts quality.
I would do this before trying any new roms or kernels. Find the true problem first.
Good luck!
edit:
I had another idea: Go into your battery stats and network stats and storage stats and see if any app seems to be using too much of any, or all of the 3. This may get you the answer more quickly.
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.