Database Info

[Q] Can you tell me What HD2 I have?

Hello everyone, I hope I am not out of line. I just "aquired" an HD2 with wp7 already installed. It needs to be activated...but wait there's more.. I don't know what I have in terms of everything. not to mention volume down button is totally non functional physically and electronically. No external sound but vibrates. please see the information below and then please inform me as much as you can:
Phone has Red and Green Buttons/Not "all" white.
When booting...I can read the following at the top of the screen:
aMAGLDR 1.13
build feb 1 2011 03:46:07
by Cotulla 2011
booting wp7...
Then I go to Settings "ABOUT"
HTC HD7 T9292
Then "phone information"
Name: HTC HD7 T9292
Model: HTC HD7 T9292
Software: Windows Phone 7
Total Storage: 176.53 MB
Available Storage: 98.76 MB
"MORE INFO"
OS version: 7.0.7004.0
Firmware Revision Number: 2250.09.07401.605
Hardware Revision Number: 0002
Radio Software Version: 5.51.09.29_22.32.50.10U
Radio Hardware Version: A.12.0.D4
Bootloader Version: 0.96.2250.0
Chip SOC version: 2.2.5.0
Sorry so anal...What radio?? do I have? What should I use?
What Version Phone do I have? is it an american 1024? or euro 512?
Does it even matter? and why?
What MAGLDR should I use? Can I use 1.13 when someone calls for 1.12?
Due to my Vol Down button being broken/and no external spkr...Is my phone just a perfect example of "the walking dead"? Can I ever load it with anything else?
It has not been activated yet!
Am I able activate it with the obvious Hardware or Software problems already mentioned?
Sorry this is such a book, Yes I am a noobe and I simply love this Site.
My ultimate goal is to turn this phone into a wp7/android Dual Boot.
But if I can't...I already know I could love it as a wp7 after activation.
This is a list of present problems - No External Spkr (So I am using Vibrate)
Bluetooth searches but never finds anything. Wifi is sporadic, but It does work!
I strongly believe that the down button got broken when they realized it wasn't
working.
Are the problems I just mentioned due to a faulty Install?
I read the "WP7 Settings and Activation" threads and quite honestly i got scared,
which prompted me to write everyone here. Because if "You" don't know these
answers...Nobody does!
By the way I think Ya'll are smartphone "Gods".
Thank you in advance for any and all assistance with my dilema.
For the record...I bought this phone in this condition, and don't know any of it's history.
Can it be fixed without replacing hardware, AND can I make it a Dual Boot?
Thank You, PV
ps. I have an 8gb sandisk sdcard but it doesn't see it.
I am using it as a phone and it seems to do that perfect, but won't accept any
files, pics, music, etc. (it says Not enough space).

does it have T-Mobile written underneath the earpiece? if yes, then you got the TMo version with the 1GB ROM - which is better for flashing and provides more space...
I dont know about the volume button and flashing without it, but MAGLDR 1.13 would be backwards compatible with 1.12
afaik only Tmobile version has red and green buttons. correct me if I am wrong.

Thank you, xDhaha, I appreciate your help,
Next question: which "radio" do I need to use? or radio version do I have? is it 2.25? (this was obviously a shot in the dark noobie question)
I am trying to get as much info so that I can start working on this.
I have to activate it, also would like to try to set up a dual boot system if possible,
but I am still worried about the volume down button stopping me and could I brick my phone if I attempt anything without a volume down button.

General ROLL-UP -Joying 2GB - Sofia ( Non MTCB/MTCD )- Tips, tricks and mods

