yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bigdave240:
when i looked in the list of apps it no longer shows up there. but it still seems to be installed and so far sites that are flash seem to be working. but haven't tested much on that yet. I need to try some bank logins and see if that is still working.

edit: i just tried some bank logins and they didn't work. i restored a copy of my last flash which was 11.1.115.11 and it then worked just fine. tried a couple of banks, BoA and BB&T.
[Xoom Android Development] runhopskipjump:
Build 107 is smooth but "android media process" seems to be using a good chunk of the cpu resources at times. I keep getting alerts from the Watchdog app about it. CpuSpy also shows that the tablet seems to stay on 1ghz for must of the time and hasn't entered deep sleep at all. I will attempt to paste a logcat, but first i must find a quick tutorial to do so via the pretty LumberJack app.

Xoom 4G + Team EOS JB nightlies = WIN
[Xoom Android Development] tumpy:
flash still work in JB, it won't show up in the play store...

version 11.1.115.12....
[Xoom Android Development] razorseal:
so it's not normal that on 107 no vzw connection is made for me? no 3g, or 4g. nothing. just says no internet conn, and radios are 'unknown'
[Xoom Android Development] billblack:
Mine shows a baseband now. I flashed 107 & radio at same time.
[Xoom Android Development] bigdave240:
i think if you moved directly from stable 2.0 to JB you will have to flash the radios.
[Xoom Android Development] razorseal:
no, i did a factory reset with 107.
[Xoom Android Development] tumpy:
Do you have any backup with working radio?, if you do load it then load 107 ontop of it...
[Xoom Android Development] razorseal:
only 2.0.0 had working radio. you mean load on top of that? (ie update)
[Xoom Android Development] serranom:
I manually installed flash with apk download.

On another note....

In settings everytime I touch storage it crashes. Is everyone having this issue.

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] bigdave240:
do this:

Reboot into Rogue Recovery

-Install the radio update

-REBOOT, and head directly back into recovery

-Install 95 + gapps

-Wipe cache and dalvik

-REBOOT

be sure you are using Rogue Recovery though. the eos one won't flash radios for some reason. here is the link to the radio file

http://goo.im/devs/teameos/radios/imm76l-radios-update.zip
[Xoom Android Development] dcmodder:
Any one else feel like this is the version of android that we've been waiting for? ICS seems like a nightmare compared to how much faster and smoother jb is. As usual I will be using the eos builds and loving it. :-) great work :good:
[Xoom Android Development] REHolt218:
I got into a problem with spontaneous rebooting of my Xoom. It would come back to the security code screen but by the time I entered the code it would reboot again. It could be related to overclocking, since I am set at 1.6 right now; but it has been stable at that on all previous roms. I was forced to restore a backup to recover. Simply re-installing 101 resulted in a bootloop. I even tried re-flashing the radios and doing a full wipe.
[Xoom Android Development] razorseal:
ok i'll try that, but how do i get into rogue recovery? i don't even know what that is. lol... eos one is the goo one? I use the regular cwm one that I can get in with volume down > android recovery... that is the rogue one?

and what's '95' ?

---------- Post added at 12:46 PM ---------- Previous post was at 12:41 PM ----------

hmm ok... this is weird. you guys saw the screenie...

well now it sees a 3g network (no 4g though) I got CDMA_N_03.1A.54P for baseband

not sure how that magically appeared...

---------- Post added at 12:52 PM ---------- Previous post was at 12:46 PM ----------

restarted the xoom, and baseband disappeared again...
[Xoom Android Development] tumpy:
yes.

you should clean all data and load the JB gapps againg..
[Xoom Android Development] bigdave240:
sorry, cut and pasted the instructions from the original post. yeah you have to use the gapps for jb not the 95 one. not sure why it started to work as 3g but with that baseband you won't get 4g. you can try using the recovery you have been using and see if it works. if it doesn't work it will just not work. the rogue recovery is another one you can flash. find it under the rogue section. here is a link to it http://xdaforums.com/showthread.php?t=1235170
[Xoom Android Development] cadiken:
Did you install the reboot menu mod BRD made for the preview version? That was causing my storage to crash. Re-flash ROM and G-Apps with NO mods and see if that works.
[Xoom Android Development] serranom:
Thanks I will do that and see if this works.

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] Droidem:
Make sure your top status bar is showing and press the pencil icon. Then press the x button to delete the unneeded screens OR press the plus button to add.

