yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] spupuz:
stefano how to solve that problem?
[Nexus 4 Original Android Development] ak:
waht problem?

i dont have problem with video.

i cant fix if i cant reproduce.

please make a more precise report.
[Nexus 4 Original Android Development] ak:
Added new section because it is impossible to handle problems without having the information, try to understand:

Q: How i can post the problems with kernel?

thanks to @ak:

- description
- how i can reproduce
- version of the rom
- version of the previous kernel
- version of the actual kernel
- last_kmsg
- kernel settings
- version of the app used for control kernel
- ecc ecc ecc
[Nexus 4 Original Android Development] Treatcon:
Are these valid with the new kernel XGenesis? Thank you for sharing your work!!
[Nexus 4 Original Android Development] ciano865:
I have flashed ak_uninstaller but now Wi-Fi do not start (CM 11 nightly).

May be I have to flash ROM again

Tapatalked with Nexus⁴ ° CM11 nightly ° ART enabled
[Nexus 4 Original Android Development] fishears:
Just reflash the CM nightly.
[Nexus 4 Original Android Development] DooshPastesh:
Delete it.

餃子 ?
[Nexus 4 Original Android Development] spupuz:
sorry stefano i realized that for error i flashed cm version over my omnirom :/
[Nexus 4 Original Android Development] sgs505:
I think if you were previously on a ak kernel with Prima Wi-Fi....

Then the correct uninstaller is the prima one...
[Nexus 4 Original Android Development] ciano865:
I've installed this one: AK.013.XGENESIS.CM.zip

and then used this: ak_uninstaller_mako.zip

I think is my mistake. Solved flashing new CM nightly.

Uninstalled because min freq seems locked to 918 instead of 384 and lower.

20% of battery drain with 45/50min of Screen On Time, usually more than 1h/1h15m with CM stock kernel and smartCover ON. I know short test.

So, sweep2wake works fine but too much battery drain for my use.

Thanks guys for all your work. ;)
[Nexus 4 Original Android Development] smoka206:
That is how the stock kernel works, and it has been asked and answered 100's of times...

You have to disable boost on mpdecison or lower the first core to the minimum frequency via trickster or other app.
[Nexus 4 Original Android Development] Volpine:
Love this version - re the battery drain issue, I've found CM11 seems to keep the cpu's maxxed out. Can't fix it. Tried loads of kernels so its a rom issue. No such issue running stock 4.4.2

Again Ak, the GPU overclock reduces performance on my device by a significant degree. This time I used 3Dmark to test it out which gave lower values than a standard N4.

Can I ask that you investigate the differences of your implementation to the one used on the Trinity Kernel for KK which **absolutely flies** when it comes to 3d work. The KK version clocks at 400 but it performs like 487 as it was on android 4.3 so I'm thinking the clock display is incorrect.

Either way the overclock is ineffective at this time...

Like I said, this kernel is great bar the GPU overclock :)
[Nexus 4 Original Android Development] sgs505:
@ak

Hi, even your new release is 100% recognized in Kcontrol ... will it be possible having the Sweep support like the bricked one ...

Otherwise cause I'm not really a a script kiddy ... I'm oblige to use trickster ...

And also... Is it possible to add 450 in GPU setting.. I see 400,487 and even 533 ! but no 450 ...
[Nexus 4 Original Android Development] ciano865:
Sorry I didn't find this info.

This is my stats of 1 our of general use with CM11 nightly and its kernel (set to interactive): about 76% of time at 384MHz, 1.2MHz 12%...
[Nexus 4 Original Android Development] sgs505:
Well apparently I was hoping too much when thinking i deserve at least sometimes an answer...
[Nexus 4 Original Android Development] Mercado_Negro:
Hi ak, hope you're doing fine. First of all, I must admit I've never used your kernel before but I've seen you're a SlimKat user. I've also seen you're using showp's hotplug driver as alternative which is also the case in SlimKat's kernel. Now, I've been searching this thread and I've noticed some people have experienced problems with clocks getting stuck at boost frequencies when using this alternate hotplug driver and I've seen the same on SlimKat's kernel. You've suggested that people should set boost to low frequencies or simply disable this but it's really intriguing to me why this is happening. Do you have any ideas why clocks get stuck after a few hours of usage or after sustained load like playing heavy games? It's a random problem and I've spent weeks trying to solve it but maybe there's something I'm missing. It doesn't matter if it's after a clean or dirty flash; it happens, eventually.
[Nexus 4 Original Android Development] hooliganx:
[MENTION=5087599]Mercado_Negro[/MENTION]

