yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Original Android Development] UpInTheAir:
Don't think so, as logs probably wouldn't show it.

You could however;

Set the same MIN & MAX frequency, then test voltage at that frequency ;) (or set Performance gov and test by changing MAX frequency)

Do for each frequency step.

Don't forget to disable "apply on boot" in Synapse app settings so you don't have issues rebooting after crash. There is always a risk of FS corruption by freeze/reboot without sync
[Galaxy Note5 Original Android Development] rajrup:
@UpinTheAir

please make a option double tap to lock screen wakeup bro.

Add a option in synapse app thank you :good:
[Galaxy Note5 Original Android Development] LiL_Assassin:
It's all good, you know more about this than I do. However that is what I have been doing. It's a slow process, as I want to test each one before I go to the next step, so I can nail the freq that is causing the reboots. But thanks for the heads up. Forgot about the untick of applying at boot. >.>
[Galaxy Note5 Original Android Development] UpInTheAir:
Please read Post #3 thanks.

Edit: In a technical term, we "break it down". meaning break the system at various points and test. This will eliminate points in the system. For example. Set MAX at half frequency scale (lets say A57 = 1400 MHz) and test with your existing voltages. If all not OK, then drop the MAX to 1000 MHz, and so on. Work up from 1400 MHz the same method. This way, you can narrow down the exact frequency without checking every single step.
[Galaxy Note5 Original Android Development] LiL_Assassin:
I think I understand it. But I hate to be a pain, but could you give me a screen shot of an example? Sorry I am more of a visual person to connect the dots so to speak.
[Galaxy Note5 Original Android Development] UpInTheAir:
Sorry, I made a mistake in previous post. My wife talking at same time. . .

example:

1000 - 1400 MHz

If all OK, set 700 - 900 MHz and test. If not OK, then voltage 1000 - 1400 MHz is too low.

Same principle to work upwards.

1600 - 1800 MHz

If all OK, then set 1704 - 2100 MHz. If not OK, then voltage 1600-1800 MHz is too low.

This way you only need to test a few times, and narrow down frequencies requiring an increase in voltages. It's a real "trial and error" process, and each chip and frequency can be different (even with same asv_summary)
[Galaxy Note5 Original Android Development] ovid1u:
[MENTION=3511708]UpInTheAir[/MENTION] for N920L? please . Thanks in advance
[Galaxy Note5 Original Android Development] UpInTheAir:
Post #3 "Help and FAQ"
[Galaxy Note5 Original Android Development] pratik_193:
hey UITA, you remember i had a problem that mic does not work when speaker phone is enabled? i tried this, flashed 3.5, without any modification in synapse, i tried mic on speaker, it worked,.! but when i fine tuned synapse, the mic broke again..

can you think of any parameter which can cause this ?
[Galaxy Note5 Original Android Development] UpInTheAir:
Nope, I don't have any issue on my N920C.

I don't have your device, so unfortunately it's up to you to narrow it down by a little trial and error.
[Galaxy Note5 Original Android Development] Rsroms:
[MENTION=3511708]UpInTheAir[/MENTION]

Thoroughly impressed. Great Kernel, great performance and stability. You did a great job. (Y)
[Galaxy Note5 Original Android Development] Manson79:
Hi,

[MENTION=3511708]UpInTheAir[/MENTION], for interactive governor what exactly do these settings "mode" and "enforced_mode" (0 or 1)?

They make a difference in general UI and benches (after deep tests), regardless of what I set for the Interactive profile for both A53 / A57 or for the Turbo Mode for A57 (I tought it was related to that but apparently no for what I've tested and these settings are also present in arter97's kernel without your performance / Turbo Mode tweaks ).

I adjust these settings for testing purpose in Synapse by editing your ramdisk (before I was doing that directly with Root Explorer /sys/devices/system/cpu -> cpu0 and cpu4), I unpack / repack your boot.img but it's just for my personnal use / tests / settings.

I searched also a bit, but for this time it seems that Google is not my friend... :p :laugh:

Thanks in advance ;)
[Galaxy Note5 Original Android Development] UpInTheAir:
They are to do with "turbo mode" and have been deliberately excluded from governor tunables because will can apply-discard bug with Synapse.
[Galaxy Note5 Original Android Development] kenpaci:
Wow! After 2 and circle battery charger full now this kernel its true amazing, very improve my battery power, and so smooth, thank to ULPN for hard work, salute to dev, using venom+ skyhigh v35 so good combination
[Galaxy Note5 Original Android Development] shapk:
Can you post somme battery life screenshots?
[Galaxy Note5 Original Android Development] kenpaci:
here
[Galaxy Note5 Original Android Development] Manson79:
Thanks for the reply (sorry, I'm out of thanks for today), also did you check your PM's? :)

By editing your ramdisk I have no issue in synapse with these two settings, they are not reseted after boot, no error in Synapse (I have issue with other settings like "hispeed_freq" but I know it's due to the permissions you setted to override TW stuff), I can change them (on / off, I mean 0 / 1) but maybe I explained wrong or I don't understand your explanation...

What I meant is these two settings are present in your kernel and like you said it's in correlation with "Turbo Mode"... but these values are also present in arter97's kernel wich do not use "Turbo Mode"

at all

so... :confused:

I can enable / disable "Turbo Mode" and at the same time playing with "mode" and "enforced_mode" with different results with different combination (UI and benches)...

My question was just what these values stand for? Because it seems I don't understand them :p:D

Sorry for the inconvenience :o
[Galaxy Note5 Original Android Development] kenpaci:
I think this more detail
[Galaxy Note5 Original Android Development] Manson79:
[MENTION=3511708]UpInTheAir[/MENTION]

I'm out of thanks for today... But hopefully I'm not out of money Ah Ah Ah... :D:D:D

Confirmation number: 6RS03663J5482082J ;)

:)

EDIT: I have my "thanks" recovers, done... :);)
[Galaxy Note5 Original Android Development] Manson79:
This need a star and needed to be linked here, so:

Source: http://xdaforums.com/showpost.php?p=64754613&postcount=846.

And I 100% agree with this post!!!
[Galaxy Note5 Original Android Development] Rx8Driver:
Which rom is that?
[Galaxy Note5 Original Android Development] kenpaci:
Venom n9208 dual+ skyhigh v35:D
[Galaxy Note5 Original Android Development] UpInTheAir:
LOL, I just don't know what to say but mate. You been a great supporter and contributor here. Thank you again

I need to correct myself a bit. I have removed mode and enforced_mode from tunables because there is no need for them for 99% of users and also because will cause apply-discard bug (for mode).

If those are enabled, will just screw CPU scaling and migration up and also single_cluster0_min_freq needs to be set. I have set up the "turbo mode" for that ;) This affects both A57 & A53.

The mode has something to do with switching between big.LTTLE cores as primary. Mode can be dynamic with enforced_mode (changing value between 0 and 1) and even after disabling enforced_mode, mode won't always return to 0 (on one of the cores). Forcing it back to 0 does not force original core behaviour to enter L_I for either A57 or A53. So, I've left it as it is. You just need to reboot after disable, otherwise A53 aggressive scaling to 1500 MHz will occur.

I think I posted this before (somewhere), but I actually made toggle for both A57 & A53 enforced_mode and mode parameters. So I could easily experiment and observe behaviour with different combinations. I even manually checked before and after all A57/A53 sysfs tunables using root explorer, comparing before and after etc.

So that's why it is what it is (for the moment anyway) ;)
[Galaxy Note5 Original Android Development] jrshabs:
will this get me more of my note 5?? what benefits will i get from this two? thanks in advance
[Galaxy Note5 Original Android Development] D47x:
Gave me a bit more SOT (>30min) but slaps in an extra 10000 points on antutu benchmark

Much appreciated dev
[Galaxy Note5 Original Android Development] dinik:
goz the same problem on my 920cd venom rom
[Galaxy Note5 Original Android Development] jrshabs:
does it overheat with long uses?
[Galaxy Note5 Original Android Development] D47x:
I'm playing minecraft story mode atm, heavy 3D game, phone gets warm but not enough to divert my attention
[Galaxy Note5 Original Android Development] CanMan1:
Effectively Disable IPv6 on Android

I figured out how to effectively disable IPv6 with an init.d script (named: 00disable_ipv6):

