yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] amack10:
This is a great kernel but i was just wondering how u load the preset profiles from gorilla p. I downloaded the performance one and i put it in the synapse profile folder in my memory. But when i select the profile in synapse and push restore it says invalide file. And doesnt load. Im on android l and chose the profile for the kernel im using. If someone could let me know what im doing wrong it would be greatly aapreciated. Thank you
[Nexus 4 Original Android Development] gorilla p:
Select profile, click √

Select restore.

Synapse will force close

When it opens, click X

All settings should be applied then

The only settings that don't seem to be applied is the msm limiter (tick enable for msm limiter)

PE-WQ should be ticked and applied as well if not already set.

Sent from my Nexus 4
[Nexus 4 Original Android Development] fr3quency:
loled @ screenshot trying to show the 'different' colours. Priceless!!
[Nexus 4 Original Android Development] AndroidReborn:
Getting amazing battery life with this,especially after undervolting by 45 mV.

Two questions.

While setting sweep2wake in synapse, it never sticks . It reverts to the previous one on pressing the tick. Sweep2sleep and dt2w work though.

Any solutions?

And second, a humble request. Could you please consider adding this to your kernel in your free time? Just a humble request from a loyal user of your kernel. It's something like LG G3 knock code.

http://xdaforums.com/showthread.php?t=2965344

Sent from my awesome Nexus 4 running SimpleAOSP with AK500. Bazinga!
[Nexus 4 Original Android Development] xshallowgrave:
Is Busy Box a requirement for synapse? I'm running stock lollipop with root but get an error when trying to install it.

---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------

Edit: got it to install successfully.
[Nexus 4 Original Android Development] ak:
s2w is buggy like in others kernels and like tc.

I think to remove this feature for the new release.
[Nexus 4 Original Android Development] demon507:
Currently running AK106 on AOSPA 4.4 and first impressions are my nexus feels more smoother than stock...will test out for battery life
[Nexus 4 Original Android Development] :
Please keep s2w feature. I don't encounter any problems with it. Besides, the battery drain is not really significant as others thought. I am willing to sacrifice a 3-5% battery drain for the convenience of swiping. Besides, if it's there, nobody is forced to use the feature or not. At least, there is an option for those who want to. Thanks
[Nexus 4 Original Android Development] ak:
New stable kernel KK

[KITKAT - CAF]

STABLE KERNEL

ak kernel download: AK.112.KK

Github Kernel: Link

changelog:

+ resolved really turn on/off lags

+ reverted to prima v181 -> fix disconnection problems

+ revert to -Os optimizations

+ cleanig cpufreq and intellidemand code

+ ecc ecc ecc

As always please press Thanks button and rate the thread.
[Nexus 4 Original Android Development] Gnome:
Ooh! New one to play with!
[Nexus 4 Original Android Development] maverickronny:
I agree, it works awesome , don't remove plz
[Nexus 4 Original Android Development] badluckclinton:
Is it ok to dirty flash over Experiment AK.111 ?
[Nexus 4 Original Android Development] Targaeryan:
Yes!
[Nexus 4 Original Android Development] robygt:
That's how I like to start my day, huge breakfast and a shiny new kernel from Anarkia!

Sent from my Nexus over 9000!!!
[Nexus 4 Original Android Development] Jagdish84:
True dat!
[Nexus 4 Original Android Development] Benjamin_L:
So no more love for cm10.2?
[Nexus 4 Original Android Development] ak:
Next update will be for cm11 ... No more updates for Jw ....

ak kk inside ;)
[Nexus 4 Original Android Development] TheQuarterMile:
Thank you for this kernel and for improving the kitkat experience :) Is touch control enabled?
[Nexus 4 Original Android Development] Targaeryan:
Still waiting for the touch control Dev to support this kernel I think.
[Nexus 4 Original Android Development] Benjamin_L:
OK, nightlies should start soon so i guess its only reasonable
[Nexus 4 Original Android Development] Locksmith81:
Anyone have kernel setting recommendations? For trickstermod or faux kernel app
[Nexus 4 Original Android Development] rshankar:
Hey, kernel is super smooth so far..

