Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
We have just released CamerAlert for Android version 1.3.4 build 533 into the Android Market. It may take a little while before it becomes active, after which you should now be able to upgrade the application through Market and benefit from the new features and bug fixes we have implemented.
Changes for Android 533 follow:
New Functionality added support for the Parrot Asteroid Separate volume control for warnings in ‘Advanced Settings’ Stop location updates if not moved more then 20m in 10 minutes whilst not on the main screen Changed the inactivity speed threshold Allow CamerAlert to be controlled by car dock events General code changes to improve reliability and speed
Bug Fixes Fix where decimal point on KM was out by factor of 10. Fix where preferences were not properly initialised. Fix where there could be a crash if the database is empty when adding a camera. Changed Redlights with unknown speed to be announced as Redlight, not “Redlight unknown speed”
It's there now, mine updated at about 4.30pm this afternoon.
Bob
Triumph Tbird 1700. And now a Bonnie T100.
Posted by IanS100 on Wed Dec 14, 2011 8:48 am
I've just purchased CameraAlert for Android & the installation & database download all went smoothly but when I try to upgrade to the latest version I get:
Package file was not signed correctly
& the upgrade terminates, any suggestions?
Galaxy Note 4 / TomTom GO : CamerAlert : CoPilot
Posted by MaFt on Wed Dec 14, 2011 10:17 am
Sounds like the Market is playing up...
You could either try later in the day to see if it has resolved or maybe reset the phone (complete power off and turn back on).
Also make sure the date/time are correct on the phone etc.
MaFt
Posted by IanS100 on Wed Dec 14, 2011 10:21 am
MaFt Wrote:
Sounds like the Market is playing up...
You could either try later in the day to see if it has resolved or maybe reset the phone (complete power off and turn back on).
Also make sure the date/time are correct on the phone etc.
MaFt
Cheers, I've tried 'power off' & rebooted about 6 times but with the same result each time so I'll leave it till this evening & try again
Galaxy Note 4 / TomTom GO : CamerAlert : CoPilot
Posted by richard345 on Wed Dec 14, 2011 11:18 am
Installed OK on my HTC Sensation on Android 2.3.4 in the last few minutes.
All looking well at the moment and it's showing the 2 mobile sites that appear now and again outside our offices.
Thanks for all the good work guys an d Happy Christmas to everyone.
Ric - TomTom 520 DEAD - Passed to the great traffic jam in the sky. Now using Maps & Waze on Samsung Galaxy S4 + CamerAlert of course!
Posted by IanS100 on Wed Dec 14, 2011 11:53 am
No amount of installing resetting & rebooting made any difference but I have a result for anyone having the same problem:-
Open Market & select CameraAlert upgrade but don't actually set it going - leave the page open &
Flip to Settings / Applications & uninstall the old version of CameraAlert
Flip back to the Market / Upgrade screen & set it going.
Result is a clean install of v 1.3.4.533
NOTE: All this is assuming that the Market continues only to offer the old version for clean installs as it did with me this morning!
Galaxy Note 4 / TomTom GO : CamerAlert : CoPilot
Posted by DrSpecs on Fri Jan 13, 2012 11:55 am
I just wondered what the permission "Phone Calls" is used for within this app? The description for this:
"Read Phone State and Identity - Allows the application to access the phone features of the device. An application with this permission can determine the phone number and serial number of this phone, whether a call is active, the number that call is connected to and the like."
Seems particularly intrusive. Could you explain why this is needed.
Thanks
Posted by lbendlin on Fri Jan 13, 2012 12:30 pm
we are reading the phone IMEI (if available) and use that as part of the unique identifier for your device. We are not using the IMEI directly, instead we create a hash from it.
Code:
final TelephonyManager tm = (TelephonyManager) getApplication().getSystemService(Context.TELEPHONY_SERVICE);
tmDevice += tm.getDeviceId();
UUID deviceUuid = new UUID(androidId.hashCode(), tmDevice.hashCode());
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Posted by 253 on Tue Dec 13, 2011 6:59 pm
an d Happy Christmas to everyone.
