yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] xenyz:
Go through /etc/init.d/00ak

Use find and replace and change 1026 to something like 810, 1728/1512 to 1026, 1350 to something like 810, 918 to something like 702. You're kind of on your own trying to drop the frequencies down so low but try things out and see how it works. You might even be on to something.
[Nexus 4 Original Android Development] iRefleX202:
Could this cause problems?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] xenyz:
Yeah, a slow Nexus 4 :laugh:

If you just want 1026 MHz max freq and not to screw around with interactive, change gov to ondemand and run what I posted here in the terminal.
[Nexus 4 Original Android Development] iRefleX202:
Haha that's what I don't want. I want the balance between battery and performance but with this kernel I only get perfomance.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] xenyz:
Best bet is to try default settings with ondemand gov from Semaphore. Delete /etc/init.d/00ak, reboot, set gov with Synapse. It likely has the best chance of longer battery life, but you can't have both. It's like a fast car that's also fuel efficient, it just can't exist.
[Nexus 4 Original Android Development] PityOnU:
The ROM is the Google factory image and it is entirely new and clean. However, I will attempt to flash an AOSP build and see where that gets me. I will report the results here.
[Nexus 4 Original Android Development] barome:
Thanks [MENTION=3685904]ak[/MENTION] ;) Yes Github is magic and so we look together what we want to add to our own kernel ;)
[Nexus 4 Original Android Development] ak:
This is not true .... How you can determinate this?

I never see here a single post with screenshot of bad battery life.

no false information, please.
[Nexus 4 Original Android Development] TheKnux:
You guys are awesome. ;)

Sent from my 1961 XP-755
[Nexus 4 Original Android Development] gorilla p:
I agree, while this kernels default settings are geared towards performance, there are plenty of settings available for you to change in order to prioritize battery life. Maybe you should check out my battery life optimization settings on bit.ly/makostuff

Sent From My Google NeXuS⁴
[Nexus 4 Original Android Development] Almayce:
I got a question, mister. Should I flash the tardis even if I'm on psx? I read somewhere that some roms are already optimized the best they can (psx among them)
[Nexus 4 Original Android Development] ak:
op

New section is up:

Q: How i can optimize performance and battery life?

thanks to @gorilla p:

[FONT=Century Gothic][SIZE=2] [URL="https://drive.google.com/folderview?id=0B77BTW0zStYCSTRIYWpZQS1nOWs&usp=sharing"][B]Link[/B][/URL][/SIZE][/FONT]
[Nexus 4 Original Android Development] iRefleX202:
Ok. But why Is it my battery life is bad? Why Is it that always like 3 cores are locked at 1.35 ghz? Am i the Only one who has that problem? What am I doing wrong?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] TheNerd:]:
Psx is optimized
[Nexus 4 Original Android Development] ak:
I dont have this problem. :highfive:

can you check synapse? do you have?:

- min 1

- max 4

- boost 2
[Nexus 4 Original Android Development] iRefleX202:
Ya

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] ak:
Strange ... new build is near with some new enhancement ... and i have added @xenyz optimizations.
[Nexus 4 Original Android Development] surtrafl:
Over the last versions my cpu is way too erratic, this was taken after using chrome and on screen off.

I reverted to 237 to test without the ramp thing.

Even if I set event history and update rate to higher numbers it will behave erratic, ramping when no load is present.

I'm on CM11 snapshot M6.
[Nexus 4 Original Android Development] iRefleX202:
Ok but for now Which settings do you use?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] ak:
I can not understand why you do a revert to the old kernel when you just change the governor. this is really strange.
[Nexus 4 Original Android Development] ak:
it isn't difficult to change and revert to ondemand ... :fingers-crossed:
[Nexus 4 Original Android Development] aviz1911:
Don't know where i'm doing wrong

Getting these errors while compiling with arm-eabi-4.8

And these while writing to .config file

Can anyone help me please :angel:
[Nexus 4 Original Android Development] ruicc:
@ak

