yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] xenyz:
Re: intelliplug

Since so many seemed to be interested, a correction to the above:

The threshold setting isn't for determining when to plug a CPU, that is determined by the profile setting and can't be modified beyond choosing a different profile.

It is actually used to determine when to unplug a CPU. It is a value, computed via bitwise operations from the thread capacity of the board, divided by total CPUs online. If the average number of threads on a single CPU is less than this value, the CPU is offlined.

So, setting a higher threshold would cause a CPU to be unplugged with more threads running (quicker), and a lower threshold would offline a CPU with fewer threads running (slower).

Still going through the code, but I saw that glaring error I made.
[Nexus 4 Original Android Development] gorilla p:
So I.e....

CPUs=4

Total max threads=1000 per CPU

If avg threads over 4 CPUs= 600 (2400 total)

Core3 goes offline because it can run 800 threads on 3 cores (2400 total)

The threshold tells it how soon to make that switch, essentially doing the same work with leas CPU cores?

Sent via Mental Telepathy
[Nexus 4 Original Android Development] ruicc:
Guys, Synapse is not working.

Install AK 333 L, then flashed latest UKM (2.7.2) and then Synapse.

Tried to open Synapse, and...NO UCI SUPPORT DETECTED...

Any help, please?

P.S. Nvm, get it working now.
[Nexus 4 Original Android Development] gorilla p:
Rather than leave the comment, perhaps you could edit it to show how you were able to fix your issue? This would benefit the community rather than having the opening statement say that something doesn't work...when it does.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] ruicc:
Sorry, gorilla p, my bad. What i've done was cleaning Synapse data in settings...Then restart Synapse and...worked. Dunno why it don't worked on the first time. SU permission was granted.

Since i'm using Android L, i thought the problem could be with UKM, some kind of incompatibility.
[Nexus 4 Original Android Development] gorilla p:
Yeah clearing data fixes most issues when switching Roms or kernels.

You can always remove synapse, delete synapse folder, reboot to recovery, reflash UKM, reinstall synapse.

That process will take care 9/10 issues if simply clearing data doesn't work.

A lot of people are just switching to UKM/Synapse and run into these random hiccups and idk if there's a place where these steps are clearly listed. However they have been went over time and time again in the UKM thread.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] hks18psigst:
Flashed 333L and got a bunch of yellow could it be a corruption in my download?
[Nexus 4 Original Android Development] paoton:
How do I activate the tuning provided in op?
[Nexus 4 Original Android Development] txuki2005:
Use synapse.

All fine here @ak

Thanks for this great stuff (this week using your kernel :) )

Arrivederci!
[Nexus 4 Original Android Development] xenyz:
Yes, it looks that way.

I made another assumption: that hysteresis value doesn't affect the sample duration in ms as I said before, it is used to bump up the threads allowed in the current profile for already online CPUs.

I have to take a closer look at this thing but for now I'd leave all default settings alone! :)

Does anyone know if faux posts technical details anywhere?
[Nexus 4 Original Android Development] T-luvR:
Hey guys i ttied both msm and intelliplug and I got far better and stable results with intelliplug ! Is it like this for everyone?! Or just me?! If so why every one like msm more?!
[Nexus 4 Original Android Development] montbazon:
I prefer intelliplug too.

Cause It is less agressive than msm.

I've got less heat, might be there more battery also.

Msm is soooooooooooo aggressive for light user like me haha[emoji13]
[Nexus 4 Original Android Development] stavca:
I prefer MSM because it's snappier with it, but it could be because I have set min 2 cores online
[Nexus 4 Original Android Development] gorilla p:
If using On demand, I'd recommend setting it to 1 core minimum. If you don't like that, try leaving 1 core minimum but max 2 cores boosted.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] ak:
new in testing

Next release will be with:

- f2fs update

- wheatley

- lazy

- topology

- arch power

- ecc

stay tuned.
[Nexus 4 Original Android Development] CallMeAldy:
You sir, deserve a cookie :P
[Nexus 4 Original Android Development] rirozizo:
[MENTION=3685904]ak[/MENTION] i gotta tell you. this is the first time i build a kernel in my life. so i need some help from a long time expert here since i know absolutely NOTHING about it, and just started learning it.

i want to disable some GPU (not CPU, but GPU) governors

i want to set default screen color calibration values

