yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] mariodantas:
New release today:

2023-04-03

Fixed April 1st release bug: Now provided with the new updater (lsec6315update)

TYPE: MD-EDITION-UPDATE
[FYT Android Head Units] mariodantas:
Fixed in the 2022-04-03 Release, download and reflash please !
[FYT Android Head Units] mariodantas:
Never tried that, my FYT units don't have SDCARD slot
[FYT Android Head Units] mariodantas:
With my 4G sim I receive incoming calls in me car's phone number without issues in 2023 kernels, I have FYT1 and FYT31 units installed in the car !
[FYT Android Head Units] Bodyroro:
Great job, works perfectly. the root is unfold without incident. the fluidity is perfect
[FYT Android Head Units] mariodantas:
This was already implemented, the new unlock code is intended to be used when you click the "Lock device" (leave car in mechanic etc.... no one can use your unit) and now youy can unlock using email by default, of code is provided in settings the it will ask for code instead of email, and can also unlock by paired bluetooth device connection !

The application lock code isn't the same feature as the device unlock code !
[FYT Android Head Units] mariodantas:
Since 2022, I created XML profiles for 8Gb RAM units and improved those existant for lower RAM units, they should perform a little bit better than stock firmware !
[FYT Android Head Units] marduk25:
How to receive incoming calls? I use Tue phone app for outgoing calls
[FYT Android Head Units] mariodantas:
I have Google phone app ! and it works !
[FYT Android Head Units] surfer63:
See thread General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware Q&A: Q20
[FYT Android Head Units] arca114@gmail.com:
Friend I have the folder in hand how do I find now what I want to add in all update.
[FYT Android Head Units] Moldeb:
Right now I've got a problem after updating: Device is now "managed by organization" (=FMC) and blocks access to USB device. In Android settings / memory I can see it but it's unmounted. Mounting is blocked by FMC. Any idea?
[FYT Android Head Units] mariodantas:
FMC get ONLY admin rights when you clock "Lock the device" the it releases admin right when you unlock the unit !

Something went wrong !

Releases are commited after at least 20 tests here !,
[FYT Android Head Units] Moldeb:
SD cards are also blocked.

This is what I did: Installed 0304 MD-Edition-Update wirh Mainservice over 0104 version, added an unlock code, locked and unlocked to test (seemed ok). After that I wanted to install another launcher from a different USB stick - was not recognized (update did not start), original update stick same, empty stick also blocked, SD-Card also blocked.

This is what I see (sorry system speaks German but it's effectively in Android settings (storage).
[FYT Android Head Units] mariodantas:
let me check here, again !
[FYT Android Head Units] mariodantas:
what did you update ? MD-EDITION Kernel with FMC or FMC Update ?
[FYT Android Head Units] mariodantas:
nothing wrong here
[FYT Android Head Units] Moldeb:
Full update
[FYT Android Head Units] surfer63:
Please start a new topic/thread about this SystemUI. This has nothing to do with Mario's Kernel and is here completely off-topic.

I will answer you in your new thread.
[FYT Android Head Units] surfer63:
Your USB-stick is corrupt. Please run a checkdisk and repair on your usb stick.
[FYT Android Head Units] LLIyT_HuK:
You are wrong. Boroondook did one teyes-style build of SystemUI, but there was no mains voltage. Konig didn't do that. In the photo, the device is from topway (ts10 / 18) or from the latest teyes assemblies. I tried to do it on fyt, but the limitation is in the MCU
[FYT Android Head Units] Moldeb:
No it's ok. I've tried multiple sticks plus a MicroSD. Definitely blocked by FMC as system admin app.

Resolved: I've disabled lock with code and only left the old method (e-mail/BT) active. Locked + unlocked using the old method. System now ok again so can access USB / MicrSD storage again.

I've also removed my account before I did the above lock/unlock but don't think that was relevant.

One additional observation: My unit has a tool bar when you swipe down twice (first swipe is status bar, second is tool bar containing a reboot feature etc.) That tool bar was also gone while I had the external storage issue and is now back.
[FYT Android Head Units] arca114@gmail.com:
OK.
[FYT Android Head Units] LLIyT_HuK:
usually a problem with USB happens when there is no request for permission and there is no this program in allappupdate
[FYT Android Head Units] Moldeb:
Good point! This is on a rather new unit and I had not yet installed DocumentsUI when I did the MD-Edition update + Code lock/unlock. I installed it thereafter but the damage was already done I guess.

I've just tried the code locking feature again and now everything works well - so the error did not occur again.

Interesting that the issue only occurred in the code unlock version, I tried the classic email based version before with no issues (despite missing DocumentsUI).

@mariodantas I guess it is a system requirement then to have DocumentsUi then ;)
[FYT Android Head Units] surfer63:
You are right. The application uses a lot of permissions (like

<uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_MEDIA_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

)

