yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] TheGoD:
Funktioniert sehr gut, bisher keine Probleme.
[Galaxy Tab S Original Android Development] sergybizzi:
Hi UpInTheAir thanks for your hard work. Your kernel is very nice works perfect!! I have a question this kernel have a kexec-hardboot patch? I want to try a multirom for T705 , primary rom a Sam based rom (with SkyHigh kernel) and secondary CM rom (wifi only T700).

It is possible test this?
[Galaxy Tab S Original Android Development] UpInTheAir:
Next to no chance. This kernel is suitable for only TW KK firmware. I'm not going to develop for CM or spend a lot of precious time for something I don't care for. ;)

Maybe ask your CM ROM/kernel dev to build for TW compatability + patch :)
[Galaxy Tab S Original Android Development] UpInTheAir:
I'll be back in the game hopefully this time next week. There are a couple things to take a look at, but don't really plan any huge update until LP. IF I get hold off a new data cable, I'll take a look at the USB controls once again.

LP will be released soon for my Note Edge and hopefully kernel source to follow not long after. That will be priority, but this tab is still great and with more to come ;)
[Galaxy Tab S Original Android Development] Sporbillis:
Awesome

Been using this kernel with the IronRom and i must say it's pretty damn good. I have a bit of a request though and i will need your knowledge on this. I am using your suggestions on post 3 for the battery life. What else is there i can do so i can be able to have my wifi/sync on and yet lose less battery? I am used on an ipad that had an awesome battery therefore i feel a bit weird that my battery goes down even when screen is off. I am losing close to 1-2 on a full night + wifi on always. Thanks
[Galaxy Tab S Original Android Development] pibach:
iPad min has 23.8 Wh battery, Tab S 8.4 has 18.6 Wh, i.e., 28% more. Otherwise the battery runtime should be in the same ballpark (if both had LTE?).
[Galaxy Tab S Original Android Development] UpInTheAir:
As I said in post #3, mostly down to user habit and what apps and processes are waking CPU to sync etc. WiFi ON will also consume power. I use greenify to hybernate a lot of rarely used apps and apps that I don't want to self start.

IPAD has horrible battery watching media and customization, whilst Tab-S has horrible battery playing some games and web surfing. Both have pros and cons due to hardware, software and user habit/needs, but this I'm not concerned with.
[Galaxy Tab S Original Android Development] lucky_515:
you should give yourself more credit..you are badd ass you got to kow this!!!!thanks for the kernal!
[Galaxy Tab S Original Android Development] UpInTheAir:
Back for a little play with the kernel again. Not sure what the end result will be yet. ;) Hopefully a KK update to give "flash-aholics" something to do. .. ;)

Just hoping LP kernel source will be released in a timely manner :)
[Galaxy Tab S Original Android Development] yreham:
I flashed this on ironROM BUT headphone volume or eq not work ....speaker tweaks ok
[Galaxy Tab S Original Android Development] UpInTheAir:
Read Post #3
[Galaxy Tab S Original Android Development] yreham:
Sorry but where is that undo buton ..is it the square one? How do i select all globally?
[Galaxy Tab S Original Android Development] UpInTheAir:
You didn't look hard enough ......

Read Post #3 - BUGS #1 ;)

Edit: For reset globally

1. tap square button

2. tap the 3 dots

3. tap "select all globally"

4. tap the back arrow button

5. apply
[Galaxy Tab S Original Android Development] UpInTheAir:
v2.8.0 released

R4_v2.8.0 kernel is now released for supported TW 8.4" models :)

Change-log is in Post #2.

NOTE: About Hotplug - I don't pretend to know a great deal about this, but have implemented and adapted [MENTION=441940]heyjoe66[/MENTION] work to suit. I set up synapse controls for SkyHigh kernel, maybe need further descriptions later on ;)

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 !!

T700 WIFI kernel is untested. 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 v2.8.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 battery life, try ONDEMAND GOVERNOR and recommendations in Post #3

Enjoy :good:

Cheers,

UITA

.
[Galaxy Tab S Original Android Development] maris__:
Thank you UITA for your continuous excellent support of our tab! The new kernel makes our tab running very smooth and fast!! :good:

I have observed one issue, which seems to be related to the SkyHigh kernel family. When trying to open the external SD card using File Manager HD (and only this app), then no item, files or folder, are displayed. "Empty folder" is indicated, although this is not the case, and although the home screen of the File Manager HD correctly indicated the used space for the SD card. Astonishingly, this issues occurs only with File Manager HD in combination with the SkyHigh kernel (also older versions) and not with any other file manager app. It also does not occur with the File Manager HD when a different kernel than SkyHigh is used. So it seems to be an interaction problem between File Manager HD and the SkyHigh kernel. Of course, this is not a real problem, as it can be easily resolved by using a different file manager app. But it would be interesting to know whether you might have an idea, where this behavior might come from.

With best regards, maris
[Galaxy Tab S Original Android Development] yreham:
Well im sorry but i did all of what you wrote but the only sound tweaks that work are the ones from the speakers......I just flahed your last kernel same thing...its ok ill live with it...the kernel is smooth fast and long lasting
[Galaxy Tab S Original Android Development] UpInTheAir:
Hi maris.

Not sure what ROM or firmware version you are using (you've not posted it !). I believe it might be a ROM incompatibility because I test https://play.google.com/store/apps/details?id=com.rhmsoft.fm.hd&hl=en OK with Skyhigh ROM v1.1 for T705. My ROM is basic stock with a few fixes (including exSDcard r/w fix).

Perhaps your ROM has a tweak that can be easily reversed to fix the issue, but can't think of what it could be. I'm sure it's simple.

Works perfect on my device and firmware mentioned above. Again, I have no idea what ROM, firmware, tweaks and settings you are using, but, if you are using stock ROM (with no audio modifications or sound changes), HeadPhone Equalizer WILL work using "work-around" in Post #3.

Edited below (correcting due to just waking up .... )

I tested method:

1. Use stock music player

2. Play "over the horizon" (leave playing)

3. Open synapse / audio

4. Disable "headphone equalizer" and apply

5. Enable "headphone equalizer" and apply

6. Adjust HP equalizer band gain settings and apply
[Galaxy Tab S Original Android Development] maris__:
Thank you very much for testing! Sorry, forgot to mention that I am also on Skyhigh ROM v1.1 for T705 plus Skyhigh kernel v2.8. So it was surprising to me that you could not replicate the empty file table for the external SD. I changed the settings in the File Manager HD, and found out that the external SD card is diplayed as empty only when Root Explorer access is activated. When Root Explorer is deactivated in the app settings, all files and folders are displayed correctly. When Root Explorer is re-activated, then the file table is again displayed as empty. I remember having obsereved the same behavior with my first custom ROM, which was SelambA-Rom plus Skyhigh kernel. When using a different kernel (e.g., Iron-kernel v1.1), files and folders of the external SD are correctly displayed (also when Root Explorer is activated). So my guess is, it might rather be kernal than ROM related.

However, please do not feel bothered by this issue, as it can be so easily circumvented, by using a different file explorer or, as I just learned, by switiching off root explorer access.

Best, maris
[Galaxy Tab S Original Android Development] UpInTheAir:
I can tell you that the app worked on my stated setup. extsdcard files were shown and accessible.

Just can't post a screen-shot right now. Tab is in a bad state from testing new patches and tweaks (won't elaborate), at least I know the cause, but the optional tweak would have been nice..........

Anyway, don't know why I feel the need to show "proof", but will post a screen-shot when I get up and running again

Edit: screen-shots attached. You might want to reconsider your assessment. As the app works for me, then it's most likely something you've done. What that exactly is, I don't know.

Edit2: Yes, YOU ARE CORRECT. In root mode, extsdcard files are not visible. Sorry, I misread your posts (in heat of battle with my soft bricked Tab) :) I don't know why, and as it's not really a critical issue, I probably won't spare the time to troubleshoot it. When time permits, I'll add to BUGS in Post #3. Thanks for reporting ! Anyway, Tab is back up again :)

.
[Galaxy Tab S Original Android Development] maris__:
Thank you ver much for the confirmation! It is very exciting to hear your are working on further optional tweaks :)
[Galaxy Tab S Original Android Development] Bogeyof:
Hi, I,m trying the newest version 2.8.0 on SM-T700. Glad to see, that hotplugging comes to this kernel, but I have to say, there are massive problems with it:

- there are 2 options for Hotplug-Management, "Screen on and off mode" and "Screen off mode". In "Screen off mode", cores go offline while Screen is off and dont reactivate if screen is on (interactive + conservative gov.). After Screen off and Screen on again, only 1 or 2 cores are online again, also under max. load. If I change back to "Screen on and off mode" all cores come back online...

- I prefer conservative gov. cause it´s much smoother on scrolling, but conservative doesn´t work correct with hotplugging. The A7 cores weren´t used (Screen on with no or less load), you can watch it in synapse at screen 2, A7 little Cores time in state and "live" cpu frequency...

Edit: tried many, many Reboots with different options:

- Reboot with "Screen off mode" and "interactive" Governor: After Screen off and on again only 2 cores are online (even with max. load) until load goes down to nearly zero. In this case (very low load) also while Screen is on some cores goes offline for a short period. And now all cores go back online under more load. It seems there is a initial setting if load reaches a minimum and afterwards all cores can be used again. But if load stays high, only 2 cores are working after every Screen off until load reaches a minimum...

- Reboot with "Screen on and off mode" and "interactive" Governor: All seems to work well...

- Reboot with "Screen off mode" and "conservative" Governor: Nearly same behaviour as with "interactive" but while Screen on no A7 cores were used (massive battery drain). After Reboot and no Screen off, for the first time A7 cores were used. After screen off, only 2 cores were used and load seems never low enough to fall back to A7 cores or "initial" settings for reactivating all cores like with "interactive".

- Reboot with "Screen on and off mode" and "conservative" Governor: while Screen on no A7 cores were used (massive battery drain).

Edit 2:

After changing the value "down threshold" from 20 to 40 for conservative governor, it seems to work ok with setting "Screen on and off mode". Now it scales back to A7 Cores and uses all cores after Screen on / off...

With this setting, also "Screen off mode" behaves like "interactive. Only 2 cores online after Screen off and on again, after low load 2nd core goes offline and afterwards all cores are usable again...
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks for your testing and report.

I need time to digest what you've written and also do some more testing.

Edit: sorry, could not "thank" your post. Have already reached my 8 "thanks" limit for the day .........
[Galaxy Tab S Original Android Development] UpInTheAir:
TESTING:

- CPU max scaling freq set = 1300 MHz (A7) & 1900 Mhz (A15)

- CPU min scaling freq set = 200 MHz (A7) & 500 MHz (A7)

- Use any number of “CPU Z” type app that show all 4 core frequencies

- Both hotplug modes tested after real time governor change and after reboots etc

Ondemand:

All cores OK after testing both hotplug modes. Test before and after reboot.

Interactive:

All cores OK after testing both hotplug modes. Test before and after reboot.

* 1x after switching from ondemand > interactive CPU freq remains high (stuck) on both hotplug modes (forgot to check the process that caused it …. ) Unable to reproduce after 10+ restarts with interactive or ondemand.

* 3x Synapse freeze when switching quickly from conservative > interactive (required hard reboot)

** I need to check this on legacy kernel versions (v2.7.0) to see if it's hotplug related, Synapse, or something else.

Conservative:

CPU freq remains high unless user increases down threshold to ~60 and up threshold to 85 (maybe I will set these values as default in source for next kernel update. I don't use this governor and rarely test)

All cores now OK after testing both hotplug modes. Test before and after reboot.

* Sampling rate sometimes does not apply when changing to conservative

NOTE:

1. Synapse CPU current freq (A7/A15): What is displayed is only core0. Other core1-3 aren't displayed.

2. Synapse CPU freq time in state: What is displayed is only core0. Other core1-3 aren't displayed.

3. When in hotplug, online cores may have to do more work - higher load/freq (and take longer) as less cores are online to finish tasks. This may give better battery life at the expensive of a little performance in general use (depending on various other factors - type of task/s, process, gov and variables etc)

4. Synapse CPU FREQ tab uses higher load (and freq) due to the “live” values it computes. Ie. updating core temps, time-in-state and current CPU freq (A7/A15). This will obviously keep the CPU freq higher (and load) and higher freq longer in state whilst viewing this page (or others similar).

5. Hotplug uses A7 cores only

FINDINGS:

1. Both hotplug modes work fine for all CPU governors (except conservative) in kernel

default

state (and min CPU 200 MHz).

2. Conservative works fine with both hotplug modes after some tweaking..

3. Some random freezing when changing governor from conservative > interactive (cause yet to be determined)

4. One time stuck high freq after switching ondemand > interactive when using both hotplug modes (no logs unfortunately or unable to capture process)

I'll take a look a the governor switching tomorrow and compare with v2.7.0 :)

.
[Galaxy Tab S Original Android Development] Bogeyof:
Many thanks for your quick answers and testing!!!

For me, it´s not the same result. Made a short screen-recorder video, which can be found in my Dropbox:

https://www.dropbox.com/s/nswrqkl1sjwn0oq/screen-recording_20150301-161735.mp4?dl=0

TESTING:

CPU Frequencies default, should be like yours:

- CPU max scaling freq set = 1300 MHz (A7) & 1900 Mhz (A15)

- CPU min scaling freq set = 200 MHz (A7) & 500 MHz (A7)

- Use CPU-Z and System Monitor app that show all 4 core frequencies

- Both Hotplug modes tested after reboot

In the short screen recorder video, you see after a fresh reboot and no changes in synapse, I´m on "interactive" governor and standard frequencies with Hotplug option "Screen on and off". System monitor floating windows shows frequencies and cores online. Later in the video, also CPU-Z shows cores and frequencies.

Video timeline:

After scrolling the 3 screens in synapse, I did a screen off and on, you can see all cores go online again after Screen on (Mode "Screen on and off"). I scrolled again 1/2 screen for keeping frequencies high and all cores online...

Now I changed Hotplug mode to "Screen off mode" and did Screen off/on again. From now on only 2 cores go online and even starting Antutu won´t reset all cores to online.

Same behavor is with other governor like conservative. In "Screen off mode" after Screen off/on only 2 cores goes online until load is so low that 2nd core goes offline too. After that all cores going online again under heavy load...

It´s 100% reproducible and I also had stucking cores at max freq. after changing between conservative and interactive more than 1 time. May be I can provide something else (logcat) to help...

Edit: For me its enough to set Down threshold to 35 or 40 and conservative gov. runs well with normal hotplugging and scaling down to 250 MHz (= 500 MHz I think !?)
[Galaxy Tab S Original Android Development] UpInTheAir:
I'll take a look at your video tomorrow.

I just tested interactive once again, this time multi-widow with CPU-Z and Antutu ( load the cores).

All kernel defaults

No 3rd party CPU type apps or tweaks that interfere with kernel

SkyHigh ROM v1.1

DVFS disabled

Hotplug screen on mode:

Cores 1-3 come online according to load

Cores 1-3 go offline according to load

Same for Hotplug screen off mode and both tests also done again after reboot.

1. Make sure NO 3rd party CPU tour apps or tweaks that interfere with kernel are installed.

2. Please provide your ROM and firmware version and also device model when reporting. I don't have your device, so others maybe able to help out.
[Galaxy Tab S Original Android Development] Bogeyof:
Thanks again for your time and testing.

One question, did you turn off screen and turn it on again. Problem appears only after turning Screen off/on?

Your questions:

1. Definitely NO other CPU/System App installed (like TricksterMod, Faux or others)

All settings default (resetted and rebooted)

2. Stock Samsung firmware for SM-T700 (T700XXU1ANF9, DBT German), Skyhigh 2.8.0, rooted, TWRP, DVFS-Disabler enabled...
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, of course :)

You are using very old firmware base. The kernel may not be compatible or should I say, your firmware may not be compatible with the kernel.

I would suggest a manual upgrade, perhaps this will help. ;)

Still the random issue of freeze when changing gov back to interactive. Will try and rule some things out today.

Edit: I think good news. I've applied a couple of patches for interactive and re-compiled. I cannot get device to freeze when changing ondemand/conservative > interactive gov . I switch another 100x with different hotplug modes, screen on & off, and dis/connected to USB power. :)

Edit2: [MENTION=4353870]Bogeyof[/MENTION] ,

I've managed to reproduce part of your issue of cores staying online. I know SD chipsets had this issue on Note3 with hotplugging, and relsoved by restarting MPdecision. I'm not sure what we can do for our Exynos yet. I will study heyjoe66 github and hopefully something there will help.

My findings:

1. Only with Interactive gov

2. Only Hotplug screen off mode

3. Usually after resume

4. Mostly Cores0/1, but also had Cores0/2 and Cores0/1/2

