yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] festr:
hello despite the fact the main developer give up (all glory to him) I'm curious if anyone managed to work out audio gain on wolfonson in synaps application. The earpiece gain simply does nothing. Any thoughts?
[Galaxy Tab S Original Android Development] UpInTheAir:
I haven't yet "given up". Please don't misquote, I just won't be actively supporting my contributions. As far as the sound control, never really tested properly as don't use the earpiece for phone function.
[Galaxy Tab S Original Android Development] festr:
oh ok! sorry for misinterpreting the information.
[Galaxy Tab S Original Android Development] lexjay:
can i flash this with the stock rom?
[Galaxy Tab S Original Android Development] nrage23:
Yes
[Galaxy Tab S Original Android Development] hillg001:
because it'd be stupid to be forced to have to buy 2 expensive devics, then have to shlep 2 devices around with you all the time? Seems to us - that that would be stupid. ;)

At least that was our logic ... saving money and clutter .... not that either the question or the answer are on topic.

.
[Galaxy Tab S Original Android Development] :
Hi. After installing the kernel, doesn't connect to my rooter.. Any help? Ironrom 1.1.5

Thanks,
[Galaxy Tab S Original Android Development] UpInTheAir:
Please read Post #1 requirements in red....

Edit : To all, this sort of post is partly why I'm not bothering to help anymore. Read the OP and help yourself first !! This is NOT Q&A and will be development no more. .. Project will be DELETED in 4 days.
[Galaxy Tab S Original Android Development] :
Ok sorry man.. I know it is disturbing, replying the same things again and again. Probably best solution another q&a threat if you dont want questions here.. We do respect your work here and your excelent kernel. And we hope you continue the development.

But you will always have questions. We cant always read all pages of every threat to see what alow the developer. I have read more than 10 pages here, and i will read all threat when i find time.

I will search more to find the solution as you obviously dont want to make it q&a here. Have a nice day!

Didnt know there were a q&a threat..
[Galaxy Tab S Original Android Development] UpInTheAir:
1. There is a link to Q&A section. Read 3rd line of OP !!

2. Another link at first line of Post #3 HELP & FAQ !!

3. Another link at bottom of last post is visible when using XDA app

4. Another link is visible on thread top tabs when viewing thread in Web view. (Discussion, downloads, ...Q&A)

I take my own time in having supporting the kernel and thread, it's just lazy that users don't reciprocate the same respect. This is my point, so I'm not bothering in future.
[Galaxy Tab S Original Android Development] Siberian Tiger:
Thread closed as OP requested.
[Galaxy Tab S Original Android Development] toyanucci:
Any chance of a 10.5 version?
[Galaxy Tab S Original Android Development] UpInTheAir:
I have answered this in both thread and in Post #3
[Galaxy Tab S Original Android Development] UpInTheAir:
deleted. ..
[Galaxy Tab S Original Android Development] toyanucci:
Apologies
[Galaxy Tab S Original Android Development] ResetBIOS:
Dear UpInTheAir, do I get it right, I need ROOT to flash your kernel? I hope I get it right! Question is, how to make ROOT!?

Or how do you make it on T705? thanks
[Galaxy Tab S Original Android Development] ramyeohy:
Use CF-AutoRoot to root your device. You need to be rooted to use Synapse to adjust the kernel settings to your liking.

Get the instruction and file here - http://xdaforums.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
[Galaxy Tab S Original Android Development] ResetBIOS:
thanks, I was sure it works for T700 only.
[Galaxy Tab S Original Android Development] ramyeohy:
Ha! Read post 14 on that thread. UpInTheAir confirmed it works and I followed. I own a T705 too. :good:
[Galaxy Tab S Original Android Development] heyjoe66:
The strange thing is when I disabled equalizers in Synapse audio settings, the tablet was refusing to play any sound through wired headset, but playback with speakers was fine.

EDIT:

Another bug related to headset, if restart device with headset plugged in then audio routes get messed somehow.

I'm unplugging headset, then connecting a BT headset, but phone call sound goes to loudspeaker or earpiece on device itself.

If I restart again, but without headset plugged, then all goes back to normal.

Just checked and could not reproduce this bug on stock kernel.
[Galaxy Tab S Original Android Development] UpInTheAir:
There are a few gremlins with the Sound control.

You need to have the equalisers enabled otherwise sound will play through bottom speaker only. I have set both enabled as default so speaker and headset work in default configuration.

I have left out volume control for the headset because it wasn't working. Just works via the equalizer.

