yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] erkme73:
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...
[Android Head-Units] psyko_chewbacca:
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.
[Android Head-Units] Timsche2210:
Hey guys,

Got the problem that my Witson PX5 with Android 9 start with wifi on and in 80% after a few minutes it automatically turns off - no chance to reactivate the wifi toggle.

I bought it from the official store at aliexpress and opened a dispute because the can bus adapter did not worked.

After get 80 bucks back I cannot open a second dispute tot solve this problem with the seller.

What are now corrective actions which I can realize?

RegardsTimo
[Android Head-Units] Fratopolis:
How does the device boot. I had this exact issue. Do you have it set to auto sleep in settings>car>extras or turn off after a set time?
[Android Head-Units] sergialess:
Rooted, script applied with Tasker, and working great so far. Big thanks to [MENTION=7047926]Hazard15301[/MENTION] and b-max.
[Android Head-Units] Hazard15301:
I know that Hal9k's rom as of 3.1 has this fix built into it now. Not sure about Malaysk's.
[Android Head-Units] sergialess:
I've applied it to a stock rom, not a custom one (which is great anyways).

I've never tried Hal9k or Malaysk roms. Are they that good?.

Edit: OK, this is not working all the time. Sometimes the USB host device dissapears and there isn't much you can do. I'm going through further investigation and tests.
[Android Head-Units] Buranax:
I soldered the gl850g chip to gl852g on my hizpo headunit. Wifi and bt works now. Original problem was I had to reset the headunit ten times to get wifi work.
[Android Head-Units] Kagol:
I'll join to the conversation. I have XRC MCU with android 8 hal9k now, but previously I had stock Android 8.0. I had the same problem with wifi&bt, so suggesting this thread I removed my GL850G usb hub and replaced with GL852G bought from Aliexpress, but now my wifi&bt totally not work. Maybe I soldered the smd in wrong way, this is my first time soldering smd in practice. Please have someone look at it

Now my console prints this error:

Is it caused by problems with my current usb hub?
[Android Head-Units] sean19661:
Trash it

I had the hipzo unit with the same wifi/Bt problem. I sent it back and went with eonon GA2170B never looked back
[Android Head-Units] Kagol:
Thank you but I have no money to trash it and buy new one. Today I soldered back my old gl850g usb hub and now wifi, bt and front usb works after the device heats up. So gl852g is not a solution for my case?

EDIT: Software fix (script) for wifi totally not work for me.

EDIT2: The manufacturer of my device claims that only IC ordered from him will works good.

EDIT3: The IC ordered from manufacturer works good.
[Android Head-Units] slytherinz8:
Update,, i saw in youtube that his headunit will loose internet when time isnt correct, am not sure but my time is set right but i still went to settings and changed from gps auto time adjustment to network time adjustment and somehow i get to make net working
[Android Head-Units] rt83:
Hi

I have some china radio with px5 core board

I have same problem no wifi and usbport2 not working...

I looked on mainboard but i dont have this kind of chip (usb host controller)

Mine is using a USX2064-AEZG

Hiw i can root my device without using wireless adb...cuz i dont have wifi rigth now

So i cant use tasker ...
[Android Head-Units] Skrzypol:
PX5 MTCE Malaysk 3.5 (oreo)

Having a problem with the tasker fix, I believe someone from this thread also had it - once added to tasker, while trying to execute it responding with Error 127. Knowing the error as "Command not found" I'm suspecting something is wrong with the sh file with the script, but I cannot identify what exactly. All is done properly along with the steps presented in the middle of this thread. The usb is 1-1 for sure.

Does anybody encountered a similar problem and could guide me on how to solve it?
[Android Head-Units] Adam_32:
Hi !

I have this radio from ISUDAR:

Wi-Fi not working:

VIDEO

