yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Original Android Development] UpInTheAir:
Not really, just a dirty work-around. Read change-logs . It works on my N920C but some users continue to report "issues" with their own induced problems or failing to give full information and device setup. I've requested only fully stock ROM and no tweaks or Xposed etc so issues can be identified.

This statement means absolutely nothing in development. How does this help? Please read the last few pages and my posts. Also read again post #3. I have on more than one occasion detailed what is required. Thanks.
[Galaxy Note5 Original Android Development] UpInTheAir:
v1.7b released

v1.7b update for SM-N920-C / CD / I device variants

Check out the change-log in Post #2.

Tested by UpInTheAir with

:

SM-N920-C 32GB device

stock N920CXXU1AOH4 firmware

no Xposed etc

no tweaks etc

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

Please CLEAR SYNAPSE DATA

before flash

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

Bugs:

GPU: with MIN frequency (default) set at 266 MHz - won't scale up in 2D operations. Set it to 100 MHz (if your device is stable at that).

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] LiL_Assassin:
[/COLOR]Cheers :). I really appreciate your work, I am. So glad the reboot bug is gone. Now I understand why you need a clean base for testing. I tried a custom rom and it rebooted. But I'm not fussed. I really like stock atm.
[Galaxy Note5 Original Android Development] UpInTheAir:
Not "gone" , work-around it ;)

I'm going to include a toggle to enable/disable Power Aware Scheduling in next release.

This was introduced in v1.0 and is still currently enabled by default (increases power efficiency) at the expense of performance.

User choice is always nice :)
[Galaxy Note5 Original Android Development] asmen5:
Any chance to N9208?
[Galaxy Note5 Original Android Development] UpInTheAir:
Not sure when. When things slow down (and they are). Probably heading away next week for quite a while. So wish to get my own device where I want it to be, before (providing I have time) taking on additional workload
[Galaxy Note5 Original Android Development] eousphoros:
So i casually read thru your thread, changelog, and git commit but other then the tima stuff nothing screamed out to me as far as potential work arounds for reboots

Mine has remained stable but the cat in me is curious what ended up being your fix. Sorry if i missed it.
[Galaxy Note5 Original Android Development] UpInTheAir:
Yeah, it's a dirty work-around for now. I just want to use the device and limited time before heading away again :)

Changelog:

[v1.5b] - 6th October 2015

ramdisk

:

Synapse: CORTEX: add CortexBrain to control screen on/off functions. Enabling this FIXES in-call reboot bug (actually a solution - not a "fix"). Thanks to Dorimanx & halaszk88 for the orignial scripts which I chopped to pieces into my SM-N915S kernel :).

/sbin: add CortexBrain script

/sbin/SkyHigh.sh: start CortexBrain on boot

I found that if the SCSI deep sleep patch is removed, then the device refuses to sleep, BUT, calls do not reboot.............. So holding a wake-lock prevents in-call reboot issue whilst screen is off. It never happened whilst the screen was on.

I modified the cortexbrain script checks both screen off/on state and device in-call. If those two conditons are met, then a wake-lock is forced, and auto remove the wake-lock if either condition is not met.

Synapse description:

Edit: forgot to mention I threw watchdog control in cortexbrain, not too sure if ti hurts disabling it whilst screen off and in-call.
[Galaxy Note5 Original Android Development] eousphoros:
Wow, that is a crazy bug and creative fix. I wonder why i haven't hit that particular panic.

Thank you for sharing

Also, in reply to your comment about samsung, gpl, and their latest kernel source. I noticed it as well. Its really obvious in their dtb image stuff (dtsi) that this is not the source they used to build the production kernels.
[Galaxy Note5 Original Android Development] UpInTheAir:
It has to be combination of things, probably including your Linux base to start with (before merging Sammy source), defconfig, TIMA, maybe even ramdisk...........

But I blame it souly on the Sammy BS firmware and SCSI and the root cause.

100% stock complied kernel and stock ramdisk = no deep sleep

stock compile + SCSI patch + stock ramdisk = deep sleep + in-call reboot

Edit: I tried to use the SEA dtbs and compile custom dtimg. Would not boot. WTF. my device it SEA !! had to use EURO !! so yes, you are right :)

