yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bigrushdog:
Just a heads up. We've had Bluetooth fail on Manta and Grouper. So double check and see if it spread over here too. I'm testing a fix right now, but it looks like Linaro is over optimizing one of the bluetooth libs. So we can fine tune the build and exclude this resource from full optimization. Should do the trick.

Edit: From the user side, us building LK inline will have no effect on your normal kernel dealings. One thing i noticed is I gotta tweak the config to give us 230 min. But compiling LK inline with a nice juicy 4.7.3 Linaro toolchain is such a pleasant and more complete building experience.
[Samsung Galaxy Nexus] info[]box1:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Great job BRD.. I will run the Lean kernel and enjoy the hard work, good choice of kernel and take your personal pro opinion.. Normally I would faux123 my device. I don't Bluetooth anything lately so can't report regarding that.

Thanks for bringing more Linaro optimizing to the toroplus. Please shred more light on Linaro transaction sounds compelling.
[Samsung Galaxy Nexus] mattallica76:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Bluetooth is working fine for phone calls so far. I'll check audio streaming later when I'm near my BT speaker.
[Samsung Galaxy Nexus] MizzouBrent:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I still haven't gotten this to boot. Would using team baked inverted gapps be the cause? I have checked md5 and everything so I'm very confused. And yes I'm doing a clean wipe of data caches and system.
[Samsung Galaxy Nexus] EvilDobe:
Where does the boot fail? Do you see the Google logo then nothing? Does the eos logo spin then nothing? Did you try flashing the regular gapps for 4.2.2? What have you done to troubleshoot the issue so we don't repeat anything you've done?
[Samsung Galaxy Nexus] info[]box1:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Since this ROM is Linaro build base I would use Xylon's inverted gapps. See what happens.

-@lmighty Galaxy Nexus Lte/Ltd™ [RAW-CM10.1/ faux123 kernel 026u] using xda premium
[Samsung Galaxy Nexus] MizzouBrent:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Hangs at the Google screen. Have never even seen the boot logo. Lol. I tried just flashing the Rom and gapps that are the stock gapps but my battery was basically dead at that point so I gave up.

I'll give that a try. I didn't even know that Xylon had inverted apps. I'll try that later tonight and report back.
[Samsung Galaxy Nexus] MizzouBrent:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Finally got this thing flashed and everything runs great. Maybe my phone just didn't like it paired with Franco? It was either that or multiple bad downloads.
[Samsung Galaxy Nexus] Blokgang:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I see an update in goo for today.. Nothing mentioned in the thread?
[Samsung Galaxy Nexus] Blokgang:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Is this thing on
[Samsung Galaxy Nexus] ajf64:
yes i so need my 230 back

also when will we see a nice custom skin from uber id really love to see that uber jelly is getting a little stale to me and the others seem the same with just diffrent coloring love to see somthing totaly new
[Samsung Galaxy Nexus] Crwolv:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Runs great with franco
[Samsung Galaxy Nexus] mrkniceguy:
I'm running the nightly now. My first time with EOS. My CM10.1 was just getting slower and slower and had major GPS issues. Really liking this so far. There are a couple of features I miss but have good workarounds. However, I can't seem to figure out how to take a screenshot. Any help there?

Edit: figured out the screen shot thing. :)
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Power and volume down simultaneously.
[Samsung Galaxy Nexus] sirxdroid:
I refer back to this when I forget the magic key combo: http://www.makeuseof.com/tag/6-ways-to-take-screenshots-on-android/
[Samsung Galaxy Nexus] ajf64:
Btw bigrushdog are u building the kernel from the exp tree or the stable tree?

BTW LK -6.2.1 is out im still waiting on proper change log i should have it soon i do have the exp dump if u need it
[Samsung Galaxy Nexus] bigrushdog:
I'll double check on that. Oh goodie I'll have to merge. I've been slightly neglectful of tuna since I fried my battery. But got a new one coming in a couple days.

Uber did a nice job on the Imoseyon graphic. :good:

