yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] dinomight:
If you are on the vanilla tiamat 1.4.2 kernel then yes, you have to install this kernel. This kernel should be identical to the 1.4.2 kernel but also adds the necessary UMS features. After flashing this kernel via clockwork mod recovery you can install the app, or is you still have the app installed from hc 3.0 it will just start working again, no need to reinstall. I would however recomend downloading the via the marketplace do that updates happen automatically.

-D
[Xoom Android Development] dinomight:
You can access the sdcard via /external/ if you are using MTP. Motorola didn't enable access to you device via UsbMassStorage, but opted for mtp. Most if not all other android devices support UMS. The sdcard is accessible via mtp if it is mounted within /sdcard (internal storage) (ie /sdcard/external). However mtp isn't always supported by an os/device. UMS is preaty standard. It's hard to find a device that doesn't support UMS. By using this app (and supporting kernel) you can have your xoom sdcard accessible via ums. It will appear as a standard usb flash drive. With the new OTG support you could even connect your xoom to another xoom and access the sdcard via ums mounting. This is something mtp won't do. Does that all make sense?

-D
[Xoom Android Development] bigrushdog:
There might have been a slight misunderstanding regarding UMS support. I will build UMS in all kernels from now on. The issue is I can't come up with a clean native implementation. That's where you come in. Also, I don't know how this app manages mounting. That's why I said mods to ramdisk and Vold are up to you. Heck, you may not even need any additional mods. I don't know. But kernels themselves will have full UMS support.
[Xoom Android Development] okantomi:
So BRD, if I have flashed your most recent Tiamat 1.5ghz with to oc gpu, can I justflashthis new kernel over it and have the best of all worlds?
[Xoom Android Development] DroidHam:
Are there any drawbacks?
[Xoom Android Development] DroidHam:
installed the UMS kernel, installed the UMS app, mounted it but when I goto my PC all I see is the Xoom, not a extra drive for the sd card. Did I miss something? do I need the OTG cable or something?
[Xoom Android Development] mcarrion78:
i just flashed and it works as advertised. nice work
[Xoom Android Development] hoopsdavis:
I seem to be having issues, I just installed the new kernal with UMS but when I get to the UMS connect screen, I select the "Turn On USB Storage" button it just sits there and spends not mounting. Any ideas?
[Xoom Android Development] Lolento:
Brd,

So does this mean the 1.4.2 kernel with gpu oc has the ums function?
[Xoom Android Development] tomcrown1:
with the ums kernel I am not getting mass storage also the clock speed is only 1.4mz. Should it not be named to 1.4 since it does not do 1.6?
[Xoom Android Development] PensFan66:
I have a similar question - Running the Tiamat 1.5 OC with the GPU OC - Should I use the add on in the first post for UMS?

EDIT - Nevermind, I should have looked - the zip in post 1 is the entire Tiamat with UMS enabled .. :) Thanks!
[Xoom Android Development] PensFan66:
Any ideas why I cant get this to work?

Im using the 1.6 with UMS and in terminal I can see different sdb1, but the USB Mounter doesnt show me a thing, it never comes up at all?
[Xoom Android Development] holtenc:
same problem here
[Xoom Android Development] dinomight:
Did you install the kernel from the first post? That is the kernel that you must have installed. If you just installed the kernel from the other tiamat page it will not work. If you don't have a ums kernel you will not see the popups. One more thing this mounts the sdcard only. So if you don't have an sdcard attched then it will not work. This doesn't attach the internal storage as ums just the micro sd card. (i might look in to see if that is possible...)
[Xoom Android Development] PensFan66:
Yep - I have the 1.6 UMS from post 1 - BUT ... I was trying to use a USB Thumb Drive with it .... I was hoping it would mount :)

So I just tried with an SD Card that workd for my Clockwork mods and in my Xoom if its in when I reboot. So I rebooted with no SD in, got to the Xoom screen, and no alert / nothing. In the external directory it says Empty Folder.

Any ideas?
[Xoom Android Development] T33H00:
I flashed the kernel, installed the USB app. however, when I plug the USB in with OTG Motorola connector, it doesn't work.
[Xoom Android Development] neaux:
hello,

I installed the kernel 1.4.2 ums (Xoom firmware 3.1) and I have a usb otg.

when I plug an external drive, I see him turn on (LED on the external drive) but nothing happens on Xoom.

I have installed the application USB Mass Storage Watcher

Can you help me please? I have misunderstood the function?

