yashsingh1/xdaforums huggingface dataset:
[Android Software Development] TheHitMan:
The ROM you are using shipped with pre-installed GApps ?
[Android Software Development] BLacklion17:
No, the vanilla version is not a Gapps version.

''Cherish-OS-v2.8-20210807-1050-raphael-OFFICIAL-Vanilla-OSS''
[Android Software Development] TheHitMan:
But the error points out that you're trying to install BiTGApps on a ROM that already has GApps pre-installed but that ROM is unsupported.
[Android Software Development] TheHitMan:
I did installed the latest version in my device Redmi Note 8 (ginkgo) running on Syberia OS A11. No pre-installed GApps.
[Android Software Development] BLacklion17:
Now I looked again, the rom vanilla version I'm using. I'm installing vanilla version because I don't like gapps versions.

To test, I downloaded and tried the Nikgapps core version and I don't encounter any errors. I downloaded and tried the R37 version again, it still gives the same error.

Cherish-OS-v2.8-20210807-1050-raphael-OFFICIAL-Vanilla-OSS When I installed the R35 version on this version, it did not give any errors.

I wanted to do a clean rom install, at that time there was a new BitGapps version R36 on the site, I wanted to install it, but it gave an error. Then the R37 version came and it gave the same error.
[Android Software Development] BLacklion17:
Vendor A10, is it possible that it's not because of that?

By the way, I tried Bitgapps R36, R37 in A11 in A10. Both failed.
[Android Software Development] TheHitMan:
The function that detect presence of pre-installed GApps using playstore is broken. Thats why you able to install. Even unsupported ROMs that shipped with GApps also able to by-pass.
[Android Software Development] TheHitMan:
Will figure it out and add a proper fix for the same.

Providing installation logs is still a better way to get things done.
[Android Software Development] TheHitMan:
@BLacklion17 If you can reproduce the same error using R37 release and providing installation log after will be helpful. Log file saved in internal storage (bitgapps_debug_xxxx).
[Android Software Development] BLacklion17:
I installed ArrowOs rom to try.

1.FRAMEWORK_raphael_miui_RAPHAELGlobal_V12.5.2.0.RFKMIXM_edbf5f63e8_11.0

2.Arrow-v11.0-raphael-OFFICIAL-20210816-VANILLA-OSS-A11FW

3.BiTGApps-arm64-11.0.0-R37_signed

-BitGapps installed successfully. But

1.VENDOR Global-V12.0.6.0.QFKMIXM-10.0-GLOBAL

2.Cherish-OS-v2.8-20210807-1050-raphael-OFFICIAL-Vanilla-OSS

3.BiTGApps-arm64-11.0.0-R37_signed

It gives an error when I upload.

I guess Android 10 Vendor is not compatible with version R37.

But with the A11 framework, the rom does not cause any problems.
[Android Software Development] TheHitMan:
But GApps has nothing to do with device specific stuffs.
[Android Software Development] TheHitMan:
After 3rd point, should i consider that installation is now fine with Cherish OS ?
[Android Software Development] TheHitMan:
@BLacklion17 Do you have time to test new fixes ?
[Android Software Development] BLacklion17:
-Unfortunately it gives the same error on CherishOs rom.

-As far as I can see, Android10 Vendor (816 mb) has a problem Gapps. But Android11 framework (101 mb) does not cause problems.

-Yes of course. Now I got the error by trying to install CherishOs rom again. I got the error log in .zip format.

Which one would you like me to share?

-Where can I find BitGapps R35 Android11 version?
[Android Software Development] TheHitMan:
Just send whatever debug log you have in compressed state.

EDIT: Do you have telegram account ?
[Android Software Development] BLacklion17:
Yes, I have a Telegram account, but unfortunately I cannot open my account because I am trying to install a ROM.

Would you like me to send it via e-mail address? If you specify your e-mail address in a private message, I can send you the diary that way.
[Android Software Development] TheHitMan:
Check PM

EDIT: I can send you test build now. Let me know Android Version & Arch.
[Android Software Development] BLacklion17:
I sent an email, what is Arch? My phone is Xiaomi Mi 9T Pro and it's ARM64 as far as I know.
[Android Software Development] TheHitMan:
Android Version ?
[Android Software Development] BLacklion17:
A11
[Android Software Development] TheHitMan:
Building test release now.
[Android Software Development] BLacklion17:
What should I do? I don't understand, I'm sorry. :rolleyes: :)
[Android Software Development] TheHitMan:
Wait for new build and test it when it is there.
[Android Software Development] BLacklion17:
By the way, thank you very much for your interest. You are awesome! :love:
[Android Software Development] TheHitMan:
Here you go

