yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] amarb70:
I've asked thus in a not so busy thread and haven't really got a suitable answer so I thought maybe I would over here.

"I don't understand something, I used this kernel for a large amount of time and liked it loads but am now looking to test another.

For some reason, I flashed the ak prima uninstaller zip and flashed the 4.4.2 stock kernel but still don't have any WiFi, like it's the "turning on WiFi" message. I thought flashing the zip would fix this. Any idea? :)"

Yes I know a dirty flash would be the way to uninstall the drivers but then again why does the ak uninstaller zip exist?:S

I've tried looking for an answer but found no luck. Apologies if this has already been asked before.

...sent from space
[Nexus 4 Original Android Development] maxver0:
The thing is with default settings it applies first setting (918MHz) to all cores instead of each specific one - using trickstermod along with ak 070.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] Gallardo994:
It would've been ROM's problem if it didn't drain only with AK kernel.
[Nexus 4 Original Android Development] ak:
I never see screenshoot or batterystat so ... the problem for me is incosistent.
[Nexus 4 Original Android Development] ak:
2 solution:

- dirty flash rom

- manually copy backup into this dir "/system/vendor/firmware/wlan/prima/"

WCNSS_cfg.dat_bck -> rename WCNSS_cfg.dat

WCNSS_qcom_cfg.ini_bck -> rename WCNSS_qcom_cfg.ini
[Nexus 4 Original Android Development] ak:
the info for mpd are here from the begin:

Hotplug:

bricked hotplug mdp (Link)

intelliplug (Link)

so please stop with polemics.
[Nexus 4 Original Android Development] maxver0:
I have already read that. But we can't set individual freq for individual core? Then What's the point with these different freq in mpdecision boost when only the first one applies to all other cores?

It's a bit unclear for me. I have read this explanation and i still don't understand.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] ak:
Probably the governor overwrite hotplug boost.

ak
[Nexus 4 Original Android Development] fbousk:
hi ak thanks for this great kernel are you working for an update for nexus 7 2013 one?
[Nexus 4 Original Android Development] maxver0:
It happens with ondemand as well as with interactive :(
[Nexus 4 Original Android Development] lightninbug:
download links not working in op? need the uninstaller.zip
[Nexus 4 Original Android Development] gorilla p:
You can download it from bit.ly/makostuff
[Nexus 4 Original Android Development] 0.0:
Just experienced a freeze, but not reboot. My phone went back to normal after. Mpd off, intelliplug on, intellidemand

I am hoping the new update fixes it :)

Edit: I saw the fixes on your github, so I will wait on that to see if it works

Sent from my Nexus 4
[Nexus 4 Original Android Development] kufikugel:
Guys reading the last 10 pages and not one bugreport which is useful. Not details no logs nothing. How do you guys expect that a developer can solve this? Cristal ball?

Did some time ago a post on PA community.....below the link....think about it.

https://plus.google.com/107859134357373490612/posts/cL6VfFN1D8R
[Nexus 4 Original Android Development] TheDarkDefender:
Wow. You are everywhere! [emoji1]
[Nexus 4 Original Android Development] Utkarsh-ezzo:
Really this guy is awesome, even when he was having a mako he was the first person on earth to have KITKAT running on maguro, he released 1st build for public just on the next day when google released source code...
[Nexus 4 Original Android Development] Benjamin_L:
I can also confirm power drain in 103. Android OS in top, same rom and using v70 it isnt. How can i help to provide more info?
[Nexus 4 Original Android Development] TheNerd:]:
Wow I've seen you in the pa thread and now here! .... Anyways I hope your family problems and financial issues have been relieved. Good luck to you sir
[Nexus 4 Original Android Development] Methroix:
I've had a couple of freezes where the phone becomes completely unresponsive but then gets back to normal by itself, if I have the patience to wait.

I'm sorry, but I have no logs to share, but I'll give as much info as I can.

