Database Users

[BUG Report] GT-I9100 Dialer isnt correctly working / AOSP Camera Bug

Hey,
I didnt know where i should Post my Bug Report so if its the wrong section dont hold back to tell me.
I'm currently using my Galaxy S2 for daily use and after flashing some Kitkat Roms Omni is in my opinion the most stable rom and with Nova + ART a damn fast Rom, so thank you very much for supporting my Device.
I dont know whats happening the last weeks but it all began with an Opendelta Issue, i wiped all Data / Factory Reset via TWRP and flashed the Rom completely new and OpenDelta still didnt work, it just said every day its all up2date. Now after a couple of days it is working again, dont know if it was a Server Issue or something else - at the official Omni Page no one post News so i have always to guess whats happening
Currently i found 2 Bugs, if you want to call someone you open up the Dialer and then the Button for the Numbers but after clicking it, theres nothing(Screenshot is attached). You have to go back and try it again then the Numbers are there. The second Problem is that there is no Zoom in the AOSP Camera App if you record a Video. My currently workaround is the Google Camera App, there all is working fine. Also there are some Issues with Apollo , freezing , doesnt update the Song DB etc. , dont know why its so popular - its horrible. Replaced it also with a 3rd party App - Omich/Rocket Player.
The last Problem is that not everywhere in the Settings the correct language is used, if you need some translation help im sure many users would like to help(including me) but that is in my opinion nothing critical .
...and sorry if my Text was hard to read, its not my native language but im working on it :silly:
Regards

Per the FAQ, this is not the place to put bug reports.
However, I9100 hasn't been maintained in a long time, so filing a bug report will be a waste of time. Support for this device is currently going to be dropped with Android 5.0, and if it receives 4.4 bugfixes, that'll have to come from a new maintainer as none of the former maintainers have time/motivation for the Exynos 4210 devices these days.
Some of the issues you describe with Apollo aren't Apollo issues, but the result of a very deep-down core bug that has a side effect of screwing up storage access. This bug has been known for nearly a year (there's a big thread disucssing it somewhere around here...) and still no one has found a fix for the root cause. In fact, it's one of the #1 reasons the device is getting dropped for L. (It will absolutely not receive nightlies unless someone finds and corrects the root cause.)

Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?

pfxandroid said:
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
Click to expand...
Click to collapse
Well, there are three things you listed:
1) Dialer stuff - probably some sort of odd HDPI issue and/or graphics subsystem stuff. The Exynos4 graphics subsystem is why many developers don't want to ever touch the platform again.
2) Zoom in video - What resolution was Google Camera? Zoom has NEVER been available for 1080p resolutions on the Exynos 4210 family, not even stock firmware will zoom in 1080p
3) The storage issues are a symptom of a deep-down kernel bug that no one has found the root cause of. This is the #1 reason the device is getting dropped for 5.0 - there is no chance even if a new maintainer steps up that nightlies will resume until someone tracks down the root cause of this one. http://forum.xda-developers.com/showthread.php?t=2612329 has more discussion (warning: It's long...)

[ROM][5.X] CyanogenMod 12.1 for Hisense Sero 7 Pro [M470BSA][METICULUS]

CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone, tablet or PMP.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
These are CM12.1 builds for the Hisense Sero 7 Pro (Enterprise, M470BSA). It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
GPL:
Code:
http://github.com/Meticulus/android_kernel_hisense_m470bsa
Warning: Currently, this ROM is in BETA
Download: meticulus.co.vu
Gapps here or here

I'm impressed. I have a Moto G 2nd Gen, which supposedly was one of the first devices to get Lollipop, but you beat them to it

NEW BUILD!
New build posted!
Mitigated a kernel issues causing lag
CM Sources update

Dude, thanks. Sero 7 and Dev's just keeps surprising me.

LOVE IT, minus one killer bug.
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work

Quickdraw996 said:
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work
Click to expand...
Click to collapse
My apologies for the sign up issues on my site. I believe I have them worked out and I have cleared your attempt so you can try again if you like.

NEW BUILD!
External SD fixed
SeLinux: enforcing
:highfive:

I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?

