yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] tomcrown1:
I may not happen.

It will not be team eos fault as they do not know what protocol is needed for the radio 4g chip in the tablet.

I do not expect team eos to break open the Xoom tablet.

If someone has can you let team eos know what the 4g chip is in the Xoom.

If team eos knows the 4g chip then I do expect 4g to work.
[Xoom Android Development] jm9843:
What's the recommended build to run if you have to have LTE? Stable, nightly 150, or something else? I'm on 148 and it's been great except for the Bluetooth acting a bit flaky. It used to automatically pair no problem, but as of late I need to toggle it off and on before it'll connect to my head unit.
[Xoom Android Development] kcrudup:
This is actually good to know. So, have you ever used your device in an LTE area ever, and is the SIM card still in your Xoom?

Also, could you power off, pull out your SIM card, reboot and see if you get data to pass?

This is much appreciated, and points to the Authentication portion of LTE being the culprit (but I'll need more info to be sure). If we can narrow down just which of the many changes are necessary to get data to pass on our devices, that'll save us a LOT of work (and increase reliability), vs. having to hack the entire layer.
[Xoom Android Development] EtchG:
Your screen looks like mine when I flash 107. Can you actually get to anything online?
[Xoom Android Development] atlmatt:
I live in a 4g area and had data until I upgraded from one on the 1st nightly builds. I will do a complete wipe, reload eos build 100 and flash eos3 107 when I get home and see if It works, I'll get you a log cat as well.

Not sure if it was 4g or not, I signed in to my Google account and then setup WiFi so I know it connected to the internet
[Xoom Android Development] pamaguin:
I am sending this over data and I've rebooted my Xoom
[Xoom Android Development] hchxoom:
Kenny... wasn't it after 100 that we started needing to flash the new radios? Is it possible that those of us that moved beyond 100 need to actually go backwards to old radios in order to get connectivity now on JB?
[Xoom Android Development] pamaguin:
Yes I've used my Xoom in a LTE area
[Xoom Android Development] edjm711:
Do any of you using your xoom on 4G have the new share everything plan? There is a known issue with reactivation if you were on the old plan, and switched to the new plan then reset and had to reactivate. Esn and iccid show in Verizons system but it won't work. Even swapping Sims doesn't work. Via tier 3 ts
[Xoom Android Development] kcrudup:
No, the RIL in JB is currently the same as that in ICS. The issue here isn't the radios (as evidenced by the fact that we have signal strength, in-service-kind status (i.e., LTE/eHRPD/CDMA) and SIM-card number (IMSI)). It appears the JB API changes mean we need to authenticate a different way now (as CDMA like what pamaguin" has service with authenticates a different way (via IMSI/MEID only).

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------

Was your SIM card in after you'd rebooted? (That was actually what I'd needed to know).

(Also, which keyboard is that?)

---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------

I'm not on a Spend Everything plan.
[Xoom Android Development] G8orDroid:
I can confirm pamaguin's assertion that you can get 3g, but you must change to "CDMA only". I did this this morning but work got in the way of posting.

His keyboard looks to be Thumb Keyboard 4. Which coincidently,is what I'm using.

I know I don't have many posts here, but you may have seen me elsewhere as G8orDroid. I have a pretty good grasp on what I'm doing.
[Xoom Android Development] Xezuka:
If anyone is having trouble connecting to Wifi, simply try a factory reset within recovery, reinstall the rom+gapps, then reboot and attempt again.

Worked for me! :good:
[Xoom Android Development] G8orDroid:
I'll pull my SIM and see what happens and get a logcat as well.
[Xoom Android Development] kcrudup:
I'd tried that yesterday when debugging; that only seems to work if you're not in an eHRPD/CDMA transition area.

