yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] EvilDobe:
​

Introducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either.

We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!

Warning: we only support anykernel methods of custom kernel installation.

Here's a bit of info you may want on this project for how we do things differently:

CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.

No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.

A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.

A team constantly exploring totally new feature sets and optimizations geared toward you, the user

We utilize a plethora of optimizations in a build system unlike any other:

Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.

Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.

Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to Google this one a bit to get an idea of the performance gain.

Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.

Optimizations are toggled on and off based on device for the best experience we can achieve for your device without sacrificing any stability

Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.

Fully built utilizing strict aliasing and isognu++11 mode.

Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.

Important Links:

Download Nightlies (Please note multiple pages available) - We have a very in depth review system, so these should be considered stable.

Download Weeklies - These are built once a week on Monday.

Download Official 4.3 Gapps OR Core GApps (mirror 1) (mirror 2) OR Modded PA Gapps OR PA 4.4 Gapps || BaNkS 4.4 Gapps

(use at your own risk)

Download SuperSU installer

Kernel Source

Interactive and Rolling Changelog

Bug Tracker

Instructions:

In the same recovery session, flash the following:

Flash rom

Flash Superuser zip

Flash GApps

Reboot

This rom is powerd by Lean Kernel so we would like to thank imoseyon for his great kernel that continues to power some of the best roms for the nexus.

​

Thank you for choosing codefireXperiment,

codefireXperiment team

- See more at: http://codefirex.com/index.php?p=/d...y-codefirexperiment-nightlies-weeklies#latest

​
[Samsung Galaxy Nexus] EvilDobe:
In order to fix your issues we need a log of your error.

Just telling us "it's broken" doesn't help anyone fix it. This would be the same as going to the doctor and telling him "I don't feel good. Fix me." and providing no other information.

There are numerous ways to get a log of errors.

Install CatLog from the Play Store.

Open the app & set the "Log Level" to error.

Do whatever causes your error.

Save the error text file & post it here or on one of those logging site (ie pastebin.com).

You can use ADB to capture the errors as well.

Plug your phone into a computer & open a terminal/command prompt.

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

Do whatever causes your error.

CTRL+C

Save the error text file & post it here or on one of those logging site (ie pastebin.com)

Kernel Information (as of 9/5/2013)

Supported kernels:

lean (included)

Mpokang_kernel-v10_1080p

Trinity TNP11b-4.3-1420-384

ASKP

Golden

Unsupported kernels:

franco

Fancy

FuguMod

Mpokang_kernel-v10_SuperRAM-fix

Optional Installs

Xposed Framework (by Rovo89): Original Thread

Xposed Installer

Collection of Xposed Modules
[Samsung Galaxy Nexus] modernbummer:
Downloading now!
[Samsung Galaxy Nexus] bigdro21:
Will give this a try
[Samsung Galaxy Nexus] modernbummer:
Wow. This ROM is incredibly snappy. Thank you.
[Samsung Galaxy Nexus] t1.8matt:
What does it mean when you say you only support anykernel methods of installation?
[Samsung Galaxy Nexus] laureanop:
Meaning they only support kernels that don't change the Rom s ramdisk, like Tiny's or Lean. When you install Franco kernel or Fancy they come with their own ramdisk, so if you have any issues with the Rom they will not answer your questions.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] t1.8matt:
I see. So does anyone know if ASKP kernel falls under that category of being unsupported? I'm gonna check Amps thread later but wondering if anyone knows off the top of their head.
[Samsung Galaxy Nexus] EvilDobe:
Nandroid. Try it. Report back.
[Samsung Galaxy Nexus] t1.8matt:
Sounds good. I'll give it a go after work.
[Samsung Galaxy Nexus] alpenglow:
Voice+ stopped

fresh install.:confused:
[Samsung Galaxy Nexus] 47th_Ronin:
Dl is on now!

