yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Hrithan2020:
Its mentioned in the second post. Try running this in the terminal:

echo 2 > /sys/module/auto_hotplug/parameters/max_online_cpus

What I've done is I used the scripter tool in the ROM Toolbox Pro, and created a script containing the above line and set it to run it at boot. [ so that even after rebooting, the setting is preserved]. Alternatively, I think there is a standalone scripter app which does this. Else, you have to create a .sh file with just this line and put it in init.d with correct permissions.

Yeah, and I've not observed any slowdown even in games like NFS MW, and it does generate less heat. I haven't quantified the battery life impact though. [but was around 1 hr more by my estimates as well]. I used perfmon to monitor cpu usage when playing games such as NFS MW and Temple Run 2 and it seems that the games don't use all the 4 cores. Generally it uses two cores at around 1-1.2 ghz and another additional core stays at 0.3-0.5 ghz.
[Nexus 4 Original Android Development] PoisonWolf:
Bring up terminal....type su, hit enter then paste the following and hit enter.

echo 2 > /sys/module/auto_hotplug/parameters/max_online_cpus

The changes only lasts until you reboot which is perfect since you only want to try it out.
[Nexus 4 Original Android Development] z3r0_x:
Somehow those settings won't stick for me...maybe an app like Faux or Trickster is interfering?
[Nexus 4 Original Android Development] lazer155:
Is it normal for terminal to show: u0_a44@android

before each command? I hit a wrong key combination (volume down d) while I was disabling 2 cores and I'm not sure it changed the default mount point. Is u0_a44@android the default mount point?
[Nexus 4 Original Android Development] PoisonWolf:
Mine says u0_a75@android before typing su.
[Nexus 4 Original Android Development] lazer155:
Are there several different ones? Since yours is different from mine? I reset terminal so I don't think any wrong key combinations I pressed should persist.
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

That's the Linux username and host of your phone, a similar thing appears when using a Linux shell on a PC. Its nothing to worry about. Its not abnormal for it to be different between phones.

Edit: mine is u0_a34.
[Nexus 4 Original Android Development] -Asskicker-:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Thanks! :) How do I know if the command worked?
[Nexus 4 Original Android Development] PoisonWolf:
Use any root based explorer and navigate to the folder. Open the last file and you should see the number 2 in there =)
[Nexus 4 Original Android Development] dark_ente:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I would like to compare battery and performance between running two core @1,5 and for core @1 with voltage 600mv.

For performance I'll use Antutu, and for battery running plant vs zombies for 10 min @ max brightness and air plane mode.

Anybody have other suggestion?

Sent from my Nexus 4
[Nexus 4 Original Android Development] PoisonWolf:
You'll need to do 30 minutes at least IMHO. 10 minutes is too short.
[Nexus 4 Original Android Development] dark_ente:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

So with 4 core @1ghz 962,5 mv, antutu score 17153, battery drain while playing plant vs zombies is 607 ma/h, battery temperature is 41.2 Celsius.

Under volt 1ghz to 600 mv, antutu was reduced to 16900, battery drain is 555 ma/h, battery temperature is 40,1 Celsius.

My screen brightness is 40%, which is the major source of drain.

extreme under volt can give you 10% more battery. Heat is another story though. 360 mv less and only 1 degree different.

So in my opinion it's not worth the risk to undervolt too much. -150 is fine already. If you want more battery no matter what, reduce your screen brightness.

Let's see how disable two core looks.

Sent from my Nexus 4
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

On 3G the whole time :)
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Impressive, some can't even get that on Wi-Fi.

What's your setup?
[Nexus 4 Original Android Development] Locksmith81:
System tuner
[Nexus 4 Original Android Development] Logi_Ca1:
This might be a bit hard to believe, but these are the voltages that my phone is running at.

