cherucole / battery-indicator

Automatically exported from code.google.com/p/battery-indicator
Other
0 stars 0 forks source link

Menu settings switched in Alarms menu #148

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Menu
2. Settings
3. Alarm
4. Add alarm
5. Alarmtype
6. Charge drops below

What is the expected outcome? 

Alarm sounds when battery level drops below preset value

What happens instead?

Alarm sounds when battery level rises above set level when charging

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

Which device are you using?
Samsung Galaxy S Plus

Which carrier are you using?
Vodafone

What language is your device set to?
Dutch

Which version of Android are you using?
2.3.6

Do you have an "Task Killer" or similar apps installed?
Yes, but set to manual, never automatic

Please provide any additional information here:
Selecting 'charge drops below' results in an alarm set for 'rises above', this 
selection is also shown as set in the menu

Original issue reported on code.google.com by jjmm.bat...@gmail.com on 5 May 2012 at 1:34

GoogleCodeExporter commented 8 years ago
It appears that a lot of settings refer to incorrect options, not just the one 
I described as a problem. Is it a problem with the Dutch translation?

Original comment by jjmm.bat...@gmail.com on 5 May 2012 at 5:02

GoogleCodeExporter commented 8 years ago
Still have the same problem on my SE Arc S(dutch lanquage, Andoid 4, T-Mobile), 
want the alarm to warn me when it comes BELOW 15%, put it that way in settings, 
but setting becomes(in words and in working!!!!!) ABOVE!!!!! 15%. Bought this 
app for the alarmpossibility, but that does not work, still! Please fix this 
soon? Hope you do something with this???

Original comment by chicay...@gmail.com on 4 Jul 2012 at 12:28

GoogleCodeExporter commented 8 years ago
Wow, I don't know how I never noticed this report from May. I'll look into this 
and report back soon.

Original comment by andr...@darshancomputing.com on 4 Jul 2012 at 10:23

GoogleCodeExporter commented 8 years ago
Huh, I just tried this on all seven of my test devices, and I couldn't 
reproduce it on any of them.  I didn't wait for the alarm to go off in all 
cases, but both of you reported that the issue seems to be in the setting of 
the alarm, and that whatever the alarms says it will do, it does.  So I'm going 
to have to dig through the code and try to figure out what might be causing 
this...

Although I just re-read both of your reports, and you're both using the Dutch 
translation.  That seems unlikely to be a coincidence.  I've got a pretty good 
idea what might be going on.  I'll look into it and report back.

Original comment by andr...@darshancomputing.com on 4 Jul 2012 at 10:32

GoogleCodeExporter commented 8 years ago
Okay, so there's a bug in the Dutch translation. I think this might actually be 
caused by a bug in my translation software, rather than being a translator 
mistake.  In any case, I'll have an update out soon, but in the meantime:

If you want "Becomes fully charged", select "Gezondheid faalt"
If you want "Charge drops below...", select "Is klaar met opladen"
If you want "Charge rises above...", select "Lading komt onder..."
If you want "Temperature rises above...", select "Lading komt boven..."
If you want "Health fails", select "Temperatuur komt boven..."

(As you can see, the array has shifted by one and wrapped around.)

You should get the behavior that you want if you follow the above mapping.  
When the update comes out in the next week or so, you won't have to change 
anything. The only change will be that the translations will be fixed, so it 
will at that point show the correct thing, rather than showing the wrong thing.

Original comment by andr...@darshancomputing.com on 4 Jul 2012 at 11:02

GoogleCodeExporter commented 8 years ago
I believe I've resolved this issue in the update I just pushed out (version 
6.0.1). I do think I still have a bug in my translation software, but in the 
meantime I wanted to fix this.  Please let me know if there are still any 
problems with it.

Original comment by andr...@darshancomputing.com on 15 Jul 2012 at 9:15