yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] integramodder:
How do I fix the SD card not being seen? I used to use Astro to move files from the onboard flash to the micro SD and now in Astro doesn't recognize the SD card. Is this an Astro problem because its looking for the SD in the older mnt location?
[Xoom Android Development] otis_bartleh:
Check your Astro preferences. You can specify what directories the External Storage (actual SD card, not the internal memory labeled as sdcard) goes to. Make sure external storage is /mnt/external1. That's working for me. If that doesn't work, try ES File Explorer.
[Xoom Android Development] REHolt218:
This brings up a question, maybe best answered by the devs: where is the sdcard mounted on the EOS ICS nightlies?

In my understanding the sdcard is now mounted at "/media/sdcard". My Xoom currently has it mounted at both "/mnt/external1" and "/media/sdcard".

If "/media/sdcard" is the new correct location should I delete the "/mnt/external1" (I assume I would need to remove the sdcard first)?
[Xoom Android Development] CUProf:
No matter what your Astro is calling your actual external SD card, you can use MicroSD Mounter which will allow Astro to see your external micro SD card. It works like a champ, just a small step to make sure that your data is secure.
[Xoom Android Development] otis_bartleh:
I used to use that too, but then realized I don't need to. Even though the app reads false, I can still read/write to the SD... Also, astro still needs to know where to look...
[Xoom Android Development] rdnckreaper:
build 41

Just loaded it and tested all radios and everything is working great. The only thing that I haven't checked is the wifi tethering using 3g and 4g, will let yall know after I finish my tiba restore
[Xoom Android Development] kcrudup:
it works; I have the 10GB LTE plan and use it to serve other devices all the time.
[Xoom Android Development] rdnckreaper:
Yeah I was just able to check it and it worked great. I just wish I could get it to work on my cappy that I installed the new Doc's ICS rom on. That is the only thing that doesn't work with that custom rom for my captivate.
[Xoom Android Development] EtchG:
/media/sdcard is the internal storage for the Xoom. The "hard drive" as it were.

/media/external1 is the sdcard in the slot next to the 4G SIM card.
[Xoom Android Development] rdnckreaper:
No restore with tiba!!!!

I have been waiting for 10 minutes now trying to do a restore with titanium backup and it hasn't even restored the first one!!!! What is going on???
[Xoom Android Development] otis_bartleh:
Then what's the /mnt/sdcard and /mnt/external1? The sd card slot next to the sim for me is /mnt/external1...

---------- Post added at 09:35 PM ---------- Previous post was at 08:46 PM ----------

I can't connect to a hidden ssid either, but now that I replaced my router, I realized my N1 on CM7.1 won't connect to a hidden ssid either...
[Xoom Android Development] solarnz:
Woah careful there, you're handing out wrong information.

/sdcard = internal storage

/data/media = internal storage

/mnt/sdcard = internal storage

/media/internal = internal storage

/mnt/external1 = MicroSD

/media/sdcard = MicroSD

/media/usb = usbOTG
[Xoom Android Development] integramodder:
thats what it was...external1

thanks
[Xoom Android Development] nswenson:
Go into recovery and select "fix permissions" under the advanced options. After that the applications will restore properly from titanium backup.
[Xoom Android Development] REHolt218:
Thanks Solarnz, that is exactly what I have confirmed. I have seen several posts that gave the wrong information and was hoping you would clear everything up.

My other question though is, should I delete the old mount point "/mnt/external1". It shouldn't really matter, but would be less confusing.
[Xoom Android Development] linj:
Hey Team EOS,

I did post this on the features request link, but it did limit the number of characters I could put out so I figured I'd post a bit more detail here.

I was wondering if you guys think it possible to implement USB DAC (sound card) support for the Xoom. It's been implemented on the Nook Color (different, but similar sources for the usb i/o portion) and a bit more information can be found at http://code.google.com/p/android/issues/detail?id=24614

I've checked out both the Nook and your stingray kernels and noticed that all the necessary c and header files are already in your kernel, except they aren't being compiled in. I compiled them in (codesourcery toolchain and turned on ALSA as well as usb sound devices) but had no easy way to flash it, so took the Rogue kernel (seems to me the only ICS kernel that's available in flashable form; I don't think you guys publish your kernel separately?) and replaced the zImage and modules with what I now have.