Help me! :(
[Android Head-Units] magick81:
Hi there

I'm the guy who was getting error 127 with tasker.

Never got a good answer from anyone I asked about it, but I did find a way to get around the problem. Whenever it boots up with no Bluetooth or wifi I go into tasker, hit the menu with the dots and reboot to recovery. Once in recovery I reboot again and its works. 100% of the time. Good luck
[Android Head-Units] cgigate:
Went throughout this thread , not get any solution.

I have PX5 (Joying Brand) head unit for few years. the Wi-Fi has problem after every few months after a factory reset.

the system comes back from sleep would not have wi-fi unless doing a cold reboot. I can switch the setting to disable "ACC for sleep" to work around, but every-time to wait few minutes to let system boot up to be able to use it..
[Android Head-Units] majkel84:
Hi,

One question, what's the best and simple solution to this issue? :(
[Android Head-Units] erkme73:
Yes, I'll post the link here in a bit when I get to my PC.

Fwiw, I never did apply the update (MCU or new factory ROM) since I really like the Hal9k ROM, but I will try it today. Just getting tired of redoing all the apps and settings.

The seller replied this am with an MCU link, telling me the techs want me to downgrade the MCU from 2.89 to 2.84. I cannot see how that could possibly make a difference but I will humor them.

As for your approach working from recovery, might I suggest that the slightly longer boot time may be giving the electronics a bit more time to warm up? It seems by the second or third reset/power-cycle the wifi/bt works... Unless I had the unit in the freezer. Then it'll take quite a bit longer.

In any case, if I leave the unit on for 10 min after initial power up with no wifi/by, and the do a normal power-cycle, the wifi comes on 100% of the time. But since I use apps that require immediate BT access (torque logging) that's not particularly practical.
[Android Head-Units] psyko_chewbacca:
I don't know but I've had this issue for quite some time now and before I found out about the recovery trick, I had times where Wifi/BT would not come back up after quite a few reboots. By the third or fourth reboot, it should have warmed up enough to get back online but it sometimes didn't. Now winter is approaching so ambiant temperature at rest is a lot lower than a couple months back and I consistently make it work through the recovery reboot on the first try.

I'm not saying that your theory is wrong but from my point of view, I don't see the temperature being a factor here.

Also, if this issue is only relevant to XRC units, temperature has little to do since the same Wifi/BT module is used across a good range of non-XRC head units.
[Android Head-Units] marchnz:
Just a hunch - try carefully remove glue with solvent from board around wifi/BT md725 area.

Also, has anyone measured +5 supply at the md725 in cold state, during boot and android loaded?
[Android Head-Units] psyko_chewbacca:
My unit has many physical buttons but I enter recovery through the reboot menu supplied in Hal9k's ROM. Navigating the recovery menu is easy as it uses the big volume knob on my headunit. I can also force boot to recovery using that same volume knob. I understand other headunits with less physical buttons might find it troublesome to browse the recovery menu.

Anyway, I'm a bit relunctant to flash the XRC2 MCU image due to the fact that your headunits has much less physical buttons. Maybe the XRC2 firmware is an alternate version of the XRC that simply disabled most physical button interface (or changed code to handle touch sensitive buttons instead of physical ones)! I'll wait for a reply of Seicane on that front! I just don't want to brick my unit.

For my part, I think that what makes the whole "boot through recovery" fix work is not the recovery itself but the sequence that leads to the system choosing to boot to recovery instead of the normal Android OS. My feeling is that the MCU is put in a state that indicates the SOM to boot to recovery (by toggling a pin on the SOM?) and putting the MCU in that state just resets the bit of code in the firmware that handles waking up Wifi/BT chipset.
[Android Head-Units] erkme73:
I think caution is probably appropriate. I don't know enough about compatibility of the MCUs. However, what is certain is that switching from the stock MCU to the downgraded XRC2 does not resolve the problem.

Also, when I booted into the recovery menu and was unable to select "reboot system now", I pressed the reset button (thinking that would act as an enter key), and it reset the radio. When it came up, the wifi/bt was NOT available. So simply entering the recovery menu isn't enough. You actually have to execute the "reboot system now" option.

The reseller has now recommended that I exchange the entire radio again (for the second time). I will have it here on Thursday. I have little faith that it'll work, but other than lost time, there's no expense. Gotta love Amazon.

This morning I once again didn't have wifi. This time, I simply waited 5 minutes with the radio on, and did a power cycle, and then wifi was available. I know that recovery menu boots work 100% of the time, but in my case, a cold unit (ambient or intentionally chilled) means 100% repeatable failure if I don't either wait for it to warm up, or use the recovery boot method you suggest.
[Android Head-Units] Hazard15301:
I've had both XRC and XRC2 mcu's flashed on my radio, and there was no discernible difference or issues with operation and physical buttons. Also, mine came with XRC 2.92 stock, so there is a newer version out there. But I had the same issues with wifi and bt on that mcu, so that's not the solution. I can also confirm that regular reboots will fix the problem about 50% of the time. Recovery reboots work 100% of the time, regardless of temp. It's been down in the 20's here lately.

Keep up the good work guys. Lot's of good research going on here. I'm still waiting on my seller to send a replacement chip, so we'll see how that goes when I receive it.
[Android Head-Units] erkme73:
Just to be clear, your seller is sending you the wifi/bt chip - the one that is soldered on - not the core board that is a daughter-board with pins, correct? I am so baffled as to why the system 'overlooks' the cold hardware flaw when booting from recovery. You would think if it's a hardware issue (a failed chip, bad solder, improper voltage, etc) then it wouldn't matter how the OS boots. Likewise, since this seems to happen to so many people, it just seems improbably that it's a defective component - but rather a bad design. Frustrating.

On the upside, my replacement unit was upgraded to NDA, so I'll have it tomorrow. It's going straight into the freezer when it arrives.
[Android Head-Units] Hazard15301:
Right, this guy here:
[Android Head-Units] erkme73:
I'm on pins and needles, brother. I'll keep my fingers crossed for you. The numbers on your chip are identical to mine - which I guess is to be expected. I'm curious if what they're sending you will also have the same numbers.

ETA: With a pic that clear, I did a little looking on Google for the chip info. There are an additional 6 solder points on the bottom edge of this board. I hope you have good soldering skills!

Also, it appears there are a number of chip variants - they all have the rtl8723BU main number, but different sub numbers. Maybe revisions? Or special features. Very interesting and intriguing.
[Android Head-Units] psyko_chewbacca:
I've been checking some head unit motherboard schematics (couldn't find a pdf for XRC board variants) and I noticed in all of them that the only signal that could switch ON or OFF the Wifi/BT module is WIFI-PWR which is coming directly from the SOM. MCU apparently does not interface the Wifi/BT in any way! Unless there's something really different on the XRC variant, it would seem only the SOM and Wifi/BT modules are part of the equation...

