yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Guto ViP:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

We will need buy this program too or will work together with Faux Clock?

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] sherman_nguyen:
I think it is fine because i was able to UV it to -200mv and i saw many of the frequency run on the same voltage.

If you are asking about the comment related to Faux then here it is

http://xdaforums.com/showpost.php?p=37054966&postcount=739
[Nexus 4 Original Android Development] Ace42:
It's a separate app altogether but he said if you bought Faux clock you will get something extra/special.
[Nexus 4 Original Android Development] Guto ViP:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Hmmm, so let's see what waiting for us. :thumbup:

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] rmkilc:
Is it correct that only 1512 and 384 MHz is used with interactive governor?
[Nexus 4 Original Android Development] hhyong99:
nope, it uses other frequencies as well.
[Nexus 4 Original Android Development] rmkilc:
So why is mine not? I am using faux's 006b01 kernel, with CM10.1.
[Nexus 4 Original Android Development] MatAuc12:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

In version 003 (I believe) Faux dissociated intelliplug from intellidemand and implemented in all governors. Its a smarter plug that doesn't turn off the 3rd or 4th core for no reason (from what I noticed, it will essentially never turn on 3 and 4 if only 1 app gives a load, and rightfully so since no single app benefits from more than dual core at the moment).

So bottom line, you get the project butter clock boost, but it will not ramp other cores needlessly.

This is my observation and abstraction and not factual fauxs re-wording, so take it for what it is.
[Nexus 4 Original Android Development] gianton:
If you are using faux's recommended settings change as follow:

interactive gov control:

Hispeed Load - 99

Hispeed Freq - 1026000

Timer Rate - 20000

Min Sampling Time - 80000

Set On Boot - On
[Nexus 4 Original Android Development] ifti_a:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Are these settings in fauxclock ?

I can't find them ?
[Nexus 4 Original Android Development] gianton:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Yes under "Governor" tab.
[Nexus 4 Original Android Development] tanjiajun_34:
Does anyone's phone rebooted when on mako-jb-kernel-005m?

I tried it my phone got reboot out of a sudden. Then when my phone is back up, the Swiftkey keyboard's data seems to be corrupted. It forgotten everything. That is just the only app that was affected in that reboot.
[Nexus 4 Original Android Development] daralph:
Most reboots happen because of massive OV, lift the voltages a bit and see what happens.

I had the same problem once and just installed a backup of Swiftkey, but dont ask me for the reasons..
[Nexus 4 Original Android Development] Mash87:
Are you undervolting? If so give 12,5mV back

had a reboot this night. I was already late for work so couldn't grep a logfile :(

I turned UV up from -137,5 to 125, now running fine again.

See if that helps.
[Nexus 4 Original Android Development] ifti_a:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I'm using intellidemand....Lol

No wonder they were missing
[Nexus 4 Original Android Development] ifti_a:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I'm using faux final 5m

Lost about 4% last night
[Nexus 4 Original Android Development] Guto ViP:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I'm getting a little over three hours of screen with the Faux kernel, is this normal? I did not UV.

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] Ace42:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Depends on your other settings, usage, signal strength, etc...
[Nexus 4 Original Android Development] nic85:
the reset kernel in OP is working? i have an aborted installation in cwm.

i need stock kernel to try one thing... :confused:

p.s. i'm on aokp maybe it can't run with stock kernel?
[Nexus 4 Original Android Development] Mash87:
check the md5sum, fauxe's server has hiccups some times.
[Nexus 4 Original Android Development] nic85:
bu that is stock kernel? do you know if it works on aokp? i need to test one thing (CPU binning)
[Nexus 4 Original Android Development] CloudTown3:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I believe AOKP comes with Faux's enhanced stock kernel. You could also relflash the ROM to get that kernel back.
[Nexus 4 Original Android Development] El Nino1977:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I can usually get near 5 hours screen on time in a working day. Average of 3/4 hours in 2 days without charging
[Nexus 4 Original Android Development] Guto ViP:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

:( for me.

Maybe my problem is because i donne the first battery cicle?

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] Giacomo700:
R: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Faux, I am going on a business trip where I will be making light demands on the phone in terms of performance - basically just email, calls, maps, web browsing; no games or video - but I really need the battery to last all day. Which of the following setups would you recommend? Am on CM 10.1.

1. 005m kernel (with settings as they are when installing the kernel, I won't be able to tweak and experiment while on the trip)

2. enhanced stock kernel r5

3. CM 10.1 kernel

Thanks in advance for your help and advice!
[Nexus 4 Original Android Development] resynx:
For some reason my search function isn't showing up so I apologize Faux if this has been asked before. Now I know it is recommended to turn off mpdecision with your kernels, but what about with your enhanced stock? I'm using interactive and would you recommend to leave mpdecision on or off? Thanks everyone :D
[Nexus 4 Original Android Development] droidmeup:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Mate I would go for 5m, intelidemand-mpd off/Eco mode on/ snake charmer on. 384/1350. Voltage, -100 . Auto brightness is a must.
[Nexus 4 Original Android Development] B3rt0:
AW: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

:) with beta006m1

