Alarm Clock doesn't turn on when phone is powered off? - Nexus S Q&A, Help & Troubleshooting

My Nokia N900 & N8 both had alarm clocks that would work even when the phone was completely shut down. Tried out the Nexus S alarm clock today and it didn't go off when powered down. Luckily I had a backup.
Is this normal for smartphones today? I've been with Nokia for quite a while.

ruprick said:
My Nokia N900 & N8 both had alarm clocks that would work even when the phone was completely shut down. Tried out the Nexus S alarm clock today and it didn't go off when powered down. Luckily I had a backup.
Is this normal for smartphones today? I've been with Nokia for quite a while.
Click to expand...
Click to collapse
I'd never expect my phones alarm to work when it's off. As far as I know with the 2 android phones I've owned, this is normal.

That's too bad. It's a feature I found very practical in my Nokia phones. I suppose if I want to use it as an alarm clock, I can leave the power on while plugged into USB. A weakness of the N900, however, prevented the phone from keeping a full charge the next morning if I did not power it down the night before.

Someone will have to correct me if I'm wrong, but I believe those two Nokia models you talked about don't actually "turn off" but rather go into a super deep hibernation mode, like some of the Blackberries and the MT4G/Desire HD/Desire Z(with "Fast Boot" enabled, and not to confuse with the flashing system), which would explain why your alarm still functions even when the phone is "off."
Most Android Phones don't have this feature, in fact, the only ones that do(as far as I know) are the ones listed above.

I never switch my phone off overnight, but this alarm situation surprises me.
Like the OP, I'm used to phones being able to switch themselves on for an alarm to go off, and took it as standard, as all my previous phones had this feature. Funny the way modern phones seem to have taken a step backwards in some areas.
Although I suppose, with the time it takes for the Nexus S to boot, the alarm will be slightly late anyway.

Corvidd said:
I never switch my phone off overnight, but this alarm situation surprises me.
Like the OP, I'm used to phones being able to switch themselves on for an alarm to go off, and took it as standard, as all my previous phones had this feature. Funny the way modern phones seem to have taken a step backwards in some areas.
Although I suppose, with the time it takes for the Nexus S to boot, the alarm will be slightly late anyway.
Click to expand...
Click to collapse
The two phones I owned previous did not have to "power on" for the alarm clock to work. Alarm would go off as planned, and when I either turned alarm off or hit snooze, I would then be prompted to power the phone on. The N900 takes about twice as long to boot up as my Nexus S, so it would have been just as impractical had it had to boot up before alarm functioned properly.

Apologies for misunderstanding you. I share your concern for the fact that something as basic as an alarm which can go off when the phone is switched off is not implemented on such a top device.

install Alarm Clock PlusV2★ and the problem is gone
http://forum.xda-developers.com/showpost.php?p=8124064&postcount=44

unremarked said:
Someone will have to correct me if I'm wrong, but I believe those two Nokia models you talked about don't actually "turn off" but rather go into a super deep hibernation mode, like some of the Blackberries and the MT4G/Desire HD/Desire Z(with "Fast Boot" enabled, and not to confuse with the flashing system), which would explain why your alarm still functions even when the phone is "off."
Most Android Phones don't have this feature, in fact, the only ones that do(as far as I know) are the ones listed above.
Click to expand...
Click to collapse
no, the nokia phones turned completely off, no deep sleep or anything. i'm a nokia nut using near every symbian phone until my first android phone nexus one.
and to the OP, you are out of luck. no android phone does what nokia does with the alarm. if the phone is off, the alarm doesnt work. kinda stinks i know.

I'm fairly sure some form of 'deep hibernation' exists, else how would the device know what time it was when it was turned on? It can do it without signal. The phone is kept running at a very very low rate, which is why it could, theoretically, be woken by itself.

Corvidd said:
I'm fairly sure some form of 'deep hibernation' exists, else how would the device know what time it was when it was turned on? It can do it without signal. The phone is kept running at a very very low rate, which is why it could, theoretically, be woken by itself.
Click to expand...
Click to collapse
because even if you pulled out the battery, popped it back in but never turned the device back on, the alarm will still turn on at the right time that you set. its rather easy to do with code i believe.
you have to have owned symbian phones to understand i guess is what it seems like.

