yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] swiftbones74:
Have you seen this thread?

https://xdaforums.com/galaxy-s5/unified-development/rom-rr-n-5-8-5-t3815397
[Samsung Galaxy S 5 Unified Development] jadugur:
Which one suitable for g900h ?
[Samsung Galaxy S 5 Unified Development] yoahmad1995:
No soup for you sir.
[Samsung Galaxy S 5 Unified Development] IKGapirov:
There are many

:D
[Samsung Galaxy S 5 Unified Development] 5starprototype:
How did you get settings dark?
[Samsung Galaxy S 5 Unified Development] subaron:
How is the battery life on this ROM compared to stock for the S5 KLTE?
[Samsung Galaxy S 5 Unified Development] Gbrl95:
Go to Settings --> Configurations --> Interface --> Themes

Now set to black and turn on the dark/black.
[Samsung Galaxy S 5 Unified Development] 5starprototype:
Thanks!
[Samsung Galaxy S 5 Unified Development] Barabba11:
For klte there is already Oreo 8.1, I suggest switch to Lineage 15.1
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
Exactly what I thought. ?
[Samsung Galaxy S 5 Unified Development] Barabba11:
How you don't understand? There is out already Android 8.1 for your phone, why you have to try to solve problems on 7.1?
[Samsung Galaxy S 5 Unified Development] Mcha01:
Ru serious? ?
[Samsung Galaxy S 5 Unified Development] SohamD:
Because Oreo for our device has problems like auto rotation and worse battery.
[Samsung Galaxy S 5 Unified Development] yoahmad1995:
Stay away from it if its not good enough for you.

Devs do this for free so you can't be so demanding when you even didn't bother to donate for them for their work or thank them at least.
[Samsung Galaxy S 5 Unified Development] Barabba11:
Yes, it works ok to me..
[Samsung Galaxy S 5 Unified Development] SohamD:
Yes I'm away from Oreo until it gets better. My statement was perceived as demanding when it was not and I was just commenting about the current status. I appreciate the developers and am patiently waiting for improvements ?
[Samsung Galaxy S 5 Unified Development] yoahmad1995:
This place has nothing to do with your "comment"

If you want to report a bug in oreo ROM then report in ita respective thread.
[Samsung Galaxy S 5 Unified Development] SohamD:
Alright stop. My comment was in response to a statement from another user. We're discussing issues with Oreo ROM. It wasn't even a bug report as those are issues faced by most of the users; I was just stating the obvious. I keep a close watch on the Oreo threads. Don't need to reply to you again.
[Samsung Galaxy S 5 Unified Development] bobcatdiver:
Hi, is there an updated security patch? I know the last was in May, didn't know if I missed it.
[Samsung Galaxy S 5 Unified Development] swiftbones74:
Look here bro. The latest is July.

https://xdaforums.com/galaxy-s5/unified-development/rom-rr-n-5-8-5-t3815397
[Samsung Galaxy S 5 Unified Development] bobcatdiver:
Isn't that just for the G900F? Will that work ok with the G900R4?
[Samsung Galaxy S 5 Unified Development] bobcatdiver:
Gotta start reading more closely, lol. Works great, thanks!
[Samsung Galaxy S 5 Unified Development] damianiw:
Hi could someone tell me if nightlight works for them, I can see live display making a difference but night light doesn't even if I turn live display off too I've attached some screenshots - I was hoping it would be similar to f.lux which tints based on sunrise and sunset - live display seems similar so it's maybe just me being confused.

View attachment 1
[Samsung Galaxy S 5 Unified Development] Mcha01:
Its inside live display, and its working for me :confused:
[Samsung Galaxy S 5 Unified Development] damianiw:
Weird you can see its outside on mine above and doesn't appear to make any difference at all to the display
[Samsung Galaxy S 5 Unified Development] Mcha01:
I think it doesn't apply on screenshot , i just took. A screen shot while enabled and disabled it to see the screenshot, it didn't applied
[Samsung Galaxy S 5 Unified Development] damianiw:
Thanks for trying to help on my phone it doesn't appear to make any visible difference to the display even when I manually switch it on the screen colour is identical to my eyes - my screenshots are matching what I see perhaps its my eyes or my model, I appreciate the time you've given to reply to my query but think I'll just stick with live display.
[Samsung Galaxy S 5 Unified Development] HippoMan:
Infinite delay in screen-lock startup.

I've been happily using this ROM for a long time on my KLTE device.

Recently, I've noticed an issue that I can't figure out.

