yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] joeski27:
Failed to flash?

So I'm trying to flash v207, while using the latest Euroskank CM11 kang (12/1), and no matter what I do I keep ending up with a failed flash. I've re-downloaded the kernel (and it is the correct cm11 version), and I've even done a factory wipe and started fresh (wipe, then flashed rom, PA 11/26 gapps, and then the AK kernel) but no dice. Anybody think of anything I may have missed here?? :confused:
[Nexus 4 Original Android Development] Treatcon:
Unmount the system partition maybe in recovery
[Nexus 4 Original Android Development] joeski27:
Never actually done (or had to) do that that before. Perhaps a dumb question, but how would one do it? Just a simple option in TWRP, or something more involved?
[Nexus 4 Original Android Development] vampire36:
go to mounts and uncheck system :)
[Nexus 4 Original Android Development] joeski27:
Uh, ok so I went there, but apparently system was already unchecked. WTF? :confused:

Has anyone successfully flashed the v.207 with the 12/1 euroskank cm11?
[Nexus 4 Original Android Development] gorilla p:
I personally got tired of playing with the unofficial cm nightlies and trying to get different kernels to work with it. I just went with a 4.4 aokp build and am using the AK kk kernel.
[Nexus 4 Original Android Development] ak:
For now im doing the same ... i cant maintain a kenel without official cm11 nightly.

Im very happy with KK aosp in this moment. :highfive:
[Nexus 4 Original Android Development] joeski27:
Yeah I hear you, but in this case I can't even get it to flash, period. I believe it said something along the lines of "zip authentication failure", not that I really know what the hell that means, lol.
[Nexus 4 Original Android Development] David9519:
No,i meant the icons.

They look like being the dock but what are they exactly
[Nexus 4 Original Android Development] ak:
icons:

https://play.google.com/store/apps/details?id=com.ds.goolors
[Nexus 4 Original Android Development] nokiagye:
Ak: what can i do for the hi temperature? Example:yesterday I watch a flash video and after 10 minutes it go up to 45°c
[Nexus 4 Original Android Development] nedooo:
Congrats on great kernel. Keep it minimalistic as possible.
[Nexus 4 Original Android Development] ak:
You can reduced throttle temp to 60c and set the max freq to the min as possible. :good:
[Nexus 4 Original Android Development] nokiagye:
Thanks I'll make it and I give feedback. Good morning
[Nexus 4 Original Android Development] ak:
Thanks

akillusion ;)
[Nexus 4 Original Android Development] nokiagye:
OK I set the temperature to 65 and max freq to 1134 and its OK now thanks again
[Nexus 4 Original Android Development] Targaeryan:
Psssttt.. Why don't you secretly hook me up with illusion ROM? ;) :p
[Nexus 4 Original Android Development] luiseteyo:
The phone sleeps incredibly, but when I try to set min frecuency to 384 it reverts to the máx frecuency, so my battery drain is being HUGE... :(

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] ak:
Mpd is the culprint.

akillusion ;)
[Nexus 4 Original Android Development] ak:
Strange ... Probably related to sweep area

akillusion ;)
[Nexus 4 Original Android Development] luiseteyo:
Vooooooilá thanks!!

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] J000rg:
Was my first thought... Then I disabled S2W and only enabled dT2W, and the bug still starts to occur at some time. Really strange.

Any other suggestions?

I mean, dT2W should NOT have any affect on the left EDGE of the screen, as it's focused on the centre area of the screen.

btw: I'm not sure if ONLY the left edge is affected, maybe all Edges of the screen become unresponsive but as I don't have any Apps that use swipe from any other than left edge of the screen (play music, play market etc) I cannot say anything about the other edges. (Status bar even works, if this bug occurs, I gues the swipe area for status-bar is large enough to compansate the unresponsive part, but the left swipe area for play-* apps is not.)
[Nexus 4 Original Android Development] snak3ater:
Tried to reproduce this thing in Google play,google Plus & Gmail...

Swiped from left edge of the screen & sliding menu showed up without any issues..Same in Google plus & gmail..Left edge isn't unresponsive or anything like that..

PS:Faux,Bricked & now Ak..This is the 3rd thread in which i saw similar post.If there was an issue with s2w/s2s,someone would have mentioned it in 3 thread combined.But so far i've never heard anyone with such issue..Can you try touch control & see if it has got same problem?

Also i just noticed that your left edge is responsive when s2s/s2w is turned off..That's really weird.
[Nexus 4 Original Android Development] J000rg:
The Problem is, the bug appears after a certain amount of time on S2W/T2W, and not instantly after turning it on. But when it appears, it can instantly be fixed by disabling s2w/t2W (by editing the file \sys\android_touch....)

