yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 4 Questions & Answers] papero68:
Perfectly normal.... Have a nice weekend

Inviato dal mio Redmi Note 4 utilizzando Tapatalk
[Xiaomi Redmi Note 4 Questions & Answers] ferbricos:
Can i put sim2 with LTE, not Sim1?

Thanks

Enviado de meu Redmi Note 4 usando Tapatalk
[Xiaomi Redmi Note 4 Questions & Answers] Danchibald:
Yes you can. In settings, just choose SIM2 for data.
[Xiaomi Redmi Note 4 Questions & Answers] ferbricos:
I've did It, but only works in 3g.

Btw, when i share this data, receivers can't connect. When i share data from Sim1 It works Very Well in LTE...

I think the problem is in miui. Any stable and clean ROM that you recomend?

Thanks

Enviado de meu Redmi Note 4 usando Tapatalk
[AT&T Samsung Galaxy S7 Questions & Answers] crapymonkey:
Wife and my self both have att s7 phones and over the last two days they both have said charging stopped because internal temp to high and will resume after cooling down. First time I noticed mine I was using a charger in my truck, hers was on a wireless charger. But I took mine out of my lifeproof and it was so hot I couldn't hold it but a second or two at a time.

Is their anyone else having these issues? I have had a s7 since release date and up until this week I've never seen this. I always worked outside in extreme heat and phones always on belt clip or pocket. Wife's just has a simple thin case and nothing like my lifeproof.
[AT&T Samsung Galaxy S7 Questions & Answers] crapymonkey:
Help still overheating

