Sorry bad english
Easiest way is to do the following
1. Download and extract platform tools from Google's platform tools
2. Go to the folder where platform tools (adb.exe) is extracted, hold shift and select Open PowerShell here or Open Command Prompt here whichever available
3. Flash Lineage 16.0 without OpenGapps and let it boot
4. Enable Developer Settings (by pressing build number 5 times) and enable ADB
5. Connect your phone to PC and type adb devices. Make sure the device is recognized.
6. Reboot to twrp or whichever recovery you use, flash OpenGapps and reboot the phone
7. Once it gets stuck on bootloop in the command window you opened in step 2, type adb logcat -d > logcat.txt
8. Upload the file here
---------- Post added at 00:51 ---------- Previous post was at 00:43 ----------
Apparently from 20200117 onward there is an issue. One log would mean a lot for me and the OpenGapps team since I have no access to my device currently to check
Yeah, opengapps bizarrely develops everything on a master branch. When they merged their Q development branch into master they added some changes to default-permissions that are absolutely unallowable for <Q.
I nearly threw my phone across the room when it ran into it on an personal-use build that has gapps built-in several days ago.
Between stuff like that, then not caring about verifying priv-app permissions, and constantly breaking their trees, it's really frustrating.
First of all, thank you for your feedback. Although harsh, it is mostly valid.
1) I'm going to pull all of the builds after the Jan 17th one, except for the Q builds which are fine now.
2) @haggertk thank you for noticing this, I'll make a test build without these permissions to check, and if it works, will incorporate a fix which will have these permissions added only for Q.
3) @curiousrom regarding your points (any opinion on this is purely mine, I can't speak for the whole team but this is how I see things):
1. Yes, users are wasting their time with broken gapps. So does everyone with broken ROMs, kernels, etc. So do I when Google decides to break something just because. This is life, **** happens.
2. I think "reputation" is a strong word. You're talking about an opensource project which is supported by a very small group of people (mostly myself, @MNBooZe, NicholasBuse with occasional help from @osm0sis and others) right now who are doing this out of pure enthusiasm without any guarantees, like most of the projects here on XDA.
I, for one, am not doing this for reputation or fame, this is a poor motivation in a world of opensource. I do that purely out of self-motivation, to keep the project going, and of the desire to have a working device with AOSP-based ROM with Google stuff.
Also I don't remember anyone making commitments about the 100% working builds all the time, daily builds have a tendency of being broken from time to time, so there's that.
3. Yes, and most probably will happen again for reasons described earlier.
4. I've already spoken to you, and wrote about it here - we are going to do that, but in order to launch a testing group and a test build workflow, we have to modify a lot of stuff:
- change the SF structure
- modify buildserver to push "test" builds instead of "stable"
- create and admin the testing group
- modify API to have some kind of "promotion" of the latest working "test" build to the "stable"
- change the website to support that separation
Assuming I'm pretty much the only one doing this stuff right now (except for the buildserver which is managed by @MNBooZe) this will take a while. And managing a separate testing community will be a very time-consuming process which someone will have to burden. I'm not sure that I'll be able to handle it per se.
5. Making weekly builds is feasible, but honestly, what does it matter? If it becomes broken, you're sill left with a week-old build, much like now. Separation of the builds to the test-stable should resolve that.
I am posting this because I sent you an XDA PM about it but got no reply. Do you read them?
I see that you deleted broken builds 2020-01-22 & 23 but in the 2020-01-24 folder they are still there.
Can't you keep the Android 10 builds & delete the others ASAP please?
For example in https://sourceforge.net/projects/ope.../arm/20200124/
Thanks for your time.
@Nezorflame, thanks for all the years of your great and solid work. Your project is really one of the essential of hole modding scene. Of course there where some problems the last weeks but that's more because of the ****ing changes of google and you have to look how came out of this ***t. Thanks to you and maartenfonville.
|gapps, open gapps, open source, opengapps|
|Thread Tools||Search this Thread|