#!/system/bin/sh
chmod 644 /sys/module/ipv6/parameters/disable
echo -n 1 > /sys/module/ipv6/parameters/disable
chmod 444 /sys/module/ipv6/parameters/disable
chmod 644 /sys/module/ipv6/parameters/autoconf
echo -n 0 > /sys/module/ipv6/parameters/autoconf
chmod 444 /sys/module/ipv6/parameters/autoconf
chmod 644 /sys/module/ipv6/parameters/disable_ipv6
echo -n 1 > /sys/module/ipv6/parameters/disable_ipv6
chmod 444 /sys/module/ipv6/parameters/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/default/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/wlan0/autoconf
echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6

I confirmed that it still works after toggling Wi-Fi, using data, and using a VPN. Note that the /proc/sys/net/ipv6/conf/wlan0/disable_ipv6 will reset to 0 (IPv6 enabled on wlan0) after a network change, but disabling autoconfig and accept_ra prevents IPv6 addresses from being assigned (IIRC). I checked for IPv6 availability on the following websites:

http://test-ipv6.com

https://diafygi.github.io/webrtc-ips/

Oddly, my public IPv4 address doesn't show up in the WebRTC test while using data (4G). If you think you know why, then please share a possible fix for the WebRTC Wi-Fi IPv4 public address leak. Or better yet, a complete WebRTC disabler.

Turning IPv6 back on requires resetting the values, deleting the script, then rebooting. If you use a VPN, you may have to connect then reconnect to it (resets tun0) to get IPv6 functionality back. I assume a reboot is also required after running the disable_ipv6 script from terminal. After IPv6 is disabled, you may have to forget then reconnect to your Wi-Fi or switch hotspots to regain connectivity.

I hope you can implement this into a Synapse toggle after cleaning up and possibly improving the code. For example, I think this cleaner script could still work (confirmed, see edit):

#!/system/bin/sh
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra
echo 0 > /proc/sys/net/ipv6/conf/wlan0/autoconf
echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra

Do you think this deserves a dedicated thread? I haven't been able to find an effective way to disable IPv6 on android by Googling.

Edit: Second script works on the test sites. Added instructions for enabling and disabling IPv6 with the script.
[Galaxy Note5 Original Android Development] Abu-khulzat:
Hi, I used to use this kernel back in September and remember that I had an issue with other party hearing me on incoming calls. I had N920CD then. I sold that phone and recently bought another one, also 920CD.

Today I rooted it and flashed this kernel on fresh stock system. No other modifications.

On incoming calls the other party doesn't hear me. What could be wrong? I searched the thread, but couldn't find a clue.

---------- Post added at 11:52 PM ---------- Previous post was at 10:58 PM ----------

Right after an incoming call I saved some logs. Here they are if they have some value:

https://www.dropbox.com/sh/1m6n3bwfk8penpt/AAB1wEc6cUAgqZRT4bjHdvC1a?dl=0
[Galaxy Note5 Original Android Development] guaneet:
Can you make sure you have equalizer enabled. This was stated as a fix a while back.
[Galaxy Note5 Original Android Development] UpInTheAir:
If you wish to post a confirmed working enable script, I will make a Synapse toggle to enable/disable. Also please state if reboot will be needed etc. The aim would be without the nedd to reboot.

As I said before, I have no way to effectively test IPv6 (edit: just sysfs changes)

Also, is you can please post the link to the original script author.

Thanks

As post below. If it's disabled, then either Synapse data was not wiped before flash, you toggled it off, or restored an old profile.
[Galaxy Note5 Original Android Development] UpInTheAir:
v3.6 released

v3.6 release for:

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

Check out the gitHub Change-log (link 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

DO NOT restore profiles from older versions or other kernels !

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

BUGS:

Disabling "Turbo Mode" will screw up frequency scaling. So if you have disabled

any time

, you need to REBOOT !!

Changing Interactive governor profiles when Interactive

is not used

, will result in Synapse display errors. Nothing to worry, no need to change the profile if Interactive it not used !

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] aclan:
9200 flashed successfully with v3.6, thanks for your work.
[Galaxy Note5 Original Android Development] muffinsmuffy:
Thank you soooo much man thank yopoou
[Galaxy Note5 Original Android Development] Abu-khulzat:
Just checked the equalizer, it is on. Bit the person in the other side doesn't hear me anyway. (((.

And this issue is kind of intermittent. Sometimes they hear, sometimes not, incoming and outgoing calls as well.

