[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto

Do you want the app to incorporate it's own stats (See post #1127)

  • Yes

    Votes: 18 90.0%
  • No

    Votes: 2 10.0%

  • Total voters
    20
  • Poll closed .
Search This thread

rogfitz

New member
Jan 19, 2010
3
1
I have the latest 3.6b version but everytime I try to set TPMS the app crashes. Can it be my car does not provde this info? I can't find any PID that looks like TPMS data.
 
  • Like
Reactions: ziddey

r0okie

Member
May 27, 2020
8
2
What I did with mine was download mqb-pm and "open" the APK as an archive and take some of the dials/backgrounds and use that when setting up. Its the last setting in the individual gauge settings. Just make sure to set gauge style as clear.

Nick - I opened mine up and can't find any graphics (I used 7zip to extract the files)

edit - Never Mind. Performance.Monitor.v0.88B\res\drawable
 

binary_boy01

Senior Member
Nov 28, 2009
238
61
Samsung Galaxy S20 FE
Has anyone faced this weird issue? I have obd2aa installed, dpi set to 110 and fermata auto as player. Every time after i disconnect my phone from car, after using aa with this setup, I'm unable to make phonecall from my phone (not over bluetooth). Since i really need aa to work and phone as well I'm forced to ditch ond2aa until a fix will be found. Thank you for your help
 

Nick_Gl

Senior Member
Oct 14, 2009
117
35
Has anyone faced this weird issue? I have obd2aa installed, dpi set to 110 and fermata auto as player. Every time after i disconnect my phone from car, after using aa with this setup, I'm unable to make phonecall from my phone (not over bluetooth). Since i really need aa to work and phone as well I'm forced to ditch ond2aa until a fix will be found. Thank you for your help
Yeah, I encountered the same problem with one plus 8 pro with Verizon sim. I tried everything, changing permissions, notification settings, cleared storage and cache for obd2aa, phone, call management, services, everything. No luck tho. Ended up just getting rid of it as "the main app" and only run it for gauges only inside android auto.
 

binary_boy01

Senior Member
Nov 28, 2009
238
61
Samsung Galaxy S20 FE
Yeah, I encountered the same problem with one plus 8 pro with Verizon sim. I tried everything, changing permissions, notification settings, cleared storage and cache for obd2aa, phone, call management, services, everything. No luck tho. Ended up just getting rid of it as "the main app" and only run it for gauges only inside android auto.
Hi there,

Thqnks for your answer.However, is there any chqnce ti run only gauges inside aa? I'm asking cause anytime i run it, crashes my phone and this happens to a s20fe. Previous phone was a huawei mate9, stock android 9 without any issues.
 
  • Like
Reactions: Fredriksonn

mverhagen

New member
Aug 3, 2021
2
0
HI,

I just purchased Torque Pro and the OBD2AA app. Inside Torque I can see all dials working perfectly, including GPS speed. On Android Auto with OBD2AA, most dials seem to work fine, EXCEPT the GPS Speed dial. This stays on 0. The GPS accuracy and other dials all work fine, so there doesn't seem to be any problem with the GPS NMEA data received from the OBD2.

The OBD2AA settings are set to NOT use the GPS from the phone, but even with that setting enabled the GPS speed dial still doesn't work in OBD2AA.

Another issue is that the "day/night mode override" doesn't seem to work. My head unit still uses the headlight setting (Suzuki Jimny 2021).

Any way I can provide more debugging info to help sort this issue?
 
HI,

I just purchased Torque Pro and the OBD2AA app. Inside Torque I can see all dials working perfectly, including GPS speed. On Android Auto with OBD2AA, most dials seem to work fine, EXCEPT the GPS Speed dial. This stays on 0. The GPS accuracy and other dials all work fine, so there doesn't seem to be any problem with the GPS NMEA data received from the OBD2.

The OBD2AA settings are set to NOT use the GPS from the phone, but even with that setting enabled the GPS speed dial still doesn't work in OBD2AA.

Another issue is that the "day/night mode override" doesn't seem to work. My head unit still uses the headlight setting (Suzuki Jimny 2021).

Any way I can provide more debugging info to help sort this issue?
For the dial issue, start up Torque manually before plugging into your head unit, and it will likely work. I've had this issue with a vehicle specific dial since I set it up. Occasionally it works fine but normally I have to start Torque first.
 

mverhagen

New member
Aug 3, 2021
2
0
For the dial issue, start up Torque manually before plugging into your head unit, and it will likely work. I've had this issue with a vehicle specific dial since I set it up. Occasionally it works fine but normally I have to start Torque first.
I just tried this, and indeed, the GPS related dials work, but ONLY when the Torque App is open AND active on the phone. The moment I turn the phone screen off, the dials stop working. This kind of defeats the purpose of having a head unit. My phone is connected via USB and in a dash-bag, so I really can't have my phone screen on...

Is there anything that can be done to workaround this issue?

Also the day/night mode issue would be very nice to get working. The daylight sensor on the Jimny is way to sensitive, so the lights go on/off all the time (when in sun/shade/sun/etc). For that reason I have covered the sensor with a sticker (so it is always night mode, for which I turned the display brightness high). If the OBD2AA day/night mode would work on sunset/rise it would mean my display could still go dim after sunset, even though the daylight sensor is always covered.
 

Speckbarbie

Member
Aug 8, 2017
8
0
OnePlus Nord
Hey guys. I bought OBD2AA and Torque Pro. I just want to set a different DPI on my Android Auto HU. I don't have a OBD BT device, so I tried both steps just without an OBD BT Device.
When I connect my Phone, which is an OnePlus Nord with Android 11, Android Auto wont bootup on my HU.

EDIT: I solved my problem by reinstalling AA und also left the Beta Program for AA. But now when I change the DPI for example, I get a Connection 16 Error from AA. Google said, turn off duplicate apps on Xiaomi phones, but I'm on a OnePlus Nord. So I can duplicate apps but i don't use this feature. Any ideas?

Hope anyone can help me.
 
Last edited:

megatoast

New member
Aug 25, 2021
1
0
Hey guys, I've got a wierd issue where I cant get my oil temp to show in OBD2AA on my head unit.

I've had to setup a custom PID in Torque as the default one doesn't get any data, and this is working fine in Torque, however when I use it in OBD2AA it just reads 0 constantly while everything else is working. I think it may be some kind of bug with it being a custom entered PID? I'm not sure

Has anyone else ran into this issue?

I'm on an unrooted Realme 7 5G if that's relevant

EDIT: SOLVED, I went into my phones battery optimization settings and turned off any restrictions to Torque and OBD2AA and it's decided to work :)
 

Attachments

  • Screenshot_2021-09-03-17-05-00-12_b9c66f921be6b9ee18febc2ed6906538.jpg
    Screenshot_2021-09-03-17-05-00-12_b9c66f921be6b9ee18febc2ed6906538.jpg
    765.1 KB · Views: 52
  • Screenshot_2021-09-03-17-05-06-14_b9c66f921be6b9ee18febc2ed6906538.jpg
    Screenshot_2021-09-03-17-05-06-14_b9c66f921be6b9ee18febc2ed6906538.jpg
    779.1 KB · Views: 53
  • Screenshot_2021-09-03-17-06-30-45_222575c0a0ebae8132a5fcfa40986ced.jpg
    Screenshot_2021-09-03-17-06-30-45_222575c0a0ebae8132a5fcfa40986ced.jpg
    244.6 KB · Views: 55
Last edited:

TheAmazingDave

Senior Member
Jun 20, 2011
192
40
San Jose
First off, @Emil Borconi your app is amazing. Thank you very much for the hard work and frustration you must have put in to put this together.

That said, I'm hoping to get some help from the community here. I've been struggling for hours now trying to get my custom-skinned gauges to work appropriately. I've been using Emil's instructions in post 1,069 but I just can't get the needles to point to the correct reading. I have no idea what I'm doing wrong.

For example, I can't get the attached intake air temp gauge to display correctly. I have the gauge set for a minimum number of 50 and a max of 150. I have set the starting point so the needle points to 50. The attached gauge face has a sweep of 270 degrees from 50 to 150, and I have the arch length entered as 270.

From what I understand, that is all correct. However, the gauge displays consistently low compared to the reading in Torque, and when I came back to the car earlier after coming out of the market, the intake had heatsoaked and Torque showed a reading of over 200 degrees, but the needle in ODB2AA was around 130.

Does anyone know what I'm doing wrong? Also, I can't figure out what Arch Indent setting does, and/or if it's related to my problem. I've tried different values but nothing seems to change.
 

Attachments

  • iat gauge.png
    iat gauge.png
    66.5 KB · Views: 35
  • Screenshot_20210913-231630.png
    Screenshot_20210913-231630.png
    189.1 KB · Views: 33
  • Screenshot_20210913-231637.png
    Screenshot_20210913-231637.png
    229.7 KB · Views: 33

TheAmazingDave

Senior Member
Jun 20, 2011
192
40
San Jose
Well I gave up and just re-made my faces with different scales that start at zero. Actually like it better now, since the displayed gauges are tiny on my head unit and were hard to read. Here's what I came up with.

1631678194808.png


not sure why the screen gets squished in the screenshot, but it appears correctly on the display. I need to redo the AFR though because the 13 is in the wrong spot.
 

lukdut

New member
Sep 15, 2021
3
0
Hi maybe you can help me with the following questions. I have an Alfa Stelvio and my motivation around obd2aa is mostly to get the Android Auto split screen via change of DPI settings. I would also like to remove the tab limit. My questions are:

1) do I need the OBD adapter/reader to change the DPI setting and remove tab limit or is torque pro + odb2aa app enough ?
2) if yes - my Alfa seems to have a security gateway on ODB port which means you probably cannot write to the port (or at least things like error messages cannot be canceled) - do you need to write to the ODB port to change the above settings?

