Ifor's orienteering training log


Page 1 of 2  > >>

Jan 3, 2012
Category: Website
Posted by: ifor
Forum added
Jan 2, 2012
Category: Website
Posted by: ifor
OK upgraded the site CMS system just now to 1.10.2.  hope everything still works.
Oct 30, 2011
Category: Website
Posted by: ifor
Added a blog section to the site.  I need to sort out the templates a bit as things are not looking so good.
CMS - 1.10.3 - Hyacinthe

Reporting issues.

OK if you have an issue I want to help try and sort it out.  Firstly please read the relevant help pages and check the forum for any relevant threads.

For any sort of crashing type scenario you should ensure you have filled in your email address for the crash reporting settings.  Settings -> Other Phone settings -> Error reporting usage stats -> user email.  The default setup for crash reporting sends a crash report to me with information like the details of exactly which line of code had an issue.  I don't get too much else certainly not enough to be able to identify the phone number or the person.  I can normally sort issues out directly from this but sometimes I can not work out the context of the issue.  If you have filled in the email address then I may get in contact to ask what you were doing at the time of the crash.  There is the same setting in IpSensorMan.

For anything sensor related then there are settings in IpSensorMan to enable it to log a file with all the sensor messages it receives.  This can be useful to see if things look to be being received properly etc.  To enable this logging go to IpSensorMan Settings -> Debug Logging Control then enable debug log for the appropriate sensor type and possible debug log low level for start-up and dropout type issues.  A file will be logged for each session into \sdcard\Android\data\com.iforpowell.android.ipantman\files\temp\*.csv there is also an IpSensorMan_log.txt file here with basic logging information from IpSensorMan.  Files in this directory are automatically deleted after a few days.  If you have an issue email real_support@iforpowell.com with a description of the problem and the files attached.  If it's for a ride you have uploaded somewhere then a link to the uploaded data may help.  

The internal ipBike detailed logs for any individual ride are held in a .ipp file.  these files can be found at \sdcard\Android\data\com.iforpowell.android.ipbike\files\internal_logs\*.ipp  The file name should match the ride name as showen in IpBike.  For any upload or bad looking data issues then this file can be usefull.

IpBike writes a logfile to  \sdcard\Android\data\com.iforpowell.android.ipbike\files\temp\IpBike_log.txt.  Some previous days logs are also kept.  Any errors may be written to this log so if you try something and it looks not to work sending me this logfile with details on the issue may help me work out what is happening.

As of IpBike version 2.4.5 Settings -> Support options -> Manage temporary files area opens a file view of the area where the log file will be you can find it and long press on it and select send to get it to some other app to get it off your phone e.g. email it or load it to Google drive for example.

It is possible to turn the logging level up.  To do this you need to put a file onto the sdcard at \sdcard\logback\  For IpBike you need ipbike.xml for IpSensorMan you need logback.xml.   You may need to right click and select save as to save the files depending on your browser.  You should only really do this if working with me on a specific issue.  having the logging turned up like this will hit battery usage by a bit so not something to do if you want a really long run time.

Email me at real_support@iforpowell.com

Previous page: gps issues  Next page: user defined expressions