yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Remoteconcern:
The app experience pro will allow you to overclock no matter the kernel limitations. If suggest that's a better way of doing things while keeping it safe for the majority. Paid app though!
[Nexus 4 Android Development] Archmag3:
this includes the wifi fix, i mean notification delay thing ?
[Nexus 4 Android Development] ckret:
i changed "enable all load" to 500, cause i had stuttering in games

but now it feels good. dont feel a huge difference between before and now

but i guess that 500-530 would also do it
[Nexus 4 Android Development] Remoteconcern:
Great, I wasn't sure about games. Maybe if thraceramin uses those values in the next test build we can get some feedback.
[Nexus 4 Android Development] rlaw:
What games were you experiencing stuttering in?
[Nexus 4 Android Development] veyka:
I tried them for a bit, and performance did seem to suffer, mostly as it seems to take to long to bring extra cores in.

I would still like to see mpdecision as an option, or at least a test build! Hehe
[Nexus 4 Android Development] thracemerin:
Yeah, hasn't been a good couple of weeks for me with being out of town and then dealing with some personal issues so I haven't had the time or mental focus to get and much testing as I'd like done. As a result there haven't been many changes or alphas lately, but hopefully I can get back to a more regular schedule soon and get the mpdecision test ready as well. :)
[Nexus 4 Android Development] veyka:
Yikes, no rush (just a bit of mild joking around), hope things clear up for you! (Its just a kernel afterall).

I shall spend a bit fiddling with hotplug values in the meantime see what I can come up with.
[Nexus 4 Android Development] ctfrommn:
Hope things improve..... Let me know if you need any help with anything :)

Sent from my blazing bionic Nexus 4
[Nexus 4 Android Development] Remoteconcern:
Ah that's a shame. I haven't really noticed any slow downs really, but I do have my boost pulse duration at 500000, as I have a theory that the 0.2s is too short and the constant quick ramping is counter productive.
[Nexus 4 Android Development] veyka:
That is true, is that 5s? The theory is I suppose that when the phone is hot plugging or ramping it can't do work, maybe 1s or 2s would also be worth a try!

The main thing I noticed is that sometimes the phone seems to get stuck with two cores on at max freq and it wont hotplug in another one.

Also, how does the boost pulse work? Does it make sure there is a minimum of two cores on, or does it hotplug an extra two cores? As it seems at times the phone just seems to add another two cores on touch, where as mpdecision for example just keeps two on at 1026mhz

I will give your hotplug values another spin with a longer boost pulse!
[Nexus 4 Android Development] Remoteconcern:
No, it's actually 0.5 seconds, as compared to the default of 0.2 with motley and 2s with MP.

Touch brings a second core online, always. This hotplug driver still seems to randomly bring more online sometimes, not sure tweaking the exposed parameters are enough to fix it. Frankly I'm appreciative of the effort that went into coding it but I'm not sure it's the greatest driver.

If it's getting stuck at Max frequency without bringing more cores online, reduce enable all load threshold. Maybe try 500 as suggested?
[Nexus 4 Android Development] MotoRaph:
Can somebody tell me which b1 is needed for the new miui Roms? Is it based on the Rom from which the miui Rom is installed? Like cm?
[Nexus 4 Android Development] ckret:
coming from harsh and going through different kernels and roms

and now i am sticked with sabermod (superfast) and motley

i think that mpdecision was the best solution so far. sparksco has it in his kernel too

didnt try his one, but since my flatmate has also a n4 is sticking with sabermod and the kernel too and

having a good batterylife without tuning anything, i kinda get the feel that mpdecision is by far the best solution

hope to get version from thracemerin with mpdecision

that would be so great. like to see the difference
[Nexus 4 Android Development] veyka:
I did try bringing the Max load threshold down to 500 but it still seem to flick cores on and off, and the extra core on touch leaves you on weird situations where you end up with 3 cores on and it seems to get confused about if it needs to offline a core or not.
[Nexus 4 Android Development] Ace42:
Has anyone done battery tests for mp decision?
[Nexus 4 Android Development] xdaShex:
Hey guys, I am currently on the last "motley kernel" and wanna switch to the "m+ kernel" any prerequisite steps needed to do the switch ?
[Nexus 4 Android Development] sirxdroid:
Flash B1 and then B7 right away, don't need to reboot in between.
[Nexus 4 Android Development] xdaShex:
Ah ok, Thanks for the quick reply!
[Nexus 4 Android Development] thracemerin:
It looks like MIUI uses a vastly different ramdisk from both stock and CM, its highly likely that neither version of B1 will work on it. Ultimately I think I should just dynamically modify the ramdisk with an anykernel script rather than packing my own ramdisks, but that's a huge pain in the butt to get working. I'll take a look at the MIUI ramdisk when I get a few mins and see what I can do.
[Nexus 4 Android Development] veyka:
Newest WIP has been working perfectly for me so far!

