yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] stlsaint:
Thanks for reply and yes I missed the one line warning but saw it post brick when I went back rereading. Since your handy with links you wouldnt happen to have one about getting into the device from laptop would ya?? I havent had to hook it up to a pc since first root/custom flashing.

Now I have to somehoe unbirck which the first link you posted doesnt show. I now know what to do should I be able to get into device.
[Xoom Android Development] runandhide05:
Put an old Rom that doesn't need bigpart on your sd card. Then boot straight into recovery by resetting the tablet by pressing the power and volume up. Then press the volume down three seconds after you see the red M . This will boot you into recovery. Then flash the Rom and you can then reboot into android then follow the steps to preform the bigpart repatriation.

For some visual aid Recovery: http://youtu.be/koxgbdQuzOQ

sent from space
[Xoom Android Development] stlsaint:
Much thanks. I was trying to get into recovery earlier but all that kept popping up was message stating "starting fast boot protocol". I will keep tinkering till I get it though.
[Xoom Android Development] kuroguy:
The devs are doing an awesome job with this rom. Until they get the charging light fixed up, you can manually disable it by opening terminal emulator and typing the following...

Superuser will pop up asking for permission. Grant it and then type...

I'm not sure if this will survive a reboot so you may need to do it after each reboot, but it does the trick while the devs tend to their real lives.

EDIT: survives Reboot.
[Xoom Android Development] shpitz461:
The key is, like RnH said, is to wait 3 seconds after you see the red M, then press vol-down. It will give you a "menu" that says --> Recovery.

Down-vol to change selection, Up-Vol to 'enter'.
[Xoom Android Development] bigrushdog:
I gotta make custom release tools so flash fails if you don't have bigpart. [MENTION=2371134]Schischu[/MENTION] showed me the commit. Just gotta make it happen.

I've lagged on charge light. Too much work doing platform, features, and devices.

As you may have seen, we have fresh boot animation! Yippee! But we also have Eos Wallpapers too. And they are slick! Also look for a new assignable action called Last App. I'm sure you'll find it fun. More win in the pipeline.
[Xoom Android Development] m3x1cant7863:
i keep getitng failed installation. i followed bigpart steps and everything seems to be ok. i should just be able to install the latest update?
[Xoom Android Development] realjumy:
Oh, man, kudos for that "last app" action.

The only thing I miss now is a multiwindows option... I did it time ago with Xposed but it was crappy...

Mate, congratulations for this ROM. It's awesome.
[Xoom Android Development] shpitz461:
Latest TWRP? Attach recovery log, your post is useless unless you provide logs and detail...
[Xoom Android Development] m3x1cant7863:
thanks for the reply. it was late last night for me so i think i posted in my sleep lol. but i cant seem to get any rom to work. i tried omni, and this rom. so after installing the latest twrp version both roms stay at the rom boot screen. it stayed like that all night. also twrp is unable to mount data and cache. so i'm going to start all over from scratch and see what happens. again thanks for the reply.
[Xoom Android Development] realjumy:
Be careful because there is 2 different TWRP versions, one of them is the Big Part version (which is needed for this ROM) and the other one is the plain version.

Maybe you need to take a look to this:

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

BigPart Repartition Upgrade and Resource Center

Good luck.
[Xoom Android Development] hochoch:
Latest build running great! Wallpapers, last app and new boot animation are all sweet!!!

So now request time ? any chance of getting cm11/kitkat theme support? Only cm10 themes are recognized by the chooser currently.
[Xoom Android Development] m3x1cant7863:
Thanks. I followed this tutorial and i still am getting these errors. unable to mount data and cache. also the eos boot screen stays spinning in the middle of the screen. gonna try and start from stock and work my way thru the process again
[Xoom Android Development] Jul0054:
Try a stock rom first then things to big part
[Xoom Android Development] bernac:
Lost!

Hi guys,

I'm getting lost :/. I have a wingray that was running Omni 4.4 Bigpart and I wanted to swithc to EOS. I just downloaded the last image (EOS-full_wingray-20140824.223028.zip), and I just can't get it working. I flashed this ROM and as I was saying it's not booting. I understood that I needed to flash Eos 4 BigPart Wingray Boot Image witch I did. But still it doesn't work.

So my question is, does this ROM needs Bigpart?

Sorry for the noob question!

BerNaC
[Xoom Android Development] WarLion:
Did you do all the steps?

Going to EOS4.4.x from a rom < 4.4.x:

Backup everything !

Go to recovery

Make a full wipe / factory reset

format /system

Flash the rom

Flash gapps

Reboot