Edit: I'll fire off a build whenever github gets pushed to.
[Samsung Galaxy Nexus] ajf64:
thanks man look foreword to it
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Hey Bigdog, curiosity got the best of me, thought I'd ask you a few questions if you wouldn't care to humor me. I've read your previous posts but I'd like to know a bit more.

1) Is there any upside to using the inline kernel for the end user in terms of stability and such? I'm unsure what 'inline' actually means other than being compiled with the ROM.

2) Is there any downside when an end user uses a different kernel? Was going to update to LK 6.2.1 but wasn't sure if I should just wait for you all to do it.

3) Most other kernels will not install, results in a boot loop both when doing a perfectly clean ROM/kernel install as well as just a cache/dalv wipe. Any idea why this is?

Thanks for reading. I'm a big fan of your work and seriously look forward to the future of EOS.

Toroplus | EOS4 | LeanKernel 611 | 260DPI
[Samsung Galaxy Nexus] ajf64:
well lk 6.2.1 will work since it is compiled useing the latest linaro tool chain i belive the other roms that are out for the nexus are not compiled with linaro there for they will not work with eos since it is a full linaro build

inline compiling helps in the way that every thing is done the same way instead of say rush god useing on verison of the tool chain and lk using a different one or no linaro at all when that happens u can get performance problems or as u see in some cases boot loops or just failure to boot so doing every thing in a unified fashion helps keep things that much more stable
[Samsung Galaxy Nexus] bigrushdog:
1) inline simply means that the kernel is compiled from source when the build is compiled. As far as end user experience, not really. It's more for "aesthetics" or "purity".

2) the build is not dependent on the kernel. So your experience would depend on the quality of the kernel. I run with LK because it's a sick kernel and Imoseyon is very talented. There are other fine kernels out there. This is just my favorite flavor.

3) ya kernel devs are distributing with boot images again. It's complex but ask your kernel dev to please use AnyKernel as an install tool. If you have a kernel you want to use, lemme know. I'll whip something up as a one time favor. Or if you use linux, i can shoot you my boot image scripts.
[Samsung Galaxy Nexus] bigrushdog:
Fresh builds cooking. I moved CDMATools source back into the project. That fixes the msl feature from not showing. Merry Christmas kang bangs! LK 6.2 but no 230 yet. Misc under the hood stuff. More win to come.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Thanks for taking the time to reply and for the offer! But that won't be necessary, Lean and my Gnex get along swimmingly together so I have no problem using it. I just wish he would include Fiops, that's my **** :P But I'll wait till you can find imoseyons 230 config and implement it to EOS as that's the only thing I'm missing. Thanks again for all your work!
[Samsung Galaxy Nexus] bigrushdog:
Is fiops a scheduler or a governer? Make your case in his thread. He seems like a reasonable guy.
[Samsung Galaxy Nexus] EvilDobe:
Hey BRD - nice new avatar in the "About". It really is more fitting.
[Samsung Galaxy Nexus] frenchy714:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Fiops is an I/O scheduler.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Fresh install of build 89. Everything is great, even feels a bit faster than the previous nightly but this is likely due to the updated LeanKernel. One tiny bug I have noticed though and thought I'd share...

Say you want to change the color of the clock (or anything else for that matter), the default RGB number is always set to FFFFFF, even though the clock is default holo blue. In order to make something white, you have to use the nearest value that is not FFFFFF, so you would use FFFFFE. Not a big thing, just an annoyance till you realize what's happening.
[Samsung Galaxy Nexus] ajf64:
slacking a little brd :) havent updated change log since 3/05/ lol
[Samsung Galaxy Nexus] dna_d:
So every day, at about 302p, my screen turns on for no apparent reason. Am I the only one, or is this common?
[Samsung Galaxy Nexus] frenchy714:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Haunted phone?? J/K. That's odd though. Have you tried wiping caches then rebooting? Or starting fresh with a clean install?? If not, give those suggestions a try, and monitor your phone around that time to see if the problem still persists.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] sirxdroid:
Easter egg :)
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Well woulja look at that... EOS and LeanKernel just broke my screen on record :)

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] blankit:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Does this ROM have the pie feature?
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Nope.

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] blankit:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Guess I'll stick to carbon then
[Samsung Galaxy Nexus] EvilDobe:
Mind sharing your settings?

