[ROM] BeyondROM V4.6 [6/08/2022] [FVG5] [August Patch] [G980F-G981B-G985F-G986B-G988B]

[73sydney]

View attachment 5619957
and as far as i know its the latest version here in australia i used frija tool and sammobile now looked other countrys and they have the right version to what beyond is

You can always use any other OXM ROM, like AUT for Austria as you have OXM in your CSC field (see your previous post with screenshot). I figured this out with some pointers from the nice folks here about how OXM CSC worked when i came back to Samsung this year after a few years on Pixel. I'd just bought an S20+ 5G and because Telstra and even the unbranded XSA are slow to be released here, so i used the AUT ROM for my S20+...a few months later i grabbed the XSA for Australia when it released as a backup for future clean flashes if needed.

 

[Carine&148]

Hello, is there a solution for Samsung Health? is there no longer the line where it was enough to set it to 0 for it to work?

 

[73sydney]

Hello, is there a solution for Samsung Health? is there no longer the line where it was enough to set it to 0 for it to work?

No, currently the last working version (for me at least) is 6.19.5.017

Stupid Samsung thinks blocking its usage on a rooted Samsung is somehow preventing *some unknown* mayhem from occurring, maybe committing step fraud?, when in fact its just pissing off people who buy their Watches and have a crippled experience as a result of their nonsense

When will they ever learn, people gonna root...its their right...

There is some work being done on trying to remove knox/root detection, but its slow going

 

[pintasmapila]

Well... This is a solution: https://forum.xda-developers.com/t/galaxy-wearable-app-on-rooted-phone-help.3838503/post-78024599
But it will change your device id (name, model and manufacturer). Works with Samsung Wear/Health from PlayStore.

 

[73sydney]

Well... This is a solution: https://forum.xda-developers.com/t/galaxy-wearable-app-on-rooted-phone-help.3838503/post-78024599
But it will change your device id (name, model and manufacturer). Works with Samsung Wear/Health from PlayStore.

Ive never seen that as a solution, thats just creating new issues....

