yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] neobuddy89:
I received PM from Aux, he has been following commits and using same base, according to his testings SOD for some users are result of Dynamic Fsync incompatibility with latest CAF merges.

I am not sure how true this holds, but here is test build with all reverted commits readded, wake controls readded but Dynamic Fsync disabled.

Test Build Link: http://www.androidfilehost.com/?fid=23329332407581157
[Nexus 5 Original Android Development] AuxXxilium:
For me it is working since hours with my kernel, so i think it should work on your's too. i hope it is the solution.
[Nexus 5 Original Android Development] neobuddy89:
This issue has gained momentum and on sidenote, another PM from 0Oo user describes this issue is resolved by updating the bootloader - even dynamic fsync enabled didn't caused issue for him.

My Bootloader version is HHZ11d

For those having issues, please share your bootloader version from the bootloader screen.

And where you get update for same?
[Nexus 5 Original Android Development] AuxXxilium:
i have HHZ11k
[Nexus 5 Original Android Development] toocool4all:
Same here

Sent from nexus 5 SENSONIC HD rom

---------- Post added at 12:18 AM ---------- Previous post was at 12:15 AM ----------

What are the things reverted ?

Sent from nexus 5 SENSONIC HD rom
[Nexus 5 Original Android Development] ChanceOfChange:
HHZ11k here too
[Nexus 5 Original Android Development] daavid1995:
I am on HHZ11k too. :)
[Nexus 5 Original Android Development] neobuddy89:
Retention voltage reduction and Clock-PLL time reduction patches were reverted.

One targeted to save power when suspended - might caused voltage starvation?

Other targeted performance optimization by reducing time required by PLL lock when display is turned on.

Anyways, I have updated my bootloader as well.

Here are useful links to save your time if you haven't updated:

http://xdaforums.com/showthread.php?p=51150167

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

Please be extra careful while bootloader update. One wrong move, your device turns into brick.

So, check md5sum before proceeding.
[Nexus 5 Original Android Development] AuxXxilium:
had a SOD 5 min ago and 1 minute after activating the fastcharge. it is one commit, that causes this crashes i think. the only thing is the display is black but the device is working in background, screenshot was working and i received a call over my bluetooth headset, can talk with the other but the screen won't wake up.
[Nexus 5 Original Android Development] oo0:
had positive SOD proof testing with latest bootloader HHZ11k posted here if you wanna give it a try. also latest radio is not recommended (.25) - .17 seems better.

