470 replies to this topic

[3shirts]

Here are my logs (I am also having the issue where iGo only works the first run after a soft reset)
 TMCLogs.zip   80.52K   132 downloads

[BeamRider]

3shirts, on Apr 21 2009, 11:40, said:

Here are my logs (I am also having the issue where iGo only works the first run after a soft reset)
TMCLogs.zip

Have you upgraded to 0.9.3.8? From the logs appears you don't

[3shirts]

Ok, I'll try that

EDIT:  Updated but still have the same issue

Edited by 3shirts, 21 April 2009 - 10:59 AM.

[Alex-1]

BeamRider, on Apr 20 2009, 12:58, said:

Sorry mate, this happened once to a friend of mine but I wasn't able to reproduce it on my device (my fault to haven't incuded into known bugs)
To fix this just manually set this segistry key:

"HKLM\Devices\BuiltIn\OmniaTMC\TMCProtocol" to 3

then decativate and reactivate TMCSerial using the tool.

The protocol box should read Royaltek also when greyed out.

Yeah.. its working now.. GPS port is probably used now and iGO couldn't find any satelites, but it can by managed I think.. Thanks for this driver!

[jeffrey2000]

BeamRider, on Apr 21 2009, 09:57, said:

Yes it should be something similar except for the fact that the driver should always be loaded in memory.

Appears that iGO is not closing in the right way, something remains loaded and keeps the serial port opened. On the second iGO launch, the new instance tries to connect to the port but the driver is still locked by the previous one and reports a failure.

I need your logfile to crosscheck this issue so, please follow this steps:

• soft reset (just to clean all)
  
• if you have \TMCSerialLog.log and \TMCDump.log files on your mobile, delete them
  
• enable logging as described in my previous post (disable TMCSerial, enable log options, enable TMCSerial)
  
• launch iGO and play for some seconds
  
• close iGO
  
• wait a 1 or 2 minutes
  
• launch iGO again (here, in your case, you should not be able to use TMC)
  
• close iGO
  
• take the two log files and mail them to me so I can take a look to what is happening

Thank you for the effort, I'm just trying to discover if this is my fault or iGO's

k the files are on the way... After the 2nd time it's says "TMC hardware not found" and the TMC options are greyed out in Igo. After reopening the OmniaTMC program I get the grey bar which is like 10% but doesn't get any data from it, when I change the frequency again I get data but still doesn't work in Igo (until I reboot)...

update: Btw the "TMCSerialLog.log" file seems to keep increasing even when not using Igo dunno if that's supposed to be like this though... The file was getting about 1 mb already and still increasing pretty fast, so deactivated TMCSerial and disabled the log files and got the message: "GPS Port does not exists", rebooted, disabled the logfiles activated the TMCSerial and worked again (once) after a reboot. But when it works it does work good , sometimes even without connecting the headset so great app just little bug in the TMCdriver or shutdown procedure of Igo.

Edited by jeffrey2000, 21 April 2009 - 12:28 PM.

[pekkala89]

I wonder if it is possible to add an test tmc message to the program. You could test that tmc is working and sending information in igo etc.

[BeamRider]

jeffrey2000, on Apr 21 2009, 13:13, said:

k the files are on the way... After the 2nd time it's says "TMC hardware not found" and the TMC options are greyed out in Igo. After reopening the OmniaTMC program I get the grey bar which is like 10% but doesn't get any data from it, when I change the frequency again I get data but still doesn't work in Igo.

update: Btw the "k the files are on the way... After the 2nd time it's says "TMC hardware not found" and the TMC options are greyed out in Igo. After reopening the OmniaTMC program I get the grey bar which is like 10% but doesn't get any data from it, when I change the frequency again I get data but still doesn't work in Igo." file seems to keep increasing even when not using Igo dunno if that's supposed to be like this though...
had to disable the TMC program service, the log file was getting about 1 mb already and still increasing pretty fast, gonna disable the logging again

Yes the TMCSerialLog increase is a symptom of the port still open, anyway the pattern shown on your log is typical of the 0.9.3.7 version. To be sure, look at \Windows\TMCSerial.dll for its version to be:

File version: 0.9.3.23
Product version: 0.9.3.8

You can also try to update it again, but just add a soft reset before to start the described procedure (a locked TMCSerial can cause problems). Also, before installing 0.9.3.8 check that both \Windows\TMCSerial.dll and \Windows\AdvFMRadio.dll are not present anymore and be sure to install to Device and not to Storage/SD.

Then try again with iGO and record a new log and send it to me so I can confirm you if the driver was updated.

