yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Targaeryan:
That's default behaviour. He might've misunderstood your post. He only added those features for now since its missing from trickster, more should be added along the way when he's free. For now you gotta use trickster along with synapse.
[Nexus 4 Original Android Development] GFXi0N:
Makes sense. Understood.... Thanks!
[Nexus 4 Original Android Development] poondog:
Cheers mate, thanks for the reply

One more thing.. Your prevent sleep works by only allowing wfi and nothing deeper?
[Nexus 4 Original Android Development] show-p1984:
Huh?

My "prevent sleep"?

"Only allowing wifi and nothing deeper"?

Huh?
[Nexus 4 Original Android Development] poondog:
I mean wait for interrupt?

https://github.com/showp1984/bricked-flo/commit/35ecdad0bb925e26924b43f1309b62791581f305

Seems you are disabling some deep sleep functionalitty. My understanding was that s2w worked only in wait for interrupt, or when the device was not sleeping at all
[Nexus 4 Original Android Development] show-p1984:
That only prevents the touch screen and it's driver from sleeping, which are required to work in order to even get an interrupt. Nothing more.

Deep-Sleep isn't touched.
[Nexus 4 Original Android Development] mammenj:
Version 70, unable to connect to wifi even after dirty flashing AOKP ROM, anyone else?
[Nexus 4 Original Android Development] stavca:
I'd like to ask you 2 things ak...first is, how to get OTG working?? I really tried with OTG and USB Y cable but haven't had luck :(

and the second is: do you plan to again release version with the new prima drivers?? I mean, is it hard to build 2 versions of your kernel, one with stock and another with prima drivers?? I had much better experience with older version with prima...
[Nexus 4 Original Android Development] GAME ON:
same here bro :crying:
[Nexus 4 Original Android Development] mammenj:
Back on v58 and all works great
[Nexus 4 Original Android Development] GAME ON:
yup bro.i revert back to v58 and wifi works again. :crying:
[Nexus 4 Original Android Development] dirwdirw:
063 070 broke my wifi, back to 058
[Nexus 4 Original Android Development] y3mita:
Using 70 exp kernel with intelliplug and intelliactive pretty smooth thanks ak for such a buttery kernel
[Nexus 4 Original Android Development] 0.0:
I'm on the 70 cm kernel. Does the simple governor get applied for any of you? I also can't configure it. When I hit apply in trickster, the GPU governor goes back to ondemand

Sent from my Nexus 4
[Nexus 4 Original Android Development] Targaeryan:
Its not present as far as I know. Only ondemand. Trickster shows the option of others but the governor itself isn't present.
[Nexus 4 Original Android Development] GFXi0N:
Anyone knows the difference between the tcp congestion methods?
[Nexus 4 Original Android Development] Targaeryan:
Wikipedia has a lot of info on the different methods.
[Nexus 4 Original Android Development] GFXi0N:
I need an ELI5..... Wikipedia explains very technically, while I found no thread explaining the pros and the cons una simple way. I'm asking about this because I have problems with my wifi at home
[Nexus 4 Original Android Development] xenyz:
So, it turns out my Nexus 4 was panicking and soft rebooted. I happened to catch it in the act this time. :) The uptime is not reset when this happens, which led me to believe it had been up and running the entire time.

I'll post the logs in a bit.

Here's some good news: I tweaked intelliactive with a mix of Franco's settings and it seems to be good. I edited my earlier post with the new settings.
[Nexus 4 Original Android Development] wisefreakz:
http://xdaforums.com/showpost.php?p=36663293&postcount=27
[Nexus 4 Original Android Development] ak:
yes it work

people with old kernel when switch to v070 have 2 possibility:

- reflash rom

- flash unistaller

and then wifi work again.