i want to set default interactive governor parameters values (interactive is already default gov in my case, just need to customize the gov's parameters like "hispeed_freq" and such)

if you can please guide me to the location of the files that i should change? or another method (like menuconfig for CPU)?

thanks!
[Nexus 4 Original Android Development] T-luvR:
If your using msm i suggest u set all 4 cores on at same time and decrease min to 162 U wont see any heat or battery difference but phone will be much smoother
[Nexus 4 Original Android Development] gorilla p:
Absolutely not. Having 4 core minimum active leaves every core online and is totally overkill, as is increasing the minimum from 81mhz to 162mhz.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] T-luvR:
Have u tried it?! Or just telling by theory?! If havent tried try ;) theory isnt always right !
[Nexus 4 Original Android Development] xenyz:
- [MENTION=4128576]bedalus[/MENTION] recent kernels have 4 cores always online and user reports say no difference

- lower minimum freq (81, 162, etc) can cause higher freq usage with most governors

- is it better to have 2 cores at 384 MHz or one core at 1026 MHz?

- If you can answer the above, what did you think was meant as 'better'?

The point is things aren't always intuitive when dealing with computing, especially so with low level systems. Tests and benchmarks are always best.
[Nexus 4 Original Android Development] Gallardo994:
Answering one of the questions, I can say, that less cores, but higher frequencies are always better if we speak about speed.
[Nexus 4 Original Android Development] TheNerd:]:
There have been many discussions in the Trinity, semaphore, and moob threads,and every single one came to the same conclusion. All four cores is perfectly fine for the device not "overkill". Some may notice a slight (very slight hit in battery) but a a boost in performance. So 1 you prevent wasted energy from constantly onlining/offlining cores. 2 prevent wasted energy and overhead by hotplug calculations.
[Nexus 4 Original Android Development] T-luvR:
Be sure more cores also all on will be better

---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------

Thats right but with some hotplugs its not good to have all 4 on

But with msm it will boost performance in cost of maybe 5 percent per cycle !

---------- Post added at 08:17 PM ---------- Previous post was at 07:55 PM ----------

What do u think [MENTION=3685904]ak[/MENTION] about this?!
[Nexus 4 Original Android Development] gorilla p:
I have found more than enough performance with on demand, 2 cores max boosted, 1 core min online, 162min freq.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] Gallardo994:
I have exactly the same setup. And 1sec for boost and core lock time and max 1 core if the screen is off.
[Nexus 4 Original Android Development] ak:
I think this is good ... And right but I have see in the bedalus thread after test you can loose by 5% - 10% of battery .... Buy I never tested enough ... [emoji4]
[Nexus 4 Original Android Development] TheNerd:]:
Having all 4 cores cancels out the hotplug. All four cores on will be the same across all kernels and all hotplugs. Hotplugs on and off cores so if all 4 cores on what's the point of the hotplug? Turning off hotplug does the same thing (all 4 cores on)

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

Honestly use whatever you want. AK kernel will still be awesome :)
[Nexus 4 Original Android Development] T-luvR:
Yep I agree I find it rocking on stock and gettin 5:30+ sot with 20 hour!!and never using msm my self i stick to intelliplug as in tests I did its more stable and it loks freq where needed ro be high so while gaming u dont get lag! But with msm some times it goes to lover and fastly increases maybe its cause my bad settings donno Its rocking and really customizable!

But about 4 cores on with some hot plugs it gives bug! Hotplug doesnt go well with it as some people reported :D
[Nexus 4 Original Android Development] xsasuke:
Can someone tell me if this is working with L b3p5? Or there is another updated zip that works?

Thanks.
[Nexus 4 Original Android Development] ak:
No. It don't work.

You can try to flash hellscreed and than AK.
[Nexus 4 Original Android Development] smartymcfly:
Does anyone know how to write an init.d script to to automatically have usb-otg enabled?

and addon.d script to keep the script on through ROM updates?
[Nexus 4 Original Android Development] ak:
You can use synapse. But have you tested otg? Work?
[Nexus 4 Original Android Development] smartymcfly:
I do use synapse on my primary phone, I also have a phone with cracked screen that is not responsive to touch. Which also has synapse. I haven't updated the kernel or ROM for sometime now, I think it is still on AK268 or 300ish. Sometimes synapse does not complete boot and otg will not be enabled. I set synapse not to update automatically so it wouldn't reset booting with otg or need require root permissions be granted again.

Yes OTG works, there is delay, but it does work, USB mouse and external flash drive via powered OTG cord. The phone is sort of picky on the order of pluging in phone to OTG-cable and otg-device and then connecting power last. Or vice versa. It needs to be in the correct way to work.
[Nexus 4 Original Android Development] ak:
I want to suggest an update to last kernel and synapse. :good:
[Nexus 4 Original Android Development] smartymcfly:
Synapse is updated, just auto update is off so that supersu doesn't ask root privileges and prevent synapse from booting correctly. And still even with supersu set to automatically grant root access and synapse updated there is still times when synapse boot doesn't complete enabling boot action which cancels OTG.

