yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] mir0o0:
Awesome kernel, Im getting 5min per % SOT, amazing!!

The random reboots seems only to happen when screen is off, maybe when doze kicks in.
[Nexus 4 Android Development] Cristiano Lira:
After a random reboot I'm having so much lag.
[Nexus 4 Android Development] isaias1983:
Hello.

I just installed this kernel in latest ressurection remix 6.0.1 and i got strange colors everywhere.something like inverted or negative colors i can say...is something wrong with the kernel?cause before install rom rr was good.
[Nexus 4 Android Development] dragos281993:
It's because you flashed the wrong version. As I remember, RR is a CM based ROM meaning that it requires the CM version of the kernel. You flashed the AOSP build so that's why you got weird colors.
[Nexus 4 Android Development] isaias1983:
Just found the solution.thnks for the answer.u were right!
[Nexus 4 Android Development] manpildo:
Tried your recommendations, but the phone doesn't boot after flashing quanta v11 on a clean-flashed Pure Nexus. Nothing happens when rebooting, the screen stays black. Help :crying:

EDIT: fastboot flashing rom's boot.img didn't help, boot process stays stuck. Dirty flashing rom now.

EDIT2: Dirty flashing worked. Solution needed for Quanta.
[Nexus 4 Android Development] zaclimon:
I'm curious. Could somebody send me a dmesg and a logcat of their device while it is booting? I don't remember changing anything that could really alter booting process...

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] mohsinkhan35:
Flashed it yesterday, my phone rebooted twice during a call. For now I reverted back to v10
[Nexus 4 Android Development] dragos281993:
"Clean-flashing ...didn't work". I just don't understand why for me and zaclimon everything is working without problems and for you and other guys doesn't. We must do something right I suppose.

For instance, for me a "clean flash" looks like this: system + data + cache + dalvik cache wipe and the I delete folders from internal storage/ Android, just in case.

Then when flashing part: Pure Nexus CMTE + Banks Gapps + SuperSU 2.67 + Quanta v11 + Viper|Atmos SB 4.6. At the end I did a cahce + dalvik cache and rebooted to system. > I don't restore any data in twrp. < I suspect this is the main problem for most users. What I do instead is backup all the apps and their data with Titanium Backup Pro before any major flashing process, then after the phone boots up after I flashed all the files, I restore all the apps without their data, at first, and then I restore only the app data that I absolutely need.

This is how I do things every time and haven't had a single problem. Basically my way is the proof that, if done properly, everything should work like a charm.
[Nexus 4 Android Development] manpildo:
Well well, it seems wiping caches after flashing quanta did the trick, it's reached the bootanimation now. It is weird because I remember reading that kernels and cache have nothing to do with each other so it shouldn't be necessary to wipe.
[Nexus 4 Android Development] dragos281993:
The caches don't have anything to do with the kernel, but the kernel is bound to the ROM and the ROMs is bound to the caches so they're pretty much working together. But keep in mind that wiping the cache partitions is recommended to be done after every flashing process, something like flashing a kernel, or dirty flashing a ROM, etc. It's something that assures that stuff will work properly when the phone boots up.
[Nexus 4 Android Development] xenyz:
[MENTION=4217103]zaclimon[/MENTION] I tried out v11 and had the same null pointer exception as the other user who posted the logcat.

I can reliably cause Quanta v11 and Taurus R41 to reboot by launching Kodi. Is it possible it's the toolchain? Perhaps upload a test build with a not so bleeding edge toolchain?

I hope you can figure it out, as it's interesting running a kernel sans-hotplug. :)
[Nexus 4 Android Development] dlfollmann:
I'm using PureNexus (latest layers build) and Quanta V11 and, so far, not a single issue. Looks more stable than stock, and also faster and smoother.
[Nexus 4 Android Development] jer_ying_fd:
I use fastboot -w update to clean flash. However, I flashed quanta first before flashing supersu. I also only restore backup by dragging DCIM, Download, Music, and Whatsapp folder back into /sdcard.
[Nexus 4 Android Development] dragos281993:
Sell, I can only assume that fastboot - w doesn't do such a great job. You at least try to use my method. I forgot to mention that I'm using twrp 3.0.0.0.
[Nexus 4 Android Development] tom0769:
Io scheduler always defaults to noop after reboot.

