yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] UpInTheAir:
Have started new T705 kernel build from newer source + ramdisk and having some success. No major features yet implemented, but it's booting and stable running on my older firmware (so far). Synapse is up and running, but most features aren't there yet. ..

Edit: new kernel appears to be running a little hotter than current release (old firmware though). AnTuTu gets thermal throttled much sooner than before, especially during "float performance". Need to flash newer firmware for further test.

https://github.com/UpInTheAir/SM-T700-kernel-T700XXU1ANF7/commits/SkyHigh

One thing I still don't understand is how the kernel still damages the recovery partition and requires recovery to be re-flashed after kernel. The size I'm currently at is a little more than 7mb and partition size is 8mb. ..... Maybe I'll make a flashable zip and flash using a different method instead of PC Odin, or use an app to flash the raw image instead. Let's see the result !

Will take a look at more tomorrow. :)

T700 : waiting on user to post requested boot.img's.

10.5" : Have made a start. Have downloaded, extracted source and now committed to github. Need to sort out this kernel first though.
[Galaxy Tab S Original Android Development] UpInTheAir:
Heat & thermal throttling

T705 heat findings: The CPU runs hotter on newer firmware on my device than earlier releases

Tested with:

1. rooted stock T705XXU1ANF8 and kernel test build T700XXU1ANF7 source + T705XXU1ANG2 ramdisk

2. complete rooted stock T705XXU1ANG2 firmware

3. rooted stock T705XXU1ANG2 ROM and kernel test build T700XXU1ANF7 source + T705XXU1ANG2 ramdisk

* Thermal throttle invoked alot easier @ 95 degC > decreased benchmark performance (compared to earlier firmware versions)

* Higher idling temp

* Higher alround temp

* Higher temps when stressing the CPU

* CPU OC 2.1 GHz > required +50 mV for stability (not required for older firmware and source on my device)

Conclusion (so far) : [MENTION=2735188]mitchellvii[/MENTION], as far as benchmarking, newer may not be always better ...........

Next to test, complete rooted stock T705XXU1ANG2 firmware with SkyHigh kernel v0.6. Don't hold high hopes though, we might need newer ROM firmware from Samsung and kernel source. Edit: Didn't go so well, powered itself off during AnTuTu and thermal throttle well before 95 degC. Will stick to the test build for now and try refine a few things. BTW GPU OC to 733 MHz is fine, but thermal throttle GPU to 350 MHz far too easily during bench and poor score. 533 & 600 MHz are quite good frequencies though.

Looks like T700 users don't wish me to support their device anymore. Once I tidy up this current T705 test build, I will now take a look at building 10.5" instead .........
[Galaxy Tab S Original Android Development] mitchellvii:
Sorry dude, been crazy busy. Here is the boot.img file for ANF9 (T700 wifi) . :)
[Galaxy Tab S Original Android Development] UpInTheAir:
No worries mate, the last line of my previous post wasn't directed at you, but T700 users in general. The heat related info was :)

There are enough other T700 users out there to contribute a little to the thread ;) I'm not going to spend 8 hours downloading the T700 just for the boot.img (T700KXU1ANG1 or T700XXU1ANF9). Yes, my connection is that slow...............

Edit; thanks for posting the image :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Heads Up !!

Next release v0.7 sometime later today (Saturday 16th August) and you will need a custom recovery such as TWRP for all future releases. I test using TWRP only ;) I have to go out all afternoon, so will get to it soon enough.

If you don't know how, please read up here: [RECOVERY][TabS]TWRP 2.7.1.1 touch recovery
[Galaxy Tab S Original Android Development] UpInTheAir:
R2_v0.7 released

R2_v0.7 is now released :)

Change-log is in Post #2.

TF700

WIFI

R2_v0.7 is untested. Please let me know how it goes........ I have added flashable Stock kernels in the Download section (if required).

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

Ensure you flash the kernel for your device model !!

NOTE: commit credits are in source.

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] Daniel Smedegaard Buus:
Question... Or, rather, feature request... Or both, actually :)

I've been wondering about the longevity of my battery in this device, and others, but especially in this tablet, since it doesn't have a removable battery.