Thanks for the flash fix guys!
[Samsung Galaxy Nexus] Phazmos:
so ..... is this stock android?
[Samsung Galaxy Nexus] Phazmos:
is there a list of options available? this sounds interesting, but need more info. Thanx!
[Samsung Galaxy Nexus] justen7723:
Backup, try it.

Couldn't find a features list, I tried.

Can't send u a PM????

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Phazmos:
same here. I don't like to load anything I don't know about, but am curious, always curious about new goodies!

pm was disabled, never had a needed for it, but should be working now.
[Samsung Galaxy Nexus] jeremytn86:
Very snappy rom. Not tons of features, but I think I found my new favorite ROM. Very fast and stable.
[Samsung Galaxy Nexus] Alton (Halo 2):
Omg this is the fastest 4.3 ROM . I'm sticking with this for awhile , thanks
[Samsung Galaxy Nexus] EvilDobe:
For giggles... can you try using the modded PA Gapps in the OP? I normally use those for everything I flash & my photos are syncing as well as no keyboard issues.

For everyone else.. how has radio, hand-offs, and data connection been? So far so good? Long time to get data back? Feedback, good & bad, on all aspects is appreciated.
[Samsung Galaxy Nexus] Saythis:
Flashed the 9/16 build last night and so far data handoffs and overall data connections have been better than previous builds. Data comes back almost instantly and it switches quickly between 3G and 4G without any hesitation for me.
[Samsung Galaxy Nexus] Backwardsblade:
On latest nightly. Locked into 3g its very solid. I'm still seeing drops, usually the drop from 4g to 3g. If I toggle LTE it doesn't take long to establish 4g, though I imagine this is probably different than typical handoffs. Does logcat gather anything relevant to connectivity or are these issues something deeper? I'm sure I reproduce drops if it'll help identify issues.
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
The link in OP for nightlies is broke. I've been using the weeklies and having to go back. There are no weeklies right?

And I know this isn't the Nexus 7 (2013) thread but I see a folder for it, flo, but nothing in it. I'm assuming soon maybe?

Its good to see Team EOS influence in the ROM. Is there going to be a tablet ui?

Edit: I just checked the folder for flo and there's a zip in there! I was going to ask if its god but I'm just gonna flash it!
[Samsung Galaxy Nexus] bigrushdog:
Flo should fire off tonight. I asked maintainers to double check download links. Good news is reports are flo is rock solid and maintained by [MENTION=1184203]Roach2010[/MENTION] and he is just a sick wicked dev :D
[Samsung Galaxy Nexus] EvilDobe:
Sorry about that. Trying to be helpful & broke the link but I fixed it.

All the various UIs are coming thanks to [MENTION=470268]bigrushdog[/MENTION] because he's just a sick wicked dev.
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
I've had the pleasure of running the EOS ROM since it was team Tiamat and before. BRD has always been a positive influence and puts out a great product. I still can't believe there's no more EOS.

And is why I was wondering if we were going to get a taste of their Nav bar mods, tablet ui specifically, its awesome. The flo ROM is very nice btw, waiting for an XDA thread to pop up.
[Samsung Galaxy Nexus] bigrushdog:
You guys are too kind. As you can see in interface settings, I've laid the backend framework for tablet ui, or any ui really. Tablet ui without DPI hacks, on any device, with any bar size, is most difficult, even for me. The Eos implementation was Ok, but it had some bugs. Next iteration will be stronger and more robust. I've been brainstorming my strategy. It will take a little time. In the meantime I'll bring in some more navbar fun. Long press this, do that. Give buttons and glow some color. Maybe add some buttons. Ya, it's all in the pipeline.
[Samsung Galaxy Nexus] Magnus_CA:
The PA Gapps did the trick. Plus i love the embedded Wallet. No more issues with Picasa photo sync and no voice typing bugs. If I were you I'd consider removing the other full and core Gapps packages. I tried both off clean installs and either they are buggy or just don't play well with your rom.

