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

Search This thread

Schlodty

New member
Sep 16, 2015
4
2
First of all: thanks all the developers for their work!

I just flashed lineage-14.1-20171130_090248-UNOFFICIAL-kminilte together with open_gapps-arm-7.1-mini-20171202 and most things work perfectly. But still I have two issues:

- I can not calibrate the magnetometer. I use the app "GPS status & toolbox" for that. I turn the phone but nothing happens. Compass calibration stays "red". Also magnetic field measurement length stays at 1120 uT, which is far too much. Anybody any idea?
- I can not turn on NFC. If I reboot it works. But after a while, when I try to turn on NFC the button gets greyed out. Same if I use status bar. Any idea or workaround?

Thank you!
 

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
- I can not calibrate the magnetometer. I use the app "GPS status & toolbox" for that. I turn the phone but nothing happens. Compass calibration stays "red". Also magnetic field measurement length stays at 1120 uT, which is far too much. Anybody any idea?
I'm using the same app but calibrating the compass is functioning over here. but it looses it after a reboot... sometimes you have to turn it slowly some more in each axis as mentioned
 

Attachments

  • Screenshot_20171211-133320.png
    Screenshot_20171211-133320.png
    123.3 KB · Views: 221
Last edited:

a-dead-trousers

Senior Member
Jul 28, 2016
271
135

starbright_

Senior Member
Apr 11, 2010
1,271
206
I'm using the same app but calibrating the compass is functioning over here. but it looses it after a reboot... sometimes you have to turn it slowly some more in each axis as mentioned
Have same problems. Sometimes calibration works, sometimes not.
Compared to my previous devices the update (rotation speed of needle) is very slow. Frankly speaking - can't imagine why.
I also use another tool :
AndroiTS GPS Test

Currently I have here two S5Mini which behave different i terms of GPS quality. One doesn't show Glonass, the other does. But even that one never uses this sats for location. Shouldn't it support that? What are your observations?
 

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
Currently I have here two S5Mini which behave different i terms of GPS quality. One doesn't show Glonass, the other does. But even that one never uses this sats for location. Shouldn't it support that? What are your observations?
EDIT: ...wrote some junk... :angel:
 
Last edited:

starbright_

Senior Member
Apr 11, 2010
1,271
206
GLONASS is a russian operated and financed navi system by the Ministry of Defense of the Russian Federation.... so we'll never be able to use their sats.

That doesn't explain the sats are shown in one device but not at another. This is strange. Either are used differnet GPS modules or it is defined by some firmware (baseband, build.prop.... ?!?)
Also GSM arena shows (not sure how reliable this is) that S5 mini has: GPS: Yes, with A-GPS, GLONASS

https://developer.sonymobile.com/knowledge-base/technologies/glonass/
https://www.pcwelt.de/tipps/GPS-Genauigkeit-mit-Glonass-erhoehen-9023102.html
 
Last edited:
  • Like
Reactions: Andi46

zpk787

Member
Oct 16, 2017
25
3
Hi!
If you're interessted in a more detailed overview which app affects the battery life you could use BetterBatteryStats.
That way I found out that the radio/wifi sometimes runs riot ("No data connection" for 100% of the time) which drains the battery just a little bit more than usual. A reboot helps to fix this problem.
wkr ADT
Thank you. I'm trying it now, I usually use GSam Battery monitor for real-time monitoring. One thing I noticed is that two nights that it consumed zero % the phone was lying close to a window. And other times it was deeper in the room (and consumed 3-4%). This might just be a coincidence though. For now I disabled "cellbroadcastreceiver" app, it's the one that bombards you with SMS about bad weather in your area. Even though I disabled receiving those SMS in the dialer app, I fell like it might still try to receive some sort of signal from the network. I also flashed the latest baseband, I'll see how that goes, then I'll try the baseband from the stock firmware I used. I don't really know how basebands work though (like what happens when you take a modem.bin from stock firmware and flash it over AOSP rom. Well, I already did it anyway, but I have a backup).
 

Schlodty

New member
Sep 16, 2015
4
2
Have same problems. Sometimes calibration works, sometimes not.
Compared to my previous devices the update (rotation speed of needle) is very slow. Frankly speaking - can't imagine why.

Thanks to Andi46's comment I tried again to calibrate the compass turning the mobile more times than mentioned: It works, but I had to turn it about 20 times in each axis to get it "green". Also the rotation speed of the compass is very, very slow for me, which makes it useless for navigation in a car. When turning it by 90 degrees, the compass needs about 20 seconds to reach the new orientation.
 
  • Like
