yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] büscher:
This one:

<6>[ 618.668151] Resume caused by IRQ 162, bcmsdh_sdmmc
<6>[ 618.668151] PD_CORE curr=ON prev=ON logic=ON
<6>[ 618.668151] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[ 618.668151] CD_L3_INIT mode=SW_WKUP activity=0x5300
<6>[ 618.668151] USBPHY mode=AUTO idlest=ON optclk=0x100
<6>[ 618.668151] DPLL_USB status=locked
<6>[ 618.668151] Powerdomain (core_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 618.668151] Powerdomain (l3init_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3

is present alot... I don't think it schould?

bcmsdh_sdmmc: BCMSDH Function Driver for the native SDIO/MMC driver in the Linux Kernel

Just an assumption: Since this is related to internal memory, could this also be the cause to my poor database I/O results in Antutu?

:confused:
[Samsung Galaxy Nexus] thuongphuong:
Thanks, this is the best kernel for my Galaxy Nexus !
[Samsung Galaxy Nexus] osm0sis:
If it didn't go away with the 2.17 from the OP after you deleted the init.d scripts and rebooted then it can't be any of the stuff I just added to the ramdisk for my updated version. And that's the only stuff that touches IO.
[Samsung Galaxy Nexus] büscher:
This is what it looks like on SmittyV_Metal (Version 1):

<4>[ 1977.914581] Disabling non-boot CPUs ...
<5>[ 1977.923339] CPU1: shutdown
<6>[ 1977.924316] Resume caused by IRQ 162, bcmsdh_sdmmc
<3>[ 1977.924316] Successfully put all powerdomains to target state

noting else changed. will check Dirty_V RSR 2/17
[Samsung Galaxy Nexus] osm0sis:
Thanks. I really doubt it's the ramdisk guys. :)

---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------

Metal also had my ramdisk with renicing, lmk whitelist and all that stuff, so I'd say that counts it out as being the problem for sure. But you're probably on to something, regardless. :good:
[Samsung Galaxy Nexus] büscher:
yep, I know about the ramdisk in smittyv metal.

Sorry for accusing your ramdisk ;) As I said, I'm a noob interpreting those logs...

whoops... and a freeze with system.ui reboot while checking Dirty_V 2/17

no entries about bcmsdh_sdmmc until now, will monitor my phone.
[Samsung Galaxy Nexus] aosp:
Do you have dynamic fsync enabled?
[Samsung Galaxy Nexus] büscher:
no, never. this little feature made me lose data more than once in the past.

edit: this is what happened during the freeze: (While I opened Whatsapp)

I/InputDispatcher( 555): Dropped event because it is stale.
...
I/Choreographer( 2032): Skipped 1695 frames! The application may be doing too much work on its main thread.
...
E/ActivityManager( 555): ANR in com.android.systemui
E/ActivityManager( 555): PID: 731
E/ActivityManager( 555): Reason: Input dispatching timed out (Waiting because the touched window has not finished processing the input events that were previously delivered to it.)
E/ActivityManager( 555): Load: 7.51 / 3.72 / 1.51
E/ActivityManager( 555): CPU usage from 14095ms to 225ms ago:
E/ActivityManager( 555): 99% 147/surfaceflinger: 0% user + 99% kernel
...
I/ActivityManager( 555): Killing 731:com.android.systemui/u0a7 (adj -12): background ANR
I/art ( 758): Wrote stack traces to '/data/anr/traces.txt'
I/WindowState( 555): WIN DEATH: Window{653c9888 u0 com.android.systemui}
I/WindowState( 555): WIN DEATH: Window{651fa558 u0 com.android.systemui}
I/WindowState( 555): WIN DEATH: Window{6539bc00 u0 com.android.systemui}
W/ActivityManager( 555): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
W/ActivityManager( 555): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
W/ActivityManager( 555): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
I/WindowState( 555): WIN DEATH: Window{653ca570 u0 com.android.systemui}
I/WindowState( 555): WIN DEATH: Window{65394760 u0 PieControlPanel}
...
[Samsung Galaxy Nexus] osm0sis:
Random derp, I think. I'm interested in those bcm mmc ones though.
[Samsung Galaxy Nexus] büscher:
until now there is nothing like that in the dmesg with DirtyV-RSR { 2/17 }