I think because Andrei wrote the code for single speaker output device, but I've had no time to try study the code to see if I'm even capable to try and fix a few things.

Best to leave the equalisers enabled permanently. If I can't fix it, I will remove the switch, but still keep enabled as default.

I don't have BT to test on that, so will require feedback.
[Galaxy Tab S Original Android Development] heyjoe66:
Questions about Exynos Octa

There are some things I don't understand about our CPU.

So we have an IKS cluster switching and each cluster has it's own frequency and all cores in cluster have one same frequency in the moment of time, so if we, for instance, set /sys/devices/system/cpu/sched_mc_power_savings to 2, then cores gonna be filling one by one. Then core pairs have to brought offline and online when needed, but I don't see if hotplug switcher ever work. At least the traditional one which writing to /sys/devices/system/cpu/cpu0-4/online. Maybe it uses some other hotplug switcher, at least when I look at CPU tab in Android Tuner, all core always online. But still I can disable cores by setting /sys/devices/system/cpu/cpu0-4/online to 0. So it seems to be reading it, but not writing.

So the question is what about hotplugging?
[Galaxy Tab S Original Android Development] UpInTheAir:
The wording that I used is "tries" to group.....

I'm away and don't have resources with me. Unfortunately no time and resources to look into things to try and answer your question properly.

Anyway, more reading here:

https://github.com/UpInTheAir/SM-T...ntation/ABI/testing/sysfs-devices-system-cpu

https://github.com/UpInTheAir/SM-T700-T705-Kernel/blob/SkyHigh/Documentation/cpu-hotplug.txt
[Galaxy Tab S Original Android Development] heyjoe66:
HA! Hotplugging is allowed only when screen is off, it's hardcoded that way.

Gonna fight with in now.

UPDATE: Fixed

drivers/cpufreq/dm_cpu_hotplug.c : line 239

if (low_stay > 5 && !lcd_is_on) ->	if (low_stay > 5) // && !lcd_is_on)

Would be nice to implement sysfs interface for setting hotplugging policy
[Galaxy Tab S Original Android Development] AndreiLux:
Hotplugging doesn't exist anymore as a PM mechanism in newer SoCs beyond coarse limiting like the screen off scenario you described. The cores are powered off by CPUIdle in a millisecond basis.

So don't try to screw with hotplugging.
[Galaxy Tab S Original Android Development] heyjoe66:
I don't quite understand. The existing code does turn off cores 1,2,3 with traditional mechanism (cpu_up() and cpu_down() methods).

It does some job for measuring load, then sets some flag that load 'is low', then checks 'if load is low and not lcd on' then turn off cores 1-3.

So you're saying that all this job is being done on top of that modern CPUIdle mechanism?
[Galaxy Tab S Original Android Development] AndreiLux:
Yes. They turn the cores off via that method in screen off because the SoC can only enter Low Power Audio mode only when just core 0 is "on". The mechanism is meaningless during screen on. Before they didn't even had the DM driver and simply limited it to core 0 in screen off, but I guess they introduced it so the phone has more power doing background tasks in screen off.
[Galaxy Tab S Original Android Development] heyjoe66:
So, we have a chain of PM techniques from CPUIdle -> traditional hotplugging (when screen is off) -> Low Power mode.

Or CPUIdle and Low Power mode are the same?
[Galaxy Tab S Original Android Development] AndreiLux:
Low Power Audio / LPA is a CPUIdle state that can only be active in screen off with 1 core.
[Galaxy Tab S Original Android Development] Armpowered:
Should this work OK on a tablet that's been updated to T700XXU1ANF9 ? Also, the only reason I want to try it, does it allow Synapse to adjust colour balance?

Thanks for the work.
[Galaxy Tab S Original Android Development] UpInTheAir:
Does Post #1 state this a kernel/Synapse feature? .......
[Galaxy Tab S Original Android Development] Armpowered:
No but you might have included it on the quiet!
[Galaxy Tab S Original Android Development] UpInTheAir:
Not in my nature to hide things. Why would I ? All is transparent thread and source up-to-date github at time of release..... ;)
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
[removed dumb-ass question] :)
[Galaxy Tab S Original Android Development] Stupid1337deer:
Might as well unlock the frequencies up to 2.5! Haha, MORE POWER ;). I'm able to OC and UV with full stability. But about the little cpu core, I would like to be able to OC/UC it! Is that possible? Could you add another section in synapse to control the little CPU core, just like the big CPU core has?

