yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Original Android Development] Elmar1801:
V2.8 runs nice and fluid on my n9208. Great work!
[Galaxy Note5 Original Android Development] gundal:
[MENTION=3511708]UpInTheAir[/MENTION]

The n9208 firmware you released, was that compiled using the SkyHigh_SM-N9208_TW_defconfig or the SkyHigh_SM-N9208_SEA_defconfig

thanks
[Galaxy Note5 Original Android Development] UpInTheAir:
They could be the same, but I can't remember. I use SEA though, but you can see just by looking at the branches I use.
[Galaxy Note5 Original Android Development] gundal:
oh you are building from the branch of the device? I thought you were building from skyhigh branch and had the sources alll merged just different defconfig. thanks for the clarification
[Galaxy Note5 Original Android Development] UpInTheAir:
No. I use SkyHigh branch which ALL source links are directed. ...... Those branches are where I've obtained the diff to use as patches to merge. I haven't uploaded any the Edge+ as never intend to merge anything from those stock sources. Just the original defconfig / dts files

I haven't merged that source in though as kernel is working. Just seems to be some problems with other variants (T). Probably need to revert something. Someone is going to lose out. This is why I didn't really wish to merge in various sources as one little thing may cause huge issue with ROM or Bootloader comparably etc.
[Galaxy Note5 Original Android Development] UpInTheAir:
v2.9 released

v2.9 update for:

SM-N920-C / CD / 8 / G / I / 0 device variants

Check out the change-log in Post #2.

Tested by UpInTheAir

:

My device setup:

SM-N920C

100% stock N920CXXU1AOI1 (THL) firmware

No modifications (apart from kernel and TWRP)

SkyHigh kernel defaults

No Xposed or other tweaks etc.

STABLE & RE-BOOT FREE !!

Please CLEAR SYNAPSE DATA

before flash

: device settings > Applications > Application manager > Synapse > force stop > clear data

Please read v2.8 change-log in Post #2 on how to update your SuperSU binary to v2.52

Please read the amended Installation Instructions, especially #8

DO NOT restore profiles from older versions or other kernels !

XDA RULE #1 'SEARCH BEFORE POSTING". Please READ Posts #1-3 BEFORE flashing !!

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] gundal:
Thanks, I'm trying to determine why stock kernel and my kernel cause phone crashing issues using ketan Rom, which is 9208sea. They work fine with TW but crash on sea. Your kernel image works on both (with either stock or my ramdisk) and so since you are telling yours is based on Sea ill start looking at the differences. Thanks again for insight, appreciate it.. :)

Yea I'm still not sure which models have the md9x35 modem and which have Shannon, do you know if all dual SIM are the 9x35 or did Sammy make an in-house dual as well?

Also the newest from Sammy that you didn't merge in, doesn't even build right out of the zip file without tons of warnings, it's kind of comical they expect us to believe that's actually a true clone of the commit they built the kernel from.

So just to confirm, your compiled n9208 kernel is essentially using the original OGE source release for the 9208_sea as a base?
[Galaxy Note5 Original Android Development] UpInTheAir:
I don't believe the N9208 defconfig has changed since newer sources have been released. = no update on that. EDIT: No, the source is not OGE. Merges of multiple sources for various device builds. It is SkyHigh source ;)

Many variants can be used as a universal IMAGE (and modem). All you need to do is diff (compare) the defconfigs and ramdisks I could probably remove some from my source, but that's for later.

Yes, same goes for the dts files, I'm just using the proven stock dt.img for stability (as in OP). You just need to fix the errors, it will compile if you've set up correctly and fixed them. My source is in compliance with GPL, I fixed what was needed, nothing to hide if you actually look for them. ......................

Best of luck
[Galaxy Note5 Original Android Development] Akia Azriel:
[MENTION=3511708]UpInTheAir[/MENTION] First of all I'd like to thank for a great kernel. I've been having problems with the xialu kernel before. When I tried this it worked wonders. So here's my problem. I've been getting heavy battery drainage for quite a while after flashing via odin v2.8. I'm using SM-N9208 btw. So now I'm trying your latest version v2.9. Will update right away. Thanks again for the great kernel.
[Galaxy Note5 Original Android Development] kirasan13:
What kind of problem that u r facing at xiaolu kernel?

