yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] saint_cow:
By having C0 enabled does that turn wifi off when the screen is off?
[Nexus 4 Original Android Development] beren:
[MENTION=3332811]faux123[/MENTION]

any chance to see doubletap 2 wake option in fauxclock app?
[Nexus 4 Original Android Development] FuPete:
No. The C-states are just the sleep States. C0 is a slight sleep, C3 is deep sleep. As far as I know, none of them turns wifi off.
[Nexus 4 Original Android Development] pikachukaki:
So to get this straight...cause you tick core 1,2 the kernel sees this and when the phone reaches 70 it close them...and when it reaches 85 it lower freq speed (ghz) but i never saw my phone reaching those temps...idle and normal use is at least 40C and gaming 45 +/-2!!!
[Nexus 4 Original Android Development] rmead01:
yeah after some playing around it looks like that how it works. For instance I have my core off lining set at 60 and throttle at 65, i really don't like my phone melting my hand, especially when my son is playing games. So when the phone hits 60, core 2 and 3 turn off, and at 65 cores 1,2,3 throttle leaving core 0 to function as intended, I may actually turn throttling for this core on too.

I was streaming audio and playing a game and my phone throttled exactly how it was supposed to.

Now that my goal is reducing as much heat as possible. I'm wondering if throttling number of cores online or freq of the cores is going to help the most to achieve the results I want. Once I can get my phone to keep the temps I want, I'll be testing the same without sacrificing performance.
[Nexus 4 Original Android Development] stab244:
http://pastebin.com/ujiULM34

Here you go. Nothing sticks out to me. I was just playing CSR Racing and finally unlocked the Pagani Zonda R when that happened. First time that happened but oh well. I usually turn DFS off when I reboot anyways to prevent as much data corruption as possible anyways.
[Nexus 4 Original Android Development] pikachukaki:
I can have this when im charging only...only then i get a really hot phone...not when im playing...

[MENTION=3332811]faux123[/MENTION] it could be nice if you add a function in fauxclock to have the kernel enable ecomode when a defined % has reached!!
[Nexus 4 Original Android Development] faux123:
Hm.. you have a legit kernel panic. It's caused by GPU memory crash... interesting... never seen this before.

My GPU drivers is stock so it must be game related...

[126984.356287] [<c011c8f8>] (kfree+0x128/0x208) from [<c0344900>] (kgsl_sharedmem_free+0x68/0x80)

[126984.356409] [<c0344900>] (kgsl_sharedmem_free+0x68/0x80) from [<c0344dfc>] (_kgsl_sharedmem_page_alloc+0x2d4/0x304)

[126984.356562] [<c0344dfc>] (_kgsl_sharedmem_page_alloc+0x2d4/0x304) from [<c033f868>] (kgsl_ioctl_gpumem_alloc+0x90/0x194)

[126984.356714] [<c033f868>] (kgsl_ioctl_gpumem_alloc+0x90/0x194) from [<c033f6b4>] (kgsl_ioctl+0x200/0x2fc)

[126984.356836] [<c033f6b4>] (kgsl_ioctl+0x200/0x2fc) from [<c01305dc>] (do_vfs_ioctl+0x4d8/0x54c)

Somehow the GPU memory the kernel was trying to release was already "released", so when kernel panic'ed when it couldn't find the portion of the memory....
[Nexus 4 Original Android Development] rmead01:
Well i'm streaming from a web URL over HSPA+ with a weak signal at work (damn building) so that tends to put some strain on the phone. Played a few rounds of candy crush and that was when I noticed the throttle kick in. Doesn't usually when i'm just doing 1 or the other, but both at the same time. This thermal throttle is awesome though. Still changing because having my phone stay a bit cool is a priority of mine. Now i've got core 2,3 off at 05 C and 1,2,3 throttle at 65. Still haven't noticed any performance issues but candy crush isn't all that intensive. Other game may have me reevaluate these thresholds.

Also, the core throttle is eco mode but better. When it reaches a certain temp you can tell it what cores to turn offline. so you can "eco" mode 1,2,and 3 based on temp. If you want exactly what eco mode does, tick cores 2,3 and set your temp threshold. once it hits that cores 2,3 will go offline.
[Nexus 4 Original Android Development] stab244:
Yeah I'll just say it's bad coding then. First time it's happened though in the 20 or so hours I dumped into that game. Whatever.
[Nexus 4 Original Android Development] italia0101:
+1 on that eco mode when the battery gets to a certain level option

Also was messing around with the simple gov settings.... Is the ramp threshold wrong in the app? It days lower = better performance, but when I put it lower it uses 128mhz a lot more. If i put it higher it's always on 360 or 600
[Nexus 4 Original Android Development] faux123:
many things are coming.. but takes time... I've added TONs of new cool features recently in both kernel and app... I have other stuff queued up too... patience daniel-son :angel:
[Nexus 4 Original Android Development] MandoH:
Patience is key!:D:thumbup:
[Nexus 4 Original Android Development] pikachukaki:
As you can see im not having any problem with temp...-100UV but im strugling to get 3+ SOT so i need the 40% and less auto enable eco mode...
[Nexus 4 Original Android Development] rmead01:
I see what you are saying now, basing it on batt %. i was confused because I was talking about temps. i'm UV -75 because once I hit 700mv for my lowest step the phone gets iffy.
[Nexus 4 Original Android Development] cocchiararo:
Turning eco mode on when battery reaches a certain % could be done with Tasker for now.

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 4 Original Android Development] italia0101:
How do you do that? Tasker confuses me so much
[Nexus 4 Original Android Development] pikachukaki:
The app someone posted a few pages back was not working properly...lags i was pressing options and it take me back to the homescreen...i remove it...

Yeah cause you said you enable this for making the phone works on dual core mode..cause of temp..you have high temp...i was wanting this to make the phone works dual core..to save battery..

[MENTION=3332811]faux123[/MENTION] btw..sorry for saying this again...eco mode could be sweet to be something like always on..and after a 20-30'' of high load...disable it...lets say im browsing something its pretty small load..i need 2 cores..but when i open a game...the kernel will see that the load is 100% for 2 cores for at least 30'' so it will say hey this is a game...eco mode...off!!!
[Nexus 4 Original Android Development] tlf55:
Does it work to use MPDecision with Intelli-thermal config ?
[Nexus 4 Original Android Development] strainhunter:
Yes, I think so. Because "MPDecision" has nothing to do with thermal controls. On stock "Thermald" controls that.

Gesendet von meinem Nexus⁴

@ <CarbonROM>+faux+franco.Kernel
[Nexus 4 Original Android Development] faux123:
yes, it work with mpdecision.
[Nexus 4 Original Android Development] kishke:
I've added a profile for tasker to turn on eco mode on chosen percentage(currently set to 40%).

Also I've added a small app I made with tasker that simply turns it on(will save the trouble of going into fauxclock)
[Nexus 4 Original Android Development] rmead01:
[MENTION=350276]faux[/MENTION]

Are you still using itellidemand for better batt? I've tried on numerous occasions to use intellidemand with the recommended settings from OP because i'm a batt nut. I just find that when I use games like candy crush the batt drops much faster than some alternatives. Wasn't sure if maybe there are other settings that I can adjust to try and counteract this drop? I don't play very intensive games, but I guess I play them like 20% of the phone usage.
[Nexus 4 Original Android Development] faux123:
you can bump the up threshold from 75 to like 95~98 percent if you want. See if that helps with candy crush... Candy crush is a very slow action game, but because of this, your screen on time will be huge... (which is the BIGGEST drain of any phone). You could also lower your brightness while playing candy crush...
[Nexus 4 Original Android Development] rmead01:
Thank you i'll try that. I only ever play it for like 20 minutes at a time, so it doesn't take up too much of my usage, but I can see the battery graph line just dropping. I'll try and raise the threshold and maybe i'll get better results. Thanks for the tip!
[Nexus 4 Original Android Development] italia0101:
How did you add that profile? By script?
[Nexus 4 Original Android Development] kishke:
I didn't understand your question, but I simply made a profile in tasker and then exported it as xml. You just need import it and change the threshold the way you want.

Edit: If your asking how to import, you have to copy the file to the sdcard/tasker/profiles folder, then in tasker click on the profiles tab, select import and then choose the profile
[Nexus 4 Original Android Development] rmead01:
hopefully my last question, but throwing performance out of the equation, which is going to be the best way to reduce heat strain when throttling occurs? reducing the freq on all cores, or turning off cores 2,3?
[Nexus 4 Original Android Development] italia0101:
I'm having an issue with this... It doesn't show up in tasker

Edit :Scratch that... Figured it out ... Ok fantastic I got a tasker for eco on and off depending in battery level
[Nexus 4 Original Android Development] Girn:
Will faux post up his own recommended thermal settings?
[Nexus 4 Original Android Development] kishke:
Actually u need to add an exit task for it turn turn eco off while your charging.

I'll give you a simple guide if you get in troubles I can upload a new profile.

1) copy the eco task.

2) long press on the profile and add an exit task

3) paste the eco task and change the number in the script from 1 to 0
[Nexus 4 Original Android Development] Jrbourque:
So two questions ..when flashing this kernel its recommended to disable mpdecision

Or is it already disabled by default? Also can't use Eco mode without faux app correct ?
[Nexus 4 Original Android Development] Hung0702:
Hey everyone, I posted a thread in general to help reduce the influx of gamma numbers this thread has seen. Post your settings there and try to comment on your setting so people can get a better idea of which fits their preferences best.
[Nexus 4 Original Android Development] feedhead:
Always quality work

I have purchase app in support of one of the android communities finest devs. Thanks for all you do sir.

I posted this with my 5 star review in the Play store but also wanted to get this here as well. One request I did not see brought up yet ... but this thread is moving fast... could the app's Screen Control section could have direct numerical entry as the sliders are not the easiest way to dial in the settings.

Your time and efforts are appreciated.
[Nexus 4 Original Android Development] idividebyzero:
For people trying to compare the colors with other phones its probably a better idea to calibrate your computer monitor and base it on that.

On Windows 7 open the control panel and type "calibrate" and choose calibrate colors, then follow the directions. Macs have an advanced calibration tool under color settings in Display.

This is a good wallpaper to test

Get a high res version and load it on your computer, if the gamma is too bright on the phone the saturated pink part in the middle where all the lines converge will be pale and the lines will be easily visible like it is with the messed up gamma, if the gamma is set correctly then the lines will bleed into the darker pink and seem like they fade away.
[Nexus 4 Original Android Development] n82k:
Buying faux app is a great investment. If you are in fact going to be using the,IMHO, best kernel in terms of battery life, smoothness, and Dev support/interaction for this device.
[Nexus 4 Original Android Development] faux123:
mpdecision is on by default to preserve "STOCK LIKE" behavior. My kernel is really just an enhanced version of stock kernel.

you can stop mpdecsion by using terminal emulator:

stop mpdecision

this will persist per powerup, you will need to do this every reboot unless you have an init.d script or using my app.

you can enable eco mode by activating intellidemand then use terminal emulator of your choice and do:

echo 1 > /sys/devices/system/cpu/cpufreq/intellidemand/echo_mode

this will only last per powerup. after reboot you will need to do this again. you can write an init.d script or use my app.

My app simply make all these tasks easier to manage with a GUI and allows users to have their settings persist over reboots.
[Nexus 4 Original Android Development] afbengochea:
Looks like it's still doing it after the binaries were updated. It happens whenever I go back into the app. Using the recent button and selecting it. Mainly if I have been using the phone on the web or tap a talk for a while
[Nexus 4 Original Android Development] afbengochea:
On Dec 10 aokp. With the recommended settings from your Google+
[Nexus 4 Original Android Development] jacklebott:
So I found out the script to set GPU max frequency and governor by init.d on my own, all that's left is control over Snake Charmer by init.d, I can't find it. Could you please tell me the command to toggle Snake Charmer? And, does setting the max frequency for cpu0 by init.d set the max frequency for all cpus if I have Snake Charmer on?
[Nexus 4 Original Android Development] faux123:
SnakeCharmer is not on by default. It is a kernel module.

To enable it, you will need to do:

su

insmod /system/lib/modules/cpufreq_limit.ko

once enabled,

you will need to do:

echo xxx > /sys/kernel/msm_cpufreq_limit/cpufreq_limit

xxx being a valid cpu frequency from cpu frequency table.

SnakeCharmer's limit applies to ALL cpus regardless of the individual core's own max limit.
[Nexus 4 Original Android Development] DJMartini:
Anyone know why my android os the would be more % use and above screen always?
[Nexus 4 Original Android Development] faux123:
Can you grab me a logcat right after it FC'ed or hit that "report" button.

Whenever you hit the "report" button, I get a copy of the log from Google directly :highfive: This will NOTIFY and HELP me at the same time to narrow down the bugs. I fixed most of my bugs from the "reports" sent in by my users.
[Nexus 4 Original Android Development] undercover:
Ive always dismissed report button as useless. Thanks for explaining.
[Nexus 4 Original Android Development] guapinoy:
Just sent one. Hope it helps. Great job!
[Nexus 4 Original Android Development] jacklebott:
Thanks, that worked perfectly! :D
[Nexus 4 Original Android Development] lookitzjohnny:
Update for my colors used a ipad mini side by side try to get colors close as possible. best grey scale i can get compared to ipadmini

Color adjustments

R:244

G:225

B:192

Gamma 1

R:2

G:1

B:0

Gamma 2

R:0

G:0

B:3

It may look different on your screen who knows, but looks pretty good on mine.
[Nexus 4 Original Android Development] bongostl:
I use the display test app to configure my gamma to get as close to 2.2 as possible, and ended up with these values :

11,11,31

0,0,0

Colors are noticeably better
[Nexus 4 Original Android Development] lookitzjohnny:
What you mean get as close as i can to 2.2? What do I compare ? Or how can I tell I'm close
[Nexus 4 Original Android Development] bongostl:
Use the app "display tester". Works great

I can only get to 1.8 on blue... The rest are 2.2
[Nexus 4 Original Android Development] lookitzjohnny:
I got you. But is it normal for the grey to havea green background. Can you post your setup the full setup not just your gamma thanks!
[Nexus 4 Original Android Development] italia0101:
Yea I'm really new to tasker, although I'm totally loving it.... figured out how to do the exit task on a Gps task so I'll do that now :)
[Nexus 4 Original Android Development] 0.0:
Very old post that I'm quoting. Trying to get a question answered. Is this true for the snake charmer feature?
[Nexus 4 Original Android Development] masterg0g0:
I think so yes
[Nexus 4 Original Android Development] faux123:
Kraits have minds of their own. Without snake charmer, they will not behave as told.
[Nexus 4 Original Android Development] tlf55:
So how do I make the core 234 crapped to the max freq selected ?

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] 0.0:
I believe you mean "capped" :p

Now to my understanding, and a user and faux seem to say I am correct in this. turn on snake charmer and it will cap all the cores
[Nexus 4 Original Android Development] 0.0:
[MENTION=3332811]faux123[/MENTION]: I checked the freq stat chart thing under the SOC tab, and it stated that one of the cores went to 1836 for 52min. I have snake charmer on, so why would it do that?

I rebooted my phone to reset it. now I will keep an eye on it
[Nexus 4 Original Android Development] tlf55:
Yeah that's what I meant .. Snake charmer doesn't work well the 1836 freq is still used by core 2 3 4 even after enabling snake charmer ..

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] italia0101:
I was getting this until I downclock to 1.3 then back to 1.5ghz with snake charmer enabled now it doesn't sure 1.8ghz o n any core
[Nexus 4 Original Android Development] masterg0g0:
I remember someone saying that the reading of cpuspy or soc can be miss guiding at times. But apparently i dont see my phone do this. Also every chip is unique ;)
[Nexus 4 Original Android Development] droidmeup:
Use cpu spy to check your core usage. This has been discussed months ago regarding some apps showing incorrectly, including faux app. Snake charmer is working as intended since it was released.

Get the app here.

http://xdaforums.com/showthread.php?t=1740622
[Nexus 4 Original Android Development] italia0101:
I think what they are talking about is the actual cpu stats included in faux clock... On the soc page
[Nexus 4 Original Android Development] droidmeup:
Thats what cpu spy does, it check cpu stats to see which frequency are used. I just remembered faux recommended that app to be used to check that snake charmer was working as intended. Although you cant view individual core stats on that app :(
[Nexus 4 Original Android Development] Shedao:
Ok, now you get the absolutely best combo of a potential bug and really insane user stupidness:

My N4 thought it would be funny to make a restart (the first in months) and as soon as it was booted again I started the faux clock app as usual to set the UV values (had NOT set them on boot). Unfortunately the values were in fact restored after the restart and so I undervolted way to much (200mV instead of 100mV). I realized this when my phone was already frozen :silly:. The problem is now that the phone can't boot anymore.

In short: Too much undervolting -> stuck on nexus logo

What I tried: flashing the awesome kernel cleaning script and then flash the stock reset kernel -> no success

Is there a possibility to avoid restoring a nandroid backup or wiping the phone?
[Nexus 4 Original Android Development] droidmeup:
Try to Dirty flash the rom.
[Nexus 4 Original Android Development] Shedao:
Is that possible with the factory image (using 4.2.2 stock)?
[Nexus 4 Original Android Development] DontPushButtons:
You can also try flashing this:

http://db.tt/jdQWzGEV

Should reset your app/kernel settings to defaults.
[Nexus 4 Original Android Development] droidmeup:
Ah ok, do you have any other kernels other than faux?
[Nexus 4 Original Android Development] DontPushButtons:
Can't believe I quoted myself and edited the quote.. Oh mornings..
[Nexus 4 Original Android Development] rmead01:
if you are on stock, there is a stock/rooted zip you could flash floating around somewhere
[Nexus 4 Original Android Development] kishke:
Easiest way, flash stock kernel, there's no uv there so phone will boot then simply wipe fauxclock data and you can flash his kernel again.
[Nexus 4 Original Android Development] italia0101:
Guys what's the terminal code for turning on snake charmer?
[Nexus 4 Original Android Development] aSquard:
Do I need both the APK and the profile? I currently only use Tasker to control my WiFi based on cell tower proximity, so I'm fairly new also

Edit: I grabbed just the profile for Tasker

Sent from Frost⁴ using XDA Premium
[Nexus 4 Original Android Development] ManOnTheMoon:
Congrats! You used approximately used 3.88% of your phone during that cycle. What an awesome kernel!!!!
[Nexus 4 Original Android Development] musashihatred:
Its cool. Im also using the latest beta.

162mhz min

1.25ghz max

Eco mode on

Snake charm on

Freq throt 70%

Core throt 80%

C2,C3 core throt

C2-C3 freq throt

:)

Mostly running single core.

-25mv no reboots

Heavy games (e.g. DH4) drains 1-2% every 10 mins. Pretty cool.

Latest beta.

Sent from my Nexus 4
[Nexus 4 Original Android Development] opensourcenoob:
Wireless Display not working using Faux Kernel

Hi guys, I just bought a Wireless DIsplay dongle to connect my phone to the dongle(Screen Beam Pro from Actiontec) and tried to connect to it while using my Nexus 4 using RootBox and Faux's Kernel version 016

It showed "connecting" and also at my TV displays "connecting", but then when in the TV displayed Succesfully connected, please wait a while to get your screen mirrored; it disconnect instantly, and I can see on my Nexus 4 that it's like "refreshed" and then ScreenBeam will be detected again but not displaying "connecting" anymore.

I come to know that the problem might coming from this kernel because I tried some other kernels and I can connect to my dongle perfectly and got my screen displayed on my TV. (I tried this using stock kernel, bajee11 kernel from RootBox, and Franco kernel Milestone3)

Please tell me how I can help to make wireless display up and running on Faux's kernel (If you do need logging, please tell me step by step how to do so because I am not a tech guy in any way)

Thank you

Regards,

Evan Hendra
[Nexus 4 Original Android Development] rmead01:
what governor are you running for cpu/gpu?

also, for simplicity purposes you don't really need to worry about core throttling. eco mode is doing that for you at all time. I think it's pretty nice to run quad core until I hit the threshold and then have it put me into eco mode.
[Nexus 4 Original Android Development] musashihatred:
intellidemand for CPU and ondemand [MENTION=1601421]600[/MENTION] for GPU :D

yup. its nice that way, but i went the reverse ways. want to run at the lowest core as possible, then hit quad when i play. and when it throttles, i'll hit freq throttle for C2 and C3 then turn it off if it gets hot. :D

i like it that way like S4's hotplugging. quad A7 plugs to quad A15. pretty cool :D
[Nexus 4 Original Android Development] rmead01:
Giving these a shot. I'm using simple instead of ondemand, supposed to be better for batt life. also running eco mode off so I can take advantage of quad core until it warms up. Have my freq throttle 0,1,2,3 at 60 and my core throttle 2,3 at 70

Wondering if I should reverse those and have "eco" mode enabled at 60 and then cap freq at 70 instead though.
[Nexus 4 Original Android Development] musashihatred:
:D increase your core up to 80 maybe? or 75?

xD thanks man. give me a reply if it works on you :D
[Nexus 4 Original Android Development] rmead01:
Well I have my core throttle early because for what I do i see no performance issues and it allows the device to stay that much cooler. Still trying to figure out what is best for batt/temps when the phone is still in use. 2 cores at max or 4 cores at throttle.
[Nexus 4 Original Android Development] musashihatred:
it really depends on your usage though.

since i got 2 cores at max all the time (While C0 always on and C1 conditional), i have up threshold set to 75 @ load, any cpu and multi core. down diff is set @ 3 and sampling rate at 50000 to 40000. 45000 is optimal.
[Nexus 4 Original Android Development] willybarca:
does it matter which core to throttle or switch off , because im throttling and setting offline limit for core 0 and 1 since they have been used more than the other two and they are abit worn out compare to the core 3 and 4... but does this affect performance, because I heard core 3 and 4 are not as robust as the first two and only kick in when there is need, any idea