PX5 GPS accuracy - MTCD Android Head Units Q&A

Hi,
i downloaded a few GPS test apps, and the best result i got was 15m.
How many satellites did you get, and how many meter accuracy?
How to improve GPS reception?

That's what I got

this is my test

PX5 Glonass Not use
He sees the satellites, but he does not use them

PX5 Glonass Not use

Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.

kesztió said:
Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.
Click to expand...
Click to collapse
This is the PX 5-2G HA unit Marshmallow ROM I own.
Upgrading the ROM of this unit to oreo.
And this is JOYING's FYT based PX5 unit.
It is obviously a problem of ROM that oreo ROM can not use GLONASS. If you want the accuracy of the position information downgrade to marshmallow or buy a FYT unit is early.

warata said:
This is the PX 5-2G HA unit Marshmallow ROM I own.
Upgrading the ROM of this unit to oreo.
And this is JOYING's FYT based PX5 unit.
It is obviously a problem of ROM that oreo ROM can not use GLONASS. If you want the accuracy of the position information downgrade to marshmallow or buy a FYT unit is early.
Click to expand...
Click to collapse
Thanks, Warata, but I still have some problems and questions.
1. The “good” configuration with Marshmallow on your photo still shows an accuracy as bad as 6 m. And no words about SBAS, Beidou or Galileo satellites.
2. I think the PX5 bord revision is very important: I have REV 8.0, something like this:
which is based on U-blox NEO M8, while REV 4.0 still uses U-blox 6 or 7. Are you sure they use all the same revision?
3. Is it safe to downgrade across different manufacturers but same PX5 board, same revision? If so, do you have the downgrade kit for Marshmallow in order to make me sure this is the problem? (It should be an update.zip of approx. 1 GB, I’d greatly appreciate if you sent me it by wetransfer, zoltan .at. studiorip .dot. com.)
4. The “native” U-blox application (u-center for windows, you can access the android unit by the U-blox droid center, if both are in the same TCP subnet) shows a bit different: Both GLONASS and GPS are used simultaneously, I can see 2 SBAS satellites, and things get even better if enabling the full power mode. Does it mean that the U-center can bypass the Android driver?
5. Wouldn’t be enough to change just the Android driver, not the whole OS? If so, do you have a clue, how the original U-blox Android driver can be purchased?
Thanks!

kesztió said:
1. The “good” configuration with Marshmallow on your photo still shows an accuracy as bad as 6 m. And no words about SBAS, Beidou or Galileo satellites.
2. I think the PX5 bord revision is very important: I have REV 8.0, something like this:
which is based on U-blox NEO M8, while REV 4.0 still uses U-blox 6 or 7. Are you sure they use all the same revision?
3. Is it safe to downgrade across different manufacturers but same PX5 board, same revision? If so, do you have the downgrade kit for Marshmallow in order to make me sure this is the problem? (It should be an update.zip of approx. 1 GB, I’d greatly appreciate if you sent me it by wetransfer, zoltan .at. studiorip .dot. com.)
4. The “native” U-blox application (u-center for windows, you can access the android unit by the U-blox droid center, if both are in the same TCP subnet) shows a bit different: Both GLONASS and GPS are used simultaneously, I can see 2 SBAS satellites, and things get even better if enabling the full power mode. Does it mean that the U-center can bypass the Android driver?
5. Wouldn’t be enough to change just the Android driver, not the whole OS? If so, do you have a clue, how the original U-blox Android driver can be purchased?
Click to expand...
Click to collapse
Photo 1 and Photo 2 are definitely the same HA unit. Only the difference in firmware. So I can assert that it is a firmware problem that GLONASS can not be used with oreo.　PX5- 4G-KLD Oreo I purchased recently was also unable to use GLONASS.
I upgraded marshmallows to Oreo using the kumarai's upgrade kit.
https://forum.xda-developers.com/android-auto/mtcd-software-development/px5-oreo-rom-t3736950
I attempted to downgrade PX5-4G-GS oreo unit to marshmallow in the same procedure, but that did not work.
JOYING's FYT based unit is totally different on the same PX5, and both GLONASS and BeuDou can be used. However, other satellites can not be recognized.
Other questions are beyond my knowledge. Please wait for other respondents.

Please write
Official Dasaita forum: PX5 Android 8.0 Glonass Not use, Only GPS (USA) http://www.dasaita.com/bbs/viewtopic.php?f=4&p=108

eter711 said:
Hi,
i downloaded a few GPS test apps, and the best result i got was 15m.
How many satellites did you get, and how many meter accuracy?
How to improve GPS reception?
Click to expand...
Click to collapse
Its not really appropriate for GPS to output accuracy in a distance unit. What they output is a level of "confidence" that you are within the GPS's rated accuracy of the position being reported. You can't translate from that measure to a distance unit, so they make something up, usually based on a linear multiple of the rated accuracy.
For instance, it may give you a 50% confidence of being within 6 feet of the reported coordinates. Or it might give you a 90% confidence that you are within 6 feet. In either case, you could very well be within the 6 feet, and in fact, you could be "dead on", but it can only provide you with a probability. Despite that, it may present 50% within 6-feet as a 20 foot radius, or 90% within 6-feet as a 7 foot radius.
Don't get too overly hung up on it. If you want a better idea about how close the GPS reads to reality, open up google maps in satellite view mode, and see how close your physical location is to the center of the target based on landmarks.
---------- Post added at 05:23 PM ---------- Previous post was at 05:18 PM ----------
kesztió said:
Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.
Click to expand...
Click to collapse
Are you sure its really a U-blox? U-blox GPS receivers are among the most notorious for counterfeits. They use some crappy nobody brand gps receiver, and program its microcontroller to communicate as a u-blox.
https://www.u-blox.com/en/counterfeit-products-and-u-blox-brand-misuse