thank you
[Xoom Android Development] dinomight:
This app does not currently handle otg drives. It's original purpose was to restore UMS notifications. That is to say the notification that is supposed to appear when the xoom is connect to a computer so that the xoom can act as a USB mass storage I.e. like s flash drive.

That being said I am working on new features that will allow the app to manage otg devices. It should be out very soon. I'm just looking for a more elegant solution for detecting when otg devices are connected. (If anyone knows how to get the USB connected intents to fire please let me know. I'm thinking it's broken, not sure if its because of the kernel or if it's just a broken API.)

-D
[Xoom Android Development] T33H00:
keep it up! we need it

thank you
[Xoom Android Development] dro1dfan:
Thanks great app.

BRD has implemented UMS in 1.4.3, but now app hangs when trying to enable UMS, just keeps having swirling circles (have enabled SU). maybe needs update.

But still thanks for all ur earlier work, it definitely works on earlier kernels
[Xoom Android Development] Hexbug:
I just updated to 1.4.3, and have no problems with either the SD Card or plugging a thumb drive in. It sees the files on both just fine. I thought it enables UMS automatically? I don't have to manually do anything (other than plug the thumb drive in). Also, I do not see any swirling circles (or any other type of notification for that matter). ?:confused:
[Xoom Android Development] b0ricua:
ditto, same behavior for me. I'm sure dinomight will be on it sooner than later

Thanks!!!
[Xoom Android Development] Brevi:
I have the spinning circles on 1.4.2 1.6Ghz UMS kernel from first post and also on the new 1.4.3. I have a Euro 3.1. Xoom (unofficial 3.1. install).

Thanks for your work!!

Chris
[Xoom Android Development] dro1dfan:
Thumb drive and SD card hve nothing to do with UMS, USB Mass Storage is when you plug it into a PC
[Xoom Android Development] cboy82:
i have the latest kernal and running 3.1hc on uk xoom when i plug the xoom into the pc i just got a debugging notice , the xoom gets mounted as a device not as a hdd so i cant ftp into it from another computer?

is there a way to get the xoom to show in windows as a normal external hdd or is it just device?

just installed busybox now i see usb but its just spinning
[Xoom Android Development] sanosuke001:
I have the same issue; US WiFi Xoom, have 1.4.3 kernel installed, connect to PC via USB, open the enable USB page on Xoom, hit the connect button, all I get is a blue spinning disk.
[Xoom Android Development] dinomight:
Updates, Problems, Solutions, Adb Logcat.

Hey Guys,

