yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] jaycb420:
80 should be good IMO. Anything beyond 80 I'd start to be concerned. During general use you'll rarely if ever see 80°. The throttle down frequencies are okay. Could you add more perhaps? Example.. Every freq step until 1497. So it won't drop off the performance as quickly?

At the end of the day. My only concern is that it won't go back up after getting two hot. Ideally. I'd like to see it throttle at 80 then max out again repeatedly at 75-79 until the cap is hit again. If this is even doable. I'm not the mastermind behind it just a user loving the dev support you give us.
[T-Mobile Samsung Galaxy Note 3] themichael:
80 for freq throttling or core throttling (or both?)
[T-Mobile Samsung Galaxy Note 3] jaycb420:
Most likely 80 throttle 85 shut down cores.

Or 75/80
[T-Mobile Samsung Galaxy Note 3] themichael:
Yeah, I believe 80/85 is stock.
[T-Mobile Samsung Galaxy Note 3] jaycb420:
I thought stock was 60\65? Can never recall my stock note exceeding 65°
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
I think 80/80. Intellithermal uses 80, so if I'm running both simultaneously.... that's what I'd set FK Thermal to... v1.3 beta will have both enabled and would really appreciate the feedback from you guys on how well they work together...

Intellithermal throttles frequencies for a set period of time i believe... FK Thermal just lowers the frequencies automatically...

I'll look into both some more to see if it's even necessary to have both enabled....
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
There's a strong possibility I fixed the 2 minute boot times just now... I also enabled intellithermal, set FK Thermal to 80 to match the max of intellithermal.... AND changed the frequencies to this for FK Thermal.

I may add more steps, but won't experiment with that just yet... still working on resolving this 2 minute boot time... :good:
[T-Mobile Samsung Galaxy Note 3] jaycb420:
Thanks for your hard work. I'll be sure to spend some time on TW so I can test it out thoroughly.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Once I fix this 2 minute boot time, I'll get to working on ColonelAX... Just can't leave this kernel booting at 2 minutes everytime... gets annoying lol
[T-Mobile Samsung Galaxy Note 3] jaycb420:
Not a problem at all. Thanks in advanced.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Update: So the 2 minute boot time is still there, still working on it... Otherwise there's quite a bot of code updates, and minor changes. Intellithermal and FK Thermal work nicely together. What I did was raise FK Thermal's max to 85, as a back of to Intellithermal's 80. So if intellithermal does throttle the temps fast enough, FK Thermal will throttle the frequencies right behind it IF necessary....

There's other things like properly merging 3.4.78 code like Imoseyon did, and a few other things... I'm still trying to see IF i can resolve this boot issue before i release v1.3 BETA, but not sure yet... so we'll see...
[T-Mobile Samsung Galaxy Note 3] chrisgto4:
take your time. no rush
[T-Mobile Samsung Galaxy Note 3] abe_cedar:
zzmoove gov

hi mike

first thanks for ur work and tech support. makes my n3 rock.

any thoughts on zzmoove gov do u think is worth adding in ?

also do you have any recs 4 super batt saver

underclock io zen lookahead etc..

I know that u have addresses some of these qs b4. ondemplus etc.

I was wondering if you have more tricks in ur bag.

tia
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Hey Mike did you update the kernel? Not sure I haven't been on in a while and under downloads it shows 1.2.x. Thanks bro

Sent from my SM-N900T
[T-Mobile Samsung Galaxy Note 3] comptonhubbard:
any way we can use this on the sprint variant?
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Not yet... Going to real soon though... I'll be PMing you soon as well

You can try, not sure how it works.... have a backup kernel though just in case
[T-Mobile Samsung Galaxy Note 3] comptonhubbard:
will do thanks.
[T-Mobile Samsung Galaxy Note 3] tripartist1:
Glad to say my N3 is rock stable at 3ghz! And still have amazing battery life! But I do have an issue... I've used several different apps to try to use the touchwake feature. They all report that the kernel supports it, but touching, double tapping, swiping, and random gestures don't wake it. Is there something I'm missing? I have this in an otterbox, and use it one handed, so this is almost a must for me. I'm running colonelX and tweaked N3 2.0...anyone else having trouble getting this to work? TIA
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Some have been having issues with it, BUT you gotta wait for the screen to time out... like if it's set to power off in 30 seconds, then you let it go off. Then just tap the screen to come back on...

