yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] archish:
Yes I have the same issue. I assume the network switching is broken for all?
[Nexus 5 Original Android Development] lolobarjo:
I'm not in a zone with LTE but I has H+ in that moment

I've also tried but it's seems it's necessary to wipe /data/data to avoid bootloop. In any case, I think it's better to do a full wipe before installing CM13

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Nexus 5 Original Android Development] theodorius123:
I had the same, sudden reboot and log said "key pressed"...it wasn't a real reboot, I no need to enter SIM-Pin after reboot. Don't know what happend.
[Nexus 5 Original Android Development] Wout2426:
Do I have to delete setup wizard in recovery when I flash this to prevent not coming past it on first boot ?
[Nexus 5 Original Android Development] simplicio11:
nope.
[Nexus 5 Original Android Development] vikashhero:
Sounds like a case of "sticky power button"
[Nexus 5 Original Android Development] nagalun:
I know it's not useful anymore, (and with kernel 3.10 maybe coming it might fix some things) but whatever, I got something new (I think):

[24921.900607] ------------[ cut here ]------------
[24921.900670] kernel BUG at ../../../../../../kernel/lge/hammerhead/kernel/sche€@re.c:4309!
[24921.900762] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[24921.900851] CPU: 2 Tainted: G W (3.4.0-cyanogenmod-gaf199e8-01466-gd99d78a #1)
[24921.900929] PC is at __sched_setscheduler+0x394/0x3d0
[24921.901025] LR is at set_cpu_freq+0x110/0x258
[24921.901077] pc : [<c01c8ef0>] lr : [<c0197a94>] psr: 20000013
[24921.901077] sp : f0819ec8 ip : f0818000 fp : f0819f04
[24921.901171] r10: 00000000 r9 : 00000000 r8 : 001de200
[24921.901263] r7 : 00122a00 r6 : f0819f14 r5 : 00000000 r4 : f0de4c80
[24921.901316] r3 : 00000000 r2 : f0819f14 r1 : 00000000 r0 : 07ffff00
[24921.901411] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[24921.901504] Control: 10c5787d Table: 30e0c06a DAC: 00000015
[24921.901554]
[24921.901554] PC: 0xc01c8e70:
[24921.901603] 8e70 ebfffeba e5943030 e1a00005
0 Corrected bytes, 8 unrecoverable blocks
Boot info:
Last boot reason: wdog_bite
[Nexus 5 Original Android Development] basti84:
hi,

well this looks nice but for the first test i miss some features:

quick pin unlock

"Silent Mode"... ithought it would be back in 6.0.x?

thank you
[Nexus 5 Original Android Development] davwman:
For the love of god please don't stop developing this! This is the fastest, smoothest thing I've seen yet!
[Nexus 5 Original Android Development] d1n0x:
Quick PIN unlock will not be included anymore because it is just a messy hack and doesn't provide any real advantage (so you have to press one more button, boo hoo)

Silent mode is there. Just press the DND tile and select the mode you want.
[Nexus 5 Original Android Development] djalfy:
If you really need quick pin unlock check out gravitybox mm. It does that and many other things.
[Nexus 5 Original Android Development] Ajfink:
Personally, the quick unlock was one of my favorite things.
[Nexus 5 Original Android Development] Playe:
You can restore that functionality with xposed and gravity box. Just make sure you turn off the rest of gb's features to avoid conflicts.
[Nexus 5 Original Android Development] davwman:
Not sure why, but, I don't get the WiFi bug on this but on stock images I do. Awesome work! Getting 5 hours sot with pretty hard use on a brand new nexus 5 is more than I could ask for.
[Nexus 5 Original Android Development] archish:
Can you do me a favour and install battery monitor widget and tell me what is the voltage when fully charged up. I am getting 3 hour SOT on my 2year old nexus. Not sure if the battery is aged much.
[Nexus 5 Original Android Development] killer618:
How is the battery life in general with CM13?
[Nexus 5 Original Android Development] davwman:
Will do. But as of right now I'm at 55% and 3.833 volts
[Nexus 5 Original Android Development] ssauger:
Around 4360 mV @ 100%

sent from Nexus5
[Nexus 5 Original Android Development] maddes1402:
Hi everybody,

I've used Cm caf since release and don't wanna use anything else cos I'm addicted to the smoothness and battery life of it.

I'm sorry for offtopic but can anyone recommend an app for chromecast which can make use of my pictures stored in my Google photos app? Connecting google photos to chromecast or my Sony android TV just give a feedback of a black picture for several weeks.

Thank you,

Regards Matt

Gesendet von meinem Nexus 5 CAF mit Tapatalk
[Nexus 5 Original Android Development] scrack26:
I use AllCast for this since Google Photos not working. Cheers!
[Nexus 5 Original Android Development] Molice:
Thank you for this. Running your cm-13.0-20160130-UNOFFICIAL-hammerheadcaf.zip as smooth as butter. Dirty flashed over myfluxi's 20160122.
[Nexus 5 Original Android Development] happiness4u:
Does the new builds that are being uploaded by you guys got the kernel updated? Or it's just pure CM commits?
[Nexus 5 Original Android Development] kylon:
just another build...

http://www.filedropper.com/showdownl...-hammerheadcaf

(yea, it s old)

src : device - kernel
[Nexus 5 Original Android Development] archish:
Any idea of the mi band Bluetooth pairing issue is resolved in CM?

Both unofficial download links seem to be super slow.
[Nexus 5 Original Android Development] playitlouder:
http://nyyu.tk/cm13/

This server is fast enough (not mine)
[Nexus 5 Original Android Development] archish:
Any idea which Kendal source is being used?
[Nexus 5 Original Android Development] playitlouder:
[MENTION=2833355]phoval[/MENTION] can probably answer that question ;)
[Nexus 5 Original Android Development] phoval:
I use only pure CM sources, eg: kernel, device

