There's only one known system that's new enough still.Головные устройства Unisoc на процессоре UIS7862 / SC9863a (UIS8581A) Android 10, [Головное устройство][Автомагнитола][Android]4pda.to
Thank you so much. So I downloaded the latest lsec6315update file and the 6315_1.zip file and replaced them with what I had on my USB and was able to successfully flash the full firmware. Before that I got my backup also, will post some updated system info soon thanks all!
What did reseller suggest when contacted for supportI recently got an S8 Ultra G2 for my car but decided to temporairly put it in my truck to play around with it while my car is in the shop. I have a bluetooth issue with the unit as it shows all connections as noName and I had to figure out wich one was my phone, LOL but when I tried connecting the OBDII for the torq app it shows noName and looks like a headset icon. I select it and it ask for the pw 1234 and it will connect for like 3 seconds and disconnect. Im running the latest 2022-04-15
I've tried factory reset and even reflashed the firmware with no luck. I did notice that under system info It shows Bluetooth version as Unknown.
Any ideas on how to correct this?
ATOTO S8 Ultra G2
kernel:#251 SMP PREEMPT Fri Apr 15 12:02:28 CST
platform: (61)6315 AF America Full Band carplay2
touch:goodix 911_1060 (fa3916ff)E:0
cust:Fri Mar 20 14:21:10 2020
APP 1024x600 2022-04-18 09:36:58
System 2022-04-15 12:20:35 Friday
I contacted ATOTO directly, was told to reset all wireless connections. No luck
Suggest warrantyI contacted ATOTO directly, was told to reset all wireless connections. No luck
Factory Reset...No luck
Sugested update but I'm on the latest one.
Even tried reflashing firmware with no luck.
Not getting the OBDII working isnt a deal killer but I did like the thought of real time info VIA the head unit
Again, that's for the fyt sc9853i, so may or may not apply here.#27. Improved Bluetooth Pairing (still far from perfect)
This is not a great solution. It is more a simple work-around.
Before flashing your firmware, you should update one line in the config.txt.
Set line "sys.fyt.bluetooth_type=1" to "sys.fyt.bluetooth_type=0". Now flash the firmware.
If you already flashed the firmware, you can do a "config.txt flash only" using my zip attached to this post.
See also #14.
#28. Order of Bluetooth pairing
Say you have an OBD2 dongle, it sometimes pairs immediately and it sometimes doesn't.
Disclaimer: Some will never pair. The Bluetooth ID-string need to contain OBD.
First in the BT contect settings "forget" your paired phone(s). (Not only unpair but really remove them).
- your dongle is compatible, but it will still not pair.
- your dongle is compatible but it will only pair using pincode 1234 (or whatever code).
Now pair your OBD2 dongle. If necessary, first set the pincode in your unit to the pincode of your OBD2 dongle,
After having successfully paired your OBD2 dongle , you can now pair your phone(s) using the same pincode.
Got this in my email,
Using bilt in BT and the OBDII is ATOTO AC-4450Which dongle do you have? I haven't tested yet, but I remember reading about a whitelist. Most of the pictures of included dongles look like your average elm327 clone though. Maybe it'd work with the soc's internal bluetooth (by setting sys.fyt.bluetooth_type=0 instead of 1), or maybe via the stock android settings > bluetooth (see first post, fyt settings explained, Mario Dantas' app). Just guesses though, and the internal bt can be a bit unpleasant to use.
That did It thank you. I did get an email with a config.txt attachment from ATOTO support just a few min ago. I opened it and noticed the bt type is 7.also has a lot of other things on it. I will try it later today. Its a little after 3am here. lolWhich dongle do you have? I haven't tested yet, but I remember reading about a whitelist. Most of the pictures of included dongles look like your average elm327 clone though. Maybe it'd work with the soc's internal bluetooth (by setting sys.fyt.bluetooth_type=0 instead of 1), or maybe via the stock android settings > bluetooth (see first post, fyt settings explained, Mario Dantas' app). Just guesses though, and the internal bt can be a bit unpleasant to use.
edit: From a different thread about an older device: https://forum.xda-developers.com/t/q-a-tips-info-roll-up-joying-fyt-sc9853i.3979377/post-80459061
Again, that's for the fyt sc9853i, so may or may not apply here.
It was quite a bit larger than the 2mb one (smallest I got it was ~30mb, which is smaller than the ~50mb that is in the T'eyes mod oem/fem location). The bootanimation I made is a proper bootanimation for Android but maybe not for my device due to size and the fact I made it full screen resolution instead of the mid-screen sized one that comes default. However, flashing the original that I pulled from the oem software didn't fix the bootloop afterwards either. I ended up recovering it by reflashing the oem software back over it without a wipe."My" script uses the standard flashing option for a bootanimation.
Copying it to the partition no longer works as FYT uses dynamic partitions since Android 10 which can't be modified. It must be done during flash.
There are 3 locations (as far as I know) where you can put bootanimations where Android will look for it. The flashing one of the lsec6315update takes the default one.
I do not know why you got into a boot loop.
Did you test it? Are you sure you made it correctly? Is it not too big?
Looks like Android recovery menu.An interesting discovery:
After firmware flash failed due to newer firmware on the unit.
I waited about 120sec and then pressed the home button on my HU.
I noticed there is a menu but I am unable to select any as soon as I release the home button.
Maybe an other tester can figure it out.
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"