glad to see you here man. ;)

Im don't have this problem since I flash Slimkat.

Don't know why :D

N4*Slim.4.4.2-b2*AK.012XG*T49H*TWRP.2.6.3.3*0.98
[Nexus 4 Original Android Development] gorilla p:
This has now been brought up and addressed literally at least 20x in the past few weeks.

I don't expect everyone to go back and read through 20 pages of comments to find an answer, but I know I had recommended adding this to an FAQ area, due to this exact question about a month ago. This should be put under FAQ's on the main page.

What is showing as your minimum freq in trickster or whatever you're using, is not your minimum freq.

It will show as 9xxmhz because it is showing the current minimum as you are playing with your phone, which jumps to 9xxmhz because MP-Decision "boost" function is on. That is what MP-Decision does as soon as you touch the screen. I don't like it. A lot of people don't like it. So, to stop this from happening....

Open Trickster Mod

Select General Tab

Set Min - 384000 (or perhaps lower if available and should you desire)

Set Max - Whatever you want (I set 1.35GHz to save a little battery)

Select Specific Tab > [MP-Decision Control]

Set idle_freq to (whatever you want the minimum freq to be)

Set boost_enabled to "OFF".

This will disable the hair-trigger boosting of your CPU freq.

---------- Post added at 06:36 PM ---------- Previous post was at 06:15 PM ----------

Hey AK, I may be reading this incorrectly, but it looks like you enabled the option to OC the GPU to 487.5MHz and 533MHz.

Using trickster Mod, I am not seeing any OC options. GPU Max freq is 400MHz and the next lowest is 325MHz (instead of 320 which you usually have).

I don't overclock my GPU, so it doesn't make a difference to me, I just wanted to let you know in case it is supposed to be there, or to be corrected if I am not reading this correctly.
[Nexus 4 Original Android Development] Jazavchar:
I think what the people are saying is, not that Trickster shows 918 mhz or some other frequency as the minimum, but that the kernel itself gets stuck at that frequency and can't go lower. Happenes to me too, sometimes.
[Nexus 4 Original Android Development] Mercado_Negro:
You just actually have to disable touch boost to stop this from happening, that's all. Idle_freq isn't the min freq you desire but:

---------- Post added at 08:24 PM ---------- Previous post was at 08:24 PM ----------

That's it, precisely.
[Nexus 4 Original Android Development] gorilla p:
So I ran antutu benchmarks with the same stock settings with both the latest caf and kxp kernel. The kxp kernel won very slightly.

So I went back the the kxp kernel and I noticed elementalx appears to have been replaced with intellidemand.

Intellidemand should a have its own thermal controls so I disables mp-decision.

But I'm curious as to why elementalx was removed and if it will be added again in the future as it was received very well. It was great on performance and battery.
[Nexus 4 Original Android Development] ak:
For now i dont have an answer, im testing mpd with kcontrol, without install another app for modify kernel parameters.

i want to see if the problem appears.

if I will find a solution will pm you with the possible fix.
[Nexus 4 Original Android Development] tsiftsism:
Can you enable dt2w via Faux Clock? Application doesn't seem to have such a setting. I'm using it and i can only see a sweep2wake feature.

Swyped from my Nexus 4 with Android KitKat using Tapatalk 4
[Nexus 4 Original Android Development] ahepas:
Hi all... I'm running slimkat with AK kernel without problems... I didn't have with stock slimkat kernel either...
[Nexus 4 Original Android Development] hooliganx:
screen freeze for a moment, and turn off screen. after 10 sec, back to normal. Have to press power button a little.

have this in 012 e now in 013-XGen.

Syslog file:

https://docs.google.com/file/d/0Bx7LunsZQGdsVWtOU2VoYnI2Rkk/edit?usp=docslist_api

edit:

forgot to mention settings:

-60 undervolt

325 gpu

1 core min / hotplug slow / unplug fast / boost disable

deadline 512

s2w on

KControl app

N4*Slim.4.4.2-b2*AK.013XG*T49H*TWRP.2.6.3.3*0.98
[Nexus 4 Original Android Development] willybarca:
yep also I get screen freeze, no undervolt or overclock
[Nexus 4 Original Android Development] ak:
I have see the same, it isnt a screen freeze, there is a conflict into gpu drivers.
[Nexus 4 Original Android Development] hooliganx:
thanks [MENTION=3475639]ak.[/MENTION]

you are a great guy.

admire you, faux, slim team... and few others...