I may be working on something else, but not gonna share what it is just yet til i get it working....;)
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
v1.3 BETA is coming peeps! Think I finally fixed the boot issue, and got some cool new things to test out... Most of which aren't obvious changes, but should yield even better battery life... Also expect performance improvements ;). I'm shooting for later today.... hopefully all goes well....
[T-Mobile Samsung Galaxy Note 3] edwardplus:
I was being redirected from Galaxy Note 3 Original Zone to here.

I wonder if this kernel fits my Note 3 (SM-N9005) as I was suffering from several problems occurred after I flashed it via TWRP.

The major problem was the clock couldn't be set using the FauxClock app (or any other CPU optimizing apps).

It always changed from 3GHz or 2.3GHz to 1.7GHz automatically meaning that it didn't allow me to change it.

While shifting the bar to control the frequency, the bar shifted itself with the recent frequency and stopped at 1.7GHz

Observing from Antutu and CPU-Z, the maximum freq. was 1.7GHz from the benchmark and never reached more than 1.7GHz respectively, despite the fact that CPU-Z showed the device was 300MHz-3.01GHz.

The another problem was the long time consuming when turned the device on.

It took almost 2 minutes for every single booting while another kernel I tested just finish the boot easily.

Plus the extremely poor benchmark result and the lag in user interface really hesitates me whether this is the kernel for my phone but the thread really redirected me to here.

Currently using SM-N9005 Stock 4.3

Regards.:o
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Mikey is working on the 2 min boot time and it seems like he has it resolved along with some more battery and performance enhancements. I also had the issue where my clock would not stick and after a few attempts in a row I got it to work in Trickstermod and its been working ever since. Try setting the clock a few times in a row even backing out of the app and doing it again.

Finally remember this kernel is in Beta currently and you have to expect some minor issues. As we report them to Mike im sure he will resolve them as soon as he can as he has been.

Give it some time and I beleive you will be happy. Good luck friend.

Sent from my SM-N900T
[T-Mobile Samsung Galaxy Note 3] Okarina26:
this sounds to me like you are running the powersave mod...:confused:
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Sounds like that to me as well... Powersave feature might be turned on...
[T-Mobile Samsung Galaxy Note 3] VeNuMuS:
Nice dude. I can't wait to try it out.
[T-Mobile Samsung Galaxy Note 3] tripartist1:
Yea, I have waited for it to time out, still doesn't work. Kinda figured others would have issues as touchwake can be really picky... and what! More performance and better battery?! This kernel is amazing already, in both departments... I'd have to say one of the best I've used since my infuse (I was using an experimental Franco with Zues ROM and had the highest benchmarks for my model for a while) can't wait for the next update! Definitely keeping this kernel for a while. Anyone know of any other good TW ROMs? Preferably unthemed (or extremely clean, like tweaked N3 2.0). Really want to go with cm11, but don't want to lose this...

Scratch that edit... nvm
[T-Mobile Samsung Galaxy Note 3] ktetreault14:
I would love to have a kitkat version of this ??
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Try using the home key or power key instead of touching the screen. I dont have the kernel riggt now but I will in a few and ill try it also. On a previous build though it worked for me with those keys. Weird but nonetheless it worked.

Tweaked Monster
[T-Mobile Samsung Galaxy Note 3] edwardplus:
[controkarina26;50212023]this sounds to me like you are running the powersave mod...:confused:[/QUOTE]

Both of you guessed wrongly.

The default governor was ondemandX but while I was trying to change it though any optimizing applications, it just didn't applied as it returned after I relaunched them or was even not applicable.

Plus I have tried to set the maximum frequency for more than twenty times including relaunching the app and shifting the control bar to several frequencies but no help.

Regards:)
[T-Mobile Samsung Galaxy Note 3] dobbs3x:
You should only have one app installed to control your governors at a time.
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Never mind it doesnt work. I did get the oc to stick no problem in Trickster though. I used and purchased faux a long time ago but for me trick seems to play better with this kernel. Also no touchwake on fauxclock where the option is there in trickster unless I missed it. Not that it matters right now as it doesnt work anyway.

Mikey please bro after you fix the boot time please try to get the touch wake working if you can. I really miss that feature.
[T-Mobile Samsung Galaxy Note 3] edwardplus:
LOL of course I didn't do the thing you mentioned.