96carboard said:
Are you sure its really a U-blox? U-blox GPS receivers are among the most notorious for counterfeits. They use some crappy nobody brand gps receiver, and program its microcontroller to communicate as a u-blox.
Click to expand...
Click to collapse
I cannot be 100% sure but in U-center it declares itself to be at least M8030 (Actually nobody pretended to be NEO 8M, it was just my thought), and with a correctly placed antenna it indeed can get 100% inside a 2,5 m diameter deviation map, at least for 20-30 minutes. So co-operating by u-center is not an issue. (Though on just 2 Hz with multi-GNSS config (GPS + GLONASS) all GLONASS satellites suddenly die.)
The big problem is with all other 3rd party applications.
Here is the text output at startup:
19:05:23 $GNTXT,01,01,02,HW UBX-M8030 00080000*60
19:05:23 $GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B
19:05:23 $GNTXT,01,01,02,FWVER=SPG 3.01*46
19:05:23 $GNTXT,01,01,02,PROTVER=18.00*11
19:05:23 $GNTXT,01,01,02,GPS;GLO;GAL;BDS*77
19:05:23 $GNTXT,01,01,02,SBAS;IMES;QZSS*49
19:05:23 $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37
19:05:23 $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFFFD*2E
19:05:23 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E
19:05:23 $GNTXT,01,01,02,ANTSTATUS=DONTKNOW*2D
19:05:23 $GNTXT,01,01,02,PF=3FF*4B
So do I have a counterfeit version or not?
*UPDATE* I forgot to update the baud rate to 19200 baud, that’s why the chip apparently hasn’t been able to face 2 Hz multi GNSS. That is, it’s almost sure that the chip is not NEO M8, “just” naked M8030, but at least I simply don’t think such a widely used board like PX5 uses fake M8030 chip. This is ridiculous.

warata said:
Photo 1 and Photo 2 are definitely the same HA unit. Only the difference in firmware. So I can assert that it is a firmware problem that GLONASS can not be used with oreo.　PX5- 4G-KLD Oreo I purchased recently was also unable to use GLONASS.
I upgraded marshmallows to Oreo using the kumarai's upgrade kit.
I attempted to downgrade PX5-4G-GS oreo unit to marshmallow in the same procedure, but that did not work.
JOYING's FYT based unit is totally different on the same PX5, and both GLONASS and BeuDou can be used. However, other satellites can not be recognized.
Other questions are beyond my knowledge. Please wait for other respondents.
Click to expand...
Click to collapse
JOYING's FYT based unit on PX5 is also Android 8 Oreo or just an earlier version (Android 7 or 6)? (And what does FYT mean?)

kesztió said:
JOYING's FYT based unit on PX5 is also Android 8 Oreo or just an earlier version (Android 7 or 6)? (And what does FYT mean?)
Click to expand...
Click to collapse
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
https://forum.xda-developers.com/an...iew-joying-px5-2gb-android-version-8-t3789422

warata said:
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
Click to expand...
Click to collapse
Tying to understand.
The hardware (PX5 Rev. 8.0) is the same, just the software is different? Or there are different PX5 boards for FYT and QD respectively?

warata said:
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
Click to expand...
Click to collapse
Do you know which on-board GPS chip is used on FYT versions? For HCT this chip is U-blox M8030 but for FYT this can be different.

I present to you my way of improving GPS accuracy: using a Holux M1000, connected to navigation via bluetooth ( Bluetooth GPS apk from Market). I also tried U-Blox7, but the result is even worse than with the native receiver. HCT-PX5, rev.10.