My Status screen shows "CDMA-eHRPD:14", and not pure "CDMA" like his is, whch means I must still authenticate via SIM-card to get anywhere.
[Xoom Android Development] G8orDroid:
Yes, my status screen does say "CDMA - EvDo rev. A:6", just as his does. I am in a 4g area though, kinda towards the fringe of it, but I don't usually have any problem getting 4g on my Xoom or my Maxx.
[Xoom Android Development] Asphyx:
Well Google announced they would push a JB OTA to Xoom devices later in the month, Won't that help get you the bits you need to get the radios fully working?
[Xoom Android Development] kcrudup:
VERY helpful- thanks.

Which Metro area are you, and how long have they had it?

Apparently (and I likely have some of this wrong, so don't quote me) when VZW started deploying LTE, in order to not have to throw out old CDMA equipment they came up with a middle solution called "eHRPD", which allows LTE to authenticate via CDMA first. I'd imagine they'd use that solution in large Metro areas first (I'm currently in Silicon Valley (the San Jose, CA area)) where there's already a large CDMA base that would be expensive to replace outright.

I'd be happy to get even CDMA-only data until we get this solved, so I'm looking to see what I can do to perhaps force that as an interim solution.
[Xoom Android Development] cadiken:
Just checked and no it doesn't. It did before went to sleep last night. I made a backup and restored using both Titanium and Rom Toolkit and both worked. All I did today was format /system, re-flash rom and gapps. Sorry bro. Rom Toolkit still works though I just checked.
[Xoom Android Development] G8orDroid:
Link to logcat (from lumberjack) with SIM card still in. https://dl.dropbox.com/u/8119920/logcat.txt

Started with wifi on, toggled from CDMA Only to CDMA/LTE, then turned of wifi. 3g came up in about 10-15 seconds and I verified it worked by loading/refreshing the tapatalk app.
[Xoom Android Development] kcrudup:
Yes, but I'm willing to bet that's probably only going to be for the Wingray (MZ600/WiFi-only) devices, which is where we already are. Remember the 5-month delay in getting the ICS build for the MZ602 from Verizon? VZW, for better or for worse, likes to certify the **** out of anything that goes on their network.

(What might help us is if there's a JB LTE handset out there, where we could maybe pull some of the VZW Telephony proprietary APKs from.)

Besides, even if by some miracle the Stingray (MZ602/LTE) build is also ready by the end of the month, I'm an impatient motherfscker and I WANT IT NOW!! :D
[Xoom Android Development] bigdave240:
thanks. not too worried. just a few glitches in this new ROM. I am sure it will get worked out eventually.
[Xoom Android Development] G8orDroid:
I wouldn't really call where I am a Metro Area. Northwest Florida (panhandle) between Panama City and Destin. We've had 4G here for about 3-1/2 months.
[Xoom Android Development] dweezle:
Curiosity killed the cat, or at least lopped off a life or two. I was humming along in150 and decided to see what 4.2.2 had to offer.:o Got into 156 and GAPPS (jb-20121219) no problem, but I wanted to return to 150. Using TWRP 2.2.20 I wiped Dalvik, and installed 150 and the old GAPPS , ( jb- 20120802). When I reboot I get past the Team EOS splash screen and then BLACKNESS. I waited 20 minutes but no luck. Can someone help me find my way home to good ol' 150. It was boringly stable and I miss it.:crying:
[Xoom Android Development] bigdave240:
I guess you dont have a nandroid? If you can get back into twrp i am thinking you need to do a factory reset then flash the rom and and gapps again. I am certainly no expert tbough so you might want wait for one of the experts to add their opinion.
[Xoom Android Development] REHolt218:
You need to read the TWRP thread. Android 4.2 requires the newer version of TWRP recovery due to changes in the system directory structure. I don't know all the details but you should be able to find them there.

---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------

150 was the last 4.1.2 release and the last release to have working lte. It was VERY stable.
[Xoom Android Development] bigdave240:
yeah i noticed he was using an older version too but since be was trying to flash 150 it wouldn't matter. But if he did a factory reset on 4.2 then that may be the issue.
[Xoom Android Development] apollyon0810:
Nightly 150 is probably what most people are using right now for LTE. I don't use 4G, but everything else has been rock solid for over a month since I flashed 150. It's obviously just my opinion, but EOS nightly 150 is probably close to the pinnacle of our experience with the Xoom. I don't think 4.2 is even worth trying to get working on our Xooms. What benefits does 4.2 have over 4.1.2 besides multi-user support? I've tried some 4.2 Roms on my Xoom and the performance is just horrible. It's just the hardware starting to show its age. Going on 2 years! This thing is ancient!

Edit: I had this stern realization at Best Buy last night whilst playing with a Nexus 10 and some new-fangled Windows 8 tablets (all of which were pretty awesome and fast as hell when compared to my Xoom).
[Xoom Android Development] bigdave240:
I am not seeing that on my xoom running 156. Actually one annoying problem that seems much better on 4.2 is having to wait for a page to finish loading before the links on it are active. Much shorter time on 4.2 than 4.1. Did you do a full reset before flashing to 4.2? Maybe I am just lucky but i am not going back to 4.1 now. Even if they cant get lte working i will just tether to my phone. Save me $40 a month.
[Xoom Android Development] jlvlawrence:
I didn't realize they sold the nexus 10 at best buy.
[Xoom Android Development] dweezle:
Made it back to boring, stable 150.;) Note to self; Things change. Read the damn TWRP posts to check for upgrade before charging ahead with new ROM:o

