yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Phssthpok:
Secondary user settings?

First, awesome work. Just upgraded from EOS 3 stable to build 171 love the 4.2 goodness. I'm seeing two errors.

First, I'm getting something like at random: the LTE service has failed/stopped. I'm on a 3G Xoom so that may be a problem but didn't see it under 3.

The other error is more limited. If I "login" as one of the secondary users, go to settings, users, and select that use to make a change, say to adjust the profile icon, I get the famous "Unfortunately, Settings has stopped." I'm not even sure you can set secondary profile pics, but that seems odd behavior.

Thanks
[Xoom Android Development] jbelew:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I feel like a dummy. I went into the developer options to disable HW overlays and the animations as recommended several posts back. I accidentally hit the toggle in the upper right corner and it turned off the developer options all together. When I turned them back on, none of the options were enabled and I am fairly certain that I saw some check marks before I hit the toggle. Can someone please give me some hints which ones should be set? I tried reflashing 171 and nothing changed in those options.
[Xoom Android Development] bigdave240:
On mine stay awake, usb debug, verify apps over usb and disable hardwate overlays are the only thing checked
[Xoom Android Development] Asphyx:
No Biggie...

Truth is if the company didn't already pay for my phone I would keep the Xoom active, use it as my hotspot for my phone and do all my voice communication via GrooveIP and GTalk.

Unfortunatly Verizon is the only carreier with decent coverage where I live so it's pretty much them or nothing.

I did the month to month which was fine and I'm sure I can always restart it if the money situation loosens up later on.
[Xoom Android Development] TheGman125:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Is anyone having problem with the play store forces closing on you? I have wipe cache/dalvik and fix permission. It still giving me that area.
[Xoom Android Development] bigdave240:
google search updated yesterday and that caused fc's but the playstore seemed ok on mine. maybe try to uninstall the playstore update and see if it works?
[Xoom Android Development] dccrens:
Which new Tablet to Stay with Team EOS

Ok. I have had the Xoom since the month Verizon debuted it. I still like it. More so, because I have always run Team EOS Roms. Now, I am thinking about going to new hardware. Price isn't an issue. Only two things are a must. There has to be an EOS Rom for it and it has to be Verizon 4G capable. So, what would be the best choice?
[Xoom Android Development] Asphyx:
Personally I'm going to wait to see what Googlrola comes out with next.

We should soon hear about what influence Google will have on the phone design whenever moto makes it's next relase announcement and I would expect a Tablet will be announced at the same time or soon after and will decide from there.

If it has 4G or not will depend on how much Google wants to deal with Carriers since there is no one standard to support.

Perhaps they could set the bar for everyone and come up with a standardized radio port that you could switch operators with a simple switch of a card the way the original Xoom could switch from 3G to 4G. Not sure Goolge will be that ambitious though.

Sort of an M-Card (cable tuners) for LTE so to speak.
[Xoom Android Development] SamuriHL:
They won't have a new tablet until this fall. (Well, Moogle, that is...Google will have new nexus tablets before then)
[Xoom Android Development] bigdave240:
That makes so much sense it will never happen LOL. but it would be really great. I think the problem would be that the carriers want to lock the manufacturer to them to get the advantage. can only hope. There is already talk about the Mot X phone with a tablet to follow. very little info but it is 'googleable' if you want to. I am going to wait as well to see what its all about. the xoom still works great for me so no rush.
[Xoom Android Development] bmhanson:
I am in the same boat. I just am not interested in any of the current offerings. Verizon is supposed to be soon getting the Galaxy Note 10.1 but

the release date has not been announced. Not sure if there is an Eos Rom for it or not.
[Xoom Android Development] SamuriHL:
I'm waiting for my bonus from work and then I'll be getting a nexus 10 most likely. Yea, new tablets are coming but I need something before mid-march.
[Xoom Android Development] Asphyx:
Sure because they opened up Nexus for anyone provided they comply with certain guidelines, It's no longer you have to get awarded the Nexus name, you can just meet certain criteria/guidelines that gets you the rights to use it. I like the idea in principle but it is going to lead people to think that Nexus and Android are two seperate products or that Android is gone and all units running android will have the Nexus label. Because nexus will be nothing more than a marketing term at that point. Nexus will become a defacto standard for Android. Every unit will do what it takes to slap the nexus label on thier product.

In Regards to nothing till the fall, yes it won't be released until the Fall in time for the holiday gift season but we will hear something about what it is probably long before then.

Like I said it will come down to how much Grief Google wants to go through dealing with the carriers. It would also require some dealings with someone like Sierra who make the cards that would be used. I have more faith they could get Sierra onboard than someone like Verizon who seems more interested in the software and features than the hardware that it runs on.

It would make a ton of sense, Google could sell WiFi only that could be upgraded to 4G with a card, simplifying the Manufacture proccess that makes producing 3 or 4 types of units expensive. Solve their seeming problem with keeping units in stock (see all the nexus out of stock issues and thats only one unit) and would have a product that could easily be sold, supported and accepted by every carrier.

The only other method that could get that is to develop a universal radio that does everything and I bet that would be a battery pig and ruin the unit performance.

But it all comes down to the issue of do they want to deal with the carriers at all...The Nexus' we have seen seems to say no! AT least on the Tablet side.

The Carriers would prefer to have a device to sell that is useless if you want to switch carriers. So thats going to be the problem I suppose. That and the OS installed which is why everyone is running to Nexus in the first place.
[Xoom Android Development] dccrens:
Verizon has the Samsung Galaxy® Tab 2 (10.1) 8GB. Just not sure that that is what I would go with.

---------- Post added at 07:57 PM ---------- Previous post was at 07:52 PM ----------

Does the Nexus have 4g? I thought it was only WiFI.
[Xoom Android Development] SamuriHL:
Only wifi. I don't see the point of having 4g built in anymore for myself. I'd love to wait for the X tablet. I just got to see a picture of it tonight. OMG that's going to be an awesome toy. I just can't wait that long.

We discussed the whole drop a card in a slot concept before. I was laughed out of the thread. LOL. But I had the same concept....a radio/sim module you could drop in a tablet and give it LTE capability for any network. Would ROCK.
[Xoom Android Development] Asphyx:
They may have laughed Samurai but at some point the Manufacturers are going to have the final say in all of it.

Not the carriers. They can bully thier way right now with the phones because of the subsidies but people are not getting tabs because they are subsidized, they are getting them because they are cheaper than Laptops and do everything they want.

So unless they want to be forced to allow free tethering via the phones or be relegated to selling pucks to make money off those data eating Tablets they will have to come to some agreement on how best to get a manufacturer to support thier radio system.

Either that or standardize LTE across all carrier which has about as much a chance of happening as me getting a 10 Million dollar Tax refund! this year LOL

I think I will wait to see what the nextgen Tablets look like before I give up the Xoom. I have yet to find much of anything other than games the unit can't do well for me.

I have yet to see a Tablet that has all the features my Xoom does and if it weren't for NFC (which seems like not so much a tab fit anyway) I don't see anything to be gained by getting just more proc and GPU.

I would hate to buy a new tablet to take me the next three years only to see the next killer feature came out that makes we want to just scrap the new unit and get the next.
[Xoom Android Development] SamuriHL:
It's a good point. I may have to do some thinking about this new tablet thing. I'd REALLY like a kick ass quad core with lots of memory. Rumor is the new nexus 10 will have all that so we'll see if I can wait that long.
[Xoom Android Development] twinkyz1979:
Well I am not one to wait for things but until i really like another tablet besides my Xoom I will wait no need to get something new while people like Team EOS keep things rolling unless the new thing is a spectacular beast.
[Xoom Android Development] bigdave240:
an actual picture? got a link by any chance? The timing seems right for me to move up to it when it comes out I think.
[Xoom Android Development] SamuriHL:
No, I can't link to it, unfortunately. But it looks like the typical moto styling and is very thin.
[Xoom Android Development] bigdave240:
Nice. The X phone sounds awesome too. Flexible display 1080P, 13MP camera and very long battery life. A picture I saw that claims it is a X phone looks like the case that my standard Razr is in.
[Xoom Android Development] SamuriHL:
The picture of the X phone that was floating around is not the final design. Moogle has some special plans for that phone. It's going to be a beast.
[Xoom Android Development] bigdave240:
even better. I should be ready for a new phone in the next 12 months so looking forward to this. Flexible 1080P displays means no more cracked screens. no need for a bulky case either.
[Xoom Android Development] SamuriHL:
I'm certainly looking forward to Google I/O this year. I think it's going to be an exciting time.
[Xoom Android Development] dboftlp:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Still got the Xoom, rocking the N10 as my daily. Got the media stand back with the Xoom when I sent it for the 4G RMA (thanks Moto), so it's at my bedside as alarm clock, media watcher, nightlies runner & sometimes beta tester. Wish the N10 would bring the peripherals already... Don't miss LTE as much as I thought I would on new the big slab, great device btw, just love it.

Swyped from my GNex running Team EOS 4 nightlies.
[Xoom Android Development] SamuriHL:
You're not helping. :P That's pretty much what I wanna do. Get an NX10 for my daily and move the Xoom to my nightstand.
[Xoom Android Development] bigrushdog:
I'm quite happy with my N7. But I keep hearing more and more N10 chatter. We got the 4.2.2 thing sorted out. Went pretty smooth overall. We should see some Bluetooth improvement. I'll start slapping a N10 build together. Be on the lookout on goo for test builds.
[Xoom Android Development] SamuriHL:
Now you're REALLY making it hard to resist getting an N10!! :D Damnit. :D
[Xoom Android Development] kentedman:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

So does that mean 4.2.2 nightly coming for n7.... and stingray?

Sent from my Nexus 7
[Xoom Android Development] dboftlp:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

this made me put down the N10 again and scratch my head, look down at it and remind myself I didn't have to pay for it, I won & sold an iSlab so it was free, but damn the Xoom just keeps coming back! "go slowly charge in a corner N10 while grown folks talk" (that's me & my Xoom).

---------- Post added at 10:01 PM ---------- Previous post was at 09:47 PM ----------

I'm 6'4" so the N7 is just too small for me.

I bought my wife a Tab 7 Plus, then the next day found an Tab 8.9 refurb + keyboard dock + charging stand + microSD card adapter (stupid proprietary Sammy ports) for $50 more so I bought it and kept the 7 Plus for a few days to play with the form factor. Love the 8.9 form factor btw, it's just too bad that the only other tablet (edit/insert "of note") in that size is from Amazon... Anyway, couldn't do it, way too small, even for her she liked the 8.9 better. Not much dev support, but she's not a "holic" like me.

& for the record, my N10 is stock/rooted & will be until there's an EOS build. #nopressure :P
[Xoom Android Development] bigrushdog:
Yes. Next nightly.
[Xoom Android Development] rlmesq:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I'm having a strange issue: white message light is constantly glowing unless device is completely powered off. I've wiped cache & Dalvik, and reinstalled 171.

Could it be liquid damage?
[Xoom Android Development] bigdave240:
Did you take it for a swim? Does it vo out if you go to settings, display and uncheck notifications? I leave mine unchecked since there is other ways to see things like email etc and i always figure an extra lite blinking drains the battery that much faster
[Xoom Android Development] rlmesq:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I spilled the dregs of a glass of wine that was on my hotel nightstand on it sometime during the night.

Tried turning off notifications, but it still glows constantly.
[Xoom Android Development] bigdave240:
I suppose anything is possible but i would be surprised if it would only turn on the lite. Give it a couple of days to dry maybe. Notbing else affected? Possibly a misbehaving app?
[Xoom Android Development] rlmesq:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I don't think it's a misbehaving app. The LED comes on as soon as the device powers up, before the splash screen even appears. It only goes out when the Xoom is completely powered down.
[Xoom Android Development] bigdave240:
just to clarify, we are talking about the light in the upper right corner right?
[Xoom Android Development] shpitz461:
That sounds like the spillage created a short causing the light to stay on. Either wait for the light to burn off, or maybe put a dark tape on top of it.
[Xoom Android Development] Asphyx:
I agree!

Other than opening up the unit giving it a careful cleaning to get rid of any residue (disconnect battery first and don't use water try Isopropyl alcohol on a cloth not the board). There is no other way to fix that....

The problem is if it is shorting out the contacts on the LED what else is is shorting out and burning up?

If you go the cleaning route make sure to wait a day before you reconnect the battery and ensure everything is totally dry first.

As a rule when you get liquid spilled you should try and disconnect the battery and throw it in a bag of rice (or Silicas gel if you have those around) and wait a few days before giving it power again. But the wine has other particulates in it that could cause shorts and the only way to fix it is to give it a bath and hope it's just a surface short and not something that got inside some component.
[Xoom Android Development] bigdave240:
the engineer in me has to ask these questions ;>) How much wine was spilled and what area on the xoom was it spilled on? There doesn't seem to be much open areas that could allow a small spill to ingress the unit. A short of the leads on an led would keep it turned off not on so that doesn't make sense to me. i do agree with the fact that if it is a short keeping the led on then there would most likely be other issues as well. the connection points on these boards is micro in size (though I havent disasembled the xoom itself so can only guess it is all surface mount technology) so something shorting out would short out a lot more than just one led. very interesting issues. Hope you get it figured out soon.
[Xoom Android Development] Asphyx:
Well it is pretty tight of a seal but remember...

In the area of the LED is also the holes for the right speaker and thats probably the most likely place liquid could seep in....

The Camera is also same daughtercard that is part of that back top piece and it wouldn't surprise me to see the controls for the LED FLASH be shared with the side Notif LED he is having an issue with..

And just to be clear regarding my previous post...

I'm not even sure the battery in the Xoom is easily disconnected...I have only opened it two or three times (just to look) and never really inspected the battery connections. But any cleaning should be done devoid of any power source whenever possible.

And the entire proccess is not suggested for anyone who has never seen a ribbon cable or PC Breadboard in thier life. LOL
[Xoom Android Development] bigdave240:
Agree with that! I work on this stuf quite often and still manage to screw up a ribbon cable on occasion.
[Xoom Android Development] Asphyx:
Yep and it's why when people ask me if I can fix thier laptop I usually say not worth the effort...

Way too fragile, never seat as good as they did when the factory seated them and most of them are in positions that is more conducive to playing a game of Twister than it is to assembling a computer! LOL

they are great for using in tight spaces where Wires don't work but they are a PITA! LOL
[Xoom Android Development] Asphyx:
Hey Samurai....

Looks like Qualcomm has the answer...LOL

http://www.androidpolice.com/2013/0...-radio-that-plays-nice-with-all-the-networks/

This looks promising!
[Xoom Android Development] SamuriHL:
Indeed it does! Now that's how we do it!!
[Xoom Android Development] bigdave240:
Nice find. Now we just need to get motorola to buils something into the X tablet that can use it.
[Xoom Android Development] shpitz461:
Flahsed 172 and gapps from OP, got to the inital setup screen and getting constant UI fc's that will come back right after I hit OK.

Anyone else?

Is it 4.2.2? is anything kernel wise missing?

Here's logcat: 172_stingray_ui_fc

Formatted system

wiped factory, wiped cache, wiped dalvik

flashed rom then gapps using TWRP 2.4.1.0
[Xoom Android Development] grncherry:
Exactly the same happening to me.
[Xoom Android Development] shpitz461:
Yeah, so I flashed cm10.1 2/21 and no fc's yet.
[Xoom Android Development] bigrushdog:
Ok I read that logcat and it is most peculiar indeed. It's a null pointer pertaining to the quick settings mobile signal tile. Yet, other telephony devices are fine. Weird indeed. I'll check the code and see what jumps out at me. I sure wish I had a Xoom maintainer :'(

I'll try and post some possible fixes. If I get a confirmed fix I'll fire off another round. Sorry about this guy's. Hang in there.
[Xoom Android Development] shpitz461:
No biggie, thanks for the quick response!

CM10.1 is very smooth, hope EOS feels the same :)
[Xoom Android Development] bigrushdog:
Of course cm is smooth! It's cyanogenmod! They are and forever will be the greatest. We do this for fun, and because we enjoy programming. Not to compete. Usually. Well, when i do want to compete, it's not against cyanogenmod lol.

That being said, here's round 1.

Download systemui trial fix 1

Guys please report back asap so i can move to the next step. btw I dead beat dog tired so do hurry please.
[Xoom Android Development] shpitz461:
Downloading now... saw this right after finished up setting CM10.1 lol

Go to sleep! this can wait to tomorrow!

EDIT: OK, flasing rom, gapps, fix.
[Xoom Android Development] bigrushdog:
nah, I gotta clean this up. I already found the real wonk. That zip is a temp fix most likely. But i'm getting another one lined up just in case. I don't have a stingray maintainer at the moment. I fear I may have to suspend stingray and umts builds until i get a maintainer.

EDIT: and either way flash round 2

download fix round 2

this is a better cleaner fix. it seems when i merged, it kept an old device telephony check in there that has since been updated. so it worked fine on phones because they have voice and data. But it was having issues with stingray as it is data only without voice.
[Xoom Android Development] shpitz461:
Error flashing fix.zip, using TWRP 2.4.1.0

'can't make /tmp/update_binary

Pinged you on IRC, 'zz_bigrushdog'
[Xoom Android Development] bigrushdog:
UGH. ok try round 2 ^^^^
[Xoom Android Development] bigrushdog:
even if it borks, just try adb pushing to /system/app and rebooting
[Xoom Android Development] shpitz461:
Here's logcat with fix2, no dice :(

Added picture.
[Xoom Android Development] ifsrob88:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I am also receiving the fc UI as well.

---------- Post added at 11:20 PM ---------- Previous post was at 11:11 PM ----------

Round 2 fixed worked for me. I simply re flashed 172 the fix round 2 right afterwards... Then reboot. Hope that helps.
[Xoom Android Development] shpitz461:
where you coming from EOS?

I came from CM10.1 and fix2 didn't work. BRD did some magic and now it works for me. He'll probably re-release a build.
[Xoom Android Development] bigrushdog:
Ya we found the derp. I'm double checking the fix then a fresh build for stringray and everest will go out immediately after i confirm the fix.
[Xoom Android Development] grncherry:
Nandroided back to 171 after flashing 172 the first time with UI fc's. Reflashed 172 with second fix and gapps and now running with no problems. Thanks for your hard work.
[Xoom Android Development] dweezle:
Someone here must have a loaner Xoom for BRD. For all the work he puts in to keep us afloat, he deserves some help. Mine is my daily driver or I'd consider it.
[Xoom Android Development] grncherry:
I'm in the same situation. There are other nice tabs out there but nothing competes with my Xoom. I refuse to purchase anything without expandable memory, seems most are made without sdcard slots for some inexplicable reason.
[Xoom Android Development] bigdave240:
brd, I can test things for you if that will help. I am usually available on short notice since I work from home and am always on here it seems. Not sure if that helps you but i am always willing to do nandroids and upgrades. I have never had a problem rolling back with a nandroid so I am not too worried about breaking something.
[Xoom Android Development] dccrens:
Why don't all of us who rely on EOS on Xoom take up a collection and buy a xoom for Bigrushdog so we can continue to get EOS goodness??? I will pony up. Anyone else? What is a xoom going about $200 to $250?
[Xoom Android Development] bigdave240:
sounds good but i wonder if he would need a data plan to go with it?
[Xoom Android Development] Asphyx:
I doubt it makes it into the next Moto Tablet....

The Board design has probably been set and locked for awhile now. This sounds a little too new to make it this year anyway.

But you never know...I would happily stick with my Xoom a little longer if they had to delay the X a bit to incorporate the new chipset.
[Xoom Android Development] quordandis:
Hey, this ROM is amazing! Thanks for all the hard work. I just flashed build 173 over 171, wiped cache/dalvik both before and after flashing zip. Device loads up ok, but Google Now doesn't show cards at all, and Play Store won't load. Cleared defaults, cache data on Play Store. Still nuthin. Anyone?
[Xoom Android Development] bigdave240:
did you reload the correct gapps? not sure you need to wipe cache after, i have never done that.
[Xoom Android Development] quordandis:
I have to reflash gapps after flashing new build? Or is there a new one I should flash after I flash 173?
[Xoom Android Development] bigrushdog:
N10 guys, let's look forward together :D
[Xoom Android Development] SamuriHL:
If my bonus ever comes I'm right there with you on that one.