yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] realjumy:
Did you used the full wipe before flashing the new rom? If so, try to re-download, do a full wipe and flash.
[Xoom Android Development] tnfsmith:
None so far. I flashed with wipe cache and dalvik cache without factory reset checked. I have collects and made backup apps and data with titanium backup and patched apps with Lucky patched, every flashed the new room with major changes I must do patch them again it's make me annoying hate lazy too @). Any better solution?
[Xoom Android Development] bigrushdog:
You gotta modify the script to delete LatinIme.apk. And in the script delete it before you extract.

EDIT: I updated package to delete LatinIME.apk and LatinIMEDictionaryPack.apk. that should give you plenty of room to make it work. Lemme know how it goes.
[Xoom Android Development] realjumy:
Thanks mate. Now is working fine. Definitely, it is a really good (and free) alternative to stock. :)

Here is the mirror to the file:

xperia_z_kbd.zip (16.6 MB)
[Xoom Android Development] bigrushdog:
Good deal. Now somebody hurry and mirror so I don't kill my Dropbox!

Edit: ok I see the mirror. Good deal.
[Xoom Android Development] realjumy:
Can somebody with other languages than English or Spanish check if it is working fine?
[Xoom Android Development] bigrushdog:
I stripped Oriental languages. Don't know about any others.
[Xoom Android Development] realjumy:
[MENTION=470268]bigrushdog[/MENTION], I have been using PA HALO since a week ago. It is pretty interesting but I don't know if it is possible to easily implement in the Eos 4.0. Is that one of the features you have in mind for a future? (No pressure, no rush, I know that our Xoom are already to the limit...)
[Xoom Android Development] narin99:
yes, with Thai , it works perfectly.
[Xoom Android Development] bigrushdog:
No plans at this time. I just don't hear enough people say it kicks a*s.
[Xoom Android Development] realjumy:
I will try this tomorrow: http://xdaforums.com/showthread.php?t=2265564

If this really works, will be a big step ahead :) If somebody wants to try it as well, and share comments...
[Xoom Android Development] bigrushdog:
An Aroma installer that customizes what to trim would be interesting. There's definitely plenty of bloat to trim.
[Xoom Android Development] hawkstorm:
That's an interesting thing... slimming down the GApps package. From what I gather, it's alot of trimming in the sense of removing tones and the like. How does that affect the ringtones and stuff? Would that mean that the selection would be further limited from the get go?
[Xoom Android Development] callsignapollo:
Stable enough to move from EOS3 stable?
[Xoom Android Development] realjumy:
Under my point of view: absolutely. Do a nandroid backup and try Eos 4. :)
[Xoom Android Development] realjumy:
I need to keep on testing the .zip, but I don't see any difference so... Great! If it works as it should but uses less space... :good:
[Xoom Android Development] narin99:
For me, yes...
[Xoom Android Development] hawkstorm:
Is anyone else having problems downloading the file from the Goo.im app? It keeps halting the download citing MD5 checksum error.
[Xoom Android Development] realjumy:
My problem is not with the MD5, is that I can't download the files from Goo.im with the tablet...
[Xoom Android Development] bigrushdog:
Check your download path.
[Xoom Android Development] samo_nz:
Unable to find files

Trying to install EOS4, when browsing internal storage in recovery I am unable to find any of the new zips I have just downloaded, I do have a lot of files on my xoom, is there a limit on the number of files recovery will scan or am I going mad?

I am using team win 2.5 recovery and EOS3

Can see files in a file manager inside android but they are missing when I select install and browse in recovery or under file manager in the advanced section of recovery
[Xoom Android Development] realjumy:
I can download other things, but from Goo.im (from the website, not using the app) it never begins...
[Xoom Android Development] Simonetti2011:
Is there a mirror? goo.im is simply too slow.

Another thing: in the toolbar, the "home" soft button isn`t working. Is there a workaround for this?
[Xoom Android Development] renton82:
Please give us a mirror...
[Xoom Android Development] hawkstorm:
I tried downloading from the website yesterday. It was really slow. Maybe a server limitation.

Still don't understand the MD5 checksum error I'm getting with the Goo manager app. Is it a connection thing or something wrong with the file?
[Xoom Android Development] romdroid.:
Stable for daily use? No fc, lags or anything else?
[Xoom Android Development] new-noob:
Stable ? - yes

No lags ? - yes but 166, 168 were smoother that 170 :)

Enjoy!
[Xoom Android Development] sledziu:
For me 170 is much smoother than 166-168. Also overclocking to 1.5Ghz also works for me on 170. On 166-168 i get crashes on 15Ghz.

Regards.
[Xoom Android Development] tnfsmith:
Try this link mirror officer: http://jenkins.teameos.org/job/umts_everest/
[Xoom Android Development] stephnd:
139 is out anyone try it yet?
[Xoom Android Development] gesreg:
on #139 apn setting is working :thumbup:
[Xoom Android Development] bigrushdog:
You don't know how glad I am. Now for tether fix and we'll be in business.
[Xoom Android Development] stephnd:
any other improvements ? smooth?
[Xoom Android Development] Darkman:
Thanks for your hard work!!! :good:
[Xoom Android Development] abbots:
Hmmm, just flashed 139, apn settings takes me to wifi networks....?

Though, i think? on very first boot, i think? I did see APNs.... but now goes to WiFis...

I'll try reboot, and report....

Also, since 138, quickview doesn't see photos, did anything alter...?

Thanks so much to brd and team eos

Back after i re-ipl xoom

/later/

weird, before reboot, tried again, maybe in 2/10, went to apn, seems, editing, all works, BUT

about 8/10, selecting apn, screen flashes briefly, and, I end in WiFi networks screen....

what log tool to use to capture relevant logs ? tried lumberjack, but, it seems to lock up on dmesg export?

//later//

just booted, on 3g, wifi off, was able to enter/edit/save APNs several times, BUT,

after a few goes, touching APN menu takes me to WiFi menu, and, getting WiFi power on message

if you need any logs, what/how to get them?

Aus 601, 139
[Xoom Android Development] thr0tt:
Does the pano camera work now ? Also, how reliable is the 3G as I use my Xoom as a tool when out and about and can't live without it.
[Xoom Android Development] abbots:
pano worked for me when tried on earlier build, had no issues

3G works, no issues
[Xoom Android Development] stephnd:
Is the Keyboard issue fixed in #139? The issue which is stated here: http://code.google.com/p/teameos/is...ne Device Owner Summary&groupby=&sort=&id=214 for Wingray, is on my everest Xoom as well.

or is it just me? I'm on #138
[Xoom Android Development] narin99:
Last night, I just flashed V 139 . It is working great. THANKs..
[Xoom Android Development] winpeace:
can you solve this problem
[Xoom Android Development] Y_Yan_C:
Hi, I am still experiencing asop keyboard issue

Edit: Hong Kong Xoom still having 4gb problem
[Xoom Android Development] winpeace:
keyboard issue not solve *139.
[Xoom Android Development] ArdinCani:
FREAKIN YEEEEAAAAAH ! THE #139 HAS WORKING 3G

HELL YEEAH!

But i think that it needs some work with the animations ... Are pretty laggy
[Xoom Android Development] cunnie84:
DO NOT SELECT SIMULATE SECOND DISPLAY in developer settings, kicked me straight into a bootloop, then my backups wouldnt work saying wrong md5 sum!!!!!!!! Luckily titanium backup has all my apps saved, after a factory reset, then reflashed rom #139 and gapps im now just letting titanium backup do its thing !!!!!!! Heed my warning, steer well clear of simulate second display, on a lighter note my aospkeyboard works fine, all ive done is changed it to pc style, from a post i saw sumwher on xda ive looked for it but cant find it agen maybe sum1 else can link to it
[Xoom Android Development] bigrushdog:
Nobody has posted this to bug tracker. However I've seen this mentioned a few times now. I will disable this for Xoom.
[Xoom Android Development] Y_Yan_C:
Thanks. I have tried the setting and had the same thing. Only thing is that my #12x backup worked and I didn't lose much
[Xoom Android Development] alex94kumar:
Lol, a while back (after 157 or 158 for wingray) when runandhide gave me a test build of his, the same thing happened to me, with the multiple display issue. I reported it to him and he kinda helped me through it. Brd, he didnt report that to you?
[Xoom Android Development] bigrushdog:
I have short term memory issues. That's why bug tracker is my friend.
[Xoom Android Development] winpeace:
i am on 139 and launcher says alot of times force close
[Xoom Android Development] LQQKS:
Does anyone use Tasker and find it won't go into Deep sleep?

Sent from my rooted Xoom MZ601

running Elemental CM10.1

using XDA Premium app \o/
[Xoom Android Development] Doc Franky B.:
Hi BRD,

after flash #171 hangs up at Moto Logo :(
[Xoom Android Development] hawkstorm:
Can anyone get bluetooth tethering to work? I can't use the connect as Access Point to work. Anyone else facing this?
[Xoom Android Development] armido:
Keep calm and go on...

Update to 172 also stops at Motorola logo. Cannot do anything but let the battery drain, recharge and try booting into recovery. Not good.

armido
[Xoom Android Development] IGstarr:
same here =(
[Xoom Android Development] attmakesmevomit:
Same here... I checked the thread about two hours ago, started the download, and just came back to the tablet and flashed the ROM... hung at Moto logo.

Plus, the two recent backups I have are failing to restore...

Edit: Restores failed, but I was able to install the previous ROM over top and I don't appear to have lost anything... got lucky!

To save you guys a search, press and hold Power & Vol Up at the Moto logo to reboot, then tap Vol Down until you see "Recovery"... then tap Vol Up again to enter Recovery. Hope you all have equally positive results.
[Xoom Android Development] IGstarr:
i download the 170 Rom (via pc) and flashed it .my xoom boots again
[Xoom Android Development] Borg1of3:
172 boot freez at moto logo, same as 171

172 boot freeze at moto logo, same as 171...I am back to 170
[Xoom Android Development] davidebeatrice:
Same here. Even flashing previous version (171) my xoom hung on moto logo

Back to 170
[Xoom Android Development] attmakesmevomit:
Flash 170 and you should be good... worked for a couple of us, at least. I believe 171 marked the add of the new kernel?
[Xoom Android Development] lchiu7:
Not to add a me too for the sake of it but this is the first ROM that did this to me. The way I got it off it was to reboot into recovery and flash 171 which I still had in the Gooimg folder.

Had a heart stopping moment when it happened until I read these posts.
[Xoom Android Development] Lypsis:
Same with me here at version 172, then tried 171 and just the same problem.

With #170 it is working again.
[Xoom Android Development] tnfsmith:
With flashed with you, did you try to reset factory before flash #172?
[Xoom Android Development] Doc Franky B.:
No factory reset, only wipe cache/dalvik and system then flash rom and gapps.
[Xoom Android Development] armido:
Thanks. Worked and I was able to recover to my last backup - while flashing 172. Before your post I tried using different combinations of volume up/down since the device was already powered up. Didn't think of including the power button.

:p
[Xoom Android Development] hawkstorm:
Is anyone experiencing problems installing big apps? I keep getting a insufficient space notification when I try to install Angry Birds. I'm on #170 haven't flashed #171 or #172.
[Xoom Android Development] armido:
You may be out of space due to storing too many backups and ROMs. Presuming you have ROM Manager installed, use this to delete old backups. Delete ROM 172 for sure! Older ROMs too.
[Xoom Android Development] hawkstorm:
Ah.... that makes sense. I'll look into it. I think I may have more than 1 nandroid thanks to OBackup. Does anyone know how to use the program. It keeps telling me that backup has failed but it seems to be writing to the device. I've selected the TWRP .tar file as a default backup choice.

BigRushDog/Devs:

I realised that the Bluetooth Tethering is also not working. I'm able to make a direct connection to the XOOM but not an access point connection as in previous builds. There's a unknown device that is listed in when I check the device status in the Device Manager. This problem wasn't in the EOS3 build but connection stability even without Bluetooth Tethering seems to be an issue with both the EOS3 and EOS4 roms. I keep getting timeout issues and disconnects when browsing and downloading apps. The connection stays stable for about 45 minutes to an hour depending on signal strength. I've tried the SIM on other phones (Motorola MB865 Atrix 2 and GNex (maguro)) and I can't replicate the problem.
[Xoom Android Development] hawkstorm:
I tried cleaning out the back ups etc but still no luck. I checked the storage menu in the settings and found that my apps is taking up more space than it should (abt 7gb). Doesn't really make sense to me considering I only have about 3gb max of apps and related data. But I have a 32gb model so I still have 20gb give or take of internal storage.... There shouldn't be any problems right?

I updated from EOS3 yesterday and did a clean install of the ROM. Haven't encountered this before in any if the builds I tested before (pre #160). I've moved the storage location for GooManager from the internal storage to SD and also move the back ups into the SD. It seems to be happening to the Angry Bird games aside from the original one.
[Xoom Android Development] RoWeKo:
Why are 171 and 172 not deleted from goo? They only make troubles and goomanager always says that there's an update available.

Staying with 170 seems to be best decision for the moment.

sent with Tapatalk 4 beta
[Xoom Android Development] htcgr:
+1:crying:
[Xoom Android Development] pots22:
171-172

What this update ?

My tab work perfect on 170

Saturday morning i install the 171 reboot and Hoooooo stay bloqued on the Motorola Logo.

I return to the recovery make a full wipe reflash but the same result.

With my smartphone i download the 172 reflash the tab and same result bloqued on the Motorola logo.

Finaly i redownload the 170 flash and Hoooo all work perfect.

Any explications about this two updates 171-172 ? :(
[Xoom Android Development] narin99:
Same here.. I flash v 172 then my xoom stuck on Moto logo...

Then, i flashback v 170 to xoom
[Xoom Android Development] Doc Franky B.:
1055 downloads by goo.im and only anybody has an failure, what did i wrong by install #172
[Xoom Android Development] hawkstorm:
Guys, from the thread, you'd realise that the build has issues. You'd be better off waiting for 173.
[Xoom Android Development] tnfsmith:
Nope, just restart or after boot up you wait a while finished loading apps in background and then try to update a or install apk big files too. This error appear from lack of memory ram to install instead of storage space. Let's it delay for a minute and you don't unexpected too. I experienced that this problem usually come with new rom installed or a hard trike to the system and must be reboot.
[Xoom Android Development] hawkstorm:
I had to do a factory reset and flashed the ROM again.
[Xoom Android Development] pots22:
173

Why people continue to download the 172 update ? stay lock on the Motorola Logo.

No explanations or news from my prefered Team EOS?

Thank's for advance :confused:
[Xoom Android Development] zaktell:
My XOOM stucks on Moto logo also with 171 and 172 update! As far as I can see the problem exist with the last two updates for Stingray and Wingray. I suppose it's something with the new kernel. Some people report that it's OK if you do a factory reset but I don't want to. Will stay with 170 update for now.

Big thanks to Team EOS for this wonderful rom!
[Xoom Android Development] pots22:
No factory reset

I test with a full wipe and factory reset but no issue for the 171 -172
[Xoom Android Development] armido:
Doing a full wipe and factory reset will require re-installation of my chroot linux environment and all programs. Too much involved to install ROMs that require a full wipe and factory reset.

Hope the problem is resolved in a way that does not require a full wipe and factory reset.

Otherwise I guess 170 will be my last EOS update.

:eek:
[Xoom Android Development] new-noob:
I installed 170 without full wipe and tablet not even started, it stucked on moto logo,

So question - what has changed tonew build that it requires full wipe?
[Xoom Android Development] hawkstorm:
That's great news. I should give it a go when I can. Anyone know what's causing the problem? Is it the new kernel as a lot of people seem to be pinpointing?
[Xoom Android Development] pots22:
The reason

I don't now the real reason of this but when i flash the 171 or the 172 and after that i try to flash the tab with fastboot an error "to much lines"

and when i connect the tab for flash with RSD lite 5.4.4 my PC don't detect correctly the tab.

So when i have the 171 or the 172 not possible to flash with fastboot or RSD mode

Error like "too much lines" or "unkmow error".....

This two updates block in the bootloader.
[Xoom Android Development] armido:
Most people have not had a problem with 170. Are you sure you do not mean 171 or 172?
[Xoom Android Development] wisekki:
Stucked at Moto-logo

Hi,

Just flashed the newest build 172 with wipe dalvik and wipe cache. Now I'm stuck at the Motorola logo and nothing happens. I can restart the xoom with volume up and power button but the same happens. I can't enter to cwm and now I'm lost what to do. I can't even turn of the device :confused:

- Andy
[Xoom Android Development] Simonetti2011:
Same here. Flashing 172 will cause my MZ605 to lock up at boot.

What I did was to manually re-flash version 170, from TWRP 2.5 Recovery. Fortunatly I still have the 170 flashable file and GApps file in my Xoom.

You can reboot your phone from the Motorla logo using VOL-UP + PWR and then PWR again to turn it on. As soon as the motorola logo shows up, quickly press VOL-DOWN several times. You'll notice a line in the upper left corner of the screen, with the boot options changing as you press VOL-DOWN. Select Recovery and then press VOL-UP to enter recovery mode. Mine took over 1 minute to enter recovery, but from there it went smooth.

Once in recovery, you have to manually mount the System partition, or the flash will fail. the select the 170 flashable file, G-apps file and flash away. You can wipe the Dalvik cache right after the flash procedure is done.

What I describe here saved my Xoom less than 12 hours ago. I did it over 5 times, so I know the procedures by heart. It only worked after I manually mounted the system partition in TWRP.

If you don't have the 170 version already in your Xoom, download it from your computer and try to find a way to copy it to a microSD card. TWRP will allow you to flash a file from the external SD card. It is best, however, to just leave the ROM files in the Xoom's internal flash memory until it is absolutely not needed anymore (say 3-4 stable working nightlies after).
[Xoom Android Development] wisekki:
Thnx man! I had completely forgotten that you have to press vol-down several times. After that it went like you said :good:
[Xoom Android Development] Borg1of3:
what is the point of?

Hi, what is the point of this upgrade? It does not working... :(
[Xoom Android Development] hawkstorm:
The latest build seems to need a full factory reset. So an app like Helium or Super Backup or Titanium back up would be advisable. from the thread those who are willing/have done the reset have been successful.
[Xoom Android Development] origami_ns:
I tried to install 172 over factory rom, I did all wipes but stuck on motorola logo.

Version 170 works like a harm! Awesome rom, even faster than stock ;)

Good work for team!
[Xoom Android Development] Hassan_Elyas:
does this rom has USERS option?

Edit : yes it does.

but the latest build isnt booting up..I flashed it and its stuck at the boot logo.
[Xoom Android Development] Doc Franky B.:
Dear Team eos,

no more nightlies?

Everytime i look on jenkins.teameos.org i became "bad request" is it only me?

What's wrong here?

Greats
[Xoom Android Development] waz675:
People saying TEAMEOS have stopped making their ROM for nexus7 in the relevant thread using stuff like 'cease to exist '. I'm reserving judgment until I can find time to see official news but if that is indeed the case, that could be a goof reason for bad request error message (say, removing web server / access if they indeed have closed their doors to making ROMs).

If so, very sad news, hoping soooo much that its wrong information somewhere along the line.
[Xoom Android Development] hawkstorm:
I doubt they would just drop a project just like that. Something may have happened somewhere. You can keep track of the other (Wingray/Stingray) threads to see if development is still ongoing. I think the team may have had a lot on their plate at the moment or maybe the latest build needed to be redone massively.
[Xoom Android Development] realjumy:
Folks, developers have the right to have holidays too... Keep calm. EOS4 is stable enough and don't need an urgent update. All us should be happy of their great work.
[Xoom Android Development] xavierleonelbr:
The same here! 172 isn't working!
[Xoom Android Development] Hassan_Elyas:
Flashed 170 and waiting for the next nightly :)
[Xoom Android Development] new-noob:
I realy hope its holidays (btw team EOS - have a good one ! ) our old good xoom thanks to team EOS still is a good tablet!

:)
[Xoom Android Development] tnfsmith:
Android 4.3 has lease and we hope the new nightlies build come with significant one and at least it the last build support from team EOS satisfaction.
[Xoom Android Development] bigrushdog:
Yes. Xoom will get 4.3. Access to resources is one of the reasons for the new project. I didn't have control of Eos servers and apparently those resources are now offline. Look for a thread in general section for test builds and discussion about the new project.
[Xoom Android Development] tnfsmith:
That's really rock man. I will be volunteer to test with new 4.3 project. Don't worry all Xoom users beloved it too. Looking for new revolution..
[Xoom Android Development] bigrushdog:
New project discussion and testing thread. An important read on what to expect and all that good stuff

http://xdaforums.com/showthread.php?p=43796331#post43796331
[Xoom Android Development] pots22:
Nightly 172

I'm think nobody have installed the 172 successfully.

So what do you think about flash the 172 + Gapp + directly the kernel ElementalX Xoom 1.2?

If the xoom stuck on the Motorola Logo it's probably the kerenel but with flashing directly another ?
[Xoom Android Development] binhaus:
never flash success from 144

Dear

I have tried many time all version of eos4/nightlies/umts_everest

and never work with after 144 to version 172

( only 167 worked = I think that why too many download at this version )

they all stuck at M logo boot screen

tried with both CWM 3.2 and 6.027 .. unlocked from adb command, clean all cached..

any advices thanks
[Xoom Android Development] hawkstorm:
Have you tried doing a full wipe (Data+dalvik+cache)? I'm on TWRP and all the nightlies up to 170 work on mine.
[Xoom Android Development] binhaus:
Sure.. all cache, data reset done ..

ps: I confirm that the 170 work with me too ( just reflash direct from 167 ) :) but then for 172 not work.. so now i doing go back to 170

:)
[Xoom Android Development] origami_ns:
I flashed version 170 over stock rom successfuly on MZ601 using TWRP, with full wipe (cache, dalvik, data).

171 and 172 didn't work for me.