yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] joshndroid:
Okay I know someone mentioned this way back... but on build 44 had the battery run to zero when the tab was physically turned off i know because I turn it off once I am finished with it and yesterday I had to make sure because I almost pushed bootloader and not shutdown lol.... Always factory reset between builds, wipe caches nd fix permissions never a problem like this before just an added voice to someone else who brought this up lol
[Xoom Android Development] slonn:
Having the same issue - no video option in GTalk or Skype. Running on version 49 with the latest Gapps flashed. Not sure why video is disabled.
[Xoom Android Development] majdinj:
I noticed some unnecessary video files in GApps file inside the following directory:

"EOS_GApps_ics_4.0.3_v10.4\system\media\video". They occupied almost 5 Mb.. So I think you must delete them from EOS_GApps_ics_4.0.3_v10.4.zip file before flashing or delete them by root explorer after flashing.:rolleyes:
[Xoom Android Development] ionSeven:
Those videos are used in the video effects for the video recorder, may have an adverse effect if removed (no pun intended)

Sent from the XOOM of Chucky!
[Xoom Android Development] Brillntred06:
I switched over to build 49 and the updated gapps after having been on version 48 with 10.3 gapps. Everything was fine but my work email wasn't through IMAP wasn't. Deleted the account, added it back again, emailed loaded but failed again once I tried to refresh. Went back to my 48 backup and haven't had any issues. Anyone else had any issues like this? I already tried a reflash of both 49 and gapps 10.4, and I wiped everything before flashing each time.
[Xoom Android Development] PMDColeslaw:
Im having issues with that. I tried to convert it to a user app in TiBU and it said it was done but in fact nothing changed. When I try to uninstall from within TiBU it says the APK file cannot be found. The APK (Music2.apk) is still in the System/App folder and Gmusic still runs fine, just wont update.

I tried removing the Music2.apk from the system/app folder and that made the icon disappear from the app drawer but the market errors out on install saying that "the application already exists." If I leave the apk in the system directory the market says the app is not signed correctly.

I've wiped cache/dalvic and rebooted and tried every other normal troubleshoot I can think of. Any ideas?

EDIT: Sorry, I'm on N49 and Gapps 10.4
[Xoom Android Development] liftman-:
they may ship that way, but I fix them up quick :)

np I can manually mount in a terminal
[Xoom Android Development] rschenck:
You hAxXor, you...:eek:
[Xoom Android Development] liftman-:
I wonder if spin up time might be a issue, I wonder what the settling time is in the auto mount.
[Xoom Android Development] SQurel23:
Thanks! That worked perfectly.
[Xoom Android Development] jodtalingchan:
I noticed that /system has 251MB size. Is It a bit low? I've checked ICS ron on my Nexus S it's shown about 500 MB on /system. Well, just for your info... By the way, thank you for this great rom.
[Xoom Android Development] majdinj:
I think there must be a way to resize system partition???:confused:

we need developers advices to do that..
[Xoom Android Development] rschenck:
I do not know of a safe way to resize partitions, but even if I did I would very strongly advise AGAINST resizing system.

Anyway I suspect system sizes itself during install...and you have no use for free space in system.

This strikes me a bit like people boasting about how much free mem they have....that stuff is meant to be USED, not admired.
[Xoom Android Development] chethammer:
I'm having some autobrightness problems. Screen gets dimmer and dimmer then a little brighter then dimmer. Anyone else?
[Xoom Android Development] bigrushdog:
Partition blocks are mapped in the bootloader and can not be written to. Instant brick guaranteed.
[Xoom Android Development] draiken:
Did You do a factory restore or only cache/Dalvik reset?
[Xoom Android Development] jodtalingchan:
So, it is fine with this size, isn't it? Less than 5MB on my /system :-P
[Xoom Android Development] joe ferreira:
yes ... 10chars
[Xoom Android Development] bigrushdog:
I'm not sure yet but it looks like about 30MB of /system space is used by some binaries in /vendor. I'm pretty sure those binaries are tied to facial recognition. Maybe you guys can dig around and see if I'm on track here...
[Xoom Android Development] RMerlin:
I know it can be done on other devices. The Nexus One has a modified HBOOT available that allows you to resize the partitions. That's how people are managing to fit ICS on its seriously limited /system partition. But the point is it requires a modified bootloader in this case, so it's neither trivial or 100% safe.

