yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] blkr00t:
I'll give that a shot now....I've had my Xoom since the first week that they were out and have been rooted and flashing since shortly thereafter so I'm not too terribly green with this stuff.

Thanks for your willingness to help.

---------- Post added at 04:12 AM ---------- Previous post was at 04:02 AM ----------

EDIT: -- Bootloop again...Charging light stays on the entire time. Will flash back to 128 until I figure this out.
[Xoom Android Development] brittoking:
Quick back ground-I just did a full wipe and factory reset before flashing build 130#..................

I've flashed build 132 today (and all of your teams builds for that matter!) But immediately had non stop fc's from about 10 random apps? So I left the Xoom be for about 30 min to settle. Came back and the power button wouldn't respond the first few presses, when I got the Xoom turned on it was non stop stutters and non responsive screen, apps, and system buttons as well. like I said this isn't my first day flashing, so I redownloaded 132# and reflashed everything and even fixed permissions in bx flashing the "new" 132# I downloaded. This time the Xoom booted fine, no Fc's BUT still completely unresponsive all around, stutter bx screen transitions and even froze up so that certain home screens would just be completely blank for mins at a time. Sorry for the lengthy post, and I'm IN NO WAY COMPLAINING! LOL! I PROMISE! I just happened to see your post asking for any feedback, problems, and thought I'd throw out my list. I've NEVER had any problems or issues with EOS builds so I'm really just looking for any help you can offer or suggestions sir. Thank you, please forgive my ramblings.
[Xoom Android Development] kcrudup:
No, it's ok- complaints are what I need right now.

I have an idea what it might be for you and the guy bootlooping . I'll try and get it in tonight for tomorrow.
[Xoom Android Development] brittoking:
As usual.....awesome.
[Xoom Android Development] Droidem:
I don't have any running. But ill try once more with the experimental update. I'm thinking it was just a bad download or that the experimental fiction isn't working properly. If I keep on getting the same system crash ill download the full 132. Will update in 30 minutes after everything is all said and done.

Sent from my Team EOS JB Xoom

OK so I might have downloaded a bad update. Since I'm in Afghanistan ill stuck to downloading the full updates. Rather not loose my only internet connection to a bad download. Too bad, I was looking toward to being able to download a portion of the code to update my xoom to the nightlies.
[Xoom Android Development] apollyon0810:
Man, you should always check an MD5 in a combat zone. I was in Iraq for 15 months. Not sure how Afghanistan is, but everything in Iraq was a microwave WAN with satellite terminal backbone. Terrible... terrible terrible... internet connections. Perhaps shy away from the incremental updates?
[Xoom Android Development] paulfm:
Same problem here. I have downloaded and installed 132 three times but I can't get the unit to boot. Stuck at the big M! Back to 128 and all is well.

Keep up the good work EOS, you keep building and I'l keep installing! I really enjoy the updates, even with the little quirks:o.
[Xoom Android Development] bigrushdog:
No the lag is there. I was trying to get away with it for at least a few more days :p . The lag is caused by the process taking time to populate the app dialog. Its been my plan to move that process off the ui thread so the user wont experience that lag. Btw, its hardly noticable on nexus 7 :p .And I haven't even looked at any sorting. Damn I can't get nothing past you guys!
[Xoom Android Development] bigrushdog:
I wouldn't mess with incremental updates. Just me personally. In the Sandbox updating your roms. THAT is some extreme Androiding! You just eliminated EVERYBODY'S excuse for fail! Epic.:highfive:
[Xoom Android Development] Droidem:
yeah I guess i'll have to start checking the MD5. I wonder if goo manager has a function for that or if i need to use an app for that.

Thanks for the :highfive: Bdog. Means a lot coming from you. But yes I will shy away from the incremental updates from now on and try them when I get back.
[Xoom Android Development] thingnblah:
Incremental updates
[Xoom Android Development] Mjamocha:
I've used the incremental updates with no issues at all. I actually prefer them to installing the next nightlys full ROM. They are smaller in size and I do not have to flash a gapp pack with it. But that's just my humble opinion. Don't be so scared. It's ok to step outside the protective bubble Lol. Make a bu, if you are not satisfied with the incremental update, restore ur bu, and flash the next full ROM.
[Xoom Android Development] kcrudup:
Can those of you who are stuck on the Moto Logo "fastboot flash boot" this image and tell me if it works for you?

