yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] agentdr8:
Yeah, the max_forward_clicks is a constant; in fact most (all?) of those settings are technically constants as they aren't set via SharedPrefs or any other areas within code that I can see. And yes, this Integer is being overwritten via the module to handle the 6-tap limit. Unfortunately that's only one piece of the overall restriction pie. There's GPS-based movement sensing, and vehicle-based movement sensors (wheel speed, vehicle GPS, gear selection, etc).
[Xposed Framework Modules] DMCShep:
Took a look at the GitHub code, wow does rovo89 make Xposed coding dead easy. Wonder if he coded API's professionally, it looks like any coding library I've ever worked with reliably. Having coded a few Android musings back when KitKat was still early adoption (and tried again with Android Wear to port a Tizen app I liked), this doesn't look all that different. I like that.

If/when I get a chance to mess around with this, I'd be recording every variable into a text file (damn wired connection removing easy logcat, unless I can get ADB over WiFi working somehow), and would sit there shifting between gears slowly but steadily, and repeatedly also. Anything that didn't change can be ruled out. Then mess with what's left!

Won't be until next month though, I'm moving in about a week, but will be happy to have a place where an electrical outlet and my car can coexist (read: looooong in-vehicle laptop sessions)

I have no idea what your particular process is, but I looked at Android Auto's AppManifest.xml first (extracting APK as a ZIP), found a few nuggets that might come in handy. Vanguard sounds familiar, Bluetooth heavy permissions ring a bell, I don't know if that's accurate or not, but there's another section that seems dedicated to the task of handling sudden changes from the OEM. Apologize for screenshot vs. text, evidently none of my text editors work with app manifests and only a text viewer which doesn't support copy/paste.
[Xposed Framework Modules] agentdr8:
That was my plan with an older debug version I had shared with a few individuals a while back. Unfortunately none of the output was as cut and dry as I had hoped, so it didn't amount to much. None of the gearhead: parameters seemed to be involved in the vehicle sensors though (at the time; seems the wheel speed sensor gearhead float does make a diff). I'm not 100% sure, but it's possible these signals are being decoded from CANBUS that the vehicle headunits are forwarding on to AA. And not having a vehicle with integrated AA makes debugging this use-case very hard for me to perform, so any help you can provide would greatly benefit yourself and the rest of the users here with built-in AA.

You'll likely want to take a look at these classes, as I'm fairly certain they're involved for vehicle sensors:

./com/google/android/gms/car/CarSensorManager.java
./com/google/android/gms/car/CarSensorEvent.java

I reverse the APK to java classes using dex2jar, and then dump the sources via jd-gui, and then parse through the java files until I find the methods I need to overwrite. Obfuscation makes it a bit harder to follow, since all the class and method names are replaced with various letters, but not impossible.

The icon on the very right-side of the AA home screen is reserved for the OEM. This screen can be populated with all sorts of additional info, not limited to only vehicle sensor output, but some other devs have creatively overwritten this last screen to be able project their own app output, such as the OBD2AA plugin.
[Xposed Framework Modules] DMCShep:
Wow, thanks! This should come in great handy, I'll take a look soon! The "browsing locked for safety" is a great motivator on its own :) I'll keep you posted on what I find, but CANBUS might be related, that's a good point too.
[Xposed Framework Modules] fk79test:
Hey,

first thx for this app!

on my old Phone with Android 6 it worked perfect.

Not on my Redmi 4X with Android 7.1.2 i did not get it to work.

Her is something from the Logfile, i don't know if i picked the right logfile
[Xposed Framework Modules] DMCShep:
Describe "worked perfect" and "not working".

Standalone Android Auto (phone only) / Integrated with OEM HU / Integrated with aftermarket HU?

I'm encountering a bug myself on Android Auto, need to diagnose if this module is related, but being in the middle of a Waze direction and taking a phone call messes Waze up badly. Street names look like a censored face on TV, guidance stops being useful, basically taking a phone call glitches the hell out of Waze. Good news is I'm done moving to my new house, but bad news is there's so much stuff to do here, I've not had many days at all where I'm solo yet, so can't yet look into this.

Maybe for the better though, it just snowed 4 inches yesterday and knocked out power in lots of places! Hopefully OP knows more about the latest report, I'm just helping out on the integrated HU side soon.
[Xposed Framework Modules] fk79test:
with my old Phone (Vernee Thor, Custom Rom, Android 6) it "worked", so i could tap as often i wanted to in Spotify in my car.