But the device is not going into deep sleep.. I tried searching, it seems no one has this issue - on AK 106 & 112.

Thanks
[Nexus 4 Original Android Development] Targaeryan:
No issues here. What ROM are you using? Did you try fully charging it and starting a new cycle? Or reboot and check again? Please mention details thx. :cowboy:
[Nexus 4 Original Android Development] ak:
People says: deep sleep is kernel problem?

I don't know .... But before publish new kernel I'm testing it for one night and I don't have see problems with deep ....

ak kk inside ;)
[Nexus 4 Original Android Development] GragonV:
same here, cannot make it stick :)
[Nexus 4 Original Android Development] ilanor:
Hello. I was using this combo of AK kernel, UKM, and Synapse on my KK Mako and Mclovin' it! I just built cm12 and it has a version number 5.0.2. Synapse complains error not supported on this device. Could it be the whacky version number throwing it off? Thanks!
[Nexus 4 Original Android Development] gorilla p:
Possibly, It could do a quick version number check and 5.0.2 probably isn't on the list of supported versions
[Nexus 4 Original Android Development] CallMeAldy:
Works fine for me.
[Nexus 4 Original Android Development] nicknc:
Search the synapse thread. There is a UCI reset terminal command to run that instantly fixes this. Just search for "device not supported".

It's three lines to run, takes 20 seconds, no big deal.
[Nexus 4 Original Android Development] fr3quency:
>styx 0001

wat [MENTION=4450732]CallMeAldy[/MENTION]
[Nexus 4 Original Android Development] CallMeAldy:
Eagle Eye.
[Nexus 4 Original Android Development] fr3quency:
I had seen it on Google+ some days/1 week ago but I was too lazy to comment. :p
[Nexus 4 Original Android Development] CallMeAldy:
AK.600.MAKO

Here's a little Christmas week gift.

AK.600.MAKO

CallMeAldy - Switch from Linaro to SaberMod
CallMeAldy - defconfig : Add IntelliMM Governor
Paul Reioux - cpufreq_intellimm: intelliminmax cpu governor initial baseline commit
CallMeAldy - block: Update to BFQv7r6
Liam Mark - lowmemorykiller: enhance debug information
CallMeAldy - Revert "lowmemorykiller: enhance debug information"
CallMeAldy - defconfig: Enable CONFIG_SECCOMP.
Liam Mark - lowmemorykiller: enhance debug information
Liam Mark - mm, oom: make dump_tasks public
Jordan Crouse - fs/seq_file: Use vmalloc by default for allocations > PAGE_SIZE
Heiko Carstens - fs/seq_file: fallback to vmalloc allocation
Al Viro - nick kvfree() from apparmor
Robert Sesek - mako_defconfig: Enable CONFIG_SECCOMP.
Robert Sesek - seccomp: Use atomic operations that are present in kernel 3.4.
Kees Cook - seccomp: implement SECCOMP_FILTER_FLAG_TSYNC
Oleg Nesterov - introduce for_each_thread() to replace the buggy while_each_thread()
Kees Cook - seccomp: allow mode setting across threads
Kees Cook - seccomp: introduce writer locking
Kees Cook - seccomp: split filter prep from check and apply
Kees Cook - sched: move no_new_privs into new atomic flags
Kees Cook - ARM: add seccomp syscall
Kees Cook - seccomp: add "seccomp" syscall
Kees Cook - seccomp: split mode setting routines
Kees Cook - seccomp: extract check/assign mode helpers
Kees Cook - seccomp: create internal mode-setting function
Kees Cook - MAINTAINERS: create seccomp entry
Will Drewry - CHROMIUM: ARM: r1->r0 for get/set arguments
Will Drewry - CHROMIUM: seccomp: set -ENOSYS if there is no tracer
Will Drewry - CHROMIUM: ARM: arch/arm: allow a scno of -1 to not cause a SIGILL
Will Drewry - CHROMIUM: arch/arm: select HAVE_ARCH_SECCOMP_FILTER
Will Drewry - CHROMIUM: arch/arm: move secure_computing into trace; respect return code
Will Drewry - CHROMIUM: arch/arm: add asm/syscall.h
Will Drewry - samples/seccomp: fix dependencies on arch macros
Will Drewry - seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER
Will Drewry - seccomp: ignore secure_computing return values
Stephen Rothwell - seccomp: use a static inline for a function stub
Will Drewry - Documentation: prctl/seccomp_filter
Sasha Levitskiy - Change-Id: I7c9d49079d4e18390c2d520513a4afd55e6eaa3e
Will Drewry - ptrace,seccomp: Add PTRACE_SECCOMP support
Will Drewry - seccomp: Add SECCOMP_RET_TRAP
Will Drewry - signal, x86: add SIGSYS info and make it synchronous.
Will Drewry - seccomp: add SECCOMP_RET_ERRNO
Kees Cook - seccomp: remove duplicated failure logging
Will Drewry - seccomp: add system call filtering using BPF
Will Drewry - arch/x86: add syscall_get_arch to syscall.h
Will Drewry - asm/syscall.h: add syscall_get_arch
Will Drewry - seccomp: kill the seccomp_t typedef
Will Drewry - net/compat.c,linux/filter.h: share compat_sock_fprog
Will Drewry - sk_run_filter: add BPF_S_ANC_SECCOMP_LD_W
John Johansen - Fix execve behavior apparmor for PR_{GET,SET}_NO_NEW_PRIVS
Andy Lutomirski - Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs
CallMeAldy - New Life
CallMeAldy - Linux 3.4.105

