yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Carlos_Manuel:
Next version of this ROM will have more avc denials fixed which need fixing..

W/wpa_supplicant( 500): type=1400 audit(0.0:3): avc: denied { sendto } for path="/data/misc/wifi/sockets/wpa_ctrl_26980-1" scontext=u:r:wpa:s0 tcontext=u:r:sudaemon:s0 tclass=unix_dgram_socket

W/netd ( 408): type=1400 audit(0.0:4): avc: denied { fsetid } for capability=4 scontext=u:r:netd:s0 tcontext=u:r:netd:s0 tclass=capability

W/Thread-16451(28785): type=1400 audit(0.0:5): avc: denied { getattr } for path="/factory" dev=mmcblk0p3 ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:efs_file:s0 tclass=dir

The current version of this ROM feels a little bit smoother than the older versions, but I still haven't figured out how to fix the proximity sensor. :confused: :eek:
[Samsung Galaxy Nexus] jrs007:
Carlos where are the files responsible for chromecast, wifi display?

I need to know the way.

:confused:

thanks
[Samsung Galaxy Nexus] Carlos_Manuel:
https://github.com/Dreams-Lp

device/samsung/tuna

wpa supplicant_8

and frameworks/av
[Samsung Galaxy Nexus] Carlos_Manuel:
I've tried a lot of things to get proximity fixed.

What I've tried so far:

A Clean flash

Sepolicy changes

I've also tested my ROM with freshgiammi's sepolicy changes as he does not have same sepolicy changes as I have, also his RIL sepolicy changes differs from mine. I thought SELinux is breaking proximity sensor but no.

I've tried my LP kernel on my KK ROM and everything work perfectly on KK even the proximity sensor so kernel is OK too!

I've flashed Ziyann's CM12 for testing and on it proximity works perfectly.

I have no idea what's breaking proximity sensor. I'm now using all the same sensor changes on device tree as ziyann on his CM12 device tree, so device tree should be OK..

I'm desperate. Any help would be great...

These are the all changes from KK and LP that I've made/applied to stock JB 4.3.1-r1 device tree and none of those changes should break proximity.. https://github.com/manumanfred/test-devicetuna/commit/c336316d352a1d694de25fa882ed7f122249e467
[Samsung Galaxy Nexus] Carlos_Manuel:
Could someone with CM12 sources try to build CM12 with my device tree, kernel repositories and with these vendor files to see if proximity sensor works correctly on CM12?

https://github.com/Dreams-Lp/device-samsung-tuna

https://github.com/Dreams-Lp/device-samsung-maguro

https://github.com/DreamsTuna/android_kernel_samsung_tuna

I have myself no other computer to build CM12 as my old notebook has no HDD and its charger is damaged.. I really need to get that proximity sensor fixed. :eek:

Btw. next version of this ROM will have camera calibration fixed which also fixes camera after a clean flash. Also the next version requires a clean flash.

If I cannot get it fixed, then probably I will abandon this ROM or move back to KK.
[Samsung Galaxy Nexus] s107ken:
hi,

download cm12 source code, replace 4 directories to your github repos, then building.

// replace 4 dirs
/cm12/device/samsung/tuna
/cm12/device/samsung/maguro
/cm12/kernel/samsung/tuna
/cm12/vendor

// 1st build
$ cd cm12
$ source build/envsetup.sh
$ lunch aosp_maguro-userdebug
$ make

// build error & workaround fix?
hardware/ti/omap4xxx/hwc/hwc.c:52:27: fatal error: video/dsscomp.h: No such file or directory
$ cp -a /cm12-original/device/samsung/tuna/kernel-headers /cm12/hardware/ti/omap4xxx

// 2nd build
$ make
$ make bacon

coundn't booted :(

cm-12-with-carlos-20150228.zip

md5:c07bb3636c75fd522d9a0483a63c1265

https://drive.google.com/file/d/0B1NZ-kUcUidjUHJrWndCbXlBSjg/view?usp=sharing

any ideas?

tomorrow, i'll try pure cm12 building.
[Samsung Galaxy Nexus] Carlos_Manuel:
Try this: https://github.com/MWisBest/android...mmit/6c9dae1b5ff51c14575d415a5aeb0e2784e3b59b
[Samsung Galaxy Nexus] Carlos_Manuel:
Since I can't get proximity sensor fixed, I probably give up messing with AOSP.