There is getting to be quite a bit of information to look through when looking for tip/solutions related to the new Joying 2GB / Sofia units. Since this is not a MTCB or MTCD unit, the threads seem to be scattered all over and very difficult to find in searching. I have seen roll-up threads for other units, that contain information such as ROMS available, tips, tricks and useful information. Kind of a "one stop shop" for the newer Joying HUs. If you have useful software, mod, tips, customization's, get something to work, etc please post here and I can include.
CPU Information - Rockchip Sofia x64 C3230RK / mali 450 GPU / Up to 1.2Ghz / 4 core / FYT5009 SoM - rated to run at up to 85C. My particular is unit clocked at 1.04Ghz.
Advanced Settings Password: 3368
Homescreen menu: 8086
Backlight Current menu: 5768
Android 6 Thread
https://forum.xda-developers.com/an...ing-intel-head-unit-android-6-update-t3597121
Android 6 specific tips:
ADB Access: https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273 -OR-
https://forum.xda-developers.com/showpost.php?p=72057022&postcount=12
Viper4Android: https://forum.xda-developers.com/showpost.php?p=72064749&postcount=41
Latest ROM - Current ROM can be downloaded from link on the Joying blog site.
https://www.carjoying.com/Joying-blog/59.html
Android 5.1 Discussion about the Feb 22, 2017/March 5, 2017/March 15, 2017 updates:
https://forum.xda-developers.com/an...d-units/joying-intel-update-feb-22nd-t3561285
People have experienced issues with the Joying Launcher (UI3) after the update. This seems related to having other packages (google voice search ) installed prior to installing the ROM. Install time 25-35 minutes.
Recovery from non-bootable system - Without being able to access recovery, about the only solution is to reload the ROM package. Unzip ROM to SD card or USB stick, put in unit (GPS Maps slot, if using SD card ) and press the 'recessed' reset button. The unit should find the update and reload the ROM. This will wipe your data, but does leave the apps. If you use titanium backup, and have a backup, you can restore your data fairly easily. See blog article above for step by step instructions.
Root - Unit comes with root accessible in adb. SuperSU can be installed easily. There are 2 methods for installing superSU. The first method is an overwrite of the boot partition with a pre-rooted image. Problem here is if future upgrade makes boot partition changes, this method will overwrite with an older version. I recommend method 2, which modifies the existing boot partition ( need source so I can provide credit ).
https://forum.xda-developers.com/showpost.php?p=69648860&postcount=84&nocache=1&z=8361786322568856 (over-writes boot partition / may not work on Joying Feb update )
https://drive.google.com/file/d/0B4qmTV7N4JliSjZMdGg3Z18wbkU/view?usp=sharing ( modifies existing boot partition )
OS & Google Apps - Android 5.1.1 ASOP based w/ pico installation of google applications. Voice actions are supported with installation of 'Google App' from play store. No support for google search talk back.
Recovery- A recovery partition is present but does not have any type of graphical UI. It does look like a complete stock android ( command line ) recovery, but no access using USB is available. It maybe be possible using PC-PC OTG cable.
SD Cards - I have not heard of any sdcard size limitations, up to 200GB have been reported to work. Must be formatted as FAT32. NTFS, exFAT, and ext3/4 do not work. You can format a USB stick with ext4 and it will work fine.
Google Voice Calling - Stock BT dialer crashes when being called from google applications ( such as google voice search ). Workaround is available.
https://forum.xda-developers.com/an...oogle-voice-to-initiate-calls-joying-t3528923
Enable OK Google from any screen - https://forum.xda-developers.com/showpost.php?p=72447390&postcount=968
Bluetooth Tethering & BT Settings - Bluetooth tethering, connects instantly, very reliable connection, works great for streaming music, gps etc. Saves phone battery vs WIFI hotspot. Limited to ~2Mbs ( slower than WIFI sharing )
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
(also good discussion here on the effects of process killing when entering standby )
Difficult to pair BT devices - Forces device pairing into database - Device pairs normally once HU thinks it has connected previously. I was able to pair TPMS, keyboard, etc using this method(s).
https://play.google.com/store/apps/details?id=com.brachcon.btautopair&hl=en
Modified stock bluetooth app to allow connection to all devices
https://forum.xda-developers.com/showpost.php?p=71280945&postcount=88
Backup Cam guideline mods - Make your lines match your camera view
https://forum.xda-developers.com/showpost.php?p=70325711&postcount=403
Apps not working after resume - The joying code will kill most applications when going into standby. This is really bad for apps that are supposed to be run at boot and background process, as they are not restarted when exiting standby. Symptoms include, widgets not updating, apps not getting GPS lock, process show running but background services are no longer running. This can be fixed by installing an updated apk file in /system/app/Sofia-1-C9-Server-V1.0 which removes the task killer. Also the key/button mods V2+ (below) will remove the task killer.
https://forum.xda-developers.com/showpost.php?p=71047452&postcount=62
Key/Button Mods - Extend the usefulness of your steering wheel keys and on unit buttons- V2+ also removes app kill on standby.
https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
If you just want to change the SRC button to call up google voice search, go here. ( also removes task killer )
https://forum.xda-developers.com/showpost.php?p=70480258&postcount=549
Immersive Mode / removes top navigation bar - No app needed - Full Screen on apps you choose, can be set from adb w/ root. Argument is list of package names separated by "," or "*" for all apps. ( survives reboot )
Specific apps:
settings put global policy_control immersive.full="com.google.android.apps.maps,com.pandora.android,com.spotify.music"
All apps:
settings put global policy_control immersive.full="*"
Clear / back to default
settings put global policy_control immersive.full=
Change Overscan - problems touching the corners, changing overscan can help:
https://forum.xda-developers.com/showpost.php?p=71492575&postcount=169
Phone/Tablet view on apps - No app needed - Change from 160dpi -> 161dpi gives "phone" view of many apps instead of "tablet" with no noticeable size change to other things. Done via adb. Requires reboot to take effect.
> wm density 161 # ( phone mode apps )
> wm density 160 # ( original tablet mode apps )
Heatsink mod Unit can run hot at heavy cpu load (such as benchmark testing). Can slightly reduce performance by throttling. Some users opt to add additional heatsink/fan to reduce temperatures.
https://forum.xda-developers.com/an...inside-look-joying-android-head-unit-t3546872
Red Themed Radio - Re-theme of stock apps - Don't like the look, change it. Can be done easily by unzipping the apk file, change images, rezip and install.
https://forum.xda-developers.com/showpost.php?p=70367793&postcount=434
More Radio Mods ( Layout change, more colors )
https://forum.xda-developers.com/showpost.php?p=71625005&postcount=286
xposed / xposed framwork - At this time, I am not aware of any way to make this work with the new Joying units. I have tried several packages and all have resulted in a non-bootable system. Please let me know you go get it to work.
Viper4android - Installer script that works on these models
https://forum.xda-developers.com/showpost.php?p=71317345&postcount=101
Nova or other launcher - Need to freeze or remove stock Joying launcher(s) in some cases, for other launchers to work correctly.
Other very useful Joying 2gb/sofia threads:
Audio Discussion / DACs - https://forum.xda-developers.com/an...ts/joying-2gb-sofia-headunits-common-t3577217
https://forum.xda-developers.com/an...pment/joying-android-5-1-1-2gb-units-t3465561
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322

