yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Remoteconcern:
Thank you, much appreciated! Enabled now, I'll see if there's any noticeable difference. I'm guessing it will be small if its only enableable for one core.
[Nexus 4 Android Development] veyka:
I uploaded a ton of init scripts to http://www.veyka.co.uk/other/motley/, colour profiles, ktweaks (which is my personal general tweaks, nothing dangerous, no extra UV, OC, etc), sound and touch tweaks (touch being the settings from the lastest version of franco posted in motleys thread by someone!).

Feel free to use and abuse as you see fit!
[Nexus 4 Android Development] IAmAN00bie:
Thanks! This is all I've really wanted. Motley's was perfect as is, so just updating it with the newest patches from CAF makes it even better.

Also, thanks a bunch for the scripts, veyka.
[Nexus 4 Android Development] thracemerin:
It is my understanding that it won't matter that much that cpu1-3 don't go into retention state since they should be hotplugged to offline before cpu0 would go into the retention state anyway.

Also, you may notice a little more wakeup latency when cpu0 goes into retention state since it is sleeping more deeply than it does normally.
[Nexus 4 Android Development] thetinguy:
Thank you so much for continuing motley's kernel!!!!!!!!
[Nexus 4 Android Development] senses!:
Thanks!! One question...notificacion fix of primo drivers?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Android Development] Kocai:
What's interesting for me is that the stock kernel on PA 3.55 that's tweaked by Franco has somewhat brighter colors. He exposed the gamma control and used his newest implementation where you can change the blacks, mids, greys, whites for each RGB gamma. When I changed the colors with the same numbers I use (visceralpsyche setting) my screen looks brighter and it's brighter than when I used the same numbers on Franco's kernel and this kernel. At first I thought it was just my eyes playing tricks on me but I asked my sister and my cousin and they agreed it's brighter.

I have the boot.img if someone want to test it out using their preferred color settings. Unfortunately I don't have the knowledge to make a flashable zip. I believe Franco didn't modify the ramdisk since I can flash m+ without getting stuck in a bootloop which makes sense since PA wouldn't want people start complaining they got stuck in a bootloop when flashing other custom kernel.
[Nexus 4 Android Development] Remoteconcern:
Further anecdotal evidence that the clocks are the same - I can't use a lower voltage for 192 compared to 384, I get crashes below 675mV.

I'm actually using the version with the totally stock clocks, I think it's probably the way forward.

Just for your information, I know Franco's most recent kernel has something about more idle drain patches, but I'm sure you know about them already :)

Thanks!
[Nexus 4 Android Development] thracemerin:
I don't see anything in the PA device tree where Franco changed the default color settings. I suppose that he may have changed something when he introduced his gamma interface, but I don't see it with a cursory glance.

Yeah, this makes me wonder whether overclocking frequencies are sticking, I guess we'll need to test that too, but given the evidence I think we'll go back to 384MHz as the minimum frequency step.

Looks like the idle drain patches you're referring to are more fixes to freezer by Colin Cross, I'll see about adding them as well.
[Nexus 4 Android Development] Kocai:
The default color settings is still the same halfbreed. Among other things, Franco exposed the gamma control. I don't have much knowledge about this but I suspect since brightness is from ROM side, it's possible that the modified stock kernel by Franco are brighter, but only in PA ROM.
[Nexus 4 Android Development] Remoteconcern:
Correct, those are the patches. Thanks.

I hadn't thought about that. But given the benchmark increase with overclocking, I would say they probably are.

I never overclock though, and it's possible not many of us do. It could be safe just to leave out.
[Nexus 4 Android Development] thracemerin:
Yeah, autobrightness values are set by the ROM, I know moles was talking about the autobrightness values on stock being crap too, so it's possible they've been changed for PA.

I'm going to leave the OC frequencies out for the next few Alphas, if people come in here and express a strong desire to have them it doesn't take much to put them back in.

I'll get those other freezer patches in a new Alpha today or tomorrow, I also noticed that faux123 has updated dynamic fsync to put in some safeties in case of unplanned reboot or kernel panic (probably would have saved me a soft brick when I was screwing with undervolting the other day), I'll see about adding that stuff too.
[Nexus 4 Android Development] ctfrommn:
I agree that the new PA kernel does look different then the old one. Im not sure which gamma they were using before. If it was Faux's, that would explain a lot. Franco's exposes a different level of values then Faux does.

As for OC, unless youre benchmarking there is zero value or need for it IMHO. Ive never seen any difference in real world use OC'ing. Oh, except for more heat and battery consumption.

What exactly are these new "freezer" commits designed to do?
[Nexus 4 Android Development] thracemerin:
It's my understanding that freezer is the process that stops kernel work when the phone goes into suspend, the patches are designed to make this process more efficient.
[Nexus 4 Android Development] ctfrommn:
Appreciate it....an appropo name for them then :)
[Nexus 4 Android Development] idaadi:
Personally I've played games UV'd and max freq at 1.13ghz(noticed a nonlinear greater need for power over 1 ghz) and I am very happy with the game play experience(no lag) . Plus I rarely play more that 30 mins at a time..... Finding solutions for lowering standby consumption and maybe alternating with those 2 cores at 600mv with performance would be a really nice solution... I've tried faux, Franco, harsh and motley kernels, out of these the most suiting was motley and then harsh...

At the end of the day, the one that gets me 1d and 16hrs (motley+) with everything turned on is the winner

Thanks for your work, personally I don't mind dumping OC freqs

WBR
[Nexus 4 Android Development] rlaw:
I don't see why OC freqs are being omitted.

The kernel doesn't clock to them by default and hurts no one by including them in there.

And by my own experience, the OC freqs are applied - unlike what we've discovered here that UC perhaps doesn't.
[Nexus 4 Android Development] sirxdroid:
I think you are right. In general I noticed that Halfbreed colors (or other dark profiles) look much better if you increase the screen brightness to around 50%. Some ROMs have customizable lux values for each auto brightness level. I don't know whether PA takes it to that level, but I'm pretty sure they do bump them up from the defaults.
[Nexus 4 Android Development] ctfrommn:
They have them, but I am almost positive they are default. I think many other Roms that use them choose lower than stock values. If you flash the old PA kernel from Goo and then flash the new one, you will see there is a difference. But I digress :)
[Nexus 4 Android Development] sirxdroid:
Could also be the grey/white swap, you can try swapping the values for grey and white, 64 and 32 and see if it makes a difference. I think Franco suggested that they should be swapped after molesarecoming "old" PA kernels.

I tried it and with my screen on auto-brightness and my eyes I can't really tell a difference, they are both equally dark, too dark for me. Maybe you guys have different screens and/or more sensitive eyes. My profile of choice is bundi22 from the spreadsheet which is brighter and that's how I like them :)
[Nexus 4 Android Development] thracemerin:
New Alpha in Post 4, all the details are there.

The dynamic fsync changes will require a little more work, because faux only has dynamic fsync and not fsync control as well so the patches don't merge nicely, i'll get those sorted ASAP.

Happy Flashing :victory:
[Nexus 4 Android Development] thracemerin:
To finish this discussion:

the number in the <item> tags is the brightness value from 0-255

the numbers in the <!-- tags is the range in lux for that brightness value.

Stock Auto-brightness levels:

<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>14</item> <!-- 0-10 -->
<item>28</item> <!-- 10-50 -->
<item>37</item> <!-- 50-100 -->
<item>51</item> <!-- 100-200 -->
<item>71</item> <!-- 200-400 -->
<item>80</item> <!-- 400-500 -->
<item>96</item> <!-- 500-800 -->
<item>108</item> <!-- 800-1000 -->
<item>144</item> <!-- 1000-1600 -->
<item>181</item> <!-- 1600-3000 -->
<item>254</item> <!-- 3000-10000 -->
<item>255</item> <!-- 10000+ -->
</integer-array>

PA Auto-brightness levels:

<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>18</item> <!-- 0-10 -->
<item>33</item> <!-- 10-50 -->
<item>47</item> <!-- 50-100 -->
<item>63</item> <!-- 100-200 -->
<item>85</item> <!-- 200-400 -->
<item>94</item> <!-- 400-500 -->
<item>110</item> <!-- 500-800 -->
<item>126</item> <!-- 800-1000 -->
<item>162</item> <!-- 1000-1600 -->
<item>196</item> <!-- 1600-3000 -->
<item>250</item> <!-- 3000-10000 -->
<item>255</item> <!-- 10000+ -->
</integer-array>

So, it's a setting specific to the PA Rom that makes it brighter.
[Nexus 4 Android Development] ctfrommn:
Hmmm, I stand corrected then. I was mostly replying to the fact that old PA and new PA kernels look different, but I wont clutter this thread with anymore of it :)
[Nexus 4 Android Development] thracemerin:
Well, its possible that they are different too, but using the PA color settings on a ROM with different auto-brightness levels will result in a different look :)
[Nexus 4 Android Development] sirxdroid:
I tried them both on the exact same ROM (EOS), same settings and they looked the same to me. Again they look so dark to me that all dark profiles look the same on my phone :laugh:
[Nexus 4 Android Development] 3c:
Setting custom RGB color settings via sysfs

Sorry if it was asked before, but how does the 6 extra values in the spreadsheet (amp 0 & 1) do correlate with the 7x3 values defined above? Asking because I'm implemented a UI for this in Android Tuner, and would like to include some presets from the spreadsheet.

By the way, who to and how do I request permission to include the presets defined in that spreadsheet into my app?

Thanks.
[Nexus 4 Android Development] rodries:
Hi thracemerin

Sorry for asking again, but any possibility to include latest prima drivers in your kernel?

I know that you want to create differents wifi modules, but I have a lot of problems with speed & lag in wifi.
[Nexus 4 Android Development] thracemerin:
The latest Prima drivers are not for this device, they are for the Qualcomm testing platform which uses a different version of the Riva WiFi/Bluetooth chip than the one that is in the N4, as a result there are many issues that result from using these drivers with the N4. You can see this by reading the various threads for kernels that include them in the forums, including my own thread on the subject.

The current version of Prima for the N4 is 3.2.1.13 and that is still the version for jb_mr1 on codeaurora: https://www.codeaurora.org/gitweb/e...efs/heads/jb-mr1-dev;hb=refs/heads/jb-mr1-dev
[Nexus 4 Android Development] thracemerin:
A note about undervolting that I neglected to mention before, when I reset the stock clocks I also reset the voltages to stock. Why? because with the change to make undervolting actually work I felt it better to use the known safe voltages from Google rather than risk the potential that some people would have difficulties with _motley's stock undervolt settings, as a result if you hadn't set the voltage table yourself with a script or kernel tuning app you are running at higher voltages than you were prior to flashing the latest Alpha, you may want to adjust your voltages down again.

Edit: I updated Post 4 to reflect this and another change I originally neglected to mention.
[Nexus 4 Android Development] 3c:
Gamma controls - new UI

Android Tuner now supports Gamma controls for this kernel, as seen on attached screenshots :D

Should you have a problem or comment, feel free to let me know on app thread or using app "help and support".
[Nexus 4 Android Development] veyka:
I have uploaded an updated version of my kernel tweaks init script, along with a init script for the fast bined voltage table that was reverted, to http://www.veyka.co.uk/other/motley/

by default 384mhz is commented out as the voltage in the table would be below the old limit of 850mv so test before you set as boot.

Also echo "N" > /sys/module/acpuclock_krait/parameters/boost is commented out in the ktweaks script, as I use it myself but I wouldn't consider it safe if you are fiddling with UV elsewhere.
[Nexus 4 Android Development] Misledz:
This is the only kernel that works properly for me. I was hesitant to try it then everyone on reddit recommended it and so I did. And I'm glad I did.
[Nexus 4 Android Development] FeintDoxx:
I'm sorry but where else can I download the kernel?

I tried using: http://goo.im/devs/thracemerin/mako/m_plus but it won't open I keep on getting an HTTP error 504..
[Nexus 4 Android Development] superleeds27:
Goo is down!
[Nexus 4 Android Development] FeintDoxx:
Does any one still have B1 and B6 that they can upload to drop box or something and pm the link? Not sure if Thrace wants other links on this post.
[Nexus 4 Android Development] thracemerin:
goo.im is working for me now, it wasn't before.
[Nexus 4 Android Development] DontPushButtons:
Check PM

---------- Post added at 09:01 AM ---------- Previous post was at 09:01 AM ----------

Oops, scratch that. Seems goo is working again.
[Nexus 4 Android Development] thracemerin:
It's Sunday and you know what that means :D

The buildbot is currently working on Build 7, if all goes well it should be on goo.im within the hour.

Change log is already updated in Post 1.

Happy Flashing :victory:
[Nexus 4 Android Development] FeintDoxx:
Yes!!! I've been running build 49 of the last _motley but I wanted to flash up to b6 of your addons and now its at b7 yes!!!

---------- Post added at 01:56 PM ---------- Previous post was at 01:44 PM ----------

Thanks any way:)

---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------

Hu.. Goo is not working for me..
[Nexus 4 Android Development] efan3719:
Goo is down for me as well :(
[Nexus 4 Android Development] thracemerin:
Strange, now it is again.
[Nexus 4 Android Development] thracemerin:
It's back up again :victory:

But, just in case:

Build 1 (CM Version): m_plus_422_build_1_CM.zip - 4.97 MB - d5944a9c40ebd965ce4b620a0e64c82c

Build 1 (Stock Version): m_plus_422_build_1_stock.zip - 4.96 MB - 58964d7a18ff35e413d54e6b29e17d2d

Build 7: m_plus_anykernel_422_build_7.zip - 5.28 MB - a890a67b46bc1e94ac760a785af49a40
[Nexus 4 Android Development] FeintDoxx:
Much obliged:)
[Nexus 4 Android Development] sirxdroid:
Thanks. Unfortunately goo.im has been a mess lately. I guess Android projects are blooming, the growing pains.
[Nexus 4 Android Development] FeintDoxx:
Okay cool! Just flashed b1 then b7 and everything went great! Idk if it was because of the kernel but even the response time from the touch is back instantly as before there was a delay of about 20 seconds after reboot because of the E015 touch driver that I installed.

---------- Post added at 03:11 PM ---------- Previous post was at 02:48 PM ----------

Hmm. My UV setting don't seem to stick. I'm using System Tuner and i change the voltage value but it goes back to stock.
[Nexus 4 Android Development] thracemerin:
Strange, mine stick using both a script and with trickster, haven't tried System Tuner though.
[Nexus 4 Android Development] Remoteconcern:
Do you have busy box installed? Might be necessary for system tuner if it doesn't include it's own version.
[Nexus 4 Android Development] FeintDoxx:
I got them to stick with Android Tuner. Its practically the same thing but just with more tweaks. I don't know why System Tuner wasn't working. Either way since I'm fairly new to UVing I followed the UV table https://docs.google.com/spreadsheet/lv?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc#gid=0 but I read somewhere that it was a bit outdated. Is there a more recent table or recommended UV values for this kernel?

---------- Post added at 05:33 PM ---------- Previous post was at 05:31 PM ----------

Yes I have it installed. Don't know why it's not working although I got it working with Android Tuner.
[Nexus 4 Android Development] thracemerin:
There was a glitch in the code in _motley's kernel where voltages below 850mV weren't actually being set, so people would think they were undervolting to 600mV when in fact they weren't. Since every chip is different, I suggest slowly lowering the voltages (say -50mV at a time, don't set on boot) from the default and seeing if you have stability issues, if you don't then you can push it down a little more and keep trying it till you find you get random reboots or SODs.

If you know the binning on your chip, I can give you the old defaults that _motley used to use, they are probably safe.
[Nexus 4 Android Development] FeintDoxx:
Since I don't have access to a computer I would have to go with the first method and just see how things go. Thanks for the help:)
[Nexus 4 Android Development] thracemerin:
Here's the voltages for the various bins from Motley b49: https://docs.google.com/spreadsheet/ccc?key=0AlgoC5O8VXsLdFU4U2xnSUxwUlNyQ05TVHF3ZDJCdXc&usp=sharing

You can try them, they're probably safe (be especially careful with setting voltages below 850mV), you can find your chips bin by using the method in Post 2.
[Nexus 4 Android Development] FeintDoxx:
From the looks of it I got lucky, faster.
[Nexus 4 Android Development] thracemerin:
Faster bin chips can usually take more undervolt than others.

An important note: there's a system on krait cpus that boosts the voltage of every step by 25mV for all bins except slow.

If you do the following in terminal or via an init.d script:

echo "N" > /sys/module/acpuclock_krait/parameters/boost

It will shut that off and your voltages will be 25mV less.

For example: if you have a faster bin and set 825mV for a step, if boost is on the actual voltage is 850mV, if you turn boost off it's 825mV.
[Nexus 4 Android Development] FeintDoxx:
Thanks! That's some helpful advice. I'll run that on the terminal and see how it runs.

---------- Post added at 12:23 AM ---------- Previous post was at 12:12 AM ----------

BTW once the code is run in terminal am I supposed to get an other line or is there a way to check wether or not the boost is on.
[Nexus 4 Android Development] thracemerin:
You can use a file explorer with root permissions to look at the file that you echo to.
[Nexus 4 Android Development] FeintDoxx:
Alright. Thanks for all the help!
[Nexus 4 Android Development] Ace42:
Thracemerin, any chance you'll consider adding PegasusQ, and Lazy governors?
[Nexus 4 Android Development] thracemerin:
The CAF versions of interactive and on demand are built with the Nexus 4 in mind, many of the other governors that are floating around XDA are for dual and single core processors or completely different architectures and while they may work they are ultimately suboptimal on our device, with this in mind I would say its very unlikely that I would.
[Nexus 4 Android Development] Ace42:
It's good to see that Qualcomm has outfitted the governors just for us, I knew they made row but not this also.

Anyway I had wanted the feature of lazy that prevents erratic behavior by introducing a min time to stay at a frequency, the Dev states it prevents lag, but as you stated that's from the single core era.
[Nexus 4 Android Development] FeintDoxx:
I have to say. Your builds for motley are amazing. With motley kernel and UV from your recommendation. It increased my screen time usage and I finally got a 14 hour battery time. This is only my second day using your build. I can't wait to see how things are after a few more power cycles :D
[Nexus 4 Android Development] Dactylion:
Hhm why didnt you reset voltages to atleast google stock -50mv. Do you intent to release with lower voltage in de future so users dont need to install additional apps for good battery performance?
[Nexus 4 Android Development] thracemerin:
I get excellent battery life anyway, and there is no need to install anything, you can set the voltages with a script.
[Nexus 4 Android Development] Dactylion:
l

Yes like u said u need to add an init script manually

everytime you install. Maybe youve got fast binned soc.
[Nexus 4 Android Development] thracemerin:
I actually have a slow binned chip on the N4 I use regularly because I find its a better testing platform since it should be the least able to handle things like overclocking and undervolting.
[Nexus 4 Android Development] swaggerwocky:
Scripts placed in /data/local/userinit.d survive kernel flashes.
[Nexus 4 Android Development] thracemerin:
init.d scripts should survive unless you wipe /system
[Nexus 4 Android Development] thunderger:
something seems to be wrong with B7. Today I've to do a hard reset and after this the phone isn't working correct.

Waht happened?! I used Google Maps with GPS enabled to navigate to adress. After this I put my N4 back to my trousers pocket. Google Maps said two or three times no GPS signal. Then there was silence and i noticed my N4 getting very hot. At work I took a look and saw that it hangs in CM boot animation.

I booted into recovery, did a cache and dalvik wipe, rebooted it. Android said optimizing apps but never finished. So I did a factory reset, fixed permissions, flashed CM nightly an m+ B1 & B7 again, wiped cache and dalvik again and rebooted.

Now I could enter system, had to enter google account information again. But systemUI and all other services crashed. After this I'm again in bootloop.

I can't use my N4 anymore. Before flashing B7 I reset all UV/OC and uninstalled Trickster mod. It ran for two days untill I used Google Maps and GPS. :(
[Nexus 4 Android Development] antih3ro:
I had something like this twice but not only with motleys. factory reset worked for me. Try do download ROM and kernel files again, or use older ones and try factory reset again.
[Nexus 4 Android Development] :
For me exactly the same! I had to do a factory reset to bring my n4 back to live :(

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Nexus 4 Android Development] veyka:
Do you run with fsync off?
[Nexus 4 Android Development] rlaw:
Try a stable ROM release or earlier nightly, mate.
[Nexus 4 Android Development] thracemerin:
Can't say I've had this happen, though the GPS issue is similar to one that people in the CM thread have reported from time to time where the GPS doesn't actually turn off when you exit the program that has been using it and continues to run in the background until you reboot, the would generate a fair amount of heat and burn your battery pretty badly, it could also have potentially caused the crash you are talking about.

As for the boot loops/loss of data, as others have pointed out, if you run fsync off (even with dynamic fsync) you risk file system corruption when your device shuts down in a less than graceful manner (soft reboot, sod, hard reboot, etc) when this happens you could end up with anything from a partial boot to being stuck at the Google logo, this is why Google leaves fsync on by default.

I'll have a look but since this is going to be a difficult one to actually reproduce I'm not sure I can track it down without logs and I'm inclined to believe its probably related to the GPS problem I talked about above which is a ROM problem not a kernel problem.
[Nexus 4 Android Development] antih3ro:
I also think it's Rom related. One time I was on motley second time on franco, on both using CM.
[Nexus 4 Android Development] Serious_Beans:
So just to be clear..if im using an aosp rom i flash b1 and then b7?
[Nexus 4 Android Development] "D":
Yes,

"Note: You must be on Build 1 or later."

"D"