What a steaming load they've given us ?!
[Galaxy Note5 Original Android Development] idle0095:
What kernel do I use for the N920i? How do I install? Just flash via philz recovery? Does this fix the call issue with reboots during calls?
[Galaxy Note5 Original Android Development] garyd9:
Thats odd. Are you using the patch in sd.c shown here: http://git.kernel.org/cgit/linux/ke...c?id=2eefd57b97609949ae40952da2dea338e7d9a125

BTW, on a stock kernel (repacked ramdisk) with writes to the sys tree to prevent caching on the RO block devices (which is what the above linked patch is supposed to do), it appears that my device wakelocks on "ProximitySensorManager" while I'm on a phone call with the screen turned off (and the device sitting on my desk.)

I don't think the device is SUPPOSED to be going into deep sleep at all while in a call. It might be worthwhile to track down a completely stock configuration (stock kernel, recovery, and firmware) to see if that device goes into suspend while on a call.
[Galaxy Note5 Original Android Development] idle0095:
So every time I boot up it says that synapse has cancelled boot. Also when i load the app it just says understood and nothing else. I had a random reboot since flashing this kernal. What could be wrong.
[Galaxy Note5 Original Android Development] UpInTheAir:
Yes. That's in my source and the patch I was referring to. I wasn't blaming SCSI for the wake lock, but that's where it all started.

I flashed back stock and factory reset before and after, but the deviced still refuse to deep sleep. I haven't tested lately or on OI1 firmware though.

What did you use to capture the wake lock? Wake lock detector? Or to PC?

Not sure it's really anything to do with the proximity sensor though. It will reboot in-call if the phone is just placed down on desk with no flip cover or having been up to the ear. So the sensor shouldn't even need to give wake lock as it's not needed. But, they could be trying to hook into that during call so it didn't panic. I forget the log a captured on it though, I'll try dig it up, but I've just moved on for a bit after work-around and play with a few features :)

I never implied (or meant to) that it's SUPPOSED to deep sleep whilst in call, that's why I gave it a wake-lock - and it works ;)

I just don't have much more time to devote to it for quite a while (upcoming work commitments). Just v1.8 beta testing right now, and release in a day or so.

You didn't follow inductions I laid out in Post #2 and 3. Use 100% stock ROM and no tweaks or xposed etc. Wipe Synapse data and then flash kernel. Wait 2 minutes after boot then run Synapse. Tap understood and apply if needed. Make ANY small change and apply. Test with SkyHigh DEFAULTS by reset globally (top right hand corner) or revert your change. Should be good to go.

Please read what's required and post as much detail of your device setup as possible. We have no idea what that is and what changes you made with Synapse.

I won't bother wasting my time if users don't want to help themselves. ;)
[Galaxy Note5 Original Android Development] idle0095:
I thought I followed instructions to the t. Yes I had xposed modules active. So what do I do now. Re flash the kernal and disable xposed models. Then wait the 2 mins and then after that I can enable the xposed modules?
[Galaxy Note5 Original Android Development] UpInTheAir:
I only endorse a factory reset fully official firmware (with custom recovery) to test on. Anything else is useless to me and development right now.

The above post might be useful to you, but unless you have done what I had required, I don't have the time to be interested either.

Today, I will amend the instructions (for those that choose to read/follow) to make the thread requirements clearer.
[Galaxy Note5 Original Android Development] idle0095:
I'm using stock from haven't touched that. I flashed your kernel and followed the instructions. When I run your app I was only getting the warning saying understood.
[Galaxy Note5 Original Android Development] garyd9:
I think it's just a coincidence that there's a bug with the scsi caching that blocked suspend and that the blocked suspend prevents the crash. I can't believe that Samsung had that bug with the SGS6 and left it in there for the Note5/edge+. That's just so damn typical of them...

BetterBatteryStats with the system app portion installed.

I wish I still had my nexus 6 available to compare with, but I believe that it also stayed awake during phone calls (even when the screen is off and the phone is laying on a desk.) What I'd like to know is: what mechanism does the Nexus6 use to stay awake during calls (or am I completely wrong and the device goes go into suspend while off hook.)

Oh, okay. I misunderstood.

Take care

Gary
[Galaxy Note5 Original Android Development] UpInTheAir:
Yes I know that, I think you misunderstood ;) The SCSI bug was where the BS started, and the Sammy BS hasn't stopped since, with incomplete source code etc
[Galaxy Note5 Original Android Development] UpInTheAir:
For those disbelievers and [MENTION=5116431]Manh_IT[/MENTION] ,