edit: using FSYNC for 48 hours now.
[Nexus 5 Original Android Development] ChanceOfChange:
HHZ11k bootloader and .23 latest radio here..sods still exists so im moving to cyanogenmod latest kernel (aokp ltest rom here)
[Nexus 5 Original Android Development] NYCguy2020:
Same here :(
[Nexus 5 Original Android Development] AuxXxilium:
updated to your bootloader and readded dynfsync to kernel to try.
[Nexus 5 Original Android Development] ChanceOfChange:
http://xdaforums.com/wiki/LG_Nexus_5

by this info your phone has the 4.4 ver firmware in it...

4.4	KRT16M	HHZ11d	M8974A-1.0.25.0.17

update with 4.4.2 firmware (bootloader - radio) and we can have the real deal!
[Nexus 5 Original Android Development] neobuddy89:
Fastcharge working good.

Users who had this issue and submitted their logs before didn't had fastcharge or dynamic fsync enabled.

And seeing your git log, adding PWRKEY_SUSPEND to touch driver is not recommended, gave me SOD issues:

https://github.com/Root-StylE/kernel_caf/commit/9e566d04b58ba1404e206eab3b8eaf63f8f87965

So, it was cleaned

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/4adc3da6f899261d728f8ccc115c6de630c74cc7

Also, PWRKEY_SUSPEND was wrongly implemented in mdss_panel_on instead of mdss_panel_off

This was cleaned here:

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/7693e5ee9228a2a91b0f825649e83fd0d9e353da
[Nexus 5 Original Android Development] AuxXxilium:
i try it, thx
[Nexus 5 Original Android Development] Tikerz:
Any updates on SOD issue?
[Nexus 5 Original Android Development] A_Button117:
Haven't had any problems on the 3/23 nightly

Studying Computer Science and Forensic Science @ UCO

Using XDA Premium 4
[Nexus 5 Original Android Development] Tikerz:
I'm going clean install CM11 and try with latest nightly.
[Nexus 5 Original Android Development] toocool4all:
It's been a day, and no sod for me, I m having latest nightly and latest boot loader .

Sent from nexus 5 SENSONIC HD rom

---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------

For those who are having sod then they must do clean install as there must be kernel remains that causing the problem

Sent from nexus 5 SENSONIC HD rom
[Nexus 5 Original Android Development] neobuddy89:
Please clean install last test build, a page back and let me know the result.
[Nexus 5 Original Android Development] toocool4all:
Lol finally gotten sod in charging .

Sent from nexus 5 SENSONIC HD rom
[Nexus 5 Original Android Development] Tikerz:
Me too. Woke up this morning and phone was SOD. This from a clean install CM11.
[Nexus 5 Original Android Development] ChanceOfChange:
most sods cause on charging some other not...cant be sure 100%
[Nexus 5 Original Android Development] neobuddy89:
Thanks for the log.

So, the claim for dynamic fsync causing issue is false.

I am going though last 15 days commits to fix issue once and for all. Will post a build in next few hours.

It is very surprising that my device didn't had any issue at all.
[Nexus 5 Original Android Development] mo976:
I haven't had any issue either with the latest cm nightly(s) and latest chaos builds while leaving it on the charger overnight as a clock in night mode.
[Nexus 5 Original Android Development] Tikerz:
Mine seems to happen when the phone is on the charger.
[Nexus 5 Original Android Development] mo976:


---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
[Nexus 5 Original Android Development] :
The battery saving profile destroyed my battery life (I was losing a percent per minute). Is that just me?
[Nexus 5 Original Android Development] toocool4all:
Ohh thanks for the temporary work around . so if any if you getting sod while charging you should put your phone in clock in night mode it will stop going in death sleep so no sod ohhhhhhh yeah

Sent from nexus 5 SENSONIC HD rom
[Nexus 5 Original Android Development] neobuddy89:
New nightly build available -

AFH or MediaFire

Here is a refined build:

Chaos-Kernel_v11.0-[03-25]-[00-29]

* Upstream update to Linux 3.4.84

* New memory utilities optimizations

* Crypto Driver updates from CAF

* Possible fix for SOD issues faced

* Performance optimizations
[Nexus 5 Original Android Development] Tikerz:
Just flashed it. Will leave it on the charger for a while. Thanks!
[Nexus 5 Original Android Development] daavid1995:
My Phone dosn't boot with new Nightly.

CM11 newest Bootloader.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tikerz:
Nevermind
[Nexus 5 Original Android Development] EnginEAR:
Will try to provide some useful feedback...

Thanks for the update and for the awesome work!
[Nexus 5 Original Android Development] neobuddy89:
Fresh install CM11 and try again, seems to be some user error.

Is anyone having any issues on latest nightly build?
[Nexus 5 Original Android Development] rachanta:
So far so good. No SOD, last few hours.
[Nexus 5 Original Android Development] Tikerz:
My phone alarm actually woke me up this morning! No SOD! *knock on wood*
[Nexus 5 Original Android Development] neobuddy89:
Thanks for the review.

This build with few more CAF updates will be finalized as stable release in couple of hours. :fingers-crossed:
[Nexus 5 Original Android Development] ChanceOfChange:
i use the latest ver not issues so far, but may i ask for this may we have a the kernel at stock settings at default and when we want so power we can use the profiles?

i say that cause i dont wanna chage settings in app i just want em kernel bassed! if is possible will be awsome!
[Nexus 5 Original Android Development] neobuddy89:
Ofcourse, profiles are meant to do so.
[Nexus 5 Original Android Development] ChanceOfChange:
profiles yes! but the all point the the kernel to be stock default as i cames! if is possible!
[Nexus 5 Original Android Development] styr:
Can you please point me to the root of the Sods? I seem to have the same problem on my builds and can't track it down. Thank you.
[Nexus 5 Original Android Development] EnginEAR:
Awesome news!

Thanks again for all the hard work!!!
[Nexus 5 Original Android Development] neobuddy89:
Patches removed from Chaos:

0097-fastcharge-New-enhancements

0114-hammerhead-gpiomux-Fix-observed-current-leak-while-b

0148-drivers-video-Fix-bug-with-backlight-dimmer

0187-drivers-video-clean-the-backlight-code

0203-drivers-wireless-Add-option-to-change-WiFi-power-mod

0205-drivers-misc-Add-BLX-driver-for-hammerhead

0210-fastcharge-Cleanup-and-fixes

I suspect fastcharge enhancement was the root cause. You may begin with reverting those.
[Nexus 5 Original Android Development] Tikerz:
Is Bluetooth performance/functionality kernel driven or in the ROM?

I noticed that CM11/Chaos doesn't send music artist/track info to my car stereo, but OmniROM/Franco does. Just curious.
[Nexus 5 Original Android Development] neobuddy89:
Both. Kernel + CM11.

I haven't touched bluetooth in the kernel, so you can check with ROM.
[Nexus 5 Original Android Development] toocool4all:
Sod on latest nightly and this time it was not in charging but let me check for few more hours or sod to pin point exact reason of causing it

Sent from nexus 5 SENSONIC HD rom
[Nexus 5 Original Android Development] Tikerz:
Post last kmsg.
[Nexus 5 Original Android Development] toocool4all:
Last kmsg
[Nexus 5 Original Android Development] rachanta:
SOD

SOD using Chaos-Kernel_v11.0-[03-25]-[00-29].zip while charging overnight. The screen was dead in the morning.

Syslog attached:
[Nexus 5 Original Android Development] daavid1995:
got SOD usig latest Nightly and fresh installed CM.

Used it for 24 hours and SOD was not at charging.

https://www.dropbox.com/s/aszcdag77lck7rz/chaos_last_kmsg

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] zeppelinmad4:
I know it was stated a couple posts back that bluetooth isn't touched in this kernel but I'm having difficulties with bluetooth in my car. I install a fresh build of CM11 and my phone connects to my car via bluetooth perfectly. I install a nightly of Chaos (10.2 constantly FC phone) and my phone will freeze when it connects to my car. After a couple of minutes of being locked, it will reboot and stay locked until the process repeats. I'll then restore the stock kernel and everything is fine again.
[Nexus 5 Original Android Development] rachanta:
[MENTION=3795148]neobuddy89[/MENTION], I am trying to compile my aicp hammerhead rom with chaos kernel.