FYI, new build is up : https://nyyu.tk/cm13/cm-13.0-20160204-UNOFFICIAL-hammerheadcaf.zip
[Nexus 5 Original Android Development] asparaz43:
I take this opportunity to thank you for sharing your work ;)
[Nexus 5 Original Android Development] Molice:
Thank you. Running your 0203 build smoothly, flashing 0204 shortly.
[Nexus 5 Original Android Development] ssauger:
Also have to say, thank you!

Is anyone able to look why miracast isn't working and maby can fix it on the CAF builds? Its' the only issue i got with CAF. Was some day's on AOSP, but it's not the same ;)
[Nexus 5 Original Android Development] ASHURiCAN:
Thank you very much, I use your builds every day and they are really great ? ! Thank you again! [emoji4]

Ah je viens de le voir et donc voici en français : Merci beaucoup l'ami ! [emoji6]
[Nexus 5 Original Android Development] mmo.xda:
Another one using your builds.

Thanks a lot for your effort.

Regards

Enviado desde mi Nexus 5 CAF mediante Tapatalk
[Nexus 5 Original Android Development] djalfy:
Google camera crash

Does anyone else get a crash in google camera when stopping video recording? It usually happens to me after taking a photo and then switching to video recording. Here are the logs: http://www87.zippyshare.com/v/pJhD20Xu/file.html . This happens to me since the first official cm 13 build and these logs are taken from the latest unofficial build.
[Nexus 5 Original Android Development] ASHURiCAN:
Happens to me too :(
[Nexus 5 Original Android Development] montbazon:
Google decided to support Miracast nomore.
[Nexus 5 Original Android Development] ssauger:
Come on. It's working on every ROM beside CAF. Also on stock.

sent from Nexus5
[Nexus 5 Original Android Development] Sly_67:
TWRP 3 is out, any chance to make one for CAF .
[Nexus 5 Original Android Development] pavik62:
Unpack.
[Nexus 5 Original Android Development] Sly_67:
Thank, I'll try it ...
[Nexus 5 Original Android Development] ssauger:
You can fin it here in OP http://xdaforums.com/google-nexus-5/development/twrp-twrp-builds-modified-to-allow-t3107550
[Nexus 5 Original Android Development] asparaz43:
Just tried it, it works :D
[Nexus 5 Original Android Development] gautam_nexus:
I am tempted to try CAF builds, but if these builds are so good over the original cm builds then why were they dropped officially from CM?
[Nexus 5 Original Android Development] ssauger:
Cause the maintainer for hammerhead/caf left. We got a new one, but only for hammerhed, not hammerheadcaf.

http://xdaforums.com/showpost.php?p=64869310&postcount=907
[Nexus 5 Original Android Development] gautam_nexus:
is doing unofficial builds a viable option for the survival of caf based ROMs? hope somebody just becomes an official maintainer soon.
[Nexus 5 Original Android Development] happiness4u:
I need a quick round-up of the features of CM13 for our devices. What features was still implemented, working, or not working. I'm about to flash it later. :)
[Nexus 5 Original Android Development] funkyslap:
I know [MENTION=4152171]myfluxi[/MENTION] stopped developing on CAF but here it is another hard reboot (wdog_byte) while browsing with Opera. Maybe [MENTION=3334728]kylon[/MENTION] can help us?

http://pastebin.com/ZQvynHAh
[Nexus 5 Original Android Development] rachanta:
Myfluxi: https://github.com/myfluxi/android_kernel_lge_hammerhead/commits/cm-13.0-caf-160209

CM-13.0-CAF: https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/cm-13.0-caf

CM-13.0: https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/cm-13.0

Actually it seems hammerhead is not moving while hammerheadcaf is running.

Why is everybody saying that caf development has stopped when myfluxi and cm are more active than any custom kernel developers I am aware of for nexus 5 caf? Is there something only I am unaware of?
[Nexus 5 Original Android Development] ssauger:
Maybe some light at the end of the tunnel, a little hope for our beloved caf? I see you also develop kernel, could you help to maintain caf?
[Nexus 5 Original Android Development] rmbq:
Hi guys, this is a kernel with new wifi drivers, give it a try ;)