Try v2.5
[Galaxy Note5 Original Android Development] UpInTheAir:
An how is this relevant to SkyHigh kernel development And promoting a NON-GPL compliant kernel in XDA ??
[Galaxy Note5 Original Android Development] kirasan13:
No no i mean try v2.5 skyhigh kernel

I notice when v2.6 is draining battery fast

Just trying to compare the latest 1 and 2.5 see how much different is the battery drain
[Galaxy Note5 Original Android Development] UpInTheAir:
root & system r/w <> r/o

[MENTION=336863]garyd9[/MENTION]

Finally got around to it :)

https://github.com/UpInTheAir/SM-N920/commit/9fe2a25b43b214d2894f735d53320e278d57841d
[Galaxy Note5 Original Android Development] andylow4421:
There are not root after I flashed with SkyHigh kernal but Busybox yes. Please advise.

N920IDVU2AOJ3
[Galaxy Note5 Original Android Development] UpInTheAir:
Install Root Validator app

https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator

And post your screenshot like this.

I assume you flashed v2.9 and I assume you used TWRP and assumed you installed SuperSU app....
[Galaxy Note5 Original Android Development] aclan:
Thx for the update, I just flashed with N9200ZHU2AOKA and everything seems ok.

Before v2.9, I encountered one auto-reboot issue with v2.8 when I received a incoming call while another call came in.

But I can't reproduce the problem again...
[Galaxy Note5 Original Android Development] andylow4421:
Yup, I did follow the instructions provided, install TWRP, SuperSU and Synapse. I did use Root checker but stated not ROOTED.

End up finally I Google, download and reinstall ROM N920IDVU2AOJ4, and retry all over again. Now its WORKS! As you know I am having reboot errors, might conflict by previous.

Anywhere, now I can enjoy root with my note. Thanks to you!:fingers-crossed::good:
[Galaxy Note5 Original Android Development] UpInTheAir:
v2.9 is looking promising :)

Yep, fresh install does wonders :) enjoy
[Galaxy Note5 Original Android Development] Akia Azriel:
[MENTION=3511708]UpInTheAir[/MENTION] I've been using v2.9 since the last time I posted here. It's great. Battery drain issues are long gone. That's the only concern I had with v2.8. I said it earlier and I'm gonna say it again. Great kernel. Thanks a bunch!
[Galaxy Note5 Original Android Development] garyd9:
Thank you.

What I'm not understanding is why the writes to rootfs are even needed. Several of the scripts don't write to the rootfs to begin with, and others probably shouldn't be. (Please keep in mind while reading this that I'm _not_ familiar with synapse and how it works internally. My suggestion here might cause a problem with synapse that I'm not aware of...)

For example, the "gpu_governor" script (as a random example) appears to use /res/synapse/SkyHigh/gpu_gov as some kind of cache for the new setting. Then, when reading the value, it does this:

P=/res/synapse/SkyHigh/gpu_gov
copy=`cat $P`
if [ $copy == Default ]; then
echo Default
elif [ $copy == Interactive ]; then
echo Interactive
elif [ $copy == Static ]; then
echo Static
elif [ $copy == Booster ]; then
echo Booster
fi

My first impression (without examining if the process has h/w to the sysfs file) is that it might be better to NOT use a file in rootfs/res/synapse, and instead do something like this:

S=/sys/devices/14ac0000.mali/dvfs_governor
copy=`cat $S`
# translate dvfs_governor values to human-readable.
if [ $copy == 0]; then
echo Default
elif [ $copy == 1]; then
echo Interactive
elif [ $copy == 2]; then
echo Static
elif [ $copy == 3]; then
echo Booster
fi