Phone still gets so hot at times you cant hold it....
[Android Q&A, Help & Troubleshooting] santiso:
Hello guys, I have this problem. Recently my apps stopped updating ( I think Playstore and Google Services updated and made that happening...idk) and couldn't access most apps, then began to restart 4/5 times in a day automatically, and couple of days later just showing the logo after turning on. So I decided to update the OS but as it's rooted it wont let me. I used to have 4.3 version (don't the name, maybe Pineapple Pizza) so I decided to start from scratch after backing up everything, took note of version in my country, efs, etc). Made a wipe clean through TeamWin, and with Odin tried to make a new install ( Stock).

Unfortunately when connecting to my pc can't recognize device "“USB device not recognized”.

I tried cleaning USB connector with dried toothbrush, other ports in the back. With other 2 computers and same result.

Installed Kies but didn´t work, unistalled Kies and tried latest versions of drivers for windows 7, same result. Tried Samsung latest drivers ( older ones), didn't work either. I have tested other devices in the USB ports and they all work fine. I thought it might be that I didn't selected "USB debugging mode" before the wipe clean...or it wasn't a Wipe Clean at all...(?).

I checked most of simmilar problems in the forum, but I couldn't find a solution, sincne I can't even access my phone.

So, Im here with my oldie S3 in some kind of "limbo"

Any ideas that might help? :rolleyes:

Thank you very much in advance! and sorry if Im posting in an incorrect forum. :(
[MTCD Android Head Units General] bazgrim01:
https://www.amazon.com/gp/product/B01JULCTYE/ref=ox_sc_act_title_2?smid=A17YHR60ETNWLC&psc=1

Thoughts? Thinking about ordering one.

I just returned a headunit from ATOTO because it worked like crap.

I like the prospect of 7.1 and offline maps already installed.

Quadcore vs Octacore I don't think makes a huge difference here.

Would love to know opinions.
[MTCD Android Head Units General] AndroidBricking:
I have a similar product to this with the product ID "B071LT7LC3" on Amazon. (I cannot post links yet) From the looks of things, my unit is likely the same hardware as yours, only with a different front panel and added DVD player. This is the information I read from the device:

MCU version: MTCD_XRC_V2.52_1

Build number: px3-userdebug 7.1.1 NMF26X eng.hct.20170527.145603 test-keys

Kernerl version: 3.0.101+ rocky@hctr930 #550

Model: px3 (800x480 O)

I sadly managed to brick mine by running an incompatible root method for Joying devices via Wireless ADB. I have not found a root method actually works on these units yet. If you are looking for an Android stereo that you can root, look elsewhere. I got a copy of the firmware from Hizpo, but not even that can fix the damage I did to it. It is with this warning I hope to prevent you making the same expensive mistake.

Note that you cannot use these units with a PC via USB, you must use Wireless ADB using an app. Use "126" to get into your factory settings and play with those, or "adbon" to enable debugging. You can also download a Development Options app to reach those settings, as they are hidden. The various methods of recoveries, including the one provided by the seller (Hold down the power button, turn on the power to the radio, release after 5 seconds and wait 30 to reach the recovery), did not seem to work for me either. It is possible I corrupted that too, but I am not sure.

I will happily share any other opinions I have about the unit if I ever manage to get it unbricked.
[MTCD Android Head Units General] typos1:
FYI - there are literally 1000s of different MTCD units by about 10 different manufacturers, they all share pretty much the same hardware and the software is interchangeable
[MTCD Android Head Units General] AndroidBricking:
But certainly not root methods and certain firmwares. Pick the wrong one and you can brick your device beyond restoration - to the point where the recovery does not work and no firmware update worked to fix it. I had to get a new unit.
[MTCD Android Head Units General] typos1:
Yes, all RK3188 MTCD units are the same inside, they use the same SoM and ROMs ARE compatible as long as you get the screen res and processor type correct and even if you get the screen res wrong its no big deal, it wont brick.

However if you flash the firmware from an MTCB unit, or from an entirely different, unrelated unit , its sounds like this is what you did.
[MTCD Android Head Units General] strykr192:
I was looking at this, but when I noticed it said PX3 I decided to skip.. Doesn't make sense to not have the PX5 chip.

Now if there was a version with a PX5 on the new os Id be interest.
[MTCD Android Head Units General] typos1:
Sure the PX5 will be fast, but the PX3, especially with 2Gb of RAM is perfectly good.
[MTCD Android Head Units General] elder-lowater:
If you decide to order, please update with your impressions. I too tried the ATOTO M4 garbage head unit, and it has almost encouraged me to give up on them entirely. If you find this one to be worthwhile, with it being at a similar price I might give it a shot.
[MTCD Android Head Units General] typos1:
No need for him to post impressions - its an MTCD unit and theres a whole forum about that you can read to see what theyre like :

https://xdaforums.com/android-auto/mtcd-discussion-questions-development
[MTCD Android Head Units General] ricanxd:
Ordered this unit myself. I'll share thoughts after I get it.
[MTCD Android Head Units General] ricanxd:
Installed, and I'm definitely impressed. Very zippy and sounds great.
[MTCD Android Head Units General] typos1:
What MCU version do you have ?
[MTCD Android Head Units General] ricanxd:
Xrc v2.54a_1
[MTCD Android Head Units General] typos1:
I meant MTCB/C or MTCD, by the look of it, its MTCD.
[MTCD Android Head Units General] ricanxd:
Yeah it's a MTCD unit px3
[MTCD Android Head Units General] typos1:
Lol, yes we know its RK3188/PX3, there are also MTCB and MTCC RK3188/PX3 units around, I wanted to know which you had, B, C or D.
[MTCD Android Head Units General] ricanxd:
Gotcha, just got confused since you asked what MCU version. I thought all new units are shipping with MTCD.
[MTCD Android Head Units General] typos1:
No, not all units are MTCD, I ve heard a rumour that a company is working on MTCB/C N, even if that is untrue then you can still buy MTCB/C units.
[MTCD Android Head Units General] ricanxd:
That I know. You can still buy KitKat units..
[MTCD Android Head Units General] typos1:
Yeah, makes me laugh, the sellers must be stupid, why dont they update the KK ones to L ? they can sell them for more.
[MTCD Android Head Units General] AndroidBricking:
ricanxd, have you been able to get your unit into recovery, or at the very least rooted? The closest I have ever gotten was getting wireless ADB working and using a root method that bricked my unit. Ours are both from HIZPO and are XRC units, but it does not seem that they are popular enough to have been cracked yet. Neither my first one nor the replacement even let me into recovery. I could just be doing something wrong, though.
[MTCD Android Head Units General] typos1:
As its an MTCD head unit, everything that applies to MTCD headunits applies to your unit.

For root you need a custom ROM, have you tried the standard method for getting into recovery ?

Plenty of threads about these things in the MTCD forum.
[MTCD Android Head Units General] ricanxd:
Haven't tried going into recovery yet. I assume it should be same as others, holding down the power button until button lights flash. Like above post says, its basically another MTCD unit. I haven't bothered with root either since I'm happy with stock setup. I did read somewhere else on XDA warning about trying to do root on these new units.
[MTCD Android Head Units General] AndroidBricking:
That does not work for me, as my unit does not even have button lights as yours does. The seller told me to turn off the power, hold the power button for five seconds while powering it back on, but that does not work from cold or warm boot.
[MTCD Android Head Units General] ricanxd:
Yeah I'm not sure about your type unit. Is there a small pin hole reset button? Thinking that might get you into recovery?
[MTCD Android Head Units General] typos1:
Lol, I keep telling you guys to look in the forum for info.

You have MTCD units, your "type" is that same as all other MTCD units, no matter what they look like, they ALL have reset holes.
[MTCD Android Head Units General] ricanxd:
Lol well I'm good. I always search.
[MTCD Android Head Units General] Blackman778g:
Been reading up on all of these Android Auto posts... please excuse my ignorance been awhile since I've rooted a device.. last device was a HTC G2 (with custom Rom) and Galaxy S3 (just was trying to get back into it)

I've learned that there are quite a few and that there are 2 iterations of the px3 chipset.. and I see the px5 obviously outperforms due to the octa-core and 32gig Rom....

[MENTION=456516]typos1[/MENTION] I see you have a good understanding about these devices as I'm look to replace my old Chinese unit with 4.2...

The new 7.1.1 units from Hizpo are typically MTCD and should offer reliable performance with the 2gb ram and 16gig Rom? The 16 gig Rom is the only thing that stopped me from buying one of these units in the past week...
[MTCD Android Head Units General] typos1:
Yes, there are the MTCB/C units with the RK3188/PX3 and MTCD units with RK3188/PX3, with L they were a little slow (some people stuck with KK on MTCB/C, MTCD never had KK so owners never had that option).

Some MTCB/C and MTCD users added an extra 1Gb of RAM which pretty much sorted the speed issue, others installed microGapps or OpenGapps to free some memory, some did both. But an RK3188/PX3 with 2Gb RAM should be plenty fast enough, certainly mine have all been pretty reliable. Why has the 16Gb RROM put you off ? You want 32Gb instead ?

I was told a month ago that someone on here was in conversation with a Chinese company about supplying an RK3188/PX3 SoM with 2Gb RAM, N and a 32Gb ROM for MTCB/C units, I ve not heard anything since and of course it may never happen.

BTW, these units are also Chinese (arent almost all electronics ??), built and made in China using components from many well known OEM manufacturers and running software from MTC who its suspected are Indian.
[MTCD Android Head Units General] Blackman778g:
Ok, I think I am going to place my purchase now...

The reasoning for 16 vs 32gb debate was to ensure that the device should have apple memory to function... my previous Android phone was a 32gb Note phone and that thing still surprises me today... but I was figuring with the way Android has expanded and apps growing in size and resources that 16 wouldn't be enough over time...
[MTCD Android Head Units General] ikerg:
All MTC software is made by HCT (ROM and MCU) as I was told.
[MTCD Android Head Units General] typos1:
Ah, the size of the ROM wont make any difference to how a device performs - youre getting ROM confused with RAM.

The ROM is the size of the flash memory, like the size of a hard drive in a pc.

---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------

HCT make the SoMs for these units.

Its certainly possible that they make the software too, I guess, where did you hear that ?
[MTCD Android Head Units General] Blackman778g:
Just over time i didn't want to experience the dreaded device slowdown after enough apps have been installed and taking up memory... I read about adoptable storage but the last thing I'd ant is for the SD card to fail lol
[MTCD Android Head Units General] typos1:
That was caused by lack of RAM, if you get one with 2Gb you wont have that problem.
[MTCD Android Head Units General] DrDabby:
PX3 MTCD XRC 2.54a_1 Help

I have a Hipzo Head Unit - Android 7.1.2 - MTCD_XRC_V2.54a_1 - Rocky@hctr930 #596

Hello,

I would like to use this head unit for OK GOOGLE function since I have a 4G sim card in it. The problem is the microphone only works during phone calls. I thought that this may have been due to the internal mic so I plugged a 3.5mm headphone jack mic into the "MIC" port on the back of the unit. (Plugs into a separate harness that goes into the back of the unit). This just replaces the internal mic for PHONE CALLS. I cannot find anyway of changing the default input device (mic) without configuring a system file. I cannot find a way to root this device either. Please help. Even another rom where someone knows this is supported and will work. It is one of the whole reasons I bought this head unit. And I bought 3!

Also, even when I press the manual mic button on the google search bar, it does not register my voice at all. downloaded voice records, camera app w/ recording. nothing picks up my voice, only phone calls.
[MTCD Android Head Units General] ricanxd:
I also have had this issue. Try contacting them, they might have a SW update to fix it.
[MTCD Android Head Units General] markmorto:
I have the same unit, a Hipzo Head Unit - Android 7.1.2 - MTCD_XRC_V2.54a_1, only mine is specifically for VW.

I don't have this mic problem - "OK Google" voice search works good on my device.

I did have a serious noise problem when I first installed it, though, and it caused all kinds of problems - wavy lines in the backup and DVR cameras, whine in the FM, and the mic not working - people couldn't understand anything I said, and "OK Google" didn't work either.

I replaced an Xtrons Android 5.1 unit with the Hizpo and the Xtrons had zero noise issues. Exact same car, wiring, installation, etc. I thought my new head unit was bad. I had to install a noise filter on the power input to the stereo, and all my noise issues went away. I think these stereos need better power-in noise filters or something.

The other major thing I noticed when comparing the Xtrons to the Hizpo was that the Xtrons had copper wiring on the power cables that came with it, and the Hizpo had steel (possibly aluminum). Not sure if this is causing the noise problem, but the wiring was definitely cheaper.

I also added an external mic, but I'm not sure if it was the new mic or the noise fix (or a combination of both) that fixed my mic issues. Since everything is working, I don't want to take it a part jut to know the answer at this point.

All things considered, I love the new Hizpo. It sounds good, runs all my Android apps without lag, and having the Internet in the car is pretty awesome.
[MTCD Android Head Units General] typos1:
Firstly I need to explain there are no "Xtrons" or "Hizpo" headunits, these companies are sellers only - they buy from the manufacturers and sell them on, units are identified by the 3 or 4 letters after "MTCD" in the MCU field, so your current unit is an XRC unit, without these letters its not possible to identify what your previous unit was.

Regardless of what processor MTCD units have - there are 3 types - RK3188/PX3, RK3368/PX5 and Intel Sofia, the motherboard and MCU for each manufacturer are the same, some units have a similar sound problem as MTCB/C units in that the internal and external mics are wired together. A lot of RK3368/PX5 users are reporting mic issues, however, [MENTION=7621504]f1x[/MENTION] has discovered that there is a software problem that causes sound problems on MTCD RK3368/PX5 units, so its quite interesting to hear of your solution, maybe you could also post in this thread (there are confusingly FOUR threads about RK3368/PX5 MTCD units !!!!) :

https://xdaforums.com/android-auto/...-head-unit-discussion-thread-t3573881/page198

to inform other RK3368/PX5 users of your solution ?
[MTCD Android Head Units General] AndroidBricking:
Is there a working root method for the px3 MTCD_XRC units? Mine errors out on every single ROM I try to install using a microSD card in the GPS slot, because my unit lacks any sort of backlighting except the screen itself, I have not managed to manually enter recovery either. I am probably an idiot, as the only thing I have ever managed to do is hard-brick one unit using a Joying root method via wireless adb. Kingroot, Kingoroot or any apps like that have no effect either. Custom ROMs just leave it stuck on the loading screen until I load the correct factory ROM (which also errors out, but fixes the unit anyway).
[MTCD Android Head Units General] typos1:
Any rooting method will be the same for ALL MTCD RK3188/PX3 2Gb N units, regardless of manufacturer.

I ve not read of any yet, not I have I seen any custom ROMs for the 2Gb N units, but I may be wrong - where did you see them ? Or are you trying an RK3188/PX3 1Gb L custom ROM ? If you are that would explain why they wont install.

I m not sure what you mean about teh back light thing, what has this to do with getting into recovery ?

Injecting root into a factory ROM is the best way.
[MTCD Android Head Units General] AndroidBricking:
I did not even know that RAM was a factor! I have a copy of my current ROM from the seller, how would I modify it to inject root? Do I add superSU to /system or something like that?

Btw, Please forgive my miscommunication; I meant the button lights. I believe the method to boot the HU into recovery involves holding the reset button until the button lights flash, except my model does not have button lights.
[MTCD Android Head Units General] typos1:
RAM is only a factor because the later RK3188/PX3 boards have 2Gb and Nougat, there are slight differences between them and the 1GB SoMs, although Nougat can be made to work on the 1Gb SoMs, albeit with a message at the bottom of the screen saying "test only".

Not entirely sure how to inject root, you ll have to google it.

I have a 2GB RK3188/PX3 unit and an RK3368/PX5 unit and the button lights dont come on, I interpreted this to be a fault, youve interpreted it to be that they dont have lights, cant say which is correct at the mo.
[MTCD Android Head Units General] rnt0:
Friend, sad to hear it...

Probably you tried this but correct recovery for this unit is:

Hold power down until it start blinking

Keep holding for five more sec.

Release the power button

(after 1 sec)

Click and release

Also, I could not manage to activate ADB, may you help me with it?

Kind regards

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

Any update on this? Same problem here
[MTCD Android Head Units General] AndroidBricking:
Enable USB debugging on your head unit in Settings -> Factory Settings, using the password "adbon" when prompted. Once completed, download an "ADB Wireless" app from the Play Store, one that is marked as "no root". You can also get into your Developer Options with a Play Store app. ADB over USB did not work at all for my HU, so that might be your best bet, as it was for me. Be careful not to use the wrong root method, or you might hard brick your HU.

Btw, My HU does not have any button lights, so nothing flashes when I hold the reset button. Madness, I tell you!
[MTCD Android Head Units General] rnt0:
No way in hell i can connect to the unit via wireless, it refuse everytime.

All apps I found, ask to connect via usb and enable wireless adb, thing is it is not possible to adb by usb on this unit
[MTCD Android Head Units General] rnt0:
Nvm, Just did it, but is almost everything locked without root
[MTCD Android Head Units General] typos1:
Well flash a custom ROM then.
[MTCD Android Head Units General] AndroidBricking:
Sorry about that, I missed a few steps!

To get to your recovery on a HIZPO XRC unit if your HU refuses to let you do it properly, using ADB Wireless:

- Download two apps from the playstore:A terminal emulator and a ADB wireless (no root) app.

- Enable USB debugging on your Head Unit by going to Settings -> Factory Settings -> Enter password "adbon".

- Start the terminal emulator app and enter "setprop service.adb.tcp.port 5555".

- Reboot your HU with the reset button.

- Run the ADB wireless app, make sure your HU and PC are connected to the same WiFi network and that you have the Android platform tools installed on PC.

- Open a command prompt on your PC (Windows), change the directory using "cd <Directory where your adb.exe is>", then run "adb shell" to start it up.

- Run "adb connect <IP HERE>" on your PC, then "adb devices" to confirm that it is connected.

- Run "adb reboot recovery" on the PC, which will reboot your HU and put it into recovery!

I have not yet tried putting a custom ROM on here or figured out how to put a custom recovery in, however. Just be careful, if you screw up and brick your HU, you might not be able to fix it by simply putting the factory rom on a microSD card in the GPS slot.
[MTCD Android Head Units General] cpeters99a:
---------- Post added at 02:18 AM ---------- Previous post was at 02:15 AM ----------

[/COLOR]

Any update on this? Same problem here[/QUOTE]

I have the same Hizpo mtcd xrc_V2.54a_1 w/2gb 7.1.2 but mine is a 7" universal. How does your VW version have a working microphone input to android to be able to use google voice? Is there something different with the VW version? Did google voice work before you installed the filter but the mic was too noisy?

I have no microphone input for any android voice recorder or google voice. I am missing voice input under keyboards in settings. This is what I've heard for all those like mine.

Both internal and external mics work together on bluetooth ok for me but no where else. I cannot shut off the internal mic with the external. I've tried a usb mic too but that did nothing.

What's the secret?!? It cant be just a line filter.