yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] tripLr:
As I told [MENTION=6005084]ripee[/MENTION], it's about solving puzzles.

If u read my post, fingerprint works in your build.

And since you went through the code and fixed errors, that's awesome.

Even though he don't have a 710, he has been building lots of stuff in his spare time.

As for being famous, he does not even sign "this is built by ripee " in his stuff.

Untill he started in the note 4 lineage thread, Dev had stalled because he was looking for fixes.

I am a user working on being a Dev, so I am in the support the Dev category by reporting bugs.

If u help by posting your hard worked out solutions, everyone benefits.

I bet your build will boot on all 4 varients which could result in thousands of happy peeps.

But u only post for 2 because you admit you only built for your device.

It's kind of pointless to post a Rom in XDA without posting how u did it, so everyone benefits.

[MENTION=6005084]ripee[/MENTION] as a Dev without a Device is still a resource for everybody. He has skills and time he donates for everybody.

I am using XDA as a change of career and to learn.

So if you post your source, everyone who has an exynos device benefits.

Including the new devices, because most likely Samsung copy's and pasted their old code to run on a newer device.

Case in point.

The 710 is a 64 bit CPU.

You built a 32 bit Rom.

Oreo 8 and Oreo 8 trebel require 64 bit. So nix on my note 4,

But if u post your sources on something NOBODY ELSE GOT TO WORK, the possibility of continuing on to greater things for everybody .

Plus , you get beer money and recognition for your hard work.

Not a bad thing..

So what I would like to see as a user , can't we all just get along ? Haha

---------- Post added at 12:46 AM ---------- Previous post was at 12:43 AM ----------

As for your build prop, it's an output generated by your compiler.

I am just reading code to figure out how your device tree was compiled. So I can duplicate it on my new Ubuntu laptop I am making .

---------- Post added at 12:47 AM ---------- Previous post was at 12:46 AM ----------

So speaker output on mp3 playback is kind of muted

Checking streaming services...
[Galaxy Tab S2 Android Development] h4waii:
Dirty flashed from previous unofficials to your build. Everything seems great!

Thank you for working on this, and making it available for us. Curiously, are your sources / modifications available anywhere publicly?
[Galaxy Tab S2 Android Development] mtnez.david:
Hello everybody, thanks a lot guys for the awesome work you are doing for this device. I own a T710 and if I get some free time I want to flash this rom and do some testing. If anyone that does not have the device wants me to do some debugging, just make me know. I'll post here once it's flashed...
[Galaxy Tab S2 Android Development] tripLr:
im one of his testers.

he has like a 50 processor 200 gb ram server haha to make builds
[Galaxy Tab S2 Android Development] T_I:
Good to see someone got the camera working. [MENTION=242033]bonuzzz[/MENTION] please commit your patches to lineage (repo upload), so we can finally move to official for this device.
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=4557146]T_I[/MENTION] I dont use git, so i will upload complete sources when I fix last bugs here
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=5624167]TotalNoobTrucker[/MENTION] he could have 100500 cores and unlimited ram, but to fix microphone by adding proximity sensor to kernel config, that's just funny

ps: bootloader here restricts only 32bit and oreo doesn't require 64 bit..
[Galaxy Tab S2 Android Development] T_I:
Thanks, would love to see what I did wrong with the last bits. (as they work on T810, but not 710, couldn't debug my tablet good enough, still learning)
[Galaxy Tab S2 Android Development] bonuzzz:
new builds have been uploaded

camera shooting fixed

gain volume in mic and speaker

sources also have been uploaded

all the links are in op
[Galaxy Tab S2 Android Development] ripee:
Thank you [MENTION=242033]bonuzzz[/MENTION] for making your sources available. I did notice that you're using the original gts2-common repo, which does not allow Netflix to function properly. You can fix this by making the following changes:

Delete mediacodec.te

Update mediaserver.te

This will work in T710 and T715 since it's in the common repo.

On another matter, would you have anything against my submitting your common blobs to TheMuppets so that they can be included in official gts210wifi and gts210ltexx builds? It looks like my gts210wifi can finally have a functional fingerprint reader!
[Galaxy Tab S2 Android Development] T_I:
Thanks for posting the code, I'm doing a build for 710 and 810 with these changes to see what changes on both devices. ( [MENTION=6005084]ripee[/MENTION] we first need to confirm that changing the blobs won't cause a problem)

