6303i Clock issue

I recently bought this 6303i classic mobile and found the digital clock in the Home screen is shown in bigger fonts in the middle aligned left. I tried to change some font settings and clock mode settings only to find its helpless.I can change de color of that font used for clock but not fonts.
I can either make the digital clock on or off in the home screen. I enquired in one of the Nokia Care centre, and they could not give me any solutions.
Is there anybody here to gimme a solution for this.

You will most likely not get an answer from Nokia here as this is a user to user forum.
To make sure you get a answer from Nokia, use the "contact us" tab on the top right on this page.

Similar Messages

IPhone 4 "Manual" clock issue

Hi,
I've been googling about my bizarre clock issue but everyone seems to be stuck with issues on auto sync clock and daylight savings time and alarm issues..... but mine is slightly different and hence my new post:
Basically, I set my clock to manual clock and for some reason it will get slower overnight. I've tried this twice now whereby I set the time manually I had sync'd time a few different people making sure the time I set was correct. Next day my clock ends up being several minutes behind everyone. 2nd time around I even set my clock faster than everyone but again clock ends up slower overnight. It is so frustrating as I have normally relied on my phone's clock as I dont wear a watch. I recently bought an iPhone and for all its functionality it cant get time right? ffs... I'm on 4.2.1 and I hope I dont need to upgrade to 4.3 to get this fixed. Any suggestions would help. Thanks!

A P.S. my reference is always my wrist watch as I have several solar powered, "atomic" time watches that get their NIST radio time signal every morning between 2am-5am. I have my iPhone date/time set to "automatic", and while it never seems to be more than 10 seconds off my watch, it is never exactly the same, and sometimes it has been a bit fast and other times a bit slow.
I just think the actual clocks in cell phones and such devices are inherently not fantastically accurate - I have a 100+ year old mechanical pocket watch that keeps better time (about +/- 2-5s per month) than any computer or mobile device I've ever owned.

Alarm clock issue after OS upgrade to 5..0.0.973

I upgraded to 5.0.0.973 and now I have issues with my alarm clock not displaying the time while charging at my bed side. I have Verizon and tried using the latest upgrade from Sprint. 5.0.0.1030 but the alarm clock issue remains. Rolling back the upgrade I am told would be one answer, but is there a way to dispose of the offending file somehow might be a good fix. Totally frustrated with BB at this point. One of the few things l like about my phone and they mess it up!! The Droids and the I-wanttobetrackedeverywhereIgophone is looking attractive these days.

Well i have the same issue, let me go over the items i have done.
First did the OTA upgrade. Issue happened.
then i downgraded to .886. worked normal.
Updated with Desktop Manager. Issue happened.
Wipe of Device to see if software conflict. Issue still happens.
also done several batteries pulls to see if that would fix it. still issue happens.
I've just downgraded again to .886 and it works. at this point i am going to be staying with .886 unless a fix is found for .973.

Clocking Issues with VWICs

We connected a 3825 to a Nortel PBX today and had some weird clocking issues. We're using VWIC-2MFT-T1 modules and I think I need to learn more about how clocking works with these things. The PBX didn't seem to like it when the router provided clock. The engineer working with us told us that he thinks the clock on the router is not stable enough to provide clocking.
Have any of you had any issues using a router to provide clocking to a PBX? It seems like it shouldn't be a problem but we kept experiencing slips on the Nortel side if the router was providing clocking.
This creates a problem for us. We will be connecting one port to a frame relay data circuit and that port must be set to "clock source line". If the router can't provide clock to the PBX then that port also must be set to "clock source line".
I ran across a tech note that says the following:
"When both ports on a VWIC-2MFT-T1, VWIC-2MFT-E1, VWIC-2MFT-G703, or VWIC-2MFT-E1-DI interface card are configured as clock source line, then they must be set to the same clock source. If they are not set to the same clock source, timing slips can occur. Each port on the VWIC2-2MFT-T1/E1 and VWIC2-2MFT-G703 interface cards can be set to independent clock sources for data applications."
Are we going to run into problems since we don't have the VWIC2 modules?
I don't understand the way clocking works with these modules anyway. With only one port connected to the PBX we were seeing slips even with the router was set to "line". We fixed that by using the "network-clock-select 1 T1 0/0/0" command. I don't know what that command actually does but it stabilized the clock and eliminated the slips. Weird. I need to go do some research on this issue because we need to get it figured out and settled soon.
Any thoughts?
Thanks!
John

