yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] erkme73:
Well, he's having me send it to Piscatawy, yes... But, unless the guy is an insomniac with really poor English writing skills, I'm guessing he's actually in China, and the NJ address is simply their freight handler/broker.

The seller goes by JBY TECH on Amazon, and the name he's having me send it to in NJ is Henry.

I was supposed to send it to him in NJ today, but I sent him a followup email this morning asking if I can't just return it to Amazon (free return, and more secure for him). I don't expect an answer until at least 1A CST.

What I can't grasp is how they continue to sell the remaining stock in Amazon. His store front shows 10 units available with Prime shipping. If this is really an issue, you'd think they'd immediately pull the remaining stock and replace it. Especially considering their expense to swap. I've now sent back two defective units to Amazon, and I'm trying to do it with the third one. He's sending the replacement from China with DHL. Unless they have 1000% margins on these things, I don't think they can do that very often before they start losing real money.
[Android Head-Units] Hazard15301:
Yea, Henry. Answers your messages at like 4 in the morning? I sent him a message, so hopefully tomorrow I'll have something.

---------- Post added at 01:16 AM ---------- Previous post was at 01:06 AM ----------

I've always figured that in cases like this, they bank on the average end user not noticing or caring enough to go through the trouble of returning it.
[Android Head-Units] erkme73:
You're probably right - especially if they leave the sleep timer set at auto (and not setting it to something less). Ever since I've done that, my radio wakes up instantly in the morning, and in all but one instance, the radio came alive.
[Android Head-Units] Hazard15301:
I leave it set to auto, I just assumed the unit turned off after the set time if set to anything else. I need mine to wake up instantly because I do my DOT logging on the unit.

Also, talked to the seller about these new units that are supposedly coming out. He said he wasn't aware of any manufacturing defect and he would look into it. So either the emails are starting to pour in and he's losing money on exchanges, or he's not the same guy and genuinely doesn't know.
[Android Head-Units] erkme73:
We shall see... My third unit is on its way to Piscataway. UPS says it arrives there tomorrow. He said they would have the factory ship out a working unit as soon as he had the tracking info on my return. I haven't seen anything indicating that's happened yet, but if it's really going DHL, it should be here in 2-3 days after shipping. It would really suck if this new unit is no better...
[Android Head-Units] Hazard15301:
There are some new units coming over from China that are CNS2 units, not MTCD or MTCE. Not too much info available on these yet. Maybe these are the "new units" that the shipper is speaking of. Fingers crossed for you.
[Android Head-Units] erkme73:
Oh God, that would suck... I hope that's not the case. Really like hal2ks rom
[Android Head-Units] muzica9:
problem is from usb hub gl850g. on 2018 mainbords, xrc made some modification. now there is no direct connection between px5 coreboard/soc and md725 bt/wifi chip. manufacturing fail problem.

you should ask for revised mainboard with other version for usb hub, or for an older mainboard from 2017/2016
[Android Head-Units] erkme73:
This is an interesting claim. Do you have any supporting information that I could forward to the seller? I do not know what the solution is that XRC is providing, but according to the seller, they have fixed it and will be shipping it directly from the factory. I am awaiting tracking info. He said they would "test" it before shipping, but unless they put it in a freezer first, I don't know what testing will reveal.
[Android Head-Units] muzica9:
yes. i work directly with xrc factory. and i reported back in may 2018, when they released the new layout of the mainboard. only happens with px5 because of android 8.0. on px3 android 7.1, no problem. they say that newer mainboard will have different version usb hub. probably gl852g. might work or not. did not test it yet.
[Android Head-Units] erkme73:
I am hopeful but will see. I'll post my findings when it arrives.
[Android Head-Units] Hazard15301:
Is there a way to fix this, for people that are out of warranty or unable to exchange? Also, what correlation do cold temperatures have with this issue?

Also, found this post about wifi and cold temps:

4pda, Translated

Very interesting read. There might be a fix in here but I haven't read all the way through it yet. A lot of it gets lost in translation, and I don't fully understand everything. This guy here broke the contacts on the wifi/bt chip and rewired it - HERE.

If anyone wants to read through this thread, there's talk of a script (towards the end) by user "b-max" that resets the usb hub without a reboot, but I haven't found it yet. Theres over 450 pages to that thread, it's a lot to go through.