Yes this is really needed. A FAQ with overview links and tips in just one post

Some people mentioned it was possible to boot into a restore function from a memory card with the update zip. If true, do we know what the exact process is? Any keys need to be held down?
Update, verified this procedure works:
sonof said:
I did recover from endless Android logo (resulting from trying to root with Joying HU root.zip found in this thread).
I did the following:
Put latest Joying update files to microSD card and insert it to GPS slot. Press and hold both reset and power buttons. Once it boots continue holding reset button.
This lead to automatic install of Joying update files and my HU was back alive but I hate the Joying company for not providing means to enter recovery and a complete ROM.
Edit: For me it did not ask if I want to update or not. It just began updating automatically. In contradict to the post above. But I was unable to boot to Android when I tried this.
Click to expand...
Click to collapse

My VW has reverse parking sensors. Does it not support those?

Just installed this unit. Speedwise it's night and day compared to my old Erisin (1gb 3188). Display is nice and crisp. Bit of a fiddle getting it mounted because of all the crap that needs to be stuffed behind it, but after some swearing and elbow grease I got it secured.
From the instructions, I cut an orange wire because I don't have a backup camera. I do however have optical parking sensors. On my Erisin this was supported (it showed a car model and visual indicators on screen). This unit doesn't appear to have this function. Can anyone confirm? I still get the beep from the speakers, so it's not really a big issue, but would be nice to know.
---------- Post added at 10:49 PM ---------- Previous post was at 10:49 PM ----------
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Didn't see your post before asking the same question

anotheruserx said:
I'd like to work on this one.
But I have two questions;
1) did you manage to get any logs of how it failed?
2) When you made it unbootable, what was the exact procedure you used to recover the unit?
Click to expand...
Click to collapse
I didn't get any logs, as I couldn't connect to it until I reloaded the ROM. If I was able to make a USB connection, at least I could have looked at the logcat.
Procedure to recover: Insert USB drive with ROM, push recessed reset button, wait 30m for ROM to install, set up apps again. I have this procedure down pretty good. - The joys of playing with the system partition without USB access or recovery tools.

catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Actually, it turns out it does, however only when there's an obstacle (hopefully we can change this). Yesterday I only tested while stationary. Today I used it while driving, and noticed that whenever the sensor picked something up, the unit does actually display the sensors. It feels next to useless for me when it only shows on beeps, but at least we know it's there.

Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.

catu said:
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
Click to expand...
Click to collapse
After updating to the January firmware parking sensors are gone completely.
edit: enabling "radar" is the solution

Installed supersu (like described in this thread) yesterday and updated it from the play store. Worked fine.
Then I installed Viper4android, also from the store. I didn't expect it to work, but it does! Driver installed, and after a reboot it does exactly what it's supposed to.
Also installed Nova Launcher and set as default home. No issues with that so far. I have not frozen or uninstalled any of the original launchers.

On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.

Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold.
Click to expand...
Click to collapse
I have the same problem on the same unit. With the car headlights off, backlight is dim when it's cold, but gets brighter when it has time to warm up. And when the headlights are on, the backlight isn't on at all until it warms up.
I thought about writing Joying about it but I expected the kind of response you got. Plus, I've had my unit for a few months already so a PayPal claim isn't an option. Please let us know if you hear anything else about it from Joying.

Hi Joshnat,
Yes we have the same problem. Sometimes I can get mine to light up by turning the headlights on and off a couple of times. Are you sure that you cant make a Paypal claim? As far as I know you have 180 days.
Anyway, you should write to them and let them know that you know that many others have this problem.
Regards
Kurt

Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Click to expand...
Click to collapse
You may have a faulty screen, my first one did something similar and wasn't very responsive to touches. I returned and my second unit was like night and day with how much better it looked and worked.

Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk

mad212 said:
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I have the same car and HU, my oem backup carmera works. I bought a harness on Amazon including backup camera, USB, and aux in.
https://www.amazon.com/gp/product/B01BM3QGCO/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Quick tip:
You can adjust backup camera brightness, saturation and contrast by touching the screen while backup camera is on.

Is there a trick to putting in the sd cards? Mine won't click in so it won't mount.
Edit: Forget it i just had to get the edge of a screwdriver and push it in. Had me worried for a minute.
Sent from my LG-H918 using Tapatalk

Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Looking to install this option
https://drive.google.com/file/d/0B4q...ew?usp=sharing ( modifies existing boot partition )

thedru13 said:
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Click to expand...
Click to collapse
Within the zip there is a file with instructions - HOWTO.txt
How-To install:
1. You need a Windows PC that is connected to the same WiFi network as your HU.
2. Unzip the attached file somewhere to your disk.
3. Run CMD.exe as Administrator
4. Change directory to the folder that you unzipped.
5. Run the install.bat script with an IP address of your HU as a parameter:
C:\Users\<username>\Downloads\Joying_JY-UL135N2_SuperSU> install.bat 192.168.123.137
6. Wait until script finishes and reboot your Head Unit.
7. DONE!
You should now have the SuperSU application working.

Cold boot problem

hi guys,
i recently upgraded my mcu to the sound patched version. sound is much better, but now the dam head unit cold starts every time. when before it almost never did. any ideas? i have already, factory reset, wiped cache, loaded my old mcu settings(like recommended saving them before the mcu update.) but still the same..... i have tried 3 or 4 different MCU's all with the same result. i read there is an option in extra settings, but mine doesnt have any option there except "play music for usb/sd card on start" or something along those lines.
Any ideias? its really anoying, as backup camera only works 30-40 second after cold start....
ps: my first mcu was mtcd_gs_v2_23_1, its a px5 unit. running stock rom, android 6.0. xtrons for the bmw e90
any help greatly appreciated.

anyone?

Dasaita PX6 SD unmounted on every boot

I've got a PX6 unit running the latest firmware from Dasaita: HA3_rk3399_10.0_ota(20210311). It's rooted but otherwise stock. I'm running Car Launcher Pro as my launcher, and Poweramp as my music player. My SD card is a Samsung Evo Plus 128GB formatted to FAT32.
After a warm boot, the SD card is not mounted, causing Poweramp to lose all its music. To get it back I have to physically eject the SD card and re-insert it, which is incredibly annoying at the start of every journey.
I have contacted Dasaita but have not yet received a reply.
Does anyone know how to fix this?

