Question Alternative FM radio app for FYT-based Android head unit - FYT Android Head Units

Hello all,
I have an Atoto S8 which is a FYT based Android head unit.
MCU Version:
2021.04.26 13:48:17 YUF_53_L6315_G32P64F64_Ver: 1.0
CPU: UIS7862 Octa-core
I was wondering if anyone knows of or has an .apk of an FM radio app compatible with the FYT head units? I tried every app around and none of them work. The Navradio developer is still porting his app to this platform, so I was wondering if there's something else I might try meanwhile.

There are re-skins, but AFAIK the radio bits are part of the proprietary MCU

But if I got an .apk from a Joying head unit, it might work no?

I'm not so sure about that.
I think you would have to do some hand editing of some files at the very least. (To put in your fyt build number)
There is more info on it at the other forum.
I looked into it for a second weeks ago, but then I bought Poweramp and haven't really used anything else.
I agree that the fm radio all looks like crap though on my Mekede

Poweramp works with online radio?

Gaugamela said:
Poweramp works with online radio?
Click to expand...
Click to collapse
What was the result when tried

Gaugamela said:
Poweramp works with online radio?
Click to expand...
Click to collapse
Apparently it does. That's not what I meant, though.
I procured some 15-30 gigabytes of songs from different playlists from another source.
(I have to be vague because of forum rules)
Anything else I want, such as podcasts, I just stream via Bluetooth.

Gaugamela said:
But if I got an .apk from a Joying head unit, it might work no?
Click to expand...
Click to collapse
If your Atoto S8 is indeed a FYT unit, it might work.
What you carefully need to look at is the name of the apk. It has to be exactly the same as the one on your Atoto unit including installed libraries.
And then you need to write the corresponding lsecupdate.sh file and use the corresponding lsec6316update binary
and off course: make a backup of your current one.

I'm working on porting NavRadio+ to FYT units.
This last weekend, after 2 months of tries, i was finally able to get sound out of my app.
I already have control of the radio commands and infos so it's just a matter of put things together in the right way and iron out all bugs. Then i could release a first FYT version probably in the first days/weeks of the new year

KoTiX2 said:
I'm working on porting NavRadio+ to FYT units.
This last weekend, after 2 months of tries, i was finally able to get sound out of my app.
I already have control of the radio commands and infos so it's just a matter of put things together in the right way and iron out all bugs. Then i could release a first FYT version probably in the first days/weeks of the new year
Click to expand...
Click to collapse
I did not know you were working on this.
Please take a look at this github from lbdroid. It contains a lot of useful "reverse engineerng" information for the MCUradio for the FYT. It is still from the Sofia3GR but as far as I know hardly anything changed.

surfer63 said:
I did not know you were working on this.
Please take a look at this github from lbdroid. It contains a lot of useful "reverse engineerng" information for the MCUradio for the FYT. It is still from the Sofia3GR but as far as I know hardly anything changed.
Click to expand...
Click to collapse
The original fyt radio app now contain code for all the platforms and each platform use different approaches. The hard part was to understand which part of code is used by each platform and how.
Sofia units control radio and audio through MCU.
UIS7862 use the native jni libs to control the radio and audio is started by MCU.
Right now I'm working only on more recent UIS7862 units, i don't think I'll adapt it to Sofia or other older units.
I know that units with canbus use another APK too (com.syu.carradio) but it's not totally clear to me what it does exactly. Can somebody explain me it?
To make my app to work, because of the native libs, is mandatory to install in OEM folder a copy of NavRadio apk (not necessarily the full apk, even a fake app with same package name is enough to set NavRadio as system app).
To do this i have 2 ways:
- directly from NavRadio for rooted units with some root commands
- downloading a zip update package to flash manually the APK in OEM folder
If you guys have other/better ways to do this, please tell me, I'm new to these kind of units..

KoTiX2 said:
I know that units with canbus use another APK too (com.syu.carradio) but it's not totally clear to me what it does exactly. Can somebody explain me it?
Click to expand...
Click to collapse
I did "some" checking on this app a couple of years ago as I had a Skoda with Canbus. The standard radio in the Skodas (and I assume in all VAG concern cars) are partly controlled by the CANbus. The Skodas use an extension on the standard CANbus commands to switch on/off the radio in the cars when ACC is switched on/off. This is NOT a direct wired coupling of power, but really a digital on/off signal from the CANbus.
My Skoda had a simple Swing radio (hence another Android unit), but other Skodas had the MIB1 Amundsen/Columbus unit (navi/media/phone/radio/tmc and car menu). The car menu inside the radio is also controlled by the CANbus. My guess at that time (not having a MIB1 amundsen/columbus unit) was that that was also "streamed" through the carradio app.
Note: I am only sure for the on/off, the rest is an educated guess. And I assume other cars with CANbus displaying/changing "stuff" via the radio, instead of dedicated hardware buttons, do the same.
Maybe other users having a VAG (Audi/VW/Skoda/Seat) car with previously an MIB1 (or MIB2, but why replace that one?) unit and now an Android unit might have more info.
Please share.

And another question: RDS-AF on all FYT units is incorrectly implemented and already since early 2016.
Does your app has a properly working RDS-AF?
If I drive in the Netherlands from North to South (or the other way round ), I sometimes go through 7 (!) frequency regions depending on the station, but at least through 4.
Working RDS-AF functionality would really be THE reason to switch to it.
Edit: I know it works for Topway and the like, but I want to know whether it also works for FYT.

surfer63 said:
And another question: RDS-AF on all FYT units is incorrectrly implemented and already since early 2016.
Does your app has a properly working RDS-AF?
If I drive in the Netherlands from North to South (or the other way round ), I sometimes go through 7 (!) frequency regions depending on the station, but at least through 4.
Working RDS-AF functionality would really be THE reason to switch to it.
Edit: I know it works for Topway and the like, but I want to know whether it also works for FYT.
Click to expand...
Click to collapse
Normally AF is handled directly by radio chip. I still haven't investigated how it work on fyts.
My app can only enable/disable AF and on some units you can set the sensitivity of reception.
On MTC units that also receive the radio station ID (PI code) i added a function to merge the alternative frequencies in the same station preset in an array so that you can easily switch between them sliding up/down on the screen.
I can see in the logs that also fyt units receive the pi code but only at native libraries level (c++), i cannot handle it in java.
I know that we can change sensitivity and read the signal strength so probably something is possible to improve AF.
We'll see...

KoTiX2 said:
Normally AF is handled directly by radio chip. I still haven't investigated how it work on fyts.
My app can only enable/disable AF and on some units you can set the sensitivity of reception.
On MTC units that also receive the radio station ID (PI code) i added a function to merge the alternative frequencies in the same station preset in an array so that you can easily switch between them sliding up/down on the screen.
I can see in the logs that also fyt units receive the pi code but only at native libraries level (c++), i cannot handle it in java.
I know that we can change sensitivity and read the signal strength so probably something is possible to improve AF.
We'll see...
Click to expand...
Click to collapse
How is reading signal strength achievable?
Would be great to see real signal strength in app.

