yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] mutiny:
I'll gladly do that if it can help out the devs/community. I'll post results in a bit.

I own a US WiFi Xoom bought about a week and a half ago from Amazon.
[Xoom Android Development] cam30era:
Yes. I have no /external folder inside sdcard.

I was just re-reading the OP. I did not download Scripter and execute the script, because BRD stated that it was for 1.4.0. Could this be the problem?
[Xoom Android Development] mutiny:
Do you have sdcard2 inside sdcard? Or were you instructed to create said folder prior to flashing?
[Xoom Android Development] i_am_the_one:
Did you try creating the /external folder?
[Xoom Android Development] cam30era:
No to both questions. So, should I create sdcard2 inside sdcard and the reflash the 1.4.1 kernel?
[Xoom Android Development] siscim23:
The script was only a mass storage thing, /external should have been created when you flashed 1.4.1.

Try creating the folder like i_am said
[Xoom Android Development] bwcorvus:
blah blah blah
[Xoom Android Development] mutiny:
Okay, a couple of things. Previously, I reported that 1.4.1 was a no go for me because my PC no longer sees "Xoom" (MTP not picking it up). So I reverted back to 1.3.2.

Fast forward to the present, I just tried doing the bwcorvus and it said "error: device not found". I found that weird because I'm using the same laptop I used to root this Xoom in the first place and I never had this issue before. Moto drivers are installed, I'm in cmd and in the right directory where adb is, etc.

So, I flashed back to 1.4.1 but before doing the commands, I checked to see if the internal and external drives were visible and they were!!! This is excellent news because I really want to stick to 1.4.1. But when I did adb, I'm still getting the same error, that the device can't be seen. WTF? This is really weird.

I have Windows 7 Ultimate 64-bit on this laptop. When I hooked up the Xoom on this laptop, I used to get that tray icon popping up saying something like device is ready and now I'm not. I checked if the Moto drivers were still there and they are. The funny thing though is that I downloaded and install 4.9 but it's now 5.0.

I'm feeling like a complete noob ATM.
[Xoom Android Development] mutiny:
Awww, man. I take it the vold.fstab didn't do it? I was going to try it but I can't even get adb to see the Xoom.
[Xoom Android Development] cam30era:
OK, I created /external inside sdcard. Then I reflashed 1.4.1 via CWM. Still can not see anything inside the external folder.

Any other suggestions?
[Xoom Android Development] bwcorvus:
Did you by chance make sure debug is showing up? Also no the vold didnt work.
[Xoom Android Development] mutiny:
I meant to hit quote but my awkward position on this laptop made me thank you instead. LOL.

Here's what I can tell you. Instead of going straight to 1.4.1 when rooting, do it the same way others who has had 100% success (now includes me --yay!) did.

We rooted into 1.3.1, created sdcard2 under sdcard, flashed to 1.3.2, checked to make sure sdcard2 is now the microSD card, flash to (a) 1.4.0 and let it create external under sdcard and in the same process empty out sdcard2 or (b) flash to 1.4.1 and sdcard2 is still your external microSD card or kept external if you came from 1.4.0.

But in reality though, I think BRD only yanked out the whole mass storage thing that he borrowed from Android phones for 1.4.0. So 1.4.1 should still create external the same way 1.4.0 did. Again, I'm not sure because 1.4.0 did create external for me, but 1.4.1 (I must have flashed back and forth a dozen times) never created an external folder... BUT I've always had sdcard2 from the 1.3.1 to 1.3.2 flash and in 1.4.1 it's my microSD card once again.
[Xoom Android Development] mutiny:
Damn it. Noob mode indeed. Lol.

Let me try again. I didn't have debug. :p
[Xoom Android Development] bwcorvus:
Alright i do think the problem is in the vold.fstab. I just reflashed 1.4.1 just to look at the log, there is no vold.fstab in the zip, and none created. I assume it is just using the one you already have. As soon as brd gets on tonite, ill chat with him to confirm. So if you get the "right" upgrade the file stays correct, if not you have no /external sdcard.
[Xoom Android Development] mutiny:
That makes perfect sense! I think BRD assumed everyone would be on the same page as him and coming from 1.4.0 to 1.4.1. He didn't anticipate others flashing directly to 1.4.1 maybe? I don't want to put words in his mouth but I suspected something alone those lines.

And here's the ss I took.
[Xoom Android Development] cam30era:
OK. I just tried to flash 1.4.0 from CWM. Got following error message:

E:Error in /sdcard/tiamat_xoom-v1.4.0.zip

(status 0)

Installation aborted.