So this WIFI-PWR signal is in charge of switching ON and OFF the 3.3V supply line to the Wifi/BT module. Of course, if 3.3V line is not turned back ON when waking up, that would explain why the Wifi/BT module is unavailable.

So if anyone has disassembled his unit and has this Wifi/BT issue, please kindly probe the 3.3V line when Android reports the module unavailable to see if power is indeed applied to the module.

Here's a picture that identifies the 3.3V line on the module:

After that, we need to figure out a way to toggle this WIFI-PWR pin on the SOM to maybe try and power-cycle the Wifi/BT Module.
[Android Head-Units] erkme73:
Thanks for doing the research on the pin-outs. When your post came through, I was just in the middle of a freeze-cycle for further testing on my soon-to-be returned unit. Timing was perfect.

I pulled the unit out of the freezer, removed the top/lid and headed to the car with the meter and your photo.

The unit powered up, and has been 100% the case when it is this cold, no wifi/BT. I then metered the two pins (albeit in reverse polarity) and, unfortunately, the card IS getting the proper voltage (see photos).

Now, immediately following this, I power-cycled the unit to make sure it hadn't warmed up enough to cause the chip to activate. When it came back up, wifi/bt was still unavailable.
[Android Head-Units] erkme73:
Incidentally, when I researched the chip info yesterday, and found the additional pins on the side, I noticed one of them is a "SUSPEND" pin. So, I think it's possible that this thing goes to sleep and for whatever reason, the SOM doesn't send the wake command under certain (cold) conditions - and sends it everytime when booting from the recovery menu.
[Android Head-Units] psyko_chewbacca:
Thanks alot! That's unfortunate.

