yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] pots22:
update 172

I flash the 172 stay stuck on the logo Motorola

Restart on the recovery and flash the kernel 1.2 succesfull

reboot and stay block on the motorola Logo.:crying:

So it's not a kernel problem.

The boot.img ?

Its different from the 170.

To night for the fun i take the boot.img from the 170 put in the 172 and flash.

I tell you the result tomorrow :confused:
[Xoom Android Development] Hassan_Elyas:
Version 171 and 172, Both builds get stuck on boot!

back to 170! though i face some force closes of system UI but its fine.

any other users facing fc?
[Xoom Android Development] pots22:
nightly 172

So i flash the 172 with the boot.img of the 170 but the same result.(the same binary img)

I check all update from EOS4 for all stuff and i see EOS team stop all nightly activities the 05/07/2013.

Do you think they work on JB 4.3 for the lovely Xoom ?
[Xoom Android Development] parkentosh:
If you would read a few pages back you would know that EOS is discontinued and that bigrushdog is working on a new project for the Xoom. He also has a thread under "General".
[Xoom Android Development] realjumy:
PLEASE, before posting:

The last EOS 4 working version is the 170 >>>> http://goo.im/devs/teameos/roms/eos4/nightlies/umts_everest/EOS-umts_everest-20130617-170.zip

Test builds (feedbak, please) >>>> http://xdaforums.com/showthread.php?t=2372197

Thanks.
[Xoom Android Development] tnfsmith:
We should stop by on 170 build for stability 4.2.2 to avoid stuck hang on boot screen M logo by many complaints. New project by bigrushdog work on Android 4.3, we should concentration to help him test and report new bugs and improvement experience with the new cool stuff too. So that's all clear :)
[Xoom Android Development] peterkling:
I did the same mistake: flashing before reading. Coming from fantastic 170 to 172 - boot loops - returned to 170 from nandroid - ok - tried again (before reading) - boot loops, but now the nandroid of 170 won't work anymore!?!?!?!?! problems resoring /system?

