yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cubsfan187:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

3 not 2. Lol. Fat fingers on a little phone! Nice catch. I'll edit it now.
[Samsung Galaxy Nexus] josip-k:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I have high hopes for this kernel. Lets try. I will review tommorow. ;)
[Samsung Galaxy Nexus] PatimusXPrime:
now what happens if you disable all of them? i did that with gemini app manager, seems to be okay except for some reason everytime i reboot i have to get a gps lock.. i think it's either because i disabled them all OR because i greenified it.. thoughts?
[Samsung Galaxy Nexus] cubsfan187:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I've never tried to kill them all. Would be a good test though.
[Samsung Galaxy Nexus] ToMeRv32:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Anarakia (not sure about the spelling..) , can you please revert the kernel boot image? Make it white on black and not the opposite.

That white is so bright that at night it's making me blind..
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

If you set delay to 0 , it works even if you lock it by yourself

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Muvolt:
The new Diamond kernel (v29) feels slower in comparison to v20...
[Samsung Galaxy Nexus] Bl4ck3urn:
Don't reboot before you go to sleep, problem solved.
[Samsung Galaxy Nexus] szucsgf:
Was going to do some testing to see if there's a difference in deepsleep behaviour with and without touchwake, but you've already expressed exactly what I found. I did three 15-minute tests:

Touchwake off: deepsleep = 14 minutes

Touchwake on, 0 delay, let screen time out: deepsleep = 0 minutes

Touchwake on, 0 delay, power button to lock: deepsleep = 0 minutes.

So I guess touchwake will severely impact your battery over a long period of time if kept always on using the 0 second delay. Too bad.
[Samsung Galaxy Nexus] ToMeRv32:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Lol, great idea..
[Samsung Galaxy Nexus] rmean:
AW: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

well, i guess a wakelock is needed to keep the screen active..

i like touchwake for reading long texts, very useful for that. 3 sec delay should be enough for that :)
[Samsung Galaxy Nexus] nrgaway:
Are you supposed to be able to change 'Temperature Limit' in Trickster from 80 to 85? I tired changing the value on 029 and it always goes back to 80.

I want to do this since I believe I get thermal throttling when the CPU temperature reaches 80, which happens sometimes for me.
[Samsung Galaxy Nexus] nikulogical:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Putting the delay on touch wake to 0 also wouldn't be a good idea because its very sensitive and even putting it in your pocket and your leg touching the screen through your pants will start the screen on. Its not like pgm where a certain pattern needs to be made.

Ak, I know you're working on a rebased purity but would it be a good idea to do a poll whether users prefer touchwake or pgm-compatibility..just to get an idea of the usage?

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] AutomaticFailure27:
Now if there was a way to combine PGM into the kernel, then all of our problems would be solved!!
[Samsung Galaxy Nexus] buggerthis:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I always kill all the maps receivers. I haven't found it to impact functionality yet.
[Samsung Galaxy Nexus] Wh1t3Rose:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

How are some of you guys getting a day and half of battery time. I can't get over 18-20 hours on days I'm 100% wifi

Toro| Xylon | AK Diamond
[Samsung Galaxy Nexus] nikulogical:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Screen on time is a better way to measure battery life. People with long battery life don't turn on the screen that much and since idle drain isn't much they'll battery will last pretty long.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] Wh1t3Rose:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Well there was a screenshot a few pages back that had 2 days of battery with 2.5 hrs screen on and he barely touched wifi. How?

Toro| Xylon | AK Diamond
[Samsung Galaxy Nexus] jjhiza:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Extended battery possibly. I routinely get between 13 and 16 hours of up time, with just over 3 hours screen on time, and I'm on 4G all the time. I live in the Metro NYC area though, and my signal strength is always good.

A lot of factors go into achieving good battery life - screen brightness, usage patterns, wallpaper color, governor/scheduler combo, etc. Personally, I'm eagerly awaiting the return of Intellidemand... I've always gotten the best balance of battery life and performance with it, paired with cfq and Westwood. :)
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

