yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bacon612:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Added them to 177? Ill give them a whirl...
[Xoom Android Development] rob62551:
Not sure what row scheduler is, sorry! But swipe to wake works. Both across and top to bottom of screen.

Thanks for your great work BRD

Did a little research as to what it is. Still not sure how to test aside from the fact I do see an improvement in performance overall with this build.
[Xoom Android Development] twinkyz1979:
3 hours to download 177? something doesn't seem right here

I am seeing big improvements in the loading of most programs with the 177 build. i am loving it a lot.
[Xoom Android Development] shpitz461:
How do I set to RoW? Trickster MOD doesn't list it as an option for I/O.
[Xoom Android Development] Mjamocha:
Roger That.

EDIT Update - not seeing the ROW Option

It is

R

ead

O

ver

W

rite Scheduling. It gives READ IO requests as much priority as possible.

Concept of ROW scheduling:

The requests are kept in queues according to their priority.

If there are READ requests in queue - they get sent first but it won't lag on

the WRITE requests. A scheduler gives way better optimization based

on the users needs.
[Xoom Android Development] atloops:
Viewing xda forums using stock browser gives the following error: "Connection Problem. There was a network error"

Page seems to load and is viewable with exception of my not being able to login to xda and the doubleclick ads not showing on right side of page.

JavaScript console reports "Unsafe javascript attempt to access frame with URL...etc. Domains, protocols and ports must match."

I searched around yet couldn't find anyone else reporting this problem. The error also appears when viewing The Weather Channel site.

Running 177. This also happened to me on 176.

Since the JavaScript console is making mention of a protocol/port mismatch, I can't help but wonder if this has anything to do with the loopback address being set in the wifi settings as reported here: http://xdaforums.com/showthread.php?t=2203918

Also received the error "Connection Problem. Authentication via the proxy server was unsuccessful" when viewing Verizon website. I don't use a proxy server. (At least not one that I know about.)

---------- Post added at 10:08 PM ---------- Previous post was at 09:30 PM ----------

OK, I figured out that the problem has to do with something in the build that is setting my wifi proxy settings manually. I can change the proxy settings to NONE but upon reboot they are switched back to MANUAL with Proxy Hostname 127.0.0.1 and Proxy Port 3128.

Can someone please confirm if this is isolated problem(?) and if there is a fix?

Thanks.
[Xoom Android Development] REHolt218:
I'm having random reboot and SoD problems with 177. That hasn't happened in a looong time.

---------- Post added at 10:50 PM ---------- Previous post was at 10:39 PM ----------

Not seeing those problems here, just the random rebooting and SoD. As long as I don't let it sleep everything works great between reboot's.
[Xoom Android Development] bigdave240:
Not seeing the proxy or reboots here. Seems ok. Swipe to wake up works fine and xoom goes into deep sleep and wakes up ok.
[Xoom Android Development] dccrens:
Sweep2wake

I took a nandroid and then loaded up 177. I wiped cache/dav loaded 177 & GAPPS; wiped again and rebooted. When everything came up, overclocking dumped and reset and everything was painfully laggy. I got FCs with several apps and text-to-speech would hang and FC.

I then wiped and restored 176 and all was well. SO... I then reloaded 177 following the same proceedure and it boots and runs great. Must have been some random quark spun in the wrong direction during the first load....

Seems to be a bit smoother than 176. My only questions is how do you set sweep2wake? I looked through every setting I could think of and could not find it. When I sweep a finger across the bottom of the screen and down from the top, nothing happens, so I assume you have to set it?

Thanks again to EOS for keeping the Xoom the best tablet there is.
[Xoom Android Development] shpitz461:
I usually wipe twice then flash, but since I'm always on EOS4 I just flash ROM & GAPPS then reboot, no need to wipe anything.

I've been running 177 for several days and do not experience any of these issues above. The only issue I have is the framerate for the camera seems slow, recording feels ghost-like, lack of FPS. Anyone else?

But it's been like that with every 4.2+ ROM, in 4.1 it's fine.
[Xoom Android Development] bigdave240:
I didnt set up anything on mine for swipe2wake. You have to swipe from the vvery edge to the opposite edge. Seems like anything less wont work.
[Xoom Android Development] rob62551:
Any Ideas