Search in the thread .. i have reverted the prima to old one.
[Nexus 4 Original Android Development] xenyz:
I'm not sure if anyone else is following along, but I made one more change to the setup linked above. The bad news is the interactive gov was never meant to run at 81 MHz. The good news is I have it at 270 MHz for 3/4 of the time while idle. I think in order to utilize these nice lower clock speeds effectively, we need CPU governors designed for them.
[Nexus 4 Original Android Development] Targaeryan:
You should post a link to your settings... And if you're talking about intelliactive, mine uses 81mhz most of the time :)
[Nexus 4 Original Android Development] FrozenLord:
With AK 70 my Nexus 4 is running well again :)

The WiFi bug is still gone and the minimum frequencies don't get stuck at the boost values after some time.

This is the first time that my mako lasts a full two days on a single charge with mild usage.

Great job AK! :)
[Nexus 4 Original Android Development] y3mita:
I started using your recommended settings but when I use video with hangouts after a couple of minutes it FCs

I got it working by using freq of. 81-1.5

And the following settings and hangouts behaves good now

Also my WiFi is perfect using slimkat latest
[Nexus 4 Original Android Development] Targaeryan:
I see. I had a half an hour hangout session today and no issue, no random reboots generally.. I've tried these settings with AOSPAL, Kaos, cfx, slimkat.. Gonna try it with PAC next..
[Nexus 4 Original Android Development] michelemascia7:
How to enable intelliplug in fauxclock? I use v63 :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] y3mita:
You can't you need trickster

---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------

@targaeryan yep not sure if it's because of the high frequencies or maybe your governor settings are too low for my device. Anyhow it's all good now.
[Nexus 4 Original Android Development] Targaeryan:
These are my settings btw
[Nexus 4 Original Android Development] y3mita:
I see I was using 800 for hispeed freq
[Nexus 4 Original Android Development] xenyz:
I did, in my own quote. I edited my earlier post.

Relevant section:

Random 20 m usage:
[Nexus 4 Original Android Development] Targaeryan:
:thumbup:

My 18 mins usage
[Nexus 4 Original Android Development] xenyz:
Now try min 270 MHz and you'll see it spend a lot less time in the higher frequencies.
[Nexus 4 Original Android Development] XsceneXhippieX:
i changed my settings to the ones in your screenshot and it may be placebo but i feel as if my scrolling is smoother with them, i find that odd considering the values i changed should have made my phone run at lower clock speeds in certain conditions. if that makes any sense.
[Nexus 4 Original Android Development] maxver0:
https://www.dropbox.com/s/j51dmz023zr3v35/last_kmsg (1)

Exp 070 + slimkat 3.4

Im using lastest multirom as well. I think this kernel is compatible? Default uv that comes with kernel and 81mhz to 1,5ghz. CPU temperature below 50C. I haven't monitor battery temperature but it wasn't hot for me and phone was 'idling' with dolphin browser enabled before reboot.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] xenyz:
Wrong thread, that is a Hells-Core log. :)
[Nexus 4 Original Android Development] maxver0:
Stupid me. I was using secondary rom with AK KERNEL. And I took last kmsg from primary ROM. If it isn't right log I might have lost one. Because after reboot I swapped roms. Then launched android and uploaded it.

https://www.dropbox.com/s/cv16ridun73pc9s/last_kmsg

edit:

I have noticed a lot of :

I think it is because of disabling "boost_enabled" of mp-decision control. But I have intelli-plug enabled, so I think it shouldn't interfere.

As my governor I use intellidemand.
[Nexus 4 Original Android Development] xenyz:
Man, that is a Franco log. :)

Look on line #2 or #3 for kernel id.
[Nexus 4 Original Android Development] maxver0:
Yeah I noticed this too but I thought that's impossible :silly:. Last time I was using Franco was in November, by that time I flashed plenty of kernels as well as few stock image flashes. So the only explaination which comes to my mind is that when I was swapping roms this log some how was created by recovery (multirom lastest).

