yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] andrei1015:
Just noticed you have more of those special kernels of yours. Are they alright to use? Asking because you haven't announced anything about them since 31.10. Thanks!
[Nexus 5 Original Android Development] myfluxi:
I won't announce or enforce anything. More or less everything has been said about the situation. Under the hood, I'm ready to take even controversial measures to enforce a quality release for the N5 after almost one year. Give it some time until the dust around L settles and use whatever you like. Everything I upload is the best I can do at that time and latest should always be best.
[Nexus 5 Original Android Development] david23400:
Hello, on stock rom when i press the power button, the lockscreen appears instantly after it, but on cyanogenmod there is a delay before the lockscreen showes up, and that ennoys me a lot... Can anyone tell me what to do to fix that? Thanks!!
[Nexus 5 Original Android Development] rockknee:
I don't see any delays there.. You should try factory reset. If it doesn't help and you can't live with the delay just go back to stock.
[Nexus 5 Original Android Development] nexzor:
Myfluxi is allready informed, search for my last bugreport in jira i this thread. But don't expeckt any fix for it since the framework stuff is realy messed up in cm
[Nexus 5 Original Android Development] myfluxi:
No, it's not messed up and I never said that. I'm just saying that apparently some stuff needs to be sorted out. Which is happening atm, new CM 12.0 branches are forked from CAF and we're having plain HALs atm.

Let's see for how long.
[Nexus 5 Original Android Development] nexzor:
ok than sorry! i havn´t understand it correct english is not my first language
[Nexus 5 Original Android Development] myfluxi:
scho klar :)
[Nexus 5 Original Android Development] SWTR:
Wusste gar nicht dass du aus Deutschland kommst:)
[Nexus 5 Original Android Development] bland.life:
Theres some leak on Cyanogenmod's CM12 plans:

http://www.landofdroid.com/2014/cm12-roadmap-leaked-exciting/
[Nexus 5 Original Android Development] nexzor:
[MENTION=4152171]myfluxi[/MENTION] i just read that the codefreez for M12 was made on 31th of Oct. so i hope the fix for skipping lockscreen (http://review.cyanogenmod.org/#/c/76071/) will make it into this build.
[Nexus 5 Original Android Development] myfluxi:
The revert is on the stable branch. As I cannot call the N5 stable at all, I requested to skip the M release due to the well-known bugs.
[Nexus 5 Original Android Development] procitysam:
So does that mean no M12 release right away?
[Nexus 5 Original Android Development] dannyella:
Quick random Question. How often would you recommend a nightly flahsher to make a clean wipe? I do so, like once or twice in a week. Or there is really no need??
[Nexus 5 Original Android Development] Circaflex:
Technically not needed, I myself like to do a clean install if running nightlies day after day probably every two weeks. Steve has commented on this topic before and says you can dirty flash CM without any problems and shouldn't need to do a clean wipe.
[Nexus 5 Original Android Development] raydekok:
I never did a clean install.
[Nexus 5 Original Android Development] dannyella:
Thanks for reply. I ask because people are quick to recommend a full wipe when something is not working right which tbh has never really fixed anything for me.
[Nexus 5 Original Android Development] Circaflex:
ok? not sure why you quoted me to state that :confused:
[Nexus 5 Original Android Development] andrei1015:
From my experience full wipe and clean install does solve 99% of the problems but 80% of those problems can be solved without such a drastic measure. And I prefer the latter.

Flowed from my Nexus 5
[Nexus 5 Original Android Development] mmo.xda:
He!

I would like to report a possible bug. With the following combination: cm-11-20141102-NIGHTLY-hammerhead + 141102_kernel_NIGHTLIES_and_M.

I think is a kernel issue.

This morning has been first time I've charged the hammerhead switched off. The Phone does not switch off screen and everytime is always showning the battery charging (the One with the lighthing). If you press the on/off button Phone starts.

The actual behaivor should be shown this screen and then switch off. If you press the turn on button it should show charging level. If you press longer turn on button it should start.

I do not know if this has been resolved in latest kernel releases or it is happening with them to.

Regards

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] nexzor:
does not occur on caf22. so maybe you should try the newest kernel https://www.androidfilehost.com/?fid=95784891001606132
[Nexus 5 Original Android Development] mmo.xda:
Ok. I will try as soon as possible.

I've been able to flash since 2/11 'cause i' ve been away working. This Weekend I believe I will have time for hammerhead fun ?.

