yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cellsafemode:
the kernel is actually a aosp base. I manually pulled the parts of the glados kernel that had the extra drivers out. then I patched them in the aosp kernel. along with some other mods. this is not a glados based kernel, just has the same addon drivers.

---------- Post added at 07:47 AM ---------- Previous post was at 07:20 AM ----------

certain features have not been exposed to the ui that exist in the kernel. we will eventually have all those features exposed. one way or another
[Samsung Galaxy Nexus] Savant:
Great work and looks fantastic.
[Samsung Galaxy Nexus] djjonastybe:
You do know that TM stands for Trade Mark right :D ? I don't think you should be using that :D
[Samsung Galaxy Nexus] original21:
Does this rom included customized nav bar?
[Samsung Galaxy Nexus] cellsafemode:
using it where? the look of the name is a logo... which is the definition of a trade mark. but please lets arm chair lawyer this thread up with bs about correct legalese. suffice everything to say no copying or pretending you are us or modifying and redistributing those modifications.
[Samsung Galaxy Nexus] sert00:
anyone have problem downloading?the site is down...
[Samsung Galaxy Nexus] dan96815:
Just downloading now works fine
[Samsung Galaxy Nexus] sam razzy:
Ohhh my goshhhh... em seeing this now... damn it... I gonna download now...

sent from jElly Belly NeXus PrimE
[Samsung Galaxy Nexus] amit_sen:
Very Fast ROM. Using it with lean kernel.

Default kernel stutters a lot initially(1-2 min).

Sound is LOUD as hell :) :)

Just a small request, consider theme chooser in upcoming version
[Samsung Galaxy Nexus] cellsafemode:
Themes likely will make an appearance eventually, but it's not exactly a priority at the moment. We are porting to other phones and working on some apps for the market.

When using other kernels, just note, we cannot make any sort of guess as to what will work and what wont and we dont care. The rom has numerous features that are kernel specific and even more importantly ramdisk specific. play in that area at your own risk, as we are only developing for the kernel we ship with.

As far as stuttering, you may see some laggy behavior for 20-30 seconds maybe.. This is mostly due to media scanner hitting up the storage for IO but it is likely also partly due to autogrouping where the kernel is learning what priority to give various processes. We felt that rebooting is fairly uncommon when compared to the benefit of the kernel being able to optimize cpu more fairly. Our only other possible reason for this bootup issue is our dalvik options which we feel are fairly nice, though they may take an initial toll. But it's our opinion that rebooting doesn't happen that often in normal circumstances so the positives outweigh this negative. It's literally less than a minute of less than crazy fast responsiveness.
[Samsung Galaxy Nexus] pottyvick:
I used to love the EB rom on the g2x. May try this when more customizations are implemented... Good job guys :)
[Samsung Galaxy Nexus] evodon84:
Flashed and running, seems nice so far for a first build. It does seem fast. Mine was stuttering at first as well but as cellsafemode mentioned above just the rom settling in after first boot. I did have a question if there are plans to include toggles and nav bar customizations. Also as you mentioned about the kernel will you be developing fast charge for the kernal?

So far its very nice though thank you
[Samsung Galaxy Nexus] cellsafemode:
the kernel already supports fast charge. we just didn't put the option in the Settings UI at the moment.
[Samsung Galaxy Nexus] evodon84:
Ok, thanks for the reply.
[Samsung Galaxy Nexus] cellsafemode:
Also it should be noted that external kernels that you use may be replacing the tuna power hal module to workaround screen on/off resets of the Cpu frequency. This is not cool.

Our rom has a screen on/off service that gets run to reset the frequency no matter what kernel you are running. The power hal module in our rom has been modified to handle re-initing the interactive cpu scheduler when the user has changed the scheduler.

The stock power hal module doesn't do this because such an option isn't available stock. So if your kernel replaces the power hal module and you utilize the ability to switch scheduler to something like "Ondemand" ...and then decide to go back to interactive, you will have default settings again in interactive. you'll have to reboot for the power hal module settings to be re-applied. Our module detects the change and re-applies the values at runtime.
[Samsung Galaxy Nexus] cpom1:
Use another ROM with it.

