yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note5] CanMan1:
Press and hold the power and volume down keys until the phone reboots. Edit: You might need to hold the home button too. It's been awhile since I've done this
[T-Mobile Samsung Galaxy Note5] andronikal659:
Tried it. It wants to boot then get stuck in download mode. I tried odin to flash root kernel 1.0 and it's back to life. Thanks
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Lol looks like i was too late with help lol
[T-Mobile Samsung Galaxy Note5] andronikal659:
All good. :) is there a reason it got stuck in download mode though? I really want to try your battery profile. I tried lowering a57 from 700-1800 , a53 200-1400 and it either stutter my phone or reboots it. I cleared all data in synapse before loading your profile.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
What your asv like mate and what version sky high are you using

99% of reboots is because asv might be too low for my voltages
[T-Mobile Samsung Galaxy Note5] andronikal659:
My asv: big:5, LITTLE:7, INT:7, MIF:7, G3D:8, ISP:7

Weirdly enough, I seem to get good battery now... Last night it was at 97% to 96% after 6 hours when I was sleeping. I will need to see my SOT later though
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Yep you asv is lower then mine and can't handle my low voltages that why you rebooted might wanna check your voltages first write them down or screen shoot it and then apply those same voltages when you wanna use any profile
[T-Mobile Samsung Galaxy Note5] andronikal659:
Ahh ok. I don't want to play with the voltage or gpu yet. Gonna try just the a57 / a53 and battery profile for now
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Ok no problem ill customize one for ya
[T-Mobile Samsung Galaxy Note5] andronikal659:
Cool. Thanks a lot man. So if I understand correctly the asv determines how low the voltage can go? It's not a trial and error where you lower the setting bit by bit too see if it's stable?
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Normally undervolting causes performance issue from what I've experienced but saves battery as your asv is lower and mine is higher its the same as undervolting while it doesn't cause any damage at all i just like things to work the way they were intended

Undervolting is trial and error but its also pointless the amount of power saved isn't noticeable and also the unexpected bugs are really annoying plus side a little less heat but thermals will take care of that for you so nothing to worry about there

So here what we are going to do is remove voltages using canman method and you can keep stock voltages that way we are sure its stable
[T-Mobile Samsung Galaxy Note5] andronikal659:
Nice, amazing man. Thanks for taking the time to explain and the time to make a good battery profile.
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
I have disabled xposed framework and left the same profile as described earlier. I haven't experienced any reboots so far today. [emoji1]

Later, I'll enable xposed and one module at a time until it reboots, then I'll send a kernel log....I'm not sure what to look for in it though.
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
https://www.dropbox.com/s/lx8c9w57nwrai7p/dmesg-2016-03-26.14.35.36.txt?dl=0

Just rebooted after waking device.
[T-Mobile Samsung Galaxy Note5] CanMan1:
If you hold those buttons after it shuts off, then it will go back to download mode. You can boot normally by letting go, or press volume up instead of down after it shuts off to go in to recovery.

True for general usage (most people), but for heavy usage (Eg gaming), I will guesstimate a 10%+ battery improvement.

So for most people, I don't think it's worth the effort.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Kernel panic mate seems like you have the call bug not sure how thats even possible also can i ask did you install any busy box or the one that came with the skyhigh v2.7

Ext4 fs seems like a recovery issue just guessing here

can you try reflash recovery twrp latest for your device
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
We are using Note5 twrp which is linked in the OP. Our own twrp recovery wasnt booting with MM bootloader last time I've tried. We have no Twrp mainteiner for S6 Edge Plus :D
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Not sure but im seeing a kernel panic
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Never happened to me with 14 steps uv, interactive.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Yeah by in the log its a panic not site if its caused bt the recovery or something also seeing a call right before that happened so maybe the in call bug seems to affect him
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
That is interesting. I thought this was unrelated, but may not be, so I'll add:

- Occasionally (not all the time), when my device rebooted it went straight to download mode instead of rebooting system.

- Once, before a reboot, I got some crazy errors in Synapse first and

lost root

....the system stayed on long enough that i could verify with titanium backup that root was not detected. After rebooting, everything was back to normal (root too).

- Sometimes (more often than occasionally) when rebooting, it hangs on the Samsung or Rom bootsplash....hard reset usually boots fine afterwards....if not, another hard reset usually does it.

- Audax 1.2 had a bug where the device wouldn't boot if plugged into a charger. It was fixed in 1.3 for most other users, but persisted on my device. I never chased down the reason.

....a thought....My device is g928c. When MM first came out it was discovered that the OTA for g928f would work for my device. So I flashed the f version firmware to get MM. A few days later g928c firmware was officially published but I didn't see any reason to change. Any possibility of that causing issues? Nobody else had reported problems, so I doubt it.

...might not be a bad idea yo odin the c version firmware though.

Currently I'm back to a stable Interactive profile for the weekend.
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Seems not related with firmware in my opinion. Also flashing C firmware to F requires Pit files etc as I read and some users have tried and flashed. I would reflash the firmware and root again, then kernel as you posted in another thread before. Sometimes prerooted roms cause a complication like you had(me also). Maybe CF root.. No issue for me now with river rom(pre-rooted rom but after first boot: no root) Beta SuperSUv2.68 and skyhigh 2.8.

Interactive is a good choice too :thumbup:
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
With a 7 asv in thinking the lower frequencies are where your problem is...increase the voltages for frequencies below 800 for a57 and 400 for a53 to be the same voltage as the "stock basement" voltage, so say your device is 850mV for 800mhz a57, then make 850 the LOWEST and same value going down to 500mhz and see if problem continues...i think the cpu could be stalling out at freq under stock- or try keeping your min freq yr stock values and see if this persist...if so I'd stay stock min freq and increase volt by 12.5mv until you get stable, then apply that voltage to all frequencies 800 and down before undervolting....make sense? That's two different approaches....

---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------

Edit- awww crap man i didn't realise you were on mm lol actually everything should still hold true, but you got A LOT more going on than simply diagnosing an undervolt stutter smh lol good luck my friend, you'll have to be very scientific in step by step isolating the issue without fudging your test results! Just go step by step, could be rom issue, could be xposed, could be a combination, could be unique to mm and thus i can't even help you without being able to reproduce on LL lol
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Well thank you all for your guidance, it means a lot to me! I'm tied up with family activities for the holiday today, but I'll reread everything again tonight and then start charting the next course.

Stalling out at the bottom frequencies seems logical to me. I have tried reproducing a reboot intentionally, but it appears so random. Sometimes its when device wakes up (although it's not in deep sleep due to cocktailbarservice)...sometimes when using camera....sometimes while just sitting there doing nothing.

I'll have to research how to flash the g928c firmware. I guess my device is no longer a g928c, since i flashed the g928f official firmware. I have the c bootloader saved....need to research the pit requirements first though, thanks for that tip!

I'll keep you all up to date.

Happy Easter everybody! [emoji1]
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Happy Easter, sir! Also your device is still what it is regardless of what firmware you've flashed. Keep that in mind when you're thinking about your pit files and partitions, especially where mmcblk settings are concerned. If you flash the wrong pit (and i variant when you physically have a c variant for instance) the pit mapping is likely different and you might hard brick it so be careful and don't get confused by the ability to flash an international rom, that don't technically change your variant....just to be clear ;) hate to read on Tuesday that you're bricked from flashing an incompatible pit file....
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Lol couldn't figure why he had a panic recovery error now i see lols see logs help but info too like uita stated as much info as possible
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
I think the process that I used to update was to marshmallow was standard and according to the instructions available at the time. I full wiped phone, then in Odin I flashed the g928f tar in this screenshot. :

...the g928c tar is one that I saved when it became available, just incase I ever needed it....but has never been flashed.

