yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] alb3rtt:
Just had a freeze after choosing ondemand as awake and sleep governor on beta 4. Stock rom. Was listening to music while it happened, however, it was about 40 minutes into listening the music so its not occuring as quick as before.

Logs: https://www.dropbox.com/s/9zlez1x56pkau2p/chaos_logcat

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

https://www.dropbox.com/s/1uolmdsonwkvq1f/chaos_debug
[Nexus 5 Original Android Development] Jur1nator:
Stays stuck on Google logo with the newest cm nightly (27.1)

There seem to be some general problems with custom kernels and the new build though
[Nexus 5 Original Android Development] alb3rtt:
:mad:
[Nexus 5 Original Android Development] Jur1nator:
Okay, I usually always read the whole post, but seems I was pretty blind this time.. Shame on me.. Sorry neobuddy... Keep them betas coming :)
[Nexus 5 Original Android Development] Jones_mcfuzz:
Happy to report that Beta 4 works flawless on latest Cm11 Sanity Harp rom.. And also with the Dalvik optimization.. Thank you so much for the hard work you put into this!
[Nexus 5 Original Android Development] gavin-phelan:
Not working on latest pac rom

Hit Thanks if I Helped

~Codename Android~
[Nexus 5 Original Android Development] srps:
v10b4 seems to be working fine on Purity ROM. I even undervolted a bit.
[Nexus 5 Original Android Development] danarama:
Had 9.2 voltages applied to 10b4. So far no freezes / reboots. Will start to play tomorrow. Could -50 on 9.2
[Nexus 5 Original Android Development] topgeardave:
Boots fine on cm11 24th nightly and is perfectly stable with - 40uv! Good work neobuddy! Battery is still the same as v9.2 but can't say for definite as it hasn't been a day yet.
[Nexus 5 Original Android Development] neobuddy89:
Last kmsg log is same as one you submitted before. Are you sure this is latest one?
[Nexus 5 Original Android Development] iraqi92:
this is my log ...i feel my phone not smooth and have some lag

https://www.dropbox.com/s/e2n8z31imc0dfxw/chaos_last_kmsg
[Nexus 5 Original Android Development] neobuddy89:
Chaos 10.0 Beta 5: http://d-h.st/wcr

Changes over Beta 4:

* Add kernel compatible CAF Hwcomposer to support latest CM Roms as well as stock based ROMs. Thanks to [MENTION=1188493]Calkulin[/MENTION] for heads up. :good:

* Ondemand governor cleanup and restore.

* Disable CM11's MSM entropy seeder - need to test now if that was battery hogger.

* We actually don't need above entropy seeders as we have ARCH_RANDOM for random no. generation at earlier boot to supply entropy and we have implemented fixes to prevent entropy depletion. :victory:

Thanks to all testers/users of beta kernel series. :cowboy:

P.S. This is a CAF Kernel compatible with all ROMs. If you flashed this kernel and wish to revert back to previous or other kernel, you need to flash ROM again and then kernel of your choice.
[Nexus 5 Original Android Development] buster041284:
You mate are pure awesome.
[Nexus 5 Original Android Development] yyz71:
This new beta is not playing nice catcalysm:confused:

---------- Post added at 07:26 PM ---------- Previous post was at 06:57 PM ----------

NVM:good:
[Nexus 5 Original Android Development] Mtk87:
Kernel 10 is the first kernel having problems :/ don't know what happened, but I'm having screen freezes followed by reboot of the device. I'm setting the nxtweak app as i always did: maximum oc, intellidemand + row for screen on, frandom, gentle and dynfsync on.

Only difference is voltages (which look like to be lower that before)
[Nexus 5 Original Android Development] alb3rtt:
Well here's a new one last kmsg and debug from a fresh freeze.

https://www.dropbox.com/sh/n1xdc8mp6qm5yxq/uEHGTqJc_5

And while i was selecting stock governors, i got another freeze...

These are all on b4. Flashing b5 now.
[Nexus 5 Original Android Development] danarama:
Try upping voltage. [MENTION=3795148]neobuddy89[/MENTION] posted the 9.2 voltages for me a few pages back. Also Max overclock is higher on 10. Try drop it down 1 step. Not all CPU can handle that.

Running sweet on max 2.496 and 9.2 voltages. No freezes, no reboots
[Nexus 5 Original Android Development] Mtk87:
Increased voltages by 15mV, crashed and rebooted while alarm clock ringed. Crashed and rebooted instantly after lockscreen from previous reboot. Installed b5 and had

bootloop. I'm on cataclysm. Had to fall back to 9.2 which for me worked like a charm. I'm sorry I can't help trying this beta, but, as I'm unable to create a log because of continuous reboot, there is no sense in keeping the beta :/
[Nexus 5 Original Android Development] alb3rtt:
B5 freeze on stock ROM. Ondemand governor still unstable. Stock governors (interactive and conservative) are fully stable though

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

https://www.dropbox.com/s/1uolmdsonwkvq1f/chaos_debug

Google play music settings are now force closing. Tried wiping their data. Here is a log. I needed to change the eq today and noticed the fc.

https://www.dropbox.com/s/9zlez1x56pkau2p/chaos_logcat

Started from b5.

I'll try upping voltages but I doubt it will fix the freezes with on demand since stock governors are rock stable.

Ill test its affects on ondemand after school, i need my phone to wake me up tomorrow for school so ill leave it on stock governors for now.
[Nexus 5 Original Android Development] gavin-phelan:
Cant get into app it just shows a white screen?I wiped data and rebooted twice still nothing?

Hit Thanks if I Helped

~Codename Android~
[Nexus 5 Original Android Development] alb3rtt:
What app?
[Nexus 5 Original Android Development] gavin-phelan:
NXTweaks

Hit Thanks if I Helped

~Codename Android~
[Nexus 5 Original Android Development] alb3rtt:
Are you rooted and is busybox installed?
[Nexus 5 Original Android Development] gavin-phelan:
Yes I've been running it for for over a month
[Nexus 5 Original Android Development] SunamY:
Wanna test it :)))

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] danarama:
reflash kernel?
[Nexus 5 Original Android Development] gavin-phelan:
this is my problem and im rooted

Hit Thanks if I Helped

~Codename Android~
[Nexus 5 Original Android Development] danarama:
Did you reflash the kernel?
[Nexus 5 Original Android Development] gavin-phelan:
Yes I even cleaned flashed different roms too

Hit Thanks if I Helped

~Codename Android~
[Nexus 5 Original Android Development] jacqueline_du93:
This happened to me when dirty flashing PA BETA4, had to reflash the kernel a second time for it to work.
[Nexus 5 Original Android Development] imageMaster:
Why we're need to reflash whole ROM instead only a kernel (e.g. stock kernel)? Thanks

Отправлено с моего Nexus 5 через Tapatalk
[Nexus 5 Original Android Development] DenyDarko:
I've got numerous spam with the following using CM11 & Nexus5:

I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting
I/auditd: Starting up
E/auditd: Failed on audit_set_pid with error: Protocol not supported
I/auditd: Exiting

And this one:

E/PowerHAL: sync_thread: failed to send: No such file or directory
[Nexus 5 Original Android Development] iburtondroid:
when starting NXTweaks, getting Unexpected error

Chaos 9.2
[Nexus 5 Original Android Development] danarama:
Because it changes things.

Then what happens? Did you search the thread?
[Nexus 5 Original Android Development] iburtondroid:
then it starts, and it seems it is working, just not clear why it is happening. I read that some users are facing the same issue.

Just updated to latest beta 10 , cleared data and cashe from NXTweak app, but the same. I have noticed that by default CPU is undervolted, is this ok? (it was not like that on 9.2)
[Nexus 5 Original Android Development] danarama:
The error is irrelevant if the app works. I've had the error since I started using chaos at 8.0

The voltage structure has changed on 10. Personally it's too low for me. I set my voltages to 9.2 then undervolted by 25. On 9.2 I could undervolt by 50 though
[Nexus 5 Original Android Development] iburtondroid:
it seems that when I want to reset setting in NXTweaks, it is not working, settings are the same as they were. Have you tried to reset to defaults?
[Nexus 5 Original Android Development] alb3rtt:
Works for me :confused:
[Nexus 5 Original Android Development] imageMaster:
10B5 works fine on latest Omni ROM. Almost no UI lags. But I'm wondering why CPU3 works on high frequency?

There is a simple browsing mode.
[Nexus 5 Original Android Development] danarama:
No. I just use the backup and restore fuinctions
[Nexus 5 Original Android Development] iburtondroid:
don't know, feel something is wrong...here are some screens

why are the sliders set to maximum? are they set like this on your phone?
[Nexus 5 Original Android Development] alb3rtt:
thats odd but they aren't in place since the control switch isnt ticked.
[Nexus 5 Original Android Development] iburtondroid:
yes, I didn't turn it on....but strange is that it is UV by default and sliders are not in place...and now I can't back to stock voltages, probably only turning switch on and place slider for each frequency to default value. Is there any other way to restore default valuse (except flashing ROM and kernel again)? I have flashed kernel again but it is the same. I have also installed Android Tuner but it is just for monitoring CPU, nothing changed there (regarding CPU). Could it be that it interfears somoehow?

