[ROM][10.0][OneUI 2.5][G930X/G935X/N930X/N935X]FloydQ V7.0

[amap2000]

FloydQ V7.0

Floyd Q Port V7.0 For the Exynos8890​

V7.0 Release Notes :-

Its only fitting to release V7 in July isn't it. The ROM is 2 years old and still has an active following which blows my mind. id like to say thanks to all the users for your support all this time, and especially a big thanks to the testing team who stuck by me for this long.

Between my university, life and other projects, i haven't had consistent time to work on the ROM, i have updated it to the latest note 9 release (which is the last one by samsung) with May 2022 Security patch. Ive done some work on the kernel and base to remove some of the issues caused in V6, added a bunch of new fixes we gathered over time and from the note 8 Q project. and just overall tidy up the ROM, there is still some work left to do, but i dont want to delay V7 any further, if/when we do another version, it will contain more experimental fixes that didn't make it here.

I have done some changes to audio, which may be better or worse on the long run, hopefully to the better, the rom only had couple months of testing with a very small test group, so i wouldn't say its bullet proof. RAM, Camera Audio and overall stability has been worked on, and hopefully this reflects in real usage. ive only used the S7 to play a couple games and use some social media, as it is not my daily driver.

So far the black screen / alarm issue has not been commonly reported, neither did audio muting, however i cant rule out that it was fully fixed until it is tested by much more people. incase you still face these issues, open new reports on github

Overall i hope this new version works better for everyone, we reached the peak of what we can fix back in V6 and that was quite underwhelming, so hopefully with this new release Exynos8890 gets a new lease on life, atleast when it comes to OneUI

And no, i do not think we will ever see a OneUI 3 public release, it is simply too buggy to even look at.

Thanks everyone for your continuous support throughout the years.

Read this F.A.Q While the rom is Downloading.

NOTES :

- After installation, leave your phone to build and optimize caches. which can take upto 15 minutes on clean flash. your phone will be HOT at this stage. If DirtyFlashing, it can take upto 30mins

- Clean flash is always recommended to avoid issues especially with this release! if you faced weird issues/blackscreens/freezes a clean flash is recommended without smartswitch / samsungcloud restore

F.A.Q :

V7.0 Related F.A.Q :

Q : Should i use Enforcing ? What is it ? How to enable it
A :
- Selinux Enforcing can be enable by ticking ENFORCING option in AROMA installer
- Enforcing adds restrictions and does not just allow anything to access anything
- Enforcing will allow you to bypass MOST root detection and will allow many Banking apps to work again
- If you want to use ROOT + Enforcing you are likely to need Magisk Hide (magisk v23) / Denylist (V24+) to retain banking apps etc
- Selinux Enforcing is still "Testing" phase, but it should be stable for now
- Settings does not show Selinux status, to know status you can type "getenforce" in terminal emulator
- Enforcing ONLY works in the included Cronos V7.0 Kernel, and will be disabled if you change kernels

Q : Note 7 Iris ?
A :
- Iris can be registered and enabled on Note 7 However it is still experimental, and is prone to causing a random reboot every few days
- A test workaround is disabling "Screen on Iris Recognition"
- In order to have IRIS Flash light torch intensity has been disabled, instead the torch will run at max brightness always

Q : Infinity wallpapers ?
A : Infinity wallpapers were removed due to out of date S9+ Builds, as samsung no longer ships updates for it

Q : Games are Laggy/Pix-elated/Stutter/sucks/crashes
A : Open GameLauncher > Top Left menu > Game Performance > Set Game performance to "Focus on PowerSaving" : Video

Q : Phone is not charging / Discharging while charging
A : Check your battery temperature, OneUI 2 wont charge when your battery is above 42C. there is no bypass to this

Q : How to get Root ?
A : Download Magisk and follow instructions (V23.0 Is recommended if you root + easy magisk hide. rename .apk to .zip and flash via twrp if your version is old)

Q : SafetyNet ?
A : The ROM Already contains bypasses and fixes for Safetynet without the need of magisk, however if you root, you must enable HIDE to restore Hiding for many apps

The full F.A.Q Can be found here

