yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] MoooN:
just wanted to thank you faux

the new betas with soc support etc are pretty awesome

for the first time after a full working day with light usage ~ 40 minutes screen i had 80% battery left in the evening

this never happened to me before

only thing i noticed were some anoying sound while listening to music @ 15b3

that might be gone with b4 need to test it first
[Nexus 4 Original Android Development] spelaben:
Awesome feature, so you can lure random people to connect to your hotspot and watch them fail.
[Nexus 4 Original Android Development] xflowy:
hey everybody. i know this is a common issue and i've already searched the thread multiple times, but i need to bring this up again:

has faux already included some kind of fix, to prevent the delay of notifications from whatsapp or whatever (wifi) when the phone is asleep. cause i am encountering this problem all the time. or am i simply doing sth wrong with my settings?

thanks a lot!
[Nexus 4 Original Android Development] stevessvt:
Scroll the drop down box down.
[Nexus 4 Original Android Development] jassycliq:
Faux I have a question about your governors, specifically ondemand. With other kernels if you set the up threshold to 95 it pretty much always idles at min then goes up to max then back down to min. Of course this is all done rather quickly. But every time I use your kernel ondemand behaves very differently. It maxes out very easily and then usually "gets stuck" (for a lack of a better description) at 702mhz for a while. This is with the same setup. I set all the up thresholds to 95 and the behavior is still very odd. To confirm my suspicion that it wasn't your intelli-plug doing anything funky, I built your kernel with a clean ondemand and it behaves as expected.

So is yours suppose to behave the way i described?
[Nexus 4 Original Android Development] ctfrommn:
Not trying to speak for Faux, but I think it is the way he set the optimal frequency and the sync frequency. Whenever I use this kernel I have to change those both to 384000 or I get the odd behavior you describe. I am not sure why those frequencies were chosen though.
[Nexus 4 Original Android Development] faux123:
yes, it's the new tunables causing the behaviors you've described and [MENTION=4110652]ctfrommn[/MENTION] is correct.

These new tunables allows the CPU to ramp up to specific sync and optimal frequencies first, hoping the Cores can complete whatever the tasks at hand... This is an attempt to save battery because if those frequencies can complete the tasks without jumping to the next step, you just avoided operating @ highest frequencies which uses higher voltages. If the load continue to peak beyond the optimal frequency, then the cpu is unrestricted and allow to go to max frequency @ highest voltage.

With this, I think it's time for another beta ;)
[Nexus 4 Original Android Development] faux123:
Beta 5 is out ;)

diff attach to shut GPL trolls up :D

Change Log:

* Fixed some bugs in intelli_plug, version 1.6 now :angel:
[Nexus 4 Original Android Development] Kagath:
Thanks for all you do for the nexus 4, i love you :D

But can you create zip for the beta ? :/

or can you explain how to create it or flash your file ?

For your work yesterday and tomorow and after tomorow i give you all my thanks :)

For your zip i give you all my thanks of today.
[Nexus 4 Original Android Development] Sucalakafufu:
the zips are actually available from fauxs app or site but I mirror them as some people have issues with fauxs host.

just uploaded 15b5

http://db.tt/T6w02Muf
[Nexus 4 Original Android Development] mkamal23:
So far so good with the new Beta. Everything seems smooth. Phone is cool. Battery life seems up to par with the previous builds. Will let u know more after a couple of days. Thanks once again for your work.
[Nexus 4 Original Android Development] bubbleguuum:
In Faux Clock, Under the Screen tab, whenever I change R,G,B values for the Amplitude[1] settings, they are lost and set to 0 whenever exiting and restarting the app. Is that a bug ?
[Nexus 4 Original Android Development] faux123:
It could be. Can you tell me your ROM/Superuser setting?
[Nexus 4 Original Android Development] wollyka:
Faux, i tried building your kernel and implement/add the OTG patch/hack discussed here: http://xdaforums.com/showpost.php?p=38906771&postcount=2

but it is not working. (Most probably i did something wrong).

My question is : would you ever consider adding this patch? (Since this is the only missing "feature" )

Sorry if i am asking too much or you already answered hat question before. ( I searched but i did not find anything)

Thanks
[Nexus 4 Original Android Development] bubbleguuum:
Stock 4.2.2 ROM, using SuperSU 1.25
[Nexus 4 Original Android Development] faux123:
I was thinking about it. Maybe I will add an Enhanced Stock with OTG...
[Nexus 4 Original Android Development] wollyka:
Thanks for the reply.