Enjoy :)
[Nexus 4 Original Android Development] is0l4ted:
Well, it will rock!!
[Nexus 4 Original Android Development] gorilla p:
Update on bit.ly/makostuff

Added new profiles for Unleashed 98u and AK v600 Created them from scratch. Hopefully this will help with people having continuous force closes.

Battery

Bat-bal

Bal

Bal-perf

Perf

Perf-Max

Added Hells Doctor Kernel L14

Added AK Kernel v600

Added TWRP 2.8.3.1

Added 27/105 hybrid modem (with 2nd revision of the .27 modem)

Added latest SuperSU flash zip 2.42

Added latest Wugs Root Toolkit 1.9.9

Added latest LBE Security 5.4 EN.

Added latest BoldBeast Call Recorder for N4

Added latest Cerberus Disguised flash zip

Added SystemUIReboot (App to do a quick reboot of systemUI)

Sent from my NeXuS 4
[Nexus 4 Original Android Development] jacomail95:
TWRP 2.8.3.2 for mako is out :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] gorilla p:
2.8.3.2 has a problem. Wipe otg-usb is missing and wipe cache runs the wipe usb+-otg command.

---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------

Hey [MENTION=4450732]CallMeAldy[/MENTION] I had a couple requests.

1 - could you please add Conservative governor back? It actually runs really smooth with L/5.

2 - Could you add the max screen off cores and touch boost freq to intelliplug or max screen off freq to msm hotplug?

3 - would it be possible to add the option for (don't power on core1,23 if load is below X or Freq is below X)?

These features are available in Unleashed 98u at the moment.

Let me know if you want me to try to find the commits. Thanks.
[Nexus 4 Original Android Development] CallMeAldy:
1) It'll be added ASAP.

2) Everything is already there, maybe you missed out on it.

3) I don't mind adding it, see if you can find the commits. I'll search for it too in the meantime.

EDIT :- Also AK now uses AnyKernel2 format instead of the old AnyKernel format.
[Nexus 4 Original Android Development] gorilla p:
For #2, it seems like each hotplug only has one or the other, but not both max screen off cores and max screen off freq.
[Nexus 4 Original Android Development] xshallowgrave:
Can latest AK be used w/ kk 4.4.4?
[Nexus 4 Original Android Development] gorilla p:
I'm having a little trouble finding the commit.