How about a 2 versions of kernel same features but, 1 having pgm fully supported and other one without it?

I know the dev don't use pgm but many of us users use it. Touchwake is not really an option because it comes with a certain amount of activation delay.. Now if you set it to 0 it will prevent your phone to deep sleep thus bigger battery consumption..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ak:
No becasue Diamond is my baby and i like a new features ... you have to wait to a Milestone release. Im sorry.

No, because is closed source.

I like the bootsplash because is like a punch in an eye. :D
[Samsung Galaxy Nexus] ak:
Yes my friend ...
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I'm hoping for that my friend thanks I'm back to v20 for now :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I also like the boot splash. :thumbup:
[Samsung Galaxy Nexus] cmoG530:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Comment Removed
[Samsung Galaxy Nexus] shanp7780:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

anarkia loving ak just like 1st time I came here never disappointing whatsoever!!!

Call me stubborn but I'm still hung up on cylon #801 that's my baby all tweaks and greatness that went into it has been a beast 4 me. I have yet to try 29 I did however use diamond-19 but missed 801 you think you may add some more I/O and governors back?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AutomaticFailure27:
I have an idea...

It's a bit controversial...

Back in my OG Evo days, I used atyoung's Mason Kernel and it gave me the best battery life at the time (heavy use, playing games, youtube and still over a day worth of battery) What I think did it was the use of SBC (Superior Battery Charge / Smart Battery Control or something of that nature) or "trickle charging" the phone. There used to be a review on therootofallevo.com about how different kernels implemented SBC and the affects it had. Let's just say, Mason Kernel definitely had the right combination of voltage and power that a) didn't "blow up" the battery 2) didn't overheat 3) stabilized the battery for a more slow and smooth percent drop.

I know there is BLX now, but I feel it still doesn't do the same as SBC once did. I don't know any of the technical architecture of this, or if it is even possible anymore. Just something I thought could be fun to experiment with.

TL;DR: Is SBC something that could be implemented into the Nexus?
[Samsung Galaxy Nexus] Charmacas:
AW: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Ok thanks for saying that. So it's something wrong with my flashing or configuration.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] ak:
todo:

- new milestone

- add zram

- add fiops

ecc ...
[Samsung Galaxy Nexus] ak:
I dont know its difficult to test .... if you compare v20 into v29 there are a lot of changes ... but from v27 to v29 there aren't minimal changes into kernel core! :fingers-crossed:
[Samsung Galaxy Nexus] ak:
I can verify ... but for now the todo list is very long .... :D :D :D
[Samsung Galaxy Nexus] madhavs:
It's just a tad above 7 am and you turned up for the work, Great commitment :good:
[Samsung Galaxy Nexus] AutomaticFailure27:
All good, can't rush perfection :victory:
[Samsung Galaxy Nexus] shanp7780:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Sweet!!! might test drive ver.29 when I flash eclipse-elemental in a bit :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ak:
Mmm .... i have make a reflection, probably the speed change is related to this commit:

https://github.com/anarkia1976/AK-tuna/commit/a5fab6796f0bbb5e724ef039e7f492ff7720cb16

Its a benefit for a battery life! ;)
[Samsung Galaxy Nexus] Charmacas:
AW: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

If I disable FSYNC I get even the same results as with v27 (maybe a little slower).

If it's good for battery life and disabling FSYNC does the job I can live with it. :) Thanks for reflecting it!

Sent from my Galaxy Nexus with Tapatalk 2

---------- Post added at 08:48 AM ---------- Previous post was at 08:42 AM ----------

If you implement ZRAM: Could you make it stable as hell?

If not I would prefer that you not implement it. It causes many SODs anytime I activated it and it has run for a few hours. I think the idea is very nice but if it's not stable I would never activate it.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] impulse101:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

What features are you disabling by stopping these startup sevices? Are you losing location reporting or any location services?
[Samsung Galaxy Nexus] Shardzmi:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Yeah, I think it was my screen. Try slim bean :)
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

29 is good :)

