yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bigdave240:
The other thing i noticed is that the display was smaller and i was doing a little zoom each time. If you go into settings and debug check 'use wide viewport' and you will get fullscreen all the time. Easier on these old eyes of mine!
[Xoom Android Development] Bobbar:
Alright, WiFi tether: I've searched this thread and can't figure out what exactly I'm missing. I see mentions of the stock Hot spot app, which apparently is the only thing that works. How can I have the stock app if I'm flashing a vanilla build? I've of course tried the tethering apps from the market, both open and secure, and they get errors when enabling.

Can anyone give a concise answer for getting tether working? :eek:
[Xoom Android Development] kcrudup:
It's simple, actually- to have tethering to WiFi using your WAN connection as the source is quite useful, and is so easy to do in Linux that it's built-into HC and forward. The reason you'd ever need an app is 'cause many carriers aren't happy unless they find ways to **** around their customers (VZW!) and will often times either remove the ability post-Google, or have you use a WAN method that forces you to pay for it. (Google told VZW the Xoom has to be an "Experience Device", so they don't get to mess with much.)

Makes sense- not only is the normal "AP/STA" driver switching not done the same way on our devices (our WiFi driver is compiled into the kernel, so it's handled via a WiFi driver control) but they're probably not compatible with JB anyway. But in any case its unnecessary to use any external App anyway.

Just set it up from the Settings Menu, then you may use (if you wish) the EOS Quick Toggle so it's easy to turn on/off from the Main screen.
[Xoom Android Development] rlrbjr:
I've been following along with most of the nightlies for several months. Nightly 138 is quite stable, but this version gets non responsive for long period of time much worse than any previous. Opening gmail can be painful, even deleting mail can be slow. Is there anything I can do to help debug this?
[Xoom Android Development] kcrudup:
:( Not really. I know what's going on and have a fix I'm going to push that should make tonight's Nightly. (It's funny that you mention "GMail", as that's one of the apps I use to test memory pressure (I got started working on fixing the kernel and flash way back in November/December (back when we had no source for HC and everything but the kernel was Google stock) when it would take as long as two minutes to start GMail.)

The root cause was just as it was now- slow EMMC Flash, and not enough memory (we would be sweet with 1.5 or 2GB). I'll bet shortly after a reboot, and for a day or so GMail loads just fine, doesn't it? It's only after it's been running for a while (and since we haven't had any Nightlies for a while y'all have had a chance to try out 138 for a few days now) that we start to get this slowdown (which is due to memory pressure, and the effects that it has on the VM subsystem).

But as I'd said before, I see this too and am constantly looking for a way to mitigate short-term speed vs. long-term reponsiveness (ironically enough, the two issues don't always go hand-in-hand), and I think my latest tweaks to the I/O Scheduler and the VM system improve it greatly.

But, did you see what I'd written in this post? Turn that on, and I'll guarantee you that when your system is unresponsive you'll see a long blue bar.
[Xoom Android Development] hax0red:
With a little tweaking I was able to get 4960 in quadrant while undervolting 90mv to 1310mv @ 1.6ghz. I tried going further to 1300mv but the performance starts to drop off...here I lose nothing and gain in battery life which seems close to stock even at this speed, easily good for 24-7 use.

My scores for 2D is an average of 570 now and 1850 for 3D. CPU score best is 7800. Compare this to a stock tegra 3 at 10600 CPU, 2550 3D there is only about a 30% difference in speed but the Xoom GPU IMO really needs a little more for games like modern combat 3...wish you could change the resolution or adjust quality settings because I get a bit of lag even overclocked.

I'm unable to run 1.7ghz and make it through quadrant without crashing but I would love to try and get maybe 50hz out of it and maybe some more from the ram/fsb(not sure what its called on these arm chips) and GPU.
[Xoom Android Development] kcrudup:
I hate to constantly harp on this, but here's another datapoint, this time on a very recent device:

Some 16GB Nexus 7s Experiencing Severe Performance Issues With Less Than 3GB Of Free Space Remaining

XDA thread on the topic. Note that the reason for the slowdown when full is because as the disk fills up there are fewer free blocks, so the EMMC must do more time-consuming Read/Erase/(Modify)/Write operations, and while the kernel I/O subsystem is waiting for the EMMC to get its work done, sometimes no other I/O operations can complete in the kernel (esp. since we have a single-point-of-failure in the I/O due to the single EMMC device).
[Xoom Android Development] spyderman33:
I am having the same issue. Just use Firefox instead and it doesnt happen anymore.
[Xoom Android Development] Bobbar:
It's built right into the ROM?! *facepalm*

Thank you. :o
[Xoom Android Development] kcrudup:
.... Or, ya know, ya can also READ a few more posts and see how to easily fix the issue. (Some sites don't mix well with the "Desktop" UA and cause the browser to crash.)
[Xoom Android Development] dweezle:
That's what I love about Android. Well said.
[Xoom Android Development] paulfm:
No feedback on 139 yet? I see no change log, that always worries me a bit but I guess I will bite the bullet and go for the install. I can always revert back if needed :)

I love updates, I feel like a kid in a candy store just waiting to see what I can get next.

Keep up the great work EOS!
[Xoom Android Development] kcrudup:
It's just a quick change to add in those tweaks I'd mentioned yesterday to alleviate (and hopefully elminate) the "long pauses of nothing" that we've been seeing lately after the devices have been running for a while.
[Xoom Android Development] JoshWithrow:
I'll chime in and let you know in a few days. This'd is my daily driver so let's get thee updated "broken in"
[Xoom Android Development] dweezle:
I went to 139 and experienced exactly what Chelseablue described happening to him in 138. I went back to 138 and the symptoms disappeared. Browser functions normally, for me, in 138, but not in 139. Go figure....:confused:
[Xoom Android Development] bigdave240:
Did you try the suggested fix? Change the ua string then change it back. Or just change it to android and leave it there
[Xoom Android Development] dweezle:
I returned to 139 and the browser UA already is set on "Android". Is the idea to change it to something else, restart the browser, and then change it back? I'll try that and see if it helps. I won't have much time today to check it out, but I'll give it a try.
[Xoom Android Development] syu78:
Delete
[Xoom Android Development] kcrudup:
Never mind
[Xoom Android Development] SamuriHL:
I wish. ;)
[Xoom Android Development] Mjamocha:
Folks having issues with the browser - I'm running the same build 139 from 138- and not having any browser problems (have not had any browser problems). It could very well be the websites that some are trying to access malfunction on a specific UA string. I have switched the UA String to I*SAD, Android, Desktop .... tried all of them, no problems.