Using v10 with latest app.
[Nexus 4 Android Development] axsdenied1:
Not sure if it was my fault or not but I thought I should report this anyway as v11 was quite a big update and someone else may have a similar issue.

I just had SOD (black screen when I tried to unlock the phone, needed to hold the power button to get the phone to reboot). Running v11.

I have been using Quanta since v4 ( I believe, it was a while ago). I had SOD only once before, long, long time ago. The phone is undervolted but it has been for long time (6 months?) without any issues. No logs as things have been working PERFECTLY so far (great work!!!).

As I said it may be caused by undervolting. I will remove undervolting and see how it goes.
[Nexus 4 Android Development] manpildo:
Is it normal that 4 cores are always online? The battery is draining like crazy when the screen is on.
[Nexus 4 Android Development] jer_ying_fd:
4 cores always online is normal, but battery draining like crazy is not normal.
[Nexus 4 Android Development] dragos281993:
They are not always online. You'll see that they work at low frequencies then go up when needed. It's how touch boost works.

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

I still got 3 hours 44 minutes SOT, so for me the battery drain is in the same range as with other kernels. Definitely not "like crazy".
[Nexus 4 Android Development] jer_ying_fd:
I didn't say that
[Nexus 4 Android Development] dragos281993:
Your previous comment says otherwise.
[Nexus 4 Android Development] jer_ying_fd:
I was quoting the other guy, and i said battery drain is not normal, which means there's nothing wrong :P
[Nexus 4 Android Development] dragos281993:
Oh, got that. Sorry !
[Nexus 4 Android Development] jer_ying_fd:
No worries! :D
[Nexus 4 Android Development] manpildo:
Even if they are working on low freqs, they are still online. I know the principle of touch boost, it's always been a hotplug or governor feature, do I understand correctly that hotplugging has been removed now? Is this a good idea on our makos?
[Nexus 4 Android Development] jer_ying_fd:
With hotplug, it has to calculate how many cores to hotplug and what the frequency of the newly online cores should be. Our chip uses all 4 cores quite frequently, and constantly going online and offline takes up considerable power as well, which is why hotplugging is removed now.
[Nexus 4 Android Development] zaclimon:
Keeping the hotplug would just use more battery because cpu-boost step up/down the cores frequency more often. (Which is also why I leave all cores online) Also, yes the hotplugging has been removed but this is why I went ahead and tried to optimize interactive to find a good balance alongside cpu boost.

Now what do you define a battery drain because my my usage and some others say otherwise.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
The phone seems snappier this way, at least from my perspective, and I get basically around the same SOT with pretty much the same usage. So for me everything is great.

Edit: I really like how we revived this thread. It's nice to discuss, contradict, etc.
[Nexus 4 Android Development] manpildo:
Actually I'm gonna let it settle some time, just did a clean install yesterday so drain is bound to be bigger in the beginning.
[Nexus 4 Android Development] dragos281993:
Yeah. That's right. After a complete charge-discharge cicle, your battery will show better statistics. I once had 2% juice left after a clean installation of ROM, etc, and when I rebooted to recovery, it was at 17%. But then I used it until I completely drained the battery, then charged it to 100%, and it started showing the correct percentage.
[Nexus 4 Android Development] manpildo:
I must say, the combination between Pure Nexus and Quanta is super smooth. It could be because of a fresh clean install, but I'm giving Quanta the benefit of doubt here, because I have never used a kernel with such configuration before. Let's see.. btw, no random reboots for me so far. Also big thanks to dragos for mentioning ViPER4Atmos Sony Beats, I didn't know such a thing existed and I didn't think it's even possible to pimp the sound up even more, but here it is :D Any reason why you recommended version 4.6 over 5.3 though? 5.3 uses the newest V4A natively compatible with Marshmallow and so far I have no problems.

