1. Check out our companion app, Forums for Android! Download from Google Play

force close issues (many processes) not going away!

Discussion in 'Android Lounge' started by vanbrueo, Aug 8, 2012.

  1. vanbrueo

    vanbrueo New Member
    Thread Starter
    5

    Jul 27, 2011
    3
    0
    5
    I'm working my way thru a "force close" issue and so far just searching the forums hasn't nipped it.. Have HTC Thunderbolt -I'm rooted, running BAMF SOAB, go launcher w/several add-ons.

    Have some battery, ram, and processor management apps that could be the cause.

    Phone: ADR6400L
    Android version: 2.3.4
    HTC Sense version: 3.5
    kernal version: 2.6.35.10-bamf_0.4-gf4df8b
    build number: BAMF Son of a Bliss v1.04

    The force closes don't actually seam to be stopping functionality so really, if I could just turn off the notification that would be great!

    All of the following processes have been force closing at one time or another:
    Google search framework
    Voice search
    Google play
    Lookout
    other random stuff (mostly connected to google)

    Some ideas:
    -google + app could be at fault but not sure why lookout would be tied in..
    -could be a recently downloaded app. Tried removing several (inc google+ but couldn't isolate). Have since reinstalled most.
    -could be gmail sync issue but not sure how to trouble shoot
    -could be a battery, ram, or processor management app? Maybe one of the go launcher add-ons

    what I've tried:
    -uninstalled several syncing apps (google +, facebook, calengoo). didn't isolate so I reinstalled.
    -terminal: su fix_permissions doesn't end the problem
    -cleared cache on most apps to no avail.

    Thanks in advance for your ideas!

    ;) -VB
     

    Advertisement

  2. !on

    !on Well-Known Member
    93

    Aug 14, 2011
    824
    120
    93
    Male
    UK
    Maybe flash a different g_apps zip in the recovery?
     
  3. vanbrueo

    vanbrueo New Member
    Thread Starter
    5

    Jul 27, 2011
    3
    0
    5
    It appears that the problem went away after the latest go launcher update. Not sure if that's why, but we'll see if it lasts..
     

Share This Page

Loading...