And as always, if you appreciate what i do, leave a thanks, constructive feedback and consider a donation @ Paypal

NewsChannel : Telegram
Support Chat : Telegram
--------------------------------------------------------------
FloydQ V7.0 [LATEST]
AFH : Download
MEGA : Download
GoogleDrive : Download
P.S : if you had issues downloading from Drive, sign in and save the file to your drive. the file name will show up as Copy of Floyd*
Size : 2.53GB
MD5 : 7d34c47272c5f241f281a60dd5a215dc
SHA1 : f6736340d23e7534bb82f49eb835de1690628276
* Make sure to verify the file hash you downloaded to avoid issues such as not being able to boot / zip corrupt
Windows : VerifyHash Thanks @dave457
Android : HashChecker

Floyd 7.0 - 01.07.2022

- Fully rebuilt and rebased on N960FXXS9FVE1 May 2022 Patch
- Cumulative fixes and changes since April 2021
- Merged samsung security patches since v6
- Re-worked Audio / AudioFX System to mitigate issues
- Boost overall Audio/Bass And match it more with Pie
- Various misc fixes in the base forked from Note 8 Q project
- Performance improvment due to base changes
- Support Selinux Enforcing
- Update ALL the apps/featuers in bloat to latest Q release

Aroma
- MemorySaver/Storage booster included by default
- Update iOS Emojis to 14.6
- Include latest chinese smart manager with added features
- Add Manage App Data feature (enable/disable network per app)
- Updated Goodlock mod to 20220413
- Update AdAway to v5.12.1
- Fix BixbyRoutines FC when enabling brightness control
- Add latest SamsungDaily
- Remove Force RCS as it needs carrier and reciver support
- Remove VancedManager due it being Discontinued
- Add calculator directly in the rom
- Updated OMC packages to latest FUK1 package
- Remove S9+ Infinity Wallpaper package due to samsung stopping updates
- Add Toggle for SELinux Enforcing (Check F.A.Q for more details)