Btw, dragos, I recommend you change some kernel audio settings too for even better listening experience. I attached a screenshot of my little tweaks, in FauxSound app it is equivalent to "quality" profile and imo the result is even better, louder and cleaner sound (especially bass performs better at higher volumes).
[Nexus 4 Android Development] dragos281993:
Viper Atmos Sony Beats 4.6 uses the previous driver and it's better than the latest one, the dev agreed too. And it's more stable and doesn't give you any static noise. I already fiddled with the sound to make it perfect. I also use 2 equalizers on the laptop. I'm a sound greak. Lol. I tweaked the presets from the V4A app's equalizer and also from the Dolby Atmos app. I don't use the kernel's sound control because I've got all I need in both apps. The sound is completely different and 1000% better than the stock one.
[Nexus 4 Android Development] manpildo:
Interesting, I do have experienced some cracking. Will try 4.6, cheers. Btw I'm also a sound geek, it all started with hacking an old Sony Ericsson walkman dumbphone :D Been rooting phones since smartphones weren't mainstream *cough*hipster*cough*.
[Nexus 4 Android Development] dragos281993:
You'll need a system wipe + reflash of the ROM + kernel, then flash 4.6.
[Nexus 4 Android Development] NTLinhHaHa:
Yep, same settings from V10, with undervolting to -150mV, cap CPU freq at 1026, GPU freq to 200, governor interactive, noop I/O scheduler, and the phone now auto reboots 3-4 times a day... It was stable at V10, but reboots itself on V11.

Btw the app works well when I stay in the app. As long as I quit the app (when the launcher appears), a "Quanta Tweaks has stopped working" window appeared :P settings are still saved properly though.
[Nexus 4 Android Development] manpildo:
Thank for the heads up. Gapps are backed up?
[Nexus 4 Android Development] dragos281993:
Oooooo ! What ?!!! - 150mV ?! No wonder you get reboots. Even if in the past you had it stable, stuff changes and the CPU weakens in time. It's hasn't been given the stock voltage for no reason, you know?

Here's how undervolting works. I'll do an analogy. Let's say that the CPU is the >human brain< and the voltage is the >air< that particular person breathes. When you undervolt the CPU, it's like you're choking that person and limit the supply of the air that needs to get to the brain. "Choke" him to hard and the brain will basically suffocate and the person will pass out/faint. That's what you're doing to the CPU at the moment. It's like you're refusing to feed the poor CPU. You're limiting the supply of power for it to operate properly. I've seen a lot of users complaining about this kind of stuff and it turned out they undervolted more than 100 mV. Try NOT going further than - 50mV and see how it goes. Also, not all Nexus 4s can take the same amount of undervolting. I always got a random reboot if I went further than -75mV, so chips are not completely identical.

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

No idea. Try NOT flashing them, reboot the phone and see if they are backup up. I haven't tried to see if they are backup up yet, so I'm curious to sit they are. Keep me posted.
[Nexus 4 Android Development] arjundas86:
You shouldn't take for granted that same settings from V10 will give same output in V11. It's a considerable change in processor management. Undervolting by 150mV is a risky move to begin with, and stability should not be assumed. The fact that it worked in V10 was more of an outstanding occurrence than the norm. You're throttling the CPU as well as starving it, then when you ask it to perform intensive tasks, you shouldn't be surprised that it fails sometimes.

Anyway, my point is, V11 has made significant changes, so you should start from the stock settings of this kernel and try to decrease frequency and voltage in small steps to find your new operating threshold.
[Nexus 4 Android Development] NTLinhHaHa:
Well I spent a month figuring out my spot for UVing :)) I've been running at -150 mV for nearly a year now, and when I first tried undervolting, I realize my phone can handle at -175 as well.

Well guess I have to decrease the amount now, or maybe I should stay at V10 :)) my only priority is battery time, performance is not my concern, so I'm happy with my settings :P

---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------

By the way, the phone now reboots when at idle state, so I began commenting here :p I've been running smoothly with cameras and Youtube 720p (all normal-high CPU tasks) for months, getting no random reboot, so... :'P
[Nexus 4 Android Development] emraz786:
How do you know the bin my nexus, if nominal, fast, faster or slow?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
Undervolting is not meant for power saving, my friend. It's meant for the CPU to run cooler. If you want battery life, reduce the max frequency and the touch boost frequency also. The CPU will get damaged over time. Try asking an engineer about this and you'll see that undervolting that much is absolutely not recommended.
[Nexus 4 Android Development] manpildo:
Yeah, the risk-reward relationship between high undervolting and possible drain gain is not worth it. I myself, on fast bin, go down -50 mV and that's enough to keep some heat in.
[Nexus 4 Android Development] NTLinhHaHa:
My phone did get hot after I bought, so I did the undervolting.