https://bitgapps.com/downloads/BiTGApps-arm64-11.0.0-R38_signed.zip

EDIT: Sent the microG build before, link updated with BiTGApps now.
[Android Software Development] BLacklion17:
Thank you for your attention, but it still gave an error. I sent the log to your email address. :(
[Android Software Development] TheHitMan:
Really pathetic your so called Vanilla ROM do contain GApps stack already. It might not be full stack but minimal implementation. I have found pre-installed GApps in product partition (if you have else it is just a folder).

Function is absolutely right, it detects the presence of playstore even in your so called VANILLA build. I directly checked the latest Cherish OS.

The whole time its your ROM fault. It has nothing to do with your device firmware, rather the ROM you're installing. You can check ScreenShot from attachment.
[Android Software Development] BLacklion17:
Thank you for your interest. :love: I can't say anything because I have no technical knowledge.

BitGapps R35 did not fail in the same ROM. Where can I find this version? I would like to try the R35 version again.

Thanks for your hard work. (Sorry for my bad English, I'm using Google Translate for help. :))
[Android Software Development] TheHitMan:
Your ROM has gapps and i don't think so this is hard to understand.

I don't kept older release and don't support them either after the new is up.

That broken function fixed in R37 and expected to work as is. So its not the BITGApps broken but your ROM.

No need to justify that it works with R35. It also don't work with R35, if i fixed that broken function earlier.

EDIT: Why you need to flash GApps in a ROM that already has ? The case is not same as Pixel Experience and Paranoid Android.
[Android Software Development] BLacklion17:
-Because Gapps is not installed in the vanilla version. More precisely, when I install the rom, the Google Play Store does not come.

-I don't want to install the Gapps version of the ROM either because there are many apps that I don't use.

- BitGapps R37, which I installed and tried the ArrowOS rom (A11 FW), AncientOs(A11 FW) does not give an error and works properly.

- When I install NikGapps latest version on CherishOs rom, it does not give an error.

-Now I installed the previous CherishOS v2.7.5 vanilla rom. I installed BitGapps R37 version, it gave an error again.

-As you said, there is obviously a problem with the rom. Thank you for all your hard work. (y)
[Android Software Development] TheHitMan:
- The screenshot above of your ROM after it is unpacked. You can see GApps packages there. The default stuff comes in your ROM. You want screenshot from Cherish v2.7.5, Let me send it then.

- Nikgapps ≠ BiTGApps and they don't detect present of gapps either, not a better way to get things done.

- Your vanilla build has GApps else it won't complain about presence of Google Play Store.
[Android Software Development] BLacklion17:
Thank you, I will have to change the rom. Hello AncientOs ROM + BitGapps R37 :love: :)
[Android Software Development] bdwilk:
I don't have digital wellbeing after flashing v0.6. I'm not complaining, I don't want it either. Just saying.
[Android Software Development] :
tyvm. it seems dev released 0.6 at the telegram page :good: it's all good now.
[Android Software Development] TheHitMan:
Server stuffs are fixed now. I will try to release today.
[Android Software Development] :
Installing these will result in boot loop to recovery

1 - lineage-17.0-20191203-UNOFFICIAL-laurel_sprout.zip

2 - OrangeFox-R10.0_2.1-Stable-laurel_sprout.zip (reboot automatically)

3 - Magisk-v20.1.zip

4 - BiTGApps-arm64-10.0.0-v0.6_signed.zip

5 - patchnofde10.zip

Trying with quickfix installer.sh some page ago doesnt help either

https://drive.google.com/open?id=1_p2VFR5XTA28A9C8xYdq5m7Cx7wvWhu6
[Android Software Development] TheHitMan:
Can you try with installation method posted in OP.
[Android Software Development] :
Installation Instructions

• Install ROM.

• Reboot to recovery.

• Install BiTGApps zip.

• Reboot.

• Note : Requires Clean Flash, if other GApps are installed.

1 - lineage-17.0-20191203-UNOFFICIAL-laurel_sprout.zip

2 - BiTGApps-arm64-10.0.0-v0.6_signed.zip

in these order? no need to flash recovery in between?

i'm new at these treble thing. back then it was easy. flash rom, flash gapps, flash magisk. done. :D
[Android Software Development] TheHitMan:
Do you have that device that require flashing recovery all the time after flashing rom ?
[Android Software Development] :
i'm just following this guide.

https://xdaforums.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603

idk. apparently we will lose recovery or something. that guide tell me to flash recovery inbetween rom and gapps.

that's why this treble thing is confusing me. i had nexus 5, flashing rom was much easier.
[Android Software Development] TheHitMan:
Try flashing like this.

Flash rom, recovery, reboot to recovery, flash gapps, reboot.
[Android Software Development] :
Progress update on Mi A3 :

Finally it boots successfully.

1 - lineage-17.0-20191203-UNOFFICIAL-laurel_sprout.zip

2 - OrangeFox-R10.0_2.1-Stable-laurel_sprout.zip (reboot automatically)

3 - BiTGApps-arm64-10.0.0-v0.6_signed.zip (using quickfix installer.sh)

4 - patchnofde10.zip

5 - Boot to ROM

6 - Reboot to Recovery and install Magisk

Yesterday I installed 0.5 in one go and it was OK.

Apparently something choke if we install Magisk and BiTGApps 0.6 in one go. Both are clean installs.

I just want to get rid of Digital Wellbeing in my ROM. Disabling it wont do, still there in the Settings.

Thank you for your help.
[Android Software Development] TheHitMan:
You rom has Wellbeing by default. BiTGApps does not have Wellbeing. Plus can you try installing BiTGApps build that is attached in OP.
[Android Software Development] :
I'm pretty sure 0.5 has Digital Wellbeing because I used it yesterday. That's why earlier I asked If it's ok to delete digital wellbeing package from BiTGApps and flash it.

Then bdwilk told me that 0.6 doesnt have it. I'm happy with 0.6

https://imgur.com/2EZ3bUZ
[Android Software Development] bdwilk:
Your device has a/b partitioning. That's why there are the extra steps to flashing. Not really a treble thing as some a-only partitioned devices are treble compatible as well.
[Android Software Development] TheHitMan:
Btw can you do what i said a few posts before.
[Android Software Development] :
this one?

with 0.5 or 0.6?

sure i can, but i know it wont boot because i need patchnofde10.zip to bypass device encryption.
[Android Software Development] TheHitMan:
No worries follow you last procedure. I am just saying use the zip attached in OP. I am not talking about modified installer.sh again.
[Android Software Development] :
Flash order

1 - lineage-17.0-20191203-UNOFFICIAL-laurel_sprout.zip

2 - OrangeFox-R10.0_2.1-Stable-laurel_sprout.zip (reboot automatically)

3 - BiTGApps-arm64-10.0.0-v0.5_signed

4 - patchnofde10.zip

5 - Boot to ROM

ROM boot successfully, but Digital Wellbeing comes back again. 0.5 has it 0.6 doesnt :)
[Android Software Development] TheHitMan:
Are you out of mind ? I asked for latest Q build. But not with modified installer.sh, the original file i post on telegram.