Sent from my Team EOS JB Xoom
[Xoom Android Development] wesamothman:
I already tired to do this change, it seems there is a way around this. I asked here, waiting for expert review...

http://xdaforums.com/showthread.php?p=29987707
[Xoom Android Development] CIPuyleart:
Got home and connected to WiFi there just fine - so that makes me think it's the WiFi router at work going wonky.

HOWEVER, I got back to work this morning and had "No Internet Connection" again when I woke up my Xoom. Toggling data, wifi, airplane mode, etc all would not bring it back. I had to reboot the tablet to get my connection to come back. Any ideas?
[Xoom Android Development] Asphyx:
Try this it seems to help...

Go to WiFi settings select menu and advanced and uncheck avoid poor connections.
[Xoom Android Development] thingnblah:
Turning mobile data off when you don't need it will definitely help battery life. I don't have a data plan so I leave my xoom in airplane mode and turn wifi on when I need it. Battery is great this way. The alternative would be to flash wingray build if you are never going to use mobile data, I like to keep the option available just in case.
[Xoom Android Development] trevormalachi:
Cause I'm getting terrible battery life compared to ics
[Xoom Android Development] REHolt218:
My guess is it's not the kernel; probably an app misbehaving. I get outstanding battery life on this ROM, as do alot of other folks.
[Xoom Android Development] Moricon:
+1. No battery life issues at all.
[Xoom Android Development] thingnblah:
Different kernels offer different/better governers, different i/o schedulers, and occasionally will allow higher overclocks. I have also noticed a distinct lack of kernels for the xoom as well as the touchpad. Kind of a bummer as there seem to always be an abundance of kernels for android phones, there are already two custom kernels for the EVO LTE.
[Xoom Android Development] freeky1:
Battery life went to crap after going to 124.
[Xoom Android Development] DaPoets:
CPU spy. If deep sleep is an issue the adjust your low end over clock. This fixed it for me. Have not plugged in for days now.
[Xoom Android Development] trevormalachi:
no apps were on it, full wipe and hadn't had a chance to put any on it and just sitting on my desk over the morning dropped to 34% from a full charge

Its just odd that there are no custom kernels saying on all my other devices I've has there have been plenty. Hell on my gnex I've found over a dozen
[Xoom Android Development] Moricon:
That is informative...
[Xoom Android Development] bigdave240:
seems the same on mine still. can you tell if it is going into sleep mode? maybe an app is keeping it up?
[Xoom Android Development] Draxin:
Sounds like the same exact problem that I had when I switched from ICS 2.0 to 98 without flashing the new radios.... for yucks and chuckles have you performed another factory wipe and reflashed everything with the new radios?
[Xoom Android Development] thingnblah:
For everyone having battery issues download CPU spy and see if your device is going into deep sleep. If it is not make sure that you have the latest radios like in the screenshot. Radios can be found here: http://goo.im/devs/teameos/radios. Flash with rogue recovery, people have reported success with TWRP as well.
[Xoom Android Development] trevormalachi:
No I haven't. I just pulled my nan of ics back because I use it way to much during the week to have that bad of battery or have time to tinker. Will probably try again this weekend with the radios
[Xoom Android Development] REHolt218:
I took mine off the charger last night at 10:00pm CST before going to bed. When I got up this morning it was still at 97%. After a full day at work plus all evening playing games (it's know 9:pm CST) kit is at 61%. 24 hours ain't bad.

I think I like this ROM.
[Xoom Android Development] kcrudup:
If you knew how much work I (and others, of course) have put into this kernel you'd understand why. This is my daily driver tablet, and until someone comes out with a 10" with a carrier option that's got a better CPU, more RAM and is a GED, will continue to be so. I've been working nearly daily to squeeze every little bit of performance out of what we have to work with, and have even gone as far as pulling in, sometimes with great effort, from higher-revision kernel sources to get what I want (they've essentially stopped pushing WiFi updates to the 2.6.39 kernel, but we're up to date with the latest, and we now have the 3.0 kernel's flash-driver logic, which means we get better thruput and even longer-lasting flash (due to support of the "DISCARD" command)).

I think a multitude of nearly-copycat kernels looks great on paper, but doesn't really make much difference. In any case, my sources are out there, and if you do improve on something, do feel free to file a patch on it and we'll put it in.

