yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] engine95:
Synapse and WireGuard infos

SYNAPSE Kernel Tuner​

Well, because Synapse is built in now, here's some needed info on it:

Synapse is an awesome and custom built kernel tuner. It can do so much more than a lot of other tuners. And because we have Exynos processors, it's about the only one we can use. But it can create a lot of problems getting to work. Hence this post. :silly:

I decided to make this built in instead of a flashable add on. It's actually easier and less invasive to do it this way.

UCI, is what Synapse uses to work. It's built into the ramdisk. I've added a lot of tunables and may add more later.

Now for the fixes and problems you WILL run into:

If you have issues, make sure to check out these threads. As they will probably have better info about Synapse issues. https://xdaforums.com/showthread.php?t=2736986 and https://xdaforums.com/showthread.php?t=3558888

No UCI support detected These are the famous words you WILL run into.

When will this show up?

When Synapse is first installed

On reboot

When you've pushed your Tablet too far

The fixes:

On first install from the Playstore. You will need to go to Settings>Apps>Synapse>Storage. Then select "Clear Cache", THEN "Clear Data. In that order!!

You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".

On reboot: This usually works unless you've messed up the settings or flash another kernel

On reboot select "Menu" and "Close all".

Open Synapse and hit "CANCEL" to have your last settings applied. (I know it's not normal but it works)

Close synapse, and reopen it to make sure of settings. (If "apply or cancel" don't show up at the top, you're good to go.)

Worst case scenario and for flashing new kernel:

You will need to go select the "MENU" button and Close all. Next go to Settings>Apps>Synapse. Select "Force stop". Select "Storage". Then select "Clear Cache", THEN "Clear Data. In that order!!

You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".

If you follow the above, Synapse will work. It hasn't failed me in over 50 tests, probably more. :silly:

WireGuard VPN​

Read about it here: https://www.wireguard.com/

XDA Thread here: https://xdaforums.com/android/development/wireguard-rom-integration-t3711635

For install and use, read here: https://xdaforums.com/android/general/guide-how-to-wireguard-android-ubuntu-t3723544

Download the "WireGuard" app from the Playstore.

I used Azirevpn. Just follow the link on the install above. Create your account. You'll get an email to confirm. Sign back in and select "WireGuard" for your config. Open WireGuard app, select the + and "create from file or archive" select the config from azire. Done

For now it's FREE so you have nothing to lose. Just be aware that WireGuard is still under development.
[Galaxy Tab S2 Android Development] engine95:
715-2CRB1 and 815-2CRA3 source has been requested and will get built when released.

Things to come: (probably)

WireGuard

NTFS - WRITING to. It does everything but WRITE to NTFS USB's

Possibly raise OC on big/LITTLE 2.2Ghz and 1.6Ghz- These were giving some issues on the initial release. Even though the Tab can go to 2.5 and 2.0 respectively, it's just pushing it way too much. Even 2.2 and 1.6 are too much for safety concern.

GPU control - this one is gonna be a bugger. But we'll see

And ?????
[Galaxy Tab S2 Android Development] Androbots:
[MENTION=1280108]engine95[/MENTION] awesome job sir but as of now my tab is confiscated by my parents due to exams...?

---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------

Yeah GPU control is something I personally would love to see because I have heard that the Mali T760 MP6 can go upto 700mhz but in any task whether light or heavy my tab atleast stays at 160mhz the lowest for all the time causing huge lags and TBH OC settings stay on A53 cores for longer amount of time so go ahead and overclock them to 1.9ghz talking about the the A57 cluster those CPUs heat up like insane and suck power like anything on the device so better to leave them at 2.0ghz or maybe like the Exynos 7420 2.1ghz..
[Galaxy Tab S2 Android Development] engine95:
Well that sucks. ;) But these Tabs are addicting. Guess you just got an intervention. :p

Anyway, when you can, give this RB1 a shot. I think I6 had some tuning issues. (my mistake) It was fine until it was tuned. Mainly in the big, A57 cores. This one should run much better.

A57 tests show that they are more efficient, but can eat power like crazy if needed. I know they can easily be undervolted by at least 2 steps which will help with heat. And/or drop the A57 clock down to 1500-1600Ghz and (I may be wrong on the direction) lower the High HMP from 479 to maybe 400-450. HMP built in is 700, but Samsung has lowered it to 479 with hard numbers. Synapse will allow HMP to be controlled.

It's a big dance configuring these kernels. Between Overclocking, Undervolting, and HMP, it'll just take time to find what works for you.

This kernel, with light use is at 266Mhz for the GPU most of the time. I haven't pushed it to see how much time it'll spend at 350,420,500Mhz. I think it may go to 600 stock, but I'm sure you'd need to underclock the CPU's to get it to run there. Again, heat is the controlling factor. Screen Protectors and cases both retain heat also.

Edit Half hour playing Eternium, all stock settings, 60FPS. Tab was just warm. GPU at 266Mhz most of the time. With tweaking, I'm sure I can get it to run cooler and GPU higher if needed
[Galaxy Tab S2 Android Development] Androbots:
Edit Half hour playing Eternium, all stock settings, 60FPS. Tab was just warm. GPU at 266Mhz most of the time. With tweaking, I'm sure I can get it to run cooler and GPU higher if needed[/QUOTE]

[MENTION=1280108]engine95[/MENTION] that 266mhz just causes the lag I saw my tab go as far as 600mhz for 3secs which is insane.

---------- Post added at 02:05 PM ---------- Previous post was at 02:05 PM ----------

Really need GPU control
[Galaxy Tab S2 Android Development] engine95:
So I found that setting HMP was broken. So I have spent the day working and testing HMP and disabling GPU DVFS. See screenshots.

As you can see, all at stock settings, they run the same. But I've gotten them to use the GPU more now.

BTW, if you've used the DVFS disabler tricks or scripts in the past, they haven't worked. (At least on RB1, and I'm pretty sure I6 also) But they will now. Everything I had to do for HMP and DVFS was in the ramdisk. So there is no source for it.

Look for V1.1 tomorow
[Galaxy Tab S2 Android Development] Androbots:
U mean GPU control is coming soon? Also does this show up that inexpensive looking kernel not senforcing crap?

---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------

Also I am getting my tab today for an hour so will test this kernel and report back..
[Galaxy Tab S2 Android Development] engine95:
GPU control maybe later. It's not on my priority list and its a lot of work to get it. If we don't get an update in the next month or so, then I'll build a kernel with as much as I can. My git skills aren't the best so merging source hasn't worked well for me. I have to start from scratch with each update. And building 4-5 kernels takes a lot more time. I tried to unify them a while back but there are about 10-15 files that are specific to each Tab.

In the past, I've mainly dev'd on my S2, read, surf, but never games. So I've been trying some games as of late. With V1, everything worked smooth and clear. With V1.1 and it scaling the GPU better, ONE TIME I noticed some artifacts and elements showing up black instead of the normal. It may have been random, but I'm still thinking that controlling the GPU isn't going to help as much as you think. That's another reason I'm not in a hurry to work on GPU.

As for the Seandroid message, yes its just a nuisance. But if you root using SuperSU, as I've posted in the OP, there is no message. Magisk doesn't pack the ramdisk the same way SuperSU does. If anyone knows the fix I'll give it a whirl. Personally, I'm just not a fan of Magisk. And SuperSU has been crap since Chainfire sold it. 2.82 was the last and best SuperSU and works great on this Tab. So that's the one I suggest.

I tried to incorporate WireGuard a few days ago, but it wouldn't build. So that's gonna take some work.

NTFS still won't write to NTFS disks. I don't know what's up with it.

So, I'm just going to try and get all the bugs worked out, which I think I have, then the addons will come later. DVFS just happened to be in the area I was working on for the HMP fix.

I'll get V1.1 uploaded and posted in the next hour or so...

Edit: V1.1 in OP. HMP reworked and DVFS for the GPU can be disabled now with those scripts that change permissions. I saw no difference running without the script. But GPU scales more now either way.
[Galaxy Tab S2 Android Development] bonuzzz:
[MENTION=1280108]engine95[/MENTION]

fix fo seandroid

echo -n SEANDROIDENFORCE >> boot.img
[Galaxy Tab S2 Android Development] andyroidking:
T810...A OK. After the initial right after flashing battery drain everything is great as usual. Back to great battery life and very stable. Haven't played with any clock settings or Synapse. Probably won't unless I see some need.
[Galaxy Tab S2 Android Development] engine95:
Really?! Can it be so simple?! A few months ago I wasted a lot of time to try to fix that. HUGE THANK YOU!!!!!:):D:good:

Anyway, V1.1a is up for the 710 and 810 just fixed the "Kernel is not SEANDROID enforcing" when using Magisk.

715 and 815 will be worked on when I get source.
[Galaxy Tab S2 Android Development] bonuzzz:
You welcome!

For t715,t815 use sources from wifi model. They don't have any difference.

Just noticed, you have dedicated sources for every models. It's easier to use one sources with several defconfigs. Save your time :)
[Galaxy Tab S2 Android Development] engine95:
I tried that very thing. I also tried to merge source. But peoples infos keep showing wrong. Or something got broken. I think I tried with Marshmallow and haven't tried since.

Only one time has Samsung released source as 710/810. So I just build them all separate now.

I know on Nougat, I've tried to cherry-pick my own 710 commits and had them conflict with the other 3. Screen, battery, touch and others I can't remember.

Also, on my early commits I used to write them myself. Now I try to find the actual commits and cherry-pick them so that people looking have the infos that might go with them. Cherry-picking saves me a ton of time now. ;)

Thanks for the thought though. :good:

On another note, and now I remember why I don't like Magisk. It's slower than SuperSU. I think Magisk breaks Synapse "Swap" infos. See Pic. It grant SU rights too late to work with Synapse. And I have Synapse starting very early. I guess I may have to rework Synapse again if it is indeed breaking swap info.

So what I need is for someone rooted with Magisk, to go into Synapse and look at the "Memory" page. For me it was blank and said it couldn't read the info. All the writing is red. With SuperSU, it works just like the pic.

Let me know how Magisk looks and I'll go from there. I really hoping it's just my Tab messing up. I need to try Magisk again.
[Galaxy Tab S2 Android Development] Androbots:
Magisk messes with memory tab in synapse I can confirm that I use magisk just because of its systemless modules
[Galaxy Tab S2 Android Development] engine95:
First off, I need/want to apologize for the direction this kernel is going to go. In all my years (Cupcake) of building ROM's, Kernels, and Theming, I have never chosen a hard line. I've always given people what they wanted. And adjusted things to everyone else's wishes.

My work has been for me, and shared with you. So I need to go in that direction.

Magisk just isn't allowing me to do that. And it slows the system down, but not as bad as Xposed. Yes, it may be the latest and greatest, but that's not always a good thing. IF we, by some chance, get Oreo, then there's no choice.

So as of now, I will not support Magisk or Xposed on this kernel. I will still make sure the "Kernel is not SEANDROID Enforcing" is removed for those of you chosing to use Magisk. But if you have issues, I may not be able to help. Sorry.... :(

I'm gonna be quite busy for the next month, so my work will be slower coming out. But it will still continue.
[Galaxy Tab S2 Android Development] engine95:
V1.2 is in OP for 710 and 810!!! See/Read changelog

WireGuard VPN is built-in, in this version - See/Read post #2 for install

Also, if you use Synapse, you probably need to clear all its data. That's in Post #2 also

I had to modify WireGuard for it to work for us. Maybe because it's built-in and not a module. So far it seems to be working fine and right with the basic tests I've done. But I've never used a VPN before now.

The nice thing, and/or bad thing about WireGuard is it's still under development. All the reviews rave about it though. And for now, It's Free!!!

I may have made mistakes with WireGuard. So if you use VPN, or have some knowledge of them, make sure to thrash and test it out.

Just a little side note, but I'm starting to notice that anything built as a module, Magisk, xposed, ntfs, etc really seem to slow this Tablet down. That's why I'm just building things in and using SuperSU.
[Galaxy Tab S2 Android Development] engine95:
715 2CRB1 V1.2 is in the OP!!!!!

It is untested, so I'm calling it BETA. Make a full backup before install!!!

It should boot up just fine. Really, I just need to know that it works. SuperSU is Recommended. Magisk breaks Swap info in Synapse

Let me know if it works. :D

815 was just being uploaded so I couldn't DL it completely. I'll get to it when I can. Maybe tonight, maybe a few days. But I will get it built.

Enjoy :)

Edit: [MENTION=7243932]Skulldron[/MENTION] give this one a go. ;)

Edit #2:815 2CRA3 V1.2 is in OP-same info as above with 715 Just wanted this done and out before the holiday.
[Galaxy Tab S2 Android Development] v00d007:
Can "Adiutor" tune this kernels or is Synapse the only tool that works?
[Galaxy Tab S2 Android Development] engine95:
It's in the OP.

Synapse is the only tuner that will do it all. But only with SuperSU.

