Hot answers tagged

9

As others said, there are ~2000 zero-width or 'invisible' unicode characters in that message. These characters are the ones which instruct the text renderer whether to display the text left-to-right or right-to-left. When you tap on the message, the text renderer tries to work out which character you are tapping on. As there are a lot of characters with ...


8

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.


7

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


7

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 copied/pasted or otherwise manipulated. Given it hangs, it is possible there is an ...


7

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


6

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. Snippets, 08-11 17:51:19.504 E/libaprpmem( 1539): Ion allocation success virtaddr : ret=2996989952 fd=48 heapid=33554432 ...


5

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


5

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


4

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 [Edit] Allegedly, the upcoming 4.4.2 OTA update ...


4

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


3

Go to Settings » Developer options, and deselect "Use NuPlayer". Reboot the phone, and your camera should work again.


3

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.


3

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


3

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


3

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


2

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


2

I found a fix that worked for me. Remove the SD card, then whilst it's out, choose to clear the SD card contents,(mine allowed this). Replace the SD card and all fine, quick n easy.


2

The process error you are getting is android.process.media The clue is in the media part. You should go to Settings > Applications > Manage Applications > Then make sure you look under the ALL tab. It is MEDIA what you are looking for. Clear the data and cache for this one. Then Force-stop it and restart your device. When it restarts, it should restart ...


2

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


2

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


2

Your SMS app is crashing because of an software bug, which is causing an uncaught NullPointerException resulting in a termination of the davlik VM and it's process.


2

Neither of those will help you. The log in Android isn't written to disk: it's stored in a ring buffer in memory, and is lost when the device reboots.


2

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


2

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


2

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


2

Unfortunately, it's quite not possible. Tasker cannot detect an app crash. However, we can still do something about it. Let's first make a profile that does the killing job. It will be executed when the bluetooth goes off. Profile (name): BTrern State (Context): BlueTooth Status [ Status:Off ] (Profile triggers when BT goes off) Task: ...


2

Had the same issue. Solced by connecting to external power supply. Did some searching and apparently, thus cyclic crashing can be due to a bad battery...


2

The wiki mentions that in order to use capps you need Cyanogenmod 12.1, what doesn't mention is that is not compatible with Cyanogenmod 13. The wiki also comes with uninstall instructions. (You don't need to wipe and flash add I thought first). Uninstall Note: Requires Root You will need to enter the following commands to remove C-Apps. Connect your ...


2

I just found the cause of the problem : It was due to the Android System Webview which was bugging and then couldn't display web UI on several applications. I just had an update of it and now everything works fine ! One of the update's patch notes (translated from French, it may not be perfect) : Resolved crashes in applications using WebView in an ...


2

I was having the same problem every time I oppended the app it crashed and I found that if i oppened it with wifi off it worked just fine so it had something to be with the automatic back up, I went to settings and allowed Backups trough cellular data and It started backing up just fine, then I turned off that option, went back to Wifi and all worked just ...


Only top voted, non community-wiki answers of a minimum length are eligible