yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] UpInTheAir:
I thought I would take the time to explain things that have been posted by others based on flawed logic and false statements.

FACTS:

This kernel is perfectly "secure".

Updating to Linux mainstream is not necessary due to:

A lot of the those patches are irrelevant & applicable to much more than our device code (I never said all)

Lollipop is coming soon, I won't waste MY OWN TIME for something of little gain before then

OEM don't update to Linux mainstream each source update

OEM apply SECURITY, stability and performance patches FOR DEVICE SPECIFIC are patched via source updates (from OEM or Google). Towel root exploit was patched by Google/samsung, NOT Linux !!

User probably wouldn't notice any improvement what-so-ever, placebo is a powerful tool. (a lot of time and effort for potentially little gain)​

This is not a Linux kernel, but a kernel based from Linux. ie. Linux > Google (Android) > OEM (Samsung) > UpInTheAir (& contributors)

OEM use Google GCC tool-chains to compile for good reason: fast, efficient and stable. (I might change to GCC4.9 when Lollipop source arrives though). Samsung actually advise GCC4.6, but I'm using 4.7 ;)

Synapse or STweaks is NOT buggy – devs need to look at there own coding skills or those they kang from. As I said, my Synapse implementation may not be perfect, but it's the best I'm capable of at time of release.

In it's default state

, this custom kernel is perfectly secure, fast, efficient and stable. I use it everyday and no issues except those in Post #3. It's up to user to make an informed opinion based on sound logical reasoning and facts, not hearsay or misconceptions.

Now, I've just lost some of dev time, back to it :) Enjoy :)
[Galaxy Tab S Original Android Development] UpInTheAir:
v3.0 released

v3.0 kernel is now released for supported TW 10.5" models :)

Change-log is in Post #2.

Updated BATTERY Section in Post #3

Please READ the GPU section in Synapse. There are new features and settings won't apply properly if not done correctly.

After changing and apply any GPU frequency or Threshold profile >> PRESS THE "Apply GPU GOV SETTINGS" button !!

Kernels are untested. I don't have device model, so please let me know how it goes........

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

INSTRUCTIONS:

Force Stop Synapse app > clear data

Flash SkyHigh kernel v3.0 in CWM or TWRP recovery

After boot (wait

at least

60-120 secs)

Open Synapse

Tap "Understood"

Make any change, and tap the "" to apply new defaults

After setting and applying any GPU freq changes, don't forget to tap [Apply GPU Governor Settings] in Synapse GPU section

Further instructions in Synapse app & Posts #1-3

For better GENERAL battery life or Performance, read recommendations in Post #3

Enjoy :good:

Cheers,

UITA

EDIT: just updated the change-log, forgot some source commits

.
[Galaxy Tab S Original Android Development] j1gga84:
2.7.0?

You mean 3.0 or am I wrong? ;)

Will test it now :)

Thanks & regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy Tab S Original Android Development] UpInTheAir:
Now we are getting "picky" :p

Edit: fixed :)
[Galaxy Tab S Original Android Development] j1gga84:
newest build booted fine on my T-805 LTE, many thanks :)

regards
[Galaxy Tab S Original Android Development] scoopdreams:
Thanks for the great work. 3.0 seems the smoothest and most stable so far on my 805.

One issue - I can't seem to backup profiles as Synapse keeps on prompting me to enter a name, which I have done so. Same for kernel backup.

EDIT: Missed the apply button at top lol. Haha it works now. Thanks and looking forward to LP Skyhigh!
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, Synapse does have the instruction:

;)

For my setup, it's much smoother using the 4 cores online same as stock. :) Battery nuts can play with the Hotplug ;)

EDIT: forgot to mention that I'm also looking forward to SkyHigh kernel LP :) Nothing will happen until we have firmware release from KIES and also kernel source code from Samsung OSRC
[Galaxy Tab S Original Android Development] VelosCohagen:
Hi UpintheAir. Thanks for the new kernel. It's a nice piece of work. I have only one small issue. When I set lmk profile to medium in Synapse, it always switches back to no action when I enter Synapse again.

I'm on a SM-T 805 with Basic Rom v3 using your kernel 3.0.

Greetings

Velos Cohagen

