yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] sirxdroid:
Is the 25mV boost something new that was just discovered? I haven't seen it mentioned in other custom kernel threads. It seems hard to tell what frequency and voltage the CPU is really running at, the kernel can claim whatever it wants via sysfs. See this post:

http://xdaforums.com/showpost.php?p=41162075&postcount=93
[Nexus 4 Android Development] thracemerin:
As to the frequency I'm not sure, showp may in fact be correct that anything below 384 doesn't in fact stick, all the apps that measure such thing suggest it does, but there could be an invisible or hard to find safety that prevents it from really dropping.

As for the UV, I know that to some extent UV settings do stick, I also know that if I remove the 600mV safety cap and UV to rediculously low voltage that my phone either SODs or crashes. This 25mV boost thing is something I wasn't personally aware of before, though looking at the code now I feel silly for not having noticed.
[Nexus 4 Android Development] sirxdroid:
It seems strange that Nominal/Fast/Faster get a boost. You'd think that maybe Slower/Nominal would need a boost but not Fast/Faster.
[Nexus 4 Android Development] thracemerin:
Yeah, I have no idea what the point of it is since slow chips tend to require more voltage than the other bins it seems to make no sense, but this is definitely what the code does, an interesting mystery if nothing else.

Edit: though this could explain why you can't UV slow chips as much (to a small degree anyway)
[Nexus 4 Android Development] sirxdroid:
Maybe they got it wrong and flipped the sign :)
[Nexus 4 Android Development] thracemerin:
Who knows, it wouldn't be the first time.

On an unrelated note I/O starts later today, yay! Let's hope Google gives us new sources with some of the big annoying stuff fixed, I don't care if its 4.3 or 5.0 as long as they fix WiFi, hsic, etc... I have big hopes but little faith at the moment, we'll see.
[Nexus 4 Android Development] sirxdroid:
I hope they fix the crappy Bluetooth stack, AVRCP 1.3+ support - it's 2013 and it's ridiculous that no track info makes it to the receiver when you stream music via Bluetooth.
[Nexus 4 Android Development] toge64:
Hoping Google can improve the battery life to compete with the HTC one m7 and s4...
[Nexus 4 Android Development] Sherrillface:
Carbon rom plays super nice best performance and battery life yet no complaints whatsoever on my n4 now using build 4 tried build 5 but battery life went down slightly it seemed so jumped back
[Nexus 4 Android Development] FeintDoxx:
Just flashed b37 and then flashed 49. Dirty flash from 3.4 Franco.nightly. Everything seems fine so far. Will keep an eye out for fishy thing other wise this is a great kernel!

Sent using XDA app.

phones:

Google Nexus 4

- CM10.1-Nightly

HTC Dream

FroyoSense Rom
[Nexus 4 Android Development] thracemerin:
I made the kernel so awesome it can run with all cores offline. :good: :confused:
[Nexus 4 Android Development] sirxdroid:
You're awesome! Next project: make it produce energy for other devices (we can already use it as a hand warmer).
[Nexus 4 Android Development] thracemerin:
Yeah, it scored a 600 in Antutu (not a typo), so it's far from awesome :p
[Nexus 4 Android Development] sirxdroid:
Score > 0 with no cores in use? I don't know about you, but I'm pretty impressed.
[Nexus 4 Android Development] thracemerin:
Well fair enough, but as you can see from the screenshot CPU2 was online at some point but CPU1 was never online, this should be impossible, so needless to say I broke the hotplugging completely :)
[Nexus 4 Android Development] thracemerin:
After a minor mishap described above, I have posted yet another Alpha in Post 4 :D

This one continues to include sweep2wake (default off of course), but it also includes the patches to the cpufreq driver and workqueues from CAF that franco added to his kernel a couple of days ago.

Happy flashing :victory:
[Nexus 4 Android Development] captaindyson:
Sorry, bit of a newb to this and don't know the difference between "dirty" and "clean" flashing apart from guessing :-S please can someone tell me how to flash this kernel, step by step with wiping cach and all :)

Also does it matter that I am not using CM recovery?

3rd and final question, will I need to do backups? And if so to what extent?

I am currently running Franco kernel if that helps :)

Sorry for all the questions and thank you in advance for helping
[Nexus 4 Android Development] thracemerin:
What ROM are you currently on?
[Nexus 4 Android Development] captaindyson:
Stock at the mo although that may change over the coming weeks :P
[Nexus 4 Android Development] thracemerin:
I'm assuming you have either TWRP or CWM installed since you're on franco?
[Nexus 4 Android Development] captaindyson:
Yes TWRP that is the one, I could not remember its name in my first post.
[Nexus 4 Android Development] thracemerin:
Ok, you'll need the following files: the reset kernel zip from Post 1, Build 1 Stock & Build 5