Any plans to make this kernel F2FS compatible?
[Nexus 4 Original Android Development] Almayce:
It is.
[Nexus 4 Original Android Development] ruicc:
It is compatible?
[Nexus 4 Original Android Development] Almayce:
I believe I just said that :D
[Nexus 4 Original Android Development] Pollie81:
something strange here.. (just installed better battery stats to find the cause but ever since v 243 i'm having android system wakelocks.

i'm using it on Mahdi rom and yesterday i even tried a fresh install, almost impossible that it has something to do with my settings.. i flashed so many roms and kernels en never had any serious wakelocks. lets see what bbs says.. anyone else having this issue?
[Nexus 4 Original Android Development] ruicc:
:) I believed in you, but i was trying to search for an answer from the ak himself...
[Nexus 4 Original Android Development] surtrafl:
Went to an old kernel because I had the 1.35Ghz ramp problem. I wanted to test why the cpu was so erratic. Even if I change to interactive/conservative/whatever it will hit all speeds even if I have 10% load across all cores, even on screen off.
[Nexus 4 Original Android Development] Jeremy:
Anyone having intermittent wifi issues? Am on the latest modem
[Nexus 4 Original Android Development] warfexion:
No flickering when disable HW overlay is checked in dev options.
[Nexus 4 Original Android Development] Targaeryan:
No issues. Did you try disabling WiFi optimization in the WiFi advanced menu? Its known to slow down WiFi speeds. Either that or its your internet connection itself. :thumbup:
[Nexus 4 Original Android Development] piasek1906:
Use trickster mod

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] saint_cow:
Anyone having issues with no touch input on reboot? Happening to me every other reboot. Doesn't do it without this kernel, could it be faux clock app?
[Nexus 4 Original Android Development] baliriot:
103 works fine so far with rascarlo's rastakat :good::D
[Nexus 4 Original Android Development] spupuz:
is device administrator under security still broken?
[Nexus 4 Original Android Development] baliriot:
still can't enable android device manager in device administrator
[Nexus 4 Original Android Development] nachordez:
Yup!

Anarkia needs sources freed to work on that (seems SElinux problem)

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] Dan1234567890:
Is it just me, or you cannot select only s2s in trickster mod, but the app changes its value in s2w and s2s...I would prefer s2s only, I am worried that s2w consumes too much battery...

Can I change value in some file manually, by es file explorer...or by terminal?
[Nexus 4 Original Android Development] spider623:
SELinux code is free, he needs the new binaries and the final stock kernel
[Nexus 4 Original Android Development] Gnome:
Yup, we all need those binaries... Sadly it might take weeks...
[Nexus 4 Original Android Development] okanb3:
Well, is there any 4.4 rom for daily usage?
[Nexus 4 Original Android Development] ak:
No ... you can't enable single feature for s2. :fingers-crossed:
[Nexus 4 Original Android Development] tmorterlaing:
I'm so sorry if this has been resolved, but I've read at least 20 pages of this thread and did a search and can't seem to find anywhere:

What is this CAF thing all about, why is it good and is it worth the hassle of staying with Cyanogenmod for?
[Nexus 4 Original Android Development] emanoj.i9103:
anarkia1976, The KK kernel seems to derp the device administrator functionality in aosp as well as n5 port, can you please look into it, if not already, Thanks!
[Nexus 4 Original Android Development] paulo_cv:
I've had it yes also after a long time with no use the phone wakes up but the touchscreen is dead. I went back to the Roms original kernel to test if it's the kernel or the ROM.
[Nexus 4 Original Android Development] Targaeryan:
Please read a few posts above. Its been mentioned many times already. I shall mention it again. Anarkia needs the n4 kitkat binaries to fix it. Sources will be dropped after a few days/weeks.

---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------

