yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Citizen_Snips:
Yes, thanks for the update. :beer::D

If I'm not mistaken the build date and time is in the file name. Looks like stable is newer.

On github here's where changes in the exp branch were merged to stable, which he just released. :p

https://github.com/showp1984/bricked-hammerhead/commit/6633714b3a323bb0954ca5f81739e3b579991ec1
[Nexus 5 Original Android Development] ChriKn:
Using the linaro Franco r25 (with your code if I remember well) I have s2s and dt2w set on boot (with the s2sdt folder created). I swipe the screen to sleep and then tap it each 5 seconds. Just tried it and got it sometimes after 5 tries sometimes after 15... Going to try to make a video when I get the occasion :/

I had touch control installed (but turned off) and the exact same thing happens with it uninstalled. Also got the unlock "click clack" during calls again.

Thanks for your devotion showp. Following your kernels since ages now and always following your threads.
[Nexus 5 Original Android Development] rancur3p1c:
I've been able to get 15-20 seconds even. Just have to make sure finger is in exactly same place when double tapping.
[Nexus 5 Original Android Development] TheDudeAbides:
Love the double tap, but it's waking my phone while just in my pocket. Would love to set the reaction time down.
[Nexus 5 Original Android Development] gpvecchi:
Well, well: now, I bought N5 because I want power, quadricore @ 2.3 Ghz, if battery lasts 1 day, it's good to me.

I tried all the 5 different kernel that are CM11 compatible(n3o, Franco/Franco linaro, Chaos, Bricked, ElementalX), in different versions (@stock settings), benchmarked with Antutu, with and without I/O, as scheduler may affect score.

Now, I know that benchmark is not all, but I like "mine is bigger": Bricked is absolutely the winner!

It gives at least 2/3k more than all other kernels!

P.S.: today's build gives a little lower score; I installed together with K Control to replace Trickster (no other change) and I got noticable less battery life...

And K-Control sometimes sees screeen calibration as compatible, then FC when using it...
[Nexus 5 Original Android Development] Phazmos:
Interesting - only time I got less than 35k in antutu was when running kcontrol. Trickster pulls 35+k, kcontrol drops it to around 32 -33.

I only set things that were in both apps to try and compare oranges to oranges.

It was still worth the $$ to support the dev though.
[Nexus 5 Original Android Development] dakore:
Luckily, we are not running benchmarks in real life situations :)
[Nexus 5 Original Android Development] wera750:
Hmm, no uv here. Maybe didn't like 2.5Ghz.
[Nexus 5 Original Android Development] ks2332:
Hey [MENTION=4195844]show-p1984[/MENTION] not a request but is screen off max frequency possibility ever or since your using your variation of mpdecision would it not be doable?
[Nexus 5 Original Android Development] nikeman513:
I'm a very basic user, so nothing really running in background. Nothing changed from swapping kernels. I do have a PVS 2, but phone wasn't getting hot or anything. Except when charging.
[Nexus 5 Original Android Development] show-p1984:
Try increasing the voltage in steps for all freqs above 2265,6Mhz and see if that fixes it.

Generally: Do not report issues if you are not running default settings. UV/OC/UC/OV will bug things if used improperly (which is usually the case)

Has nothing to do with mpdecision, but it's certainly doable.

Usually I keep this out of my kernels because some people use their phones for camera recording in their cars and a screen off freq set too low will interfere with that.
[Nexus 5 Original Android Development] wera750:
Just to make sure, the default settings in this kernel are the recommended?
[Nexus 5 Original Android Development] Emilius:
holy crap nexus 5 can work with no voltages at all. Just kidding but default voltages are way to high.
[Nexus 5 Original Android Development] show-p1984:
Depends on which settings :)

PVS id 3 =(

and u? :)
[Nexus 5 Original Android Development] akaHardison:
Great work.But man,I can't decrease cpu voltage.The lowest voltage is too high.
[Nexus 5 Original Android Development] show-p1984:
Voltage control is fixed in 20131114_182445_master-e09d141 (currently the latest available version).
[Nexus 5 Original Android Development] akaHardison:
Why.Why fixed voltage..So sad,waiting for updated
[Nexus 5 Original Android Development] show-p1984:
Huh? Fixed as in repaired. And the version that has that is already online for over 6 hours. You don't have to wait. :eek:
[Nexus 5 Original Android Development] akaHardison:
You mean the beta release?I flashed stable version.And I can't see the timestamp in website.Only Sha and md5 show up.
[Nexus 5 Original Android Development] Emilius:
okay, not really sure what is PVS standing for. I did not do full testing but until now I did 4-5 steps down on the voltages and 96Mhz is on 637500. no crashing, no nothing but like I sad I did not did full testing... this weekend I will find some time for that I hope ;)
[Nexus 5 Original Android Development] show-p1984:
I am absolutely sure the timestamp shows up. It's even in every zips filename.

Directly after the timestamp even is the unique hash identifier of the last commit that went into that kernel, so identifying a kernel on my website from my previous post (where I gave you the timestamp + branch + hash) should be a no brainer.

adb shell cat /sys/kernel/debug/krait_variant

Your krait chip variant is:
[ ] SNAIL
[ ] SLOWER
[ ] SLOW
[X] NOMINAL
[ ] FAST
[ ] FASTER
[ ] OVER 3000!

Starts with 0 (SNAIL) and ends with 7 (OVER 3000!).
[Nexus 5 Original Android Development] akaHardison:
Thanks.I didn't notice that.And is there any changeable voltage version.I want to flash it.And by the way,This kernel is good.No lag when input because of input boost.

And the UC save the battery.Good.

And I am very pleased talking with you.
[Nexus 5 Original Android Development] Emilius:
it give me device off line. I am on mac at work this moment.
[Nexus 5 Original Android Development] show-p1984:
The version I posted you has exactly what you want, even the 'repaired' version.

Seems like an adb issue on your mac.

Anyway, you can execute it on your device too:
[Nexus 5 Original Android Development] Emilius:
Nominal. Is that good? I guess is normal ;)
[Nexus 5 Original Android Development] akaHardison:
Oh,forgive me.I ignore date again.I am a careless guy.I am so sorry bother you.

Edit:I have fast version Krait.My phone made in Korea
[Nexus 5 Original Android Development] jazzor:
Showp, your latest commits reminded me something about the current suspend framework in android. I noticed now that they are using "late" suspend and "early" resume. In the current PM framework, it will automatically disable non-boot cpus when entering suspend already, without the need for msm_mpdecision to do it.

The question is: can msm_mpdecision use the new late suspend and early resume framework rather than using screen off trigger? What if there is some app that i ask to do some explicit processing on the phone that may take some time and I leave it there. If the screen times out, mpdecision will turn off all cores but this is not wanted in this case because the device is still awake and working on something. Instead, it should just keep running and let PM turn off all cores when it is actually suspending (it should only disable on late suspend). Any thoughts?
[Nexus 5 Original Android Development] jlevy73:
Excellent kernel, best battery life I've had since getting the N5 (with no performance drop off). Great job!
[Nexus 5 Original Android Development] sammko:
Best kernel for the N5 IMO, I have tried almost all of them but I get the best performance and battery life on this one. Also thanks for adding MultiROM support cause I was about to fork your repo and submit a PR :D
[Nexus 5 Original Android Development] gpvecchi:
My phone can't handle overclock to 2.5Ghz: may I boost the voltage a little or is it safier to stay at 2.4? Thanks...
[Nexus 5 Original Android Development] SPANX:
How can I use the multi ROM feature?
[Nexus 5 Original Android Development] show-p1984:
As long as the background data collection is activated in KControl under Settings (it isn't the default setting) KControl will stay active and collect cpu usage and temperature data for the graph. This will use system resources and affect battery life and performance (considering that KControl keeps a vast history for you to scroll back to this is not surprising).

This function is meant as a diagnostic tool to see how much the cpu is used during a game/running an app and when thermal limits are hit. (Just one example, I use it frequently to debug the lower sleep states. Deep sleep will pause the data collection.)

Overclocking is dangerous and you can try to bump the voltage yourself ofc. The voltages I set in the kernel are just "failsafe" voltages, as I have no way to do a proper characterization on all the chip bins and determine a stable-for-all voltage on that frequency. (Like qcom does it for example)
[Nexus 5 Original Android Development] openlatedotorg:
I always find myself jumping between this kernel and elemental.

Anyone have an issue with the phone randomly vibrating for 7 seconds or so then just rebooting? Didn't touch the settings and it did it once on a clean install.

Other than that, killer kernel. Thanks so much!
[Nexus 5 Original Android Development] show-p1984:
The vibrating sounds like the bug report feature (vol key combination).

I never, ever, had a reboot on any stable or beta up until now, so gimme logs :)
[Nexus 5 Original Android Development] garynych:
?

why any change in the frequency more of 2265, causes hot reboot ?
[Nexus 5 Original Android Development] Savant:
Your phone might not be able to handle it.
[Nexus 5 Original Android Development] garynych:
NO its wrong

