yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] show-p1984:
It's an issue for me.

The only difference between our devices seems to be the ROM. I am running stock on both of them.

Please give me the output of this command: (run as root)

find /sys/devices/ -name "scheduler" -not -path "/sys/devices/virtual/*"

PS:

When asked about a version "latest" is never an answer. Just write down the version string.
[Nexus 5 Original Android Development] michelemascia7:
Is normal that the compatibility with kcontrol is 96%? I use the latest stabile version (20151031) :) [MENTION=4195844]show-p1984[/MENTION]

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] show-p1984:
Nope it isn't. It works fine for me.

The GPU compatibility check just tests if the module is present and if it is possible to insert it (it's a whole lot more complicated behind the scenes, but that's the jist gist <--- Urban Dictionary just informed me that "jist" is the wrong spelling of "gist". Who knew? ^^).

Please give me the output of these commands (run as root):

lsmod | grep kcontrol_gpu_msm | tail -n1
ls -al /system/lib/modules/

Additionally a logcat from a fresh KControl startup (use menu->quit and swipe it away from recents, then start the logcat and launch KControl. Stop the logcat when the compatibility list is done loading.)

Are you using systemless root?
[Nexus 5 Original Android Development] michelemascia7:
No i use the normal root , i flashed supersu 2.52.

I think I did all the steps correctly, let me know if I made some mistakes :) Thanks

I attached the logcat, and the output of the commands (i make a screenshot).
[Nexus 5 Original Android Development] show-p1984:
You attached a last_kmsg. Not a logcat.
[Nexus 5 Original Android Development] michelemascia7:
Sorry, is this correct?
[Nexus 5 Original Android Development] show-p1984:
Yes. But this:

11-02 23:18:53.695 E/de.bricked.kcontrol.GPU_Overview(17566): Failed to insert, unrecoverable error -1

Points to a kernel log error. So I will need a kmsg as well (note: not a last_kmsg, a kmsg. Or the output of "dmesg")
[Nexus 5 Original Android Development] michelemascia7:
Is this correct? I open the kcontrol app, and then take a kmsg with another app

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] show-p1984:
Sadly no.

There are two ways to get kernel messages of an event:

Do your stuff you want to log and use the "dmesg" command to get a kernel message that should (if it's not spammed away) contain the event.

Start a kmsg log with "cat /proc/kmsg > /sdcard/yourfile.log". This command will block until you cancel it. Now do your stuff you want to log and finally cancel the previous commad with CTRL + C once you are done.
[Nexus 5 Original Android Development] michelemascia7:
I use dmesg command in the terminal , and i save this file. Sorry but i'm not experienced.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] michelemascia7:
[MENTION=4195844]show-p1984[/MENTION]

Sorry if I failed to give you all the informations , but I'm not very practical . I hope that the problem will be resolved , because I find your kernel very

satisfactory , for this I bought your app :D Thanks anyway ;)

P.S Is not implemented the fast charge usb?
[Nexus 5 Original Android Development] show-p1984:
I didn't not answer because I disliked the information you gave, which was sufficient. I didn't answer because I had no time. :)

From the last log it seems that selinux on your device is killing the module's insertion:

[ 8579.665573] type=1400 audit(1446546514.767:8053): avc: denied { module_request } for pid=32419 comm="su" kmod="personality-8" scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=system permissive=0

Which is odd. Not that it does that, but that it doesn't do that on my device too. I will have to investigate once I have more time.
[Nexus 5 Original Android Development] michelemascia7:
Thanks for the informations :)

Inviato dal mio Nexus 5 con XDA Forums
[Nexus 5 Original Android Development] shri_chanakya:
Knock knock... Any new update planned? New factory image is out. Change log mentioned some kernel security fix. Not sure if it's for hammerhead
[Nexus 5 Original Android Development] Yank555:
Factory image is not source drop.

HH kernel has no changes, here's the last commit :

https://android.googlesource.com/kernel/msm/+/android-msm-hammerhead-3.4-marshmallow-mr1

Security fixes is on the ROM-side.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r9 v0.61
[Nexus 5 Original Android Development] shri_chanakya:
so this patch was on 04-Nov, latest brick was 31-Oct last year. Probably this patch is not yet included in the build I guess.
[Nexus 5 Original Android Development] Yank555:
You'd need to check bricked git.

Here's the commit log from Google to compare with :