is this a common problem?`

Flashing 170 now again and trying to nandroid resore afterwards...

Edit/Update: It doesn't boot anymore at all (it showed the M-sign when I was writng the last post). I charged the xoom the whole night.
[Xoom Android Development] realjumy:
A full wipe before flashing should make it work again. Try to download again the 170 to be sure that the .zip is not corrupted.
[Xoom Android Development] peterkling:
Thank you - it worked and you saved my Xoom. :angel: :good: But the (not corrupted, because MD5 is correct) 170-nandroid backup did not work to restore, so I had to work with my TitaniumBackus.
[Xoom Android Development] realjumy:
You're very welcome.

Update your recovery to the last version. I remember a bug in old versions of the recoveries having problems with the backups. *Maybe* then you can restore your backup. So the best is to update recovery, do a new backup, try to restore your previous backup and if you are not lucky, restore the backup done after updating recovery.

Remember to do a wipe before restoring a backup.

Good luck.
[Xoom Android Development] new-noob:
....ok, now I'm a bit worried about lack of updates, we stuck on 172 build and nothing since, can any1 say why?
[Xoom Android Development] matt4321:
Merging with codefirex, check the general section
[Xoom Android Development] bigrushdog:
As I previously mentioned, I don't have access to the teameos goo account, as well as control over servers. If I could delete the last 2 builds I would have. This is part of the reason we got a new project going. Come by general board and hang out a bit.
[Xoom Android Development] pippocannelunghe:
Simeone some post ago told that this project has been discontinued... :(
[Xoom Android Development] new-noob:
This if , well was, far best ROM for xoom, in my opinion anyway...

Smooth, fast, with USB support (had no problems copying large files over to usb disk)

Thank you bigrushdog for all your work! And please let us know once new projects build is ready to download! :)

Thank you!
[Xoom Android Development] peterkling:
This is a pitty! How come? Maybe you could put this info in the first post!?

I double that!
[Xoom Android Development] hawkstorm:
Maybe this thread should be closed? Just a suggestion.
[Xoom Android Development] matt4321:
If you had read the discussion thread in the general section, you'd see that these threads will be closed in the near future when new builds with the new project are complete
[Xoom Android Development] daniel_cassian:
If anybody still reads this i have problems with rom.

Installed TWRP 2.5.0 and ClockworkMod 5.0.2.8 Based -Rogue Touch Recovery v1.5.0-

Have ROM (172) + Gaps on device.

Install = Bootloop

Combo tried (every time bootloop): Flashed Rom - reboot; Rom - wipe cache - reboot, Rom - Gaps - reboot, Rom - Gaps - wipe - reboot

After every attempt factory reset+wipe caches
[Xoom Android Development] zaktell:
Build 170 is the last working one!

171 and 172 hang on Moto logo.

Cheers!
[Xoom Android Development] joho5:
Is umts the 3g or 4g version?

I have never had a clear answer on which rom to install, or radio if I still have the 3g version (never updated the hardware during the time period they were doing it).

any help would be appreciated.

thanks
[Xoom Android Development] hawkstorm:
Everest is the 3G variant. I think the 4G one is stingray.... If I'm not mistaken.
[Xoom Android Development] kikuto:
No HDMI output

Hi guys,

I'm on build 170, today my HDMI adapter arrived, but when I plugged HDMI cable nothing happened.

It's a problem? :(

Thanks in advance.
[Xoom Android Development] realjumy:
Mine is working fine here. Maybe is a problem with the TV or the cable...
[Xoom Android Development] Lucifertfa:
Tried 172 today didnt boot. Was it a bad file or is anybody else having problems?
[Xoom Android Development] zaktell:
Dude, read a few pages back. The last working build is 170!

Cheers!
[Xoom Android Development] Lucifertfa:
Thanks, silly me not reading the thread first.
[Xoom Android Development] realjumy:
Ok, let's try again:

PLEASE, before posting:

The last EOS 4 working version is the 170 >>>> http://goo.im/devs/teameos/roms/eos4/nightlies/umts_everest/EOS-umts_everest-20130617-170.zip

Test builds (feedbak, please) >>>> http://xdaforums.com/showthread.php?t=2372197

Thanks.
[Xoom Android Development] rocky12345678900:
Why no new nightlies?
[Xoom Android Development] realjumy:
Because 170 is stable enough and now all the efforts are focused into developing a 4.3 version... The problem is that Xoom has a serios problem of space and it's really hard to make the new version...
[Xoom Android Development] Mjammjam:
Hi brd,

I am trying to get the USB Host API running on my MZ601 Umts Everest running Team EOS 4.0 AOSP 4.2.2 JDQ39 Nightlies 170. This did turn out to not be that easy. With that image all USB devices run great through standard linux methods (/dev/ttyUSB*), but none show up on the USB Host API (http://xdaforums.com/showthread.php?t=2456138).

Giving up and putting dreamcwli's 4.3 on my MZ601 it turned out that there the USB Host API works fine there.

Reverting back to Team EOS 4.0 AOSP 4.2.2 JDQ39 _Wingray_ Nightlies 203 and trying USB Host API there, this works great as well.

Then somewhere on the internet someone stated that USB Host API never worked on Umts Everest because of that old reason that it's not a Google Experience Device.

Is that true? Or, anyhow, could you give me some guidance on how to fix that myself? I already tried that permissions setting on android.hardware.usb.host and tablet_core_hardware.xml, but that did not help. Is that now a matter of files missing, kernel settings, build.prop, or something completely different? Any help would be greatly welcome!

Thanks,

Mjammjam
[Xoom Android Development] gigi07:
mz601 4gb storage issue

Hi all,

I just decided to upgrade my mz601 (hong kong model) running eos 3 to eos 4 (170) last night. All working really well except the bloody 4gb storage issue is back again. :(

Is there an easy way to fix it or I have to roll back to eos 3?

Thanks
[Xoom Android Development] hawkstorm:
You can try assefMod which is based on the EOS framework and works quite well.
[Xoom Android Development] gigi07:
I really like Team EOS image but I am happy to try "assefMod" if it will fix my "4 GB storage" issue.

Thanks for your replied here!
[Xoom Android Development] gigi07:
No luck with assefmod.:(

Any1 has any suggestion? I can't believe I am the only person that has this issue.
[Xoom Android Development] realjumy:
Sorry, no idea. Try flashing a stock image and begin from there... I was looking for a solution for that, but I find nothing. Sorry mate.
[Xoom Android Development] gigi07:
I decided to go back using eos 3 again as it is just not worth the hassle. At least the eos 3, storage shows 26 gb.
[Xoom Android Development] realjumy:
Strange... I think that it's some kernel issue. Try with EOS 4 and apply a different kernel. Keep an eye on the development news. If we finally do right the repartitions maybe will be interesting for you... And if we finally port Android 4.4 we will try to give you real storage ;)
[Xoom Android Development] gigi07:
Thanks, let me know if u need anything from me or I am happy to test if needed.
[Xoom Android Development] Bobby Buggs:
:rolleyes:
[Xoom Android Development] smyrosnik:
Does anyone has the 170 build cause the goo links dont work.

Thanks in advanced
[Xoom Android Development] voce82:
what about the goo.im server? Is not possible to download this rom for everest
[Xoom Android Development] smyrosnik:
no there isn't a folder for team eso images
[Xoom Android Development] realjumy:
Do you need the Everest version?
[Xoom Android Development] smyrosnik:
yes the UMTS everest version for MZ601
[Xoom Android Development] pots22:
EOS Everest

The last good working is the 170, the 171 and 172 don't work.

Here: https://mega.co.nz/#!4tp0QZiL!B6m1DjH5aneg7pn2N6809Ro8nC8LywrzxU1mPygPN0s

And the Google App for this ROM

Here: https://mega.co.nz/#!owxzwZbD!KM0ovVCdOwohJglns4kjggiblNpPUyuyeE3CuYbcJ_E
[Xoom Android Development] smyrosnik:
Thanks a lot!
[Xoom Android Development] pots22:
APN

When you configure an APN you exit with the button down in the center and it's memorised
[Xoom Android Development] deb10042:
ES File Explorer performance issues (nightly 170)

I hope that this is the right place to ask my question:

Shortly, I completely wiped my rooted Xoom (Wifi/GSM) and installed the last working nightly (#170) and Google apps.

Then I installed ES File Explorer and found that usage of this app is extremely laggy with my updated Xoom. Before, I was on Android 4.0.2 and ES File Explorer had a good performance. Now that everything is totally cleaned up, every touch and hold activity in ES File Explorer needs a touch of at least 3 seconds until the touch and hold action is carried out.

Do you have any ideas, why I have this extreme performance issue and what could be done against it?

Thanks! :o

(btw: everything else seems to run at a good speed at the moment, so, no issues outside ES File Explorer)
[Xoom Android Development] treid:
thanks for reply. you mean the home button?...as i do not have other button in the center
[Xoom Android Development] htcgr:
hi

what is this rom-------> .EOS-umts_everest-20130617-169.zip.gfs135534126 (2013-11-26 4:26:23 PST ) ?????
[Xoom Android Development] treid:
no. i have EOS-umts_everest-20130617-170.zip. is there any changes with the one you specified?
[Xoom Android Development] htcgr:
i dont know...i saw that---------> http://goo.im/devs/teameos/roms/eos4/nightlies/umts_everest
[Xoom Android Development] treid:
can please someone that installed EOS-umts_everest-20130617-169.zip.gfs135534126 latest added on goo.im server tell me if the APN settings for 3g networks works and if the rom is ok? thanks
[Xoom Android Development] treid:
nobody? :(
[Xoom Android Development] realjumy:
Last stable version is 170. Working fine here.
[Xoom Android Development] tnfsmith:
Build #170 stop by here. Just need another build for 4.3 or Kitkat but hopeless about hardware compatible and developers to do it for Xoom fans.
[Xoom Android Development] treid:
APN

You can add new APN in mobile networks?
[Xoom Android Development] realjumy:
I never had a problem with that, to be honest. Right now I'm studing, but later I will try to check if it has that problem...
[Xoom Android Development] treid:
APN

thank you...
[Xoom Android Development] realjumy:
Seems like I have not that problem here, mate...
[Xoom Android Development] treid:
APN

k. thanks a lot...i will reinstall the rom maybe it works
[Xoom Android Development] mohamed_moscow:
Please can someone upload version 170 to 4shared or mega, as the file from the goo doesn`t work.
[Xoom Android Development] pots22:
170