I'm going to download cm12 sources and I'll try to build CM to see if proximity works on CM... if not... then I really don't know what is breaking proximity sensor when it's not SELinux, kernel or the device trees..

I just don't have time to mess with this, also I don't want to use KK again..
[Samsung Galaxy Nexus] Carlos_Manuel:
Good News and bad News..

Proximity sensor works perfectly on CM12 but it doesn't work correctly on AOSP and I am not going to use CM12 as a base for this ROM because I like AOSP more.

I really don't want to start using CM as a base again.. :/
[Samsung Galaxy Nexus] nikodr:
Other aosp roms do they have the proximity sensor working ok?

What if you only take the source code for the sensor and nothing else?Where are the files that deal with the sensor?
[Samsung Galaxy Nexus] Carlos_Manuel:
I don't know about other LP ROMs...

It's not that easy... I cannot find the commits which are required to fix the proximity sensor for maguro.. And there's noone who could help me...
[Samsung Galaxy Nexus] sgspluss:
Dont know about sensor problem but what you could try...

Add CM repo and replace aops sensor line(s) with cm once in your manifest.

Maybe there will be more dependencies, if its so you have to replace also them with cm once.
[Samsung Galaxy Nexus] Carlos_Manuel:
There's nothing to replace... device trees and kernel are both Ok.. I'm already using Ziyann's libsensors as those works fine

replacing repos with different project repos just gives you errors..

What I think, the problem is in frm/base but I've already checked the 30 pages of commits but I only foun two of the commits which could work but Ive already tested them on AOSP and didn't work..but there's lot of more telephony, msim commits in CM's repos..
[Samsung Galaxy Nexus] nikodr:
As this rom is very interesting and the only one so far to have usb audio,can't you ask for help from aosp or the other kernel gurus?I think it would be a waste to lose such a rom because of a proximity sensor not working,maybe the others could help you?

I would love to have a rom with usb audio working.
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm going to do some tests, maybe I can get prximity to work some day. :D

[MENTION=2744041]nikodr[/MENTION] Including USB Audio support is easy. In the Kernel's config file config_snd_usb_audio must be enabled and then just a few modifications to device/tuna and you will have USB audio support on Nexus. but... It's not working perfectly yet and I hope other GN ROM/kernel devs will try to get it working better on our Nexuses. :cool: as currently it's not working perfectly.
[Samsung Galaxy Nexus] Carlos_Manuel:
Proximity sensor seems to be fixed now.

This is the new organization profile where I made modifications to RIL..: https://github.com/DsLp-test

Thanks to Ziyann for helping me as much as he could.. :), mwisbest for his RIL commits.. and freshgiammi (I took most of the RIL commits from his repos..)

I don't know what exactly broke the proximity sensor, but I'm really happy I got it fixed. :cool:

Dreams version 5.3.1 should be available in a week.
[Samsung Galaxy Nexus] nikodr:
Thumbs up :) Ι feel great that other rom developers and gnex guys helped you.

It would be sad to have one less rom developer for our Gnex,we need all the good guys we can have making roms.
[Samsung Galaxy Nexus] Bad Tiger:
can any test your build for lollipop?

because i can't find download links
[Samsung Galaxy Nexus] Carlos_Manuel:
Download links are in the (first post) OP.

system.img and boot.img (no ota zip yet..)

A new build should be available in 2 hours.
[Samsung Galaxy Nexus] Carlos_Manuel:
Dreams v 5.3.1:

Download links are in the first post and changelog of v5.3.1 is in the second post.

Proximity sensor is working properly now

Video playback on the Google play movies works now

etc.

Next version:

Revert "Fix memory leak where we close the descriptor instead of the file."

FORCE_SCREENSHOT_CPU_PATH

Remove built-in root.. It doesn't get flashed like for some reason..

Flash-able OTA zip package

More avc denials fixed

etc.

...
[Samsung Galaxy Nexus] ALBIEL:
Graphical glitches?
[Samsung Galaxy Nexus] Carlos_Manuel:
Yep. I've not included any workarounds to fix those glitches. :)
[Samsung Galaxy Nexus] rubikqj:
I flashed it, now it's still booting. I noticed in the logcat this errors, are they normal?

