[ROM][7.x][T715][UNOFFICIAL] LineageOS 14.1 for Tab S2 8.0 2015 - Galaxy Tab S2 Original Android Development

[ROM][7.x][T715][UNOFFICIAL] LineageOS 14.1 for Tab S2 8.0 2015 - Galaxy Tab S2 Original Android Development

Forgot 2 patches for the merge in Lineage, added them today and build image. OP updated.

Is there any diffrence to the build which was posted in the old thread?

xeta_at said:
Is there any diffrence to the build which was posted in the old thread?
Click to expand...
Click to collapse
Other then that the sources are coming from LineageOS github, nop. At least there are no changes in my sources, some in LineageOS sources, but I didn't notice any differences.
This was a test build to see if all was transferred correctly.

Ok.
Then I will wait for the next Update.
Except the mentioned problems the ROM already works fine for me.

Hi,
Have Problems with YouTube (Videos Looks after 30sec in Zoom) and Facebook Videos are Not starting.
(T715)

I think, I'll give it a try. Actually I'm using [ROM 5.0.2] [Kernel] [Mod] Tab S2 [T715-T715Y] v3.0 By Jafangie|Deodexed|Rooted . But there are still some issues, like failure "Gallery stopped".
Best regards
Tim

Slider-Override said:
Hi,
Have Problems with YouTube (Videos Looks after 30sec in Zoom) and Facebook Videos are Not starting.
(T715)
Click to expand...
Click to collapse
Same in T710 but it's random, I mean the YouTube problems

Great work, but this was built for the 10'' model. The screen size of the rom needs adjustment to fit exactly for this model. Other than that, once the important issues get resolved, this is my preferred ROM for my Tab S2. Already installed.

eliasps said:
Great work, but this was built for the 10'' model. The screen size of the rom needs adjustment to fit exactly for this model. Other than that, once the important issues get resolved, this is my preferred ROM for my Tab S2. Already installed.
Click to expand...
Click to collapse
You can try to set 700 instead of 768 dpi.

Yes, the camera isn't working.
In the upper tiles I found a button for the torch. The tablet hasn't a torch.

Sorry, this i my third post:
GPS isn't working . No signal in sight.

GPS isn't working .
Adaptive brightness with manual correction isn't possible.

+ hotspot won't work, video zooming in while changing to higher resolution

I use the fingerprint sensor a lot, maybe if this will be fixed i'll try the rom. I've heard about 7.1 coming for some 9.7" Tab S2 variant...not sure if 8" version will receive it too. But i didn't hope. Samsung teached me how to kill a device without major updates with my previous device.

Giuskiller said:
I use the fingerprint sensor a lot, maybe if this will be fixed i'll try the rom. I've heard about 7.1 coming for some 9.7" Tab S2 variant...not sure if 8" version will receive it too. But i didn't hope. Samsung teached me how to kill a device without major updates with my previous device.
Click to expand...
Click to collapse
Lineage 14.1 is Android 7.1, so yeah, it'll be there for T715. Fingerprint sensor isn't working on any Samsung device (at least on any Tab S2, 2015 or 2016 release). This is being worked on, at least for all Samsung Exynos devices. (common lib)

T_I said:
Lineage 14.1 is Android 7.1, so yeah, it'll be there for T715. Fingerprint sensor isn't working on any Samsung device (at least on any Tab S2, 2015 or 2016 release). This is being worked on, at least for all Samsung Exynos devices. (common lib)
Click to expand...
Click to collapse
Yeah i know that Lineage OS is Android 7.1, but i was talking about official one by Samsung. I've heard it's coming for some Tab S2 9" variants but it's not sure if it will be avaible for 8" models too. Anyway, hope that the fingerprint will be fixed soon thaks for all the work you do guys

Hello and a big thank for your work so far. I gave it a try (2017-02-06 build) and liked it very much. Despite the camera problem I encountered a strange behaviour when receiving the first call: I was able to pick up but couldn't hear anything. Then I tried to analyse the issue the behaviour changed - no incoming calls were possible. When I called someone from my mobile they could pick up the call but audio wasn't working. I couldn't hear anything and was not heard. Mobile data worked like a charm over LTE. Do you have an idea how and if this could be fixed? I would like to use Lineage OS as productive OS on my T715 and yes - I am using it for making phonecalls although it might look funny to see me with an 8" device attached to my head. I didn't try if audio would work with a BT device, but maybe I can test this on this WE. For now I'm stuck with stock rom again.
Thanks & Regards, Simon

As I just have a T710 on loan, I can't test RIL and call related issues. Mic should have been fixed, but I'm not sure.
As hardware libs were rewrittento change back to Samsung ril instead of the AOSP one, I had to copy a few gts210ltexx patches to gts28ltexx. I just did a recompile and uploaded the image. OP is updated. Haven't tested it. (I don't own a T715 and haven't had time to test if it'll boot on the T710)

Hello, thank you for the new build. I gave it a quick try, but unfortunately the SIM module didn't recognise my installed SIM card. I tried shut downs etc. So telephony is broken . I rolled back to stock immediately and it worked again.

