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

[Rolf850]

Whenever I reset the phone, the order of the notifications buttons are reset to default, it's a little annoying whenever I restart the phone having to accommodate the buttons as I like

Another small problem is that sometimes when I restart the phone, it works with quite a bit of lag and I have to restart it again for it to work smoothly

But other than that the ROM works perfect, good job! If anyone knows how to fix those little bugs, I'd appreciate it

And sorry if my english is bad

 

[Shazilsonu]

Aaahhhhhh..
Waiting For Android R With One Ui 3.0

 

[bigd4ve]

Whenever I reset the phone, the order of the notifications buttons are reset to default, it's a little annoying whenever I restart the phone having to accommodate the buttons as I like

Another small problem is that sometimes when I restart the phone, it works with quite a bit of lag and I have to restart it again for it to work smoothly

But other than that the ROM works perfect, good job! If anyone knows how to fix those little bugs, I'd appreciate it

And sorry if my english is bad

Apparently that happens if you select extra toggles in aroma when installing. I've avoided choosing that option and never had the issue. Dirty flashing without that option should hopefully fix it.

I experience lag every now and again but just restart like you. Not sure there is a solution to that but maybe what we're experiencing is different as I can't say I notice it particularly after rebooting.

 

[bigd4ve]

Hi again, thought I'd 'bump' this as I feel there is an answer but I don't know it. I tried accessing the root folder by using adb toolkit but that didn't accept the phone - came up as 'unauthorised'. I thought there would be a couple of files I could delete in the phone's system folder if I could access it but can't find any way of doing this either. Thanks

Have you tried flashing the Magisk uninstaller ZIP? I think using the native uninstall option from Magisk manager should also work but maybe it missed something. Can always clean flash the ROM to start again.

I've always managed to hide root from my banking apps by hiding Magisk manager and then using MagiskHide to hide the apps. YMMV but I'd make sure you've tried that if you want to stay rooted.

 

[Noctifers]

Hi! First time posting on this thread, so first of all - great job and thanks to ananjaser1211 and other developers and testers!
Been using v4 and v5 on two separate S7 Flat phones for several days (v4 for about 2 weeks), installed after a full wipe, having the latest bootloader and modem (U8ETI2), rooted with Magisk, no fatal crashes nor freezing, running smoothly for everyday tasks. Yet few bugs are bothering:

1. WiFi disconnects randomly while still seeing networks (seems like v4 is having it less often now - could it go away in time?), only turning WiFi off and on lets me to connect to any network again. The worst thing about this is shortly after lost connection phone starts draining battery rapidly, even if mobile data is still active, stops when WiFi is restarted.
2. Mismatching battery percentage seems to be worse in v5. On v4 phone, after charging it to 100% once while off, it has been showing correct values for a week now (within 1%), while v5 mismatches every single time. Whats even more strange, v5 does not keep track of percentage while being off too: maybe people can verify it by charging it for some time while off, then unplugging the charger, when the screen goes dark, connect the charger back - my phone shows lower percentage straight away. And it always repeats up until 95%, when it quickly goes to 100%, stops charging, and I need to unplug it, plug back in to see 96%, which quickly goes to 100%, but after replugging shows 97% and so on by 1%.
3. Somehow the UI seems to be snappier on v4, fewer app crashes, also v5 sometimes opens background app by itself or closes quick response window while typing. But this claim is a bit too random to reproduce, more like a subjective observation.

Have not observed audio problems, maybe I am not using apps which trigger that.

To update my previous observations:
(1) I was "lucky" enough to get WiFi disconnection during a night on v5, it ate most of the charge and AccuBattery showed 180 mA consumption. I know the number is heavily averaged and not all night was in this state, but still its huge for 'sleeping' s7 with AOD and mobile data off, when it should be around 20 mA or 40 mA when AOD is on. DeviceCare does not show which app is to blame, just a rapid discharge curve. As the effect was observed on 2 different phones and both v4 and v5, I wonder why nobody else has mentioned significant background battery drainage during WiFi crashes.

(2) Turns out the strange charging behavior starting from 95% for turned off phone is similar for v4 too - the percentage difference between turned on and off state is noticeable at those numbers. While v5 almost always has difference about 6-15%, v4 has been staying within 1-2% after the initial turned-off full charge (excluding 95% and up).