I wonder why I am the only one noticing this issue: Thatswhy I flashed every Kernel that supports s2w and/or t2w feature and tried to reproduce this bug and on every kernel I got the same result. This is also why I posted this on the other kernel Threads, too.

thank you anyway

If anyone, who has s2w or dt2w enabled, could just sometimes check if swiping from left on e.g. play store is buggy, that would be great :)

I love this feature so much, but this bug is the only reason I have t2w disabled :/
[Nexus 4 Original Android Development] Benjamin_L:
Works fine for me
[Nexus 4 Original Android Development] ak:
[CM10.2] STABLE KERNELS

ak kernel download: AK.035

Github Kernel: Link

changelog:

+ 2 patches for interactive from 3.10 android

+ some patches for lib routine

+ a lot of fixes here and here

+ low cpu freqs steps: +162 Mhz, +270 Mhz, +378 Mhz

+ auto hotplug tuned for battery life

+ rwsem patches

+ binder patches

NB:

no lag with last cm nighlty for me!

NB:

seems users want speed ..... and speed will be!
[Nexus 4 Original Android Development] melbourne408:
Is this updated from today's previous release?
[Nexus 4 Original Android Development] ak:
No its only for repost changelog
[Nexus 4 Original Android Development] melbourne408:
That means lights out for me, time to give my glasses a break and go contacts tomorrow.

See you in the morning man, thanks for all of your work!
[Nexus 4 Original Android Development] AzizWahid:
Is this compatible with stock 4.3 JWRYY?

I had flashed the latest version just now but my display become such a total mess. I've also tried flashing the screen tearing fix I found on purified kernel thread but its still the same.

Any help?
[Nexus 4 Original Android Development] ak:
No compatible my friend ... only CM10.2 roms and derivate ... CAF godness is inside. :highfive:
[Nexus 4 Original Android Development] gpvecchi:
Do you have MPDecision off or on?
[Nexus 4 Original Android Development] ak:
mpd is dropped = only auto hotplug

I have uploaded a new version super optimized:

http://xdaforums.com/devdb/project/?id=1023#downloads

Changelog:

https://github.com/anarkia1976/AK-xCrossing/commits/ak-cm10.2-015-prima

... you can try this version and report if lags are gone.

Thanks a lot.
[Nexus 4 Original Android Development] ivanich:
Did anyone notice that in 0.41 some strange default color gamma? It's too blue. Is it related to commit "Switch to cm10.2 colors " ?

EDIT: Forget about this, it's my bad gamma settings, after resetting it colors become fine
[Nexus 4 Original Android Development] Benjamin_L:
0.41 doesnt default to halfbreed colors. I liked that 0.35 did this.
[Nexus 4 Original Android Development] Targaeryan:
Doesn't use halfbreed by default. But there are preset options, that can be chosen, present in trickstermod.
[Nexus 4 Original Android Development] gpvecchi:
Nope... My CPU tends to stay [MENTION=416804]162[/MENTION]Mhz; it takes some times to raise, so when I scroll the homepages, i have lag... It takes around 1 second, but I need to use the touchscreen a lot, if I make a single press, frequency stays at 162...
[Nexus 4 Original Android Development] direwolf1:
I'm sorry if this is silly or redundant, but has anyone tried this on Slim ROM? I know cm kernels used to work on slim, but they made some changes that forced use of a JWR kernel that seriously reduced compatibility with most kernels for a while. Since then supposedly things have improved. I'm currently using AK JWR 0.23+ and would love to try out your latest work.
[Nexus 4 Original Android Development] Sblast:
yeah, I wish there was a JSS/JWR version of this great ROM.
[Nexus 4 Original Android Development] evcz:
That's how intelliplug works :(

And that's the reason I'm back to the official cm kernel while waiting for a faux kernel with CAF support: I love the smoothness provided by mpdecision and can't appreciate my phone without it :-\
[Nexus 4 Original Android Development] hlt4668:
What governor are you guys with lag using? I'm using intellidemand and I don't suffer any responsiveness issues. Default hot plug & governor settings.
[Nexus 4 Original Android Development] poondog:
Shouldn't take that long to ramp up... Do ypou mean intellidemand? The hotplug here is generic hotplug by thalamus. Faux kernel primarily uses intelliplug on the main cores, not mpdecision

