[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - Grouper

Search This thread
By:
Advanced…
ricardowec

ricardowec

Senior Member
Jul 7, 2011
1,941
577
Galapagos Islands, ECUADOR
www.ricardowagner.com
Yes... I is an epic move from Team EOS.. CONGRATULATIONS.. Just wipe caché and delvik as usual and flash over 32.

As it comes with the stock kernel, will flash Franco 20 shortly.

Sent using The Beast via Tapatalk 2

---------- Post added at 05:41 PM ---------- Previous post was at 05:37 PM ----------
lightninbug said:
I too updated my boot loader last night....after a full wipe and installing this ROM r33 everything works perfectly!! Even running Franco kernel r20!!! Epic work team eos!!

Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse

No full wipe required

Sent using The Beast via Tapatalk 2
 
ÜBER™

ÜBER™

Recognized Themer
Nov 9, 2011
13,808
8,904
Texas
Hey BRD where's my nav bar mods bro!? :p JK how is that coming along?

Sent From My N7 via White Tapatalk
 
ricardowec

ricardowec

Senior Member
Jul 7, 2011
1,941
577
Galapagos Islands, ECUADOR
www.ricardowagner.com
short/y said:
I haven't answered because I wasn't sure what you were asking. So, let me see if I can answer two of the questions you may be asking.

First, I flashed this BEFORE going to 4.1.2 so if you were asking if it was OK to flash before build 33 (which includes 4.1.2 code) then I guess the answer is yes, it's OK. I flashed it this morning and ran for a while on 32 (while waiting for 33 to show up on goo.im). I had no discernible problems with it.

I just flashed 33 and checked the bootloader version AFTER bringing 33 all the way up (yes, I rebooted after installing 33). My bootloader is still 3.41 so if you're asking whether you need to reinstall the new bootloader after flashing 33, I guess the answer is no, you don't.

Hope this helps.
Click to expand...
Click to collapse

Thanks Shorty.. No, I was just concerned I might go back to the original b/l because as stated in other thread ( stock rooted 4.1.2) the b/l has to be flashed AFTER upgrading to 4.1 2 which has proven not to be the case with EOS, in fact the new b/l is not needed unless you want to solve the recovery from b/l bug.

Everything is fine on my side also, except that we have to wait for the new Kernels.

Cheers

Sent using The Beast via Tapatalk 2
 
B

brizey

Senior Member
Aug 6, 2011
2,451
620
I flashed dirty with no wipe and was unable to reboot properly. Had to boot into fastboot to get to recovery. I did flash a faux kernel...is there an issue there?

Edit: I am dumb. Kernels need to be rewritten for .2
 
Last edited:
ricardowec

ricardowec

Senior Member
Jul 7, 2011
1,941
577
Galapagos Islands, ECUADOR
www.ricardowagner.com
solarnz

solarnz

Retired Recognized Developer
May 23, 2010
679
2,121
Sydney
lightninbug said:
Just a quick question... may be mighty stupid...but I'll ask anyway.. are the new binary drivers in r33? Fond in this thread.. http://xdaforums.com/showthread.php?t=1905961

Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
There were minimal changes to the proprietary binaries, and these have been included.

player911 said:
Just flashed latest 4.1.2 nightly and latest bootloader. All seems well except the Build number still says JR003L build 33!

Its freaking me out! >:D


Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse

Oops.
 
  • Like
Reactions: lightninbug
GideonX

GideonX

Senior Member
Jun 10, 2010
3,489
3,754
NYC
www.droidhype.com
lesilent said:
Hi !

Two questions :

1- Do i have to download this Bootloader ? http://xdaforums.com/showthread.php?t=1928915
2- Do i have to unlock the new Bootloader ?
3- Could i live WITHOUT upgrading Bootloader ? (i think it does not affect Nexus 7-EOS smoothness and functions..
Click to expand...
Click to collapse

1 - no, but it's recommended to prevent you from not getting into recovery from the bootloader.
2 - it retains whatever lock state you had. Mine was unlocked, it stayed unlocked after flashing the new bootloader.
3 - yes, but it all goes back to #1.

Sent from my Nexus 7
 
lesilent

lesilent

Senior Member
Aug 9, 2011
136
4
GideonX said:
1 - no, but it's recommended to prevent you from not getting into recovery from the bootloader.
2 - it retains whatever lock state you had. Mine was unlocked, it stayed unlocked after flashing the new bootloader.
3 - yes, but it all goes back to #1.

Sent from my Nexus 7
Click to expand...
Click to collapse

Ok..thanx a lot.

Could i flash with CWM recovery ?
 
Reginald476

Reginald476

Senior Member
Sep 19, 2012
690
510
Lansing
I flashed the bootloader zip in TWRP 2.3 and it went smooth as butter, I am still on build 32. I can now boot into TWRP from the the bootloader!!! Downloading build 34 right now.
 
ricardowec

ricardowec

Senior Member
Jul 7, 2011
1,941
577
Galapagos Islands, ECUADOR
www.ricardowagner.com
It is my feeling that my N7 is consuming more battery than in previous versions.

Here is what I've done

- installed 33 yesterday. It came with stock Kernel and my battery consumption was abnormal.. So i thought the kernel wa to be blamed for it.

- so last night I installed Trinity 166 ant uc at 1.3. Same story

- installed 34 this morning with the EOS kernel... Same story, have lost 10% since then ( less than 1 hour)

Anyone in the same situation?

Sent using The Beast via Tapatalk 2
 
L

lightninbug

Senior Member
Sep 17, 2009
4,968
1,789
ricardowec said:
It is my feeling that my N7 is consuming more battery than in previous versions.

Here is what I've done

- installed 33 yesterday. It came with stock Kernel and my battery consumption was abnormal.. So i thought the kernel wa to be blamed for it.

- so last night I installed Trinity 166 ant uc at 1.3. Same story

- installed 34 this morning with the EOS kernel... Same story, have lost 10% since then ( less than 1 hour)

Anyone in the same situation?

Sent using The Beast via Tapatalk 2
Click to expand...
Click to collapse

I'm kind of in the same boat...although I am not losing 10% an hour, I am noticing slightly faster battery drain.

Sent from my Nexus 7 using XDA Premium HD app
 
kptnk

kptnk

Senior Member
Apr 15, 2011
1,546
686
Paris
ricardowec said:
It is my feeling that my N7 is consuming more battery than in previous versions.

Here is what I've done

- installed 33 yesterday. It came with stock Kernel and my battery consumption was abnormal.. So i thought the kernel wa to be blamed for it.

- so last night I installed Trinity 166 ant uc at 1.3. Same story

- installed 34 this morning with the EOS kernel... Same story, have lost 10% since then ( less than 1 hour)

Anyone in the same situation?

Sent using The Beast via Tapatalk 2
Click to expand...
Click to collapse

lightninbug said:
I'm kind of in the same boat...although I am not losing 10% an hour, I am noticing slightly faster battery drain.

Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse

You need to wait 2 or 3 full battery cycles to state on a real battery drain, especially with both new Rom and new kernel.
 
  • Like
Reactions: poondog
You must log in or register to reply here.

Similar threads

aaronpoweruser
  • Locked
  • Poll
[rom][8/1] paranoidandroid 3.91 | 4.3
Replies
18K
Views
4M
EvanA
EvanA
eak1080
[ROM] CyanogenMod 11 [OFFICIAL] [NIGHTLIES] [M5]
Replies
4K
Views
909K
D
dado1295
rascarlo
[ROM] RASTAPOP[Android 5.1.1_r6 LMY48G] [PRODUCT_DEVICE := grouper]
Replies
4K
Views
648K
K
kot5678
Dees_Troy
[RECOVERY][grouper] TWRP 3.1.1-0 touch recovery [2017-05-19]
Replies
1K
Views
533K
dark0shark
dark0shark
franciscofranco
[KERNEL][GPL][N7]franco.Kernel - r82
Replies
9K
Views
2M
rahimali
rahimali

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 47
    teameos
    teameos
    Team EOS​
    JB 4.1.1 Grouper​
    NIGHTLIES​

    Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!

    It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.

    --
    NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
    --

    A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.

    EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.

    Team EOS Nightly builds: http://goo-inside.me/devs/teameos/roms/eos3/nightlies/grouper/

    G-Apps Package
    Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:

    Temporary Gapps package gapps
    --
    Features:
    Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
    For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org

    Kernel:
    Kernel Note: This rom is currently using the stock kernel, so you can find the sources from aosp.

    --

    Installation Notes:
    These builds are designed to be installed from your favorite recovery.
    Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS or JB based rom.

    BUGS!
    If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.


    Want to contribute to the Eos rom? Well you can!
    Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.

    ---

    Enabling voice search in google now

    1. Go into Settings
    2. Go to "Language & input"
    3. Scroll down to "Speech" and click on "Voice Search"
    4. Click on "Download offline speech recognition"
    5. Swipe Across to the "ALL" tab if needed
    6. Download your speech pack for your language
    View
    20
    bigrushdog
    bigrushdog
    Just a quick update. We've been taking a break while we wait for 4.2 source to drop. A much needed break I might add. I've taken the opportunity to learn A LOT of new things. So later I can apply these new skills to rich dynamic and stable new and innovative features. Thanks for rolling with Eos guys.
    View
    16
    bigrushdog
    bigrushdog
    ricardowec said:
    I apologize foe the comment I am going to make with regard to your post.

    I have been a big Fan of EOS since my Wingray days. I regret having sold it as I enjoyed every single N/L because it added functionality, power (by the way of the Tiamat Kernel) and ad the end.. value.

    And I regret more the fact that I replaced it by a useless quad-core device that devs have overlooked at. This device is a Tegra. 3 similar to several you do work for but does not even have a custom kernel.. not even a custom rom.

    With regard to the N7 you where one of the first to show up.. your work is great but honestly I can't figure it out what is in the pipeline other than implement features mentioned by you, similar to what PA already has.

    I haven't even flashed 26 because I lost interest. I preferred to switch to the "other " because I know there is a pipeline of features without loss in. Stock functionality or stability ( as once was suggested in this thread) .

    Just to mention .. with regard to the screen density I was told to go to the market and get. "One of several apps available ". Very disappointing comment that at the end you are backing up from.

    Cheers

    Sent using The Beast via Tapatalk 2
    Click to expand...
    Click to collapse

    Hmmm. Where do I go with this... ok. We don't really try to "sell" the Eos project. This project is a manifestation of mine and solarnz's desire to build aosp as a hobby. On goomanager, we go back and forth with aokp as the top downloaded build. The reason is word spread by "mouth" that our builds are generally highly stable and fast as hell due to true linaro optimization as well as various other optimizations. Also, people tended to enjoy our builds for simple, unobtrusive features that people actually use. This is not a feature driven project. Features, in and of themselves, do not make a great build. This is a project built from scratch. Eos is not "based on" cm, aokp, or any other teams work but our own. We may bring in another teams work just as we know other teams use our work. For the most part, we build features for ourselves. If there's something I want, I write it. Coming from Xoomland, you also know we can be highly responsive to user needs as well. So your concern is what's in the pipeline. I don't know. Whatever crosses my mind as a cool idea. This is how its always been with us. There's no shortage of roms these days. Although they are almost all one flavor of cm or aokp. And that's just fine. If another build suits your needs, by all means good sir flash away. That's why you bought a nexus device in the first place. Don't I have the right to change my opinion on a matter based upon further reflection or understanding? Yes, there are plenty of apps that will fully and effectively change your system dpi for you. No, there are no apps that will do what the Paranoid team has accomplished. Therefore, it has attracted my attention. But why would I bloat our build with a feature that is available for free on the market? Especially since many users have no interest in such a feature. A rom feature should encompass functionality that a user app can not accomplish. Hope that brings clarification to my position.
    View
    13
    bigrushdog
    bigrushdog
    ricardowec said:
    Can see. Oven at full speed.. Lots of devices to care for. Anxious to see how they bring in all their mods.

    I am standing still on #37

    Sent from The Beast via Tapatalk 2
    Click to expand...
    Click to collapse

    Ya I'm working at full throttle. It's been an insane amount of work. Very soon now.
    View
    8
    solarnz
    solarnz
    Just to give you guys a tease of something I'm adding...

    QhsY.png


    wp1L.png


    69iNy.png


    This is WITHOUT any dpi hacks, and will be user selectable between the hybrid UI and the tablet UI.
    View

New posts