I have made the changes required in my local manifest, and now have chaos kernel in my local repository after repo sync. (aicp/kernel/lge/chaos)

I have also make changes in device/lge/hammerhead/BoardConfig.mk on L111 & L112

TARGET_KERNEL_CONFIG := kernel/lge/chaos/arch/arm/configs/hammerhead_defconfig

TARGET_KERNEL_SOURCE := kernel/lge/chaos

I get the following error:

ra:raop rax$ brunch hammerhead

including vendor/aicp/vendorsetup.sh

Looking for dependencies

Adding dependencies to manifest

Traceback (most recent call last):

File "build/tools/roomservice.py", line 223, in <module>

fetch_dependencies(repo_path)

File "build/tools/roomservice.py", line 212, in fetch_dependencies

add_to_manifest_dependencies(fetch_list)

File "build/tools/roomservice.py", line 128, in add_to_manifest_dependencies

existing_project = exists_in_tree(lm, repo_target)

File "build/tools/roomservice.py", line 55, in exists_in_tree

if child.attrib['path'].endswith(repository):

KeyError: 'path'

** Don't have a product spec for: 'aicp_hammerhead'

** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

What else is required to compile with chaos kernel instead of stock? Please guide me.
[Nexus 5 Original Android Development] A_Button117:
SOD happened again, 3/23 pac nightly, 3/25 chaos nightly
[Nexus 5 Original Android Development] neobuddy89:
Have you compiled aicp before? Do you have device tree for same? Why are you compiling with ROM?

