yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
I'm running antutu at 4x192mhz right now, let me just say that the UI is horribly laggy like this OMG!
[Nexus 4 Android Development] sirxdroid:
Push it lower! Can you do 27Mhz like showp? How about all cores offline?
[Nexus 4 Android Development] thracemerin:
yeah, min 192, max 192, all 4 cores forced on. Testing 304 now.
[Nexus 4 Android Development] thracemerin:
First one: min/max 192Mhz, 4 cores forced online

Second one: min/max 304Mhz, 4 cores forced online.

It's antutu, take it for whatever it's worth, but 400+ points isn't insignificant.
[Nexus 4 Android Development] ctfrommn:
Ok, heres Quadrant at 192 and 304......I say its not working at 192 as both scores are statistically identical.
[Nexus 4 Android Development] thracemerin:
Interesting that my Antutu results seem to show the opposite.
[Nexus 4 Android Development] sirxdroid:
What did I tell you you'll get better numbers at the lower freq? :good:
[Nexus 4 Android Development] ctfrommn:
Shows what opposite? Those are statistically identical too. The higher score was on graphics not cpu....this is why I only ran the cpu test.

---------- Post added at 02:27 PM ---------- Previous post was at 02:26 PM ----------

I hate it when youre right :p
[Nexus 4 Android Development] thracemerin:
192Mhz

CPU integer: 1106

CPU float point: 975

304Mhz

CPU integer: 1115

CPU float point: 1047

The integer increase is 0.8%, but the floating point increase is 7.2%.

Gotta remember too that part of that graphic score is for software accelerated graphics which would be handled by the CPU not the GPU.
[Nexus 4 Android Development] ctfrommn:
I doubt those small variances accurately represent nearly doubling the frequency. Ill try 304 vs 486 and post the results. Im guessing the change is dramatic as it should be.
[Nexus 4 Android Development] thracemerin:
Well, 304 is a fake frequency too, the actually stock minimum frequency is 384, so it's possible 304 isn't working too.
[Nexus 4 Android Development] ctfrommn:
Ok, as I suspected.....if you want to add 384 back in and test I am willing to check that too. I love troubleshooting and testing stuff :)
[Nexus 4 Android Development] thracemerin:
I'll build one with the stock clocks later.
[Nexus 4 Android Development] ctfrommn:
So now Im wondering if 304 is the frequency not being recognized. No matter how many times I set 304 as the min my phone keeps idling down to 192. I thought all frequncy steps had to be a multiple of 27 mhz which 304 is not.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------

As an aside, I forgot how silky smooth Motley is. How much has changed since his 49 build?
[Nexus 4 Android Development] thracemerin:
Build 1 = Build 49, all the changelogs are in Post 1 :)
[Nexus 4 Android Development] ctfrommn:
Hmmm, changelogs you say? What a novel idea...haha. After reading about the script to change the min freq to 192 I wonder if this is the issue we are facing testing this. More testing to confirm. :)

So I read post 3, deleted the init.d script and still cant get 304 to stick.
[Nexus 4 Android Development] thracemerin:
You did flash B1 then B6, right?
[Nexus 4 Android Development] ctfrommn:
Hmm, missed that little detail.....embarassed

Ok, stupidity corrected. Big difference too, much smoother. Is default really Interactive? I cleared all kernel apps data and thats what it booted with.
[Nexus 4 Android Development] thracemerin:
If not you probably have mpdecision and thermald on, which would override and/or fight with auto hotplug :)
[Nexus 4 Android Development] ctfrommn:
Actually I had Trinity on before, so mpdecision was removed but as I said above huge difference doing it correctly.
[Nexus 4 Android Development] thracemerin:
[MENTION=4110652]ctfrommn[/MENTION] alpha with stock clocks is posted, it's 4cdc6d0, should be on goo.im shortly.

For everyone else, details are in Post 4.

I made this build to further the testing ctfrommn was doing for me, but there is no reason you can't use this build assuming you don't want to overclock. Assuming the testing we've done is right, we probably weren't actually on 304 or 192 anyway.
[Nexus 4 Android Development] SkyBeam2048:
Actually this really explains some things. I was wondering why anyone would see such strange increase in voltage required for most users at >1GHz. My own device appeared to run fine [MENTION=1601421]600[/MENTION]mV 1134MHz but then requiring a huge bump to 862.5mV for the next step (1242MHz).

Taking your findings into account it perfectly makes sense since the device might actually run at 850mV and 1242MHz is the frequency which does simply not run stable any more at 850mV. So I will have to re-verify voltages for frequencies below 862.5mV but I can definitely set 192MHz-1134MHz to 850mV to start testing with lower ones. Also I hope that 192Mhz is will run with actually lower voltage than 850mV since my device spends most time in deep sleep or at 192MHz.

Just make sure to announce in first post that up to now UV was capped at 850mV and people should first reset to this minimal voltage to be sure their device runs stable. Else I guess many devices (including my one) will instantly crash when applying existing settings of 600mV up to 1134MHz.

I guess the UnderVolting Motley spreadsheet on Google Docs will require an update.
[Nexus 4 Android Development] Remoteconcern:
Good work thraceramin. It works now. Old settings caused an instant reboot.
[Nexus 4 Android Development] thracemerin:
Are you saying that the warning in Post 4 is not large enough? :p

I'll of course put it in post 1 when it goes to the mainline build.
[Nexus 4 Android Development] brainbeatuk:
Done a two hour try and overheat. Seems safe I have done.

2 an tutu stability tests

2 stability test an tutu

A bit of GTA vc gaming in between above

2 geekbench 2 tests running during stability test 1600 score.

Screen .allways on sync on ect. Full no privacy experience :)

I am under conclusion that GTA BC at full gfx settings after twenty mins does get to 66 so inevitably won't be able to play for heavy session. If you have thermal stock settings on it will eventually go poor frame rate. So either way unable to experience great. Its the game engine. You get 60fps indoors and in corridors but goes to 30-60 when outside.

What's more draw 1512 x600 or 1296 x 950. If I'm doing 600 now of course :) Ive def noticed it cooler I tried this script before on build 5

P.s android tuner seems to have bug when I pick record for one hour it actually did 2 hours even though at bottom says one hr. for ten mins was five mins lol.

Another strange quirk I can not under volt 304 to 600 it crashes :) only tried changing that freq and bam.
[Nexus 4 Android Development] gsans:
Hi,

Very weard... the new B6 Kernel not run with Touch Control....

Touch Control not found the kernel... with Motley B49, it was ok

Any problem ?

Regards
[Nexus 4 Android Development] thracemerin:
After you run your script, go to /sys/devices/system/cpu/cpufreq/vdd_table and open vdd_levels with a text editor and copy it to here, I want to see if it's actually sticking.
[Nexus 4 Android Development] thracemerin:
Post 3:
[Nexus 4 Android Development] gsans:
Ah ok... so bad

thank you
[Nexus 4 Android Development] brainbeatuk:
192000: 625000

304000: 637500

486000: 700000

594000: 725000

702000: 775000

810000: 850000

918000: 862500

1026000: 862500

1134000: 887500

1242000: 900000

1296000: 950000

1350000: 1035000

1404000: 1037500

1458000: 1040000

1512000: 600000

1566000: 1067500

1620000: 1075000

1674000: 1100000
[Nexus 4 Android Development] thracemerin:
Yeah, I have no idea how this works for you, when I tried it it locked up my device so badly it corrupted my data (this is why testing with fsync off is a bad idea kids :cool:). My guess is that something in the performance governor or the thermal controller is setting the voltage, but I don't see where it would be happening, maybe you got some sort of freak device.
[Nexus 4 Android Development] brainbeatuk:
Try changing all the freq steps to default i undervolted them too but are on edge for me. I cannot do 600 without thermal off it appears and maybe change 1512 to 700. I'm sure you may have to do as init.d. as the switchover you have to do have all cores online when script running use geekbench

Even with thermal off I cannot under volt to 600 on the interactive cores. So its definitely to do with the performance governor. It only works on perf
[Nexus 4 Android Development] SkyBeam2048:
Indeed I think it's sufficient - at least for me ;)

At least for me I using trickster mod the settings anyway reverted to default each time I upgrade the kernel. Perhaps it's more an issue for people using custom init scripts. But I guess these people will know and understand the implications of the fix.

I did some modification on the Google spreadsheet and hope others will add their real values as well. I will insert as soon as I upgrade to new kernel and stability-tested my voltages. Strange enough that some people claimed they were running unstable at 600mV and added some safety margin (e.g. up by two steps) to get stable results. Not knowing that their phone was always running @850mV no matter whether they select 600mV or 650mV.
[Nexus 4 Android Development] thracemerin:
I'll check again once I unbrick my phone :eek:
[Nexus 4 Android Development] idaadi:
So I'm trying to replicate your setup, but when I run this script I get some errors.... Plus my antutu benchmark only does 16000.

Any suggestions please?

Log output:

" System Tuner (terminal)

=======================

> sh /sdcard/motleyscriptthermal (su)

=======================

Unable to chmod /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor: No such file or directory

/sdcard/motleyscriptthermal[12]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq: No such file or directory

/sdcard/motleyscriptthermal[14]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq: No such file or directory

/sdcard/motleyscriptthermal[16]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor: No such file or directory

/sdcard/motleyscriptthermal[19]: can't create /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq: No such file or directory

/sdcard/motleyscriptthermal[21]: can't create /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq: No such file or directory

/sdcard/motleyscriptthermal[23]: can't create /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor: No such file or directory

/sdcard/motleyscriptthermal[26]: can't create /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq: No such file or directory

/sdcard/motleyscriptthermal[28]: can't create /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq: No such file or directory

Unable to chmod /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq: No such file or directory

/sdcard/motleyscriptthermal[30]: can't create /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq: No such file or directory

"
[Nexus 4 Android Development] brainbeatuk:
I have edited script should force all four online at beginning and made volts stock and 800 for 1512

You need to have all cores on when the script is ran otherwise won't change cores that are offline. If doing as script use a benchmark like geekbench run script during it. There is likely a script line to force all four cores online too if so add to beggining of script

I have on init.d but obviously you need to test voltage first :)

Im using linaro optimised prime runner ROM. Stock would get between 16-18 I guess
[Nexus 4 Android Development] idaadi:
Much better: I forced all CPU's online with System Tuner

as for the script line : echo 1 > /sys/devices/system/cpu/cpu1/online etc... (Try it , if it works , please modify your script inside the previous post so it's complete)

I think you should add a 1 before changing the stuff , and then 0 after , or no?

Edit: or with the min_online cpu's like you did , thx

BTW , I get a restart/freeze whenever I want to watch statistics with faux's app , but I can watch them ok inside System tuner...

I got 19700 in Antutu , and will try to compare batt life with the previous setup.

BR and thx
[Nexus 4 Android Development] brainbeatuk:
I think if you did a 0 it turns off but. The performance cores will not be on unless its gaming or benchmarks I found. Still got hot plug governor turning them on and off. The original script is edited I don't wanna spam more :)

What you running 1512 at?

Remember to keep eye on temp. Its like manually tweaking an engine Lol. Use analyser if system tuner has it? Change record items tick CPU freq and temp
[Nexus 4 Android Development] idaadi:
I'm running your initial script , with the UV voltages.. so at 600 but I'm gonna do a scaling Stability test and check if everything holds...

BR

Crashed at 1512 so I'll keep searching for that voltage.. just testing at 1512 this time... Will post the end voltage in a few...
[Nexus 4 Android Development] brainbeatuk:
Cool i not used. I'm sure it will crash if its forcing all four to 1512 though! Rule 1 interactive CPU Max lower than performance. Apps like trickster and faux stability test? Don't have multi core CPU control like SYS/android tuner
[Nexus 4 Android Development] idaadi:
Any idea why my phone is stable at low freqs (192mhz [MENTION=374871]625[/MENTION]000 304mhz@637500 ) but after i let it sit/ I guess it goes into deep sleep or some low power state , it restarts....

what should I increase? is there any way you guys know to find out what it doesn't like ?

BR

[MENTION=4896574]brainbeatuk[/MENTION] when you specify the min freq 304 , then the 192 shouldn't be used , right?
[Nexus 4 Android Development] brainbeatuk:
Bump all them all up by 100. Maybe you cant uv that low. I cant do 304 at 600 anymore myself unless i used performance .See if that helps

Regarding 192 just my pref never tested with 192 min.

BTW I have 3 hr screen on time 40% left least hr of 3d gaming. Will post final. Suspect battery lying as first full run cycle on primerunner
[Nexus 4 Android Development] thracemerin:
Your device will require the most power when coming out of deep sleep, if you're having crashes/restarts during the wakeup sequence you've UV'd it too much
[Nexus 4 Android Development] caliban2:
Actually it will use way more power than it could ever save by undervolting during that reboot after the crash... ;)
[Nexus 4 Android Development] thracemerin:
That too.
[Nexus 4 Android Development] idaadi:
It's not that ... I just leave it untouched for 15-30 secs and then it restarts , it wakes up just fine until then. Do you know how fast it normally goes into deep sleep? Now i'm testing with the stock voltages to see if it still happens . [MENTION=4896574]brainbeatuk[/MENTION] , try leaving your phone untouched for 1 min , does it restart? [MENTION=4303511]thracemerin[/MENTION] last post , promise. I appologize for spamming your thread

BR
[Nexus 4 Android Development] thracemerin:
Don't worry about it, that's what the thread is for :)

I noticed the glitch with the UV thanks to somewhat unrelated discussion that was going on in here, so you may think you're spamming the thread with irrelevant stuff, but sometimes it gets me thinking about stuff and I find/fix things.
[Nexus 4 Android Development] brainbeatuk:
Mines stable been pudding round for weeks :). Tested again just in case and I'm fine. It'll be the interactive volts in my opinion

Caliban you lost me :)
[Nexus 4 Android Development] thracemerin:
Well, for those who are interested, over a roughly 18 hour idle (its nice to have access to 2 devices for these tests) on my N4 there is almost no difference in drain betweeen 192MHz and 384MHz being the minimum (all else being equal), this lends further evidence to the theory that we are not in fact using 192MHz despite it being set. This is by no means a scientific test, and without disassembling the device and doing tests on the actual chips themselves we can't know for 100% sure, but I'm beginning to think show-p1984 is correct that frequencies below 384MHz are not set.
[Nexus 4 Android Development] sirxdroid:
There was a post by faux123 I think in his kernel FAQ that said Qualcomm deemed freq < 384 as unstable, so it would make sense for them to actually enforce 384 somehow.

[MENTION=4303511]thracemerin[/MENTION] - couple of questions on the gamma interface, you know, just to switch topics a bit :)

(1) In the OP there's an example using Faux' presets. I tried setting those out of curiosity but they don't take. Perhaps because the numbers are invalid. If so, I think it's better to just remove them from the OP.

#!/system/bin/sh
# Set faux Google presets ([B]not sure why his numbers differ[/B])
echo "460 64 68 118 1 32 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "461 64 68 118 1 33 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "445 32 35 116 0 32 96 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue

(2) If I use Trickster to set any of the presets PA Brighter/Contrasty/Halfbreed and then I read the values from sysfs, it seems that greys and whites are swapped. I'm comparing this spec from the OP:

checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
^^^^^ ^^^^

With the values from the spreadsheet for the molesarecoming profiles, e.g. for Halfbreed 64 and 32 are swapped.

# cat /sys/devices/platform/mipi_lgit.1537/kgamma_red
378 64 68 118 0 25 4 66 32 1
^^ ^^

Could you please take a look at the code when you have a chance and if the code is correct just fix the OP spec?
[Nexus 4 Android Development] thracemerin:
There is some debate over which value is white and which value is grey, I believe franco put forward that they were swapped in the initial assessment that was done, but I never saw that anyone confirmed this for sure. Molesarecoming still uses whites first then greys as _motley does (i think faux may also still use this), franco uses greys first, it looks like trickster uses franco's interpretation. I personally have no idea which is right and there is no reference manual for how these values are set by LG or Google so we have to go with people's best guess, I'm not really inclined to change it without some sort of consensus being reached.
[Nexus 4 Android Development] sirxdroid:
I solved the problem: I'm using color profiles where grey == white :)

Motley uses Faux gamma interface, right? I can't find the spec for the Faux color interface in the faux123 kernel thread.
[Nexus 4 Android Development] thracemerin:
Reading what _motley originally wrote again, now I'm not sure if franco suggested that it was greys first then whites or vice versa, I'm so confused :confused:

What I can tell you is that the order that is in post 2 is the order that molesarecoming sets the values in his calibrated kernels, whether that's the right order or not, I have no idea.
[Nexus 4 Android Development] sirxdroid:
But now Franco worked on the latest PA kernel. Yes, clear as mud :confused:
[Nexus 4 Android Development] thracemerin:
Yeah, I don't have any idea anymore, I'm just going to leave it for lack of a better option. :D

I was going to say something in the semaphore thread, but given the fact that I have no idea what I'm talking about I should probably avoid it.

I did remove those faux values from Post 2 though.
[Nexus 4 Android Development] sirxdroid:
This is why Google should just expose the gamma interface in their next kernel, just like they did with the RGB values. I'm sure they should be able to get a clear answer from LG.
[Nexus 4 Android Development] thracemerin:
But, Google likes the ****ty colors that come with stock.
[Nexus 4 Android Development] brainbeatuk:
Hi again. Any idea why the voltage goes up n down. I've uploaded a battery stat screenshot. Good a good solid battery time in my opinion. Also from five percent I changed high speed freq to 702 and changed ideal load to 99. Noticed improvement in draw and benchmark.

Also you said maybe I had a freaky nexus may be true :). When I try halfbaked ect it looks right to me but using display tester my yellows magenta cyan gamma level are a mess. Using obsanity preset when on Franco was the closest to 2.2 on every colour. If someone has a script be much appreciated
[Nexus 4 Android Development] veyka:
Are you going to revert this as well? http://review.cyanogenmod.org/#/c/37851/

Sent via Nexus 4
[Nexus 4 Android Development] thracemerin:
Seems like I probably should. I will before B7 live.

Like Steve Kondik pointed out, it is reverted upstream at codeaurora: https://www.codeaurora.org/gitweb/q...it;h=7a80a938cae195d13978ad1420b35b8b57650f8e
[Nexus 4 Android Development] thracemerin:
I can step it down further, but the lower the uV the higher chance of instability (SODs or random reboots).
[Nexus 4 Android Development] sirxdroid:
Wow, how much lower do you want to push it? My phone I don't think can even do 725mV and it claims to be a Fast bin. -100mV from the stock voltages and I'm happy :)
[Nexus 4 Android Development] UgoBoss:
I just wanted to flash this kernel but I was wondering, am I obliged to do scripts to tune kernel ? Or can I control this kernel with faux's or franco's app ?

Thanks :)

Always connected with Tapatalk {¤_¤}
[Nexus 4 Android Development] veyka:
I found tricksters mod worked well before i started doing everything via script, so you can try that :)

Sent via Nexus 4
[Nexus 4 Android Development] Remoteconcern:
Thanks for continuing the work that motley started.

What kind of plans do you have for this kernel? I was just wondering what to expect in future updates. Thanks!
[Nexus 4 Android Development] UgoBoss:
Ok I'll try that Thanks ;)

Always connected with Tapatalk {¤_¤}
[Nexus 4 Android Development] MaDInDy:
I flashed _m+ kernel with linaro cm 10.1 trailblazerz11's build.

It is smooth and fast for me.

Thank you.
[Nexus 4 Android Development] gsans:
Hi,

I am on B49 Motley Kernel, it's the same as your first release Motley+ ?

regards
[Nexus 4 Android Development] Remoteconcern:
Yes, the same.
[Nexus 4 Android Development] gsans:
Thank you :o
[Nexus 4 Android Development] thracemerin:
I don't have some grand long term plan, but I can tell you what I added to Build 2 so far :)

Krait Retention

Fully updated ROW with all the newest CAF tweaks & magic values from franco (now default i/o sched)

FIOPS sched was removed because _motley committed FIOPS and ROW together, I'll re-add it if it was people's favorite and they want it still.

Fully updated interactive governor to the newest CAF version

My device hasn't blown up and I haven't had any odd problems with it, so expect that later today.
[Nexus 4 Android Development] thracemerin:
Build 2 is available, see the changelog in Post 1 for details.

Keep in mind, like _motley's builds this is an update to build 1, you need to be on build 1 first before flashing it or you may experience some unexpected results.

Happy flashing :victory:
[Nexus 4 Android Development] Remoteconcern:
Right, just flashed. Thanks. Immediately I notice a second core comes online with interacting with the screen, like the input boost. I'll see how this affects battery and things!

Does retention still need to be enabled manually, or is that state turned on by default.
[Nexus 4 Android Development] thracemerin:
Krait retention functions the same way it did on kszaq's build, you need to enable it manually.

echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled

Retention is only available for cpu0 on this board, so echoing this to cpu1-3 will be ignored.