But i always see temp throttle on logs :/
[Samsung Galaxy Nexus] cubsfan187:
It's stopping maps from opening without you actually doing it. The bottom 2 are for update notification and rating reminders for the store. The others ones are different location reporting things. Like if you want your friends to know where you are in some apps. GPS and maps and all that will still work just fine.
[Samsung Galaxy Nexus] ak:
I have to verify, because im always on debug session and i have lunched antutu but i cant see throttle horse! :cowboy:
[Samsung Galaxy Nexus] definator:
just a little feedback for atom v10 with ak v20 and neph settings with modified color settings

voltage is all lowered by -50

performance all over is ok, but could be better. it was just a testing sequence for battery behavior

for my device therer were some issues:

- crippled ringtone and notification sounds when screen off + screen didnt want to wake up sometimes when incoming calls

- sometimes stuttering coz of slow frequency stepping

- not so good audio quality with bt playback (hands free sound system)

i think first and third are belong to the - voltage, which my device cant handle that good as others do

first and second maybe could be coz of the low max cpu speeds

i will make another test run, but with v29 (anarkia is too fast to get some setups through one kernel version :P)

this time with higher speeds and voltages

ps: for the testing setup, sync, and mobile connections (+data, if not wlan) where active all the time

did surfing, benching, whatsapp, streaming music via bt and having phone calls (really..!)

display brightness has been fixed to approx 25%
[Samsung Galaxy Nexus] sajty:
I had exactly the same problem.But in v029 it looks,that problem is gone.
[Samsung Galaxy Nexus] ak:
Good ... thanks a lot for hard testing!

Have you see thermal throttle problem?
[Samsung Galaxy Nexus] definator:
no issues for me with throttling. had no performance break down or what ever

will give it a try and see :)
[Samsung Galaxy Nexus] swarm871:
R: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

First battery cycle with diamond 29

Setting:all stock except

Freq 230-1200

Uv

230mhz - 750mv

350mhz - 800mv

Very very good battery life.

I used wifi when in the screen wifi is on... 3g the rest of the time

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] musashihatred:
:)

thanks captain. i read the log somewhere 5 mins every after boot that cpu temp throttle exceeds @ cpu freq 700 and 910.
[Samsung Galaxy Nexus] ak:
new kernel

I want to share some good news for the new kernel:

- problem for thermal resolved:

omap_temp_sensor.c + temp_control.c: Remove safety and Up the Threshold

- re-add fiops

- new readahead value - good bench with fiops

mm.h: Set VM_MAX_READAHEAD 768

- A lot lot lot of news on net/ip drivers - Thanks Lioux

Codel and Merge with a lot of commits from 3.2 kernel

Changelog:

ak-4.2.2-official-mainline
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Zram is pretty stable, the problem comes in when ppl have different scripts changing there VM setup, it throws off the values to the system,

Like everything I have come to notice about these phones is that once we have the performance parts ready i.e. kernel and rom, we have to fine tune the setup to run insync with each other properly
[Samsung Galaxy Nexus] sajty:
I want to do fresh install of whole system,now i will "must" wait for it! :laugh:
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Oh yeah :) this is it. XD
[Samsung Galaxy Nexus] cubsfan187:
Stefano are there any plans to add sakuractive gov and row scheduler back in the future? I know you're still working on a stable base and reworking the whole kernel but I was just curious.
[Samsung Galaxy Nexus] Nephilim:
I know I'm not Anarkia but I have to say, hotplug governors such as sakurative have been proven to not play nice with our devices cpu. I've noticed that without hotplug, sakurative and pegasusQ that there have been far less people complaining of freezes and SOD's. Honestly interactive yields excellent results with a little tweaking.
[Samsung Galaxy Nexus] ak:
I agree with the analysis!

i can when i see a superstable kernel ... this for remedy to entropy generator! :good:
[Samsung Galaxy Nexus] Heart1010:
Diamond v029 doesn't work with PGM2, do it?! (Slide2Wake)