Try another governor, like interactive because it should not take a whole second to ramp up unless its a super power saving governor.
[Nexus 4 Original Android Development] hellsgod:
There is no intellitplug in the kernel. It uses auto_hotplug. If you want a raised frequenzy by touch, you need a touch boost. There are more theories about it. I'm thinking it's a way to improve smoothness, and i'ts a way to save battery. It doesn't need to scale up and down when you are scrolling, or interact with the UI. 1ghz for example can handle a lot of backgroundload and UI Interactions. Fix it by touch for 1 second after touch, but let it scale above, if needed.

Every frequency-calculation needs power. If you reduce them in form of less frequencies avaiable to scale (by touch it scales only from 1ghz to max) you will have some sort of battery saving. mpd does something similar. By touch min_freq = 1026000 for 3 seconds and 2 Cores.

Look at [MENTION=3685904]anarkia1976[/MENTION] git, you will find there something ;)

hells

---------- Post added at 02:29 AM ---------- Previous post was at 02:13 AM ----------

intellidemand is a good example. It uses a dynamic samplerate. If you touch your screen, the samplingrate will be lower for 2.5 sec, so you will have much less latency in UI interactions. If you use that lesser latency together with touch boost, like I do... Yes, it's smooth as butter :D

hells
[Nexus 4 Original Android Development] gpvecchi:
Strange is that I use kernels without MPdecision from a long time, but I never had issues of CPU not ramping up...

This looks more like a touch boost issue, not a governor one.
[Nexus 4 Original Android Development] snak3ater:
Really strange..My s2s/s2w are always enabled..I never disable it..

This option if the first option that i turn on after flashing the kernel :D

But the thing is that i tested in 3 different Apps..All working fine..Will test in other Apps too :)
[Nexus 4 Original Android Development] ak:
Im using 2w with trickster app but I never see this problem. I'm sorry.

I'm verify the drivers for see if there is a possible tuning of the sweep area

akillusion ;)
[Nexus 4 Original Android Development] ak:
Can you collect dmesg messages during the problem?

Related to kernel, no logcat please

akillusion ;)
[Nexus 4 Original Android Development] J000rg:
Thank you haha :D

I guess, I messed sth up, because if you always have s2w enabled but never noticed this bug, it has to be my fault. I am on Stock 4.4 Kit Kat, rooted.

Maybe just check with Play Store, every half hour or sth. if not to much to ask =)

But thank you anyway, I get my N5 soon, and if this "bug" only occurs with my N4, maybe I will change my mind and flash some custom s2w-Kernel on my new N5
[Nexus 4 Original Android Development] C4SCA:
But the min frequency is set to 1026mhz only for a couple seconds aftr touching the screen right? Mpdecison works like this, is part of project butter, am i right?

sent from my NEXUS 4 tasting KitKat for the first time
[Nexus 4 Original Android Development] ak:
No problem man I'm here if you want im here :thumbup:

akillusion ;)
[Nexus 4 Original Android Development] snak3ater:
Yes you are right :)
[Nexus 4 Original Android Development] J000rg:
Thanks, really appreciating that. I will try to display some dmesg, while this bug occurs.
[Nexus 4 Original Android Development] rodries:
Fix multirom with 2w

Finally I've fixed multirom problem.

You have to delay the input_register_device, I'll fix it in dt2w also, then I'll send to you a diff.

Testing now to be sure I haven't broken anything.
[Nexus 4 Original Android Development] Dryblow:
Old settings are lost on KitKat kernel?
[Nexus 4 Original Android Development] J000rg:
It occured again (after about 40 minutes after enabling dt2w), managed to make a screen recording:

http://www.youtube.com/watch?v=E43DSivoJsY

But I could not display any dmesg messages