Sadly lost audio bug has appeared few times, once for the alarm clock, then for a call, both time smart watch helped me out. Interestingly enough, even without the sound there were no problems with earpiece during that phone call.
Still no echo in phone calls (received or made ones) with a speaker.

As the battery percentage mismatch and stability seems to be a bit better in v4 with OneUI 2.1, maybe it would be easier to fix those bugs in this slightly older version before proceeding to newer and possible less compatible OneUI 2.5?

 

[ananjaser1211]

To update my previous observations:
(1) I was "lucky" enough to get WiFi disconnection during a night on v5, it ate most of the charge and AccuBattery showed 180 mA consumption. I know the number is heavily averaged and not all night was in this state, but still its huge for 'sleeping' s7 with AOD and mobile data off, when it should be around 20 mA or 40 mA when AOD is on. DeviceCare does not show which app is to blame, just a rapid discharge curve. As the effect was observed on 2 different phones and both v4 and v5, I wonder why nobody else has mentioned significant background battery drainage during WiFi crashes.

(2) Turns out the strange charging behavior starting from 95% for turned off phone is similar for v4 too - the percentage difference between turned on and off state is noticeable at those numbers. While v5 almost always has difference about 6-15%, v4 has been staying within 1-2% after the initial turned-off full charge (excluding 95% and up).

As the battery percentage mismatch and stability seems to be a bit better in v4 with OneUI 2.1, maybe it would be easier to fix those bugs in this slightly older version before proceeding to newer and possible less compatible OneUI 2.5?

1) Battery overnight will discharge ALOT if you had the wifi issue, because the phone keeps looping the wifihal, on my wifi chip i dont face it, my overnight drain is few % on average. it gets worse the more social apps i add ofcourse. not many people looked into wifi crash to notice the drain if i have to guess, but yes it is 100% there based on old wifi crash logs ive seen.

2) the 2.1 or 2.5 does not matter with this mismatch, i had constant 1-2% mismatch on all versions since V1, higher mismatch happens randomly, hence why we still could not pin point this bug. some different measuring algorithm is causing issues in the health HAL if i have to guess, but not something i can fix yet.
the only time i had significant mismatch (8%) i got it down to 1/2% by just recharging my phone while its powered off for few cycles, that always got it down for me, if it helps

3) i dont know really, these bugs are common across all versions, they are not specific to any, but i prefer the 2.5 update because it fixed a much nastier issue which is overnight crashing (where the phone will just freeze and die overnight). this has never happened in V5 yet. the rest of the bugs are "common" whether we are on 2.0 2.1 or 2.5, they will be there until we find a fix

i rebase and update the version / security patch because it takes less than 30 minutes of work, finding and debugging these bugs on the other hand is what makes each release take over a month or so, especially due to lack of logging for the wifi crash , muting etc, issues i cant recreate on my device.

regarding to battery percantage.
I have found battery issue also persist in other rooms, such as nfe ported pie roms. when you go to the twrp they also have different battery percentages. this rom somehow reads battery percentage from root file and shows same percentage with twrp.

TWRP will always have a mismatch, this is since the galaxy S6, the mismatch bug we face in Q is the offline charging mismatch (when the phone is powered off and shows the charging animation) and that one actually causes issues, TWRP mismatch is fine and can be ignored, offline mismatch however no

------------------------------------------------------------------------------------------------------------------------------------------------------

For the charging mismatch i am almost 100% certain it is something wrong in the ramdisk, since Q has moved it to vendor, and ditched all device-specific / samsung-specific nodes from init.rc , we lack a ton, ive added most of them in V5 which may be the reason why the overnight crash was gone, but we still have more to go to figure out why 2 charging scenarios show up with different percentages,

for those that have significant gap (and i mean atleast 5% difference) it would help if you can send me your dmesg by following the logging kit, and then power off your phone, let it show offline charging, then hold the recovery combo and send me log_kmsg also via the logging kit.

this might give us some tips on what is being read

 

[Redscorpian]

Have you tried flashing the Magisk uninstaller ZIP? I think using the native uninstall option from Magisk manager should also work but maybe it missed something. Can always clean flash the ROM to start again.

I've always managed to hide root from my banking apps by hiding Magisk manager and then using MagiskHide to hide the apps. YMMV but I'd make sure you've tried that if you want to stay rooted.

