yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] VOLTAGEROCK:
I have the 10/26/2014 nightly and I'm wondering if anybody else is experiencing this issue. When I go to make a phone call and this doesn't happen all the time, but it happened 7 times in a row when I left work today at 5pm, on AT&T service, when I go to make a phone call the phone rings for about 2 rings and then suddenly hangs up. I noticed in my status bar that when the call hangs up my service signal strength meter turns into a blank triangle meaning there is no service whatsoever. Then when the phone call hangs up after 1 second the signal strength returns back to normal and this has happened to me a bunch of times at random times throughout the day. Is this an AT&T issue or is this related to CyanogenMod?

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] bigbrown:
I'm getting the same thing.
[Nexus 5 Original Android Development] VOLTAGEROCK:
What can we do? This is really frustrating. Am I supposed to be posting these issues elsewhere?

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] stone_ship:
I think this is an AT&T issue. I'm having that and I'm not even on CM (stock 4.4.4)
[Nexus 5 Original Android Development] VOLTAGEROCK:
Thanks so much. So you aren't rooted and no Roms, kernels, nothing? I'm calling att tomorrow about this.

I just don't remember having this problem on my first nightly of 08/19/2014...

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] dannyella:
Does the newest experimental build fix the sensors?
[Nexus 5 Original Android Development] myfluxi:
The nightly is just fine now.

https://download.cyanogenmod.org/get/jenkins/88828/cm-11-20141030-NIGHTLY-hammerhead.zip
[Nexus 5 Original Android Development] neobuddy89:
Fix is "to-be" included:

http://www.cmxlog.com/11/hammerhead/

30th nightly. Don't know abt any experimental builds.
[Nexus 5 Original Android Development] neobuddy89:
30th Nightly build with fix available.

http://download.cyanogenmod.com/get/jenkins/88828/cm-11-20141030-NIGHTLY-hammerhead.zip
[Nexus 5 Original Android Development] mbellot:
Is the kernel OK now too, or is your 1028 build still better? I have been getting some scary good battery life with it.

:good:
[Nexus 5 Original Android Development] procitysam:
Have you gotten any lag with the 1028 kernel?

Edit: just switched to it and everything is good so far :D
[Nexus 5 Original Android Development] myfluxi:
The kernel image is a test, a proof of concept that we will have a stable base for the L release. "Battery life" will be as awesome as ever. The rebased kernel adresses several bugs that exist since January, instable and unreliable bluetooth, occasional memory corruption, extreme graphical glitches, occasional kernel panics and a bug in memory handling that is also known as the "stutter cam" or "memory leak bug" and occurs after some time without rebooting and probably many more. I'll upload a "feature complete" version later. Either L or some custom patches will bring further improvements, it's just a bit too early for this.

I am aware of the funny boot animation behavior. This is however related to patches in the subsystem that causes the cam/mem bug, so we will have to live with this until there is time to patch up carefully.

Nightlies and M releases are still with the old kernel.
[Nexus 5 Original Android Development] fagyi:
Hi myfluxi!

What do you think about this krait optimization on the BoardConfig:

# Krait optimizations

TARGET_USE_KRAIT_BIONIC_OPTIMIZATION := true

TARGET_USE_KRAIT_PLD_SET := true

TARGET_KRAIT_BIONIC_PLDOFFS := 10

TARGET_KRAIT_BIONIC_PLDTHRESH := 10

TARGET_KRAIT_BIONIC_BBTHRESH := 64

TARGET_KRAIT_BIONIC_PLDSIZE := 64

Maybe useful for http://review.cyanogenmod.org/#/c/54822/ Im using it few days ago on my N5 without any issue.

Or its already on the vendor state? Or this one no need for msm8974?
[Nexus 5 Original Android Development] myfluxi:
Our libc is pretty darn good already. These values are defaults btw: https://github.com/CyanogenMod/android_bionic/blob/cm-11.0/libc/arch-arm/krait/bionic/memcpy_base.S.

I don't see much tweaking potential. On the contrary, my impression is, that while benchmarks are really good on CM, user experience is sometimes not the best and I attribute this to "tweaking" in the framework - I may be totally wrong, though. Maybe it's just better to focus on real world usecases than on benchmarks? Raw power is not an issue on our device and as long as your personal wellbeing does not depend on Antutu scores, everything should be really fine. Not that we actually have problems with Antutu.

