[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU]

[kindlyoldbear]

Has anyone else encountered this ? Is there an Over clock option available on this ROM?

A clean install of the ROM in this thread is OC'd to 1209mhz. That, along with the usual optimization routines (try L-Speed and adaway) are as good as it gets. I've read that the Facepoke app is badly behaved so you might want to stick with accessing it via browser.


Edit: seems there is an updated, optimized kernel available in another thread.

 

[silver9990]

Are these files available anywhere else? msm8916 is downloading at 10-40 KB/s

Never mind, it took 5 hours but I finally got the file.

 

[enzo87mx]

I've been reading the most of the thread and I have a doubt, can this ROM be used in a Galaxy Tab E bought in Mexico?? (SM-T560NZKAMXO)

 

[genstukov]

Does anyone have the boot.img from 20171121? The nightly doesn't seem to exist anymore and I the boot.img from the latest of the unofficial in OP isn't working for me :/

 

[Delgoth]

This thread is great. I haven't read it all the way through just yet. But I'm in the process of setting up the LOS 14 build environment on ubuntu. I just need to get the Lineage Sources now.

This is one of the devices I was going to try and build. I want to build for the SM-T350 as well, which also uses the APQ8016. Looks like you did half the work I want to do already.


What I would like to know then @vince2678 , Can I just start from your T560NU sources and just switch out device trees for the SM-T350? Because only the kernel would really be different right? The only real difference I can tell off the top between the 560NU & 350 is the display size and screen resolution.

I ask because I have the box ready for Lineage Sources. I have both a T560NU and T350 device. I'd like to be able to clone your Sources to make building for the Tab E 9.6 immediately possible. Once I have that set up, I should be able to poke around enough to get it to boot on the Tab A 8.0 soon enough. And I really want to try out LineageOS 14.

I bought these two tablets specifically to familiarize myself with LOS build process. Once I get my head wrapped around using "repo" I'll be set.

But do I really need to download ~70-100GB of sources in order to build for 2 devices that are almost identical? Like really. Why would I need to download all the sources for devices that are nowhere near compatible with the SD410e?

 

[vince2678]

This thread is great. I haven't read it all the way through just yet. But I'm in the process of setting up the LOS 14 build environment on ubuntu. I just need to get the Lineage Sources now.

This is one of the devices I was going to try and build. I want to build for the SM-T350 as well, which also uses the APQ8016. Looks like you did half the work I want to do already.


What I would like to know then @vince2678 , Can I just start from your T560NU sources and just switch out device trees for the SM-T350? Because only the kernel would really be different right? The only real difference I can tell off the top between the 560NU & 350 is the display size and screen resolution.

I ask because I have the box ready for Lineage Sources. I have both a T560NU and T350 device. I'd like to be able to clone your Sources to make building for the Tab E 9.6 immediately possible. Once I have that set up, I should be able to poke around enough to get it to boot on the Tab A 8.0 soon enough. And I really want to try out LineageOS 14.

I bought these two tablets specifically to familiarize myself with LOS build process. Once I get my head wrapped around using "repo" I'll be set.

But do I really need to download ~70-100GB of sources in order to build for 2 devices that are almost identical? Like really. Why would I need to download all the sources for devices that are nowhere near compatible with the SD410e?

We have trees for the T350, so in theory we can build for it on the server, but los 14.1 is deprecated and I don't have any of the tabs anymore, so it'll be up to Sean to maintain for the T350 (there was only one issue left, the audio, which we are working on). If you're willing to test out los 15.1, keep an eye out on jenkins for whenever we manage to get it working.

 

[Delgoth]

We have trees for the T350, so in theory we can build for it on the server, but los 14.1 is deprecated and I don't have any of the tabs anymore, so it'll be up to Sean to maintain for the T350 (there was only one issue left, the audio, which we are working on). If you're willing to test out los 15.1, keep an eye out on jenkins for whenever we manage to get it working.

Well, you guys already have the 560NU on lock. Thanks. But really I'm mainly focused on the T350, the wife uses the 560 normally. If you have trees for the T350. I. Am. Game.

I want to do this. I want to test it and be involved in some capacity. There are no builds of LineageOS at all for T350 that I've found in like 2 weeks of straight looking. I want this to happen. I get it that the dev work takes time and effort.

But I'm also not looking to sit back and simply wait, when I have a T350 that could help progress the project.

I suppose I'll need to join up in the Telegram Channel/Group. Who should I message then in order to get the ball rolling?

No rush, I know I'm a little late to the game here.

But tell me what you want me to do!

 

[vince2678]

Well, you guys already have the 560NU on lock. Thanks. But really I'm mainly focused on the T350, the wife uses the 560 normally. If you have trees for the T350. I. Am. Game.