Thanks to all here for the guidance.
[Xoom Android Development] Mjamocha:
Yes 150 is very stable, but hardly boring. I've used 4.2 and in my experience, it was smooth, a little faster, but it was not all that spectacular. I guess like anything else, it all depends on the user and their device needs. Respect to the Devs, keep up the good work. We appreciate it.
[Xoom Android Development] apollyon0810:
Hello all. I was wondering if there was a quick answer to this...

I decided to try nightly 156 and I'm really not enjoying it. Previously, I was on nightly 150 with the latest TWRP from this Xoom development forum. I made a nandroid of my Xoom w/ nightly 150, but when I restore it, it just hangs at the splash screen. Any ideas? I let it sit for over a half hour last night hoping it would just load after a while...

EDIT: Well, I just wiped and installed nightly 150 fresh with the 08022012 eos-gapps. It booted up just fine. I went back into recovery at the activation screen and am currently doing just a "data" restore from TWRP (On the 12/19 build now. Wasn't originally, but was on the "4.2 fixed" version immediately preceding the current version). Ill let ya know how it goes!

EDIT 2: Seems to be back where I want it. For some odd reason restoring the "System" partition from my nandroid borked my Xoom. Solely restoring the "data" partition brought me right back to where I wanted to be after doing a clean install of the ROM and GAPPS.

TLDR; SOLVED
[Xoom Android Development] Mjamocha:
Happy Holidays To All!

​
[Xoom Android Development] bigdave240:
157 dropped! Christmas presents?
[Xoom Android Development] electroman987:
Hey all,

If a Xoom needs to be "broken" open and examined, I can do this. I'm a electrical engineer in "training" Lol. Been doing things like this forever. Will see what I can do when I get back from the keys in Florida.

Cheers
[Xoom Android Development] bigdave240:
158 is out. Fixes issue from 157 of the tablet continously rebooting when left idle. Hadnt even noticed that until last night. But it seems good now on 158
[Xoom Android Development] bigrushdog:
If you could, please test bluetooth HID (mouse, kbd, etc), hdmi, and by chance did at least 3g pop up yet?
[Xoom Android Development] bigdave240:
Sorry, didnt bring any bt stuff with me. No data either. No 3g or 4g. Meid still only shows 4 digits under status.
[Xoom Android Development] REHolt218:
I still get a continuously occurring error about the phone app stopping whenever I turn off airplane mode.

I will try Bluetooth and HDMI and report back to you.

Edit: HDMI works great!

Edit 2: BlueTooth Keybord works as well! I have a full size Logitech Bluetooth Keyborad and am using it to type this message,
[Xoom Android Development] stevefxp:
Are these updates available for all? I am still on 150 and Goo does not show any updates.
[Xoom Android Development] REHolt218:
Yes, go to this link for the 4.2 EOS4 ROM and gaps listing: http://goo.im/devs/teameos/roms/eos4
[Xoom Android Development] bigrushdog:
Beautiful. I got my old xoom back for about a week. Let's see if i can get LTE going.
[Xoom Android Development] bigdave240:
Make sure you have a good nandroid in case you want to go back. Should probably do a factory reset and you have to use a recovery that has been updated to be used with 4.2 such as the twrp 2.3.3. If you dont then hou will have problems if you facgory reset under 4.2. Make sure to flash the recovery if you have to change it before making the nandroid though so it will be compatible. Use the gapps for 4.2 xoom not neon
[Xoom Android Development] REHolt218:
At one time there was a new gmail app floating around "Android_Police_Gmail2.apk" with pinch to zoom capability. We seem to have lost that in the latest EOS Gaps and I can't seem to get it to install. Anyone still using it? Is there any way to get it to install on the latest nightly?
[Xoom Android Development] Droidem:
Couldn't you just install the apk like you did before? Or are you wanting it to be included in the gapps package?
[Xoom Android Development] flippingout:
I am updating an old Xoom (wife got the N10) and I want to update to 150. On my Xoom I remember having to flash new radios before moving to 98 build (I think it was that build). Anyway, I can't find the radios to flash in Rogue Recovery. Do I still need to do this or if I flash 150 will that include all the required files? The Xoom is currently on build 93.

Thank you!

Edit: never mind, found the Goo link on page 10 of this thread.
[Xoom Android Development] bigrushdog:
Good deal. If something goes south post up. But it's pretty straight forward. Wipe, flash radio, rom, gapps, reboot, profit.

On a separate note. Can someone run netcfg and post up the output. Thx.
[Xoom Android Development] liftman-:
Thank you for using Better Terminal Emulator Pro

/ $ netcfg

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00

dummy0 DOWN 0.0.0.0/0 0x00000082 ae:8b:17:f2:e3:75

ifb0 DOWN 0.0.0.0/0 0x00000082 b2:e8:d5:c5:cd:79

ifb1 DOWN 0.0.0.0/0 0x00000082 02:05:bd:9c:19:03

sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

wlan0 UP 192.168.1.151/24 0x00001043 40:fc:89:2b:a5:2d

qmi0 DOWN 0.0.0.0/0 0x00001002 3e:42:bf:5b:71:52

qmi1 DOWN 0.0.0.0/0 0x00001002 ba:87:7a:01:3a:f6

qmi2 DOWN 0.0.0.0/0 0x00001002 ba:cb:5a:7e:b8:24

qmi3 DOWN 0.0.0.0/0 0x00001002 52:73:8f:0d:c7:b1

usb0 UP 192.168.20.1/29 0x00001043 02:21:00:1d:34:fb

mmi0 UP 0.0.0.0/0 0x00001043 02:21:00:1d:38:fb

mmi1 DOWN 0.0.0.0/0 0x00000002 02:21:00:1d:3c:fb

mmi2 DOWN 0.0.0.0/0 0x00000002 02:21:00:1d:40:fb

mmi3 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:44:fb

rmnet0 UP 0.0.0.0/0 0x000000c3 02:21:00:1d:38:fb

/ $
[Xoom Android Development] bigrushdog:
Ok that's beautiful. We're almost there. Thanks liftman

Edit : that is eos 4 right?
[Xoom Android Development] REHolt218:
I tried that, but it will not install. I get " installation failed" error each time. I saw something earlier about changes that were made to the Xoom gaps for 4.2 I was wondering if that had anything to do with why it won't install?
[Xoom Android Development] Droidem:
If I remember correctly you have to delete the old gmail apk then install the new one as a system app.
[Xoom Android Development] kentedman:
Here's one from cm10.1 stingray with working 3g if it helps for comparison.

:/ $ netcfg

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00

dummy0 DOWN 0.0.0.0/0 0x00000082 fa:38:82:3e:ad:f2

ifb0 DOWN 0.0.0.0/0 0x00000082 ce:3f:a7:50:02:27

ifb1 DOWN 0.0.0.0/0 0x00000082 7a:7d:12:54:15:33

sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

wlan0 UP 192.168.1.106/24 0x00001043 40:fc:89:0b:2e:6c

qmi0 DOWN 0.0.0.0/0 0x00001002 3e:e6:67:31:6b:13

qmi1 DOWN 0.0.0.0/0 0x00001002 7e:59:2d:6d:98:93

qmi2 DOWN 0.0.0.0/0 0x00001002 fa:ba:bd:7e:89:3f

qmi3 DOWN 0.0.0.0/0 0x00001002 2e:64:58:b3:8a:f1

usb0 UP 192.168.20.1/29 0x00001043 02:21:00:1d:34:fb

mmi0 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:38:fb

mmi1 DOWN 0.0.0.0/0 0x00000002 02:21:00:1d:3c:fb

mmi2 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:40:fb

mmi3 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:44:fb
[Xoom Android Development] bigrushdog:
Thanks. Ya i'm pretty sure liftman posted eos 3. Lol this is the 3 thread after all. No way can rmnet0 be up on eos4. I'd s**t kittens if it was though :angel:
[Xoom Android Development] kentedman:
I'm currently backing up and will wipe and fresh install eos4. I'll send netcfg shortly

---------- Post added at 11:47 PM ---------- Previous post was at 10:55 PM ----------

Hers from clean install of EOS4 stingray 158

u0_a39@android:/ $ export PATH=/data/local/bin:$PATH

u0_a39@android:/ $ netcfg

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00

dummy0 DOWN 0.0.0.0/0 0x00000082 aa:d7:76:f5:5e:56

ifb0 DOWN 0.0.0.0/0 0x00000082 6e:90:20:09:e9:93

ifb1 DOWN 0.0.0.0/0 0x00000082 12:3b:38:44:83:ba

sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

wlan0 DOWN 0.0.0.0/0 0x00001002 40:fc:89:0b:2e:6c

qmi0 DOWN 0.0.0.0/0 0x00001002 4a:cd:5e:70:4f:f1

qmi1 DOWN 0.0.0.0/0 0x00001002 e2:0d:68:e9:07:dc

qmi2 DOWN 0.0.0.0/0 0x00001002 fa:2f:f4:c5:2e:45

qmi3 DOWN 0.0.0.0/0 0x00001002 b2:fa:1f:42:00:5c

usb0 UP 192.168.20.1/29 0x00001043 02:21:00:1d:34:fb

mmi0 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:38:fb

mmi1 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:3c:fb

mmi2 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:40:fb

mmi3 DOWN 0.0.0.0/0 0x00001002 02:21:00:1d:44:fb

u0_a39@android:/ $

MDN/MIN Is still only pulling four digits (and the wrong ones). But I didn't get any telephony fc's at all this time. The radio indicator is showing 3 or 4 bars though.
[Xoom Android Development] bigrushdog:
I got my old xoom back from my buddy for a while. I'll be able to test more effectively now.
[Xoom Android Development] liftman-:
sorry eos 3 build 150.
[Xoom Android Development] kentedman:
I'm currently running cm 10.1 stingray 4.2.1 with working 3g (dirty upgraded from cm10) and I have rmnet0 (which I guess is why 3g works)

Glad you got your stingray back. Still happy to help with logs or tests if needed. Thanks
[Xoom Android Development] Maikai.Guy:
I, for one, am hoping team EOS works out the LTE thing with 4.2.

A dual core system running at 1GHz isn't "showing it's age" and it's not "ancient". I'm working on a Cortex A5 development system running below 600MHz with 4.2 running on it. It is smooth, albeit limited with regards to running a lot of concurrent apps. The issue with the XOOM is Motorola/Verizon stopped supporting it awhile ago, so the LTE code needs to be migrated.. which can be a challenge.

I hope EOS is up to the task and takes on this challenge.
[Xoom Android Development] liftman-:
yea that should make it alot easier- u can do it :)
[Xoom Android Development] bigrushdog:
This is an accurate assessment. There's a handful of classes from 4.1.2 that need to be wrapped into the 4.2 telephony framework. Indeed it is proving most challenging. I may start a brain dump thread for collaboration.
[Xoom Android Development] freeky1:
I am excited about the prospect of having 4.2 only Xoom. I have already ordered a Windows 8 Pro tablet, but I am keeping my Xoom too. I'm not sure I am ready to go completely back to Windows again, but I wish Android didn't have so many limitations.
[Xoom Android Development] liftman-:
lol