We might even start using the original Google/QCOM/AOSP PowerHAL that boosts inputs for a full 3 seconds... because it feels so good ;)
[Nexus 5 Original Android Development] procitysam:
Is anyone having a second or so of lag when you turn the screen on while using the 1028 kernel?
[Nexus 5 Original Android Development] magnamentis:
2 things

a) i recommend always to flash the latest version before going to troubleshoot an earlier version, except the latest version has know bugs which were mentioned here or elsewhere.

b) 28th build is broken ( sensors ) so there might be other issues but i immediately went back to 26th nandroid after recognizing that it's not clean.

because of that not many are around who could help you with 28th in detail but consider a) and every additional word becomes superfluous :)

good luck

BTW latest nightly is just good for me on 4 devices so flash away
[Nexus 5 Original Android Development] procitysam:
I'm not talking about the 28th nightly, I'm talking about [MENTION=4152171]myfluxi[/MENTION] 1028 kernel. I'm on M11 with that kernel and everything is good except for the bit of lag I mentioned.
[Nexus 5 Original Android Development] andrei1015:
The second of lag is a known issue I think. It will get resolved.
[Nexus 5 Original Android Development] magnamentis:
ok thanks !

thanks for telling me again, you wrote that correctly so my bad, sorry for the detour.
[Nexus 5 Original Android Development] procitysam:
You're fine it was just a little misunderstanding. At least you didn't tell me to flash something that would cause a brick lol
[Nexus 5 Original Android Development] reas0n:
Hello! I'm new in N5 forum :D

Can I use [MENTION=4152171]myfluxi[/MENTION] CM with Chaos kernel, or not? Because the default kernel doesn't have the ability to turn off the cores.
[Nexus 5 Original Android Development] funkyslap:
I think it should work but actually "Chaos Kernel" is discontinued. AFAIK, currently CM Kernel (@myfluxi) uses built-in MSM Hotplug which is exactly what are you talking about :)
[Nexus 5 Original Android Development] reas0n:
yeah, but neither Synapse+USM nor TricksterMOD works, i was also trying to make a init.d script... no success

EDIT: i got it, i just change the online file to 0 in cpu1 and cpu2 folder and then changed the permissions.
[Nexus 5 Original Android Development] SWTR:
What is "Push-Abos" in google sync?
[Nexus 5 Original Android Development] bland.life:
If you still have the sensor problem in the 30/10/2014 nightly make sure that you have not flashed OnePlus One's dalvik and bionic.

Just a note for anyone who could be having problems.
[Nexus 5 Original Android Development] myfluxi:
Here's a feature complete kernel. With proper ROM support, we'll have all the awesome esoteric audio stuff that makes us happy. We can even build the effects in our devicetree which makes us entirely independent. Changes from AOSP are minimal and everything is super easy to follow for custom cooks (and yes, already pushed). Give us the L, now.

141031_kernel_NIGHTLIES_and_M.zip
[Nexus 5 Original Android Development] frankoid:
Thanks!

Just to make sure I understand, have you basically gone back to a closer-to-AOSP kernel to increase stability by avoiding mixing and matching different codebases? EDIT: I've just read http://xdaforums.com/showpost.php?p=56382612&postcount=9667 and sounds like the answer is "yes"?

Is https://github.com/myfluxi/android_kernel_lge_hammerhead/commits/cm-11.0-l the source for this kernel?
[Nexus 5 Original Android Development] myfluxi:
Perfect summary.

I pushed more or less all relevant kernel stuff to several branches. mr2 is the base, rotator is to get it working with the damned display HAL patches plus obvious improvements, l includes Googles current development branch and audio is just to show, we're ready for the nice stuff (offloading, effects, hardware encoding, 24 bit, ULL), even with compatibility google HALs. I can only guess what's coming with L, I want to be prepared for everything and share with anyone interested. Less is more, actually.