I see you went back from compiling dtb to including a pre-compiled one. Looks like we have a lot of work to integrate these changes. (but at least we have a working base to start from, that helps a lot)
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I haven't tried netflix on tablet.

At least you should ask [MENTION=4557146]T_I[/MENTION] for permission, because he supports official repo. And I'm not sure you test everything

Are you going to fix fingerprint with these commits? https://github.com/ripee/proprietary_vendor_samsung/commits/cm-14.1

so, great! You just copypasted my vendor blobs without any testing. All users will say thank you, when you break their tablet functionality. As I said before, you don't know what you are doing.
[Galaxy Tab S2 Android Development] mac231us:
link file has -20180101 is it supposed to be 20180102 (as in thread title) or is it 20180101? Thanks so much for your work!
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=3105136]mac231us[/MENTION] . that's ok
[Galaxy Tab S2 Android Development] Shaolian:
Hi, [MENTION=242033]bonuzzz[/MENTION]. Thanks for your ROM and for sharing.

I have not own a Tab S2 yet, but am trying to decide between a T715 or a T719. All my previous phones I've ended up installing either a CM or AOSP rom, so I'm a big fan of an as close as stock Android experience.

I'd just like to ask if there's anything that is not working for the T715 in this ROM? Like can we make calls using the in-built earpiece, or can we adjust the vibration strenght? Seems like everything else is working fine, or am I missing something?

Anyways, thanks all for the sharing :) !
[Galaxy Tab S2 Android Development] PaterProx:
Can anybody please test if you are able to change vibration strength in the latest build?

Just go to settings - > search function - > type vibration strength and click on "vibration strength". now will you just get into the "other sounds" menu or are you actually able to change it? Thanks
[Galaxy Tab S2 Android Development] T_I:
I own both the 810 and the 813 and the latter is faster then the first. Also it has a snapdragon as core cpu, so it's more common to develop for. There should already be an image for the 719. I'd check the gts28veltexx build to see if there are issues.
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=4557146]T_I[/MENTION] I didn't test with compiled dtb.

common repos are common for 71x because i make for them only. you should decommonize some files at least in vendor, in particular sensors.
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=7130270]PaterProx[/MENTION], no. because I have to patch kernel for this, but I dont want to do this before I make common kernel for s2 and note4. if you add this parameter, i will write about it in changelog. [MENTION=3523490]Shaolian[/MENTION] t719 doesn't have any aosp builds. probably someone will make it in future.

t715 performance has been greatly improved in last builds. I think you will not notice significant differences in performance between 715 and 719. [MENTION=5075128]LuK1337[/MENTION] is advanced developer, but he supports only wifi models. I suppose modem part will be a weak place, if aosp rom will ever released for 719.

But I anyway will choose t719 because nobody else is working on exynos5433.. this platform has stable nougat now, i cant say anything about oreo and further releases.

Forgot to say about battery. I dont know about lineage in t719, but 715 has battery drain for now compared with stock

And also 719 has chances to get stock oreo.
[Galaxy Tab S2 Android Development] Shaolian:
Wow, thanks for all the advices. I'm actually using a Huawei Mediapad X2 (7-inch, 16:10 screen) now. It's a great device, and I have no complains about. It also has a very stable CM built for it too.

But my lust for an ever bigger screened "phone" has reared its ugly head again :p After some searching, the Tab S2 8.0 looks like the perfect tablet/phone to me. Great ergonomics, design and competitive CPU.
[Galaxy Tab S2 Android Development] majorkid:
Hey I was trying to compile a ROM using your device tree and this is the error I got , Anyone help please Click Here
[Galaxy Tab S2 Android Development] bonuzzz:
you forgot one more repo
[Galaxy Tab S2 Android Development] majorkid:
Yes , I fixed it , forgot to sync gts2-common repo . but now I got another error

Another Error

