yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] RaymanFX:
Nice to see someone else jumping in and compiling :)

I'm still working on the mic input issue..

I have it working on my Galaxy Note 5 which uses a similar audio HAL setup, so this is strange issue for me.

There are a bunch of other patches I uploaded to gerrit yesterday like advanced/accelerated fimg2d drawing/blitting and such (2D graphics acceleration by using Samsung specific hardware).
[Galaxy Tab S2 Original Android Development] ttalonso:
any alternative for SM-T713 users? :(
[Galaxy Tab S2 Original Android Development] NeWONEx:
Thought might you don't like that [emoji28]
[Galaxy Tab S2 Original Android Development] nostupidthing:
Can you take a look at T710/715 as well?? :D
[Galaxy Tab S2 Original Android Development] Hitchi:
Will you also release a T819 version? There are no Custom Roms available in general for this device...strange

Gesendet von meinem SM-T819 mit Tapatalk
[Galaxy Tab S2 Original Android Development] seancojr:
None of these issues bother me so much. I'm having trouble with mobile data not working even though it's enabled and I'm using the default. ATT Phone APN Sending an SMS message displays an error even though they are delivered. It had me confused quite a bit at first and I'm concerned about when messages actually do fail to send, how I'll know. I discovered that this was reported as a known issue for the official CM13 as well. Hopefully, RaymanFX will be able to provide a fix.
[Galaxy Tab S2 Original Android Development] Adler12:
Hi, in my SM-T815, CM 14 build, i have two problems. 1st= i have no mobile Internet. Apn are manualy entered for german 1&1 E-Plus. Everything are on. But no mobile conection. 2nd= the mhl chip ist not working in this rom! Today i am stay in school but i habe no signal in the Beamer. Not with VGA and not with HDMI.
[Galaxy Tab S2 Original Android Development] RaymanFX:
I'm working on the hardware accelerated video playback issues right now, but LTE and Mic input are next on my list.

As some of you might have noticed, CyanogenMod is no more and we rebranded to LineageOS.

However, we're not going anywhere (http://lineageos.org/) :)

What was CyanogenMod is now LineageOS, we just rebranded.

Almost all of the developers I know have made the switch and are on board with LineageOS.

I hope Samsung gets Nougat out of the door rather sooner than later, because this will simplify the task for sure.

If not, we'll just continue to hack our way around the issues as we are doing right now.

Fingerprint implementation has a low priority for me right now, so that needs to wait some more..
[Galaxy Tab S2 Original Android Development] erni83:
Good news:fingers-crossed:

I'm looking forward to new release

Many Thanks

Happy New Year
[Galaxy Tab S2 Original Android Development] NeWONEx:
https://review.lineageos.org/#/q/owner:raymanfx%40gmail.com

There are many changes happened last few days. Is there Any chance to compile the rom from source ?

Thanks in advance [emoji16]
[Galaxy Tab S2 Original Android Development] TheMorpheus:
Unfortunately I've moved and I don't have my pc with me so I can't compile... Sorry :(
[Galaxy Tab S2 Original Android Development] NeWONEx:
It's okay thanks for your response [emoji4] we are going to wait [MENTION=3463426]RaymanFX[/MENTION] to release new build.
[Galaxy Tab S2 Original Android Development] suzook:
Is he actually involved with this anymore?
[Galaxy Tab S2 Original Android Development] NeWONEx:
Yes, he is working on (T81X) most of the time and solving many issues. But he don't have time to compile and upload rom I guess. He never mind if someone compile the rom and post link here.

If you want to see his work from the link below:

https://review.lineageos.org/#/q/owner:raymanfx%40gmail.com
[Galaxy Tab S2 Original Android Development] Lexuzz89:
Delete please
[Galaxy Tab S2 Original Android Development] NeWONEx:
Why T815 still didn't get nightly build from lineage? most of the issues are solved. https://download.lineageos.org
[Galaxy Tab S2 Original Android Development] RaymanFX:
Soon (TM).

LTE is fixed, so is hardware decoding.

And today I fixed fingerprint.

The only thing that's broken still is mic input, but it's working for incall usecases...

So Lineage 14.1 builds should be out soonish.
[Galaxy Tab S2 Original Android Development] NeWONEx:
You are amazing , Thanks :D
[Galaxy Tab S2 Original Android Development] RaymanFX:
New LineageOS 14.1 builds for Tab S2 LTE and WiFi are attached to the first post now :)

Fingerprint, microphone input, and many more are fixed.