maybe they will solve chrome/fb issues, maybe not. maybe they are faster and more battery friendly, maybe not. let me know!

if they are better, i will commit them to CM repo.

my source code is here
[Nexus 5 Original Android Development] jugoslavpetrovic:
CAF?
[Nexus 5 Original Android Development] rmbq:
yes, it's the caf thread!
[Nexus 5 Original Android Development] jugoslavpetrovic:
Yea, sorry my question was faster then I realize that it is caf cuz at the moment I was kinda multithreading?

Thanks.

Umm, the img file, why not zip? Any cons or pros?
[Nexus 5 Original Android Development] :
Please read what he wrote.

Because he provided an image file. What's wrong with it? Flash it via fastboot or TWRP.
[Nexus 5 Original Android Development] Vk-dzK:
I can flash without wipe internal storage?

I can't backup why not have pc on moment :/

Thanks
[Nexus 5 Original Android Development] :
If you do a backup via TWRP it will be saved on your internal storage <- this partition isn't touched if you don't explicitly wipe it.
[Nexus 5 Original Android Development] Vk-dzK:
Thanks Man ;)
[Nexus 5 Original Android Development] Slacker:
[quote name="rmbq" post=65274086]Hi guys, this is a kernel with new wifi drivers, give it a try ;)<br [/QUOTE]

Used flashify, a couple of taps and a reboot and all is good so far.
[Nexus 5 Original Android Development] jugoslavpetrovic:
Flashed and stuck on bootanimation, reflashed racer over but same result, restored stock boot partition in twrp and all good. Dont know what could produce the issue, my config is in signature, I guess I will skip.
[Nexus 5 Original Android Development] mpena:
i have a question, why the button of play/stop of my headphones don´t work in this rom. (I have the xiaomi piston v3 and in others roms work perfectly.)
[Nexus 5 Original Android Development] kong:
Been using the kernel for two days, no reboot yet :good:
[Nexus 5 Original Android Development] djalfy:
Did it have any effect on the battery life?
[Nexus 5 Original Android Development] kong:
I'd say no difference for my daily usage :silly:
[Nexus 5 Original Android Development] eternal70:
Umm, sorry if this has been asked before. Is hammerhead pickup sensor didn't work properly ? I mean it takes too much time to turn on the screen after the pickup activity. Comparing to my old gnex with kitkat, hammerhead is far behind gnex on this case. Again, sorry if this is already a known bug, i'm quite new to hammerhead :D
[Nexus 5 Original Android Development] myfluxi:
Thanks to cyngns awesome firepower, the long lasting bug where the backlight came on sometimes with Ambient Display enabled, will be fixed soon.

And whatever you do, do not apply useless tweaks, updated drivers or compile with custom toolchains. This is useless snake oil and totally ridiculous. The occasional reboots for some are modem related, send LGE an email, they should update their stuff for current QCOM codebase... I am now 49 days without any errors where I had reboots every other day before. Look at the OnePlus One, check current QCOM kernel trees and all of those workarounds and see the ugly face of modem craziness, modems must die.
[Nexus 5 Original Android Development] xzr3b0rnzx:
wow really gd to know and thanks for your update!

it feels really nice to see you around!
[Nexus 5 Original Android Development] ssauger:
Thanks for your update. Is there any hope that miracast will work again on caf, or nobody cares about anymore?
[Nexus 5 Original Android Development] :
Does anyone else notice lags while scrolling in certain apps? It's not just single lags but more like... delayed/stuttering touch-response. I can clearly see it when scrolling in Google Play Music or WhatsApp conversations. Scrolling through contacts or pictures in my gallery works fine though.

Not sure if this has been asked before...

