yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
Ooops.. sorry, my mistake -- permissions set correctly now

Video

---------- Post added at 08:08 ---------- Previous post was at 08:01 ----------

It's not that I am scared to root my Head Unit - its that I don't believe there is any way to root my Eonon unit, at least without installing a ROM update.

I have used Tasker ( a little bit) to automate non-rooted functions, but it appears that some of these Tasker task that alter Accessibility, requires Tasker to have root access

Thank you for taking the time and making the effort to make the tasker suggestion.

FYI

Looking at the big picture: FCC's support for Split Screen is a technical achievement, but I am not sure how much I really want to split screens on my car's head Unit.

The only reason I can see to do so, is to have a GPS (say Goodle map), running in a split screen, while keeping some FCC widgets visible on the screen at the same time.

But an added factor (for me), is that MyHead Unit is installed in older car, replacing a radio that was mounted very low on the dash.

So it is both far away, and down low, making it difficult to view while keeping an eye on the road while driving.

To help with this, I have made most FCC screen Touch function, available on the steering wheel.

This greatly reduces the need to carry out touch operations on the screen, or complicated changes where one has to keep a prolonged look at the screen.

(ie setting up split screens with multiple steps, only to end up with FCC squished up in a split screen, and no longer so easy to view.)

So, when I have say the GPS displaying, it is better to have it as big as possible, and not in a split screen, cluttered up with buttons that I really do not need available, if I am using and frequently looking at the GPS.

Also, with both mechanical Buttons on the head unit, and on the steering wheel to select FCC (Home), or GPS, there is little need to have both displayed at the same time.

So, why am I even messing with Split screen ... maybe the same answer as to why you would climb a mountain .. because it is there !!!

It is also technically interesting to study and experiment with these advanced features, even if at the end of the day, one decides not to make use of them.

Also, if I am going to Beta Test FCC, I feel I should beta test all its features as a complete application, and not just a few specific area of it.

Beta testing FCC over the past 2 year, has been a most enjoyable experience, and I like to think that my contributions have added something to FCC that may well not have been part of FCC, if I had not contributed.​
[Android Head-Units] rigattoni:
Any PX5 can be easily rooted without custom ROM and we have an app to reactivate Tasker on boot.
[Android Head-Units] Scopesys:
I did not know that !!! I need educating ... can you point me in the right direction please. (via PM)
[Android Head-Units] rigattoni:
Just have a look at this posting --> https://xdaforums.com/showpost.php?p=76725981&postcount=740

You need to install the newest ADB package on your Laptop --> https://www.xda-developers.com/install-adb-windows-macos-linux/

After

# adb shell /system/bin/su --daemon&

the console may get stuck. In this case just close the console and reopen it.

Then follow up with these commands:

# adb remount
# adb shell /system/bin/su --daemon&
# adb push rooting.rc /system/etc/init/rooting.rc

Additional most important information:

Never... never, never update SU if you open the app!!!

Link to SU: http://supersuroot.org/downloads/supersu-2-82.apk

Link to SU-zip: http://supersuroot.org/downloads/SuperSU-v2.82-201705271822.zip

Unpack the ZIP and a file named su in SuperSU-v2.82-201705271822\arm64

Store the "su" file in the adb folder

Install SuperSU on your device, but don´t touch the Update now!!!! Otherwise the unit will run into a bootloop and you need to flash the firmware again. (softbrick)

Attachments:

Tasker import file to activate ADB on your device. So you don´t need to install any terminal emu on your device, if Tasker is installed. Just import the task and run it. At the end the unit will be rebooted.

OPEN_CMD-HERE.BAT as zip. place it in the same folder as the adb.exe and click to open the console in this folder. It´s easier to work with instead of walking through the paths with CD...

This root method works with each PX5 and PX6 unit, independent from the MCU.

Tried it with CSN2, some MTCD/E and the newest RL7Ac.
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] while you’re in the mode of fixing a few bugs, there’s one that I’ve had for a few months (it’s nothing major).

