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

[Panzerknakker]

The overall experience is great, thanks for the great work!
I have two issues:
The phone doesn't boot when switched of and the charging symbol is visible. The power button just dosen't have any effect.

- To boot from charging press volumedown + powerbutton and wait.

 

[Schlodty]

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]

- 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

 

[Andrea224]

Hi to all, since @hennymcc has skipped to LOS15 and @ayke isn't updating the rom for a while, I ended up building a december update.
It's only a repo sync, so I don't know what are the changes (if there are), apart from the LOS changes.
LOS-14.1-2017/12/11 - https://drive.google.com/open?id=1PghFY3mkZOMDPLN4rKJQY_EjojwhwYHM

 

[a-dead-trousers]

Hi to all, since @hennymcc has skipped to LOS15 and @ayke isn't updating the rom for a while, I ended up building a december update.
It's only a repo sync, so I don't know what are the changes (if there are), apart from the LOS changes.
LOS-14.1-2017/12/11 - https://drive.google.com/open?id=1PghFY3mkZOMDPLN4rKJQY_EjojwhwYHM

hi, thanks.
What is the ASB level? November or is it already December?

 

[starbright_]

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?

 

[Andrea224]

hi, thanks.
What is the ASB level? November or is it already December?

Tbh idk, but it should be december.

 

[Andi46]

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:

 

[starbright_]

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

 

[jagdish.m.k]

S5

 

[a-dead-trousers]

Tbh idk, but it should be december.

Can you verify it in settings > about? What security patch level do you see?

 

[Panzerknakker]

Can you verify it in settings > about? What security patch level do you see?

Versions dated from 11.12. are level 5.12.
You can check this here https://www.cmxlog.com/14.1/klteduos/.
Just neglect the klteduos stuff (marked with red stars).

 

[Andrea224]

Can you verify it in settings > about? What security patch level do you see?

Atm I don't have it installed on my S5 mini.

Edit: Yes, it has december security patch.

 

[zpk787]

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]

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.

 

[starbright_]

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]

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_]

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?

 

[starbright_]

I asked in another forum for other ROM - the issue is the same. I have an idea why it loses calibration - it can't save calibration file.
Maybe due to permissions or because the handling with sdcard / data has been changed since its original release.
Look here: A log with qstiles.
https://www.android-hilfe.de/forum/...ta-2-11-2017.819907-page-9.html#post-10810778

 

[Andi46]

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 :

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:

[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]