I am on v324-f2fs-auto on phone w/good screen that is http://mirror.lnx.im/android/mako/ak/.

I will asap, I am waiting for Joli nard to post an update to AK330-f2fs-auto version. With System(ext4), Data/Cache(f2fs)

I posted the question in the OTG thread also...
[Nexus 4 Original Android Development] gorilla p:
To ensure synapse has root

You can go to SuperSU settings...

Uncheck reauthentication

Check "enable su during boot"

Problem solved

You can set it to "grant" by default as well and there are no issues as long as you don't install sketchy apps from sketchy places.

You only have to approve root once.

Sent via Mental Telepathy
[Nexus 4 Original Android Development] T-luvR:
Wooooowooooooo:D it made my daaaaaaay

Huhuuuu I downloaded it as soon as it was up :D and im on it now :p one q my bin is 0!! But device is faster can I oc?!

If I helped thank T-luvR

---------- Post added at 12:54 PM ---------- Previous post was at 12:50 PM ----------

And the new logo is good but the old one was perfect! I enjoyed that logo more than everything in this kernel :/ can i apply that again with new kernel?!

If I helped thank T-luvR

---------- Post added at 01:03 PM ---------- Previous post was at 12:54 PM ----------

Are u sure this bining is correct! Im running on 1.9 now!! With no isue!! Also increased vol by 50(1.9=135) to aviod reboot and reboot is gone!:D

If I helped thank T-luvR

---------- Post added at 01:16 PM ---------- Previous post was at 01:03 PM ----------

Feedback nothing happened but i set the min 1.5 and max 1.9 ran an antutu and 20% in one running antutu!!!!:D lol :D im sure binning is wrong for me:D thanks a lot ak

I returned to previous kernel that gave me better score in all scales and was faster i donno why! Also the gpu worked better on previous for me

If I helped thank T-luvR
[Nexus 4 Original Android Development] txuki2005:
Thanks @ak

I am testing last version, missing stock GPU frequency (400mhz), i suggest, it is possible, to add interval 320-400-487.

Thanks for all!!
[Nexus 4 Original Android Development] gemj95:
v335 is working fine here, i'm gonna try "lazy" for a bit and see how it is working...

But... what about adding Bedalus's Preservative gov? it tryies to keep the phone at lower frequencies and ramp up only when is necessary avoiding overkill frequencies.
[Nexus 4 Original Android Development] fr3quency:
Awesome, f2fs fixes. Thanks @ak
[Nexus 4 Original Android Development] GruZone:
Will it work with android L [MENTION=3685904]ak[/MENTION] ?
[Nexus 4 Original Android Development] manulemaboul:
It will likely break wifi, be patient, the porting Team have created a kernel branch on their git so kernel dev would be able to merge their L fixes more easily, but they're still working on it ATM.
[Nexus 4 Original Android Development] iskandar1023:
can somebody explain to me what Arch power is?
[Nexus 4 Original Android Development] fr3quency:
From what I could find:

ARCH POWER

Significance: ARM Topology Awareness.

Arch Power patch causes arch dependent power functions to be used instead of generic high resolution timer ticks and double ticks.
[Nexus 4 Original Android Development] bart.found:
I remain on 324 for now.. I like stock GPU freq.. And don't need overclock.. Hope that next releases will have these features.. Thanks for you work ak!
[Nexus 4 Original Android Development] Rembi:
Oh my god oh my god oh my god.

Wysłane z Nexus 4 za pomocą Tapatalk.
[Nexus 4 Original Android Development] yellman:
There is no difference between update ak version and flash from stock to ak ? I have had v333L with UKM, Synapse. I only flashed 335L over and stuck on L boot animation. Should I follow update installation steps neither that I had 333L ?? I am sorry, long time haven´t used AK´s. Thank you for help.
[Nexus 4 Original Android Development] XsceneXhippieX:
i am thoroughly confused as to how you are finding the L versions of this kernel, i mean hellscore is great on my L rom in multirom right now but i prefer AK on 4.4.x based roms and would like to compare it with hellscore on the L dev preview, gonna do some searching in the thread in a bit but still, i cant find the L releases on the download page for the normal AK kernels and that confuses me when people are talking about the L releases is all
[Nexus 4 Original Android Development] Rembi:
For unknown reasons, revoke my Clockspeed: C