I want to do this. I want to test it and be involved in some capacity. There are no builds of LineageOS at all for T350 that I've found in like 2 weeks of straight looking. I want this to happen. I get it that the dev work takes time and effort.

But I'm also not looking to sit back and simply wait, when I have a T350 that could help progress the project.

I suppose I'll need to join up in the Telegram Channel/Group. Who should I message then in order to get the ball rolling?

No rush, I know I'm a little late to the game here.

But tell me what you want me to do!

You can contact me. My handle is vince2678 on telegram, or wherever really.

 

[AsItLies]

Hey @vince2678 my name is Hank, you may recognize me as the person that opened the Lineage regression ticket for the gtelwifiue. I didn't know this thread existed or else I would have just posted in here.

I've read the threads going back a bit, it seems the boot.img is the problem with the newer builds? I just wanted to say Vince I'm willing to help testing etc. I have a 9.6 Tab e and am pretty handy technically. Haven't done a lot of android stuff but I can learn.

Thanks for the good work you're doing, would be glad to help if needed.

 

[hughdn]

Make sure you're using the twrp from my jenkins and not any other.

You can also try disabling signature verification if the md5 matches and you still get the same error.

Hey,
Unlike the guy who said he was an idiot but figured this out, I must be a bigger idiot as I cannot. Successfully flashed TWRP (TWRP-3.1.1-lineage-14.1_j15_20170922_gtelwifiue) using ODIN 3.12.3, downloaded the zip, and booting into TWRP to flash the rom, however, getting the Signature Verification error that is not allowing me to flash the latest build (lineage-14.1_j22_20170905_NIGHTLY-gtelwifiue.zip) for my SM-T560NU. And I have no clue how to disable the verification. Tried other zip releases to get the same issue.

Confession, I am not a developer, and know just enough to be dangerous, have flashed devices in the past but it was a long time ago.

Found a tool (Xposed?) which is supposed to be able to allow me to do this but have no idea what i'm doing...

Any help would be greatly appreciated, as I cannot stand the bloat of samsungs UI and apps any longer....

---------- Post added at 06:13 PM ---------- Previous post was at 05:17 PM ----------

Hey,
Unlike the guy who said he was an idiot but figured this out, I must be a bigger idiot as I cannot. Successfully flashed TWRP (TWRP-3.1.1-lineage-14.1_j15_20170922_gtelwifiue) using ODIN 3.12.3, downloaded the zip, and booting into TWRP to flash the rom, however, getting the Signature Verification error that is not allowing me to flash the latest build (lineage-14.1_j22_20170905_NIGHTLY-gtelwifiue.zip) for my SM-T560NU. And I have no clue how to disable the verification. Tried other zip releases to get the same issue.

Confession, I am not a developer, and know just enough to be dangerous, have flashed devices in the past but it was a long time ago.

Found a tool (Xposed?) which is supposed to be able to allow me to do this but have no idea what i'm doing...

Any help would be greatly appreciated, as I cannot stand the bloat of samsungs UI and apps any longer....

So if you're a noob like me, you might not have realized that the recovery tool you were booting to was in fact the stock android recovery, and NOT TWRP version as provided here. The reason being when installing this using the ODIN tool, you must hold the VOLUME UP and HOME buttons while flashing TWRP, or else when it reboots the tablet, it overwrites it with the stock android recovery tool.
Chatted with @kindlyoldbear (THANKS!) who made me realize I was not in TWRP and found this article which illuminated why it wasn't installing properly. (can't post link but its from "How to install TWRP recovery using ODIN" from the androidsoul website)

I think I may be booting into Lineage now... we will see.

 

[AsItLies]

Hey @Delgoth and @hughdn everyone, is there anything new happening with these builds? I have a 560NU. If I can help pls let me know.

Do we need a build box? Is that the issue at this point? I don't have one but would be willing to chip in to get one. It's unfortunate to see the development for this device so abruptly end.

 

[musical_chairs]

Hey @Delgoth and @hughdn everyone, is there anything new happening with these builds? I have a 560NU. If I can help pls let me know.

Do we need a build box? Is that the issue at this point? I don't have one but would be willing to chip in to get one. It's unfortunate to see the development for this device so abruptly end.

Hi! I recently was given a 560NU. I've done a bit of muddling in roms for several phones. If I can free up some hard drive space, I'll download the lineage 14.1 sources and see if I can figure out why the recent builds aren't booting. I don't know that I'll be bringing Oreo to our tab, I'm not quite on that level, but I hope I can find the regression and get some new working builds again.

 

[AsItLies]

Hi! I recently was given a 560NU. I've done a bit of muddling in roms for several phones. If I can free up some hard drive space, I'll download the lineage 14.1 sources and see if I can figure out why the recent builds aren't booting. I don't know that I'll be bringing Oreo to our tab, I'm not quite on that level, but I hope I can find the regression and get some new working builds again.