The 2800 and 3800 routers have internal tdm buses that can be used to tdm switch between any ports on the box. You use 'network-clock-select' to pick the clocking source for the internal tdm bus. This clock source is then used for every interface that is identified via the 'network-clock-participate' command. The best you can do in your case is to clock off the frame relay network and see if you get slips on the T1 to the nortel, or clock off the nortel and check for slips to FR. Make sure the nortel is set up correctly to either take clocking from the T1 or provide clocking on the T1 - you may not have a choice there depending on protocol used. Best practice (and what you may end up needing to do) is to separate the T1s onto different VWICs so that clocking can be independent. Even with a VWIC2 you only get 1 clock source if using voice (with data can run ports independently).
The internal clock on the router, like the internal clock on the PBX, should only be used for fallback as they aren't nearly as accurate as what is used in the cloud. For this reason you create a synchronization plan that cascades the clock from the cloud. In your case the nortel would clock off the PSTN (I'm sure already being done) and cascades clocking to the 3825. When you get more PSTN trunking into the IP side of things you would want to swap - have the 3825 clock off a PSTN T1 and then cascade clocking to the Nortel.
hth,
Don

OVM server clock issue

Hi,
Does anyone has any problem with the OVM server 2.1.2 system clock issue? The clock is getting the wrong time even if I used ntp server. Any idea why? Thank in advance.

Hey,
You manually set the clock initially and then use these command
# /etc/sysconfig/clock sets whether the hardware clock is stored as UTC or local time.
# Symlink /etc/localtime to /usr/share/zoneinfo/... to set your timezone.
# Run ``date MMDDhhmm'' to set the current system date/time.
# Type ``/sbin/hwclock --systohc [--utc]'' to set the hardware clock.
Now restart the ntpd service..
Do you h ave ntpd server - to which all other server refer to and synch time ?

Clocking issue with LP7

Hi,
I have both LP7.2 and LP8.0.1 on my MacBook Pro 17" (Late 2008) and Mac Pro (1st Gen 2006). I'm currently working on a project editing audio in 96K in LP7.2. Randomly, sometimes as soon as two audio cuts and sometimes after 20 mins I get buzzing when playing/scrubbing audio, which sounds like a clocking issue - despite me going directly through CoreAudio (I'm not using any external sound cards)
I work on the same project using my MOTU 8pre on my MacPro (setting the MOTU to 96k the MOTU Audio Setup app) and hey presto - no issues.
The only way I can resolve the issue on the MBP is by trashing com.apple.logic.pro.plist and reopen Logic 7, but this is a really slow way of working.
The engineer I work with mentioned that it could well be a conflict in LP7 and LP8 as they use the same preferences... but it seems more to me like a Core Audio issue?
Does anyone have any suggestions?
Cheers,
Ben

This issue was resolved after applying latest patch from Oracle.

Boot camp / Mac OS X Leopard clock issue

Howdy,
Yesterday, I installed XP on my MacBook Pro using Boot Camp and I've come across a quirk that now comes up on Mac OS X. The clock is 5 hours behind! When I start up in Windows, the time is fine (set for US Central time zone). However, when I start up in Leopard, the time is stuck 5 hours behind. I checked the time settings and it is also set on US Central time and it would not let me manually push the time ahead by 5 hours. (The minutes are correct, so this morning at 7:43 AM, it was showing up as 2:43 AM).
Do you know what would cause this? How do I fix this?

Hello.
I searched around a bit more and found out this is an ongoing issue. I've read over previous commentary on this issue and will try some of those techniques.
Thanks.

Nokia N8 Belle Alarm Clock Issue