some specific repo is missing
[Galaxy Tab S2 Android Development] bonuzzz:
https://github.com/ripee/android_de...mmit/67dea02e33c7a41e4ab85e7f8a3dd4790b455cd4
[Galaxy Tab S2 Android Development] mfhotdog:
Hi,

thank you for your nice work. I have a problem, I flashed the LTE Version on my T715, but it is beeing recognized as T815. Everything is working with this excpet the LTE Modul. The mobile card is not usable and I have no service at all.

Any idea how I can fix this problem?

Thank you very much.
[Galaxy Tab S2 Android Development] ripee:
bonuzzz, you asked how I'd go about fixing the fingerprint sensor in gts210wifi and gts210ltexx. First I'll fork your device trees and build my own for the gts210's, then I'll worry about the blobs.

I was just about to mention the liblights in your gts2-common repo, but I also noticed that you commented out the gts2-common entry in your gts28wifi dependencies file, but not in the gts28ltexx one. I noticed because I take advantage of these dependecies so as to keep my roomservices as clean as possible. Since your gts28ltexx isn't commented out I thought this was something very easy to overlook.

About Netflix, I can assure you that T_I's old fix is the only one that actually works, which is why I've been using it since I started building for gts210wifi months ago. Netflix has always worked since, despite having to sideload the app on rooted roms. I know that he and other devs intended to introduce a better fix but they never got around to it so I just stick with what works.

I built today's gts210wifi using your kernel, gts2-common, and blobs and my tablet is noticeably snappier than yesterday, although I will look into the fingerprint sensor later, so thank you very much for sharing your repos!
[Galaxy Tab S2 Android Development] bonuzzz:
oops:) seems I broke modem in last build. I will upload fix soon
[Galaxy Tab S2 Android Development] mfhotdog:
Ahhh, okay. :) I will flash an test the new version.

Thank you
[Galaxy Tab S2 Android Development] bonuzzz:
I always comment out repos in dependencies, so do not pay attention here

I've tried your fix, but it doesn't work for me. I think I have broken codec. But that T_I commit doesnt make sense anyway, because we dont switch stagefright to less secure mode.

dont't forget about sepolicy. you should get mobicore working. fingerprint will not working without it.
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I mentioned you, because [MENTION=7078341]majorkid[/MENTION] is using your roomservice. after mention i had look at your repo and sent him exact commit
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=8831265]mfhotdog[/MENTION] flash this file as boot image in twrp

https://yadi.sk/d/HbCoact83RAUwH

i will upload full rom in 30-40 min
[Galaxy Tab S2 Android Development] mfhotdog:
Thanks its LTE and Voice is working now. But in Settings - Status it still says " Device Type: SM-T815"

I will try to flash the full rom and see if its stating the correct Device Type and let you know.

Thank you ;)
[Galaxy Tab S2 Android Development] bonuzzz:
it's just cosmetic parameter. anyway i replaced it to t715 and new builds will show the right model
[Galaxy Tab S2 Android Development] mfhotdog:
Thank you very much. I just noticed it. ;)
[Galaxy Tab S2 Android Development] bonuzzz:
the link for t715 has been replaced
[Galaxy Tab S2 Android Development] tripLr:
hi from total noob trucker

got my build laptop up, working on compiling a source next. thanks

new username

tripLr
[Galaxy Tab S2 Android Development] ripee:
I don't want to distract away from gts28 by talking about gts210, so I'll just mention the changes which are most likely common to all 4 variants: I took bonuzzz's gts28wifi blobs and added these two files from stock T810ZCU2CQL4. After switching over to bonuzzz's gts2-common repo, the screen no longer goes from bright white to yellowish and back randomly, all apps and settings launch quicker than with lineage repos. Bluetooth is the same as with the lineage repos and the fingerprint sensor doesn't even appear in the security menu. The camera is snappier and wifi is more stable.