I haven't found anything in logs that I might be able to understand (or Google)
[Galaxy Tab S Original Android Development] pibach:
What do you guys use to verify the CPU frequencies? Is there any app that can show all 8 cores, as overlay?
[Galaxy Tab S Original Android Development] Bogeyof:
There is a free App in Google Play called System Monitor, shows 4 cores (there are max 4 cores online, A15 or A7), you can show it as a floating window over all other Apps...
[Galaxy Tab S Original Android Development] pibach:
The one by Christian Göllner? Seemingly the floating option is available in the paid version only.
[Galaxy Tab S Original Android Development] UpInTheAir:
I just use any app that shows the 4 cores and observe/test in multi-window.

I don't use any app that has capability to interfere or modify kernel values (except Synapse), so I just use CPU-Z ;)

Anyway, so still have an issue with interactive gov not allowing all cores back online with Hotplug screen off mode. I've done a heap of testing today and no win on this yet. I will try some more interactive patches etc tomorrow. If I can't fix it, Hotplug will go.

EDIT: [MENTION=4353870]Bogeyof[/MENTION] , I'll PM you tomorrow with a new T700 test kernel. If you can please spare the time, I need more constructive feedback from you. ;)
[Galaxy Tab S Original Android Development] drmodify:
Nice work! But let me get this straight, this will work right off the bat? No need to change settings via synapse unless I want to eh?
[Galaxy Tab S Original Android Development] Bogeyof:
[MENTION=3511708]UpInTheAir[/MENTION] Yes for sure, I will help as much as I can. I have enough time and, after 25 years of software developing, I also know a bit about testing ...
[Galaxy Tab S Original Android Development] pibach:
Theoretically, yes.

In practice you will go for untervolting, as this provides most benefit. Overclocking might not be worth it though.

Synapse can be quite overwhelming.

Anyway, very interesting to see the all these kernel options ;)
[Galaxy Tab S Original Android Development] UpInTheAir:
You don't even need to install it if you don't wish. Not using Synapse would exclude some very nice features.

If playing with voltages etc, just make very small adjustment and test for stability.

I would suggest to disable synapse from boot (in synapse app settings - 3 vertical dots in to right hand corner) until you are familiar with your device and what settings are stable ;)

If you're after some generic battery or performance tweaks, read Post 3. Suggest to read Posts #1-3 and v2.8.0 release post too.

Thanks :)
[Galaxy Tab S Original Android Development] drmodify:
Of course I will install this and give it a try looks promising.

Yeah I read them and saw all the features and the warning that user Habit is number one :(

Just wondering if this will work as programmed automatically or if you really need to set up synapse for that beefed up fly performance
[Galaxy Tab S Original Android Development] UpInTheAir:
There are default performance/battery changes made to kernel that might help without user interaction.

As I said, read Post#3 (the whole of it) for further generic info that should be applicable to 99% or users/devices. I have not included any further advanced tweaking, as user habit and device build quality (asv group) has a lot to do with it.
[Galaxy Tab S Original Android Development] pibach:
Fly performance? Maybe its a bit smoother? Or better battery life? Difficult to assess. I flashed back and forth to stock kernel to verify and can't tell any observable difference. Benchmarks, task switching, keyboard blending, browser scrolling/pan/zoom - remains same ballpark. I can only vaguely guess what all the listed features realy do, but seemingly their effect on user experience is rather minor. Maybe they add up for some % improvement, don't know, but nothing I could truely recognize. Only thing I can tell for sure, deriving from therory, is that undervolting will reduce power consumption.

So overall you get some control over system parameters to tinker (which will be irrelevant for most users) plus probably 5-10% more battery runtime from undervolting - at the costs of fiddelIng with voltage levels and unknown stability. That's it.
[Galaxy Tab S Original Android Development] UpInTheAir:
Can

one

user from T700 & T705 confim they have TWO /proc/last_kmsg files ?

Thanks.

EDIT: confirmed. thanks
[Galaxy Tab S Original Android Development] Bogeyof:
Can confirm, for me its the same, but they have exactly same size and date, so are these really two files or only to directory entries?

I just found your message (PM, didn´t receive any notification for new PM), will test asap and report...

Edit: OK, found wrong settings for PM, "notification mail on PM" was unchecked. From now on, it should work...