*edit

Found it, HERE. Too tired to read anymore though.
[Android Head-Units] erkme73:
Wow, what a find, [MENTION=7047926]Hazard15301[/MENTION]. This is the best part:

If I read the translation correctly, the implication is, with the missing screw from underneath the module, the core board can curl up on the edges (due to the aluminum moving more than the PCB) when cold. Since the wifi module (via USB) pins are on the outer edge, the lifting of the board basically unplugs those pins. Once warm, it relaxes and the pins get plugged back in.

On the surface, that looks like it explains the behavior I've seen. However, it does not explain why it works when booting from the recovery menu. Logically, one would think if this is a mechanical disconnect due to temperature, then it shouldn't work at all - until the connections are physically reestablished. Unless, of course, booting from recovery loads a different set of usb drivers and there's an alternate pathway to that module?
[Android Head-Units] Hazard15301:
I edited my post with new info that explains this. Best part is that script that resets the usb hub. I also seem to recall them talking about working with Hal9k to integrate this into the next version of his rom. If that script works, someone should reach out to him about that. But for now it seems we can plug that script into tasker and be done with this issue. But it's too late for me to go outside and mess with it. I'll be doing this first thing in the AM. Seems promising!
[Android Head-Units] erkme73:
Wohoo! Makes me wish I still had my unit. Though I did try to download the rar files in that post, and it came back 404. Sure hoping [MENTION=472138]hal9k[/MENTION] has the goods for this...
[Android Head-Units] Hazard15301:
I'm pretty sure that .rar just has the two scripts in it.

resetusbpower.sh

#! / system / bin / sh
su sh -c 'echo "0"> / sys / bus / usb / devices / 1-1 / authorized'
su sh -c 'echo "1"> / sys / bus / usb / devices / 1-1 / authorized'
sleep 1
su sh -c 'svc wifi disable'
sleep 5
su sh -c 'svc wifi enable'

resetusbsleep.sh

#! / system / bin / sh
su sh -c 'echo "0"> / sys / bus / usb / devices / 1-1 / authorized'
su sh -c 'echo "1"> / sys / bus / usb / devices / 1-1 / authorized'
sleep 1
su sh -c 'svc wifi disable'
sleep 30
su sh -c 'svc wifi enable'

Looks like we just need to find out which device our usb hubs are listed as (1-1, someone else said theirs was 3-1)
[Android Head-Units] Hazard15301:
Well I put the script on the SD card and configured Tasker. I wont know if it works until tomorrow, but the script at least functions as intended when I do a test run and when I rebooted the unit. I'll keep you guys informed.

*edit

So, I'm happy to report that this script does indeed restore wifi/bt without rebooting to recovery. I forgot to add tasker to the list of apps that don't close when going to sleep, so I had to run the script manually. But it did work as intended without issue. As long as I can get tasker to work properly, I'd say we're in business.
[Android Head-Units] erkme73:
AWESOME! I have dabbled with Tasker in the past, but never got terribly comfortable with it. Would you mind doing a quick step-by-step write up that shows which elements in Tasker you configured, and where you entered the script? I hate to sound so incompetent, but I imagine it'd be a popular read ;)
[Android Head-Units] Hazard15301:
I'd be happy to. I don't have time tonight, I'll try to get something going tomorrow. But I did get tasker to work properly, so the issue has definitely been worked-around.
[Android Head-Units] erkme73:
Well, you get my vote for the Nobel prize. Unfortunately, I'm without unit still. Hoping "Henry" gets me a tracking number or shipping status tonight. What a relief to know that even if the replacement unit isn't working as it should, you've got a solution. Friggin awesome!
[Android Head-Units] erkme73:
It's official. I have a man-crush on you now... Thank you!
[Android Head-Units] Hazard15301:
Happy to do it, if it helps someone. I posted it over on Hal9k's thread, and also asked about including it in his next release.
[Android Head-Units] psyko_chewbacca:
Thanks alot, I was going in that direction as well. I was trying to compile a c program that just send a IOCTL command to do a USBRESET to the hub. Supposedly it is confirmed by Linux gurus that sending this IOCTL command has the exact same behavior as unplugging and replugging USB devices.

So I'll abandon this thing seeing that the script with Tasker will work just as good!

