Hello, I thought I would give a unbiased opinion on the Android and Saveo triggers. To give you a little background at where I am coming from; we have been using Mc55's since 2010. I have spent countless hours troubleshooting the wifi network, tweaking network profiles on the scanners,uninstalling and reinstalling NSCAN, find the best lighting for the lasers to read barcodes and we finally had enough. We decided to finally ditch the old tech and try something new.
The installation process was very easy if you are familiar with installing apps on your phone. If not your familiar with the installation of apps, the instructions are pretty well written. The trigger setup and paring was again fairly easy too. Setting up the NSCAN profile was straight forward. It did take a minute to get the profile to update, but when it does the first time, you are good to go.
The phone wifi is extremely stable even without MAC filtering and a full lobby of patrons. I did still leave broadcasting off for the SSID. I have not had any disconnects or drops. The processing speed is very fast. The triggers seem to work perfect. The lighting has no effect on reading the barcodes (crazy I know). We opted for actual phone cases to be mounted on the triggers (Does require the person at the end of the night to make sure the charging cable is tight).
The downside is that the screen display will go to sleep. So, we tried setting it the max and it seemed to complicated to explain to the usher core how wake the screen up. To solve this you could try and find a screen app to keep your phone awake. They all seem to complicated and did not work or had ads popping up, but there may be one out there on google play. So, I slapped together a simple app the do the job for us. If you want to try it is the zip on my profile files called, "installer" (Please note there are two versions in the folder. The more professional version is called ScreenOn and NoSleepy was the test. THIS IS AT YOUR OWN RISK!). I have only tried it on GS5's and GS6's.
Overall, if you are in the market for scanners that actually scan you may want to consider Android phones and the Saveo triggers. I am certainly please.
Travis
Travis,Thanks for the update! That is good to know!I'm curious to know if you are on RAMP or are your servers hosted locally?
Thanks,Daniel WilliamsFlat Rock Playhouse
We are on RAMP.
Travis,
We just purchased a Saveo. During our set up we are running into a problem I wonder if you have encountered.
The NScan app reads the barcode but does not translate all of the data; The bar code number is displayed but none of the text ie the buyer name and the seat location . This info will be displayed if we press the 'Go' Button, to the left of the bar code field. Also the screen won't reload. The scanned info. stays on the screen.
Did you run into this problem?
Any suggestions/ help is welcome---all three of our MC 55 have died!
Thanks,
Carol
I wonder if NSCAN group would consider implementing a toggle for FLAG_SHOW_WHEN_LOCKED or some other procedure to override the keyguard a proper way.
Hello Carol, No I did not have that issue. Have you tried multiple tickets? What droid devices did you get S4, S5 ...etc.? When scanning a ticket, the screen shows the ticket info and will not reload, but rather display the next ticket info once scanned.
Yes! The connection issues have been dramatically reduced. I think you be pleased. The only thing I have noticed is that some users do not allow the phone to connect to wifi before launching nscan, which obviously doesn't allow the profile to update or error out. Stress to the users to just be paitent and let the phone connect before launching.
Thanks for responding, Travis,
I downloaded the wrong version of NScan…. Still working out a couple of bugs, but the connectivity problems have vanished-- Phew!!
Looking forward to getting them up and running!
Thank you,
Carol Ciulla
Box Office Manager
37 Main St. 01966
978.546.7391 x 102
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Travis Armbuster Sent: Friday, November 4, 2016 12:02 PM To: Carol Ciulla Subject: Re: [Tessitura Ticketing Forum] Android and Saveo Triggers
From: Carol Ciulla <bounce-carolciull6102@tessituranetwork.com> Sent: 11/3/2016 4:24:09 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hey Travis.
This is super useful. We went with the Saveos after seeing them at the conference. We have Galaxy S5 phones. We constantly have problems with the scanners not scanning but they continue to beep as if they are reading the barcodes. The ushers are not always quick to notice this. I'm not sure it's a "sleep" issue but I will check out your app.
We do have dedicated NSCAN Wifi so I don't think that's an issue but I'm not sure how to check the stability anyway.
We were told that if we have issues with it not scanning to restart the app and reload the device profile. It doesn't seem like you guys have had any issues but every other night seems to be an issue for us with the scanners. Have you been told any other trouble-shooting ideas that we don't know about?
Thanks in advance.
Hello Adria, Make sure you disconnect and reconnect the bluetooth before every use and do a test scan (Do not forget to make sure the profile updated too.). Someone should check the all of them before every use. I do not know your wifi system, but I would review that too. Example, forcing disassocation at -X db. I am local so I could swing by if you really need help.
Hi Travis,
Thanks for the feedback regarding the Saveo triggers, that is great to hear.
Could I ask which model you are using, is it the R11D-BH or M22D-BH?
Kind regards,
Stefanie
Hey Travis. I'm still having problems with my Saveos. I haven't been able to scan tickets at all. Some Saveos aren't uploading the profile even though I've reset them with the barcode in the NSCAN documentation. I changed barcodes at the beginning of the season because we thought it was the barcode design. Then I saw that the address for the NSCAN RAMP had changed. I updated that and I still cannot get the scanners to work. Any thoughts? Do you know if there are barcodes that will not work with SAVEOs? When I try to scan in TEST mode it says invalid scan value.
Not that I am aware of, but I would start with the basics and work to the barcodes to makes all scanners are talking and profiles are updating first. Then maybe do a batch ticket print and do a mail merge with dobsons barcode 128. If that works, then it most likely is the desgin/barcode. Feel free to call me.
Just thought I would jump in.. We have had success getting SAVEO scanners paired with Android (v 5.1) device via BlueTooth running Nscan 6.0.6.
Thanks to Stefanie and Ranie @ Tessitura for their help.. Two caveats when doing this:
1. Saveo scanner must pair with BlueTooth
2. You need the Saveo documentation entitled 'Connecting to Saveo Scan via Bluetooth SPP' specifically, and you need to scan in all the SPP Bluetooth profile codes from B1 to B7, in order,
Cheers!