Making XDA a better place every day.

really thanks!

N4*Slim.4.4.2-b2*AK.013XG*T49H*TWRP.2.6.3.3*0.98
[Nexus 4 Original Android Development] poondog:
@ak

For flo, what's the difference between x-CM, xGenesis and the old xCrossing kernels? It seems patches and features are similar. Are the newer kernels based off newer CAF sources? I see some things are different like intelliplug vs mpdec, newer patches fpr intellidemand elenental gov etc.. Will help me decide whether to download sauce for xGenesis or xCM :)

Thanks, I think I might get off my bottom and compile for my flo, he's lonely ;)
[Nexus 4 Original Android Development] gorilla p:
Thats what I was trying to figure out earlier. I've been able to decipher the following...

xGenesis are all CAF based

KX are the regular KK kernels

KXP are the regular KK Kernels with Prima Drivers (But the 300+ ones appear to be using intellidemand governor instead of ElementalX)

Where I am getting confused is figuring out where certain features left and others came in.

While I prefer intelliplug over MP-Decision, MP-Decision appears to be the only option until the most recent KXP kernels. Then intellidemand is available, but intelliplug doesn't appear to be available via Trickster Mod. It also doesn't have the ElementalX governor.

Basically what I'm hoping to find is the following...

162MHz Min Freq

Intelliplug Thermal

ElementalX and/or Conservative governor

S2W/S2S

Sound Control.

It appears that this was all achieved with the KO256 kernel (loving it) , with the exception of intelliplug

But I may be wrong. I had asked a question a couple months ago and never received an answer.

I wanted to know if I am using this kernel and I disable MP-Decision, is there something else that is automatically enabled, i.e. intellidemand?

Any help with clearing this up would be greatly appreciated.
[Nexus 4 Original Android Development] Abd121:
Any idea why weak charge???

Not even games...

It happens with Spotify!!!

(and everything else)

Battery decrease WITH AC plugged in!,

Omni rom

Ak. KX.300
[Nexus 4 Original Android Development] Targaeryan:
Ok. Let me give it a shot...

You're right about the classification of the kernels. Ak figures that caf kernels offer better performance etc compared to aosp directly. So it was changed. Intelliplug was removed due to choosing show-ps mpdecision (from bricked kernel), as it offers full control of mpdecision. By disabling it, there's no other hotplug driver taking over as far as I'm aware so it'll run on all 4 cores. Intellidemand is just the governor, controlling frequency, load distribution etc, but it doesn't hotplug the cores here.

Since xgenesis just started, he is adding features. It does have s2w and s2s. Sound control I think it does as I can't access it since I haven't gotten the donate version of trickster yet. Xgen is also using showps thermal control.. More options than intellithermal as far as I can see.

Please correct me if I'm mistaken.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Don't report bugs unless you're using the latest version.
[Nexus 4 Original Android Development] Abd121:
???

What is the latest version (with full feature)
[Nexus 4 Original Android Development] RealSlimShadyMC:
311 of the standard branch, 13 of the xgenisis branch. Xgenisis is the only supported by AK.
[Nexus 4 Original Android Development] ska4fun:
I'm unable to use any colour profile (fauxclock, trickstermod) whith xgenesis kernels. This is normal?
[Nexus 4 Original Android Development] hooliganx:
no.

I'm using it.

N4*Slim.4.4.2-b2*AK.013XG*T49H*TWRP.2.6.3.3*0.98
[Nexus 4 Original Android Development] ska4fun:
Wich colour profile? I am able to control colour and gamma, but not load custom profiles, like obsanity and halbreed.
[Nexus 4 Original Android Development] atxbang56:
does anybody have a link for v311 please?

°°° KitKated from my Nexus 4 °°°
[Nexus 4 Original Android Development] hooliganx:
I already use this version. and 311XP too. and never have this issue with charge.

N4*Slim.4.4.2-b2*AK.013XG*T49H*TWRP.2.6.3.3*0.98
[Nexus 4 Original Android Development] Abd121:
After installing latest version!..... Same problem :eek:

BTW AC WAS plugged all the time
[Nexus 4 Original Android Development] ak:
Xgenesis is clean with all the necessary features ... I want to suggest this branch

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] ak:
Very strange can you use the 3rd post with "how to post a problem" please.

You have to collect dmesg when in charging.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] poondog:
thx, are you building cm and AOSP with the same defconfig?
[Nexus 4 Original Android Development] gorilla p:
Thanks for taking the time to respond. I had incorrectly assumed that intelliplug was included with intellidemand.