Too bad the touchscreen on my unit died a couple of days ago.

Replacement touchscreen is on it's way but I don't know how long it will take to get here.

Are there known issues with touchscreen in cold weather? Because mine started acting up the same day we had a big temperature drop, it's now constantly below 0°C and the touchscreen is completely unresponsive, even when the car's interior has warmed up quite a bit.
[Android Head-Units] Hazard15301:
I can't speak for the PX5, but I used my PX3 all last winter in 0 degree and below weather. Other than the touch screen being a little sluggish before it warmed up, I never had any issue.
[Android Head-Units] erkme73:
As I'm sure you've read in my previous posts, I've subjected all three of my radios to the freezer (set to 0°F). The displays had frost on them when I plugged them in. All of them worked as expected, though one did lose the capacitive soft buttons around the display. That was fixed by swapping it with another display from a radio that hadn't yet been returned.
[Android Head-Units] gforums:
Thanks for the translation of this possible fix. I am also monitoring this 4pda thread daily and implemented the fix some days ago. The script itself is working, still it does not completely resolve the issue for me.

Yesterday after roughly 20 minutes of driving, the usb host dropped and my dab application therefore closed as well as WiFi turned off.

I indeed have the impression of a more stable usb host connection, but I can confirm that this fix did not work for 100%.

I would like to add a tasker action next, that always turns on WiFi after it has been turned off.

As my unit is very new, I still prefer a trade unit from my supplier.

BR, Christian
[Android Head-Units] Hazard15301:
That sucks that it doesn't work for you. Normally I'd agree with you about returning the unit, but if you read through the last few pages, [MENTION=943895]erkme73[/MENTION] is on his third return, and each one had issues. There are so many of these units out in the market (PX5s with an XRC board and Android 8.0) that odds are you'll keep getting one with the same issue. I'd try for a return at least once, but at least for me, it would get old returning it multiple times. Hopefully this script helps most people that suffer from this problem. In my case, once I got Tasker running the way I wanted it, it's completely fixed the problem. If it wasn't for the toast message, I wouldn't even realize what was happening.

If you go back several pages in the 4pda thread, you'll see them talking about the screws on the core board. It's been confirmed that in several cases that the board heats up and bends in a slight arc, due to the expansion rates of the different materials. This in some cases causes the wifi and bt pins on the end to break contact. It might be possible that your unit has this issue along with the host controller defect, and you're just fighting two different problems that have the same outcome. Both problems manifest the same issue (disabling wifi/bt). If you don't plan on returning it, you might try adding the extra screws to hold down the core board and see where that gets you.
[Android Head-Units] sean19661:
[Seicane PX5 Oreo] Wifi &amp; bluetooth sometimes not working when waking up.

It's a hipzo 8 core 4gb/32 rom

Model PX5 1024X600 OREO 8.0.0
[Android Head-Units] Yak54:
I have just seen this thread and I am also affected by this problem. I bought and installed my Seicane Head Unit (S32556G PX5-MTCE-4GB/32GB - MTCE_MX2_V2.83) in August 2018.

Already during the first tests the WIFI/BT problem occurred with me. In my case, the error only occurred when I had connected the mobile phone to the head unit via BT. I suspected a problem with the double connection, because the car also has a BT setup. In order to reactivate the WIFI function, a factory reset was always necessary. That was very annoying, since then again all laboriously made settings had to be repeated (Launcher etc.). So I decided not to connect the mobile phone and found out that the head unit has been running without WIFI failure for more than two months. However, WiFi is switched off every time the head unit is switched on, which is no big problem for me.

The port of the internal USB hub is may be overloaded during startup and then blocked because the WIFI/BT modules need a lot of power, as I had to see with some experiments with such breakouts in the MQTT area.

My experience with an occasionally unrecognized DAB+ USB dongle and USB stick also suggests that the problem must be with the internal USB hub.
[Android Head-Units] erkme73:
Not that this helps anyone (other than me), but I just received confirmation from the seller that my "new and improved" Hizpo XRC unit is shipping today. He provided a DHL tracking number. I'm guessing by early next week, I'll be able to confirm whether they really did resolve this.
[Android Head-Units] Hazard15301:
Ok.... Go on....?

---------- Post added at 02:23 AM ---------- Previous post was at 02:15 AM ----------