---------- Post added at 12:04 PM ---------- Previous post was at 11:55 AM ----------

Ya know?! More inspiration for me to get my isht right (hell, I don't want you distracted by anything when you've got the Taliban gunning for you, much less having you have a crashing Xoom on the back of your mind!)
[Xoom Android Development] sovereign_313:
Hmmm. I wonder how hard it would be to hack the Google voice commands to open haywire or or the Google voice app when I say "text so and so hi" instead of being told off with a gut wrenching "this device can't do all that fun stuff"...

Sovereign
[Xoom Android Development] bigdave240:
So, to get Facebook working again I had to restore from my old 128 then I did a factory reset and upgraded to 130 and still works so far. Will go to 132 now and see if it breaks it again.still not sure it was the ROM or if it is some app messing it up. Have only installed tibu so far.

Edit: going to 132 broke the browser again. In Facebook the chat window won't load, just keeps saying Loading. Also no

Noticed that logins don't stick, had to log in to this site each time I closed the browser and came back even though I hit remember me check box.. back on 130 now and all is good.
[Xoom Android Development] kevdliu:
pretty difficult since we don't have the source for google now. but there might be some way to make google now think that this is a phone
[Xoom Android Development] kcrudup:
It doesn't matter- if my hunch is correct, you'll boot- if it doesn't then I have another boot.img I'd like you to try.

I'm pretty sure I know which commit I've reverted that's causing y'all fits- but 't want to throw away the entire thing 'cause it's otherwise beneficial, so I've just changed the part that I think is the issue.

So, please let me know ASAP. Thanks!

---------- Post added at 04:50 PM ---------- Previous post was at 04:48 PM ----------

Crap- now that I think about it, yeah, flash it afterwards- but you should already have 132 (or whichever nightly has you stuck) flashed to it first (else you won't have the "Stuck on M" issue anyway, right?).
[Xoom Android Development] REHolt218:
The Weatherbug elite widget is also broken with 132. It just continues to say "Loading...".

I can't be certain because I didn't use it much today, but I thought it was working this morning. The tray info was working until I rebooted due to installation of twarp 2.2.2. Is there some way that twarp recovery could have caused it to break?
[Xoom Android Development] paulfm:
Ok, I used the command fastboot boot boot.img (i shortened the name of the file). The process went without errors. I rebooted but still stuck at the M. Did I do this properly? If so please feel free to post another file for me to try.
[Xoom Android Development] dboftlp:
goo.im does an MD5 checksum when it completes a download I believe.

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] kcrudup:
OK- charge light stayed on, right?

Anyway, good to know. Sorry to use you as a Guinea pig, but there's some combination of Tegra2 or build date or part buildout that causes non-booting in some Xooms.

Please try this image now. Thanks (and be sure to keep your charger plugged in).

You only have to flash this in, not the Nightly all over.
[Xoom Android Development] paulfm:
Yes - charge light stays on.

Same results with new file, still stuck on M
[Xoom Android Development] kcrudup:
Urrrgh ... OK, yet another try.
[Xoom Android Development] paulfm:
Sorry, not luck... I'm willing to keep trying if you are.
[Xoom Android Development] paris1129:
Is anyone else having an issue with the stock android browser? It used to remember login info for websites but now I have to log in over and over again. Its no linger saving or accessing the cookies. This has been going on for me for a few days. It started with just one website but now all my regulars are making me log in all the time.
[Xoom Android Development] kcrudup:
You're damned right I am! Try that one (and what are we up to now, take what ... 3? :))
[Xoom Android Development] paulfm:
We're getting closer ( I think). I get past the M and see the Team EOS splash screen. Then it goes on to the spinning expanding/contacting animation. It seems to stay there forever, not locked up, the animation continues. Also the charge light goes out once I get past the M. I hard reset (vol up - Pwr) with the same results.

Hold on - Spoke to soon, after about 5 minutes I am now booting up.

Well it was the longest reboot I have ever seen but I am running 132 :) Nice job Kenny!
[Xoom Android Development] kcrudup:
Great! That's all I'd really needed it to do, but dammmmm ... it! OK, so there's a commit that was reverted a while back by SolarNZ as some devices had your issue. It only changed three things, and between the previous three tries I tried reverting just each change (they're not really interconnected). The fact that it worked for you means I know what the issue is, but for the sake of the ROM, can you try one or two other boot.img files for me, please?