So I've been reading up on thing, such as this article from the battery university, which explains how detrimental to battery life it really is to keep it fully charged. It seems avoiding charges above something like 70 or 80 percent might prolong the life of ones battery by several years...

I then remembered my horrible, horrible Chinese Ainol tablet (pronounce that name in English, and you know how bad it is), on which I installed a custom ROM which charges the battery quite a bit less than the original ROM did.

So... My question-slash-feature request is this: Is it possible to tweak the kernel to prevent charging the battery above a certain level (possibly force shutdown at higher levels as well, as that seems to be equally bad for your battery)? And is that something you might implement here?

Thanks in advance, and also thanks for making this kernel in the first place :)

XOXO
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, it's possible. There are kernel patches called BLX (battery life extender) for other devices. Not sure of the work involved or if it's possible to port to our kernel source. I might not have the knowhow anyway. Maybe something to take a look in the future, busy starting the 10.5 kernels :)
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
That's cool, thank you :) I'm gonna have a look-see... I am a developer, but nothing like kernels and OSes, so it's a bit out there for me. Well, I did write some client-server FTP-ish apps back in the days in C++, but these days it's pretty much all Node.js, and soon a bit of Go... I'll have a look at that BLX stuff and see if I can wrap my head around it :)

Oh, is there like a github repo for your kernel or is it closed-source?

Cheers :)
[Galaxy Tab S Original Android Development] mitchellvii:
Ran 0.7 on my t700. While overclocks seemed to stick and heating issues appeared solved, my Antutu scores actually decreased the more I overclocked. Strange.

Don't know if I have a bum rig here or what (runs great) but my benchmarks are nowhere near what others are achieving.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
I have warned before of decreased benchmarks with high OC or device still in warm state ;) I aslo said that these newer firmware and source run higher temps, just have to wait for newer releases afraid. My benchmarks are down about 500 points, but don't particularly care, not going to downgrade firmware at this point in time, look to the future :)

I observe the CPU/GPU frequencies and temperature at which they throttle. GPU 733 MHz is next to useless for benchmarking (will throttle easily), I was just in the mood to have a play...... CPU 2.1 GHz is not as stable on my device under default values. Older firmware and source - no problems. For stabilty, I've had to +25/50 mV.
[Galaxy Tab S Original Android Development] UpInTheAir:
Any code built or modified from original Google source is bound by GPL. This is also part of XDA rules to make available the source used to compile.

My work is fully GPL & XDA compliant, where my source (github) and commits are up-to-date at time of release and can be found at the bottom Post #1. It is not neccessary to commit a modified ramdisk (have in the past for other kernels), as it is not built from a source.
[Galaxy Tab S Original Android Development] mitchellvii:
Temps never got over 95c for me when benchmarking and I have DVFS disabled which should prevent throttling. But I was losing as much as 4000 points when overclocked. Didn't really play much with it as far as real world responsiveness when overclocked.

My guess is the CPU on this doesn't like being overclocked because it messes up the interaction with the slower cores hence the drop in benchmarks. Unlike a Snapdragon 4 core CPU where the tide lifts all ships, overclocking just the fast cores may be a problem.

The best solution may just be a gpu overclock and leave the CPU alone.

Sent from my SM-T700

---------- Post added at 10:35 AM ---------- Previous post was at 10:10 AM ----------

OK, screw the benchmarks for a minute. Just overclocking the gpu to 533 x 677 it does feel as if page draws in Maxrhon Browser are quicker. Instead of the page loading in blocks the entire page just appears ready for scrolling. Even with JavaScript enabled it seems quite brisk.

So that's a win IMHO. Leaving CPU alone for previously stated reasons.

Not sure if i should have a lower minimum on gpu.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
95 degC will thermal throttle regardless of DVFS. It is there for device protection. It is this that is responsible.

Don't forget that there are 4 big core sensors, and there may be discrepancy between the temps. Most CPU temp apps show only a single sensor temp.

