yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Theliels:
02-09 13:28:02.260: I/CameraService(215): CameraService started (pid=215)

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: dev name = /dev/video1, cam_idx = 1

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: opened, break out while loop

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: cannot open control fd of '/dev/video1' (No such device)

02-09 13:28:02.270: E/mm-camera-intf(215): camera_open: mm_camera_open err = -1

02-09 13:28:02.270: E/QCamera3HWI(215): static int qcamera::QCamera3HardwareInterface::initCapabilities(int): camera_open failed

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: dev name = /dev/video2, cam_idx = 2

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: opened, break out while loop

02-09 13:28:02.270: E/mm-camera-intf(215): mm_camera_open: cannot open control fd of '/dev/video2' (No such device)

02-09 13:28:02.270: E/mm-camera-intf(215): camera_open: mm_camera_open err = -1

02-09 13:28:02.270: E/QCamera3HWI(215): static int qcamera::QCamera3HardwareInterface::initCapabilities(int): camera_open failed

and a lot of more new kernel errors in log, not only camera related
[Nexus 5 Original Android Development] timosuomi:
I can report that the FF cam works fine on 1-17 and ElementalX .24 kernel. I'm sure the CM kernel will get worked out soon.

via my nerded out Nexus 5
[Nexus 5 Original Android Development] phiral:
Definitely kernel related, with stock Google camera and cm kernel it FC when switching to front facing camera. With Franco.kernel-r32 works fine.
[Nexus 5 Original Android Development] mo976:
Has anyone tried it yet do we know if this solves the reboots and SoD issues

Never mind I see people are reporting the front camera is not working

---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------

Cmxlog is great for following changes

http://www.cmxlog.com/11/hammerhead/
[Nexus 5 Original Android Development] shotta35:
I did a fresh wipe just now because of the new kernel and saw the camera issues so i fired it up. The rear camera seems to work fine at first but once switching to the front camera it crashed and now wont start up. Good thing i didn't get all setup yet so i just wiped again and now just gotta remember to not switch to front camera :P
[Nexus 5 Original Android Development] Chris123NT:
It should be fixed in pretty short order. It never popped up in testing because steve threw in some last minute commits before the main merge that borked it. I pinged him about it so hopefully it gets sorted soon.
[Nexus 5 Original Android Development] WoodburyMan:
Confirmed Jan 16th Front Camera worked fine. Flashed Jan 17th, front camera fails.

Realllly waiting for the new kernel...
[Nexus 5 Original Android Development] Chris123NT:
This IS the new kernel
[Nexus 5 Original Android Development] WoodburyMan:
It is? I thought they just merged this... http://review.cyanogenmod.org/#/c/57452/

Not to savvy with github but I know this is the new kernel tree, was never on code review only in github. https://github.com/CyanogenMod/android_kernel_lge_hammerhead/tree/next No idea how to tell myself if its been merged with main or not.
[Nexus 5 Original Android Development] Chris123NT:
Main kernel = next with some new stuff on top now, it's the new stuff on top that messed the camera.
[Nexus 5 Original Android Development] highKo:
i voted, too. hopefully it will be fixed soon. the workaround with the line "p2p_no_group_iface=1" is enough for me until it will be fixed
[Nexus 5 Original Android Development] q1t1:
And I confirm the 2 cams work back with franco kernel
[Nexus 5 Original Android Development] R0axet:
Kernel stuff

For the novice that doesn't swap kernels making mention of the the franco kernel working is nice, but for us that prefer to leave kernel twiddling be, the rest of us will have to wait until the kernel is rev'd by the maintainer(s). :D
[Nexus 5 Original Android Development] xeonight:
Same here, first time i've used non-CM kernel too, i'm not gonna bother with tweaks or anything, i am just making my phone a daily driver until the CM kernel is fixed, and btw, it doesn't get said enough in here, but AWESOME JOB GUYS, you are very good at what you do, and all of us here appreciate it A LOT!
[Nexus 5 Original Android Development] mixtapes08:
Can anyone locate the commit for cm stock landscape battery? Thanks in advance. Been searching it for hrs.

Sent from my Nexus⁴
[Nexus 5 Original Android Development] Android-Parnaoid:
Flashed last nightly (17/1/2014) and now the default launcher (GEL) is gone.