As far as I can recall all of my freezes have occurred when I have the keyboard up and am typing. It has happened in Textra SMS, Dolphin Browser and GNotes.

The shortest freezes lasted for maybe 5-10 seconds, the longest for perhaps 2 minutes.

Although I have had freezes lasting longer than 30 seconds where I didn't wait for the phone to sort itself out.

These happen running standard voltage, UV 50mV and UV 100mV. Fast binned CPU.

Governor: Intelliactive

Intelliplug activated.

MPDecision, scroff and boost deactivated.
[Nexus 4 Original Android Development] tvisforme:
Yes, I'm having the same issue. It seemed to start with 80. We have two N4s, one is still on 63 and doesn't have the problem. I even did a factory reset on my phone but the problem came back.
[Nexus 4 Original Android Development] sidnoit22:
AK Linux 3.4.86 is out! ;)
[Nexus 4 Original Android Development] spupuz:
?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] themike10452:
He's telling AK that a new Linux version was released.

Sent using my nexus⁴ running Purity 4.4.2 KVT49L (Dalvik) powered by hellscore b45kk Linux 3.4.84 kernel.
[Nexus 4 Original Android Development] ak:
New release is under testing .... Probably out tonight. Stay tuned.

ak
[Nexus 4 Original Android Development] joefso:
get back to work ak to produce something worthy
[Nexus 4 Original Android Development] tvisforme:
Anyone else have issues going to the latest CM nightly? I went from the 4th to the 6th, using the same AK v103 CM kernel and the same Gapps, but ran into issues with Theme Provider crashing repeatedly.
[Nexus 4 Original Android Development] 0.0:
You should go to the CM discussion thread for this question. I assume you flashed a CM nightly? Reflash ROM without AK to see if it's a kernel problem or not

Sent from my Nexus 4
[Nexus 4 Original Android Development] Darkmasterhk:
Just tried "EXP v.103" and noticed some issues:

1) already read this but anyway: can't connect to wifi.

2) CPU goes berserk, on default settings all cores @1,5GHz

3) Two times touch didn't work for me (HW-Key does) (sadly no log :/)

Did I do something wrong?

Flashed it on slimkat build 4.

Even tried wiping /system /cache.
[Nexus 4 Original Android Development] FrozenLord:
I tried to compile your kernel on Ubuntu and although some work, I am missing WiFi in the newer versions.

I compiled 070 by accident, which seems to work just fine - including WiFi.

When compiling 112 (Prima) and 127 (non-Prima) however, the kernel will boot and seem to work fine, but I can't enable WiFi...

Is there anything that I need to take care of?

(I only cloned your anyKernel, AK-linaro, the main branch, the experimental branch and the experimental prima branch).

The only thing that is missing, as far as I realized by checking the output of your script, is the kcontrol_gpu_msm - but I don't need those GPU settings it exposes.

@ak: it would be great if you could give me a hint, as to what I might be missing :)

Thank you.
[Nexus 4 Original Android Development] unknown_2:
the new experimental, battery drains like crazy.

even though minimum core speed is set to 81MHz, but it spike between 700 - 900, sometimes spike all the way up to 1.9GHz (idle).

tested it last nite, left my nexus 4 idle with data off & wifi off.

it drains 5% battery over the course of the nite without even touching the phone.

p/s, wanted to try the stable built, but your site is down again.
[Nexus 4 Original Android Development] xenyz:
I've found that the Nexus 4, while 'idle', still uses more CPU than 81 MHz can deliver. Certain governors, like semaphore's ondemand, are pretty good about not ramping to max freq, while most others are not. You have to find a min freq with which your CPU/governor can handle the device's 'idle' load. This is probably different depending on your ROM and your usage.

Generally, I've found setting cpu0 to ~160-200 MHz and cpu1-3 to lower frequency is a good trade off.
[Nexus 4 Original Android Development] unknown_2:
seems like this kernel is not working well with CM11

previous post, the setting is using inteldemand .

