yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] kenshin33:
http://review.cyanogenmod.org/#/c/87365/30/src/com/android/settings/fuelgauge/PowerUsageSummary.java <--this is your culprit, it has been there for few days already

---------- Post added 23rd February 2015 at 12:09 AM ---------- Previous post was 22nd February 2015 at 11:33 PM ----------

this was the last one I did :

-rw-r--r-- 1 kenshin users 272003604 Feb 21 16:51 cm-12.0-hammerhead-signed-ota-772fcfb986.zip

my timezone == eastern (-5).

I just spent the last 30 minutes listening to music through my BT headset (RAPOO 6086) nothing to report (no stuttering no stops, even with notification sound).

although this message was flooding the logs :

E/bt-btif (27673): ## Audio Congestion (iterations:96 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:96 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:95 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:95 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:94 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:93 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:93 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:92 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:91 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:91 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:90 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:90 > max (2))
E/bt-btif (27673): [media task tx timer] ts 103217875370, diff : 18446744073705277921, queue sz 16
E/bt-btif (27673): ## Audio Congestion (iterations:129 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:128 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:127 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:127 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:126 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:126 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:125 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:124 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:124 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:141 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:141 > max (2))
E/bt-btif (27673): [media task tx timer] ts 103222652585, diff : 04314796, queue sz 6
E/bt-btif (27673): ## Audio Congestion (iterations:184 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:184 > max (2))
E/bt-btif (27673): ## Audio Congestion (iterations:183 > max (2))

it is annoying but seems harmless.

if you use KDE try kde connect
[Nexus 5 Android Development] mmo.xda:
Removed. It was a bad idea. Sorry.
[Nexus 5 Android Development] myfluxi:
Bluetooth is broken because something went wrong when adapting to CMs build system. For me this means hours of debugging because there is not a tiny bit of logical trace. For you this means likely a week or more until any new build as my time is very limited at the moment.

This is why I find your comment not the least bit funny and totally uncalled for. Seriously, do you have an idea? Stuff like that makes ask myself if it's worth it. Nothing gets fixed automagically.
[Nexus 5 Android Development] ssauger:
[MENTION=4152171]myfluxi[/MENTION] things takes time, no need to rush i think. CAF #42 is great and i stay on it until the next build. One thing i also noticed on cm-12-20150222-UNOFFICIAL-hammerheadcaf.zip, Color Profiles does'nt work. Anyway thanks for your great work and effort on the lovely N5. :good:
[Nexus 5 Android Development] mmo.xda:
Surely due to English (not mother tongue) I did not explain well. But first things first. Sorry. I'm sorry.

My comment was intended to be humorous. We are all eager to try your great job, as we have usually doing.

It is simply expectation.

Again, sorry if my comment was bad, I did not mean to hurt you.

On other occasions, in public and private I have shown my admiration for your time and effort.

Furthermore, at user level, we do not know why Bt or HDR is broken. We do not know if it takes seconds or weeks to repair. And most of us here, besides sending logcats and information you request, we can do little.

Finally, again, my sincere apologies. I will erase the post.

regards
[Nexus 5 Android Development] djsubtronic:
I don't think he meant any offense the way I read it.

But anyway, I'm sure you already spotted this if you saw the logcat for bluetooth failing, but just in case I thought I'd point it out, I notice this line:

I/bt_vnd_conf( 6270): vnd_load_conf file >/etc/bluetooth/bt_vendor.conf< not found

Then again, this file isn't present on CAF42 either so it might be completely unrelated.
[Nexus 5 Android Development] Viper LABs:
Yes, #42 is really great, no issues at all, that could ruin the party.

myfluxi, I'm sure the most users of CAFtastic builds will do everything to help you figure out, what's going on, while you preparing CAF builds to become nightlies. Just let us know what to do/test/try/report. In the most cases we just don't know what we could do to help.

And never make yourself doubt, that you're doing a right job. Because you make this piece of hardware awesome with every CAFing build!!
[Nexus 5 Android Development] The_Virus:
That's what I will do too, stay on CAF #42 until next hammerheadcaf build. I just hope that the next build will be upgradable from CAF builds too.

But really a big thanks [MENTION=4152171]myfluxi[/MENTION] for your great work! Really appreciate the effort you put in those builds. :good:
[Nexus 5 Android Development] ast00:
I was wondering... Which kernels work on CAF? I want to change kernels because i want to undervolt.

