yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] dragos281993:
Ok, I didn't have time to leave a comment earlier but I noticed some people felt either offended that I called our Nexus 4 a grandpa, or to even stop using the analogy that I previously used. The thing is, those that are INCAPABLE of understanding my analogy, should just chill out and basically don't reply to me, at least until they fully get it. My point of view makes total sense if your "CPU" can successfully process my comment.

So to clear things out, what I said was a piece of advice which you can take for granted or simply ignore. You can do whatever you prefer to your device because it's yours. You can undervolt as much as you desire. No one's stopping you.

Listening to other overall unprepared users that say that a certain undervolting value, like -200mV, is completely stable, is wrong and should not be encouraged. But you can do it anyway. Different users use their phones in different ways, obviously. If user X didn't get a problem at a specific value, that doesn't mean everybody else will have the same results. It's VERY unlikely. Different users do different things on their devices and that means a different impact on the CPU for both sides. Even 2 CPUs that share the same name are not identical. Some can take -150mV, others can barely do -90. The silicone is different. Ordinary users have very little experience UNLESS they do their homework. Usually, only professionals can tell if these sorts of things are right or wrong, but those who heard their opinion are able to give a little advice to others.

You'll find below the opinion of a chip designer, whose point of view and expertise you can't contradict, simply based on his 14 years of experience. READ CAREFULLY (even twice if needed cause the whole thing is VERY interesting and explicit).

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

PS: Sorry for the OT, Miles ! I felt like this was needed.
[Nexus 4 Android Development] zeeBomb:
The perfect post... Thanks dragos. I have taken your post in consideration and I believe I went a little to brazen with that extreme undervolting from applesans post. I mean...I was crashing all the time when I flashed chroma ROM! Thanks for all youve taught me man...you make a great mentor to the inexperienced ones :)
[Nexus 4 Android Development] Applesan:
here some interesting articles:

The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC

How Undervolting Decreases Heat & Increases Battery Life

Is undervolting over-rated?

we can see that power consumption is depends on second power of voltage. therefore when I use my phone it is quite colder with undervolting, than without it.
[Nexus 4 Android Development] zeeBomb:
Read that a while ago...love anandtech with their credible andc informative articles! By the way what ROM are you using? Any changes that you did with the voltages? Any tweaks? CPU governor?
[Nexus 4 Android Development] Applesan:
I use latest nightly AICP Rom and I have only my own Synapse config, no other tweaks. CPU governor is Interactive, and GPU voltage is 900 mV on voltages 1-3.

of course I lose some performance, but for my tasks (web browsing, chatting, calling) performance is enough.
[Nexus 4 Android Development] zeeBomb:
Damn. Im surprised its stable enough for you to use haha. Never encountered such undervolting that seems awesome at first, then falls apart (for me) in the long run.
[Nexus 4 Android Development] bart.found:
[MENTION=5796730]dragos281993[/MENTION] I agree with you (almost) totally! Every CPU is different, actually, CPU binning says this.

Looong time ago, with KitKat and Franco kernel, I read a very interesting guide about undervolting, and did it properly! I tested (with stability test) every single frequency lowering it's voltage by 25mV steps till I got a reboot, finally I raised latest stable values by 25mV... At last I raised even more the voltages of those frequencies that was causing crashes and kernel panic.

Obviously, as ever, there's a right way and a wrong way to do it! You can't simply copy an undervolt table from another user as [MENTION=7179560]zeeBomb[/MENTION] did! But if you do it properly, you'll not have any stability issue, I can confirm this.

;)
[Nexus 4 Android Development] Applesan:
it is really stable for me, no one reboot for a long time. proof in screenshot below.

I completely agree with you :) tables are completely unique to each device.
[Nexus 4 Android Development] zeeBomb:
Great. Thank you for you guys for teaching me so much. By the way, other than hells kernel, this one is the best I've used up to date. Great stuff txuki :good::highfive:
[Nexus 4 Android Development] dragos281993:
R43 on the way. Testing it right now.

New stuff added. People will be HAPPY.

i'm shutting up now. I already divulged too much.
[Nexus 4 Android Development] zeeBomb:
Haha that's awesome. Take it easy man. (btw is there any way to "scrap" posts so I can read later?"
[Nexus 4 Android Development] quentin2260:
Hi dragos ! Do You use Taurus (r42) instead of Hells for daily usage ?
[Nexus 4 Android Development] dragos281993:
What do you mean? If you have Tapatalk installed, and subscribe to the threads that you like, you'll get push notifications whenever a new comment is posted. If you decide to read them later, they'll stack up and when you finally decide to start reading them, when you click on one, you'll be sent to the first unread one.