So what should I take then... purity030? (but that's gone here from the thread)
[Samsung Galaxy Nexus] TomPzh:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

To wait for next update~
[Samsung Galaxy Nexus] ak:
I dont know and this is a question for search button!

Post the problem on PGM thread.

No more PGM request here please!
[Samsung Galaxy Nexus] NutellaBanane:
I already answered it here : http://xdaforums.com/showpost.php?p=39635301&postcount=1571
[Samsung Galaxy Nexus] ciprianruse88:
Stefano, I sent you a pm :fingers-crossed:
[Samsung Galaxy Nexus] quickstang:
I was waiting for someone besides myself to answer that :D

I vote to ban the word PGM from this thread. lol

Or maybe tell the dev of PGM to clearly state to contact him for ANY issues related PGM & that it is not the responsibility of the Kernel dev to be the go to person for all related PGM stuff. I don't use it myself, but man the amount of PGM stuff on here is over kill.

On another note... v029 is working great. As the ROMS keep improving, the Kernels get better as well as apps getting better, the GNex is finally coming to life like it should be.

For those of you who use ES File Explorer, this was one of my HUGE culprits with lags & freezes. I'll never know what was the issue with it & whether it didn't like 4.2.2, my ROM or Kernels, but the latest beta fixes any lag whatsoever in that app. It's a great update as it was my daily driver for file explorers & installers but was laggy as hell before this new version. My lag is slowly disappearing :good:
[Samsung Galaxy Nexus] sajty:
Big delay between incoming call and screen turning on is kernel or ROM related?Now i had call and it took about 5 second to turning screen on :(.
[Samsung Galaxy Nexus] quickstang:
Probably ROM related or some other issue. However, I am using an LTE version for Verizon & not GSM so yeah. However i would rule out the kernel unless you have min or max screen on very very low & the phone is waking slower than when the call comes in.
[Samsung Galaxy Nexus] Muvolt:
I'm back with Diamond v20. v29 was slower for me and I really don't get the point of the extra battery optimizations vs performance...you can always charge your device at night or get a bigger battery but nothing will replace the user experience with faster menus, more responsive scrolling etc....
[Samsung Galaxy Nexus] sajty:
AK 029 - interactive+deadline,230min/1060max and 525 max screen off + XenonHD 7.1
[Samsung Galaxy Nexus] kmakiki:
I need to read up more on how these various different governors work at a hardware level; as an electrical engineering student, this kind of stuff is fascinating. In doing so, hopefully I can contribute more to this thread! Still rocking your kernel Anarkia, it is simply the best!
[Samsung Galaxy Nexus] ak:
I dont know why, im on AOSPA and i recieved about 30 40 calls every day without problems. :highfive:
[Samsung Galaxy Nexus] ak:
That would be very nice as is doing Lioux with net / ip part!.
[Samsung Galaxy Nexus] sajty:
Hm,i will try ondemand and waiting for fiops :).
[Samsung Galaxy Nexus] quickstang:
Look at Mr popular. I don't think anyone calls me 40x in a whole month. lol. I rarely use my phone. And when I make calls, my most monthly calls are probably to 911 for my job. lol

sajty, you could bump up the 230 min one step & see if that helps. Then if not, try one more step. Just test it that way. If you still have the problem, you know its not that issue then move on from there.

There were times when I had my min very low my phone would never wake. Some people have no issues, but I did. I always keep mine a bit higher, but always still test with every new kernel release. That's the nice thing about all of this development. You can keep playing with stuff & maybe something that doesn't work at one point finally does.
[Samsung Galaxy Nexus] dp917:
I've gotten this too with toro AOSPA, and also happens to text and alarms. I did a clean wipe yesterday and it still happens. For me I'd get a notification light (lightflow), about a second later start to vibrate, then sound about another second later, and screen on couple seconds later. I'm using Nephilim's settings.
[Samsung Galaxy Nexus] ak:
You can try to use stock settings and leave min 350, off 700 .... this is my suggestion!
[Samsung Galaxy Nexus] cubsfan187:
I see your point. Especially now that we can turn the cores off (for lack of a better way to put it) with the multicore power saver option. I already use your settings Neph and have had great results with them. Screen off idle stats are super low and screen on is about where I'd exoect it to be under mod-heavy use. :good:
[Samsung Galaxy Nexus] spupuz:
i'm also using a similar configuration with nephelim settings:

congestion control TCP cubic

Read Ahead buffers size 896

scheduler deadline

minx freq screen off 180000

max freq 920000

max freq screen off 350000

governor interactive

content adaptive brightness on

fast charge on

group activity in less number of core 2

high sound performance off

boost sound in hearphone 3

touch wake off

fsync off

smart relfex core iva mpu ON

i also use crossbreeder and toggle2g and greenify for unwanted sync apps (like FB or Linkedin or G+)

whit these settings i achived a battery usage screen off of -1,5%/h / -2.0%/h
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Guys, I used touchwake with delay set to 0 and now I seted delay to 60 seconds and touchwake works also if I lock the screen manually and after 60 seconds it's off and the device enters in deep sleep so now it's all perfect.

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] definator:
oh man... you announced another new version :-S

