yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Noob9496:
I use LineageOS 16 for microG, all works. If you use black theme in android settings, turn off.
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Thanks, disabled troubleshooting dark mode.

But past builds didn't have this problem!!!
[Samsung Galaxy S 5 Unified Development] curiousrom:
Google Chrome Browser Crashing

Reboot, reproduce the Google Chrome Browser Crashing in Dark Mode problem, capture a logcat & attach it to a reply.

Or try the Google Chrome Browser Dev, Beta & Canary versions: https://play.google.com/store/search?q=chrome&c=apps

***
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
logcat in Android dark mode

And a screenshot of the Google Chrome crash
[Samsung Galaxy S 5 Unified Development] curiousrom:
Google Chrome Browser - Dark Mode Working

I don't know what's wrong with your setup but just for you: using Play Store I downloaded the Google Chrome browser & a minute after installing it, Play Store offered an update.

Currently I have Chrome v80.0.3987.119 & it's working fine in Dark mode as you can see in the screenshots.

When starting Chrome for the first time I declined:

Help make Chrome better by sending usage statistics and crash reports to Google.

Lite Mode: Browse faster. Use less data. In Lite mode, Chrome loads pages faster and uses up to 60 percent less data. To optimize the pages that you visit, Chrome sends your web traffic to Google.

Turn on sync: ...Google may use your history to personalize Search, ads, and other Google services...

Then > Chrome (which was Light theme by default) > Settings > Themes > System default and Chrome instantly switched to Dark Mode because in my > Settings > Display > Style > Dark is selected.

If I close Chrome, clear Recent apps, > Style > Light & Open Chrome it's now automatically Light themed.

That's tested on Galaxy S5 G900M LineageOS 16.0 klte build 2020-02-23 + Open GApps Pico + LineageOS AddonSU & no custom kernel.

Did you install a custom Adreno driver and/or kernel?

Too busy right now, will take a look at your logcat later. Thanks for posting it. :good::cool:

***
[Samsung Galaxy S 5 Unified Development] digital mystik:
Has anyone else lost cellular recently? Just updated a G900V today with the 2/23 nightly and lost network. I have IMEI and MEID numbers that aren't zeroed out, and have the latest haggertk baseband/modem installed. Going to try to reinstall the baseband and modem to see if that does anything... hoping it's just the latest build and will work itself out with the next one *fingers crossed*, but it looks like everyone else is fine.
[Samsung Galaxy S 5 Unified Development] haggertk:
That part is relatively "easy" -- looks like the packages/apps/Settings chain got stale because someone either added/removed/reordered/whatever the changes. I haven't synced in a couple days because I've been attacking sepolicy. I'll make sure to update the picklist.

As far as your build issue, it's likely build environment. Runtime speed will suck once selinux goes back to enforcing, but you can try replacing all of the below with WITH_DEXPREOPT := false just to see if a build completes.

https://github.com/LineageOS/androi...lob/lineage-16.0/BoardConfigCommon.mk#L55-L60
[Samsung Galaxy S 5 Unified Development] anonnow:
Would be nice to have signature spoofing for microg.
[Samsung Galaxy S 5 Unified Development] SNiPe08:
[ROM][9.0][UNOFFICIAL] LineageOS 16.0

I have tried the last build of haggertk (lineage-16.0-20181019-UNOFFICIAL-klteduos.zip). Magisk doesn't seem to work after flashing versions 17.1, 17.2, 17.3 (tried many times). In TWRP recovery it is saying it was successfully installed but after booting "no root" was detected by any root checker and obviously magisk manager is not there in the apps.

I tried to flash superSU and my device was successfully rooted and I can use Titanium backup. But I don't want to use superSU because of lack of updates as its developer already stopped. Any chance for our beloved Magisk to work? My device is SM-G900FD.
[Samsung Galaxy S 5 Unified Development] haoyangw:
Did you try installing Magisk Manager manually(using an apk)? I faced this a few times before but once I installed Magisk Manager I could see 'Magisk 17.x is installed' and root works properly(though a few times Magisk Manager asked to download some extra files but after that everything works perfectly).
[Samsung Galaxy S 5 Unified Development] TeamAndroid14:
Go into Magisk manager app and go into "superuser" and grant the root checker app. Whenever an app was denied root, simply go into Superuser in Magisk Manager and thats where all the apps that were granted and denied root
[Samsung Galaxy S 5 Unified Development] justjr:
Yeah, magisk works fine with LOS16, but flashing the zip on twrp don't install the apk, if you do it manually you will find magisk working fine.
[Samsung Galaxy S 5 Unified Development] silva_dump:
Can anyone of you suggest a good profile for get good standby battery please