Unfortunately, it then gets stuck at the boot screen (red Motorola logo), and I can't get any further. I'll be the first to admit I'm way out of my element here, but I'd love to contribute in any way I can.

Thanks!
[Xoom Android Development] dtrud0h:
NO REHolt218!!

/mnt/external1 is the mount point that the operating uses to mount the media. If you remove it it will not be there anymore, not /mnt/external1 nor /media/sdcard. You just have to come to grips with it.
[Xoom Android Development] EtchG:
All I can say for myself is....oops.
[Xoom Android Development] tonesto7:
Thanks for letting me know i'm not crazy!

It worked on the HC rooms so I thought I was doing something wrong.

I've had to use the Wifi Advanced Config tool from the market to get it to work before.
[Xoom Android Development] ZanshinG1:
Hidden SSIDs generally aren't supported by mobile devices for good reason: each scan has to actively check for each hidden SSID, which is expensive battery-wise.

Hidden SSIDs are also LESS secure than broadcast. http://blogs.technet.com/b/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx
[Xoom Android Development] wiredup:
My Wifi network has a hidden SSID and I haven't had any issues.

Build 41, GAPPS 10.4
[Xoom Android Development] hurricanes:
I am also connecting to a hidden SSID with no issues. Build 39 and GAPPS 10.4

---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------

While I agree that hidden SSID's are not more secure than broadcasted ones, I disagree that they are less secure. They are equal.
[Xoom Android Development] csseale:
Yep I'm on a hidden ssid also no problems. I do believe your wrong on both points. Sorry.
[Xoom Android Development] otis_bartleh:
Weird. I connected to my wifi, then changed to hide the ssid, and it disconnected and wouldn't connect again. I'll update to the latest build when I get home tonight and see if that helps, I'm still on 32...
[Xoom Android Development] bigrushdog:
Windows scans for hidden ssid but Android does not. Hidden ssid is not a security measure thus it can not make a network less secure. But I can tell you this. When I play with aircrack I look at visible ssid's first.
[Xoom Android Development] johnny0911:
OK from 39 to 42 let's see how it go's.
[Xoom Android Development] ZanshinG1:
Android (when driver/supplicant/wifimanager are modified to support hidden) sure does actively probe for known hidden networks each scan.

There's no other way to automatically connect to a hidden network.

You're right in that Android doesn't by default. If you look at WifiManager's source, the hidden SSID support is disabled, even though the flag exists in WifiConfiguration.
[Xoom Android Development] mds96:
You can also use File Manager HD (Honeycomb) to transfer files from internal to external. In the app internal is "home" and external is "storage".
[Xoom Android Development] bigrushdog:
Ok. I was thinking in a slightly different context. Yes it does scan for them if they are KNOWN networks.
[Xoom Android Development] otis_bartleh:
Is there a way for me to activate whatever necessary to find and connect to known hidden networks, like mine at home?

I know it's not extra secure, but I'm rolling with the out of sight out of mind thing. If a neighbor wants to hack a network around me, there are plenty visible ones to try first.
[Xoom Android Development] exstatica:
Security is security, and a hidden SSID will be in my opinion slightly more secure than a broadcasted one. However security really comes from the encryption method you use. Everything can be broken, and I mean everything. I personally run AES CCMP + TKIP + PPK, with key rotation. I also expire all the keys when another device disconnects. This is all on top of EAP + VLANS + mac authenticated DHCP.

yes I'm very paranoid.

I did a bunch of crazy testing this last week with some cisco access points and 802.11n draft equipment.

So if you run into a problem with really bad download, you have to disable N, or look for a software update that makes your AP 802.11 standard. The new broadcom drivers in ICS for the xoom is now 802.11 certified and has a bug with older 802.11n draft devices.

I had to move all the ones without problems to the over 40mhz 5ghz range, and all the crappy hardware (xoom) to a 2.4ghz b/g, without n.

Myself and a few others have been dealing with it on the motorola forum

https://forums.motorola.com/posts/f3146e9b0a

Oh, and I use hidden networks on my Nexus S 4G, and Xoom. Both work fine.
[Xoom Android Development] dtrud0h:
Exchange Security Restrictions...