(maybe I have the wrong app: https://play.google.com/store/apps/details?id=t0mm13b.dmesglog&hl=de)

After setting dt2w to 0 with trickster, and turning screen off and on again, bug was gone.

Sadly screen recording stops, when turning screen off, so I could not show you, that the bug disappeared....
[Nexus 4 Original Android Development] rodries:
Attached the diff patch to be used in ak-xaosp-012-kk (git apply muiltirom2w.patch)

Fix the multirom problem.

Also I've seen something weird in detect_sweep2wake function I've added scr_on_touch=true; in the first if, I'm not sure about this change maybe fix the problem reported by users where s2w is not working.

Edit:

After read the code again scr_on_touch is not used at all, I think this var can be deleted, probably comes from another s2w port.

Edit2:

Have you seen this patch: https://github.com/showp1984/bricked-mako/commit/0d4a16c8147b460b7f5459eb6a2058dc27c9a2e6

Also need to add dt2w_switch to the condition
[Nexus 4 Original Android Development] ak:
Thanks a lot for your support.

this patch is a reworked i2c retry (replace https://github.com/showp1984/bricked-mako/commit/0d4a16c8147b460b7f5459eb6a2058dc27c9a2e6)

https://github.com/anarkia1976/AK-xAosp/commit/764f71da77303cae6bbfdb4906cef15ec9528d60

I have pushed a new commit for touch freeze:

https://github.com/anarkia1976/AK-xAosp/commit/ab176dffa945038e77ebb131331c3349d073c4c5
[Nexus 4 Original Android Development] rodries:
I've sent to you a private message with a ak kernel for testing.

Can you test s2w stuff?
[Nexus 4 Original Android Development] J000rg:
Thanks.

testing...
[Nexus 4 Original Android Development] snak3ater:
[MENTION=3685904]ak[/MENTION] .. This is just perfect..I hope it solves my problem too (screen freeze) :D
[Nexus 4 Original Android Development] rodries:
No need to test it. Ak has fixed the problem already.
[Nexus 4 Original Android Development] ak:
About 4 hrs with new patch without problems. :D
[Nexus 4 Original Android Development] AndrolinRoot:
illusion :p

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] The Zel:
Is today the day? ?

N⁴
[Nexus 4 Original Android Development] ak:
Hi my friend ... Illusion is on the way ...

akillusion ;)
[Nexus 4 Original Android Development] AndrolinRoot:
If I get through the build errors, sure :p

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] ak:
I have see a lot of progresses on git.

Thanks a lot for your hard work

akillusion ;)
[Nexus 4 Original Android Development] AndrolinRoot:
I added -03, will it work with AK ?

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] ak:
Yes .. But you have to add to build flags mno unaligned access

akillusion ;)
[Nexus 4 Original Android Development] musa47:
Let's have a break, and have akillusion :P
[Nexus 4 Original Android Development] AndrolinRoot:
Can you come hangouts ?

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] hardwareadictos:
Can someone explain to me what is the illusion project?
[Nexus 4 Original Android Development] AndrolinRoot:
A Rom :p

Gesendet von meinem AOSP on Mako mit Tapatalk

---------- Post added at 06:56 PM ---------- Previous post was at 06:56 PM ----------

little preview :p www.illusionroms.com

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] sims34:
Can't download, the site doesn't work.
[Nexus 4 Original Android Development] goofball2k:
Cant wait!!!
[Nexus 4 Original Android Development] Raider1284:
same here, cant access the site at all. looks like it down for everyone too: http://www.downforeveryoneorjustme.com/http://ak.hiddenbytes.org
[Nexus 4 Original Android Development] ak:
#
# AK LINARO OPT
#
CFLAGS_A15 = -march=armv7-a -mtune=cortex-a15 -mfpu=neon -funsafe-math-optimizations
CFLAGS_MODULO = -fmodulo-sched -fmodulo-sched-allow-regmoves
KERNEL_MODS = $(CFLAGS_A15) $(CFLAGS_MODULO)

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-format-security \
-fno-delete-null-pointer-checks \
-ftree-vectorize \
-mno-unaligned-access \
-Wno-sizeof-pointer-memaccess \
$(KERNEL_MODS)
[Nexus 4 Original Android Development] boubou93:
[MENTION=3685904]ak[/MENTION] do you work for cm11 ?

Fast charge ? And etc.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] AndrolinRoot:
Thanks. so... I heard some people want illusion ? #Illusion

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] The Zel:
You heard right!
[Nexus 4 Original Android Development] AndrolinRoot:
You have to wait until tomorrow :( had school from 6am until 5pm :p But our themer is working on some nice stuff :p

Gesendet von meinem AOSP on Mako mit Tapatalk
[Nexus 4 Original Android Development] xator91:
For purity, KK or cm?

PS: Anyone can mirror ak.218.kk zip? website down
[Nexus 4 Original Android Development] paulo_cv:
https://www.dropbox.com/s/kbbyasaj88hoxfk/AK.218.KK.zip
[Nexus 4 Original Android Development] Raider1284:
Thank you very much for this. Its installed and working well now, but i dont seem to have any voltage control with v218. When i do try and change the voltage, using system monitor, the phone instantly reboots.
[Nexus 4 Original Android Development] moneyolo:
You undervolted too much. Try to find that sweet spot so it won't reboot on you.
[Nexus 4 Original Android Development] da900:
Hi. Could anyone share the latest CM11 release, please? Thanx a lot.
[Nexus 4 Original Android Development] soumoks:
Official cm 11 nightlies are going to start in a few days if you're willing to wait, check this out.

http://www.cyanogenmod.org/blog/cyanogenmod-10-2-0-release
[Nexus 4 Original Android Development] capeorigins:
Is anyone else having problems going to the website? Is it down?
[Nexus 4 Original Android Development] da900:
:) I mean CM11 version of this kernel. As site is down for now and I can't download it from the link in the OP.
[Nexus 4 Original Android Development] ak:
Site is up and running .... :D
[Nexus 4 Original Android Development] ak:
New kernel online