would be great if someone who also had issues could check in their logs.

edit: here we go again, dmesg is full of it

<4>[ 2367.178283] Disabling non-boot CPUs ...
<5>[ 2367.179260] CPU1: shutdown
<6>[ 2367.179840] Resume caused by IRQ 162, bcmsdh_sdmmc
<6>[ 2367.179840] PD_CORE curr=ON prev=ON logic=ON
<6>[ 2367.179840] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[ 2367.179840] CD_L3_INIT mode=SW_WKUP activity=0x5300
<6>[ 2367.179840] USBPHY mode=AUTO idlest=ON optclk=0x100
<6>[ 2367.179840] DPLL_USB status=locked
<6>[ 2367.179840] Powerdomain (core_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 2367.179840] Powerdomain (l3init_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<3>[ 2367.179840] Could not enter target state in pm_suspend
<6>[ 2367.179901] Suspended for 9.457 seconds
[Samsung Galaxy Nexus] bsmitty83:
The power domain message has been present in at least the last 3 builds , not sure what's causing it

But I've seen it before .
[Samsung Galaxy Nexus] büscher:
okay. can't say much to 2/15 and 2/10. I didn't use those because of wifi driver of 2/10 and 2/15 being supresed to fast :silly: :D
[Samsung Galaxy Nexus] aaron13:
Phone is flying again with Nephs settings, however I raised the voltages a bit(+825). Too low gave a key guard test activity error at the startup. I also set westwood and sioplus for even better battery :thumbup:
[Samsung Galaxy Nexus] Punkiderma:
got a random reboot (for the first time not during a call) after hours of running fine and smooth, I would have logged it but I don't know how to obtain last_kmsg, is disabled inside syslog.

How can I enable it?

Forgot to say, nephilim's settings but without any undervolt, just underclocked to 920 max
[Samsung Galaxy Nexus] aaron13:
deleted
[Samsung Galaxy Nexus] aosp:
If it happens again it should be here /proc/last_kmsg if missing check the about system status in settings for current uptime might be the system_server crashing not the kernel

Bootlog can grab last_kmsgs and check uptime automatically ;)

https://play.google.com/store/apps/details?id=se.mumu21.bootlog
[Samsung Galaxy Nexus] bsmitty83:
And as I type that ive yet to see it come up . I'm using dirtyV regular ram . it may be a setting keeping it from its target
[Samsung Galaxy Nexus] pattyboi:):
+1 for the havent seen it part. been running dirtyv bigmem without issue
[Samsung Galaxy Nexus] pattyboi:):
its a sloowwww day in the dirty thread...
[Samsung Galaxy Nexus] Punkiderma:
Yeah bootlog says there was a system crash, but the problem is that I can't obtain last_kmsg(syslog app says is not supported by my kernel), so bootlog doesn't work properly (it says only that the phone crashed)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] milojoseph:
it got quiet
[Samsung Galaxy Nexus] pattyboi:):
i think everyone was busy today lmao
[Samsung Galaxy Nexus] cujo6801:
I think there might be a$$

Play involved... :eek:

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
u crack me up to much man i swear xD
[Samsung Galaxy Nexus] cujo6801:
Proof ..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] milojoseph:
*warning* NSFW ROOF ROOF LML :D
[Samsung Galaxy Nexus] pattyboi:):
Do NOT let Smitty's wife find those ,I can hear her now .."so THATS why you have been on xda so much" ;) (LOL,btw cujo,those are f*cking awesome xD)
[Samsung Galaxy Nexus] cujo6801:
I'll tell my sisters you liked them....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
In the case that they are your sisters,I think they are very upholding and beautiful women. They deserve the up-most respect.
[Samsung Galaxy Nexus] cujo6801:
O I'm sorry I should have been more clear..