Wow! That would be awesome!

While this Tab isn't great, it functions well for most everyday type things, and it's inexpensive.

I believe the issue with it booting has something to do with the boot.img file, and the last known good one was in the 20171121 build. I don't have that build but do have the complete build from 9/19. I'm running the 10/05 build but don't have the original just the twrp backup of that install.

It would be great to see this device supported again, they really are pretty handy especially in the budget category.

Thanks again!

 

[musical_chairs]

I believe the issue with it booting has something to do with the boot.img file, and the last known good one was in the 20171121 build.

Well, I got it to build. My build doesn't boot either, which is to be expected at this point I guess. I need to get adb enabled by default so I can get a log of what is going wrong.

 

[silver9990]

I have a 377p so the issue might be different but I was able to boot up until the late November builds I think, then no matter what it just stopped working.

 

[musical_chairs]

I have a 377p so the issue might be different but I was able to boot up until the late November builds I think, then no matter what it just stopped working.

It could be the same issue, it looks like gtelwifiue and gtesqltespr use the same common device tree and the same kernel. It looks like a tag from QCom's upstream or something was pushed to our kernel on Nov.25, this could very well be the source of our problems: https://github.com/LineageOS/androi...mmit/0d93724e00bada55b3e63ccb9b2ba679c5b29830

 

[silver9990]

It could be the same issue, it looks like gtelwifiue and gtesqltespr use the same common device tree and the same kernel. It looks like a tag from QCom's upstream or something was pushed to our kernel on Nov.25, this could very well be the source of our problems: https://github.com/LineageOS/androi...mmit/0d93724e00bada55b3e63ccb9b2ba679c5b29830

To be honest, although I know a little, most of this is beyond my skill set. However, I was able to dump a logcat during boot earlier this month & though I don't have enough skills to debug it myself I was able to locate part of the log related to QCom & found the following:

backtrace:


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #00 pc 00046888  /system/bin/linker (__dl_tgkill+12)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #01 pc 00045e6b  /system/bin/linker (__dl_pthread_kill+34)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #02 pc 0003e20f  /system/bin/linker (__dl_raise+10)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #03 pc 0003cccb  /system/bin/linker (__dl___libc_android_abort+34)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #04 pc 0003bc34  /system/bin/linker (__dl_abort+4)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #05 pc 0003dd0b  /system/bin/linker (__dl___libc_fatal+22)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #06 pc 00009c4b  /system/bin/linker (__dl__ZL29__linker_init_post_relocationR19KernelArgumentBlockj+3146)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #07 pc 00008f6b  /system/bin/linker (__dl___linker_init+358)


[ 02-05 21:38:30.765 10324:10324 F/DEBUG    ]
    #08 pc 000027c0  /system/bin/linker (_start+4)


[ 02-05 21:38:30.771 10320:10320 W/qcom-system-dae ]
type=1400 audit(0.0:129): avc: denied { read write } for name="diag" dev="tmpfs" ino=3022 scontext=u:r:qcomsysd:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0

[ 02-05 21:38:30.779 10320:10320 E/QCOMSysDaemon ]
Can't find/open bootselect node: (No such file or directory)

[ 02-05 21:38:30.779 10320:10320 I/QCOMSysDaemon ]
Starting qcom system daemon

[ 02-05 21:38:30.779 10320:10320 E/Diag_Lib ]
 Diag_LSM_Init: Failed to open handle to diag driver, error = 13

[ 02-05 21:38:30.779 10320:10320 E/QCOMSysDaemon ]
 Diag_LSM_Init failed : 0


[ 02-05 21:38:30.788   246:  246 W/         ]
debuggerd: resuming target 10321

[ 02-05 21:38:30.788   246:  246 E/         ]
debuggerd: failed to send signal 18 to target: No such process

[ 02-05 21:38:31.142 10088:10291 W/dex2oat  ]
Compilation of void android.os.BatteryStats.dumpLocked(android.content.Context, java.io.PrintWriter, java.lang.String, int, int, boolean) took 616.123ms

[ 02-05 21:38:33.040 10088:10291 W/dex2oat  ]
Compilation of void android.widget.TextView.<init>(android.content.Context, android.util.AttributeSet, int, int) took 140.622ms

[ 02-05 21:38:34.665 10088:10088 W/dex2oat  ]
Compilation of void com.android.server.SystemConfig.readPermissionsFromXml(java.io.File, int) took 108.321ms

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.CodedInputByteBufferNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.CodedOutputByteBufferNano$OutOfSpaceException from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.CodedOutputByteBufferNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.MessageNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.ExtendableMessageNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.Extension from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.Extension$PrimitiveExtension from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.FieldArray from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.FieldData from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.687 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.InternalNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.InvalidProtocolBufferNanoException from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.MessageNanoPrinter from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.UnknownFieldData from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.WireFormatNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.android.ParcelableExtendableMessageNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.android.ParcelableMessageNano from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:34.688 10088:10088 W/dex2oat  ]
Skipping class com.android.framework.protobuf.nano.android.ParcelableMessageNanoCreator from /system/framework/telephony-common.jar previously found in /system/framework/framework.jar:classes2.dex