Related

[ROM][6.0.1][T710][UNOFFICIAL] CyanogenMod 13.0 for Tab S2 8.0 [EXPERIMENTAL]

As CyanogenMod is no more, this project is abandoned and continues asLineageOS 14.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is EXPERIMENTAL and not ready for daily use at the moment
Marked as EXPERIMENTAL, as all uploaded images are untested by compiler, as I don't own the device. (Donations to fix this are welcome :fingers-crossed: :laugh: )
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@CTXz
@RaymanFX
I used @CTXz his T710 work and @RaymanFX's T815 image to base this cm 13.0 build on.
Before you start
THIS ROM IS ONLY FOR THE SM-T710 AND UNTESTED BY DEVELOPER
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : EXPERIMENTAL
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
What is not working
Important
Fingerprint scanner not working
Camera (needs testing, don't know if that is still the case)
Minor
mic not working?
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to recover from issues
Looks like the reset to recovery (<HOME><VOL-UP><POWER>) is still broken on some or all T810 devices with this build.
Press and hold <HOME><VOL-DOWN><POWER> to enter 'download' screen.
Select cancel <VOL-DOWN>
Immediately press and hold <HOME><VOL-UP><POWER> to enter TWRP
Restore back-up made during installation phase
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
01/01/2017 - Rebuild boot.img with self-compiled dtb. ([url]https://www.androidfilehost.com/?fid=529152257862692110[/url])
- Used 18-11 image and replaced boot.img with new one.
**********
18/11/2016 - Recompile with pre-google-update kernel. ([url]https://www.androidfilehost.com/?fid=385035244224398400[/url])
**********
12/11/2016 - Recompile with latest patches for kernel. ([url]https://www.androidfilehost.com/?fid=457095661767115403[/url])
**********
04/09/2016 - Selinux enforcing and switched back to T710 stock blobs for all instead of some common blobs from T815..
**********
29/08/2016 - Selinux permissive build as to test of this made the build non-booting.
**********
23/08/2016 - Recompile with latest gts2-common and CyanogenMod patches, blobs from TheMuppets.
**********
16/07/2016 - Recompile with latest gts2-common and CyanogenMod patches, blobs from TheMuppets.
**********
14/07/2016 - Recompile with latest gts2-common and CyanogenMod patches to check if we can start proces to get it into nightlies.
**********
11/07/2016 - Recompile with latest gts2-common and CyanogenMod patches.
**********
06/07/2016 - Take 4, selinux disabled...
**********
05/07/2016 - Take 3
**********
02/07/2016 - First build based on [user=64263608]@CTXz[/user] github with minor additions by me (prop blobs)
- Correct blobs?
**********
Downloads
Latest CM 13.0 build : https://www.androidfilehost.com/?fid=385035244224398400
Latest known working CM 13.0 build : https://www.androidfilehost.com/?fid=24591000424946172
All CM 13.0 releases can be found here : https://www.androidfilehost.com/?w=files&flid=76091
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All our sources can be found here : https://github.com/Galaxy-Tab-S2/android_device_samsung_gts28wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Samsung Galaxy Tab S2 8.0 T710, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 6.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: EXPERIMENTAL
Created 2016-07-02
Last Updated 2016-07-02
XDA:DevDB Information
CyanogenMod 13.0 for Tab S2 8.0, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, CTXz, RaymanFX
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-07-02
Last Updated 2017-01-27

Experimental
I can't state this enough, this build is highly experimental. Don't start with these images unless you know exactly how to recover a device.
I've taken the sources of @CTXz, added the proprietary-files.txt I use (used the blobs from T710 stock image... these differ from T815), took the dtb.img from the image I have (test, don't know what the difference is with the one in git, diff reports they differ) and adapted our (T810/T815) kernel config for T710. (enough I hope)
I'm very curious if this image boots. When it does (and hoping for a small miracle, works as expected), I can try the same method for T715.

Downloading right now!! I tested CTXz cm13 first release it was nice despite few bugs especially with tv's apps (in france) hope this one gets success and People join the thread
---------- Post added at 06:36 PM ---------- Previous post was at 06:10 PM ----------
Sadly it won't boot but i only performed a factory reset and dalvick, cache wipe(no data,system wipe) this was enough for my nexus 7 2013 maybe it's different with Samsung. Notice that it did the same process for cm 12.1 and CTXz cm13 and had no problem.
I have a bootloop on the first screen "Samsung galaxy tab s2 powered by android "

mysa50 said:
Downloading right now!! I tested CTXz cm13 first release it was nice despite few bugs especially with tv's apps (in france) hope this one gets success and People join the thread
---------- Post added at 06:36 PM ---------- Previous post was at 06:10 PM ----------
Sadly it won't boot but i only performed a factory reset and dalvick, cache wipe(no data,system wipe) this was enough for my nexus 7 2013 maybe it's different with Samsung. Notice that it did the same process for cm 12.1 and CTXz cm13 and had no problem.
I have a bootloop on the first screen "Samsung galaxy tab s2 powered by android "
Click to expand...
Click to collapse
Thanks, then I probably know what went wrong, will do a recompile tomorrow.
Sent from my T810 running cm-13.0

need me to go through a huge testing session???????
---------- Post added at 01:38 AM ---------- Previous post was at 01:37 AM ----------
you can send to me before posting make sure its stable

T_I said:
Thanks, then I probably know what went wrong, will do a recompile tomorrow.
Sent from my T810 running cm-13.0
Click to expand...
Click to collapse
I've uploaded the new build with what I expect that gone wrong fixed. (had same issues with T810, after repo sync the common blobs weren't included, resulting in a Samsung logo stuck on display) Updated OP with new link.
samsung_xoom said:
need me to go through a huge testing session???????
---------- Post added at 01:38 AM ---------- Previous post was at 01:37 AM ----------
you can send to me before posting make sure its stable
Click to expand...
Click to collapse
Would be nice if you can test as well. I think I'll make an experimental file section tomorrow and upload the gts28wifi images there until we know they boot.

Ill get right on it

Still that same bootloop on latest build

error 7

Ah, ok, new try tomorrow, other dtb.img. It's either that or the kernel, will check the kernel config that CTXz used.
Sent from my T810 running cm-13.0

I went through tried to change a few things but didnt get far (midnight pushups in the rain suck)

Was messing around a bit with my new Moto G4 (no cm yet, want one, so I need to build ) Did a recompile with the kernel config I could find and just the prop blobs that differ from T815 build taken from stock image. When someone feels lucky...

Still same error

samsung_xoom said:
Still same error
Click to expand...
Click to collapse
Ok, found the kernel config, or to be precise, asked @CTXz where he placed it in our combined github. Will compile a run with it tomorrow.

Well, thats good i couldnt pinpoint what went wrong on it. Had some time was doing some peeking lol

Looks like selinux was disabled in the kernel config @CTXz was using. Build with that kernel is on-line. When this one boots we'll need to have a look at the selinux settings. (As T810/815 use the same selinux policies and those images boot)

Last 06/07 build booted fine here. I will mess with it today ans try to report bugs if i found ones

Can someone please link android 6.x I can't find it
Sent from my SM-T710 using XDA-Developers mobile app

mysa50 said:
Last 06/07 build booted fine here. I will mess with it today ans try to report bugs if i found ones
Click to expand...
Click to collapse
Nice, it's good to read that we have something to start with. Issues reported by @CTXz were mic, and camera, nothing more.

flyguy914 said:
Can someone please link android 6.x I can't find it
Click to expand...
Click to collapse
Check op in last cm13 build
---------- Post added at 01:45 PM ---------- Previous post was at 12:54 PM ----------
T_I said:
Nice, it's good to read that we have something to start with. Issues reported by @CTXz were mic, and camera, nothing more.
Click to expand...
Click to collapse
Indeed they don't work. Except a few lags it runs nice and has the same issue i had on CTXz build i.e live TV won't work with the applications i use (orange TV and canal+) .
You're on the good way keep going!!!
YouTube app is also really laggy and vidÃ©os don't load well

[ROM][7.x][T810] LineageOS 14.1 for Tab S2 9.7 wifi

You. Are. The. Man!
Sent from my ONEPLUS A3003 using Tapatalk

Wow that was fast
Running awesome BTW... Thanks!
Sent from my SM-T810 using Tapatalk

tzlot said:
Wow that was fast
Running awesome BTW... Thanks!
Click to expand...
Click to collapse
Could have posted a day sooner, but was messing with the dtb compile (@RaymanFX got it working, currently compiling to test).
I hope the solution workd for all Tab s2's with the exynos chipset. I think the T71x tabs have issues with the stock dtb/kernel combination. Would be nice to get those builds up and running again.

Might flash this tomorrow. Anyone try Netflix on it yet ?

Awesome stuff. Will give this a flash here in a bit after I do a Odin. Just for my infos :angel: Does this have similar tweaks to CM 14.1 did or still pretty barebones at this date. Either way it won't stop me from trying it, just curious.

maddog975 said:
Might flash this tomorrow. Anyone try Netflix on it yet ?
Click to expand...
Click to collapse
DroidIt! said:
Awesome stuff. Will give this a flash here in a bit after I do a Odin. Just for my infos :angel: Does this have similar tweaks to CM 14.1 did or still pretty barebones at this date. Either way it won't stop me from trying it, just curious.
Click to expand...
Click to collapse
It's a rebranded cm-14.1, so expect all issues cm-14.1 had to be acailable in this build as well, until we fixed them.
Just replaced the boot.img from a failed build of yesterday with a new one with a self compiled dtb made today. The change to build the dtb killed something else, so I need to hunt that new bug down. Will update OP with link to new file when the upload finishes.

T_I said:
It's a rebranded cm-14.1, so expect all issues cm-14.1 had to be acailable in this build as well, until we fixed them.
Just replaced the boot.img from a failed build of yesterday with a new one with a self compiled dtb made today. The change to build the dtb killed something else, so I need to hunt that new bug down. Will update OP with link to new file when the upload finishes.
Click to expand...
Click to collapse
Sounds cool...and thanks a ton for all the work you're doing on this...and Happy New Year!

maddog975 said:
Might flash this tomorrow. Anyone try Netflix on it yet ?
Click to expand...
Click to collapse
Netflix will cast fine if you have a chromecast but doesn't work locally yet. The video zoom issue is much improved - YouTube works great, prime video works, Facebook video works but still a bit buggy (videos sometimes play at half speed, sometimes need reloading to work fullscreen).
Sent from my SM-T810 using Tapatalk

NalNalas said:
You're the best! I'll totally donate to you when I get the chance.
Click to expand...
Click to collapse
Just did exactly that yesterday . Work like this needs tangible support.
Sent from my ONEPLUS A3003 using Tapatalk

Thanks for the support.
Just compiled a complete image with the new boot.img generation (incl. compiled dtb instead of stock). Updated OP. Image not yet tested, flashing as I type..

T_I said:
Thanks for the support.
Just compiled a complete image with the new boot.img generation (incl. compiled dtb instead of stock). Updated OP. Image not yet tested, flashing as I type..
Click to expand...
Click to collapse
Mine is stuck on the boot screen.
Edit: I flashed the boot.img file from the 12/31 build with Odin and the 01/01 build booted fine.

Check, stuck on my tab s2 as well. Will build a new image tomorrow.
Sent from my SM-T810 running lineage-14.1

Build 01/02 boots just fine

Did a recompile, added latest patches of @RaymanFX on the gts2-common tree and rebranded the product name to lineage. (missed that one) Updated op with link. (and tested, it boots )
Feels a tad faster on the screen as well.

Sounds great that something is happening for the Tab S2 However i have a T815 (LTE model), any chance it will be supported somewhere down the line? (with or without LTE support, as i rarely use it)

Epedemic said:
Sounds great that something is happening for the Tab S2 However i have a T815 (LTE model), any chance it will be supported somewhere down the line? (with or without LTE support, as i rarely use it)
Click to expand...
Click to collapse
@RaymanFX is building the T815 sources and to be honest, doing most of the work. I mostly check of his patches don't break the T810 build. I don't know where he uploads his images.
Speaking of which, when he was debugging the T815 to locate the missing hardware decode support, he found, after a clean install, that they were used. I've compiled today and I'm now rebuilding my device, to see if graphincs have improved. When someone with netflix could test if it works after a clean flash, that would be nice.
OP updated with link to todays build.

Did a factory reset, fresh install - Netflix still can't play.
01-05 19:37:02.502 E/BufferQueueProducer(2616): [SurfaceView - com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity] cancelBuffer: BufferQueue has no connected producer
Thanks for the efforts anyway.

Drat, still no-go...
Sent from my SM-T810 running lineage-14.1

NalNalas said:
Youtube is having a problem where when you set the video to 1080p, after a minute or so the video zooms in awkwardly. It can be easily replicated.
Click to expand...
Click to collapse
This is a very well-known bug, affecting all AOSP-based 7.1.1 ROMs. The problem has to do with auto quality detection. If YouTube, and pretty much all web-based video, allowed for the resolution to be manually and statically set, this wouldn't be a problem.

[ROM][7.x][T715][ABANDONED] LineageOS 14.1 for Tab S2 8.0 2015

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As of 30-01-2017 the sources have been included in LineageOS, created new thread https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-14-1-tab-s2-8-0-2015-t3551027 as the project is now original LineageOS.
This ROM is BETA and not ready for daily use at the moment
Marked as BETA/EXPERIMENTAL, as all uploaded images after 7-2-2017 are untested by compiler, as I don't own the device. (have one on loan for a few weeks) (Donations to fix this are welcome :fingers-crossed: :laugh: )
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
@Sarum4n
I used @CTXz his T710 work and @RaymanFX's T815 image to base this cm 13.0 build on.
Special thanks to @Sarum4n, as he loaned me the T710 to test the builds and debug the boot issue we had. All except lte functionality i stested. (as the T710 doesn't have lte)
Before you start
THIS ROM IS ONLY FOR THE SM-T715 AND MOSTLY UNTESTED BY DEVELOPER
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : BETA/EXPERIMENTAL
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
Bootanimation not working
Mic not wirking
What is not working
Important
Fingerprint scanner not working (included, but not working)
Camera not working (killed it with kernel update )
Vibration not working (probably also kernel)
Minor
Instructions
How to install Lineage 14.1
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy Lineage 14.1
How to recover from issues
Looks like the reset to recovery (<HOME><VOL-UP><POWER>) is still broken on some or all T710/5 & 810/5 devices with this build.
Press and hold <HOME><VOL-DOWN><POWER> to enter 'download' screen.
Select cancel <VOL-DOWN>
Immediately press and hold <HOME><VOL-UP><POWER> to enter TWRP
Restore back-up made during installation phase
How to ROOT
Install the correct root package from here. (after flash of the image)
In LineageOS 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of LineageOS's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
29/01/2017 - First build LineageOS 14.1.
- Fixed mic
**********
Downloads
Latest LineageOS 14.1 build : https://www.androidfilehost.com/?fid=457095661767133753
All LineageOS 14.1 BETA releases can be found here : https://www.androidfilehost.com/?w=files&flid=141202
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All our sources can be found here : https://github.com/Galaxy-Tab-S2/android_device_samsung_gts28wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
LineageOS 14.1 for Samsung Galaxy Tab S2 8.0 T715, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: BETA
Created 2017-01-30
Last Updated 2017-01-30
XDA:DevDB Information
LineageOS 14.1 for Tab S2 8.0 2015, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, RaymanFX, CTXz
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-01-30
Last Updated 2017-02-11

Jumped the gun a bit, as it's compiling now. The issues are overcome and the build should work. (Want to have it online as soon as it's upoloaded) All info in OP is correct, except the latest build link. (need to upload that first )

Thank you! Will test this.
Quick question. Is LTE module working? And which gapps shoud i install, arm or arm64?

Uploaded build and updated link in OP.
PaterProx said:
Thank you! Will test this.
Quick question. Is LTE module working? And which gapps shoud i install, arm or arm64?
Click to expand...
Click to collapse
Don't know if lte is working, don't have a T715, just a sleep-over T710. I'm now repacking and flasing so I can test it there.
The device is arm, so you need arm gapps ans root package. I test with opengapps pico.

T_I said:
Uploaded build and updated link in OP.
Don't know if lte is working, don't have a T715, just a sleep-over T710. I'm now repacking and flasing so I can test it there.
The device is arm, so you need arm gapps ans root package. I test with opengapps pico.
Click to expand...
Click to collapse
Okay, im downloading. Will give you a report. What do you mean with root package?

PaterProx said:
Okay, im downloading. Will give you a report. What do you mean with root package?
Click to expand...
Click to collapse
See OP -> How to root. Things changed in Lineage, root isn't available by default anymore.
Tested image on T710 and it boots. Screenshot added to OP.
Camera isn't working. As it did in cm-13 build for T715, I can check what I killed.

Okay, installed it and it boots. WLAN works, LTE also works but not on first boot. Only thing I noticed is that vibration is not working and camara also. But all in all its very smooth. Will give this a week and report again.

PaterProx said:
Okay, installed it and it boots. WLAN works, LTE also works but not on first boot. Only thing I noticed is that vibration is not working and camara also. But all in all its very smooth. Will give this a week and report again.
Click to expand...
Click to collapse
I killed the camera in the process of getting screen back up. (Kernel config) When I remember correctly, vibration is also a kernel option. Will look into this and post a build when I get a solution.

Installed and works!
Just installed the ROM. I can confirm, that everything is working as described above, perfect! Thanks for the great work, i will continue testing and try to support as far as i can.
One first, little thing i just found by chance:
When opening settings app, the last menu entry 'About Tablet' shows 'SM-T815' under 'Device Model'.
Not a big deal, just wanted to report.
Thanks again, i appreciate the work done by you all!

Thanks for the Rom :good:
Since I own the T715 I am waiting for this.
Will give it a try during the weekend

The T710/T715 sources have been included in LineageOS github on 30-01-2017, so I'll be moving the thread over to the official development section. (or be more precise, create a new one there)

Hi,
Have Problems with YouTube (Videos Looks after ~30sec in Zoom) and Facebook Videos are Not starting.
(On a T715)

Please report the issues to the correct thread, as this one is abandoned. (we moved to original development) (And fixes to bideo playback are made and upodated images will be posted there )

T_I said:
Please report the issues to the correct thread, as this one is abandoned. (we moved to original development) (And fixes to bideo playback are made and upodated images will be posted there )
Click to expand...
Click to collapse
Closed - in future, please request that the thread be closed and also ADD REDIRECTION to your final thread post to enable others to find things...
https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-14-1-tab-s2-8-0-2015-t3551027

[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]

LineageOS 17.x Unofficial for Galaxy A3 2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26

Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations

Reserved

Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)

banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home

Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.

yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM

Ok thanks. Another issue : I can't get split-screen working with any apps. And you?

Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...

That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?

starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing

MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.

starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using

Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.

The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.

MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?

Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards

Migrate doesn't detect it as an installed rom, any help?

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:

[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit the Wiki.
Important Info
WARNING: the official 17.1 build 20201101 is defective, causing a bootloop & got removed from the Lineage servers. The ROMs affected are klte, klteduos & kltedv.
If you updated to 20201101 and are caught in a bootloop as reported by several S5 users in the pages #3 of this thread and the following pages: flash an older version like 20201025 without wiping anything (a.k.a. dirty flash) and you will not lose your aps & settings:
1- On the S5 you can simulate a battery removal if you press Volume down + Power button for 10-20 seconds while frozen, in bootloop or Download Mode: the S5 goes black & turns off.
If you keep on pressing the buttons until the Samsung bootloader splash screen appears & release them then S5 should reboot in System.
Or remove the battery to turn it off.
2- With the S5 turned off hold Volume Up + Home + Power to boot in recovery and either sideload the older version or copy to the S5 the older build as MTP is enabled by default in TWRP and flash it from there.
***
To flash this rom you need TWRP version 3.3.1-0 or newer or the Lineage Recovery specific to your device model.
Some TWRP 3.4.0 users reported fail to install LineageOS after a wipe. Rebooting to TWRP recovery after the wipe solves this issue.
The adb command adb reboot sideload does not work in TWRP for the S5 as if you sideload a file afterwards it will fail as I tested myself with this error message: " command is: 'sideload' and there is no value". You must manually select in TWRP > Advanced > ADB Sideload > swipe to begin sideload then you can sideload your file. You must do the same for each files if you sideload more than one.
The S5 maintainer haggertk recommends not choosing Internal storage for the Micro SD card (adoptable storage) when formatting the card in the device and posted about it here: "...my opinion is no one should use adoptable storage. It's a fragile mess and always has been since Google explicitly does not care about sdcards.".
Some S5 17.1 users reported being stuck in an endless boot animation after restoring a 17.1 TWRP backup. A workaround tested by @wireroot & posted here is to flash the original LineageOS ROM that you were running when you made that backup right after the restore operation. This was confirmed by @jdrch in his post here.
An other possible workaround is to flash "fix_rootfs_label.zip" that you can find here right after restoring the TWRP backup. Note: this was NOT confirmed yet by S5 users in this thread.
EFS Partition Restore - @Eadn33 reported here in the old 16.0 thread that he could not restore the EFS partition with TWRP 3.4.0 but could with TWRP 3.3.1-0 on his S5 G900V. Other models may have that problem also but no other reports so far. See EFS Partition Backup - No Service, No IMEI & No SIM Card Fix for explantions.
Warning: do NOT select install TWRP app in TWRP as it will cause a bootloop.
Download Links
The Galaxy S5 klte variants currently supported by LineageOS are:
klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
klteactivexx - SM-G870A, SM-G870F
kltechn - SM-G9006V, SM-G9008V
kltechnduo - SM-G9006W, SM-G9008W
klteduos - SM-G900FD, SM-G900MD
kltedv - SM-G900I, SM-G900P
kltekdi - SCL-23, SC-04F
kltekor - SM-G900K, SM-G900L, SM-G900S
Each respective download pages include a link to the official clean installation instructions and a link to Device info which includes a link about how to upgrade to a higher version. For example from official 16.0 to official 17.1 without losing your settings & apps.
The wiki mentions only the Lineage recovery but several S5 users reported successful clean install or 16.0 > 17.1 upgrading while using TWRP instead.
TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Google apps (Optional. The S5 requires the ARM for Android 10 version because LineageOS 17.1 is based on Android 10 & the S5's ARM architecture.): https://wiki.lineageos.org/gapps.html
As a rule of thumb the larger the Open GApps package, the more chance of a problem on first boot with the ever changing privapp-permissions.
I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/ See Open GApps Package Comparison
Some users prefer not installing any Gapps packages & use the Aurora Store v3 - a FOSS Google Play client to download apps from Play Store. Note that some apps may require the Google Play Services & librairies which are included in the Gapps packages & may not work properly or will not get timely notifications because of it.
Root (Optional): The LineageOS AddonSU and Privacy Guard are deprecated in 17.1.
Magisk which is the only root solution for 17.1 @ the present is not supported by LineageOS. See Magisk download & Installation instructions by the Magisk dev & also the excellent Magisk and MagiskHide Installation and Troubleshooting guide by @Didgeridoohan. Thread on XDA: Magisk General Support / Discussion.
Magisk can be installed later at anytime so it's not necessary to install it during the initial installation of LineageOS.
Bug Reporting
If a bug is discovered, confirm it with other users in this thread & include your device model & build date (for ex. lineage-17.1-20201025-nightly-klte), then report it following the LineageOS wiki here: https://wiki.lineageos.org/bugreport-howto.html
Known Bugs - Known Issues
1- On an encrypted S5 17.1 + Gapps if Secure Startup is enabled it may fail to reboot or take a very long time to boot. See bug report here.
From haggert's post here:
...there is some kind of timeout that hits ALL legacy devices - addition of gapps is seemingly enough to push it over the edge. Aside from first boot or upgrade, sometimes you'll be able to get in and sometimes not. I bet if you are able to decrypt in twrp and delete dalvik cache you'll get fully booted again.
Bottom line, if you are encrypted, make sure to disable secure startup (go change the pin/pattern/password, even to the same thing, and say that you do not want to have to answer for the device to start). {bold by me}
Click to expand...
Click to collapse
2- Not a bug really but some S5 users reported fail to boot on 17.1 or no SIM card recognized because they had an older baseband/modem. See S5 Odin Flashable Modem & Bootloader.
Haggertk posted here about 17.1: "...I'm willing to bet that you have some L or earlier baseband. Except for the activexx build, you have to be running M baseband now." {bolding by him}.
3- Google Backup cannot be restored if you use a 4x4, 5x5 or 6x6 lock screen pattern in LineageOS instead of the Android default 3x3 pattern. See the bug report here.
4- Display accepts touch input while off due to proximity and screen does not turn back on after call bug report by @Eadn33. The bug was fixed with klte family builds 2020-11-13 or newer. Thank you Mr. haggertk.
5- SMS reception notification delay depends on doze / unlock state by @wireroot. He posted about it in this thread here.
6- Bluetooth Crashing - Some users reported having issues with Bluetooth in this thread: @KrautHolg here, @liquidraver here and here, @pmduper here, @navcar here and included a logcat, @badesh here and here, @mrmarioman who posted here.
@KrautHolg created a report in the LineageOS bug tracker with a logcat here: Bluetooth repeatedly crashes with multiple devices for the S5 klte LineageOS 17.1.
OTOH @Eadn33 reported here that he does not have any problems "with a soundbar, music and hands free in car , or scan tool for car". I tested for 2 hours listening to music with Bluetooth headphones, received a call & also had no problems on my S5 G900M klte.
So far nobody created a Bluetooth bug report with an attached logcat in the LineageOS bug tracker for the S5 running LineageOS 17.1. See this post about how to create one: S5 Bluetooth Crashing Bug Report?
7- Fingerprint Scanner: Some S5 users reported not being able to register their fingerprints in > Settings > Security > Fingerprint. Contrary to the Lineage instructions the finger must be swiped down & not just "Touch the sensor". See the screenshot & the linked trick if you still can't register the fingerprint in S5 G900F Fingerprint Issue.
Not a bug but some users reported the scanner not working on older basebands but working after updating it like @jackass5 in his post here. See S5 Odin Flashable Modem & Bootloader.
Several users, including me, reported a higher battery usage after registering some fingerprints. See S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat
8- Camera (Snap) > Settings > Storage > if you select SD Card the photos are saved to /external sdcard I.D./Android/Data/org.lineageos.snap/Files/ but taping on the thumbnail of the photo you just took mistakenly opens /storage/emulated/0/DCIM/Camera/. Additionally, Gallery does not see that Files folder but a third-party app like Simple Gallery Pro that does show the Files album.
In LineageOS 17.1 build 2020-11-23 or newer the SD Card option was deleted instead of fixing the bug. See LineageOS 17.1 - In Camera the Option Save to SD Card has Been Removed in this thread.
9- Call Forwarding Not Working - In both the stock Phone app or when dialing a code it's broken. See this post that includes a link to a bug report: S5 klte LineageOS 17.1 Call Forwarding Error. Thanks to @uyguremre for reporting the issue here.
***
S5 U.I. Speed-Up Tip: Try those as fast as you can before the tweak: expand/close notification curtain, app drawer & scroll, recent apps & scroll, horizontal scroll fast between hope pages if you have a few, open Settings & scroll, etc.
Then: Settings > Accessibility > enable Remove animations.
Test again as you did before. Profit!
LineageOS FAQ
https://wiki.lineageos.org/faq.html
LineageOS Stats
https://stats.lineageos.org/
Credits
The S5 klte + variants LineageOS maintainer is @haggertk who valiantly supported the S5 klte family through LineageOS 14.1, 15.1, 16.0 & now 17.1. Big thanks for his perseverance & dedication.
He is also one of the 9 LineageOS directors and maintains other devices as well as you can see in https://wiki.lineageos.org/contributors.html
Many thanks also to the LineageOS team and all the contributors out there in the community that made the Lineage project possible. You can see their names or nicknames in the zoomable & searchable > Settings > About phone > Contributors.
Haggertk seemed uninterested in creating an S5 17.1 tread on XDA or he is too busy maybe so I went ahead and created one using part of the OP of his old S5 LineageOS 15.x thread. If he wants a transfer of this thread's ownership I will gladly do it.
haggertk said:
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
klte-common (shared by all klte* devices): LineageOS/android_device_samsung_klte-common
klte: LineageOS/android_device_samsung_klte
klteactivexx: LineageOS/android_device_samsung_klteactivexx
kltechn: LineageOS/android_device_samsung_kltechn
kltechnduo: LineageOS/android_device_samsung_kltechnduo
klteduos: LineageOS/android_device_samsung_klteduos
kltedv: LineageOS/android_device_samsung_kltedv
kltekdi: LineageOS/android_device_samsung_kltekdi
kltekor: LineageOS/android_device_samsung_kltekor
Click to expand...
Click to collapse
Kernel Source Code:
Kernel tree: https://github.com/LineageOS/android_kernel_samsung_msm8974/tree/lineage-17.1
LineageOS Gerrit code review: https://review.lineageos.org
Android version: 10
Note: this post as well as posts #2 & 3 will be updated soon.
***

Reserved.

Reserved for alternative clean install & upgrading tutorial.

If you are going to make a thread and list mappings to builds, please make it correct. Inspect the wiki (hint: G900AZ and S902L are no longer supported in the klte build).
Sent from my PH-1 using Tapatalk

haggertk said:
If you are going to make a thread and list mappings to builds, please make it correct. Inspect the wiki (hint: G900AZ and S902L are no longer supported in the klte build).
Click to expand...
Click to collapse
Fixed, thanks.
Are you sure you don't want the ownership of this thread?
***

... and for the one for hlte ...

Issue with brightness control 20201025 update
Hi all,
I did an update yesterday from 17.1-20201018-NIGHTLY-klte to 17.1-20201025-nightly-klte via the inbuilt updater and TWRP 3.4.0 on my sm-g900f.
Flash went smooth but brightness control stopped working in 20201025.
If I use the brightness adjustment slider, the global variable is set accordingly, I checked that via Tasker.
But the display itself does not change brightness one way or the other.
Same with auto-brightness on.
I manually flashed back to 20201018 just now. Brightness adjustment works fine again.
Anyone else?

Hawaiihemd said:
Hi all,
I did an update yesterday from 17.1-20201018-NIGHTLY-klte to 17.1-20201025-nightly-klte via the inbuilt updater and TWRP 3.4.0 on my sm-g900f.
Flash went smooth but brightness control stopped working in 20201025.
If I use the brightness adjustment slider, the global variable is set accordingly, I checked that via Tasker.
But the display itself does not change brightness one way or the other.
Same with auto-brightness on.
I manually flashed back to 20201018 just now. Brightness adjustment works fine again.
Anyone else?
Click to expand...
Click to collapse
Actually, was a little concerned, but, did it anyway (My build kltedv). Just concerned about the "Recovery", I have not, switched to LineageOS Recovery. So, knowing I was running what one could say , is Not the correct recovery (Still TWRP )
Had not issues, every thing went rather smooth and easy of course!
thanks

Still on 1 build before latest one
Will change soon, this ROM is brilliant

Hi,
Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing. As I use it all the time with the fitness tracker as well as the earphones it is more than a little nuisance. Any ideas on what should I try first to fix this issue?
Best,
Holger from Flensburg

Hi sorry if this already covered the latest version of this klte ROM keeps shutting down as it installs logo freezes then back to boot screen _ flashed unofficial version same klte phone flashed fine _ clean install always I'm mystified unless its a bootloader version problem ?

Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!

Arrxa said:
Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!
Click to expand...
Click to collapse
You have good chances to get it upgraded, if you follow wiki.lineageos.org

KrautHolg said:
Hi,
Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing. As I use it all the time with the fitness tracker as well as the earphones it is more than a little nuisance. Any ideas on what should I try first to fix this issue?
Best,
Holger from Flensburg
Click to expand...
Click to collapse
Nothing. Bluetooth sucks since LOS16, constant disconnects (more frequently if you use more than two devices watch+earphone+car - etc), smart watch can't reconnect after disconnection, etc.
There are temporary solutions, like go to apps and clear storage on bluetooth app + reboot, but it won't last.
If you want more stable bluetooth, go back to 14.1. (or stock)

liquidraver said:
... go back to 14.1.
Click to expand...
Click to collapse
I can only find builds from lineage-17.1-20201025-nightly-klte to lineage-16.0-20200913-nightly-klte -- but nothing older. How do I find a 14.1 build?

KrautHolg said:
I can only find builds from lineage-17.1-20201025-nightly-klte to lineage-16.0-20200913-nightly-klte -- but nothing older. How do I find a 14.1 build?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=140202

KrautHolg said:
.. Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing...
Click to expand...
Click to collapse
Have you tried flashing an older 17.1 build over it without wiping System & Data (a.k.a. dirty flashing) so not to lose your settings & apps?
***

curiousrom said:
Have you tried flashing an older 17.1 build over it without wiping System & Data (a.k.a. dirty flashing) so not to loose your settings & apps?
***
Click to expand...
Click to collapse
I haven't done anything yet, exactly because of this. Still considering my options. Reinstalling everything by hand is such a pain....

dtr. said:
Hi sorry if this already covered the latest version of this klte ROM keeps shutting down as it installs logo freezes then back to boot screen _ flashed unofficial version same klte phone flashed fine _ clean install always I'm mystified unless its a bootloader version problem ?
Click to expand...
Click to collapse
Solved _ flashed latest klte firmware via Odin (had to try a few times kept 'looping) eventually managed to install firmware then flashed twrp now running 25.10.20 fine no bootkoops everything OK thanks for the build

Arrxa said:
Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!
Click to expand...
Click to collapse
Yes, I successfully dirty flashed 17.1 over 16.0 with TWRP 3.4.0. Yes, you need a newer gapps package(ARM, Android 10).

Database Develop

welcome