But I don't see code that really requests these permissions.

Something like

private void requestStoragePermission(){
if(ActivityCompat.shouldShowRequestPermissionRationale(this,arrayOf(android.Manifest.permission.READ_EXTERNAL_STORAGE,android.Manifest.permission.WRITE_EXTERNAL_STORAGE).toString())){
Toast.makeText(this,"Need permission write whatever I like to external storage",Toast.LENGTH_SHORT).show()
}
ActivityCompat.requestPermissions(this, arrayOf(android.Manifest.permission.READ_EXTERNAL_STORAGE,android.Manifest.permission.WRITE_EXTERNAL_STORAGE),
STORAGE_PERMISSION_CODE)
}

But of course: it is very hard to detect that from smali code.

A system app doesn't need to request this.
[FYT Android Head Units] surfer63:
Yes: You definitely need that. (I also described that in my thread under Q&A: Q20)
[FYT Android Head Units] LLIyT_HuK:
I'm weak in code, took it for granted. In most mods. firmware on 4pda it is customary to insert this program into allappupdate.bin/priv-app/.

Doesn't take up much space, but USB works
[FYT Android Head Units] Moldeb:
Well yes I'm aware of the general requirement for other apps like file managers - and I had installed it a bit later. I was not aware that MD-Edition requires it once you use code unlock. That was my point.
[FYT Android Head Units] arca114@gmail.com:
Apk camera for anyone interested in having access to the rear camera of the vehicle when moving can access it at any time..
[FYT Android Head Units] mariodantas:
Maybe check for the presence of the package before locking the unit ?

Wow, now I'm pretty confused about this behaviour, so, using email, the lock/unlock device works well but using code this didn't work as expected ?, I really don't see what documentsUI have to do here, I'm not sure about what to do next !
[FYT Android Head Units] Moldeb:
Just define it as requirement in the documentation - people should have it anyway. And they should have it before installing MD-Edition on a new unit, not after as I did ;)

My other (older) unit is fine, it has had DocumentsUI for a long time ;)

Checking for the package on first using the locking function would of course be ideal but described in the documentation is good enough I think.
[FYT Android Head Units] surfer63:
documentsui has nothing to do with the locking.

the Documentsui.apk is necessary when a non-system app wants to access the internal/external SD.

You can't make the documentsui.apk part of the Kernel, but you could add it in the lsec script, just like the fmc "install". But that is of course completely up to you.
[FYT Android Head Units] LLIyT_HuK:
It seems to me that you should not do this ... Very often this apk is located in different places and with a different name, because in this way you can duplicate it and possibly break it
[FYT Android Head Units] mariodantas:
The point is, that I'm not reading/writting anything (I mean the FMC code) when locking/unlocking the device either by email or code)

So I still blind in front of this behaviour !

Sorry fellows,
[FYT Android Head Units] mariodantas:
Do you thinks that, if I included DocumentsUI as an FMC asset or raw file, and at the first launch I check for existence (by package name of course), and if not I install it silently would be a good Idea ?
[FYT Android Head Units] Gscipione:
I have installed md-edition without documentsui and I had no problem on my HU. My hu is a medeke m6pro with Uis7862s. I have no problem with usb stick
[FYT Android Head Units] mariodantas:
Ahhhhhh, Android, dear Android.... LoL
[FYT Android Head Units] mariodantas:
Added in my TODO list

DONE
[FYT Android Head Units] mariodantas:
I think that you had FMC normal version already installed when you flashed MD-EDITION (wich come with a different FMC)

Solution: Uninstall FMC (if it was your case) and reflash

Maybe, Have to look into, but have already more than 10 users reporting that it works flawlessly

Let me check the code again.
[FYT Android Head Units] mariodantas:
Found it

You didn't flash the 6315_1.zip file or it doesn't flash correctly

The message only appears if app is System App and mdedition flag ins't found inside the system partition, so you have the system app (Platform Edition) but not the Kernel ?

Download it from *** HERE *** and flash your system again !
[FYT Android Head Units] marchnz:
Perfect, latest (19/01) flashed.