KoTiX2 said:
Normally AF is handled directly by radio chip. I still haven't investigated how it work on fyts.
Click to expand...
Click to collapse
A lot of Philips TEF6686 radio chips are used and RDS is part of the chip. Some of the cheaper units use a TEF6851 which does not have RDS. Or the budget STMicroelectronics TDA7786x which does not have RDS either.
But it is still the software that "should know" how to retrieve and use the RDS info and in this case specifically the RDS-AF. The FYT software is not doing that correct.
That's why I switched in my other "deceased" car to a DAB+ module using @realzoulou's DAB-Z which uses proper "service following" (as RDS-AF is called in the DAB+ world).
That was a great solution, but I still prefer not to have extra hardware connected when it is not necessary.

surfer63 said:
A lot of Philips TEF6686 radio chips are used and RDS is part of the chip. Some of the cheaper units use a TEF6851 which does not have RDS. Or the budget STMicroelectronics TDA7786x which does not have RDS either.
But it is still the software that "should know" how to retrieve and use the RDS info and in this case specifically the RDS-AF. The FYT software is not doing that correct.
That's why I switched in my other "deceased" car to a DAB+ module using @realzoulou's DAB-Z which uses proper "service following" (as RDS-AF is called in the DAB+ world).
That was a great solution, but I still prefer not to have extra hardware connected when it is not necessary.
Click to expand...
Click to collapse
I looked a bit at the logs during RDS-AF and it definitely is working wrong:
AF should search for an alternative frequency of the same station (identified by the pi-code), but somehow,after a while, if the signal strength is ok it switch to a station with a different pi-code.
All this seem to be controlled by the native library fmjni.so but i have no idea how to modify a c++ lib (maybe a revers engineering?)
Maybe I'll find some other way to handle AF using the logs but i can't promise anything right now.

