1ktkeith
Really, really dumb question here, but: I've been using the iPhone LT app to scan in my large collection, and it's great. But just recently it stopped making the little beep/vibrate notification that it used to when a book was successfully entered. Now I have to interrupt my process to check the status of every book I scan.
I have looked everywhere in the app and my iPhone settings to see if there is a setting that turns it on and off. I can't find it. (Yes, my phone is not set to "mute".) Any suggestions?
Thanks.
I have looked everywhere in the app and my iPhone settings to see if there is a setting that turns it on and off. I can't find it. (Yes, my phone is not set to "mute".) Any suggestions?
Thanks.
2kristilabrie
I'm going to ask what might be a stupid question but: is your volume up?
If yes and you're still not getting the scan "beep", what iOS are you on?
If yes and you're still not getting the scan "beep", what iOS are you on?
3conceptDawg
We have not changed the app. It's possible that you have your mute switch turned on (little switch on the left side of the iPhone above the two volume buttons).
4RobFaggart
I had the same problem. The problem (for me) is that the sound icon is confusing. On the scan screen, look at the bottom left for the sound/mute icon. If it HAS a slash, it is UNMUTED. WITHOUT the slash, it is MUTED. I guess it's showing what it will do if you tap it, rather than its current status. Drove me crazy until I figured it out. This is backwards from how mute is represented on virtually every other app I've ever used.
5kristilabrie
>4 RobFaggart: Where are you seeing the sound icon, again? I'm not seeing it in the iPhone app. To my knowledge, we don't have a sound button within the LT App.
6kristilabrie
>3 conceptDawg: >1 ktkeith: already said they checked that their phone wasn't on mute. :)
7lorax
kristilabrie (#6):
Thanks. It's nice to see staff believing users on bug reports when we say "I checked for this obvious case of user error and it's not the cause".
Thanks. It's nice to see staff believing users on bug reports when we say "I checked for this obvious case of user error and it's not the cause".
8kristilabrie
>7 lorax: I assume conceptDawg missed that part, I've been completely guilty of reading too fast or missing a detail or two here and there, but thanks. :)