yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] DMCShep:
I'm constantly getting a 404 when trying to download it within Xposed. Other modules download fine. Xposed logs don't really capture anything useful on it. 1.7.5 is latest?

Attaching screenshot, maybe it'll help. Rooted S8 on T-Mobile running Nougat. Any insight?
[Xposed Framework Modules] _Mist_:
This module works great for me, thank you very much!

I still get the "Paused for safety" message when I scrool items list in any media player(DoubleTwist or Rocket player).

I've poke around and looks like this code fixed the issue. It change duration of nag window to zero:

XposedHelpers.findAndHookMethod(targetcls2, lpparam.classLoader, "a", String.class, Long.class, new XC_MethodHook() {

[MENTION=439709]override[/MENTION]

protected void beforeHookedMethod(MethodHookParam param) throws Throwable {

String s = (String) param.args[0];

if (s.equals("gearhead:content_browse_speed_bump_duration_ms")) {

param.args[1] = (long) 0;

}

}

});
[Xposed Framework Modules] agentdr8:
That's odd. Might be an issue with the Repo. I'll check the link.

You can also download the latest release from the OP and just install it like any other APK.

EDIT: I think your Xposed Installer needs to refresh the module list, as the descriptions don't seem to line up with what's posted on the site. See image.
[Xposed Framework Modules] agentdr8:
Thanks! I'll add in that setting as well and post a new release shortly.
[Xposed Framework Modules] DMCShep:
This is what I ultimately wound up doing, but what's strange is that the latest version doesn't even show up.

I noticed that too, but the modules list updates automatically, and it does see two modules with updates from the last 24 hours (one in all chinese, one called GrindrMod, neither one of which I use). What I did note though after quickly glancing through them was that not a one of them has letters in their version numbers.

Maybe tag the next release as 1.7.6? Letters in the versions seem to cause issues on downloading the module through the app. Great work on the app by the way, can't wait to finally put it to the test! Android Auto acts like I never have someone riding shotgun, now I can force it to! :good:
[Xposed Framework Modules] _Mist_:
Spoke too soon. My fix works only partially. Still getting "Browsing locked for safety" while driving. But when phone is not connected it works.
[Xposed Framework Modules] DMCShep:
MD Player and Waze do the same kind of lockout if you need more test cases. MD Player is particularly nasty in folder view with more than 10 folders, Waze just doesn't let you search at all.

