yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ChazzMatt:
Over in Franco kernel thread,

he did speed tests and Westwood TCP won every time

. (see chart below) And AK uses it as default, probably for that reason. It's proven to be fastest, most efficient. (Westwood is actually Westwood Plus, if you go researching; it's not the original "Westwood")

Now, schedulers -- yeah, your preference. :) Especially with the new "winning tunable" scripts implemented.

---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------

Yeah. osmosis and Franco dev team put in months on those "winning tunable" scripts. AK has given full credit of course,

even in the Franco kernel thread,

And now

at least one other kernel team

are using those scripts. It's a revolution. :)

I do like how AK is using the latest 3.4 Wi-Fi drivers, letting WEP die the death it deserves. Using AK kernel (with newest wi-fi drivers) integrated with the Franco dev team scheduler "winning tunable" scripts seems to be the best of both worlds for right now.
[Samsung Galaxy Nexus] ak:
New patch for wep is present into new kernel.

Can you confirm that wep work now?
[Samsung Galaxy Nexus] ak:
Do you use purity ROM or atom?

Carbon ROM for me no problem.
[Samsung Galaxy Nexus] ak:
Its impossible ... Because v70 have the same 3.4 drivers
[Samsung Galaxy Nexus] frenchy714:
Looks like he's on Atom v12. I'm also on Carbon (4/13 nightly) and have no issues.
[Samsung Galaxy Nexus] slyd0997:
Turn off backup in settings. Fixed sleep for me.
[Samsung Galaxy Nexus] 93foxgt:
Once again ill say I'm using atom v12 with 83 on toro with no problems at all. No freezes, lags or sod. Running excellent. Thank you again anarkia1976.
[Samsung Galaxy Nexus] vlc_marcos:
i have a question to you guys.

am i the only one that has 3d quite slow?

last kernel and the rom is the slim bean 1.15 version
[Samsung Galaxy Nexus] ak:
Slim bean from des franco?
[Samsung Galaxy Nexus] vlc_marcos:
yes
[Samsung Galaxy Nexus] ak:
I have tested it with old kernel version and no problem for me.! :good:
[Samsung Galaxy Nexus] vlc_marcos:
yes me to. with the 81 version was ok. i will wait for the new kernel to come. thanks
[Samsung Galaxy Nexus] ak:
Have You problem with gaming?
[Samsung Galaxy Nexus] vlc_marcos:
well in the game hungry sharcks is quite laggy. so after done the the antutu test i saw the reason, the 3d is very bad, normally i get more than 2000 and now i get less than 1000
[Samsung Galaxy Nexus] ak:
Ok I'm making a test with carbon in this moment for compare the difference!
[Samsung Galaxy Nexus] ak:
CARBON ROM:

ANTUTU 3D = 2100 points :D

No problem with kernel! :fingers-crossed:
[Samsung Galaxy Nexus] Tex99:
v83 no problem. also wi drop seems to be solved now ;)

what do you think about carbon ? you are on last nightly with memory leak fix ?
[Samsung Galaxy Nexus] vlc_marcos:
ok. so it was something from the rom or some appl. :D

thanks
[Samsung Galaxy Nexus] ak:
Yes last nightly and work like a charm! ;)
[Samsung Galaxy Nexus] sk8oldschool74:
Has Color changed???

I guess not but am going to test the rest of the kernel... ;) :)
[Samsung Galaxy Nexus] SahilC:
Thanks! But then I wouldn't get a screen off profile, right? :( I thought it would help to force it to under clock when screen off?
[Samsung Galaxy Nexus] mainicia:
I got random reboot on ak.457.berserk (4.1)

Does anyone happened too?
[Samsung Galaxy Nexus] mohaimed:
did anyone use both zen and ak kernel?? can anyone tell me which one is better in terms of performance and battery life??
[Samsung Galaxy Nexus] mainicia:
I think ak is better in performance and battery is both the same.
[Samsung Galaxy Nexus] ak:
Have anyone tested bluetooth with new 4.1 v457 kernel? :cowboy:
[Samsung Galaxy Nexus] pcphobic:
Prior to using AK, I was on Zen. It caused me some freezes at that time when I was on Xylon 006. Then I gave AK kernel a try and never looked elsewhere again.
[Samsung Galaxy Nexus] ak:
Preupdate release for 4.2.X:

3.0.55 + bluetooth drivers update

Changelog:

https://github.com/anarkia1976/AK-berserk/commits/ak-berserk-4.2-experimental4

Kernel Version: ak.457.42.berserk - Bluetooth Update

http://www.androidfilehost.com/?fid=9390214368362233994
[Samsung Galaxy Nexus] Vladivid:
Thanks! :good:
[Samsung Galaxy Nexus] ak:
new kernel

Project name: AK KERNEL 4.2.X

•anarkia1976 - Kernel Version: ak.457.42.berserk

•anarkia1976 - 3.0.55+ Linux

•anarkia1976 - Bluetooth drivers Updated​
[Samsung Galaxy Nexus] welingtonhs:
and the version pgm?
[Samsung Galaxy Nexus] ak:
.... lost or no lost .... :good: next days ... :cowboy:
[Samsung Galaxy Nexus] Exostenza:
If you tell me how to do it I will!
[Samsung Galaxy Nexus] ak:
AK wiki is your way ... First Page :thumbup:
[Samsung Galaxy Nexus] Nicuz95:
Damn, I can't flash AK everyday! hahahahaha
[Samsung Galaxy Nexus] ak:
A new release tonight ... stay tuned :D

I'm kidding ... I think I'll retire ...:p
[Samsung Galaxy Nexus] ciprianruse88:
retire?...no way :fingers-crossed:
[Samsung Galaxy Nexus] Nicuz95:
hahahahaha

By the way maybe is Off topic, can I ask what is your build environment? Ubuntu 12.04? :)
[Samsung Galaxy Nexus] SahilC:
Just wanted to let you guys know.. Been messing around with some scheduleres and governors..

For me, nothing is as smooth as interactive + deadline..

Battery is okay, but even Xda is a super smooth
[Samsung Galaxy Nexus] thommy86:
just flashed the v83 kernel,, I've got a great wifi stength, but internet is really slow.. every app using internet is really slow.. any ideas?
[Samsung Galaxy Nexus] sergini:
Like in said in the end of my post, I use atom.
[Samsung Galaxy Nexus] ak:
Try to change your rom.
[Samsung Galaxy Nexus] ak:
No problem for me ... change westwood to cubic and verify.

Every AP or ROUTER are different.
[Samsung Galaxy Nexus] Teemoo:
I can't use usb-otg with v83 but I can with rubik v3 and cm stock. It says usb is blank and doesnt mount it. cm latest nigtly.
[Samsung Galaxy Nexus] ak:
I cant verify, you have to post logcat and infos for the problem .. i dont have cable. :fingers-crossed:

Beta testers on g+ dont report problem with otg.
[Samsung Galaxy Nexus] sergini:
So, diamond version 80+ and atom aren't compatible?

Cuz 70 works great., I'm using it.
[Samsung Galaxy Nexus] ak:
I don't know ... I can't verify why you have problem .... Post all the infos ... Maybe kernel problem maybe ROM problem ... :rolleyes:
[Samsung Galaxy Nexus] Teemoo:
here is a cat. hope it helps. fat32, formatted with win7, tried multiple usb sticks.
[Samsung Galaxy Nexus] savagehax:
I love this kernel.. So much.. I'm also about to get a nexus 7 soon and was wondering if this kernel or anything from ak existed for that device?
[Samsung Galaxy Nexus] Javicii23:
Anarkia, I've found a pattern of errors when i use the recent menu and appears the artifacts.

<3>[14154.419403] omapdss DISPC error: VID3_FIFO_UNDERFLOW, disabling VID3
<3>[14154.419555] omapdss DISPC error: GO bit not down for channel 0
<3>[14154.463470] omapdss DISPC error: SYNC_LOST, disabling LCD
<6>[14154.476043] ignoring apply mgr(lcd) while blanking
<6>[14154.492828] ignoring apply mgr(lcd) while blanking
<3>[14177.969635] omapdss DSI error: rx fifo not empty after write, dumping data:
<3>[14177.970245] omapdss DSI error:	rawval 0x17000202
<3>[14177.970428] omapdss DSI error:	ACK with ERROR (0x2):
<3>[14177.970764] omapdss DSI error:	SoT Sync Error
<3>[14177.970947] omapdss DSI error: dsi_vc_dcs_write(ch 1, cmd 0xf7, len 2) failed