Make sure your gapp is correct I'm using the pa gapps modular mini for 4.4.4
[Xoom Android Development] bernac:
Yep I did all that just haven't flashed the GAPPS. I just reflash OMNI and it's booting fine :(. Really don't get it. Gonna try again...
[Xoom Android Development] shpitz461:
Also, provide the recovery log, saying 'it doesn't work' doesn't help @ all...
[Xoom Android Development] bernac:
Well it says :

Installing '/sdcard/EIS-full_wingray-201400824.....

Built at: 2014-08....

script succeeded: result was (/system]

Updatin partition details...

Successful.

But still it's not booting it stays stuck on the moto logo.

I pretty sure it's my fault I might miss something.

I'm going to redownload the image file...

Thx
[Xoom Android Development] drewski_1:
i haven't tried 8/24 yet, but don't flash the EOS4 Boot Image with this ROM

that was only needed before BigPart specific ROMs were built. this ROM has a BigPart compatible kernel included.
[Xoom Android Development] stingbandel:
Remove your microsd and reboot. If it works then u have the same problem like me. The build no 20 has this problem on me... Try ro clean the microsd
[Xoom Android Development] realjumy:
Just to clarify. Did you used the correct wipes?

Also, if you are coming from a NON BIG PART ROM, you need to follow the steps here: http://xdaforums.com/showthread.php?t=2506997 BUT don't flash any kernel or boot image if the ROM you are flashing is Big Part Ready.
[Xoom Android Development] bernac:
Lost!

Hi,

Yes I did the correct wipe, and i'm coming from Omni BigPart, so my Xoom is already Bigparted. Then it should have worked. I'll try again tonight with removing my SDcard and if that doesn't working I'll try to flash with an older release.

Cheers,

BerNaC
[Xoom Android Development] brewer75:
FYI, I just noticed there is a new 8/27/14 stingray_cdma build. :good:
[Xoom Android Development] bernac:
Hi guys,

Here is my log :

http://dl.free.fr/rGclKKeYt

If you have any idea.

Thx

BerNaC

---------- Post added at 08:35 PM ---------- Previous post was at 08:24 PM ----------

Ok just downloaded EOS-full_wingray-20140824.223028.zip (the version just before) and it's booting fine....

BerNaC
[Xoom Android Development] runandhide05:
English hosting page would be helpful as chrome won't or can't translate

sent from space
[Xoom Android Development] eckka:
Tried this on the latest build - 27-8-14 - and it doesn't work. I didn't need this on the 24-8-14 build, in this version the setting for battery light in the display section worked. I guess something happened in the new version.

Thanks for the amazing work. The tablet is a dream to use.
[Xoom Android Development] kuroguy:
You've done it wrong. I'm using it on the 8/27 build and it's worked on the last 4 builds (didn't try it before that).
[Xoom Android Development] shidum:
Good job guys!

Only thing to mention, flashing bootloader zip corrupted my xoom (everest) and I had to repeat the process twice.

Thanks
[Xoom Android Development] father1e:
I tried to load this latest stingray_cdma build on my Verizon 3G Xoom and it just sits in the Motorola Dual-Core logo screen. Seems there's still a problem for the CDMA build. I had CM.11 for Xoom BigPart running and then did advanced wipe to wipe everything except SDCard. I'm using TWRP 2.6.3 BigPart recovery. Then did install of latest stingray_cdma build.

Willing to work with someone to try and get this working
[Xoom Android Development] bigrushdog:
I don't have stingray cdma and I have no clue what the problem is. The device tree is on our github and review link is on the OP. I'm killing the build until someone pushes a fix to review. Sorry guys. I can only do so much
[Xoom Android Development] widekaze:
Feel disapointed the rom not support XOOM HDMI out... I'm using 4.2.2. in previous but not i UPGRADE my rom to 4.4.4, find out that rom not support HDMI out...

Development, do you concider add back this function in future? (it will be very helpful for Video output by this device)

Thank you.
[Xoom Android Development] chykal:
HDMI out works for me on this rom.
[Xoom Android Development] widekaze:
that was wired.... my tv show the video was not supported....
[Xoom Android Development] Obsy:
Your TV is Full HD or just HD ready?
[Xoom Android Development] widekaze:
full Hd, it was difference?
[Xoom Android Development] bigrushdog:
Drm protected content won't stream over hdmi or screen cast. That's Android API. Like Netflix and HBO Go are protected and won't work.
[Xoom Android Development] chykal:
I use HDMI out for streaming Google Play TV & Movies and streaming Amazon shows.
[Xoom Android Development] taninos:
Is this an API's limitation for Android 4.4.x? I wonder it because on a rooted android 4.3.1 both work, I mean, Netflix and HBO Go.