I think what worries people is that eventually it might become a factor limiting what TeamEOS (and other custom firmwares) can put into their ROM. But I'm fairly sure there is plenty of places where space could be recovered if it came to that, starting with bundled wallpapers. So I wouldn't worry about that at this point.
[Xoom Android Development] eckka:
I can't get automount of USB drives to work!

I am only able to connect my 16Gb sandisk Cruzer, formatted in 32bit, by using the storage settings in the settings menu and then it will only allow me to connect after the Internal storage categories have finished calculating and display their usage values. If I tap the Mount option after these values have updated then I can connect.

I tried the same thing with a 750Gb external drive, formatted in NTFS, which used to connect perfectly using Drive Mount on the Moray ROM but even after the values have updated the best I can get it do is make the drive light blink each time I press the mount option. The same thing occurs with my 1Tb Lacie drive, formatted with NTFS, which also used to connect.

I've tried the various USB OTG mount apps with limited success. I could get Drive Mount to work once but then it would crash or give me a black screen. Other apps had me update BusyBox but this didn't seem to make any difference. While the app, USB Mass Storage Watcher OTG, would claim the drive was mounted, in reality it did not appear, even in the folder the app used to mount the device.

I've tried with and without the USB debugging setting and this makes no difference. I usually name the volumes when I format them and thought this may have been an issue but even without volume names I still can't get automount to work.

I'm currently running Nightly Wingray version 49 with gapps 10.4 on a WiFi GED unit. I even tried a full wipe and reinstalled everything from scratch. I use File manager HD and have a bookmark set for the /media/ folder. I've even set Moboplayer to this folder /media/sdcard/ as the source for my movies. Essentially all things are set to use the new mount points in ICS. I've tried to get Superuser to update its binaries but I get the "Unfortunately, Superuser has stopped" message.

Is there anything I'm doing wrong or should do? Should automount do as it suggests or does it require intervention?
[Xoom Android Development] liftman-:
yup deleted it, breaks facial recognition lol

there is the missing space, 25.5 megs after deleting it lol

nothing else seems to be broke.

gonna need 2 flavors of gapps now.
[Xoom Android Development] bigrushdog:
Maybe you can move vendor/pittpatt folder to /data and symlink it back. Just make sure perms are right. Should work.
[Xoom Android Development] Xoom Master:
OK so I installed this rom and I really like it but what if I want to put the stock from back on? Not now but maybe in a couple months?
[Xoom Android Development] mr_wrong_0:
Ad-hoc?

I saw on the changelog the other day what looked liked support for adding ad-hoc networks

I've been using the ICS bluetooth tethering between my photon and the xoom, but if I would really like to use my wireless tether in ad-hoc mode.

But when I flashed the nightly (including the newest Gapps at the time 10.4) there was still no ad-hoc support. That was disappointing but no big deal, however bluetooth tethering wasn't working on that build. So I flashed back to the older build (keeping the newer Gapps) and bluetooth tethering was still not working until I flashed the older Gapps version as well. Just wondering if anyone could shed some light on this issue.
[Xoom Android Development] WarLion:
This is rom is a beauty Congrats to the developers I really love it thanks a lot for all the work
[Xoom Android Development] P0yraz:
No one here to help me out? I want to root and flash this ROM :'(
[Xoom Android Development] liftman-:
# ln -s /data/pittpatt /system/vendor/

works fine with wrong permissions, also rebooted and check, still bad permission (I'm sick and lazy)

you can link that in the updater script and move the dir accordingly.

man the updater script is getting longer :)
[Xoom Android Development] rschenck:
Use the following guide....there is none better on adb in general or rooting the Xoom specifically.

http://xdaforums.com/showthread.php?t=1249798
[Xoom Android Development] liftman-:
very nice it is.

:D
[Xoom Android Development] russtyd:
You need to be in the folder where adb.exe is located before running the command - on my Windows 7 x64 its in "C:\Program Files (x86)\Android\android-sdk\platform-tools" (on 32-bit OS it will be C:\Program Files\Android.....)"