I will push devicetree and blobbage as well.
[Nexus 5 Original Android Development] nictki:
can we expect your kernel changes in nightlies builds?
[Nexus 5 Original Android Development] nh5:
Anyone having modem crashes when picking up calls or dialing out once the other party picks up? Over the past two weeks I'll pick up a call signal will drop to no service, and it appears the modem resets. I'd say its happening about 50% of the time. I've pulled modem and kernel logs can't see anything definitive. Anyone interested in looking at my modem log? I'm skeptical about publicly uploading until I know my data has been scrubbed. I'm on ATT.
[Nexus 5 Original Android Development] procitysam:
If you read a few pages back, it was determined it wasn't the ROM but an AT&T problem. Personally I haven't gotten this problem and I'm on AT&T but others have also had that problem.
[Nexus 5 Original Android Development] myfluxi:
Stufe 1: http://review.cyanogenmod.org/#/c/72393/ ;)
[Nexus 5 Original Android Development] MaxRabbit:
myfluxi, thank you for this hard work. Would you mind terribly elaborating on "We can even build the effects in our devicetree which makes us entirely independent."?
[Nexus 5 Original Android Development] procitysam:
Seems like this kernel is using more battery than the previous test builds of it. Is anyone else seeing this? Do you know why it could be happening?
[Nexus 5 Original Android Development] myfluxi:
I have no idea how/where Google will add the effects as these are present as binary in the L preview but not yet in the HALs. That's why I'm evaluating options.

Additionally there is not so much support from CM and HAL changes might be a show-stopper (some audio HAL changes that are intended to bring us h/w encoding and do not influence any other device, sit in gerrit for 3 weeks now).

Frustrating and very sad.

It does not happen. With only a few changed files in completely other areas, this is a typical case of random and unrelated behavior.
[Nexus 5 Original Android Development] MaxRabbit:
No kidding, huh. So this means that, unless CM starts merging your changes in gerrit, we will be continuing with unofficial builds?
[Nexus 5 Original Android Development] unknvvn:
[MENTION=4152171]myfluxi[/MENTION]

are you going to continue to make CAF CM releases?

It had one great feature - ability to control the volume while audio DAC is connected.

With CM or CM w/ your kernel can't do that. Only either max volume or volume off.
[Nexus 5 Original Android Development] rockknee:
Just search. It has been asked before and it is very easy to find the answer. Reading this will also help: http://xdaforums.com/showthread.php?p=56288681

It means no.
[Nexus 5 Original Android Development] unknvvn:
How it means no?
[Nexus 5 Original Android Development] rockknee:
Personal project=non shared project

Same question asked here http://xdaforums.com/showthread.php?p=56331793

Scroll through the page and you'll see also myfluxi's announcement "Like talking to a wall" when there was the question about caf releases :D
[Nexus 5 Original Android Development] kong:
personal != not shared

Most of the projects here are "personal" and developers can quit anytime they want.

Regarding the CAF builds question, he never said that he would STOP developing nor he will CONTINUE to develop it. He just said that it won't be official.

That's why I asked the question in the first place. He could have just replied YES or NO normally and cleared things up but... well, I don't know :/
[Nexus 5 Original Android Development] Circaflex:
so you already knew the answer and asked anyways?
[Nexus 5 Original Android Development] rockknee:
No, you should not expect yes or no directly from myfluxi ;D
[Nexus 5 Original Android Development] bonedriven:
I haven't used CM for a year I'm wondering how is it now...compared to slimrom?

I liked slimrom but had some serious bugs after an update. Since I need to do a factory reset I'm thinking to try CM. Any opinion compared to slim rom?
[Nexus 5 Original Android Development] Circaflex:
this isn't the right area to ask this question, you should ask it in the Nexus 5 general section, reason being is these debates never end nicely when asking for a comparison between rom a and rom b inside of rom bs thread.
[Nexus 5 Original Android Development] rohankumar.112:
While I agree with what [MENTION=1413320]Circaflex[/MENTION] said, I must mention that with the combination of recent nightlies and last kernel from Myfluxi, CM on Hammerhead has never been more stable!

All the little bugs that have plagued us since Jan/Feb have now been addressed, Bluetooth connectivity among multiple peripherals works without a hitch, battery life is phenomenal and overall the smoothness of the UI is great. All these packed with just the right amount of features from CM ensure that I'll continue with this current setup well after Lollipop is officially available.

Thank you [MENTION=4152171]myfluxi[/MENTION], can't wait for what you cook up next.
[Nexus 5 Original Android Development] myfluxi:
I have no idea what happens with the nightlies, let's wait patiently until L drops.

In the meantime I will push whatever I have to Androidfilehost and Github. The kernels fix more or less everything for Nightlies and M releases. The full CAF builds are bleeding edge, perfectly fine as daily driver and a real joy to use but have some really tiny bugs in special usecases.

I will not respond to any question and I won't announce anything, it's all private fun. PM me for questions, if you spot an error - fixit!
[Nexus 5 Original Android Development] mo976:
Speaking of L dropping, good chance we will see that happening in the next day or so. ?
[Nexus 5 Original Android Development] topgeardave:
L only dropping for tablets tomorrow, for nexus 5 factory images, kernel source and blobs there's still a few weeks :(
[Nexus 5 Original Android Development] magnamentis:
not so sure