I'm not a beginner on flashing kernel and modifying the system.

Just answer my question as I had detailed them.
[T-Mobile Samsung Galaxy Note 3] chrisgto4:
if you would search the thread a little bit you would find that lots of users have also had the same issues and have found they're answers. regards

---------- Post added at 04:45 AM ---------- Previous post was at 04:23 AM ----------

sounds like you borked up somewhere, had a bad flash, or didnt read/search thoroughly. regards

be sure and hit the thanks button

---------- Post added at 04:48 AM ---------- Previous post was at 04:45 AM ----------

Both of you guessed wrongly.

The default governor was ondemandX but while I was trying to change it though any optimizing applications, it just didn't applied as it returned after I relaunched them or was even not applicable.

Plus I have tried to set the maximum frequency for more than twenty times including relaunching the app and shifting the control bar to several frequencies but no help.

Regards:)[/QUOTE]

power savings mode can be found in the settings menu on the phone. ..its nothing to do with choosing a governor....specifically under the general tab
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Both of you guessed wrongly.

The default governor was ondemandX but while I was trying to change it though any optimizing applications, it just didn't applied as it returned after I relaunched them or was even not applicable.

Plus I have tried to set the maximum frequency for more than twenty times including relaunching the app and shifting the control bar to several frequencies but no help.

Regards:)[/QUOTE]

After you set the clock frequency in Faux try viewing it with another app like android tuner, set cpu, Trickster etc... and see if it is sticking

---------- Post added at 10:57 PM ---------- Previous post was at 10:40 PM ----------

After you set the clock frequency in Faux try viewing it with another app like android tuner, set cpu, Trickster etc... and see if it is sticking

[/QUOTE]

Someone mentioned in an earlier post a few pages back that this was the case for them. If they went back in to Faux it would show defaul clock freq..but viewing throigh another app it would show the correct frequency set earlier. Worth a shot I think.
[T-Mobile Samsung Galaxy Note 3] edwardplus:
power savings mode can be found in the settings menu on the phone. ..its nothing to do with choosing a governor....specifically under the general tab

You cant explain why I flashed the Faux123 official kernel and I am still using it with no issue.

And I do know that the power-saving mode will ruin my phone performance but just no. I didnt turn it on.:(

After you set the clock frequency in Faux try viewing it with another app like android tuner, set cpu, Trickster etc... and see if it is sticking

---------- Post added at 10:57 PM ---------- Previous post was at 10:40 PM ----------

After you set the clock frequency in Faux try viewing it with another app like android tuner, set cpu, Trickster etc... and see if it is sticking

[/QUOTE]

Someone mentioned in an earlier post a few pages back that this was the case for them. If they went back in to Faux it would show defaul clock freq..but viewing throigh another app it would show the correct frequency set earlier. Worth a shot I think.

[/QUOTE]

That was what I was talking about. The bar to control the maximum frequency was not sticky and no matter how I tried to set it to max and reopened the Faux app to check whether it was stuck, not working at all and having no clue on that.

The situation in my case is not totally the same as them as the max freq only equaled to 3.01GHz ONCE after I shifted the bar to its max position. Viewing in CPU-Z and ANTUTU Benchmark, the CPU never reached 3.01GHz. And resulted a very disappointed benchmark score.

In case that was lower than my previous Note 2, only 17xxx marks.

Regards.:) Plus thank for you guys' patience. :highfive:
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
I'm gonna release a v1.3 beta.... The 2 minute boot time is still there, but i'm working on it. I know it's definitely something in source. [MENTION=4180899]wcoast[/MENTION] is helping me thoroughly with the testing. Much appreciated bro... I'll be building and releasing in a few... at least the performance and battery life is there. By the time v1.3 beta goes to stable I'll have the 2 minute boot time fixed....

Stay tuned peeps....
[T-Mobile Samsung Galaxy Note 3] farfromovin:
I feel like an idiot but cannot get this kernel to boot for the life of me on Tweaked 2.0. I'm using the latest TWRP and read back a couple pages but didn't see anything related.