How can i bring it back?
[Nexus 5 Original Android Development] hanschke:
why nobody answer my question why "caf" cm will be better and is here postet :confused:
[Nexus 5 Original Android Development] nexzor:
i would suggest you to read all posts of myfluxi. if you would do this, you would see that no decision is made jet if these changes will get official or not!
[Nexus 5 Original Android Development] vtec_:
The code is more up to date AFAIK and apparently fixes some issues such as ram leakage (see myfluxi post). However from an end user point of view, it certainly isn't "better" as I'm finding regular CM + ElementalX kernel smoother.
[Nexus 5 Original Android Development] myfluxi:
Thanks for the bug report. I will happily continue to invest in hardware out of my own pocket to support your device and buy a wireless charger.

Regarding smoothness and performance, we can improve scheduler performance by 100% with a few changes and smoothness as well. Don't worry about this part, there is more important stuff to accomplish right now.
[Nexus 5 Original Android Development] JesusFreak316:
[MENTION=4152171]myfluxi[/MENTION], I know this is about as low priority as it gets, but does your build have support for Wii remotes? I saw this patch on gerrit http://review.cyanogenmod.org/#/c/63293/ and my Wiimote pairs but doesn't do anything. Do you have the flags in your kernel mentioned?

CONFIG_HIDRAW=y
CONFIG_HID_WIIMOTE=y
[Nexus 5 Original Android Development] gravis86:
Oh wow! I don't expect you to do that at all... But if you are going to buy one, would you like a donation? I feel bad making you spend your own money.
[Nexus 5 Original Android Development] neobuddy89:
I think he intended sarcasm. :laugh:
[Nexus 5 Original Android Development] Pretoriano80:
That actually made me smile this morning,i also think it was sarcasm [emoji3] .

[MENTION=4152171]myfluxi[/MENTION] : i don't use bluetooth here so can't do much testing here but i do have a wireless charger (Nokia ) and the device is charging just fine with build 04.

Honestly i don't even use CM so much but i followed your work since i got this device and i saw how much effort you have put to make CM ( and not only) better on this device even if you didn't received the deserved feedback/appreciation.An example would be the gamma control code,when you released it ,many devs were happy to use your code,now they made some buck and didn't followed your path anymore (removing the negative values) and this created fragmentation .
[Nexus 5 Original Android Development] c_86:
Looks like the build failed today nothing for Aug 30
[Nexus 5 Original Android Development] Barracuda77777:
failed because of the torch commit, it broke the build, this commit has been reverted so tomorrow should build with no problems.

also myfluxi's hard work on the kernel has been commited, so tomorrows build should have the bluetooth fix.

all thanks to myfluxi!
[Nexus 5 Original Android Development] Audioboxer:
I wonder how much of the work from his test builds though, as he changed a lot for the better.
[Nexus 5 Original Android Development] Pretoriano80:
[MENTION=4152171]myfluxi[/MENTION] : I decided to test the Bluetooth auto connection and disconnection issue and after i managed to find my old Bluetooth headset i started to play with it.Indeed there are connection/disconnection issues but are a bit random, so i tested under various conditions (and got a logcat for every test), here's the results and also an easy way for others to reproduce.

Pre-test requirements:

* switch ON bluetooth connection on your smartphone

* switch ON your bluetooth device

* pair you device with your smartphone

** Test 1 **

Start Condition: Bluetooth connection OFF and Bluetooth device OFF

On this first test the BT Headset didn't connected at all, no matter how many times i switch it On and Off

Log - - http://pastebin.com/3Z554pMT

** Test 2 **

Start Conditon : BT connection OFF and BT device ON

This time as soon as i switched the BT connection ON the Headset connected right away.

Log - - http://pastebin.com/hwn3GWae

** Test 3 **

Start Conditions :BT OFF - Headset ON - - > switch the Headset On and Off a few times

After switching the Headset On and Off a few times ( 2-3 times always did the trick here) the Headset will either get stuck as Connected or will fail to connect again

Log - - http://pastebin.com/jKyyPgrw

** Test 4 **

Start Condition : BT Off - Headset Off

As you can see this test is the same as test 1 but this time the Headset connected just fine, the issue is that after you switch Off the Headset it will still show as connected on your smartphone.

Log - - http://pastebin.com/raw.php?i=tSALv1Aj

**Test 5 **

Start conditions : BT Off - Headset Off

In this test the Headset get stuck as connected if you go out off range or if you turn it off.

Log - - http://pastebin.com/1mvq4MWb

*** NOTE ***

In every test i noticed that switching the Bluetooth connection Off and the back On will always fix the issue.

Now i don't know if any of these will be helpful for you to narrow this issue but this is all i can do to help.
[Nexus 5 Original Android Development] Audioboxer:
Very useful testing. If you can be bothered could you try doing the same with this test build from myfluxi?

http://xdaforums.com/showpost.php?p=55096825&postcount=8351

It fixed all my BT issues in my car. It's a special CM build though so I'd nandroid, check it out, then revert back to official if that's what you're on.
[Nexus 5 Original Android Development] Pretoriano80:
That's the build i'm on and that's what i used for testing.
[Nexus 5 Original Android Development] Audioboxer:
Really good testing then, as [MENTION=4152171]myfluxi[/MENTION] obviously made some great progress switching over to implementing more CAF, and with your logs maybe the last few niggles can be sorted.
[Nexus 5 Original Android Development] topgeardave:
Would just like to ask those who flashed the unofficial rom, do you have high idle battery temps?
[Nexus 5 Original Android Development] Audioboxer:
Mine seem okay, but I haven't checked just from holding phone. Neo has just posted a new version of 14.0 with a few of the BT changes myfluxi made to the kernel that failed for nightly 30, so I'm going to switch back to official for now.
[Nexus 5 Original Android Development] luisangel89:
Just curious...do a lot of you use the trebuchet launcher? If not what launcher so you all use?
[Nexus 5 Original Android Development] aldyu:
Yes, i do, but it seems only on the reading, the phone really is not hot.
[Nexus 5 Original Android Development] topgeardave:
Feel the phone at the top? I can feel it get really warm
[Nexus 5 Original Android Development] aldyu:
Can no longer confirm since I went back to official nightly with elementalx for the moment.
[Nexus 5 Original Android Development] topgeardave:
Nova, been using it since ICS days on my Desire :)
[Nexus 5 Original Android Development] luisangel89:
I've been using nova too since my inspire 4g.
[Nexus 5 Original Android Development] thederekjay:
I was under the same impression. I don't have any data to back up the claim, but when I was running the test builds, more heat was being generated even at idle..
[Nexus 5 Original Android Development] topgeardave:
Here's some data, temps were hovering around 36 mark before I flashed unofficial rom and chaos kernel then shot up to 48 degrees on idle. Here's some screenshots I took before I reverted to official nightlies.

Just before and after, look at time on the bottom axis:

A few hours before flashing and just when I flashed:

My average battery temps over a 24 hour period and just when I flashed ROM and kernel:
[Nexus 5 Original Android Development] Visa Declined:
Edit: Nevermind
[Nexus 5 Original Android Development] sergtot:
Is there contacts synchronisation from Facebook in last snapshot? Because I don't have it.
[Nexus 5 Original Android Development] arbi97:
Guys, have you got FC of "SoundRecorder"? It's started on 29th nightly, and in 31st i have it! Any suggestions?
[Nexus 5 Original Android Development] Pretoriano80:
Battery temperature is definitely higher on the CAF Test build 04 compared to other roms/kernels (in my case compared to Miui with ElementalX).

Here's the battery with CAF Test 04:

And this is with Miui plus ElementalX kernel:

Test was made in the same conditions,fresh boot and 5 minutes of light use ( just reading on Tapatalk).

The issue is when you plug the charger,with CAF build the battery will Overheat and the device will charge very slow if you keep using your device but with Miui it will charge just fine even if you are still using the device.

So yes,imo those 6-7 degrees makes a difference.
[Nexus 5 Original Android Development] Audioboxer:
[MENTION=4152171]myfluxi[/MENTION] are you intending to release any more CAF test builds or have we done all the testing needed?
[Nexus 5 Original Android Development] kellybrf:
this feature got pulled years ago. you can use an app like haxsync
[Nexus 5 Original Android Development] snorfu:
How do you guys think about the cm11 performance? I think it is not so smooth

