Infotainment Specifications just for giggles and grins (the Tablet), way tech post...

Cash Traylor

Cash Traylor

Well-Known Member
About that little Android Tablet screen on our dash...

General Specifications
Manufacturer MITSUBISHI ELECTRIC
Model MY16ADA
Android version 4.2.2; 64; SDK17
CPU 4 cores; ARMv7 Processor rev 9 (v7l) tegra; Max: 900.0 MHz; Min: 450.0 MHz
Display 800 x 480; DPI: 160; Evaluated Size: 5.8"
Touch screen Multitouch 4 points
GPU NVIDIA AP; NVIDIA Corporation; OpenGL ES-CM 1.1; OpenGL ES 2.0 16.05001
RAM 1024 MB (988 MB available)
Flash 8 GB (7.031 GB actual); 931.513 GB (see memory map tab)
Communications
Phone None
WiFi ak7738
USB Host Yes
Bluetooth Yes
GPS Yes
Advanced Features
Front camera open(cameraId = 0) is Unsupported.
Back camera No
Sensors Corrected Gyroscope Sensor (Google Inc.); range: 0...4.276; resolution: 0 (0.004%); power: 6.1mA;
Rotation Vector Sensor (Google Inc.); range: 0...1; resolution: 0 (0%); power: 6.1mA;
Gravity Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Linear Acceleration Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Vibrator No
Supported languages 51; Afrikaans; Amharic; Arabic; Belarusian; Bulgarian; Bengali; Catalan; Czech; Danish; German; Greek; English; Spanish; Estonian; Persian; Finnish; Filipino; French; Hebrew; Hindi; Croatian; Hungarian; Indonesian; Icelandic; Italian; Japanese; Korean; Lithuanian; Latvian; Marathi; Malay; Norwegian; Dutch; Polish; Portuguese; Romansh; Romanian; Russian; Slovak; Slovenian; Serbian; Swedish; Swahili; Tamil; Thai; Filipino; Turkish; Ukrainian; Vietnamese; Chinese; Zulu
Battery Technology: null; Voltage: 0
SD Version: 1.1 7

KERNEL: Linux version 3.1.10+ (jenkins@NDYWY3861584) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 14 13:20:49 JST 2018
CODENAME: REL
Mainboard: Andromeda
BRAND: Honda
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: vcm30t30
DISPLAY: 1.F1A2.34
FINGERPRINT: Honda/Andromeda/vcm30t30:4.2.2/1.F1A2.34/64:user/release-keys
HARDWARE: vcm30t30
ID: 1.F1A2.34
TAGS: release-keys

Processor : ARMv7 Processor rev 9 (v7l)
processor : 0
BogoMIPS : 1799.32
processor : 1
BogoMIPS : 1799.32
processor : 2
BogoMIPS : 1799.32
processor : 3
BogoMIPS : 1799.32
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 9
Hardware : vcm30t30
Revision : 58c800
Serial : 0000000000000000

RAM: 1024 MB (988 MB available)

tegra-nor: 64.000MB
System RAM: 988.000MB
fbmem: 8.000MB
fbmem: 8.000MB


Flash: 8 GB (7.031 GB actual); 931.513 GB

mmcblk0: 7.031 GB
sda: 931.513 GB
mtdblock: 0.087 GB


Yes, this is sometimes entertaining for a number of reasons.

The build.prop is interesting. I will post a reference version for our car later as it is slightly different than what I found in other Honda variants (Accord, Civic, etc - ones that have a knob).

Cheers,

Cash
 
Hey Cash

Try and find an up-to-date FAST Android with new version and see if we can replace ours !!

Just got a new Amazon Fire 10" HD-
crisper; faster; and I made it near fully Android (from the Amazon Fire version it comes with) for $150 Cnd.....

Cash Traylor said:
About that little Android Tablet screen on our dash...