So far I tried two kernels, both got stuck at the Google logo. Probably because they are for AOSP.
[Nexus 5 Android Development] neobuddy89:
Wait for it. Let nightlies roll out once issues, if any, are sorted.
[Nexus 5 Android Development] moksha51:
Bluetooth skipping and playing in fast forward??

Hello, my car bluetooth audio is behaving really weird. Ever since the last couple of nightlies, the BT audio is like in 2X the speed and it keeps skipping while playing those tracks.

This didn't happen before. I am using Google music. (It doesn't do this with all bluetooth audio devices. I paired my friend's phone and it works fine).

I tried a clean flash and on the latest nightlies (2/22) and Franco kernel r71

Anybody else have these issues?
[Nexus 5 Android Development] drewdidriksen:
Didn't you already post this in the official nightlies thread? Bit cheeky posting here too.... :what:
[Nexus 5 Android Development] moksha51:
Ha. Yup. Just trying my luck. :p
[Nexus 5 Android Development] x.para:
BT start

Anyone having issues to even start BT on latest CAF?

logcat attached
[Nexus 5 Android Development] ast00:
Well, you might find an answer if you were looking. Yes, it's broken for everyone.
[Nexus 5 Android Development] ryanmat:
Looks like this change to bluetooth is in review for those of us experiencing the audio artifacts and it seems to be working according to the comments: http://review.cyanogenmod.org/#/c/89606/
[Nexus 5 Android Development] reas0n:
[MENTION=4152171]myfluxi[/MENTION] Sooo the CAF source is moving to CyanogenMod github, right? Is it for example android_device_lge_hammerhead-caf which was empty when I had been looking on it?
[Nexus 5 Android Development] myfluxi:
Apparently the build system does not like hyphens and underscores so we end up with hammerheadcaf. This is how it will look: https://github.com/myfluxi/android_device_lge_hammerheadcaf

BT works now - don't ask, you have to be hating Google and the world sometimes.

A2DP is bugged all over CM and amazing people do amazing work to fix it. Deal with it for now.
[Nexus 5 Android Development] drewdidriksen:
Can enable Bluetooth on latest caf build :thumbup:

HDR+ still not available on Google camera but as far as I can tell this is also the case on official nightlies so not a problem with myfluxi's builds.
[Nexus 5 Android Development] kenshin33:
to use instead of https://github.com/myfluxi/android_device_lge_hammerhead branch:cm-12.0-caf?
[Nexus 5 Android Development] reas0n:
Yes, but I had some errors while trying to compile, I see in the commit "Force a present vendor dir to avoid bad third party builds" but it seems like some lines are going to hammerheadcaf vendor folder, not the old one. I think [MENTION=4152171]myfluxi[/MENTION] rather wants us to wait till everything will be set up :cowboy:

For now it's better to just cherry-pick the new commits (about bootloader and speaker tweak), not sure about the bluetooth one. It's better to wait IMO.
[Nexus 5 Android Development] Ph0Xy:
I was wondering if this was a known issue: When I enable ambient display, my screen randomly wakes every 15s with no real notification.

I tried searching all over this thread and other places, but couldn't find anything about this issue other than this reddit comment.

It does work with actual notifications too though. Is there any known solutions / something wrong with my setup?
[Nexus 5 Android Development] myfluxi:
Interesting. [MENTION=1664077]kenshin33[/MENTION] found out we can just use bacons sensor hal and I was under the impression the wakeups were limited to us.

I anticipated your error, that's why I forced it. You cound have just copied and setup the makefiles.

https://github.com/myfluxi/proprietary_vendor_lge/commits/cm-12.0
[Nexus 5 Android Development] reas0n:
Eeeh, I haven't seen that update in vendor, most probably because it was in different branch. Thanks!
[Nexus 5 Android Development] zerosum0:
Nice rom. Very fast and fluid.
[Nexus 5 Android Development] Dr.Pepper:
I have installed latest CAF cm 12 by myfluxi!

Everything is OK,but HDR+ gone(there is no hdr+ button in google camera)!

I tried to flash rom with euroskank gapps and stock PA package gapps!

Can someone help me to fix it?
[Nexus 5 Android Development] ast00:
Read. It's broken for everyone and the is no known fix.
[Nexus 5 Android Development] djsubtronic:
Has anyone been able to figure out why on 4G connections the signal indicator will switch between "4G" and "LTE" seemingly randomly...?
[Nexus 5 Android Development] ssauger:
I also have no HDR+ on builds after CAF42