i try switching to demand, it has got worst with core0 pretty much dead at 1.9GHz, while the other cores sleep.

CPU usage is up-to 50-60% idle.
[Nexus 4 Original Android Development] xenyz:
Run this command to ensure it's actually 'idle'

top -m 3 -n 3

You'll find your device is always up to something. I put idle in quotes for a reason. Is anything using more than 5-10% CPU?
[Nexus 4 Original Android Development] unknown_2:
looks like something is up.

it shows 18%, 19%, 17% on the 3 runs.
[Nexus 4 Original Android Development] xenyz:
Does it have anything to do with the kernel?
[Nexus 4 Original Android Development] unknown_2:
majority of the usage is system.
[Nexus 4 Original Android Development] hoangtungst:
Can dt2w kill the touch screen ?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Rohit02:
Yes, provided you double tap using a HAMMER.. :P :D

It wont harm the screen mate but would drain battery upto some extent.
[Nexus 4 Original Android Development] Sp_Ark:
If you mean that it doesn't respond to touch, then yes. This happens If you set to auto load such setting after each boot (with an app like trickster) plus sometimes mine is not responding even after deepsleep.
[Nexus 4 Original Android Development] TheRebel:
Sorry if this is a stupid question. Which governor u mostly use with AK kernel?

And i have seen GPU frequenc going to very low level 27MHz, why it goes to such a low level when in all other kernels (including stock) the minimum goes to 128MHz. This 27MHz min compromises performance?
[Nexus 4 Original Android Development] FrozenLord:
Edit: AOSP only. There is currently NO Intelliplug included.

I finally managed to get the kernel working :D

(Turns out I had missed the Prima files in anykernerl's directory...)

If anyone would like to give this highly experimental kernel a home, feel free to try.

However, the usual disclaimer applies:

...warranty void if used...not responsible for impregnated cats or world war III...have fun :)

It's a direct clone of AK's git, the version on git would be 127.

I've replaced the Prima driver with the latest stable one for Kitkat (according to Qualcomm), which is this one: https://www.codeaurora.org/cgit/qui...e&id=a59b1f7686bbe0fb9b2eb10651665300c310bc1e

According to this document, the 2.7-branch is the latest for our SoC (marked as apq8064 in this document, which seems to share its WiFi driver with the dual core variant, the msm8064).

Additionally, it was compiled with the toolchain on AK's git - "4.8.3-2014.03.20140318.CR83" to be precise.

So far it's working fine and my WiFi works as well ;)

It's an anykernel flashable ZIP - like the genuine AK stuff.

UPDATE:

Have a look at the more recent posts to get Intelliplug and a slight chance of a hang-free kernel (I am still testing that :) )
[Nexus 4 Original Android Development] 0.0:
Is it the aosp version? If so, could a cm version be made?

Sent from my Nexus 4
[Nexus 4 Original Android Development] jmtjr278:
Works great. I can't seem to find intelliplug. Any idea? Thanks for making this though
[Nexus 4 Original Android Development] TheNerd:]:
[MENTION=1577473]FrozenLord[/MENTION] I'm not so sure [MENTION=3685904]ak[/MENTION] wants his personal testing kernels being released before they are ready because if these builds are faulty, users will come crying back to him even though the problem is not necessarily his fault.
[Nexus 4 Original Android Development] FrozenLord:
[QUOTE='TheNerd:][MENTION=1577473]FrozenLord[/MENTION] I'm not so sure [MENTION=3685904]ak[/MENTION] wants his personal testing kernels being released before they are ready[/QUOTE]

Duh, that's what my disclaimer was for...

just kidding :P

This thread has seen some kernel versions compiled by users, and so far AK didn't seem to mind.

If he changes his mind, for whatever reason, I am happy to take the file down.

The file is only AOSP.

There is a CM-branch in AK's Git, but I am currently running AOSP and am therefore unable to test whatever file my VM spits out.

(I vaguely remember that there haven been problems with some of the more recent builds for CM as well, which makes this endeavor too risky IMHO)

I'll have to check about that.

In AK's Git it seems to be present, so either I screwed up while building (pretty unlikely, as it is a straightforward process thanks to AK's script), my VM is missing some dependencies (I have not seen any errors...), it is actually disabled,...