AllGamer said:
install Alarm Clock PlusV2★ and the problem is gone
http://forum.xda-developers.com/showpost.php?p=8124064&postcount=44
Click to expand...
Click to collapse
Will this one really turn NS on?!??

Related

Random shutdown solution!

Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem

[Q] Another G2x noob, is my phone going to be a lemon?

I'm kinda hesitant to post this, because I know you guys go through great lengths to emphasize searching first. I watched the video when I registered, nice touch. More forums could use vids like that!
oh well, here we go:
I have owned an Iphone every since they where introduced to the market. I have been wanting to make a switch for a while now. I was very close to purchasing a G2x back in April when they came out, but I held off. Well recently, a coworker let me check out his HTC G2 and I was amazed at the functionality, features, and other misc items compared to my old Iphone 3GS. I was never a fan of the slide out keyboard, so I knew the G2 was not for me.
Last week, I just missed the free promo on T-MO's web site, so Instead I purchased a G2X locally. I was totally unaware of all the problems you guys where having, as the typical review sites never mention these issues.
I have owned the phone for 8 days, So far here is whats been a going on:
7-29-11 Purchased the phone from Best Buy, decided to buy from them since they where the cheapest out the door with out rebate. I hate rebates! lol
Right before I am going to bed, I plug in to charge, and the phone shuts off, I cannot get it to power back up. I did not know about pulling the battery, I thought it had just died. I was going to wake up the next morning and take it back.
7-30-11 When I woke up, I looked around online, and found out about removing the battery and putting it back in. Now phone is working again.
I was able to get the OTA update to 2.3.3, right after the update, I did a master reset.
8-2-11 I downloaded a "radio scanner" app, and the first time I executed it, the phone froze, requiring another battery pull. Afterwards, the app ran fine.
Those are the only 2 major issues I have had.
Here are a few other things I noticed:
Screen: No separation, very slight light blur around top corners with lit black screen. Does not bother me, and I can't really notice it 99% of the time.
GPS: I know some have been having issues with this, for me, The time to get an accurate fix can sometimes take anywhere from 5-30 seconds. Even with the stock toggle always turned on, I do not always have the GPS Icon in the top bar, I don't know if I am supposed to. Can someone please confirm this?
WI FI: Seems to be working like intended, no complaints there.
BT: I have nothing to pair with the phone, so I will probably never know.
Making calls: this is kinda annoying, I will look through my call log and select a person, I see the dialer initiating so I put the phone to my ear, but a few seconds go by and nothing.... I look at the phone and find myself looking at the call log again, like the dialer crashed? Also, during the conversation the screen will turn off. I think this is normal, but when the phone detects motion shouldn't the screen turn back on?
Other than that, I love this phone so far. However, I do not want to swap handset after handset, refurb after refurb with T-MO or LG.
Is it possible that the phone will NOT continue to get worse as time goes on? Or should I take the first shut down as a sign of whats to come in the future? I have a 6 days left to take this thing back, but I am having a major conflict with myself about keeping it. What makes it even harder, Is I have already ordered a 32g micro SD, Trident case, and 3 extra data cables.
My plans are to root it, and run some sort of rom with it once I read up and half ass know what I am doing.
---------------------------------------------------------------------------------------
TLDR:
Have owned phone for a week. Shut down instantly the first time I charged it requiring a battery pull. Froze/crashed due to an app maybe Second battery pull.
Question a few functions but otherwise works like a champ.
Purchased case, micro sd, extra data cables.
thinking of taking it back and cancelling contract to avoid future headaches, but not sure if I should or want to at this point. need avdice please!
Doesn't sound like a lemon. The stock software is buggy. If you're gonna root it and flash another rom then you're gonna love this phone.
The GPS indicator is normal. It only shows when an app is using GPS for your location. Otherwise it doesn't show.
G2X CM7
It doesn't sound like a lemon to me either. I bought mine in April and my phone had a few reboots while charging overnight and two freezes in the first month. It has been OK since then, although I did not do anything about it (and I'm still on Froyo). The only thing I do is that I reboot my phone manually once in 7-10 days because the phone starts to lag. I believe this is normal for all smartphones including iPhone...or am I wrong?
Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.
HTXg2x said:
Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.
Click to expand...
Click to collapse
The lockscreen issue is a known bug. CM7, or any ROM with 2.3.4+ doesn't have that problem.

