| View previous topic :: View next topic |
| Author |
Message |
mrfrank
Occasional Visitor
Joined: Mar 06, 2006
Posts: 46
|
 Posted: Tue Feb 08, 2011 8:11 pm Post subject: |
 |
|
| mrfrank wrote: | | lbendlin wrote: | | Just for the sake of crapshooting, can you please confirm you haven't enabled "Ignore direction" in the settings? |
I haven't.
But, tomorrow I am going to try by using cameralert in the foreground, just to rule out that it is a problem of using the app in the background with "Sygic aura" in the foreground. |
I'll be damned. Using cameralert alone in the foreground worked perfectly in both directions. After the END specs I got the all clear and al was well.
To summarise, then:
1 - cameralert alone in the foreground = no SPECS issue
2 - cameralert in the background and Sysgic Aura in the foreground (launched automatically by cameralert via the "on startup also run" feature) = FAIL after END SPECS.
3 - cameralert in the background and Sysgic Aura in the foreground (launched manually afterward) = I WILL TEST tomorrow.
If 3 above passes, it may be an issue with the "on startup also run" feature.
If 3 above fails, well....we wil see if we get there.
Cheers. |
|
| Back to top |
|
 |
253
Lifetime Member
Joined: Mar 05, 2007
Posts: 1058
Location: The green bit between the M40, M4 and M25.
|
| Posted: Tue Feb 08, 2011 11:11 pm Post subject: |
|
|
Keep it going mrfrank, I'm enjoying this.
As an innocent bystander with no interest so to speak. 
Cheers, Bob
_________________
Triumph Tbird 1700. And now a Bonnie T100. |
|
| Back to top |
|
|
mrfrank
Occasional Visitor
Joined: Mar 06, 2006
Posts: 46
|
| Posted: Wed Feb 09, 2011 8:54 pm Post subject: |
|
|
| mrfrank wrote: | ...
If 3 above passes, it may be an issue with the "on startup also run" feature.
If 3 above fails, well....we wil see if we get there.
Cheers. |
UPDATE:
1 - cameralert alone in the foreground = no END SPECS issue
2 - cameralert in the background and Sygic Aura in the foreground (launched automatically by cameralert via the "on startup also run" feature) = FAIL after END SPECS.
3 - cameralert in the background and Sygic Aura in the foreground (launched manually afterward) = FAIL after END SPECS.
4 - cameralert in the background and Google Navigation in the foreground (launched manually afterward) = FAIL after END SPECS.
Tomorrow I will do the final test: cameralert in the foreground AND sygic aura in the background.
If this final test passes at the END SPECS I wil be able to safely say that there is a bug when cameralert runs in the background, at least on HTC Desire (android 2.2) that I am using.
Cheers. |
|
| Back to top |
|
|
hellybob
Occasional Visitor
Joined: Feb 17, 2006
Posts: 56
|
| Posted: Wed Feb 09, 2011 10:18 pm Post subject: |
|
|
| I think I am exactly the same on my rooted Hero on 2.2 |
|
| Back to top |
|
|
lbendlin
Pocket GPS Staff
Joined: 02/11/2002 22:41:59
Posts: 11878
Location: Massachusetts, USA
|
| Posted: Thu Feb 10, 2011 1:13 am Post subject: |
|
|
@mrfrank: I was able to replicate the issue and to correct it. Thank you for your persistence.
We'll test the fix internally and will release an update as soon as possible.
_________________
Lutz
Report Map Errors here:
TomTom/TeleAtlas NAVTEQ |
|
| Back to top |
|
|
mrfrank
Occasional Visitor
Joined: Mar 06, 2006
Posts: 46
|
| Posted: Thu Feb 10, 2011 10:47 am Post subject: |
|
|
| lbendlin wrote: | @mrfrank: I was able to replicate the issue and to correct it. Thank you for your persistence.
We'll test the fix internally and will release an update as soon as possible. |
Thx for this.
I just also tried using cameralert in the foreground and Sygic Aura in the background and it worked correctly.
So, can you confirm that the issue was caused by running cameralert in the background?
I am now very curious on what the root cause was ;)
Cheers. |
|
| Back to top |
|
|
lbendlin
Pocket GPS Staff
Joined: 02/11/2002 22:41:59
Posts: 11878
Location: Massachusetts, USA
|
| Posted: Thu Feb 10, 2011 3:43 pm Post subject: |
|
|
Well, one thing is clear - you'll never hear me say that this was a simple beginner programming mistake.
There. Keep calm and carry on.
_________________
Lutz
Report Map Errors here:
TomTom/TeleAtlas NAVTEQ |
|
| Back to top |
|
|
mrfrank
Occasional Visitor
Joined: Mar 06, 2006
Posts: 46
|
| Posted: Thu Feb 10, 2011 4:27 pm Post subject: |
|
|
| lbendlin wrote: | Well, one thing is clear - you'll never hear me say that this was a simple beginner programming mistake.
There. Keep calm and carry on. |
I am calm, cos I know you will provide the best and fastest support you can, as you guys always do ;)
Cheers!! |
|
| Back to top |
|
|
MikeB
Frequent Visitor
Joined: 20/08/2002 11:51:57
Posts: 3859
Location: Essex, UK
|
| Posted: Thu Feb 10, 2011 6:46 pm Post subject: |
|
|
We believe that this issue is now fixed in build 368 which should be available on Google Market now.
_________________
Mike Barrett |
|
| Back to top |
|
|
mrfrank
Occasional Visitor
Joined: Mar 06, 2006
Posts: 46
|
| Posted: Thu Feb 10, 2011 6:53 pm Post subject: |
|
|
| MikeB wrote: | | We believe that this issue is now fixed in build 368 which should be available on Google Market now. |
Got it from market place and going to check now on my way back home. Finger crossed and will report later tonight.
Thanks.
EDIT: It did work on the way back home with latest cameralert update. After the END SPECS was passed, the average speed monitoring reset and I did not get the repeated "50" big circle in the screen once I accelerated to 70mph. However, I did not see the red banner "Average 50 E (xxxyds)" popping up on the foreground and did not hear the "all clear". But, I may have missed them.
So, I cannot say for sure if there is a small quirk caused by the bugfix, so I will recheck next week on my way back to work. But, the main bug is resolved, which is the main good thing.
Cheers. |
|
| Back to top |
|
|
teb
Occasional Visitor
Joined: Dec 16, 2005
Posts: 17
|
| Posted: Mon Feb 14, 2011 4:53 pm Post subject: |
|
|
Hi Guys, I am experiencing exactly the same problems on the same set up as MrFrank; HTC Desire with Froyo 2.2 and Sygic. Im on Cameralert version 1.06.372. Dont get an all clear and the average speed camera warnings continue even after restarting the app and the GPS. If you need any further info let me know.
Cheers
Teb |
|
| Back to top |
|
|
lbendlin
Pocket GPS Staff
Joined: 02/11/2002 22:41:59
Posts: 11878
Location: Massachusetts, USA
|
| Posted: Mon Feb 14, 2011 5:04 pm Post subject: |
|
|
You may not get the all clear if you are either driving too slow, or if there are more cameras that are potentially coming up.
Can you please tell us the stretch of road where you experienced that behaviour?
_________________
Lutz
Report Map Errors here:
TomTom/TeleAtlas NAVTEQ |
|
| Back to top |
|
|
teb
Occasional Visitor
Joined: Dec 16, 2005
Posts: 17
|
| Posted: Mon Feb 14, 2011 6:17 pm Post subject: |
|
|
It occured on all average speed camera zones I passed on my journey;
A14 at Cambridge (70mph)
A1M roadworks (40mph)
M25 roadworks between A1M and M1 (50mph)
Coming out of these zones and increasing speed above the average speed limit sets the warning. The A14 70 mph limit showed the whole way home to Ely where are no further cameras en route and its mainly a 60mph road. Switching the app off and back on again when I arrived home it still showed a 70mph limit in the top right corner. Switching the app on again after a few hours the warning has cleared.
Hope this helps. |
|
| Back to top |
|
|
lbendlin
Pocket GPS Staff
Joined: 02/11/2002 22:41:59
Posts: 11878
Location: Massachusetts, USA
|
| Posted: Mon Feb 14, 2011 7:16 pm Post subject: |
|
|
what app version are you running?
_________________
Lutz
Report Map Errors here:
TomTom/TeleAtlas NAVTEQ |
|
| Back to top |
|
|
teb
Occasional Visitor
Joined: Dec 16, 2005
Posts: 17
|
| Posted: Mon Feb 14, 2011 10:20 pm Post subject: |
|
|
Version 1.06.372.
The same problem occured on the previous version and the Beta release before that. |
|
| Back to top |
|
|
|
![]() Posted: Today Post subject: Pocket GPS Advertising |
|
|
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making 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!
|
|
| Back to top |
|
|
|
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
