yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] danwood76:
I have had a quick look over your changes.

The NFC sepolicy stuff doesn't look right to me (it may work but there is probably a simpler/correct way to fix it). I am guessing that an NFC file was incorrectly labelled, what were the original denials you were getting? I could probably fix our SEPolicy properly. It may be that Jan was in permissive when he made the original commits (I have usually taken care of the SEPolicy stuff).

The "patch_tcpsockettracker-crash.patch" fudges round a kernel bug which I should really get round to fixing, I think it is only a few picks (I might take a look at it tomorrow).

BTW running "device/samsung/universal7580-common/extract-files.sh" on an S5NEO stock firmware will probably break stuff, we use the A510F nougat as the source of the common files (our kernel is also based on the A510F). Running the extract scripts from the latest LOS version should work fine but it is actually better to simply use themuppets repo as that has our 18.1 changes already.

As you gathered the call recording feature is disabled in a lot of countries due to legality. For example it is illegal in Germany, Sweden, and lots of other countries.

Also if you fix anything you can always push your changes to gerrit and we can review/merge ;)

Kind regards,

Danny
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
To me, looking at @Fincer's commits adding the SELinux rules, they seem like they've just been copied right out of a different device tree.

I'm using the new open source Samsung NFC HAL on my own LineageOS 17.1 builds. To address the SELinux denials that I got with it, I labelled its service in the sepolicy in my commit here: https://github.com/TALUAtGitHub/and...mmit/914f6ec44657732de3562fd1b259d3ad1b8fcf95 ...and so, your guess that a file, which happens to be the NFC HAL service, is incorrectly labelled is correct. Labelling it with the correct label is absolutely all that's necessary.

Speaking of NFC, I've got an issue with my S5 Neo where NFC only works with another phone that I've tested it with. It doesn't work with any of the NFC tags/cards that I've tested, and this issue exists with both the new open source NFC HAL and the old NFC HAL. I don't know if that issue exists on the stock firmware as I never tested NFC on it. Has anyone got similar issues?

On the topic of call recording, to enable it (for whichever regions it's set to be allowed in, of course), all that would be required is this change: https://github.com/TALUAtGitHub/and...mmit/11448569ef5d1358bae1e6abbfce9d37200f6887 I haven't tested it myself yet. Changes outside of device-specific trees, as have been shared for it, should always be avoided if at all possible.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] 0LDST4R:
So much technical stuff in this last posts. Very interesting for me to read all these things, and even more interesting how many people are active in development with this device. I'm just only the " typical enduser " with a fraction of all your knowledge, but i'm very happy to benefit from that.

Greetz, respect, and thanks.

_-_-_-_-_

0LDST4R

-_-_-_-_-
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Fincer:
Thanks for commenting!

I am pretty sure there's room for fixes in my SEPolicy. What comes to NFC, I haven't copied all SEPolicy rules from "other device trees", although there are some rules used from other device tree sources (I know, rules should be evaluated, simply haven't had time for that). In most NFC rules, however, I simply allowed capabilities which did not cause any avc denials in my logs. I am pretty sure my SEPolicy might be too loose and should be more restrictive, and I am grateful if anyone like to improve it. I don't have list of original denials, but the current NFC SEPolicy rule set is mostly based on those.

Running '"device/samsung/universal7580-common/extract-files.sh" has not caused any issues on my S5 Neo, well, so far.

The patch file for TCP socket tracker crashing was one I found once I analyzed my logcat output and was seeing constant messages of the tracker process crashing. I don't like unnecessary crashes.

My personal opinion for call recording is that anyone who uses patches or workarounds to enable the feature takes legal and personal responsibility of doing so, as well.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] danwood76:
That sepolicy change looks correct. Are you happy for me to cherry-pick your patch and upload to gerrit? (Or you could do that yourself?)

The moving config to vendor patch isn't quite right for us, I will do a correct version with your authorship if you are happy? (also upload to gerrit). We like to keep the config file names the same as on stock.

To test the NFC I use the android CTS verifier. You can emulate payments and all NFC functions using that.

I will also cherry-pick your call recording overlay patch, not really sure how that got dropped as I remember we had that a few years ago.

Thanks for your input.

Kind regards,

Danny
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Alright. Yes, you can upload it to gerrit. I don't know how to upload patches to gerrit yet, so it would be better for you to do it.

I've edited that commit through a rebase myself, and removed the change of the filename: https://github.com/TALUAtGitHub/and...mmit/c98d51d42c92af13bcfb8cb5157fcde077d9bdad

I see. I think the CTS tests for NFC would pass. I just have the issue that I've described on my specific S5 Neo with both the new and old NFC HAL, and it looks like no one else has any similar issues. I think something might just be wrong with the NFC coil in the battery that I'm currently using, which really needs to be replaced, anyway.

