yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Pac-Man:
Is there any problem with deep sleep and such stuff on later posts? :)
[Nexus 4 Android Development] txuki2005:
Nor, all fixed.
[Nexus 4 Android Development] madskillz.yu:
How to update kernel if i already have previous version, should i just flash it or i need to dirty flash rom and follow procedure from first post?
[Nexus 4 Android Development] abbas416:
dt2w

how to enable double tap to wake up?
[Nexus 4 Android Development] dragos281993:
Get Kernel Adiutor Mod from here: http://xdaforums.com/showthread.php?t=3333549

To activate dt2w, just open the left side panel, go to "Wake Controls" and you'll see there the option you want to activate.
[Nexus 4 Android Development] Pac-Man:
I feel that PN (previous version) with this kernel with Ondemand governor drains the battery too fast :(
[Nexus 4 Android Development] txuki2005:
Rom problem not kernel... rom need updated to last security updates...
[Nexus 4 Android Development] ivanich:
Confirming, the same issue in hellspawn kernel, with ondemand it refuses to stay at 384 Mhz. Tried with cm13 rom.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] txuki2005:
So.... in next release i will delete dyn_hotplug.... this hotplug affect to my ondemand....
[Nexus 4 Android Development] snacs:
For me it's ok, better than before. Don't do that, dyn_hotplug is awesome.
[Nexus 4 Android Development] Pac-Man:
I had turned on, but battery drain is too high. I should change the rom for one more updated (OmniROM, for example), and try again.
[Nexus 4 Android Development] snacs:
I'm using RR. If you like CM, there's a lot of nice features and very stable.
[Nexus 4 Android Development] :
cm13 rom. Today I had automatically shut down the phone, as happens in version r.45 and r.46, there is no problem in the version r.44 .
[Nexus 4 Android Development] jacomail95:
Can this be done in this kernel? I'm sort of a audiophile :D thanks for reading

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

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] zeeBomb:
Its been a while since I was here! What post includes the updates to the newest version of Taurus?
[Nexus 4 Android Development] dragos281993:
http://xdaforums.com/showthread.php?p=67787702
[Nexus 4 Android Development] zeeBomb:
I'm a little surprised I finally updated when I was still on R42. Why no more decrease to the voltage to under 384Mhz? Otherwise, still stable, and deffo my favourite.
[Nexus 4 Android Development] mjehan:
R47 will contain the August security patches and performances fixes right ?
[Nexus 4 Android Development] txuki2005:
New update is coming with august security and more....
[Nexus 4 Android Development] txuki2005:
R47 aosp/cm

R47 CM/AOSP online

Changelog:

- August security update

- Security patch CVE-2016-5340

- Anothers patches

- Compiled with Uber 5.4.X last version

- Settings by default on ramdisk:

- Max brightness 100

- Vibrator amp 70

- GPU: Simple, max 400 mhz by the fault. ( OC with synapse or adiutor)

- CPU: 384-1512 ( Overclock to 1.7)

- Ondemand Governor by default

:eek:Must be installed on your preferred kernel stock rom.:eek:

DOWNLOAD

AOSP

https://www.androidfilehost.com/?fid=24591000424954492

CM

https://www.androidfilehost.com/?fid=24591000424954493

;)
​
[Nexus 4 Android Development] TheArt.:
Thank for the update [MENTION=5311064]txuki2005[/MENTION], by the way do you think that this: http://xdaforums.com/showthread.php?t=2769899&page=1 could be useful to you and us?
[Nexus 4 Android Development] txuki2005:
Miles thanks!!

Yes, you can study it. :p
[Nexus 4 Android Development] AndroidXDA:
With last version of Chroma I have reboots on startup.

I install from CMR, wipe all, install chroma, install open gapps, install taurus kernel, reboot... and mobile power off alone in startup always.
[Nexus 4 Android Development] Applesan:
any logcat?
[Nexus 4 Android Development] orcgoblinsupply:
Looks like everything is going fine with this kernel and fake Nexus rom. Is there any guide to all CPU governor tunables? I found only some of them in Google.
[Nexus 4 Android Development] :
good kernel. long battery lives, but today I again automatically turn off the phone.
[Nexus 4 Android Development] AndroidXDA:
Sorry? logcat?
[Nexus 4 Android Development] bart.found:
CWM recovery is more than deprecated! Install TWRP Recovery before flashing Marshmallow ROMs and Kernels
[Nexus 4 Android Development] bart.found:
hi [MENTION=5311064]txuki2005[/MENTION], no ETA, just pour parler.... Is there any plan to compile this Kernel in Nougat flavour?