General Specifications
Manufacturer MITSUBISHI ELECTRIC
Model MY16ADA
Android version 4.2.2; 64; SDK17
CPU 4 cores; ARMv7 Processor rev 9 (v7l) tegra; Max: 900.0 MHz; Min: 450.0 MHz
Display 800 x 480; DPI: 160; Evaluated Size: 5.8"
Touch screen Multitouch 4 points
GPU NVIDIA AP; NVIDIA Corporation; OpenGL ES-CM 1.1; OpenGL ES 2.0 16.05001
RAM 1024 MB (988 MB available)
Flash 8 GB (7.031 GB actual); 931.513 GB (see memory map tab)
Communications
Phone None
WiFi ak7738
USB Host Yes
Bluetooth Yes
GPS Yes
Advanced Features
Front camera open(cameraId = 0) is Unsupported.
Back camera No
Sensors Corrected Gyroscope Sensor (Google Inc.); range: 0...4.276; resolution: 0 (0.004%); power: 6.1mA;
Rotation Vector Sensor (Google Inc.); range: 0...1; resolution: 0 (0%); power: 6.1mA;
Gravity Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Linear Acceleration Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Vibrator No
Supported languages 51; Afrikaans; Amharic; Arabic; Belarusian; Bulgarian; Bengali; Catalan; Czech; Danish; German; Greek; English; Spanish; Estonian; Persian; Finnish; Filipino; French; Hebrew; Hindi; Croatian; Hungarian; Indonesian; Icelandic; Italian; Japanese; Korean; Lithuanian; Latvian; Marathi; Malay; Norwegian; Dutch; Polish; Portuguese; Romansh; Romanian; Russian; Slovak; Slovenian; Serbian; Swedish; Swahili; Tamil; Thai; Filipino; Turkish; Ukrainian; Vietnamese; Chinese; Zulu
Battery Technology: null; Voltage: 0
SD Version: 1.1 7

KERNEL: Linux version 3.1.10+ (jenkins@NDYWY3861584) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 14 13:20:49 JST 2018
CODENAME: REL
Mainboard: Andromeda
BRAND: Honda
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: vcm30t30
DISPLAY: 1.F1A2.34
FINGERPRINT: Honda/Andromeda/vcm30t30:4.2.2/1.F1A2.34/64:user/release-keys
HARDWARE: vcm30t30
ID: 1.F1A2.34
TAGS: release-keys

Processor : ARMv7 Processor rev 9 (v7l)
processor : 0
BogoMIPS : 1799.32
processor : 1
BogoMIPS : 1799.32
processor : 2
BogoMIPS : 1799.32
processor : 3
BogoMIPS : 1799.32
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 9
Hardware : vcm30t30
Revision : 58c800
Serial : 0000000000000000

RAM: 1024 MB (988 MB available)

tegra-nor: 64.000MB
System RAM: 988.000MB
fbmem: 8.000MB
fbmem: 8.000MB


Flash: 8 GB (7.031 GB actual); 931.513 GB

mmcblk0: 7.031 GB
sda: 931.513 GB
mtdblock: 0.087 GB


Yes, this is sometimes entertaining for a number of reasons.

The build.prop is interesting. I will post a reference version for our car later as it is slightly different than what I found in other Honda variants (Accord, Civic, etc - ones that have a knob).

Cheers,

Cash
Click to expand...
 
JohnT said:
Hey Cash

Try and find an up-to-date FAST Android with new version and see if we can replace ours !!

Just got a new Amazon Fire 10" HD-
crisper; faster; and I made it near fully Android (from the Amazon Fire version it comes with) for $150 Cnd.....
Click to expand...


I am actually researching options for this. I would prefer to grab a Clarity headunit from a salvaged car on ebay that is "for parts" so I can dig into the mainboard a bit. I don't really want to take mine apart for that long, my car is my daily driver. It actually isn't hard from a "hardware" standpoint, it's the software. I am in the process (as others are) for finding a method to grap a nandroid backup of the infotainment system, similar to a TWRP installation. Just have not had a lot of time lately. May work on it now as a lot of us are now finding ourselves at home, learning how to "home school" our kids that are on a longer spring break than planned.

Anyone interested or currently doing the same feel free to join in! I am not that smart....

I will post what I find in this thread, likely with links to results in XDA.

Cheers,

Cash
 
Pulled down the installed packages list today during a backup (going to play with platform migration on an androidVM with simulated hardware connections). Deleted most of the stuff I know I installed to make this an "OEM" package list, however it is chicken and the egg. You can't get the list without the hack, and the hack may install some modules I didn't track at the time by date (or requires manual date comparison and well, I am too low on beer for that task).

