yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jacklebott:
Yeah, it's Qualcomm's way of deciding which cores should be online or offline. It's not very efficient but it gives great performance, which is why I only have it on while gaming. The minimum frequency changing is a part of mpdecision, it changes it to 1026MHz when the screen is touched
[Nexus 4 Original Android Development] Reatret:
Ok then is mpdecision in intellidemand because its changing the minimum there also :o
[Nexus 4 Original Android Development] faux123:
I recommend turning off mpdecision completely. The new intelli_plug is a complete replacement of mpdecision.
[Nexus 4 Original Android Development] Reatret:
I also see people mentioning s2w how would one enable this? :)
[Nexus 4 Original Android Development] 3bs11:
Faux's app > Misc tab > Turn on Sweep2Wake.

Here's a video demo if you don't know what it does or how it works (I didn't up until yesterday) http://www.youtube.com/watch?v=RtmxlnikTiQ
[Nexus 4 Original Android Development] faux123:
if you have fauxclock (my app) you can find it under "misc" category and enable it.

if not, you can use terminal or some sort of script manager and do:

echo 1 > /sys/android_touch/sweep2wake

it is disabled by default because most users don't want to have the feature enabled unless they want to use it. With it enabled, it may cause more drain while in pocket due to accidental triggers.
[Nexus 4 Original Android Development] 3bs11:
I thought show-p1984 said it shouldn't be triggered in pockets etc because the mako has a capacitive screen?
[Nexus 4 Original Android Development] romeoliny:
Okay so Faux what you added in beta 6 fixed the issue I was having with the screen becoming unresponsive.

However I'm noticing a brief delay where when you turn the display on (after deep sleep) it comes on like a back lit black screen then comes on fully after about (slight delay) one to two seconds.

This happens to me on both s2w and power button.
[Nexus 4 Original Android Development] jacklebott:
Why would that make a difference? If my screen is on in my pocket, my legs press the screen constantly and it starts navigating randomly. I'd assume the same principle applies

Though I suppose if for some reason you have the screen facing outward, that'd be different. I don't know why anyone would do that though
[Nexus 4 Original Android Development] faux123:
the brief pause is due to touch driver detecting a lockup condition and re-initializing the touch driver to a pristine state. While the touch driver is being re-initialized, it will have a slight pause, It is an unfortunate side-effect but it fixes the complete lock up issue.
[Nexus 4 Original Android Development] ChongoDroid:
Couldn't be happier so far, 2hrs 30 minutes screen on at 35% brightness

Edit: Phones gonna last longer then me *yawn*

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
capacitive screen will be triggered if there's enough static (bio) electricity touching the screen. In a thick coat jacket, it probably wouldn't trigger anything, but in a pocket from pants, your legs may trigger them. So it really depends on the situation.
[Nexus 4 Original Android Development] 3bs11:
Will you be working on the s2w feature to try and optimize it to minimize battery drain, lock up issues and delays or having to sweep several times to get it to work? Or is this not your work so you can't change it?
[Nexus 4 Original Android Development] Reatret:
So this is all with beta6?
[Nexus 4 Original Android Development] 0.0:
it started from beta3. beta5 added a lot of tweaks. beta6 just added a fix for unresponsive touchscreen
[Nexus 4 Original Android Development] faux123:
Showp1984 is the real author for this. I simply took his original work and added a few features and fixed a few minor bugs. He deserves lots of credit for this orignal work. :highfive: :good:

He has something else instore for sweep2wake coming soon (NO ETA of course, but it should be pretty sweet). I don't want to go too far off tangent if he has major changes coming up.
[Nexus 4 Original Android Development] 0.0:
when he does release some updates to his sweep2wake, will you include his code into your kernel as well?
[Nexus 4 Original Android Development] Reatret:
Got it! I needed a reboot because sweep2wake wasnt showing up for somereason :) many thanks! Will post first cycle tomorrow
[Nexus 4 Original Android Development] faux123:
Yes, I will try to sync with his updates whenever he releases a new version or updates.

For now, sweep2wake is MOSTLY working with some minor inconviniences like multiple swipes to wake from deep sleep plus slight pause for people with screen lock up issues due to re-initialization of touch driver.
[Nexus 4 Original Android Development] MiG123:
i've noticed more lag and less butter in UI especially on opening recents when turning off mpdecision. no significant difference to battery life observed between these 2 'governors'. do advise on the advantages using the new intelli_plug over mpdecision given i do not want to sacrifice even an ounce of butter/performance on this phone (the very reason why i got a nexus)
[Nexus 4 Original Android Development] faux123:
The UI performance should be similar but the battery life should be better with intelli_plug.