sent from Nexus5
[Nexus 5 Android Development] oSandmaNo:
Edit build.prop - Change model from Nexus 5 CAF to Nexus 5. And ro product device from hammerheadcaf to hammerhead, reboot and HDR+ is back :)

But, you need to change the update script to skip device check each time you flash the next nightlies.
[Nexus 5 Android Development] ionuts:
I just flashed CAF40 over 38 and I have a random problem : from time to time I have a notification with "No data. Please connect to a network". I tested from another phone ans it rings and as soon as I press on the notification the 4G shows. Reflashed the radio package from 1st post, reseted the APN but stilll the same error.

Ps : Thanks [MENTION=1394147]myf[/MENTION]luxy for your awesome work.
[Nexus 5 Android Development] ssauger:
This mean there is no other way to keep hdr+ in future when using caf builds and are there other things to won't work cause the string in build.prop? :silly:
[Nexus 5 Android Development] oSandmaNo:
I don't know. But I can see that the HDR libs work only if model is Nexus 5 or product is hammerhead. Maybe there is another fix. I do not know [emoji14]
[Nexus 5 Android Development] myfluxi:
I already discussed the device name issue to get back HDR+, CM people are super-supportive as always. I hope we can get this to work in a sane way.

Which brings me to an important info: stuff becomes official as we speak. Nightlies take a few more steps, though. Please don't push me, things will be done if things are done.

A user approached me with an issue of the cam mic. Is it better for your usecase with tonights build?

I added a tiny patch in tonights build. Does this improve the (well known) issue? With my little doze app, that is present in the build, we do not absolutely need the synthetic pick-up sensor. I know, my abusive involvement of the tilt sensor is at least a second too slow, but it's very reliable and will always show the Ambient Display upon pick-up.

Maybe I can convince Steve leak a nice sensor HAL for us...?

We have gerrit now so you can follow my under-the-hood changes and ideas better. And thanks for having me here under the radar and all the great support (and headaches) you all gave me.
[Nexus 5 Android Development] reas0n:
[MENTION=4152171]myfluxi[/MENTION] sooo I successfully compiled a hammerheadcaf, but I can't flash it in recovery..

EDIT: nevermind, forgot about updater-script, i can change it ;) but still it needs a workaround
[Nexus 5 Android Development] myfluxi:
This is an issue with TWRP and the regular hh recovery, obviously Dees_Troy just confirmed we get our flavor soon.
[Nexus 5 Android Development] Sultanxda:
Package assert can be customized via TARGET_OTA_ASSERT_DEVICE:

TARGET_OTA_ASSERT_DEVICE := hammerhead
[Nexus 5 Android Development] Ph0Xy:
So if I understand, the issue is it thinks it's being picked up? I do have "Lift to Wake" turned off if that matter.

Is it not possible to have Ambient Display only for notifications and not for lifting then?

I'll try the new build and report back.

EDIT: I see "Lift to wake" option was removed in the newer build and merged in ambient display.

But yeah it still has the same problem. Randomly wakes every 15s, and me lifting it or not doesn't seem to have any impact on it.
[Nexus 5 Android Development] oSandmaNo:
I think this is the default behaviour of ambient display. To pulse the display every few seconds when there is a notification
[Nexus 5 Android Development] Ph0Xy:
There is no notification though. It's just blank with the clock.
[Nexus 5 Android Development] myfluxi:
Sure. But this would leave the encrypted folks in a bootloop where TWRP even suggested to wipe even though a simple flash of the older build would cure them. I will discuss an assert for relesetools, that could be used as well when people need an upgrade patch S/W -> H/W crypt.

Regarding the HDR+ issue, I checked out multiple methods and so far only one worked (which still appears to be delicate).

I didn't have a single doze/Ambient wake-up with the additional sysprop.
[Nexus 5 Android Development] zerosum0:
That's a cm problem. Read what the OP says
[Nexus 5 Android Development] ionuts:
Update : Today the tap on "Sign in to a network" popped a GoDaddy page ???
[Nexus 5 Android Development] ast00:
I meant to say is broken for everyone, but SwiftKey decided is fine for everyone. Sorry about that.
[Nexus 5 Android Development] kenshin33:
it is, but 3-4 times and it stops (at least that is my what I think I observed)

---------- Post added at 11:28 AM ---------- Previous post was at 11:25 AM ----------

may be a captive portal gone wrong?