Never mind then. I will just wait till another error will occur. I really love the smoothness of this experimental.
[Nexus 4 Original Android Development] 0.0:
I am on v70 CM version. When eco mode is activated, does anyone experience extreme lag from time to time? I think eco mode may be broken. I never experienced horrible lag with eco mode on faux.

I also have thermal throttling, but that shouldn't affect it since I keep the temp limits on the higher side.

Edit: I also turned on intelliplug and turned off mpdecision and turned off touch input boost
[Nexus 4 Original Android Development] cpanos:
What governor do you use? All Eco mode does is disable cores 2 and 3 and make the device dual core.
[Nexus 4 Original Android Development] 0.0:
I use intelliactive

I know what eco mode does. But it makes my phone lags a lot when turned on. As I've said above, I never experienced a lot of lag with faux on eco mode :(

Edit: I also turned on intelliplug and turned off mpdecision and turned off touch input

Sent from my Nexus 4
[Nexus 4 Original Android Development] TheNerd:]:
Turn on MPdecision or touch input then
[Nexus 4 Original Android Development] xenyz:
Ran her down today. 100% wireless and dim screen, but everything else on (sync, location, now, etc.)

Mostly reddit, browsing and email but I probably watched about 20 m of video as well.
[Nexus 4 Original Android Development] Targaeryan:
Nice! [MENTION=3118524]xenyz[/MENTION],what ROM are you using?

@ak, I used the cm version with the PACman ROM, the sabermod version, there's no call audio.. Stock PACman kernel, which is the cm kernel has audio.
[Nexus 4 Original Android Development] xenyz:
Stock 4.4.2
[Nexus 4 Original Android Development] nokiagye:
Ak you want make something good find a solution to remove the stupid bionic patches from the slim

---------- Post added at 07:14 AM ---------- Previous post was at 07:13 AM ----------

I try many days I am disappointed

---------- Post added at 07:15 AM ---------- Previous post was at 07:14 AM ----------

Many bootloops
[Nexus 4 Original Android Development] ak:
So .. do yuo see into kmsg problems .. the version is the same of faux.

I dont understand what is the problem :confused:
[Nexus 4 Original Android Development] 0.0:
Idk what happened...but I flashed an update to my ROM that I built, and all is well. speeds are fine. not much lag. crazy eh? lol
[Nexus 4 Original Android Development] nokiagye:
The problem is simple we cannot flash anymore the motox patches it's very important for me and others and solution no where

It's slim (feature)feature xaxa
[Nexus 4 Original Android Development] ahepas:
..but why are they so important..?
[Nexus 4 Original Android Development] Targaeryan:
[MENTION=3685904]ak[/MENTION] , I used the cm version with the PACman ROM, the sabermod version, there's no call audio.. Stock PACman kernel, which is the cm kernel has audio.
[Nexus 4 Original Android Development] ak:
The problem is only with pacmam ROM?

Do you have link to source of this kernel?

Thanks

Akiller revolution!
[Nexus 4 Original Android Development] Targaeryan:
Yeah only with it.. I'm trying to locate the source, but not having luck.. Let me try to look some more..
[Nexus 4 Original Android Development] ak:
No problem ... When I have access to my box I can check the source of PAC kernel

Akiller revolution!
[Nexus 4 Original Android Development] cpanos:
Its not eco mode, i believe its intelliactive. I had lag as well, same setup as you, especially when apps were updating everything would lag horribly. I switched back to ondemand and everything works smooth now.

I now have ondemand governor, eco mode on, intelliplug on, mpdecision off, touch boost off, min frequency 270Mhz, max frequency 1.3Ghz, some undervolting, and the phone is mostly smooth, with excellent battery life.
[Nexus 4 Original Android Development] Utkarsh-ezzo:
hey [MENTION=3685904]ak[/MENTION] , v0.7 is flying on my new mako, without any wifi issue,...

thank you buddy...

---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------

