Develop Bugs

Anyone get V4A to work with Nougat and Magisk?

Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck

I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.
This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287
Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289
NOTE: You are, I believe using the @tdhite kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.

The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.
The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
Sent from my iPad using Tapatalk

@koop1955 Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel
@tdhite Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?
Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol.
Chuck

@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.

koop1955 said:
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
Click to expand...
Click to collapse
No doubt! Version 13 gives me something to look forward to for sure
Chuck

digitalchaos1980 said:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
Click to expand...
Click to collapse
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed

Saafir said:
Place a copy of audio effects.conf in vendor/etc. Should get you working. Be sure to set permissions as well.
Click to expand...
Click to collapse
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.
Sent from my iPad using Tapatalk

[O][8141/8142][.270] M-ROM: Xposed, Daydream compatible

Hello everyone.
The XZ Premium is the LAST of the Mohawk tribe. It's got the genuine feel of unleashed power.
But this amazing masterpiece really DOES lack great ROMs. And, as you guys are not too active in this field, our Chinese friends took their turn.
So as nobody else did organize it into a separate ROM thread, I present this ROM to you. This ROM is NOT my work.
also, I'm NOT responsible for any damage you might encounter.
You MAY request for some corrections, but, as I'm NOT the author of the ROM, I'm not authorized to modify the ROM, NOR i'm really willing to.
Don't expect any updates from ME!
All I've done is the translating of the installer from Chinese into English, replacing some of the software with the international version, tweaking and making this step-by-step tutorial for you. I've spent a few days testing it, to make sure you guys won't have much trouble.
I did it voluntarily, because this ROM is SO GREAT that I just feel necessary to share it with you guys!
All credits to machao44 @ bbs.gfan.com
Remember, this CUSTOM ROM is a modified STOCK ROM.
And the MAIN reason you might need this ROM is the Xposed.
Features:
JanJan's .270 kernel and patch
Aroma configurable installer
DEODEXED
Magisk OR SuperSu
Viper4Android (Optional)
Xposed WORKING (!!!) (XposedInstaller.apk NOT included)
Daydream WORKING (!!!) (Install the Daydream Enabler patch from Magisk repo)
XZ2 Themes
XZ2 UI
XZ2 Camera
XZ2 Loops
XZ2 "Ambient Screen"
Some other stuff from Google Pixel and XZ2
Some old widgets you've been missing (Photos, Top Contacts, Camera)
And some extra minor tweaks.
Changelog [Google Translated from Chinese]
Code:
Updated to 47.1.A.12.270
---------------------------------------
Updated to 47.1.A.12.235 (must be forced to brush 235, otherwise drm is invalid)
Add Android P system animation (Setting - Custom Function)
Add pixel navigation bar animation (set - custom function)
Add status bar clock adjustment (Setting - Custom Function)
Add ram display to multitasking interface
Update multitasking interface locking function Restart does not become unlocked
Update multitasking interface lock icon to display directly
---------------------------------------
Updated to 47.1.A.12.205
Brush machine optional SuperSU or Magisk
Other adjustments
---------------------------------------
Updated to 47.1.A.12.179
Update to graphics brush
(Supported in the TWRP download of the graphics brush machine)
Brush machine optional streamline
Add status bar speed
Add task lock
Add v4a sound
Fixed an error in Ultra STAMINA mode
Other adjustments
Update app
---------------------------------------
Replace the boot animation for the XZ2 original animation
Add dialing to enter the number to display the attribution
Update the attribution of the call log display (display operator)
Add attribution details in the contact details
Delete the third-party call vibration that comes with it
Add native call vibration function (within dialing settings)
Porting XZ2 environment display
Add environment display extensions (lift up bright screen, gesture sensing, pocket mode)
Other adjustments
Ps: There is a patch for the XP framework to use normally in the download.
---------------------------------------
Update the bottom package to 12.119
Fix Bluetooth sharing error
Join the theme of XZ2C
Join the network location of the Bank of China
---------------------------------------
Porting XZ2 icon ringtone media tone theme etc.
Porting XZ2 UI system interface
Porting the XZ2 main camera
Porting XZ2 Loops System Animation
Porting the XZ2 lock screen clock and animation
Porting the Xperia Touch desktop clock (same style as XZ2)
Open environment display
Update app
Note that users of XO1.2.2 and previous roms must clear the data in.
---------------------------------------
Updated to 47.1.A.12.75
Update app
---------------------------------------
Updated to 47.1.A.12.34
Call vibration
Call Recording
Extended desktop
Navigation bar height adjustment
---------------------------------------
Separate the Google service (you can directly brush the Google service pack after you have finished brushing the rom)
Replace magisk with supersu (magisk will cause some apps to be abnormal and new magisk will lose the drm patch)
No longer integrate twrp
Fix screen image
Fully merged with odex
---------------------------------------
1.1.1 update added xperia assistant and several errors caused by not extracting lib
Updated to 47.1.A.8.49
Crack system signature
Add Sony's desktop widget
Add dial T9 pinyin
Add call attribution
Add night mode (blue filter)
---------------------------------------
Fix bug
SELinux status changed to PERMISSIVE
---------------------------------------
Based on 8.0 47.1.A.5.51
Lightweight and streamlined
DRM patch
Disable RIC
TWRP3.1 (power button + volume under power off)
Magisk
Bank Profile + Google Service
PS: Because XZP's TWRP does not currently support graphics flashing (reported to TWRP authors), this ROM does not have a graphics flash.
Old rules, the first version does not add extra features
Lots of tweaks in this ROM have been taken from xda, so credits go to those people as well:
@sToRm//
@zxz0O0
@serajr
@the_brad
@tobias.waldvogel
@Myself5
@sudamod
@mokee
@niaboc79
Instructions and download links are in the 2nd and 3rd post.