Also kernel config path should be

kernel/lge/chaos/arch/arm/configs/chaos_hammerhead_defconfig
[Nexus 5 Original Android Development] rachanta:
Yes. I am running my own compiled ROMs the last 2 days.LorD ClockaN feels I done everything right. I need to make clean. Will check config path after I am back from my walk and on my PC.

[MENTION=3795148]neobuddy89[/MENTION] I have made the change to /kernel/lge/chaos/arch/arm/configs/chaos_hammerhead_defconfig

..but still get the same problem

I am compiling with rom to have some fun...and not need to download and flash kernel updates from you all the time. I will get my stuff from https://github.com/neobuddy89/hammerhead_kernel_caf whenever I repo sync.
[Nexus 5 Original Android Development] Tikerz:
I have the same problem with CM11 and Chaos. Try Elementalx and see if that fixes your problem. It works for me. I think it might be the kernel too.
[Nexus 5 Original Android Development] neobuddy89:
Chaos-Kernel_v11.0-[03-26]-[21-35]

* Updates and fixes from CAF

* Backport epoll updates from 3.14 mainline kernel

* Revert reduction of reduction of retention voltages
[Nexus 5 Original Android Development] zeppelinmad4:
Thanks for the reply. I prefer Chaos but I will Elementalx.
[Nexus 5 Original Android Development] rachanta:
8 Thanks exhausted. :good:

Will try tomorrow morning.

Cant take chances with alarms not going off because of SOD as it happened yesterday while the phone was on charging. I leave the phone to charge overnight to start the day with 100%.
[Nexus 5 Original Android Development] chaoszero112:
2 SOD logs from today. Don't know that they'll help now that there is a newer version, but here you go.

https://www.dropbox.com/s/cf4ya86ucrbk8vj/chaos_last_kmsg1

https://www.dropbox.com/s/ud58oiewkoap1nq/chaos_last_kmsg2

Bootloader d
[Nexus 5 Original Android Development] neobuddy89:
There are fixes deployed, I am not sure if they are related but please give a try to latest version.