It does this for every app!
[Samsung Galaxy Nexus] Carlos_Manuel:
Flash this ROM with these gapps:

https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20150222-signed.zip
[Samsung Galaxy Nexus] rubikqj:
Ah that's why. I already had another gapps package so I used that one. It's working well nevertheless, so I am not going to reflash.

The ROM is super smooth, thank you so much! It's really a great experience. The only problem I encountered were the graphical glitches that you mentioned above. Not a big deal IMHO, I can live with it.

I have two questions:

* Is it possible to get quick settings when swiping down from the right? It would be very convenient. Currently one has to do a double swipe down.

* Do you think you will add CM12 Theme Engine in the future?

Thanks again!
[Samsung Galaxy Nexus] Carlos_Manuel:
:) Np.

About "right pull QS": I may include that to the next build if I'm able to port it from CyanogeMod without any problems.

One of the reasons why I don't use AOSPA or CM as a base for this ROM is because of the theme manager. It's great but it will eat pretty much of memory and battery. At least for now I'm not going to include any theme manager to this ROM.

Currently I have a goal to get this ROM as stable as possible.

I must get these bugs fixed:

1. white background in "screenshot captured" notification:

2. Status bar brightness slider...

3. graphical glitches
[Samsung Galaxy Nexus] phaleg:
In the first post I read the following:

- flash through fastboot ...

after a bit I read instead:

put files in the phone and use the recovery....

Which one then? Can I do from TWRP that is easier then?

Thanks
[Samsung Galaxy Nexus] Carlos_Manuel:
I didn't didn't make a new thread for lollipop builds so the first post is a bit confusing.. Next build will be in a flashable zip. After getting a ew build ready, I'll update the information from OP and clean it a bit...

for now.. flashing 5.3.1 you must use fastboot. I think new build will be available in 24 hours..

EDIT: I'm not familiar to TWRP even thought I'm currently using it by myself too. I don't know can you flash any img files trough twrp
[Samsung Galaxy Nexus] Carlos_Manuel:
It's going to take a while to update my sources to lollipop 5.1 as I'm not any expert with git.., I have to update the sources a more difficult way and this way will take a lot of time...

Next version of this ROM will be based on lollipop 5.1 "LMY47D"
[Samsung Galaxy Nexus] fearlessaryan:
Thats fine but can you upload the flashable zip for this :)
[Samsung Galaxy Nexus] Carlos_Manuel:
As I said in post #1091, next build will be in a flashable zip.

So no more .img files to flash.. :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Here we go...

https://github.com/Dreams-Lp/manifest/commit/5729da1a9b5f7404da8e19057afb089719285136 AND https://github.com/Dreams-Lp/manifest/commit/bfbb9d9a6b73582cead7ad98462c066527c9103d
[Samsung Galaxy Nexus] Carlos_Manuel:
Dreams version 5.3.2: (Test version)

Lollipop 5.1 LMY47D

https://drive.google.com/file/d/0BxlYDVLp_RkMd3JMejRvVWNWaEE/view?usp=sharing

A little story:

[IMG="--"]https://lh3.googleusercontent.com/-shy_YMSNJnk/VP9YwY4wg5I/AAAAAAAACB8/gmQXKw9hxhA/w608-h342-no/output_mte901.gif[/IMG]
[Samsung Galaxy Nexus] fearlessaryan:
trying

---------- Post added at 09:12 PM ---------- Previous post was at 09:08 PM ----------

Can I try doing a dirty flash on latest CM 12 build ???
[Samsung Galaxy Nexus] Carlos_Manuel:
Most of the changes done for Dreams v5.3.2 (LP 5.1) are the same as in Lollipop 5.0, but most of the customization features are not included on this test version. Probably most of the memory leak commits won't be included as most of the memory leaks are fixed on LP5.1 AOSP...

This build seems to be really stable. Also this feels pretty smooth

Changes in tuna device tree:

releasetools.py: Remove journaling from read-only FS to save space

BoardConfig.mk: Disable journaling to save system.img space.

Enable PIE for tuna

Upcoming changes:

Fixes/workarounds for graphical glitches.

Maybe Grouper's DRM libs (I have to test them before)

