yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DoesntPostAThing:
Just realized I didn't. After I did, Franco seems quite smooth though. I'm thinking of changing some settings around in AK v20 (best one for me) to reach the same smoothness. Does Franco still hardcode GPU to 512?

EDIT: Can confirm, same settings as Franco 372, runs a lot faster on AK, at least on my device. I'll post the settings later/tomorrow after I further polish them and put them under some testing/benchmarking (speaking of benchmarking, AK performs better than Franco in AnTuTu)
[Samsung Galaxy Nexus] Blackcrx:
Looking at that screen shot it looks to be lean kernel
[Samsung Galaxy Nexus] abalam:
By Diamond v063 I have come to a firm decision. I was all the time to switch between Franco and your kernel, but after the last experimental kernel I crown you the winner. Personal decision. The battery drain is something more as V062 but we know you, you will solve the issue hehe. PGM also works like a charm. With a word AWESOME KERNEL!!!

TNX man for you hard work
[Samsung Galaxy Nexus] MBQ_:
Aw snap. ;)

#Oldschool
[Samsung Galaxy Nexus] ubabic:
I revert back to AK v044...I think that v063 is better considering performance but battery drain is horrible. Last night my battery was at 98% at the moment when I went to bed. In the morning it was at 89% after just 5 hours of sleep. All my data and sync options are off as always, and i know that none of the apps is causing wakelocks because I use the same configuration as before...I know that DIAMOND is experimental kernel but it can't be good for daily use. This morning i have used my data on 3G to read some new stuff on xda as usual, also little bit of FB and local news but battery went down to 50% very quickly. I know that anarkia is going to fix it soon so only option is to wait something better... :cool: Anyway thank you for your hard work!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 93foxgt:
Funny as i am using the same kernel currently. Runs awesome.
[Samsung Galaxy Nexus] adambala:
yes yes yes.......rubik is so sweet....cpu at 1060 cpu screen off 350 uv all at -25.......
[Samsung Galaxy Nexus] MBQ_:
Great minds think alike. :D
[Samsung Galaxy Nexus] TheMysteriousOne:
Nice.

I went to diamond v33 a few hours back. It had the most awesome battery life for me. (5hrs OST)

Let's see if I can hit the mark again. :)
[Samsung Galaxy Nexus] zandander:
I've been going between 44, 37, 63, and 20 about every 4 hours lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gummie:
Just like mine, been trying around Kernels again since PGM has been updated but I keep coming back to Cylon v801. I jumped to Diamond v063 because I saw that Voltages on steps are reverted to Cylon's digits but results are surprisingly not as good as Cylon. Maybe has something to do with my Kernel setup on Cylon v801 :laugh:
[Samsung Galaxy Nexus] TheMysteriousOne:
37 and 44 had WiFi drops as far as I can remember.

Try sticking to diamond v33 or Cylon 801 and let it settle.
[Samsung Galaxy Nexus] zandander:
That's the odd thing. I've never, and I mean never, had a Wifi drop lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] alangrig:
I'm on v44 for now. During business hours all time Wi-Fi. No drop issue at all. Stable.
[Samsung Galaxy Nexus] Butter Smooth:
For me, the WiFi icon turned grey sometimes, but the connection always worked.
[Samsung Galaxy Nexus] zandander:
Odd about the wifi drops.. Well anyways, just flashed v33 and gonna let it settle and see how it runs tomorrow when I get up.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TheMysteriousOne:
You have never seen a grey icon after turning your screen on?

Just for the sake of clarification, when I say WiFi drops, I am referring to drops when the screen is off.

Grey indicates that there was a drop when screen was off.
[Samsung Galaxy Nexus] ak:
I have used for sometimes last leankernel exp.

Have anyone tested MPU IVA COR min calibrated voltages and can explain how it work?