When it tries to boot I get a message in red up top that says something along the lines of kernel not seenforcing. Any assistance or tips?
[T-Mobile Samsung Galaxy Note 3] VeNuMuS:
When you flash the kernel make sure to clear Cache and Dalvik. Then wait for it to boot.
[T-Mobile Samsung Galaxy Note 3] farfromovin:
Thanks, tried that 3 times with separate downloads. No such luck...unless the first boot takes several minutes and loops a few times first?
[T-Mobile Samsung Galaxy Note 3] VeNuMuS:
I personally stopped using TWRP once i noticed that it never really cleaned the Cache thoroughly. I use Philz recovery with no problems. Ive ran this Kernel for a while now with Tweaked and it always works. The boot time depends on device i think. Personally my boot time is closer to the 7 min mark.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
I also recommend Philz recovery. Nothing against TWRP, but it just doesn't seem to do everything properly on the Note 3...
[T-Mobile Samsung Galaxy Note 3] dobbs3x:
Never had a problem with twrp, flashed this kernel, saber, combustion, and faux and never had one issue.
[T-Mobile Samsung Galaxy Note 3] farfromovin:
Yeah, I've never experienced this on previous devices with various recoveries as well. Oh well, next time I clean flash I'll try again. Fwiw, Philz didn't fix my problem either.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
v1.3 BETA is live! See the changelog in the first post. Added a new governor variant of interactive governor... Let me know how that works for you guys :good:

[MENTION=4217465]farfromovin[/MENTION] See how that one works out for ya...
[T-Mobile Samsung Galaxy Note 3] farfromovin:
1.3 flashes and is running great here. Thanks everyone.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Alright folks....

v1.3 is a BETA. So this means I need you guys to test test test... I've added a few new things, and added back some new things after removing them in v1.2. Let me know how everything fairs out... The 2 minute boot issue, I'm still working to resolve. I had it fixed, til I started adding stuff back, but I seem to be constantly overlooking it.... See the changelog in the first post, and let me know what you guys think so far.

Sidenote: ColonelAX is still coming guys.... just trying to get a great kernel going... Might be prolonged considering 4.4.2 is right around the corner. I hope with the S5's release, we get the new UI on our Note 3s as well with the 4.4.2 update.... We'll see I guess....
[T-Mobile Samsung Galaxy Note 3] dobbs3x:
Would be cool to get a new ui, but the international note 3s didn't get it so I would be surprized, but you never know.
[T-Mobile Samsung Galaxy Note 3] jaycb420:
Did the s4 eventually get our ui?
[T-Mobile Samsung Galaxy Note 3] sbreen94:
Not officially but it's easy to port when on the same android base ;)
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
I'm wondering if Samsung & T-Mobile may be holding out on Kitkat for the Note 3 so we get all that in one update... I doubt the carriers will update to 4.4.2, then do another UI update, unless it has bug fixes and such that have to be taken care of. S5 I'm guessing will be announced officially on the 24th... Hopefully with the new UI, and more....
[T-Mobile Samsung Galaxy Note 3] Craniotomy:
As of now, max clock settings is sticking, when I wake up the phone i can see it going from screen off click i set then jumps to 2265, then goes to the max clock I've set. It's just a few hours since I flashed, I'm still testing, will update if I see something. Thanks!

POWERED by the ELITE MASTER!
[T-Mobile Samsung Galaxy Note 3] farfromovin:
Not shabby at all...
[T-Mobile Samsung Galaxy Note 3] chadcspencer:
No Head phones with 1.3 beta 1

Hi all,

Love the kernel, but just noticed with the new beta that there is no response when plugging the headphones in. Sounds still plays on phone speaker, no notification, no nothing. I'm going to drop back down to 1.2.5 for a bit. Thanks for the hard work.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Checking into it now.... Can anyone else verify this issue? Wondering if it's widespread or isolated....
[T-Mobile Samsung Galaxy Note 3] farfromovin:
My headphone jack works.
[T-Mobile Samsung Galaxy Note 3] wcoast:
I can confirm that headphone jack is working 110%, I have tried a million and one ways to recreate any kind of issue and it's still working awesomely well! I tested with both PowerBeats and Note 3 headphone, both working flawlessly.

---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------

Just flashed and tested headset sound on my brother's Note 3, everything is working perfect!
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Hey Peeps!

I hope Saturday is going well for all of you. I also hope v1.3 BETA is working fine...

As I've stated before, this kernel is in BETA, so I need you guys to help me with something important...

Can you guys please download terminal emulator from the play store and type this in it.... DO THIS AFTER A REBOOT (So I can see what's happening during those 2 minutes)!

su
dmesg >/mnt/sdcard/dmesg.txt
logcat -d -v time >/mnt/sdcard/logcat.txt

It would help greatly if a few of you guys can do this. Post both files in the thread if possible.... Thanks peeps! :good:
[T-Mobile Samsung Galaxy Note 3] GeneLM:
I would love to help. I have enjoyed your ROMs and Kernals in the past. However, I am on CM-11 and cannot use your Kernal at this time.

Still following the thread closely.
[T-Mobile Samsung Galaxy Note 3] Morningstar:
Here ya go...
[T-Mobile Samsung Galaxy Note 3] sshafranko:
FYI...kernel is running awesome for me. Havent found one issue other than the boot time. Will post the log for you later when I get home Mikey. These stats are with 3 hrs of gameplay (my daughter) and oc to 26. Pretty damn good imo...Awesome kernel...just need TOuchWake and im in heaven lol
[T-Mobile Samsung Galaxy Note 3] jpeps:
Oc to 26 setting please
[T-Mobile Samsung Galaxy Note 3] farfromovin:
Couldn't paste directly from my phone but here are the startup logs from my device: https://www.dropbox.com/s/19lvc3erw1r0cw9/lolcat & dmesg.zip
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Thanks for the logs peeps.... trying to get the 2 minute boot issue resolved before the next beta build....
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Looks like the 2 minute boot time issue is resolved. Got it consistently booting in 15 secs now... Expect another beta tonight possibly. Also...new file host... Might be goo.im or androidfilehost...
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Thanks bro, finally got the boot issue resolved.... Now i can work on something new... Gonna look into adding KnockKnock (Doubletap2wake) soon... it's not a lot of work, but it's gonna take some testing for sure... Not sure if it'll be in v1.3, might be a v1.4 thing... But i believe I can get it....

Just focusing on getting this thing super stable, then i'll jack it up again with something new lol
[T-Mobile Samsung Galaxy Note 3] btbamzao:
I'm 100% on board with the dt2w feature! You need a tester just hit me up.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Sounds good... I'll make it something I add in v1.4. Gonna get started on ColonelAX maybe tomorrow and get it going as v1.3 as well... Phew glad i got the boot time crap situated. Shout out to [MENTION=4180899]wcoast[/MENTION].... thanks homie!
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Sorry not sure are you asking for my settings?
[T-Mobile Samsung Galaxy Note 3] jpeps:
Yes
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
A few new things coming up starting next build:

New naming system, no more versions, gonna count by releases, starting from R9

New file host, probably AndroidFileHost

I restart development on ColonelAX this week

Gonna also start working on doubletap2wake, maybe later this week after ColonelAX

I'll keep everyone informed for sure...
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Here you go. Sry for all the pics its the easiest for me. I havent totaly adjusted voltages one by one the way I usually do it I just did it quickly also keep in mind depending on your bin# lower voltages may reboot you.
[T-Mobile Samsung Galaxy Note 3] sshafranko:
I never used DT2W and am not sure how it works so help me out if im wrong. With Touch wake the Digitizer would stay on as long as you set your delay for which I usually set for 10 seconds and then no more wakelock after that.

With DT2W isnt it something that is either on or off? So if on wouldnt it have to keep the digitizer on and have a wakelock all the time? If so wouldnt that cause some extra battery drain? Just wondering im not really familiar with this feature, thanks bro.
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
You're absolutely right! It does keep the digitizer on, hense causing the battery to drain more. It's basically the knock knock feature from the lg g2... when the screen goes off, just double tap the screen and it wakes up... I just know it's sought after feature
[T-Mobile Samsung Galaxy Note 3] sbreen94:
Double tap to wake would be pretty cool. You could minimize battery drain with like a screen off max profile that makes sure the CPU isn't going wild :D
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
That's a GREAT idea!! That makes complete sense! :good:
[T-Mobile Samsung Galaxy Note 3] chrisgto4:
was it the haptic stuff that was causing the long boot towards the end of the posted dmesg?

edit: or awesome player or selinux

lol looks like a lot of redundancy in both logcat and dmesg. glad you got it figured out. I have no real knowledge of what's going on in either of those. ... glad someone does. Thanks for all the hard work Mike. Your my boy blue!!
[T-Mobile Samsung Galaxy Note 3] fullklip211:
stock rom

Does this work on stock rom thanks for your work