Kernel:

most of these commits will be pushed to the kernel:

f5d7b8b tegra3_android_defconfig: disable HW crypto engine by Iliyan Malchev - 9 weeks ago android-tegra3-grouper-3.1-lollipop-mr1 android-5.1.0_r0.4
a2a15f1 tegra3_android_defconfig: enable CONFIG_CRYPTO_AES_ARM by Iliyan Malchev - 10 weeks ago
db7324a ARM: 8120/1: crypto: sha512: add ARM NEON implementation by Jussi Kivilinna - 7 months ago
9e41649 ARM: 8119/1: crypto: sha1: add ARM NEON implementation by Jussi Kivilinna - 7 months ago
284f62c ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures by Jussi Kivilinna - 7 months ago
8c5d905 crypto: arm-aes - fix encryption of unaligned data by Mikulas Patocka - 8 months ago
85ff160 CRYPTO: Fix more AES build errors by Russell King - 1 year, 2 months ago
01199e3 ARM: add .gitignore entry for aesbs-core.S by Russell King - 1 year, 5 months ago
363d286 ARM: add support for bit sliced AES using NEON instructions by Ard Biesheuvel - 1 year, 6 months ago
be8b38f ARM: move AES typedefs and function prototypes to separate header by Ard Biesheuvel - 1 year, 6 months ago
aa62fd4 ARM: 7837/3: fix Thumb-2 bug in AES assembler code by Ard Biesheuvel - 1 year, 6 months ago
d8f23c7 ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling by Ard Biesheuvel - 1 year, 10 months ago
674126b ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible by Dave Martin - 2 years, 2 months ago
8c73ff8 arm/crypto: Add optimized AES and SHA1 routines by David McCullough - 2 years, 6 months ago
bfd5c1b net: ipv6: allow choosing optimistic addresses with use_optimistic by Erik Kline - 3 months ago
954e7e0 net/ping: handle protocol mismatching scenario by Jane Zhou - 4 months ago
9e6ff30 cgroup: remove synchronize_rcu() from cgroup_attach_{task|proc}() by Devin Kim - 5 months ago
085ab6c net: ipv6: Add a sysctl to make optimistic addresses useful candidates by Erik Kline - 4 months ago

Most of the stuff from my LP5.0 sources

---
[Samsung Galaxy Nexus] Carlos_Manuel:
You can try dirty flashing.. but I recommend to make a clean install
[Samsung Galaxy Nexus] fearlessaryan:
Its showing android written on the screen and going on for a while :( Should I stop it and do a clean flash or should wair more ?
[Samsung Galaxy Nexus] Carlos_Manuel:
It might take something like 10-20 minutes on a first boot
[Samsung Galaxy Nexus] fearlessaryan:
Ok does ur ROm has a fix for offline charging means its still on boot animation or installing the rom. Can I plug charger at this point??
[Samsung Galaxy Nexus] Carlos_Manuel:
Offline charger works just fine on this ROM
[Samsung Galaxy Nexus] alboz83:
Great the first 5.1 rom, thanks!!

Camera has green lines in video recorder? And video recording in 1080p are smooth or laggy?
[Samsung Galaxy Nexus] ibraheeemz:
How's the stability? Plus video recording had lines before, still present??
[Samsung Galaxy Nexus] Carlos_Manuel:
https://www.youtube.com/watch?v=WmR2UJyS-lw&feature=youtu.be 1080p recored video is smooth. Yes that green line won't go anywhere yet... ;)

Stability compared to other LP ROMs for tuna which uses ddk1.9, I don't know. As this ROM is using ddk 1.8 and performance is really good for me. :)
[Samsung Galaxy Nexus] fearlessaryan:
Just opened aaahhhhhh. It took sooooooo long :). Just setting it up will give feedback after some use. thanks :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Great! :)

Yeah, unfortunately a first boot takes a long time.. Thanks to ART and deodexed system.
[Samsung Galaxy Nexus] fearlessaryan:
First Impression : Every things working nicely. Graphics glitches but bearable not too worry some. video green line. Except that I feel its fast. I just came from CM 12 the icons seems so big :p