I've reported possible bug if it hasn't been noticed even though I know I'm having an Old nightly kernel combination. Maybe developer does not charge Hammerhead switched off (I do not do it regularly myself)... So possible use case passes unnoticed..

Regards

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] hanschke:
hope of new nightly never stop ;)
[Nexus 5 Original Android Development] mmo.xda:
Ok. Charging bug solved.

With latest combination (cm-11-20141108-NIGHTLY-hammerhead.zip + 141108_kernel_NIGHTLIES_and_M.zip) it is gone.

On the other hand, everything smooth and perfect.

Thanks again

Enviado desde mi Nexus 5
[Nexus 5 Original Android Development] VOLTAGEROCK:
I'm not sure which nightly you are on, but go to setting, display and lights, and scroll down to where it says prevent accidental wake up and uncheck that. I had that problem on a previous nightly and I don't see it in mind now. My current nightly is from the end of October and this feature doesn't seem to be in it. But it was in the nightly that was from the end of August. Try and see if you have that option and uncheck it and then every time you hit your power button, your screen should turn on immediately. It just mainly prevents and accidental wake up if you hit your power button and your proximity sensor is close to your skin. I never have that problem when my phone is in my pocket so see if this helps and if you can let me know.

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] fattire:
CM-12.0 in the repos... here's how to build...

To anyone building CM themselves, I just wanted to note that a cm-12.0 branch has been cut in the CM repositories on github, and there are device/kernel branches in staging/cm-12 (plus a caf staging build as well) for nexus 5.

Basically that means:

$ repo init -u https://github.com/CyanogenMod/android.git -b cm-12.0 && repo sync

(or use the staging/cm-12.0 or staging/cm-12.0-caf branches...)

gets you source. I believe you also need to add these lines to .repo/local_manifests/roomservice.xml :

<project name="CyanogenMod/android_device_lge_hammerhead" path="device/lge/hammerhead" remote="git

hub" revision="staging/cm-12.0" />

<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="git

hub" revision="staging/cm-12.0" />

You'll also need lge props/blobs which you can probably get from the factory image or wherever fine blobs are sold.

To see how to build cm11-- it's basically the same process-- check out the build wiki for hammerhead. If you haven't done this before, there are some small things you need to do like run vendor/cm/get-prebuilts, etc, but it's all explained in the wiki link.

Caveat: I'm building Lollipop now on cm-12.0 brack (not the staging one though that's probably what I should be using...) and haven't finished building yet-- no breakage so far but it's only 20 minutes in. This early in the CM porting/conversion process, YOU SHOULD EXPECT ALL KINDS OF ISSUES and carnage, but for those who know what they're doing or don't mind destroying their phone in the act of learning, it could be fun to break stuff.

Be sure to repo sync often as this is a time of great flux. I wouldn't install this over a current cm-11 installation because who knows what it might do. Also, be sure to check out gerritt for patches/fixes as they show up.

Cheers.
[Nexus 5 Original Android Development] vegas217:
Myfluxi

Where can I find the myfluxi builds at?

Edit: found it.
[Nexus 5 Original Android Development] procitysam:
Awesome work man, looking forward to it :D
[Nexus 5 Original Android Development] fattire:
Package Complete: /media/test/lollipop/out/target/product/hammerhead/cm-12-20141109-UNOFFICIAL-hammerhead.zip

-rw-rw-r-- 2 fattire fattire 214M Nov 8 19:55 /media/test/lollipop/out/target/product/hammerhead/cm-12-20141109-UNOFFICIAL-hammerhead.zip

Hmm. I'm kinda scared to try it. Dare I? :P
[Nexus 5 Original Android Development] ASHURiCAN:
Try it! And let us know! :P
[Nexus 5 Original Android Development] neobuddy89:
Steve cooking new kernel from google's

https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/staging/cm-12.0

:D
[Nexus 5 Original Android Development] SWTR:
Does this mean that we cen get CM12 in a few hours/days?
[Nexus 5 Original Android Development] neobuddy89:
Officially - I don't think soon.

But if someone uploads unofficial build, it would be anytime.
[Nexus 5 Original Android Development] EnginEAR:
if you upload it- I will try it :)
[Nexus 5 Original Android Development] SWTR:
Me too:)
[Nexus 5 Original Android Development] myfluxi:
CM L first build. For root access, use SuperSU and (only once) a kernel with permissive SELinux rules. This will now be my daily driver, 11.0 is more or less a thing of the past now.