Use @#GNOME's build with ak kk kernel. Its good for daily driver.
[Nexus 4 Original Android Development] Glowing_Potato:
Using AK kk.103 with 4.4 MAKO-odexed.NEXUS 5 port V3 makes screen really sensitive while charging. Any way that i can fix it ? is that a ROM issue ?

Thanks in advance.
[Nexus 4 Original Android Development] piasek1906:
AK-Piasek.103.JW V1 = Ak.103JW + Franco Gamma Control + Double Tap 2 Wake - s2w/s2s

AK-Piasek.103.JW V2 = Ak.103JW + Franco Gamma Control with s2w/s2s
[Nexus 4 Original Android Development] Almayce:
Well why would he? he put it for everyone to see in the op, so u might just wanna be glad that at least I did answer you, instead of scolding you that you didn't read the op :P
[Nexus 4 Original Android Development] xenyz:
You'll find that your device is never really idle, even when it appears to be doing nothing. It's always up to something.

When you were testing, you said you ran Chrome and then ran the monitor? You might be surprised to learn that Chrome uses 5-10% CPU, while in the background, even while 'closed'. And if you were sitting on your home screen and have the Google Now launcher, Google Now was waiting and listening for an audio command. These are just a few things, if you'd like to see more, run this command in the shell to find out what your CPU is up to.

$ top -m 5

Edit: You're also aware there's an input boost, so when ever you touch the screen one CPU will be at 1350 MHz?
[Nexus 4 Original Android Development] ruicc:
Mate, before post my question i was reading the OP, and i didn't find anything...I think i need glasses! :D

I thought that someone could post this question, and i was trying to see if ak answered....

But, many thanks for your help on this, i'm maybe moving to F2FS when things were more compatible.
[Nexus 4 Original Android Development] Almayce:
Well it isn't in op per say exactly, it's in the second post under "os:" I was thinking as well to move to f2fs,but then I realized it's too much hassle and no real gain. I read some posts and topics and it didn't really convince me + if it were so darn better then all the people would already be on it, right? Which is not the case, so I'm sticking to ext4 for the time being.
[Nexus 4 Original Android Development] ruicc:
Well, i read only the first... that's why i missed it :p

That's my point of view...already asked on "Recovery and Rom for All-F2FS 28/04/14" thread about CWM Touch recovery F2FS compatibility and i got a "NO" as an answer...i really dislike TWRP recovery.

So, i'm thinking like you...sticking with EXT4 for the time being. I need more informations to show me that F2FS is far better than EXT4.

Thinks from Samsung are suspicious for me....
[Nexus 4 Original Android Development] ak:
fix for 4.8:

anarkia1976@anarkia1976 ~/android/AK-xGenesis $ git diff cc6503b2d2adc704264fd686edb270dfeb514231 a361f6b9ccdcecacdb88b5c9b1a6fce9785e9b56

diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c

index 50f73be..0462e65 100644

--- a/net/bluetooth/hci_conn.c

+++ b/net/bluetooth/hci_conn.c

@@ -403,7 +403,7 @@ void hci_le_ltk_reply(struct hci_conn *conn, u8 ltk[16])

memset(&cp, 0, sizeof(cp));

cp.handle = cpu_to_le16(conn->handle);

- memcpy(cp.ltk, ltk, sizeof(ltk));

+ memcpy(cp.ltk, ltk, sizeof(*ltk));

hci_send_cmd(hdev, HCI_OP_LE_LTK_REPLY, sizeof(cp), &cp);

the second error it isn't a problem.
[Nexus 4 Original Android Development] xenyz:
OK, check this out, it's basically a port of myfluxi's Nexus 5 settings. I tried to get his intentions of the frequencies right, as we have 384-1512 and they have 300-2265. I was careful to make sure the steps were matched up either above or below their related steps, but of course it isn't exact. They might have to go a bit higher as the N5 has a more powerful processor too.