Now I will have another dilemma, using ES kernel or your full tbm kernel :p
[Nexus 4 Original Android Development] 0.0:
I hope faux adds it to his tbm one. It'll be cool! I don't want to switch to the enhance stock just for otg

Sent from my Nexus 4
[Nexus 4 Original Android Development] ftarules:
Can't download from faux website rift now. Can someone upload a mirror for 15b5?
[Nexus 4 Original Android Development] dzel:
wow looking forward to that.. I'm using the enhanced stock with slimbean rom & it's rock stable.
[Nexus 4 Original Android Development] linelock:
Here you go. 1 page back.
[Nexus 4 Original Android Development] DJMartini:
Been using majority of the betas abs haven't had any problems, but just got a random reboot on 15b5 not sure where to pull the logs to help investigate. Could someone point me in the right direction?

Thanks
[Nexus 4 Original Android Development] jassycliq:
adb pull /proc/last_kmesg

Or in terminal

su

cp /proc/last_kmesg /sdcard/last_kmesg.txt

Edit: corrected my derp
[Nexus 4 Original Android Development] MasterJam882:
Jihaaaaa.

Finally a little love for ES(best kernel in the world)

Thanks and greetz

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] kstano83:
Thank you very much. Today I had the androidos at 45%. I got the app but I dont really know whether something is wrong or not so I attached some screenshots. I have tried uninstalling some apps I dont really need or dont use much, but it didnt help. Maybe I should reflash the rom with a complete wipe?
[Nexus 4 Original Android Development] kara mustafa:
There is just a magic in this kernel:)
[Nexus 4 Original Android Development] kstano83:
constantly on wifi with over 6 hours of sot? HOW? :)

PLEASE share what settings and rom you used!!!
[Nexus 4 Original Android Development] JaylanPHNX:
There is a thread for better battery stats in the general apps section of xda. The first few posts have a lot of good information on how to use the app to track down battery hogs.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] cocchiararo:
Would you consider enabling and option in faux clock to have swipe2wake Not to enable on boot? The bug that disables the touchscreen when you reboot or turn on the phone and leave it untouched until the screen turns off is quiet nasty ;p

--

Tapatalk2
[Nexus 4 Original Android Development] VipinKC:
intellidemand

The Faux 123 Kernal app doesn't have intellidemand but is replaced with Ondemand,

I see few members have mentioned i am on intellidemand but i don't see that option.
[Nexus 4 Original Android Development] Michealtbh:
Are you running Faux kernel?
[Nexus 4 Original Android Development] VipinKC:
Yes, Faux Kernel and screenshot is of Faux Clock 123 enhancement kernel app
[Nexus 4 Original Android Development] wiwid.colgate:
I believe intellidemand at above interactive

Sorry for my bad English
[Nexus 4 Original Android Development] VipinKC:
Its not there in the app.

I am missing some thing
[Nexus 4 Original Android Development] Zaldi00:
Scrolling te list of governors.

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] wiwid.colgate:
It's so weird, coz I'm using this kernel too..

And I have that cpu governor...

Try to reflash the kernel, perhaps fixed the problem bro..
[Nexus 4 Original Android Development] Michealtbh:
Are you using Enhanced Stock kernel?
[Nexus 4 Original Android Development] morrislee:
Can you try.... Scrolling up that tiny list??
[Nexus 4 Original Android Development] dzel:
what kernel the guy coming from?

look like hes missing a file / folder/line???

did you do any mod?

either way flash the stock kernel from motley thread then faux..or clear the apps data..
[Nexus 4 Original Android Development] VipinKC:
I don't see any options

---------- Post added at 06:26 PM ---------- Previous post was at 06:25 PM ----------

Bought the phone and flashed the Faux Kernel first.

Reflashed the Kernel but same results

---------- Post added at 06:26 PM ---------- Previous post was at 06:26 PM ----------

Using Turbo Boost Mainline then moved to 15b4

---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------

Double Checked and no option of IntelliDemand

---------- Post added at 06:28 PM ---------- Previous post was at 06:27 PM ----------

I bought the phone brand new and flashed Faux Kernel directly.

I will try to flash the motely kernel and then Faux
[Nexus 4 Original Android Development] wiwid.colgate:
Im using mainline 4.2.2 stock
[Nexus 4 Original Android Development] xflowy:
am i the only one struggling with this annoying bug?
[Nexus 4 Original Android Development] morrislee:
Scroll up like this??
[Nexus 4 Original Android Development] VipinKC:
Reinstalled the App and it works now.

