im currently building a digital signage app, which is running on displays which are based on android 7.*. Everything is working perfectly, except a weird OS behavior:
After a while (6-9h) of running the app, android minimizes my application, i don't get any error logs nor do i get a exception thrown.
My workaround solution is that im reopening the app every 2 hours, this is working fine, but its not what it should be.
I already tried it with WakeLock, Keep alive, Kiosk Mode, nothing seems to be working.
Does anyone have a idea how i could solve this android behavior?
I am getting pretty frustratet. PLS help :)
I made a Java application for a client that needs to be installed in the computer, the app connects to a SQL database in a server. When the app is in use runs normally until at a random moment it starts lagging despite no consult to the database is being done, something as simple as scrolling in the app gets slow and changing from frames gets really slow(maybe a minute or two when normally it takes half a second).
I read that the problem could be the Java version and that could be slowing the application, but after updating Java the app keeps lagging despite randomly and returning to normal randomly as well.
When the app is being used in Netbeans it runs with no problem and the code doesn't seem to be the problem because it works normally and it does what it's supposed to do.
Any idea of why the Java executable lags randomly when in Netbeans runs without problem?
I'm using Android studio 3.4.1 on Windows 10 x64 and I'm constantly getting same error over and over.
I can't run the app, because "MainActivity is not declared in AndroidManifest.json", and all code that uses something that requires permissions (NFC, read/write files, atc.) is marked as error, and the message is claiming that the permission is also missing in manifest.
These errors can be simply solved by Syncing grande files, as stated in this question: The activity 'MainActivity' is not declared in AndroidManifest.xml
However, after few minutes, these errors are back there again!
I've tried restarting the IDE many times, invalidating caches, syncing gradle many times...
But nothing helps. I got these errors, I sync gradle, errors are gone, I run the app, make tiny changes in code (like changing string in setText or changing textview margin), try to run it again, and the error is back. I sync gradle again, error is solved, I run the app, then I leave the IDE, Google something, and when I return to the IDE, the error is again back, even if no changes were made to the code.
I tried to Google this issue, but I was only able to find questions where this happend once.
Obviously there something that makes the Android Studio "forget" manifest every few minutes. The issue started to occur after my computer once lost power and shut down, so my first idea was corrupted files (as it could have happend while Android Studio was saving something), but if I ran the app after grande sync, it works fine, and it lasts few minutes before the errors are there back again.
So, as this issue happening once has been asked many times about, and many times there were different replies, I just started trying other suggestions.
I came acros this reply: https://stackoverflow.com/a/52687462/6357453
which suggests deleting folders with cache and other stuff Android Studio has created. I did and as of now, it's been more than an hour without this error, so this propably solved the issue.
Ok, so I am a standing at the beginning on my relationship to linux and spend the last couple of days to get Eclipse running on my Chromebook using crouton.
Now I ran into this really weird problem:
When ever I start Eclipse everything works fine. I open my new project and Class and want to begin my long journey of finally really learning Java.
Typing works fine but as soon as I hit enter my screen turns black.
I can resolve this issue by switching back to my ChromeOS and back to XFCE again. Pressing enter again however turns my screen black again.
This usually happens 2-3 times. After that it works fine as far as I can tell. Hitting backspace has a similar effect but in reverse. It works fine until i hit a certain point. Typing while the screen is black works fine btw..
What can that be? I'm happy to try and provide pretty much everything you need to help me fix this issue.
UPDATE:
I just found out that when i press the little minus or plus symbol to collapse or expand lines it also goes black. Maybe thats a vital clue?
Eclipse uses SWT which poorly integrates with GTK. Try running eclipse with SWT_GTK3=0 in environment.
I was using Eclipse this morning and it was working fine, both it and the AVD would load in less than a minute... After a few hours it started crashing.
Now if I'm lucky enough for Eclipse to load without crashing the AVD takes at least half an hour to go from the basic "ANDROID" text to the actual logo.
I've tried cleaning my project, recreating the AVD, increasing the AVD's memory from 256mB to 1024, disabling animations and loading from snapshots...
Other than using Eclipse the only thing I have done with my computer is searching on stackoverflow.
What could have caused such a change in performance over a few hours?
Maybe you started a background application or something. Restart your machine. Your memory is probably being barraged somewhere. Check that the processor isn't on battery save mode or anything.
Also, perhaps this post might help.