If the CPU is truly running at those voltages (I say if because it's kinda too good to be true), then I think the lower voltages could go below 700mv :)
[Nexus 4 Original Android Development] aventu:
maybe they are stable at only 50% load. you have to test them seperately to be sure.
[Nexus 4 Original Android Development] sideeffects:
Main reason to under volt on this phone is to beat thermal throttling and gain performance any battery saving is a bonus.

My phone crashes if I go below 975mV at 1404MHz but tests stable using stability tester and benchmarks at 975. :)
[Nexus 4 Original Android Development] wurzelsepp3:
1.13Ghz at 0.7 Volts??? That's insane
[Nexus 4 Original Android Development] Logi_Ca1:
Indeed it is which led me to believe that the voltages are not being properly applied. Yet on the other hand, my phone does hang if 1.4Ghz is set to too low a voltage (around 0.925v). Also I have verified that my 1.13Ghz is stable by mining for Litecoins at that frequency, with the app AndLtc.
[Nexus 4 Original Android Development] sideeffects:
Yes also device is cooler to the touch so it has to be undervolting. Perhaps the UV value is wrong and not quite that low or these chips are that good:)
[Nexus 4 Original Android Development] Cyb3rGlitch:
These are my voltages. As far as I can tell they're stable. http://db.tt/ourdQoeN

---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------

Would it be possible to add higher GPU frequencies? I'm getting lag in NFS:MW that I wasn't getting on my international S3. I feel that underclocked CPU + overclocked GPU would be a good match.
[Nexus 4 Original Android Development] yokken:
Running this kernel @ 87.5mV undervolt, aka 1000mV @ 1.4GHz with interactive/sio. Running smooth and stable so far and getting epic battery life. It's been at 91% for the past 30 minutes! By this time in the day my phone would be at something like 85%. I'm psyched to see if it gets even better. FINALLY a kernel that has improved my battery life.

Using faux's app to tune the voltage by the way.
[Nexus 4 Original Android Development] keda:
950mV crashes my phone when playing game. I'll stick with 975mV
[Nexus 4 Original Android Development] gbroon:
Found the same myself today had to up it to 987.5 at 1.4. Strangely last night was fine with stability tests and streaming a full movie with plex. Today reboots with Google music and angry birds. Sometimes it feels like my phone likes to change its mind for no good reason. Maybe its a woman I dunno.

Also got 1.29 at 975mv and 1.24 at 925mv.

If no problems I'll bump a few others down tomorrow.

The deep sleep problem I had is gone so it was either the previous version or something else. Went from total 7 minutes deep sleep in 1 day to 55%.
[Nexus 4 Original Android Development] aestil:
I installed system tuner on my device and i'm still seeing the CPU spike to 1.5ghz frequently.

Should I manually lower the frequency under the CPU tab in system tuner?

Which governor is best?
[Nexus 4 Original Android Development] yokken:
Continuing to get awesome battery life. It's probably 110% of what it was before, maybe 120% but it seems to drain a LOT less when it's idle. It's awesome. Leaving it at -87.5mV UV. Might push it down a tiny bit more to see if I can get even lower, but right now it's awesome.

Edit: Weird... the stock values for the voltage changed. It says only 1000mV for 1.4GHz but I swear it was more before. It says -87.5mV put me at 912.5mV for 1.4GHz which is low. No way I've been running it at that. Wonder why it went down...
[Nexus 4 Original Android Development] ptesmoke:
When you "set on boot" I'm pretty sire it overwrites the default table. Motley would know though for sure..
[Nexus 4 Original Android Development] yokken:
I don't ever recall turning that on. I wanted to make sure it was stable first.
[Nexus 4 Original Android Development] whittikins:
So you're getting 10-20% better battery life than stock?
[Nexus 4 Original Android Development] rootuser11:
This -175mv has been rock stable for me.

Been playing NFS:MW...

Of course, I still get overheating problem + throttling after playing 3-4 races.

I wish someone implements the current Optimus G's throttling configuration (starts throttling at +6'C higher).

By the way, my screen turns into yellowish on the lower portion of the screen, and then disappears once the phone cools down.

https://www.dropbox.com/s/5aod0zl2q8bpbs3/Screenshot_2012-12-05-21-50-05.png

UPDATE::

Tried out the System Tuner for finer tuning.. We will see how this config goes.

https://www.dropbox.com/s/pcgsnf5e83qm6sc/Screenshot_2012-12-05-22-02-58.png
[Nexus 4 Original Android Development] keda:
912.5mV on 1.4, that's crazy. It crashes at 950mV for me. I use System tuner. Interactive and sio

---------- Post added at 05:04 AM ---------- Previous post was at 05:02 AM ----------

Heard that System Tuner only cap frequency for first core.
[Nexus 4 Original Android Development] rootuser11:
I did not touch the cpu freq/governor (so ondemand, sio)

apparently, my gpu clock is at 400 not 325.
[Nexus 4 Original Android Development] _motley:
Thanks for the feedback

Thanks for the feedback everyone. I have tagged the latest build as stable. Other than reports of too much UV causing instability, we have a nice stable kernel and battery savings are definitely being realized.

Some notes thus far:

After testing and getting reports back from others, OnDemand is giving the best battery life.

For those spiking to 1.5Ghz, you must still be using the initial release. If you want to stabilize at at a lower frequency than 1.5, install the latest build and allow it to run at 1.4GHz. I haven't missed 1.5GHz one bit since I removed it. Running at 1.4 uses less energy by default and allows for a little more UV. The ability to UV on this device has been amazing yet puzzling leaving me wonder if there is something else (mpdecision etc.) still making some corrections after we go below a given mV/freq scenario. It is definitely working due to lower temps and proven instability when we UV too much, but I am still wondering if there may be a firmware fail-safe that is kicking in somewhere. In the kernel, I haven't yet been about to see a min_mV setting that appears to be in action, but I am still looking around.

Someone commented about lowering the lower frequency step ever further (lower than my 304MHz). While I have given the ability to lower uV at this frequency to 700mV, I am not going to go lower on the frequency. There are two reasons for this. With screen off, when the phone wakes up to do work, we want the work to be done quickly so it can go back to deep sleep. Secondly, going too low can start causing SODs and can cause stability issues with audio streaming/decoding when the screen is off. I recall some CM kernel commits for HTC awhile back in some early build where they went to 195Mhz. It just caused too many issues and that school of thinking doesn't work past a certain reasonable threshold. I will be doing more testing in this area as we move forward.

For anyone testing or having issues with deep sleep, be sure to test when your USB cable is unplugged from the computer or charging adapter. The device will not deep sleep when plugged into a power source. Deep sleep has been excellent for me, so if you have issues in this area, you likely have an app keeping the device awake.

Thanks for your support and keep that feedback coming!:good:
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Latest Exp (b31), latest cm nightly, all I change is the tcp congestion algorithm to westward, rest is stock.

Oh, autobrightness on.

I do have good data signal though, 2-5 bars (goes up and down randomly, even when not moving)

Most of the time spend using tapatalk, chrome beta and Google reader.
[Nexus 4 Original Android Development] barrybear:
Hey guys! I'm using the Mainline build 57 and I seem to be having some problems..

1. Whenever I set the minimum and maximum CPU frequency in the Settings > Performance, after a while it just goes back to default 1026 @ min and 1512 @ max.

2. I try to type in the terminal "echo 2 > /sys/module/auto_hotplug/parameters/max_online_cpus" with su first, but it just says "No such file or directory".

I changed ROM to CM10.1 and flash the kernel right after flashing the ROM. Help is very much appreciated :)
[Nexus 4 Original Android Development] Saiger:
try to use a kernel tuner app from the playstore to set up the cpu frequencies
[Nexus 4 Original Android Development] lazer155:
Why would undervolting cause the score to go down? I would have thought it would be closer to the same score.
[Nexus 4 Original Android Development] Elchemist:
I can't set the gamma options. Running motley b31, with CFX SR8. Busybox installed.

I have tried copying over the sample scripts from the OP and created a file in the init.d directory, permission is set to allow all to execute.

When I checked the settings using the cat command nothing has changed.

I tried echo each line manually in terminal emulator and I get an error, can't create /sys/devices/platform/mipi_lgit.1537/kgamma_red: permission denied. Even though this file already exists.

Any insight as to where I went wrong?

Thanks.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Mainline keeps mpdesision from stock, so it will push up the minimum to 1ghz and 2 cores on when you touch the screen.

If you want to use in kernel hotplug use the newest experimental build, its perfectly stable in my experience :)
[Nexus 4 Original Android Development] DynamicRam:
use this flashable zip (you can change the values with any text editor)

http://xdaforums.com/showpost.php?p=37286436&postcount=1212
[Nexus 4 Original Android Development] Elchemist:
Thanks a lot the file worked.

I am still wondering what I did wrong though when I checked, aside from the contents and file name I can't tell the difference is?
[Nexus 4 Original Android Development] DynamicRam:
before you do the echo command you have to type su
[Nexus 4 Original Android Development] j3di:
Motley, there seem to be new CM10.1 kernel commits relating to charging. I take it they have come from Google and can you shed anymore light on this? Thanks
[Nexus 4 Original Android Development] Hrithan2020:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I think it is based on the 4.2.1_r2 which Google released. Here is the change log :

https://gist.github.com/raw/4696612/2b0ee4f3c38c5c275e9723dbecdc9abd392e3238/1

But saw a few people/devs mentioning that it contains fixes for wake lock and bluetooth.

Sent from my Nexus 4
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

It contains the 2 patches related to charging, it says something about hsic host wake lock, but its as it relates to charging from a USB source not related to the radio interface. People are reading the commit messages and thinking the patches do things they do not.

That being said, there's no reason that motley shouldnt merge them for the next release.
[Nexus 4 Original Android Development] azrash:
Hi motley, I do not have the experience in building ROMs nor kernels but I have just bumped into this.

Does it mean we can get the Linaro goodness from using Google toolchain now?
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

That change is "Review in Progress" which means it hasn't been merged to Google mainline, which means the Google tool chain doesn't currently contain the Linaro enhancements. If it gets merged they will be the same at the point hat the diffs were made, but if linaro continues to improve they will still differ.
[Nexus 4 Original Android Development] _motley:
Yeah, those two commits state they are for off-mode charging (disables the hsic host driver and mdm driver in off-mode, i.e. when the OS is not running). Anyhow, I have just merged them in for the next release:good:

As far as the hsic/usb fixes and reading across the forums, it seems some still think the batch of patches cause data instability (CM has reverted them from their kernel again). It doesn't affect me in how I use the device (from what I can tell), but some claim to have data drops and less stability when coming off WiFi to mobile data. What does everyone think now that we have been running this batch of patches for awhile? Are these patches good, or do they cause more issues than the little bit of power savings that they bring?

I find it interesting that Google has merged the above two commits, yet hasn't chosen to commit anything else for public consumption when it comes to all the code aurora hsis/usb changes we have been watching. I think it goes to show you that their use of a USB bus for a modem has proven to a bit more of a PITA than they would like. It is also likely that the patches on code aurora are still a work in progress and nobody has officially signed off on them for a stable release.

Anyhow, I digress, let me know your feedback on data stability since the build where the patches were merged in.
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

CM didn't revert them again, that was the initial revert from early January prior to Harsh and others discovering the fix to the data drop issue. They haven't been particularly receptive to reintroducing them despite my kernel versions that haven't exhibited any negative data related issues sine the 15th. As for other kernels, faux123, Franco, mathkid, etc... have picked some but not all of the patches I did and/or implemented other solutions which may be why they continue to have problems.
[Nexus 4 Original Android Development] _motley:
Thanks, it will be interesting to see what others say. I don't hear about data drops very often in this thread. I too still think there are other things playing a role besides these patches, with or without them. I think part of the issue, and what makes it so hard to judge these patches, is that mobile data is just not as reliable as sitting on a WiFi network. Every device I have ever had has never been perfect on mobile data, but it is due to the coverage and lack of resilience of the network I sit on in my area. Sometimes I get 10 Mbps+ speeds, but other times it is around 1 Mbps. Sometimes when driving, say once per week, it isn't fast enough to keep up with a streaming podcast. However it may be the streaming server I am connecting to...so many variables. Can't really start running IP diagnostics when I am hurling down the highway @70mph in 2 tons of steel LOL.
[Nexus 4 Original Android Development] matte3560:
Do you need to reboot after changing the thermal throttle setting on experimental b31?
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I haven't personally had any data drops that I'm aware of with your kernel and my network provider is flaky on the best of days so based on my test group of 1 I'd say there aren't issues but like you say there are way too many variables involved here for it to be easy to say one way or another.
[Nexus 4 Original Android Development] _motley:
No, that setting and all the rest of the settings in post #2 will be active immediately once changed until you reboot. If you want them to persist after a reboot, you will need to setup an init.d script, or use a scripting app to set them to whatever you like on boot.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Zero new data stability issues, from time to time the whole thing drops (signal bars go black) but that happended pre patches as well heh, signal strength jumps up and down like mad as well.

Anyway, patches seem to help and don't cause any issues for me :)
[Nexus 4 Original Android Development] _motley:
Thanks for your input veyka.
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Thanks for your kernel motley. I am having amazing battery life and 100% stability in everything : data, system. I love running b31 at its stock settings :)

For now I have frozen Trickster, BBS, don't need them.
[Nexus 4 Original Android Development] lazer155:
I asked this awhile ago in the thread but it wasn't answered; I was wondering what you guys consider mid range frequencies to be as well as what you consider to be high and low range frequencies.
[Nexus 4 Original Android Development] lightningstalon:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Just curious motley, what are you using for your kernel compression algorithm? LZO I'm hoping?
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Well, guess I'll shine in again after few days on data drops. B31 is very very good, I feel as if it gave me food battery life, atop of good data connection most of the time. I tend to switch on and off between this and matrix kernel, usually use Motleys though. I don't know if this relates to T-Mobile being odd, but what sometimes would happen... I would have H icon and blue bars, pretty much full bars. I'd initiate to load sometime that requires data, yet it wouldn't really load. I'd see an up arrow, but no down. Usually starts working after about 30-45 seconds. I decided to jump on matrix kernel again to see if it happened and if hasn't. Again, could have purely been the network as well.
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Unless I'm completely misreading his defconfig, he uses XZ.
[Nexus 4 Original Android Development] efan3719:
have this happen as well on Motley's. Havent tried other kernels to see if it does anything different. I guess i should. But I have kinda crappy data coverage where i am at so it could very well be a network thing.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I think it is kernel related. Flashed r31 again this evening and just had 2 data timeouts where I never have issues on matrix.
[Nexus 4 Original Android Development] efan3719:
i'll give matrix a try and see if the same thing happens.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I also get the stuck up arrow of doom, 3UK, i have gotten it a lot less on this phone, but it's happended to me on my sgs2 and my gnexus, also sometimes happens to my mother who has a gnexus.

As far as I know, its a network/android issue that's been happening intermittently for a long time (people have been mentioning it since the G1)
[Nexus 4 Original Android Development] w0dash:
I don't know if its a problem with System Tuner or your Kernel, but the CPU clock settings are not applied correctly.
[Nexus 4 Original Android Development] j3di:
Motley, Is this because /sys/devices/system/cpu/cpu2 (or cpu3) Do not contain a cpufreq folder? Or has it always been this way? I'm on b31.
[Nexus 4 Original Android Development] z3r0_x:
I guess that's a display error of the app! Check with PerfMon: http://xdaforums.com/showthread.php?t=1933284

I've tested with Faux app and Trickster and both apply the reduced Max CPU Freq to all cores!