---------- Post added at 07:44 PM ---------- Previous post was at 07:33 PM ----------

Heh. Actually, it is, 'cause I'm seeing it too, and now I have outside confirmation. :)

We've pulled in new LTE support code from that leak that's allegedly supposed to be the official MZ602 JB version from Google/Moto/VZ, and I've noticed that a wakelock associated with the original on-board CDMA radio never seems to expire (so no deep-sleep).

We might have ended up in the same situation as folks who flash ICS/JB w/o flashing the new radio code, with the problem being that we don't have any "new radio code" to flash yet.

I'll probably have to end up reverting some of the LTE support code 'till we get new radios. There weren't any real improvements in the leaked stuff (but I was hoping it'd help some of y'all out there with "no LTE connection after sleep" issues), so it should be OK.
[Xoom Android Development] SamuriHL:
Shouldn't there have been a radio with that leak?
[Xoom Android Development] kcrudup:
There very well might have been- but unfortunately (and I haven't looked today, but will after I post this) we didn't get an update.zip that would contain them, only a /system image.

ETA: just checked over there. According to his screenshot, the CDMA radio is now at "CDMA_N_03.1A.66.PS" but we're only on "CDMA_N_03.1A.65P". Doesn't look like the LTE radio baseband's changed, though.
[Xoom Android Development] SamuriHL:
Interesting. Hopefully you guys can get ahold of it anyway and see if it makes any difference.
[Xoom Android Development] kcrudup:
I've figured it out, and the fix should make it into the nightly.

Turns out it was due to a largely-unnecessary service we'd picked up off that (allegedly) official leaked build called "ConnMO" ; I don't know exactly what it does, but we haven't had it as part of our builds for months (if at all).

I might restore it once we get the new CDMA baseband, if I can figure out exactly what it is and if it provides any benefit.
[Xoom Android Development] Mjamocha:
I might be mistaken, ConnMO.apk and ConnMO.odex are part of the update and has something to do with setting up or wireless.

pulled this as an example :

3f0eee36feb5c071f2d9b0817abd5915 /Downloads/Blur_Version.5.9.905.to.6.7.2233.XT875.Verizon.en.US/patch/system/app/ConnMO.apk.p

568d4186aa83318c50612f758f03a095 /Downloads/Blur_Version.5.9.905.to.6.7.2233.XT875.Verizon.en.US/patch/system/app/ConnMO.odex.p
[Xoom Android Development] sovereign_313:
Thank you. (sincerely).
[Xoom Android Development] Asphyx:
Does this help at all?

http://android.clients.google.com/p...igned-tervigon-JRO03H-from-IMM76.f85d815e.zip
[Xoom Android Development] bigdave240:
I noticed someone complaining about random reboots on xoomforums.com as well. I haven't had one in a couple of days (now on 124) so not sure if it is fixed or just hasn't happened to me lately.
[Xoom Android Development] rob62551:
Jenkins shows build 125. However; can't download. Via web or goomanager.
[Xoom Android Development] serranom:
Saw it uploading this morning but could not download either. :banghead:

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] Draxin:
I had seen that too before I posted. I am 124 now as well, and still have the problem, I had wiped dalv and cache before flashing. It seems the most prevelant when streaming video on netflix or Youtube and I pause it. I havewn't tried crackle yet. If I am watching a video and pause it for more than about 15 seconds or so, the picture becomes stuck, xoom unresponsive to touch, then black screen, reboot. Sometimes I also seems to have a heck of a time waking it up sometimes if it has been sitting idle. I will keep hitting the power button and it is unresponsive, hold power button volume up, and after about 5 seconds, screen lights up with the shutdown menu. Browser also becomes unresponsive alot of times and force closes.

Since it seems to be touch and go of who is having these problems and who isn't, is it possible the recovery used to flash them is the culprit?? I used Rogue touch screen
[Xoom Android Development] Asphyx:
I am about to flash 124 now but I have also seen issues with playing video streaming media such as DLNA sources from my local network.

I can't say for sure if that is due to the radio subsystem or merely an issue with the video decoder.

If I had to make a best guess I would say it's radio and networking related since local (internal storage) media did not seem to have any issues.

The WiFi seems to drop out (which is why I shut off the avoid weak signal checkbox in WiFi) every now and then and thats enough to kill any stream.
[Xoom Android Development] Draxin:
I could see that if it was force closing the apps, but why would it reboot the xoom?
[Xoom Android Development] JCMX:
stingray-cdma

