Hot answers tagged crashes
5
Uhhhh, that is not a virus! Who told you that? :)
kworker is part of the Linux Kernel's scheduler in which it manages the processes running and switching to it a la multitasking.
That is normal behaviour of the kernel! It exists on the desktop linux also, see this example to illustrate:
ps -elf | grep kworker
1 S root 5 2 0 60 -20 - 0 ...
5
A behavour as described above in most cases indicates something's messed up in the system. The most likely candidates here are:
Application Cache
Dalvik Cache
As you might have guessed already, different solutions are available for rooted devices -- but only few for non-rooted devices, which cannot directly access the Dalvik Cache. So read on below ...
4
I encountered exactly the same problem as yours on my Galaxy S2 with CM9 earlier this week.
I figured out it might be the problem that the internal USB storage had some error on it.
Unfortunately, formate Dalvik Cache and Cache won't fix the problem.
You can try to mount your phone onto your computer and try to fix the error using some disk check ...
3
If you as a user experience such crashes, and want to help the developer to get them fixed, you can use tools such as aLogcat (free) - logcat or Bug Reporter to catch a log of what happened:
While aLogCat allows you to restrict the log closer to the crash event (by letting you define what to capture), Bug Reporter enables you to send other useful ...
3
It's probably too late to help the original poster, but I had this exact same problem for the past 24 hours or so on my HTC Incredible with Cyanogenmod 7.1.0. I was consistently getting SQLiteDiskIOException errors every time I tried to start an application, including even the keyboard and crash reporters.
After stopping and uninstalling all sorts of ...
3
If your foreground app is being closed without warning, the suspect is no other than Kernel. It generally happens when Kernel runs out of memory. In such case, Kernel reclaims memory by killing other apps, otherwise the device would be crashed. In such situation, Kernel doesn't respect multitasking (apps with background services, apps having icon in status ...
3
Try installing another launcher. Then press the Home key and it will ask you which launcher to use. Select the "new one". Then try going in to Settings -> Applications -> Manage Applications -> ADW and Clear the data.
You will probably also want to delete the "settings backups" that are stored on the sdcard, if you created them.
Then you should be able to ...
3
Even if it might only cover a part of your question: Don't let you scare by those "virus" marketing bluff. There is no such thing as a virus on Android, and hardly will be.
Sure some companies want to sell you their "anti virus product". But if you take a deeper look at what it really does (apart from the marketing buzzwords), none of them seems to really ...
2
I would indeed verify first that this is not related to some 3rd party app or any other than stock ROM. For this do a complete reset and try again. Also try with a smaller SD card since 16GB might not be supported by your phone (need to check specs for that, I don't know).
You can make a backup to get it back to your personalized settings quick.
If you ...
2
I tried a different approach, seeing the problem was with radio / telephony...
I put in another SIM from a different carrier, and so far I am having no reboots!
What is the difference? My main carrier is a "virtual carrier", a company that rents other company's network to offer their service, usually with more competitive prices.
The SIM I'm using now is ...
2
I had a similar issue and resolved it easily enough by carefully reading the short messages that were regularly popping up on my screen informing me just what apps were causing my phone to "force close." In my case the culprit was the Volume+ app. As soon as I uninstalled Volume+ the phone was right as rain.
2
An app can certainly deliberately reboot the phone, depending on the permissions for the app in question and whether it has root privileges.
An app can also force you phone to reboot if it bombs out and takes Android down with it, particularly apps that interact with phone functionality (volume adjustors, automatic task killers - which are a bad idea in ...
2
That's not entirely true. When your device gets crashed, Press and hold the power button for 10 seconds. The device will be rebooted. It works atleast on my Galaxy S. You should try it, too.
If this method is not working, you shouldn't blame Android for that. This is the way computers work. When Kernel runs out of memory, the device is crashed. Your screen ...
2
Read an article at this location
http://www.anandtech.com/show/4502/tmobile-g2x-review-gingerbread-infused/9
Seems to be a software problem.
Imho root and flash cyanogen or install the ROM after reading in XDA
1
logcat might give you some information but that is cleared when the device reboots.
abd logcat will connect you to the "rolling log".
logcat is not stored in a file, only in a memory stream but you can easily dump it to file.
adb logcat -d -v time > logfile.txt
using the options I listed above will give you a time stamp of when events occur. The -d ...
1
It could be that you have enable something like Google Latitude tracking, which goes via the Maps app on your phone. Maybe have a look at the settings in your Maps app to see if there is nothing enabled that works in the background, and prevents the application from stopping.
Maybe you have used the application some time before that error? Because Android ...
1
Mainly due to hardware differences.
You can use a logcat viewer on Android 2.3 or below to view the logcat from all apps - this will provide the log from the apps which will tell your the exception.
Please be aware that in Jellybean or ICS google stopped apps from reading the logcat from other apps on the device - you can still use adb to see the entire ...
1
It sounds like something has corrupted within your phone.
You didn't say if you forced a factory reset - that would be my first suggestion.
Failing that, you're left in a tricky situation. The only think I can suggest is to root your device and install a new ROM over top, I tend to advise people to install Cyanogenmod. Luckily there are complete ...
1
System Tuner looks like it could help you figure out what's going on. Excerpts from the app's description:
Display log(cat) for all/one process (even on JellyBean Android 4.1)
Record (optionally at boot) activities in the background
Record all apps or all processes
Allows analyzing past recordings without limits
I didn't try it for ...
1
Search the logcats for stack traceback. Try uninstalling apps one at a time, to see if the problem disappears when you uninstalled a certain app.
If the issue come from an installed application, then you should uninstall that app and/or contact the developer to fix the crash.
If the issue is system level, then there is not much you can do. You can either ...
1
It seems you are accidently triggering the generation of a bug reports, as described on this google support site (click on the nexus link):
Generate a bug report immediately:
Press Volume (in between Up and Down) and Power at the same time (after a >significant delay -- up to a minute -- the device will vibrate if successful and open a new message in ...
1
It is possible that the problem is in your battery more precisely in battery controller.
There are a few possible solutions:
Try recalibrating your battery.
Try removing /data/system/batterystats.bin.
Put somebody's battery inside (if you know somebody with the same model) and look how phone works. If it works fine with somebody's battery then just buy ...
1
In such cases I would highly suggest to try to replicate the problem while usb debugging is enabled. Install the android sdk which will give you the necessary tools to "logcat" what's happening. The messages might give you a clue what is causing the sudden shutdown of your application.
After having installed the sdk you can simply start the logging through ...
1
If you suspect an app or service is causing the freeze, and if your phone is rooted, install Bloat Freezer and then freeze background apps and services in groups to try and isolate the problem.
A good list of apps that can be safely frozen can be found here. Some of them are:
All share
Analog clock
Android live wallpapers
Ap Mobile
Bookstore
There are ...
1
Sorry to hear your hassles however it is actually good news that your phone works well without the problem sd card. Since your phone runs like crap and reboots you may be forced to use a computer sd card reader to salvage what you can.
I hope someone can make sense of those log files, otherwise maybe mounting your sd card on a desktop pc and running ...
1
Yes, an application can lead to a phone reboot, usually by combining a badly designed application and a bug in the framework. Exemple: an application that registers an Account but no ContentHandler issue 5009
1
It sounds to me it could a hardware issue and not a software issue.
Things I would try
Flashing even more ROMs. Try CM7 if it is available for Droid 3. If it keeps rebooting with other ROMs, you most likely have a hardware problem
Hardware suggestions: try a new/different battery. Also, since you are using GSM and it deals with losing your signal, ...
1
I have this happen from time to time. My issue is usually just about any application, not just "non-stock".
To fix it I have to reboot in to the recovery and clear the cache. I believe that it has to do with the number of applications that I have installed, ~105 total, and the amount of data they store in the cache.
Clearing the cache usually fixes it, ...
1
You might need to reset the battery stats anyways. Drain the phone entirely -- when it shuts off, turn it on again until it shuts off again and repeat until it won't turn on. Then wipe the stats and charge to 100% with the phone off (leave it plugged in for an hour or so after it appears to be fully charged). Turn it on, drain it again, and charge to 100% ...
1
I would suggest to start your phone in recovery mode (download and install quickboot from market).
If your phone restart in recovery mode you just need to find the last version of cyanogen working on your phone, install it and live happily.
If you don't feel like it just do a wipe all from your recovery menu (that's a complete "format" of your phone) and ...
Only top voted, non community-wiki answers of a minimum length are eligible
