yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] iammodo:
Oaky so online now, to test and give logs or what ever.

but just tried plugging it into my pc (win764bit) and it came up on the computer fine. but on the app it just had a spinning wheel. go back into the app and it just had the ( mount usb device)

hmm ill just unplug the cable then.

bam xoom frozen

had to hold power till it restarted.

still nothing when i plug in a usb drive to it just 0mb.

any help from dev suggests asks?
[Xoom Android Development] iammodo:
Anyone getting the omb I've been trying to test and give logs to the Dev he is slowly getting there.

hope for us yet.

Sent from my Tablet
[Xoom Android Development] dinomight:
Yep I've been at it most of the day. Slowly going since I can replicate the issue on my xoom. But we are getting there. I've already figured out one part of the problem. Hopefully some one else will be able to get online in a few hours to test with me. Anyone who is available in three hours pm me we can chat on google talk. I think I can get this worked out tonight... the. On to new features...any suggestions?

-D
[Xoom Android Development] sanosuke001:
Just tried it on 2.0.9 and I get the same spinning disc. I wonder if it's an issue with the MTP dismounting the internal storage so your app can't mount it? logcat keeps spitting out /mnt/sdcard no such file or directory errors when root explorer definitely shows it as existing. I'll send you my new dump via pm. Also, if you need a guinnea pig, I'll be around; I'll give you my google talk address
[Xoom Android Development] dinomight:
Help me out

Ok so i'll be online for the next few hours so someone who is having the 0mb issue that can test with me please pm me and we can start to work... The good news is that i actually figured out how to adb and debug a remote device (across the internet) I tested from my tethered laptop to my xoom sitting on my internal house wifi. If you want to help me out here are the instructions on how to get setup.

1. Make sure usb debugging is turned on on your xoom.

(method 1 - requires working adb)

2a connect your xoom to the usb port on your computer.

2b type the following "adb tcpip"

2c disconnect your xoom from your computer.

(method 2 - requires a console/terminal app installed on your xoom)

2a.bring up the terminal

2b type the following:

setprop service.adb.tcp.port 5555

stop adbd

start adbd

---- Continuing on -----

3. visit http://www.whatismyip.com/ on your xoom and send it to me.

if you have a 3g xoom and don't mind using your 3g connection you're done. You're setup and i can now debug with your device.

---- Continuing on (just wifi) ----

Now we just need to setup your router,

4. get the ip address of your xoom (go into settings->wireless & networks-<Wif-Fi Settings -> click on the connect wifi network to see the settings)

5.you need to setup port forwarding on your router. Log in to it.

6. Find the port forwarding section and add the following ports to forward

forward ports:

port: 5555

port range: 8700-9999

7. assuming you did the steps properly then your done. I should now be able to connect to your xoom and debug

With this setup i can upload builds automatically, run it and see logging, errors step through the code. Basically everything i need to workout this problem. All you will need to do is look at the screen occasionally.

Without this I'll have to email you a file, you'll install it, you'll run it, you'll tell me what happened, i'll probably have you send me the log cat, then i try changing the code, send you the new version.... and so on.

if your on 3g it will be much faster on wifi and would be preferable even if the setup is a little harder to do.

I really hope someone is online tonight that is able do this and test with me.... Right now i'm trying to fix the 0mb issue. so that's the type of person i need.

pm me or even better google talk with me (administrator@skidmrk.com)

-D
[Xoom Android Development] T33H00:
I tried to reboot uninstall, reinstall and still have the same problem. When I connect it with my MAC, It asks for mounting and when I click mount, it just runs the circle thing.
[Xoom Android Development] kymikes:
Sorry for a noob question but I'm not sure I understand the interrelations here. I'm running a US WiFi Xoom just received a few days ago. Updated to 3.1 OTA and then progressed to the Tiamat ROM 1.0. I was not able to see the contents of my microSD card through Root Explorer but could access the card thru cmw 3.2.0.0 using mount USB storage. Don't as yet have my OTA cable so my testing is limited. When I loaded your app, I get the same Win Explorer popup of my microSD card that I got through cwm mount (definitely easier that booting into recovery) but I still don't see the SD card content through Root Explorer. When I unmount the USB storage through your app, the Win Explorer window closes (as expected) and I still don't seem to be able to see the SD card content thru Root Explorer on the Xoom. Is this the expected function or have I managed to disable my ability to view the external SD contents w/o having to mount?