These errors always shows when I use the recent application menu with diamond v80 and v83. With diamond v70 this problem doesn't appear.
[Samsung Galaxy Nexus] jjlyons:
No problems with atom and v083 on my end :p
[Samsung Galaxy Nexus] frenchy714:
v83 stock settings. Going to change the gov to wheatley this cycle.
[Samsung Galaxy Nexus] tetrakinitis:
Can someone post a screenshot with the interactive governor tunables? Thanks!

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] MaLiXs:
Work fine here with stickmount and 16gb microsd and his adaptor

Send from my Pure Ak GNex
[Samsung Galaxy Nexus] DoesntPostAThing:
I can confirm that USB OTG doesn't seem to be working with v83. StickMount will mount it to /sdcard/usbStorage/sda, where usually it would go to sda1. Not a big deal I think. Anyway, Once I open up that folder, it's empty. However, USB mouse and keyboard work fine. I also checked the same flash drive on my S2 running PACman, all files are viewable just fine.
[Samsung Galaxy Nexus] jeffcavicchi:
Hoping someone here can help me. All of a sudden Trickster is causing hot reboots for me when set on boot is enabled. Seems independent of setting changes. If I have the screen on when Trickster settings kick in I am OK, but if the screen is off the phone reboots. If I uninstall Trickster, everything works fine. I am not changing anything significant - just lowering the max voltage, turning on FFC, changing the color profile.

This only started recently - after the last update of Trickster and the change to Diamond V8x versions. I am running Diamond V83 on the latest version of Atom. Happens on the latest version of PA as well - I am switching back and forth between ROMs to try to figure out what is going on.

Any ideas? I'd love some help - I brought my phone right back to the stock image and deleted all internal storage to try to resolve the problem, with no luck.
[Samsung Galaxy Nexus] slayr76:
I have the exact same issue with screen freeze an constant rebooting at startup with set on boot with trickster, if i physically touch screen during startup after rebooting it stops it from boot looping over an over though which is weird, if i just let phone reboot by itself an don't touch it, it will just keep rebooting, been using ak kernel with atom rom.
[Samsung Galaxy Nexus] jeffcavicchi:
Thank God someone else has the same issue (although I am sorry for you) - I thought I was going crazy! If you don't mind, please post something over on the Trickster thread - they think I am crazy over there.

What ROM are you using?
[Samsung Galaxy Nexus] mrdevil_25:
I had the same issue with reboots being boot looped. What i did was uninstalled trickster reboot into recovery then reflashed v83. let it do its thing and then reinstalled trickster and then set it up from there. havent had problem since.
[Samsung Galaxy Nexus] slayr76:
Lol i thought it was kernel related but it been happening with atom rom with ak kernel 080 - 083 for me, definatetly not kernel or rom related because i remember trickster app was updated not long ago an its been happening ever since then.
[Samsung Galaxy Nexus] manardrs.jb:
My settings don't stick after reboot with trickster using 83 w latest carbon nightly
[Samsung Galaxy Nexus] lesp4ul:
Check your init.d scripts, clear trickster data and flash AK again :)
[Samsung Galaxy Nexus] chikimonke:
Also, don't Greenify Trickster, not sure why, but it screws up its ability to set on boot.
[Samsung Galaxy Nexus] manardrs.jb:
Cool thanks
[Samsung Galaxy Nexus] jeffcavicchi:
Worked like a charm - thank you so much!
[Samsung Galaxy Nexus] LostSoulFly:
Took me the longest time to figure out why I couldn't get to 180mhz, even though I was setting it. Turns out, there is a default screen-on min CPU speed, but nobody is talking about it and I didn't have anything set up to enforce that, which threw me off.

Got BBS and saw that my phone was going to 180 at some point, skipping 230 entirely. Well, that's a good clue. I concluded that it had to be some kind of profile somewhere, but I had SetCPU disabled entirely and couldn't find anything about profiles in the performance settings.

Got Trickster MOD finally, after being confused for hours and searching this thread like crazy, I found the setting that controlled it.

Getting amazing battery life with this and AK83: 71% after 13h. Not much screen on time (20mins, 7 mins of netflix on wifi, 10m of voice calls), but I just want my phone to last through a day and a half or two with light use.

Sakuractive, 180 min screen off, 350 max screen off, lowered min screen on to 230, multicore power saving set to 1.

Very pleased with XenonHD, been using it for a while, has its ups and downs but overall the best I've used on any device. <3
[Samsung Galaxy Nexus] strifej:
I had boot loops as well. I didn't notice if I touched it or not to get the boot loop to stop, but going ot try the suggestion below to uninstall trickster mod then reinstall after v83.