1) I'm not sure what you mean by this.

2) If that's the only problem you have with your wifi, you should consider yourself lucky. You can use tasker to toggle wifi on everytime the units boots up.

3) I don't know about all that, but I do know that when the internal usb host is acting up, connected usb devices are also not recognized.

You can try running the script just to see if it restores access to your usb devices, at the least.
[Android Head-Units] timolen:
I'm gonna post here also, as recommended even though i'm sure it's a rom issue but, even though I have hal9k mod installed, and i get the toast saying tasker got superuser rights, when i'm clicking "use root" in tasker, i get an error saying "it seems this device is not rooted" or something like this. Any clue why and what should i do? I think because of this, the script is not working.
[Android Head-Units] psyko_chewbacca:
I contacted Seicane and they finally acknowledged the issue with the USB hub IC. They are sending me a replacement IC I will need to swap on the mainboard. Luckily, it's in a SOIC/SOP package so soldering isn't that bad.

I will post more info on the replacement IC they sent over when I get it. For the moment, they haven't told me the part number they are sending over.
[Android Head-Units] sean19661:
HIPZO PX5 1024X600 8 CORE 4gb ram/32 GB rom

MTCE XRC289V2. Bt 725 ver.1

Sorry if this is a double post.

I wound up flashing HAL9K

rom after experiencing bt/wifi issues not seeing or connecting to my phone I would have to boot to recovery clear cache and boot back into the unit would make it start working. I went to yandisk server downloaded MTCE XRCV2.89.2 witch is over 1.2 GB in size I flash it with a wipe It seems now when I start the car my bt is connected to my head unit also wifi will flip on or if I wait it will tether to my phone.

I have been in contact with the seller I bought the unit only a couple of weeks from sent me a link to the software and said if this doesn't work would have the core module replace apparently he knew about this because I only told about wifi switch would flip back to off when I tried to flip it on. As of now its working! So far
[Android Head-Units] Hazard15301:
Sounds like tasker wasn't properly given root access. I'd go into magisk settings and clear anything you have for Tasker. Then I'd run the script manually and grant Tasker root rights.
[Android Head-Units] Yak54:
I hope that the exchange will solve the problem and I am looking forward to your report.

Today we have temperatures below 5°C and what should I say, a connection to USB devices is only possible after several reboots.
[Android Head-Units] sean19661:
Dose any one have the link for the script and with tasker for the bt/wifi problem I'm running maylay3.1rom please need a write up on what to do

---------- Post added at 06:35 AM ---------- Previous post was at 05:52 AM ----------

IM also dealing with the same seller HIPZO PX5 Octa core MTCE_XRC2_V2.89.2 1024x600 4gb ram 32 gb rom

He was talking about sending me a ic chip with a video on how to replace it or send me a new Unit.
[Android Head-Units] sean19661:
So I'm in the process of sending back my hu due to the bt/wifi issue JB TECH on Amazon I bought the PX5 1024x600 by Hipzo only a few weeks ago I also purchased the square trade plan with it from Amazon he said he will send me another HU

I specifically made it clear it needed to be same specs as the one I purchased but not with the bluetooth and wifi issues. He ask for the order # so I guess he can start the process. I hope this problem will be resolved. Oh how is the script and tasker working out for anyone who is using it just curious just incase. It's a shame I really love the unit except for those two problems.
[Android Head-Units] Hazard15301:
I had a handful of time (maybe 2 or 3 out of 20) that the script didn't work. I added a 5 second delay before tasker runs the script and it seems to have fixed it.
[Android Head-Units] MoSH89:
Hi. I have same problem and I talk with the seller and him send me a clip and some instruction. We need to change the GL850G chip with GL852G IC chip to work
[Android Head-Units] erkme73:
That is insane! I cannot believe they expect their retail customers to desolder and resolder a surface mount component with 30 pins on it. Even with the right equipment, I doubt that less than 1% of the population would have the skill required to do that without soldering at least a handful of pins together. I am reasonably proficient with a soldering iron, but there's no way I would attempt something like that!
[Android Head-Units] MoSH89:
I'll wait to send that chip to try ti replace it. In video that seller send me it's not so hard but I'll see.
[Android Head-Units] Hazard15301:
It's a hell of a lot smaller than it looks. Something like that would be out of most people's abilities. You'd almost need a hot air station.