There's two new patches merged in CM to fix some iffy stuff with the LED, when you get a chance!

Hope things have gotten a bit more relaxed as well.
[Nexus 4 Android Development] thracemerin:
Yeah, just need to get internets for my build boxes again and I'll be good to go, should be mid next week sometime because the cable company is being needlessly slow. Also have an mpdecision version mostly done but I can't release tests since I can't push it to github yet. Good things are coming though :)
[Nexus 4 Android Development] Kearkan:
I don't know if this is kernel or ROM related, but since flashing this and latest pa nightly, my network bars are constantly grey, same for on WiFi. However everything is connected and working fine.
[Nexus 4 Android Development] antih3ro:
Never had or heard about such problems with this kernel, so I think it is ROM related.
[Nexus 4 Android Development] veyka:
Gray bars just means that you can't connect to Google's servers, it happens sometimes, its a rom or Google issue.
[Nexus 4 Android Development] Kearkan:
But I am connected, that's what I'm saying.
[Nexus 4 Android Development] veyka:
Try cleaning Google play services data and rebooting, whatever it is, it's an issue with the connection to Google rather than a kernel issue.
[Nexus 4 Android Development] FeintDoxx:
This happened to me too before. It went away after a reboot, but if that doesn't work by all means try what veyka suggested.
[Nexus 4 Android Development] pa.pn2:
[MENTION=592646]thrace[/MENTION]

could you make a bootable version for miui please?
[Nexus 4 Android Development] thracemerin:
It's on the list, as soon as I have internet for my build machines I'll get it done.
[Nexus 4 Android Development] thracemerin:
Good News: I have access to a linux machine that can do Build 8 for me, it's just going to be the same as the Alpha, but it'll be an official build, thanks to everyone who tested this for me.

Bad News: I'm using my 3G hotspot as internet so it's very slow and I can't upload the sources for the mpdecision test yet.

Anyway, Build 8 will be available relatively shortly and hopefully if the damn cable folks show up today like they claim we'll have more stuff to release later today.
[Nexus 4 Android Development] Kocai:
First of all, I'm sorry if this sounds insensitive considering your situation. If you have the time, can you please find out about the CAF patches to improve 3G/data that franciscofranco merged. I'm testing his nightly build #155 and my data speed seems faster.

Thank you in advance.
[Nexus 4 Android Development] thracemerin:
I believe he uses the same set I do, I will have a look for the next alpha.

Side Note: B8 should be on goo.im now or very shortly if it's not. (I updated to the 2013.06 toolchain, the alpha was 2013.05 :D) Happy Flashing :victory:
[Nexus 4 Android Development] thracemerin:
For those waiting patiently for MIUI support, I have pulled the ROM down and will try to pack a boot.img for build 8 later, I will need some people to test since I don't personally run MIUI, more details when I'm done doing this.
[Nexus 4 Android Development] hp13:
how do i flash this kernel ? instructions a bit confusing.

do i flash base then latest build? or just latest build? i am running stock kernel as of now. i wanted to flash a stable build. thanks.
[Nexus 4 Android Development] thracemerin:
Flash Build 1, then Build 8.
[Nexus 4 Android Development] hp13:
ok so in future, i just flash newer builds ? or i have to do both base 1 + build 9?

and what is the difference between CM and stock base 1?
[Nexus 4 Android Development] thracemerin:
If you are on at least Build 1, you can just flash the newest build. You only need to flash Build 1 if you are on a kernel other than this one.

Example: You can go Build 7 directly to Build 8, but you can't go from the Stock kernel to Build 8 without flashing Build 1 first (well, you might be able to, but I can't guarantee what might happen so I wouldn't advise doing it).

CM version is for CyanogenMod based ROMs, stock is for everyone else.
[Nexus 4 Android Development] thracemerin:
OK, MIUI build 8 is in the wip directory, if you are on MIUI you only need to flash this.

Note: I am unable to test this as I don't run nor do I have any intention to run MIUI, if it doesn't boot I will do my very best to assist, but please make a backup before you try.