Also, are there any other performance tweaks you could add to the kernel that would speed up the device even more or optimize it? Keep up the great work! I just might donate (;
[Galaxy Tab S Original Android Development] UpInTheAir:
Might do up to 2.5 GHz, will have other things to do before that. As I said, would probably be counterproductive and decrease performance for benchmark junkies (complaints flood in. .... )

The CPU frequency control is for both. Max frequency for big and min frequency for little (edit: depending on user min frequency set). Don't think would be of any real benefit to try control max little frequency or OC it.

There's always something that I could do, but as I posted, development is currently suspended. I'll be at it again in a few weeks time. :)

I would prefer to keep the kernel relatively simple, and therfore have a stable and balanced experience :) I could also look at patching to latest linux and custom toolchain etc, but still not that sure of the real benefits vs simplistic stability.

Donations:

Thanks but no thanks. I do this for the enjoyment and challenge where time and skill level/knowledge permit. If anyone wishes to donate, I would suggest to please donate to AndreiLux who has shared with us his wealth of knowledge and expertise for many years now. Without him, essentially Exynos development would be dead. Otherwise maybe XDA for hosting our great forum, or a local recognised charity of your choice. :)
[Galaxy Tab S Original Android Development] ssuper2k:
Did you modify cpu volt settings?

Cause mine is not stable at 2100, not even after raising volt 50or 100

Every time I start a demanding game, the tablet hangs and resets after 10-15secs

Then, default 1900mhz is auto applied
[Galaxy Tab S Original Android Development] UpInTheAir:
Every CPU is different.

If not already, maybe try without any other user kernel tweaking (ie. GPU at default)
[Galaxy Tab S Original Android Development] ssuper2k:
First thing I tried was that, only 2100

Now at 2000 seems to be stable, also min now at 200mhz

Strange thing is, cool tool tells me it's at 100 sometimes when iddle

The four cores are 40-47°.. havent seen them higher
[Galaxy Tab S Original Android Development] UpInTheAir:
Not strange,...... Read Post #3 ;)
[Galaxy Tab S Original Android Development] Stupid1337deer:
Well Im sorry about your luck buddy! I set my tablet to 2100 as well as ramp up the GPU clock, and she runs like a charm :cool: I benched it and stability tested it with Antutu and it was perfectly stable. So then I began undervolting it. I currently have the big core at -15, and all else -21.5. In antutu, my benchmark scores top all other devices ^-^
[Galaxy Tab S Original Android Development] eousphoros:
Nevermind, got it working :)
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
Any chance of seeing an upcoming version with TWRP? It's either having that or having this kernel, and I really want this kernel :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Good to hear (whatever the problem was) :)
[Galaxy Tab S Original Android Development] UpInTheAir:
Welt not both ? Both require Odin to flash. ....
[Galaxy Tab S Original Android Development] eousphoros:
This issue was in the Makefile for the firmware, the relative paths werent resolving for the synaptic hex files. Just had to update the makefile and all was good. :) (Touch screen not working for custom kernel)
[Galaxy Tab S Original Android Development] slackerz_86:
I have problems using this kernel... i did not change any settings but yet my t705 always in 'black no-screen' after i unflap my book cover... had to do the download mode in order to restart it. Any ideas why?
[Galaxy Tab S Original Android Development] UpInTheAir:
No idea. I don't have a cover to reproduce. Need other user input.

I presume you have completely stock rom (except root) and no other mods to cause any potential issues?

Maybe turn on logging and post the logs next time it happens, don't really have time right now to even look, but someone might see something.
[Galaxy Tab S Original Android Development] slackerz_86:
Stock Rom onky with your kernel and root.... it happens everytime. After i closed the cover for 2-3 mins, and when i opened it back, it will just show black screen. No buttons can wake it up.... until i restart it by pressing 'Download Mode' combinations.
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
Well, if I flash TWRP and then your kernel, I lose TWRP.

If I flash your kernel and then TWRP, I get a bootloop.

I'm assuming it's because they're mutually incompatible, but I may be wrong :)
[Galaxy Tab S Original Android Development] pibach:
I was able to overclock to 2GHz, GPU all up, some undervolting, and stable in Antutu benchmarkt (31xx score).

However I then got a "stuck at download mode". Probably not a fault of the kernel.

Tried to reflash the kernel via Odin. Did not succeed. Now it does not connect anymore. Cannot reboot (does not power off).