One of my players is Apple Music and I have it whitelisted in Hal9k rom on Android 8 but when I start the unit from sleep if Apple Music was the last player I used when it wakes up then it will carry on the song from where it stopped when I turned the unit/car off but there is no album art. What I have to do to get album art back is to wait for the next song or if I press pause/rewind/ffward then the album art will appear.

I apologise if you’ve already fixed this as I e not updated in a couple of months.
[Android Head-Units] SpeedFire-:
FCC 3.365 v26:

- This version may work slightly better with NavRadio+
[Android Head-Units] Scopesys:
Player widget NEXT/Previous now working, but not always reliably.

Previous version seemed more stable, when station changes only worked off the Steering wheel buttons.

But NavRadio+ also seems unstable.. sometimes, even in Full screen.

Started to make a Video, but after 10 minutes, the results were so unstable & un-repeatable, I stopped, as it became a mess.

The RDS text coming from Navradio+ and displaying in the FCC Notification or the Player widget's SONG ARTIST is still broken up into small parts.

One EASY thing to fix is to stop displaying the Progress bar when NavRadio+ is selected as a Quickplayer (It's meaningless, and just counts up to max and stays there)

Difficult to get a grip on what is going wrong, as both NavRadio+ and FCC's processing of navradio's Notifications seem to both have bugs - difficult to tell which App is the major cause.
[Android Head-Units] ntldr:
Here is a test I've done yesterday after factory resetting the unit and clean installing FCC and NavRadio+. It's pretty much unusable for me (I am using a Dasaita PX6 unit / Rockchip rk3399)

https://youtu.be/BrF3OIDmwWQ

So far, the only launchers that work pretty well (but not perfect) with NavRadio+ are Agama and Car Launcher Pro. Unfortunately they lack the high level of customization that FCC provides.

Maybe I'm wrong and what I'm saying now may sound stupid, but I think one problem with NavRadio+ is that it can't register itself as the default Radio App, and all launchers are calling the default Radio app when they switch back to radio.
[Android Head-Units] Scopesys:
Currently, I am also getting similar operation with NavRadio+ in FCC

(a) Works mostly ok for a short time, then becomes un-responsive

(b) Often, even the Full screen Navradio+ becomes unresponsive, or does not even display the navRadio+ APP's screens correctly.

Your Video seems to show you having to go into APPS, and re-start navRadio+ ???

You also did not seem to have any time, where the navRadio+ displayed logos consistently for Radio station changes, let alone displaying the RDS information.

( maybe you don't have Logos set for your radio stations ? or FCC displaying the RDS information ( song, artist etc)

I'll add a Video I made yesterday, which shows issues similar to yours. Its Long, and somewhat "mixed up" (Understatement !! ), and I was not going to post it, but it does go to show that I am getting similar "unstable operation", like in your video.

NavRadio+ with FCC as of 5/29/2020
[Android Head-Units] okij:
Thanks, I will try it too and see what has been improved. :)

Why did APK increase from 52 MB to 71 MB between v25 and v26? :confused:

Also, yesterday I still had two launcher restarts with v25 without apparent reason, even though you said that you hope that they are fixed in v25. Should I catch a logcat for you when it happens next time?

BTW, the launcher restarts began with the implementation of split mode in FCC.

Since I - like [MENTION=9325785]Scopesys[/MENTION] too - don't really need split mode support in FCC, I would vote for a user option in FCC settings to disable split mode support, if this makes FCC more stable again on certain head units or setups.
[Android Head-Units] mr_shaba:
I share the opinion/wish of okij.
[Android Head-Units] ntldr:
I never used/needed split mode. I vote for stability.

---------- Post added at 10:49 AM ---------- Previous post was at 10:46 AM ----------

@SpeedFire- I noticed another issue. The reboot button doesn't do anything when pressed in the app drawer. However, it works as a widget. Can you fix that? I don't want a reboot widget on any of my home screens, but from time to time, I want to reboot the unit :) It used to work on a previous version I installed a few months ago.
[Android Head-Units] Scopesys:
"No Pain, NO Gain" .... while I personally don't think I will use Split Screen. I do fully support FCC continued development.

