Database Users

Stay Stock? Or go with custom ROM?

Do you think it's better to stay on the stock ROM, but de-bloat it, or move to a custom ROM?
I'm a little stuck between the two choices.
I realize there are threads on this for other phones, but I am specifically referring to the G2.

Personal
mikenike500 said:
Do you think it's better to stay on the stock ROM, but de-bloat it, or move to a custom ROM?
I'm a little stuck between the two choices.
I realize there are threads on this for other phones, but I am specifically referring to the G2.
Click to expand...
Click to collapse
Totally depends on your personal preference, i tend to like a clean functional ROM with minimal bloat. For myself the stock rom was far to messy and bloated and im not a fan of installing things like xposed, also after tasting kitkat i don't think i could ever go back to jellybean . Keep in mind however due to there not being an official lg kitkat firmware to build off there are still quite a few bugs mainly device specific to the G2 and some rom specific.
Happy Flashing
---------- Post added at 02:46 AM ---------- Previous post was at 02:20 AM ----------
mikenike500 said:
Do you think it's better to stay on the stock ROM, but de-bloat it, or move to a custom ROM?
I'm a little stuck between the two choices.
I realize there are threads on this for other phones, but I am specifically referring to the G2.
Click to expand...
Click to collapse
Totally depends on your personal preference, i tend to like a clean functional ROM with minimal bloat. For myself the stock rom was far to messy and bloated and im not a fan of installing things like xposed, also after tasting kitkat i don't think i could ever go back to jellybean . Keep in mind however due to there not being an official lg kitkat firmware to build off there are still quite a few bugs mainly device specific to the G2 and some rom specific.
Happy Flashing

Downgrade to Marshmallow to avoid bootloop?

My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel

No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!

Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app

rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..

rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk

Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.

Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?

I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app

CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.

I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.

jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!

Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.

Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app

Bad news, and there isnt official answer from Google

I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it

seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.

jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse

CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?

ROM Recommendations