For error on starting NXTweaks, I was thinking, there should be an add on 1st screen where it says about donation, but there is no one, maybe it gives an error because of adaway?
[Nexus 5 Original Android Development] RhapsodyK:
Does anyone have flashed the new binaries driver update? I just wonder if it will affect the operation of Chaos Kernel as i believe the update is based on stock kernel.
[Nexus 5 Original Android Development] danarama:
Your voltages are stock for 10. It is not UV, it is stock for this kernel.

You'll have to manually set the 9.2 voltages if that is what you want.

Test turning on voltage control and see if you can move the sliders up.
[Nexus 5 Original Android Development] KarloHD:
I love this Kernel ;)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] kronflux:
hmm. seems flashing 9.2 breaks the current nightly build: cm-11-20140131-NIGHTLY-hammerhead

specifically - causes phone to be unable to boot.

I can't be sure whether it is just the latest nightly or whether it's been happening for a few days, as I haven't updated in a few days.

Also causes some graphical glitches in PhilZ Touch Recovery 6.12.8

(the recovery is just a guess. at least, I haven't noticed the graphical glitch since flashing the stock rom/kernel), specifically - sometimes while installing a zip or navigating through the pages, it kind of flickers, and sometimes flashes all sorts of colors, like a broken LCD.

If someone could verify these issues, I'd appreciate it, maybe I've broken something by accident.

Still have the boot issue, but it turns out the recovery itself was in fact responsible for the graphical issues.
[Nexus 5 Original Android Development] abcdw654:
This is probably from the changes implemented in 27/01 nightly. Try flashing Chaos Kernel 10b5. [MENTION=3795148]neobuddy89[/MENTION] fixed the compatibility issue in that release.
[Nexus 5 Original Android Development] avalpert:
Bluesleep Wakelock

Anyone else having issues with bluesleep wakelock and bluetooth in general? I am on 9.2 and this is the one wakelock issue I still have (17hrs out of 26hr the phone was on) and I also have had intermittent issues with it connecting to the bluetooth in my car - even when it is connected at times it picks up on the handset and won't switch to the bluetooth and yesterday it wouldn't even let me turn bluetooth on.

Any thoughts?
[Nexus 5 Original Android Development] kronflux:
Works a treat! thanks :)
[Nexus 5 Original Android Development] firewave:
Exactly, changes of experimental nightly 26/01 broke the 9.2 kernel. Version 10 beta is now a must.
[Nexus 5 Original Android Development] moksha51:
when under 90% , a reboot clears the battery resets to 0

I am using the Cataclysm ROM. I am seeing this issue and I am wondering if it is related to this kernel? (I flashed 9.2)
[Nexus 5 Original Android Development] neobuddy89:
Future plans for Chaos kernel:

1. Drop support for non CAF Roms.

2. 100 percent sync with CM11

Why CAF?

As all are aware we have got diversion with CM ROM started merging CAF patches which broke compatibility with stock kernels.

I have been trying to maintain support for both stock as well as CM11 but that results into no perfection for any one of them.

Also, going through the patches it can be easily inferred that CAF is more efficient in terms of stability, speed, power and many other things..

What about non CAF ROMS?

Apologies but I hardly find time to test on multitude of ROMs for compatibility. And am more CM based Rom fan than anything else.

You may opt for variety of kernels available in forums. :)

What to take care of?

While flashing Chaos, make sure you haven't modified any system files like flashing libraries to make non caf kernels compatible, moto x dalvik libs (those are not meant to use for us)

A CM based ROM built after 27th Jan would be good enough to give best experience with Chaos.

If you wish to kang support for other ROMs, you are welcome to do so. However, I may not able to provide additional support with same.

What else is gonna change?

Kernel will be more clean i.e. No files other than boot.img inside zip file. Modules like for exfat and frandom will be inbuilt and activated. NXTweaks will get auto installed after boot (it will get installed from Ramdisk)

Above setup is ideal setup for any kernel i.e. Not to kang with system files. Also it would be helpful for multirom users to share same kernel with compatible roms.

The basic aim of enhancing experience of all ROMs has been changed to enhancing that of CAF / CM11 ROMs.

I am sure many of you wont like this decision for next updates, but its already high time maintaining the bridge. I have tried my best to explain the reasons associated with favoring CAF only. If you have something valuable to add, please go on. If you just gonna troll, move on.

Thanks for enthusiasm shown for era of chaos since version 1.

Next update tonight. CM based Rom users can request nicely to their favorite devs for incorporating latest CM updates.