I was finally able to update my N8 to Nokia Belle a week ago and was reasonably impressed with it's attempt at an Android Froyo kind of thing, it is a step in the right direction. However-
I set a several alarms for between 6:45 and 10am today (I'm a fairly heavy sleeper). I snoozed the first alarm by turning over the phone to give me a few more minutes of sleep. The next thing I know, my sleep is breaking and it's 9:32am! All without a sound from any of my alarms.
I looked at my phone, and saw the box with 'Stop' and 'Snooze' on it, for the 6:45 alarm, as if it had just been activated and was waiting for me to choose either option. I pressed 'Stop' to get rid of the box and suddely similar boxes for all the other alarms started popping up in rapid succession, only then. What happened???
I was willing to wait 6 months past the original release date because I assumed such bugs were being sorted out properly; a smartphone shouldn't still be grappling with Alarm clock bugs - it should have better things to do. I'm hoping there's a quick solution to this problem, as I cannot wait two years for the next update. Please advise!
Also why does shuffle deactivate everytime I return to my song list? Seems silly, really - I don't want to have to keep turning it back on.

First thing First!
AlarmClock: Being Honest! theres no such issues with the Default Alarm app. U might hav done sumthing unusual during sleep or your app had been crashed or it might b buggy or may b sum RAM issues.
Its not a General issue.
I myself is a Heavy sleeper lke You!
I too set 7 Alarms within 6:30 - 10:00 range.
All works fine with my Nokia N8-00 Belle.
MusicPlayer: Yeah! this had been a big problem for Music lovers that when you are Dazzling on SHUFFLE mode & once you clicked on a particular song in a list, the SHUFFLE is de-activate itself.
It might be a problem for Some people, but Logically speaking If you are in A Shuffle mode, u should not interrupt the playlist, if you do it gets deactivate automatically.
Nokia got a point this time
In Love with Nokia, Symbian & N8-00

Alarm clock issue

So there is an issue with alarm clock since 4.4.4 update and it is still in 5.0.2. When i try to clangw Alarm clocks sound it opens File commander not stock sound! In 4.4.4 usualy after Restarting phone all worked fine for some time, but now in 5.0.2 it is not fixing problem. Any ideas how can i get in stock alarm clocks sounds? Or fix it at all?
Solved!
Go to Solution.

You could clear defaults for all apps in settings-apps-all.
All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

Nokia N8 Daylight Saving Clock Issue

I have discovered a issue with the clock on my Nokia N8 following the commencement of daylight saving here in Melbourne Australia.
My device is set to "Automatic time update" & yesterday it adjusted the time for daylight saving by 2 hours instead of 1. It is now one hour fast.
I have a feeling there may have something to do the phone confusing UK time for GMT time (UK still in daylight saving time to my knowledge).
Anyone else have this issue?

Mine is working fine, I changed from Brisbane to Melbourne, only moved forward an hour with automatic time update on.
I'm using Belle though, perhaps when you get the Anna update it shall fix it.
For now you might have to just turn the automatic updates off

A Clock Issue for OS X Mavericks

Hi
I have an iMac Early 2009 Model with the newly upgraded OS X Mavericks (OS X 10.9) and I am trying to put in the correct time my clock because it's 1 minute faster than the real time on my iPhone, but when I attempt to change the clock every time, it always asks for the administrator's user name and password. When I attempt to use the administrator's name and password on the screen, the letters & numbers within the 2 spaces are blank instead of normally seeing my original user name on my iMac since after I've upgraded the software from a Leopard (10.5.8). So every time I try to use my screen name and password, it does NOT accept the password and user name.
The problem with the user name and password from the administrator does not just accept the clock problem, but it does not work for any other feature such as downloads, software updates and more, etc...
Are there any alternatives to fix this issue?
I hope there can be a new mavericks update to fix all of these issues in the next year or so.
Thanks!!!

Another user seemed to resolve it via safe mode…
https://discussions.apple.com/thread/5563384?start=0&tstart=0
Safe mode
https://support.apple.com/kb/HT1455
If that makes no difference I'd also try some of the simple resets…
Reset the SMC
https://support.apple.com/kb/HT3964
Reset the PRAM
https://support.apple.com/kb/HT1379

[SOLVED] System Clock Issues (Wrong UTC?)

**RESOLVED -- SEE END FOR FIX
Hello everyone.
First off I'd like to say that I am thrilled to be here. I've been an Ubuntu user for a few months now, but decided that it was time to take a trip down the rabbit hole and see all that Linux had to offer--and to that end I switched to Arch. And I must say that I have nothing but positive things to say of it. The documentation on the Arch Wiki was phenomenal in helping me get started on the process, and the installation of it has proved to be a very enjoyable learning experience.
With that said, I have run into a bit of a snag, and after perusing the documentation on the Wiki, as well as running a few Google searches and searches of this particular forum, am no closer to a solution that when I started, so here I am. The problem is with my clock.
Okay, so I live in the Eastern United States, and as a result have my local time set as Eastern, and I have my hardware clock running UTC. Here is the problem. . . For whatever reason, the time displayed on my clock is five hours behind. Perplexed, I decided to see if I had set up my time zone info incorrectly and ran the "timedatectl status" command, and the results were really strange. A copy paste of the output is here:
Local time: Thu, 2012-12-20 19:27:02 EST
Universal time: Fri, 2012-12-21 00:27:02 UTC
RTC time: Fri, 2012-12-21 00:27:02
Timezone: America/New_York
UTC offset: -0500
NTP enabled: no
NTP synchronized: no
RTC in local TZ: no
DST active: no
Last DST change: EDT → EST, DST became inactive
Sun, 2012-11-04 01:59:59 EDT
Sun, 2012-11-04 01:00:00 EST
Next DST change: EST → EDT, DST will become active
the clock will jump one hour forward
Sun, 2013-03-10 01:59:59 EST
Sun, 2013-03-10 03:00:00 EDT
As you can see, the time zone is set correctly to America/New_York (originally US/Eastern, but I changed it to try and resolve the problem--to no effect, obviously). However here is where it gets strange. As I type this, it is 00:27 local time. My computer has decided to use the local time for UTC, and then subtracts five hours (as I live in UTC -5) to get the local time that it displays.
I've tried rerunning the hwclock --systohc --utc command, to no avail.
If anyone has any input as to why my computer is confusing UTC and local time, and any way I could fix it, I would greatly appreciate it.
I could just change my timezone to UTC - 0, that would cause my system to display the right time (I think) but I'd rather actually fix the problem, instead of simply covering it up with a band aid, if it is possible.
Thank you,
Douglas
EDIT:
I probably should mention that the machines (I'm having this same problem on two different computers) are both running Arch Linux and Arch Linux alone, although one was originally a Windows 7 and the other a dual boot of Win 7 and Ubuntu.
RESOLUTION (Thanks lhoffman):
Install the network time protocol daemon. This will allow you to sync your system time over the internet.
sudo pacman -S ntp
Once installed, run the following command:
ntpdate pool.ntp.org
This will link your computer with the time servers of the NTP Pool Project. For me my clocks fixed themselves quickly after running the command. And that was it.
After running this command and setting the system clock, run:
hwclock -systohc (thanks Scimmia)
Otherwise the computer will mistake local time for UTC and subtract/add time based upon your timezone again upon reboot.
Last edited by douglasr (2012-12-21 21:23:11)

Scimmia wrote:Not exactly. The root of the problem is that your hardware clock is set to localtime. To change this, you need to update the system (software) clock, which ntpd already did for you. The timedatectl command would have just done that manually. Now that your system clock is correct, you need to write this to your hardware clock so that it is correct when you reboot. hwclock --systohc does that. If you don't run that command, the system will boot up thinking it's getting UTC from the hardware clock and will subtract 5 hours. Then, once ntpd runs, the time will skip ahead 5 hours. This will cause all kinds of issues.
I fixed this on my system too. Thanks for the explanation.

Dashboard world clock issue

Since ML I can't add any standard world clock widget to my dashboard other than automatically set up to my local time.
Any one wit same issue ?
Any Ideas ?
Jean.

I finally called Apple Care.
The solution is to delete the corrupted plist file named "widget-com.apple.widget.worldclock.plist"
in the preferences folder in your user library
Restart the computer, a new file is created and you can make your dashboard clock widget settings as usual.
Jean.

Vwic2-2mft-t1 clocking issue

Have a PRI and point to point T1 terminated to a VWIC2-2MFT-T1 card, when the pri has priority clocking, there are no slips except on the point to point T1 and vice versa. Does anybody know a way around this, both clocks are set to internal. I have read where you can setup independent clocking but only if both are used for data.
I hope that the only answer is not to get 2 separate single port cards.
Thanks,

If you do a search on this forum, you will see that many people have run into the same issue. To my knowledge, the only workarounds are to use the same carrier for both circuits and ask them to provide the same clocking or live with the slips/errors. The only other option is, as you said, another card.
Hope this helps.
Brandon

Multiple PRI ports clocking issue

Hello,
We have a 3845 with 2 VWIC2-2MFT-G703 cards. The router is between Telcos and another 3945.
This router acts as a forwarder, fax gateway, etc. We are working with 2 Telcos and we are getting voice service.
3845 has 4 PRI ports. 2 of them are connected to Telcos and they are on the first VWIC2 card and the other 2 is connected to 3945 which is the main device for our IP Telephony.
Telco1---- -----
3845 3945
Telco2---- -----
I have the following commands for network clock:
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 E1 0/0/0
network-clock-select 2 E1 0/0/1
Telco1 has no slip errors since it is the master clock source.
Telco2 has slip errors since we are using Telco1's clock
We can not use clock source line independent since this is a voice line.
3845 acts as network side for the connections between 3845 and 3945. We do have slip errors on these connections as well.
Unfortunately I do not have access to 3945 router.
Any ideas to get rid of slip errors?
Here is E1 controllers status:
E1 0/0/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (238 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 0/0/1 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (239 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
30 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
30 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
10938 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
10938 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 0/1/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (238 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
84 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
84 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
30432 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
30432 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 0/1/1 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (239 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
53 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
53 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
4259 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
4259 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

If the appropriate IOS images are used with all the supported hardware, then there should not be any issues. Guess, you have enough memory too for the required images.

6303i Clock issue

Similar Messages

Maybe you are looking for