Then, the code in the top portion of this script that writes to /res/synapse/SkyHigh/gpu_gov could be completely removed (as well as both rootfs remounts.) This has an additional advantage of being "aware" of changes made outside of synapse.
[Galaxy Note5 Original Android Development] UpInTheAir:
Still have one little issue to sort out on it on it.

If you don't make root temporary r/w those actions will get permission errors in Synapse.

Also very quick look at what you've written. Makes senses initially, but need to digest later on when I've woken up. ..

Thanks for your input.
[Galaxy Note5 Original Android Development] gundal:
Haha oh man.. I was seriously stumped by this issue, I was sure I had defconfig lines wrong.. and using wrong drivers. It turns out simply that my kernel and stock were both enforcing.. So totally Rom issue.. Huge time waste, shoulda trusted my intuition, when stock works....

Just posting my findings if anyone else cares lol, thanks for letting me bounce that of you
[Galaxy Note5 Original Android Development] kumbangdesa:
hi sir.. Is any possibilities to make MHL support from the kernel?.. Thanks
[Galaxy Note5 Original Android Development] CanMan1:
I think a tester was needed

I'll may try it if you tell me what cables are needed. My MHL cable for my S4 doesn't fit in the Note5.
[Galaxy Note5 Original Android Development] UpInTheAir:
I don't know as I gave up on the idea and didn't want to force the connector and break the device micro USB connection. It's not important to me to risk it. Edit: But if anyone has a compatible adapter, then I might try and compile with enabled. I don't stress enough,

if it does not fit

DO NOT FORCE IT !!

Glad someone actually searched :thumbup:
[Galaxy Note5 Original Android Development] kumbangdesa:
I'm also got the mhl adaptor. I will test if you can try to build it. Thanks
[Galaxy Note5 Original Android Development] UpInTheAir:
So does it fit correctly (as far as you know) without forcing it or potential to damage the device? If any doubt, do not.

If yes, I can try compile the driver again for test.

Let me know
[Galaxy Note5 Original Android Development] kumbangdesa:
Yes it fit and I'll try.
[Galaxy Note5 Original Android Development] UpInTheAir:
You may need an app for it. I'll try post a test (kernel) for you tomorrow.
[Galaxy Note5 Original Android Development] CanMan1:
What adapter do you have? Can you post a link?
[Galaxy Note5 Original Android Development] LiL_Assassin:
Sorry for the off topic. Is anyone else having issues with Bluetooth and ps4 controllers? (old tablet doesn't have issue.) It lags in input after a while. Old tablet doesn't so this. (not blaming kernel, just curious)
[Galaxy Note5 Original Android Development] kumbangdesa:
Using samsung mhl adaptor but I think it's better to wait the test kernel first.
[Galaxy Note5 Original Android Development] UpInTheAir:
v2.9 MHL

Here is a SM-N9208 v2.9_MHL test version. As I said, you probably require an app to make it work, if it actually does.

Not sure which bootloader you have, so I uploaded both zip and tar.

#
# Mhl device support
#
[COLOR="Red"]-# CONFIG_SEC_MHL_SUPPORT is not set[/COLOR]
[COLOR="Green"]+CONFIG_SEC_MHL_SUPPORT=y[/COLOR]

N9208 v2.9_MHL Test kernels >> HERE

If it doesn't work, I'll eventually delete them from the repo, which is only for official releases.
[Galaxy Note5 Original Android Development] kumbangdesa:
Could you upload with flashable zip for this test kernel too?. Thanks.
[Galaxy Note5 Original Android Development] alexander1995:
Is there anyway to disable DVFS thermal throtting? DVFS Disabler didn't work and so did wanam xposed for Samsung
[Galaxy Note5 Original Android Development] UpInTheAir:
I suppose not then.

TMU throttling in itself is, but unwise because hardware safety limitations would be removed.
[Galaxy Note5 Original Android Development] fabiolmm1:
private mode

hi, this kernel is awesome, but did not work the private mode, even whith wanam xposed? has someone use the private mode with this kernel?
[Galaxy Note5 Original Android Development] anmolkakkar:
Installed v2.9, Performance is good. Battery Life is also very good (~2 days 4 hours) with decent screen-on time (~5 hours).

Only issue i faced (not a big concern though) was while using the "Ultra Power Saving Mode". Once the screen goes off, on pressing the power-button, it takes 5-7 seconds to respond back.
[Galaxy Note5 Original Android Development] CanMan1:
It works fine for me on 2.8 without wanam. ROM is Dr Ketan n9208
[Galaxy Note5 Original Android Development] UpInTheAir:
Can't find any issue with v2.9 defaults with stock SM -N920C OK7 ROM. No Xposed or Greenify etc installed.
[Galaxy Note5 Original Android Development] anmolkakkar:
I'd suggest let the device go into deep sleep for about 10 minutes and then try to replicate?

It happened to me couple of times.

I am also on Stock, rooted, OK7, no xposed/greenify.
[Galaxy Note5 Original Android Development] kumbangdesa:
I had test this yesterday and unfortunately it doesn't work. Not sure if it must be enable with any app or it already on by default. Thanks for the build sir. :)
[Galaxy Note5 Original Android Development] UpInTheAir:
I already told you you probably (more than once) require an app to make it work. It needs an interface.

Whether there is an app that works, is up to you to find out ;)
[Galaxy Note5 Original Android Development] kumbangdesa:
Yes i know that you had told me. Already find any app but no luck. It not so important to me since I got other devices that support mhl. I'm just enjoying to try it on note 5. Thanks a lot sir. ;)
[Galaxy Note5 Original Android Development] UpInTheAir:
I tested for 5 minutes and then 10 minutes. No issues. Tested with v3.0_RC , I doubt anything in my commits since v2.9 would affect what you're describing. Maybe another N920C user else can confirm with v2.9

