Not sure how helpful this will be for development but this utility is crashing quite often for me. I’ve been home a lot and using it a lot so I’ve really been putting it’s endurance to the test. Often when I open it I get a message saying that it has stopped working. It always starts right back up though.
Can you tell me what you are doing or what steps I need to reproduce this? I use my app every day without issue. More information would be appreciated. Been doing some thinking, does this only occur when resuming the app? If that is the case, can you tell me which tab you are on when this happens. I would like to solve this issue asap.
- Garrett
As far as I can recall it only happens when resuming. I don’t think it’s ever happened while I was using it. The tab is the Devices tab. After a while loading that as default finally took.
I’ll open the app a bunch today and in the coming days just to get a better idea of when it happens.
For the record this is the only app that has crashed on me so far, which is why I found it important enough to mention here.
Very odd. I’ll try and test on my tablet and see what happens. I’ve done the same and set the default to devices. Sounds like it does not like something when resuming. Keep me posted. I would like to track this down. Is everything else working OK within the app?
- Garrett
Have we verified that he is on the latest version?
I should have asked… S-F are you running 1.3.3? I have been going back and forth with the app running on my Transformer (1st gen) and I can not reproduce crashing when the app resumes. Can you go into Android Settings → Applications → Manage Applications → AutHomationHD → Clear Data? This will start from a clean slate and you will need to setup the app settings again. Might clear up any gremlins that could cause the app to crash on resume.
- Garrett
Well I’ve been using this tool every day many times and since I started this thread it has only crashed one time and that was when I “woke up” the Prime and went right to AutHomation.
I don’t know what to say, other than that this is working out quite well for me. If I have issues in the future I’ll be sure to note the circumstances and try clearing the data.
Thanks for the great app!
EDIT:
Well I’ll be…
Just after I posted this I fired up the Prime to find the version # (1.3.3 BTW) and as soon as I opened up AutHomation I was greeted by a message saying that it has stopped working. I clicked “OK” and then went right on using it. Everything was fine. Go figure.
S-F,
This sounds like the same issue that fba is having. I just released this app to the Android Market. Can you do me a favor and remove the current version and install AutHomationHD from the market? The reason I ask is, if the app crashes I get a report on the crash. This would be very very helpful. It really does sound like fba’s problem here:
http://forum.micasaverde.com/index.php/topic,9327.0.html
If that is the case, I think I know what is going on and hopefully have a fix for it. I really am sorry that it is doing this to you. Not a very good user experience. I am determined to track this down and fix it.
- Garrett
OK
I uninstalled, reinstalled from the market and set it back up. No crashes yet but it’s not respecting the default tab setting for me again. Last time it took a day or so for that to work itself out so I’ll be patient.
Thanks for all the hard work!
Peach of a tool you’ve got here.
[quote=“S-F, post:9, topic:170317”]OK
I uninstalled, reinstalled from the market and set it back up. No crashes yet but it’s not respecting the default tab setting for me again. Last time it took a day or so for that to work itself out so I’ll be patient.
Thanks for all the hard work!
Peach of a tool you’ve got here.[/quote]
S-F,
Thanks for installing from the market. Hopefully we can catch this bug. As for the default tab, I think I know what is going on. If you run the app and press the home button or switch to a different app, when resuming it will load the last saved state. This is because the app is technically still in memory and most likely because you use the app quite a bit. If you have not run the app for some time, say over night, the Android OS will close the app to allocate memory else where. Let me do some thinking on how I can tackle this. I can have another option in the default tab settings called “Current Tab” and that could save the current tab you are on when moving out of the app. If I go this route, I will need to adjust the way it preserves the tab selection on screen rotation.
- Garrett
Yeah I thought about that myself but I don’t think it’s the case. As I said before, it didn’t work at first and then it started to work just fine. If I left the device alone for a long period of time the difference was that when I opened AutHomation it would display the first room instead of whichever I was on last. It respected my selecting devices instead of scenes as default though. Now It’s not respecting that choice. I don’t recall whether or not it loads the first room in the list or the last one though. But I must be clear, that even if I switch to a different app for a little while, say a minute or so, when I go back it’s on scenes again. And it certainly hasn’t stopped the app as it’s the last one used and only a moment ago.
I wish I could be of more help. I’m always really moved when the developers of OSS take their work seriously.
EDIT:
OK. When switching between AutHomation and other apps, upon return AutHomation is remembering the last viewed room but not that I was viewing devices as opposed to scenes, even though I also have devices set as the default tab. And this is only leaving AutHomation for less than a minute.
Another quirk I just discovered is when selecting last saved level I get a ERROR Level out of range message. All works well again when I uncheck it. Appears to be 100% reproducible.
Hmmm, that us interesting. I’ll look into this. Is it reporting this when using the on button or the slider?
- Garrett
I did some testing on the last saved level option and I can reproduce the error. The error happens because when the option is enabled, and you go to turn on a dimmable device with the toggle button and you have not used the slider for that dimmable device after setting the last saved level option, the error pops up. This is a stupid error on my part and should have seen this. It came down to me checking the wrong value on a device that has not had the level value saved yet. I fixed this bug.
- Garrett
p.s. I loaded up an Ice Cream Sandwich tablet emulator and noticed a cosmetic bug. When resuming or switching tabs, the room section would not highlight the current room you are in. I did not notice this as it works on my Transformer running Honeycomb, but does not work when running Ice Cream (got to love it! Works on version, breaks in another. Love supporting multiple versions.)
- Garrett
[quote=“garrettwp, post:14, topic:170317”]p.s. I loaded up an Ice Cream Sandwich tablet emulator and noticed a cosmetic bug. When resuming or switching tabs, the room section would not highlight the current room you are in. I did not notice this as it works on my Transformer running Honeycomb, but does not work when running Ice Cream (got to love it! Works on version, breaks in another. Love supporting multiple versions.)
- Garrett[/quote]
Ha ha! I guess I didn’t know that feature didn’t work because I’ve never seen it! I installed ICS the moment I got the tablet.
It just crashed on me again. Same circumstances as the last time. Do you still want input on crashes or do you get all you need through the market?
If is not too much trouble, please keep me posted on anything you see that causes issues. I got the crash report and I am looking into the problem. It kind of has bee stumped, but I did had a few things to hopefully prevent this.
- Garrett
p.s. I forgot to ask, would you be willing to do some testing on a test build?
I’m not sure how much feedback I can really give on the crashes. It basically seems to only happen when opening the app or switching to it or however Android works.
And I sure would love to test an experimental build.
Trust me, you are providing me some good feedback. I would have not known about these issues unless you stepped up and told me. Out of curiosity, are you using the “auto refresh” option in the settings? I would like to try and reproduce what you have. I am adding some things to the current build and broke a few things which I am in the process of fixing, once I get those fixed, I’ll send you a PM with a link to the test build.
- Garrett
I just checked refresh on resume for the first time last night so I don’t think it has any direct relation to the crashes. I have auto refresh time set to 30 seconds, which I think is the default. Auto refresh is unchecked. What does that do exactly?