sorry if those are obvious questions but I am not an expert in the field.

thanks, Luke
 

1qazwsx4

Senior Member
Sep 19, 2011
652
378
New Zealand
Hi maybe you can help me with the following questions. I have an Alfa Stelvio and my motivation around obd2aa is mostly to get the Android Auto split screen via change of DPI settings. I would also like to remove the tab limit. My questions are:

1) do I need the OBD adapter/reader to change the DPI setting and remove tab limit or is torque pro + odb2aa app enough ?
2) if yes - my Alfa seems to have a security gateway on ODB port which means you probably cannot write to the port (or at least things like error messages cannot be canceled) - do you need to write to the ODB port to change the above settings?

sorry if those are obvious questions but I am not an expert in the field.

thanks, Luke
I think to change your headunits DPi it usually requires an app to "request" full screen which is often achieved by apps using root. I know that using an AAWireless device (made and sold by this dev) enables you to force split screen meaning you can run two apps on screen. As for using OBD2/torque if it's just reading data so should work fine - sounds abit odd that you couldn't use OBD2 to clear codes etc that would get annoying.
 

lukdut

New member
Sep 15, 2021
3
0
I think to change your headunits DPi it usually requires an app to "request" full screen which is often achieved by apps using root. I know that using an AAWireless device (made and sold by this dev) enables you to force split screen meaning you can run two apps on screen. As for using OBD2/torque if it's just reading data so should work fine - sounds abit odd that you couldn't use OBD2 to clear codes etc that would get annoying.
Hi thanks for the response. I am aware of the AAwireless and have actually preordered the device but the shipment date seems to be quite distant ; I thought that obd2aa would have the ability to change the DPI setting and based on some other discussion I read that seems to be done on the headunit so I thought it is via the OBD2 connector facilitated via obd2aa app so that it is done properly - am I wrong?
 