Again, this is complete tech/geek nonsense really at this point as it is useless info. However, I posted this entire thread as useless info from the start. The folks that can really do something with this have for themselves, and will never publish it for fear of us mere mortals bricking our cars with such dangerous knowledge. However, I have pushed the limits successfully thus far and am working in the "do this, if you want, but tread no further for beyond which there be dragons list."
I am fairly certain that the following is possible with little risk other than voiding the tablet warranty.
  • Online Honda Hack with basic "Clarity" settings
  • Most of anything you can do that is built into Honda Hack, including apps from HH's built in app manager
  • Most "non-root" apps are safe. They may not work but likely will not break anything, may be slow....
  • The software DSP Sound improvement seems to work reliably. Has been tested pretty thoroughly in other models on the MY16ADA platform.
  • Where the dragons are sleeping are in the build.prop and kernel settings. There is currently no "direct" way to unlock the bootloader to install a custom recovery that could permit a nandroid/image system backup to help protect against bricking.
  • The "factory restore" is pretty limited, there are two levels that I have used and documented here (the XDA forum is unreadable at this point), however that depends on the boot loader functioning and it at least booting to the recovery menu.
Where I would like to go:
  • The CPU is "underclocked" and appears to be done that way for thermal control considering it is likely to operate in a hot car. However that doesn't mean it could not be bumped up with adequate thermal throttling controls or additional cooling (just point the vent down at it...) I don't mind it running slow when hot but speeding up once it cools down.
  • There is a memory space issue that could be optimized as the current zram solution appears to be optimized for extreme reliability - reboots are not deal breakers if they happen twice as fast.
Here is the package file list mentioned above. Very boring stuff, but I think there are a lot of us stuck at home right now so....

