Apps keep crashing

Discussion in 'Thunderbolt Tech Support' started by Banana5139, Apr 14, 2011.

  1. Banana5139
    Offline

    Banana5139 New Member

    Joined:
    Apr 14, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    I just got my tb and im new to this whole android thing. ive been playing around with it and downloading some apps and trying to figure out how to spot apps from running in the background...
    i dont know if i did something wrong but my downloaded app games such as bubble blast and angry birds keeps crashing
    sometimes it will give me the crash error and i would hit force stop and it sends me to the home screen but sometimes he brings be to the main menu screen on the app and i can continue playing for a bit before it crashing again. it seems to be only my downloaded apps...preinstalled games did not crash for me

    can someone help?

    i got it last night and couldnt connect to the web..wifi worked but the 4g didnt connect. once i hooked it up to my computer and did it several times the internet on the phone began to work...
    no idea if thats relevant at all
  2. Droid DOES!!
    Offline

    Droid DOES!! What iDoesn't Theme Developer Premium Member

    Joined:
    Jun 12, 2010
    Messages:
    6,321
    Likes Received:
    12
    Trophy Points:
    0
    Are you using a task killer? If so, uninstall it..they're not needed with Android.

    This thread has been Thunder struck!
  3. xan
    Offline

    xan New Member

    Joined:
    Mar 12, 2011
    Messages:
    320
    Likes Received:
    0
    Trophy Points:
    0
    I assume you meant "stop apps..." right?
    unlike a desk/laptop theres really no need to stop apps from running in the background, and depending on what and how you stopped some processes, thats probably why the phone is having issues.
  4. Banana5139
    Offline

    Banana5139 New Member

    Joined:
    Apr 14, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0

    I dont think i stopped anything important. i stopped apps such as the blockbuster and some other preloaded apps that i opened to see what they were..

    no i do not have task killer

    =( i dont have dropped calls or anything
    it seems its just the downloaded games that crashes
  5. Banana5139
    Offline

    Banana5139 New Member

    Joined:
    Apr 14, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    i did not download any kind of task killer =( is there one preinstalled?
  6. amuse
    Offline

    amuse New Member

    Joined:
    Nov 9, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    0
    HTC Thunderbolt Crash issues...

    You aren't alone. We have seen the crash issues with lots of apps, including our own app ShopSavvy.

    HTC and Google area aware of the issue, but until they fix the underlying issue there isn't much app developers can do. Here is the technical explanation from one of our developers:

    After much toying, tweaking, and hacking I can safely say that the problem we are encountering with the HTC Thunderbolt can not be fixed from our side of the fence. Doing testing across the Nexus S, Nexus One, Evo, and Thunderbolt I have pinned the problem down to the garbage collection mechanisms on the Thunderbolt; both on the native heap and in the dalvik. On each product screen we place a large image of the product on the lower half of the screen. Each time we create this image an allocation is done on the native heap to hold the actual Bitmap bytes while a small reference object is placed on the dalvik. The error that currently causes ShopSavvy to crash involves the native heap growing until the operating system can no longer allocate anymore space causing the program to crash from the native side of the application, not the dalvik.
    In order to free memory on the native heap an Android programmer can either ensure that 1. The bitmap reference on the dalvik is garbage collected which will in turn call the native destructor which will delete the buffer on the native heap or 2. Call the recycle() method on the dalvik Bitmap object which will immediately delete the buffer on the native heap. By calling delete on the native buffer the operating system should then mark that buffer space as reusable and the next allocation should be able to take advantage of the space ensuring that the native heap does not need to grow in size. Therefore, to track down the problem I needed to ensure that both methods were used to keep the native heap under control.
    The first round of tests involved ensuring that the Bitmap.recycle() method was called on each product image to ensure that the bitmap should then be immediately recycled. I included a Bitmap.recycle() and a logging statement on activity shutdown methods as well as in the activity finalizer to ensure that the method was called and the bitmap destroyed. On the Thunderbolt calling recycle() on the bitmap never caused an increase in free native heap space. Therefore every time the product screen was visited another 1-2mb would be allocated onto the native heap until the program would get an OOM (Out Of Memory error). If we compare memory consumption of the Evo with the Thunderbolt; after viewing 6 product screens, the native memory usage on the Thunderbolt would grow from 6Mb to 24Mb, where the Evo would grow from 9.9Mb to 14Mb (where it stayed).
    The next round of tests determined the activity of the Dalvik garbage collection mechanisms. I went through the code and put printouts in the finalize methods of our product screen objects. This ensures that I get a message every time the dalvik deleted one of these objects from memory. I also wrapped our BitmapDrawables to ensure that the finalize method was being called on them as well. On the Nexus S, Nexus One, and Evo the garbage collector would kick in fairly quickly; after about 4 product screen views. I received messages that the activities, tasks, drawables, and tasks associated with the product screen were all purged from memory. This was also confirmed by my native heap gaining free space and not growing in overall size. The thunderbolt however never called the finalize methods on anything other than Tasks. This means that every activity was still being kept in memory along with WebViews and BitmapDrawables. Even though the references to all objects were deleted on the activity shutdown methods; the objects were never cleared from memory causing large memory usage.
    I’m unable to recommend any fixes at this time. All Android best practices are being exercised in our app. We have concluded that all references are being deleted and all bitmaps have been recycled either by manually calling recycle or through the Bitmap object being finalized.



Search tags for this page
all my android apps keep crashing
,
android app keeps crashing
,

android apps keep crashing

,
android games keep crashing
,
app keeps crashing android
,
apps keep crashing android
,
droid apps keep crashing
,

how to stop apps from crashing on android

,
how to stop games from crashing on android
,
my android apps keep crashing
,
my apps keep crashing android
,

why do my android apps keep crashing

,

why do my apps keep crashing android

,
why do my apps keep crashing on my android
,
why does my angry birds keep crashing