On another note, I'm having a strange issue when I connect my phone to my pc via usb. I know i have the right drivers installed so i can use the phone like a usb drive but I'm getting a prompt to install drivers for a device called 'INT2' (or something like that) and my pc won't recognize it as a drive. I've got USB debugging enabled. Is there another setting preventing it from being recognized as an mtp device as it was in other Roms?
[Samsung Galaxy Nexus] EvilDobe:
Sounds like a PC issue, tbh. I plug into various computers throughout the day & never had the issue you're describing. No one else has reported it so I'd take a look at your PC and the driver's being (or not) being installd.
[Samsung Galaxy Nexus] EvilDobe:
Codefire Changelog

I also updated the OP with the 9/17 PA Gapps to work with the cfX ROM.
[Samsung Galaxy Nexus] jeremytn86:
The download link only shows 9/12 as the latest, where are the newest ones
[Samsung Galaxy Nexus] EvilDobe:
You can either go to page 2 or you can sort by date & it should bring the newest to the top.

Sept. 22, 2013 build
[Samsung Galaxy Nexus] jeremytn86:
I feel stupid, I didn't even notice that lol. On another note can I dirty flash 12 over 22? Or did you make changes that wouldn't play nice

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

One more thing, this is by far the fastest ROM I've ever used, I can't believe this thread isn't blowing up
[Samsung Galaxy Nexus] EvilDobe:
No worries. Happens to the best of us.

I only clean flash but there shouldn't be any reason you can't dirty flash. Before you reboot just clear the caches & you should be all set.

Yeah...... There aren't a lot of buzz words like "PIE" or "HALO" or whatever kids are looking for these days AND the rom just works so there really isn't much to keep the banter going. Stop by.. say hi any time.
[Samsung Galaxy Nexus] konjiki7:
Thats why I love this rom. I still would love volume key track changes.:)
[Samsung Galaxy Nexus] jeremytn86:
I don't care so much for all that, just BLAZING speed for our aging phones
[Samsung Galaxy Nexus] bigrushdog:
Its not ruled out. In fact if you check review you see some hardware key stuff in there.
[Samsung Galaxy Nexus] konjiki7:
Where can I find this review you speak of? I'm interested in what may be coming down the pike.
[Samsung Galaxy Nexus] bigrushdog:
If it was a snake..... Lol. Check my sig. Phabricator is different than Gerrit so it's a learning curve getting around. But it's most powerful too.
[Samsung Galaxy Nexus] EvilDobe:
https://github.com/codefireXperiment

http://review.codefirex.com/differential/query/all/
[Samsung Galaxy Nexus] jlsesler:
Yahoo sports is force closing on me. I tried fixing permissions and didn't work. Anyone else see this?
[Samsung Galaxy Nexus] M@XLOL:
I have been looking for something like this. Bigrush I'm glad your here. I remember you from ages ago.
[Samsung Galaxy Nexus] bigrushdog:
Haha yes sir. Still in the game. Getting old but not rusty. Any thoughts or issues on the build post up. Welcome!
[Samsung Galaxy Nexus] EvilDobe:
Thanks for reporting. Try to grab a log if you can (instructions in 2nd post) for debugging. Thanks again.
[Samsung Galaxy Nexus] bigrushdog:
Uninstall and cleanly install from market.
[Samsung Galaxy Nexus] jlsesler:
Hmm...I tried that and no luck. I will try a new clean install.
[Samsung Galaxy Nexus] M@XLOL:
would love to see lockscreen targets
[Samsung Galaxy Nexus] clnzx2:
Loving this rom. Only thing missing is different battery icons which is very minor. Thanks.
[Samsung Galaxy Nexus] M@XLOL:
Several options in xposed modules. Take a look. They were all too involved for me but I liked just changing the color to white.
[Samsung Galaxy Nexus] EvilDobe:
Sorry for the unexpected break in nightlies. The build box ran out of space & some of the builds didn't make it. Our beloved Toro nightlies have resumed & live on PAGE TWO of the download site.