I was reading through posts on THIS thread and a user named Viddy in post #122 has a fix that works with the Xoom on this nightly (v39) with gapps v10.4 .

Maybe it's something that Team EOS could implement into the EOS settings area if you could find a way to do it and undo it on fly. As it stands it requires replacing /system/app/Email.apk with a modified one.

Either way the info is there and it has been working well for me for 2 or 3 days. Email and Calendars from exchange sync perfectly and I've had no notice to update security settings as of yet.
[Xoom Android Development] bigrushdog:
In wireless settings just add network and enter your ssid and save.
[Xoom Android Development] otis_bartleh:
I have that done, and it always reconnects automatically (quickly too :) )when it's visible, still not when hidden though. :confused: I'm gonna do a complete wipe and update to the newest nightly, and try again... Its only my home network, so I'm not really that worried, I don't rely on that for security anyway...
[Xoom Android Development] CUProf:
I have been running 42 for about 6 hours (on 3g till just now when I got home from work) and it was very stable. A slight lag here and there, but overall stable. While browsing the internet (on wifi) just now it lagged out and rebooted 3 times in a row. When it finally come out of the loop I had a notification that the over clocked settings had been reset. I usually run 1408 over clock. Would this reboot cycle be a rom glitch or from the over clocking or both maybe? I wasn't able to get the logs unfortunately.
[Xoom Android Development] REHolt218:
I did not see any entries in the changelog for nightly #42 so I decided to not update and instead stay on 41 without a reboot and see how it runs today. Yesterday I experienced a spontanious reboot while browsing with Dolphin HD and switching between wifi and 4g. That was early in the morning (around 7:am CST). Since then I have had no issues and no rebooted either voluntary or spontaneous. That puts me at around 36 hours of up time with no issues.

Not sure what the glitch was yesterday but it sure isn't a big deal.
[Xoom Android Development] liftman-:
having problems getting the media scanner to scan external1

this is not a new problem, had it a while but decided to mess with it tonight. I keep all my music on the sdcard. I really have not read about too many people who haven't got the media scanner going by clearing the media storage. this has not work for me.

for many many nightlys I have had a media scanner stop message. logcat show it was running out of memory. so I up the

dalvik.vm.heapstartsize=32m

dalvik.vm.heapgrowthlimit=96m

dalvik.vm.heapsize=256m

that got rid of the media scanner from self destructing.

now I see in logcat it scans the /mnt/external1/Music folder but no sub folders.

I can add a song folder in sdcard/music and it will find it.

if I rename the external1/music to something else still a no go.

any ideas where to go from here?

thxs

edit:

Google Services Framework. Cleared data.

works :-)
[Xoom Android Development] CUProf:
I should have checked the log, but compared to me yesterday (enough reboots to make me revert back to my nandroid of 32) this has been a lot more stable today. I'll keep 42 till the change logs show me a new nightly.
[Xoom Android Development] johnny0911:
I have been running 42 for most of the day today with out one issue, not over clocked is course.
[Xoom Android Development] cydetrakd:
I am sad to be back on stock 3.2.4 after experiencing the sickness of this rom. I had issues with a faulty charging port on my few months old Xoom. I figured send it off while it's still in warranty and get it fixed or end up having a bad battery due to it never displaying the right battery stats since it always thought it was plugged in. Vzw is making me send it back to Motorola for repair I hope they fix it since stock hc only shows the issue when accessing by status in about tablet where it says not charging and resets up time after each reboot. I think I should put a note in the box just in case since its not as easy to tell like on the Team Eos rom regardless I will be without my beloved Xoom for 3 weeks according to the customer service rep. Has anyone had to deal with Motorola repairs should i leave the note to make sure and how fast is the turn around time? I hate that i had bad luck with the charging port but atleast im stock locked and unrooted just to be sure.
[Xoom Android Development] Tom_S:
My first download of 41 boot looped. Flashed back to 40, re-downloaded and re-flashed 41. All good since then.
[Xoom Android Development] REHolt218:
Downloaded 43 this morning. Everything is running well for now. No rebooted or FC's yet in the last 3 hours.
[Xoom Android Development] johnny0911:
They will most likely just replace your Xoom with a referb .
[Xoom Android Development] cydetrakd:
The Vzw rep assured me that I will get my Xoom back so I hope that it is the case just fixed. Its barely 3 months old so I hope I don't get a refurb.
[Xoom Android Development] mgabriel2:
Installing 44 as we speak - Changelog mentions some kernal updates... Am I the only one who keeps having the Google Music App problem ? ( have to uninstall - reboot recovery - wipe cache/dalvik - install from market )

