Topic: MK19200, iphone TOM TOM

Hi Looking to see if this may be a known issue.

I have a MKi9200 recent install.  Iphone 3GS with a TOM TOM app.  The iphone and TOM TOM I have been using for a long time with no problems.

Having had Parrot installed and setup I find that when running the TOM TOM app that the phone will randomly shut down and repower itself up.  This is when attached to the TOM TOM cradle or just a normal power cable.  I have not tried it without power attached yet.

Any thoughts or experience of this?

Mike

Re: MK19200, iphone TOM TOM

Just in case anyone interested problem not with Parrot.  It did the same thing yesterday when bluetooth connected to another built in car system  Must be App or iphone.

Re: MK19200, iphone TOM TOM

Hi Mikejp,

and thank you for your return.
have you checked for software update for your iPhone 3GS?
We never faced any similar issues regarding a phone or a specific app.

Re: MK19200, iphone TOM TOM

I agree, it is not a Parrot issue, this device is very good.

It is a problem with iPhone, although on latest software and latest apps it randomly crashes with anything that uses GPS

Re: MK19200, iphone TOM TOM

Parrot Advisor UK 75 wrote:

Hi Mikejp,

and thank you for your return.
have you checked for software update for your iPhone 3GS?
We never faced any similar issues regarding a phone or a specific app.

That was probably his problem....I updated my iphone 3GS to ios 5 (5.0.1 I think...have since replaced the 3GS with a 4S) and it started rebooting. The 4S and the 4 are both fine and it only started happening after I did a software update...maybe Apple have fixed it with the latest updates???

It's probably not as random as you think. I found mine was doing it in exactly the same location all the time and normally when on a voice call. A quick google found that since the update others had the problem.....when the signal is marginal/lost and the phone is in use and talking to the base station (ie voice calll or data connection) then it wil ldo a full reset and leave a kernel panic in the logs

Martin