Hi all, I have a Lumia 1020 USA AT&T model with WP8.1 and all the latest updates from the Preview for Developers installed. I have a problem where my Lumia will turn off or at least I think it's off. Most of the time a soft reset will cure the issue but I'm wondering if anyone else has this problem?
It pre-dates WP8.1 and was happening with WP8 too. Today for example, I didn't charge the phone last night and I think it dies earlier this morning but after plugging it into power, again nothing. No beeps, no signs of life, nothing. I did a soft reset and it's back. I'm beginning to think that it could be an app...
Besides a hard reset, does anyone have any suggestions for me to try? I think that's going to be the end result but I thought I'd ask first. Let me know if you have any suggestions.
Cheers.
Same problem
I'm having the same problem, mostly at night. There are other people with this issue. Nokia has exchanged phones for some.
I did the hard reset but that did not fix the problem. I'm trying other things -- uninstalling apps and turning off battery saver -- we'll see if it works.
My firmware is 3051.40000.1346.0001, unlocked AT&T phone running WP8.1 Dev preview. Is there a newer firmware?
Related
Im having a problem with my 820 and its pretty darn annoying. Every one and then it just turns off and the only way to turn it back on is to take the battery out. Anyone else having this problem?
Yep
http://forum.xda-developers.com/showthread.php?t=2021800
Hope you get it sorted.
Yep, I had it once, it was just after I paired it via bt to my car but it hasn't happened since.
Sent from my RM-825_eu_euro1_217 using Board Express
I think the system update released yesterday fixed this.
Yep, instead of taking out the battery, turn it on while holding volume down.
jambo89liam said:
Yep, instead of taking out the battery, turn it on while holding volume down.
Click to expand...
Click to collapse
thats doesnt even work... have to take out the battery.
This crap happened 3x in the last 24h. Phone is going back and I regret that I didnt take another Android phone...
Had to send mine back, Bear in mind this is a hardware issue and not related to the OS as my replacement is working faultlessly, Androids have their hardware issues too and I have had to send many a HTC back for repair, Am none too impressed with Nokia ATM as the wifes Lumia 900 has just had to go in for repair with a non working loudspeaker
AndyFZ1S said:
Had to send mine back, Bear in mind this is a hardware issue and not related to the OS as my replacement is working faultlessly, Androids have their hardware issues too and I have had to send many a HTC back for repair, Am none too impressed with Nokia ATM as the wifes Lumia 900 has just had to go in for repair with a non working loudspeaker
Click to expand...
Click to collapse
I agree, this is Nokias last whistle if they want to survive in the phone market and so far they are blowing it... ;/
I got a Lumia 820 for X-mas with the same error.
I have update the firmware to verion 1232.5951.1249.1003 and there is still this problem where the screen is turned off and I have hold down power and "volume down" button to restart the phone. It is very annoying, special when the alarm is not working in the morning.
Is there a software/firmware solution to the problem or is it a hardware error in the phone?
I found this at nokia forum:
http://discussions.nokia.com/t5/Nokia-Lumia/Lumia-820-freeze/m-p/1613474/highlight/true#M25637
I will try to turn off speech in setting and see if the phone will continue to freeze
I gave mine into to get replaced... Pissed me off too much to try and fix it.
MortenRJ said:
I got a Lumia 820 for X-mas with the same error.
I have update the firmware to verion 1232.5951.1249.1003 and there is still this problem where the screen is turned off and I have hold down power and "volume down" button to restart the phone. It is very annoying, special when the alarm is not working in the morning.
Is there a software/firmware solution to the problem or is it a hardware error in the phone?
I found this at nokia forum:
http://discussions.nokia.com/t5/Nokia-Lumia/Lumia-820-freeze/m-p/1613474/highlight/true#M25637
I will try to turn off speech in setting and see if the phone will continue to freeze
Click to expand...
Click to collapse
After 4 days with the Speech settings turned off have the phone only freezed one in that time. The phone used to freeze 3-4 times every day. The phone af been constant turned on and I can use the alarm to wake up in the morning.
Update:
Today the Lumia 820 freezed. The only thing have have changed is that the Bluetooch have been turned with my headset, used and then turned off again.
got my phone back today... Unfortunately its the same phone... reflashed. Reinserted my SIM... 30min and it froze.... THANKS NOKIA! First and last phone from you.
That really is bad work from Nokia, I ended up selling my O2 replacement as got short of cash but cannot fault O2 as they did replace my faulty handset.
I am now debating whether to get another Nokia as had nothing but trouble with all of the Lumias me and the wife have owned, From Proximity sensor failures to loudspeaker to Device not waking up,
Think they really are in trouble now as they have shifted yet another 1000 workers
AndyFZ1S said:
That really is bad work from Nokia, I ended up selling my O2 replacement as got short of cash but cannot fault O2 as they did replace my faulty handset.
I am now debating whether to get another Nokia as had nothing but trouble with all of the Lumias me and the wife have owned, From Proximity sensor failures to loudspeaker to Device not waking up,
Think they really are in trouble now as they have shifted yet another 1000 workers
Click to expand...
Click to collapse
They are definately in trouble. This was there last chance and they blew it. Shoulda gone Android when they had the chance and not bash it. Some really good looking phones with crappy software.
Time to go b*tch at the guy from the store again.
Possible Solution !!!!
THIS IS NOT MY COMMENT, only copied from http://discussions.nokia.com/t5/Nokia-Lumia/Nokia-Lumia-920-freezing/td-p/1604040/page/13 from user CloudStrife
I think there are many problems all software related. I wonder if all the Lumias were made using the same hardware, i.e. the same wlan adapter, the same video processor etc etc... if the answer to this question was NO, then there might be compatibility issues with the driver for different components.
Some experience the issue with the WLan I read, I exprienced that with the data network, leaving it only WLan never made it freeze. Some others with the "find my phone" option. That maybe could explain the crashes during the night?
However... I found and tried to follow a suggestion that one user reported coming from both Microsoft and Nokia, and surprisingly it seems to have fixed my issue.
I removed the SIM, then turned up the phone and left it on for 10 minutes (I read that when the "no sim" message appears, some files are supposed to be deleted, and written again when the SIM will be put back in the handset and recognized as new).
Then I shut it down, inserted the SIM back, and turned it on.
It has never frozen again, it's about four days.
My issue was when I had both network data connection and WiFi, or when I had only network data connection but with low service so it was often switching between 2G (Edge) and 3G data connection.
From when I tried that I left enabled both WiFi and network data, and it never froze again.
I don't know if it's a definitive solution, but I hope so.
What I'm pretty sure of is the fact that if I left both WiFi and network data enabled before, it was a matter of hours for it to freeze.
I hope that my experience can be helpful for someone... at least, it worths a try.
OR
Try this:
If automatic date/time settings are on, the phone freezes if there is problems with the date/time sync:
1. On Start, flick left to the App list, tap Settings , and then tap Date+time.
2. Tap to toggle Set automatically to Off.
3. Perform a "Soft Reset", i.e. press and hold the power button and volume down button for about 10 seconds; the phone should vibrate and reboot your phone.
4. After reboot date+time should be wrong! Thus, on Start, flick left to the App list, tap Settings , and then tap Date+time.
5. Tap on each of the options to set your current Time zone, Date, and Time. When you're done, tap the phone's back button.
IMPORTANT Don't turn on automatic date+time setting again!
OR
It is the Network + update and affects everyone!
after software update ,not switching on
after the windows software update automatically my lumia 820 gone for restarting,, after that it shows nokia logo and gone off again,, now my phone is not switching on,, is there any problem happen with the software update? how to recover from this problem?
Hello all, having an issue with the accelerometers on my SGS5.
So, got it on Sunday. Had it home and doing the usual thing... installing apps and configuring services. Noticed the battery was being nuked... checked what was using it... and gsiff_daemon popped up. Er, little bit of digging and I think this might be related to the sensor suite. Honestly not entirely sure because I didn't dig overly deep.
Checked again a little later, and well... it was gone from the list, and the battery was performing much better. Unfortunately now the accelerometers don't work. I'm guessing the service crashed or something. Lived with it for a day or so, and late last night I did a full factory reset on the phone. Hey look, accelerometers are working again. Go to bed (around 3AM PDT after the eclipse) wake up this morning and the accelerometers aren't working again.
Is there any way I can check to see if gsiff_daemon has crashed (if that's even what I should be looking for). I tried a sensor testing app and at least confirmed that sensor data isn't being logged.
Any help on this would be greatly appreciated.
So, little bit of an update. It has to be a service that's crashing. Sometimes if I do a restart, the accelerometers will come back online and be working. Within the first few minutes they will stop working again.
So yea, one more update.
Doing a regular restart doesn't fix it. I have to do a soft reset (pulling the battery on shut down) for the accelerometers to come back online, and they still don't last very long. Wondering if this is an issue I need to take back to Sprint and get fixed. Hope not.
Probably software/app related.
The phones don't truly power off on restart/power off thus why the battery yank need.
I doubt you need an exchange but you can probably try factory reset.
bryanu said:
Probably software/app related.
The phones don't truly power off on restart/power off thus why the battery yank need.
I doubt you need an exchange but you can probably try factory reset.
Click to expand...
Click to collapse
So, found what might be the culprit... and it's something familiar to Note 3 users out there... com.sec.android.sviewcover seems to be the issue. I'm checking to see if disabling the lock screen solves the issue (it's something like a slow leak, or intermittent failure... resetting com.sec.android.sviewcover fixes it without a reset).
I'll post again with overnight results.
Arkanthos2015 said:
So, found what might be the culprit... and it's something familiar to Note 3 users out there... com.sec.android.sviewcover seems to be the issue. I'm checking to see if disabling the lock screen solves the issue (it's something like a slow leak, or intermittent failure... resetting com.sec.android.sviewcover fixes it without a reset).
I'll post again with overnight results.
Click to expand...
Click to collapse
So, went ahead and did a full factory reset on the phone. Even swapped the cover back to the stock back and the problem persists. Looks like I might have gotten a lemon. Going to take it to a Sprint store soon to get it replaced. Confirmed with the manufacturers own on-board diagnostic *#0*# that it's not just the accelerometers that are failing it's also the compass, barometer, gyroscope, proximity sensor, and HRM sensor. Kind of a bummer... but hopefully this thread will help anyone else out there having these issues.
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello folks,
My mothership made a suicide attempt (sudden bootloop) and showed some strange behaviour recently. It was solved sort of with a reset, but since the problem could not be replicated I figured it must have been a software fault after one of the many little updates Sony has pushed out recently gearing up for the Lollipop.
So I decided to do a software repair. So far so good, but for some strange reason I am stuck on an older version of What's New. Could this possibly be a server issue with Android 5.0 on the way?
Also, is there a good way to check for hardware problems? I am going to run some benchmarks but any input would be appreciated.
(I am on stock, unrooted btw)
I sent it to Sony for repair.
Last night I went to sleep with 75% of battery and I woke up with it completely flat. No drain, no identifiable cause. Just BAM. Dead.
So for now it is back to my old cracked S3 and wait for a few weeks....
I have a very weird issue with my HTC U11 plus:
When the screen is off (the device is asleep, not turned off), pressing the power button or using the fingerprint sensor turns it on, but there is a random delay, between 5 and 20 seconds, where the screen stays blank.
Additionaly, the Edge Sense is absolutely unreliable: there is again a delay of between 5 seconds and 35 seconds.
It has started doing that last week.
I tried factory resetting it today, but I get the same result. I have opened a ticket at HTC, but as it is out of warranty, I don't think they'll be able to help me...
Has anyone ever seen such an issue?
Did you solve this？
I have this problem too and my camera also have delay when i open.
I tried flash the stock RUU,but it's no use.?
No, unfortunately not. HTC support said they could repair it but as it was out of warranty they gave me a quote for several part replacement they might have to do, and it cost the price of a new handset (500 euros for a motherboard replacement) so in the end I went with a new handset
It's so unfortunately.?
I have the exact same issue and from the last weekish or so, and no luck fixing it or finding out what is causing it. Also tried factory reset, safe mode doesn't help. Randomly its ok at times but typically 5 seconds to wake from sleep mode. Ive done no system updates. And yes camera is affected, almost feels like CPU tied up doing something.
running android 9
software 2.20.709.2
kernel 4.4.153
It must be an APP issue causing this, does someone have the issue on a rooted device to see what's using the CPU. Once its out of sleep mode for a bit its all ok and runs normal.
---------- Post added at 02:42 PM ---------- Previous post was at 02:11 PM ----------
Hi edzilla,
Did you try another ROM, or does anyone with the HTC u11+ not have this issue and if so what ROM/stock version are you on?
I believe I was on the latest update when it happened, and that that there wasn't any update before it started happening.
ill try rooting/aftermarket rom later to confirm if its hardware.
i downgraded back to android 8 RUU and the issue is still there. i have not tried non stock rom yet but this seems like a hardware issue with the screen or CPU once its in full sleep mode. is anyone running a decent alternative rom i can try?
Anybody found a solution? Like with a different ROM? Or confirmed it is hardware?
I have the same. Came out of the blue. First it was draining the battery. That has stopped now. But since a couple weeks, huge delay when starting. Up to 25sec.
Thought it was an app. So did a hard reset, wiped everything. But even without any apps installed, still the same delay when starting from standby.
Android 9
software 2.19.401.2
kernel 4.4.153
Is it worth putting a different ROM? Don't want to waste a weekend...
So maybe better directly getting a new phone? Any thoughts?
Thank you!
ForSH-3719 said:
Anybody found a solution? Like with a different ROM? Or confirmed it is hardware?
I have the same. Came out of the blue. First it was draining the battery. That has stopped now. But since a couple weeks, huge delay when starting. Up to 25sec.
Thought it was an app. So did a hard reset, wiped everything. But even without any apps installed, still the same delay when starting from standby.
Android 9
software 2.19.401.2
kernel 4.4.153
Is it worth putting a different ROM? Don't want to waste a weekend...
So maybe better directly getting a new phone? Any thoughts?
Thank you!
Click to expand...
Click to collapse
I couldn't find a good rom to try and never found a fix for the slow wake issues.. still happens in safe mode so not an app. Most likely hardware.. gave to my daughter who can deal with the issue better than me.
jaya21 said:
I couldn't find a good rom to try and never found a fix for the slow wake issues.. still happens in safe mode so not an app. Most likely hardware.. gave to my daughter who can deal with the issue better than me.
Click to expand...
Click to collapse
Then won't spend time - served me well for 3+ years.
Will get a new phone...
Thanks a lot for letting me know.