yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bigdave240:
well, right or wrong I always wipe the caches, flash the rom then flash the gapps. the lates gapps is on the first page of this thread. always works for me. I have cards on google. now, that said, it is telling me that there is an upgrade but don't download it cause it won't work with this rom without a work around unless they fixed it when i wasn't looking.
[Xoom Android Development] bigrushdog:
Still down and out on the upgrade. I'd consider using tb to remove the market link.
[Xoom Android Development] bigdave240:
i just ignore it.
[Xoom Android Development] Asphyx:
I Only wipe cache between different Android versions....Like from 4.1 - 4.2

But the system actually rebuilds the cache on first boot when upgrading...

I have found that you should flash GApps after every upgrade though...

Since I switched to TWRP it's easy since it lets you select both zips and let it go.

I hate wiping Dalvick and only do it when all else fails....

Every time to wipe it I get all this extra crap apps I have long since deleted and don't use get re-downloaded.

I'm sure there is a way to stop that I'm missing but thats mostly because I'm a lazy bastard in general! LOL
[Xoom Android Development] Vnvjeep:
lockscreen widgets

I'm using a pin password for my lockscreen and wanted to replace the default clock widget with the dashclock widget from the market. I noticed in the EOS settings that I can add all Widgets to be selected to the lockscreen. Thing is, I'm not seeing how you can add them? There's no interface to add when you're on the lockscreen... I can remove the default clock, but it comes back. Can someone please give me a hint? As always, much appreciated! ;)
[Xoom Android Development] Asphyx:
Well swipe over the default clock (L-R) and you should see a space for a widget that has a plus sign....

Press the plus sign and add your widget.

Then remove the old one...

(You can actually remove it before and you should see the plus sign after it's gone.)
[Xoom Android Development] kentedman:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Actually. I don't think it works with pin or password lock. I've had lots if people tell me it should work, but I could never get it to work. Piece of cake on swipe to unlock but no luck on pin.

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

What if u turn pin lock off turn swipe lock on. Setup your widgets, then turn your pon lock back on...

Edit:

Work on my phone (toro eos'ed)
[Xoom Android Development] ifsrob88:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Yes

---------- Post added at 06:58 AM ---------- Previous post was at 06:55 AM ----------

Yes I did come from EOS
[Xoom Android Development] Asphyx:
Hmmm I wonder if he set up the widget under slide lock it would persist after switching back to pin lock.

I prefer to protect my Tab by never letting it out of my sight! LOL

Sorry run didn't see you suggest that already....LOL
[Xoom Android Development] brittoking:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Hey guys and gals need a little help. Been out of the flashing game for about a month now left off on nightly 162 with no lte or data working. My quick question is does flashing 173 resolve that old data prob, or is there author step I'm not seeing in the op or thread to enable my data connection again? Thank you in advance for the help.

If I happen to be of help to you, please hit THANKS, as I have low self-esteem and crave validation! Running TEAM EOS ICS
[Xoom Android Development] bigdave240:
follow the instructions in the first post about using the correct gapps and the right recovery. I use the latest twrp which works very well. do a nandroid so you could go back if you had to. you might even want to do a clean install just to get it all cleaned up when you start. I hadn't done that in a while and it seemed to be better than just doing update over old but thats just me.
[Xoom Android Development] Asphyx:
First off what version did you come from when you lost your Data?

There was a Radio flash that was required sometime during the ICS Development before you could move past a certain Version (I forget the actual version number I believe it was in the 120's though).

That could be one cause of loss of data.

If you did that and know it was done (you only needed to do it once) then follow Dave's instructions
[Xoom Android Development] bigdave240:
i was thinking that 162 was the firs4.2 where data didnt work? Then it got fixed in a later release?
[Xoom Android Development] Asphyx:
I'm talking about the radio flash that was required long before 150 even came out....I don't remember which of the 4.2 versions had or didn't have radio when it first came out but just wanted to be sure he didn't come from EOS2 Stable which requires a Radio flash before you can run the newer versions of Jellybean....

Just in case....

You explanation (upgrade to latest) is probably what he needs to fix I was just being thorough in case it didn't work.
[Xoom Android Development] brittoking:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I've been running every nightly since they started way back when. I did the radio flash long ago, I just lost data (along with everyone else) on 162(I believe it was?). Then got really busy with a new baby, New job, etc etc so I haven't been tracking the thread religiously like before but was wanting to jump back in to see when it got fixed or how. Flashed 173 with new gaaps this am and its running great but I kinda forgot that...well...I hadn't paid my Verizon bill in awhile too, so I can't vcheck if data is working! Lol guess I'll have to wait till next week to see on payday. thanks

for the quick support guys!

If I happen to be of help to you, please hit THANKS, as I have low self-esteem and crave validation! Running TEAM EOS ICS
[Xoom Android Development] grncherry:
http://goo.im/devs/teameos/radios/imm76l-radios-update.zip

Hope this helps, I think this is the proper one from months ago.
[Xoom Android Development] brittoking:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Yea I flashed that months back, as I said above I was flashing regularly until about a month ago, and that happened to be when data got broken on a couple builds

If I happen to be of help to you, please hit THANKS, as I have low self-esteem and crave validation! Running TEAM EOS
[Xoom Android Development] ShinySideUpAZ:
Speech to Text Keyboard

Can anyone validate for me that they also are missing Speech to Text in nightly 173? Flashed back to 171 and it returned. Flashed to 173, Gone.
[Xoom Android Development] grncherry:
I can verify that it is gone from mine as well.
[Xoom Android Development] ShinySideUpAZ:
Does anyone have any suggestions on how to add the capability backinto a nightly 173 system?
[Xoom Android Development] Vnvjeep:
Well, Frak. I have a device administrator that forces pin or password and can't disable it to try this out, unless I start wiping out my exchange accounts. Sounds like it would work though. Great suggestion...
[Xoom Android Development] Mjamocha:
Just poking my head in to see whats good, as I haven't made the leap to 4.2 yet :o
[Xoom Android Development] bigrushdog:
Well get to leaping! And you should be backing up runandhide maintaining the xoom too!
[Xoom Android Development] Asphyx:
Sorry to confuse everyone with my post....

I was just trying to be thorough as the poster stated they had not flashed in awhile....

Awhile could have been a very long time! LOL

I did not ever experience an outage of Data problem when I flash because I only flash the latest and only after checking the threads to see if there are any bugs a few days after it is released before I D/L and Flash....

So Apologies for starting a pile of crap that wasn't neccesary! LOL
[Xoom Android Development] bigdave240:
wouldnt worry bout it. It could have been a multitude of reasons why no data so its always good to get multiple answers! I am usually pretty hesitant about answering here being a noob! (only been messing with these roms for a year or so)
[Xoom Android Development] Mjamocha:
lol, good job fellers. I can wait until 5.0 comes out. (fingers crossed)

My current 4.1.2 does everything I currently need.
[Xoom Android Development] thehotboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

I apologize in advance if this has been asked in here already but i see no mention of it in the past few threads. My contract for my Xoom ended and I decided to stop using 4G .. would I be better off flashing the Wingray Roms since I will only be using WiFi from now on or it doesn't matter? thanks.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Xoom Android Development] bigdave240:
word i got when asking that was that if you flash the wingray rom it will make your battery life short. so it was advised to keep flashing the stingray rom.
[Xoom Android Development] Asphyx:
NO!

Stick with the Rom specific to your unit which in the 4G case is Stingray!

You probably could get it to work but there is no need to at this point since Stingray is up to date with Wingray as far as Andoid version is concerned.

In fact the only thing that has changed since your contract ran out is you no longer have to go into Airplane mode to save Data charges! LOL
[Xoom Android Development] bigdave240:
that little exchange is the most excitement around here in a while now LOL. wonder if there is any new 'goodness' coming? Couldn't imagine what but these guys always seem to have something awesome to show us. got to be reaching the eol on this thing though at some point. waiting to see what the motorola X tablet offers
[Xoom Android Development] bigrushdog:
Fresh builds tomorrow. Should see a manta build pop up on goo in a few hours. We got a killer new feature called Glass. Brought in some Linaro optimizations. So ya we got some goodness coming.
[Xoom Android Development] bigdave240:
sweet! doing nandroid now before I go to bed. working nights for a couple of weeks.
[Xoom Android Development] Asphyx:
Well I knew you would have something up your sleeve! LOL

I wouldn't say the Xoom is EOL just yet but I do think 4.2 is probably the last Android Version we will ever see...(Saying this will just inspire BRD and Team EOS to give us Android 5.0 just to prove us wrong! LOL)

Not bad considering the Xoom is essentially the Android Tablet prototype and very first Android Tablet ever released!

Just goes to show that if you want long life and ability to stay current with Android Versioning, an Unlocked Bootloader is just as good as Nexus!
[Xoom Android Development] SamuriHL:
You got that right. I will never buy a non-unlockable device again.
[Xoom Android Development] Asphyx:
Just be sure to do your homework because unlockable is not a constant as far as the manufacturers go...

HTC unlocked but it was no where near the unlockable a Nexus or Xoom was....

It really all comes down to the kernel accessability....

If you can flash a Kernel then it's possible to get the next version to work without an Official OTA in most cases.

Carrier specific units are more difficult than the nexus in that regard but if you control the Kernal you pretty much control the entire device.
[Xoom Android Development] bigdave240:
I read somewhere that the motorola X will be unlockable but that Verizon will charge a monthly fee if you want to do it. But it will be available from other carriers as well who may not charge anything. should be interesting.
[Xoom Android Development] Asphyx:
Not sure if that just means they will charge you an extra fee for a developer edition unit compared to thier standard locked version....

I don't see how thier system could tell one way or the other once it has been unlocked...

I mean they can't even catch the tetherers without just making an assumption of data usage compared to the average...

They also say they won't support any OS but stock yet I don't know a sole who has a stock Xoom running on thier network! LOL

Just activate it while it is still locked and then unlock it after the account has been opened...

I doubt they would ever know.
[Xoom Android Development] SamuriHL:
I always do my homework, believe me. :) I'm quite sure the X phone or whatever the hell it's going to be called in the real world is NOT going to be unlockable on VZW. It will be on the other 3 carriers. Tablets....I'm not going with a carrier branded tablet again so that will be less of an issue.

---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------

That charging for unlock crap was a rumor. And not something I believe. I'd ignore that. I know exactly where that rumor came from and the person who originally posted it said it was NOT a sure thing and something VZW was only considering. They're not going to allow an unlocked phone on their network if they can help it.
[Xoom Android Development] bigrushdog:
Alpharev can unlock nearly anything. Kernel source is a absolute must. But that's just the beginning if you have a device with proprietary technology, ie evo 3d or note 2. Fresh shiny manta (n10) build on goo. Have fun.
[Xoom Android Development] rob62551:
Glass is Class!

Thanks Team EOS! Glass is a great addition to EOS Control Center. Liking my system bars at full transparency!

Update : Read posts about folks having issues with setting wallpaper and I noticed that I have no problem using NOVA launcer aside from losing navigation bar transparency if I chose a live wallpaper. Switched to stock launcher and have the same issues as others. Can't set any wallpapers and get a black background.

As I prefer and use NOVA, I still like this new feature. Bet BRD will.smooth this out! So far everything else is going well.with new build. Thanks Team EOS.
[Xoom Android Development] bigdave240:
Actually if you set the sliders all the way up (to the right) you can see your wallpaper on the toolbar at the bottlm but not on the top. The whole screen is black excpt for the bottom toolbar
[Xoom Android Development] bigrushdog:
Ugh. It always works fine in the laboratory. Ok somebody put up a few screens, portrait and landscape, so I can get a feel for the wonk.
[Xoom Android Development] bigrushdog:
Yes. I commented on live walls and dreams in the change log. It on the to do list.
[Xoom Android Development] bigdave240:
See post #315 for pics
[Xoom Android Development] bigrushdog:
Wow ya that's weird. Is that with glass enabled or disabled or both?
[Xoom Android Development] bigdave240:
enabled. on both. if i disable it then the bar becomes the color of what is chosen so you can't see the wallpaper through it.
[Xoom Android Development] bigrushdog:
Darn. That's how it should look with stock launcher and launcher presets. Ok I'll dig in the launcher xml and see what I missed. Hang in there. See if live walls work on stock launcher.
[Xoom Android Development] bigdave240:
doesn't seem to work with live either. sorry. glass is pretty cool though
[Xoom Android Development] bigrushdog:
Its cooler when wallpaper actually shows in launcher lol. Should have a fix soon. You can use a Launcher2.apk from an older build to get by.
[Xoom Android Development] bigdave240:
no worries. looks sort of cool all black.
[Xoom Android Development] bigrushdog:
Ok guys fix trial round 1

Download

download and drop in /system/app and reboot

I'm not in the mood to make zips so deal :laugh:
[Xoom Android Development] shpitz461:
No need for ZIPs, i kinda like using fastboot and adb :)

Fix looks good to me.
[Xoom Android Development] bigrushdog:
Fix double confirmed. merged and fresh builds going out.
[Xoom Android Development] bigdave240:
Fixed!
[Xoom Android Development] tselling:
I don't see a zoom vs stretch option for apps that aren't meant fot the tablet's large display. Did that go away with 4.2? Some of my son's math games need that so they aren't too small.
[Xoom Android Development] ShinySideUpAZ:
Speech to text still missing?

Can anyone else confirm that Speech To Text Still missing. I am seeing this, but I don't want to assume it is the ROM and not me.
[Xoom Android Development] red911turbo:
Has anyone got Dashclock to work correctly? I can set up the widget but as soon as i tap on it, it minimizes and highlights the unlock circle.
[Xoom Android Development] jlvlawrence:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Really liking the glass settings.
[Xoom Android Development] tselling:
I loaded CM10 stable on my Xoom to get this feature back. Please let me know if anyone finds out if this can be enabled on 4.2. Thanks.
[Xoom Android Development] Asphyx:
LOL Samuri - Your advanced status on these things is well recognized...That was mostly for the rest!

You can't really operate any controls in a Widget from the Lockscreen AFAIK...I know other widgets I have used do not allow hotspots to work. You probably have to unlock and load the Dashclock app to change any settings for it.
[Xoom Android Development] webeougher:
Haven't seen this mentioned anywhere, and I searched this thread, but when I flashed Version 173 from 2/21, everything runs perfectly. With 174 and 175 (from 3/5 and 3/6, respectively), though, I flashed and wiped cache and dalvik cache, but when the ROM boots, I can't access my Google account, so GApps just close with no force close error or anything. I can't even add a Google account from the Accounts settings menu. I tried a full wipe and clean install with both 174 and 175, but I keep getting an error that my data can't be activated, in spite of having constant 3 bars of 4G. Again, I apologize if this has been addressed elsewhere, but I had no luck locating any information. I swear this isn't my first time - I've been flashing since 2009 (on my Samsung Omnia) and flashing Android ROMs since early 2010 (OG Droid).
[Xoom Android Development] Asphyx:
Did you flash the gapps when you flashed the ROM?

Also if your gonna wipe cache and Dalvick might as well go to factory as well and get a truly fresh start.
[Xoom Android Development] webeougher:
I tried both ways - flashed just the rom, rebooted, and flashed the GApps, and also tried flashing them both in the same recovery session. No luck either way. And, as I said, clean installs of 174 or 175 kept giving me errors that I couldn't activate mobile data, in spite of having 3 bars of 4G. I travel quite a bit and can't count on strictly wifi, so that's a dealbreaker for me.

Thank you for the suggestions, though - I appreciate any and all attempts at assistance.
[Xoom Android Development] shpitz461:
ROM & GAPPS always come in pairs... you have to flash GAPPS immediately after ROM, no reboots in between.

If you go back to 173 problem is solved? did you try that?
[Xoom Android Development] webeougher:
I realize that you aren't supposed to reboot before installing GApps but since the standard method wasn't working for me, I was trying alternate options to see if I could make it work.

And yes, everything works fine on 173, but the goomanager notification periodically popping up to remind me that an update was available for my ROM was rather irritating. As of today, I'm on 175 and everything is working correctly (except for Google Now). I did a full wipe, installed 173 and GApps, went through the setup process, let all of my apps reinstall from the market, rebooted, let it sit overnight, rebooted into recovery this morning, installed 175, wiped cache and dalvik, installed GApps, and rebooted. For whatever reason, it worked today, when the exact same process failed both Friday and yesterday. All's well that ends well, I suppose.

As for Google Now, as long as i use the version in the GApps, I have no issues. But if I install any updated versions from the Play Store, whenever I open it or try to perform a search from the search bar, it opens to a white screen or else partially loads the header image and then closes with no force close message. I havent had time to search the thread to see if this is expected, but I wanted to point it out. It's only a minor inconvenience until college football season starts.
[Xoom Android Development] shpitz461:
Did you try to clear the cache for Google Now? In settings->Apps
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Disable hot word detection...same thing we have been saying for months.

Settings》language and inputs》 voice search 》》 uncheck hot word detection
[Xoom Android Development] bigdave240:
The issue with google now is a known issue. There is a workaround but i just dont take the update and it wirks fine. This happened before and eventually the devs got it fixed but do a search for the workaround as i forget it right now.
[Xoom Android Development] Liwais:
today

The file you requested was not found

Lets see if we can find that for you...

Search results for devs/teameos/roms/eos4/nightlies/stingray:crying:
[Xoom Android Development] bigdave240:
Nice! server messed up I hope

Lists of devs is slowly coming back. must have been doing maintenance maybe
[Xoom Android Development] shpitz461:
When I record a video and press the screen, it freezes than FC's. Upon restarting the app it says camera is unavailable and quits, after another app restart it's back working. Every time I press the screen while recording a video it FC's.

Anyone else?

I've attached a log.
[Xoom Android Development] webeougher:
Just wanted to say thank you to everyone who offered assistance. Everything is now up-to-date and working perfectly (at least everything that I use on a regular basis, which is good enough for me).
[Xoom Android Development] EvilDobe:
Try installing TalkBack from the market. That should solve your issue.
[Xoom Android Development] Mjamocha:
Keep up the great work boys! We appreciate it.
[Xoom Android Development] REHolt218:
I see there is a new Stingray Nightly:fingers-crossed: but none of the links work:crying: not even the mirror site. Where can a guy get a fix around here:confused:

Edit: Duh, try the first post, it has a link that works. Why didn't I think of that?
[Xoom Android Development] bigdave240:
Not sure i can test this absolutely but the 176 release seems to load web pages much faster? And seems a bit snapier overall? Will run an antutu in a bit
[Xoom Android Development] bigdave240:
Antutu seemed to be about the same as before but havent had one single crash or had to empty browser cache at all. This version is so extremely stable. I read through the list of changes and dont understand most of them but its a long list. You guys did something better this time cor sure. Nice build
[Xoom Android Development] cydetrakd:
I will have to agree with bigdave on this one fast and stable just curious what was taken out to make the latest jb run on our Xooms? I know the keyboard features that i dearly miss with the auto prediction which i hope can be brought back since i also miss the auti correction features. Other than that what was taken out just out of curiosity?
[Xoom Android Development] jbelew:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Since going to 176, my wi-fi connection has no Internet connectivity after I wake my Xoom up. The wi-fi icon is gray, not blue, and I can't get to anything outside of my network. I have to toggle wi-fi off and back on or otherwise reconnect to the network. Anyone else having similar trouble?

Other than that, I agree that 176 is running great!
[Xoom Android Development] shpitz461:
Never happened to me, try to reflash rom and gapps again and see if that helps.
[Xoom Android Development] jbelew:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Stingray / MZ602 / VZW 4

Well, I deleted the network and re-added it. So far, it hasn't happened again. Strange. Thanks for the response and I will give it a shot if I see it again.
[Xoom Android Development] Mjamocha:
I'm just lurkin, checking the scene!
[Xoom Android Development] bigrushdog:
I dropped Row scheduler and sweep2wake in the kernel. Can you test and see if they work?