• Welcome to N-cars.net - the largest Hyundai N car forum. Check out the model specific sections below and scroll down for country specific forums. Scroll down for i30 N, Ioniq 5 N, i20 N, Veloster N and Kona N forums! Check out the i30 N Bible Here!

Radio Engineer Mode / Android

Toggle sidebar Toggle sidebar
Bu11eT said:
Have you thought about running a DSP? The issue with just running an AMP is that the equalizer built into the radio is not doing proper equalizing. It's just shifting the frequency curve and distorting it even more. The AMP is then obv amplifying that bad quality and your sound output will never sound super clean.

I could only solve this issue by running a proper DSP and to control the tweeters directly from it and not from the head unit
Click to expand...
I'm running a 4 channel active system. Although my amp is not a DSP it's particular functionality is really close to one(high/low pass filters from 50hz-4khz). My objective was to separate the inputs for the custom midbass and tweeters and blend them, replacing the stock crossovers for additional tuning potential.

I found that this head unit's main issue is processing of the Bluetooth/aux in. The outputs are almost pure distortion because of the internal head unit signal chain. The android auto/probably apple car play(not tested myself) outputs are CLEAN. As always your mileage may vary
 
  • Like
Reactions: Bu11eT
Bu11eT said:
Have you thought about running a DSP? The issue with just running an AMP is that the equalizer built into the radio is not doing proper equalizing. It's just shifting the frequency curve and distorting it even more. The AMP is then obv amplifying that bad quality and your sound output will never sound super clean.

I could only solve this issue by running a proper DSP and to control the tweeters directly from it and not from the head unit
Click to expand...

If you use your built in HU, you only can equalize the signal from the HU. If there is a way to get a raw audio signal, digital or analog from before it is equalized within the original HU please let me know, I'd be very interested in this!
 
Teddy said:
If you use your built in HU, you only can equalize the signal from the HU. If there is a way to get a raw audio signal, digital or analog from before it is equalized within the original HU please let me know, I'd be very interested in this!
Click to expand...
You can 'reset' or better said clean up the signal using a DSP. For example the Mosconi DSPs come with a default cleanup map for our cars, which cleans up the frequency distortion from the HU.
 
Bu11eT said:
Have you thought about running a DSP? The issue with just running an AMP is that the equalizer built into the radio is not doing proper equalizing. It's just shifting the frequency curve and distorting it even more. The AMP is then obv amplifying that bad quality and your sound output will never sound super clean.

I could only solve this issue by running a proper DSP and to control the tweeters directly from it and not from the head unit
Click to expand...
Also I tried running my aftermarket amp off of pure signal as an experiment disconnecting the hi-inputs, using aux in directly. The difference of measurements between that and Android auto with bass 0 midrange -10 highs -9/-10 is insignificant. This applies to my case and my speakers/measurement rig.

If you'd want to evolve this further I'd recommend a rooted dedicated android auto phone with UAPP. This is my choice. You could have room correction files,EQ filters, additional gain control while using your main phone for Bluetooth calls simultaneously.
 
Trailerhead04 said:
Also I tried running my aftermarket amp off of pure signal as an experiment disconnecting the hi-inputs, using aux in directly. The difference of measurements between that and Android auto with bass 0 midrange -10 highs -9/-10 is insignificant. This applies to my case and my speakers/measurement rig.

If you'd want to evolve this further I'd recommend a rooted dedicated android auto phone with UAPP. This is my choice. You could have room correction files,EQ filters, additional gain control while using your main phone for Bluetooth calls simultaneously.
Click to expand...
That's not so easy unfortunately. It's not just cleaning up a distorted curve by switching some settings. The guys at Mosconi had actual sound engineers work multiple weeks with the car to develop a base map that completely cleans up the frequency distortion. The HU is doing some weird stuff including changing frequency settings when changing volume as well as modulating frequencies when using the equalizer or fading tool.
 
Last edited:
  • Wow
Reactions: jeroenvde
Bu11eT said:
That's not so easy unfortunately. It's not just cleaning up a distorted curve by switching some settings. The guys at Mosconi had actual sound engineers work multiple weeks with the car to develop a base map that completely cleans up the frequency distortion. The HU is doing some weird stuff including changing frequency settings when changing volume as well as modulating frequencies when using the equalizer or fading tool.
Click to expand...
I have observed that frequency response changes weirdly with the HU fader and EQ. Speed dependant volume ruins things further. Also is the i30N correction curve available on all Mosconi processors or is it limited to a certain range of products?
 