lichan said:
I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?
Click to expand...
Click to collapse
Hmm... S-on is an HTC thing isn't it? Like some sort of bootloader thing I think... Strange. Might be an Sepolicy issue.
I'll look into it... I currently looking into Apps2SD issues on another device ATM...

HTC and something else if I remember correctly.
Sent from my XT1023

A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.

AngryManMLS said:
A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.
Click to expand...
Click to collapse
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....

Meticulus said:
External SD fixed
SeLinux: enforcing
:highfive:
Click to expand...
Click to collapse
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)

Quickdraw996 said:
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)
Click to expand...
Click to collapse
Don't dirty flash this one, the selinux contexts will be messed up if you do....

Alright, thanks!
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)

Meticulus said:
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
Click to expand...
Click to collapse
True. It's a matter of optimizing code and what not I'm assuming.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
Click to expand...
Click to collapse
I'll try to get you a log in the next day or two. I've been busy working on a project on my Verizon Note 3 not to mention I'm still trying to find a recovery that will still let me restore back to my CarbonROM 4.4.2 backup. Seems like the newer recoveries aren't letting me restore back... very weird.
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
Click to expand...
Click to collapse
True true. I was more of less noting there being no theme support for those wanting to know more than anything else.
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....
Click to expand...
Click to collapse
I'll try to get you a log of Bluetooth use on my end alongside with the Titanium Backup issue.

And here we go...
http://www.androidpolice.com/2015/0...-built-lollipop-5-0-1-rolling-select-devices/
Official nightlies are coming out now.

NEW BUILD!
CM Sources update
Tweaks to Kernel for latency...
Feels snappier, but might be a placebo effect.
New bug/issue tracker on the download page. Please submit issues/bugs there. :good:

NEW BUILD!
BLUETOOTH FIXED!!!
Graphical Glitch in Navigation bar fixed
Missing schedulers in performance fixed
:victory:

Really want to try this but its my wife's tablet. So she won't let me. She doesn't want to loose everything on her device.

CyanoGenMod 13 soon ?

Don't want to ruin the surprise but I think somebody is trying to develop CyanoGenMod 13 for us...
https://www.androidfilehost.com/?w=files&flid=52432

http://forum.xda-developers.com/xperia-z5/general/dev-cyanogenmod-sony-xperia-z5-t3302622
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
yeah @moonbutt74 is working on the Z5 Premium, @CTXz on the compact

zacharias.maladroit said:
http://forum.xda-developers.com/xperia-z5/general/dev-cyanogenmod-sony-xperia-z5-t3302622
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
yeah @moonbutt74 is working on the Z5 Premium, @CTXz on the compact
Click to expand...
Click to collapse
To be fair we work both on both devices. There's still nothing to celebrate as both builds are still flooded with bugs

Risky to test ? x)

I'm building a pure aosp rom right now , will test today and see what the bugs etc are.

krabappel2548 said:
I'm building a pure aosp rom right now , will test today and see what the bugs etc are.
Click to expand...
Click to collapse
It should just work (Internet, Phone, SD Card, sensors, etc.) - the camera had some colors off last time I built one,
but with recent kernel changes it should have improved

krabappel2548 said:
I'm building a pure aosp rom right now , will test today and see what the bugs etc are.
Click to expand...
Click to collapse
zacharias.maladroit said:
It should just work (Internet, Phone, SD Card, sensors, etc.) - the camera had some colors off last time I built one,
but with recent kernel changes it should have improved
Click to expand...
Click to collapse
@CTXz has done a great job of squaring the sources for Cyanogenmod the, the repo is Sony Kitakami Platform Developer Organization A straight run of a build @ branch cm-13.0 should result in the following:
On my current build for the Z5P, @KbaB.BroS confirmed nfc and communications functional.
Bluetooth file transfer is working through cm filemanager send function, but legacy bluetooth apps may fail.
Media Playback, seems square, though access the microphone for audio recording is no go, though mic working in-call.
Camera is janky, and record function broken so screen record fails.
With the current state of Cyanogenmod, OpenGapps is working, Though due to mic issue OK Google crashes.
Rotation sensors are working, yay games.
Brightness is twitchy/dark, needs work.
CTXz, says omnirom has the storage issue sorted for exfat cards so i'm looking at vold to see if i can get it working.
Note: in house root is a bit twitchy, while system-less root is cool, i would recommend going the "traditional" route, BETA-SuperSU-v2.52
does well.
Trebuchet has issues when laying out wallpaper from gallery, Nova Launcher does not, so it's a problem with trebuchet.
m