Thanks
[Samsung Galaxy Nexus] slayr76:
Uninstalling trickster, reflashing ak v83 kernel an reinstalling trickster an enabling set on boot didn't change a thing, still get endless boot loops unless i physically swipe screen a few times while phone settles after rebooting, even turning off set on boot doesn't fix the reboot problem, only uninstalling trickster mod app altogether fixed it.
[Samsung Galaxy Nexus] akira02rex:
I set my delay on trickster to 60sec all the time and it seems to work.
[Samsung Galaxy Nexus] marcusva79:
How long should I wait after flash the newest nightly? I have plenty lag running the latest carbon nightly.

Never had issues before. Also when updating nightlies I should normally do rom-gapps-kernel-music mod....correct? After a full dalvik cache wipe. I have done that and my phone gets really hot.
[Samsung Galaxy Nexus] manardrs.jb:
Tried everything still can't get trick settings to stick

Has to be the ROM never had this problem before on any other
[Samsung Galaxy Nexus] stevensoaj:
Sounds like your Color Adaptive Brightness. If something (such as an init.d script) sets it on or off on boot, and then trickster reverses that when its settings are applied, then it causes the behavior you described. Make sure CAB is on the same setting everywhere its applied. :thumbup:
[Samsung Galaxy Nexus] ak:
Can you try to disable rotation for the lockscreen?
[Samsung Galaxy Nexus] ak:
http://comments.gmane.org/gmane.comp.handhelds.android.porting/16025
[Samsung Galaxy Nexus] marcusva79:
Well I installed cm10.1 nightly and its no lag that I see. Must of been carbon.
[Samsung Galaxy Nexus] ak:
http://www.reddit.com/r/Android/comments/1cb0y2/systemui_memory_leak_causing_422_lag/

Fantastic

Cr88 you are famous
[Samsung Galaxy Nexus] DoesntPostAThing:
Thank you cr88, you not only fixed my lag issue, but got me a ton of upvotes.

Sent from my Paranoid Galaxy Nexus powered by AK Dummy Kernel
[Samsung Galaxy Nexus] Bosio91:
I must have missed this, but how much memory should SystemUI be taking up if working correctly?

Thanks :)
[Samsung Galaxy Nexus] kaluoshi:
To @anarkia1976. My friend I uploaded new Rubik kernel, please update op :D
[Samsung Galaxy Nexus] ak:
Ohh Yeah!
[Samsung Galaxy Nexus] ketann:
I keep getting this message in logcat

E/Tuna PowerHAL( 576): Error opening /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq: Permission denied
E/Tuna PowerHAL( 576): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device

I tried fixing permissions in twrp.

Clean installed slim+ diamond v83
[Samsung Galaxy Nexus] ak:
This isnt a problem .. is normal.
[Samsung Galaxy Nexus] Soundigy:
Wif testi: Westwood vs Cubic

I have 100mbit connection, and I have tested westwood vs cubic, with speedtest.com app.

Im getting this results:

[B][U]Westwood[/U][/B]:

Test Date: Apr 15, 2013 8:54:03 AM
Connection Type: Wifi
Server: Nis
[B]Download[/B]: [I]9.46 Mbps[/I]
[B]Upload[/B]: [I]9.92 Mbps[/I]
Ping: 106 ms

[B][U]Cubic[/U][/B]

Test Date: Apr 15, 2013 8:50:42 AM
Connection Type: Wifi
Server: Nis
[B]Download[/B]: [I]18.86 Mbps[/I]
[B]Upload[/B]: [I]18.67 Mbps[/I]
Ping: 78 ms

* With stock Kernel and ROM I'm getting about 22MBit/s upload/download.

Device: Gnex

ROM: Purity 5.3

Kernel: AK Diamond v083
[Samsung Galaxy Nexus] sajty:
I read in franco thread,that cubic should be faster than westwood (overall the fastest).
[Samsung Galaxy Nexus] Soundigy:
I know. This is just to prove that ;)
[Samsung Galaxy Nexus] ak:
I have revert from cubic to west only for verify drops ...but now I'm sure this isn't kernel problem
[Samsung Galaxy Nexus] bunnahabhain:
Yeah, i wanna know too... mine is at 59mb constantly with newest CM 10.1 nightly!
[Samsung Galaxy Nexus] alangrig:
Have different results:

Cubic:

Download: 4,522 kbps

Upload: 6,975 kbps

Ping: 100ms

Westwood:

Download: 3,989 kbps

Upload: 9,566 kbps

Ping: 88ms
[Samsung Galaxy Nexus] BriVG:
Something goofy there, download should be faster than upload...
[Samsung Galaxy Nexus] alangrig:
Corporate strick policy amendments for download.
[Samsung Galaxy Nexus] Butter Smooth:
Was a few days off, but thanks for all advices on the PowerAmp stuttering issue!

In the meantime, I flashed v83 (and the latest CM10.1 nightly) and reset all kernel settings. This time, I reduced the RAB to 128 (this seems rather small, but I haven't found any disadvantages of it) and I haven't touched the voltages. Now running fiops+interactive, and the PowerAmp stuttering issue has gone (meanwhile, I'm investigating some new drain problems, but I think they're more CM10.1/app related). Thanks all!
[Samsung Galaxy Nexus] BriVG:
I see, learn something new every day :)
[Samsung Galaxy Nexus] musashihatred:
But i think i believe cubic is the fastest.

Cubic processes data faster but at small intervals at a time while westwood handles bulk data at long intervals. This produces different latency and ping. So i think, westwood is good for downloading large files while cubic is good for surfing ang streaming.
[Samsung Galaxy Nexus] MBQ_:
OT:

No more laptop for me. :D

On topic: v83 is running great for me.
[Samsung Galaxy Nexus] ak:
new v090 stay tuned

New version is NEAR:

https://github.com/anarkia1976/AK-tuna/commits/ak-4.2.2-exp23

Fix OTG

Add Hyper

Fix Dynamic Fsync

Revert to CUBIC

a lot lot lot of fck fixes ..... :D
[Samsung Galaxy Nexus] Godra:
Cant wait.. :fingers-crossed:
[Samsung Galaxy Nexus] MBQ_:
You are the BEST. :)
[Samsung Galaxy Nexus] ak:
Your thanks meter grow faster every day .. people love you and your work MBQ.

Thanks a lot.
[Samsung Galaxy Nexus] MBQ_:
Same to you bro!

You deserve all the love and donations you get. You're so knowledgeable, kind, and take the time you have to help your users. On top of that, you're a humble person and eloquent speaker. We're all more than thrilled and honored to have you here as a kernel developer on XDA man. :)
[Samsung Galaxy Nexus] Hetalk:
Both you guys are pretty nice. Now stop this OT and thank this post, so I can get close to your numbers. :D
[Samsung Galaxy Nexus] kekko986:
WiFi direct - superbeam

Anyone have problem with wifi direct using SuperBeam app??:confused:

I'm on CM10.1 M3 with AK83..if i flash old drivers wifi direcr works well...but i can t use hotspot wifi anymore..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] MBQ_:
Okay. ;)
[Samsung Galaxy Nexus] ak:
thanks

Thanks to ALL ak team and users here with the support for fix all problems! ;)
[Samsung Galaxy Nexus] ak:
Have you reflashed cm kernel?

you have to revert with OP script.

I dont have merge IBISS support ...
[Samsung Galaxy Nexus] kekko986:
I dont remember... If i do a clean installation i will solve the problem? Or i have to use OP script to flash AK?

I usually flash in twrp

1.Cm10.1

2.Ak kernel

3.Reboot

4.titanium backup restore

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] frenchy714:
Thanks Anarkia for your tenacity! Will the new release have Osmosis's tweaks baked in like 83?
[Samsung Galaxy Nexus] ak:
always osmosis inside :good:
[Samsung Galaxy Nexus] ak:
Have you flashed cm def kernel?
[Samsung Galaxy Nexus] kekko986:
No..i only flashed ak...i need to flash cm-stock too?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] frenchy714:
:D:D:D
[Samsung Galaxy Nexus] alangrig:
Anarika1976,

Is there any solution to remove general system lag when uploading huge files like 500mb-3gb to Google Drive for example? General system lags happens on every ROM and every kernel while Google Drive prepares for uploading file for instance.

Or this problem specifically is app related?
[Samsung Galaxy Nexus] ak:
Why have you flashed this:

I'm on CM10.1 M3 with AK83..if i flash old drivers wifi direcr works well...but i can t use hotspot wifi anymore..

Do you want IBISS support?

