Application crash when I try to create alarm

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Samsung Galaxy S2 with ICS (4.0.3)
2.Try to create Alarm

What is the expected outcome? What happens instead?
When I touch "Add alarm" application crash (stop working)

What branch (Free or Pro) and version (number) of the app are you using?
Pro (5.1.4)

Which device are you using?
Samsung Galaxy S2 (XEZ)

Which carrier are you using?
Vodafone CZ

What language is your device set to?
English

Which version of Android are you using?
4.0.3

Do you have an "Task Killer" or similar apps installed?
No.

Please provide any additional information here:

Original issue reported on code.google.com by stefan.v...@gmail.com on 26 Apr 2012 at 8:26

[GoogleCodeExporter]

Same problem. Same device and settings. Only difference is carrier (mobile 
vikings).

Additional: when the app restarts, an alarm is added and can then be set.

Original comment by johandel...@gmail.com on 20 May 2012 at 1:28

[GoogleCodeExporter]

Same problem at the same devive with the same firmware.

Original comment by paxl...@gmail.com on 18 Jun 2012 at 8:03

[GoogleCodeExporter]

But still open issue :-((

Original comment by stefan.v...@gmail.com on 18 Jun 2012 at 8:06

[GoogleCodeExporter]

Sorry for taking so long to respond.  When I get a bug report I always try to 
reproduce it, and when I can't, I really ought to say so.  But I always hope I 
can try harder and somehow figure it out, so it just ends up sitting there.  
That's a failing on my part that I aim to get over.

Anyway, it's certainly interesting that you all have the same device.   I can't 
think of what would make that device behave that way though.

Questions for anyone having this issue:

1) Are you still having the issue?
2) You can't set any alarms, because when you press "Add Alarm", the app 
crashes?
3) Do you get a Force Close message, or does the app just disappear?
4) What language are you using the app in? (Several weird bugs like this have 
been tracked down in the past due to a missing string in a translation.)

Thanks for taking the time to file this issue, and sorry for the delay; I'll be 
better from now on.

Original comment by andr...@darshancomputing.com on 9 Aug 2012 at 12:43

• Changed state: NeedMoreInfo

[GoogleCodeExporter]

1) problem still exists. Since the update (aug 4) the alarm no longer sounds 
when recharched or overheating.
2) yes. App crashes when "add alarm" tapped.
3) no force close message. I get a black screen and the phone hangs. App 
immediately restarts after the crash and an alarm is added in settings that can 
be customized but doesn't sound (before the aug 4 update it did sound)
4) using english. Android system also in english. 

Thanx for responding.

Original comment by johandel...@gmail.com on 9 Aug 2012 at 1:13

[GoogleCodeExporter]

That's really strange.  Would you mind sending me your system logs?  There are 
several ways to do so, but if you don't already have a favorite, I recommend 
the app in the Market called CatLog.  If you get Battery Indicator to crash, 
then run CatLog, there's an option to email the logs.  My email address is my 
username here (the part before the '@' is 'android').

Hopefully there will be something in there that gives a clue as to what's going 
on, because it sure doesn't make any sense to me right now.

Thanks!

Original comment by andr...@darshancomputing.com on 9 Aug 2012 at 1:26

[GoogleCodeExporter]

I got your logs fine; thanks for sending them.  The relevant lines are these:

android.database.CursorIndexOutOfBoundsException: Index 0 requested, with a 
size of 0
at android.database.AbstractCursor.checkPosition(AbstractCursor.java:400)
at 
android.database.AbstractWindowedCursor.checkPosition(AbstractWindowedCursor.jav
a:136)
at 
android.database.AbstractWindowedCursor.getInt(AbstractWindowedCursor.java:68)
at 
com.darshancomputing.BatteryIndicatorPro.AlarmDatabase.addAlarm(AlarmDatabase.ja
va:168)
at 
com.darshancomputing.BatteryIndicatorPro.AlarmsActivity$1.onClick(AlarmsActivity
.java:85)

The line causing the problem makes it look like the new (empty) alarm was never 
created for some reason.  That's very strange.  Before jumping in and sending 
you test builds to experiment with (which is the next step, if you're willing), 
lets try something easier: Can you uninstall the app and then reinstall it?  
I'm wondering if the database was somehow corrupted.

Thanks.

Original comment by andr...@darshancomputing.com on 9 Aug 2012 at 6:03

[GoogleCodeExporter]

I need a volunteer who can work with me to run some test builds in order to 
figure out what's going on.  I'll keep thinking about this, but it's unlikely 
I'll figure anything out without a tester with an affected device.

What this involves:

 A. Initial set-up:
   1. Ensure that "Unknown Sources" are enabled so you can install the build
   2. Download CatLog or similar program from the Market

 B. At least a few (it's impossible to know how many) rounds of:
   1. Receiving a test build from me via email and installing it
   2. Run it, then send me the logs via LogCat

Initial set-up should take 2-3 minutes, and each round of testing should take 
maybe 3-4 minutes.  Again, I'll do my best, but I don't have high hopes of 
figuring it out without help, since I can't reproduce the issue on any of my 
test devices.  Thanks.

Original comment by andr...@darshancomputing.com on 10 Aug 2012 at 12:44

[GoogleCodeExporter]

Okay, I still don't understand what was/is causing the problem, but I've made a 
few changes that I think might resolve the issue.  It's kind of a shot in the 
dark, but I think there's a reasonable chance the changes will avoid the 
problem, and in any case the code is slightly cleaner now.  If someone can test 
it, that would be great; otherwise the next time I push an update (probably 
within a month) these changes will be there we'll find out then.

Thanks!

Original comment by andr...@darshancomputing.com on 11 Aug 2012 at 2:00

[GoogleCodeExporter]

The latest update on the market seems to have fixed the problem, added two
alarms and the app didn't. If there is a problem later on I'll let you know.

Sorry I didn't want to install off market. I did install the classic
plugin, but still think that it should be part of the app itself, the new
icon is kind off bland, the classic one clearly indicates battery.

Greetings, Johan Delpire

crash when I try to create alarm

made a few changes that I think might resolve the issue.  It's kind of a
shot in the dark, but I think there's a reasonable chance the changes will
avoid the problem, and in any case the code is slightly cleaner now.  If
someone can test it, that would be great; otherwise the next time I push an
update (probably within a month) these changes will be there we'll find out
then.

Original comment by johandel...@gmail.com on 3 Sep 2012 at 8:53

[GoogleCodeExporter]

Awesome, I'm marking this as fixed for now; will reopen if anything else comes 
up.

Original comment by andr...@darshancomputing.com on 3 Sep 2012 at 4:57

• Changed state: Fixed