******************************************************************************************
com.android.backupconfirm-20200321-223705
com.android.browser-20200321-223613
com.android.calculator2-20200321-223626
com.android.calendar-20200321-223629
com.android.certinstaller-20200321-223654
com.android.contacts-20200321-223748
com.android.defcontainer-20200321-224458
com.android.deskclock-20200321-223657
com.android.galaxy4-20200321-223610
com.android.gallery3d-20200321-224136
com.android.htmlviewer-20200321-224217
com.android.inputdevices-20200321-224242
com.android.inputmethod.latin-20200321-223359
com.android.keychain-20200321-224244
com.android.location.fused-20200321-224133
com.android.magicsmoke-20200321-224255
com.android.music-20200321-224416
com.android.musicfx-20200321-224419
com.android.noisefield-20200321-223624
com.android.packageinstaller-20200321-224500
com.android.phasebeam-20200321-224502
com.android.phone-20200321-224403
com.android.providers.applications-20200321-224529
com.android.providers.calendar-20200321-223637
com.android.providers.contacts-20200321-223801
com.android.providers.downloads.ui-20200321-224055
com.android.providers.downloads-20200321-224052
com.android.providers.drm-20200321-224057
com.android.providers.media-20200321-224257
com.android.providers.settings-20200321-224605
com.android.providers.telephony-20200321-224414
com.android.providers.userdictionary-20200321-224708
com.android.provision-20200321-223708
com.android.quicksearchbox-20200321-224526
com.android.settings-20200321-224533
com.android.sharedstoragebackup-20200321-223710
com.android.systemui-20200321-224626
com.android.vpndialogs-20200321-224811
com.android.wallpaper.holospiral-20200321-223712
com.android.wallpaper.livepicker-20200321-224253
com.android.wallpaper-20200321-223459
com.honda.displayaudio.navi-20200321-224154
com.honda.displayaudio.whitelist-20200321-223511
com.honda.telematics.core-20200321-224643
com.keramidas.virtual.ACCOUNTS-20200321-223337
com.keramidas.virtual.APP_WIDGETS-20200321-223509
com.keramidas.virtual.BLUETOOTH_PAIRINGS-20200321-223611
com.keramidas.virtual.COUNTRY_LANG_TZ-20200321-223804
com.keramidas.virtual.DATA_USAGE-20200321-223906
com.keramidas.virtual.WALLPAPER-20200321-224812
com.keramidas.virtual.WIFI_AP_LIST-20200321-224812
com.mitsubishielectric.ada.app.acuralink-20200321-223339
com.mitsubishielectric.ada.app.aircon-20200321-223348
com.mitsubishielectric.ada.app.androidauto-20200321-223351
com.mitsubishielectric.ada.app.antitheft-20200321-223503
com.mitsubishielectric.ada.app.appmode-20200321-223714
com.mitsubishielectric.ada.app.avplayer-20200321-223523
com.mitsubishielectric.ada.app.camera-20200321-223640
com.mitsubishielectric.ada.app.carplay-20200321-223648
com.mitsubishielectric.ada.app.dalauncher-20200321-223813
com.mitsubishielectric.ada.app.dasettings-20200321-223834
com.mitsubishielectric.ada.app.dealerdiag-20200321-224022
com.mitsubishielectric.ada.app.developerdiag-20200321-224039
com.mitsubishielectric.ada.app.ecotripcomputer-20200321-224102
com.mitsubishielectric.ada.app.emergency-20200321-224105
com.mitsubishielectric.ada.app.energymanagement-20200321-223720
com.mitsubishielectric.ada.app.etc-20200321-224113
com.mitsubishielectric.ada.app.externaldisplay-20200321-224122
com.mitsubishielectric.ada.app.filemanager-20200321-223508
com.mitsubishielectric.ada.app.hft-20200321-224504
com.mitsubishielectric.ada.app.letdiag-20200321-224246
com.mitsubishielectric.ada.app.mirrorlink-20200321-224400
com.mitsubishielectric.ada.app.preshipmentdiag-20200321-224518
com.mitsubishielectric.ada.app.systeminfoservice-20200321-223739
com.mitsubishielectric.ada.app.systemupdate-20200321-224634
com.mitsubishielectric.ada.app.taskmanager-20200321-224640
com.mitsubishielectric.ada.app.usbcert-20200321-224706
com.mitsubishielectric.ada.app.voiceportal-20200321-224733
com.mitsubishielectric.ada.app.wifi-20200321-224816
com.mitsubishielectric.ada.appservice.acuralink-20200321-223345
com.mitsubishielectric.ada.appservice.appmanagerservice-20200321-223513
com.mitsubishielectric.ada.appservice.appmodeapservice-20200321-223516
com.mitsubishielectric.ada.appservice.avapservice-20200321-223602
com.mitsubishielectric.ada.appservice.camera-20200321-223646
com.mitsubishielectric.ada.appservice.carplayapservice-20200321-223651
com.mitsubishielectric.ada.appservice.clocksync-20200321-223703
com.mitsubishielectric.ada.appservice.compassservice-20200321-223746
com.mitsubishielectric.ada.appservice.diag-20200321-224048
com.mitsubishielectric.ada.appservice.emergency-20200321-224108
com.mitsubishielectric.ada.appservice.errormanager-20200321-224111
com.mitsubishielectric.ada.appservice.externaldisplay-20200321-224119
com.mitsubishielectric.ada.appservice.hft-20200321-224208
com.mitsubishielectric.ada.appservice.hudapservice-20200321-224219
com.mitsubishielectric.ada.appservice.linkmanager-20200321-224251
com.mitsubishielectric.ada.appservice.navigation-20200321-224441
com.mitsubishielectric.ada.appservice.phonecoordination-20200321-224512
com.mitsubishielectric.ada.appservice.powermanager-20200321-224516
com.mitsubishielectric.ada.appservice.raspapservice-20200321-224521
com.mitsubishielectric.ada.appservice.roadtovehicle-20200321-224116
com.mitsubishielectric.ada.appservice.screenshot-20200321-224523
com.mitsubishielectric.ada.appservice.sensormonitor-20200321-224531
com.mitsubishielectric.ada.appservice.siriefm-20200321-224608
com.mitsubishielectric.ada.appservice.strgsw-20200321-224623
com.mitsubishielectric.ada.appservice.telematics-20200321-224654
com.mitsubishielectric.ada.appservice.unitinfomanager-20200321-224703
com.mitsubishielectric.ada.appservice.vehiclecoordination-20200321-224710
com.mitsubishielectric.ada.appservice.vehicleinfomanager-20200321-224717
com.mitsubishielectric.ada.appservice.videomanager-20200321-224720
com.mitsubishielectric.ada.appservice.voiceportalap-20200321-224809
com.mitsubishielectric.ada.appservice.wifi-20200321-224819
com.mitsubishielectric.ada.framework.cpucomservice-20200321-223810
com.mitsubishielectric.ada.framework.mcservice-20200321-224356
com.mitsubishielectric.ada.framework.speech.g2p2-20200321-224231
com.mitsubishielectric.ada.framework.speech.g2p-20200321-224222
com.mitsubishielectric.ada.framework.speech.tts-20200321-224240
com.mitsubishielectric.ada.framework.speech-20200321-223519
com.mitsubishielectric.ada.framework.vehicledbmanager-20200321-224713
com.mitsubishielectric.ada.util.vehiclerw-20200321-223744
com.mxtech.videoplayer.ad-20200321-224421
ngi.ask.jcr-20200321-224059