Thanks for your advice anyway. I will change my settings accordingly :D
[Nexus 4 Android Development] dragos281993:
If it were up to me, I'd limit the undervolting capability to maximum -50. That's a good spot, but man... -175 ?! I dare you to speak about this in other threads and even threads from other devices and I assure you people will say that you're insane and you got balls for doing that, tbh.
[Nexus 4 Android Development] NTLinhHaHa:
By the way, I am practically new to the CPU boost section of the Quanta Tweaks app. What settings do you guys use for input boost duration, boost duration, and specially, sync thresold :-?

---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------

As much as I remember, there was a terminal "code" you should type in and it returns the value. Try Googling about it, find the guides about installing the terminal console and type in some codes, and that's what you should look for.
[Nexus 4 Android Development] dragos281993:
Zaclimon tweaked this kernel as best as he could, for the best performance and battery life at the same time. It's the best balance. I only increased the input boost frequency from 918 MHz to 1026 MHz. And that's it. I suggest you try using it with default values at first, monitor everything and after you've gathered some statistics, you can try decreasing the maximum CPU frequency at first and then other stuff. You have to have a "base" that you can compare other tweaks to. And also, from a 2100 mAh, you can't expect to get more than 4 hours with decent usage cause it's not possible. Those that got over 4h SOT, did only light usage on their phone. Not even the newest phones with the best power managed CPU and huge batteries can't get to much. It's just how it is. Even the Nexus 6P gets around 4.5-5 hours SOT and that phone has a 3450mAh battery. So we have to be realistic.
[Nexus 4 Android Development] TheGrinder77:
I'm at -150mV with V11 as well and I've never had a single problem or random reboot.. And battery life is awesowe!
[Nexus 4 Android Development] NTLinhHaHa:
Well there's an issue here. The I/O scheduler doesn't set after reboot. I can't set it to noop, after every reboot it changed itself back to deadline.
[Nexus 4 Android Development] manpildo:
On KK I got some amazing SOT, record being ~8 hours, 4 was average. And it wasn't light usage, meaning I played games, surfed the web etc. Kitkat, Purity KK to be precise, was by far the best in terms of battery life and stability. Lollipop+ got too power hungry.
[Nexus 4 Android Development] manpildo:
It was a very bad idea. Now my phone is wholly corrupt, full of raging FCs, and I must make a clean install again because naturally I was too lazy and arrogant to make a backup... fml.
[Nexus 4 Android Development] jolas:
[MENTION=4217103]zaclimon[/MENTION],

Have you any news about the reboots problem? :o
[Nexus 4 Android Development] dragos281993:
Try not to do backups in twrp. It happens to cause problems. Try backing up your apps and data with Titanium Backup Pro. I can send you a link to a good TB pro apk if you want. That way you can do a clean wipe every time you have to flash something important and then after flashing all the stuff, you can quickly boot up the phone cause it doesn't go through optimizing a ton of apps, and then, while the phone is on, you can restore your apps and their data and the great part is that you can use your phone during the restore process. This is what always do and it may be one of the reason I don't have any problems while booting up, etc.

Edit: I know now why you get FCs after a system wipe. Even if the Gapps are backed up, all the permissions are stored on the system partition, which you wiped. Flashing the Gapps after the ROM basically resets the package's state to stock and all the permissions reconfigure along with the ROM.
[Nexus 4 Android Development] manpildo:
I'm already doing it now, no need for TB apk. It still requires me to tweak system settings like they were before, it's a pain in the arse. Never had problems recovering backups in TWRP either, I don't know what you're talking about. This is just a heads up - don't dirty flash gapps on Pure Nexus, even if you wipe system and caches.
[Nexus 4 Android Development] dragos281993:
When you make a backup in twrp, you back up system apps too. That's what causes problems later on.
[Nexus 4 Android Development] manpildo:
I attempted a second system-wiped flash with gapps following the ROM, but the result was even worse. The first flash without gapps might have screwed it up, but I wouldn't try it again either way.
[Nexus 4 Android Development] dragos281993:
Whats screwing everything up is the data from the data partition.
[Nexus 4 Android Development] manpildo:
Yeah, that's why it requires a full wipe. Gapps problems are a *****!
[Nexus 4 Android Development] dragos281993:
I'm telling you, if you try it my way, you'll never ever have a problem when flashing stuff. But it's your choice.
[Nexus 4 Android Development] manpildo:
I'm sure, but I promised to try a semi-dirty flash to check if gapps are backed up properly. Now we know. Anyway, enough of the gross OT :P
[Nexus 4 Android Development] dragos281993:
Well, it's not really OT. Do this procedure to check if the Gapps are backed up then after you finish everything up, start using the phone with Quanta v11 and basically "give it a spin", or at least a few hours of testing, with no undervolting, of course, or at least not anything as crazy as -150mV.
[Nexus 4 Android Development] emraz786:
because to me it is me like butter and very good consumption, no lag nor resumed

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] manpildo:
Naah, I got viper 4.6 and now I'm settled on pure nexus with quanta, can't be bothered to waste time on flashing anymore. I'm not a raging flashaholic I used to be. I'll allow you to try it though :p
[Nexus 4 Android Development] dragos281993:
Ha! So was I. I used ro flash cm12.1 nightlies every day, with both caches wiped every time.
[Nexus 4 Android Development] roi14:
I can't believe it!!! I'm the first one to download V12???? Is it real [MENTION=4217103]zaclimon[/MENTION]!? hahaha, anyway, thanks a lot! gonna try this!
[Nexus 4 Android Development] zaclimon:
Ohh well, thanks guys for reviving the thread that was a little silent! XD I knew about the random reboots problem since a bit but I wanted to give the faulty component a last chance. It didn't pass so let's remove it.