Suggestions?
[Xoom Android Development] bwcorvus:
Alright you vid_mem is different then mine...BUT the part i think makes the difference...i DONT have no_console_suspend=1 :)
[Xoom Android Development] bwcorvus:
Common error, try mounting sdcard and system in the mounts menu then run again. 1.4.1 uses a different script to kill the error.
[Xoom Android Development] mutiny:
The only way many of us could flash into 1.4.0 was through KM, not CWM. BRD has since fixed that bit so that flashing would not produce that error. Unfortunately, KM is acting up right now.
[Xoom Android Development] cat2115:
hi, i use rom manager to flash from 1.3.1 to 1.4.1 and i myself do not see "external" folder anywhere in the directory. i check in sdcard, i check sdcard2 and non to found for "external" folder. Do i have to creat manually? I remember with 1.4.0 it automatically created the "external" folder. but if coming from 1.3.1 to 1.4.1, no "external" folder beside sdcard2 folder
[Xoom Android Development] Land Master:
Hmm' ... Well obviously you mounted the card in Clockwork and was able to navigate to the file or it wouldn't know the file name. I would venture a guess that this is probably a path/mount problem though. I'm thinking that flashing 1.4.0 first was probably the way to go.

And...while I am here....The 1.4.1 Change Log has not been created but I recall that when I viewed 1.4.1 in Kernel Manager that it said SD Card "stuff" was removed. Maybe BRD will get a chance to clarify and let us know if he agrees in flashing 1.4.0 first. TIA.
[Xoom Android Development] cam30era:
A big "thank you" to bwcorvus and all who helped me with this. I did as suggested above, and was able to successfully flash 1.4.0 via CWM. This did create an external folder inside sdcard, and it did have my files on it. I then reflashed 1.4.1 and all is good.

Thanks a lot, again.
[Xoom Android Development] Hexbug:
My LED is always lit too when plugged in... whether off, in standby, or on. I am running 1.3.2, but I believe mine was like that from day 1. I am going to try 1.4.1 shortly and see if anything changes with that. BTW, I have the wi-fi model, if that makes any difference..?
[Xoom Android Development] bwcorvus:
I believe 1.3.2 was the one kernel that had it. Well that we knew of until today ;)
[Xoom Android Development] joeski27:
Yeah you are correct, but I've been pushing for this to be put back. I really liked being able see the charge status while the Xoom is sitting on the dock.
[Xoom Android Development] mutiny:
Nice. Glad to hear I am not alone in this. Let us know how the update goes for you.
[Xoom Android Development] Land Master:
OK Guys don't flame me.....please

Does the "Easy scripter Script" from the OP need to be setup and run or not?

I took the language to mean that it was "built in" to 1.4.x Kernels but upon reading more thoroughly I believe just the hardware (on board reference) was enabled in the Kernel and the Script (application) is needed to "turn it on"

I ask because when I plug in the Xoom I get an Auto-play pop up and have access to Both internal and External SD Cards through explorer. External being accessed through the "external" directory.

Granted my Xoom say's it is being accessed through Debug mode but if I can get to the drives who cares? What an I missing by it not indicating "Mass Storage"?

TIA
[Xoom Android Development] Hexbug:
Ok, I am now on 1.4.1 and my LED has not changed. Still staying on when plugged in (whether on/off/standby). Cool! :)
[Xoom Android Development] mutiny:
The feature you speak of is deprecated. But to answer your question, the script was ran using the scripter app to emulate what you see on other Android devices pre-Honeycomb. BRD explained it in more than one post if you read back a few pages.
[Xoom Android Development] mutiny:
Fist bump. Lol.
[Xoom Android Development] siscim23:
Don't quote me on this, but I think 1.4.1 uses whatever folder you already have for the external card. In your case, you have sdcard2 as the external card folder, so 1.4.1 will continue to use that folder. 1.4.1 will use /external if you were coming from 1.4.0. Again, not 100% sure about this, will someone confirm?
[Xoom Android Development] gerbick:
I can't say the same. Lost it with 1.4.0 and it hadn't come back.
[Xoom Android Development] zonk7ate9:
The LED light has always worked on all Xooms since launch, however, it was configured to come on only when the device is off. There is simply a setting in one file where you can chose to enable when the Xoom is on. I believe BRD turned changed this setting in 1.3.2 and then back off in 1.4... it tripped me out because I couldn't believe I didn't notice it before. As was speculated earlier in the thread Moto probably thought this would be annoying if you were using it plugged in during low light situations (like watching a movie). Personally I like it off when the Xoom is on, the LED is way bright and the light is not welcomed while I'm sleeping ... its way brigther than the charge light in my Nexus One.
[Xoom Android Development] cj10488:
Guys and possibly gals. For those that previously flashed my charge light modified 1.4.0 update the charge light shall stay as the boot.img file was unchanged in this update. For others that want the charge light flash the modified charge light 1.4.0 file then update to the newest 1.4.1 kernel and all should be good.