Last_kmsg is not useful and I am not getting these issues. :(
[Nexus 5 Original Android Development] EnginEAR:
Just experienced SOD... Not connected to charger...
[Nexus 5 Original Android Development] neobuddy89:
Irrelevant but can you switch to previous baseband and check?

I will flash your baseband once I am back home.
[Nexus 5 Original Android Development] neobuddy89:
Are you guys setting up alarm?
[Nexus 5 Original Android Development] modyt:
Yeah. My alarm is always on. And just had an sod.
[Nexus 5 Original Android Development] rachanta:
My alarm is always on as well.
[Nexus 5 Original Android Development] chaoszero112:
I have alarms, but they are not enabled when I experience a SoD. So technically no alarm. I just experienced another one a second ago. March 26 aicp and March 26 Chaos. Bootloader still HHZ11d. Was not on the charger (was just sitting face down on my desk).

Something I have noticed: This time, and a few others, it SoD'd after the screen timed out. Normally I turn off the screen with the button, but if I'm preoccupied I just put it down without turning off the screen. This has resulted in a SoD at least 3 times.
[Nexus 5 Original Android Development] neobuddy89:
AICP, I haven't tested. CM11 lately had lot of changes in Ramdisk, I am not sure if AICP has changed it or not.

Is anyone with latest CM11 and last Chaos nightly there?
[Nexus 5 Original Android Development] Vanhoud:
Random reboot while attempting to watch a video

https://www.dropbox.com/s/ghh0fkhyg4fjwmg/chaos_last_kmsg
[Nexus 5 Original Android Development] rachanta:
Is there a recommended way to reference chaos while building my own ROM? [MENTION=3795148]neobuddy89[/MENTION], I have tried your solution in an earlier post. but got same result - build gets interrupted - some path issues, and question if I have the right repo.

I have no problem in building stock AICP from source.
[Nexus 5 Original Android Development] mo976:
Always using the latest CM nightly with the latest chaos and no sod/alarm etc issues. I use the alarm every morning but I also leave my phone on the charger overnight with the clock night mode enabled so that may be why I have no problems.
[Nexus 5 Original Android Development] neobuddy89:
Thanks for report. Let me check my updates for VIDC and get it fixed.

Can you please post interruption message you are getting?

I am using Chaos with CM nightlies only and never had any of the issues.

For those who posted SOD issues, are you using latest CM11 nightlies?

There were random reboot issues earlier with Chaos + AOKP/AICP and this now seems to be converted in SOD issue.

----------

If anyone is interested in my settings of Chaos via NXTweaks... it's here

(No stuttering as in CM, noticeably faster, may consume little more battery)

Default Profile +

PE WQ: Enabled

Overclock: 2.576

Boost: 100

I/P Boost: 120

Boosted CPU: 1 core

MAX CPU: 4 cores

Default Governor: Intelliactive

IO Sched: ROW

Voltages: Stock

KSM: Enabled (This saves me 60 MB of memory usually)

Wake Control: Disabled

Sound Profile: Quality

Gentle Fair Sleepers: Disabled

Dynamic FSync: Enabled

Fast Charge: Disabled

Color Profile: Piereligio TrueRGB v7
[Nexus 5 Original Android Development] toocool4all:
Last nightly is awesomely stable. No sod, using since 24 hour
[Nexus 5 Original Android Development] kkk-sgs2:
No issues with aicp since my last posted logs for 2 months. Always last nightly of Rom+ kernel.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] rachanta:
I just built aicp ROM from source with chaos kernel from source. I have had 2 reboots in the last 15 minutes. What could be the problem [MENTION=3795148]neobuddy89[/MENTION]?

Edit: here is the link to my syslog: https://www.dropbox.com/s/eimlaakczezsy3w/2014-03-28_23.47.zip
[Nexus 5 Original Android Development] neobuddy89:
AICP and CHAOS will have different Ramdisk. That can be your culprit.

Checking your logs.

Meanwhile, please try below nightly:

Chaos-Kernel_v11.0-[03-28]-[23-49]

* Sync VIDC with CM11

* Revert some of ALARM conflicting updates
[Nexus 5 Original Android Development] rachanta:
Ok I will try the new build and report, but what I do about ramdisk? :confused:

Installed Chaos-Kernel_v11.0-[03-28]-[23-49]

Booted OK,, will check for SOD. I am going to leave the phone charging overnight and I do hope I will get my alarms.
[Nexus 5 Original Android Development] ker0ltjuh:
With the latest nightlie I got one SOD on crDROID rom when I just had the alarm set and turned of the screen. I haven't experienced a SOD before.
[Nexus 5 Original Android Development] Vanhoud:
Provide debug log
[Nexus 5 Original Android Development] rachanta:
Latest nightly: No SOD so far. Alarms worked well. Phone was on charging.
[Nexus 5 Original Android Development] doubleohseven:
[MENTION=3795148]neobuddy89[/MENTION] Dude I love your kernel. I don't know if this has been asked, but have you considered making it for the Nexus 7 as well? I'd absolutely love that.
[Nexus 5 Original Android Development] neobuddy89:
SOD confirmed..

Kept overnight charging with data off, alarm on. Similar last kmsg as posted before. I am looking into it.
[Nexus 5 Original Android Development] neobuddy89:
So here is what we can do to get rid of SOD without workaround:

1. I will be posting some test builds, testing myself.

2. These test builds will have reverted batch of commits.

3. If you wish to help, you can test along and post your chaos_last_kmsg as soon as you face SOD mentioning test build no.