Those are just too many possibilities for the time remaining today.

I'll try to find out tomorrow where Intelliplug got left behind.
[Nexus 4 Original Android Development] jmtjr278:
hey [MENTION=3685904]ak[/MENTION] when i try to build your kernel using the ak-mako-build.sh script it builds version 63. did i do something wrong? i thought i synced with the 127 git. thanks for all you do.
[Nexus 4 Original Android Development] poondog:
You need to switch to nightly branch

git checkout nightlies

Or whatever its called
[Nexus 4 Original Android Development] FrozenLord:
TL;DR: Below is a build that contains Intelliplug and a working WiFi driver.

All disclaimers apply, it's still an unofficial and highly experimental build!

Et voila, I am fresh out of ideas...

The file is there (like in AK's Git), it's added during the building phase and yet, neither Trickster nor FauxClock detect any Intelliplug.

Has anyone got any nice ideas, as to why this might be happening?

I've attached the build log, in case someone wants to take a look.

(The bbuild.sh is AK's ak-makobuildsomething... with the toolchain being changed to the latest linaro one in his Git)

You have to do

git clone https://github.com/anarkia1976/AK-xGenesis.git -b ak-xGenesis-nightly-cm ak-xGenesis-nightly-cm

The "-b" part tells git to select a different branch and is followed by the branch name.

The last part (the second "ak-xGenesis-nightly-cm") is the folder where it should place the branch's files.

However, there is a slight bug in AK's build script that makes the script search for the zImage in AK-xGenesis (instead of the differently named folder)!

Therefore, I'd suggest cloning the branch into a folder named "AK-xGenesis", which gets us this neat command line:

git clone https://github.com/anarkia1976/AK-xGenesis.git -b ak-xGenesis-nightly-cm AK-xGenesis

Have fun and ALWAYS check the size of the file!

If it is below 5 MB something has GONE WRONG and you don't even need to flash it, to find that out ;)

UPDATE:

I have no clue why, but as soon as I replaced the old Intelliplug that AK used (v 2.0) with Faux's new one (v 2.3), it started to work.

...or at least it is displayed in Trickster. (whether it works is up to you lot to find out ;) )

...but this time, the WiFi does not work -.-

So now you actually have a choice: a) Wifi and no Intelliplug b) Intelliplug and no WiFi c) one of the old, stable builds ;)

So again, a highly experimental build (all the disclaimers still apply!) with the only change being the new Intelliplug.

(I found out that for some reason the VM included the wrong WiFi driver.

UPDATE:

I managed to replace the file in its archive without having to recompile :)

So it's a simple file replace - it flashed fine on my device and the WiFi works, Intelliplug is still displayed.

Enjoy a frankenstein build of this highly experimental build.
[Nexus 4 Original Android Development] FrozenLord:
...it says "Edit / Delete" but there is no way to delete.

Could someone delete this post, please?

That would be great :)
[Nexus 4 Original Android Development] nokiagye:
Frozen the same fuk....ing freezes still exist
[Nexus 4 Original Android Development] poondog:
what can you expect from a guy named frozenlord? :D

Plus the kernel is still exp branch not stable
[Nexus 4 Original Android Development] FrozenLord:
Unfortunately, they do.

I wager it is some change in the kernel's sources that causes them.

As stated before: these builds are merely straight builds of AK's repository with a different prima driver.

If I'd know where those hangs originated, I could give it a try to fix them - but taking into account that I have no experience with actually developing a kernel and have no idea where the suspect might be, I'll leave this kind of tinkering to the pros ;)

So far, they seem to appear most frequently when the device has been running for some hours and I start typing text in WhatsApp via KiiKeyboard.