sent from my Nexus 4
[Nexus 4 Original Android Development] rmkilc:
What will that do and why should I do this?
[Nexus 4 Original Android Development] El Nino1977:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Enhanced stock would be the best option, stick with fauxs recommended settings in post 2 and you'll be fine my friend.
[Nexus 4 Original Android Development] gianton:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

You asked why your device is only using min and max freqs all the time. If you change to what I suggested the device will use the 1026MHz freq too.

That's with interactive gov enabled.
[Nexus 4 Original Android Development] rmkilc:
I thought interactive governor used all the frequencies. Is this not true?
[Nexus 4 Original Android Development] gianton:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Not with the default settings in faux kernel.
[Nexus 4 Original Android Development] Ace42:
It can access every governor, use CPU spy to see which are and aren't used.
[Nexus 4 Original Android Development] rmkilc:
Please refer to my previous post, found here: http://xdaforums.com/showpost.php?p=37153175&postcount=4483
[Nexus 4 Original Android Development] codesplice:
Are there any updated instructions for managing the eco_mode status via the terminal? /sys/devices/system/cpu/cpufreq/intellidemand/eco_mode (or echo_mode, for that matter) doesn't exist even when I set Eco Mode: On using the app.

Alternatively, does Eco Mode only affect the intellidemand governor? The reason I ask is that I use Tasker + a couple of scripts to switch between battery and performance settings when I launch a specified game; I'd like to be able to enable Eco Mode for general use but make sure I have all four cores active when I'm gaming.
[Nexus 4 Original Android Development] Ace42:
In your photo all freqs between 384 & 1512 were used.

Above hispeed delay = "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load"

go_hispeed_load = "when the CPU hits X% amount of load, then jump to the hispeed_freq."

min_sample time = "how long do I wait before lowering the clock speed from what it's currently at."

timer_rate = "wait this long before changing the clockspeeds from what it's at now."
[Nexus 4 Original Android Development] MatAuc12:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

He said battery life is paramount.

In ES you don't get intelliplug intellidemand eco mode and all the other tweaks.... Those are huge battery savers.

Go with latest beta and you should be totally fine. (Or last mainline if you prefer), the guy before who recommended settings were good settings too.

---------- Post added at 03:04 PM ---------- Previous post was at 03:00 PM ----------

Did you even look at something else than the bars? When you have 62% of deep sleep + your min clock added + your running clock, it doesn't leave many % left for the ramping clocks. The clocks that are not "milestones" do not get hanged on, they are just there for incremental speed and are used as such. You chart looks totally reasonable to me. 14 minutes across 3 hours of activity.
[Nexus 4 Original Android Development] dispatch:
FYI I get the same data drops with faux ES5 kernel.
[Nexus 4 Original Android Development] faux123:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I haven't heard of data drops since a few betas ago.
[Nexus 4 Original Android Development] Reatret:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Settings please :)
[Nexus 4 Original Android Development] Lush78:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Haven't had any data drops on ES5 and I have been using it heavily since it was released... Prior to ES4, I was getting them regularly... I believe data drops were resolved with ES4...
[Nexus 4 Original Android Development] SeaSeeC:
I think i'm getting data drops on the 006b1 and on 5m. When on hspa I randomly lose my cellular data.

Should a logcat be fine for the next time it happens or do you need something else as well?
[Nexus 4 Original Android Development] Guto ViP:
I found a bug in the kernel or better in sweep2wake, when during a call the screen goes black but the touch still works, finishing the call or dial involuntary if the numeric keypad is enabled.

Kernel version 006-B1 ( the same with 005)
[Nexus 4 Original Android Development] Mash87:
I'm seeing a lot of throttling to 1.134GHz max. in fauxapp since 06b1.

Same usage behavior as on previous kernel versions where this did not happen. Using intellidemand governor, mpdecision off.

EDIT: Added kmsg
[Nexus 4 Original Android Development] MatAuc12:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I second this. I attributed it to maybe not covering the proximity sensor correctly for a while because, let's be honest, I have a tendency to hold my phone pretty hectically when talking. But I recently realised it was definitely still inputting touch when screen is black (avoiding to use the word "off" because it apparently would be technically wrong).

---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------

What is your max clock and does of throttle and eventually go back to your max clock or once it throttled that is the new max? Also under which circumstances? Gaming? Browsing? Bench?
[Nexus 4 Original Android Development] rmkilc:
I still don't understand how so many people get 4+ hours of screen time per charge. The most I have seen is 1.5 hours, on all the kernels I have tried. The guys getting 4+ hours, are you on a carrier besides AT&T? Could it have something to do with fastdormancy?
[Nexus 4 Original Android Development] jjcandroid2012:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

