Guys, so I rooted my phone while ago and installed some stuff over magisk. I recently realized that my model changed from OnePlus whatever, to Pixel XL. Is this normal?
Ah **** I kinda hoped he wouldn't notice.....f&ck!!!
-OP's 5T
When flashing LinageOS + Google Apps to my 5T yesterday, during the initial setup my phone was referred to as a Pixel XL on the Google part of the setup.
However when looking in settings the phones model is "OnePlus A5010", I can't find anywhere else its referred to as a Pixel XL though.
You probably installed a magisk module for daydream vr or something similar, it usually changes this entry in the build.prop but I found that it works without changing the model name.
M.Sami said:
You probably installed a magisk module for daydream vr or something similar, it usually changes this entry in the build.prop but I found that it works without changing the model name.
Click to expand...
Click to collapse
This wouldn't affect anything, right? Does it really matter if that changes?
Kristyshaker1095 said:
This wouldn't affect anything, right? Does it really matter if that changes?
Click to expand...
Click to collapse
Just make sure the device is certified on the play store, otherwise you should be fine
M.Sami said:
Just make sure the device is certified on the play store, otherwise you should be fine
Click to expand...
Click to collapse
Oh. Okay. Thanks a lot, mate! ?
Related
have anyone try the pix3lify module from magisk in pie?
ledio456920 said:
have anyone try the pix3lify module from magisk in pie?
Click to expand...
Click to collapse
If you decide to try let me no as im interested that.
ledio456920 said:
have anyone try the pix3lify module from magisk in pie?
Click to expand...
Click to collapse
Hello,
I used it on pie and it is sympathic But GAPPS are required and it's so bad
Pierre
Pierre_C said:
Hello,
I used it on pie and it is sympathic But GAPPS are required and it's so bad
Pierre
Click to expand...
Click to collapse
What do you mean Gapps are required and why is that bad
Ive tried it, it works ok, but theres a few google apps that arent in the zip, that have to be in system or privapp, i think that is what he means
Yeah i tested it on OnePlus 5t most of the stuff is working.
Good just for accent color and notification style
Many of its features not working and don't know why
I used it on Stock Pie rom, makes the phone a whole lot more usable. But I'd suggest you to use the slim version, the full version makes Photos app recognize your phone as a Pixel device which is not xD Therefore caused me some backup issues back then. Slim works great though ( On Pie )
marstonpear said:
I used it on Stock Pie rom, makes the phone a whole lot more usable. But I'd suggest you to use the slim version, the full version makes Photos app recognize your phone as a Pixel device which is not xD Therefore caused me some backup issues back then. Slim works great though ( On Pie )
Click to expand...
Click to collapse
Which features will I get in a slim version?
gkornaks said:
Which features will I get in a slim version?
Click to expand...
Click to collapse
You get rounded corners and Google Call Screening (which didn't work properly last time I tried) also Google's sound picker in settings (which also crashes lol). Maybe some other stuff too I'm not sure. Oh also your device identifies as Pixel again and Photos app shows a message that you had unlimited storage on cloud but your time has passed so you can only store images/vids at high quality (same as Full package of Pix3lify - doesn't mess the Photos app either in full or in slim package, sorry for the confusion). I love rounded corners myself but don't love it as much as rooting and not being able to get updates (although we still don't get updates, thanks Xiaomi ) So I just install Google Sounds apk from apkmirror and use unrooted stock ROM right now. Cheers.
EDIT: For more info check: https://forum.xda-developers.com/apps/magisk/module-pixel-2-experience-t3757137
marstonpear said:
You get rounded corners and Google Call Screening (which didn't work properly last time I tried) also Google's sound picker in settings (which also crashes lol). Maybe some other stuff too I'm not sure. Oh also your device identifies as Pixel again and Photos app shows a message that you had unlimited storage on cloud but your time has passed so you can only store images/vids at high quality (same as Full package of Pix3lify - doesn't mess the Photos app either in full or in slim package, sorry for the confusion). I love rounded corners myself but don't love it as much as rooting and not being able to get updates (although we still don't get updates, thanks Xiaomi ) So I just install Google Sounds apk from apkmirror and use unrooted stock ROM right now. Cheers.
EDIT: For more info check: https://forum.xda-developers.com/apps/magisk/module-pixel-2-experience-t3757137
Click to expand...
Click to collapse
Thank you!
Google quietly discontinued Daydream VR with the Pixel 4. If you have an existing Daydream VR viewer, it's useless with your Pixel 4. Fortunately, with root, we can re-enable support. While Daydream VR and phone-based VR in general are dying out, you can still use existing services like YouTube VR and other VR apps.
How to Install
Flash the Magisk Module attached to this thread and reboot.
Install Daydream from APKMirror.
Install Daydream Keyboard from APKMirror.
Note: If you don't hear any audio in Daydream, try running the following command in a rooted shell:
Code:
setprop persist.audio.vr.enable true
My Magisk Module should have already set this value, though.
Thanks, I was looking into getting one of those for YT, so I appreciate it!
Thats awesome thank you. And its nice thats its still a Pixel 4 in settings and not changed to Pixel 1 like other modules do.
Goofy19882 said:
Thats awesome thank you. And its nice thats its still a Pixel 4 in settings and not changed to Pixel 1 like other modules do.
Click to expand...
Click to collapse
Yeah, I wasn't satisfied with how a bunch of other modules were adding so much unnecessary stuff. This has just the bare minimum needed to get it working.
this works great! I can't use google photos though
Works great, thanks!
Anyone else notice there seems to be pixel ghosting? My original Pixel XL seemed to have hard time rendering smoothly, however movement had text semi readable, when still it was good.
However on my Pixel 4 XL, even slight movement makes text a blurry mess. Anyone know if this is an issue with display technology, or if it is a setting to fix?
I already tried:
force 90hz via developer settings
disable battery optimization for VR services, Daydream, Daydream Keyboard, and "Basic Daydream"... not sure what that last one is, but figured worth trying to disable battery optimization for that too, but no change, still blurry text at even very slight movement.
I appreciate this sharing
Thank you for this. Who in the world would have thought Google would discontinue this on their new phone!!
Anyone else having issues or know of a fix with apps closing when trying to load them in Daydream?
Thank you ! Is this specific to Pixel 4 or can I try to apply it on different phones ?
My sister will get a Xiaomi Mi 9 lite during holidays for example, would that have a chance to be usable ?
Ok, I rooted my phone, installed the magisk module, and the the daydream app and keyboard. However, when I put my phone in the headset, it still gives me an error message of "incompatible phone". What am I doing wrong?
crisco654 said:
Ok, I rooted my phone, installed the magisk module, and the the daydream app and keyboard. However, when I put my phone in the headset, it still gives me an error message of "incompatible phone". What am I doing wrong?[/QUOTE
It was working perfectly for me until I did the December update
Click to expand...
Click to collapse
sunorbitearth01 said:
crisco654 said:
Ok, I rooted my phone, installed the magisk module, and the the daydream app and keyboard. However, when I put my phone in the headset, it still gives me an error message of "incompatible phone". What am I doing wrong?[/QUOTE
It was working perfectly for me until I did the December update
Click to expand...
Click to collapse
Yeah I'm on December update as well. Btw, when it was working, what version not Magisk were you using?
Click to expand...
Click to collapse
crisco654 said:
sunorbitearth01 said:
Yeah I'm on December update as well. Btw, when it was working, what version not Magisk were you using?[/QUOTE
I believe it has updated twice since then so it would have been 2 revisions ago.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sunorbitearth01 said:
crisco654 said:
sunorbitearth01 said:
Yeah I'm on December update as well. Btw, when it was working, what version not Magisk were you using?[/QUOTE
I believe it has updated twice since then so it would have been 2 revisions ago.
Click to expand...
Click to collapse
I've tried downgrading Magisk, but it seems like it's not working with the December update for some reason.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anyone on the Dec or Jan update have any luck with this yet?
Any update on this? Does anyone have this working with a 4XL running the Jan update?
Thanks,
I believe it worked fine on the December update. But just tried it on the Jan update and the module doesn't seem to be installing for me.
MishaalRahman said:
Google quietly discontinued Daydream VR with the Pixel 4. If you have an existing Daydream VR viewer, it's useless with your Pixel 4. Fortunately, with root, we can re-enable support. While Daydream VR and phone-based VR in general are dying out, you can still use existing services like YouTube VR and other VR apps.
How to Install
Flash the Magisk Module attached to this thread and reboot.
Install Daydream from APKMirror.
Install Daydream Keyboard from APKMirror.
Note: If you don't hear any audio in Daydream, try running the following command in a rooted shell:
Code:
setprop persist.audio.vr.enable true
My Magisk Module should have already set this value, though.
Click to expand...
Click to collapse
Will this be fixed for the February update?
bobhilton6969 said:
Any update on this? Does anyone have this working with a 4XL running the Jan update?
Thanks,
Click to expand...
Click to collapse
tysj said:
I believe it worked fine on the December update. But just tried it on the Jan update and the module doesn't seem to be installing for me.
Click to expand...
Click to collapse
airmaxx23 said:
Will this be fixed for the February update?
Click to expand...
Click to collapse
Hey guys, sorry for the delay. I had it fixed for a while, but I'm just now uploading it. The problem was that the module template was outdated, so I used MishaalRahman's file, changed the module template to the updated one, and repackaged it. And it works like a charm now, on all updates, including Jan and Feb. Anyway, just download the module attached to this post, and remember to install Daydream and the Daydream Keyboard(those links can be found on the first post).
So, my oneplus 7T has just arrived yesterday. I only come to know that the phone doesn't has LED notification today. Do I miss something that can replace the functionality of LED notification?
Thanks before.
djangosteen said:
So, my oneplus 7T has just arrived yesterday. I only come to know that the phone doesn't has LED notification today. Do I miss something that can replace the functionality of LED notification?
Thanks before.
Click to expand...
Click to collapse
there are a few apps to mimic this behavior in the play store
MrGimpGrumble said:
there are a few apps to mimic this behavior in the play store
Click to expand...
Click to collapse
I actually aware of that. Unfortunately I don't like the app. So I'm actually trying to figure out other options if there's any.
djangosteen said:
I actually aware of that. Unfortunately I don't like the app. So I'm actually trying to figure out other options if there's any.
Click to expand...
Click to collapse
I dont think there is any other options... unless you are rooted and want AOD working, this i feel is a much better solution
MrGimpGrumble said:
I dont think there is any other options... unless you are rooted and want AOD working, this i feel is a much better solution
Click to expand...
Click to collapse
So I'm new to this forum as I've only received mine yesterday. But is there any detailed guide on how to root this device? I have hd1900 with 10.0.7 OOS. I've browsed the guide section but it is for 10.0.3. Thanks.
djangosteen said:
So I'm new to this forum as I've only received mine yesterday. But is there any detailed guide on how to root this device? I have hd1900 with 10.0.7 OOS. I've browsed the guide section but it is for 10.0.3. Thanks.
Click to expand...
Click to collapse
the concept is the same as 10.0.3
you need to install magisk canary app, set OEM unlock and adb in developer options in phone, then find the correct 10.0.7 magisk-patched-boot.img file from the forum then flash with adb
Just installed aodNotify by Jawomo on playstore. It's an early access app(not everyone will be able to download just yet). It's just fantastic!! I bought the pro version (less than a dollar). No battery drain, absolutely does what you intend to. Highly recommend it!
naazgulla said:
Just installed aodNotify by Jawomo on playstore. It's an early access app(not everyone will be able to download just yet). It's just fantastic!! I bought the pro version (less than a dollar). No battery drain, absolutely does what you intend to. Highly recommend it!
Click to expand...
Click to collapse
How can you use it on oneplus ? . As far as I know AoDNotify only compatible with Samsung phones . No way to run on oneplus .
Please check on playstore. It clearly says its for one plus(actually 8). Anyways i have been using it flawlessly. Y don't you try it for yourself and see..
naazgulla said:
Please check on playstore. It clearly says its for one plus(actually 8). Anyways i have been using it flawlessly. Y don't you try it for yourself and see..
Click to expand...
Click to collapse
Thanks for sharing. I guess the app developer needs to update the app's description then, as it still lists specific Samsung devices as the only ones with which it will work.
Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers.
Using magisk canary.
I just came here to post this exact question and you beat me to it. I'm having the same issue, but I did verify that SafetyNet passes using another app from the play store, so the issue seems specific to magisk.
terlynn4 said:
I just came here to post this exact question and you beat me to it. I'm having the same issue, but I did verify that SafetyNet passes using another app from the play store, so the issue seems specific to magisk.
Click to expand...
Click to collapse
What's the other app? As long as it's passing I guess that's all that really matters.
Konfuzion said:
What's the other app? As long as it's passing I guess that's all that really matters.
Click to expand...
Click to collapse
I used "Root and SafetyNet Checker" by BetterOpts
Here you go:
twitter.com/topjohnwu/status/1382563209995964418
xLexip said:
Here you go:
twitter.com/topjohnwu/status/1382563209995964418
Click to expand...
Click to collapse
Thank you
Oh well, that looks bad. May switch to iPhone if that's the case. Pixel phones lack performance and other Android phones have a quite bad software experience in comparison, oneplus included.
My plan was to switch to a pixel rom soon to have the best of both worlds like I did with previous OnePlus phones as well. Now I may not be able to do that without losing many features. Thanks Google!
deezid said:
Oh well, that looks bad. May switch to iPhone if that's the case. Pixel phones lack performance and other Android phones have a quite bad software experience in comparison, oneplus included.
My plan was to switch to a pixel rom soon to have the best of both worlds like I did with previous OnePlus phones as well. Now I may not be able to do that without losing many features. Thanks Google!
Click to expand...
Click to collapse
Per the link above, this is just an issue with Magisk app's API key, and the dev already has a fix. No reason to do anything drastic like switching to iPhone.
terlynn4 said:
Per the link above, this is just an issue with Magisk app's API key, and the dev already has a fix. No reason to do anything drastic like switching to iPhone.
Click to expand...
Click to collapse
Just saw it
xLexip said:
Here you go:
twitter.com/topjohnwu/status/1382563209995964418
Click to expand...
Click to collapse
A fix is out: t.me/lexipG/9937
xLexip said:
A fix is out: t.me/lexipG/9937
Click to expand...
Click to collapse
thanks man, you are man of culture
Do GPay, Netflix etc. work with Magisk now?
deezid said:
Do GPay, Netflix etc. work with Magisk now?
Click to expand...
Click to collapse
Yeah, like before.
Now he just needs to add back "Install to inactive slot(after OTA)" and we are all set lol
xLexip said:
Poprawka została wydana: t.me/lexipG/9937
Click to expand...
Click to collapse
Działa ! It works, thank you.
schmeggy929 said:
Now he just needs to add back "Install to inactive slot(after OTA)" and we are all set lol
Click to expand...
Click to collapse
I still have that option after updating the app.
terlynn4 said:
I still have that option after updating the app.
Click to expand...
Click to collapse
It is weird, some people still have others don't. It was temporarily removed in the last few updates for Google Pixel phones bootlooping. I have tried all 3, stable beta and Canary builds. All 3 have it missing.
Delete
schmeggy929 said:
It is weird, some people still have others don't. It was temporarily removed in the last few updates for Google Pixel phones bootlooping. I have tried all 3, stable beta and Canary builds. All 3 have it missing. View attachment 5282401
Click to expand...
Click to collapse
Strange. I'm on the same version of the app as your screenshot, but I haven't done the latest update of magisk itself so that's still on 22102.
terlynn4 said:
Strange. I'm on the same version of the app as your screenshot, but I haven't done the latest update of magisk itself so that's still on 22102.
Click to expand...
Click to collapse
Yeah don't update or you will be re-rooting the long way. Lol
Title says it all, have seen lots of rumours that it might be enabled but nothing concrete.
It's already here with a magisk module,
I don't think anyone here knows anything beyond what's publicly known, which is that there have definitely been code tweaks that are geared towards face unlock, but who knows when or even if for sure.
As said, yes, also if you root you can use a Magisk Module to get face unlock.
Well, the code was added, face match is added on Google assistant but not working yet, everything seems to point out that will be implemented, but until front end setting's are added, we'll have to rely on a magisk module. My bet is that will be implemented in future builds, whether is android 13 or afterwards I guess we'll see
My guess is no, they are getting everything set up and tested for the Pixel 7, we won't see it.
TonikJDK said:
My guess is no, they are getting everything set up and tested for the Pixel 7, we won't see it.
Click to expand...
Click to collapse
That is my guess too.
acidspider said:
It's already here with a magisk module,
Click to expand...
Click to collapse
I can't get the magisk. I'm on AT&t. They will not let me unlock the phone.