Gesendet von meinem Galaxy Tab S SM-T 805
[Galaxy Tab S Original Android Development] scoopdreams:
That's correct behavior as once you load the lmk profile it will adjust the settings appropriately, and then default to no action as you have already loaded the profile.
[Galaxy Tab S Original Android Development] VelosCohagen:
Tried it, and yes, you're right. Everything is ok.

Gesendet von meinem Galaxy Tab S SM-T 805
[Galaxy Tab S Original Android Development] Subsonic44:
Looking forward to it. If you need me to test for you let me know. Your kernel is already looking better than stock!
[Galaxy Tab S Original Android Development] UpInTheAir:
Better if we had updated sources and ROM firmware release... Older firmware performed better (bench) ..... We got what we got though. .
[Galaxy Tab S Original Android Development] brando56894:
running great on my 800!
[Galaxy Tab S Original Android Development] jodvova:
Running awesome on T800 with BasicRom v2
[Galaxy Tab S Original Android Development] eousphoros:
So I noticed you are using the G2 kernel, I was wondering if you had any issues with bcmdhd and it not trying to load wifi drivers. Tried both the klimtwifi_00_defconfig (stock) and my klimt defconfig I used from my N7 kernel + deferred init and had no love. Under sys/dhd both nvram_path and firmware_path are set correclty.

(Grumbles something about issues that don't generate error logs being difficult to diagnose)

Anyways would appreciate any insight you might have, or if this is just a "me" issue.
[Galaxy Tab S Original Android Development] UpInTheAir:
Never had any issues.

Are the WIFI drivers actually being compiled during the build ? If so, maybe permissions in ramdisk ?
[Galaxy Tab S Original Android Development] eousphoros:
Yep, and the same ramdisk with the N7 kernel works fine. Even tried updating the wifi drivers in the ramdisk I'm making to see if that was the issue. Guess its time to crank up the dmesg buffer to 20 and start adding in printk lines. Thank you for letting me know its just me. Amazing how valuable that can be sometimes. :D
[Galaxy Tab S Original Android Development] UpInTheAir:
Will get around to a new release sometime v1.0 today. Change-log posted and zImages are done. Got personal stuff to take care of first.......... :)

You will need to clear Synapse data before flashing !
[Galaxy Tab S Original Android Development] UpInTheAir:
v1.0 released

R3_v1.0 kernel is now released for supported 10.5" models :)

Change-log is in Post #2.

They are untested because I don't have the device and doing you a favour. Please let me know how it goes[/B]........

For those on older ROM firmware, please upgrade or you might have issues that we can't reproduce.

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

If you have Synapse issue after UPGRADING, please force stop app and delete Synapse data/cache first ;)

Further instructions in Synapse app & Posts #1-3

For UMS & other: Please read BUG REPORT tab found in PC website layout

Enjoy :good:

Cheers,

UITA

.
[Galaxy Tab S Original Android Development] WarLion:
Finally I test v1.0 on a t800 great kernnel I test the overclock works well but there is something extrange with the max cpu if I put it on 2100 I can use it all day long but if I need to do a reboot the sypnase app just find it as a fault and restore the max cpu to 1800 (default) and give me a error,

I love the option to low the cpu freq to 200 that will save a lot of battery drain thanks for you work keep it coming
[Galaxy Tab S Original Android Development] UpInTheAir:
It's not a flaw. Your max CPU temp has exceeded 75 degC and been throttled. If you apply your OC settings and reboot, allow time for the kernel to settle and cool before opening Synapse. Everything should be as it were ;)
[Galaxy Tab S Original Android Development] WarLion:
Ohh good to know thanks a lot
[Galaxy Tab S Original Android Development] eousphoros:
Not to hijack the thread, but just for future reference.

drivers/net/wireless/bcmdhd4354/dhd_linux.c:#if defined(CONFIG_DEFERRED_INITCALLS)

They introduced DEFFERED_INITCALLS which was breaking my old init. Anyways thought you might want to know. :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Great you've got to the root of it :)
[Galaxy Tab S Original Android Development] jodvova:
Installed v1.0 today, seems to be running fine. I run with 2100mhz max CPU speed.

Also run under basic ROM.
[Galaxy Tab S Original Android Development] WarLion:
Tested with super samsung rom amazing antutu score v5 well done
[Galaxy Tab S Original Android Development] jodvova:
Actually ignore my last post about running fine.

If I over clock max CPU to 2100, min to 200, the tablet runs fine for about 10mins and then hangs with funny straight lines on the screen. Only reboot helps.