I tried but it seems that SR still calibrates below the threshold.! :confused:
[Samsung Galaxy Nexus] Muvolt:
Last Diamond v63 is slower than v44 with Slim Bean (build 3)...
[Samsung Galaxy Nexus] LauraSakura:
I've been getting SoDs pretty often lately. running diamond 44. Anyone have any ideas on how to troubleshoot this? I'm not changing any kernel settings, I leave them pretty much at default (except I turn on high quality sound). I'm also running PGM, if that matters. Thanks
[Samsung Galaxy Nexus] MBQ_:
Cool story.
[Samsung Galaxy Nexus] ak:
Dont use pgm.

Dont use 180 230 slot.

Raise voltages MPU +25.

Read OP Guide.
[Samsung Galaxy Nexus] ak:
question

I have a question for all:
[Samsung Galaxy Nexus] frenchy714:
This screen shot was taken while on Lean 6.3.1 stable.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
Ok can you try to undervolt MPU to 810 and set MPU Min Calibrated Voltages to 830?

SR stop calibration to 830?
[Samsung Galaxy Nexus] differentstyles:
I'm using the stable Kernel Rubik since yesterday and for the moment I'm totally happy with it also because of the xlouder patch. Sorry if it's the wrong thread but I wanted to show my respect also for the stable modified version.
[Samsung Galaxy Nexus] frenchy714:
I've tested and it works on Lean but automatically +10 mV on top of the calibrated setting (if set to 830 mV the min. MPU SR voltage will be 840 mV, if set to 840 mV the min. MPU SR voltage will be 850 MV, and so on and so fourth).

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
I have tested with exp version and i verify calibrated voltages with trick but its lower than MIN VDD.

Can you try this, please?

Mpu Min Calibrated Voltage = 830

180Mhz Voltages = 805/810

For me trickster show:

805

For you?
[Samsung Galaxy Nexus] frenchy714:
Confirmed working (see screen shot). I uv'd to 810 mV and has the calibrate MPU SR set to 830 mV.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
No my friend ... you have calibrated to 810mv ... the third value from right!

Is this right?
[Samsung Galaxy Nexus] frenchy714:
I did as you asked. I manually set my 350 step to 810 mV and had the MPU SR set to 830 mV. When the MPU set value is lower than the MPU SR calibrated value, your phone will always choose the lower value.

Is this not what you asked me to do?

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
Yes, is this normal at this point, right?

Do you have a link where Imoseyon explain this please?
[Samsung Galaxy Nexus] frenchy714:
Forgive me but I'm not sure I understand your question.

I'll see if I can find anything fr Imoseyon on MPU SR calibration settings.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
g+

From G+ Chicago.
[Samsung Galaxy Nexus] AutomaticFailure27:
For those having lag, try enabling "force gpu rendering" in developer options. It feels smoother and from what I read, possibly save some bettery since it is taking the load off of the cpu.

For me, v63 is running the best any ak kernel has. It has given me the best battery to drain yet, although I have a typically "faster than normal" battery drain since I have pgm, tasker, lux, and lightflow, constantly running in the background, but nothing to severe.

Give it time, it's going to space!
[Samsung Galaxy Nexus] ak:
I have resolved lag problem .... now i have a test kernel and i'm verifying in this moment the idle drain! stay tuned!
[Samsung Galaxy Nexus] thegtfusion:
Ak, v63 is awesome but the battery life js horrible. I lost 15% overnight (8 hours) with wifi and sync on... No apps running in the background. Is there still a problem with sio?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] cubsfan187:
You are a machine!!!
[Samsung Galaxy Nexus] ak:
Have you tried others scheduler?

Drain is a known issue. you can use v44 or Rubik.
[Samsung Galaxy Nexus] jreyno10:
Switching from sio to fiops fixed idle drain for me.
[Samsung Galaxy Nexus] pik1:
drain on v63 but not on v62...
[Samsung Galaxy Nexus] thegtfusion:
Known issue. Its already fixed in the next version ;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] butikofer08:
I thought gray wifi bars had something to do with the Google servers, not actually if your connected to the web. Mine are gray sometimes when i turn my screen on but they turn blue shortly and internet works no matter the color of the bars. Isn't it normal for the OS to do this. ( i have the keep WiFi in sleep option turned off in trickster)