No no no that's there slutty girlfriends....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
This is probably the first time I've heard the word "slut" and been attracted other than disgusted...considering I live in the land of crack sluts lol...but nice girlfriends...you lucky bastard..
[Samsung Galaxy Nexus] cujo6801:
O and so there no problems here...

They all use DirtyV....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
You better hope they don't have a dirtyv...
[Samsung Galaxy Nexus] cujo6801:
I'll just leave this here

Sent from the "DOG" pound
[Samsung Galaxy Nexus] milojoseph:
Ok so since everyone like battery saving... what apps so you recommend. ?. Beside greenify
[Samsung Galaxy Nexus] Hetalk:
None :D

I'd resist adding another app on my already huge app list. :good:
[Samsung Galaxy Nexus] gohamstergo:
thats one problem i have. i have like 20 apps that are always in the background, eatin my RAM X_X. the beauty of android tho, is that i can choose to do that if i want.
[Samsung Galaxy Nexus] büscher:
Good morning (afternoon, night...) everyone!

Yesterday I clean flashed my ROM and DirtyV 2/17 again.

I'm pretty shure those micro fereezes were cause by omniswitch that was added in CM Remix in the last build. So nothing kernel related.

My phone is on since 2 hours now, I'm at 90%, listening to music while on train (with viper as driver) and about 10 minutes screen on.

Not bad so far, had worse days.

Will report if anything unusual happens, also if I find those powerdomains in my dmesg and if, after what I did before...

btw: bcmsdh_sdmmc not in dmesg until now.

Have a nice day!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Pootch:
30% battery drain over night.. data connection disabled, only gsm..

back to old version before ramdisk (ramdisk is what for on a smartphone??)
[Samsung Galaxy Nexus] Gabboplano:
Check your wakelocks...
[Samsung Galaxy Nexus] büscher:
now there is another cause of that powerdomain:

<4>[ 752.230560] Disabling non-boot CPUs ...
<5>[ 752.231658] CPU1: shutdown
<6>[ 752.232238] omap2_gpio_set_edge_wakeup: aborted suspend due to gpio 46
<6>[ 752.232238] GIC returns spurious interrupt for resume IRQ
<6>[ 752.232238] PD_CORE curr=ON prev=ON logic=ON
<6>[ 752.232238] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[ 752.232238] CD_L3_INIT mode=SW_WKUP activity=0x5300
<6>[ 752.232238] USBPHY mode=AUTO idlest=ON optclk=0x100
<6>[ 752.232238] DPLL_USB status=locked
<6>[ 752.232238] PD_L4_PER curr=ON prev=ON logic=ON
<6>[ 752.232238] PD_MPU curr=ON prev=ON logic=ON
<6>[ 752.232238] Powerdomain (core_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 752.232238] Powerdomain (mpu_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 752.232238] Powerdomain (l3init_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 752.232238] Powerdomain (l4per_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
[Samsung Galaxy Nexus] Culex316:
Is there any technical reason why smartreflex can't go above 1.5ghz in this kernel?
[Samsung Galaxy Nexus] Edward Stanbury:
awhhh yiiss :P
[Samsung Galaxy Nexus] büscher:
sorry for spamming this thread with dmesgs now ;)

but the bcmsdh_sdmmc powerdomain was taken over with this one after clean flashing:

<4>[ 1127.650482] Restarting tasks ... done.
<6>[ 1127.659759] PM: Syncing filesystems ... done.
<7>[ 1127.664581] PM: Preparing system for mem sleep
<4>[ 1127.664886] Freezing user space processes ...
<3>[ 1127.668151] Freezing of user space aborted
<4>[ 1127.669281]
<4>[ 1127.669311] Restarting tasks ... done.
<6>[ 1127.672607] suspend: too many immediate wakeups, back off
<6>[ 1138.157073] PM: Syncing filesystems ... done.
<7>[ 1138.169281] PM: Preparing system for mem sleep
<4>[ 1138.170135] Freezing user space processes ... (elapsed 0.026 seconds) done.
<4>[ 1138.196258] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
<7>[ 1138.197723] PM: Entering mem sleep
<6>[ 1138.207000] PM: suspend of devices complete after 7.904 msecs
<6>[ 1138.208068] PM: late suspend of devices complete after 1.068 msecs
<4>[ 1138.208068] Disabling non-boot CPUs ...
<5>[ 1138.209289] CPU1: shutdown
<6>[ 1138.210144] Resume caused by I/O pad: CONTROL_PADCONF_WAKEUPEVENT_0[22]
<6>[ 1138.210144] PD_CORE curr=ON prev=ON logic=ON
<6>[ 1138.210144] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[ 1138.210144] CD_L3_INIT mode=SW_WKUP activity=0x5300
<6>[ 1138.210144] USBPHY mode=AUTO idlest=ON optclk=0x100
<6>[ 1138.210144] DPLL_USB status=locked
<6>[ 1138.210144] Powerdomain (core_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 1138.210144] Powerdomain (l3init_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<3>[ 1138.210144] Could not enter target state in pm_suspend

I have no clue why this happens or if it may has to be like this?

One thing to mention: battery life is waay better now with DirtyV 2/17 RSR after a clean flash and these powerdomain entries are not that frequent anymore.

aww yes they are, but obviously only if unplugged.

aaand those chicks :good: :good: :D sitting in class and accidentally scrolled trough :p
[Samsung Galaxy Nexus] Sheetzie03:
Sllliiiiiiip

****f****!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Uhoh. Now this thread's getting really dirty.

I like it :good::highfive:
[Samsung Galaxy Nexus] pattyboi:):
Poor Smitty,hope hasn't missed all the fun we have been having,but anyway for relevance, I have yet to have a issue with dirtyv 2-17
[Samsung Galaxy Nexus] Hetalk:
Been running the latest one by [MENTION=4544860]osm0sis[/MENTION] with slimkat and yet to see an issue.

Got best every screen-on time and is pretty damn smooth.

Phone's never been this smooth. Seriously! :good:
[Samsung Galaxy Nexus] qu4nd:
Are u using this one? DirtyV-RSR-2.17.14-osmod.zip
[Samsung Galaxy Nexus] Hetalk:
Yes.
[Samsung Galaxy Nexus] sagara.sandaru:
Those pics should be added to the OP lol :D someone make a banner plz ;)
[Samsung Galaxy Nexus] Kustaa:
I'm afraid I'm becoming cleaner and cleaner...need some dirtiness!
[Samsung Galaxy Nexus] hasnol143:
Other than the snapchat camera hangups, smittyV-16 has been working awesomely for me, going to try Nephilim's setting now and see whats up
[Samsung Galaxy Nexus] cujo6801:
This is the end...

Thanks everybody...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
Guys, although the T&A pics are great and all, remember how much negative attention this much OT brought to the AK thread back in the day. We should probably take this stuff to the General Discussion section of the G+ board. ;)
[Samsung Galaxy Nexus] ASHURiCAN:
Great idea! :P
[Samsung Galaxy Nexus] 47th_Ronin:
MOM????
[Samsung Galaxy Nexus] pianistaPL:
Oh, c'mon guys... Don't make spam.
[Samsung Galaxy Nexus] cujo6801:
OK sorry OP.... ^^^^^^

Wait a minute...

sent from the DOG pound
[Samsung Galaxy Nexus] Nephilim:
Feel free to take my comment sarcastically guys, but do not be surprised when this thread is threatened to be closed by Mods just as AK thread was last year more than once.

You all know I'm not trying to spoil the fun, I am merely trying to keep this thread from having problems.
[Samsung Galaxy Nexus] büscher:
Sorry to interrupt your OT ;)

Just wanted to say some more to DirtyV RSR 2/17 after a day of using it:

This latest kernel is really freaking fast, my phone is buttery smooth! Especially after a clean flash of my rom and extensive cleaning. Switching homescreens, switching opened app, texting, almost everything of my daily usage.