With the new Redmi 4x (Originial Rom, Android 7.1.2, of course rooted) it is "not working", meens i can just tap 6x on Spotify and then the warning is coming
[Xposed Framework Modules] DMCShep:
In your car -- in-dash Android Auto then? Huh, interesting that Nougat broke that part, that's exactly what I'm working on as soon as I get a decent environment to do so (OP doesn't have an in-dash HU)

[MENTION=434511]agentdr8[/MENTION] maybe overthinking it and it's a "Marshmallow / Nougat" bug rather than a simple "standalone / in-dash" bug? Also can't remember, but is there a different APK for Nougat vs. Marshmallow? I thought Google Play got smart at one point and started adapting to the end phone, we might be seeing something there.

It's a good lead, thanks for the report! :)
[Xposed Framework Modules] agentdr8:
What version AA do you have installed? I haven't updated the module for 3.0.5705 yet.

AFAIK, there aren't any different versions of AA for different Android versions. The only package differences are for the target architecture; arm, arm_64, x86, and x86_64.
[Xposed Framework Modules] fk79test:
i have AA 3.0.570554 installed.
[Xposed Framework Modules] agentdr8:
I would recommend installing the previous version of AA (2.9.xxx) if you need the module to function. You can find it on APKMirror.

For the 3.0.xxx version, Google has moved the 6-tap limit to its own class, and rewrote the method so that the value is a static local. I have to do some rewriting of the module to accommodate their changes, and don't know when I'll have it tested and working.
[Xposed Framework Modules] fk79test:
ok thx,

i just installed 2.9.574924 now and will test it tomorrow in my car
[Xposed Framework Modules] fk79test:
yeah that was the solution!

With AA 2.9.xx it is working now :)

But for the future it would be nice working with AA 3.xx :)
[Xposed Framework Modules] agentdr8:
Good to hear. Yes, I too need it working with 3.x, as I have a new wireless AA headunit on the way, and only the 3.x+ versions support wireless projection.

I'll update everyone once I've made progress.
[Xposed Framework Modules] Emil Borconi:
[MENTION=434511]agentdr8[/MENTION] try running the following command as root:

am start -n com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.devsettings.EngineerSettingsActivity

This should allow you to change the limit. My phone is not rooted so it's hard for me to test if changing the limit here it actually works, but it does refer to default value used in gservice, so they might have moved it, like many many things slowly migrating to Google Play Services.

P.S. This will also allow you to enable "wifi" for unsafe cars, but without a head unit which can handle Wifi connection that won't help you too much.
[Xposed Framework Modules] agentdr8:
I've never seen the tap limit in the engineering settings page before, just the parking speed setting:
[Xposed Framework Modules] Emil Borconi:
I think it was under vndevsettings before but it always was there. If it works probably just create an app which uses root to start this activity, that will work even without exposed being installed.
[Xposed Framework Modules] vlucchetti:
version 1.78 does not appear to be working with AA version 3.0.570554
[Xposed Framework Modules] agentdr8:
This has been addressed here. Module hasn't been updated for AA 3.x yet.
[Xposed Framework Modules] vlucchetti:
Thanks, didn't see that thread.
[Xposed Framework Modules] pjcamp:
I learned something new a couple of days ago. I have been having issues with SAA for a LONG time. It just wouldn't work, no matter what combination of SAA, Android Auto, and Xposed versions I used. But I was fooling around on Monday, looking for some files using Root Browser, and it wouldn't work either. So I used Root Checker and it said I did not have root access. But I know that I did a systemless root successfully and nothing has changed since then.

The problem turned out to be SuperSU. On my device, for some unknown reason, if I have it set to prompt me when an app asks for root access, it will do nothing. Eventually the request times out and the app claims there is no root. If, however, I set the default action in SuperSU to grant access instead of prompt for permission, it works flawlessly. So the ultimate problem I was having had nothing to do with SAA or Xposed. Xposed was asking for root and SuperSU just ignored it. Without root for Xposed, SAA obviously didn't function either.

So anyway, I mention this as something to look for it you are having problems. If SAA doesn't work, it might actually be SuperSU that is the problem. I posted in that forum but so far no one has replied.