Wysłane z Nexus 4 za pomocą Tapatalk.
[Nexus 4 Original Android Development] Almayce:
Got kernel panic in last kernel whilst taking photos. Latest Mahdi. Running stock voltages and basically everything else too with minor changes. Here's the kmsg. What's the problem? The kernel runs very smooth by the way, gonna report battery later :)
[Nexus 4 Original Android Development] smartymcfly:
I already had it set like this, plus turned automatic update for synapse off, and made sure synapse is updated manually and setup synapse settings and for a couple reboots everything worked as planned, but for some reason synapse doesn't always start correctly disabling otg. Plus anytime I that flash an update to the ROM or UKM I likely need to reenable OTG. If I have an init.d script to enable it, then when ever I flash something I can have the init.d in an installable zip to make sure it is enabled on boot. And the addon.d would keep init.d script installed on ROM updates. The flash able zip would be used whenever a new ROM is flashed or every update without an addon.d script.

Will someone please help point me in the direction of writing an init.d script to have OTG enabled on boot?
[Nexus 4 Original Android Development] yellman:
" AK.333.L.MAKO.zip " its named on gdrive. Iam enjoying this kernel very much,also thanks to "gorilla p" for tips in synapse... so I could not run v335 on L version, won´t let me get over boot up. Nevermind, I´ll wait for later version more compatible with last version of L android. Currently I am on Beta 2 with AK.333.L with msm hotplug. Nice ! Thanks AK !
[Nexus 4 Original Android Development] chewu.pg:
Why is wheatley governor so choppy, isnt it supposed to be much like ondemand with proper utilization of c- states??? o.O
[Nexus 4 Original Android Development] KcLKcL:
Few pages back there was a discussion about more core & low freq vs less core & more freq

I did some research (googling, actually lol) and what I get is low freq & more core is more battery friendly than high freq & less core.

-----------

By the way, I'd like to ask.

I'm using my own compiled ROM (Fresh CM11 M8 with JustArchi's Android Optimizations, compiled with GCC 4.8)

With the stock CM Kernel (which I built using the Optimizations, including -O3, etc. but with GCC 4.7), wifi turns on instantly.

But with every other kernel I tried, whether it's AK, Hellscore, or SaberMod franco, my wifi sometimes won't turn on (it's just stuck on "searching wifi network..") and even can cause Settings to FC. Toggling it for a few times can fix it though but sometimes I had to puty phone in Airplane Mode a few times until it works again.

I know this is not AK kernel related since it happened on every kernel except stock but do you guys have any idea why? Does kernels built with GCC > 4.7 makes wifi go crazy? This happened since 4.4.3 I think, anyone having the same problem too?
[Nexus 4 Original Android Development] DontPushButtons:
I'm no developer or expert, but I think I recall reading in the justarchi thread about some of the different toolchains having hangups like that. Could just be part of his optimizations. Have you tried compiling any of those other kernels using his commits and your toolchains to see if there's any relation? Or is that a little further down the rabbit hole than you wanna go lol. :P
[Nexus 4 Original Android Development] Rembi:
How is it different from Wheatley lazy?

Wysłane z Nexus 4 za pomocą Tapatalk.
[Nexus 4 Original Android Development] KcLKcL:
Nah this wifi issue also happened when I was using LiquidSmooth, so it's not the optimization. Used the kernel included in LiquidSmooth also works fine when I was using the the ROM so I am sure I can say it's not due to the optimization.
[Nexus 4 Original Android Development] gorilla p:
This happened with the 4.4.4 update. Lots of posts with this question in the past 20 pages. Try flashing WiFi revert 443 fix zip

Sent via Mental Telepathy

---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------

These are the ideas I've been playing with for my profiles actually. Debating more cores/lower freq vs less cores/higher freq

Sent via Mental Telepathy
[Nexus 4 Original Android Development] kevinnol:
You got wifi working? or just using L without wifi?

btw if someone using 4 cores on low freq could report about battery life would really appreciate that :)
[Nexus 4 Original Android Development] yellman:
Wifi working all day long. Now am gonna try beta3-p5 and trinity until ak fix wifi issues.
[Nexus 4 Original Android Development] yellman:
3-4 SOT auto brightness UV+OC+MSM+force gpu rendering in 2D. Depends on usage with these settings. Ak 330 on L beta2. Very quick response,no reboots lags in 2-3 days.
[Nexus 4 Original Android Development] kevinnol:
So wifi works on beta 2 but not on 3?

-

Wow that's some heavy underclocking, well if it's to your liking nice. bet the battery life is awsome haha