Search on xda-developers.com doesn't work for me right now and the app says it doesn't find anything in this thread containing the keyword 'scroll'.

Thanks in advance!
[Nexus 5 Original Android Development] basti84:
Hi,

i installed TWRP 3.0 CAF, CM 13 CAF and your Boot.img

works really great

Battery seems very stable at the moment

i will keep an eye on it

##edit

still looking good
[Nexus 5 Original Android Development] djalfy:
Yep. I can confirm that.
[Nexus 5 Original Android Development] :
[MENTION=4350782]basti84[/MENTION] Please don't discuss custom kernels here. Thanks! :)

[MENTION=6243698]djalfy[/MENTION] Thanks. I thought I was alone with that :P
[Nexus 5 Original Android Development] nagalun:
You could say the same about the unofficial builds, it is not a custom kernel in the way of features, but trying to fix the reboots and to improve the main kernel, I think that shouldn't be bad for this thread... right? :confused:
[Nexus 5 Original Android Development] basti84:
hmm ... not very kind

i just share my experiences with this kernel ... i don't see any discusson here!?

there are enough problems around with Nexus 5 and the WiFi-Bug so this could help someone like me ...
[Nexus 5 Original Android Development] :
Let me highlight this. Please let's only discuss about hammerheadcaf either purely built from CM sources or CM sources + myfluxis repositories.

Whoever wants to upload a modified build/kernel though, is free to share it here - as long as proper information (sources, cherry-picks, etc.) is provided.

By the way: If you want to discuss your modded build please use a separate thread :)

Please respect this. Thanks for reading! :)
[Nexus 5 Original Android Development] mmo.xda:
What build are you using?

Regards
[Nexus 5 Original Android Development] :
The builds from [MENTION=2833355]phoval[/MENTION] ( nyyu.tk/cm13/ ).

Do you have the same scrolling behaviour with your phone/build?
[Nexus 5 Original Android Development] mmo.xda:
Same builds.

Mine is from 12/02 (quite old)

And no lag at all.

You can see here (link) a screencast with a test case with Google Music. Toons of albums and songs. No lag from scrolling (only downloading time for album cover art).

Hope it helps.

Regards
[Nexus 5 Original Android Development] :
First off all thanks for taking the time to do a screencast!

When scrolling fast it's not that bad. It's most noticeable when scrolling slowly. Try to scroll up and down. When changing direction you can see a little delay/stuttering. At least it's not as responsive as scrolling in contacts or settings :p
[Nexus 5 Original Android Development] mmo.xda:
You're welcome, we all try to help :)

Finding bugs is better for all of us :)