cm-12-20141109-UNOFFICIAL-L-hammerhead.zip

The kernel lacks the not-yet-pushed LGE IRQ patch that stopped the relase, so battery might be bad. Display gamma is there with full compatibility plus other important patches.
[Nexus 5 Original Android Development] hanschke:
[MENTION=4152171]myfluxi[/MENTION]

which kernel do you use:confused: how to flash? Can I update ontop my cm11 and flashing the gapps (xdaforums.com/showthread.php?p=49497001). ElementalX-N5-2.01 will not work right?
[Nexus 5 Original Android Development] myfluxi:
Wipe, use the default kernel (which will be the best choice again) or any other L compatible kernel you like.

Remember that this is still 95% AOSP as almost no CM features have been added, yet. And don't forget to flash L radio and bootloader.
[Nexus 5 Original Android Development] Tylog:
Oh, nice one fluxi, download :) thanks for sharing
[Nexus 5 Original Android Development] hanschke:
I think it is the fast way to get android 5 instead of waiting for the factory image without losing my data:confused:
[Nexus 5 Original Android Development] ASHURiCAN:
You mean full wipe? System+data+internalSD?
[Nexus 5 Original Android Development] myfluxi:
Once the factory images are there, read up on how to avoid sdcard wipe by commenting the userdata image flash.

Only data, system will be formatted anyway.
[Nexus 5 Original Android Development] ASHURiCAN:
Ok, thank you for your great work!

Another question, can I use MultiROM to flash it as secondary ROM?
[Nexus 5 Original Android Development] mo976:
If i already repo synced lollipop r2 the other day there is no need to wipe my source directory, can I just do a new repo init pointing to cm12 and repo sync the cm12 stuff plus the prebuilts etc and then pull the device blobs with extract-files.sh and it should all work, correct?
[Nexus 5 Original Android Development] david279:
Is ambient display turned on in this build? I've been watching review.gerrit and didn't see anything, guess they were doing it all thru git right now.
[Nexus 5 Original Android Development] SWTR:
I hope notification led settings will be implent soon. I don't need more features:)

Anyway thank you myflux for the fast work.
[Nexus 5 Original Android Development] archish:
getting below error when I try to load cm12. Coming from L Dev Preview build.

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
[Nexus 5 Original Android Development] gpvecchi:
Me too... Any hint, please? I just made a factory reset from recovery before flashing...
[Nexus 5 Original Android Development] lolobarjo:
Same error here. Maybe it's the recovery related
[Nexus 5 Original Android Development] gpvecchi:
Latest TWRP for me...
[Nexus 5 Original Android Development] ssauger:
I got this too. Tried latest TWRP and CWM recovery. Also flashed 4.4.4 factory image, but without wiping internal storage, the only thing i left till now.
[Nexus 5 Original Android Development] obayda.bd:
Can't install it using multi ROM twrp recovery.
[Nexus 5 Original Android Development] mo976:
Probably not that's a nexus 6 feature and not part of AOSP.
[Nexus 5 Original Android Development] Tylog:
Build boot fine and is smooth. It's possible to install as secondary, something i like. No issues here. For now it's aosp pur like fluxi say but good to have a base now:)
[Nexus 5 Original Android Development] lolobarjo:
Do you have installed it with K.K. bootloader and after intalled L. bootloader or have you directly installed it on L. bootloader ?
[Nexus 5 Original Android Development] david279:
It actually is in the aosp code and just needs to be enabled.
[Nexus 5 Original Android Development] mo976:
You don't have a link by chance?

Edit: NM I found the bootloader in Vomers L IMG files on AFH so next question if I'm on HHZ11k is HHZ12d a must?
[Nexus 5 Original Android Development] kong:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy

This error can be ignored. Just wait patiently and the flashing will succeed.

The error is shown because /data is already mounted by TWRP.
[Nexus 5 Original Android Development] obayda.bd:
I have tried to install it as secondary but it said "failed to open zip".
[Nexus 5 Original Android Development] Tylog:
L bootloader, i use since a few days L Roms.

---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------

Yes, you need HKZ
[Nexus 5 Original Android Development] fattire:
So I read Steve was getting a crash off current hammerhead builds so I backed off on trying it as I kinda need my phone today and didn't have time last night to do a full backup, test the build, watch it crash, then restore... But hey- myfluxi posted a build above so I guess you can all try that instead.

