Hello,
I just heard that Verizon is dropping CDMA support at the end of the year and that in order to make voice calls I will need functioning VOLTE. I know AOSP ROMs do not support VOLTE currently, but is there any hope of it working in the near future? I am currently on AOSP Extended and running microG and I love how I have my phone set up now and I really don't want to have to go back to stock to get VOLTE.
If there is no hope of a fix for AOSP ROMs, is there anyone out there willing to make a totally debloated and deodexed stock VS996 ROM that would work with microG? I looked into doing it myself but I think its a little outside my skill set currently, and any guides I could find about it seemed pretty outdated. If anyone has anything that could point me in the right direction or is willing to make such a customized stock ROM that would be awesome. I'm sure I can't be the only with this dilemma, and I would really like to get ahead of this issue.
Thanks!
zsmith95 said:
Hello,
I just heard that Verizon is dropping CDMA support at the end of the year and that in order to make voice calls I will need functioning VOLTE. I know AOSP ROMs do not support VOLTE currently, but is there any hope of it working in the near future? I am currently on AOSP Extended and running microG and I love how I have my phone set up now and I really don't want to have to go back to stock to get VOLTE.
If there is no hope of a fix for AOSP ROMs, is there anyone out there willing to make a totally debloated and deodexed stock VS996 ROM that would work with microG? I looked into doing it myself but I think its a little outside my skill set currently, and any guides I could find about it seemed pretty outdated. If anyone has anything that could point me in the right direction or is willing to make such a customized stock ROM that would be awesome. I'm sure I can't be the only with this dilemma, and I would really like to get ahead of this issue.
Thanks!
Click to expand...
Click to collapse
I've resigned to going to PIE stock for VOLTE--root it with TWRP and debloating it myself by deleting files in TWRP file-explorer
It's easy enough to just load VS996 and then debloat yourself. Not too hard to do that. Only thing to be aware is that you must leave MyVerizon working in order for VOLTE to work... at least that's what I've experienced.
There isn't too much in the ROM that can't be easily disabled, so it's not worth much to wait for someone to debloat manually... that's probably why no one has done it.
I still have the issue of needing to be deodexed in order to apply the signature-spoofing patch required to run microG. Any guides on deodexing I could find were from like 2013 or something and, from what I can gather, may not apply to Oreo and up.
Ran across this with a quick search: https://************/how-to-easily-deodex-android-stock-rom-without-pc/
Well, looks like I can't post a link there? It's from appuals... titled "how-to-easily-deodex-android-stock-rom-without-pc". It talks about using this app which is pretty well rated in GPlay: https://play.google.com/store/apps/details?id=ccc71.at.free
Related
I know I will almost indefinitely be flamed for asking this, but oh well here goes.
When I first got my AT&T SGS2, I installed an international rom (villain) It ran perfectly fine other than the fact calls were not operating properly. I immediately jumped ship though scared for my phone's life. I reflashed stock and AT&T modem, but now that I think back on it- wouldn't having flashed the at&t modem remedied that problem? and if truly need be couldn't an at&t version kernel be flashed( i.e. Entropy's DD) Everything seemed to operate perfectly fine (install went well, booted properly, smooth homescreen, apps running great)
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Entropy512 said:
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Click to expand...
Click to collapse
You go entropy. Awesome. I will be glad to test it for you if needed.
Sent from my SAMSUNG-SGH-I777 using XDA App
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Hammersuit said:
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
Ha! Completely understandable. Thank you so much though, this proof-of-concept is wonderful news. It would be most beneficial to see some ports of well-supported GT-I9100 roms such as villain and DLEV rom etc.
Looks like there might be some known issues with my PoC port then... as I said, I haven't tested outgoing audio much (this is much harder for me to test than dialing voicemail...)
task650 said:
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Click to expand...
Click to collapse
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Entropy512 said:
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Click to expand...
Click to collapse
When I get home tonight ill look at which files I had to replace for dlev rom and shoot them over to you. Might be tomorrow depending on how late though bro.
If you want to see CyanogenMod for this device...start here:
https://www.gofundme.com/j2ja89xs
And follow here:
http://forum.xda-developers.com/lg-v10/general/discussion-cm-12-lg-v10-g4-cm12-t3241897/page26
Once we have Base... Ports are next.
Fingers crossed. Waiting patiently.
Bumping this as we are more then half way there.
I'm excited for a CM base, I don't know about the rest of you...
Even though everyone is excited for a cm based rom, we have too keep in mind that this phone is amazing because of its camera and I'm pretty sure in order to run those features it'll require alot of lg files so in the end , most of us will most likely adhere to stock than cm , at least IMO
tavito05 said:
Even though everyone is excited for a cm based rom, we have too keep in mind that this phone is amazing because of its camera and I'm pretty sure in order to run those features it'll require alot of lg files so in the end , most of us will most likely adhere to stock than cm , at least IMO
Click to expand...
Click to collapse
Yep, and in addition to that there's also the HiFi DAC/Amp and the secondary screen. With such specialized hardware I feel like a debloated stock-based ROM is probably gonna always be the best bet, though of course more development and more options are never a bad thing
Working CM 12 is posted in the development section. Flash away.
Sent from my LG-H901 using Tapatalk
Wow. Amazing! Hoping for CM 13
But having CM 12 is also good ofc!
Thx
No data
Has anyone had any problems with no data I installed 12.1 the latest version with the gapps everything works I can send and receive text messages and phone calls just have no data any answers would be appreciated my data switch is on
I downgraded from 47A to 10B via TOT, then used StumpRoot and installed TWRP. Then I booted to TWRP and installed the 35B bootstack, along with CM13 and an open gapps package.
It seems that literally everything else is working fine; I can receive sms/mms, I can make and receive calls, I have mobile data.
But I just cannot send a text message. My Preferred Network Type is set to Global, and I am using the VZWInternet APN.
I have searched google and these forums but have not found a solution. I have also tried clearing the caches and using the DirtyUnicorn rom as an alternative.
Does anyone have any suggestions as to how to get this working?
EDIT: it seems that making a phonecall does something and then my texts will send. Googling around turned up nothing of use.
There are often issues on non-stock ROMs. Sometimes there's a nightly build that works reasonably well and then another later that breaks things again.
It takes a year/a year and a half minimum for any new version of CM to become kinda sorta stable. Until then it's a constant work in progress.
If you read the last posts in the CM13 thread you'll see you're not alone with issues. I've stuck with VS985 stock based ROMs for a year.
Note that sometimes when users flash either a non-stock ROM or an international-based stock ROM, sometimes they had trouble getting things working right again even when they flash a stock based ROM until they flashed the TOT again and start fresh.
roirraW "edor" ehT said:
There are often issues on non-stock ROMs. Sometimes there's a nightly build that works reasonably well and then another later that breaks things again.
It takes a year/a year and a half minimum for any new version of CM to become kinda sorta stable. Until then it's a constant work in progress.
If you read the last posts in the CM13 thread you'll see you're not alone with issues. I've stuck with VS985 stock based ROMs for a year.
Note that sometimes when users flash either a non-stock ROM or an international-based stock ROM, sometimes they had trouble getting things working right again even when they flash a stock based ROM until they flashed the TOT again and start fresh.
Click to expand...
Click to collapse
Thanks again for the reply. I did notice some people having data issues on some of the later nightlies, but didn't see any reports of sms issues so I thought I might be safe lol.
I'll probably try flashing the 10B tot again then using a stock based rom like you suggested (even though I'm not a fan of LG's ui).
Do you have any recommendations on a stock-based rom to flash? I noticed that in the 47a stock thread you posted about debloating, do you just use a debloated version of 47a? or do you go with some of the other stock based ones with maybe some more features?
inexplicability said:
Thanks again for the reply. I did notice some people having data issues on some of the later nightlies, but didn't see any reports of sms issues so I thought I might be safe lol.
I'll probably try flashing the 10B tot again then using a stock based rom like you suggested (even though I'm not a fan of LG's ui).
Do you have any recommendations on a stock-based rom to flash? I noticed that in the 47a stock thread you posted about debloating, do you just use a debloated version of 47a? or do you go with some of the other stock based ones with maybe some more features?
Click to expand...
Click to collapse
You're welcome!
Both of @xdabbeb 's ROMs are excellent. His 35B (5.1.1) based VS985 v2.0 ROM is awesome, and he took a lot of care and effort in making it. His stock rooted 47A firmware is as stock 47A as you can be while being rooted and able to get into TWRP. In the third post of the 47A thread (and in my signature below) I have a link to my debloat zips post, and also a link to @joshua70448 's really cool online customized debloat zip generator, so you can make your own debloat zip that does exactly what you want.
I flash my "All" debloat zip and for most others I recommend the "No OTA" debloat zip. 47A is just very slightly even smoother than 35B, although it has some idiosyncrasies with USB OTG access (I have to navigate to root/mnt or root/storage - I forget which, to access it in X-plore File Manager), and I consider Xposed and several modules a must. Just use the search field in the 47A thread and type in Xposed and you should find the most important info if you need it. Greenify's aggressive doze feature is helpful, too. When I've hardly touched my phone over a holiday weekend, I've truely gotten, twice no less, 120 hours on battery between charges, but this includes less than an hour screen on time, and just staying home where the signal is consistent, so don't expect that while actually using the phone.
I've been using his 47A debloated since it came out.
roirraW "edor" ehT said:
You're welcome!
Both of @xdabbeb 's ROMs are excellent. His 35B (5.1.1) based VS985 v2.0 ROM is awesome, and he took a lot of care and effort in making it. His stock rooted 47A firmware is as stock 47A as you can be while being rooted and able to get into TWRP. In the third post of the 47A thread (and in my signature below) I have a link to my debloat zips post, and also a link to @joshua70448 's really cool online customized debloat zip generator, so you can make your own debloat zip that does exactly what you want.
I flash my "All" debloat zip and for most others I recommend the "No OTA" debloat zip. 47A is just very slightly even smoother than 35B, although it has some idiosyncrasies with USB OTG access (I have to navigate to root/mnt or root/storage - I forget which, to access it in X-plore File Manager), and I consider Xposed and several modules a must. Just use the search field in the 47A thread and type in Xposed and you should find the most important info if you need it. Greenify's aggressive doze feature is helpful, too. When I've hardly touched my phone over a holiday weekend, I've truely gotten, twice no less, 120 hours on battery between charges, but this includes less than an hour screen on time, and just staying home where the signal is consistent, so don't expect that while actually using the phone.
I've been using his 47A debloated since it came out.
Click to expand...
Click to collapse
Nice, I'll look into what you're saying while I'm at work and then work on it when I get home. And holy crap 120 hours?!? On the HTC One m7 I'm coming from I could maybe get 1/10 of that (very low usage with data off and battery save on), so your 120 sounds like a made up number to me haha.
On a slightly unrelated note, and I'm not sure if you would have an answer to this, but do you have any suggestions on how to get into some more in depth android development? (kernels/bootstacks/roms etc) I believe I have the necessary skills to do so, just never really found a good entry point.
Really though, I know you probably enjoy helping people, but I want you to know that its really helpful having someone reply quickly with great answers.
inexplicability said:
Nice, I'll look into what you're saying while I'm at work and then work on it when I get home. And holy crap 120 hours?!? On the HTC One m7 I'm coming from I could maybe get 1/10 of that (very low usage with data off and battery save on), so your 120 sounds like a made up number to me haha.
On a slightly unrelated note, and I'm not sure if you would have an answer to this, but do you have any suggestions on how to get into some more in depth android development? (kernels/bootstacks/roms etc) I believe I have the necessary skills to do so, just never really found a good entry point.
Really though, I know you probably enjoy helping people, but I want you to know that its really helpful having someone reply quickly with great answers.
Click to expand...
Click to collapse
I know I took screenshots of my battery life the 2-3 times I had 100 or more hours, but I don't know for sure if I uploaded those particular screenshots although I know I commented about my success. I'm very sure I uploaded screenshots to the VS985 v2.0 thread when i was on that ROM, although might not have been quite as extreme as on Marshmallow. 100+ hours is easy with aggressive doze and not travelling/not touching your phone hardly at all.
Are you familiar with Linux? If not, start there since it makes real development easier or is necessary for some aspects. I've just barely scraped the surface - I've just recently made a version of my LG G Pad 8.3 stock ROM that has busybox and SuperSU "baked" in based on @xdabbeb 's examples with his permission. Baking those in and having made the 3MinitBatteryMod for the Sprint Galaxy S3 in the past are the extend of anything approaching real developing I've done, but still not really. Making the stock tablet ROM wasn't really developing - I just followed other's examples and the only thing I modified was a text file.
Open a stock ROM zip of @xdabbeb 's and look at the contents. Look at the updater-script and clean.sh (just text files) in the two subfolders. Open them with the free NotePad++ if you're on Windows to get them to display correctly.
I've fooled mostly with Ubuntu and a little of BBQLinux distributions of Linux for some Android work. BBQLinux is more geared towards Android developing but I'm really not experienced enough to suggest one Linux over another.
Every once in a while I play around with the idea of doing some real developing. I have to considerations I'm keeping in mind: 1. It may be easier to start with something that's already been developed, and try to re-create it as in that case there's already a working reference, such as compiling TWRP or CM13 for the VS985. Once I'm successful doing that, the experience would help me develop for another device. 2. I don't want to actually publish anything that just duplicates what everyone else is doing - there's enough of that in my opinion, so in the end, my aim would be to develop for my LG G Pad 8.3 VK810, since there's at least been *some* development in the past for it, but there's no active or at least public development going on for it currently, and I have particular desires to make the tablet work better that could be addressed by developing.
Thank you and you're welcome! I do enjoy helping people and I get the most out of it when someone has been able to do whatever it is they were trying to do. I've learned from a bunch of helpful people on here and enjoy paying it forward.
roirraW "edor" ehT said:
Are you familiar with Linux? If not, start there since it makes real development easier or is necessary for some aspects. I've just barely scraped the surface - I've just recently made a version of my LG G Pad 8.3 stock ROM that has busybox and SuperSU "baked" in based on @xdabbeb 's examples with his permission. Baking those in and having made the 3MinitBatteryMod for the Sprint Galaxy S3 in the past are the extend of anything approaching real developing I've done, but still not really. Making the stock tablet ROM wasn't really developing - I just followed other's examples and the only thing I modified was a text file.
Open a stock ROM zip of @xdabbeb 's and look at the contents. Look at the updater-script and clean.sh (just text files) in the two subfolders. Open them with the free NotePad++ if you're on Windows to get them to display correctly.
I've fooled mostly with Ubuntu and a little of BBQLinux distributions of Linux for some Android work. BBQLinux is more geared towards Android developing but I'm really not experienced enough to suggest one Linux over another.
Every once in a while I play around with the idea of doing some real developing. I have to considerations I'm keeping in mind: 1. It may be easier to start with something that's already been developed, and try to re-create it as in that case there's already a working reference, such as compiling TWRP or CM13 for the VS985. Once I'm successful doing that, the experience would help me develop for another device. 2. I don't want to actually publish anything that just duplicates what everyone else is doing - there's enough of that in my opinion, so in the end, my aim would be to develop for my LG G Pad 8.3 VK810, since there's at least been *some* development in the past for it, but there's no active or at least public development going on for it currently, and I have particular desires to make the tablet work better that could be addressed by developing.
Click to expand...
Click to collapse
I've actually spent the summer learning unix, so maybe this'll motivate me to actually put that to use haha.
Android developing is really the only thing I wanted to use linux for anyway so maybe bbqlinux is a good option.
Compiling cm13 would definitely be a good start, and I'm sure there are plenty of ways to make personal modifications to it. I guess mainly I want to do the same things as you lol, go where other devs have left or just do things for personal use.
Thanks again for all your help!
I suggest you use an aosp based ROM. Options include Tesla, Tipsy, XenonHD, BrokenOS or Exodus. All very stable options. If you want to build I would suggest linux mint. Ubuntu base, very smooth, lots of support. You can follow this guide to get it set up: https://github.com/PAC-ROM/android_vendor_pac/blob/pac-6.0/docs/PrepareForBuildLinux.md
It is made for PAC, but it is working for the ROM I am currently developing.
Like I mentioned, I'm currently running xdabeb's 47A stock based ROM. I also have a few mods going, like the debloat script and the over sharpening fix. But I've really been out of the 'game' for a while, so I'm a bit confused and overwhelmed. It's kind of like I've unlearned quite a bit so it would be awesome if you could act like I'm completely ignorant in your answers...
Here is a screenshot of my current setup for reference. Please ask if you need any further info.
The point being, I would like to upgrade to the most current software available. Another important issue is that I'm currently living in a house with no wifi and very poor cell reception - so if there is a more up to date version of the radio firmware available, please point me in that direction. Can you also tell me if I'd need to flash any supplemental​ things, like a different bootstack? Is there any way I'd be able to dirty flash an upgrade?
And while we're here, how is the custom​ ROM scene for the VS985 lately? Any suggestions on that front? Because while I've been running a stock ROM for years on this phone, I'd be open to trying something more 'fancy' and customized​. The only requirement is that it's stock based because I really don't want my camera quality to decline. I'd also like to avoid ROMs with big issues like 4G not working on the VS985.
So can you guys please help me out here? My phone really needs a breath of fresh air and I would be VERY appreciative of any assistance.
Thanks!
This is the Rom I been running. Its a whole different bag of stuff though. Theres all kinds of info on here. Youll have to read and figure out what you like. This will get you started though.
https://forum.xda-developers.com/lg-g3/development/oct-n-d85x-ls990-vs985-t3538814
Hello good people.
Now I've rooted my phone, I've gotten a taste for Android customisation, I'm hooked. Have been looking at custom ROM lists and a post over at LineageOS18.com (https://www.lineageos18.com/2021/01/best-custom-rom-for-lg-v30v30-android.html) is stating that someone has ported Oxygen OS to the LG V30, Oxygen OS looks to be the best android variant for my taste, but after several hours of 'poking around the internet', this looks like another clickbait pipedream that I've fallen for. And I would have to port it myself (And given my knowledge of Android, I think this would take me a year to do).
So unless someone has a cheeky port they want to share, I'm wondering if people are keen to share their recommendations on Custom Roms for the V30 US998? And why they like them... Mostly looking for a good solid base for further customization. Keen to get rid of all the bloatware, and have as simple an android experience as I can on this beautiful *old* piece of hardware. Extra credit for suggestions that are running later Android versions The only thing I really want to make sure I can bring over is the quad DAC driver.
P.S. Not too many people running Android 10 or 11 on the v30 by the looks of things... There must be a reason for this?
Cheers
The biggest issue I see with a custom ROM is that you can't get VOLTE/VOWIFI working in most cases. That's the reason I never left stock. I think you can get DAC capability, but you need to be on the lookout for that.
So many people are obsessed with "debloat"... frankly, I don't get it. I have moved on to a Galaxy S10+ phone now for my DD, and it's not even rooted. I don't see the point anymore, but to each their own.
That being said, if you're rooted then why not just debloat and refinish as you desire? This way you can keep the stock ROM and it's functionality. Heck, if you want to throw in a kernel, you can do that on stock as well. I guess what I'm asking is, what are you looking for in the replacement ROM? Why can't you get there from stock?
Thanks for your response shwinn8! You're a champion.
Ive heard of this volte issue, but I guess I don't understand it enough for it to scare me off the idea... Should it though? Sounds to me that I'll simply get a lower bitrate in audio quality in calls...
I recently purchased this phone to have it as a backup phone, to learn android customisation more deeply, and as sort of 'media' device. I may have just bought a mp3 player, but the audio quality on this device is good, and the phone and android experiences are a nice bonus.
I'm really not too worried about the bloatware, Its annoying, but I can live with it. I think you're probably right about staying with the stock firmware, but as an android noob, I guess I'm just looking to get the most out of my device, and before I begin the long process of learning custom theming and widgets, I wanted to optimise my starting point - so I figured the questions were worth asking before I started the process.
what am I looking for in a custom ROM?
Im a UX and UI nerd. I have strengths in these areas, I guess... Due to my neurotic, perfectionist nature. It's not a big thing if I cannot customise everything to my liking, I suppose, I'd just like to have as much control over the customisation as I can get.
I like the way the oxygen os looks, and although I don't have experience using it, from what Ive seen, it looks and functions really nicely. The biggest drawcard for me is the simplicity of their app layouts there. It's very minimal and pretty close to what I would design myself.
I would like a starting point for customisation that is as minimal as possible I guess. In an ideal world I would build my own ROM from the ground up, making all the UX and UI decisions myself. Perhaps this is realistic? Is there any software availability that would allow me to relatively easily do this? I am not a good programmer, but do have some experience.
The issue with VOLTE and VOWIFI is that many US carriers are planning to drop their 3G service "soon" (the dates keep changing), and they will require that all devices support VOLTE in order to retain service. In some cases, the carriers are being dumb and dropping support only based on IMEI model number (ie, if they THINK you don't have VOLTE, then they'll drop you anyway). For example, US998 on ATT works and gets VOLTE, but they may drop people just because it's not an ATT IMEE. For this reason, the clock is ticking for the V30 in the USA.
You say you want to customize the UX, and that's fine. I think that once you're rooted, you can do that with any ROM. (I admit, I'm the opposite - I really DON'T care about UX, as long as it works.) Granted, Oxygen is close to what you already want, so that makes it easier, but if you really want to tinker than I might suggest trying to copy the Oxygen UX that you like over to stock... that way you don't lose functionality. This may require some programming and tinkering, which you are able to do with root. AFAIK, custom roms don't have much MORE functionality over stock, and in fact have less if they can't do VOLTE (which they can't).
That's my opinion, at least.
schwinn8 said:
The issue with VOLTE and VOWIFI is that many US carriers are planning to drop their 3G service "soon" (the dates keep changing), and they will require that all devices support VOLTE in order to retain service. In some cases, the carriers are being dumb and dropping support only based on IMEI model number (ie, if they THINK you don't have VOLTE, then they'll drop you anyway). For example, US998 on ATT works and gets VOLTE, but they may drop people just because it's not an ATT IMEE. For this reason, the clock is ticking for the V30 in the USA.
You say you want to customize the UX, and that's fine. I think that once you're rooted, you can do that with any ROM. (I admit, I'm the opposite - I really DON'T care about UX, as long as it works.) Granted, Oxygen is close to what you already want, so that makes it easier, but if you really want to tinker than I might suggest trying to copy the Oxygen UX that you like over to stock... that way you don't lose functionality. This may require some programming and tinkering, which you are able to do with root. AFAIK, custom roms don't have much MORE functionality over stock, and in fact have less if they can't do VOLTE (which they can't).
That's my opinion, at least.
Click to expand...
Click to collapse
Thanks mate. I'll stick with it. Appreciate the input. *thumbsup*