yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] pamaguin:
Yes there is no LTE in my location and I my Xoom has been upgraded; got a free dock too

And as for the Logcat, you will need to give me instructions on how to and I will not be able to get to it till after midnight. I have to go to work right now
[Xoom Android Development] kcrudup:
Why not just hit the "back" button or tap elsewhere on the screen?
[Xoom Android Development] dboftlp:
re: feature requests :) I know...

anyway, gapps could use an update, just sayin.

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] rlmesq:
If you don't want an app to do anything, why would you click on it in the first place? :confused:
[Xoom Android Development] runner1717:
Going to be baking in some 4.2 goodness?

Mike
[Xoom Android Development] Droidem:
Has the source code for 4.2 been released yet?
[Xoom Android Development] Asphyx:
Here is the issue it'a about the docking and maybe the better request would have been to ask for a setting to shut off docking app action.

I tend to use my unit at home as a media device and the dock is on a low shelf of the media station so what I have been doing is selecting the media I want to see, then putting it into the dock to send to the TV. But everytime I do that it totally messes me up by asking what to run as default for docking and throwing my program into the background making me have to operate the unit from the dock to bring it back up which sort of defeats the purpose of selecting the media off the dock (comfort) in the first place.

So perhaps what I really want is a way to shut off the autoload App on docking.

I didn't click on anything this is mostly to stop it from trying to run something everytime I stick it in the Dock!

I'm sure there are other examples where it would be useful.

Personally I don't really like the Just Once second press. I would rather go back to the check box to set it as default instead. But thats another request entirely and not something I would expect the devs to try and change since it is the way Google has chosen to do it from now on.
[Xoom Android Development] rlmesq:
That's odd. I have the HD dock and it just goes to a clock screen when I insert the Xoom. I have to hit the home button, then it goes to the lock screen. (Maybe it's because I have a pattern lock set.)

Ahhhh, now I get it.
[Xoom Android Development] Asphyx:
Thats because you selected the Clock app as the default option for docking.

I don't want the clock I want the Media player unfortunatly the program I would RATHER run on dock default (the Media Player) isn't listed in the option to autoload.

What happens is the clock (or the dialog since I removed the default setting to the clock app) shows instead forcing me to go back and load the media player all (Moviebrowser UPnP) or make all my selections to view while it's docked.

I would prefer my Unit not to do or ask for anything when it docs. My Home screen shows me everything I need when docked anyway and I would rather whatever is on screen at the time I dock it to stay there and not do anything else automatically.

I think a check box to do nothing on Dock would solve this, either via the dialog or in Dock settings.
[Xoom Android Development] rlmesq:
Yep, seems I set clock as the default app some time ago & forgot about it... so I cleared the default to see what would happen.

It's surprising that only Clock, TuneIn Radio and Tasker showed up as selections, but I set Tasker as the default app, then created a task to play Pandora. Works just fine for me... I dock the Xoom and Pandora starts playing.
[Xoom Android Development] Asphyx:
Yep not sure how it decides to pick which apps to display (I guess sort of the same as based on .ext type)

I never installed tasker on my Pad but have it on the phone...You might have given me the solution I need here. Thanks!
[Xoom Android Development] kcrudup:
Ah. Get the app "Dock No-Op" from the market, then when you set it in the dock, select that then make it the default.
[Xoom Android Development] mptpro:
Where are you all setting the default app for dock? In settings / dock all I see is settings for "sound when inserted" and "audio"?
[Xoom Android Development] Droidem:
I'm thinking he means when he actually docks the app selection pops up when you don't have a default app set up
[Xoom Android Development] Asphyx:
Thanks that did the trick!

Yep when you dock the unit the action dialog pops up, if you select an app and press always it won't ever ask you again and you have to go into the settings/apps find the app that was set and clear defaults
[Xoom Android Development] qiuge:
How about xoom mz600? :confused:
[Xoom Android Development] Droidem:
Has anyone noticed that on 150 the icons on the notification bar sometimes disappear? Or is it just me?

Sent from my Team EOS JB Xoom
[Xoom Android Development] bigdave240:
Haven't noticed it here. Only time I see that is if a notification pops up but then they come back.
[Xoom Android Development] SamuriHL:
Chirp chirp. :D Anyone home? Uh, anyway, 4.2 is going out on AOSP today. Hopefully we'll see an update in the near future?
[Xoom Android Development] dccrens:
Seems like after 150 everything just died here...
[Xoom Android Development] SamuriHL:
Yea, and 4.2 won't come out for Xoom officially, either. Start planning your exit strategy.......now. :) LOL
[Xoom Android Development] Moricon:
Well it is a 2 year old devise. Eventually time will catch up to it. Don't thing it's done quite yet though.
[Xoom Android Development] SamuriHL:
Not yet it's not. February....then it'll be a 2 year old device. That's still 3 months. But yes, it's getting older. I hope they don't think we're going to replace tablets every 24 months though....cause that gets expensive.
[Xoom Android Development] Moricon:
I am betting they hope everyone will do it ever year. Lol.
[Xoom Android Development] SamuriHL:
They can kiss my....uh, NO. Just no. :)
[Xoom Android Development] Moricon:
I agree. Belive me.
[Xoom Android Development] Asphyx:
Considering it is the first Android Tablet EVER I'm actually surprised it has lasted as long as it has truth be told.

What is more depressing is there really is no other option that has all the features this xoom does including WLAN in the two years since it was released!

I would have less problem jumping if there was something that actually had more features. I guess I will have to wait for the next gen Nexus10 to get WLAN.

Or just carry a puck around from now on.
[Xoom Android Development] SamuriHL:
This right here. The Xoom, for the slow start and troubles it had in the beginning, is still a majorly awesome device. I'm not going to get a new tablet until at least March at the earliest. I don't see the need just yet. Eventually something has to come out that can match or beat the Xoom in quality and balance. So far, I don't see it. The NX10 doesn't impress me enough to want to replace my Xoom with it.
[Xoom Android Development] dboftlp:
:(

I'm considering missing my WAN capabilities & moving to next gen platform.

Will hold out till next year if I can.

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] Asphyx:
I understand the reasoning for not wanting to include 4G because of all the carrier complications involved and if the carriers didn't want to charge extra (read: Verizon) for tethering to your phone I almost wouldn't care about the LTE.

But the Xoom does everything I need it to do and until something else comes out that does something I can't I'll stick with it.

The EOS releases have really solved just about all the problems I ever had with the Xoom.

And the truth of the matter is while 4.2 would be cool to have I don't see anything in it really making me say need to buy a new unit just to be able to run it.

The only ones who really need all that extra horsepower are folks who play a ton of games. To me it's mostly a media and information device.

The few games I play work well as is so no real need to spend another $500 on hardware I will hardly take advantage of. Would rather get a new phone with the money.
[Xoom Android Development] SamuriHL:
If these stupid hardware designers got themselves a clue, they'd make the WAN radios a plugin module that consumers could buy from their carrier of choice. Want VZW LTE? Go sign up for a plan and buy a plugin radio that slides into a slot on the tablet. Done. Want to switch to AT&T? Buy an AT&T LTE radio and replace it. But NOOOOOOO, you'll never see that happen. SIGH.
[Xoom Android Development] kcrudup:
Actually, we do have- somewhat- that abilty; after all, there's a "removable" Mini-PCI LTE radio in the LTE Xoom that could be swapped out for one of several versions (CDMA, GSM, LTE), but the issue is the radio software (RIL) to run them still would need to be configured somewhat.

I'm leaving for Australia soon and am actually under the gun to try and get that done for the Mini-PCI HSDPA+ radio module I have (Sierra Wireless unit), but I don't know if I'd be able to finish it before I have to leave. Rest assured that if/when I do, it'll be ported to the EOS ROM!
[Xoom Android Development] SamuriHL:
Yes, you're correct, that the Xoom "kind of" give us that ability . I want it more fleshed out as a standard for all tablets to use. In fact, I want the sim card to be part of the radio module. Since WiFi would be standard, they could require a quick update for the RIL over wifi when you insert the new radio. Done. How awesome would that be? Get a new tablet...no problem, pop out the radio and drop it in the new tablet. Those that want wifi only would just never buy a radio.
[Xoom Android Development] bigrushdog:
There's a ton of devices not officially supported in aosp, yet they run aosp just fine. I haven't seen the 4.2 source yet but I have no reason to believe Xoom can't run it. My only concern is does the Xoom have the horsepower to actually run it half way smoothly. We'll find out soon enough.
[Xoom Android Development] SamuriHL:
Let's not forget we still haven't gotten official JB yet. Meaning 4.1.2. Moto keeps pushing that back. So it's not TOO surprising to see that we're not getting 4.2.
[Xoom Android Development] kevdliu:
I think it's more verizon than moto. Or maybe it's both but most of the time verizon is the problem. the GSM galaxy nexus has 4.2 factory images while the verizon variant does not. :(
[Xoom Android Development] SamuriHL:
No, it's VZW. I'm a Bionic user. I know all about VZW and their crap. Let's be honest here....the wifi version's had it since what, July? You really think it takes Moto 4 months to add a radio driver? LOL. VZW is just ridiculous about certifying releases for old devices cause they simply don't care.
[Xoom Android Development] Asphyx:
That would work but I am hoping by the time 5G rolls out that all these spectrum issues and voice networks are gone, All carriers are forced to use the same wireless data standards so it doesn't matter which carrier you use anymore which will not only make coverage universal but force carreiers to be competitive on prices as well. Then the coverage issue goes away as any carrier can charge another a roaming fee for access to the tower without standards getting in the way.If they are so insistent on charging us for the amount of data we use then it's in thier interests to make sure we can keep getting data even outside thier own coverage area.

Too bad Moto didn't have the foresight to make that easily swappable.

It would be similar to the M-Cards the cable carriers now offer to replace set top tuners for TVs who have the capability.

Yep thats all on Verizon. By now I'm sure they would prefer you just buy another unit from them so they get the folks who still have unlimited data off thier books.
[Xoom Android Development] dweezle:
Nexus S And Motorola XOOM Most Likely Officially Stuck On 4.1.2
[Xoom Android Development] Asphyx:
You could say Xoom is stuck even further behind because the LTE Xoom still doesn't really have it.

There are two realities in android land...The Official and the Developer...

Unless there is some driver related issue I don't know about I'm sure the Team EOS reality is much more important than anything Google or Verizon have to say!

LOL
[Xoom Android Development] SamuriHL:
My thoughts exactly. I've not run official software on my xoom since January.
[Xoom Android Development] bigrushdog:
The key is older xoom binaries playing nice with new android framework. We had to tweak phone framework just a hair to make lte work on jb. But i don't believe the internal telephony has really changed from 4.1.2. Basically there's no reason to believe that the Xoom can't run 4.2 any better or worse than 4.1.2
[Xoom Android Development] Asphyx:
LOL you should give Verizon a call because I bet they haven't figured that out yet which is why we are still waiting for JB from them! LOL

I suspect if they ever get around to releasing the Stingray version of JB those files would work fine on the minor tweak.

From the best I can gather from 4.2 it's mostly interface tweaks not anything deep in the core hence the minor revision versioning number.
[Xoom Android Development] kevdliu:
I doubt VZ will release any more updates for the xoom since updates is one of their (dirty) ways of getting people to upgrade and spend money.
[Xoom Android Development] razorseal:
Looks like end of the road for this one.
[Xoom Android Development] Asphyx:
Yep but then again what would you upgrade to?

The 10" Galaxy which really isn't much more than 3-4 months behind in the EOL status than the Xoom is?

The Xoom2?

Thats what is so disappointing, The Xoom is the first Android Tablet and the prototype used to create the Android Tablet universe and yet two years later you are still hard pressed to find a unit that has all the features the Xoom has all in one package.

It's either that or the IPad and if thats the case Verizon should just get out of the Tablet Market altogether (they sure aren't competitive in pricing) just sell WiFi Pucks and we all carry and extra device around.

If they were smart and had figured out that Tethering is a money maker not system breaker for them now that they got rid of unlimited, they should just sell WiFi Tablets with tethering options on the Phones they sell.

Nah not until KLP comes out can you really say that IMO.

4.2 adds some minor interface tweaks and multiuser accounts but from an App standpoint the only thing that will have problems on our units from what I could see is the higher end games that rely on the proc and GPU more than the Xoom is capable of.
[Xoom Android Development] dboftlp:
Received an iPad 2 16GB WIFI I won at a vendor event last night. Of course the Nexus 10 16GB is sold out as of yesterday, meh.

But wait! Just checked the Play Store & it was back. Delivery in 2-5 business days & I can sell the iPad & keep my Xoom! w00t!

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] bigrushdog:
And sense when have we relied on aosp to keep these devices running? Dude I just cracked toroplus radios in less then 24 hours of source dropping. And toroplus is not officially supported. But if you wanna put your Xoom out of its misery, we can take it to the desert with my

40 caliber and give it a proper burial :laugh: :laugh:
[Xoom Android Development] Moricon:
Sounds like we still have good stuff coming our way.
[Xoom Android Development] Asphyx:
LOL

Using terms like "Unsupported" or "Can't be done" are phrases that make Devs foam at the mouth and rabidly go after proven the person wrong!

It's phrases like those that the best Developers Live for!

As for me until this Xoom CAN'T do something I need to do you will have to pry it from my cold dead hands.
[Xoom Android Development] twinkyz1979:
I don't think i have ran stock anything since i bought it. if i have it has just been to see what it was like then go back to my choice of dev rom. I must also say i agree with the problem being VZW when it comes to getting things in a timely manner or at all.

Did i forget to say Team EOS kicks major @$$!!!! Keep up the great work us non-devs are used to. :)
[Xoom Android Development] Asphyx:
I think I actually ran stock for a week while I got busy and read all I could here on XDA regarding all the ROMS that were available and then when I figured out which one I was planning to install I read the entire thread for that ROM just to e sure what I could expect to face.

Something I wish more users would do before flashing because if you read the entire thread for a ROM just about all your questions are already answered and you can avoid asking the same question that was answered a month ago.

I finally picked EOS, Read the entire thread and have not gone back on that decision. It's just gotten better and better!
[Xoom Android Development] bigdave240:
i second that! So many issues are either already covered or would be totally avoided if people read and maybe re-read a couple of times before they did it.
[Xoom Android Development] Dedren:
This video's rental period has expired.

I recently bought a few movies from Google Play, but when I try to play them it says, "This video's rental period has expired". This used to happen when the DRM lib files were incorrect on other ROMs. Anyone know if this is a known problem that is being addressed?
[Xoom Android Development] Tom_S:
I had the same issue a couple of days ago. Several Google searches later, I found this: http://rootzwiki.com/topic/35609-toro-build-5-milestone-1-play-movies-license-fetch-error/ post #3

It worked perfectly for me.
[Xoom Android Development] SamuriHL:
Maybe a new option to toggle it on and off so people can switch between google play and hulu plus more easily. I'd choose hulu plus, personally, but, a toggle would work nicely.
[Xoom Android Development] Zaiaku:
Is anyone able to get Text to Speech working on any JB rom?

It's a feature that so far only able to get it to work on ICS.
[Xoom Android Development] apollyon0810:
I don't know if everybody knows this but me, but deleting (renaming) those files, as prescribed in the link, kills HDMI output on my Xoom.
[Xoom Android Development] Tom_S:
I watched a Google Play movie via HDMI after renaming the files. No issues at all.
[Xoom Android Development] alex94kumar:
coming over here from the Wingray thread to relay a post.....
[Xoom Android Development] SamuriHL:
Excellent. Can't wait to see it.
[Xoom Android Development] tomcrown1:
Whoa it was posted on the WiFi only site. If it had the 4G radio then iam sure that Team EOS would have posted the good news here.

My guess is that 4G is still not ready yet.
[Xoom Android Development] SamuriHL:
I doubt very much that a lot changed for the radio between 4.1.2 and 4.2. I suppose I could be wrong but generally the two branches are mostly kept in sync. So we'll see.
[Xoom Android Development] Asphyx:
I'm more curious if they have figured out a way to increase the size in the system partition. That would extend the life and solve the problem that seems to be at the heart of dropping Xoom from AOSP support.

If they have then we could even get facelock back for those who wanted it. (not me mind you I hated it as I don't really lock my Xoom)
[Xoom Android Development] bigrushdog:
We can't increase its size. However I don't believe we need to. I've got almost everything from 4.1.2 merged. Radio won't be an issue. I cracked Toroplus radio I'll pwn this one too.
[Xoom Android Development] Asphyx:
LOL BRD I never had any doubt you would get it working, Just curious as to what might be a stumbling block long term which from the best I can gather is that system partition.

There is another thread floating around XDA about being able to increase the sys through ADB but no actual details on how thats done.

My guess is it would require some sort of fastboot mod or something along the lines of a bootloader flash but I can't really speak with any intelligence on such matters.

Perhaps it is a hardware limitation and not really a partitioning problem.

You guys would know what the issue is far better than I would.
[Xoom Android Development] SamuriHL:
Don't mean to be annoying, but, do you mean 4.2 or 4.1.2?
[Xoom Android Development] Stratus41298:
Is there another Gapps package I can try out? Every time I flash this package it never works and i'm left without them. I've tried flashing several times and re-downloading the package.

Edit: To clarify, the package installs fine but it doesn't do anything.
[Xoom Android Development] bigdave240:
what package are you flashing? i use the 802 one and it seems fine

http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip
[Xoom Android Development] Stratus41298:
Is that the one that's posted above? If so then it's not working for me. Munno.
[Xoom Android Development] bigdave240:
what does it do when you flash it? you may need to wipe \system to get it working again.
[Xoom Android Development] jawonder:
You guys are Rom Engineers can't wait for 4.2 . Thank you for your hard work and dedication throughout the years .
[Xoom Android Development] Stratus41298:
Okay... I re-downloaded it for a third time and installed the 150 nightly and it worked. Not sure which part worked but it's all good now :)
[Xoom Android Development] bigdave240:
I always flash the rom first then the gapps.
[Xoom Android Development] apollyon0810:
That was a lie. My mom has a cheap refurb TV (thanks woot!) and I just had to mess with the cable. I just wanted to post here and say that nightly 150 has been the single most stable ROM I've ever had on my Xoom. I haven't rebooted in weeks and this thing just won't slow down. I love my Xoom so much. I've been trying to justify purchasing a Nexus 10 for Christmas and I just can't. My Xoom runs too well and I'm not a huge gamer, though that high resolution display... drool. Team EOS better watch they don't get sued by Google for cutting into their sales!

BRD, et all, you're my heroes! There should be some annual android developer awards or something. Been running EOS for almost two years now! No regrets!
[Xoom Android Development] bigrushdog:
Thank you for the kind words. I've been given the responsibility of leading the Eos project. Solarnz will bail me out of emergency situations if or when they arise. So, it's taken me a bit longer to merge our build tweaks and other misc behind the scene stuff. Good news is almost everything is back in place. Couple bugs here and there but I will have some test builds soon. I'm looking for device maintainers for all xoom builds as I sold mine a while ago. Especially with lte. So rather soon now we should have some experimental builds to play with. I'll keep you guys posted.
[Xoom Android Development] alex94kumar:
I know you probably don't want to give away too many details, but are all the new features of Android 4.2 included as would be on the Nexus 10? Barring a few, im sure though, since our device is almost 2 years older than that one
[Xoom Android Development] SamuriHL:
And just like that 4.2.1 is out. :D
[Xoom Android Development] bigdave240:
? is it on goo or somewhere else?
[Xoom Android Development] tomcrown1:
Their is a wifi only 4.2.1 out now. It is not from team EOS.

Will the new 4.2.1 be announced in this tread or will a new tread be started?
[Xoom Android Development] SamuriHL:
Huh? No. It's been released by Google. Not for Xoom. I'm just saying it got released for the Nexus devices this morning to fix that stupid december bug in the calendar.
[Xoom Android Development] bigdave240:
haha sorry. got all excited! i am having flashing withdrawal. back to patiently waiting.....
[Xoom Android Development] SamuriHL:
You and me both. 150 has been rock solid, though, so, it could be MUCH worse. :)
[Xoom Android Development] Droidem:
I have a lte xoom at your disposal for flashing if needed. :D
[Xoom Android Development] Asphyx:
from what I understand the main difference between 4.2 and 4.2.1 is December! LOL
[Xoom Android Development] EvilDobe:
Hey hey now don't forget the joystick and gamepad support. :)
[Xoom Android Development] bigrushdog:
Most of the new features are in gapps. So I don't know what features will be xoom compatible.