I don't understand the fascination with pie. I don't understand passing up a rom because it doesn't have pie. Are you really gaining that much more of a user experience because you've gained back such a small portion of your screen? Is e-mail becoming much more clear because you don't see three soft keys? Home life getting better because you have pie? To each their own I guess but personally I'd rather have a slim, glass, navbar with the gestures than pie. I would never pass up a rom because it didn't have the gimmick I was looking for. It can never hurt to experiment and try a new rom - you might find something new & unexpected that will make you switch.
[Samsung Galaxy Nexus] CRIME INC.:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Lmao, my wife left me, my dog got ran over, and my house was foreclosed on all because of this ROM having no pie. Lol
[Samsung Galaxy Nexus] sirxdroid:
I've seen LMT mentioned as an installable app for ROMs that don't have Pie built in. Not my cup of tea, so I'm not sure if they are functionally the same or even close.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I'm right there with ya man. I've tested out pie quite a bit of multiple occasions and find it very clumsy even after spending a few days with it. Innovative, yes; practical, thats debatable. Frankly, I hope this ROM never gets pie, I don't like seeing code-heavy cherry picks put into ROMs, which is something the EOS team has made sure to avoid and is one of the reasons its so fast and stable. Now, the WebOS style navbar feature EOS has made, THATS where its at! I love it. If you wanna get screen real estate back, just edit your DPI in build.prop and go on your way. You'll find that its a much more effective solution to getting the space you need than using PIE. Anyway, </end rant>

Kernel Settings you requested with LeanKernel:

Gov: Interactive

IO: sio

TCP: Westwood

Max: 920000

Min: 350000

Screen Off: 350000

Hispeed_freq: 700000

GPU OC: 384

ZRam: Off

Force GPU rendering

Viola, 5 hours screen on time with a few calls, lots of WiFi use, some music streaming, etc.

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] sirxdroid:
Would this be a problem for VOIP calls with the screen off? I guess only one way to find out, but maybe someone already messed with it.

And I see LK has two new builds with 180 and 230 min. Interesting there isn't just one build that offers both options.
[Samsung Galaxy Nexus] ajf64:
i got well over 8 hours screen on time with 230 undervolt and extended battery
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

What extended battery? If its bigger than 2100 then I'm inclined to believe you. If not, then I have never ever seen anywhere near 8 hour screen on time not only on my device but anyone else's Gnex either. And I do a 'lot' of lurking in kernel threads :)

Also, is that with constant data, GPS, NFC, sync all on? Because I never turn any features off. Do you use profiles? What are you doing that im not?!? Haha!

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] sirxdroid:
His sig lists: Accessory: 4000MAh Battery

---------- Post added at 11:11 AM ---------- Previous post was at 11:07 AM ----------

Is there any way to get Bluetooth audio streaming to send the track info? Is this a b/t driver issue, ROM issue, music player issue?
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Ahh that explains it, can't see his sig on mobile. Did you check to see if VoIP worked on 350000? I don't use it but is be interested in your findings. And sorry but can't help ya with the Bluetooth audio, I never use it.

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] sirxdroid:
Don't know about VOIP and 350. The only way I found VOIP to work reliably is with the screen on, but I'm not sure whether it's because of the CPU or because of wifi performance. More experimentation is required, but it's kinda sad to waste battery to keep the screen on while the phone is at your ear.

The GNex seems to be somewhat better with VOIP, but HTC One X+ is atrocious in their stock implementation, no matter what you do VOIP doesn't work well with the screen off, just a broken implementation, keep wifi always on doesn't help, it seems the setting is just ignored.
[Samsung Galaxy Nexus] blankit:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I'm used to the pie feature....and the bigger screen real estate without actually having to increase screen size is a big plus
[Samsung Galaxy Nexus] dna_d:
I clear the cache every time I flash a nightly (2 or 3 times since this started happening), but I don't really want to go through the hassle of doing a clean install. Thanks for the tips, though!