Magisk and/or any other Kernel tuner will work, but won't do everything I've built in.
[Galaxy Tab S2 Android Development] IngoPan:
so this dosnt work with xposed installed ? too bad ;(
[Galaxy Tab S2 Android Development] engine95:
I never said that. It just may not tune right. It'll run like stock kernel. Just better. ?

If you have issues installing Xposed or Magisk, you're on your own. I don't like the way either are working on this tablet. So I don't recommend them.
[Galaxy Tab S2 Android Development] engine95:
V1.2.1 for all in the OP See/read "whats in this thing" Just a small update.

GPU DVFS permissions are re-enabled. I didn't like the way it ran without them

WireGuard updated to v0.0.20180708
[Galaxy Tab S2 Android Development] engine95:
Things have been crazy for me this last month. So, sorry for no updates.

I did just find that the 710 has an update, RG1 released in Aug. I have no idea what's in it. I just found it. Just an FYI ;)

Edit: Make that RG2. I can only find it on Sammobile.com
[Galaxy Tab S2 Android Development] engine95:
Last build for RB1

V1.3 is on the OP!!! See/read the "So what's in it"

Total rewrite to build the kernels.

Synapse is removed

WireGuard to latest 20180809

Some infos:

I was FINALLY able to combine source. Thank you Samsung. :) So now all builds for the RB1 are under the 710 git.

Build scripts now for each variant

Using latest AIK for correct permissions in Ramdisk. I've been using an older mkboot

This is the last build for the RB1 kernels. They work just fine on RG2, just so you know

I finally decided I needed to update/upgrade how I build. I've spent a lot of time re-learning and rewriting things. Gotta teach this old dog to keep up with the times. :D

Magisk is what I will use now. As well as AIK for packing kernels.

Look for 2DRG2 kernels coming soon. It'll be in a different thread because of the way I'm building now. Git wanted WAY too much work for me to try and merge it into RB1. I spent a couple days trying.
[Galaxy Tab S2 Android Development] andyroidking:
will test... tablet is starting to fade though... the crack is making phantom touches if i move it too much. Gonna miss this tablet...

---------- Post added at 06:17 PM ---------- Previous post was at 06:07 PM ----------

810 w/SuperSu boots fine. Thx!
[Galaxy Tab S2 Android Development] Androbots:
[MENTION=1280108]engine95[/MENTION] did you like remove synapse support just because m tweaks was too good? ?
[Galaxy Tab S2 Android Development] IngoPan:
so this dosnt work with xposed installed ?
[Galaxy Tab S2 Android Development] engine95:
Well that sucks. I know what you mean though, this really is a nice Tablet.

Just an FYI, everyone but the 810 got an update. 710 is RG2, while 715, 815 is RH1. Hopefully the 810 will get an update as I need its Ramdisk to build the new kernels. There were about 9 changes in it and I'm not sure which one would apply to the 810

Not really. As I've said, Synapse is the only one that will do everything I have built into it. All others lack in some area.

I have to build UCI which is the source that Synapse runs on. So that takes a lot of extra time. I guess I was just lazy and left it out. ;)

I actually just run my kernel with no tuning and it does what I want.

As I answered the last time, I just don't support xposed if you have issues. I haven't seen anyone that does. Everything runs on the kernel, so installing it will be just fine. But if you have issues, look to xposed for help, as it won't be the kernel causing the issue.

On another note

Samsung just released source for RG2. It took over 2 weeks, but its finally out. But now I need to request RH1 source to see if any changes. I can't imagine there being many as they are only 2 weeks apart. End of July and first part of Aug, which would reflect the G2 and H1. Although the kernels are 2 months apart.

Samsung made a lot of changes from RB1 to RG2. 47ish compared to stock. And if I merged it, almost 200. That's why I'm starting from scratch. I make a lot of changes in base source just to get it to compile right.

The changes I remember are to battery, with the 210's (10 inch) getting the most reworked.

Wifi

Sound

I'll call it internet, being that its ipv4 and ipv6.

There is more, that's just what I can remember.

I have a base build all setup for the 710, 715, and 815. The 810 will need to wait until its updated to RG2 or RH1 or ???

The new kernel may be a bit, as I'm still cleaning up from the wildland fire and flood on our property. I work on the kernel when I'm home. So depending on weather and the insurance company, it may me sooner rather than later. I really don't like the stock kernel. ;)
[Galaxy Tab S2 Android Development] efebe:
DRG2 a new base? ... cuz i cant find the firmware for it
[Galaxy Tab S2 Android Development] engine95:
Sammoble.com is the only place. Samsung firmware might
[Galaxy Tab S2 Android Development] IngoPan:
Hi,

