It actually doesn't, sadly. It still wakes up if there's a magnet nearby the phone.
[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]
- Thread starter hennymcc
- Start date
You wrote disable in settings, what I mean is freeze (with TitaniumBackup e.g.)
After looking at the logs you have uploaded, I have the impression there might be a denial that's not audited at all or some sort of other file reading error from /efs/*. The denials present in your logs for appending to /efs/nv.log, could be a strong indication that rild is failing to start due to some other error and it tries to log that in the respective file.
@skysurfer1111, I have prepared a debug build @ https://www.androidfilehost.com/?fid=817550096634783242, that has permissive SELinux and disabled dontaudit rules. I would need new logs from that build and the /efs/nv.log file, if it exists (I think you can copy it easily with TWRP to phone memory if you don't have su binary installed).
Note for everyone, this build is only for debugging of the sim card issues. You should not install it if you don't have this kind of issues on your device.
Yeah, freezing and disabling is actually the same, but still not working - I also tried Titanium Backup
Note for everyone, this build is only for debugging of the sim card issues. You should not install it if you don't have this kind of issues on your device.[/QUOTE]
I always had the SIM card issue with the former builds and solved it with the kernel of spookcity. My device runs on baseband: DRE-G800FXXU1CQB1 the baseband QE1
@mirciulica: With your ROM and the implemented Kernel from 2nd of july the SELinux state ist "moderate" and the SIM card is also found! The first hour it seems to work without problems.
Thank all developers for the energy they put in this ROM, the kernels and basebands :good:
EDIT: Log- files copied from TWRP
I always had the SIM card issue with the former builds and solved it with the kernel of spookcity. My device runs on baseband: DRE-G800FXXU1CQB1 the baseband QE1
@mirciulica: With your ROM and the implemented Kernel from 2nd of july the SELinux state ist "moderate" and the SIM card is also found! The first hour it seems to work without problems.
Thank all developers for the energy they put in this ROM, the kernels and basebands :good:
EDIT: Log- files copied from TWRP
Last edited:
Spookcity's Kernel
This ROM is great and it does keep my S5Mini perfectly adequate to use as my primary phone. Thank you all.
In the last few pages, you are mentioning Spookcity's kernel a lot. Plus I just noticed he had bumped it to 2.0. And I did read the thread there, but I don't understand most of it to be honest.
I know what a kernel (as in linux kernel) is, but should I care about it in relation to LineageOS 14.1?
As a regular user, I am more concerned in battery life as opposed to performance, so the fact it overclocks the GPU and CPU should probably keep me off, right?
Can somebody put a few words here (or point me to where it is better explained) - should I change the kernel and why? What are the benefits? What are the known issues?
Thanks in advance!
This ROM is great and it does keep my S5Mini perfectly adequate to use as my primary phone. Thank you all.
In the last few pages, you are mentioning Spookcity's kernel a lot. Plus I just noticed he had bumped it to 2.0. And I did read the thread there, but I don't understand most of it to be honest.
I know what a kernel (as in linux kernel) is, but should I care about it in relation to LineageOS 14.1?
As a regular user, I am more concerned in battery life as opposed to performance, so the fact it overclocks the GPU and CPU should probably keep me off, right?
Can somebody put a few words here (or point me to where it is better explained) - should I change the kernel and why? What are the benefits? What are the known issues?
Thanks in advance!
@hennymcc Could you please add Android N File Based Encryption (FBE) to this rom?
This is the guide by Google:
Enabling file-based encryption
FBE is enabled by adding the flag fileencryption with no parameters to the fstab line in the final column for the userdata partition. You can see an example at: https://android.googlesource.com/device/lge/bullhead/+/nougat-release/fstab_fbe.bullhead
Whilst testing the FBE implementation on a device, it is possible to specify the following flag: forcefdeorfbe="<path/to/metadata/partition>"
This sets the device up with FDE but allows conversion to FBE for developers. By default, this behaves like forceencrypt, putting the device into FDE mode. However, it will expose a debug option allowing a device to be put into FBE mode as is the case in the developer preview. It is also possible to enable FBE from fastboot using this command:
fastboot --wipe-and-use-fbe
This is intended solely for development purposes as a platform for demonstrating the feature before actual FBE devices are released. This flag may be deprecated in the future.
Source: https://source.android.com/security/encryption/file-based
Thanks a million and keep up the great work
This is the guide by Google:
Enabling file-based encryption
FBE is enabled by adding the flag fileencryption with no parameters to the fstab line in the final column for the userdata partition. You can see an example at: https://android.googlesource.com/device/lge/bullhead/+/nougat-release/fstab_fbe.bullhead
Whilst testing the FBE implementation on a device, it is possible to specify the following flag: forcefdeorfbe="<path/to/metadata/partition>"
This sets the device up with FDE but allows conversion to FBE for developers. By default, this behaves like forceencrypt, putting the device into FDE mode. However, it will expose a debug option allowing a device to be put into FBE mode as is the case in the developer preview. It is also possible to enable FBE from fastboot using this command:
fastboot --wipe-and-use-fbe
This is intended solely for development purposes as a platform for demonstrating the feature before actual FBE devices are released. This flag may be deprecated in the future.
Source: https://source.android.com/security/encryption/file-based
Thanks a million and keep up the great work
Simply that Android ( google one's ) is based on a linux kernel that is locked as "security purpose" , means application cannot gain root privileges ( like virus and others) , same it's not possible to build a firmware with the google certificate ( as manufacturers do ) so all this free portages like lineage or previously cyanogenare should be considered as counterfait and not genuine.
Some android "critical" applications needs that the Linux kernel stays locked ( considering you have a genuine manufacturer's firmware) , so changing the level of the kernel as permissive should prevent them to work.
for a great majority of Android's applications , these have no meaning.
Last edited:
Now I'm convinced that this option definitively makes a difference:Hi!
I think I found a possible drainage:
https://android.stackexchange.com/q...-battery-usage-shows-shows-huge-drain-from-it
After disabling this option (situated in Location) the "wifi running" stat inside BBS is going down. I'm not sure if that "drastically" improves battery life time because I found out about this just now and haven't tested it over a longer period.
I only wanted to let you know that I'm still on it and haven't forgotten about it.
For two consecutive times now my battery lasted more than four days instead of previously three.
The option keeps the wifi running even if you turned it of AND have your geolocation service deactivated. I'm not sure if this is the intended behaviour by Lineage/Android or if it is a "bug" in this ROM.
But here is the catch: If you use gelocation and you need high accuracy this option is automatically turned on but not turned of after you switch off geolocation. Also if you are using wifi on a regular basis (e.g. keeping it on while you don't use your phone to get status updates from whatsapp or whatever) I doubt that turning this option off will have any effect on your battery lifetime at all. It'll only work if you're like me and keep your phone in deep sleep most of the time.
Wow, 4 days! For me it is even with rare usage not even 2 days - even with GPS always off
Following the linked article is - I don't have this setting: "Scanning always enable"
I do often have the problem, that after disabling GPS/OruxMaps power consumption keeps high. Only reboot helps.
But my GPS setting is "just device - so no wifi at all.
What really works is the flight mode. Power consumption is really low than. I use this during the night.
Additional question: How do I now if battery gets old and weak? Just duration is not a good indication, as it depends on the load and from software revision. In other devices I could see gaps in battery status, so a drop from 30..20% as an hint. What about the S5Mini?
The option is nowadays hidden under "Location->Top right menu->Search" but as I said you need to disable location and wifi to get a better battery life.
I used BetterBatteryStats to determine the usage statistics. Maybe you could also use it to see if something else drains your battery OR if nothing drains it, that the battery is getting weak.
Last edited:
As I am in "just device - GPS only" - mode, this are greyed and inactive. I guess I have a different problem
Last edited:
I'm just using this ROM since a couple of days, but it seems that it destroyed my external SD card, which I used to extend the storage.
First I got the message that the SD card is slowly. One day later my phone always freeze while display switched off. Could only reboot when taking out the battery, but same problem after reboot.
Now I use another SD card, hope it will work longer.
First I got the message that the SD card is slowly. One day later my phone always freeze while display switched off. Could only reboot when taking out the battery, but same problem after reboot.
Now I use another SD card, hope it will work longer.
Hi,
For all those having problems with the SIM card on latest ROMs, I was able to fix it by installing the latest stock ROM (Through KIES), and then installing again TWRP and the latest ROM provided in this thread (Clean installation).
For all those having problems with the SIM card on latest ROMs, I was able to fix it by installing the latest stock ROM (Through KIES), and then installing again TWRP and the latest ROM provided in this thread (Clean installation).
This should explain why the installing of the stock ROM "fixes" the problem:
https://forum.xda-developers.com/showpost.php?p=72719518&postcount=1074
In short: The EFS is being updated through installing the stock ROM.
It works for me like this. Good idea,THX!
Is there no possibility to extract the EFS as a flashable ZIP- File for all the other users? Or can it be integrated in the Lineage ROM?
Hi,
it also worked for me. It seems to be essential to let the stock rom finish booting. I tried it before with just installing the stock rom, but that did not work.
As stock rom I used "G800FXXU1CQB1 - 1 und 1 Germany" from https://www.usp-forum.de/downloads.php?do=cat&id=210 and flashed it using Odin.
I restored my TWRP backup afterwards (exluding the EFS partition) and dirty flashed 170622 -> SIM problem is gone!
Thanks, CherAlban
I think, the EFS partition is individually for every phone. It contains your IMEI number and personal data. You should never erase it unless you wanna brick your phone.
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