With the V20 firmware, my N95's alarm stopped working when phone is off. As soon as I turn on phone it gives the alarm. And yes it's a clock alarm not agenda alarm. Just try it. It's an extremely important and serious bug if it's a common case.
Can please everyone tell their exact version with everything (*#0000#), whether you've restored your phone from backup after the update, and if you have the alarm bug or not.
Hmm, I'm not sure, I wouldn't call it a bug. Different people have different preferences of how the phone should behave I guess. Personally, if I'm going to a concert and turned my phone off, I REALLY do not want it to turn itself back on and start making alarm sounds...
I've just checked this out and my N95 will switch on and sound an alarm. Phew! One of the good things about Nokias is their ability to switch on and sound an alarm, so it can be used for an alarm clock.
To have to leave my N95 on over night to ensure the alarm went off would be a serious PITA. It is also one of the reasons why the in-built alarm has an advantage over 3rd party clock/alarm software, which can't activate if the phone is switched off. The N95's alarm clock might not have the bells and whistles the other software offers but at least it comes on.
I agree. I used to use Handy alarm but the fact that you have to leave the phone on is a pain, especially when I'm working shifts and my friends don't know the pattern so call me when I'm trying to sleep!
The feature has come in very handy when I have been away on business, with just a trickle of power left in the battery and no charger with me.
If I were to leave the phone on, there is no doubt that the battery will be dead in the morning before the alarm would sound... and thus missing a meeting.
Mines doesnt work either just get a white screen and all the buttons light up, tried it twice now.
yeah, my v20 works fine too...
normal start, nokia screen, alarm sounds, stop the alarm, phone asks if it wants to be switched on.
LEE69 wrote:Mines doesnt work either just get a white screen and all the buttons light up, tried it twice now.
yes, i algo get a battery symbol, just like it has been charged and the battery is full. i have to take out the battery and put it back.
maybe you could try reflashing it... if it worked before...
It worked in previous firmware, none with v20
can16358p wrote:yes, i algo get a battery symbol, just like it has been charged and the battery is full. i have to take out the battery and put it back.
exactly what mine does.
except i can wait a bit and it powers up as per normal.
I came onto this forum to post about my "not coming out of standby to trigger alarm" and found this thread. I upgraded the firmware last week, but this morning was the first morning shift I had since the upgrade, I was thinking my sleep was way too peaceful, that was because my N95 alarm didn't go off, this is a critical bug as far as I am concerned!!! A lot of us are travellers and use our phone as an alarm clock, this is not good!
I was thinking "not again, I set the alarm for 1days time instead of the current day" (which when setting at 1am can happen, I have done this a couple of times in the past), but as soon as I switched the phone on, the alarm triggered. The phone was switched on at 10.30am, the alarm was set for 9am...grr. The alarm works fine when the phone is switched on (I have a daily 8pm alarm which has been working fine).
I just deleted all my alarms (yes, I did a restore from V12, so figured "maybe this is the reason why"😉, reset the wakeup alarm tone, and now the phone partially started up with with a white screen, lights and the battery signal indicator only, I think it was hung, it certainly didn't respond to much, so out came the battery to reset. Ok, I tested this a few times, and eventually the phone switches back off after this "lights on hung like appearance" by itself. This would explain why my battery wasn't completely drained this morning from this critical bug.
Regards
People actually turn their phones off? 😊
I just stick mine in silent mode, the alarm still works and I don't get bothered by late night callers or text messages.
dchky wrote:People actually turn their phones off? 😊.
With my previous 6310i, no, I didn't switch it off, ever. It would last up to 3 days without a charge. With the N95, I have to switch it off so it will last 24hours without a charge (including the 5-8hours off time).
I noticed another nasty issue with the N95 when I first got it related to alarms. With my old 6110/6210/6310i, if the battery died overnight (should I say, if the phone switched off due to low battery), it would still have enough juice to fire off the alarm in the morning. The N95, once it switches off due to low battery, will not switch on again.
So a big negative for anyone using the N95 as an alarm, it wasn't reliable as an alarm if left on overnight as sometimes it would switch off due to low power, and now it isn't reliable when switched off overnight. Thanks Nokia grrr.
There has got to be a more logical explanation for this than the purely random nature that is being displayed in this thread. I mean, we've the same phone, all upgraded to v20, presumably a variant of Euro code and yet some have the alarm working when the phone is off, and others refusing to awake from its switched off state. What can the variables be?
dchky wrote:People actually turn their phones off? 😊I just stick mine in silent mode, the alarm still works and I don't get bothered by late night callers or text messages.
In that case, why not turn it off? Exactly the same will happen, no bothering calls or messages and the phone will come on to ring the alarm. Plus you aren't draining you battery or wasting electricity leaving it plugged in all night.
3Shirts wrote:....and the phone will come on to ring the alarm.
Not if it's one of the N95s that doesn't seem to switch itself on when an alarm is due.... 🙄
You get all kinds of faults restoring from a previous FW backup.
You HAVE to reinstall stuff because it's effectively a different device.
It's the whole point of firmware - the layer that changes the way software sees hardware. Once changed, it's no longer the same device - and you wouldn't restore a Dell backup to a Compaq PC.
I have backed up and restored at each upgrade without issues (this is my third or 4th upgrade). Is this the first issue? Maybe. The jury is still out. Ok, those of you that have this bug, did you all restore once upgraded?
I have an Aussie or Asiapac code for mine, not a Euro.
That "DON'T RESTORE" business is just a warning, application settings etc still remain the same between versions generally, and if they don't they would default that entry (you would hope!). I certainly give everything a quick check after the restore and things are OK (only thing that seems to not like getting restored is themes and anything with a certificate out of date). I never had the "keypress bug" for example...
Nokia wouldn't provide a backup and restore facility, if they thought that restoring would bugger things up, I am sure they would flag the backups with the firmware version and lock them down in this case. And who is to say what is restored, maybe the application is smarter than you make it out, only restoring what it knows is correct for the newer f/w revision. I am sure "hardware layer" items aren't trashed/restored, most restoration items are typically application settings (and most applications don't change settings wise anyway), and re-installing through restoration previously installed applications. But that isn't to say that perhaps the restoration of the alarm times between versions has trashed one of the settings for the alarm clock making its behaviour as we are describing here, that is the risk I am certainly willing to take to avoid spending possibly 3hours or more setting everything up again from scratch.
So come on alarm clock issues people, have any of you done a reset/clear and/or not actually done a restore and have this issue? If so, what is your code/region?
Regards
Ok, can everyone type *#0000# and write what is displayed there, also don't forget to indicate if you have the bug or not.
About restoring, what people told is true, a new firmware means a new device in the software side, and old restore would not work.
But what I'm restoring is not memory card restore. I backed up my contacts, calendar and web bookmarks and I'm restoring them ONLY, nothing else. And they work flawlessly. I don't think if that's the case.
Anyway, my firmware:
V 20.0.015
13-11-07
RM-159
Nokia N95 (02.01)
and I HAVE the bug.
V 20.0.015
13-11-07
RM-159
NOKIA N95 (01.01)
i have the bug.
Did not restore from back up.
V 20.0.015
13-11-07
RM-159
Nokia N95 (13.01)
Did a restore, I have the bug.
V 20.0.015
13-11-07
RM-159
NOKIA N95 (01.01)
Did not restore from backup.
i do not have the bug.
can16358p wrote:With the V20 firmware, my N95's alarm stopped working when phone is off. As soon as I turn on phone it gives the alarm. And yes it's a clock alarm not agenda alarm. Just try it. It's an extremely important and serious bug if it's a common case.
can1635p, could you edit this post to ask if folk could add whether or not they restored from back-up - in addition to whether they have the bug ?
Make a useful piece of statistical analysis.
Cheers
V20.0.015
13-11-07
RM-159
Nokia N95 (01.01)
I do not have the bug and didn't restore, only synced back contacts and calendar from Outlook using PC Suite.
V 20.0.015
13-11-07
RM-159
NOKIA N95 (01.01)
No Bug
Did not restore from back up
Pheonix SZ wrote:can1635p, could you edit this post to ask if folk could add whether or not they restored from back-up - in addition to whether they have the bug ?
Make a useful piece of statistical analysis.
Cheers
Done.
It's very weird, there is no specific case that causes the problem I could find up to know from the posts.
3Shirts wrote:In that case, why not turn it off? Exactly the same will happen, no bothering calls or messages and the phone will come on to ring the alarm. Plus you aren't draining you battery or wasting electricity leaving it plugged in all night.
Good point! 😊 I can't argue with that.
Ok, I have made some progress with this bug-
Did a factory reset (through the menu) and confirmed the bug was still there (but then so was my contacts, my old alarms etc... not much of a factory reset!)
Did a format (power up, green,3,*) and can confirm the bug is gone!
So perhaps those of you that have this bug despite not doing a settings restore, did you by any chance have a heap of applications stored on the MicroSD card? I have been doing all this testing without that card inserted to remove a possible variable. I think if that card has apps on it, when you start the phone up after an upgrade, it will try to re-install those apps anyway.
So, I have to eat my words now... it looks like doing a restore after an upgrade can give you issues 😊!
Regards
tonymy01 wrote:Ok, I have made some progress with this bug-
Did a factory reset (through the menu) and confirmed the bug was still there (but then so was my contacts, my old alarms etc... not much of a factory reset!)
Did a format (power up, green,3,*) and can confirm the bug is gone!
So perhaps those of you that have this bug despite not doing a settings restore, did you by any chance have a heap of applications stored on the MicroSD card? I have been doing all this testing without that card inserted to remove a possible variable. I think if that card has apps on it, when you start the phone up after an upgrade, it will try to re-install those apps anyway.
So, I have to eat my words now... it looks like doing a restore after an upgrade can give you issues 😊!
Regards
Glad you got it sorted, dude.
Bravo for taking the reformat plunge - you're the first dude I've EVER seen do that instead of just arguing the point.
Given the number of restore-from-a-backup-made-under-previous-FW issues that are posted, this thread REALLY oughta be stickied.
Mods ?