so i will wait for next testing period with new kernel then
[Samsung Galaxy Nexus] sajty:
Oh,how i hate those situations :D.I know,that new version of kernel exists,but its available only for the chosen ones.It like to say to a small child,i have a candy for you,but you must wait for it :laugh:
[Samsung Galaxy Nexus] ak:
Not right this ... because the new kernel is on my phone only ... dont create entropy please! ;)

and in this moment fiops dont work very well!
[Samsung Galaxy Nexus] Khizar:
lol we dont have any new kenrel either..i think only Ak has it :p

Edit- Ak already posted :good:
[Samsung Galaxy Nexus] sajty:
lol,ok,i have said nothing :D

EDIT: btw.,i raised frequencies and changed governor to ondemand.Now i had incoming call and delay between sound and screen on was much smaller.
[Samsung Galaxy Nexus] Blackcrx:
What's your thoughts on the ROW scheduler? Any chance of it being included in the future releases?
[Samsung Galaxy Nexus] flip360:
is 60sec. the sweet spot for touchwake?

it doesnt work after i lock the screen manually here though :)
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Set it to 0 first.lock it manually then touch the screen to wake it and then set it to 60 and try again cuz it should work

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Alkemix:
I prefer SIO scheduler than deadline, now. SIO seems more reactive, I haven't any lags ... I hope for battery life (tomorrow I will know it), because AK diamond is a nuclear rocket ! ;) Baked blackbean 8 rom flies by Ak diamond 29 :cool:

Yesterday "touch wake" function has determined a freeze on my Galaxy Nexus. I will use it with caution in the future...
[Samsung Galaxy Nexus] MBQ_:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

SIO is a personal favorite of mine
[Samsung Galaxy Nexus] Nephilim:
Will that work on my iPhone?
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Only on iphone 6

Sent from my Shining Nexus using AK DIAMOND ED.

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

Mine too.always using sio

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] flip360:
Thanks i will try it

tried it still not working on manual lock (works on "0" only)

Here also but i left it a "0" and after sometime the touchscreen didnt respond anymore had to pull battery out
[Samsung Galaxy Nexus] MBQ_:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Yes
[Samsung Galaxy Nexus] Nephilim:
F*ck iPhone 6, My Zune has AOSPA 3.15!
[Samsung Galaxy Nexus] buggerthis:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Touch wake doesn't seem to be working on my phone. I set the delay to 5 seconds because my screen lock is delayed by 5 seconds, and I figured that when the screen timed out I could touch it within 5 seconds to get back to an unlocked device with the screen on. But it doesn't work. When I touch the screen, it comes on and then goes off again immediately.

Have I got the way touch wake is supposed to work figured wrong?
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

You had a sod.go to play store,take pgm free app,open it,give it superuser acces,activate pgm module,unistall the app and see then if touchwake will work if u lock the screen manually.these are the only things I did and for me it works fine.

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] spupuz:
i do prefer AOKP :P unicorn power!
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Open gtalk

Sent from my Nexus Prime
[Samsung Galaxy Nexus] ak:
Guys please no Off-Topic! :D