Auto Respond 0.10.2

Auto Respond 0.10.2 has been published to the Play Store. It may be an hour or 2 until it is live on Google’s servers, but it has been posted. All of the bugs from the list earlier today are fixed. I tested on both 4.1 and 2.3 devices, and both are verified working. Changes made in settings screen will now happen immediately in all Android versions as well.

Free:
https://play.google.com/store/apps/details?id=com.havens1515.autorespondfree

Paid:
https://play.google.com/store/apps/details?id=com.havens1515.autorespond

Again, I am going to ask people to PLEASE report any bugs you may find. If you don’t report them, I may not know that they exist. If you send me an email about a bug, at least then I know it exists and can look into fixing it ASAP. So far, all of the bugs I have fixed are things that I have found myself.

Also, if you have any feature requests, let me know. I can add them to my to-do list.

Back to coding

I know it has been a while since I’ve done anything new… It has been a busy month. I started doing some more coding this week, and I’ve found and fixed a few bugs. (Why does nobody tell me about these?? If you find bugs PLEASE send me an email so that I can fix it!)

Here’s some stuff I’ve been working on:

Auto Respond:

1) A pretty big bug fix – I noticed that Auto Respond would sometimes toggle itself off. I was wondering why… what is causing this. It seemed kind of random, but I finally figured it out. It was something in the Dock Settings Menu. I figured out what was causing the problem, and it has been fixed. (It may not have been an issue if the dock options were not enabled. I’m also no 100% sure that this bug affected the free version.)

2) I fixed a small bug on the schedule tab, which cause 12pm to be shown as 0pm when using 12-hour clock.

2a) While on the subject of the scheduler, the changes made in the SDK have set me WAY back in the development of the scheduler. They depreciated some of the code I was using, and I need to figure out how to use the new methods.

3) I’ve made settings on 4.0+ devices take effect immediately. I’m not sure if the same is true for Pre-4.0 devices. (I know I tried it once, but it didn’t work quite as well as I had hoped.)

4) Google just released a new SDK, so I’m going to look at the new options in the SDK and the “support” API to see if there is a way for me to unify the menu across Android versions again.

5) I don’t think anything needs to be changed for the app to support Android 4.2, but I will be looking into that as well. (Especially once some 4.2 ROMs are released for the Galaxy Nexus, and I can test on an actual device.) I would actually like to look into the possibility of adding something into the “quick settings” area of 4.2. Not sure if apps have the ability to add toggles to that list, but it would be cool if I could make that a reality.

These changes are still a work in progress, and are not fully tested as of now. I will likely be fully testing them, across multiple Android versions, in a couple days. Once they are fully tested, and confirmed working properly, I will release an update.

As always, the app is available on the play store:
https://play.google.com/store/apps/details?id=com.havens1515.autorespond
https://play.google.com/store/apps/details?id=com.havens1515.autorespondfree

Both versions are still purple for epilepsy awareness month, and all purchases of the paid version still go to the Epilepsy Foundation.

GUI Euchre:

I have some changes that will be made in my Euchre game as well. I’ve found a few small issues (listed in the known issues document on the download page) and I plan on fixing those later this week. Not too many people actively use that program, so it’s a little lower on my to-do list. The issues that are present are not pressing issues either. They do not greatly effect the usability of the program, they’re just small things that annoy me when I play.

I want to take some extra time to re-do the AI in the game as well. Since I programmed it, I find it a little too predictable. There are also times when I think the computer players call trump too often, or they take risks that are not necessary to take, and other times they are quite risky enough. I want to add some more random events into their logic, making the players a little less predictable, but also try to make them play smarter. Some of my logic is built on too specific triggers, and I want to work on that.

Having never taken a class or read anything about AI design, I am learning as I go. It’s kinda tough to teach yourself a concept like AI design, but I think I’m doing pretty well with it. I would like to eventually be able to build in selectable play styles, or difficulty settings, but that’s kinda tough to do in a game like euchre. I’d first need to learn different play styles, then perfect them, then program them.

if you want to check out the Euchre game (as it is now) you can get it here: bit.ly/GUIEuchre

Auto Respond for Epilepsy Awareness!

As I said in my last post, this month is Epilepsy Awareness Month.
I have decided to turn Auto Respond purple for the month. My icons and my Play Store banner have been turned purple instead of their normal blue and green.