****************************************************************************************
Cheers,

Cash
 
Cash Traylor said:
About that little Android Tablet screen on our dash...

General Specifications
Manufacturer MITSUBISHI ELECTRIC
Model MY16ADA
Android version 4.2.2; 64; SDK17
CPU 4 cores; ARMv7 Processor rev 9 (v7l) tegra; Max: 900.0 MHz; Min: 450.0 MHz
Display 800 x 480; DPI: 160; Evaluated Size: 5.8"
Touch screen Multitouch 4 points
GPU NVIDIA AP; NVIDIA Corporation; OpenGL ES-CM 1.1; OpenGL ES 2.0 16.05001
RAM 1024 MB (988 MB available)
Flash 8 GB (7.031 GB actual); 931.513 GB (see memory map tab)
Communications
Phone None
WiFi ak7738
USB Host Yes
Bluetooth Yes
GPS Yes
Advanced Features
Front camera open(cameraId = 0) is Unsupported.
Back camera No
Sensors Corrected Gyroscope Sensor (Google Inc.); range: 0...4.276; resolution: 0 (0.004%); power: 6.1mA;
Rotation Vector Sensor (Google Inc.); range: 0...1; resolution: 0 (0%); power: 6.1mA;
Gravity Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Linear Acceleration Sensor (Google Inc.); range: 0...19.613; resolution: 0 (0%); power: 6.1mA;
Vibrator No
Supported languages 51; Afrikaans; Amharic; Arabic; Belarusian; Bulgarian; Bengali; Catalan; Czech; Danish; German; Greek; English; Spanish; Estonian; Persian; Finnish; Filipino; French; Hebrew; Hindi; Croatian; Hungarian; Indonesian; Icelandic; Italian; Japanese; Korean; Lithuanian; Latvian; Marathi; Malay; Norwegian; Dutch; Polish; Portuguese; Romansh; Romanian; Russian; Slovak; Slovenian; Serbian; Swedish; Swahili; Tamil; Thai; Filipino; Turkish; Ukrainian; Vietnamese; Chinese; Zulu
Battery Technology: null; Voltage: 0
SD Version: 1.1 7

KERNEL: Linux version 3.1.10+ (jenkins@NDYWY3861584) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 14 13:20:49 JST 2018
CODENAME: REL
Mainboard: Andromeda
BRAND: Honda
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: vcm30t30
DISPLAY: 1.F1A2.34
FINGERPRINT: Honda/Andromeda/vcm30t30:4.2.2/1.F1A2.34/64:user/release-keys
HARDWARE: vcm30t30
ID: 1.F1A2.34
TAGS: release-keys

Processor : ARMv7 Processor rev 9 (v7l)
processor : 0
BogoMIPS : 1799.32
processor : 1
BogoMIPS : 1799.32
processor : 2
BogoMIPS : 1799.32
processor : 3
BogoMIPS : 1799.32
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 9
Hardware : vcm30t30
Revision : 58c800
Serial : 0000000000000000

RAM: 1024 MB (988 MB available)

tegra-nor: 64.000MB
System RAM: 988.000MB
fbmem: 8.000MB
fbmem: 8.000MB


Flash: 8 GB (7.031 GB actual); 931.513 GB

mmcblk0: 7.031 GB
sda: 931.513 GB
mtdblock: 0.087 GB


Yes, this is sometimes entertaining for a number of reasons.

The build.prop is interesting. I will post a reference version for our car later as it is slightly different than what I found in other Honda variants (Accord, Civic, etc - ones that have a knob).

Cheers,

Cash
Click to expand...

I have CR-V 2020 Touring in Europe which should have maps in the head unit but for some reason the dealer deleted the maps or removed the internal sd card. In a service manual I saw that the sd card cannot be removable. Do you have any clue how does it work? I rooted the unit and cannot see the sd card. It is listed under /mnt/sdcard2 but when I write something on it, it disappears after reboot. I wonder if the sd card is an embedded style or removable when you disassemble the unit. Please advise
 