Okay. By the way, I've also edited that commit through a rebase to remove the call_recording_audio_source overlay, so that the default audio source, 1, is used. With audio source 4 which was set to be used through that overlay, call recording fails, with the following log messages from logcat:

[...]
07-15 09:48:02.103 3564 6980 E APM::AudioPolicyEngine: getDeviceForInputSource() no default device defined
07-15 09:48:02.103 3564 6980 W APM_AudioPolicyManager: getInputForAttr() could not find device for source 4
07-15 09:48:02.103 3564 6980 E AudioFlinger: createRecord() getInputForAttr return error -22
07-15 09:48:02.103 3594 5636 E IAudioFlinger: createRecord returned error -22
07-15 09:48:02.103 3594 5636 E AudioRecord: createRecord_l(0): AudioFlinger could not create record track, status: -22
07-15 09:48:02.104 3594 5636 E StagefrightRecorder: audio source is not initialized
07-15 09:48:02.104 6728 6746 E MediaRecorder: start failed: -2147483648
07-15 09:48:02.145 6728 6746 W CallRecorderService: Could not start recording
[...]

With audio source 1, it works fine.

You're welcome.
[Samsung Galaxy Note 9 Questions & Answers] trivjednom:
Hello, could anyone advise me which rom I can download and flash using odin. Which they are according to CSC.

I don't understand which I can use according to csc. Thank you in advance.

View attachment 5339955
[Samsung Galaxy Note 9 Questions & Answers] trivjednom:
I'll try to write it down more, maybe somewhere I'll be interested in helping me ... I bought a Samsung Note 9 via eBay the original owner has it from at & t ... it's a snapdragon and I live in Europe ... my European SIM card works there and actually everything works only what doesn't work are updates my last update is december and especially the security update is from december 2020 does anyone know me how to put a newer or current security patch there ...?
[Samsung Galaxy Note 9 Questions & Answers] trivjednom:
Problem solved.
[Samsung Galaxy Note 9 Questions & Answers] cirla09:
can i flash also this to sm n960j? thanks

i
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] penglezos:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

Information:

This is an OSS non-dimlayer vendor built rom.

Based on the latest Android Security Patch

Latest LineageOS changes according to the ROM date release

NFC icon on status bar (when enabled)

Burn-in icon protection

Blur toggle moved to Display section

Stability and performance improvements

Safetynet passes out of box

You can flash custom kernels but no support will be provided

Recovery and Widevine L1 persists if patched via MIUI.

Known issues:

None. You found one? Please report it here by providing a description with a log or a video if necessary.

Installation Instructions :

Assuming you have an unlocked bootloader, a recovery installed and the ROM zip:

Go to recovery (Official TWRP is recommended)

Wipe Data/Cache/System/Vendor

It is recommended to flash latest Android 11 firmware (not vendor) according to your region

Flash the ROM

Flash your favourite gapps (optional step)

Flash DFE (optional step if you are not encrypted)

Reboot

NOTE: I always recommend following these steps. Also there's no need to flash any kind of MIUI Vendor.

Downloads and Changelog:

lineage-18.1-20211019

Source Code:

https://github.com/penglezos/kernel_xiaomi_raphael
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] penglezos:
Reserved for future reference.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] mauam:
Need to change data to f2fs!? And out of curiosity, which kernel is used?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] camp70:
Wow, thanks, a must try. Are u going to keep maintenance? Is call recording and miracast working?

Edit: miracast works, call recording not
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Toni Suwanto:
It should support both ext4 and f2fs.

Could be his own kernel
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] z1022:
Is it Vanilla build ? I would like to install Vanilla build.

I never is OSS vendor built. If future upgrade from this ROM, can I dirty flash ? I use encryption.

Thanks
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] birdr:
Hi Englezos - great effort, I'm using this now. One issue - I can't answer normal phone calls. When someone calls the phone rings, but there is nothing showing that allows it to be answered?

Clean install following your instructions.

Any suggestions?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Toni Suwanto:
Check default app, could be phone not set as default
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] birdr:
Yes. This was the problem. The default app is becomes not set in the clean install + Nik gapps core. Thanks.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] kcajjones:
How is this different from the other "unofficial" lineageos 18.1 Rom?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] penglezos:
No theres no need to change data. It's Englezos kernel.

I don't like these kind of questions to be honest. But for the record I've been releasing my personal builds on my github profile since Jun 7, 2020. I will check what I can do for call recording even though I don't use it.

No gapps included. I don't really recommend dirty flashing but its up to you.

Nice to hear that you solved your problem.

Feature wise it's the same goold old LineageOS ROM. I don't like bloat I enjoy simplicity and stability. Code wise its completely different since its OSS. Try and let us know.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] z1022:
I understand from other ROM change to your ROM. I need clean flash. I mean when next update for your rom. I also need clean flash to update is better. Right ?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] kcajjones:
Thanks for the answers.

