yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] brittoking:
I have an odd problem all of the sudden: my google drive documents are blank. All of them? I tried clearing cache and uninstalling but to no avail. Any ideas at all would be appreciated. Thank you in advance!

Edit: Nevermind! They each loaded after an interminably long time of starting at a blank page. Weird

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] REHolt218:
EOS Bluetooth pairing

Is there a trick to getting the Xoom to pair with Bluetooth devices?

I've never really Used Bluetooth with my Xoom so I just haven't thought about it until yesterday. I bought an ELM 327 Bluetooth device to read diagnostic codes from my car. When I went to pair my xoom to it I started the process without really knowing the key code (wasn't in the documentation), the first time it tried to pair it came up and asked for the key so I entered "0000" and it errored out. Now it will not even ask for the code.

I tried with my wife's Acer A500 using 1111 and everything worked fine.

I also tried to pair with my BMW stereo but again the Xoom will not even ask for the key code but the Acer works fine.

Anyone have any suggestions?
[Xoom Android Development] hchxoom:
I can't test to confirm right now, but believe you go into settings and bluetooth on the xoom and look for the device. You should be able to select the device and "forget" it, much as you forget a wifi connection you no longer want. Once forgotten, you can scan for devices, choose yours, and the init setup should start over. Post your results, and if that doesn't work I'll be glad to experiment later today.
[Xoom Android Development] REHolt218:
I tried that last night and never could find a way to make it "forget" the connection. When I select the device it says it is pairing, but never asks for the code.
[Xoom Android Development] TheRandom1:
May have to longpress the device to get the popup asking if you want to connect or forget or detonate nuclear explosives*

(*last bit was a joke since I don't recall the 3rd option it gives but could swear there is one)
[Xoom Android Development] REHolt218:
I don't get any response when I "long press" on the device. Initial press starts the pairing operation (without a request for key code) but longpress does not give any other options.
[Xoom Android Development] TheRandom1:
Interesting. Wish I'd have brought my Xoom with me today, could have sworn that was how I did it.
[Xoom Android Development] REHolt218:
Any chance that the pairing information is stored in a directory somewhere that can be deleted?
[Xoom Android Development] Drakkula4:
Anyone have problem connecting to 4g?

I seem to be only getting 3g at all times with no success of even a single bar of 4g.

This started happening 3 days ago, the odd thing is my gnex gets 4g 100% of the time.

Any suggestions?

I'm heading over to vzw to see If its the sim possibly, just figured I'd ask if anyone has this issue too.

Nightly 93, stingray.

Thanks
[Xoom Android Development] rob62551:
Been on 93 a longtime no 4g issues. On 94 now and sending this while on 4g!
[Xoom Android Development] Tom_S:
I didn't have any trouble connecting to 4G while I was on Nightly 93. I'm on 94 now and all seems perfect. :D
[Xoom Android Development] kcrudup:
Apparently, it's not just you. Perhaps VZW is having yet another LTE issue in your area? I'm assuming you've rebooted?
[Xoom Android Development] hchxoom:
Kenny - couldn't find a changelog for #94... does it include anything from the new ics release for the 4gxoom?

REI... will try to test bt connect and forget in my car in a bit and will report back.

Edit:

REI... after pairing with bt in my car, when I open settings/bt I see the device listed. Off to the right, there is a settings icon (see screenshot). Clicking on that, I get several options including "unpair", which should be what you need. I'm not 100% certain this will work for you as it sounds like your initial pairing was unsuccessful... if you don't see the icon on yours, let me know and I'll try to fail in pairing the device and see if I can reproduce your issue. I'm on #93, by the way... which build are you on?
[Xoom Android Development] kcrudup:
I don't really keep up with the changelogs, but as we just got the system dump yesterday (and Thanks, airesch!), and I'm just now pulling the relevant stuff (we don't need everything, just the proprietary binaries), I'd assume not.

I'm sure SolarNZ (who does most of the packaging) will probably give that stuff a bold new banner, if not a new release revision, when we have it all integrated.

... but it's the #1 thing on my list (I want the new radios and BT firmware, for sure!) so stay tuned!
[Xoom Android Development] SamuriHL:
Most excellent. This is what I was hoping would happen. I thought I read, too, that the official ICS release has a fix for random reboots. Maybe something in the proprietary code will help those who've had that issue with EOS. In any case, I see this as a major positive. Looking forward to a release with all that in there.
[Xoom Android Development] kcrudup:
I only thought it was one or two people who've had an issue with those, though? In any case, 95% of any cause of that would be in the kernel, and we're not going to use the official kernel (my kernels have new code, optimizations and fixes that wouldn't be in any Moto kernel (yet, anyway)).
[Xoom Android Development] SamuriHL:
I haven't had the issue lately that I'm aware of. But I had before. I guess it makes sense that it'd be a kernel issue. And to be fair, I haven't seen any reports of that happening to people recently. The problem I was having most recently was that stupid CNN app causing it to wake up constantly. (Thanks for that!) So maybe it's a non-issue now.
[Xoom Android Development] solarnz:
Not yet.

#94 has a new kernel, and the ability to blacklist or whitelist applications from writing to the logs. (Useful for blocking applications that spew personal information into the logcat)
[Xoom Android Development] Drakkula4:
Just got back from vzw. Swapped sim, full wipe, several reboots, and still no go. Like I said tho, my nexus is 3 bars strong on 4G. So its definitely not the network. So now I'm thinking its the tablets. I guess now all I can do I lock/unroot and hope for the best. Thanks for the help
[Xoom Android Development] kcrudup:
How do you figure that will help you? So many other people are running the same ROM as you are, but you're the only one saying they're affected with an outage. If anything, it's either hardware (which I still say is unlikely) or VZW is having an issue- don't forget, it's possible to have authorization issues with a single device, as there's SIM (IMSI) authentication and IMEI authentication.

I just don't want you to have to wipe your Xoom over this just yet, since it's such a drastic step. If anything, I'd try reinstalling our Official 2.0 build or a previous nightly and see what happens.
[Xoom Android Development] REHolt218:
Thanks for the help and testing.

Yea, my problem was a failed pairing. I don't have that icon out to the side because it isn't paired yet. After the failure it just quit asking for the key code.
[Xoom Android Development] Drakkula4:
First off thanks for the help.

Before i got a chance to read your reply, i went and did as follows.

1- Update from Nightly 93 to 94 - Outcome, still no 4G (not even the icon switching from 3g, just plain and simply nothing) :eek:

2 - Updated to Official EOS 2.0 - Outcome, Still same. :confused:

3 - Full wipe on EOS 2.0 - Outcome, still the exact same. :mad:

4 - ADB, stock image and lock to HLK75D - Outcome, still no 4G, but this time it at least switched to the 4G icon and then back to 3G. :confused::confused:

5 - System update to HLK75F - Outcome, switched to 4G (speettest.net apk, ran 18.7 DL speed)

then another update came along to HLK75H, and now its still good, 4G, 3G, no prob at all anymore.

now since this part is completely out of my league, this is my question.

Could Motorola/Verizon in some way shape or form, have targeted specific tablets to disable 4G, or anything at all to get us some flash back to stock to accept the coming OFFICIAL ICS update easier I guess?

thanks again guys, I would be a lost little sheep without everyone here, and all the things I learn here everyday. :D
[Xoom Android Development] hchxoom:
No problem, I was afraid that might be the case. I can't do it tonight, but will test a failed pairing tomorrow after a morning meeting and see if I can help figure anything out.

EDIT: try this... in settings/apps (all), find bluetooth share (a system app) and clear data, then reboot... this cleared my cached devices list entirely.
[Xoom Android Development] twinkyz1979:
I went back to stock upgraded to OTA ICS 4.0.4 didn't like it so went back to nightly 93 updated to nightly 94 and never once had 4g problems.

Although i would like to know what changes were made in nightly 94 though since they have not been posted.
[Xoom Android Development] rob62551:
New kernel 3.0.22

Ability to whitelist or blacklist apps that record to the log. You can find under system in the settings.
[Xoom Android Development] kcrudup:
Bizarre ... The kinds of changes you saw could only happen if some files in our builds didn't transfer properly, but ... that just really doesn't happen.

Ah well, T-EOS is essentially done pulling our builds to the IMM76L radio versions, so expect a new build soon to try.
[Xoom Android Development] liftman-:
yea going on 6 weeks for me in columbus ohio area, but if I leave columbus 4g works great.

man what a fight with verizon.

new sim card, put factory rom on unrooted no luck. have 6 hrs on the phone with verizon tards lol
[Xoom Android Development] apollyon0810:
I live in Columbus and my 4G is bang on. Full bars just about everywhere on my Gnex. I've never activated my Xoom. :-(
[Xoom Android Development] twinkyz1979:
Why is the changelog not being updated for the new releases? What changes happened in #95?
[Xoom Android Development] khanh1289:
Anyone experience FC when using the face effects with front camera?
[Xoom Android Development] runhopskipjump:
Bug: The Status bar toggle option in nightly 95 no longer functions properly. The status bar just becomes unresponsive when toggled to be hidden.

Xoom 4G + Team EOS ICS nightlies = WIN
[Xoom Android Development] REHolt218:
35 seems to have disabled 3g/4g completely. Wifi works great though.

Edit: make that Stingray Cornerstone nightly #34 and Stingray Nightly #95 has done the same thing unless viz is dead this morning.
[Xoom Android Development] rob62551:
Same here. Looked into settings and found that there is no base band listed. Listed as unknown.

Went back to 94 and 4g is working just fine. On it right now.
[Xoom Android Development] SamuriHL:
Yup it's definitely broken. Since I'm not traveling with it for a couple days I can live on wifi until it's fixed.
[Xoom Android Development] brittoking:
95 definitely broke 4g and as I don't see a new changelog I went back to 94. I did see the theme chooser in the settings interface though?! There's only the one theme though, anyone know how to use that (do you download specialized themes? Sorry for that noobish question but that's a new feature set for me lol) or is it still being developed perhaps as there's no choices with it currently.

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] rob62551:
Yes you have to download themes. Since 4g didn't work, I went back to 94 and didn't take the time to try it yet.

Search market for CM9/AOKP themes utilizing TMobile themer
[Xoom Android Development] kcrudup:
Re: busted LTE- SolarNZ will get the new radios package from the IMM76L Moto/VZ drop we just got put up officially, but until then, you can get the new LTE/CDMA radios here. You'll need to flash that via recovery (just like you would an "update.zip").

Sorry about that; I wasn't aware the changes were going in just yet.
[Xoom Android Development] rob62551:
Thanks! You gentlemen do excellent work for us all.
[Xoom Android Development] REHolt218:
I down loaded the radio package and installed it over 95 but it did not solve the problem.
[Xoom Android Development] rob62551:
It works for me. Flashed radio and 95 and gapps all together. Only cleared cache and dalvik as usual.

Getting 22 down and 14 up on Speed Test.

Baseband is listed as CDMA_N_03.1A.65P LTEDC_U_07.1F.00

Also stay away from status bar toggle! Definitely does NOT work!
[Xoom Android Development] SamuriHL:
Ummm, hmmm. I'm using Rogue Recovery and am not sure how I can flash the bin file? Am I being an idiot today?

EDIT: Woa, I missed that Solarnz released EOS recovery R6 back in freaking April??? Good lord. :(

---------- Post added at 12:19 PM ---------- Previous post was at 11:43 AM ----------

Ok, so I got the radios updated and it doesn't seem to work for me, either. Do we have to reflash the rom after doing this?
[Xoom Android Development] rob62551:
[/COLOR]Ok, so I got the radios updated and it doesn't seem to work for me, either. Do we have to reflash the rom after doing this?[/QUOTE]

In my case I flashed 95, ggapps and the radios all together. Don't know if that helps.

I know I am on nightly 95 with baseband listed in my prior post. Themes do work. Have to say some are merely changing blue to whatever colors.

Going to try Bazaar's.

I wish I had a better answer for you!

Curious SamuriHL, in settings/about tablet, does it show the baseband?
[Xoom Android Development] SamuriHL:
No, it shows unknown which is definitely a problem. :) I'm attempting to roll back to 94 at the moment and see what happens. Definitely doesn't seem good though.
[Xoom Android Development] rob62551:
I rolled back to 94 also due to status bar toggle failing. When I recovered my backup all was good EXCEPT NO RADIOS!

I said the heck with the status bar toggle for now. I went ahead and flashed 95, ggapps and the radios all together (after normal wipe).

Got me working. Maybe check your radio zip file to be sure it's good?
[Xoom Android Development] SamuriHL:
Similar to what I'm trying now. I rolled back to 94, made sure it was working (it was) and am now flashing 95, gapps, and radios. I redownloaded it on my laptop and transferred it over via usb cable to make sure it wasn't corrupt. When I downloaded it on Chrome on the Xoom this morning it gave me a weird uuid filename with a .bin extension. Screwy. Anyway, rebooting the xoom now so we'll know shortly if it worked.

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

Nope. Unknown baseband. SIGH. This sucks. :(
[Xoom Android Development] hchxoom:
Sitting in rdu airport and downloaded 95 and radiopack from kcrudup... flashed 95, then radios, then gapps (radio flash took a fairly long time) and rebooted. 4g radio working great, 2 more bars than prior radio and seemed faster reconnecting to these forums. Baseband changed as expected.
[Xoom Android Development] SamuriHL:
Believe me, I WILL get this fixed. I just created my own update zip for the radios from the OTA update for ICS. We'll see if that works any better. If not, I'll do it the old fashioned way and force the issue.

---------- Post added at 01:30 PM ---------- Previous post was at 01:24 PM ----------

I really don't know what the problem is with this. :( And apparently you can't fastboot flash the radios????? Well that sucks. I may have to get a bit more creative as this is most definitely NOT working.
[Xoom Android Development] bigrushdog:
Everybody take a deep breath..... ahhhhhh. Better. For now, flash kcrudup's radio pack and reboot. then in your terminal, run

savebpver

Then let it sit for a few minutes. Lemme know what happens. you guys act like you don't remember history! Who brought you LTE on ics? Who's gonna babysit you through this one? :p:rolleyes::cool:
[Xoom Android Development] SamuriHL:
I know FULL WELL who brought LTE on ICS and seriously appreciate it! :) That's why I'm trying to fix my Xoom on my own without trying to bug you. Isn't it better when the community is actively trying to solve problems? :D Anyway, once I get back to 95 and if I still have the issue, I most certainly will do as you suggest.
[Xoom Android Development] bigrushdog:
SamuriHL you've been in the game since the start. Nothing but love :D.

Mirror for kcrudup's radio pack here

I'm currently disconnected atm but that shoudn't slow me down. You guys will have your beloved LTE back soon.
[Xoom Android Development] SamuriHL:
I'm almost done with what I'm trying. If it doesn't work it'll be interesting to figure out why. Cause I went back to 94, rebooted to make sure I was back on VZW network, checked to make sure the previous baseband was installed, and all that checked out. I went back into recovery, flashed the radio update, rebooted again and still had VZW connection with the updated baseband (the version posted above). So that's encouraging. I've now run the update for 95 again and we'll see how things go from there.
[Xoom Android Development] rob62551:
Just curious BRD, if all is well with the 4g and I've rebooted a few times and all remains and works; do I still need to do what you've stated?

Thanks for all your hard work. BTW, themer works well . Just tried Bazaar's Green and Red and it does what he's gotten to work so far.
[Xoom Android Development] SamuriHL:
Ok, so, that idea did not work. I have no baseband again. Running the savebpver command as we speak.

Alright the command finished and output a "255". What next?
[Xoom Android Development] bigrushdog:
This is the sequence i'm trying now. I've had cdma showing but i haven't got the lte baseband to show yet.
[Xoom Android Development] bigrushdog:
No. if you're already up and running, take your win and run! Sit back and watch us do the funky chicken and laugh.

EDIT: well, it looks like in my case the LTE radio is not sticking. I show correct cdma radio, but the LTE radio is the old version.

INFOversion-baseband: CDMA_N_03.1A.65P
INFOversion-baseband-2: ltedc_u_05.19.00
[Xoom Android Development] SamuriHL:
Isn't that a good time! :) At least I'm not alone in having issues. Small comfort, I know :D
[Xoom Android Development] kcrudup:
First- for all of those affected by no radios, my apologies. Team-EOS is usually more stable than this but as with any Development ROM, things sometimes don't always work the first time when presented to the full userbase. When I get to the office today I'll post up a file with the old radio set, in case you want go to back (once the radios are flashed, the ROMs prior to today won't know how to work with them).

Also, I believe (but not certain) that after flashing the radios, it might be necessary to immediately reboot (into recovery, not a full boot) then flash the ROM.

Secondly- it appears that the radio versions that "fastboot getvar all" and what's shown in "Settings/About" don't get updated until "savebpver" writes them to NVS somewhere outside the ROM, but it appears that "savebpver" won't get called until successful RIL operation(s) take place and then some info is saved. I can't say for sure, but there is a chance that some of you may have to restore your previous "Data", flash the new radios, flash the latest ROM, then reboot.

If anyone who's got issues wouldn't mind sending me a compressed copy of "adb logcat" after it's been running for about 5 mins from a fresh reboot, it'd be appreciated.

Be assured we're trying to get you all back on line!
[Xoom Android Development] twinkyz1979:
I have just installed 95, then gapps, then the radios, and then wiped cahe/davlik cache rebooted and have 4g working.

I am currently rebooting to see if it saved or not.

It did save but i am not sure if it did it on it's own or if using savebpver had something to do with it since i used it as well. Although there was no pausing after using the command like there normally is when the OS is doing something like writing to storage.
[Xoom Android Development] SamuriHL:
Sooooo, it simply sucks to be me? Is that what you're all saying? :D Ok, time for one of my infamous stupid questions now. :D Those that are succeeding...what recovery are you using? SPECIFICALLY...version, etc.
[Xoom Android Development] kcrudup:
It really shouldn't matter, as everything needed to flash the radios is included in the .zip file, but FWIW I use the latest Team Rogue touch recovery.
[Xoom Android Development] twinkyz1979:
CWM Rogue Touch Recovery v1.5.0 is what i am using only because i think the other touch recovery is a little to touchy. Nothing against Team EOS i normally love their stuff.

http://xdaforums.com/showthread.php?t=1235170
[Xoom Android Development] SamuriHL:
I agree. I'm just trying to rule out all the possibilities. Thanks!
[Xoom Android Development] stevefxp:
Should the saverbpver output something? I entered it but the next line is blank!
[Xoom Android Development] twinkyz1979:
So was mine and it never paused or anything just right to the next blank line.
[Xoom Android Development] stevefxp:
Ok cool...mine just returned.

I rebooted one more time and Baseband is still showing as unknown on my Stingray.
[Xoom Android Development] twinkyz1979:
Mine was showing unknown in 94 until i flashed 95, gapps, and the radio update then wiped cache/davlik cache then rebooted. After i rebooted i had a blue 4g in the corner then i went into terminal and typed savebpver then rebooted again and still have 4g. You may want to try going back to 94 and following what i did and see what results you get but make sure you follow the same steps as it looks like maybe there is something involved there that may help.
[Xoom Android Development] SamuriHL:
Alright people listen up. :D I fixed mine. I used Rogue Recovery and followed these steps exactly.

-Make sure 94 is working and you're able to connect to VZW

-Reboot into Rogue Recovery

-Install the radio update

-REBOOT, and head directly back into recovery

-Install 95 + gapps

-Wipe cache and dalvik

-REBOOT

This should in theory do it for you. I now have the latest baseband and am connected.
[Xoom Android Development] bigrushdog:
Seems to me that I'm doing more harm than good trying to give advice while disconnected. So ill just step over here and make a new Button or something. :rolleyes:
[Xoom Android Development] SamuriHL:
I don't think so. :) You know far more about this than me!! I'm just persistent and stubborn, that's all. :D In any case, it did seem like recovery made a difference so I think more testing should take place around that. Find out why solarnz's EOS recovery had issues and/or whether it was only me that has/had an issue with it. But at least we know a way that should work for most people now.
[Xoom Android Development] solarnz:
With the theme engine just being introduced, there is obviously going to be some bugs.

Please report them on https://bugs.teameos.org
[Xoom Android Development] kcrudup:
BTW, I should point out the use of "savebpver", while likely benign, shouldn't be used by the end-user. All it does is save the baseband versions (and perhaps something else?) to NVS, but it won't fix anything if the system doesn't connect for whatever reason.

T"L";DR: stop using savebpver. It won't help.
[Xoom Android Development] solarnz:
Radio update zip that is required for the latest nightly onwards: http://goo.im/devs/teameos/radios/imm76l-radios-update.zip
[Xoom Android Development] Vnvjeep:
no dice...

No luck... mine still shows unknown. :-( Ughh. Any other advice on getting this to work? On 95 now... wifi works great... 4g, not so much.
[Xoom Android Development] SamuriHL:
You followed all the steps? And you're using Rogue Recovery? UGH!!! That's the only thing that seemed to work for me. Note that I didn't boot back into a rom after updating the radio...I rebooted and went right back into recovery. I'm not sure what else could be going on.
[Xoom Android Development] Vnvjeep:
Hot damn... you were right. Rogue Recovery is the thing that did it! I orinally stuck with the Solarnz recovery, followed the same steps, and for some reason it just doesn't seem to apply that radio update right. Crazy. Thanks alot!