segflaunt Just to make sure I fully understand what fixed it, was it disabling the secure app spawning toggle?
That's peculiar if so, but I'm glad to hear it worked.
segflaunt Just to make sure I fully understand what fixed it, was it disabling the secure app spawning toggle?
That's peculiar if so, but I'm glad to hear it worked.
matchboxbananasynergy I can confirm MyQ is now working on my 6a. Thank you, sir/ma'am!
segflaunt Since you've mentioned you're on Matrix, could you please DM me the logs at @matchboxbananasynergy:matrix.org
?
Ideally, the app should work without the need to disable secure app spawning. There might be something that the app developer needs to fix.
matchboxbananasynergy duplicating verification here, but for the benefit of anyone else with the issue / interested in the solution, it sure was.
I have toggled it back and forth confirming that is the difference. The app must have some issue with running in that environment. Maybe putting its grubby fingers where they do not belong. Who knows.
I am on the Pixel 7 Pro, I have the "Settings > Security > "Enable Secure App Spawning" Enabled as I have never disabled it. I am trying to help my uncle get myQ working on his p6p and he had issues until reading this thread to disable this feature.
I am posting to express that this may appear to fix it but there must be a different issue as it works flawlessly on my p7p (google profile-3rd/profile) when keeping the feature enabled. If this thread ever continues I am willing to help on my end if there is anything I can do.
This allowed my MyQ to work on my p7p as it was not working before.
https://grapheneos.org/usage#exec-spawning
Secure app spawning is a global (system-wide) switch and disabling it will negate security benefits it brings. So I would tread carefully here. Is it really worth to you disabling it for a feature that you don't use every 5 minutes?
Running Grapheme on Pixel7. You have to keep secure app spawning turned off for MyQ to work fully. If you open it and then turn back on secure app spawning, some functions in the app don't workcand then as soon as you reboot the phone, you're back to square one. And if you're going to leave secure spawn off, why install grapheme in the first place? All the other IOT apps I have installed are able to work with secure spawn turned on, so the MyQ devs need to figure out why their code is buggy and fix it. Until then, I'll just have to use the garage remote like a freaken' normal person.
Just FYI tried the steps above and have not had success logging in. Get an error after login "Error 401.122" from the app. I will try to contact their support to request they make it compatible.
Pixel 7a, Secure App Spawn disabled, Reinstalled app, Exploit protection compatibility enabled, All permissions given.
tarv
I'm having the same problem/error. Did you come up with anything?
I'm looking at a hardware solution... Ratdgo plus Hubitat, but I need to do more research.
I know this is late, I had the same issue with the MyQ app. I had to disable app spawning in settings and this worked. Also, you must have G services installed or the app will not work, period.
ozzmanj1
yeah, i have g services installed in the main profile along with the app. turned off app spawning. rebooted, etc..
just can't get it to work. did some searching and found someone who (on lineage) got it to work with an older version of the app but i have not been able to duplicate his success. not the same os, of course, but just fishing..
are you still using myq, or was this a while ago?
I'm in a similar situation with Bbiscuit_tosser_88. Installed MyQ on the main profile of my Pixel 6 Pro with secure app spawning disabled, reinstalled the app, and turned on exploit protection compatibility mode. Nothing helps. Always "error 401.122". I'm beginning to think they're checking for MEETS_STRONG_INTEGRITY, as per this thread.
PacoBell
I eventually gave up on MyQ. I was not happy with them after they dropped API support for 3rd party integrations and how they messed up their main app screen with marketing junk.
I use an automation hub at home and have different z-wave devices connected. Light switches, dimmers, etc.
In a nutshell, I bought a z-wave relay online and connected it to a spare garage door remote. I cancelled my MyQ account and now I can control the door and get alerts through my hub, right to my phone.
I'm more comfortable not being connected to that company.
I suppose that's for the best. I just called their support and got a script monkey that insisted that the only way I would be able to get the app to work on my phone would be to install another third-party OS that's capable of running rooted. I shit you not. I had to clarify that point three times over the phone just to make sure I wasn't understanding that incorrectly. They only want to talk to Google-blessed OSes, but don't want to admit it publicly.
biscuit_tosser_88 Are you willing to share a link or two that describes your setup? I just installed the myQ app on a pixel6a GrapheneOS device, and am getting the 401.122 error, too. I would be very interested to go "off app" as you describe, and would like to know more about the automation hub and z-wave device connection, as you describe. Thanks for any help you can send my way.
Just here to add another 2024 me too. Error 401.122 after entering login credentials.
I am having the same exact problem as above.
I also remember reading this thread a couple of years ago on Android 14 and the secure app spawning was able to be changed and settings under privacy on a different profile.
For some reason on Android 15 it's impossible to change. It's missing. Had to log into my owner profile under Settings Privacy, exploit protection and change it there.
Tried giving the app all permissions plus turning off secure apps spawning.
Deleting and reinstalling the application didn't help.
I am able to use the application on my Pixel 7 Pro but on the Pixel 9 Pro XL I am getting the same exact error
I have noticed that on my Pixel 9 the app version is different though. (Newer version)
Also on my P9ProXL the myq application is on a different profile, same as on my Pixel 7 Pro.