Ok. I've tried again and, sincerely, I'm not able to feel difference, sorry :( :(

Here is the new screencast (link) with slow scroll and several direction changes.

Maybe, it something related to hide application top bar. When you scroll down top bar (music, artits, albums, and so) hides. Maybe is that transition that is not working right and you feel laggy??.

have you tried with no effects in "developer option"?

Maybe is something related to theme??

As you can see, I've changed theme to try with a different one and it seems (for me) exactly same behaviour.

Regards
[Nexus 5 Original Android Development] :
I tried to use stock theme and disabled animation.. unfortunately didn't help.

Then I installed FPS meter from Play Store and did a few tests. When scrolling in contact app it reaches 59 easily while it stays on 40-50 while scrolling in Google Play at the same speed.
[Nexus 5 Original Android Development] nexzor:
i don´t want to offend you but this polici would be rediculess.

The patch in this testkernel is similare to the testkernels myfluxi posted all the time her.

and it´s the first try to fix a bug since myfluxi "left". so please let people post such kernels. but if this gets to much, lets say more than 2 testkernels a week from different developers, this would clearly be a showstopper.

if the patch inside the kernel realy fix a problem the one who build it should submitt the patch to myfluxi and hopefully he is willing to integrate it in his repository.

A seperate Thread for each such Kernel would result in not using these kernels, becouse i think the most people wouldn´t rekognize them. So it would result in stopp of development.
[Nexus 5 Original Android Development] lcrponte:
Do you know what's also ridiculous? Talking about a fix for a bug that is not solved with an attempt that myfluxi already stated here that that's not the path to follow.

Even though I agree you in the way that something has to be done and not wanting to know anything about the community efforts to solve bugs isn't in any way cool! :rolleyes:
[Nexus 5 Original Android Development] rmbq:
since the kernel which you are talking about is the one i built, i think i should reply.

first: i never said new wifi driver will solve the bug.

second: why i updated the driver?

stock wifi driver is made by broadcom. the driver i used is made by broadcom.

stock driver is for bcm4339 (and others) chipset. new driver is for bcm4339 (and others) chipset.

so, what's the matter? maybe new driver will not solve the bug but maybe is just better. otherwise why broadcom developed it? the whole CAF kernel isn't stock but no one never complained about it, on the contrary everyone said it's better than stock.

and if the new driver is worse who cares! we have got a stable one but you can't say it's useless to update it if you haven't tried it.
[Nexus 5 Original Android Development] myfluxi:
We are the first and probably the only device that got a pick-up function without any OEM-support. We are abusing the low-energy tilt detector sensor that has a fixed rate of 2 seconds and have our own little app for this.

You can edit your build.prop and enable a native pick-up gesture that we stole from the OnePlus One. Unfortunately there was a side effect when sometimes Ambient Display came on without a buzzworthy notification. I'm using it like this for some days now and it appears to very OK now, I didn't feel like it was bugging me:

ro.qti.sensors.pick_up=true
[Nexus 5 Original Android Development] myfluxi:
Some ****ty apps are programmed ****ty. Remember our own Eleven music app? It was ****ty as well, now it's great. The super energy-saving Partial Screen Updates feature that we have in the caf builds exposes this bug. You'll notice it in Youtube's split screen view as well, it's not that smooth until you cached the preview pics.

I will not change this because there are the AOSP builds. If it bothers you, use AOSP that wastes all of its energy to compensate for ****ty apps.
[Nexus 5 Original Android Development] :
Okay, about 'custom' kernels: I think that's the first time someone posts his own kernel and since he 'only' updated the wifi drivers we can't really talk about a custom kernel here. [MENTION=4487443]rmbq[/MENTION] Just leave it here - everyone's free to use it :)

I just saw a few heavily-modified CAF kernels here and I meant they should have their own thread. Anyways, that's definitely not the point here - Sorry for sounding harsh guys...

[MENTION=4152171]myfluxi[/MENTION]:

If I understood correctly that side-effect is now gone since DreamManager has been fixed. So will you set that build.prop tweak by default? :)

I'll start using AOSP when CAF is really dead. As long as you're still working on it it's a way better option for me and I'm willing to do my own builds :P Can't say it often enough! Thanks for your efforts, thanks for teaching me how to build from your repos! :)

By the way: There's official TWRP 3.0.0-0 for hammerheadcaf now. Time to update your signature! :P
[Nexus 5 Original Android Development] myfluxi:
http://review.cyanogenmod.org/#/c/133386/

The other AD patch does not have anything to do with it. Somebody will whine again, essentially the reason why I do not bother any more.
[Nexus 5 Original Android Development] satyr007:
Why would you change caf to aosp? Everything is working fine... I just don't get it.
[Nexus 5 Original Android Development] lcrponte:
Hold your horses. Did I offend you in any way? Did I say that you're trying to do anything? Did I question in any way something that you did? Relax your oring. I just emphasised what myfluxi said. And my "attack" wasn't directed to you.

You did what you did and by any way just keep doing what you do. Any help or update as minor as it can be will always be welcomed.
[Nexus 5 Original Android Development] rmbq:
no problem, i meant "you" in its plural form... and no offense at all, i clarified why i used updated driver. i quoted you just because you were the last :cowboy:
[Nexus 5 Original Android Development] ssauger:
Not all is working, miracast still broken on CAF as far as i know, was working on CAF CM 12.1. And thats a showstopper for me. But honestly, i miss CAF.
[Nexus 5 Original Android Development] Disrupthor:
Will this work on AOSP side?
[Nexus 5 Original Android Development] :
I don't even know what kernel source I should use now for my own CAF builds... seems like both repositories (myfluxi/CyanogenMod) are being worked on - but I think they're a bit async right now, aren't they? :/ Sorry for sounding noobish.. I'm not a developer - just trying to do up-to-date builds... Can someone help/explain it for me? Thanks a lot!
[Nexus 5 Original Android Development] willybarca:
whats our own little app?
[Nexus 5 Original Android Development] ssauger:
+1

i also interested

Did a build with CyanogenMod repo and changed ro.qti.sensors.pick_up=true isn't set after boot, edit the build.prop for my own now

Will test it some time, i miss CAF that much :crying:

I post a DL link soon here, if it isn't ok, please tell me [MENTION=4145479]experience7[/MENTION]

<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="myfluxi/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
</manifest>

https://mega.nz/#!5tlC1Cza!JiuRQvHwAw8CgpAMcp2Mwtx97gwXZtsiGM8UZRPxS9U