Thanks for the effort
[Samsung Galaxy Nexus] Carlos_Manuel:
Nice :good: :)
[Samsung Galaxy Nexus] Namautoenx:
Where is "Zip file" of Rom?I can't find it ,pls help!
[Samsung Galaxy Nexus] Carlos_Manuel:
It's in the OP (first post)!

https://drive.google.com/file/d/0BxlYDVLp_RkMd3JMejRvVWNWaEE/view <--- https://docs.google.com/uc?export=download&confirm=Hn6g&id=0BxlYDVLp_RkMd3JMejRvVWNWaEE
[Samsung Galaxy Nexus] rambhanushali20:
How can i Install the latest version.?

---------- Post added at 08:37 AM ---------- Previous post was at 08:33 AM ----------

I mean is it a full rom package for i have to flash it over something..?
[Samsung Galaxy Nexus] Carlos_Manuel:
Put the zip package to Nexus or flash it via adb sideload while you are on recovery and then flash GApps.

1. Boot into recovery

2. Wipe factory data reset (Clean flash) or wipe cache and dalvik cahce (dirty flash)

3. Flash the ROM (install from internal storage), or install from ADB sideload

4. Flash Gapps

5. reboot
[Samsung Galaxy Nexus] entravink:
well.. downloading now.. will be tested soon
[Samsung Galaxy Nexus] obscurer:
just booted, feels really solid and smooth

very good work!
[Samsung Galaxy Nexus] Namautoenx:
Thank you,my bad.
[Samsung Galaxy Nexus] Carlos_Manuel:
Full ROM.. Just flash it like how you flash other ROMs. using dirty flash method or clean flash.

:good: :)

:) Thank You for the feedback! :))

Np. :)
[Samsung Galaxy Nexus] girkev:
Much more than I expected . Very Well done!!!
[Samsung Galaxy Nexus] Namautoenx:
+1000
[Samsung Galaxy Nexus] castaway1:
is 5.1 good (fast) enought for daily use?
[Samsung Galaxy Nexus] cartman333:
Can i flash Bsmittys full auto kernel? or is it bootlooping? :D
[Samsung Galaxy Nexus] fearlessaryan:
Test is and let us know :)

---------- Post added at 01:59 PM ---------- Previous post was at 01:58 PM ----------

For me its pretty good :)
[Samsung Galaxy Nexus] cartman333:
As soon as my phone is charged, im gonna flash this ROM and give it a try then reporting back ASAP. :D if it boots with the kernel or not.
[Samsung Galaxy Nexus] rambhanushali20:
Does not work with R11 kernel... It bootloops
[Samsung Galaxy Nexus] phaleg:
Ok, small noob question from me...

I read many expert saying that deodexed is slower (at least on first boot) and some says it's laggy, so what's the good part of using deodexed?

About art, I am reading that it's a runtime that replaces Dalvik to be faster than it. Is my understanding correct?

By the way, I am trying to push my wife to install this ROM, since I don't have a Nexus anymore. :highfive::highfive::highfive:
[Samsung Galaxy Nexus] fearlessaryan:
[MENTION=4022928]Carlos_Manuel[/MENTION] any plans of adding the tap to wake / swipe to wake implementation in the Kernel.
[Samsung Galaxy Nexus] girkev:
Some Browser FC ocurred. Both Chrome and Firefox.

Anyone else with this issue?

sent from my maguro
[Samsung Galaxy Nexus] obscurer:
I used AOSP browser and Opera without problems

must say this rom is a really first that feels solid Lollipop on GNex so far!
[Samsung Galaxy Nexus] prozac:
i tested a 5.0.2 release and this one, iam not happy with that Android 5.*

because i cant turn off the vibration, i cant chance the Pop Up Style ( turn it off )

and if i rotate the screen, the screen always glitches !

Can anyone help me?
[Samsung Galaxy Nexus] fearlessaryan:
Glitch is the problem which is already discussed by the dev. You should have gone through the forum once before the installing it. go to other sounds switch off the vibration if u are uncomfortable with keyboard vibration go to keyboard AOSP setting and stop it.

Which pop up u are taking about I am not sure.

Please do not say that you are not happy and all. You can ask for help for these things but please do not provide negative feedback.

Thanks,

fearlessaryan

---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------