Are you saying you have to reconnect to a network?
[Samsung Galaxy Nexus] TheMysteriousOne:
How exactly did you conclude that ' internet works no matter the color of the bars'?

No need to enable WiFi high performance in trickster.

If you are having drops in older kernels versions, try disabling WiFi optimization in settings->WiFi>advanced.
[Samsung Galaxy Nexus] elmexicanoalto:
Rasbean + AK Rubik 3 is the best combo of all time. I've never experienced something so smooth and fast since an iPhone haha
[Samsung Galaxy Nexus] TheMysteriousOne:
Battery drained like a river as soon as I switched to fiops on diamond v33. Switched back to sio.

Just saying.

Waiting for AK to release his fix. :)
[Samsung Galaxy Nexus] catanzaro27:
I have diamond v63 at the moment. Do i have to do something if i want to swich to rubik kernel or i can just flash over?
[Samsung Galaxy Nexus] pik1:
i know, just wanted to report... sorry
[Samsung Galaxy Nexus] sajty:
Yes,you have to read OP,you can find everything here ;).
[Samsung Galaxy Nexus] butikofer08:
So when you have a drop your saying you have to go into WiFi settings and reconnect, correct?

Never had a WiFi drop then if that's what your talking about....
[Samsung Galaxy Nexus] buggerthis:
The grey WiFi bars do just mean not connected to Google's servers. I've done stupid **** like forget to flash gapps after a ROM flash sometimes, and the internet works after that but the bars just never turn blue.
[Samsung Galaxy Nexus] catanzaro27:
Thank you! What's your personal recomandation? 63 or rubik? I search for stability mainly and something faster than stock.
[Samsung Galaxy Nexus] irminsul:
No, it's really something else. Grey bars all the time = not connected to Google services (or Talk, as I remember), but the issue I experienced all the time on Franco or Lean was when after I woke up my device, WiFi was reconnecting, resulting in an 'H' or '3G' icon, quickly changing to grey WiFi, and after a second or so, blue WiFi. Or just grey WiFi signals quickly changing in normal blue bars. It happens so often that I really can't remember when it didn't occur.

The effects of it are hard to measure, but it's easy to conclude that constantly reconnecting to WiFi is draining your battery (battery life sucked balls on my device, even more worse than the all ready worse battery life on maguro, I topped 2h of screen on time during 10 hours of standby at the max.)

I used ak 63 for a day, and not a single WiFi drop occured, but battery drain overnight was too huge for stable use for me. I cleaned my rom, changed back to MMuzzy's and flash ak 44, and idle drain at work WiFi is superb (2 hours of moderate use at office WiFi (10 minutes screen on) and just lost 3%, with the first our 0% just idling).

It has to do with the WiFi drivers/patches, because most other kernels don't use them. Glad I finally fixed this on my device!
[Samsung Galaxy Nexus] ak:
Rubik is your way if you want stability! :D
[Samsung Galaxy Nexus] TheMysteriousOne:
Can someone verify whether grey bars signify WiFi drop or something else?

The way I know it is that if you see WiFi bars as grey after unlocking screen after it's been idle for a while, it means that WiFi connection was dropped.

I don't think it has anything to do with Google servers.

Ak verified that there was WiFi drop in some of the recent kernel versions and I think I think it was fixed in v44 or v63 as AK said himself.
[Samsung Galaxy Nexus] sajty:
If grey bars means WiFi drop,problem was not solved in 044 either 063 for me.Bars are grey always when turning screen on and from time to time when screen on too.
[Samsung Galaxy Nexus] ak:
Turn off wifi opt.

Turn on wifi high perf.

and verify.
[Samsung Galaxy Nexus] AutomaticFailure27:
Grey = WiFi connection to an access point. This

MAY

include internet access but,

it also may not.

