FORScan Lite Beta for Android

[FORScan]

Update v0.9.8beta, 2015-05-28
- Added new option 'Save debug info' (in addition to 'send' one). Added specially for users that have no mail setup. Logs are saved to Downloads/FORScan/log
- Fixed incorrect opening live data in connected mode
- improved parameters sorting in profile

Update v0.9.7beta, 2015-05-14
- last selected module is now remembered in Table, Dashboard or Graph modes
- added Drag button to the profile for more convenient sorting
- adjusted Dashboard gauges graphics (sizes, colors etc)
- fix of the send debug info function in Android 4.0
- trial period is extended until July 1st, 2015

Update v0.9.6beta, 2015-05-03
+ Added Enable/Disable Bluetooth setting (enable Bluetooth on start and disable on exit). Note: it doesn't ask for permission anymore, just enables if the setting is on, connection type is set to one of Bluetooths' and demo mode is off. Disables on exit for the same conditions.
- fixed several bugs in layout and navigation between sections in tablets
- fixed incorrect work with UTF characters in names of saved files
- fixed incorrect work with Downloads folder in some cases
- fixed delete options in open menus
- fixed small content bugs

Update v0.9.5beta, 2015-04-29
* Added "Exit" function when user taps Back from the main application window
* Added ability to save logs as TXT files to standard Downloads folder
* Added ability to save live data in CSV format to standard Downloads folder
* All documents are saved now to the standard Downloads/FORScan folder instead of internal storage
Note: it is recommended to use a file explorer (for example ES Explorer) to work with TXT and browse documents in the Downloads folder
* Fixed crash bug in the PID profile sorting procedure
* FIxed crash bug when user opens Table, Dashboard or Graphcs of module with large number of PIDs
* incorrect handling measurement units (Metric/Imperial) in some cases

Update v0.9.4beta, 2015-04-22
* Fixed Bluetooth communication bugs
* Added Bluetooth Request on applcation start
* Added Short module name on Errors page
* Added Android 4.0 support
* Fixed incorrect font size on some devices

Update v0.9.3beta, 2015-04-19
* Changes in Bluetooth 0 connection method
* Fixed bugs in sending debug information procedure
* Fixed content bugs

Update v0.9.2beta, 2015-04-19

* Fixed bug sharing files on Android versions 4.4 and higher
* Some changes in Bluetooth 0 connection method

Download link is updated. It is recommended to remove previous version before installing new one

It was decided to make public the testing version for Android . Everyone can download trial version using the link below. This version will expire in 1 month from today, and user will be suggested to download actual version for Android Play Market.

FORScan Lite limitation (differencies from FORScan for Windows):

* No Test and Service chapters. Tests is going to be added in the future
* Support of Bluetooth and WiFi adapters only. USB support may be added in the future
* Only Android v4.0 and newer devices are supported. We do not plan yet to support older versions (in our opinion, amount of such devices is already insignificant)
* This version of application is built only for ARMv7 architecture. If your device has another one, or you don’t know what it is but the application doesn’t work, please send us model and name of your device – we will add necessary archs.
* Only English language is supported yet (other of supported languages planned to be added later)

Rest of main functionality is identical to otherversions, as all versions (Windows, Android, iOS) are built on the same kernel , so only GUI is different.

How to install:

1. Enable Unknown sources installation: Settings->Security->Unknown sources
2. Open phone browser and load the application using this link:

Trial APK link 

Install the application. By default, it will work in demo mode that doesn’t require an adapter. Next steps describe how to connect an adapter.

3. Connect adapter to the OBDII port and wait until it is loaded.
3.1. Bluetooth
3.1.1. Enable Bluetooth in phone/tablet settings and pair the phone with the adapter. Current version of FORScan will work only with paired adapters!
3.1.2. In FORScan settings: disable Demo mode, select Connection type: Bluetooth 0, Bluetooth 1 or Bluetooth 2