But sadly the battery drain stays and also database i/o and storage i/o performance is very poor, not only benchmark scores (database: around 200 instead of 650). If I open an app that is not cached (like whatsapp after a reboot) the start takes veery long compared to previous builds. You really feel the lag...

The rest is amazing!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mangusZen:
and 4chan is there for a reason. Please try to behave and follow common netiquette forum rules.

While OP may be tollerant, he's not the one who decide when to show the Axe.
[Samsung Galaxy Nexus] Nephilim:
What settings are you using for I/O scheduler and RAB? I have had nothing below 600 for database and my storage i/o is about 870 to 1100.

Also, is this the new DirtyV osm0sis updated ramdisk version?

---------- Post added at 11:56 AM ---------- Previous post was at 11:55 AM ----------

Very true, I would love for us to be able to post whatever we like, maybe someone should open an official Google+ Community for that............
[Samsung Galaxy Nexus] Kustaa:
Everytime I reboot or power on my phone, it reboots itself again some seconds later of booted. Then Trickster shows a " Dirty reboot" message.

DirtyV 2/17, CM11, Neph settings (1200 max and stock voltages)
[Samsung Galaxy Nexus] Nephilim:
Do you let your device's screen turn off before it activates the custom settings by chance? I've found that sometimes with trickster mod on certain roms that if the device's screen is off when trickster tries to set the "set on boot" settings it will hot reboot.
[Samsung Galaxy Nexus] büscher:
Hmm... It doesn't matter what scheduler I use, tried it with bfq@256, fiops@768, sioplus@1280 this are the ones performing the best ond my phone normally.

And I'm using the "original" DirtyV from the OP since 12 hours now. Storage I/O varies from 450 to 800...

Also the scores depend on if I make a full antutu test or only storage performance. A full one I get worde database scores (~200) and "good" storage i/o (~900). If I only test storage performance i get both around 500 (strange tough).

But I ran antutu at least 10 times today, everytimes the same atrange results.

Sent from my Galaxy Nexus

---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------

Thats also becaue of the CAB settings.

Unlock your phone after a reboot and let trickster do its work.

But since I use init.d scripts this does not happen to me anymore.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
Have you tried out Noop? I actually ditched FIOPS for Noop recently after doing some testing for about 3 days on it. I do know that more than just you are having this issue with I/O on the latest builds, not sure what's causing it. For me I can do a benchmark and get one score and then an hour later get a completely different one, both off of a cool device. I too am on the most recent OP DirtyV.

I would like to try the osm0sis version but I'm having a pain in the ass time finding the post with the link lol.
[Samsung Galaxy Nexus] Kustaa:
Yeah, youre right, certainly if I unlock the device it wont happen.

But with some eariler versions of the kernel this doesnt happen...

Sorry for my ignorance but what is "CAB settings"?

Edited: you're totally right. CAB enabled: no more reboots
[Samsung Galaxy Nexus] büscher:
Will try noop this evening then and report tonight or tomorrow how it performs. Strange, I also always tested with a cool device...

Mh.. I just wanted to upload osmod for you, but apperiantly I deleted it...

Sent from my Galaxy Nexus

---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------

CAB = Content Adaptive Brightnes

Dont really know why it does this but I also had this issue on previous versions...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Here

http://xdaforums.com/showthread.php?p=50446420
[Samsung Galaxy Nexus] bsmitty83:
I got to set up my old versions so people can still download them , I'll try to add metalsprings versions and osmosis' as well .

Haven't really gotten any progress yesterday . I've been bringing most of the mm up . in current Linux kernel zram lives in drivers/block and everything that was in staging is now in mm or drivers/block . I think that's why database and io is low because I'm about halfway there , still gotta move zram . been stuck on this for a while . also I've been using a dirtyV with no memory reclaim and its just as fast efficient and handles just like bigmem or sr .