also that solution is overkill, you dont need to change that many props to have that working (i did it on another device, my Pixel 2XL for my Buds+ to work from memory, misrepresenting it as a Samsung phone in the early days of the Buds- so the opposite, then found an alternate way that didnt bork my entire device by presenting it as something it wasn't) I'll see if i can find my post on which props are actually required, but it was aways back

also i would a simple standalone module just for the props...installing magiskhide props config just for that is overkill, from memory its only 2 props, not 5/6

update: i misremembered, it wasnt when i was on Pixel 2XL, it was before that..i was on a Note 4, to get the Wearables app to even run for the Buds+

where all i had to change was:

ro.product.manufacturer
ro.vendor.product.manufacturer

Galaxy Wearable App on Rooted Phone Help

Hello, I am trying to install the new Wearable app on my galaxy s9 that is running a custom rom / rooted. The app says it is not compatible due to the phone being modified in an unauthorized way. I know people got the previous wear app to work on...

forum.xda-developers.com

in that vein, ive attached a simple module to change just these props if anyone wants to play with it, if it doesnt work, uninstall the module to revert - the beauty of magisk...module name: FakeGoogleProps

the only active part of the module are the following lines in system.prop in the root module folder

ro.product.manufacturer=google
ro.vendor.product.manufacturer=google

the are no files touched, no permissions changes, nada, just those two lines

test if you like....hopefully it works for this purpose (if not, extract the module, add the additonal lines to system.prop and re-zip, and install module again (over the top is fine)), its far easier to setup (install it) than using MPHC (as much as i love that module, saved me in the past)

 

[pintasmapila]

Ive never seen that as a solution, thats just creating new issues....

also that solution is overkill, you dont need to change that many props to have that working (i did it on another device, my Pixel 2XL for my Buds+ to work from memory, misrepresenting it as a Samsung phone in the early days of the Buds- so the opposite, then found an alternate way that didnt bork my entire device by presenting it as something it wasn't) I'll see if i can find my post on which props are actually required, but it was aways back

also i would a simple standalone module just for the props...installing magiskhide props config just for that is overkill, from memory its only 2 props, not 5/6

update: i misremembered, it wasnt when i was on Pixel 2XL, it was before that..i was on a Note 4, to get the Wearables app to even run for the Buds+

where all i had to change was:

ro.product.manufacturer
ro.vendor.product.manufacturer

Galaxy Wearable App on Rooted Phone Help

Hello, I am trying to install the new Wearable app on my galaxy s9 that is running a custom rom / rooted. The app says it is not compatible due to the phone being modified in an unauthorized way. I know people got the previous wear app to work on...

forum.xda-developers.com

in that vein, ive attached a simple module to change just these props if anyone wants to play with it, if it doesnt work, uninstall the module to revert - the beauty of magisk...module name: FakeGoogleProps

the only active part of the module are the following lines in system.prop in the root module folder

ro.product.manufacturer=google
ro.vendor.product.manufacturer=google

the are no files touched, no permissions changes, nada, just those two lines

test if you like....hopefully it works for this purpose (if not, extract the module, add the additonal lines to system.prop and re-zip, and install module again (over the top is fine)), its far easier to setup (install it) than using MPHC (as much as i love that module, saved me in the past)

Fantastic! I always thought that was overkill. Thank god for Magisk modules XD.
One thing i liked about the overkill solution (not sure about your yet) is that i also got pixel weather widgets working in my current ROM, Lineage 19.1.

 

[slutman]

Hi,

I need help / advice, and since it can be Rom related (depending of model and Rom - optics/product/vendor...), I'm asking here.
If it's the wrong section, sorry in advance and plus light me up

I was trying to find a way to do 2 things :
- Enable Screenshot quick tile.
- Add an option to auto-connect data while i'm on Wifi and I receive/send a MMS.

I found how to by editing the file cscfeature.xml in /optics/configs/carriers/XEF/conf//system/
- For the first Screenshot quicktile, I added <CscFeature_SystemUI_ConfigDefQuickSettingItem> option and it worked.
- For the AutoConnect, i found <CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS> but it doesn't work.
(Firefds Kit have this option but it's not working either)

Could someone help me or give me an idea pls ?

 

[73sydney]

Fantastic! I always thought that was overkill. Thank god for Magisk modules XD.
One thing i liked about the overkill solution (not sure about your yet) is that i also got pixel weather widgets working in my current ROM, Lineage 19.1.

your mileage may vary on pixel features which *may* be dependent on model or internal model name or both(Pixel 3 and crosshatch for example respectively)..as mentioned feel free to edit and ad for testing, its a matter of unzip, edit, rezip, flash, reboot

 

[pep086]

Hi Guys how is the battery life on this rom? magisk and lsposed works fine?
thank you,
regards.

 

[73sydney]

Hi,

I need help / advice, and since it can be Rom related (depending of model and Rom - optics/product/vendor...), I'm asking here.
If it's the wrong section, sorry in advance and plus light me up

I was trying to find a way to do 2 things :
- Enable Screenshot quick tile.
- Add an option to auto-connect data while i'm on Wifi and I receive/send a MMS.

I found how to by editing the file cscfeature.xml in /optics/configs/carriers/XEF/conf//system/
- For the first Screenshot quicktile, I added <CscFeature_SystemUI_ConfigDefQuickSettingItem> option and it worked.
- For the AutoConnect, i found <CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS> but it doesn't work.
(Firefds Kit have this option but it's not working either)

Could someone help me or give me an idea pls ?

Why wouldnt you just leave mobile data enabled, and connect to wifi and txt away.... i do it day in day out on stock at least....what am i missing in your question? Help me understand what youre trying to achieve by doing this, and why....

I remember seeing this "hack/feature" back in the old days trying to be added by people who thought leaving mobile data off was a good or desirable thing, sometimes for tinfoil hat reasons (which i have zero time for)...not sure its even relevant anymore?

 

[slutman]

Why wouldnt you just leave mobile data enabled, and connect to wifi and txt away.... i do it day in day out on stock at least....what am i missing in your question? Help me understand what youre trying to achieve by doing this, and why....

I remember seeing this "hack/feature" back in the old days trying to be added by people who thought leaving mobile data off was a good or desirable thing, sometimes for tinfoil hat reasons (which i have zero time for)...not sure its even relevant anymore?

Sure, I can easily answer that

Where I leave, mobile data is really bad and I've much better WiFi.
On top of that, I now work 100% at home.

I hope it will help you understand my situation

 

[SpaceRob62]

What to do at the battery drain? Just reach half a day when lucky.

 

[Piliip]

What to do at the battery drain? Just reach half a day when lucky.

Find out what causes it, and fix it?

 

[73sydney]

Sure, I can easily answer that

Where I leave, mobile data is really bad and I've much better WiFi.
On top of that, I now work 100% at home.

I hope it will help you understand my situation

as far as im aware modern Android devices running Android 10+ use wifi when you toggle it on and connect to wifi, and intelligently switches to mobile data for MMS and then back to wifi when done.....all in the background (as long as mobile data is toggled on)

so again, why you just leave both enabled as i do every day and not worry about it?


does it not work when you leave both on?

 

[starbucks2010]

I updated the 1st post with latest patched SHealth (flash in twrp). Don't forget to uninstall any application updates (Applications - 3 dots - Uninstall updates) before flashing the patched one.

 

[pintasmapila]

I updated the 1st post with latest patched SHealth (flash in twrp). Don't forget to uninstall any application updates (Applications - 3 dots - Uninstall updates) before flashing the patched one.

Cool. Thanks buddy

 

[Benoni1]

I am absolutely connected with ROmka. I have something to add. But when I install the kernel, the camera doesn't go there. Thanks for the answers.

 

[DarkAngel217]

hey got another issue now my phone say it has 15gb of storage

 

[irnehhenri]

Does the telephoto camera work with any GCam port on this ROM? I'm wondering whether to root my S20U (G988B), since tele does not seem to work on stock OneUI 4.1...

 

[brambles1234]

I have flashed this ROM and I have been using it for a few weeks now. It is a nice ROM and functions well. The onluy issue I have is that it takes up a lot of space. The system storage takes up 16gb and the 'other' takes up 13.42gb I have moved files over to the SD but I am still getting the limited storage notification.

I must say that I wiped the internal data and started fresh when I flashed this ROM.