Related
Does anyone here have a chromebook they use with their Oneplus 3?
I got a chromebook recently and can't pair the OP3 to the chromebook, and as a result can't use Smart Lock to unlock the chromebook by unlocking the phone. Am I doing something wrong or is the chromebook or the phone the issue?
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Anova's Origin said:
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Click to expand...
Click to collapse
Are you on stock OOS?
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
peterk-1 said:
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
Click to expand...
Click to collapse
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
2x4 said:
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
Click to expand...
Click to collapse
Sorry - I missed the point in my explanation. I should have made clear the "trusting" doesn't work in either direction. In the case of attempting to set up any device to unlock a Pixel C, the Pixel C menu Smart Lock > Trusted devices doesn't open to BT / NFC options but instead gives an "error" message " Trusted devices feature is not available to use". This has been the case with Android M and N so it has been suggested that this is a hardware restriction. The relevance? - Pixel C started life designed as a Chrome device. Another suggestion is that there is a coding error and GPS has been included as a requirement - I doubt this since trusted locations works.
2x4 said:
Are you on stock OOS?
Click to expand...
Click to collapse
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Anova's Origin said:
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Click to expand...
Click to collapse
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
2x4 said:
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
Click to expand...
Click to collapse
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
yes it is up to date
2x4 said:
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Click to expand...
Click to collapse
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
MrWilsonxD said:
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
Click to expand...
Click to collapse
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
2x4 said:
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
Click to expand...
Click to collapse
My pleasure. I doubt it's a problem with the CBP. Probably something to do with oxygen OS unfortunately.
added a new user to the chromebook today, and enabled smartlock with her phone (Nexus 6P) with zero issues - it's definitely the Oneplus 3.
i'm current on freedomOS community beta version. not sure what the issue is...
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
F4uzan said:
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
Click to expand...
Click to collapse
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
2x4 said:
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
Click to expand...
Click to collapse
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
F4uzan said:
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
Click to expand...
Click to collapse
tried a clean flash of the ROM I'm currently on (FreedomOS based on OOS beta), and the issue still persists.
I'd be open to using another ROM but haven't ever had a reason to switch and I like the optimal camera performance with OOS
just tried a clean flash of lineage OS (https://forum.xda-developers.com/oneplus-3/development/rom-t3532088) - smart lock STILL didn't work (I keep getting the "can't find your phone" error message)
what specific ROM(s) did you see it work on @F4uzan ?
Early this morning, out of the blue a notification popped up on my 3XL running DU that the device can no longer be used for contactless payment. Checked Magisk to find CTS failing along with the same contactless message if I open GPay. Checked Props to be sure I still had the 3XL fingerprint running, which I did. Checked my wife's stock/rooted P3 to find no issues with either SafetyNet or GPay. I even tried a P3 Android 11 fingerprint on mine with no change to the failure. The only thing I can think of is that the 3XL had hardware attestation turned on, but surprisingly I have seen no other comments today.
Anyone else see anything similar or have any thoughts?
sliding_billy said:
Early this morning, out of the blue a notification popped up on my 3XL running DU that the device can no longer be used for contactless payment. Checked Magisk to find CTS failing along with the same contactless message if I open GPay. Checked Props to be sure I still had the 3XL fingerprint running, which I did. Checked my wife's stock/rooted P3 to find no issues with either SafetyNet or GPay. I even tried a P3 Android 11 fingerprint on mine with no change to the failure. The only thing I can think of is that the 3XL had hardware attestation turned on, but surprisingly I have seen no other comments today.
Anyone else see anything similar or have any thoughts?
Click to expand...
Click to collapse
Fails for me also on DU.
mgp53 said:
Fails for me also on DU.
Click to expand...
Click to collapse
I assume you had been passing using the fingerprint module before? Also, I wonder if the 11 kernel on my wife's (EX) is hiding the unlocked BL while the 10 kernels are not.
sliding_billy said:
I assume you had been passing using the fingerprint module before? Also, I wonder if the 11 kernel on my wife's (EX) is hiding the unlocked BL while the 10 kernels are not.
Click to expand...
Click to collapse
Can't answer that as I wasn't using gpay. I tried setting it up and ran into the same problem. I am using the fingerprint module and still not able to pass.
mgp53 said:
Can't answer that as I wasn't using gpay. I tried setting it up and ran into the same problem. I am using the fingerprint module and still not able to pass.
Click to expand...
Click to collapse
Hard to believe that you and I are the only ones seeing this (including other custom rom users). I really don't want to go to 11, but it might be a thought until DU puts out 15.
I have had the same issue since mid-Septembers update for LineageOS though on my 3XL. CTS fail and GPay fails. However, CTS passes fine on my Galaxy Tab A running the same LineageOS versions but I don't use GPay on that so can't confirm it's status.
rspkt said:
I have had the same issue since mid-Septembers update for LineageOS though on my 3XL. CTS fail and GPay fails. However, CTS passes fine on my Galaxy Tab A running the same LineageOS versions but I don't use GPay on that so can't confirm it's status.
Click to expand...
Click to collapse
That helps that it is not DU specific but custom rom on 3XL specific. My Tab S2 running LOS 16 is fine like your Tab A, but again no GPay on there.
sliding_billy said:
That helps that it is not DU specific but custom rom on 3XL specific. My Tab S2 running LOS 16 is fine like your Tab A, but again no GPay on there.
Click to expand...
Click to collapse
That's the same conclusion I came to as well. I'm curious whether this affects a stock Android 10 install on a 3XL with just Magisk installed and nothing else? I never tried it on either my phone or my tablet to see how that would pan out. Maybe one of us should just to see? What do you think about that theory?
rspkt said:
That's the same conclusion I came to as well. I'm curious whether this affects a stock Android 10 install on a 3XL with just Magisk installed and nothing else? I never tried it on either my phone or my tablet to see how that would pan out. Maybe one of us should just to see? What do you think about that theory?
Click to expand...
Click to collapse
Definitely a good idea to see if it is an A10 issue regardless and to see if it follows different custom kernels, etc. I am guessing most everyone who has read this is either on 11 or a 10 custom ROM. I am still thinking of going to stock 11 until custom 11 ROMs start popping up, and doing an intermediate install of 10 would only add a little bit of time. I am just a bit up against it to put the time into a full reconfig of my phone just to solve a GPay issue. Nothing else that I use is impacted by the CTS fail, and since all the GPay issues started a a couple of years ago, I think everyone (myself included) has a credit card ready just in case when using contactless. Not sure if I care enough, but that could change if I get some free time.
Got SafetyNet to pass and GPay to get rid of the contactless failure. My wife's P3 kicked to device attestation last night and failed SafetyNet, though strangely didn't show the contactless error. Either way, I decided to mess with bith of them this morning. The P3, I selected the 4a fingerprint (she had no other fingerprint set) and then after reboot did a force basic. After another reboot, it was passing SafetyNet and still showed no issues with GPay. For the 3XL, I had to do a completely reset of the props/fingerprint module (which in my case also reset a custom prop I had set) to get rid of my 3XL fingerprint. Reboot , change to 4a fingerprint, reboot, re-add my custom prop and another reboot. No need to force basic since it never changed to device attestation. Everything is passing now. Need to physically check GPay at a store, and who knows how long the 4a print will continue to pass, but for now all is working.
.
As per the thread title, has anyone successfully gotten any of the streaming apps to work on Android Auto that has root? I was thinking that I would be able to get it working once I had root but that's not the case. I can get them working on my Galaxy or LG devices (both unrooted) just fine but not on my pixel which has root
Android 12 and recent AA versions seem to break screen mirroring apps. Haven't tried CarStream or similar.
LLStarks said:
Android 12 and recent AA versions seem to break screen mirroring apps. Haven't tried CarStream or similar.
Click to expand...
Click to collapse
I haven't been able to get anything working including car stream, fermata, car tube. Absolutely nothing is working. I was hoping someone here has figured out the trick with having root to make it happen
Negan said:
As per the thread title, has anyone successfully gotten any of the streaming apps to work on Android Auto that has root? I was thinking that I would be able to get it working once I had root but that's not the case. I can get them working on my Galaxy or LG devices (both unrooted) just fine but not on my pixel which has root
Click to expand...
Click to collapse
Did you properly set up Zygisk (-> Enforce Denylist)? And set up Universal SafetyNet Fix?
I do not use Androidauto, but all the apps I'm using (banking, security, google pay etc) work without a problem once Zygisk is properly set up.
Yes but it's not likely a safety net thing though
The stream2auto and AA Tweaker threads have some clues. But I've not tried them myself.
I've been able to recently get stream2auto working for one day by uninstalling AA and installing version 6.9.613744. Lost it next time I tried to use it. Also needed to clear app data for AA and Google Play services. This is due to a combination of AA and Google Play Services doing their best to remove third party apps from AA.
I've seen some suggestions for using LuckyPatcher to rename screen2auto. Also seen some for detaching AA from the playstore, but have not tried those for a more permanent. Read through the links posts/threads for more insight.
https://forum.xda-developers.com/t/...te-android-auto-utility.4194239/post-86087981
https://forum.xda-developers.com/t/...g-only-for-root-devices.4062787/post-84806229
Screen2Auto and AAStream suddenly started working for me. You still have to install with AAEase or AAAD.
Android Auto 7.3.120444
LLStarks said:
Screen2Auto and AAStream suddenly started working for me. You still have to install with AAEase or AAAD.
Android Auto 7.3.120444
Click to expand...
Click to collapse
Lucky you. I was able to get those to install and both show up in AA but fc when trying to launch. AA 7.1.614574. will try updating to that version and see but I'm not optimistic.
Interestingly enough yesterday when I started AA I got that warning that happens every so often where AA doesn't start and makes you have to stop and agree to the terms again and everything started working again. Idk if it's just luck or there's something to it but what I did was used AAAd to download catstream 2.05 and the AA Aio tweaker app to patch catstream and it works... For now
HI,
does anyone know how to get the Spectrum TV app working with root? Atm I'm running OOS 11with Magisk and I always get the error in the screenshot. I've always tried the deny list and still get this error. I've Google for an hour with no luck.
The_Keeper86 said:
HI,
does anyone know how to get the Spectrum TV app working with root? Atm I'm running OOS 11with Magisk and I always get the error in the screenshot. I've always tried the deny list and still get this error. I've Google for an hour with no luck.
Click to expand...
Click to collapse
Contact the app developer and ask them if they can add the phone to their support list. I mean, it's not a ROOT issue as per your screenshot.
Spectrum TV won't work if you have USB debugging on. Also, it unticks in Magisk's Deny List whenever you reboot. I would make sure both of those are taken care of, then clear all data from the Spectrum app, reboot, open Magisk and retick Spectrum in the Deny List, and then try to open the app.
Thank you both for replying! I tried all of that and still same issue. I guess I'll try contacting the app developer. I'm surprised this phone hasn't been added to the supported devices list. I was just hoping someone here had the 9 pro as well and had experience with the Spectrum app.
Maybe it would be possible to trick the app into thinking I have a Galaxy or something? Obviously those are supported. Probably too much trouble though lol.
I have a OnePlus 9 Pro, running C48, rooted with Magisk 24.3, and the Spectrum TV app works for me, using Deny List and the Universal SafeNet Fix. Do you subscribe to Spectrum as your wifi or cable provider? It used to be that the app wouldn't work unless you were connecting to the same wifi (or in the same area, if using mobile data) that you are obtaining from Spectrum. Not sure if that still applies, though.
rogerinnyc said:
I have a OnePlus 9 Pro, running C48, rooted with Magisk 24.3, and the Spectrum TV app works for me, using Deny List and the Universal SafeNet Fix. Do you subscribe to Spectrum as your wifi or cable provider? It used to be that the app wouldn't work unless you were connecting to the same wifi (or in the same area, if using mobile data) that you are obtaining from Spectrum. Not sure if that still applies, though.
Click to expand...
Click to collapse
I subscribe to their internet and cable service. It used to work on my Oneplus 7 Pro which was also rooted. I've only had this phone since February. I tried the universal safety fix just now and re added Spectrum to the deny list but same thing unfortunately :/
*edit* I've noticed Spectrum TV keeps ubchecking itself from the deny list even without rebooting.
Did you force stop the app, then clear its cache and data, reboot, retick Spectrum in Magisk's deny list after rebooting, and then try the app?
rogerinnyc said:
Did you force stop the app, then clear its cache and data, reboot, retick Spectrum in Magisk's deny list after rebooting, and then try the app?
Click to expand...
Click to collapse
Yeah, I tried all of that. What actually worked I found out about a module called Shamiko installed that and rebooted and tried the app again and it's working! Hopefully it stays working lol.
They do stupid things like this and they wonder why people turn to piracy...
EtherealRemnant said:
They do stupid things like this and they wonder why people turn to piracy...
Click to expand...
Click to collapse
Totally agree with that!
The_Keeper86 said:
Yeah, I tried all of that. What actually worked I found out about a module called Shamiko installed that and rebooted and tried the app again and it's working! Hopefully it stays working lol.
Click to expand...
Click to collapse
Hey are you by any chance still running it this way? I'm on a Moto G Power 2020 but I can't find any combination of anything that works. Shamiko, with deny list on or off (it says it doesn't work with the list enabled but that seems contrary to what we're trying to do with it) Nothing either way. USB debugging is off, Magisk app hidden. Still getting the Spectrum error. Somehow it knows anyway . All I can really think of is that Viper4Android is also running but that's a deal breaker as it's the whole reason I bought this phone in the 1st place, which was to be a dedicated music/podcast player and navigation phone for work. I'd just use the stock Pixel 6p I have for TV casting otherwise.
-- Edit -- Scratch that sorry I got it to work finally. I wasn't rebooting after disabling the enforcement list and trying with Shamiko module running. It works in that config now. Though I also installed kdrag0n Universal Safety Net fix as well so maybe that combo helped? Either way it did the trick finally and I don't have to worry about Viper being in the mix. Viper works (yes Neon enabled yes processing showing) while using SpectrumTV btw. In case anyone is wondering.
You don't need the universal sfn fix. I use shamiko and denylist in zygisk and every app and game works as intended for me. Fully passing SN. Only thing I don't have is L1, but I could give two butts less about that.
Anybody able to use any sports book app on a custom rom. Seems to trip the geolocation part of the app. Staying on unrooted A11 stock for this reason.
kjslabber said:
Anybody able to use any sports book app on a custom rom. Seems to trip the geolocation part of the app. Staying on unrooted A11 stock for this reason.
Click to expand...
Click to collapse
Yeah I had the same problem. Using magisk denylist worked for me but then the geolocation flagged my device and now can't use that sportsbook anymore because they banned me for it
I think I found the problem. It was the encryption security in my wireless router. Just logged into the router using my PC and turned off the security, rebooted router and it works now. Non-rooted extend A13 running now and FanDuel geolocation works.