Here: https://www.dropbox.com/s/d0n074kvb6i4a8i/EOS-umts_everest-20130617-170.zip

Gapp: https://www.dropbox.com/s/gflcbey5miq7lb2/gapps-jb-20130413-EOS-XOOM-ONLY.zip
[Xoom Android Development] beefytr:
Thanks bro pots22, you are a life-saver.

For God's sake all the zip files at goo.im are flawed and corrupt; can someone kindly deal with this issue?

Merry Xmas to all...
[Xoom Android Development] jahizen:
how can i speed up the processor. once i added gapps it slowed down. great so far tho. love it.

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

oh and where can i get a working hulu app and crackle. i forgot where i got it from last time.
[Xoom Android Development] armido:
I just want to report I've walked the walk doing the BigPart partition and successfully installed all Omni ROMs through 108.

But...

I've returned to EOS 170 using EOS4 BigPart boot image because there are some issues possibly related to the selinux kernel used by Omni. I am certain SuperSu is not the issue. I have successfully used Linux Deploy with EOS. But, due to the fact under Omni the rootfs is mounted nodev, noexec with no apparent way to change it (remounting rw with FX makes no difference), Linux Deploy cannot write downloaded files to /data/local/linux/mnt. My question about end user control over selinux went unanswered.

Maybe if a different kernel is used, or information how to manage selinux under android is provided, I'll give it another go.