Hi all,

I am confused about the status of the stingray-cdma build. I see it under the eos3/nightlies in goo.im at 20120808-100. I have not flashed it yet. Is this a JB build or still ICS? Which GApps should I flash with it?

Thanks
[Xoom Android Development] sovereign_313:
I was running 98 cdma only before i sent my Xoom in for the 4G/LTE upgrade and it was certainly JB. I flashed that and thr latest gapps (found on gapps on goo under EOS3) and it was be you te full.

Sovereign
[Xoom Android Development] REHolt218:
So, what's wrong with gooim and Jenkins today? Jenkins won't let me download nightly 125. It keeps telling me the file I am looking for is not found and gooim does not even list 125:confused:
[Xoom Android Development] SamuriHL:
124 and just had a random reboot. :( It's been.....well, not overly stable for me on this release. Tapatalk randomly crashes, as well. Yes, I've wiped. No change.
[Xoom Android Development] bigdave240:
actually now that you mention it I have had 2-3 times where it didn't want to wake up and it took several preses on the power button to wake it up. hmmm
[Xoom Android Development] REHolt218:
I have not had any reboot's, but I have had several browser crashes. Everything else seems to run OK for me.
[Xoom Android Development] SamuriHL:
Yea, I don't know what's up with it. Was ok before 124. I'll wait for the next build and if it doesn't fix it I'll factory reset it and start over. Giddyup.
[Xoom Android Development] REHolt218:
Nightly #125 has supposedly compiled successfully but won't download. Hopefully it will solve some of the problems when it becomes available.
[Xoom Android Development] SamuriHL:
that's what I'm hoping for. We'll see.
[Xoom Android Development] kcrudup:
I know what the issue was with random reboots- I've pushed a fix yesterday that will take care of that. Essentially, an optimization I'd picked up from NVidia didn't play well with our kernel, so I've reverted it. Also, a while back I'd turned down the GPU speed to 300MHz (thinking that was part of the issue here) so that's also been reverted back to a default of 400MHz, which should help with rendering video (and games and such).

As far as why it was rebooting (vs. an FC), the GPU hardware was deadlocking waiting on a condition to be settled and because there was a loss of synchronization in the video pipeline, it never occurred. There's a kernel watchdog which wasn't being pinged in time due to the deadlock, so that rebooted the kernel.

But the most surprising revelation for me here is that there's folks discussing our product off-XDA! Where else is this all being discussed, so I can join up and keep an eye on things?
[Xoom Android Development] SamuriHL:
That's great to hear that it's not just me. Thanks!!
[Xoom Android Development] kcrudup:
They are,

I think it's probably some sort of "Connection MOnitoring" SW for QoS (or maybe Carrier IQ! :)). In any case, we've been running fine w/o it for months now.
[Xoom Android Development] ijustintouch:
Does anyone have a mirror for the Jelly Bean gapps? Goo.im is down for maintenance.
[Xoom Android Development] thingnblah:
I in no way meant any disrespect by my comment. It was more a commentary, albeit extremely brief, on the lack of respect this tablet has gotten. It was the first honeycomb tablet and was supposed to get the best support from google as it was meant a development device. The reality is that slabs like the transformer and the galaxy tab got all of the recognition while the xoom sat back in the shadows, even though the physical build quality of those tabs pales in comparison to the xoom. I appreciate all that yourself and the rest of team EOS are doing to keep this great tablet relevant. The only thing I would like to see in the kernel is a wider range of governors, otherwise it is fine as is. The kernel has been updated far more frequently than any other custom kernel I have run on my other devices, not to mention it has been incredibly stable (I had my first random reboot last night since build 101 when I started with EOS 3). So now that i have rambled on forever let me again say thank you for your amazing kernel work and sorry that my comments may have come off as unappreciative.

---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------

Tapatalk, via xda premium app, always force closes for me. The general consensus seems to be that the move to Tapatalk 2 has everything screwed up.
[Xoom Android Development] Draxin:
I had found some dicussion on EOS3 at xoomforums.com, thanks for your work on these ROMS:D
[Xoom Android Development] SamuriHL:
Not for me. It's been perfectly stable until 124.
[Xoom Android Development] Lare2:
Great, because I also experienced the random reboots mentioned earlier, and both of them where while using the YouTube app so it makes sense.
[Xoom Android Development] dweezle:
Hopefully 125 will be up before goo.im closes for their upgrade maintenance.
[Xoom Android Development] kcrudup:
Figures that a major update fixing several issues can't be downloaded :mad:
[Xoom Android Development] wesamothman:
Check here, if 125 is not available here, then goo manager won't find it..

http://goo.im/devs/teameos/roms/eos3/nightlies/stingray
[Xoom Android Development] rob62551:
Not found. Been unavailable since built.

Wish we knew status from goomanager.
[Xoom Android Development] shadowace:
seems to be working fine now and 125 is there....
[Xoom Android Development] SamuriHL:
Confirmed...downloading now myself.
[Xoom Android Development] HefyOrb:
Just finished the download now
[Xoom Android Development] shadowace:
I am having an issue with only getting 3G and not 4G, I had 4G with EOS 2.0 but I only get 3G since build 122 (first one I tried). I updated the radio to imm76l-radios-update, anyone have any other suggestions? I did do a complete factory reset just now before sticking on build 125.
[Xoom Android Development] rob62551:
125 loaded and so far so go! Thanks EOS
[Xoom Android Development] REHolt218:
What recovery did you use to install radios?
[Xoom Android Development] shadowace:
twrp, but i will try to reflash with rogue

And BAM that would do it. Made a backup in twrp, flashed rogue, flashed radio update, rebooted and 4G on boot.

Thanks!
[Xoom Android Development] Mjamocha:
You guys are on Android.gs Geeks

http://www.android.gs/update-sprint-samsung-galaxy-nexus-to-jelly-bean-4-1-team-eos-custom-rom/

The Android Soul

http://www.theandroidsoul.com/transformer-prime-jelly-bean-update-install-eos-nightly-eosteam/

and

OMG! DROID as well.

http://omgdroid.com/team-eos-is-spilling-the-beans/
[Xoom Android Development] kcrudup:
Oh, I know. But believe it or not, the fact that it *is* a GED means we get fewer random little kernels, and the few ones out there are pretty damn good.

Every time I see my tablet lag my I get fired up and do what I can to fix it. I've got stuff waiting in the pipeline that I'm perfecting that should make a big difference, considering the hardware we've got (and the weak point is not so much the Tegra-2 (as everyone believes it to be)).

---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------

Thanks. With such a widespread audience I guess I've got more incentive to hold my sh!t together, huh?

("OMG! Droid"?! ... really?! :) ... and when did XDA start censoring posts?!)
[Xoom Android Development] bigdave240:
You guys are amazing! Not sure i can stand it getting better :eek: siriously, keep up the good work, it is appreciated
[Xoom Android Development] kcrudup:
Oh, I'm sure you will :)

