Engineers Menü

Re: Engineers Menü

menu
Benutzeravatar
folder Do 31. Jan 2019, 18:28
So was die Installation von Apps (Netflix etc.) angeht gehts hier weiter:
https://www.goingelectric.de/forum/hyun ... 53-20.html
IONIQ Premium bestellt: 28.04. >> uvb. Lieferung: August/September >> 20.12.2017 >> 03.02.2018 >> 22.01.2018 Abholung
Anzeige

Re: Engineers Menü

menu
g4rb4g3
    Beiträge: 269
    Registriert: Do 4. Okt 2018, 20:43
    Hat sich bedankt: 20 Mal
    Danke erhalten: 68 Mal
folder Fr 1. Feb 2019, 22:32
TeamViewer Host funktioniert leider auch nicht. Lässt sich zwar installieren stürzt aber ab sobald man sich registrieren/anmelden möchte. Vermutlich weil TeamViewer auf Hochformat umschaltet...
Schade hätte das testen wesentlich vereinfacht...
Creator of the fabulous ABRPTransmitter for Ioniq BEV :)
Bild

Re: Engineers Menü

menu
jokercrs
    Beiträge: 6
    Registriert: Do 14. Feb 2019, 12:58
    Danke erhalten: 3 Mal
folder Do 14. Feb 2019, 13:07
I dont know if people have forgotten this amazing bit, but I've been trying to create some software for this radio as I just bought my Ioniq.
So far I have created a radio/MP3 player based on exoplayer2 library, meaning it is rather good. I have also managed to link it to the controls on the steeringwheel and the buttons under the LCD.
What I have not been able to do, is to register my app to the broadcasts that seems to be going, and there is a LOT of them. I dont assume anyone of you would know how to do this ?

Here is a TINY bit of it lasting about 100ms :