New features include hardware RGB display tuning (Settings->Display->LiveDisplay), this is now done on the display processor instead of the GPU and does not drain the battery any longer.
[Galaxy Tab S2 Original Android Development] igna.98:
I think I love you, you are my hero!
[Galaxy Tab S2 Original Android Development] NeWONEx:
I [emoji16] it was really soooner than what I thought ^-* .

Thanks
[Galaxy Tab S2 Original Android Development] harise100:
Did a clean install on my T810:

- Microphone doesn't work good (tested with Google and Soundrecorder)

Saying "ok google" activates the search, but it can't "hear" my question.

- I can register Fingerprints, but unlocking doesn't work

- Statusbar clock is centred, changing it, crashes the Settings

- What happened to the Bootanimation ? There isn't any.

Other than that, the tab is running nice and smooth.

Thanks for your effords.
[Galaxy Tab S2 Original Android Development] NeWONEx:
- Fingerprint works very well here . to unlock and in app

- Clock in the center while it in the right in the settings .

- untill now settings crashed once only

- Mic works but it is very very low.

Everything else is amazing . very smooooth ^^ thank you
[Galaxy Tab S2 Original Android Development] sporc10:
Great work!!!

Is there a chance this project will be officially supported by lineageos?

best regards
[Galaxy Tab S2 Original Android Development] pilspeda:
I think u have actually fallen in love with you, thanks
[Galaxy Tab S2 Original Android Development] noratroll:
no boot animation, either. black screen instead. good for battery ;)
[Galaxy Tab S2 Original Android Development] noratroll:
Supersu 2.79 sr3 not recognized; installed system mode -> ok
[Galaxy Tab S2 Original Android Development] tzlot:
Can anyone confirm the status of the video bugs in the new build?
[Galaxy Tab S2 Original Android Development] NeWONEx:
Download "addonsu-arm-signed.zip" from here https://download.lineageos.org/extras then flash it

It's necessary since Devs removed Root access from CM 14.1
[Galaxy Tab S2 Original Android Development] noratroll:
Thank you for this advice. I'm aware of the lack of inbuilt root in LOS due to the needs of those who use apps which do not accept rooted devices.

It is a kind of habit to use SuperSu since it's well configurable. The former inbuilt SU did not exactly match my thoughts. I have not tried the new su-zip of LOS so far - will try soon
[Galaxy Tab S2 Original Android Development] papampi:
Any way to get network bandwidth monitor like RR on status bar ?
[Galaxy Tab S2 Original Android Development] noratroll:
in case of no solution I'ld recommend network monitor mini. creates an overlay which you can place anywhere.
[Galaxy Tab S2 Original Android Development] danielfrancisarthurs:
My T815 don't get any mobile network?
[Galaxy Tab S2 Original Android Development] papampi:
Display setting won't switch to night mode automatically and when I click it it brings up the force close/mute settings.

After I enable night and set it to auto it stick to it until screen off , then the display color views as off( full white ).

Even day mode not show correct color temperature.

Anyone else has same issue ?

---------- Post added at 10:57 PM ---------- Previous post was at 10:51 PM ----------

Mine enabled after first setup accounts and reboot for the 1st time.
[Galaxy Tab S2 Original Android Development] vinylzero:
Working great on my T-815, including mobile data (LTE) and fingerprint. Actually it seems to be even better than the last official cm13 build that was available. Now I'm hoping we'll get official nightlies soon, as we now don't even get an official lineage 13 build.

[MENTION=3463426]RaymanFX[/MENTION]: Any plans on what needs to get fixed before the T-815 can be added to the nightly roster? Thanks for your great work!
[Galaxy Tab S2 Original Android Development] risant:
is this a software bug on t810...? the apps cannot move to sd card ...and whenever i formatted a new sd card as internal storage it got corrupted.. I tried 20 diffirent brands of sd card it got corrupted ...what's the solution for this please help
[Galaxy Tab S2 Original Android Development] shabure:
Can you tell me if Netflix is working? Installed RR and AOKP, but the are sadly useless for me when Netflix and my NAS app doesn't seem to work...
[Galaxy Tab S2 Original Android Development] harise100:
No, Netflix is still broken. You can only stream to Chromecast.
[Galaxy Tab S2 Original Android Development] MSe1969:
SM-T815 LOS 13 build?

Hi all,

hope you don't mind me asking about LOS 13.0 for the SM-T815, but I am not sure whether the CM13 thread for this device is still "active", I have posted my question already there (which may be the wrong place):

https://xdaforums.com/showpost.php?p=70879351&postcount=117