Fixes
- Fix issues with power/thermal HAL that caused lag and performance degredation
- Improve Auto brightness tables
- Fix IRIS sensor on Note 7 and make it work in secure folder and other places
- Fix note 7 lag on lock screen
- Disable Note 7 torch intensity slider to avoid FCs and workaorund it
- Fix Selfie capture with HeartRate sensor
- Support more NFC card types (Mifare plus Thanks @Pavlon333)
- Cleanup some of the broken constant logging services
- Disable High Brightness Warning
- Improve and update basic safetynet hiding without magisk
- Update Safetynet Fix to bypass recent GMS restrictions (Thanks @@AndrzejDwo and @Ivan_Meler)
- Enable back Audio encoding in Slowmotion videos
- Remove problematic RAM configs
- add 2x zoom button in camera
- More improvments to RAM/ZRAM
- Fix wakeup freezes
- Fix Alarm issues
- More test fixes for Audio muting issue
- Improve Audio Quality / bass a bit
- Set Actual device name instead of note 9 by default
- Remove old deperecated props
- Various other misc changes in the ROM/Base
- Workaround initial FDSAN Error that causes issues
- Prevent Notes APP from updating on N7FE (to fix pen issue)</*)

CronosKernel
- CronosKernel V7.0
- Re-enable wakeups by eventpoll
- Revert problematic I2C stall fixes
- Revert CPUFreq relation back to stock
- Enable back HMP Boosting on GPU to avoid wakeup issues
- Restore default DVFS CPU Behaviour
- Add custom tune build flag
- Optimze the kernel for performance instead of size
- Revert power-queue changes
- Revert GPU MIF clock back to stock
- Revert CPU Boost freq back to stock
- Merge updates for I2C From Exynos7870
- Restore N7FE Camera/Iris code
- Misc sound-core driver changes from Exynos7870
- Enable CIFS Driver
- Disable Forced Permissive
- Enable back Audit logging
- Increase default audio in moro_sound
- Set Torch brightness to max on Note7 due to lack of slider
- fix pm_qos kernel panic in camera driver

ghi chú ứng dụng bị lỗi. xin lưu ý. cảm tạ.

ghi chú ứng dụng bị lỗi. xin lưu ý. cảm tạ.

My device installed very easy. Thanks for rom by admin Ananjaser1211

 

[amap2000]

My device installed very easy. Thanks for rom by admin Ananjaser1211

 

[hongthien68]

[ATTACH = full] 5650883 [/ ATTACH]

có thể bạn sử dụng s7? Tôi đang sử dụng note 7fe

Mod translation via GT: maybe you use s7? I am using note 7fe

 

[Badger50]

@hongthien68

Greetings. As a "one time" courtesy, I have translated your last three posts. Please check your browser settings, and be respectful and observant
of XDA Rule #4 for all of your future posts.

Spoiler: XDA Rule #4

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

Your cooperation is much appreciated. Thank you.

-Regards: Badger50

 

[nil2009]

Hello developer! Many thanks for your great support!
I can't install rom v7.0 on my Galaxy S7 (SM-G930K) Korea varian
When I choose to install zip in recovery show an error, AROMA installer not starting and can't installing the rom and I tried install the rom v6.0 is normal and does't show the error as above
Please help guide me to fix the problem

 

[kdcv781]

My device cannot set up fingerprint security. I don't use SELinux, and my device is S7e. I flashed the hotfix but no change. Looking forward to your help!
Thanks @ananjaser1211 for your rom.

 

[amap2000]

My device cannot set up fingerprint security. I don't use SELinux, and my device is S7e. I flashed the hotfix but no change. Looking forward to your help!
Thanks @ananjaser1211 for your rom.
View attachment 5650977

My s7edge finger is fine.

 

[kdcv781]

My s7edge finger is fine.View attachment 5650981

Thanks @amap2000 for the response!
How did you install in the AROMA installer? Please let me know!
I also formatted the data in TWRP.

 

[mechul-1]

Floyd V7.0 Critical Hotfix

This is a pretty important hotfix, as to avoid reuploading the entire ROM for 700kbs, download this patch and flash it via TWRP.
This is required mainly if you use SElinux enforcing, however some users reported issues while permissive aswell. This fixes the following :

1) An issue that prevented lockscreen from being set
2) An issue that prevented the phone from switching to permissive when enforcing is not enabled
3) Patches various Selinux denials that users reported in logs
4) some fixes for Storage denials

This will fix the first 3 issues, however if you are one of the users who had issues relating to internal storage (Unable to take screenshot due to policy, unable to write data to internal or sdcard) then this fix is not likely to help much, you will have to reinstall the ROM and NOT select enforcing (so the ROM is permissive)

I dont know why it happens yet, when it is figured out hotfix2 will be released.

If anyone complains about the issues listed above please guide them to this post.

Download : GDrive | Mirror

Now OK...

 

[ananjaser1211]

Hello.
Excellent and good.
It runs at a great speed and more smoothly.
But fingerprint still doesn't work in some programs and the island program is out of order.
It was checked with test DPC program, the problem is with the user profile.
It would be great to solve this problem.
Many thanks to you and your team.
Thank You

Thank you for the report, ive justed tested island and indeed it does not work, this is related to WorkProfile, i might need to update the patch we used, i will look into it and include a fix in the next patch once we get enough bugs reported.

Please follow this https://github.com/ananjaser1211/FloydQ_Reports/issues/83 report, i will update the status of the bug there.

có thể bạn sử dụng s7? Tôi đang sử dụng note 7fe

Mod translation via GT: maybe you use s7? I am using note 7fe

Note 7 comes included with a custom Notes APK, you dont need to install an app from the play store. if it is crashing please take a logcat and open a github page about it.

Things you can try is long press notes icon > about > allow permissions for the app.

alternatively, you can go to twrp > mount > tick system > go back > advanced > file manager

navigate to `/system/system/app/Notes` and press on Notes.apk and press delete. if you have root you can also do this using root explorer or fx explorer

Then reboot to rom, download THIS EXACT VERSION https://www.apkmirror.com/apk/samsu...samsung-notes-4-1-04-11-android-apk-download/

and it will install fine, do not install from playstore, and do not update notes app, otherwise when you use PEN it will FC

But i would appreciate if you can take a log of the crash you have before replacing the app, because none of my note 7 testers have this bug.

My device cannot set up fingerprint security. I don't use SELinux, and my device is S7e. I flashed the hotfix but no change. Looking forward to your help!
Thanks @ananjaser1211 for your rom.

View attachment 5650977

This might be a sensor calibration issue, i know some users had no fingerprint on Blackdiamond pie and floyd Q, even though the sensor itself was working fine, we never figured out why that was the case.
between Floyd V1 and V7 the fingerprint drivers were not changed.

The only thing that comes in mind would be that it is an older FP revision that only works on stock fingerprint driver, which we cant use on Pie or Q , we use a more recent FP driver (which causes the FP bug in 3rd party banking apps)

so i think it will only work if i some how manage to fix 3rd party FP and bring back the stock fingerprint driver.

This ofcourse assumes FP works fine on stock, and its not dirty / broken

 

[4550286]

after first restart phone
UI very lag and slow
animation scale working 5 fps very lag
i reflash this ROM but after first restart or turn off phone and turn on
interface UI lag

 

[hongthien68]

Thank you for the report, ive justed tested island and indeed it does not work, this is related to WorkProfile, i might need to update the patch we used, i will look into it and include a fix in the next patch once we get enough bugs reported.

Please follow this https://github.com/ananjaser1211/FloydQ_Reports/issues/83 report, i will update the status of the bug there.

Note 7 comes included with a custom Notes APK, you dont need to install an app from the play store. if it is crashing please take a logcat and open a github page about it.

Things you can try is long press notes icon > about > allow permissions for the app.

alternatively, you can go to twrp > mount > tick system > go back > advanced > file manager

navigate to `/system/system/app/Notes` and press on Notes.apk and press delete. if you have root you can also do this using root explorer or fx explorer

Then reboot to rom, download THIS EXACT VERSION https://www.apkmirror.com/apk/samsu...samsung-notes-4-1-04-11-android-apk-download/

and it will install fine, do not install from playstore, and do not update notes app, otherwise when you use PEN it will FC

But i would appreciate if you can take a log of the crash you have before replacing the app, because none of my note 7 testers have this bug.

This might be a sensor calibration issue, i know some users had no fingerprint on Blackdiamond pie and floyd Q, even though the sensor itself was working fine, we never figured out why that was the case.
between Floyd V1 and V7 the fingerprint drivers were not changed.

The only thing that comes in mind would be that it is an older FP revision that only works on stock fingerprint driver, which we cant use on Pie or Q , we use a more recent FP driver (which causes the FP bug in 3rd party banking apps)

so i think it will only work if i some how manage to fix 3rd party FP and bring back the stock fingerprint driver.

This ofcourse assumes FP works fine on stock, and its not dirty / broken

thank you very much. i followed the instructions by going to twrp... and it worked. again thank you very much!

 

[hongthien68]

@hongthien68

Greetings. As a "one time" courtesy, I have translated your last three posts. Please check your browser settings, and be respectful and observant
of XDA Rule #4 for all of your future posts.

Spoiler: XDA Rule #4

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

Your cooperation is much appreciated. Thank you.

-Regards: Badger50

Thank you for the reminder. maybe because of the browser it wasn't right when i wrote the post. I will be more careful. thank you!

 

[kdcv781]

This might be a sensor calibration issue, i know some users had no fingerprint on Blackdiamond pie and floyd Q, even though the sensor itself was working fine, we never figured out why that was the case.
between Floyd V1 and V7 the fingerprint drivers were not changed.

The only thing that comes in mind would be that it is an older FP revision that only works on stock fingerprint driver, which we cant use on Pie or Q , we use a more recent FP driver (which causes the FP bug in 3rd party banking apps)

so i think it will only work if i some how manage to fix 3rd party FP and bring back the stock fingerprint driver.

This ofcourse assumes FP works fine on stock, and its not dirty / broken

Is there any way I can fix it? On version V6, my fingerprint security still works fine when I restore from backup. Thanks

 

[bendybruce]

Just want to mention a very minor bug I have noticed, in case you get a chance to address it with your upcoming V7 release.
The Force Dark Mode option in the Developer Menu does not retain its setting and always reverts back to an off state, after rebooting the phone. Edit: Sorry I'm an idiot I did not realise it was already out. Have just downloaded

 

[Wojtek240]

I did a dirty flash from v6(1year old install), only wiped dalvik then flashed the patch, magisk, and moro 8.8.1 - everything works perfectly.

That includes: Googlepay, fingerprint, camera, rom control with mtweaks and root.

Thanks! @ananjaser1211

 

[bendybruce]

I did a dirty flash from v6(1year old install), only wiped dalvik then flashed the patch, magisk, and moro 8.8.1 - everything works perfectly.

That includes: Googlepay, fingerprint, camera, rom control with mtweaks and root.

Thanks! @ananjaser1211

This is very useful to know. I am hesitating to do the install, mainly because I have the SecureID App installed, with offers two factor authentication for logging into my works network.
Because of that App, restoring from Backup, if for some reason the install did not work, is a last resort for me, as I have to at least suspect it will break the App. Otherwise, anyone could just take a full backup of your phone, install it on another S7 Edge, and duplicate the SecureID code generator. I would be amazed if it did not have a method to detect and stop that from happening.

The other thing I'm a bit worried about, is honestly I cannot remember exactly what install options I did and did not choose when I installed V6. If I make some different decisions, could that mess things up? I'm assuming my existing Data config is fitted to match with the exact configuration I went with the first time. Sorry if this is a dumb question. That said, I was following along with a Youtube video guide when I set it up originally, and pretty much copied his options, so I can probably find that video again.

 

[ananjaser1211]

Is there any way I can fix it? On version V6, my fingerprint security still works fine when I restore from backup. Thanks

If you installed the ROM with enforce option enabled in the installer, i would say try to reinstall the rom (skipping data wipe) and not selecting enforce, let me know if it gives different results (make sure you have V7 and the hotfix flashed ofcourse)

Just want to mention a very minor bug I have noticed, in case you get a chance to address it with your upcoming V7 release.
The Force Dark Mode option in the Developer Menu does not retain its setting and always reverts back to an off state, after rebooting the phone. Edit: Sorry I'm an idiot I did not realise it was already out. Have just downloaded

Regarding Force dark mode (and many other developer options in samsung ROMs) they just dont stick, they get reset, i face the same issue on my other phones running stock oneui, there might be a magisk module or something that makes it persist on oneui roms, but i wouldn't know much about it.

under android 10, most apps should just respect normal settings dark mode, but i am aware some dont, sadly i dont have solutions for such issues

This is very useful to know. I am hesitating to do the install, mainly because I have the SecureID App installed, with offers two factor authentication for logging into my works network.
Because of that App, restoring from Backup, if for some reason the install did not work, is a last resort for me, as I have to at least suspect it will break the App. Otherwise, anyone could just take a full backup of your phone, install it on another S7 Edge, and duplicate the SecureID code generator. I would be amazed if it did not have a method to detect and stop that from happening.

The other thing I'm a bit worried about, is honestly I cannot remember exactly what install options I did and did not choose when I installed V6. If I make some different decisions, could that mess things up? I'm assuming my existing Data config is fitted to match with the exact configuration I went with the first time. Sorry if this is a dumb question. That said, I was following along with a Youtube video guide when I set it up originally, and pretty much copied his options, so I can probably find that video again.

Regarding re-installing the ROM, you can pick whatever options you want, it wouldn't affect existing installation, only time it would is for example unselecting apps like bixby, were you would need to manually uninstall it from the app menu otherwise it would not work. the rest should be fine.

Now, since you are most likely dirty flashing to V7 (installing without wiping data), you would install the ROM + hotfix1 (linked in the same section V7 can be found in) i would highly recommend NOT selecting the "Enforce" option in the installer. i have been getting many reports that dirty flashing the ROM with enforcing causes a myriad of weird issues.

Also id like to mention, if your SecureID application requires a seperate container to run (Such as WorkProfile or Knox WorkProfile mode) do not upgrade to V7.0 as this currenty is broken in it for whatever reason.

edit : i have installed the secureID app from playstore (with the cloud and checkmark icon) and it did not spawn a work profile instance. however i did not enroll any services into it as i have none

otherwise, it should be fine to upgrade.

usually you would backup the data partition in TWRP to retain applications like this, however i doubt that a secure application would just fly being restored, as these apps use certain hashes that might get corrupt after a data restore (an example would be samsung account, if you restore a twrp backup you will have to re-sign in)

So there is risk involved, i made it so when upgrading the ROM, it would perform like an "official" samsung OTA update, and run the required optimizations and whatever (System is updating pop-up in the notification panel). your app should survive that. but i cant give you 100% guarantee that it will as i have not used the app personally.

i can however say that the chance of the app failing after an update is slim, but not none (this assumes your app just gets installed to your normal launcher, and does not enable knox profile, knox profile shows up as a second tab in your app drawer on the top of the screen)

 

[bendybruce]

If you installed the ROM with enforce option enabled in the installer, i would say try to reinstall the rom (skipping data wipe) and not selecting enforce, let me know if it gives different results (make sure you have V7 and the hotfix flashed ofcourse)

Regarding Force dark mode (and many other developer options in samsung ROMs) they just dont stick, they get reset, i face the same issue on my other phones running stock oneui, there might be a magisk module or something that makes it persist on oneui roms, but i wouldn't know much about it.

under android 10, most apps should just respect normal settings dark mode, but i am aware some dont, sadly i dont have solutions for such issues

Regarding re-installing the ROM, you can pick whatever options you want, it wouldn't affect existing installation, only time it would is for example unselecting apps like bixby, were you would need to manually uninstall it from the app menu otherwise it would not work. the rest should be fine.

Now, since you are most likely dirty flashing to V7 (installing without wiping data), you would install the ROM + hotfix1 (linked in the same section V7 can be found in) i would highly recommend NOT selecting the "Enforce" option in the installer. i have been getting many reports that dirty flashing the ROM with enforcing causes a myriad of weird issues.

Also id like to mention, if your SecureID application requires a seperate container to run (Such as WorkProfile or Knox WorkProfile mode) do not upgrade to V7.0 as this currenty is broken in it for whatever reason.

edit : i have installed the secureID app from playstore (with the cloud and checkmark icon) and it did not spawn a work profile instance. however i did not enroll any services into it as i have none

otherwise, it should be fine to upgrade.

usually you would backup the data partition in TWRP to retain applications like this, however i doubt that a secure application would just fly being restored, as these apps use certain hashes that might get corrupt after a data restore (an example would be samsung account, if you restore a twrp backup you will have to re-sign in)

So there is risk involved, i made it so when upgrading the ROM, it would perform like an "official" samsung OTA update, and run the required optimizations and whatever (System is updating pop-up in the notification panel). your app should survive that. but i cant give you 100% guarantee that it will as i have not used the app personally.

i can however say that the chance of the app failing after an update is slim, but not none (this assumes your app just gets installed to your normal launcher, and does not enable knox profile, knox profile shows up as a second tab in your app drawer on the top of the screen)

Just did the install (including hotfix) and everything is working GREAT (happy dance)

The only issue I had was I lost my precious on screen nav bar, but not a problem, I just went back and used TWRP to recopy the apk file to system/vendor/overlay with the chmod775 and boom, she was back.

Since I had a bit more of a clue what I was selecting this time I was a bit smarter with some of my item choices, and am very happy with how it is set up. ps. I should mention we have voLTE here in NZ and as far as I can see, it seems to be working which is a nice bonus to get with your ROM, From what I have heard, most custom roms don't support it.

Anyway, I just want to thank you again for creating this fantastic product, I am sure it was a labour of love and I hope you gain a lot of satisfaction in knowing that plenty of people have chosen it as their daily driver. I recently chucked in a 128 gig SD card and I think I will be sticking with this phone setup for quite some time to come.

ps. to answer your actual questions, yes, it was a dirty install, and yes, SecueID was still working fine afterwards.

 

[Thugscub]

Thank you very very much Annanjasur. Rom works perfectly.
People read the installation instructions.
It will prevent a lot of bugs.
Thanks once again Annanjasur.