Iike other aosp roms, unfortunately :(
[Nexus 5 Original Android Development] Audioboxer:
On hammerhead it needs an overhaul, [MENTION=4152171]myfluxi[/MENTION] and [MENTION=4800121]Sultanxda[/MENTION] are trying to push through some exciting changes for us.
[Nexus 5 Original Android Development] snorfu:
Yeah i tried the third version from [MENTION=4152171]myfluxi[/MENTION] but i wasn't satisfied, anyways keep up the great work
[Nexus 5 Original Android Development] Audioboxer:
Jump over to the 4th beta and then try this kernel http://xdaforums.com/showpost.php?p=55134753&postcount=3678
[Nexus 5 Original Android Development] dannyella:
Damn..today's nightly lags massively!
[Nexus 5 Original Android Development] michelemascia7:
Has the rom the option to stop/resume download?
[Nexus 5 Original Android Development] fleischbanane:
Works perfect here.
[Nexus 5 Original Android Development] boysetsfire:
here too!
[Nexus 5 Original Android Development] dannyella:
I literally cannot use my phone. Response time is like 5 seconds. Let me try a full clean wipe. :cyclops:
[Nexus 5 Original Android Development] snorfu:
I've tried that combo and the performance is good but i noticed a delay when turning the screen on... This also happens on myfluxi's "stock" CAF build. I've made these observations in comparison to stock rom + Franco kernel.
[Nexus 5 Original Android Development] tnpapadakos:
nova
[Nexus 5 Original Android Development] cjwaggsrx8:
On the 31st build sound recorder has been removed from the app drawer although it shows the app in system/ app.. No biggie just curious where it went?
[Nexus 5 Original Android Development] cjwaggsrx8:
http://review.cyanogenmod.org/#/c/71797/

Apparently it's not just me..
[Nexus 5 Original Android Development] myfluxi:
Franco is using a patch of mine that got reverted in each incarnation of CM because it may produce unwanted effects during screen on for some users.

Pls don't do this because any feedback will be rendered absolutely useless. Applying loads of untested stuff on something under development makes everything a mess. This mixing and matching produces..umh chaos. The next thing I see is memory corruption and all kinds of freakish and unfortunately well known errors..

This would be very well appreciated. I don't need either, a bluetooth device or a charger but users may very well benefit.
[Nexus 5 Original Android Development] neobuddy89:
Lol. That's not same kernel for which you are referring "memory corruption" :p

It's this: https://github.com/neobuddy89/hammerhead_kernel_caf_kk-3.
[Nexus 5 Original Android Development] Audioboxer:
It's based on your kernel sources, but I understand what you're saying :good:

Not asking for an ETA but are you going to push out any more beta builds for us to test [MENTION=4152171]myfluxi[/MENTION] or am I best to just switch over to the nightlies and keep an eye on progress? Thanks
[Nexus 5 Original Android Development] lexusisf:
Yes in 2 weeks
[Nexus 5 Original Android Development] ilbert:
From 08-31 nightly I sometimes my nexus doesn't wake up from stanby and I have to press every button to reboot it.

Am I the only one facing these problem?
[Nexus 5 Original Android Development] thederekjay:
Pressing every button? Holding the power button works. And no, not facing any issues. Without any detailed info its hard to help.. Grasping at straws but make sure that 'prevent accidental wake up' in display settings is unchecked or make sure proximity sensor remains uncovered when turning on the device.. Other than that, gonna need more info.
[Nexus 5 Original Android Development] RJQXCV:
Is this still a thing? I posted this in May...
[Nexus 5 Original Android Development] Circaflex:
no
[Nexus 5 Original Android Development] willybarca:
does anyone else battery overheat and charge slow
[Nexus 5 Original Android Development] Klausi:
Does anyone see this after calling the mailbox and choosing the download?

It happens since some weeks now. I can only end the call while pressing the on/off key (after enabling that in settings).

I have no idea how to fix this :(

Thanks, Klaus
[Nexus 5 Original Android Development] boxcar8028:
I’m on nighty Sep 1 and my N5 is working just fine. No battery issues, charging is normal hard wired or wireless with no over heating. :cyclops:
[Nexus 5 Original Android Development] rangerelf:
Mine did so I reverted to 8/29 :-/
[Nexus 5 Original Android Development] aldyu:
Everything's fine here with latest nightly...
[Nexus 5 Original Android Development] UrbanDrawer:
Mine's somewhat the opposite, charges fully in minutes and.. discharges even faster.

I'm almost certain it's a HW issue though.
[Nexus 5 Original Android Development] tim2100:
I have been having this problem on 20140902 nightly. It is still active as I get a flashing LED for new notifications but the screen will not wake up. I have tried pressing all buttons but only responds after holding down the power button to power cycle the unit.

I have gone back to 20140829 to resolve this.
[Nexus 5 Original Android Development] stonew5082:
Anyone have the 27th nightly?
[Nexus 5 Original Android Development] kornklown69:
Tomorrow has a pretty large change log building up
[Nexus 5 Original Android Development] dannyella:
None that I'm particularly interested in.
[Nexus 5 Original Android Development] kornklown69:
Same here nothing specific hammerhead related just like to see work implemented.
[Nexus 5 Original Android Development] kara mustafa:
Any bugs or problems with the latest nightly?
[Nexus 5 Original Android Development] hanschke:
yes I got the gui crash from incall and cannot take the incall for speaking :crying:
[Nexus 5 Original Android Development] comscier:
Todays nightly... stuck at boot after update... force reboot to recovery, clear cache, then it seems to works fine.

I was on yesterday nightly. (No custom kernel, and I am using cwm recovery bundled with CM11)
[Nexus 5 Original Android Development] gt-kingz:
Exactly the same setup, also coming from yesterday's nightly. I didn't need to clear cache. Sometimes you just need to wait a few mins for booting up.
[Nexus 5 Original Android Development] jpbl1976:
Had the same issue with mine. Hoping it gets solved by tomorrow's nightly.
[Nexus 5 Original Android Development] aldyu:
I'm on 20140902 nightly and never experienced the issue. I might stay on this nightly for a while as there are many merges recently that might break things. :)
[Nexus 5 Original Android Development] VOLTAGEROCK:
I do. What's up?

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] ASHURiCAN:
No problem for me with today's nightly.
[Nexus 5 Original Android Development] kornklown69:
today's nightly working flawless here ElementalX also installed
[Nexus 5 Original Android Development] mbellot:
Just had my first SOD, running 8/31 nightly.

Stock CM11, TWRP recovery, no custom kernel
[Nexus 5 Original Android Development] Darkside14:
Maybe it's only with me, but with the today's nightly, when I try to delete a contact, the app force close, even if I clear the app data

Otherwise, absolutely no problem
[Nexus 5 Original Android Development] ilbert:
Did you change something in the performance zone?

I had conservative governor, I set back interactive updated to latest nightly and no more problem so far (finger crossed)
[Nexus 5 Original Android Development] thederekjay:
Not happening on my end.. Did you/can you get a log??
[Nexus 5 Original Android Development] Darkside14:
Sure ! But how can I do that on the easy way? The crash report of the app? Or any other solution?
[Nexus 5 Original Android Development] thederekjay:
OK.. Not realizing I was on yesterdays nightly, when I updated to today's I had the same issue. Wipe data from contact and contacts storage and report back..
[Nexus 5 Original Android Development] VOLTAGEROCK:
I have Bluetooth issues where it says I'm connected even when my tooth is off. Also the power button doesn't work every time and I never had that problem when running non ROM while rooted.

What about you?

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] thederekjay:
Settings > display & lights > prevent accidental wakeup

