Emu black, v3 3.061, 3.064 (updated for this retest)
EDL-1 1.25 and 1.26 (tried both)
Issue
None of the devices ever see EMULOGGER on the eDash app Rescan screen
All devices see EMULOGGER on the native bluetooth pairing screens
Pairing and clicking them does nothing, EDL stays flashing the blue led
Using a Fire 7 tablet, attempting to use RealDash on it works, blue led goes solid
Havent been able to install eDash on it due to issues on the store
On the ONN device (android 11), i always get the "Permission denied, Bluetooth and Location permissions are required to scan and connect to BLE devices” error
Seems android 11 has a different permission and the app is not seeing it, permission screen on the android settings does not show a Nearby devices or bluetooth permission to be granted to any app.
EDL file, yes the mac and BT mod values are empty
EDL Firmware: 1.26
Bootloader version: 2
Bluetooth module:
MAC addres:
Ive spent several hours playing around the devices and versions etc, no luck.
Device: iPhone 14 Pro
iOS: 17.2
ECU: EMU Black Plug-In ECU for 1.8T
Connection: EDL-1
Issue: Can’t find the device in the app, but the phone is connected to it via Bluthooth
EDL-1 firmware is 1.26
ECU firmware is 3.064
I have formatted the sd and deleted the file several times, even after reflashing 1.25 and 1.26 trying to get them to populate.
Sometimes i get no data at all, most times i get the partial empty strings i posted. If i highlight the text in the file, i can see empty spaces on both variables (18 spaces on the mac, 50 spaces on the BT module)
if theres a way to enable extended logging/output, im willing to flash and post the log
Flashing 1.25 gives me this
EDL Firmware: 1.24
Bootloader version: 2
Bluetooth module:
MAC addres:
Flashed 1.22 and got this:
EDL Firmware: 1.22
Bluetooth module firmware version: +BOLUTEK Firmware V2.2, Bluetooth V2.1
Bluetooth module mac addres: AB:53:86:34:3A:01
Flashed 1.26 again, same as before, lost the variables.
@DIMITRIS_ECUMASTER@LopinRD -
About problem in Android 11.
There is different permissions model in Android 11 than in newer Android versions. Developers are going to fix it in the next app version
OH, ive had this EDL for a few years so let me ask, this version of the EDL logger hardware does not support the BLE protocol, if i get a new EDL it would work?
If support for it will be added afterwards might be a good idea to make a note on the manual about the EDL logger versions so people are aware and if support is coming to just hold for a bit.
Thanks for the response, let me know if i can test/help in any other way.
Hi! I recently installed the edash app on my Atoto S8 to test it out. I’ve a problem with the bluetooth conection :
“Permission denied. Bluetooth and location permission are required to scan and connect to BLE device”
I tried to grant permissions through the Android applications section, but the option to grant it doesn’t appear.
While we’re on the subject, I’d like to ask about the signal range of the EDL-1 module.
Currently, I have to position it with the SD card slot facing the back of the ATOTO device At a distance of 5 centimeters, because otherwise the signal is too weak and it can’t connect It to use the emudash app. This makes accessing the SD card impossible, as I would have to disassemble Part of the dashboard to access it.
I don’t know if it’s a problem with the emudash application or the EDL-1 module. I hope this improves with the edash app.
There are millions of units that are android 10 being used every single day. Can we please get version 10 of android to work this is one of the reasons why I bought emu MU black.
I like my RealDash quite frankly, I would rather have E --dash work since the last three versions really struggled in this category . This is also for aToto S8.Thank you
At the moment, eDash officially supports Android 11 and newer, which covers the large majority of active Android devices. This decision is mainly related to Bluetooth and system permission changes introduced in newer Android versions, which significantly improve connection stabilityand security. Supporting older Android versions increases development complexity and can negatively impact BLE communication reliability.
We understand that some Android head units are still based on Android 10. We are reviewing possible options, however at this stage we cannot guarantee support for Android 10.