Blue = WiFi connection with communication to Google Sync servers which means you definitely have internet.

What I see for "wifi drops" is that the wifi icon disappears completely, then comes back on. Hasn't dropped since I

re

flashed v63.

Also, when I initially flashed v63, I didn't do my normal wipe cache/dalvik before/after flash. That's when I noticed my wifi acting funky and dropping signal. Reflashing with wiping cache/dalvik cleared everything up. There was also a setting on my router for DTIM that I changed from 1 to 255, which before v63 caused no issues, but after lowering that down to 3, wifi signal stays and also less "Are you there? communication" between my phone and my router.

I flashed AOSPA

without

gapps and still was able to connect to the internet, use Facebook, Reddit, basically everything except Google services (Play Store, Gmail, Search)

When I did that, I noticed the icon wasn't blue like it normally was. After flashing gapps, the icon changed from grey to blue and all the Google services started working again.

Found this bit of information doing a quick Google search. This is from Page 27 of the official Android 2.3 user guide (Same rules apply for ICS+) :

Network status icons turn green if you have a Google Account added to your phone and the phone is connected to Google services, for syncing your Gmail, Calendar events, contacts, for backing up your settings, and so on. If you don’t have a Google Account or if, for example, you’re connected to a Wi-Fi network that is not connected to the Internet, the network icons are white.
[Samsung Galaxy Nexus] MBQ_:
Rolling with Cylon 801, 0407 cm nightly, and have 2/3 of the animations at .5x, man. This is fast. Here are some screenshots: (sorry if it the picture is waay too big) if my screenshots are too large, I'll take them down so they're just attachments, :)
[Samsung Galaxy Nexus] jcmm11:
No. Gray means that you lost connection to Google services. That's all. Connection is still fine when gray.
[Samsung Galaxy Nexus] Droid-21:
Dev host, does not work in several countries, please upload to another server kernels.
[Samsung Galaxy Nexus] tattedupboy:
I've given up all hope of ever getting decent battery life on this phone, but at least with the newest version of this kernel, combined with MOST of nephilim's settings, I'm finnaly seeing consistent smoothness and no SODs or or lagginess.
[Samsung Galaxy Nexus] MBQ_:
If you've read other pages, it has been noted 063 has drain issues. Please revert back to an older kernel that you've had success on for the time being. You can also get a 3500 or 3800 (I forget) MaH battery on Amazon for 32$ USD with 3-5 day shipping, and you will notice your battery lasting 1.5-3 times longer than before.

---------- Post added at 08:27 AM ---------- Previous post was at 08:23 AM ----------

Wipe cache

Wipe dalvik-cache

Flash the kernel

Fix permissions

Reboot

Let the phone sit for ~5 minutes

I'm excited! :D you in project Chicago?

Please elaborate next time. :)
[Samsung Galaxy Nexus] TheMysteriousOne:
Out of curiosity - why would the connection with Google's sync servers be lost?

Yep. :)
[Samsung Galaxy Nexus] MBQ_:
This sounds silly, and its a long shot, but, try a different browser? :)
[Samsung Galaxy Nexus] SahilC:
Just wanted to add that I went back all the way to v19 from 63, and everything is much faster. :)

Sent from my Nexus Prime powered by AK goodness!
[Samsung Galaxy Nexus] MBQ_:
To my (sometimes lacking) knowledge, when the connection color isn't blue, it means it isn't being used

I could be wrong though. It happens. :cool:
[Samsung Galaxy Nexus] tattedupboy:
Nothing new for me. Every ROM and every kernel I've ever tried has yielded poor battery life for me.
[Samsung Galaxy Nexus] MBQ_:
Do you clean flash?

And, try different settings bro. Every phone has a magic elixir of kernel settings. :good:
[Samsung Galaxy Nexus] irminsul:
Why would one wipe the dalvik cache and fix permissions after flashing a kernel?

It's useless, makes the first boot take way longer.