Noticed in the Changelogs the following lines :

change Ibd9017c5ef0f0cd3f9bf39b6883afdeb539193ab

project: eos/device/moto/wingray

and

change I4cd06ebef792629a1eaa3fa7fb6f433a8981d8b5

project: eos/device/samsung/tuna

Does that mean that no changes for the 4G Xoom ( Stingray ) ??
[Xoom Android Development] CUProf:
Looks like no change last night for us.
[Xoom Android Development] Tom_S:
I'm running nightly #41 with the 3.0.4 kernel that came with it and haven't experienced the GM issue.

If I interpret the changelog correctly, Stingray didn't get touched last night. Let me know if you end up with a kernel later than 3.0.4.
[Xoom Android Development] mgabriel2:
Kernel version

2.6.39.4-Tiamat-3.0.5-gpuoc-020680g99da013
[Xoom Android Development] tinpusher:
I believe when it says "wingray common" it includes changes across the product line (similar) they are supporting.

Otherwise it will just have the product name without "common" if its device specific.

"Tuna" is for the galaxy nexus product line.
[Xoom Android Development] stevefxp:
As to the GM issue I too was having the problem. What I do now is delete the GM apk using root explorer, reboot, and then install from the market. I do not have to reboot into recovery and wipe dalvik.
[Xoom Android Development] dimitri407:
The one issue I am seeing is with Plume. When you have the Widget on the desktop and you select a tweet yo view the menu options are all white. You can't see anything. When you select one of the lines, it highlights the lines and you see what you are selecting. This has always happened with the ICS Roms. Not a game changer for me just an annoyance.
[Xoom Android Development] mgabriel2:
Is this something that is going to get fixed ? is it known why its occuring ? Or is it user specific and if so where / what info should I provide to look into this ?
[Xoom Android Development] CUProf:
I have never experienced issues with GM (using it now with no issues). The only issue I've had with any nightly - as far as apps - was with tibu permissions to restore apps after a wipe. It maybe user specific like you said.
[Xoom Android Development] SamuriHL:
USING GM isn't the problem. Updating it from the market is. So once you install gapps 10.4, go to the market and you'll either find that it thinks it's not installed or there's an update for it. The update fails. But the installed older version WORKS just fine.
[Xoom Android Development] Asphyx:
If I had to guess I would say it is related to the DRM in GM not the Rom itself.

It may be that with each rom install the DRM key is wiped or changed causing issues unless you totally wipe data and dalvik or uninstall GM and start new from the Market.

The way Google restores the apps it may not restore DRM properly or DOES using old DRM settings from thier backup of your system.

By uninstalling that data gets removed and renewed when you re-install.

But like I said I'm just guessing!
[Xoom Android Development] brittoking:
Edit: double post. I apologize.
[Xoom Android Development] brittoking:
The newest version of GM is 4.1.512 (I believe), and I like everyone else posting was having the errors re: missing app in market or failed update. So I simply downloaded the newest Google Music apk off the net, unzipped the 10.4 GAPPS and swapped the old GM.apk for the newer updated one, re-zipped the GAPPS package and I simply flash it every time I flash a new build, of course clearing cache and dalvik each time as well. Works perfectly.

Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
[Xoom Android Development] ZanshinG1:
That's a theming bug in Plume, should be fixed if you update the app.
[Xoom Android Development] tonesto7:
I think there is some confusion about the issue I'm actually having... It's not an issue of the SSID...

The network is an enterprise 802.11 - PEAP network... It authenticates successfully with the RADIUS but fails to pass the WEP key to the driver...