Make sure that's not checked or be mindful of your proximity sensor..
[Nexus 5 Original Android Development] Barracuda77777:
this issue will be fixed with this commit, I just finished building my home build and

the force close issue is gone :), so next nightly will fix this issue.
[Nexus 5 Original Android Development] dave-:
Found this doing a search looking for flip to mute ringer, is this still the case? Seems pointless to run a custom ROM and then still need to add something like gravitybox (which is awesome for a stock ROM) to get these sort of features?
[Nexus 5 Original Android Development] Saturn2K:
I just had a bad run in with one of the more complex combination roms out there. So now I'm looking into the simple roms.

Does this rom have the bit where notifications are on the lock screen?
[Nexus 5 Original Android Development] stonew5082:
Well I did a full wipe and everything's fine now. Something seems to have changed after the 27th maybe... but I'm running perfect for the last 24 hours. I'm also using elementalx though.
[Nexus 5 Original Android Development] Darkside14:
I did that and all is working now
[Nexus 5 Original Android Development] hanschke:
incall ui crashed. wft i cannot talk to an incoming call :(
[Nexus 5 Original Android Development] thederekjay:
Not having that issue on the 0904 Nightly. If you're using a theme, try reverting to default and see if issue persist..
[Nexus 5 Original Android Development] hanschke:
take the german provider for searching "das telefonbuch" and put your internet on and got a call with number you dont know. You will get the crash!
[Nexus 5 Original Android Development] DOBBY0:
When I'm tether my data, it seems like I start getting issues when my mifi is active. I was going to change the WiFi channel on the mifi but do not know the default channel on cm. Does anyone know this?
[Nexus 5 Original Android Development] thederekjay:
6 is the default..
[Nexus 5 Original Android Development] xonone:
I gotta say the Latest Nightly feels pretty smooth after a fresh install. It seems smoother than stock.
[Nexus 5 Original Android Development] niv3d:
Does anyone have the green line video playback issue? Using Elementalx
[Nexus 5 Original Android Development] xonone:
I just flashed it and I haven't seen any issues yet. Been on Netflix and watching Rangers play via MLB at bat. I'm on the newest nightly with elementalx 1.05