Then in Odin, I flashed the recovery in the screenshot below. It's meant for note5 as [MENTION=5364232]Konsstantine34[/MENTION] mentioned, but it's the only recovery available for my device :

Then disconnected from the computer and booted to recovery and flashed a 928 ROM, then Sky High kernel.

My process to flash any new ROM is to full wipe 3 times, flash rom, flash kernel, wipe cache/dalvik, reboot system, wait 10 minutes, setup rom. If I'm updating the same rom, I usually dirty flash unless dev requests clean flash.

Then I restore apps with TB, user apps only and no system data. Then setup synapse - all globally, then tweak whatever.

If all is well, I flash xposed. If still well, I flash dark themed play store and reboot. If play services are working well, I flash dark themed Google Now, Hangouts, Voice, YouTube. If all is still well I install several dark themed signed apps and a dark theme from kdio.

What is the "in call bug"? I didn't see anything useful in Google that I thought applied, and I haven't thought to pay attention to reboots relative to completed calls...I didn't notice a pattern before, but I'll pay attention closer to it.
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
24 hours of Interactive with no problems. I have xposed and all mods applied.

It seems to me the least risky thing to try is [MENTION=5663089]Rx8Driver[/MENTION] 's suggestion to check the bottom frequencies. So, I've restored my ktoonz profile and set bottom frequencies at default. Overclocked to 2400 & 1600. Voltages all default, except I extrapolated voltage increases for oc frequencies. A few small tweaks of other tunables, but mostly defaults. I have closely simulated Turbo mode by setting HMP at 1 & 25.

Here's the profile if anyone's interested. It's been stable for 90 minutes so far. I'll test it all day tomorrow or until it reboots.

If it works, I'll undervolt. If not, I'll consider going back to stock and rebuilding my setup.

Edit: Reboot after 3.5 hours of being good.

Setup:

Device - g928c

Bootloader - 6.0.1 MM g928f

Kernel - Sky High 2.7

ROM - BobCatRom 2.0

Mods - several as indicated in previous posts

Circumstance: I was surfing on Chrome and clicked a link. Link didn't work, device stuttered, popup displayed saying Google Play Services had stopped. Then phone rebooted. It got stuck on bootsplash screen during boot and I had to hard reset. Then device booted normally.

Here's the kernel log

I'll drop max frequencies to default for now and stay on ktoonz.

Edit: When I woke up this morning my phone was stuck at the bootsplash again. I had to unplug the device and hard reset, then it booted normally. All frequencies and voltage were at defaults, so it has to be one of the other tweaks....I think.

This morning's log

Edit: I didn't have time to change anything this morning before work, so I still have default freq and volts, same tweaks, same system setup. There were no problems for 10 hours today. I just got home and started downloading a ROM update, and device got warm and rebooted.

This afternoon's log

What are you guys using to view the log? DroidEdit sometimes can't open the file. ES, html viewer....I can't search for a keyword like "panic"

Edit: Updated ROM and kernel to Bobcat 3.0 and SH 2.8...xposed and all mods as previously posted, except newer versions of dark themed Google Now, Play Store, and YouTube.

I believe my most modified tweak was the HMP thresholds that I had set....so I'm going to isolate that tweak and test it out.

ktoonz - all default except HMP

HMP threshold - min up to A57 = 1

HMP threshold - max down to A53 = 25

That's the only tweak.

Edit: Bingo....its the HMP thresholds. I'll need to go back to Interactive or find a more stable way to simulate turbo mode on ktoonz...damn. FWIW, 1 & 25 make my device fly!
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I wonder if the lag from migrating between clusters so often with hmp at 1 and 25 made the kernel think it was in panic and forced a reboot? It just seems to me that poorly coded apps might jump back and forth so frequently that the kernel is forced into panic?
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
That's possible. I'm only just beginning to learn about these things, so this was definitely an experiment.