Start a command window, then type

cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"

it should work after that...

My only concern is if you didn't have the skill/knowledge to work this out for yourself you probably shouldn't be trying to root your Xoom .... next post will be "Hey Guys, I bricked my Xoom... what do I do" :cool:
[Xoom Android Development] majdinj:
The size problem started on Eos-wingray-44 after announcing that it would support ntfs format USB devices.. realy I don't know what happened. Does this ntfs stuff eats the rest of the space in system partition or what:confused::confused::confused:
[Xoom Android Development] Blondblueyed_girl:
Hi chethammer, yes I had the same brightness problems on nightly 47. Am on nightly 48 now and that doesn't happen.
[Xoom Android Development] liftman-:
brd is working on it, its the face lock stuff it seems, give them a few days.

if you do not use face lock you can delete /system/vendor/pittpat and you get 25 megs. I think that was what was left in hc
[Xoom Android Development] Boarder277:
@p0yraz I have a Windows 7 machine, and the easiest way to be sure it works is to open the folder that you unzipped and saved ADB to and hold ctrl + right click and select "open command window here" then try typing in the command window "ADB devices" and if it returns a serial number your in business and can go ahead with the rest of the commands...
[Xoom Android Development] stonebear:
If I do "ADB devices" I get nothing back, if I do "fastboot devices" I get the serial number back, I don't know why...

I managed to install CWM anyway, the instructions are -

"adb reboot bootloader

fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img

fastboot reboot"

and I connected my Xoom in fastboot mode (power and vol down)

and just did -

"fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img

fastboot reboot"

Maybe you can get round it the same way...

------------------------------------

Anyway, I wanted to say thank you to TeamEOS for this lovely ROM. :)
[Xoom Android Development] joshndroid:
You need to have debug option enabled in settings lol
[Xoom Android Development] technoghost:
Exchange Mobile Device Profile corrupted after flashing rom

Thanks,

My Exchange server has a corrupt mobile profile that I cannot delete???:confused: Any suggestions?

Thanks everyone!
[Xoom Android Development] majdinj:
Rooting Xoom:

===========

1) Install the driver "MotoHelper Driver" from the following link and install it in your computer: http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers

2) In your Xoom --> settings --> applications --> development --> check USB debugging

3) Plug in your USB cord

4) Download Universal Xoom Root from the following thread and place in the root of your SD card (not in any folder!!) http://xdaforums.com/showthread.php?t=1242241

5) Copy the following attached folder "adb" into the root of the C drive on your computer so it will be like this: "C:\adb"

6) On your computer, open up a command prompt, write the following command:

"cd C:\adb" then press enter key... you will be now in "adb" directory.

7) Copy and paste the following one line at a time into the command prompt followed by hitting the enter key after each line:

Code to unlock your xoom:

adb reboot bootloader

fastboot oem unlock

8) If reboot again to the system, be sure that you still in USB debugging mode

9) Download Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from the following thread http://xdaforums.com/showthread.php?t=1074979 and put it inside C:\ADB folder

10) Copy and paste the following one line at a time into the command prompt followed by hitting the enter key after each line:

Code to flash the ClockWorkMod recovery mode (CWM mode):

adb reboot bootloader

fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

fastboot reboot

11) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.

Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.

12) In cwm, go into "install zip from sdcard" --> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.

Note: use the volume buttons to navigate and the power button to select

Reboot your device and then welcome to your rooted device!

At the end I would like to thanks solarnz for making this possible :)

​
[Xoom Android Development] rschenck:
Notify your network admin that they need to fix their profiles and certificates.
[Xoom Android Development] ricardowec:
I noticed n50 updates to a new kernel. Do I need a full wipe? . (DATA/FACTORY RESET) ?
[Xoom Android Development] rschenck:
I don't believe so
[Xoom Android Development] ricardowec:
I noticed N50 - N51 updates to a new kernel. Do I need a full wipe (data/factory reset) ?
[Xoom Android Development] rschenck:
Again...NO. Full wipes are usually required in one of four situations:

When changing to a completely different ROM (not just a new kernel or an update of your current ROM)

When changing Gapps versions (when advised to do so by Devs)

