yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] jhford:
SIM Death

Hi. Sorry to bother, but I want to certain that my reason for installing this ROM is valid before I do so.

1. I just noticed this ROM is a subfolder of the Verizon Note 4 variant. But I have a T-Mobile snapdragon (N910T). The first one died after about 7 years, and I replaced it with this one which is in mint condition for $105. I don't think there's any hardware problem. Does this Verizon issue mean that I'm SOL with MODest?

2. If not, I'm no stranger to custom ROMs; I've installed more than I can count. I'm currently running Ripee's [ROM][UNOFFICIAL][10] Havoc-OS 3.x [tblte][trlte][trlteduos] (https://tinyurl.com/y6o23pf5), and, although I like it a lot, I'm not married to it.

3. MY PROBLEM is that intermittently on boot I have no bars; the icon isn't even present on the Status Bar, which I only noticed this past week. People have been telling me for weeks that they can't reach me by phone. I think this is known as "SIM Death." An XDA member suggested that I install Wake Lock. I installed the oldest version first, then I upgraded to version 3.1.6. However, the intermittent problem persists.

So, do you think that the MODest ROM will solve my problem? If not, do you have any other suggestions?

Thanks for your help.
[Verizon Galaxy Note 4 Android Development] FritzM:
Has anyone tried to upgrade to Magisk 22.0 with this ROM?

I noticed that starting with the Magisk 21.x releases, I could no longer do direct install to upgrade Magisk, but I could use TWRP to flash the separately provided .zip file to upgrade Magisk.

Now with the v22 release, the .apk file contains both the new Magisk v22 App (formerly Magisk Manager) and Magisk v22 itself. The .apk file can be copied/renamed to .zip and that can be flashed via TWRP to install Magisk, but that is only recommended for first time install on an unpatched (no Magisk) kernel. I tried patching boot.img from the Modest v11 Rom zip file, but that failed as shown in attached log file magisk_install_log_2021-02-26T10_01_47Z.log. When I tried direct install, I got the error in magisk_install_log_2021-02-26T10_00_59Z.log (notice that it was unable to find the device path to the boot partition). The file magisk_install_log_2021-01-14T19_17_37Z.log is back on Magisk Manager app 8.0.5 when I tried to upgrade to Magisk 21.2 via direct install. It failed, but it did at least show the correct device path to the boot partition. It seems there were permissions problems back then that prevented direct install, but I was able to flash the Magisk 21.2 zip file with no problem.

I was all the way to Magisk Manager v8.0.7 and Magisk 21.4 when I tried to upgrade to v22. I should have guessed that the failure of direct install was going to bite me eventually.

I decided to fall back to Magisk Manager 7.5.1 with Magisk 20.4 which was the last release before the newer Manager format and problems with direct install, and I am staying with that for the time being.

I am not sure if Kevin is still watching this thread, but thought I would mention what I discovered, so others do not try to upgrade to Magisk v22.
[Verizon Galaxy Note 4 Android Development] signupstuffid:
I have never experienced SIM death with this ROM, on a 910V with Verizon service, and I have another friend on Verizon who has also never had that issue. That same friend changed carriers to ATT, and has used this same ROM on his 910V successfully for two years without experiencing SIM death.

There are likely some small differences using this ROM on a 910T instead of a 910V. I have also used the lineage ROM you mentioned on a 910V, and experienced occasional SIM death. It's worth a try.

If you actually see this message, and try it, let us know how it goes!

** As for avoiding SIM death on boot up of lineage based ROMs, I have done the following before booting, and around 90% of the time, the SIM boots up and is active.

1) Boot to TWRP recovery

2) Mount Modem, Firmware, and EFS partitions

3) Use TWRP to reboot system, which will load Android, and 90% or more of the time cause the SIM to be alive on boot

* As to why specifically this has worked for me, I'm don't know enough to explain why, but it does.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Hello, I'm also having issues with the new Magisk methods. I've kind of been out of the loop for awhile and just recently gotten a chance to get at a few problems that never got fixed. Not to mention the few things that I learned more about since I last posted anything.

Then the new Magisk released and put everything else on hold for a bit.

