Related
Hey,
did somebody try to install Xposed Framework on the book?
Its normal Android 6.0.1, so it should be work. It must be the x86 version right?
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
nan0s7 said:
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
Click to expand...
Click to collapse
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
ox_eye said:
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
Click to expand...
Click to collapse
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
nan0s7 said:
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
Click to expand...
Click to collapse
I downloaded the arm64 file again, but got the same error "error: 255".
ox_eye said:
I downloaded the arm64 file again, but got the same error "error: 255".
Click to expand...
Click to collapse
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
nan0s7 said:
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
Click to expand...
Click to collapse
Okay, I have the time. But I dont know what I have to do.
ox_eye said:
Okay, I have the time. But I dont know what I have to do.
Click to expand...
Click to collapse
I'm still having a look around, but before I shove more test builds down your throat for you to see if they work I need to ask; do you know how to fix a boot-loop? Because that may happen and I can't be liable for your device.
But if you're cool with that, I'll give you more things to test out ;D
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
ox_eye said:
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
Click to expand...
Click to collapse
Yeah, I mean you can install TWRP on your device, it's just not recommended at the moment as it can be unstable. But yeah, it's basically the same here.
Have you got your device Rooted? Because I'd like to test out Magisk's Xposed version on x86_64. It doesn't say that it supports it or not... and I'm not sure if it's just implied from the original compatibility. But I guess now is a good time to find out, and I'll be able to update my Megathread with the information.
To install it (assuming you're Rooted via Magisk - if not, my Megathread has the information) just download the Magisk Manager app from the Play Store, go to the "Downloads" section, and download the latest SDK version (I think it's 24 or 23...) and install that (if the option is there). Once that's done downloading, just go to this page and download the Material Design Xposed Installer, and follow the instructions there.
Hopefully that should work... but if not, that just means we're going to have to do more experimenting!
Installer link: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
ox_eye said:
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
Click to expand...
Click to collapse
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
nan0s7 said:
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
Click to expand...
Click to collapse
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
ox_eye said:
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
Click to expand...
Click to collapse
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
nan0s7 said:
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
Click to expand...
Click to collapse
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
frankjerkyass said:
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
Click to expand...
Click to collapse
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
nan0s7 said:
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
Click to expand...
Click to collapse
Thanks I do have Magisk installed and have working root.
There is still no way to install xposed?
matata86 said:
There is still no way to install xposed?
Click to expand...
Click to collapse
In the moment not
Hi, friends! Did anyone try to install xposed*.zip via TWRP ?
I'm seeing more and more people use Android phones Google-free by not installing gapps and getting all their applications through alternative sources like F-Droid. When I look at the custom ROMs for the Essential Phone, I see most have gapps baked in.
Just curious if anyone has experience on the PH-1 without gapps or Google service. What ROM are you using? Any issues?
Sent from my [device_name] using XDA-Developers Legacy app
Yes I'd love to know if anyone has gone microG, Xposed FakeGapps on Oreo with a custom rom?
Also if anyone has used Terminal Debloater on Stock Oreo and doing ok?
Thanks
Does Generic System Image come with Gapps? if not then you can use that.
TheIronLefty said:
Does Generic System Image come with Gapps? if not then you can use that.
Click to expand...
Click to collapse
I was thinking that as well. In fact, perhaps the deodex ROM is without gapps. I'll have to ask in that thread.
Sent from my [device_name] using XDA-Developers Legacy app
TheIronLefty said:
Does Generic System Image come with Gapps? if not then you can use that.
Click to expand...
Click to collapse
If that reply was for me, I'm asking more about Custom Roms.
ooklathemok said:
I'm seeing more and more people use Android phones Google-free by not installing gapps and getting all their applications through alternative sources like F-Droid. When I look at the custom ROMs for the Essential Phone, I see most have gapps baked in.
Just curious if anyone has experience on the PH-1 without gapps or Google service. What ROM are you using? Any issues?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It has been a long process, but I am most of the way there. Used deodexed Oreo Stock. Had to use Tingle manually to patch the framework.jar to get microg running. Haven't debloated yet, but most of the stock apps are disabled at this point. Most apps I use are from F-Droid. Using it as DD now.
Took several days to discover the NFC point is very narrow at the bottom center of the back. I had thought I had broken something. :silly:
I think I'm 99.9% there with CarbonROM LOL...
UnifiedNip is registerd in system, but this section I can't checkmark, even after rebooting. I was using the latest Preview GMSCore, I'll flash the rom over and try with the Stable GMSCore and see if it makes any difference and report back.
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
DoR3M3 said:
I think I'm 99.9% there with CarbonROM LOL...
UnifiedNip is registerd in system, but this section I can't checkmark, even after rebooting. I was using the latest Preview GMSCore, I'll flash the rom over and try with the Stable GMSCore and see if it makes any difference and report back.
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
Click to expand...
Click to collapse
I don't have "UnifiedNlp has known location" checked even though Satstat and OSM clearly show the location.
I am using Core -127 from NanoDroid 17.7.
Debloater is up next.
Well I just wiped/formatted, flashed back the Oreo fastboot image, now ready to flash in carbonrom and try this as I said with the stable versions of microg...
BRB...
DoR3M3 said:
I think I'm 99.9% there with CarbonROM LOL...
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
Click to expand...
Click to collapse
How was your experience with FakeGapps? I kept getting Null pointer exceptions. Tried v1.1 and 2.0.
gadgetguy08 said:
How was your experience with FakeGapps? I kept getting Null pointer exceptions. Tried v1.1 and 2.0.
Click to expand...
Click to collapse
Where did you see, get this at?
Ok UnifiedNIp is registered in system - [Checked]
To make everything work correctly, you'll want to push the GmsCore.apk to /system/priv-app/GmsCore/GmsCore.apk and then extract the lib/ folder from the GmsCore.apk to /system/priv-app/GmsCore/lib - otherwise the bundled libraries will not be found by the app and the maps library will crash apps.
If you don't know how to extract from an .apk, just rename to .zip, then copy out the lib directory.
I did have Xposed modules installed for this, so I will go back one more time, wipe it all again, and this time, see if I get it again.
DoR3M3 said:
Where did you see, get this at?
Ok UnifiedNIp is registered in system - [Checked]
To make everything work correctly, you'll want to push the GmsCore.apk to /system/priv-app/GmsCore/GmsCore.apk and then extract the lib/ folder from the GmsCore.apk to /system/priv-app/GmsCore/lib - otherwise the bundled libraries will not be found by the app and the maps library will crash apps.
If you don't know how to extract from an .apk, just rename to .zip, then copy out the lib directory.
I was always able to get
I did have Xposed modules installed for this, so I will go back one more time, wipe it all again, and this time, see if I get it again.
Click to expand...
Click to collapse
I had the FakeGapps errors in the Xposed Log [systemless version 90.2-beta3]. Tried several things. Interesting you didn't experience them.
I was always able to get UnifiedNLP to registered. It just doesn't show that it has a known location in the microg self check, but SatStat, OSM and others show it.
gadgetguy08 said:
I had the FakeGapps errors in the Xposed Log [systemless version 90.2-beta3]. Tried several things. Interesting you didn't experience them.
I was always able to get UnifiedNLP to registered. It just doesn't show that it has a known location in the microg self check, but SatStat, OSM and others show it.
Click to expand...
Click to collapse
Xposed showed a notification, I mean, you just looked in the logs, or how did you first know?
What is SatStat, OSM and others?
How are you installing microg? I just installed the apk is all, these versions and in this order;
Services Core - com.google.android.gms-12221403.apk
Services Framework Proxy - com.google.android.gsf-8.apk
Store (FakeStore release) - com.android.vending-16.apk
DroidGuard Helper - org.microg.gms.droidguard-14.apk
This is how I intalled microg on another phone and rom and it always worked.
So you have UnifiedNIp is registered in system - checked? For some reason I had to do the steps I mentioned to get it registered... hmm
DoR3M3 said:
Xposed showed a notification, I mean, you just looked in the logs, or how did you first know?
What is SatStat, OSM and others?
How are you installing microg? I just installed the apk is all, these versions and in this order;
Services Core - com.google.android.gms-12221403.apk
Services Framework Proxy - com.google.android.gsf-8.apk
Store (FakeStore release) - com.android.vending-16.apk
DroidGuard Helper - org.microg.gms.droidguard-14.apk
This is how I intalled microg on another phone and rom and it always worked.
So you have UnifiedNIp is registered in system - checked? For some reason I had to do the steps I mentioned to get it registered... hmm
Click to expand...
Click to collapse
I noticed I had an issue with FakeGapps because the MicroG self check showed that sig spoofing failed. At some point after that, I found the Xposed logs showing many errors for Null Pointer exception. I searched around but could not find anyone else with the issue. I submitted an issue on github.
SatStat, OSM are open source apps that will show location on a map. They are able to locate me so I know it is working using UnifiedNlp Settings (shows in the Setting > Location settings).
I installed microG using NanoDroid 17.7 using the full package.
How did you install Xposed?
Ok on NanoDroid 17.7...
DoR3M3 said:
How did you install Xposed?
Ok on NanoDroid 17.7...
Click to expand...
Click to collapse
I installed Xposed Framework 90.2-beta3 systemless through Magisk.
I'd use the Xposed Installer - XposedInstaller_3.1.5.apk;
https://forum.xda-developers.com/showthread.php?t=3034811
But I've learned a trick with it, flash rom and magisk, then install Xposed as the first app, and install the framework from within Xposed 'Install/Update' click cloud on right...
P.S. I'm not using Xposed any longer since it will break SafetyNet check....
Welcome to the XDA home of Webview Manager by Androidacy
Read about it on our blog:https://www.androidacy.com/tag/webview-manager/What is this?This magisk module allows to install several webviews and browsers, replacing the stock one with more privacy friendly/better performing browser and/or webview. By default this module will install Bromite.
Can I use older versions?No.
Why use different webview or default browser?These webviews are de-googled or more privacy friendly, or just more updated, or better optimized. Because it's better than Google or AOSP webview.
Why not other methods?These usually involve directly modifying system and are less versatile and more incompatible. In addition, thanks to auto updates and dynamic system detection, you know you get the right files without extra bloat.
Systemful installSystemful install is not supported and we currenly have no plans to change that.
ConfigurationConfiguration is done during install, thanks to @Zackptg5 magnificent Volume-Keys selector with a touch of our own spice.
Getting supportZip /sdcard/WebviewManager/logs, and send along with detailed description of the issue including device name, ROM, and Android version.
LinksWebsite and blog is at https://www.androidacy.com
Donations are here
Beta/alphas: no longer available, due to an improved QA process.
ZIPs: click me
Telegram: Androidacy Discussions
Discord: Available to Patrons. See our donation link above.
reserved
reserved
Not sure, if this is relates to your module. I installed the module, but in developer settings, where I can choose the webview engine, bromite is greyed and it is written, it is not active for the user "me"... What should I do? I am on Linage for MicroG 15.1
doesnt seem to work on pixels. i think it is because the package name for webview is different on them.
what this module do?
gorillus said:
Not sure, if this is relates to your module. I installed the module, but in developer settings, where I can choose the webview engine, bromite is greyed and it is written, it is not active for the user "me"... What should I do? I am on Linage for MicroG 15.1
Click to expand...
Click to collapse
disable chrome
It's a preferred webview package and will be used no matter what if installed
pbanj said:
doesnt seem to work on pixels. i think it is because the package name for webview is different on them.
Click to expand...
Click to collapse
Package name being different
I wouldn't be surprised if Google blocks it though; the stock ROM probably only will allow Google packages
kos25k said:
what this module do?
Click to expand...
Click to collapse
Exactly what it says
anyway to exclude the actual bromite webview from the zip and script it detect architecture and download correct version and install as system since the filesize is awfully large 150mb+!? i guess that'd make it only work in magisk manager and not twrp flash.
clcombs262 said:
disable chrome
It's a preferred webview package and will be used no matter what if installed
Click to expand...
Click to collapse
Well it was kind of the opposite. I disabled the default webview (Lineage OS) and installed the Bromite Module afterwards. Now I re-enabled webview, which was no longer the default, but Bromite. So it works, if you don't disable default webview, because Bromite is a replacement. Never had chrome installed btw.
Problem is the version is kept anonymous.
So there is no easier way to find what version of Bromite u r flashing.
No details in Magisk module, nothing.
I mean, I know u can't keep the browser up-to-date, but that doesn't mean, u need to hide it too. It dumb thing to do.
JohnWrick said:
Problem is the version is kept anonymous.
So there is no easier way to find what version of Bromite u r flashing.
No details in Magisk module, nothing.
I mean, I know u can't keep the browser up-to-date, but that doesn't mean, u need to hide it too. It dumb thing to do.
Click to expand...
Click to collapse
We don't hide anything; the app version is easily found under app info
Sent from my Moto Z3 Play using XDA Labs
DvineLord said:
anyway to exclude the actual bromite webview from the zip and script it detect architecture and download correct version and install as system since the filesize is awfully large 150mb+!? i guess that'd make it only work in magisk manager and not twrp flash.
Click to expand...
Click to collapse
It was chosen to do it this way because the last attempted way broke versions 1.4-2.0, we just aimed for a stable version
Thanks for the feedback though, we'll definitely consider it in v3.0
Sent from my Moto Z3 Play using XDA Labs
clcombs262 said:
Exactly what it says
Click to expand...
Click to collapse
but it doesn't say.it converts chrome to work with other view?
kos25k said:
but it doesn't say.it converts chrome to work with other view?
Click to expand...
Click to collapse
Because it doesn't
It de-systemized chrome so it won't act as a preferred webview
Sent from my Moto Z3 Play using XDA Labs
Weird, I installed this module on Xz premium (stock pie) but it's not showing in selection of webviews, in developer settings ,not there at all.
I use Google-free Chinese version with NanoDroid installed.
I don't think it's module problem, it appears in list of system apps,but system doesn't recognise it as Webview.
Edit: just tried to push apk into system, results are the same.
Theoretically if I repack apk with the same name as android Webview maybe system will recognise it.
Good evening, first friend, excuse my English, I use Google translator! I installed on my Xiaomi S2 Android 9 Miui10 and everything OK. Only application that gave bad was OLX. Reminding friends that I installed Magisk and used the Titanium backup to freeze the Google View.
Not working on the few AOSP / LOS ROMs for the OnePlus 3 I've tried.
Module installs but there's no Bromite webview under developer options
Anyway I have to uinstall it because I couldn't open Gmail and other apps behaved bad, i.e exit itself.
Waited few days, rebooted but nothing worked.
Device: 1+5, Magisk, Twrp, Oxygen Os Latest
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!