yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] UpInTheAir:
Charge controls

TBH, I've never played with the charge controls a great deal. Just had a little play and test of A/C Mains charging...........

Open Synapse and to battery controls to observe "Current Now"

Connect tab to A/C Mains charger

Switch on charger

"Current Now" displayed = ~1370 mA

Switch off charger

Set A/C Mains Input Current = 3000 mA (charger not capable of supplying though)

Set A/C Mains Charge Current = 2550 mA

"Current Now" displayed = ~1660 mA

Switch off charger

Set A/C Mains Charge Current = 2600 mA

Switch on charger

"Current Now" displayed = ~79 mA

This was repeated over again with near identical results (unstable power detection enabled/disabled).

Seems the charging controls are limited to 2550 mA max (for whatever reason).

Doesn't appear the A/C Mains (screen-on) charging controls have any affect. Perhaps they will with some other type of charging source ?

I just don't really want to get further into it right now or look at the source. I've done enough over the last few weeks and preparing for work commitments.

Food for thought anyway :)
[Galaxy Tab S Original Android Development] UpInTheAir:
ALL.

I hoped you enjoyed the effort I've put into this LL kernel in starting from scratch, porting a lot of mods/patches from my KK kernel and then updating in such a short time period.

v1.5 is the last until next month. "To do" list #1 is looking at some memory management issues. Hopefully a new source will also be released by Samsung and more fun on the horizon :)

The best,

UITA
[Galaxy Tab S Original Android Development] meduza:
1.5 makes a good (first) impression on t800 :)

Thx.!

m.
[Galaxy Tab S Original Android Development] meduza:
After over 24h action on 1.5 I discovered two issues:

- clock doesn't work/synchronize after tab was inactive for a while

- the app gravity screen pro doesn't work 100% correctly. Has to be enabled manually after tab was inactive for a while. The app is using sensors to switch screen off/on. This issue is definitely kernel not app related because it (actually both issues) appeared after flashing 1.5.

If logs are helpful, I would provide them, just tall me what log would be useful.

m.
[Galaxy Tab S Original Android Development] UpInTheAir:
Clock seems fine on my device, not kernel related.

Tried the free version, appears to do as designed.

There is a motion timeout setting (without checking, I assume it holds a small wakelock. No matter what they say, it will consume battery).

I tested it and fails to wake after designed 10 min setting.

Tested again set timeout to 1 min and failed to wake then.

Also tested the motion sensor waking without issue.

Conclusion: from my brief tests with the free version and kernel v1.5, can't fault anything on my T705XXU1BOE6 device which is compiled with the same (sensor/proximity) drivers as all other Exynos variants. I haven't tested with any other kernel version, because it works.
[Galaxy Tab S Original Android Development] meduza:
Thanx for testing! I think, there must be something with the walker up, because gravity doesn't start like it should and the time doesn't update when device was inactive for a longer time. Non of those issues was present before flashing 1.5.