EDIT: This is on a 2017 Kia Optima with Android Auto from the factory, that warning is only removed if I put the car in Park.
[Xposed Framework Modules] agentdr8:
What are you connecting the phone to, a built-in AA or an aftermarket one? Sounds like a vehicle sensor is possibly overriding that one gearhead param.
[Xposed Framework Modules] DMCShep:
I think he's saying Android Auto as a dedicated app is now fixed, but when connected to a HU is not. This is to be expected as every HU ever has a "park sense" input wire connected to the shifter (or parking brake on manuals), whereas the app seems to go off of GPS and has a bit of tolerance.
[Xposed Framework Modules] agentdr8:
Ah, yes. I still haven't found where in the code AA reads in vehicle gear selector position. Overriding that would likely resolve the scrolling limitations while connected.
[Xposed Framework Modules] aryehzev:
I'm currently on Android Auto version 2.7.573954 on a Ford Fusion with Sync 3 and this isn't working. Do I need to downgrade my Android Auto version?
[Xposed Framework Modules] lilloscar:
I only use them for the powerAmp app, never had a problem with it, I use a modified android auto for the mazda connect (which didn't support AA yet)
[Xposed Framework Modules] agentdr8:
The current module version should be for that version of AA. If you can, please enable debug in the module settings and provide me the Xposed error.log.
[Xposed Framework Modules] agentdr8:
Updated the module for AA 2.8.57451x
[Xposed Framework Modules] eng3:
Does this still work on Nougat?

I tried it for the first time today.

The 6 tap limit didnt work. For example scrolling on the playlist to skip to a song. After 6 taps of the arrow it got locked. I could choose a visible song then immediately go back to hitting the arrow 6 times though.

I couldn't remember an action to try to test the parking (speed limit).

Also, I recall I use to be able to pull down on notifications, goto the app switcher, select an app, then hit the home button and I'd get the home screen. This time, I kept getting sent back to the Android Auto screen most of the time. It would also do that randomly while I was in another app. All my apps ran extremely slow and laggy.

Ironic, I was having such a hard time that I had to stop because it started feeling unsafe. Had they not had these blocking features, I could have completed the task in a fraction of time being much safer. Same with the 6tap thing.
[Xposed Framework Modules] agentdr8:
This should work on anything from LP and newer, as long as the Xposed Framework is functional. And the AA app itself determines whether or not you can get to other apps or the main launcher while it's running. Google really doesn't want you to browse on the phone while AA is running, but I believe they may lessen this restriction over time (possibly with the introduction of a Passenger Mode).

If you have debug enabled in the module, please post up the Xposed error.log and I can take a look to see if something isn't working right.
[Xposed Framework Modules] andresoid:
Hi,

Thanks a lot for the great job and efforts to solve the annoying 6-tap limitation!!

So, the thing is that it's also not working for me... Running Huawei P10 plus. Here some info that may be of your interest to debug the problem:

1.- XPosed framework running normally (88.2)

2.- Install SAAX module, activate, restart.

3.- Xposed framework still running normally.

4.- Change a couple of settings in SAAX: 999 taps limit, for example.

5.- Restart

6.- Xposed framework shows the following message: "The 88.2 version of the framework is installed, but not active. Please, review the logs for further details" (see attachment)

-- The logs are empty, even if that option is clicked --

-- Here comes something weird --

7.- De-activate SAAX

8.- Restart

9.- Xposed framework back to green :confused:

I hope that this might help to diagnose!

Best.
[Xposed Framework Modules] agentdr8:
Hmm, so the module is somehow interfering with the framework? I'll have to do some research to see if something is needed specifically to support Nougat.
[Xposed Framework Modules] andresoid:
Hi,

Some more information that might be of interest for debugging...

With saax activated, and then the framework complaining about it (claiming that it is not activated), I have installed other modules. In particular gravity box N . After this (and reboot), the framework itself complains no more, it's green again, gravity works fine, but unfortunately saax does not. Unfortunately there are no logs available...

Best.
[Xposed Framework Modules] agentdr8:
I'll get Nougat loaded on my dev m8 this weekend and try and figure out what's going on with the module. Thanks for the feedback.
[Xposed Framework Modules] agentdr8:
I loaded up my m8 with RR 7.1.2, official Xposed Framework 88.2 (arm), and AA 2.8.574513 and the module seems to load and function as expected.

The log within the Xposed Installer app shows the module loading and hooking the AA application, as well as overriding the settings per the preferences.

I'm not sure why it isn't working on your P10. I would suggest maybe uninstalling the SAAX module, and maybe try uninstalling/reinstalling the Xposed Framework.
[Xposed Framework Modules] andresoid:
Thanks for checking :good:

I've tryed that and it's also not working... I am researching a bit on the side of Xposed... There seems to be some problems with EMUI phones... When I find out how to fix it, I will post it here.
[Xposed Framework Modules] KnightJeep:
Samsung Galaxy S8

Sorry if this has been asked before. Do I require to root my device to test this on my phone?

Also is there a chance that this could break my phone?
[Xposed Framework Modules] agentdr8:
Let me link you to the 2nd post in this thread. You'll want to read up on the Xposed Framework, and what that entails.

And with any modifications, there's always the risk of something not going right. I can't guarantee it will or won't cause issues on your device.

As the saying goes, "Your mileage may vary."
[Xposed Framework Modules] DMCShep:
Yes. Yes. Samsung especially is nasty, the S8 only charges to 80% once rooted. I still haven't gotten MMS working on mine either, and with the hardware Knox thing, ugh, man if all you need is stuff from this one app look elsewhere. If you have a whole bunch of reasons like I do, worth checking the Q&A forum in the S8 section.

Going back a bit, any progress on this? Still an annoyance that hasn't been fixed yet on my end:

That's the single biggest sticking point with Android Auto for me, I am often pissing off my neighbors by parking at the end of my street and making them go around me because my car is dumb and I am continually forgetting.
[Xposed Framework Modules] baggar11:
Is this module possible on the Xposed v8.1 beta for Oreo?

Is this only for AA on phone or vehicle AA too?

I'm showing AA v2.9.574924-release. Anyone else running this module on that AA version?
[Xposed Framework Modules] DMCShep:
On vehicle Android Auto: this module doesn't yet fix its shortcomings (see second quote in the post right above yours for last update on that). Phone Android Auto, I was snagged today with Waze in the back seat, I will check again though -- I have since rebooted which I don't do often, but I'm on 7.1 Nougat Galaxy S8 on T-Mobile for reference. Need to upgrade to Oreo soon (Meltdown/Spectre), glad to hear Xposed is available, on my "to do" list!

I still say this is the most basic of functionality that should be bred into Android Auto from the start. Shame this module even needs to exist, but glad it does and makes an effort to fix this glaring flaw. Good on dev!
[Xposed Framework Modules] agentdr8:
I haven't loaded Xposed yet on my Pixel, but I can't imagine it not working. There's nothing version-specific about the module, as long as the device supports Android Auto (5.0+). If anyone discovers that this isn't the case, I can definitely look into why.

I too noticed a new release of AA, so I'll have to update the module to account for it. I should have the update up before the end of this week.

I wholeheartedly agree. But I can't see Google ever putting themselves into a position where someone could sue them because they didn't have any usage restrictions.
[Xposed Framework Modules] baggar11:
Thanks! If you need any debug logs to help improve the vehicle AA side of things, let me know. Should be no problem.
[Xposed Framework Modules] DMCShep:
Not to sound like I'm starting an argument (I've added this part after re-reading and sounding too abrasive for my own tastes), apologies if I come across harsh: Waze? I mean every HU ever, aftermarket or OEM, displays a full-page warning, Android Auto could easily do the same. They choose not to let anyone use Android Auto while making a lawsuit even easier when you're using Waze by avoiding the legaleze entirely.