and yeah those new gpu binaries are awesome, makes it more smooth...
[Nexus 4 Original Android Development] maxver0:
Any idea why trickster doesn't apply settings after reboot?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] Targaeryan:
There's a settings drawer on the right (swipe from right edge in trickster) and then tick kernel settings on boot :)
[Nexus 4 Original Android Development] maxver0:
Sure I did tick that. I even cleared cache of trickster but it still doesn't work.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] Targaeryan:
Usually it takes one minute to set.. Weird that it doesn't.
[Nexus 4 Original Android Development] ak:
i have see tuning before for intellidemand can you try?

thanks man.
[Nexus 4 Original Android Development] ak:
can you send to me by PM your last config for intelliactive?

thanks a lot man
[Nexus 4 Original Android Development] ak:
op updated

SCREEN EDGE FIX APP

Screen edge fix with s2w/s2s/dt2w - Link

Thanks a lot:

@maxver0
[Nexus 4 Original Android Development] Targaeryan:
I couldn't find the source :(
[Nexus 4 Original Android Development] rirozizo:
why need the sources? It's an app

Sent from my Nexus 4
[Nexus 4 Original Android Development] Targaeryan:
Hahhaahh no.. Not for the app... I was talking about PACman ROM kernel sources.. Ak knows :) :p
[Nexus 4 Original Android Development] ak:
No source probably use the default one with modified ramdisk.

but.

pacman is aosp kernel based, right?
[Nexus 4 Original Android Development] Targaeryan:
No.. They're using the cm kernel.. Flashing aosp kernel gives the screen the colour issue. Flashing cm version works.
[Nexus 4 Original Android Development] misterk267:
+1

I feel that these patches have a positive impact on my phone, but i find recent kernels' and Roms' updates don't work with them.

This kernel is excellent and honestly, I'm perfectly happy without the patches if I can run AK, but being able to run both would be even better.

In the end, I'm happy with whatever direction this kernel takes. This is the best kernel out there and I'll use it regardless of my ability to use the patch.
[Nexus 4 Original Android Development] dEris:
OTG is not working with this Kernel on OmniROM - flashed a different kernel, rebooted and it works. Anyone know why it isn't working? Mako
[Nexus 4 Original Android Development] nokiagye:
It is my friend it is.
[Nexus 4 Original Android Development] cpanos:
Otg works fine with this kernel and slimkat.
[Nexus 4 Original Android Development] nokiagye:
If you want this tell me
[Nexus 4 Original Android Development] anurag549:
my minimum cpu frequency resets to 918 mhz even when i change and save it in trickster is it normal behavior?
[Nexus 4 Original Android Development] TheNerd:]:
That's normal
[Nexus 4 Original Android Development] anurag549:
so is it actually working on 81 mhz? why does is gets changes to 918 mhz in trickster because of touchboost?
[Nexus 4 Original Android Development] TheNerd:]:
Yes touch boost aka mpdecision boosts the core 0's frequency to 918 MHz when you touch the screen. This provides the butter and more overall smoothness/speed in the ui. Core 1,2,3 get boosted too but the min frequency shown by kernel control apps depend on core 0
[Nexus 4 Original Android Development] xenyz:
PM sent I think, but it doesn't appear in sent items. Let me know if you didn't get it.
[Nexus 4 Original Android Development] ryaniskira:
Slow for me as well. Takes about 4 minutes to install a 20mb app

I'm using XGENESIS.70

Nexus 4 Aospa 4+
[Nexus 4 Original Android Development] stavca:
not working also on PAC ROM with AK kernel
[Nexus 4 Original Android Development] ak:
The problem is Google play

[MENTION=784850]akiller[/MENTION]
[Nexus 4 Original Android Development] ak:
This is the only ROM I don't know why ...

[MENTION=784850]akiller[/MENTION]
[Nexus 4 Original Android Development] stavca:
ok, tell me if I can help you somehow with finding solution :) I'd like to have OTG working with this ROM...
[Nexus 4 Original Android Development] ak:
My comment is related to audio.