That's 'cause you're running my personal "init.stingray.rc", which runs a command that scans the Flash drive and reclaims Flash blocks so that the EMMC is more efficient (now that we're using "Trim" commands on the Userdata filesystem, this is important). I'd eventually like to make this a standard part of the Team EOS ROM, but we'll need to figure out a way to reliably ensure it only runs once, then every 5/10 reboots after that.
[Xoom Android Development] paulfm:
Sounds good! I have about another hour and a half to give you before bedtime. I'm glad that I can help.
[Xoom Android Development] kevdliu:
Maybe create a log file that gets updated with init.d script to keep count
[Xoom Android Development] kcrudup:
OK, tell me if this boots. If so, I know exactly what the issue is- but what stumps the hell outta me is why it affects some devices, and not others.

BTW- when did you buy your Xoom, Paul?

---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------

BTW, I'm really just curious if you get past the charging light, as that lets me know the device fully brought up the kernel and has started the Android init phase.
[Xoom Android Development] paulfm:
Fastboot failed:

sending 'boot' <4482 KB>...

FAILED (remote: (00120000))

finished. total time: 0.297s

Screen on Xoom - Failed to process command error (0x120000)

I was at the Verizon store on kickoff day to buy my Xoom.
[Xoom Android Development] kcrudup:
Try it again- that's a local issue. MD5Sum on that image is 07479ac269be73e387d642695389803d .
[Xoom Android Development] paulfm:
After my 7 minute boot, I am good to go again:D
[Xoom Android Development] kcrudup:
!

Thank you for indulging me- your time means that a proper fix will go into tonight's run and should now fix the issue for everyone!

(Can you do me one last favor, though? Reboot (I know, 7 mins!), then do an "adb shell dmesg" and PM me the first 20-30 lines? I'm trying to see if there's anything "special" about your boot command-line and/or your system specs. It doesn't have to be tonight. Thanks!)
[Xoom Android Development] paulfm:
PM sent - Have a great night. Thanks again for all you do for the team.
[Xoom Android Development] dweezle:
Not knowing what is ROM related and what isn't, I figure that I'll post the anomalies that I am getting on rev. 132, just in case they are relevant issues. 1.) I installed a boot animation and the Xoom behaved as if it wasn't rooted. Instead of the new boot animation working when installed in system/data (which is where i think that it goes when rooted), I had to put it into the data/local folder before it would install. 2.) Netflix will only play the top row of "continue watching" videos. I am not able to play by browsing to a title and clicking on it.

Thanks for all your work on turning out a truly spectacular ROM for Xoom.
[Xoom Android Development] LesismoreTN:
Kenny, I don't know how to do it. YOU ARE AMAZING! I appreciate you and all this work.

Paul. Thanks for being the guinea pig!
[Xoom Android Development] cantos:
Anyone else seeing issues with the Netflix app on nightly 132? It loads up and will log in and take you to the main screen. If you click on any of the shows it's supposed to pop up a box with the episode list and a button to add the show to your instant queue. I've tried this on two separate tablets running 132 and all I get is a blank dialog box. Netflix is useless at this point since it won't do anything. Thoughts?

---------- Post added at 09:22 AM ---------- Previous post was at 08:58 AM ----------

Apparently I should have read your post a bit closer since you're experiencing the exact same issue I am with Netflix...
[Xoom Android Development] Asphyx:
Just because we may be thoroughly stupid doesn't mean we can't be stupidly thorough as well! LOL

