i am truly sorry about srating a new thread (poll) on this, but i didnt find out how to change the poll options... >.<
thanks for the feedback, definatelly gona get this phone now at last lol
Once a day or something, randomly. Sometimes I can go days without any reboots, sometimes it happens a few times a day.
And LG just postponed the fix... lol
Sent from my LG-P990 using XDA App
Since using custom roms like Modaco rom ( tried fr12 and 17 and both where realy good and very stabel roms ) or cyanogenmod (.31 better battery life then modaco ) i didnt had one freez or something like that. My O2X runs very well and smooth.
I had a lot of problems with the Stockroms ( Vodafone Germany) like freezes, bootloops, batterydrain etc...
greetings
3 times a day on stock Rom.
My second handset totaly stock 1 bsod in 3 week look at the up time
Never
many weeks with many ROM changes!
Meltus said:
Never
many weeks with many ROM changes!
Click to expand...
Click to collapse
How often do you use WIFI and how long when using?
Never had it with stock rom, once with custom rom. I bought two months ago.
Sent from my LG-P990 using XDA Premium App
The poll should be changed this way:
- 10-20 times (or more) per day
- 5-10 times per day
- 1-5 times per day
- 1-5 times per week
- Never
If the phone got problem, it will always freeze.
that mean, the phone will NEVER work stably for the whole week (in case of you got problem phone)
My phone reboots time to time... can't pinpoint a reason though
1.no random reboots
2. no backlightbleeding or something else
3. @ 1500 Mhz got only 57° after 10 minutes of stress testing
I´m a lucky men with a good phone
Well i voted 0 reboots but right now i had something strange that was a reboot... i'm standing next to my phone and it was on and ok. Next i pressed power to make a call and it was asking for my simcard pin. So i guess it rebooted but didnt made any sound .... is this the usual random reboot?
nunomeneses said:
Well i voted 0 reboots but right now i had something strange that was a reboot... i'm standing next to my phone and it was on and ok. Next i pressed power to make a call and it was asking for my simcard pin. So i guess it rebooted but didnt made any sound .... is this the usual random reboot?
Click to expand...
Click to collapse
well from what i know it could be it, but hey, basically ALL phones have some reboots every once in a while.
for how long have you had your phone ?
I have the phone since monday and i had 2 times the simcard pin asking but the 1st i thought it was me but can see it wasnt ...
Sent from my LG-P990 using XDA App
Something will auto reboot or shutdown and no reason. But changed custom ROM was fix the reboot bug, however, the phone also always auto shot off. Waiting v10e, hope can fix all issue.
Sent from my LG-P990 using XDA App
mine never reboots.
and the Poll is weird...
1 time per week? make it 2-3 times per week. cause 1 time per week can't really justify anything.
Same here, mine never reboots.
Owned the phone since release.
Sent from my LG-P990 using Tapatalk
I got frozen state i think twice in 2 weeks. Last one was today. But also twice i got forced reboot, since GSM module simply lost signal and was not reacting till restart.
So if ~40% of O2x users here don't suffer from issues, wouldn't that indicate that there isn't really a problem with the firmware? Rather it would indicate that there are defective O2x units being sold.
Ergo, if the defect is indeed due to a hardware problem, then any "fix" that LG releases is a workaround to the hardware issue - and not true remedy. The only remedy to a hardware issue would be a replacement.
Just something to think about - for all those waiting for LG's magical "fix".
Related
I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!
deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm
If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.
Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.
jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse
eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.
Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!
ryunbaik said:
Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!
Click to expand...
Click to collapse
Hi
So you want to say SuperSu fixed your SOD?
What are the other settings of Devil kernel? Could you please share them
thx!
Yes more info would be nice. Right now I am fighting with my phone SOD about 5-8 times per day. Sucks.
as for me I keep "Captivate Keep Alive" till 70% of battery
then it turns off ..
My battery last about a working day - so it is somehow could be called "fine"...however I would prefer to NOT use wakelock progs....
I'm using Devil kernel too and Lanight ROM.
So please tell us more details: ROM version, kernel version, kernel settings ....etc...
Sorry for late response!
Sorry for the late response guys.
I thought it was the rooting to cm10 and SuperSu that did the trick, but apparently after rooting the phone, I started downloading all the Apps that I wanted to make my phone look cool. As silly as it sounds I installed World Weather app for clock and weather... oddly enough this thing keeps my phone from going to sleep. I realized this because after uninstalling it, going for a different look, I downloaded Rings Digital Weather and my phone started to turn off every 30 minutes again. Let me know if it works for you guys... cuz seriously this was the last thing I would've turned to to fix my phone
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!