The keyboard will even close every once in a while without displaying a FC window.

UPDATE:

I replaced AK's touchscreen files with some files I borrowed from bricked's git and so far it's looking good.

(Only excessive testing can really tell us whether the issue has improved or not, but so far everything seems to be fine :) )

I've attached the new build (Prima 2.7, built with Linaro 4.8.3 of march 14, bricked touchscreen).

Handle with care and do not try to hold anyone responsible if things go south.
[Nexus 4 Original Android Development] jmtjr278:
[MENTION=1577473]FrozenLord[/MENTION] thanks for all your help. I got 123 built successfully! Only the second time I have successfully built a kernel!

Folks like yourself are a testament to xda.
[Nexus 4 Original Android Development] ak:
Thanks man for support.

New kernel line is the branch named "reborn exodus"

I have reworked all commits with a cleaned implementation ...

I have merged new hotplug from myfluxy n5 branch

ak
[Nexus 4 Original Android Development] montbazon:
Sounds great. Bricked's one is also works great. but it's too aggressive.

나의 Nexus 4 의 Tapatalk에서 보냄
[Nexus 4 Original Android Development] ak:
new mainline

New kernel:

https://github.com/anarkia1976/AK-xGenesis/commits/ak-xGenesis-reborn

New ramdisk:

https://github.com/anarkia1976/AK-anykernel/commits/ak-anykernel

New prima implementation have this file loaded by default:

${HOME}/android/AK-anykernel/cwm/data/ak/wifi/prima

chmod 755 WCNSS_qcom_cfg.ini

or revert this Related commit if you want old prima support:

https://github.com/anarkia1976/AK-xGenesis/commit/1e2dc36714e266bfc0b7707fe5749dc264982193

Synapse:

https://github.com/anarkia1976/AK-anykernel/commit/6b47e907968d61ef94a1e1064e0435de358864e7

Nb:

- i need help with implement features into synapse ... if someone wants to contribute im here.

thanks

ak

Download for test kernel:

View attachment AK.200.EXODUS.MAKO.zip
[Nexus 4 Original Android Development] FrozenLord:
Great, thanks AK :)

I just flashed it and there seems to be a default voltage that is quite a bit higher than your last kernels (850mV at 384 MHz) and the ultra low frequencies (< 384) are gone too.
[Nexus 4 Original Android Development] ak:
Yes right:

- no linux merge

- no vdd disabled

- no overclock

- no bull****
[Nexus 4 Original Android Development] FrozenLord:
100% Ak, 100% bs-free :D
[Nexus 4 Original Android Development] Targaeryan:
Hahhahahhahahahhaha

:D

Looks like he's starting clean again!
[Nexus 4 Original Android Development] FrozenLord:
Nah, there are still some hacks in his Git.

But those features (the ones dropped for now) might be to blame for the kernel hangs.

v 200 seems fine so far, whereas my last build still suffered from some hangs, although the touchscreen felt smoother for me, but that might just be a placebo...

Anyways, 200 seems fine so far.

Let the testing commence :D
[Nexus 4 Original Android Development] Targaeryan:
Yeah I tried your build too.. It was still hanging up.. I'm on 200 too.
[Nexus 4 Original Android Development] ak:
there are some implementations not supported in this moment into trickster like:

- d2tw sema

- hotplug drivers

- gpu policy

- gpu voltage interface

ecc ecc

Im working on synapse for implement these features but my time is very short lately. :silly: :silly: :silly:

https://github.com/anarkia1976/AK-xGenesis/commit/823a15b215a7eed1599fbf123578b279be8b4b1d

https://github.com/anarkia1976/AK-xGenesis/commit/46db449cab76c5fde1a412d3a97c1a6da6b8f7e2

https://github.com/anarkia1976/AK-xGenesis/commit/9819a7e8e965371b7dabaca22294e7de957241e9

https://github.com/anarkia1976/AK-xGenesis/commit/ba57bb3147f77c4bddb8ef73ea997ffae6d10b24

