Weird problems after System updates

I downloaded updates for iTunes and Java earlier this week, and now I have some weird behavior going on with my iMac. I'm running 10.5.8 and Safari 5.0.2. When I'm using the computer the windows have started jumping around, moving from side to side, or one window moving to the front, then the back, by themselves. There is sometimes a noise...hard to explain, but sounds kind of like bom, bom, bom. It's happened before, but usually goes away with a restart. Not this time, though...
Anyone else had this problem, and/or hopefully able to suggest a fix?

Hi,
Rule out any problems with the startup disk since the software is "jumping around" ...
Insert your install disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu and launch Disk Utility.
(In Mac OS X 10.4 or later, you must select your language first from the installer menu)
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
Select your start up disk and click Restart
While you have the Disk Utility window open, look at the bottom of the window. Where you see Capacity and Available. M*ake sure there is always 15% free space.*
If the startup disk is ok, might be a good idea to run the Apple Hardware Test considering the, "bom bom bom" sounds, instructions here.
Intel-based Macs: Using Apple Hardware Test
Carolyn

Similar Messages

  • Xperia z1 Problem AFTER system update to latest software 14.3.A.0.681

    Hello people, First of all let my just say that I am new into the ''smartphones world'' so please excuse my queries if they proof to be 'obvious' to you! I have carried out a system update to my Xperia Z1 phone yesterday (Android 4.4.2. kitkat, latest available software 14.3.A.0.681). The update seem to have been correctly performed. However I have since encounter the following issues/problems with my phone and do not know how to fix them: 1) First of all my phone will no longer rotate...why is this? Is this related to the update?? Pictures/photos can no longer rotate and also phone screen does no longer rotate! Why is this..? 2) Second the 'Notifications Bar' structure has changed : is this also the result of the update or can I do something in settings to fix it and make it as before? When I scroll dawn the notifications bar, the icons are no longer displayed at the top line but are instead spread underneath BUT this is AFTER I press 'Quick settings'. 3) Battery signal icon has changed completely: no lines included inside icon to show usage but instead usage %age is now displayed. Also, when I charge my phone, there is no icon flashing as before and now lights flashing.. 4) Also when I want to use the phone after it has remained unused for sometime it states 'swipe to unlock' and makes a 'funny' note upon performance of the act: this was not the case before.. Can you please help me with the above? I am freaking out because I am excited with my new phone and would love to make full use of it properly but it is a bit hard for me since I have no clue how to fix issues/problems appearing every now and then since I am new into these things.. Thanking you in advance

    Hi there,
    I think you have fixed your 1st issue.
    2) Yes, Kitkat has changed the Notification Bar structure. Its a bit annoying, but to get around it you can use Widgets - Tools and select the Icon, such as WIFI to be placed on your home screen to avoid multiple clicks. You cant do anything in the settings to make it like before.
    3) Battery Signal Icon - Again a Kitkat update has done that. The good thing is that it has enhanced Battery life considerably.
    4) I am assuming you are stating about the "sound note" it makes when you swipe in. Thats again a Kitkat feature and you can get rid of it though Sound settings if you dont like it.
    Reality is that Kitkat runs very well on Google Nexus 5. Apart from that it has issues on every other Android power Smartphone out there. I also own a Nexus 4 who recently got upgraded to Kitkat and compared it with Nexus 5. Was not impressed to be honest.
    As of my upgrade on Z1, I have been facing Volume issues. When I play a video the volume is minimized for some reason. Pause and play again and it goes to Normal. I have to reboot it sometimes to play normally. It also takes ages to connect to my 3G provider, whereas previously it was fast enuf. I hope the next upgrade will fix those issues. 

  • Wireless problem after system update

    After installing system updates to OS X 10.3, the system stopped connecting to my wireless network. I'm pretty sure the updates were the cause, because I downloaded and installed the updates over the wireless network. The problem is not in the network hardware, because I am posting this thread over the same network from and IBM Thinkpad (that still works on the network).
    The iBook can see and connect to the network, but it does not recieve and IP address. Any assistance would be appreciated.

    I found some fixes to this problem if anyone is interested:
    http://www.wwco.com/~wls/blog/2007/01/27/apples-security-update-2007-001-for-air port-breaks-internet-connectivity/

  • MySQL socket problems after system update

    I have been using my new Mac Mini Snow Leopard server as Squeezebox Server for over a month wihtout problems. After a system update this weekend I started to get MySQL socket errors after reboot.
    Started; log sequence number 0 43655
    091213 17:10:04 [ERROR] Can't start server : Bind on unix socket: Invalid argument
    091213 17:10:04 [ERROR] Do you already have another mysqld server running on socket: /Users/admin/Library/Caches/Squeezebox/squeezebox-mysql.sock ?
    091213 17:10:04 [ERROR] Aborting
    Although I have posted this issue to the Squeezebox forum (http://forums.slimdevices.com/showthread.php?t=72510) where it primarily belongs to I wanted to hear if anyone maybe had an idea what recent changes in Apple updates could cause this? Maybe someone else has similar MySQL problems with other installations? I am a bit desperate by now so any idea or hint is appreciated.

    Here was my solution/workaround for this issue to the rest of us poor fellas that have too fight around with Squeezebox server from time to time:
    I setup SBS to use the the standard MySQL installation on Mac OS X SL Server since I could get it to run without problems from Server Admin. Here are the instruction from the SBS Wiki:
    http://wiki.slimdevices.com/index.php/ExistingMySQLInstance
    However, I had to deviate a bit from that in order to make it work since it seems a bit outdated.
    First deviation was necessary for the MySQL access privileges. Notice the extra grant to slimserver@localhost. Don't ask me why but this worked. I do also not know whether both grants would be necessary because I haven't tried it. Feel free to improve it:
    # mysql -u admin_user -p
    Enter password: admin_password
    Welcome to the MySQL monitor.
    Commands end with ; or \g.
    Your MySQL connection id is 103 to server version: 5.0.24a-log
    Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
    mysql> create database slimserver;
    Query OK, 1 row affected (0.22 sec)
    mysql> grant all on slimserver.* to slimserver identified by 'slimserver_password';
    Query OK, 0 rows affected (0.13 sec)
    mysql> grant all on slimserver.* to slimserver@localhost identified by 'slimserver_password';
    Query OK, 0 rows affected (0.13 sec)
    mysql> flush privileges;
    Query OK,
    mysql> quit
    There were also slight differences necessary in the preferences setup because MySQL socket location was different from the standard one. Here are my db entries ~/Library/Application Support/Squeezebox/server.prefs:
    dbpassword: slimserver_password
    dbsource: dbi:mysql:database=slimserver;mysql_socket=/var/mysql/mysql.sock
    dbusername: slimserver
    Notice the extra mysql_socket configuration.

  • Small problems after system update

    I have a couple of problems which appeared after a recent pacman update. A lot of stuff was updated, including the kernel and xorg.
    1) Shutdown stalls at "Save system clock".
    2) Ctl-Alt-F(1-6) doesn't get me out of X11. Actually, this works sometimes, but usually not.
    I could fix these, if I knew where to start. Can anyone help me with some diagnostics? I have a pretty simple setup, no desktop, just ratpoison and the apps I need for work, mail, web.
    Can I redo an update, and if so, how? Is there (ever) any point in doing that?

    man hwclock:
          --directisa                                                                                                                                                                                                 
                  is meaningful only on an ISA machine or an Alpha (which implements enough of ISA to be, roughly speaking,
                  an ISA machine for hwclock's purposes).  For other machines, it has  no effect.   This  option  tells  hwclock
                  to use explicit I/O instructions to access the Hardware Clock.  Without this option, hwclock will try to use the
                  /dev/rtc device (which it assumes to be driven by the rtc device driver).  If it is unable to open the device (for
                  read), it will use the explicit I/O instructions anyway.
                  The rtc device driver was new in Linux Release 2.
    So as you can see, directisa is something that SHOULDN'T do anything on your system, but for some reason it is failing.  I'm guessing it is very specific to your hardware, though I've never heard of this happening.
    Last edited by codemac (2008-02-11 05:13:04)

  • ADSL / fglrx problems after system update [Solved]

    I'm hoping that somebody will be able to help me with this as I'm struggling to find the answer elsewhere in this forum. I recently installed Arch 0.7.2 base. I then got my internet connection sorted using my speedtouch modem as per the instructions on the Wiki. (using pppoa). I the installed xorg7, and gnome. I installed the ati-fglrx drivers from the instructions on the wiki. Up to this point, everything was working just fine.
    I then decided to update the system so I did a pacman -Syu and all seemed to go well. After rebooting the machine, it would not start x and from the debug messages on the screen it seemed to be saying that it was having a problem loading the fglrx module.
    I thought that I would try uninstalling the fglrx packages, then reinstalling and reconfiguring. I uninstalled them but then discovered that when I tried to download anything, my connection would be lost within a few seconds and wouldn't let me reconnect. The only way to reconnect was to reboot first. (I did find out that I had to do a modprobe ppp-generic first in order to connect since the update)
    I then deleted my xorg.conf, and created another using hwd -x and then managed to get back into gnome using the default drivers - but obviously with no 3d acceleration. (I have a radeon 9500pro by the way). I tried connecting again and this time tested the connection through firefox. I managed to open 1 webpage before losing my connection again.
    I'm sorry that I cannot post any logs just at the moment as I'm at work although I can later on. I'm just wondering for now if these problems seem familiar to anyone?

    I have exactly the same problem as atalman.
    My modem works fine, I can play eternal-lands/browse webpages for hours on end, but as soon as the modem is under any kind of heavy load, ie: ktorrent, amule, ebay (lots of images and open in new tabs) the connection dies..
    I try 
    killall pppd
    usually to find
    pppd: no process killed
    , so I then try
    pppd call speedtch
    which lets me know that the modem is already connected??
    So I have to unplug/replug the modem in, pppd call speedtch, then it connects again on a different 'channel'.
    dmesg shows no errors, I have enabled debug in the pppd settings which shows nothing, my firmwares are correct as Ive used the same on Slackware and Arch for ages. I originally thought the modem(rev 4) was dying so I swapped it over for my backup, an older manta/stingray  version, different (working) firmware but all the same problems.

  • Problems after system update

    After i made the last updates of my z2 from my phone, i cannot use my cellphone or made any call even i canot open my contacts, it always made restart the system, i need help

    Hi sherif_, welcome to the community!
    If you can unlock the screen of your device you can back up your data, just open PC Companion and click Start under Backup & Restore and follow the on-screen instructions.
    Running the repair:
    1. Install and open PC Companion then select Support Zone.
    2. Phone Software Update.
    3. Start.
    4. Repair Phone
    5. Continue
    6. Accept data removal
    7. Next
    8. Wait for prepare
    9. Select Phone
    10. Follow the connection steps
    Best of luck, keep us updated.

  • Problem after system update (base installed only) and other concern

    I have had two strange problems upon updating from Arch using pacman.
    1) My keyboard is no longer detected
    2) The BIOS time seems to be eight hours behind. (Setting the clock to UTC from another distro sets the clock right since my time zone is GMT-8)
    Does anyone have a work around?
    Btw,  here is rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/unimaps
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="localtime"
    TIMEZONE="/usr/share/zoneinfo/America/Los_Angeles"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # Scan hardware and load required modules at bootup
    MOD_AUTOLOAD="yes"
    # Module Blacklist - modules in this list will never be loaded by udev
    MOD_BLACKLIST=()
    # Modules to load at boot-up (in this order)
    # - prefix a module with a ! to blacklist it
    MODULES=()
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    HOSTNAME="myhost"
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
    lo="lo 127.0.0.1"
    eth0="dhcp"
    INTERFACES=(lo eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    #gateway="default gw 192.168.0.1"
    #ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network-profiles
    #NET_PROFILES=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network netfs crond)
    # End of file
    I commented gateway="" and ROUTES="" since I am using dhcp.
    I also have a concern about the latest kernel.
    I decided to install and build the latest kernel (from a chrooted environment) and noticed that I got a kernel panic (upon trying to boot into arch) no matter what I did (about it not being able to mount the root filesystem from /dev/sdb2). I could enable old pciix support, but I got annoyed by the clock skew outputs when building. How are devices, particularly SATA drives, named and accessed now?
    [edit]By the way, I have two separate kernel booting for Arch. Here's is my grub config for those
    title Arch Linux
    root (hd1,1)
    kernel (hd1,1)/boot/vmlinux-2.6.16.arch root=/dev/sdb2
    initrd (hd1,1)/boot/initrd26.img
    title Arch Linux (modified kernel)
    root (hd1,1)
    kernel (hd1,1)/boot/vmlinuz-2.6.20 root=/dev/sdb2
    Last edited by NoOneImportant (2007-02-13 23:16:22)

    zeus wrote:
    1) USB or PCI?
    2) TIMEZONE="America/Los_Angeles"
    3) What preceded a panic?
    Most likely the name of disks was replaced. Look in output.
    try Fallback image/ try UUID in grub/fstab
    1) USB
    2)I just tried to boot into arch and no dice.
    3)
    Starting balanced_irq
    Using IPI Shortcut mode
    VFS: cannot open root device "sdb2" or unknown-block(0,0)
    Time: tsc clocksource has been installed.
    Please append a correct "root=" boot option
    Kernel panic -not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
    Last edited by NoOneImportant (2007-02-13 23:31:22)

  • Problems with System Update 3.14.0019 after installation SP2

    Have you encountered problems with System Update 3.14.0019 after installation SP2 for Windows Vista?
     After this upgrade I view  this error: "An error occurred while gathering user information."
    Thanks for the help

    A known issue.  It wasn't supposed to be supported until SP2 is RTM.  However, look at the stickied post in the forum for some bad news about SU.
    x61s

  • 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

  • Lack of 3g after system update

    Hello :-)
    It's problem with Xperia E dual
    Few days ago I updated the system to the 4.1.1 version (compilation 11.3.A.1.39).
    Unfortunatelly after updating I've discovered that smartphone don't works with 3G. On the display I've only icon "E". Before updating there was typically "H". Of course now the transfer is slower than before and of course I'm not happy of that.
    I try to solve this problem - choose in menu list of available provider and... there are only 2G nets. Because I've functioning still in the same place of live and the problem has occured after the updating I'm sure that it's strictly connected.
    Is there any solution for that?
    Another problem is with trying to call. After system updating typically twice a day I have to restart smartphone because it's totally hanged. No one can connect with me and I can't call to anybody. Smartphone looks normally and doesn't give any siglan that something is wrong. But when I try to connect to somebody I direst the number and... there is no signal at all. After few seconds telephon return to main menu. There is also no record about this trial of connection in the list of done connections. It's very uncomfortable situation.
    Sure, there are also some adventages with the system updating but problems mentioned above are really annoing.
    Have you any solutions for it?
    Thanks in advance.
    Rafal
    Solved!
    Go to Solution.

    Hi, try repairing phone software with PC Companion or Update Service.
    http://www.sonymobile.com/gb/tools/pc-companion/
    http://www.sonymobile.com/gb/tools/update-service/
    Be aware that this will erase phone data completely, backup if necessary.
    Before proceeding with software repair, confirm with your Network Operator that there is nothing wrong with the network. Also, remove and reinsert SIM card and try again (have a close look at the contact surface, ensure that it is relatively clean).
    Don't forget to mark correct answer as Accepted Solution.
    If you find the post helpful, press Kudos.

  • 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

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

  • 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

Maybe you are looking for

  • Deactivating the automatic setup for creation of batch numbers in GR

    Hello, The user wants to key in the batch number for material purchased while creating  GR. But the batch number gets created automatically. Could you please help and letme know how can the user deactivate this? Is it activated in master-data or cust

  • Can't get iCloud to work properly from new MBP.

    I recently bought a new MBP and gave my old one to my wife. I deleted the calendar and contact info from my old MBP since she didn't need it. Only I didn't realize that it would also delete all the information from my new MBP that I had initialized f

  • How to get customer consignm orders (type of cat item KBN) updates LIS

    Good morning, we have an issue with this type of sales orders, we are trying to update an not standard info structure (created by us) but we have found that this type of category item is not relevant foe info structure updating (it has Statistics gro

  • Smartform LOGO Printing -reverse for a User???

    Hi Guy, This is typicial issue which I never got. He says what ever he is printing like PO,STO every logo is printing up in Reverse direction. He is using a Network printer and funny thing is all others are also using the same printer and they are ab

  • My adapter getting very hot

    hi everyone please help me...i have a one problem.During recharging my 60watt adapter is getting very hot. about 60celsuis.Is it normal?