Thank you! ;)
[Nexus 4 Android Development] pfederighi:
I love the stability of this kernel. I used to love the battery saving properties of this kernel; I used to be able to get at least four days per charge with my regular use. Now I'm lucky to get two. Perhaps it's related to my questions: Does anyone else have the issue that the first cpu core is always at maximum frequency no matter the frequency, the governor, or the hotplug? Are there any solutions to this?

edit: Okay, I rebooted and tried intellidemand. Now it actually seems to work well, but it seems to be the only governor that does. What's up with the others?

edit: Well, never mind. The intellidemand governor is now displaying weird behavior as well, like keeping all the cores at 1026 MHz even when there is no load.
[Nexus 4 Android Development] txuki2005:
I think..... nor, because maybe .... i have to rebase the kernel and i dont have time to do it...

Sorry :(
[Nexus 4 Android Development] bart.found:
It's a pity... but life comes first!

Thank you for your awesome work! I think this is the best Kernel I've ever used
[Nexus 4 Android Development] ziouzitsou:
Is it possible to keep the cpu speed at 384Mhz during the touch of the screen (eg. scrolling) in Synapse?

In franco’s kernel the relevant option was ‘input boost freq’ if I remember correctly.

I have ‘MSM limiter’ enabled, but I haven’t found a relevant option.

Thanx
[Nexus 4 Android Development] Applesan:
Hi, maybe you could build r48 (for android 6.0.1) with last security patches for the last CM nightly builds. We have december builds: cm-13.0-20161221-SNAPSHOT.

Because of: Cyanogen Inc shutting down CyanogenMod nightly builds and other services, CM will live on as Lineage.

Maybe this is the last nightly builds for Mako on android 6.0.1.

We will be very grateful to you. TaUrUs is the best kernel ever for Mako.
[Nexus 4 Android Development] Jorge R:
There will be no problems and install the kernel in omnirom?

Can you give a last update to the latest versions of AOSP and CM? ;)
[Nexus 4 Android Development] Applesan:
very good job, fantastic stability work. good battery life, nice smooth.
[Nexus 4 Android Development] .stendeck:
Do I necessarily need UKM and/or synapse and/or busybox to profit by Taurus' optimizations? ;)
[Nexus 4 Android Development] granazis:
[MENTION=5311064]txuki2005[/MENTION],Hi friend at first i ought to say Tnx for still supporting our N4.

Your new project is just excellent in all fields.Its still my preffered kernel.

Many thanks

Regards, Christos
[Nexus 4 Android Development] bart.found:
If you want to tweak every single parameter of the kernel you need to flash ukm and install synapse and busybox.

You can also use the kernel out of the box, or tweak it via kernel adiutor, but you won't be able to change some values..
[Nexus 4 Android Development] chaostrodamis:
[MENTION=5311064]txuki2005[/MENTION] do you recommend using your version of ukm or the original.
[Nexus 4 Android Development] dragos281993:
I suggest you use that.
[Nexus 4 Android Development] chaostrodamis:
Sorry but I'm kinda unsure which you mean by that.
[Nexus 4 Android Development] dragos281993:
Sorry. Tsuki's UKM, I meant.
[Nexus 4 Android Development] cet.junior:
Hi there,

I've tried to install the latest Taurus kernel (R42, in the time of this post) in my Nexus 4 (CM13 snapshot), and every time that I install it, my screen goes like a negative, with strange colors (really, like a negative or without any touch of red or something like that on screen - for reference, things like Instagram turned out cyan/blue and the green of material design turned a brownish yellow). I've tried to take screenshots to show you, but it seems ok on the screenshots, like it is happening only with screen itself; tried to change gamma and RGB settings through Kernel Adiutor and other apps too, but no success.

When going back to Quanta or the CM stock kernel, everything went fine again. I've wiped cache/dalvik cache, changed the TWRP (was using 2.8.7.0, changed to 3.0.0 and now 3.0.2), but no lucky at all. For now, I'm back at Quanta R14 and TWRP 3.0.2. I can't wipe data now, because I use a bunch of corp apps that are a pain in the ass to get back again.