Now I need to figure out how to control the WIFI-PWR pin from inside Android OS. Maybe toggling it OFF and then ON could fix the issue without rebooting the system.

Man, I just don't understand why this problem only seem to affect XRC boards if the MCU is not involved. To my knowledge all SOMs are identical, whatever the motherboard variant.
[Android Head-Units] erkme73:
Well, my UPS driver just dropped off my third XRC unit. I just put it in the freezer and will head out to the car in about 20 min. God I hope this one works.

The only rationale I can figure is that perhaps the XRC manufacturer just got a bad batch of radio boards. If it isn't being controlled by the MCU, then, as you point out, it should be differences in that interface. I just wish I knew more about programming and could inspect what the differences are in the booting sequences from a standard reboot/power-cycle/reset vs. the boot from recovery. The answer has to be in there somewhere.
[Android Head-Units] psyko_chewbacca:
I forgot to mention that when Wifi/BT isn't working, usb device RTL8723BU(chipset on MD725 modules) does not show up when enumerating detected USB devices in Android. So it's not just the Wifi/BT stack not working, the device is just not detected by the system.

For reference, the VID:PID of the RTL8723BU is 0bda:b720.
[Android Head-Units] psyko_chewbacca:
Initially, that was what I suspected, however checking both pictures and schematics of the Mainboard, it looks like this pin is not interfaced at all.

Only pins interfaced between module and SOM are 3.3V, GND, D+, D-. The rest are related to the antenna connection so nothing that could explicitely put the chip in suspend.
[Android Head-Units] erkme73:
Well, I'm sad to report that the new replacement unit has the same problem. Warm out of the box it worked. But after being in the freezer for 20 min, no go.

On the upside, on this unit, the recessed reset button works like the large power knob on the units with a physical knob. So I can get into recovery and navigate the menu with that button. That is progress.

However, in messing with the touch key study function under factory settings, I managed to clear out the capacitive buttons. And now they don't respond to any input. I tried relearning them. I even flashed the 2.84 MCU thinking that would clear whatever I screwed up... But nope. It's like they're unplugged.

Time to send another email to the seller...

I think it may be time to return everything and start looking for a non-XRC version that fits the Tundra/Sequoia.
[Android Head-Units] bjt2:
I'm having a similar problem to you, I have the exact same bluetooth/wifi chip (RTL8723BU) as well. The only difference is that my Wifi always works, but the bluetooth stops working after sleep until a reboot. I tried physically removing the onboard module and replacing it with a USB MD725 which didn't fix it, which made me think its either software/OS or MCU related. I have a KGL unit with MX MCU firmware.
[Android Head-Units] Hazard15301:
*edit sorry, I misread your post

Was the onboard module the RTL8723BU or something else?
[Android Head-Units] erkme73:
I just received this from my seller after informing him that the third unit has the same issue:

Who knows what that means, or if it is even true. It may just be their way of trying to keep me from ordering and returning a 4th one.
[Android Head-Units] bjt2:
Yes, same chip set. The USB module works fine with the same factory settings, but it has the same habit of not detecting bluetooth whatsoever, i.e. it doesn't exist in hardware until a reboot. Not sure if this is the same issue but it sounds very similar, but I thought it interesting that its the exact same chip I was having issues with, and that it occurs whether its the internal chip or USB. Shows that its not directly the module's fault.
[Android Head-Units] erkme73:
I'm curious what the age range of the radios are that are having this issue. All of mine were built in August and September of this year, purchased on Sept and October.

My seller claims this is a "recent" problem. Given that XRC is the only manufacturer of the pk5 for the Tundra/Sequoia trim, unless I'm willing to go with a universal double-din and matching trim kit from scoshe or metra (and I don't think they look good compared to the XRC version), I'm stuck with fixing it, living with it, or waiting until they have their @#_! together for a replacement.