the first nexus 6 devices reached the customers on thursday and until now i don't remember that it ever took weeks from first deliveries with a new OS version till sources were released. but let's see, only a slightly other assumption based perhaps on optimism or experience :)

i'm not concerned by the way because a stay on K for many practical reasons.

http://www.androidpolice.com/2014/11/01/first-impressions-googles-nexus-6-really-big-really-beautiful/
[Nexus 5 Original Android Development] topgeardave:
http://www.androidpolice.com/2014/1...p-on-nov-3rd-other-devices-later-in-november/

I trust android police because they've always been right with everything like this
[Nexus 5 Original Android Development] _MirageX_:
is anyone able to use photosphere on myfluxi build number 21?
[Nexus 5 Original Android Development] nictki:
no, panorama doesn't work as well
[Nexus 5 Original Android Development] _MirageX_:
oooh, thanks, I thought it was a problem with my gapps.. been trying to fix for 2 hours lol
[Nexus 5 Original Android Development] kong:
Sorry I don’t quite follow your logic ???

Since there is CAF 21 in his folder I guess the answer is yes :P
[Nexus 5 Original Android Development] oliveko:
Automatic rotation still broken on caf21..
[Nexus 5 Original Android Development] myfluxi:
Stufe 2: http://review.cyanogenmod.org/#/c/76071/

I won't fix this for him.
[Nexus 5 Original Android Development] myfluxi:
Then don't use it as I can't fix what does not happen to me. Photosphere and HDR will be fine again though.

Explaination: Too much abuse has been done to sensors lately. CM people copy&pasted stuff from OnePlus to other devices even is these are special fixes for this particular device, breaking stuff everywhere. Then there are bad framework hacks, like http://review.cyanogenmod.org/#/c/76071/ and others. Last but not least the latest crap with the non-functional sensors. I'm sick and tired of this. And an ignorant "still does not work" on a Monday morning is just what I needed.
[Nexus 5 Original Android Development] oliveko:
Sorry for reporting the problem
[Nexus 5 Original Android Development] mo976:
Factory image releases and AOSP source being pushed to the public are independent of each other. We may not get our device specific source blobs yet, but L source will probably be pushed out once factory images start to become available. The nexus 9, 6, 7 WiFi (2013) and 10 WiFi Images will probably be released first and in that order.
[Nexus 5 Original Android Development] myfluxi:
We are walking on thin ice again and I think I'm really clear with my words, the level of ignorance is often stunning. I would like to help everyone but there are obstacles and more obstacles. I think I can at least expect a bit of maturity and empathy. PMs, detailed bug reports with steps to reproduce and comparison with regular nightlies after a wipe are not rocket science.

You want a working device, do something relevant. And I recieve a lot of awesome feedback incl. bug reports...
[Nexus 5 Original Android Development] oliveko:
delete...
[Nexus 5 Original Android Development] Viper LABs:
All sensors are working as expected on CAF21 build for me. Flashed over 10/30 nightly + myfluxi's kernel for nightlies/M. No issues as well on other stuff.
[Nexus 5 Original Android Development] mmo.xda:
After 12 hours, with

"cm-11-20141102-NIGHTLY-hammerhead" + "141102_kernel_NIGHTLIES_and_M"

everything seems to be working fine and smooth.

Thanks myfluxi for this awesome work.

Regards
[Nexus 5 Original Android Development] myfluxi:
You mentioned it as small bug in your deleted posting, ok. Let me give you a little bit more info and an example: There are the black preview images in Instagram, this is a very special usecase for only a few people. This error appears with the official CM HAL repos but not with the original untouched CAF HALs. The question is, if CMs stuff can be fixed; this is beyond the scope of our device and therefore out out my scope. And even if this usecase would be fixed, it may cause errors for other devices. So in the end of the day, a seemingly small bug puts everything in danger. 100 improvements and advantages may outweighed by some black preview image.

While many people are contributing to HTC and Sammy, nobody helps on hammerhead. That's the situation.

I may sound rude or whatever you may call it, but there is a plan. The plan is complex and really frustrating but usually I don't give up before I reach my goals. Your role would be to support the device by supporting me and that starts by trying to accept certain things that help everybody.

