i use antenna on passat b6 ,please photo
"Listen" to what @Clandaries says.
i tell, i dont have active antenna, it is car antenna, please see cable"Listen" to what @Clandaries says.
This has nothing to do with either FYT or another type of unit (MCD/E, Topways, whatever)
This has to do with having an active antenna or not.
If you have an active antenna, you need to connect the "blue wire". It is a blue wire on a FYT. If your unit is not a FYT, the color may be different.
Our posts crossed.
I really have no idea. I never used such an app. Did you contact the developer? [email protected]surfer63, i have app (tv app) why i cant use, i dont see video, it is problem from dev app ?
the older versions worked, but I can't use them anymore, ask for an update, I connect to the radio via hotspot, the internet works
i need too activate in radio video codecs >?, i tried evrything, reset radio, reinstall app...
mp4 work ok
No idea about Isudar specifically, but my FYT 7862 (Mekede M500s) has a great reception. I would even say FM reception is slightly better than my original Kia stereo (made by LG I believe).
Please read post #2 bullet IX "If everything goes wrong ...". I think the modded apk blocks everything and I think you really have to force your unit in recovery mode, being option 3), and try with that update.
It is indeed brand new and they also use a new kernel.JOYING has released new firmware 2023-05-23
Why not just take ACC?Hello @surfer63 , can I use ANT wire for powering up my fan (i.e. could this 12V output power up my fan current-wise)? The fan I bought to install on my unit is a 70mA ball bearing fan, as it was advised here... The reason for asking this question is that my unit has two wiring harnesses, the one that has ground (required for fan -) also has ANT wire and the AMP wire is on the second wiring harness. So, aesthetically, it would be neater to use both (+) and (-) from one wiring harness. (I know I wouldn't see wirings after installation, I'm just curious to know if ANT could be used for this purpose but I can live with using AMP wire). Thanks
So I decided to give the firmware flashing a try.
I'd edited the fyt.prop from the AllAppUpdate.bin of the Joying 1280 x 720 MIPI Screen New UI firmware using Notepad++ to change ro.fyt.uiid= from 2 to 4, then got the 5 files in my formatted USB drive and got down to it.
I ended up with this:
And after the GOOGLE word loading was done and it rebooted I got this:
And it went into a loop
Am I understanding it correctly that the problem was specifically with the config.txt file and not the rest of the files?
Anyway, I decided to download a fresh copy of the Joying firmware, and this time I thought about what @bluemask69 said about not changing the uiid and I decided to try a Hail Mary and straight copying the 5 files from the new download over to the (re)formatted USB drive, unmolested i.e. I did not make any changes at all, ro.fyt.uiid=2 was left untouched.
And it worked I did not get any errors during or after. The GOOGLE word during the loading was upright this time ... the previous failed flashing the GOOGLE word loading was -90degrees like the above photos.
I don't understand though ... in a full firmware flash, the original company's boot animation still remains?
I see @surfer63's guide to change boot animation, but does anyone know where I get my hands on the Joying boot animation that corresponds with this particular firmware?EDIT: Nevermind, I found this firmware’s “Powered by Android” logo … selected it, and now the original company’s is gone.
Hi all ... I had an issue which turned out to be a setting I assume I’d set previously (I can’t remember it) but got wiped during the flash to the Joying 15 May 2023 update. I assumed it was a problem with the firmware, and I tried PeaceOS, which faced the same issue … I later realised what the issue was and set it correctly.Hi all,
So I'd flashed my unit with the Joying 15 May 2023 update. Everything runs fine.
However, it seems installing launcher from @mariodantas' FYT Factory doesn't work now? Or at the very least, it seems it doesn't work if it's a "UI4" because it does not overwrite the stock UI4. I tried a "UI6" as well and it does not overwrite the stock UI6. Or did I miss any setting after the flashing?
I'd tested installing 1 which is "UI20" and it works, so I guess it's just not overwriting the stock launcher.
config.txt overrules fyt.prop.
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=0
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 (uis7862(s)) lsec_update/7862lsec.sh (uis7862(s)) lsec6316update (uis8581a) lsec_update/8581alsec.sh (uis8581a) "stuff that needs to be copied/moved/installed"
lsec6315update (binary) lsec6316update (binary) lsec_updatesh (folder) 7862lsec.sh (shell script) 8581lsec.sh (shell script) OEM_APP (folder) 190000000_to_be_replaced (folder of the apk) 190000000_to_be_replaced.apk (some apk we want to replace)
#!/system/bin/sh #Remove the current app data/program cache/cache. This is only necessary for some applications, but it never harms rm -rf /data/dalvik-cache/profiles/190000000_to_be_replaced rm -rf /data/data/190000000_to_be_replaced rm -rf /data/dalvik-cache/arm64/*190000000_to_be_replaced* # # Copying file to /oem/app # cp -r /storage/sdcard1/OEM_APP/* /oem/app/ # # Updating folder/file access rights # chown -R 0.0 /oem/app/190000000_to_be_replaced chmod 755 /oem/app/190000000_to_be_replaced chmod 644 /oem/app/190000000_to_be_replaced/190000000_to_be_replaced.apk
Hi.Thanks for the good idea!
Unfortunately in my case, the cars SWC are all through CANBUS and so I haven't connected the KEY1/KEY2 inputs to the HU at all. In so doing, I am relying on the CANBUS manufacturer to intepret those button presses as "mode, vol +, vol - ", which is unfortunately unable to be remapped at the moment.
I may just install a simple aftermarket remote to the KEY1/KEY2, to use my current SWC controls, AND the after market ones in parallel. Then I will remap the after market buttons, to whatever I want, eg. Button 1 = Spotify, Button 2 = Tidal etc ".
Will update if I manage to get the parts off Aliexpress soon!