Thank You All for the Support :fingers-crossed:
[Nexus 4 Original Android Development] android88:
That happens when using WiFi with kernels that haven't implemented the patch to fix that yet. Faux hasn't implemented the patch yet.
[Nexus 4 Original Android Development] mkamal23:
So I noticed on the 15b05 that I would see my phone using the max clock value more than before. For an example... yesterday i was listening to music and watching a few videos, and I realized after I was done the phone would be a little bit more warmer than the previous builds. I also checked CPU spy to see what values have been used and it was more on my max values (1.836) than being somewhere in the middle. My set up was 162min-1.836max with Echo, mpdecision, and snake charmer off. Also was on C0, C1, and C3 on. Before with the same settings, 1.836 would be used very minimally with the other values being used more. As for performance, the phone felt just as smooth as the previous builds. Your kernels have always been smooth in my opinion with no lag whatsoever.But in this build... i just felt as if battery was actually draining a little faster than before. Maybe it could be something on my end. Maybe i had other things that i did not know running in the back. But this is just my experience. I know others could have the total opposite of my experience. Im just trying to give some feedback for a great kernel and amazing development.
[Nexus 4 Original Android Development] MoooN:
my nexus just died suddenly and doesnt turn on again ... red blinking when i plug it

IT WAS YOU FAUX IT WAS YOU :crying:

just kidding

going for a replacement device tomorrow when googles service openes again
[Nexus 4 Original Android Development] ctfrommn:
No need to replace it. Red light of death has plagued many and its usually very easily fixable. The best practice is currently to hold the power button for 30 sec to a minute, plug it in and let it charge for an hour or two and then hold the power button again to reboot. All that happened is your device thinks the battery is dead. Its almost never fatal or that big of a deal. For future reference dont OC as high next time.
[Nexus 4 Original Android Development] MoooN:
didnt oc at all

capped cpu @ 15xx

we will see it it works out with your method
[Nexus 4 Original Android Development] JediDru:
15b5 sleeps like a baby for me. Maximum clock intellidemand and fiops gpu at 400. Mp off eco on. Thanks again faux!
[Nexus 4 Original Android Development] Das IceDice:
Maybe someday we see this on your "Turbo Boost"-kernels :)
[Nexus 4 Original Android Development] jassycliq:
iirc RLOD is from excessive heating, usually cause by OC but can also be achieved from regular speeds, its just usually much harder for that to happen.
[Nexus 4 Original Android Development] MoooN:
after charging it for some hours its back now

seems it overheated as i was carying directly on my skin while doing sports
[Nexus 4 Original Android Development] ctfrommn:
Good to hear....this is usually the outcome. :)
[Nexus 4 Original Android Development] stevessvt:
I must have been lucky, I used mine for an hour on my dashboard in 85 degree heat, plugged in charging, OC to 1.8, and screen on the entire time with navigation.
[Nexus 4 Original Android Development] android88:
Was the phone hot?
[Nexus 4 Original Android Development] stevessvt:
Really, really hot. It wasnt charging anymore, but was staying at a constant %.
[Nexus 4 Original Android Development] xflowy:
thanks. but why hasnt faux implemented yet? should be to do nr 1., shouldnt it?

which kernels do have the fix?

thanks!
[Nexus 4 Original Android Development] MoooN:
very sad outcome

i was planing to do this a lot more having higher temperatures while biking

if this happens more frequently i might have to look for an alternative music player

nexus4 seems to have problems with that
[Nexus 4 Original Android Development] ctfrommn:
Are you undervolting? You could also underclock drastically if youre just playing music. Were you streaming or playing local music? Streaming gets a ton hotter.
[Nexus 4 Original Android Development] thracemerin:
The patch introduces a whole different set of problems.
[Nexus 4 Original Android Development] JamesInsights:
Anyone else here feels eco mode does not make much of a difference from your experience? On battery.
[Nexus 4 Original Android Development] j3di:
Makes a huge difference, as it should! Check you only have 2 cores active when turned on and all 4 when off.
[Nexus 4 Original Android Development] silvbm:
Starting with Version 12 I get random reboots. I used 12m, 13m, 14m and 14tbm and I tried all versions of the current beta 15.

Can someone take a look at the last_kmsg.txt and help me?

EDIT: NO Reboots with Kernel integrated in Rootbox ROM, so it has to be related to Faux Kernel.