By the way, I didn't restore any profile. I flashed the kernel on a new fresh system.
[Galaxy Note5 Original Android Development] UpInTheAir:
Flash stock N920CXXU1AOK7 such as I test with
[Galaxy Note5 Original Android Development] drathian1:
I've noticed that I get the "boot settings cancelled" message even if I wait 10+ minutes before opening synapse after rebooting. Has this ever happened to you?
[Galaxy Note5 Original Android Development] namfat:
Still some! But try to install step by step as instruction in OP.
[Galaxy Note5 Original Android Development] lightdelegate:
Yes I did.

And tried a clean install again but same. Yesterday eve i had a long phone call...

After 5 or 6 times rebooting I just couldn't handle it anymore...

Will try again the next ver.

Thanks alot!
[Galaxy Note5 Original Android Development] rabbitweed:
sm-n9208 support in near future?

SM-N9208 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note5 Original Android Development] UpInTheAir:
1. Force Close Synapse and clear data

2. Open Synapse and tap "understood"

3. Make

any small change (that should be stable) and apply

4. Reboot and wait for 2 mins and also "synapse boot completed"

5. You should be good to go ;)

Not in the near future because I'm away all September
[Galaxy Note5 Original Android Development] charlie.s:
I've been using it for over a day and have not had a single reboot. To be fair, I don't use the phone function all that much, so I don't know if this is significant or not.
[Galaxy Note5 Original Android Development] Derpling:
Is their a way to disable TW DVFS without xposed? the thing throttles the phone after couple of minutes of heavy gaming.
[Galaxy Note5 Original Android Development] sshafranko:
Try this:

Root Explorer or Es or whatever....

Sys/devices/14ac0000.mali

Long click dvfs, dvfsmin lock, and dvfsmax lock

Tick Permissions and uncheck all check marks, so no permissions....Reboot.

Let me know if it works i havent tried it cause i had to go back to stock for this week.
[Galaxy Note5 Original Android Development] Derpling:
That was the first thing i tried, but it applies the settings then resets them always, i tried to delete the whole folder, root permission given, but it always keep bringing it back.
[Galaxy Note5 Original Android Development] sshafranko:
I wouldnt delete the folder there are other things in there u dont wanna loose....im sry i cant mess w it now cause im not rooted and no lap top im on vacation till sun...why dont you flash jthrashers deodex rom and use xposed?
[Galaxy Note5 Original Android Development] Derpling:
I want but it for Sprint variant if i'm not mistaken, i've got N920C.
[Galaxy Note5 Original Android Development] sshafranko:
Ohh ok...its for tmo variant
[Galaxy Note5 Original Android Development] Jmakhdoom:
Will this work with dual sim SM-920C ?
[Galaxy Note5 Original Android Development] drathian1:
That worked great, thank you.
[Galaxy Note5 Original Android Development] UpInTheAir:
It can be done at source, but only for GPU. There is no HardLimit driver like Yank.lu wrote for Qualcomm devices

that can make sysfs toggle.
[Galaxy Note5 Original Android Development] Derpling:
Is there anything that can be done, outside of settings govenors to performance to decrease it's throttling?
[Galaxy Note5 Original Android Development] UpInTheAir:
De-odex your ROM and try wanam Xposed and DVFS disabled. I "think" he has it working for 5.0 + for de-odex only. That would disable TW DVFS, but NOT behaviour of normal thermal throttling. Controls for this are a possibility later on where user can set GPU freq or CPU temp limits for each thermal throttling step.
[Galaxy Note5 Original Android Development] Derpling:
Thanks for help! how can i deodex the rom?
[Galaxy Note5 Original Android Development] tellez 888:
Any fix for private mode?
[Galaxy Note5 Original Android Development] namfat:
No. Note 5 2 sim is N9208 or N9200, not N920C my friends.

Sent from my SM-N920C
[Galaxy Note5 Original Android Development] CanMan1:
Disable IPv6 on Android

Thread: http://xdaforums.com/general/networking/guide-disable-ipv6-android-t3298659

Background

After trying a lot of non functional methods for disabling IPv6, then using a working but sometimes high battery drain one, I decided to read the Linux kernel documentation and create my own method.

Functionlity

No reboot needed. Modifications persist across network changes, but reset on boot. Thus, an init.d script is used. Notes: I haven't tested IPv6 over data as my provider doesn't seem to support it, but rmnet0/disable_ipv6 didn't reset when switching to data from Wi-Fi . wlan0/disable_ipv6 resets on reconnect, but there should be no IPv6 addresses on the interface.