on the other cores is all ok with OC...

and that any violation of the frequencies that are the default leads to restart...

reboot<300 or 2265> reboot

:confused:
[Nexus 5 Original Android Development] Savant:
Then post a kmsg log because being all knowing is not helping your situation. If you're undervolting don't do it or find a solution.
[Nexus 5 Original Android Development] Citizen_Snips:
My phone handles >2265 just fine. Undervolted as well. I have a PSV 1. Sounds like you're undervolting your CPU frequencies too low. Raise them to more stable levels.

Notice my 21hr uptime. Been running just fine @ 2.4 the whole time. Updated apps from play store, some YouTube. Also gaming. Injustice: Gods amongst us. Check your setup & try a clean install. The kernel works fine the problem is on your end.
[Nexus 5 Original Android Development] garynych:
please, set more 2265, and run antutu benchmark... and I'm sure 100% ,You will receive a hot reboot (panic) ,when will test the processor (test progress for about 10-20 percent)
[Nexus 5 Original Android Development] Citizen_Snips:
I don't use benchmark apps, never have. For the simple reason that I can run a test and get 35k. Test it again right after and get 30k. Then 28k right after and close to 35k again. They don't actually say anything useful. Unless maybe you're going to run 100 BM's and get the average. (You would have serious problems...mentally I mean)

The phone will not reboot OC if you don't run BM apps? So why use them? I game fine with bricked under heavy usage- over clocked and under volted.