https://android.googlesource.com/kernel/msm/+log/android-msm-hammerhead-3.4-marshmallow-mr1

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r9 v0.61
[Nexus 5 Original Android Development] leonman44:
Hello , i really like your work , you are the only guys that have an actual gpu oc (cpu could be higher by the way my phone can do a 2.9ghz) , i have the 6.0.1 version android so i tried the last beta kernel for hammerhead but i am having trouble with it , phone will freeze soon or late using kcontrol or not , mainly when i try to change cpu governor or when benchmarking with oc or not , tried a format -> clean stock rom install -> kernel flash (with or without ) -> supersu flash but again got same problem. I tried also the latest stable kernel but my phone wouldn't boot , same thing for the previous beta. What version works best for this kernel?
[Nexus 5 Original Android Development] show-p1984:
Hi,

Sorry, at the moment I have very little time working on my kernel. I will however see if I can squeeze an update to the kernel (which is only patched up to Lollipop iirc) in on Wednesday.
[Nexus 5 Original Android Development] shri_chanakya:
nice to see this kernel being revived... was my go to kernel but had to move along as updates were not consistent.
[Nexus 5 Original Android Development] leonman44:
He is the only guy who oced the gpu!! If you play games you appeciate that :D

So should i downgrade my phone at 5.0.0 so i can use this kernel? :)
[Nexus 5 Original Android Development] show-p1984:
Started a beta build @ http://jenkins.bricked.de/job/bricked-hammerhead/22/console

Contains a quick merge of the Marshmallow mr2 release in Google's repos + a defconfig update.

Will be auto-uploaded to bricked.de soon(tm)
[Nexus 5 Original Android Development] shri_chanakya:
Boots up fine. Had a unexpected reboot but it was due to previous kernel settings being applied. Uninstalled app fir settings and is working fine so far for an hour or so.
[Nexus 5 Original Android Development] hsrn:
great kernel.

happy to have sweep2wake feature back.

i was on stock kernel for a long time.

the colours are more vibrant on stock compared to default bricked color settings.

could we have stock kernel like color settings as default for bricked kernel?
[Nexus 5 Original Android Development] show-p1984:
If memory serves I didn't touch color defaults. Are you sure this is an actual difference compared to the common placebo effect?

Also: Keep in mind that certain light intensities affect contrast levels. (When held in the sunlight I get ramped up contrast for example, making the display look completely different)

PS:

Have you changed color values over an app? And is that app automatically applying your settings on boot? (it wouldn't be able to on stock kernel, which is why there will be a difference)
[Nexus 5 Original Android Development] hsrn:
i havn't had any control app installed.

i have just installed your kernel app after installing your kernel.

it might be placebo then.
[Nexus 5 Original Android Development] montbazon:
Das freut mich sehr.

BTW I have a question. Do you have any plan to have another nexus device? Current or upcoming whatever.
[Nexus 5 Original Android Development] jinwook222:
Dear Bricked developer

I used Nexus 5. (the present.... I use Nexus 5x.)

I loved this kernel and KControl app.

I want Nexus 5x Bricked kernel. T_T

please~~~~~~~~
[Nexus 5 Original Android Development] hsrn:
[MENTION=4195844]show-p1984[/MENTION]

i have applied a custom color profile with your app.

screen looks much better now.

is there any possibility to save these settings?

i don't want to do that again after the next clean install.
[Nexus 5 Original Android Development] show-p1984:
Currently my money is tight. I am probably waiting for the next Nexus.

I don't have a Nexus 5x and I generally only develop for devices I own. That being said: Somebody got a used and cheap 5x lying around? :)

You can save them through my app, but you will have to back up your app data with Titanium Backup (or manually). Otherwise the settings will get wiped if you wipe your app data partition. (The update which brings online sync and export to KControl is in the works)
[Nexus 5 Original Android Development] show-p1984:
[IMG="Buildbot"]https://bricked.de/_stuff/building.png[/IMG]

As promised a stable release on Wednesday :p

bricked_hammerhead_20160608_111521_master-c160ca1

Changes
[Nexus 5 Original Android Development] hsrn:
[MENTION=4195844]show-p1984[/MENTION]

just for me to understand the installation pocess of this kernel:

i flashed the kernel on top of stock rom.

with the june update i wanted to do a clean install.

i wiped cache, system and data in twrp.

i booted up the stock rom.

checked the "about phone" section: it still said "bricked" kernel.

do i have to flash your uninstaller to be 100% sure to get rid of all bricked kernel related stuff.

so wiping system and data and flashing stock rom alone doesn't do the job.

am i correct?
[Nexus 5 Original Android Development] show-p1984:
When you flash stock Rom, be sure to also flash the boot partition (that's where the kernel lives) otherwise the previously installed kernel will persist. (Or use the uninstaller, which will only work if you haven't deleted the backup zImage from your sdcard)
[Nexus 5 Original Android Development] shri_chanakya:
Using Stable version. So far no issues. Things working fine. No issues so far. Thanks for the good kernel.
[Nexus 5 Original Android Development] hsrn:
i flashed a flashable zip provided in a one of the threads here.

i have to check if his script contains the command to flash the boot.img.

that might be the problem.

thanks for your quick answer.
[Nexus 5 Original Android Development] pepa 77:
Hi,in flashable.zip delete boot.img is ready : D
[Nexus 5 Original Android Development] nishant203:
I have a Nexus 5 whose power button is broken. So I was thinking of flashing this kernel to use Sweep2wake or KnockKnock feature. By enabling them how much is the battery drain?
[Nexus 5 Original Android Development] Mrcactuseater:
Quite a significant amount.

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Nexus 5 Original Android Development] show-p1984:
Due to hardware limitations on the Nexus 5 (as opposed to the HTC Sensation, HTC One X, Nexus 4, etc...) we can't use purely IRQ based calls to detect touches. We have to keep power to the display controller as well. This will eat about 10-20% of your battery in a normal use cycle (18 hours). As always: YMMV.
[Nexus 5 Original Android Development] fabio000:
The first post isn't updated since 2014 so I think it's ok to ask

the max CPU OC is still only 2.5Ghz?

I was thinking in flashing it because of GPU OC, but my CPU can handle stable 2.7Ghz without overheating/random reboots
[Nexus 5 Original Android Development] shri_chanakya:
Max clock is stock unless you use app to override.
[Nexus 5 Original Android Development] show-p1984:
At which voltage? (or: on which kernel, so I can look up the voltage, which you can do as well, with the information below)

As you can see here, the maximum CPU clock is 2534,4MHz @ 1,155V for the lowest (slowest) PVS id 0. Personally I would avoid anything above 1,16 Volts. Why? - Electromigration.

Electromigration occurs always. It's basically the transfer of material of the small copper fins inside the CPU, leaving that spot with less copper than before. The shrinking gate size in recent years helped to make this a much more serious issue. Factors increasing this effect are temperature and voltage. So what does this mean? - If the voltage is higher the effect increases. BUT: The higher the voltage, the higher the wattage, the higher the temperature. So increasing voltage does increase this effect way more than temperature alone.

Worst case: Your CPU will run fine for 2 months, and then suddenly become unstable on OC. You then clock down to a stable level and 2 months later your CPU doesn't run with that either (until you are reaching stock clocks and it will fail in the bootloader).

So points to think about: Is it worth it the extra 200MHz? Can you

FEEL

it? Are you hitting the 1,16V limit on 2,7Ghz, or are you on a better PVS id which allows higher oc? (your PVS id is?)

Are you sure your current kernel (the one you are doing 2,7Ghz on) isn't lying to you? Let's examine this line:

{ 1, { 2534400, HFPLL, 1, 132 }, L2(19), 1155000, 1 },

(I marked the most important stuff for you)

RED = The TEXT that is shown for this line. I can enter 3500000 here, and it will report 3,5GHz. Which is nonsense. (and lying, or not knowing better, or... well... I don't want to stomp on anyone's feet...)

MAGENTA = The clock source that is used. Here, it is HFPLL, which is clocked at 19200KHz in our handset.

BLUE = The multiplier. If you are born prior to the 1990s you might remember this from having to set it on your PCs motherboard with a jumper. Same principle: clock_source * multiplier = Speed. This is the ACTUAL speed the CPU is running at.

GREEN = The voltage this speed should be using. Here: 1,155 Volts.

Still,

is it worth the 200Mhz?
[Nexus 5 Original Android Development] fabio000:
Voltage is at 1.11V/ElementalX

I never tested at 2.5 so I don't know if the 200Mhz make a huge difference, but from 2.2 to 2.7 feels a lot more smoother

PVS line

{ 1, { 2726400, HFPLL, 1, 142 }, L2(19), 1195000, 831 },

-edit-

Strange, kernel managers apps shows 1115mv and in the line is 1195

-edit2-

actually, I don't know if I got the correct line, I found another (pvs 3) with 1.11V

{ 1, { 2726400, HFPLL, 1, 142 }, L2(19), 1115000, 831 },