In short - I could build a nicely working LOS 13.0 ROM on January 7th but after synch'ing the repo to include the January security fixes, the newly built ROM simply boots into a "black screen" (see the referred post). I have read in the T810 forum mentioning a similar issue (for LOS 14.1 however), which has been fixed now, so I appreciate any advice on how to fix it for LOS 13 (e.g. what needs to be altered in build manifest etc.).

Using 'Nougat' is currently not an option for me, due to the lack of Xposed (ans thus Xprivacy).

To clarify:

1.) I did a clean install (factory reset, no Xposed flashed), before I reported the issue here.

2.) If the tablet is turned into landscape mode and the home button is pressed, about 3cm of the android keyboard on the right hand side is visible, the rest of the screen is blank and black, but it reacts if I tap on the area, where the keyboard would normally be displayed.

Thanks again for any idea!
[Galaxy Tab S2 Original Android Development] bowhunt2005:
Didnt see anyone ask this yet but from what i understand the t817r4 version uses the same hardware as the t815. Is this information correct and will the t815 build work for the t817r4? Thanks for the work
[Galaxy Tab S2 Original Android Development] MSe1969:
Hi bowhunt2005,

I can't provide you with a definite answer, but these are my thoughts on this topic:

The SM-T815's 'internal' device name according to /system/build.prop is gts210ltexx (entry ro.product.device or ro.build.product); the check in the flashable ZIP for CM / lineage is against values 'gts210lte' or 'gts210ltexx'. So if your device's /system/build.prop shows one of these values, you will be able to flash the respective ROM. Otherwise, the ROM will not allow to flash.

You can read this entry from your device using the command

adb shell cat /system/build.prop

- even from an unrooted device with stock firmware, assumed you have established a working adb connection.

Generally spoken, Samsung is known to have different "variants" in use within the same "marketed model" (e.g. "Samsung Galaxy Tab S2 9.7 LTE", which can be SM-T815, SM-T817r4, SM-T819, ...); which turn out to differ in hardware components and thus require an own dedicated ROM build.

Regards, M
[Galaxy Tab S2 Original Android Development] RaymanFX:
Hey everyone, I will kick off official weeklies for the SM-T810 and SM-T815 very soon.

During the last days, I fixed encryption, a few SELinux issues and Google Play Movies.

Regardless of that, there will be a few bugs still present once the official weeklies start, namely:

Fingerprint

YouTube videos zooming in when switching to 1080p

For the YouTube stuff, there is a commit on Gerrit to work around the issue, if I don't find the proper fix soon, that solution will probably be integrated.

Now for fingerprint, you will probably say "oh but it was working in your last build" - and while that is true, there is an issue I was not able to fix until now: the fingerprint kernel driver *must* hold a permanent wakelock to be able to receive input from the sensor.

If I drop this wakelock code from the driver, the FP sensor will work once after the first boot, but not anymore when resuming the device from suspend.

Aaaaaaaaand there's another catch:

You *must* use my builds of TWRP for OTA updates to work: LINK.

That is because TWRP and Android must mount the same partition at /misc for the BCB (boot loader control block) to work. Unfortunately all TWRP builds out there don't mount anything at /misc at all, so they will not be able to handle OTA updates.

Please test the TWRP builds I put up there while I prepare the last steps for weekly builds.
[Galaxy Tab S2 Original Android Development] NeWONEx:
So you are going to drop support of FP in Weeklies build for now. I saw some commits from S5 devs. They worked on it for a while don't know if they solve it or not.
[Galaxy Tab S2 Original Android Development] echo124:
Thanks for your work for G850 ;)
[Galaxy Tab S2 Original Android Development] lodespawn:
Battery Drain

Hey,

So first off nice work on the ROM I've found it works quite well, looks fantastic. Only a couple of issues I can see. Am I reading right that to get the finger print scanner to work you've got the tablet continuously monitoring the scanner? I've noticed a bit of a larger battery drain than the stock ROM, do you think this might be the cause?

The other issue is that every now and then (it seems mostly random) I get an error that says the browser has stopped working. I can try get some info on this one for you, what exactly would you like?
[Galaxy Tab S2 Original Android Development] halloarno:
I noticed inbuild browser fc on every lineage (based) rom (including tab s2, Xperia sp and Xperia t). So not device specific bug. Luckily there are plenty alternatives.
[Galaxy Tab S2 Original Android Development] lodespawn:
Hah indeed, I'm not using the browser so it's not a huge issue for me, I just noticed it and hadn't seen it mentioned in any earlier posts.