I would recommend to stop sending the report to firefox and chrome increases there performance. I am not too sure, I use both of them while installing I un-tick the option to send the health report and ....... every other thing.
[Samsung Galaxy Nexus] prozac:
Aight, thx for help anyway.
[Samsung Galaxy Nexus] Carlos_Manuel:
Well.. I've used my lollipop ROM a long time now. so I think, yes this is good enough for daily use! :)

It will bootloop. His kernel is for lollipop ROMs with the new ddk 1.9. :)

Read this: http://codeversed.com/deodexed-vs-odexed-rom/ :)

I've not really seen any improvement on the speed while using ART on my Nexus. optimizing apps takes a long time on ART, which also makes the first boot last much longer.

There's not really any big noticeable difference in the performance with odexed vs. deodexed apks.

I have not seen any double tap or swipe commits for Nexus's kernels. I've only heard about those apps but I never tested those apps..

After a little testings Chrome worked fine for me without any crashes or force closes. Anyways I use myself AOSP browser

Unfortunately Lollipop doesn't have the full silent mode anymore.

Glitches should be fixed on the next build.

_______________________________________________________________

So far the only bug I've found is Unknown carrier text on the lockscreen:
[Samsung Galaxy Nexus] rubikqj:
I feel dumb, but I don't find a setting anymore. I set a PIN for my device, and usually when I typed it right the phone unlocked without the need to press the tick mark (=enter). Now I always have to press it. I remember there was an option that allowed to login as soon as the code was correct, has it been removed?

Also, in the power button menu I see only "Power off", is that intended?
[Samsung Galaxy Nexus] Carlos_Manuel:
Those features are removed for now. Some of those features will be added back later. First I have to fix those graphical glitches.
[Samsung Galaxy Nexus] ibraheeemz:
There is silent feature, use volume up or down, if you choose none, it will turn silent on. Also for priority notification you can set it to work as silent.
[Samsung Galaxy Nexus] opticyclic:
Shouldn't that be mentioned on the original post as an outstanding bug?

Its not exactly "Everything is working." either then is it?
[Samsung Galaxy Nexus] Carlos_Manuel:
Video recording with the green line is on every Galaxy Nexus LP ROMs. Even though.... video recording works fine, but just that green line is there.

Even invert colors feature doesn't worn on LP ROMs for Galaxy Nexus... but why should I mention those common broken things in the OP?

To make you happy, I updated OP.
[Samsung Galaxy Nexus] werty100:
For my i have the bug of chrome closing after few seconds

And lockcreen in roamimg for my shows the carrier
[Samsung Galaxy Nexus] Carlos_Manuel:
Hmm okay.

For some reason there's unknown carrier on the lock-screen when roaming on EMT operator.. I don't know if this same happens on any another operator. Normal operator "Sonera" works fine.

About Chrome. I have no idea.. it works fine for me.Did you make a clean flash when you installed Dreams v5.3.2? Also which Gapps you are using?
[Samsung Galaxy Nexus] werty100:
i have change to maxthon and it works good :p

I make a dirty flash i was in 5.0.2 fml and i flashed yours + 5.1 pa gapps micro
[Samsung Galaxy Nexus] Carlos_Manuel:
Dirty flash is the problem..
[Samsung Galaxy Nexus] werty100:
Please look in github my pull request they are improvement for speed and also for graphic card
[Samsung Galaxy Nexus] ILA:
So this isn't a ddk 1.9 bug, but a LP one?
[Samsung Galaxy Nexus] Carlos_Manuel:
If you read the OP, you see this ROM is using ddk 1.8.

So, yeah. that isn't caused by ddk 1.9
[Samsung Galaxy Nexus] Astug:
Cheers for the update. Looks like 5.1 made LP a more stable build for the GN, which is what I was hoping for.

I'll wait for you to finish the next build, the kernel changes sound interesting.
[Samsung Galaxy Nexus] adamgraver:
Does anyone know if the camera works without crashing and requiring a reboot in this ROM? :D
[Samsung Galaxy Nexus] obscurer:
Camera working without FC's. I use this rom as daily driver from the day it was released.
[Samsung Galaxy Nexus] MrPutuLips:
Using 5.1. ROM's damn fast, and haven't had any memory leaks yet. Chrome hasn't crashed yet, either. Only problem so far is artefacts in the recents menu thumbnails and when rotating the screen.