I'm ok with mine now that I can boot straight to recovery with the reset switch, and thereby overcome the cold environment failure. However I cannot get the other buttons to anything. I swear, if it's not one thing, it's another.
[Android Head-Units] erkme73:
Last night, I swapped the new display (the one with the reset button that works to get me into/navigate the recovery menu) with the unit I was getting ready to return. I now have a fully functional unit (less wifi when it's cold) that I can directly enter the recovery menu. So I'm happy.

But, one thing I did notice that lends credibility to your theory [MENTION=1143298]psyko_chewbacca[/MENTION] - when I'm 'cold' and have no wifi/bt, the USB port on the front of the radio is also dead to the world. Interestingly enough, the USB port cable that comes off the back of the unit must not be on the same internal hub - as it works 100% of the time.

The attached photo shows the USB port on the front. Certainly is one more data point to consider.
[Android Head-Units] erkme73:
I had something interesting happen this afternoon when I went to drive my truck for the first time today. Despite being only 30° outside, when the screen came on, it was instantly the desktop. It had been more than 18 hours since I last powered up the radio, and it hadn't shut down fully (what I call 'sleep').

When I swapped displays two days ago, I never changed the sleep setting from "auto sleep" to "1 Hour" - which is what I had done on the previous radios.

I assumed that 1 hour was the longest it would go before going into sleep mode. Apparently "auto sleep" lets it go much longer than 1 hour.

In any case, when it came up, the wifi and BT icons were present! I then drove for about 5 minutes, and left off for about 3 hours. When I came out, to start the car, the radio once again was instantly on... but this time, BT and wifi icons were missing.

Up until this even, I've never had the icons disappear if the radio hadn't gone to sleep. For whatever that's worth.

Also, the color "element" side buttons were off. I had to do to car/factory settings/other and change the keys from White to RGB LED. I've never changed that setting before, and it was working fine yesterday - so something went into the MCU settings and changed it. I'm officially befuddled.
[Android Head-Units] erkme73:
In an interesting development (for me), the seller has indicated that latest shipping units (from the manufacturer in China) have the WIFI/BT issue resolved. He's asking that I ship my unit back to them (a NJ address) and once I provide him with a shipping receipt, they will send out a properly working unit directly from China. He says that it will take "a long time" before those units populate the Amazon inventory system, so this would be the fastest way to get get resolution.

IF the unit I would receive from China is 100% functional, then this decision would be an easy one. However, I'd hate to do this dance only to find out it has the same problem. Especially considering I still have about 3 weeks of Amazon's return window available to me. If I mail this thing to him tomorrow, I don't know how they will ship it. If it gets here within 3 weeks, I suppose I could return that one to Amazon. But if it takes a month to get here, I'm SOL if it doesn't perform. 1st world problems, I know.

None of this helps you guys with units that are not under warranty. However, if you still have a line of communication with your seller, and you're within your warranty period, it may be worth pursuing this angle. At a minimum, let them know that at least one other Amazon seller has indicated XRC has fixed a known issue, and is shipping functional units.
[Android Head-Units] psyko_chewbacca:
I found out about this too. USB Bus 1 seems to go directly to the troublesome Genisys USB hub, on my unit, this hub is feeds the Wifi/BT module, the USB OTG port on the front of the unit and the backside USB port that isn't labeled "DVR". When the Wifi/BT is not detected, all these device won't be either. So my assumption is that the XRC motherboard are populated with a USB hub chip that does not sit well with Android while other variants of motherboards must have other types of USB hub chips on them.

I guess this is a situation that only occurs when running Android Oreo. These motherboards must have been used for quite some time and I don't think the issue we're experiencing was this prevalent on units running previous versions of Android.

Anyway, I'll contact my seller and hopefully he'll be able to provide a solution. If nothing can be done, i'll just rewire the USB lines coming from the SOM to my own USB HUB board.
[Android Head-Units] Hazard15301:
Is your guy in Piscataway, NJ? Sounds like we might be dealing with the same guy. I sent him a message regarding these new units, hopefully he'll be open to an exchange. Still waiting on that chip, but it's sounding more and more like the issue lies somewhere else.