yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] tbayne:
As far as I know this is all about mount points, if you want to understand them do a google search.

If you DON'T have an sd card installed the directory "sdcard/sdcard2" will act like a regular directory (the mount of the card into "sdcard/sdcard2" will fail). If a card is in the slot, then the card will be "mounted" on "sdcard/sdcard2" - and data written to that directory will be written to the card.

The reason for the move of "sdcard2" under "sdcard" was to allow gallery (and other apps that default to "sdcard" for data reads/writes) to be able to write to the card. If you don't put "sdcard2" under "sdcard" gallery (and probably other apps that are looking for sdcards) won't see it.

(then again I could be wrong but this is my understanding of how it works)

Terry
[Xoom Android Development] admiral70:
I just got carious, I took my SDCard out and it rebooted. Upon booting up I plugged in and saw the sdcard/sdcard2 entry but nothing in it. I reinserted my sdcard, again force booting came up plugged in and see sdcard/sdcard2 with data in it. It is differently reading the card just no visual proof of it.

One of those trust things that is hard sometimes.
[Xoom Android Development] jnrandall:
Now I have it! :D Thanks to all.

I removed an old 4GB sdcard and used the one in my Nexus One. Once I rebooted, I see all my files from the phones 16GB card/Class 6. Must be the old 4GB card.

Thanks again, :D
[Xoom Android Development] bwcorvus:
On 1.3.0 it showed up as sdcard and sdcard2. This made it where your computer and android programs (other then file managers) couldn't access it. In 1.3.1 he moved the mount to inside sdcard (ie sdcard/sdcard2), this allows your computer and some android programs (gallery) to see it.
[Xoom Android Development] kev0153:
When looking under about Tablet. It shows my kernel version to still be 2.6.36.3Tiamat_Xoom-v1.3.0-gc02ada7

Is this right? I just flashed 1.3.1
[Xoom Android Development] bwcorvus:
yea its fine.
[Xoom Android Development] andybarron:
I did disable USB debugging
[Xoom Android Development] JungleJiujitsu:
If the OP says "adb shell, mkdir, /data/media/sdcard2, exit" why is everyone creating "/sdcard/sdcard2" instead? I just want to make sure I am doing this correctly, TIA!
[Xoom Android Development] i_am_the_one:
i just used columnar to create sdcard2 inside sdcard and it works perfectly
[Xoom Android Development] JungleJiujitsu:
Ok, nice! Mine was not working but thanks for confirming that it works when created directly under sdcard. Will reflash boot and push modules again, now that I have created the folder in the right location!
[Xoom Android Development] kcrudup:
"/data/media" is the real name on the internal flash that is eventually turned into /sdcard" by the "sdcard" service.
[Xoom Android Development] dascope:
You must reboot the Xoom to see/access the MicroSD card... it's NOT hot-swappable. Something to keep in mind :)
[Xoom Android Development] jnrandall:
Thanks :o
[Xoom Android Development] Synman:
A simple modifcation to titanium backup will allow it it to now use it too :-)
[Xoom Android Development] JungleJiujitsu:
Mine is still not working, I created /sdcard/sdcard2, flashed boot.img, pushed modules but when it boots back into the device I still don't see anything in /sdcard/sdcard2...I should note that I pushed the modules from a folder on my desktop. Would it make a difference if I replaced the modules in the Tools folder with them instead so that I just enter the commands as posted in OP, w/o C:\"path"\modules?
[Xoom Android Development] ilovechi23:
for the life of me i cant get my xoom to get passed the protocal screen.... once i reboot into bootloader it just stays at that screen and i have to hold power and vol up to get xoom back on... any ideas why this keeps happening?
[Xoom Android Development] Squeak22:
When you make the directory in /data/media/sdcard2, should you change the owner and group to media_rw?
[Xoom Android Development] JungleJiujitsu:
I went ahead and placed the new image and files into the Tools folder so that I could just copy and paste the commands exactly as they are posted and I still cannot see anything when I navigate to sdcard2. I used androzip to create the folder, and I was able to mount an sdcard with v1.3, idk what I missed or what I can try next:::EDITED:::I had the card installed while flashing, idk if that makes a difference...
[Xoom Android Development] robbiev80:
Try this:

Reinstall your SDK.
[Xoom Android Development] teo91:
This does not work for me. I have a wifi version. When I pass in version Tiamat 1.3.1 I have a problem. My Wifi does not work. Before I have version Tiamat 1.3.0 and everything is allright. But with this version I haven't wifi. I don't why ? I followed the instructions (I was before 1.3.0), commands adb going well but to no avail. Sorry for my English

Help
[Xoom Android Development] ClydeB1:
Repush bcm4329.ko

If that still doesn't work, uninstall SDK and re-install and then push the file again.
[Xoom Android Development] teo91:
I have a question, when you upgrade it's the same technique (boot.image,...) or just push adb ?

i have do all the procedure (boot,.... and push) and no wifi
[Xoom Android Development] teo91:
Thanks for your answer. I will test tomorow :-)
[Xoom Android Development] teo91:
But can you answer at my second question, it will be good. Thanls a lot
[Xoom Android Development] ClydeB1:
If you used adb and fastboot to do the img flash and to push all of the relevant files as instructed on the first post but wifi doesn't work, just try to adb push the bcm4329.ko file again.
[Xoom Android Development] JungleJiujitsu:
Im on Windows7, SDK is not listed in apps installed...and just to clarify, SDK is adb correct? TIA!
[Xoom Android Development] jlaw904:
Came from 1.1.6 to 1.3.1... Everything works fine! Thanks!!!

I played it safe and just completely reinstalled SDK tools before pushing the files over. Wifi still works and I am able to read/write to the microsd card with no problems. Time to order a 32 gig :)
[Xoom Android Development] krat0s123:
Well, since the sdcard2 is mounted to the internal one, does it get wiped out every time you restore/reflash the xoom?
[Xoom Android Development] crauzz:
Is everyone running setcpu? Because no matter what I set the Max at I still see it jumping to 1504. Anybody know of another good governed?
[Xoom Android Development] ericdabbs:
What governor setting do you have when you have the phone on? If you set it to "ondemand" then the xoom will scale up to the max frequency when needed.

If you set it to "performance" then the xoom will use the max frequency setting all the time. At the same time when you use this setting the battery will drain faster.
[Xoom Android Development] crauzz:
I have it set to interactive 1000 MHz. The reading still still jumps to 1504.
[Xoom Android Development] Archangel:
I replaced the files and images from the one click root 3G method and just flashed it and right now it seems stable will report back

So far everything seems good and no problems, very easy and works perfect just downloaded a boot animation to it but had to redirect the web file download directory to /mnt/sdcard/sdcard2

QUOTE=crauzz;12910057]I have it set to interactive 1000 MHz. The reading still still jumps to 1504.
[Xoom Android Development] rank78:
Having trouble from the get-go :confused:

Rooted wifi version, already rooted with the one-click method.

I do the first step of adb fastboot and I'm at the red M screen with the text saying 'starting fastboot' but nothing else happens. I even tried quickboot to go to bootloader and same thing.

I'm new to the Xoom but not adb as I have an Evo.
[Xoom Android Development] flippingout:
Seeing the same thing with interactive. I have it set to 1200 and it jumps to 1504. I'm also using SetCPU. Wonder if another governor would be better...
[Xoom Android Development] padanfain:
I just flashed and haven't overclocked and I am seeing some instabilities with the stock browser. It seems to constantly crash.. main websites are theregister.Co.UK yahoo finance. This a known issue?
[Xoom Android Development] flippingout:
Make sure you have the fastboot.exe in the same folder as adb.exe. When that screen shows on the reboot type the fastboot command as shown in the first post. It doesn't look like the Xoom is ready to receive a command but it is. Just need to make sure you have the correct files in the correct directory.
[Xoom Android Development] Archangel:
I am using the stock browser and cant duplicate that,,,i use the crap out of it and it runs fine?
[Xoom Android Development] padanfain:
Weird.... this is happening with Firefox too.. maybe the Javascript rendered is mucked up somehow?
[Xoom Android Development] rank78:
Ah this pertains to me too. I just noticed fastboot.exe is in tools dir, should I just cut/paste it into platform-tools dir and everything will be ok?
[Xoom Android Development] crauzz:
I'm a noob to android so I'm trying to find someone to suggest a different governor but this is definitely a problem and could solve a lot of the instability issues.
[Xoom Android Development] gerbick:
For the life of me, I cannot flash this. And I did 1.30 without incident last night. Heck, the commands are still in my bash shell!

I'm using a Mac, have had no problem(s) in the past from the original unlock to flashing 1.30, but I'm getting errors left and right.