Slim6 port for R1-HD **CAMERA_Almost_FIXED**

Know issues:
1. Bluetooth toggle will not turn on
2. video codec makes first 10-15 seconds of video only green screen--(not noticed so much after install gapps and using chrome browser)
3. Camera not working
Resolved*
*testing phone had stock camera app disabled and was using open camera. With stock camera multiple crashes and unable to connect issue with camera. V3.5 has removed stock camera and added open camera to priv-app (preinstalled)
4. Microphone is also not working
V3.5 has fixed microphone.
5. video recording not working
V3.7 fixed video record for back camera only--also seems to have stabilized photo camera--(but still has crashed)
V-x-4.1 minor edits. Removed old renamed files. Removed apps and libs for fingerprint scanner. Swapped apns-config.xml from V21 to try get connection for more carriers. But it seems some devices are not able to even see imei from board V4.1 removed. Audio broken
x-v-4.6 has audio streaming partly functioning. Audio/ video plays some amount of time then stops. but will continues if playing through bluetooth. Further testing on speaker needed. Audio issue notIS present in FMRadio and unknown in phone. So far only in streamingMOST SOUND situations, like music apps and YouTube.
Also list of added apps primarily added for testing reasons
1. GPS test
2. AudioRecorder
3. File_Manager _es_file V3 (fewer ads)
4. OpenCamera
V5.0
removed extra fingerprint program, added MDDB folder (base band) trying to resolve 2 reports of lost IMEI on this rom. I have not had issue, so cannot confirm if adding these files has fixed problem.
V6.7-current beta
/system changes tracked on github
v6.7-or current /system
boot.img changes on github
https://github.com/mrmazakblu/Slim-port-boot-img
..
..
Install:
must have unlocked boot loader.
put rom file on sdcard and install with twrp =>Latest TWRP 3.1.1-0
you needs to install gapps.
http://opengapps.org/http://opengapps.org/
You need to enable navigation bar to get onscreen buttons.
settings >Navigation >Navigation bar >Enable navigation bar.
thanks to : @vampirefo this rom is ported from his build for the BLU Life Max
XDA:DevDB Information
Slim6 port for R1-HD, ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 's Blu Life Max SlimRom
Version Information
Status: Beta
Stable Release Date: 2017-06-16
Current Beta Version: x-5.0
Created 2017-06-09
Last Updated 2017-11-02

Thanks Great work I would like a RR.5.7.4
Enviado desde mi R1 HD mediante Tapatalk

can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak

meroher said:
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
Click to expand...
Click to collapse
there are 4 screen shots on the screenshot tab. But the look of any rom can be changes how you like with different launchers if desired.

Fixed the bugs except for the camera one.
New zip file in download tab.
Moved status from testing to beta.

camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk

vampirefo said:
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6

Camera Is Fixed*
I now have camera working on this slim port...
uploading built/port number 33 (X-3.3)
still needs small bug fixed, that will not screen cast to chromecast.
and first time I opened camera I did not have any on-screen navigation buttons(no way to exit camera). after some time buttons were available and next time it opened normal.

mrmazak said:
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Click to expand...
Click to collapse
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk

vampirefo said:
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,

mrmazak said:
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
Click to expand...
Click to collapse
Yes, ROM is built for 6737, R1HD and Life Max are almost the same phone, difference size, camera and 6737 instead of 6735.
Anyway good job.
Sent from my Life Max using Tapatalk

how is the performance vs stock with all bloatware removed?

deathblade200 said:
how is the performance vs stock with all bloatware removed?
Click to expand...
Click to collapse
Seems a little quicker on slim6

Great job, I like it

So is this a usable daily driver?

roboman2444 said:
So is this a usable daily driver?
Click to expand...
Click to collapse
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.

mrmazak said:
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
Click to expand...
Click to collapse
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?

roboman2444 said:
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
Click to expand...
Click to collapse
I do not think the camera fix here will help 7.
These lib files, "so" files, "blobs", call them as you will. Are still for Android 6 so , as I believe will not work on 7

