Hi, everyone!
I'm using a Huawei P30 and recently got a sprinkler controller as a present. Later I found articles and reviews that said this device is compatible with Alexa, Apple HomeKit, iOS, Android, etc. So I downloaded this Rachio app. For some reason, this app and some others stopped responding. I tried to restart my phone and reinstall these apps, but it doesn't help. Maybe someone had the same or similar problem and already found a solution?
Thanks in advance!
NoraHensl said:
Hi, everyone!
I'm using a Huawei P30 and recently got a sprinkler controller as a present. Later I found articles and reviews that said this device is compatible with Alexa, Apple HomeKit, iOS, Android, etc. So I downloaded this Rachio app. For some reason, this app and some others stopped responding. I tried to restart my phone and reinstall these apps, but it doesn't help. Maybe someone had the same or similar problem and already found a solution?
Thanks in advance!
Click to expand...
Click to collapse
Nora it's possible to get this app running correctly if you had root...
([emoji88]Omni Rom[emoji88])
@NoraHensl
Main reason for an ANR ( read: Application Not Responding ) is device's low RAM and/or GHz.
FYI:
An ANR will occur if you are running a process on the UI thread which takes a long time, usually around 5 seconds. During this time the GUI (Graphical User Interface) will lock up which will result in anything the user presses will not be actioned. After the 5 seconds approx has occurred, if the thread still hasn't recovered then an ANR dialogue box is shown informing the user that the application is not responding and will give the user the choice to either wait, in the hope that the app will eventually recover, or to force close the app.
The easiest way to fix an app that keeps crashing on your Android smartphone is to simply force stop it and open it again. To do this, go to Settings -> Apps and select the app that keeps crashing. Tap on the app's name and then tap on 'Force stop'. Now try opening the app again and see if it works well.
____________________
cookspot.org
Related
Hello guys,
I have registered this account to ask this question, I will try my best to avoid any of the annoying pitfalls of being new.
HANDSET - Samsung GT-i9100
CARRIER - Vodafone UK
OS - Android 2.3.3 using GoLauncher Pro
This morning the notification bar showed 10 updates available, I updated them all, all of them being apps that I recognised. Following the updates I now get a recurring pop-up window asking for my Google account username and password. The window pops up in the middle of the screen with whatever I was looking at before dimmed in the background. It occurs on the lockscreen, homescreen and in any app I open. Pressing cancel just causes it to reappear, only pressing the home button makes it go away fully, however never for more than 30 seconds. I am able to stop it from appearing for a few minutes by clearing the RAM.
I tried entering false information into the form to see what happened - it now prompts me with the options to 'Reinput' or 'Cancle' (actual spelling) and appears just as frequently.
AVG has turned up nothing and Android Assistant doesn't show any strange processes.
I am completely stumped.
Thanks for taking the time to read this and in advance for any input you may be able to offer.
solved by unistalling and reinstalling GoLauncher. No idea what caused it. Cheers.
notoriousTOBP said:
solved by unistalling and reinstalling GoLauncher. No idea what caused it. Cheers.
Click to expand...
Click to collapse
Damn. I uninstalled GoLauncher.
Usually it happens when you try to modify something on your account without stopping the sync before
Sent by my Optimus 2x using Tapatalk
It was an update to GoLauncher EX Notification - they have been having trouble making it work with the Gmail app for some time and thought they had it cracked, however people updating to the new version experienced this problem. Their poor spelling I suppose exacerbated the problem as it made it look like malware. Can't be critical though, must be an absolute nightmare to program something like this and write the UI in a second language.
Today's update reverts the changes and explains (ish) in the update log.
Hey everyone, I'm working on my first Android app and ran into an issue that I haven't been able to solve after hours of searching...
When testing my app in the emulator, it launches perfectly fine the first time. However, if I exit the app using the Back button (which sends it to the Stop state I believe), if I try to reopen the app, it instantly force closes.
The error comes up on the setContentView(R.layout.main); part of the code inside the onCreate. LogCat has a number of errors like "Error inflating" and stuff.
I've only done WP7 development, so Android is all new to me, but according to all the code demos, I'm doing everything right... I can't figure out why it keeps crashing like this! After it force closes, I can launch it like normal again...
I've attached the archive file of my project so you guys could look at the code. There must be something going wrong with it trying to restore from the savedInstanceState, but all the samples I've looked at don't do anything differently! I don't understand what could be going wrong!
Thanks!
Ahh apparently I was asking too much of Android and was getting out of memory errors. Funny thing is it works fine on android 2.2 but if I try it on 4.0 it always crashes and NEVER opens.
Time to rewrite stuff...
Sent from my Galaxy Nexus using XDA
Be aware that, on Android, the second launch is often different from the first.
When you 'exit' after your first launch your activities are all destroyed (if you really exited) but the process remains in memory along with some resources and other objects.
This means that your second launch is not a fresh start like the first. For example, if you didn't clean up your activities properly when they closed after your first launch, that could cause a problem upon second launch.
You can see all of this in DDMS. Note that your process is still around after you exit. You can hit stop on the process to kill it (though Android will re-launch it in some circumstances).
Hi folks,
I have a peculiar problem. I'm using Tasker to kill some apps. One of the apps has a persistent notification icon and it refuses to be killed (even with root). The notification icon is gone for a second but will always come right back. Using pstree I tried to find out if there was a watchdog process keeping the app alive, but I found none. Also it is not hooked to any events according to Autorun manager. A force close under "app management" always works.
What is going on?
This seems like an answer that has been asked before. So off course I have searched. I found similar questions (examples: http://forum.xda-developers.com/showthread.php?t=1854858 http://forum.xda-developers.com/showthread.php?t=2040841 ) but no answers.
Who can help me? I'm really at a dead-end.
what app is it? Some apps (especially system apps) can't be closed, and if does gets killed, OS programs it to restart almost immediately after it's been killed.
Preaper said:
Hi folks,
I have a peculiar problem. I'm using Tasker to kill some apps. One of the apps has a persistent notification icon and it refuses to be killed (even with root). The notification icon is gone for a second but will always come right back. Using pstree I tried to find out if there was a watchdog process keeping the app alive, but I found none. Also it is not hooked to any events according to Autorun manager. A force close under "app management" always works.
What is going on?
This seems like an answer that has been asked before. So off course I have searched. I found similar questions (examples: http://forum.xda-developers.com/showthread.php?t=1854858 http://forum.xda-developers.com/showthread.php?t=2040841 ) but no answers.
Who can help me? I'm really at a dead-end.
Click to expand...
Click to collapse
This is actually Android-by-design. Apps are supposed to be killed from time to time to conserve resources (e.g. memory), and also restarted transparently to the user. This is handled by the ActivityManager. You can view it as Android swappes app's instead of swapping memory. This to improve the real time performance of the device. When someone calls you, you don't want to wait half a minute for the phone to swap out Angry Birds before it can load the Phone app ...
Hence, killing app's will most often only give very short term effect.
Just got the mate 10 pro and Everytime I open a new instance of either Facebook or messenger app the app just closes I tried uninstalling both of them then reinstalling without any luck. Anyone else is facing this issue ?
Ido not know how to solve your issue, but I have a similar issue (I think), so I thought I could try and help pinning it down by describing it here as it is differently triggered: I cannot use google translate's "tap to translate" feature, i.e., automatically opening google translate right after copying some text to clipboard. It actually starts loading, then closes back to the app I was on. But after that, trying to open the google translate app itself, it works. So, it also sounds like "app does not open on first try" maybe? And the reason I posted this is because I do not manually try to open the app the first time, but it should be automatically opened bythe system. So maybe it does not matter how you try to open the apps first time, either manually or called by the system? Idk. Just trying to help pin the source of the problem down.
gamekill said:
Ido not know how to solve your issue, but I have a similar issue (I think), so I thought I could try and help pinning it down by describing it here as it is differently triggered: I cannot use google translate's "tap to translate" feature, i.e., automatically opening google translate right after copying some text to clipboard. It actually starts loading, then closes back to the app I was on. But after that, trying to open the google translate app itself, it works. So, it also sounds like "app does not open on first try" maybe? And the reason I posted this is because I do not manually try to open the app the first time, but it should be automatically opened bythe system. So maybe it does not matter how you try to open the apps first time, either manually or called by the system? Idk. Just trying to help pin the source of the problem down.
Click to expand...
Click to collapse
You think it could have something to do with the optimization of EMUI 8?
Hello,
The device is fairly new, up2date Hardware/Software wise. However, the device seems to be struggling with performance intensive applications like Zattoo Streaming TV app and e.g. Youtube.
On the first open of the app you can feel the laggyness, which leeds to the app beeing closed automatically, by android 11 system I assuem, because the app seems not to be responding, but it's just struggeling with the processing. On the next open usually things go quicker and I'm able to use the app. It is like some cache is beeing created on the first start which is taking too long for the Android system and hence is beeing force closed.
Since this happens to other apps as well and only performance intensive, I believe it is sime kind of Android feature. Usually the Android system shows a message/warning when an app isn't responding, in this case it doesn't. The app just closes. Next start and it's usually working fine, but from time to time it take 3 or even 4 start for the app to work correctly. I have two of those identical boxes and both show the same behaviour.
So, is this behaviour known to somebody and is there a way to increase the timeout threshold (which in my opinion seems to be the problem)? Thanks in adavance.
Lenny
Apparently not :-(