James
[Xoom Android Development] mutiny:
I hardly ever have my Xoom off so when it's charging and on standby in the dark, I like to know when I can unplug it. I guess you're lucky then that yours is as is should be. We'll see what the rest wants and what BRD decides to do in future updates.
[Xoom Android Development] jlaw904:
Im trying to use cifs manager to access a network drive. And I keep getting a "no such device" error. Would it have anything to do with the 1.4.1 kernel? (I haven't done this on any other kernel). Please help!
[Xoom Android Development] Archangel:
Did this and it worked perfectly you just have to flash the new 1.4.1 through clockwork recovery or else the charge light stays off. Tried installing through kernel manager and no charge light after being on the mod 1.4.0, thanks!
[Xoom Android Development] dro1dfan:
i think you may have to insmod the cifs.ko so that cifs manager can see it. would post a better answer but im not at PC.

i think in adb shell try:

insmod cifs.ko

then enable it in the cifs manager settings
[Xoom Android Development] kevdog:
I came from 1.3.2 to 1.4.1. I used to have a white charge light when charging with the device in standby. Now I got nothing. Is this normal?

clarify : standby not off
[Xoom Android Development] mutiny:
You get nothing even with the device off? That's not normal.
[Xoom Android Development] hm1b:
Is there is a way to roll back to 1.4.0? I tried using recovery it will not work
[Xoom Android Development] mutiny:
I could never flash to 1.4.0 using CWM but when KM starts working again, you can use that to go back.
[Xoom Android Development] cam30era:
Reboot into recovery. In CWM choose mounts and storage. Choose mount external SD. Then flash 1.4.0 from your external SD.

Note: this is a common problem.
[Xoom Android Development] mulletcutter:
On xda app so search sucks, but how do you manual boot into recovery? One of yhe themes i flashed i guess got messed up and everything FC so i cant get to clockwork.
[Xoom Android Development] mutiny:
Does anyone else hear the speakers make that raspy "TSK" sound? My Xoom does that once in a while.

I'm posting this here because this started as soon as I got 1.4.1 working perfectly last night. Meaning, everything was fine except for MTP not seeing my Xoom. Last night, I don't know what I did differently but the device's internal and external drives could be seen again. The only problem now is the "TSK" sound I get.
[Xoom Android Development] siscim23:
Yeah I've gotten that before. Only happened once though.
[Xoom Android Development] cam30era:
Download the app "quick boot " from the Market. This will allow you the option to reboot to recovery.
[Xoom Android Development] lewi3069:
I'm guessing since I followed this guide http://xdaforums.com/showthread.php?t=1058272 that is why my sd card dosent work. I flashed directly to 1.4.1. I am going to go back and try downgrading to 1.4.0 then to 1.4.1
[Xoom Android Development] Land Master:
Sorry you experienced difficulties but that guide does recommend that you start with 1.4.0 and THEN flash 1.4.1. It recommended this in the disclaimer at the top of the thread when the 1.4.1 link was added, even before it was made "official" through Cam3era's trials.

Either way Cam3era was able to get this sorted exactly as you suggested. Flash back to 1.4.0 and then forward to 1.4.1.

Good luck!
[Xoom Android Development] mulletcutter:
Nothing would work, everything would fc and couldnt open anything...just had to hook it up to a computer and adb reboot recovery
[Xoom Android Development] jawonder:
I'm not seeing anything in my Gallery after flashing 4.0.1 and my icons on my home screens which came from the Gallery are now colorless . If i flash back to 1.4.0 using Kernel Manager will that correct the Gallery and icon problem ?.
[Xoom Android Development] hm1b:
thank you for your help... i rolled back to 1.4.0 but did not fix the problom I am havining in :

http://xdaforums.com/showpost.php?p=13442311&postcount=1576

can you help?
[Xoom Android Development] hm1b:
I flashed back from 1.4.1 to 1.4.0 ....it did not fix the problom...all music albums use to be in music are not there evan after flashing... every thing use to be in sdcard such gallery, music is not there anymore... you can accsses it through file explorer ...

also, it is read only
[Xoom Android Development] kev0153:
Try this

Go to manage applications and go to all applications. Find something called media storage and hit clear data. It forces to rebuild all media on the device.
[Xoom Android Development] hm1b:
I tried it is still the same. I think the problem coming that the external folder permission shows

external rwxrwxr-x.....

I wanted to change permission but whenever i chose to make it rwxrwxrwx it will accept the it will go back again immediately to rwxrwxr-x!!!! it is not changing
[Xoom Android Development] mutiny:
What does the mount say? Change that first then change permissions.
[Xoom Android Development] hm1b:
permissions:

mount r/w

I tried also, r/o "I thought i try it any way" well it is the same result...I get no control over my external folder....now everythime i want use it i boot to recovery and mount the sd card from there. it is a big hedach. I don't know where is the probloms!!
[Xoom Android Development] jawonder:
In 1.4.0. everything was good but with 1.4.1 the image files are there in SDCard2 and Exteral but they aren't viewable when the file is open i have to click on each individual image then the Gallery opens up and i can see that image , if just go to Gallery or try to put a custom icon on my home screen from the Gallery it tells me that the Gallery is empty .
[Xoom Android Development] hm1b:
I rolled back to 1.4.0 ...I hope things will be amazining on the custom rom BRD promised. Thanks for the info.
[Xoom Android Development] starcms:
I can't read this thread without getting frustrated by some people's ignorance. There is absolutely nothing wrong with 1.4.1 and SD cards. I wish KM had never been made. Too many idiots not knowing what they are doing. And it's so simple anyway.

BRD, please keep up the great work and don't get discouraged by a few!!
[Xoom Android Development] mbroeders:
totally agree! Amazing work brd! Unlocked and rooted yesterday, and of course installed your kernel. All went smooth and easy. The kernel is running great. Looking forward to seeing more of your work in the future...
[Xoom Android Development] mutiny:
Hahaha. I'm one of the people who were spoiled by KM but I don't rely on it completely to flash though. I do agree that too many are taking shortcuts and not reading up and trying to learn first before asking. It makes BRD look like he's the one who screwed up. Not so.
[Xoom Android Development] judison:
Mass Storage

Hi all,

I have rooted today, instaled 1.4.1 direct, but after reading here, reverted to 1.4.0 then flashed 1.4.1

the content of my sd card is in /mnt/sdcard/external (AND /data/media/external (???))

so it's rightly mounted...

when I start the UsbStorage activity

# am start -n com.android.systemui/.usb.UsbStorageActivity

the dialog shows up (with a progress indicator in the right top corner that never stops)

when I click the button sometimes I'm asked about ative apps using data (normal stuff) but most times I don't get this

the button in replaced by a progress indicator,

and it never ends, nor get a mass storage device available in pc..

I get this from logcat when I click the button to enable mass storage

I/PackageManager( 119): Updating external media status from unmounted to unmounted
D/VoldCmdListener( 83): volume unmount /mnt/sdcard force
W/Vold ( 83): Attempt to unmount volume which isn't mounted (1)
D/VoldCmdListener( 83): volume share /mnt/sdcard ums
E/Vold ( 83): Unable to open ums lunfile (No such file or directory)
E/MountService( 119): Failed to share/unshare
E/MountService( 119): com.android.server.NativeDaemonConnectorException: Cmd {volume share /mnt/sdcard ums} failed with code 406 : {volume operation failed (No such file or directory)}
E/MountService( 119):	at com.android.server.NativeDaemonConnector.doCommand(NativeDaemonConnector.java:258)
E/MountService( 119):	at com.android.server.MountService.doShareUnshareVolume(MountService.java:511)
E/MountService( 119):	at com.android.server.MountService.access$200(MountService.java:78)
E/MountService( 119):	at com.android.server.MountService$UmsEnableCallBack.handleFinished(MountService.java:307)
E/MountService( 119):	at com.android.server.MountService$MountServiceHandler.handleMessage(MountService.java:411)
E/MountService( 119):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/MountService( 119):	at android.os.Looper.loop(Looper.java:126)
E/MountService( 119):	at android.os.HandlerThread.run(HandlerThread.java:60)

Am I doing something wrong???

what should I do?

-----

another question, can I hot swap this SD card?
[Xoom Android Development] bwcorvus:
Mass storage was removed in 1.4.1.
[Xoom Android Development] scotty1024:
I personally lay the issues at Motorola's feet. If Motorola stepped up and released SD Card/USB storage support people wouldn't be so desperate to dive into doing things that are beyond their grasp.

I agree completely: BRD, keep up the good work!
[Xoom Android Development] siscim23:
No, that's not available yet. Typically, even adding/removing files to/from the external card requires a reboot for the changes to be seen.
[Xoom Android Development] zonk7ate9:
Do you happen to know the full changelog for 1.4.1?
[Xoom Android Development] jlaw904:
Does 1.4.0 or 1.4.1 support CIFS?
[Xoom Android Development] kevdog:
yes . I know 1.4.1 has the cifs module
[Xoom Android Development] pyrator:
nice, now to add the NTFS binary's
[Xoom Android Development] bug_nuts:
am i mental? do i need to have 1.3.2 installed to attempted 1.4.1? SD card doesn not mount... at least on my mac if i try usb mount in Clockwork recovery..
[Xoom Android Development] cam30era:
If you flash 1.4.0 from CWM, then 1.4.1, your SD card should mount. Worked for me.
[Xoom Android Development] thefredelement:
clockworkmod has it's own kernel, the version you have on the system has nothing to do with it.
[Xoom Android Development] forsaken82:
does the 1.4.1 update support usb hosting? i realize 1.4.0 to 1.4.1 is th eway to go for the sd card support but not sure about the usb hosting. im getting my xoom tomm and am still a little new at this, so please bear with me
[Xoom Android Development] pof:
Please add support for the following options in next builds:

CONFIG_USB_ETH=y

CONFIG_USB_NET_CDC_EEM=y

CONFIG_USB_NET_CDC_SUBSET=y

This allows to wifi-only xoom users to tether via USB using an android's phone 3G data connection (with a microUSB to microUSB cable like this: http://yfrog.com/hsnxhmzij )

Thanks!
[Xoom Android Development] cam30era:
This would be a great feature!
[Xoom Android Development] lokko21:
Yes indeed..!!

Evo Better Than The Best...
[Xoom Android Development] SS2006:
Is SetCPU Neccessary for overclocking to 1.5 ghz

or will the xoom scale the speed up to 1.5 ghz on its own

thanks
[Xoom Android Development] TsaiKimon:
ya you have to install setCPU. You can download cpuSpy for free and you'll see how the processor is being used before you setup setCPU
[Xoom Android Development] saleum:
"Understanding How Your Xoom And SD Card Behave in Tiamat Xoom 1.4.0"...

A couple of questions:

- Is this valid also for Tiamat 1.4.1 ?

- The script is very nice but what is its use ? I mean, if I am in Linux with script or without it, I cannot mount anything. If I am in Windows, everything is mounted in the right way, so "sdcard2" is included as a directory in "sdcard" and I can transfer to/from it anything to the computer. So, why the script?

Sorry if my questions are stupid... perhaps I haven't discover some wonder in all that script-stuff. As the kernel in itself is already a wonder and works wonderfuly, it is possible that something has been disregarded by me. ¡Incredible job!
[Xoom Android Development] Land Master:
I asked the same question a few days ago. That script is no longer used. While it would probably work in 1.4.0, "Mass Storage" support has been removed from 1.4.1.

You said it correctly.....You can get to everything you need by simply plugging in so the script is NOT necessary anyway.
[Xoom Android Development] c0t0d0s2:
Are people still having random reboots with these kernels? Because I am.

Where should be be submitting crash dumps if we do?

http://pastebin.com/hUmrYyAU

Here's one of mine, which I will submit to the proper place once I know what it is...

EDIT: No overclocking, and wifi sleep policy is set to "NEVER"
[Xoom Android Development] mutiny:
Which version did you flash from?
[Xoom Android Development] c0t0d0s2:
I've been flashing these since 1.3.1. (is that what you meant?)
[Xoom Android Development] mutiny:
Sorry for the confusion. I meant which version did you have prior to flashing 1.4.1?

I'm asking because there might be a pattern with others who are having similar problems as you.
[Xoom Android Development] ericdabbs:
What are people getting in quadrant and linpack values in v1.4.1? I have been getting linpack values of 35-40 at 1.5 GHz and quadrant values ranging from 2200-2500. Is it just me or does the Xoom lag more in 1.4.1 than in previous versions when swapping screens?
[Xoom Android Development] Archangel:
Quadrant scores are a little slower (which was never really a good determiner for cpu speed for me) but linpack (mflops) was a lot higher.
[Xoom Android Development] ericdabbs:
What were you getting in linpack (mflops) values? At this point, I will probably revert back to 1.4.0 since I am not impressed at all with 1.4.1.
[Xoom Android Development] bigrushdog:
I updated my OP with a few things. In the 3rd post, we now have Tiamat Modpacks. Also, removed old, unsupported kernels. Rebooting is likely caused by the borked overclock mod. This is an issue me and Cybertronicz are working on to fix. In fact, i consider it the most pressing kernel issue on the table. Make sure to read all the new OP's so you can be up to speed. thx

brd