---------- Post added at 02:33 AM ---------- Previous post was at 02:32 AM ----------

[MENTION=943895]erkme73[/MENTION]

Did you ever get your replacement radio?
[Android Head-Units] erkme73:
Indeed. I'd love to see the video they sent him showing how easy it is ;)

Not yet, but DHL says is about 100 miles from me and handed over to USPS this morning. I'm hopeful it'll be here tomorrow. It's estimated to be Wed, but they usually run a day a head of projections.

I'm on pins and needles... And jonesing for something better than the crappy stock Toyota radio!
[Android Head-Units] Hazard15301:
Being that you're doing their job for them, did your seller at least offer to replace the radio in the likely chance that this repair fails?

You should post a link to that video, I'm curious to see how they did it.
[Android Head-Units] MoSH89:
This is the link to the arhived video. http://fs.163.com/fs/display/?file=...4dMxbDdW4sC-rIW657Q0ErMH7ZfN1ZvuwgmYI4ZUtWSOg

Its an strange site but I downloaded the arhive and its ok
[Android Head-Units] jtrosky:
Good luck with that... While I wish you the best, I'm thinking that it's a lot harder than it looks in that video (unless it's something you do regularly) - and they never showed it actually working after they did it, either. :)
[Android Head-Units] Hazard15301:
Man, they make it look easy for sure. But those people do that kind of stuff everyday. I like how they just ran the tip down each side with a blob of solder on the end and somehow didn't bridge any of those legs together. More power to you though. If you can pull it off, I might be tempted to try it as well.

Also, I read that instruction spreadsheet they sent you. Not clear on what chip you're replacing vs. whats already in it. Also, what are the differences between the GL850G and the GL852G?
[Android Head-Units] gforums:
Hi there,

looks for me like the replacement of the chip really might solve the issue.

I just googled for "GL850G issues" and found several topics about disconnecting issues with that chipset - not at all related to the PX5 / car stereos.

What do you think?

for example:

https://www.microchip.com/forums/m658161.aspx

https://forum.allaboutcircuits.com/threads/gl850g-usb-hub-is-behaving-randomly.143246/

https://www.8devices.com/community/viewtopic.php?f=13&t=765

I contacted now my seller and waiting for feedback.

Best regards,

Christian
[Android Head-Units] MoSH89:
I'll waiting to sent that chip and I'll will go to someone that repair this kind of system. I hope to fix this problem.
[Android Head-Units] crazybird82:
Awesome

The fix is awesome. thx!
[Android Head-Units] MoSH89:
You have replace that chip?
[Android Head-Units] Hazard15301:
I was just reading the thread over at 4pda. Looks like Hal9k is testing/integrating the fix script into the next version of his rom.

---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------

I doubt it. You're the first person that has mentioned replacing the chip. I don't think too many sellers are looking to admit to this being an issue due to a flood of returns and not being able to sell old stock.
[Android Head-Units] crazybird82:
No, sorry! I used the software fix. A great solution for me. If it would not working I would try to cut off the internal usb hub and make a port to a external usb hub with a relay from the amp power to the battery for the power and use a bt dongle and a wifi dongle.
[Android Head-Units] MoSH89:
It recognizes all kind of dongle? And what software fix do you used?
[Android Head-Units] crazybird82:
No, not all. But WiFi rtl81xxx should be working and a lot of bt dongles. We just have to consider which onces. :D.

The Internal-USB-Sleep-Fix
[Android Head-Units] MoSH89:
But an dongle that have both ( wifi and bt) that working on this player exists? And it recognizes automatically or its need to do some settings?
[Android Head-Units] erkme73:
It came in. It's below freezing. It works!

I took this picture of the suspect processor through a screw hole...

I'm just buttoning it up with remaining daylight.
[Android Head-Units] erkme73:
All set. Spent the rest of the time re-installing everything (after switching to the Hal9k rom, of course). Everything works. I had to pinch myself. As you can see in the screen grab, they did swap the chip with the newer 852 version. It was the 850.

Since this thread was started, a number of people have joined the "me too" movement. I'm guessing the XRC units are gonna all need to be fixed (or have the tasker script workaround). What a nightmare that must be for them. So glad it's over for me!