Bjt maybe you already knew that.

---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------

Yes, on my primary ROM. On the second ROM I have hellspawn installed at the moment. I recently redid my setup this way.

I have always loved Taurus because it gives me the best amount of features that I like + good battery and also great performance.
[Nexus 4 Android Development] quentin2260:
Your primary Rom = Pure Nexus ?
[Nexus 4 Android Development] dragos281993:
Of course. Primary: PN (Layers) + Taurus r43 (testing now as I previously mentioned), and Secondary combination: PN (CMTE) + hellspawn.
[Nexus 4 Android Development] txuki2005:
I'm thinking of adding the ZRAM, zCACHE and Zsmalloc our nexus 4. What think? It is necessary?

:P
[Nexus 4 Android Development] dragos281993:
I believe people will like having something new implemented. Let's see how compressed RAM and Cache behave on our N4.
[Nexus 4 Android Development] txuki2005:
Maybe more CPU usage...so more battery drain??

I have to think about it.
[Nexus 4 Android Development] dragos281993:
Having 2 options would be "safe": a normal Taurus kernel build and another version with Zram, Zcache, and Zmalloc. Our Nexus 4 is a bit "picky" when it comes to new stuff, so it might be a good idea to have there a stable backup option.
[Nexus 4 Android Development] ivanich:
Zram is needed only on devices with low ram 1G or lower, mako have 2G which is enough for Marshmallow, however zram consumes more cpu cycles to compress ram pages.

If you going to add it please set it disabled by default :)
[Nexus 4 Android Development] arjundas86:
I second this opinion/request.
[Nexus 4 Android Development] mubaidr:
I don't think it is necessary, or worth the effort considering the fact that 2gb is enough ram.
[Nexus 4 Android Development] txuki2005:
Okay, not zram....

Thanks!!
[Nexus 4 Android Development] zeeBomb:
ZRAM? What's that and what's its main use for?
[Nexus 4 Android Development] tom0769:
ZRAM means compressed ram, something like a swap partition in ram.

This could be used for low ram devices to get better multitasking.
[Nexus 4 Android Development] zeeBomb:
Oh OK. I wouldn't see that as a problem on the nexus! Any compromises on using it? Enabled by default?
[Nexus 4 Android Development] tom0769:
Read a few posts back, [MENTION=4329165]ivanich[/MENTION] explained it, [MENTION=5311064]txuki2005[/MENTION] will probably not implement it.
[Nexus 4 Android Development] Applesan:
We are looking forward new kernel :fingers-crossed:
[Nexus 4 Android Development] quentin2260:
Hello ! I have a lot sleep of death on my N4 with PureNexus. I flashed kernel over stock and clean cache dalvik.

I don't have kernel tool apps like kernel adiutor.

Sometimes my phone take a moment to wakeup.

Did you know what cause SoD and how can prevent ? Its very annoying for alarm clock.
[Nexus 4 Android Development] dragos281993:
I experienced something like that when I tried "Naptime" from the Play Store, which is meant for fiddling with Doze. Uninstalling it didn't fix the delay.

So, Reboot into recovery, clear cache + dalvik cache, dirty flash the ROM, then the kernel (+ other stuff, if you're using something that's written on the system partition and gets removed when you dirty flash the ROM), clear cache + dalvik cache again, and reboot to system.
[Nexus 4 Android Development] quentin2260:
Did you know what it sod ? Its very strange bug. I always clean récent apps before lock screen but its completly random bug. I remember sod didn't exist on 5.1.1 Android system

Its custom kernel fault or marshmallow bug ? I just want to know if sod exist on stock purenexus kernel.
[Nexus 4 Android Development] dragos281993:
I didn't experienced any. SODs no matter what kernel I used. Only that delay, and that was only once. So something external is causing it, which means it's something on your part. Try doing what I said in my previous comment. You won't lose any data cause the only things you'll be wiping are the cache partitions. Dirty flashing your ROM doesn't wipe anything, and only restores the ROM to the stock state. That's why you need to flash the custom kernel again, right after the ROM.
[Nexus 4 Android Development] quentin2260:
Thank you for your explanations !!