Anyone has passed through this? Any clue how to solve it?

Thank you very much.
[Nexus 4 Android Development] arjundas86:
This inverted colours problem usually happens when one installs an AOSP kernel on a CM ROM or vice versa. Double check to see that you got the CM version of Taurus, not the AOSP.
[Nexus 4 Android Development] cet.junior:
arjundas86,

Yeah, it was that! My bad! :good: :good: :good:

Thank you very much!
[Nexus 4 Android Development] arjundas86:
Glad to help :)
[Nexus 4 Android Development] THEBANDIT420:
Hey is there CPU OC on this kernel or not? Installed it and it doesn't seem to have it.
[Nexus 4 Android Development] fr3quency:
Using kernel adiutor, I see I can OC up to 1,7GHz
[Nexus 4 Android Development] deani77:
In newest R42... Minimum speed have been increased to 384MHz compared n R41, 192MHz. Was that correct?
[Nexus 4 Android Development] dragos281993:
The presets bother you ? You can easily configure the kernel according to your needs with Kernel Adiutor, etc. And considering the amount of features and customizations, tweaking is something ordinary and expected from the users.
[Nexus 4 Android Development] :
Yesterday I was again spontaneous turn off the phone. Please help, why this is happening...
[Nexus 4 Android Development] dragos281993:
Problems occur when the users don't bother doing some research before flashing stuff. That's the main culprit.

1. When the user flashes a custom kernel over another custom kernel, problems occur. That's probably the most frequent error users do and end up having problems.

2. Then, when the user flashes a new kernel following instruction but forgets to wipe the data from the kernel manager that he used for tweaking the previous kernel, before he reboots and do the necessary steps for the transition to another custom kernel, problems will occur. Why ? Because the kernel manager, right after the device reboots, will apply the "old" settings. Why is it a big deal ? It's a big deal because those settings were meant for the previous kernel and kernels are different. That means that the kernel manager is gonna try to apply settings that are completely different and the phone will get "seizures" cause it doesn't known what exactly to do. And it reboots. Then the phone boots up, the kernel manager applies the same "corrupt" old settings, and makes the phone "confused" again, and it won't have another choice but to reboot again, and so on.

So if you did what I wrote at step 1, you screwed up and you need to dirty flash the ROM that you're currently using in order to override the custom kernel, and only after that should you flash the desired custom kernel. Or easier, you can extract the "boot.img" file from the ROM that you're using, flash it in recovery then flash the preferred custom kernel. It's faster this way.

If you did what I mentioned at step 2, then go to Settings, Apps, search for the kernel manager that you're using, and delete its data and cache, then reboot the phone . Only then can you do all the tweaking that you want.

Another thing that causes random reboots is excessive UnderVolting. Not all the phones can take the same UV. For instance, some went to -175 without problems, and others couldn't UV more than -95 without getting a random reboot.

GPS always turned on can make the phone reboot, as one of my friends experienced. The fix for that is to have "Location" turned off and activate it only when you need "directions". This saves battery too.

Xposed is very well known to cause a LOT of problems too.

Also, make sure you don't have both hotplugs active. You must disable the active one before activating the other one.