We should ban this fairytale from Android land.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] tattedupboy:
I never dirty flash and I never restore old app data from Titanium backup (apps yes, but not app data). Believe me when I tell you, I've tried every possible combination of settings I can think of, and I can never get good battery life.
[Samsung Galaxy Nexus] Droid-21:
androidfilehost - Last Version:

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

Differential Changelog: Link

help me with another server?
[Samsung Galaxy Nexus] MBQ_:
-_-

I wonder if its your battery.

Didn't you just ask this? According to XDA rules, don't ask the same questions in an XDA thread more than once in 24 hours.
[Samsung Galaxy Nexus] Blackcrx:
Not to throw out any hate or disrespect, but I also went back to 43 and everything is smooth as can be
[Samsung Galaxy Nexus] MBQ_:
It isn't disrespectful. Sometimes, kernels dont work well with phones. :)

In example, some people has 0 lag with 062, and I had bad lag, even after raising my Voltages, and messing around with CPU stuff. It is what it is though. :) I'm rolling with cylon 801 now and having amazing results!
[Samsung Galaxy Nexus] Blackcrx:
disable animation completely and change duration to .5x

then sit back and hold your phone tight...

edit: does anyone have the download link for cylon 801?

I only have the diamond series kernels left on my phone since I did a clean up
[Samsung Galaxy Nexus] MBQ_:
Its too weird for me to do that, I kinda like the animations. Like, I know it makes the phone feel even faster, but I prefer a little bit of animation :)
[Samsung Galaxy Nexus] Blackcrx:
Totally agree. But sometimes the problem with internet is that comments can be taken the wrong way depending on how to read it. I just didn't want to offend anyone
[Samsung Galaxy Nexus] MBQ_:
So true. :good:
[Samsung Galaxy Nexus] sajty:
Yes,its completly useless,but i do it everytime :D
[Samsung Galaxy Nexus] ak:
name: AK.801.CYLON.zip

type: Kernel

size: 4.4MB

md5: bbcf05a0722cf477e642f3db99bcf8cc

url: http://www.androidfilehost.com/?fid=9390355257214632219 link

desc:

3.0.69

You can use link into OP with the old files repository.
[Samsung Galaxy Nexus] ak:
Im uploading now v063 on filehost
[Samsung Galaxy Nexus] ak:
4.2.2 DIAMOND ED. (EXPERIMENTAL)

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

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

Differential Changelog: Link

Features: Link

Github: Link
[Samsung Galaxy Nexus] irminsul:
So why do you do it? I'm to impatient to wait for something that's completely useless.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Blackcrx:
Thank you sir

I have tried the links in the OP. "AK Kernel 4.x old"

Android host is down or unreachable from Canada

Dev-host only has Diamond and Purity: http://d-h.st/users/anarkia1976/?fld_id=0#files

Please correct me if I am looking in the wrong place
[Samsung Galaxy Nexus] sajty:
Really dont know,probably for good feeling :D.But cache and dalvik (should) has nothing to do with kernel.
[Samsung Galaxy Nexus] MBQ_:
Yep!!

For me, its more force of habit :)
[Samsung Galaxy Nexus] Blackcrx:
this may sound stupid but is this a new diamond 63 or the same as the one posted a couple days ago?

I checked the change log and github, all shows as April 6th
[Samsung Galaxy Nexus] ak:
Link work well for me.

http://xdaforums.com/showpost.php?p=31785054&postcount=1349
[Samsung Galaxy Nexus] marcoperro74:
I have tried the last exp whit interactivex governor and the phone is laggy....whit normal interactive the phone is smooth...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] arifqur:
Same here
[Samsung Galaxy Nexus] ak:
can you share log file located in:

/data/ak-boot.log

please :good:

with cm10 interactivex works well, what are the roms?
[Samsung Galaxy Nexus] TheMorpheus:
I've experienced a couple of sleep of death with the last exp
[Samsung Galaxy Nexus] ak:
logcat

dmesg

/data/ak-boot.log