I haven't really tested it for very long but it seems worthwhile for others to try out what myfluxi did with his interactive and boost settings.
[Nexus 4 Original Android Development] gorilla p:
We've established that "optimized" is an extremely broad term. These roms that people say are optimized appear to have optimized bionic but not the Qualcomm optimized dalvik patch which tends to improve performance fairly significantly.

If you rum quadrant benchmark and check your CPU score (not overall score) and it is under 22k, then you do not have the Qualcomm optimized dalvik patch.

Perhaps some devs have some other dalvik optimizations that they implement, but I have yet to find any that compare with the Qualcomm optimized dalvik patch.

However as stated in the Qualcomm optimized dalvik thread, almost all custom roms have a better optimized bionic.

Sent From My Google NeXuS⁴
[Nexus 4 Original Android Development] Almayce:
So I installed it, I think the aosp version. It booted fine. I didn't wipe cache & dalvik though, should I go back and do it?
[Nexus 4 Original Android Development] Nekator:
Had a reboot on 241 Version. Reboot reason kernel panic.

https://drive.google.com/file/d/0B-YTTKZdx1XEM0lBVzN5STQ3RVU/edit?usp=sharing

https://drive.google.com/file/d/0B-YTTKZdx1XEV3VjRDB5RDFNLW8/edit?usp=sharing

https://drive.google.com/file/d/0B-YTTKZdx1XEYU91TEZuZUFzaTA/edit?usp=sharing

https://drive.google.com/file/d/0B-YTTKZdx1XEak9HVUN5clZIMDQ/edit?usp=sharing

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] gorilla p:
When I installed it, I wiped prior to installing and then everything went smoothly, but idk if that's the recommended procedure. If youbrun quadrant benchmark and you're getting CPU scores (not overall scores) in the 25k-35k area, it was successful.

Sent From My Google NeXuS⁴
[Nexus 4 Original Android Development] ak:
too uv:

[24620.652099] L1 / TLB Error detected on CPU 0!
[Nexus 4 Original Android Development] Nekator:
Good to know thanks for your fast reply.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] TheKnux:
Changelog for v254?

Sent from my 1961 XP-755
[Nexus 4 Original Android Development] scarcry:
I'm on LiquidSmooth 3.1 for which the CM AK kernel is necessary (non CM kernel results with frakked up colours).

I got about 13500ish CPU quadrant score so decided to try the optimized dalvik cm zip. I made a nandroid and just flashed the optimized dalvik zip for cm,wiped cache + dalvik and rebooted and got stuck with a bootloop (got as far as the android is optimizing apps screen though).

Booted back into recovery (cwm 6.0.4.6 touch) and tried flashing the non cm optimized dalvik zip (not the aosp one) and wiped both caches again but never got past the boot animation screen.

Just restored my nandroid and am going to try again.

I'll try wiping both caches prior to flashing the dalvik zip this time just don't know which zip to use on LiquidSmooth though.

I figured to go with the cm one since I also used the cm version of [MENTION=3685904]ak[/MENTION] kernel.

Mako running LS on AK Exodus kernel
[Nexus 4 Original Android Development] ak:
new kernel

[XGENESIS KERNEL v.243]

A kernel based on CAF CM branch.

aosp: AK.254.EXODUS

cm: AK.254.EXODUS.CM

[INSTALL STEP-BY-STEP]

- go to recovery

- flash kernel

- reboot

- install synapse

- enjoy ak

- finish

changelog:

- linux 3.4.91

- new toolchain 4.9

- linaro fixes

- bfqv4

- interactive tuning

- hotplug fixes

- topology fixes

- ecc

synapse merged with last n4ukm.

see git.
[Nexus 4 Original Android Development] Nekator:
So greate work (as always).

Just a little think to "improve". When i enter a backup name i first have to aply it reather then just click backup. Otherwise the name wont be set.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] scarcry:
Thanks again Stefano for the ever ongoing improvements on your great kernel!

Just flashed 254 cm kernel.

Really like the synapse updates,however just wanted to report restarting synapse just shows an empty black floating bubble and synapse never really restarts for me.

