[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]

[starbright_]

I rooted the installation and installed AntuTu CPU Master. This shows indeed that the kernel scales the CPU interactively from 400 to 1400 MHZ, so my assumption was wrong. I now forced it to 400MHZ, effectively not doing any interactive CPU scaling at all. I will see how this works out with regards to power drain.

Thank you.

With moderate/low usage it can last 3 or 4 days (flight mode at night). If you have bad reception (weak signal) it can go down to 24 hours. Check your signal. Here it happens that it jumps between 3 station and always sends with full power - this drains battery.
You can also give BetterBatterStat (BBS) a chance to find out which app might prevent the device from sleeping (wakelocks).

Cheers and thanks to all the devs. The only I miss is the compass which loses calibration ....

 

[ChrisP]

Which theme are you using? It looks great!

Swift Dark Substratum Theme:
https://play.google.com/store/apps/details?id=com.brit.swiftdark.substratum

Gesendet von meinem SM-G800F mit Tapatalk

 

[Lord Ossor]

With moderate/low usage it can last 3 or 4 days (flight mode at night). If you have bad reception (weak signal) it can go down to 24 hours. Check your signal. Here it happens that it jumps between 3 station and always sends with full power - this drains battery.
You can also give BetterBatterStat (BBS) a chance to find out which app might prevent the device from sleeping (wakelocks).

Cheers and thanks to all the devs. The only I miss is the compass which loses calibration ....

This morning I had a loss of almost 10% power during an hour and the phone wasn't used. It turned out the mediaserver process run at 100% CPU. Now I assume the mediaserver process does some kind of indexing for pictures and other media files, correct? Is it right to assume that it should no longer torture the CPU once it has done it's inital indexing? For now I killed it.

 

[a-dead-trousers]

This morning I had a loss of almost 10% power during an hour and the phone wasn't used. It turned out the mediaserver process run at 100% CPU. Now I assume the mediaserver process does some kind of indexing for pictures and other media files, correct? Is it right to assume that it should no longer torture the CPU once it has done it's inital indexing? For now I killed it.

Nope.
The mediaserver governs the access to the camera amongst others. Most of the time if the mediaserver process runs amok that means something is wrong with the camera app you are using. This was a huge problem at the beginning of the development of this ROM. As far as I know Google Camera 2.7.010 should fix this. Other solutions include uninstalling/freezing the stock camera and using alternatives like OpenCamera. In the worst case scenario when nothing else helps you need to use a mediaserver killer app (requires root) to stop the process after you're done using your camera.

 

[Wonzentjue]

Hello -after updating to latest lineage-14.1-20170819-UNOFFICIAL-kminilte.zip version, I now have a Problem with my SD Card. Former the sdcard was listed under storage /21E7-1808/... - it is now listed under mnt/media_rw/21E7-1808.
The System shows an sdcard1 and I can browse this with the system.
Using Total Commander - the external SDCard is listed as sdcard1 under /mnt/media_rw/21E7-1808 and I can browse the data. Knowing this, I can find my external sdcard also using rootexplorer at location /mnt/media_rw/21E7-1808
Looking at the folder mnt, there is also another entry sdcard this pointing to /storage/self/primary and this shows my internal storage

Now what is the problem - using the following App
ES-explorer
I do see only sdcard and I see my internal storage there.
There is an entry for media_rw but with a question mark -rw instead of drw in the date column there is N/A
App folder sync
As the location of the externals storage sdcard moved, I must change all my folder settings.
But it does not work anymore
I can activate root access - but not activate "access to external storage in the setting" - hence
when I try to access it, the folder /mnt does not have an entry media_rw
Can anyone help - with folder sync I backup all my data.
Many thanks in advance

This is a bug that happens to me every time I flash a new version of this rom - the name of the sd-card changes. For me this has never been a problem. (And don't use ES-File explorer, it's spyware and full of crappy features no one needs) Unfortunately I can't help you with this, you'll have to mount the sdcard every time you update.

 

[Kenarude]

Hello,
First I would like to THANKS all devs for the great work done, as well as people who help on the forum.
I use the hennymcc rom (02/06/2017) for a while and it works very well all the time, it has given new life to my s5 mini!!

One minor problem that could be improved is the fingerprint sensor (problem raised a few times in the thread but does not seem to be solved).
Sometimes the fingerprint is not responding when I want to unlock my phone. I use a flip cover case and I activated the option.
The problem does not occurs every time, it seems to happen after a long period of inactivity.
This problem was not present on stock ROM (4.4.2 - 5.0.1 - 6.0.1).

I was able to recover the log when the fingerprint sensor is not working

09-08 07:55:40.533  2365  2365 I SystemServiceManager: Starting com.android.server.fingerprint.FingerprintService
09-08 07:56:06.790  2365  2404 E ActivityManager:   0% 2075/fingerprintd: 0% user + 0% kernel / faults: 30 minor 1 major
09-08 07:56:16.635  2365  2404 I ActivityManager: Start proc 3064:com.validity.fingerprint/1000 for added application com.validity.fingerprint
09-08 07:56:16.997  3064  3064 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1357 android.content.ContextWrapper.startService:613 com.validity.fingerprint.ValidityServiceStarter.onCreate:33 android.app.Instrumentation.callApplicationOnCreate:1025 android.app.ActivityThread.handleBindApplication:5448 
09-08 11:54:41.921  2075  2075 V fingerprintd: stopAuthentication()
09-08 11:57:02.561  2075  2075 V fingerprintd: stopAuthentication()
09-08 11:57:05.574  2075  2075 V fingerprintd: authenticate(sid=0, gid=0)

and the log when it is working

09-05 08:36:19.703  2068  2068 V fingerprintd: stopAuthentication()
09-05 08:36:22.709  2068  2068 V fingerprintd: authenticate(sid=0, gid=0)
09-05 14:06:53.977  2068  2068 V fingerprintd: stopAuthentication()
09-05 14:08:48.874  2068  2068 V fingerprintd: stopAuthentication()
09-05 14:08:52.929  2068  2068 V fingerprintd: authenticate(sid=0, gid=0)
09-05 14:21:44.348  2068  2068 V fingerprintd: stopAuthentication()
09-05 14:21:47.874  2068  2068 V fingerprintd: stopAuthentication()
09-05 14:21:50.889  2068  2068 V fingerprintd: authenticate(sid=0, gid=0)
09-05 14:22:09.090  2068  2475 D fingerprintd: onAcquired(0)
09-05 14:22:09.090  2068  2475 D fingerprintd: onAuthenticated(fid=1, gid=0)
09-05 14:22:11.045  2068  2068 V fingerprintd: authenticate(sid=0, gid=0)

Hope this can help.
Thank you.

 

[xianhu]

Any update on the call forwarding problem? (setting up call fwd not possible, phone disconnects from network).

 

[Andrea224]

@hennymcc What's about Oreo? Is in your plans to update the S5 Mini to Android Oreo?

 

[a-dead-trousers]

@hennymcc What's about Oreo? Is in your plans to update the S5 Mini to Android Oreo?

At first LineageOS has to do the transition to Oreo (v15.0).

 

[StanleyNL]

At first LineageOS has to do the transition to Oreo (v15.0).

LineageOS already has a few working (unofficial) Oreo builds as far as I know. Source: https://www.xda-developers.com/list-android-oreo-unofficial-ports/

 

[StanleyNL]

LineageOS already has a few working (unofficial) Oreo builds as far as I know. Source: https://www.xda-developers.com/list-android-oreo-unofficial-ports/

It's kinda funny but right before I posted this (6 hours ago), henny started working on LAOS15.0 https://github.com/cm-3470/android_device_samsung_smdk3470-common

 

[Andrea224]

It's kinda funny but right after I posted this (6 hours ago), henny started "working" on LAOS15.0 ? https://github.com/cm-3470/android_device_samsung_smdk3470-common

Yeah, really funny, who knows if it's a coincidence or not. Anyway, good to know.

 

[eriksson25]

HI, Have a G800F with newflashed lineage-14.1-20170819-UNOFFICIAL-kminilte
And open_gapps-arm-7.1-micro-20170910

I formated everything before flash with latest twarp. But I get instant wizzard crash after boot, before any Language settings or similar. So I can not scroll down and activate Wifi. Any tipps?

 

[maddis_android]

u probably need a newer twrp version. i had the same issue and after flashing twrp 3.1.1-1 everything worked fine.

rgds mad

 

[Swellhead]

u probably need a newer twrp version. i had the same issue and after flashing twrp 3.1.1-1 everything worked fine.

rgds mad

Hy there -
I had TWRP 3.0.0 installed and got multiple errors with GAPPs after updating to lineage-14.1-20170819-UNOFFICIAL-kminilte.zip
Today I installed I did install TWRP 3.1.1-1 and reflashed above image and superuser. Normal System boot worked ok.
Then I rebooted and flashed open gapps nano.
Sytem rebooted and I can work with Google Apps - the only problem remaining is, that google play store app often is closed.
reopening the app works though.

 

[Oleggluk]

Official firmware updates are coming from the Samsung 6.0.1 (G800FXXU1CQH2) https://www.sammobile.com/firmwares/galaxy-s5-mini/SM-G800F/. Is there any difference on which firmware version is Los made?
And what file or library is responsible for the light sensor? It is possible to fix the highlighting in the bright sun after a dark room.

 

[Mildars]

Hello, please help. I have installed this rom (build 19/08/2017) and gapps (open_gapps-arm-7.1-micro-20170909). When i start up my phone, i get notification about gapps crash. Previous build of LOS was OK. Thx for any response

 

[Danko Jones]

Official firmware updates are coming from the Samsung 6.0.1 (G800FXXU1CQH2) https://www.sammobile.com/firmwares/galaxy-s5-mini/SM-G800F/. Is there any difference on which firmware version is Los made?
And what file or library is responsible for the light sensor? It is possible to fix the highlighting in the bright sun after a dark room.

It seems Samsung has fixed the light sensor in stock rom. I didn't tested it by myself.
https://xdaforums.com/showpost.php?p=73703317&postcount=20

 

[Pat750]

Hello, please help. I have installed this rom (build 19/08/2017) and gapps (open_gapps-arm-7.1-micro-20170909). When i start up my phone, i get notification about gapps crash. Previous build of LOS was OK. Thx for any response

Do you use latest TWRP 3.1.1-1? If not you can find it in original development.

 

[C0rn3j]

Could you please up the patch level to Sep 5 to fix the bluetooth exploits? ^^