I`m on the OE3 FW.

m.

PS.

Just switched the tab to sleep, disabled Wi-Fi, changed physical location and network. Time was absolutely wrong and gravity didn't work after tab was walked up again.
[Galaxy Tab S Original Android Development] UpInTheAir:
As I said, clock time IS NOT KERNEL related. If your GPS, modem and wifi work, then from a kernel perspective, that's ok.

As I said, there are timeouts in the app, depending on user settings. The app also mentions that if you use power button to sleep, the app may not work properly either . ...

If you could please follow the guidelines outlined in post #3 so we know your exact device configuration and EXACT steps / method to reproduce. Thanks.

ALL.

I'm away now for this month, but will still be checking in now and then. Won't be near a PC for any debugging or development purposes. You need to help yourselves (and each other) to narrow things down if it's kernel related. Please search first, read /follow Post #3 and try things yourself before posting your issue.

Cheers.

UITA
[Galaxy Tab S Original Android Development] Tinchoska:
Guys this is for stock firmwares using touch wiz right? And lp
[Galaxy Tab S Original Android Development] freaksamael:
Yes; the title of thread is self-explanatory "SkyHigh TW LL Kernel".
[Galaxy Tab S Original Android Development] Tinchoska:
Ups, wrong thread, it wasn't for this...je je lol, thanks for the answer any way my friend
[Galaxy Tab S Original Android Development] crownvn:
Do I flash this kernal by TWRP?
[Galaxy Tab S Original Android Development] meduza:
...or any other custom recovery :)

m.
[Galaxy Tab S Original Android Development] freaksamael:
Yes, only from TWRP. Check post #1:

INSTALLATION

Backup your WIFI settings if you are coming from stock ROM or kernel with ro.securestorage.support=true

Backup your original boot.img [BOOT] in custom recovery (or better to backup everything)

Uninstall any CPU control apps, tweaks and scripts etc.

Recommend: Disable or remove KNOX (you can disable with Synapse once kernel is flashed if you wish)

Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!

Disconnect device from PC USB

Device settings > developer options > enable USB debugging

If flashing from previous SkyHigh kernel > Force Stop Synapse app > clear data

Flash SkyHigh kernel in custom recovery

If you wish F2FS (data & cache partitions)

Follow > THIS < guide, but flash SkyHigh kernel instead !!

After boot:

a) wait at least 60-120 secs to stabilize

b) Open Synapse

c) Tap "Understood" and apply

d) Change any setting and apply
[Galaxy Tab S Original Android Development] UpInTheAir:
Answer below. Any means any....

Any custom recovery. TWRP F2FS only needed if you wish to change file system to F2FS for cache and data partitions. Otherwise an appropriate CWM recovery should work. Backups may not be compatible between them though.

Perhaps Post #2 :)
[Galaxy Tab S Original Android Development] crownvn:
My cpu is ARM V7 (VFPv4 Neon) ,as post1 it suiable for exyno ,it means my divice cant?
[Galaxy Tab S Original Android Development] UpInTheAir:
If your device meets the REQUIREMENTS listed in Post 2, you should be OK. You need latest compatible firmware for successful boot.

If you don't understand what processor your device has, maybe flashing this kernel might not be advised......... You can use various apps (CPU-Z) etc to give you device info, or check your /system/build.prop for universal5420

Some advice:

But if you still would like to try and tweak your values, best to read/search things first and know how to recover your device because this thread is not a help thread for newbies. Don't under-volt too much and do not set Synapse to apply settings on boot (Synapse menu settings) until your settings are stable. If you need to ask, better to leave settings as default ;) Although I have made many descriptions available for Synapse, some element of experience is needed to competently adjust some values.

Enjoy :)
[Galaxy Tab S Original Android Development] MohamedN:
@op

I need to sincerely apologize for my stupid act of reporting what I thought a freeze issue without following the instructions on post 3 even though I have red them.

The issue was completely user error not related to the kernel in any way.

Your work is top notch. Keep it up please [emoji106] [emoji106]

Sent from my SM-T705
[Galaxy Tab S Original Android Development] UpInTheAir:
We all have "bad" days ...... ;)

I won't even consider looking at logs if some element of user self-troubleshooting isn't done. If I can't reproduce it, more than likely points to something unrelated to kernel, but user settings, ROM, apps, tweaks etc. That's why I require a baseline to work from, and although I test method on my own T705 device, every single eventuality still can't be covered, especially since I don't have other variants to test fully. Constructive user feedback is required to help out :)
[Galaxy Tab S Original Android Development] Tinchoska:
Guys what about battery here? On stock listening music and reading comics and browsing Facebook news pages I have this stays
[Galaxy Tab S Original Android Development] Orical:
Sorry wrong place, my bad.
[Galaxy Tab S Original Android Development] UpInTheAir:
Could users please confirm if SkyHigh kernel v1.5 is working with the following official firmware bases (

not

custom ROMs) :

SM-T700 WIFI

T700XXU1BOF2

T700XXU1BOF3

T700XXU1BOF4

SM-T705 LTE

T705XXU1BOF1

SM-T800 WIFI

T800KXU1BOF2

I would assume there will be further updates for various models soon. We won't know of current compatibility unless someone reports.

Cheers,

UITA
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
I decided to update once again xD. But I can confirm that skyhigh kernel for T800 runs fine on OF2 firmware from KOO region. Other than the bloat and Korean bootloader the firmware came with, skyhigh runs great!
[Galaxy Tab S Original Android Development] UpInTheAir:
Looks like I'll be supporting our Tab-S kernels for a little while longer yet ;)

Extremely disappointed in the specs of the Tab-S2............. Exynos 5433 (64 bit capable), but maybe "crippled" to run at 32 bit just like my Note Edge? Screen aspect ratio and dpi is down too, but not a deal breaker like the SoC etc !! Was hoping for at least expecting a 7420 (wishing for 7422) ......... Maybe the Sony Xperia Z4 Tablet (hopefully a compact 8" version) or future Z4 Ultra could be worth a look?

This tablet is still sweet, and more optimization updates expected from Samsung and my SkyHigh kernel. Wait and see :)
[Galaxy Tab S Original Android Development] MohamedN:
Lucky us [emoji106]

Sent from my SM-T705
[Galaxy Tab S Original Android Development] s_john8686:
Lucky us to have you and your kernel.

I have just bought a Tab S, was initially a bit upset to hear that the Tab S 2 is coming :(

After reading your comment above it gave me a better feeling, definitely :D And BTW, the Synapse has a lot of settings that we can tweak our Tab S. Is there any guide on what we should really do ? So far I only did mild underclock to try to extend the battery life. Is there any guide on how we may extend the battery life while improving the performance / responsiveness of the Tab S ? Speaking from a normal user perspective ....

Thanks in advance.
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks.

SkyHigh kernel (Synapse) defaults are balanced and if you wish to try various generic tweaks, I've added some Battery and Performance tips to Post No #3. Suggest not to UV too much and do not set Synapse to enable on boot until you have stable settings. For further info please read Post No #3 in full and anything else (advanced) if you don't understand after reading Synapse descriptions + some Googling, best to leave as default ..... QoS changes may not be immediately evident until you use video or camera or such, so be careful !

Cheers,

UITA
[Galaxy Tab S Original Android Development] Orical:
Just an update, I've tried every configuration to get Ubuntu running using the kernel the way it is and it's not going to happen, loop tester says the device will run it but the few other files are apparently needed to get it to work. I'm more than willing to test out a few builds if interested in it. That would make this kernel the only one that supports it for this device and would add so much more to such a great device.
[Galaxy Tab S Original Android Development] UpInTheAir:
I'll see if I can get kernel to compile (and boot) with those few extra drivers enabled.

You'll have to be patient though, not due to return home until another 15 days ........... Also got a few adjustments and additions to look into, but unable to do anything until then afraid.
[Galaxy Tab S Original Android Development] Orical:
No problem at all man, I've got nothing but time so no worries from me, I'm just glad you're going to add do them in and once it's done and you get it compiled I'll do a walk through video on how to install Fedora, linux, etc. Thanks again for your time and effort.
[Galaxy Tab S Original Android Development] nimnab:
Sorry for asking.

Is there any way to restor all of synaps settings to its initial (default) value?
[Galaxy Tab S Original Android Development] Orical:
Go to app settings and clear data and you'll be all set.
[Galaxy Tab S Original Android Development] UpInTheAir:
Or. .. use the button found in the Synapse REBOOT Tab ;)
[Galaxy Tab S Original Android Development] UpInTheAir:
Paypal Donation Link

Hi SkyHigh users.

I have finally decided to add my PayPal donation link to my profile. I have previously refused many requests and suggested to donate to other more worthwhile parties. Times have changed and I suppose it's just another way of appreciation other than hitting the thanks button for the (years) and 1000's of hours spent for my contributions to many devices and forums. So why not?

I don't expect anything, but please be reminded to not expect anything more than what I'm able/capable of with my limited time and knowledge. We do this for the fun of it, not obligation ;)

Cheers,

UITA
[Galaxy Tab S Original Android Development] nimnab:
Thank you for your answer . however clearing data didnt restor all setting for me.

I have another problem. My device (t705) stops showing and using files on external sd (64 gig exfat) after a while. I thought it is somthing related to IO scheduler. I tried every algorithm and it changed only the time befor hiding files. Have any idea?
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, there appears to be a problem with the "Clear Synapse Data" button. I will look into that when I return.

Device settings > Applications > Force Stop Synapse app > Clear data and REBOOT

or

Use the Synapse menu > top right-hand corner to "select all globally" >>>>>

Had had a similar issue a while back, turned out to be a bad Sandisk sdcard because that card would do the same thing in my Note Edge
[Galaxy Tab S Original Android Development] UpInTheAir:
Any user is having major home screen re-draw with SkyHigh kernel and LMK Whitelist enabled ?

Work-around for now is disable LMK Whitelist for system apps (maybe reboot, not sure). You could also remove the launcher from the list found in your internal storage SkyHigh folder and reboot (not tested this).

I will try to take a look and make adjustments when I return. I'm almost sure this is the culprit.

Cheers

UITA
[Galaxy Tab S Original Android Development] dknk99:
I'm back on rooted stock, I had lots of redraw issues and sluggishness especially when downloading a torrent file. Also went back to ext4 from f2fs.
[Galaxy Tab S Original Android Development] UpInTheAir:
And the point is what? You tried my suggestions above? Also did you read Post #3 about streaming and try it as well? Perhaps that will help.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Well I did have a few redraws on stock homescreen, and switching between apps like YouTube and hangouts (mostly on those three things) with skyhigh installed. I followed your suggestion and disabled(untick the box) LMK whitelist for system apps and rebooted. After running for a day or two after disabling that, I've seen no redraws or reloads on the home screen. Switching between Hangouts and YouTube doesnt show a black screen and reload anymore too(in a good way), so.. Everything seems to be working fine! Though I can't be sure, its what I've experienced so far.
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks for your continued constructive support, testing and feedback! :thumbup:
[Galaxy Tab S Original Android Development] dknk99:
Oops, my bad. Re-installed 1.5, made those changes you pointed out, seems to be better after 24 hrs of use. Thanks for that kick in the butt...
[Galaxy Tab S Original Android Development] UpInTheAir:
Butt kicking over :)

Please report back again if ok after a few days or issue.
[Galaxy Tab S Original Android Development] s_john8686:
As I underclocked earlier on, and could not reset the synapse, what I did was :

- to go to TWRP, restore the boot partition that I backup earlier on

- restart back to system, checked kernel info

- to go to TWRP again, flash v1.5

- clear cache & dalvik

- restart back to system

That shall reset the synapse back to default values correct ?
[Galaxy Tab S Original Android Development] UpInTheAir:
You don't need to do that.

As I posted just a few back:

http://xdaforums.com/showpost.php?p=62016936&postcount=252

Edit: forgot to mention, home end of week and intend to take a look at the kernel not long after that. Have a few little changes in mind.
[Galaxy Tab S Original Android Development] maxq1:
what do we do w/o you, man?!? btw: 4XT36337EM827082P
[Galaxy Tab S Original Android Development] UpInTheAir:
You're the first donation ever :) Thanks and appreciated mate
[Galaxy Tab S Original Android Development] qbic2:
wrong thread sorry
[Galaxy Tab S Original Android Development] dknk99:
After 6 days of use with LMK Whitelist system apps unchecked, the redraw issue has not been seen. I think you were correct in your assumption. Good one.
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks for reporting back.

Will have it either:

1. removed completely, or

2. disabled by default and/or

3. without launcher added by default, and

4. deleting any saved LMK whitelist config on internal sdcard SkyHigh folder on flash via zip

on next release :)
[Galaxy Tab S Original Android Development] geminiahmed:
Great kernel decreased the voltage for the CPU FOR FREQUENCIES 1.9GHZ and 2GHZ..

Much more stable and reliable at higher frequencies...

Trying out the battery fuelguage fixer.. 'Hope this can solve my inaccurate battery readings I have had in every Rom.

Running

*iron.Rom

*smt700..

*SkyHigh kernel

Thanks...

-Ahmed-

W
[Galaxy Tab S Original Android Development] UpInTheAir:
Update in progress

Working on a new update fro T705 & T805.

Please post your extracted stock boot.img from the following firmware packages so I can update your ramdisk to the latest:

T700XXU1BOF3 (higher change-list than __F4)

T800KXU1BOF2

You can download the firmware packages from sammobile or samsung-updates (approx 1.5GB )

Without boot.img, T700 & T800 devices will miss out ;)

Edit: [MENTION=4106798]Orical[/MENTION] , I can try compile a kernel with extra loopback drivers enabled for you testing after this update, that is if you're still interested ?

Cheers,

UITA
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
T800 OF2 boot.img https://www.androidfilehost.com/?fid=24052804347789605

Thanks!
[Galaxy Tab S Original Android Development] rookie12:
Will you be planning to add more CPU governors?
[Galaxy Tab S Original Android Development] UpInTheAir:
Nope, they are not optimized / designed for our Exynos big.LITTLE device. Interactive and On-demand are still best. A fancy name does not make it better ;)
[Galaxy Tab S Original Android Development] UpInTheAir:
v1.6 released for SM-T705 + SM-T800

v1.6 update release for SM-T705 LTE & SM-T800 device

Tested by UpInTheAir with

:

SM-T705 LTE 16GB device

rooted stock T705XXU1BOF2 firmware

F2FS cache and data file systems

no Xposed etc

Tested by [MENTION=5978945]DUHAsianSKILLZ[/MENTION] with

:

SM-T800 WIFI 16GB device

BOE3 firmware

Xposed installed

IF YOU HAVE AN ISSUE AND HAVE NOT SHOWN RESPECT TO ACTUALLY READ POSTS #1-3 - DO NOT BOTHER POST. THIS IS BREAKING XDA RULE #1 'SEARCH BEFORE POSTING"

READ Posts #1-3 and especially Post #3 for confirmed supported firmware base ! !

Don't forget to force stop & wipe Synapse data before flashing

F2FS users: backup your data to extSdCard

before

converting data partition !!

Have fun :)

Edit: forgot to link v1.6 to Post #2. Please check your version number !! Is corrected now ;)

Edit2: SM-T800 WIFI v1.6 released

Cheers

UITA
[Galaxy Tab S Original Android Development] Orical:
Definitely, I've actually been waiting for you to add it but I didn't want to be a pest about it.
[Galaxy Tab S Original Android Development] MohamedN:
Update is running Amazingly well [emoji106]

T705 XXU1BOE6

Sent from my SM-T705
[Galaxy Tab S Original Android Development] UpInTheAir:
loopback test

[MENTION=4106798]Orical[/MENTION]

I've attached SM-T800 v1.6 + Loopback_v1 for your test.

The same patch will boot on my SM-T705 device but have not tested with Ubuntu.

In addition to already set defconfig build flags:

[COLOR="Red"]CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8[/COLOR]

I've changed the following in deconfig thus far:

diff --git a/arch/arm/configs/SkyHigh-T800-LL_defconfig b/arch/arm/configs/SkyHigh-T800-LL_defconfig
index afe4a19..16bd40b 100755
--- a/arch/arm/configs/SkyHigh-T800-LL_defconfig
+++ b/arch/arm/configs/SkyHigh-T800-LL_defconfig
@@ -1265,7 +1265,7 @@ CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
[COLOR="Red"]CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8[/COLOR]
[COLOR="DarkOrchid"]-# CONFIG_BLK_DEV_CRYPTOLOOP is not set[/COLOR]
[COLOR="MediumTurquoise"]+CONFIG_BLK_DEV_CRYPTOLOOP=y[/COLOR]

#
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected
@@ -1428,7 +1428,12 @@ CONFIG_DM_CRYPT=y
CONFIG_DM_UEVENT=y
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
[COLOR="DarkOrchid"]-# CONFIG_TARGET_CORE is not set[/COLOR]
[COLOR="MediumTurquoise"]+CONFIG_TARGET_CORE=y
+CONFIG_TCM_IBLOCK=y
+CONFIG_TCM_FILEIO=y
+CONFIG_TCM_PSCSI=y
+CONFIG_LOOPBACK_TARGET=y
+CONFIG_ISCSI_TARGET=y[/COLOR]
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
@@ -2205,7 +2210,7 @@ CONFIG_IR_LIRC_CODEC=y
# CONFIG_IR_MCEUSB is not set
# CONFIG_IR_REDRAT3 is not set
# CONFIG_IR_STREAMZAP is not set
[COLOR="DarkOrchid"]-# CONFIG_RC_LOOPBACK is not set[/COLOR]
[COLOR="MediumTurquoise"]+CONFIG_RC_LOOPBACK=y[/COLOR]
# CONFIG_IR_GPIO_CIR is not set
CONFIG_MEDIA_TUNER=y
CONFIG_MEDIA_TUNER_CUSTOMISE=y
@@ -3290,6 +3295,7 @@ CONFIG_FS_MBCACHE=y
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
[COLOR="MediumTurquoise"]+# CONFIG_OCFS2_FS is not set[/COLOR]
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
@@ -3350,7 +3356,7 @@ CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_HUGETLB_PAGE is not set
[COLOR="DarkOrchid"]-# CONFIG_CONFIGFS_FS is not set[/COLOR]
[COLOR="MediumTurquoise"]+CONFIG_CONFIGFS_FS=y[/COLOR]
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
@@ -3445,6 +3451,7 @@ CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
[COLOR="MediumTurquoise"]+# CONFIG_DLM is not set[/COLOR]
CONFIG_DYNAMIC_FSYNC=y
CONFIG_RESTRICT_ROOTFS_SLAVE=y

Good luck with your testing :)

Cheers,

UITA
[Galaxy Tab S Original Android Development] UpInTheAir:
v1.6 released for SM-T805 LTE

v1.6 update release for SM-T805 LTE device

NOT TESTED !!

IF YOU HAVE AN ISSUE AND HAVE NOT SHOWN RESPECT TO ACTUALLY READ POSTS #1-3 - DO NOT BOTHER POST. THIS IS BREAKING XDA RULE #1 'SEARCH BEFORE POSTING"

READ Posts #1-3 and especially Post #3 for confirmed supported firmware base ! !

Don't forget to force stop & wipe Synapse data before flashing

F2FS users: backup your data to extSdCard

before

converting data partition !!

SM-T700 WIFI users, if you read back a page, you will know what to do. I'm not going to chase it ;)

Have fun :)

Cheers

UITA
[Galaxy Tab S Original Android Development] Orical:
I'll test it in the morning when I'm free of dealing with life, I'll let you know how it goes from there but I'll have a report for you as soon as I get it all set up and running.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
T700 OF3 Boot: https://www.androidfilehost.com/?fid=24052804347790599

I chased it for ya ☺
[Galaxy Tab S Original Android Development] rookie12:
Thank you for uplouding