The notion of "accuracy" in GPS is not nearly as straightforward as you may have been lead to believe. In fact, most of these GPS HAL's will be fudging the accuracy based on the HDOP value. HDOP means "horizontal dilution of precision". While a smaller DOP value does typically indicate a greater precision, it is in NO WAY related to horizontal accuracy in terms of an actual distance, which is what Android reports.
In other words, if you're using an NMEA GPS, then you can basically ignore the reported accuracy in Android -- its meaningless.
Now there are ways to get more reasonable values, but this requires you to deal with the binary format that is output by your GPS module, not the standard NMEA output. For example, using the gpsd Android HAL (https://gitlab.com/gpsd/gpsd/-/tree/master/android), because gpsd uses the binary format for some GPS units (ublox in particular), it will output a reasonable distance for accuracy.

Very interesting ! Can you tell us how to do it on ours devices ?

fratellos said:
Very interesting ! Can you tell us how to do it on ours devices ?
Click to expand...
Click to collapse
If you can build Android from source, you just add gpsd to your local manifest and device makefiles, and remove the nonsense hal they previously included. However, as this thread appears to be related to chinese "px5", its not that simple. I'd say you would have to build it in AOSP, then manually copy in the files needed for it.
But the bottom line is really this; you don't actually need to do this. Making the accuracy values correct won't change the actual accuracy of the gps output, so all you really need to do is IGNORE the accuracy value.
If you want to get a picture of what the actual accuracy of your gps is, hook it up to a gnu box, let it get a fix with gpsd, and see what accuracy it spits out, then just remember that number and substitute in your head.
Automotive navigation doesn't actually require all that great of accuracy. If its accurate to within a few HUNDRED feet, that's good enough, because the software will snap your location to the nearest road anyway.

Related

seicane unit?

Not many manufacturers make head units to match my car, a 2004 C5, even less with the newer PX5 units. I did find this one,
https://www.seicane.com/android-199...mirror-link-backup-camera-dvr-obd2-dab-s32577
Anyone familiar with this brand? Do they make their own or repackage?
What 2004 C5 is? (I expected a Citroën C5)
the link you provided is for a 2004 Audi Series (A4, A3, A6)
I think the same Audi you linked is on Daasaita (HotAudio):
https://es.aliexpress.com/store/pro...2804594516.html?spm=a2g0v.12010612.0.0.cLbLd3
ikerg said:
What 2004 C5 is? (I expected a Citroën C5)
the link you provided is for a 2004 Audi Series (A4, A3, A6)
I think the same Audi you linked is on Daasaita (HotAudio):
https://es.aliexpress.com/store/pro...2804594516.html?spm=a2g0v.12010612.0.0.cLbLd3
Click to expand...
Click to collapse
Audi C5 is the Volkswagon/Audi platform code,
https://en.wikipedia.org/wiki/Audi_A6#C5_.28Typ_4B.2C_1997.E2.80.932004.29
What I need is for the A6 only, not the A3 or the A4. The A3 and A4 both use a different size face plate. I need one for the A6 from those years specifically.
anyone have one of these Seicane units?
is there any reason to think it's any different than the other PX5 units as far as modding and firmware upgrades?
thanks!
Hello, yes I do have a unit bought by Seicane SELLER.
Seicane is just reseller and you will get all sorts of units built buy other MANUFACTURERS if you buy from them.
In my case I bought a unit for Subaru and found it to be an MTCD device built by Klyde (MCU manufacturer code: KLD).
So as of my current knowledge you won't really know what manufacturer built your unit until you check the system about screen for the real manufacturer. And as a result the devices are no different than the ones bought by any other reseller.
Don't buy from them, they have worse to NO service at all!
I have a broken (warranty) seicane unit, i am mailing with them now for 1,5 month to get instruction how to send back.
They give bull**** answers or ask bull**** questions to keep you waiting, after a while they stop responding.....
I advise do absolutely NOT BUY from them, just a worse and also expensive seller....
B3rt said:
Don't buy from them, they have worse to NO service at all!
I have a broken (warranty) seicane unit, i am mailing with them now for 1,5 month to get instruction how to send back.
They give bull**** answers or ask bull**** questions to keep you waiting, after a while they stop responding.....
I advise do absolutely NOT BUY from them, just a worse and also expensive seller....
Click to expand...
Click to collapse
Seicane are a seller not a manufacturer, there are no "Seicane" units.
Whats wrong with your unit ?
typos1 said:
Seicane are a seller not a manufacturer, there are no "Seicane" units.
Whats wrong with your unit ?
Click to expand...
Click to collapse
I know they are sellers and not manufactors, but have no idea who is the manufacturer.
But warranty is given by a seller, not a manufactor, they sell it as there own but give no support what so ever on it.
If you have a problem they simply ignore it and hope you stop complaining and so there problem is gone.
Please make sure if you buy from China that you chose a seller which does give support!
The problem with my unit is it does not turn of anymore.
When plugged in it directly boot up, also when acc is off, when acc is turned on and off agin it should turn off by ACC control through can-bus control.
It seems can-bus is not working properly anymore....
When i asked support i get the most stupid answers such as:
check the 12V acc wire is connected... DUH there is no 12V acc wire in my car, it is fully can-bus, also there is NO 12v acc wire in the connector of the radio!
This then i get 4 times to check!
Now i get 5 weeks (i contact them 3 times a week) that there engineers are checking the software, FIVE WEEKS !!!!!
I am now aprox 9 weeks contacting them how to solve this (the unit was when i first reported it under warranty, now it is out of warranty...)
I never buy/order from them again!
I hope no one does!
B3rt said:
I know they are sellers and not manufactors, but have no idea who is the manufacturer.
But warranty is given by a seller, not a manufactor, they sell it as there own but give no support what so ever on it.
If you have a problem they simply ignore it and hope you stop complaining and so there problem is gone.
Please make sure if you buy from China that you chose a seller which does give support!
The problem with my unit is it does not turn of anymore.
When plugged in it directly boot up, also when acc is off, when acc is turned on and off agin it should turn off by ACC control through can-bus control.
It seems can-bus is not working properly anymore....
When i asked support i get the most stupid answers such as:
check the 12V acc wire is connected... DUH there is no 12V acc wire in my car, it is fully can-bus, also there is NO 12v acc wire in the connector of the radio!
This then i get 4 times to check!
Now i get 5 weeks (i contact them 3 times a week) that there engineers are checking the software, FIVE WEEKS !!!!!
I am now aprox 9 weeks contacting them how to solve this (the unit was when i first reported it under warranty, now it is out of warranty...)
I never buy/order from them again!
I hope no one does!
Click to expand...
Click to collapse
I know a lot of sellers have bad support. I m just trying to see if I can help.
The stereo will have pins for ACC even if the loom does not have wires, what ahv eyout ried so far ? Have you asked on here for help ?
The MCU type will tell you who makes your unit.
typos1 said:
I know a lot of sellers have bad support. I m just trying to see if I can help.
The stereo will have pins for ACC even if the loom does not have wires, what ahv eyout ried so far ? Have you asked on here for help ?
The MCU type will tell you who makes your unit.
Click to expand...
Click to collapse
Yes thx for any help, but the problem is within the canbus decoder i believe.
It is a unit specific for a Mini cooper, it has besides the radio/android part also the dials for fuel, obd and other car control lights etc, these also do not work properly anymore.
This car section is also controlled by the can-bus part of the unit.
The android part itself works fine, it is the can-bus part which is not working properly anymore.
The MCU have the letter KGL in it, i have really no idea who is the 'real' manufactor, but i actually doubt the manufactor will help.
B3rt said:
Yes thx for any help, but the problem is within the canbus decoder i believe.
It is a unit specific for a Mini cooper, it has besides the radio/android part also the dials for fuel, obd and other car control lights etc, these also do not work properly anymore.
This car section is also controlled by the can-bus part of the unit.
The android part itself works fine, it is the can-bus part which is not working properly anymore.
The MCU have the letter KGL in it, i have really no idea who is the 'real' manufactor, but i actually doubt the manufactor will help.
Click to expand...
Click to collapse
Yes, I know the type, it has a round screen. KGL are the manufacturer - Shenzhen Kai Ge Le.
In factory settings, how many options are there for your car, for Minis ?
You can list CAN Bus decoder by manufacturer, how many many are showing for Mini ?
I ask this because you may be able to sort things out by getting a new CAN Bus decoder.
typos1 said:
Yes, I know the type, it has a round screen. KGL are the manufacturer - Shenzhen Kai Ge Le.
In factory settings, how many options are there for your car, for Minis ?
You can list CAN Bus decoder by manufacturer, how many many are showing for Mini ?
I ask this because you may be able to sort things out by getting a new CAN Bus decoder.
Click to expand...
Click to collapse
I will take a look, at the moment the device is stored in a box
Thx for the tip!
Witson sells one for our cars...just picked one up for my allroad
Sent from my iPhone using Tapatalk Pro
Seicane = Bad Customer Service + Do nothing for you after the sale.
I purchased a Head Unit from them back in June 2018. The bluetooth module has never worked and after going around with them about it, they sent me a different module, not the Parrot BT module I purchased originally. Replacement of the BT module requires disasembly of the unit, de-solder old BT, solder new one, but the reason the BT did not work was that a few of the SMD resistors were damaged during build or soldering the BT module in. 3 months since purchase and still dont have a working unit. Now they want me to ship the unit back but I know they will void warrentee due to customer opening the unit (not the factory), and will claim I damaged the board attempting replacement. Oh, did I tell you they never told me the BT module was soldered onto the main board?? When they offered to ship a replacement BT I was under the impression it was a snap in module simular to how PC processors or flat cable connectors lock in. They knew, but dont want to deal with problems.
Remeber, they are only resellers, not the manufacturer. They all buy from the same manufacter for the most part. Good luck if you do get one that works as expected from them.
Seicane:
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Memory: 3891
Kernel Version: 4.4.93+ [email protected] #263 Wed May 9 09:36:56 CST 2018
Build Number: px5-userdebug 8.0.0 OPR5.170623.007 end.hct.20180515.095719 test-keys
MCU Version: MTCE_KLD_V2.80_1 Mar 1 2018 16:54:22
Model: px5(800x480)
Android version: 8.0.0
Android security patch level: October 5, 2017
Dont buy Seicane
I will just add that I purchased from Seicane in May 2018 and at day 174 I have tonight lodged PayPal buyer dispute due to the ongoing issues I have ane the absolutely substandard customer service. Simply terrible. Buyers beware.
If PayPal cant resolve this then I will be offering payment to anyone in the forum who can resolve the issues for me.. watch this space. Dont buy Seicane!
G
Duck020 said:
I will just add that I purchased from Seicane in May 2018 and at day 174 I have tonight lodged PayPal buyer dispute due to the ongoing issues I have ane the absolutely substandard customer service. Simply terrible. Buyers beware.
If PayPal cant resolve this then I will be offering payment to anyone in the forum who can resolve the issues for me.. watch this space. Dont buy Seicane!
G
Click to expand...
Click to collapse
Seicane are a seller only, there are no "Seicane" units.
What MCU do you have ?
What problems do you have ?
typos1 said:
Seicane are a seller only, there are no "Seicane" units.
What MCU do you have ?
What problems do you have ?
Click to expand...
Click to collapse
Hi typos1,
The spec for my unit as follows:-
Head Unit: Seicane s081988f
OS: Android 7.1.2 (Nougat)
CPU: Allwinner T8, 8-core Cortex-A7 @ 1.8GHz
Memory: 2GB DDR3 RAM, 16GB EMMC, 2xUSB2
Display: 9", 1024x600 capacitive
MCU Version: T8.3.19-23-10-E43101-171127
System Vers: V9.2.2_20171202.103838_TW2
Linux Kernel: 3.10.65 (20171129)
Security Patch Level: 2017-07-05, 7.1.2 (Nougat)
Issues still unresolved:
Microphone only works for phone calls, no android apps (no OK google)
Screen calibration slightly off by 0.5cm
Audio from AM / FM radio good, but Android apps (google maps, Spotify, youtube etc) audio louder from front left channel than all other channels
no root, unable to add some apps that I would like
Using AM / FM radio and waze, an alert in waze mutes AM / FM radio and it does not return. This doesn't happen in google Maps
When using google maps, something happens to the audio where it sounds like it changes the audio fade to front speakers more than rear speakers but when this happens the balance between left and right seems to be corrected resolving issue 3. System audio preferences for navigation set to use all 4 speakers but doesnt appear to be working
I suspect that there are other issues that I cant recall right now but whats listed above is enough to be unsatisfied with the product. The primary issues that I need resolved are the Microphone and the Audio being all over the place depending on what app is used. It just needs to be consistently balanced left to right, front to back right in the middle for all apps.
I am not against using an updated system ROM or MCU but I am not knowledgeable in this area and despite doing quite a bit of research I still havent figured out if there is a compatible release that I can apply to my unit, and frankly with all the time invested in research, forums, testing and trying to resolve issues with the re-seller I've got more important things to do with my time (work, family, hobbies)
Any assistance that can be provided would be greatly appreciated and rewarded.
cheers
G
I bought about 9 months ago, directly from Seicane a radio of 9 "android 8 PX5, 8 core 64 bit cortex A53, memory 3891 MB, MCU MTCE HF V2.86 May 28 2018, for a Subaru Forester, the integration and the connectors are excellent but the radio had problems with the bluetooth handled by google and when connecting the cell phone via usb Easyconected, it did not recognize the cell phone, I asked for support but the solution from them was simple, and it was still the same, at the end I found a firmware of Hal9k, I installed to the radio and with this all these problems were solved, the link is "https: //forum.xda -developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477 ", Seicane never respond very bad seller.
Duck020 said:
Hi typos1,
The spec for my unit as follows:-
Head Unit: Seicane s081988f
OS: Android 7.1.2 (Nougat)
CPU: Allwinner T8, 8-core Cortex-A7 @ 1.8GHz
Memory: 2GB DDR3 RAM, 16GB EMMC, 2xUSB2
Display: 9", 1024x600 capacitive
MCU Version: T8.3.19-23-10-E43101-171127
System Vers: V9.2.2_20171202.103838_TW2
Linux Kernel: 3.10.65 (20171129)
Security Patch Level: 2017-07-05, 7.1.2 (Nougat)
Issues still unresolved:
Microphone only works for phone calls, no android apps (no OK google)
Screen calibration slightly off by 0.5cm
Audio from AM / FM radio good, but Android apps (google maps, Spotify, youtube etc) audio louder from front left channel than all other channels
no root, unable to add some apps that I would like
Using AM / FM radio and waze, an alert in waze mutes AM / FM radio and it does not return. This doesn't happen in google Maps
When using google maps, something happens to the audio where it sounds like it changes the audio fade to front speakers more than rear speakers but when this happens the balance between left and right seems to be corrected resolving issue 3. System audio preferences for navigation set to use all 4 speakers but doesnt appear to be working
I suspect that there are other issues that I cant recall right now but whats listed above is enough to be unsatisfied with the product. The primary issues that I need resolved are the Microphone and the Audio being all over the place depending on what app is used. It just needs to be consistently balanced left to right, front to back right in the middle for all apps.
I am not against using an updated system ROM or MCU but I am not knowledgeable in this area and despite doing quite a bit of research I still havent figured out if there is a compatible release that I can apply to my unit, and frankly with all the time invested in research, forums, testing and trying to resolve issues with the re-seller I've got more important things to do with my time (work, family, hobbies)
Any assistance that can be provided would be greatly appreciated and rewarded.
cheers
G
Click to expand...
Click to collapse
You have an Allwinner chipset (not Rockchip or Intel Sofia) and "MTCD" or "MTCE" does not appear in your MCU field, so you dont have an MTCD/E unit and are in the wrong forum, try the Android Headunits general forum.
migcep said:
I bought about 9 months ago, directly from Seicane a radio of 9 "android 8 PX5, 8 core 64 bit cortex A53, memory 3891 MB, MCU MTCE HF V2.86 May 28 2018, for a Subaru Forester, the integration and the connectors are excellent but the radio had problems with the bluetooth handled by google and when connecting the cell phone via usb Easyconected, it did not recognize the cell phone, I asked for support but the solution from them was simple, and it was still the same, at the end I found a firmware of Hal9k, I installed to the radio and with this all these problems were solved, the link is "https: //forum.xda -developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477 ", Seicane never respond very bad seller.
Click to expand...
Click to collapse
Thanks Migcep !! I think you saved me. So little about the same unit I bought for my Forester. Glad you shared your info.

PX3, PX5 or other?

I have a MTCD GS (Xtrons) unit for my Audi (PF75ATTAR). This is a RK3188 unit with Android 5.1. I have installed Malaysk's latest 12.6 ROM for this however I expect this is the last ROM he will be releasing for this platform.
The unit is a bit slow, however the MicroG version of Malaysk's ROM speeds things up. But I still think its time for a replacement.
I am trying to decide on whether to get a PX3 or a PX5 based unit. Both seem to be popular and Malaysk has current ROMs for both. I like the idea of Android 7.1.
Just wondering whether anyone has had or has both currently and their experience/comparison?
Is it worth just replacing the SoM for a PX5 board since the actual head unit hardware is the same?
Andy
ADB100 said:
I have a MTCD GS (Xtrons) unit for my Audi (PF75ATTAR). This is a RK3188 unit with Android 5.1. I have installed Malaysk's latest 12.6 ROM for this however I expect this is the last ROM he will be releasing for this platform.
The unit is a bit slow, however the MicroG version of Malaysk's ROM speeds things up. But I still think its time for a replacement.
I am trying to decide on whether to get a PX3 or a PX5 based unit. Both seem to be popular and Malaysk has current ROMs for both. I like the idea of Android 7.1.
Just wondering whether anyone has had or has both currently and their experience/comparison?
Is it worth just replacing the SoM for a PX5 board since the actual head unit hardware is the same?
Andy
Click to expand...
Click to collapse
Nobody?
ADB100 said:
I have a MTCD GS (Xtrons) unit for my Audi (PF75ATTAR). This is a RK3188 unit with Android 5.1. I have installed Malaysk's latest 12.6 ROM for this however I expect this is the last ROM he will be releasing for this platform.
The unit is a bit slow, however the MicroG version of Malaysk's ROM speeds things up. But I still think its time for a replacement.
I am trying to decide on whether to get a PX3 or a PX5 based unit. Both seem to be popular and Malaysk has current ROMs for both. I like the idea of Android 7.1.
Just wondering whether anyone has had or has both currently and their experience/comparison?
Is it worth just replacing the SoM for a PX5 board since the actual head unit hardware is the same?
Andy
Click to expand...
Click to collapse
I'd say px5 with 4gb ram. If you can't find one then 2gb ram.
Because they are making an Android Oreo build for px5.
ADB100 said:
Nobody?
Click to expand...
Click to collapse
Try @Hal9k_'s ROM, use the microG settings, its easily the best and fastest RK3188/PX3 ROM.
Hes even made the Nougat ROM from the RK3188/PX3 Nougat SoMs work on the 1Gb version, although its not as fast as his Lollipop ROM and is just the standard Nougat ROM (rooted), made to work non Lolliop units, he is working on a custom Nougat version that will work on both 1Gb and 2Gb RK3188/PX3 units.
However, you could probably very easily remove gapps and replace with microG yourself to make it faster, theres a guide for doing it (to Lollipop units) in the forum, just removing about 5 apps and installing microG.
Of course a 2 or 4GB RK3368/PX5 will be faster and newer, but @Hal9k_'s ROM will give your old unit a new lease of life.
I can't recommend the px5 for the unstable rom and no improvement in an year.
I haven't tried the others (px3) but even slower hardware is better with stable software.
I'm also disappointed about the functionality in general, you can't set stay on without ignition and go to sleep after half an hour, there is no low voltage shutoff, the device drains the battery well below 10 Volts and goes in an reset loop at low voltages disturbing other can bus devices some till some failure. Switched off by power button still takes nearly full current.
Not a device to put in an car overall.
iwl said:
I can't recommend the px5 for the unstable rom and no improvement in an year.
I haven't tried the others (px3) but even slower hardware is better with stable software.
I'm also disappointed about the functionality in general, you can't set stay on without ignition and go to sleep after half an hour, there is no low voltage shutoff, the device drains the battery well below 10 Volts and goes in an reset loop at low voltages disturbing other can bus devices some till some failure. Switched off by power button still takes nearly full current.
Not a device to put in an car overall.
Click to expand...
Click to collapse
I decided on a PX5 board with 32GB ROM 2GB RAM which took only a couple of weeks to arrive from China (Witson) and its working fine in my MTCD(now E) GS unit. The hardware behaviour is exactly the same as it was with the PX3 board (which I would expect as I haven't changed the MTCE hardware). The unit powers off with no ignition (as it did previously which I don't see as an issue?) and I don't have battery drain. I can only think you have it wired wrong or you have faulty hardware?
I installed Malaysk's 6.2 ROM and have installed my own apps and its all good. I have issues with the integration with the car (CANBUS) but these are exactly the same as they were with the PX3 - I don't think anything but new firmware for CANBUS decoder will fix these issues.
Andy
iwl said:
I can't recommend the px5 for the unstable rom and no improvement in an year.
Click to expand...
Click to collapse
Here I tend to partially agree. However Android 8 might be available as custom ROM on PX5/2GB/4GB units soon. There are official Android 8 preinstalled PX5/4GB boards available already but it's still not clear whether we can upgrade PX5 2GB SoM and the PX5 4GB SoM which were shipped with Android 6. Probably this will be sorted out soon.
What kind of instabilities are you referring to in particular?
I am asking since my PX5 with stock KLD ROM from November 2017 is quite stable. At least no app crashes and similar issues. Despite the famous Google Maps hanging which seem to be mainly related to Google Maps code itself and there is a work-around for it.
iwl said:
I'm also disappointed about the functionality in general, you can't set stay on without ignition and go to sleep after half an hour, there is no low voltage shutoff, the device drains the battery well below 10 Volts and goes in an reset loop at low voltages disturbing other can bus devices some till some failure. Switched off by power button still takes nearly full current.
Click to expand...
Click to collapse
Not sure what would cause this. My unit enters standby immediately after ignition is off. Then it kills all applications to avoid any background process waking the device (which is btw. the root cause for some app issues). In Standby mode my device draws very little power. I didn't have a single issue even after the unit being on standby for more than a week when the car was not in use. If concerned you might connect a battery watchdog in between the unit and the car so when voltage drops below a certain treshold it would cut-off the head unit from power.
If the unit would have such a battery watchdog implemented that would of course be great but I guess the units were built to keep a certain price range and in most cases such a watchdog is not required.
Though I understood that some cars do not have an ignition trigger any more but get their power-on signal on canbus. Here I could imagine that the canbus adapter perhaps need additional power to listen to canbus wakeup events. Not sure about this scenario though as my car has an ignition cable connected to the head unit.
I fully agree to the "unable to turn on when ignition is off" issue. This is usually possible with factory head units but MTCD/MTCE units seem to be mostly unable to be powered on without ignition. The only work-around I can currently imagine is to mount a switch which shorts battery+ to ignition input on the head unit which would allow you to manually power it up. Also such a switch can be combined with a small electronic timer. So it would be medium difficulty to mount a button which pulls on the ignition line on the head unit to 12V for 30 minutes and then resets. Still a pity it's not built in I agree.
iwl said:
I can't recommend the px5 for the unstable rom and no improvement in an year.
I haven't tried the others (px3) but even slower hardware is better with stable software.
I'm also disappointed about the functionality in general, you can't set stay on without ignition and go to sleep after half an hour, there is no low voltage shutoff, the device drains the battery well below 10 Volts and goes in an reset loop at low voltages disturbing other can bus devices some till some failure. Switched off by power button still takes nearly full current.
Not a device to put in an car overall.
Click to expand...
Click to collapse
You ignition/sleep problems will be down to your car and/or the CAN Bus decoder, not the stereo, as will whether the unit can be powered on or off with the ignition on.
I ve not heard of anyone saying the ROM is "unstable" before. In fact I ve not heard of any of your problems before, only the GPS bug and the BT/mic probs which you dont mention.
It sounds to me like your stereo has not been installed properly.
Many are just lacking deeper technical knowledge to see that problems I have investigated.
Or try to fix it with cooling fans.
I have a original mercedes radio having the missing features it is just a matter of proper engineering.
Yes it is not android computer I would like to have but not crashing every hour and at the end the car distracted by.
Don't tell it works just count the posts.

Xtrons Head Unit - Pretty bad. anything I can do?

I bought a car that came with an Xtrons Android 10 IN70PTFL Head unit - So far I am pretty unimpressed with it.
it has android 10, a RK-PX30 and 2gb ram.
Its pretty slow overall. unresponsive. Google Maps is terrible on it (either crashes completely, or takes absolutely ages to load maps even when I have downloaded them for offline use. I tried downloading the App "Offline Maps" which worked ok for a while, but then started crashing.
Is there anything I can do to make this thing better? Maybe a firmware upgrade or custom rom or something?
Sorry if obvious. I'm very new to these head units.
If it is an MTCD/E, upgrading the SOM to PX5 or 6 might be an option. Otherwise, do you have an adjustment hammer.
Hi
I have a similar problem
i have a XTRONS PX6 ANDROID 10 MTCE GS V3 53 3
I can not connect to my wifi terminal while not passing my phone it goes without problem.
in addition the time is not updated automatically by the GPS while I have everything set up ...
It does have developer options but nothing I can see to cut memory or display speed tweaks.
Mines OK but quiet slow for 2gb of ram, but I'm guessing if the processor is pants there's not a lot to be done.
I've ran android speed up apps but no difference if not a little slower
There's got to be something but I'm not that technical to know on these units. Maybe a processor overclocker if we can get root.
I'll have a play when I've time, but if anyone has had success it would be good to know.
Use hammer method.
marchnz said:
Use hammer method.
Click to expand...
Click to collapse
Might need to do a step by step tutorial complete with pictures for this highly undocumented but incredibly effective method that works with all models regardless of whether MTCD/E.
Xtrons are still selling 2GBram/32Rom devices now and for silly money: https://xtrons.co.uk/audi-various-android-12-octa-core-2gb-ram-32gb-rom-qea12uca12a4r
I bought mine (GS) from them in 2018 and it was 4GB ram then, for much less. It's been great but they would not be my first choice now. 2GB ram was barely adequate with Oreo 8, much less with later Android versions.

Carplay on Joying HU Low FPS

Hey all, first time posting here so please let me know if this isn't the right place. I bought a Joying head unit, and so far it's awesome. I haven't installed it yet but I have been testing it with a DC supply since my engineering school has lots of tools for that kind of stuff.
In the android home screen, everything works awesome. It's smooth, customizable, and is filled with features. It has the CarLink app for Apple Carplay, which is the main reason for buying the headunit, and that unfortunately seems to be the weakest link. The FPS is low, and not smooth at all like I've seen in the videos for Joying head units. This supports wireless carplay, and it's the same performance wired or wireless.
Here's a video showing what's happening:
The lag is also very noticeable when I call Siri, since the bubble that pops up is SUPER choppy and awful to look at. Can anyone tell me if there's a way to fix this? My specific model is the JY-UQB09N4G-H.
On a sidenote, this isn't as important but it's still annoying, but WiFi is off every time I reboot the head unit, even though I turned on the option for turning wifi on after boot in the wifi settings. I'm currently using home wifi to get this thing setup. Is this not an issue if I fast boot in my car when the +12V line is always powered?
Having the same problem on my new 11.6”. Any fixes?
Same here... any fix in the meanwhile?
As soon as i use the "old" Carlinkit adapter, it is smooth as butter since you can set it to 60 FPS.. unfortunately siri does not work with it.
Joying released a new version of their carlink apk last November.
Did you already try that one? first option.
Updated Firmware
www.joyingauto.com
surfer63 said:
Joying released a new version of their carlink apk last November.
Did you already try that one? first option.
Updated Firmware
www.joyingauto.com
Click to expand...
Click to collapse
Will try that, thanks!
Theyve also sent me the newest firmware which i couldnt find on the Homepage:
Android 10.0 1280X800 2021.12.23.zip
https://drive.google.com/file/d/12-SR2xh49oj8Ri3aM0eNz5g4XPo5b2ja/view?usp=sharing
for this Device:
Joying 10.1 Inch VW Skoda Seat Autoradio 1280x800 Screen Resolution Head Unit
SKU: JY-VQD10N4G-DAShip From: Chinese/EU WarehouseOS: Android 10.0CPU: Octa Core 1.8GHz. 64-bit high-performance processorRam:LPDDR4 4GB Rom:Samsung 64GB1). 10.1 Inch HD 1280*800 IPS Screen Radio.2). Support Carplay&Android auto, Bluetooth, Navigation, FM Radio, 5GHz WiFi, SPDIF&Optical Digital...
www.joyingauto.eu
I have no clue what the changes are to my 2021.11.16 version.
I will give both options a try and keep you updated