[q] major bugs in samsung droid charge

Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
I haven't experienced any of the problems you bring up.
Sent from my Gummy Charged GBE 2.0 using xda premium
1. Are you sure that you are not pressing the power button while in the camera application. Doing so will toggle the screen lock and appear to freeze the phone.
Sent from my SCH-I510 using Tapatalk
I haven't experienced any of those issues either.
As for number 4, I think that was a conscious design decision. I don't really like it either, but you can use Tasker or Locale to detect when you're in a call and change your timeout to whatever you want.
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
Click to expand...
Click to collapse
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
Click to expand...
Click to collapse
Never had this issue on either phone.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
Click to expand...
Click to collapse
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
Click to expand...
Click to collapse
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Out of curiosity, are you on EE04?
I have not experienced any of these on the 3 months with my phone. It locked up maybe once on the camera but never more than that.
I've had none of these issues and furthermore I second the above thoughts regarding locking three camera and the status bar brightness.
Sent from my SCH-I510 using xda premium
Count me in the camp that says I havent seen any of those issues. As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
All the other issues you are seeing are unique.
Search these forums for them, if others have had the problem you will find someone asked about it.
If you do find them, I am sure that they will be very isolated.
I couldn't say about a totally stock phone as I flashed mine to gummy 1.9.1 on its very first boot, but I have never had a single problem with my phone.
I absolutely LOVE this thing, I have owned a TON of phones and IMHO this is hands down the best phone I've ever owned.
My boss bought a new Bionic last Friday and after playing with it for the day Friday I wouldn't swap my phone even for the Bionic (among other things, the screen SUCKS on the Bionic). My boss doesn't like it either, he is returning it tomorrow.
~John
Never experienced number 1,2 or 4. But I have experienced number 3. Only happens though every couple of weeks. Hardly ever basically. It is weird though. I have no idea why my brightness changes even with my auto brightness off. Still a great phone though.
Sent from my GummyCHARGED Charge using Tapatalk
kelmar13 said:
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
Never had this issue on either phone.
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
Out of curiosity, are you on EE04?
Click to expand...
Click to collapse
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
piizzadude said:
As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
.
Click to expand...
Click to collapse
Mine must have come with a different card as I have had no problem recording in HD (I just tried it again to make sure)
ms0chez said:
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
Click to expand...
Click to collapse
Lol, anytime!
It's a feature I don't think I could live without now.
I can honestly agree with ur first concern. My camera is wonky. I can take pics all day without flash enabled. But I turn on the flash and try to focus (tap to focus), and as soon as the pic is snapped, the screen goes black, causing me to do a battery pull. Happened to me on my former Charge, my current replacement Charge and my wife's Charge. Happened on stock unrooted, stock rooted, and with custom Roms on all firmware versions. And I can easily replicate it.
Sent from my SCH-I510 using XDA Premium App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
I think the fact that he is a journalist with some very pointed questions is the dead giveaway for his agenda. He's looking for a sensationalist angle to play for an article. Whether it's against Verizon or Samsung, I don't know, but it's pretty certain he came here with an agenda.
jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
Well put, I agree 100%
~John
never experienced those issues either..probably a android issue..
Sent from my Gummy Charged GBE 2.0 using XDA App
I've had my Charge for about three months. I ran bone stock EE4 for a few weeks and have been using the various iterations of Humble Roms ever since. I never encountered any of the 4 issues brought up by the OP.
As for HD recording, I recall posts mentioning that some phones shipped with class 2 and some with class 4 sd cards. I got a class 4 card in mine and I've never had an issue with recording HD. Likely the source of the recording issue.

Lumia 820 turns off and wont turn back on

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?

Problems after problems

