That doesn't work anymore for about 1½ years. FYT had removed that option.
But is it about not being killed or automatically started again. See for the latter Q19 in post #1
That doesn't work anymore for about 1½ years. FYT had removed that option.
Thanks a lot for your corrections and additions.- Automatic start and stop
I believe it is useful for cars that have automatic stop and start. Newer cars turn off engine when they get to a red stop light, for example. I think this option keeps the screen on for a short amount of time such as when automatic start/stop engages. I keep this on so that when I turn off my car, the head unit stays on for a short period of time. If I then
want to listen to the radio I then put it into the accessory position.
- Power Conditioning
I consider this as absolute sound and then other sound settings are based on that. So, what I did was figure out the volume that I wanted to normally listen at. I normally listen to Poweramp from about 8 at the low end to about 12 or 15 and when I really want to pump up the volume, I put it to anywhere from 20 to 25. The upper limit of volume setting is 30. At all of those levels, there is no clipping and sound does not get cut.
- Antenna normally on
Some cars require a constant 12V power supply for the antenna. I believe the VW cars do this...may include Audi and Porsche.
I'm not completely sure about the first. My car does not turn off the engine at stops. Also, this was not a complete answer. When I said that I turn to listen to the radio in accessory mode, I meant that the radio does not go through a complete reboot when I had turned off my car. Sometimes I can go in to get a coffee and come back out and when I start my car the head unit picks up where it left off. This is not sleep mode. I believe the screen is just turned off or the blacklighting is turned off. I have my settings to reboot and not sleep.Thanks a lot for your corrections and additions.
The first one: I have such a car but it doesn't work for me like that. Maybe you are completely right, but then it is an omission in my canbus.
power conditions: I said releative output, but it is indeed the absolute output. The other volumes are relative to this one.
Antenna normally on: Are you sure? I was told by someone with an old mercedes having an automatically retracting/extending antenna that it did work for him like I described it, but I don't have it myself so I can't be sure about this.
I'm sure you're an expert at this but for me this is too confusing. I don't even know if I can flash teyes cc on my tablet or not. I don't even know if flashing teyes cc will fix my issue or not? I tried to search for someone with Bluetooth issue but I couldn't find any post for FYT with the NOR type mcu version so I can't replicate his solution. I tried every method to get my seller to give me a firmware instead that at least I know it'll for sure work, but the seller has closed shop and I have no more way to get the Bluetooth working. I really don't want to brick the device due to my wrong assumptions. I really hope for some guidance in the community, at least point me to the right materials then I'll try to do some self studies on them. Many thanks
check maybe with KoTIX https://kotixworld.wixsite.com/navi...x-rom-v10-for-the-px5-android-601-mtc-devices
To start with: you do not even tell us what unit you have yourself. We can assume you have a FYT, but it would help if you tell what you have.
Sure, I have a FYT 31 Android head unit. This is the UI posted by the developer of the NaviRadio. I think he developed this rom also. This is for MTCD head unit and he has developed this. But not sure if this will work on FYT or not.To start with: you do not even tell us what unit you have yourself. We can assume you have a FYT, but it would help if you tell what you have.
And it would help if you tell us on which system this UI is running. Then we might be able to tell you if it is possible to run it on your unit.
Still strange. USB-tethering doesn't start working by only updating a propery value. Either the software already supported it, or it doesn't at all which makes the scam even bigger.Mailed Joying about my disappointment concerning the "Android 12" update. Got to say they responded quickly (as always) and, imho, quite reasonable.
Relatively speaking that is, as I still find the way they implemented the USB tethering somewhat misleading/poorly chosen.
"I am sorry friend, we release Android 12 just mainly to add the USB Tethering function to differentiate from previous firmware, that's why our advertisement is still Android 10.0, not changed to Android 12 to attract more traffic, if this disappoints you, we felt deeply sorry for this, We will learn this lesson and do better in the future, and be more cautiously."
English please. Read the sticky moderator posts.Olá, tenho um dispositivo FYT, modelo M700S da marca Navitree, versão 8gb de RAM 128gb de memória interna, aqui está o link (https://www.aliexpress.com/snapshot/0.html?orderId=8145570029879167) . Eu tenho um citroen c5 2011, estou tendo alguns problemas
1º principal é a má recepção de FM, tenho como melhorar a recepção de FM, já coloquei amplificador de sinal mas não melhorou nada
2° sempre que ligo o carro o navradio + abre e fecha duas vezes mas continua tocando, e se o music player estiver tocando antes de desligar o carro este continua a tocar e a mesma situação não acontece mais com o navradio+ quando o carro liga funcionar, você sabe como resolver?
3° meu carro tem sensores de estacionamento na frente e na traseira, para a traseira não tenho problema, mostra a imagem do radar com a traseira e frontal e a câmera mas para a frente só mostra os vips mas a imagem sim não aparece do radar, é possível fazer a imagem aparecer?
Tentei resolver todas essas situações mas não teve sucesso muito obrigado pela ajuda
Desculpe pelo meu Inglês
You're right about USB tethering and even other stuff, that must be implemented not only by changing a property, but chinese always operate like that, of course this Android 12 (property) is to attract more customers !
Disable share contacts within Google account settings on the headunit, and enable share contacts at Bluetooth settings of your phone. That should fix it.
I flash the last version that was post here and all work fine for me. I have a Navifly m700sAre you using a Mekede as well? I still haven't updated Carlink, because I'm wondering if it's perhaps meant for use only on Joying? But did you install the zip? I tried the APK on my phone, and one thing I noticed: it contains another app logo, than the current Carlink on my headunit.
I'm a bit reserved with flashing random versions of Carlink, just to not break things.
It seems our Russian friends at 4PDA, already found a fix for the home launcher that keeps changing back to the default one: after changing to another one.
So it's really that easy? And what's the point of this Digital Wellbeing App anyway? Or is it lost in translation?
I just doing backup and restore, and now l can’t use the 360 camera view. And then I got firmware for Teyes CC3, it’s works but requires software cativation. Now I can’t downgrade to firware before Aug 2022 .
I tried to unpack the firmware with 7zip and add some changes firmware, but it failed verify whole signatures. How to unpack and repack firmware in the right way, thank you.
twipe_all # Wipe entire system twipe_data # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults" twipe_cache # Will wipe the cache of the apps thereby removing the temporary files that are stored for those programs. twipe_sd # Will wipe internal memory /sdcard (but not the data partition) dellapp # Remove all 3rd party apps make_updates # Make an upgrade U-disk boot file test # test unit and firmware before flash
ro.product.locale = pt_BR ro.sf.swrotation = 90
persist.sys.zlink.mic.vol=9.9 persist.audio.mic.senstivity=1 persist.btmic.gain=10 persist.btspk.gain=7
com.zoulou.dab = -10 net.dinglisch.android.taskerm = -10
brotli -vd system.new.dat.br -o system.new.dat
sdat2img.py system.transfer.list system.new.dat system.img
mkdir system sudo mount -o loop system.img system ls -Rl system
sudo mount -o loop system.img system sudo mksquashfs system system.img.sqsh sudo umount system
sudo mount -o loop system.img.sqsh system
Apart from the /oem partition and a few others, the /system, /vendor and /product partition are read-only. In earlier FYTs, you could use the lsec script to make them read-write and then modifiy content, add/remove files/apks, etcetera from these partitions. The big disadvantage for modders with these new dynamic partitions is that you can't make them read-write anymore.Dynamic partitions are a userspace partitioning system for Android. Using this partitioning system, you can create, resize, or destroy partitions during over-the-air (OTA) updates. With dynamic partitions, vendors no longer have to worry about the individual sizes of partitions such as system, vendor, and product. Instead, the device allocates a super partition, and sub-partitions can be sized dynamically within it. Individual partition images no longer have to leave empty space for future OTAs. Instead, the remaining free space in super is available for all dynamic partitions.
lsec6315update lsec_update/7862lsec.sh "stuff that needs to be copied/moved/installed"