Thanks and tried that but still have the same banking apps saying they won't work with 'rooted' phones etc. I don't mind if I have to unroot or flash this/another ROM but would rather not. I have just uninstalled and reinstalled Magisk and associated apps to find I now have proper root access and have installed Titanium Backup Pro again so now have a full backup to make any changes easier to recover from, hopefully! But having done this, like I said, some banking apps not cooperating. Any more ideas? I don't mind if I have to 'unroot' my phone as there aren't many other things I'm bothered about now. Thank you.

 

[aegidios2]

Hi,

Very good rom, I've wiped everything and format data (by enter "yes" in twrp) and I dont have any echo problem, (I've not installed dual speaker..) , and perfs are awesome, very pleased to see the same thing that new flagship on my old S7 !!! so nice !!!
The only problems that I've found is , one with my Led cover wich is not fully supported at this time and, most annoying, pictures are impossible to add to a mms after one or two times, need to reboot phone to send them again ... is anyone facing the same issue ?
Exepts those points , perfect work , and many thanks !!!

 

[fun4357]

Aaahhhhhh..
Waiting For Android R With One Ui 3.0

Pro Tip: You can get it faster if you sponsor Anan an S20

 

[Marsu42]

With this a10 works UniXcam_v1.2beta_FIXED-HDR.apk. I downloaded it from telegram.

I've downloaded the one Floyd posted on Faq section. It worked. Thank you very much. A perfect rom!

EDIT: Sorry, found it it's the F.A.Q. and not the Faq, that's why it didn't turn up in the search.

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

Welcome to Floyd Q Port For the Exynos8890 Series Some information you should know.. This is a full Galaxy Note9 port with Android version 10.0 / Oneui 2.5 This ROM is made with heavy collaboration from @corsicanu make sure to give him coffee...

forum.xda-developers.com

 

[joam280]

[QUOTE = "fun4357, publicación: 84068253, miembro: 7229875"]
Consejo profesional: puede obtenerlo más rápido si patrocina a Anan un S20
[/CITAR]
sit would be great to see it on our galaxy s7

 

[Marsu42]

ensure you are running recent oreo bootloader and modem!

I'm stuck at this step - how do I check that I've got the 'latest' one?

Currently, I'm running Lineage Pie, but want to migrate because of the echo bug that's only solved in stock roms.

 

[dolf123]

adaway is not working on floyd 5 : no su binary or root..

Have both..

Whats the problem here?

 

[dolf123]

adaway is not working on floyd 5 : no su binary or root..

Have both..

Whats the problem here?

Solved...installed Rom 5 once more

 

[bigd4ve]

Thanks and tried that but still have the same banking apps saying they won't work with 'rooted' phones etc. I don't mind if I have to unroot or flash this/another ROM but would rather not. I have just uninstalled and reinstalled Magisk and associated apps to find I now have proper root access and have installed Titanium Backup Pro again so now have a full backup to make any changes easier to recover from, hopefully! But having done this, like I said, some banking apps not cooperating. Any more ideas? I don't mind if I have to 'unroot' my phone as there aren't many other things I'm bothered about now. Thank you.

If you've done Magisk Manager Settings > Hide Magisk Manager and then afterwards MagiskHide and selected your banking apps, then I'm not sure what else you can do to hide root. If you opened your banking apps before hiding root then maybe they can remember that status somehow.

If you try hiding on a clean install before opening the apps, that will confirm/reject it as a possibility. If none of that works and you won't miss root access then you should be fine on a clean install with no Magisk.

 

[Noctifers]

Thanks and tried that but still have the same banking apps saying they won't work with 'rooted' phones etc. I don't mind if I have to unroot or flash this/another ROM but would rather not. I have just uninstalled and reinstalled Magisk and associated apps to find I now have proper root access and have installed Titanium Backup Pro again so now have a full backup to make any changes easier to recover from, hopefully! But having done this, like I said, some banking apps not cooperating. Any more ideas? I don't mind if I have to 'unroot' my phone as there aren't many other things I'm bothered about now. Thank you.

As it was said before, you need to use Hide Magisk Manager, it will reinstall the app with different name and a default icon. Note, this option is only available if you have network connection. Just choose some random name, not Magisk, Manager or Root. Afterwards add Google Play services and framework to MagiskHide, then clear their cache (you can force-stop them before doing that, just to be sure), also clear the cache or even the whole data for banking apps after adding them to MagiskHide. Note, some root modules can trip the SafetyNet or even make apps suspicious without tripping the root, for example, edExposed module. So far I am using root and even edExposed (XPrivacyLua) with banking apps without problems. Samsung Pay wont work, though, and PayPal wont be able to register fingerprint, but those are common problems for all custom ROMs.

 