Hope this isn't a really ignorant question but trying to understand the basics before my OTA cable gets here and I try more expansive testing. Thanks in advance for your help.
[Xoom Android Development] iammodo:
mtd/sdcard/external
[Xoom Android Development] dinomight:
Ok so here is a little more information that i've found. You need to have busybox installed. Tiamat rom 1.0 has an olderversion that doesn't have blkid as a tool. I've adjust things to gracfully handle the lack of blkid but in this case settings will not be saved for a given partition. I'm working on a busybox detector and downloader so that you don't have to worry about having it. Here is a link to busybox that i use https://market.android.com/details?id=stericson.busybox&feature=search_result install the app then in the app download the lastest stable.

Now on to other bugs..... There is a big issue with the system trying to automount fat partitions when a device is attached. in tiamat's rom this has a lot of issues.... much more so than the stock. I'll work with brd to get these fixed, and for the time being i'm working on a work around. Also with tiamat 1.0 rom the intents are not getting sent when a device is connected. This means no notification of drive, app won't start up automatically on insertion, and the pages don't update on insertion/removal. I'm working on a solution to that but i don't like it.... there is a reason those intents were added to the 3.1 sdk. Without them i have to leave the application running and polling the filesystem for changes (i don't like this).

So for those of you with 0mb issue. this is fixed and will be uploaded today... those on tiamat 1.0 anticipate some issues and hopefully i'll have a funky patched version today as well. For everyone: for the time being download busybox, that will resolve some issues.

I'll post again as i make progress. I huge shout out to REHolt218 and ArA for the great deal of time spent debugging with me. We should all thank them for their time.

-D
[Xoom Android Development] iammodo:
And a little shout out to me

Sent from my phone
[Xoom Android Development] kymikes:
OK, I'm confused. Thsi version of Busybox (3.4.6) when install on my Xoom running Tiamat 1.0 causes me to hang at the red M on reboot. Had to reflash the ROM to recover. Was there something else to do beside install the updated Busybox?? I'm back to where I was but cautious about re-attempting the Busybox update. TIA for any guidance.
[Xoom Android Development] kymikes:
If this was in response to my post, I'm guessing you meant /mnt/sdcard/external. This folder is empty whether I have mounted or not. Should it be showing the external card contents when not mounted? Thanks for your answer.
[Xoom Android Development] REHolt218:
I have had some problems with installing the latest busybody from the Market. It causes my Xoomto crash and then it will not reboot. It gets hung at the Dual Core screen. I was forced to restore the system partition and then reflash the ROM 1.0.

It happened twiceo I have pretty well narrowed it down.
[Xoom Android Development] dinomight:
sorry

I'm so sorry guys it looks like there is some problem with that busy box in combination with the tiamat rom. So for now don't install it we can just use the work around that I have in my latest build (not on the market yet.... later tonight I promise). I've chatted with brd a little and I think we can work together to make the umswatcher work better with the rom. I know there are things that need fixing rom side and things brd wants a little different, at least in a future rom update. But for now I will have workarounds that will gracefully handle whatever setup you might have(until some other rom/config through a wrench in the machine) for now that means a working version that works for both the tiamat rom and for vanilla rom again sorry to anyone affected by the busybox no reboot problem.... so once again to everyone DONT INSTALL THE OTHER VERSIONON BUSYBOX.

Thanks again to everyone bearing with me while I work this all out and thanks to the testers.

-D
[Xoom Android Development] okantomi:
please dinomight, what version of busybox should we use and how can we get it if we have already followed earlier advice and updated? Should I reflash the Tiamat rom? I'm afraid to reboot now.

Damn, I should have stopped tinkering.
[Xoom Android Development] dinomight:
So Sorry about that ... i got peoples google talk names incorrectly associated with their forum names....