On top of changing the color, ALL money that is made from the sale of the paid version of Auto Respond during November will be donated equally between the National Epilepsy foundation (http://www.epilepsyfoundation.org/) and my local branch of the Epilepsy Foundation. (http://www.epilepsyuny.org/) My local branch has done WAY too much for me, my family, and my friends to not include them specifically.

70% of all sales in the Play Store go to me, the rest goes to cell carriers. ALL of that 70% will go from my bank account, to the Epilepsy Foundation at the end of the month. I will not keep 1 cent of the sales that I make this month.

Unfortunately, I do not know if there is a way to get 100% of your purchase to charity, but my 70% can still make a difference!

If you would like to donate, separate from your purchase, you can do so here:
https://secure2.convio.net/efa/site/Donation2?df_id=1774&1774.donation=form1
or here:
http://www.epilepsyuny.org/donate.htm

Donations from the “Donate” link in my app can also be sent to the Epilepsy Foundation. Just include a note when you donate that you would like that donation to go to the Epilepsy Foundation. (The money will initially go to me, but I WILL make sure it gets to the foundation at the end of the month!)

Auto Respond 0.10.1

0.10 doesn’t load the Settings screen properly on pre Android 4.0 devices, so I had to scramble to get some workaround code. It’s back to normal for now, I’ll start working on a solution that works cross-version, since my current setup obviously does not. (The Settings menu shows slightly differently depending on your Android version, but it will work on all devices now regardless of version.)

0.10.1 has been published to the market but, as usual, it will take an hour or so for Google’s servers to push it out.

Auto Respond 0.10

I have published Auto Respond 0.10 on the Play Store. Some of this was actually included in previous releases (0.9.2 or so), but I included all of it in this changelog.

Big things:

• The Android SDK changed to make it a lot harder to have the menu setup the way I did, so I had to put everything into categories
• Added a couple new options: notifications are totally optional now, with an additional option for it to be permanent, and there is now an option for vibrate as well as silent
• Added more info into the JB style notifications

Small things:

• Fixed a few small bugs
• Added “Cancel” to the long-press menu for the list of messages

Full Changelog here: http://bit.ly/Rmi6Wf

The new version should be live in the Play Store as soon as the Google servers are updated (an hour or so usually.)

More Work on Notifications

I’ve been playing around a lot with notifications. I enhanced the JB style notifications more. They now tell you your current message, how many replies were sent, and provide a list of contact names that have been replied to.

I also made separate options of “Show Notifications” and “Permanent Notification”. If only “Show Notifications” is on, you will see a notification every time a response is sent and the notification will be able to be cleared. If both “Show” and “Permanent” are on, there will be a permanent notification, as it works now. If neither are on, the app will not display a notification at all.

I may throw them into a new sub-category of settings, and I will likely keep building on the current options. (Especially for Android 4.1+ users.) If you have any ideas, suggestions, etc. feel free to let them be heard!

These notification enhancements have not been released yet, but I will let you all know when they are!

Also, I’ve been working with ad displays in the free version. I may have overlooked something stupid, and there may not have been an issue in the first place. I am still working with Tap for Tap on some other lingering issues, but I’m not sure if there were any issue with ads displaying properly or not. If anyone has any feedback as to whether or not you are seeing ads in the free version, it would be appreciated. (If you’re not now, I’ve confirmed that they will be displaying correctly in future versions.)

Auto Respond 0.9.3

As promised, I looked into the issue with the notifications. It took me some time to figure out how to make notifications work properly on JB and pre-JB, but I did it.

Notifications pre-JB should be working again. And for users who are actually using JB, you should have a little extra info in your notifications. (Your current response message and the number of responses sent. I’ll build on it later.)

For those of you pre-JB (or at least pre-ICS) ads are still not working in the free version. Lucky you. I have been in constant contact with Tap for Tap trying to get numerous issues worked out in the past 24-hours, so hopefully (for me, not hopefully for you) you will be seeing ads soon.

I’ve been doing a lot of thinking, and I think that the scheduler may end up becoming a paid only feature. It’s a lot of work, and I need to give people incentive to buy the paid app, especially since ads aren’t even working right now.

New versions have been posted for both the free AND paid versions. It may take a while for the updates to get through Google’s servers though.

Oh, and one last thing… the new options I mention in a previous post… they’re in there 😉
(Vibrate as well as silent, and the *still untested* option to ignore calls – use at your own risk!)

Auto Respond 0.9.2

Found another FC in Auto Respond, thanks to a crash report someone sent in. I just released an update that fixed it.

Unfortunately, I did some work on notifications today too (working toward getting Jelly Bean style notifications working) and that work has made notifications stop working in some Android versions (possibly all versions prior to 4.1)

I was in a rush to fix the FC, and pushed the update, not realizing that it broke notifications. (I tested it later on my Droid 2, and that’s how I realized it broke notifications.) I am extremely tired, after dealing with Tap for Tap developer support most of the day, and some craziness happening at work, so I need to go to sleep. Sorry for the issues, I will try to fix notifications tomorrow and push an update ASAP.

BTW – Only the free version is affected by this FC and notification issue. The FC wasn’t present in the paid version, therefore I did not push an update for it and I did not break notifications for it.

Fixing Bugs, adding options

I’ve been working on some stuff for Auto Respond.

BUG FIXES:
I noticed that other day that between 12am and 1am, the hour shows as -12, and it shows as pm instead of am. That has been fixed.
I also noticed, on my phone, that my ringer kept getting set to “ring”, instead of “ring and vibrate” and I finally figured out that it’s my own app that’s causing it. If you have the “Silence Ringer” option selected, it wasn’t always properly returning the ringer to it’s previous value when disabling Auto Respond. I figured out why, and fixed that as well.

NEW SETTING:
Another thing that bothered me was that when I selected the “Silence Ringer” option, it turned off vibrate as well. So I kept the silence ringer option (for those of you who want it truly silenced when active) and added a sub-option to set it to “Vibrate” instead of fully silent. This has been tested, and seems to be working fully, so it will be in my next release.

IN PROGRESS:
I’m also working on an option to “Ignore Calls”. This will be enabled when “Auto Respond to voice calls” is active. If “Ignore Calls” is active, it will ignore any call that is sent a text response. If the call does not come from a mobile phone, comes from a number that’s not in your contacts, or comes from someone on the “Do Not Respond” list, it will not be sent a response and therefore will not be ignored. For this reason, the ringer options are still available even when ignoring calls is enabled. (This function is not tested yet, so if it doesn’t work properly, it may not make it into the final product.)

As I was thinking about the “Do Not Respond” list, I also thought about creating a number based list. Any phone number in this list would not be responded to. I haven’t even begun to implement it, I just got the idea while working on other things.

I haven’t forgotten about the scheduler. I have spent a lot of time working on it, and have been thinking about the best way to implement some of the necessary aspects of it. It is by far one of the most complex features I have worked on thus far for this app, so it may take more time than expected.

This is how the “Phone Settings” menu looks now (Assuming the “Ignore Calls” function works properly)

tl;dr – some small bug fixes, new vibrate setting, testing ignore calls setting, possible DNR number list in future, still working on scheduler.