Just wanted to give you a quick update. The new version of the app is coming along very nicely. It should be ready very soon. I've gotten otg drives to properly send the intents to the app. Now it will run when you plug in an usb drive via otg cable. This was a huge step. I've also got the app polling the system for loaded kernel modules (this is needed to enable fs types (fat,ntfs,ext,hfs,hfs+) and will load the proper module when needed. I can also get a list of attached drives their partitions with their partition types and sizes. Pretty much all that is left is interface stuff. So in summary the back end is finished just a little interface design and it will be ready for release.

Sorry to hear people are having problems with the new kernel. I'm currently on the newest kernel and everything is working for me. It's near impossible for me to troubleshoot when i can't replicate the problem, so i will need some help from the people who are having the problem. Could someone experiencing the problem send me a log cat from when you connect to a computer all the way until you press the button and get the perpetual spinning indicator. The thing with it is that once you see that page with the click here to mount usb button you are no longer in my application. At that point you are using android's own interface. That doesn't mean we can't diagnose the problem, but it probably means my app has very little to do with it. It would also be nice if someone could get online tonight and work with me (trying new builds and sending logcat's until we can fix this).

For those people having the problems can you check the following (sorry if these are obvious but i need to be certain the problem isn't user error)

1. you have an microsd card inserted in to the xoom.

2. you have the "external" folder in your xoom's internal memory (path = "/sdcard/external") and by this i do not mean your microsd card has a folder called external, but that the internal /sdcard/ folder has the directory.

3. can you browse through the microsd card from within the xoom. (i.e. use somthing like root file explorer and navigate to /sdcard/external/ and see if you can see files.)

4. is your microsd card formatted fat32?

If the answer is yes to all of these and you are still having the problem then we have something. if you answer no to any of these let me know which one, then try to fix it and try again, then report back.

-D
[Xoom Android Development] sanosuke001:
I'm at work right now and don't have my Xoom with me but

1. you have an microsd card inserted in to the xoom.

a. yes. 32GB Patriot and I have the 8GB card in my Driod X I can test with as well

2. you have the "external" folder in your xoom's internal memory (path = "/sdcard/external") and by this i do not mean your microsd card has a folder called external, but that the internal /sdcard/ folder has the directory.

a. Without my tablet I cannot confirm but I am 95% sure it is there and mounts correctly; it worked correctly in 1.4.2

3. can you browse through the microsd card from within the xoom. (i.e. use somthing like root file explorer and navigate to /sdcard/external/ and see if you can see files.)

a. Again, I cannot confirm but I am fairly sure

4. is your microsd card formatted fat32?

a. yes. formatted on my laptop to fat32 and worked/read correctly for 1.4.2

I will be home in ~4 hours (5pm EST) if you need someone to help diagnose things. (I can even write code myself to speed up the process if you know what you need but don't have the time). Just let me know what logs you need and I'll post them ASAP
[Xoom Android Development] dinomight:
Thanks, That's exactly what i need. As for getting me the logcat just run "adb logcat" then clear out your console buffer, then click on the links and attempt to start the mass storage device. after a little while (while it hangs) copy what was output by logcat and send it to me. I won't be able to work on this until about 8 MST (-7) so 10 your time. Unfortunately my day's and afternoons are booked up with work and kids.
[Xoom Android Development] sanosuke001:
Not a problem, man. I'll get that log to you as soon as I get home. Let me know if you need anything else.
[Xoom Android Development] sanosuke001:
So not quite sure if I'm missing something or not, but when I do adb logcat I get a couple exceptions in Videos.apk (I'm assuming because they disabled it on the Xoom because the MPAA are *****es) and in libdrmwvmplugin.so, it unpacks the umswatcher-1.apk fine (no exceptions anyway).

I re-run adb logcat after I tell the usb mas storage app to connect but it just sits at "- waiting for device -". What do you mean by, "then click on the links and attempt to start the mass storage device"? Also, logcat exits after the first call (before I tell it to mount the USB Mass Storage), is it supposed to keep printing out appended info?

doing an "adb reboot" after ctrl+c'ing the adb logcat says, "error: device offline" so it must disconnect the usb entirely for some reason.

Let me know if there's anything else you need.
[Xoom Android Development] sanosuke001:
Also, /sdcard/external does exist and it does show the contents of my 32GB sdcard. I tried to go to /dev/log/system (where logcat says it's reading from as far as I can tell) but it doesn't exist (or root explorer doesn't want to display it for some reason) so I can't check directly.

I'll keep poking around until I hear back from you.
[Xoom Android Development] sanosuke001:
So it looks like after killing processes and rerunning logcat I got some ums info/exceptions to print out. I'll pm you the text file.
[Xoom Android Development] sanosuke001:
Also, updated sdk and it fixed the logcat quitting issue. Still got the same ums exceptions that I sent you in that pm so I'm not going to send you a new dump unless you request one.
[Xoom Android Development] dinomight:
Windows... Oh how i hate thee.

Ok so i'm narrowing things down a little further. I'm experiencing a similar issue (not sure if it's exactly the same) When i try to use this with windows. In my case the spinning indicator goes away but the drive never shows up in windows. Can anyone else confirm that they have it working in windows with the 1.4.3 kernel? At first i thought it might be a conflict with mtp running, but after getting mtp to work on my linux machine i'm starting to question that theory. I've tested on osx,ubuntu, and windows 7. Windows 7 was the only one with any issues.

Anyone else out there on windows that has ums working? Please let me know which version of windows and whether or not mtp is running. I'll keep trying to nail this down. If I can figure out how to disable the mtp service from within the xoom that might help me eliminate mtp as the culprit. I'll keep you up to date, and thanks to those who sent logcats. i'll pm you if i have something else for you to test. I doubt i'll make any more progress tonight (sorry) i just through out my back and i'm in horrible agonizing pain. I'm going to drug up and sleep.
[Xoom Android Development] sanosuke001:
Thanks a lot for the continued work; definitely appreciate it!
[Xoom Android Development] mradlauer:
If you'd like some help beta testing, i have some time to donate. I am especially interested in getting hfsplus going because i only use a mac. I have vmware of windows and an ubuntu distro as well.

Excited to see this come to fruition! Its something i actually need to do my job at times.
[Xoom Android Development] jmc2543:
Ok I am very very confused. According to Bigrushdog, if I am understanding it correctly, UMS is "stock in build." Does this mean that the current kernel 1.4.4 will work? I have the 1.4.4 installed (along with this app from the market) and its not working?
[Xoom Android Development] phonepersonality:
I'd like to know this too please :)
[Xoom Android Development] youngproguru:
Me As well. Newest 1.4.4, app from the Market.

The app reports that when USB is inserted, and gives me the option to mount, however all I receive is a spinning circle, and Windows (and Ubuntu 11.04) do not show any activity.
[Xoom Android Development] KidJoe:
It might be similar..

For me... Windows 7 Pro (32bit), Verizon 3G Xoom, 3.1, with either the Tiamat_Xoom-v1.4.2_1.6Ghz_UMS.zip (from the OP), or Tiamat_Xoom-2.6.36.4-v1.4.4_Full-Throttle_stockGPU.zip (from the other thread) kernels, and either the v1.1 APK from the OP, or v1.1.1 from the market... the following happens...

Connect via USB

Windows sees it and autolaunch comes up (its in MTP mode)

Hit the "USB Connected" in the notification area on the Xoom

USB mass Storage screen comes up with spinning circle in upper right corner

tap "turn on USB Storage" button.

button is replaced by a spinning circle (that makes two on screen now)

after a long while, the spinning circle reverts to button saying "turn on usb storage"

So when you say the spinning indicator goes away but the drive never shows up in windows. What do you mean by goes away?
[Xoom Android Development] stevefxp:
Hello all,

I have tried the new kernel but I never get past the Motorola boot screen. It just hangs right there. I am also using the updated CWM 3.2 on this Xoom. Is anyone running into the same issue?

Thanks,

Steve
[Xoom Android Development] ClydeB1:
I've seen a few other posts about this. It seems that Tiamat 1.4.4 and CWM 3.2 don't play nicely together. I'm going to hold off on the CWM upgrade until this gets sorted
[Xoom Android Development] dinomight:
New Version Huge changes check post 1

Changes galore, See post #1 for all the details
[Xoom Android Development] Brevi:
Thanks for your hard work dinomight. However the App (with OTG) crashes immediately, when usb plug is inserted. Windows 7 Pro 64bit, Xoom 3g european model with 3.1 US rom installed.

Thanks again and greetings from germany!

Update:

Just to clarify. I tried connecting to Win7 Computer via normal usb cable with 1.4.4 Tiamat Kernel. No OTG stuff.
[Xoom Android Development] pyrator:
force closes with otg cable and tiamat rom from brd
[Xoom Android Development] dinomight:
Can you pm me the logcat of the crash. (clear the log, run the app , send the remainder of the log).
[Xoom Android Development] Stealyourface:
I found the Easter egg. But email wouldn't send :-(
[Xoom Android Development] dinomight:
FC fixed (i think). Download the update from the market. And if you were having the problem please report back on whether or not it was fixed.
[Xoom Android Development] dinomight:
Ok email address fixed you can email in now (but i'll add you to the list.) It was easy right?
[Xoom Android Development] dinomight:
Can anyone think of a good prize for finding the easter egg (other than name in credits). Something that's free (since i've made ~ 1$ on ads). Any ideas?
[Xoom Android Development] iammodo:
Gamecih forces you to click on the add and wait till its fully loaded before you can you the app,might be an idea.

Also not sure my problem.

got a working otg cable works with Xbox controller,keyboards, and what not if I plug in a SD reader it shows up in mtd/otg.

But in your app it comes up as Dev/block/sda. 0mb

Shows data In astro in mtd/otg am I doing something wrong?

Sent from my Tablet
[Xoom Android Development] Epedemic:
Thanks for the update. It looks nicer than the old version.

However i have had a strange problem even with the old version. The sdcard mounts fine on my pc, and i can copy files... However, when the files are copied, the apps on the xoom (astro/file manager) does not see the files untill i reboot the xoom. Then they work just fine.
[Xoom Android Development] dinomight:
I don't really care about making a lot of money off ads i just wondered if anyone can think of a cool free prize for finding the EE

If you see /dev/block/sda than the system has seen a device attach. which is good. Did it prompt you to choose an app/give permission when you attached the drive? To see whats wrong can you do the following. when the device is attached can you bring up a shell and type the following:

fdisk -l /dev/block/sda

(you might need to change sda to something else. look in /dev/block/ for sd* devices. Android currently has a problem where it doesn't reuse sd* names, so if you plug in a device the first time you get sda, the second time you get sdb and so on.) PM me with what you get from the fdisk command.

-D
[Xoom Android Development] dinomight:
This is a bug in the ums implementation. It's a bug within the kernel. I've been looking for a way to fix this but it requires kernel modification and i still have yet gotten to the point of getting the kernel development env set up. This is the next thing i'll be working on, and hopefully with some help from BRD I can get cracking at it.

To all:

Can you report your device, os version, rom, kernel that you are using. Also if you've messed with anything (kernel, vold, etc) i also need to know this.

-D
[Xoom Android Development] kfernandes29:
Still Force Closes immediately when opened.
[Xoom Android Development] dinomight:
Wow I can't believe it was so easy. I found a working solution that didn't require recompiling a new kernel. Honestly i can't believe that what i tried happened to work. I'm not sure if it will introduce any bugs but it is possible so look for them. You can get the latest version from the market.

Can you send logcat? And make sure you're on the latest version. (i see a stack trace on my market debugging screen (kinda cool it logs the errors and crashes and then i can browse through them from my android developers publish pages). I think i found you (11:16pm) And that error should have been fixed.
[Xoom Android Development] Stealyourface:
Yes, it was. Funny as well.
[Xoom Android Development] iammodo:
Okay in your app I see the string /sda. But if I use astro to look at the file path I don't see any files sda or b or c.

Yet in astro I can see the files on the pen drive.

Can't do the shell command as not at a PC.

Felling like a noob now.

Sent from my phone
[Xoom Android Development] Mandelbrot.Benoit:
3G Xoom, Tiamar ROM and Kernel. I can see files in file explorer from SD card. USB watcher propmts and gives same 0mb reading as others have reported. /dev/block/sda 0mb.
[Xoom Android Development] sanosuke001:
Tiamat 1.4.4, UMS OTG installed, nice Easter Egg by the way :P

Get an infinite loop of logcat messages, will PM you a dump.
[Xoom Android Development] dinomight:
For those that are not seeing a size on sda or another drive i found the problem. I'll upload a new version when i get home.

-D
[Xoom Android Development] iammodo:
Eeeek cant wait

Sent from my phone
[Xoom Android Development] dinomight:
New Version - More issues fixed

Ok i've uploaded another bugfix version to the market (2.0.8) This fixes a bunch of problems.(including a runaway timer that i found myself.:-)) Thanks so much for all of the testers. Keep up the good work. If you find something after upgrading to 2.0.8 let me know. As far as i know everything is good now.

-D
[Xoom Android Development] Steady Hawkin:
Awesome tool, thank you very much!
[Xoom Android Development] myv6mustang:
Easter egg.....damn damn damn damn!!!!!
[Xoom Android Development] Mandelbrot.Benoit:
Downloaded 2.0.8. No better. Still 0mb. Cleared data and cache no good. Uninstall/superuser clear and reinstall no good.
[Xoom Android Development] dinomight:
is there anyone having the 0mB problem online that can test the builds until i can confirm the problem is resolved.

-D
[Xoom Android Development] T33H00:
hello!

I got the usb connected but it always says 0mb, please fix
[Xoom Android Development] iammodo:
Ill be online at 7pm uk time.

Or you can email me builds and ill test, will be at work so no adb

Sent from my phone
[Xoom Android Development] dro1dfan:
awesome work! OTG support is much appreciated will give it a shot.

i guess i can unintall the old on :)
[Xoom Android Development] dro1dfan:
BASTARD! found the easter egg
[Xoom Android Development] adamtuba:
Lol at rickroll.

Nice work btw, not getting 0mb issues here.
[Xoom Android Development] dro1dfan:
guys, just a quick advice:

if u are getting 0mb issue, connect to ur PC and activate mass storage (or deactivate if it activates automatically). this will bring up the SU permission screen, you can click accept.

I found that this solved the problem for me. (not sure if this is a fix or co-incidence)
[Xoom Android Development] T33H00:
hello!

Thank you fir hard work. I kniw a lot of people get it to work but me (0mb) which is really sad for me. I already updated to 2.0.9 but still no word. Please let me kniw if you need test build or something
[Xoom Android Development] REHolt218:
i loaded version 2.0.9 but am still getting the 0mb error. I sent an email earlier.

I would be willing to test you fixes if need be.

By the way, I found the Easter egg.