I dont see why people ask for the same features in every ROM. How does that give anyone selection if every ROM is the same?? There are plenty of great ROMs out there with features to fit everyones wants and desires.
[Samsung Galaxy Nexus] oOo B0XeR oOo:
We may add in a power widget tray toggle and some kind of navbar reorder in a bit. We want to write it fresh though and not just pull something from CM or AOKP. Right now we are focusing on a large scale multi-device deployment as well as a few Market Apps so Im not sure on the timeframe for those added features.
[Samsung Galaxy Nexus] AllAboutAndroids:
I'm just patiently waiting for EB to land on the T-Mobile Galaxy SIII :D
[Samsung Galaxy Nexus] cpom1:
Really liking this ROM. Been dying for you guys to come back. Thanks.
[Samsung Galaxy Nexus] Jesushasadroid:
This ROM is sick...rocked the past 3 days flawless....what about options for folders , launcher and more
[Samsung Galaxy Nexus] Toxina:
dont mean to insult anyone bad this rom lags really hard for me, anyone else having this problem?
[Samsung Galaxy Nexus] j0hnnyth3f0x:
At the risk of sounding retarded, which nexus device is this for specifically? Will it work with Toro?

EDIT: nevermind, I am retarded...Just noticed maguro in the title...smh

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] evodon84:
Roms been working great for me. I do notice that it's slow after a restart for a couple of minutes but after that it's butter.

Using the kernel that comes with the tomorrow.
[Samsung Galaxy Nexus] wallendiaz:
i lost my root after install this ROM :eek::rolleyes:
[Samsung Galaxy Nexus] cellsafemode:
I doubt root is lost. we have backups to safe guard against that. without a more helpful description of your problem... I'm going to guess that you think root is lost because there is no superuser.apk. just go on market and download whatever root manager you want.... it will also update su to one specific to that manager.
[Samsung Galaxy Nexus] badpanda:
Me too!

I lost root right after installing...
[Samsung Galaxy Nexus] damage98:
I had problems with supersu after flashing your rom. I launched it and just got the 'working'. Animation, and never an updated binary.

I was never prompted to allow root access by the usual apps which require it. No apps that had root appeared in the list of root apps allowed.

I tried changing to superuser but I still had problem with rights. Did fix perms it did not change the behavior. I of course did full wipe before flashing. Any ideas? I did a nandroid and changed to a different rom and no problem with that.

Thanks!
[Samsung Galaxy Nexus] cellsafemode:
you wont get prompts because everything is allowed. The stock su binary is meant to be replaced by the root manager app so it allows everything so you dont have to get stuck juggling root managers around to get the one you want.

Try this, goto EB Options. Goto the checkbox that says Su Disable .... check it and then uncheck it. Then try updating the su binary in SuperSU.

If that works then there is a slight bug in my su binary that deals with handling a default behavior when the property for disabling su isn't set (this happens when that checkbox has never been clicked). I _Thought_ i had that handled correctly but it may not be. Let us know if toggling the option on and then off fixes the problem with SuperSU.
[Samsung Galaxy Nexus] damage98:
It took me minute had to nandroid and install your rom.

It seems like checking the disable builtin su and trying to use supersu or superuser does not work. Titanium backup reports no root access until I re enable your su. I think this is as intended by you? When I restored apps supersu got installed and I made the mistake of thinking I needed it?

---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------

I just realized I did not answer your question. Your suggestion above did not work... So no bug?
[Samsung Galaxy Nexus] cellsafemode:
checking the disable checkbox will disable su.. the idea is to uncheck it after checking it. This creates a property file that su looks at. My bug may be in handling the case where that property file doesn't yet exist. (new install). If you can install superSU and update the su binary after unchecking that disable option then that's what is happening.

The in-rom su allows su access without asking a app for permission. This is intended in order to allow users to easily use whatever root manager app they want. It also allows us to universally repair broken su setups that we detect on boot so that the user never "loses root".

Your SuperSU app should now be able to replace the su binary now that you toggled the option on and off if the issue is what i think it might be.

edit: if the updating of su didn't work then i'll have to look into why by trying to install superSU and doing the same thing. But in the mean-time, everything that requires su access should work just fine. Assuming that Disable SU option isn't checked.

edit again : i tried out superSU. it does appear to not like whatever it's trying to do. i assume it updates the su binary automatically since there are no options to do so. weird. i'll have to debug supersu more. SuperUser.apk should fair better since it has a manual option to update and replace the su binary and i believe we tested that during pre-release and it worked fine.