com.android.bluetooth E/bt-btif: pool(0):cur(0)tot(48), p(1):c(1)t(26), p(2):c(0)t(45), p(3):c(1)t(200)
02-14 10:31:50.270 1762-1776/com.lge.ivi.server V/IVIMessageManager: dispatchIVIMessage: id = 0x8449
02-14 10:31:50.270 1762-1776/com.lge.ivi.server V/IVIMessageManager: dispatchIVIMessage: id = 0x8449
02-14 10:31:50.270 1762-1776/com.lge.ivi.server V/IVIMessageManager: dispatchIVIMessage: id = 0x8449
02-14 10:31:50.270 2113-2113/? I/micomd: <- UartPort: \x8449 [29 00 04 00 00 01 92 bc ]
02-14 10:31:50.270 1683-2373/com.lge.ivi.coreserver V/IVIMessageService: handleIVIMessage(id=GW_EV_P_05(0x8449))
02-14 10:31:50.270 1683-2373/com.lge.ivi.coreserver V/DischargeWarningNotifier: [onIVIMessage] id:8449
02-14 10:31:50.270 1683-2373/com.lge.ivi.coreserver I/DischargeWarningNotifier: GW_EV_P_O5 msg:<GwEvP05(0x8449): crLdcPwrMonW=0x29, crMcuMotPwrAvnKw=0x0, crVcuDistEmptyAddKm=0x4, crBmsQcChgRemainedTimeMin=0x0, cfBmsStdCha=0x0(NONE), cfBmsStdCha120V=0x0(NONE), cfBmsFlt=0x0(NORMAL), crDatcAcnCompPwrConW=0x32, crVcuDistEmptyKm=0xaf>
02-14 10:31:50.270 1683-1683/com.lge.ivi.coreserver I/DischargeWarningNotifier: [handleMessage] msg:{ what=7 when=0 obj=<GwEvP05(0x8449): crLdcPwrMonW=0x29, crMcuMotPwrAvnKw=0x0, crVcuDistEmptyAddKm=0x4, crBmsQcChgRemainedTimeMin=0x0, cfBmsStdCha=0x0(NONE), cfBmsStdCha120V=0x0(NONE), cfBmsFlt=0x0(NORMAL), crDatcAcnCompPwrConW=0x32, crVcuDistEmptyKm=0xaf> }
02-14 10:31:50.270 1683-1683/com.lge.ivi.coreserver I/DischargeWarningNotifier: [onReceiveGwEvP05] info:<GwEvP05(0x8449): crLdcPwrMonW=0x29, crMcuMotPwrAvnKw=0x0, crVcuDistEmptyAddKm=0x4, crBmsQcChgRemainedTimeMin=0x0, cfBmsStdCha=0x0(NONE), cfBmsStdCha120V=0x0(NONE), cfBmsFlt=0x0(NORMAL), crDatcAcnCompPwrConW=0x32, crVcuDistEmptyKm=0xaf>
02-14 10:31:50.270 1683-1683/com.lge.ivi.coreserver I/DischargeWarningNotifier: [update]
02-14 10:31:50.270 1683-1683/com.lge.ivi.coreserver D/CoreConfigDataBase: getENV() : EV
02-14 10:31:50.270 1683-1683/com.lge.ivi.coreserver I/DischargeWarningNotifier: [stop]
02-14 10:31:50.270 1762-1762/com.lge.ivi.server V/NaviGreenCar: onIVIMessage: id=8449
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/NaviGreenCar: handleDTEOffEvent : GwEvP05 -> dte off :0, dte(fromCan) : 175, sDteKm : 175
02-14 10:31:50.270 1762-1762/com.lge.ivi.server V/EVPowerDisplay: onIVIMessage: id=8449
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: GW_EV_P_05
02-14 10:31:50.270 1762-1762/com.lge.ivi.server V/GreenCarSystemPopup: onIVIMessage: id=8449
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/GreenCarSystemPopup: GW_EV_P_05
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: MSG_SYSTEM_DATC_PE_03
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrVcuDistEmptyKm, oldValue : 175, newValue : 175
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCfVcuDteOff, oldValue : 0, newValue : 0
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCfBmsFstCha, oldValue : 0, newValue : 0
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrBmsQcChgRemainedTimeMin, oldValue : 0, newValue : 0
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrVcuDistEmptyAddKm, oldValue : 4, newValue : 4
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrMcuMotPwrAvnKw, oldValue : 0, newValue : 0
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrLdcPwrMonW, oldValue : 43, newValue : 41
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCrDatcAcnCompPwrConW, oldValue : 50, newValue : 50
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/EVPowerDisplay: updateCfBmsFstEvseFltAlram, oldValue : 0, newValue : 0
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/Config_Version: envType : EV, index : 3
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/GreenCarSystemPopup: MSG_SYSTEM_GW_EV_P_05
02-14 10:31:50.270 1762-1762/com.lge.ivi.server I/GreenCarSystemPopup: FAIL_HIGH_CHARGING : 0 , high_error__popup : trueFastCharge : 0
02-14 10:31:50.310 1111-1456/? I/audio_hw_primary: out write! [1][1][1][1][1]
02-14 10:31:50.360 2113-2113/? I/micomd: <- UartPort: \x8610 [03 85 63 00 00 07 6b 07 5b 0b 7b ]
02-14 10:31:50.360 2113-2113/? I/micomd: <- UartPort: \x86f1 [00 00 00 00 0a 00 28 8c ff 22 2e 00 02 1c ff ]
02-14 10:31:50.360 1683-2373/com.lge.ivi.coreserver V/IVIMessageService: handleIVIMessage(id=PERIODIC_AVN_STATUS(0x8610))
02-14 10:31:50.360 1683-2373/com.lge.ivi.coreserver V/DischargeWarningNotifier: [onIVIMessage] id:8610
02-14 10:31:50.360 1683-2373/com.lge.ivi.coreserver V/IVIMessageService: handleIVIMessage(id=(0x86f1))

Re: Engineers Menü

menu
g4rb4g3
    Beiträge: 269
    Registriert: Do 4. Okt 2018, 20:43
    Hat sich bedankt: 20 Mal
    Danke erhalten: 68 Mal