Will have to let battery run down to try anything else.
[Galaxy Tab S Original Android Development] ssuper2k:
Power+Vol_down+Home for 10-15 secs will do
[Galaxy Tab S Original Android Development] slackerz_86:
That is Download Mode Combination....
[Galaxy Tab S Original Android Development] edan1979:
Yup... and you can press down to reboot normally
[Galaxy Tab S Original Android Development] slackerz_86:
Yes and that is what i am saying. I had to reboot my t705 by this method becoz using this kernel makes my device stuck in black screen after i opened my book cover flap....
[Galaxy Tab S Original Android Development] UpInTheAir:
A user has previously reported that flashing kernel breaks recovery.

I don't understand why as usually if the kernel is too big for partition, it will fail to boot after Flash.

I will take a look when I return ( edit: slim kernel down or change compression mode) and in the meantime try post a bug report and note else where to warn users.
[Galaxy Tab S Original Android Development] UpInTheAir:
To exit DL mode: hold volume down + home + power. Might take a few seconds.

After that, re-boot into DL mode again and try flash stock kernel provided (will lose wifi password).
[Galaxy Tab S Original Android Development] UpInTheAir:
Can someone please post Odin flashable stock recoveries for T705 and T700. appreciated.
[Galaxy Tab S Original Android Development] pibach:
That worked, thanks (power button alone does not). Recovered by re-flashing stock ROM.

Gave the kernel another try, but again, stuck at Download Mode after gettiing the message "es wurden nicht autorisierte Vorgänge entdeckt - rebooting...". Might be some Knox message. Is it related to the kernel? Should I uninstall Knox?
[Galaxy Tab S Original Android Development] UpInTheAir:
You are obviously rooted and disabled knox with SuperSU?

Sorry, don't understand the language on your error.
[Galaxy Tab S Original Android Development] pibach:
Didn't disable Knox, so that obviously caused the problem.

With Knox disabled kernel OC/UV is running fine so far.

Thanks a lot!

Did anybody do some performance and battery runtime comparisons?

That gets stuck within flashing boot.img.

I successfully flashed Samsung stock ROM.
[Galaxy Tab S Original Android Development] SS2006:
I also had to flash back to stock after I tried booting into TWRP, i got a boot loop. I am back up now with TWRP installed, but will wait for an update on this kernel before flashing it, which I hope its soon because to be honest I can feel my tablet is SLOW again on stock. This kernel was veryyy good/fast
[Galaxy Tab S Original Android Development] UpInTheAir:
Flash stock recovery after this kernel, otherwise wait for kernel update around end of next week ;)
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
Update? Cool :) Will it have Synapse color settings support?
[Galaxy Tab S Original Android Development] UpInTheAir:
No, will try to take a look at a couple bugs.

A month ago, I took a brief look at it and will need porting and I may not have the skill to do it. Some level of control using from stock kernel can probably be added for various profiles, but not in next release though.
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
Fair nuff, thanks :)
[Galaxy Tab S Original Android Development] moontime:
How do I remove the original Kernel?
[Galaxy Tab S Original Android Development] pibach:
I did some Antutu tests, SM-T705:

1) regular settings, no overclocking: 33000

2) overclocked to 2GHz (2.1 isn't stable at my device): 33900

3) Overclocked 2GHz + GPU max: 33700

Did not test with stock kernel however.

So got a very slight improvement by overclocking.

Wondering that GPU overclocking does not have positive effect.
[Galaxy Tab S Original Android Development] ayenzel:
My Tab S stuck on download mode after trying to get into recovery after flashing this kernel. and now I want to flash stock kernel it was stuck on boot.img on the odin and just like that forever. How to fix this? My Tab cant boot up also, stuck in download mode. If I flash the stock firmware will it fix the problem?
[Galaxy Tab S Original Android Development] pibach:
Yes, had the same issue. Flashing stock ROM does recover. It is the Knox service causing it, disable it via SuperSu.
[Galaxy Tab S Original Android Development] UpInTheAir:
Did you tread the WARNING posted in the download section before flash and the BUG REPORT section (in Web view) ???

To exit download mode, ensure USB is disconnected, hold vol down + home + power for around 10 secs. When prompted, don't vol up, volume down.
[Galaxy Tab S Original Android Development] UpInTheAir:
Read Post #3 on OC
[Galaxy Tab S Original Android Development] UpInTheAir:
Sorry, I don't understand.

You don't need to remove anything, just read the WARNING in download section, bug report and last few pages of thread before doing anything.

