yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] star_throne:
Could you try to report this issue on GitHub if it hasnt been already, as you seem to be more familiar with using it? lol. Hope we can get this fixed! The bug is really random, haven't got any drops in normal use for few days, but it has dropped few times when really "stressing" it, switching between wifi and data, 2G and 3G, and using pentest software

edit: And to clear things up, yes we do have this problem on CM13 dark rom build too, it cant be related to toolchains, setups, machines, personal configs or anything like that

Also, do you have link for the systemui thingy commit?
[Nexus 5 Original Android Development] kenshin33:
I don't think that has to anything with what you're doing. I 've had problemes with bluetooth since 2-3 builds ago (using cm sources, with no modification at all )
[Nexus 5 Original Android Development] Dark_Eyes_:
I'm pretty sure our problem comes from some commits for hammerheadcaf kernel. All builds, that is official cm13, myfluxi based or truesight based all have a common base for kernel and probably all have the same faulty commit. There are 13 commits on the official cm13 repo between may 30th or 31st that could cause that. It's the correct time period too. So, anybody here could try reverting all of those commits and test to see if it's indeed related to that?

I have contacted [MENTION=4152171]myfluxi[/MENTION] to ask for his help, hopefully he can shed some light on that bug.
[Nexus 5 Original Android Development] :
He maintains branches per day. Use an older one, compile and try.

Can't test because my internet is down plus I'm at work right now...
[Nexus 5 Original Android Development] myfluxi:
Interesting. I was under the impression, some crazy patching from this development branch went bad because I noticed some stalls and an occasionaly broken modem as well.

Are you sure it happend in this exact timespan? It might be this commit, that was very useful on ****ty bacon when I played with it but might be bad on hammerhead. Can somebody try to revert it and report back?

I noticed broken A2DP for some time as well. I sometimes use it to stream to my AV receiver and didn't bother to check where CM messed it up again...
[Nexus 5 Original Android Development] ssauger:
So kylon updates the blobs to MOB30M on his bitbucket.

[MENTION=4152171]myfluxi[/MENTION] or any other guy can tell me

ElementalX kernel was updatet with june security patch. If such security things affect the kernel, is there some automatic from cm that patch the kernels too, or must the device maintainer do this?
[Nexus 5 Original Android Development] myfluxi:
I will add these, bacon has a new set of hardenings as well.

But guys, remember you are carrying around huge security holes with your rooted devices and custom recoveries. The theoretical risk from these adressed vulnerabilities is sooooo small in comparision. Hacking is 99.9% getting ahold of the physical device and social engineering.
[Nexus 5 Original Android Development] :
@myfluxi Just saw your question on the previous site about reverting the commit. I'll do that and report back as soon as possible :)

EDIT:

Alright guys, synced my repositories...

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="myfluxi/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf-160602" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="myfluxi/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>

$ git revert --no-edit d24ce319

$ source build/envsetup.sh
$ brunch hammerheadcaf

Will let you know when the download is ready! :)
[Nexus 5 Original Android Development] kenshin33:
I noticed this week (I think, as I and time are orthogonal for all entent and puposes, we don't project on each others).

to add insult to injury, it only happens when I'm on the bus and far away from the computer, I tried to look in the logs by but I gave up.

in regards to the bluetooth problem :

the audio stops but the player keeps going for few seconds and then

com.android.Bluetooth crashs with this exception:

2016-06-08 03:10:42,ERROR,BluetoothDevice,Android System,
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.bluetooth.IBluetooth$Stub$Proxy.getRemoteClass(IBluetooth.java:1440)
at android.bluetooth.BluetoothDevice.getBluetoothClass(BluetoothDevice.java:1048)
at com.android.server.audio.AudioService.setBtScoDeviceConnectionState(AudioService.java:3103)
at com.android.server.audio.AudioService$2.onServiceDisconnected(AudioService.java:3304)
at android.bluetooth.BluetoothHeadset$2.onServiceDisconnected(BluetoothHeadset.java:1010)
at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:1229)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1243)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at com.android.server.SystemServer.run(SystemServer.java:303)
at com.android.server.SystemServer.main(SystemServer.java:175)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

That'all I could get while on a bouncing bus and a tiny screen.
[Nexus 5 Original Android Development] :
https://drive.google.com/drive/folders/0B4SRS2qeoUCyVE1xdDFOYUNWUWs