Proper [BOOT_COMPLETED] handling is the feature I wanted and ability to autostart in background. I use JBV1 which leverages Waze, this app connects to Valentine One Gen 2 radar detector. Now it reliably autostarts with wave in background.

Thanks Mario.
[FYT Android Head Units] Bettman66:
If that works, I'll switch from an MTCE device to an FYT device. It would also be nice if the device automatically unlocks itself when there is a Bluetooth connection with the mobile phone.
[FYT Android Head Units] Moldeb:
Thanks much for the good work, installed smoothly! One question though on the above: I have two FYT units and it seems I have to register (not just log in) on each unit - do you really ask me to set up two users on your site?

Other than that, everything seems to work apart from things not yet active (launchers via cloud?)

One thing I've noticed is a pop up message (I don't have full details as it is cleared too quickly) complaining about a package mario.dantas[something] failing to do something on some channel - no precise idea, may come from Agama launcher as that brings up such a pop up e.g. when another mp3 is played (artist etc info from mp3 player when player in background). May be an Agama issue.

Edit: Also have been using your Android Shortcut Settings for a long time and did not uninstall before installing MD edition - suppose that's neutral or should it be uninstalled? Back then I installed it mainly to access BT settings but they're now in MD Edition anyway...
[FYT Android Head Units] mariodantas:
If the register form detects your email in the database it will behave as a login form (Will instroducs more information in upcoming updates)

Completely dissociated app, nothing to do with MD-EDITION its behaviour is the same as in original firmware
[FYT Android Head Units] yokala:
Super boulot, merci Mario !

Do FMC handle autostart for accessibility settings ? I have an 11.6" unit with some tweaks here and there to make it work in portrait mode only, and with the stock firmware I use FYTStarter to autostart a tasker task to launch 2 apps at the same time in split screen, witch require accessibility settings (unfortunately it's not working at every wake).

Also, a while ago I modified the 190000000_com.syu.us.apk app to change some hidious graphics when the reverse cam is on (if you never saw them it's because it's only visible in portrait mode), it's from a quite old firmware, you think I could install my modded version with your firmware ?

Thanks
[FYT Android Head Units] mariodantas:
Of course because com.syu.ms has nothing to do with kernel level, it is included in applications level
[FYT Android Head Units] yokala:
That's great :) and what about auto start accessibility services ?
[FYT Android Head Units] mariodantas:
Please name some f the service you yant to autostart ?
[FYT Android Head Units] yokala:
I mainly use tasker and a small app called ''Always visible split screen'' witch display a tiny floating button to engage split screen more easily. Both of these apps need accessibility services enabled to work and as you know the stock firmware disable all apps in accessibility services everytime it goes to sleep or reboots.
[FYT Android Head Units] mariodantas:
Share that app here, I'll take a look and see what can I do for it !
[FYT Android Head Units] mariodantas:
New release today, check post #1 and #3
[FYT Android Head Units] yokala:
Tasker :

Tasker - Apps on Google Play

Automate everything from settings to photos, SMS to speech. ADC2 prize winner.

play.google.com

always visible split screen :

Screen click macro splitscreen - Apps on Google Play

Click the button to split the screen.

play.google.com

Thanks man !
[FYT Android Head Units] mariodantas:
Will check it ASAP !
[FYT Android Head Units] marchnz:
Hi Mario, I have a similar request - JBV1 accessibility service

JBV1 - Apps on Google Play

A companion application for Valentine One Radar Locators. DRIVE AWARE.

play.google.com

Have to wonder why the chinese developers disable accessibility services.
[FYT Android Head Units] spendaccia:
EDIT:

Hi, I want to install the firmware in my fyt 116 unit. After installation, will I lose my car stereo settings (rear camera / steering wheel control)?

Ciao, voglio installare il firmware nella mia unità fyt 116. Dopo l'installazione, perderò le impostazioni della mia autoradio (telecamera posteriore / comando al volante)?
[FYT Android Head Units] marchnz:
FYI - reported, not english, off topic/thread hijscking
[FYT Android Head Units] mariodantas:
That's exactly what I'm doing now, crawling the firmware to find the reason (and if possible bring it as a NORMAL android should be)
[FYT Android Head Units] Moldeb:
Have you tried to lock using the new code method? My unit ran fine otherwise too.

