Becoming undependable

[noodle15]

I love the device but it bas been lately been a not reliable phone. Love the size and capabilites, but it has rebooted in the middle of important times of use then to try and make a call following it will not at all so then i have to do a battery pull. It has become laggy and slowed down. I maybe jumping back to the blackberry life. Maybe the update will.solve some of these issues.

 

[esn]

I am having the same issues but all smart phones have the same issue IMO. I will wait until the end of the week for the update to see if all gets fixed if not back to a dumb phone and a camera.

 

[un8elievable]

1st question is are u using a task killer? if so delete it. tk's are like a virus. don't believe what you read from die hard tk supporters. android os is intended to run and kill tasks on it's own. that said, i had the same issues until i installed launcherpro. i can't explain the how and why's but man what a difference. plus the personalization available is awesome. just my 2 cents.

 

[theineffablebob]

With 2.1, I had it reboot on me like three times. With the leaked 2.2, so far, no reboots.

 

[dguy]

Rebooting is not normal, don't let anyone tell you it is.

If your phone is rebooting either A.(and by far the most likely) You installed crappy software or B. Your phone is defective. This is not an issue that everyone experiences.

If your phone is being laggy/slow, it is because you have one or more defective/crappy apps on your phone that do not know how to sleep properly so they consume CPU time even when in sleep mode. The phone being slow randomly is not normal.

 

[darreno1]

^^Exactly!! This is not normal at all. I can't remember the last time my phone rebooted. And it has been rock solid even with the leaked 2.2. Also I depend on it a lot during the work day for navigation, calls, emails, texts, research on the web, testing wifi signal levels, etc. It HAS to be reliable and the X gets the job done no problem.

You need to probably take a close look at all the apps / services running and eliminate the ones you added temporarily to trace the problem. If you have a task killer, remove it for the time being like was suggested above. If all else fails, perform a factory reset if you haven't done so already. But constant rebooting is NOT NORMAL. Once in a while an app will misbehave and cause some instability, even a reboot, but that should be rare.

 

[wharpig]

I have yet to have a reboot on my phone. Most likely you installed an app that is causing the reboots...try uninstalling any apps you recently installed, if that fails do a factory reset. This is not a blackberry so reboots are not normal....

 

[noodle15]

Thanks for all your opinions.. I will say this has been the best smart phone thus far I have owned.. I do understand that all smart phones need reboots, its just when I need and stress need the phone to be working the screen goes blank.. I have the original software I try to really never use the TK, I have install some dumb software at times so try to only download the necessary stuff.. Again thanks for your support.

 

[JazzMat]

No reboot issues here, either. Phone has been rock solid. Deleted my task killer yesterday and have noticed no battery-life difference today. Guess I'll leave it off. Also running Launcher Pro. Love it.

 

[Member112085]

Whether you "use" the task killer or not, it could be causing problems. Uninstall it.

 

[matty032]

No issues here either. Best phone I ever had. Try a factory reset.

 

[rjoudrey]

This phone is rock solid with the leaked Froyo. Something is definitely wrong with yours.

 

[protocollie]

1st question is are u using a task killer? if so delete it. tk's are like a virus. don't believe what you read from die hard tk supporters. android os is intended to run and kill tasks on it's own. that said, i had the same issues until i installed launcherpro. i can't explain the how and why's but man what a difference. plus the personalization available is awesome. just my 2 cents.

Okay, so, this is patently untrue. First off, I don't know what your definition of a virus is but it's way different from what everyone else agrees a virus is. Second, android itself CONTAINS task killing facilities in the applications area of the settings menu, it's just so clunky and hard to get to that a task killer app is useful. Three, run and killing tasks are a basic OS function - if android can't handle a request to close an application, it is a POS operating system.

It's definitely perfectly fine to kill tasks on your own. Android does a certain amount of garbage collection and memory maintenance on its own, but it's not perfect, and a runaway task eating up memory and CPU could easily look like an important and active process and never get swept away by the GC.

 

[rjoudrey]

I use ATM and never had any kind of problem.

 

[Steven58]

my first reboot in teh middle of a call was this week, when I was on the phone with VZW.

 

[rjoudrey]

Bring it back

 

[TheXFactor]