Reboot into recovery

Flash the reset kernel

Then flash Build 1 stock version

Then flash Build 5.

Reboot

Done!
[Nexus 4 Android Development] captaindyson:
Thank you :) will this wipe any data? Will I need backups?
[Nexus 4 Android Development] thracemerin:
It shouldn't, we're only messing with the kernel, but it might not be a bad idea to do a nandroid from TWRP before you flash, just in case :D
[Nexus 4 Android Development] captaindyson:
Thanks again, you are doing a great job :)
[Nexus 4 Android Development] thracemerin:
Well, it looks like Google did announce that AVRCP 1.3 and Bluetooth Low Energy are coming to Android, the bad news is that it appears to be exclusive to API level 18 and above which would mean a new and as yet unannounced version of Android (be it 4.3 or 5.0), the good news is it sounds like the N4 is capable of supporting these features so whenever we get them they'll work.

http://www.androidpolice.com/2013/0...vrcp-1-3-coming-to-android-with-api-level-18/

I'd say that the new version of Android will be announced sooner rather than later, but not likely this week at this point.
[Nexus 4 Android Development] :
I am more than happy to report the battery performance. Great work thracemin by continuing the awesome work of motley.

For those who want detailed statistics check the paste bin. It's a text dump from BetterBatteryStats.

http://pastebin.com/M1u7CjUt
[Nexus 4 Android Development] swaggerwocky:
Battery life with b5 has been quite good for me.
[Nexus 4 Android Development] Ace42:
Anyone know how to disable entropy like in faux kernel?
[Nexus 4 Android Development] thracemerin:
Oh hey, green name. :victory:
[Nexus 4 Android Development] mundixx:
Congratulations on the RC! Well deserved, mate. :D

Tapatalked from my AOSPA Nexus 4
[Nexus 4 Android Development] IAmAN00bie:
Try either:

echo 0 > /sys/block/mmcblk0/queue/add_random

or

echo 0 > /proc/sys/kernel/randomize_va_space

Saw these a loooonnnggg time back in Faux's thread.
[Nexus 4 Android Development] thracemerin:
Those of you on the alpha in post 4 (8342074) any impressions? I realize that having S2W on decreases battery life and I'm still on the fence about keeping that in the release version, but other than that does anyone noticed any performance improvement/decrease? And if you aren't using S2W is the battery life about the same?
[Nexus 4 Android Development] AcmE85:
I am using it since you have posted it and there are no problems so far.

Everything is as smooth as before and the battery is on par with b5.

Yesterday I was on 50 percent with almost 3 hours of screen time. But

on data for most of the time. Usually I only get this screen time on wifi.

S2W is disabled and I am using init.d scripts for retention and no voltage boost.

Thanks!
[Nexus 4 Android Development] rodries:
Have you seen this comment on your other thread?

http://xdaforums.com/showpost.php?p=41478241&postcount=654
[Nexus 4 Android Development] antih3ro:
I tested sweep2wake over night with wifi and sync on. Lost about ~ 1% per hour.
[Nexus 4 Android Development] thracemerin:
I did, but I can't seem to reproduce it at all.
[Nexus 4 Android Development] caliban2:
Neither can I, be it on b5 or latest WIP plus mod-value. Signal and notifications are fine.
[Nexus 4 Android Development] veyka:
Haven't noticed any negative effect on the battery life using the newest alpha, i dont use s2w.

Sent via Nexus 4
[Nexus 4 Android Development] AcmE85:
I have decided to test this again. Instead of just changing the ini file in place, I pulled the file from your hsic_v6.

I also compared every single value in both your ini and the one from the rom I am on (LinaroBean CM10.1based).

There are some values set, that differ from your ini file which is weird (not arp offload, bcastmcast, suspend).

Last time I tried the described fix in v6 I flashed in this order: rom > v6 > motley (without prima!)

This should work as intended, doesn't it?

edit: check http://xdaforums.com/showpost.php?p=41539310&postcount=660

Right now I will test stock WCNSS_qcom_cfg.ini with gEnableSuspend=2