without walls who needs windows
[Xoom Android Development] freeky1:
Unfortunately Android has many more walls than Windows does. I love Android on my phone, and I use my Xoom several hours a day every day. It just seems that too often I have to put down my Xoom and pick up my laptop to complete a task. Whether it is due to a limitation of the browser or being unable to print or not being allowed to watch Hulu or the owner of a video on YouTube not allowing it to be viewed on mobile. I run into many more walls with Android than with Windows. I think that if Flash still worked on the Xoom, I might feel a little different. Like I said, I love my Xoom and I am using it right now.
[Xoom Android Development] kentedman:
Who says flash doesn't work? Just because it isn't available from the play store doesn't mean it isn't available. Flash, hulu, YouTube (desktop version). All working great on this rom. That's the beauty of android. Wonderful smart people continue on after the manufacturers and official developers stop. It cost $300 everytime I want to update windows. In the year and a half I've owned my iPhone I've gotten maybe 4 updates from apple, yet on my xoom I literally get updates, improvements and fixes almost daily.... and all for free. Yes. I still use my laptop for some things, but I also pickup my xoom over my laptop for many more things
[Xoom Android Development] liftman-:
it is a reference to all the "nix's" os's in general, if you do not get it it is ok- lol
[Xoom Android Development] freeky1:
Gotcha! I just wanted to be clear that I love Android and I love my Xoom and will continue to use it. I'm just not sure I will buy another Android tablet.
[Xoom Android Development] runandhide05:
The newest g.ail is in the gapps package, as long as you r using the correct package dated 1216 xoom-only.