First of all, you WILL need an Unlocked Bootloader. I hope you know what it means, otherwise you'll have to RTFM.
#. Long ago I've learned from some wise guy who recommended to always flash a full stock FW before installing a custom ROM based on it. You MIGHT or MIGHT NOT want to do it. But I've NOT tested this FW without flashing the full .270 image upfront via Flashtool, with FULL wipes. (Or, flash 16.20 if you want to go for the 1.8.0. Also, HERE is the discussion on it)
Or this .235:Newflasher+.235
0. Push the Aroma-ready TWRP via ADB.
1. Boot into the Recovery (hold power&vol-) and install the ROM. You DON'T HAVE to reboot afterwards, so you might want to add all the other ZIPs to the queue.
2. Install the Xposed-v90-SDK26-arm64-beta3.zip, which contains - no surpsise - Xposed SDK. You might want to install the SYSTEMLESS version of it, but you will need to find and download it yourself and install it at THIS step, instead of this particular zip.
3. Install the Xposed FIX. It has to be done separately for an unknown reason. I've decided NOT to play with it, trying to embed it into the ROM itself, and left it as a separate zip. MAYBE you don't need it if you're not going to use Xposed, but why use this ROM at all then??
4. Install the Kernel Patch. It's the standard Kernel Patch from JanJan.
5. Optionally, you MIGHT want to install the Sound Mod. I recommend you NOT doing so, because the volume on it is cranked up TOO much, and on my device it began producing crackling sound not even reaching the maximum volume.
6. HERE I INSTALL GAPPS. You might NOT need to do so, but if you want to use the phone with Daydream VR, and also if you might want to use Google Camera (sadly no HDR+, but I use it mainly for a cool Bokeh and 3d panoramas!), you'll need to install the SUPER arm64 8.0 package, which is almost 1gb big. Don't worry, we're going to debloat our device in step 7, deleting 80% of that crap...
p.s. To enable Daydream, install Daydream Enabler magisk module from repo
p.p.s. To enable Google Lens, install Google Lens Enabler magisk module from repo. It will also let you backup the photos with the Google Photos app in original quality as if it were the Google Pixel FOR FREE! It WON'T TAKE UP YOUR SPACE!!!
7. Debloater. Here is what it removes:
Code:
delete_recursive("/system/app/AdvancedLogging");
delete_recursive("/system/app/AnonymousData");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/com.sonymobile.infoapp");
delete_recursive("/system/app/com.amazon.mShop.android.shopping");
delete_recursive("/system/app/com.facebook.appmanager");
delete_recursive("/system/app/com.facebook.katana");
delete_recursive("/system/app/com.s.antivirus");
delete_recursive("/system/app/com.sonyericsson.xhs");
delete_recursive("/system/app/com.sonymobile.xperialounge.services");
delete_recursive("/system/app/com.spotify.music");
delete_recursive("/system/app/com.swiftkey.swiftkeyconfigurator");
delete_recursive("/system/app/com.touchtype.swiftkey");
delete_recursive("/system/app/DemoAppChecker");
delete_recursive("/system/app/DeskClock");
delete_recursive("/system/app/DMAgent");
delete_recursive("/system/app/Exchange-release");
delete_recursive("/system/app/ExternalKeyboardJP");
delete_recursive("/system/app/externalkeyboardsinternational-release");
delete_recursive("/system/app/FitnessPrebuilt");
delete_recursive("/system/app/fota-service");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/GoogleHindiIME");
delete_recursive("/system/app/GoogleHome");
delete_recursive("/system/app/GoogleJapaneseInput");
delete_recursive("/system/app/GooglePinyinIME");
delete_recursive("/system/app/GoogleZhuyinIME");
delete_recursive("/system/app/IddAgent");
delete_recursive("/system/app/KoreanIME");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/Lifelog-googlePlayLiveRelease-4.0.A.0.14-8388622");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/newssuite");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/playstationapp");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/app/PrebuiltBugle");
delete_recursive("/system/app/PrebuiltDeskClockGoogle");
delete_recursive("/system/app/PrebuiltExchange3Google");
delete_recursive("/system/app/PrebuiltGmail");
delete_recursive("/system/app/PrebuiltNewsWeather");
delete_recursive("/system/app/SemcEmail-release");
delete_recursive("/system/app/SemcWarrantyTime");
delete_recursive("/system/app/SomcMovieCreatorRmm-release");
delete_recursive("/system/app/Tycho");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/com.facebook.services");
delete_recursive("/system/priv-app/com.facebook.system");
delete_recursive("/system/priv-app/com.sonymobile.retaildemo");
delete_recursive("/system/priv-app/EnterpriseService");
delete_recursive("/system/priv-app/NexusLauncherPrebuilt");
delete_recursive("/system/priv-app/sonyentrance2-release");
delete_recursive("/system/priv-app/textinput-chn-xxhdpi-release");
delete_recursive("/system/priv-app/Turbo");
delete_recursive("/system/priv-app/UpdateCenter-release");
delete_recursive("/system/priv-app/usb-mtp-backup-transport");
delete_recursive("/system/priv-app/usb-mtp-factoryreset-wrapper");
delete_recursive("/system/priv-app/usb-mtp-fotaupdate-wrapper");
delete_recursive("/system/priv-app/usb-mtp-update-wrapper");
Voila.