I have seen similar issues but not with NetFlix.(EDIT: I don't use that app so I can confirm what you see at all)

There does seem to be an issue displaying certain kinds of contents where you get blank space (Mybe white Text on white BG?) that I have seen in one of my newspaper apps (NY Post) since upgrading to 132.

I am going to try and see if a new theme might solve that issue and who knowsd it could be related to what others have seen with the bad Txt/BG colors of some launcher widget picker lists.
[Xoom Android Development] bigdave240:
Similar to what i had with facebook. The chat box that pops up to show who is online would popup but not finish loading. Also any site that hat the login info stored had lost that info and would not store it again. I had to go back to 130 and am hoping its fixed in the next release. It almost seemed like something in the environment lost a path somehow.
[Xoom Android Development] bigrushdog:
Well I fixed it. Mostly. More like a cheat really. Now that issue is properly "rationalized" :D:confused:
[Xoom Android Development] freeky1:
Since upgrading to 132, I have had issues with scrolling in several apps, including Dolphin, Facebook, and Tapatalk. Apps freeze, then after a few seconds the box pops up asking if I want to wait or close.
[Xoom Android Development] Asphyx:
Thanks but it really wasn't that big a deal since it is in a section you go once and pretty much set and forget! But thanks for the attention on it dude you guys are so quick with these things!
[Xoom Android Development] bigrushdog:
I knew about it and it bugged me. It was on the fix list anyway. You're keen observation skills just bumped it up a bit. Nah for real I needed to clean up all that code anyway. The action target features now implement a most elegant abstract class. It's in gerrit. You should see it. Its clean. As for the other xoom issues, I don't know. I pretty much just do feature development on the project as a whole now.
[Xoom Android Development] Asphyx:
I just chalked it all up to being caught in between the long press and then subsequent Ring support.

Do you know of any themes that are JB compat I can try? All the ones in chooser say not compatible.
[Xoom Android Development] bigrushdog:
I'm getting the same thing on the market. Why? Who knows? So I nandroided back to ics and grabbed all my themes then restored from tb. Cobalt, Simple Swagger, and PCB all work fine that way.
[Xoom Android Development] bigrushdog:
Regarding features, any ideas. I know I gotta do show/hide system bar/navbar. And I gotta do user defined SMS/voice before the umts guys form a lynch mob. Maybe lock ring targets? Give me some original ideas. Not just "oh abcd team has this or that" :angel:
[Xoom Android Development] farmsatguy:
Just curious if anyone who uses Google Play Magazines is having any issues with it? I can open the app, see my magazine covers for each one but when I click on one, it starts by opening the magazine cover and just stalls out there with a spinning circle...

I tried the usual of clearing the apps cache and data, uninstalling and reinstalling, rebooting, etc. Just stalls out no matter what I do. I grabbed my wife's Xoom just to make sure there wasn't an issue on the server side and everything worked fine. But, she's on the last ICS nightly - hadn't moved her over to JB yet.

FWIW, I tried a couple different magazines from XBOX and one from PlayStation, no luck from any of em on nightly 132. I could revert back to 128 to see if they open correctly there, just curious if anyone else is having issues. I saw recent posts about Netflix and Facebook issues, wondered if they're all linked somehow...

BTW, not complaining, I'm always glad to help troubleshoot any bugs if I can and this may not even be a rom issue. Y'all folks in Team EOS are awesome, wish I had some some good and original ideas for ya BRD, been following you since got my Xoom 14 months ago!
[Xoom Android Development] thingnblah:
Any chance we could have the option of showing toggles in notification area without having to hit it twice???
[Xoom Android Development] bigrushdog:
Possibly. As long as it doesn't mess with notifications I don't see why not. Maybe even have toggles on the systembar itself?
[Xoom Android Development] rob62551:
I sure would love to see the return of customizing the softkeys icons! Have gathered a large collection of softkey icons...need to put them to use! :laugh:

Thanks.
[Xoom Android Development] dweezle:
I went back to rev.130 and problem with Netflix did not exist in that version.
[Xoom Android Development] dboftlp:
I can confirm this behavior. Tried clearing app cache & app data to no avail. Netflix is teh died...

Swyped from my GNex running TeamEOS 3 nightlies.

---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------

Testing this "theory"... Mwahahaha!

I need my Netfix. (see what I did there? yea, that just happened.)

I'm rockin EOS 3 nightlies on my LTE Xoom.

---------- Post added 26th August 2012 at 12:12 AM ---------- Previous post was 25th August 2012 at 11:55 PM ----------

fml, Netflix works on 130, not 132... Staying put on 130 until further notice. Let me know if devs need debuggers (yes on Stingray too).

Swyped from my GNex running TeamEOS 3 nightlies.
[Xoom Android Development] freeky1:
My Netflix is working fine on 132.
[Xoom Android Development] REHolt218:
Mine is not. Playing a movie works fine, but playing a TV show does not. The screen which allows selection of episodes does not function.
[Xoom Android Development] Mjamocha:
Hows about, current weather on navbar next to the clock. Options toggle on/off in status bar menu.
[Xoom Android Development] bigdave240:
a lot of the issues that I have seen seem to have a common thing, a popup that won't load? for me it was the chat box in Facebook that would popup but not load the names and just hang. also for me it was the fact that the browser lost all of the saved logins so i had to log into everything each time i went to a website.

---------- Post added at 08:31 AM ---------- Previous post was at 07:41 AM ----------

Flashed to 133 and the logins are in tact but still have the problem of popups that dont load so cant use facebook. I assume there will be other related similar issues. Going back to 130.
[Xoom Android Development] REHolt218:
Netflix still has the same problem as well.
[Xoom Android Development] rob62551:
Ditto on the Netflix.:(
[Xoom Android Development] SamuriHL:
Has anyone with netflix issues posted up some logs for the devs to look at?
[Xoom Android Development] Asphyx:
Thanks I'll try that....

Only feature I am dying to see at this point is ability to set col/rows in the stock launcher. I find 3rd party launchers to be less smooth than the stock and I really don't need all the other bells and whistles those launchers provide other than maybe resizable Widgets.

But I'm guessing those are low priority for you guys considering how many launchers are available out there.

---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------

I don't think it is an error being thrown on those content items.

I really think it is a case of bad text/bg colorizing that hides the content. That wouldn't throw an error in the logcat.

I seen similar behavior with many custon launcher's widget and app listings as well. Black text on Black BG

Which is why I was trying to find a theme that is JB compat so I could load it and see if that solved the problem.

Unfortunatly I was never big on Theming my unit and don't have any in TBU so I have to try the ICS nandroid (if I have one) and try that.
[Xoom Android Development] SamuriHL:
Yea, I don't theme, either. That's an interesting theory though. Looking forward to seeing if that's what the problem ends up being.
[Xoom Android Development] rob62551:
I went back to build 130. I thought about an email I received from Lookout regarding a survey. On build 132 & 133 I could not submit the survey.

I would see the options to chose my response but nothing would take.

On build 130 no problem with survey.

As BigDave does, I too wonder if the Netflix issue is correlated with this Lookout survey in that pop ups are not working.

Just thinking...also logcat did NOT show anything when I accessed Netflix or the survey while on builds 132 & 133.
[Xoom Android Development] smiznith:
Battery Life

So I have decided to wipe my xoom and see if this kills any apps that are killing my battery. looks like it has not worked. can anyone get 2-3 days of idle on their xoom now? my other xoom that is completely stock ICS gets 3 days easy with use and idle, but my rooted one only gets about 15hrs of just idle. am i crazy?
[Xoom Android Development] bigdave240:
Out of curiosity what are the two xooms? Both 4g or wifi or one of each? My friend has a wifi stock on JB and it goes for days but my 4g may go for 24 hours at the most. But it has always been a battery hog since the radio was upgraded to 4g. I think it was poorly designed and rushed to delivery to satisfy a verizon promise.
[Xoom Android Development] paulfm:
I agree, I could get 2-3 days on my Xoom before the 4G upgrade. Now I charge every 24 hours, usually around 40 - 50% battery left.

That's good enough for me though. Especially since my battery is starting to get to the later end of it's performance life. 2 years is about it for these batteries and I purchased on opening day. I can't complain though, with the help of these EOS roms; my Xoom runs better than new.
[Xoom Android Development] dweezle:
:D

Besides the Netflix issue, I am unable to select "BUY" when trying to buy an app. on Google play. The button appears, but pressing does nothing. Similar to what happens when I press the arrow trying to play some Netflix videos-

On rev.133. I'm going to assume that 132 is the same, but you know what they say about ass_u_me. ;)
[Xoom Android Development] cantos:
Are you guys using something like SetCPU to drop the clock speed during screen off etc? I can get about 3 days of standby with the radio on using this method, and upwards of 15 days in airplane mode of course.
[Xoom Android Development] rob62551:
In this case you assume correctly ;)
[Xoom Android Development] thingnblah:
I would prefer it just in notifications, looks a little cleaner IMO

---------- Post added at 03:04 PM ---------- Previous post was at 02:58 PM ----------

Beautiful Widgets will do that if you don't mind having a weather widget.