When running into serious performance/connectivity problems

When captured by Cyberdyne Security and lack the time to completely destroy/incinerate your Tablet
[Xoom Android Development] zacharias.maladroit:
unfortunately those "general" capacitive stylus models are way to thick

you can't really write with those (I got an Acer Stylus-Pen Duo)

the Dagi Stylus and Adonit Jot it look like they're the best ones for this purpose

stylus-support works with this ROM already ? - haven't seen anything saying the contrary

I've got the German MZ604 so using this ROM should be no problem right ?

[first gotta find some nice guide to prepare it, unlock bootloader, etc.]

nice to see you here, btw :)
[Xoom Android Development] okantomi:
Any WiFi Xoom can use this Rom because the hardware is the same. You will only need to get your language support set-up.

On the stylus issue, I have the Adonit Jot, and it's great.
[Xoom Android Development] rschenck:
Hey there Zach! Welcome aboard.

First use this guide (by the gentleman just above me) for rooting and all that good stuff....http://xdaforums.com/showthread.php?t=1249798

Beyond that, you are going to LOVE this ROM...a lot like CM but without all the idiots...well....MOST of the idiots.
[Xoom Android Development] Muffycheeks:
Is anyone else having these problems since flashing #51?
[Xoom Android Development] alesandro:
Thanks ,, amazing :)
[Xoom Android Development] philly0128:
I've tried nightly 50 and 51. download, whip cache and delvick, installed rom/installed gapps and on both roms I can't get the market to open. anyone has this issue or was this mentioned in another thread. if so I haven't found it yet... still doing some searching.
[Xoom Android Development] rschenck:
Check the EOS wiki in my sig for some market solutions to try. Look in the how-tos.
[Xoom Android Development] banny7000:
I've just installed 51 I've had market freeze antutu benchmark crashed twice and one random reboot,I've installed every nightly bar a couple and never had issues until now.has anyone who has done a full wipe had any issues?
[Xoom Android Development] jrock60:
The first version i have installed is 49 and it seems great with the exception of a slightly lower benchmark coming from Moray. My question is this:

If I want to update my build to the newest nightly can I just apply the zip over what I have now and not lose anything? Can I do the same if I want to revert back to an earlier build?

Please let me know.
[Xoom Android Development] rtb35:
Not sure if it has already been posted but I thought I would let people know that with v51 and the latest update to the game itself GTA3 is now fully working on this rom. I have just been playing it for 40 minutes at least and did not have a single crash.

Also I would like to take this opportunity to say thank you to team EOS for their work on this fantastic rom :)
[Xoom Android Development] banny7000:
Just done a full wipe on 51 market and antutu seems okay but my keyboard just froze and had to force reboot so I'll give this build a bit more time any more trouble and I'm back to 49
[Xoom Android Development] Peterpaulmarie:
Same here. Reboots with n51. I went back to 50.
[Xoom Android Development] eckka:
I also had problems with lockups with v51. Autorotate seemed to cause/bring on the problem.

BTW I'm still looking for an answer to the USB OTG problem!
[Xoom Android Development] banny7000:
Is it possible to install 50 over 51?
[Xoom Android Development] rschenck:
Of course
[Xoom Android Development] Antzor:
Nope, battery life for me is INSANE. Unplugged for 12 hours sitting beside my bed = 2% battery drain. battery stats show it going to sleep as well
[Xoom Android Development] mnaim:
Still no solution for wifi leap protocol support. Something wrong is happening in wifi stack.
[Xoom Android Development] bigrushdog:
Yes rest assured we know wifi and Bluetooth are not perfect yet. We are still learning and getting used to the. 39 stack. It will get worked out in time.
[Xoom Android Development] ggrant3876:
Had same problems here, except I was just turning wifi on. I think I'll just stick it out until 52 tomoirrow.
[Xoom Android Development] xBlackDroid:
I've this issue....

When i try to copy some files to /system/lib, say "not enough space"

I used rootfile to do this action, this happened with Build 49/50 with fullwipe..

Any idea to fix it?