Do you think if Xposed can cause SoD ? I have modules installed (amplify, greenify,volumesteps+).
[Nexus 4 Android Development] dragos281993:
That would be the main culprit. A lot of users had a ton of problems on Lollipop, then Marshmallow was launched and the few months Xposed wasn't compatible with M, users didn't report major bugs, and then, when Xposed had finally been made to work with M, users started experiencing all sorts of problems. It's how it is though. Note that there are developers that specifically warn users that they won't be responsible for bugs and errors experienced by those who are using Xposed.

But yeah, most probably minimum one of the modules you're using, caused you problems.
[Nexus 4 Android Development] quentin2260:
So what app can i use to control and block wakelocks without using xposed ?
[Nexus 4 Android Development] dragos281993:
What do you mean ? Did you use Xposed to block wakelock till now ? Aren't those modules for something else, like extra functionality ? The wakelocks occur randomly and are caused mostly by apps. The fixes consist of either a phone reboot or a data wipe of that particular app that's causing the problems. In order to monitor the apps' activity so you can find out what is causing a wakelock, you'll need BetterBatteryStats, or something similar. The app will gather stats and you'll need to look how much time your stayed awake with screen off. If the time is exaggerated, you'll need to go to the "Kernel wakelocks" section and after that, to the "Partial wakelocks" section. That's where the apps that are causing wakelock are.
[Nexus 4 Android Development] quentin2260:
Before I used Amplify module to block some wakelock. Betterbatterystats cannot block wakelock its just show stats. But now since I uninstall Xposed and all modules, screen wakeup is fastest than before. So betterbatterystats is only app installed on your phone to get good battery life?
[Nexus 4 Android Development] dragos281993:
No, BBS only shows the stats so you know what might be causing a wakelock. Didn't know that Amplify blocked wakelocks, as I've never used Xposed. What wakelocks could you block with this module ?
[Nexus 4 Android Development] quentin2260:
I dont remember but its like 'Nip....' sometimes like that
[Nexus 4 Android Development] tom0769:
I used Amplify in KitKat.

With Amplify (donnate version) you could block all wackelocks, alarms and services separately.

As BetterBatteryStats it detects all services and processes, that cause the cpu to wake.
[Nexus 4 Android Development] arjundas86:
I used to use Amplify back in LP, but once I moved to MM and started using Doze Settings Editor, I found that I was getting similar battery life without Amplify as I did in LP with Amplify.
[Nexus 4 Android Development] quentin2260:
What settings did you use un Doze ?
[Nexus 4 Android Development] arjundas86:
inactive to	180	s

sensing to	60	s

locating to	30	s

location acc	20	m

motion inactive to	180	s

idle after inactive to	60	s

idle pending io	180	s

max idle pending to	180	s

idle pending factor	1

idle to	3600	s

max idle to	14400	s

idle factor	2

min time to alarm	900	s

Max temp app whitelist	600	s

MMS temp app whitelist	60	s

SMS temp app whitelist	20	s

Everything else default.
[Nexus 4 Android Development] quentin2260:
Did you try Arstoien settings on official Doze thread ?

http://xdaforums.com/showpost.php?p=63943171

Some users say its ultimate setting.
[Nexus 4 Android Development] arjundas86:
No, I just got the app and set it according to my preferences. I did read through his settings.