I have my screen lock timeout set to 2 minutes. The timing works fine ... if the device is idle for that amount of time, it indeed starts the lock procedure.

However, instead of locking the screen, the display simply dims and remains in that state without the locking actually taking place. I believe that there is supposed to be a short time window at the start of the lock process where the screen dims for a few seconds before the locking actually takes effect. On my device, this time window now seems to last forever.

I can't find anywhere to set the duration of that time window,

I understand that this could be due to the side effect of one or more of my installed apps, although I haven't figured out which one(s). However, I'm wondering if perhaps there is some build prop or sysctl value or other configuration variable that I can set within this ROM to get this pre-screen-lock dim time back to a reasonable value.

Thanks in advance for any help that any of you could offer.

.​
[Samsung Galaxy S 5 Unified Development] Ythan:
Did you install any of the modded Adreno drivers from this thread? I was having the same problem and that was the cause.
[Samsung Galaxy S 5 Unified Development] HippoMan:
Install failed because of device confusion.

I have been using this ROM on my KLTE device (SM-G900T) for a long time. I hadn't upgraded for a while, and I decided to install the latest version:

RR-O-v6.1.0-20180806-klte-Official.zip

When performing the ROM flash, I got this error, however:

E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx: this device is .

In other words, my system seems to think that my device is of type "." (a single dot) instead of KLTE ... or maybe the dot is the period at the end of the sentence, in which case my system considers its device name to be an empty string.

The value of Settings -> About phone -> Device name is "klte". The ro.rr.device build prop setting is also "klte".

I have done numerous upgrades of this ROM over the past year or so without this problem occurring.

Does anyone know how I can fix this problem so I am able to install this ROM?

Thank you very much in advance.

.​
[Samsung Galaxy S 5 Unified Development] HippoMan:
Using the official instructions, ROM flash seems guaranteed to fail

UPDATE: I did some investigation, and it appears that this ROM update is doomed to fail if we follow the official install instructions.

Those instructions say that we need to wipe /system before flashing the ROM, but if we do so, we lose the build props, which means that the following code at the top of this ROM's META-INF/com/google/android/updater-script will always fail ...

assert(getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" ||
getprop("ro.product.device") == "klteacg" || getprop("ro.build.product") == "klteacg" ||
getprop("ro.product.device") == "klteatt" || getprop("ro.build.product") == "klteatt" ||
getprop("ro.product.device") == "kltecan" || getprop("ro.build.product") == "kltecan" ||
getprop("ro.product.device") == "kltelra" || getprop("ro.build.product") == "kltelra" ||
getprop("ro.product.device") == "kltetmo" || getprop("ro.build.product") == "kltetmo" ||
getprop("ro.product.device") == "klteub" || getprop("ro.build.product") == "klteub" ||
getprop("ro.product.device") == "klteusc" || getprop("ro.build.product") == "klteusc" ||
getprop("ro.product.device") == "kltevzw" || getprop("ro.build.product") == "kltevzw" ||
getprop("ro.product.device") == "kltexx" || getprop("ro.build.product") == "kltexx" || abort("E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx; this device is " + getprop("ro.product.device") + "."););

Do I understand this correctly, or am I missing something?

---------- Post added at 16:02 ---------- Previous post was at 15:48 ----------

FURTHER UPDATE:

Actually, even without wiping /system, the flash fails on my device. But I got it to flash by (1) unzipping the ROM bundle; (2) editing update-script and removing those lines; (3) reconstructing a new ROM zip file from this modified code; (4) flashing with the modified ROM.

.​
[Samsung Galaxy S 5 Unified Development] swiftbones74:
Do I understand right? You updated to Oreo from Nougat? A clean install is the only way to do that if you don't want problems.
[Samsung Galaxy S 5 Unified Development] HippoMan:
Oh! I wasn't paying attention, and I didn't realize that the ROM is for Oreo until installation. Apologies for the bandwidth.

Actually, I got it installed (with the modified ROM) and it seems to be running fine, but I'll keep my eyes open for any potential problems and do a clean install later if necessary.

.​
[Samsung Galaxy S 5 Unified Development] HippoMan:
... except ...

After a full factory reset of my KLTE device, I still get the following error when attempting to flash this ROM ...

E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx: this device is .

.​
[Samsung Galaxy S 5 Unified Development] swiftbones74:
I am going to take a shot in the dark and say you need to update TWIRP. The latest for klte is 3.2.3-0. I am wondering also if you flashed proper gapps for 8.1.2 ?

I personally prefer RR_N. If you want to check out an unofficial Nougat RR build with latest security patches look here.