Anyway - maybe it was a hickup, it's working now. Don't know whether it was in relation to DocumentsUI or not but I could definitely not mount USB sticks or MicroSD as long as the issue persisted. As my screenshots say, it was forbidden by FMC as my system administrator ;)
[FYT Android Head Units] Gscipione:
Yes and work all fine. No problem
[FYT Android Head Units] mariodantas:
I hope this is not a bug, becouse FMC disables USB and many stuff to avoid unattended people to try to reflash unit etc ! while locked of course !
[FYT Android Head Units] Moldeb:
When it happened, first thing I tried was to again lock/unlock using code, this did not help (DocumentsUI was not installed on the first lock/unlock but at this stage it was). I then removed my google account (no help). Then I disabled the new code method but left the old method active as I knew that was working. Locked/unlocked using the old method and the USB became available again.

Originally I then re-added my google account and planned to ignore the new code lock method for the time being as everything else seemed to work. Based on the discussion here I gave it another try (re-enabled code lock) and from then on it's been working fine.

So yes, maybe a hickup. As I didn't have to reset the system and it's working now I guess I won't be able to reproduce this...
[FYT Android Head Units] badwhip:
would be cool if it allowed recording
[FYT Android Head Units] arca114@gmail.com:
Yes friend, but unfortunately it's not possible, I removed this apk from a Russian rom, I've been looking for it for a while..
[FYT Android Head Units] badwhip:
My ATOTO already allowed this from factory the TEYES allows you to record from rear now.
[FYT Android Head Units] arca114@gmail.com:
You can't copy the apk file or provide the rom link, for me to try to extract.
[FYT Android Head Units] badwhip:
I can send you a copy of the app that came with my radio tomorrow
[FYT Android Head Units] mariodantas:
Here a BETA MD-EDITION witouth Mainservice that SOULD allow incomming calls using Google Phone app, I can't test as my car is yet in the paintshop !

If anyone here wants to test a report feedback, here is the attached kernel !

Download it HERE !
[FYT Android Head Units] Clandaries:
I would but unfortunately i cant test it on my Hizpo S8 and my Teyes CC3 :(
[FYT Android Head Units] LLIyT_HuK:
I can check in the evening after work.
[FYT Android Head Units] Clandaries:
FMC does not work on CC3 rooted with Magisk, right?
[FYT Android Head Units] mariodantas:
Nope
[FYT Android Head Units] arca114@gmail.com:
I'm waiting.
[FYT Android Head Units] Clandaries:
I always buy the wrong head units :)

Would love to use your Mod.
[FYT Android Head Units] badwhip:
here you go
[FYT Android Head Units] arca114@gmail.com:
Friend thanks for the app, but the record function did not appear, but the operation looks like what I posted .. Thanks again ..
[FYT Android Head Units] badwhip:
im sorry it must of been a miscommunication. it doesmt have record. the teyes is supose to have it.
[FYT Android Head Units] Renval:
hi, I installed the complete kernel but now every time I turn on the car stereo it always starts with the animation and gives me the right time with a little delay. before the update, the launcher appeared immediately. What can I do? Thank you
[FYT Android Head Units] mariodantas:
Nothing fellow, the FMC app needs a little time to put his service in place and this takes ressources from unit ! If this is a real problem for you, I'm really sorry and recommend you to rollback to your old kernel !
[FYT Android Head Units] PaY87:
For me its the opposite. With Marios kernel is the first time that my car starts with correct time. Before my time and date always got a reset by the unit and I had to wait for GPS.
[FYT Android Head Units] arca114@gmail.com:
Let's contribute with a coffee for the effort of everyone involved in improving the MD EDITION project, a small thank you and we will have more and more improvements and news!!

Donate to Mario DANTAS

Help support Mario DANTAS by donating or sharing with your friends.

www.paypal.com
[FYT Android Head Units] linuxaro:
another coffee ,thanks Mariodantas
[FYT Android Head Units] badwhip:
does the joying radio have duel bluetooth?
[FYT Android Head Units] fagner:
Hi, how to disable log "YLOG-ZIP:run 'python analyzer.py' to unzip me" 000-1231_210010_poweron.ylog. is creating this log and flooding the media
[FYT Android Head Units] BRainXstorming:
@mariodantas hey thanks for your work. I cant wait to install it on my joying radio! I read that you did something with bluetooth. would it now possible to connect a normal bluetooth remote crontrol for mobiles? I dont want to install external steering wheel controls.
[FYT Android Head Units] Renval:
Greetings. but did you make special settings or did the time and date immediately appear correct immediately after installing the kernel? Thank you
[FYT Android Head Units] j0hn83:
No other changes should be needed. The time and date will still reset with Marios kernel but it should update quicker after a reboot.