Edit: next update is completely fresh code and no stutters at all. :)
[Nexus 5 Original Android Development] Akeel1994:
[MENTION=3795148]neobuddy89[/MENTION]

will the next version work with omnirom? thanks!
[Nexus 5 Original Android Development] :
He said CM /CAF based ROMs.

Sent from Nexus 5 on Slimkat
[Nexus 5 Original Android Development] Akeel1994:
Yes, I know. But I am not sure if omnirom has caf support, too. That is the reason why I am asking.
[Nexus 5 Original Android Development] bvt-1:
So, no more stock/aosp-kernel???

... N5 rulez ...
[Nexus 5 Original Android Development] Akeel1994:
no/nein bvt
[Nexus 5 Original Android Development] bvt-1:
Oh, sorry, hanging arround on wrong page :o

Okay, only CM ... and no more Chaos-kernel for me .. dont like CM ...

All the best for you, neobuddy89 ;)

... N5 rulez ...
[Nexus 5 Original Android Development] neobuddy89:
Requesting all to avoid such replies.

Base rule - CM and CM based.

Don't like, please move on.

Will it work on X?

Test yourself. 99% no.

Edit : best way to identify compatible roms, check link of kernel source of your rom.
[Nexus 5 Original Android Development] buster041284:
Keep up good work buddy iam just glad there is good kernel for CM based roms
[Nexus 5 Original Android Development] danarama:
[MENTION=3795148]neobuddy89[/MENTION] - thanks for all your work!

Please could you identify the OTG commits required to get a kernel up to the stage your kernel is at for me?

Thanks in advance
[Nexus 5 Original Android Development] blade_:
I have a little problem.. Sometimes I take the phone in my hands, and screen lights on, without press any button.. Is it a bug?
[Nexus 5 Original Android Development] danarama:
maybe phone was near a magnet. screen turns on / off when near magnets. It is design. Do tests with surfaces.
[Nexus 5 Original Android Development] Meakii:
Is pocket mode set to on in your ROM settings?
[Nexus 5 Original Android Development] blade_:
You are right my friend! Thanks! You know how can I disable it? I don't see in my rom (Slimkat) any option
[Nexus 5 Original Android Development] danarama:
No. all i can say is its the "hall effect" sensor. Maybe there is an app to disalbe sensors?
[Nexus 5 Original Android Development] blade_:
So it's a bug from Google.. Unacceptable..
[Nexus 5 Original Android Development] danarama:
No. It's not a bug at all. It's designed for flip cases with magnets to turn on and off screen. The phone is acting as it is supposed to.

Anyway, this is off topic
[Nexus 5 Original Android Development] blade_:
understand.then,i want to have an option about this..i have nexus,not an apple phone
[Nexus 5 Original Android Development] neobuddy89:
Here is the update:

Chaos 10.0 Beta 6: http://d-h.st/yas

*** Only for CAF based ROMs ***

*** CM11 Official Supported ***

** CM Derivative ROMs should have been built from updated sources **

Changes:

* Complete refreshed code from scratch

* Clean code, removed all unused garbage code

* In 100% sync with CM11 - CAF kernel ***

* Dropped support for stock-based ROMs

* Heavy performance improvement

* Kernel zipped clean - can be shared via multirom with compatible ROMs

* Reduced Panel Voltage - to save power when Screen on

* Reduced CPU DMA latency - more performance

* Fixes for Interactive governor

* Minor updates for Video driver, USB driver and MSM board

* Sync some latest updates from Android-kernel-3.4 common branch

* Removed UKSM - most part of the code is deprecated. If needed by someone, I can enable updated KSM

* EXFAT is no longer built as module instead it is inbuilt just like FRandom

* NXTweaks auto-installed on boot

* Entropy seeder of CM11 is retained at the moment (needs more testing)

* Sync Ramdisk with CM11 and specifications from Qualcomm

* Minor optimizations all over

* Updated to 3.4.78

Do not flash on non-CAF ROM. Works great with CM11 (post Jan 27).

DroidKang v18 is incompatible unless updated.

In case you are using compatible ROM and if you have flashed previous chaos, you need to first install ROM again (dirty flash should work) and then flash this version of Chaos. Thanks all. :)

*** Uploading new source code
[Nexus 5 Original Android Development] DenyDarko:
E/PowerHAL(242): sync_thread: failed to send: No such file or directory

E/PowerHAL(242): enc_boost: failed to send: No such file or directory

E/PowerHAL(636): sync_thread: failed to send: No such file or directory

E/PowerHAL(636): sync_thread: failed to send: No such file or directory
[Nexus 5 Original Android Development] neobuddy89:
Which ROM? Send debug logs via NXTweaks log generation tab.