[ 02-05 21:38:35.781 10326:10326 W/init     ]
type=1400 audit(0.0:130): avc: denied { create } for name="rild-cas" scontext=u:r:init:s0 tcontext=u:object_r:socket_device:s0 tclass=sock_file permissive=0

[ 02-05 21:38:35.813 10326:10326 F/libc     ]
CANNOT LINK EXECUTABLE "/system/bin/rild": library "libril_shim.so" not found

[ 02-05 21:38:35.813 10326:10326 F/libc     ]
Fatal signal 6 (SIGABRT), code -6 in tid 10326 (rild)

[ 02-05 21:38:35.813   246:  246 W/         ]
debuggerd: handling request: pid=10326 uid=0 gid=0 tid=10326


[ 02-05 21:38:35.824 10329:10329 E/         ]
debuggerd: Unable to connect to activity manager (connect failed: Connection refused)

[ 02-05 21:38:35.874 10329:10329 F/DEBUG    ]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


[ 02-05 21:38:35.874 10329:10329 F/DEBUG    ]
LineageOS Version: '14.1-20171226-NIGHTLY-gtesqltespr'


[ 02-05 21:38:35.874 10329:10329 F/DEBUG    ]
Build fingerprint: 'samsung/lineage_gtesqltespr/gtesqltespr:7.1.2/NJH47F/524454e000:userdebug/release-keys'


[ 02-05 21:38:35.874 10329:10329 F/DEBUG    ]
Revision: '4'


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
ABI: 'arm'


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
pid: 10326, tid: 10326, name: rild  >>> /system/bin/rild <<<


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
    r0 00000000  r1 00002856  r2 00000006  r3 00000008


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
    r4 a913e58c  r5 00000006  r6 a913e534  r7 0000010c


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
    r8 befd1730  r9 00000001  sl befd1750  fp a90cb030


[ 02-05 21:38:35.875 10329:10329 F/DEBUG    ]
    ip 00000002  sp befd16c8  lr a911ee6f  pc a911f888  cpsr 200f0010


[ 02-05 21:38:35.880 10325:10325 E/QCOMSysDaemon ]
Can't find/open bootselect node: (No such file or directory)

[ 02-05 21:38:35.880 10325:10325 I/QCOMSysDaemon ]
Starting qcom system daemon

[ 02-05 21:38:35.880 10325:10325 E/Diag_Lib ]
 Diag_LSM_Init: Failed to open handle to diag driver, error = 13

[ 02-05 21:38:35.880 10325:10325 E/QCOMSysDaemon ]
 Diag_LSM_Init failed : 0


[ 02-05 21:38:35.871 10325:10325 W/qcom-system-dae ]
type=1400 audit(0.0:131): avc: denied { read write } for name="diag" dev="tmpfs" ino=3022 scontext=u:r:qcomsysd:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0

[ 02-05 21:38:35.886 10329:10329 F/DEBUG    ]

 

[vince2678]

It could be the same issue, it looks like gtelwifiue and gtesqltespr use the same common device tree and the same kernel. It looks like a tag from QCom's upstream or something was pushed to our kernel on Nov.25, this could very well be the source of our problems: https://github.com/LineageOS/androi...mmit/0d93724e00bada55b3e63ccb9b2ba679c5b29830

Nope. gtes builds have been broken since as far back as June or around then. As for the more recent boot issue with the gtelwifiue, that has nothing to do with the kernel. All msm8916 builds for 14.1 are broken because of an upstream lineage change.

 

[AsItLies]

Nope. gtes builds have been broken since as far back as June or around then. As for the more recent boot issue with the gtelwifiue, that has nothing to do with the kernel. All msm8916 builds for 14.1 are broken because of an upstream lineage change.

Does that mean Vince that it's not going to change? Would a build for 15.0 possibly work? Sounds like devices with msm8916 processors are going to fall by the wayside...

 

[musical_chairs]

Nope. gtes builds have been broken since as far back as June or around then. As for the more recent boot issue with the gtelwifiue, that has nothing to do with the kernel. All msm8916 builds for 14.1 are broken because of an upstream lineage change.

Thanks! Would you by any chance be able to point me in the right direction? Or would I be better off skipping Lineage and building off of a ROM that's more of a straight aosp base? I actually like pure aosp better than lineage anyway, but if I did actually get it working I'd be constantly facing 'can you add this feature' requests...