Try UC the GPU -50 mV 100-533 MHz to start. Hopefully stable on your device.
[Galaxy Tab S Original Android Development] mitchellvii:
YouTube screams with this gpu overclock. Instant load, zero buffering. I also use the firewall hack to.improve youtube speeds but this seems improved from that.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
Forgot to add that lowing the GPU to 100 MHz may save a little battery in idle state. I can only just notice the slightest reduction in response when called upon, but I'm really looking for something though.
[Galaxy Tab S Original Android Development] mitchellvii:
As I suspected benchmark sucked - just 30500, but who cares, tablet is fast as hell.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
Let's hope there's a source update from Samsung soon :)
[Galaxy Tab S Original Android Development] mitchellvii:
With stock kernel and stock rom I was scoring about 34500. With the gpu overclocked I drop 4000 points yet performance seems great. Who knows?

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
As you know, I did extensive testing on this. ... If you want higher benchmark, stick with older firmware and kernel source. The newer just runs hotter, completely official or not.

Anyway, not concerned, this kernel has lots going for it. time for sleep
[Galaxy Tab S Original Android Development] mitchellvii:
Me neither. Runs fine, screw the benchmarks.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] mitchellvii:
Nice bonus. Crank main volume on audio up to 3db. Pumps the sound without distortion. Sweet.

Sent from my SM-T700

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

Here's good article on what those tcp algorithms mean in networking.

http://slaptijack.com/system-administration/14-algorithms-for-tcp-congestion-control/

I chose *Westwood* because it is supposed to be great for wireless networks. Got 57 mbps down as opposed to 50 before. Nice.

Sent from my SM-T700
[Galaxy Tab S Original Android Development] UpInTheAir:
The seems to be a slight bug with the audio. Due to the patch being for a single speaker device, just the top speaker on our dual speaker device is boosted.

Actually it's "Westwood Plus" (newer) but just shown as the old "Westwood". I have thought about making it default, but keep forgetting about it with every kernel and device .... :)
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
That's cool, thank you! And sorry for not checking OP in the first place :o

---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------

This reminds me: Earlier today I used synapse to boost volume across the board because I was watching a very low-volumed movie on Netflix. Just set +12 db on all bands on both speaker and headphones, thinking I'd either tweak it down later or just reduce volume with the rocker to avoid distortion.

Thing is, it had 0 effect on my headphones experience, but later today I noticed the speakers being extremly loud and distorted, so definitely some effect there. Anyone have any success using Synapse to change volume levels on headphones?

EDIT: Woops — I now see the UITA note about only the left speaker being boosted. This is pretty funny though, from day one I noticed that the left speaker seemed to be louder than the right one. And the other night, unplugging my headphones, the right speaker went completely silent. I though it might be toast, but stopping and restarting my video, the right speaker sprang back to life... Weird :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Yeah, I'll take a closer look at the Sound Control this week. Not sure what I can do, but I'll try anyway.

Currently patched in PowerSuspend driver up to v1.2 . Might not have deep sleep, need to test more overnight. Above v1.2 requires screen off/on hooks into the display driver and there is no port to cherry pick. I'm not sure yet how to do it. But of course, I'll try anyway. I'm just not a coder. .... Maybe I'll ask Yank nicely if he could spare the time. :) See how the deep sleep goes first

Edit:

[MENTION=2735188]mitchellvii[/MENTION] / [MENTION=4142938]Daniel Smedegaard Buus[/MENTION]: Just had a play with the HP audio equalizer boost, all works :) You just can't adjust the boost whilst media is playing. You need to pause the player first before adjusting the equalizer & then apply before resuming media playback ;) Tested with stock player and "over the horizon" mp3

Currently downloading the source for SM-T700_JPN_KK_Opensource.zip (T700OPU1ANG2) and going to basic compile, see if the basic kernel will help with temperatures etc, on newer firmware. Of course depending if it compiles, boots, and works without issues........ My connection is so slow, DL will take a few hours

Edit2: Main Speaker equalizer boot also boost only the top speaker (same as Main Speaker Amplification), but media

doesn't

need to pause before applying changes (unlike HP).
[Galaxy Tab S Original Android Development] UpInTheAir:
Actually I meant Post #2, at least you found it :)
[Galaxy Tab S Original Android Development] UpInTheAir:
WolfsonMicro WM5102 sound control

WolfsonMicro WM5102 sound control :