Split-Screen is a new feature, that may have growing pains.

Like all new features introduced in FCC over the past 2 years that I have been using FCC, it can take time to get bugs sorted out, but the end result has always been good.

I look back at some features that took a little time to get working properly, and am glad that SpeedFire- worked on them, added them, and got them debugged.

Feature like Settings Back-UP & Restore, Quickplayers, Compass, Bluetooth and Wifi widgets -- now all working well, contribute to make FCC the great Launcher that it is today.
[Android Head-Units] okij:
Yes, I also fully support FCC continued development and I am not against split screen support in general.

That's why I wrote: "I would vote for a user option in FCC settings to disable split mode support, if this makes FCC more stable again".

It seems to me that [MENTION=4292729]SpeedFire-[/MENTION] needed to add some trickery to add split screen support, which e.g. leads to FCC launcher to be shown on the recent apps screen, while normally launchers aren't shown there. Of course this is not a problem if FCC will be running rock stable again, which currently it isn't. Also I found that the home button didn't work reliably to get back to FCC launcher in the split screen test versions, although this got better again in the latest releases.

So I keep my fingers crossed that the remaining instabilities with the split screen support gets solved. But if they souldn't get solved, I hope that there will be a user option to disable split screen support. :fingers-crossed:
[Android Head-Units] okij:
[MENTION=1633144]speedfire[/MENTION] and [MENTION=2734955]KoTiX2[/MENTION]: I now tested FCC 3.365 v26 for a while and have to confirm what [MENTION=9325785]Scopesys[/MENTION] wrote:

Using the next/previous button on the player widget now puts NavRadio+ in a weird state, where no station list, station logo and frequency is shown (please see 1st attached screenshot).

Also after selecting the favourite list again, NavRadio+ still is not responding to button presses on the favourite list. The button changes, but the selected station doesn't start playing and there still is no station, logo and frequency shown (please see 2nd screenshot).

Even a reboot of the head unit doesn't fix this weird state! Only after starting the stock radio app (which I activated again in app settings for testing this), the radio starts playing normally again and also NavRadio+ is in its normal state again when starting it (please see 3rd screenshot).

Also the changing between NavRadio+ and other players still isn't working well in v26: The biggest problem is that when changing from NavRadio+ to another player, often the radio sound isn't turned off or muted, but continues to play along with the audio outpot of the other player.

With v26 it seems to me like FCC launcher still directly accesses the radio hardware instead of only using media intents to access the NavRadio+ app.
[Android Head-Units] jrobbom5:
Just to remind everyone, the split-screen version of FCC that [MENTION=4292729]SpeedFire-[/MENTION] has been busily working on is an *Alpha* release, which means that it has had only rudimentary testing done. It is 100% expected to be unstable. If you want a stable release, then just install the version from the play store, it works a treat. Every software products goes (or at least should go through) through Alpha and Beta phases of testing before being released, most developers do not share alpha builds or even beta builds, we are lucky that #SpeedFire- is happy to share them with us. But they are only for people who want to help test new functionality and are happy to accept the consequences of instability and crashing. Like I said, if that's not you, then just stick with the version on the play store.
[Android Head-Units] okij:
[MENTION=9400855]jrobbom5[/MENTION]: Yes, of course.

I'm sure that the people on this thread know what alpha and beta releases are and that's why we're here on xda and on this thread, for testing stuff and reporting back. Because it's fun. :) Otherwise we could download FCC from Play Store like the average user and leave our comments there. ;)
[Android Head-Units] jrobbom5:
well, given that people have been complaining that the alpha release is unstable, I felt that it needed to be emphasised.
[Android Head-Units] Scopesys:
Well, that saved me an Hour , as there is now no need to post in detail what I find the current situation is at my end.

I get EXACTLY the same results as all 5 of the points made by [MENTION=4916555]okij[/MENTION]

One thing that is now working today, that was not yesterday, is that FCC now displays the whole RDS text correctly, and even updates that RDS text, when Radio station updates its current song.. That's a GREAT PLUS.