Thanks for testing anyway :)
[Galaxy Note5 Original Android Development] anmolkakkar:
So you're suggesting to wait for v3.0 which might address this issue? ;)

Great work anyways :good:
[Galaxy Note5 Original Android Development] UpInTheAir:
There is no issue that you describe that I can replicate with either v2.9 or v3.0_RC

I was suggesting for someone else to help out and test as my device WAS in an experimental state of testing.

I have now reverted and tested for 13+ minutes with ultra-power-saving mode > no wake-up delay from under device conditions I previously described.
[Galaxy Note5 Original Android Development] alexander1995:
After doing some research I've managed to shut down the throttling and do the test. But it seems that 105℃ is the temperature that the phone will shut down no matter which frequency I used (1.9 to 2.4). To shut down the throttlng, please go to /sys/class/thermal/thermal_zone0, edit the "mode" by using text editor and change "enable" to "disable". Then the CPU will not throttle and my phone bump from 54xx to 57xx in the Geekbench3, running at 2.1G+1.5G

---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------

However, other files which control thermal temperature are automatic set to default even if I change the values. So, here is my question, is there anyway to change those actually? Cause the temperature settings in the synapse didn't work at all.
[Galaxy Note5 Original Android Development] UpInTheAir:
I know for a fact that at least the GPU thermal control does work. I have released from DVFS throttling in source (not TMU-thermal), so the CPU thermal controls probably do work too if TW DVFS is somehow disabled.

BTW [MENTION=535343]all[/MENTION]

I have made incorrect assumptions of the temperature sensors being same from Exynos5410 > 5420 > 5433 > 7420. Those 4 sensors are not all for A57 cores. The 3rd sensor will display "-1" when the GPU is at rest 0 MHz, and I tested the GPU thermal controls and observed the throttling and reduction of frequency at user set temperature.

EDIT: Found it :)