With Tinycore app I can monitor both cpu load and frequency on all cores individually, and on Interactive - Turbo, you can really see how the big cluster handles most tasks. I don't know the method that Turbo mode uses to make that happen though. HMP thresholds don't appear to have changed in Synapse.

On Ktoonservative, the only way I could think of to emulate Turbo mode was to manipulate HMP thresholds to "force the use of the big cores over the LITTLE ones for increased ui responsiveness...." When I set 1 and 25, the load animation on Tinycore closely resembled what I saw with Turbo, and I could definitely verify snappy ui responsiveness compared to default HMP. But I don't really understand the details of how it works, so you're probably right.

There must be another mechanism that Turbo mode uses...not much info available online though, that I could find.

As fun as it is learning this stuff and coming so close to achieving what I intended, I'm not convinced 100% that I would have realized a very noticeable battery savings. The ultimate goal was to make a "turbo" mode and come as close to "deep sleep" as possible with edge feeds still displayed.

I think I can run a shell script to manually take individual cores online and offline and use Tasker to control it all...kinda my own custom hotplugging. I think it would work with Interactive. But that is definitely not recommended, and I'm not sure I want to mess with it.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I feel like turbo mode basically just effectively swapped a53 and a57 cores, so instead of everything getting packed into the small cores until load reaches the threshold it pushed the foreground and active tasks (like ui) to the big cores first. I tested my theory on this by watching what happened on the cores when using a combination of turbo and hmp little packing settings and it appeared to me that when turbo was enabled of you also enabled hmp little packing (which is supposed to pack tasks into the smallest core for power efficiency) it seemed that it was instead packing them into the big ones....i could be wrong, UITA would obviously know best what his implementation of hmp little packing ACTUALLY does when turbo is enabled, but it seemed to me that it would only pack processes into the a57 cores (albeit leftmost core lol) when turbo was enabled; this, along with the battery drain i noticed, lead me to believe that the hmp migration was basically being reversed, with the a57's getting the bulk of the active workload.....anyone who can, feel free to correct me of I'm wrong!

---------- Post added at 02:07 AM ---------- Previous post was at 02:07 AM ----------

What did you observe [MENTION=6311359]muffinsmuffy[/MENTION]??
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Ahhhh....now I understand more clearly what you said here !

Edit: I'm sure that if there were a way to apply the same method to ktoonz, UITA would already have it available though...

On Qualcom devices there is a program called mpdecision that needs to be disabled before running:

# echo "0" > /sys/devices/system/cpu/cpu7/online

....which should take cpu7 offline. But if mpdecision is running, the file is immediately overwritten back to 1.

I observe the same behavior, but I don't think exynos uses mpdecision. I'm not sure what to disable to allow my custom hotplug theory to stick, when I set to 0.

"# stop mpdecision" doesn't appear to do anything.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
My thoughts exactly however it's possible to simulate turbo on kt through threshold keeping a57 threshold very low will keep iu in that cluster sampling rate will have to be reduced as well while keeping a53 higher when i get to office ill work on one with smooth performance then he give it a try and use it a base but your thoughts are exactly what i had was working on a project with canman and i studied the behavior of clusters to figure it but your spot on
[T-Mobile Samsung Galaxy Note5] drbveb88:
Hey All.. .

I recently got stuck with a locked S7. Since i got a 2nd s7 free, 2 Vr gears, 2 years netflix i decided to trade my N5 in for a V10. 1, because i have a feeling Samsung is gonna try to lock the N5 up. 2, it was basically like having 2 of the same phones. 3. I NEED Development!! LOL.

I appreciate everyones help, tips and knowledge that contributed to this thread. I hope to see you guys around.

PEACE ✌ [emoji41] [emoji2]
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
That might be where I went wrong...I didn't adjust sample rate at all. I didn't understand how that would affect things, or why I should do that....one of the few tunables that I didn't research much.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Sampling rate and up/down threshold effect performance alllot most people don't realize it but would rather depend on benchmarks and benchmarks never give the full picture as how gov tunables can effect reponse time and battery life iu and even benchmarks themselves can be effected by how well you tweak the gov