However, I have yet to try importing the lineage kernel's gts210 defconfigs into bonuzzz's kernel. I will do so and implement his changes (about 8 lines). Unfortunately, bonuzzz, your kernel doesn't work in building either gts28 with your device trees or gts210 with the lineage device trees; ir errors out around 6%. Building with the lineage kernel works of course but I'm interested in those 8 lines you included that are not in the lineage kernel.
[Galaxy Tab S2 Android Development] Giuskiller:
Hi, installed right now with opengapps and addon for root. The problem is that fingerprint is claimed to be working but actually it isn't fully working. For example it let me register an ID fingerprint, but when i'm trying to unlock my device it recognizes the fingerprint 2 times on 10. Don't know what problem could be, hope the feedback can help
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I can't understand you goal. You and [MENTION=5624167]tripLr[/MENTION] are spamming everywhere without respecting other users. I think no one else is interesting what you are doing. You already did a disservice with twrp...

So, if you and [MENTION=5624167]tripLr[/MENTION] want to write something, start your own topic. But, please, stop spamming in my topics anymore.

Thanks in advance
[Galaxy Tab S2 Android Development] lahegry:
Is it just me, or can anybody else get Firefox to work? It constantly force closes on me.
[Galaxy Tab S2 Android Development] ripee:
XDA is a community of people who work to help one another for the benefit of the community rather than the benefit of their own egos.

If my goal isn't obvious, let me write it down for you: according to the OP, you claim to have fixed all the bugs in gts28wifi and gts28ltexx that have been plaguing the official lineage repos. My goal is to use whatever resources are available to fix those same bugs in gts210wifi and gts210ltexx.

A disservice with TWRP? I don't think we are living in the same reality. As someone who is new to TWRP development, how else could I have raised awareness about a new build given that no builds had been released for our 4 variants since last March by any of the established gts2 devs? On that matter, I took the time to learn how to build TWRP and I got official TWRP support for all 4 variants.

You also don't seem interested in restoring Netflix support in your builds. I wonder if you think no one else is interested in that either.

Rest assured that I intend to start a separate thread once I figure out the fingerprint sensor in gts210.
[Galaxy Tab S2 Android Development] mac231us:
ripee... you do have the talent, skills and sometimes more importantly the motivation to take a look at things that may be dormant...yes, you would be served better (as well as the community) if you started your own threads-it would get due credit I am sure. Thanks for your work!
[Galaxy Tab S2 Android Development] bonuzzz:
Yes, and to respect other people they create separate topic to discuss their problems. And I dont know why you write here about error on 6 percent of building without any logs. Or why [MENTION=5624167]tripLr[/MENTION] writes how he installs linux on his notebook...

I think [MENTION=4557146]T_I[/MENTION] is doing the same work. At least we could cooperate...

I've created another topic for discussion sources here https://xdaforums.com/tab-s2/orig-development/sources-lineageos-14-1-t3729720 You and [MENTION=4557146]T_I[/MENTION] welcome.

This topic is to discuss my builds only. It's not about my ego, just if someone writes about bug, I don't know what build he uses.
[Galaxy Tab S2 Android Development] lahegry:
.......soooo no one has been having issues with Firefox but me[emoji6]
[Galaxy Tab S2 Android Development] bonuzzz:
Just installed firefox, it crashes for me too
[Galaxy Tab S2 Android Development] NoCoolNamesRemain:
Just dirty flashed 20180101_233133 overtop of 20171130_164423 and am happy to report that the fingerprint reader issue mentioned by [MENTION=5915249]Giuskiller[/MENTION] (post #86) seems to be resolved.

Thank you [MENTION=242033]bonuzzz[/MENTION]!
[Galaxy Tab S2 Android Development] Giuskiller:
How this could be? I flashed with a clean install the version 20180102_214553 wich is supposed to be the latest avaible and here i had (and still having) the issue xD tell me how you resolved it
[Galaxy Tab S2 Android Development] Giuskiller:
Here are some logcats, maybe they can help
[Galaxy Tab S2 Android Development] engine95:
Everything is working for me also. I'm running it as dual boot and it's stable and smooth.

Nice work [MENTION=242033]bonuzzz[/MENTION]. Thank you

Edit: I'm running with stock Gapps, so all Google apps are working also. Haven't tried Firefox.

Nice to have another fully working option to run as a DD.

Having the Pixel option is nice too.
[Galaxy Tab S2 Android Development] bonuzzz:
check my repo again

Why does it happen? Because of inproper gitignore in Los repo
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=5915249]Giuskiller[/MENTION] make clean install with wiping data
[Galaxy Tab S2 Android Development] ripee:
Almost there with your revised kernel. As soon as I am able to build my own gts28wifi I'll be able to narrow down the fingerprint on gts210.