https://github.com/anarkia1976/AK-x...mmit/f8422ba072a82c793cd1cacc558198da698183a2
[Nexus 4 Original Android Development] apb_axel:
Hello [MENTION=3475639]ak.[/MENTION] I can contribute with synapse features if you'd like, just let me know what i can do to help and i'll try my best :)
[Nexus 4 Original Android Development] fr3quency:
As usual no CM11 love. I'd really love it if we didn't have to REPEAT it in order to get a CM11 version. :p

Discrimination...
[Nexus 4 Original Android Development] XsceneXhippieX:
cm11 always gets love with new releases (official ones) in my experience
[Nexus 4 Original Android Development] fr3quency:
If I wait for a stable CM11 release I'll die... ak is not famous for his speed, you can see that. :p
[Nexus 4 Original Android Development] ak:
Very interesting ... Man. [emoji11]

My surname is " lumacone " [emoji6]

ak
[Nexus 4 Original Android Development] apb_axel:
Hey [MENTION=3685904]ak[/MENTION] reading your previous post about d2tw sema, did you replace the current dt2w with sema's or do you now have both in your kernel? My question is for synapse if you want me to add it in leaving the current one or, replace it completely? Thanks!
[Nexus 4 Original Android Development] TheNerd:]:
You switched to Sema!!!!! Nice!!
[Nexus 4 Original Android Development] ak:
Sema touchwake + dt2w and work very well. :good:
[Nexus 4 Original Android Development] apb_axel:
[MENTION=3685904]ak[/MENTION] so far so good https://github.com/apbaxel/AK-anykernel/commits/ak-anykernel.

Anything else you need? :)
[Nexus 4 Original Android Development] ak:
Thanks a lot im testing right now. :D

nb

https://github.com/apbaxel/AK-anyke...7f573ae2c1c27844535bab5#commitcomment-5979712
[Nexus 4 Original Android Development] FrozenLord:
The WiFi in 200 crashed on my mako.

I can't activate WiFi anymore, the slider stays on "off" and won't budge - so no "starting WiFi" this time around...
[Nexus 4 Original Android Development] ak:
What type of wifi ap do you have?

nb:

wifi drivers are original ... i have modded only .cfg.
[Nexus 4 Original Android Development] FrozenLord:
I am not sure it has anything to do with the ap.

The strange thing that really bugs me is that it worked for a few hours and then suddenly stopped working :confused:

It wouldn't even come on after a reboot, so something got screwed completely.

However, I simply dirty flashed your new kernel over the old installation...

I just did a dirty flash of my ROM again (that should have cleaned the last remnants of the old kernel installation) and flashed your kernel again.

The Wifi is working again - for now ;)

So with 200 and onwards, I'd recommend doing a dirty flash of the ROM.
[Nexus 4 Original Android Development] ak:
Im using the same version with Mahdi without problem, please post dmesg logs if the problem persist. :D

thanks
[Nexus 4 Original Android Development] ak:
new test kerne

Synapse source update:

https://github.com/anarkia1976/AK-anykernel/commit/c82f6fc2798929c2cf509f096e2de7b64efaec65

nb:

please download synapse and test it!

Synapse: add 1wake, 2wake, readahead and cleaning

New test kernel changelog:

https://github.com/anarkia1976/AK-xGenesis/commits/ak-xGenesis-reborn

Download:

View attachment AK.203.EXODUS.MAKO.zip

please press Thanks button! :good:
[Nexus 4 Original Android Development] fr3quency:
I just can't live without ak's kernel. :P Moved to PA 4.2 Beta 4. I can live with it, but I'm waiting eagerly for a CM11 version.

The latest "frequent" updates rock btw.
[Nexus 4 Original Android Development] Utkarsh-ezzo:
[MENTION=3685904]ak[/MENTION] , m I missing mp decision and intelliplug options somewhere or you have wiped off mpd and made intellipug as default...???

ezzo