It is available in Hells Doctor kernel under msm-MPDecision "Idle Frequency".

See screenshot.
[Nexus 4 Original Android Development] aviz1911:
HERE

I don't think there's any separate commit for idle freq. It's build into the hotplug(msm mpdecision)
[Nexus 4 Original Android Development] CallMeAldy:
AK doesn't use MP Decision. I'll see what i can experiment with;)
[Nexus 4 Original Android Development] ilanor:
Must've been something changed in the latest cm sources. Resynced, built, and everything works with no fiddling. :confused:
[Nexus 4 Original Android Development] AndroidReborn:
Bump.

Sent from my awesome Nexus 4 running SimpleAOSP with AK500. Bazinga!
[Nexus 4 Original Android Development] sykopompos:
A new anykernel format? Does it bring anything new??
[Nexus 4 Original Android Development] aviz1911:
AFAIK, only s2s, s2d, dt2w, touch wake works. s2w doesn't work. It's combined with s2s that is why it's visible in synapse.

And tap2unlock is a good feature but just imagine the battery drain it can cause if the screen is always welcome for touches from user ?? Also, these features are like 1 day or 1 week used features and eventually again users shift to dt2w. I'm not against it, it's upto Callme and AK to add it or not ;)
[Nexus 4 Original Android Development] AndroidReborn:
Yeah I realized it was more of a novelty rather than actually useful. My main query and the reason for bumping was my question regarding s2w. It does say sweep2wake and sweep2sleep on the first page though.

Thanks!

Sent from my awesome Nexus 4 running SimpleAOSP with AK500. Bazinga!
[Nexus 4 Original Android Development] renegadedj:
op DL link

Opening page download link for aosp v600 not working! :( :eek:
[Nexus 4 Original Android Development] gorilla p:
Good thing someone has been hosting every AK kernel for the past year...
[Nexus 4 Original Android Development] renegadedj:
And where is the mirror then? Haaaaalp haha
[Nexus 4 Original Android Development] Pollie81:
In your bathroom..
[Nexus 4 Original Android Development] renegadedj:
Eureka! Wonder what other kind of files i can find in my porcelain repository. Thanks for the help. :rolleyes:
[Nexus 4 Original Android Development] Pollie81:
Ah, you couldn't laugh with my joke?
[Nexus 4 Original Android Development] renegadedj:
I chuckled a little but was more cynical about about being in the bathroom in the first place when you said that, hence rolling the eyes. Haha
[Nexus 4 Original Android Development] CallMeAldy:
Basketbuild are having alot of downtime lately. I may switch to AndroidFileHost

EDIT :- Mirror added in OP.
[Nexus 4 Original Android Development] sidnoit22:
I download 5 times and always fail download. :(
[Nexus 4 Original Android Development] CallMeAldy:
Mirror is given for a reason.
[Nexus 4 Original Android Development] gorilla p:
If you have trouble with OP links, check bit.ly/makostuff

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sidnoit22:
lulz i wanted to write "That's why when i downloaded 5 times it failed" :p
[Nexus 4 Original Android Development] nicknc:
I still have to run UCI reset on latest cm before synapse runs. Even does it with the built in synapse on defconui's kernel.

Oh well.
[Nexus 4 Original Android Development] Rohit02:
Follow proper procedure while flashing

ROM+Gapps,

kernel

ukm3.6.1

su

reboot

install synpase(fresh - from playstore)

If restoring synapse through TB, restore only app.

Voila!! :)
[Nexus 4 Original Android Development] sgiannouris:
How about busybox? Or does CM has that bundled?
[Nexus 4 Original Android Development] fr3quency:
I believe CM has one built in, but you can download "Busybox on rails" from the Play Store and, I believe, it will tell you if you whether need busybox or not.
[Nexus 4 Original Android Development] atoyota:
I've looked up in the thread but I can't seem to find the solution to this.

I'm using the command "echo 1 > /sys/android_touch/doubletap2wake" to enable DT2W via tasker.

Now I need a task that disable it. What is the command to do that?
[Nexus 4 Original Android Development] fedexist:
I'm no expert, but try "echo 0"
[Nexus 4 Original Android Development] atoyota:
Well, sir, you may not be an expert, but surely you know better than me! :D it worked, and it was so obvious..that's what happens when I do something without knowing what I'm actually doing.

Thank you man!

Sent from my Nexus 4
[Nexus 4 Original Android Development] nicknc:
Thanks for the suggestion, but your assumption that I am flashing in an "improper" manner is inaccurate-- I already follow those steps in that order (which is arguably what most folks probably do anyway). Unfortunately, it does not make a difference on my phone.

Furthermore, I experience the same behavior with unleashed kernel, which has SuperSU and UCI built-in. In that scenario, your proper procedure wouldn't apply anyway.

Again, it's no big deal and easily fixed by resetting UCI via terminal in about ten seconds.
[Nexus 4 Original Android Development] Sblast:
What's the latest 4.4.4 AK kernel?
[Nexus 4 Original Android Development] gorilla p:
Check bit.ly/makostuff for older AK versions.

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] Sblast:
Thanks, but what's the latest I can use on Kitkat?
[Nexus 4 Original Android Development] gorilla p:
I finally created a thread for Makostuff. It is currently under construction, but you can find it here...