You mentioned that there is an mpdecision alternative in the new xgenisis builds? Is that setting available in trickster?

Im curious to see how the caf kernel goes. I like it in theory, but benchmarks rated it slightly slower than the standard kernel. Perhaps its improvements are in untested areas, but im curious to see a legitimate comparison.

I think I'll be ready for the fulltime switch once more features are added. If AK does what he usually does, I'm sure it will include 162mhz freq and another governor (preferably elementalx).
[Nexus 4 Original Android Development] Targaeryan:
No problem.

Yeah. Mpdecision control is present in trickster.
[Nexus 4 Original Android Development] drinkypoo:
I got discharge with pc connection, but not power only.
[Nexus 4 Original Android Development] Bladyle:
Hello,

I'm about to test this kernel but right now I'm using stock ROM with stock kernel and from what I see your poll is only for AOSP and CM. So is there any users using this kernel over stock ROM? Do you think it will be a good combination ?
[Nexus 4 Original Android Development] themike10452:
Yes this kernel works with Stock ROM go for it. Are you looking for battery life or performance?

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6 KK Linux 3.4.0 kernel.
[Nexus 4 Original Android Development] Bladyle:
Thanks. My first priority is battery life. Actually i like the performance and stability of stock kernel but I miss some of advantages of custom kernels like UV, custom gamma settings and others thats why I'm searching for good alternative of stock with some more features.
[Nexus 4 Original Android Development] Reed-Sternberg:
My priorities are very much like yours and so far after testing all kernels, my choices are either AK or matr1x. Excellent battery life and very good performance with both. If you decide to flash this one, try the setting the man himself suggested a couple of pages back for battery, you'll get insane battery life (I'm on 48 hrs with 4hrs SOT with light usage).
[Nexus 4 Original Android Development] Stygmatik:
Hey there !

I was using AK Kernel with the Project Kitkat rom from GNOME (the dev name on xda) and everything was fine.

Now, I'm using the latest Paranoid Android 4.0 Beta from 23/12/13 (4.4 KK) and I'm now using the latest AK Kernel with CAF/xGenesis stuff and I get bootloop.

Any idea ? Because Paranoid Android is based on AOSP so the kernel should work, no ?

Thanks by advance !
[Nexus 4 Original Android Development] Targaeryan:
Did you download the aosp version?

Did you clean flash PA and then xgen or you flagged xgen on top of another kernel?
[Nexus 4 Original Android Development] Stygmatik:
I did clean flash PA yesterday. Everything was running nice. And now, I'm flashing xgen on top of it, after wipe Dalvik/cache.
[Nexus 4 Original Android Development] themike10452:
deleted
[Nexus 4 Original Android Development] willybarca:
you don't have to flash kernels everyday, ak has more stable versions aswell which gets updated in a slow pace, I think you should use fauxkernel he is the most innovated developer and his kernels are the most stable, the only reason I use ak kernels is that he combines all the good feature of every kernel into one,
[Nexus 4 Original Android Development] Stygmatik:
So nobody here is using latest PA Beta with the latest AK kernel ? :confused:
[Nexus 4 Original Android Development] Marsou77:
Hello everyone !

I've to report some BSOD (Black Screen Of Death) with xGenesis 013. I use stock value.

I'm alone ?
[Nexus 4 Original Android Development] johnb380:
Thanx for the bug report but In the future u must follow AKs guide to posting bug reports first you need to get a last_kmsg And upload it to your fav file sharing site (Dropbox, G Drive, etc.) and then post The link with Your setup such as, ROM version, build date, kernel version basically any settings changed from stock setup the dev has laid out for u

Sent from my Nexus 4
[Nexus 4 Original Android Development] Targaeryan:
Try dirty flashing the ROM and then xgen kernel with no wipes.
[Nexus 4 Original Android Development] IRX120:
On 013 I'm getting an issue where the touch screen won't work when I wake the device. After a min or so I get a freeze and reboot

Here's the kmesg

http://pastebin.com/G7QYDDVS
[Nexus 4 Original Android Development] xjcook:
I'm using latest Ak with PA Beta without any problems :)

Try reflash ROM.
[Nexus 4 Original Android Development] nokiagye:
OK gyes let's begin the lesson. If you have immediately power off bug look at the volts or reflash the kernel. If you open the phone you must work it for 2 minutes before you lock it or you I'll have the unresponsive screen problem, if you open it and you don't touch it and it lock by it shelf again the screen will won't work. Sometimes we change something on trickster on faux on kcontrol after the first reboot maby will work fine but if you set settings on boot you must be carefully.

