Develop Bugs

Problems after installing CM12.1 nightlies

Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)

Copy important files to computer. Factory reset. Set it up as new device.

ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.

decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova

Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?

jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.

decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova

Flashing ROM reboot issues, advice massively appreciated.

I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran

Have you tried going back to the latest official Oxygen OS (Stable or OB)?

jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'

Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.

my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM

[GUIDE] How to flash Android 9 Pie (PixelExperience, Havoc OS etc.)

Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):

Don't need to flash p lag fix, volte fix and other stuff?

Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)

bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?

moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.

Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help

moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?

Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.

GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/

sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie

Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.

HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.

Is hotspot working in PIE GSI?

dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!

Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom

it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem

And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?

moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok

expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.

soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on

Problems with flashing a new Rom

Tried to flash the latest Resurrection Remix ROM on my OP3 (which is the RR-P-v7.0.1-20190309-oneplus3-Official.zip found here )ontop of the previous version RR-P-v7.0.0-20190302-oneplus3-Official.zip .
At first a assert failed and I couldnt flash it but after I flashed the Stable 5.0.8 Modem+FW from here the flashing succeeded.
Rebooting and starting the device works at first until the bootanims finishes, it stay for some time on the last from (where the circle is closed around the logo) but then automaticly shuts down.
I redownloaded all used files multiple times and reflashed them just as often. What could be my problem?
To use my device atm I simply reflashed the previous version RR-P-v7.0.0-20190302-oneplus3-Official.zip and it works with the newer Modem flawlessly.

Anyone
Same problem, any solution?

Have you tried a clean flash with full wipe instead of a dirty one ?
If i were you, i would :
- Backup my data
- Flash TWRP (look in the ROM thread for the correct one)
- Flash modem (look in the ROM thread for the correct one)
- Full wipe (even /data)
- Flash ROM
- Flash Gapps if needed
See if after a clean install of the ROM you still have issue. If you still have issue, maybe try another ROM. LOS, OOS Leaked, Havoc or Nitrogen, idk.

Lineage 16.0 Official

Lineage 16.0 now available from here
https://download.lineageos.org/crackling:laugh:

for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
upd: yes, my bad, for me 15.1 also doesn't work, so it is on my side.
upd: I did this to fix it: https://forum.xda-developers.com/showpost.php?p=66158015&postcount=2) as I understand I downgraded fastboot to be cynogen, from los

ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
You may have to sideload it if coming from 15.1

ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
Are you using the nougat bootloader? Try downgrading to any of the COS13 firmwares then flashing.
FWIW though this is a bug with LOS since beroid's crDroid works fine with the newer bootloader. Same with his TWRP (this bug does exist in OrangeFox Recovery which suggests it's a software thing).

Works, but I'd stay to 15.1
The ROM works fine for me. Everything, the camera, talks work fine. But I don't know if it's just me but my phone runs pretty slow on the new ROM, without any of my apps installed.

I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?

romanboy said:
I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?
Click to expand...
Click to collapse
Are you installing the GApps in TWRP immediately after the LOS Installation, prior to booting into LOS?
Have you tried the nano instead the pico?

I followed the instructions at https://wiki.lineageos.org/devices/crackling/install using twrp 3.2.3 as instructed. I used MindThe Gapps 9.0 as I saw somewhere (as romanboy above found) that standard Gapps gives error 70 (not enough space) even for nano version. Swift boots into LOS 16 after some time but it keeps displaying popup about Pixel Setup keeps stopping: I can only show App Info (with Force Stop option) or Close app: either case results in popup appearing again. I've asked the author of the above wiki (on reddit #LineageOS) but no reply.

I started again by installing cm13.2 then used twrp 3.2.3 to install LineageOS16.0 followed by OpenGapps 9 pico. All now Ok.. So MindTheGapps 9.0 is no good.

Camera not working, flashed with latest TWRP.

Official Rom
LaneyUK said:
Camera not working, flashed with latest TWRP.
Click to expand...
Click to collapse
There is now an official lineage Rom
https://download.lineageos.org/crackling