[Kernel][AOSP][2.02 | November 2nd] Plasma kernel

[enormous]

Thanks for all you do!

2CT02846UD4304718

 

[tvwebguy]

I just learned about Synapse. Does anyone have any recommended settings?

 

[NickosD]

I just learned about Synapse. Does anyone have any recommended settings?

Not all devices are working the same. I always had a lot of uv on both of cpu and got and abb voltages.
You have to try yourself. For start you can go all cpu steps -50 except the 800 mhz one. It won't boot, it must have the default voltages. The same for gpu.

Sent from my GT-N7100 using Tapatalk

 

[ffolkes]

Thank you so much to those who donated, it is always very, very much appreciated.

Plasma kernel v. 2.52 has been released!

Download (and extended changelog)

Changelog:

• Plasma BackBlink
• Added S-Pen detach/insert actions
• Support for ZZMoove profiles in Synapse
• Upgraded to ZZMoove 0.9 beta 3
• Ported existing Plasma changes to new ZZMoove version
• Added native input booster to ZZMoove (based on faux123's intelliactive)
• Added minimum frequency while mUSB plugged in (ZZMoove tuneable)
• Added core up/down staggering (ZZMoove tuneables)
• Added up/down block multipliers for each core (ZZMoove tuneables)
• Added support for Boeffla sound engine
• Added limited support for intelliactive CPU governor
• Added optional instant key-up upon key-down for Home button
• Made optional CPU boost on buttons/touchkeys adjustable
• Fixed WaveWake bugs
• Fixed minor S2W bug
• Fixed Touchkey hardware staying on with S2W
• Updated BFQ scheduler to v7r2 (thanks psndna88)
• Other small commits (battery savings)

 

[skye206]

Thank you so much to those who donated, it is always very, very much appreciated.

Plasma kernel v. 2.52 has been released!

Download (and extended changelog)

Changelog:

• Plasma BackBlink
• Added S-Pen detach/insert actions
• Support for ZZMoove profiles in Synapse
• Upgraded to ZZMoove 0.9 beta 3
• Ported existing Plasma changes to new ZZMoove version
• Added native input booster to ZZMoove (based on faux123's intelliactive)
• Added minimum frequency while mUSB plugged in (ZZMoove tuneable)
• Added core up/down staggering (ZZMoove tuneables)
• Added up/down block multipliers for each core (ZZMoove tuneables)
• Added support for Boeffla sound engine
• Added limited support for intelliactive CPU governor
• Added optional instant key-up upon key-down for Home button
• Made optional CPU boost on buttons/touchkeys adjustable
• Fixed WaveWake bugs
• Fixed minor S2W bug
• Fixed Touchkey hardware staying on with S2W
• Updated BFQ scheduler to v7r2 (thanks psndna88)
• Other small commits (battery savings)

I think its about time I venture back aosp to try this update out. I only wish there was a touchwiz version of this. Boeffla or voodoo is a must have on a note 2.

Sent from my SPH-L900 using XDA Free mobile app

 

[ffolkes]

I think its about time I venture back aosp to try this update out. I only wish there was a touchwiz version of this. Boeffla or voodoo is a must have on a note 2.

I'll probably try to make a TW version soon.

 

[skye206]

I'll probably try to make a TW version soon.

You just made my work day a little better thank you.

Sent from my SPH-L900 using XDA Free mobile app

 

[t4d73]

I'll probably try to make a TW version soon.

That would be so cool! I love AOSP but it was really because I love this kernel. Cm is a great rom but if I could have a stock experience with this I just might jump ship. I just thought it would be a real ***** to get done with the way Sammy locks everything down. Hope you can pull it off!

Sent from my SPH-L900 using XDA Free mobile app

 

[skye206]

That would be so cool! I love AOSP but it was really because I love this kernel. Cm is a great rom but if I could have a stock experience with this I just might jump ship. I just thought it would be a real ***** to get done with the way Sammy locks everything down. Hope you can pull it off!

Sent from my SPH-L900 using XDA Free mobile app

Same here its this kernel that brings me to aosp. I love cm but I don't like the bugs. This kernel makes me live with them. I loved Perseus kernel on 4.1.2, this kernel replaces that part.

Sent from my SPH-L900 using XDA Free mobile app

 

[aleve1983]

I'll probably try to make a TW version soon.

Ffolkes you can read on international forum n7100? We have a problem with softkey

 

[stylz3]

Ffolkes you can read on international forum n7100? We have a problem with softkey

I can second this as I tried the latest kernal on omnirom and the soft keys were inactive.

 

[bjrmd]

I can second this as I tried the latest kernal on omnirom and the soft keys were inactive.

I had the same thing on omni but thought it was using xposed additions that remapped buttons. I find that if I start hitting the capacitive keys during the boot process (before synapse complete flashes) the keys will work fine -till the next reboot.

 

[t4d73]

I thought it was my chrome browser but it did happen to me too once while trying to hit the menu button. But after just holding down the home button and clearing apps it worked just fine.

Sent from my SPH-L900 using XDA Free mobile app

 

[ColeTrain!]

I'll probably try to make a TW version soon.

That would be great, we don't have a kernel other than stock.

 

[ffolkes]

Ffolkes you can read on international forum n7100? We have a problem with softkey

Sorry about the problem with the touchkeys, it happened to me once but never again, so I assumed it was just a freak accident. I see the problem now, it should only be affecting people using Touchwake. I will get an update out soon, until then you must make sure "Ignore touchkeys while screen off" is unchecked and reboot, as that setting is what is causing this, and it is on by default.

 

[bjrmd]

Sorry about the problem with the touchkeys, it happened to me once but never again, so I assumed it was just a freak accident. I see the problem now, it should only be affecting people using Touchwake. I will get an update out soon, until then you must make sure "Ignore touchkeys while screen off" is unchecked and reboot, as that setting is what is causing this, and it is on by default.

That doesn't work for me, always had that off anyway, but tried toggle and reboot, no effect.
Still, if I hit the soft keys a few times as it boots, they function fine thereafter

 

[ffolkes]

Plasma kernel v. 2.53 has been released! I've put a lot of work into PatternUnlock, and I'm anxious to see what people think of it. Read more about it here.

Download (and extended changelog)

Changelog:

• Plasma PatternUnlock
• Fixed unresponsive touchkey bug
• ParanoidAndroid variants should handle root properly now
• Other small bugfixes and Synapse corrections

 

[jlmancuso]

Plasma kernel v. 2.53 has been released! I've put a lot of work into PatternUnlock, and I'm anxious to see what people think of it. Read more about it here.

Download (and extended changelog)

Changelog:

• Plasma PatternUnlock
• Fixed unresponsive touchkey bug
• ParanoidAndroid variants should handle root properly now
• Other small bugfixes and Synapse corrections

Guess I will have to nand back to 4.4.4 and test it out!

Sent from my GT-N7105 using XDA Premium 4 mobile app


Edit: working good so far. Pattern unlock will take some time to figure out correctly but seems to be fine.

Edit: Edit: Well I started to extract a rom zip and tried turning off the screen. Bad thing to do. Screen will not stay off. It keeps turning on wanting me to unlock it.

After futher testing it does not seem to be related to pattern lock. Not sure if it is kernel or rom related yet. I will try with another kernel and let you know.

One other thing. Would you mind if I compile your kernel with my 4.4.4 beanstalk rom?

 

[bjrmd]

Plasma kernel v. 2.53 has been released! I've put a lot of work into PatternUnlock, and I'm anxious to see what people think of it. Read more about it here.

Download (and extended changelog)

Changelog:

• Plasma PatternUnlock
• Fixed unresponsive touchkey bug
• ParanoidAndroid variants should handle root properly now
• Other small bugfixes and Synapse corrections

Thanks again for the great job

Pattern unlock does have a problem if the device is waked from hitting touch keys or slide to unlock when the "enable wakelock+pattern unlock is chosen. The screen will come on but the pattern unlock is not there. If the wake lock choice is disabled it seems to work fine, but only slide to wake turns the screen on-not hitting a soft key.
Not a big deal--just fyi

Softkey issue nonresponse has been fixed-thanks.

 

[ffolkes]

Thanks again for the great job

Pattern unlock does have a problem if the device is waked from hitting touch keys or slide to unlock when the "enable wakelock+pattern unlock is chosen. The screen will come on but the pattern unlock is not there. If the wake lock choice is disabled it seems to work fine, but only slide to wake turns the screen on-not hitting a soft key.
Not a big deal--just fyi

Softkey issue nonresponse has been fixed-thanks.

This is actually intentional in a strange way, but I will make the "Lock All Input" option default to true in future versions. What happened is, PatternUnlock started as merely a way to tap your screen to turn it on, much like Doubletap2wake, so it always held a wakelock, and when it was tapped with the proper pattern, it would wake. Then I added the ability to lock input as an afterthought. But then after that, it was suggested that people might not want to hold a wakelock at all, and instead always press power and enter their pattern. So when you use "Enabled - No Wakelock" internally it HAS to lock input, otherwise it would be useless. But when you use "Enabled - Wakelock", it's operating the way it originally intended - simply as a way to turn your screen on. It's up to you to scroll down and check "Lock All Input" since it is no longer done implicitly, because the user might only want PatternUnlock to just turn their screen on and not actually ever lock any input. It's really confusing, sorry.

I'm not sure what you mean by the touchkey stuff. Could you please explain.