So at 2100 my T800 is really unstable.
[Galaxy Tab S Original Android Development] UpInTheAir:
You may need to increase voltage to the OC frequencies. To help with stability, first try increasing voltage to 2100 MHz +50 mV . Not all devices are created equal ;)
[Galaxy Tab S Original Android Development] WarLion:
Mine works well on 2.1 ghz for almost an hour
[Galaxy Tab S Original Android Development] jodvova:
How do you do that ?

In Synapse app, the big cores voltage at 2100mhz is already at max which is 1362.5mv. I can't increase it, only decrease it.
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, that's correct. Please read the synapse description. I explain there ;)

If you wish to know the reason:

It's like this so user also has choice to manually adjust LMK values, otherwise profile values try to override user set values everytime you open synapse and would create a "apply/discard bug"
[Galaxy Tab S Original Android Development] UpInTheAir:
v3.1 released

v3.1 kernel is now released for supported TW 10.5" models :)

Change-log is in Post #2.

Please READ the GPU section in Synapse. There are new features and settings won't apply properly if not done correctly.

After changing and apply any GPU frequency or Threshold profile >> PRESS THE "Apply GPU GOV SETTINGS" button !!

Kernels are untested. I don't have device model, so please let me know how it goes........

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

INSTRUCTIONS:

Force Stop Synapse app > clear data

Flash SkyHigh kernel v3.1 in CWM or TWRP recovery

After boot (wait

at least

60-120 secs)

Open Synapse

Tap "Understood"

Make any change, and tap the "" to apply new defaults

After setting and applying any GPU freq changes, don't forget to tap [Apply GPU Governor Settings] in Synapse GPU section

Further instructions in Synapse app & Posts #1-3

For better GENERAL battery life or Performance, read recommendations in Post #3

Enjoy :good:

Cheers,

UITA

.
[Galaxy Tab S Original Android Development] j1gga84:
Latest build is running very well on my T805 as usual :)

Many thanks

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks for reporting. You are just about the first every time :) would be so easy to make a mistake building for multiple kernels at once, and unable to know if it actually boots. :thumbup:

What I do need to do is remove wipe cache and wipe dalvik options. A bit useless and could cause issues if user doesn't reboot in a hurry... I'll add Wipe Cache & Dalvik-Cache Reboot (if I have time)
[Galaxy Tab S Original Android Development] jawz101:
Dang. What's with all of this "adaptive" stuff? I'm impressed. Are these custom things you've thought of? I'd always wondered why some of those settings couldn't be more smartly managed because I can't trust myself to pick values. As if I know what I'm doing.

Pretty cool

I'm curious how expensive it is to make some of those typically static settings adaptive. I mean, are they dynamically adjusting all the time?
[Galaxy Tab S Original Android Development] UpInTheAir:
I don't believe anyone had done this yet for dirty_background_ratio or dirty_ratio , so could be a first. . It had been done for vfs_cache_pressure though (I also made that optional compile) :)

Took me quite a few hours to get things right and some testing to ensure no SOD etc. I'm no dev, but also studied others code, pieced bits and pieces from a couple places, then adjusted the method for what I wanted :) Just kept trying until it worked.

What I might try later is actually make those settings dynamic where screen on/off values can both be adjusted and or disabled. Just like dynamic dirty writeback etc. ;) Swappiness could be another too.

Screen off values I chose are from V6SuperCharger and after Googling how increasing/decreasing values might effect device. In most cases, we are not too concerned about writing data to disk and performance with screen off (except idle/sleep), so good values to start with for screen off battery ;) they night also be OK with screen on and cache pressure reduced to 20 and also reduce Swappiness etc. .. (I just haven't tested)
[Galaxy Tab S Original Android Development] UpInTheAir:
v3.2 update for 10.5" out soon.
[Galaxy Tab S Original Android Development] UpInTheAir:
v3.2 released

v3.2 kernel is now released for supported TW 10.5" models :)

Change-log is in Post #2.

Please READ the GPU section in Synapse. There are new features and settings won't apply properly if not done correctly.

After changing and apply any GPU frequency or Threshold profile >> PRESS THE "Apply GPU GOV SETTINGS" button !!

Kernels are untested. I don't have device model, so please let me know how it goes........

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

INSTRUCTIONS:

Force Stop Synapse app > clear data

Flash SkyHigh kernel v3.2 in CWM or TWRP recovery

After boot (wait

at least

60-120 secs)

Open Synapse

Tap "Understood"

Make any change, and tap the "" to apply new defaults

After setting and applying any GPU freq changes, don't forget to tap [Apply GPU Governor Settings] in Synapse GPU section

Further instructions in Synapse app & Posts #1-3

For better GENERAL battery life or Performance, read recommendations in Post #3

Enjoy :good:

Cheers,

UITA

.
[Galaxy Tab S Original Android Development] j1gga84:
First one as usual :p

Booted up fine and running great until now, restore of synapse profile backup also worked without any problems, many thanks :)

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy Tab S Original Android Development] scoopdreams:
Mate slow down with the updates and go spend some time on Phuket beach.

