does that mean v96 OC GPU by default... If it's true,I dont want that. I want my xoom to be run at the stock freq. And, OC is forever remain as an option
Please, someone help me to clarify ....
[ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
- Thread starter teameos
- Start date
- Status
does that mean v96 OC GPU by default... If it's true,I dont want that. I want my xoom to be run at the stock freq. And, OC is forever remain as an option
Please, someone help me to clarify ....
does that mean v96 OC GPU by default... If it's true,I dont want that. I want my xoom to be run at the stock freq. And, OC is forever remain as an option
Please, someone help me to clarify ....
The GPU will be overclocked.
If you want a stock gpu clocked kernel, you will need to flash the 3.0.5 kernel.
I can't please everyone...
Thank you for a quick clarification there. hix... hix.. OK i guess i either live with it or dance around the old kernel then..
Any idea why gpass has changed??
Any idea if its ok to try just wiping cache and dalvic cache then flashing
nightly 96 and new gapps is relatively safe?? Would like to atleast try avoiding full wipe.
Any idea if its ok to try just wiping cache and dalvic cache then flashing
nightly 96 and new gapps is relatively safe?? Would like to atleast try avoiding full wipe.
OK, for those who's devices don't boot with the latest roms, please try the following kernels in sequential order and report back.
If you have a device that boots with the latest builds, don't bother trying these - you're just wasting your own and my time.
http://goo.im/devs/solarnz/test/Tiamat_TEST_1.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_2.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_3.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_4.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_5.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_6.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_7.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_8.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_9.zip
I have verified that all 9 kernels boot on my own device.
If you have a device that boots with the latest builds, don't bother trying these - you're just wasting your own and my time.
http://goo.im/devs/solarnz/test/Tiamat_TEST_1.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_2.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_3.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_4.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_5.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_6.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_7.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_8.zip
http://goo.im/devs/solarnz/test/Tiamat_TEST_9.zip
I have verified that all 9 kernels boot on my own device.
Sorry for the confusion, meant to say all along "splash screen"
I am down loading 97, then will try the test kernels in order.....I will post my results
Sent from my Xoom using XDA
How about providing a version of the latest kernel that is not overclocked so people can decide which version they want to use.
Sent from my PC36100 using Tapatalk 2
okay, tried all of them with the nightlies #93, #96 and #97 (btw #97 is in the cornerstone category of goo.im) ... still no success, still stuck on splash
//edit
i figured out that its not a kernel problem ... after the testing session with the 3 nightlies i restored my rom (#90 was the last that worked for me) and flashed your kernel 3.0.14 test1 file over it... it booted up completely without any problems...
Last edited:
Have tried going all the way back to stock? Delete everything, unroot? I mean all the way back. and then starting over with the rom. Something doesn't seem right. Are you loading the rom from your external SD card? And do you have a nandroid backup that maybe you can start from?
---------- Post added at 08:09 AM ---------- Previous post was at 08:01 AM ----------
I guess you updated the same time I replied. Glad you got it working.
Last edited:
Solarnz,
OK, I first updated to 97-----no joy
Then I tried the 3rd 3.0.14 test kernel you posted previously------no joy
I then tried Tiamat Test 1....it works
the only thing I did was wipe Davlik cache between flashes.
Everything seems to be working good...Nightly 97 Test kernel 1
Sent from my Xoom using XDA
yeah... but only with #90 ... btw im doing everything from the internal storage and i started also from the beginning...
Solarnz,
OK, I first updated to 97-----no joy
Then I tried the 3rd 3.0.14 test kernel you posted previously------no joy
I then tried Tiamat Test 1....it works
the only thing I did was wipe Davlik cache between flashes.
Everything seems to be working good...Nightly 97 Test kernel 1
Sent from my Xoom using XDA
Sorry if I wasn't clear, I'm more interested in which ones don't work.
Each kernel is one change between Tiamat 3.0.11 and Tiamat_3.0.12.
Once I know which one breaks it, then I can revert that change and everything *should* be good again.
yeah i know... i tested ALL NINE kernel files with the builds 93, 96, 97... no success...still stuck on splash
then i reverted back to my backup (nightly #90) and flashed, just for fun, tiamat 3.0.14 test1 ... and it worked
I wonder if your downloads are getting corrupted. Everytime I update the Nightly I always wipe the big three. I tried using the internal on my wife's on an update it seems like it took longer. I always use the external SD. Glad you got some life back in it.
Can you please give me the output of:
Code:
adb logcatOn the latest build.
If you start this just after you reboot from recovery it should connect.
(This is while the device is still at the splash image - I now believe the device is actually starting but cannot progress to the point where it can start the boot animation)
Can anyone report on the Android OS drawing a lot of juice in builds 96 or 97? I just updated the other day from I guess 91 (one that I had ran for a while and didn't have this issue) to i think 95 and experienced my xoom going from 90% to 14% in 24 hours with only 2 hours of use. I have installed 97 but won't have much time to test between now and wednesday when i leave for vacation and just want to see if maybe I should revert back as I don't want to have to deal with a dead battery unexpectedly while out of town if I forget to charge it overnight.
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
215Team EOS XOOMICS 4.0.4 Wingray MZ604NIGHTLIES
Welcome to the evolution of TiamatXOOM.
With the AOSP release of Android 4.0 begins the next dawn of the Android operating system. And with this release comes Team EOS, the natural evolution of the TiamatXOOM development team.
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. The launching point for this development effort is the Motorola XOOM.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
--
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 once every 24 hours 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 Xoom 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 Xoom Nightly builds: http://goo-inside.me/devs/teameos/roms/nightlies/wingray/
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:
Use the latest available gapps package available from http://goo.im/gapps
*Note - You will need to re-flash G-Apps after you flash an updated nightly build. You can do this before you reboot after the installation of a new nightly.
Also note that if you are coming from an earlier G-Apps package you will need to wipe prior to installation of this package in order to avoid FC issues.
--
Current Known Issues:
This builds is only for the MZ604 Wingray (WiFi XOOM) It does not support data on any GSM or 3G only Xoom
Features:
Because these are nightly builds the included features are constantly evolving. Change logs are generally generated on a daily basis.
Change logs can be viewed at http://nightlies.teameos.org/changelogs/
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Tiamat ICS Xoom kernel
Support for OC;Under/Overvolt
Governors: lagfree, interactive, conservative, ondemand, userspace, performance
Kernel Note: In compliance with GPL kernel source can be found at: http://git.tiamat-dev.com/tegra2/tiamat-xoom/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery (Solarnz R4c, Rogue, Clockwork)
Perform a full wipe (read Factory Reset) prior to installing this over ANY Honeycomb based rom (this includes all Tiamat roms)
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
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.
FEATURE REQUESTS!
We need YOU, yes YOU to help us build the best AOSP rom out there. Have an idea for a feature you want to see implemented then let us know!
Team EOS Feature Request
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
EOS Motorola Xoom Boot Splash
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.
Welcome to the XOOM evolved. Welcome to Team EOS.57For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
Also a note on 3G/4G Xooms- You can infact flash and install this rom on 3G/4G xooms. You will not however be able to use the 3G/4G radio. There are new basebands that are needed in order for the 3G/4G radios to be able to communicate with the RIL and until these updated basebands are released we are in a holding pattern for radio connectivity.
Also there are sporadic reports of HDMI partly functioning. Full HDMI functionality is dependent on additional proprietary binaries that Google has not been able to release yet due to licensing issues.
Also, please note that while the current builds are proving to be very stable, and for users that do not use their cellular radio they can be used as a daily driver these are still nightly builds and are subject to constant development. If you find strange or otherwise unexplained errors logcats are greatly appreciated as it makes it much easier to track down issues.
Thank you all for your support!
*Updated G-Apps Package*
The developers working on CM9 have released an updated G-Apps package for 4.0.3 AOSP based builds
New version is 4.0.3 V8
A Special Thanks goes out to gpstar this G-Apps build
Download: http://www.multiupload.com/54DD4VIXZ6
MD5: 4a6a7543b025a17f9536eccc4e5afc17
*Note - Because of changes made to the G-Apps package a wipe will be required if installing this version of G-Apps over a previous G-Apps package in order to avoid FC issues. This version of G-Apps appears to address some of the communications issues that have been plaguing Google services on AOSP builds.
Bug Reporting:
As you test out the platform and you discover bugs please report them to:
https://bugs.teameos.org/
A couple of notes about bug reporting. If it is an application issue (IE a particular game generates FC errors) please do not report it. There is nothing that we can do about specific application issues.
If you do report an error please, Please, PLEASE include logcats showing the errors. It is often time difficult if not impossible to replicate errors and logcats make resolving issues much much easier. Please feel free to add the logcats as attachments to the bug report.
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
Eos Motorola Xoom Boot Splash
Thank you again for your continued support of Team EOS!19
Ya I'm certain it will. We just gotta dig through the code some. You guys may have noticed the change log slowed down a bit. Its called burn out. Our build is pure aosp and our (mostly solarnz 's) commits. Unlike cyanogenmod, who has around 170 maintainers, we count our maintainers on 1 hand. We don't pull commits from all over and call it a new rom. We don't kang. Our build is organic from the ground up. Also, the xoom builds are built by two guys who have been in the xoom game from DAY 1, when we had no source and nobody else wanted to touch Honeycomb. Just thought I'd throw that out there.18This was originally posted in the Stingray thread in response to the issue of the leaked sbf that appeared yesterday.
--
The sbf in question that has been released comes from points unknown. There is no way of truly verifying its orgins or its integrity. Use extreme caution if you choose to flash this sbf as there is no way of knowing what changes if any have been made. We have chosen to use only what is absolutely necessary out of this release and even what we have chosen to use has been tested by our own infosec people.
Yes this may sound paranoid, however when it comes to my personnel data and what we put our name on for the community we are extremely cautious as to ensure the safety and security of all who choose to use these builds. I would much prefer to err on the side of caution then to put any of you at unnecessary risk.17
Build IML77 for the MZ604 (Wingray) - this is the official ICS OTA that is being pushed out for the soak test prior to general release. I can now say that we have this build in house and are working on it.
That and...
It's about damn time Motorola released this!