[manelito20]

hey.
im loving this rom, but the games are too laggy.
even with all i read with game booster/launcher

´´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 ´´

no sucess for me. games always laggind with frames out.

thanks for your great Work.

 

[riojosepha]

hey.
im loving this rom, but the games are too laggy.
even with all i read with game booster/launcher

´´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 ´´

no sucess for me. games always laggind with frames out.

thanks for your great Work.

Can I ask which games you are trying to play? Try uninstalling updates for game booster & game optimizing service.
Apps > Show system apps > Game Booster/Game Optimizing Service > App Info > Three dots > Uninstall updates.

 

[Tae-il]

I have got to say this rom is amazing. I can't believe how much work has been put into this rom. Kudos. I'm running v.5 clean flash and all problems ice had before like the random restarts not charging having to use Ambient display so the phone doesn't seize up requiring a force restart. The only problem I've got is the downgraded camera quality and the speaker at times is a bit quiet. Can't wait for a 3.0 port.

 

[Noctifers]

1) Battery overnight will discharge ALOT if you had the wifi issue, because the phone keeps looping the wifihal, on my wifi chip i dont face it, my overnight drain is few % on average. it gets worse the more social apps i add ofcourse. not many people looked into wifi crash to notice the drain if i have to guess, but yes it is 100% there based on old wifi crash logs ive seen.

2) the 2.1 or 2.5 does not matter with this mismatch, i had constant 1-2% mismatch on all versions since V1, higher mismatch happens randomly, hence why we still could not pin point this bug. some different measuring algorithm is causing issues in the health HAL if i have to guess, but not something i can fix yet.
the only time i had significant mismatch (8%) i got it down to 1/2% by just recharging my phone while its powered off for few cycles, that always got it down for me, if it helps

3) i dont know really, these bugs are common across all versions, they are not specific to any, but i prefer the 2.5 update because it fixed a much nastier issue which is overnight crashing (where the phone will just freeze and die overnight). this has never happened in V5 yet. the rest of the bugs are "common" whether we are on 2.0 2.1 or 2.5, they will be there until we find a fix

i rebase and update the version / security patch because it takes less than 30 minutes of work, finding and debugging these bugs on the other hand is what makes each release take over a month or so, especially due to lack of logging for the wifi crash , muting etc, issues i cant recreate on my device.

But how come it discharges more on some phones? The attached screenshot shows DeviceCare window of a time the WiFi crash happened during a night after unplugging the charger, at around 1am on the graph. I charged it in the morning while switched off, then decided to check if it will act the same if I leave WiFi on, but change password of the router, so Android cannot succeed connecting to a known network. I did it at around 1pm (13 o`clock on the graph), then changed the password back to what it was around 5pm (17 on the graph) - the steepness does not change, so there is a clear difference in crashed WiFi and just 'looking for a WiFi'.
What logs would you need to see, when this repeats?

Just a thought about temporal solution while the real root is unknown: maybe a script can be started in the background, which checks if WiFi is enabled, if it is, but its disconnected, restart the WiFi, as it might have crashed. It could be run in 10min or even larger intervals, and WiFi restarting, if its disconnected, shouldn`t do any harm.

For the charging mismatch i am almost 100% certain it is something wrong in the ramdisk, since Q has moved it to vendor, and ditched all device-specific / samsung-specific nodes from init.rc , we lack a ton, ive added most of them in V5 which may be the reason why the overnight crash was gone, but we still have more to go to figure out why 2 charging scenarios show up with different percentages,

for those that have significant gap (and i mean atleast 5% difference) it would help if you can send me your dmesg by following the logging kit, and then power off your phone, let it show offline charging, then hold the recovery combo and send me log_kmsg also via the logging kit.

this might give us some tips on what is being read

I have a question about log_kmsg from recovery - adb does not see the phone to make a log, or you meant TWRP log, but its only dmesg and recover.log.


I encountered echo in Wire messenger calls, most probably it is different from normal GSM calls and implemented fixes do not work there. Also it is impossible to change volume during a call. Would you need any logs to check it out?