Best.
[Xoom Android Development] bigrushdog:
It's not limitation. That is what drm does. The drm layer allows you to view drm protected content. The app decides if you can pipe content to other frame buffers. In the case of Netflix and HBO Go and Hulu, you can not.
[Xoom Android Development] tnfsmith:
Just bug report here. Apps force close every I chose correct words from hint menu original keyboard. I am in English input and system too. Who guys like me?

Sent from Tapatalk MZ601 - TeamEOS 4.4.4 Kitkat nightlies
[Xoom Android Development] shpitz461:
My Stingray still freezes while docked on occasion. last_kmsg attached.
[Xoom Android Development] ahmed007:
multirom

guys is this possible with our xoom would love to run 2 roms :cyclops:

http://xdaforums.com/moto-g/development/mod-multirom-v27-testing-t2852897?__utma=248941774.2011678790.1409547364.1409758227.1409784695.8&__utmb=248941774.2.10.1409784695&__utmc=248941774&__utmx=-&__utmz=248941774.1409547364.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)&__utmv=-&__utmk=194269102
[Xoom Android Development] Prack:
Few minor issues I'm having. Have tried full wipes and can't seem to get rid of them:

*Boot animation shows 4 tiny colored dots right before the logo starts spinning.

*Booting up in media dock makes a loud pop sound.

*Netflix playback crashes after about 10 minutes of watching, not really sure why this is happening. Like I said above I've full wiped, reinstalled netflix etc and nothing fixes it.
[Xoom Android Development] shpitz461:
Maybe provide a logcat so the devs can have a look? I've booted up while in the media dock many times, never heard anything like that. At what point exactly does it happen?
[Xoom Android Development] Prack:
Yeah when I get home I'll grab one just wanted to post and see if anyone else is experiencing this. It happens right out of the gate. First thing I hear is a pop sounds, then I see the 3-4 animation dots, then the animation.
[Xoom Android Development] akazerotime:
The Motorola HD Dock has always POP'ed when it was booting on the device for me. Bother-in-laws does the same thing too. It's the dock getting power. I have always heard this going back to Honeycomb. Sometimes it's loud and sometimes its not. Here is the fix: take the XOOM off the dock, reboot it, wait until its at the lock screen and put it back on the dock. No sound. Hope this helps. :D
[Xoom Android Development] Prack:
Well I'm in rough shape now. I tried to wipe it in TWRP 2.7.1.0 using the format, typed yes, rebooted. Tried to wipe things and it can't mount data or internal. Tried to reinstall the ROM and it comes up to the screen that says my tablet encryption is unsuccessful. It then tells me I can reboot to format and it goes back into TWRP and does the format again but I see it failing to mount data over and over.

I connected it to my PC and tried to do the fastboot oem unlock. It was successful and boots right back into TWRP. Even now at this point everything I do in TWRP says I'm unable to mount data. Did this some how lose bigpart? I just tried to reflash TWRP 2.7.10 and it still says unable to mounc cache, data and internal storage.
[Xoom Android Development] runandhide05:
Reflash older version of bigpart twrp I pulled twrp 2.7.x because people how format then don't set the format file type back to ext4 can not mount data or cache. If you wish to use it that's fine but you have to reset the format type to ext4 and NOT f2fs

sent from space
[Xoom Android Development] Alxoom33:
How are you feeling my friend? Better I hope?
[Xoom Android Development] Prack:
Flashed 2.6.3.0 big part. Went to wipe and can't mount dalvik, cache, data or internal sd.

---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------

Yes this is probably my problem. How do i set it back to ext4?

---------- Post added at 09:15 PM ---------- Previous post was at 08:59 PM ----------

Wait I think I see it now. When I do format on 2.6.3.0 I can see it formatting to ext4. I get it now. I think I might be up and running again here in a minute. Thank you for the help.
[Xoom Android Development] runandhide05:
seen better days...long and painful recovery ahead. Thanks for the support guys. It's nice.

I presume all is well now?

sent from space
[Xoom Android Development] fvlserevere:
...

[/color]