---------- Post added at 11:46 AM ---------- Previous post was at 11:19 AM ----------

OK, I just tested SuperUser and it works just fine. SuperSU must be trying to do something strange upon installation (perhaps to work around most rom's needing another superuser app installed for su binary to work) ... Basically, SuperSU is trying to be smart, but fails to handle the most simple scenario where it's got root access without any apps installed.

It looks like for SuperSU you'll have to install a non-SuperSU root manager app first so it can be smart and work around it when you install SuperSU. At some point we should probably message the person who does SuperSU and let them know that their app is not handling this situation (and there is no reason why it shouldn't handle it).
[Samsung Galaxy Nexus] damage98:
Awesome and thanks for the detailed explanation. I really like this rom.

If it helps, the reason I found this 'feature' is that I was trying to create a nandroid from cwm gui and your rom will not restart and create the backup from there. I like to nandroid from cwm gui in os so I can easily create a backup name other than the default. Hope this helps!
[Samsung Galaxy Nexus] poging22:
looks like an awesome rom!
[Samsung Galaxy Nexus] cpom1:
anyone been having issues with wifi going in and out?
[Samsung Galaxy Nexus] oOo B0XeR oOo:
There shouldn't be any lag at all. If youre experiencing any lag (aside from just after a reboot) than you should reinstall or look into your hardware.

The only reason it may seem to lag after a reboot was actually intentional by design... the media scan is delayed until after the rom fully boots (as opposed to during). This allows the bootup to be much more efficient and quicker.
[Samsung Galaxy Nexus] oOo B0XeR oOo:
No. Please elaborate...

Do you mean wifi bars going blue to gray or losing wifi icon completely?

Are you using 2.4gHz or 5gHz network? WEP or WPA?
[Samsung Galaxy Nexus] lowrider262:
was this happening to you on any other jb ROMs? cause I've noticed (for me anyways) WiFi signal pretty much sucks in general on all jb ROMs compared to ICS.

man I can't wait to see this ROM progress! team EB was the king of the g2x forums back when I had mine... top notch work from top notch devs!:thumbup::beer:
[Samsung Galaxy Nexus] Savant:
Don't have problems with WiFi on any connection with jb and I'm always at full bars.
[Samsung Galaxy Nexus] cpom1:
Nope. This wasn't on the other jb ROMs I generally use.
[Samsung Galaxy Nexus] badpanda:
I'm having lots of lagging even after 48 hours of heavy use...
[Samsung Galaxy Nexus] blitz911:
So far so good. Bluetooth and wifi work well, no issues with connectivity. Digging the built in color control. One thing, I accidentally forgot to delete SetCpu when I restored my apps through Titanium and that caused screen/sound jittery issues since it has it's own cpu control, but once I deleted SetCpu, it was all good. Benchmarking seems like a no-go with Linpack and Quadrant due to some very abnormal scores, but the phone runs great anyway. The battery icons don't seem to be calibrated. It was stuck on 44 when the phone was down to 29, lol. Gonna run it for a few days and see how battery life is. Other than that, another very solid ROM. Thanks EagleBlood team for all your work. Besides stock rom, EB is the only other one I've had and used as a daily driver..
[Samsung Galaxy Nexus] cellsafemode:
indeed, this rom is meant to be run without any hardware manipulating programs. No setcpu, no glados control apps... etc. Not all of their features will conflict, but some do.

as far as lagginess ... The rom implements the overheating protection mechanisms found in the glados patchset. Once it hits 90Cish it will underclock until it cools down. You can check the cpu settings menu and verify what the temperature of your phone is when you experience this lagging after boot.

if it's temperature related, then this is intended. It keeps your phone's hardware safe. Once the phone reaches 110C for any given period of time you will start to damage the hardware since that's the thermal limit of the solder joints on the cpu (not that they would melt at that low temp).

edit: If you are using a kernel other than the one that comes with the phone, then you might as well not bother posting about problems about performance here. I have no control over what other kernels do or how they're setup. The rom is setup with certain expectations and I really have no idea how it behaves when those aren't met.
[Samsung Galaxy Nexus] cpom1:
Been using it with trinity without any issues. You mentioned that the ROM has some fail safe guards when it comes to throttling...so if you install any other kernel are those applications still implemented?

