yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] romeoliny:
My colors stay for a while but after screen shuts off for a bit only the gamma sticks and the colors shift. ( this issue is intermittent but will happen eventually ) After I re open or go back to FauxClock and press the power button again the programmed colors will return.

I have the latest addition of SuperSU so that's not the issue.

Using beta 9 but this problem I've experienced with all the betas. A lot of others who are using SuperSU I've noticed are also reporting the problem.

Easiest way to detect this issue is to drastically change your colors so you can spot the change. I how this helps. Not sure if there is a log that I can provide to help in this instance and if so please tell me how to pull it and I shall.

Thanks Rome
[Nexus 4 Original Android Development] jacklebott:
Pretty sure that's already implemented
[Nexus 4 Original Android Development] inferno17x:
Hi, do you have any other apps besides FauxClock which can alter the screen color? eg. Trickster Mod

I have experienced this before if I set the screen color in FauxClock, Trickster Mod will register the same color settings and if you apply anything using Trickster Mod it will stay with the color settings set in Trickster Mod even though you change the color settings again in FauxClock.

So I removed Trickster Mod as not to create any conflict with my settings in FauxClock.

Hope this help.
[Nexus 4 Original Android Development] SeaSeeC:
I think he added them in one of his newest betas, I remember him adding a new table for the "Faster" bin type.
[Nexus 4 Original Android Development] evonc:
003 beta11 is up in case no one noticed :P
[Nexus 4 Original Android Development] Reatret:
What does beta 11 bring?

Also faux could you incorporate an upgrade to screen sensitivity in this kernel? :)
[Nexus 4 Original Android Development] jacklebott:
Another beta skipped... Does that mean beta11 is another super awesome one? Perhaps including thermal throttle fixes? Hmm...

I do see he included thermald.conf in his kernel zip, so here's hoping!
[Nexus 4 Original Android Development] Traxex_:
+1
[Nexus 4 Original Android Development] aSquard:
I have the same problem that Rome has (and I'm not using another colour control app). My colours don't stick unless Faux's app is running (beta 8) - moving to beta 11 now

Enlightened with Paranoid Android on the Nexus 4 and XDA Premium
[Nexus 4 Original Android Development] evonc:
Yeah I believe he had mentioned that he will be going ahead with thermal changes tonight if the s2w screen lock doesn't bring any more problems.

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
Beta 11 is out!

Check details here:

http://xdaforums.com/showpost.php?p=34502836&postcount=3
[Nexus 4 Original Android Development] jacklebott:
I've noticed that after my phone gets hot enough (battery 40C or higher), no matter what temperatures I set in the thermald.conf file, the CPU keeps switching between 1134MHz and my max frequency (v3b11). Before trying to manually edit thermald.conf, I figured it was the new CPU temp parameters you set, but editing those doesn't seem to actually change anything. Is this intentional?

I stand corrected. Raising the temp thresholds doesn't help, but setting them back to what they were before did

I've also noticed in the last few betas, Intellidemand often won't let me change "lmf_active_max_freq" by script (whether in init.d or a manual .sh script)

The last issue that's still present that I can think of is that the max frequency lowers itself permanently under high stress situations (only encountered so far using Intellidemand)
[Nexus 4 Original Android Development] faux123:
If Beta 11 is fine. it will be released as official 003 version.

new stuff will be added to 004 betas
[Nexus 4 Original Android Development] SeaSeeC:
This kernel and DS Battery Saver works wonders.

Sent via my Nexus⁴
[Nexus 4 Original Android Development] samwebbo1990:
Does anybody know what this gtalk async conn wake lock is? I've benn researching and people seem to think its Google talk or location updates but I've signed out of Google talk and disabled the app and all location settings are turned off and I'm still getting it :/ thanks in advance :)
[Nexus 4 Original Android Development] kwerdenker:
If I remeber this correctly, the Play Store uses the Gtalk channel as a backend for the communication and synchronisation. Your wakelocks might come from that.
[Nexus 4 Original Android Development] aypro:
I have a problem with my settings not sticking, i'm using kernel 003b11 and the FauxClock app.

Each time i reboot the phone, i wait for the app to get root access (SuperSU), launch the app, and find that i have the default settings, "ondemand" governor, S2W disabled and others. Even without rebooting the phone "S2W" is not working even if the option is ON.

I tried clearing data for the app, reflashing kernel, reset kernel but the problem is still there.
[Nexus 4 Original Android Development] DforDesign:
It started to work for me after turning it on and rebooting.
[Nexus 4 Original Android Development] richteralan:
That's what I'm getting all stock.
[Nexus 4 Original Android Development] Letitflow:
With Jellytime v2 on stock kernel im getting 18k+ all the time.
[Nexus 4 Original Android Development] brianbgrp:
I just got 176xx on stock ota kernel/ROM rooted set at 384/1456 thru Trinity tool box. Updated antutu.

Sent from my Nexus 4
[Nexus 4 Original Android Development] richteralan:
I see it's the CPU floating points score that get improved....wonder why.

All my other scores are very close to you.
[Nexus 4 Original Android Development] P0MM3S:
yeah i used the new antutu.. with faux 005 i'm getting around 16000, with shakys 18000, so there IS an improvement

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] danyshotbang:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!

Again the screen sensitivity issue on the phone (its an issue without nobody tellin me its not!) how can it be fixed is it software related (ROM, Kernel) or is it hardware related! i want u pleas to answer me faux cuz u are the one that nows the most.

and i know that everyone that knows about this issue wants to!
[Nexus 4 Original Android Development] mastibeta:
Apparently your research skills are on par with your grammar skills. (guessing english is your second language) The "sensitivity issue" is really a non factor. It may show as an issue in a synthetic test, but day to day usage has shown no issue at all for me. Perhaps those with a noticable issue recieved bad hardware?
[Nexus 4 Original Android Development] faux123:
It could be any combination... no one knows exactly.. The touchscreen input is a combination of Hardware, Firmware (100% proprietary, not hackable) and kernel driver. At this moment it is difficult to say where the "fault" is at. If it is a hardware issue, then a replacement is the ONLY solution. If it is a firmware issue, then we will need to wait for Google/LG to update the newer firmware in the subsequent ROM release. The kernel driver is just a bridge between hardware and firmware.. I highly doubt the issue is @ the kernel driver. I will look into further but with ABSOLUTELY no guarantee or ETA of anything..
[Nexus 4 Original Android Development] ctfrommn:
Beta 005 not deep sleeping? Or just me? I have tried both intellidemand and ondemand and neither seem to shut off the cores.
[Nexus 4 Original Android Development] sarni84:
Mine is deep sleeping on intellidemand .....84% 005version
[Nexus 4 Original Android Development] Guitarfreak26:
Is there any reason why the min clock keeps going to 702? Is it to do with the amount of cores running with intellidemand?
[Nexus 4 Original Android Development] crr127:
I was having similar issues with 005 not going into deep sleep. That was fixed by re flashing the kernel after wiping the "Cache" and "dalvik cache". It then just started working...
[Nexus 4 Original Android Development] spadie:
i flash your kernel, i go to benchmark, and device reboot...

now i cant trun ON..... RED Light turn on/off all time.. and dont boot.... :S

any help????

i use beta 005
[Nexus 4 Original Android Development] faux123:
be careful, not every phone can be overclocked...

read here to recover from it...

http://xdaforums.com/showpost.php?p=34585684&postcount=81

Just a word of caution. ONLY overclock when you accept the risk for it :(
[Nexus 4 Original Android Development] spadie:
i cant get 4º step :S

---------- Post added at 11:57 PM ---------- Previous post was at 11:52 PM ----------

i do all steps, but when i reboot from recovery, it look red too ;S
[Nexus 4 Original Android Development] elliot.newnham:
Can you try

1. hold vol down

2. hold power button.

if you get into fastboot mode, use the nexus 4 toolkit v1.30 in this forum and flash Stock OS.

Next time, don't flash beta software unless you know EXACTLY what you're doing.
[Nexus 4 Original Android Development] estallings15:
Let your phone charge a while and try again.
[Nexus 4 Original Android Development] spadie:
i restore Google's factory IMG, and lock the bootloader.. and i cant boot... **** RED LED....

I can enter into recovery, bootloader... but i cant boot

---------- Post added at 12:18 AM ---------- Previous post was at 12:10 AM ----------

I can be in the bootloader an hour, but I disconnect the usb and device power off, i only can using phone whit cable... maybe batery broken?
[Nexus 4 Original Android Development] elliot.newnham:
I think a few other people are in this boat...

The general consensus is your phone is hard-bricked and your out of luck.

Warning: Please don't install kernals/firmware unless you know EXACTLY what is going on!
[Nexus 4 Original Android Development] spadie:
omg... great...

and warranty dont cover this... true? hahah **** off
[Nexus 4 Original Android Development] aypro:
I tried that, it wasn't working and the option was OFF
[Nexus 4 Original Android Development] jhericurls:
I seem to have lost the ability to control the GPU in the app.

Its stuck at 487mhz. Is there anyway to manually switch it to 200mhz
[Nexus 4 Original Android Development] jacklebott:
echo 200000000 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk

If you put that in an init.d script, it'll auto-set on boot as well
[Nexus 4 Original Android Development] teh_lorax:
I'm still occasionally losing all settings for the Faux app. Just happened this morning. And I'm using SuperSU. Not sure what other details I can report to be helpful though.
[Nexus 4 Original Android Development] ziggy34:
Flashed the beta 11 and got the non response touch screen, first time I ever had it. Reboot and it worked if I unlocked the phone before the screen shut off. Once the screen shut off, the screen would not respond.

What worked for me to fix it was rebooting and unlocking right away. Go in to the app and turn off sweep2wake. Exit the app,screen off, turn on screen and screen worked. Turn back on sweep2wake and now all is fine. Sweep2wake works and screen responds after screen off and deep sleep.

Was not in a place to get a log.
[Nexus 4 Original Android Development] nateysmith:
Which app allows for disabling/enabling sweep2wake?
[Nexus 4 Original Android Development] laverdure#1:
Faux app from playstore. Well worth the small price.
[Nexus 4 Original Android Development] DforDesign:
003b11 is the first and only kernel that fixes throttling for me. Incredible temperatures compared to stock:

Spoiler content hidden.
[Nexus 4 Original Android Development] nateysmith:
Thanks. I have purchased the app but I completely missed that option.
[Nexus 4 Original Android Development] tr1gg3r.man:
So far I haven't rooted my new Nexus 4 as of yet, but when I do... I plan to Faux it right away =] used your Kernel on my old HTC Sensation, glad you decided: "Uht-oh, better get Mako!"
[Nexus 4 Original Android Development] italia0101:
These looks decent indeed ! Did it throttle at all ?
[Nexus 4 Original Android Development] ZeroDefined:
I flashed 003b11 and phone would not boot up and was stuck at the Nexus boot logo. Tried re-flashing 003b11, an earlier beta as well as the reset kernal and none of that seemed to work. Ultimately had to do a factory reset :(

Never had an issue with any other betas. Running Faux's recommended settings for battery and UV to -175 on the Stock Rom

Made a Nandroid, so I'm going to try restoring and flashing a different kernal to see if that does anything. Mainly b/c I really don't feel like setting up all my apps and preferences at work. Will report back
[Nexus 4 Original Android Development] phewizzo:
B11 booted fine for me.
[Nexus 4 Original Android Development] DforDesign:
No, not even for a second:D I used -100UV but now I dont use uv at all and after 30min it still runs fine without throttling
[Nexus 4 Original Android Development] italia0101:
That is sweet ! May finally be time to dive in on this kernel

Also do you know the actually changes faux made to the thermal file?
[Nexus 4 Original Android Development] ZeroDefined:
No Luck with a different kernal (tried Franco's r23 fyi) guess I'm stuck restoring the phone... boo
[Nexus 4 Original Android Development] superleeds27:
Does anyone have a link to the post where Faux has posted his recommended settings?

Would be helpful!
[Nexus 4 Original Android Development] opethrocks:
You should try flashing the reset kernel then re-download faux's latest beta and re-flash. It might have been a bad download
[Nexus 4 Original Android Development] ZeroDefined:
The Search bar isn't just for looks...
[Nexus 4 Original Android Development] Higadeb:
Don't want to add clutter to this thread, but simply thanking Faux's post didn't seem enough! This kernel & the Faux app are both amazing (esp the gamma control)! Many thanks for all the hard work :D
[Nexus 4 Original Android Development] superleeds27:
I did search, it knowing what to search for and filtering out the pointless posts!
[Nexus 4 Original Android Development] faux123:
Recommended Settings is now stored in 2nd post due to popular demands!!!! Go to 2nd post for all the gory details :D Have fun!
[Nexus 4 Original Android Development] :
Fresh wipe off AOKP's first official build, with Beta03 build 11... getting a lockup on reboot if I dont unlock when the screen first turns on after boot.... if i let the screen sleep after boot... then turn it on... screen is unresponsive to touch.... but if i unlock right away, its fine until the next reboot....
[Nexus 4 Original Android Development] fnf:
Thanks. I was really looking for improvements in thermal throttling. Unfortunately data connection is still spotty for me in beta 11. logcat and dmesg showed nothing out of order but the phone struggles to transmit under strong signal (-69dB).

Edit: Need further testing. I flashed back 002m and the speed is still slow. I will use beta 11 for a while to see if it is different.
[Nexus 4 Original Android Development] Jrbourque:
Beta 11 running good for me. But have a question with the app. Randomly i see a message pop up granting root for a shell in faux app. Is this normal to see it pop up a decent amount?
[Nexus 4 Original Android Development] drdrewdown:
yea it's normal. what most people do is disable the toast notification on per app basis. this can be done in supersu app
[Nexus 4 Original Android Development] Higadeb:
It happens to me too, I just silenced the toasts in SuperSU. Would be nice to have some clarification if this is correct behaviour though :)

Edit: Too slow.... ;)
[Nexus 4 Original Android Development] ziggy34:
Had the same problem with beta 11, I posted a page or two ago. What worked for me was using faux's app I turned off sweep2wake, exited app, let phone sleep, when I turned it back n all was fine. I then turned sweep2wake back on and all was fine.
[Nexus 4 Original Android Development] superleeds27:
Not too sure about colours. Think ill stick to stock default. Too much of a perfectionist :/
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

For the settings I use Faux123 Kernel Enhancement Project from the Play Store.

But how I can set mpdecision on / off with your tool?

Thorsten.
[Nexus 4 Original Android Development] drms12:
The only problem with this kernel is the suspend_backoff kernel wakelock that refuses to go away.

The phone consumes 27% of battery after 7 hours of sleeping without screen and data&wifi off! From 100% to 73%!!

suspend_backoff wake the phone for hours!

Am I the only one with this problem ??
[Nexus 4 Original Android Development] linelock:
Turn off sleep2wake.
[Nexus 4 Original Android Development] drms12:
Maybe it is the cause. But turning off S2W isn't a real solution.

It is one of the best things of this phone.
[Nexus 4 Original Android Development] 3bs11:
It's in his app on the main page. Are you on one of the newer betas?
[Nexus 4 Original Android Development] italia0101:
Anyone else got any success stories for the thermal problems,?
[Nexus 4 Original Android Development] jhericurls:
You have to live with it then. This initial version is still considered as experimental. Show-p is releasing a new version soon.
[Nexus 4 Original Android Development] faux123:
if you come from bricked or another kernel where mpdecision is PERMANENTLY disabled, you will need to restore it first. Check with showp's thread (or the previous custom kernel thread you used and ask the dev to restore to pristine stock conditions).
[Nexus 4 Original Android Development] ExMM:
Faux your version 3beta8 is doing miracles. Its better than ever:

max clock: 1.026 ghz

min clock: 384 mhz

Intellidemand

mpdecision: off

eco mode: on

snake charmer: on

UV: -212.5 mv

GPU clock: 400mhz

I/O scheduler: deadline

Readahead size: 2048

TCP: westwood

Vibration: 50%

Wifi on most of the time, data always off with moderate usage, rom PARANOID Android. ONLY 48%...

I never spent my money better in the google play store.

Keep up the good work!
[Nexus 4 Original Android Development] LarsenB:
Are these settings supposed to stick after a reboot?? They aren't for me.
[Nexus 4 Original Android Development] ExMM:
They stick for me. But I had problem with the rom,so I had to wipe everything out and flash the ROM and the beta8 again.

I'm downloading the Beta11 now..
[Nexus 4 Original Android Development] drms12:
Probably.

It just strange nobody else report about that battery drain wakelock.

Showp says that this shouldn't be such a drainer.

If someone else get that suspend_backoff wakelock also with S2W enabled I'd like if he can confirm here.
[Nexus 4 Original Android Development] faux123:
Switch from superuser to superSU
[Nexus 4 Original Android Development] romeoliny:
Using SuperSU.

My general settings stick such as clock speeds but the color profiles don't initialize until after the power button is pressed or the screen turns off. Is there any way to force them to initialize by boot alone? (Colors / Gamma)
[Nexus 4 Original Android Development] Reatret:
I couldn't use your app at all without super SU. I think you should include it in the OP
[Nexus 4 Original Android Development] faux123:
FAQ is posted in the 4th post!

http://xdaforums.com/showpost.php?p=34502852&postcount=4
[Nexus 4 Original Android Development] faux123:
No, because the design of the driver is the issue. App is ALWAYS run after kernel initialization, so by the time app gets the chance to change it, it's already too late!
[Nexus 4 Original Android Development] Locksmith81:
You have s set on boot?
[Nexus 4 Original Android Development] Ace42:
Faux, will you consider ROW I/O scheduler in future releases?
[Nexus 4 Original Android Development] faux123:
I had it since day 1. I just didn't release it due to issues I had with it. I will revisit it some times later. Why not use fiops instead.
[Nexus 4 Original Android Development] italia0101:
Faux what exactly did ya tweak in thermal ?
[Nexus 4 Original Android Development] Ace42:
I use Fiops but, I figured qualcomm's would be better since it's their chip.
[Nexus 4 Original Android Development] whittikins:
Then you should use Qualcomm's wonderful kernel features like mpdecision... :)
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

@ faux,

in your 2nd post you have change the I/O scheduler from deadline to fiops.

How about the difference between this both I/O schedulers and which one is the best for battery efficiency?

Thorsten.

PS:

Thanks for the information about the mpdecision on/off, now it works if i come from the stock kernel. :good:
[Nexus 4 Original Android Development] faux123:
it's all in my thermald.conf file

I just adjusted the values to my liking and removed GPU throttling
[Nexus 4 Original Android Development] Ace42:
That's true...I retract my request faux, qual can keep their implementations to themselves. :)
[Nexus 4 Original Android Development] faux123:
FIOPS is designed from ground up for Flash based devices like cellphones and tablets.

CFQ, Deadline, even BFQ were all designed for harddrives and they were great at hiding the harddrive latencies but, unfortunately, they aren't good for Flash based devices.

For my deadline scheduler, I've tweaked it to work better with Flash devices, I essentially crippled deadline

by preferring read over write

and removed the queuing since we don't have spin latency to hide (sounds familiar ain't it? Yes, my tweaked "deadline" is essentially the same as ROW IO scheduler, that's why I am not too hot about ROW scheduler from Qualcomm because the concept isn't new :p ).
[Nexus 4 Original Android Development] Redmed427:
I'm noticing slightly less battery life with the 11 than 9. Will continue testing
[Nexus 4 Original Android Development] faux123:
it could be because I disabled "standalone" powercollapse (Qualcomm SOC's sleep states) for EHCI connections.

I want to release 003 mainline (matter of fact, I am running it right now before I officially announce it tonight).

I will continue my EHCI testing on 004 betas. 003 mainline will NOT have any EHCI patches from the beta.
[Nexus 4 Original Android Development] arvonn:
lovin' 003 beta 11..

I went from 8 to 11, but i'm loving 11. see attachment. light usage, but 1.5 hrs screen on, almost 1 day 8 hrs and ~40percent battery left. The one big drop half way in is the switch from beta 8 to beta 11.. overall quite happy with the last couple kernels.

This is providing basically double the battery life of stock kernel, for me, at this point. Stock Rom, mako 003b11, undervolted -150 mv, and intellidemand with eco mode turned off.
[Nexus 4 Original Android Development] aSquard:
This are my results with Beta11 and eco mode off (I was curious of my own personal usage with eco on/off)

Loving it so far - I'll run with eco mode on tomorrow and see what the battery life looks like

Enlightened with Paranoid Android on the Nexus 4 and XDA Premium
[Nexus 4 Original Android Development] Peter1856:
I can confirm that... from beta 8 (actually starting with beta 5) I got worse battery life (especially on standby) but now on beta 11 everything is back to normal (4,5h to 5h screen on time). Not sure why I had the higher drain with the earlier betas though, as it didn't sound like a widespread issue here in the thread...
[Nexus 4 Original Android Development] Ace42:
Woah you guys are getting better battery with quad than Eco mode?
[Nexus 4 Original Android Development] ftarules:
After reading the last three pages I'm a bit confused. Should Eco mode be ON or OFF when using Intellidemand?
[Nexus 4 Original Android Development] faux123:
Eco On for battery

Eco Off for performance

:D
[Nexus 4 Original Android Development] Ace42:
Eco disables the last two cores. However now users are stating they get good battery even with it off :what:
[Nexus 4 Original Android Development] Reatret:
I have no idea how people are getting 5hrs screen on unless they have eco :rolleyes:
[Nexus 4 Original Android Development] expl0it4:
Guess I'm getting the best of both worlds. Eco off 1.35ghz ondemand fiops -100uv s2w with 5hrs screen on location access on gnow off. :thumbup:

---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------

It's very possible. I refuse to cripple my device down to two cores and I'm breaking 5hrs.