Sept 25th, 2013 nightliy.

Interactive changelog
[Samsung Galaxy Nexus] Backwardsblade:
Was 9.25 pulled? I have experienced some quirks with GPS and some non-specific ui hiccups. Data handoff excellent on 9.25 though.
[Samsung Galaxy Nexus] konjiki7:
Yeah gps is much slower.... for me.
[Samsung Galaxy Nexus] EvilDobe:
Yeah.... about that........... It was pulled. Lets just pretend that 9/25 never happened. Take some solace in the fact it's hump day.
[Samsung Galaxy Nexus] konjiki7:
Whats the most current version at this point? Or should i wait for tonights version ?
[Samsung Galaxy Nexus] bigrushdog:
Wait for tonight. You will have a better day. Promise.
[Samsung Galaxy Nexus] EvilDobe:
And if you don't.. you can still blame [MENTION=470268]bigrushdog[/MENTION].
[Samsung Galaxy Nexus] bigrushdog:
It wasn't me. And you're fired. We have an open toro maintainer spot. Accepting applications now.

Hahahahah lol. Now blame me!

Hahahah

Jk. I WUB U
[Samsung Galaxy Nexus] EvilDobe:
This could be us!!!
[Samsung Galaxy Nexus] jeremytn86:
WTF?
[Samsung Galaxy Nexus] nitsua98:
lol
[Samsung Galaxy Nexus] konjiki7:
X2!
[Samsung Galaxy Nexus] 47th_Ronin:
I think i threw up in my mouth a little...
[Samsung Galaxy Nexus] EvilDobe:
Chew it up & swallow! Two dinners for the price of one!
[Samsung Galaxy Nexus] Saythis:
Yet another reason I love this ROM and its devs lol
[Samsung Galaxy Nexus] Backwardsblade:
9.26 was definitely worth the wait. Data is stronger, GPS is back to fast locks and feels very stable. Great job!
[Samsung Galaxy Nexus] EvilDobe:
9/22 Changelog

Option to disable low battery warning dialog (bigrushdog)

Updates from upstream, and some minor fixes

9/23 Changelog

Some new optimized functions

Minor updates

9/24 Changelog

Many new optimized routines (strlcat, strncmp, strnlen) that perform far better than the old routines. All "basic" aka naive routines are ~30-40% faster than the old routines across the board.

Hardware key rebinding ported from CM. (jrior001 and bigrushdog)

Temporarily reverted some jpeg changes to fix a few issues

9/25 Changelog

Fixed the link volume option. (bigrushdog)

Synced libm with upstream freebsd

libm: using e_sqrt and e_sqrtf for ARM with hard float instructions

libm: using s_fma and s_fmaf for ARM with hard float instructions

libm: using s_lrint and s_lrintf for ARM with hard float instructions

libm: Integrated ARM specific CodeAuroraForum e_pow ASM and made it more generic for all ARM NEON devices.

libm: fixed a potential issue when fmal may be needed.

Small updates from the AOSP

9/25 Nightlie issue & Changelog

The hard float routines in the previous nightly were very thoroughly tested on two different chips and three architectures, however we did not take into account the lower accuracy of some of qcom's newer chips such as the s600 and s800 when running our tests.

They tested very well for accuracy and the minimal benches on both a cortex-a9 Exynos 4412, and a big.LITTLE Exynos5 Octa Cortex-A15 1.6GHz Quad and Cortex-A7 1.2GHz Quad CPUs.

We've temporarily reverted the changes however, and will be conditionally building them depending on the accuracy of each chip in the supported phones to be on a side of caution.

Some audio types also failed to play from the audio link "fix." This will be fixed one way or another.

Disabled tree vectorization when ARM NEON fpu is in use per the Debian discussion.