Settings are: intellidemand. 384-1512, mpc&eco off, snake on, fiops, soc all sleep states on, rest as recommended
[Nexus 4 Original Android Development] JamesInsights:
Okay thanks. How do i check it? When using the faux clock app it only shows one core online.

My other problem is that amplitude 1 settings in fauxclock dont survive a reboot :(
[Nexus 4 Original Android Development] j3di:
https://play.google.com/store/apps/details?id=eu.chainfire.perfmon

Works in realtime and floats on top of other apps, very useful.
[Nexus 4 Original Android Development] pl4cid:
After matrix causes several soft boots I decided to use this one, running the stable mainline version of this kernel and there's nothing to complain. I use trickster and the recommended settings but from 162 to 1350 and 50mV uv.

Looks promising so far, thanks! ;)

Tapatalked
[Nexus 4 Original Android Development] kstano83:
My screen is unresponsive when I want to answer a call while my phone is sleeping. Pressing power button to turn the screen off (and silent the call) and turning it back on solves the freezing. Is this caused by low clock - 162mhz or SOC is not working ok with my phone? I have C0, C1 and C3 enabled.
[Nexus 4 Original Android Development] mzanette:
Oh I see, i've only started using this since last night.

Does it matter if I update to the latest nightly betas? Or should I stick to one for a few days? I'm on the lastest beta (and just updated the latest application from they play store)
[Nexus 4 Original Android Development] undercover:
Don't update for a few days. See how it goes. If it improves, do nandroid and then try next beta for a few days. If it doesn't deliver you can always roll back.
[Nexus 4 Original Android Development] bfspider:
dang, sorry, too many forum tabs open! :p
[Nexus 4 Original Android Development] MatAuc12:
1 thing to consider, if you play with your phone a lot and don't go through stuff like sleep and deep sleep cycles, your phone tends to be hotter, the hotter circuits are, the more current leakage (power effectiveness loss). So we do get lower battery life when we spend time tweaking and let go of our phones.You can jump from 3hours straight battery to like 4 hours on a daily use (which you would think would be the opposite because even screen off uses battery.

"Letting it settle in" is mostly a myth coming from first boots (where you build application caches) and maybe also from when we used to have to "burn in" batteries. If you install kernel, tweak and reboot at least twice, that's the most "settled in" you'll get.

And last, battery use gains are largely due to making your phone efficient for your usage. The type of usage you have should correlate with your tweaks. Sometimes UC or core controls could be detrimental due to taking longer to perform certain tasks.

Oh, almost forgot. You can most likely UV even more than that if you UC to 1.13. I run 800mv at 1.13GHz (if you raise your clock though it will instantly crash because the voltage need increases extremely fast after that and global UV makes clocks higher than 1.13 require more than the relative mV 1.13 needs.
[Nexus 4 Original Android Development] undercover:
Settle in is to stop people from messing with it hence decreasing constant high drain ;)
[Nexus 4 Original Android Development] MatAuc12:
Indeed, people try a setting 10min, see 2% drop, reboot, lost 5%, change settings to extremely low battery drain, reboot, lost 3%, freak out, says f it, might as well go high performance, have the same drain as low battery drain settings then say f it, I see no gain.

All that in maybe 2hours.