An alternative solution would be to cherry pick the Browser.apk from Builds 135-137 and drop it into your Build 139 System/app folder. Basically replace the said malfuctioning Browser.apk with an unmodifed (working for you) Browser.apk from a previous build. Yes, if you would like to be in desktop mode; you would have to switch to desktop mode manually, but that really is not that big of a deal. I know sometimes, we want everything to be perfect, but in reality nothing is really perfect. Sometimes we just gotta tweak it a little bit or sit back and tolerate the small things until things work themselves out.
[Xoom Android Development] bigdave240:
Thought that kcrudup covered this a few pages ago? Change the uastring and change it back and it seemed to work.
[Xoom Android Development] Mjamocha:
For you and I and those who read a few pages back to keep current yes it was covered. However for some (not sure why) - that did not work. A few pages beyond this one; lol someone is gonna bring it up again. Vicious cycle, I tell ya! Just Vicious.
[Xoom Android Development] kevdliu:
Kenneth,

I have a question about sqlite and SQLITE_NO_SYNC

The flag breaks an app im running (doubleTwist). Which parts of the ROM should I recompile with mmm after removing the flag? I tried recompiling and pushing libsqlite.so and /xbin/sqlite3 but they don't seem to do it.

Thanks
[Xoom Android Development] Droidem:
Could anyone tell me how to mount a USB hard drive using a OTG cable natively in EOS? I was using the app USB Mass Storage Watcher but it seems 138 force closes it. Any ideas?

Sent from my Team EOS JB Xoom
[Xoom Android Development] kcrudup:
Interesting. How are you sure this is it? We've had this in place for a while, and I haven't seen any previous issues with it. I'm all for pulling if it can be tracked to cause failures, though. What's the failure mode?

When I was testing the change I'd blow away the INTERMEDIATES directory for "sqlite" in ${ANDROID_PRODUCT_OUT}/obj . That'd be enough to force the recompilation (Android.mk changes aren't dependency tracked).
[Xoom Android Development] thingnblah:
You should be able to just plug it in, no app needed as it is supported in the kernel. That said the Xoom may not be able to power the drive via the USB port so you will most likely need an external power source. I use flash drives in this manner but an actual spinning disk will need more power. Once the device is detected you can browse its contents via your file manager of choice.
[Xoom Android Development] SamuriHL:
I've done it with my 2.5" seagate external. No external power. Is it recommended? Probably not. But, it's possible depending on the drive.
[Xoom Android Development] kevdliu:
My bad the problem was actually caused by the kernel i was running not the flag. The flag is all good sorry
[Xoom Android Development] dweezle:
I didn't know that it could be done without an app. I have been using StickMount and haven't had any problems. I'm on 139
[Xoom Android Development] hammer4203:
I'm on 139 and my stock browser keeps opening torrent when I'm browsing on godlikeproductions website. Any clue why?
[Xoom Android Development] bigdave240:
HBO GO seems to be broken again. Anyone know which rom version broke it? Or is it just me?
[Xoom Android Development] xyrcncp:
Mine is working just fine. I'm on 139.
[Xoom Android Development] rlmesq:
I had to reenter my password after installing 139, but otherwise there's no problem.

Have you tried uninstalling HBO GO, then reinstalling? That's what I had to do with the Comcast Xfinity streaming app on previous updates. (Strangely, the Xfinity app had absolutely problems after the 139 installation.)
[Xoom Android Development] bigdave240:
Thanks guys! I usually suggest reinstalling and didnt follow my own advice. Lol. It works fine after doing that.
[Xoom Android Development] hammer4203:
139 seems to be a lot faster at moving through apps.
[Xoom Android Development] Droidem:
Where would the drive be mounted then?

Sent from my Team EOS JB Xoom
[Xoom Android Development] Asphyx:
eck under storage/usb0 or usb1
[Xoom Android Development] kcrudup:
For those running 139: try to use it (and use it a lot) w/o rebooting, and look to see if you get any "it just freezes" issues (where it's totally unresponsive, vs. just slow or lagging a bit).

There's an update in the system (that hasn't been turned into a build yet) that modifies the "Show CPU Usage" in Settings->Developer Options so it gets rid of the list of processes and reduces it to just the colored bar (showing the various system states) with the embedded load-average; when that version gets built I'd like people to turn that option on at all times (it's a lot less intrusive now) and compare the state of their systems when things get slow and let me know what you're seeing (which color is most prevalent, what's the first number).
[Xoom Android Development] scottgti:
I'm on wingray, but don't see you over there too much. Latest wingray nightly has no more unresponsive or unable to wake up. The bar turns blue after opening Currents and doesn't smooth out until I kill Currents. Just thought I'd throw that out there. Thanks.
[Xoom Android Development] Droidem:
I'm not doubting you but I can't seem to get it to work without using an app to mount the drive. I can usually figure things out with trial and error but this is escaping me.

Sent from my Team EOS JB Xoom
[Xoom Android Development] thingnblah:
You are positive it is an OTG cable? Have you used it with other devices? Mine shows up as usbsomething, I don't have my Xoom handy right now but I will check the exact directory when I get home.
[Xoom Android Development] Droidem:
Yup. Its a knock off but it works when I use the app USB mass storage watcher. I bought it off of amazon.com http://preview.tinyurl.com/c2tt2ed

Sent from my Team EOS JB Xoom
[Xoom Android Development] Asphyx:
Then check under setting and storage

Under USB storage try manually mounting the drive.
[Xoom Android Development] Droidem:
Is what I see. Pressing mount SD card does nothing. Anything I can do to see if something is "running" in the background to check if its working?

Sent from my Team EOS JB Xoom
[Xoom Android Development] thingnblah:
What type of drive is this? Is it powered externally or does it draw power over USB?
[Xoom Android Development] Droidem:
It draws power from the USB. Its a western digital my passport 1TB.

Sent from my Team EOS JB Xoom
[Xoom Android Development] JoshWithrow:
Been using it WO red booting in lots of apps for days. So far no slowdown. However, at times the browser becomes unresponsive even after fiddling w the uastring. Facebook website seems to hang when trying to navigate recent posts menu.

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

He stated before that USB powered drives won't work. They require an external power source.
[Xoom Android Development] Droidem:
That's confusing because I can use an app to mount it without any additional power...:confused:

Sent from my Team EOS JB Xoom
[Xoom Android Development] SamuriHL:
Again, I also used a 2.5" external drive on the Xoom without external power. Worked fine.
[Xoom Android Development] thingnblah:
What I had said was that the xoom may not be able to power the drive. Different drives have different power requirements, some will work some will not. When I plug in a flash drive it auto mounts in /storage/usb0, check there for your data. If it does not see the drive and you cannot mount it via storage settings try plugging in a flash drive and see if you get the same behaviour. The idea here is to determine the point of failure so as to better assist you.
[Xoom Android Development] MWFD:
These may be noob questions so I apologize in advance if so. I just bought Android Overclock because my Xoom was getting very hot and I wanted to monitor the temperature. It is at 102 degrees Fahrenheit and I have the ROM (139) set at 216 min frequency, 1408 max using interactive governor. Is this too high of a temperature and if so why is it running so hot when I've seen others post similar overclock settings with mid 90s temps. Also, is there a way to see the temperature in the ROM without having to use the Android Overclock widget?

Thanks
[Xoom Android Development] Droidem:
I use temp+CPU v2 www.tinyurl.com/ckyxjhw

Sent from my Team EOS JB Xoom
[Xoom Android Development] Droidem:
So i took your advice and plugged in one of my thumb drives and it still does not auto mount. Also I froze my mounting app using TB thinking that it messed with something. Tried again and nothing. So then I defrosted it and mounted using the app and it works. Any idea?

Sent from my Team EOS JB Xoom
[Xoom Android Development] bigdave240:
Maybe try

uninstalling the app then reboot and try it.. i just mounted my usb thumb drive by simply plugging it in and as usual it mounted correctly.
[Xoom Android Development] Droidem:
OK so i did what you asked and still no joy. Guess I'll keep with my original plan. I'm starting to think my knockoff is a true knockoff and does not support OTG capabilities.

Thanks for the help anyway.

Sent from my Team EOS JB Xoom
[Xoom Android Development] bigdave240:
I looked at the link you posted a bit back and I think that is where i got mine but they are pretty cheap so not about the quality. At least it works with an app. Still pretty useful
[Xoom Android Development] Droidem:
Thanks for helping me out this whole time though

Sent from my Team EOS JB Xoom
[Xoom Android Development] kcrudup:
This is in #140 now. Please do this, and report back to me on slowdowns and lags. Thanks.

---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------

FWIW, this is exactly the cable I have (and I have three). Works perfectly. (It's funny how prices change on Amazon- I'd paid like $3 ea.)

What format is the external drive in, on it's first active partition? I believe the system natively only supports FAT, ext[234] and NTFS, and on the first partition only.

---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------

It must be some app you're running. BTW, what's your "Up Time" vs. "Awake Time"?
[Xoom Android Development] freeky1:
Why does the GooManager keep telling me there is a new Rom when I have already upgraded to 140?

---------- Post added at 02:39 AM ---------- Previous post was at 02:21 AM ----------

Actually, I guess a better question is why does my Xoom still say it's on 139 after downloading 140 twice and installing it three times?
[Xoom Android Development] rlmesq:
I bought a super-cheap OTG cable on Amazon... 79 cents with free shipping (from China, so it took about ten days).

Plugged in a 16 gig flash drive I was using to transfer files to my car, opened Astro file manager, and it works flawlessly. I'm able to play the mp3 files.

http://www.amazon.com/SANOXY-Female-On-The-Go-Adapter-Samsung/dp/B005GI2VMG/ref=pd_cp_cps_2
[Xoom Android Development] monkeybone12:
And I just bought a few thanks to you. never knew we could do this. Neat!

Jelly Beaned Moto Xoom
[Xoom Android Development] freeky1:
I was prompted by GooManager to download the 140 update again...

So, now I have downloaded the 140 update three times and installed it four times, and I am still on build 139. What gives?

And I am still being prompted that there is an update for my rom!
[Xoom Android Development] tomcrown1:
this is a winner for me. Browser opens up faster than before. No force close on browser.

Hulu + now works and video does not shut down.

This is alpha no bugs or anything just pure joy!!!!:o:angel::laugh:
[Xoom Android Development] SamuriHL:
OMG you're right. I just checked and it's working for me, as well. It was NOT working for me earlier this weekend so this is great!!
[Xoom Android Development] kcrudup:
Summamabitch! It does!
[Xoom Android Development] DioNYc777:
unfortunatly, settings has stopped

Thank you for the great ROM.

So far, I found only two issues (errors - unfortunatly, settings has stopped) when I'm trying to open "Select a theme" and "Device settings" from EOS Settings. I'm on build 140 with no extra customizations.

Xoom with Verizon 4G.

Thank you
[Xoom Android Development] Asphyx:
LOL Now that you got the new 140 running Hulu I'm almst afraid to point out to the Devs that Google released new Binary Drivers for the Xoom Jelly Bean for Nvidia and WiFI/BT

https://developers.google.com/android/nexus/drivers
[Xoom Android Development] kcrudup:
Thanks- I'll look into these, but so far nothing in video nor BT nor WiFi have changed since January, despite them putting out new packages all the time. (ETA: yeah, there's nothing new; I think Google just puts out new packages so the release names match up).

... and fear not- as much as I use Hulu+, now that Hulu has gotten their sh!t together I promise nothing I do will ever break it! (BTW, nothing we did made it work- they just fixed their servers or something.)
[Xoom Android Development] rlrbjr:
Anyone else having problems with News 360 on build 140. It crashes almost immediately for me.
[Xoom Android Development] Asphyx:
Yeah I didn't think much would have changed if at all since the OTA anyway but hey you never know!

As for Hulu isn't that all tied up into the aame server farm as HBOGo and the Max App?

I know they recently updated the HBO Go which I think might carry over to the other services. I could be mistaken about the linkage there though.
[Xoom Android Development] xjack:
I had this problem while on 136 or so.... Removed the news360 widget, uninstalled, then reinstalled from play store and its been mostly fine since. (Now on stable eos3)
[Xoom Android Development] Droidem:
OK so on my portable hard drive the first active partition is NTFS. However upon further inspection I had an inactive partition consisting of 7MB. So I'm in the process of getting rid of it.

On my thumb drive the first active partition is also NTFS. So i don't know what is going on there. Any ideas?

Sent from my Team EOS JB Xoom
[Xoom Android Development] kcrudup:
if it's not the first one, it won't matter (so no need to mess with it), and it appears your issues are deeper, anyway:

if you have access to "adb", then plug in the drive, wait 10 seconds, unplug the drive, then send me the result of "adb shell dmesg". If you don't, grab "Lumberjack" from the Play Market, then send me the kernel logs (dmesg) after doing the plug-in/wait/un-plug on your external hard drive.
[Xoom Android Development] Droidem:
Sent you a pm kenny

Sent from my Team EOS JB Xoom
[Xoom Android Development] slider2828:
Hey guys, new flasher here for XOOM, but been on galaxy S flashing....

Anyways, I am flashing GAPPS 7/26 and EOS GAPPS and both freeze during copying files while in CWM 3.2.0.0 R4c....

Can anyone help?
[Xoom Android Development] Moricon:
Swich to TWRP 2.2 for your recovery. Make sure you are using the correct gapps. It's from 8/1 I think.

Sorry 8/2. Use the link in the OP.
[Xoom Android Development] Droidem:
I don't know what I did but now I can't even mount the hard drive using an app. The app force closes on me. ... fml...

Sent from my Team EOS JB Xoom
[Xoom Android Development] slider2828:
I am trying twrp 2.2.2.0 and still doing the same thing :(
[Xoom Android Development] rlmesq:
Rogue Recovery seems to work for everybody... especially with the radios, which can be really tough to flash.
[Xoom Android Development] dweezle:
Just to be certain the gapps file is called: gapps-jb-20120802-eos-signed.zip

The current Rom is called: EOS-stingray-20120923-140.zip

Are those the files that are freezing while you are trying to install them from TWRP v2.2.2.0?
[Xoom Android Development] bigdave240:
Try uninstalling the app then reinstalling it.
[Xoom Android Development] Droidem:
...why didn't I think of that? It worked though. Thanks

Sent from my Team EOS JB Xoom

OK so I guess it kinda worked. It didn't force close upon trying to load it with a USB stick, but when I plug in my hdd it force closes. I hope Kenny can figure out what's wrong with my tablet so I don't have to use an app (no rush Kenny).
[Xoom Android Development] bigdave240:
Very strange indeed. Have you ever done a full factory reset? (i think i remember that you did though)
[Xoom Android Development] electroman987:
Hey guys,

Just had a freeze up this afternoon after I was trying to uninstall an app using system settings under app tab. Had to hard reboot to get it to respond. Which log do I need to upload from lumberjack and how do I recover a previous log after a reboot? Thx ahead of time. Just trying to help the process. On n139.
[Xoom Android Development] Droidem:
I can try that. I guess it wouldn't hurt.