That's odd I get around 4 hours of screen time and I have att. That's with several different kernels too. Maybe bad battery?
[Nexus 4 Original Android Development] rmkilc:
My buddy has similar results. Both live in the same area with Nexus 4s on AT&T. Both with "fast" processors.
[Nexus 4 Original Android Development] jjcandroid2012:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I really think its a battery issue with stock kernel and everything I would get two hours of screen time and that's with auto sync on brightness on auto and location on
[Nexus 4 Original Android Development] Guto ViP:
Maybe your configuration?

Do you have Auto Bright? Google, Haxsync, Whatsapp and Voxer accounts syncs on? Kernel UV? Location on (Google Now)? Programs running in background (Cerberus, Avast, Faux Clock and etc..)?
[Nexus 4 Original Android Development] rmkilc:
Yes, I have most of those. A week ago I did a complete wipe, and started with nothing. Over a few days I slowly started installing my plethora of apps, and the results were similar. Nowhere near 4 hours of screen-time.
[Nexus 4 Original Android Development] erikiksaz:
Indeed, go find betterbatterystats and find what's causing your wakelocks.
[Nexus 4 Original Android Development] Guto ViP:
I have all of theses - Auto Bright, Google, Haxsync, Whatsapp and Voxer accounts syncs on, Location on (Google Now), Programs running in background (Cerberus, Avast, Faux Clock and etc..) and my better screen time has 3 hours ans some minutes.
[Nexus 4 Original Android Development] MatAuc12:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Is latitude logged in? Latitude causes insane battery drain and should only be signed in when you actually wanna share your location. I'm saying that because once you sign up for latitude (which a lot do because its pretty awesome) as soon as you link your phone to your gmail, it will be enabled by default and not noticeable except in Maps -> Settings
[Nexus 4 Original Android Development] Mash87:
I've added a kmsg to my post, if further logs are needed let me know.

My normal max is 1.35GHz. Once it is throttled down it stays there until I change it back up.

It happens even while texting or browsing the gallery. Web browsing also. I rarely play games.

Happens with eco mode on and off, I've UV'ed by -125mV

EDIT: Added another kmsg

You can see I've changed the max. to 1.35GHz. After a short time of browsing the frequency is adjusted to 1.134Ghz and never changes back up
[Nexus 4 Original Android Development] Guto ViP:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

My Latitude is off I never use it. :)

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] faux123:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I can't find your post. Are you using intellidemand governor? If so the so call throttling is done on purpose to save battery while web browsing texting or any activities which take a while to complete.

It will return back to original frequency when those activities are completed.

If this feature bothers you, switch to interactive governor. Check out the FAQ on the first few posts
[Nexus 4 Original Android Development] Mash87:
the throttling itself is fine, just that it won't change up again (for me) is an inconvenience.

If you say it is something specific for me only that it wont change up again I'm fine and I'll try with a clean wipe of ROM and kernel again. But maybe it occurs for others too on 06b1
[Nexus 4 Original Android Development] faux123:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

It will change back after the load has gone away for a few minutes. The only chance it won't go back is when you have something constantly running in the background creating a load keeping the CPU busy.

Or switch to interactive governor. If you are still experiencing issues with interactive, then you may have a rogue app
[Nexus 4 Original Android Development] Mash87:
aah

. That might be the key. Probably I haven't waited long enough. I'll keep an eye on that

Thanks for your answer, much appreciate it.
[Nexus 4 Original Android Development] B3rt0:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Intellidemand , faux' settings :)

Sent from my Nexus 7
[Nexus 4 Original Android Development] 999vulcan:
ES is buttery
[Nexus 4 Original Android Development] DroidRC1:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

I'm getting by far my best battery life on 006b1 with intellidemand , eco mode on, sio and UV 125...11 hours with 3 and half hours screen on
[Nexus 4 Original Android Development] DirkBelig:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

What does sio do better than fiops, as recommended by faux?
[Nexus 4 Original Android Development] MatAuc12:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

The differences between schedulers is mainly the priority and queue system. Every other scheduler than FIOPS take into account seek time and are designed with that in mind. Since flash devices do not have seek time, FIOPS should be overall better.

Obviously, it is nearly impossible to make a scheduler that will be the best in every situation, so it is hard to analyse and compare. But the fact seek time is a core behavior, removing it as a factor should make FIOPS a no-brainer (benchmarks and real-life also seem to suggest that).