I've been using the Cyanogenmod ROM for a while now, A2016UV1.0.0B20, but I've been noticing a little more instability the longer it's running. Are there any recommendations for what ROMs I should look at, or places where comparisons of the available ROMs are posted? I do need a fairly stable device, and the Play Store doesn't work consistently anymore, even with a few hours of troubleshooting.
If there's already a thread with this kind of information, I'd love to get a link (I didn't spot one as I looked through the recent posts).

I'm using official Resurrection Remix and it is rock solid. Has never crashed on me yet

CandyRom ftw

Keraos said:
I've been using the Cyanogenmod ROM for a while now, A2016UV1.0.0B20, but I've been noticing a little more instability the longer it's running. Are there any recommendations for what ROMs I should look at, or places where comparisons of the available ROMs are posted? I do need a fairly stable device, and the Play Store doesn't work consistently anymore, even with a few hours of troubleshooting.
If there's already a thread with this kind of information, I'd love to get a link (I didn't spot one as I looked through the recent posts).
Click to expand...
Click to collapse
Rerurrection Remix all the way. I went back to stock after some time though, but simply because stock works kinda more fluidly than custom roms. Also NucleaROM has been praised a lot, never tried it myself though.

Only stock ROMs can use the DAC, is that right? The only stock ROM was Bad Boyz?
Is there a guide for stock ROM with magisk? I just want Viper.

baconboy said:
Only stock ROMs can use the DAC, is that right? The only stock ROM was Bad Boyz?
Is there a guide for stock ROM with magisk? I just want Viper.
Click to expand...
Click to collapse
Most developers say that the AKM DAC is always used on all of the ROMs. No one is really sure though.
I think that Magisk 10.2 worked on the stock ROM, but I tried on stock MM a2017G and I couldn't even boot

I'm struggling to find a rom with working 4g... There was a big problem since december that some people from The Netherlands couldn't receive 4g. They fixed it in the last A2017G b04 update, but the modem doesn't work on custom roms.

Hm, I actually hadn't considered going back to stock. The peripheral features that ROMs add aren't typically my focus, as long I have root I can make it do what I want. I'll look into Resurrection though, I've heard good things

IMHO, I think that some phones just aren't worth the trouble of running a custom rom. I believe the Axon 7 is one of them. I've seen a ton of people wanting to go back to stock and have major problems. I have primarily used Nexus devices for the last several years, and they are awesome for running custom roms. The OnePlus is another great phone for tweaking, but to me running Oxygen is like running a custom rom to begin with. I wouldn't feel compelled to run a custom rom on a oneplus device, but it's certainly easy enough to do.
I'm not saying someone shouldn't run custom software on their axon 7, but good luck to you if you do. I'll stick to stock for now and wait until next year when the price will drop on a oneplus 5. See ya!

They do have the DAC working now b19 bootloader magisk unofficial nightly Resurrection Remix Viper 4 arise works with it just fine as well Rock Solid ROM better than stock much better than bad boys. Nuclear kernel is good also. Aicp is supposed to be good also I hear good things about the developer.
Most of the other ROMs right now our unofficial or haven't been developed for a while.

keessonnema said:
I'm struggling to find a rom with working 4g... There was a big problem since december that some people from The Netherlands couldn't receive 4g. They fixed it in the last A2017G b04 update, but the modem doesn't work on custom roms.
Click to expand...
Click to collapse
Try flashing LineageOS over stock B04 without the LOS bootstack. It should work.

If you ever want to get to stock, the best way seems to flash the stock recovery through TWRP, reboot to recovery, then flash an official system update ZIP. I killed my device trying to get back to stock using only twrp so be careful xd
---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------
keessonnema said:
I'm struggling to find a rom with working 4g... There was a big problem since december that some people from The Netherlands couldn't receive 4g. They fixed it in the last A2017G b04 update, but the modem doesn't work on custom roms.
Click to expand...
Click to collapse
Maybe you can flash your ROM then get the B04 modem zip and flash it? I did that with the B04 modem and had a slight increase in cell coverage, so it did work

Choose an username... said:
If you ever want to get to stock, the best way seems to flash the stock recovery through TWRP, reboot to recovery, then flash an official system update ZIP. I killed my device trying to get back to stock using only twrp so be careful xd
---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------
Maybe you can flash your ROM then get the B04 modem zip and flash it? I did that with the B04 modem and had a slight increase in cell coverage, so it did work
Click to expand...
Click to collapse
Didn't work.
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
mario972 said:
Try flashing LineageOS over stock B04 without the LOS bootstack. It should work.
Click to expand...
Click to collapse
I don't think this will work.

Magisk ROM for the J3 Emerge SM-J327P ( Boost Mobile, Sprint, Sprint XAS, and Virgin

**No longer being maintained**
IF YOU HAVE NOT READ AND FOLLOWED THIS POST COMPLETELY BEFORE FLASHING MY ROMS, I DO NOT WANT TO SEE ANY COMPLAINTS!!!
For your SuperSU ROMs go to @Sands207 thread :
https://forum.xda-developers.com/ga...custom-rom-j3-emerge-sm-j327p-t3634206/page83
Magisk ROMs AFH
https://www.androidfilehost.com/?w=files&flid=232990
BOOST MOBILE VARIANT ONLY, AT THE MOMENT.
If anyone wants a magisk build, take the ARG2 stock update and go through intial setup. When you do take the update, you WILL NOT, I repeat you WILL NOT be able to downgrade to the ARF2,ARC1 AQJ3,APL1, AQF4 , and AQB6 versions or you will risk bricking your device.
From now on, ALWAYS, I repeat, ALWAYS, keep Gapps( arm, 6.0, stock) on hand!!!
There is no need to check any of the checkboxes when using the aroma as you should have already wiped dalvik,system,data, and cache prior to flashing the ROM. I have also integrated the no verity ashyx zip into my ROM, so unless data cant be mounted then before flashing rom, there is NO reason to flash the no verity ashyx zip manually. After flashing rom, wipe cache , dalvik and then reboot.
If you like what I do, feel free to donate here:
https://www.paypal.me/DpAmC
Go join this discord for support and announcements for my magisk ROMs and @Sands207 rom family. https://discord.gg/cYVqjBk
Don't forget to join a rank in the #request-a-role channel by reaction.
If you have no carrier then you would use Uncarrier as your carrier.
This is so we can help you easier.
DSP Manager is now working again, so anyone who was having problems with it fc'ing, just re-download from my afh, as i will be replacing the zip with the one that doesnt fc.
If you're having problems with Google dialer, make sure it is set as the default dialer.
**ROM has now been updated with Good Lock as systemUI**
DISCLAIMER!!!!!!!
I am NOT, I repeat NOT responsible for bricked devices!!!
I am gonna say it one more time!! I am NOT responsible for bricked devices!!!

Nothing is free
I guess not

jlrockafella said:
I guess not
Click to expand...
Click to collapse
@Sands207 is doing one.

SonderTech said:
@Sands207 is doing one.
Click to expand...
Click to collapse
I finally pulled us out of alpha and the first beta is ready. She's a little rough around the edges but overall it's pretty nice. I'll update the OP in a few. Once we can get the stock from stable I'll build a device tree and take a crack at compiling and building lineage os and probably others too, hang in there

@jlrockafella and @SonderTech beta will be live soon here https://drive.google.com/folderview?id=0Bz99NuhE3XwmcHUzcmhpZXJ4Sms i included stock boot.img so those who would like to use it instead of supersu can do so. This will be less complicated @SonderTech i included your boot animation too. i have slow upload so hang tight and thank you so much for all the contributions you've made!! ??I'll update the op with simple directions for us in a bit but it's close to stable now

New build up!! ROM is now stable
Sent from my Samsung SM-J327P using XDA Labs

I'm trying to download from Google drive but it says I need permission? I requested access yesterday and it said to wait for an email. Nothing yet.

ExecuterSedriss said:
I'm trying to download from Google drive but it says I need permission? I requested access yesterday and it said to wait for an email. Nothing yet.
Click to expand...
Click to collapse
Newest build is here https://drive.google.com/file/d/0Bz99NuhE3XwmLTZyZnVIaGN3U00/view?usp=drivesdk

I'm a little new to custom roms but I'm learning pretty quick. I can throw the img onto my sd card, factory reset and flash it over in twrp right? Had to do the same **** to root my phone and all that jazz.

ExecuterSedriss said:
I'm a little new to custom roms but I'm learning pretty quick. I can throw the img onto my sd card, factory reset and flash it over in twrp right? Had to do the same **** to root my phone and all that jazz.
Click to expand...
Click to collapse
How you flash this is your choice ? I prefer to flash my ROM's as zips

Sands207 said:
How you flash this is your choice ? I prefer to flash my ROM's as zips
Click to expand...
Click to collapse
I think that's what I meant. The zip is what I would flash over in twrp and then I reboot and wala. Now does this ROM include root, supersu and all that?

ExecuterSedriss said:
I think that's what I meant. The zip is what I would flash over in twrp and then I reboot and wala. Now does this ROM include root, supersu and all that?
Click to expand...
Click to collapse
Yes. All the info is here at the OP https://forum.xda-developers.com/ga...nt/wip-custom-rom-j3-emerge-sm-j327p-t3634206

Thanks so much you've been more than helpful. I do have a final question, though. I don't have boost/sprint but my model is indeed a j327p. It's a virgin mobile phone, I know that might affect it just curious if this was made for all variants.

ExecuterSedriss said:
Thanks so much you've been more than helpful. I do have a final question, though. I don't have boost/sprint but my model is indeed a j327p. It's a virgin mobile phone, I know that might affect it just curious if this was made for all variants.
Click to expand...
Click to collapse
You have twrp on your device now correct? I have successfully built one for boost. Tonight I'm working on the sprint version for a friend and if you like I could make one for Virgin if firmware is available, im doing this in my extra time so it make take me a few days but I'll certainly try if you want me to.

I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
Sands207 said:
You have twrp on your device now correct? I have successfully built one for boost. Tonight I'm working on the sprint version for a friend and if you like I could make one for Virgin if firmware is available, im doing this in my extra time so it make take me a few days but I'll certainly try if you want me to.
Click to expand...
Click to collapse
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.

ExecuterSedriss said:
I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.
Click to expand...
Click to collapse
Excellent I'll have it finished in a day or so I'll update the OP so others can find it as well, I'm almost done with the sprint version now. I appreciate the support and input, thank you
-sands

ExecuterSedriss said:
I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.
Click to expand...
Click to collapse
I built this today for you https://drive.google.com/folderview?id=0Bz99NuhE3XwmajBNY0IyZ2FFWkk I understand you are not fond of touchwiz and neither am I, what i suggest is to install xposed to use gravity box and use the firefds kit along side it to make the ROM however you want. Your ROM is in testing phase so I dont want to tear things apart and replace them until we know whats good and not good. Thank you for your support. Enjoy and follow along as we improve on this base ROM. I used Virgin Firmware so make a backup please first and let me know what you think. It's uploading now so please wait an hour or so for it to finish
-sands

Is the boost mobile ROM, touchwiz?

SonderTech said:
Is the boost mobile ROM, touchwiz?
Click to expand...
Click to collapse
It is for the time being, pulling touchwiz caused ALOT of confusion for folks im working on using a different one but setup is affected without it. Honestly i wish i could use evie as the base without borking the rom

Sands207 said:
It is for the time being, pulling touchwiz caused ALOT of confusion for folks im working on using a different one but setup is affected without it. Honestly i wish i could use evie as the base without borking the rom
Click to expand...
Click to collapse
Ah, I see, you could try making it aosp and see what happens

What Roms is everyone running?

What ROM's are people running on their Verizon LG V20? Im getting ready to root mine and go through that process. Looking over the ROM's though and they seem to be lacking. Back in the day we had tons of options, now we have a handful on XDA. Are there ROM's people are running that arent listed?

Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.

Ashalinia said:
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Click to expand...
Click to collapse
Ive been trying to find screenshots as Im pretty particular on my OS. I used to love MIUI when it was around.

Lineage for ls997 is horrible I'm using emotion build 4-16

pbedard said:
Lineage for ls997 is horrible I'm using emotion build 4-16
Click to expand...
Click to collapse
Why is it horrible? And why is Emotion better?

Depend on what device u using

pbedard said:
Depend on what device u using
Click to expand...
Click to collapse
That's true for anything. Just going out on a limb here, I'm guessing since we are in the LG V20 forum its safe to assume we are using that device.
Next time come prepared with proof of your claim. With no proof and bold claims you sound like a fool.

as Android goes further the ROM field is super small now KK had the biggest amount of ROMS not a lot of this model I have this version too we have RR DU is coming down the line Lineage WETA AOKP Here is a list of ROMS https://www.androidfilehost.com/?w=search&s=us996&type=files

I have a ls997 and im running Paranoid Android.

I have a vs995 and I'm running XOSP ?

Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?

mirrin said:
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
Click to expand...
Click to collapse
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.

mkfryan said:
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
Click to expand...
Click to collapse
that is what i tried first but the rom was not rooted...

Gre thanks

mirrin said:
that is what i tried first but the rom was not rooted...
Click to expand...
Click to collapse
Did you flash supersu or magisk? Not all roms come rooted...

None I had issues getting it to work had issues booting found weta it worked it has a janky root but it worked and Pokemon go worked and I don't even get the static lines on the screen...

BroeknOs to be
Currently I'm running stock OS on LightningZap! kernel (still in beta, but looking like I'll have a release soon).
I have gotten BrokenOs running quite well and smoothly. But lacking the second screen is what's holding me back.
On LG V20 AT&T (H910), btw...