mrmazak said:
Seems a little quicker on slim6
Click to expand...
Click to collapse
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not

deathblade200 said:
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
Click to expand...
Click to collapse
They would be the same or about the same, a rom doesn't increase benchmarks, a custom kernel might, benchmarks have their place this isn't one of them.
To each their own I guess.
Sent from my Life_Max using Tapatalk

Samsung Galaxy S5 G900W8 What Custom Roms Work

Hello I am new to custom roms
I am working with a Samsung Galaxy S5 G900W8 as a platform for learning
Can the experts here recommend some custom roms
I finally got one to work - however it seems to be for the TMobile version
The install worked - yet without wifi support
If people here please suggest a number of options to work through

I'm on the same phone as you. LineageOS works. I'm using Ressurection remix latest build KLTE. The KLTE bit is what you want for the roms. There are others I've tried but I end up back with the two I mentioned as they offer more functionality. Those are nougat. Tipsy Rom 6.0.1 works if you want marshmallow. So does the RR marshmallow rom. I've got twrp custom recovery installed. And magisk for root. Super user works as well but you won't pass safety net. So use magisk if you use android pay or play Pokemon go.
---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------
Do the custom recovery first if you haven't already. I assume you have because you flashed a rom. If you are using Odin to flash them you are probably flashing stock. Don't do that. Not unless it's the stock for your device and you don't want to be on a custom rom
---------- Post added at 07:14 PM ---------- Previous post was at 07:05 PM ----------
You will need Odin to flash the recovery. You can root from the custom recovery. And you will flash roms from the custom recovery on the device.
https://twrp.me/devices/samsunggalaxys5qualcomm.html
This will give you the files and info you need to use Odin to flash twrp. Lineage and RR have their own sites as well. Super easy to find. Just remember the KLTE. Download the rom right onto the device or put it on the SD card. Boot into recovery using power, home and volume up and go to the directory with the rom zip, select it and swipe to install. Don't dirty flash the rom, wipe the phone first. It will not delete the custom recovery. Once the rom is installed reboot. It will take a few minutes to load. You flash the superuser or magisk zip from the recovery as well. If you do superuser download the app from playing store. Magisk you can find on xda. After all that you are rooted and on a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
You can use the recovery to create a backup of your phone too. Usually I'd recommend this but you already flashed a rom that's not working right anyway.

Security Updates for Samsung Galaxy S5 (Telus Canada SM-G900W8)
godkingofcanada said:
I'm on the same phone as you. LineageOS works. I'm using Ressurection remix latest build KLTE. The KLTE bit is what you want for the roms.
Click to expand...
Click to collapse
Vortell said:
Most roms based on Lineage[LOS] should work with any Snapdragon based S5[KLTE] LOS unified the roms a while ago. I use crdroid it has adaway built in super stable..
Click to expand...
Click to collapse
I'm using a Samsung Galaxy S5 (Telus Canada SM-G900W8), and given the lack of support I'm looking at a custom ROM.
Can someone please tell me if any of the above ROMs are getting good security patches?
I believe that there are mitigation patches for the Krack WiFi and BlueBorne Bluetooth Vulnerabilities that were recently disclosed., but most phones will take a long time to get them, if ever.
Any suggestions/input is much appreciated.