Until you got 0.9.3.8 I can't be of much help because the previous version was flooding iGO with status messages (80621 appears to be less sensible to serial "flooding") and I think this was causing most of the problems.

[3shirts]

Here are the logs with the latest version

 TMCLogs.zip   17.78K   67 downloads

[jeffrey2000]

BeamRider, on Apr 21 2009, 13:30, said:

Yes the TMCSerialLog increase is a symptom of the port still open, anyway the pattern shown on your log is typical of the 0.9.3.7 version. To be sure, look at \Windows\TMCSerial.dll for its version to be:

File version: 0.9.3.23
Product version: 0.9.3.8

You can also try to update it again, but just add a soft reset before to start the described procedure (a locked TMCSerial can cause problems). Also, before installing 0.9.3.8 check that both \Windows\TMCSerial.dll and \Windows\AdvFMRadio.dll are not present anymore and be sure to install to Device and not to Storage/SD.

Then try again with iGO and record a new log and send it to me so I can confirm you if the driver was updated.

Until you got 0.9.3.8 I can't be of much help because the previous version was flooding iGO with status messages (80621 appears to be less sensible to serial "flooding") and I think this was causing most of the problems.

Just deactivated, and checked and I have TMC Serial driver:
File version: 0.9.3.23
Product Version: 0.9.3.8

So I guess it's the latest version as you just posted.

UPDATE: 15:11 21-4-2009:
-uninstalled
-rebooted (TMCSerial.dll and AdvFMRadio.dll files were gone)
-reinstalled
-activated the OmniaSerial -> rebooted
-Opened Igo again into TMC settings -> scanned for channels and got some TMC (GIFT) channels and received the traffic info right after.
-closed and reopend Igo and TMC settings are greyed out and TMC Hardware is not found again

16:17 21-4-2009: Just sent new logs...

Edited by jeffrey2000, 21 April 2009 - 02:18 PM.

[BeamRider]

jeffrey2000, on Apr 21 2009, 15:03, said:

Just deactivated, and checked and I have TMC Serial driver:
File version: 0.9.3.23
Product Version: 0.9.3.8

So I guess it's the latest version as you just posted.

UPDATE: 15:11 21-4-2009:
-uninstalled
-rebooted (TMCSerial.dll and AdvFMRadio.dll files were gone)
-reinstalled
-activated the OmniaSerial -> rebooted
-Opened Igo again into TMC settings -> scanned for channels and got some TMC (GIFT) channels and received the traffic info right after.
-closed and reopend Igo and TMC settings are greyed out and TMC Hardware is not found again

Ok folks from 3shirts logs (confirmed as 0.9.3.8) I noticed that the last session was never closed. If you take a look at TMCSerialLog.log you'll find these sections (time in ms):

173200 TMCSerial initialised in Royaltek mode

202543 Begin of session
241802 End of session (init and tune / rds and tmc data present)

249894 Begin of session
241802 End of session (init only)

255058 Begin of session
258433 End of session (no init or command issued)

259991 Begin of session
263090 End of session (init only)

265210 Begin of session
269402 End of session (init only)

270604 Begin of session
368429 End of session (init and tune / rds and tmc data present)

413041 Begin of session
473287 ... no init and no commands issued. TMCSerial keeps sending state notifications

something very bad happened to iGO after 368429 (I think you closed iGO here and reopened around 400000). It opened TMC port, but he was not initialising TMC nor reacting to state notification coming from me. Simply it stays there with the port opened.
I bet that is not me, but iGO sources for executables, data files and config files are so many that I can't be more accurate. Are you able to test with newer iGO builds?

EDIT: From jeffrey2000 logs (that are very similar) I also noticed that my internal buffer are saturating so it seems that the port is opened but nobody is reading from them ... A good reason for iGO not detecting TMC (in fact he is not reading from the port).

---------------

I found also that, in some conditions, with 80621 thare are some audio problems caused by FM chip initialisation (that configures some audio   parameters ... :S) and causing sound playback to slow down. I'm trying a workaround, but the cause is inside Samsung part and I prefer to keep solutions on my own code.

Edited by BeamRider, 21 April 2009 - 02:08 PM.

[jeffrey2000]

so can't the driver be loaded on demand? So when Igo starts the driver starts aswell and when you shut it down the driver does it aswell, this also saves your battery life and maybe solves this problem?

Edited by jeffrey2000, 21 April 2009 - 02:36 PM.

[qwertztmc]

Hi!

Works in Germany, I received TMC Data from a few stations in the in the configuration-tool and in Igo 8.3!