folder Fr 15. Feb 2019, 09:28
I guess thats because com.lge.ivi.server provides a service and doesn't send system wide broadcasts.
You have to bind to the service somehow to receive them. Maybe this will help you:
https://developer.android.com/guide/com ... d-services
But I'm not sure if you can bind to the service since you don't have an interface for it since it seems like they have used AIDL.
https://developer.android.com/guide/components/aidl
The client must also have access to the interface class, so if the client and service are in separate applications, then the client's application must have a copy of the .aidl file in its src/ directory (which generates the android.os.Binder interface—providing the client access to the AIDL methods).
Creator of the fabulous ABRPTransmitter for Ioniq BEV :)
Bild

Re: Engineers Menü

menu
Benutzeravatar
folder Fr 15. Feb 2019, 12:44
Das ist ein Android based IVI (In-Vehicle Infotainment), welches auf Qt basiert.
https://wiki.qt.io/About_Qt
IONIQ Premium bestellt: 28.04. >> uvb. Lieferung: August/September >> 20.12.2017 >> 03.02.2018 >> 22.01.2018 Abholung

Re: Engineers Menü

menu
jokercrs
    Beiträge: 6
    Registriert: Do 14. Feb 2019, 12:58
    Danke erhalten: 3 Mal
folder Fr 15. Feb 2019, 15:02
g4rb4g3 hat geschrieben:
Fr 15. Feb 2019, 09:28
I guess thats because com.lge.ivi.server provides a service and doesn't send system wide broadcasts.
You have to bind to the service somehow to receive them. Maybe this will help you:
https://developer.android.com/guide/com ... d-services
But I'm not sure if you can bind to the service since you don't have an interface for it since it seems like they have used AIDL.
https://developer.android.com/guide/components/aidl
The client must also have access to the interface class, so if the client and service are in separate applications, then the client's application must have a copy of the .aidl file in its src/ directory (which generates the android.os.Binder interface—providing the client access to the AIDL methods).
Thanks, this was much needed insight and great tips. It would make a lot of sense if they did things this way.
I'm sure it'll be a lot of work to peek into it - but I'm confident there is a way. There's always a way. :)

-TJ / Team Avalaunch

Re: Engineers Menü

menu
g4rb4g3
    Beiträge: 269
    Registriert: Do 4. Okt 2018, 20:43
    Hat sich bedankt: 20 Mal
    Danke erhalten: 68 Mal
folder Fr 15. Feb 2019, 22:41
Seems like I found a way to talk to the GreenCarManager...
Dateianhänge
20190215_222029.jpg
Creator of the fabulous ABRPTransmitter for Ioniq BEV :)
Bild

Re: Engineers Menü

menu
jokercrs
    Beiträge: 6
    Registriert: Do 14. Feb 2019, 12:58
    Danke erhalten: 3 Mal
folder Sa 16. Feb 2019, 09:52
Very nice !! :D I have been reading through the "The Mobile Application Hacker's Handbook" to find a way through this, and it does point out a lot of weaknesses, but you seem to have gotten a lot further than I have already.

Do you bind to the service in order to access the broadcasts ?

-TJ / Team Avalaunch

Re: Engineers Menü

menu
g4rb4g3
    Beiträge: 269
    Registriert: Do 4. Okt 2018, 20:43
    Hat sich bedankt: 20 Mal
    Danke erhalten: 68 Mal
folder Sa 16. Feb 2019, 09:56
Read your PN 😉 I've sent you much more information then I posted here. Including a file I don't want to post here...
Creator of the fabulous ABRPTransmitter for Ioniq BEV :)
Bild

Re: Engineers Menü

menu
NatroN
    Beiträge: 152
    Registriert: So 3. Jun 2018, 23:39
    Hat sich bedankt: 3 Mal
    Danke erhalten: 11 Mal
folder Sa 16. Feb 2019, 17:19
Awesome g4rb4ge - not bad not bad.
Can you check - is the android alive while charging, like the CanBus is?
Anzeige
Antwortenedit build arrow_drop_down

Zurück zu „IONIQ - Infotainment“

Gehe zu arrow_drop_down
  • Vergleichbare Themen
    Antworten
    Zugriffe
    Letzter Beitrag