Anyway, returning to EOS after going to Omni is doable.
[Xoom Android Development] alidali:
message after boot

I install v170 but every time it starts I get the message 'android update. Optimising 1 (2, 3) of 3' . After that it works. Is this normal?
[Xoom Android Development] superbay:
Every time you flash a new same rom over the old one, it happens and yes it is normal. But it should only happen once in the first reboot after flashing. Do you encounter that every time you boot the device?
[Xoom Android Development] alidali:
It happens every time i boot it.
[Xoom Android Development] tnfsmith:
Any wake on touch mod kernel pls, I behind something wrong
[Xoom Android Development] kouponi:
i have eos3 124 ver and 3.0.2 recovery. can someone tell me how i can udpate to eos 4? i read the 170 ver is stable .are everything working ok?
[Xoom Android Development] tnfsmith:
Just update your cwm from runandhide05, link http://xdaforums.com/showthread.php?t=1782235 and flash new 170 build download through Goo manager as you done on eos3, it simply too. Eos4 with 170# look good for me, I have no trouble too. Good luck!
[Xoom Android Development] kouponi:
i flashed this rom and everything its OK. but i looking for and i didn't find the option "wireless screen". where is it?
[Xoom Android Development] tnfsmith:
If nothing wrong you will see it setting option.
[Xoom Android Development] kouponi:
sorry my friend but i didn't find it. can you see it,where is it?
[Xoom Android Development] xoom mz601:
xoom mz601

dead link .... my xoom mz601 need this file ... Team EOS Xoom Nightly builds 4.2.2 .....please help ...
[Xoom Android Development] riddevi:
Me too!!!
[Xoom Android Development] pots22:
EOS link

Last stable version 170 JB don't update to 171 or Crash an Gapp specific for this ROM

https://www.dropbox.com/s/rakb0l2vs7478c2/EOS-umts_everest-20130617-170.zip?dl=0

https://www.dropbox.com/s/n8rcdjkng8g5xq6/gapps-jb-20130413-EOS-XOOM-ONLY.zip?dl=0
[Xoom Android Development] mangareds:
thanks a lot...I needed this...
[Xoom Android Development] gabrieleda:
Hi I would like to install this rom, but I'm not sure if it is a Big part Rom or not, can you please confirm?
[Xoom Android Development] GedeWK:
Just waiting for the tethering and wifi hotspot fix. I really need them for my phone.. my phone has c**p internet.
[Xoom Android Development] xavierleonelbr:
Please TEAM EOS! We need Wifi Thethering very much! Help us please! Keep up the good work!
[Xoom Android Development] bigrushdog:
I think I know what it is. In the meantime I've heard reports wireless tether from the Play Store works. Or they have a Google projects site too.
[Xoom Android Development] I.Am.J:
i got lag while playing games... like NBA 2K13, NFSMW... does anybody got same problem with me?
[Xoom Android Development] OtavioMalzone:
I'm having issues with keybord. I'm trying to login on facebook via chrome, but the keybord keep trolling me hiding, and showing some secs efter, pressing 3-4 times the type area.

Btw, awesome rom!
[Xoom Android Development] jamie_lee142000:
i use a program called six-axis controller which connects a ps3 controller to your device via Bluetooth, its working when i connect physically via usb. but its not working via Bluetooth, its not even turning on the Bluetooth. its been re-written to support 4.2.
[Xoom Android Development] gucio1200:
Probably its six-axis related, becouse my bluetooth works perfect. With keyboard...
[Xoom Android Development] jamie_lee142000:
yeah when i restarted my tablet, my bluetooth started working again.
[Xoom Android Development] RoWeKo:
Use JellyBeanKeyboard from PlayStore. Works perfect. Your problem is already discussed earlier, no other solution possible for now.
[Xoom Android Development] cyber-junkie:
Workaround/solution is in post 1:
[Xoom Android Development] bigrushdog:
possible tether fix. need testers please

http://xdaforums.com/showpost.php?p=36851182&postcount=118
[Xoom Android Development] cunnie84:
Tried the possible fix with no luck im afraid :( really gutted for ya man this rom is amazin so far :)
[Xoom Android Development] adelancker:
A little something to keep you going, guys!

Great work on porting android 4.2 to my Xoom!

Have been enjoying it and found no bugs!

Really snappy performance and so glad you continue your support for the Xoom!