If one LUCKS on a situation when it all works for a given radio station, then all is good, but the issue arise when the station is changed, either by the FCC widget, or back in NavRadio+ Full screen.

SO the overall impression I get is that there are currently some Instability issues in NavRadio+, so it is not surprising that FCC is having issues displaying what the APP is doing, in FCC's Player widget.

NO IDEA why the RDS text is working today in FCC, when it was not yesterday. I did not update anything, and I have Auto-Updates turned off.

I also Re-Booted the head unit several times yesterday, back then was still getting the Partial RDS text being displayed by FCC.

That problem did not present itself at all today .. when FFC displayed the text, it was complete, and if too long, scrolled as expected in FCC

---

BTW Apologies for posting some previous Videos in this forum that were not viewable by anyone. Had permissions set wrong on Google Drive. :(

Hopefully that is now corrected. Today saw a whole slew of Notifications that viewers could not access the Videos.

I think in future, I will throw them up on YouTube, set so they are are not searchable on YouTube, but can be viewed if one has the correct URL (ie from the forum)
[Android Head-Units] okij:
Where did people complain that the alpha release is unstable?

We only give feedback after installing and testing new versions, so that [MENTION=4292729]SpeedFire-[/MENTION] can take notice and improve things.

And IMHO it is OK if users on this thread write if they need a certain feature or not, so [MENTION=4292729]SpeedFire-[/MENTION] can improve or implement things that the users ask for. As I wrote today, I personally don't really need split mode support in FCC, but of course it is OK for me if other users need this feature and if it gets implemented.

But as wrote today, I would like to see a user option in FCC settings to disable split mode support, if this makes FCC more stable again on certain head units or setups. With this I mean that if for some reason split mode cannot be made really stable for a release version (e.g. when this instability is caused by Android itselfand cannot be fixed), then there should be an option to (de)activate split mode support. Otherwise the users on Play Store would complain about restarts of the launcher.
[Android Head-Units] jrobbom5:
You yourself wrote:

We already have a stable version, its in the play store. But you weren''t the only one, I have noticed several people expressing similar opinions lately, and so I felt an explaination was necessary. You might night like it, but I don't really care :)
[Android Head-Units] okij:
[MENTION=9400855]jrobbom5[/MENTION]: a) This wasn't a complaint, b) please read my previous post for explanation.
[Android Head-Units] Scopesys:
Running Navradio+ again today, it looks like FCC & NavRadio+ are getting out of sync when the Previous Station Player Widget is used to change the radio station.

TO reproduce. get navRadio running and playing a radio station, and use NavRadio+ fiull screen to change radio stations. All works well.

Then try using the Player widget to change stations, and if you go BACK a Radio station, things get out of sync, all becomes unstable, and navradio+ will actually crash if you select another player !!!

I have a Video of this .. spent 1 hour editing out all the irrelevant bits, and adding captions, but, just as I was finishing, the Video Edit crashed, and I lost it all. Not editing it again.

But here is the original version, will all the unnecessary (and often wrong) comments !!!

NavRadio+ with FCC 5-30-2020 VIDEO

And now I find that Moviemaker kept a backup as I was editing, so I still have the Edited version !!!

VIDEO --navRadio+ & FCC in the Twilight Zone - Edited Version

CORRECTION: Its the FCC Player Widget Previou-Next that seems to cause the issues.

It's after thinks break down, that the Steering Wheel buttons stop working.

So, 3rd time lucky , a 3rd Video that shows this in better detail.

Video 3 -- Its NavRadio+ causing some of the issues.

Later on, I tried Navradio+ with FCC uninstalled, and it still got into a locked up condition, where it stopped displaying Radio Channels, and would not tune the Radio, without a full system re-boot.
[Android Head-Units] SpeedFire-:
This was already fixed in the latest betas here
[Android Head-Units] SpeedFire-:
Yes, current way to control NavRadio is not good. It uses some hacky way to control it which have some bad results.