Here's the updated ROM. Built on Ubuntu 16.04 LTS with OpenJDK 7.

Repositories are listed in my previous post :) Please test, test, test & report back!
[Nexus 5 Original Android Development] :
last_kmsg

Sorry for double-, triple- and quad-posting but I got something new... installed my build and did some tests. It's still crashing ocassionally - like on installing/deinstalling apps, activating/deactivating bluetooth or airplane mode.

I managed to get the device to reboot two times - both ended with a watchdog_bite. I attached the last_kmsg...

EDIT: Log deleted
[Nexus 5 Original Android Development] KamilDM:
I can confirm this. Yesterday I flashed ROM with this kernel - cm-13.0-caf-160602 from myfluxi github and had a lot of freezes and reboots, all of them was the wdog_bark and wdog_bite. I was connected to my Wi-Fi, no mobile data, if it's significant. So something is broken but maybe [MENTION=4152171]myfluxi[/MENTION] already know about that
[Nexus 5 Original Android Development] myfluxi:
Seriously, you have no idea what you're doing. Don't use some random branch for builds that you share with the community. I stash crap in these branches for visual review and there is a lot of wild stuff there. If it's not on cm's repo it's not relevant and only serves my own purposes and maybe except for letting people know I'm alive and enjoying myself. Please don't annoy me with the xda drama stuff "oh noooz it's broken but please add the new shiny patches because I need all the latest".

Use cm's repo, cm-13.0-caf branch. And for now test minus the mentioned sps irq commit. For me, the stalls are gone. I'd be interested to get feedback for this exact usecase.

git fetch github

git checkout github/cm-13.0-caf

git revert eafcd7bad
[Nexus 5 Original Android Development] myfluxi:
I can repro this at will. It appears to be one of those dreaded A2DP timer problems that crpalmer adressed with amazing patches in cm 12.x, maybe we have to revive that stuff. A2DP is a mess on CAF (talking about codeaurora in general, not about our device).
[Nexus 5 Original Android Development] :
The disclaimer on the first page clearly states that no one but the end-user itself is responsible for his action if he decides to use the work provided here.

I can’t remember that I ever begged for a feature to be merged / implemented. You know best about what’s working, what’s not and when to merge it.

I thought you want to track it down to that specific commit and provided a build based on your latest work – nothing more, nothing less. Will try it that way as soon as I’m at home.

TL;DR: Most of us – including me – are willing to help. I provided a build, I provided a log and last year I even spent 5 bucks to you. All with the intention to support (whether it be your work or your private life) – and you just complain and rant. I was not aware that the build and the log was inappropriate or useless, sorry. I already deleted that stuff.
[Nexus 5 Original Android Development] Boal:
Guys, there's no need to fight. We're all on the same side here. myfluxi just warned against using random branches without review because they might contain code that is unstable. Keeping that in mind is good for everyone because otherwise the great people who provide builds are just wasting their time if the builds end up broken and the users would ultimately also suffer when they use faulty software.
[Nexus 5 Original Android Development] matt4321:
^^ This

Let's play nice everyone, thread cleaned a bit.

Forum moderator,

Matt
[Nexus 5 Original Android Development] :
[MENTION=4393511]matt4321[/MENTION] Thanks! [MENTION=4152171]myfluxi[/MENTION] Sorry again! Not knowing that these branches contain loads of untested stuff was definitely my fault. I was a bit upset in my last few posts...

Let's just forget about this whole wail - I'll try to publish a build with sources mentioned by myfluxi soon :)
[Nexus 5 Original Android Development] :
Second try...

So here's the build - purely based on CyanogenMod / TheMuppets repositories...

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>

$ git revert --no-edit eafcd7bad

$ source build/envsetup.sh
$ brunch hammerheadcaf

https://drive.google.com/drive/folders/0B4SRS2qeoUCyOS1uTGNGa0pNRnc
[Nexus 5 Original Android Development] myfluxi:
Whatever, try this: cm-13.0-20160609-UNOFFICIAL-hammerheadcaf.zip .

a) no more modem stalls, b) no more A2DP stalls (for me).
[Nexus 5 Original Android Development] Dark_Eyes_:
Was it the commit you pointed out earlier? Did it fix both modem and a2dp? I haven't got a chance to test a2dp, but modem seems fixed when reverting that commit! Thanks!
[Nexus 5 Original Android Development] myfluxi:
Yes and no.

