yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] lchiu7:
Thanks. Since this Xoom isn't in regular use (I have a number of other devices) I decided to bite the bullet and shoot for a Lollipop ROM viz.

http://xdaforums.com/motorola-xoom/development/rom-omnirom-wingray-bigpart-alpha-t3147007

Had to basically the same steps except for having to format my device (wiping the partitions gave emmc errors) and also digging around trying to find the Gapps that work.

Have it up and running but with no camera support, HDMI audio, it's just a work on progress. I will wait to see what the devs are going to do next. But it's an amazing feat to get Lollipop up and running on a 1st gen tablet.
[Xoom Android Development] bigrushdog:
You got LP running? Did I read that right? If so you got sources up somewhere?
[Xoom Android Development] lchiu7:
I can't take any credit for this apart from following instructions from the Dev. Links to the ROM in my post. As I noted, it's a work in progress.
[Xoom Android Development] bigrushdog:
If you dig through the history on my kk4.4 av branch, you'll see a couple tegra2 compat commits. They will give you cam. And you probably need legacy hwcomposer support for hdmi. Check out kk4.4 libhardware and libhardware_legacy projects.
[Xoom Android Development] lchiu7:
Actually I gave up on the LP ROM and flashed this one. Since I already had a recovery that supports Bigpart it was pretty easy. Now the Xoom is going nicely and I think I will stick to this ROM from now one. It's amazing the life the old Xoom still has with the efforts of the developers. I am just using the Xoom to play video and audio to my HiFi system over HDMI and also some video via a Chromecast. For that it works just fine.

Only thing I have noticed IIRC. The 4.2.2 EOS ROM has some of speed control - overclock etc. This ROM doesn't seem to have this functionality.
[Xoom Android Development] bigrushdog:
Ya I know longer officially support xoom. I paid my xoom dues long ago. All the source is up on TeamEOS github if anyone wants to carry the torch forward. I just drop in from time to time when I'm either drunk or depressed and wish to reminisce back in the day when android was simple.
[Xoom Android Development] lchiu7:
I can understand that given the age of the device. For me all it does now is sit in a dock, connected to my TV over HMDI and play content. It also acts as a clock:)

Then emboldened by the success of this flash I also flashed my Everest device. It was slightly trickier since I originally put in the same TWRP 2.8.6.0 recovery thinking that would do BigPart, flashed the 4.4.4. Everest ROM and it would just hang on the TeamEOS startup animation. I then went back and flashed the 2.6 recovery and the BigPart addition and then it went fine. The SIM card slot is recognised but I don't have a standard size SIM I can test with since all my phones now use micro or nano SIMs and I don't have an adapter.
[Xoom Android Development] TouchPro2_PRO:
Can someone tell me the difference between the wingray, stringray, and everest roms? Which one should I use as a beginner?
[Xoom Android Development] shpitz461:
It's not a matter of 'user level', each is its own device model. So depending on the model (hardware) you got, you need to flash the appropriate rom.

Stingray and Wingray are interchangeable (if you have the LTE version and you flash Wingray, you lose data, but wifi always works).

Wingray = Wifi only

Stingray = LTE

Stingray_CDMA = 3G (before the 4G/LTE upgrade)

Everest = 3G Europe (GSM?)
[Xoom Android Development] lchiu7:
I actually both Wingray and Everest models (this is GSM) and applied different ROMS to both to get the updates. That being said, I haven't tried putting in a SIM card in the Everest model since I never take it out of the house. I presume the SIM card will work as there was no mention of loss of cellular functionality with this ROM.
[Xoom Android Development] meganukebmp:
Hello I'm thinking of flashing this. How good is performance compared to stock and the JB build?
[Xoom Android Development] realjumy:
More than performance, you should consider features provided and security patches.

The performance is not going to be as good as Honeycomb, and it uses to be laggy sometimes, but is worthy to install and use.
[Xoom Android Development] meganukebmp:
Yeah. Flashed both this and EOS 3. Thinking of staying on EOS 3 because it seems to be more stable. Anyways thank you all for working on EOS and bringing back life to this device. Still holding on strong 5 years after release.
[Xoom Android Development] bigrushdog:
Just as a reminder, this build is no longer officially supported. I highly recommend someone clone our kk4.4 branch and pick up where we left off. I'm keeping this thread open for informational purposes. If someone steps up and carries the torch I'll forward folks to that thread and close this one.
[Xoom Android Development] realjumy:
Hi man.

I will be more than happy of doing that, but I'll need some guidance. Do you think it will be possible for you to bring me some help to start doing this stuff?