What I mean by the above is : a problem with the "sign-in portal". You see the way it works, when you tap to sign in, your phone tries to open a web page (any web page would do) when it hits the gateway it notices that it's coming from a computer (in your case a phone) that it doesn't know, it replies instead of the actual server with an http redirection to the sign in page of the wireless network -it can be hosted anywhere- you're trying to connect to.

From the screenshot you have it seems that the address you're redirected to doesn't exists and is hosted on somewhere that has something to do with GoDaddy.
[Nexus 5 Android Development] myfluxi:
Does this hack enable HDR+? My Gapps package does not support it, so I can't test myself without too much hassle.

https://drive.google.com/file/d/0B4LorYIBlqSSWTY3eWpVRnFoa3c/view?usp=sharing
[Nexus 5 Android Development] salter83:
This worked for me.
[Nexus 5 Android Development] ssauger:
Great, its working and also color profiles, like editing the build.prob. Will this be in next CAF? :good:
[Nexus 5 Android Development] mo976:
Love the CAF stuff going on here, I just might abandon my project and come over to the dark side :D

In the meantime here is a new regular build https://www.androidfilehost.com/?fid=95916177934534278
[Nexus 5 Android Development] ionuts:
There are two cases :

Case 1.

- i call or get a phone called - everything is fine

- call ends ( 2 secounds later the signal dissapears and it takes 10-15 secounds to get back )

- LTE is coming back normally

Case 2.

- again incoming/outgoing call

- call ends ( screen is turned off using power buton - turn screen on and I have that notification - LTE icon is missing )

- today I noticed that Godaddy page and as you can see in the screenshot I was not connected to any wireless - how was that page displayed ?

Best regards.
[Nexus 5 Android Development] kenshin33:
as far as my experience goes (I might be mistaken, I never looked at the code) the "tap to sign in" appears only and only when you're trying to connect to a WIFI network that requires "signing in" on a web page.
[Nexus 5 Android Development] Ph0Xy:
Sorry for the trouble/confusion. Turns out it was Lightflow interfering.

There doesn't seem to be a way to get those two to work together as of now.
[Nexus 5 Android Development] kenshin33:
won't we have a problem if both hamerhead and hamerheadcaf use the same path for kernel ???

I tried to build hamerheadcaf it failed compiling display/liboverlay complaining about some macros not defined* (which are normally defined in kernel headers), I found out later that the kernel source was on the wrong branch (cm-12.0). I restarted the build with the right branch, still building.

(*) in liboverlay/overlayUtils.h : enum eMdpFlags
[Nexus 5 Android Development] salter83:
USB OTG

I was trying various drives I have for use with OTG. I have a 16GB USB2 drive which works fine, auto mounts et all without any problems, but when I try using a 32GB USB3 drive, I get nothing.

When I plug the drive in, the status LED flashes (repeatedly), so something is happening (I'm assuming it's continuously trying to mount the drive). I've tried the drive formatted as FAT32 and exFAT.

Is there a limitation with regards to USB3, or drives over 16GB? I've had a quick google about but I can't seem to find any mention of anyone having similar problems. Is this a known issue?

If logs would help shed some light on this, could someone point me to the appropriate logs?

Thanks,

Dave

Edit: This is the CAF build.
[Nexus 5 Android Development] MidnightDevil:
For some reason when I tried to flash the 24th I got the error that its required the bootloader hhz12d, the recovery returned that error in red and aborted, so I flashed bootloader-hammerhead-hhz12d.img, thinking some rom might have downgraded my bootloader, now, I've got the hhz12d, I flash the CAF 24th and tried 25 as well, but it bootloops.

Any suggestions?
[Nexus 5 Android Development] nexzor:
had the same problem with an usb3 HDD. i tryed with an y-cable with powerside attached zu an usb charger and after this it worked. usb3 needs 700mA and usb2 only 500mA. i think the nexus 5 provides only 500mA and thats not enough for usb3
[Nexus 5 Android Development] myfluxi:
We have to oat2dex: http://review.cyanogenmod.org/#/c/77711/ or pull apks from the muppets.
[Nexus 5 Android Development] Cloonix:
Why is there only a single .dat (system.new.dat) file within the .zip? Usually i remove some apps within the /system/app folder. Is this a change in CM12?
[Nexus 5 Android Development] misfit0313:
This build is giving me the same f/c. Sorry, driving and AFK at the moment.
[Nexus 5 Android Development] Clienterror:
Just flash foxhound for now. He's got center clock, resizable, nav bar, and a black themed option if you like it with a few more things.
[Nexus 5 Android Development] Sharpe351:
Can I like that post 100 times? I hate changing kernel.
[Nexus 5 Android Development] topgeardave:
Is encryption already pre-enabled in this build?
[Nexus 5 Android Development] GialanG:
Nope. And never with roms flashed in recovery.