Last nights test: flashed an v1.8b test version and made two test calls:

In-coming ~30 minutes = no reboot

Out-going ~30 minutes = no reboot

Charged the device to 100% and put to sleep after checking a few things.

This should be no different from v1.7b, but thought I would post anyway.

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.

Attached is the "evidence" ;)

Edit: attached battery usage screen-shot (note that it has top off the charge back to 100% whilst connected to PC and transfer images) - this proves no reboot last night.

Cheers,

UITA
[Galaxy Note5 Original Android Development] DLUX24:
Awesome, if you need anymore testers for your "T" version, let me know, I'd like to test:D
[Galaxy Note5 Original Android Development] UpInTheAir:
v1.8b released

v1.8b update for SM-N920-C / CD / I 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.

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

Please CLEAR SYNAPSE DATA

before flash

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

Bugs:

GPU: with MIN frequency (default) set at 266 MHz - won't scale up in 2D operations. Set it to 100 MHz (if your device is stable at that). I need more testing on stock to assess the behaviour

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] liqn7:
Thanks for all your great work :)

You probably don't remember me but I was also a huge fan of your work for the GTab 7.7 as well (oh the memories) :P .

Looking to get a Note 5 very soon (Prices still pretty high in Australia) to join the fun.
[Galaxy Note5 Original Android Development] LiL_Assassin:
off topic i know, can anyone give me a link to download SM-N920I Stock firmware? i bricked my device accidently wit bloody faplock somehow turning it self on and flashing custom recovery
[Galaxy Note5 Original Android Development] UpInTheAir:
A familiar name

:)

sammobile.com or samsung-updates.com

1.5+ GB.

Good luck !
[Galaxy Note5 Original Android Development] LiL_Assassin:
thanks very much for that! quick question before it downloads. it doesnt wipe data partition using Odin does it? i have EVERYTHING backed up, including my EFS folder on that. if this messes up my EFS folder somehow i can just restore, but not if data is gone :/
[Galaxy Note5 Original Android Development] Abu-khulzat:
Hi!

Is it possible to implement f2fs support in your kernel?
[Galaxy Note5 Original Android Development] keaheng:
random reboot while device was being screen off.. default kernel setting N920C

https://www.dropbox.com/s/zclkhsrr18mbqdu/last_kmsg-2015-10-13.23.54.53.txt?dl=0hope this help
[Galaxy Note5 Original Android Development] UpInTheAir:
Can never be 100% sure, but Samsung don't seem to be releasing wipe firmware for a long time.

Yes. But not right now or anytime soon.

Post #3
[Galaxy Note5 Original Android Development] wish2:
thank u for this great work

but i notice that there is no speaker boost in synapse only ear piece speaker ???

will you add it later or speaker cannot be boosted ???
[Galaxy Note5 Original Android Development] UpInTheAir:
Only if AndreiLux patches the source. To be truthful, I don't have much of an idea on it.
[Galaxy Note5 Original Android Development] UpInTheAir:
v1.0 released for SM-N920-T

v1.0 initial release for SM-N920-T device

NOT TESTED

!! : You will have to tell me ;)

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

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] wish2:
is there any fix for wifi passowrd forget ? and also titanium backup pro not working on this root
[Galaxy Note5 Original Android Development] bill340:
Both work without problems here...
[Galaxy Note5 Original Android Development] UpInTheAir:
WIFI fix is there. All future passwords will stick from now on reboot.

I just backup XDA app > uninstall > restore with TB pro = no problem

