MMS messaging problems after jellybean update.

I am having issues sending and receiving any MMS messages since the update.  If I send one it appears on the phone that it was sent.  I have questioned several people and they do not receive them.  Also I have had several people send me pictures and messages that I do not receive.  I have checked the settings and can not find what is causing the problems.  Also not receiving all my calls.  It's random.  Sometimes the phone will ring normally and sometimes it doesn't ring or show that I have missed a call.  Any suggestions? 

    Hello to you Kabull!
Getting the newest update is always exciting, but I definitely don't want you to experience any difficulties! I will be delighted to provide some suggestions to help out!
It seems to me that both issues may actually be related. Generally when a phone doesn't ring or show a missed call and you aren't able to send/receive messages you may not be experiencing a solid connection to the network.
I would start small and highly recommend leaving your phone on, pull the battery out, pull the sim card out. Leave everything apart for about 10 seconds and put everything back together.  This will cause your phone to "reprogram" or update. 
Let us know how this goes!
Thanks,
MelissaM_VZW
Follow us on Twitter @vzwsupport

Similar Messages

  • 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

  • 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

  • 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>

  • 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.

  • HT6065 Problems after latest updates for the mac

    After the updates my computer keeps  freezing  the wheel keeps spinning! any sulutions?

    When you have the problem, note the exact time: hour, minute, second.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough. It is never necessary or helpful to post more than about 100 lines. "The more, the better" is not the rule here.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Problems after FW update

    I have been having slight problems after updating to the new firmware. I updated yesterday and had to reinstall all of apps that I had lost since I forgot to make a backup. I tried to install facebook and it worked, but then when I tried to validate it it kept giving me an error saying it was unable to connect. The same thing happened w/ pixelpipe. I uninstalled both apps and tried to reinstall them, but then a new problem started where if I go to the ovi store or app manager I will get the preparing for installation bar to appear and start and then stop and do nothing. My n900 can still mutlitask and do other things, but not that! I'm getting urked because I don't know when the next FW is coming out and would like to be able to use my device as it was intended! Any help or likeness to this complaint will help not only myself, but other users and nokia determine what the hell is wrong!

    I disabled and reenabled the repositories and got the same time out messages. https://downloads.maemo.nokia.com/fremantle/ovi/./Packages     Resolving host timed out: downloads.maemo.nokia.com    My connection is timing out, but why? This was the ovi store. Can anyone tell me if the repositories are correct?

  • IMessage problems after iOS6 update

    Hi All,
    Is anyone getting similar problems to this after iOS6 updates?
    My iPad is used on 2 wifi networks, my home network and work wifi, I pick the pad up on a morning, shove it in my bag, go to work and pick up the wifi there, carry on as normal, repeat in reverse when heading in the opposite direction.
    On iOS5, my iMessages would simply carry on the conversation when rejoining either network *there is no 3g connection on this ipad*
    Since updating, I leave for home, get to work and iMessage refuses to resume, messages stick at about 90% sent, then fail, I head home , rejoin the home network and boom, it just picks up where it left off
    When at work, occasionally it might start working after 10 minutes or so, but today i've been sat about 5 hours so far, no dice
    I have tried just about every combination of restarts, resets, updates I can think of, including, changing the DNS on my device to the same one I use at home *8.8.8.8* , shutting iMessage down, renewing the DHCP lease, Hard resets, soft resets ,  forget wifi network, restore network setting  you name itI've tried it
    Under iOS5 I had used the device for months without doing so much as a power down and not had one single 'not delivered' failure on an iMessage, since iOS6 I've probably had abotut 50% service from this.
    As far as I know, nothing has changed on either wifi networks, everything else works fine on the works network, browings, itunes, app store, skype etc etc.
    I'm at a loss as to what to do next, and yes, I've also done a full device restore as well for good measure, with a iCloud back up, again, it restored, went to messages and it just sat there doing nothing until I got home , where the messages just sent first go.
    Massively frustrated in what I can only see as something that's been introduced as a result of this iOS6 upgrade.

    I may have found my own answer... it seems that anything less than 3 bars of wifi signal after rejoining a network and the message wont send, I switched my device off, moved closer to the wifi router, tricky as it's in another building, rebooted, managed to get two bars of wifi, still wouldn't send, moved even closer to the router manged to just get 3 bars and pow, the message sent right away!
    Moved away back to my normal desk at work, signal dropped to 2/1 bars of wifi, however now, messages continue to send now.
    Clearly when I'm at home I'm only ever a few feet away from my wifi router and always have solid 3 bars of signal, not the case at work.
    However, this still only appears to be something that's been introduced at the iOS6 update as this was never an issues prior to this, but has been an issue right from day one after updating!

  • Touch sensitivity problem after latest update iOS 6.1

    Hi guys,
    does anyone else have the same problem? After updating my iPhone 5 to latest version iOS 6.1, touch screen stared to work wierd. I have to slide a few times just to unlock my screen. Can not poroperly open any application and when I want to scrool, that's pain in the ***.
    Can anyone help me about this? Is that problem with the update iOS 6.1 or my iPhone5, 3 motnhs old become broken?
    Thanks in advance.

    Hi. I have a 3 years old 3GS which i have updated whenever a new iOS was avaialble. This has been working with improvements besides the fact that the phone gradually is becomming slower with increased functions and especially from iOS 6.0 and up. It has however worked ok keeping in mind that it is a 3 years old phone. With the latest update to iOS 6.1, however, the use af the iphone has severely been affected, much like you other guys are experiencing. The below described behavior of the iphone has never happened before, until the faithfull morning of the 4th of februar, 2013 when i accepted to update the iOS to 6.1. Immediately after the update the problems started:
    When sliding to unlock the phone it takes several attemps (sometimes 10 or more) before the slider actally follows my finger to the end and the iphone unlocks.
    When typing  (eg. a text msg. or email message), it is now allmost impossible to type a meaningfull message because some of the keys do not respond and other only respond to a very hard press. Only when typing very slowly, making sure the touchscreen is actually responding, a usefull message can be made. It seems like the sesitivity of the touchscreen has been altered making it less sensitive.
    The same behaviour is observed for other functions and Apps like games which are now impossible to use due to the poor response of the touch screen.
    Now i only wish i could roll back the iOS to an earlier version (like 5.1.1) where the iphone was really working well.
    I really hope that a new and improved iOS will be out soon to correct for this problem

  • Impossible problem after latest update of 10.5 and 10.6

    Hi all,
    I've an incredible problem that I'm not able to solve...:
    after latest update of 10.5 (some days before SL) I noticed that mouse movement was very strange and every 10 seconds (about) the mouse acceleration speeds up and after 1 seconds turn normal. The problem repeat in infinite cycle. With 10.6 and 10.6.1 is the same.
    I made also this test: I boot with Leopard DVD and tested the mouse movement on the install screen. The movement is ok but if I boot with Snow Leopard DVD the mouse movement on the install screen is wrong.
    Then... this is not a problem of a software on my hard disk (my first suspect) but some difference on the driver of the mouse that on my iMac has this problem.
    Someone can help me?
    Thank you all

    faabri
    What kind of mouse are you using?
    EDIT: I just saw your other post here . . .
    You should include all the detail in your post here, so that
    people can help you with as many facts as possible.
    Message was edited by: ~Bee

  • E63 sound problems after firware update

    Hi,
    I installed the new ovi suite on my PC and it said there was a new firmware so I though i would install it on my E63. Since that time I am having problems with sound coming out of the phone.
    After the upgrade the phone restarted and seemed normal, played the nokia sound but then there were no tones. Because the phone was fully reset, I went to setup the phone and select the ring tones and it would not play them. Also at that time I received an SMS and no tone played.
    I then went into the media player and nothing played. Then all of a sudden it started to play, and all tones were back so i though it was OK.
    This morning no tones again. could not change my tone either. went into the music player, plays music then I could go back and had tones.
    The Firware version is now 200.21.012. Has anyone else had problems with the update?

    I had no problems with that update nor the v4 update available in North America. Try a reset. Here is the discussion:
    /discussions/board/message?board.id=communicators&message.id=43316&query.id=1042038#M43316
    If I have helped you with your problem in some way, please take a little time and hit the kudos button in my post. Without your feedback, I don't know if I am being helpful or should just be put out to pasture.

  • 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!

Maybe you are looking for