My understanding of how it works is as follows....

The time and date resets on all these units when they are rebooted. There's likely nothing you can do to prevent this without making considerable hardware modifications.

The time and date updates when the units boot up and either

1. Connect to the internet, or

2. Establish a GPS fix.

Mario has made changes that means his kernel uses " supl.google.com network for fast location acquisition instead of chinese servers " meaning the GPS should connect quicker and the time/date should update quicker.

On my unit the time updates much quicker with Marios kernel vs the stock kernel, but it still isn't immediate.
[FYT Android Head Units] surfer63:
I assume "dual". The answer is No.
[FYT Android Head Units] Renval:
Ok thank you
[FYT Android Head Units] surfer63:
Don't repeat your question within 5 hours. Have patience until someone who knows what is going on can answer you.

Respect the forum rules.

There is no need to spam us all.
[FYT Android Head Units] aiui:
Hello, I tried to install but I couldn't, I got the following error.

E:Signature verification failed

E:error:21

Installation aborted.

update error reboot in (447)seconds!

what can I do?
[FYT Android Head Units] mariodantas:
Indeed, they haven't backup battery
[FYT Android Head Units] mariodantas:
What version did you download ?
[FYT Android Head Units] mariodantas:
Not MD-EDITION Kernel related !
[FYT Android Head Units] aiui:
FYT_7862_FIRMWARE_MD_EDITION_WITH_MAINSERVICE
[FYT Android Head Units] fagner:
When I install your kernel, it keeps creating infinite logs, when I install the kernel without changes that you made available on google drive it doesn't create these logs
[FYT Android Head Units] mariodantas:
Never enabled that by default but will check and put it off by default in the next release !
[FYT Android Head Units] surfer63:
Share some of those logs so that we can see what is in it.

Nobody has a clue right now.
[FYT Android Head Units] mariodantas:
What date ?
[FYT Android Head Units] fagner:
When I inject the pendrive it creates this folder and files on the pendrive, my media is default.
[FYT Android Head Units] mariodantas:
@fagner I'll disable YLOG in the settings by default for the next release, this week end maybe !
[FYT Android Head Units] aiui:
2023-04-03
[FYT Android Head Units] mariodantas:
Use this lsec6315update
[FYT Android Head Units] mariodantas:
Ok YLOG disabled by default (can be enabled again in Engineer mode) will release this WE !
[FYT Android Head Units] WarSpaz:
Just a couple of questions.

I have ordered a FYT unit with 8gb ram and 1920*720 resolution and from what i can understand this will make better use of 8gb than the stock kernel.

1. Is this a complete ROM or as stated a kernel update only?

2. Will quick boot work as it normally would or will it force a full restart every time?

3. Does this install make the unit rooted as default or is it only an option to enable?

Thanks in advance!
[FYT Android Head Units] LLIyT_HuK:
1. Kernel update

2. As usual

3. Default off, can be turned on
[FYT Android Head Units] mariodantas:
@LLIyT_HuK fastest support !, Congrats fellow !
[FYT Android Head Units] mariodantas:
By the way, in a couple of days I'll release here a REVIEW of a "not yet released" compilation, managed by @LLIyT_HuK and also created (modded) by himself, the result is beautifull but I can't say more before crawling that packages.

But after taking a little look at the creations I start calling @LLIyT_HuK in a friendly way like, "My XML master".

This has nothing to do with MD-EDITION I know, I leave this here to keep you in touch, because this compilation of mods seems (by the moment) to be something that will keep your attention.
[FYT Android Head Units] aiui:
gives the same error, can I use my lsec6315update
[FYT Android Head Units] mariodantas:
Yes but I don't understand as I didn't have problems with this lsec6315update, and by the way I think that it's the last version released by FYT
[FYT Android Head Units] surfer63:
A little bit late, but did you check your SD-card/USB-stick for errors?

This error can also simply be a corrupted 6315_1.zip which is why the signature not fits the total zip file.

So do a check on your usb-stick and correct it. Then unzip the kernel zip again and flash it.
[FYT Android Head Units] mariodantas:
New release today:

2023-04-07

Kernel level: Disabled YLOG by default, can be enabled again in Engineer mode settings

FMC: Added Engineer mode settings link

FMC: Reorganized Settings page

TYPE: MD-EDITION-UPDATE