Here's the build.prop from mine, NA Clarity 2018 PHEV Non-Touring (Rooted with HH):

Code: 
 # begin build properties
# autogenerated by buildinfo.sh
ro.build.id=1.F196.58
ro.build.display.id=1.F196.58
ro.build.version.incremental=42
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Tue Jul  4 04:57:05 JST 2017
ro.build.date.utc=1499111825
ro.build.type=user
ro.build.user=MitsubishiElectric
ro.build.host=BUILD_PC
ro.build.tags=release-keys
ro.product.model=MY16ADA
ro.product.brand=Honda
ro.product.name=Andromeda
ro.product.device=vcm30t30a
ro.product.board=Andromeda
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=MITSUBISHI ELECTRIC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=vcm30t30
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=vcm30t30-user 4.2.2 1.F196.58 42 release-keys
ro.build.fingerprint=Honda/Andromeda/vcm30t30a:4.2.2/1.F196.58/42:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-icera.so
rild.libargs=-e rmnet0
persist.tegra.nvmmlite = 1
ro.sf.override_null_lcd_density = 1

keyguard.no_require_sim=true

#NFC
debug.nfc.fw_download=false
debug.nfc.se=false

ro.ril.wake_lock_timeout=200000

#support dynamic resolution change property
ro.streaming.video.drs=true

#USB-A OTG mode
persist.sys.usb1_mode=host

#Color Adjustment
persist.tegra.un_premult_alpha=1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=wifi-only
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
 
Yes, reviving a thread back from the dead [emoji16]

Has anyone had anymore "development" on this Headunit??

I was looking around the other day to see if I could change DPI settings so I could enable Android Auto split-screen. Has anyone played around with those settings and gotten it to work??

Thanks

Sent from my SM-G975U using Tapatalk
 
Honda hacked my HU yesterday. Been having way too much fun since. Managed to get to the 4.2.2 "easter egg" game in Android (remember those?) by installing Shortcut Master (lite) and finding com.android.systemui.BeanBag in the App Explorer.
20211026-135711.jpg

Now that I'm HH'd I want to do a couple different things. I got it so I could use Head Unit Reloaded and make the HU wireless Android Auto capable. Good news and bad news on that front: it's entirely possible! I got it working at least once. The bad news, is that it's a bit slow (not as slow as running Google play services, but not zippy as usual) and involves a lot of setup. Here's the guide. I'm using WiFi method #2 until I can figure out if the HU is capable of starting a hotspot, which doesn't look possible so far. By all means, someone please prove me wrong.

The only other ideas I have ATM are to find a lightweight game just for fun, or potentially try and unlock the maps functionality on my non-touring PHEV. Pretty sure it's out of my pay range, not to mention illegal, but a man can try. For educational purposes of course
 
Last edited:
Enoxys said:
The bad news, is that it's a bit slow (not as slow as running Google play services, but not zippy as usual)
Click to expand...
Codeage (dev of HH) offers a lite/barebones version of G Play Services in-app. Other than that, you can also disable animations through dev ops, and reduce the touch response times through diagnostics menu. Won't be fast by any means, but better than it is by default.
 
Arctiic said:
Codeage (dev of HH) offers a lite/barebones version of G Play Services in-app. Other than that, you can also disable animations through dev ops, and reduce the touch response times through diagnostics menu. Won't be fast by any means, but better than it is by default.
Click to expand...

Thanks for the tips! I am pretty comfortable with using APKs so I don't have a big need for Play Services, although that's good information. Next time I fiddle around with the HU I'll go into the developer options and toggle those, it can't really hurt ¯\_(ツ)_/¯

On another front, I've gotten wireless AA working pretty reliably. The procedure to get it working manually was easy enough, following the forum thread from above, but one of my goals for using AA wirelessly was for it to be less of a hassle than taking my phone out of my pocket to plug it in. I went down the rabbit hole that is Tasker in order to automate the process, and it's more or less functioning. The task runs when I connect/disconnect to HandsFreeLink, and it does a few things:
  • Unlocks the phone. (After many trials and tribulations and tasker plugins suggesting I could unlock the keyguard, I just resorted to changing my pattern password to a PIN and sending touch inputs to it. Secure, I know.)
  • Toggles a mobile hotspot on my phone (Make sure your HU automatically connects to it)
  • Launches Android Auto. If you're following along in tasker, when you're on the app selection screen you gotta long press on AA and scroll down the list until you see companion.settings.DefaultSettingsActivity.
  • Then it sends a touch input to the 3 dots on the top right and the 3rd option on the list that drops down, which is the start/stop button for the head unit.