As for myself, I didn't get any problems with r42 and I've started using it a few days before the users got the final build. So, without a doubt, the problem is on your end.
[Nexus 4 Android Development] xenyz:
Look at /proc/last_kmsg to find out. It is the kernel log from the previous boot. Save a copy (# cat /proc/last_kmsg > /sdcard/last_kmsg.txt) and upload somewhere for devs to look at.
[Nexus 4 Android Development] :
I just install rom and kernel:

installing the rom I use TWRP

before installing the rom, I do Wipe Cache / Dalvik cache and system

I install rom CM 13

I do Wipe cache / cache dalvik

I install kernel Taurus MR1 R42

and again I do Wipe cache / cache dalvik

I'm doing something wrong?
[Nexus 4 Android Development] bart.found:
Which kernel tweaker do you use? Synapse? Kernel adiutor? Did you undervolt? Did you delete data of these apps (also uncheck the apply on boot checkbox and reboot to restore kernel defaults)
[Nexus 4 Android Development] :
I do not use any kernel tweaker. Only I install kernel and uses the default settings.
[Nexus 4 Android Development] mubaidr:
May i ask why do you want custom kernel? if you do not want to change any settings? :)
[Nexus 4 Android Development] :
TAURUS MR1 R42 better battery life, the phone runs faster than on the stock kernel CM 13
[Nexus 4 Android Development] ju1da:
Anyone please suggest balanced settings for the 4.2 kernel! I just changed cpu governor to smartmax_eps min 192, and GPU governor to conservative.
[Nexus 4 Android Development] mesaj:
https://android.googlesource.com/kernel/common/+/f7ebfe91b806501808413c8473a300dff58ddbb5 [MENTION=5311064]txuki2005[/MENTION] could you verify and eventually include this?
[Nexus 4 Android Development] txuki2005:
Yes, i included it a long time ago ;)
[Nexus 4 Android Development] mesaj:
Glad the best kernel is alive again since R41 was pretty unstable for me and hoped you won't leave us with it forever :fingers-crossed:
[Nexus 4 Android Development] mohsinkhan35:
How can I make this kernel permissive? The ROM I am using requires a permissive kernel. I have searched on these forums and so far, the procedure involved the ROM to work. But, when I flash custom kernel, I get bootloop and can't get into the ROM.
[Nexus 4 Android Development] dragos281993:
http://xdaforums.com/showthread.php?t=2524485
[Nexus 4 Android Development] zeeBomb:
Hello...I have been summoned to try this new kernel! Any of you guys undervolt? If so, by how much? I've undervolted from lowest to greatest: 725, 750, 775, 825, 850 875, 925 950 975 1025 1050 1075 1125 and hardly any crashes.
[Nexus 4 Android Development] Mrcactuseater:
Why even bother undervolting?

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] mubaidr:
I am using -125mv global and -150mv for 192 and -100 for the last freq (1.7ghz).

---------- Post added at 08:51 AM ---------- Previous post was at 08:50 AM ----------

To reduce heat and some mild increase in battery life.
[Nexus 4 Android Development] Mrcactuseater:
I'm quite aware of the heat decrease, but surely underclocking to a slightly lower clock speed would be more effective, while still keeping the device reliable.

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] bart.found:
705@192

715@384

720@486

745@598

760@702

800@810

825@918

850@1026

875@1134

935@1242

950@1350

987@1458

1025@1512

pretty stable, no freeze, no reboot, no SoD! ;)
[Nexus 4 Android Development] tom0769:
Maybe a note (or let's say warning) regarding undervolting/overclocking.

I'm no android developer, but I'm an embedded developer for many years now.

If you read the data sheet of an µcontroller/µprocessor briefly, there's always some specification of core voltage over frequency.

You have to be aware, that if you leave this specified range, the manufacturer of the device will give no warranty for the behaviour of it.

In other words the devices may behave in any way, doing anything thats imaginable, there's no predictable behaviour guaranteed any more.

Sometime you'l get "only" something like freezes or reboots.

BUT it may also happen that (by accident) some code is unintentionally executed, that could at least softbrick your phone.

I experienced this several times of my own, seeing that definately death code was executed by a µcontroller that was driven out of its specification.

You could succeed 999 out of 1000 times with doing so, but one time you could byte the dust;)
[Nexus 4 Android Development] Applesan:
Here is my undervilting.
[Nexus 4 Android Development] bart.found:
I also like to live dangerously! XD

Higher voltages may harm your device's hardware, but lower voltage can cause instability issues and, maybe, cache corruption, and this, 99,999999% of the times leads you to a random reboot. I never read before about someone that damaged his device undervolting it...

wow! Crazy high undervolt!
[Nexus 4 Android Development] Ciao600:
Actually, it isn't so heavy. I used to undervolt until 665 mV@ 94 MHZ with hellscore kernel and Mahdi rom (4.4.4). With lollipop and newer Android version I can't go lower than 700 mV.
[Nexus 4 Android Development] bart.found:
Do you have a "faster" CPU? Mine (fast), can't hadle less than 700mV, but my undervolt table is the same since kitkat times!
[Nexus 4 Android Development] zeeBomb:
Applesan that's INSANE undervolting...is that stable? Or did you apply liquid cooling onto your nexus, LOL :p