KoTiX2 said:
I looked a bit at the logs during RDS-AF and it definitely is working wrong:
AF should search for an alternative frequency of the same station (identified by the pi-code), but somehow,after a while, if the signal strength is ok it switch to a station with a different pi-code.
All this seem to be controlled by the native library fmjni.so but i have no idea how to modify a c++ lib (maybe a revers engineering?)
Maybe I'll find some other way to handle AF using the logs but i can't promise anything right now.
Click to expand...
Click to collapse
I now think it even works differently for the standard FYT radio. My experience so far is only on Sofia 3GR (2 models), a PX5 and a sc9853i, no experience with the uis7862. Hopefully the uis7862 will arrive this week.
The RDS-AF only works for memorized stations. If I want to follow one station, for example NPO 2 FM, through the Netherlands, I need to add 4 frequencies (or more) and memorize these as presets.
It seems the radio app/mcu does not interpret the RDS-AF signal itself, but it seems to check (part of) the RDS data it has for a certain station, with RDS-data from other memorized stations. If part of it is equal (which part? only the station name itself?) with that other station (which you have to have memorized, otherwise it can't compare) and that station is stronger, it will switch to that station. If it can't find a stations from its memorized stations it seems to just select the strongest "whatever" station. This means that I have to blindly save 4 "NPO 2 FM" stations in the presets. And this for some other preferred stations as well. And of course: 1 frequency is what you can easily hear and set, but the other frequencies you have to google or so, because at the moment of adding it to a preset, you don't not have (sufficient) reception for that station.
"Real" RDS-AF should check the alternate frequencies inside the signal. Not do a "does some of the data look like a station I already have in memory".
I am a "restless" listener and listen to multiple stations. I switch when there is talking I don't like, a song I don't like, etcetera. I can't even memorize my five preferred stations in 18 presets.
In the Netherlands we have another deal breaker: FM frequencies are sold every five years and anyone can pay to it. It really means multiple different frequencies, whereas in some countries you only have one frequency for a station through the entire country, like in some countries in Azia.

surfer63 said:
I now think it even works differently for the standard FYT radio. My experience so far is only on Sofia 3GR (2 models), a PX5 and a sc9853i, no experience with the uis7862. Hopefully the uis7862 will arrive this week.
The RDS-AF only works for memorized stations. If I want to follow one station, for example NPO 2 FM, through the Netherlands, I need to add 4 frequencies (or more) and memorize these as presets.
It seems the radio app/mcu does not interpret the RDS-AF signal itself, but it seems to check (part of) the RDS data it has for a certain station, with RDS-data from other memorized stations. If part of it is equal (which part? only the station name itself?) with that other station (which you have to have memorized, otherwise it can't compare) and that station is stronger, it will switch to that station. If it can't find a stations from its memorized stations it seems to just select the strongest "whatever" station. This means that I have to blindly save 4 "NPO 2 FM" stations in the presets. And this for some other preferred stations as well. And of course: 1 frequency is what you can easily hear and set, but the other frequencies you have to google or so, because at the moment of adding it to a preset, you don't not have (sufficient) reception for that station.
"Real" RDS-AF should check the alternate frequencies inside the signal. Not do a "does some of the data look like a station I already have in memory".
I am a "restless" listener and listen to multiple stations. I switch when there is talking I don't like, a song I don't like, etcetera. I can't even memorize my five preferred stations in 18 presets.
In the Netherlands we have another deal breaker: FM frequencies are sold every five years and anyone can pay to it. It really means multiple different frequencies, whereas in some countries you only have one frequency for a station through the entire country, like in some countries in Azia.
Click to expand...
Click to collapse
I believe that standard radio receivers have a double tuner to handle the AF: one that keep the station tuned and one that scan all the frequencies to find the better one with same pi-code.
On MTC devices even if it's not perfect, it work correctly, the station is kept while the second tuner scan silently all frequencies until a new one is found.
On the FYT device i can hear changing frequency continuously until a stronger one is set.
I don't know yet if it try to tune the preset ones or try to find some other but anyway it's definitively not working correctly.
I'll dedicate more time to it after the first release of NavRadio app.
Right now on my app work like original app (so it doesn't work).

Related

FM Radio Question

Does it annoy anyone else that it is impossible (as far as I can see) to allocate a meaningful label to the presets on the FM radio application so that all you can do is store them by frequency number?
If I have 10 presets set up it seems so obvious to me that I would actually want to see them as things like "Radio 1", "Radio 4", "Capital", "Virgin", or whatever rather than <xy.z>MHz and have to remember what station is on what frequency/preset.
Are there any third-party FM apps that can talk to the HTC hardware? I know there are lots of apps out there to listen to streaming internet radio but since the tuner is hardware specific I suspect the app that drives the FM tuner is probably HTC-specific and written by HTC. I'd love to be proved wrong or for someone to tell me that I've just not seen the feature to allow me to assign a label or that there's a registry hack or something.
- Julian
I can't help here as I'm still waiting for the O2 version but, I thought this phone supports RDS. Is that not true? And if so, doesn't it automatically name the stations it finds?
Paul
pmeekin said:
I can't help here as I'm still waiting for the O2 version but, I thought this phone supports RDS. Is that not true? And if so, doesn't it automatically name the stations it finds?
Paul
Click to expand...
Click to collapse
It does support RDS, and it works in the UK, but unfortunately the RDS data is only displayed once you've tuned into the station and it doesn't save the info against the preset so there's no way of using the RDS data to decide which preset to select in the first place.
This isn't a huge deal, it just infuriates me because this is such an obvious feature and I just think it's a bad piece of software design.
- Julian

Use HTC Touch Diamond 2 as a remote for a rc car

Hi everyone,
Okay, here is the idea. I have a HTC Touch Diamond 2 and I was thinking that it could be interesting to try to use it as a remote control to pilot a small car or plane (using the Bluetooth frequency).
I found several receivers in the 2.4 GHz frequency band, but I'm not sure whether it could work or not. Here are a few: link 1, link 2, link 3.
So the main questions are:
- Is it possible to program my HTC so that it sends information the receiver will 'understand'?
- Is there by any chance already an app that allows me to do just that (or something close to it that would need minor modifications)?
On top of this, I was also thinking of adding a camera on the car that would send back to my phone what it records. But this more than optional since it probably will make things much more complex... (I found transceivers such as this one and this one, but it looks like a lot of work to install and configure them).
Thank you for your answers and your help in advance!
Anyone to help me?
It won't work, sorry. Not with any store bought RC car. Your only chance is if you engineer the receiver yourself, including the circuitry that translates the radio signals into motor signals.
Thank you for your reply!
Ah, that's quite disappointing
But just to make sure, can you tell me exactly where the problem is? I mean is it a true hardware problem, in relation with the kind of signal that I can transmit with my phone (like a frequency incompatibility or something else)?
I was hoping it was possible to program my HTC to send the appropriate signal corresponding to what the receiver is expecting to get. Why couldn't it work?
Am I at least asking my question on the appropriate section of the forum, or is there another one that I should use rather than this one? Thx again.

Question Mekede /Navifly 7862 CAN code.

Hi.
Can any of you add modified CAN codes to the 7862 radio? I have a Peugeot 308 SW car. Unfortunately, it is not on the car list. I am currently using the setting for the Peugeot 408. But not all functions are working. The steering wheel rotation codes that are used for the moving guide lines for the rear view camera are missing.
depends who is the manufacturer of the decoder, however try XP, or OD or check all, Android Settings > Car settings > Factory settings (password: 126) > Canbus tab > Select the manufacturer of your canbus decoder and the car model, or select the closest match if you cannot find exact model, e.g. volvo xc90 not on list but xc60 available. I hope it make sense.
I'm working on an open source CAN bus box for these sort of situations. The idea is that it fits exactly into the connector for the existing standard CAN bus boxes all these units use (so it will work for PX5/PX6/intel/UIS7862 etc). I've had a similar problem with my Audi A3, where the button functions are incorrect and unchangeable. My car also has an OLED display on the gauge cluster which doesn't show anything useful without the stock head unit (my primary motivation for this project). I'll make a more detailed post about it here once it's working smoothly in my car. For now I'm still working out a few hardware and software kinks, especially since I also need it to control my external DAC and gauge display.
To configure it for your car you will need to know the CAN bus communication rate, as well as the packet ID and bits changed for the following functions:
ACC on
Park
Reverse
Headlight/interior illumination brightness
Optional:
Steering wheel buttons (if you want SWC)
Dashboard display (if you have one - mine operates as 1 line 20 characters in my preferred configuration)
Interesting parameters to monitor (fuel consumption, temperature, instantaneous speed, etc)
I'd also suggest being familiar with modifying Arduino code to change the packet values as I won't modify it for anything other than my Audi A3 8P. The way this data is coded can vary quite a lot car to car - for example in mine the brightness is coded as an integer from 0-100. You'll also need a way to solder the parts.
JLCPCB is insanely cheap for ordering boards if you're a new customer, and the rest of the components cost ~$30. I may build and sell some of my extra boards if there's interest, but I won't be providing any software besides for my Audi A3 8P. I'll update within the month, as I don't anticipate needing to change anything this point besides software, but only have 1 day a week to dedicate time to this project so progress has been slow.
Daro101 said:
Salut.
Poate cineva dintre voi adăuga coduri CAN modificate la radio 7862? Am o mașină Peugeot 308 SW. Din păcate, nu este pe lista de mașini. În prezent folosesc setarea pentru Peugeot 408. Dar nu toate funcțiile funcționează. Codurile de rotație ale volanului utilizate pentru liniile de ghidare mobile ale camerei de vizualizare din spate lipsesc.
Click to expand...
Click to collapse
Hi try these:
8888
6789
7890
3368
3369
1617
1618
1688
and the list can continue to check on these and let you know if it was helpful
Salut incearcale pe astea:
8888
6789
7890
3368
3369
1617
1618
1688
si lista poate continua verificale pe astea si anuntama daca ti fost de ajutor
COASTER19 said:
I'm working on an open source CAN bus box for these sort of situations. The idea is that it fits exactly into the connector for the existing standard CAN bus boxes all these units use (so it will work for PX5/PX6/intel/UIS7862 etc). I've had a similar problem with my Audi A3, where the button functions are incorrect and unchangeable. My car also has an OLED display on the gauge cluster which doesn't show anything useful without the stock head unit (my primary motivation for this project). I'll make a more detailed post about it here once it's working smoothly in my car. For now I'm still working out a few hardware and software kinks, especially since I also need it to control my external DAC and gauge display.
To configure it for your car you will need to know the CAN bus communication rate, as well as the packet ID and bits changed for the following functions:
ACC on
Park
Reverse
Headlight/interior illumination brightness
Optional:
Steering wheel buttons (if you want SWC)
Dashboard display (if you have one - mine operates as 1 line 20 characters in my preferred configuration)
Interesting parameters to monitor (fuel consumption, temperature, instantaneous speed, etc)
I'd also suggest being familiar with modifying Arduino code to change the packet values as I won't modify it for anything other than my Audi A3 8P. The way this data is coded can vary quite a lot car to car - for example in mine the brightness is coded as an integer from 0-100. You'll also need a way to solder the parts.
JLCPCB is insanely cheap for ordering boards if you're a new customer, and the rest of the components cost ~$30. I may build and sell some of my extra boards if there's interest, but I won't be providing any software besides for my Audi A3 8P. I'll update within the month, as I don't anticipate needing to change anything this point besides software, but only have 1 day a week to dedicate time to this project so progress has been slow.
Click to expand...
Click to collapse
Hi @COASTER19 .
Thanks for posting about this, always good to hear about real development work.
I for one would be very interested to read more about your project, would you consider posting more information.
Also, there is another thread discussing similar work you may not be aware of, so have posted here.
CANBOX , CAN decoder reverse engineering
Hi All, I have a PX5 radio that was supplied with fittings for 2006 Toyota RAV4 , sadly it didnt come with a CANBOX and supplier was not able to provide one that matched, I managed to get my hands on a Canbox for VW unit and decided to reverse...
forum.xda-developers.com
hi all, i am new here and thinking to buy navifly HU
I have one question, dose the unit support climate control for AC? can I control my AC from unit?
The other question, can i add 360 cameras system?
Thansk
amin111111111 said:
hi all, i am new here and thinking to buy navifly HU
I have one question, dose the unit support climate control for AC? can I control my AC from unit?
The other question, can i add 360 cameras system?
Thansk
Click to expand...
Click to collapse
It depends on whether your car exposes CAN-bus to the head unit and whether the provided CAN-bus box supports it. Generally, the answer is no unless specifically mentioned in the listing text. Navifly support doesn't speak good English, so I wouldn't expect a correct answer from them.
@marchnz I posted an early demo of the project on Youtube and have attached the latest schematic to this post.
I'll start a thread in a few more weeks once I get the optical audio working, but the current board layout probably needs another revision before then. I had to use a rotary tool to cut part of the board so the connector could physically fit. CANBOX looks interesting, but also works very differently from what I'm doing. I'll look into it more once I have a fully functional stereo again, as I'm definitely interested in trying to get some of those functions running.
COASTER19 said:
It depends on whether your car exposes CAN-bus to the head unit and whether the provided CAN-bus box supports it. Generally, the answer is no unless specifically mentioned in the listing text. Navifly support doesn't speak good English, so I wouldn't expect a correct answer from them.
@marchnz I posted an early demo of the project on Youtube and have attached the latest schematic to this post.
I'll start a thread in a few more weeks once I get the optical audio working, but the current board layout probably needs another revision before then. I had to use a rotary tool to cut part of the board so the connector could physically fit. CANBOX looks interesting, but also works very differently from what I'm doing. I'll look into it more once I have a fully functional stereo again, as I'm definitely interested in trying to get some of those functions running.
Click to expand...
Click to collapse
Fantasic work, really like the approach to steering wheel keys.
What is selected for CANBus type on the unit to enable the split between analog steering wheel, Illumination, ACC and vehicle specific CANBus signaling say from car doors, AC etc?
I am very interested in making one and having a go at modifying the software for Toyota specific vehicles, if you're comfortable with releasing and commenting the source? Understand if you're not though
Great video. Thanks again for contributing to real development. Your work deserves its own thread!
Illumination, ACC state, Park state, and Reverse are just +12v signals onto wires. Normally, everything else happens over the serial communication, but in my case I use KEY1/KEY2 with selectable resistors for SWC.
Vehicle specific stuff such as reverse radar sensors, climate control, and door status would require reverse engineering the head unit's 2 wire serial protocol. Luckily it does appear at first glance that the protocol is the primary focus of the CANBOX project.
If there's a way to select an app to open over that serial connection it would be really convenient, but I don't think that's an option discovered yet. It would allow the mode carousel to be controlled entirely from the microcontroller which would be great. I loved how HAL9k's ROM on my PX6 allowed me to customize this, but my PX6 ran incredibly slow for some reason (20+ seconds to open maps). The 7862 is far nicer hardware despite the unpolished software, so the preferable option to me. Optical audio output is also great compared to the noise in both the PX6 and 7862 amps.
Ok. Couldn't find problem like mine. After starting car my dashboard HUD is in Chinese. Can't find anything like original radio settings to change it. Any ideas?
KDPD said:
Ok. Couldn't find problem like mine. After starting car my dashboard HUD is in Chinese. Can't find anything like original radio settings to change it. Any ideas?
Click to expand...
Click to collapse
Use phone and Google translate to get to language menu?
marchnz said:
Use phone and Google translate to get to language menu?
Click to expand...
Click to collapse
Will use opcom to do that as navifly 7867 doesn't have setting for that inbuilt. Lots of cd400 radio settings are gone. Thanks.
KDPD said:
Will use opcom to do that as navifly 7867 doesn't have setting for that inbuilt. Lots of cd400 radio settings are gone. Thanks.
Click to expand...
Click to collapse
I dont know what that has to do with using translate on your phone to find the language menu on your head unit, but if that spins your wheels.
marchnz said:
I dont know what that has to do with using translate on your phone to find the language menu on your head unit, but if that spins your wheels.
Click to expand...
Click to collapse
That means I can't change settings from head unit as that setting doesn't exist. It's not head unit language I'm talking about, it's dashboard display.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So using Google translate is impossible, hence I mentioned that opcom is needed.
With the Google translate app on a phone, you can use your camera to point to the text and translate it.
Perhaps you can use that to navigate to your dashboard settings to change the language?
Don't know if such a setting exists, though...try it and let us know.
Edit:
So, if with your previous head unit, that's where the language settings were found and not directly through another method, then the head unit that replaced the factory head unit should provide those functions.
For the TEyes CC2 and CC3, once the proper Canbus setting is specified, I believe there is a Car Info app or something similar, that provides access to vehicle specific functions/settings. For the CC2, which I have, there are additional menus that are available in the normal settings when you specify a Canbus adapter. Have a look around your settings to see if you can find anything like this.
Question...did this just start happening or is this the first time with the head unit and the Chinese text in the dashboard is showing up?
Question...have the head unit language settings been set to the proper language?
mastrv said:
With the Google translate app on a phone, you can use your camera to point to the text and translate it.
Perhaps you can use that to navigate to your dashboard settings to change the language?
Don't know if such a setting exists, though...try it and let us know.
Edit:
So, if with your previous head unit, that's where the language settings were found and not directly through another method, then the head unit that replaced the factory head unit should provide those functions.
For the TEyes CC2 and CC3, once the proper Canbus setting is specified, I believe there is a Car Info app or something similar, that provides access to vehicle specific functions/settings. For the CC2, which I have, there are additional menus that are available in the normal settings when you specify a Canbus adapter. Have a look around your settings to see if you can find anything like this.
Question...did this just start happening or is this the first time with the head unit and the Chinese text in the dashboard is showing up?
Question...have the head unit language settings been set to the proper language?
Click to expand...
Click to collapse
Issue is. Supplier sells unit with CANBUS for generic GM as Chevrolet to European cars such as Opel Astra. Settings for canbus is GM/Cruze/cruze_manual, and kinda covers most of ECUs. In settings under 3368, settings for language don't exist. It covers basic personalisations, lights and doors, not nothing like that. At the moment decoder is by HiWorld. I got GM compatible one from Rise but don't know how to force unit to recognise it. When I connected it in canbus settings i couldn't na choose Rise. So I got an OBD OPcom/vauxcom and will change language trough that. But thanks for the tip with translate. I know that display by memory, it's just annoying to see avarage consumption as bunch of lines putted together.
KDPD said:
Problem jest. Dostawca sprzedaje jednostkę z CANBUS dla generycznego GM jako Chevrolet do europejskich samochodów, takich jak Opel Astra. Ustawienia dla canbus to GM/Cruze/cruze_manual i w pewnym sensie obejmują większość ECU. W ustawieniach poniżej 3368 ustawienia języka nie istnieją. Obejmuje podstawowe personalizacje, oświetlenie i drzwi, a nie nic takiego. W tej chwili dekoder firmy HiWorld. Dostałem kompatybilny z GM od Rise, ale nie wiem, jak zmusić jednostkę do rozpoznania go. Kiedy podłączyłem go w ustawieniach canbus, nie mogłem wybrać Rise. Więc mam OBD OPcom/vauxcom i przez to zmienię język. Ale dzięki za wskazówkę z tłumaczeniem. Znam to wyświetlanie z pamięci, po prostu denerwujące jest widzieć średnie zużycie jako kilka połączonych linii.
Click to expand...
Click to collapse
Your problem is very simple to solve. Just go to the "Vehicle Settings" tab and there is an option to change the language. I will try to send the photo as soon as possible.
Tomaso84 said:
Your problem is very simple to solve. Just go to the "Vehicle Settings" tab and there is an option to change the language. I will try to send the photo as soon as possible.
Click to expand...
Click to collapse
Well, there is no setting for an language for dashboard of the car. only for the language of the HUD. but thanks. im trying to get update from manufacturer.
At first, my car spoke Chinese too. Managed to change on the menu
Tomaso84 said:
At first, my car spoke Chinese too. Managed to change on the menu
Click to expand...
Click to collapse
Well.... It's not that easy on my unit. Or maybe decoder is wrong. Basically no language setting. And most of settings are empty screens. Canbus is set as a Chevrolet Cruze. I have a second "Opel" canbus unit but not sure how to connect it. Does it require reset if the HUD or is it plug and play?

Software Development [Dev] New "NavRadio+" ported to UIS7862 and sc9853i FYT devices.

Hi all,
I finally ported my NavRadio+ app to FYT based devices with CPU UIS7862, sc9853i and sc9863a!!
It surely don't work on Sofia and older FYT devices.
I own an Isudar V72 unit with CPU UIS7862 with MCU NOR FYT=1 but it's been confirmed to work on other FYT types too (31, 51 etc..)
A FREE VERSION FOR XDA USERS IS AVAILABLE TO ACCOMPLISH THE XDA RULES AND TO LET USERS TEST THE COMPATIBILITY BEFORE BUYING IT.
GET IT HERE:
V2.80 DROPBOX LINK
or
V2.80 GDRIVE LINK
IT DIFFER FROM PAYED VERSION JUST IN TERMS OF USER CUSTOMIZATIONS OPTIONS AND NO LOGOS SUPPORT.
If you are sure that your unit is compatible with the app you can get it on the Google PlayStore, here:
https://play.google.com/store/apps/details?id=com.navimods.radio
or on the Huawei Appgallery at this link:
https://appgallery.huawei.com/app/C107643913
Here you can see a sample video of my working progresses:
Sample Video
Here a demonstration video of the automatic assignment of Logos, station name and alternative frequencies:
Demo
It's widely customizable in the graphics and layouts:
- Wallpapers: Presets (about 30), system wallpaper, solid color, from personal images
- Color themes (20 predefined or personal adjustments)
- Night mode on / off, timed or automatic with car lights (MTC only)
- Resizable text elements and Font choice
- 3 view modes:
Vertical List (Left/Right and5,6 or 6 buttons)
Horizontal Grid (1x5, 2x3, 2x4, 2x5, 3x3, 3x4, 3x5)
Fullscreen (double tap or timed)
- Selectable inactivity timer for fullscreen activation
- Toggable StatusBar in fullscreen mode
- Toggable Clock and GPS speed in fullscreen
- Toggable Frequency slider
- Automatic and manual assignement of Logo images to the stored radio stations based on RDS id and station name scraping.
- Logos can be downloaded from internet DIRECTLY IN THE APP or sideloaded.
- Station lists can be sorted by name or frequency and saved/restored in a Json format
- Improved RDS AF function with automatic storing and merging of alternative frequencies found
- Notifications Toasts
- Selectable Radio Region
- Station editable elements : Position, Frequency, Name, Logo, Favorites
- 2 Homepage Widgets, horizontal and vertical design
- Floating widget
- Autostart on boot option
- Support 800x480, 1024x600, 1280x720 and 1920x1080 display resolutions
- Resizable Texts elements
- App full settings backup/restore function
List of available Logos by nationality, in Bold the ones with automatic Logos assignement functionality (by RDS id):
EUROPE: Albania, Andorra, Austria, Australia, Belgium, Bulgaria, Bosnia and Herzegovina, Belarus, Cyprus,Croatia, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Germany, Gibraltar, Greece, Hungary, Ireland, Iceland, Italy, Lithuania, Latvia, Liechtenstein, Luxembourg, Macedonia, Malta, Monaco, Moldova, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Russia, Serbia, Slovakia, Slovenia, Sweden, Switzerland, South Korea, Spain, Turkey, Taiwan, Ukraine, United Kingdom
SOUTH AMERICA: Argentina, Brazil, Chile, Colombia, Mexico, Perù
USA: Alabama, Alaska, Arizona, Arkansas, California, Canada, Colorado, Connecticut, Delaware, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachussets, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Virgin Island, Washington, Washington DC, West Virginia, Winsconsin, Wyoming
CHINA, JAPAN, MALAYSIA, PHILIPPINE
MOROCCO, TUNISIA
AUSTRALIA, NEW ZAELAND
Some pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME TIPS AND GUIDES
- REMOVE ORIGINAL RADIO APP -​There are some issues due to original radio app coexistance. To avoid these issues the best option is to remove the original radio app from the system using the FYT_Radio_REMOVER/RESTORER tool availabe here:
DROPBOX: FYT RADIO REMOVER/RESTORER
or here:
GDRIVE: FYT RADIO REMOVER/RESTORER​
Extract the zip file on the root of a FAT32 USB disk so you have:
a folder "BACKUP_RADIO_APK"
a folder "lsec_updatesh"
a file "lsec6315update"
a file "lsec6316update"
a file "lsec6521update"
With unit powered up and android running, insert the USB and when prompted press "START".
This will reboot the unit and run some shell commands to rename the original radio app from "******_com.syu.radio.apk" into "*******_com.syu.radio.bak" so it will not be found by android.
You will see some linux commands scrolling and at the end you'll see a green text "update success!Pls remove device". Do it and the unit will reboot to android with radio disabled.
The script will also make copy of the original radio app on the USB in the folder "BACKUP_RADIO_APK" in case you need it in the future.
TO RESTORE THE ORIGINAL APP​Simply insert again the USB with same files in it and let the process run again.
Essentially everytime the USB stick is inserted, it remove the original app renaming it with .bak extension or if the .bak file exist it restore it back with .apk extension.
You can use it as many times you want.
-----------------------------------------------------------------------​
TOGGLE SCREEN NORMAL/FULL:
- Double Click on the station information toggle fullscreen on/off.
NORMAL SCREEN:
- Long press on the station information popup the "ADD Station" dialog window if the station is not in your station list. If it's already in your list, it will focus the relative station button.
- Long press on a station button bring up the "EDIT Station" dialog window
- Single press on screen arrows <> does a small frequency step fwd/back
- Long Press on screen arrows does a quick search fwd/back
FULLSCREEN MODE:
- A Single press of the arrows <> switch to next/previous station
-A Long press on station information(center of the screen) bring up the "EDIT Station" dialog window.
- In interface settings you can remove the big frequency in background if a logo is available.
- In settings you can hide status bar, activate the clock and a speed gauge
STEERING WHEELS CONTROLS:
- The steering wheels commands act exactly in the same way as the fullscreen arrows, they just need to be setup in the correct way in carsettings application.
FAVORITE LIST:
- The FAV list is the result of merging FM and AM favorites, so you can have both frequencies in the same list.
- FAV stations can be edited within the fav list but cannot be added. You need to be on fm or am list to add a station and set it to favs.
- Deleting the FAV list will just remove the fav flag from the fm/am stations but will not delete them.
- Deleting AM/FM list it will delete the FAV list too.
LOGOS:
- you can use your own station logos, you just need to know where you have them stored and browse for them when editing a station.
- To get the stations Logos from the app you have to set the nationality of the logos in the interface menu, download and extract them.
Once they are extracted you have to edit each saved station to assign the logo image to it.
- The automatic assignment of the Logos is based on the RDS id of the radio stations (pi code) and the search of the logo by RDS name.
The first method (by id) is faster and more precise but it needs that the name of the logo contain the picode of the station and for this purpose i renamed them for some of the available countries. Of course i cannot make them all and the functionality of this method depend of the availability of correctly named logo images for your country.
The second method (by name) is less accurate and it work comparing the RDS name with all available logos. If the rsult of the comparison is 100% correct the logo is autoamatically assigned. If the result are more then one logo, a dialog window popup asking you to choose it.
For USA and Canada the assignment of the logo is is done by searching the frequency of the station in the logo file name.
AF (Alternative Frequencies) handling: (Doubleclick to switch between stored AF)
AF service allows the radio tuner to tune in to an alternative frequency when the signal becomes too weak. The minimum level signal can be set in factory settings (Auto Search Stop) and has been found
that around 30 db is the best choice.
To improve even more this service I added an automatic storing of the alternative frequencies so that every time a new frequency is received, it's added in a list.
After an autoscan some radio stations can be found on different frequencies, NavRadio+ have an option (in Settings/radio) to automatically merge the frequencies in just one button populating the AF list
The frequencies available in this list can be selected using the station editor or switched one by one DOUBLECLICKING on the station button.
NOTES:
I'm the only developer of the app and I work on it every single day for some hours a day.
I try my best to develope the app at best of my possibilities and I wish at evey release that it is bug and crash free.
This is very hard to achieve, even if I have some very good friends that help me testing it.
I'm really thankful to them for their help and support.
Thank everybody who beleive in my work and thanks for understanding.
EDIT: Updated FYTRadio remover/restorer with new lsec6315update file
Great news. Thanks for your work! Will check this out and drop my feedback
On FYT 31 works well, but steering wheel control doesn't work.
stediste said:
On FYT 31 works well, but steering wheel control doesn't work.
Click to expand...
Click to collapse
SWC will work on next release.
I already found the fix for it.
I have a question for all FYT users:
While using a navigation app like maps, does the sound from the radio mix with Navigation announcements?
It mix sound when using the audio player but it doesn't do that on my unit with the original radio app.
Is this normal for fyt units??
I just installed this and tried it a bit and it works on my Atoto S8!!! This is so much better than the default radio station. Thank you so much!
It doesn't seem to have that function of combining all frequencies of the same station into one button though, but I guess that's because this is the free version? That's the big problem with the FYT-based radio apps. The way they do AF is terrible.
The steering wheel controls, and widget next and back buttons of the Agama Car Launcher aren't working but this is awesome! Can't wait for the update to the full version and I'll purchase it when it's released. Amazing!
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
This works. Autscan and seek stations. Is there anything else you wish me to test?
- if RDS informations are displayed
Yes!!
- if sound output work (you can hear sound)
Definitely. It was working great.
- if audio focus and mixing work correctly
I still didn't try this but I'll turn on navigation and drive to the supermarket in the next couple of hours so I'll try it.
Gaugamela said:
I just installed this and tried it a bit and it works on my Atoto S8!!! This is so much better than the default radio station. Thank you so much!
It doesn't seem to have that function of combining all frequencies of the same station into one button though, but I guess that's because this is the free version? That's the big problem with the FYT-based radio apps. The way they do AF is terrible.
The steering wheel controls, and widget next and back buttons of the Agama Car Launcher aren't working but this is awesome! Can't wait for the update to the full version and I'll purchase it when it's released. Amazing!
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
This works. Autscan and seek stations. Is there anything else you wish me to test?
- if RDS informations are displayed
Yes!!
- if sound output work (you can hear sound)
Definitely. It was working great.
- if audio focus and mixing work correctly
I still didn't try this but I'll turn on navigation and drive to the supermarket in the next couple of hours so I'll try it.
Click to expand...
Click to collapse
The arrows of the Agama widget has never worked on other models either.
Steering wheels controls should be working now on new version 2.16 (i updated the link in first post) download it again please.
Merge of frequencies can be done only if the unit receive the station id from RDS. right now only MTC units can do it, FYT ones need some tricks and headache:I'll see what i can do...
AF on FYT is definetively wrong handled and i don't know if i can fix it...
KoTiX2 said:
I have a question for all FYT users:
While using a navigation app like maps, does the sound from the radio mix with Navigation announcements?
It mix sound when using the audio player but it doesn't do that on my unit with the original radio app.
Is this normal for fyt units??
Click to expand...
Click to collapse
So, the original radio app in my Atoto S8 decreases sound when indications are given in Waze. Navradio works the same. The web radio app I use decreases the sound more drastically than Navradio and the stock radio app.
2.16 managed to make the steering wheel controls work! Very impressive.
I'll wait and see what you can do about radio merging and AF. What you've done is already very impressive. Thank you.
Any other test you need me to do?
Gaugamela said:
So, the original radio app in my Atoto S8 decreases sound when indications are given in Waze. Navradio works the same. The web radio app I use decreases the sound more drastically than Navradio and the stock radio app.
2.16 managed to make the steering wheel controls work! Very impressive.
I'll wait and see what you can do about radio merging and AF. What you've done is already very impressive. Thank you.
Any other test you need me to do?
Click to expand...
Click to collapse
What about bluetooth audio switching between calls and radio?
*delete*
KoTiX2 said:
What about bluetooth audio switching between calls and radio?
Click to expand...
Click to collapse
Test:
1 - Opened Navradio Free and was playing a radio station,
2 - Opened Bluetooth One (the phone app) and called someone,
Result: as expected, same behaviour as every other app. Sound from the call took over and nothing was playing on the background. When the call ended, Navradio resumed trouble-free.
A couple issues that I detected:
Issue 1:
1 - Was playing Navradio when I switched off the car.
2 - When I turned on the car, Navradio did not resume.
3 - Instead, the default Radio app started by itself on the radio station last played by Navradio.
4 - I had to start Navradio by myself.
5 - Expected to have Navradio open instead of the Radio app. Or at least to have Navradio to restart as well. Toggled option to have Navradio starting on initialization. Made no difference.
Issue 2:
1 - When Navradio is open, Radio is open in the background.
2 - If I kill Radio in the task manager, Navradio stops playing and does not restart untill I kill it and restart again.
Hope you manage to do something about AF and station merging. I'll keep my fingers crossed.
Gaugamela said:
Test:
1 - Opened Navradio Free and was playing a radio station,
2 - Opened Bluetooth One (the phone app) and called someone,
Result: as expected, same behaviour as every other app. Sound from the call took over and nothing was playing on the background. When the call ended, Navradio resumed trouble-free.
A couple issues that I detected:
Issue 1:
1 - Was playing Navradio when I switched off the car.
2 - When I turned on the car, Navradio did not resume.
3 - Instead, the default Radio app started by itself on the radio station last played by Navradio.
4 - I had to start Navradio by myself.
5 - Expected to have Navradio open instead of the Radio app. Or at least to have Navradio to restart as well. Toggled option to have Navradio starting on initialization. Made no difference.
Issue 2:
1 - When Navradio is open, Radio is open in the background.
2 - If I kill Radio in the task manager, Navradio stops playing and does not restart untill I kill it and restart again.
Click to expand...
Click to collapse
It's good that Bluetooth is ok, thx for testing it
The problems with original app cannot be solved by a third party app like NavRadio because some things are hardcoded in the syu.ms server.
To avoid this we will probably need to modify the server or to disable/remove the original app but we have time tothink about it and maybe find other ways.
For now it's better to never start the original app and close it with back button before running NavRadio.
Tomorrow I'll upload the full version of the app on PlayStore for those who'd like to purchase it and enjoy all the extra features.
The free version is already available on the store with version 2.16.
Interesting. I guess that making a modified firmware with Navradio installed as the default app might work. Otherwise I'm not sure how to bypass that. @surfer63 is the resident expert on FYT headunits. I think he might have a good idea on how to proceed further.
I tried disabling the stock radio appp, but that option is greyed out so I don't think it can be disabled.
I'll definitely get the full version tomorrow then.
Gaugamela said:
Interesting. I guess that making a modified firmware with Navradio installed as the default app might work. Otherwise I'm not sure how to bypass that. @surfer63 is the resident expert on FYT headunits. I think he might have a good idea on how to proceed further.
I tried disabling the stock radio appp, but that option is greyed out so I don't think it can be disabled.
I'll definitely get the full version tomorrow then.
Click to expand...
Click to collapse
Situation so far:
You can't disable the standard radio app and you certainly should not remove the standard radio app (with an lsec script or modified firmware).
If the unit gets a real cold boot, the FM-chip and Amplifier start before Android and that's why you always hear the radio on a real cold boot.
Removing the radio app makes it impossible to stop the radio (believe me. I've been there when removing the useless radio with a script after switching to DAB )
Also: the radio/FM-chip is actually not switched off, but the radio audio channel is muted.
The new NavRadio+:
If the new NavRadio+ can switch on/off the radio output, it could replace the standard radio. Note though that in that case you would use the free version and would still need to purchase the full version.
But that is just one step: The difficult part would be that some of the activities in the com.syu.ms should be rewritten to launch the app in case of cold boot (if only to switch it off) and when using (hardware) keys, although my FytHWOneKey app could help in the second case as well. The diffcult part is replacing the package name com.syu.music as it should be replaced by "com.navimods.radio" for the full version and by "com.navimods.radio_free" for the free version, requiring two different com.syu.ms mods. Also my FytHWOneKey can't take that over as it is really a call for the package name, which can't be double and which can't be "activity aliased".
As my FytHWOneKey is open source under GNU GPL3, that specific "activiity alias" radio part could be incorporated in both the free and full version.
surfer63 said:
Situation so far:
You can't disable the standard radio app and you certainly should not remove the standard radio app (with an lsec script or modified firmware).
If the unit gets a real cold boot, the FM-chip and Amplifier start before Android and that's why you always hear the radio on a real cold boot.
Removing the radio app makes it impossible to stop the radio (believe me. I've been there when removing the useless radio with a script after switching to DAB )
Also: the radio/FM-chip is actually not switched off, but the radio audio channel is muted.
The new NavRadio+:
If the new NavRadio+ can switch on/off the radio output, it could replace the standard radio. Note though that in that case you would use the free version and would still need to purchase the full version.
But that is just one step: The difficult part would be that some of the activities in the com.syu.ms should be rewritten to launch the app in case of cold boot (if only to switch it off) and when using (hardware) keys, although my FytHWOneKey app could help in the second case as well. The diffcult part is replacing the package name com.syu.music as it should be replaced by "com.navimods.radio" for the full version and by "com.navimods.radio_free" for the free version, requiring two different com.syu.ms mods. Also my FytHWOneKey can't take that over as it is really a call for the package name, which can't be double and which can't be "activity aliased".
As my FytHWOneKey is open source under GNU GPL3, that specific "activiity alias" radio part could be incorporated in both the free and full version.
Click to expand...
Click to collapse
NavRadio+ can switch on/off the radio output as it use the same commands of the original app.
I'll try tomorrow to remove the original app and see what happen on cold boot, maybe something has changed in these new units...
I'm pretty sure that at some point i was able to start NavRadio in place of original app at cold boot but i can't remember now how i did it and if there were other issues involved.
@surfer63 please note that now we are on Android10 where system partition cannot be mounted and you cannot make any changes even with Superuser. You need a magisk modules to make changes there i guess...
We can always use the lsec script method to modify what we need.
KoTiX2 said:
NavRadio+ can switch on/off the radio output as it use the same commands of the original app.
I'll try tomorrow to remove the original app and see what happen on cold boot, maybe something has changed in these new units...
I'm pretty sure that at some point i was able to start NavRadio in place of original app at cold boot but i can't remember now how i did it and if there were other issues involved.
@surfer63 please note that now we are on Android10 where system partition cannot be mounted and you cannot make any changes even with Superuser. You need a magisk modules to make changes there i guess...
We can always use the lsec script method to modify what we need.
Click to expand...
Click to collapse
Note that both the radio app and the com.syu.ms are in the oem partition, not in the system partition. That oem partition is also accessible on these Android 10 units. You do not have to "touch" the system partition. And yes: it requites the 7862lsec.sh script (or 8581lsec.sh script on the 9863a units, where the apps are identical).
Speaking of this: You should edit the title of this thread to "New "NavRadio+" ported to FYT uis7862 (ums512) and FYT sc9863a (uis8581a) devices".
System partitions (6315_1.zip versus 6316_1.zip) are different. The AllAppUpdate.bin is identical. You could create a "universal" installer using the lsec6315update with the 7862lsec.sh for the uis7862 units, and the lsec6316update and 8581lsec.sh for the uis8581a units.
surfer63 said:
Note that both the radio app and the com.syu.ms are in the oem partition, not in the system partition. That oem partition is also accessible on these Android 10 units. You do not have to "touch" the system partition. And yes: it requites the 7862lsec.sh script (or 8581lsec.sh script on the 9863a units, where the apps are identical).
Speaking of this: You should edit the title of this thread to "New "NavRadio+" ported to FYT uis7862 (ums512) and FYT sc9863a (uis8581a) devices".
System partitions (6315_1.zip versus 6316_1.zip) are different. The AllAppUpdate.bin is identical. You could create a "universal" installer using the lsec6315update with the 7862lsec.sh for the uis7862 units, and the lsec6316update and 8581lsec.sh for the uis8581a units.
Click to expand...
Click to collapse
/oem is a symlink of /system/oem
So mount properties behaves the same.
I got access with Superuser from my app only with the original firmware that came with the unit.
After upgrading the firmware to a slightly newer version was not possible to mount OEM or system
KoTiX2 said:
/oem is a symlink of /system/oem
So mount properties behaves the same.
I got access with Superuser from my app only with the original firmware that came with the unit.
After upgrading the firmware to a slightly newer version was not possible to mount OEM or system
Click to expand...
Click to collapse
They now use dynamic partitions.
product, vendor, system, etcetera are now all part of the superpartition unisoc.
But as far as I know /oem is still not a symlink from /system.
But I guess I have to wait till I have my own unit.
Do you still have that slightly older firmware where it was still possible? I really would like the 6315_1.zip from that one to investigate how to go back from dynamic partitions to the "old fashioned" partitions. I like to see it before I try without "proof from the past"
KoTiX2 said:
Hi all,
I finally ported my NavRadio+ app to FYT based devices with CPU UIS7862!!
It surely don't work on Sofia and older FYT devices and probably it won't work on all others.
I own an Isudar V72 unit with CPU UIS7862 with MCU NOR FYT=1 so at this stage i know it work on my unit, other users will confirm the compatiibility with other models.
I still need to work on some parts like steering wheel controls, launchers integrations etc.. but I also need to know if this free version work for all people with a compatible model.
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
- if RDS informations are displayed
- if sound output work (you can hear sound)
- if audio focus and mixing work correctly
Right now i can publish only the free version here:
DOWNLOAD NAVRADIO FREE v2.16
IT DIFFER FROM PAYED VERSION JUST IN TERMS OF USER CUSTOMIZATIONS OPTIONS AND NO LOGOS SUPPORT.
When i'm sure that this version work ok i will publish on playstore the full version.
RIGHT NOW THE NAVRADIO APPS ON PLAYSTORE DOESN'T SUPPORT FYT UNITS.
You can use only the version from this thread.
PLEASE REPORT BACK ANY ISSUE.
Thanks
Here you can see a sample video of my working progresses:
Sample Video
Here a demonstration video of the automatic assignment of Logos, station name and alternative frequencies:
Demo
It's widely customizable in the graphics and layouts:
- Wallpapers: Presets (about 30), system wallpaper, solid color, from personal images
- Color themes (20 predefined or personal adjustments)
- Night mode on / off, timed or automatic with car lights (MTC only)
- Resizable text elements and Font choice
- 3 view modes:
Vertical List (Left/Right and5,6 or 6 buttons)
Horizontal Grid (1x5, 2x3, 2x4, 2x5, 3x3, 3x4, 3x5)
Fullscreen (double tap or timed)
- Selectable inactivity timer for fullscreen activation
- Toggable StatusBar in fullscreen mode
- Toggable Clock and GPS speed in fullscreen
- Toggable Frequency slider
- Automatic and manual assignement of Logo images to the stored radio stations based on RDS id and station name scraping.
- Logos can be downloaded from internet DIRECTLY IN THE APP or sideloaded.
- Station lists can be sorted by name or frequency and saved/restored in a Json format
- Improved RDS AF function with automatic storing and merging of alternative frequencies found
- Notifications Toasts
- Selectable Radio Region
- Station editable elements : Position, Frequency, Name, Logo, Favorites
- 2 Homepage Widgets, horizontal and vertical design
- Floating widget
- Autostart on boot option
- Support 800x480, 1024x600, 1280x720 and 1920x1080 display resolutions
- Resizable Texts elements
- App full settings backup/restore function
List of available Logos by nationality, in Bold the ones with automatic Logos assignement functionality (by RDS id):
EURÓPA: Albánia, Andorra, Ausztria , Ausztrália, Belgium , Bulgária, Bosznia-Hercegovina, Fehéroroszország, Ciprus, Horvátország , Cseh Köztársaság , Dánia, Észtország, Feröer-szigetek, Finnország , Franciaország , Németország, Gibraltár, Görögország, Magyarország , Írország , Izland, Olaszország , Litvánia , Lettország, Liechtenstein, Luxemburg, Macedónia, Málta, Monaco, Moldova, Montenegró, Hollandia, Norvégia, Lengyelország , Portugália , Románia , Oroszország, Szerbia, Szlovákia, Szlovénia, Svédország, Svájc, Dél-Korea, Spanyolország, Törökország, Tajvan, Ukrajna, Egyesült Királyság
DÉL-AMERIKA: Argentína, Brazília, Chile, Kolumbia, Mexikó, Perù
USA: Alabama, Alaszka, Arizona, Arkansas, California, Kanada, Colorado, Connecticut, Delaware, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachussets, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, Észak-Karolina, Észak-Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, Rhode Island, Dél-Karolina, Dél-Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Virgin-sziget, Washington, Washington DC, Nyugat-Virginia, Winsconsin, Wyoming
KÍNA, JAPÁN, MALAJZIA, FÜLÖP-szigetek
MAROKKÓ, TUNÉZIA
AUSZTRÁLIA, ÚJ-ZÉLAND
Néhány kép:
Click to expand...
Click to collapse
rem

Question Any tips on how to access pins via the MCU within an Android app?

Title says it all. I want to build an app that can read and write the pins that the MCU has access to, for example steering wheel, antenna power, etc.
Anyone know how the stock apks do that?
Is the unit an FYT, post Android system information including MCU version
cryptyk said:
Title says it all. I want to build an app that can read and write the pins that the MCU has access to, for example steering wheel, antenna power, etc.
Anyone know how the stock apks do that?
Click to expand...
Click to collapse
@marchnz is completely right: What type of unit are we talking about?
Your request is like: "I have a car. Which wires do I have to connect to a radio I bought".
If it is a FYT unit, you need to decompile the 190000000_com.syu.canbus.apk. That one contains per CANbus decoder the necessary commands.
This is a teyes cc3.
I was expecting that ST (the SOC manufacturer) or FYT used the standard Android library for connecting to the GPIO pins, or provided a library of their own. I didn't suspect that each brand would create their own unique hardware library for something as fundamental as GPIO access.
I tried the standard Android libraries and GetGpioList() doesn't return the pins.
Was hoping someone else had already gone through the effort to decompile this part and see how it works. All good if not; I can definitely do it.
@surfer63 thanks for the lead, but the canbus implementation is done with 3 dedicated bxCAN networks on the SOC which are separate from the GPIO controller.
Thanks for the notes all. I'll just start digging in and let y'all know what I find.
cryptyk said:
This is a teyes cc3.
I was expecting that ST (the SOC manufacturer) or FYT used the standard Android library for connecting to the GPIO pins, or provided a library of their own. I didn't suspect that each brand would create their own unique hardware library for something as fundamental as GPIO access.
I tried the standard Android libraries and GetGpioList() doesn't return the pins.
Was hoping someone else had already gone through the effort to decompile this part and see how it works. All good if not; I can definitely do it.
@surfer63 thanks for the lead, but the canbus implementation is done with 3 dedicated bxCAN networks on the SOC which are separate from the GPIO controller.
Thanks for the notes all. I'll just start digging in and let y'all know what I find.
Click to expand...
Click to collapse
Try this repo: https://github.com/lbdroid/MCUd/
By now very old but it might still contain some useful info.
surfer63 said:
Try this repo: https://github.com/lbdroid/MCUd/
By now very old but it might still contain some useful info.
Click to expand...
Click to collapse
Very very nice! This is a huge headstart. Thank you!

Categories

Resources