to see if there is any different behaviour.
[Nexus 4 Android Development] FeintDoxx:
Okay so I was on Day 4 with this kernel and my nexus was acting weird. It would get stuck on the boot animation and would not boot up. Like I said before I did do a dirty flash since I didn't restore my kernel. So I'm assuming that's what was causing the weird activity. Either way great kernel. Definitely restore kernel to original ROMs kernel.
[Nexus 4 Android Development] karanrajpal14:
Hey guys, trickster mod got updated and now it shows us to tweak touch screen filter and sound control. Can someone tell me what each value does? Or maybe link me to a post that explains it? Thanks!
[Nexus 4 Android Development] rodries:
I have same issues that you have describe in that post, so i guess there is a patch in motley that make the difference, I'll try to use old motley versions to try to find in which version is the patch that modified the behaviour
[Nexus 4 Android Development] AcmE85:
After 2 days of testing I have to say that the fix helps a little bit. Notifications arrive approximately 1-2 minutes later but that is okay for me.

Definitely better than it was before.
[Nexus 4 Android Development] thracemerin:
Ok, in keeping with my releases coming out on Sundays, Build 6 is now on it's way.

I decided to remove sweep2wake (but the wip build (8342074) with it in is still available if you want it).

Everything else from 8342074 made it to live, I noticed a small performance improvement.

Anyway, happy flashing :victory:
[Nexus 4 Android Development] AcmE85:
Thanks.

Franco mentioned in his changelog for r138

Maybe you could try to add this in an upcoming update.
[Nexus 4 Android Development] thracemerin:
Already in my private build, a new Alpha will appear early this week :)
[Nexus 4 Android Development] Remoteconcern:
This kernel is really good. Looking forward to the idle drain patches, we all love battery life!
[Nexus 4 Android Development] brainbeatuk:
Hi I have decided to go back on stock ROM and kernel. Testing battery usage at stock compared to that performance glitch?? I been doing. Few questions if anyone can answer. Using trickster mod I noticed that SOC thermal control is off. (Totally fresh wipe so not old kernel settings.). Also can mode vision be turned off on stock kernel or will it be ignored?

And is there a kernel that is stock with just voltage control?
[Nexus 4 Android Development] Remoteconcern:
You can turn off mpdecision on stock kernel, but it will leave all four cores on. It does hot plugging as well as raising the minimum.

Voltage control only? No, maybe try faux enhanced stock but has a few other tweaks. Experience pro, the paid app, allows you to under volt stock kernel.

As for thermal, that is likely because trickster is just not detecting stock thermal control. It definitely exists though.

I don't know what glitch you mean.
[Nexus 4 Android Development] brainbeatuk:
Thanks for reply I'll try that app. Basically I can run 1512mhz [MENTION=374871]625[/MENTION]mv so long as you turn off thermal control. Will overheat after a while on GTA so its finding optimum setting for performance/battery. As soon as I turn back thermal on it will crash. Or if you change back from performance

That experience pro is just what I was looking for. I presume that flicking on and off thermal control did the job now as it didn't crash at 1242 @ 600 performance mode. Writing this on it :). Know any terminal calls to check voltage to be sure?
[Nexus 4 Android Development] Ace42:
Is 625mv a typo...? No way you are doing that on fast chip!
[Nexus 4 Android Development] sirxdroid:
The sysfs can set and report any bogus number, it doesn't mean that's what the chip actually runs at, you'd have to open up the phone and measure the voltage. Look at this post re min frequency (I do realize we are talking about voltage instead):

http://xdaforums.com/showpost.php?p=41162075&postcount=93
[Nexus 4 Android Development] brainbeatuk:
I can assure you it is. To try yourself you must first turn thermal off and only be on performance. From my two weeks testing I presume it needs a lot of voltage to change freq step. I have using scripts even had core one and two normal volt interactive and last two cores say as performance 1577 or 1620 (have to be unused interactive freqs) at 625mv.

I actually noticed no difference in draw from 192 to 384 I didn't read that though thanks

I have been using battery programming to record ma draw. I'm pretty sure it is cos I will crash at that volt with thermal on
[Nexus 4 Android Development] thracemerin:
How are you turning thermal off?
[Nexus 4 Android Development] brainbeatuk:
When I did scripts I wrote a command. Just tested on stock and trickster doesn't work as I noticed it go back to 1184. At the moment I'm on virgin stock settings. Checking how long GTA vc runs from full battery so I can use as a battery benchmark while using android tuner to record temp ect. Then I will use your kernel again and find perfect game settings for me. I want to be able to do long sess on it but not be slow. About the 625 thing here an example say 1512 @ 625 lasts ten mins before getting to 60c well at 700 it would say take 8 mins.

su(press enter)

echo N > /sys/module/msm_thermal/parameters/enabled(press enter)

