yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] Area51©:
I don't see why the app which only uses BLuetooth can cause your issue. I am guessing "Mobile Data has stopped" is related to wifi.

Can you make a logcat?:

First install an app called Catlog from the Play store.

First start the app, click the 3 dots in the lower right corner, select More and then Settings. Set Log Display Limit to 100000.

After installing you can drag the Widget that it has to your home screen.

To start logging hit the Catlog widget and press OK.

Then do your things that cause an issue.

After this hit the Catlog widget again to stop recording.

Then from the menu, select send, as attachment, choose E-mail.

For destination use same email as donation email address or support email as indicated in the Play store.
[Paid Software Announcement and Discussion] CrossCroissant:
Mail sent, logcat recorded.

Edit: Installed a russian "custom rom", mostly a modified stock rom. Still same Error :(
[Paid Software Announcement and Discussion] Area51©:
Rootless version progress

Good news, I have a prototype of the rootless version working on a non-rooted Samsung S4. There's still quite some work to do to tidy up things and make it really stable as currently it's really unstable but the most difficult part is done now. Even multi-touch is working already.
[Paid Software Announcement and Discussion] adfurgerson:
Is this different from the "tethered" option you spoke of before? The method that required a P.C. or mini board to reset it after a reboot?
[Paid Software Announcement and Discussion] Dannn531:
Miracast Interference

Has anyone had any issues with display quality and interference when using a Miracast adapter?

I have an SPH-DA120, Microsoft Wireless Display Adapter V2, rooted Note 4, MM 6.0.1, HDCP is disabled and I can successfully connect and mirror without much of an issue.

After a 10-15 minutes of driving, the casted portion of my display starts to get fuzzy, and eventually becomes unreadable. If I touch the display, it will clear up for a few seconds then get blurry again. I updated the WDA firmware, and it will now hold a stable connection without dropping out, but the display keeps getting blurry and twitching. I've tried a 3' HDMI extension cable, 6ft Male-Male cable with a female-female adapter, and tried placing both the phone, and display adapter in different locations without much luck. Also disabled bluetooth, wifi scanning, and mobile data without much luck. Even when not in full app mode, and just mirroring VIA HDMI input, its still fuzzy. It only happens after a few minutes of driving though.

Cable shielding maybe? Direct connection through a samsung MHL adapter works alright, but it does cut out completely from time to time if the cable moves around too much.
[Paid Software Announcement and Discussion] Area51©:
No it's that option. At least I know that option is working. However there might be another option to use the additions that are done to the Accessibility Service on Android N.
[Paid Software Announcement and Discussion] Area51©:
What if you connect it to your tv at home, does it happen also? Unfortunately a car is not the most RFI friendly environment for using wireless devices.
[Paid Software Announcement and Discussion] Dannn531:
It stays clear at home on my TV. I had the same thoughts about wireless interference in my truck, gonna do some testing with shielding and such. Probably gonna pull the appradio out and bench test it to see if I have any interference away from my truck.

I did just have a thought about what may be interfering, might be my factory TPMS (tire pressure) sensors. I know its a different frequency, (300-450mhz roughly) but might be a start.

Also going to mess with the 2.4ghz-5ghz forcing on my adapter, think I might have a method to make it switch over to 5ghz after negotiating on 2.4.

I will report back soon.
[Paid Software Announcement and Discussion] Dannn531:
Gave up on the Microsoft adapter and bought an actiontech screenbeam mini2. works great with zero issue. Wish i would have bought one of those originally instead of the MS adapter.

I did get a bit of the interference to go away with the MS adapter by powering it from a portable usb charger, however it still had some odd fuzzing issues. Thinking I had some sort of ground interference between the 5v usb power from the radio or car charger i used and it was feeding it into the HDMI cable or something. oh well.
[Paid Software Announcement and Discussion] AgentJz:
Ftw you can update the sb mini software with an android app, try that
[Paid Software Announcement and Discussion] Area51©:
In the AppRadio Unchained Reloaded alpha community there was someone doing the exact opposite, claiming that the Microsoft adapter was a lot better than the Actiontec. Btw, are you already using the alpha version?
[Paid Software Announcement and Discussion] Dannn531:
I think I'm using the alpha version. I'm signed up for the alpha community currently, and have joined it through google play. I have all of the screen mirroring options under settings. I'm on version 0.31
[Paid Software Announcement and Discussion] Area51©:
Yes that's the alpha version.
[Paid Software Announcement and Discussion] Catskinner:
Well today I got a notification that a new system OTA was waiting for my Nexus 5x. Since I'm using chainfire systemless root I flashed the OTA with flashfire without thinking about it too much, until I discovered that this was the Android 7 system update and I found myself upgraded tot he best and latest of what Google has to offer..

Oh my...

Miracast seems to be gone for good. The "persist.debug.wfd.enable=1" line was gone from my new build.prop file, although strangely enough the cast button with it's additional options remained active. Nevertheless, I re-added the line, rebooted the device and - no joy. The MS dongle is discovered, the Nexus 5x tries to connect and fail - repeatedly. I took the adapter home but the phone won't connect no matter to which screen or TV I'm trying to cast.

Has anyone experienced a similar problem with Miracast and Android 7? Is there any other solution that enable me to connect back to my car? The Nexus 5x has an USB-C port for which of course no cable adapter exist that will connect to the car and until now Miracast worked extremely well with Marshmallow, so I never looked for another option. Any suggestions how to get myself out of this mess?
[Paid Software Announcement and Discussion] bryanintransit:
I have the same problem on my rooted Nexus 6P running Nougat. Everything worked fine on Marshmallow.
[Paid Software Announcement and Discussion] rsandoz:
I am on a Note 4 (rooted) with MHL2 adaptor. I have ARUR (paid) and while it work good, there are some glitches (sometime comes up blackscreen, no connect, etc). I am considering getting a new phone. I have tried it with an Asus Zenphone and it didn't work. What rootable modern bigscreen phone works best? ARUR compatibility is now a consideration in my phone purchase decision as mirroring it to my truck radio is now something I can't live without.
[Paid Software Announcement and Discussion] slickric21:
I dont know of any latest gen smartphones with mhl support bar the Sony Xperia line.

There is slimport or hdmi over usb-c possibly on the latest LG or HTC phones...but charging at the same time is a big question mark.

Myself personally will be keeping a Galaxy S5 soley for ARUR in the car and use a 2nd newer phone (when i get one) just for bluetooth calls.
[Paid Software Announcement and Discussion] lpasq:
I too had no luck with Miracast once going to Nougat on N5X. I just went back to Chromecast without issues.
[Paid Software Announcement and Discussion] limeaide:
For whatever reason that has never worked on any of my pioneer h/u's. I was just hoping somebody else had this issue and found a viable work around. /shrug
[Paid Software Announcement and Discussion] mr_frog01:
Yeah Cant Wait! Keep in mind also here to help and test!
[Paid Software Announcement and Discussion] Area51©:
As soon as there is a version for testing available I will announce it here. I am trying to work on it as much as possible. I made the prototype more stable and also have implemented keyevent injection so now the buttons work as well. My best guess is that ETA for the test version is less than 2 weeks.
[Paid Software Announcement and Discussion] mumakil32:
Xiaomi/MIUI 8

Hello, I have a pioneer sph-da100 and Xiaomi with miui 8 rom, but the app is crashing after launch and when I press at the "Compatible Apps" button.

Or after touch screen setup.

I think I've tried all versions which you could find online(not the purchased ones) with the same result.

So the question is, if it's going to work with the version from the app market or it's a incompatible with MIUI 7/8 rom?
[Paid Software Announcement and Discussion] Area51©:
The only way is to try. It will work on any 'normal' Android version. Custom ROMs however can have weird behaviour and crash apps that work on regular Android versions. You can try for 48 hours and get a refund if it doesn't work.
[Paid Software Announcement and Discussion] Pig Vomit:
I'm really looking forward to this. This app is the only reason that my device is rooted. I probably have a higher need than most people for phone security and I've always been uneasy with root. Glad to see this is being worked on.
[Paid Software Announcement and Discussion] Kaliman43:
I am using App Radio Unchained Reloaded Alpha on my Nexus 6P. SInce the Nougat update my Chromecast will no longer auto connect. I need to open the cast settings and click on the Chromecast device in order for it to connect. Does anyone know how to fix this?
[Paid Software Announcement and Discussion] Pig Vomit:
For what it's worth, I'm using the non-alpha version on a 6P with NRD90U using Chromecast to connect to my head unit. There was no change from Marshmallow to Nougat for me. I basically have the same auto-connect features on the Play Store version by using Tasker. It took me quite a while to figure out the correct Tasker profile, which I can post and explain usage if someone is interested. If there is a compatibility issue with the current Alpha, your auto connect problem could be solved with Tasker.

Based upon reading posts, it appears the alpha has a feature to adjust the delay time on attempts to connect to Chromecast? If so, I did notice that it takes just a few seconds longer to make the Chromecast connection on Nougat, so you may want to try increasing the connection delay number.

Since I've never even seen another 6P in the wild, I'm SHOCKED to see someone also from Orange County using pretty much the exact same setup with ARU/6P/Chromecast/Pioneer!

Regarding the Alpha.....for privacy reasons I've made a conscious decision to avoid all forms of social media, including Google+. I am a very satisfied paid customer for ARU, but would like to help test the alpha. Is there any way to get the alpha without joining Google+?
[Paid Software Announcement and Discussion] Kaliman43:
Thanks for the reply. Could you please post your Tasker profile? I have been trying to avoid using Tasker since the Alpha version handles the casting connection automatically. I have tried several different delays in the app 1, 5, 10, 20 and 30 seconds, still no luck.

I have yet to see another 6P as well. As for the beta version, I am not sure if it is possible without joining the plus community, that would be a question for Area51.
[Paid Software Announcement and Discussion] Pig Vomit:
Here's some screenshots and some explanations so that people can more easily figure out what's going on and how to set things up for their own device if their resolution is different and therefore the screen tap positions are off. These settings are based upon a Nexus 6P, rooted stock Nougat 7.0 NRD90U ROM.

Check out the Screenshot JPGs I've posted.

Screenshot1 shows positioning of quick launch icons. Note positions of Hotspot and Cast icons. Those icons must be in these positions in horizontal mode for the following to work correctly. Icon positioning can be adjusted in System UI Tuner (positions of other icons doesn't matter).

Screenshot2 shows 1st page of Tasks. Screenshot3 shows rest of the tasks.

Set up a profile in Tasker to activate a Task module when your bluetooth is connected to your head unit. Here, my task module is titled ARU Start. ARU Start module contains the commands in Screenshot2 and Screenshot3. The time settings in #11 and #13 can be adjusted as needed. The worse the signal, the longer it takes. These are probably longer than most people need, but coverage happens to suck at my house and this allows me to get down the street to a better location before the connection finishes. Your mileage may vary.

I also created a second Task list for stopping ARU and Hotspot (Screenshot4 and Screenshot5). I turned that into an APK with an icon on my home screen.

Here is an outline of what each of the Tasks do:

Waits 1 second to allow Bluetooth connection to finish (just seems to work smoother for me).

Launches ARUnloaded

Waits 2 seconds to allow ARUnloaded screen to load

Simulates tap on START button on ARUnloaded

Waits 2 seconds to allow ARUloaded to start

Simulates swiping from top (in horizontal mode)

Waits 1 second for settling

Simulates swiping from top to bring up quick settings icons

Waits 1 second for settling

Simulates tap on Hotspot

Waits 15 seconds for Hotspot to activate

Simulates tap on Cast

Waits 25 seconds for Chromecast to connect to Hotspot

Simulates tap on Chromecast device in top position on Cast device list

Waits 1 second for connection

Simulates tap on Home button to bring up Home screen
[Paid Software Announcement and Discussion] Area51©:
Did you check that in the phone's 'Settings->Accessibility' screen, 'ARUnchained Reloaded' is still enabled?
[Paid Software Announcement and Discussion] Kaliman43:
Yes, I checked that.

Once I select the "Cast" options and then "More Settings" where the available cast devices are listed, the phone will automatically connect. It is almost as if the application is not opening the available cast devices screen, or it is not keeping it open and waiting till it connects.

---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------

Thank you for this. I will try it if I cannot get the app to work soon.
[Paid Software Announcement and Discussion] Area51©:
Can you post a screenshot of what the Cast screen looks like in Nougat? Apparently it has changed from Marshmellow.

I didn't upgrade to N yet as then I don't have a device to test on that's running M and going back from a backup is a PITA.
[Paid Software Announcement and Discussion] Kaliman43:
Here you go. As soon as I grabbed this screenshot the phone connected to the Chromecast device automatically.
[Paid Software Announcement and Discussion] Area51©:
My guess is, it's not opening the correct cast screen but as soon as you open it, it does find the right thing to click on. Can you install an app called QuickShortcutMaker. Open it and select Activities, then scroll down to Settings. In there find the Cast screen. Can you tell me what is listed there? Something like com.android.settings/com.android.settings.Settings$WifiDisplaySettingsActivity. But probably slightly different.
[Paid Software Announcement and Discussion] Kaliman43:
This is listed for Cast:

com.android.settings/com.android.settings.Settings$WifiDisplaySettingsActivity

It appears to be the same.

I have seen the app load the screen, it just sits on the screen.
[Paid Software Announcement and Discussion] Pig Vomit:
I finally broke down and got the alpha. Love all the new automation.....but there does appear to be a problem with the final connection to Chromecast on a stock rooted Nexus 6P. Shows the Chromecast device name, but never clicks on it. I can manually click on it and it connects. So this does appear to be a thing with Nougat. I've gone back to the regular release and Tasker for now. Really looking forward to the rootless, that's what I would really like to try. Would much rather not be rooted. ARUnchained is the only reason I root.
[Paid Software Announcement and Discussion] Area51©:
Ok. Can you make a logcat when trying to connect as described here: http://xdaforums.com/showpost.php?p=68544193&postcount=1720 ?
[Paid Software Announcement and Discussion] Kaliman43:
I just emailed you the LogCat. Thank you.
[Paid Software Announcement and Discussion] Kaliman43:
Did you receive the Cat Log?
[Paid Software Announcement and Discussion] Area51©:
Yes. I looked into it briefly. The automation is doing something but not exactly the right thing. I need to compare with a successful one on Android 6 but I haven't found the time yet.

Ok, I looked into it. It seems the cast screen shows something like:

Cast

No nearby devices were found.

After some time it changes to?:

Cast

WRX

Is this correct?

It seems that the way this is handled in the cast app has changed so the events that the accessibility service gets are also different. Basically it's never detected that the Chromecast is available and so it won't be clicked once it becomes available.
[Paid Software Announcement and Discussion] taudio123:
samsung j7, chromcast and dual DV635MB

Is it possible to use Samsung j7 with chrome cast for this solution. Because as the j7 phone natively does not support screen mirroring of any kind and secondly will this app work with the dual DV635MB? Any help appreciated
[Paid Software Announcement and Discussion] Area51©:
Not sure if Chromecast does actually work with a J7. This app only works with Pioneer head units. Other brands are not supported.
[Paid Software Announcement and Discussion] Kaliman43:
Thanks for having a look at this. I never see the screen say "No nearby devices were found", I only see it with my Chromecast device "WRX" waiting for me to click on the device to connect.
[Paid Software Announcement and Discussion] Pig Vomit:
It was the same with me. Shows my Chromecast device, but never connects. Everything appears to work correctly except for the connection.
[Paid Software Announcement and Discussion] Area51©:
It might just display it very briefly. Anyway I need a device with Android Nougat to fix it but I don't want to upgrade my N6 yet so probably going to get a 5X for development.
[Paid Software Announcement and Discussion] Proof79rr:
Hello everyone, I have a note 4 and AppRadio 2 before I used arliberator with a cable MHL .... then with the move mashmallon stopped working I'm not making me create the virtual machine ... now my question is this wanting to go aru reloaded this problem disappears? and wanting to connect via Miracast you can recommend any particular device? (I bought one of China but does not work) needless to say I root permissions and SU ... thank you all
[Paid Software Announcement and Discussion] Area51©:
Yes, ARUR works with SELinux in enforcing mode. Please see page 4 'Fixing Miracast issues on rooted Samsung phones' of the alpha's user's manual: https://goo.gl/iYv1Qo

Better Miracast devices are the Actiontec Screenbeam Mini 2 and the Microsoft Wireless Display adapter V2. But your cheap one might work if you use the fix.
[Paid Software Announcement and Discussion] hainleander:
I have a rooted Galaxy S3. I keep getting installation failed. Any suggestions?
[Paid Software Announcement and Discussion] stargate125645:
I haven't been able to find what improvements are made by Microsoft in version 2. Have you any idea? Also, what's the latest with the rootless version?
[Paid Software Announcement and Discussion] Proof79rr:
Thanks , Now work The miracast And Buy Aru R

.......

I purchased and is spectacular ... less than a minute to connect and full mirroring .... But another question: You can not make a direct connection to miracat when you start Aru or even when the wi-fi detects the dongle start the Miracast and then connect dell'aru reloaded? It would be great if turning on the car did everything automatically :D:D:D excuse the form of language but use Google translated :o
[Paid Software Announcement and Discussion] adfurgerson:
There is an alpha version, I believe it launches casting after Bluetooth connection is made.

https://plus.google.com/communities/108835433120083901102?pli=1
[Paid Software Announcement and Discussion] Area51©:
Do you get 'Invalid license' when trying to connect or is it something else? If so please describe it in more detail.
[Paid Software Announcement and Discussion] Area51©:
I don't know either. I only know some people reported it worked better but that could just be the placebo effect.

As for the rootless version, I made quite some progress. I have a working prototype and all major issues are fixed/working. Just need to do tie up some loose ends here and there. Probably about 40 hours to go till there's a test version.
[Paid Software Announcement and Discussion] Area51©:
That's correct. The alpha version of the app supports automatic connection to casting devices.

You can apply here for the alpha version: https://plus.google.com/communities/108835433120083901102?cfem=1

You need to become a member of the AppRadio Unchained Reloaded Alpha G+ community to be able to get it.

Once you have access to the G+ community, you can find instructions in the pinned post on how to get the alpha version from the Play store.

The link I gave you already, is the user's manual for the alpha version: https://goo.gl/iYv1Qo
[Paid Software Announcement and Discussion] Area51©:
I ordered a 5X and will get it today so I have a device to run Nougat on in order to solve any issues. The casting issue is then easy to fix.

Coincidentally the AVH-X2800BT AppRadio One device that I ordered to see what can be done with that will also arrive today.
[Paid Software Announcement and Discussion] lpasq:
Thank you for continued development: 7PN78531UP655694C
[Paid Software Announcement and Discussion] stargate125645:
I presume this still requires access to ADB and a computer? I believe that was implied with an earlier post.

Are you expecting to be able to reverse-engineer the MirrorLink software?
[Paid Software Announcement and Discussion] Area51©:
Yes.

It doesn't seem to be mirrorlink but something proprietary. It would be a huge project to reverse engineer that so I am thinking more along the lines of a modified version of the Pioneer app that by coincidence works together with the rootless version.
[Paid Software Announcement and Discussion] stargate125645:
I presume the rootless method is going to be relatively simple, so the next question is compatibility. Do you think the method will work on all phones? And do you think updates to Android could block your method of access to remote touch?
[Paid Software Announcement and Discussion] Pig Vomit:
Just a quick mention.....

I've got a Nexus 6P, using it with a Chromecast to my head unit. On Marshmallow, while navigating long distances with the charger plugged in, I would have pretty significant battery drain on the 6P. Since going to Nougat, my 6P actually gains battery power to a full charge. Nougat, good!

Still waiting for rootless. Cat and mouse game with Google and SafetyNet (not ARU's fault) is getting frustrating. Would like to be able to unroot and lock bootloader.
[Paid Software Announcement and Discussion] mr_frog01:
Any update on the rootless version, Boss?
[Paid Software Announcement and Discussion] Area51©:
Finally finding some time to work on it. Just tried it with Nougat on my 5X. It's not working of course. SELinux is giving some trouble. Hope I can find a workaround.
[Paid Software Announcement and Discussion] RRSpikes:
This is what I get with my Note 4 or my Note 4 Edge connected a 4000, 7000 & 8000.

When pressing the ARUR widget:

Single tap = no effect.

Double tap = phones 'recent apps' appears.
[Paid Software Announcement and Discussion] Area51©:
There's only minor changes that should not effect this. I am just asking because some people like to use an ancient version.