That's what I'm saying. I cannot reproduce but certainly I must accept that the bug report may be 100% valid for his application. At the same time, "it does not work" is wrong as it works for many/most and does not help anybody.

Edit: [MENTION=3857343]crpalmer[/MENTION], what about your time, got any? :)
[Nexus 5 Original Android Development] crpalmer:
October is a bad android month for me (we do a big Halloween display). I will have some time in a couple of days up until the L repos are pushed to CM (I have 2 devices that I am the sole maintainer and one that is just myself and invisiblek, who also maintains a ton of other devices). Ironically, I purchased my hammerhead because I thought I would just be able to use it without needing to work on it...

But, as you know, I love the CAF project. I'll talk to you when I'm at my computer and see if there are specific things I can help with.
[Nexus 5 Original Android Development] mo976:
Google is pushing L source to AOSP. Let the games begin! http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/
[Nexus 5 Original Android Development] procitysam:
https://android.googlesource.com/device/lge/hammerhead/+/lollipop-release
[Nexus 5 Original Android Development] saramon:
http://www.gadgtspot.com/2014/10/31/roundtable-cyanogenmod-12-roadmap-leaked-fun-times-ahead/ we should see the first glimmer of cm12 in a few months...
[Nexus 5 Original Android Development] mainicia:
what's about CM12?

how long.. :silly:
[Nexus 5 Original Android Development] mo976:
Really? If I didn't think you were joking I would say you should be banned...but according to the article posted above, about a month.
[Nexus 5 Original Android Development] fattire:
rambling with excitement

It took ~3 days last time for the source to be merged and basic cm10 patches to be applied to cm11 by arcee et al. That one was relatively simple-- there has been a LONG time from AOSP 4.4.x to AOSP 5 code drop so who knows how dramatic the differences are this time. For reference--the jump from gingerbread --(unreleased honeycomb--> ics was massive and it took a ton of work (weeks->months) to figure out how to work around all kinds of issues for older non-nexus devices which had outdated audio systems, missing kernel modules (for network auditing), etc.

Usually AOSP will be merged over first, then there will be an unstable but somewhat buildable state for a few days... it'll be buildable.. it'll break... etc. for each device, the new /device/*/* changes will need to be ported over. People will be posting quick patches and so forth as we go, so keep your eyes on gerritt if your builds get stuck...

AOSP Lollipop source is here. We're looking at the android-5.0.0_r2 tag. the If you've got a non Nexus device (and yes I know this is a n5 forum, but just saying) and you're building from source, you'll need to make a branch in your devices/manufacturer/codename directory and take a look at what was changed between kitkat->lollipop, then apply as makes sense. See here for more on porting...

(more than anyone asked for, but I always get excited on code-dumping day)

[youtube]9-DuC0tE7V4[/youtube]

Update: Some notes on building/porting 5.0
[Nexus 5 Original Android Development] Viper LABs:
http://review.cyanogenmod.org/#/c/76071/

Who did it? Marc did it!!

Nice!
[Nexus 5 Original Android Development] neobuddy89:
Something like this ?

https://android.googlesource.com/device/lge/hammerhead/+/android-5.0.0_r2

;)
[Nexus 5 Original Android Development] myfluxi:
Chris, you're then man! Whatever you do, it'll be awesome.

This happens all the time. I messed up #ifdefs in the audio HAL lately - that's the game. Hope it's ok for everybody now and the original committer will push an improved version.

Regarding L, changes are reasonable and even without knowing the kernel side, it looks sweet. We even get our own camera HAL, to quote Sultan, "LGE loves us" ;) Now we gotta wait until Steve updates the HALs, then we know where it goes. Fingers crossed that we'll be full AOSP in display again. Whatever happens, we are prepared.
[Nexus 5 Original Android Development] fattire:
Well, whichever... I was saying for non-nexus devices you could take the hammerhead or grouper or whatever delta... so yeah. I just did a quick pass for encore for example. Very few non SELinux changes in my first look... it's late I'll go back and double-check..the SE policy stuff looks like the biggest changes.
[Nexus 5 Original Android Development] Viper LABs:
Just wanted to inform, that HDR+ from Google Camera is not working on CAF21 build. But then I found CAF22 and HDR+ is fine again. Thanks, Mark!

Just in case it is important, here is a logcat from CAF21 while taking a picture in HDR+ mode.
[Nexus 5 Original Android Development] myfluxi:
I just forgot to reapply Sultan's patch when moving back to a CM repo. All is good now. Stuff like that would not happen if it was the real thing ;)