I've created sdcard/sdcard2 via Root Explorer. I'm getting stuck after the ./adb reboot bootloader command... then I have to use ./fastboot-mac flash boot boot.img and it's erroring out.

Same USB cable, same environment, same everything as the 1.30 flash... but nothing doing.

I'm scratching my head here.
[Xoom Android Development] padanfain:
That was unpleasant. I just had a hard freeze and had to hard reboot with volume up+power. I just uninstalled setcpu to see if that makes a difference.
[Xoom Android Development] Archangel:
Maybe i do not know but is there any reason why more people are not flashing using the one click method for the 3G xoom's, or are all these instability problems having to do with the wifi models?
[Xoom Android Development] bwcorvus:
People like myself want to do it by hand. We like to learn, make mistakes, and learn again. One clicks should not exist. You need to learn adb, so do it by hand.
[Xoom Android Development] destroyerbmx:
immediate instability issues w/ 1.5 just like the other kernel, I am running stock again for the time being.

Dont get me wrong I appreciate the Dev for the xoom and I will be running kernels when I can be stable, I am more fearful for hardware damage since I just dropped all cash on it.

I take that back I cant go to stock because I cant get wifi to work.

I cant get wifi to work with anything now.
[Xoom Android Development] ejlax:
did you back up your stock bcm4329.no and SCSI_wait_scan.ko files? If not that would be why....
[Xoom Android Development] xlGmanlx:
Did you try unlocking it again to see if that fixed it?
[Xoom Android Development] jkurl:
Can someone on here who has the OC kernel installed test out this custom boot animation and see if it will work w/ the OC Kernel.

http://www.xoomforums.com/forum/motorola-xoom-themes/563-my-first-xoom-boot-animation.html#post6161
[Xoom Android Development] blozout:
Need serious help. Kernal flashing didnt work for some reason and now i'm stuck in an endless boot loop. Computer wont recognize the Xoom...and it'ss not mine, it's my bosses. I was trying to do him a favor and it didnt work. Worked for me yesterday on my Xoom but don't know what happened with mine. Please someone help. I can get to the RSD protocol support 3 screen but nothing happens from here.

Edit: Was finally able to access bootloader via a combination of volume rocker / power button attempts.
[Xoom Android Development] FuzeAction:
I'm able to pull a 66 with v2 of the original OC kernel. I challenge all to try and top it ;)

Come at me, Bro.
[Xoom Android Development] hawkye:
Yeah I can't get anywhere clost to that with this kernel. I love Smartass but it just can't compete with coolbho3000 kernel. I look forward to new Smartass releases. I use it on my Inc and love the performance and battery life.
[Xoom Android Development] bigrushdog:
I'd love a screenie :-) New kernel today or tomorrow. Latest commits from aosp and some commits from linux stable upstream.
[Xoom Android Development] FuzeAction:
How did I know someone would ask for this?
[Xoom Android Development] destroyerbmx:
not sure what it is but all of kernels freeze my xoom. I will set 216 min and 1000max in set CPU with no profiles and next thing I notice is I am running at 1.5, but set CPU still says Max is 1000. It might not be high enough voltage or something. I am currently looking for the stock wifi drivers to revert back to stock so I don't reset every 30 min.
[Xoom Android Development] bigrushdog:
That's just sick bro. I can't even get past 60, but i've loaded mine up with junk already :rolleyes: Also, I have noticed some issues with the smartass governor. I doesn't seem to scale right and i've been getting hard reboots when changing out of smartass to other governors. Likely, next release will remove smartass until further research can be done.
[Xoom Android Development] xlGmanlx:
Just loaded this bad boy up, amazing
[Xoom Android Development] xlGmanlx:
What kinds of things you looking to put in this after source is released? You think about SBC?
[Xoom Android Development] Cayniarb:
The AOSP kernel source is out. SBC was designed for HTC phones, so it may or may not be portable. I've looked a bit at HAVS too, but that was designed for MSM processors and does not look like it will port well, (also, it looks like some level of dynamic voltage scaling is built in). The Tegra 2 platform is still extremely new, so it's going to take some time for there to be some more significant development for it...
[Xoom Android Development] xlGmanlx:
Thanks for the quick breakdown
[Xoom Android Development] PaulG1488:
just flashed 1.1.0 with no issues at all will report back later on today if i run into any performance problems
[Xoom Android Development] destroyerbmx:
I would say about 3-4 months until we have some killer mods, I got on the train w/ the fascinate in the beginning and it felt like years checking xda everyday for some good mods/roms, but once it gets moving it will move quick.
[Xoom Android Development] PaulG1488:
Exactly what I've been telling people that keep complaining about the xoom
[Xoom Android Development] xlGmanlx:
Even after you say that there is an update for today yes!!!
[Xoom Android Development] MrHawaii:
Does anyone have any feedback about the version that got posted today? Are we still experiencing the frequent rebooted? I am tempted to flash, but I am scared...
[Xoom Android Development] Archangel:
Sounds good but if it results in a gazillion problems because of misplaced files and images and causes soft brick or other problems is avoiding one clicks really that advisable, just asking no flaming. I know how to adb and it is rather simple but easy to screw something up if you mistakenly put in the wrong command in the wrong place which is what i see alot going on here.
[Xoom Android Development] bwcorvus:
The more you do it, the better you get :). Plus these usually come out here first, then you have to wait for the one click author to update.

Sent from my Xoom
[Xoom Android Development] Archangel:
I can understand that, I was nervous when I replaced the files and images of the one click and put it back together and crossed fingers when i ran it LOL fortunately it worked good no problems at all, no forces closes, no setCPU problems or browser issues. The night is still young though I dont want to speak too soon.
[Xoom Android Development] i_am_the_one:
Not true. I Used the one click root to root my xoom. I read all the prompts then watched the commands being entered through adb. Just because I was not typing the commands doesn't mean I am not learning. I have since flashed the 1.3.0 and the 1.3.1 just using the instructions in the op. In my opinion there is little difference in using the one click root rather than copy and pasting the commands.
[Xoom Android Development] ebamit:
Worked like a charm. Took about ten minutes, including figuring out that the ADB dll's were in the wrong folder. Great job devs!
[Xoom Android Development] Archangel:
I can see it both ways. People need to know how to ADB and when they do, it would keep most of the problems down. It is so easy to screw something up. I have seen some cut and copy and when they did they left off a letter or number and it caused some bad problems. One clicks are great as long as they do the same thing as I would do in ADB which is what the one click root method does, you can see the commands run if you watch it.
[Xoom Android Development] xmellyx:
Worked for me without a hitch.

Fyi: to the people getting stuck at fastboot, make sure that the fastboot drivers from the android sdk are located in the same folder that you adb from. I had the trouble of my terminal not recognizing the fastboot command and realized that I was abd'ing from C:\android-sdk\platform-tools and my fastboot drivers were located in the C:\android-sdk\tools folder. I just moved the fastboot drivers over to my platform-tools folder and was good to go.
[Xoom Android Development] i_am_the_one:
Yup, really people just need to slow down read every thing fully before they start. And pay attention to the details.
[Xoom Android Development] Mandelbrot.Benoit:
Droid OverClock app by jrummy has been stellar so far. I had several reboots with set CPU and the Max bug. I've been at 1400 interactive and stable 48 hours. First time to stick with a kernel!

You have to use it in portrait or it will force close when selecting frequency settings.
[Xoom Android Development] ryan562:
okay quick question guys.

i flashed 1.3.1, or so it seems, and followed the "special" instructions listed. sdcard2 shows up within the sdcard directory folder. HOWEVER, when i go to my settings menu on the xoom, it still says tiamat kernel 1.3.0 and not 1.3.1. is this normal? i flashed 1.3.1 three times to be sure lol.
[Xoom Android Development] Archangel:
Hmmm that is weird i went in and changed my setCPU scales down to 912 in both landscape and portrait and it did not force close?
[Xoom Android Development] Hexbug:
Worked for me, no problems at all! And I am hitting my highest Quadrant score with this one too! Great job!!!
[Xoom Android Development] Archangel:
Yeah after i recompiled the one click root program with the new 1.3.1 kernal i am getting scores well over 3300!!! Great work devs!
[Xoom Android Development] i_am_the_one:
The number didn't change because the kernal wasn't changed. So in the about device it will still say 1.3.0. As long as sdcard2 works you're all set
[Xoom Android Development] ryan562:
Cool, thanks
[Xoom Android Development] crauzz:
Ok I got someone to help me with setCPU who knows a lot more than I do. I had to create a couple of profiles, and I will post the settings in a few minutes; So far I have not been able to replicate the instability issues I was having before. The browser is working perfect. If this works I'm happy otherwise I will try Droid Overclock.
[Xoom Android Development] crauzz:
Profile: Charging