[KITKAT] [STABLE]

download: AK.221.KK

changelog:

+ blx

+ interactive patched to last common and with boost interface

+ 2w: fix problem with hardboot and multitouch

+ 2w: hacky solution for unresponsive screen

+ fixes

+ ecc.

thanks and rate.
[Nexus 4 Original Android Development] soumoks:
Oops sorry about that,my bad :p
[Nexus 4 Original Android Development] saint_cow:
Not sure if is a fault but in trickstermod I can't enable mpdecision, it resets itself. Same thing happens when trying to set interactive gpu governor.
[Nexus 4 Original Android Development] ak:
You have flashed a kernel that removed mpd and change the default gov to interactive.

You have to reflash your rom.
[Nexus 4 Original Android Development] atxbang56:
have you tried what franco uses in his kernel to improve gaming experience ?

*** KitKated from my PSX/AK Powered Nexus 4 ***
[Nexus 4 Original Android Development] ak:
No ... i dont have problem with gaming. :good:
[Nexus 4 Original Android Development] atxbang56:
me neither but I don't undertstand what is exactly his "patch" for gaming

*** KitKated from my PSX/AK Powered Nexus 4 ***
[Nexus 4 Original Android Development] snak3ater:
There's no need of any patch. I tested Franco kernel just to see the performance.. It was smooth no doubt but ak kernel is on par in performance & really smooth without any patch..
[Nexus 4 Original Android Development] abalam:
Yow [MENTION=3685904]ak[/MENTION] tnx for the hardwork. I'm Already a few days your kernel to run and runs perfectly. Right from the start with my android device I turn kernels al Started the galaxy-S, then the maguro and now with the mako. Keep it up!
[Nexus 4 Original Android Development] da900:
Hi. Any news about update for CM11 version?
[Nexus 4 Original Android Development] gorilla p:
I mentioned this a couple days ago but with this kk kernel I've been having serious trouble undervolting, at least at first. I can undervolt 384mhz to nearly 700mv but if I open trickster and lower it across the board just -25mv from standard 850mv , it will reboot on me, then next time I might be able to Uv -125 with no problem and save that setting until I upgrade to the latest kernel and I have to have my phone dump on me 5 or 6 times until it takes the UV. Then it works fine until I have to update again....
[Nexus 4 Original Android Development] paulo_cv:
#Illusion? :D
[Nexus 4 Original Android Development] ak:
Kernel have boosted disabled (-25mv) .. problems with voltage are resolved ... have you tried the last version?
[Nexus 4 Original Android Development] alahkel:
OK here i am, same exact issue. I have it with dt2w (which i love) enabled via trickstermod (no s2w or s2s enabled) and it seems to occur with trickster mod auto run at boot. I have this setup:

omnirom official mako nightlies + xposed + gravity box+xhalofw in first slot of multirom (second slot i have cataclysm 25nov, both having same kernel ak218 and bug) and on multirom boot menu i can navigate only with physical volume and power buttons, touch is disabled as told before from others.

My findings:

1) it looks like the touchscreen unresponsive edges bug appears for me on boot when trickster loads the kernel settings including dt2w and if i don't touch the phone before trickster loads those settings, the whole touchscreen becomes frozen, like just disabled.

2) physical left and right edges are unresponsive only. if i put my device in landscape, drawer left menu works again.

I'm writing this asa I've seen the quoted post, I haven't read the following pages yet, I'll put an edit if this was already reported or fixed :)
[Nexus 4 Original Android Development] donjamal:
hello,

Im using now the latest KK kernel and i have a massive battery drain because of the media server. its over 60% all day long. Is is a kernel problem, anyone else has the same issue? Or is it just for me?
[Nexus 4 Original Android Development] ak:
I dont know but i cant verify these 2 problems:

- i dont use multirom but i have implemented a patch to fix this and this is confirmed fixed

Thanks a lot @rodries http://xdaforums.com/showpost.php?p=48062772&postcount=2193

- i dont have the problem with unresponsive edges, i need kernel log eventually for verify
[Nexus 4 Original Android Development] ak:
Media server is a problem from rom side.
[Nexus 4 Original Android Development] donjamal:
it wasnt that bad before. Actually i use your kernels since 3 weeks now, and the battery was good until now. I installed some soundfx and sonyapps maybe thats the problem.. i just wanted to ask :) thanks