I am periodically seeing this message appear in my LogCat. I've cannot find much information on what it means. Can anyone provide an explanation? I've also searched for the tag in my code but cannot find it.
My application contains a WebView that displays a catalogue of images but does not scroll smoothly. (It does in the Chrome app). I have tried various different combinations of hardware acceleration and cache modes. I have settled on: WebSettings.LOAD_CACHE_ELSE_NETWORK and the default Application level acceleration, but this is far from perfect performance at the moment. The error seems to sometimes appear when the WebView sticks but I don't know if that is the cause.
Related
I found scrolling performance on Chrome Android is so terrible. If you slide down the page with your finger not leaving the screen to perform a scroll action you'll notice obvious stutters/jitters (even if no dom has changed). Removing all relevant event listeners doesn't make a difference. So I tried to capture a performance record to figure out the problem but found nothing useful.
You can see in the following screenshot, "Others" cost so much time. I've googled for a long time to find what does that "Others" mean in the Summary tab but failed to find any information about it. Those "Others" almost occupied the whole timeline, but I don't know if it's related to those stutters. I tried to open the same webpage in an app's webview (don't know which Chrome version it uses) and did not find any stutters.
Example screenshot
Chrome Version: 61(stable)/64(dev and Canary)
Android Version: 8.0
Device: Google Pixel
Is there an events or way to find out a screen device's power failure.
I need to flag on a remote device if all the parts are working.
I found ways for most off the elements but for the screen I could only find events that tells if screen is on sleep or active but nothings to detect if a screen is powerless or broken. Could not find any code sample to workaround. As a beginner I do not know how to resolve. Anny hints would be welcome.
I haven't started coding this up yet. This is more investigative than anything at this point.
Although I have never tried to detect an error with the screen, it doesn't look like there is much on this. If the screen is broken, the low-level device driver plumbing may not even give you any information or incorrect information. You might check out
DisplayManager as it contains a DisplayListener which may notify you when a display such as the main device display is disconnected but it sounds like it is more for external displays you are connecting to the device. Closest I could find.
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
Ive been reading into App optimisation and have come across the GPU overdraw functionality embedded in the Developer menu in Android.
There are some great articles here that I have read
http://cyrilmottier.com/2013/01/23/android-app-launching-made-gorgeous/
http://www.curious-creature.com/docs/android-performance-case-study-1.html
The issue here is within my Ionic App it does not show any overdraw. I am interested to see if I can make any optimisations or changes to my App and see how it performs.
Does anyone have any information on whether you can get overdraw to show, or if there is even a point in doing so?
When I open my activity the screen is just blank...then I see the above error in the log:
01-28 15:19:03.000: D/TiledPage(3366): ERROR: We don't have enough tiles for this page! nbTilesHeight 427575 nbTilesWidth 786344
I am lost as to where I need to go from here. The application has worked fine in the past, now it is just showing a blank screen.
The layout for the activity being displayed is the actionbar and a webview filling the remaining space. Not even the actionbar is appearing, so, I don't think it has to do with the webview specifically.
Any help would be greatly appreciated!
Update:
When I force close the app, and open it again, it works. Obviously, I don't want this to happen when a user is using the application, so, what can I do to prevent it in the future? It would help to know how to find the actual cause.
Do you have hardware acceleration turned on?
You can try turning it off by setting View.setLayerType(View.LAYER_TYPE_SOFTWARE, null);.
This turns off the hardware acceleration just for the view. You can also turn it globally.
Check here for more information on Hardware Acceleration.