Courtesy of simms
[Nexus 4 Android Development] thracemerin:
What parameter turns it off though? I'm trying to figure this out, I wasn't aware it was possible to completely disable it in the sysfs, seems a risky thing to expose to users.
[Nexus 4 Android Development] brainbeatuk:
su(press enter)

echo N > /sys/module/msm_thermal/parameters/enabled(press enter)

This stability test was on either build 4 or 5 1511@600v

The numbers in 80s are a performance rating if you try on default setting either stock or yours ect it will snake up n down from 50 to 90
[Nexus 4 Android Development] ctfrommn:
Oh yeah, Ive been benchamarking like that for a while. Most kernels allow that. I usually just use a file browser and go to /sys/module/msm_thermal/parameters/enabled and type N where the Y normally is. Not sure if this is exposed with the stock kernel but most custom ones allow for it. It works to as Ive seen near 90c while benchmarking.
[Nexus 4 Android Development] brainbeatuk:
Same I stopped testing 1674 when I seen 84 pop up. Was like Sixth 20000 an tutu benchmark in a run though

You can cool down CPU without thermal control using hot plug governor I change the disable to 110 middle one to 200 all cores set to 350. Not exact been a week since I did hot plug stuff and you have to tweak to the freq you on. I can change to dual core eco mode that way. BTW uses a lot more power at 100% two core than all four on and warms up quicker
[Nexus 4 Android Development] thracemerin:
static int enabled;

Y or N would still be > 0, so it's always enabled.
[Nexus 4 Android Development] brainbeatuk:
Sure its a static int. How does trickster mod turn it off?
[Nexus 4 Android Development] thracemerin:
It doesn't.
[Nexus 4 Android Development] ctfrommn:
Interesting.....not sure how to explain no throttling happening then if its still on. You obviously know a ton more about his than I do so Ill defer to your knowledge.
[Nexus 4 Android Development] thracemerin:
It's possible if you set it to 0 instead of N it might be off, I'm not sure how you're doing it.
[Nexus 4 Android Development] ctfrommn:
As stated.....I only went by what Simms said too. I dont know enough to be messing with stuff indiscriminately.
[Nexus 4 Android Development] thracemerin:
Yeah, I'm not sure now....let me look at it more.

Edit: Nevermind, it's working as you described it. Y for enabled, N for disabled.

Edit 2: still doesn't explain how you can run 1511@600 with thermal off and not with thermal on, makes me think its not really running at 600.
[Nexus 4 Android Development] MotoRaph:
Nice kernel. Thanks.

Could you upload a version with the newest prima drivers as well, as in your other thread? Then people can decide which solution is the best and also get the benefits of this kernel.
[Nexus 4 Android Development] Remoteconcern:
It makes me think that the voltages aren't being applied properly somewhere.

Has anyone else noticed that in general, motley kernel lets you use lower voltages than other kernels?

I can use 600mV right up to 1134mHz. On franco, that reboots instantly.
[Nexus 4 Android Development] brainbeatuk:
Yeah for me I can under volt most on motley. I also tested this on trinity and bricked kernel. I tested bricked at 1824 at 850 it crashes lower than that on bricked for me funny thing is if I do a benchmark on 1824 normally with no tinkering I get red light issue on bricked faux and trinity.

BTW if I turn thermal back on it won't crash straight away. Just when it tries to thermal control and change to 1184 it will be fine until cooled down as soon as it say goes to 1512 [MENTION=1601421]600[/MENTION] it will then crash. Would be able to workaround if a script could change 1512 to default volt when not in use then say automatically under volt when back in use.
[Nexus 4 Android Development] thracemerin:
Franco uses a modified version of Morfic's UV code, _motley used Faux123's code but it looks like they are more or less doing the same thing.

Franco limits UV at 750mV and _motley limited it at 600mV (which I think is the lowest of any kernel) so you will be able to set lower voltages, but whether that's whats really being set I'm unsure, it looks like the way it's being set is the same as the way it's set on franco kernel so there should be no reason it's not, i'll look into it more.

If you turn thermal debug back on, you'll see that re-enabling thermal without a reboot doesn't actually restart thermal. To check this, make sure thermal debug is on and you can see the thermal polling data in dmesg, then turn it off, you will see no thermal polling, if you switch it back on and check dmesg you'll see that the thermal polling data doesn't restart.
[Nexus 4 Android Development] thracemerin:
I believe I found the problem, we're not actually going below 850mV no matter what is actually set in the vdd_table, this would explain many things, LG decided to hide a verification of the voltage in a mako specific board file that wasn't changed by _motley when he originally added UV for this kernel. I'll correct it for the next Alpha :good:
[Nexus 4 Android Development] sirxdroid:
Let the crashes begin :)
[Nexus 4 Android Development] thracemerin:
Yeah, I will definitely put a warning in that people might want to reset their UV before flashing, just in case :)
[Nexus 4 Android Development] sirxdroid:
People who claim they can run 1.5Ghz @ 600mV should not be flashing custom kernels, let alone mess with voltages.
[Nexus 4 Android Development] thracemerin:
850mV still seems low for 1.5Ghz, but it explains why it might work.