Can i use this one stock rom rooted ? T810 here. Thanks!
[Galaxy Tab S2 Android Development] engine95:
Just make a full backup first, just in case. This kernel modifies the ROM. You should have no issues. It's for stock based ROMs.
[Galaxy Tab S2 Android Development] IngoPan:
Too bad i have xposed installed. I just love the "youtube adaway" and "unlock home" modules.

Or is there another way to install/use xposed modules without actually having xposed installed ?
[Galaxy Tab S2 Android Development] engine95:
This is the most current. RB1. That's why it's dated. RG2-RH1 will be coming shortly.. I have never said this won't work. Just follow what I wrote above your last post. If issues, restore your backup or ask in the Xposed thread. It's not the kernel.
[Galaxy Tab S2 Android Development] IngoPan:
flashed RB1 v1.3 in TWRP, flashed SuperSU SR5 2.82. Rebooted. Softwareinformation still says 3.10.9.

What am i doing wrong `?
[Galaxy Tab S2 Android Development] engine95:
I'm not sure, but the new RG2, RH1 kernels are in another thread as of now. https://xdaforums.com/tab-s2/development/kernel-9-11-18-rg2-rh1-710-810-715-815-t3841316 Give those a shot. They are 3.10.9.. "engine95" should show up on any of my kernels in "Settings>About tablet>Kernel version". Maybe you installed the wrong build?

And you can use Magisk now if you prefer. Both should work just fine.
[Galaxy Tab S2 Android Development] IngoPan:
I am on DBT RB1. Can i flash this kernel? Thanks.

---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------

OK, i flashed RH1 on RB1 Rom and works. Thanks!
[LeEco Le Max 2 Guides, News, & Discussion] sasaelbhiry:
This is How To Make Account For Leeco 2018

https://www.youtube.com/watch?v=Z6MsurEASzc
[LeEco Le Max 2 Guides, News, & Discussion] Soe Soe Maw:
Cloud created problem for user Myanmar
[Galaxy S6 Q&A, Help & Troubleshooting] slhsrc26:
turkish language support https://mega.nz/#!RYhnyQCI!ilxEDkmWsTR_FuPAWl1CweeMobLYKGuWOhEQI63UrXU
[Samsung Galaxy S7 Edge Questions and Answers] Redischen:
Hello,

I have a Samsung Galaxy S7 edge ( SM-G935F ) Exynos Version.

I flashed the new Oreo Firmware with Odin. I have also a Samsung Gear 3 and wanted to use SHealth. I rooted the device ( didnt work) .

I set back the OEM setting in the Developer Options and turned off USB-Debugging. After restarting I got an ERROR: Custom binary blocked by FRP Lock.

I deleted my Data : "Wipe data/factory reset" in the Android Recovery

Now my Problem: I cannot flash the Stock Firmware again and i cannot flash TWRP.

So I think i dont have Android and i also dont have enabled the options OEM & USB-Debugging.

Has anyone an Idea what to do?
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
So you have disabled oem unlock and you can't flash custom rom or recovery due to custom binary blocked by frp error..

Also you can't flash stock rom due to dm verity error if i guessed correctly?

You are badly stuck... maybe follow this thread it may help https://xdaforums.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963/
[Samsung Galaxy S7 Edge Questions and Answers] harishbalaji123:
I'm in the same situation and the link is dead. please help..

..
[Xiaomi Redmi Note 4 Questions & Answers] dawoodrangrez:
miui 10 faceunlock any solution ??
[LeEco Le Max 2 Questions & Answers] beta546:
Hey

Does anyone else have serious issues with this in every Oreo ROM? My battery will drain %1 per minute while playing even the most basic games, and the phone will get so hot it becomes uncomfortable to hold, it's top left of the phone so I presume CPU heat and not battery heat.

I have read about fixes for this after Oreo updates, but they're for other phones, but things like flashing older baseband, modems, and things like that.

I'm definitly not a noob when it comes to modding android, but I'm also not an expert.

Is it possible I could have some baseband or modem miss match? Would it be safe to flash an older version, and where would I find it?

Also is newer firmware included in ROMs? As I have seen some that say a certain version firmware is required or recommended, and I've never that I remember, flashed anything to do with firmware specifically...could I maybe have an older firmware? And could that even affect the battery in this way?

The battery isn't just bad, it is really bad, I took it off charge last night, slept 6 hours and woke up to %85 battery, with less than 1 minute SOT, every single battery savings feature is enabled, performance is set to battery and all that stuff.

Is this a problem that just I am having, or is this the same for everyone on every Oreo ROM? If it is just me, I hope someone can help me solve it.