yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] Psychotic Penguin:
Wow this is just smoking fast, great job
[Verizon Samsung Galaxy Note II] dogswind:
Thank God I tried this before retreating to a TouchWiz ROM again. This + the RootBox ROM is perfection. Many thanks!
[Verizon Samsung Galaxy Note II] bANONYMOUS:
New v1.60 works flawless on i317/M :D
[Verizon Samsung Galaxy Note II] zodduska:
Excellent updates, thank you!
[Verizon Samsung Galaxy Note II] ffolkes:
It already does. If no settings are made in STweaks, then it defaults to 60Hz always, as is stock.
[Verizon Samsung Galaxy Note II] bigmixxx:
Ok, I've flashed kernels before --

However this is a REALLY good one ....

Unless I don't see it anywhere (you can flame away if you'd like)

How can I get most value out of the kernel. I'm on the latest nightly of Rootbox. A couple of reboots into it to calm the Android OS utilization down, and I want to play with sound a little more ( kinda quiet to me ).

Is there a tutorial on STweaks floating around?

Also, any word on the dock (not the OTG cable works perfect) but the samsung dock....
[Verizon Samsung Galaxy Note II] Aesrys:
There's a guide in the General section for STweaks.

http://xdaforums.com/showthread.php?t=2079311&highlight=stweaks
[Verizon Samsung Galaxy Note II] shangrila500:
Did he ever post the flashable tweaks? I never could find them.
[Verizon Samsung Galaxy Note II] Aesrys:
Is that what this one is about? Haven't read it too closely.

http://xdaforums.com/showthread.php?t=2119761
[Verizon Samsung Galaxy Note II] shangrila500:
Yeah but there are no flashables that I found in the thread from him. I seem to remember them being there at some point but I can't find em anymore.
[Verizon Samsung Galaxy Note II] mallman:
yes, going back to 1.58 fixed it so 1.60 isnt for my device :)

mode delete or disregard, see the response from OP about a bad module and its been re-upped. sorry
[Verizon Samsung Galaxy Note II] benwalburn:
I use stweaks to turn off the backlight for the buttons, but after a reboot they're back on, even though the box is still checked to turn them off. Is this a kernel bug or a stweaks one?
[Verizon Samsung Galaxy Note II] shangrila500:
There is probably a setting in your ROM overriding the STweaks setting.
[Verizon Samsung Galaxy Note II] benwalburn:
You are correct. I found it in a settings menu I thought I had no need to use. Thanks for the reminder
[Verizon Samsung Galaxy Note II] ncwildcat:
Why is this so slow at charging...ramped up in stweaks and still very slow. 10% to 77% in 6 hours overnight...
[Verizon Samsung Galaxy Note II] ffolkes:
Sounds like you're not using a dedicated charging port, and instead just using a regular one.

On the 2-amp charger that comes with it, I usually get 1% a minute. Whereas when I connect it to a downstream port (aka my computer) it takes practically the entire day, as it's charging much, much more slowly.

Unrelated, I'll be getting 1.65 out to you guys today. :)

(The S-Pen changes below are obviously at the driver level, so they affect all apps)

1.65

- Battery battery life, particularly while idle. [thanks, temasek]

- Gesture engine now has support for two special gesture flags. I spent days perfecting this. More details later, but suffice it to say, you can set a gesture to use the touchkeys as a modifier, and while that modifier is held down, the entire touchscreen becomes gesture input only. So no more errant "tap-throughs" when drawing gestures. The power of this is awesome, and has changed how I use my phone.

- S-Pen: Disabled the booster and made it optional, as well as what frequency it boosts to. By default this used to lock at 800MHz when you used the pen, which has shown to be way overkill for the most part.

- S-Pen: Adjust input averaging strength (2 or 3 are the only useful settings. Wanna see what the actual input is from the digitizer? Set this to 0 and draw a line. Yeah...now you see what the poor driver has to filter out)

- S-Pen: Adjust box filter strength for pen input and hover input. Mostly experimental.

- S-Pen: Set minimum pressure before pen input is registered.

- S-Pen: Set fixed pressure (driver will never report sensitivity, and instead uses this value)