And I haven't had an ounce of lag. Fixed the WiFi issue. So everything is smooth now.
[Samsung Galaxy Nexus] cellsafemode:
the kernel has thermal throttling... and so it depends on if the kernel you install also does.

As always with those experimenting, if you decide to use another rom or use kerne/hardware modifying programs, dont bother reporting on rom behavior unless you've verified it is behavior that exists in stock-form.
[Samsung Galaxy Nexus] blitz911:
After a few days, I must say that this rom is badass..super stable and smoith plus battery life is one of the best I've ever experienced and I usually use stock ROM+Franco or JameBond kernels.. thanks..
[Samsung Galaxy Nexus] dw9906:
Wow, you should really pull this rom. It has some serious problems. Talk about being laggy.
[Samsung Galaxy Nexus] cellsafemode:
yea i know there are some serious issues. The biggest issue is that there are these users who feel the need to reboot their phones all the time and base the performance of the rom on how it handles this task that by all accounts should not be done during the course of any normal use. I so wish we could fix that issue.

We purposely sacrifice bootup jitters for better actual-use performance. And it's obvious that it pays off as seen above by the reports of those who dont have some kind of reboot OCD.

For those with actual feedback : if there is jitterness after bootup (30 seconds or so after home screen) then one would think some logs and other important information would be great to track down what's going on as it's not normal behavior and would indicate something is misbehaving.
[Samsung Galaxy Nexus] damage98:
Personally found this rom to have great performance.

Thanks for all your efforts.
[Samsung Galaxy Nexus] sudman:
Search bar removal?

Hi does anyone know if it's possible to remove the search bar at the top in this rom or will I need to find & flash a patch to do this.

Cheers

Sud
[Samsung Galaxy Nexus] evodon84:
I've had zero lag issues during daily use with this rom using EB kernel. Not sure what some others have been experiencing. I would be happy to provide any logs you want but I only have that normal lag during the first 20-30 seconds after boot which has been discussed to be normal. Also getting the best battery life of any rom I've used with this phone.

---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------

Umm you could install a different launcher. I don't use the built in launcher so I can't remember if there is an option to remove the search bar.
[Samsung Galaxy Nexus] cellsafemode:
there is no current option to removing the search bar.. In the next release we will have more launcher options .. At the moment we're rolling out some apps we'll have on the app store.
[Samsung Galaxy Nexus] oOo B0XeR oOo:
Its hard to find any truth behind this comment after yours is 'sandwiched' between the two posts below...

...trolling?
[Samsung Galaxy Nexus] Savant:
Great ROM and works wonderfully so far
[Samsung Galaxy Nexus] blitz911:
Hmmm...i just noticed something...i don't usually plug it in to transfer files because I've always used Airdroid, but now that I did plug it in, the computer doesn't see the phone..It just doesn't go to MTP/PTP at all..it might just be me, but it could connect fine when I was on stock rom..Samsung drivers are already installed..other than that though, it definitely is a great rom..not many roms can be this stable and smooth for an initial release..:good:
[Samsung Galaxy Nexus] oOo B0XeR oOo:
Ya I don't know whats going on these days regarding USB drivers on PC's going in and out... seems to happen to me on all ROMs including a clean AOSP build and Stock. I've also noticed a few times I'll plug in and it'll fail mounting it but I'll unplug from the USB-A (PC side) and replug it in and it gets recognized. It's real strange. I swear I have to reinstall the driver on my office PC at least twice a month.

I'll edit this post in just a sec with a download link to the i0250 USB driver.

http://www.mediafire.com/?yy8aukcgkyg9qwz
[Samsung Galaxy Nexus] blitz911:
Thanks oOo B0XeR oOo. I re-installed it and it still didn't work. I then tried the Samsung USB cable since I was using another brand cable and it worked. Such a brain fart moment, not checking it with the Samsung cable first..D'OH! Thanks though.
[Samsung Galaxy Nexus] oOo B0XeR oOo:
We have a really cool app coming out in the Play store very soon... keep your eyes open.
[Samsung Galaxy Nexus] astaccz:
Im loving this rom. The smoothest ive tried on my phone. Can i flash another kernel? Will the rom have problems after flashing another kernel? If I can what kernel do you prefer?
[Samsung Galaxy Nexus] blitz911:
You can flash any kernel you want, but the EB team won't help if that kernel messes with the rom on your phone. They've already stated that. They made this rom and kernel to match each other perfectly. Anything else might throw it off..but feel free to experiment at your own risk though..:p
[Samsung Galaxy Nexus] astaccz:
Thanks for that information. I went ahead and flashed a Trinity Kernel. Everything works smooth still but it broke the gamma and vibration strength in EB settings. Which is fine because I like the Trinity Colors and vibration settings.