Mako running LS on AK Exodus kernel
[Nexus 4 Original Android Development] Targaeryan:
Yay! New version! :D
[Nexus 4 Original Android Development] Nekator:
I dont have this Problem. Tested it after ur post. But i m not on cm Version.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] scarcry:
thanks for confirming. I did install the N4UKM 1.3 zip a while back while on an older [MENTION=3685904]ak[/MENTION] kernel but from what I get from [MENTION=3685904]ak[/MENTION] is that his kernel updates also are merged with the N4UKM updates so I figure having flashed that older 1.3 zip should not be an issue.

Mako running LS on AK Exodus kernel
[Nexus 4 Original Android Development] Darkmasterhk:
ondemand

Somehow everytime I change to ondemand (both) my first core sticks to

1,5ghz and won't clock down.

Using aosp kennel on latest slimkat.

Settings done using synapse.

Anyone an idea why this is happening?

I can provide a log as soon as I'm home.
[Nexus 4 Original Android Development] bart.found:
Just Flashed 254

-I setted suspend frequency to 486MHz (under this value I had delays when waking up the device on 243)

-Noticed that high speed freq in interactive governor is now 918MHz (before was 1350) I used to set it to 1134 cause is the frequency that on my device can handle the lowest undervolt (-200mV), but I'll give a try to this new settings (at 918MHz I undervolted -175mV)

-As in the 243 version I'm not able to set interactive governor for GPU in Trickstermod, it always auto-revert to ondemand (actually work ondemand and performance)

-During charge frequency goes to its minimum value (81MHz) rarely, while on battery it works fine.
[Nexus 4 Original Android Development] ak:
inline:

-I setted suspend frequency to 486MHz (under this value I had delays when waking up the device on 243)

its normal

-Noticed that high speed freq in interactive governor is now 918MHz (before was 1350) I used to set it to 1134 cause is the

frequency that on my device can handle the lowest undervolt (-200mV), but I'll give a try to this new settings (at 918MHz I undervolted -175mV)

true

-As in the 243 version I'm not able to set interactive governor for GPU in Trickstermod, it always auto-revert to ondemand (actually work ondemand and performance)

interactive isnt implemented

-During charge frequency goes to its minimum value (81MHz) rarely, while on battery it works fine.

its normal
[Nexus 4 Original Android Development] ak:
no problem for me ... tested with carbon nightly.
[Nexus 4 Original Android Development] ak:
no problem for me with carbon ... synapse restart work.
[Nexus 4 Original Android Development] bart.found:
Thanks for fast reply and great kernel! Is too complicated/useless to introduce the stock GPU frequency (400MHz)? I'm not an overclock enthusiast.

PS: sei anche tu siciliano? XD
[Nexus 4 Original Android Development] chewu.pg:
When i try to switch from hells doctor to ak kernel, i am stuck in a bootloop, hells is totally ok but ak just bootloops... Anyone can help?
[Nexus 4 Original Android Development] jimyiak:
Dirtyflash your rom..

sent by neXus 4 kitkat-ed ?
[Nexus 4 Original Android Development] ak:
No, you can underclock to 320mhz.

PS: sono lombardo. :fingers-crossed:
[Nexus 4 Original Android Development] CamoGeko:
I'm back on my Nexus 4 for a couple of weeks while my One M7 is in repair.

Need to flash an updated AK kernel :D
[Nexus 4 Original Android Development] ak:
How do you feel with M7? what do you think of M8?
[Nexus 4 Original Android Development] CamoGeko:
I love it! I'm happy to say its the best Android device I've ever owned, with the Samsung Galaxy S2 following closely in 2nd place. :)

