ATTENTION: 2.1 Known Issue

[cereal killer]

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.

 

[Nedaroth]

wow that will raise some eye brows if we get fixed version:icon_eek:

 

[iPirate]

That is a pretty big problem. Once you drop a widget on your screen, you wouldn't be able to remove it, correct?

 

[SinCitySRT4]

if thats the case i can wait longer for 2.1 to come out so all the kinks can be ironed out

 

[droiddoes1912]

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.

 

[vzwmandroid]

im in no rush either im! ok with android 2.0.1 for now:icon_ banana:

 

[TxDoc]

A true example of "Be Careful What You Wish For" (or demand). :icon_eek:

 

[SinCitySRT4]

exactly and plus ive only had the phone for a week so 2.0.1 is still new to me

 

[bossrogue]

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

 

[KZIWarrior]

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.

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

 

[mjs31]

I really had no plans of getting rid of my GDE cube anyway :icon_ banana:

 

[Martin030908]

Thanks for the heads up Cereal.

 

[brendanstl]

I really had no plans of getting rid of my GDE cube anyway :icon_ banana:

I'm happy with a rooted 2.0.1 droid running GDE with the 2.1 gallery, news and weather widget and music player. Haven't had a problem with it yet. Hope they take their time getting it right but I wish they would hurry the hell up with the 10.1 Flash.

 

[mike_kauble]

FWIW. . .I'm running 2.1 and have been for about a month. The only "bug" I've experienced is that the phone actually unlocks when the slider is opened. Other than that, it's worked flawlessly.

Oh. I guess I should mention that the PROzoom app seems to FC and continually cycle an FC.

But other than that, I love it!!!!!

 

[pc747]

WOW if I was one of the people who paid 575 plus tax for a nexus 1...I WOULD BE PISSED.......Not to throw salt, but I wonder how many of them dropped the droid to get the next best thing.
I hope they get that fixed, no body want to pay good money for a device that has flaws.
Looks like verizon holding off on the nexus until spring is now a wise decision.