Max: 1200000

Min: 608000

scaling: performance

Priority: High: 100

Profile: Battery <

Battery <: 101%

Max: 1200000

Min: 456000

scaling: ondemand

priority: high: 100
[Xoom Android Development] drziddo:
Not showing the new sdcard at gallery.

Any ideas?
[Xoom Android Development] qubz:
What are you guys formatting your sd card as? FAT or ext? are you using a swap?

Are you formatting in Linux or recovery?
[Xoom Android Development] Hexbug:
Formatted mine on the PC as FAT32 and it works just fine on the Xoom.
[Xoom Android Development] Crazypinoy9:
Did you create the "sdcard2" folder in "sdcard"?
[Xoom Android Development] krat0s123:
Anyone ever tried to restore their xoom after mounting the sdcard2 inside the sdcard folder? Those who have, did the sdcard2 get formatted as well, when xoom wipes out the sdcard folder? I've asked this a few threads back, but got buried by threads whether the one click root should or shouldn't exist. I'm not trying to be a di*k or something. And I know I can find out the answer myself, which I will do if no one ever has. I'm just getting tired of people arguing whether the one click root should or shouldn't exist. I mean, there's a reason why it exists and why someone took the time to write the script! And there's also a reason why someone would rather wait for a one click root than be one of the first few who can root their device manually. Instead of flaming someone who relies on on click root, just let them be. They will learn through time as it's not hard. Everyone who's done it already knows how easy it is, and those who hasn't surely have been told or have read/heard the same. They're just not comfortable about doing it manually yet. And maybe they don't just have the time to thinker with it if it ever bricks their device.. I'm not trying to start anything nor am I flaming anyone. I'm just getting tired of this same pointless argument on every single device's thread. I would simply put it as this, ADB is very easy and simple enough if you follow the instructions right. But I wouldn't recommend it to anyone I know who hasn't done it! I would rather do it myself or give them the one click root if one exists! Just to save myself the trouble of reviving their device or getting blamed for a bricked device. Because trust me, most of the time, they will tell you they followed the instructions to the "T" and yet it still bricked their device! Obviously, if they messed up following a simple instruction, they would sure mess up reviving their bricked device as well. So please, give that argument a rest. Sorry for the rant. Just really tired of seing redundant threads about the existence of one click root. Ok, I feel better now.. :)
[Xoom Android Development] ClydeB1:
Glad you got that off your chest LOL - I haven't tried what you are asking, but I guess a way to prevent the sdcard2 getting formatted would be to simply remove the sd card from the device when doing a restore, unless you're asking because you do want the sd card to get formatted.
[Xoom Android Development] rank78:
OK I followed the instructions and it seems to have gone well, but how do I confirm that it worked? I have sdcard2 in my sdcard directory but that isn't what it looks like in this pic...

Mine just shows sdcard, not sdcard2
[Xoom Android Development] ClydeB1:
The latest version mounts sdcard2 inside sdcard. Look there ;)

Edit: provided you created the folder first.
[Xoom Android Development] rank78:
I created the sdcard2 in /sdcard/ before flashing using ES explorer. I tried to create it using adb as instructed after I flashed to see if I created it in the right place and it said directory already exists.

Heres how it looks......
[Xoom Android Development] ClydeB1:
That is right. Try putting a file like a photo or video in the sdcard2 and see if you can view picture or play video.

The other picture you originally displayed was from the older 1.3.0 version.
[Xoom Android Development] kcrudup:
That's a bug in SetCPU; I've seen this too and have E-mailed the developer, who says he'll have a fix shortly.
[Xoom Android Development] teo91:
I have a question : is it normal to have kernel version 1.3.0 after flash ?
[Xoom Android Development] ClydeB1:
Yes as there were no actual changes to the kernel as BRD explained, just tweaks to get sd card to work.
[Xoom Android Development] teo91:
Thanks a lot for your help everthing is allright. sd card to work (sandisk 16GO) :D
[Xoom Android Development] teo91:
But what is difference with this version : [KERNEL][AOSP]Tiamat 1.3.1_Cybertronic_p0 (repackge) :confused:
[Xoom Android Development] BlackDino:
Apparently it will be added to this source, so there might be an update today