Makefile:130: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
make: Leaving directory '/home/ripee/android/lineageos/kernel/samsung/gts2'
[ 12% 4156/33870] target Java: ims-com...RIES/ims-common_intermediates/classes)
Note: frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[ 12% 4156/33870] target Java: voip-co...IES/voip-common_intermediates/classes)
Note: frameworks/opt/net/voip/src/java/com/android/server/sip/SipService.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: frameworks/opt/net/voip/src/java/com/android/server/sip/SipService.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[ 12% 4156/33870] target Java: service...ES/services.net_intermediates/classes)
frameworks/base/services/net/java/android/net/util/ConnectivityPacketSummary.java:376: warning: non-varargs call of varargs method with inexact argument type for last parameter;
return String.format(MAC48_FORMAT, printableBytes);
^
cast to Object for a varargs call
cast to Object[] for a non-varargs call and to suppress this warning
Note: frameworks/base/services/net/java/android/net/ip/RouterAdvertisementDaemon.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
[ 12% 4156/33870] target Java: icu4j (...LIBRARIES/icu4j_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: external/icu/icu4j/main/classes/core/src/com/ibm/icu/impl/Relation.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/ripee/android/lineageos'

#### make failed to build some targets (04:19 (mm:ss)) ####
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I don't know how you build. This error is out of my config
[Galaxy Tab S2 Android Development] ripee:
I build according to _mone's [GUIDE] Build LineageOS 14.1. This way works for all lineage-based sources, both official repos and forks. I build regularly for a handful of devices and I've never had a problem. I'll look into it on my end.
[Galaxy Tab S2 Android Development] bonuzzz:
I sync sources once a month. last sync was 14th december. probably something has been broken with new commits... I don't know... Maybe the real error is not in your log...
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=6005084]ripee[/MENTION] I think It will be easier for you to add support for t81x to my sources than trying to port my work to official one.
[Galaxy Tab S2 Android Development] lahegry:
[MENTION=242033]bonuzzz[/MENTION]

Do you have a telegram group? Not to be "That Guy" but it's starting to get a little muddy keeping track as to what's going on.
[Galaxy Tab S2 Android Development] NoCoolNamesRemain:
I spoke too soon; fingerprint reader is not working to unlock most of the time as originally reported.

I am going to learn how to access the logs and see if there are any clues in them.

Has anyone had any success with multiple profiles? Only my primary profile is stable. All others crash frequently. For example, if I reboot and select a profile (other than primary) on many occasions the cLock widget will read "Loading widget..." and the desktop wallpaper will be missing. After about 30-90 seconds the device will show the LOS loading screen indefinitely. A hard reboot is required at that point.
[Galaxy Tab S2 Android Development] mac231us:
anyone having problem making calls? For me, the screen goes black although the call is on (the sound seems to be coming from external speaker not the internal one for the ear as it is especially loud like a speakerphone) pressing home and other buttons cannot get rid of the black screen (only returns after call has ended) Thanks

edit: my device is the T715

Caller can hear the other end and vice versa (just the issues above) thanks
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=2484493]lahegry[/MENTION] . no, i dont have telegram group and i'm not going to create one [MENTION=2317358]NoCoolNamesRemain[/MENTION] I dont have problems with fingerprint. but i use clean installation with only couple of programs. Physically sensor is working and you able to lock and unlock. I don't see any lie here in original post.

What about mutiple accounts, the logic is same as on official build.

[MENTION=3105136]mac231us[/MENTION] i haven't touched call settings. But i remember posts about the same problem (black screen during call) on note4, so probable i will take a look later
[Galaxy Tab S2 Android Development] mac231us:
...about

[MENTION=3105136]mac231us[/MENTION] i haven't touched call settings. But i remember posts about the same problem (black screen during call) on note4, so probable i will take a look later[/QUOTE]

just found out that the stock TW 7.0 itself suffers from the same issue (screen black during call and prox. sensor does not work)

not so on LL, not used MM much to recall