I just repo synced this morning (pulled the newer source) and already there are two new packages, so everyone keep in mind it's likely to be really really unstable. To whoever asked "does this mean we'll have CM12 in a few days", it only means ther will be some AOSP (standard android)->CM hybrid as it becomes more and more CMized with time. I believe a ton of the repos that make this build are still pure AOSP and will be replaced slowly with CM repositories. Tthose CM repos themselves have to be integrated/rebased so that older patches to older android fit in... along with new ones... so it will be a long unstable process for a while. And the latest CAF stuff needs to come in too.

That said, it's fun to watch and help out. Anyone interested in the process-- I highly suggest your read the wiki so you understand what's going on, and I always encourage you to learn to build CM yourself. It really isn't that hard and is enormously satisfying, educational, and empowering.
[Nexus 5 Original Android Development] lowrider82:
Guys aside from franco kernel any other good ones you would suggest?

Sent from my Nexus 5
[Nexus 5 Original Android Development] j3di:
Yeah, try stock kernel. Cm merged a new kernel a few nightlies back and it is good in its own right.
[Nexus 5 Original Android Development] lowrider82:
Cool will try it. Any idea what the benefits are?

Sent from my Nexus 5
[Nexus 5 Original Android Development] j3di:
Much, much better battery life in a nutshell!
[Nexus 5 Original Android Development] juancaperez2000:
Somebedy know if i can get problems if i switch to art?
[Nexus 5 Original Android Development] :
Hi,

You need to remember that ART runtime is stiil "highly" experimental, so maybe expect some apps don't working well with ART...

The rom itself should not have issues, but who knows since ART is always in "beta" stage... For example if you use Xposed Framework, ART will not work (if you choose ART it will switch automatically to Dalvik runtime due to incompatibility).

And if you search for ART in this thread you will have some feedback, it seems that there is no issues with the rom.

:)
[Nexus 5 Original Android Development] BRiANj64:
DONT USE 20/01/14

The media volume slider is broken, it's always on loudest!
[Nexus 5 Original Android Development] juancaperez2000:
Thanks ill give a try
[Nexus 5 Original Android Development] Smallsmx3:
Is anyone using the cm camera instead on the stock Google one? Any comparison?
[Nexus 5 Original Android Development] Pwnna:
Confirmed. What does this key combination do anyway?
[Nexus 5 Original Android Development] R0axet:
Random reboot stock browser

Had one reboot on auto rotation while in browser on the 1/18 nightly.

Anyone seeing more random reboots?:confused:
[Nexus 5 Original Android Development] LamboBull:
It triggers the capture of a bug report on a stock rom which you send to Google. I kept getting this message because my case was pressing it because of the tightness, thankfully that feature is not in cm 11 ;)

Sent from my Nexus 5
[Nexus 5 Original Android Development] q1t1:
No problem for me with it (but I am using CM kernel)
[Nexus 5 Original Android Development] Pwnna:
Everytime I do this, everything crashes to a halt....

It looks like this feature /is/ there in cm11. There must be a way to disable this... I'll see if I can find it in the source..
[Nexus 5 Original Android Development] Chris123NT:
Probably a result of not using the CM kernel, bunch of kernel commits were merged last night (75 to be exact, look on github).
[Nexus 5 Original Android Development] Doopliss:
I can confirm this, but it only affects some apps. From what I tested Play Music and Giant Bomb Video Buddy were locked at max volume. Youtube and Rain Sounds could have their volume adjusted normally. This was with the stock kernel.

I guess it relates to low power vs. low latency audio playback?
[Nexus 5 Original Android Development] koelspy:
I'm using CM11 nightly with PA gapps: Stock package + Photosphere Camera + Google Dialer. If I go to APN settings I get FC:

E/AndroidRuntime(21350): FATAL EXCEPTION: main
E/AndroidRuntime(21350): Process: com.android.phone, PID: 21350
E/AndroidRuntime(21350): android.content.ActivityNotFoundException: Unable to find explicit activity class com.android.settings/com.android.settings.ApnSettings}; have you declared this activity in your AndroidManifest.xml?