Is not always kernel problem!
[Nexus 4 Original Android Development] ak:
After reading old post i have see good and bad comment, but sometimes this is part of xda and a thread with developing.

I now understand what was said long ago in the thread of the PSX rom.

The problem is that there are too many critics and few facts, too many users that claim but do not contribute.

We can all take a source, add four patch and then say this is the best kernel.

I could make some changes every now and publish a kernel per month but with what purpose.

Thank you very much.

ak
[Nexus 4 Original Android Development] ak:
@themike10452

very bad post, I would not have expected from you.

I think now its the time for migration.
[Nexus 4 Original Android Development] themike10452:
sorry man for being too honest :P keep up the good work.

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6.1 Linux 3.4.0 kernel.

---------- Post added at 12:15 AM ---------- Previous post was at 12:08 AM ----------

@ak do you think CAF is a better performer than AOSP? I've been using your latest xGen 2 days ago with BeanStalk Harmony ROM and the thing I was most worried about which is Camera Video zoom bug is no longer there on CM kernels. So is your kernel based on CM or is it AOSP+CAF commits? I still don't understand this CAF thing. I might be going back to CM when I find a good rom. CyanFox looks promising :fingers-crossed:

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6.1 Linux 3.4.0 kernel.
[Nexus 4 Original Android Development] ak:
No comment.
[Nexus 4 Original Android Development] ak:
The problem of the camere was related to camera pack itself not the kernel.

This kernel is based on cm = caf. the only difference for make it working on aosp roms are 2 commits. thats all.

And 'useless that we continue to denigrate the work of cyanogen, at this time is better than any other on the Android market.

In fact, many developers do not admit it but most of the commits that matter are taken from the work done by CM.
[Nexus 4 Original Android Development] themike10452:
appreciated. *post deleted btw*

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6.1 Linux 3.4.0 kernel.

---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------

hmmm weird. While I was on CM with CM kernel the camera bug was there, but when I used franco or faux kernel + CM commits by ziddey the problem was not there :what:

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6.1 Linux 3.4.0 kernel.
[Nexus 4 Original Android Development] ak:
NB:

this isnt true because i have personally tested:

caf kernel = cm based = camera work on:

- stock rom

- slim rom

- cyanogen nightly
[Nexus 4 Original Android Development] ak:
Do yuo have post the problem on the right thread?
[Nexus 4 Original Android Development] themike10452:
What I said was two month ago, in fact 2 days ago I checked for it again and the camera was working fine on CM kernel.

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by Piasek v6.1 Linux 3.4.0 kernel.
[Nexus 4 Original Android Development] ak:
So at this point what is the problem?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] sgs505:
can we answer also ? or try too ?

@ak

hope i didnt send you kms making wrongly investigate when on 309__311_312

but i notice i didn't follow one rule

NOT enabling both d2tw & s2 ...

it was a major cause of issue ... at least for me...

Perhaps writte the sentence bigger and in red ...

+ wishes or words about it ?

From my point :

* Prisma Wifi = cost less battery ...more often signal weaker (don't know if there is a way to log & see)

*miss Intelidemand 5.0 wich apparently disappear since new standard to fit in

Also i had to uninstall Trickster Mod+FauxClock+Franco to use only kControl if i want to be sure nothing unexpected could happend ...

miss the c0/1/2/3 states control ... makes a huge difference for battery consuption
[Nexus 4 Original Android Development] themike10452:
No problem at all :D
[Nexus 4 Original Android Development] sgs505:
A last one [MENTION=3685904]ak[/MENTION] you should quote your advice at the beginning too like the baterry savings settings in kcontrol Kind of kcontrol ak preset ... Till akcontrol ;)

Otherwise it will be lost for so many in the sea of news posts

Ams those tricks are good
[Nexus 4 Original Android Development] nudou350:
I couldn't find the "screen on off" stuff..did you find it on kcontrol?
[Nexus 4 Original Android Development] sgs505:
Not so sure but think he was talking about the use only one core when screen is off option...

At least that's what match the more his words ... :p
[Nexus 4 Original Android Development] ak:
OP updated

Q: How i can have battery saving profile?

thanks to @ak:

I want to suggest for battery life:
- open kcontrol
- set interactive as default governor
- undervolt all -25mv
- set min core 1 max core 2
- under mpd set hotplug slow
- under mpd set unplug fast
- set brightness to auto
- make one time screen on/off with power button