Not in this thread, because the hardware is so different.will we have a version to the users of the variant SM-G800H?
... Wiped everything according to hennymcc's guide at the first post of the thread and in TWRP formatted /Cache and /Data partitions with F2FS according to this guide, and than installed the zips.
Now the phone definitely feels faster than ever, but I'm not sure whether the battery life is a bit shorter. ..
Sorry for asking: I understand that formatting to F2FS some extra step to be done, which potentially speed up operation.
How compatible is it in terms of TWR backups?
Doesn't it make sense to reformat also the (external) sd-card ?
@Panzerknakker, @hennymcc @all:For those who wondering where this is released:
https://androidfilehost.com/?w=files&flid=201249
Thanks to @Panzerknakker.
Flash stock rom and see if the issue is still there. If yes it's more probable that it's an hardware issue, if not it's more peobable that it's a software issue.@Panzerknakker, @[email protected]:
I have a problem with one of the three S5minis we have in our family. After updating to LOS14.1 the phone is not able to switch to mobile data when WiFi is disabled. A second S5mini has no problem to switch to mobile data when WiFi is disabled.
I checked several things:
- APN is correct and the same on all S5minis
- Baseband is the same from https://forum.xda-developers.com/galaxy-s5-mini/general/baseband-sm-g800f-t3354355 on all S5minis. I tried several basebands, nothing changed
- I tried several versions from @Panzerknakker, nothing changed
- changed the SIM-card to different phone, works fine in the other phone. Other SIM-cards also don't switch to mobile data in the S5mini with the problem above
If I check seetings - about the phone - status - status SIM-card the staus of mobile network says connection will be established and isn't changing for hours.
I don't know what to do to get mobile data running.
SMS and calls are working fine on the phone.
Any hints?
Thank you!
I will try it.Flash stock rom and see if the issue is still there. If yes it's more probable that it's an hardware issue, if not it's more peobable that it's a software issue.
It's easier than you think. Just wipe system/data/cache/dalvik and then flash the stock rom with Odin. If the rom goes on bootloops, go again into recovery (this time it will be the stock one) and wipe data/cache.I will try it.
Do you have a link with a short explanation how to do this?
The phone is having TWRP 3.2.1.0 as recovery. I think, I first have to make a backup with TWRP, than replace the recovery and flash stock rom, right? After flashing stock rom it is only necessary to boot until the first run manager starts. Afterwards I reflash TWRP and recover the backup, right?
I did following:It's easier than you think. Just wipe system/data/cache/dalvik and then flash the stock rom with Odin. If the rom goes on bootloops, go again into recovery (this time it will be the stock one) and wipe data/cache.
Any hints?
I had this issue on both our S5 minis, when I put CM/LOS 14.1 onto them the first time about a year ago.
I resolved it finally by using Samsung's phone recovery within Kies to put the original FW on.
Rebooted and set it up basically.
Then installed TWRP with odin.
Wiped everything. I think I had even to do some repartitioning to get LOS flashed.
Installed LOS 14.1 and set it up, no gapps, no apps. Checked mobile data worked ok.
Then installed my apps one after another from scratch.
I did not restore with TWRP and restored only some apps (not system apps) with Titanium Backup.
Since then mobile data has been working on both Minis flawlessly.
The second one is my wife's phone, too. It runs fine since then and no divorce in sight.It's my wife's phone ....
Well, made a complete backup with TWRP and also a backup of data/media.Well, unfurtunately, I have to do it this way. I will let you know, if this helped me out.
Good to know and mostly good for you. I really forgot to suggest you a direct LOS14.1 clean flash.Well, made a complete backup with TWRP and also a backup of data/media.
Wiped everything (system/data/cache/dalvik/internal, NOT SD-card) within TWRP.
Installed lineage-14.1-20180116-UNOFFICIAL-kminilte, latest OpenGApps and LOS-root-package from first post.
Wiped dalvik/cache again.
Phone booted succesfully to LOS14.1, finished setup manager.
Phone succesfully switched to mobile data!
After installing some more of the previous installed apps, the phone is still running fine.
Should have made more backups with Titanium. It is much easier to restore apps TB as I thought before.
Thanks to @Andrea224 and @Panzerknakker my problem is solved.
To me that problem is still strange, because it happened only when performing a direct update from CM13 to LOS14.1. As @Andrea224 said it is a software problem. It was not necessary to go back to stock. Only wiping everything and reinstalling LOS14.1 helped to solve the problem.
Before you start: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)
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
https://github.com/cm-3470/android_device_samsung_kminilte
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
* 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)