I bought S8 from another seller, while for 3 months there was not a single problem that was written about here. The only thing I did was a microphone, but look on YouTube, this is a problem for all models, everything else in them is absolutely the same, both in Teyes and in another company, for the average user, only the firmware is different. Inside they are made the same. Most likely they take spare parts from one manufacturer and assemble them under their own name. I saw different models of different companies in disassembled form, I don’t know how they differ. In my case, I'm 99% satisfied.Perhaps there is some difference in the details, but I'm not interested.
[General Discussion] QF001 (ROCO K706) Head Units with UIS 7862s (not FYT based) [read first post first]
- Thread starter blue_one
- Start date
When I connect my phone to USB1 or 2 it pops a message saying slow charging & recommends to switch chargers. It even isn't stable. Flipping charging process on and off. I wasn't planning on driving to the French Riviera from hereso I started charging over cigarette lighter again.
They must have special cars & phones in China...
He spoke about lagging and restarts, maybe he has general voltage problem in his HU.
I stay hopeful that a DAB+ dongle with a operation current < 50 mA (0.25 Watt) will function right, time will tell...my USB front camera works flawless, no worry here yet.
And yes special they are
, but didn't expect a 10 Watt charging capability from this HU, USB 2.0 port should be designed for a maximum of 500 mAh load, but hopefully you can tell later with a USB tester what it does.
Last edited:
There is one function in Teyes that is solved differently from the others. The processor has its own fan-cooled heat sink, and the case only cools the power amplifier screwed down and not in the pocket.
Last edited:
But is it worth to spend ca. twice that much as S8 price (i compared HU with 6/128, and same processor, from official stores). For me not, but i don't look to anybodys pocket
Did you manage to use carletter with android auto wireless? In my case Galaxy S22 or some Chinese phones it works, but without mutlitouch which is essential for maps... All those phones work smooth in other cars with wireless/wired android auto with good multitouch support.
Hello. Do you have some direct communication with vendor? I've noticed the obvious bug with Android Auto (wired/wireless). In my case with Galaxy S22 and some other Chinese phones. It works, but without mutlitouch which is essential for maps... All those phones work smooth in other cars with wireless/wired android auto with good multitouch support. I suspect this to be Carletter host app bug, but I can not find neither the github repository nor even the contacts of developers. Any ideas how to fix or at least report this issue? Thanks in advance!
Lucky you. Wireless? Can you tell me the version of that carletter application?
Sorry, sorry i have no multitouch too. Tried just now wireless. Never tried wired.
Thanks, but my S8 unit works flawless and paid half the price of your CC3, maybe it's time to leave us, this thread is for helping eachother out for the S1-S8 unit's, not for oooooh my other unit is sooooo much better.
This will all respect but you not helping.
Last edited:
Is this what you need......Hi, does anybody have the radio apk file to share, please?
I'd like to look inside it for possible porting of my app NavRadio+.
Thx
Extracted QF_FMRadioExt.apk from the latest 23030306 FW
Last edited:
BTW it was located in the "\system\priv-app\" folderYep, thank you
Maybe it is only me, went back from latest 20230306 to 20230207 FW, had some weird sounds from the radio when using my Sygic navi, on moment that Sygic makes notification, it should with navi mix put the radio a little down but the radio sounded really weird, like under water sounds.
Also had the impression that the antenna reception of the radio is a little worse.
All good again with downgrading to previous februari version, actually the first time I don't like an update.
Last edited:
https://webshare.cz/#/file/t23MaWKaGmHi, does anybody have the radio apk file to share, please?
I'd like to look inside it for possible porting of my app NavRadio+.
Thx
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6Hi guys,
I just wanted to let you know that the porting of NavRadio+ on this units is going better than expected.
I already can change frequency, receive RDS data etc.. i can't control the audio focus right now but I'll figure it out sooner or later.
I'd like to ask you some questions:
1. Have you ever seen, on the original app, the RDS text broadcasted by radio stations with song name or other infos? Not the name of the station.
2. How do you set LOC or DX in the original app?
3. Do you think the AF and TA function work well on the original app?
Thank's to anyone who reply5The flash was successful. Only the HU indicates that I have 6GB and that should be 8, so no idea why, but think it has always been 6. If you open the HU, you can also see that there is a sticker on it with the data of the device, there you also see 6 + 128GB, so the same story as android 10 (fake12) Direct update to 20230414 did not work (again a checksum error, but was able to do a full reset) so I updated the HU in steps with the *major" updates with auto update, that went well. Recovery procedure was easier than I thought, with some more extensive explanation from Vėžys, so thank you @Vėžys
Glad I have a well-functioning HU to update it again, thanks to the people on this forum 
4Finally did a mic adjustment. I removed the pcb & capsule from within the OEM Vag mic housing & put an 6 mm capsule from an old Parrot mic in place. At the radio end/center console side I made an adapter to 3,5" mono jack (so it is the pcb/circuitry preventing the OEM VW mic to be used with aftermarket units).
So I have my external mic now sitting at the designated location in my Golf MK5 without need to run any extra cable. And normally it is future proof if I were to change to another aftermarket unit. I unsoldered & removed the internal mic of the HU all together btw. Good riddance.
Works very well - better than the internal mic mod did. And no more mic picking up the (low) fan noise.
Edit: inside the OEM mic housing there is an small pcb which has a 6 mm mic capsule soldered directly to it. If one is carefull in removing the guts (pcb with capsule) you should be able to repurpose the capsule. I was too brute and broke the capsule's solder islands (but I knew I had another 6 mm mic capsule laying around if needed)
Could also be simplified by just cutting off the OEM mic housing and soldering an external mic directly to the OEM connector leads of course. And make an adapter to 3,5" mono jack to connect to external mic socket.3
problem with notification tone when calling fixed by firmware 0508! -
17Hello all,
it seems that there are some QF001 owners out there but not much informations. So i will try to collect everything and put it at one place.
The original manufactor is shenzhen jitu technology co. ltd.
These units are sold from Ossuret, Hizpo and other brands. This are the sellers specs:
The Android 12 is fake which is Android 10 in reality.
I have the 8/128GB Version myself:
Codes for the factory settings menu:
- 8888 - access to advanced settings
- 114477 - activates developer mode (Than you have to do the usual procedere: touch the build number on the system info screen several times until it says that you are developer now.)
- 22558800 factory reset
- 15935700 turns off sleep mode (Not tested by myself)
- 332211 - Shows temperature and clock speed
- 996633 - Exports some config file
- More codes are here https://forum.xda-developers.com/t/...uis-7862s-not-fyt-based.4525675/post-88055377
- https://forum.xda-developers.com/t/...d-read-first-post-first.4525675/post-88203789
Dedicated thread for gaining recovery access: https://forum.xda-developers.com/t/...uret-s4-s8-uis-7862-headunits-no-fyt.4538107/
Beside the faked Android 12 Version the head unit seems to be a good bang for the buck. I´ve paid around 230 Euros including VAT and shipping. The unit runs stable and powerful so far. Everything works as expected. The Android is a bit downcutted by the manufactor. There are no text notifications in the statusbar e.g. But i can compensate that with widgets.
Against the description android auto works wireless with my Xiaomi Mi10t pro. So that's also nice to have.
Tweaks, mods and others:
- my wire harness was labeled wrong. Key 2 and Key GND were swapped. So better check the cables before connecting. For me the correct wire names/functions were in the printed manual.
- replacement fan that fits my model: Sunon MF35101V21000UA99
- there's a sleep whitelist in the factory settings menu that prevents apps from being killed in standby mode (ignition off). That's very useful. I've whitelisted Google maps e.g. and don't lose my programmed route anymore if i turn off the engine for a short stop.
- tasker trigger for warm boot: detect any USB device connected. (You have to plug in something into the usb port, dashcam or pendrive e.g.)
- the status bar only shows a few symbols and no text notifications. Therefore I use a notification widget in combination with nova launcher. This way I can see all notifications in a widget which would be at the status bar originally.
- wireless ADB is enabled by default with root user.
The port is 9876. ( I've found that inside the build.prop)
- if you want to have a look inside the firmware you can use a rom kitchen tool like CBR
- how to change the boot logo:
1. If your player is 1280*720 screen, you need to rotate the picture 90 degree, and cut it into 720*1280 size, transform the picture to .BMP format.
2. If your player is 1024*600 screen, you need to cut the picture to 1024*600 size, transform the picture to .BMP format.
3. copy the picture into your Udisk root path, and then connect Udisk to the player. follow the steps settings-factory-8888-Logo set-then you can see your picture and select it- click update logo.
- how to change boot animation: https://forum.xda-developers.com/t/...uis-7862s-not-fyt-based.4525675/post-88086835
- enhance the microphone and call quality by using the external microphone and disable the internal microphone by masking two pins of a ribbon cable. It's explained inside this thread (link to post will follow)
- GPS tweak: https://forum.xda-developers.com/t/...uis-7862s-not-fyt-based.4525675/post-88112693
Known issues:
- "hey Google" (activate the assistant by hotword) doesn't work
- no car speed dependent volume control (manufacturer says it would be implemented later)
- the firmware is a debug release which is a serious security risk (every app or malware can get root access through ADB shell). On the upside you can also get root access through ADB and do everything you want
To be continued...
Cheers
blue_one9And now a few more!
1122 / 2211 - both popup a bubble with chinese text. I thought they were the same at first but they have different characters. (They both have the word “log” in it)
6655 - opens up a screen that appears to be the same as 555666 but these are also in Chinese so I don’t know if there are differences. Notably when you enter this menu with either code it will record a snippet of audio from the mic and play it back.
4455 - engineer mode (lots of stuff in here to explore, includes adb shell)
5544 - gps stuff
1212 - notification that says “slog copied to unkown”
2121 - seems to just take you home
45645600 - download mcu file9
Just by trying a bunch of different codes and looking for patterns. Starting by looking at the codes we already knew I discovered they are all a repeating sequence of digits that are adjacent to each other on the keypad. Once you find a pattern there’s usually another code that uses the same pattern somewhere else on the keypad. If you actually type in the codes and look at the physical pattern they make you’ll see what I mean. For example 114477 is just the digits in the left column of the keypad going down. 336699 is the same pattern in the right column. And then some codes are just variations on top of that, like doing a code in reverse (which we already knew) as well as adding 00 to the end of some. This is how I discovered all the codes. Once I’d find one code Id try that same pattern in all places and variations. Simple as that! I’m sure there’s more patterns yet to be discovered so try different ideas out and see what you can find. With many people using these strategies I’m sure we can discover more! I may have even missed a few using the patterns of ones I found.8For whom that's interested and is annoyed that display time is out of sync with atomic network clock time.
Myself don't use 4G network, but WIFI hotspot from phone.
Each time when I opened the GPS test app, time changed and was out of sync by 2 to 4 minutes, also when I forgot to put hotspot on my phone on, after that it was taken the GPS time sync by default after startup,
So first taken my right hotspot network time and changed 30 seconds later to the out of sync GPS time, it was also out of sync with my OEM Opel board computer display.
With some hassle I could changed that back but needed to be sure that hotspot was always on before starting the car.
Think I found a solution.
Note, I don't use sleep mode, always have a fresh cold start, unit starts up with firmware date and time, 09-01-2023, 12:05:54.
After going in the factory 5544 GPS setting, changed on first tab screen "agps" the server SUPL host to supl.google.com, changed port to 7276 (seems secure port), but you also can leave it on 7275, then tab screen "information", on the bottom page changed the satellites to GPS, Glonass, Galileo, my problem disappeared.
My unit correctly shows the time now, after a start-up it is in sync within 1 second compared to atomic clock, with or without hotspot, mean also without network connection it syncs with GPS satellites the time correct.
The AGPS SUPL was using the Chinese host (supl.qxwz.com) and preferred what it looks some Chinese satellites for Glonass and Galileo and somehow the Chinese GPS time is inaccurate.
Rather Google then the Chinese that follows me