Cheers.
[Xoom Android Development] matt4321:
I can probably give you a little bit of guidance with this.

My only concern about all this is that 4.4 is dead now, no development for like a year. I've got enough know how to be build this from source, make a few tweaks and cherry pick some features. But realistically I'm not skilled enough to give us fresh new features. This is why I haven't bothered doing it myself. I don't see much point just syncing and building when nothing is going on upstream.

Having said that, I don't know if [MENTION=697814]realjumy[/MENTION] is a programmer. I can help setup build environment and what needs to be done if you know where you're taking this.
[Xoom Android Development] shpitz461:
Matt, I don't think we care about new features, just want a reliable and stable platform :)

To this day, I have both CM and OMNI freeze on me randomly, once every few days.
[Xoom Android Development] matt4321:
I'm just not sold that syncing and building will do anything for us. The lastest EOS build would be 99.99% the same as one if I built it now from source because nothing upstream has changed. That includes stability and reliability enhancements.

Going forward, if we were to do this we need someone who knows what they're doing with the programming side, even if it's just to add stability. I've already reached my limit, I'd be very bad at that and not experienced. We need someone who would.

Sadly, I think the xoom is dead in terms of a stable and up to date ROM.

But heck, this is xda, I'll still get involved and help others with what I know to whoever wants it
[Xoom Android Development] shpitz461:
I agree.

We need to get Schischu to stop messing around with Samsung devices and focus his attention to the XOOM :P
[Xoom Android Development] realjumy:
Yeah man, I'm a programmer, but I'm usually extremely busy. My main intention is to give at least a stable version for people who want to keep their Xoom alive. I have some ideas of features I want to bring to Xoom (and as far as I know they should not be too difficult to implement), so I guess that will keep people's interest for a while if they understand that the time I can spend for this is limited.
[Xoom Android Development] matt4321:
[MENTION=470268]bigrushdog[/MENTION]

is 'repo init -u git://github.com/teameos/manifest.git -b kk4.4 -g all,-notdefault,wingray,moto' enough to make this buildable?

I recall Schischu had forked omni and cm framework stuff to make it Xoom specific. does teameos sources have the needed amendments to build this and have it at the same stage as the latest build?
[Xoom Android Development] bigrushdog:
That should do the trick. I left that branch proper. After you sync...

source build/envsetup.sh

lunch full_wingray-userdebug

make -j8 otapackage

For the most part you're gonna be back porting features. Definitely a worthy goal. Lots of win upstream.
[Xoom Android Development] shpitz461:
What is the BRD playing with these days? :)
[Xoom Android Development] pkelly517:
Wow!

This thread is on fire!
[Xoom Android Development] matt4321:
sweet! I didn't see vendor blobs on eos github.

Did you use schischus ones?

https://github.com/Schischu/android_vendor_nvidia_wingray

https://github.com/Schischu/android_vendor_broadcom_wingray

https://github.com/Schischu/android_vendor_moto_wingray

though I only see 4.3 and 5.1 branches
[Xoom Android Development] realjumy:
I tried "repo init -u git://github.com/teameos/manifest.git -b kk4.4 -g all,-notdefault,wingray,moto" and during the fetching I receive the error :

"Fetching projects: 4% (19/465) Fetching project hardware_atheros_wlan

fatal: remote error:

Repository not found.

"

And during the sync:

"remote: Total 1 (delta 0), reused 1 (delta 0)

From https://android.googlesource.com/pla...xternal/mesa3d

* [new tag] android-6.0.0_r6 -> android-6.0.0_r6

Fetching projects: 9% (42/465)

error: Exited sync due to fetch errors"
[Xoom Android Development] realjumy:
Hey [MENTION=470268]bigrushdog[/MENTION], we are having problems syncing here, more specifically regarding the wlan and audio repositories because they have been removed from eos Github.

Fetching projects: 12% (56/465) error: Cannot fetch hardware_samsung_slsi_exynos5
error: Cannot fetch hardware_atheros_wlan
Fetching project platform/external/libpcap
Fetching projects: 12% (56/465) error: Cannot fetch hardware_samsung_slsi_exynos5
error: Cannot fetch hardware_qcom_audio-cm_aosp
error: Cannot fetch packages_apps_EOSWallpapers
error: Exited sync due to fetch errors
error: Cannot fetch hardware_atheros_wlan
Fetching project platform/external/libpcap
Fetching projects: 12% (56/465) error: Cannot fetch hardware_samsung_slsi_exynos5
error: Cannot fetch hardware_qcom_audio-cm_aosp
error: Cannot fetch packages_apps_EOSWallpapers