EDIT: I will update the installer to remove Wellbeing completely.
[Android Software Development] :
LMAO. soooo that's what you meant. that's why i felt weird. Why this guy wants me to flash an old build? LOLOLOLOLOLOL. I'll try with Telegram build. I'll update later, need some food.

tldr; oops my bad.
[Android Software Development] TheHitMan:
No problem. I will wait.
[Android Software Development] TheHitMan:
@BLacklion17 Check below screenshot. You even have GApps shipped with 2.7.5 build of CherishOS.

First Screenshot: You can see downloading of Cherish OS

Second Screenshot: GApps files in ROM

Third Screenshot: Properties from 2.7.5 ROM for confirmation.
[Android Software Development] BLacklion17:
In this case the error is not me doing something wrong or related to BitGapps. There is a problem with the rom itself.
[Android Software Development] TheHitMan:
Thats what i want to convey from yesterday.

EDIT: In second screenshot, Phonesky means GooglePlayStore and PrebuiltGmsCore means GooglePlayServices.
[Android Software Development] BLacklion17:
Thank you for all your hard work. you are amazing :) (y) :love:
[Android Software Development] TheHitMan:
Its a gimmick. There are no GApps in vanilla variant of Cherish OS. It is just the GApps package created somehow but there is no APK files inside.