Lol
[Nexus 4 Original Android Development] undercover:
I still do it sometimes. It's like a reflex you have to overcome with knowledge. So its easier to say "let it settle in" to others AND yourself :D
[Nexus 4 Original Android Development] MatAuc12:
How do you think I know the process? :p except maybe the step of "omg, this sucks, no gain" that I just extrapolate from kernel/ROM threads post :p
[Nexus 4 Original Android Development] mzanette:
Not really I set it this morning and didn't tweak at all during the day. Just used my phone as I normally would but battery went down 50% in only 8 hours which is pretty much normal for me even before I installed faux's kernel. I was expecting to see some improvement but so far seems the same to me. :(
[Nexus 4 Original Android Development] MatAuc12:
The post you quoted is mostly an overexageration and joke that people can relate to.

Secondly. From the info you tell me you have awesome battery life. Morning = 7-8am? Means by 3-4pm you have 50% left? Another 8hours = 10pm? Which is bed time or at least a time you have a plug close that you can bump charge for 10mins for an extra 2 hours while you cook dinner or choose your TV channel?
[Nexus 4 Original Android Development] zimphishmonger:
Anyone else having a problem with the GPU speed not sticking after a reboot in FauxClock (even with set on boot enabled)? Mine keeps jumping back up to 487mhz for some reason.

AOKP Dec8, V002b4 Kernel, Only cpu control app is FauxClock
[Nexus 4 Original Android Development] MatAuc12:
App update fixed it for me.
[Nexus 4 Original Android Development] mzanette:
16 hours in a day of moderate use I don't really consider "good". In any event my point is that's my normal battery life before I even flashed this kernel so it hasn't seemed to make a difference so far. I'll give it a few days and see how it goes.
[Nexus 4 Original Android Development] zimphishmonger:
Im using the latest version :/
[Nexus 4 Original Android Development] MatAuc12:
Honestly, a day is 16hour awake, 8hours sleep (standard day). Which means you have a full day charge which is more than you can really ask for. But what are you looking for really?

Gains depend heavily on type of use, individual devices, apps, ROMs. It is known that kernel tweaks can really be YMMV. Also the "measurements" are really subjective. It depends on network load, precise use, how much movement, day of the week (seriously), was more apps open in the background or not, if autobrightness was on was the usage under the same light.

Today I stayed at home and just browsed mostly, I got 5h20 screen on. Tomorrow I will be in my car a bit, go in a building that connection can be spotty and also DLNA 2-3 TV shows off my phone while browsing. I don't expect to get 5h.

What you might think was no gain today could be some gains that you just didn't notice because your usage was slightly different (yes it was, it always is). But you can't really know, maybe you would have had 7h to 50% today.
[Nexus 4 Original Android Development] mzanette:
Maybe I'm expecting too much I was just disappointed that my battery seemed the same after all the tweaks. Like I said I'll give it a few days and not worry about it to see where I stand.
[Nexus 4 Original Android Development] undercover:
Just tweaked mine few hours ago. Charged it fully. Now on 61 percent left, after 4h off charger and 2h7m screen on.
[Nexus 4 Original Android Development] italia0101:
What kind of battery life are people expecting ?? I'm still on stock and easily get 3 hours screen on time daily with 15 hours in total ..
[Nexus 4 Original Android Development] undercover:
That's piss poor for me. I come from a sensation where with extended battery (1900mah) I would most definitely get 4.5h. Normally over 5h. And that phone was regarded as really bad with battery life. That's from morning till evening, minimum of 14h. So, I expect 4h minimum, averaging 4.5h+ in 14h off charger. These are my expectations.
[Nexus 4 Original Android Development] italia0101:
Well I guess then its perception. . I mean I came from a nexus s that on occasion couldn't get 1h 20 of screen on time lol

I'm on 30% right now with exactly 3hs screen on time and up time of 14h 32...
[Nexus 4 Original Android Development] cocchiararo:
From beta 3 or 4 to beta 5 my phone stopped working, keeping the last image it had displayed on screen (last time it was a black screen :p)

Dunno what could cause this tho

--

Tapatalk2
[Nexus 4 Original Android Development] stevessvt:
I just discovered that mpdecision has to be off for ecomode to work correctly.
[Nexus 4 Original Android Development] danslecarton:
faux, I'm getting this again on your latest beta

Photo is taken with the stock camera app zoomed in

Any ideas how to fix it?
[Nexus 4 Original Android Development] meangreenie:
I suspect superuser in causing random reboots. Never seen so many reports on it since roms started integrating it.

Install supersu from the market and let it update the binary by running it. Then disable superuser in the settings and delete its app entries, then reboot.

Could be totally wrong though, and I don't mean to rag on superuser, but it may be worth a go if your suffering from reboots.
[Nexus 4 Original Android Development] silvbm:
Could be, but on Carbon and Rootbox ROM both integrated Kernels were ok, reboots started with Faux Kernel!
[Nexus 4 Original Android Development] ftarules:
Can we flash supersu in recovery? Is that easier?
[Nexus 4 Original Android Development] Reatret:
Where can I find the latest enhanced stock?

Also does it have the intelliplug? Or only mpdecision
[Nexus 4 Original Android Development] meangreenie:
Which ever way you like :)
[Nexus 4 Original Android Development] linelock:
There is link on the op for es kernel. And no, it only has mpdecision.
[Nexus 4 Original Android Development] faux123:
New beta is out.

Latest USB patch from caf

Rtc patch from caf

Power charger patches from caf

Bfp jit patches added

Final beta for 015 series.
[Nexus 4 Original Android Development] MrMagic:
I have the exact same issue. I'm on Carbon ROM, which one are you on?