Iammodo: definately deserves a shout out for the help testing.
[Xoom Android Development] dinomight:
anyone who downloaded and installed the busybox i suggested on the tiamat rom(i believe that is the only thing affected. I'll post a link to the actual busybox, just copy to the xoom and overwrite the one you installed (/system/bin/busybox or /system/xbin/busybox)

I had to push mine to /system/xbin/busybox .... now this is very important... make sure you give busybox execute permissions before the adb push... here is what i did

adb remount

chmod 777 busybox

adb push busybox /system/xbin/busybox

That's it...

if you're in windows i'm not sure how to give ti the right permissions ... this is what i'd do in that case.

adb push busybox /sdcard/busybox

adb shell chmod 777 /sdcard/busybox

adb remount

adb shell cp /sdcard/busybox /system/xbin/busybox.

Now i just need to figure out why the tiamat rom dies with a different version of busybox.... and find one that works.... i'm going to work with brd so that a working up to date version is include in the rom. I'm on gtalk if anyone needs help.... (administrator <at> skidmrk <dot> com)

PS i just need a tester to test out the latest build on their device (i've tested it on the tiamat rom and i'm in the process of reverting to the stock rom to test on that, but if someone wants to run it on their as an extra tester it would help... hit me up on gtalk.) By the way i'm avoiding the whole busybox uuid issue for now. But everything still works as before.

-D
[Xoom Android Development] dinomight:
Ok,

I built my own busybox based on the latest stable build 1.18-5 ... built just fine and installed in into the rom. i was able to reboot with the new busybox without any issue. I'm not anywhere close to an expert on this but if you are feeling brave you can go ahead and try to install my version. All i know is that it works for me. I'm going to talk to brd and see if we can get it into the next tiamat rom.

If you do try out my busybox report back any success you might have. Don't forget to chmod the busybox binary. By the way i copied the existing busybox to busybox.bin.... again i'll be on gtalk tonight (at least for a little while longer) should you need help or can help test.

-D
[Xoom Android Development] dinomight:
if you do get hung at the Motorola logo as a result of the busybox binary you can fix this easily without a full rom restore....

use the busybox that was in the link a few posts ago (not the zip i attached) and

adb remount

adb push busybox /system/xbin/busybox

you are able to access adb from the moto logo or from the recovery mode. and if you really want to know what the problem is:

adb shell

adb logcat...

i found that the broken busybox caused an error (which looks like the compile options)

run-parts can't find /system/etc/init.d

tiamat rom doesn't use that path..

I hope this helps anyone who has got stuck at the moto logo.... no more reason to freak out
[Xoom Android Development] iammodo:
Are you trying to see the SD card by the sim card port?

You will need to be running tiamat kernal for that.

Have you done that?

Sent from my phone
[Xoom Android Development] dinomight:
Ok new build is up.... and i think it's good for both stock and tiamat roms. Lots of fixes but little to be seen (other than it works correctly). This should handle vold's automounting of single fat partition devices. (tiamat has some problems with the vold automount but it shouldn't matter to me.) If it's automounted by vold then i see it... if not that the app knows about it. Once this is in fact stable i can start adding more stuff. (any requests). Since the first build of v2 (ie UMS watcher OTG) This really has been a all testing and bug fixes... haven't been able to really focus on anything else. Other than a few little things i wanted to add (and anything anyone suggests here) i will be able to move on to porting to pre 3.1 devices (those devices don't handle otg offically or within the sdk so i didn't want to bother)

Let me know of the bugs you find with the latest build (i'm sure there are some.) Thanks again to testers and users (and easter eggers) (I'm going to go to bed now.

-D
[Xoom Android Development] rajones19:
Loaded the new version this morning, but at first was faced with instant forced-closes as soon as I plugged a flash drive onto the cable. After reviewing messages posted here during the night, I used BusyBox Installer from the market (Stericson's app), installed BusyBox version 1.18.4, and so far it's working marvelously. Thanks so much for all your hard work on this!
[Xoom Android Development] zeroxg4:
Do you teach philosophy at HU by any chance?
[Xoom Android Development] kymikes:
Yes. But along my path (currently on ROM 1.0 but had the same issue with Tiamat 1.4.4) I had a couple of stumbles (flaky USB port, user error, etc.) and someone commented I might have deleted the /sdcard/external folder and therefore wouldn't see the SD card contents. I didn't lose that folder but I have never been able to see the SD card contents unless I mount the USB storage and then I can see it via Windows explorer (with USB connection in debug mode). Since I am still a bit new to these functions, I thought that once on the Tiamat kernel, I should be able to see the SD card from the Xoom. It seems a bit confusing since there are so many folders on the Xoom side that "might" be related (/mnt, /sdcard, /MicroSD, etc.) but I have not been able to find the SD card contents anywhere on the Xoom side, mounted or not. My understand is that you can only have the folder mounted on one side or the other at one time (makes sense) but I seem to be able to only get to it from the PC side or cwm flash.

Have I missed the boat? Thanks for any advice.
[Xoom Android Development] dinomight:
TIamat Busybox....

It looks like i forgot to include the link to the busybox used by the tiamat kernel... for those who had issues with busybox causing bootloops. push this busybox version onto your xoom (/system/xbin/busybox)

https://github.com/solarnz/Tiamat_Xoom_Rom/blob/master/system/xbin/busybox
[Xoom Android Development] dinomight:
I'm not sure about the fc's... i need to check this out.... I guess it's possible that it happens when busybox isn't installed at all (I thought that it was installed on both the stock rom and tiamat.) I guess i'll revert all the way back to stock to see what it does and does not have.

-D
[Xoom Android Development] rajones19:
Nope, sure don't. Not even sure what HU is!
[Xoom Android Development] dinomight:
New version out.... now it checks for and downloads if needed busybox. Such a pain in the butt to install busybox when i need busybox to do the cp. :-) Let me know if anyone is getting any more fc's This will only download busybox if you need it.... that should keep things happy with roms that have busybox already installed. The app downloads busybox 1.18.5 (latest stable build). I compiled it myself and tried to include all of the busybox modules/applets.... I'm not an expert on tuning busybox but it will do the job.

So i had an idea for a new feature let me know what you thinl:

Desktop Widget... see mounted devices, mount and unmount from within the widget..... I've never done widgets so i don't know what is installed but thought of the idea last night while i was sleep deprived. Any other idea's for features you'd like to see.

-D
[Xoom Android Development] okantomi:
That sounds really great. I would absolutely use it.

And thanks for all your hard wwork!
[Xoom Android Development] dro1dfan:
When i triple tap the android, I now get a downloading file pop-up. what is this file?

Was hoping for a video ;-)
[Xoom Android Development] dinomight:
Oops i left that in for debugging.... please update now... we don't want that file to download (it's busybox)...

The new version (released 5 seconds ago) has this removed.
[Xoom Android Development] bigrushdog:
I'm gonna give the new busybox build a run. I was gonna build my own blend, but didn't have the energy to focus on it. i grabbed the zip from ur post about 6 up or so. If you have another build in mind, let me know. Also, I'm gonna start digging into this hfs+ issue too. I know all the Mac guys are itching for that.
[Xoom Android Development] dro1dfan:
done - too easy
[Xoom Android Development] Dynagem:
Using Tiamat Rom just downloaded the absolute latest update of app. I can mount. I see the drive via root explorer in /usbOTG and i see the files but i can't open( in the case a jpeg). It seems the drive is r/o. I click mount r/w and it doesn't register. Drive is r/w fully (checked on my pc). So i am lost. So close but so far....
[Xoom Android Development] T33H00:
can you add the refesh button into the app?

Also please let us know the paypal address, i would donate some (even though its just a little) for your hard work with useful app
[Xoom Android Development] rkboid:
Just downloaded from market and it fc,s every time. Running tiamat
[Xoom Android Development] kymikes:
Just d/l update also. I DIDN'T have an FC's.
[Xoom Android Development] rkboid:
ok unistalled, rebooted, reinstalled and now no more force closing. It iss not registering my USB but I am sure that is a problem on my end. My USB mouse works but not the thumb drive
[Xoom Android Development] armychris28210:
i can mount, and see the drive<500gb western dig external> i see the files<music,pics,etc>but when i try to open, the cant be viewed...music cant be played. if i drag and drop to xoom, it works fine, its just accessing from otg drive thats an issue.... i also have a msg under my drive info in saying

"blkid missing"...anyone? but i am very excited to see my drive and info there now on a usb powered HD...thanks man!

im
[Xoom Android Development] dinomight:
Can you try to unmount and remount the drive.... Also the blkid issue has to do with an out of date busybox .... i have a workaround that will download a local busybox with just the features needed for the app (won't mess with or override any existing version. I should have that update released tonight.

-D
[Xoom Android Development] dinomight:
also how are you trying to open the files are you using something like astro file manager.... what is the parition type?
[Xoom Android Development] iammodo:
I still get that error on fat32 8gb pen.

can't wait for this new busybox fix.

Sent from my Tablet
[Xoom Android Development] iammodo:
Can you plug the drive in then use astro to go to

/Dev/block and tell me how sda you see?
[Xoom Android Development] armychris28210:
ok, its a Ntfs partition,and in astro, i have sda and sda1...sda1 is the one that its on. i tried unmount/remount....etc, but...i can see the files when using ESmanager, when using astro, there are no files in my usbOTG folder.
[Xoom Android Development] dinomight:
New version (bug fixes, credits, new easter egg)

New version on the market.... go and get it.

I think this will fix a lot of problems (all of the one's i'm aware of). Check out the credits.... the testers definitely deserve recognition.

Also there is a new easter egg. (much more difficult to find). And don't worry it's not a rickroll. The old easter egg is still there so don't bother looking there.

Please report any issues. I hope this tides us over (bug wise) until i am able to do a feature release. (desktop widgets?)

Any suggestions would also be appreciated.

-D
[Xoom Android Development] armychris28210:
If god had a tablet...

It would be a xoom.

You da man.. But seriously.... works ehfing great. Mounts my usb powered 500 gb western digital, and a 2tb hd no problem. All files show and its quick too.. now I'm trying to see battery drain. This is a serendipitous occasion. Seriously.
[Xoom Android Development] Dynagem:
Taken a step back

With last update I was able to find my drive(4gig flash), mount and see the drive via Root Explorer. I just could not open files. It said my drive was R/O. I tried to hit R/W and nothing would happen. Like it was defiant on changing the drive type for file use.

With this update i am back to the: /dev/block/sda 0MB screen.

Running Tiamat 1.0

Busybox installed
[Xoom Android Development] okantomi:
Hi dinomight, do you have any idea why I am unable to install this app? I tried to upgrade and it told me (in app) that I had an old version and needed to uninstall it. I did and now I can't install the new version.
[Xoom Android Development] dinomight:
oops

I am aware of the installation problem. I made the mistake of uploading the new build before leaving the house. As soon as I'm back home I'll upload the fix. It appears that the issue is caused by a certificate signing problem.(not sure why I know I signed it.)

Any who the new version doesn'have and new fixes. But what it does include will definately help fix them. There is a new menu option that allows you to email me debugging information. It should send me all of the information that the app is using(what is has determined from the system. Should you have an issue use this option and I can fix the problem. I'll post again as soon as the fixed properly signed app is back up on the market ~2hrs

Sorry for the mix up.

-D
[Xoom Android Development] dinomight:
ok market version should be installable..... for those with bugs/errors use the new menu option... "email debugging information to developer."
[Xoom Android Development] dinomight:
Please uppload the debug information using the new menu option. I'll look at your problem as soon as I can... what kernel are you using? Can you email me a link?

-D
[Xoom Android Development] okantomi:
I downloaded and it works great! I will leave a comment on the market for you. Thanks!
[Xoom Android Development] Dynagem:
Emailed you a link. I am using the native kernel included with tiamat 1.0. Thank you for your attention on this.
[Xoom Android Development] hoopsdavis:
i was able to get the latest release installed, the issue im having is when I connect to the PC, (windows 7 64bit) I select the "Turn on USB storage" button, it spends a few seconds and nothing happens.

Debugging email sent from the app.
[Xoom Android Development] bappems:
I'm getting the same thing... Debug message sent as well.

Mark