SM-G900W8 Best ROM for Stability/Security/Usability?
Vortell said:
I prepher crdroid to RR but not sure if either have kept up with latest LOS changes but I know from Oct article LOS is patched blueboorne was before this.
https://www.xda-developers.com/future-lineageos-14-1-builds-safe-krack/
Click to expand...
Click to collapse
Thanks Vortell for the reply, that article is very helpful. Based on your response I think I'll give crDroid a shot.
(Just curious - are you using an SM-G900W8?)
crDroid was on my radar, but when I went to the crDroid web site, and it didn't list the S5/SM-G900x as an officially supported device. I see from the link you provided below references to an up to date S5 crDroid ROM, so it looks like this should be a good mainstream choice.
Other than surfing through tons of (sometimes great and sometimes terrible) YouTube vids any suggestions as to a quick way for me to speed on the mainstream ROMs? Do I need to consider anything beyond LOS, RR and crDroid?
I don't know if something like it is baked in, but from what I've been reading I need to install something like Xposed/XPrivacy. Way too many apps ask for access to identiy, contacts, location and device control that they don't need for me to use the app, and that I don't want them to have. Denying permission is no good, because then the app will die. Other than Xposed/XPrivacy should I be looking at anything else?
My priorities are Security, Stability, Usability, and then Features and Speed. Don't need/want bleeding edge, and it things are working, I likely won't update unless there is a vulnerability that needs patching or a really killer feature I want/need.
Vortell said:
Since both are built off of LOS source code they use should be patched. Also you can make any kltevzw build work with your w8 with right changes to build prop and APN. If my memory serves me right. I think it has all been integrated and built into LOS for a long while though.
Ask the developers for each over at:
https://forum.xda-developers.com/galaxy-s5/unified-development
Click to expand...
Click to collapse
Any suggestions as to how I can do this since I'm just a Noob without sufficient permissions to post in that forum?
(Just in case someone from the crDroid project sees it: Props on the really nice "banner page" ( https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894 ) - very helpful. Suggestions: It would be helpful if there was a line about security/patches as well as a way for a user to quickly get up to speed on changes to know if they need to update. )
Thanks again/in advance for any comment, suggestions, or assistance