-edit3-

after a little googling I understood what is pvs

so, this is the correct line, I checked and PVS id = 3
[Nexus 5 Original Android Development] NineInchNails:
Read through the thread
[Nexus 5 Original Android Development] szucsgf:
http://xdaforums.com/showthread.php?p=47430539
[Nexus 5 Original Android Development] IharpI:
http://xdaforums.com/showthread.php?p=47430539&highlight=charge#post47430539
[Nexus 5 Original Android Development] szucsgf:
Beat you to it! :p
[Nexus 5 Original Android Development] paul_59:
Edit

Sorry, ignore this, just realised already asked and answered

I am a new user of your kernel, and have just bought kcontrol, previously used trickster, wonder if someone could help ,

I can't access GPU settings
[Nexus 5 Original Android Development] davy917:
[MENTION=3619123]paul_59[/MENTION] GPU settings is not yet available.

I'm having an issue where I set the UV to -50mV and runs fine. I set it to UV at boot and when I reboot, the phone crashes and reboots as soon as the UV kicks in. Phone runs fine until a reboot..

I've never pulled a logcat or kmesg before, is there an easy documentation on how to do that so I can be helpful?
[Nexus 5 Original Android Development] IharpI:
This is very strange.

As in both cases just the app applys the undervolt.

Do you have ADB setup correctly?

If not please search for a tutorial. There are lots of them out there for different computers.

When you have it, just type this for kmsg: adb pull /proc/last_kmsg

For logcat: adb logcat
[Nexus 5 Original Android Development] show-p1984:
Nope, this kernel doesn't have a screen off max freq limitation yet.

I don't know why you have that stuttering, my device runs fine in sleep with music playing. (I am using it as a car audio player all the time and just tested it with a 15minute 700kbps flac file. Worked fine.)

Just by the way: Are you sure that you are even getting the full 700kbps out of the n5? Seems a bit overkill for the hardware and it's designed purpose. I bet the soundchip and amp add so much noise that you can't even distinguish 350 and 700 kbps :)

Nope, I didn't change anything regarding microphones or speakers, yet.

Usually the issue you describe is caused if you have a case that doesn't leave an opening for the ambient noise mic, or you covered it by hand. On the Nexus 5 that mic is right beside the headphone jack. (that small hole)

Yes it does, but this kernel currently does not support faux's sound control. I will go ahead and pick it when s2w and dt2w are released.

That's normal. The Nexus5 brings a newer model of the kgsl driver where some symbols changed. KControl does it's best to automagically handle that but fails since the changes were too many and I wrote it in a way that it rather gives up than brute forcing it, which could cause any number of issues.

An update will fix that soon(tm).

That issue is easily explained and not a bug at all.

Your phone runs fine on -50mV, as long as there is no load. With load temperature rises and with rising temperatures the electrical resistance rises as well, effectively decreasing the voltage slightly.

What you have there seems to be a bare-edge case of undervolting. As long as no load is put on the cpu (and hence the temperatures are quite low) everything works fine, but a small increase in load will make it fail.

That's why you always test your undervolt settings on at least the min and max freq with a cpu stress tester for about 5 minutes. (in case of the max freq: until thermal throttling kicks in)

Bootup is putting quite a strain on the cpu, it's over 50% load for at least one minute.
[Nexus 5 Original Android Development] davy917:
[MENTION=4195844]show-p1984[/MENTION] thanks for the explanation.. phone actually seems good now. I was watching movies and streaming netflix last night so I figured the UV was taking well. Maybe something wasn't playing right for whatever reason, I'll get you a kmsg next time.
[Nexus 5 Original Android Development] show-p1984:
In case of UV/UC/OC/OV crash-logs are usually pretty much useless since the hardware resets, not the software. So there isn't anyhting to log. (Except maybe the last_kmsg's last part, the reason. Should be: "hw_reset")
[Nexus 5 Original Android Development] akaHardison:
But I think you should add a selectable box in kcontrol or what other apps.My motherboard is Gigabyte.And I want to say is I am using USB port about 5 years(I am 16 years old).And I am always overload my usb port.Trust me,even in China.Gigabyte's motherboard has PTC.All you concern is your power.Maybe your power overload and break down.I tested one motherboard is P35-S3L.It can provide 500ma Fusb and 1A Rusb.Another is Z77-D3h.Usb2.0 has 2.5A.Usb3.0 has 3.4A.You can add the warning in kcontrol.But just don't disabled it.If you can provide this function I will happy.If you not.I won't blame at you.That is not your fault.I just need to DIY an USB port .And I am lazy.....lol
[Nexus 5 Original Android Development] erpalma:
Am I wrong or this kernel does not work with Cataclysm rom? Mine goes in bootloop :(
[Nexus 5 Original Android Development] psxsnake:
It works very well.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] sammy789:
Do you use the new official cwm recovery? I got bootloops after flashing this kernel using that recovery. Returning to the unoffical touch version solved the problem for me.
[Nexus 5 Original Android Development] show-p1984:
Well, if it works for you, fine. Pull my sources compile the kernel with it and you are happy :)

