yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] DontPushButtons:
V4a is a little bit finicky as far as which music apps it wants to work with and for how long. Sometimes it just decides not to work at all. Also, for a while there (and maybe still), it didn't play nice with koush's supersu.

The kernel sound patches are a lot more useful, as they apply to all sounds since the changes are applied at such a front-end level.

You are of course more than welcome to build your kernel however you see fit, but the patches are much better than relying on something inconsistent like the v4a app, in my opinion.

Just my $0.02. Keep up the excellent work.
[Nexus 4 Original Android Development] mrg666:
Well, thanks for the comments. But I disagree. V4A does more than what the kernel sound patches do. It is a sound processor replacement - kernel patches don't do any sound processing other than gain control. I have been using it since some time and V4A is working great for me. Bass boost, surround, equalizer, gain control, etc are better than stock MusicFX. I haven't seen any of the problems you mentioned. But I only use stock Music app. I also don't agree with adding kernel patches for enhancements that can be done in the user space since anything that bloats the kernel affects all of the system. If there are some apps not working because of that, too bad :)

I was listening "Shine On You Crazy Diamond" while writing this .... sounds awesome!
[Nexus 4 Original Android Development] DontPushButtons:
It is definitely better than musicfx, can't disagree with that. But faux sound is something I find difficult to part with. Especially for the apps in which v4a doesn't seem to want to cooperate with.

It is of course your prerogative, since you build the kernel for your personal use and share it with the community. There are plenty of kernel options with the sound patches, and I appreciate you discussing your rationale for not including them in yours.

Edit: also, just noticed this is in original development. Congrats on the forum jump, always odd to me when some things aren't considered "original"
[Nexus 4 Original Android Development] C4SCA:
the overclocked version only lets me OC to 1.728?

why?

shouldnt it be 1.89?
[Nexus 4 Original Android Development] mrg666:
It was posted here earlier. Thermals were unmanageable above 1.728. I have removed the higher frequencies for safety.
[Nexus 4 Original Android Development] C4SCA:
Ooopps my bad!

im new here,the simplicity of ur kernel caught my eye.

would it be possible to add voltage control? i know that mne can be undervolted to -137.5mV

if not, its not a problem, -100mv is quite good
[Nexus 4 Original Android Development] mrg666:
WOW! you have gem of a cpu in your hands.

Adding voltage control is very easy but it adds 10+ rw parameters to sysfs. Monitoring each rw parameter in sysfs is an additional job for kernel even if you don't change them. So I didn't add that "feature".
[Nexus 4 Original Android Development] C4SCA:
My cpu binning is fast... I think its linked to that :victory:

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (4.3).
[Nexus 4 Original Android Development] THEBANDIT420:
Doesn't mean you will be able to with this kernel I can undervolt - 150 on neo but only - 87.5 on faux.
[Nexus 4 Original Android Development] C4SCA:
I can do -137.5 on matrix and faux. -150mv on semaphore, but to be sure i used -137.5, eventhough i tested palying RR3 with -150mV for 30min and all worked perfect

My voltages are compared to the stock ones by the way

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (4.3).
[Nexus 4 Original Android Development] mrg666:
There is a new build in the OP with many backports from Linux mainline

- block: row: Fix crash when adding a new field in bio struct

- update /dev/random to 3.16.rc6

- net/ipv4 fixes

- arm:crypto update to 3.16.rc6 (ARM: add support for bit sliced AES using NEON instructions)

- several other code clean up

Please see the repo for full details.

There are too many patches in this build but I have tested and didn't see any problems. Please post if you have any feedback.

Cheers!
[Nexus 4 Original Android Development] guimendes:
[MENTION=4203114]mrg666[/MENTION], I'm facing problems with compiling latest version. The error is:

arch/arm/crypto/aesbs-core.S: Assembler messages:
arch/arm/crypto/aesbs-core.S:449: Error: thumb conditional instruction should be in IT block -- `addeq r6,r6,#0x10'
arch/arm/crypto/aesbs-core.S:904: Error: thumb conditional instruction should be in IT block -- `addeq r6,r6,#0x10'
arch/arm/crypto/aesbs-core.S:2100: Error: thumb conditional instruction should be in IT block -- `subne r9,#0x10'
scripts/Makefile.build:343: recipe for target 'arch/arm/crypto/aesbs-core.o' failed

Any ideas? Maybe some new toolchain or some new config.
[Nexus 4 Original Android Development] mrg666:
Try the latest [MENTION=4825437]Christopher83[/MENTION] a15-optimized gcc-4.9-based toolchain here. Thumb specific code is breaking the assembler after the latest patches. Hopefully it will be fixed in the next linaro gcc release. But Cristopher83 has early builds as always. Don't forget thanking him.
[Nexus 4 Original Android Development] guimendes:
Awesome! It worked! Maybe you should update the build post referring to this toolchain.

Thanks!
[Nexus 4 Original Android Development] mrg666:
Great! I am too tired for today. I will update the post before the next build.
[Nexus 4 Original Android Development] xenyz:
Eh, it does say built using the latest Linaro, should be good enough for most. OT, but I'm curious: is there a way to detect which compiler built a binary?
[Nexus 4 Original Android Development] guimendes:
Well, if you use some app like trickstar mod you'll find some info about compiler, but not everything.
[Nexus 4 Original Android Development] mrg666:
You can read /proc/version for the Linux kernel.
[Nexus 4 Original Android Development] Sir_gpm:
[MENTION=4203114]mrg666[/MENTION] love your kernel, can I ask, how do you wake your phone?. I think 2t2w is useful to power button life.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] xenyz:
Another option is Gravity Screen, a really useful app to avoid using the power button entirely.
[Nexus 4 Original Android Development] Sir_gpm:
[MENTION=3118524]xenyz[/MENTION] thanks you made my day.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] mrg666:
I have been using my power button all the time. I don't like touch to wake or swipe to wake hacks. It is very easy to replace the power button if it is broken.

This app is genius! Thanks, xenyz!
[Nexus 4 Original Android Development] Tommy-Geenexus:
Hi [MENTION=4203114]mrg666[/MENTION],

Just dropping in here to say thanks for your awesome work, your git is always worth taking a look at.
[Nexus 4 Original Android Development] mrg666:
Thanks for stopping by. I am glad the repo is useful for you. That is the whole purpose :)
[Nexus 4 Original Android Development] apatal:
Getting really good battery life using latest OC build with Gravity Screen. Thanks!
[Nexus 4 Original Android Development] mrg666:
Is gravity screen causing more battery drain?
[Nexus 4 Original Android Development] apatal:
Not that I can tell. 3.5 hours SOT is my average on stock kernel so anything better than that is a good sign for me. :)
[Nexus 4 Original Android Development] ForMartha:
well,

using FK not increasing the phone standby and screen on time (i'm about 2 hours oh screen on..),

would using this one would make it better?

would be happy to hear from you about it..

thanks :)
[Nexus 4 Original Android Development] mrg666:
I have been testing the following settings in the last couple of days.

/sys/kernel/autosmp/conf/cpufreq_up -> 1200000

/sys/kernel/autosmp/conf/cpufreq_down -> 1000000

These settings will make autosmp less aggressive. It will hotplug the cores later and unplug earlier. At least, I didn't see any noticeable performance degradation. It would be great if you could also test the battery life and performance.
[Nexus 4 Original Android Development] apatal:
I'll be happy to help. Happen to just finished charging completely. Will apply these settings and see what stats I end up with. Cheers.
[Nexus 4 Original Android Development] apatal:
Here's what I ended up with. Conclusion: didn't make much of a difference I think. Not sure how this would go down without Gravity Screen though.
[Nexus 4 Original Android Development] mrg666:
Thanks for testing. My experience is similar with my normal use. I'm not really a gamer, but I will test more with a couple of games and post the new build by the end of this week.
[Nexus 4 Original Android Development] ForMartha:
MRG666, could you please upload IMG files also? (I'm using flashfiy to manage my kernels & backups..)

thanks :)
[Nexus 4 Original Android Development] apatal:
Just extract the boot.img file from the zip using Root Explorer or zArchiver. :)
[Nexus 4 Original Android Development] ForMartha:
thanks :)
[Nexus 4 Original Android Development] Sir_gpm:
Do you mind share your GS setup?
[Nexus 4 Original Android Development] apatal:
Default settings except for disabling "Turn Screen on by Motion".
[Nexus 4 Original Android Development] mrg666:
I have uploaded the new build. The download links are in the OP.

- Linux 3.4.100 and 101

- Many other small updates, please see the repo.

Enjoy!
[Nexus 4 Original Android Development] aviz1911:
I saw many kernels(including me) go with all the features which are out in the arena but the only 2 kernels I know which have limited/useful features and ROCK STABLE are this and semaphore kernel.

Damn I should still learn sooo many awesome things from you. You remember or not The first kernel sources I downloaded from github is yours and I kept messaging you about all non sense. You patiently answered every bit of my questions and taught me so many new things.

Thanks for your awesome work bro. I just wanted to express my gratitude and I did :D
[Nexus 4 Original Android Development] mrg666:
Thanks for the awesome comments too, aviz. I remember you :) I am glad I could help a little.
[Nexus 4 Original Android Development] defconoi:
I too appreciate your work on msm kernel on github, you got some great code, keep up the great work!
[Nexus 4 Original Android Development] TheNerd:]:
I don't know if it is just me, but auto SMP feels superior than the other hot plugs. Even though I have no idea how it works and no idea how to customize it it's awesome battery and performance wise. [MENTION=4203114]mrg666[/MENTION] can you

1) explain how it works

2) how to customize

3) explain the philosophy as to why it's superior to the others

I love i though , and I have no idea why others don't adopt this hot plug
[Nexus 4 Original Android Development] ForMartha:
Just flashed the Kernel - lets see how goes for me - thanks mrg666!

BTW - this kernel got the latest Qualcomm drivers?
[Nexus 4 Original Android Development] jimyiak:
It says f2fs support..can i flash this to all f2fs system??thanks!!

sent by nexy 4
[Nexus 4 Original Android Development] mrg666:
The idea is simply the following, autosmp works as a slave for the cpu governor for efficient and consistent response to power demand. It does not even check the cpu load, just monitors the cpu governor. When the cpu governor ramps up the cpu and gets close to saturating the frequency, autosmp plugs in another core if available. When cpu governor scales back the cpu frequency, autosmp waits a certain number of cycles before unplugging one core if multiple cores are online. It doesn't do anything else and the code is as simple and efficient as I could make it to be, just 305 lines including the comments. I will not claim it is superior to anything else, it is just how I wanted it to be. For customizing, you can check /sys/kernel/autosmp/conf. The parameter names should give an idea about their function.

I haven't added the necessary lines in the init scripts in the boot image. Just flashing the boot image will not work with f2fs system. You need to create an anykernel updater.
[Nexus 4 Original Android Development] ForMartha:
I'm getting crazy with maintaining the Nexus 4 battery - It's been 2:30 hours since i've unplugged it and i'm down to 78%

only 33 min of screen on and the rest is voice calls 32 min.

what do you guys think ?

checked for wake locks - nothings special, also, I'm using greenify (donation) + Xposed + mirage kernel + stock 4.4.4.

BTW - [MENTION=4203114]mrg666[/MENTION] I love it that you didn't touch the volume sound and vibrator, it's too much noisy and with a lot of saturation.
[Nexus 4 Original Android Development] TheNerd:]:
How's your signal and screen brightness? Google now on? Location on? Data or WiFi? Auto sync on?

---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------

Thanks a lot. Well I think it's superior :)
[Nexus 4 Original Android Development] ForMartha:
First of all, thanks for responding.

I'm on 3G (HSPA+) all the time (and when I'm near wifi - it switches to it), sync is on, brightness set to auto, Google now is off, location is off (but I switch it on when needed), and the signal is stable (sometimes it drops but usually it's OK).
[Nexus 4 Original Android Development] TheNerd:]:
Take into consideration that 3G and voice calls use a lot of battery. Don't use xposed and turn on art . Apologies if I sound demanding. Oh and what ROM are you using?
[Nexus 4 Original Android Development] ForMartha:
the only reason I'm using xposed is the quick unlock feature under gravity box & the battery precantage. I've read somewhere that using ART instead of Dalvik dose not effect the battery that much.
[Nexus 4 Original Android Development] TheNerd:]:
Theoretically it does save battery. For some it helps tremendously for others not at all, but it doesn't hurt to try. I personally run art whether it actually works or not. The concept, the philosophy of art makes a lot more sense. My setup is similar to yours : greenify, location off, google now off, auto sync on, but I use art . I don't know what difference it makes , but somehow I manage at least 1hr of screen on time at 78%. So why not try it and come back with your findings. Quick unlock and battery icon are basic features you can find in 99% of the Roms here. I suppose you're using stock but using custom Roms will not one bit affect your experience negatively, but it might (I say might) improve your experience. Hope I helped :)
[Nexus 4 Original Android Development] ForMartha:
Once again, thanks for taking time and answering :)

One thing that I hate with flashing Roms is the obsesst behavior of updating every single week or so, and - as I use my phone as a daily driver (my mobile office) I can't take a chance of malfunctioning app or so. that's why I'm still using stock while modifying the framework using Xposed.

I used to use ART, it works fine but nothing noticeably regarding battery life in comparison to Dalvik.

But, I did noticed that this kernel works perfectly but the phone heats as hell, so - I've decided to move back to franco and undervolt everything.

in addition, dose Ondamend governor supports undervolting ? (I've tired to use trickesterMOD to undervolt, but nothing worked).
[Nexus 4 Original Android Development] TheNerd:]:
Um the CPU governor has nothing to do with undervolting. The CPU over clocked version is undervolted by default though. To be completely honest I think hellscore kernel in the general section will best suit your needs no offence [MENTION=4203114]mrg666[/MENTION]. To continue this discussion how about PM'ing me instead? To avoid further discussion of other kernels.
[Nexus 4 Original Android Development] xenyz:
I use the same setup and if you're on 3G and outdoors (brighter screen) that's about right, especially if you were using data when not on calls. The radio just uses a lot of power transmitting.

Post your battery stats here to be sure.
[Nexus 4 Original Android Development] ForMartha:
I'll fully charge my battery and upload after once cycle - i'll keep everyone posted.

thanks!! you guys are the best.

*Edit* - please see the attached files regarding battery usage. (Btw I'm aware about the bad reception, I'ts not regular issue, but than again. Maybe something else would be useful to assist with finding the root of the issue)
[Nexus 4 Original Android Development] criminalzen:
comments...

hello mrg666.. defconoi has added your autosmp to his kernel which is followed in [L][5.0][PORT] Android L pv-79 Developer preview for Nexus 4 [BETA 4 series] thread. I collected a few comments about peeps reactions to its inclusion in his kernel.. didn't know if they would follow his suggestion to drop by here...

as always thanks for your serious kernel work here.. I notice it spread throughout the gits of nexus 4 kernels... :)
[Nexus 4 Original Android Development] mrg666:
Thank you for reporting the feedback. Looks like autosmp works well in other kernels too. I will take another look at the code now that it is being used in different kernels. Thanks again :)
[Nexus 4 Original Android Development] jmtjr278:
I have a question. I know this is a flash and forget kernel but after flashing and opening trickster I notice mpd is toggled on. In order to use your autosmp hot plug should I disable mpd? Also should thermal throttle be toggled on? Thanks!
[Nexus 4 Original Android Development] mrg666:
There is no mpd in MiRaGE and it can't be toggled on. I don't know why trickster think so but just disregard it. I would actually uninstall trickster while using MiRaGe. Thermal throttle is on by default for safety. Don't disable thermal throttle; it is a must imho.
[Nexus 4 Original Android Development] apatal:
Your work is finally getting the attention it deserves. Well done and keep up the good work. I'm actually using the OnePlus One as my daily driver now and I'd gladly pay to have Mirage on it. Alas, I'd have to make do with it running on my Nexus 4, for now. :)
[Nexus 4 Original Android Development] mrg666:
So how is OnePlus One? Do you recommend it over Nexus 5? I think I am satisfied with the capabilities of Nexus 4 for now, just wondering what is better. I was planning to buy Nexus 5 when it goes on sale before the next model released.
[Nexus 4 Original Android Development] xenyz:
[MENTION=4203114]mrg666[/MENTION] have you tried running with cycle_up 3 (same as cycle_down)? It seems to smooth things out a bit in problem apps (Tapatalk and Play Store noticeably). Battery might take a hit, though, with fewer cores @ higher freq.
[Nexus 4 Original Android Development] mrg666:
I added cycle_up just for completeness as I had cycle_down parameter. Autosmp waits cycle_up cycles after the last hotplug event to plug another core. If cycle_up is more than 1, the delay with plugging a core can reduce the performance. I wouldn't recommend assigning anything other than 1 to that parameter.
[Nexus 4 Original Android Development] apatal:
I think the Nexus 5 is still an excellent device. I was also planning to buy it before an opportunity came for me to get the OPO. I guess I just couldn't pass up the bigger battery and storage for more or less the same price. I just wish I can have someone build me Mirage for it. I don't mind being a tester/thread maintainer. ;)
[Nexus 4 Original Android Development] mrg666:
Developing a kernel without the device is a little hard for me but I could try. OPO is using CM and kernel source should be available in Github, right? Let me give it a shot. Is the OPO ROM available at CM server for download for extracting the boot image?
[Nexus 4 Original Android Development] C4SCA:
As for the rom image, check the end of the page: https://cyngn.com/products/oneplusone/

sent from my diabetic Nexus 4 (too much KitKats).
[Nexus 4 Original Android Development] xenyz:
It looks like 3G modem. The telling part was when your phone was idle and still had significant drain.

Have you seen the xposed module Gravity Box's feature 'Smart Radio'? If your service provider has 2G and 3G coverage, the app can automatically switch it for you.

The only other option I can think of is a battery that has used a lot of cycles and has a lower capacity. Have you considered a replacement?

Another user has suggested trying another kernel, but I doubt you will find better energy usage than with this one.
[Nexus 4 Original Android Development] apatal:
You can also check out the kernel source here:

https://github.com/CyanogenMod/android_kernel_oneplus_msm8974

---------- Post added at 02:59 AM ---------- Previous post was at 02:56 AM ----------

If this works, do you mind if I start and maintain a thread at the OPO forums? I did it before for _thalamus back in my Nexus S days and the setup worked fine for us (he was not very fond of dealing with this sort of stuffs). All credit goes to you of course. :)
[Nexus 4 Original Android Development] mrg666:
It is okay with me if you start the thread. I don't have the bandwidth to be active in too many threads anyway. I will PM you when I have the kernel ready for testing. After your testing, we can post it in the right forum. First I will fork the kernel and find the boot image. Give me about a week (or two).
[Nexus 4 Original Android Development] ForMartha:
Well,

It can be from the 3G coverage, the reception is OK but not perfect.

another thing that I'm thinking about is the SIM card got something to do with it - maybe it got some issues with it, but, I can't be sure of it.

I'll give Smart Radio a shot, maybe it could assist me with the drain issues.

and about the battery, It's not new, but not that old - so replacement can be considered but than again, I can't be sure that this is the root of the issue.

last thing, about kernels - I've tried some, but found this one as my favorite one - mainly because of [MENTION=4203114]mrg666[/MENTION] great attitude and kindness that offers perfect balance between a good kernel and a good man that stands behind it :)
[Nexus 4 Original Android Development] xenyz:
I know it sounds counter-intuitive, but have you tried it? I keep switching back and forth and I'm pretty convinced about better performance, although not sure about battery drain just yet. Could it be that doing more work at higher freq runs better than doing less work over more cores at lower freq? Or perhaps the overhead of plugging in for a short time isn't worth it?

If anyone else could try this and tell me if I'm crazy or not?

# echo 3 > /sys/kernel/autosmp/conf/cycle_up
[Nexus 4 Original Android Development] mrg666:
Reading your previous posts, it seems to me that your tweaks on the OS and kernel are causing the high battery drain. If I were you, I would restore the stock ROM and remove all of the hacking and tweaking apps. It is not really that much harder to use a plain stock AOSP ROM. All of the convenience you get from those tweaks and hacks are lost when you start dealing with these problems. Just my 2c. And ... thanks for the nice words :)

OK. I will try.
[Nexus 4 Original Android Development] xenyz:
From my experience, those wouldn't have any effect on CPU usage, and by extension battery life.
[Nexus 4 Original Android Development] ChaosChris:
Hi all, first of all i think this is a really great kernel! but the "lost root" is really annoying. I am currently on paranoidandroid and i dont want to flash supersu or some extra stuff, so i decided to make an any-kernel-update-zip. So i want to test the kernel over a long period, and i dont want to extract the boot.img evertime so i forked your repo and added some scripts to generate the zip. So i can easy rebuild the whole kernel.

[MENTION=4203114]mrg666[/MENTION] is it okay for you if i post my ready-to-flash build here? it is the same code as in your repo exept the generating-zip-code+tools-to-build-zip. you can have a look here: https://github.com/ChaOSChriS/android_kernel_mako
[Nexus 4 Original Android Development] mrg666:
This is okay with me as long as the kernel code is not different. I am using the a15-optimized gcc-4.9 toolchain by Christopher83. Link for download is given in the credits part of OP. Please try to use the same toolchain. Thank you for your effort.