Lum_UK said:
I've got a PX6 unit running the latest firmware from Dasaita: HA3_rk3399_10.0_ota(20210311). It's rooted but otherwise stock. I'm running Car Launcher Pro as my launcher, and Poweramp as my music player. My SD card is a Samsung Evo Plus 128GB formatted to FAT32.
After a warm boot, the SD card is not mounted, causing Poweramp to lose all its music. To get it back I have to physically eject the SD card and re-insert it, which is incredibly annoying at the start of every journey.
I have contacted Dasaita but have not yet received a reply.
Does anyone know how to fix this?
Click to expand...
Click to collapse
I have the PX6 unit running the latest MCU, but only Android 9 ROM (none of the downloaded Android 10 ROMs seem to work) and I have a similar issue with my USB1 not being read always. But USB2 or 3 is always available Would love to know where you got a working ROM? The one from Dasaita website will not load.

Knightbird68 said:
I have the PX6 unit running the latest MCU, but only Android 9 ROM (none of the downloaded Android 10 ROMs seem to work) and I have a similar issue with my USB1 not being read always. But USB2 or 3 is always available Would love to know where you got a working ROM? The one from Dasaita website will not load.
Click to expand...
Click to collapse
You are not missing anything running Android 10.
The most stable working version I believe is 8, all versions post 8 are rushed ported bug fests.
Stop chasing a higher number.

Lum_UK said:
I've got a PX6 unit running the latest firmware from Dasaita: HA3_rk3399_10.0_ota(20210311). It's rooted but otherwise stock. I'm running Car Launcher Pro as my launcher, and Poweramp as my music player. My SD card is a Samsung Evo Plus 128GB formatted to FAT32.
After a warm boot, the SD card is not mounted, causing Poweramp to lose all its music. To get it back I have to physically eject the SD card and re-insert it, which is incredibly annoying at the start of every journey.
I have contacted Dasaita but have not yet received a reply.
Does anyone know how to fix this?
Click to expand...
Click to collapse
My suggestion is to copy the music (some or as much of it as you can get) from the SD card to the internal memory and set that folder as the primary folder for PowerAmp. These units seem to have more difficulty mounting SD cards, especially higher capacity ones.
I've had a little better luck with having fewer folders with more files than the other way round. By at least having some music files in the head unit storage, this should get PowerAmp playing music sooner and it should catalog the files on the SD as needed in the background once the SD card is mounted.

I've been kind of torn between using the "warm boot/auto sleep" capability vs just having the head unit shut down every time. It seems the "auto sleep" function never brings the head unit back up the way it was when the car was turned off.
Since the cold boot time is so "short" (I use that word rather loosely here) it's probably just as well to let the unit shut down after n minutes/seconds. Like what's the use if the "fast warm boot" requires us to have to fiddle with stuff every time (e.g. popping SD card out/in, etc)?

marchnz said:
You are not missing anything running Android 10.
The most stable working version I believe is 8, all versions post 8 are rushed ported bug fests.
Stop chasing a higher number.
Click to expand...
Click to collapse
I appreciate your input! I am not "chasing a higher number", I am just trying to realize the features that were supposed to be in the product I purchased, such as split screens, 1280x1024 resolution and Android 10. Instead I got 1024x600 and Android 9 and very unstable. Navigation link fails to launch Wayze or Google Maps, VLC cannot display any video , they play but there is no video (audio sounds great) and an awful looking radio app.
I hear great things about the stability of the PX6 Android 9 version rk3399-userdebug 9 PQ2A.190305.002 20191210.152625 test keys. Supposed to be VERY stable and fast. Anyone have this version?

Knightbird68 said:
I appreciate your input! I am not "chasing a higher number", I am just trying to realize the features that were supposed to be in the product I purchased, such as split screens, 1280x1024 resolution and Android 10. Instead I got 1024x600 and Android 9 and very unstable. Navigation link fails to launch Wayze or Google Maps, VLC cannot display any video , they play but there is no video (audio sounds great) and an awful looking radio app.
I hear great things about the stability of the PX6 Android 9 version rk3399-userdebug 9 PQ2A.190305.002 20191210.152625 test keys. Supposed to be VERY stable and fast. Anyone have this version?
Click to expand...
Click to collapse
No option to send it back/warranty/product not as advertised?