maybe it's just me but tbh the updates are too fast and furious. Would prefer a slower dev pace like once a week that packs in more updates and gives you more time to catch bugs and Real Life (tm).

Your kernel your rules though! Great work and much thanks.
[Galaxy Tab S Original Android Development] jawz101:
I just have to say that's so damn cool. I'm tried of tweaking scripts and apps. If it's really important to adjust it should just be at the right setting or if it's dynamic I figure it should be fairly conservative in polling and making its adjustments.

I wish there was a straight forward test for settings like that if they truly are significant because it seems like something could just benchmark load on your device for a few moments and set them.

btw, if you do follow other kernel people I'm sure you probably follow Franco but I also might suggest @mrg666. Specifically his mako kernel

thread

repo

really sharp guy
[Galaxy Tab S Original Android Development] UpInTheAir:
Just trying to wrap things up :) fixing my derp.

Could be last release before LP as professional commitments come into play over the next month. The kernel is where I want it to be, there's always something though, but this needs to be fixed ;)

Will actually be taking my son to the beach Sunday before the Aussie F1. :)
[Galaxy Tab S Original Android Development] UpInTheAir:
v3.3 released

v3.3 kernel is now released for supported TW 10.5" models :)

Change-log is in Post #2.

Please READ the GPU section in Synapse. There are new features and settings won't apply properly if not done correctly.

After changing and apply any GPU frequency or Threshold profile >> PRESS THE "Apply GPU GOV SETTINGS" button !!

Kernels are untested. I don't have device model, so please let me know how it goes........

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

INSTRUCTIONS:

Force Stop Synapse app > clear data

Flash SkyHigh kernel v3.3 in CWM or TWRP recovery

After boot (wait

at least

60-120 secs)

Open Synapse

Tap "Understood"

Make any change, and tap the "" to apply new defaults

After setting and applying any GPU freq changes, don't forget to tap [Apply GPU Governor Settings] in Synapse GPU section

Further instructions in Synapse app & Posts #1-3

For better GENERAL battery life or Performance, read recommendations in Post #3

Enjoy :good:

Cheers,

UITA

.
[Galaxy Tab S Original Android Development] UpInTheAir:
Just had a look at his git repo, mako is far different from ours (msm krait........... ), but might be some usefull generic commits etc. Studying others methods are useful for learning and adapting for our needs, because everything isn't just "cut & paste" :) Also. the end result may differ due to many factors.
[Galaxy Tab S Original Android Development] wbedard:
It seems crazy to me that nobody has provided feedback on the new build of your kernel! Let me fix that by confirming that is running fine on my T800 right now. Thanks for all your support to our devices.

R/

wbedard
[Galaxy Tab S Original Android Development] scoopdreams:
All fine here too. 5ghz wifi freeze and slowdown seems fixed.

Have a good time with your son at the beach and the races.
[Galaxy Tab S Original Android Development] j1gga84:
Also on T805 no issues as usual ;)

Thanks & regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy Tab S Original Android Development] Astania:
Well, latest kernel running perfect, but Synapse while restoring profiles has strange behaviour. After restoring profile, and then reboot, after waiting then two minutes and entering synapse, it asks me to apply some settings. I didn't apply them, but looked what was changed. It looks like in GPU QoS section were strange frequencies, I click camel and all works, but I don't know why I must to camel settings I've changed. But all things work flawlessly.

Wysłane z mojego SM-T800 za pomocą Tapatalk 2
[Galaxy Tab S Original Android Development] UpInTheAir:
Do not restore profiles from different kernel versions.....

