ATTENTION: 2.1 Known Issue

Discussion in 'Android General Discussions' started by cereal killer, Jan 19, 2010.

  1. cereal killer

    cereal killer Administrator
    Staff Member

    Joined:
    Oct 29, 2009
    Messages:
    11,397
    Likes Received:
    1,280
    Trophy Points:
    558
    Location:
    Austin, TX
    Ratings:
    +1,427
    Current Phone Model:
    Nokia Lumia Icon
    This post is ONLY a heads up and is in no way saying what is coming our way. Since the N1 is the only device running 2.1 this issue may be resolved when it's released to us.

    Seems the workaround is to run a Home Replacement App......

    Nonetheless it's always good to be prepared so there are no surprise. I for one am certainly in no hurry to get 2.1. I DO NOT want to deal with bugs especially since 2.0.1 has been working flawless. Let them clear this issue then push it to us.

    Link to OP if you want to read entire thread:

    [ANSWERED] Launcher Force Close - xda-developers

    --------------------------------------------------------------------------------


    EDIT: A member of the Android development team has confirmed that this is a known issue and will be fixed in a future release of Android. I suspect that once the source code is released that the wonderful developers at XDA will fix it first. Here's the quote:

    Quote:
    Long pressing a widget just triggers an out of memory error. A solution (unfortunately) is to uninstall a few apps. It's a known issue that will be fixed in a future version of Android.
    While I'm not happy about this, and many are simply using alternative home screen apps, I'm thrilled to finally have official confirmation that this is a known issue and will eventually be fixed. Thanks to everyone who sent me their list of apps. It turns out not to be one specific app as I've always suspected.

    EDIT 2: After much thought, and after not being able to install all my apps on the phone for which I paid $575 is a bit unacceptable. If Google is aware of that this is an issue then an update should be pushed out immediately. It is unacceptable to tell users (not actual tell them because I had to post an issue in a place I'm sure 99.9% of users will never find) to "uninstall a few apps." Seriously? That's the answer? Imagine Apple told users to "uninstall a few apps." I wonder what hard working developers think of that answer. Actually, since I am one, I can tell you. It sucks. It's not like I have that much space in the first place. Simply ridiculous.


    ---- Original Post ----

    Hey All,

    With no Nexus One Q&A section yet, I figure this is the best place to post this since I didn't want to post in the dev section. I am getting a force close on my launcher when I long press a widget. It doesn't happen every time. It usually happens after I wake up the phone. I can replicate on command by repeatedly long-pressing a widget. While it happens on built-in widgets, I can more easily replicate it on third-party widgets (or while third-party widgets are loaded) such as Pure Calendar and Android Agenda Widget. The logcat is below.
     
  2. Nedaroth

    Nedaroth Member

    Joined:
    Nov 25, 2009
    Messages:
    471
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    Long Beach, Ca
    Ratings:
    +2
    wow that will raise some eye brows if we get fixed version:icon_eek:
     
  3. iPirate

    iPirate Active Member

    Joined:
    Dec 26, 2009
    Messages:
    1,436
    Likes Received:
    0
    Trophy Points:
    36
    Ratings:
    +0
    That is a pretty big problem. Once you drop a widget on your screen, you wouldn't be able to remove it, correct?
     
  4. SinCitySRT4

    SinCitySRT4 Member

    Joined:
    Jan 19, 2010
    Messages:
    298
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    if thats the case i can wait longer for 2.1 to come out so all the kinks can be ironed out
     
  5. droiddoes1912

    droiddoes1912 New Member

    Joined:
    Jan 10, 2010
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    It's not a problem on the SDK, so hopefully it shouldn't be a problem to fix, if it is even there for the Droid 2.1. Here is hoping it isn't.
     
  6. vzwmandroid

    vzwmandroid Member

    Joined:
    Dec 2, 2009
    Messages:
    243
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Homestead, FL 33030
    Ratings:
    +0
    im in no rush either im! ok with android 2.0.1 for now:icon_ banana:
     
  7. TxDoc

    TxDoc Active Member

    Joined:
    Nov 12, 2009
    Messages:
    437
    Likes Received:
    62
    Trophy Points:
    28
    Location:
    TEXAS
    Ratings:
    +63
    Current Phone Model:
    XT1635-01
    A true example of "Be Careful What You Wish For" (or demand). :icon_eek:
     
  8. SinCitySRT4

    SinCitySRT4 Member

    Joined:
    Jan 19, 2010
    Messages:
    298
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    exactly and plus ive only had the phone for a week so 2.0.1 is still new to me:)
     
  9. bossrogue

    bossrogue Member

    Joined:
    Jan 12, 2010
    Messages:
    111
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    St. Louis, MO
    Ratings:
    +0
    I agree to the others who have said they are in no hurry to get 2.1 either. I'd rather them work out the kinks first than to have problems immediately upon getting 2.1
     
  10. KZIWarrior

    KZIWarrior Silver Member

    Joined:
    Dec 31, 2009
    Messages:
    2,609
    Likes Received:
    2
    Trophy Points:
    103
    Location:
    Nashville, TN
    Ratings:
    +2
    FINALLY, someone else with this thinking. I've been amazed at how many people seemingly can't wait to get the update. I have no problem with waiting if it will fix known issues (and help flush others out).

    Note: I know it's likely because it is a port and not meant for 2.0.1 but running the 2.1 Launcher I've had the phone freeze several times just trying to launch the app screen (and twice it has led to an automatic reboot). Unless there are a LOT of changes in the underlying structure of the 2.1 OTA I could see things like this being an issue. PLEASE let Moto and VZW take their time and get 2.1 right before they push it...
     
  11. mjs31

    mjs31 Member

    Joined:
    Oct 30, 2009
    Messages:
    870
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    NE Texas
    Ratings:
    +0
    I really had no plans of getting rid of my GDE cube anyway :icon_ banana:
     
  12. Martin030908

    Martin030908 Super Moderator

    Joined:
    Nov 1, 2009
    Messages:
    8,773
    Likes Received:
    0
    Trophy Points:
    151
    Ratings:
    +0
    Thanks for the heads up Cereal.