Related
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
Updated on July 3, 2018:
(reason in post #636)
MicroG in post #396, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
Open GApps in post #416, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible. It also performs a one time nice Google setup of the unit, beginning with language, account, and so on.
Note to all using this firmware for the first time: since it is differently partitioned from what you had before, you must also perform a wipe all in recovery, ideally just before the first startup (to avoid wasting time), or at any time now.
WARNING: MicroG Core and LP don't work well: contacts are not seen from apps like Hangouts, Google/Voice Search, while True Contacts needs local loading of profile & contacts - from vcards on the internal SD. Therefore I strongly recommend the Open GApps version!
Note also that with the MicroG version, the gms core app must be configured, and Hangouts' service called NetworkConnectionCheckingService must be disabled, for Hangouts to work:
Code:
pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService
TomTom GO storage support is explained in post #45.
TT GO spoofing is in post #392.
Poweramp's early start&restart is also supported by default.
Phone calls via a BT connected phone could be dialed by (always) selecting the MTC Service(aka Headunit), as the preferred dialer.
MTC Sound direct sound control is readily supported, if the associated hardware mod is also done.
Automatic screen brightness control based on location&time is also implemented by default.
Blank logo kernels are in post #600 (get them while they last).
Developer Mode in post #332.
Firmware is also rooted and xposed.
To those who make outlandish claims about this firmware: they are either trolls or firmware is not for them. However firmware supports all rk3188 MTCB or MTCC units. Make your own judgement, and don't get scared away.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
===
Here's another one: in principle, unless an unlikely bug is reported, I don't reply in this thread to users who are not listed as saying thank you to this post.
===
Mod Edit :- Content Removed
Thanks @dsa8310 .. your rooms are great .. I installed microg rom yesterday . Works great . Will try the new one soon. The only question I have is the performance of both roms similar coz I have 1GB Ram
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396.
Open GApps in post #416.
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Hi @dsa8310, is it possible to find what version of your firmware that I have installed in my radio. I think I updated yesterday, but not sure if it the recent one that you posted yesterday.
Maybe a tall tell signature or something to look for.
Again, thanks for your work on the firmware. And I hope this section works out for you.
Wayne
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
As usualI I ll be putting the ROMs on the fileserver for everyone.
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
dsa8310 said:
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
Click to expand...
Click to collapse
I have the 6/28 one.. MicroG I guess. Getting Gapps..
Thanks bud.
Like to donate as well..
EagleSoldier said:
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
Click to expand...
Click to collapse
I now use the (pico) Open GApps enabled version. I like it because I don't have to configure things and it is 100% Google compatible. I dislike it because of Google ads' undisturbed presence, unlike the MicroG version that avoids them, partially, at least for my set of apps.
There might be observable differences in their footprint size (necessary RAM) and load of system (background tasks). I can't say for sure, since I have a 2GB RAM (upgraded) unit. Furthermore, I run the same set of apps most of time: Poweramp and TomTom GO which have the same heavy requirements (TT mainly).
Perhaps 1GB units should use MicroG while 2GB ones could afford the Open GApps version.
A technical comparison between versions could be done, in a terminal (termux), with commands like "free -m" (free memory) and "uptime" (busybox uptime) (for load average); "busybox ps", too, if implemented.
But, ultimately, it's a matter of feeling: if you feel that one version is more responsive, feel free to use it.
(switching back and forth is facilitated by the same partitioning, though going through a wipe all in recovery seems necessary)
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
ankerede said:
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
Click to expand...
Click to collapse
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
dsa8310 said:
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
Click to expand...
Click to collapse
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
ankerede said:
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
Click to expand...
Click to collapse
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396, and here:
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
Open GApps in post #416, and here:
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
elyl said:
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
Click to expand...
Click to collapse
No, they are not.
It's possible, but then uninstall by hand three apps: com.google.android.gsf, org.microg.gms.droidguard, FakeGapps1.1, and then reboot.
Hi dsa,
i'm on your latest microg version of your firmware with the playstore. But when i open the playstore and try to connect i get this error: [RH-01]
any idea?
problem iam facing now i cant play music while using google maps, any help?
dsa8310 said:
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
Click to expand...
Click to collapse
I give it a + for GApps. Still works nice with Google Play and able to use what you paid for with no issues.
Finally got more play time with the latest and I like it.. Using 1G, no upgrade memory at all..
Still need to add a few more apps.. but good to go..
Thanks @dsa8310
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
dsa8310 said:
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
Click to expand...
Click to collapse
Exactly what I did. A setup that I have never seen before had to be done. Great Job.
It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question.
Instead this thread is intended to share experiences as I spend quit some days to become my phone as free from Google.
I did this on a Galaxy A3 (2017) with LOS.
First of course is not to install Gapps. We can replace many of its functionality. First of all we need a store to download apps. I highly recommend FDroid as a first choise. You can download the app at their website.
With this you get a variety of apps for almost all, but not all problems. Nevertheless I recommend to take your time and check what is offered there, even if you used other apps before.
If you don't find an equivalent, you might want access the google playstore. In FDroid there are two apps available for this purpose. With both you can anonymously access all (not payed) apps on Playstore. You can of course login with your google accound, but ... ok, that's not so anonymous anymore
What else do we miss without Gapps. There is a way of receiving push notifications, that is often handled via GCM (google cloud messanging).
First of all we need to enable spoofing. This was quite a challange, as usual tools (tingle, ...) work with non-odexed ROMS, while that for A3 is an odexed ROM.
Finally I found a zip here, that works for me:
https://forum.xda-developers.com/showpost.php?p=77456471&postcount=3775
Download that zip, goto TWRP.
Before installing it you have to do two steps.
Mount /system
Create a link (with advanced/terminal): ln -s /system/vendor /vendor
Otherwise install of this zip will fails. Be patient, it takes around 5..10min to pass.
Now we can work with microG, that will replace some google-APIs.
Add the repo "microg.org/fdroid/repo"
Then install micoG core, fakestore and proxy.
To get unifiedNLP running (this is for location services) the microG core must be a system app.
So do a reboot in the TWRP. Mount system first.
Than copy with integrated filemanager the folder com.google.android.gms-xxxx
from /data/app/
to
/system/priv-app
and reboot.
You will find in your app-overview the microG app - please open and let selftest run.
Enable permissions there and also disable battery optimisation
unifiedNlp should be registered. Next is to enable them.
Download from FDroid these two apps:
Local GSM Location (with this you can download a database of cell towers and their location, giving you a chance to get a rough estaimatin where you are, without waste of energy for GPS)
and
NominatimNlpBackend (to get your position as street/city/country instead of coordinates).
Very important:
Apps that require this gapps need to be installed after microG. Otherwise they will not work properly.
I guess that are usually apps that needs location.
Feedback for microG installation
I´ve tested your microG installation these days. Worked like a charm ! Thanks for your post.
The Nanodroid patcher referred in your link was gone, so i used http://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-18.1.20180909.zip.
I had the same problems with Yalp downloads you´ve described earlier, after reboot it worked.
GCM works, but just not with Threema ;-( But it´s a known problem.
Getting NLP to work was a little bit of hassle, but I found many articles about it. Was not sure which of the backends to use, there are many.
What is interesting - I didn´t use encryption and patched the ashyx_no_encryption patch right after flashing LOS and I didn´t use SU or Magisk right now. Result: absolutely no boot loops and no reboot after power off !
From which stock variant you came ?
@cyberbix:
The patcher for spoofing was quite beta at that time. Did you have to do any preparations to let it run? I remember in TWRP I had to mount /system and create that /vendor-link. Is it still required? I reported my issued there but I am not sure he cooked it with these patches finally.
The Yalp issue is completely independent on microG. It seems that there is a bug in the Downloader of LOS15.1. There are others suffered from this issue, not just the A320FL. The workaround to use internal download works.
Can you give more details about the NLP-hassle? That might help others to not go that painful way. Imho all is fine if you copy (or move) the folder I described above and reboot.
About the backends ... I think there is no alternative for Nominatim, which works only online. For the cell bases location I prefer a offline solution, I found that "Local GSM Location". The microG-Packages usually contain the mozilla-online backend.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I had latest Oreo 8.0 installed before. But I am not sure whether or not I updated the bootloader too with Odin.
@starbright_
Did you have to do any preparations to let it run?
Yes. I did exactly the same as you did in TWRP.
Can you give more details about the NLP-hassle?
I wasn´t sure if its needed at all and even if microG went green, the backends seemed not wo work at all.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I did it in the same way as you. Flashed the patcher, installed the rest from FDroid. That´s it.
Moreover: i didn´t install Magisk or any other root and I didn´t use Xposed. I used the push notification tester to test GCM. Everything was fine.
I can check if installing an su package or Magisk will lead into the same problems.
Installed Magisk on top of your microG setup. Everything works, see McFys thread. I guess you just didn´t read what TB tells about SU.
starbright_ said:
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question..
Click to expand...
Click to collapse
My experience below:
-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green
-yalp works fine, i like it, but in the end i had to use my goggole account instread of the experimental 'internal account' and this because of gmaps
-gmaps works fine BUT it doesn't find the current gps position unless i restart it (long press on back arrow). This is odd because other map-apps (openstreet, tomtom..) work! Also, when i need to use the google account to save some locations or simply the offline maps, it does work only for the first time, later it doesn't recognize my (already set) googke account
-i don't know if it's related to microg but camera doesnt find the gps, while opencamera yes, fotej camera neither
-again, i don't know if it's related to microg but each time i add the google account i loose my contact list
-apps that need to talk with playstore doesn't work at all, I wanted to use Europe3D by geoflier and it didn't load properly until i installed also the playstore
- the same for those apps that need to purchase some addons
-BUT worst, above all (crying) is that the speechTotext is not wotking and it's a feature I really miss!
I don't know if a proper patched rom would work better, I always hope that mcFy finds some time to release the rom already patched.
Anyhow next days I will try to reinstall the stock rom to see if these behavioours happen also there.
I did another installation again. More details next.
But finally I gave up. I couldn't solve two issues
- neither telegram nor whatsapp works after a few minutes (doesn't wake up at incoming calls)
- heavy instabilities with LOS15.1/Magisk/Xposed/microG
I didn't find which component is responsible for that, but I remember that I didn't always get SU with Magisk. After a reboot it works again.
Even such components as DuckDuckbrowser crashed.
I couldn't recover my apps backup by TB from my previous S5mini on A3 with TB and Magisk (Parser error).
I need a rest from all this stuff.
starbright_ said:
I
I need a rest from all this stuff.
Click to expand...
Click to collapse
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
pink0 said:
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
Click to expand...
Click to collapse
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means this.
I installed localGSMbackend which created an offline database with celltowers. This works fine in energy saving mode I get a rough position without any waste of energy or privacy (as offline).
Altogether I did at least 20 complete wipes and started from scratch.
At the first I started early with root (either Magisk or LOS-addsu).
Than there are two options to get a spoofed ROM.
Either via Xposed/Fakestore module or via nanodroid patcher.
Both works in general.
Than installed microG (different ways - manually, nanodroid, unofficial installer, that are the 3 options I know).
But it always become instable. Apps don't get root anymore or does FC ....
So I did it another way around.
I first installed all required via FDroid (without any root, Xposed ...). That seems to me rather stable. The good thing: this are around 80% or apps I need. Than I did a backup, so that I don't have to starts from scratch, which is painful as hell with around 40 .. 60 apps.
My last attempt was after that install Magisk, Xposed, Fakestore. Spoofingchecker was red, but a microG gets green.
I installed it with nanodroid (created first with setup wizard a file, so that only microG and mapsapiv1) gets installed.
This was first time my apps work fine with maps. Other attempts to manually install the maps framework/lib wasn't succesful (why ever).
Problems started when installing TB. First it doesn't get root permission. After a restart it works, but I get parsing errors. If I understand FAQ this is due to different busyboxes ?!? Ok, the backups I created at another device with LOS14.1 and addsu.
But this was not the only issue. Browser crashed and I never get neither Telegram nor Whatsapp to get wake up after a few minutes of deep sleep (they arn't get registered at microG too, so this might be another issue).
@pink0:
Did I understand it right, you use GMaps?
@cyberbix:
My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Does your system keeps stable after all?
To be honest, that Magisk and Xposed seems to add to much intrusive stuff that might fail altogether. But even with the manual way it wasn't perfect. Maybe after a rest and with the next version from McFy I try this again. Good luck I didn't sell my old S5min til now.
starbright_ said:
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means
@pink0:
Did I understand it right, you use GMaps?.
Click to expand...
Click to collapse
it's here i writed down because my personal memory buffer, at my age, is really small
yes gmaps is working quite good except the behavour I wrote, but enabling developer options I can easily kill the program to get the new/current position (also I noriced tgat because of this gps problem ir cannot calculate any route while navigating)
I also dislike the idea of using xposed bexause I never needed it but now it's different
about telegram/whatsup i'm not using such softwae so I can't say what's wrong
starbright_ said:
...My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Click to expand...
Click to collapse
I do not use WhatsApp, I use Threema and Threema has known problems with microG GCM.
starbright_ said:
Does your system keeps stable after all?
Click to expand...
Click to collapse
Yes, but I didn´t flash Xposed, just Magisk.
Ok.That spoofing can happen via Xposed Module or nanodroid patcher. For non-odexed ROMs are more options (tingle,...) but not for ours.
So after all I am now happy with my current installation:
- install TWRP via ODIN
- Wipe in TWRP (system, data, cache, dalvik)
- install Lineage via TWRP
- boot into system
- install FDroid
install and setup most of needed apps - there is a good selection of apps in FDroid now
- Create Backup (via TWRP)
- Install Magisk (viaTWRP) and Magisk Manager in LOS
- Setup adaware and afwall (both from FDroid as they need root)
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
- install Yalp from FDroid and via Yalp the missing apps that are not available via FDroid.
I found that Telegram (and Whatsapp not 100% sure yet) push-notification work. I disabled battery optimization for both.
starbright_ said:
So after all I am now happy with my current installation:
[...snip..]
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
Click to expand...
Click to collapse
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
pink0 said:
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
Click to expand...
Click to collapse
I am not sure, but the LOS15.1 for A3 2017 (by @McFy from 08/21) ROM is in a state you need the patcher. Other methods (as tingle - what I used before with other mobiles) don't work.
Not sure what is odexed and deodexed. The only other method works for spoofing is Xposed framework. There is a module that fakes this. But until now I did't see a need for Xposed and I don't want to increase complexity. (From that point of view I rather should go for addsu instead of Magisk)
I did first a Magisk installation, as root is more important and you have later the chance to chose between microG and Gapps. (Did it step by step with backups not to start again from scratch).
But I didn't use Magisk for installation, but TWRP. How does it works? I am a Magisk newbee.
An update of LOS15 requires to redo it. I also updated microG in this sequence. Just as a short summery:
- boot into TWRP
- wipes system/cache/dalvik
- installed new LOS
- installed Magisk
- reboot into system (just for curiosity, probably not required) and back to TWRP
- let run uninstaller of microG (I used the zips from here: https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- install (run) the patcher (be patients, that takes long time, maybe 15min)
- install (run) setup wizard (selected only few things, as maps-api, can remember exactly)
- install the real package (install what has been selected in setup).
check this out https://hackernoon.com/e-first-beta-soon-to-be-released-82d7ec950dd
basically, this is a LOS-based rom including microG, aiming at avoiding google applications/usage.
or https://download.lineage.microg.org/a5y17lte/
Nominatim backend
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
cyberbix said:
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
Click to expand...
Click to collapse
My selfcheck gives just 2 unchecked points:
Playstore signature (I installed Fakestore+Yalp and Fdroid)
Radiocell based location (altough Nominatem is setup).
"Playstore signature" I could manage after apply permission spoofing to Fake Store (system app).
But, I don't get any app registered, although I have enabled Google registration and GCM.
I even deinstalled ebay and installed it again - no effect. ?!? What can I do?
I remember @cyberbix mentioned the Push notification tester:
It fails for me with step1 - "No register" ?!? How can that be? What did I miss.
[/COLOR]
starbright_ said:
?!? How can that be? What did I miss.
Click to expand...
Click to collapse
Did you do the device check-in ?
See https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/
What is push notifcation exactly claiming ? Unable to register or missing Play services ?
I am no longer working on this, or updating any information here! This was created back in the day of Oreo.
I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T.
/e/OS documentation - OnePlus 5T
Info about OnePlus 5T - dumpling
As of this post edit on 10/20/22 I'm using 'e-1.4-r-20220922220394-dev-dumpling' and /e/ uses microg. It runs quite nice, so check it out!
NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.041719 - (Read the second post for changes!)
OOS[microG] - Better performance, basic and simple, customize it your way!
No more proprietary Google Framework & Play Services!
No more OnePlus Data Analytics!
OOS[microG] comes with native support built in for microG and Signature Spoofing!
OOS[microG] is based on 1 year of experience on several devices, also hundreds of hours went into the preparation and making of OOS[microG]!
OOS[microG] is OxygenOS stripped down and more basic, allowing you to start installing it your way! There's not even a browser in OOS[microG], install what you want!
The point of OOS[microG] is to be as Google Free as possible, to offer better Performance, Security, Privacy, and Freedom without the Google Framework & Play Services!
OOS[microG] is not as complete a Google ROM as OxygenOS, but it still uses and requires a few Google applications because of how OnePlus created the ROM.
OOS[microG] uses F-Droid to access "Free Open Source Software", you can also install Aurora Store or Yalp Store which downloads directly off of the Play Store servers for any other applications you want.
Please be aware that OOS[microG] plays no part in the development of any application installed!
If you have any problems please be specfic, with as much detailed information as possible, so that issues can be investigated properly!
Please read this entire post before making any replies, as it may answer your question(s).
Features
Full ROM Deodex
Android & OnePlus setup wizards disabled
AOSP WebView & Google WebView
App permissions - "Spoof Signature" listing
boot.img patched - sepolicy for Oreo Deodex
EasterEgg removed
framework-res.apk patched - microG, signature check, signature spoofing
Gapps & OnePlus applications debloated
Google backup removed and disabled
Google Calendar & Google Contacts Sync support enabled
OnePlus Account removed
OnePlus bug reports/log removed and disabled
OnePlus Data Analytics applications removed and disabled
OnePlus Forum removed
OnePlus Photos Online removed
OnePlus Weather removed - not supported in microG
OnePlus "Notifications" "User experience program" and "System stability improvement program" removed and disabled
open.oneplus.net added to the "hosts" file to help block online Data Analytics
OxygenOS OTA update removed and disabled
RZ v3.7.0 Kernel - suspicious OnePlus services patched
services.jar patched - signature spoofing
System permissions added for microG support
8 new wallpaper added
Additional Applications
AOSP Keyboard - UI changes and Mic removed
AOSP WebView
DejaVuNlpBackend
FakeStore
F-Droid
F-Droid Privileged Extension
microG - NanoDroid version
MozillaNlpBackend
NominatimNlpBackend
Not Working
Because OOS[microG] is OxygenOS stripped of the Google Framework & Play Services, some applications and features will not work at present, these issues are being investigated, maybe in time they will be supported! Hopefully the lack of these few features will not discourage those from the many other benefits of OOS[microG]!
Gallery applications - "Share button & "Set as"
OnePlus Weather - (removed)
Because of the modifications needed for the framework-res.apk, the Gallery "Share button" & "Set as" will not work. Without these changes to the framework-res.apk the alternative would be the need for Xposed in the ROM, maybe in time this situation might change.
FAQ
Q: What is OOS[microG]?
A: OOS[microG] is a stripped down version of OxygenOS 5.1.7 that uses microG instead of the Google Framework & Services!
Q: What is this Performance, Security, Privacy, and Freedom being mentioned?
A: The Google Framework & Services do not offer the same Security, Privacy, and Freedom, mainly because of the "Proprietary Nature". The Google Framework & Services are also heavier on system resources, whereas microG is much lighter, so they lack the Performance that microG offers!
Q: OOS[microG] is for Oreo?
A: Yes - At the moment this is Oreo 8.1.0
Q: Can I Root OOS[microG]?
A: Yes - OOS[microG] can be Rooted like any typical ROM, it was tested on Magisk 18.0!
Q: Is OOS[microG] completely free software?
A: No - it still has OnePlus' proprietary software to support their hardware, and a few of their own proprietary applications, also a few Google applications are still installed because of how OnePlus created the ROM.
Q: Will OOS[microG] pass SafetyNet with microG?
A: Yes - Please see the "SafetyNet" section below!
Q: What is microG?
A: microG is basically a replacement for the Google Framework and Play Services, to allow you to still access all of Google's services, and use applications that rely on them, please see https://microg.org/
Q: Does everything work with microG?
A: It is not 100% perfect, so you might run into an issue with either an application or functionality that relies heavily on the Google Framework & Services.
Q: Is battery life better with OOS[microG]?
A: Yes - microG is lighter on resources which improves battery life, whereas the Google Framework & Services are heavier on resources causing more battery drainage.
Q: Why do you use the NanoDroid's version of microG and not the Official microG?
A: The Official microG sometimes doesn't get development as fast, and thanks to the great work of the NanoDroid project, NanoDroid-microG is getting faster development. Please be aware this is still the Official microG with fixes/changes added in by the NanoDroid project!
Q: Isn't it better to just use Custom ROMS?
A: It depends - If Custom ROMS are not using microG, then you don't have the same Performance, Security, Privacy, and Freedom, they are still reliant on the Google Framework & Services which are proprietary and not free, so less Performance, less Security, less Privacy, less Freedom, also heavier on resources, with microG it's the complete opposite! Custom ROMS also need good development to support a manufacturer's hardware, like the camera on the OnePlus 5T as an example. The hardware from manufacturers is typically supported by proprietary software, and depending on the Custom ROM development, trying to support this hardware can be easy or difficult. Using a ROM developed by the manufacturer offers the best hardware support, but of course manufacturers all use Google. For those looking for alternatives away from Google, and the best hardware support, this is where OOS[microG] steps in!
Q: Can't I just run a ROM without any Google or microG and still have it all work the same?
A: No - If you want an Android phone with a lot of features and functionality, otherwise it's going to be very limited. At the present moment you need either the Google Framework & Services or microG. The job of microG is to replace the Google Framework & Services so that you have all the same features/functionality, localization services, push notifications, Google Cloud Messaging, Maps API, etc., not to mention all the applications that are reliant on the Google Framework & Services, that won't work if you don't have either the Google Framework & Services installed or microG!
Q: I thought Android was Open Source and Free?
A: Yes and No - The core of the Android source code is known as Android Open Source Project (AOSP). However, proprietary software developed by Google known as the Google Mobile Services (GMS), is not a part of the Android Open Source Project (AOSP).
Q: Why does Free Open Source Software matter?
A: There are of course Pros & Cons between Proprietary and Free Open Source, but if Freedom, Security, or Privacy, along with Performance on the subject of microG, if any of these matter to you, then you need to investigate this for yourself. This subject matter is to indepth to fully explain here. These are a few links to point you in the right direction;
https://www.fsf.org/
https://en.wikipedia.org/wiki/Open-source_software
https://en.wikipedia.org/wiki/Free_and_open-source_software
Q: What is F-Droid Privileged Extension?
A: It allows F-Droid to install and uninstall applications without needing the unsafe "Unknown Sources" to be enabled. F-Droid can then install updates in the background without user intervention needing to click "Install".
Q: How can I get paid applications?
A: For some applications you might be able to download them through your account on either Aurora Store or Yalp Store, for others you might need to have the Play Store installed. If you need to use the Play Store, please visit the NanoDroid project on XDA for help with replacing FakeStore with the Play Store. It is recommened that you use the NanoDroid version of the Play Store which has been patched to work with microG for paid applications.
Q: Why do I see the Play Store listed for update when I add in the NanoDroid F-Droid Repo?
A: The FakeStore spoofs the Play Store as a replacement this is why you see it, you can ignore the update in F-Droid so it doesn't appear!
Q: What is this version of WebView installed and how do I update it?
A: This is the AOSP WebView, you can also install the Google WebView if you want to use it too. Whichever version you use be sure to enable it in the "Developer options" > "WebView implementation". Updates for AOSP WebView will appear on this post for you to download and install when they become available.
Installation instructions
Before installing OOS[microG]-5.1.7-3185.041719 you should check that it has the correct signatures.
Code:
MD5: 3d58a7ec85ba5d4e267c666f497a1643
SHA1: 30f8285caccd27acfc96e8a429ee31e9972b36f4
SHA256: a2ba548b75ddff1d31abd9a84e6f8f0528f81e3a553d725237bd0954463ec507
OOS[microG] is made from OxygenOS 5.1.7 Oreo!
Before installing OOS[microG] you need to wipe all of your partitions including the Storage, backup any data you have, then flash OxygenOS 5.1.7!
Next wipe all of your partitions including the Storage again, then flash OOS[microG]!
Install Steps:
Boot into Fastboot > fastboot -w
Boot into TWRP > Wipe > Format Data
TWRP > Advanced Wipe > Check all except USB
TWRP > Advanced > ADB Sideload > adb sideload OnePlus5TOxygen_43_OTA_040_all_1811051816_115c75d257934eea.zip
Boot into OxygenOS and allow it to run!
Boot into Fastboot > fastboot -w
fastboot flash recovery twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Boot into TWRP > Wipe > Format Data
TWRP > Advanced Wipe > Check all except USB
TWRP > Advanced > ADB Sideload > adb sideload OOS[microG]
Please do not post any problems you encounter if you don't follow the steps above, these problems might be related to doing a dirty flash, you've been warned!
Download
Be sure to download the latest version "OOS[microG]-5.1.7-3185.041719"!
Thanks to their generosity OOS[microG] is hosted for download at Android File Host!
https://androidfilehost.com/?w=files&flid=289145
OxygenOS 5.1.7 from OnePlus' Official Server.
http://oxygenos.oneplus.net.s3.amaz...3_OTA_040_all_1811051816_115c75d257934eea.zip
Post Installation
The Android Setup Wizard has been disabled, even though it's disabled it still runs in the background helping to complete the installation. When the phone first starts, if you notice an overhead notification from the "Android Setup", tap "NOT NOW" then "Never", there is nothing further you can do with the Wizard!
OOS[microG] comes with the DejaVuNlpBackend, MozillaNlpBackend, and NominatimNlpBackend for the Location Services for microG. The NominatimNlpBackend uses MapQuest's Nominatim service. For the NominatimNlpBackend you'll need to sign up for a free account at MapQuest to get an API key. There are also other plugins available through F-Droid to use besides the ones installed in OOS[microG], if you wish to use!
https://developer.mapquest.com/
Phone > Settings > "Location ( Mode - High Accuracy)"
microG - "Google device registration" - ON (Enabled)
UnifiedNlp Settings - check mark all - DejaVU, Mozilla, Nominatim
"Address lookup" - Nominatim - pick MapQuest!
F-Droid > Settings - enable "Expert mode" - "Privileged Extension" will now be enabled at the bottom of the Settings.
F-Droid > Settings - Repositories - Add the NanoDroid Repo - https://nanolx.org/fdroid/repo so that you can update microG and the applications it uses!
Highly recommened for better performance/speed! - "Developer options" > Drawing - "Window animation scale" (Animation off) - "Transition animation scale" (Animation scale .5x) - "Animator duration scale" (Animation scale .5x)
Changing the "Drawing" settings in the "Developer options" might appear jumpy to some people, that is because the windows and applications will respond faster. If you don't like it, play with the settings to find what's comfortable to you. These settings that have been recommended are for people that want the ultimate speed.
Once you have completed all of the "Post Installation" steps, you should now see all the sections check marked under "Self-Check" in microG. Under the "UnifiedNlp status" section you should have 6 sections now checked, sometimes you have to give it a few seconds for all 6 to appear checked, either go out of "Self-Check" and return, or scroll up and down a few times. At any time, if you disable the Phone Location, or change the Mode, then you will see the "UnifiedNlp status" section with sections unchecked, and it will take a moment for them to all appear checked again, once you have all your Phone Settings for Location correct! "Google device registration" is also required for the Location Services!
SafetyNet
SafetyNet was tested and working with Magisk 18.0 & 18.1.
OOS[microG] doesn't come installed with Google's proprietary binary DroidGuard.
You'll need to download NanoDroid-microG from the NanoDroid Project on XDA for DroidGuard. It is located in the "/system/app/DroidGuard" folder.
You will then need to boot into TWRP and mount "System", from your computer run; adb push DroidGuard /system/app
Use the file manager in TWRP to verify that you now see /system/app/DroidGuard/DroidGuard.apk
In microG make sure that "Google SafetyNet" is ON and upper right, "3 dots > Advanced" - make sure "Use Official Server" is marked!
Open Magisk, in the menu tap "Magisk Hide" and check "microG DroidGuard Helper" & "microG Services Framework Proxy" to hide them! Now tap, "Tap to start SafetyNet check", it should pass! SafetyNet passed in OOS[microG] testing, see the screen shot below!
Updating microG
OOS[microG] uses the NanoDroid-microG version, to keep it updated, place the NanoDroid F-Droid repository in F-Droid.
F-Droid > Settings > Repositories > Upper Right + > https://nanolx.org/fdroid/repo/
FakeStore spoofs the PlayStore, so you will first notice an update for the PlayStore, which can be ignored in F-Droid. Do not install this update with only the FakeStore installed!
Parallel Apps
If you use Parallel Apps it will create a second version of microG in the App Drawer. The second version of microG is not needed and should be removed. To remove it, press and hold on the icon, when the menu appears tap on "App info", then it will take you to microG's "App info" page, tap "Disable" to disable it. You should no longer see the second version in the App Drawer.
Hit the THANKS button it keeps me happy and motivated!
Watch this section for Announcements, Updates, ChangeLogs, ToDo, etc...
April 18 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.041719
ChangeLog:
microG Dirty-227 that was updated in the last release of OOS[microG] was crashing the Gallery application, so the previous version of micoG Dirty-167 was put back into this OOS[microG] release!
To update to a new version, read the Install Steps under the Installation instructions in the OP!
April 17 2019 - New Announcement
The latest update to Dirty-122 microG that was added in the latest release of OOS[microG]-5.1.7-3185.040519 has been found to crash the Gallery application.
A new release will come out shortly reverting microG back to the last version of Dirty-167 which is working fine!
April 06 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.040519
ChangeLog:
A few OnePlus & Google apps that were originally debloated have been added back in to help improve system performance.
NanoDroid microG updated to the latest version Dirty-227
AOSP WebView updated to version 72.0.3626.121
To update to a new version, read the Install Steps under the Installation instructions in the OP!
March 08 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.030819
ChangeLog:
Parallel apps is now working!
To update to a new version, read the Install Steps under the Installation instructions in the OP!
March 05 2019 - New Announcement
I've come to realize through more testing that the reason the Gallery Share button & Set As will not work, is because of modifications to the framework-res.apk, which are needed! Without these changes then Xposed would be needed in the ROM. Hopefully many will agree, that a lack of a few features such as these in the Gallery is a better choice, instead of needing Xposed. I'll keep looking into this situation, maybe in time I will be able to figure out a work around.
Parallel apps is now working, and I will release another update in a few days!
Have a look at the screen shots I've attached for Parallel apps!
March 03 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.030319
ChangeLog:
Additional apps removed for better performance, privacy, security - (mainly suspicious apps)
App permissions - New listing added for "Spoof Signature"
AOSP Keyboard added - UI changes and Mic removed
AOSP Webview updated - 71.0.3578.99
Calendar & Contact Sync added - Tested with Gmail
EasterEgg removed
Gallery - Share button & "Set as" not working
Google Webview added back in - (Now 2 Webview choices to use between AOSP & Google)
microG updated to the latest version
microG and GsfProxy both now have matching signatures for better support
microG Signature Spoof native support updated
Parallel Apps removed, not working in microG
Simple Keyboard removed
System permissions updated
Now you have the choice of using either AOSP or Google WebView! Before using Google WebView be sure to update it to the latest version!
To switch between WebView versions: Developer Options > WebView implementation
SafetyNet also tested and working in Magisk 18.1 - (Screenshot added in OP)
To update to a new version, read the Install Steps under the Installation instructions in the OP!
ENJOY!
Thanks! I'll test it right now
im try it Now.. thanks..
how to fix cst profile & basicIntegrity in magisk 18.1?
Yeah, that's the kind of ROM I was looking for ! I'm just gonna wait for the android pie version
Thanks for your job !
draentor said:
Yeah, that's the kind of ROM I was looking for ! I'm just gonna wait for the android pie version
Thanks for your job !
Click to expand...
Click to collapse
made for the most stable OOS firmware, in PIE OOS stable 9.0.3 is not the latest, because the PIE ROM base is too early
Is it only 5.1.17 we can install on... That's quite far back for Oreo..
Also do you mean 5.1.7 or 5.1.17 because you mentioned both
siliwangi said:
how to fixed cst profile & basicIntegrity in magisk 18.1?
Click to expand...
Click to collapse
The post has been edited over, see the new "SafetyNet" section!
Please don't make one post after another; known as "Double Posting", try to keep posts contained to one at at time, thanks...
dali786546 said:
Is it only 5.1.17 we can install on... That's quite far back for Oreo..
Also do you mean 5.1.7 or 5.1.17 because you mentioned both
Click to expand...
Click to collapse
That was a typo, thanks for pointing that out, fixed now, and it's 5.1.7
DoR3M3 said:
Even LineageOS microG doesn't come with DroidGuard installed, which is suppose to be needed for SafetyNet, they don't even talk about SafetyNet either on their website.
OOS[microG] doesn't come with DroidGuard becasue it's a Google Properitary Blob, and the point is to try and stay away from Google as much as possible, but it doesn't mean someone can't use it and work with SafetyNet on their, it's just not supported in OO[microG].
SafetyNet is difficult at times to pass, given Google is always making changes, you'll have to Google or check on XDA for SafetyNet.
That was a typo, thanks for pointing that out, fixed now, and it's 5.1.7
Click to expand...
Click to collapse
Is it only from main Oxygen OS branch, not the beta?
And any idea on ETA to pie?
Look at me asking a bunch of questions to a ROM that I tried to do manually. (I have disabled all Google tracking downloaded Firefox with extensions, disabled Google history... This solutions seems a hundred times better)
dali786546 said:
Is it only from main Oxygen OS branch, not the beta?
And any idea on ETA to pie?
Look at me asking a bunch of questions to a ROM that I tried to do manually. (I have disabled all Google tracking downloaded Firefox with extensions, disabled Google history... This solutions seems a hundred times better)
Click to expand...
Click to collapse
I've been so busy working on OOS[microG], that when I started the Pie firmware was not released and I haven't been paying attention to it, but now that I see it's been released when I get a chance I'll start working on a Pie version to release, don't have an ETA at the moment.
It's great to see replies and excitement, did you read my "microG - Deodex - Signature Spoofing - Debloat Gapps!" guide when you did all this manually?
https://forum.xda-developers.com/oneplus-5t/how-to/guide-microg-deodex-signature-spoofing-t3862961
DoR3M3 said:
I've been so busy working on OOS[microG], that when I started the Pie firmware was not released and I haven't been paying attention to it, but now that I see it's been released when I get a chance I'll start working on a Pie version to release, don't have an ETA at the moment.
It's great to see replies and excitement, did you read my "microG - Deodex - Signature Spoofing - Debloat Gapps!" guide when you did all this manually?
https://forum.xda-developers.com/oneplus-5t/how-to/guide-microg-deodex-signature-spoofing-t3862961
Click to expand...
Click to collapse
No i didnt use your guide to do that.
Feedback on the ROM
Love the concept and idea
It is however quite jumpy and lavgy (when scrolling or switching apps)
It didnt come with a browser and initially F-droid wouldnt install anything... Parse error. I rebooted disabled the extension then it worked. Re enabled it
Parallel apps isnt working and some apps that require Oneplus Framework crash.... OnePlus Weather
Apps that require GSF dont work. I tried loggijg into snapchat (it cpuld also be safetynet issue with snapchat tho)
Magisk returns safetynet error.... SNot failed safetynet... Just error i think to load it
dali786546 said:
No i didnt use your guide to do that.
Feedback on the ROM
Love the concept and idea
It is however quite jumpy and lavgy (when scrolling or switching apps)
It didnt come with a browser and initially F-droid wouldnt install anything... Parse error. I rebooted disabled the extension then it worked. Re enabled it
Parallel apps isnt working and some apps that require Oneplus Framework crash.... OnePlus Weather
Apps that require GSF dont work. I tried loggijg into snapchat (it cpuld also be safetynet issue with snapchat tho)
Magisk returns safetynet error.... SNot failed safetynet... Just error i think to load it
Click to expand...
Click to collapse
Have you ever used a microG ROM before? They all work the same, of course there are different versions of microG someone can use, but overall some apps are just difficult with GSF or SafetyNet.
If you're seeking help please be "Detailed" and "Specific", also the exact steps you've taken when you saw an issue.
Did you follow the post, wipe all partitions, install OOS 5.1.7?
Has Pie been installed on your phone, or a lot of 3rd party ROMS?
OOS[microG] is a Full ROM Deodex it will only lag when you first start it. If you changed the Animation in the Developer options as I mentioned, sometimes it might seem like it's jumpy because it moves faster, the windows will move snappier. So if this is the jumpy you are talking about, if you don't like the speed it gives, you can always change back to the default settings.
I explained in the OP that it doesn't come with a browser.
F-Droid works fine, did you dirty flash, or enable "Install unknown apps" on your phone?
OnePlus Weather does not work with microG. Are there other apps giving you a OnePlus Framework message/error?
When you look at the microG GitHub Repo, and the issue reports, based off of that, and how many apps are on the Play Store, the working percentage of microG seems very high. How many apps have you tried that are not working?
Nothing is 100% with microG like any piece of software, I have no control over this, for any apps that require GSF and OnePlus Weather please seek help and submit a report on the NanoDroid if you care to run microG on ROMS!
Parallel Apps appears to not work with microG, so it will be disabled in the next release. There are 3rd party apps that help with this...
P.S. See the OP it's been edited over, there's a new SafetyNet section that's been added!
I read all the things in op and great work doing this , also gone thru faq. I m sure the developers have spent hours an days which is great...but need to be clear what we are achieving with so much effort
But still not clear what is the single pressing point to do this , battery life ? Performance ? Do we know how much % it will improve when compared to same use with Google framework rom ? I m sure the developer did some baseline around this . Performance ratings ?
Other than battery life why would one not want to use Google framework , the way it sounded it to me is , Google is buggy and has lot of issues ,, but in my day to day use I don't experience anything like that
Just trying to figure out motivation for myself to try out this ROM
Manan79 said:
I read all the things in op and great work doing this , also gone thru faq. I m sure the developers have spent hours an days which is great...but need to be clear what we are achieving with so much effort
But still not clear what is the single pressing point to do this , battery life ? Performance ? Do we know how much % it will improve when compared to same use with Google framework rom ? I m sure the developer did some baseline around this . Performance ratings ?
Other than battery life why would one not want to use Google framework , the way it sounded it to me is , Google is buggy and has lot of issues ,, but in my day to day use I don't experience anything like that
Just trying to figure out motivation for myself to try out this ROM
Click to expand...
Click to collapse
I thought the objective was made clear?
OOS[microG] - Basic and simple, customize it your way! Faster, lighter, more private, more secure, better performing!
OOS[microG] was made with simple goals in mind, Freedom and Performance!
It doesn't sound like you have used microG in the past?
DoR3M3 said:
I thought the objective was made clear?
OOS[microG] - Basic and simple, customize it your way! Faster, lighter, more private, more secure, better performing!
OOS[microG] was made with simple goals in mind, Freedom and Performance!
It doesn't sound like you have used microG in the past?
Click to expand...
Click to collapse
No I have not used in past and many users are new I guess
But how can u say better performing have u done any benchmarking ? Private I don't care
Secure how ? ...aren't we secured now? Google scans apps and all ..not sure what secure means coz it is a big context
Lighter means what ? Less in size ? Or less battery draining ? Any benchmarking ?
Google is pretty basic and simple too from end-user perspective...I can customize most things
Freedom = what ? We already have freedom , don't we ?
Manan79 said:
No I have not used in past and many users are new I guess
But how can u say better performing have u done any benchmarking ? Private I don't care
Secure how ? ...aren't we secured now? Google scans apps and all ..not sure what secure means coz it is a big context
Lighter means what ? Less in size ? Or less battery draining ? Any benchmarking ?
Google is pretty basic and simple too from end-user perspective...I can customize most things
Freedom = what ? We already have freedom , don't we ?
Click to expand...
Click to collapse
I was only asking, because by understanding and knowing microG, the Google Framework & Services, you'd then understand these things you are asking.
OOS[microG] isn't reinventing anything, or creating anything new, it has only incorporated into OxygenOS what has exsisted for several years in Android & microG.
It's already mentioned in the OP that the Google Framework & Services are heavier on the system resources, that's a fact, because of it, you don't get the same level of performance or battery life as microG.
The Google Framework & Services are Proprietary, and because of this, there are of course many discussions on the differences of Proprietary vs OpenSource as it relates to Freedom, Privacy and Security, that is why these things are mentioned in this ROM. Google also has a past track record that relates to many of these areas, that bring concern to many users...
Since we are discussing a ROM, this is not just about end-user perspective that you only see when using it, but what is underneath the hood at the System Level. At the System Level Google is not so basic and simple, it lacks the Freedom you are asking about in that it is Proprietary, only Google knows what is in that code, and that also begs the question over it's Security, when you can't audit the code and know what it's doing.
DoR3M3 said:
I was only asking, because by understanding and knowing microG, the Google Framework & Services, you'd then understand these things you are asking.
OOS[microG] isn't reinventing anything, or creating anything new, it has only incorporated into OxygenOS what has exsisted for several years in Android & microG.
It's already mentioned in the OP that the Google Framework & Services are heavier on the system resources, that's a fact, because of it, you don't get the same level of performance or battery life as microG.
The Google Framework & Services are Proprietary, and because of this, there are of course many discussions on the differences of Proprietary vs OpenSource as it relates to Freedom, Privacy and Security, that is why these things are mentioned in this ROM. Google also has a past track record that relates to many of these areas, that bring concern to many users...
Since we are discussing a ROM, this is not just about end-user perspective that you only see when using it, but what is underneath the hood at the System Level. At the System Level Google is not so basic and simple, it lacks the Freedom you are asking about in that it is Proprietary, only Google knows what is in that code, and that also begs the question over it's Security, when you can't audit the code and know what it's doing.
Click to expand...
Click to collapse
Ok I mostly care Abt perf and battery...so will try it out ..thanks
Manan79 said:
Ok I mostly care Abt perf and battery...so will try it out ..thanks
Click to expand...
Click to collapse
If you care to wait a few days, I am releasing a updated version, there were some changes made...
Thanks Bro
This work deserve more attention.
Even if it's not on Pie, I don't care, it's just too good. Pie is overrated and barely at Nougat kneel.
Thank you.
EDIT : Continuation from a DM ;
It is absolutely perfect in almost every areas,smooth and debloated of ****, sadly I can't make it work with a game called "Girls frontline" , it basically says "can't install the app" via playstore.
Of course, I got some paid apps like themes, hyperion launcher and another game that works.
So i'm turning to you, as I don't really know why it is happening.
As for your update, I can't wait to get it, it could probably fly the small issue i'm facing.
Also, I did your guide several times since the first time you created it, for fun, and I learnt lots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Install Instructions(If coming from stock or another rom):
Prerequisites: Coming from stock rom with bootloader unlocked, Developer settings enabled, android debugging enabled.
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Install copy A/B partitions zip,
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these.
(5) Select Back arrow button
(6) Select Format Data Button. Type yes
(7) Select Install button. Choose rom zip. Swipe to confirm flash.
(8) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(9) Reboot. Phone will mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then take you to the lineage recovery screen. Use volume down button to select Factory data reset, press power button, select yes to delete data. Phone will reboot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM.
Upgrade Instructions(If coming from one of my previous builds):
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Select Install button. Choose rom zip. Swipe to confirm flash.
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache
(5) Reboot(6) If you had Magisk installed, you can then reboot into TWRP/Ofox and flash magisk.zip
Tips for Use
1. Root can be enabled in this build by going to Developer Settings->Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. Looking for a great camera? Try Hypercam for Moto G7 from gcambrasil at https://gcambrasil.com.br/motorola
1. After installing, go to internal storage, create folder "gcam" (without quotes), create folder "Configs" inside of "gcam," and place the Pixelmod_byJGB.xml (attached) file in that folder.
2. Open up Hypercam, double tap on black space near camera button, load Pixelmod_byJGB.xml file.
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & LimitsThis thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A and/or visit the Telegram group https://t.me/mG7Power. I'm happy to help but going to the telegram group or opening a Q/A thread allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
Download:
Change log
1. Latest March security update
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Mar. 5, 2020
Download link: https://www.androidfilehost.com/?fid=4349826312261741637
MD5: 54b467570f65ce85f164bd8e99943ab7
Older Versions:
Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Feb. 5, 2020
Download link: https://androidfilehost.com/?fid=4349826312261727435
MD5: aeb4aa1141c6d74ac016e8fba797c245
Next update news...:
Mar 10, 2020 - Currently working on USB-C audio during phone calls, increasing audio volume. Once USB-C audio gets fixed, I'll enable OTA updates.
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android...otorola_sdm632
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Rom Last Updated Mar. 10, 2020
Thread Info Last Updated Mar. 10, 2020
Guide on how to build your own posted here: https://forum.xda-developers.com/g7...d-lineageos4microg-16-0-t4070079#post82069641
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
clarkkentxda said:
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
Click to expand...
Click to collapse
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Bernie_nix said:
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Click to expand...
Click to collapse
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
clarkkentxda said:
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
Click to expand...
Click to collapse
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Bernie_nix said:
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Click to expand...
Click to collapse
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
clarkkentxda said:
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
Click to expand...
Click to collapse
Hypercam is ported from gcam so YMMV. Given that it works on this ROM with microg, if it has any hooks they probably aren't deep. I'd give it a go
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
flash713 said:
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
Click to expand...
Click to collapse
Glad you like it and thanks for your feedback; tip on root explorer pro.
Bernie_nix said:
Glad you like it and thanks for your feedback; tip on root explorer pro.
Click to expand...
Click to collapse
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
robson_89 said:
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
Click to expand...
Click to collapse
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
DanAlucard said:
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
Click to expand...
Click to collapse
That would be great!
In the meantime, i've built and updated my LOS 16 as attached - forgot to add screenshot previously.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
Not from me. I build this for personal use, share it and have no interest in a vanilla los build. Robson is correct. Go with his build of you don't want microg.
flash713 said:
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
Click to expand...
Click to collapse
Thank you for your kind words! I use busybox from osmosis via magisk module; yes, I enjoy magisk on this rom. Busybox (osmosis) actually makes apps like Titanium Backup work great if you've purchased a non-Google play license file from them. This rom is my personal build that I uploaded to xda and shared, and I plan on maintaining it for some time. So...Magisk flashed via twrp/ofox works great, and so does busybox magisk.
+1 on your comment about Hypercam. Completely agree about hypercam. I've tested a lot on this device and of course am open to suggestions.
I will update this rom via the Lineageos patches, however, the Feb update hasn't been pushed yet so no new rom for now. I have isolated a few bugs, e.g. usb-c for calls and am working on OTA, however, I am going to release a surprise test build in the next couple of days (hopefully). It's building as we speak, and I will test before releasing. Stay tuned, and I look forward to yours and others feedback and questions.
P.S. I am a linux user and believe in the power of open-source. If you or others have any questions or comments, feel free to reach me via the telegram link in the 1st post; I usually answer a bit quicker there but also answer on here. Best wishes and thanks again!
P.S.S. Welcome Robson to our open-source team! If any of you are looking for a lineageos build without microg, check out his post a couple of posts above.
generally audio is lower quality than stock rom, it's not as loud and not as clear.
clarkkentxda said:
generally audio is lower quality than stock rom, it's not as loud and not as clear.
Click to expand...
Click to collapse
Did you try the audiofx app that is included?
Bernie_nix said:
Did you try the audiofx app that is included?
Click to expand...
Click to collapse
Indeed sir, it doesn't help all that much for me though.
rottenwheel said:
I accompany this sentiment. It happens with most Motorola Moto G devices I own and use: if kept with stock builds both camera and audio have a far better quality than custom ROMs do. Motorola engineers do hell of a job when working on their OEM firmware. It is a real shame yet not so far from reality that we need to take these tradeoffs to obtain better privacy.
An idea that comes to mind is for us to debloat the stock build, bake in microG and possibly update security patches as they come out. Motorola Moto G1 (falcon) has something alike with IDCrisis - https://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595
Thank you for the heads-up, though. I definitely love the audio on stock.
Click to expand...
Click to collapse
Unfortunately you can't do that with stock. Microg requires signature spoofing enabled in the ROM which is a patch applied when building a ROM. You could try patching stock to enable signature spoofing with a tool like Heystack but it most likely won't work on stock. Another route is using another ROM with signature spoofing support e.g. crdroid or omni, applying signature spoofing patch if necessary and then patching in twrp with something like nanodroid patcher.
That being said I am working through desired edits and bugs in this ROM but can't provide any ETAs. I encourage anyone with a bit of coding experience or interest to build their own and learn. Making changes to rom builds is not hard, just time consuming and unfortunately doesnt pay the bills...so its done in hobby time. I do plan on maintaining this ROM for some time though and will probably be on Pie longer than most users until 10 is ready; right now 10 has way too many bugs for me to use or build for daily driver material.
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Usage with my Proton Kernel is recommended to get the most out of your phone. The ROM does not include Proton Kernel, so you will need to flash it yourself. The ROM will still work with other kernels, but you will not get the benefits of Proton Kernel.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Thank you very much for posting this. I'll definitely be checking it out. Your Proton kernel is quite good already. Interested to see how the ROM functions too.
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
GoldElocks said:
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
Click to expand...
Click to collapse
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
letrain02 said:
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
Click to expand...
Click to collapse
microG is supported on the non-gapps build, not included. The gapps build includes full gapps.
Thank you for awesome rom, big plus for microg support. Will flash as soon as my Bramble arrives.
did flash all. now google logo, then a fire with beaker on screen.
edit: nevermind...guess that was the loading screen. took a few minutes. didn't seem like a "loading screen"
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Estebanium said:
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Click to expand...
Click to collapse
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
kdrag0n said:
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
Click to expand...
Click to collapse
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Estebanium said:
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Click to expand...
Click to collapse
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
kdrag0n said:
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
Click to expand...
Click to collapse
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
GoldElocks said:
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
Click to expand...
Click to collapse
Ocwa said:
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Click to expand...
Click to collapse
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Estebanium said:
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
Click to expand...
Click to collapse
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
OptoChip said:
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Click to expand...
Click to collapse
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
kdrag0n said:
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Dynamically sized partitions explains the "no free space" (and it makes total sense to layout the system partition this way). I was trying to use Magisk Systemize, took me revisiting it to realize that I didn't have Busybox installed. Installing the Magisk BusyBox module enabled me to Systemize the Phone app. Many thanks!
kdrag0n said:
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
wilspeak said:
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
Click to expand...
Click to collapse
Yes. The hotspot option comes with it from what I have tried.
J-I-N-X said:
Yes. The hotspot option comes with it from what I have tried.
Click to expand...
Click to collapse
Thank You for your time
I cant manage to root this rom with proton kernel even on stock cant root pixel4a 5g any guide or help apriciated....