Despite my best efforts, I have not been able to patch Andrei's control for our dual speaker device .......... probably a rather simple fix and could have overlooked something staring me in the face, but I am not a Dev and understand very little. I learn by reading, comparing patches, and trial & many errors., but for me, did give it my best shot resulting in no audio and high CPU usage caused by spi2 running in background.

So, what to do ?

Only the top speaker amplification & equalizer is working, so remove the controls from Synapse ? Speak up if you still intend to still use it, or

they'll be gone in next release

. HP equaliser will remain though..
[Galaxy Tab S Original Android Development] UpInTheAir:
T700 WIFI Users !

Please post your SYSTEM partition number. I need it for your next release

/dev/block/platform/dw_mmc.0/by-name .........

THANKS
[Galaxy Tab S Original Android Development] kempi46:
I may help but I don't know what to do after I arrive at by-name
[Galaxy Tab S Original Android Development] UpInTheAir:
What number do you have ending mmcblk0p__ for "System"
[Galaxy Tab S Original Android Development] kempi46:
under SYSTEM it's

mmcblk0p18

hope that helps :D
[Galaxy Tab S Original Android Development] UpInTheAir:
Same as my T705 LTE. I'm adding de-Knox to the kernel install script.

Cheers
[Galaxy Tab S Original Android Development] UpInTheAir:
T700 WIFI T700KXU1ANG1 boot.img required

T700 WIFI boot.img

The all new T705 kernel is ready, but need a T700 WIFI boot.img for tester. Will release once both are ready, but I won't wait too long.......

Could someone please post their stock T700KXU1ANG1 boot.img. I'm ready to re-pack for testing :)

Edit: Upcoming v0.8 Change-Log in Post #2

Cheers,

UITA
[Galaxy Tab S Original Android Development] stitoo:
As you wish UpInTheAir T700 WIFI KXU1ANG1 boot.img.
[Galaxy Tab S Original Android Development] onairda:
a version for T805 Exynos was not even included in the future?

I hope so, in the meantime thank you

Adriano
[Galaxy Tab S Original Android Development] edan1979:
its hard to make something when you dont have the device...
[Galaxy Tab S Original Android Development] onairda:
you're right, but maybe having the same hardware but only the smaller screen might be a little 'easier, I hope :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Display size had nothing to do with it, not having the device does. ..

I am looking into a 10.5 kernel as I type this response. Trying to take some shortcuts. Test compiling and hopefully don't have to take the long way. Thought I had success, but not so lucky :( Long way, here we come.

A successful compile does not necessarily mean successful boot. ...

It takes a huge amount of time for a device I don't own or use. Time taken away from my own device. Please be patient :)
[Galaxy Tab S Original Android Development] UpInTheAir:
HOW TO MONITOR "LIVE" cpu & GPU VALUES ??

HOW TO MONITOR "LIVE" cpu & GPU VALUES ??

Please refer to Post #3 for instructions and link to my personal cool tool app presets :)
[Galaxy Tab S Original Android Development] killall:
Hi. I don't usually use non stock kernels as I find them very complicated. But with stock my t700 takes a loooong time to charge. If I flash your kernel and leave everything as preset will it help?

Thanks
[Galaxy Tab S Original Android Development] UpInTheAir:
In default state, no.

But user has choice and full control to increase it decrease rate of charge. This of course is dependant on the max output of the charging source and battery level etc.

Most info is explained in Synapse app.
[Galaxy Tab S Original Android Development] UpInTheAir:
v0.9 released

R3_v0.9 kernel is now released for supported 8.4" models :)

Change-log is in Post #2.

T700

WIFI

R3_v0.9 is untested. Please let me know how it goes........ I have added flashable Stock kernels in the Download section (if required).

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

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] Daniel Smedegaard Buus:
How did you make an image like that? I'm wondering about how to do an Odin-recoverable snapshot of my device... I'm assuming I'd be able to using a method such as what you applied here?

---------- Post added at 10:49 AM ---------- Previous post was at 10:47 AM ----------