+1
[Xoom Android Development] Prack:
Yes rom is up and running again. Thank you for the info.
[Xoom Android Development] elton.de.nascimento:
Anybody here have a problem with xoom doesnt wake up after night? I dont know how to solve this. I use Kernel Control APP att min 456 and max 1504 on demand. Tks guys
[Xoom Android Development] ahmed007:
I am having the same problem wake up at morning and it won't wake up running the latest bold
[Xoom Android Development] kuroguy:
It's happened twice to me. i usually find out when i wake up completely refreshed but also late for work because my xoom is also my alarm clock.
[Xoom Android Development] Borg1of3:
same problem Mate, do not know what to do.... just switch on again and again... sorry I cold not help
[Xoom Android Development] elton.de.nascimento:
I can't use my Xoom for alarm. Because this problem. I change the minimum frequency and today (morning) freeze again. Take a look in this picture. The tablet battery was in 100% and after freeze the battery stay with 80%.
[Xoom Android Development] drewski_1:
My SOD issue was solved going to 312 MHz min, but you're already over that.

Maybe try a different governor? I'm using Interactive / Deadline
[Xoom Android Development] elton.de.nascimento:
[MENTION=4752026]drewski_1[/MENTION] I will try change governor to interactive

Tks
[Xoom Android Development] cctv35:
MZ600 CDMA 3G flash the wingray version no problem, flash the EOS-full_stingray_cdma-20140903.112302.zip However I always get stuck at the Motorola boot screen.:crying:
[Xoom Android Development] ahmed007:
Settings fc when I press the lock screen setting in the settings menu
[Xoom Android Development] shpitz461:
Anyone else having video issues with YouTube? I play a video and the screen is blank, just audio. Turns out if I reduce the resolution to 480p or less it plays fine. It's as if the video is rendered in software and the tablet doesn't have enough power for 720p rendering. This is also happening on YouTube.com in Chrome.
[Xoom Android Development] slow1234:
SODs and stock browser quick controls flickering

First off - much thanks to the TeamEOS folks - you have kept my Xoom alive and I really appreciate it. You were the first to 4.4.4 for the Xoom and you continue to provide excellent support!

Yep, I was having the same issue with sometimes not waking up after a night in the speaker dock, as well as increased SODs even when off the dock. These SODs issues combined with my Xoom showing increased lag over the last few weeks prompted me to go back to OmniROM over the weekend. Things are functioning much more smoothly now and I do not seem to be having any SODs. The improved smoothness could have just been an artefact of a factory reset prior to Omni install though.

One other thing to add - in the TeamEOS ROM, the stock browser was working beautifully with quick controls. However, upon install of OmniROM, the stock browser navigation bar kept flickering and not disappearing. So, I pulled the browser.apk from the 20140824 TeamEOS ROM zip fill and installed it on OmniROM. It seems that the flickering has gone away and quick controls are functioning properly. There must be some differences between the Omni and EOS stock browser apks.

Cheers,

slow
[Xoom Android Development] elton.de.nascimento:
Logcat Xoom mz604

hello . follow my logcat e dmesg. I have many SOD´s

can anybody help me how to solve this?

tks
[Xoom Android Development] Mjamocha:
Lurking ...... ;)

Nice to see that Xoom is alive and well.
[Xoom Android Development] brewer75:
I too, am having the problem with no video when i try to look at anything on YouTube. Nice sound but it is kind of like looking at the radio! On another note, this may be a stupid question, but what is the Falcon build that is showing up in the list of nightly builds now?:confused:
[Xoom Android Development] runandhide05:
Falcon is the code name for the Motorola G

sent from space
[Xoom Android Development] Jul0054:
Anyone have a mirror link. My downloadS stop about 95 % with different devices and Internet connexions. Plz
[Xoom Android Development] geko1966:
EOS Just Rocks!!

ThanX BIG time for making it possible to make me feel like i have a new Xoom tablet, everytime i update to a new android version

Your guys are awesome!

From the bottom of ma Drokking Android heard THANK YOU!:good::good::good::good::highfive:
[Xoom Android Development] SoCalArm:
Alright this is a awesome ROM update. But one problem here.

When going to settings and Lockscreen it crashes and says: Unfortunately settings has stopped.:crying: :eek:
[Xoom Android Development] Obsy:
You will need TWRP the bigPart one....
[Xoom Android Development] kmcrane:
I tried flashing the wingray 6-8 but that failed for me. Used PA micro modular gapps.
[Xoom Android Development] bigrushdog:
Try again. I think some builds got added before the Skia fix got merged. The 6-9 build should be proper.
[Xoom Android Development] Cubanluke88:
thanks
[Xoom Android Development] Obsy:
Deeds not words! :p

[MENTION=470268]bigrushdog[/MENTION] You said in first post at installations tips to flash optional kernel... so... what kernel do you recommend? ART is working with your ROM?
[Xoom Android Development] bigrushdog:
I haven't got that far in the xoom kernel game this cycle so I don't know. For now I'm including [MENTION=4684315]flar2[/MENTION] vanilla because it's strong and stable.