Is anyone else getting higher battery drain? I noticed that the device doesn't seem to go to sleep. If I look at my battery history the awake bar never shows the devices moving to sleep mode. I did have "keep wifi on during sleep" set which I thought might be keeping the device up but after turning that off the same issue persists.
[Galaxy Tab S2 Original Android Development] NeWONEx:
Most likely it related to FP issue. Weekly build is very soon, hope if dev find the way to solve it;)
[Galaxy Tab S2 Original Android Development] JustMeToo:
I don't know if this info is entirely true. In my build.prop the tablet, SM-T817W, is referred to as gts210ltecan and as gts210ltevl yet I too can not flash this ROM. I read somewhere (maybe this thread?) that the problem may be that the TWRP I'm using is the 810 flavored and should be the 815 flavored. I looked for a .tar file of the 815 and couldn't find it. I only found the 810 one which is why I used it. The one for the 815 was an .img file and I did't know how to incorporate it.
[Galaxy Tab S2 Original Android Development] MSe1969:
Hi JustMeToo,

but that's exactly, what I said: gts210ltecan / gts210ltevl is unequal gts210ltexx / gts210lte, hence a CM / LOS ROM for SM-T815 (which checks for the expressions "gts210ltexx" or "gts210lte") won't flash, if those expression do not match . . .

Regarding the TWRP, .tar is only a compresed archive (which Odin recognizes), which packs the twrp.img file, you can also directly flash the unpacked .img - if I remember properly, this is what I did, when I rooted my device.

If yout TWRP boots fine however, you should be all set, I think. The recovery is device specific, but a recovery "only" needs to boot and be able to mount and access the device's partitions, it does not need to access network, wifi, camera etc. - so if your TWRP does this, all should be fine in my opinion.

Regards, M
[Galaxy Tab S2 Original Android Development] JustMeToo:
My bad! I thought that the 'xx' in 'gts210ltexx' are place holder for the various model type. :(
[Galaxy Tab S2 Original Android Development] MSe1969:
LineageOS 13 for SM-T815 - SOLVED (work-around)

Hi all,

I was able by myself to solve the described issue here from the same thread: https://xdaforums.com/showpost.php?p=70894401&postcount=221

The issue is the bootanimation.zip file in /system/media on the device:

The "resized" boot animation for the gts210ltexx device in the LOS 13 has only 'one-pixel' pictures, which results from the fact, that the value TARGET_SCREEN_WIDTH and TARGET_SCREEN_HEIGHT are nowhere set! The system cannot handle this, which results in that weird (and broken) behavior.

As a work-around, I have simply deleted the bootanimation.zip file in my build, which brings up the standard aosp "android" boot animation (same by the way with my working January 7th build). In the LOS 14.1 tree, those values have been defined in device/samsung/gts2-common/BoardConfigCommon.mk - this file however looks completely different than in LOS 13.

As I am not sure, how this is organized for all the SM-T8* devices in LOS 13 and since I know, that the relevant people for the gts2 device family are present in this thread, I would like to ask for advice, where to fix it properly, and also to fix that in the LOS 13 tree for gts2-common.

Thanks a lot, cheers

M
[Galaxy Tab S2 Original Android Development] anks329:
If the problem is the screen height and width not being set, then copy the configuration from the 14 branch into the 13 branch. Basically add:

TARGET_SCREEN_HEIGHT := 2048

TARGET_SCREEN_WIDTH := 1536

Into the board common config file and you should be good to go.
[Galaxy Tab S2 Original Android Development] MSe1969:
Thanks a lot, did that, cleared out directory, compiled again and now all is fine.

I'll try to log this also as a change in the LOS gerrit (will be my 1st try there).

Regards, M
[Galaxy Tab S2 Original Android Development] JustMeToo:
There is a new TWRP out, 3.0.3 (I think). It's an .img file and someone posted instruction on how to flash it. I flashed the 815 version and now I was able to flash the RR ROM marked 'gts210ltexx'. So, I guess the person that has said that changing to the correct TWRP version will help was right. I now have Nougat 7.1.1 on my tab. I even asked for a sim card but I don't have one, and never planned on using one, so that I can't tell if lte works or not.
[Galaxy Tab S2 Original Android Development] MSe1969:
Hi, glad it finally worked out for you.

If you flash a ZIP using the ZIP flash method, the script within the ZIP file, /META-INF/com/google/android/updater-script, is executed to perform the flashing. If you use a LOS ZIP for SM-T815, the first line of that script is:

assert(getprop("ro.product.device") == "gts210lte" || getprop("ro.build.product") == "gts210lte" || getprop("ro.product.device") == "gts210ltexx" || getprop("ro.build.product") == "gts210ltexx" || abort("E3004: This package is for device: gts210lte,gts210ltexx; this device is " + getprop("ro.product.device") + "."););

I have actually never tried to flash a .ZIP for a "wrong" device, but this coding clearly states, that the device / product in the build.prop must match. (Of course, if you want to bypass that check, there is plenty of ways to do so :) )