Note 2: I pulled the ramdisk from the port by [MENTION=4311896]luiseteyo[/MENTION] here: http://xdaforums.com/showthread.php?t=2312677 I don't know if it will work on other versions or not, it should but MIUI is strange and I can't guarantee it.
[Nexus 4 Android Development] hp13:
ok great. that makes a lot more sense. Thanks
[Nexus 4 Android Development] sirxdroid:
What's the difference between the normal, CM and MIUI builds? Just the ramdisk? Just curious if you could say a couple of words on how these ramdisks are different. Thanks!
[Nexus 4 Android Development] thracemerin:
Yes, just the ramdisk.

For reasons that I can't fully explain certain ROMs use different sockets, etc... to do certain communication, as a result one ROMs ramdisk won't boot another ROM. I'm working on fixing the anykernel script so this won't be necessary anymore but I'm not done with this as yet.

Example: CM uses common ramdisk components for all CM builds and then just adds a small script to do the specific functions that differ between devices, since the stock/AOSP ROMs don't have this setup they won't initialize the system correctly for Mako, on the other hand CM expects it to be initialized in this way so the stock ramdisk won't initialize some specific CM components.

This can be fixed with a more extensive anykernel script that would do things like disable mpdecision and thermald in any ramdisk, I just haven't had the opportunity to get this working correctly yet, once I do there will be no need for specific ramdisks.
[Nexus 4 Android Development] jazzboyrules:
Hi thracemerin, thanks for continuing motley's work. I am posting just to let you know that there are people like me who follow the updates on this kernel regularly, even if doing so passively :)
[Nexus 4 Android Development] Remoteconcern:
Same here. There are users, the kernel just works so well I don't feel inspired to much discussion. Looking forward to mpdecision test though.
[Nexus 4 Android Development] thracemerin:
Thanks Guys! :D

I've always taken a lack of discussion to mean that the kernel works well, if you follow the other threads all you see is whining about this micro stutter or that mini lag, since nobody is doing that in here I just always assumed such problems didn't happen on this kernel. :p

Plus, I do appreciate that people don't constantly post their battery screenshots in here, that has always annoyed me.
[Nexus 4 Android Development] Kocai:
I just flashed build 8. Got the same 3G speed with Franco's #155. So no need to look at it if you're busy.

Sent from my Nexus⁴
[Nexus 4 Android Development] mastrgamr:
Veerry interesting. Is this specific to this kernel or do you know if it's the same deal with all kernels??
[Nexus 4 Android Development] thracemerin:
Seems to be a hardware lock of some sort, [MENTION=4110652]ctfrommn[/MENTION] did more looking at this than me, he may have tested other kernels. If my theory on the hardware lock is correct it is unlikely that other kernels could have bypassed it.
[Nexus 4 Android Development] sirxdroid:
[MENTION=3332811]faux123[/MENTION] used to have something in his kernel FAQ to the effect that Qualcomm said the CPU was unstable at frequencies below 384 Mhz. It seems that statement has been removed from the thread and the faux kernel now allows going down to 164 Mhz. It's anyone's guess whether the CPU really runs at that frequency or it's just a number the sysfs reports. [MENTION=4195844]show-p1984[/MENTION] who develops the Bricked kernel showed that he could "run" at 27 Mhz :)
[Nexus 4 Android Development] thracemerin:
There is pretty close to 0 chance the OS would be stable at all at 27MHz, and I think show-p said there were errors in the logs about not actually being able to set 27MHz too. Not saying they don't work/aren't set, my testing was extremely unscientific, but it seemed a reasonable inference from the data I had. I can also confirm with a reasonable amount of certainty that the battery usage at 384MHz and 192MHz is the same under similar usage, and 192MHz should use considerably less power (definitely noticeable over a 100-1% drain).
[Nexus 4 Android Development] show-p1984:
Ah another one switching to gitlab's continuous integration platform :)

You might want to consider pulling my pull requests since they are a bit slow when it comes to merging stuff. The pr fixing the trace log will just modify the install manual, you will have to do that stuff mentioned in there since Active Record sucks :)

Fix build trace only showing the first 2^16 bytes (using utf8 even less)

https://github.com/gitlabhq/gitlab-ci/pull/167

Add additional autoscroll button below the buildtrace.

https://github.com/gitlabhq/gitlab-ci/pull/168

Allow all visitors to see the build detail page if the project is public.

https://github.com/gitlabhq/gitlab-ci/pull/169

The result should then look like this:

http://buildmachine.zapto.org:88/

Clock discussion:

My findings have hardened over the last few weeks and I will remove my 192Mhz step too. There is absolutely no gain on the s4, whatever the reason.

Mpdecision discussion:

Qcoms mpdecision is getting a better and better solution (it was pretty much crap in the beginning, so I guess any improvement is major :p), sadly, because of being not configurable and there being absolutely no source it sucks.

If you want to use a hotplug in-kernel solution that works similar, yet is fully configurable and opensource you might want to look into my mpdecision :)
[Nexus 4 Android Development] codingrobot:
My data connection seems to drop constantly. I have a 5-bar signal.

I also did a clean install of CM 10.1 RC5 and build 8 of the kernel. Radio is version 54.

Almost no one seems to have a similar problem. Does anyone have any tips how to solve this. With Franco 155 I didn't have the problem.
[Nexus 4 Android Development] alen1901:
No gain? How? I mean, 192mhz is much lover than 384, and it has less voltage. So when phone is on idle with screen on (eg. reading), or you are looking at some pic, browsing), it will spend more time on 192mhz and therefore save more battery, no? And system is stable, at least on fas and faster binned chips.

Sent from Sparkling Nexus 4
[Nexus 4 Android Development] thracemerin:
Should yes, but the evidence suggests that it does not actually save any battery which is one of the reasons (along with statistically identical benchmark scores) that I think that 192MHz or any frequency lower than 384MHz is not actually being set regardless of what the kernel thinks is being done and what is being reported by the sysfs. Sadly the only way to test for sure would be to break an N4 open and hook it up to some appropriate testing equipment, which while tempting seems a waste of $400 right at the moment.
[Nexus 4 Android Development] thracemerin:
I think I may have screwed up and not removed a patch from B7 that I removed in the Alpha after people reported some drops, the funny thing is I had the drops in B7 and don't on B8, so I'll have a look into this again.
[Nexus 4 Android Development] thracemerin:
I think I have the one that makes it so the whole output appears in the window, I noticed that was a fix you submitted, the others I don't have. I have to set gitlab_ci up on a new buildbox so when I do I'll add them, thanks!. :D
[Nexus 4 Android Development] soumoks:
Thanks for this awesome kernel! tried it today for the first time and loving it,one of the snappiest kernels out there :)
[Nexus 4 Android Development] Proda:
Hi folks,

So I've been using this kernel with CM10.1 (always latest version). Excellent performances. But recently I noticed that I can't beam anything (I would always get message Beam did not complete). Testing was performed with Nexus10 with latest CM10.1 nightly (CM10.1 kernel also).

Today I installed latest CM10.1 nightly on my Nexus4 (June 19th) but didn't flashed this kernel over it and now Beam works as it should be.

Btw, a couple of days ago I tried beaming a photo to another Nexus4 with Stock kernel and it didn't work also.

EDIT: I should say that beaming from Nexus10 to Nexus4 was failing too. But now it works

Sent from my Nexus 4
[Nexus 4 Android Development] Remoteconcern:
I'm not 100%, but I don't know how much beam is related to the kernel. I doubt NFC is touched. My beam works fine anyway, stock ROM.
[Nexus 4 Android Development] IAmAN00bie:
I second show's suggestion. If we should go with an mpdecision like implementation, his solution is the closest to it while also giving us a crap load of customization.
[Nexus 4 Android Development] thracemerin:
If we're gonna stick with custom hotplugging, I don't think I'd change from thalamus' version to another, the mpdecision musings were more to see if the stock hotplug solution had something that was worth giving up the customization for. Not saying no, but I don't think the current system is bad or in need of replacement, it just seems that a lot of the mpdecision haters have rethought their initial opinion or at least tempered their criticism so I wanted to see how it was since I haven't used an mpdecision kernel in ages.
[Nexus 4 Android Development] atulalvenkar:
4.2.2 has a bug where the Bluetooth hangs while starting. This causes beam to fail. A reboot fixes this issue.

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
I'm reasonably sure NFC is fully in the OS, even if it's not I haven't tinkered with it at all. I just tested and can beam between my N4 and N7 without issue.
[Nexus 4 Android Development] Ace42:
Oops.
[Nexus 4 Android Development] faux123:
As far as the clock issue is concerned, I am not sure why HFPLL would lie. My implementation was using the HFPLL rather than PLL8 that [MENTION=4195844]show-p1984[/MENTION] was using. The formula to calculate the corresponding HFPLL value is correct. If there's a hardware limitation, then the lying is done by the hardware not software. I don't see anywhere in the software clock driver that would lie to the sysfs entries.