Nothing such on 31st Jan CM11.

EDIT: That seems to be mpdecision warnings, let me confirm.. if so nothing to worry, we got msm hotplug driver.
[Nexus 5 Original Android Development] DenyDarko:
Related to this Perhaps ?

CM11 today's nightly , Nexus 5.

I had no "enc_boost" errors with beta 5 though.
[Nexus 5 Original Android Development] Ashish Bhalla:
This version wont work on stock rom with xposed ?
[Nexus 5 Original Android Development] neobuddy89:
The one you linked me to, is mpdecision.

So, it seems that error is logged because we have disabled mpdecision as well as disabled creation of socket for same in ramdisk.

In 30th Jan CM11, enc_boost error not there and it is logged only once or at max twice.

There is no need of mpdecision. mpdecision tend to consume more power than current msm_hotplug_driver.

These errors (should be called warnings) should be ignored.
[Nexus 5 Original Android Development] neobuddy89:
No, sir.

Only CM11 and derivative ROMs (if any)
[Nexus 5 Original Android Development] DenyDarko:
Good. You may add a FAQ for that :)

Another issue I found related to the NXTweaks:

Does not apply "Negative offset voltage":

02-01 22:41:34.215 I/com.gokhanmoral.stweaks.app.Utils(20276): [Running command:/res/uci.sh cpu-voltage 0 90]
02-01 22:41:34.305 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Error received: renice: invalid option -- n
02-01 22:41:34.305 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Error received: USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
02-01 22:41:34.315 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Line received: 90
02-01 22:41:34.475 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Line received: [%nexttweaks%]
02-01 22:41:34.475 I/com.gokhanmoral.stweaks.app.Utils(20276): [Finished command:/res/uci.sh cpu-voltage 0 90]
02-01 22:45:34.177 I/com.gokhanmoral.stweaks.app.Utils(20276): [Running command:/res/uci.sh cpu-voltage 0 70]
02-01 22:45:34.267 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Error received: renice: invalid option -- n
02-01 22:45:34.267 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Error received: USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
02-01 22:45:34.277 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Line received: 70
02-01 22:45:34.437 D/com.gokhanmoral.stweaks.app.Utils(20276): --> Line received: [%nexttweaks%]
02-01 22:45:34.437 I/com.gokhanmoral.stweaks.app.Utils(20276): [Finished command:/res/uci.sh cpu-voltage 0 70]

Not sure if you manage this app though :s
[Nexus 5 Original Android Development] neobuddy89:
Negative voltage offset requires calculation.

Thanks reporting, perhaps bash version in CM11 is old. I will get it replaced.

EDIT: It is working! You need to turn of Voltage master switch first, apply and then ur changes to offset voltages.
[Nexus 5 Original Android Development] DenyDarko:
Ah..!

Not my fault though:p

Check the screenshot and find the main switch. The box (when not ticked) is almost invisible:
[Nexus 5 Original Android Development] neobuddy89:
Blame your themer. :P
[Nexus 5 Original Android Development] dany20mh:
[MENTION=3795148]neobuddy89[/MENTION]

I got a random reboot ( 10b6 ) while the phone screen was off , here my last_kmsg
[Nexus 5 Original Android Development] DenyDarko:
It works fine here too :)

I've just missed the main switch box.

I use really low brightness on my device and I was unable to see it until you mentioned it and I searched more carefully.
[Nexus 5 Original Android Development] dany20mh:
[MENTION=3795148]neobuddy89[/MENTION]

In it just happen again , I hope these help you.
[Nexus 5 Original Android Development] blade_:
[MENTION=3795148]neobuddy89[/MENTION] really thanks for this kernel.but it make me sad that you stop support aosp roms..i dont understand why you choose cm and not aosp
[Nexus 5 Original Android Development] neobuddy89:
watchdog bites.

Send other debug files.

Need to check your settings.

These kind of reboots are tend to happen with very low voltages.

Is Dynamic FSync on?

Goto Profiles tab and load default profile. Please use default profile.

No issue since a day on default profile.
[Nexus 5 Original Android Development] neobuddy89:
I found CM-CAF more fascinating and more fruitful for N5.

AOSP has got lot of talented kernel devs/integrators around. :)

I can see many devs around are merging CAF kernel updates to test (including myfluxi - Omni ROM maintainer and franco), lets see if they come up with balanced solution.:good:
[Nexus 5 Original Android Development] DenyDarko:
I see you have N5 too.

My device is not stable even with -50mV. It causes reboots. Hammerhead does not appreciate undervolting very much as far as I can see.