https://xdaforums.com/galaxy-s5/unified-development/rom-rr-n-5-8-5-t3815397/page7
[Samsung Galaxy S 5 Unified Development] HippoMan:
Thank you very much.

Flashing this ROM is the first step and gapps comes second. I didn't even get to the gapps step when this error occurred with the ROM flash.

I'll try the newer TWRP. I'm currently on 3.1.0-1.

I'm wondering if perhaps I need to install a newer bootloader before the Oreo flash would work.

Also, I'll look into the Nougat build you mentioned. Thank you!

.​
[Samsung Galaxy S 5 Unified Development] hiitsrudd:
Anyone have experience & comparisons with this rom:

[ROM][Unofficial][7.1.2_r36]Resurrection Remix-N-5.8.5 [KLTEXX][2018-08-05 PSL] by [MENTION=7489422]IKGapirov[/MENTION]
[Samsung Galaxy S 5 Unified Development] IKGapirov:
The difference is that in my build is Update Security string to 2018-08-05 :D
[Samsung Galaxy S 5 Unified Development] hiitsrudd:
[MENTION=7489422]IKGapirov[/MENTION], so you would recommend this update then on my G900T? Is OTA an option
[Samsung Galaxy S 5 Unified Development] IKGapirov:
I can not advise anything, everyone has their own taste
[Samsung Galaxy S 5 Unified Development] swiftbones74:
Don't use ota. You should update if security is important to you, if not don't bother.
[Samsung Galaxy S 5 Unified Development] HippoMan:
I upgraded TWRP. It works fine, but that didn't fix my problem with flashing the Oreo ROM.

I tried that Nougat build. I was able to load it, but I noticed occasional FC's with some of my apps that I never experienced on the older Nougat ROM, so I went back to that ROM. Later I'll spend more time investigating that issue.

I'm still trying to figure out why the Oreo ROM won't flash.

.​
[Samsung Galaxy S 5 Unified Development] Deydacar3:
Hi guys, which camera is the best for lineageos 15.1, I mean an app that comes closer to the s5 stock camera. I tried camera zoom FX and camera FV5 but they don't work well in lineage 15.1
[Samsung Galaxy S 5 Unified Development] HippoMan:
RR-O-6.1.0_xxxx updater script can't work with 5.8.3 ROMs

I have a KLTE device, and I have been using a 5.8.3 version of this ROM for a while. I decided to try out the RR-O-6.1.0_xxxxx series that is now being offered in this thread, but I'm having a problem upgrading.

The updater_script within the RR-O-6.1.0_xxxx ROM bundles checks the ro.product.device and ro.build.product build props to make sure that the current ROM is compatible for this upgrade. However, in this 5.8.3 ROM, neither of these build.props are set to any value at all. The only similar build prop setting for that ROM is an attribute called rr.ro.device, which indeed is set to "klte" on my device.

I know I can edit the build props or perhaps upgrade first to a 5.8.5 ROM which might (???) contain either ro.product.device or ro.build.product. And I know how to edit updater_script in a ROM bundle. But since 5.8.3 is a valid Resurrection Remix ROM release, it would be helpful if the RR-O-6.1.0 updater_script also checks the rr.ro.device property, in addition to those other two.

Thank you to the maintainers for at least considering this request of mine.

PS: On the download links offered in this thread, only the RR-O-6.1.0 ROMs are available. Otherwise, I wouldn't be reporting this in this thread.

---------- Post added at 16:05 ---------- Previous post was at 15:57 ----------

For clarity, here is more detail ...

The error I get when trying to flash any RR-O-6.1.0 ROM after a factory reset is this:

E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx: this device is .

And at the top of updater_script for that ROM series, the following code exists:

assert(getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" ||
getprop("ro.product.device") == "klteacg" || getprop("ro.build.product") == "klteacg" ||
getprop("ro.product.device") == "klteatt" || getprop("ro.build.product") == "klteatt" ||
getprop("ro.product.device") == "kltecan" || getprop("ro.build.product") == "kltecan" ||
getprop("ro.product.device") == "kltelra" || getprop("ro.build.product") == "kltelra" ||
getprop("ro.product.device") == "kltetmo" || getprop("ro.build.product") == "kltetmo" ||
getprop("ro.product.device") == "klteub" || getprop("ro.build.product") == "klteub" ||
getprop("ro.product.device") == "klteusc" || getprop("ro.build.product") == "klteusc" ||
getprop("ro.product.device") == "kltevzw" || getprop("ro.build.product") == "kltevzw" ||
getprop("ro.product.device") == "kltexx" || getprop("ro.build.product") == "kltexx" || abort("E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx; this device is " + getprop("ro.product.device") + "."););