As previously stated, get showp some logs. Just coming in and complaining won't do much. :)
[Nexus 5 Original Android Development] garynych:
i`m know it ;)

if no use OC, phone work fine ...

I just don't want to have a possibility to change the frequency,time, they did not work in full measure) that is'd like to display only ..... (those that employ 300<->2265) , want to see the frequency in addition to these ;)
[Nexus 5 Original Android Development] cd69:
I have a weird issue. Double tap to wake does not get activated by kcontrol. I have rebooted, toggled lot of times already. Any ideas? I am on nexus 5, stock rom and of course this kernel :)
[Nexus 5 Original Android Development] william1974:
Sound and color control are not able on this kernel? Or I did something wrong?
[Nexus 5 Original Android Development] FlyinGrub:
Not yet

envoyé depuis mon HID.
[Nexus 5 Original Android Development] Phazmos:
It's antutu, and has been doing this for some time now. Anything over stock will reboot when running it.

Phone will run fine, other benchmarks are good, it's antutu not a kernel issue. This has been seen on other kernels too.
[Nexus 5 Original Android Development] cd69:
Hey guys, need help. The kernel says 91% pass with color and sound control failed. Any ideas?
[Nexus 5 Original Android Development] tyea:
I think that's normal, because it has been the same for me. Showp hasn't put those features in the kernel yet.
[Nexus 5 Original Android Development] Citizen_Snips:
Interestingly enough, every time I open K-Control it gives me a different number. Sometimes it's 91% and most of the time it's 96%. Every so often it pops up as 100% too, but rarely.
[Nexus 5 Original Android Development] FlyinGrub:
I ve already reply to this question one post above yours

envoyé depuis mon HID.
[Nexus 5 Original Android Development] cd69:
Thanks guys for answering. Apologies for the repeated question. I did see some screenshot somewhere with 100% and thought will ask.

Thanks again and loving the double tap to wake function.

In case any one is interested to know, the battery drain is bearable :)
[Nexus 5 Original Android Development] davy917:
I'm getting a license verification check fail when running kcontrol app :(
[Nexus 5 Original Android Development] william1974:
Not yet
[Nexus 5 Original Android Development] cd69:
Got it thanks :)
[Nexus 5 Original Android Development] decemberlast2013:
show-p1984 is mpdecision better than hotplug? How do you explain that some developers work on hotplug? Doesn't that mean qualcomm and google are stupid and they do not know what they did by picking mpdecision route?
[Nexus 5 Original Android Development] nealkoy:
What are you talking about? Mpdecision is the hotplug!
[Nexus 5 Original Android Development] decemberlast2013:
I mean hotplug with mpdecision off, like franko's, he went different route, right?
[Nexus 5 Original Android Development] skulldreamz:
Yes, mpdecision is just the name Qualcomm calls their proprietary hotplug. When you hear a developer saying they are not using mpdecision, they just mean they are not using the normal mpdecision but using one (hotplug) that they compiled from source on their own or just staying away from the typical mpdecision we have all grown to know. If you can get a job deving at google , I would say that the person is not too dumb or knows the right people...lol ;)
[Nexus 5 Original Android Development] bodooo:
Will this kernel have franco's audio patch implemented in the future or will it stick with faux?
[Nexus 5 Original Android Development] A-FrenZy:
how to edit the system file ?

it dosent allow me to save

sorry for noob question :crying:
[Nexus 5 Original Android Development] hd2009:
show-p1984, is it normal to have the cpu load at higher frequencies even when browsing or messaging ?

I mean , my cpu uses only 300 mhz or 2200 mhz, with no significant use of intermediate frequencies...
[Nexus 5 Original Android Development] Phazmos:
Pretty much normal if using ondemand governor. Interactive uses higher frequencies more conservatively, you may want to try it.
[Nexus 5 Original Android Development] bog3nator:
I just installed the kernel last night and while just using my phone everything is OK. I tried to run antuntu and it crashed my phone twice at 21%
[Nexus 5 Original Android Development] skulldreamz:
Try using interactive governor with row io scheduler. Should start to scale up and down frequencies with more flex....
[Nexus 5 Original Android Development] estallings15:
Set system to R/W.
[Nexus 5 Original Android Development] KingDani1997:
For me the Battery drain with stable version 30/12 is bigger than with the versions before. Anoyone else experiencing this problem?
[Nexus 5 Original Android Development] hd2009:
Ill give it a try. I dont know whats row io scheduler though. Im using bricked, there are 2 strings to change, mmcblk0 and mmcblk0rpmb.
[Nexus 5 Original Android Development] Phazmos:
Use some kernel control app - kcontrol or trickster will have the option.

---------- Post added at 05:24 PM ---------- Previous post was at 05:20 PM ----------

Unfortunately, yes. I just went back to the 12-12 version yesterday and battery life is back.

62% remaining, 7 hrs up time, just shy of 4 hrs screen on. I'd be at 40% or less on latest version.
[Nexus 5 Original Android Development] bog3nator:
By that statement I will go to 12-12 as well I got about 3-4 hours screen on time with 12-30. Will check out 12-12. 12-30 alright crashed my phone when running antunu. Dunno why....
[Nexus 5 Original Android Development] Phazmos:
I know antutu crashes if you oc, but it ran fine for me. Sometimes it crashes when run right after flashing a kernel. Try it again with stock frequencies and see what happens.
[Nexus 5 Original Android Development] bog3nator:
It was stock. But it was also right after I flashed. Not to worried since everything else is working perfect
[Nexus 5 Original Android Development] decemberlast2013:
4hrs screen on at 62%? Auto brightness? What settings?
[Nexus 5 Original Android Development] Citizen_Snips:
Yeah antuntu crashes on this kernel even with stock voltages. Over clocking will get you a soft reboot. As a matter of fact, all of these apps will crash. Antutu, quadrant, cf bench, any. Just search for BM app on play store. Every single one will FC or soft reboot.

As far as real world use goes, I have had no reboots when doing anything else. Battery is pretty solid and so is performance.
[Nexus 5 Original Android Development] gpvecchi:
I don't have crashes, as far as I stay at stock voltages and overclock max to 2.4...
[Nexus 5 Original Android Development] cvsolidx17:
MULTIROM Support?

I read in another thread that bricked-kernel had incorporated MULTIROM suppport in the latest stable release, however checking the changelog I can't seem to be able to determine whether or not this is the case. Then again its really late and I could possibly have just missed it all together. If any of you could let me know, that would be great, thanks
[Nexus 5 Original Android Development] Remoteconcern:
Yes, this is the case, as of the latest update.

+Accidental thanks ;)
[Nexus 5 Original Android Development] cvsolidx17:
It happens lol thanks though. Finally gonna give this multirom thing a shot.
[Nexus 5 Original Android Development] Phazmos:
No auto brightness, wifi, noop, interactive. I do set mpdecision to kick in early, and governor to ramp up quicker.

Ended with 13 hrs up and just shy of 8 hrs sot. Using 12-12 version, not latest
[Nexus 5 Original Android Development] hd2009:
Can someone post his settings with this kernel ?

I have kcontrol. Do i need to change blk0 or blk0rpmb ?
[Nexus 5 Original Android Development] Phazmos:
In kcontrol - misc/governor - set all to the governor you want.

Above that is scheduler - again, set to what you like.

I find trickster is a little easier. Bought kcontrol, and it gives more options, but trickster is less confusing.

Still worth it to support a good dev.
[Nexus 5 Original Android Development] jwhyte:
I'll attach what [MENTION=4195844]show-p1984[/MENTION] originally posted...

I can give you a few, quick hints: (some may already have been set as default and some may not be supported by your device. Like vdd, freqs, etc...)

CPU->Frequency->Min: 96Mhz on all

CPU->Voltage->-50mV

Thermal->+5°C for performance, -10°C for a cooler phone (on all, except shutdown)

MPDEC->Simple-> Hotplug cores Fast for performance, unplug cores fast and hotplug cores slow for battery.

MPDEC->Simple->￼isable boost for battery, this might cause the typical Autogroup [X]

Scheduler->Childfirst [X]

Scheduler->CFQ on all

Scheduler->CFQ Settings->group_idle to 1 for all

Vibration->80 (slightly stronger, more like n4)

Ondemand already has everything set to optimized values.

Benchmark scores are subject to throttling which occurs earlier on lower PVS id SOCs. Check your PVS id and if it's below 3 you know why.

Why are lower binned SOCs earlier throttled? Because they need more power to run stable which equals more heat.

If you show me a repo where it is actually being developed and tuned for the n5 I will. Otherwise adding 1 million governors that are not tuned for this device just makes no sense, at all.

Shared from Google Keep
[Nexus 5 Original Android Development] Remoteconcern:
Dennis, do you think the 96mHz actually works on this? I recall the N4 having that option removed due to it non functioning.
[Nexus 5 Original Android Development] Remoteconcern:
Yes, I know it displays but the N4 had hardware limitations preventing it from actually using that speed despite the display.
[Nexus 5 Original Android Development] dionisius1:
Hi! Thanks for developing this kernel, so far has been a wonderful performance for me. How do you set the temperature using trickster mod? Because my phone getting hot quite often by just doing simple task like checking social network. Thanks!
[Nexus 5 Original Android Development] hd2009:
Ok, my goal is battery life.

governor: interactive

CPU->Frequency->Min: 249600Mhz on all -75mV Max: cores0/1:1036800 cores1/2:883200

CPU->Voltage->-50mV

MPDEC->Simple-> unplug cores fast and hotplug cores slow for battery.

MPDEC->Simple-> disabled input boost, although Autogroup is ON. (dont know if need to leave on or off...)

Scheduler->Childfirst [X]

Scheduler->CFQ on all (i don't understand why there are 2 strings here, blk0 and blk0rpmb, while others tweakers only have 1)

Scheduler->CFQ Settings->group_idle to 1 for all <<<<<<<<<< not working, min value is 10. Does anyone know if it's safe to use?

I don't understand why showp is giving us the most customizable kernel without giving us some good tips to use for

performance

battery

balance
[Nexus 5 Original Android Development] gpvecchi:
Problem, I don't know if this is kernel related, but it happened 2 times...

Turned on phone and let it on Pin request till deep sleep.

Then I had to long press power button to restart. I had data corruption too...
[Nexus 5 Original Android Development] Alcibiade:
Feels the same to me too. Battery drains a bit faster
[Nexus 5 Original Android Development] decemberlast2013:
+1
[Nexus 5 Original Android Development] Phazmos:
12-12 is the best on battery for me. There are a couple posts on the a few pages back.
[Nexus 5 Original Android Development] Citizen_Snips:
Surprisingly, me too. Lost like 700 texts. Game saves. My Nova launcher desktop setup (everything was stock nova). I had it in my pocket a few hours and took it out and noticed it
[Nexus 5 Original Android Development] bog3nator:
Question: I previously flashed Franco kernel and another kernel. Before I flashed this I restored my boot from my stock nandroid I made. Will that put the stock ram disk back? I am not sure if either kernel comes with a ram disk or not.
[Nexus 5 Original Android Development] jwhyte:
Yes.
[Nexus 5 Original Android Development] ausaras:
I was on 12/30 build and had the same problem. I plugged in my phone and left it overnight. It was powered off in the morning. But when I use it during the day intermittently, it does not power off.

Last night, I flashed back to 12/12. Left the phone in the same way. No power off.

Something is not right with the 12/30 build.
[Nexus 5 Original Android Development] hd2009:
Replies on quote.
[Nexus 5 Original Android Development] Phazmos:
That's interesting, I am seeing something similar in my phone as well. That means the multirom patch worsens battery life O.O

(That's the only thing changed between the versions: https://github.com/showp1984/bricked...00d0...6633714)

That's why I went back to 12-12. Saw that was the only change, and I'll never use it.