Got my Head unit from Pumpkin in Jun 2015. Had no major problems with it until December 2015. Drove for 4 hours with the head unit running TomTom with no problems. Went to use the car the next day and the headunit's screen was just black, the backlight was lit up and all features still worked. Poweramp would load up and start playing music off the SD card and I can get the radio to work. I can even change the station using the touchscreen.
This leads me to this it's the LCD that gone faulty. Just wondered if anyone has any idea I could try to fix it.
Been 3 months without the head unit now, so just wondered if anyone can think of something to check on the unit, or if anyone knows what screen it uses?
I've tried checking the connections for the board and the screen, but couldn't see any problems.
Specs of the unit are:
800x600
RK3066
Ram: 1GB
CPU: armv7 1.6GHz (x2)
MCU: MTCB-KLD2-V2.50
KLD
Thanks
fpscod said:
Got my Head unit from Pumpkin in Jun 2015. Fitted it to the car, Had the custom rom from on here had a reverse cam installed and had done the external mic fix.
Specs:
800x600
RK3066
Ram: 1GB
CPU: armv7 1.6GHz (x2)
MCU: MTCB-KLD2-V2.50
KLD unit
Had no major problems with it until December 2015. Drove for 4 hours with the head unit running TomTom with no problems. Went to use the car the next day and the headunit's screen was just black, the backlight was lit up and all features still worked. Poweramp would load up and start playing music off the SD card and I can get the radio to work. I can even change the station using the touchscreen.
This leads me to this it's the LCD that gone faulty. Just wondered if anyone has any idea I could try to fix it.
Been 3 months without the head unit now, so just wondered if anyone can think of something to check on the unit.
I've tried checking the connections for the board and the screen, but couldn't see any problems.
Thanks
Click to expand...
Click to collapse
Can you send the product's link? I want to know more about the product details before helping u.
fpscod said:
Got my Head unit from Pumpkin in Jun 2015. Had no major problems with it until December 2015. Drove for 4 hours with the head unit running TomTom with no problems. Went to use the car the next day and the headunit's screen was just black, the backlight was lit up and all features still worked. Poweramp would load up and start playing music off the SD card and I can get the radio to work. I can even change the station using the touchscreen.
This leads me to this it's the LCD that gone faulty. Just wondered if anyone has any idea I could try to fix it.
Been 3 months without the head unit now, so just wondered if anyone can think of something to check on the unit, or if anyone knows what screen it uses?
I've tried checking the connections for the board and the screen, but couldn't see any problems.
Specs of the unit are:
800x600
RK3066
Ram: 1GB
CPU: armv7 1.6GHz (x2)
MCU: MTCB-KLD2-V2.50
KLD
Thanks
Click to expand...
Click to collapse
Had the same problem with mine, this may sound stupid but have you tried the reset button. I pushed the reset on mine and the screen worked again when it rebooted, it has done this twice where I would lose the display but all else would work. I have reflased the rom and have not had the problem since.
the reset is a small hole on the front of the unit.
Paul2482 said:
Had the same problem with mine, this may sound stupid but have you tried the reset button. I pushed the reset on mine and the screen worked again when it rebooted, it has done this twice where I would lose the display but all else would work. I have reflased the rom and have not had the problem since.
the reset is a small hole on the front of the unit.
Click to expand...
Click to collapse
Hey Paul,
Have given it a go a few times. Did you press it whilst it was on? and for how long?
Also, what rom did you put on after?
Cheers!
Paul2482 said:
Had the same problem with mine, this may sound stupid but have you tried the reset button. I pushed the reset on mine and the screen worked again when it rebooted, it has done this twice where I would lose the display but all else would work. I have reflased the rom and have not had the problem since.
the reset is a small hole on the front of the unit.
Click to expand...
Click to collapse
Hey Paul,
Have given it a go a few times. Did you press it whilst it was on? and for how long?
Also, what rom did you put on after?
Cheers!
Pressed it when it was on, the unit should shut down and then restart. Rom I got from autopumpkin.com it's there stock rooted rom android 4.4.4 duel core
Paul2482 said:
Pressed it when it was on, the unit should shut down and then restart. Rom I got from autopumpkin.com it's there stock rooted rom android 4.4.4 duel core
Click to expand...
Click to collapse
Gave it another go but no luck. Thank for the suggestion though.
Currently awaiting (Since Jan) for a replacement screen from pumpkin. They have not been helpful.
Might give it a go at flashing the pumpkin rom without the screen on
Hi, Have a similar problem I have a Pumpin 10 4gb ram 32 rom. The screen is blank but the backlight work. I have no sound and nothing works, however, if I turn it off and on again every now and again I get something like Pumpkin 10 for a split second then the blank screen.
I tried the reset button a few times but nothing
So I bought -what I believe- is this Android Head Unit over a month back (Apparently I can't post links yet, but if you search Amazon for "Car Stereo Touch Screen Bluetooth GPS DVD Double Din In Dash Sat Navigation Vehicle Head Unit for VW Volkswagen Jetta Golf Passat Tiguan T5 VW Skoda Seat Hands Free Call Free Map Backup Camera" the result is the item that I got. ) It worked fine once I got it installed, then about a week ago it started having issues (Screen would freeze, buttons unresponsive, and would stay like this until car had been off for some time. Still switched to backup camera on reverse.) I tried to go into settings and do a factory reset to see if that would fix the issue, but now it's stuck with a black screen and the word "Erasing". It still seems to be doing something because overnight the next time I come out the screen is on and it says, "Recovery 7.1.1 :failed to mount /cache (invalid argument)" I've tried several different button pressing methods to try and get to the recovery screen, but it just keeps coming back to the "Erasing" screen regardless of whether I use the Reset button or the Power button (held). I have a couple pictures of settings from the "Droid Info" app (because I couldn't find anything helpful in the settings themselves) that I took before I started having problems with it. So I'm looking for some help regarding getting it into recovery and/or finding out what I'm doing wrong.
Brand is confusing, roundabout on Amazon I found "Malanzs", but it looks exactly like and has the same Manufacturer # as the TMOTEC brand (DS02P051S01C0) and a lot of the pictures of the Malanzs one look like they photoshopped them from the TMOTEC pictures.
One of the things I was trying to find on my pictures but I don't have is the MCU version (apparently this is important for where I will get the most help with my post)
Any help is appreciated, thanks for your time.
I can't help get it working (it sounds defective), personally I'd return it to Amazon quick !
MrGubby said:
I can't help get it working (it sounds defective), personally I'd return it to Amazon quick !
Click to expand...
Click to collapse
Thanks for the response, I'm in communication with the seller to try and get it returned, but as it's been longer than a month, it's outside of Amazon's return period. I was just hoping to possibly find a solution here.
im not sure the region in which u live ...
but sounds like it possibly overheated ...
and something fried,
ive a px3 rockchip 7.1 hizpo (for ford fusion/f150/exploders)
had it bout idk 8 months, put in some nice sundown 12's in my trunk w/a 40k orion amp and between that and summer in full swing early, im drawling alot of heat, and the same things happenin to mine...
seems over 96 degrees the unit just shats on it self...
the heads still on but android system(ui) crashes...
imma try these few idears while i wait for my px5 upgrade to get here from ebay...
other then this fabricating trick,
im outta suggestions... ive tried everything to get it too
function correctly, even sit in a ice box ova ac just to keep it cool...
anyways ...
these were for px5 but hw as i understand is same under the hood...
:good:
https://youtu.be/k4HYcKsszsg
https://youtu.be/C-s2FN3VeAc
Hi,
There's an issue that has been mildly bugging me since I have had my Android Head Unit. Just wondering if I'm the only one or if this is a known issue.
Sometime when starting the car and the Head Unit powers up, the bluetooth and Wifi radios are not working. My phone cannot connect via bluetooth and the Wifi activation slider in the Wifi Setting menu will not move to the "activated" position.
Usually, a full system restart fixes the issue but I've had occurence where a second reboot in a row is necessary!
This has been going since I have had the unit. I didn't stay on stock ROM for long as I moved to Malaysk first and now using Hal9k ROM. Both ROMs exhibit the same issue. Point is I don't know if the stock ROM had this issue.
Head Unit is equipped with a MD725 version 1 radio module.
Does somebody have a workaround (other than rebooting)?
Thanks!
EDIT: Please check this post for a detailed explanation of the cause of the problem, the resolution process and finally provides fixes for it.
psyko_chewbacca said:
Hi,
There's an issue that has been mildly bugging me since I have had my Android Head Unit. Just wondering if I'm the only one or if this is a known issue.
Sometime when starting the car and the Head Unit powers up, the bluetooth and Wifi radios are not working. My phone cannot connect via bluetooth and the Wifi activation slider in the Wifi Setting menu will not move to the "activated" position.
Usually, a full system restart fixes the issue but I've had occurence where a second reboot in a row is necessary!
This has been going since I have had the unit. I didn't stay on stock ROM for long as I moved to Malaysk first and now using Hal9k ROM. Both ROMs exhibit the same issue. Point is I don't know if the stock ROM had this issue.
Head Unit is equipped with a MD725 version 1 radio module.
Does somebody have a workaround (other than rebooting)?
Thanks!
Click to expand...
Click to collapse
How disappointing to see that no one has replied. I purchased a Seicane unit from an Amazon seller two weeks ago, and among the things I noticed immediately was the frequent, seemingly random WIFI/BT disconnect. As you described, it happens when waking up. Either pressing the reset button or holding the power button for >5 seconds has returned their functionality every time (so far). But, in corresponding with Seicane, they act like it's the first time they've heard of it. They want to replace the WIFI module. But, I'm sure that'll take weeks, and by the time it gets here, I'm outside the return window with Amazon.
I'm fully stock, and I really like the fit and finish in my Tundra.
Can I thread-jack and ask you some questions to see if you have other issues like me?
- Google account sync is missing calendar (and chrome too, for that matter). That means any calendar app (stock or 3rd party) cannot access events. Do you see calendar under settings/accounts/google/sync?
- Side-loading apks is a no-go. Whether I use file manager, or the default "Apk-installer", when I try to install an APK (even OEM legit ones on the internal memory), I get a momentary flash of "package install.." then right back to the file list. Seicane doesn't seem to understand the issue, even after I sent them a video of how it's behaving.
- Fader is not working. I do have left/right, but when I move fader to rear, everything goes quiet. It seems front and rear are combined, because full front has sound coming from all speakers. That's not a deal breaker since I generally listen to podcasts, and not music.
Just knowing there's someone else out there with similar issue(s) is comforting.
Seicane = Bad Customer Service, No Support after they have your money
I purchased a Seicane Nav/Radio Unit back in June 2018, and from day 1 the Parrot Bluetooth module I paid extra for has never worked. Did everything recommended, used their BT apk, tried setting up via Phone apk, changed name of BT module, change passcode to 0000, 1234, 01234, but it never saw my BT enable Phone or Tablet that was within 2 foot of the Head Unit, nor did my phone or tablet ever see the Head Unit.
I have been going back and forth with Seicane, and after 3 months got them to send me a replacement BT Module. They shipped me an unmarked module that does not even look like its Bluetooth other than the 10 pins at the bottom of it for mounting. Oh, no instructions, no explanations, nor did they tell me the Head Unit needed to be COMPLETELY disassembled to get at the existing BT module. Once opened it was apparent that the module was soldered in requiring de-soldering of the old, and soldering in the new. Problem was while inspecting how to do this I found 3 SMD resistors on the main board that were damaged during manufacturing, so now I know why the BT never worked! I assume they knew it also, and that is why they sent me the replacement module knowing that if I opened the case, the factory warrantee was then void. So now they want me to spend $60 to ship the Head Unit back to them in China, and of course, they will void the warrantee and change me $60 to get it back.......NEVER AGAIN WITH SEICANE.................
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
I have similar problems, i thought that only the "XRC" units (MTCE_XRC_...) ones had the problem with WiFi and Bluetooth not working sometimes when you start.
From what i saw, a restart sometimes fixes it.
Somebody said that entering into recovery and then restarting seems to always fix the issue, but it's still annoying.
Until somebody finds a "real" solution, we're stuck with restarting the unit if the WiFi/BT doesn't work.
You could try using an USB adapter for the WiFi and Bluetooth, the ones i had (for my PC) didn't work, probably we need something designed for Android.
P.S. the problem is not from custom ROMs, it does the same with the ROM that it came with.
Well, that's not very promising. I initiated the refund/return process for mine with Amazon. I have about 10 days left before the return window closes. So glad I bought from AZ vs. AliExpress or directly from Seicane.
There's another seller of the PX5 (Hizpo) that is custom fit to my Tundra, but uses the button-less trim. I'm hoping that it doesn't have this issue.
On an aside, I figured out why my APKs wouldn't side-load. Under settings/car/factory defaults/other is a setting called "install apps" which was set to disabled. Switching it to enabled allowed me to install all my favorite 'patched' apks. Unfortunately, the intermittent wifi/BT is a deal breaker. I'm hoping Seicane can come up with a fix/workaround suggestion in the coming days - else, this one is getting picked up by the big brown truck.
verszipo said:
I have similar problems, i thought that only the "XRC" units (MTCE_XRC_...) ones had the problem with WiFi and Bluetooth not working sometimes when you start.
From what i saw, a restart sometimes fixes it.
Somebody said that entering into recovery and then restarting seems to always fix the issue, but it's still annoying.
Until somebody finds a "real" solution, we're stuck with restarting the unit if the WiFi/BT doesn't work.
You could try using an USB adapter for the WiFi and Bluetooth, the ones i had (for my PC) didn't work, probably we need something designed for Android.
P.S. the problem is not from custom ROMs, it does the same with the ROM that it came with.
Click to expand...
Click to collapse
Yeah, if I can't find a satisfactory solution, my backup plan is to mount a USB hub behind the radio and use a USB Wifi/BT adapter.
From what I read, the Comfast WU725B is compatible with the android headunit. It's probably the same chipset that is used on the internal MD725 module of the head unit!
psyko_chewbacca said:
Yeah, if I can't find a satisfactory solution, my backup plan is to mount a USB hub behind the radio and use a USB Wifi/BT adapter.
From what I read, the Comfast WU725B is compatible with the android headunit. It's probably the same chipset that is used on the internal MD725 module of the head unit!
Click to expand...
Click to collapse
I've got that Hizpo arriving on Wed. If it has the same issue running stock (as the Seicane XRC) does, then I'll be happy to give the WU725B adapter a go. I just wonder why there aren't more people complaining about this phenomenon given the popularity of the PX5 systems.
psyko_chewbacca said:
Yeah, if I can't find a satisfactory solution, my backup plan is to mount a USB hub behind the radio and use a USB Wifi/BT adapter.
From what I read, the Comfast WU725B is compatible with the android headunit. It's probably the same chipset that is used on the internal MD725 module of the head unit!
Click to expand...
Click to collapse
I'd be interested to know if this works. I found a thread where others have done that to fix BT call issues. Apparently it's not just plug and play in most cases.
https://forum.xda-developers.com/an...ons-development/bluetooth-usb-dongle-t3684383
Same unit, different issues...
Hazard15301 said:
I'd be interested to know if this works. I found a thread where others have done that to fix BT call issues. Apparently it's not just plug and play in most cases.
https://forum.xda-developers.com/an...ons-development/bluetooth-usb-dongle-t3684383
Click to expand...
Click to collapse
Hi,
I think I have the same unit - I too had issues with Bluetooth, but after a factory reset it seemed to behave itself. The only downside is the hardware buttons on the facia (its a merc slk 200 type facia) are now not working! navi, setup, BT, 1-6, power etc all not responding. I'm a bit of a newb when it comes to the hardware side of these android head units - am I missing some sort of interface APK that helps the hardware buttons talk to the android OS?
Sorry for thread jacking, but I'm starting to get a bad feeling - I purchased from seicane direclty and so far, the support feels like one guy doing it after he gats back from the factory...
For ref I took some pics and a video of the issue - any hints?
https://photos.app.goo.gl/WRrc69Qr3CpFaTq7A
I believe it MTCE_MX2_V2.94_1 on 8 core 64-bit coretex-A53 @ 1.5Ghz
px5-userdebug 8.0.0 OPR5.170623.007
xboson said:
Hi,
I think I have the same unit - I too had issues with Bluetooth, but after a factory reset it seemed to behave itself. The only downside is the hardware buttons on the facia (its a merc slk 200 type facia) are now not working! navi, setup, BT, 1-6, power etc all not responding. I'm a bit of a newb when it comes to the hardware side of these android head units - am I missing some sort of interface APK that helps the hardware buttons talk to the android OS?
Sorry for thread jacking, but I'm starting to get a bad feeling - I purchased from seicane direclty and so far, the support feels like one guy doing it after he gats back from the factory...
For ref I took some pics and a video of the issue - any hints?
https://photos.app.goo.gl/WRrc69Qr3CpFaTq7A
I believe it MTCE_MX2_V2.94_1 on 8 core 64-bit coretex-A53 @ 1.5Ghz
px5-userdebug 8.0.0 OPR5.170623.007
Click to expand...
Click to collapse
You need to go into the Factory Settings menu, under the Panel Key Study header and manually set all your physical buttons
Hazard15301 said:
You need to go into the Factory Settings menu, under the Panel Key Study header and manually set all your physical buttons
Click to expand...
Click to collapse
Hi,
Yep - tried that - a couple of times (factory settings code 126) - tried reset and panel key study - nothing appears on screen. Tried waiting a minute or two but no dice. I'll try again just to be sure and report back.
---------- Post added at 10:02 PM ---------- Previous post was at 09:52 PM ----------
xboson said:
Hi,
Yep - tried that - a couple of times (factory settings code 126) - tried reset and panel key study - nothing appears on screen. Tried waiting a minute or two but no dice. I'll try again just to be sure and report back.
Click to expand...
Click to collapse
Yep - so just tried that page again - waitied about a minute and a half - nothing showed up - blank page & no response to any hardware buttons on the facia - the canbus based steering wheel answer, hangup and volume controls work as expected. So it should just detect the hardware buttons no issue? No special apk needed?
erkme73 said:
I've got that Hizpo arriving on Wed. If it has the same issue running stock (as the Seicane XRC) does, then I'll be happy to give the WU725B adapter a go. I just wonder why there aren't more people complaining about this phenomenon given the popularity of the PX5 systems.
Click to expand...
Click to collapse
The new hizpo unit worked GREAT! No dropouts. Well, at least not for the first 10 min... After that the screen went dark. Resetting and power-cycling made it beep and the buttons illuminated green for about 2 seconds... But that was it.
I did an exchange through Amazon and the replacement arrived today. On power up, no wifi or BT. ARG. I did a power-cycle, and both came back. I went to vehicle several more times during they day/evening, and despite cold booting, wifi resumed each time. Fingers crossed, but I'm guessing it will disappoint me soon.
I sent a message to the seller asking for stock MCU and firmware images, but I'm sure that will be met with crickets.
Will update if anything changes.
That didn't take long. Got in truck this am to find no wifi. Took FOUR resets for it to finally wake the wifi/bt. Really frustrating. Took a video and sent it to the Amazon seller (JBY TECH) asking what I need to do to get a functioning unit. If I do another exchange it'll be the third unit. This sucks.
Wish I could get a non-XRC unit that fits my Sequoia.
Growing more frustrated and impatient by the day, I opted to remove the back of the radio (which leaves the factory warranty seal intact) to get a better view of the wifi/bt components. The thing is tiny - smaller than a postage stamp. It appears to be soldered directly to the main board at 8 points - though the ones on the left are hard to identify due to the hot-glue applied to the antenna wire connection point. These points are not surface-mount sized. A steady hand with a standard iron should be able to comfortably resolder these connections. I would attempt it if out of warranty and all other options have been exhausted.
I did push down on each joint before re-assembling the unit. After several power-cycles, WIFI/BT remain on. The acid test will be in the AM. I am reluctant to even post this now, as I don't want to jinx it. I will post updates as they happen.
erkme73 said:
Growing more frustrated and impatient by the day, I opted to remove the back of the radio (which leaves the factory warranty seal intact) to get a better view of the wifi/bt components. The thing is tiny - smaller than a postage stamp. It appears to be soldered directly to the main board at 8 points - though the ones on the left are hard to identify due to the hot-glue applied to the antenna wire connection point. These points are not surface-mount sized. A steady hand with a standard iron should be able to comfortably resolder these connections. I would attempt it if out of warranty and all other options have been exhausted.
I did push down on each joint before re-assembling the unit. After several power-cycles, WIFI/BT remain on. The acid test will be in the AM. I am reluctant to even post this now, as I don't want to jinx it. I will post updates as they happen.
Click to expand...
Click to collapse
The seller of my radio thinks I have a bad chip as well. He's sending me a new chip, should be here monday. So I'll be doing this exact procedure when it gets here. I think someone else said there's ten total solder points, and two are real close together and very easy to short together.
I was wondering why it is that wifi and bt will remain functional across short term sleep cycles, but only seems to act up when left in sleep overnight (at least that's how it works in my case). Not sure if that points to a software or hardware issue.
Hazard15301 said:
The seller of my radio thinks I have a bad chip as well. He's sending me a new chip, should be here monday. So I'll be doing this exact procedure when it gets here. I think someone else said there's ten total solder points, and two are real close together and very easy to short together.
I was wondering why it is that wifi and bt will remain functional across short term sleep cycles, but only seems to act up when left in sleep overnight (at least that's how it works in my case). Not sure if that points to a software or hardware issue.
Click to expand...
Click to collapse
I'm no engineer, but if I unplug all wires from the back of the radio and leave it de-energized for an hour, I would think that any residual electrons would be gone - or at least comparable to an overnight connected shut down. The fact that it still works after that hour makes me think it's hardware.
The one variable that changes overnight is temperature. The unit cools down completely overnight, and by morning the symptoms return. I suppose I could take the radio and put it in the freezer/refrigerator for a few hours and see if recurs.
If it is temp, that would lend credence to poor electrical connections - with the most likely suspect being the hand-soldered points (not the SM-ed board components). Admittedly, it's a stretch.
If your seller has OK'ed the replacement of your board, if I were you, I'd practice with the old one and re-solder those 8-10 points.
I recall reading posts elsewhere stating that keeping pressure on that board resolved the issue (one guy wrote about using tape!).
I just received word from the seller that they suspect the "core board" to be the problem. They want me to open the case and unplug/replug it to see if that resolves it. I've attached their photo. If it does not solve the problem, they suggest replacing it, and they provided a link to the latest XRC firmware (XRC8.0_20180510). I'm downloading it now.
Looks like when daylight comes, I'll be doing some vendor-approved dissection...
New daylight, and with permission to disassemble, I managed to get a better picture of the wifi/bt module. Unless there are pins underneath the board, it really looks like 8 connections.
I removed the 'core board' and replaced it. No wifi/bt. After third power-cycle it came up.
I really think this is temperature-related. By the 2nd or 3rd reboot, the electronics have warmed up and it starts working. Now I have to wait until it gets back to ambient temp to do more testing. To prove this theory, I've placed it in my freezer. I'll give this a go in about 30 min. If it stop working again, I think that would be pretty conclusive. Will update as I proceed.
After leaving the unit in the freezer for 30 minutes, the wifi/bt once again stopped responding. In fact, it stayed off for about 5-10 minutes (regardless of the number of power-cycles/resets). I even held down on the wifi chip and it made no difference. Only after it had completely thawed out and warmed up did it re-enable.
I'm going to relay this back to the seller. FWIW, since they provided me with a factory rom and MCU image, I took this chance to install the Hal9k rom. WOW is that worth it...
erkme73 said:
I just received word from the seller that they suspect the "core board" to be the problem. They want me to open the case and unplug/replug it to see if that resolves it. I've attached their photo. If it does not solve the problem, they suggest replacing it, and they provided a link to the latest XRC firmware (XRC8.0_20180510). I'm downloading it now.
Looks like when daylight comes, I'll be doing some vendor-approved dissection...
Click to expand...
Click to collapse
Could you upload the MCU update image?
Interesting stuff about the temperature. Quite frankly I had this ruled out since rebooting through recovery fixes the issue 100% of the time while normal reboots only works sporadically. I was under the impression that the issue was related to the MCU or some other component not waking up the device from sleep when unit wakes up.
Hi everyone,
first of all, my apologizes in advance for duplicating the thread, but I've got the feeling that the original HERE is not in the right place, and therefore I've got 0 comments since open.
Therefore, I transcribe the problem here.
After buying an android head unit for the Fabia mk3 from my wife and testing it at my workshop, I got mad because the front panel buttons were not working. I was almost giving up when I decided to install the radio anyway just to profit from the navigation by forcing us to use it only by the touchscreen, when I found out that the front panel buttons get activated only when the head unit receives the can-bus signals.
However, some days after the installation and the happiness of solving the issue, big surprise when we found the car with the battery dead. o after bringing it back to life, I removed the android radio and checked the current drainage. It was around 300mA for the car switched off. Too much for a car that is parked so long due to the COVID-19 quarantine.
After asking Google, I found out that in the new VAGs, included the Fabia mk3, there is no longer a "switched-off" power cable arriving to the radio. Only an "always-on" one. It seems that the original radio is being switched off by the can-bus signal, bringing the current drainage to a minimum. What is this minimum, I do not know as I haven't measured it.
This doesn't seem to be the case with my android radio which is sucking 300mA when turned off by the can-bus.
So I looked for a "switched-off" signal from the fuse panel and I brought it all the way up to the radio to force the total current shut-off when switching off the car.
Happy with the solution, my wife takes the car again some days after and and told me that the radio was not starting. I went to check it and I found the unit getting blocked at the "android" starting screen.
Sometimes it ends up just blocked there. Sometimes shows an alternating picture between the word "android" and a kind of arrow picture. I share here a couple of screenshots and a small video.
I've tried the reset button, even with the 15 seconds wait, and nothing happens, I get the same blocked starting screen...
Any ideas what can this be? It looks pretty damn bricked to me but I refuse to give up with the radio, it looked very well installed in the car and I was able to "taste" the capabilities right before the battery drainage and it was even sounding better than the ****ty original radio.
Here the head-unit specs:
Android 9.0 System
Capacitive Screen HD 1024*600 1080P HD Video
CPU Rockchip PX3 Cortex A9, 4 core 1.6GHz
2GB DDR3 RAM Memory
16 GB Nand Flash