error: Exited sync due to fetch errors

As [MENTION=4393511]matt4321[/MENTION] suggests, maybe the Atheros is not needed because we use Broadcom, but the audio can be a problem. Can you please give us a hand with this, please?

Thanks!
[Xoom Android Development] bigrushdog:
Guys! How about remove the offending entries from the manifest then sync? It's been over a year since I touched that repo and I'm not going back. I'll give some guidance here and there but you guys own this
[Xoom Android Development] matt4321:
that was the plan (fork and remove) but we wanted to check if the atheros and audio-cm stuff was important to the xoom.

if we don't need it then we'll go ahead with forking and removing the packages
[Xoom Android Development] shidum:
Hello, I al running 4 but I'd like to go back to 3, which tutorial shall I follow? Thanks

Enviado desde mi Xoom 3G mediante Tapatalk
[Xoom Android Development] meganukebmp:
Follow this guide and undo bigpart

http://xdaforums.com/showthread.php?t=2669457

booting the non bigpart recovery took about 20 minutes here. Screen might go dark. Just click any hardware button and it will light up again.

Then just wipe > flash EOS3 > flash gapps > done

If you do not return to normal partitions you will bootloop. Already happened to me.
[Xoom Android Development] ahmed007:
Anyone has files for 3 pls share the links thanks guys
[Xoom Android Development] robocuff:
Are you wanting EOS 3.0? If so, I have it. Can upload it to my dropbox if you'd like.
[Xoom Android Development] ahmed007:
yes pls i am looking for eos 3 for wingray can you pls upload it if you mind mind cheers
[Xoom Android Development] robocuff:
OK, here's a link to the rom. EOS-wingray-3.0.zip Md5 checksum is 93440e0398d55928e908baab3be01d3a

You'll also need the gapps. I believe these are the correct ones. It's been a while but on my computer they are dated the same as the rom so I have to assume they are the correct ones. Pretty sure anyway. gapps-jb-20120802-eos-signed.zip Md5 is d16e90373d941ca9dc801a519ed0b2d3
[Xoom Android Development] ahmed007:
thanks man
[Xoom Android Development] robocuff:
You're welcome :)
[Xoom Android Development] moeburn:
I'm trying to download this ROM for my Xoom, but the download link doesn't appear to have any actual downloads on it. I clicked on the "wingray" folder and it just says "0 objects in this folder, 0 B total."
[Xoom Android Development] pots22:
Mode ART dont work
[Xoom Android Development] Geeba:
Yeah just tried as well... same no files... :(
[Xoom Android Development] bigrushdog:
I've been posting for months for folks to get involved and take over. Nobody here can even cook a build and post up? I'm done. Thread closed.
[Xoom Android Development] DrGreem:
Worked perfectly, thanks a lot!
[Xoom Android Development] logitechor:
The developers and the Xoom continue to amaze me. I have tried to resolve a couple of issues around Amazon. So far unable but I have other devices.
[Xoom Android Development] tnfsmith:
Bravo to see TeamEOS back with news winds up. We till loyal Xoom and you guys too. Many happy if everest ready for test. I am on 170 build, people who drive on 4.4.3 give the full change log to help us rest new Era android on old Xoomer. Thanks
[Xoom Android Development] Jacklad:
So far....

All is pretty great - a couple of things, which I believe others have mentioned - still get the "unknown SIM' message, Chrome browser crashes, Google + & Photos crash when opening a pic or video - that's what I've got so far - great to see the continued support and updates - thanks so much for keeping us serial flashers happy!
[Xoom Android Development] Prack:
So glad to see EOS back in action. Xoom doesn't feel right without an EOS ROM on it. I'll be flashing this sometime this weekend :)
[Xoom Android Development] elton.de.nascimento:
I have the same problem.
[Xoom Android Development] taylorinnov:
This SIM Card is from an unknown source.

Yes, I get ""This SIM Card is from an unknown source." on my notifications panel... The kicker is that my mobile data seems to work fine. If this warning just simply wasn't there or could be dismissed it would be great!

FYI, I have Verizon 4G on my Xoom, and it's a newer miniSIM in an adapter. It goes back and forth between the Xoom and my Nexus 7 for testing right now. Assuming I can get all the kinks worked out of this ROM though, I'll be adding the Xoom to my Verizon account permanently.
[Xoom Android Development] Alxoom33:
4.4.4.... http://xdaforums.com/showthread.php?p=53532886

Wow really 4.4.4 already?

http://m.androidcentral.com/google-posts-android-444-images-many-nexus-devices

