A behavour as described above in most cases indicates something's messed up in the system. The most likely candidates here are:
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 ...
I had the same problem where settings would keep on crashing. I just got the snapshot today and it did the same thing. After experimenting I fixed it by going in the app drawer and holding on setting, opening its app info, and clearing data. It now opens and works well. I hope this helps.
You can't (without customizing the code). The relevant code is in the Activity Manager (see crashApplication() and handleAppCrashLocked()) and it only suppresses these crash messages in 2 cases:
The app crashed too soon since the last crash
The app has crashed too many times total
I rebooted into TWRP and edited /data/system/packages.xml. Under <package name="com.google.android.apps.nexuslauncher" and <perms>, I added the following lines:
<item name="android.permission.STATUS_BAR" granted="true" flags="0" />
<item name="android.permission.MANAGE_ACTIVITY_STACKS" granted="true" flags="0" />
When I rebooted back ...
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 ...
This is a partial answer based on the output of logs provided.
Okay, after looking at the logcat, my guess would be a buffer overrun error originating/stemming from mm-camera and connected services/processes and ion memory allocation.
08-11 17:51:19.504 E/libaprpmem( 1539): Ion allocation success virtaddr : ret=2996989952 fd=48 heapid=33554432
Tom Scott did an interesting video on the subject
Fundamentally, the fact that it is triggered by touching the text probably means it's a bug in the code responsible for working out which part of the text is highlighted (which is not at all trivial in unicode) so it can be copy/pasted or otherwise manipulated. Given it hangs it possible there is an ...
As pointed out by my other answer, and confirmed by the OP for the given device with reference to a blog article on the Z1, most devices with non-removable batteries have other means to "disconnect from power", usually "reset buttons" or "reset holes" to be poked with a pen or similar object. This should remedy in situations where the device freezes in a way ...
If nothing can be retrieved from logcat you are probably running into a kernel panic.
You could check via adb the output of: dmesg
Some devices also have a kernel feature where, on critical errors, the last received kernel message can be read from /proc/last_kmsg
Maybe this will give you some hints whats going wrong.
If not you could stream the full ...
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 ...
You are not alone. Inability to uninstall any apps and crashes in Settings, are some of the nasty bugs in Sony's recent Google Play edition devices. Currently there are no workarounds, and you must wait until Sony releases an update with fixes for these issues.
Sources: Android Authority, Android Community
Allegedly, the upcoming 4.4.2 OTA update ...
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 ...
My HTC One V was getting so slow that I was getting ready to smash it. After trying everything with nothing working, I went through my apps and deleted a few. Apparently the one causing all the trouble was You Don't Know Jack. The second it was off my phone my speed dramatically increased and started functioning normally again. Not sure if this will help ...
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 ...
If your device is rooted, and you have a custom recovery installed: Wipe the dalvik cache. Next boot will take a little longer (as the Dalvik cache has to be rebuilt), but the problem should be gone.
If the above is not an option, you could try to backup the affecgted apps and their data using e.g. Helium Backup, then uninstall the apps, and restore them (...
If the device freezes, usually you can long press the power button. Depending on the configuration of the device, it will either turn the device off completely (e.g. Nexus 7, HTC Butterfly S) or make the device do a restart.
You can simply see the crash stack trace after any crash happens.
Use ADB command below,
adb logcat -b crash #default
adb -d logcat -b crash #show from device when multiple device
adb -s logcat -b crash #show from simulator when multiple device
A few things to note:
Answer compiled from comments
A SIGABRT signal/error generally indicates that the system forcefully stopped a process from executing, via the syscall abort(). Refer this SO question.
OpenGL ES libraries not found: It could be that your OEM does not or has not provided the OpenGL ES libraries which this app requires or has provided ...
I had the same problem recently. The phone was constantly reporting Google Play Services and many others as having stopped. A hard-reset left me unable to complete the initial setup, as the account manager kept stopping too. My S3 was stock standard, not rooted or running any custom firmware. I was able to fix the problem, and I'd like to share my ...
How to Speed up Slow Android
Remember the day you bought your android? It wasn't slow. It was so fast. What happened? Did the silicon get slower? Did the bits get clogged? Of course not. You're just running more invisible background services.
First, disable auto updates in
Samsung galaxy store (if applicable),
in settings > software updates,
In secret ...
I wouldn't run the "Addon Apps" like "RAM Manager" or the "Seeder" script. I am not sure if you are using those, but the RAM manager could cause instability because it forces applications to close to "free ram".
The need to free RAM is a myth, if an application kills other apps, to free up some RAM, the OS will find something else to fill that RAM. Android ...
Here's a few tips for troubleshooting:
Go to System Settings > Apps > click Android keyboard (AOSP). Clear Data. Clear Cache.
If that doesn't work, and you have a custom recovery, reboot into recovery and clear the entire cache, clear davlik cache, and go to advanced > Fix permissions.
Other than that, you could try uninstalling and reinstalling from ...
If your screen blinks and/or keyboard freezes, go into
Settings --- > Developer options and make sure the following are checked.
Disable HW Overlays and
Force GPU Rendering
Now it should be blink/flash-freeze-free
The answer to your original question is no. Sometimes, if a device DOES have an easily removable battery, it will not have a hardware reset option.
You could build an Android device that had no other option to reset besides a battery pull. The manufacturer has to specifically build some form of external reset. If the software is completely locked up then ...
There are multiple ways to obtain useful information. But as Dan pointed out, on-device solutions will require root (starting with JellyBean) – and off-device solutions ADB:
adb logcat was already described in Dan's answer. For more details, you can see our logging tag-wiki.
adb bugreport > report.txt gives very detailed information, including details ...
Unfortunately logcat does not survive a hard reboot because the logs are stored in circular buffers in memory, and are never actually written to storage. Your solution to leave a terminal session running may work, but as you said may grow the file uncontrollably, and during a reboot it may corrupt the output file. I would suggest adding the -r and -n ...