Hi pals:
I have recently successfully flashed LineageOS 18.1 with Magisk passing SafetyNet. Everything seems to be perfect, but can anyone ring some bell about if there is any project trying to make the IR camera working?
I do somewhat care about privacy and thus have not logged on Google yet. What I am trying to do is to figure out a perfect way of using as much potential as possible of this phone while maintaining a reasonable degree of privacy protection by dodging Google services as much as possible. That being said, I still have to use Android Auto frequently with Waze, thus Gapps are still installed, but just not logged in.
Can anyone make some advice about if I should use Lineage and wait for IR camera implementation or restore to stock Oxygen 11 then root with Magisk redone? Thanks.
I am also interested in this.
as far as i know: No OOS Cam no IR Sensor.
Download this GCam port .apk and install it, no config file necessary. When you run the app, select camera ID4 to activate the IR camera.
https://1-dontsharethislink.celsoazevedo.com/file/filesc/GCam_8.1.101_Wichaya_V1.4_Snapcam.apk
Related
Before I begin: I am in no way responsible for your device or any kind of content on it, I want to warn you that this can brick your device (or make it unusable in other ways), proceed with caution - YOU ARE RESPONSIBLE FOR YOUR DEVICE.
I tried it, it worked for me perfectly, but that doesn't mean it will work for you too.
My device is: Wileyfox Swift 2 plus Android 7.1.2 (TOS163B)
download and install the apk from this guide. (it says it only works on SD 820, 821 and 835, but ignore that) - direct link to the apk
download and install the magisk module from here. (you need at least Magisk v13)
reboot and enjoy your new Google Camera with HDR+.
Note: not all functions of the Google Camera work. (you can only take photos and videos)
I hope this guide helped you and now you can take better pictures :fingers-crossed:, if not let me know and I will try to help you.
Credit goes to:
otaconremo - Camera2API enabler magisk module
B-S-G - modified Google Camera
Works great, just the focus is a bit slow...
EDIT:
Uninstalled and reverted back, because OpenCamera and Vivino had issues - distorted images.
For those who don't know, RattlesnakeOS is a build of AOSP that you compile yourself, using resources in the cloud (Note: that you pay for!). From its github page (https://github.com/dan-v/rattlesnakeos-stack): RattlesnakeOS is a privacy and security focused Android OS for Google Pixel phones.
Quick Review:
Very bare bones, but also very fluid and stable. Everything works as expected. This is a great option if you're looking for a no-frills, bug free, gapps free ROM. Stock launcher works well with gestures. Great battery life too (see attachment).
The only issue I haven't found a solution for yet is that icon shape is square, with no way to modify it.
Installation:
Follow the instructions on the github page to get up and running with a build: https://github.com/dan-v/rattlesnakeos-stack#installation
I only changed the region to 'us-east-2', everything else used default settings.
Note that by default the deploy will set up a job to compile the ROM on the 10th of every month. So, unless you turn this off, you WILL END UP BEING BILLED FOR IT. Either remove the AWS Lambda schedule that it creates, or set the schedule to some very large value so you can trigger builds manually when needed. If you don't mind the cost, then obviously its best to get the OTA with security patches every month.
Root:
Root is obviously optional, and given the security focused nature of the ROM, not really recommended. I needed root for some apps, so I kept my bootloader unlocked, and then used the instructions for magisk boot.img patching (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching) to get root.
TL;DR- The boot.img can be obtained from the image created by RattlesnakeOS. Patch it in magisk manager, then flash using fastboot.
Camera:
Install microg (Services Core only i.e. com.google.android.gms) from its f-droid repo here: https://microg.org/download.html, then install Google Camera (apk can be pulled from the stock install before wiping it, or from apkmirror etc). I didn't need to do any signature spoofing etc, just installing 'Services Core' was enough to get gcam working without issues.
Cost:
My cost on AWS was ~1 USD. YMMV, depending on the resources you use and which region you use them in.
Conclusion:
Doesn't seem to get a lot of attention, but RattlesnakeOS is a great way to get a gapps free ROM. Its fairly hassle free once its setup, and OTAs are automatically generated in the cloud so updates should be seamless.
Curious if others are using it and what their experiences have been.
Hello all,
I would like to ask what ROM like the new Paranoid where I can use all the bank applications, Google play and my work application s without issues.
I think Lineage is not possible, bank applications will not work
Can anyone advise others ROM where this can be achived
My bank application works on Lineage. I typically don't leave a work application installed on my phone, but the couple times I've needed it, it works.
Guide Installing Lineage < See section 5, Very optional Magisk, it's more than Magisk. Maybe it doesn't work for what your doing, but it does for me.
You can try a virtual OS if you like. It's an app which simulates another android os within your current ROM. Works without root. Basically, a virtual machine.
https://www.xda-developers.com/vmos-lets-you-run-a-virtual-android-environment-on-your-phone/
Fresh install of Paranoid & my bank app & Gpay both work fine.
Didn't install magisk or any other root package.
I'm running Lineage 17.1 Nightly without GAAPs. And the AOSP camera is terrible. Every photo comes out blurry.
I tried installing Gcam V.2.2.1 from Arnova8G2 and OOS camera apks from mirror apk but nothing works. After install I get the same problem, "Camera Keeps Stopping".
Does anyone know of a work around for this. I can't get any camera apk working, (other than the stock pre-installed AOSP camera)
You can't just use the OOS Camera. You need a bunch of other libraries and such to make the OOS camera work.
Once I find a GCam that everything works on I tend to just stick with it. On 17.1 I'm using, 7.2_GCam_Urnyx05-v2.1.apk.
Look here, download GCam from here. (I would start by trying 2.1 since it works for me.)
Other versions are here if you want to try them.
Next to the 2.1 download click the configs link, scroll down to OnePlus 6/6T. These are XML files, I would download the first one natural / noiseless. You can try others later if you want. In internal storage of your device create a folder called GCam, inside that folder create one called Configs7. Place that XML that you just downloaded (oneplus6t-more-naturally-and-noiselessly-v2.xml) inside Configs7.
Now when you open the camera double tap the black area near the button that takes a picture, and select that XML.
OhioYJ said:
You can't just use the OOS Camera. You need a bunch of other libraries and such to make the OOS camera work.
Once I find a GCam that everything works on I tend to just stick with it. On 17.1 I'm using, 7.2_GCam_Urnyx05-v2.1.apk.
Look here, download GCam from here. (I would start by trying 2.1 since it works for me.)
Other versions are here if you want to try them.
Next to the 2.1 download click the configs link, scroll down to OnePlus 6/6T. These are XML files, I would download the first one natural / noiseless. You can try others later if you want. In internal storage of your device create a folder called GCam, inside that folder create one called Configs7. Place that XML that you just downloaded (oneplus6t-more-naturally-and-noiselessly-v2.xml) inside Configs7.
Now when you open the camera double tap the black area near the button that takes a picture, and select that XML.
Click to expand...
Click to collapse
Thank you so much! I did followed everything you said, but I still have the same problem. The app force closes before I get the chance to add the config. I tried enabling all of the permissions from "app info" along with allowing it to "modify system settings". But it still force closes
https://ibb.co/NSShkNN
Lifewithoutdeath said:
Thank you so much! I did followed everything you said, but I still have the same problem. The app force closes before I get the chance to add the config. I tried enabling all of the permissions from "app info" along with allowing it to "modify system settings". But it still force closes
https://ibb.co/NSShkNN
Click to expand...
Click to collapse
Just out of curiosity, Does installing WebView fix it? ? (You can uninstall it if it doesn't).
Im trying to think of what might be different since this works for me. Some apps require webview and will crash immediately if you dont have it. The LOS browser should work for this, but I've found for many apps it doesn't. There is a a library that is required for WebView on some ROMs (like Omni), but Ive never needed it on LOS.
OhioYJ said:
Just out of curiosity, Does installing WebView fix it? ? (You can uninstall it if it doesn't).
Im trying to think of what might be different since this works for me. Some apps require webview and will crash immediately if you dont have it. The LOS browser should work for this, but I've found for many apps it doesn't. There is a a library that is required for WebView on some ROMs (like Omni), but Ive never needed it on LOS.
Click to expand...
Click to collapse
Sorry for the late reply. I installed webview, but that didn't change anything.
It's also worth noting that after flashing Lineage, I lost my TWRP recovery. I then flashed Magisk through Lineage's supplied recovery.
I wish there was a simple solution for this. I came from OmniRom and Omni had the stock OOS camera and it was great! But without GAAPS installed, Omni is way too glitchy for my liking. That's the only reason why I'm using Lineage, to avoid random app force closures....guess I didn't avoid it entirely with the camera issue
Lifewithoutdeath said:
Sorry for the late reply. I installed webview, but that didn't change anything.
It's also worth noting that after flashing Lineage, I lost my TWRP recovery. I then flashed Magisk through Lineage's supplied recovery.
I wish there was a simple solution for this. I came from OmniRom and Omni had the stock OOS camera and it was great! But without GAAPS installed, Omni is way too glitchy for my liking. That's the only reason why I'm using Lineage, to avoid random app force closures....guess I didn't avoid it entirely with the camera issue
Click to expand...
Click to collapse
Wait.... Several things in there. So did you use the MicroG version of Omni then? As Omni can use Gapps if you use the regular build of Omni? Next did you just flash LOS straight over Omni? This maybe giving you issues. Also that GCam folder must be in place otherwise it won't work, you did that step right? As for recovery, yes, you have to flash TWRP after LOS to keep TWRP.
I have a Lineage Install Guide here. The second post has the cliff notes version if you want. However the long version does have some extra stuff in it, like passing safety net and such.
OhioYJ said:
Wait.... Several things in there. So did you use the MicroG version of Omni then? As Omni can use Gapps if you use the regular build of Omni? Next did you just flash LOS straight over Omni? This maybe giving you issues. Also that GCam folder must be in place otherwise it won't work, you did that step right? As for recovery, yes, you have to flash TWRP after LOS to keep TWRP.
I have a Lineage Install Guide here. The second post has the cliff notes version if you want. However the long version does have some extra stuff in it, like passing safety net and such.
Click to expand...
Click to collapse
Yes, I tried the micro-g version on Omni...twice. I haven't tested the standard version yet. When I flashed Omni, however, I didn't flash it over OOS. It was a clean flash.
I did not flash Lineage over anything either.
Yes I have that GCam folder in my internal storage, as instructed.
Appreciate the info, I'll check out your install guide!
Edit: Worth mentioning that when I used Omni. Both times, there was a broken google search bar at the top of the app home screen page. Couldn't get rid of widget, use it, nor move it. It was stuck in place, and no longer said "Google". It was an entirely blank search bar.
I do love the Poco F2 Pro as great value for money, just disappointed there's no custom ROM support. I thought I'd see if I can get MicroG to work. It's not a super simple process, as requires first debloating and removing the Google Play Services before doing so. I had the best success actually using the Systemless Debloater using the terminal and Magisk. It sounds complicated, but is fairly simple. I would gradually remove a few apps at a time and do a TWRP backup and restore if it failed to boot up. I also disabled a majority of the Miui apps and services including Mi Account. When attempting to remove FindDevice the device failed to boot up, so have left it for now.
Debloater can be installed directly from Magisk by going to downloads and searching. Then check this https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
There's other articles on debloating also https://medium.com/@mail.anonymous....devices-via-android-debug-bridge-2e5bcd94dfa0
As obviously the ROM doesn't support signature spoofing natively for MicroG to wok it needs to be patched. I tried the NanoDroid MicroG Patcher, but it failed.
There is a way to do it with an Xposed module. But I was able to do it by using this tool. Seriously one of the best tools I've yet seen, so deserves all the credit.
Using the Smali Patcher 6.9. Download and run it on your computer. It creates a Magisk ZIP that can be flashed by TWRP or Magisk and enables signature spoofing and a range of other hacks.
https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
After signature spoofing is enabled. You can flash MicroG. There's multiple ways to do this. I've been able to get all the boxes checked for signature spoofing support with MicroG, but just a few issues still getting the Play Store to sign in. I actually used this package by FriendlyNeighbourhodShane https://github.com/friendlyneighborhoodshane/minmicrog_releases/releases
But also NanoDroid MicroG installer would be fine, which can be downloaded by https://github.com/Nanolx/NanoDroid
This is still a work in progress. To just get Signature Spoofing and MicroG working isn't too hard, it's often a bit trickier to get the Play Store to function correctly, but only required for paid applications, as the Auora Store and F-Droid work well especially with the privileges extension, that allows them to auto update apps. This is included with the friendlyneighborhoodshane version of MicroG standard installer.
I'm curious why there is not even an unofficial Lineage. I mean, source code is out, isn't it?
dustojnikhummer said:
I'm curious why there is not even an unofficial Lineage. I mean, source code is out, isn't it?
Click to expand...
Click to collapse
Maybe devs need more time to port roms to our phone ¯\_(ツ)\_/¯
Ok following up this thread. It seems that most Xiaomi bloatware can be removed. This article seems to go over what can and can't be removed. https://selivan.github.io/2020/02/25/removing-bloatware-from-xiaomi-miui-android.html
Go get the Google Play store working in the end. Was able to by running the NanoDroid_MicroG.zip in TWRP. Modify the nanodroid-setup file and change it so PlayStore=10 to install PlayStore.
Boot up phone and go to MicroG settings. Enable the UnifiedNlp back ends. I enabled Google Device Registration. Then sign into your Google account from MicroG. Don't run the Play Store, but clear data.
Restart phone then try running the Play Store and see if it opens correctly.
I'm somewhat ok with this phone. I think the phone is great, but just wish I could get HavocOS or LineageOS for it. I'm going to test it for a while now and see how it goes.
Hello,
on Android 11 (Xiaomi.eu rom - tried with stable and beta), after installing the Smali Patcher module, i've got a bootloop. Have you tried to enable signature spoofing on Android 11 ?
Would love to have a full guide now when Lineage is out.
Lowxorx said:
Hello,
on Android 11 (Xiaomi.eu rom - tried with stable and beta), after installing the Smali Patcher module, i've got a bootloop. Have you tried to enable signature spoofing on Android 11 ?
Click to expand...
Click to collapse
Haven't tried on any Android 11 ROMs as yet. CrDroid and a few custom ROMs have signature spoofing already. I'll do a bit more testing and might update this thread if I can get MicroG all working on other ROMs.
Hello, it's good to know that this is possible however a full guide would be much more useful. Thank you!