[Sprint  Galaxy Note 4 Android Development] IAmTechFreq:
Coming back again after using this. :)

I Absolutely love this Rom, it's Snappy, Smooth and Overall a N7 Hybrid Experience ;D

Here's my experience....

Obvious Known issues From the Post:

This is the list of known minor issues upon initial release.

Always On Display aka "AOD", Edge Lighting and Night Clock are obviously not gonna work properly.

(I have it turned off by default. You can enable it and play with it as well as try different "AOD "fixes" that may be available)

Fingerprint Scanner not working (Workaround added)

Optical Reader app keeps force closing because well, their's no Iris scanner thats on Note 7

No Iris Scanner (I removed instances of Irus scanner in setting because obviously the N4 has no Iris scanner module)

FM radio is broken (I plan to fix this in the future as time permits. (I simply did not make this a priority )

WiFi calling is impossible to fix. (The IMS versions of N4 and N7 are very different. No way to fix this with the N7 dialer)

Launcher swiping left and right has a glitch where it sticks if you press to swipe between home screens

(use short "flicks" instead and there's no issue swiping left & right) Fixed! Flashable zip fix is in post #2

There are probably a few more minor things that i'm forgetting so I will work on a more precise bug list as I get to them.

***Please report any issues or bugs if you find something. Also PM me so your report doesn't get overlooked in the thread***

BUT Reality Issues!!... On My End

This reminded me when i had my S6 back a few years ago, and I was

Having fun flashing the Stock Debloated and or Deodexed ROM(s)... and hoped it had Advanced Reboot, ROOT,

Viper Audio Mod and a Custom Kernel, etc etc

I Didn't need Xposed, until after the fact that, Snapprefs Stopped working, and that most roms didn't need Xposed for the Advanced Reboot.

But Any ways

==========Installation====

I'm ON PJ1 BL and Modem.

Wiped Phone In "TWRP v3.1.1.0"

"Regular Wipe" then , "Advanced Wipe", and then after wards "Format DATA", then Rebooted into "TWRP" again...

So I flashed this Rom from my 16gb sdcard, and then rebooted into the Phone noramlly, and took awhile like 10-15 Minutes, afterwards.

I noticed SuperSu was installed, so I rebooted the phone Into TWRP anyways.

I Installed the "Modset" for Viper, Camera UHQ+, and Magisk and then MM Vanilla Boot ANimation.

After it was done, I went to make sure Super Su was uninstalled and flashed the Unsu Zip i found somewhere else and then i rebooted the phone back to normal.

And after I let it install, I went into Magisk Manager, and I noticed the safety net wasn't passing..

So I'm thinking it's, The Kernel, that wasn't letting me sign into Snapchat

and the fact that SuperUser in Magisk was set to Enabled Access, might be the other call aswell.

So what i did was, Disable Superuser Access in Magisk and then used the Modset again.... to flash the Stock Kernel it Offered.

Then I proceeded with rebooting the phone and going to snapchat and it worked. :)

So, at this point, i think im having to go back into Magisk Manager and download the install file,

rebooted back into Twrp Flashed the Magisk File.

And now that it rebooted I went into the app and it's working aswell c:

But V4A wasn't so ....!!!!

So, I allowed access for SuperSu on Apps and ADB and then

I went back into V4A prompted to install drivers, i selected allow and then I rebooted the phone

and i went back Into V4A prompt doesn't come up but it's still unsupported....hmmmmm

but ....im thinking if this doesn't work.... I'm probably im having too,

go back into the Modset to flash the Other kernel, Beastkernel again and then reboot back to normal???? let me try that..

So, after I, went back into the Modset and flashed the BeastKernel,I rebooted into the phone and

I went TO V4A 1st and it says it's enabled and Supported. C: YAY! Prob Solved ;)

BUT!! then I go to magisk manager to check the safetynet, it says it was succesful;,

but it says ctsProfile False and

basic Integrity false........

so, I'm not sure what's going on here, but basically what I'm gettin from this is that,

1 or the Other works and then the other doesn't... a.k.a Magisk working Fuly or passing but V4a doesn't get supported

or basically this method right now where V4A does work but MM says false craps..... but it's working and buttery smooth lol

So, I'm guessing now I have to go back into the TWRP and flash just magisk and reboot the phone back to normal?

So, after I flashed Magisk from the Downloaded Zip earlier onto this beast Kernel,

I Rebooted back to normal, still says false but it does detect that it's installed, this time. ANd V4A is working.

Magisk is hiding from Snapchat, and my other module is Android O Emojis.

SO I went back into Magisk, disabled SuperUser Access...just incase....

:)

===Side Note===

So, I guess if i need to use a Rooted App and Grant Permissions,

I would then check to see if it's Disable and then Afterwards Enable it Just for APPS.

Then proceed to the APP ..ex. Root Explorer achieve the prompt, grant root and then go back into Magisk, and Disable it.

=Issue=

When I try to tap on

Reboot and from the "UN7 Power Menu" of selections, it seems as tho nothings working for me.

Doesn't Fully Reboot, it's like a Soft Reboot.

And then once it actually does reboot I'm prompted with this each time

Android is starting. Starting Apps, but I mean it still boots and works....questionable.

==

==Issue==

Samsung Keyboard FCS or closes after I'm trying to type a message with an S PEN and I accidentally select the T with a Pen on it Symbol.

and it was just say that error, or when I was tryign to write a Note Down, with the S Pen it didn't force close that time, but no writing appears, hmm.

So i disabled the Pen Detection.

====

Side note

Usually when I Use SnapMaps and Zoom out , it logs me out beacuse its root checking stuff

and i Have to Go through the same steps again, To log back into it. BUT it didn't happen this time. ;D Profit??

Old Issues...Semi Solved...( Short version, MMC Read Failed, installed Wake Lock Power Manager.)

After some use it would be lagging or have hard lag around 60 or 50% and sometimes even, just randomly,

reboot and it wasn't even using that many apps or processing power and as well as for the screen, it was warm when it would do this.

Switching for apps would be snappy and then I'd just waiting for about 20 Seconds for it to be done lagging...

More so just Random Reboots at around 20% battery life...Started to make me feel less about this Rom ,

I have a new battery so I wasn't sure what my problem was...or why it's happening on this phone or ROM....

Until Later on I realized, I had an mmc read fail. When I was testing out other Roms and properly, Flashing, and etc.

I read through forums and downloaded an app called " Wake Lock PowerManager" and i set it to "Partial Lock Level 4"

And after that I haven't been getting Lag or Random Reboots as bad as it was. Hardly nothing at all.....makes me think for every

other Rom I tested, wasn't because of the Rom maybe it was just my phone acting up... that was 20 Roms Ago tho lol.

And that's my experience, I don't use the Kernel Auditor or anything else, but If I did understood it or if someone can point me into the right direction, I'm hoping i can get it to be as smooth as the Emotion OS R22 Roms kernel or Speed or MHZ and etc, with it being on Balanced Power, nothing higher. C: but yeah.

There ya have it man.