http://xdaforums.com/showthread.php?t=2987907

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sgiannouris:
I have V600 with SmartMax governor, -50 mV and 81Mhz Min frequency on SimpleAOSP Build 8.

Two nights in a row, I plug it in to charge through the night and I wake up to it being frozen, unable to resume from deep sleep, I presume.

The interesting thing is that through the day it is fine, and does that while plugged in :eek:

Do you suggest raising the min frequency? I did not have this problem with v.500 and the same settings btw.
[Nexus 4 Original Android Development] AndroidReborn:
Sweep2wake not working ....anyone?

Sent from my awesome Nexus 4 running SimpleAOSP with AK500. Bazinga!
[Nexus 4 Original Android Development] dantezinn:
Im facing some trouble when i make a call, i don't know if it's a rom or kernel problem.

When i make a call, i can't hear or say anything.

Purity 4.4.4

AK 360

Since i don't know the source of the error, i posted on both threads.
[Nexus 4 Original Android Development] CallMeAldy:
Are you using MultiRom? I bet it's not the kernel's fault
[Nexus 4 Original Android Development] nicknc:
I had the same problem on 4.4, even on stock kernel. It seems to be linked in my case to specific hybrid radio zip files. I have two phones, one affected, one not on KitKat. When I flashed the unaffected phone with the 33/104 radio copied over from my affected phone, it started acting up as you describe. When I flashed the previous radio (33/103, I think) it resolved. Flashing ANY of the older hybrid radios I had on my affected phone do not resolve it.

Updating to 5.0.x also seems to have fixed it. I tried the other fixes listed in other threads, including updating play services, editing some arcane sound file, reboot procedures, but none worked.

All I have found is that lollipop has it fixed and there seem to be a select number of hybrid radios that do not cause the silence issue.

It's definitely not the kernel- I tried a bunch.

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

Also, on my unaffected phone I do not have multirom installed, but still got silence after flashing that version of 33/104. Fwiw.

