[Verizon Galaxy Note 4 Android Development] dij_333:
[MENTION=5285430]kevintm78[/MENTION] It definitely made MY day when I was finally able to find a ROM that actually made the best of the ORIGINAL software, rather than trying to force-implement things from all the newest phones on the market. Don't get me wrong...the newest phone/features/OS can have some great benefits, and some of them can be wonderfully implemented into older phones (I'm likely to be trying the edge panel mod at some point), but the extra taxing of the hardware (especially with our eMMCs) and potential incompatibilities/bugs that are involved with trying to achieve all the newest extras on an old "daily driver", mostly doesn't seem logical to me. You gave everything a "Modest" approach in the best kind of way, and it is also very refreshing to see someone who consistently remains humble and open-minded in both their approach and response (too many people are too quick to look down upon, talk down to, or place themselves on a pedestal above the rest, especially if those people seem to know less or are just starting out). I also chose your ROM because it's one that includes the best overall support thread, and continues to include great support, even to this day! There's a lot out there that I've come across in my research that hasn't received much (if any) support or updates in about 4 years, and it's a great feeling to know that us Note 4 and ModestROM users have not just simply been "left behind". Thank you once again for all of the efforts, contributions, and support that you continue to give!!! The ModestROM process was very well defined and pretty straightforward, and one could not ask for a better write-up and support thread (except of course for the XDA "search" difficulties that hold us back sometimes). The most difficult part for me was the initial process of rooting and unlocking the CQL1 bootloader that mine came with, without having to downgrade first, as well as the problems of dead links and/or file-hosts being temporarily/permanently down (I even received a public IP security block from the entire AndroidFileHost website at one point due to my repeated download attempts, and had to email their support to request that they remove my block)...but all that was mostly due to the fact that I was mainly stuck reading old forums with a lot of conflicting information about the process (especially regarding what "is" or "isn't" possible with the N910V, versus the processes for the factory Dev edition). Most of my troubles happened before I ever arrived at this thread, as I wasn't researching or trying to decide on a custom ROM until I had fully achieved the CQL1 bootloader unlock. Once I finally arrived at your ModestROM thread, it became pretty smooth sailing from there. I've even noticed (for whatever reason) that the search function seems to perform more efficiently in this thread than it does with many others, so that was a bonus as well!

Sooo, now down to the nitty-gritty...and I apologize in advance if any of my future questions or comments are ignorant or redundant at any point, as I'm sure there will at least be a few along the way, lol...here is my overall progress so far:

After reading all the (older) methods that seemed too ridiculously long and risky to try (aside from running into many dead links, and I'm not much of a programmer), I eventually ended up at https://xdaforums.com/note-4-verizon/development/vzwnote4emmc15chipsetonlybootloaderunlocku-pgradedowngradebootloadersroot-t4018001 to use jrkruse's (THANK YOU [MENTION=1949695]jrkruse[/MENTION]) VERY simplified method of rooting/unlocking the CQL1 bootloader, although it did require an updated version of the KingRoot APK, along with multiple reboots before root was finally achieved (also changed the CID to match the DevEd, which I believe to be a requirement for the unlock). I was eventually able to install the ROM supplied at his link, not knowing for sure any of the details of or modifications that have been made to it (I believe it's just a Magisk-rooted and debloated version of the DevEd ROM, or more likely that the DevEd ROM is already that stripped-down). After getting so far along setting up that ROM, I realized that I didn't truly gain anything aside from the root/unlock/TWRP/debloat, and I was needing a bit more than that. I knew most of what I needed could be achieved with ADB commands and manual system modifications, but I wasn't looking to have to research and apply everything one at a time, and knew their had to be a good ROM available that I could upgrade to and eliminate most of my headaches. After much more research and many ROM comparisons, I had been STRONGLY drawn to try your ROM above all the others. Just to make sure I was completely covered...I wiped everything except TWRP and the unlocked CQL1 bootloader, cleared the cache, re-flashed the CQL1 modem/partial firmware, cleared cache again, flashed MRv11, and cleared cache one final time before booting...it didn't take long after booting MRv11 to confirm that it was EXACTLY what I had been looking for :D. I then configured all my basic settings, installed/tested most of the apps I use, linked my accounts, and made a full NANDROID backup (minus the cache) of my progress up to that point (I know, should have done before installing apps/accounts/etc...I got on a roll because the new ROM was moving along so smoothly for me). After hitting that major milestone, and knowing I had that to fall back on in an emergency, I was ready to begin some deeper updates/modifications/tweaking. First, I performed the "Advanced/WiFi Calling fix, and it works beautifully (thanks [MENTION=5947413]mharleston[/MENTION]). Next, I enabled legacy HD Voice via the AMR setting in the hidden service menu per the instructions provided by [MENTION=4813050]SUNUN[/MENTION] at https://xdaforums.com/note-4/general/enable-servicemenu-galaxy-note-4-hd-t2919157 (probably irrelevant at this point, but performed the extra steps for good measure and redundancy). After (dangerously) poking around the service menu for a while and enabling the setting for carrier aggregation, I reflashed the CQL1 modem/baseband firmware as an extra measure, although I don't think reflashing changed anything due to the fact that service menu settings seem to stick even after reflashing the baseband, as they are stored within the EFS (per my limited understanding)...I don't think simply enabling CA in the service menu provided any immediate benefits either, but I'll come back to that subject in my Q&A. I then attempted to update Magisk by installing Magisk Manager, only to realize the new version of MM isn't compatible with the older version of Magisk included in the ROM. I uninstalled MM and installed the older version that was originally paired with Magisk 15.3 in order to use MM as an uninstaller for Magisk rather than simply flashing the new Magisk uninstaller. After using MM to uninstall Magisk 15.3, I additionally flashed the Magisk uninstaller through TWRP just for safe measure to clear any possible residual files that may have been left over. I then cleared the cache, flashed the factory QCL1 kernel, booted, rebooted, cleared the cache, flashed the latest version of Magisk (v20.3), cleared the cache, booted, installed the latest MM (v7.5.1), rebooted, cleared the cache, flashed your Flashpoint v5 custom kernel, and cleared the cache one final time (way overkill on clearing cache I'm sure...I installed Flashpoint v5 AFTER flashing Magisk per the recommendation from the official Magisk site regarding installing custom kernels). I did make my best attempt at reading and understanding the updated flashpoint kernel thread to see if I could find anything newer/better than your recommended v5 in the MRv11 thread, but most of what is in the kernel thread goes over my head, and it seemed like the recent kernel updates were primarily (if not solely) designed to run on the AOSP ROMs...so I had planned on keeping with your v5 kernel, but have not yet installed a kernel auditor or attempted to apply the JSON file you were running with your Flashpoint v5. At this point, I made another full NANDROID backup in TWRP to protect me before moving along any further. I then attempted to update the MRv11 included version of BusyBox by osm0sis via the latest BusyBox flashable installer zip (v1.31.1) included in his thread at https://xdaforums.com/showthread.php?t=2239421 by flashing through TWRP, which DID install the latest Osm0sis BusyBox module into the Magisk modules list...BUT when using the free BusyBox app by Stephen (Stericson) to verify the updated version, it still shows the original MRv11 version (1.27.2) as being installed to the "/system/xbin/" location. That brings us to exactly the point I am currently at with my MRv11 installation and configurations...and NOW come the questions :D:D:D

I'm not likely to ever directly use BusyBox myself, but since it was already included (and possibly required...if not now, then later), I wanted to make sure that it was updated to the latest version. Is BusyBox an actual requirement for running MRv11 with the way that you have it set up, would it be safe to remove, and if removing/uninstalling/upgrading it, what would be the proper/recommended way of doing so? My hope was that the flashable zip from Osm0sis would fully handle the upgrade for me, but it seems to have simply added the Magisk module rather than replacing the existing version that is embedded into MRv11...but if the old version is required to be embedded into MRv11, maybe the flash did exactly what it was supposed to do??? My main thought was to get it updated, but NOT to have 2 different versions at the same time, if possible. Would it be better to keep the system version AND the new module, remove it from the system and keep the module, or remove the module and just keep/update the version embedded into the system??? I've wandered into VERY unfamiliar territory attempting that one...

Regarding the custom kernel...am I best off to keep your Flashpoint v5 (and possibly add the kernel auditor with you JSON file), or do you think it best to change it for the version 3.1 you provided in your first reply? If changing to v3.1 that you linked for me, is it best to revert back to the stock CQL1 kernel before doing so (likely redundant since you started using AnyKernel), or should I just flash straight from v5 to v3.1 (I know the possibility of breaking ADB was mentioned in the past)? Upon changing kernels, should I uninstall Magisk completely before doing so, or do I leave my new Magisk version as it is, flash to v3.1, and reflash magisk over the top of itself? Is there any need to boot to the OS or clear the cache in between any of the kernel/Magisk flashes (I likely do it way too often for things)? Should I handle BusyBox before or after handling the kernel/Magisk flash, or does the order matter?

I was considering whether or not would benefit me (or mostly just use more resources) to install the "ROM control app" that was mentioned in previous posts of the MRv11 thread. It seems that it was included in previous versions of MR, but not v11, and I don't know how to approach that since I prefer to keep things simpler and more debloated overall, but I do appreciate having certain customizations available, but usually only ones that can benefit my productivity...I'm not so much for just trying to change icons or themes. I found a link to a control app that someone mentioned, but I'm not even sure if its the same one that you included in older versions, or what your specific reasons were for not including it in MRv11 as well. If installing the "control app", I assume it would be best to install it AFTER changing kernels?

I am also trying to update the AdAway version that is bundled in MRv11, but am unsure of the best/cleanest way of doing so. I've been leaning toward using Titanium Backup (unfamiliar with using, and leaning toward the Pro version due to likely needing the extra features) to do it...but I'm curious as to if there are any (clean) alternatives to doing so, since AdAway is already installed as a system app and I'm trying to avoid duplicate versions/installs, as well as avoiding leaving behind any residual files from the old version. Upon moving/uninstalling/updating, do you recommend installing/moving the new AdAway version to the system apps as well, and are there any specific benefits in doing so?

The Verizon Visual Voicemail app bundled with MRv11 does in fact work, but it also has an issue that it won't connect/refresh/retrieve VMs during any period that the WiFi is connected (has the same issue even with 100% stock firmware), showing "error code 9004 / can't connect". I was unable to find any fixes for this, short of trying to forward my voicemails through a 3rd party service such as Google Voice. I have considered forcing the mobile network to stay active (through the developer options menu) even when WiFi is connected, but I'd rather not have that option active system-wide, as I'm sure it would take a toll on my battery, as well as my data allowance. Would you possibly have any suggestions for a better fix? My hope would be some way that tells the Verizon VVM app to trigger/use the mobile network instead of WiFi, but only as necessary. It would be GREAT if i had a fix for this that would work with my father's 100% stock no-root N910V as well, as he has the same issue, and he doesn't want/need any "hardcore" modifications done to his phone. I have considered the possibility that it MIGHT be able to be corrected with an updated Verizon VVM APK, but I've been unable to find any newer APKs that will allow the install due to "compatibility". On a side note, regarding the Verizon apps, I'm also getting "error code 1000" every time I reboot (I believe is related to the "Backup Assistant"), but the information regarding fixing Verizon error codes is very vague and usually just involves disabling apps/services...do you have any knowledge or suggestion as to a "proper" fix for this (disabling or otherwise)? For reference (as already stated in my first post), I'm running the N910V on Straight Talk, but using the Verizon towers/network/VM service/etc.

Regarding the carrier aggregation for the N910V, I don't suppose anyone might have a confirmed method of getting that fully functional, if anyone has even tried?? I believe that all I've achieved with it at this point is "turning it on"...I'm 90% sure it still requires a deeper NV configuration to tell the phone what specific bands to aggregate, as well as defining one as "primary" and one as "secondary", by modifying certain NV values so that the phone knows which CA configuration it is supposed to try to use. Most carriers make use of CA currently, but it was factory disabled on the N910V since it wasn't fully implemented at the time that the phones were being manufactured, therefore it's is also VERY unlikely to have any ACTUAL aggregation configurations on there. From my limited knowledge of the service menu, it appears that no "CA combinations" have been added yet, even though the feature itself has now been enabled. I do realize that CA only kicks in when actively available from the tower, during heavy data usage, and when the phone/tower/service configurations match each other. The tower is supposed to read the CA capabilities of the phone and use the signals accordingly, but if the phone isn't programmed to use any CA combinations, then NO DICE...I have read up some on people configuring their CA to work on newer phone models when changing to a different carrier, but I don't even know where to begin to apply the proper Verizon CA combinations on an old N910V. Given the risks and difficulty involved in editing those NV values, I was hoping maybe someone here might have already figured out the values and combinations to edit before I get a wild hair and start trying to experiment with it myself. There's very little information out there about it, and it's mostly people just trying to enable extra LTE bands rather than combining existing ones for use with CA.

On a further set of side notes, if you have any suggestions, Netflix "could not reach the Netflix service" with error code 15001, but I believe that is a known issue that was mentioned in previous posts by other XDA members, and its the LAST thing I'm worried about getting to work, but if you already know of an easy fix, I'm down to try it! Also, Microsoft Authenticator DOES work on MRv11, however it does not allow the "enable phone sign-in" option to avoid typing an extra password, saying that "this feature is not supported on this device"...I assume due to a security check of some sort that doesn't allow that feature to turn on while using a custom/rooted device. I tried tweaking Magisk a little to see if it would allow it, but haven't been able to make any progress on Netflix or MS Authenticator as of yet (although MS does have basic functionality). I assume the issue with MS is that it falls too far near to the category of "banking apps", and some of the issues that those types apps may face...nonetheless, it is a non-essential feature, and I can try to tweak things to enable it later on (MS phone sign-in feature works on 100% stock...but on my previous rooted ROM before the switch to MR, it claimed that I did not have the screen lock on, no matter what setting the screen lock was actually using). My normal banking apps work flawlessly (Capital One, Paypal), but I do have an app called iSolved go (for viewing payroll/paystubs) that says "an unknown error has occured" when I try to log in. I no longer work for the company that uses that payroll app, so unless they give me a raise and beg me to come back, I wont be needing that app anymore anyway :laugh::laugh::laugh:. Basically this last paragraph was general information about what FEW incompatibilities I've faced while using MRv11, they are all very minor hiccups to me, and it's definitely not any kind of "deal breaker", for sure...I doubt any custom ROM out there for the N910V could come even CLOSE to interacting with apps as smoothly as MRv11 has for me!!!

I'm sorry I've posed so many questions to you Kevin...I know you have many other obligations on your plate. Just know that I HAVE given very extensive research into the majority of these questions/issues, and for the most part have come up short, in-definitive, or (in the case of BusyBox) too far over my head to grasp at this time...I need an expert opinion, lol. I greatly appreciate your timely responses, I completely understand if any of my questions are unable to be answered, and I'm completely open to and thankful for any knowledge that you are able/willing to pass along!!! Again, I apologize if any of these questions feel too "novice" or seem to be poorly researched. I try to be as thorough as I possibly can, and don't want to perform any steps/actions that I'm not fully confident in...thank you again for building such a great ROM!!!

NOTE: I slightly edited this post to include the further inquiry about carrier aggregation that I forgot, as well as to include some grammar/spelling/punctuation errors to make the post a little easier to read/understand.