#elif defined(CONFIG_SOC_EXYNOS7420)
enum tmu_core_number {
EXYNOS_TMU_CORE_BIG	= 0, [COLOR="Red"]>>[/COLOR] sensor 0
EXYNOS_TMU_CORE_LITTLE, [COLOR="Red"]>>[/COLOR] sensor 1
EXYNOS_TMU_CORE_GPU, [COLOR="Red"] >>[/COLOR] sensor 2
EXYNOS_TMU_CORE_ISP, [COLOR="Red"]>>[/COLOR] sensor 3
};
#endif
[Galaxy Note5 Original Android Development] UpInTheAir:
v3.0 released

v3.0 update for:

Early Christmas present for all !! :highfive:

SM-N920-C / CD / G / I / 0 / 8 device variants

Check out the change-log in Post #2.

Tested by UpInTheAir

:

My device setup:

SM-N920C

100% stock N920CXXU1AOK7 (THL) firmware

No modifications (apart from kernel and TWRP)

SkyHigh kernel defaults

No Xposed or other tweaks etc.

STABLE & RE-BOOT FREE !!

Please CLEAR SYNAPSE DATA

before flash

: device settings > Applications > Application manager > Synapse > force stop > clear data

Please read the amended Installation Instructions, especially #8

DO NOT restore profiles from older versions or other kernels !

XDA RULE #1 'SEARCH BEFORE POSTING". Please READ Posts #1-3 BEFORE flashing !!

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] alexander1995:
DVFS DISABLER seems not to work on 5.1.1 or 7420. Is there any apps could disable it?
[Galaxy Note5 Original Android Development] UpInTheAir:
I've already replied to you, so please take it up on the relevant forums. Thanks.
[Galaxy Note5 Original Android Development] smalldroid:
You are hard working. Your kernel works well in my note 5 n9208tw. Thanks!

Gửi từ SM-N9208 của tôi bằng cách sử dụng Tapatalk
[Galaxy Note5 Original Android Development] ebusuhejbi:
Where is download link for sm-n920w8?
[Galaxy Note5 Original Android Development] aclan:
Thanks for your Early Christmas Gift! My N9200 flashed successfully. Everything goes well.

BTW: I used v2.9 for almost 3 days and There's no need to reboot ( and the device slept well ) !:good:
[Galaxy Note5 Original Android Development] garyd9:
Suggestion: Add to the FAQ (post 3?) information on what phone functions the driver wakelocks are associated with. For example, disabling sensorhub related wakelocks could potentially impact "S Health" (or google fit.)
[Galaxy Note5 Original Android Development] UpInTheAir:
Maybe. But no one really reads it. :p

Can be found out by Google. .. It's in advanced section, so shouldn't be touched anyway unless you know what you're doing.
[Galaxy Note5 Original Android Development] cornelito:
Top man !

I love my N9208 with your Kernel.

Keep up the good work !
[Galaxy Note5 Original Android Development] sarshar:
I'm on my brand new N920C since v2.5 and SkyHigh kernel has been on my device since the first day of buying.

ROM is stock OK6 with the same BL version

TWRP is 2.8.7.1 and Xposed+Wanam are my main apps.

I have never experienced SOT more than 4~5 hours even after disabling system apps as I know them safe to freeze.

Today I flashed SkyHigh 3 but no success, Wakelocks are draining battery like hell and the most hungry one is Android System at the top of the others, as GSAM with root says.

I bought Package Disabler Pro which was a waste of money as it doesn't work on rooted device (no need to mention it didn't work after unrooting procedure and dev is not responding in Google Play nor email reply)

Any suggestion ?

Any solution?

Any specific well known battery draining app included in Android System ?

is it kernel related maybe ?

Regards

EDIT:after disabling 3 added wakelock drivers, phone became unstable and rebooted 2 times, synapse clear data solved but with default profile which is not my goal of using custom kernels :(
[Galaxy Note5 Original Android Development] anmolkakkar:
Thanks for the updates. I hope it doesnt happen so often on my device.

Rest assured, the v2.9 seems very stable as a daily driver. :)

:good:
[Galaxy Note5 Original Android Development] UpInTheAir:
Thanks. Thats it for a good while.