EDIT: Seems I'm not the only one...

http://code.google.com/p/android/issues/detail?id=39625

I looked through the Wake Lock Detector program, but it has a ton of apps and I am not too sure how to read it.
[Samsung Galaxy Nexus] EvilDobe:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

IMO you can't be all that used to it. It's only been in "existence" for the last ~3-4wks and in a decent functional state for maybe the last two weeks. I mean no disrespect to the pa team because I love the 220dpi tablet mode but I'd much rather have the features & stability of this ROM than that one.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Pie has been around since mid January bruh. And its been stable since 3.0 which was released in early February.

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] MizzouBrent:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Yeah definitely been around for longer than a couple weeks. I like it but obviously not everyone feels that way.
[Samsung Galaxy Nexus] EvilDobe:
lol so my time line is a bit skewed... oops. It still isn't a very long time in the grande scheme of things. Regardless passing up a ROM because it doesn't have a particular gimmick is silly to me. Like passing up a woman that doesn't have DD cans when everything else is top-notch stellar.
[Samsung Galaxy Nexus] sirxdroid:
Different men, different priorities, when it comes to women and ROMs.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I agree with ya on both ROMs and women, just pointing that out.

Toroplus | EOS4 | LeanKernel | 260DPI
[Samsung Galaxy Nexus] mattallica76:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

New nightly is up.
[Samsung Galaxy Nexus] sirxdroid:
So if I dirty flash an EOS update, I still need to flash gapps too, right?
[Samsung Galaxy Nexus] EvilDobe:
Is glass for the navbar working for anyone? Status bar works fine but no matter where I put the slider the navbar doesn't change.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Yes.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I'm sorry if this has been answered. I'm on the latest nightly and am trying to set the nav bar to completely transparent. I can make the status bar 100% transparent but not the nav bar. It's probably something simple but I'm not seeing it.
[Samsung Galaxy Nexus] EvilDobe:
So you ARE having an issue with the navbar glass settings....? I can set mine to 0 or 255 and nothing will happen. I can set it to zero & reboot - nothing. Set it to 255 & reboot - nothing.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Yes I am also having a problem with changing the nav bar transparency settings.

I can change the status bar but not the Nav bar.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

What do you mean? Your navbar is 100% transparent. The launcher you are using just has a shadow effect at the bottom. Am i missing aomething? You need to change that setting, or use a different launcher that has that option. My navbar goes 100% transparent no problem.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

I'm not using a launcher. So I guess you mean the shadow us normal for no launcher.
[Samsung Galaxy Nexus] sirxdroid:
I love this ROM. No deep sleep issues, no bloat, no high-school looking themes with dragons, snakes and unicorns :) Just the right tweaks, smooth, fast and stable, very good on battery.

I settled on EOS for both my GNex and now my new Nexus 4.

Wonderful work Team EOS!
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

You can't not be using a launcher... Do you just mean that you are using the stock launcher? If so, yes, it has a shadow that you can't turn off. Use nova, apex, etc.
[Samsung Galaxy Nexus] EvilDobe:
I'm using the latest Apex. When I apply the setting nothing happens. Same Apex that I was using yesterday when it worked.

Reflashed, clean, again. Using the launcher that comes with the rom nothing happens.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Could be an apex issue then I suppose. I use nova and transparency works just fine.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

With all due respect, that seems silly since most people use the stock launcher. It should be called "glass-unless-you-use-a-stock-launcher". But thanks a million for the answer.
[Samsung Galaxy Nexus] EvilDobe:
I now have Nova, Apex, and stock installed. None of them let the navbar be transparent. I'd like to add that I'm on toro but I doubt that matters.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Then perhaps I'm misunderstanding your alls issue. In the picture the other guy posted, his nav bar is in fact transparent. I assumed he was talking about the obvious dark spot above his navbar that looks off. That's a launcher thing.