You don't actually need to reboot to apply. After select profile > apply > restore, Just press the restart synapse button and then the [X] Cancel. You only need to reboot (if you want) to update the lists after backup or delete profiles/kernel image
[Galaxy Tab S Original Android Development] j1gga84:
First off all I want to say thank you for all you gave to us, the THANKFULL users of your great kernel :good:

For all the efforts you put into your work, although you do not own the "big Tab S" :good:

I saw the "conversation" between you and the unregenerate user who seemed to not have read the thread/opener and such users are a big reason why you will stop/reduce development :(

To say it in a few words, build 3.3 will be the final build of you great kernel for KK and maybe there will be development for LP in the future when it is released for our Tab S, but then in the new thread that you mentioned?

Again, many thanks and all the best to you my friend :good:

regards from germany
[Galaxy Tab S Original Android Development] UpInTheAir:
You and all grateful users/contributors are welcome :)

Yes. But no planned active support (by any means) from myself. Just a repository. I'm not sure whether this will be the last KK kernel, depends when LP source is released. ;)
[Galaxy Tab S Original Android Development] jawz101:
Definitely differences. Some of his generic stuff he backports are pretty nice
[Galaxy Tab S Original Android Development] trazfer:
My tablet t800 has 2 random shutdown with skyhigh kernel 3.3. This happens when i followed your instruction on post 3 to maximize battery life.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
I never had any problems with those settings. It gave me 9 hours screen on time and I tested that by watching YouTube and browsing the Web 9 hours straight.(No users has reported that those settings did that...) Anyway try this. I removed a few in which I always use this.

CPU GOV: governor = ondemand (tweaked for power efficient workqueues)

CPU FREQ: 200 > 1900 MHz (-25 mV for

GPU: 100 > 480 MHz (-50 mV for all) (100 MHz may induce some GUI sluggishness)

GPU: Midgard Power policy control = coarse_demand

GPU: Midgard Power policy threshold control = Battery (may induce some GUI sluggishness)

CPU Multicore Power Saving = (2) Agressive

That should help a bit since CPU Multicore Power Saving is the most effective in terms of battery(for me). I most use that to save some power as well as keep some performance. Looks like he added a few settings since I haven't checked that post for months. So yeah. Hope this helps!
[Galaxy Tab S Original Android Development] UpInTheAir:
Unfortunately your device hardware is probably of lower quality (check your asv group in INFO) and cannot handle the UV of GPU or GPU. You will need to find those values for yourself. I did forget to copy the first line of PERFORMANCE section to BATTERY. These are just generic values that will be suitable for most, but not all.
[Galaxy Tab S Original Android Development] trazfer:
Ty for your suggestions i will flash the kernel again and try your suggested settings.

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

It says here that ASV group is 4

Edit: i followed duhasianskillz 's setting and everything is okay now. No more random shut downs for me. Ty
[Galaxy Tab S Original Android Development] Astania:
Dear UpInTheAir, million thanks for great job. Kernel and Synapse work flawlessly . But if you have really free time and you will feel do bored, please, have a look into Synapse.:)

I cleared Synapse data, removed profiles, then I flashed latest kernel again. Cleared dakvik cache and cache.

As I said all works great but one thing not. I saved default settings under Default name, then I created two profiles: battery and performance. But while I switch from battery to performance, accordingly with data from entry posts, the UKSM settings won't change. UKSM switch is not restored. The same to LMK profile (for performance you said to set it to aggressive).

Additionally, when I switch to profile, then restart Synapse, it says to apply something. It looks like settings from old profile, When I click Camel, then New settings appear. It's nothing difficult to deal with, but could it be easier, can Synapse to show New settings immediately after the New profile is restored?

Big thanks once again and best wishes to You :)
[Galaxy Tab S Original Android Development] trazfer:
Thank you for [MENTION=3456089]nvertigo[/MENTION] for this wonderful kernel. Usually at nyt before i go to sleep my battery will be aroung 10 -15% then i will chrge it overnyt. But now i am going to sleep with 43% battery left. Huge difference. Btw i am a heavy tablet user playing clash of clans with 3 account using multi user + watching a tv series and playing brave frontier too. Thanks God Bless you always!
[Galaxy Tab S Original Android Development] budeone:
Well.. This sucks... ?? I say thank you.. Your work was appreciated by me.