Does this rom have adaptive battery charging to restrict maximum charging percentage?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nitty202:
Official LOS builds don't have this feature...very likely that this build too will not have it
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nitty202:
Thanks for your efforts dev....does this ROM support signature spoofing ?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] camp70:
Excuse me. I didn't want to bother you, just notice that some devs share experimental builds and then stop. Thanks for check call rec, I know that Octavi Os have it working, I hope it helps.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] maxtouf:
Hello, I can't install the rom, I have the lineageos logo that appears and after 30 seconds it comes back to TWRP. I did Wipe Data/Cache/System/Vendor

Thx
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] kcajjones:
Same issue here.

Could it be because I have data and system as F2FS?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] maxtouf:
I tried in F2FS and ext4 and it's the same
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] FallenJedi:
You might need to format data to boot into OS. IF you are not particular about encryption then flash dfe and it will boot.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] FallenJedi:
You might need to format data to boot into OS. IF you are not particular about encryption then flash dfe and it will boot.

One suggestion. Please put OSS in the title since the Miui vendor based LOS is also called Unofficial Lineage OS. It would be easier for people to identify.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] penglezos:
It's already stated inside the thread.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] birdr:
After a day of use everything seems very stable - no crashes, good battery, etc.

The only issue I have found is that earpiece volume seems very low even when set to max. This is for all apps (Phone, WhatsApp, signal, etc).
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nonewithnothing:
Could you add a Quick Tile for switching mobile data SIM cards?

After using it for a few days, I didn't find any obvious problems, very smooth, battery life is also good.

I turned from another LOS rom. I used it for more than a year. From my experience, these two LOS rom both good, I am very grateful for the contribution of each own developer, I just want to use OSS. so I choose this one, I really don't like MiUi's things, even it is just vendor.

I know that developer has already released several releases on GitHub, so I think it should be the choice of my daily use, it is really good! thank you again!
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] mrmathematica:
Is there hope that we see official LOS for this device?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Morpheuspt:
I guess this build also doesn't boot for those people who replaced their screens, yes?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] harry_turtle:
Exactly the same issue here, don't want to use dfe.

Tried TWRP and Orangefox, not flashing any other zips.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] FallenJedi:
You will need to format data not wipe.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nonewithnothing:
I found a problem with the location today.

Given the application location permission, and enable the location in the system setting, but still unable to get the location. At the same time, use the GPS Test application to view GPS information, and find only one satellite and the signal is very weak. another mobile phone can search for more than 20 satellites at the same place and time, and I am sure before flash this rom, the phone can also successfully get location and search so many GPS satellite signal.

tried Google Maps, Google Earth, GPS status, GPS Test, clear cache, reboot phone a few times, or update the A-GPS data, still not work.

Very weird, can't get the location yesterday. tried any way I could know, but everything is normal today ...
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nocio:
I don't have that kind of problem on this ROM, actually I don't have any kind of problems with it.. Its almost perfect
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] :
When flashing just the ROM without Gapps, it boots for 30 seconds and then enters the recovery, whereas it boots normally with Gapps (tested with nikgapps core).

Has anyone flashed just the ROM without gapps and managed to get it working?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nonewithnothing:
Very weird, can't get the location yesterday. tried any way I could know, but everything is normal today ...
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] ugurbor:
I have been using it since yesterday and the battery life is amazing. But my only issue is that I get frequent slowdowns in applications while scrolling etc. Animations stutter. This mostly happens when I unlock and use or if stop for a moment using the phone heavily. I really don't know what I'm talking about but it seems the CPU governor is too 'conversative' with power saving. Can I change it to a more responsive one?

Edit: I tried with a kernel manager to set all governors to performance but it didn't change anything. Though, after restarting the phone, issue seems to be gone for now. Maybe it slowdowns with uptime? Or something holding good chunk of memory in the background?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nonewithnothing:
Another question, can anyone use the buttons on the Bluetooth earphone or use the Bluetooth keyboard to input on this rom?

I can’t make these operations here.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] harry_turtle:
Using OrangeFox:

Wipe: Cache, System, Vendor

Format: Data

Install lineage-18.1-20210616-UNOFFICIAL-raphael.zip

Still reboots to recovery after approximately 30 seconds of lineage logo

Edit: Same as @DontBeEvil

Flashing works only with Nikkgaps (core) it seems.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] FallenJedi:
Strange. For me it booted without any gapps. I'm unencrypted though.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] suisujin2:
Same here. Had to flash with NikGApps (basic). My phone is encrypted.

So far everything works fine. No problems with Magisk and ANXCamera. Only opening the app drawer and swiping slowly through the homescreens seems a bit choppy. Now it's smooth.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] birdr:
After over a week of use this rom has proven very stable.

However, I am still experiencing very very low earpiece volume. This was not the case on previous roms. Further, it is commented that transmitted voice often becomes robotic.

I've tried various firmware, including the latest global android 11 V12.5.1.0.RFKMIXM.

Mine was a clean flash, with full wipe and format, with nikapps core.

Does anyone else have this problem? And solution? If not, perhaps someone could comment if they did something different so I can try to remove the problem? Thx.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] suisujin2:
I don't experience these issues. The volume is pretty loud. I think I also have the newest firmware and didn't do something special besides flashing the rom with the NikGApps.

Here are my findings after 2 days of use:

Battery life is like EvolutionX (where I come from). Roughly 2 days max. with >6 hours display on time.

Rom is very stable. No crashes here.

Fingerprint reader works ok. I was surprised of the newest EvolutionX version. I thought it was really quick. Nevertheless it works most of the time and is not something I would complain about.

Opening the app drawer and swiping though homescreens sometimes still stutters. It also feels like the maximum speed at which I can swipe the homescreens seems limited. That feels a little bit unresponsive.

When the app drawer is open it scrolls blazingly fast.

The only real complaint I have concerns the Bluetooth. When the screen is locked the connection between my watch and the smartphones drops occasionally and it doesn't connect again until a wake the phone. That's annoying because I use my watch get message notifications.

It also does not connect automatically after returning from a run where my watch is out of Bluetooth reach. For me it seems like there is a power saving option for Bluetooth enabled but I can't find anything in the settings to turn it off.

I didn't experience this issue with the stock MIUI, LOS 17 and EvolutionX.

Otherwise I had no problems until now. (y)
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Iocere:
I also can't get it to boot. Followed instructions and format data afterwards. Not using gapps.

Tried Arrow (oss vendor) and it was just fine.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] ugurbor:
I am having the same slowdowns in animations but they are easily fixed by a restart. Not sure what is the problem.

I also found the ROM really stable. Hoping we can have frequent updates.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] suisujin2:
I have still these Bluetooth problems where my watch disconnects constantly. I tried to pair it again and even removed it from the Garmin app. This did not work.

I saved a log file and there is an error regarding Bluetooth but I don't know if this has anything to do with the disconnects. Here is an excerpt with the error "E/BluetoothPhonePolicy":

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_main.cc(361)] bta_gattc_hdl_event: Event:BTA_GATTC_INT_CONN_EVT

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_main.cc(385)] Ignore unknown conn ID: 5

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_main.cc(361)] bta_gattc_hdl_event: Event:BTA_GATTC_INT_CONN_EVT

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_main.cc(305)] bta_gattc_sm_execute: State 0x00 [GATTC_IDLE_ST], Event 0x1f0c[BTA_GATTC_INT_CONN_EVT]

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_act.cc(488)] bta_gattc_conn: server cache state=0

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_act.cc(491)] bta_gattc_conn: conn_id=0x0006

[07-07 10:26:34.074 2304:3112 V/bt_stack]
[VERBOSE1:gatt_api.cc(1269)] GATT_GetConnectionInfor conn_id=0x0006

[07-07 10:26:34.078 2304:2304 E/BluetoothPhonePolicy]
Received unexpected intent, action=android.bluetooth.device.action.ACL_CONNECTED

[07-07 10:26:34.078 2304:2304 I/BluetoothPhonePolicy]
processDeviceConnected, device=10:4E:89:E9:8D:B0

[07-07 10:26:34.078 2304:2304 D/BluetoothDatabase]
setConnection: device=10:4E:89:E9:8D:B0 and isA2dpDevice=false

[07-07 10:26:34.078 2304:2304 D/BluetoothDatabase]
Updating last connected time for device: 10:4E:89:E9:8D:B0 to 815

[07-07 10:26:34.078 2304:2304 D/BluetoothDatabase]
updateDatabase 10:4E:89:E9:8D:B0

[07-07 10:26:34.079 2304:3112 V/bt_stack]
[VERBOSE1:bta_gattc_main.cc(305)] bta_gattc_sm_execute: State 0x02 [GATTC_CONN_ST], Event 0x1f0e[BTA_GATTC_DISCOVER_CMPL_EVT]

I've also attached the whole log.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] penglezos:
New release is up!

It is advised to flash latest Android 10 firmware before flashing this ROM according to your region. Clean flash is always recommended.

Thanks to everyone for reporting an issue properly by providing logs.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] suisujin2:
Thanks @Englezos. Great work.

I flashed the latest Android 10 firmware and dirty flashed the ROM. I think the stutters are gone. Also, the FOD now aligns properly within apps.

I noticed a bug with ANXCamera with the old and new version. When I select the portait mode the app stops working with the error message "Camera error. Can't connect to camera". Does anyone have the same issue?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] harry_turtle:
Has anybody got call recording to work?

Played around with it but to no avail.