I think this has something to do with the Google Dialer, but how to fix this?
[Nexus 5 Original Android Development] shotta35:
Not much maybe just report it but since Google Dialer is not in AOSP, not much can be done about it.
[Nexus 5 Original Android Development] MobyDick92:
I have the feeling that settings in the performance menu are set, but not applied to the kernel.... My max. Clock is set to 1,5Ghz, but in CPU spy i have the major time spent on 2,3 Ghz... Is there a fault on my side?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Smallsmx3:
Just set at 2. 25 for max and set on boot, it will stick, had that issue, seems to be fine, the new kernel is great
[Nexus 5 Original Android Development] procitysam:
Does CM12 have 1) LED controls and 2) Wi-Fi miscellaneous bug?
[Nexus 5 Original Android Development] Tylog:
No, it have no features, only base. About miscellaneous i let you know after formula1, i only flash it and make a boot, after this formula one started
[Nexus 5 Original Android Development] procitysam:
I figured that but just wanted to ask to be sure. I used Lollipop for a few hours yesterday and today, and sometimes I had the bug but then at other times I didn't.
[Nexus 5 Original Android Development] Tylog:
Yes, i know. Goggle fixed it but don't push it to the source, this **** was the reason for the update delay. But you are right. One day it's present , other day it isn't but i can't reproduced what exactly is the reason, we now wifi bit i use must time wifi. Let's hope it's really fixed with the realese.
[Nexus 5 Original Android Development] unknvvn:
Which gapps are recommended for android L ? Can i use normal PA gapps intended for 4.4.x?
[Nexus 5 Original Android Development] Mr-Glass:
I know Dhacker just put up new L gapps earlier today.... http://t.co/93KtocLXSI
[Nexus 5 Original Android Development] Tylog:
This http://xdaforums.com/showthread.php?t=2930260
[Nexus 5 Original Android Development] myfluxi:
Yeah, give it time (over 5 minutes or longer for now).

Chances are, we keep our clean Google HALs and I want to make sure, our device stays as much Google as possible as well. Certain patches will surely go in or are already there.
[Nexus 5 Original Android Development] mo976:
I'm guessing calendar sync is a gapps problem! Anyhow for a first build its working very nicely! Thanks [MENTION=4152171]myfluxi[/MENTION]
[Nexus 5 Original Android Development] rampino:
anyone got the Google+ fix working with this cm12 first build?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] mmo.xda:
Please, use a CM12 THREAD or something. But please, keep this for CM11.

Thanks in advance

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] richarddwyer10:
Could you please give me a link for the cm12 thread, I can't find it anywhere thank you very much.
[Nexus 5 Original Android Development] herna:
Use this gapps, they has Google+ fix included.

https://www.androidfilehost.com/?fid=95784891001607224
[Nexus 5 Original Android Development] topgeardave:
Before I flash, could I just ask if cm12 unofficial contains the files which screw your recovery partition?
[Nexus 5 Original Android Development] ramjet73:
CM12 ROM Thread

New thread for the CM12 ROM in the General Forum.

I hope [MENTION=4152171]myfluxi[/MENTION] doesn't mind and I will close that thread if he decides to create his own.

ramjet73
[Nexus 5 Original Android Development] Barracuda77777:
it worked for me, I copied the folder ".repo", into a cm12 folder, then re-init to cm12 sources, 10 minutes later its done :)
[Nexus 5 Original Android Development] mo976:
I stand corrected and now the commits are open in cm git review for ambient display on hammerhead.
[Nexus 5 Original Android Development] olus:
lol.. everyone moved to the cm12 thread? ;)
[Nexus 5 Original Android Development] ramjet73:
As the saying goes, "Be careful what you ask for because you just might get it." :cool:

ramjet73
[Nexus 5 Original Android Development] Koragg618:
Well he did ask for it. CM11 is essentially dead now, maybe after the final release, and CM12 will take the thread's place.
[Nexus 5 Original Android Development] sam razzy:
Huh! I'm late to the party. Before i flash this testbuild of cm12 i would be glad if someone tell me whether any feature merged or is it just stock build..?
[Nexus 5 Original Android Development] lcrponte:
Hi,

http://xdaforums.com/showpost.php?p=56623594&postcount=9810

Regards.
[Nexus 5 Original Android Development] enigma9o7:
Aha! I have this problem too (with CM11 20141104 Nightly on a different phone) and was searching for it, in my case it always shows "No devices connected" even when my laptop is connected... haven't tried any other devices. So must be a cyanogenmod related issue.
[Nexus 5 Original Android Development] fluther:
Same here, Kindle connects fine, but the notification still says 0 clients connected. Works anyway though.

Also, M12 is rolling out now, seems to have skipped hammerhead? Should we expect a build later, or will there be no m12 for the N5?
[Nexus 5 Original Android Development] DanderMan:
What a pity. I think it has something to do with following postings:

Perhaps someone like myfluxi can provide us with more information