Anyway, put your money where your mouth is so..

it's not much, but I am sure I'll donate once again soon. I've only recently retrieved my PayPal password, so I could only start showing my gratitude towards all the devs this month! lol

Confirmation number: 13L788467K033943R
[Xoom Android Development] AVIMPEG:
140 is out
[Xoom Android Development] Doc Franky B.:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

For me a little slow . Must i clean all i mean is factory reset needed?

Sorry my bad English :o

Regards
[Xoom Android Development] gesreg:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

1/19/13

Phones

Tuna Series

All - bring back depricated SMS framework fixing Handcent issues

Maguro - update build fingerprint

Toroplus

Update toroplus build fingerprint to official 4.2.1

Bring in official 4.2.1 vendor binaries! Dramatically better battery life, radio performance, gps lock, and fixed drm for Hulu+ yippie!

Tablets

All

Fix clock digit cut on lock screen

Fix annoying Back/Ime button bug when using a hard keyboard

Xoom

Stingray - New activation helper app for clean activation on initial boot

Stingray - Removed activation app in favor of a better framework fix

TF101

Numerous AutoRotate patches fixing a number of pending issues

Nexus 7

Enable CRT screen off animation (I like it better, will make user defined soon)

All

Clean up EosControlCenter icons

Feature - control wifi off timeout when device sleeps

Enable XDA support links in ECC information, disable Rootz link for now

Bring back the Toasts in frameworks non app / services

SystemUI: respect statusbar background for themes

Add config to allow to decrease suggested wallpaper size

Fix Launcher lag with optional overlay config value

Add EOS Daydream into SystemUI. Welcome back Roach! Fling away ;D

Fix Recents Landscape Killall

1/9/13

Phones

Tuna Series

Update device tree

Update Leankernel 5.6exp2-230

Bring in usb-otg support

Update omap3 branch and libhardware branch fixing Tuna gps

Maguro - fix signal strength bug caused by importing Everest code

Tablets

TF101 - Fix system crash when changing dock keyboard layout

Grouper - Update device tree

Bring in usb-otg support

kill long press volume buttons for bug reporter

All

Bring in some cli binaries

iw, libnl, dropbear, powertop, scp, sftp, ssh-keygen, tcpdump

Update some quick settings panel icons

Update broadcom/wlan branch

Misc framework updates from CyanogenMod thanks guys

Yet another attempt to fix APN settings, should work for real now

(LTE devices) new LTE Quick Settings toggle (see, I remembered ;D )

changelog >> http://code.google.com/p/teameos/wiki/ChangeLog :thumbup:

---------- Post added at 03:13 AM ---------- Previous post was at 02:18 AM ----------

For what I do is wipe cache -dalvik cache - wipe system- flash latest nightlies-flash latest gapps -and keep OC'd @1600 :thumbup: :D
[Xoom Android Development] Y_Yan_C:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Asop keyboard still not fixed, 4gb internal storage for Hong Kong xoom still not fixed. Keep on the good work. Also, is it possible for 4.1 interface! Like status bar and clock back to the bottom right corner? Also adding the "No Wallpaper" option in the wallpaper option?

Quadrant first test 2177
[Xoom Android Development] MDAman:
Just installed #140 (full wipe)

No wifi-tether, EOS Control Center crashes when fliping the table horizontal-vertical and the other way.

Theres also an issue when setting to airplane mode, "data enabled" gets disabled and has to be reenabled manually when turning airplane mode off.

When trying to enable/ disable "airplane mode" using Eos toggles its not working at all.

The desktop seems a little laggy compared to #124, which i used so far.

Hope the bluetooth problem is gone. Sometimes when i enabled BT, the xoom instantly turned into "cycling-four-color-loading-screen" and got stuck there forever.

Only flashing or recovering from a backup brought it back to life.
[Xoom Android Development] gucio1200:
Old ui is bad idea , new one is much better... in my opinion. And i wont agree for mod it in main tree :) Try to mod ui yourself mate ! Its cosmetic ... Dont be lazy ! Learn u droid :)
[Xoom Android Development] elkedra:
New status bar is not better for some of us if only because some apps cover the top status bar and then you can't see the clock or access the quick launch tab without closing the app!

Also, to call someone lazy because they don't know how to mod is ridiculous. Some of us are happy to support xoom development by answering questions on the forum or making donations.
[Xoom Android Development] Y_Yan_C:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

I know my droid pretty well thank you very much. I don't like to put mod on the system because it slows the whole thing down, especially when EOS4 is still in its early stages. And yes, that is exactly why I want the old ui back