1.6.1 Google Disk.
1.8.0 - as is!!
Beetle84's contribution, translated 1.8.0 installer
The folder should contain:
aroma-ready twrp.img
1. ROM image. Google, Yandex
2. Xposed SDK
3. Xposed FIX
4. Kernel Patch (JanJan's)
5. Optional Sound Mod (DontBelieve)
7. Optional debloater patch
Enjoy!
Known issues:
#0. I'm not the author of the ROM. I'm only sharing with you what's working for me. I am not a professional developer either. Please remember it's a COMMUNITY, not a workshop.
#1. Substratum DOESN'T WORK.
#2. If you WON'T upgrade your phone fully to stock .270 via FLASHTOOL (!), or if you won't flash the included .235+newflasher beforehand, your G8141 WILL NOT RECEIVE ANY SIGNAL.
#3. SOME G8141 users still report having NO signal. Try flashing your device as G8142, and then flash the G8141 kernel manually before step 4. You can find the Shoey's G8141 kernel inside the zip file of ROM. Don't foget to patch.
#4. If you can't stand the one tab in Settings that's in Chinese, here's the translated settings.apk
1.8.0 settings.apk
#5. DON'T UPDATE XPOSED AND MAGISK.

Screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to hate me, but I still have no signal. This is driving me crazy.

It is a very very fast and stable rom
Used the original 1.6.1 and it is fast

Mobfigurz said:
You are going to hate me, but I still have no signal. This is driving me crazy.
Click to expand...
Click to collapse
So, you redownloaded the ROM, and you chose the G8141 kernel while installing, and it didn't work?
Are you sure you're using the right files?
Did you flash 235 or 270 beforehand? Try flashing full .270 or 235 upfront and then install this rom on top of it.
Else, I don't know why @amakuramio has no problem with her G8141...

karrouma said:
It is a very very fast and stable rom
Used the original 1.6.1 and it is fast
Click to expand...
Click to collapse
I only translated the installer and embedded the G8141 kernel in it. Adding gBoard doesn't count, so, it's the same ROM you're talking about And yes it's fast!

Very fast!!
Thanks again for your time

saved-j said:
So, you redownloaded the ROM, and you chose the G8141 kernel while installing, and it didn't work?
Are you sure you're using the right files?
Did you flash 235 or 270 beforehand? Try flashing full .270 or 235 upfront and then install this rom on top of it.
Else, I don't know why @amakuramio has no problem with her G8141...
Click to expand...
Click to collapse
Yes, redownloaded your files and installed in this sequence, 1, 2, 3, 4, 7 and no change with the signal, still not able to pick up a network, even when I search for it and click it, tell me I cannot register on the network.
I did a clean flash of .270 yesterday and started on the files you shared, I will flash .270 from scratch now and run through the files you provided and report back.
I do appreciate all your help, this is just a glitch and hopefully I will have a fully functioning device soon.

Mobfigurz said:
Yes
Click to expand...
Click to collapse
Very strange.
By the way. Once you flash the stock FW... Run it and check if your phone receives the signal on the stock FW.
Then try dirty flashing (without wiping /data).
Also, after the full installation, if the signal still doesn't work, try pushing the JanJan's kernel via ADB and patching it, then wipe dalvik/cache and try for luck once more.
If there's no luck, maybe you really need to flash the .235 ~150mb that @amakuramio mentioned. I'll try to find it and then I'll upload it to the Google Disk. I'll let you know when it's there.

Mobfigurz said:
Yes
Click to expand...
Click to collapse
DONE.
Try here
Is your phone provider-locked, or locked to the network, or sim-card, or in any other possible way? Call the provider and tell them you "updated the software and the phone stopped receiving the signal, so you had to roll back to be able to make this call"... Maybe try another SIM card as well... Check everything to exclude every single stupid possibility!

saved-j said:
Very strange.
By the way. Once you flash the stock FW... Run it and check if your phone receives the signal on the stock FW.
Then try dirty flashing (without wiping /data).
Also, after the full installation, if the signal still doesn't work, try pushing the JanJan's kernel via ADB and patching it, then wipe dalvik/cache and try for luck once more.
If there's no luck, maybe you really need to flash the .235 ~150mb that @amakuramio mentioned. I'll try to find it and then I'll upload it to the Google Disk. I'll let you know when it's there.
Click to expand...
Click to collapse
Stock 270 have network signal. Images attached.
I think something is missing, there is nothing I have removed or added to your file collection to alter it, so something must not be doing what it should be doing for single SIM, G8141.
I am going to flash your files over this now and see what happens.
Update - Back to no signal, I think the Kernel is not set for G8141, only G8142.
Update - Flashing JanJan's Kernel obtained from his/her thread gives me the same issue, no signal. I am going to flash from the beginning, stock .270 and then JanJan's kernel and see what happens. But, if I do that and have a signal, would flashing Xposed and the Xposed fix in TWRP without M ROM give me a working Xposed?
UPDATE - The issue is not with JanJan's Kernel,it is with M ROM, as I installed Stock .270, installed JanJan's Kernel and additional files and booted fine, strong signal, Root and DRM, but obviously no Xposed.

Mobfigurz said:
M ROM
Click to expand...
Click to collapse
I'm sorry bro. I will think what could be causing this issue. I'll try to inspect the differences between 8141 and 8142, but don't expect it to be soon ?

Mobfigurz said:
Stock 270 have network signal. Images attached.
I think something is missing, there is nothing I have removed or added to your file collection to alter it, so something must not be doing what it should be doing for single SIM, G8141.
I am going to flash your files over this now and see what happens.
Update - Back to no signal, I think the Kernel is not set for G8141, only G8142.
Update - Flashing JanJan's Kernel obtained from his/her thread gives me the same issue, no signal. I am going to flash from the beginning, stock .270 and then JanJan's kernel and see what happens. But, if I do that and have a signal, would flashing Xposed and the Xposed fix in TWRP without M ROM give me a working Xposed?
UPDATE - The issue is not with JanJan's Kernel,it is with M ROM, as I installed Stock .270, installed JanJan's Kernel and additional files and booted fine, strong signal, Root and DRM, but obviously no Xposed.
Click to expand...
Click to collapse
I have g8141 and dont have a signal issue, try to download internet settings or manually enter APN.

Beetle84 said:
I have g8141 and dont have a signal issue, try to download internet settings or manually enter APN.
Click to expand...
Click to collapse
His phone doesn't receive ANY NETWORK. Like if there was no sim-card. With all respect, I don't think your advice is relevant.
But it's surely very important to know that you don't have the signal issue on your 8141.?

[email protected] updates the brand new ROM.

saved-j said:
His phone doesn't receive ANY NETWORK. Like if there was no sim-card. With all respect, I don't think your advice is relevant.
But it's surely very important to know that you don't have the signal issue on your 8141.?
Click to expand...
Click to collapse
After tinkering with the packages and flashing them in different sequences I managed to get going. In M ROM Aroma installer I ignored the G8141 option and let it flash the G8142 files and bingo, Network Signal and showing SIM 1, the software thinks it is a 8142 and I tinkered some more, got Xposed running, but then, I had a major issue, System UI crashed and would not re-appear after installing some Xposed modules.
I think, if I can find 12.75 I am just going back to that, I just need a stable, working phone for daily use and though others seem to work, mine does not. SO I thank you all for your help and assistance.
Who knows where I can get a '3 UK' 12.75 ftf or any 12.75 ftf as Xperifirm does not keep older roms?

Mobfigurz said:
After tinkering with the packages and flashing them in different sequences I managed to get going. In M ROM Aroma installer I ignored the G8141 option and let it flash the G8142 files and bingo, Network Signal and showing SIM 1, the software thinks it is a 8142 and I tinkered some more, got Xposed running, but then, I had a major issue, System UI crashed and would not re-appear after installing some Xposed modules.
I think, if I can find 12.75 I am just going back to that, I just need a stable, working phone for daily use and though others seem to work, mine does not. SO I thank you all for your help and assistance.
Who knows where I can get a '3 UK' 12.75 ftf or any 12.75 ftf as Xperifirm does not keep older roms?
Click to expand...
Click to collapse
I have the Australian .75 firmware I think and I have TurboROM p75d which I will upload to mega for you. My internet's pretty crap though

I have 12.75 both in US and CE1. And I also have pretty much all Turbos roms

Xposed and Safety Net Pass -- How To!

XPOSED and Safety Net PASS -- Instructions How To
I've been using Xposed because it has functionality that I don't want to give up. But "regular" Xposed won't pass Safety Net.
Thanks to @drewcu, I now have found a way to use Xposed and PASS Safety Net.
This is important enough it deserves its own Guide thread. All credit goes to @drewcu -- and of course the edXposed devs! Go here and THANK this post. Full exchange is below, but please go thank @drewcu in that post.
_______
drewcu said:
Installed Magisk and edXposed and all is well.
Thanks!
Click to expand...
Click to collapse
ChazzMatt said:
First hearing about "edXposed". Quick Google search, sounds interesting, and some say it allows you to pass Safety Net, which regular Xposed (I use) doesn't. Is that true?
Which Magisk version are you installing with that?
Click to expand...
Click to collapse
drewcu said:
Latest Magisk 19.3.
YES, EdXposed absolutely passes Safetynet (both ctsProfile and basicIntegrity)! Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!
Click to expand...
Click to collapse
TotallyAnxious said:
Thanks. I've been meaning to check out the new Xposed offshoots.
Click to expand...
Click to collapse
_________
@drewcu:
edXposed INSTRUCTIONS
Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!

When I go to download the file, it's in, I assume, Chinese characters.
Any help.
Never mind, figured it out.

This is great. I'm so happy to have Gravity Box again.

I too had a problem with lag with newer versions of edxposed. I switched to the version recommend in the OP and all is well.

If you comfortable using "chinese" app. Taichi is simpler solution (personally), although not much modules currently supported. Both edxposed and taichi are available on magisk repo

Thanks @ChazzMatt, finally got around to installing Xposed again. Thank god for GravityBox!
edit: after playing around for a day, I'm disabling edx. I'm getting lag, force closes, unresponsive back button, and major battery drain. Sad to see the framework hasn't changed much in 1-2 years. It's not worth it for a single Xposed module.

Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?

qwas7899 said:
Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?
Click to expand...
Click to collapse
Edit; figured it out

qwas7899 said:
Edit; figured it out
Click to expand...
Click to collapse
share with the class.

Right. Didn't have riru-core module installed.

Thanks a lot for this guide . It's great to have xposed and safety net passing.

soo I tried to install edxposed sandhook (latest version), after a couple reboot, all went fine, but now I lost wifi and data connection (they cant be turned on), any ideas or fix? is it linked to that version of edxposed? I have a Lg ls998 converted to Us998h, thank you

LeTerrible said:
Just wanted to share my experience with NFC banking and FullHD working Netflix. Managed to delete everything google and installed Microg only (to get Gcam to work), my banking app, Netflix app, Canary EdXposed and it works flawlessly! Could never get FullHD and NFC banking to work previously with Xposed. Of note was the fact I am running Xprivacy, too. Just make sure you blacklist the apps in EdXposed and also hide them in Magisk and it all works
Hope this helps others as it really made my NoGapps/Rooted stock phone experiences significantly better.
Click to expand...
Click to collapse
Great.

I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?

radwolf76 said:
I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?
Click to expand...
Click to collapse
Solution Found. My EdXposed Manager had been installed to External Storage. It only works on Internal Storage.

Safety Net Fail w/ Gravitybox
It looks like as soon as I enable the Gravitybox module that you recommend, safetynet fails. Are you still passing with your setup (I'm wondering if there has been some update that this version of Gravitybox no longer passes)?
UPDATE: even though safetynet shows up as failing in Magisk, I am still able to use Google Pay, so maybe it is working? I'll update this post once I've tried using Google Pay to pay for something.
UPDATE again: after a couple of days, Google Pay showed a pop up message saying that it would no longer work. Uninstalling and reinstalling gets it working temporarily again it seems.

Dear @ChazzMatt
Should I install the old beta in the last page or the latest canary to avoid safety net and which versions is the best?

Note to everyone: installing xposed framework will trigger safetynet....and uninstalling it will do as well
And i don't know how to solve this except flashing a new rom

[ROM] [OFFICIAL] [AOKP 9.0/Pie] [cheeseburger] AOKP Pie for OnePlus 5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ROM][AOKP 9/PIE][cheeseburger] AOKP Pie for OnePlus 5
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Introduction
WE ARE LIVE!!
AOKP is a ROM developed by TeamKang, based on AOSP/LineageOS with magical unicorn bytes (awesome features) baked right in!
Features
Android 9 Pie
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
Custom animations
Customizable AOKP logo in status bar
So many other features, explore and find them on your own!
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
Click to expand...
Click to collapse
Known Issues
Pixel Launcher crashes constantly if you try to use it. This is an upstream issue, Lineage-16.0 has the same issue.
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Ensure you have the proper firmware installed (9.0.9)
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
Official AOKP download page:
AOKP cheeseburger files
Source:
AOKP Source
Kernel source
Click to expand...
Click to collapse
Changelog
Initial Official release.
Thanks To/Credits
TeamKang
tdm
LineageOS
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Pie Android Open Kang Project for OnePlus 5 [cheeseburger], ROM for the OnePlus 5
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, TWRP 3.2.3 or later by codeworkx (Other TWRP versions not tested!!), Firmware package from OOS 9.0.9
Based On: LineageOS, CyanogenMod, OmniRom, AOSP
Version Information
Status: Nightly
Created 2020-01-20
Last Updated 2020-01-24

Reserved

Reserved

Builds are LIVE!!
Hey guys, AOKP Pie is OFFICIAL! Download links are in the OP, and I am including them below.
http://xfer.aokp.co/?developer=AOKP&folder=cheeseburger

This ROM doesn't officially support signature spoofing/microg?

Pokemetti2 said:
This ROM doesn't officially support signature spoofing/microg?
Click to expand...
Click to collapse
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.

Does this rom has a working googlepay support?
I have been on stock oxygen OS roms for too long and i am thinking about a change.
EDIT: it is working. Had to make sure that safetynet is passed and using hidemagisk on google products

shane87 said:
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.
Click to expand...
Click to collapse
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.

d1n0x said:
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.
Click to expand...
Click to collapse
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.

shane87 said:
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.
Click to expand...
Click to collapse
That's fine by me, just wanted to know whether I had to flash NanoDroid Patcher.

Update to OP
Hey guys, I just wanted to point out that I made a small update to the OP. I included a notice of the required firmware package from OOS that this ROM needs. Currently that is 9.0.9. We ran into an issue over on 5T, and it likely had to do with incorrect firmware on the phone. I forget that not everyone pours over gerrit as much as I do, so they don't see the required firmware commits.
I will update the OP, and post an announcement, any time that we update the firmware base required.

I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.

fosunite said:
I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.
Click to expand...
Click to collapse
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.

shane87 said:
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.
Click to expand...
Click to collapse
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.

fosunite said:
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.
Click to expand...
Click to collapse
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

Added to the OnePlus 5 Index Thread here.

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Sorry it will take a while, because i am unfamiliar with doing logcat. I will try connect my phone to pc via adb and try to log the events. It s quite tough doing while phone should boot.

newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Ok, Finally managed to pull a logcat. Hope this helps.
rikkker said:
newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?
Click to expand...
Click to collapse
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.

fosunite said:
Ok, Finally managed to pull a logcat. Hope this helps.
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.
Click to expand...
Click to collapse
Thanks for the logcat. I'll dig into it this weekend and see if it shows anything interesting. Quick question, have you tried lineage 16? If so, does it do the same thing as far as the sim1/sim2? Since we base off of Lineage, I want to make sure that the issue is linked to AOKP, and not something that we have inherited from lineage. I only have a single sim, so I can't test myself.
On the flashing sequence, I have personally never had any issues with flashing magisk right away, but ymmv. I do a wipe/factory reset, (after backing up via tibu and/or nandroid back up in twrp), manually wipe system, cache, and dalvik cache, flash ROM, flash magisk, flash gapps. Again, YMMV.
Also, you ONLY need the no verity flash if you have unencrypted your data partition. I left my data partition encrypted.
I have not flashed the 01/31 build yet, but I will check it out, probably tomorrow.

[DISCONTINUED][ROM][9.0][SM-G930F] Lightheart OS [30/10/2020]

Lightheart 1.0 - The key to speed.​
Hi everyone. My name is Skulldron and for those of you who do recognise me, know me as the creator of Project Pixel, another one of the greatest ways to emulate the Pixel Experience, whilst keeping all the benefits of using OneUI and its stock optimized drivers as its base. Today I'm going to introduce something, different. Over the years of working on Touchwiz based ROMs, I've learnt the description of every little apk, every little permission, what it accepts and what it rejects, its pros and its cons. As a result of this experience, I have one of the best debloat lists out there, with each item on the debloat list, being tested, through extensive testing, and it goes over every file and every partition known in the OneUI OS. This exact same debloat script was used in Project Pixel, which has received positive review after positive review for how efficient and how lightweight OneUI became after the debloat. Today however, I present to you Lightheart OS, a new project that I will be building myself and updating monthly. Today I showcase Lionheart, the Lineage OS to my Cyanogenmod.
Key Features:
1. Heavily Debloated System: The debloat script that was made by me, has over 250+ debloated permissions, apks and other files.
2. Better Battery Performance due to Efficiency - With the removal of an incredible amount of bloat, along with better performance and lesser services, you should be looking at better SOTs and better standby times.
3. Kernel Power Control: With MTweaks and Magisk, you will be able to control your device’s clock speed and be able to force higher GPU and CPU Clock, when doing more intensive tasks such as gaming.
4. Better Kernel Performance - Due to the deepness of the debloat, the kernel now has more RAM and more space to be more efficient and allow it to focus on less threads at once.
5. Latest available patch with the promise of updates every month - Every month an update is released, the ROM will be updated along with it, with a time frame of 1-2 weeks.
6. Restored some stock Google Permissions - Some stock google framework was restored, such as the default setup wizard.
7. All Essential Samsung Features have been kept - All essential OneUI features have been kept alive, for the sole purpose of necessity.
8. Completely Deknoxed -The ROM has been Deknoxed and FRP lock measures have been disabled
9. VoLTE Supported
Individual Features:
1. AdAway
2. Eleven Music
3. Files GO
4. GBoard
5. Android Pie AOSP Emojis
6. Lightheart X Boot Animation
7. AOSP System Sounds
8. Samsung Gallery (Stripped Down and lightened to improve performance)
9. Samsung's Stock Camera with HDR parameter changes, debloated and additional video modes
10. SystemUI Tuner (Provides battery stats along with other useful customizations - Check QS icons and add it to QS Panel to view)
11. YouTube Vanced (Ad-free Youtube)
12. Mtweaks (Has Hardware Control - Similar to Kernel Adiutor but more tailored to Exynos)
INSTALL INSTRUCTIONS: (Backup everything,contacts, photos etc.)
1. Download the zip and download the latest Magisk (ROM will not boot if Magisk is not flashed due to encryption procedures)
2. Wipe System, Data, Dalvik Cache and Cache
3. Flash the zip and flash Magisk.
Notes:
- To view Battery Stats and Storage, pull down the Quick Settings Panel and on the top right click the three bubbles button and then Button Order. Then move the new Battery and Storage icon to the Quick Settings.
- Set Trebuchet as default launcher, for better battery savings. OneUI Home was only included for its app switcher.
Changelog:
1.0 - Initial Release
If changes are made, they will be highlighted in the next post.
Download Links:
1. Lightheart 1.0:
https://drive.google.com/file/d/1cqQXrQecOmmXEhXnUx6GL8aV7_Xsarwk/view?usp=sharing
2. Magisk Manager:
https://github.com/topjohnwu/Magisk/releases
3. Magisk:
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Credits and kernel source:
Cronos Kernel Source: https://github.com/ananjaser1211/Cronos_8890/releases/tag/V4.0-Pie
@arcatarc for permission to use his base
Check the screenshots tab to see screenshots of the ROM in action.
XDA:DevDB Information
Lightheart 1.0, ROM for the Samsung Galaxy S7
Contributors
Skulldron
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Bootloader Available
Based On: OneUI
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-10-30
Created 2020-10-30
Last Updated 2020-10-31

Samsung note fe base???

Hi, thanks for the ROM. Will try it. Could you please provide md5?

Can't use GPay

mie_ayam said:
Samsung note fe base???
Click to expand...
Click to collapse
Yes it is running the base from a Note FE. In particular the SuperLegerra ROM

wow, ... and echo cancellation works perfect ... but two things that I miss so far
the option "kill app back button" in the settings -> developer options ... please don't forget to build-in
the possibility to mount the SD card in the file system
Both options are default in LOS ... and yes, I know it was an initial release.
Thx for your work. we are hopefully waiting for the improvements!
:good::good::good:

Download and trying to install tonight

Info regarding phone stuck on boot pic
Hi there,
I have little experience with custom roms etc. I had installed LineageOS some moths ago as my phone was working poorly on stock rom and now with LOS 17.1 was starting to have problems again. Like an hour ago decided after some research to install this rom. However, after flasing the rom and magisk (I couldnt flash Gapps as error 20 appeared), my phone got completely stuck on boot picture (SAMSUNG GALAXY S7; POWERED BY ANDROID). I have both tried to get into twrp (previously installed) and download mode. No luck in any of the cases. I have tried to do the same from odin, to flash again twrp. However, as I cannot access download mode, I didnt work.
Now, I´m trying my best to figure out how to install some OS and continue from there, or at least be able to flash twrp and install another ROM.
I would much appreciate any advice in the matter.
Thanks in advance.
EDIT: NEW SITUATION. No need of help anymore (by now)

iggamez said:
Hi there,
I have little experience with custom roms etc. I had installed LineageOS some moths ago as my phone was working poorly on stock rom and now with LOS 17.1 was starting to have problems again. Like an hour ago decided after some research to install this rom. However, after flasing the rom and magisk (I couldnt flash Gapps as error 20 appeared), my phone got completely stuck on boot picture (SAMSUNG GALAXY S7; POWERED BY ANDROID). I have both tried to get into twrp (previously installed) and download mode. No luck in any of the cases. I have tried to do the same from odin, to flash again twrp. However, as I cannot access download mode, I didnt work.
Now, I´m trying my best to figure out how to install some OS and continue from there, or at least be able to flash twrp and install another ROM.
I would much appreciate any advice in the matter.
Thanks in advance.
EDIT: NEW SITUATION. No need of help anymore (by now)
Click to expand...
Click to collapse
Could you write down here how you can solved the proble, it might be helpfull for other.

Hi All, has anyone got EdXposed working?
I've installed magisk 21.1, riru core 21.3 , and riru YAHFA 0.4.6.4 EdXposed manager shows framework not active :/

Does mobile hotspot work?
I've been looking for a ROM that has kept the Samsung gallery and camera so I want to try this ROM. but I need to be able to use mobile hotspot so please let me know if it works fine. Thx

Hello, the ROM works great. There are some minor things. Like always on display does not work with option to tap the screen to show for 10 seconds. Also for some reason I can't instal Revolut from the play store. And lastly Titanium backup does not restore all the apps. I could not figure out a way how to make that work.

The hotspot works fine on mine.
I had the same issue with Titanium backup.
In the end I used split screen and installed each app from the play store, then restored data only.
Has anyone got xposed working?

Gapps
Do I need to flash gapps or is it included?
I'm currently using lineage is 16 with gapps. Do I need to flash gapps again if flashing a ROM again? Sorry I'm a newbie.

Wara35 said:
Do I need to flash gapps or is it included?
I'm currently using lineage is 16 with gapps. Do I need to flash gapps again if flashing a ROM again? Sorry I'm a newbie.
Click to expand...
Click to collapse
No gapps needed.
---------- Post added at 03:59 PM ---------- Previous post was at 03:52 PM ----------
@Skulldron, thanks for the ROM, works great and it's stable. Just few things. Could you please update the Adaway app? There is a newer stable version on xda available. I tried to update it myself but it was not possible. Also could you please fix the Always on display function? The tap on screen option does not work.

Blato said:
Hello, the ROM works great. There are some minor things. Like always on display does not work with option to tap the screen to show for 10 seconds. Also for some reason I can't instal Revolut from the play store. And lastly Titanium backup does not restore all the apps. I could not figure out a way how to make that work.
Click to expand...
Click to collapse
As I experienced from other ROM that based on Note FE base, the Galaxy S7 cant show AOD with tap to show mode due to hardware problem, so please choose always show option on the setting

Flashing a different rom, I do like this rom but need xposed and it's annoying that YouTube and adaway are system apps.

6sicSIX said:
Flashing a different rom, I do like this rom but need xposed and it's annoying that YouTube and adaway are system apps.
Click to expand...
Click to collapse
Youtube and Adaway can be removed with System App remover or Link2sd from Play Store. Then you restart the S7 and install Adaway from github and Vanced.app

I do like this rom, espicially the first boot right after install, which was really fast, made an impression. Probably the most battery friendly and lite-weight One UI-Rom one can find. One usability problem for me was the *missing feature that increased touch sensitivity*. With my screenprotector on, I have to push harder and several times before successfully pulling down the notification bar or when writing or selecting.

Is it just me or is SmartSwitch taking a long time/not restoring messages? I get to the part when it would start restoring messages but then it just never loads.. other then that, the ROM is great!

6sicSIX said:
Hi All, has anyone got EdXposed working?
I've installed magisk 21.1, riru core 21.3 , and riru YAHFA 0.4.6.4 EdXposed manager shows framework not active :/
Click to expand...
Click to collapse
I tried many versions of modules ,but no luck .Is possible to work exposed framework?