I hate to be "tin foil hat" but with the way YouTube is going, I'm too dumbfounded by how Google is handling anything anymore to make things as simple as they ought to be. Probably deeper reasons why Android Auto keeps forcing this crappy methodology on us. I don't care though, I just hope you can find where the Parking Sense Wire input is read on the device soon! Getting to the point of considering car modifications to accomplish the same thing in wiring!*

* Every forum ever says don't talk about this, so don't ask
[Xposed Framework Modules] agentdr8:
I don't think it came across as an argument. I found the reason for the initial 6-tap limitation; NHTSA guidelines. Back in 2012, they came up with Phase 1 of the proposed guidelines for built-in infotainment systems, and recommended that any interactions that required touch or keypress input be completed in 6 inputs or less. See page 136, section V.5.f of the guidelines. Leave it to the government to think they know what's best for everyone. Of course these were/are only recommendations, and OEMs didn't have to comply or even follow them. Google made the decision voluntarily for Android Auto, even though Apple didn't for CarPlay (go figure!).

So I can't imagine Google ever undoing this restriction in AA, unless the NHTSA recommendations change.
[Xposed Framework Modules] 911jason:
Not working for me.
[Xposed Framework Modules] agentdr8:
Can you provide the Xposed error.log?
[Xposed Framework Modules] 911jason:
Attached. I changed .log to .txt so XDA would accept it for upload.
[Xposed Framework Modules] agentdr8:
Thanks. I see what the issue is and will get a fixed version up later today.

EDIT: See new version on OP/repo.
[Xposed Framework Modules] 911jason:
No change. Log attached as text file.
[Xposed Framework Modules] agentdr8:
The module is properly loading now at least. Can you enable debug in the module preferences and restart your device? Then plug it into your headunit and provide the error log?
[Xposed Framework Modules] 911jason:
I did all that before I posted. I'm at work now, but I can do it again later if you think it would help.
[Xposed Framework Modules] agentdr8:
I'm not seeing any output in the log from when the module is hooking the Android Auto package. Usually if debug is enabled, it starts filling up the log with info about overriding values, once AA is running.

You do this without connecting it to your vehicle. Just run AA on your phone, and then look in the Xposed Installer -> Log and see if SAAX is outputting any lines.
[Xposed Framework Modules] 911jason:
The log is not updating at all. I clicked reload. I started AA, went to music and scrolled recent activity until it locked, shut down AA, checked the log, nothing, did it again, still nothing. AA had been running for 7 minutes when I took that screenshot of the log.
[Xposed Framework Modules] agentdr8:
Hmm, something isn't right. I'll try and get Oreo and Xposed loaded on my m8 test device this weekend and sort it out.
[Xposed Framework Modules] feffrey:
I'm having the same issue after switching phones.

Essential phone running LineageOS 14.1, Android version 7.1.2.

Nothing in the Xposed logs for SAAX with debug on.
[Xposed Framework Modules] :
So there it is. I wonder how many other manufacturers follow this. The rest of my radio doesn't limit taps. I'm willing to bet my life this will never apply to FM in the US, the 5 companies that own the stations and the RIAA would lose their minds.
[Xposed Framework Modules] ema987:
Same for me unfortunately, warning is still displayed and doesn't let me scroll. Xposed log is empty

Android 7.1.2 oxygen OS on OnePlus 3

edit: it works now! Not sure why it didn't work the first time, but I haven't change anything since then, so probably for some reason the xposed module wasn't loaded.

Thank youuuuuu!!
[Xposed Framework Modules] XDAUser1234:
Using this on a Pixel 2 (8.1) with Xposed 90-beta3, and cannot get it to do anything. Enabled logging as well, and the logs were blank.
[Xposed Framework Modules] DMCShep:
(Just saw this, email notifications got very delayed it seems)

Wait, I thought in-dash was yet to be fixed at all? Phone Android Auto doesn't have the click limitations, but my in-car most certainly still does, just ran into it yesterday even. Last I heard you were having trouble finding the gear selector code. Have you found it yet? If it should work, mine isn't, and I can most definitely provide error/debug logs for you. Let me know.

I did just see something about "content rate limiting" that was still not activated yet on the settings screen for your module, no clue what that does but activated it and logging just in case.

Rooted S8 on T-Mobile running Nougat 7.1
[Xposed Framework Modules] vlucchetti:
Just installed 1.78 but unable to access settings since the app isn't showing in the app drawer like other xposed modules.

Log not showing it installed but shows installed under framework (90.1-beta 3 systemless).

Android auto version 2.9.574924

Pixel XL (8.1)
[Xposed Framework Modules] XDAUser1234:
So...it seems the module might be doing something, somewhere, though I don't think as intended. Just opened Waze at my desk to check how long it would take me to get somewhere, and it immediately popped up with the driving warning to ask if I was the passenger. When I disabled the module and rebooted, I didnt get the passenger warning.

Also, still nothing in the log, and also also - if I read a post up above correctly, is this only intended to work with Android Auto as a stand alone app running? And *NOT* with the in-dash car integration? If so, that was just a misunderstanding on my part!
[Xposed Framework Modules] DMCShep:
In Xposed itself, go to Modules, long-press SAAX --> Launch UI. I never use the app drawer if I can help it as it's a cluttered mess for me ;)

Waze or Android Auto? I think maybe there's confusion on that. This module addresses Android Auto, not specifically Waze (however Waze is compatible with Android Auto and does work within it). If you pull up Waze independent of Android Auto, the passenger warning still shows if it detects movement (such as when you first enable GPS and it hones in on your location). If you open Android Auto first and then navigate to Waze within, this module kicks in.

But last I knew he hadn't figured out where the code was phone-side that determined if the car was in park or not, and until he knows where it is, he can't bypass that "browsing locked for safety" message that happens on six taps, so his debugging of that exact scenario seemed odd to me, like maybe something changed on that front. The goal with this module is to hopefully work both in-dash and on-phone, but until the gear selector code is found, perhaps the most annoying things can't be fixed, being dependent on allowing more than six taps.
[Xposed Framework Modules] vlucchetti:
Thanks, that seems to have worked. Will link to the car and check it out. Never thought to do that.
[Xposed Framework Modules] DMCShep:
To be fair I only learned that trick after a few other Xposed modules did the same thing and left me wondering how so many features were installed but not really. I think one of the ad blocking ones does it (YouTube maybe?)
[Xposed Framework Modules] agentdr8:
I still haven't had a chance to load up my test device with Oreo. I'll hopefully get to it this week, and figure out why the module isn't showing as loaded in the logs (and verify that it's actually loaded and doing stuff).

And the vehicle sensors bypass is still an outstanding item. I've combed through quite a few classes but nothing has stood out as far as injection/modification points.

TBH, I have no idea what content rate limiting does, or the majority of the gearhead-specific parameters within the AA package. I just assumed that anything that does limiting is a bad thing, and why not flip the boolean to see if it helps. There's a good chance it doesn't do what I think it does.
[Xposed Framework Modules] DMCShep:
You rang? :p

I mean I am a six-year C# veteran, if a name doesn't make sense, I can probably make out more about what it means than the average joe. That one I think I've seen before, maybe more on a global Android approach? If it were an integer, it would be "milliseconds before you can toast again" or something similar I'd imagine. As a boolean, probably similar to "currently throttled" or "enable throttling" would be my guess.

Always wanted to get into some of the more nuanced styles and open source projects as well, I need to start looking into Xposed coding more.
[Xposed Framework Modules] vlucchetti:
Whatever it is, I thank you for the tip!
[Xposed Framework Modules] agentdr8:
I got 8.1 loaded up on my m8 and the module seems to be loading and injecting into the AA process like it has in previous versions:

02-14 19:34:57.891 I/Xposed ( 276): -----------------
02-14 19:34:57.891 I/Xposed ( 276): Starting Xposed version 90-beta3, compiled for SDK 27
02-14 19:34:57.891 I/Xposed ( 276): Device: m8 (HTC), Android version 8.1.0 (SDK 27)
02-14 19:34:57.891 I/Xposed ( 276): ROM: lineage_m8-userdebug 8.1.0 OPM1.171019.018 1b2c2eaf3c test-keys
02-14 19:34:57.891 I/Xposed ( 276): Build fingerprint: htc/m8_google/htc_m8:6.0/MRA58K.H6/648564:user/release-keys
02-14 19:34:57.891 I/Xposed ( 276): Platform: armeabi-v7a, 32-bit binary, system server: yes
02-14 19:34:57.891 I/Xposed ( 276): SELinux enabled: yes, enforcing: yes
02-14 19:34:57.912 I/Xposed ( 276): -----------------
02-14 19:34:57.913 I/Xposed ( 276): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
02-14 19:35:01.054 I/Xposed ( 276): Detected ART runtime
02-14 19:35:01.058 I/Xposed ( 276): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
02-14 19:35:01.814 I/Xposed ( 276): Loading modules from /data/app/com.dr8.xposed.saax-NfJZ_suByBlgl4MeFHGjrw==/base.apk
02-14 19:35:01.828 I/Xposed ( 276): Loading class com.dr8.xposed.saax.Xposed
02-14 19:35:21.423 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : Hooked Android Auto package
02-14 19:35:21.619 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:max_forward_clicks is currently: 6
02-14 19:35:21.620 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : setting gearhead:max_forward_clicks to 999
02-14 19:35:21.624 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:content_rate_limit_enabled is currently: true
02-14 19:35:21.625 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : setting gearhead:content_rate_limit_enabled to false
02-14 19:35:21.636 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:feature_vanagon_unlimited_browse_speed_bump is currently: true
02-14 19:35:21.637 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:feature_vanagon_unlimited_browse_speed_bump is now: false
02-14 19:35:21.643 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:max_parked_speed_wheel_sensor is currently: 0.5
02-14 19:35:21.646 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : setting gearhead:max_parked_speed_wheel_sensor to 67.056
02-14 19:35:21.647 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:max_parked_speed_gps_sensor is currently: 1.5
02-14 19:35:21.649 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : setting gearhead:max_parked_speed_gps_sensor to 67.056
02-14 19:35:21.655 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : gearhead:passenger_mode_feature_enabled is currently: false
02-14 19:35:21.658 I/Xposed ( 1631): [2018-02-14 19:35:21] SAAX: : setting gearhead:passenger_mode_feature_enabled to true
[Xposed Framework Modules] DMCShep:
The first two seem entirely relevant, if not already addressed (passenger mode has a checkbox by the same name at least), the third I don't know what it is, and the fourth...

That fourth one is lock screen stuff I believe, which I think means that Android Auto won't let anything else happen if you're running it, a "feature" I despise. On my Kia anyhow, as Bluetooth is still active after you've exited and locked the car and walked away. Google didn't consider the stupidity of OEM's, and Kia goes a level above the rest on some fronts, that being one of them. Why are you routing my calls to a radio that's off again? So I can't text my wife that I made it to work safely? Thanks pal. I am at least glad the default is "false" and had been wondering about it as it wasn't acting up recently. Seems Google wisened up a bit on that one.

Anyhow, recognized the rest and saw nothing else related. Are you able to dive through code on this to determine if max_clicks is pulled from settings or just a constant? I'm wondering if it's even grabbing the limit from there at all.

I'll take a look at GitHub code soon, would love to contribute if I can!