If you still wish to flash, just follow the installation instructions. In addition, it's highly recommended to have knox disabled.
[Galaxy Tab S Original Android Development] pibach:
You can exit, but only to reenter. It is stuck in downlooad mode loop. Only way out I figured was flashing stock ROM.
[Galaxy Tab S Original Android Development] UpInTheAir:
No need to flash full firmware. As I said, read warning and bug report section.

Where to find stock recovery, you'll have to extract yourself and make Odin. tar.

No one could be bothered to post after my request. .......
[Galaxy Tab S Original Android Development] pibach:
Yeah, might be overheating.

But for short burst it should utilize overclocking for better responsiveness. E.g. launcher animations, scrolling and panning etc. Do you know some test to better quantify the effect?
[Galaxy Tab S Original Android Development] UpInTheAir:
You might have a ROM issue rather than kernel. My device is ok with or without OC. You can setup cool tool app to view various "live" parameters. Kernel governor parameters can also be modified via Synapse app etc and you can also try disabling DVFS in ROM.
[Galaxy Tab S Original Android Development] Daniel Smedegaard Buus:
IME, I don't think GPU overclocking even works.
[Galaxy Tab S Original Android Development] UpInTheAir:
Why do you say that ?? Of course it does. Ever heard of thermal throttling :what:

Edit: just did a AnTuTu test.

No fresh boot or clearing RAM or anything.

GPU 100-480 MHz = 10,807

GPU 100-677 MHz = 11,293

Of course with a totally cold device with loads of available few RAM, increasing minimum frequency, and time to cool between benchmark (instead of 1 minute) would increase that score quite a lot ! But why should I care about a SYNTHETIC benchmark. ....

Edit 2: interesting that I scored very similar 266-600 MHz to 100-677 MHz
[Galaxy Tab S Original Android Development] pibach:
Thanks for clarification. Good to know. I am just asking for better understanding. Keep the good work going!
[Galaxy Tab S Original Android Development] UpInTheAir:
I just don't think we're going to see the huge score increases compared to older devices with smaller and lower resolution screens.

But with OC, the is still a difference.
[Galaxy Tab S Original Android Development] le0.br4zuc4:
Thanks for the kernel. Will try it out. Hope to have the same speed as some people reported. Did want one notice better battery life with this kernel?
[Galaxy Tab S Original Android Development] UpInTheAir:
I don't employ many "battery saving" tweaks within the kernel. I just patch and or expose various configurable user options. This is a balanced kernel without too much deviation from stock values. Each device is different, so one tweak may work well on one device and not so well on others. There are many excellent kernel guides/info found in XDA that explain the principle behind many of the features and configurable tweaks. ;) I prefer to keep things stable. Users can work from a stable "base" that suits there own needs and device capability.

I'm personally currently using :

CPU 200-1900 MHz (-25 mV)

GPU 100-480 MHz (-50 mV)

Still room for further individual frequency/voltage adjustment, though too busy with work to test my device thoroughly.

All other kernel values at SkyHigh default.
[Galaxy Tab S Original Android Development] mitchellvii:
I'm curious as to why benchmarks are higher for the T800 than the T700. I got 35,300 using ThunderRom800 on stock kernel. Any idea?

Also, I just picked up a T700 and gave my T800 to the GF so hopefully I can help with testing going forward. Despite the benchmark scores bieng lower this T700 "feels" faster to me than the T800.

One thing that completely SUCKS on both units - embedded videos. They lag so badly and won't buffer at all. This is so odd as the YouTube app streams even 4k video flawlessly. Any ideas on what is fubaring embeddeds? I have 60mbps DL speed. These embeddeds should not be lagging even a little.
[Galaxy Tab S Original Android Development] Enddo:
I got 36,000 on my T700 using TouchWiz and Stock kernel. Where is there proof that the T800 is better than the T700?
[Galaxy Tab S Original Android Development] mitchellvii:
Could you post a screen shot of your score please? I'm running EMSpilot's rom and am getting around 32500. Doesn't make sense to me either as both devices should get similar scores; however, 36000 seems exceptionally high to me for stock. Another user in this thread was getting only 33900 overclocked.

gsmarena only got 31754 for the Tab S 8.4 stock. http://www.gsmarena.com/samsung_galaxy_tab_s_84-review-1095p5.php. However, This website scored 35613 http://tabtec.com/android/samsung-galaxy-tab-s-8-4-shows-up-in-antutus-database/. So there seems to be quite a large divergence in scores.