Hmm interesting. I'll see that too.
[Nexus 4 Android Development] Applesan:
For me it is really stable! :)
[Nexus 4 Android Development] zeeBomb:
Holy hell Apple San...you're now my Apple Senpai, cuz this EXTREME UV is working really well for me too. Wow...runs a LOT cooler too (I also have the faster bin on my nexus 4) how can I save/scrap great posts like these?
[Nexus 4 Android Development] dragos281993:
Undervolting is not something very healthy for the CPU. What you're doing is basically starve the CPU of the correct amount of power it requires to operate properly. Higher frequency are even in more need of a good voltage. For example when you OC a PC CPU, you're gonna increase the voltage, gradualy, for better stability, NOT reduce it.

Undervolting to a specific value may bring down the CPU temperature >a bit< but you'd have to set the max CPU frequency a bit lower and also manually set a value for the frequencies over 1GHz to something not as much as what the lower frequencies received. Over time the CPU will weaken and it won't be as tough as before.

A quick analogy: let's say the CPU is the human brain and the voltage is the oxygen the brain requires to "operate" properly. If you're trying to do something, easier or harder or a combination of both, your brain will need the required amount of oxygen to keep you "healthy" and lucid.

The moment you reduce your supply of oxygen and try to do the same things, you're gonna get tired easier and at some point, due to lack of oxygen, you'll just faint.

The same goes for CPUs. Limit the amount of voltage the CPU requires to operate properly and at some point the thing will just "faint" through a random reboot. If you didn't get a random reboot after undervolting at a stupid low value, it means that you barely used your phone. Try multitasking a bit and basically make the CPU "run" from "a place to another" and then you'll get it to "sweat".

You're not gonna get better performance just because the CPU is a tiny bit cooler and it wouldn't throttle as much as before. Lower voltage means punishing the CPU and that alone creates instability and poor performance. Better battery life ? Never got that even after testing the phone for a few days with -95mV.

The CPU has not been optimized to handle lower voltages as well as the newer CPUs do. These new CPUs are capable of doing that and the level of optimization translates into cooler temperatures and better battery life without sacrificing too much stability or performance. The N4's CPU is weak, tired and seriously outdated. It's like a grandpa that refuses to die and still has a bit of muscles left on the "arms". Just like Arnold Schwarzenegger and his soggy muscles.

I hope you understood my analogy.
[Nexus 4 Android Development] bart.found:
Instability could happen only if you undervolt too much! I can say that my old Mako is still smooth and stays cool!

I never reported weird behaviour if I respect its voltage limit.

It, unfortunately, heats only if I use simultaneously 3G+GPS and it's probably due to the modem... not to the CPU.

Maybe you'll not save a great amount of battery, maybe your phone will be only "a bit" cooler (I'd say more than a bit), but, if you don't exceed, perfomances and reliability are not affected at all.
[Nexus 4 Android Development] bdasmith:
I've done lots of overclocking PCs....and you can most definitely under clock....you find the lowest stable voltage the CPU will run with. And a cooler CPU means longer CPU life. The nexus 4 CPU....though several years old is not a grandpa.
[Nexus 4 Android Development] mubaidr:
Your whole post is just based on assumptions. The thing it, CPU is just an electrical component, if it did not get enough voltage it will fail. But you completely ignored the fact that most of user reported that they have very stable cpu, after undervolt. Its not brain, it will not get weaken, stop using this analogy.
[Nexus 4 Android Development] tom0769:
OK, just one more note:

as I stated here, anything could happen, when µcontollers are driven out of their specified range. What happens if you flash the firmware of another device in bootloader or pull the battery while flashing?

When you run your preferred rom, you'll never be able to reach fastboot commands, fastboot is only active in bootloader mode ........ normally.

When the cpu drive nuts, program execution could end up anywhere, not predictable. And for the benefit of what???

But anyways, happy undervolting:silly:
[Nexus 4 Android Development] bdasmith:
Sorry....but none of that made any sense.

The CPU only runs code that is fed to it

..that's not dependant on the voltage....if not enough voltage it will only cause a crash.
[Nexus 4 Android Development] zeeBomb:
One more thing guys...what is your preferred CPU governor? I've been using Wheatley for some time and it wonders for me.

On regards on the undervolting controversy... I'm sticking with my original settings from my other post. The extreme one crashes my device too much :(
[Nexus 4 Android Development] TheArt.:
This is extremely interesting. We should research more on UV consequences, because I can't decide who is right and who is not.