Trailerhead04 said:
I have observed that frequency response changes weirdly with the HU fader and EQ. Speed dependant volume ruins things further. Also is the i30N correction curve available on all Mosconi processors or is it limited to a certain range of products?
Click to expand...
Should be available on their PICO lineup. But contact the dealer if they have the map for the N available to flash it onto the device!
 
Given you can easily update the headunit software now, has anyone taken a look into the files?


There's a password protected zipfile, which contains update.zip, i can only assume this is the OS files.
Aside from that in other folders i can see json and xml files.

One Json files has config lines for max volume, split screen and a bunch of other settings.
 
  • Like
Reactions: Jajodu
Here's a bunch of configurable items in productinfo.json found in NaU\2018_20_i30_N_AU\BIN\variant\AUS

Replace AUS with your country code.

I'm going to test increasing the max volume value and see if that applies

JSON: 
{
    "MetaInfo": {
        "version": "1.0.0.6",
        "updateDate": "2020.10.22",
        "basePlatform": "STD5",
        "baseRegion": "AUS"
    },
    "System": {
        "bSupportSplitScreen": 0,
        "bStandaloneSplitScreen": 0,
        "bUseBaiduEngine": 0,
        "frontSessionWindowSize": [
            800,
            480
        ],
        "rearSessionWindowSize": [
            800,
            480
        ],
        "frontWidgetWindowSize": [
            396,
            395
        ],
        "rearWidgetWindowSize": [
            836,
            720
        ],
        "frontSubPreviewSize": [
            640,
            640
        ],
        "frontSubPreviewRect": [
            1280,
            631,
            640,
            0
        ],
        "maxVolumeValue": 45,
        "minVolumeValue": 0,
        "defaultQuiteModeVolume": 7,
        "defaultTalkModeVolume": 20,
        "bUseDelayedVRAction": 0,
        "bSupportTMCIndcator": 0
    },
    "Common": {
        "toastPopupTimeOut": 3000,
        "bStopMarqueeByDrivingRegulation": 0,
        "bUseUnifiedMultiLanguage": 0,
        "vcrmVersion": "v.20.3.2.0",
        "guestRestriction": 0,
        "mapFlyerType": 1,
        "bEngineeringModeListFlag": 1,
        "bMainMenuMultiTabStyle": 1
    },
    "Map": {
        "mapScrollTriggerInterval": 50,
        "mapLongPressTriggerInterval": 1000,
        "mapPosAutoSyncInterval": 15000,
        "mapOverviewWhileStopInterval": 15000,
        "mapModeFixLevel": 11,
        "frontJunctionViewRect": [
            458,
            480,
            800,
            149
        ],
        "rearJunctionViewRect": [
            458,
            480,
            800,
            2
        ],
        "frontRouteOverviewRect": [
            105,
            390,
            478,
            112
        ],
        "rearRouteOverviewRect": [
            80,
            388,
            502,
            69
        ],
        "frontStopOverviewRect": [
            105,
            390,
            765,
            40
        ],
        "rearStopOverviewRect": [
            159,
            360,
            735,
            69
        ],
        "subPreviewOverviewRect": [
            1280,
            600,
            1920,
            20
        ],
        "recentDestinationPopupRect": [
            103,
            610,
            1280,
            89
        ],
        "splitScreenOverviewRect": [
            116,
            626,
            524,
            96
        ],
        "frontDTEFitAreaRect": [
            70,
            415,
            790,
            65
        ],
        "rearDTEFitAreaRect": [
            70,
            415,
            790,
            65
        ],
        "evWidgetDTEFitAreaRect": [
            10,
            227,
            395,
            0
        ],
        "rearAirviewRect": [
            150,
            150,
            1240,
            560
        ],
        "frontTrafficDetailRect": [
            50,
            440,
            342,
            50
        ],
        "rearTrafficDetailRect": [
            150,
            670,
            700,
            50
        ],
        "bMapUseCallSyncRendering": 0,
        "bUseOverviewOnSS": 1,
        "bUseLocationSharingOverviewOnSS": 1,
        "bUseStopOverviewIcon": 0,
        "bNeedChangeViewport": 1,
        "bNeedInitViewport": 0,
        "bNeedKeepScrollMode": 1,
        "bUseSingleTheme": 1,
        "mapScaleBarVisibleInterval": 5000,
        "fuelWarningTimeoutLimit": 300000,
        "bMapScaleBarAlwaysVisible": 0,
        "bUseTronviewOnWidget": 0,
        "trafficDetailInfoWidth": 335,
        "bShowMultiSymbolsOnPreview": 0,
        "viewModeSequenceOnNormal": [
            1,
            0,
            2,
            1
        ],
        "viewModeSequenceOnSS": [
            1,
            0,
            2,
            6,
            7,
            1
        ],
        "bSupportTron": 0,
        "bUseSingleTron": 0,
        "mapPitchAnimationInterval": 500,
        "mapPitchAnimationMoveAngle": 8,
        "bMoveCenterByGuideMode": 1,
        "bUseRouteEditPreview": 1,
        "mapBasePointShiftWidth": 0,
        "mapFrontWidgetBasePoint": 0,
        "mapRearWidgetBasePoint": 0,
        "bMapScaleBarVisibleOn3DView": 0,
        "supportViewModeAR": 1,
        "supportAirviewMode": 0,
        "showScrollCursorOnTrafficDetail": 0,
        "bNeedMoveDetailViewBySS": 1,
        "detailGuidanceWidth": 335,
        "mapFrontWidgetArabicShiftWidth": 0,
        "bSupportDayNightViewMode": 0,
        "bSupportTouchSubPreview": 1,
        "bSmoothAnimation": 0,
        "bPreviewViewmodeTypeHeadingup": 1,
        "mapRouteOptionHeightLine3": 41,
        "mapSSFitAreaMarginHeight": 0,
        "mapVerticalBasePoint": 105,
        "mapWidgetVerticalBasePoint": 65,
        "bFrontWidgetTheme": 0,
        "mapMycarWidth": 0,
        "btrafficDetailPreview": 1,
        "bFrontWidgetMainView": 1,
        "bFrontWidgetCTTLine": 0,
        "bUse3DbuidingOnSS": 0,
        "bUse3DbuildingOnHomeWidget": 1
    },
    "Route": {
        "destinationValidLevel": 6,
        "closeDestinationDistance": 70,
        "bSessionIndependentRoute": 0,
        "maxWaypointCount": 3,
        "bMultiRoadSupport": 0,
        "maxAvoidRoadCount": 10,
        "confirmRouteinOverviewInterval": 5000,
        "bOverviewAutoConfirm": 1,
        "bUseNetStatusPopup": 0,
        "bLevelSettingPopup": 0,
        "bAutoMapLevelSet": 0,
        "bSpecificWaypointPopup": 0,
        "bInvalidPointPopup": 1,
        "bUseOnlineRouteing": 1,
        "roadInfoUpdateInterval": 1000,
        "bUseAvoidFailPopupImage": 0,
        "bUseNonExistingICOut": 1,
        "hiPassReCalculateInterval": 5000,
        "bRouteEditDefaultWaypointFlag": 1,
        "bTollFareIconSupport": 0,
        "waypointListStyle": 1,
        "bNeedCheckOverviewButtonHide": 0
    },
    "Guide": {
        "overSpeed2ndWarningPercent": 110,
        "m_maxLaneCountOnExpandMap": 10,
        "m_maxLaneCountWithSS": 10,
        "m_maxLaneCountOnDetailedView": 7,
        "tbtReturnTime": 10000,
        "bTbtPoiSearchSupport": 1,
        "bDetailViewWithTBT": 0,
        "bFirstGuidanceWithTBT": 0,
        "bTBTSupportRear": 0,
        "bDetailedViewSupportRear": 0,
        "bGuideVirtualMap": 1,
        "bRoadNumberSymbolSupport": 0,
        "bRoadSymbolSupport": 0,
        "bottomTextToggleTime": 5000,
        "bottomTextToggleWatingTime": 1000,
        "bUseMarqee": 1,
        "congestionPopupDistance": 1000,
        "timeRestrictPopupTimer": 600000,
        "bLocationSharingSupport": 0,
        "bTrafficEventBtnSupport": 0,
        "tbtTypeList": [
            0,
            2,
            1
        ],
        "bottomToggleItemMain": [
            0,
            1
        ],
        "bottomToggleItemSS": [
            0,
            1,
            8
        ],
        "bUseTripInfo": 0
    },
    "Search": {
        "schdefResultMaxCount": 50,
        "schdefRadiusforPoiCategories": 10000,
        "maximumRecommendCount": 5,
        "maxInputSearchCommon": 100,
        "maxInputEditName": 32,
        "maxInputEditAddress": 32,
        "bHomeWorkPrevDisplayOnlyExist": 0,
        "schdefPoiCategoriesTab": 1,
        "schdefHyundaiDealerShipClassCode": [
            "0x2080"
        ],
        "schdefKiaDealerShipClassCode": [
            "0x2100"
        ],
        "schdefGenesisDealerShipClassCode": [
            "0x2680"
        ],
        "hmiFavoriteStyle": 1,
        "hmiListAct": 1,
        "categoryListImageLocation": 0,
        "onliseSchCP": 0,
        "backWhenDeletePrevDest": 0,
        "isPlaceSearchOnlyCurrent": 0,
        "isPrevDestPopupStyle": 1,
        "isSupportFavorite123": 1,
        "isSupportRecommendFuel": 0
    },
    "Traffic": {
        "defaultTrafficOnRouteStatus": 0,
        "trafficCategoryLists": [
            6,
            5,
            3,
            13,
            9,
            1,
            8
        ],
        "categoryFilterNeedTransitionBack": 0,
        "liveParking2LineSupport": 0
    },
    "Setting": {
        "GPSInfoPointSize": 42,
        "GPSInfoIcoGpsImageSize": 279,
        "GPSInfoCircleSize": 261,
        "GPSTimerNeed": 0,
        "settingMenuStyle": 2,
        "configSaveStyle": 1
    },
    "Engineer": {}
}
 
  • Like
