Database Users

Help Identifying Android Head Unit - RK3188, 1GB RAM, 16GB ROM, 1024x600 10.2"

Hey guys,
Sorry in advance if this has been posted in the wrong area, but it seemed the most appropriate.
Been looking around to see what head units are available for my car ('07 Mazda 6) at the moment and unfortunately there isn't much choice; a rare and expensive 2DIN dash kit and a Newsmy unit or one of these Last time I looked these weren't available so it's a bit more appealing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not interested in it if the firmware hasn't been torn apart and fixed by members here though, so I was hoping that somebody could identify who makes this particular unit.
Here are the specs:
Specifications
OS Android 4.4.4
CPU RK3188 series(PX3)
Cores 4 cores
MHz 1.6G
RAM series DDR3
RAM capacity 1G
ROM series iNand Flash
ROM capacity 16G
Double SD card/MuIti-Media Maximum capacity: 64G
Screen Size Different Car DVD model different size (Edit: this particular one is 10.2")
Screen Resolution 1024*600
Screen Panel CTP (Capacity Touch Panel)
GPS module GPS/Beidou
WIFI Built-in(IEEE 802.1 lb/g/n)
3G Unicom/Telecom/Moblie(Adapter)
USB(Port) 3 pieces USB2.0(Extensible)
SD card slot 2 pieces
Moblie HD Support FAT/NTFS

kylemd said:
Hey guys,
Sorry in advance if this has been posted in the wrong area, but it seemed the most appropriate.
Been looking around to see what head units are available for my car ('07 Mazda 6) at the moment and unfortunately there isn't much choice; a rare and expensive 2DIN dash kit and a Newsmy unit or one of these Last time I looked these weren't available so it's a bit more appealing.
I'm not interested in it if the firmware hasn't been torn apart and fixed by members here though, so I was hoping that somebody could identify who makes this particular unit.
Here are the specs:
Specifications
OS Android 4.4.4
CPU RK3188 series(PX3)
Cores4 cores
MHz1.6G
RAM seriesDDR3
RAM capacity1G
ROM seriesiNand Flash
ROM capacity16G
Double SD card/MuIti-MediaMaximum capacity: 64G
Screen SizeDifferent Car DVD model different size (Edit: this particular one is 10.2")
Screen Resolution1024*600
Screen PanelCTP (Capacity Touch Panel)
GPS moduleGPS/Beidou
WIFIBuilt-in(IEEE 802.1 lb/g/n)
3GUnicom/Telecom/Moblie(Adapter)
USB(Port)3 pieces USB2.0(Extensible)
SD card slot2 pieces
Moblie HD Support FAT/NTFS
Click to expand...
Click to collapse
My questions are on similar note. I recently purchased Android HU from AliExpress. [https://m.aliexpress.com/item/32330018202.html
I wish, I had done some research on it and gone for joying brand considering their US popularity. Not that I have any issues with current one but I am not sure if I can flash any ROM on it or not. Here is what it says in about screen of settings.
Everything is working flawlessly, radio, backup camera, bluetooth obd device, play store. I even can get into factory settings using 126 password. May be I can root it as well depending upon my ROM concerns for flashing purpose.
How can I identify,
A. There is no malicious communication to some third party server?
B. Any compatible clean ROM without losing any HU functionality?
C. Recommended list of apps (for syncing phone notifications with HU, verify specs with listing)
D. Any other recommendations by experienced user?
E. How can I make steering wheel control working? SWC key1 and key2 cables are on unit, I know SWC cable on factory harness but when I connect it, I blew the back up fuse on my Honda CR-V 2006. May be factory wiring diagram I have is wrong. For now, I am not using it but eventually I would like to use it. Do I need any axxess aswc-1 module for it?
Let me know if you have any more questions.
Thanks,
Sent from my SGH-I337 using XDA-Developers mobile app

Bump, still interested in this device and whether anybody knows what it is/who it is made by.
EDIT - One of the resellers on Aliexpress sent me a screenshot from the "About" page on the device if it helps with identification:

Another bump with some more information:
There's a large Russian thread discussing a similar unit for a Hyundai IX35. I believe this is a MCU version of those particular units.
Does anybody know if I'd be able to flash Malaysk on this? I doubt it but can't hurt to ask.

nbhor said:
My questions are on similar note. I recently purchased Android HU from AliExpress. [https://m.aliexpress.com/item/32330018202.html
I wish, I had done some research on it and gone for joying brand considering their US popularity. Not that I have any issues with current one but I am not sure if I can flash any ROM on it or not. Here is what it says in about screen of settings.
Everything is working flawlessly, radio, backup camera, bluetooth obd device, play store. I even can get into factory settings using 126 password. May be I can root it as well depending upon my ROM concerns for flashing purpose.
How can I identify,
A. There is no malicious communication to some third party server?
B. Any compatible clean ROM without losing any HU functionality?
C. Recommended list of apps (for syncing phone notifications with HU, verify specs with listing)
D. Any other recommendations by experienced user?
E. How can I make steering wheel control working? SWC key1 and key2 cables are on unit, I know SWC cable on factory harness but when I connect it, I blew the back up fuse on my Honda CR-V 2006. May be factory wiring diagram I have is wrong. For now, I am not using it but eventually I would like to use it. Do I need any axxess aswc-1 module for it?
Let me know if you have any more questions.
Thanks,
Sent from my SGH-I337 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have the same HU as you (basically. same specs, different hardware button locations).
I'd be interested to know what you find out...

xtravbx said:
I have the same HU as you (basically. same specs, different hardware button locations).
I'd be interested to know what you find out...
Click to expand...
Click to collapse
My experience,
- you cannot run multiple applications simultaneously, unit just slows down
- supplied GPS app, Sygic is too slow
- SWC controls do not work out of the box with 2006 CRV, I am using axe's adapter to get 2 buttons mapped.
Root to rescue,
- used Kingo root app
- using Greenify, adblocker, autostart manager, AF Wall+ apps to conserve memory hungry and malicious net activity apps if any.
- using google maps offline for local commute and Waze for long drive with tethering to phone
- multiple Tasker profile for bluetooth and wifi management on phone
After all these tweaks, things are running smooth. Let me know if you need anymore info about it or any suggestions about how I can improvise?
Good luck[emoji106]
Sent from my SGH-I337 using XDA-Developers mobile app

nbhor said:
My questions are on similar note. I recently purchased Android HU from AliExpress. [https://m.aliexpress.com/item/32330018202.html
Click to expand...
Click to collapse
xtravbx said:
I have the same HU as you (basically. same specs, different hardware button locations).
I'd be interested to know what you find out...
Click to expand...
Click to collapse
nbhor said:
Good luck[emoji106]
Click to expand...
Click to collapse
These posts are about a MTCD unit guys. There is actually a whole section dedicated to these units. For the purposes of keeping the discussion focused on identifying this type of unit it'd be appreciated if you could move these posts to the relevant section :good:
I bought the unit in the OP from here on Sunday in a moment of weakness, so I'll report back here with actual findings when I receive and install the unit.
As for who makes the unit, the most I've been able to find out is that it is either made by Ling Sheng (凌盛), or by a subsidiary of theirs called Haotewei (浩特威). Again, even this may not be correct and they may just be resellers. I have not been able to identify whether it is a MTCB/MTCD based unit or otherwise yet.
As for the stock firmware, as per the aforementioned Russian thread there seems to be some issues with it; GPS and music cannot be used at the same time being the main problem.
In terms of getting some custom firmware on it, after some reading I'm fairly confident I'll be able to either kitchen up my own ROM for these units, or get enough info to assist somebody in building the kernel from source (I could give it a dig but it'll take years for me to get anywhere).
So far the plan is to:
Output an AIDA64 report to get hardware information
Use Flashfire to rip the ROM from the unit
Record the GPIO pinouts where possible using this tool
If anybody else has any suggestions in regards to what other info I'll need from the device it'd be fantastic.

OK guys, so I received the unit Thursday and installed it today.
Other than being a pain in the ass to install (because of the car, not the unit!) it was fairly straightforward. Fit leaves a little to be desired, of which I'll post some pics when it's light.
The stock ROM is pretty unpolished; kills apps aggressively (can only have three apps open on the device, excluding background services), steering wheel keys don't work in any other player other than the one provided, doesn't seem to have an lux sensor so no autobrightness. Other than that it runs fairly well, the intended functions work as long as you make sure that the only apps open are maps and music.
To root the unit I installed KingRoot, then used SuperSUMe to install SuperSU on the device.
So far my attempts at using Flashfire to extract a ROM off of the device have been epic fails so I will have a go at using the RockChip tool posted on the FreakTab forums. I need a USB A Male > USB A Male cable to connect to the head unit though, so I'll need to go get one of those.
Below is the AIDA64 log from the device if anybody is interested in seeing what's under the hood.
<<< System >>>
Manufacturer: rockchip
Model: rkpx3
Brand: rockchip
Board: rk30sdk
Device: rkpx3
Hardware: rk30board
Platform: rkpx3
Product: rkpx3
Serial: QK2142BV3L
Total Memory: 1024 MB
Available Memory: 237 MB
Internal Storage Total Space: 1003 MB
Internal Storage Free Space: 448 MB
External Storage State: mounted
External Storage Total Space: 12.65 GB
External Storage Free Space: 8819 MB
Device Features: android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.front
android.hardware.faketouch
android.hardware.location
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.device_admin
android.software.live_wallpaper
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A9 @ 1416 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r3p0
CPU Cores: 4
CPU Clock Range: 312 - 1416 MHz
Core 1 Clock: 1416 MHz
Core 2 Clock: 1416 MHz
Core 3 Clock: 1416 MHz
Core 4 Clock: 1416 MHz
CPU Utilization: 9 %
Scaling Governor: interactive
CPU ABI: armeabi-v7a
CPU ABI2: armeabi
AES: Not Supported
NEON: Supported
SHA1: Not Supported
SHA2: Not Supported
<<< Display >>>
Screen Resolution: 1024 × 600
Screen Size: 153 mm × 90 mm
Screen Diagonal: 6.99 inches
Pixel Density: 170 dpi (mdpi)
xdpi / ydpi: 170 / 169 dpi
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
Refresh Rate: 64 Hz
Default Orientation: Landscape
OpenGL ES Version: 2.0
GPU Version: OpenGL ES 2.0
OpenGL ES Extensions: GL_EXT_debug_marker
GL_OES_texture_npot
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_depth24
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth_texture
GL_OES_packed_depth_stencil
GL_EXT_texture_format_BGRA8888
GL_OES_vertex_half_float
GL_EXT_blend_minmax
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_rgb8_rgba8
GL_EXT_multisampled_render_to_texture
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_ARM_mali_program_binary
GL_EXT_shader_texture_lod
GL_EXT_robustness
GL_OES_depth_texture_cube_map
<<< Network >>>
<< Telephony >>
Phone Type: None
<< Wi-Fi >>
State: Enabled
SSID: "MyMazda"
BSSID: b0:e2:35:c1:9e:51
Hidden SSID: No
MAC Address: 3c:33:00:c1:bd:17
Signal Strength: -45 dBm (Excellent)
Link Speed: 72 Mbps
Network ID: 3
Gateway: 192.168.43.1
Netmask: 255.255.255.0
DNS1: 192.168.43.1
DHCP Lease Duration: 1 hour
Wi-Fi Direct: Supported
<<< Battery >>>
Power Source: A/C Charger
Level: 50 %
Status: Discharging
Health: Good
Technology: Li-ion
<<< Android >>>
Android Version: 4.4.4 (KitKat)
API Level: 19
Rooted Device: Yes
Android ID: dfadfb094e9512ee
Build ID: 885-1605071020-WQ-16EN-M6
Codename: REL
Fingerprint: rockchip/rkpx3/rkpx3:4.4.4/KTU84Q/eng.zbunix.20160226.155041:eng/test-keys
ID: KTU84Q
Incremental: eng.zbunix.20160226.155041
Java Runtime Version: Android Runtime 0.9
Java VM Version: Dalvik 1.6.0
Java VM Heap Size: 64 MB
Kernel Architecture: armv7l
Kernel Version: 3.0.36+ ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #9 SMP PREEMPT Tue Apr 26 10:55:36 CST 2016
Tags: test-keys
Type: eng
Google Play Services Version: 9.8.77 (032-135396225)
OpenSSL Version: OpenSSL 1.0.1e 11 Feb 2013
ZLib Version: 1.2.8
ICU CLDR Version: 23.0
ICU Library Version: 51.1.0.1
ICU Unicode Version: 6.2
Android Language: English (Australia)
Configured Time Zone: Australian Eastern Daylight Time (UTC+11:00)
UpTime: 00:26:29
<<< Devices >>>
<< Rear-Facing Camera >>
Resolution: 0.8 MP (1024 × 768)
Focal Length: 35.00 mm
Focus Modes: fixed
Video Snapshot: Supported
Video Stabilization: Not Supported
Zoom: Supported
Smooth Zoom: Not Supported
Auto Exposure Locking: Not Supported
Auto White Balance Locking: Not Supported
<< Front-Facing Camera >>
Resolution: 0.8 MP (1024 × 768)
Focal Length: 35.00 mm
Focus Modes: fixed
Video Snapshot: Supported
Video Stabilization: Not Supported
Zoom: Supported
Smooth Zoom: Not Supported
Auto Exposure Locking: Not Supported
Auto White Balance Locking: Not Supported
<< USB Device - Linux 3.0.36+ dwc_otg_hcd DWC OTG Controller >>
Manufacturer: Linux 3.0.36+ dwc_otg_hcd
Product: DWC OTG Controller
Serial: usb20_otg
Device ID: 1D6B-0002
Device Class: 09 / 00 (Full-Speed Hub)
Device Protocol: 00
Revision: 0300
Supported USB Version: 2.00
Current Speed: 480 Mbps
<< USB Device - Linux 3.0.36+ host20_hcd DWC OTG Controller >>
Manufacturer: Linux 3.0.36+ host20_hcd
Product: DWC OTG Controller
Serial: usb20_host
Device ID: 1D6B-0002
Device Class: 09 / 00 (Full-Speed Hub)
Device Protocol: 00
Revision: 0300
Supported USB Version: 2.00
Current Speed: 480 Mbps
<< USB Device - USB2.0 Hub >>
Product: USB2.0 Hub
Device ID: 05E3-0608
Device Class: 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol: 01
Revision: 8536
Supported USB Version: 2.00
Current Speed: 480 Mbps
Maximum Power: 100 mA
<< USB Device - Lexar USB Flash Drive >>
Manufacturer: Lexar
Product: USB Flash Drive
Serial: AA3XQD9XCFEZWVV8
Device ID: 05DC-A81D
Device Class: 00 / 00
Device Protocol: 00
Revision: 1100
Supported USB Version: 2.00
Current Speed: 480 Mbps
Maximum Power: 200 mA
<< USB Device - Realtek 802.11n WLAN NIC >>
Manufacturer: Realtek
Product: 802.11n WLAN NIC
Device ID: 0BDA-8179
Device Class: 00 / 00
Device Protocol: 00
Revision: 0000
Supported USB Version: 2.00
Current Speed: 480 Mbps
Maximum Power: 500 mA
No OpenCL devices found.
No CUDA devices found.
No Vulkan devices found.
No PCI devices found.
<<< Thermal >>>
No thermal sensors found.
<<< Sensors >>>
Gravity sensor:
Compass Magnetic field sensor:
Orientation Sensor:
Gyroscope sensor:
Proximity sensor: 9.0 cm
Light sensor:
Pressure sensor:
Temperature sensor:
Rotation Vector Sensor:
Gravity Sensor:
Linear Acceleration Sensor:
<<< Apps >>>
AIDA64: com.finalwire.aida64(v1.42)
DiskUsage: com.google.android.diskusage(v3.7.1)
F-Droid: org.fdroid.fdroid(v0.100.1)
FasterGPS: org.fastergps(v1.11)
FlashFire: eu.chainfire.flash(v0.53)
Google Keyboard: com.google.android.inputmethod.latin(v5.1.23.127065177-armeabi-v7a)
Maps: com.google.android.apps.maps(v9.40.2)
MiXplorer: com.mixplorer(v6.9.6.BETA)
Power Manager: com.peppe130.powermanager(v4.2)
Shuttle+: com.simplecity.amp_pro(v1.5.15)
SuperSU: eu.chainfire.supersu(v2.78)
SuperSU Me-Pro: darkslide.com.supersumepro(v9.3.8)
XDA Labs: com.xda.labs(v1.0.9.3b)
<<< Codecs >>>
OMX.rk.video_decoder.avc: video/avc
OMX.rk.video_decoder.m2v: video/mpeg2
OMX.google.vp8.decoder: video/x-vnd.on2.vp8
OMX.google.vp9.decoder: video/x-vnd.on2.vp9
OMX.rk.video_decoder.h263: video/3gpp
OMX.rk.video_decoder.m4v: video/mp4v-es
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
OMX.google.amrnb.decoder: audio/3gpp
OMX.google.amrwb.decoder: audio/amr-wb
OMX.google.aac.decoder: audio/mp4a-latm
OMX.google.g711.alaw.decoder: audio/g711-alaw
OMX.google.g711.mlaw.decoder: audio/g711-mlaw
OMX.google.vorbis.decoder: audio/vorbis
OMX.google.mp3.decoder: audio/mpeg
RkAudioDecoder_DTS: audio/vnd.dts.hd
RkAudioDecoder_WMA: audio/x-ms-wma
RkAudioDecoder_WMAPRO: audio/x-ms-wmapro
RkAudioDecoder_AC3: audio/x-ms-ac3
RkAudioDecoder_RA: audio/vnd.rn-realaudio
RkAudioDecoder_AAC: audio/mp4a-latm
RkAudioDecoder_WAV: audio/wav
FLACDecoder: audio/flac
AACDecoder_MIRRORING: audio/mp4a-latm
OMX.google.vp8.encoder: video/x-vnd.on2.vp8
OMX.rk.video_encoder.avc: video/avc
RkOn2Encoder: video/avc
OMX.google.h263.encoder: video/3gpp
OMX.google.mpeg4.encoder: video/mp4v-es
OMX.google.amrnb.encoder: audio/3gpp
OMX.google.amrwb.encoder: audio/amr-wb
OMX.google.aac.encoder: audio/mp4a-latm
OMX.google.flac.encoder: audio/flac
AACEncoder: audio/mp4a-latm
OMX.rk.video_encoder.avc: video/avc
RkOn2Encoder: video/avc
OMX.google.raw.decoder: audio/raw
OMX.google.mp3.decoder: audio/mpeg
RkAudioDecoder_DTS: audio/vnd.dts.hd
RkAudioDecoder_WMA: audio/x-ms-wma
RkAudioDecoder_WMAPRO: audio/x-ms-wmapro
RkAudioDecoder_AC3: audio/x-ms-ac3
RkAudioDecoder_RA: audio/vnd.rn-realaudio
RkAudioDecoder_WAV: audio/wav
RkAudioDecoder_AAC: audio/mp4a-latm
FLACDecoder: audio/flac
AACDecoder_MIRRORING: audio/mp4a-latm
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
HEVCDecoder: video/hevc
<<< Directories >>>
Data: /data
Root: /system
Java Home: /system
Download/Cache Content: /cache
<< External Storage >>
Primary External Storage: /mnt/internal_sd
External Files #1: /mnt/internal_sd/Android/data/com.finalwire.aida64/files
Alarms: /mnt/internal_sd/Alarms
DCIM: /mnt/internal_sd/DCIM
Downloads: /mnt/internal_sd/Download
Movies: /mnt/internal_sd/Movies
Music: /mnt/internal_sd/Music
Notifications: /mnt/internal_sd/Notifications
Pictures: /mnt/internal_sd/Pictures
Podcasts: /mnt/internal_sd/Podcasts
Ringtones: /mnt/internal_sd/Ringtones
<< Mount Points >>
/: Device: rootfs
File System: rootfs
Read-Write
/dev: Device: tmpfs
File System: tmpfs
Read-Write
/dev/pts: Device: devpts
File System: devpts
Read-Write
/dev/cpuctl: Device: none
File System: cgroup
Read-Write
/proc: Device: proc
File System: proc
Read-Write
/sys: Device: sysfs
File System: sysfs
Read-Write
/sys/kernel/debug: Device: /sys/kernel/debug
File System: debugfs
Read-Write
/system: Device: /dev/block/platform/emmc/by-name/system
File System: ext4
Read-Only
/metadata: Device: /dev/block/platform/emmc/by-name/metadata
File System: ext4
Read-Write
/data: Device: /dev/block/platform/emmc/by-name/userdata
File System: ext4
Read-Write
/cache: Device: /dev/block/platform/emmc/by-name/cache
File System: ext4
Read-Write
/mnt/extsd: Device: /dev/block/vold/8:1
File System: vfat
Read-Write
/mnt/internal_sd: Device: /dev/block/vold/179:13
File System: vfat
Read-Write
<<< System Files >>>
Buddy Info: /proc/buddyinfo
Build Properties: /system/build.prop
Character & Block Devices: /proc/devices
Command Line: /proc/cmdline
CPU Information: /proc/cpuinfo
Default Properties: /default.prop
Execution Domains: /proc/execdomains
File Systems: /proc/filesystems
Frame Buffer Devices: /proc/fb
GPS Config: /system/etc/gps.conf
Hosts: /system/etc/hosts
Interrupts: /proc/interrupts
Input Devices: /proc/bus/input/devices
I/O Ports: /proc/ioports
Kernel Version: /proc/version
Load Average: /proc/loadavg
Locked Files: /proc/locks
Memory Information: /proc/meminfo
Memory Map: /proc/iomem
Misc Drivers: /proc/misc
Partitions: /proc/partitions
Statistics: /proc/stat
Swap Spaces: /proc/swaps

keep us updated, at this moment i am curious the steps for rooting on this device. I really want to add Viper4Android to improve the sound a bit
---------- Post added at 08:29 PM ---------- Previous post was at 07:57 PM ----------
Got everything to work, thanks kyle. Sounds much better! I can tune the music 10x better

Small update
Messed around with the unit today and managed to get >3 apps running. Download L Speed and change RAM management to "balanced".
While you're at it, enable quick boot... It doesn't make a huge difference but it does do something.
I got the required cable so I'll rip the ROM tomorrow afternoon.
nguyentoogood said:
keep us updated, at this moment i am curious the steps for rooting on this device. I really want to add Viper4Android to improve the sound a bit
---------- Post added at 08:29 PM ---------- Previous post was at 07:57 PM ----------
Got everything to work, thanks kyle. Sounds much better! I can tune the music 10x better
Click to expand...
Click to collapse
No problem

Oh yeah, while I think about it - you can't switch the screen off without it killing audio. Minimum brightness is still way too bright for night time, which is a problem.
If I find a solution I will post.

Hi Guys,
Recently I bought HU from AliExpress, below are the specifications of my HU.
Head Unit details :
aliexpress.com/item/10-1-Quad-core-1024-600-HD-screen-Android-4-4-Car-GPS-Navigation-for-Honda/32708554093.html?spm=2114.13010608.cb0001.14.fc9Ka W&scm=1007.13441.37946.0&pvid=3a034f70-d392-4c7b-9de8-790e43f12f59&tpp=1&aff_platform=aaf&sk=VnYZvQV f%3A&cpt=1478535874212&dp=c2294045051522105e3a3e60 ca9a28a4&af=240682&cv=47843&afref=http%3A%2F%2Ffor um.xda-developers.com%2Fprivate.php%3Fdo%3Dshowpm%26pmid% 3D18914319&aff_trace_key=39df33ce6ea94384a4f906d99 58a8a5d-1478535874212-04755-VnYZvQVf&aff_platform=aaf&sk=VnYZvQVf%3A&cpt=14786 09174296&dp=a8cabe104380485a17e39830d9338d48&af=24 0682&cv=47843&afref=http%3A%2F%2Fforum.xda-developers.com%2Fprivate.php%3Fdo%3Dshowpm%26pmid% 3D18918833&aff_trace_key=3bf1fba6485a40e4b30cb4010 7eb204f-1478609174296-07856-VnYZvQVf
When I installed this product, everything works perfect specially the sound quality was same as original sound quality, except reverse camera flickering issue.
Then the seller, sent updated OS version to fix reverse camera flickering issue and the camera issue has been fixed.
But, the sound quality was poor with new OS update. But the seller is not responding now to fix this issue.
Could you please try to fix this issue ?
This is the OS firmware image file, but it has audio output quality issue..
mediafire.com/file/hah6zoa6v467v4m/update_accord_8_system_file.zip

rizu3544 said:
Could you please try to fix this issue ?
This is the OS firmware image file, but it has audio output quality issue..
mediafire.com/file/hah6zoa6v467v4m/update_accord_8_system_file.zip
Click to expand...
Click to collapse
Can't help without OS and MCU version. Take a screenshot of the About page in System.
Also I'm not a developer, hoping one has this unit of sees the thread and is able to assist.

kylemd said:
Can't help without OS and MCU version. Take a screenshot of the About page in System.
Also I'm not a developer, hoping one has this unit of sees the thread and is able to assist.
Click to expand...
Click to collapse

I'm going to start calling them JAX SLX7786 based units, as going through the APKs last night it's pretty obvious JAX is the software vendor, although who that is I don't know.
rizu3544 said:
Click to expand...
Click to collapse
OK, so it's definately a JAX SLX7786 based unit.
I haven't had a chance to look at the ROM you've posted, but have you checked the gain settings to make sure they're all OK?

kylemd said:
OK, so it's definately a JAX SLX7786 based unit.
I haven't had a chance to look at the ROM you've posted, but have you checked the gain settings to make sure they're all OK?
Click to expand...
Click to collapse
Can I know how to check ROM details ?
I will check GAIN setting too.

rizu3544 said:
Can I know how to check ROM details ?
Click to expand...
Click to collapse
You just posted them - as far as I can gather all these units are all characterised by their OS version being JAXyymmddhhmm0G-WQ-16EN (yy being build year, mm being month and so on) and their MCU version containing the string SLX7786.
Unless you're talking about a ROM update or dump, which is the mediafire link you posted. I haven't been able to extract a ROM from my device yet so I'll see what I can work out from that.
As for extracting ROM - I can't connect to ADB via USB or wireless, and I can't access the Rockchip flash mode either. I think I managed to get it to boot into flash mode last night but I couldn't get Windows to pick up the device.
I think I'll have to dd the partitions onto a USB drive and work it that way.

kylemd said:
I think I'll have to dd the partitions onto a USB drive and work it that way.
Click to expand...
Click to collapse
I will wait for your update.
Thanks

rizu3544 said:
I will wait for your update.
Thanks
Click to expand...
Click to collapse
I've managed to extract the update.img that you posted. The build.prop looks nearly identical to mine as far as I can tell, but I will have to go get mine out of the car to know for sure.
If I get a chance tonight or this weekend I'll boot into Linux and see if I can get TWRP on there as per this thread over at FreakTab.

kylemd said:
If I get a chance tonight or this weekend I'll boot into Linux and see if I can get TWRP on there as per this thread over at FreakTab.
Click to expand...
Click to collapse
Hi,
I have checked the GAIN controls, no changes even after adjusting the controls.
Shall I try firmware from FreakTab to upgrade my HU ?
One more thing...!!! My HU dose'nt have any buttons, only touch screen.

No MCU information showing up in settings?

Hello,
I bought this R9 headunit from aliexpress (seller was JMCQ) and when I go into the "System Info" it does not display any information about the MCU type? It only says MCU1: 0.5 (3561) shouldn't there be a string of numbers there? Also if i try to access the about device in the android settings it shows everything except an MCU. Here are pictures of what I'm talking about:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the head units info:
DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: alps
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2018/08/16
13:44
RIL Version: mtk gemini ril 1.0
Build Number: YT3560_00012_V012
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MR
A58K/1572320644:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 57.44 Hz
PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: performance
Kernel Version: 3.18.19
Kernel Architecture: aarch64
GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0
RAM
Total: 2048 MB
This report is generated by Droid Info Android app.
Java Heap: 128 MB
STORAGE
Internal: 25.8 GB
External: 25.8 GB
PRIMARY CAMERA
Resolution: 0.4 MP
Flash: Yes
Video Resolution: 1904x232
Supported Resolutions:
Image:
1904x232
Video:
1904x232
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
Not Available
Can anyone help me identify what type of MCU this is (MTCD/C or MTCB ?) so that I don't flash the wrong rom? I'm hoping it is compatible with Hal9ks rom..

Ahhouai said:
Hello,
I bought this R9 headunit from aliexpress (seller was JMCQ) and when I go into the "System Info" it does not display any information about the MCU type? It only says MCU1: 0.5 (3561) shouldn't there be a string of numbers there? Also if i try to access the about device in the android settings it shows everything except an MCU.
Here are pictures of what I'm talking about:
Here is the head units info:
DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: alps
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2018/08/16
13:44
RIL Version: mtk gemini ril 1.0
Build Number: YT3560_00012_V012
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MR
A58K/1572320644:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 57.44 Hz
PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: performance
Kernel Version: 3.18.19
Kernel Architecture: aarch64
GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0
RAM
Total: 2048 MB
This report is generated by Droid Info Android app.
Java Heap: 128 MB
STORAGE
Internal: 25.8 GB
External: 25.8 GB
PRIMARY CAMERA
Resolution: 0.4 MP
Flash: Yes
Video Resolution: 1904x232
Supported Resolutions:
Image:
1904x232
Video:
1904x232
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
Not Available
Can anyone help me identify what type of MCU this is (MTCD/C or MTCB ?) so that I don't flash the wrong rom? I'm hoping it is compatible with Hal9ks rom..
Click to expand...
Click to collapse
Not an MTCx unit. Try searches based on the information not hidden.

Ahhouai said:
Hello,
I bought this R9 headunit from aliexpress (seller was JMCQ) and when I go into the "System Info" it does not display any information about the MCU type? It only says MCU1: 0.5 (3561) shouldn't there be a string of numbers there? Also if i try to access the about device in the android settings it shows everything except an MCU. Here are pictures of what I'm talking about:
Here is the head units info:
DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: alps
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2018/08/16
13:44
RIL Version: mtk gemini ril 1.0
Build Number: YT3560_00012_V012
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MR
A58K/1572320644:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 57.44 Hz
PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: performance
Kernel Version: 3.18.19
Kernel Architecture: aarch64
GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0
RAM
Total: 2048 MB
This report is generated by Droid Info Android app.
Java Heap: 128 MB
STORAGE
Internal: 25.8 GB
External: 25.8 GB
PRIMARY CAMERA
Resolution: 0.4 MP
Flash: Yes
Video Resolution: 1904x232
Supported Resolutions:
Image:
1904x232
Video:
1904x232
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
Not Available
Can anyone help me identify what type of MCU this is (MTCD/C or MTCB ?) so that I don't flash the wrong rom? I'm hoping it is compatible with Hal9ks rom.. [/QUOTEI have same problem
Click to expand...
Click to collapse

marchnz said:
Not an MTCx unit. Try searches based on the information not hidden.
Click to expand...
Click to collapse
Does this mean I'm out of luck for flashing ROMs?

Ahhouai said:
Does this mean I'm out of luck for flashing ROMs?
Click to expand...
Click to collapse
I have the same issue with the radio I bought.
Sent from my SM-A705MN using Tapatalk

Anyone know if there's a way to load TWRP on this unit?

The android version is fake. Actually it is Android 6.
The solution provider (actual manufacture) is XY AUTO (掌讯). And this model YT3560 never has an Android system higher than 6.0.
If you google "掌讯3560“, you'll find that all Chinese firmware has version 安卓6.0M (Android 6 Marshmallow), and the "international" firmware has Android 8.1 or 9.1, which are fake.
The one I bought is advertized as "rotatable screen". But actually the system doesn't support the screen rotation at all. To make the system working in portrait mode, it needs the "vertical screen ROM" to be flashed.
My suggestion is never buy a unit from XY AUTO again.
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Here I found some firmware update packages: https://www.mobile01.com/topicdetail.php?f=519&t=6047144
To be honest, I'm not sure if it will become Chinese system after flashing the update. However, I'm pasting the update for YT3560 here.
Landscape mode (2020-03-06) https://mega.nz/#!RzIUlQRT!_sp-cPTxS2_j_eAC4BQYHGsxZ9p7bv0KbCjTeQzmD4w
Portrait mode (2020-06-18) https://mega.nz/file/dqwxnICS#mERfv2SOL9To_M0DFO8cep9gA1JEBlQuIFv5Uqxaci8
The system is still Android 6.0. I assume the update is only minor tweaks.

I found a way to "rotate" the screen.
First, in "Car settings" -> "Other settings", untick the "Screen setting - Force mode".
Then, install screen rotation soft button: https://play.google.com/store/apps/details?id=com.alwaysrotate
Now, my problem is there is not a good launcher for portrait mode. And several stock app doesn't support portrait mode very well.

Hi, i have the same unit. My problem is the audio in a phone call using BT. I listen perfectly but the other person listen to me far away. Almost nothing.
Do you have the same problem?
BR.

chupitobaena said:
Hi, i have the same unit. My problem is the audio in a phone call using BT. I listen perfectly but the other person listen to me far away. Almost nothing.
Do you have the same problem?
BR.
Click to expand...
Click to collapse
Mine has the same problem. I'm thinking change it to a PX6 or TS9 unit. This YT3560 unit has too many issues.

Hi,
I am using YT3560 along with RAISE Can Bus. I am having the problem with built in mic. I am able to hear others without any issue. But, others complaining that my voice is low and lot of noise. Even I have disconnected the supplied external mic. But no improvement.
Can anybody suggest if we replace with a good external mic, will this solve the problem?
Further, my Car Information not showing RPM Rev data. All other data receiving from Raise Can Bus. Am I missing any setting or is it an issue with my Vehicle ?
My car is Skoda Rapid (India) Ambition - 2017 Model.
Please suggest how can I solve the issue:
1. Rev RPM data in my car information
2. MIC issues
Thank you.

snailium said:
The android version is fake. Actually it is Android 6.
The solution provider (actual manufacture) is XY AUTO (掌讯). And this model YT3560 never has an Android system higher than 6.0.
If you google "掌讯3560“, you'll find that all Chinese firmware has version 安卓6.0M (Android 6 Marshmallow), and the "international" firmware has Android 8.1 or 9.1, which are fake.
The one I bought is advertized as "rotatable screen". But actually the system doesn't support the screen rotation at all. To make the system working in portrait mode, it needs the "vertical screen ROM" to be flashed.
My suggestion is never buy a unit from XY AUTO again.
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Here I found some firmware update packages: https://www.mobile01.com/topicdetail.php?f=519&t=6047144
To be honest, I'm not sure if it will become Chinese system after flashing the update. However, I'm pasting the update for YT3560 here.
Landscape mode (2020-03-06) https://mega.nz/#!RzIUlQRT!_sp-cPTxS2_j_eAC4BQYHGsxZ9p7bv0KbCjTeQzmD4w
Portrait mode (2020-06-18) https://mega.nz/file/dqwxnICS#mERfv2SOL9To_M0DFO8cep9gA1JEBlQuIFv5Uqxaci8
The system is still Android 6.0. I assume the update is only minor tweaks.
Click to expand...
Click to collapse
Thanks for these! I found a newer update 2020/08/07 and it fixed a lot of my sound issues (volume dipping). The mobile01.com files seem to have password protection now so I could not download those. Can confirm this 20200807 package works on YT3560 XY Auto DSP with ST7850 Amplifier. My board is also V1.31.

Download link for the 20200807 update: https://mega.nz/file/PNUwHBYA#5eYuPVDgytHUV0Yg3hbQZZA9hgi3IfKwzy5gj69aGdE

Ahhouai said:
Download link for the 20200807 update: https://mega.nz/file/PNUwHBYA#5eYuPVDgytHUV0Yg3hbQZZA9hgi3IfKwzy5gj69aGdE
Click to expand...
Click to collapse
is this one legit to be used for 3560 unit?

codearm2 said:
is this one legit to be used for 3560 unit?
Click to expand...
Click to collapse
You can see my system in the OP and determine for yourself if it's the same as yours.

Ahhouai said:
You can see my system in the OP and determine for yourself if it's the same as yours.
Click to expand...
Click to collapse
It is the same
But mine is 4G version
Just wonder if it will lose the 4G function and make it into Wifi only unit
Also how about the language?

codearm2 said:
It is the same
But mine is 4G version
Just wonder if it will lose the 4G function and make it into Wifi only unit
Also how about the language?
Click to expand...
Click to collapse
Mine's 4G as well and still working (despite **** speed because of the antenna bands but that's always been the case). Language stayed the same as my system settings.

Ahhouai said:
Mine's 4G as well and still working (despite **** speed because of the antenna bands but that's always been the case). Language stayed the same as my system settings.
Click to expand...
Click to collapse
Nice!
Yeah the speed is ****ty, I can reach 80 Mbps on my phone using 4G
But on the head unit, it's only around 3-4 Mbps
Still enough for navigating and spotify though
Btw, what's the difference between vertical and horizontal fw?
3560 Horizontal screen (2020/03/06)
3560 Vertical screen (2020/06/18)
Found it from other forum (mobile01)
Is it the same like yours?
Also I attached the details of my head unit, it is the same right?
Just wonder if it's suitable to flash the rom

Ahhouai said:
Download link for the 20200807 update: https://mega.nz/file/PNUwHBYA#5eYuPVDgytHUV0Yg3hbQZZA9hgi3IfKwzy5gj69aGdE
Click to expand...
Click to collapse
boss,
what to do after downloading ?
how to install this ?

how to connect google assistant with steering wheel switch ?

Help with upgrade of YT9213AJ (full_8227L_demo) and get andriod auto working (possibly)

I have a 10.1" head unit. I wish I never would have bought it (don't buy one). After all the pain of install, I don't want to replace it.
I want to get android auto working with it. I installed the right APK and it had some dependencies ( google maps and google browser). I sideloaded all three, I cleared the problem of the dependencies with andriod auto, and it cleared the install screen.
Now android auto won't load, I think I need to upgrade the andriod and see if that helps
So here is my question: Can I update my firmware? How can I find the rom?
Can I get andriod auto to work with it?
Here are the specs:
Model: YT9213AJ(full_8227L_demo)
Manufacturer: ALPS
Build Number: YT9213AJ_00011_V001
Build Fingerprint: alps/full_8227L_demo/8227L_demo:9.1/O011019/1594284080:user/test-keys
OS: O MR1 (9.1)
CPU Arch. : ArMv7 Processor rev3 (v7i)
Chipset AC8227L
Cores 4
Instruction Sets: armeabi-v7a,armeabi
CPU features half thumb fast mult vfp edsp thumbee neon vfpv3 tis vfpv4 idiva idivt vfpde32 ipae evtstrm
Kernal version: 3.19.79

Did you find any answers? I'm wondering the same thing for my unit.

touchstone2 said:
I have a 10.1" head unit. I wish I never would have bought it (don't buy one). After all the pain of install, I don't want to replace it.
I want to get android auto working with it. I installed the right APK and it had some dependencies ( google maps and google browser). I sideloaded all three, I cleared the problem of the dependencies with andriod auto, and it cleared the install screen.
Now android auto won't load, I think I need to upgrade the andriod and see if that helps
So here is my question: Can I update my firmware? How can I find the rom?
Can I get andriod auto to work with it?
Here are the specs:
Model: YT9213AJ(full_8227L_demo)
Manufacturer: ALPS
Build Number: YT9213AJ_00011_V001
Build Fingerprint: alps/full_8227L_demo/8227L_demo:9.1/O011019/1594284080:user/test-keys
OS: O MR1 (9.1)
CPU Arch. : ArMv7 Processor rev3 (v7i)
Chipset AC8227L
Cores 4
Instruction Sets: armeabi-v7a,armeabi
CPU features half thumb fast mult vfp edsp thumbee neon vfpv3 tis vfpv4 idiva idivt vfpde32 ipae evtstrm
Kernal version: 3.19.79
Click to expand...
Click to collapse
You are correct. These units are horrible, but with a bit of tweaking, you can get them to perform reasonably well. I've made a guide on how to improve performance and user experience on YT9213AJ here.
PS - you don't need Android Auto on a true Android Head Unit. Just run the apps natively. AA requires a lot of resources and is meant for head units that can't run Android natively.

F9212A Firmware & Android Update

Hello all
I have purchased a chinese MCU recently, it works fine but the sound is low comparing to the original MCU.
i searched a lot on the internet to try and find if there is maybe an update to the firmware or android version but its really confusing and i though maybe someone here will be able to help maybe finding firmware and android update to the MCU, or maybe a way to boost audio output With an app or something.
Here is the info retrieved from the MCU by CPU-Z
SOC
Cores : 4
Architecture 4x ARM Cortex-A7 @1.12 GHz
Revision r0p3
Clock Speed 598MHz - 1.12 GHz
CPU 0 1118 MHz
CPU 1 1118 MHz
CPU 2 1118 MHz
CPU 3 1118 MHz
GPU Vendor ARM
GPU Render Mall-450 MP
GPU Load 0%
Scaling Governor performance
DEVICE
Model F9212A(full_8227L_demo)
Manufacturer aips
Board unknown
Hardware ac8227l
Screen Size 5.83 inches
Screen Density 160 dpl
Total RAM 1024 MB
Available RAM 316 MB (30%)
Internal Storage 11.96 GB
Available Storage 10.69 GB (89%)
SYSTEM
Android Version 10.0
API Level 29
Security Patch Level 2020-02-01
Bootloader unknown
Build ID F9212A_00017_V001
Java VM ART 2.1.0
OpenGL ES 2.0
Kernel Architecture armv71
Kernel Version 3.18.79 (1614921830)
Root Access No
Google play Services 22.12.15 (040300-439420056)
System Uptime 3 days, 04:15:30
Hope those info are enough, thanks for the help in advance

i have the latest version 7.3, now it has a separate application for the equalizer, but the audio output strength depends on the audio chip, I am a manufacturer and there is an option to manufacture with DSP (digital sound processor) this one does sound much louder than the original

Darkhack3r77 said:
i have the latest version 7.3, now it has a separate application for the equalizer, but the audio output strength depends on the audio chip, I am a manufacturer and there is an option to manufacture with DSP (digital sound processor) this one does sound much louder than the original
Click to expand...
Click to collapse
Hello @Darkhack3r77
When you say Latest Version 7.3 do you mean android version?
and is it possible to change this one audio chip ? os should i purchase a new one that supports DSP?
Thanks

So no one really have an answer ?

هل يمكنك مساعدتي ، أحتاج 9212 ملفات كاملة

ZaKzOuKer said:
Hello all
I have purchased a chinese MCU recently, it works fine but the sound is low comparing to the original MCU.
i searched a lot on the internet to try and find if there is maybe an update to the firmware or android version but its really confusing and i though maybe someone here will be able to help maybe finding firmware and android update to the MCU, or maybe a way to boost audio output With an app or something.
Here is the info retrieved from the MCU by CPU-Z
SOC
Cores : 4
Architecture 4x ARM Cortex-A7 @1.12 GHz
Revision r0p3
Clock Speed 598MHz - 1.12 GHz
CPU 0 1118 MHz
CPU 1 1118 MHz
CPU 2 1118 MHz
CPU 3 1118 MHz
GPU Vendor ARM
GPU Render Mall-450 MP
GPU Load 0%
Scaling Governor performance
DEVICE
Model F9212A(full_8227L_demo)
Manufacturer aips
Board unknown
Hardware ac8227l
Screen Size 5.83 inches
Screen Density 160 dpl
Total RAM 1024 MB
Available RAM 316 MB (30%)
Internal Storage 11.96 GB
Available Storage 10.69 GB (89%)
SYSTEM
Android Version 10.0
API Level 29
Security Patch Level 2020-02-01
Bootloader unknown
Build ID F9212A_00017_V001
Java VM ART 2.1.0
OpenGL ES 2.0
Kernel Architecture armv71
Kernel Version 3.18.79 (1614921830)
Root Access No
Google play Services 22.12.15 (040300-439420056)
System Uptime 3 days, 04:15:30
Hope those info are enough, thanks for the help in advance
Click to expand...
Click to collapse
Do you by any chance have a memory dump? I got the same spec head unit with software issues for cheap, thinking it would be simple to fix it, untill I trried to flash it with wrong firmware and totally forgot to remove the preloader. If you have a dump I would be very greatful.

ZaKzOuKer said:
Hello @Darkhack3r77
When you say Latest Version 7.3 do you mean android version?
and is it possible to change this one audio chip ? os should i purchase a new one that supports DSP?
Thanks
Click to expand...
Click to collapse
sorry for the late reply, if you need the rom ADD ME ON WSP +52 7773740878 i will help you

AFALAH said:
هل يمكنك مساعدتي ، أحتاج 9212 ملفات كاملة
Click to expand...
Click to collapse
اخي هل استطعت ايجاد فلاش هذا الجهاز f9212a

SWC problem

Hello friends
I buy a chinese 10" 1din headunit and i have a problem with the steering wheel controls,the buttons next/previous work only with default apks (video player/music player/radio).
I test a lot of third-party apks but don't works, (an other car with other chinese headunit all apks work perfect the next/previous buttons).
I update everything and next hard reset but don't fix.
Its big problem for me and i don't know how i resolve it..
Device info:
--------------------------------------------------------
Device Name : tb8163p3_bsp
Model : tb8163p3_bsp
Manufacturer : alps
Device : tb8163p3_bsp
Board : tb8163p3_bsp
Hardware : mt8163
Brand : alps
Build Fingerprint : alps/full_tb8163p3_bsp/tb8163p3_bsp:12 skin/PPR1.180610.011/eng.publis.20220917.100736:user/release-keys
System info:
--------------------------------------------------------
Android Version : 12 skin
Version Name : Pie
Released Date : Αυγούστου 09, 2018
Code Name : Pie
API Level : 28
Security Patch Level : 2021-09-05
Bootloader : unknown
Build Number : full_tb8163p3_bsp-user 12 skin PPR1.180610.011 eng.publis.20220917.100736 release-keys
Baseband :
Java VM : 2.1.0
Kernel : 4.9.117+
Language : (el_GR)
OpenGL ES : 3.1
Root Management Apps : No Apps Detected
SELinux : Unable to determine
Google Play Services : 23.08.15 (100300-512743456)
Vulkan : Supported (1.1)
Treble : Supported
Seamless Updates : Not Supported
CPUinfo:
--------------------------------------------------------
Processor : ARMv7 Processor rev 3 (v7l)
CPU Architecture : 4 x 1.30 GHz
Supported ABIs : armeabi-v7a, armeabi
CPU Hardware : MT8163
CPU Type : 32 Bit
CPU Governor : interactive
Cores : 4
CPU Frequency : 600 MHz - 1300 MHz
GPU Renderer : Mali-T720
GPU Vendor : ARM
GPU Version : OpenGL ES 3.1 v1.r26p0-01rel0.526d936ea9da20486773a9aaceecd920

Any help?

First: Do you know what codes your SWC are generating?
If it works fine for all the stock things then you might want to modify these 3rd party apps.
Use UsbMode.apk (in my sig) to see what the SWC (mapped through the stock software) are generating.
There is also the possibility of per-app mapping. But I don't do that.

No i don't know the SWC codes (i am rookie).
i use you apk and if i push next/pre button the apk write this.

Today i test the UsbMode.apk with SWC buttons and don't work!only with head unit buttons work.
My friend give me for test a topway ts7 head unit and i put to mycar (with my canbus),all third-party apps work perfect...
I don't understant where the problem in my headunit.
sorry for my english