:cowboy: Sept 26th, 2013 nightly :angel:
[Samsung Galaxy Nexus] NykoNako:
UPDATE: Flashed 9/26 Nightly in order to rule out an issue with the 9/22 build, the results are the same (eg no cell/data svc when trying to return from Airplane Mode)

Wiped & flashed the 9/22 Nightly and here is my experience:

- Phone does not reconnect to Verizon when trying to return from Airplane Mode (logcat attached)

- Tried to run phone under AOSP mode (switch ON) and the results are the same

- When playing Youtube videos, the audio is sketchy (eg pops, cutouts)

Hopefully this helps as I'll have to move to a different ROM as my daily driver.

`N
[Samsung Galaxy Nexus] mosshorn:
EDIT: I'm dumb. 9/26 seems to be working smooth as silk.
[Samsung Galaxy Nexus] EvilDobe:
Thank you for reporting. I'll look into the airplane mode & YouTube issues. Anyone else sharing this experience?

AOSP mode is a visual feature. It would not impact your data connection in any way.
[Samsung Galaxy Nexus] NykoNako:
I figured as much with the aosp, I brought it up because it makes my bars blue (sometimes), but I never see lte/3g return. I forgot to mention that a reboot gets my service back. Another test was Airplane, reboot, airplane off, service connects normally.

---------- Post added at 01:00 PM ---------- Previous post was at 12:48 PM ----------

I figured as much with the aosp, I brought it up because it makes my bars blue (sometimes), but I never see lte/3g return. I forgot to mention that a reboot gets my service back. Another test was Airplane, reboot, airplane off, service connects normally.
[Samsung Galaxy Nexus] clnzx2:
Latest nightly. Data drops are very frequent and I can't connect to gps at all
[Samsung Galaxy Nexus] ba_hamilton:
I'm not getting that. I get data back after turning airplane mode off but it takes about 15 seconds. I also have to manually turn on wifi again. It doesn't connect automatically.
[Samsung Galaxy Nexus] Saythis:
I'm also getting this as well. I'm also having some handoff issues with the latest build and data isn't returning sometimes even after airplane mode which is requiring a hard reboot to fix.
[Samsung Galaxy Nexus] M@XLOL:
Individuals with data issues clean or dirty flashes?
[Samsung Galaxy Nexus] clnzx2:
Clean
[Samsung Galaxy Nexus] Saythis:
Both
[Samsung Galaxy Nexus] konjiki7:
Tried tinykernel yesterday. So far data drops are not as bad.

Though its much slower then lean kernel and golden... connectivity is better.

Wifi actually moved from a grey state to cyan. Gps is a no go .....
[Samsung Galaxy Nexus] kmcrane:
I couldn't get gps to lock in 30 mins with 9-25... And had deep sleep/battery issues. I'm waiting for that to improve, otherwise it's as good or better than anything else I've tried.
[Samsung Galaxy Nexus] EvilDobe:
9/25 was VERY bad. A lot of issues due to some optimizations that weren't properly tested. Everything after 9/25 (which if I remember correctly was pulled for this reason) should be better. GPS & signal should be more on par as of the most recent nightlies.
[Samsung Galaxy Nexus] kmcrane:
This comment about gps is a no go, is what I was talking about. These forums are pretty quiet. Which usually means the rom is solid and doesn't have many issues. But I had issues with bt and gps with eos. And I am loyal... But I am content on CM wishing gps was as good as that. Maybe I'll jump back and try this, but I'm kinda waiting for some posts that are positive on gps.

The connectivity issues are on every rom, so I don't hold that against this rom.
[Samsung Galaxy Nexus] EvilDobe:
Roach recently got me addicted to Ingress & I've been using my GPS constantly on this rom. The only time I've ever had an issue was 9/25 which really pissed me off cuz I didn't notice right away & I was heading out to farm some gear. I'll give you data issues - as you've said 99% of roms are having the issue. GPS has been rock solid for me outside of 9/25.
[Samsung Galaxy Nexus] kmcrane:
Ok I'll try it. What gapps? Still flash rom, gapps, superSu, then kernel? Also if I want to dirty flash from 10-1 to 10-2 do I flash everything again? (i usually wipe cache and dalvic on dirty flashes)
[Samsung Galaxy Nexus] EvilDobe:
I flash ROM, SuperSU, and then gapps. My logic is that the SuperSU install zip monkeys around with the Google apps & moves them around. That annoys me so I flash the SuperSU zip second whereas people normally suggest it last. In your case I'd do rom, supersu, gapps, kernel. Lemme know how it goes.
[Samsung Galaxy Nexus] kmcrane:
Should I use banks, pa, official, or another gapps?
[Samsung Galaxy Nexus] EvilDobe:
I've been using the PA I post in the OP. The gapps you use shouldn't impact gps or radio functionality.
[Samsung Galaxy Nexus] kmcrane:
Ok. I'll try it again tonight. Thanks!
[Samsung Galaxy Nexus] EvilDobe:
Sounds good. Lemme know how it works out for you. I'm very curious.
[Samsung Galaxy Nexus] konjiki7:
Just updated team win recovery(v2.6.3) will try to reflash soon....
[Samsung Galaxy Nexus] M@XLOL:
With clarification of data drops no longer being present ill update tonight. Thanks dobe
[Samsung Galaxy Nexus] EvilDobe:
Oh the data drops happen. Happens on every 4.3 I've run. It's an Android 4.3 issue across the board.
[Samsung Galaxy Nexus] M@XLOL:
I haven't noticed. We must have great signal here. New nightly is up and running just fine. Tweaked just a bit with xposed. Thank you.
[Samsung Galaxy Nexus] EvilDobe:
I live in a great 4G area, travel through a bunch of awful dead-zones daily, and it's noticeable when my data drops. It drops then doesn't come back or takes a very long time for it to come back. Everything else works flawlessly. This isn't isolated to this rom either. It happens on Purity, PA, Slim, etc..
[Samsung Galaxy Nexus] kmcrane:
Oct 2 having mass bt share issues.
[Samsung Galaxy Nexus] EvilDobe:
Log please, good sir.

Edit: Also - what are you doing to get the error? I just turned on BT, went to

more

under "Wireless & Networks", then "Tethering & portable hotspot" and checked the box for "Bluetooth tethering" and was able to connect my laptop to the phone. Just wanted to make sure that we're doing & talking about the same thing.
[Samsung Galaxy Nexus] kmcrane:
I fresh installed 10-2 and it booted to set up screen and the error was popping up. Had to press "ok" over a hundred times trying to go threw set up.. I gave up. Reflashed clean install again, and it was the same. I downloaded 10-1 and it installed fine. I'm running it now. I'll test gps in an hour or so. I will run the same test I ran with cm yesterday.
[Samsung Galaxy Nexus] metalspring:
Also on Oct 2nd build, and Bluetooth share constantly force closes right from first boot until you freeze or remove the Bluetooth apk

I'll see if I can get a log later if you still need it
[Samsung Galaxy Nexus] EvilDobe:
Thank you fine towns-folk for reporting & confirming. This has been reported & confirmed across multiple devices as well. Downsides to nightlies I guess.

Good news is that BRD has some soft key features in the works, the CRT functions are coming back (hopefully soon), and some other general improvements over-all.
[Samsung Galaxy Nexus] kmcrane:
As for gps I ran the test. It took 10 mins to lock.. I was disappointed, but I had ran the cm gps for a while and with a different kernel. So I swapped kernels.. Waited an hour and ran the test again and it locked in less than 30 secs. Not as fast as cm, but it was acceptable. I will try again tomorrow morning, that way it's honestly the exact same as the cm test.

Running 10-1 because of the issues on 10-2.