Vortell said:
Speed on mainstream rom? If you ment speed up, then there is only tuning the kernel or changing it. There is very limited support for extra kernels now. I think there might be a couple but you need to make sure they are compatible with los. You can also adjust the performance with kernel auditor. Lspeed it's another mod that had options like that. There maybe a bit more but once I got on crdroid my performance was fine. There other thing you can do is try to find updated drivers for the video card.
Click to expand...
Click to collapse
Sorry, I guess there was a typo (or auto correction gone wild) I meant to say how can I get up to speed (meaning become informed) as to the differences between the major mainstream ROMs. As I said, as long as it's useable stability/security is much more important than speed. Thanks for the detailed info anyway.
Vortell said:
If you want paranoid level of control xprivacy is good otherwise privacy guard baked into all there if those is pretty damn good. Honestly if you don't have a Sunset device and are concedering using xprivacy for extra protection then you should really use gapps alternative. I forgot the frameworks name. It uses open scource and privacy minded services to avoid Google tracking. Then should only use simple app stores like xda or f-droid which has something called yalp if you want free stuff from Google. Otherwise privacy guard which will limit access to the things you mentioned is baked into all three you just have to turn it on in each. Crdroid has adaway built in if you add extra lists it really cuts down on ads. I also like viper4arise mod so I can increase volumes on my phone and change sounds processing on the fly. Then for the s5 there are volumes boast mods specifically because the mic is quiet.
Click to expand...
Click to collapse
Thanks very much for this.... Yalp looks very interesting, I'll check into that further.
Is this the viper4arise sound mod you are talking about?
( https://forum.xda-developers.com/galaxy-s5/general/mic-volume-gain-mod-s5-t3491483 )
Vortell said:
Here are the extra lists I use for adaway:
http://winhelp2002.mvps.org/hosts.txt
http://someonewhocares.org/hosts/hosts
http://www.malwaredomainlist.com/hostslist/hosts.txt
https://isc.sans.edu/feeds/suspiciousdomains_High.txt
https://mirror.cedia.org.ec/malwaredomains/justdomains
https://ransomwaretracker.abuse.ch/downloads/RW_DOMBL.txt
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://raw.githubusercontent.com/zant95/hosts/master/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
Click to expand...
Click to collapse
These are great - thanks. I run a pfSense firewall, and I use some of these on it. One question... is it possible to override list entries either temporary or permanently? I know I've had problems with my firewall breaking certain web pages. It's a real problem on those rare occasions when I really need access to a broken page. I put up with it because ad networks have been a vector for malware recently.
Vortell said:
As for exposed it's great and all but can lead to problems with substratum. It does work great with Crdroid and substratum for me using:bubble upnp, gravitybox. It didn't work though with rr on my note 4 with substratum. Someone reported it worked fine without substratum. Honestly the only reason I like it past what is baked into Crdroid though is to change status bar text colors. Rr allows a bit more statusbar customization to begin with though. I have also read rr is some what problematic on s5. It will however be very hard to get Android pay working on anything but touch wiz based 6.0.1 rom FYI because of safetynet. There is also was to get shealth working but that is very privacy invasive. Crdroid has g+ page if you want you ask them stuff directly. Either way back up your working rom. Sd cards are cheap now. You can always try more then 1. There is even was to use note then one rom on one phone. Read around a bit is kinda fun.
Click to expand...
Click to collapse
Thanks for this.... Am I correct that Xposed that it's necessary for XPrivacy? If it's just for color changes, them I won't need it. I'm not worried too much about theme colors... as long as it's readable I'm fine.
As for Android Pay, good to know.... these phones are such security cess pits, that I'm not likely to use my phone for banking or payment of any kind for some time.
Thanks again... I can't tell you how much I appreciate the help.

Vortell said:
Xprivacy is great if you trust the school who made it and your that paranoid... At that point though you should be buying a new phone or learning to Port a more secure kernel then Linux. Or at least a security build of it. Outside that the kernel is going to be outdated to one degree or another.
Click to expand...
Click to collapse
You raise some good points - and again TRUST is a big issue. I'm not sure that buying a new phone even solves the problem. Ultimately you have to trust somebody, and quite frankly a bunch of passionate hackers looking over each others shoulders is likely more trustworthy than a bunch of corporate scumbags trying to market/sell your personal information. The big manufacturers (Other than Google-and I don't like their phones because they don't have a removable SD Card) are historically poor with support.
Security is often an oversight because the market doesn't value it. (Although all the high profile hacks that have occurred may change things.) "Secure" phones are such a limited market that they are hard to get, have poor support, and are obscenely expensive.
Anyway that's enough philosophy/ranting.
Vortell said:
The least secure part of most Androids is the Google framework though. I use xprivacy on older devices because it's the only reliable way to get control over permissions. The problem is there is to much for less advanced users. Some permissions look invasive but it's just the way Google put the os together. Like phone access is there even if it's just to pause sound for incoming call.
Click to expand...
Click to collapse
You raise a very good point about the underlying design. Do I understand correctly that the permission that allows pausing the sound for an incoming call will also allow an application to make a call?! If so that's totally crazy. Again back to my comment about corporate scum bags. Google sells advertising/data services, and they are going to set up the design to be as exploitative as they can get away with. If their system was secure/privacy oriented a lot of the ecosystem would disappear.
Vortell said:
Anyways what I was talking about was gravitybox which I feel outside of Android 4 x is the best Xposed mod. In Android 4.x it's app settings and xprivacy for the permission control.
Click to expand...
Click to collapse
I had a quick look.... gravitybox while allowing many interesting customizations doesn't seem to deal with permissions - or did I miss something?
Vortell said:
Honestly adaway is like a firewall though it's linked to domain rather then port. No firewall should use lists like that. They should close off ports unless connections originate from you. Adaway uses an old school method of using what's called a host file to redirect the request to your own phone with no http service at they address set up there are also pretty services thought your own phone that so this aka blockad and dns66 but they use extra services so it's a tiny bit less per effective. All 3 are easy to turn off.
Click to expand...
Click to collapse
As I said, I run a system very similar to that on my pfSense firewall (pfBlokerNG) to limit the ad networks as an infection vector. My firewall does all the DNS and NTP for my system to somewhat restrict the number of endpoints my system is communicating with. As I discover restrictions that are too problematical I reluctantly override them or stop using the service that depends on them depending on the circumstances.
Vortell said:
If you care about privacy, get the German Firefox klar or Firefox focus for your browser.
Click to expand...
Click to collapse
Thanks for this... Klar looks like a useful addition.
I'm less worried about ad tracking than spyware (unauthorised mic/camera/theft of data/passwords etc.), ransomware and permissions that allow my contacts and cell data to be stolen. I don't like to be accessible 24/7 anyway, so as long as the airplane mode actually works I make frequent use of it--the problem is that it may not work, and there is no way to tell since the cell radio is not easy to audit. I discovered questionable behaviour on my first android jellybean (way back in the day) by putting packet capture on the wifi. That was my first foray into modding.
Thanks again, and in advance for any assistance/advice/comments.