Reactions: regimail and Andi46

starbright_

Senior Member
Apr 11, 2010
1,271
206
Thanks to Andi46's comment I tried again to calibrate the compass turning the mobile more times than mentioned: It works, but I had to turn it about 20 times in each axis to get it "green". Also the rotation speed of the compass is very, very slow for me, which makes it useless for navigation in a car. When turning it by 90 degrees, the compass needs about 20 seconds to reach the new orientation.

Is it same in stock ROM? Don't have an idea why it is so slow. Usually access to this kind of data is via I2C or SPI - fast. And I can't imagine that the magnetic sensor needs this time.... Maybe they do some heavy averaging?
 

Schlodty

New member
Sep 16, 2015
4
2
Is it same in stock ROM? Don't have an idea why it is so slow. Usually access to this kind of data is via I2C or SPI - fast. And I can't imagine that the magnetic sensor needs this time.... Maybe they do some heavy averaging?

No, in stock ROM, the calibration works using 3 turns around each axis. And it is also not slow. In LOS, I turned off averaging in the app (GPS status), but the behaviour is still the same.
 

starbright_

Senior Member
Apr 11, 2010
1,271
206
No, in stock ROM, the calibration works using 3 turns around each axis. And it is also not slow. In LOS, I turned off averaging in the app (GPS status), but the behaviour is still the same.

So it is in fact a matter of LOS ?!? Mh, question is: who can check this ? Are other LOS device affected to or is it just ours?
 

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
Regarding the GPS/Compass issue + still an avc:denied timestamp

i created a logcat from the calibration process. when i looked into it and searched for GPS related timestamps i found :
Code:
12-14 21:27:34.243  2356  2444 V MPL-storeload: inv_get_mpl state size = 6040
12-14 21:27:34.244  2356  2444 V MPL-storeload: calData from inv_save_mpl_states, size=2
12-14 21:27:34.244  2356  2444 V MPL-storeload: cal data size to write = 6040
12-14 21:27:34.247  2356  2444 V MPL-storeload: Bytes written = 6040
12-14 21:27:34.250  2356  2444 V MPL-storeload: inv_get_mpl state size = 6040
12-14 21:27:34.250  2356  2444 V MPL-storeload: calData from inv_save_mpl_states, size=2
12-14 21:27:34.250  2356  2444 V MPL-storeload: cal data size to write = 6040
12-14 21:27:34.250  2356  2444 V MPL-storeload: Bytes written = 6040
12-14 21:27:34.251  2356  2444 D ALPS    : save ALPS calibration file.
[B]12-14 21:27:34.251  2356  2444 E ALPS    : Couldn't open ALPS calibration file.[/B]
12-14 21:27:34.303  2069  2832 I AudioHardwareTinyALSA: setParameters(screen_state=off)
12-14 21:27:34.436  2356  9171 I GnssLocationProvider: WakeLock acquired by sendMessage(3, 0, [email protected]583)
12-14 21:27:34.444  2356  2382 I GnssLocationProvider: WakeLock released by handleMessage(3, 0, [email protected]583)[/B]
@hennymcc or any other dev/user with more knowledge- can you please have a look at the log and eventually we'll be able to gain a fully functional Navi without always having to recalibrate the compass like we've had in previous devices?

BTW: with the compass calibrated : the needle reacts fast in Sygic navi app (att. pic), with GPS status a bit slowlier and in AndroiTS GPS bad/slowly. :fingers-crossed:

i've also still seen an avc:denied ts in the log, hopefully @mirhciulica again finds some time for the denial :fingers-crossed:
Code:
[B]12-14 21:30:01.583 20173 20173 W busybox : type=1400 audit(0.0:727): avc: denied { setattr } for name="scaling_governor" dev="sysfs" ino=10123 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs_devices_system_cpu:s0 tclass=file permissive=0[/B]
 