.​
[Samsung Galaxy S 5 Unified Development] SohamD:
Try this

https://xdaforums.com/galaxy-s5/unified-development/mod-15-1-camera-supporting-60fps-120fps-t3809145
[Samsung Galaxy S 5 Unified Development] Deydacar3:
Thanks, I tried the mod you left and the truth is that it works very well on the g900p. The camera has notable improvements, and slow-motion recording is going very well. Thank you again
[Samsung Galaxy S 5 Unified Development] Emazed:
I'd like to start by saying fantastic rom! I can't believe my 4 year old phone can be this buttery smooth.

I'm having one slight problem though, on some occasions the screen will glitch out and and have a sort of"tear" effect to it, or else on rare occasions the screen will go black. Clicking the power button to turn the screen off and turn it back on fixes both these problems so it's not a MAJOR issue.

I just wanted to know is this a known problem or is there a fix for this issue? thanks once again to the dev of this great rom. Your work is massively appreciated by me! :D
[Samsung Galaxy S 5 Unified Development] SohamD:
Yup it happens to me as well. The screen just fails to turn on on the first try sometimes. A lot of people's phones have this issue. It's just that our screens have been damaged. So I don't think that the dev could do anything about it.
[Samsung Galaxy S 5 Unified Development] brickman:
Might be the screen ribbon is loose,happened to me.Just take it to a phone tech & get it checked.
[Samsung Galaxy S 5 Unified Development] Emazed:
Nope, definitely not. I literally never had it until I flashed this rom. Now I have it. not a massive problem and rarely happens but just thought I'd let the dev know. When the screen glitches out ect, tapping on part of the "glitched" effect returns it to normal. Definitely software... I'll try screenshot next time it happens. :)
[Samsung Galaxy S 5 Unified Development] swiftbones74:
This dev has left us a long time ago as, he got a new phone and RR official is Oreo now. If you want to stay on Nougat with way more up to date security patches try this.

https://xdaforums.com/galaxy-s5/unified-development/rom-rr-n-5-8-5-t3815397/post77052244

Or if you want official RR Oreo try link below but I don't think you will get any help from the dev here.

https://xdaforums.com/galaxy-s5/uni...rrection-remix-os-6-0-0-t3762443/post75867182

Good luck!
[Samsung Galaxy S 5 Unified Development] rusherrrx:
kltekor not available?
[Samsung Galaxy S 5 Unified Development] Startw:
My sim card contact are not showing for some reason.

When i go to import contacts, there is no option for sim contacts. Data and phone call/ text msgs are working well tho.

Anyone? please help me out with this issue. Other than that the rom is perfect.

My device is klte/G900f. Thanks.
[Samsung Galaxy S 5 Unified Development] saikyom:
I tried almost every rom for s5...and this one is by far the best, needs only a liiiiittle bit more options.
[Samsung Galaxy S 5 Unified Development] funeralplanner:
Need some help please. It has been several years since installing this ROM. I'm now trying to activate the phone for my young son to use. It is a sprint 900p and it currently has RR-N-v5.8.4-20170812-kltespr-official. For some reason I can't get the phone to program the new number and data and profile update. Just need someone to point me in the right direction. Using Team Win Recover 3.1.0-1 currently on Android 7.1.2
[Samsung Galaxy S 5 Unified Development] guest4711:
Does it detect the new simcard? Is the new simcard issued from sprint?
[Samsung Galaxy S 5 Unified Development] hiitsrudd:
Link

can you post the link for the rom thx:good:
[Samsung Galaxy S 5 Unified Development] saikyom:
Dude it's the rom on this thread the Nougat resurrection remix
[Samsung Galaxy S 5 Unified Development] funeralplanner:
It does, service is fine, just won't program. Also keeps telling me there is a new ROM update available, but it won't let me download it.
[Samsung Galaxy S 5 Unified Development] yeahman45:
anyone has charging very slow and battery drain (when screen off) very high?
[Samsung Galaxy S 5 Unified Development] yeahman45:
Any recommendation of kernel and settings to increase battery life? While performance is quite superb on this rom, battery life is very very poor.... I bought a new oem battery start of this year. I had much much better battery life with stock rom(but performance was quite aweful)...
[Samsung Galaxy S 5 Unified Development] PartimusPrime:
Hey bro could you please let me know how you have your SMS auto convert to MMS? Thanks.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I'm back on RR marshmallow but when I was on this rom I used Yaata for my sms and that allowed that configuration to auto convert to mms. You can find it in the play store. It's actually a really nice app.
[Samsung Galaxy S 5 Unified Development] Requiemmg:
Came from another ROM (ALEXNDR ROM, MM 6.0.1), factory reset/wiped from TWRP on my SGS5 (klte) and installed this one with Open GApps.

