yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chaoslimits:
Feels good. Voice+ crashes on a clean install though. Will return when it's fixed.

Edit: Voice+ removed from new nightly and Bluetooth Share force closes (even before phone is setup).
[Samsung Galaxy Nexus] EvilDobe:
Run from boot to launcher. Once you get to launcher hit CTRL+C. It will appear to be doing nothing but when you open the text file it will contain a log. Please post that to help squash any bugs.

adb logcat > C:\path\you\can\find\error.txt

Thanks!
[Samsung Galaxy Nexus] chaoslimits:
Already went back to Vanir (cos of Voice+). I'll reinstall later today and download the logcat.

Also, it seemed like Voice+ was missing a permission. I think it was Notification Cancellation.
[Samsung Galaxy Nexus] sickopsycho:
Giving this a whirl as development for FTL has all but ceased for the time being. Seems pretty straight so far- will report back after a little more usage... Thanks, [MENTION=633993]EvilDobe[/MENTION]
[Samsung Galaxy Nexus] jlsesler:
This is running very nice. I don't like or need a lot of features, and this certainly fits that bill. Having said that, I would like to see a few more minor features added (I.e. more status bar options, nav bar long press, etc). Also, maybe I am missing something, but the keyboard swipe isn't working. I don't see a setting to toggle it.
[Samsung Galaxy Nexus] EvilDobe:
Sounds like when you're looking at your Language & Input settings you have AOSP keyboard selected. You need to get the Google keyboard from play (or random gapps have it too) and then enable it. Once you get that Google Keyboard you should be golden.
[Samsung Galaxy Nexus] reitman1:
Did you find out if it works with ASPK?
[Samsung Galaxy Nexus] Saythis:
It does. It also works with Golden since it's based off of ASKP.

Edit:

Here's ASKP Build 19MR2 on this ROM:
[Samsung Galaxy Nexus] t1.8matt:
No, sorry i did not. i've been so busy i haven't had a chance to even flash CFX yet. But if Golden does work with it then ASKP should work also.
[Samsung Galaxy Nexus] modernbummer:
ASKP works fine. The latest version even works with PGM.
[Samsung Galaxy Nexus] sickopsycho:
PGM works fine with the supplied kernel- which is Tinys if I'm not mistaken...
[Samsung Galaxy Nexus] bigrushdog:
All those bells and whistles are coming. Plus actual unique features with unique original code. Because we are actually programmers lol. This project is ongoing development. So you can always expect new things. But first, we gotta get things strong and stable. I'm aware of the bluetooth obex fail. It is project wide across all devices. Also, I'm working overtime getting legacy devices like Xoom and tf101 online. So, in the meantime, if you find fail, blame [MENTION=633993]EvilDobe[/MENTION]. When you find win, thank me ;p
[Samsung Galaxy Nexus] modernbummer:
Definitely looking forward to the continued development.
[Samsung Galaxy Nexus] MoNsTeReNeRgY22:
Loving this rom, this thing is rock solid and flies. Blows anything else I've tried on my phone lately out of the water! Keep up the good work.
[Samsung Galaxy Nexus] TuxDroid:
Has anyone whose tried this also tried Slim Bean beta 2? I have been really impressed but wondered how they compare speed & stability wise. Thanks!

Edit: to clarify, Slim is the one I have been impressed with.
[Samsung Galaxy Nexus] EniGmA1987:
This ROM looks great!

One request though, which I hope all ROMs get to implementing soon, CM now has the open sourced "Voice+" app (from Koush), which integrates Google Voice into any messaging app. Would it be possible for you to integrate this code and app as well so that GVoice users can have a better time using this ROM?
[Samsung Galaxy Nexus] bigrushdog:
I've looked at the source for this as well as other cm privacy /security enhancements. To be honest, if we want to implement these things, we might as well just fork their framework tree. And I just don't foresee that. At least not at this time. Core functionality comes first.
[Samsung Galaxy Nexus] chaoslimits:
Seems like it was taken out of the first beta (it was missing a permision). Needless to say it was FC'ing.
[Samsung Galaxy Nexus] mosshorn:
Awesome. With the battery improvements in 4.4+ this rom, I smell infinite battery!