Suggest to read Post #3. Clean stock I have no issues.
[Galaxy Note5 Original Android Development] nahsen27:
thanks for kernel. İts fantastic

Sorry my English
[Galaxy Note5 Original Android Development] inspiron_1420:
Hi Bro! I use V3 for N9208 smooth, nice battery! Big thank you!

Gửi từ SM-N9208 của tôi
[Galaxy Note5 Original Android Development] CanMan1:
I'm getting frequent read errors in Cool Tool when accessing /sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq. I've had this problem since 2.8 or earlier. I think it only occurs after the screen has been off for a while. Does the file ever disappear or have completely different values on screen off?
[Galaxy Note5 Original Android Development] 3473:
Would it be possible to implement something like

Screen Off Maximum A57 CPU

Screen Off Maximum A53 CPU

Thanks
[Galaxy Note5 Original Android Development] UpInTheAir:
It's cool tool. I've had that issue with all kernels on a number of devices. Perhaps it's from from the cores are hotplug

.

Just open cool tool > show panel > hide > show > close

Via some of ktoonsez patches is possible (mixed in with ktoonservative governor). The patches messed with frequency control and I could not fix it.

I've actually done via CortexBrain background service, but didn't like it.
[Galaxy Note5 Original Android Development] CanMan1:
Are there any other locations that I can read the A57 frequencies from?

Can you implement a screen off governor (eg conservative)?

Is sys/class/thermal/thermal_zone0 for A57, *1 A53, *2 GPU, *3 ISP? For monitoring purposes, which temp does the CPU throttling use? If both, which CPU core typically measures hottest?
[Galaxy Note5 Original Android Development] UpInTheAir:
1. I've already answered that previous post. Whilst the governor works, the accompanying code messes with the clock control. I tried to get rid of it, compiled ok but would reboot when change governor to ktoonservative.

2. Not 100% sure. Probably both. A57 gets hottest in heavy applications, GPU in graphic intensive operations.
[Galaxy Note5 Original Android Development] CanMan1:
1. I meant using the built in conservative kernel for screen off, not ktoonservative.
[Galaxy Note5 Original Android Development] UpInTheAir:
No.

I could for Interactive, but the value would be only static and same for both A53/57

Edit: you need to be looking here >> /sys/devices/10060000.tmu/curr_temp
[Galaxy Note5 Original Android Development] CanMan1:
Any idea what those thermal zones I used before measure? Thermal zone0 seems to match A57 temps. The other ones give strange values (32, 40, 32)
[Galaxy Note5 Original Android Development] UpInTheAir:
Read the "type" and search the kernel source.....
[Galaxy Note5 Original Android Development] Tomleungyuethei:
Does 3.0 also support the older firmware of N9200, such as OJ9?
[Galaxy Note5 Original Android Development] andylow4421:
I am using v2.9 currently, so i just flash 3.0 directly, any others action need to carry out? Btw, v2.9 works fantastic for me. :D
[Galaxy Note5 Original Android Development] UpInTheAir:
http://xdaforums.com/showpost.php?p=64174190&postcount=685

Did you bother to search ........................................... (XDA rule #1 )

http://xdaforums.com/showpost.php?p=62564377&postcount=2

http://xdaforums.com/showpost.php?p=64355487&postcount=872
[Galaxy Note5 Original Android Development] -=RaZoR=-:
Hi UpInTheAir ! thanks for the hard work! I have long been using their kernels and as always they're perfect.

only one question...

what about kernel for SM-G920F? the Thread is there but no links to download...

will the kernel for SM-G920F or not?
[Galaxy Note5 Original Android Development] Manson79:
Hi,

This v3.0 seems the best of all your versions (at least since I tested your kernel...), smoother for me, battery seems the same for me compared to the previous versions (so no complain, nothing wrong / nothing better to me about battery life.. but battery life depends... YOU KNOW THE STORY :D:p:D:angel:)... maybe the "placebo effect"? but not sure about this... :)

It was just a little humor :D :);)

Anyway great work on this v3.0, thanks for your gift ;)