Anyone can share cpu usagea n governor development you'll using

It seems that SOT is not a problem but standby is a lil problem in these new LOS operatin systems
[Samsung Galaxy S 5 Unified Development] ItzRsh:
Are the simcards working on kltedous build?
[Samsung Galaxy S 5 Unified Development] clockstoper:
SIM cards works fine here

On my klteduos sim is working just fine
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks for the pointer. I really hate distracting you with this sort of stuff, it's not fair given it's unsupported and a work in progress.

A 'repo sync haggertk' was not quiet sufficient but sorted the SIM issue and then commenting the code and inserting the WITH_DEXPREOPT := false allowed me to build successfully! :good: :cool:

I'm running Ubuntu 16.04, so I am guessing that there maybe something amiss at the OS level. I think there is at least one other user seeing the same thing. I was able to built 15.1 and 14.1 successfully on my 'aged' Linux box. I'll have a tinker and see if I can narrow it down a bit more.
[Samsung Galaxy S 5 Unified Development] :
Rom is working fine, except for Magisk im losing root from time to time and I have to restart my device to get the root working. Nothing for this rom in the Magisk thread. If any1 have the same issue and know if we can fix this. :)

G900F klte, Bruno's build (18/10/05), Magisk 17.3
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
Read about 7 posts before yours, all is explained.
[Samsung Galaxy S 5 Unified Development] thystan:
S5 LineageOS16 encryption

Hey,

I use lineage-16.0-20181019-UNOFFICIAL-klte on a 900F with twrp 3.2.3

I can not encrypt my device and SELinux is not enforced.

How can I encrypt my device?

How can I enforce SELinux?

My device is not rooted.
[Samsung Galaxy S 5 Unified Development] TheFixItMan:
You can't - selinux is set to permissive

Unless you want to rebuild the kernel & get selinux working as enforcing encryption will not be possible

Obviously when the rom is a position where all things are running as expected they will start on the more difficult things like selinux

Just wait
[Samsung Galaxy S 5 Unified Development] thystan:
Sounds legit!

I didn't know they were connected.

What's the latest version with enforced selinux/ encryption possible?

P.S. Everything else works for me, though I just use apps and not much OS functionality.
[Samsung Galaxy S 5 Unified Development] TheFixItMan:
Lineage 15.1 if you require encryption - eventually it will be available on lineageos 16 too
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
That's a funny thing regarding the SEAndroid Permissive State that i've noticed regarding many/most of the Custom Firmwares released for Android 9.

There's been posts on my SELinux Switch thread that pops up from time to time regarding this topic.

When i see this situation, all I can really tell the members is that the Permanent Permissive State is by design to allow the Firmware to work.

I also add that the Firmware Developers hands are pretty much tied at this time and I'm sure that those developers are working on a way to allow the Firmware to appropriately operate in an Enforcing Mode which, in turn, will allow the SEAndroid the ability to change upon demand.

I feel bad that there's nothing more I can do to help those members out. :(

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Samsung Galaxy S 5 Unified Development] Trey n:
On stock battery and 10-19 build with smartpack kernel all that I can say is wow! Ur awesome devs keep up the great work!
[Samsung Galaxy S 5 Unified Development] silva_dump:
Bro can u please share the kernal info and the tweaks please
[Samsung Galaxy S 5 Unified Development] Trey n:
Here ya go extract it and

Apply in smartpack kernel manager

Edit I also have greenify installed

And govtuner
[Samsung Galaxy S 5 Unified Development] kurtn:
Just crashed a other phone with same symptoms by dirty flashing an old build. Later I recognised, only my ISP was down for a few hours.
[Samsung Galaxy S 5 Unified Development] digital mystik:
I wish it was just my ISP haha.. but yeah I have tried everything aside from starting from scratch. Hopefully a newer build will fix the issue.. not sure what happened.. wifi works, but my SIM isn't recognized and no cell connection.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 G900V No Network

The S5 G900V is notorious for needing an EFS partition restore once in a while after flashing LineageOS 16.0.

Probably related to the required bootloader hack to unlock it and the fact that it can't be updated. Say thank you to Verizon for asking Samsung to cripple their S5 G900V branded models.