V12 (21/02/16):

- Reverted Nvidia'a relaxed power settings

- Misc improvements/fixes

Both builds available on BasketBuild. Just a regular flash should do.

Also QT got updated to 4.1.3 as well with the following:

- Fixed FC's when exiting

- Fixed restoring I/O schedulers on boot

- Fixed Ext4/F2FS converter

I wiped my device without any backups beforehand whilst getting this done so I hope there won't be any problems now XD.

It should be available in the next hours in the Play Store.

Well well well, looks like [MENTION=4103048]roi14[/MENTION] announced the release before myself! :o

Enjoy!! :)
[Nexus 4 Android Development] emraz786:
[MENTION=4217103]zaclimon[/MENTION], ¿You can be installed above or wipe to do?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
Thanks, man ! Now this latest version sounds like a real beast, just like the engine found in the gorgeous Aston Martin DB9.
[Nexus 4 Android Development] roi14:
you can never beat a pro stalker! hahaha! cheers!
[Nexus 4 Android Development] zaclimon:
No wipes are necessary. Though it may vary as it looks like not every device is made the same.

Geez, this kernel is nowhere near that. That said, I would like to thank [MENTION=4493540]TheArt.[/MENTION] that pointed me to this guide made by [MENTION=5886947]soniCron[/MENTION] here:

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

This is why I was mostly able to optimize further the Interactive governor found in V11/V12. :p
[Nexus 4 Android Development] :
Random reboot :(
[Nexus 4 Android Development] dragos281993:
Then you need a clean install. If you've this far, and I mean you tried a custom kernel, you know that if something is not right, you're gonna have to do a clean install.
[Nexus 4 Android Development] zaclimon:
Wait a minute, I could have been drunk somewhere..
[Nexus 4 Android Development] str3tch72:
Can You give me optimal touch boost values? :)
[Nexus 4 Android Development] NTLinhHaHa:
Wait what, you can do THAT?!

Oh wow.
[Nexus 4 Android Development] zaclimon:
Ok guys I've reuploaded V12. I included some patches that I shouldn't... If you still have random reboots, well I don't know what to say lool...

Sorry for the back and forth.

What do you mean by optimal values? The absolute optimal or mine's? I don't know for the first option but you can check in QT for mine's. It's nothing really. The boost I've put is only to kick up a little bit the CPU before the governor can handle the rest.
[Nexus 4 Android Development] str3tch72:
Okay, I will play with it, thanks! :D

Reflashed V12 reuploaded kernel, I will see about random reboots. ;)
[Nexus 4 Android Development] emraz786:
I changed the partitions f2fs, but the system partition remained in ext4

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
Yes, of course. That's because the ROM needs some "manual intervention" to be able to stay on f2fs. However, having the system on f2fs won't give you any improvement, except for maybe some errors. "Data" and "cache" are the most used partitions. Everything that's happening on your phone, is happening on these 2 partitions. So you're fine.
[Nexus 4 Android Development] emraz786:
¡thanks for the clarification!

Enviado desde mi Nexus 4 mediante Tapatalk