for troubleshooting ...

with 066 no problem?

do you use interactiveX?
[Samsung Galaxy Nexus] arifqur:
I am using the sep19 cm10 nightly.

I only used the interactivex for a little while then switched back to interactive so the log won't help
[Samsung Galaxy Nexus] rebretz000:
I may be in the minority but I'm not having any issues with the latest experimental kernel using InteractiveX
[Samsung Galaxy Nexus] lippol94:
Hey Anarkia :)

you got a PM ;)

EDIT: LOL just got your reply :p
[Samsung Galaxy Nexus] marcoperro74:
I reboot the phone after change governor in interactivex...this is the file requested

The rom is miui jb...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renaud:
Miui busybox is missing some basic commands or some links.
[Samsung Galaxy Nexus] marcoperro74:
And is there a solution for busibox?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ak:
busybox

try to copy from cm10 to miui ... and reboot ... :D
[Samsung Galaxy Nexus] renaud:
If you don't put the correct links, that won't work.
[Samsung Galaxy Nexus] gianton:
I notice the lag with InteractiveX running latest 067 exp and CM10, no lag with Interactive.
[Samsung Galaxy Nexus] Xerodark:
I had one this morning,.. running the latest exp 067 with interactivex. I haven't had it happen again though. Other than the single time, its been running super smooth.
[Samsung Galaxy Nexus] rebretz000:
I just had that. Was wondering if it was the kernel or ROM.
[Samsung Galaxy Nexus] mpokwsths:
Using v067. Great performance. Faster response than v064.

Interactive only. Why use interactiveX? Interactive also turns off the one core when not needed...
[Samsung Galaxy Nexus] Stylez Ray.:
I thought my Gnex was perfect but then I flashed this kernel..awesome work you did here!
[Samsung Galaxy Nexus] ciprianruse88:
Tested too.not trickster fault
[Samsung Galaxy Nexus] djjonastybe:
Changing governors is a waste of time. ;) keep interactive. it's the best.
[Samsung Galaxy Nexus] ak:
Yes you are right ... but if i do this ... is no longer so important to play with the kernel .. i can install another from another develpor ... and bam problem resolved ...

If you have any help or trouble

would be greatly appreciated. :victory:
[Samsung Galaxy Nexus] ak:
No ....
[Samsung Galaxy Nexus] lordofcamster:
What's wrong?

:)
[Samsung Galaxy Nexus] ak:
:D nothing my error .....
[Samsung Galaxy Nexus] GCbard:
Just curious then, what is the best way to use interactive with 455? Does 448 have the problem in interactive where it is locked in the highest cpu setting unless you switch from ondemand?
[Samsung Galaxy Nexus] ak:
Kernel version v448 don't have the problem with interactive. :angel:
[Samsung Galaxy Nexus] Exostenza:
Ok well the battery was draining VERY fast this morning until I read this thread and it seems I was stuck at 1200mhz using interactive and moving to intellidemand fixed that issue right away. Not a big deal atm tbh if intellidemand is a good governor! :)
[Samsung Galaxy Nexus] albsat:
@anarkia

What is your evaluation about the rom?

Glad to hear some opinion from an expert like you.
[Samsung Galaxy Nexus] ak:
I personally use xylon because its into constant evolution and im feeling happy with this! :D

Cm10.1 isn't official for now and i prefer don't use it. :rolleyes:
[Samsung Galaxy Nexus] Nicuz95:
And Xylon is also one of the best and most customizable AOSP ROM 4.2, I'm using it too :D
[Samsung Galaxy Nexus] ak:
For the problem with v455 I'm working for a solution.

For now i have disable screen off conservative features with this the next release will be all the ak governors: lazy Wheatley interactivex and more ....

Stay tuned :eek:
[Samsung Galaxy Nexus] Nicuz95:
I read the previous page but I don't have bugs, maybe is because I use intellidemand and not interactive
[Samsung Galaxy Nexus] ak:
Yes guy :D