mpdecision (a closed sourced non-user tweakable proprietary solution from Qualcomm running in userspace) artificially raises the miniumu CPU frequency to a ridiculous amount (1.026 GHz) and keep it there for serveral seconds before releasing it for EVERY touch input. So if you are running games or using apps with lots of touches, this artificial floor @ 1.026 GHz is an overkill and may use more battery than it's really called for.

intelli_plug replaces the mpdecision with an OPEN SOURCE in kernel solution. It will ramp the CPU speeds only when needed and does NOT artificially raise the minimum to do so. It is also tweakable because the solution is open source. I also added an Eco mode for those seeking longer battery life.

For your case seeking absolute performance, give interactive a shot with mpdecision OFF and Eco Mode OFF. This should give you probably the best performance. You can give my tweaked ondemand or intellidemand a shot as well.

If you still feel that none of my solutions satisfy your needs, you can ALWAYS turn on mpdecision and go back to Ondemand.

With my kernel you HAVE ALL THE CHOICES (some kernels have mpdecision disabled completely, so you have NO choice in turn it back on even if you wanted to).
[Nexus 4 Original Android Development] jacklebott:
Hmm, I had never though to try Interactive. Interactive+Intelli_plug appears to yield the same performance as OnDemand+Mpdecision in-game! Whew now I can stop caring about mpdecision ;)
[Nexus 4 Original Android Development] wazka2:
Does anyone know if its possible to save a profile with screen settings on fauxclock so its not needed to adjust after flashing new ver.
[Nexus 4 Original Android Development] 0.0:
Profiles aren't in the app. I hope it gets implemented in the near future

Sent from my Nexus 4
[Nexus 4 Original Android Development] zimphishmonger:
Unfortunately, still experiencing lock screen glitch when you the touch screen is unresponsive in 003beta6 :( Hard to grab a log if ur not near a PC as you essentially are forced to three-finger . Sorry I cant provide more info, reverting back to beta3
[Nexus 4 Original Android Development] trismegistos:
Do you have s2w enabled?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] asawoszc:
I'm having random data connectivity issues on 3b6 where it just won't connect to anything until I reboot phone. I came from 3b3 and did a full wipe of everything and install to latest CM nightly. Data then works for a period of time before stopping again. Three times it's happened. Anyone else having this issue? On intellidemand with mpdecision off and snakecharmer on. All other settings default.
[Nexus 4 Original Android Development] kwerdenker:
Did you test it with a different kernel to see if the issue persists? Since you also updated your ROM, there is more than one variable that changed.

Send from my secret moonbase via space carrier pigeons
[Nexus 4 Original Android Development] asawoszc:
Agreed it might be the latest CM nightly at fault. Haven't tried a different kernel yet but if it happens again I'll go back to 3b3 and see what happens. Thanks for the reply.

EDIT: Went back to 3b3 and the data connectivity issue is gone. So looks like it's something in the newer beta's (in my case).
[Nexus 4 Original Android Development] zimphishmonger:
Yes

Sent from my Nexus 4
[Nexus 4 Original Android Development] kwerdenker:
The battery with this kernel is really phenomenal. Got around 35 hours with nearly 6 hours of screen on time. Usage was mostly surfing and tapatalk, with sync and latitude on and some push and pull services too.

3/4 of it was with 3b3, the rest with 3b5.

Settings: 384 min, 1512 max, intellimand, mpdecision off, eco on, UV - 175mv, GPU 200MHz ondemand, s2w off, brightness on auto

Thanks for your work faux! :thumbup:

Send from my secret moonbase via space carrier pigeons
[Nexus 4 Original Android Development] pro.aggro:
b6 still got these WhatsApp delivery problems. I think it was with b5 when i heard of it.

Messages arrive 10-20min later.
[Nexus 4 Original Android Development] 0.0:
I don't believe the kernel has anything to do with it. The ROM or the app could be at fault

Sent from my Nexus 4
[Nexus 4 Original Android Development] gknnn':
it is a kernel Problem ;)

Faux should Check..

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Der_Schubi:
@kwerdenker:

Do you really get no issues with -175mv? My N4 gets unstable at -75mv. Did you try this once with eco mode disabled?

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] fnf:
I concur. I was having problems with intermittent data connection and slow speed for the last 2 days with beta 5 and 6. I'm using 3 (UK) with strong HSPA+ 15 signal. Switching back to the stable version 002 avoided the problem (beta 3 may work too as I didn't recall having issues with it).

Granted we need a larger dataset though.
[Nexus 4 Original Android Development] Sucalakafufu:
not all chips are the same. im stable at -200 with any settings
[Nexus 4 Original Android Development] Der_Schubi:
I know. I just wondered...

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] MontAlbert:
I am also having data connection issues.. It will just all of a sudden lose connection although it tells me maybe 2 or 3 bars and it's still connected but in reality there is no internet connection. I put it down to being in a holiday place most recently and before that maybe an issue With wifi tether in Aokp but it seems to do it randomly. Reboot seems to be only way to fix it.

Will test a different kernel tomorrow to narrow issue down to kernel.
[Nexus 4 Original Android Development] Harsh:
@Faux123 if you implemented "EHCI: HSIC: Add support to vote for SVS digital voltage" in your version beta6, than you need to make changes in your board-mako too.

You need to look as latest 3 commits and add those in your board-mako too.

board-mako.c history

May this help in solving few data issues which were brought in beta6
[Nexus 4 Original Android Development] Michealtbh:
Beta5 is fantastic. Currently at over 5 hours screen on/17.5 hours total with 15% remaining, that includes some Google Nav and gaming (NFSMW and Devil's Attorney) and loads of browsing/Tapatalk/Reddit. It's much smoother than previous versions too due to Intelliplug, just as smooth as kernels with Qualcomm's mpdecision imo.
[Nexus 4 Original Android Development] kwerdenker:
I'm really lucky with the chip I got but while undervolting helps with the battery usage, it's not the holy grail some people make it. Having a good governor that doesn't jump around too much and keeps the frequency as low as possible, combined with as much deep sleep as possible contribute much more to the battery savings in my opinion. Also how you use your mobile greatly contributes to how much time you can squeeze out of it.

Go as low as you can with the UV but don't be bummed out if others can go lower. That's just the way it is with IC chips :)
[Nexus 4 Original Android Development] faux123:
check my git, was done already.
[Nexus 4 Original Android Development] Harsh:
no you are missing my point. Yes you already did those commits but missed them out in board-mako.c

here is your history of board-mako.c
[Nexus 4 Original Android Development] faux123:
Ah I see :D I did miss you point. Just woke up :D

It's 6:40 AM and I completely forgotten about LGE's split mako/8064 board files :p
[Nexus 4 Original Android Development] Harsh:
Goodmorning... and have a great sunday.

That thing is really working, I observed better battery on HSDPA after that commit. Wish we could find more like those :D
[Nexus 4 Original Android Development] faux123:
Thanks man, just cherry-picked your commits :D No need to re-invent the wheels :D
[Nexus 4 Original Android Development] Ace42:
Faux are there any updated camera drivers on the way, maybe from CAF?
[Nexus 4 Original Android Development] faux123:
what's wrong with the current camera?
[Nexus 4 Original Android Development] italia0101:
Hay faux has the thermal stuff coming on ? :)
[Nexus 4 Original Android Development] Ace42:
I'm not sure if its the stock software or the driver but the image quality differs greatly from the iPhone 5 despite sharing the same sensor.

It seems like they Google is nuking features, default screen calibration is diff from lg and an embarrassment, and lte chip isn't stated even tho it functions.
[Nexus 4 Original Android Development] ExMM:
This setting is stable for me as well, I just pushed it to -212mv and its still stable!
[Nexus 4 Original Android Development] expertzero1:
Dump state asked me for root. Anyone know what that is ?
[Nexus 4 Original Android Development] Redmed427:
Just flashed 3b06 last night.I'll report back in a few days. My main concern is battery life, which I'll be keeping an eye on sharply. So far I get a tiny bit of delay when trying to unlock the phone, but other than that it is pretty smooth.

Sent from my Nexus 4
[Nexus 4 Original Android Development] flx-grafix:
Got a problem with the FauxClock app, it's causing massive wakelocks.

Was on CM10.1 Nightly & faux Kernel as I noticed that AndroidOS was taking up until 50% in the batstats. Tried several things, wiped caches, re-flashed CM, uninstalled apps and so on... without success.

So I did a factory reset, made a fresh and clean install of CM. Wakelocks were gone. Stayed on the stock CM Kernel, installed one app after another to see if it's an app waking up the device.