If you want to try something out, build today's cm-13.0-caf-160610 branch. It has the offending sps commit but with sps patched up in order make use of these two important commits (1 and 2).

I'm convinced, the offending commit is correct after all, so let's do it.
[Nexus 5 Original Android Development] Dark_Eyes_:
Thanks man! I think I speak for everyone when I say : You rock! Thanks for keeping that beloved N5 up and running amazing!
[Nexus 5 Original Android Development] ssauger:
+1
[Nexus 5 Original Android Development] SH1M4BD3:
Om new on nexus bought it from my friend what am really intersted was CM CAf thanks [MENTION=4152171]myfluxi[/MENTION] the question is does the CAF is still updated, where i can download each released rom thanks
[Nexus 5 Original Android Development] nexzor:
Tausend Dank. Thank you. Just made a little trip and had no Stall or hardreboot. Perfect.

Dayli builds are on https://nyyu.tk/cm13/. Would suggest you to stay with the stock builds. myfluxi explayned why some posts ago.

Personally i will stay on myfluxis last build till he does a new one. last time i updated i got the trubble mentioned above.
[Nexus 5 Original Android Development] SH1M4BD3:
Thanks mate
[Nexus 5 Original Android Development] mmo.xda:
As usual, your build is working flawless. It's awesome.

You should commit all changes to cm kernel repository... It's great.

Kind regards

Enviado desde mi Nexus 5 CAF mediante Tapatalk
[Nexus 5 Original Android Development] SH1M4BD3:
Agree, 20160612 works fine here
[Nexus 5 Original Android Development] archish:
Link to the download please.
[Nexus 5 Original Android Development] :
https://nyyu.tk/cm13/

Anyone knows if the QuickBoot app works in CM-13? Back in the days of CM-12 I used it a lot.

I noticed the app itself being present in the /system folder - but it can't be enabled because the entry under Settings > Developer options isn't there anymore. Is it as easy as cherry-picking this commit? http://review.cyanogenmod.org/#/c/61690

EDIT: I'll try to add it to Settings tomorrow :)
[Nexus 5 Original Android Development] kenshin33:
seems like it is as simple as that. worst case (if it comiles) the setting won't appear.
[Nexus 5 Original Android Development] trwrt:
I synced and built from the CM kernel repo and TheMuppets blobs and I still have the data drop problem. Are the 6/12 success reports based on using myfluxi's kernel sources? I see there were a bunch of kernel commits merged today but I'm still having problems.
[Nexus 5 Original Android Development] mmo.xda:
I think there are two important commits that are pendding approbal:

msm: sps: check the BAM clock status before access a BAM

msm: sps: check new pending IRQs before exit IRQ handler

(He said they were important here)

I'm sure MyFlyxi will commit them ASAP and then CM repository will be up to date.

