Problem after amber update on L620- India

I got my 620 updated from a nokia care centre 2 days back. But after the update, the screen hs stopped being as responsive as it was earlier . Especially the bottom of the screen just abve the windows, back and search keys. It rarely works with a light tap and i have to tap hard a few times to make it respond. Its exasperating to say the least. Some help anyone? 

return the phone back to the care center and let them inspect the problem, sounds like an hardware issue
The silence will fall

Similar Messages

  • Problems after amber update in my lumia 520

    I have updated my lumia 520. After it there is regular fluctuation in my internet connection even my data setting is on and battery is also discharging quickly after update.

    hi mate,
    have you checked that you are up to date with all the latest Nokia system app updates from the Store? also try performing a soft reset, and check your Network+ and Access Point settings in the Settings.

  • Multiple Samsung Stratosphere problems after FF1 update

    There have been multiple posts on various issues users have found after the recent Stratopshere FF1 update.  Some were replys to older posts and some only touched on a single issue.  I wanted to consolodate into one thread, and hopefully get teh attention of Verizon to maybe reply here.
    For reference, a lot has been discuss here --> https://community.verizonwireless.com/message/874446
    Summary:  Verizon and Samsung have finally updated the Stratosphere almost 1 year after release.  This updated the phone from Android 2.3.5 to Android 2.3.6.  Going by filename, this is known as the FF1 update.   This update went live at the end of August 2012, and most users were upgraded before mid September 2012.
    There were some noticable changes in this update:
    -Lock screen has changed.  The puzzle piece and glass lock options have been removed.  New options have been added, such as facial recognition unlock.
    -Call answering screen has changed, introducing the option to ignore call with a message.
    -Camera now has digital zoom ability.
    -Ability to uninstall the 2 games the phone comes with (Need for Speed and Lets Golf)
    -Phone icon has changed ever so slightly
    -Wifi icon now included up and down arrows to indicate data is being sent or recieved
    -Wallpaper no longer "stretches" over multiple screens - ie, it no longer scrolls as you move from screen to screen
    -The visual voicemail app has been improved (I have personally not used this feature)
    -Callback number is now supported in text / picture messages
    -Android core OS updated from 2.3.5 to 2.3.6 (both versions are still Gingerbread)
    -Update to how the device deals with the end of scrolling.  It used to rubber-band bounce back, now it will just give a green bar and expand the bar as you scroll.  (I cannot fault Samsung for this change as this was at teh core of an Apple lawsuit and has been changed in newer versions of Android.)
    -(I am sure there are more.  please list any others you may have noticed)
    I have found some problems, and others have confirmed that this is (at least) somewhat widespread:
    -The biggest problem is with wifi connectivity.  Upon an initial connection to wifi, everything works great.  After somewhere between 15minutes and 2 hours, problems start happening.  Its as if the wifi keeps hanging or reconnecting.  Download speeds (tested with the SpeedTest.com app) slow to about one third of normal.  Apps like Facebook that require a constant connection will just time out.
    -It appears the signal strength for 3g and 4g connections is lower.  There are places where I used to get a 4g connection, and now I only get 3g.  Some palces I fall back to just 2g digital.
    Another minor issue i found was with text messages.  When you reply to a message, it no longer automatically focuses the text in the input box.  You have to first click into the box to start typing.  Not a huge deal, but one more step to take over and over.  Minor annoyence.
    At my house, I struggle to get a 3g or 4g signal.  I depend on wifi for my data connection.  So with the wifi connection problem introduced by teh FF1 update, my phone is somewhat useless to me now while at home.  Here are teh troubleshooting steps I have been through so far to attempt to fix the wifi problem:
    -Complete factory reset on my phone.  (did not help)
    -Pull battery and SIM card out of phone for 15 minutes.  (did not help)
    -Went to a Verizon store.  The guy at the store was helpful, and said he also had a Stratosphere and was getting the same wifi problems after the update.  He said all he could do was to send me out a replacement phone. I got the replacement phone, and it had the same problems.
    -I read in multiple palces that Android 2.3.6 has a bug within wifi and DHCP.  Apparently if you have a DHCP lease set to "forever", the phone will keep requesting a new address.  Setting the DHCP server on the router to something like 2 weeks, or using a static IP is supposed to solve this.  I have a NetGear N900 router, and I can not change teh DHCP lease time.  It appears, however, that my router is not sending out "forever" leases.  But just to make sure, I gave my phone a static IP.  (None of these steps made any difference).
    The only thing that temporarily fixes the problem is a reboot of the phone.  This will again give you anywhere from 15min to 2 hours of good wifi use before problems start happening.
    I have now had this update for over a week, and on 2 phones.  I still can't maintain a wifi connection for much longer than 15 minutes without problems starting up.
    I am asking Verizon or Samsung to at least confirm this issue if possible.  Maybe there are newer revs of the Stratopshere hardware that don't have this problem.  Or there is something unique about my (and apparently others) situation.  But it seems like Verizon's current stance is to offer a repalcement phone (as currently all Stratospheres are within their 1 year manufacture warranty as the phone has not been ouy for quite 1 year yet).
    I am asking for a workaround for this problem, or a true fix adressed by a new software update, or at least allow us to roll back to the original Andorid 2.3.5 software.
    I have had my original Stratosphere for almost a year with no wifi problems - then get the FF1 update and have had nothing but problems on 2 different phones.
    Thank you for your time.

    Thanks for starting a comprehensive thread on problems with this update. I want to add one more.
    I have Bluetooth in my car (a 2004 model), and previously the phone has connected to it practically instantly when I start the car. Since the update, I have never been able to connect the phone to the car by Bluetooth. Several times the phone has made a standard notification sound at the moment it should be connecting to Bluetooth, though no notification appears. I have no idea what that could mean.The car's Bluetooth shows up as paired in the list of devices in Settings > Wireless & networks > Bluetooth settings. I haven't seen this widely reported as an update issue, but perhaps some others have experienced it too.
    UPDATE: I finally did some testing, and found that the notification was to signal the extremely brief appearance of a dialog indicating that the car's Bluetooth was requesting a connection. Accepting that request let the phone connect with the car, and calls went to the car's sound system as they should. When I turned the car off and back on (just the electrical system; not wasting any gas on this!), the connection was established immediately, so apparently the acceptance only had to be done once. Nevertheless, it did have to be done, and the dialog notification disappears within seconds. I believe it would have been possible to go into Bluetooth settings and accept the connection request there if I missed the notification; but not seeing the notification, I might not know to do this.
    One further observation: When I turned the phone's Bluetooth off and back on after a connection had been established, leaving the car on the whole time, the two did not reconnect. I believe that may be different from before the update, but I'm not really sure.
    Message was updated by David Rensberger

  • EFI Problems after last update anyway to downgrade ??

    Hello
    EFI Problems after last update anyway to downgrade ??
    i have updated my MacBook 2010 EFI to MB71.0039.B0E which is 2.1 version
    after updating to this version the Boot time become much slower when i want to change boot partition
    and shutdown become very much slower and startup too
    i tried to install Mac OS X Lion again but it doesnt help
    can i downgrade to this version 2.0 ???
    or when Apple will release the new version ?
    or where can i send a feedback regarding this issues !!!!
    Thanks

    These are user to user forums. If anyone knows the answer, they will give it.
    You can always call Apple support which may charge a fee or you can patiently wait for an answer here, which is free.

  • Share and save problem after latest update

    hello,
    i have share and save problem after latest update - i have installed ps touch on nexus 5 about 2 months ago and until yesterday everything was good but after latest update i can't save and share images in ps touch ( i do reinstall this app  but problem is still  and app doesn't work properly   ) how  can i downgrade to the old version ? Could you fix this problem quickly ?

    i use app which called "aLogcat"
    --------- beginning of /dev/log/main
    I/dalvikvm(24476): Enabling JNI app bug workarounds for target SDK version 11...
    D/dalvikvm(24476): GC_CONCURRENT freed 174K, 2% free 17054K/17264K, paused 2ms+2ms, total 15ms
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    --------- beginning of /dev/log/system
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=27743080, downTime=27743066, deviceId=4, source=0x1002 }
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=27743086, downTime=27743066, deviceId=4, source=0x1002 }
    D/dalvikvm(24476): GC_FOR_ALLOC freed 122K, 1% free 17271K/17428K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 10K, 1% free 17434K/17604K, paused 7ms, total 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 65K, 2% free 17690K/17928K, paused 8ms, total 8ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 17.615MB for 328336-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18010K/18252K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18011K/18252K, paused 9ms, total 9ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 18.073MB for 479536-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18479K/18724K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 18481K/18724K, paused 2ms+1ms, total 10ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 6ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 18.532MB for 479536-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18949K/19196K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 19418K/19668K, paused 1ms+1ms, total 10ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19592K/19844K, paused 8ms, total 8ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 20.049MB for 933136-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 20503K/20756K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 21416K/21668K, paused 1ms+1ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 50K, 2% free 22351K/22580K, paused 7ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 5K, 1% free 23900K/24140K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 1% free 25824K/26084K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 3411K, 14% free 24528K/28204K, paused 12ms, total 13ms
    D/dalvikvm(24476): GC_CONCURRENT freed 2814K, 14% free 24256K/28204K, paused 2ms+1ms, total 11ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 9266K, 1% free 17270K/17424K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 15K, 1% free 17575K/17748K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 22K, 2% free 17875K/18072K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 2% free 18195K/18396K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18517K/18720K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18838K/19044K, paused 11ms, total 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19159K/19368K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19480K/19692K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19974K/20192K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 20616K/20840K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 21431K/21664K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 22714K/22960K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 2% free 24004K/24432K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 8478K, 33% free 17593K/26228K, paused 14ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 32% free 17895K/26228K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 31% free 18198K/26228K, paused 11ms, total 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18519K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 29% free 18840K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19482K/26228K, paused 2ms+1ms, total 14ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 10ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 23% free 20297K/26228K, paused 2ms+1ms, total 15ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 19% free 21260K/26228K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22543K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 9% free 23979K/26228K, paused 21ms, total 22ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 8485K, 33% free 17598K/26132K, paused 13ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 25K, 32% free 17894K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 12K, 31% free 18204K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18524K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 28% free 18845K/26132K, paused 8ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19487K/26132K, paused 1ms+0ms, total 9ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 20129K/26132K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 20% free 21091K/26132K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22375K/26132K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 9K, 9% free 24011K/26132K, paused 14ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 2147K, 10% free 23855K/26456K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed 8776K, 35% free 17337K/26304K, paused 3ms+2ms, total 20ms
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=564.0, y[0]=-50.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=28190972, downTime=28190972, deviceId=4, source=0x1002 }
    D/dalvikvm(24476): GC_CONCURRENT freed 186K, 31% free 17626K/25476K, paused 2ms+1ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 63K, 30% free 17884K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 3K, 29% free 18201K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 27% free 18696K/25476K, paused 2ms+1ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 25% free 19190K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 19831K/25476K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 19% free 20794K/25476K, paused 2ms+0ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 14% free 22078K/25476K, paused 1ms+2ms, total 14ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 7% free 23855K/25476K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 6% free 24176K/25476K, paused 2ms+1ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 6440K, 26% free 19562K/26216K, paused 9ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 93K, 23% free 20207K/26216K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 11K, 21% free 20935K/26216K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 18% free 21673K/26216K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22499K/26216K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 10% free 23695K/26216K, paused 9ms, total 9ms

  • IPhone 4s got problem after I update to 7.1.1. Battery drain so fast

    iPhone 4s got problem after I update to 7.1.1. Battery drain so fast

    The Ultimate Guide to Solving iOS Battery Drain
    <http://www.overthought.org/blog/2014/the-ultimate-guide-to-solving-ios-battery-d rain>

  • Had a problem after download updated itune, error 7 (window error 126) cant open itune at all

    Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

    Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

  • Please Read This To Reduce or Eliminate Problems after Software Update

    Hi all, I have been reading quite a handful of Mac users here reporting problems ranging from minor ones like slow downs to major ones like application crashes, and many of them blame the new OS and/or Security Updates.
    Without learning more from the details of how did they perform their Software Updates and Install, I am making a huge assumption that it maybe something they did or didn't do, one of the key things they did not do is Repair Disk Permission
    Below is what I called, the "ritual procedure" needed to perform before and after a Software Update, and also any other major software installation - to help reduce or eliminate "hiccups" afterwards, I cannot gaurantee that all macs all over the world will not suffer any problems after an update, but by doing so, you may help reduce it; I have 4 macs all together and so far I have not encounter any major problems after many versions updates.
    Anyway, I didn't come out with this series of procedures, I read it off somewhere in this Discussion quite a while ago, and thought I share it again with all of you:
    1.Before starting Software Update, unplug all external devices, FireWire, USB, hubs etc etc, not just turning them off but unplug the cables off your Mac, leave only your keyboard, mouse and internet connection on (unless you are using a wireless keyboard and/or mouse or on wireless internet)
    2.Repair Disk Permission
    3.Restart the Mac, then start your SU, do not run any other apps.
    4.After finishing SU, restart your mac; If you are updating OS or Security Updates, Restart is required.
    5.Repair Disk Permission again
    6.Shutdown and re-plug in everything and start up your mac as normal.
    I know the procedure is pretty long and "troublesome", especially the unplugging and restarting part, but so far it really has done my macs good, so I am going to "swear" by it... my FireWire, USB devices etc still work as normal.
    This is really contrary to that "Macs are easy to use", yes, no doubt about it, but the software updates etc is just well, put it this way: The Mac OS when it comes to updates, is very very delicate... so handle with it great care, it will just turn out okay.
    Cheers

    Thank you for posting that. I posted a similar set of suggestions here:
    http://www.macmaps.com/backup.html
    Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

  • Problem with my Lumia 928... started after Amber update.

    First, I to state that I love my Lumia 928 and the Windows Phone 8 OS. Second, I've been a Third-Party Microsoft developer for over 14 years and just started developing for Windows 8 and Windows Phone 8. So, I'm not a normal consumer but one that will try everything in my toolbox before asking for help or even writing posts like this.
    History:
    As of October 6, 2013, Verizon is sending me a new phone (not guaranteed to be new. ) to see if that fixes the issue
    Used for work and personal emails so I can't just go and do a "hard" reset without have extreme headaches.Last resort before I get my "new" phone, I've broken down and started doing a "hard" reset (actually this is my second time).
    No damage to the phone (Verizon employee has confirmed these, hence the new replacement)
    No cracked screen
    No frame cracked
    No water damage
    Shortly after the Amber update, I started having problems. In order of oldest issue first.
    Lock upsRandom apps just freeze. No rhyme or reason. No pattern. Just all over the board.
    No touch responseSide buttons work but that does be no good when I can't select anything on the screen. Solution, "soft" reset and things are good... for a while.
    Phone call speakerStarted losing phone calls. Thought it was a signal issue until I noticed that the call were not actually dropped. Speaker just started cutting in and out (completely) and sometimes it would just dim to almost nothing and then come back.
    Microsoft account
    This is new as of October 5, 2013
    October 4, 2013, nothing was wrong. Then the next day, my Live account associated with my phone stopped working. Keeps saying "Not up to-date". Had to create another account to get my emails. As of today, it's still not working. Unfortunately, I didn't write down the error code so I can't post that here.
    Is anyone else experiencing these issues after the Amber update and if so, what did you do to resolve it (if you did)?
    Thanks,
    Stu

    The Amber update came to our Lumia 928 and we had just activated it like one or two weeks prior, so we were just getting to know the phone.  In answer to your difficulties following the Amber update:
    millerstu wrote:
    Shortly after the Amber update, I started having problems. In order of oldest issue first.
    Lock upsRandom apps just freeze. No rhyme or reason. No pattern. Just all over the board.  The only "freeze" or app problem I recall is the GREEN SCREEN when opening the camera, happened once, and a power off and restart fixed it.  The problem has not come back, to date (this was several weeks ago).
    No touch responseSide buttons work but that does be no good when I can't select anything on the screen. Solution, "soft" reset and things are good... for a while.  I have heard of this happening to others, but I have not personally experienced the screen freeze issue. 
    Phone call speakerStarted losing phone calls. Thought it was a signal issue until I noticed that the call were not actually dropped. Speaker just started cutting in and out (completely) and sometimes it would just dim to almost nothing and then come back. I've had this happen on a couple of calls - the caller becomes very garbled and static filled.  I've had to hang upand call back - and they say the same thing happens on  their end, my voice is all garbled, like I'm underwater or something.  Not all calls, and not frequently, but maybe once every couple of weeks.
    Microsoft account
    This is new as of October 5, 2013
    October 4, 2013, nothing was wrong. Then the next day, my Live account associated with my phone stopped working. Keeps saying "Not up to-date". Had to create another account to get my emails. As of today, it's still not working. Unfortunately, I didn't write down the error code so I can't post that here. This has not happened, to date, for me.
    My screen is cracked due to a drop, prior to the Amber update.  (Yeah, it was nearly brand new when I dropped it   )  That doesn't seem to affect the overall function of the phone though. 
    So, to sum, I am experiencing some of the issues you described, but I'm not sure it's Amber, maybe just the phone design itself.  I don't know that a "new" phone will resolve things either.  Please do keep us posted...

  • 4G option missing on Lumia 820 after Amber update

    Hi
    I bought Lumia 820 from singapore (Starhub variant), it was SIM-unlock can use any SIM. i came back to my country Bangladesh. it was working like a power house. i'm ok with the performance. later i faced one power problem issue. i took my handset to Nokia Service center. they fixed the problem as we ll as update my firmware to amber update (which i didnt request to do for Nokia care official. they did it by their own), it was working good, all new feature data sense, sms call block, nokia smart cam, radio etc. every things works fine but i found 4G option is not available in the data selection mode. only 2G & 3G is available. later i checked in nokia web site and found the FW version is for bangladesh only. my question is the FW blocked the 4G option due to no 4G service provider or any other issue. i chose 820 only for LTE option because i traveled a lot to SGP and KL for business purpose and their is 4G service available.
    again yesterday my phone got restarted automatically after that i can not sync google contact (only) and my SMS+Call Block option is wiped from the settings menu.
    can any one suggest how i can solve this without going to Nokia Care center because local nokia care center service is not good enough to deal with. if no one is available answer my question than i need to visit NOKIA CARE center.
    thanks and welcoming expert opinion from expert/pro users.
    cheers
    Sayeed

    hi mate,
    if the 4G option was initially present on the phone when you bought it from Singapore, it appears that your local Nokia Care point has flashed the Amber update for your local region (Bangladesh). as LTE services are not widely available in your country, as you have rightly said, 4G is not present in the options.
    unfortunately in this case, there is nothing you can do except to go back to Nokia Care and tell them to put the initial firmware (w/Amber, mind you) back onto your device as that was why you bought the device (to use 4G services).

  • Start up problems after security update 2014-002

    Hi, after this update sometimes my Mac does not start up like it should: the Dock is not appearing and the screen is flashing between fully grey and thenormal background.  The only cure seems to be to restant a second or third time. Already resetten PRAM, used disk utility (no problems) and repaired permissions. Does anyone else has encountered this problem? Thanks

    I have always had good luck with DiskWarrior. I've had serious issues and DiskWarrior has always come thru .
    Are you nervous because you have never used DW before, or are you afraid it will hose your system?
    By your report, it kinda sounds as if your hard drive has either failed or on it's last leg.
    I'm guessing you had issues with the drive before installing the update and you did not know it. Updates tend to point out problems in a big way sometimes.
    I run repairs on my hard drive before installing any updates.
    I don't remember, does Jaguar have S.M.A.R.T. status in Disk utility? If so, what does it say about your drive?
    Dale

  • Problems after Airport Update

    I own a 2ghz/2gb MBP running 10.4.7. After I installed the latest Airport Update 001, my computer has been acting up. The MBP now has major issues connecting to my graphite airport, though my eMac (10.3.9 w/latest security update) does not have any issues. The graphite airport has WEP enabled, but the MBP refuses to keep the password in the keychain. Everytime I try to connect to my network (upon wake up or start up) I receive an error stating that there is a problem joining the network. After about 10 seconds, though, it connects. Also, it doesn't recognize that the airport is one of my "trusted networks." Before connecting it says, "none of your trusted networks could be found, would you like to join (my network name)."
    What I have done so far:
    Repaired permissions.
    Created a new user (has same problems).
    Shutdown and restarted all of my computers/router/modem at least 5 times.
    Put the WEP password in the keychain manually.
    Changed the Airport's channel a few times as well.
    MacBook Pro 15", Powerbook 12" G4, eMac G4 & iMac G3   Mac OS X (10.4.7)  

    After countless nightmares trying to connect to my home network, and one kernel panic, I zapped the update with AppZapper. No problems after that.
    Apple, I'm sorry ,but I think you got this latest SU wrong!

  • New iPad with retina display with 30 pin connector mirroring to TV with dvi adapter problems after software update

    Hi. Good day to everyone my New iPad with retina display 30 pin connector will not mirror to TV even with divi adapter after software update. Adapter works fine. Or is it a software glitch with IOS 7.04? I've tried resetting and reconnecting nothing seems to work.

    That's one of the weird things.. it recognizes it maybe 10% of the time. And usually, only after I do the two-button reset. Problem is.. since it won't charge above 2%, anytime I try to do a restore or anything like that using iTunes, my device shuts off and I lose whatever progress I'd made.
    So, an update... after reading through a bunch of similar complaints (there are literally 1000's of them so there's NO WAY this isn't somehow ios7 related, thanks a lot APPLE ) I decided to try a restore in recovery mode. After 3 hours and several disconnections... I ended up having to just set it up as a new iPad, as the restore did nothing. Weirdly though... as I was doing the restore in recovery mode.. I noticed I'd gotten up to a 10% charge.. higher than it's been since September, so after setting it up as a new device, I turned it off and plugged it in using the wall charger. 2 hours later and I was up to 38%. Still not great, as my iPad, before ios7 could've fully charged twice in the amount of time it took for me to now get 28% more of a charge. And that's with a fully cleaned out device.. so that really ***** and I'm now more confused than ever.
    But I'm gonna leave it overnight charging and see what I come up with tomorrow. Sadly, when I paid $600 for it in February, I never expected to have to play "wait and see" with it...

  • Netscape cursor/text problem after Software Updates

    A friend of mine recently ran Software Update (3) updates and ended up with a reasonably serious issue with Netscape which he uses for e-mail. Here's his description...
    "I did a routine Apple update the other day:
    Mac OS X Update (Power PC) 10.4.6
    QuickTime 7.1.1
    J2SE 5.) Release 4 4.0
    Since restarting after that update, the screen display of text in my
    Netscape email program has been damaged. Trying it a second time with
    the update combo did not help.
    The main complaint is that I cannot see the current or previous
    characters being typed, nor the cursor itself, nor the end of the line
    after an automatic return. Ends of lines are replicated for some reason,
    cluttering up the typing window.
    A couple of indications of how screwed up it looks: notice the font
    gibberish below the text, every touch of the return key yields an
    apostrophe, and then there's the other clutter that appears below and
    around the signature.
    When I do spellcheck, some (but not all) of the stuff disappears.
    The spellcheck itself doesn't catch many errors anymore. .
    All the best,
    ph"
    Here's a screenshot of the issue...
    http://homepage.mac.com/wellesgoodrich/grrrr.jpg
    Does anyone have any guesses what might be wrong? I had him run the 10.4.6 Combo Updater as occasionally the combo fixes issues with Software Update versions. It made no difference. Unfortunately, even though I've preached having an external backup prior to any system upgrade, he has not yet done so. His computer is the 17" Flat Panel iMac 800 mhz.
    Thanks!
    G4 1.5GHZ, Rev.A iMac, Mac IIsi, Mac Plus   Mac OS X (10.4.6)  

    Did your friend check his hard drive for any directory problems with Disk First Aid repair via Disk Utility when booted from the Tiger install disc before installing the 10.4.6 Update and other updates and were all running applications quit before the install - namely Netscape?
    As a first step, I suggest Resolving Disk, Permission, and Cache Corruption for system troubleshooting procedures and when doing so, follow all steps/instructions in the order provided including using a system and user cache cleaning utility.

  • Printing problems after security update

    Any fixes to the printing problems (for me it is with Quicken) after the security update??
    Don

    There are several threads popping up over in the Mac OS X v10.6 section of ASC about the Security Update.
    Mac OS X v10.6 Snow Leopard: Mac OS & System Software: Apple Support Communities
    It seems that the update has killed printing and other functions for some PowerPC Applications.
    Start with > after Security update 2012-001 cannot...: Apple Support Communities

Maybe you are looking for