3.1.3. Select your adapter (if not selected automatically)
Bluetooth 0 - recommended way. It is optimal for last Android versions (4.2.1 and higher). May not work with some china clones in Android versions below than 4.2.1.
Bluetooth 1 - try it if the option Bluetooth 0 doesn't work. May be preffered option for Android versions below than 4.2.1
Bluetooth 2 - an alternative implementation, may show the best results (performance and stability) on some devices with Android version below than 4.2.1. Should not work on last Android versions (4.2.1 and higher), although may still work on certain devices.

3.2. WiFi
3.2.1. Enable WiFi in phone/tablet settings and connect to the adapter (select it as a WiFi access point).
3.2.2. In FORScan settings: disable Demo mode, select Connection type: WiFi, make sure IP and port settings are correct (should be correct by default, but it worth to check)
4. Connect

How to use:

1. Application status
FORScan status is indicated using the application icon at the upper left corner.
BLUE – application disconnected
WHITE – connection started, FORScan Lites tries to connect to the adapter
ORANGE – the application has connected to the adapter and tries to connect to the vehicle now
GREEN – FORScan Lite has successfully connected and ready to work
RED – connection failed

Also, if communication with the adapter or vehicle is performed, a circular progress bar is available in the action bar.

User can track the connection status in more details if opens the Log page of the application.

2. The user interface is similar to iOS one, so until the Android manual is not ready, documentation for iOS version can be used (Documentation chapter on the site).

3. Important feature of the Android version: if FORScan is connected to the vehicle, it will maintain the connection unless user has disconnected it manually or Android OS has killed the application to safe resources. Even if the application is in the background and user works with another application, or the phone is in sleeping mode, connection to the adapter and vehicle will be still online. This is important difference from iOS version that “freezes” adapter connection if user has switched to another application.

4. Another important feature: if FORScan is connected to the vehicle and FORScan Lite is active, the phone/tablet will not go to sleeping mode.

Adapters:

The application was tested with OBDLink MX and two types of china Bluetooth clones. In theory there may be some china adapters that do not work.

Bluetooth performance: In our tests china clones show minimum ping in range of 20-35 ms depending on the adapter type, phone/tablet type and some other (unknown for us) things. OBDLink MX has minimum ping in range of 7-10 ms stable. It should be counted that WiFi and Bluetooth chips of all china clones are locked to 38400, in contrast to OBDLink MX that is locked to 115200. This makes significant difference in performance, especially noticeable on vehicles with fast CAN bus.

WiFi performance: there is no any specific (comparing with Windows and iOS versions).

How to report problems:

1. Please send us short problem description (ANR, crash etc) and specify your device name and model, as well as fail conditions.
2. Send us debug information
2.1. Enable Debug mode in FORScan Settings
2.2. Reproduce the problem and go to Vehicle section, touch service icon in the action bar and choose Send debug info and send mail using Gmail or Mail application (or any application that allows to share files), or Save debug info to save the logs to Documents/FORScan/log folder.

[Automate]

Thanks for releasing this! I like that the app shows the MAC address of the Bluetooth adapters. Since I have two adapters I can tell them apart.

[carlus]

The image!!:



I 've tried for 5 minutes and perfect. He has hit fast.

Environment:
- Galaxy Note 3 (Android 4.4.2)
- OBDLink MX Bluetooth
- Mazda CX7 Diesel

When I connected the application, the phone also had it connected with bluetooth car stereo.

I 'll tell you my impressions, but for now great.

As mentioned in paragraph "Known problems of this version:" only one problem, the application can not attach in an email, CSV log files.

Thank you very much to the team forscan!!!!

[int0x13]

