[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]
- Thread starter hennymcc
- Start date
I've been waiting for like 30 mins and nothing happend. So I flashed the older build which was no problem. When I got home a few hours later I tried it again and it worked! The whole flashing process took about 30 seconds.
Honestly, I expected better battery life from this build but it looks like it's still the same. I'll try using kernel adiutor and I'll see what I can do.
@hennymcc I've noticed that on this build the fingerprint scanner works also when the screen is off, but it will unlock the phone only if you wake up it through the power or home button. It would be great to unlock the phone with the fingerprint when it's off.
On LOS13 with the MM libs, it works when screen off and also unlocks the phone. Thanks for the tip btw
Isnt it possible to put the changes we do in kernel adiutor in to the next build?
Okay, I found something out about the fingerprint scanner not working sometimes: It's not caused by the libs (you can revert back to MM libs), it's because the sensor doesn't power off immediantly on when phone is locked.
You can test this yourself:
-Lock phone
-Wait 5 seconds
-Tap on the fingerprint sensor multiple times
-Press home button
-And boom - when you try to unlock your phone the sensor is frozen
I hope it's fixable as it also occurs on Stock LP (Don't know about stock MM)
EDIT: Sometimes it still works though - that's weird..?
You can test this yourself:
-Lock phone
-Wait 5 seconds
-Tap on the fingerprint sensor multiple times
-Press home button
-And boom - when you try to unlock your phone the sensor is frozen
I hope it's fixable as it also occurs on Stock LP (Don't know about stock MM)
EDIT: Sometimes it still works though - that's weird..?
Hey, cool. At least I know now how to "reactivate" the fingerprint sensor.
Press the home button multiple times and then it starts to work again. :good:
I can confirm the behavior you mentioned. With LP libs the sensor doesn't freeze completely like before with MM libs but it's not working all the time. Maybe using new libs from recently released samsung MM firmwares is worth a try. (I don't know if there are differences between the samsung MM libs)
Most people here have the g800y. That camera issue could he related to that maybe?
Maybe, I'm not sure but for now I'm just saying on the stock ROM until either 13 or 14.1 become a bit more stable (especially the camera).
The cam (hardware) works, it's the snap.apk that's causing the issues. if you deactivate the system camera in apps and install Google Camera 2.7.008 from apkmirror, reboot and test it you'll see it works :good::good:
After a dirty flash from the previous build of LOS 14.1 to the newest build I got stuck in a boot loop (restarts 3 seconds after the sim lock appears). I'm back on the previous build now and everything's normal again. Any suggestions (clean flash is not an option)?
Sent from my kminiltexx using XDA Labs
Sent from my kminiltexx using XDA Labs
You should provide more info:
1. Have you cleaned cache, dalvik/art cache and system partitions before installing?
2. What Gapps version did you use?
3. Did you install other zips?
1. Have you cleaned cache, dalvik/art cache and system partitions before installing?
2. What Gapps version did you use?
3. Did you install other zips?
Last edited:
Another update
* Sync with LineageOS sources
* Fix OTA updates (add missing /misc partition)
* Enable building TWRP recovery
Not much has changed otherwise, but OTA is working now. If you want OTA updates from my server (in any order):
* install the latest TWRP recovery: twrp-20170222-UNOFFICIAL-kminilte.img
* install the latest ROM: lineage-14.1-20170222-UNOFFICIAL-kminilte.zip
The full list can be seen here: https://aykevl.nl/android
Note that it won't automatically update from CyanogenMOD 13 to LineageOS 14. Maybe it works, but I haven't tried. You can do that by installing the ROM yourself at your own risk, but I would recommend backing up using Titanium Backup (and using TWRP just in case), and restoring again using Titanium Backup. Also note, that Google now stores a lot more backup information (since Android 6/CM13), so most of your apps and data might be restored by the Play Store after you sign into the phone.
* Sync with LineageOS sources
* Fix OTA updates (add missing /misc partition)
* Enable building TWRP recovery
Not much has changed otherwise, but OTA is working now. If you want OTA updates from my server (in any order):
* install the latest TWRP recovery: twrp-20170222-UNOFFICIAL-kminilte.img
* install the latest ROM: lineage-14.1-20170222-UNOFFICIAL-kminilte.zip
The full list can be seen here: https://aykevl.nl/android
Note that it won't automatically update from CyanogenMOD 13 to LineageOS 14. Maybe it works, but I haven't tried. You can do that by installing the ROM yourself at your own risk, but I would recommend backing up using Titanium Backup (and using TWRP just in case), and restoring again using Titanium Backup. Also note, that Google now stores a lot more backup information (since Android 6/CM13), so most of your apps and data might be restored by the Play Store after you sign into the phone.
S
StanleyNL
Guest
I can't install the TWRP image for some reason, when installing, it says: Can't open file name (not a directory)
Do you have any idea what to do?
Last edited:
I've had this error before for whatever reason when the .img I was trying to flash was on my SD card. Moving it to internal storage fixed it for me. Don't know why it happened though.
Sent from my SM-G800F using Tapatalk
S
StanleyNL
Guest
Yeah you mentioned that earlier. It's already in my internal storage, but maybe I should try to move it to the external SD. I'll try it out and report in a moment.
Yeah I don't know. I'm sure someone will be able to help. I've only had that happen once and couldn't figure out the reason. Good luck!
Sent from my SM-G800F using Tapatalk
I've had the same issue. For some reason it appends a slash at the end of the file name. You can use Odin to install it (see first post), or Heimdall like me (open source clone of Odin that works on Linux).
When I have more time I might look into it, but I have very little time for Android development at the moment.
I had nearly the same TODAY... but i got stuck at the bootlogo. the ONLY WAY to get it running was wiping cache, Dalvik cache, system and data. From TWRP i copied the hole internal storage including TitaniumBackup and TWRP folder! to PC and back after flashing new FRESHLY. couldn't even manage to update from the ONLY nandroid backup. I learned from my early days (regularly hole system backup via Titanium and Nandroid TWRP) on cm 11/s4 mini :silly: where i lost all without any backups or so :silly: Viel Glück...
EDIT: seems like my girlfriend's one has the same issue. Both devices are SM-G800F. Both of them had cm13, Lineage 14.1., the recently in germany released original MM FW and then back to this build . The devices from YOU (where the update from 30/01 to 19/02 works) - have you also recently upgraded to latest MM OFW or have you been the hole time on custom side. Really strange issue (both devices got stuck) - @hennymcc - please have a look at it, THX
Last edited:
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