SAA is an awesome module and now that I know how to make it work again, even awesomer.
[Xposed Framework Modules] DMCShep:
[MENTION=7787241]pjcamp[/MENTION] awesome to know, but I of course have to ask: what versions of all the things (Android, AA, SAAX) did you get working? :)

Also, wonder if SuperSU or Xposed logs would show anything relevant here. I checked my phone, and my SuperSU logs are too flooded with other apps that are working fine (I've disabled their logging as a result), still though. SAAX doesn't even show up as an app listed on SuperSU for me, only Xposed which already has granted access.

Just thought of this, but there's a "tapjacking protection" option in SuperSU too, if tapping "enable root" doesn't work on the dialog, I've often found disabling that setting allows me to enable root on a single app. But I usually still get the dialog, so might not help in your case.
[Xposed Framework Modules] pjcamp:
Haven't looked at the logs. Too tedious. Tapjacking is not the problem. I tried all the settings and grant by default is the only one that works. What is interesting is that SuperSU will occasionally pop up a dialog, but it is generally 5 to 10 minutes after an app has made the request. Tried removing and reinstalling SuperSU and nothing changed.

I'm stuck on Android Marshmallow thanks to Lenovo acquiring Motorola and not being able to find their ass with both hands. That's 6.0, not even 6.1. AA 2.9.574924, downgraded from 3.0 per previous comments. SAAX latest 1.7.8. Xposed 3.0. SuperSU 2.82.

I don't think you'd see SAAX on SuperSU since it isn't an app itself, just a module inside XPosed.
[Xposed Framework Modules] DMCShep:
I laughed WAY too hard at that and I don't even know what it means :victory:

Thank you for version info, looks like I need to downgrade to pre-3.0 AA myself, lots of successful reports thus far! :good:
[Xposed Framework Modules] pjcamp:
What it means is that there is a Nougat update available but I can't have it. My wife got it 6 months ago. Our phones are identical, purchased at the same time, direct from Motorola pre-Lenovo, and we have always had the same carrier.

Lenovo support keeps telling me that updates come from the carrier and I have to wait for the carrier I bought the phone from to provide it to me. I keep telling them I didn't buy it through a carrier, I bought it direct from them, and the whole point of the X series was to make the phone purchase separate from the carrier choice, just like Google does with their Pixel phones. I've been going back and forth with them for two weeks and each time a new support person goes to the script and quotes the same text back to me -- you must wait for the carrier you purchased the phone from. I didn't buy it from a carrier, I bought it from you. I got updates from you before Lenovo took over. Now nobody seems to remember what Moto Maker was. It's very much like Kafka's The Trial. There haven't even been any security updates since Lenovo took over.

Motorola used to be the true hacker's phone. Don't buy Motorola.
[Xposed Framework Modules] Ralfioni:
I'm looking forward to your release as I'm reliant on 3.x which fixes the functionality to add reminders in Google Calendar (wouldn't work at all in previous AA versions for my Audi).

I hope the changes in 3.0 can be overcome. What do you think?

Thank you for all the effort you are putting into this!!!
[Xposed Framework Modules] DMCShep:
I still, latest version of everything (still haven't gone pre-3.0 -- I know, I know), get this weird issue of Waze refusing to hand volume back to everything else once it's done. I'll be driving somewhere when it lowers AA volume, says "turn left in 1.5 miles", and doesn't raise it again like it's supposed to. Makes for a maddening music experience when my car (a brand new Kia Optima with Harmon Kardon system too even) can barely drown out road noise as it is, and I'm stuck with an inaudible song or two until it issues the next command.

It definitely happens less frequently as both Waze and AA have gotten more updates, but it's hard to tell which is at fault more. I'm waiting for 3.0-compatible SAAX but nothing is preventing me from downgrading beyond fear.

Oh, and weird glitching in Waze after taking a phone call that forces me to find somewhere to stop, turn off my car, disconnect and reconnect my phone, and continue my journey, so at this point I'm kinda not wanting to tempt fate. I've learned to just not take calls while driving for the time being. But hey, just saw Oreo's rolling out on the S8, so guess it's time to mess around some more with it and see it that affects anything.
[Xposed Framework Modules] agentdr8:
I like to believe that anything can be accomplished given sufficient time, money, and effort. Of course money isn't really an issue here, but time and effort aren't something I have a lot of at the moment. But hopefully soon I can dedicate a whole weekend to trying to figure out the 3.x puzzle.

I'm pretty sure this is an issue with Waze. What version are you on? There's been a number of small fixes to their beta releases which may address these sound focus oddities.
[Xposed Framework Modules] DMCShep:
Latest stable, actually just got an update this morning, so let's see if that helps. Also rebooted my phone, I rarely do anyhow. Fingers crossed!
[Xposed Framework Modules] Ralfioni:
So I finally rooted my phone, installed Magisk, Xposed, AA 2.9 and the corresponding module. I adjusted the module settings, restarted the phone (Xiaomi Mi5, Resurrection Remix 5.8.5, Nougat) but my Audi still shows the warning (see attachment). Could this be a headunit related issue? Audi does not use touch screens but a dial to navigate through the Android Auto UI.
[Xposed Framework Modules] krilok:
Yeah, not working for me either... Still get the warnings...
[Xposed Framework Modules] Ralfioni:
Which HU and Android version are you using?
[Xposed Framework Modules] pjcamp:
See my post further up. Try setting SuperSU to always grant permission by default and see if that works.
[Xposed Framework Modules] DMCShep:
I still don't know why that worked for you or how you were missing dialogs in the first place, but if that fix works, do remember to change it back to "ask for root" and re-test. A clean phone is a happy phone, and malware sucks. Only takes one rogue app... Worst case, phone responsibly and "always allow" root if that's what's needed.

Re-reading your post, I see you mention Root Checker not seeing you had root at all. Where can I find said app? There's multiple in the Play store with that name, I think even F-Droid has a couple. Also, does it now show you have root? You didn't specify if changing that setting made Root Checker acknowledge you have root or not, although I would hope it did.
[Xposed Framework Modules] pjcamp:
Yeah, I know. It is a pain in the ass and I don't know how to fix it. I posted in the SuperSU forum and got no answer. It absolutely does not work in prompt mode. Not at all. Sometimes I'll get a dialog 30 minutes later, but mostly nothing ever happens.

The Root Checker app I use is Joey Krim's:

https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
[Xposed Framework Modules] krilok:
I've a Kia Sportage with a built-in head unit, and AA version on phone is 2.9.57. Using Magisk, not supersu. Xposed module activated and all permissions granted...
[Xposed Framework Modules] Ralfioni:
Xposed Installer definitely has root on my device. Your root checker confirms root is available. Using Magisk instead of Super SU shouldn't be a problem, right?

---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------

Anyone here using SAAX successfully with an Audi or VW builtin HU?
[Xposed Framework Modules] DMCShep:
Dialog and confirmation of root for me.

[MENTION=2913096]krilok[/MENTION] does Magisk allow root permissions? The consensus seems to be "it's complicated" from what I can tell, I seriously can't figure out if it's a good SuperSU alternative.

Kia Optima myself, not working yet but haven't tried anything to fix it either.

EDIT: just to be clear, I have SuperSU and not Magisk, and AA 3.0 isn't working (although [MENTION=434511]agentdr8[/MENTION] they just released AA 3.1 if I saw the AndroidAuthority APK breakdown article right, don't know if it will help or hurt progress on a 3.x fix at all)
[Xposed Framework Modules] krilok:
Yes, Magisk is a great alternative to supersu, and so far I've had no problem with it. All root operations work well, and has a few extras supersu lacks...
[Xposed Framework Modules] agentdr8:
Yep, saw the 3.1.x version. I haven't had a chance to take it apart yet, but I have a feeling it'll be the same as the 3.0.x releases.
[Xposed Framework Modules] CUBENSIS:
Yes, works for me on Audi. If it doesn't work for you, it's more likely a problem w/ your install (eg wrong version of AA).
[Xposed Framework Modules] Ralfioni:
Oh, thank you for letting me know! Which AA version are you using? I tried 2.9 with the corresponding SAAX (1.7.8) and it did not work.

Car is a 2017 A5 SB in my case. Other Xposed modules work for me - so the phone's setup is okay AFAIK.
[Xposed Framework Modules] DMCShep:
It's still a hit-or-miss on whether AA 2.9 works, it is not safe to assume that this is brand-specific or even model-specific. Look through the last few pages and you'll see conflicting reports across the board. Heck at this point, the phone used might have something to do with it, it's too early to say. (And buying a brand new Audi is beyond the budget for agentdr8 I'm sure ;) )

AA 2.9 seems to fix it for about half of the people posting here, based on their follow-ups or lack thereof, but it needs to be emphasized that this doesn't fix it for everyone and the other half report back that it doesn't work. Sometimes an oddball fix is found, but it is more likely to be have a more global fix when AA 3.1 is working with this module. Give agentdr8 time, he'll figure it out.
[Xposed Framework Modules] Ralfioni:
I hope he does. I'm curious how "taps" are counted if there is no touch screen involved - like on my Audi. It's SUPER annoying if you don't even get to scroll for more than a few songs. I also do not understand why Spotify induces an additional "15 songs per page" limit that not even Google Play Music has. WTF?

BTW: Here's the more or less "official" thread regarding this topic on the Google product forums:

https://productforums.google.com/fo.../EP2qxj9XjgY;context-place=forum/android-auto

I would really like to see a Google employee make an official statement about this. So, feel free to speak up, guys!
[Xposed Framework Modules] DMCShep:
Scrolling is my biggest gripe too. I mean, I am perfectly capable of knowing my target starts with "S" and seeing I'm in the "L" section and now forbidden from going further. And this is WITH touhscreen on my 2017 Kia Optima.

I'm just in this apparently unknown group where Waze will freak out if it has to make a command go out while I'm taking a call in Android Auto. When I go back it just spazzes out so badly that everything becomes useless. Keeping Waze and AA updated has so far mitigated the worst of it, so in my use case, AA 2.9 isn't even a viable option.

Good damn luck getting Google to make an official statement on this lol. They still never made any substantial statements about the future of Android Wear, everyone just assumed by the name "Wear OS" they were heading more universal and compared to the amount of inquiry about it they've said nearly squat. When you control the ecosystem, do you need to explain yourself?

Android Auto probably has the same team size Android Wear did in its hay day. Which is to say small, and they probably don't have the same access to legal opinions that they did upon starting this endeavor. I doubt they're going to go the Waze route and ask "passenger?" as that was a decision made by the guys at Waze well before Google owned it. Google is taking the safe (but aggravating) approach that no one can be trusted about it, rather than writing up a set of legalese that says that pressing the "passenger" button as a driver absolves them from any responsibility and linking to it in a dialog (which, again, requires a legal team to write).
[Xposed Framework Modules] Deniz343:
Can somebody please share all preferences for Android Auto. I'm wondering if it's possible to change screen size or aspect ratio for better user experience for vertical oriented head units.
[Xposed Framework Modules] shmykelsa:
Does this module support latest AA?
[Xposed Framework Modules] agentdr8:
Unfortunately no. With the relocating, and all my regular work commitments, I haven't had any time to look into adapting this for the latest AA.

If anyone wants to contribute or fork the code, it's available on my gitlab.
[Xposed Framework Modules] Ralfioni:
I have basic PHP experience. :D Any suggestions for an Android developer crash course that will enable me to make the necessary adjustments within a short period of time?
[Xposed Framework Modules] agentdr8:
I've managed to find a few extra minutes to take a look at the latest (3.4.582534) AA code.... from my initial look, it seems that Google has removed the 6-tap limit? Can anyone verify this? I don't think I have enough libraries or content in order to tap 6+ times to reach, so I'm having a hard time validating this. Keep in mind, the tap limit is different than the scroll or browse limit.

The message I'm seeing when "excessively" scrolling is "Paused for safety", which I believe is called the content rate speed bump, and I believe I can override that easily enough.
[Xposed Framework Modules] DMCShep:
Tap limit being different from scroll/browse limit: if I click "page down" buttons more than six times, does it mean I just tapped past the limit or scrolled? App in particular is MD Player, although Waze would do the same browsing through Favorites. Trying to figure out when it would kick in.

My Kia's got "Auto Hold" and will maintain braking with my foot off the pedal, which still triggers all limits. Putting it into Park overrides them.
[Xposed Framework Modules] shmykelsa:
Starting from Android Auto 3.1, you can scroll as much as you like, but after 6 taps, a message pops out saying "Pay attention to the road" for 6 or 7 seconds, and then gives you the ability to scroll again.