Database Users

installing gapps on custom ROMS

When I first installed CM 11 M1 from stock kitkat, I didn't have the playstore, so I had to download the gapps package.
Ever since CM 11 M1, I've tried different custom roms, but everytime I flashed them from the custom recovery, they all came with the playstore.
Should I be installing the gapps from the package?? Or can I just install the apps from the playstore??

Either way works. From the play store you can pick and choose what you install and can be uninstalled without jumping through hoops because they install as user apps. When you flash gapps, they typically go in as system apps and are a bit more troublesome to get rid of if you don't want everything in the package.
Sent from my Nexus 4 using Tapatalk

Addition to what said above, just open the gapps package ade delete which ever apks you don't need. This way you can get rid of the apps you don't want to install as system app. To me, modular PA gapps or banks core gapps is enough. You don't need to flash full package gapps.

ankuzero said:
When I first installed CM 11 M1 from stock kitkat, I didn't have the playstore, so I had to download the gapps package.
Ever since CM 11 M1, I've tried different custom roms, but everytime I flashed them from the custom recovery, they all came with the playstore.
Should I be installing the gapps from the package?? Or can I just install the apps from the playstore??
Click to expand...
Click to collapse
This is because gapps has updater script and as long as you won't manually format system your previously installed gapps will remain in a new rom. (including play store)
Installing apps from gapps package via recovery will install the apps to system partition.
Installing apps from play store will install them to user data partition.
In order to save space in user data I recommend installing the gapps you need to system partition via recovery.

Thanks for info guys :good::laugh:

[GUIDE] Install Lineage OS 14.1 on Redmi Note 3 (No in call audio issue fixed)

Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?

xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?

@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.

I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107

r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse

How to update AOSP extended ROM

Hey everyone I recently installed aosp extended and saw in their website that a newer version was available when I checked a youtube video it said that I needed to flash gapps along with the update can someone help me on how to update the ROM is it same like pixelexperience where we just flash the file and clear cache alone?

#updateaex
1. Boot into TWRP
2. Flash AEX zip
3. Flash TWRP installer
4. Reboot to TWRP
5. Flash gapps
6. Flash magisk (optional)
7. Wipe dalvik cache
8. Reboot to system and enjoy
from telegram channel
But, what's your actual version of AEX ?