Or the easier way: Buy an adapter on ebay or amazon which just noops the data+&- lines on your usb plug. This will also work for not hacked phones, which is the big advantage here.

Since you mentioned PTC, well on boards following the USB standard to the letter the fastcharge hack won't do you any good anyway. You will get something like this:

(This is out of a whitepaper on USB protection circuits following the USB standard)

Which means:

Phone charges for a few seconds normally until the PTC detects abnormal current and goes into high resistance mode. The phone barely gets anything at all at this point. After a time the PTC resets and the dance starts over again.

So it's basically: Charging, not charging, charging, not charging, charging, not charging, etc...
[Nexus 5 Original Android Development] erpalma:
Yes, the official one!

I'll try the unofficial one thanks
[Nexus 5 Original Android Development] benjamin.j.goodwin:
Love your long explanatory posts, proper feedback. :beer::)
[Nexus 5 Original Android Development] show-p1984:
*coughs*

https://plus.google.com/u/0/108262968419038009038/posts/MmeoDsnoAfz

*sneaks out*
[Nexus 5 Original Android Development] benjamin.j.goodwin:
Installed, thanks man! Will give it a good going!
[Nexus 5 Original Android Development] raycaster3:
Working with no issues. Can't get enough of the s2w/s2s.
[Nexus 5 Original Android Development] guapinoy:
Fantastic kernel. Appreciate all the great work! Just a small thing I've noticed. Tried on 4 reboots: In KControl enabled Sweep2Wake, checked to see if "Apply Sweep2Wake Settings" is on, turned the device off and on using Sweep2Wake :good: , but reboot doesn't retain the settings. All other settings are retained, such as Vibration, CPU Voltage, etc.

Again, awesome work! Thanks! :)
[Nexus 5 Original Android Development] leoaudio13:
Can we dirty flash or have to flash stock then this kernel ? Thank you so much for this :)
[Nexus 5 Original Android Development] show-p1984:
from bootup:

logcat | grep de.bricked.kcontrol

Try a dirty flash. If you experience any issues flash the boot.img of your rom first and then the kernel again. Check if the issue is still present, then post it in the issue tracker if it is.
[Nexus 5 Original Android Development] leoaudio13:
Dirty flash works gr8t so far. S2w working.

---------- Post added at 07:12 AM ---------- Previous post was at 07:07 AM ----------

Minor update: s2w is disabled after reboot. Have to re-enable again
[Nexus 5 Original Android Development] guapinoy:
Here ya go

Logcat

https://app.box.com/s/f0v2gt799gf8b3gjt1ib
[Nexus 5 Original Android Development] show-p1984:
That's normal. Kernel files are virtual files linking to in kernel functions. You will have to use an init.d script or an app to keep it enabled.

Thanks, it's a logic fail on my end in KControl.

I/de.bricked.kcontrol.BootupHandler( 2975): Sweep2wake is supported
I/de.bricked.kcontrol.BootupHandler( 2975): Sweep2wake version 1 found.

Doesn't re-apply on atm. Fixing that and a few other bugs for a new KControl release asap.

Edit:

Fixed in the next KControl update

I/de.bricked.kcontrol.BootupHandler( 2275): Sweep2wake is supported
I/de.bricked.kcontrol.BootupHandler( 2275): Sweep2wake version 1 found.
I/de.bricked.kcontrol.BootupHandler( 2275): Enabling Sweep2wake.

Edit2:

Rolling out now.

https://plus.google.com/u/0/108262968419038009038/posts/X3mkn38fx2p
[Nexus 5 Original Android Development] J0ESK0:
Nevermind.. I just used a kernel app to keep it enabled. Working GREAT! Thank you!!! My power button thanks you as well :good:
[Nexus 5 Original Android Development] davy917:
How do you change the i/o scheduler on this kernel? Also what is the default? I can't tell from the kcontrol app :(