After installing FauxClock to tune the screen, the wakelocks reappeared. Just to be sure, I uninstalled the app and rebooted - wakelocks gone again.

Had to uninstall, since the wakelocks were draining big time. And therefore... sadly, back to the washed out colours.

Could it be that this is a problem with the stock CM kernel and FauxClock?
[Nexus 4 Original Android Development] Reatret:
What exactly does eco mode do? Does it lower performance?
[Nexus 4 Original Android Development] 0.0:
It can, or most likely will on heavy intensive apps. It shuts off 2 cores so you're pretty much running a dual core device instead of a quad

Sent from my Nexus 4
[Nexus 4 Original Android Development] Zanr Zij:
Turn off 2/4 cores, lower performance, save battery!
[Nexus 4 Original Android Development] faux123:
FauxClock does NOT hold any wakelock (apps need to request for wakelock from Android System, which my app does NOT). So it couldn't possibly keep the phone awake at all :p
[Nexus 4 Original Android Development] djkinetic:
Faux the new b6 is wow, I went to bed and about 9 hrs later check my phone it had only lost 1 freaking percent....with previous kernels i would have easily lost 10 percent...great job!!
[Nexus 4 Original Android Development] flx-grafix:
Thank you very much for your reply.

Maybe it has something to do with the screen tuning? I'm gonna install the app again right now, but won't do anything in it. Gonna check back in an hour for wakelocks. Maybe it's not the app itself, but something the app triggers? Sorry, I'm no dev and dunno how things like screen tuning work, but it has to be something since installing and tweaking started the wakelocks and uninstalling fixed them. Haven't done anything else to my phone during this time.
[Nexus 4 Original Android Development] Ace42:
It could be an app you already have installed. Some apps/games have the permission to keep the device awake.
[Nexus 4 Original Android Development] Luk_Sch:
Wanted to see what I can squeeze out of this little sweet thing.. AOKP 27/12 Build + 3b5

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] DforDesign:
Woot, beta7 up? Can you give us the changelog faux?
[Nexus 4 Original Android Development] Michealtbh:
Probably includes the tweaks for better battery life when on 3G mentioned by Harsh earlier
[Nexus 4 Original Android Development] DforDesign:
I jumped from bricked kernel. Applied reset kernel first, cleaned cache and dalvik, applied b7 and when I lock the phone and unlock it after few min it is soooooo laggy. No matter what settings I have in fauxs app.

It looks like it locks on 384MHz

No problems in bricked btw. What can be the cause?

The in advance
[Nexus 4 Original Android Development] expertzero1:
Did you do the reset kernel then reboot then go back to recovery and flash faux kernel again with wipe cache
[Nexus 4 Original Android Development] Ace42:
^Follow the poster above

And are you saying that the min/max are both locked at 384, or that the min is locked at it? :confused:
[Nexus 4 Original Android Development] faux123:
Kernel 003 Open Beta 7 is out!

Enabled a couple of features that was from Beta 5 but was not enabled in Beta 6 because I forgot about LGE split the board files into their own which was pointed out by Harsh. (Thanks to Harsh for pointing this out)

Added a couple of minor bug fixes to Ondemand and Intellidemand.

Latest beta can be found here:

http://faux.androidro.ms/mako/beta/mako-jb-kernel-003b07.zip
[Nexus 4 Original Android Development] grisha1:
Bricked renames thermald and mpdecision with _bck. Make sure you follow the instructions in one of the first posts (maybe even op) from bricked thread to name them back. :thumbup:
[Nexus 4 Original Android Development] GSMachinst:
Did you fix data going on and off on beta 7?
[Nexus 4 Original Android Development] faux123:
yes, it's all fixed in beta 7 (AKA release candidate :D )
[Nexus 4 Original Android Development] DforDesign:
Yes. It shows min 384 and Max 1512, but cpu spy shows almost only 384MHz. No matter what governor settings I have even at high speed load at 10:D

Edit. Looks like moving max slider left and right fixed it:D strange...
[Nexus 4 Original Android Development] Ace42:
You say "almost only" so that means it used other freqs, no? If the CPU load is not enough it will not increase the clock but on my phone it spends most of its time at the min and deep sleep. Try running a benchmark or "stability test" and you'll be able to see if it's really stuck.
[Nexus 4 Original Android Development] DforDesign:
I tried stability test and it was stuck on 384,but now it looks fine.
[Nexus 4 Original Android Development] raycaster3:
Make sure to wipe cache and dalvik after flashing. I tried flashing the kernel and not wiping cache and dalvik and got the unresponsive screen and reboot didn't fix it. It may or may not be the case from everyone... should probably wipe the caches after every kernel flash anyhow.