But I flashed some updated drivers for Galaxy Nexus on this rom and it improved the scrolling speed massively on top of what the EB Team has done to this rom already. http://xdaforums.com/showthread.php?t=1930640 The only problem I had with that is that now Stock Gallery and Stock Camera Apps say no external storage available which is weird. I had to download third party apps. I let the OP in that thread aware of my problem.
[HTC One S] topcat888:
Hi,

In FASTBOOT my HTX S says it is VLE PVT

I'm assuming this one and the same 'Ville' version, in which case I can install CM10 nightly's as listed here:

http://get.cm/?device=ville

Thanks
[HTC One S] a13xemz:
Yes the HTC One S is called the ville so that is the exact nightly !
[HTC One S] el_smurfo:
Assuming you have the S4 processor. There is no CM port to the S3 as of now.
[HTC One S] topcat888:
Yes, its the S4.... Another question, once you have flashed the first nightly including the boot image, do you have to flash the boot image each time when you flash the next nightly..??

Thanks
[HTC One S] el_smurfo:
Only if it changes. BTW, if you have hboot less than 1.13 and use TWRP, you don't need a separate flash of the boot.img.
[HTC One S] topcat888:
How will I know if it changes, as the page doesn't mention boot images at all..??

http://get.cm/?device=ville

Thanks
[HTC One S] el_smurfo:
Look for anything kernel related. You can also extract the boot.img from the zip and compare the MD5 from the previous install.
[HTC One S] topcat888:
ok thanks...
[Galaxy Note 10.1 Android Development] zedomax:
Here's App2SD Script you can use to "swap" your internal storage and microSD card storage space.

For example, if you have a 16GB Note 10.1 and use 64GB microSD card, applying this script will allow you to get 64GB for your apps instead of just 16GB.

When you first use the script, you might see missing app data. To fix this, simply copy the whole contents of your internal storage to microSD card beforehand (or you can do it after too). You can also use Titanium Backup app to backup apps/app data before using the script then restore your apps with data.

Now, you can enjoy 64GB easily without paying for it!

To disable the script, you can simply erase the file below using ES File Explorer with Root Explorer/Mount enabled in settings:

/system/etc/init.d/11extsd2internalsd

OR you can also disable the script by leaving your microSD card out during boot then plug it back in after booting.

Requirements:

- You will need a rooted ROM/kernel with init.d support (OR you can probably use Script Manager app to run the script at boot, I haven't tried this but let me know, it should work just fine)

- Works on ALL stock or TouchWiz based ROMs

- Works for ALL Note 10.1 including N8000,N8010,N8013

To install:

- Simply flash the zip file in CWM Recovery or TWRP!

Download App2SD Script v0.2:

http://downloadandroidrom.com/file/GalaxyNote10.1/app2sd/11extsd2internalsd_GNote101_ZEDOMAXv0.2.zip

Credits:

Thanks to Mattiadj for original script on i9300, which I modified for Note 10.1.

Here's a photo of my Note 10.1 Wifi 16GB:
[Galaxy Note 10.1 Android Development] iamchocho:
I didn't think this thing supported anything over 32GB for microSD.
[Galaxy Note 10.1 Android Development] mitchellvii:
It does. You just need to format it fat 32.
[Galaxy Note 10.1 Android Development] Noxey:
Quick question:

I'm new to the whole Android roothing thing. When you say I need a rooted rom, does that just mean I need to root my device? As in, if I root my device but continue running stock TouchWiz, can I enable this mod?
[Galaxy Note 10.1 Android Development] zedomax:
Yes it should work with any rooted on stock tomorrow with script manager although I haven't tried. If you have trouble just install my rom.
[Galaxy Note 10.1 Android Development] demandarin:
After I already returned my 16gb and ordered a 32gb..lmfao should be here Thurs.

Greatwork though..it'll likely come in handy as I have tons of big games. This is good to have for offline map use also.