N80IE Firmware 4.0707.0.7 bugs

Can anybody please advise on when Nokia will fix the bugs already identified in N80IE firmware 4.0707.0.7? Things are no longer OK with my phone since I "upgraded" to this new firmware and most frustrating, I can no longer access my credit balance by doing something like *123# anymore.

I myself report the bug on my N80 and I hate Nokia team that luch such a disaster.Moreover, they should stop this firmware because causes many troubles to so many Nokia fans. I can not see my balance, I receive system error..Nokia wake up!! Do something!
World in zugzwang!

Similar Messages

  • N80ie V 4.0707.0.7 important bug

    If you key something like *123# (send) to access operator info (like credit balance) sent by special flash message, it doesn't work.
    It says "Requesting..." then nothing!!!
    Ideas?
    MrAnderson

    Although most people do not use the short code very often, but this is the essensial function of the phone. I am sure nokia engineer is working on it. by the way I just found another bugs with s60 internet radio, I am not sure if it's the nokia or the software. Everytime I am listening to the internet radio and there's a incoming call, an "error not connecting to server code -13" is popup then disappear. It didn't happen when I got the old firmware.
    My favorite N80 applications: Nokia Mobile Search, Smart2go Beta,
    S60 Internet Radio, Mobile Weather.
    N80ie Firmware: V 4.0707.0.7 (March 28, 2007).

  • New bug in new firmware v4.0707.0.7 for n80

    in most time whene i try to chageing n80 said not charging
    the problem diapear whene i restat my phone and racharg it

    Hi,
    That is very odd.. perhaps u can try updating the software again. The new NSU client 1.3.60 has been launched.
    If the issue persists,then have it checked out at a Nokia service center.
    Cheers
    Let me be a ripple in the silent stream of your memory ~ Viveca

  • N80 V 4.0707.0.7 BUGS, BUGS and BUGS we need a new...

    1. Flash message not working... Pre paid customes oops.
    2.You need to enter clock and date after every switch on -- brrr.
    3. Network operator time Update is not happening
    when do we get a relief ... ?
    I hope its not like asking to UNMessage Edited by ys_drake on 19-Jun-200704:49 PM
    N80 V5.0719.0.2 24-05-2007 RM-92 Nokia N80 (12)

    Yes, the new version is 5.0719.0.2 it is available now (I really dreamed last night that Nokia has launched this 5th version) when I checked I was very happy because I thought it would solve all the problems I have in my last V4.0707.0.7 but unfortunately it solved only some bugs but the most important bug has not been solved and the new version has the same bug as the previous one:
    1.Phone requests Time/Date when restarted – whenever switched off and back on (this is the most important bug and I want to reply to the guy who thinks that it is a hardware problem: NO it is a bug in the new firmware because I haven't had this problem before i update to V4.0707.0.7 I am deadly sure)this is still on the new version 5.0719.0.2 !!!
    2.No service messages available, it show requesting then nothing (ok this was solved on the new version)
    3.A cursor appears blinking at the right side of the balloon that shows caller number(this is still on the new version 5.0719.0.2 !!!)
    4.Led stays blinking even after using the keypad and when calling (ok this was solved on the new version)
    5.Lower video quality (ok this was solved on the new version)
    I was waiting for the new Version to solve all the bugs specially the first one - but now after the new version I am thinking to throw Nokia products forever as I am not willing to wait more than that withouht the alarm colock, reminders, and more important I used to switch off my phone to get a quiet sleep since the new version I cannot sleep well, I have to leave my phone switched on to keep the clock running! but what if the battery runs out especially it lasts for less than day and all N80 users know this well and i think this bug cannot be solved.
    I want to tell all the users of N80 that we are all have been screwed by Nokia - I am really disappointed and wouldn't ever think that I will use other brands than Nokia but know just to retort this to Nokia I will have to use other brand

  • Firmware update reduced features, increased bugs 2...

    Hello, i updated my Nokia 2700c firmware last night in the hopes that it might get rid of some bugs that i found very irritating after the last forced update by the Nokia care (after a problem with the phone, instead of reinstalling the same version they updated it instead).
    But the bugs have now grown in number as well as a bit more serious now.
    --The phone now doesn't read the name of a contact, in the from field in sms or call list which has more than one number saved or even randomly, some numbers have it displayed, some don't.
    --The media player starts playing a song after a 5sec lag in which the phone is unusable, like if i am texting at the same time, it would stop responding,
    this becomes worse by the balance notifications after every sms by my operator, in which case it notifies by sounding the sms tone 2 times but now with a 5sec gap in between while playing music, thus making the fone pretty much useless for those 15secs.
    --The screensaver functionality is gone.
    --The main menu has a menu option repeated one more time, which i never used in the first place.
    --The T9 text entry has a lot of bugs with the order of matched words.
    --The transition effects have all gone slow, thus prompting me to switch them off.
    I can live with the last four but the first 2 i've listed have completely turned me off. Why isn't adequate testin done before releasing an update?
    The first version of the device was 7.15, which was updated to 7.80 and this latest one is v9.95(?) i guess they even typoed the version number in this one (9 instead of 7) cause it doesn't look like such a major 'upgrade'.
    Please tell me is there any solution to these problems?? Or am i stuck with these bugs for good?
    Thanks.

    Update: Managed to fix the second issue by a hard reset.

  • 5800 XM Firmware 11.0.0.8 bugs

    Hello
    my previous firmware didn't have any but but i've put the newer version to see if the performance is better, but now i'm disappointed actually:
    1- you accelerometer response is too slow (it was faster before)
    2- when I'm in the desktop main page and i'm grabbing the mobile horizontally, and when i try to open the menu, the menu screen doesn't appear correctly.
    3- the worst bug is the " EXPIRED CERTIFICATE " which you really have to fix ASAP NOKIA.
    4- probably other users are encountering other problems as well.
    above all, you should be working harder and better because you are Nokia and we( your customers ) deserve better...
    Thanks .

    18-Jan-2009 06:24 PM
    vahram wrote:
    Hello
    my previous firmware didn't have any but but i've put the newer version to see if the performance is better, but now i'm disappointed actually:
    1- you accelerometer response is too slow (it was faster before)
    2- when I'm in the desktop main page and i'm grabbing the mobile horizontally, and when i try to open the menu, the menu screen doesn't appear correctly.
    3- the worst bug is the " EXPIRED CERTIFICATE " which you really have to fix ASAP NOKIA.
    4- probably other users are encountering other problems as well.
    above all, you should be working harder and better because you are Nokia and we( your customers ) deserve better...
    Thanks .
    There is an easy fix for the 'EXPIRED CERTIFICATE' error. The reason you get this error, as i did, is because when you upgrade the firmware, it messes with the time and date on your phone (you might recall having to set the time & date correctly again after update completion). I read somewhere that it had something to do with the sim-clock or something (dont quote me on that as i'm not 100% sure that its the sim-clock lol). But anyway, it should be an easy firmware fix which nokia will hopefully sort out very soon.
    Here's how to fix the 'expired certificate' problem after updating your firmware to v11.0.08:
    1) back up all your files using Nokia PC Suite ie. contacts, pictures, videos etc.(i would also remove the memory card, it might not be necssary, but better be safe )
    2) Once data has been backed up....you need to reset your phone to its original factory settings by dialing *#7370# (it will ask you if you would like to restore to original factory settings, you will choose 'yes' and enter the default passcode '12345' and your phone will restart)
    3) Once the phone has restarted, choose your location just like you did when you started up your phone for the very first time, and then set the correct date and time.
    4) All done, and the 'expired certificate' problem should be gone and you can re-insert the memory card if you have taken it out and restore all your backed-up files back onto your device.
    Let me know if this has worked for you.
    Message Edited by dan2007h on 20-Jan-2009 07:25 AM

  • Latest E51 Firmware 200.34.36: minor bug found

    Hello, I have found a little bug; unfortunately I don't know, if it's also on the initial firmware, but the 200.34.36 does have it.
    If I have my SD card inserted (8 GB, with quite many MP3 and WMA files), it's not possible to set the system sounds, like ringing tone, mail tone and so on.
    While opening the respective menu, instead of seeing of the usual sound clips list, I see only "Download sounds" and "Off".
    I think, the e51 isn't able to enumerate the complete list?...
    While the SD card isn't inserted, the lists work as they should.

    maybe I am wrong but I can not see the similarity with your computer. when you install a new disk you install a lot more hardware than just the disk itself.
    I use many professional devices that work with memory cards and they all have a maximum for which the manufacturer guarantees the device to work. If you install higher capacity cards you may expect problems. Because the devices needs to access the memory card which is a completely different process than when a computer wants to access it's hard disk.
    There are even differences in different brands of cards. Some brands may produce a 8 GB card that works with a certain device others produce a card that does not work. When you upgrade your firmware and you get a problem as soon as you insert your card, it is very likely that the card is the issue.
    I would suggest to try a 4 GB card and see if the problem persists. If not you know the answer. You can alternatively try different brands of 8 GB cards.

  • UTA200-TM Firmware 1.01.08 timestamp bug

    I am using T-Mobile @home service. I was given an UTA200-TM HiPort Adapter.
    Firmware 1.01.08 has a major timestamp bug.
    Status: Current Time: Not Available
    I tried flashing fimware 1.01.04.
    Status: Current Time: Came up with correct date and time.
    Firmware 1.01.04 timestamp works perfectly.
    However, the UTA200-TM reflashes itself to 1.01.08. How aggravating!

    Tech Support:
    The UTA200-TM hardware is not the problem.
    The problem is that there is a major flaw in the time-stamp under firmware version 1.01.08:
    “Status-Router-Current Time: Not Available”.
    Under firmware version 1.01.04:
    “Status-Router-Current Time: Correct Date and Time”.
    Further testing:
    Kbhonline did some troubleshooting and he figured out the flaw even deeper.
    When you assign a static address to the WAN port, the time service, for some reason does not operate.
    Just for fun he set the UTA200-TM to act as a DHCP client, rebooted and, voila, it all came up, including the time.
    He then started to make my changes, one change at a time and reboot.
    When he changed the WAN setting from DHCP to Static, no time request went outbound.
    All other services worked fine, just no correct time.

  • RV180W Firmware 1.0.2.6 bug

    Our company own a RV180W router. It works well with firmware 1.0.1.9 but with firmware 1.0.2.6 it is impossible to SSH between our devices. Ping still works though.
    I don't know if there is another place where to report such bugs

    Hi Dominique, thanks for using our forum, my name is Johnnatan and I am part of the Small business Support community. Please call the Small Business Support Center to confirm if this is a bug. Please go here to find the phone number in your country:
    https://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    I hope you find this answer useful, 
    “Please rate useful posts so other users can benefit from it”
    Greetings, 
    Johnnatan Rodriguez Miranda.
    Cisco Network Support Engineer.

  • N80 new firmware v4.0707.0.7

    code: 0527494 , u can check that. And, anyone has updated it? is it gd? does EAP-LEAP/PEAP work in that version?

    05-Apr-200702:27 PM
    patc wrote:
    Shhhhh!
    Don't tell 'em that!
    They'll never release the firmware
    Tell 'em something like the firmware improves the photo quality by using a different compression algorithm. Sufficiently confusing to get by them, I reckon.
    I did quote potential battery life improvements, etc etc, but to be honest she threw me by asking why I wanted it!! I did mention potential battery life improvements too, which drives me nuts.
    Anyway, we shall see (without baited breath)..

  • WAP4410N firmware 2.0.4.2 bug: 300Mbps data rate not possible

    I've spent parts of the past five days buying and exchanging several WAP4410N units because I was not able to achieve anything close to a 300Mbps data rate. I also tried various wireless-n network cards which were known to be configured correctly for 300Mbps speeds with no luck.
    The highest speed I was able to achieve was 130Mbps, which is an indication that channel bonding is not in effect.
    Then I came across another post in the forums:
    WAP4410N does not exceed 130Mbps in N mode at close range.
    where the OP mentions recently upgrading to firmware 2.0.4.2, though not treating that as the cause of his problems.
    On a lark, I tried downgrading to both firmware 2.0.2.1 and firmware 2.0.3.3, and to my surprise, I was able to achieve the full 300Mbps data rate with both firmware versions.
    When I reverted back to 2.0.4.2, I was not able to achieve the full 300Mbps data rate.
    So, right now, I downgraded to firmware 2.0.3.3 so I can get the higher data rate, though there are other quirks to deal with.
    Furthermore, when I do a web search of reviews, I can see that the inability to achieve the 300Mbps data rate is a huge source of complaints.
    Cisco, please fix this firmware!
    Edited to add: I found another post regarding the same phenomenon:
    WAP4410n LIMITED TO 130Mbs in N-mode

    Hi James,
    When I bought the WAP4410N I was still using Vista and a beta of Windows 7 x64.  My PC was reporting 300Mbps but I never believed it and just figured this was better then the Linksys Wap54g with DD-WRT. I was only showing 54Mbps on my laptops but the amount of data I could download over a minute was better then the WAP4410N.  The best speed I can achieve (but only lasts a few minutes) is 130Mbps from the WAP4410N and downloads are painfully slow.  Using a desktop gadget "network meter" on one of my desktop PCs with a wireless N USB adapter it is showing a speed of 54Mbps and a signal strength of 70% at a distance of 4 feet from the WAP4410N.  At this distance I also experience interruptions in connection and poor performance.  I do not know if my WAP4410N is defective but a beta firmware is to be released this month that is supposed to help.  I have had to recommend other brands in this price range to those wishing to buy a stable product as this performance is not acceptable.  My network is mostly GigaLan devices and strangely the intelligent switch reports the WAP4410N as running at 100Mbps with the firmware set the 1000Mbps so there is another mystery.
    Best regards,
    Brad

  • WVC210 firmware 1.1.0.12 bug

    Hello experts,
    I updated my WVC210 firmware from 1.0.0 to 1.1.0 and now I have two big problems.
    With 1.0.0 I used to let the camera ON (always, 24 hrs a day), and I used to shut down my router during the night.
    In the morning I used to set to ON the router and the WVC210 (wireless connected) automatically linked to the router and to DynDNS (so that I was able to reach the camera both from my LAN and from the internet).
    1. Now with 1.1.0 the WVC210 (always ON) doesn't automatically connect to the wireless when I restart my router: I always need to start the router first and then to restart the camera;
    2. the DynDNS doesn't update automatically as before happened (I need to do as describet on point 1. ...router first, then webcam).
    What's wrong?
      Thankyou so much
    - Enrico

    Hi Enrico,
    Recommend you post your issue in the Small Business Support Community here: https://www.myciscocommunity.com/community/smallbizsupport/securityandsurveillance/surveillance;jsessionid=F18EAC90A152CC8FA3AD68156729796D.node0.
    This Challenges forum is not as likely to provide a response.
    Thanks,
    Stephanie Reaves
    Cisco Small Business

  • SPA514G: BLA, re-SUBSCRIBE record-route is broken (firmware bug?)

    I have a BLF configured on SPA514G as "fnc=blf+sd+cp;sub=201@$proxy".
    The proxy forwards SUBSCRIBE to our presence server.
    The "200 OK" on SUBSCRIBE and the NOTIFY to SPA contains record-route.
    When the SPA re-SUBSCRIBE, it sends directly to the presence server from contact header.
    The route header is correct.
    The PROXY is dual-homed:
    192.168.3.15 -> 192.168.3.3 --- 192.168.2.3 -> 192.168.2.5
    SPA514G ---------------- PROXY -------------- PRESENCE
    I've tested firmware 7.5.6a and 7.5.2b.
    Partial trace:
    192.168.3.15:5060 -> 192.168.3.3:5060
    SUBSCRIBE sip:[email protected] SIP/2.0
    Via: SIP/2.0/UDP 192.168.3.15:5060;branch=z9hG4bK-6df8985a
    From: "Cisco" <sip:[email protected]>;tag=2d763ae2f27077d6
    To: <sip:[email protected]>
    Contact: "Cisco" <sip:[email protected]:5060>
    Event: dialog
    User-Agent: Cisco/SPA514G-7.5.2b
    192.168.3.3:5060 -> 192.168.3.15:5060
    SIP/2.0 200 OK
    Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=2d763ae2f27077d6>
    Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=2d763ae2f27077d6>
    Via: SIP/2.0/UDP 192.168.3.15:5060;rport=5060;received=192.168.3.15;branch=z9hG4bK-6df8985a
    From: "Cisco" <sip:[email protected]>;tag=2d763ae2f27077d6
    To: <sip:[email protected]>;tag=57902af3e183b228161407cf3808f4bc-81e5
    Contact: <sip:192.168.2.5:5060>
    192.168.3.3:5060 -> 192.168.3.15:5060
    NOTIFY sip:[email protected]:5060 SIP/2.0
    Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
    Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
    Via: SIP/2.0/UDP 192.168.3.3;branch=z9hG4bK06a2.97fdfb93.0
    Via: SIP/2.0/UDP 192.168.2.5:5060;rport=5060;branch=z9hG4bK06a2.6e6e2853.0
    To: <sip:[email protected]>;tag=2d763ae2f27077d6
    From: <sip:[email protected]>;tag=57902af3e183b228161407cf3808f4bc-81e5
    Event: dialog
    Contact: <sip:192.168.2.5:5060>
    Subscription-State: active;expires=180
    Content-Type: application/dialog-info+xml
    192.168.3.15:5060 -> 192.168.3.3:5060
    SIP/2.0 200 OK
    To: <sip:[email protected]>;tag=2d763ae2f27077d6
    From: <sip:[email protected]>;tag=57902af3e183b228161407cf3808f4bc-81e5
    Via: SIP/2.0/UDP 192.168.3.3;branch=z9hG4bK06a2.97fdfb93.0
    Via: SIP/2.0/UDP 192.168.2.5:5060;rport=5060;branch=z9hG4bK06a2.6e6e2853.0
    Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
    Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
    192.168.3.15:5060 -> 192.168.2.5:5060 <--------- Should use PROXY (192.168.3.3)
    SUBSCRIBE sip:192.168.2.5:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.3.15:5060;branch=z9hG4bK-f35b1d45
    From: "Cisco" <sip:[email protected]>;tag=2d763ae2f27077d6
    To: <sip:[email protected]>;tag=57902af3e183b228161407cf3808f4bc-81e5
    Route: <sip:192.168.3.3;r2=on;lr;ftag=2d763ae2f27077d6>, <sip:192.168.2.3;r2=on;lr;ftag=2d763ae2f27077d6>
    Contact: "Cisco" <sip:[email protected]:5060>
    Event: dialog

    Release notes say it is fixed in 7.5.7, didn't test myself yet.
    SPA50x/30x/51x Firmware Release 7.5.7
    =====================================
    Bug Fixes and changes since 7.5.6
    =================================
    - CSCur27078 - SPA514G - BLF is broken in firmware 7.5.6

  • Zen bug reports... where to submit? Firmware & Media Explorer bugs

    There seem to be two rather annoying bugs (actually, three, but the firmware ones are closely related) - there should be a separate forum for bug submission...
    The firmware bugs are related to the embedded graphics and are present in the updated firmware, too.
    The first bug: embedding a graphic in an MP3 properly, with tested tools such as ID3Tagger, works fine in any player supporting the image display - but Zen will *not* display the graphic unless the header's "Album" field is filled, too. If the "Album" field is empty in ID3v2 (or v), Zen will never display the graphic.
    The second bug seems related to this: if the "Album" field has the same value in more than one file in the same directory (or playlist), Zen will only use the first indexed graphic for all those files. As a result, right now I have 0 various Star Wars themes in my Zen, each file with a different graphic embedded in it - and yet Zen shows the same graphics in all of them.
    The third bug is in the Media Explorer: every time the player is plugged, CTPlyLsU.exe loads. But very often, it will load as a new process each time - and it will NOT be terminated after the player is disconnected, but it will stay in the memory! When that happens, every time the player is detected again, a new instance of the process will be started and used. I plugged the player in 0 times yesterday, and I had 0 instances of that process devouring the resources.

    The third bug is in the Media Explorer: every time the player is plugged, CTPlyLsU.exe loads. But very often, it will load as a new process each time - and it will NOT be terminated after the player is disconnected, but it will stay in the memory! When that happens, every time the player is detected again, a new instance of the process will be started and used. I plugged the player in 0 times yesterday, and I had 0 instances of that process devouring the resources.
    Strange, CTPlyLsU.exe is on my system but based on the task manager it doesn't load at all when the player is connected and everything works fine.Message Edited by jpalm on 0-30-200709:6 AM

  • Short code is not working after new firmware updat...

    I am in USA on T-mobile network. I recently updtated my N80 to the latest firmware 4.07.XXX. Everything worked fined especially VoIP features. However, I used short cut code for example like #MIN# to get my min usage status for my acct. It sends the message but not receive back the message like it used to be. Is anybody have similar issue? None of the short code is working on my phone.
    My favorite N80 applications: Nokia Mobile Search, Smart2go Beta,
    S60 Internet Radio, Mobile Weather.
    N80ie Firmware: V 4.0707.0.7 (March 28, 2007).

    Hard reset your phone *#7370# 12345 reformat, lose all data and don't install apps on your memory card.
    ‡Thank you for hitting the Blue/Green Star button‡
    N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

Maybe you are looking for