In other news, I would buy the N5 in a heartbeat if I had the cash. Not many phones make me drool, but wow.
[Samsung Galaxy Nexus] dsr13:
Getting G+ FCs. Seems to be a dalvic issue. Log is here: https://db.tt/D61zshJr
[Samsung Galaxy Nexus] Maikai.Guy:
Lost recovery

Deleted question - Asked before fully investigating. Nevermind. :-/
[Samsung Galaxy Nexus] dsr13:
Well my Nexus 5 arrives Friday so I just want to say that I really hope cfXe comes to my new device... You guys are amazing, bleeding edge, and what real "development" is all about... Thank you so much for making my gnex (and hopefully my N5) incredible!

Dan
[Samsung Galaxy Nexus] EvilDobe:
Some Notable Changes

Implemented a very clean weather service with the help of jug6ernaut, and added a setting to show weather info in the expanded statusbar header. (bigrushdog)

A few code fixes.

Merged a massive camera/media update from the CAF. (bigrushdog)

Updated all our develop_34 branches for our LLVM suite toolchain, and added support for xiw's awesome "stack"

Fixed compiler-rt aeabi_mem* routine behavior to allow Android libc building and linking properly ;)

I also updated the OP with the latest PA gapps for 4.3 & 4.4 I have yet to try the 4.4 stuff with our ROM so use it at your own risk. If you try 4.4 gapps let everyone know what your results were. I'll be updated soon & if I have anything wonky happen I'll do the same.