I downgraded to the last build of the tiamat 4g Honeycomb rom and it connects right away... So I'm assuming its because the driver we are using for ICS still has some bugs in it...
[Xoom Android Development] brittoking:
New #45 build and 10.5 GAPPS would not boot for me. Tried everything , clearing all caches etc but wouldn't go past moto splash screen. Reverted back to #44 since 45# had no improvements anyway, used 10.5 GAPPS again and worked immediately. Don't know what the issue is but it seems #45 was no good for me? I even downloaded it twice to make sure. Just a heads up!

Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
[Xoom Android Development] REHolt218:
Nightly #45 and Gapps 10.5 booted fine for me. I went ahead and did a clear cache and wipe Dalvik cashed.

In the list of changes above it says "revert to v9 of Google backup transport" . If this was meant to fix the problem with the backup account, it did not for me. It is still greyed out.

Everything else seems to be working for now.
[Xoom Android Development] liftman-:
try removing data for google services framework and google backup transport.

also you need to be on wifi(at least i did)

you can also check your backup here:

https://www.google.com/dashboard/?pli=1 (works while xoom not being used)

last week I turn it backup off and it remove all data except paid apps. turned it on and apps where up to data.

although google seems to be retaining some old devices.
[Xoom Android Development] brittoking:
Wonder why it was different for me? Corrupt download? And the way I read the changes to the backup, they were to the GAPPS not the ROM right? There was nothing in the official changelog (last I looked). I'm probably mistaken it was 3 am when I was tooling with it all.

Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
[Xoom Android Development] brittoking:
Your trick worked for me just had to uncheck then recheck the backup box after clearing the two Google services/backup and it was no longer greyed out! Thanks

Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
[Xoom Android Development] johnny0911:
On 44 now with gapps 10.5 no problems with install and no problems with from, his far. Thanks team EOS. Will inform if things change.
[Xoom Android Development] REHolt218:
Thanks for the help liftman, my problem is now solved. Took a little more doing than I expected but it is a least fixed.
[Xoom Android Development] kcrudup:
Uh, what? I connect at home to 5GHz N without a single issue (and before that, 5GHz A).

The BCM4329 chip is pretty robust- what issues were you seeing?

(Also, the latest EOS kernels have lots of WiFi driver improvements over Xoom WiFi.)
[Xoom Android Development] REHolt218:
Loaded 46 this morning even though I didn't see any changes in the change log. When the system booted, I happened to be watching as it complete the application updates (unfortunately I did not have my glasses on so I could see any messages). When it complete the update it immediately rebooted. When it came back up all was well and has been working great since.

Thanks Team EOS for a great ROM.
[Xoom Android Development] apollyon0810:
I created a 5Ghz N network in my apartment specifically for my Xoom. The 2.4Ghz spectrum is WAYYYY crowded in my area and I was getting better reception from a neighbors router than my own router in the next room (literally 20 feet away directly in my line of sight). Since moving to n-only, my signal strength doesn't READ as strong, but its much faster and stable. In summation, I've never had any problems with 5ghz 802.11n.

As an aside: what's stopping EOS from making a stable ROM and releasing it? As opposed to nightly builds. Everything is working, right? I guess my problem isn't Team EOS, just my tendency to get caught up with a desire to flash every new nightly! Haha.
[Xoom Android Development] kcrudup:
Yeah, I've been 5GHz for 7 years now for the same reasons- plus you get less interference from microwave ovens and 2.4GHz cordless phones as a plus. And like you said, don't sweat the lower signal strength- 5GHz has lower signal penetration because of the higher frequency.

Talk to SolarNZ about that- I just do the kernels from time-to-time :)
[Xoom Android Development] bigrushdog:
Part of the reason is we don't have the build stable ENOUGH. Also, there are elements of ics that still don't function correctly, such as wifi and p2p. p2p0 I believe is the root of most of our issues, including reboots. I've spent the last several days analyzing logs and digging through source. I believe I'll have solutions soon. But I'm very excited about Android being able to merge the config80211 Linux wireless api stack. This opens countless doors.
[Xoom Android Development] nswenson:
Are any of you noticing severe performance issues in the web browser after running a few days? I believe there is an issue with the browser cache. On pages with embedded flash the browser freezes for a couple seconds, not allowing you to scroll until flash elements are completely loaded and running. It wasn't like this when I initially loaded the rom. I found that clearing browser cache fixes the issue and makes the browser far more responsive. I think it's odd that caching would actually reduce performance. Any way to disable browser cache?

Btw, I'm on Stingray build 41.