Change Log: http://xdaforums.com/showthread.php?p=53535403
[Xoom Android Development] drewski_1:
and BRD has already merged it! :laugh: :good:
[Xoom Android Development] Alxoom33:
Wow, really? Not in a current nightly yet?
[Xoom Android Development] bigrushdog:
Alrighty! Feels like we're starting to get some traction now! 444 is just some openssl nonsense they should have put in 443 ugh. Couple thoughts. I may just bring in Nova free as the default launcher. I messaged [MENTION=2371134]Schischu[/MENTION] about wallpaper picker so maybe I can get some help there. Either way, Nova pwns. I haven't had much time for xoom testing as I got a shiny new M8. Get me some logs on the Amazon app and other crashes. For stingray, I'm gonna do some experimenting. For starters, delete MotoSimUiHelper app from system app and reboot. Then see if lte works and the nag notification is gone.
[Xoom Android Development] bigrushdog:
Oh. I guess it's time to bring in everest and stingray_cdma too.
[Xoom Android Development] dsbnz:
[MENTION=507808]BRD[/MENTION]..

Back on EOS, nice work !

Question.. I don't know if its a Chrome thing, or AOSP thing, but Chrome seems to freeze, or hog memory (not sure) since v34. Chrome only appears to work reasonably well on v33. I've tried it on EOS and Omni, with same experience.. Who is the right person/people to approach?

Cheers
[Xoom Android Development] emaxxim:
Yeah bigrushdog, I have the Everest version I need TeamEOS ROM!
[Xoom Android Development] bigrushdog:
Chrome is a memory hog all around. Here's the deal. As we all know, Google drop support of non neon devices some time ago. The entire gapps package today is built on the assumption that the target device supports neon instructions. I MAY be able to get non neon support into the chromium_org frameworks. I'm not optimistic as that is a behemoth of a software suite. Half of the aosp compile is just building chromium. As time goes on, gapps apps that depend on neon will become unavailable to xoom users. Sad but true.

I hear Ya. I think we're stable enough to bring you guys in.
[Xoom Android Development] Alxoom33:
I like that plan! Nova is my default launcher :) it's great and has tremendous customizations and backup. I use goggle now and epic launchers as backups.
[Xoom Android Development] drewski_1:
6/19 is 4.4.4, but, as BRD said, pretty minor. I read the OTA was just 2.5MB
[Xoom Android Development] elton.de.nascimento:
How to install this?its stable?
[Xoom Android Development] no*boundaries:
Everest Rom MZ601

Happy to test if and when needed, looking forward to EOS again on the Xoom, With Gurus like all of you , you just cant kill the xoom off !!!! thanks to all involved
[Xoom Android Development] webeougher:
I appreciate all of your hard work, BRD, but if I could respectfully ask that you not simply switch to Nova, it'd be greatly appreciated. Reason being, these guys can always install Nova from the Play Store and have it working, but if you just give up on Google Experience/Google Now launcher, those of us who prefer to avoid third-party whenever possible don't have that option.

On the bright side, I followed your request, deleted MotoSimUIHelper.apk and rebooted. No persistent SIM notification, and the following screenshots should speak for themselves. The first is from my Moto X and the second is from my Xoom.

Moto X

Xoom

Excellent work, man!

PS - That's still the 6/12 Xoom build. I'll update to the latest today and edit this post.
[Xoom Android Development] kmcrane:
Google experience launcher is in the play store. And you can freeze or disable Nova. I disable the trebuchet now.

Sent from my XDA Free mobile app
[Xoom Android Development] REHolt218:
Just stumbled onto this thread this morning. I have read the whole thing and am pumped. This is great!!

I had retired my Xoom but have really missed Eos and all the great features. I WILL BE giving this a try. Unfortunately I have not yet gone to "big-part" on my Xoom so have some research and work to do.

Welcome back Team EOS.
[Xoom Android Development] bigrushdog:
http://jenkins.teameos.org/

Brought up and added to jobs. She's queued up!

Nova paid has taken care of me on all my devices for about a year now. I'm hooked.

Get big-parted and hit the OP for details. We have some issues still but it's stable.

Thanks, Xoom gives me gray hairs. So thanks for the kind words

You don't know how beautiful it is seeing the little "4g" up in the statusbar. I merged the commit removing MotoSimUiHelper.apk last night. Good deal!

I tend to agree with you adding Nova as a replacement for Trebuchet or Launcher3 or whatever. But I'm in a bind here. I see the WallpaperPicker fail. It's EGL. And I don't know how to fix it. YET. So in the meantime I have the default launcher crashing when guys go to change the wallpaper.

