So, this is an odd one.
I have implemented a custom ScrollView that allows drag and sort operation on a list of items by intercepting touch events. This works well enough on three out of four devices that I have tested on.
On Dell 7 tablet running 4.4.2, the behavior is really strange. The movement while dragging is rough. And in the middle of a drag, the Google Keyboard crashes. This happens irrespective of whether the keyboard is currently open or not. And no exceptions are present in my logs. The app continues to function as before - perhaps a bit more smoother - this happens once after the activity starts - on the first drag operation. After this, the keyboard and the drag-sort work as expected.
There were a few mentions of spell-checker events (not sure if they were indicative of an exception) in the System and event log included in the crash report. These spell-checker log statements were output right before the keyboard crash. So, I checked whether the spell check was turned on. The three devices on which the app functioned fine had the spell-check off. Only the Dell tablet had the spell-check on.
Next, I turned off the spell-check on Dell tab and the keyboard crashes stopped. This is very unusual, and I can't wrap my head around it.
Has someone experienced this behavior? If there exists a bug report detailing the issue, it'll be great if someone could point to it.
Thank you for reading. I did not include any code because I don't know what the relevant part(s) would be.
Related
Since upgrading to Nougat, there are some situations when my app's UI is completely unresponsive to touches on my Nexus 5x even though all views are drawn and contain the correct contents; only the Back or Home key are effective to dismiss it. There have been a few rare occasions where it does work on my 5x, and there is also no problem with it working on an emulated 5x, which of course has no other 3rd-party apps installed, etc.
Since this app has worked flawlessly in this respect since its original release on Android 2.3, obviously something has changed. What I suspect is some sort of race condition during initialization, but I don't know where to start to figure out what is happening.
What is it that could be disabled so as to make the app's UI visible but unresponsive? Is there a place that I could insert a break or logging statement, or just look at settings to figure out what's happening?
First off, this has never happened before on any other android device I've used (multiple devices have been tried and tested before this).
Now I have an app that I have worked on for a little over a year now, it is called AutomatedId (on the app store) and it has worked quite well for my company for quite some time.
Recently I have been given a device to add compatibility to the app (specifically for reading UHF tags) but that isn't the problem.
The problem comes whenever you open the app, the screen stops reading inputs completely, as well as buttons cease to function. I turned on developer options to see the screen inputs and as i suspected, it completely stops and does not read any of the inputs after the app is opened. Clicks don't work, buttons don't work, keyboard doesn't open, hardware buttons on the device stop working. It's a mess, does anyone know what could have caused this?
This is a S98 from here: http://www.wepoy.com/product_view_18.html
moved my comment to the answer as you said. This may be due to memory leak. Here are some references that may help you fix them: Fixing-Memory-Leaks-in-Android-Studio & use this library from square to detect memory leaks early: leakcanary
We have an Android App which needs to run all day, the issue is that sometimes after several days it freezes where the buttons cannot be clicked. We are able to see our Apps UI but none of the buttons are clickable.
At First i thought the whole OS was frozen but I was able to click on the Back and Home native Android buttons. This is telling me that something is freezing within the App but not the OS itself. There is also NO message of App not responding when I click on it, its just completely frozen.
There are some devices connected via OTG USB hub like credit card reader, scale and printer in case that helps.
I dont know where to begin to look, and whats strange its sometimes hard to replicate, sometimes it works after 24-48 hours and sometimes it doesnt. But it has happened a few times already after a weekend of no interaction.
Could a Button click listener just stop responding for some reason based on duration? is there something in the code I have to do to keep a button listener awake for over 24 hours?
Any suggestions would be great
Thank you
I used Eclipse before and I could easily stop logcat from scrolling, but I can't find same funcionality in Android studio. Anyone knows how to do it?
There's no dedicated button for this, but you can just click on / highlight some text around where you want to stop scrolling.
android studio have this feature
you just click on the line three times and you can selectd the line , it will stops scrolling.
I had the same issue. Simple solution:
In Android monitor, on the right, change No Filters -> Show only selected application.
Android Studio Stop scrolling log
Disable Scroll to the end
If not - you are able to scroll to necessary line manually and LogCat will not be automatically scroll to down
I actually just had a problem (in 1.2.2) where I couldn't keep it from scrolling. I tried all the tricks and proper methods mentioned here, but it kept scrolling out from under me.
Turns out there was a problem trying to connect to an emulator that had long since been disconnected, and it kept retrying. And every time it did, it reloaded everything causing logcat to refresh. So it wasn't REALLY scrolling, it just felt like it was because of how big the buffer is.
I unplugged my physical device (that was running along side the emulator), restarted Android Studio, plugged the physical device back in, and boom, it no longer kept "scrolling".
Hopefully this might help someone else. Because I was getting incredibly frustrated for a while, there.
Goodness, the trick is to search. Search for something within LogCat and then scrolling will stop. Tested: running Android Studio 1.1.0 against a real device (S5). Also, was ticking one line up and one back down until I then right clicked. Then it totally stopped. After that, I can remove the search and the scrolling is no longer automatic.
We’re porting to Android some interactive iOS apps used to teach young children with learning disabilities. We have hit a major usability issue, because we can't figure out how to disable physical or on-screen navigation buttons (Home and Recent Apps).
Before anyone says “you don’t want to do that”, we fully understand why you would always want these buttons enabled for an able-bodied adult, but these children pose a unique set of accessibility issues. Specifically:
Their fine motor control may be poor - they may inadvertently touch a different area of the screen to the area they intend, or accidentally use more than one finger at once.
They may have weak muscle tone and poor physical strength – so e.g. the bottom of the palm of their hand may drop and touch the screen while trying to just use a finger.
They struggle to achieve and easily become disheartened or disruptive if they fail.
For instance, a typical 5 year old child with Down syndrome will accidentally drop out of the app they are using as a result of inadvertently touching the Home button: when this happens repeatedly, and the adult teacher or parent has to go back into the app for them repeatedly, the child loses interest and focus. Another typical scenario is a young child with Autism, who may freak out completely and need physically restraining if this happens while using their favourite app. Also, many disabled children will try to poke any other button they can find, in search of a response. In any of these situations, a potentially valuable educational session may have to be completely abandoned.
We're aware of SYSTEM_UI_FLAG_HIDE_NAVIGATION and SYSTEM_UI_FLAG_LOW_PROFILE, but these only reduce the visibility of the on-screen buttons until the child touches some other part of the screen, and then they re-appear in a way that’s more distracting than if they were visible all the time.
On iOS there is the “Guided Access” feature that solves this problem trivially. Can we emulate anything similar on Android?
On iOS there is the “Guided Access” feature that solves this problem trivially.
Guided access appears to be a device setting, not something that developers enable unilaterally themselves, thank heavens.
Can we emulate anything similar on Android?
There is no similar device setting in stock Android.
You can download the Android source code, modify it as you see fit, build the results into a ROM mod, and install that ROM mod on devices as you see fit.
Or, you can perhaps work with a device manufacturer creating tablets aimed at children to see if either they have already added this capability to their devices, or would be willing to work with you to add such a capability in a future iteration of their devices.