Are you using the supplied charger? Because if you charge it with anything else, the current will be ~500 mA (USB 2 specs), while the supplied charger gives you ~2A, or four times faster charge (give or take).
[Galaxy Tab S Original Android Development] UpInTheAir:
Just un-tar/zip from the firmware package found at sammobile etc, or dump the partition via terminal emulator commands. Some hex editing would be required to expose just the boot.img rather than the whole partition.
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
Ah, okay, I thought this might be a way to back up your current installation, like dd :)
[Galaxy Tab S Original Android Development] MariozPOC:
Thnks very much! I just installed on my SM-705 your kernel version 0.9 and synapse app. My goal is to get a better battery life without to loose performances. I followed your suggested settings and in a couple of days I'll let you know my impression.

Thnks again
[Galaxy Tab S Original Android Development] kempi46:
Deleted
[Galaxy Tab S Original Android Development] UpInTheAir:
Screen Mirroring / AllShare Cast Fix for rooted devices

Screen Mirroring / AllShare Cast Fix for T705 LTE ???

SkyHigh_kernel_T705_LTE_TW_R3_v0.9.1.zip

There is no difference to T705 LTE v0.9 kernel except for a hopeful fix.

I don't have supported TV to test,

so please post your results here to see if it made any difference

!
[Galaxy Tab S Original Android Development] UpInTheAir:
As i type this post, there are now 16 downloads of the v0.9.1 test release for screen mirroring.

How about some feedback if it worked or not ? Please also post your ROM & firmware version and status.

Because i won't be sure if I'm wasting my time, without feedback, it will be impossible continue to help you in future !
[Galaxy Tab S Original Android Development] palaiouras:
Hello,

I've tried the latest kernel with my lte galaxy s and a miracast device for a couple of times.

I didn't work unfortunately.

Nonetheless great kernel. Keep up the good work.

Greetings from Greece.

Nikos
[Galaxy Tab S Original Android Development] UpInTheAir:
Thank you for reporting.

What ROM and firmware version ?

Did it previously work before you rooted device and had official status ?

Any others with success or failure ? Please give details so we have a bigger picture.
[Galaxy Tab S Original Android Development] TheGoD:
Could it be that there is a problem with the low memory killer? I noticed that even though I set it to 400 MB (or even 800) the kernel isn't killing off apps when there is only 200 or less free. I think the main source of stuttering while switching apps etc.results from low available memory.

Also, could you implement back light notifications?
[Galaxy Tab S Original Android Development] gcappa:
Because it is my phone. Sold note 3.
[Galaxy Tab S Original Android Development] UpInTheAir:
The kernel uses 1 GB of RAM for SWAP space, same as stock. It doesn't appear in your app "free RAM", so whilst it reports low memory, in fact in probably doesn't tell the whole story. My device is devoid of lag/stutter etc. I use official NG2 odex firmware. I will however test a little more on my own 8.4 device with same firmware.

Edit: having GPU min freq set to 100 MHz will impart a very slight "sluggishness", so try set back to stock 177 MHz. A little OC to 533 MHz might help too, I personally set freq 100-480/533 MHz -50 mV.

BLN and some other absent features require a full code review, something I'm not capable of.
[Galaxy Tab S Original Android Development] UpInTheAir:
Testing v1.0 . Working nicely. :)

A few more Synapse features i just can't get right yet. small things, but i love to have a configurable option rather than fixed values. Maybe in v1.1
[Galaxy Tab S Original Android Development] esmund:
hi, can anyone tell me how to get twrp? mine suddenly hangs at teamwin page. :( thanks
[Galaxy Tab S Original Android Development] edan1979:
direct link. flash using pc odin.

http://techerrata.com/file/twrp2/klimtwifi/openrecovery-twrp-2.7.1.1-klimtwifi.tar

[MENTION=1872640]uit[/MENTION]A

did the kernel support crossbreader? i'm thinking to add it in my next rom release.
[Galaxy Tab S Original Android Development] UpInTheAir:
It'll change some of SkyHigh and stock defaults. Keeping the entropy pool full may increase battery consumption. I'll be looking at some more tweaks in future releases past the upcoming v1.0 release. Just having trouble setting some config in Synapse and causing annoying little issues.

I can't guarantee full compatability with other tweaks around the place or their compatability with this kernel or our firmware.
[Galaxy Tab S Original Android Development] edan1979:
ok... i'll stick with current one then... ^_^