[KERNEL] [N4] [6.0][3.4.0][AOSP/CM] [10/26] [M2] - AK

[ak]

You should really consider making an app that can be used to control the awesomeness of this kernel

I haven't the necessary java/android basis for make an app. im sorry.

 

[brian88]

all cores always run in v210, is it normal???

 

[snak3ater]

@Sak3ater
I have see these:

- for have S2S
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/s2w_s2sonly
[email protected]:/ # cat /sys/android_touch/sweep2wake
cat /sys/android_touch/sweep2wake
1
[email protected]:/ # cat /sys/android_touch/s2w_s2sonly
cat /sys/android_touch/s2w_s2sonly
1

- for have S2W
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/s2w_s2sonly
[email protected]:/ # cat /sys/android_touch/sweep2wake
cat /sys/android_touch/sweep2wake
1
[email protected]:/ # cat /sys/android_touch/s2w_s2sonly
cat /sys/android_touch/s2w_s2sonly
0

do you have see the same?

with these set s2s work .....

Yes.. I got the same.. Earlier i was using trickster.. I don't know why trickster caused trouble this time.. It never happened before.. now i used the commands to set s2w/s2s

Sent from my Nexus 4 using Tapatalk 4

---------- Post added at 06:00 PM ---------- Previous post was at 06:00 PM ----------

all cores always run in v210, is it normal???

No it's not normal.. Turn on mpdecision

Sent from my Nexus 4 using Tapatalk 4

 

[arifqur]

Dear Anarkia I have been using your kernels forever and at some stage during the 4.3 development I started having freezing at reboot with s2w enabled and unless I immediately unlock the lockscreen when it appears after a reboot, the screen turns on but touchscreen is totally unresponsive. Same problem with neo's kernel until v14.
Sad to say I still have this problem with v210.

 

[snak3ater]

Dear Anarkia I have been using your kernels forever and at some stage during the 4.3 development I started having freezing at reboot with s2w enabled and unless I immediately unlock the lockscreen when it appears after a reboot, the screen turns on but touchscreen is totally unresponsive. Same problem with neo's kernel until v14.
Sad to say I still have this problem with v210.

Strange..No such thing at me end..

 

[hardwareadictos]

Is possible that 210 is giving bad battery percentage readings?

 

[ak]

Dear Anarkia I have been using your kernels forever and at some stage during the 4.3 development I started having freezing at reboot with s2w enabled and unless I immediately unlock the lockscreen when it appears after a reboot, the screen turns on but touchscreen is totally unresponsive. Same problem with neo's kernel until v14.
Sad to say I still have this problem with v210.

Dont enable at boot .. its simple man. :fingers-crossed:

 

[ak]

Is possible that 210 is giving bad battery percentage readings?

No, only if you use s2w ...

 

[hardwareadictos]

Aaaaa okey. Thanks for reply!

---------- Post added at 04:54 PM ---------- Previous post was at 04:45 PM ----------

Ak can you add the multirom patch in the next release?

 

[ak]

Aaaaa okey. Thanks for reply!

---------- Post added at 04:54 PM ---------- Previous post was at 04:45 PM ----------

Ak can you add the multirom patch in the next release?

Yes no problem

ak

 

[hardwareadictos]

Yes no problem

ak

Awesome!! Thanks!

 

[ayysir]

[KITKAT] [EXPERIMENTAL]
download: AK.210.KK

Changelog:
Thanks a lot to showp1984 and bricked kernel for n5
+ s2w v2.0
+ s2s v2.0
+ dt2w

+ codel net scheduler
+ se linux boost

+ ecc ecc ecc

Thanks and rate as always.

Vertical s2w backport

https://github.com/Ayysir/android_kernel_google_msm/commit/f94d54648f6391bfe2f6a34dcad924df9e3e2f1b

and

https://github.com/Ayysir/android_kernel_google_msm/commit/3df9fdba080084f119cc1a1a8ae783b9e67db89e

 

[ak]

Vertical s2w backport

https://github.com/Ayysir/android_kernel_google_msm/commit/f94d54648f6391bfe2f6a34dcad924df9e3e2f1b

and

https://github.com/Ayysir/android_kernel_google_msm/commit/3df9fdba080084f119cc1a1a8ae783b9e67db89e

Thanks man ... for the support and help.
I have see a derp into powerkey drivers from my side i have pushed fix:
drivers/input/misc/pmic8xxx-pwrkey.c
now
power_on_display_dt2w(ipwr);
fixed
power_on_display_dt2w(pwr);

 

[ayysir]

Thanks man ... for the support and help.
I have see a derp into powerkey drivers from my side i have pushed fix:
drivers/input/misc/pmic8xxx-pwrkey.c
now
power_on_display_dt2w(ipwr);
fixed
power_on_display_dt2w(pwr);

good stuff

done: https://github.com/Ayysir/android_kernel_google_msm/commit/2f5060a97b29c4b8ca82a084c0dfff29690961df

it would be great to make a sysfs for horizontal s2w and vertical s2w

 

[c_86]

cm11 support coming soon?

 

[gorilla p]

cm11 support coming soon?

I assume you mean for s2w?

Sent from my Nexus 4 using Tapatalk

 

[c_86]

I assume you mean for s2w?

Sent from my Nexus 4 using Tapatalk

i meant for v210... its only KK currently...

 

[ak]

i meant for v210... its only KK currently...

Can you confirm - v.207 - work with cm11 official nightly?

 

[c_86]

Can you confirm - v.207 - work with cm11 official nightly?

yes, im using it on the latest cm11 kitkang 11/26 build without any issues... hopeing to see overclock come back soon tho

 

[David9519]

I miss the features too :/

Sent from my Nexus 4 using xda app-developers app