Obviously this is a glitch comes from ROM. But i will also add fixes from my side for the same. I have already reported the same to Cherish OS maintainer of raphael.
[Android Software Development] BLacklion17:
Thank you for your great attention. Exceptional to informing the authorized places. Long live BitGapps and TheHitMan. :love:
[Android Software Development] aliveday:
how to uninstall it

I need to reinstall some app

When I try to uninstall it with twrp

always Error "! Invalid config found"

https://github.com/BiTGApps/BiTGApps/wiki/Basic-Installation

The method provided on this page does not work at all
[Android Software Development] TheHitMan:
GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project

The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.

github.com
[Android Software Development] ele3131:
So if I understand, to uninstall the version installed the corresponding installation and config file are required, however after a new version release, old versions are deleted, couldn't the forum's page keep them?

About the config, is it required even with Systemless installation? Or BitGapps can be uninstalled from Magisk?

Still about Systemless, not possible to make BitGapps be updated through Magisk?
[Android Software Development] TheHitMan:
Yes.

EDIT: I never tried uninstalling using latest release and latest config. Will test that too and if everything goes fine. You will see an update in documentation too, regarding this. Will also notify here.

Will try to do that.

Yes, explained in this doc

GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project

The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.

github.com

I didn't get it. But if you concern is upgrading from last BiTGApps release to latest then you can do it. But upgrading not possible through magisk app itself.
[Android Software Development] Zytrel:
Greetings,

I'm using Lineage 18.1 for klte. Before I used "BiTGApps-arm-11.0.0-R29_signed" which was fine. After upgrading to R34, I lost SELinux. Unfortunately the current version R37 doesn't mitigate the problem. I tested this with clean installs (Wipe system/data/everything). R29 results in SELinux enforcing while both R34 and R37 will set SELinux to permissive.

Unfortunately for some reason I can't roll back to an earlier TWRP backup as this will result in being stuck at the boot screen forever.

Any help on this matter would be highly appreciated.

Many regards,

Zy.
[Android Software Development] TheHitMan:
You can spend some time reading documentation but still https://github.com/BiTGApps/BiTGApps/wiki/SELinux-State

Keep in mind, i can't spoonfed every single person. So better you and others put some efforts in reading first post before using anything.
[Android Software Development] aliveday:
there is no way to get R29 bitgapps-config.prop, I tried to upgrade R37 but it reported error, I had to directly use R37 bitgapps-config.propto uninstall R29, It destroyed my system.

it remved my keybaod, Input method, Android System WebView, gesture navigation and

every Google-related apps not installed through gapps.

Fortunately I have a backup, otherwise I will be crazy.

i'm reading documentation now and i think Systemless Installation will be the only choice that Versions after R29 have too many restrictions that I cannot bear the consequences.

there are many situations that can't be avoided by read documentation.
[Android Software Development] TheHitMan:
You're pretty much wrong in everything here. The current revision is R37 and you are still using R29. Everybody is supposed to do clean install when upgarding from R29. Because change in installation type. It is literally explained in this doc https://github.com/BiTGApps/BiTGApps/wiki/Installation-Status. Apart from this doc it is also mentioned in R30 revision changelog https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/page-37#post-85437119.

EDIT: You cannot uninstall R29 using anything after R30 revision. As said earlier change in installation type.
[Android Software Development] TheHitMan:
Thats how it works, it removes Non-GApps components + GApps components and then restore back Non-GApps components in ROM. The backup saved in data partition and used by uninstall functions to restore. It has been tested many times.
[Android Software Development] Zytrel:
I tried digging through the docs, but there is more praise about features than actual information in there.

As expected the mentioned zip in the link only did send me back to the endless bootscreen again.

Regards,

Zy.
[Android Software Development] TheHitMan:
Ok!
[Android Software Development] Zytrel:
The thing is, as you told another user "The current revision is R37 and you are still using R29. Everybody is supposed to do clean install when upgarding from R29. Because change in installation type.", why not issue a warning on the download page? Guess BitGapps is not for me as I'm not willing to follow this thread on a daily basis just not to miss some important notice.

EDIT: Fact is, anything beyond 29 sends my device into permissive state on a clean install without configuration file. That should just not happen.

Regards,

Zy.
[Android Software Development] TheHitMan:
Ok

