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?
Just as the title says. For example, if i set the time in android as the same of windows mobile and go to sleep, i am probably miss my bus-because after one night passes the clock will be nearly 12 min late.
Is there someone who could tell my how to solve this problem plz?
Lots of thanks.
icehust said:
Just as the title says. For example, if i set the time in android as the same of windows mobile and go to sleep, i am probably miss my bus-because after one night passes the clock will be nearly 12 min late.
Is there someone who could tell my how to solve this problem plz?
Lots of thanks.
Click to expand...
Click to collapse
Same here....
There is a problem with WinMo return from Android. My phone's hour is always incorrect. This is even after a hard reboot of the phone, even after pulling the battery. This does not happen with WinMo even if I set the time incorrectly and boot.
I know littlel of how our Android interacts with the phone's hardware. I have had a similar problem with Gparted. When trying to boot computer afterwards, the cmos was farklet and I needed to reset it.
hey all, question here. I have noticed this in the last few roms, not sure if this happens in stock, but i have been running cognition, currently 3.04 ( before that 3.02, 3.0 and 2.3b6), Occasionally I notice that after the phone comes out of sleep I see the clock go from example 1:30 to 3:30 or something like that. IS that a bug in cognition? or does the clock occasionally turn off when in sleep mode, and the reason for the lag sometimes be the phone cpu usage is doing some thing when i come out of sleep causing the jump to current time? or whats the reasoning behind this?
thanks.
JJ133169 said:
hey all, question here. I have noticed this in the last few roms, not sure if this happens in stock, but i have been running cognition, currently 3.04 ( before that 3.02, 3.0 and 2.3b6), Occasionally I notice that after the phone comes out of sleep I see the clock go from example 1:30 to 3:30 or something like that. IS that a bug in cognition? or does the clock occasionally turn off when in sleep mode, and the reason for the lag sometimes be the phone cpu usage is doing some thing when i come out of sleep causing the jump to current time? or whats the reasoning behind this?
thanks.
Click to expand...
Click to collapse
When the device goes to standby, all the widgets and screen updating apps are put to sleep to save battery. When u turn on screen, all these are refreshed. This is normal.
alright. Just curious, how come sometimes i see the clock go super speed to catch up, and other times it at the correct time? ( I usually dont see it, Ive only seen it maybe 5 times past month)
JJ133169 said:
alright. Just curious, how come sometimes i see the clock go super speed to catch up, and other times it at the correct time? ( I usually dont see it, Ive only seen it maybe 5 times past month)
Click to expand...
Click to collapse
No clue. Didn't go into so deep architecture I shall see if I can find out how it works internally when I get some time.
Thanks. Anyone else feel free to answer as well.
I am looking forward to your research. I am a techy as well, and not knowing why somethings happen and dont happen when it comes to things like this bug the heck out of me.
JJ133169 said:
Thanks. Anyone else feel free to answer as well.
I am looking forward to your research. I am a techy as well, and not knowing why somethings happen and dont happen when it comes to things like this bug the heck out of me.
Click to expand...
Click to collapse
As a more visible and more frequent occurrence, load a time app onto ur home screen. You can see it get updated when u turn the screen on frequently.
I think its more dependent on how many apps/widgets need to be updated when u turn ur screen on. I hardly have any on my screen so its a rare case I see the time update.
ok, so let me get this right, your saying it probably happens more often when i haven't used my phone in a while, because lets say I have things that update every four hours, and if the phones in sleep, and they haven't updated, they all could possibly be updating when i come out of sleep because there over due, thus sometimes causing the system clock to jump?
Any one else know anything ?
JJ133169 said:
lets say I have things that update every four hours, and if the phones in sleep, and they haven't updated, they all could possibly be updating when i come out of sleep because there over due, thus sometimes causing the system clock to jump?
Click to expand...
Click to collapse
All that u set for 4 hours to update, get updated but in the 'background'. The 'display' part of them is not updated, and is 'refreshed' when screen turns on.
Hey, anyone else got any theories or updates?
I'm using ultimate Rom, newest version as of a couple of days ago.
Just noticed this about 3 times in half an hour or less.
Interested in learning why I will see my clock jump from like 2:13 - 2:17 instantly at times when I come out of sleep...
a google search using different words found this :
http://code.google.com/p/android/is...ec=ID Type Status Owner Summary Stars&id=9524
Are there any devs here that could explain or potentially fix this issue ?
Reading all that worried me, thinking hey, maybe my alarm clock isn't reliable either...
I had this issue when I was running 2.1 stock. I haven't had the issue since flashing 2.2 (have used both cog 3.02 and andromeda 2.0).
Your link also seems specific to 2.1, and I believe is a known issue coming out of 'deep' sleep. I had some luck with app called 'load monitor'. It's free and has a setting I think is called prevent suspend that doesn't allow phone to go into deep sleep.
Not sure if re-flash might help since what you describe shouldn't happen running 2.2
i897 running Andromeda 2.0
Okay. But what are the chances of me repeatingly getting bad flashes? Ive been on cog 2.3b6, 3.0 , 3.02, 3.04 snd now ultimate rom. Sometimes i wont see it happen for weeks. Other times ital happen a few times in 30 mns.
Sent from my GT-I9000 using XDA App
Oh and reading through that link you see tons on 2.2 have that issue, not just 2.1
Sent from my GT-I9000 using XDA App
Yeah not sure. Really thought was general 2.1 issue, not just on captivate.
Try load monitor. I forget the setting there, but it'll prevent deep sleep. That or you could try app 'no led' and send yourself an email before going to bed (when active notification that app prevents deep sleep too).
Sorry those are lame options that'll affect you battery life to some degree. Perhaps there are better options posted here but you'll have to dig for it.
i897 running Andromeda 2.0
I'm assuming a ton of people have it but dont pay much attention to it expecially that it comes and goes in seconds.
Sent from my GT-I9000 using XDA App
Important topic bump.
Sent from my GT-I9000 using XDA App
Stil no fixes?
Sent from my GT-I9000 using XDA App
I've been on some or other version of the ROM I have in my signature, and never observed a clock lag so far. Maybe u cud try this ROM once. By the way, I am on xcal's kernel, and not the kernel supplied in this ROM.
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
jonmorris said:
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
Click to expand...
Click to collapse
Have done a factory reset? I've seen a few reports of reboots and soft-reboots and it could very well be user installed apps, settings and other stuff causing it.
Try a full factory reset and install the most "needed" stuff only. Try it for a day or two.
Sent from my C6903 using Tapatalk
I'm really not keen on doing that if I can help it. I'd sooner wait for an update, or someone figuring out what is causing the problem if there's a workaround temporarily.
Over the years I've done loads of resets and reinstalls, only to find it doesn't fix the problem and just wasted hours of my time.
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
travisb said:
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I've been at an exhibition today and it was quite embarrassing (and frustrating) to have it crash twice. Once when uploading the YouTube videos (as mentioned) - which fortunately resumed okay, and then later when I was trying to watch the Apple event (via The Verge).
One thing I've noticed from the beginning, is that changing settings sometimes required a reboot to take effect
Sent from my C6903 using Tapatalk
I'm not expecting much, but I'm now downloading the Central Europe FTF and will flash that to see if it makes any difference at all (currently on commercial/journalist version).
Anything I can try that won't force me to start from scratch has to be worth it.
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
In the interest of scientific research (and reading the high CPU thread) I've backed up my sd card, re formatted it and just copied the music and DCIM folders back in, to see if that makes any difference. Card is genuine SanDisk 32gb class 10 card. Watch this space.
Sent from my C6903 using Tapatalk
Gitaroo said:
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
Click to expand...
Click to collapse
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
jonmorris said:
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
Click to expand...
Click to collapse
Glad to see Sony keeping up with the updates
I have the same problem with the Z1. Also on ...257 and using 4G/3G. On the old firmware the phone hard-crashed several times and needed at 'hard-reset' at the simcard. But that happens not now - only 'soft restarts'. But very annoying. It happens both when using the phone and when its idle (in the night for example it restarts several times). You can see the restarts in the log on the phone.
I have some 'old' samsungs and they almost never restarts (sometime app's closes - but thats different) . I didn't expect such an unstable product from Sony when it's so expensive.
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
jonmorris said:
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
Click to expand...
Click to collapse
I've not had a single random restart.. I've been on Global LTE firmware for a week and have just changed to Central Europe one.. Will report if anything happens...
Two this evening with central Europe firmware, so clearly need new version ASAP. It's almost getting to the point where I can't use it because reset will happen at any moment.
Yes, also had 2 in last 30 minutes. So sd card reformat not a cure.I've contacted @SonyXperiagb on Twitter to see if they are aware of problem.
Sent from my C6903 using Tapatalk
it is a bug on sony fw and appear on google 4.1 - 4.2 android. it has something to do with wifi sleep power policy and wakelocks, im not sure. I had experience this problem with many devices on 4.1 and 4.2, include samsung ones. The easiest way to fix is to reset to factory and trace back your steps, anything to do with wifi (auto update, auto upload) is the culpit. Or if you can remember, try to trace back so you dont have to factory reset .
on .534, i had this problem when turning on update via wifi only in update center settings, get sod and constant restarts. disable it does not help, only to find out has to reenable again backlight optimisation.
Good luck!
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
jonmorris said:
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
Click to expand...
Click to collapse
the fix are only those i told , further more updates will fix it but you can do it manually your self
A factory reset with a whole world of pain, and no guarantee it won't still mess up, isn't really a solution to me. Sorry!