Really starting to believe the ram reclaim doesn't do anything really . o never get close to being out of ram . I always only use around 250mb of ram with zram on . it always stays there . never gotten it lower even with 30 apps open in the background or however many I can open at once
[Samsung Galaxy Nexus] ak:
Clean thread is the right way for a solid future. This a suggestion for make this forum every day the best place for fun and develop, and I want to propose myself to the moderator apply ... So "state in campana guys" .... ?

AK&4&7
[Samsung Galaxy Nexus] Kustaa:
Well Im using 480 mb on fresh boot lol
[Samsung Galaxy Nexus] metalspring:
The amount of ram everyone uses just varies on the rom, what apps they are using, how many apps, how they use those apps and how often they reboot

Some may really benefit from extra ram if they don't reboot often, use memory intensive apps, lots of apps that run background processes (for notifications), memory heavy roms (which usually are the ones with lots of features and theming), etc. But others may not need any extra ram at all, it just depends
[Samsung Galaxy Nexus] büscher:
I don't know much about kernel development and I really appreciate your hard work!!

Also I think more RAM is usefull with a featurefull ROM like CM-Remix (PaPIE, Halo, Omniswitch, Appbar etc.) so I'm very happy that you build kernels with RAM reclaiming! (Using 450MB as I write this and AppBar, Omniswitch and ZRAM are disabled atm).

Your kernel is a beast, really the best that could happen to my phone. I'm glad not having to buy a new phone because it does not cover my needs anymore. :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Same question for both you guys since I know you're both using the one from the OP: with or without the init.d scripts? If with, try removing them and rebooting and bench again. :good:

If you two work out some better settings I'll put them in the ramdisk. :)
[Samsung Galaxy Nexus] Kewyang:
Any idea why i have been facing freezing on CM remix? IM use 17 feb build SR version.
[Samsung Galaxy Nexus] Edward Stanbury:
yes it should boot on 4.3 roms as its in anykernel format :P
[Samsung Galaxy Nexus] Vekhez:
That's what I thought, but the 4.4 ROM's in the OP had me concerened, this does work on 4.3! Going to replace the 4.3 AK kernel that I am currently running :D
[Samsung Galaxy Nexus] Seraz007:
Working without any issues on CM-Remix 4.4
[Samsung Galaxy Nexus] Nemed:
This kernel is really fast, probably the smoothest i ever tried, but sometimes the phone freezes for a couple of seconds. I'm on CM11 using ART. Then i've got random reboots using the lower frequency (180MHz), but maybe my nexus just doesn't like it :D
[Samsung Galaxy Nexus] bsmitty83:
180mhz is always like that most devs got rid of it because it was too low so its not just you
[Samsung Galaxy Nexus] ken6336:
Touch control support?
[Samsung Galaxy Nexus] 3n3rg1c:
yes supported
[Samsung Galaxy Nexus] motorazrv3:
Which modul has to be selected?

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Its a setting in trickstermod app on the specific settings page . its aka doubletap 2 wake
[Samsung Galaxy Nexus] Ashtrix:
It would be of great help if i can get any mirror, can't download from here via dev-host, Thanks :good: !!
[Samsung Galaxy Nexus] bsmitty83:
Hers it is out of my dropbox

https://www.dropbox.com/s/jjg7tmzjlazkqki/Dirty_V-Linaro4.8.zip
[Samsung Galaxy Nexus] AbhishekS:
Woah! So you mean to say that's in-built in the kernel and we don't need the TouchControl/PGM app anymore? :eek:
[Samsung Galaxy Nexus] bsmitty83:
Correct I'm using it and I never downloaded any other app from gplay store
[Samsung Galaxy Nexus] atoyu:
If someone have boot problem when switch to art mode. I suggest flash the rom amd kernel first. Then switch to art. After that ,install gapps. Hope it help. This method without bootloop for me.
[Samsung Galaxy Nexus] 3n3rg1c:
Tried with trickster mod
[Samsung Galaxy Nexus] Gabboplano:
I got something like 5 freezes in 5 minutes with this kernel, stock Vanir's works fine

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] AbhishekS:
By never do you mean never on your kernel or actually never?

Because I cannot find it on Trickster. I'm using ASKP though.