Great Job! Thank you very much!

[evil Homer 3k]

Hi all...

I installed the first version yesterday before the new version came out (had just hard reset my phone and was reinstalling everything).

Got it all working but didn't get a chance to try it out on the road. After my buggering around with installing last night, I left the phone charging overnight, but today it depleted the battery by 60% with hardly any usage.

So can I assume that this driver is constantly active in the background monitoring TMC data even though IGO isn't in use? If so, is there a way to start and stop it when running IGO rather than manually?

If it means a constant battery drain, I'd rather go back to not having TMC access if you see what I mean.

[BeamRider]

evil Homer 3k, on Apr 21 2009, 21:49, said:

Hi all...

I installed the first version yesterday before the new version came out (had just hard reset my phone and was reinstalling everything).

Got it all working but didn't get a chance to try it out on the road. After my buggering around with installing last night, I left the phone charging overnight, but today it depleted the battery by 60% with hardly any usage.

So can I assume that this driver is constantly active in the background monitoring TMC data even though IGO isn't in use? If so, is there a way to start and stop it when running IGO rather than manually?

If it means a constant battery drain, I'd rather go back to not having TMC access if you see what I mean.

Hi the driver remains loaded but sleeping: on TMC port closing, the driver closes both GPS and TMC and stops its internal threads.  GPS and tuner chip areactivated only when TMC port is opened or if something else is keeping the port opened (ie GPSGate). Battery draining is not acceptable and the driver has been developed with this in mind. So I can assure you that you'll end up using TMC without killing your battery (as a matter of fact I'm keepeng it running 7x24 and charging just like before).

Just for statistics, which iGO build are you using? Is somebody else experinecing battery drain?

EDIT: one thing I missed, do you still have the first version?

Edited by BeamRider, 21 April 2009 - 09:26 PM.

[BeamRider]

jeffrey2000, on Apr 21 2009, 16:25, said:

so can't the driver be loaded on demand? So when Igo starts the driver starts aswell and when you shut it down the driver does it aswell, this also saves your battery life and maybe solves this problem?

Yes it is exactly what you are doing by Activating/Deactivating TMCSerial ... but this driver it has been designed for a minimal impact and must work without manual intervention. Other point against on demand loading is that if you can't Deactivate/Reactivate TMCSerial after iGO shutdown you would be unable to do it also with "on demand" method.
I'm building an high level test/stress application to test this situations. This application will: open TMC port, search TMC station and receive/decodes data (n times) then closes the TMC port and restarts the loop. It should provide a stability proof when in doubt.

AdvFMRadio must remain loaded because it is a kernel mode driver (just like original FMRadio).

[Fabione72]

Both Omnia TMC and FM radio succesfully tested on igo8.3.2.71348 (ITALY: 102.5).

Multiple igo8 start-up without soft-reset test: OK, it works.

notes:

- SDKcert installed.
- your driver installed on MYStorage space
- igo8 GPS port:3  igo TMC port: 4


G R E A T    W O R K  ! ! ! ! ! ! !


Hale to the TMC drivers king !!!    

[jeffrey2000]

@Beamrider: FYI: I posted the Omnia files, link is in ur mail, so waiting for your test results, if it's just the exe file itself I would appreciate getting the 'right' file tnx in advance!, I made some 'performance' changes in the sys.txt and SGH-i900.ini file (data.zip).

Edited by jeffrey2000, 22 April 2009 - 08:26 AM.

[evil Homer 3k]

Deleted

Edited by evil Homer 3k, 22 April 2009 - 09:30 AM.

[evil Homer 3k]

Deleted

Edited by evil Homer 3k, 22 April 2009 - 09:28 AM.

[evil Homer 3k]

BeamRider, on Apr 21 2009, 22:20, said:

Hi the driver remains loaded but sleeping: on TMC port closing, the driver closes both GPS and TMC and stops its internal threads. GPS and tuner chip areactivated only when TMC port is opened or if something else is keeping the port opened (ie GPSGate). Battery draining is not acceptable and the driver has been developed with this in mind. So I can assure you that you'll end up using TMC without killing your battery (as a matter of fact I'm keepeng it running 7x24 and charging just like before).

Just for statistics, which iGO build are you using? Is somebody else experinecing battery drain?

EDIT: one thing I missed, do you still have the first version?

Oh ok... I've disabled it for now, but battery drain continues so I do apologise for questioning your driver. Obviously its something else lol.

Build of Igo 8 is quite an old one, 8.3.2.64873.

Edited by evil Homer 3k, 22 April 2009 - 09:27 AM.