http://goo.im/devs/teameos/roms/eos4/gapps/gapps-jb-20121216-EOS-XOOM-ONLY.zip

You have to enable the pinch to zoom in the general settings.
[Xoom Android Development] REHolt218:
Thanks! Somehow I missed that. On 150 it worked by default.
[Xoom Android Development] Mjamocha:
Happy New Year All

​
[Xoom Android Development] johnny0911:
HAPPY NEW YEAR ALL!

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

I have been experiencing force closings wherever I try to open google now, I am on the latest eos nightly. I am able to run the setup but right afterwards it just flashes back to the home screen. Any ideas?
[Xoom Android Development] bigrushdog:
Go into settings/app and remove the update.

I got a new build cooking. It's has experimental lte apks in it. Lemme know if we get any win. I'll take even a glimmer of win at this point lol.
[Xoom Android Development] johnny0911:
While I was browsing goo manager I noticed there was a stingray build for jb 4.2 I installed with the correct gapps but I could not activate data. I did some searching and was unable to find a support forum here on XDA for stingray my question is, is this only experimental? The ROM was running great but I must have data.
[Xoom Android Development] kentedman:
No data yet but that will change soon. BRD sounds very close to cracking this and one of the other teams {cm) got 4g working just this morning. So hang tight. Data is imminent.
[Xoom Android Development] REHolt218:
I saw where 159 was compiling this morning on Jenkins Dashboard and now shows complete; however, I can't find 159 at either of the normal locations.
[Xoom Android Development] johnny0911:
That is awesome! I was not sure if it was for 4g or not. Can't wait and please take your time BRD your work is phenomenal!

Edit: do we have to use a modified recovery to install 4.2 being it is dual users?
[Xoom Android Development] bigrushdog:
Confirmed tdr cracked lte wide open. I congratulate him. Guess I'm getting rusty in my old age lol.
[Xoom Android Development] johnny0911:
That is bad a$$