If you can't make the nav bar anything but black, that is in fact a different problem. When you updated to this nightly, did you clear cache and dalvik? I would try that. If its still not working I'm unsure why as it works fine for me. A clean flash would probably fix the issue if wiping the caches does not.
[Samsung Galaxy Nexus] EvilDobe:
100% clean install. I was coming was from PA so I wiped everything. Also when it didn't work I installed it again with a clean install. I now have Apex, Nova, stock, and Next Launcher 3D... none of them let the navbar become transparent.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Clean install here too. You can see the status bar is transparent but the nav bar is not.
[Samsung Galaxy Nexus] EvilDobe:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Yours does more then mine. Mine just stays black.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Would you be so kind as to shoot me that wallpaper? I'm going to try to recreate what you are talking about.
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Here is my wallpaper. Thank you for looking at this.
[Samsung Galaxy Nexus] Acvice:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

Ok, if you take a look at the first screenshot, you'll see 100% transparent navbar and status bar on the stock launcher. There is a shadow at the bottom above the navbar. The second picture is the same wallpaper with Nova launcher, with the shadow turned off. So, you see, the nav bar is 100% transparent in both instances. Stock launcher for android is just an uncustomizable piece of crap. There is literally no reason whatsoever to use it.
[Samsung Galaxy Nexus] bigrushdog:
Try those default check boxes for stock launcher.
[Samsung Galaxy Nexus] ajf64:
i found 130 on the nav bar and 255 on the status bar with auto brightness on looked more unified but im also using a dark screen
[Samsung Galaxy Nexus] slyd0997:
Re: [ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Toroplus

It was a silly question. Thx.

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
[Samsung Galaxy Nexus] ajf64:
what skin is that u are useing brd?
[Samsung Galaxy Nexus] bigrushdog:
https://play.google.com/store/apps/details?id=bigdx.jbextreme.com

I'm working with the developer bignadad to get ECC themed up. I HIGHLY recommend this theme series.
[Samsung Galaxy Nexus] EvilDobe:
Circle battery = bad. Looks great otherwise.
[Samsung Galaxy Nexus] sirxdroid:
Please don't force a theme by default. Having the option to theme the ROM is fine, but not everyone likes themes.
[Samsung Galaxy Nexus] EvilDobe:
I don't think he's referring to the rom getting themed but the EOS Control Center (ECC). Probably lookin to spice up the ECC interface for us.
[Samsung Galaxy Nexus] ajf64:
that looks nice ya i saw ur eos icon had was different im using

https://play.google.com/store/apps/details?id=com.darkdog.theme.crystal2

Atm i really like how he used transparent icons so they look good with any color bg but im going to give that one u linked a try
[Samsung Galaxy Nexus] bigrushdog:
I meant the BigDX jellybean extreme theme series is is becoming compatible with our control center. So the control center will be properly themed when using this theme series. I'm not theming anything lol. Man I can't do graphics for squat! But bignadad can and he's most talented.
[Samsung Galaxy Nexus] ajf64:
what dose it matter even if he did set a new skin to default u could go in and change back to stock with theme manager. Any way that is the whole reason its there for so u can change a theme on the fly and not have to worry about it. I would love to see a custom skin for eos and im sure alot of people here would to, so plz brd dont listen to people like him. People who like stock can always use stock so lets get something for the people who love sexy custom skin. And we all know u don't do graphics work but we all know uber dose :)
[Samsung Galaxy Nexus] bigrushdog:
I should make this default

Now that's smooth!
[Samsung Galaxy Nexus] sirxdroid:
A little more pink and I'm in :)

---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------

That's fine, you may include themes in the ROM, as long as the stock one is there too and it's the default :)
[Samsung Galaxy Nexus] bigrushdog:
https://play.google.com/store/apps/details?id=bigdx.jbextreme.purple

I'm just showing off my buddy's work. Get it from the market.
[Samsung Galaxy Nexus] Acvice:
New build is up