(Edit: 4.4 gapps boots but there is no launcher. I would imagine if you push Nova 'er something it would work fine. I just re-flashed & called it a day.)

Toro nightlies - As always SORT BY DATE. There are two pages of .zips so make sure you get the latest & greatest.
[Samsung Galaxy Nexus] dx1881:
G+ force closes repeatedly:( not sure why seems to be the only app
[Samsung Galaxy Nexus] bigrushdog:
Should be fixed next build.
[Samsung Galaxy Nexus] EvilDobe:
How's the latest nightly going for everyone? G+ bug fixed for you?

Also, if you have a moment, check out the new beta site http://beta.codefirex.com. Register.. chat... comment. [MENTION=4065411]ajf64[/MENTION] has been working his tail off to get the site up & running. As soon as I stop being lazy I'll get a toro thread posted up there as well but I may wait until the site is "live" and out of beta.
[Samsung Galaxy Nexus] EvilDobe:
Notable project changes

Qualcomm CAF dependent devices

Update audio-caf from CM. Supports Moto X audio

HTC One

Update some camera libs from muppets

Project wide

Update weather service. Make service sticky when enabled. Was getting destroyed after a while. Cleaned up refresh in settings activity. Added new forecast layout. The layout is a work-in-progress. Icons coming soon.

Synergy fixed the wonk we had in many user apps including the "acid trip" in NetFlix and fc when starting Google Plus. It appears there are some lingering issues with some apps in the HTC 8960 series and that is being actively researched. Great job Synergy!

News

We continue to wait patiently for the AOSP to reconsile the KitKat release with the master branch. Many of our device maintainers have already begun preparing their device trees for the merge. Hang in there! The wait is almost over!

I've also updated the OP with the latest SuperSU 1.69. Please consider updating as soon as possible.

SuperSU Changelog

- XBIN mode (some new roots need this)

- Slightly adjusted binary installer

- Backup script installation now available for all backuptool-capable ROMs

- Fixed su-ing to a non-root user not working on some 4.3+ firmwares

- Fixed BOOTCLASSPATH vulnerability (CVE-2013-6774) - Fixed notification sanitization vulnerability (CVE-2013-6775) - Fixed possible closed special files vulnerability

- Updated language files
[Samsung Galaxy Nexus] EvilDobe:
Android 4.4 aka KitKat has finally been merged into AOSP's master branch and the behind the scenes work has begun to bring this into our sources. More updates will follow as work progresses, but for now please be patient as we work through all the source updates and testing.
[Samsung Galaxy Nexus] kmcrane:
Will you let us know when the KitKat version is ready for download?

There is always a new nightly, but I rarely see anything changed. (i know most of the changes are behind the scenes.)
[Samsung Galaxy Nexus] EvilDobe:
You know I will, maaaaaaaaaaaaan. I gotchu, boo.
[Samsung Galaxy Nexus] shauder:
Hope the merge is going well =D. I really enjoy the 4.3 version of this.
[Samsung Galaxy Nexus] kmcrane:
Been a month with no builds... Not even test builds.. :'(
[Samsung Galaxy Nexus] metalspring:
Btw, I did my own build of codefirex awhile ago and the reason they probably haven't released anything yet is it's basically the same as AOSP with tons of optimizations (only a couple custom features have been added yet)
[Samsung Galaxy Nexus] kmcrane:
I would like to try a basic feature free version of CFX 4.4.2... As a little teaser before the big release.. I'm having some withdrawals @ EvilDobe.
[Samsung Galaxy Nexus] Rangizingo:
Testing

I will be flashing and reporting back on this later today. I'm coming from Liquid Smooth 4.2 which has been all but perfect, so I am excited to try this. Thanks for your work and dedication!
[Samsung Galaxy Nexus] bigrushdog:
Guys how is the data handoff going from lte to 3g? We've had kinda major issues on sprint toroplus. I'm curious if the vzw radio plays nice with 4.3
[Samsung Galaxy Nexus] EvilDobe:
IMHO Voice+ is one of those things that is "Cool, yay - you did it" but shouldn't be a deal breaker for using any rom. Voice+ doesn't additional functionality (MMS) to Google Voice, the Emoji doesn't work, and the ONLY benefit is the use the use of the stock messaging app.. which sucks anyways. Personally I use Voice Plus which I find to be far more useful than the CM Voice+.

I look at it this way... if I want a CM feature, I use a CM rom. If I want a PA feature, I use a PA rom. Using the roms that blend features together just to cram as many features into a phone as possible is, imo, asking for problems. Not knocking any other roms (Lord knows I slut around these threads) but when it comes down to it I'd rather have a few solid features that I know I'll use vs everything & the kitchen sink jammed in.
[Samsung Galaxy Nexus] konjiki7:
This ROM will be perfect once the curse of BT obex has been cured!
[Samsung Galaxy Nexus] sickopsycho:
I have been getting all sorts of funky issues so I had to revert back to FTL ROM. I was getting bluetooth fc, my phone app was not working and I'd have to call people back and i was getting excessively long screen-on times- even a black screen of death once or twice. I only had MINIMAL apps installed- nothing crazy either- all standard apps...
[Samsung Galaxy Nexus] kmcrane:
I haven't tried b.t. since it fc's when I turn it on. I have had a tough time getting deep sleep, but I think it worked itself out. I made a couple calls and the phone acted like it was calling but there was no sound. The other person never heard a thing either. I'm using tiny's new 5.1 kernel and now I'm ok on the deep sleep.
[Samsung Galaxy Nexus] mfdemicco:
I had trouble making calls. I dialed a number and there was no ringing. I connected on another call and neither of us could hear each other.
[Samsung Galaxy Nexus] bigrushdog:
Guys get me some logs of the phone audio wonk. I'm about 99% sure where to look. But I need logs on this one for sure. I've duplicated the obex issue and it is a project wide derp. I already have extensive logs on it so we're good there. Thanks for the positive feedback.
[Samsung Galaxy Nexus] kmcrane:
I don't know how to get a log. :( I'll admit that...
[Samsung Galaxy Nexus] EniGmA1987:
I dont notice any issue. At work I bounce between 0-1 bars of both 3G and 4G data. Idle battery drain seemed to be much worse today on this ROM than others I have been on back on 4.2.2 and then with a CM10.2 ROM I had been trying for a day before this. But I have no way to attribute that to anything about the ROM itself so far as it could have been just a very bad day which does happen from time to time with my phone in that area. Data handoff between the networks didnt seem anything out of the ordinary from what I am used to.

I did have this issue today once though. I didnt think anything of it though as I have had the same problem from time to time on other ROMs, because of my lack of good service at work. I didnt think it was a ROM problem since I always thought it was a network problem. I hung up and made the call again and it worked fine
[Samsung Galaxy Nexus] bigrushdog:
Please try this. Mobile networks set it to cdma evdo only. Then reboot. See if data starts on boot
[Samsung Galaxy Nexus] EniGmA1987:
Yes I do, at home at least. It comes up as full bars of grey signal with no data, then within 1 minute tacks on a 3G next to the signal and then it turns blue a few seconds later. Again this is for Verizon though not the Sprint ToroPlus.

Oh, and this is on the 2013-08-18 nightly. I havent tried the latest nightly
[Samsung Galaxy Nexus] EvilDobe:
If you're near a computer & plugged in you can use adb to get a logcat. The hard part is being in the right place at the right time.

adb logcat > C:\path\you\can\find\error.txt

The log will appear to be doing nothing. When when you hang up the call push CTRL+C and then go look at that error.txt file. Should be filled with goodness. Post that up here.
[Samsung Galaxy Nexus] zandroid:
Can users provide logcats from apps, like alogcat? It maybe easier than using adb for some.

https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en
[Samsung Galaxy Nexus] EvilDobe:
Of course. A log is a log. :)
[Samsung Galaxy Nexus] mfdemicco:
I'd like to help, but already flashed back to my previous rom. I like this rom though, but will wait for a stable version.
[Samsung Galaxy Nexus] tjarvis:
"what rolls down stairs, alone or in pairs,

rolls over your neighbors dog, it fits on your back, its great for a snack, LOG LOG LOG!

its log, its log, its big its heavy its wood! its log, its log, its better than bad, its good!

everyone wants a log, your gonna love it log, come and get your log! everyone needs a log!

LOG LOG LOG!"

Sorry, couldn't help it... Anyway, great rom! I haven't had any problems yet and glad to see the new team kicking out some great stuff. I'll keep you posted though.

Sent from the GNex
[Samsung Galaxy Nexus] gorillabiscuit:
Gonna give this a shot... Thanks dobe ...

The latest nightly seems to have superuser, which negates the flashing of SuperSU... reflashing now as I screwed something up.
[Samsung Galaxy Nexus] jlsesler:
Have the phone and BT issues been worked out?
[Samsung Galaxy Nexus] EvilDobe:
Sorry for the ambiguous answer but they may be. Some changes were made, blobs were updated, blood was spilled... BUT they may not have been made in time for today's nightly. I don't use BT at all anymore ('er at least not very often) so the fact it keeps crashing isn't a huge deal to me. If it is I'd say wait until tomorrow - if not - give it a shot today. Nandroid & try it out. If there are some deal breakers in there - restore. If not - hang out and see what's up.
[Samsung Galaxy Nexus] bigrushdog:
Ya. OBEX is fixed. It was a stupid derp actually but **it happens lol. Brought in a few updated blobs from 4.3 Google driver page. Fixed derped fingerprint. The obex fix likely didn't make the nightly but will tonight for sure. I wanna push a few more things too. Keepin it rollin
[Samsung Galaxy Nexus] konjiki7:
Would be willing to look into why Gt Racing crashes on this ROM?

I'm not on codefire at the moment so I'm log-less...
[Samsung Galaxy Nexus] bigrushdog:
Well, buy me the game or dump a log and I can do something :D
[Samsung Galaxy Nexus] konjiki7:
I would buy it for you but its free.
[Samsung Galaxy Nexus] rajputrajat:
Hi Dev,

I think thread for maguro is not up yet..

I'm testing first test build for maguro and most of the android resources seem displaying on wrong dpi..

Very happy to see you guys started building maguro too :)
[Samsung Galaxy Nexus] bigrushdog:
Crap. No DPI is fine. That derp is a long story but will be fixed in tonight's nightly. I didnt know we started building maguro. I'll double check the device tree and make sure it's cool.
[Samsung Galaxy Nexus] EvilDobe:
Link me to the game that is crashing & I'll see what I can find.
[Samsung Galaxy Nexus] sruel3216:
Can someone tell me if these features are in the rom:

-Nav bar

-custom quicksettings

-hold volume to skip tracks

-theme chooser

thats all i need. thank you
[Samsung Galaxy Nexus] EvilDobe:
-Nav bar

Yes it has a nav bar. :D If you're looking to modify that nav bar, not yet. It's coming.

-custom quicksettings

Yes. Custom quick settings including the CM camera tile & an LTE tile

-hold volume to skip tracks

Not yet. It is coming. Can't say when but it is on the docet of things to do.

-theme chooser

Yes. Theme chooser is available & working.
[Samsung Galaxy Nexus] sruel3216:
sweet. i flashed the newest nightly and dpi seems all messed up. for example reboot menu, the words were all off and night aligned
[Samsung Galaxy Nexus] EvilDobe:
yeah sorry about that. HUGE project-wide derp. Flash the 22nd & you should be golden. Only current issues I'm aware of BT Obex being wonky. Most everything should be fixed tonight if you want to wait.
[Samsung Galaxy Nexus] sruel3216:
Oh ok. i saw the derp but thought it had been fixed. il test out the 22 build. thanks
[Samsung Galaxy Nexus] EvilDobe:
We thought it was fixed too.. :(
[Samsung Galaxy Nexus] sruel3216:
where is theme chooser? i cant find it lol

edit: nvm found it. never seen it in the app drawer like this before lol
[Samsung Galaxy Nexus] modernbummer:
It's a separate app. Should be in the app drawer.
[Samsung Galaxy Nexus] kmcrane:
Bt share problem still happening on the 24th nightly. Otherwise all looks good.
[Samsung Galaxy Nexus] TuxDroid:
I decided to give this a try but the keyboard fc'ed to the point that I never actually saw it display. Anyone else have that problem?
[Samsung Galaxy Nexus] kmcrane:
I haven't.. I set up and downloaded SwiftKey and never looked back.
[Samsung Galaxy Nexus] TuxDroid:
Long term I too would use SwiftKey but was just experimenting. If a completely unmolested copy that doesn't even have GApps installed doesn't play nice then I am chicken to try it as a daily driver. I am going to be watching for updates though so I can try again.
[Samsung Galaxy Nexus] shauder:
I also get this. The keyboard works fine though. Bluetooth FC on first boot.
[Samsung Galaxy Nexus] EvilDobe:
You guys can try flashing the PA gapps if you want. Shouldn't have any adverse affects other than providing a ton more apps.

So how is it going for everyone? Everything except BlueTooth working?
[Samsung Galaxy Nexus] shauder:
I do like it a lot so far. Just going to maybe cherry pick a few things from Paradigm =D
[Samsung Galaxy Nexus] TuxDroid:
Posted this a little earlier (only reposting b/c you specifically asked)...
[Samsung Galaxy Nexus] kmcrane:
New build is up! Bt share still not working with dirty flash on last 2 nightlys...

---------- Post added at 11:55 PM ---------- Previous post was at 11:32 PM ----------

When I click on "themes" in the app drawer, the display of the stock theme is very distorted. Not a big deal, just trying to find odd things that can be corrected.
[Samsung Galaxy Nexus] EvilDobe:
[MENTION=3795758]TuxDroid[/MENTION] what gapps are you flashing? You're the first to report, I think, keyboard issues. I've flashed using the gapps in the OP many-a-time and flashed using the latest (and 2nd latest) PA gapps and haven't had a single issue. Just wondering what you're doing or using that may be different from everyone else. From what I think I'm reading you're not using a gapps package that has a keyboard.

My suggestion is either to use the gapps in the OP or the PA gapps. Both have worked flawlessly for me.
[Samsung Galaxy Nexus] TuxDroid:
For the test I actually wasn't using a GApps package. I have never seen a ROM that did not have a keyboard in it so I never considered that being the issue... was my assumption the problem?
[Samsung Galaxy Nexus] EvilDobe:
Hmmm.. Your issue is quite the conundrum since there are 3 keyboards included. Any chance of providing a log for your error?
[Samsung Galaxy Nexus] TuxDroid:
Sure thing. I'll reflash and grab one in the next few hours.
[Samsung Galaxy Nexus] TuxDroid:
[MENTION=633993]EvilDobe[/MENTION] - A logcat is attached. I got this by doing a full wipe, installing the nightly from the 25th, letting it start up, and opening the browser. I stopped the logcat right after the error occurred so the good stuff is most likely at the end.
[Samsung Galaxy Nexus] EvilDobe:
Thanks [MENTION=3795758]TuxDroid[/MENTION]. Should be fixed tonight. Sorry about that.
[Samsung Galaxy Nexus] konjiki7:
Finally got around to sending this.

http://www.google.com/url?q=https:/...oQFjAA&usg=AFQjCNEpYRwIGOMq2nswHpPzFiPWXMZhPA
[Samsung Galaxy Nexus] EvilDobe:
Thank, mate. With the images being fixed in last nightly your game may work properly. I'll see what I can find, if anything, now.

[MENTION=3795758]TuxDroid[/MENTION] keyboard issue is fixed.

[MENTION=2934813]kmcrane[/MENTION] the images issue should be fixed.

BlueTooth is in the works. The brains are on it.
[Samsung Galaxy Nexus] EvilDobe:
Good news boys & girls. Bluetooth has been fixed. Images are now proper. Wifi works. 4G works. Everything should work!

Go get it.... 8/27/2013 nightly
[Samsung Galaxy Nexus] bigrushdog:
I'm not sure if bluetooth made that nightly. Either way it will be in the next nightly for sure. Bluetooth was a royal ***** but we got there!
[Samsung Galaxy Nexus] EvilDobe:
It had to have had made it. Using it now. Power on. No errors. My Icon has connected.
[Samsung Galaxy Nexus] bigrushdog:
Well, sounds like winsauce to me. ****, you guys don't know man! Bluetooth was killing me! I was deep in the pits of fail. Then, out of nowhere, I saw the fail for what it was. I reached for my sheath and drew the Sword of Win. I then decapitated the Fail Dragon and transferred pRoNz over OBEX.
[Samsung Galaxy Nexus] kmcrane:
I am on the latest nightly. Full wipe.. I mean format then wipe then install for otg-usb. The reason I wiped so much was I have been havibg a deep sleep problem. I have tried the built in kernel and Tiny's 5.1. I believe its a gps lock issue. I started my phone from a shut down and let it sit for 2 hours 20 minutes and Android OS has used 34% of my battery (now at 85%) if i click it is says cpu total 46s and kept awake 2h 1m 8s. I woul like to beat this. Now that BT is fixed, the deep sleep is my only problem.

Any help or advise is welcome. I have used Tiny's kernel with about 20 roms and I am sure his kernel is not the issue. I'm sure it is a setting, set up, or program that i have due to no one else complaining about it on here.

Kevin

I want to add I was on the first nightly and have had deep sleep issues since day 1. I did the big wipe to eliminate that first step.

Edit #2 it's been an hour since I first posted. I turned on gps and let it set for 20 min. When I checked it It said 8 mins of deep sleep. I turned off gps and now deep sleep seems to be working as normal.

Now the Question.... Do I need gps to be turned on after a reboot? I usually turn gps off in the first 10 mins after installing a rom and turn it on if I need navigation (once or twice a month)
[Samsung Galaxy Nexus] EvilDobe:
Check your apps. I'm getting a nice deep sleep.
[Samsung Galaxy Nexus] Saythis:
Yeah I'm running into this issue too with deep sleep. It'll sit with "gps-lock" until I turn on gps and let it sit for awhile or open Google Maps. I've tried using the stock Kernel, ASKP, TinyKernel, Fancy Kernel on clean ROMs and it doesn't seem to change. I've used Greenify to hibernate my apps but it doesn't seem to do anything lol.
[Samsung Galaxy Nexus] kmcrane:
I know.. I did better battery stats, greenify, and gsam. But it's definitely a GPS lock issue. The only thing I have is after boot, turn gps on for 30 mins or so... Then turn off gps.