But as said, the most important is, that it works for you and you're happy now.

Regards, M
[Galaxy Tab S2 Original Android Development] bowhunt2005:
Getting ready to possibly try to flash this after i root and check my build prop for correct version. Wondering if the bugs list in the op is up to date. I was thinking i read the netflix bug is corrected now. Am i right?
[Galaxy Tab S2 Original Android Development] bowhunt2005:
So your build prop showed gts210ltecan and it ended up flashing ok once you changed to the t815 twrp?
[Galaxy Tab S2 Original Android Development] otto8:
Same to me: no data connection on german O2/E+. Phone calls and SMS working. Manually created APN didn't solve problem. Recovering "Radio" (modem) from previous working rom didn't work, too.
[Galaxy Tab S2 Original Android Development] Adler12:
The o2 problem has been solved. The problem with the MHL chip is probably larger. The guys / girls have probably no access to the code ...

Das o2 Problem hat sich aufgelöst. Das Problem mit dem MHL Chip ist wohl größer. Die Jungs/Mädels haben wohl keinen Zugang zum Code...
[Galaxy Tab S2 Original Android Development] otto8:
How to solve O2 problem?

Wie löse ich denn das O2-Problem?
[Galaxy Tab S2 Original Android Development] ivanox1972:
This ROM is great as expected from one of XDA kings... I have 1 question: is theming somehow supported? Thanks
[Galaxy Tab S2 Original Android Development] noratroll:
please follow the rules: this is an English speaking forum.
[Galaxy Tab S2 Original Android Development] otto8:
Clean install solved my problem!
[Galaxy Tab S2 Original Android Development] NeWONEx:
Nope
[Galaxy Tab S2 Original Android Development] ivanox1972:
[MENTION=3463426]RaymanFX[/MENTION] I found very big issue in this, for my opinion. I installed rom and all is great. Also install your recovery 3.03 to have ota. First smaller problem ota search not working. Big problem is recovery 3.0.3 not restoring your this rom good. I successfully backup twice totally health this rom, restored and got unusable something.phone fc, empty settings, killed it, unusable. I also backup once stock rom and restored twice perfectly.
[Galaxy Tab S2 Original Android Development] bowhunt2005:
So i went ahead and flashed this on my sm-t817r4 and it installed just fine. I then flashed the micro gapps and the root file in the op. It seems i have root but no supersu app that i can find. Also my wifi wont turn on. But i beleive that to be a hardware issue as that has happened b4. It does not find the sim card but im guessing thats probably normal seeing as its a uscellular tab. I am wondering however if the wifi issue could be related to the rom or if you agree that hardware is the best guess. Thanks
[Galaxy Tab S2 Original Android Development] lewmur:
What options did you choose when backing up? The default is normally just Data,Cache and System. Have you tried checking ALL of the boxes, thereby backing up everything?
[Galaxy Tab S2 Original Android Development] NeWONEx:
Data, System and boot . This is what recommended for backup. Maybe he tried to restore recovery :confused:
[Galaxy Tab S2 Original Android Development] lewmur:
Yes, that is what is recommended. But if that isn't working, do you keep doing it or try something else? The reason the other options are there is that ~sometimes~ they are needed. Checking all of the options makes the backup take longer and requires more space. So, if just backing up the ones recommended works, then fine. But if not, then it only makes sense to try backing up the other partitions.
[Galaxy Tab S2 Original Android Development] halloarno:
Huh? Nope, for backing up a ROM just backup boot, system and data.
[Galaxy Tab S2 Original Android Development] ivanox1972:
Normal, as ever . I had note, note3, note5, s4, s6 a9, tab t700, t800, t715, t810, tt705, t815. All ever root twrp... Always never problems with backup. Default options. Try to restore backup please
[Galaxy Tab S2 Original Android Development] lewmur:
Your mind is made up. Don't dare confuse you with facts.
[Galaxy Tab S2 Original Android Development] ivanox1972:
Not good. I tried with RR 7.1 and got same results, it is expected become it is same rom in essentials as cm 14.1. I backup usual 3 partitions, no errors, restore and got error com. Android. Phone has stopped and it is unable. I tried to reflash old 3.0.0 twrp and to restore rr wit it. Got same so last thing I can try is reinstall rr or this rom and backup it with old recovery and try to restore. If not work, I don't know where is problem. Is it nougat or root or...??? All time any version twrp backup nad restore rooted stock rom perfectly ...