Three things (one showstopper and two minor questions):

1. I need to carry over my app data. So I used Titanium Backup to make a backup, but when I start it (current version with Pro key), it instantly crashes. Sent adb catlog to the developers, but is anyone els experiencing this? Did anybody found a fix? Or how should I carry over ma data? Went back to 6.0.1 for now...

2. On Pixel launcher, is there any way to remove Google and Weather icons from start page? Like it very much, but this is annoying

3. When I choose a photo as a background in settings, I can't crop the image or center it, nor zoom in...so it always just shows the leftmost part of the picture and not what I want to. How do I set it correctly?
[Samsung Galaxy S 5 Unified Development] krkhaha:
Hi everyone im on nemesis but battery consumption.... not good. I want back to aosp but I have some questions. Xposed working here? What about cm theme can I use pichblack theme for cm? Maybe someone know something about kernel... I mean, stock it's good? Audiomod... arise working here, someone know? And supers, working good without any problem? Thank you.
[Samsung Galaxy S 5 Unified Development] aogakid:
xposed and theme engine doesn't have support on cm(lineage) 7.1 based rom

and..... which is your model? I tested nemesis but it was very laggy to me
[Samsung Galaxy S 5 Unified Development] krkhaha:
My model klte. I don't have any lags. In my opinion nemesis it's fast but battery... no good. But if xposed don't work and cm theme engine don't work I stay on nemesis. Maybe later cm theme will be work and xposed. Sorry for language but this is not my first language.

On nemesis I find one big bug, maybe not bug but I don't like this,

My phone is seen like s5 neo.
[Samsung Galaxy S 5 Unified Development] scrawnyb:
Seems so @ the No SIM fix. I've been having this issue and dealing with it for about 2 weeks now (2 separate issues though). I *believe* there's also another way to fix this by modifying selinux permissions using "restorecon" on the appropriate folders, but I'm not going to advocate it because I haven't done it enough times myself to feel completely comfortable that I'm not giving bad advice here.

I've been spending my time getting "working" builds for my own S5 device, which was broken (causing the 2nd "No SIM" issue) due to the MM blobs that were committed right after the 2016-12-22 builds. I now having a working build with the old libs, but am trying to decide how we want to proceed to maintain some level of compatibility, as some phones (like mine) are still stuck on LP modem/BL, and others are moving on to MM (and eventually some will likely have Nougat). So in my mind, we are at a bit of a crossroads that may require certain devices (like mine) to use older LP proprietary blobs, whereas most new ones might be MM. Depends on the device support. But it's worth mentioning I have a working ROM on latest Lineage+RR sources as of today (screenshots attached below).

PM me with the logcat/dmesg and I can try to take a look.
[Samsung Galaxy S 5 Unified Development] aogakid:
G900x???? and this is not my first language either :)
[Samsung Galaxy S 5 Unified Development] krkhaha:
G900f

---------- Post added at 19:43 ---------- Previous post was at 19:41 ----------

This is very good rom really, but I don't like substratum. CM theme engine it's much better
[Samsung Galaxy S 5 Unified Development] aogakid:
ahhhhh mine is M... i agree with but there nothing I could do :)
[Samsung Galaxy S 5 Unified Development] krkhaha:
Guy's someone from here use black substratum theme? Please upload screenshot if you can ofcourse from setting I want see style before install. Thanks
[Samsung Galaxy S 5 Unified Development] jshute:
Let me know if you need someone with MM bootloader and recovery to test. Running the TMobile model on Cricket (ATT towers).
[Samsung Galaxy S 5 Unified Development] xarmx:
Thanks for the clarification scrawnyb. I haven't try the supposed fix for the TWRP restore yet. As for now, all I'm doing is backup all the system and user apps with data using titanium backup so that I'll just clean flash and restore what I need in the future (the previous restore workaround). Thank god for the 64gb microsd that I just bought. Probably gonna try the restore fix today.

If you want anyone to try the latest build, I'm using g900f with MM boot and modem. Then I can try the supposed twrp fix too if the earlier turned out to be a lemon build :D though any chance for the auto rotate and battery saver setting bug to be sorted out?