As faux said "FIOPS is the only scheduler built from the ground up with flash in mind". I also believe faux created FIOPS.
[Nexus 4 Original Android Development] DeepEmbrace:
EDIT: This result is when on Wifi for the whole durration. I tried this while i was out and only using the mobile network and the results are SEVERELY impacted. Seems like there are data drops and battery life is draining much faster :(

EDIT2: There are no data drops. I analysed the log cats and there is nothing being reported on the radio. Its just slow to pickup. Might be signal in my area :S

I heard some of you guys need some settings to break out 5 hours of screen on time.... so here is my setup that made me a happy bunny ;)

Quick Stats:

Mainline 5 (stable) kernel running on googles stock rom (4.2.1)

1.2Ghz Max - 384min - Intellidemand

Mpdecision - OFF

Eco mode - OFF (why have 4 cores and not use it??? :silly:)

Snake Charmer - ON

Voltage - -100mV (-150 is not reliable, and -125 is not reliable at 1.5Ghz)

GPU - 400

IO Scheduler - CFQ (differences are not massive between them. Nor do i personally feel it, so i set it back to stock roms idea of CFQ)

Read ahead - 1024 (2048 just as good... still playing on this)

Emmc Entroppy - OFF

Sweep2Wake - OFF (what is this S**t :P Not really my thing)

TCP - Westwood

Vibration - 60%

Anything i have not mentioned are default what Faux has set. All them "up threshold" extra tweaks, im still playing with myself.

And this is some extras im doing on top to really pull more battery life:

Wifi:

Program - Wifi tx Power

Reduced power to 18dB. 25dB is pointless. Not enough reduction. But 18 is good enough to not have any bad drop outs and keep speed up :)

Display:

Program - Screen Filter

On Auto brightness, it felt to me that is was just a tad too bright. So with Screen Filter, i made a 69% profile. So i could have auto brightness as i did my day to day thing, but reduce the brightness a little more.

I believe the screen is just the biggest thing to work on to save battery, but thats the price to pay for something so bright and beautiful ;)

Oh, nearly forgot... My usage for that screen on time is a full day of Facebook, Twitter, Whatsapp, Gmail, Texts + phone calls and a good 2 to 3 hours of music while i on purposely left the SCREEN ON :P

Turning it off DRAMATICALLY increases battery time while listening to music, i could push that 17 hours further if i was using it like a normal person. And i went to bed with 9% battery. Woke up 6 hours later to find it at 5% (as you see).

Faux, you beter not mess this up, or ill go Iphone :P

Cheers brother :victory:
[Nexus 4 Original Android Development] DeepEmbrace:
Valid points. I guess i just didnt want to make it feel unresponsive. Like i said, some things dont feel like they do much. What aint broken, dont fix :P

Its all very subjective this business, but you are totally right about the voltages to what cap i set.... i face palmed at my own mistake :P

Gonna get lower now and see how far i can push this ;)
[Nexus 4 Original Android Development] guggi4:
Hi, just one question:

I kind of like the on demand governor and i read that faux said that ondemand needs more or Less mpdescision. But I in op stands that it is highly recommended to turn of mpdescision cause it conflicts with intelli_plug.

But I also use eco mode I think I read something that it needs intelli_plug...
[Nexus 4 Original Android Development] rmkilc:
Why do you like the ondemand governor? This kernel isn't really tailored for that...
[Nexus 4 Original Android Development] nic85:
R: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

is this kernel compatible with this command?

http://xdaforums.com/showthread.php?t=2052496

i cant't get any info

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] copi:
u have to do that command right after reboot. :good:
[Nexus 4 Original Android Development] nic85:
R: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

omg thank you! 4=faster :D

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] copi:
me too "4".. my understanding is 4 = faster.

but i also try that command on harsh kernel,, and its show "fast" :confused:

but I dont really care anyway hahaha.. the best thing is my phone flies with good battery

faux good,, harsh also good. nexus 4 has the best devs, thats why it makes the best phone right

really enjoyed
[Nexus 4 Original Android Development] dark_ente:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Just flash CM10 and run the command. That's what I did anyway

Sent from my Nexus 4
[Nexus 4 Original Android Development] nic85:
R: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

with eco mode the phone is running always with only 2 cores? or only with apps that don't need much power?

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] 0.0:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Your phone is running on 2 cores once eco mode is on

Sent from my Nexus 4
[Nexus 4 Original Android Development] Guto ViP:
Mine is nominal and im using -125 UV with no problem.

---------- Post added at 10:17 AM ---------- Previous post was at 10:14 AM ----------

Faux, and about my question about sweep2wake?

Tnx.
[Nexus 4 Original Android Development] nic85:
R: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

oh, I switch it off...

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] jhericurls:
Re: [Kernel] (version 005) Mako (UV Control/CPU/GPU OC/Optimized) [Jan-19]

Sweep2wake is broken and you shouldn't use it, as simple as that.

If you want sweep2wake use Touchcontrol.
[Nexus 4 Original Android Development] Solarian:
I still got data drops on 5m too, I went back to 3m r2, and looks like I'll stay at that one for awhile.