DARKSIDE
[Nexus 4 Original Android Development] wera750:
I had this problem many many times, and in your case after a deep sleep ,it will come back. Wipe data on faux clock app, reboot to recovery and flash the rom,gapps, and kernel again.
[Nexus 4 Original Android Development] DroidRC1:
Thought wiping caches for kernels was useless
[Nexus 4 Original Android Development] IAmAN00bie:
Hey, I know we can monitor time-in-state for the CPU, but is there any equivalent way to see what states the GPU spends time in?
[Nexus 4 Original Android Development] zimphishmonger:
I'm still getting the touch screen issue , even w beta7. Am I missing something? Used the reset kernel in between. Only thing I havent done is a full wipe. Even On first boot of beta7, touch screen is unresponsive.
[Nexus 4 Original Android Development] supersain08:
Touch screen didn't work on latest beta. Went back to beta 2
[Nexus 4 Original Android Development] Thorsten_de:
Hello!

How about touch screen didn't work?

My touch screen works, but a little bit slow after press the power button or sweep2wake.

Thorsten.
[Nexus 4 Original Android Development] flameinthefire:
im on paranoidandroid rom and when i flash this kernel it doest not boot. it gets stuck on google logo. what do i do?
[Nexus 4 Original Android Development] zimphishmonger:
I'm having the same issue with beta 7. Touch screen is completely unresponsive in boot

Sent from my Nexus 4
[Nexus 4 Original Android Development] guapinoy:
Yeah you may want to wipe or check some rogue apps. I'm getting deep sleep with intellidemand.

Nexus 4 using xda premium
[Nexus 4 Original Android Development] undercover:
Ah, that explains it (sort of, off to research powerHal). Weird that they chose rom to control it some of the cpu functions. Well, I'll be keeping an eye on your progress. Thanks for reply.
[Nexus 4 Original Android Development] mastibeta:
Just did a clean flash of room and kernel...still have deep sleep as an unused step...very odd. I rebooted and wiped dalvik.
[Nexus 4 Original Android Development] P0MM3S:
hi there!

just wanted to say that battery life is great with intellidemand!

faux, you might check out shaky156's kernel https://twitter.com/shaky153/status/273042339566592000 , as it provides a great improvement in performance!

big thanx for all your work!
[Nexus 4 Original Android Development] afbengochea:
Are you on WiFi or using network data? For some reason I noticed that on Wi-Fi I was getting deep sleep but on data I wasn't

More than likely is a rogue app though
[Nexus 4 Original Android Development] mastibeta:
I think i had a hangup in the market installs, every time i rebooted another app or two would pop up on my homescreen, even though they were already installed, im getting deepsleep now, but im going to try shaky's kernel.
[Nexus 4 Original Android Development] Letitflow:
there is no intellidemand for me with beta 004, where is it? :eek:
[Nexus 4 Original Android Development] ctfrommn:
Download link in post #220....few pages back.

---------- Post added at 11:18 AM ---------- Previous post was at 11:04 AM ----------

Not sure how others are getting such great performance from this kernel.....benchmarks fell apart on it for me. Back to Faux's fabulous kernel! :)
[Nexus 4 Original Android Development] danyshotbang:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!

i ordered the Nexus 4 used to have HTC One X then i saw that the Nexus 4 had a touchscreen sensitivity problem is that fixed in ur Kernel or is there no fix for it pleas answer!
[Nexus 4 Original Android Development] mastibeta:
I think he is mistaken the performance increase as being kernel related, when, in reality, it is likely due to the updated antutu.

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------

the touch sensitivity is fine on the nexus.
[Nexus 4 Original Android Development] ctfrommn:
Im referring to people getting over 18K on Antutu....I managed just 14k with Shaky's and 16 with Faux's.
[Nexus 4 Original Android Development] faux123:
I haven't heard of any issues with touchscreen. Point me to the right direction and I may look at it.
[Nexus 4 Original Android Development] ctfrommn:
Early on some were measuring touch sensitivity and found it much less sensitive than the Gnex and Nexus 7. I have yet to hear anyone complain about actual issues when using the device.
[Nexus 4 Original Android Development] undercover:
It might be not the most sensitive display, so if you have very thick dry skin you might experience a bit of problem, but in general it's good enough.