Feel free to try Arstoien's or my configuration; however, I feel that you should always understand the impact of each setting rather than blindly following someone else's configuration. Your needs and overall preferred phone behaviour might not be the same as his or mine.
[Nexus 4 Android Development] zeeBomb:
That I needed to know. Bookmarked! Ty!
[Nexus 4 Android Development] jacomail95:
Can be considered the new lazyplug a good experimental feature in a R43 release? That is, if you want to add it. Feedback seems positive about it :thumbup:

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] :
CM13 new build and Taurus MR1 R42 has a problem with the display settings. The program crashes. Using the default kernel CM13 this problem does not exist.
[Nexus 4 Android Development] txuki2005:
I will check it for future releases.
[Nexus 4 Android Development] txuki2005:
Display settings? Maybe DTI ...my kernel not use that. I dont like cyano...so for the moment i will not check it,maybe...on the future. For me AOSP roms are better than CM.
[Nexus 4 Android Development] :
txuki2005--- what rom AOSP you recommend?
[Nexus 4 Android Development] dragos281993:
Try Pure Nexus. It's hands down the best one, even of it's Unofficial, and despite the fact that the devs don't officially support our N4, they're gonna help you if you ever need help. And you can also do feature requests.
[Nexus 4 Android Development] txuki2005:
Purenexus or chroma. For me, pure better than chroma.
[Nexus 4 Android Development] txuki2005:
https://github.com/txuki2005/TaUrUs_Kernel/commits/taurusdev
[Nexus 4 Android Development] chaostrodamis:
Can't wait
[Nexus 4 Android Development] quentin2260:
Hello ! I found the item causing SoD : Xposed. Now never SoD or slow wakeup.
[Nexus 4 Android Development] jacomail95:
Probably a module, not xposed itself, i never had a issue with it

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] :
Thank you for your answer . I tested both rom, Pure Nexus is primitive for me and Chroma does not have a full Polish translation.
[Nexus 4 Android Development] Mrcactuseater:
Given that Chroma is mostly a fork of purenexus, doesn't make them both primitive?

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] dragos281993:
I tested a Taurus test build with lazyplug included a few hours ago and the thing is too unstable. The > positive feedback < probably came from users who didn't even turn off AutoSMP and activated lazyplug. The time I test it was like this: I activated lazyplug and as soon as I turned the screen off, the damn thing stayed completely off; instant SOD. Then I decided to try hellspawn kernel, cause that's the kernel someone said they're using with lazyplug activated. What do you think happened ? The exact same thing. So my conclusion is that those users that said that they're using lazyplug as hotplug, don't even have it activated. I gave Miles some log files and he said that this new hotplug doesn't look good at all. As I said before, Spezzi is working on improving it, but right now, activating it makes the phone unusable. AutoSMP is absolutely the best option at the moment.
[Nexus 4 Android Development] Mrcactuseater:
100% agree that AutoSMP is the best. It's very smooth and very effective at managing the phone. [MENTION=4203114]mrg666[/MENTION] made a great hotplug!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] Razorfoot:
Guys is android file host unaccessible for you too? I can't download the R42 for CM roms :(
[Nexus 4 Android Development] dragos281993:
They're working on it. The whole data has been transferred to Google cloud.
[Nexus 4 Android Development] Razorfoot:
Dragos would you have a copy of it to share? I really need to test this CM rom before the week begins!

[MENTION=309187]edit[/MENTION]

it just got back online! yay
[Nexus 4 Android Development] dragos281993:
Unfortunately I don't. I stopped using CM or cm based ROMs a long time ago. You should just ask this question in all N4's "crowded" threads. Someone has to have the file.
[Nexus 4 Android Development] Applesan:
It works fine. I have downloaded R42 for CM roms now.

There is some interesting features on hellspawn kernel:

[MENTION=5311064]txuki2005[/MENTION] what do you think about it? Is it necessary for Taurus kernel for better battery life? And what about updating ondemand code to Linux v3.18?
[Nexus 4 Android Development] txuki2005:
be quiet... still testing. I like stratosk ondemand... for me it is the best ondemand for our old N4, so its not necessary to update.

You must remember that now all new android phones use Interactive governor by default.
[Nexus 4 Android Development] txuki2005:
I ran out of time for today. Until Thursday, that is the day I have free at work, I can not continue. I also add the "msm_limiter" but I have to look good to avoid any problems.

See you guys.
[Nexus 4 Android Development] txuki2005:
R43 coming soon....

Finally tested..... and go..... FINE!!

;)
[Nexus 4 Android Development] j2002:
So......
[Nexus 4 Android Development] dragos281993:
So... yeah, r43 looks great. "msm limiter" is awesome. Today I had 4h12m SOT with moderate usage, so... hell yeah !!!

Performance, good battery life, stability, a lot of features, msm limiter, etc, etc, etc. You'll all be very pleased. VERY PLEASED.

:laugh: I already teased you too much. lol.
[Nexus 4 Android Development] mjehan:
Will the May security patches and updates be included in R43 !
[Nexus 4 Android Development] dragos281993:
Those are ROM related patches.
[Nexus 4 Android Development] fr3quency:
loled, you went too far with that. Go back to a Nokia 3310.
[Nexus 4 Android Development] dragos281993:
Ha ha ! I had one. The damn thing refused to die no matter the situation.
[Nexus 4 Android Development] matteus198701:
When you release r43 version? Is it possible in this weekend?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] Applesan:
What is msm limiter? Mobile Station Modem Limiter? What this limiter means? Is it possible to decrease amount of msm_hsic_host wakelock? It is very interesting!
[Nexus 4 Android Development] dragos281993:
The "Msm limiter" limits the CPU in certain conditions such as frequency during suspend, resume and minimum frequency and other scenarios. It reduces power consumption as it limits the CPU frequency after the screen off. Regarding OC, if this feature is enabled, the OC frequency will be overridden after the screen turns off. So you need to disable it if you like to make OC frequency stay.