Hello forscan team and users!
First i want to thank you for the hard work and efforts that lead to the release of the mobile versions. And especially about this Android version which i'm interested, because i have a Samsung Galaxy s2 (GT-I9100).
I've spent 2 or 3 hours yesterday to test it. I've tried most features and i saw no big problems. It's working great! Really happy about it. Fantastic job Forscan developers! The GUI is simple to use and convenient to use. It's the most important thing in a mobile app like that. We can browse through the recorded datalogging easily, it's much more efficient than the windows version in this particular task.
I was able to record datalogs in the app in background, and going back to Forscan Lite it was still working and record is done. It is very important because i have done 4 power bench using another application called PerfExpert (it's an application made to measure your car power and torque), and i wanted to record the Forscan PCM sensors during the power bench, to compare the 2 applications resultats and data. I will make another post that because i have some interrogation about that (the max torque measure by Forscan which is the "net engine torque" is not the same AT ALL that the torque measure by PerfExpert).
I'm using a bluetooth adapter to test this application, the bluetooth stack is working great, the time to connect is about 10-15s. I've noticed and very nice thing, when you stop the car the bluetooth connection is not lost when you switch on ignition (turn on the car again), Forscan lite is instant connected.
I can mention some little problems/improvements that i think about:

=>I have 20ms ping between OBD adapter and the phone (Forscan says into about "Information" window), it says fast latency, but when i'm checking about the actual latency with the throttle pedal PID and checking if it's refresh fast or not, i find it's pretty slow compared to the 20ms ping announced. It is not LIVE at all. I dont know if it's a matter of the bluetooth stack, physically or logically, Android limitation, OBD limitation...

now some point that could be improved (no bug or problems):
=>a "select all PIDs" feature that would fastend the tick of all PIDs into PID select dialog.
=>Ability to move/ajust the PIDs squared/instruments needles into the dashboard view
=>Ability to customize the graphics scale for each pid into the Graph view/ Or feature that automatically scale based on the values. I was checking the DP_DPF graph and the graphic line is all the time flat, because of the scale
=>A feature that could display for each PID the min/max/average, so we can find easily this information. And maybe later a feature that could WARNING you when some PID is OVER/UNDER a specified value and then send an alert through mail/sms
=>And later...very later a feature that could measure 0-100kmh 0-60mph. This feature would be called 0-100 bench.


Config:
phone:galaxy s2 (Android 4.1.2)
OBD adapter: China BT clone with ON/OFF switch (http://www.ebay.com/itm/Mini-ELM327-Blu ... 7675.l2557)
Car: Ford Focus MK2 2.0L TDCI 136 (2007)

[bluebear]

I'm an old user of Forscan windows version, but on android version, not working on my Ford Focus 2 2007 1.6 tdci 90 HP.
I'm attaching here some printscreens.
I try bluetooth 0,1,2.

On every other programs on android is working fine.

1

Screenshot_2015-04-19-15-03-20.png (116.32 KiB) Viewed 227332 times

2

Screenshot_2015-04-19-15-03-33.png (70.33 KiB) Viewed 227332 times

3

Screenshot_2015-04-19-15-13-12.png (61.75 KiB) Viewed 227332 times

[mx-user]

Hi,
my Report/Questions about Beta Testing
C-Max 1,6 TDCI, 2006
Android 4.4.2
Fonepad 7
OBDLink MX

1. Install APK - no problems

2. Bluetooth connection
at first some problems because I'm not understanding how to connect,
but after some different try's I learned to click the second symbol from the upper right.
Than Connection Type Bluetooth 0 works

3. Information - very good, VIN, Software versions etc. interesting information

4. Errors - works
Remark: dtc P2458-21 possible cause -"check the PCM for the latest calibration" what does that mean?
"Check that the pre and the post-catalyst sensors are operating correctly" here i know only the PID DPF Temperature.
What are the PID names of the pre and the post-catalyst sensors?

5. Table and Dashboard.
Her I have obvious a problem of understanding.
If I select e.g. PCM and than CANVP , how I confirm my selection?

Thanks in advance for help to Item 4 and 5

[Steve_v6_ghia_x]

After all that waiting I've been so busy I have not had a chance to test this software in my car yet but I can confirm that although this is written to run on arm processors it installs and boots without any issues on the 86x Intel Atom Quad Core Z3735 CPU so anyone with a hudl 2 or other 86x android device should have no problems.

Will report back on software and adaptor when I get a chance to test in car, hopefully later today.

[carlus]

More data:

Environment:
- Galaxy Note 3 (Android 4.4.2)
- OBDLink MX Bluetooth
- Mazda CX7 Diesel

My phone connected with three devices at the same time:
- Car stereo
- OBDlink
- Xiaomi My Band

Connection Type: Bluetooth 0.

Today (40 minutes of use), I sent a CSV file to my email account and everything has been perfect.

I believe that the application is running fine and I guess the next thing included in the application serlia the following.
- It should be possible to customize the PDI graphics (color, minimum and maximum range).

- Should an alarm to be included if a given PID reach a certain value. This point is very important as it has always interested me know when it is producing a regerenación the DPF and now could have the phone with the screen off (not consume much battery) and forscan notify me with an alarm when a PID I indicated that this remains a regeneration.

- A PID may be the GPS coordinate, because with this could know the exact position in which drive of the PIDS values ​​were obtained

- Should be able to change the recording frequency values ​​PIDS. For example, I'm recording 15 PIDS at a frequency of 30 per second. This makes a very large CSV file is generated and sometimes not be interested me such a high frequency, and I'd opt for frequencies of 1 per second about, eg when doing long trips.

I will continue with improvements and testing.

Otherwise, it is an essential tool and look forward to appear in Googe Play to buy it because I think that the work is being done with it is amazing.

Thank you very much. (applause)

[FORScan]

We are sorry, looks like we are unable to perform both correspondence processing and active development at once, either development or correspondence suffers. So:

First of all, thank you for all the feedback, here are some comments:

=>I have 20ms ping between OBD adapter and the phone (Forscan says into about "Information" window), it says fast latency, but when i'm checking about the actual latency with the throttle pedal PID and checking if it's refresh fast or not, i find it's pretty slow compared to the 20ms ping announced. It is not LIVE at all. I dont know if it's a matter of the bluetooth stack, physically or logically, Android limitation, OBD limitation...

20ms is minimal ping between FORScan and adapter, it is performed by sending ATI command to ELM and measuring response time. So it doesn't count module response time, that depends on bus type. ISO bus is about 150 ms, J1850 - 40 ms, CAN - 5-20 ms. Next, PIDs are requested one by one. So if you have 10 pids and ping is 20 ms, you will have 200 ms per cycle (so every PID of 10 will be updated once per 200 ms).

However if Android version works slower than Windows version with the same adapter, vehcile and set of PIDs, it may mean a problem that should be investigated.

Many ECUs support so called "block" mode of reading PIDs that allows to read PID data much faster. It was partially implemented in FORScan v1, in v2 we have removed it but are going to add in the future releases.

=>a "select all PIDs" feature that would fastend the tick of all PIDs into PID select dialog.

Are you sure it is a good idea? This is possible technically, but some modules have 100+ PIDs, so adding them all will slow communication down, and make the board not readable for a human (too much data).

=>Ability to move/ajust the PIDs squared/instruments needles into the dashboard view

Do you mean change order of PIDs in the board? It should work now in PIDs settings view with long tap on a PID. We plan to add a drag & drop button there.

=>Ability to customize the graphics scale for each pid into the Graph view/ Or feature that automatically scale based on the values. I was checking the DP_DPF graph and the graphic line is all the time flat, because of the scale

Min and Max functionality (to adjust upper and lower values of the Dashboard scale and graph) will be added. Actually it exists in iOS version, we have not added it to the first Android release just to save
some time...

=>A feature that could display for each PID the min/max/average, so we can find easily this information. And maybe later a feature that could WARNING you when some PID is OVER/UNDER a specified value and then send an alert through mail/sms
=>And later...very later a feature that could measure 0-100kmh 0-60mph. This feature would be called 0-100 bench.

OK.

[FORScan]

I'm an old user of Forscan windows version, but on android version, not working on my Ford Focus 2 2007 1.6 tdci 90 HP.
I'm attaching here some printscreens.
I try bluetooth 0,1,2.

On every other programs on android is working fine.

Screenshot_2015-04-19-15-03-20.png

Screenshot_2015-04-19-15-03-33.png

Screenshot_2015-04-19-15-13-12.png

As far as we can see, the adapter says it is ELM327 v2.1, so if your adapter is not Vgate iCar, it seems to be a problem with adapter, discussed on our forum:

http://forscan.org/forum/viewtopic.php?f=4&t=22#p840

You said you work with Windows version successfully, do you use another adapter for Windows/