Instructions (scripts at end of post)

Disable IPv6

Add disable script to init.d

Run disable script

Optional? (may interfere with Afwall+ if IPv6 support is enabled)

Maybe rename/backup ip6tables when disabling IPv6 since it won't be used, then rename/restore it when enabling IPv6.

Enable IPv6

Delete init.d script

Run enable script

Wait for IPv6 addresses to be added (less than 30s)

Explanation of Script Commands

https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt

Testing IPv6

http://test-ipv6.com

https://diafygi.github.io/webrtc-ips/ (IPv6 addresses may still show until reconnect or reboot. Will try to fix if someone reports this issue)

References

If you want to give credit for the method, then please mention this post and/or my username. I'll probably create a new thread for this, so update you with the link when it happens. If you know what section of the forum would get the most views and participants, please send me a link.

I can try to find and link every source of information used, but there would be dozens.

Side Notes

Not even the paid play store app Disable IPv6 Pro works as simply or effectively. That app also increases battery drain like the free network change method I used before, whereas this method should have no effect on battery. So, AFAIK, it's the best method available for our android device. Perhaps someone should make a FOSS app for this.

VPN/Privacy Notes

If using a VPN, I recommend using Firefox with WebRTC disabled to prevent your public IP from leaking. Alternatively, you can block all connections that don't go through your VPN using iptables.

Scripts

Disable IPv6 (name: 00disable_ipv6_v5)

#!/system/bin/sh

# Disable IPv6

echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6

Enable IPv6 (name: 00disable_ipv6_v5_reset)

#!/system/bin/sh

# Enable IPv6

echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra

echo 0 > /proc/sys/net/ipv6/conf/all/disable_ipv6
[Galaxy Note5 Original Android Development] UpInTheAir:
I'll re-read your post tomorrow. Great someone being proactive here. I'll take a look tomorrow once I've finished with some other "stuff". Won't be a problem to include in Synapse.
[Galaxy Note5 Original Android Development] Abu-khulzat:
Hi!

Just factory reseted my phone and flashed OK7 firmware (Baseband seems to be OK5). Without installing anything, I flashed 3.6 version of the kernel. After that installed synapse and supersu. Did everything as described in the OP and tried to receive and make a call. The other party does hear me now, but as soon as I turn the speaker phone on, the other party stops hearing me for about 10 secs. This happens for incoming and outgoing calls. Sometimes they don't hear me from the beginning. There seems to be some delay for the mic to get on. But if it turns on in the beginning of the call normally, turning on the speaker phone interrupts the mic for some time.

Tried to disable equalizer in the Synapse. My voice disappears the same way when I turn the speaker on, but this time it doesn't reappear. Turning on the equalizer brings everything to the state I described in the beginning. My sound reappears after about 10 secs.

This seems to be affecting only N920CD device, since I had it 3 months ago, and I observed there something similar with this kernel.
[Galaxy Note5 Original Android Development] Ahmed Wael:
iam using this great kernel v3.6 on my stock room but i want change my rom . what is the best rom work with this kernel better should i use VANOM OR DR.KETAN rom which one more bettary save and ram save and stability ...... thank you
[Galaxy Note5 Original Android Development] santiargy:
Anyone had issues updating FW to OK7 or OL1? I have been getting errors. I'm on version v3.0, OJ3
[Galaxy Note5 Original Android Development] Manson79:
Hi,

A kernel works great on any rom and a rom works great with any kernel... , again, keep in in mind that battery life is mainly on the user side (and in your case about RAM too), install a bunch of apps with obviously a few running services and you'll see your battery life / RAM usage decreased...

All this stuff is mainly about YOUR settings... Synchro for example can eat your battery, bad signal reception can eat your battery... Chrome can eat your RAM... You see it is nothing especially related to a rom or a kernel.

Yes you can tweak the kernel to minimize battery comsuption but only at some point, after that it's all on the user side

:)
[Galaxy Note5 Original Android Development] Ahmed Wael:
thank you for reply i will flash VANOM rom soon and i will do settings in cynapse to save battery and make a ram free
[Galaxy Note5 Original Android Development] UpInTheAir:
1. Have you tested without Synapse? If not, wipe Synapse data > reboot > test

2. Try older kernel release? Wipe Synapse data > Flash v3.0 (older ramdisk base and dt.img) > reboot. Test without Synapse first.