Not sure about the M8 coz I don't really like the look of it, but if the rumours about the M8 Prime are true and it really will have the 810 SoC then I will definitely go for that one.
[Nexus 4 Original Android Development] Targaeryan:
Its 805.. 810 was a typo it seems.. My sister in law uses the m8.. Its pretty good. Compared to my bros m7, not much difference.. Its more metal than m7.. Dual camera.. The sound is a bit fuller with less bass compared with m7 with beats.. Battery is pretty good with m8.. Performance seems similar if not the same in terms of ui and what not.. Sense 6 is quite nice and minimalistic..
[Nexus 4 Original Android Development] sidnoit22:
Can we donate even when we got have unverified paypal? :angel: @ak
[Nexus 4 Original Android Development] Utkarsh-ezzo:
Hey [MENTION=3685904]ak[/MENTION] may be you already know this or I am wrong somewhere but I am facing this problem with synapse

i have flashed v254 right on top of v243, and I have restarted synapse...

ezzo
[Nexus 4 Original Android Development] CamoGeko:
Well you never know, it was posted on Twitter by evleaks I think. Pretty sure HTC will try and make the M8 Prime the most powerful device thats available currently, but I have some doubt considering the One Max wasn't like that.

The frontal speakers are a joy on the M7, quite possibly my favourite feature! Especially when using [MENTION=4388232]ZeroInfinity[/MENTION]'s SRS sound mod.
[Nexus 4 Original Android Development] Rembi:
AK, you will still overclock to 1944mhz option?

Wysłane z Nexus 4 przy użyciu Tapatalk.
[Nexus 4 Original Android Development] apb_axel:
It happens sometimes, but it's a problem with synapse not our scripts. It's already been reported to the app developer but in the meantime just exit/enter the app to fix it. From my testing it only happens when you open the app and starting browsing immediately, what I do is wait until the superuser toast goes away so I know It loaded up correctly.
[Nexus 4 Original Android Development] 3n3rg1c:
Not really needed n4 is good with 1.6 /1.5GHz. I get antutu score around 23k in 1.6 ghz and 24k+ on 1.7 ghz and I don't see major performance improvement at 1.9 GHz. It will only eat ur battery
[Nexus 4 Original Android Development] Rembi:
1.9GHz eats batteries? I'm at 1.9 ghz ondermand and GPU conservative doing 3.5 - 4 hours per display.

Wysłane z Nexus 4 przy użyciu Tapatalk.
[Nexus 4 Original Android Development] Targaeryan:
https://mobile.twitter.com/evleaks/status/468364611008602112

Sadly no 810.. Evleaks corrected himself. :(

Yeah those front speakers are amazing.. Blows my n4 out... Sigh... :P
[Nexus 4 Original Android Development] montbazon:
You can't. Because of the new toolchain.

Gesendet von meinem Nexus S mit Tapatalk
[Nexus 4 Original Android Development] azrash:
Great to see that 243 is out. I will flash it soon.

With 241, I had two random reboots. The second one happened minutes after the first. I have linked them here.

Would be glad if someone can shine some light on what happened, and some pointers on how I can prevent it from happening again.

Cheers

Running CM M6

https://www.dropbox.com/s/lavqh9r9wbktago/2014-05-20_23.36.zip

https://www.dropbox.com/s/8r9150fnzepx2f0/2014-05-20_23.42.zip

Logs were pulled using SysLog app.
[Nexus 4 Original Android Development] chewu.pg:
These new qualcomm chips SUCK... Instead of moving to different CPU architecture(cortex-a57; ARM v8 instruction set) they just bump clocks of everything... And resault is battery life that sucks... And iphone 5s dulacore arm v8 at 1,2ghz beats new snapdragon 805 2,5ghz quadcore chip.. Conclusion, dont buy new qualcomm phone till they rethink and move forward.
[Nexus 4 Original Android Development] Targaeryan:
That's what I was thinking as well.. I want to wait for the next gen 64bits before upgrading... Hopefully it'll be here soon :fingers crossed: so far I don't see any interesting phones yet...
[Nexus 4 Original Android Development] CamoGeko:
Can't enable s2w in trickster anymore. :(

Sent from my baked potato