Thnx
[Xoom Android Development] liftman-:
last build will leave you about 9m. if you need more and not using face lock you can delete safely delete /system/vendor/pitpatt. that will give about 18m more.
[Xoom Android Development] xBlackDroid:
I just installed the last build 51, and all work perfectly again

Thanks for your answer man :)
[Xoom Android Development] stonebear:
I have debug enabled, I still get no devices listed if I do "ADB devices" but I get the serial number if I do "fastboot devices".

edit

I am talking about when the Xoom is in fastboot mode, "adb devices" gives me back a serial number when the Xoom is booted up into android. I guess it is normal, lol.
[Xoom Android Development] rockhumper:
have you tried mount or remount then devices (sorry I forget which command works..) I had the same issue and that fixed it for me.
[Xoom Android Development] jonman364:
Installed 51 and gapps 10.4 at 9 this morning. Used off and on throughout the day. At 4, copied a file to internal storage over USB and left work for the day. At 9 I went to use my Xoom again and it would not turn on. No security light on short power button press. Plugged it in and the charging light did not come on. Connected via USB to my PC, it was not detected. Power + volume up and it powered up.

This is the first time this has happened. It was scary. Any ideas? I have not messed with overclocking.
[Xoom Android Development] keunhuvac:
Xoom is hang and reboot 2 times when im playing game, never got this problem b4.
[Xoom Android Development] joshndroid:
I had this on 49 just yesterday ey

Sent from my mind control device
[Xoom Android Development] stonebear:
"adb remount" worked. :)

Thanks.
[Xoom Android Development] dj_ghosie:
Hi SolarNZ and Team,

Just some suggestion to your already great rom, would it be possible to move the EOS buttons to the clock pop up box after pressing the clock, ala CM's power button style?

It seems to be one too many steps to get to those quick toggles and kinda duplicate with is of the standard quick settings if they appears on the same page. The standard ones could serve as a more advanced setting sine u have to dive into the setting page.

Seems like everything is functioning as I should and to the stage of optimization, nice!

Thanks a lot, Team EOS!
[Xoom Android Development] toyscooter:
I'm having the same issues with multiple nightlies. About ready to change to another rom. 1st time it happened I freaked but then found that power + volume up would boot it. I can be using it and it just locks up then goes black. Yes, I did follow instructions for install and I actually do a full wipe between installs and still have the issue.
[Xoom Android Development] dsbnz:
Ive had a few lockups and reboots since installing 51, which has only happened on 51, never on earlier builds.

(did the usual flash rom then gapps before rebooting.)
[Xoom Android Development] bigrushdog:
Ok. Enough is enough. From this point forward all bugs need to be reported at

http://bugs.teameos.org/

All "bugs" posted here will be ignored. There is far too much crying and sniffling and not enough development discussion. I will be asking moderation to aggressively clean up this thread.
[Xoom Android Development] wmfreak:
Has similar experience this morning. went to turn my xoom on (from stand by) as my notification light led was blinking but it would not turn on. I tried pressing the power buton for a little longer but no luck. it finally booted after I bfiefly pressed volume up and then power. Donno what the deal was but hated it. Nightlies 47

W
[Xoom Android Development] wanderfowl:
Why might "media server" be using 85% of my battery on a day when my Xoom has been mostly sitting on a bedside table unused? Build 48. Never had this before.
[Xoom Android Development] rschenck:
You may not be using it, but sounds like one of your apps is going to town without you.

Now you just need to figure out which one...
[Xoom Android Development] banny7000:
52 seems a good one for me,everything's working well thanks again teameos
[Xoom Android Development] ricardowec:
I just had my first unwanted reboot on 52 while swiping the home screen. It happened on hour after flashing,

I had not a single problem with 51

Edit: ive been running at 1.408 with no problems since 39. Have switched to 1.200 now

Edit: just had a FC while editing with XDA premium.

In order to flash I did as usual. Wiped cache and delvik
[Xoom Android Development] Xoom Master:
Would that affect it?
[Xoom Android Development] masterslacker:
I had three random reboots yesterday while using the browser and just scrolling a page. I was on 51 at the time, and had no overclocking at all. I wipe cache and dalvik cache with every flash, and have never had any issues until now.

I went back to 50 and it has been stable since. I think I'll wait a while before flashing a new one.