I just entered my WIFI password and reboot = no problem.
[Galaxy Note5 Original Android Development] wish2:
this message appear when i open TB PRO
[Galaxy Note5 Original Android Development] bill340:
Did you install SuperSU ?
[Galaxy Note5 Original Android Development] bimori:
tested tmobile version. All seems well.
[Galaxy Note5 Original Android Development] wish2:
yes
[Galaxy Note5 Original Android Development] bill340:
Strange... it works here without any problem...
[Galaxy Note5 Original Android Development] wish2:
can you give me the tb pro apk may be my apk is old version ?
[Galaxy Note5 Original Android Development] bill340:
Get the latest from playstore...
[Galaxy Note5 Original Android Development] wish2:
it is very expensive :(

and i m not sure if i purchased it if it is will work or still not recognizing the root
[Galaxy Note5 Original Android Development] MCarnage:
Something I've noticed is that on SM-N920T it will be connected to wifi but still randomly connect to 4g then disconnect. I don't have boost mode or wifi smart switch on.

Edit: I was looking at the logcat and I think it's the tmobile my account app so froze it. Initially seems to solve it.

Edit 2: Nope!
[Galaxy Note5 Original Android Development] UpInTheAir:
Please show respect to the Devs and XDA (and SkyHigh kernel thread) do not promote such Warez here. Thanks.
[Galaxy Note5 Original Android Development] wish2:
i m sorry upintheair just i requested athing to help me activate all features of your great kernel .. second time i m sorry
[Galaxy Note5 Original Android Development] jpeps3:
5.8.8 version of playstore
[Galaxy Note5 Original Android Development] UpInTheAir:
Yes. Strange. Glad you found a work-around for now. Hope it stays that way :)
[Galaxy Note5 Original Android Development] jpeps3:
Can please make n920t kernel flash able with twrp
[Galaxy Note5 Original Android Development] bash_array:
Got a fatal bootloop on 1.7

Plugged it in for the night. When I woke up it was bootlooped. The the only thing I could do to recover it was a full wipe and restore.

Running T-Mobile stock COI5 with no xposed mods or any other changes
[Galaxy Note5 Original Android Development] UpInTheAir:
I don't support TMO for the time being, so please do not post in the

International thread

.

From the TMO OP:

When I have free time again to support any other device than my own remains to be seen. TMO thread is CLOSED. Best if you switch to another kernel.

Edit: and BTW, the latest kernel is/was v1.8b
[Galaxy Note5 Original Android Development] UpInTheAir:
IN-CALL REBOOT ISSUE FINALLY FIXED !?

Improved stability. ...

Stay tuned for tomorrow's report on further testing of v1.9 test kernel ;)

CortexBrain = disabled (offline) !! and off charge (USB or A/C)

Incoming:

Call #1 = 47 minutes + no reboot

Outgoing:

Call #1 = 37 minutes + no reboot

Call #2 = 30 minutes + no reboot

Call #3 = 33 minutes + no reboot

Charge to 100% + no reboot.

ALL GOOD !!
[Galaxy Note5 Original Android Development] Abu-khulzat:
I still have problems letting my phone deep sleep on this kernel (ver 1.8b) N920CD. I did a factory reset yesterday, still no deep sleep. If I flash arter97 or spaceX kernels, I get deep sleep.

I don't have xposed or any other modifications. Stock AOH4 rom.
[Galaxy Note5 Original Android Development] meysam Z:
thanks for new version :D

could U add better battery saver like arter97 kernel (no Disrespect) on Ur next develop ?

Note5 N920CD
[Galaxy Note5 Original Android Development] UpInTheAir:
v1.9 released

v1.9 update for SM-N920-C / CD / I 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 !!

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

Please CLEAR SYNAPSE DATA

before flash

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

[MENTION=2346758]eousphoros[/MENTION]

I'm a little embarrassed to say I've found the “simple” solution to the in-call reboot. Please take a look at my v1.9 source change and/or change-log................ I did try it back in late August, as I didn't realise then that there was any issue, so went with Google (as source readme recommends) as it's always been most reliable > until now...........

You probably do know the trouble and extensive time I went to in trying to find proper solutions, most of which was never released or documented in source as it was private test only. I created sysfs configurable controls to adjust wakelock timeouts for proximity sensor, ported drivers, tried and merged different sources and various defconfig. Played with ramdisks, boot.img tools etc. Not to mention the "creative" CortexBrain work-around. So the road wasn't really so “simple”, but relief, phew, all good so far (touch wood) :)

[MENTION=5116431]Manh_IT[/MENTION] , you might wish to reconsider the solution I found and compile your kernels again. I promised I would share the fix with you and [MENTION=4454815]jovy23[/MENTION] . Up to you mate ;)

Have fun :)

Cheers

UITA
[Galaxy Note5 Original Android Development] mastergrillo:
I know you stopped building for n920t but how about one last one for old times sake ?
[Galaxy Note5 Original Android Development] UpInTheAir:
I'm waiting for Moderator to unlock the thread ;)
[Galaxy Note5 Original Android Development] garyd9:
Not much changed... linaro, disabling ext2/3 and JBD or clearing the compiler cache? I'm curious too - which was the magic bullet?