See S5 - No Network, No IMEI, No SIM & EFS Partition Restore Fix.

My Galaxy S5 G900M LineageOS 16.0 klte build 2020-02-23 works fine.

Please report back if you fix your problem or not. :cool:

***
[Samsung Galaxy S 5 Unified Development] digital mystik:
Will do.. it's late where I'm at but I'll have a go at it tomorrow. I was going to try tonight but the OE firmware looks like it's going to take hours to download.

I might try to find an older build if possible so I can use Towelroot to make it simple; it's been a while since I rooted and it looks like a few of the root package links are down unless I didn't see it correctly.
[Samsung Galaxy S 5 Unified Development] curiousrom:
[MENTION=8521285]digital mystic[/MENTION] - You don't have any TWRP backup that includes an EFS partition?

Flashing stock Samsung & unlocking the G900V bootloader is a pain.

Try here https://xdaforums.com/verizon-galaxy-s5/general/testers-required-easier-root-method-t3561529

***
[Samsung Galaxy S 5 Unified Development] digital mystik:
Unfortunately I don't.. didn't think to years back when I first rooted it. (that's what I get for not going through all the docs at the time)

So having an IMEI number doesn't mean that /efs is intact necessarily?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 G900V No Network

No. There is a lot of stuff in there.

Having a recent TWRP full backup is good practice when using custom ROMs, especially before updating.

I have a S5 GSM phone so I'm just guessing but can you see in > Settings > Network & Internet > Mobile network > Advanced > Preferred network > and set to CDMA w/o EvDo, turn off the S5, wait 2 minutes then back on?

Can you see > Settings > Network & Internet > Mobile network > Advanced > scroll all the way down to Access Point Names and compare to your network provider's recommendations?

Did you try with an other SIM?

***
[Samsung Galaxy S 5 Unified Development] digital mystik:
I'm not by my phone right now but will check tomorrow and let you know. The sim is only a couple months old as well.

I found this thread which seems promising for root, and it's fairly recent: https://xdaforums.com/verizon-galaxy-s5/development/vzw-emmc-15-chipset-onlyroot-bootloader-t4009089
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Thanks for your guidance

Fixed issue with dark mode
[Samsung Galaxy S 5 Unified Development] digital mystik:
I fixed it!! I used this thread to get back to stock-ish:

https://xdaforums.com/verizon-galaxy-s5/development/vzw-emmc-15-chipset-onlyroot-bootloader-t4009089

and used your super clean install guide as well just to start fresh. I backed up the working efs this time too haha.
[Samsung Galaxy S 5 Unified Development] Boatshow:
This has been bothering me for a while and afaik it's in all AOSPs.

You tap the power button -> You go to a screen that says "Swipe up to unlock"

You can disable this with a LineageOS setting, fair enough. Let's disable this.

You tap the power button -> You go directly to password entry

Except the password entry screen wastes screen estate. It hides your status bar and all your notifications. You can't even tell the time. Now you have to press the back button to see the time.

It wasn't like this in older Androids so someone intentionally make the lockscreen worse. I can understand why nobody cares, most people use fingerprint sensors now. Look at this, it's literally a waste of screen estate:

https://img.gadgethacks.com/img/81/...r-secure-with-pin-changes-with-time.w1456.jpg
[Samsung Galaxy S 5 Unified Development] m4v3r0ne:
Hey, just wanted to say thanks for the work!

I used LOS16 on my S3 (ChronoMonoChrome's new version is awesome!) for a long time and finally got my hands on a newer S5.

Trying the official 16 nightly for now and it feels SO nice on this device. No troubles so far. Missing a couple customization features that another ROM provided (crDroid) but meh, can't have everything, right? ;)

Will report back any errors and again THANKS THANKS THANKS, you guys rock! <3
[Samsung Galaxy S 5 Unified Development] rootkitty:
Question about updating / Google Play Download Problem

Let me start with a quick thanks to the Devs on this fantastic ROM..... been using it since December and for me the phone is better than new!

Sorry for the Nooby questions, but I just want to make sure I get things right:

I initially flashed LOS 16.0-20191218-NIGHTLY-klte / open_gapps-arm-9.0-pico20191217 / Magisk-v20.1, and then later I updated to 16.0-20200123-NIGHTLY-klte by clearing the cache and flashing the zip. I also update Magisk to v20.3 using Magisk Manager.

I recently noticed that Google Play won't download updates... just says Downloading...., but nothing happens.

I noticed the March security patches drop tomorrow, so I thought I would wait one or two days, Flash that update, and and updated open_gapps-arm-9.0-pico.

Am I correct that all I need to do is boot into TWRP (take nandroid backup) clear the cache and flash LOS16 nightly followed by the new open_gapps-arm-9.0-pico, and then reboot?

Does this wipe Magisk? Do I have to reinstall Magisk?

Has anyone solved the Google Play download issue?

Any help much appreciated.
[Samsung Galaxy S 5 Unified Development] odoll:
I'd follow this order:

DL recent LOS, GApps, Magisk.

Boot into Recovery (TWRP) and make a Nandroid backup (just to be safe)

(You could flash over the existing system, but I'd wipe the system partition first)

Flash 1st LOS and 2nd GApps

Clear Dalvik and Cache

Boot into System and let it settle

Reboot into TWRP and finally flash Magisk.

(Wipe Cache/Dalvik)

Reboot into System
[Samsung Galaxy S 5 Unified Development] curiousrom:
Android Bump Security String to 2020-03-05

FYI the monthly Android security patch Bump Security String to 2020-03-05 was merged & is included in LineageOS 16.0 for the S5 klte + variants build 2020-03-09 or newer as you can see in the klte changelog: https://download.lineageos.org/klte/changes/

See Android Security Bulletin—March 2020 for details about the security fixes.

I updated to LineageOS 2020-03-09 via the built-in LineageOS OTA Updater a Galaxy S5 G900M LineageOS 16.0 klte running build 2020-03-01 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind & everything went smoothly as usual.

After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version 9 > Android security patch level: March 5, 2020.

View attachment 4967341 View attachment 4967343

The Vendor security patch level remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

BTW even if does not show up in the changelog for klte Update Chromium Webview to 80.0.3987.132 which is used by the stock Browser & many other browsers & apps is also included in the update.

You can check the LineageOS Webview version (com.android.webview) in > Settings > Apps & notifications > 3-dots > Show System > Android System WebView or > Developer options > WebView implementation.

In that WebView implementation you can choose which WebView you want LineageOS to use by default if you installed more than one.

As you can see in the screenshot I installed Google's Chrome browser & it added an extra Webview option.

View attachment 4967375

Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :good::cool:

***

When To Update?

Just because the LineageOS automated builder is churning out nightly builds for 16.0 @ the present it's not a reason to update daily. Look in the changelog for your device to see if updating is worth the trouble.

Especially with many LineageOS devs working on the upcoming 17.1 the number of changes applicable to 16.0 have dropped dramatically.

LineageOS Updater > 3-dots > Preferences where you can set the Auto updates check to Never, Once a day, Once a week or Once a month.

You could choose Never & check manually once in a while.

BTW you can create a direct link to Updater & much more like to Privacy Guard Advanced for example with the LineageOS Settings widget.

After the upcoming LineageOS 17.1 is launched (don't ask for an ETA please), the 16.0 automated build schedule will be changed to once a week only and 17.1 set to daily builds because new LineageOS versions often have bugs or new devices being added to the roster so several patches may be merged daily like it was the case when 16.0 got launched.

***
[Samsung Galaxy S 5 Unified Development] kurtn:
My preferred tool for updating is built in updater. Settings > system > advanced. Magisk and GApps survive those updates.
[Samsung Galaxy S 5 Unified Development] odoll:
Correct, but as the OP wanted to overcome an "GApps" issue wiping the system partition and flashing clean LOS, GApps and Magisk once might be the better option. If everything works fine then s/he could indeed continue with the updater more easily ...
[Samsung Galaxy S 5 Unified Development] rootkitty:
That would be good if I can do that... how do I then update gapps? Is it OK to flash after doing an OTA update once that update has settled?

---------- Post added at 03:56 AM ---------- Previous post was at 03:46 AM ----------

Sorry for the Nooby question, but does wiping the system partition clear out messages, contacts, etc. or are they safe?
[Samsung Galaxy S 5 Unified Development] odoll:
Yes, you can flash GApps once again after an OTA LOS update. But the Q is, if a screwed system will be fixed by that.

no (but in any case you should have a Nandroid backup)
[Samsung Galaxy S 5 Unified Development] kurtn:
Normally you don't need to update GApps. Let just play store do the work.
[Samsung Galaxy S 5 Unified Development] cartman02au:
Same issue here - lineage-16.0-20200309-nightly-kltedv-signed.zip on G900ITEL1CQJ2
[Samsung Galaxy S 5 Unified Development] fitittome:
I saw changes recently that could cause this. Submit a bug report to make the dev aware.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Failed to Boot S5 SM-G900I kltedv

The post you quoted is about an old 2019-03-02 build so how can you say that you have the "same" issue? :confused:

The bug in build 2019-03-02 was fixed & that build was removed from the LineageOS servers.

You don't give any setup description, don't say how you installed it exactly & if you flashed anything else besides LineageOS which makes it impossible to troubleshoot.

You have a S5 SM-G900I, right?

Try a S5 LineageOS Super Clean Install including Format Data (not wipe) + wiping System, Dalvik / Art cache & Cache.

Some users, including me, reported fail to boot if you select install the TWRP app when asked in TWRP. That app is fluff, wants to start at boot, run in the background, collect data & is not necessary anyway because the TWRP updates are not frequent & it's easy enough to update manually.

So go to TWRP > Settings > General and disable: Prompt to install TWRP app if not installed.

***

Just curious: which changes exactly? Links?

***
[Samsung Galaxy S 5 Unified Development] rootkitty:
I just noticed that my Google Playstore was 17.9.17 -- IIUC that's very old. How would I update Google Play Store?

I tried installing YALP store, but it couldn't log in, and I was reading something about the Aurora store causing your Google account to get banned. Where is the best place for someone who is new to this community to find out about alternative app stores.
[Samsung Galaxy S 5 Unified Development] kurtn:
The main question: do you want to stay with GApps or get away from proprietary Google apps?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Google Play Store Problems & Open GApps

On my Galaxy S5 G900M LineageOS 16.0 klte build 2020-03-09 + Open GApps Pico 2020-01-27 + LineageOS AddonSU: Play Store (com.android.vending) version 19.1.47.

Play Store should update itself if you logged in with a Gmail account but it may take a while & not be instantly updated.

Try this if you have update or download problems: long press the Play Store's icon > i > app info > Storage > Clear storage & reboot to reset it.

Which Open GApps package did you install exactly? Edit: open_gapps-arm-9.0-pico20191217 from a previous post.

***

You could download the most recent build of the exact same Open GApps package & dirty flash it after wiping only the caches.

Going to https://opengapps.org/ select the package then all the way down you can click on Version information to see the versions of the apps it includes.

In today's open_gapps-arm-9.0-pico-20200310.versionlog.txt I can see for Play Store: com.android.vending 19.1.52-all.

Edit: I still have open_gapps-arm-9.0-pico-20200127.versionlog.txt and in it I can read com.android.vending 18.5.59-all so Play Store did update itself to my current version 19.1.47. I am also attaching that file for those who may be interested.

While this is not necessary normally as the apps should updated themselves including Play Store that may solve your problems if clearing Storage does not work for some reasons.

If you do that Open GApps will create a open_gapps_log.txt in the same folder as the Open GApps...zip you flashed with TWRP.

If you use Sideload, open_gapps_log.txt will be created in /data/media/0/ a.k.a the internal sdcard. That's a new Open GApps feature.

I attached the installation log that Open GApps automatically created when I sideloaded open_gapps-arm-9.0-pico-20200127.zip.

It also creates a larger open_gapps_debug_logs.tar.gz in the same location that must be unpacked twice if you want to see the files inside: ....tar.gz > …..tar > normal folder.

***
[Samsung Galaxy S 5 Unified Development] rootkitty:
Thanks....

If Google Play does updates, does it overwrite Open Gapps and replace it with it's own spyware? I'm wondering if I am better to not worry about Google Play at all since I am concerned about keeping my data as private as possible. Unfortunately I use and want to continue to use Waze, so I'm stuck with some Google stuff. I wish there was a reasonable way to put all that stuff on ice so it's only collecting data when I am using Waze. I wish we could "dockerize" android apps and still run them... keep them all isolated and let them only have the minimum they need to do what we want them to do.... This business of stealing contacts/sms etc. is complete BS.

Can someone tell me what this is about (appears at the top of the page on the web site):

Disclaimer :

Using Aurora Store with your own Google account may cause your account

to be blacklisted, use at your own risk.

Thanks...