Not February 2020, in September 2020.
Depending if it is Asian date format or English date format, this ROM is from 5 February or 2 May.
Someone really put some effort in this fake.
Not February 2020, in September 2020.
Not February 2020, in September 2020.
Depending if it is Asian date format or English date format, this ROM is from 5 February or 2 May.
Someone really put some effort in this fake.
I did in my reply. Check the link I included.
That's Wikipedia. I don't think AliExpress will accept it for a dispute
That's Wikipedia. I don't think AliExpress will accept it for a dispute
Thank you so much!![]()
Android 11 Beta is available today
Android 11 focuses on three key themes: People, Controls, and Privacy. Available in Beta today.blog.google
That't the beta announcement.
The floating dot is touch assistant, you can go to the app and uncheck the options to turn it off.I installed some apps (then uninstalled) and now I have a strange behaviour of the screen, it scroll up and down (1 cm down) and seems to load something. I tried to stop some android processes and uncheck buttons of Nexi Voice App , but remain the upper left white dot point and nothing happens. I think to reflash the fully Mekede rom... Other solutions?
Don't know but it seems significant enough that you can't rollback to the previous firmware.hello everyone, I installed the latest firmware (2022-10-27) distributed by JOYING official on the unit.
I haven't seen any particular improvements, but I noticed that the date of the baseband version has changed.
Does anyone know what this baseband version means?
I had problem with my 7862 NOR FYT=1 , see my last post. I resolved the problem : I updated the mcu with latest MCU NOR_with 360 system 20220624_E60.rar , then flashed latest firmware (2022-10-27) distributed by JOYING official.Hi, I have a Chinese UIS7862 head unit with FYT=1. All is working well except that there is frequent restart whenever i start navigation using Google Maps. The head unit would go unresponsive up to a point the system restarts itself. Sometimes the system will restart randomly when I play Youtube videos.
At this point I do not know what is the actual root cause of this happening, but I keep getting the issues almost everytime i'm driving.
Does anyone have similar issues?
Hi all,
When I bought the Navifly M700S, it came to me with two wires to connect on the back. At the other end of one of the cables was a USB plug, while the other cable had two USB plugs. I think all these devices have these cables supplied. Indeed, I also received a cable to connect to the original USB port of my car (a Peugeot 308) but unfortunately I do not know where to connect the other end of the standard USB plug to the car located on the armrest.Hi all,
I was looking android headunits and found some are offered with 3 USB ports. Then I looked at the pinout for my HU and found out that connector E has two USB inputs. Could I just make a 6 pin connector with all the pins connected or do I need to activate the third USB port somewhere?
Im not sure if my issue has anything to do with mcu. Anyway, my unit is without 360, maybe i can give it a shot to update the mcu. Where did you get the mcu update file from?I had problem with my 7862 NOR FYT=1 , see my last post. I resolved the problem : I updated the mcu with latest MCU NOR_with 360 system 20220624_E60.rar , then flashed latest firmware (2022-10-27) distributed by JOYING official.
After some further reading. I found the mcu update file from 4pda site (MCU NOR_without 360 system 20211009).Im not sure if my issue has anything to do with mcu. Anyway, my unit is without 360, maybe i can give it a shot to update the mcu. Where did you get the mcu update file from?
no probz for 360 camera I don't have it, try the mcu I suggested to you , it works (recommended on 4PDA)After some further reading. I found the mcu update file from 4pda site (MCU NOR_without 360 system 20211009).
I will try update the mcu and see if it fix the instability issue.
hello everyone, I installed the latest firmware (2022-10-27) distributed by JOYING official on the unit.
I haven't seen any particular improvements, but I noticed that the date of the baseband version has changed.
Does anyone know what this baseband version means?
Don't know but it seems significant enough that you can't rollback to the previous firmware.
Sorry for asking without searching. And thanks for the clear answer.Please do some googling both.
Baseband version updates are part of normal Android updates/patches. In this case FYT has obviously updated the underlying kernel with available patches from Android.
Baseband is the low level firmware for the "radio" which in this case is for (cellular) calling, WiFi, Bluetooth, texting. (so not the AM/FM radio).
Please can you point me to the firmware version? Of the 14 listed here, which is relevant for generic FYT units?hello everyone, I installed the latest firmware (2022-10-27) distributed by JOYING official on the unit.
Updating the MCU does not fix issues with missing canbus functions.yes, I just have yin and the parody looks like I have the newer N32, only I have problems with can, no ambient temperature, reversing sound and resetting the backlight of the side keys... is it possible to upload this older mcu g23 as above?
This looks like a 7731 unit but I am not sure whether it is a FYT unit. Looking at the systemUI it is a FYT.Hi i need split screen supported launcher.
my device info at attached photo
Upper kernel 6316 is newer than lower one, that's allI do not know how to compare these two files, which is newer, which is older and possibly which matches my radio .... config.txt files are the same, while in one file 6316_1.zip is slightly larger.... the difference as in the picture.
Yes, it is. You do need to read post #1 and #2 though to get the necesary background info.Is it possible to run a custom ROM or another seller’s FYT unit’s English ROM so I can have an English UI?
Binary | Unit | Script |
lsec6315update | uis7862 (ums512) | 7862lsec.sh |
lsec6316update | sc9863a (uis8581a) | 8581lsec.sh |
lsec6521update | sc9853i | lsec.sh |
lsec6523update | sc7731 (uis8141e) | lsec.sh |
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"
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!
Cheers!