Sorry to but in...
I have a Mi9 with AOSP...
(please go easy..I'm a tad clueless)
If there is an update do I follow the instructions 21vm gave? And will I lose my apps and settings?

[GUIDE] [J400X] How To Install GSI in Samsung Galaxy J4

• Introduction
Samsung Galaxy J4 is a phone based on Exynos 7570 with 720x1280 resolution, ARM Mali T720 GPU, Cortex A53 Quad-core CPU. This phone released in 2018 with Android 8 shipped out-of-box, and available OS update until Android 10.
But, since it already 2 years (in 2020) from launched, this phone only have developer that can be counted on one hand. There is no custom rom for this device, and custom kernel only 1 or 2 or 3 (I'm building this kernel right now, but I'll release it when I have enough post count )
The good news is, this device is Treble supported! So we can install most of available GSI, even without any vendor or kernel required.
• Stock ROM vs GSI
What's the different? In my opinion, very much! As we know, GSI is based on AOSP, which is pure android, and almost no bloatware. And, for other GSI, like Havoc or Lineage or any GSI like that, have cool theme and animation. Why not giving a try?
• Warning
Although this is cool, but, remember this is GSI, bugs are widely open. Bugs I found are in below.
Second thing, your warranty is void! This is sure, you unlock bootloader, Install TWRP, even install GSI, that surely will trip knox and voiding warranty.
And, last one, backup ALL of your data. This process will wipe your data partition.
• Bugs
As far as I use Havoc-OS GSI 3.7 Android 10, I feel these bugs:
1. Camera Streching, use Open Camera
2. Video recording, use Open Camera too
3. Camera in Whats'App
4. I forgot
If you feel other bugs, please write it in below.
• Steps
Since currently this phone have Android 9 Android 10 update, the steps will be different. Dont worry, I'll write all the steps
From Android 9 stock :
1. Download TWRP 3.2 and 3.4
2. Copy to your PC
3. You must have Odin
4. Download GSI image A64 A-ONLY / ARM32_BINDER64 and put it in your Micro SD card or USB (for OTG)
5. Download Gapps (optional if you want google apps installed) nano / pico ARM-10.0
6. Download Magisk if you want root
7. Dont forget to copy downloaded zip file to Micro SD Card or USB (For OTG)
8. Flash TWRP 3.2 via odin, then reboot recovery
9. Wipe - format data - yes
10. Wipe - advanced wipe - choose system, data, internal, cache / dalvik cache
11. Install - install image - choose gsi image you downloaded - choose system image
12. reboot recovery
13. mount - system
14. wipe - advanced wipe - choose system - repair filesystem - resize
15. install - install gapps zip
16. reboot download
17. flash TWRP 3.4
18. reboot recovery
19. flash magisk (optional)
20. flash zygotefix
21. reboot and complete setup
From Android 10 stock :
1. Download TWRP 3.2 or OrangeFox
2. Download any a64 A/B (arm32_binder 64) xz decompress it* and put it in your Micro SD card or USB (for OTG) or internal memory
3. extract it with any extractor app
5. Download Gapps (optional if you want google apps installed, some have it included)
6. Reboot recovery
7. wipe. advance wipe. system, data, dalvick cache.
8. Flash the extracted GSI
9. Flash Gapps if they are not included
10. Flash magisk (optional)
11. Reboot system
And Done!
If you have anything you ask, feel free to join our Telegram group : t.me/SamsungGalaxyJ4
Or PM me in Telegram : t.me/hendramanudinata
Cheers!

calls have no speaker or mic

Everytime no matter what I do after flashing a ROM it eventually stops my calling ability. It calls out but no one. Can hear me and I can't hear them.

What OOS are you using? How are you exactly installing roms, step by step..? What rom installing?? Must have more details to help...
After i see that info ill know more. Possible its a hardware issue but i lean more towards software.. Let me know those things and i can help more.
How I install on OnePlus 6t global (or converted)
Boot twrp v3.5.0
Flash OOS 10.3.7 from repo or updater app
Flash rom (with gapps)
Flash twrp installer zip
Flash finalize
Format data (wipes it ALL)
Reboot recovery
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Without gapps rom install:
Boot twrp
Flash OOS 10.3.7
Flash rom (without gapps included)
Flash twrp installer
Flash finalize
Format data (wipes everything)
Reboot recovery
Flash gapps package
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Use NanoDroid Micro G and Fdroid instead of Gapps on a rom that has sig spoofing and NO Gapps included:
1st part of micro G install:
Boot twrp
Flash OOS 10.3.7
Flash rom
Flash twrp installer zip
Flash finalize
Format data
Reboot recovery
Flash magisk 21.4
Reboot system
Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
2nd part of Micro G rom install:
Boot twrp
Install micro g (stable) zip from Nanolx xda thread
Install Fdroid from Nanolx xda
Reboot system
Can also use twrp mauronofrio's 3.4.0-9-11. Those are newest twrp. I've flashed everything made for 6t and never an issue like this. Link to micro g and fdroid installer and more in my signiture.
(Edit)

Hey thanks for the responce, so here we go....
How I flash my roms
Flash OOS 10.3.7/twrp
Reboot recovery
Flash other side of a/b with OOS/twrp
Reboot recovery
Flash rom/twrp installer
Reboot recovery
Flash additional as in my migrate/magisk
Format data
Boot
The Roms I've tried are resurrection remix latest build & msm extended & one other I can't remember which tho. & with stock kernel. I've tried flashing other kernels it doesn't do anything or I'm trying the wrong ones.
Im not new to flashing been doing this for a while now, there's always bugs but there's also ways to fix the bugs. Something interesting is just one time calling it worked fine then the next call... back to no audio feedback. There are 2 other Roms that did the same thing. It happens completely random, like I'll be done modding my phone to my likings go a month or a week & all the sudden no audio. I doubt it's hardware cuz if I format data calls work again but yay all my customizing is gone. I've tried all the suggestions from other forums asking similar question like editing build.prop & a few other things I can't remember nothing's worked. I love this phone to death but it's not easy to keep it stable unless I wanted to go with linegen ROM but ever since they left cyanogen their customizations are lame. Anyways I hope this is enough details I imagine not just let me know thanks I appreciate your help.

I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio

jessejamesd2i said:
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
Click to expand...
Click to collapse
The only time i experienced similar on my 6t is when i used a sound mod, the zen 5 sound mod from asus phone ported.. It caused me to have this no sound issue but when i disable it via magisk it was fine and i had sound again.
Have you tried going back to OOS 10.3.7 only and see if sound is an issue?

If this is present on OOS i would think its a hardware issue.