I'd be wary if a compiler change fixed a bug. That would usually indicate that its only masking a larger problem behind re-ordered instructions. (... but not completely surprised. I've seen compilers spit out bad code before.)
[Galaxy Note5 Original Android Development] UpInTheAir:
read the linaro notes (open the commit)............... and you would have also read the change-log? ;)

Edit: The source has specific build instructions for Linaro and afterwards I checked with other 7420 devs source and they also use it
[Galaxy Note5 Original Android Development] garyd9:
That's really interesting. Like I said, I'm not completely surprised. I haven't spent the time to pull the samsung source to recompile it myself. The longer I stay away from Sammy's source, the longer I'll be able to enjoy the phone without getting REALLY angry at Samsung. Again.

I'd still be paranoid about it, though. Makes me want to pull the source myself and try to find where GCC has gone wrong...

(Oh, and no - I didn't read the change log. I just jumped into the commit log. I speak 'C' much better than English.)
[Galaxy Note5 Original Android Development] UpInTheAir:
Other creditable devs such as Andrei, arter, wanam all use Linaro in their 7420 source for compiling. I could pull their source and compile and boot using Google GCC, but all would have in-call panic. I'm fairly certain if I'd compiled with Linaro, wouldn't have that issue....

Maybe Google updated the TC, I haven't checked, and no time to delve into something I'm surely lacking available time.

But this kernel is out of beta, at last :)
[Galaxy Note5 Original Android Development] asmen5:
Using v1. 9 on N9208 sva rom, look great... Thanks
[Galaxy Note5 Original Android Development] hshah:
I'm using a N920CD and it just rebooted with the latest v1.9. I was wirelessly charging at the time and this thread's notification email had just come in.
[Galaxy Note5 Original Android Development] mastergrillo:
So testing 1.9 on my n920t during a call and it's good thanks for you hard work

Just made another call for 3min and still going usually it would reboot a min after the screen would turn off [emoji1] [emoji1] [emoji1] [emoji1] happy camper
[Galaxy Note5 Original Android Development] Nurik225:
Tested on the latest S\W for N920C. Works perfect. But sometimes i see reboots. Any suggestions?
[Galaxy Note5 Original Android Development] UpInTheAir:
You'll need to give full details as per Post #3. I don't have any issues on SM-N920C as per my device and setup stated in v1.9 release post. I can only assume you have the latest version and followed instructions in Post #2 and Post #3

Lets hope it stay that way :) Please keep TMO to the TMO thread. The Mod has kindly re-opened it.

You'll need to give full details as per Post #3. I don't have a wireless charger to test (or your device)

I haven't released any official support for your device variant. Up to user to try, all well and good if things work as hoped, but I'm not interested in any bug reports. I just don't have the time to support any other variants right now.
[Galaxy Note5 Original Android Development] asmen5:
N9208 using skyhigh V1.9
[Galaxy Note5 Original Android Development] UpInTheAir:
I see you have dual network connection in status bar. Do both SIM work?
[Galaxy Note5 Original Android Development] asmen5:
Yes Dual SIM work like a charm....:o
[Galaxy Note5 Original Android Development] daffie:
Very good news indeed...may try this myself on my N9208.
[Galaxy Note5 Original Android Development] UpInTheAir:
Which kernel did you flash, and please report if any drivers are/aren't working, BT, WIFI, GPS, audio, charging, sensors etc. I do think the C and I kernels can be merged. There is only one entry in the ramdisk default.prop that's extra, so I wouldn't think much difference.

I don't have the time to look at anything, but might be useful to others with your variant. Just make sure you please post your entire device setup and firmware versions when doing so and I can point them to your detailed post (if stable).

Thanks
[Galaxy Note5 Original Android Development] asmen5:
N9208 (duos) using skyhigh kernel v1.9 C variant, dirty flash on xiaolu kernel+SVA Rom.. Till now only NFC payment not work..
[Galaxy Note5 Original Android Development] UpInTheAir:
Isn't that "normal" on rooted devices. I don't use it, only what I've read........... Although NFC turns on, will result in payment failure, so Users will just have to use stock if they wish to use Samsung Pay, Google Wallet so such payment type services. If this is the case, then not really the fault of the kernel itself.