marchnz said:
No option to send it back/warranty/product not as advertised?
Click to expand...
Click to collapse
Sadly was an eBay purchase that was "NEW IN BOX", but according to the stickers was an Amazon return.. All packing was perfect, I suspect that the purchaser got the wrong unit for his A/C controls.
Dasaita model is HA-5226-MAX6-CP, also shows X002F1YJQ9.
Instructions were clear, all components were still factory packaged, I just want a stable usable preferably factory (unmodified) ROM.
And I'd be happy if I could find a stable A9 ROM. Two weeks of searching and enough is enough.

Mine came with 10, I just updated it to a slightly newer version. Was really hoping not to use internal memory as its a pain copying stuff over when you want to chop & change music around, vs just bringing the car inside and doing it on the computer, especially as updates tend to wipe the internal memory, or require a factory reset (which doesn't preserve userdata on these units)
Will try the cold boot and see if I can live with that, otherwise it may be back to Malaysk ROM (which worked great on my PX5). Anyone know if the issue is resolved on that ROM?
I'm also annoyed that it was sold as supporting bluetooth tethering, but does not actually do so, but turning that option on is what killed my PX5, so I'm reluctant to mess with that.

Just seen that a new firmware is out, so might try that.
UPDATE2: Ignore below. Firmware update didn't fix it.
UPDATE:
Firmware HA3_rk3399_10.0_ota(20210507)升级包 seems to have solved it, and also solved the issue where Car Launcher wasn't updating track names and album art reliably.
I'll confirm tomorrow when the radio has had more time to idle, but I think this is the fix!
As a bonus, I was able to dirty flash without issue. Had to re-root but that's to be expected.
I first updated the MCU to 3.75B and that did not fix it, so an MCU update probably isn't necessary.

Pumpkin brand PX30 MTCE HT - seeking MCU update

Hi,
I have a PX30 head unit with Pumpkin branding.
I've updated the ROM to Hal9k which is great but the unit often fails to boot sitting on a black screen. Repeated attempts to reset the unit, and it eventually turns on.
Auto sleep is not working either so its always cold boot, even if the unit has only been turned off a few seconds.
I would like to try updating the MCU software but cannot find a file.
The version info is: MTCE_HT_V3.60_1, Aug 14 2020 10:19:07
I have tried to register for manufacturer forum to ask there but didn't get a response for account approval.
If there is a newer version that would be great, equally the same version or an older version that is known to be stable could also help me.
Thanks!

Looks like I managed to answer my own question, I found version 3.71 on a German forum, here is a link to it.
210.4 KB file on MEGA
mega.nz
Still don't have the sleep working, if I change it to delay shutdown or sleep it makes no difference and its a cold boot every time. I've checked my wiring and I'm sure the unit is still getting +12v from the car when ignition is switched off.
Anything else I can try or check?

Hello, try if you don't have Default power status - OFF: Factory settings/126/Other/Default power status - set ON or if the radio does not remember saved stations, then set: remember last state.

Pavel-71 said:
Hello, try if you don't have Default power status - OFF: Factory settings/126/Other/Default power status - set ON or if the radio does not remember saved stations, then set: remember last state.
Click to expand...
Click to collapse
Hi, I tried this, the power settings don't make any difference.
If the unit is only off for less than say 1 hour, it will boot up again OK. It's not instant on like some youtube videos, maybe 10-20 seconds. I guess this is still standby mode?
If the vehicle is parked overnight, unit will not boot, just get a black screen. It takes several (usually 10+) attempts to reset it before it eventually boots.
This is really annoying, is there anything else I can check? The only thing I didn't change yet is the "customer type" number, would this make any difference?

Changing the customer version is not recommended, serious control errors and sometimes a black screen may occur, but it is up to you if you take that risk. Sometimes a new MCU update will make this change. The last number after the underscore indicates the customer version, MTCE_HT_V3.60_1, the last one is 1 so the customer version will be 1. If you have updated the MCU this may have changed. It is best if you have saved the factory settings in the dmcu.cfg file, with this file the MCU will be updated and all settings will be returned to the original settings. Factory settings - EXPORT button and save the dmcu.cfg file to external storage, if you do not specify a path, it is saved to the root directory by default. If the error was caused by the update to Hal9k, then the problem may be with this update, try to update again with wipe data or reinstall the original ROM. If that doesn't solve the problem, try a different car type in the canbus factory settings. Or the canbus adapter may be faulty.

Thank you, that is helpful. The unit was already doing this before any updates, I was hoping that updating the ROM and MCU would help but it seems to have made no difference.
I don't have a canbus adaptor.