While uita tuned it as balance battery/performance my screen rarely goes off so any benefits are negligible so id rather have the cpu tilted to performance rather then battery im always close to a wall socket anyway

---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------

Till we meet again mate

Btw confirmed note 5 will NOT be lockedbut since yoy have an s7 its an upgrade so thumbs up and the v10 is a very decent device man so goooood choice on both of em if it were me i would have made the same choice
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Thank you very much! I hate to put you to the trouble though. I would be more than grateful for a stable base to start from. And also, thankful for all of you that have chimed in. This is a most useful thread for learning, thanks to you all!

I agree. My screen is literally never off (since it's considered On when edge feeds are displayed). I want a tilt to performance, and I'm hoping to achieve better battery (relative to turbo) due to hotplugging cores.

So, while you are working on something stable, I'm testing the profile I had...but with a sample rate of 25000. The frequency latency on core0 and core4 is 100000 (according to /sys/devices/system/cpu/cpu0/cpu_freq/freq_latency)....so i chose 25k only because it divides evenly. (I still don't quite understand how it all ties together, so it's a guess).
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
https://drive.google.com/file/d/0B8Ps-jVB8IblN19QTm5aZHlpNXM/view?usp=docslist_api

This one i made a while ago but when applied still seems effective my thermals are really low i don't like hot devices also check your voltages just to be sure you won't have a any problems before you apply have the 2 mins safety then adjusy your voltages back to stock as mine can be too low for your device its just a base that you can go back to if you run into any trouble
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Well, thank you very much for the share man! I used it all day yesterday, and it is certainly stable. I struggled with performance though and it didn't appear to allocate most load to a57, so I tried adjusting a few things. I always end back up at dropping HMP extremely low though...and man, it works! Just isn't stable yet. A few times when entering Synapse, the 'X' is on the screen so I look for the setting that changed, and it does seem to complain about the sampling rate when hmp is so low. You were right about that. I feel like I'm just guessing though when i try to adjust it. All my research speaks to adjusting sampling rate relative to frequency latency...I am having a hard time making the connection to how hmp affects latency.

On another note....I finally decided to figure out what my uv potential actually is, so I took your advice and used Performance governor to test each step for 2+ min. I dropped one cluster at a time. When both A57 and A53 tested fine all the way down to -100, I just left it there to test for the weekend with Interactive. Not bad for ASV 7, huh? [emoji1]

Zero freezes and reboots, good performance, zero Samsung dvfs throttling....it's been 10 hours.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Welcome mate also that x when you open synapse is due to thermal throttle your device was possible warm

Performance struggle might be because of voltages i noticed reducing voltages results in reduced performance as well

Also did you say core threshold if you narrow a57 up threshold and lower them and keep the cores close to each other should be more responsive also hmp make sure that -100 mv is safe if cpu is under load it might cut off from cold if memory serves correct cpu consumption changes with its temp

Side note your correct sampling rate=latency

But you shouldn't forget block cycles also =sampling rate skipped eg block cycle 10 = sampling 4500 skipped 10 times before kicking in = hideous latency = horrid lag

I actually think i forgot to check block cycles on the profile will do that when i get home on an html viewer currently back on stock for tests of my hard mod

---------- Post added at 05:34 PM ---------- Previous post was at 05:19 PM ----------

Another side note if you wanna give more load to a57 keep sampling rate up threshold low on a57 cluster and block cycles maybe 3 (any lower you might have a57 jumping frequencies for no reason and hotplugging cores on for no reason) and frequency skip 7

Then a53 with high up threshold and and high sampling rate and up block cycles and low down block cycles just the opposite of a57 that way you keep lower load on a57 and a53 kicks in under high load along with a57