I haven't tried art on xoom. However, on my other builds it's flawless
[Xoom Android Development] cybgo:
Awesome rom

The rom works perfectly!!!!! Thank you so much :)) keep on the good work :good::good::good:
[Xoom Android Development] elton.de.nascimento:
Hello guys. I havê xoom with omni rom, but i would like go back to EOS. Its only follow the instructions on the first post? I havê bigpart on my xoom.

Tks
[Xoom Android Development] andPS2:
good to see TeamEOS back!

flashed the EOS-full_wingray-20140609.005601.zip

couple of issues i noticed:

coming from CM 11 bigpart 4.2.2 only wiping cache and dalvik and then gapps resulted in

beeing stuck at the X logo after reboot

wiped everything and then flashed image + gapps worked

couldnt change the wallpaper with standard launcher

trebuchet would always FC

installed nova launcher from playstore and then could change wallpaper

currently restoring my apps with titanium backup and testing everything

p.s. i am using these google apps

gapps-wingray-kk-20131223.zip (Note: TTS removed as it currently crashes)

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

p.p.s. [MENTION=470268]bigrushdog[/MENTION] there is a newer kernel version from flar 2.1 which omnirom uses

maybe that will help? this rom still uses 2.0 i think

i cant find the performance menu yet to overclock to 1400 mhz ?
[Xoom Android Development] pots22:
everest

I'm really looking forward to testing the Everest release :p
[Xoom Android Development] andPS2:
mmh not too many ppl posting here even though this is the first 4.3 image

omni and cm are still on 4.2 (the bigpart versions)

tested all my apps and no issues

OTA update doesnt work yet have to update manually update to EOS-full_wingray-20140610.005600.zip

worked

this seems to be stable and once the cpu speed option will allow us to overclock the slugginess will be gone

(i hope)
[Xoom Android Development] hochoch:
Great so far. Updated to today's nightly and installed elemental x 2.1. Running smooth, used trickstermod for OC and turned animations way down to .25.
[Xoom Android Development] andPS2:
thanks didnt know trickstermod running great now with 0.25 and 1400 mhz cpu

xposed + app opps working as well

pretty good job for such an early version ;) kudos

[MENTION=3353248]hochoch[/MENTION] are u using overclocked elementalx 2.1 or vanilla

which one is in the image elemental 2.0 gpu oc or vanilla?
[Xoom Android Development] hochoch:
I installed 2.1 overclocked, not vanilla (why not right?!?). Don't know about what one was included originally, but it was listed as 2.0+ and i think the plus sign means OC'd.
[Xoom Android Development] Alxoom33:
I just stumbled onto the thread. Awsome! ! ! I'm so excited to flash EOS again on my Xoom. ;) Donation sent.

Thank you BRD and team!

Link to 4.4.3 PA gapps

http://goo.im/devs/paranoidandroid/...Apps/pa_gapps-stock-4.4.3-20140608-signed.zip
[Xoom Android Development] bigrushdog:
Ok guys. Gonna need some help here. I'm finding it exceedingly difficult to get Stingray LTE up and running with a deactivated sim card. I need a motivated individual with an activated Stingray to do the following:

Flash the latest Eos Stingray build

Produce a radio log from boot

adb logcat -b radio > ~/Desktop/eos_xoom_radio_log

Produce a regular logcat from boot

adb logcat > ~/Desktop/eos_xoom_normal_log

Then i need someone to repeat the procedure with the latest CM nightly from [MENTION=2371134]Schischu[/MENTION]. I flashed the latest CM nightly and it was unable to bring up the LTE modem with this deactivated sim card. In other words, it left me in the exact same state my build does. You guys want some LTE? Get me some logs! Heck, could already work for all I know.

Let's get LTE up and running, then we can repeat the procedure for Everest. Then we can work on getting this build polished up some! But we gotta eat our vegetables and get the hardware proper first.
[Xoom Android Development] cybgo:
Hey I'm sorry, I have a dumb question. When u manually update with the newest eos rom, do u have to flash the kernel and G apps again?

Thanks!
[Xoom Android Development] bigrushdog:
Your kernel, yes. Gapps, no
[Xoom Android Development] Alxoom33:
I'm sorry. I didn't see a separate kernel in op. Link please. Thank you. ;)
[Xoom Android Development] bigrushdog:
I was trying to say if the user has a favorite kernel to flash separate from what's included. The Tegra2 platform isn't being developed anymore for the most part, so you probably won't find the super uber kernel out there. I may pull off a few tricks in time but don't expect any miracles.

I think I got LTE on stingray last night. Give the latest build a go and let me know. But yes. I still need those logs please.