Sent from my NEXU5
[Nexus 5 Android Development] unknvvn:
Is it normal that swyping doesn't work on AOSP keyboard? Gesture typing is be enabled.
[Nexus 5 Android Development] dlsygaco:
is it me or carrier label on the lockscreen is not at the left?
[Nexus 5 Android Development] lolobarjo:
Yep it's not at his right place

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Android Development] ast00:
AOSP keyboard never supported it. Stock ROMs use the Google Keyboard, which supports ut, but in case of the AOSP keyboard, it's just a blank option.
[Nexus 5 Android Development] gangrel_82:
Does anyone know if screen mirroring through slimport adapter is currently working?
[Nexus 5 Android Development] bhavstech:
Is the rom a daily driver?
[Nexus 5 Android Development] mo976:
Yes, BUT its still missing most of the CM apps and while there have been some enhancements and more are being added constantly its still closer to AOSP .
[Nexus 5 Android Development] mo976:
New ROM is up! I'm having a problem editing the first post from my phone so here is the link https://www.androidfilehost.com/?fid=95784891001615072
[Nexus 5 Android Development] luisangel89:
Can't seem to find double tap to sleep.
[Nexus 5 Android Development] hanschke:
Does CM merged to Android 5.0.0_r7 (LRX21V) :confused:
[Nexus 5 Android Development] mo976:
Its under buttons you can assign actions to the home and recent including screen off. The proper version is still missing.
[Nexus 5 Android Development] pianistaPL:
Yes
[Nexus 5 Android Development] Sharpe351:
[MENTION=4152171]myfluxi[/MENTION] I ran a build yesterday with ALL of your cherry picks from gerrit and I'm still getting the OmaDmclient fail. I'm going to pull a log to see why.
[Nexus 5 Android Development] reas0n:
There are also more compatibility issues. Synapse (app for kernel) doesn't recognize the device. Also there may be more issues. Is it really necessary to change the id of device for CAF?

EDIT: Okay, the author will add support for hammerheadcaf, but still.. I hope it won't cause issues with apps, mods etc
[Nexus 5 Android Development] salter83:
Cool, thanks for the reply! ^^
[Nexus 5 Android Development] myfluxi:
Make sure you checkout to the appropriate branch before build - I ran into this error lot's of times when not using the build script with checkout commands...

This is indeed not our error. There are relevant apps that should be supported of course, i.e. Google's camera.

Consider the case where the app maker forgot to implement proper error checks and hits a non-existent sysfs node. It's always better to throw a meaningful error (like "This device is not supported") because then, if our builds will eventually be relevant, the app maker can provide compatibility.
[Nexus 5 Android Development] kenshin33:
my little experiment with ro.product.device (PRODUCT_PROPERTY_OVERRIDES vs setprop in init.hamerhead.rc) lead to this:

after build :

--- target info ---
blocksize = (int) 131072
boot_size = (int) 23068672
build.prop = (dict) { ..., [B]'ro.product.device': 'hammerhead'[/B], '...}
....

the assert in updater-script tests for (ro.product.device == hammerhead)

I end up with 2 "ro.product.device" in /system/build.prop, one is "hammerheadcaf" and one is "hammerhead" (listed in that order).

yet after boot getprop ro.product.device yields hammerheadcaf.

This is a fringe case indeed but, I can't shake the feeling that there's an inconsistency between what the build system does and what getprop does when the same property is defined twice.
[Nexus 5 Android Development] myfluxi:
Thanks for playing with this but honestly, I just wanted the dirty work to be done. The cleanest approach would have been to inject a vendor lib into init but we're too late there and our ro property is already set.

Whatever, it works and users can be happy.
[Nexus 5 Android Development] BRiANj64:
Running 25/2/2015 build without issues for some time now. I wiped all data and clean flashed it. I came from CAF40 and it's still as good as usual :D
[Nexus 5 Android Development] kenshin33:
on the bright side it installed over the old one without giving a headache :)
[Nexus 5 Android Development] wolfen69:
I tried the latest zip and dirty flashed it. It's the first time a dirty flash has worked 100% for me. Woohoo!

Been using this rom for about 4 weeks and so far it's been perfect. Awesome job.