I also tried Trickster Mod and ROW does not show up on list of I/O options. Tried reboot and even a reinstall of build 177.

Curious if anyone has successfully obtained this option and how so. Thanks!
[Xoom Android Development] Asphyx:
Unrelated to 177 (been happeneing here since 173)

Anyone else having issues with Clock Stopping on them?

Wondering if I need to do a factory reset here....
[Xoom Android Development] Tiger62651:
Don't know if anyone else has this problem but since updated to 177 my screen wont turn back on. Have to Vol up and power to force reboot. Worked fine for few minutes and tried on then off at intervals of several minutes. But after sitting for hour it wont turn screen back on. Even holding power button does nothing. I didn't change any settings since update and don't see anything dealing with screen in options. Any ideas, tried installing again and wipe caches but doesn't fix it. Going to restore nandroid backup waiting for reply.

edit: had to deal with kiddies and screen went off and wouldn't come back on, haven't restored yet......

Edit2: nandroid applied works fine 3 hours later.
[Xoom Android Development] REHolt218:
I am having the same problem. Sometimes it wakes fine bust most of the time I have to reboot to get it to come back.
[Xoom Android Development] bigdave240:
Ha! You guys are bad luck lol. It just happened to me too
[Xoom Android Development] bigrushdog:
Maybe I should revert the sweep2wake. I'll keep an eye on this.
[Xoom Android Development] bigdave240:
I have seen this occasionally on previous releases as well. but not a lot. usually it seemed like it was when I had a lot of tabs open in the browser and maybe watching some video on utube and let it sleep. good to keep an eye on though.
[Xoom Android Development] Frazer Scott:
Is there a way for me to disable the sleep to wake? I keep turning the screen of by mistake. Other than that this rom is perfect :)
[Xoom Android Development] rob62551:
I am using Trickster Mod ( available in Play) . It has a toggle for S2W.
[Xoom Android Development] shpitz461:
I set mine to turn off after 30secs, never had an SoD, s2w always works. Sometimes, after a long time the tab was asleep, i swipe and it will take maybe 3-4 seconds to wake up, I'm guessing it's 'cause of the weather widget I got installed on the lockscreen.
[Xoom Android Development] bigdave240:
Ok, maybe i am a little slow here but i just realized that the swipe is a toggle. If its on it turns off, if off it turns on. Hardly any use for the power button now. Awesome
[Xoom Android Development] REHolt218:
May just be my imagination but if I leave 4g on it seems to be better. With just wifi on it was happening almost ecru time it went to sleep. Today it only happened once with 4g on.
[Xoom Android Development] bigdave240:
bt works fine for me. i use the Logitech Z515 speaker and it sounds fine and paired right up no problem. pretty complete rom at this point. great job as usual. running 163
[Xoom Android Development] marnett2005:
I got data to enable for a while, but on reboot it won't connect.
[Xoom Android Development] liftman-:
make sure your settings didn't revert.

verizons had 4g problems in columbus oh today
[Xoom Android Development] marnett2005:
It seems like if I toggle to CDMA/LTE to just CDMA and back it picks up 3G.
[Xoom Android Development] bigdave240:
did you check to be sure the cdma subscription is set to ruim/sim? Maybe it was reset.
[Xoom Android Development] Kamau54:
Just a clarification.

If you're coming from #3, you still have to perform a full wipe/factory reset before installing this version?
[Xoom Android Development] khanh1289:
Yes, it's a .1 version jump.

Thanks for all your hard work dev's. Much appreciated. The 2 years old Xoom lives on :)

Sent from my Nexus 4
[Xoom Android Development] kentedman:
I've noticed the signal strength seems a bit wonky at times, but the connection seems OK nonetheless. I know there was talk in the Everest thread about the signal strength indicator not reporting correct values because of a change in the way signal strength is reported in 4.2. Maybe we're seeing some of that effect??

Activation takes FOREVER (once you switch subscription to RUIM/SIM), but once set, it hasnt ever reverted. even updating nightlies.

maybe wait it out a little while and see if your connection steadies. could be network issues ??
[Xoom Android Development] bigdave240:
Noticed that the artifacts effects i was seeing on some web sites seems to be fixed in 163. Nice!
[Xoom Android Development] freeky1:
Awesome! I knew there was a reason nobody had posted in the old thread in over 12 hours! Thank you Team EOS!
[Xoom Android Development] rob62551:
+1

On 163 and BT works great. Using Boselink speaker.

So far 162&163 no problems!

---------- Post added at 08:04 PM ---------- Previous post was at 07:25 PM ----------

Just noticed that when I update rom and install Xoom.Only Gapps, Google Play notifies me that Gmail, Current and others need to be updated.

Should I update them?
[Xoom Android Development] runandhide05:
Sure update them,
[Xoom Android Development] liftman-:
my bose soundlink will not connect, did you do a clean(factory reset) install or a upgrade?

i put 150 on and the bose will alway make a connection, even after i clear out the bose memory.

clean install of 163 is a no go.:(
[Xoom Android Development] rob62551:
I went from 150 to 162/163 with full wipe. BT worked on 150 and continues to work on both 162/163.

I just powered up my Boselink when my Xoom BT was on and it connected no problems.
[Xoom Android Development] liftman-:
thanks

still have issues getting mine to connect:eek:
[Xoom Android Development] rob62551:
Don't know if you've tried any of these ideas from Bose. Hope this helps. BTW, does BT work on any other device?

http://worldwide.bose.com/productsu...soundlink_mobile_pairing_connecting/page.html
[Xoom Android Development] micjgeoghegan:
Need a little help here. I cannot for the life of me get my 4G to work. I have the network mode at LTE/CDMA, and when I try to change the subscription from NV to RUIM/SIM it just swaps right back. I've reloaded and rewiped a few times, and redownloaded 163 and verified the MD5. Am I missing something?
[Xoom Android Development] liftman-:
thanks

i was just doing the factory reset(mute 10 secs) should clear it all, always work in the past. so i tried just the Bluetooth button reset snd it work!

yea

runandhide trash that bug report-sorry bud
[Xoom Android Development] runandhide05:
Good to hear!
[Xoom Android Development] khanh1289:
Currently, when I try to use Google Now from the lock screen, I have to unlock the device first. On my phone I didn't have to do this. My lockscreen is just the simple slide to unlock. Is it supposed to be like this with this rom? Or mine is messed up?

Thanks,
[Xoom Android Development] bigdave240:
Noticed sometbing that might be related, it turns on over and over then it wont. Reboot and there is notice of an update for one of my apps. This has happened every time so far. I haventhad it a lot but i thought i noticed this pattern in a few previous builds but it wasnt happening that often so i didnt put it together. But after each time it wont turn on and i have to reboot, there it is, a notification of an available update. They are all valid and for different apps. Anyone else notice this or just a coincidence?
[Xoom Android Development] REHolt218:
Didn't notice it until you mentioned it but looked this time and had the same thing. I am also having a problem with Dolphin browser crashing. Something else that I haven't seen in a long time. I don't recall seeing a DB update lately so not sure what changed.
[Xoom Android Development] rob62551:
Just posting to let developers know that I am not having the issues with newer builds of Stingray.

Been using Sweep2Wake with no problems. Great not having to use power button. It's been said many times that every Xoom tablet acts in its own way! I guess I am lucky to have one that cooperates more than others.

No reboots or SODs. An occasional lag loading web pages or loading apps. Nothing else of note so far. Hope to see what ROW I/O will do for this old toy!
[Xoom Android Development] bigdave240:
Been running 179 for a couple of hours. No issues so far. Very fast page load in stock browser
[Xoom Android Development] dweezle:
I was on 177, watching Netflix, when screen went black. It would not come back, power button would not get it back. Until I read some the posts here, I figured it had just died. Pwer button/vol up did restart it. Went to 179 and the screen did go black one time since then

. It happened when I rotated the xoom, 180 degrees. Pwer/vol. up restarted okay and it has not happened in the one hour since that event.
[Xoom Android Development] stevefxp:
NFL Mobile Support

Hello all,

I am running build 179 at this time. I cannot seem to get NFL Mobile to run on this build. I had posted a question about this in the Q&A section, and a person who responded indicated that only stock 4.0.4 will allow NFL Mobile to work. Is this true, or is there something that can be done to allow this app to work on JB.

Thanks,

Steve
[Xoom Android Development] bigdave240:
Well, same thing happened again. Put the xoom down and it went to sleep. Tried to wake it but no luck. Soft reset and when it did there was an update for some of my apps available. Have to figure out if i can turn off play store notifications?
[Xoom Android Development] Lare2:
How exactly does Sweep2Wake works. I'm turning off my display by error a lot when playing games. I'm also having the sleep problems mentioned above where the device wont wake up after screen is off.

I'm going to use Trickster mod to disable the Sweep2Wake feature as mentioned earlier and see if that resolves this issue.

I'm on Nightly 179 on Xoom LTE
[Xoom Android Development] shpitz461:
I think it's more useful if all the complainers start providing logs, I don't think it will ever get resolved when no logs are provided.

I have not experienced any of the locks people are reporting so I can't provide anything.

Guys with issues, did you try flashing ElementalX? That's the kernel I'm using. Maybe the culprit is in the ROM's kernel...

Swipe2Wake turns the screen on/off when the user fully swipes across the screen (vertical or horizontal). I can see playing games this can happen while not intended to... I wonder if the feature can be ignore when there's a 'fullscreen' app running (game, video playback, etc...)?
[Xoom Android Development] bigdave240:
Calling us complainers is a little harsh! a lot of us may not have the experience level that you do and are just reporting issues here on the devs pages. I would like to suggest that the process for collecting a log file be put on the first page with the install instructions. I have done one but it was a long time ago at the request of one of the devs and I didn't keep the directions unfortunately. as far as flashing other kernels goes I am not sure that I will go that far. If BRD or one of the other devs says to do that I might be inclined but for now i will stay with what they give us in the rom. just my 2 cents worth.

edit: googled how to do the logcat and will do that if it happens again. in the mean time, i turned off notification in the play store and it has not happened since. I will file a bug report shortly with this info.
[Xoom Android Development] mekeleee:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

just thought id chime in....no probs on 177 or 179...everythings working great....did want to mention, no swipe is necessary to wake or sleep. All it takes is touching both edges of screen simultainiously to trigger. Im assuming others have noticed this?
[Xoom Android Development] bigdave240:
hadn't noticed that one. wonder if that is why the gamer who posted is having it shut down on him. interesting.
[Xoom Android Development] Lare2:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

And that's what is causing problems with games. Most game control layouts are located at the edges of the screen.

-- edit --

Just tried it with a game on full screen, Earn to Die, and it does it as well. It turns off the screen off as son as you put down the fingers on the controls : (
[Xoom Android Development] Tiger62651:
Well since update to 179 been working just fine now. Swipe2wake little odd since sometimes I swipe longer to change desktops but it its more than happy to turn screen off but not back on, but power button turns it back on without problem.
[Xoom Android Development] mekeleee:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

bummer....be sad to see it go...even the two finger thingy/glitch works out well fir me. I turn this thing on n off 100+ times daily while working betweeen multiple devices. Sweep saves me from usin no less than 3 different auto on apps depending on circumstance. Maybe a workaround possible/disable toggle of some sort? Trickster doesnt seem to work on my rig.(tried just to verify). Still... my vote is to keep this useful feature.

recap: @bummer...thought I read.."game changer was having feature shut down"(as in removed from build)...note to self squint less at terminal/get glasses...lol
[Xoom Android Development] bigdave240:
was sort of wondering where you got that from LOL. Hope they keep it in the builds too. I like it
[Xoom Android Development] bigrushdog:
https://review.teameos.org/#/c/123103/

I think we can keep it. We just gotta get it under control. I'm doing a toggle as well as settings controls for set on boot. It will be disabled by default. I may want testers on this tomorrow. Hit me on the chan.
[Xoom Android Development] xjack:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Just found this by accident while moving shortcuts around. If you're moving shortcuts to the left and go one screen too far, the swipe back to the right will sleep the Xoom also. Same feature, or something different that I can't find a setting for?
[Xoom Android Development] mekeleee:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

off topic: brd...maybee a little assist @ iruiz regarding btrack efforts... 4.2 kern adjusts and such... :) ty
[Xoom Android Development] bigrushdog:
Ugh. I've tried so hard to offload this thing :laugh:
[Xoom Android Development] mekeleee:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

haha,.but you the best..angel(devmind)..no one cqn keep uper:)... imamazed..

---------- Post added at 01:46 AM ---------- Previous post was at 01:39 AM ----------

ok...brd...we about to feed you grapes...who we im james... i work for silly folk....

---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------

ok...you are my hero...and then some....brd..we should hang ..im in fl18 santamon29.. ty always
[Xoom Android Development] bigdave240:
180 is out, the list is long. It definitely has a toggle for swipe2wake now. So far so good. Got go give it a day or so. Thanks devs!
[Xoom Android Development] REHolt218:
I have been runing all day. I was hoping it solve the SoD problem. It is definitely better but I just had to reboot to get it to wake up. Same scenario as before: on reboot it showed a rom update available (I'm already on 180) and app updates in the market.

---------- Post added at 07:14 PM ---------- Previous post was at 07:00 PM ----------

Is there an explenation of the various I/o scheduler seettings and when one might be used as opposed to another?
[Xoom Android Development] shpitz461:
Have a look here
[Xoom Android Development] xjack:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Anyone having swipe2wake on by default and toggle doesn't work?
[Xoom Android Development] bigdave240:
works here when it is set to start on boot.
[Xoom Android Development] bigrushdog:
Make sure it disables if set on boot. And make sure the toggle actually works.

I need testers on #xoom for a possible bluetooth tether fix. I brought in bluetooth network stack from common/3.0. Should do the trick

https://review.teameos.org/#/c/123121/
[Xoom Android Development] bigdave240:
verified that it disables if i check the box then un check it. and toggle works correctly. i have it set for boot
[Xoom Android Development] bigrushdog:
Perfect, thanks bro big time. It's hard doing these things without a test device.

Bluetooth tether fix test build

HERE
[Xoom Android Development] bigdave240:
I have never tested tethering w/ bt. I just tried it with the original stack that came in the rom and it causes my xoom to lockup everytime it goes to sleep. I will dl your fix and see if that helps. brb

---------- Post added at 02:43 AM ---------- Previous post was at 02:06 AM ----------

no luck but not sure i am doing it right either. i enabled and paired my xoom to my BT enabled laptop. I turned off the wifi on the laptop and turned on the PAN but the laptop never shows that it is connected for internet. suggestions?
[Xoom Android Development] REHolt218:
Thanks, great resource for understanding some of the tweeks.
[Xoom Android Development] xjack:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Either I'm misreading or my behavior is different than yours. Toggle works fine once I rebooted and tested a bit.

However If I set the toggle to off and set on boot to on, then s2w is active after reboot. Is this consistent with your behavior?

It appears to be the opposite for me of what is written in init.d. my goal is to disable s2w persist.

Edit : solved by modifying init.d to always echo "0".
[Xoom Android Development] bigdave240:
so if you don't check for it to be active after boot and don't check the toggle it isn't active right? at least that is how mine seems to be working. which effectively makes it disabled. or am i not reading your post right?
[Xoom Android Development] xjack:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

The problem I was having Is that it was still active regardless of checkbox status. Both boxes unchecked still had s2w active on reboot.

Solved it by clipping the init.d, but will revisit on my next wipe.
[Xoom Android Development] shpitz461:
I'm getting system UI FC's when enabling/disabling data, anyone else? Happens with 179 and 180.

Also happens with 177.
[Xoom Android Development] bigrushdog:
I'll look into that fc.
[Xoom Android Development] dweezle:
My xoom freezes in about five minutes if I set lock screen to "none". I'd post a log if I knew how to do it. Happens on both 179 and 180.
[Xoom Android Development] bigdave240:
After looking at it closer i re-tried what you describe and yes it is active on boot regardless of checkbox status. What i tried yesterday was to make sure that it could be disabled even if the boot box was checked. that works. but with both boxes unchecked and a reboot it will be active when the xoom comes back up and both boxes still show unchecked. sorry for the confusion.
[Xoom Android Development] xjack:
No worries, I probably didn't explain it quite right. I did a TWRP reset and got the same result, as well as in 181. It's not really important since the toggle is more important than it being disabled on boot.
[Xoom Android Development] bigrushdog:
http://xdaforums.com/showpost.php?p=39905615&postcount=1839

Adhoc support.