Regards
[Nexus 5 Original Android Development] simplicio11:
Commits present from 11.06 build (cm13_hammerheadcaf_with_myfluxi_kernel https://nyyu.tk/cm13/ ) ;)
[Nexus 5 Original Android Development] mmo.xda:
It's done!!!

Link

Thanks [MENTION=4152171]myfluxi[/MENTION] you're awesome

Regards
[Nexus 5 Original Android Development] Green Daddy:
After fearfully converting to stock after the official nightlies were dropped, I kept monitoring this thread and I am now back to CM13 CAF (20160609 by [MENTION=4152171]myfluxi[/MENTION] ) which is so much more fluent and simply awesome. No issues so far. Stock is so annoyingly slow and battery consuming imho.

However, I did notice that the "green screen" issue on screen mirroring to TV (in my case Panasonic) is still there. AFAIK logs and issue descriptions have already been provided on that one some time ago.

Anyone else still facing this issue?

Is there anything I can do to help with debugging this? New logs, things to try, ... ?

Or is it a "known bug" and it will/will not be fixed anyway...

Many thanks!
[Nexus 5 Original Android Development] ssauger:
Yeah, i just repo synced and do a build atm, I will post a link here when it is finished and my phone is running fine with it.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
</manifest>

cm-13.0-20160613-UNOFFICIAL-hammerheadcaf.zip

Miracast is still broken, i also hope that there will be a fix, but i don't know if anyone is working on it or trying to fix it.
[Nexus 5 Original Android Development] KamilDM:
Today I flashed a stock cm build from nyyu.tk/cm13 with latest myfluxi commits, and the problem with modem is still present. After couple minutes of using a cellular data, internet connection disappear and exclamation mark is next to signal indicator. Only hard reboot helps.

This build uses a kylon/proprietary_vendor_lge stuff from his bitbucket with updated blobs to MOB30M. I also flashed a build with older blobs from TheMuppets github but nothing is changed.

I am the only one with these old problems with recent builds?
[Nexus 5 Original Android Development] Dark_Eyes_:
Thanks for reporting. I also had the modem stall bug, but using another kernel that is based on the latest myfluxi's branch. That kinda confirms that the bug is still present in the original source. Hope [MENTION=4152171]myfluxi[/MENTION] can shed some light on this!
[Nexus 5 Original Android Development] :
I've got some data drops (exclamation mark next to signal indicator) and A2DP issues today. Device and kernel stuff based on CM sources, vendor/lge from myfluxi/proprietary_vendor_lge. Maybe both issues (network / bluetooth) have the same cause.

I was able to logcat a bluetooth crash while driving home from work... will send it to myfluxi.
[Nexus 5 Original Android Development] simplicio11:
Same here on cm-13.0-20160613-UNOFFICIAL_with_myfluxi_kernel
[Nexus 5 Original Android Development] Green Daddy:
Hard Reboot on 20160909 by [MENTION=4152171]myfluxi[/MENTION] using Twitter - last kmsg attached.

However, no issues with A2DP nor data on that one :)
[Nexus 5 Original Android Development] nexzor:
Also had a hardreboot on the 20160609 [MENTION=4152171]myfluxi[/MENTION] build. I was on my way through the city and after i reached my destination i found the phone on PIN screen.

here is the last_Ksmg:

installation was made over a build from https://nyyu.tk/cm13/ stock rom 20160608

if this could cause the problem i will make a clean install.

Modem is radio-hammerhead-m8974a-2.0.50.2.29

i´m on ja!mobil (german T-com)

http://pastebin.com/DdPbVcQG
[Nexus 5 Original Android Development] Slacker:
06/03 by myfluxi is the most recent stable build for me.
[Nexus 5 Original Android Development] Green Daddy:
mine was on clean install, but you had a modem_err while I had a watchdog bite. Do not know if this could be related...

Just in case: My provider is Austrian MVNO "HoT" with LTE enabled.
[Nexus 5 Original Android Development] simplicio11:
I try to change Cubic TCP algorithm to Westwood and seems the bug is gone.
[Nexus 5 Original Android Development] Dark_Eyes_:
I've been using westwood the whole time and I got data drop too. It doesn't seem to be related to TCP.
[Nexus 5 Original Android Development] rachanta:
Yes big problems there, also phone is not recognized when connected to PC. Unusable, but I am trying.
[Nexus 5 Original Android Development] EnginEAR:
Appreciation

Didn't mean any disrespect for your work. Quite the contrary. Was just reporting back...
[Nexus 5 Original Android Development] rachanta:
Never thought of it as disrespect. Happy that the problem is confirmed. I now have internal storage showing up, but network is still missing or goes missing even if it shows up briefly.
[Nexus 5 Original Android Development] banciii:
Btw. I have 2 strange issues with the latest build:

1) random soft reboots quite often (2-3/day)

2) 1 of my friends, who has CM12.1 snapshot, can't call me. It's ringing at him, but my phone does not do anythin, no sign of incoming call at all. However, if I turn off my phone during the call, he gets busy line signal, so it looks like the connection is being made, but my phone ignores it totally. :eek: I have never seen anything like this :eek: I mean, without blacklist. But I have not blacklisted him and I also can't find any blacklist feature yet. However, I see some kind of blacklist error in my logcat: http://1drv.ms/1QASDdi
[Nexus 5 Original Android Development] crian:
Can someone confirm the issue that themes applied to the navbar don't stick after reboot?
[Nexus 5 Original Android Development] nexzor:
Bugreport

I hope bugreports are allowed now. if not please ignore.

was playing 2048 than got a freez and a reboot.

last_kmsg and dmesg are attached

i´m on latest build with gapps_mm-Mini
[Nexus 5 Original Android Development] sachin123:
So my device is stuck in a bootloop.