OTG work without problem

[MENTION=784850]akiller[/MENTION]
[Nexus 4 Original Android Development] Targaeryan:
Ak your signature is actually mentioning someone, as in another member (akiller) because you put the '@' symbol so every time you post, it mentions that member, so you might want to change that part :)
[Nexus 4 Original Android Development] Gnome:
TRUE!!!
[Nexus 4 Original Android Development] ak:
thanks a lot ... i have insert @ by mistake
[Nexus 4 Original Android Development] Targaeryan:
Anything new you're cooking up? :p :angel:

Hahhahaha :D
[Nexus 4 Original Android Development] 0.0:
[MENTION=3685904]ak[/MENTION] I am on v70. I set my min to 81mhz, but it ends up going to 270mhz and it never goes back to 81. I am not too sure if that's a bug and if you are aware of it. just letting you know :)

edit: for some strange reason, it went back to 81...
[Nexus 4 Original Android Development] Utkarsh-ezzo:
Explained just few posts back, It is because of touch boost , whatever min freq you set will get applied to all the cores except core 0 , and trickster shows the freq of core 0,

if you want to set core 0 also to a lower frequency then goto specific tab in trickster then in MP decision control then in boost freq and set core 0 freq to desired frequency..
[Nexus 4 Original Android Development] ak:
There isnt any problem ... mpd is consolidated because is present into kernel from begin.
[Nexus 4 Original Android Development] ak:
yes i have merged function for set a whitelist for lmk, process or app into this list aren't killable by system.

I have merged [MENTION=1143630]osmosis[/MENTION] synapse for doing this from the app directly.

stay tuned.
[Nexus 4 Original Android Development] Targaeryan:
Btw.. Call audio works with 11/3 new sabermod pacman build so no worries about my previous comment.
[Nexus 4 Original Android Development] Gnome:
What version of SM Toolchain are they(PACMAN) using?
[Nexus 4 Original Android Development] 0.0:
I turned off touch boost

I have mpd turned off. But it seems to be ok...

Sent from my Nexus 4
[Nexus 4 Original Android Development] Targaeryan:
I'm not too sure. Its unofficial build by the mako maintainer.. Probably 4.8 :)

[MENTION=5334172]Gnome[/MENTION] its 4.9
[Nexus 4 Original Android Development] Gnome:
Can you link me to it please... :)
[Nexus 4 Original Android Development] Targaeryan:
http://xdaforums.com/showthread.php?t=2668912

[ROM][OFFICIAL][KitKat 4.4.2][mako] PAC-man Build-1 [CAF]

Second post
[Nexus 4 Original Android Development] Gnome:
Weird, SM 4.9 ain't available to public, we are the only ones that have the new one. My HH Kernel runs SM 4.9. I wonder where he got that.
[Nexus 4 Original Android Development] Targaeryan:
I think he's using it from AOSPAL, its available there right?

Edit: because he credited paranoid saberdroid
[Nexus 4 Original Android Development] Gnome:
[MENTION=3685904]ak[/MENTION] sorry for this OT. Lol!

[MENTION=5403224]Targaeryan[/MENTION], It's either he's one of our team members or he is using the Old TC, AOSPAL isn't using 4.9 yet since it has issues with the ROM, "in call audio" to be specific. SM 4.9 is stable only for the kernel but not for the ROM. And the new SM 4.9 is only available to us via Team Email. That's why I'm wondering... :confused:
[Nexus 4 Original Android Development] Targaeryan:
Ah I see. But the latest build doesn't have any issues.. The previous build only had call audio issue with aks kernel. Stock kernel and hells kernel worked fine. That was for the 9/3 build. The 11/3 build has no issues.
[Nexus 4 Original Android Development] Gnome:
Maybe he's using the old one OR he is using a different 4.9 TC, anyways we're off topic already. Lol! Thanks [MENTION=3685904]ak[/MENTION] keep them kernel's rocking! You the man!
[Nexus 4 Original Android Development] ak:
No problem guys ...