Hi thanks for the response. I am aware of the AAwireless and have actually preordered the device but the shipment date seems to be quite distant ; I thought that obd2aa would have the ability to change the DPI setting and based on some other discussion I read that seems to be done on the headunit so I thought it is via the OBD2 connector facilitated via obd2aa app so that it is done properly - am I wrong?
Changing the DPI doesn't need an OBD adapter, just needs to be requested by the device running AA. You should be able to change it without using torque or an OBD adapter.
 
  • Like
Reactions: lukdut

Top Liked Posts

  • There are no posts matching your filters.
  • 56
    Update 30.11.2022
    End of life and open source.

    Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source.

    Code is accessible: https://github.com/borconi/obd2aa

    I will like to thank all of those who supported this project.

    App Requirement
    • Torque Pro
    • OBD2 Reader
    • Android Auto compatible headunit or at least a copy of the Headunit Reloaded App (see signature).


    This app will have limited functionality if you are using Android Auto on a your phone, the only functions you will be able to use is to see are notification about the speed cameras and street card!
    Gauges and torque data will NOT work!

    Previous XDA purchases can be reclaimed here: https://www.b3itlabs.com/download.php

    How to purchase:
    1. Visit: https://www.b3itlabs.com/prod.php?id=2

    Instructions on how to get it running:

    Option 1 - Will work on any phone & car/headunit combination, however the following features won't: - AutoPlay Music, 6 Tap limit remover, DPI change

    1. After installing the app from XDA Labs, sign up for beta testing here: https://play.google.com/apps/testing/uk.co.boconi.emil.obd2aa and update the app
    2. Once app is updated, make sure you disable auto-update in PlayStore then please uninstall it and reinstall it from XDA Labs.
    3. With your screen unlocked, plug in the phone to the car, when prompted which app to use make sure you select "Android Auto"


    Option 2 - Might NOT work on some device combination (for sure it won't work on Xiaomi phones), but if this method works all functions of the app are available
    1. Install
    2. Make sure you do not have any other 3rd party app Android Auto app installed.
    3. Open the app and hopefully it will be quite self explanatory on how to set it up (choose colours, set gauge number, etc)
    4. Open Android Auto (on the phone), go to About, tap the "About Android Auto" header 10 times, once you are a developer from the 3 dotted right corner menu select "Start Headunit Server" (ROOT users can skip this step!)
    5. Close Android Auto
    6. MAKE SURE YOUR SCREEN IS UNLOCKED and connect to the car, when prompted which app to use select "OBD2AA" and always (this needs to be done one time only) - If you are a HUR user select Android Auto and always! (If you do not see the prompt to chose, please go to settings -> apps -> all apps -> Google Play Services -> Clear Defaults and then try again)
    7. Select the last tab on the right, by pressing it again you should see an app selector and choose OBD2AA
    8. Give it a bit of time to start pulling the data from Torque.

    Change log
    Version 3.2 and 3.3 released 04/11/2018

    • Fix "drunk" map effect on Sync 3 units
    • Fixed rooted devices not being able to start headunit server.
    • Added option to change DPI for your screen!
    • Added option to auto play music on start
    • Added option to select default start screen.

    Version 3.1 releases 26/08/2018
    • Compatibility fix for Pie devices.
    • Tap limit remover now working on all device
    • Tap limit remover allows Maps to be searchable even when driving.
    • Can be used for those who have problem with the parking brake wire.
    • Freeze issues fixes.
    Important notes

    Version 3.0 releases 05/07/2018

    • Compatibility fix for AA 3.0 and above.
    • Added option for overriding 6 tap limits
    • Added option for Bluetooth Audio output.
    Important notes

    Thanks to @slash_m_a_x for the support offered on this.

    - Some users have reported choppy audio when using the app, this will mainly be due to the speed of the phone, the buffer on the car/headunit and other factors which are out of my control, if that is the case and you cannot use the app please feel free to contact me for a refund.
    - Bluetooth Audio output might not work on all devices, it does depend how the car/headunit handles the Bluetooth. There will be devices which completely disable A2DP/Bluetooth capabilities of the car when Android Auto is running. In this case all the sound will be heard from the phone speaker rather then the car speakers.
    - Tap limit will be disabled only for cars/headunits which are equipped with a GPS.
    - In rare cases it can happen that after unplugging the phone from the headunit you will see a message which says that you are still connected to Android Auto, simply Force Stop the Google Play Services.
    - You always need to make sure that Headunit Server is running on the phone (unless you have root), if the icon bothers you simply hide it.



    Change log
    Version 2.0 releases 17/01/2018

    • Added new layout option
    • Added styled gauged
    • Option for custom background on each gauge.
    • Option for custom needle on each gauge
    • Removed integration for CamSam/Blitzer.de (fully integrated now)
    • Possibility to change needle color
    • Possibility to adjust arch (indent, position, length) when using custom bg
    • Separated speed camera settings
    • Option to only download speed cam db over Wifi
    • Fixes for min/max value
    • Speed camera warnings over car speaker (Thanks @martoreto for the how-to)
    • Street info card
    • Added French translation (Credit to @fbike for doing the translation)
    • Added Danish (Credit to @Gunde for doing the translation)
    • Added Finnish (Credit to @Pyrres for doing the translation)
    • Added Spanish (Credit to @madabase for doing the translation)
    • Added Italian (Credit to @ilgaspa for doing the translation)


    Version 1.6a - releases 03/10/2017
    • Fixed negative input for min/max values
    • Code cleanup
    • Added Greek language (credit to @sosimple for translating)

    Version 1.6 - releases 29/09/2017
    • Fixes for custom PIDS
    • Fixes on Graphics rendering.
    • Fixed overlapping text
    • Fixed PSI/BAR conversion
    • Enhanced the gauge style.
    • Different approach for torque data pulling.
    • Moved to service should start work automatically when connected to the car
    • Added Supports PID alarms from Torque.
    • Added Toggle/Collapse layout for Pid settings.
    • Added Preview button with random data
    • Added Option to toggle units display
    • Added notification cleanup on exit
    • Added translation for DE,HU,RO (Credit to @FormelLMS for DE)
    • Added import/export setting option
    • Added option for colored text
    • Added TPMS option/screen
    • Added option to override car's headlights based on day/night
    • Added warning screen if nothing is configured to prevent black screen with no information.
    • Added more settings and move them to separate Settings options.
    • Added customizable background
    • Added search for PIDs
    • Added Support for Heads-Up notification
    • Added Speed camera warnings (powered by CamSam Plus)

    Supported settings/Features:
    • 3 x Colors for each gauge
    • Text color
    • Toggle needle, arch,units,scale,decimal and text for each gauge.
    • Variable number or gauges ( 1 - 15 )
    • Set warning limit for each gauge (percentage). This will be calculated relative to the given PID max value which is retrieved from Torque at runtime.
    • Possibility to set gauge in reverse mode. (example fuel tank)
    • Units will be converted automatically based on your Preferences in Torque
    • TPMS Screen (if you have PID's for TPMS data)
    • Possibility to use custom background/needle for each gauge
    • Low Fuel warning
    • Warm Engine warning
    • Speed Camera Heads Up Warning
    • Option to Overwrite Headlights state based on calculated sunset/sunrise


    How to use it?
    Open app and select each PID you want to display on your screen, adjust the number or gauges you want to see adjust the preference for each PID. If you want to use custom background/needle and interested on how to, please read HERE

    Locking Pid values
    On some PID's Torque reports wrong min/max values, by default if while using the application a reported value is higher/lower than the initially reported range, the app will adjust the range to the new values. However in some cases this is not desired and you will like to specify manually what is the min and max value for the give PID. In this case, simple edit the minimum/maximum for the pid and they will become locked, meaning the app won't make any adjustments.
    By editing, it means you have to change the min or max value, the lock is triggered by the first keypress on this input fields.
    The lock will be automatically removed when you select a different PID for the same gauge.

    Preferences menu
    • Alternative pulling - Only enable this option if you have difficulties getting gauges updated, it uses an old deprecated method of obtaining data so should not really be used.
    • Enable debugging - Only enable it if you have problems with the app and I requested you to collect a bug report, otherwise it will spam the logs for no reason.
    • Automatically start Torque on Android Auto - Nothing to explain here :)
    • Launch FartKontrol on start - launches a Danish Speed Camera app (useless outside Denmark)
    • Custom Background (any background you will like to use instead of the black color)
    • Demo - When enabled random data is generated for the PID's just to see how things will look (in case you do not have an OBD2 adapter), so don't enable it.
    • Pid Alarms section. You can set up a low level fuel warning (displayed as a heads up notification) and a notification when the engine is warmed up. There a several PID options for both of this, pretty self explanatory.

    TPMS Settings
    - You set up the 4 PID's for TPMS, this will be used to display the tyre pressure values on the TPMS screen inside Android Auto

    Speed Camera
    • Show current street card - Displays information about current street (name and speed limit if know). This information is updated once in 5 seconds and at a minimum distance of 200 meters so it's not 100% accurate it's more for general information.
    • Enable speed camera warnings - This will enable the app to display speed camera warning when driving, like any app which does this it relies on a database, which means it does NOT guarantee that it will warn you of all the cameras, and it might also produce false warnings. All options are pretty self explanatory.

    Export & Import
    - Allows you to export your current app configuration file which can later be imported (grate way of saving time of re-doing everything) after a clean install or so. The format use for Export & Import is JSON so if you want you can manually edit/adjust the values. Please see following post for more details about the sturcture/value/meanings


    Permissions
    • Read notification permission - Only required so the app can read the notifications from CamSam and display them on AA scren
    • Locations - Only required if you want the app to overwrite the day/night theme based on sunset/sunrise
    • Storage - Only needed if you want to use your personal image as a background and/or planning to import/export settings

    Can I create my own layout for the gauges?
    - Yes, see instructions below:

    Here is an example of the XML structure required, once you created the XML please send it over by email to borconie@gmail.com and I will include it in the next build.

    Code:
          <FrameLayout
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            android:tag="wrapper_layout">
            <!-- Left column -->
    
            <View
                android:layout_width="226dp"
                android:layout_height="226dp"
                android:layout_gravity="center_vertical|start"
                android:tag="gauge_2"
                />
    
            <!-- Middle column -->
            <View
                android:layout_width="match_parent"
                android:layout_height="match_parent"
                android:layout_gravity="center"
                android:tag="gauge_1" />
    
            <!-- right column -->
    
            <View
                android:layout_width="226dp"
                android:layout_height="226dp"
                android:layout_gravity="center_vertical|end"
                android:tag="gauge_3" />
    
        </FrameLayout>

    Important
    • Each view must contain a tag, which is formated like in the example, where the number corresponds to the Gauge number from the setting screen.
    • The layout which wraps everything together must have a tag called: wrapper_layout
    You are free to use any Layout you want, except ScrollView.


    How to produce bug report?

    Step 1 you need to enabled debugging in OBD2AA app, then follow this instruction set:

    2. Enabling Developer Mode
    1. Open Settings > About phone.
    2. Scroll down to the Build number.
    3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
    4. Return to the Settings menu and select Developer options.
    5. At the top of the screen, make sure 'Developer options' is set to On (green).
    6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
    7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.

    3. Capturing a Bug Report
    It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
    1. Hold the Power button down until the menu appears.
    2. Select Take bug report. and wait for the device to capture the bug report.
    3. Tap the 'Bug report captured' notification when it appears.
    4. Share the bug report. (I recommend to email it to yourself.)
    5. Download the bug report to your computer.
    6. Send the bug report by email to borconie@gmail.com


    I have decided to open up my software, meaning I have made the source code available on GitHub, but it's only available for personal use, and you are not allowed (under any form) to redistribute your own version of the app. You can download and compile it yourself if you wish to do so, and you can implement your own changes for your own personal use, but you cannot create clones of the software which you redistribute under your own name. Source can be found here: https://github.com/borconi/obd2aa.
    Due to the fact that there are some irresponsible developers out there, who created video apps for moving cars, which was one of the main reasons Google blocked 3rd party apps, I won't be updating the code on github any more, to try to prevent those developers to use my technique to overcome the limits. If you are developing a 3rd party app and you will like to know more about how I have done this, you are always welcome to contact me. If your project is something useful, I will be more then happy to share things with you.

    This does not mean it is now a free app and apk can be freely shared!
    17
    Thanks all, this is what keeps me going :) don't worry I haven't given up, finally today I had my exams (passed both) so I will be hitting the road in a couple of hours (1600 miles or 2700km with a few stopovers) so I should be home by Tuesday evening. Once home I'm sure I will find some time for more development.
    17
    I made some really good progress, with the app.
    All you guys with non-rooted phone can expect a public beta this week.
    16
    Non-Root users a gimps of hope for you too as well, today I have managed to move forward from where I was stuck since February with the hack, so hopefully I will be able to make further progress and get it back online in the next couple of weeks for everybody.
    16
    Hi guys. Back in the UK and I'm working on it. Currently still stuck at the same point (SSL related) I will update you as soon as I can, at least testing is much easier now.