Attachments

  • logcat.rar
    50.9 KB · Views: 4
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    This is a LineageOS 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).

    DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE

    Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
    Hence please do not ask for support or ROMs for the G800H.

    Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.

    Working features
    • HW accelerated GUI
    • Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
    • MTP storage
    • Flash Light
    • Bluetooth (A2DP, HFP, HID)
    • IR
    • Sound
    • SMS
    • Initiate and receive calls
    • Wifi
    • Mobile Data
    • USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
    • NFC
    • Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
    • Light sensor (needed for auto-brightness)
    • Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
    • SD-Card as internal storage (new Android M feature)
    • GPS
    • Fingerprint scanner
    • SELinux

    Non-working features:

    Known issues:
    • Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
    • See the Bug Report section of this thread.

    Disclaimer:
    • You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
    • Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
    • Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
    • The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
    • It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
    • Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
    • Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
    Before you start:
    • Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.

    Download:

    Install recovery:
    • Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
    • Confirm the following warning message with the Volume-Up button.
    • Connect your device to your PC via USB
    • Make sure the device driver's are installed on your PC
    • Start Odin
    • In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
    • Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
    • Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
    • After the recovery flashing process was successful, power of your device, wait a few seconds and reboot into recovery mode (see instructions below).
    • Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.

    Before you flash:
    • You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
    • Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.

    Flash ROM:
    • Reboot into recovery mode (Press Volume-Up + Home + Power button)
    • If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
    • If you haven't copied the installation files yet, you can now copy the GApps and the ROM zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
    • Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
    • Install the CM ROM zip-package
    • Install the GApps zip-package

    How to root:
    LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
    After that root access is still disabled by default. If you want to activate root access for apps, do the following:
    • Open the Settings menu, select "About Phone"
    • Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
    • Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.

    In case you want to go back to the stock ROM:
    • lf you do not have the latest ROM for the G800F you can download it from SamMobile
    • Reboot your phone into Odin mode
    • Open Odin on your PC and connect your smartphone with your PC via USB
    • If you have a zip-file unzip it so that you have a .tar.md5 file
    • In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
    • Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
    • Reboot

    Changelog
    Code:
    Changelog:
    19/08/2017:
    * SELinux policy update
    * Update to newest LineageOS sources
    02/06/2017:
    * Firefox crash&reboot fixed (thanks to Spookcity)
    * Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
    * Ambient display option added (disabled by default)
    28/05/2017:
    * [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
    
    20/02/2017:
    * Fixed Youtube scaling issue on window resizing
    * Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    * cpufreq config added
    * Charge mode fixed (starts when plugging USB into a powered-off phone)
    * USB-Tethering and Wifi SoftAP (Hotspot) fixed
    * Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    * Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    
    01/02/2017:
    * conversion to LineageOS
    * updated some libs with stock MM versions
    * fixed robotic voice problem
    * fixed silence on first call
    
    07/11/2016:
    * Initial test build

    This section is for developers:
    A README file with build instructions can be found here:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte

    Sources:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte
    https://github.com/cm-3470/android_vendor_samsung_kminilte
    https://github.com/cm-3470/android_kernel_samsung_kminilte
    https://github.com/cm-3470/android_device_samsung_smdk3470-common

    Developers welcome
    • At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
    • Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
    • Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.

    Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.

    XDA:DevDB Information
    [G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini

    Contributors
    hennymcc, Panzerknakker, spookcity138, psyafter, ayke
    Source Code: https://github.com/cm-3470

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
    Based On: LineageOS

    Version Information
    Status: Beta

    Created 2017-02-01
    Last Updated 2018-08-18
    21
    Hi there is a new build:
    https://www.androidfilehost.com/?fid=529152257862704787

    Changelog:
    • Fixed Youtube scaling issue on window resizing
    • Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    • cpufreq config added
    • Charge mode fixed (starts when plugging USB into a powered-off phone)
    • USB-Tethering and Wifi SoftAP (Hotspot) fixed
    • Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    • Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    21
    Official TWRP 3.1.1

    I've worked together with the TWRP maintainers to make TWRP official, and it's finally here :D
    https://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-1-1-exynos-t3626646

    You can download it from here:
    https://twrp.me/devices/samsunggalaxys5miniexynos.html
    21
    A new build is available:
    https://www.androidfilehost.com/?fid=961840155545570720

    It turned out that the patch found by Spookcity not only fixes Firefox but also the fingerprint bootloop. So the new build should be usable again.
    As the initial bootloops probably were also caused by the fingerprints it should not be necessary anymore to wipe everything (although still recommended).

    Changes:
    • Firefox crash&reboot fixed
    • Enabling the fingerprint reader does not cause bootloops anymore
    • Ambient display option added (disabled by default)
    17
    A new build is available.
    https://www.androidfilehost.com/?fid=889764386195902448

    Changelog:
    Code:
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone