yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] faux123:
no, qualcomm will NEVER reveal / release their secure TZ binaries. It's just the way it is... many other phones have the same limitations such as TI OMAP, ARM Mali and nVidia ULPGeforce. GPU is pretty proprietary and lots of trade secrets in them. It's just the way it is for Android/Linux in general. I might add more capabilities when I have more time. Right now you can control between Overclock and stock frequencies with my kernel + app combination.
[Nexus 4 Original Android Development] Carter07:
I hope so! I'd like to see (if possible):

1) possibility to lock gpu frequency to a lower value (ex 128mhz)

2) possibility to undervolt gpu with your app

Here I read:

http://xdaforums.com/showpost.php?p=33919920&postcount=228

Adreno320 GPU Freqs, 27,128,200,325,400Mhz

Adreno320 lowest vdd 900, highest 1200
[Nexus 4 Original Android Development] faux123:
I could allow lower freq operations. voltage controlled by microkernel, so I can't touch it.
[Nexus 4 Original Android Development] ctfrommn:
What is the reason for choosing 700mhz for the lowest freq on intellidemand over 328?
[Nexus 4 Original Android Development] whittikins:
Also curious about this.
[Nexus 4 Original Android Development] linelock:
This was answered earlier.
[Nexus 4 Original Android Development] cmikeh2:
In order to maintain a minimum level of performance, Faux123 has the minimum set for 700 mhz when only one core is active. If you watch the behavior of the cores, when a second core comes online the 384 mhz frequency becomes enabled.
[Nexus 4 Original Android Development] ctfrommn:
I saw and understood that answer. I was wondering why said minimum performance lock was set at 702 and not 384. Is this the lowest a minimum lock can be set at or 384 was too low to wake properly?

---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------

I get that, but the stock kernel runs at 384 even when 1 core is active. Was just wondering the reasoning for a higher than stock option is all.
[Nexus 4 Original Android Development] FallingEdge:
So in something like no-frills CPU, the minimum should be 700 and when using intellidemand, it will auto drop down to 384 when more than one core is being used regardless of what the minimum is set?
[Nexus 4 Original Android Development] ctfrommn:
I still set the minimum to 384. I think if you set it to 702 it will never fall below that frequency.
[Nexus 4 Original Android Development] mastibeta:
this ^^ set to whatever you want the multi core low to be. It will maintain 700 for single core.
[Nexus 4 Original Android Development] faux123:
You guys are inquisitive bunch aren't ya...

The reason for ID governor to run @ 700 MHz while single core is due to ID governor's design. mpdecision is very chaotic and aggressive hotplugging cpu on/off all the time, while ID governor is much more orderly and less aggressive.

mpdecision will allow 384 min because when it needs power, it will very aggressively ramp the frequencies and cores which actually uses more power than it needs (overreaction). ID governor, on the other hand, will carefully look at the load and running averages to determine whether or not higher frequencies and additional cores are required for the current operations. Because ID governor reacts more orderly and less aggressive, it needs some minimum performance guarantee so when instantaneous load spikes occurs, it has enough oomph to take care of it otherwise it would struggle and lag which is not what we want ;)

Hope the current geek talk series are helpful to you guys ;)
[Nexus 4 Original Android Development] ctfrommn:
Hahaha....thanks Faux. Yea, Im a natural researcher/learner. I cant help it. I'll quit bugging now. :)
[Nexus 4 Original Android Development] maddoggin:
Awesome. Thanks man!
[Nexus 4 Original Android Development] Globespy:
Already did that.... only seen this increase in Android OS use since updating to beta 5 02.... no other changes on my phone, so it is plausible that it is the kernel.... of course it could be a random evil entity that entered my phone? ;)
[Nexus 4 Original Android Development] faux123:
it's probably the increased HSIC wakelock. There's no choice. Either data loss or slightly increase in wakelock, I chose the latter.
[Nexus 4 Original Android Development] Stryder5:
I also noticed Android OS usage increased significantly in 005 b2, along with higher battery drain. Any chance it is the kernel causing this?

EDIT: Just saw Faux post above mine.

I also had 2 or 3 SOD's today, but didn't get a chance to grab a log (S2W disabled) since I needed to use my phone immediately. I'll try to log it tomorrow or so.
[Nexus 4 Original Android Development] aSquard:
Yeah, like the others said -100mV for starters is good, just don't set at boot until you find what's stable under load. 005beta01 was stable for me at -175mV but it doesn't hold on 005beta02 - I'm currently at -162.5mV ('Fast' binned chip)

Enlightened with Paranoid Android on the Nexus 4 and XDA Premium
[Nexus 4 Original Android Development] Globespy:
Fair enough mate..... I'm sure you will find the perfect mix. Also when Google release an updated base band radio, then the data drop issue will be gone and then you can eliminate the wakelock.

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

I guess my phone must be a strong performer as I'm at -225 across the board on beta 5 002 for a day with zero reboots or sod's.
[Nexus 4 Original Android Development] romeoliny:
Hey everyone!

PGM from bponury just came out with his working paid slide2wake app for the Nexus 4. Works perfectly on enhanced stock kernel. On the play store.

I love it with the enhanced stock kernel kernel faux put out with the wake / data fixes. I hope you enjoy. Paul/Faux you should try it its awesome!

Later,

Rome
[Nexus 4 Original Android Development] ftarules:
How do you find out if your CPU is fast or faster binned?
[Nexus 4 Original Android Development] aSquard:
Ha ha, I don't like you :p - That's awesome though! I'm sure your battery life is stellar!! :good:

Check here: http://xdaforums.com/showpost.php?p=35566840&postcount=1
[Nexus 4 Original Android Development] MontAlbert:
Pgm module Doesn't work on latest beta.

*that was meant to be a reply to Rome above..
[Nexus 4 Original Android Development] romeoliny:
Yeah I just tried it on Faux's kernels. That sucks because I lost data on the last enhanced stock kernel by Faux. Kind of unfortunate. Can anyone confirm no data drops on any of the enhanced kernels from Faux?

Thanks,

Rome
[Nexus 4 Original Android Development] faux123:
PGM doesn't work because PGM is listening on the input events. Recent patch from kernel.org has consolidated the input events into 1 packet instead of multiple packets (this reduce the computational overhead and reduce the locks in the kernel which improve overall performance for inputs). The author of PGM needs to update his software to deal with multi or single packet input events (all newer kernels have this optimization so it's better for the author to fix it anyways).
[Nexus 4 Original Android Development] romeoliny:
Thanks Faux,

I tried enhanced stock r3 with data fix but still having drops unfortunately. Any tricks up your sleeve with another enhanced stock version?

Following your twitter and thanks for all your hard work! You're an amazing dev!
[Nexus 4 Original Android Development] expl0it4:
The exact kernel release version isn't shown and I've forgotten which one I had flashed. Can faux or anybody else tell me what release this is? I've had great results but want to update my rom + kernel to latest but need to know current if I want to revert.
[Nexus 4 Original Android Development] droidmeup:
I think that's the 3m or 3m_r2 or could be 3b11.
[Nexus 4 Original Android Development] resynx:
Look at the last downloaded kernel on your sd card xD
[Nexus 4 Original Android Development] masterg0g0:
Hi faux,

How can we know what our chip quality? I know you had a kernel output for nexus 7. There was a binned command I tried but it seemed to be not working.
[Nexus 4 Original Android Development] Sucalakafufu:
not working for me too. does this command have to be run on stock?
[Nexus 4 Original Android Development] elzafir:
CPU binning? Try this thread http://xdaforums.com/showthread.php?t=2052496

1. Download Terminal Emulator

2. Run it, type 'su'. Grant root access.

3. Reboot

4. Type 'dmesg | grep PVS'.

Question:

The FauxClock app, can it be used with other non-faux kernels? Should i restore default values or even uninstall it before i flash other kernels?
[Nexus 4 Original Android Development] Sucalakafufu:
doesn't work. that's what i already tried

to answer your question: yes it can be used on other kernels. i would reset uv at least. so as not to create a bootloop
[Nexus 4 Original Android Development] sryche:
i think u re on 003b11, cause your kernel release 03 jan. and that date faux release 003b11. u can check there http://faux.androidro.ms/mako/beta/
[Nexus 4 Original Android Development] MontAlbert:
Reboot again. I had to reboot a couple times to get mine to work for some reason. My output was 1 which I assume is slow or nominal. Whatevs, I can still uc to 125mv
[Nexus 4 Original Android Development] basshamster:
005b2 quite good here. No data drop since yesterday morning and battery good as usual! :)
[Nexus 4 Original Android Development] Bierfreund:
Do I have to enable Sweep2wake? If it's necessary, how can I enable it (I don't have the paid Faux App installed).

I tried the latest stable and the latest beta version and by default Sweep2Wake does not work for me.

I'm using latest xylon nightly as ROM.
[Nexus 4 Original Android Development] jhericurls:
Sweep2wake is broken, I recommend you don't enable it.
[Nexus 4 Original Android Development] nic85:
I have aokp + 04m + settings for battery life as first post. but I think there is too much drain.. offline mode.
[Nexus 4 Original Android Development] Bierfreund:
Bad News...

Touch Control App from Google Play also does not work...

I think I'll switch to another kernel and use Touch Control App until Sweep2wake is fixed.
[Nexus 4 Original Android Development] justbabu:
Sweep2wake works perfectly for me on Kernel 5 Beta 2.
[Nexus 4 Original Android Development] Stryder5:
Currently works with stock kernel and Faux's enhanced stock kernel. Hopefully the dev will make it compatible with other kernels.

It will work for some people, but is not fixed yet. Showp is supposed to release version 2 that has it working properly.
[Nexus 4 Original Android Development] Bierfreund:
How can I enable it, to test if it's OK for me. Do I need the paid faux App?
[Nexus 4 Original Android Development] jhericurls:
echo "1" > /sys/android_touch/sweep2wake
[Nexus 4 Original Android Development] Stryder5:
You can also use the Trickstermod app from the play store to enable it.
[Nexus 4 Original Android Development] nateysmith:
Has Faux commented on whether he will add what needs to be done for his kernel to be touch control compatible?

Also bponury said the following about faux's earlier comments as to making the changes to the app to be more efficient "I will take a look at this today The other thing would be on the developer side (disable CONFIG_MODVERSIONS)."
[Nexus 4 Original Android Development] Jur1nator:
Again new app update

And beta 5.03 is out!! :)
[Nexus 4 Original Android Development] superleeds27:
Flashed 005 Open Beta 3

is the build date correct?

beets- #47

Tue 15 Jan 20:40 CST 2013
[Nexus 4 Original Android Development] faux123:
Yes, I am always a few versions ahead of my releases :D

and beets is my buildbot that someone has kindly donated for me to use.
[Nexus 4 Original Android Development] superleeds27:
:)

Was just checking. Making sure it had flashed correctly!
[Nexus 4 Original Android Development] 0.0:
I think you have done it faux! The latest app update fixed the startup time. The app opens fast, even after I open a few apps and go back into it again :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
not sure why I need to disable CONFIG_MODVERSIONS?

STOCK, CM and my version all has https://github.com/CyanogenMod/lge-kernel-mako/blob/jellybean/arch/arm/configs/mako_defconfig#L36 set to Y. So it is NOT CONFIG_MODVERSIONS issue.

I wish the developer would just listen to what I

said

. It is the input packet optimization that's killing his software. He NEEDS to fix his module to be compatible with these new changes.

https://github.com/faux123/mako/commit/8f3fe225cdfed1a4f18238f762170e0a68515599

Once his module is fixed to be compatible with above changes (which will be in all the newer Linux kernels, so he needs to do it anyways), his software will work :angel:
[Nexus 4 Original Android Development] romeoliny:
Hey Paul,

Think you can use the new data fix on an enhanced stock kernel? Thanks for everything you do!

Rome
[Nexus 4 Original Android Development] Harsh:
Hi, faux its not that commit which is not letting his app work. I had a talk with him, and it does not work even on my kernel. I have not applied those specific input optimization. Its definitely something else, he will look at changes on github and see if it can be solved.
[Nexus 4 Original Android Development] remydlc:
From Faux own G+ account, i recommend you follow him:

Paul Reioux 1:01 PM - Public

https://play.google.com/store/apps/details?id=com.teamkang.fauxclock

FauxClock build 55 is out!

Cleaned up unnecessary background services

more performance tune-up!

I highly recommend you do a REBOOT after updating the app (so the older services can die)

Nexus kernel 005 Open Beta 3 is out!

Added emmc corruption patch from CAF

added qseecom performance boost from CAF (qseecom is qualcomm's proprietary firmware engine running in ARM TrustZones :()

Backported Linux 3.8+ file system performance patch

https://lkml.org/lkml/2013/1/15/14

http://faux.androidro.ms/mako/beta/mako-jb-kernel-005b03.zip

Oh, and 004m release 2 is also out!

Finally fixed all data issues :p

http://faux.androidro.ms/mako/jb42/mako-jb-kernel-004m_r2.zip
[Nexus 4 Original Android Development] faux123:
I am not sure what else is broken on N4. But on Galaxy Nexus, the input optimization patch was the breaking point for PGM. It was working fine until I added it to my Galaxy Nexus kernel, so I assumed that similar coding would be used for N4 as well, but it sounded like N4 has more issues than Galaxy Nexus it seems.
[Nexus 4 Original Android Development] gr3if:
Hi I updated your APP and just lost all my settings....

A bit disapointing since it happends all time updating. Can it be fixed or is it Wirkung AS designed?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Globespy:
I moved the dis dial to -250 across all frequencies (although the lower frequencies seem to be unable to go below 800), and still no reboots/sod's 12 hours later.... my phone is freewil definitely runninga lot cooler. Can't be sure about battery life improvements since the Android OS process is the number 1 user of battery. It will be interesting to see battery life when Google fix the wakelock issues and then faux doesn't need to compromise around that.
[Nexus 4 Original Android Development] faux123:
"Backup" your settings under "Misc" Tab before upgrading. Then after upgrade, go back to "Misc" tab and hit "restore" and reboot!
[Nexus 4 Original Android Development] jhericurls:
I keep losing my options in the GPU section

http://db.tt/v9UDr0Lz

Only fix is to reflash the ROM and than the settings disappear again after a reboot
[Nexus 4 Original Android Development] faux123:
Thanks for the screenshot. I will take a look at it.. It seems that the app was unable to gain root access for GPU settings.... weird.
[Nexus 4 Original Android Development] spelaben:
Hi, I just sold my Galaxy S2 and got my Nexus 4 today and decided to try your kernel first after some reading in the original development section. :)

I noticed a minor issue in the FauxClock app, the minimum frequency setting won't stick after a reboot. All other settings are sticking fine though, I'm using the newest version of app and kernel.
[Nexus 4 Original Android Development] MasterJam882:
@Faux

Just saw the new ES4 kernel. Could you please tell us what's new in here?

Datafix? UV now possible?

greetz

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] linelock:
If you have mpdecision on it will change your min freq whenever you touch the screen.
[Nexus 4 Original Android Development] spelaben:
I turned mpdecision off as recommended in the second post, I don't think that is the cause.
[Nexus 4 Original Android Development] Bluewall:
Same problem as you mate ! But only since the new app update.

To avoid useless question :

CM10.1

004mR2

Clean install (ROM + Kernel)

SuperSU (and not superuser)
[Nexus 4 Original Android Development] faux123:
Hm.. I will look at it. It might be a race condition between mpdecision and my app... you see, by default mpdecision is ON before android is done booting. The app only runs after android has completed booting and then proceed to disable mpdecision (if you have it disabled), but if you touch the screen before the app start up (you will see the SU toast notification for my app), then the minimum could be raised to the mpdecision minimum of 1026MHz.

Is that what you are seeing when you say the min does NOT stick?
[Nexus 4 Original Android Development] Bluewall:
I think that's not the actual problem. I let the phone start and when all is started properly, I touch it and launch your app (there's a toast saying that the service is already running).

But it's not only the frequency that are resetted, that's the whole set-up, it's back to the default settings.

Hope it helps :)
[Nexus 4 Original Android Development] ceroglu:
+1 with min frequency is not sticking on reboot. Everything else is working great.
[Nexus 4 Original Android Development] tyea:
Cm10.1 01/16 + Faux 5b03 is working well for me. I'm just starting to use S2W and find it more useful than I previously thought. I'm using the Faux recommended settings posted on the OP, with interactive governor, and only 256k read ahead, instead of 2048k.

Occam LGE-960, Tapatalk
[Nexus 4 Original Android Development] Sucalakafufu:
getting that darned not recognizing kernel bug in the app every so often. even after all these beautiful updates :(
[Nexus 4 Original Android Development] faux123:
ROM and logcat?

Next time when it happens, grab a logcat immediately after the issue and tell me which ROM you are using.

for logcat app, I highly recommend Logcat Extreme from Play store.
[Nexus 4 Original Android Development] xmatrix13:
Every time I set the LMF Freq for the itelledemand gov it resets to default value after close app and loading it back up.
[Nexus 4 Original Android Development] faux123:
LMF is tied to Max CPU freq from the CPU tab. It's designed on purpose like that.
[Nexus 4 Original Android Development] jacklebott:
Try uninstalling and reinstalling Faux's app. I was having that problem, and that fixed it
[Nexus 4 Original Android Development] xmatrix13:
I assumed that as well, but I also assumed that my MAX CPU freq was set to 1.5 but it wasn't....once I changed the CPU freq the LMF values followed.... Faux u are the man when It comes to quick replies!
[Nexus 4 Original Android Development] B3rt0:
Can anyone recommend that app: https://play.google.com/store/apps/details?id=me.paranoid.touchcontrol ?
[Nexus 4 Original Android Development] faux123:
That's the pgm app from galaxy nexus. It's basically monetized version of showp1984's sweep2wake mod. It's done differently though. Showp's version directly mod the touch driver, the pgm is listening on the input events. Both however use the same power key emulation originally from ezekeel's hack from galaxy nexus.

That's the history of sweep/slide to wake development in a nutshell ;)
[Nexus 4 Original Android Development] copi:
hi faux

what kernel that u running now? the 4r2 or 5b3? i want to follow u hehe.
[Nexus 4 Original Android Development] B3rt0:
just a shot into the blue... but I guess faux is way to busy with scripting and hacking to testdrive his own betas :P
[Nexus 4 Original Android Development] faux123:
It's virtually impossible to be on the same version as me ;) I'm always 1 to 2 versions ahead. I'm on 005b04 ;)
[Nexus 4 Original Android Development] B3rt0:
Well that proves me wrong :P
[Nexus 4 Original Android Development] copi:
booo.. ur cheating.. lol. ok i already found the answer. so got to be the beta one :D thank u
[Nexus 4 Original Android Development] Caner092:
I installed free version of this app but it say that your kernel doesn't support. Are you going to add support for this app? It has some good features like double tap to unlock etc.
[Nexus 4 Original Android Development] Sucalakafufu:
ill try next one. was on the go so couldnt do it. btw i use catlog. good enough? or should i still check out logcat extreme?
[Nexus 4 Original Android Development] raycaster3:
That's been the topic of discussion (among other things) on the last cpl pages. Have a read .

DARKSIDE
[Nexus 4 Original Android Development] 0.0:
i am wondering, why is there a toast message saying "service is already running" whenever i open the faux app? an option to turn it off would be nice, if you want faux
[Nexus 4 Original Android Development] joshnichols189:
Is the "enhanced stock kernel" the same as the mainline kernel?
[Nexus 4 Original Android Development] sherman_nguyen:
I tried every kernel that faux123 posted and by far 005b003 is not great for battery life. I used the same setting as he used on the first page. Max frequency for me is 1.35ghz and i used intellidemand, but i only got 13 hours on battery and 2h47 min on screen. The best one for me is kernel 004b004. With that one i got 22hours on battery and close to 5 hours on screen.
[Nexus 4 Original Android Development] drtek:
Hi, since using this awesome kernel my battery status drops straight to 95% directly after unplugging it from the usb charger. Did a battery wipe but it didn't last for long. Is this kernel related?

Thanks, Tek.
[Nexus 4 Original Android Development] B3rt0:
I cant complain. 1d 5h and 3h screen on time and 17% left ;)
[Nexus 4 Original Android Development] remydlc:
My settings never stick as of late. I back it up, but it doesn't restore, not even a single one of them after the reboot.

Is anyone having the same issue?

Update: the phone got in a hung state, and rebooted it, after the reboot the settings reset without me flashing a thing. Weird.

Update 2: the settings applied. I guess it just takes about a minute or so. Maybe that explains the locks up after a minute or so the phone boots up.
[Nexus 4 Original Android Development] sherman_nguyen:
It happened to me also. The phone keeps rebooting and i have to flash the stock kernel before i could flash back to 005b003 again
[Nexus 4 Original Android Development] Globespy:
Someone probably answered this, but the answere answer is in the OP. You need to uninstall your current su update to SuperSU for settings to stick

https://play.google.com/store/apps/details?id=eu.chainfire.supersu
[Nexus 4 Original Android Development] Locksmith81:
Never had this problem ever... All settings stick through all flashes
[Nexus 4 Original Android Development] superleeds27:
Beta 05003 hasnt been out 1d 5h so how can u say its good?
[Nexus 4 Original Android Development] B3rt0:
oh :P lol havent seen the latest beta. my fault. i am on 002. sry
[Nexus 4 Original Android Development] sherman_nguyen:
It out for the past 10 hours. Haven`t you check the faux app yet
[Nexus 4 Original Android Development] gd6noob:
1 day has 24hours... His reply was stating thats its been out for less then 1 day, so did the other guy have 1day5hr tested... what is wrong with his statment?
[Nexus 4 Original Android Development] sherman_nguyen:
Hahaha my bad then, i thought he mean he used the other kernel and have not checked the new one net.
[Nexus 4 Original Android Development] nic85:
in kernel info I read "tue Jan 15" it's b2 or b3?

I can't read which version I've installed