Like I posted in another thread I have had zero issues with my X. No freezes, no reboots, no 3G signal issues, nothing. Solid all the way, so far. I am stock, no roque apps installed. It's been great. Not that it helps you guys with problems, but it shows that it's not normal what you are experiencing.

 

[graff_king]

FAQ: Why You Shouldn’t Be Using a Task Killer with Android
a very good breakdown of task killer apps usefull/less ness

 

[dguy]

Okay, so, this is patently untrue. First off, I don't know what your definition of a virus is but it's way different from what everyone else agrees a virus is. Second, android itself CONTAINS task killing facilities in the applications area of the settings menu, it's just so clunky and hard to get to that a task killer app is useful. Three, run and killing tasks are a basic OS function - if android can't handle a request to close an application, it is a POS operating system.

It's definitely perfectly fine to kill tasks on your own. Android does a certain amount of garbage collection and memory maintenance on its own, but it's not perfect, and a runaway task eating up memory and CPU could easily look like an important and active process and never get swept away by the GC.

I really should copy and paste this so that I don't have to retype it every time I come across someone who doesn't have a full grasp of Android's process system but talks like they do because I've posted something like this at least twenty times.

The first rule to understand is that empty RAM is wasted RAM. There is no advantage what so ever to having a ton of free RAM. Android keeps things in RAM even after you "close" them so that they can be opened extremely quickly next time the user decides to run them(Windows 7 does the same thing). Something sitting in RAM doesn't consume any battery or use any CPU. Any time a foreground application needs more RAM than is available, Android will close the least used application to free up space for it. It takes far less CPU and battery to open an application that is already in RAM than one that is not.

A task killer manually shuts down applications. The main reason this is a problem(but not the only reason) is because most task killers allow the user to shut down critical processes, which leads to reboots or crashes down the line when some app you are running expects a service to be there and it isn't.

Android will continuously attempt to keep RAM use at a reasonable level. This is where the second problem of using a task killer comes from. It means that if a task killer keeps automatically killing tasks for no reason, Android will keep opening up those applications. This is exactly why virtually everyone who complains the most about Android battery life happens to have a task killer.

Now I will explain the anomaly that is why some users experience better battery life when they use a task killer. Users will occasionally encounter buggy/glitchy software(and they might not know it) that has a defective sleep/idle mode. An app's sleep mode is broken if it consumes any CPU at all while in sleep mode. This, and only this, is the reason why anyone who has ever used a task killer that has experienced better battery life experienced better battery life; because they have a defective app they don't know about and the task killer takes care of it. My suggestion for these people is to stop using the task killer and find out which app or apps have the broken sleep mode. System panel lite allows you to see how much CPU an app is consuming.

Quick tip: If a user is finished with an application and doesn't plan to go back to it, this is how they should attempt to exit the application: First try to exit using in app exit menus or buttons. If an app does not have an exit button, exit the app by hitting the back button. These two are the only way to make an app either close or go into sleep mode. If the only way to exit an app is via the home button(some apps don't allow you to exit via back) then it's a crappy app that should be installed because it will remain in fully awake background mode if you exit it with the home key, which consumes battery.

 

[rembrandtqeinstein]

I have had two BBs and both had lockup issues.

My Droid X has also locked up and rebooted. It got better when I got rid of my task killer. It got much better when I went to Android OS v2.2.

There are some Android Apps that I can't run on my DroidX or they will cause crashes/freezes/reboots. I just avoid those. I have a lot of useful and stable apps, so I am very happy with my Droid X

 

[colchiro]

That's the problem with Android, lots of apps, but easy to install buggy ones, then not sure why it's unstable.

I had my first hard lockup after exiting "angry birds" (beta). Finally had to pull the battery. No amount of button pressing would get rid of the screen.

 

[CrashF16]

As an owner of a defective phone that suffered from constant reboots, let me tell you that it is not normal. I now have a new phone with the exact same apps loaded, and it works perfectly. Those people that say it's ATK or the Weather Channel app have probably not had a phone that rebooted constantly...even from the activation screen after a factory reset.

I have only one remaining theory that I didn't get to try with my defective phone before I replaced it. I would have done a factory reset AND reformatted the SD card. When I was cleaning up the old phone, it stopped rebooting after I took most of the music, photos, movies, etc files off the SD card. ...Just wondering if that's somehow related. It would have been worth a try.