Reactions: Bu11eT, Jajodu and NULLOBANDITO
Hey guys, scanned through this post and have tried all options to get into the engineering mode, although my car is the 1.6T 2020 Nline, no the N spec. Any pointers to gain access?
 
I'm a new i30N FL possessor and here are a few things I would love to mode about the new infotainment system:

1. Remove the welcome/recommendation screen. It's really frustrating especially since it won't let me press the Confirm button only after a random amount of time (another frustrating thing). Sometimes I can press confirm after 5 seconds, other times I have to wait like 10-15 seconds.
2. Remove the Hyundai right widget at all while in Android Auto/Apple Carplay and try to make them full screen.
3. Have the Hyundai right widget display a selectable default widget, for example I would want to always show my Oil Temp, but whenever I start the car it turns to the G-Force thing...
4. Whenever I'm in Android Auto/Apple Carplay and siwtch from Bluetooth Audio to Radio (by pressing MODE on the steering wheel), instead of just showing a quick notification it literally switches all the infotainment to Radio. That only happens when on Android Auto/Apple Carplay, if you do this while looking at the Hyundai Map, it works fine.
 
RasherN said:
I'm a new i30N FL possessor and here are a few things I would love to mode about the new infotainment system:

1. Remove the welcome/recommendation screen. It's really frustrating especially since it won't let me press the Confirm button only after a random amount of time (another frustrating thing). Sometimes I can press confirm after 5 seconds, other times I have to wait like 10-15 seconds.
2. Remove the Hyundai right widget at all while in Android Auto/Apple Carplay and try to make them full screen.
3. Have the Hyundai right widget display a selectable default widget, for example I would want to always show my Oil Temp, but whenever I start the car it turns to the G-Force thing...
4. Whenever I'm in Android Auto/Apple Carplay and siwtch from Bluetooth Audio to Radio (by pressing MODE on the steering wheel), instead of just showing a quick notification it literally switches all the infotainment to Radio. That only happens when on Android Auto/Apple Carplay, if you do this while looking at the Hyundai Map, it works fine.
Click to expand...
Send a screenshot of your software version.
 
Is the head unit on the i30N the same as the standard i30? Part 96550G4100PMP?
Just software makes the difference? Or is it physically different?

There is an i30 wreck available, and I was thinking of potentially getting a spare head unit for cheap, just in case.
 
Clemet said:
Is the head unit on the i30N the same as the standard i30? Part 96550G4100PMP?
Just software makes the difference? Or is it physically different?

There is an i30 wreck available, and I was thinking of potentially getting a spare head unit for cheap, just in case.
Click to expand...
It would make sense for the manufacturer to rationalise production by using the same part. Look at partsouq.com and check part numbers.
 
  • Like
Reactions: ClarkyAU
You must log in or register to reply here.

Top Bottom