So it helps the battery life at the cost of very little performance loss.
[Nexus 4 Android Development] Applesan:
This is like "screen off max freq" in other kernels. Does phone have some long wake up time on min screen off freq?
[Nexus 4 Android Development] dragos281993:
It's not only related to screen off. It limits the overall "everything" in some areas. That's what gave me that very good SOT.
[Nexus 4 Android Development] spezi77:
Any benchmark results?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
Sorry, but I never cared about benchmarks. I always tested something "in the field". But I'll do one for you. Tell me what app to use to do the test and I'll do it. I'll do it later, though.

Now I have to vaccinate both my dogs and that will take a few minutes cause the girl is smart enough to not stick around when she sees the needle. lol
[Nexus 4 Android Development] granazis:
After good news for new build a good answer is here.

Cngrts [MENTION=5796730]dragos281993[/MENTION]
[Nexus 4 Android Development] quentin2260:
Can't wait for r43 update !
[Nexus 4 Android Development] dragos281993:
Here's a benchmark result:
[Nexus 4 Android Development] chaostrodamis:
Any idea of a release. Sorry about breaking the rules asking for an ETA.
[Nexus 4 Android Development] Mrcactuseater:
It's still a rule not to ask for an ETA, even if you apologise lol. It'll come when it's ready man

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] spezi77:
You could try to apologize for your rude behavior by making a donation and thank txuki for his hard work! [emoji12]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] chaostrodamis:
Absolutely correct, just want to say sorry to the community for my lack of patience.
[Nexus 4 Android Development] dragos281993:
I'm pretty sure Spezzi was a bit sarcastic when he said that. I don't think it's disrespectful to ask for ETA. Yes, some devs get pissed when people ask them that, but it's not that big of a deal to get an answer, whether it's a vague or a specific one. Sykopompos (my absolute favorite dev) allowed people to ask stuff, as long as everything was said in a respectful manner. I don't want to speak in place of the others though.

As for a new Taurus build, Miles said it should be released soon. He's a bit busy at the moment, so we should be a bit patient. I already have a completely stable test build, but I'm not the dev, so I'm not allowed to share it.
[Nexus 4 Android Development] arjundas86:
Stop taunting ussss! :P lol
[Nexus 4 Android Development] dragos281993:
I'm evil, ain't I ? ??
[Nexus 4 Android Development] txuki2005:
I see good new commits from new Quanta versión, so i will check them on friday, [MENTION=4217103]zaclimon[/MENTION] make a very good work!!

Be patient my friends and i have hard work these days.... :(
[Nexus 4 Android Development] Zero2098:
hello i have taurus r42 and the cpu clock is stuck on 1280 HZ what should i do to fix this problem??
[Nexus 4 Android Development] txuki2005:
Testing new changes.....
[Nexus 4 Android Development] arjundas86:
Agreed. I'm currently on Quanta V15, and it's terrific! Glad to hear some of that work will make it into Taurus R43. Now I'm even more excited to try it. :)
[Nexus 4 Android Development] txuki2005:
Stay sttuned guys!! Today is the apocalypse day!!

;)
[Nexus 4 Android Development] mubaidr:
Awesome!
[Nexus 4 Android Development] txuki2005:
Taurus r43 aosp/cm

R43 CM/AOSP online

Changelog:

- F2FS last updates (Thanks [MENTION=4217103]zaclimon[/MENTION] )

- WLAN updates

- MSM limiter from [MENTION=955548]neob[/MENTION]uddy (use my last UKM to see it)

- Quick Wake UP from motorola

- Adaptive and Barry_Allen new GOvs.

- AUTOsmp by default

- Linux 3.4.112

- More patches for stability and performance

- Compiled with Uber 5.3.X last version

- Settings by default on ramdisk:

- Max brightness 100

- Vibrator amp 70

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

- CPU: 192-1512 ( Overclock to 1.7)

- Interactive Governor by default

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

DOWNLOAD

AOSP

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

CM

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

;)

Special thanks to [MENTION=5796730]dragos281993[/MENTION] for testing it :highfive:
​