you should be cautious with the 81mhz step most of the time when it settles down to 81mhz it will ramp up to 300+ because of the 'load'
[Nexus 4 Original Android Development] manulemaboul:
Nah, if you do nothing, it stays on 81mhz, when you read a post here or a text elsewhere for exemple, it sits peacefully at 81. The trap is -100mv everywhere, -100 to the 384mhz default voltage is often as low as your SOC can go, so it tends to freeze and reboot with -100 at the 81 default voltage.
[Nexus 4 Original Android Development] kevinnol:
In my case i can't go below 270mhz, if i use 81 mhz it ramps up even doing nothing (using ondemand)

Used perfmon to make sure
[Nexus 4 Original Android Development] Rembi:
intelli conserwative profile & 1944mhz ondermand is incredibly fast: D while at 4.5 h on the screen

Wysłane z Nexus 4 za pomocą Tapatalk.
[Nexus 4 Original Android Development] beelzebulx:
Thanks AK for v. 335! Great performance so far, Antutu benchmark on v. 324 was 21969, increased to 23537 on v. 335!
[Nexus 4 Original Android Development] gorilla p:
Bit.ly/Makostuff updates

:cool:Bit.ly/Makostuff Update:cool:

Added AK 335 Kernel :good:

Added UKM 2.7.2 :good:

Updated build.prop tweak doc. - Removed problematic/redundant tweaks - Added T-Mobile specific section

Added Synapse Profiles

AK 335 - Battery

AK 335 - Battery/Balanced (exp.) :confused:

AK 335 - Balanced

AK 335 - Performance
[Nexus 4 Original Android Development] arffrhn:
Edit: Just me not reading properly.
[Nexus 4 Original Android Development] xenyz:
logger is disabled on boot. To enable, as root:

echo 1 > /sys/module/logger/parameters/log_mode

To disable again, echo 2 (not 0, as per usual)
[Nexus 4 Original Android Development] arffrhn:
Thank you. Sorry I must have missed that part. Shame on me. [emoji21]
[Nexus 4 Original Android Development] ak:
news

oneplusone is on the way guys. :D

thanks a lot to

@Shambola
[Nexus 4 Original Android Development] txuki2005:
oneplusone?

[MENTION=3685904]ak[/MENTION] is no better, make one kernel - gamers edition (with overclock) and other version - normal edition (stock max frequencies):p

just a suggestion:D
[Nexus 4 Original Android Development] nadavar:
Lucky you, those invites are hard to come by
[Nexus 4 Original Android Development] poondog:
And spend double the time compiling and uploading, plus supporting two kernels at once in this thread plus flo kernel? I think its better for one kernel here.. Just my two cents
[Nexus 4 Original Android Development] bart.found:
I appreciate this suggestion too! :P

---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------

This is right too.. but at least I'd like to set stock GPU frequency if I want.. I love 330 ak kernel!! It fits perfect to me! It has all the features I need, but the newest versions are too extreme for my usage! XD
[Nexus 4 Original Android Development] ak:
This is a exp version, i have compiled with overclock enabled. Next release will be normal. :D
[Nexus 4 Original Android Development] piasek1906:
AK-Piasek.TWO.JW for Android 4.3

Based od AK-Piasek.ONE.JW

Support Trickster MOD GPU Governor control

cpufreq: intellidemand: add new power_suspend pm driver

cyanogen_mako_defconfig: enable POWERSUSPEND

powersuspend: new pm kernel driver for android w/o early_suspend

cpufreq: intellidemand: update two_phase_freq to 1242Mhz

cpufreq: intellidemand: update to version 4.4 Nexus 5

msm: kgsl: Add touchboost to trustzone governor

Using in My phone and all work properly ;)

P.S. Using someone else Android 4.3?
[Nexus 4 Original Android Development] piasek1906:
Try AK-Piasek.TWO.JW

Support GPU governor in Trickster MOD.

Change governor to performance/simple and Try. In Real Reacing 3 and Emulator NDS no lags
[Nexus 4 Original Android Development] Targaeryan:
Which ROM? Kernel doesn't affect DPI as far as I know. Its the ROM.
[Nexus 4 Original Android Development] llevo3:
wi-fi disconnecting, clean flash KK111 at gnome 11/06, art enabled
[Nexus 4 Original Android Development] Rycon33:
Hi guys, I'm a new AK kernel user and I'm using it with gnome's KK rom and I'm wondering if there's an app there that can tweak the color display also. (I'm only familiar with faux kernel, he had an app for color tweaking).

TIA

Tapatalked from my N4