... but you know how after a long day of use, it'll get laggier and laggier? I know the root causes behind that (it's related to memory management, I've already made an effort to reduce latency and increase bandwidth on the EMMC, a known bottleneck) and am doing what I can to reduce it, but as we're on a 2.6 kernel still (and I wish I had the time to port it over to 3.0+) there's only so much I can do w/o reworking into a higher kernel level the memory-management subsystem (with no guarantees we'll get a win out of it).

But I prod ahead, all for my own good- and the end-users benefit by extension!
[Xoom Android Development] bigdave240:
Haha yes i will
[Xoom Android Development] Mjamocha:
Is it lonley at the top?! That's right, hold it down. Thanks for all of the hard work, time and effort y'all put forth.

I love the ROM and theme'n the sh!t out of the EOS ROM. Hands down EOS is the hardest crew on the XDA streets! :cool:

Any chance of a JB Development Overlay down the pipeline?
[Xoom Android Development] brittoking:
I apologize in advance if this question has been answered (this forum is huge!) But I can't seem to make a widget for google music? Its not in the app drawer either but google play marketplace won't let me install (gives me the option to but then during install states its already installed!). I've tried clearing caches and data, also reflashed ROM with no luck. I have the option to create a google library widget but it force closes when I click on it afterwards. Thanks in advance, I've been on every version of the EOS roms and they are hands down the best out there. Period.
[Xoom Android Development] ijustintouch:
OK, so I'm not sure if its just me not being able to find it, but where is the option to take a screenshot from the power button?
[Xoom Android Development] dweezle:
Try hitting volume down and power Button at the

exact same time

.