Hey everyone, so I had a thread on here the other day about my S8+ having dead pixels, and I thought I'd start a new thread because things have escalated quite a bit.
So originally I had a clump of dead pixels form in the middle-left side of the screen. I was a bit hesitant to get it RMA'd because that was the only fault, or so I thought. Since then, I've had nothing but trouble:
> Force touch home button sometimes doesn't respond, with both screen on and off.
> Notifications are ridiculously lagged. They either come in 10-20 minutes after my other devices get them when the screen is off, or only when the screen is turned back on. On both WiFi and 4G.
> Intermittent lag. Mostly noticeable with Messenger chat heads, but have also seen it with the "connected to wifi" toast notifications. Everything freezes until the toast notifications fades out.
> Alarms not sounding. They only vibrate now. Even on loud mode. Settings show the alarm tone and okay it fine there. Luckily I wake up to my phone vibrating.
> GPS. 90% of the time it can't locate me properly. I'll be like 2 towns over and I'm forever pointing north. So navigating is impossible as I either don't move or am no where near where I actually am. Give the phone a restart and it works fine for a bit.
> Fast Charging doesn't fall back to normal charging if any 3rd party cable is used, even Belkin. My S7E used to fall back with no problems. It says it's charging but percentage doesn't move at all. Turning off fast charging works.
> Forever getting notifications that my Gear S2 is connected. Doesn't pop up but they come up in the notification drawer.
Is anyone else having these problems? Maybe I'm just unlucky.
Edit: Can a mod please move this to S8+ forum? Phone's XDA app had wrong phone selected.
Im about to get off from my couch and go buy s8 plus and now u got me thinking to keep my s7 edge since im really happy with it
frogomas7 said:
Hey everyone, so I had a thread on here the other day about my S8+ having dead pixels, and I thought I'd start a new thread because things have escalated quite a bit.
So originally I had a clump of dead pixels form in the middle-left side of the screen. I was a bit hesitant to get it RMA'd because that was the only fault, or so I thought. Since then, I've had nothing but trouble:
> Force touch home button sometimes doesn't respond, with both screen on and off.
> Notifications are ridiculously lagged. They either come in 10-20 minutes after my other devices get them when the screen is off, or only when the screen is turned back on. On both WiFi and 4G.
> Intermittent lag. Mostly noticeable with Messenger chat heads, but have also seen it with the "connected to wifi" toast notifications. Everything freezes until the toast notifications fades out.
> Alarms not sounding. They only vibrate now. Even on loud mode. Settings show the alarm tone and okay it fine there. Luckily I wake up to my phone vibrating.
> GPS. 90% of the time it can't locate me properly. I'll be like 2 towns over and I'm forever pointing north. So navigating is impossible as I either don't move or am no where near where I actually am. Give the phone a restart and it works fine for a bit.
> Fast Charging doesn't fall back to normal charging if any 3rd party cable is used, even Belkin. My S7E used to fall back with no problems. It says it's charging but percentage doesn't move at all. Turning off fast charging works.
> Forever getting notifications that my Gear S2 is connected. Doesn't pop up but they come up in the notification drawer.
Is anyone else having these problems? Maybe I'm just unlucky.
Edit: Can a mod please move this to S8+ forum? Phone's XDA app had wrong phone selected.
Click to expand...
Click to collapse
All good over here. Return the unit and get it swapped with a new one.
If you have this many issues, You shouldn't waste time posting here (Unless another Manufacturer "assists" you .. *Wink,. We all need money.) - However, Best Advice - Go to a Samsung Service and return it.
Viouf said:
Im about to get off from my couch and go buy s8 plus and now u got me thinking to keep my s7 edge since im really happy with it
Click to expand...
Click to collapse
I don't want to persuade you from upgrading. The phone is amazingly good, don't get me wrong, at least for the first few days with my one. I just think I've got a defective one, which happens. Just wanted to see if anyone else had the same problems.
JazonX said:
All good over here. Return the unit and get it swapped with a new one.
If you have this many issues, You shouldn't waste time posting here (Unless another Manufacturer "assists" you .. *Wink,. We all need money.) - However, Best Advice - Go to a Samsung Service and return it.
Click to expand...
Click to collapse
I will be for sure. Just wanted to put my experiences out there and see if anyone else has the same issues. Especially with a new device IMO, it's good to see whether it's a single deffective unit or wide spread bugs are appearing.
Viouf said:
Im about to get off from my couch and go buy s8 plus and now u got me thinking to keep my s7 edge since im really happy with it
Click to expand...
Click to collapse
I have no idea whether you should upgrade, but using just the most recent anecdote (out of millions) you happen to have encountered is not an accurate way to assess a product's quality.

Categories

Resources