Anyway, whether or not he's actually at 650mV, his comments did lead me to find a couple of things that I should probably fix (UV not applying and thermal not being able to be turned on without a reboot), so it was helpful :)
[Nexus 4 Android Development] ctfrommn:
Exactly....theres zero chance any chip would be stable at that voltage/frequency.
[Nexus 4 Android Development] brainbeatuk:
If you read back I said I wasn't sure if it is right. No need for narky comments pal. Glad I helped ya thracemin. So I'm assuming its 850 MV still low though?
[Nexus 4 Android Development] ctfrommn:
Not sure if youre refering to my comment or not. If so, no offence was meant nor did I intend to offend you. If my comment was taken that was I apologize :)
[Nexus 4 Android Development] brainbeatuk:
No not you bud sorry :)
[Nexus 4 Android Development] thracemerin:
Not at anyone in particular: Let's just try and keep it civil :D
[Nexus 4 Android Development] Remoteconcern:
That makes a lot of sense. I was wondering why you could always go lower with motley kernel. We probably should have figured it out earlier to be honest.
[Nexus 4 Android Development] sirxdroid:
My comment was not directed at anyone in particular, just a very generic comment about people who brag they can undervolt or overclock or underclock by some crazy amount without stopping for a minute to think if that even makes any sense. Something like "if the sysfs reports a number it must be true, forget the laws of physics".

My sincere apologies if anyone here got offended, it was without intention.
[Nexus 4 Android Development] thracemerin:
All the needless duplication by LG caused this issue (there are 2 of nearly every board file, which are identical and must match), but I'm building an Alpha now with the fix for it, so we'll see.
[Nexus 4 Android Development] sirxdroid:
And you are going to open up your N4 and put a voltmeter on it to debug it, right? :laugh:
[Nexus 4 Android Development] thracemerin:
Um....I have a semi broken one here, I probably could except the digitizer is broken so I'm not sure how I'd load the kernel on it to begin with.
[Nexus 4 Android Development] sirxdroid:
I was just kidding, but while you are at it, see if you can measure the min CPU clock so we can settle once and for all whether the CPU runs at < 384Mhz. :laugh:
[Nexus 4 Android Development] Remoteconcern:
I honestly think it doesn't change the minimum either. It doesn't seem to affect drain at all for me. Which it should, although not hugely. Keeping on a steady screen for an hour is how I tested. Both 384 and 192 minimum at same voltage drain 9% battery.

Not a great test because I'm not sure what android reports as 100, and there could be discrepancies. However you'd think it would show.
[Nexus 4 Android Development] thracemerin:
New Alpha is done, goo.im seems to be a tad slow with updating, but it'll get there eventually. :good:

Added the freezer fixes that faux introduced some time ago (should be the same as the ones franco has, they were originally written by Colin Cross from google)

Fixed the UV issue that we've been talking about in the thread.

WARNING: If you have UV set below 850mV, you might want to reset your UV settings before flashing this kernel just in case your chip can't actually handle it, bad things may result from ignoring this, you've been warned.

Happy Flashing :victory:
[Nexus 4 Android Development] thracemerin:
I'm fairly certain the minimum frequency is being set, it's being reported correctly by the kernel driver and Android OS, still could be wrong but it means it's being set somewhere outside the scope of the kernel and the OS which I'd believe if we were using mpdecision, but since we're not I think it's working.

As for the power consumption, we're talking about very small values, it would take a fairly long time to notice a real difference.
[Nexus 4 Android Development] ctfrommn:
Seems to me an easy test would be to online all 4 cores, set min/max to 192 & 384 respectively and benchmark them.
[Nexus 4 Android Development] thracemerin:
Stop making reasonable suggestions :p
[Nexus 4 Android Development] ctfrommn:
Id be happy to do it if you like.....I honestly havent flashed a Motley kernel in months so it might be a nice treat :)
[Nexus 4 Android Development] sirxdroid:
And be amazed by how you will get better numbers at 192 than 384 :)
[Nexus 4 Android Development] ctfrommn:
If that happens Im blaming you :p