4. This should help to track down culprit.

5. This should also help me to group stable commits.

If you don't wish to test, I would suggest rollback to a stable nightly version (someone posted version no. pages back) or switch to stock kernel.

Test Build #1:

http://www.androidfilehost.com/?fid=23329332407582420
[Nexus 5 Original Android Development] rachanta:
Installed with AICP. Looks good so far. Pocket mode worked well when I took it out of the pocket, active notifications lit up. No SOD. Have you updated repository with this? I would be doing my next build referencing chaos from github in the next half hour or so implementing [MENTION=1184673]LorD ClockaN[/MENTION]'s suggestions on mpdecision bin.
[Nexus 5 Original Android Development] Vanhoud:
Last stable no SOD nightly was chaos-Kernel_v11.0-[03-13]-[05-51].zip
[Nexus 5 Original Android Development] rachanta:
I copied chaos kernel enabled ROM init.d folder content 01sysctl from a ROM on which I installed the last test build. I corrected the mpdecision file name in system/bin. These were LorD's suggestions to get my chaos included build to work. No success. The ROM boots. Works normally. Instead of sleep it reboots

Are there any scripts included in chaos zip
[Nexus 5 Original Android Development] neobuddy89:
#1 failed.

Test Build #2: http://www.androidfilehost.com/?fid=23329332407582573

I will really like to thank all those helping out by sending me logs in PM/Topic.

Please make sure, you are on CM ROM before you report any log.

[MENTION=1863016]rachanta[/MENTION]: Let me first fix SOD issues for all. Repo is updated as per latest build.

If you need ramdisk I am using, you can send me PM.
[Nexus 5 Original Android Development] MauroG:
How you do to get those SOD? I've been using chaos for weeks with aicp and have not gotten any SOD

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] neobuddy89:
Same here. Not all devices are same. There must be some h/w related code which is not suitable for few chips.

I got one SOD in three weeks. And there are couple of users who get frequent SODs.

So lets resolve for them.
[Nexus 5 Original Android Development] MauroG:
Should not there be a log with EVERY thing as h/w and s/w?

Cause I'm in 28/3 nightly aicp and latest nightly chaos (not test build) with 14/03 aicp gapps. And I neither have kernel related problems like sod nor those bugs people are getting with aicp like navrings, bt and so on...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Vanhoud:
[MENTION=3795148]neobuddy89[/MENTION]

I just experienced some severe graphical glitches on my screen using the latest nightly not test build. I went to recovery, flashed the last stable nightly then rebooted and then captured the debug log

https://www.dropbox.com/s/yuqz6m6z1xwhpk6/chaos_last_kmsg
[Nexus 5 Original Android Development] neobuddy89:
What ROM is this? Why is mpdecision being used in this ROM?
[Nexus 5 Original Android Development] Vanhoud:
It's CM. Not sure about the mp
[Nexus 5 Original Android Development] rachanta:
Test build 2 installed on my working aicp build (which I built with stock kernel). Will report on SOD. BTW I had no sod with test build 1.

mpdecision is used by chaos. My aicp has mpdecionRENAMED in system/bin and a 99mpdecRenamer, 00start, and 01sysctl scripts in etc/init.d.

After I flash chaos: system/bin has mpdecision and init.d has only 01sysctl.

This means chaos uses mpdecision, unlike the stock n3o-hammer kernel that aicp ROM uses.

Edit: Test build working well last 3.5 hours with freshly repo synced and built AICP.

No SOD or sluggish lock screen start on power button press.

Is there anything else to be tested [MENTION=3795148]neobuddy89[/MENTION]?
[Nexus 5 Original Android Development] neobuddy89:
Mpdecision is not used by Chaos. Please rename it manually to something like Mpdecisionxyz.

Right now only SOD needs to be tested. There maybe little freeze and reboot due to scheduler throttling which will be fixed as soon as I put all commits back.
[Nexus 5 Original Android Development] rachanta:
Good clue. Ramdisk info and file awaited