What is the OLD wifi drivers?
[Samsung Galaxy Nexus] kr3g3r:
im loving the idle drain on AK83!! ...... idle drain is what always drove me nuts on all the phones ive had .... being at work 12-16 hours and sometimes having a dead phone without even using the darn thing

this is the best version of AK for me so far
[Samsung Galaxy Nexus] Javicii23:
I have this option disabled.:(
[Samsung Galaxy Nexus] dizzy1k:
LiquidSmooth with Ak v83 all you'll need! just try :eek::cool:
[Samsung Galaxy Nexus] ak:
new kernel online

4.2.2 DIAMOND ED. (EXPERIMENTAL)

androidfilehost - Last Version: AK.099.DIAMOND.zip

dev-host - Last Version: AK.099.DIAMOND.zip

Differential Changelog: Link

Features: Link

Github: Link

Project name: AK KERNEL

•anarkia1976 - Kernel Version: AK.099

•anarkia1976 - Linux 3.0.74

•anarkia1976 - tuna_ak_defconfig: Rework for WIFI 3.4 Compatibility

•anarkia1976 - bcmdhd: Enable Ad-Hoc (IBSS) mode interface flag and avoid some P2P specific settings while scanning.

•anarkia1976 - cpufreq: Add Hyper governor

•anarkia1976 - tuna_ak_defconfig: Enable MSDOS_PARTITION - Break OTG

•anarkia1976 - Revert "tuna_ak_defconfig: Enable Default WESTWOOD"

•anarkia1976 - Revert "net: wireless: bcmdhd: Fix WEP-104 authentication"

•anarkia1976 - bcmdhd/Makefile: Remove -DUSE_IW

•anarkia1976 - Revert "netfilter: xt_qtaguid: Allow tracking loopback"

•anarkia1976 - Revert "net: loopback: set default mtu to 64K"

•anarkia1976 - tuna_ak_defconfig: Disable Big Stack Frame Warning FRAME_WARN=0

•Steve Kondik - cpufreq: interactive: Enable CPU utilization statistics

•Paul Reioux - dynamic filesync: add some cache optimizations - Thanks Faux and Tiny

•Andrew Bartholomew - fs/dyn_fsync: check dyn fsync control's active prior to performing fsync ops

•Steve Kondik - cpufreq: interactive: Fix uninitialized spinlock
[Samsung Galaxy Nexus] boki2911:
You're indestructible:good:
[Samsung Galaxy Nexus] kaluoshi:
bro i was reading the diff changelog, have you fixed WEP with 3.4 drivers? :D
[Samsung Galaxy Nexus] gautam_nexus:
Will you not let my phone take a breath? I flashed Rubik 5 like a couple of hours ago and now you are out with v99! :banghead:
[Samsung Galaxy Nexus] ak:
I think! :cowboy:
[Samsung Galaxy Nexus] marcoperro74:
Ste .. Just to know ... Have had you my little appreciation for your work? Sorry if it's not much ... As soon as I replied ;) thanks for everything!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ak:
A present from you is always a "big Present" for me. Thanks a lot. :good:
[Samsung Galaxy Nexus] marcoperro74:
Di niente... È sempre un piacere... ;)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sajty:
There are 3 sure things on planet Earth:

1) tommorow will be sunshine again

2) my salary is terrible

3) my phone is not able to settle down,because new version of kernel will be sooner
[Samsung Galaxy Nexus] un.droid:
it feels like 99 is much faster than 83. using hyper governor and my phone feels like a rocket. thanks!
[Samsung Galaxy Nexus] butikofer08:
This is diamond v99, previous public release was v83. Rubik is another kernel by ak.
[Samsung Galaxy Nexus] alangrig:
PGM works?
[Samsung Galaxy Nexus] ak:
yes and no .... :D
[Samsung Galaxy Nexus] qu4nd:
Kernel supports PGM, but PGM has to support kernel ;)

So in A's words: "Yes and no" :D
[Samsung Galaxy Nexus] sajty:
I cannot say,that "much faster",but i can feel small difference too.v83 was slightly slower than the previous one,but v99 looks perfect again.
[Samsung Galaxy Nexus] marcoperro74:
Yes it works... But if pgm don't work isn't kernel problem but is pgm that must be updated... On the playstore there is the link for say to pgm's dev that need an update... ;)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] MBQ_:
99? Score. :D
[Samsung Galaxy Nexus] kaluoshi:
:D i'll try to set modem to WEP when home and will report bro :thumbup: