yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] kentedman:
That's what I love about android and these communities. Great developers like Bigrushdog, TDR and Dreamcwli who are all on different teams but all working together for the common good. Thanks to all your hard work, our 2 year old tablets are not only still relevant but continue to stay on the leading edge. Amazing work! Thank you!
[Xoom Android Development] SamuriHL:
So does that mean that 159 will have full working LTE?
[Xoom Android Development] REHolt218:
That's great news!! I was hoping for your sake that you would be the first one to get it, I have always thought the EOS Team was the best. But at least we can now count on 4g.
[Xoom Android Development] Mjamocha:
Wowserz, 4.2 with LTE! Awesome work fellas.
[Xoom Android Development] kentedman:
Fresh install of 159. Sadly still no LTE.
[Xoom Android Development] johnny0911:
It will come just give them some time :laugh:
[Xoom Android Development] SamuriHL:
That's why I was asking if that code had made it into 159...it didn't sound for sure like that code was in it. So, we'll wait. No big deal.
[Xoom Android Development] REHolt218:
Where did you get 159? I have not been able to access it all day.
[Xoom Android Development] kentedman:
http://mirror1.teameos.org/roms/eos4/nightlies/stingray

And BTW. I wasn't complaining about no 4G, I was just informing.
[Xoom Android Development] runandhide05:
Just updated gapps, got google now working with latest update,

enjoy

http://xdaforums.com/showpost.php?p=36152887&postcount=821
[Xoom Android Development] REHolt218:
Based on the news about lte this one is already OBE, but thanks for the link anyway.
[Xoom Android Development] EvilDobe:
Very exciting times! LTE working.. pending 160 build on jenkins... I may have to bring my tablet to work and get some monkeying around done.
[Xoom Android Development] bigrushdog:
Consider it a test build. It should work but I don't know as I can't test. Also if it does work I won't open a thread until the Rogue guys say it's cool. I'm just testing since as of yet I haven't even got radios to work.
[Xoom Android Development] REHolt218:
160 is better, I no longer get the "phone.app" error, but it still does not initialize 3g/4g.
[Xoom Android Development] johnny0911:
Is deep sleep working on160? It was working off and on as of 158.
[Xoom Android Development] REHolt218:
Not sure yet since I have been using my Xoom continuously since I installed 160. I will say that my battery performance on 158 and 159 have been the best I have ever seen; although, I assumed that was because the radio was not on/working.
[Xoom Android Development] EvilDobe:
What happened to TDR and the Rogue team? I shouldn't be asking here but I figured since BRD knows this would be the quickest, and least painless, to get an answer.
[Xoom Android Development] bigrushdog:
They have a huge collaboration post on g+. They're not opening threads yet but find them they got test builds posted. 4.2 is so wonky on xoom I'm not taking anything personal this time around lol.
[Xoom Android Development] bigdave240:
No 3g/4g on 160. Still dont see a full min or mdm number, only last 4 digits
[Xoom Android Development] tomcrown1:
If 4g works I think we would see a new thread titled team EOS 4 stingray and bulid maybe #1.
[Xoom Android Development] Mjamocha:
Lol, be patient man. I think Dev said he's borrowed the xoom back so pretty sure what's being reported, he already knows.

True, TCrown - once a working Radio is implemented the Dev Masters will let us know.
[Xoom Android Development] dweezle:
This is what makes our community impressive. Folks who won't give up until they get a piece to work and those willing to test out the "imperfect" builds. It's a priveledge just to watch it come together.
[Xoom Android Development] bigdave240:
Yeah. I have been following but it seemed like in post 2248 hr was looking to see if what they did in rev 160 might have fixed it. I am almost to the point of not caring anymore though. With verizon allowing tethering it would save me $10 a month to end the data service and just go wifi. Loving this 4.2 though!
[Xoom Android Development] johnny0911:
I agree!
[Xoom Android Development] bigrushdog:
OK guys, here we go. The nightly cooking right now should bring everything online. There will still likely be some kinks to work out, but we'll get to all that later.

First and foremost, I take ZERO CREDIT for getting lte going. First, credit and love must go to CyanogenMod. Their legacy ril support is ultimately at the core of bringing lte back to xoom. They are the kings of AOSP internal systems and the AOSP community and Eos would not be where it is today without them.

Next, TDR of Team Rogue figured out the proprietary apk smali hacks to get those apks to play nice with the new telephony framework. He also came up with the build.prop values to get things going smooth.

I'm trying to find something i can take credit for here. But i'm coming up short lol.

Lemme know how it goes.
[Xoom Android Development] bigdave240:
Not to worry BRD! You have plenty to take credit for by being a huge part of this total community. You guys are all awesome and we wouldn't be where we are without all of you devs. It gets better each time you guys do a release
[Xoom Android Development] REHolt218:
What he said, with a huge thanks to the whole EOS Team.

Just loaded 161. 3g/4g now appears to connect as long as wifi is also on (the icon turns blue). However, when I turn wifi off the 3g/4g icon turns grey and I have no connection.

Edit: skip that... I went in and set the preferred network mode to LTE/CDMA and I am now up and running on 4g. This is great!!! Thanks!!!
[Xoom Android Development] bigrushdog:
Go into mobile data setting and change the cdma subscription value from nv to ruim. Or whatever it is. Play with those mobile data settings some.
[Xoom Android Development] REHolt218:
Thanks BRD. It was already set to ruim/sim but there was no network mode selected. Choosing LTE/CDMA did the trick.
[Xoom Android Development] bigdave240:
Mine was set to nv and also had to select lte cdma to get it working but it seems to be just fine. Did some reading on the ruim and nv settings and think we should be on ruim for verizon? Seems to work on either though
[Xoom Android Development] Lobout:
Flashed from stable 3.0

So I flashed 161 from stable build 3.0 and flashed the xoom gapps. I get 4g data connection but am stuck on activation. if i flash without gapps i work fine with 3g/4g and wifi working fine(just no apps). Is there a way to bypass the activation of gapps?

EDIT: It eventually timed out and let me skip the activation.
[Xoom Android Development] EvilDobe:
You were the first one to run the build bot for team EOS and brought us a working stingray build. BOOM! Credit given.
[Xoom Android Development] EtchG:
Do we need to run the radio driver zip before installing the 4.2 rom, or does it contain everything needed now?
[Xoom Android Development] paris1129:
AWESOME!! I've been waiting for LTE to work before giving this a try. I am playing with it now. Is there a way to move the home buttons back to the bottom left corner in landscape mode instead of centered?
[Xoom Android Development] Lobout:
Radio is included in the build no need to run it as a separate install.
[Xoom Android Development] EtchG:
Awesome. Thanks. :)
[Xoom Android Development] bigrushdog:
Ummm no. Incorrect. We never include radios in builds.
[Xoom Android Development] EtchG:
I will continue to run the radio install before the rom then.

Do I need to do a factory reset before installing the updated rom or can it be installed over the top without issue?

I have installed a few of the 4.2 updated roms, but haven't done a factory reset before any of them.
[Xoom Android Development] bigrushdog:
If your coming from a 4.2 build you shouldn't need a wipe.
[Xoom Android Development] Lobout:
let me reprhase. you shouldn't need to install the radio as it should already be there.
[Xoom Android Development] EvilDobe:
There is an option in EOS settings for "traditional" nav bar. I don't remember the exact terminology used but when you see it you'll know it.
[Xoom Android Development] paris1129:
This is pretty awesome. However it is running pretty sluggish on my

Xoom. I did a flash over Eos nightly 150. Is anyone else having some pretty severe lag on this rom?
[Xoom Android Development] Lobout:
I'm not seeing anything that i would call severe lag. there may be a slight lag, but not much that I can see yet.
[Xoom Android Development] REHolt218:
Mine seems to be running smoothly, nothing that I would call significant lag.

---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------

Are you sure you got the latest Xoom GPS file?
[Xoom Android Development] Lobout:
I assume that it is included in the build. I will have to check and see what version it is.
[Xoom Android Development] bigrushdog:
Activation is a known issue. It's being researched. By someone. Hopefully.
[Xoom Android Development] Lobout:
ahhhh so it isn't just me then. Good to know. keep up the great work.:laugh:
[Xoom Android Development] kentedman:
Here's the deal (so far)... TDR has been playing with this for a few days on the CM 10.1 g+ thread.

on first boot the Xoom will try to activate but eventually fail/time-out. (be patient) hit Skip or Cancel. complete set-up without activating. At this point the 4G should be working anyway, but your device is not "Activated" (whatever that really means). in the status tab it should show Verizon, but it will still only have the partial 4-digit MDN/MIN. Go into data settings and network, and change the subscription type from NV to RUIM/SIM. (some are reporting you also need to change the connection type from CDMA to LTE, but mine was already correct). Your connection will drop and then after 2-3 minutes (be patient again) then the 4G will come back. Now if you look in the status your correct MDN/MIN should be displayed and you are now officially activated.

TDR has thrown out a few CM trial builds trying to get the defaults switched over so we dont have to change anything manually but until then this works.
[Xoom Android Development] thehotboy:
wow you devs are amazing! can't believe i've had my xoom since launch day and i have never felt like its been outdated since rooting and running EOS. thank you for all your hard work!!

Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
[Xoom Android Development] Lobout:
but you just sent your comment from a Nexus!!! :laugh:
[Xoom Android Development] thehotboy:
the beauty of having more than one android device lol

btw guys just curious why i do not get a new notification from goo for an update? thanks

edit: guessing its cus its officially EOS4 now, cool
[Xoom Android Development] bigrushdog:
Try our gnex build. I'm running the latest nightly. It's sick fast

No notification going from 3 to 4. It's on purpose for complex reasons.

Well looks like everything is going smooth. I'm taking a break. Leave me alone now. :cool::D:p:laugh:
[Xoom Android Development] Lobout:
a well deserved break even if it is only like 9:30 am there ;):highfive:
[Xoom Android Development] REHolt218:
I actually meant gaps file. But it looks like you got the real answer.
[Xoom Android Development] rlmesq:
Maybe I'm riding the short bus, but I can only find the wingray thread for Team EOS 4.

Bueller? Bueller?

Could someone please share the link?
[Xoom Android Development] kentedman:
That's all there is to date. No EOS4 thread for stingray or Everest until its deemed by the devs to be somewhat stable. Now that data is on the verge of finally being resolved you'll most likely see new threads opened soon.
[Xoom Android Development] Mjamocha:
He he he, sorry I could not resist

​
[Xoom Android Development] GedeWK:
Edit: sorry wrong thread actually I wanna post in mz601 thread lol
[Xoom Android Development] johnny0911:
Rolmfao!

---------- Post added at 05:04 AM ---------- Previous post was at 04:59 AM ----------

I have been on eos build 161 sense yesterday afternoon and have had no issues to speak of, there are the minor bugs but that has not prevented me keeping this as my new DD. Thank you team EOS, beer is on me!
[Xoom Android Development] bigdave240:
I see 162 is loading on jenkins. Since the recent changes isnt updated past 150, is there somewhere else we sbould look for the changelog?
[Xoom Android Development] REHolt218:
I was one of the first to load 161 yesterday morning and it has been running great eversince. No application errors or problems. I love having 4g back!! Thanks Team EOS!

I did notice just now that when I go into setup, EOS control center, if I select "softkey settings" EOS control center crashes.
[Xoom Android Development] bigrushdog:
Fixed. Should be cooking now or done.
[Xoom Android Development] bigdave240:
softkey settings works for me. Maybe do a soft reset and see? Running 161 here also

---------- Post added at 10:08 AM ---------- Previous post was at 10:02 AM ----------

dl'ing 162 right now. like Christmas every time i get a new rom from you guys! LOL
[Xoom Android Development] bigrushdog:
It was tied to a bad null check. So if you already had used the feature it still worked. But if first time it failed. But fixed now so we'll just try and forget all about it :laugh:
[Xoom Android Development] REHolt218:
Loaded 162 and it now works! Thanks BRD!!
[Xoom Android Development] bigdave240:
looking good on 162. just did a speedtest on 4g and got 9mb/s dl and 7.5 mb/s upload. pretty good with only 1 bar showing.
[Xoom Android Development] johnny0911:
I agree 162 is working great.
[Xoom Android Development] runandhide05:
Just an FYI in 4.2.x Google re-wrote the way the signal is displayed, if you look at actual signal levels in the about phone/tablet and compare to what 4.1.2 was the actual levels are the same.

So although the singla looks low. Its just about normal.
[Xoom Android Development] dweezle:
I'd like to try 162. I'm at 150 w/gapps-jb- 20120802-eos-signed.zip. Recovery TWRP 2.3.3.0. Which gapps version should load with 162? What should I wipe prior to flashing 162? Will I have any problem going back to my TWRP back up of 150 if I decide to do so?
[Xoom Android Development] runandhide05:
Grab the gapps from win gray eos4 thread's OP

And a full wipe is required ( factory reset)
[Xoom Android Development] kentedman:
and make sure you read this to get your 4G data to activate after instalation

http://xdaforums.com/showpost.php?p=36228957&postcount=2283
[Xoom Android Development] dweezle:
Will that effect the results in RF Signal Tracker too?
[Xoom Android Development] REHolt218:
Coming from 150, I have loaded each of the 4.2.x.x eos4 roms and have never done a factory reset. I am currently on 162 and it is running great.
[Xoom Android Development] thehotboy:
can anyone set custom softkeys on 162? the option disappeared for me

Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
[Xoom Android Development] runandhide05:
He said he was on eos3, that's why I said factory reset, only need to do it if coming from anything but a eos4 nightly
[Xoom Android Development] REHolt218:
Not arguing, the developers certainly know more than I do, just stating a fact. When I first went from EOS3 (150) to EOS4, I forgot to do a factory reset. Everything appeared to work anyway so I did not go back. Since then I have continued to simply load on top of whatever I was running and have had no problems.
[Xoom Android Development] runandhide05:
I didn't mean for it to sound harsh,

Its recommended to factory reset,

;)
[Xoom Android Development] slvrbul:
I can not find the 162 build it comes up as file not located!!!

Carl
[Xoom Android Development] johnny0911:
On the goo manager app?
[Xoom Android Development] slvrbul:
Thanks got it now. I have not installed a ROM yet on my Xoom can I go straight to 162 with the wingray gapps.

Carl
[Xoom Android Development] liftman-:
thanks so much, was on another rom for the past few weeks, and i missed eos terrible.

love the eos settings.

clean install, 4g working smooth, peppy, no fc yet or reboots(only running few hrs)

bluetooth not connecting to my bose soundlink, worked ok in 150. (i did clear it) same problem on cm10.1

log: http://lang-world.com/downloads/2013-01-04-21-10-00.txt

so how can i get rid of that damn search bar?

while using cm10.1 i did like the feature for night time scheduled quite time, be a nice addition to eos rom.

other then that cannot think of anything else in it that was overly cool.(i am not knocking the rom, it ran nice and i do appreciate the hard work of all the developer in all the Android communits!)

thanks
[Xoom Android Development] khanh1289:
did LTE work for you on 162 without the activation process?
[Xoom Android Development] Mjamocha:
Awesome work fellers! Thank you.
[Xoom Android Development] kentedman:
Yes. Data will work without activation, but you can make it successfully activate by going into data/network setting and change subscription type to RUIM/SIM. (Be patient. Takes 2-3 minutes)
[Xoom Android Development] rob62551:
Thanks for the info!

As you described I now have correct MDN/MIN and all seems to be working well as LTE goes!
[Xoom Android Development] Vnvjeep:
162 issues

Going to 162 has been pretty smooth except for a couple of items... for one, each time I reboot, I get the "unfortunately the clock stopped working". Not a biggie, because the clock(s) seem to be working fine.

The bigger issue is that the calendar no longer works. It shows up as not being installed, eventhough its listed under system/app... CalendarGoogle.apk and CalendarProvider.apk. If I try to manually install either, it immediately says "app not installed". If I try loading Google Calendar from the play store, it says "incompatible with another application with the same shared id"

I tried removing both apks and reinstalling 162 and the wingray gapps, but I'm in the same boat. Any ideas?

Thanks in advance for your advice!

Edit: the clock not responding error message does seem to be popping up regularly.
[Xoom Android Development] marnett2005:
I could be crazy, but i feel like 162 made my display look better. Everything seems like it's clearer.

A small issue that I do have involves the keyboard. Any version of the 4.2 keyboard I've used on my Xoom like to close itself for no reason. I thought it would work better if it was baked into a ROM, but it's still happening on this ROM. Is this a common issue, our something that's just with MY Xoom.
[Xoom Android Development] kentedman:
See this post for help with the keyboard issue

http://xdaforums.com/showthread.php?p=36291539
[Xoom Android Development] kentedman:
Go into settings, apps, find clock. Clear data and cache and reboot.
[Xoom Android Development] dweezle:
I'm still trying to find 162, if that's the ROM that has the best shot at a working LTE. GooManager directs me to WIngray versions. EOS3 Stingray stops at 150. EOS4 shows Wingray versions to 169. What should I be looking for and where?

Thanks from deep in the confusatorium.
[Xoom Android Development] kentedman:
http://goo.im/devs/teameos/roms/eos4/nightlies/stingray

Make sure you read earlier instructions given in this thread about getting data to activate. (Its a manual process)
[Xoom Android Development] Vnvjeep:
Duh! Never even knew it was possible to do that for the clock. Fixed that! Thanks!

Anyone have any ideas about my calendar issue a couple of posts up? Not coming up as being installed... I used the gapps package from the wingray forum. :(
[Xoom Android Development] kentedman:
Not sure, but maybe try renaming the calendar apks (apk.bak) and then the reboot and try reinstalling calendar from play or gapps all together.
[Xoom Android Development] freeky1:
Which gapps. Should be loaded with 162?
[Xoom Android Development] Vnvjeep:
Afaik, the gapps package listed in the eos4 wingray forum OP.

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

I've had no luck on this... it looks like everything is installed just fine. Versions are the same as the ones coming from the gapps package. For some reason the OS doesn't think the calendar is installed. I tried renaming the calendar apks in the app folder, rebooting and installing from the market but I get the same error about there being an app already installed with the same id. :(
[Xoom Android Development] Talkdj:
I'm sorry but for the life of me I can't get search and Google now to work. I am using the special gapps for xoom on 162. I've cleared cache etc. Help please?
[Xoom Android Development] runandhide05:
What is the date on the gapps package?
[Xoom Android Development] freeky1:
I'm not sure what this even means...

The one called gapps-jb-201311-EOS-XOOM-ONLY.zip found at http://goo.im/devs/teameos/roms/eos4/gapps/gapps-jb-201311-EOS-XOOM-ONLY.zip is the one I downloaded.

---------- Post added at 03:43 AM ---------- Previous post was at 03:10 AM ----------

I installed 162 and the gapps package in the last post, and it worked like a charm! Thank you Team EOS!
[Xoom Android Development] Talkdj:
That was the problem as I was using the December for xoom only gapps. I didn't see the January xoom gapps was even available. Thanks for the heads up :)
[Xoom Android Development] fling42:
Hey guys, quick question for anyone who knows and has the time- I have Verizon model without the LTE upgrade or a Verizon service and don't really plan to get one (is it even possible(feasible) to upgrade to 4G radios if you missed deadline). I've been running EOS3 150 and love it, but was wondering what my best update options are if I wanted to try a newer build. Without needing to use 4G/3G is there any problems/benifts with switching over to wingray or should I go ahead and use latest stingray? And is it gapps-jb-201311-EOS-XOOM-ONLY for both ROMs?
[Xoom Android Development] jlvlawrence:
You can definitely flash the wingray build if you don't use data.
[Xoom Android Development] REHolt218:
Just wanted to say Thanks again to the EOS4 Team. I have been running nightly 162 for 2 days 6 ½ hours and have had absolutely no problems. Everything runs smooth and fast and having 3g/4g again has been great.

Team EOS4 is the greatest!
[Xoom Android Development] Kauffman_c:
Loving 162.... Only bug I can find is the damn security error with exchange email that we had with the ics upgrade. Can anyone else duplicate? Worked fine on 150.
[Xoom Android Development] bigdave240:
Not sure if its just me but after flashing the 201314 gapps with 162 i have been getting fc's on the browser. I noticed it because on the 201311 gapps it seemed like the memory leak that has been there since honeycomb was either fixed or at least better. I didnt have to clear cache at all. Then i flashed 201314 and it was back and worse than ever. At least that has been my perception. I also noticed that on some web pages as you scroll you would see what i would describe as artifacts that would clear as you lift your thumb? Anyone else seeing this? I think this started with 162 but not 100% sure but it is very recent.
[Xoom Android Development] liftman-:
3 days on 162- no random reboots

no fc messages ( except some lte stuff when switching users, 4g still works)

wish Bluetooth work for my speakers, but i can do without till its fix:laugh:
[Xoom Android Development] rlmesq:
Not cool, dude. I just spent three weeks with my tongue frozen to a flagpole. If we didn't have a few days of warm weather, I'd probably still be there.
[Xoom Android Development] runandhide05:
Can fix if we don't know what's wrong/ anything is broken...

Bug tracker http://code.google.com/p/teameos/
[Xoom Android Development] liftman-:
submitted with log

thanks
[Xoom Android Development] runandhide05:
Thanks I'll take a look at it
[Xoom Android Development] otis_bartleh:
Are the EOS4 Gapps from the wingray thread required, or could I run with a different 4.2 Gapps package?
[Xoom Android Development] bigrushdog:
Use any gapps you want. But the odds are the rom and gapps will exceed the system partition size. Then all bets are off. And make sure the gapps are non neon.
[Xoom Android Development] otis_bartleh:
Cool, thanks. Been a minute since I've been on EOS, so wanted to make sure, I'll grab the EOS4 Gapps to be safe...