Related
[Solved] [Magisk Module] [Oreo Update] Spoofing "Daydream ready device" on a Nexus 6P
TL;DR Skip to the last paragraph!
Daydream runs pretty nice on my n6p. sucks to sideload all apps also not all apps can be found on google. so i wanted play store to recognize my device as "daydream ready" and let me download all daydream apps. a little googleing later i found 2 reddits explaining what to do and saying "it works" in the comments.
https://www.reddit.com/r/oneplus/co...got_daydream_working_on_a_oneplus33t/dbmy2it/ creating 2 new files in /system/etc/permissions/
https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other/ put the 2 feature tags in handheld_core_hardware.xml
none of those worked. i could start sideloaded daydream apps before this. updating/downloading from play store is my issue.
things i didnt try yet:
- a clean flash of the rom then change the permission files in twrp adb then reboot.
- putting the feature tags in 2 seperate files AND in handheld_core_hardware.xml
- https://android.googlesource.com/pl.../etc/android.hardware.vr.high_performance.xml has the <feature name="android.software.vr.mode" /> and the high performance mode tag in it. didnt try that 2 tags in one file way yet.
anybody got this to work yet? if so pls share
EDIT: i made a magisk v10 module changing the build.prop. if anyone wants to do it this way feel free to dl the attached module.zip. just downloaded some previously "incompatible" apps. idk what happens if u install it on a device that is not daydream-compatible. n6p is the dev device so it is compat but not daydream-ready. as every dev i take no responsibility for anything. u flash this at ur own risk. that it requires magisk to be installed and working is self-explainatory. just ignore the "wrong vendor.img" warning that pops up on booting.
UPDATE: magisk module disabling bug fixed since some versions ago.
V1.1 : quick and dirty commented out out manufacuturer line and zipped it again. still v10/11 magisk template but it works. just tested. template didnt change much anyway to v12 i think.
DaydreamBypass.zip : version for oreo by @tazzkiller
Here you go::
1) Get a build.prop editor out of the play store once you have acquired root access.
2) Locate the following strings of texts and change what is written there to "marlin", without the quotes.
ro.build.product
ro.product.device
ro.product.board
ro.product.name
3) Locate the following strings of texts and change what is written there to "Google", without the quotes.
ro.product.manufacturer
4) Locate the following string of text to "Pixel XL", without the quotes.
ro.product.model
5) Locate the following string of text and change what is written there to "google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys" without the quotes.
ro.build.fingerprint
The last part might not be the proper string of text but I am doing this off of memory. Just look for the text that looks like the above and swap it out. After you do this, reboot your device. You will get an error message or two upon booting up and the first boot may take longer than normal but it works. I've personally done it with my 6P to get proper Daydream store games because I wanted to play Gunjack and ArcSlinger. Your build.prop editor should save the original build.prop as a build.prop.bak. When you are done installing your new games, simply change the new build.prop to build.prop.bak1, and the original back to a build.prop
The only bugs I have noticed with this are that during the first 24 hours after doing this I continually got an overheating message while in daydream even when the device wasn't hot. I don't know if time played a factor or multiple reboots but eventually the message stopped popping up. Let me know if it works for you.
Varking said:
Here you go::
1) Get a build.prop editor out of the play store once you have acquired root access.
2) Locate the following strings of texts and change what is written there to "marlin", without the quotes.
ro.build.product
ro.product.device
ro.product.board
ro.product.name
3) Locate the following strings of texts and change what is written there to "Google", without the quotes.
ro.product.manufacturer
4) Locate the following string of text to "Pixel XL", without the quotes.
ro.product.model
5) Locate the following string of text and change what is written there to "google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys" without the quotes.
ro.build.fingerprint
The last part might not be the proper string of text but I am doing this off of memory. Just look for the text that looks like the above and swap it out. After you do this, reboot your device. You will get an error message or two upon booting up and the first boot may take longer than normal but it works. I've personally done it with my 6P to get proper Daydream store games because I wanted to play Gunjack and ArcSlinger. Your build.prop editor should save the original build.prop as a build.prop.bak. When you are done installing your new games, simply change the new build.prop to build.prop.bak1, and the original back to a build.prop
The only bugs I have noticed with this are that during the first 24 hours after doing this I continually got an overheating message while in daydream even when the device wasn't hot. I don't know if time played a factor or multiple reboots but eventually the message stopped popping up. Let me know if it works for you.
Click to expand...
Click to collapse
oh so its build.prop not permissions. or do i need those too?
will make me a magisk module for the build.prop mods tomorrow or so. and tell u how it worked out. u dont recommend keeping the changed build.prop?
Sent from my Nexus 6P using XDA Labs
All I did is unlock my bootloader, root my phone, and edit the build.prop. I would keep both build.props. It makes it so you can easily switch to the Pixel XL settings to download and install new games, and then load the original 6P ones again after you are done. Editing the build.prop like above had Google email me a welcome to the Pixel family email, too lol.
But I have 100% working daydream and store access just by doing what I listed above.
4RK4N said:
oh so its build.prop not permissions. or do i need those too?
will make me a magisk module for the build.prop mods tomorrow or so. and tell u how it worked out. u dont recommend keeping the changed build.prop?
Click to expand...
Click to collapse
I'm on a Nexus 5X and I'm on Pixel ROM, but I've heard keeping that build.prop change is fine. It doesn't affect Nexus as our OTAs and Stock apps don't need it. It'll just give you access to the Pixel specific apps
My experience on Sony Xperia Z1 says that you need to clear data of Google Play Service and Google Play Store after you modify the XMLs in system. I guess that by doing this, your device will be updated as a "Daydream ready phone" in Google's database.
By the way, Xperia Z1's Daydream doesn't work on AOSP 7.1.1. It crashes. Anyway, after I cleaned the data of those two apps, I can download apps like Daydream, Google VR Service, Daydream Keyboard, etc. from Google Play.
UPDATE:
apparently the build.prop modifications crash google camera (latest purenexus). fc upon opening the app.
also various daydream apps (twilight pioneers, vr karts sprint, etc) report "phone overheating" quite fast and force you to "cool the phone" with a "take it out of the headset and close the app" vr screen.
interstingly disabling the magisk module in magisk manager wasnt enough. build.prop was still set to the pixel xl values. uninstalling my module restored original build.prop.
no "wrong vendor.img" warning, google camera works, i still get "performance reduced. phone overheating." overlay warnings while playing daydream games but no force cool off time.
so i just install the module again once a week to check for updates on daydream apps and then uninstall it again.
anybody figured out how to disable the kinda annoying "overheating" warning while playing? ^^
Sent from my Nexus 6P using XDA Labs
4RK4N said:
UPDATE:
apparently the build.prop modifications crash google camera (latest purenexus). fc upon opening the app.
also various daydream apps (twilight pioneers, vr karts sprint, etc) report "phone overheating" quite fast and force you to "cool the phone" with a "take it out of the headset and close the app" vr screen.
interstingly disabling the magisk module in magisk manager wasnt enough. build.prop was still set to the pixel xl values. uninstalling my module restored original build.prop.
no "wrong vendor.img" warning, google camera works, i still get "performance reduced. phone overheating." overlay warnings while playing daydream games but no force cool off time.
so i just install the module again once a week to check for updates on daydream apps and then uninstall it again.
anybody figured out how to disable the kinda annoying "overheating" warning while playing? ^^
Click to expand...
Click to collapse
About the build.prop, don't change manufacturer. That messes up the camera. Allot.
I'm really interested in making my Samsung Galaxy S7 Edge "Daydream-compatible". I don't even have a Daydream headset, just the regular Gear VR. I really wish that Google would just make a Youtube VR app for Gear VR--it's the only reason why I'd like to give Daydream a try. If you want me to test anything, please let me know!
itinkerstuff said:
I'm really interested in making my Samsung Galaxy S7 Edge "Daydream-compatible". I don't even have a Daydream headset, just the regular Gear VR. I really wish that Google would just make a Youtube VR app for Gear VR--it's the only reason why I'd like to give Daydream a try. If you want me to test anything, please let me know!
Click to expand...
Click to collapse
since it requires the actual daydream headset to activate daydream mode im afraid i cant help you. besides the youtube vr app is optimized for the daydream controller. making it work with the gear vr headset buttons or the gear vr controller would require some rewriting of the yt vr app.
Sent from my Nexus 6P using XDA Labs
i tested this magisk modul on my s7 edge. seems to work. but then my NFC doesnt work anymore ?!?! so daydream doesnt work.
are really all prop need to be changed?
what build.prop item can make NFC unfunctional?
btw. this is the error i got in Need for Speed VR (logcat) ->
"failed to initialize async reprojection, unsupported device"
inteks said:
i tested this magisk modul on my s7 edge. seems to work. but then my NFC doesnt work anymore ?!?! so daydream doesnt work.
are really all prop need to be changed?
what build.prop item can make NFC unfunctional?
btw. this is the error i got in Need for Speed VR (logcat) ->
"failed to initialize async reprojection, unsupported device"
Click to expand...
Click to collapse
try removing the manufacturer line. maybe nfc still works and u can daydream.
just recived my n6p back from rma (ranfom hardware failure) dunno if module still works with latest magisk.
about nfs vr idk. maybe samsung messed up some graphics function. wait no they call it "optimized" xD find a aosp rom and try it again.
Sent from my Nexus 6P using XDA Labs
use magisk prompt incompatible
use magisk daydream prompt： ‘’ incompatible phone ‘’
how to deal with .......
my telephone model is Nexus 6
xiaoluwan said:
use magisk daydream prompt： ‘’ incompatible phone ‘’
how to deal with .......
my telephone model is Nexus 6
Click to expand...
Click to collapse
What? give us a little more than a few random words pls. ur post makes like no sense sry to day that.
ALSO: changed the module to NOT alter manufacturer. i still wouldnt recommend having the module always running. just tested it. still can dl all daydream apps while module is active. module disabling works now with magisk yay. new version in first post.
Sent from my Nexus 6P using XDA Labs
How to get past this screen?
Not able to proceed even if I enter my credentials.
Will this work for leeco lemax2?
Guys don't bother. I got Daydream running on my Moto X Style and virtually all of the 3rd party apps don't work. They either crash on launch or are in full screen 2d mode and not split screen 3d mode. Only the Google made Daydream apps seem to work.
tboy2000 said:
Guys don't bother. I got Daydream running on my Moto X Style and virtually all of the 3rd party apps don't work. They either crash on launch or are in full screen 2d mode and not split screen 3d mode. Only the Google made Daydream apps seem to work.
Click to expand...
Click to collapse
How did u skip add payment option?
baratheon16 said:
How to get past this screen?
Not able to proceed even if I enter my credentials.
Click to expand...
Click to collapse
i never had that screen lol. cant help you sorry. i have a paypal linked with my playstore since ages ago maybe thats why it never asked me.
Sent from my Nexus 6P using XDA Labs
baratheon16 said:
How did u skip add payment option?
Click to expand...
Click to collapse
I never got that option. maybe because I have paypal linked to playstore as previous guy said.
Seriously, don't waste your time.
Hi all! I bought the X820 for my girlfriend and I arrived some days ago.
I installed Mokee and SlimROM and both have the same problem: If I pinch to zoom, from the beginning of zoom slider until almost the end, the displayed image is not correct (anfter taking the photo, the saved image is correct).
I don't know if this is a bug of certain roms, a misconfiguration of my setup... I just realized that the problem disappears if image resolution is changed to anythind 16:9. Once again, idk if this is a known issue or not, you tell me.
Other thing I'd like to ask is what is the best rom in you opinion. As I said before, I have installed Mokee and SlimROM so far. I'd like to know what's the most stable and battery friendly rom.
Thank you!
Heyyo, that digital zoom bug is present on custom Nougat and Oreo ROMs for many camera apps. I'm unsure if it's because they enforce camera HAL2 when LeEco never updated to it or if it's the camera shims.
Certain camera apps though don't suffer this issue such as CAMU... So yeah, it's an odd bug.
For most stable and battery friendly? I'd say OmniROM Nougat is definitely that since the focus of OmniROM Nougat is stability and it is pretty decent for battery life, especially if you use Greenify with root and APK profiles such as Project X.A.N.A. battery.
Otherwise? SlimRoms has been pretty darn good for a balance of stability, battery and performance.
ThE_MarD said:
Heyyo, that digital zoom bug is present on custom Nougat and Oreo ROMs for many camera apps. I'm unsure if it's because they enforce camera HAL2 when LeEco never updated to it or if it's the camera shims.
Certain camera apps though don't suffer this issue such as CAMU... So yeah, it's an odd bug.
For most stable and battery friendly? I'd say OmniROM Nougat is definitely that since the focus of OmniROM Nougat is stability and it is pretty decent for battery life, especially if you use Greenify with root and APK profiles such as Project X.A.N.A. battery.
Otherwise? SlimRoms has been pretty darn good for a balance of stability, battery and performance.
Click to expand...
Click to collapse
Thank you bro! My girlfriend is loving CAMU
victor141516 said:
Thank you bro! My girlfriend is loving CAMU
Click to expand...
Click to collapse
You're welcome!
Oh also if she wants apps that require passing SafetyNet checks? You'll want to install Magisk 14.3 and Universal SafetyNet fix for the Le Max 2.
I know 14.5 is latest but it's a bit experimental since it has some major changes which still require testing hence I recommend 14.3 or 14.0 stable.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
After Magisk is flashed via TWRP? Reboot into your ROM and then reboot to TWRP and flash this Magisk module
https://forum.xda-developers.com/le-max-2/themes/magisk-how-to-pass-safetynet-check-t3617017/amp/
Now Google Play Store should show under settings that the device is certified.
Example of apps that require SafetyNet is Nintendo apps and Netflix. There's other games and apps that also require it but not 100% sure which ones but a Google search should reveal a list.
ThE_MarD said:
You're welcome!
Oh also if she wants apps that require passing SafetyNet checks? You'll want to install Magisk 14.3 and Universal SafetyNet fix for the Le Max 2.
I know 14.5 is latest but it's a bit experimental since it has some major changes which still require testing hence I recommend 14.3 or 14.0 stable.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
After Magisk is flashed via TWRP? Reboot into your ROM and then reboot to TWRP and flash this Magisk module
https://forum.xda-developers.com/le-max-2/themes/magisk-how-to-pass-safetynet-check-t3617017/amp/
Now Google Play Store should show under settings that the device is certified.
Example of apps that require SafetyNet is Nintendo apps and Netflix. There's other games and apps that also require it but not 100% sure which ones but a Google search should reveal a list.
Click to expand...
Click to collapse
I installed 14.5 and she is using only Netflix (I mean apps that require SafetyNet). I only had to hide root using Magisk Hide and it works fine. IDK if it's just Netflix what is needed to be hidden or other Android apps too but I hid some Android things (Android Shared Library and others) and now even Play Store reports as "Certified" :angel: (sadly Magisk doesn't pass SafetyNet test D: )
victor141516 said:
I installed 14.5 and she is using only Netflix (I mean apps that require SafetyNet). I only had to hide root using Magisk Hide and it works fine. IDK if it's just Netflix what is needed to be hidden or other Android apps too but I hid some Android things (Android Shared Library and others) and now even Play Store reports as "Certified" :angel: (sadly Magisk doesn't pass SafetyNet test D: )
Click to expand...
Click to collapse
Ah glad to hear it! Yeah the Magisk SafetyNet check isn't 100% accurate. As long as the play store says cetified that's all that matters anyways
ThE_MarD said:
Ah glad to hear it! Yeah the Magisk SafetyNet check isn't 100% accurate. As long as the play store says cetified that's all that matters anyways
Click to expand...
Click to collapse
This is the list of apps hidden, if anyone is interested:
Android Shared Library
com.google.android.gms.setup
Google Play Store
Google Services Framework
Netflix
First off, T-Mobile version H932 rooted with bootloader unlocked and TWRP installed.
I was a long time user of Cyanogenmod/Lineage on other platforms in the past and overall prefer AOSP based ROMS that are close to stock. So, I have tried PixelExperience, Lineage, and LiquidRemix on my V30. I like them all but overall I like LiquidRemix the best mostly due to some of the LiquidLounge options.
However, I have 3 things I miss. I could probably do without them but I think my overall usefulness of the phone is better when I have them.
1. WiFi Calling - I have poor coverage in my office until TMO deploys Band 12 or Band 71 in my area. Not on schedule for almost a year yet.
2. OK Google support. I have tried numerous things to get this working on all 3 of the custom roms but it simply does not. Sounds like a MIC volume issue currently in all AOSP based ROMS on the V30. I use Android Auto (with a headunit) and not having this is kind of a pain.
3. Google Pay NFC support. I installed Magisk on all 3 custom ROMS but never could get it to fully pass all the safetynet checks.
As for running Stock. I know it would fix 1&2 above, but if I kept the device rooted and bootloader unlocked I am not sure #3 would be fixed. However, I can deal with that. What I hate about LG Stock overall is the interface, all their crap, and especially their dialer. I previously was side loading APK version of Google Dialer but it is missing the SPAM features and such unless you can flash it. I also sideloaded a pixel launcher and GCAM. But the dialer thing was always a pain.
I am going to try the debloated/magisk 20p STOCK. Anyone using this and have suggestions on how to get it working with Google Pay, Google Dialer, etc?
Next phone, I will probably spend the money on a pixel
Havoc is pretty awesome
TheCoryGuy said:
Havoc is pretty awesome
Click to expand...
Click to collapse
Yes, I'm sure it is. The guys doing custom ROMs do great work. But... Does I'm sure none of the 3 things I listed work on it.
Some day we'll get Wi-Fi calling in a custom ROM. One would think this would be more a standard method built into Android itself
I've got a H931 (basically daily driver with us998 20g) and a ls998 that I've used to test various roms and am now experimenting with serious debloating us998 20g on it.
I'm also accustom to Lineage, but as you know, there are not official builds for all devices. While the available roms are good, they are still a bit away from supporting all the basics.
In the meantime (and possibly for longer), just got through debloating the ls998. Now only 27 apps installed. Everything I need is working, very well actually. Looking at debloating even further. Watching to see if there are any ill effects.
It's difficult to determine what is the best, most productive way to go. At this point for me though I think it's debloating a stock rom. Time consuming but I hope worth it.
Good luck with your choice, Cheers
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
thebitjockey said:
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
Click to expand...
Click to collapse
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
AsItLies said:
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
Click to expand...
Click to collapse
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
You're not running any Xposed modules, are you?
ChazzMatt said:
You're not running any Xposed modules, are you?
Click to expand...
Click to collapse
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
schwinn8 said:
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as both 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
Click to expand...
Click to collapse
I don't know. Mine was hiding from Google Pay very well on18.0 and then 18.1 -- until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed route even though I know that can't be invisible from Safety Net. I made the choice on purpose.
ChazzMatt said:
I don't know. Mine was hiding from Google Pay very well on 18.1 until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed even though I know that can't be invisible from Safety Net.
Click to expand...
Click to collapse
Stock rooted US998.
* Battery circle with percentage number inside, instead of TWO stock LG battery icons (wasted space and looks ugly). How complete the circle is also indicates percentage.
* Actual LTE symbol, not silly"4GLTE".
* H for HSPA, not "4G".
* Gradient distinction for both carrier and Wi-Fi strength.
Some are build prop edits, but I'm also running two Xposed modules.
Sent via open market LG US998 V30/V30+
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Funny, in that I just tried my procedure on my 2nd device and it didn't work - but still working / worked on the H931...
My guess is that on one, Titanium bkup wasn't installed (installed after enable gpay), on the other, already installed?
will post back if I figure it out.
Try magisk hide props module
Bupreno said:
Try magisk hide props module
Click to expand...
Click to collapse
What is "props module"?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Go to Magisk forum. It has detail instructions how to pass Google pay.
You have to install old version of Google service frame work in order to make it.
It's working fine on my phone.
I use omnirom atm, se enforcing, safetynet check passes, cts profile matches too, but netflix isn't there, some other apps are missing too.
I tried to install magisk hide, and magisk hide props, tried different finger prints, cleared playstore cache.
I'm out of ideas. Does anyone know what could cause this?
I would be thankful for pointing me in the right direction. I'm thinking of going back to stock right now...its a bit more bloated and one android version down, but at least things work.
chainer1 said:
I use omnirom atm, se enforcing, safetynet check passes, cts profile matches too, but netflix isn't there, some other apps are missing too.
I tried to install magisk hide, and magisk hide props, tried different finger prints, cleared playstore cache.
I'm out of ideas. Does anyone know what could cause this?
I would be thankful for pointing me in the right direction. I'm thinking of going back to stock right now...its a bit more bloated and one android version down, but at least things work.
Click to expand...
Click to collapse
Greetings. The problem you're facing is caused because our device supports DRM Level 3.
You can use Netflix, but you won't be able to stream in HD. Just download the app from an external source like apkmirror (here) and install it manually.
Hey guys,
Spending way too much time on my iPhone lately and recently purchased a Pixel 4a to strip down the OS to the bare essentials. If possible, I want to retain the following functions:
Gmail/Email
Tasks/To-Do
Calendar
Notes
Navigation
Weather
Clock
Plex or PlexAmp
Signal Messenger
Possibly WhatsApp
Everything else, I'd like to remove, including the option to install more Apps from the Play Store. Essentially, what the Ghost Phone does, but without a $300 price tag and a several month wait.
What's the best way to accomplish this? I installed LineageOS but I'm not sure if that will break any of the functions I'm trying to accomplish. Any pointers greatly appreciated. Bonus points if there's a way to lock it to grayscale!
on android, everything is a app. you already installed custom rom, try to freeze/disable each app on its own and do some test phone is working properly. if phone is stable you can uninstall.
you can disable packages by adb shell or by app (no root required)
you may also have a look in microG (root)
https://github.com/microg/GmsCore/wiki
for strip down kernel during runtime try Kernel Adiutor (root)
https://github.com/Grarak/KernelAdiutor/releases
alecxs said:
on android, everything is a app. you already installed custom rom, try to freeze/disable each app on its own and do some test phone is working properly. if phone is stable you can uninstall.
you can disable packages by adb shell or by app (no root required)
you may also have a look in microG (root)
https://github.com/microg/GmsCore/wiki
for strip down kernel during runtime try Kernel Adiutor (root)
https://github.com/Grarak/KernelAdiutor/releases
Click to expand...
Click to collapse
Hey Alecxs, sorry for the delayed reply, I seem to have missed this. Thanks for the feedback. I'm mostly trying to figure out a solution where I don't need to do much customization -- like the Ghost Phone but just the ROM component of it.
Thank you!