The code is here for you to verify: https://github.com/faux123/mako/commit/662543938427a4de68d75944751f819444ae7615
[Nexus 4 Android Development] sirxdroid:
If frequencies < 384 can be set, then what about stability? Didn't Qualcomm say the CPU would not be stable at anything < 384?
[Nexus 4 Android Development] thracemerin:
Not saying you're wrong, I believe I was using show-p's implementation, I'll have another look at the whole thing.
[Nexus 4 Android Development] soumoks:
Anyone undervolting this kernel?if so by how much?I just want to know my options before starting..
[Nexus 4 Android Development] sirxdroid:
It depends on your CPU bin. Start with -50mV, then -75mV, -100mV, etc. On my fast binned CPU I use the range 384Mhz @ 750mV - 1.5Ghz @ 1050mV.
[Nexus 4 Android Development] soumoks:
Have a nominal cpu, Thanks for the advice :)
[Nexus 4 Android Development] pa.pn2:
It works for me

But i think you just have to modify a little part to let it boot with miui as i read

You dont have to use the complete ramdisk

Maybe its miui. But if open the app drawer i have a little lag

I changed to deadline instead row and its feels now snappier

Ill have a look today what parts have to be changed to let it boot

Anyway good job. Love the kernel
[Nexus 4 Android Development] thracemerin:
So, I didn't actually revert the hsic patches that caused the data drops from Build 7 in Build 8 and not only were they causing all sorts of weird data issues for me but they also somehow broke my WiFi (No idea how :confused:). Anyway, quick maintenance build to fix this issue Build 8.1 (shows as 8-1 on goo.im) is now on it's way to goo.im. If you aren't experiencing issues with 3G/mobile signal, then you don't need to update, but that's completely up to you.

Happy Flashing :victory:
[Nexus 4 Android Development] karanrajpal14:
I'm really loving this kernel! Thanks for keeping it alive. Hope that motley is fine. Hey, a small feature request. Could you add the sleep to wake and sweep to sleep. I tried AK kernel a few weeks ago and that was the only feature that I missed. Touch Control is causing freezes!
[Nexus 4 Android Development] thracemerin:
I had s2w for an alpha or two, but when I asked for feedback it seemed like nobody was using it so I dumped it, I can certainly put it back in along with s2s, I'll take a look.
[Nexus 4 Android Development] pa.pn2:
Could you please update for miui aswell?

Kernel gets better with every charge. Just wow wow
[Nexus 4 Android Development] thracemerin:
Should be able to flash it directly over b8 for miui, if you can't let me know.
[Nexus 4 Android Development] pa.pn2:
Ill check that out now. Thx

Edit. It works

Thank you so much
[Nexus 4 Android Development] karanrajpal14:
Oops! Sorry about that! I'll check the thread more often now. Thank you for considering the request. It's really handy with s2s.
[Nexus 4 Android Development] thracemerin:
So, I'm having a strange issue where for some reason my phone won't connect to WiFi networks that it has saved when I enter the coverage range, and sometimes it fails even after I try to force it, setting airplane mode on then off fixes it, but I'm trying to sort out if this is kernel related or not, anyone else having similar issues?
[Nexus 4 Android Development] Lazy Rich:
I think the whole "we hate mpdecision, we have to switch to something else"-thing is way overrated.

I have used a lot of custom kernels (faux, franco, trinity, harsh, matrix), all of them giving me between 3 and 4 hours of SoT on my daily usage. And they all stutter like hell, the smoothness is no where near stock. Scrolling becomes a real pain in the...u know ;)

So I decided to go back to a kernel with mpdecision (faux enhanced stock) and what should I tell? SoT over 5 hours, every single day, and of course it is smooth like butter. So for me, mpdecision is the only hotplugging method that really satisfies me completely. I hope that more devs will add it back soon.
[Nexus 4 Android Development] karanrajpal14:
I've faced that quite a few times. I just restart my router and I'm not sure if it's kernel related but I can assure you that I've faced it on other kernels too. The main problem is that it's very random and isn't easily reproduced. I'll try to get a kmsg next time it happens.
[Nexus 4 Android Development] ata1918:
My experience, no clue if this is relevant:

I bricked my router some time ago, I then reverted to stock Netgear firmware, my nexus wouldn't even connect, I tested it with a Galaxy S+ and Galaxy S 2, they had no issues connecting. TLDR: For whatever reason my nexus4 only works when I use OpenWRT firmware.

Typed from my Mako.