So far Magisk v21. 4 is the most current working version. I've tried using an unmodified firmware as well and it also failed signature verification. For some reason cp is getting denied access no matter how it's installed. Flashing through twrp gives a success message but it's a false positive. Admittedly though, I'm a couple versions behind with Twrp.

Since it doesn't seem to be a rom issue there's probably enough other people having similar issues that topjohnwu will have this figured out before I do but I do have a couple ideas just in case.

For those who may have gotten their root environment all out whack like I've been doing I'll post my process to at least get your phone stabilized.

You'll need osm0sis' unSU.zip

https://xdaforums.com/attachments/update-unsu-signed-zip.4720903/

A copy of the original boot.img that'll I'll add a link to if anyone needs it. As well as the 21.4.zip that's linked above.

If you have an uninstall option available to you in magisk then do that first. Otherwise just uninstall the manager app like you would any other 3rd party app.

Next boot to recovery and flash unSU.zip, wipe cache/dalvik (possibly unnecessary), install og boot.img, and reboot system. Once it boots completely check your app drawer just to make sure the stub.apk is removed too. It'll just have the generic android icon but it will still be labeled as Magisk. I think it depends on which version of magisk that was last installed so if it isn't there don't worry about it.

After that just boot back to recovery and flash magisk v21.4. Once your phone fully boots it will still take about 2 or 3 mins before you see the magisk manager app show up. Once your to that point everything else appears to be working like it always has and your good to go if you want to add modules or kernel changes. Although if you flash a boot.img you'll need to reflash magisk 21.4, if you flash a kernel that's using the anykernel3 method then it should be ok.

I hope all that makes sense. I have a feeling there's going to be an adjustment period for the new Magisk environment so 21.4 should be viable for awhile still.
[Verizon Galaxy Note 4 Android Development] kevintm78:
FIx for Magisk v22- alpha

Install instructions:

Just download the attached zip and proceed to install either via the Magisk v22 app or if you have v21 installed you can use the direct method within Magisk manager.

I've flashed this zip using several different starting points, with magisk already installed, completely uninstalled, and various stages of half installed. So far the results have been the same. Magisk v22 gets installed correctly but I've still have many tests to run.

NOTICE:

During some of the tests I lost my wifi passwords that has been saved, but the new ones were saved going forward.

As mentioned earlier, I've yet to run many tests so please make a backup in case something goes wrong.

This kernel is compiled source from samsung with minimal changes:

Root restrictions removed

default.prop additions to allow for easier debugging

source code

Let me know how it goes. If you encounter errors dry to grab some logs or explain how to reproduce.

Nirvana's 2nd album...

Thanks to anyone still using this rom! It means a great deal to me and as long as I own a note 4 I'll do my best to support this project.
[Verizon Galaxy Note 4 Android Development] FritzM:
Kevin,

Thanks for continuing the work on this ROM. I love it!

I was running with the Flashpoint 3.1 and the Flashpoint v5 Anykernel installed on top, along with your Kernel Adiutor profile applied. I also was running Magisk 21.4 with Magisk Manager 8.0.7.

I could not install your test4magisk_22.zip via Magisk Manager, so I did the following:

1. Performed backups with Titanium Backup and TWRP 3.3.1

2. Froze Kernel Adiutor via Titanium Backup

3. Upgraded Magisk Manager to the version 22 Magisk App

4. Rebooted into TWRP 3.3.1 and flashed your zip file

5. After "reboot system", I was able to do direct upgrade to Magisk 22 successfully!

I decided to leave Kernel Adiutor disabled since the kernel was marked "dirty" in About-Phone listing, and I was not sure if I should reapply Flashpoint v5 again.

After a number of hours, I started having problems with my App Drawers in Smart Launcher V5. I would switch to different categories and they would be empty. I then started having slowness and eventually the phone rebooted and got stuck with "Samsung" on screen.

I pulled battery and forced my way into TWRP to do restore of Boot, Data, and Cache which got me back to the starting point where I am now, back on Magisk 21.4 and Magisk Manager 8.0.7.

Did I do something wrong in my approach?
[Verizon Galaxy Note 4 Android Development] signupstuffid:
I came back to this ROM specifically because it works properly with VOLTE, which my MVNO using Verizon's towers requires. I still have one 910V running this ROM with the older Magisk v15 just fine.

I have another 910V that was on Resurrection Remix (linked below) and Magisk 20 was working fine.

https://xdaforums.com/t/rom-9-0-0-trlte-resurrection-remix-7-0-2-20190920-official.3899186/

I wiped everything except internal storage before successfully installing V11.

Trying to get any compatible version Magisk to install via TWRP, and I get the following error on all attempts.

- Unpacking boot image

- Unsupported/Unknown image format

- Unmounting partitions

Updater process ended with ERROR: 1 Error installing zip file "/sdcard/insertfilenamehere.zip

After doing some research I found that this is usually a boot.img related problem, so I found the stock boot.img (boot-CQL1-V-VZW-stock.img) Kevin attached on post #2037 and installed it with TWRP version 3.5, rebooted and then tried to flash 3 different versions of Magisk, 15, 18, 20, and all failed with the error above.

I also attempted to use the Magisk uninstaller Magisk-uninstaller-20181208.zip it gave the same Error 1 above.

UPDATE-unSU-signed.zip did seem to give a message that it worked, but after rebooting and trying to install Magisk, still the same error.

Is there something I'm missing, or should try before flashing a stock samsung MM image in Odin, and going through the whole bootloader unlock process again?
[Verizon Galaxy Note 4 Android Development] kevintm78:
Sorry for the delay, I'm not in the habit of checking xda like I used to be and apologies as well for the kernel packaged in the v11 zip. It's difficult to deal with especially with a very old version of Magisk.

I haven't had any issues flashing Magisk until v22. Your process sounds correct though or your very close. I usually boot to recovery, flash unSU.zip and then the stock boot. Then after the system boots up with the stock kernel I go right back to recovery and flash Magisk v21.4. Once that boots up it sometimes takes about 45 seconds before the Magisk app shows up in the drawer.

I also pulled my boot.img that's running Magisk 21.4. If you want to try just flashing that, probably wouldn't hurt to flash unsu.zip first though.

I'm guessing it should work ok although I've never tried installing that way. You may need to install the manager app too so I'll attach it. The patched image is stock but if you'd like to use a custom kernel flashpoint v5 is an anykernel zip so it won't affect your Magisk environment.

Oh, and if anyone is interested, I'm still trying to crack that Magisk 22 problem. I've been digging through a lot of source code and, although I think I've learned quite a bit, I'm still not any closer to solving the problem.
[Verizon Galaxy Note 4 Android Development] kevintm78:
I cleaned up a few mistakes from the original flashpoint v5 zip and also upgraded to the latest version of anykernel3. As mentioned in the previous post, the kernel.zip will not affect your magisk setup. The only part of the ramdisk that gets touched is a few default.prop changes. If you'd like to remove those just unzip the zip file edit the anykernel3.sh file near the end where it says ## Begin ramdisk changes. Then just zip it back up and flash it.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Magisk v22 fix ​

So, this is this best I can come up with. It's not too bad for now at least.

Flash this kernel, that we'll call Flashpoint v6:

Flashpoint v6 download

And in order to past safety net you'll need to use the canary version of magisk

Magisk canary v(22104)

Thanks @FritzM for helping me to see the error of my ways.

Also download kernel audiutor to make sure all cpus are online. If not switch the hotplug to MSM
[Verizon Galaxy Note 4 Android Development] FritzM:
Kevin,

Using TWRP, I flashed your Flashpoint_v5r1 from your previous post, then I flashed Flashpoint v6.

I discovered that the "Revoke USB Debugging Authorizations" option disappeared from Developer options.

I re-flashed Flashpoint 3.1, flashed the Magisk 21.4 zip, and finally flashed Flashpoint v5. The "Revoke" option was there again.

I discovered that flashing either of your Anykernel v3 zip files (Flashpoint v5r1 or v6) causes the loss of the "Revoke" option.

I am back using Flashpoint 3.1 and v5 for now.

Questions:

1. Can you create a new Flashpoint v6 that retains the "Revoke" option, and also includes the v5r1 fixes/changes (if it doesn't already)?

2. When I am ready to upgrade Magisk, I assume I should side-load the canary .apk file to upgrade the Magisk Manager app to the canary Magisk app, then I should do the direct upgrade option from within the canary Magisk app to upgrade Magisk itself. Correct?

3. Regarding Kernel Audiutor, since I am already using it with your custom profile, I assume that I don't need to worry about switching the hotplug to MSM?

During my testing I did not have any issues with CPU's staying offline. I did use Titanium Backup to freeze the Kernel Audiutor app before flashing back to Flashpoint 3.1 just to be on the safe side.
[Verizon Galaxy Note 4 Android Development] theqwertman:
The source code link in the first post doesn't work anymore. I'd like to compile a custom kernel module against this ROM/kernel, and in order to do that I believe I'll need the source code. Is it available anywhere?
[Verizon Galaxy Note 4 Android Development] FritzM:
Kevin,

Just to clarify ... when the "Revoke USB Debugging Authorizations" option is missing under the Developer Options, we are unable to use adb commands as there is no prompting to authorize the adb connection on the phone.
[Verizon Galaxy Note 4 Android Development] FritzM:
Has anyone been able to connect their Note 4 with this ROM to their vehicle's Android Auto enabled USB port?

How about their Note 4 with stock 6.0.1 firmware?

I tried connecting with "USB Debugging" (under Developer Options) both enabled and disabled. In both cases there is a compatibility error that comes up on the 2021 Honda Accord Touring Hybrid's head unit. I also went under the same Developer Options and tried changing "USB configuration" from "Charging" to "MTP(Media Transfer Protocol)", but that just triggers the compatibility error again and then the Note 4 USB configuration reverts back to "Charging" mode.

I have tried 3 different USB cables with the same results. I am assuming that there is some sort of low level hardware/firmware issue because the phone is so old and the car is new. Android Auto is supposed to work with Android 6.0.1 and I have the latest version of Android Auto loaded on the Note 4. The Bluetooth is working fine for phone and audio, so I am just going to use it in that manner, but it would be nice if it could work with Android Auto via the USB connection.
[Verizon Galaxy Note 4 Android Development] dd350:
Yes, I was able to connect my ModestROM Note 4 to Kenwood DMX957XR and DMX1057XR with Android Auto once I got the right cable. I did get that error initially, but it went away on its own. However I can't say my experience was a resounding success. The only apps that worked with it were Maps, Whatsapp and Spotify, and Google Voice albeit with extremely limited functionality such that it was unusable. I don't use Whatsapp or Spotify so that meant only Maps worked for me. AA wouldn't recognize Pandora, and the voice assistant became stupid and didn't understand anything I asked it anymore. It was a big disappointment and I returned both units. In contrast, Carplay on an iPhone worked perfectly... But I'm not taking the nuclear option.
[Verizon Galaxy Note 4 Android Development] dd350:
Here's a workaround to this problem:

How to restore USB Debugging Authorizations on Windows or Linux
[Verizon Galaxy Note 4 Android Development] dd350:
Here's the link:

https://drive.google.com/file/d/1NUZTcbEzJBgF44OwEaG7d4SMeRQZyJQN/view?usp=sharing
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
Hi,

I just dirty flashed over the previous Rom version. So far no problems. I highly recommend you to make a backup in TWRP and also titanium if you have to wipe.

I will report back later how the phone performs. So far no issues...
[Verizon Galaxy Note 4 Android Development] kevintm78:
Yeah I tried it as well. I try to run these roms for a couple days to make sure things like that don't happen . I never use Snapchat, but my banking app checks for root and it runs so I assumed all was well. I see what I can figure out. I still think it may be related to the way the rom kitchen flashes su. If so I might have a suitable fix.
[Verizon Galaxy Note 4 Android Development] mrand1:
Thanks
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
Hi kevintm78

Just wanna give you a quick update. I used your previous Rom version all day and had the same issue again that the screen went black when I was driving and using it for navigation. Rebooted and didn't had any other issues all day. Used it again as navigation when I drove back home today and screen didn't shut off.

I am thinking it might have to do if the battery is full. This morning the battery was at 100 and I plugged it in to the car charger and turned off after about 10-15 minutes driving.

Tonight I started driving at 50% and drove for 45 minutes and screen never went black.

I will keep an eye on it.

Now on your latest version with a dirty flash and so far everything works.

Only "bug" I see us in visual voicemail. The arrow for the drop down menu in the top left corner seems too big for me. See attachment.
[Verizon Galaxy Note 4 Android Development] kpballing84:
yea I had to restart it like 3 time but it work thanks
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
I have a small feature request for the contacts app.

Could you add that it opens the contact detail page if you click on the picture of the contact in the main list. That's how it worked on the note 7.

If you click the name it expands the contact to quickly dial or text and if you clicked on the picture it opened contact details.

So far very stable Rom.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Hey man I attached a zip for stock battery. It kind of looks like the battery is a little close to the clock of you're keeping out on the right, but I can't really tell. That potato clock is real pain in my a$$, it always wants to crowd another icon.
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
[MENTION=5285430]kevintm78[/MENTION]

the new rom runs with emotional kernel? Looks like there is fast charging disabled, could that be? Even in kernel auditor I cant find that option anymore. It was present in Oscar Kernel.
[Verizon Galaxy Note 4 Android Development] kevintm78:
I finally got logged in, but it's a bit of process. Uninstall snapchat then go into superuser app. Go to settings, then to full unroot. It will ask something about restore boot image, click no on that. Then it should reboot on its own, if it doesn't manually reboot. Once the root binaries are gone download Snapchat and you should be able to log in. After that flash the su.zip attached to get root back.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
I can confirm that this works. Thank you so much! I've now backed up my Snapchat using Titanium Backup in case I re-install this ROM or install a new ROM. I would suggest maybe adding a link to that particular reply in the OP for those having similar issues with either Snapchat or anything else that has trouble running with Root installed.

New problem. I absolutely HATE my Status Bar. Thre's too much junk on it, in my opinion. How do I get of it? I only want to see my notifications, Wireless/4G strength, battery percentage and time. It looks like it shows battery percentage twice, one occurrence is inside of a circle whereas the circle illustrates in blue what your battery life is like. I also see a number next to it, I think it's the day of the month (currently 25). Last but not least, I also see Upload/Download bit rate. How do I get rid of all of this?
[Verizon Galaxy Note 4 Android Development] EdrickMG:
After last updated everything smooth and perfect... Small request there is an app called MUVIZ use audio fx, to display bars at the sound of the music, in your rom you use viper so I'm guessing it was deleted but would love to get file to use the app thank you

---------- Post added at 01:16 PM ---------- Previous post was at 12:24 PM ----------

By the way not like a big deal but when you reboot or when start after Samsung screen there is a message of starting apps not know if it's related of xposed or the rom itself thanks for everything
[Verizon Galaxy Note 4 Android Development] kevintm78:
I meant to put an faq section in the op but haven't had a chance yet, but a lot that stuff can be changed in that modest control app. For instance, the traffic mod can be toggled off and under the potato clock section you can go to date style and click on gone. Potato clock is a little weird, you usually have to pick an option in each section or it doesn't do what it should sometimes. Also with the battery, the percentage toggle is in the smart manager app and if you'd rather have stock battery you can flash the file attached or you can wait until I get off work tonight, I'm going see if I can put a zip file together to add the free options for 3 minit battery. As it is now, you would have to get the paid app from the playstore to change battery styles. You can also change the status bar back to transparent in the gradient app. If you set it to two colors and then select the color and you'll see that slider bar under the color box that checkered as it goes to the right. Just slide it all the way to right and it will make it transparent. You'll have to do that for both colors.
[Verizon Galaxy Note 4 Android Development] kevintm78:
I'll check on that sound app, it may have been a part of sound adapt, which I did delete. I'll look for tonight when I get home. On the android starting issue, did that start after xposed. If it did there may be a space in the name of one of your system apps. I was getting that too when added potato clock. I had to change the name of the app from "potato clock" to "potatoclock", getting rid of the space in the name. I thought I had got them all on my end, but just in case, maybe check the ones that are built in as well. I didn't put any of the added ones in folders so they should all be visible at the bottom of /system/priv-app and /system/app.
[Verizon Galaxy Note 4 Android Development] EdrickMG:
I tried it unfortunately the same green screen.... It's a minor thing but oh well just letting you know
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
Where can i find the actual xposed installer.apk to use xposed and install and configure modules?
[Verizon Galaxy Note 4 Android Development] kevintm78:
This is the one I use. I think there's a link to the material version on the jasmine thread.