Question Has anyone tried to enable AM Brdcast rcv on SC7731 (UIS8141) low-end units?

I recently purchased an iMars branded low-end (1-16) Android 8 head unit from Banggood and of course, immediately pulled it apart and took photos and made notes of the ICs, layout, etc.
I was looking all over the board for the broadcast band radio chip and found all antenna lines led to the CPU (GPS, WiFi & FM).
When I looked-up the specs for the UIS8141e - SC7731 uP, I saw it's an all-in-one SOC that also has GSM baseband modems.
So - my question is this:
If this chip is capable of receiving FM broadcast via a DSP in the uP chip, and I have seen on some other (Banggood) HU specs that units with AM capability specify the same processor (might be false Chinese description though) , is there a driver, app or other software that can enable AM bad receive on the SC7731?
Unfortunately, the SC7731 datasheet is sketchy on RF capability details.
I have searched XDA and 4PDA forums for details and found none (except Russia doesn't use AM radio).
Any ideas?
Thanks
bigbop said:
I recently purchased an iMars branded low-end (1-16) Android 8 head unit from Banggood and of course, immediately pulled it apart and took photos and made notes of the ICs, layout, etc.
I was looking all over the board for the broadcast band radio chip and found all antenna lines led to the CPU (GPS, WiFi & FM).
When I looked-up the specs for the UIS8141e - SC7731 uP, I saw it's an all-in-one SOC that also has GSM baseband modems.
So - my question is this:
If this chip is capable of receiving FM broadcast via a DSP in the uP chip, and I have seen on some other (Banggood) HU specs that units with AM capability specify the same processor (might be false Chinese description though) , is there a driver, app or other software that can enable AM bad receive on the SC7731?
Unfortunately, the SC7731 datasheet is sketchy on RF capability details.
I have searched XDA and 4PDA forums for details and found none (except Russia doesn't use AM radio).
Any ideas?
Click to expand...
Click to collapse
I have a UIS8141e-SC7731. Tapping System Info pops up radiotype:F Si47xx_f474x(0).
this family of chips provide FM/AM some do Shortwave also. The specs for the AM look good but the reception is poor on the head unit I have. I suspect poor input circuitry from the ANT.
jimw1024 said:
I have a UIS8141e-SC7731. Tapping System Info pops up radiotype:F Si47xx_f474x(0).
this family of chips provide FM/AM some do Shortwave also. The specs for the AM look good but the reception is poor on the head unit I have. I suspect poor input circuitry from the ANT.
Click to expand...
Click to collapse
Is your FM reception OK?
If not either you might need an antenna amplifyer.
surfer63 said:
Is your FM reception OK?
If not either you might need an antenna amplifyer.
Click to expand...
Click to collapse
NO it is a few db down from my OEM and another regular aftermarket radio.
I was thinking it may need to be amplified. The datasheets for the Si47xx eval boards show using amp for the AM circuit. The RF front end does suffer on this unit.

Categories

Resources