I flashed the TWRP caf recovery, wiped data, cache, dalvik cache and system and flashed the ROM with the latest SuperSU.

I was coming from Stock Marshmallow, which was rooted with the latest ElementalX Kernel.

What have I done wrong?

Also, I didn't flash any gapps as well.
[Nexus 5 Original Android Development] minidou-77:
Did you install the Rom? Which version?
[Nexus 5 Original Android Development] sachin123:
I flashed the latest build

cm-13.0-20151111-unofficial-hammerheadcaf.zip
[Nexus 5 Original Android Development] minidou-77:
Can you try to wipe + install again?

Try installing gapps in the same time
[Nexus 5 Original Android Development] banciii:
SuperSU is the cause. Don't flash it, you don't need it, su is working in CM13 already (there are only a few incompabilities with eg. Greenify's screen off function, which I guess is because of the new busybox change).

Tapatalk-kal küldve az én Nexus 5 CAF-el
[Nexus 5 Original Android Development] sachin123:
I got it to work now.

Thank you so much!
[Nexus 5 Original Android Development] asparaz43:
Lately it recurred the black screen problem after an incoming call as the factory image :(
[Nexus 5 Original Android Development] rachanta:
Synapse Opening / Working

[MENTION=892369]EnginEAR[/MENTION], [MENTION=2482202]willybarca[/MENTION] and others

Here's my latest test kernel for myfluxi's cm-13.0-caf unofficial ROM: https://www.androidfilehost.com/?fid=24269982086996099

Synapse works

Internal Storage / mtp /adb shell works

No SIM problem solved; for internet you may still have to turn modem off/on after dialing *#*#4636#*#*
[Nexus 5 Original Android Development] EnginEAR:
Dirty...

Is dirty flashing okay?

I noticed that when I tried your previous kernel (which I dirty flashed) the sim card wasn't recognized also after dirty flashing back. Had to clean flash to get sim functionality back...
[Nexus 5 Original Android Development] rachanta:
I haven't tested it much. I flashed it over a fresh and clean cm-13.0-caf rom install along with the ROM.

Sequence

ROM

UKM

Kernel

Su 2.52

Boot

I rebooted a few times to check for boot stability and then posted it here, because here's where all the myfluxi rom users are.

However I think this time the usual dirty install over previous kernel should work. I think I have finally got the kernel template right. I used the same template for my aosp kernel and found the problem of internal storage not showing up that my kernel had with chroma rom also got sorted out.

Many thanks to [MENTION=4684315]flar2[/MENTION] for the great template that showed me how to call the init.racer.rc script containing [MENTION=3795148]neobuddy89[/MENTION]'s code for busybox path alternatives.
[Nexus 5 Original Android Development] EnginEAR:
Legacy of the Void

Power overwhelming!!!

(it works great!!!)
[Nexus 5 Original Android Development] EnginEAR:
VoBT

I use BT to connect my phone to my car's audio system.

Used to work perfectly on CM12.1.

The audio works perfectly still; however, conversations over BT are barely audible. As soon as I switch to the phone - all is fine, so it's definitely something with VoBT ("Voice over Blue-Tooth").
[Nexus 5 Original Android Development] kenshin33:
https://android.googlesource.com/de...a17eb28461a0583e6260d4782b2c9cc2a53dd13^!/#F0

a shot in the dark (i'll know soon enough)

but this might be of interest for changing Network Mode (LTE/3G)

yep, made all the difference!!!
[Nexus 5 Original Android Development] rolmos:
In case it helps, im on 0612 and am also getting data drops that I can only recover from rebooting.
[Nexus 5 Original Android Development] Boal:
And I'm on [MENTION=4152171]myfluxi[/MENTION]'s own build from 20160609 and everything's great so far.
[Nexus 5 Original Android Development] phoval:
The build from the 16/06 contains the fix for the modem data issue. https://github.com/CyanogenMod/andr...mmit/0698ff882840ec249de185bd3e5e23fb0c0ac99a
[Nexus 5 Original Android Development] SH1M4BD3:
Same bug DATA on myfluxi builds, today i flashed the regullar build to see if it does affected too or not
[Nexus 5 Original Android Development] HermannSenator:
True, I can confirm that in the latest stock build the data bug is gone! :D