Pretty crappy issue, all in all.
[Nexus 4 Original Android Development] GragonV:
? I thought [5.0 - KERNEL v... can be used on 4.4.4 ? (I'm using version v.500 at the moment and going to update to v.600. Should I worry about anything?

and btw, I cannot file the change log of this kernel thread, would anyone mind show me :)
[Nexus 4 Original Android Development] dantezinn:
You saved me! Flashed radio 33/103 and its ok now! Thank you!
[Nexus 4 Original Android Development] nicknc:
Could you post a link to where you got the radio? Again, it seems to me like a few of the 33/103 radio zips are buggy as I have used at least one that did not work to fix the no in-call audio bug.

Also let us know if it returns. Mine was much more prone to this issue in the afternoon, strangely enough.

Glad to hear it seems to be working.
[Nexus 4 Original Android Development] gorilla p:
33/103 is outdated.

105 radio is available now as well as 33/105.

And none of the zips are "buggy". They're simple hybrid modem flashable zips.

You can get any of the hybrid modem images or AIO LTE enabler zip for 33/105 from makostuff

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] dantezinn:
bit.ly/makostuff

Is that the last one compatible with kk?
[Nexus 4 Original Android Development] nicknc:
Yeah, I've been using your awesome site for several months now. Very cool of you to do what you do.

As for the zips, some definitely cause a no in-call audio issue on 4.4 for me. Stock or hybrid- it didn't matter. Call it a bug or feature, it doesn't really matter. On my second mako I can reproduce it pretty reliably when flashing 33/102, 33/104 or 33/105 on 4.4. This is on stock ROM, stock kernel even. Tried .27 hybrids too to no avail.

Doesn't affect VoIP calls though-- just cell calls, and more often in the afternoon. Reboot will fix it for a call or two sometimes, but not always.

It doesn't happen on lollipop, at least yet...

---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------

It is, but the version on bit.ly was problematic for me on my 4.4 phone.
[Nexus 4 Original Android Development] gorilla p:
I think what you may be having trouble with is calling while using LTE, which I've heard a couple times. I don't believe it has anything to do with those files in general, bit perhaps your provider/region.
[Nexus 4 Original Android Development] nicknc:
Perhaps you're right, but I have two makos on the same network, in the same region (T-Mobile, NC). The one with 4.4 currently installed never had an issue until I updated the hybrid modem on it to 33/104 (using a zip pushed to it from my other mako). It instantly began having in-call audio issues. Reverting the radio instantly fixed it (back to the 33/103 that was on it). I did try disabling VoLTE and that didn't work either.

On my other mako, which is my primary phone, the 33/103 file I have on it ALWAYS had issues with in-call audio as did the 27 variants. Hence the reason I am a little suspicious about the actual zip files themselves. A few were pulled from your site, a few from the radio thread and a few from the N4 LTE modem app on Google Play. Unfortunately, I don't remember which ones came from where, but believe me, my desire to avoid upgrading to 5.0 was enough to try a number, including stock radios (which did not work either). The calling audio issue affected me here and also in Texas and Georgia, so particular regions don't appear to make a huge difference.

I understand that rationally speaking all hybrid modems should be the same, but different folks have created them, right? Maybe there's some errata in the zips with which I have problems that only affects some phones.

When I get my 4.4 mako back in my possession, I'll do a little more testing, but again, the 33/103 on my 4.4 mako works fine. The 33/103 on my 5.0 mako (which I got from a different place), however, had tons of in-call audio problems when I had 4.4 installed on it. This was on stock, with stock kernels, no build.prop edits (other than enabling LTE) and in areas with great coverage. I would literally finish a fully functional call and the very next call seconds later would be completely silent.
[Nexus 4 Original Android Development] gorilla p:
That is really strange.

I really don't use LTE because of the additional battery drain on this device, good speed of hspa+ and usually don't download enough for it to matter, unless I'm at home and I use WiFi.

I don't believe it will help with your audio issues, but there are some T-Mobile specific tweaks that may be useful to you.
[Nexus 4 Original Android Development] jacomail95:
Love the kernel boot logo, GPU voltages table and GPU conservative governor, actually it seems the only Lollipop kernel for mako that has them. What about the Unleashed Thermal LED indicator? Can i ask for it in a future release? Many thanks :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] poondog:
It comes from semaphore btw :)

You'll need the led trigger series of commits from stratosk and then modify the current thermal driver to work with it :P doesnt look too hard tbh