Normal way to control it (via Media Button intents) should work but they do not work for me. I'll try to find another way.
[Android Head-Units] okij:
How about working on this together with [MENTION=2734955]KoTiX2[/MENTION]?

I mean, if the Media Button intents don't work, maybe it's on his side to have a look after it. I'm not sure about this though, since NavRadio+ is said to work with other launchers, so probably the intents actually are working.

[MENTION=2734955]KoTiX2[/MENTION]: Could you comment on this and offer some help, e.g. with some documentation of the intents that can be used to control NavRadio+?
[Android Head-Units] ntldr:
Here's a new feature request,if that's possible. Can we have a widget that displays the car's battery voltage? On my PX6 unit that's possible in the status bar, but I usually prefer keeping the Launcher in full screen.
[Android Head-Units] KoTiX2:
I'm talking with [MENTION=4292729]SpeedFire-[/MENTION] privately don't worry.

;)
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

[MENTION=2734955]KoTiX2[/MENTION]

FANTASTIC -- Good to hear .. I have now invested many, many hours messing with NavRadio+ in FCC ( and NavRadio+ just by itself).

(An insignificant amount of time compared with you guys developing your Apps, but still "Fun" time for me.)

Unfortunately, I now have a major issue with NavRadio+ -- I had made a whole set of local radio station Logos, and got Navradio+ set up to use them.

Then I decided to BUTTONIZE the logos, so I had Navradio+ CLEAR all Logos.

Now NavRadio+ will not accept any Logos. (The original ones (250 x 250) , or the buttonized ones which are 200x200 )

Uninstalled, re-booted, re-installed, and still, NavRadio+ CRASHED when a logo is selected, (before telling to save).

(sent numerous Crash reports from within the app for this)

Also, as other have reported, NavRadio+ often gets into a mode where it stops displaying any Radio Stations, and requires a Re-Boot to start working again.

Since this happens ,( even if FFC is running or not,) for me its time to take a break, until his bug is fixed in NavRadio+ as it is (for me) Unusable.

Hope you two Developers can get all this sorted out .. I was fast becoming a fan of NavRadio+ :)

Attached are my set of Maryland Logos (a normal and Buttonized sets)

UPDATE: 5/30/2020

Above Logo work, but Logos MUST be put in NavRadio's default folder for it's Logos .. RADIOLOGO folder
[Android Head-Units] Scopesys:
Ref: NavRadio+

After many hours of messing with navRadio+ (with FCC), I finally have it "able" to work - and it keeps working with current versons, provided you follow some special rules.

(1) Only change radio Station with NavRadio+ in FULL Screen

ie Do not change stations by Swipe, Widget buttons or steering wheel buttons.

ie do NOT (at the moment) use FCC to "CONTROL" NavRadio+

(2) DO not switch to your Default radio and change Frequencies there either. This will also cause sync issues.

I have found that if you use Navradio+, following these temporary restrictions, its runs pretty smoothly.

But if you break these rules,and thing lock up or get out of sync, its a "Royal Pain" to get things working again, requiring re-boots etc.

Another rules seems to be .. If you add your own logos, they MUST be in NavRadio+'s RadioLogo folder ( and be png, not jpgs etc)

.. BTW That is where any Logo's obtained by download using the Navradio App's collection get put by navRadio+

What a weekend !!! Did not help that it was REALLY Hot, and after a drive when the car as hot, I parked in the garage, and played with this, without the Car's A/C on.

All sort of CRAZY things happened, crashes, freezes, etc .. because CPU was up to some INSANELY high temperature.

S0 a good part of the weekend was spent, pulling out the head unit, and installing a couple of Fans in it. Now it does not overheat at high ambient temperatures !!.
[Android Head-Units] KoTiX2:
The most important thing to know is that the NavRadio don't work correctly if you run the original radio app too and viceversa.

Mostly one app loose the MCU control and the audiofocus when you start the other because the other take control.

You need to stop/close the app you don't want to run to have back things to normality.

So why many people disable the original radio app or even remove it for the system.

I don't know if this happen with FCC too but for sure it's better to not run the original app from it.