this is true too. :confused::confused::confused::confused: I'm so perplexed! :p:highfive::cool:

Get back in the game! Get your big-part proper and give it a go.
[Xoom Android Development] kmcrane:
[MENTION=470268]bigrushdog[/MENTION] how do I get the Amazon app store log you need? Or what should I Google to research it. ?
[Xoom Android Development] bigrushdog:
The easiest way is to grab CatLog from the market, run it, make your app crash, go back to CatLog and email me the log or attach it here. If need be, check my profile for email.
[Xoom Android Development] kmcrane:
I'll do it tonight. Also I see the new grouper thread, loving EOS back!
[Xoom Android Development] phixom:
Hi,

Will there be an everest release?
[Xoom Android Development] drewski_1:
see last page. post #112
[Xoom Android Development] iruiz2:
In plain english...

Edit: Damm, I was late!
[Xoom Android Development] luismateos:
CDMA

any updates on stingray cdma?
[Xoom Android Development] no*boundaries:
Everest not up

I updated the ROM to # 1 (Excellent on WiFi, but everest radio no go, sorry to say.

Misleading title, should be NOT working...
[Xoom Android Development] drewski_1:
i've had a couple of SOD's (for the uninitiated, SOD = Sleep of Death => i have blank screen, notification light flashing, can't wake up Xoom).

BRD, is there a way to log this / help diagnose?
[Xoom Android Development] kmcrane:
I have sent you a log by email.

Thanks

Sent from my XDA Free mobile app
[Xoom Android Development] bigrushdog:
I got it, thanks. It's the exact same error we're getting with wallpaper picker. It's not getting egl config properly. The strange thing is i brought in some legacy support commits into fw/native that should have addressed this issue, but it didn't work. I've since reverted those commits as they were causing other issues with other devices. I may have to take a fresh look at those.

Fresh everest builds up

http://downloads.codefi.re/teameos/nightlies/MOTOROLA/everest

I'll bring up stingray_cdma tonight or tomorrow.
[Xoom Android Development] colklink14:
Couple of missing things??

Hey EOS,

Cannot thank you enough for the great work allowing our Xooms some life.

I noticed a couple of things missing on the developers page,

No advance boot,

Performance options.

If they are somewhere else just let me know and accept my apologies.

Thanks in advance,
[Xoom Android Development] bbshopper:
Amazon Store Crash...

I've had this problem too. My temporary fix has been to load an early copy of the Appstore (version 2.1), which at least works! When I update to the latest store, it crashed, so I left it on the old Appstore and loaded my apps.... Looking forward to a fix though....
[Xoom Android Development] colklink14:
Edit: Found the advanced boot

I would like to have it run at 1504MHZ as before, are there any kernals we can use to achieve that, that you endorse??
[Xoom Android Development] webeougher:
I realize that the Google Now launcher is in the Play Store, but if BRD gives up on it, then it still won't work properly even if I install it from there. Does that better illustrate my point?

---------- Post added at 09:33 AM ---------- Previous post was at 09:28 AM ----------

Would it help with the Wallpaper picker issue if I captured a log on this rom of me attempting to change the wallpaper and one on one of Schizu's 4.4 roms successfully changing the wallpaper? I'm not sure if that'd be enough to point you in the right direction in his git or not.
[Xoom Android Development] bigrushdog:
Grab any kernel mod app from play store. I have an old app i wrote that works too. It's a bit rusty, but I may bring it out of retirement for Xoom. Only for xoom though. It works, but it's too rusty for newer devices.

Ya, grab some logs and compare. I'll keep chasing down the derp. I'm sure the solution is hidden right in front of me.
[Xoom Android Development] bigrushdog:
Ok guys, play with this a bit

https://www.dropbox.com/s/u7vrrtui8z5n1se/KernelControls.apk

Install as a user app. give it a go, see how she runs. I haven't touched it in a while. I can tell by the code :rolleyes:

But i bet it works :o
[Xoom Android Development] drewski_1:
Included Elemental-X can overclock. I use Trickster Mod
[Xoom Android Development] bigrushdog:
You can overclock with this too. It's nothing compared to trickster but I wrote it. It's mine. It's simple. It works.
[Xoom Android Development] andPS2:
unfortunately the settings dont seem to be saved on boot neither on power off and power on nor on power menu reboot

the other tools like trickster mod at least seem to save the settings that way

however all the other tools i tested dont save the settings when rebooting with rebooter

can u put back the option into the rom ?

cause on omni rom and cm11 those settings survive all the possible reboots