Ok!

I will also mention in "Installation Status" doc that which revision require clean install. It will cover both old & new.

Ok!

But i also didn't see any logcat, recovery log or boot image of your device, not even a screenshot, to figure out the bootloop issues after installing selinux package.
[Android Software Development] aliveday:
Thank you brother, I am about to scold him, your reply calmed me down and let him edited the words that mocked me.

He doesn't understand that if the user knows everything, no one needs him.

He never thought that I use R37 configuration file to uninstall R29 Because he deleted the download link of R29,

He just hopes that every user will come to carefully read every word written in his post every day

I'm left, the R37 causes my tablet bootloop, his attitude makes me not interested in using it .
[Android Software Development] TheHitMan:
I removed those words, because it won't make things better rather complicate them. Also not a better way to convey something.

Thats why i spend countless hours on writing documentation, still grabbing a little information is so hard for you.

I know that you're using latest config with R29.

I don't have endless quota on my server. It is nowhere said that you have to read everyday. You know that already, you're on a little older release. Keeping this in mind, you must have checked the changelog of newer builds.

Well, its upto you. If you want it, you have go through with whatever required. And please no need to give baseless justification. Bootloop happens because of your actions. You are not the only person who ignore documentation, there are many like you and i have to take additional steps in serving same information again and again.

On a side note, do you even think, this is worth the time, everything is there in doc, if you have done some research already you don't even have to land on this thread.
[Android Software Development] Zytrel:
Logcat.
[Android Software Development] TheHitMan:
Leave it.
[Android Software Development] Zytrel:
Just in case you're interested, despite telling me to leave it, the utterly simple solution was to format data instead of just wiping, restore data, then reinstall system with BitGapps R29.

Regards,

Zy.
[Android Software Development] TheHitMan:
Ok
[Android Software Development] TheHitMan:
I have tested the same selinux enforcing package with one of klte user running pure khalvat build and he hasn't encountered any sort of bootloop. Not only he tested enforcing package but permissive package too in a row and still boots fine. So i can conclude that you made a mess here. It is obvious that you can boot fine with BiTGApps but not with enforcing package. Although enforcing package uses the same boot modification functions from BiTGApps.

You can also check telegram post https://t.me/bitgapps_downloads_official/119 of the same.
[Android Software Development] Zytrel:
Ok.

EDIT: Sooo, I was just able to reproduce this on my Galaxy Tab Pro (picassolte) with a clean Lineage 18.1 install and R34, which also ended up with SELinux in permissive mode (At first I thought it was the ROM).

I was able to downgrade to R29 with the following procedure: Backup everything (TWRP/internal SD). Format data, wipe system/dalvik/cache. Reboot recovery. Restore data partition from TWRP, internal SD from backup. Install latest lineage system/BitGapps R29. Flash the BiTGApps-selinux-enforcing script. Reboot.

So clearly there is an issue with BitGapps R3x and Lineage 18.1, at least on (older) Samsung devices.

Maybe you should consider toning down your arrogance a bit, and stop assuming you're the smartest person in the room while everyone else is just an idiot.

I noticed the R3x versions started patching the kernel image, and can only assume that might be the source of the problem. Also, why, for the love of god, do you have to mess with the kernel in the first place? It's a damn Gapps package, not Magisk.

Many regards nonetheless,

Zy.
[Android Software Development] TheHitMan:
Your inability to read makes you think that it comes from ROM.

Pitty on you!

This is not an issue. It is made on purpose change.

Below post will let you know, who has arrogance and who is an idiot here.

I did explained in this document https://github.com/BiTGApps/BiTGApps/wiki/SELinux-State from where you downloaded that selinux package. I am actually amazed with the fact that you aren't even able to read the very first three lines from same post from where you are downloading. It is literally written there when selinux change to permissive.

Stating from SELinux State Doc:

You're justifying your fact here that you don't want to read but wants someone to serve you.

Still you don't know, why we are changing selinux state. Even the first three lines from SELinux State doc are self explanatory.

So modifying kernel is a privilege of magisk only ?

In the end, instead of bashing on me. You can spend sometime reading. If you can't do that then don't spam with which is already explained and not an issue in first place. None of your posts till now helped me in making this project better anyhow neither helped in cutting down bugs. The fact is, upto this post, you're still making assumptions on what causing it. Any sane person will grab the right information and ends the topic there.