http://forum.xda-developers.com/showpost.php?p=62409122&postcount=302
I have this same issue trying to run Wanam's Xposed on my GS6 regular on Ramified rom. Has anyone gotten this to work? I know @Tardeaux has by dirty flashing, rebooting, and reinstalling. None of this has worked for me.
I'm on 3.1 and greatly debloated by myself and I have not had one issues.. running like 5 modules too!
I am trying to figure out why it works for some and not others. I am running ramified (edge rom with regular unikernel) on S6 regular. @Saafir, you are on ramified OGA-V1 debloated. Are you edge or regular? @JoeFCaputo113 your signature says twisted rom and S6 regular. Are you on ramified or twisted? Xposed works (no radio issues) for me on twisted, but has the radio issues on ramified. Anyone else S6 edge or straight have success or not on ramified OGA-V1 debloated?
todivefor said:
I am trying to figure out why it works for some and not others. I am running ramified (edge rom with regular unikernel) on S6 regular. @Saafir, you are on ramified OGA-V1 debloated. Are you edge or regular? @JoeFCaputo113 your signature says twisted rom and S6 regular. Are you on ramified or twisted? Xposed works (no radio issues) for me on twisted, but has the radio issues on ramified. Anyone else S6 edge or straight have success or not on ramified OGA-V1 debloated?
Click to expand...
Click to collapse
Sorry for the misinformation I haven't updated my signature in like a month lol. But yes I am on Ramified v3.1 and I debloated the ROM myself. Xposed work flawlessly for me.
I'm running same as Joe - bloated ramified with a bunch of stuff I froze or removed myself, and the v6 unikernel port on the s6 regular. No issues with xposed or my radio, and it shows G920PVPU2BOFE under baseband version.
Yes this happened to me but i wiped the whole phone except internal storage cache dalvik data system and flashed rom again and contacts.zip and kernel after it booted then installed xposed and it was fine
I did have the same problem just after Flashing Rammified and Xposed.
Wipe everything but internal storage worked for me.
Try not flashing Unikernel, I think Rammified already includes it.
When the wierdest things like that happen even though it seems nothing is incompatible I wipe system, data, cache, dalvik, but not internal storage, reflash my desired setup and everything is fine.
It has happened on alot of my Androids.
These things might have caused my the problem you're having because mine ended up the same way:
I had Alliance framework installed and maybe not working. Also Wifi Settings could not stop crashing when I had wifi calling enabled before flashing xposed.
Flashing my stock radio and modem, etc all over the place on not-really-compatible roms could have confused the system.
CrazyJ36 said:
I did have the same problem just after Flashing Rammified and Xposed.
Wipe everything but internal storage worked for me.
Try not flashing Unikernel, I think Rammified already includes it.
When the wierdest things like that happen even though it seems nothing is incompatible I wipe system, data, cache, dalvik, but not internal storage, reflash my desired setup and everything is fine.
It has happened on alot of my Androids.
These things might have caused my the problem you're having because mine ended up the same way:
I had Alliance framework installed and maybe not working. Also Wifi Settings could not stop crashing when I had wifi calling enabled before flashing xposed.
Flashing my stock radio and modem, etc all over the place on not-really-compatible roms could have confused the system.
Click to expand...
Click to collapse
I run Dualboot, so can run multiple roms. I just tried installing onto a test slot which forced me to do a clean install of ramified. It works fine in this test slot. Guess I'll have to clean install ramified on my primary. First I am going to try just wiping system.
I thought ramified installed the edge version of unikernel and it was necessary to flash the S6 regular version.
george241312 said:
Yes this happened to me but i wiped the whole phone except internal storage cache dalvik data system and flashed rom again and contacts.zip and kernel after it booted then installed xposed and it was fine
Click to expand...
Click to collapse
CrazyJ36 said:
I did have the same problem just after Flashing Rammified and Xposed.
Wipe everything but internal storage worked for me.
Try not flashing Unikernel, I think Rammified already includes it.
When the wierdest things like that happen even though it seems nothing is incompatible I wipe system, data, cache, dalvik, but not internal storage, reflash my desired setup and everything is fine.
It has happened on alot of my Androids.
These things might have caused my the problem you're having because mine ended up the same way:
I had Alliance framework installed and maybe not working. Also Wifi Settings could not stop crashing when I had wifi calling enabled before flashing xposed.
Flashing my stock radio and modem, etc all over the place on not-really-compatible roms could have confused the system.
Click to expand...
Click to collapse
I have been playing with this and have intermittently gotten it to work. After getting it to work on my test system, I tried wiping system on my live partition and reinstalling rom, contacts, unikernel, and xposed all at once. Didn't work. On my test system, I did system reset and flashed all. Didn't work. On my test system, system reset, flashed rom, unikernel, and contacts, Rebooted. Initial setup of device, and then flashed xposed. That worked. I am going to try that once more on my test, to convince myself that it is the process and not coincidental. Anyone install xposed without clean install?
Related
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.
Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.
mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?
It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium
Hi
I've got a problem with a Sense modification, specifically with the gestures on the main screen. They don't work since ARHD 8.1 (earlier everything worked just fine on my M7, and on M8)... I've tried wiping, did all the stuff from s-off to changing firmware etc. Everything except this options work fine... And these are my favourite options. To be clear, there's a screen in attachment of what doesn't work. Tried to turn it off and on few times etc. etc. I've even waited for the new ARHD 9.1, did everything to flash it properly, and it does work like a charm except the Sense mods :/
ancymon85 said:
Hi
I've got a problem with a Sense modification, specifically with the gestures on the main screen. They don't work since ARHD 8.1 (earlier everything worked just fine on my M7, and on M8)... I've tried wiping, did all the stuff from s-off to changing firmware etc. Everything except this options work fine... And these are my favourite options. To be clear, there's a screen in attachment of what doesn't work. Tried to turn it off and on few times etc. etc. I've even waited for the new ARHD 9.1, did everything to flash it properly, and it does work like a charm except the Sense mods :/
Click to expand...
Click to collapse
Flashing firmwares has made your kernel unwritable. Dirty flash the rom or flash a kernel to fix it. If that doesn't fix it, you need to do a full clean install, this means when you go to twrp, go to wipe, advanced, click cache, dalvik, data, system and wipe. NOT internal or ext or usb.
an0ther said:
Flashing firmwares has made your kernel unwritable. Dirty flash the rom or flash a kernel to fix it. If that doesn't fix it, you need to do a full clean install, this means when you go to twrp, go to wipe, advanced, click cache, dalvik, data, system and wipe. NOT internal or ext or usb.
Click to expand...
Click to collapse
I've did full wipes few times after flashing rom etc. (i always do full wipes, without sd card) and i didn't help, I'll try flashing kernel once more (maybe got back to stock kernel, not the ElementalX).
update: Flashing Kernel helped, thank You Sir
update nr 2: I've tried if it work with the new google account, and it worked, but when I full wiped, and tried my old google account with my settings it does not work :/
ok, finally I've got it worked - You can't bring back your google settings, if You log on to Your old account, without option of "backing up Your settings, apps etc." it works like a charm... More work to do to bring back all the settings, but it does work.
Everyone having the same problem, I think it's the only solution, tried everything else :/
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes
Wow, that is poor. You aren't having this problem with stock OS?
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.
I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys
Package installer crashes and i cant install .apk files, i tried other installers, but they crash too. Also, when I want to give location permission to app, it crashes saying package installer crashed. What could be the cause? (i know i can install apps through adb, but i dont always have access to computer)
You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.
redpoint73 said:
You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.
Click to expand...
Click to collapse
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.
DarkKnightComes said:
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.
Click to expand...
Click to collapse
Try flashing another Lineage build, is probably the easiest way.
redpoint73 said:
Try flashing another Lineage build, is probably the easiest way.
Click to expand...
Click to collapse
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now
DarkKnightComes said:
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now
Click to expand...
Click to collapse
Ah yes, that pesky gapps. Very easy to forget!
Lineage 16 on the M8, is it a smooth experience?
Cheers