Ak in the house :)
[Nexus 4 Original Android Development] maxver0:
Hey, experimental 070 works great so far. Thank you for your work.

I applied additional -50 uv (-100 total) my phone froze and rebooted shortly after. When phone booted up it applied SAME settings succesfuly. Could you take a look at last kmsg to check if it was the case?

https://www.dropbox.com/s/iezdjnnbg329x5w/last_kmsg (2).txt

Woah, another one - that was quick gonna increase up UV to -75.

https://www.dropbox.com/s/uzhnpymsmkfz2yg/last_kmsg (3).txt
[Nexus 4 Original Android Development] ak:
no problem ... kernel panic related to undervolt:

L1 / TLB Error detected on CPU 3
[Nexus 4 Original Android Development] Targaeryan:
Edit: sorry! It booted :p
[Nexus 4 Original Android Development] xenyz:
Updated intelliactive settings, it seems to run fine for me. Anyone else tried it out?
[Nexus 4 Original Android Development] Targaeryan:
I applied the settings.. I'll try it out and give some feedback :D
[Nexus 4 Original Android Development] maxver0:
How about the second last kmsg? reboot reason was watchdog

https://www.dropbox.com/s/uzhnpymsmkfz2yg/last_kmsg (3).txt
[Nexus 4 Original Android Development] ak:
For me ok .... I want to create synapse profiles with users tweaks for governors. The code is open source ... On my git ... Help is very appreciated ...

Ak in the house :)
[Nexus 4 Original Android Development] ak:
I don't see problems related to kernel

Ak in the house :)
[Nexus 4 Original Android Development] xenyz:
OK, I will look into Synapse and dust off my github acct.
[Nexus 4 Original Android Development] maxver0:
When I set simple governor and press apply after 2second governor switches back to ondemand. Any idea why is that happening? Same thing on Mil 064 and exp 070
[Nexus 4 Original Android Development] xenyz:
Simple, there is no simple governor. :)
[Nexus 4 Original Android Development] maxver0:
I'm talking about GPU governor which should be obvious.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] jolinnard:
Looking the code there are only 2 GPU schedulers:

...
#define TZ_GOVERNOR_PERFORMANCE 0
#define TZ_GOVERNOR_ONDEMAND 1
...

[MENTION=3118524]xenyz[/MENTION] is right.
[Nexus 4 Original Android Development] 0.0:
must be a trickster app problem for showing simple and interactive governor for GPU
[Nexus 4 Original Android Development] poondog:
Not a problem.. Its hardcoded go show all the time the governors. On stock kernel It shows all 4 too

It's normal
[Nexus 4 Original Android Development] RealSlimShadyMC:
He asked for TCP congestion methods, not IO schedulers
[Nexus 4 Original Android Development] poondog:
Tcp--> no difference from what I've tested and seen.. I just use Westwood because it has the best benchmark scores

Not replying to you.. Just to the question and thought I'd quote you for context :)
[Nexus 4 Original Android Development] XsceneXhippieX:
so if setting the read ahead buffer size to 1024 or even 2048 increases I/O performance according to everything ive ever read on the subject, why is stock custom kernel/rom setting still set to 128? im just curious at this point, wondering what the benefit to keeping it low may be that ive never heard about at this point. and im currently using AK kernel so i figure this is the best place to ask that i know of
[Nexus 4 Original Android Development] TheNerd:]:
I heard the lesser the number the better throughput and the higher the number the better latency. You have to find a balance.
[Nexus 4 Original Android Development] sidnoit22:
Kernel 3.4.83 is out so AK time to merge. Hehe. :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
I believe it's vice versa, but the concept is right.

FWIW, Faux123 recommends 384 KB.
[Nexus 4 Original Android Development] TheNerd:]:
Haha I think you were the one that explained io in the AK thread. Thanks for clarifying