To get it working seamlessly with the HU, have HondaHack launch Head Unit Reloaded on startup. Once the phone and the HU are connected to each other, start Wifi mode on HUR, and AA should come on your screen. After a few seconds of lag, my connection has been pretty rock solid. There's a little bit of input delay that gets less noticeable after ~15 seconds.

One thing of note for the android devs out there, there's a service within the Android Auto app package that should start the head unit server, called
"com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService". I'm not sure how to start that service without manually pressing buttons, and my task is pretty inefficient because of all the manual inputs. Someone with more android dev knowledge and caffeine than I would be of great service to the Head Unit Reloaded community were they to figure out how to launch the service without having to resort to sending inputs.

If anyone has questions, go ahead and ask. I don't consider myself a master at this stuff just yet but I'll give it a shot.
 
Enoxys said:
If anyone has questions, go ahead and ask. I don't consider myself a master at this stuff just yet but I'll give it a shot.
Click to expand...
Slightly off-topic, but I'll try your 'mastery' anyway !
As you probably know, we are able to read the HV battery capacity through the OBD2 port. This involves reading a single PID from the CAN bus. The head unit undoubtedly has CAN access, and it would be very nice to read this parameter and display it on the screen (much like HH does with the 12V battery and CPU load). This would only need to be done once during startup because the value is more-or-less static, so it should not have a negative impact on normal operations... Any idea how to read a vehicle CAN value with the head unit?
 
MrFixit said:
Slightly off-topic, but I'll try your 'mastery' anyway !
As you probably know, we are able to read the HV battery capacity through the OBD2 port. This involves reading a single PID from the CAN bus. The head unit undoubtedly has CAN access, and it would be very nice to read this parameter and display it on the screen (much like HH does with the 12V battery and CPU load). This would only need to be done once during startup because the value is more-or-less static, so it should not have a negative impact on normal operations... Any idea how to read a vehicle CAN value with the head unit?
Click to expand...

Is PID the only traceable data header? I'm assuming that header value is not static, which makes narrowing it down difficult unless you have another unique identifier to search by? I'm not very knowledgeable in this area, but I am aware of a fairly pricey piece of hardware called the Comma Panda; despite the price tag though, the community behind its development is open-source (OpenPilot). You might be able to get more information by interacting with the development community there, provided there's no conflicts of interest in the exchange of the involved information. Another such community you can try would be Giraffe community; they are also open-source, and they are the ones responsible for the development of the $30 piece of hardware (optionally, you can build your own) that enables OBD-II data injection into the CAN-buses while selectively filtering the ADAS' stream. More importantly, the Giraffe handles CAN-ID emulation and ECU fingerprinting; I've not looked very deep into the infrastructures involved, but just based on intuition I'd say they would have a good chance of being able to point you in the right direction, if not straight-out answer your inquiries. Hope that helps!
 
Arctiic said:
Is PID the only traceable data header? I'm assuming that header value is not static, which makes narrowing it down difficult unless you have another unique identifier to search by? I'm
Click to expand...
Sorry, maybe I didn't explain this well enough. The header is fixed, and I already know the PID addressing and decoding. Just pondering how the head unit interacts with the vehicle CAN. Are there Android CAN drivers in place with sufficient documentation too use them? I have and used a CAN sniffer through the OBD port... Just need to be able to do this from Android with the head unit.
 
MrFixit said:
Any idea how to read a vehicle CAN value with the head unit?
Click to expand...
I have never touched an OBD2 port in my life, let alone interacted with CAN, though I have seen a handful your posts about getting a battery readout. You guys use Bluetooth OBD2 readers right? Is there anything stopping the Honda Hacked lot of you from BT connecting to the reader directly from the head unit and install the app you use to read the data on the HU? If the app is lightweight enough I bet you could get away with reading the relevant data without the use of your phone.
 
You must log in or register to reply here.
Back
Top