- S-Pen: Disable side button (for those that don't use it, it can really get in the way at times)

- S-Pen: X and Y axis offset (tweak this to your screen and usage. Samsung defaults this to -30 for right handed users)

- S-Pen: When the pen is within hovering distance, the touchkeys will now be disabled. When out of range, the block will be held for a definable period before restoring them. This means you can naturally write without fearing the buttons will come on and do crazy stuff.

- GPU: Frequency, voltage, and up/down threshold are available for each of the 5 steps.

- GPU: Expanded GPU clock options: 54, 100, 160, 200, 266, 275, 300, 333, 350, 400, 440, 500, 533, 600, 640, 666, 700, 733, 750, 800, 833, 850, 900 MHz.

- GPU: Adjust GPU scaling driver polling frequency.

- GPU: Lock GPU to one user-defined step.

- GPU: Increase default GPU polling frequency to 100ms (stock was 1000ms (!!!) and causing laggy performance within the first few seconds of using your device). [thanks, AndreiLux]

- Updated to Linux 3.0.82 [thanks, temasek]
[Verizon Samsung Galaxy Note II] shangrila500:
I get the the same charge with mine when using the charger that came with it and the Anker car charger I got, it usually takes about an hour and a half to 2 hours to charge mine completely depending on how low the battery is. If I use my wall battery charger that came with my Anker batteries it takes about 5-7 hours depending on how drained it was.
[Verizon Samsung Galaxy Note II] ncwildcat:
I use the charger that came with the phone Always...I only have seen this issue with kernels (Perseus on tw and this) that have stweaks support. Hopefully the new release will help
[Verizon Samsung Galaxy Note II] ffolkes:
Very strange. Has anyone else reported this in any of the Perseus threads?
[Verizon Samsung Galaxy Note II] ncwildcat:
I haven't seen it reported..I will report if I get it working..
[Verizon Samsung Galaxy Note II] Peperm1nt:
I just flashed cm 10.1(current nightly) and this kernel earlier today. I'm now home charging(same cable and adapter that the phone came with) and I'm getting the REALLY slow charging bug. I have STweaks installed and I haven't changed any settings. It's almost at a stand still on charging and I used this charger last night with no problems.

Tapin' the Talk on my GNote ii
[Verizon Samsung Galaxy Note II] ncwildcat:
I saw a tip in the liquid thread that I tried and fixed my charging issues - froze performance in titanium, then made stweaks a system app. Now I am charging like a champ
[Verizon Samsung Galaxy Note II] shangrila500:
Very very odd.... at least you found a fix so we can help anyone else who has this issue.

What exactly did you free in Tibu? Was it just an app named Performance?
[Verizon Samsung Galaxy Note II] busab:
Sorry if this is a stupid question but can this kernel be flashed onto a tmobile note 2? I'm running liquid smooth 2.7.
[Verizon Samsung Galaxy Note II] Peperm1nt:
Can you elaborate please? I don't see an app named performance in TIBU.. I would like to get this solved. Kernel is amazing.

Tapin' the Talk on my GNote ii
[Verizon Samsung Galaxy Note II] akellar:
He's probably referring to performance control and not all roms include it
[Verizon Samsung Galaxy Note II] shangrila500:
Is it found under System Apps in Tibu? I've never heard of doing what he did and haven't seen Performance Control in the AOSP Roms I've been running.
[Verizon Samsung Galaxy Note II] a1rb0rn:
Some ROMs (liquid smooth, carbon to name a couple) have an app called "performance control" baked into the ROM itself. This app overrides s_tweaks and won't let it function. If you have a ROM that includes this performance control app, it will be in the main list of apps in titanium. You can freeze it, and set s_tweaks as a system app and this will allow it to function properly, and you can use it to adjust the charging performance, etc.
[Verizon Samsung Galaxy Note II] strikeir13:
Is this in the OP and the number just has to be changed?
[Verizon Samsung Galaxy Note II] ncwildcat:
This...exactly. Once that was frozen and I moved stweaks to be a system app charging and controls for stweaks worked great. Moving to system may have been overkill but this worked for me
[Verizon Samsung Galaxy Note II] Peperm1nt:
What settings did you use?

Tapin' the Talk on my GNote ii
[Verizon Samsung Galaxy Note II] ncwildcat:
I guess any you want...the settings now respond to what they should
[Verizon Samsung Galaxy Note II] Peperm1nt:
I've made sTweaks a system app in CM and I have the settings default. Also, I've checked for the performance app and can't find it. I know stweaks is working via testing the screen settings. I guess I'm just afraid of adjusting the power options.

Tapin' the Talk on my GNote ii
[Verizon Samsung Galaxy Note II] ncwildcat:
Performance is included with liquid and some other aosp
[Verizon Samsung Galaxy Note II] strikeir13:
Sorry, I may be missing it, but is 1.65 available yet? Or just in testing?
[Verizon Samsung Galaxy Note II] a1rb0rn:
Nothing yet, I think that may have been a teaser to make sure we're still paying attention. :D
[Verizon Samsung Galaxy Note II] wizayne:
I thought I couldn't find it or something simple like that so thanks for helping clear it up.

to the posters with the stweaks fixes, don't think I have had an issue with stweaks not executing my settings but I'll be freezing the other performance app and setting stweaks to be in /system/app. I don't use the inbuilt performance app anyway so perhaps that's why I have not been affected by this but it certainly can't hurt to disable an app I don't use

Can't wait for the SPen enhancements and thanks ffolkes.
[Verizon Samsung Galaxy Note II] idkwhothatis123:
+1

I don't even see an update in his commits since 6/13
[Verizon Samsung Galaxy Note II] ffolkes:
My github isn't entirely current at the moment. :P But it will be once I'm sure there are no bugs left.

In addition to what I posted the other day, S-Pen insertion is fixed, and the GPU can be limited to a max step. For people who don't play games and otherwise don't mind slow graphics performance, you can set the max step to step 2 or 3. Personally, for daily use I limit to 3 steps, and customize them to 54, 100 and 160.

Latest version: v1.65 and here is the flashable gesture pack. The preset gestures are explained on the Gestures tab of STweaks.

Since some gestures require a touchkey to be pressed, you have to enable the Touchkey Modifier Delay on the Screen tab by setting it to something like 150ms since it is turned off by default.

Any time you touch and hold a touchkey and then touch the screen within the delay you just set (150ms) you will activate gesture-only mode, during which the touchscreen will no longer send touch events to the operating system, only the gesture engine. This means you won't get any bleed through of gesture draws into the foreground app. It's also a safety of sorts, to prevent critical gestures from being accidentally triggered. The downside is, you can't have your cake and eat it...well, not without some delay at least. If the touchkey modifier was simply piggybacked onto the touchkey driver that would be nice, but it would also mean every time you used it, it would also report the touchkey (Menu/Back) event. Or, if you blocked it always, well then obviously your touchkeys wouldn't work anymore. So a compromise is using a very short delay, and after that delay is up, the touchkey driver checks to see if the screen has been touched and the touchkey is still down. If so, then gesture-only mode is set in the touchscreen driver until all fingers are up. If the screen has NOT been touched after the delay, then the touchkey driver assumes it's just a normal touchkey press and reports it like normal. This may seem like an insanely small delay, but it's meant for you to touch the touchkey and start drawing with another finger *simultaneously*.

tl;dr: Flash the gesture pack, go to the Screen tab and set the Touchkey Modifier Delay to 150ms or so, then apply it. Now test it. First swipe from near the bottom-left corner, up towards the middle-right side. Nothing should happen. Now repeat, this time putting a finger down on the touchkey and holding, while *at the same time* starting to drawing this simple gesture. Aim to have both fingertips touch down at the same time. If it goes well, the virtual power key will be pressed and it will go into suspend. If you have trouble, increase the delay until you get more practice. Eventually you'll be able to do this gesture one-handed by touching the touchkey with the side of your thumb, and sliding/flicking your index or ring finger outward in an arc.

Good luck. :P
[Verizon Samsung Galaxy Note II] idkwhothatis123:
I love you.
[Verizon Samsung Galaxy Note II] broprah:
ohhh sweet nectar
[Verizon Samsung Galaxy Note II] dbrickg:
flashed 6/26 kernel over the latest cm10.1 yesterday, and, though I didn't notice it till today, the speaker stopped working: no ringtone, no notification, no music... not sure it's due to the kernel, but when I reflashed the cm10.1 w/o this kernel, and then, later, when I reflashed the previous kernel, I got the speaker back again.

PS: it was just the built-in speaker that stopped working: earphones still worked.
[Verizon Samsung Galaxy Note II] Spencer_Moore:
Same problem for me
[Verizon Samsung Galaxy Note II] dbrickg:
Thanks. Good to know it wasn't just me having the speaker cut out and go mute like that.
[Verizon Samsung Galaxy Note II] kiitick:
For those with audio problems, disable voodoo and enable sound controls in stweaks.
[Verizon Samsung Galaxy Note II] shangrila500:
With Voodoo disabled, and Wolfson control enabled, the volume is still noticeably lower that previous versions set up the same way, including me old son audio being the selected option instead of Voodoo.

The volume is only lower on calls, strangely enough, regardless of whether I use the built in phone app. It doesn't make any difference if I used speakerphone.
[Verizon Samsung Galaxy Note II] dbrickg:
Thanks for the advice.

ffolkes: you might want to mention this in the OP. Otherwise it's pretty obscure. I stopped using voodoo a long time ago, and almost never use stweaks, so it never occurred to me to go there to enable what should probably be the default behavior.
[Verizon Samsung Galaxy Note II] benwalburn:
With the latest version I am seeing battery life identical (if not slightly better) to using a stock rom, while the previous version had a slightly lower battery life. And I haven't even messed with stweaks much.

But speaking of stweaks, my stylus is broken and I don't plan on replacing it till I get around to replacing my phone (cracked screen). Is it possible to disable stylus support to improve battery life? I believe there is a setting that disables the digitizer when the pen is inserted, but I can't find it now.
[Verizon Samsung Galaxy Note II] Peperm1nt:
If using CM, Settings>advanced settings slide over to audio and raise the values there, it helped me when I was using CM. Also I'm fairly sure you can raise the values in the audio tab in STreaks and it will help.
[Verizon Samsung Galaxy Note II] shangrila500:
I am using VRB and have adjusted all the settings in VRB and Stweaks to what they previously worked at with version 1.60. 1.65, with the same settings and worth higher settings, doesn't do anything to the speakerphone or phones built in headset, no matter what they are changed to the volumes never change. All other audios will adjust with Stweaks settings but not those 2. I am going to flash the latest stable version so hopefully it won't have the same issue.
[Verizon Samsung Galaxy Note II] ahjee:
Kernel runs great.
[Verizon Samsung Galaxy Note II] ffolkes:
Thanks for the suggestion, but it has been the #1 FAQ question for months. :P It's the 2nd post after the OP.

I'm thinking of getting rid of Voodoo entirely. AndreiLux's Wolfson Sound Control (it doesn't have an official name really..) is much better. I only left Voodoo there because some people preferred it. But really, anything you can do with Voodoo you can do with Sound Control.
[Verizon Samsung Galaxy Note II] shangrila500:
I would be fine with that, Voodoo doesn't do jack diddly on my phone. The sound is all kinds of wonky and I can never get it right, on Wolfson I never have any issues whatsoever,
[Verizon Samsung Galaxy Note II] dbrickg:
Ooops. Sorry about that. I don't think I'd ever looked at the FAQ. Everything just worked. And then it stopped. And I hadn't noticed anything in the change log that I understood to make the sound stop working... even though it was there. I just hadn't understood.

Thanks again for the marvelous kernel.
[Verizon Samsung Galaxy Note II] shangrila500:
So I'm having issues in VRB, no matter what changes I make I cannot get the speaker volume during calls to get any louder. I went back to 1.60 to see if my issue was with 1.65 and I had the same issue.

Has there been an edit in the CM bases that stops kernels from being able to change the in call volumes?
[Verizon Samsung Galaxy Note II] a1rb0rn:
What ROM are you on?
[Verizon Samsung Galaxy Note II] bigw34:
Hes on Vanilla Root Box (VRB), at least that's what he keeps saying in his posts.
[Verizon Samsung Galaxy Note II] ffolkes:
I'm using the Sprint version of RootBox, and can confirm lack of meaningful in-call volume control. The in-call volume ranges between normal and barely-perceptibly louder. It affects both earpiece and speaker. I think this is a ROM issue?

Voodoo has been removed from the kernel build I'm using, so it's not that.
[Verizon Samsung Galaxy Note II] bigw34:
Hey guys, Ive flashed a lot of Rom's before to my phone, but Ive never messed around with kernels yet. Ive also never messed with the power controls baked into Rom's either. So with that said, I am starting to learn more and looking into kernels, but Im not looking to play with all of the aspects of it. Im basically looking for better battery life and a little overall system improvement.

If I flash this, am I forced to tweak things or will I have to try and match my settings between my Rom (Liquid Smooth 2.7) and STweaks/turn off my power control, make STweaks a system app, etc....?

Thanks for your help in advance.
[Verizon Samsung Galaxy Note II] shangrila500:
You should be able to control everything in Stweaks without having to tweak with the ROM controls. That being said sometimes the ROM controls can cause some problems, like the capacitive button settings may hold over from your ROM and the STweaks settings may not work until you turn the ROM controls off, but for the most part you can just use the kernel controls.

You don't have to make Stweaks an app, there was an issue a guy had on one of the AOSP Roms, I want to say Liquid, where he had to freeze Performance controls or something like that using Tibu.

As for settings, there is a great thread in General that ChaoticWeapons started that people are using to post their tweaks and it helps you get everything set up. Here is a link to it:

http://xdaforums.com/showthread.php?t=2079311

---------- Post added at 06:42 PM ---------- Previous post was at 06:38 PM ----------

I was hoping I wasn't crazy, dlsolo in the VRB thread said that he has working Voodoo and that he can adjust his volume just fine.... He is on 6-27 and I can't remember which nightly started causing the issue with Voodoo.

I would much rather be using Wolfson controls but I cannot for the life of me get it to work so I'm going to take his advice and see if I can get Voodoo working until Wolfson works again.
[Verizon Samsung Galaxy Note II] dbrickg:
Just wanted to second this. My in-call volume is really low. When I turn it all the way up, it becomes loud enough for a quiet room, but not a noisy one. I'm running yesterday's nightly release of cm10.1, if that makes a difference. I'm just doing a nandroid and then I'll try the rom without the kernel, to see if that makes a difference.

---------- Post added at 07:08 AM ---------- Previous post was at 07:04 AM ----------

I'm having in-call volume control problems. The buit-in speaker and the audio-out for headphones seems to be fine, but the earpiece for phone calls is pretty weak. I'll try the rom (cm10.1) without this kernel to see if I can determine whether it's a kernel problem or a rom problem... or maybe I'm just crazy :-\

... OK, just finished reflashing the 20130701 CM 10.1 nightly without this kernel, and it didn't seem to make any difference for the in-call volume. I'm going to back to the rom thread and see what I can figure out there....
[Verizon Samsung Galaxy Note II] shangrila500:
OK what I found out last night while tinkering around on VRB 6-28 nightly, i clean flashed it again and started all over, is that there is a new addition to Settings/Device Options called Audio. Under Audio it has In-Call volumes set at 50%. You can jack it up to 100% but it will actually sound lower than before, you have to set it at 90% instead. Once that's done you can tweak with STweaks and jack the volume up nice and loud.
[Verizon Samsung Galaxy Note II] dbrickg:
Hahah... 100% is less than 90%. Thanks for the hints. What do you tweak in STweaks to make the volume nice and loud?

Hopefully they'll get this sorted out soon so we don't have to go chasing will-o-the-wisp config options much longer. I mean, I love all the cool stuff I can do with my phone, which would have been impossible except for all the work the developers have done, but a phone really should work as a phone without having to beat it into submission
[Verizon Samsung Galaxy Note II] FrankyFiggz27:
I also found that 60% > 90%, at least for me..
[Verizon Samsung Galaxy Note II] enik_fox:
Tried flashing this and the loudspeaker only put out the softest of tones. Reflashed without this kernel and everything is fine. Weird
[Verizon Samsung Galaxy Note II] dbrickg:
As was pointed out to me yesterday, you might want to try item 1 in the FAQ (post #2, in this thread):

In fact, more explicitly, it was suggested that I turn off Voodoo and use Sound Controls instead

---------- Post added at 04:26 PM ---------- Previous post was at 04:13 PM ----------

Just wanted to emphasize that the in-call volume problem is NOT due to this kernel, but exists in the plain CM 10.1 ROM and, apparently, the VRB ROM as well. See the discussion near the end of the CM 10.1 nightlies thread, starting about here:

http://xdaforums.com/showpost.php?p=43063325&postcount=1452
[Verizon Samsung Galaxy Note II] enik_fox:
That was what I tried first
[Defy Q&A, Help & Troubleshooting] jokermithun:
Hi friends after following cm10 and jellyx kernel thread i knew this 17feb 2013 nightly is the most stable rom...i tried flashing this build on my defy and defy+ from scratch i.e.starting from sbf..but every time it went into bootloops:rolleyes:

is there any way so i can boot this rom on my both defys:o
[Defy Q&A, Help & Troubleshooting] joke19:
Hi, what you installiert to this? Test cm,gapps and jellyx only.

Gesendet von meinem MB526
[LG Optimus Black] BlackPie:
Can I please have a step-by-step way of how to properly calibrate my bettery after flashing a new ROM?Thanks.
[LG Optimus Black] SaschaKH:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT

I know that it is not really what you asked for but it might give a few thoughts.
[LG Optimus Black] YkZ_1967:
Battery Calibration

Requirements: Android 2.1+ | Root permissions

Calibration needs to be done after flashing a new ROM, but you can calibrate any time you think your battery is miscalibrated. This program does it by removing the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.

It's suggested, but not necessary, to let the phone fully discharge after calibration, then charged to 100% without break.

=> https://play.google.com/store/apps/...EwOSwiY29tLm5lbWEuYmF0dGVyeWNhbGlicmF0aW9uIl0.
[LG Optimus Black] dcop7:
You don't need to calibrate the battery, ever.
[LG Optimus Black] BlackPie:
But what if I already tried it,will the system reset the stats again or smthing?