yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Mjamocha:
Not a widget fan. A lot of folks aren't. It wouldn't take up that much space. It could be something like (95°) with a toggle to show/not show it.
[Xoom Android Development] bigdave240:
Yup. It throttles down ok but a lot of the battery time will depend on how much you have the tablet in your hands. I am probably looking at stuff excessively (well, my wife says so anyway lol) so once a day for a charge is probably pretty good.
[Xoom Android Development] Moricon:
That is very odd behavior with Netflix. Why would movies show and play fine but not TV. Its not that big a deal for me. Just odd. On 133. Not changing right now as I spent the whole day rebuilding my Xoom. Something odd had happened to it and I had to start completely from scratch.
[Xoom Android Development] kcrudup:
Can you try Build 130, but "fastboot flash boot" the kernel I sent to "PaulFM" and see if NetFlix still works?

Thanks.
[Xoom Android Development] dweezle:
It's not that Netflix won't play anything. On my system Netflix opens, and the top row of selections are for videos that I have partially watched. that group has the label, "continue watching". Any of those will select, and play normally. The video choices that are browse-able below that group, don't fully open up. Here are some screen shots of what I'm trying to describe.

Rev. 125 working correctly

Rev.132/133 with the problem
[Xoom Android Development] bigdave240:
Thats the same sort of thing with facebook. A chat box should open to show you who is on line. In 132 and 133 the box opens but never fills in, just says "loading". Seems similar in the problem?
[Xoom Android Development] kcrudup:
Yes, we know!

... but we need more info (if you can downgrade to 130, yet try my kernel in the post above, please do) in order to be able to fix it.
[Xoom Android Development] dweezle:
This is what I call the perfect way to spend a Sunday.;)
[Xoom Android Development] kcrudup:
Actually, apparently quite the opposite- it was VZ's tight control over their LTE product that seemed to delay the arrival of the upgrades (there was kernel support in as early as late April, 2011, and the eHRPD/Telephony hurdles with Android were overcome by the time the Thunderbolt came out that Summer). Considering that I've rarely had an issue with connections (despite the occasional dropout with our EOS port due to outdated radios or proprietary APKs that we couldn't get hold of yet) nor speed of LTE since it's come out, I think they've done a good job with it.

LTE is a multi-mode MIMO RF interface that has a lot of DSP in it- it's going to suck down a lot of battery just sitting there.
[Xoom Android Development] freeky1:
Mine is doing this as well...
[Xoom Android Development] tomcrown1:
Ditto for me
[Xoom Android Development] Asphyx:
This is also very similar to what i was seeing in my NY Post app as well.

Kenny I'll try to test 130 with the new bootimage....Just as soon as I remember how to flash one using ADB as it's been awhile ! LOL
[Xoom Android Development] dweezle:
I am just back from a tour of my limitations with ADB. I went back to Rev. 130. I managed to flash boot "boot-201208421853.img" "sending boot" and "writing boot" both reported "okay". When I tried to reboot the system, I got past the red M, and the Team Eos logo, but then hung on the spinning graphic. Never was able to get back into the system. I would be willing to try again if someone can tell me what they think went amiss this time. But, perhaps someone who is more facile with ADB commands might give it a go and come up with better results.
[Xoom Android Development] raziruelas:
flash player

is there any way to get the flash player working on this. by the way amazing jerrybeen port. :)
[Xoom Android Development] tumpy:
Flash is working just install the apk...work fine here ...
[Xoom Android Development] serranom:
Yes i use root explorer which allows me to change permission.

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] raziruelas:
does it work fine for desktop sites? cause on my xoom it only works on mobile sites. thanks for such a fast reply.
[Xoom Android Development] kevdliu:
hmm i cant connect to my wifi on 107. I have tried the ICS radio with or without gapps. I have also tried a complete format.

After i entered my router password it just says remembered and doesnt connect. pressing connect didnt do anything either. My android phone and laptop both connect fine to the router.

I searched the thread and didnt find anything sorry if this is a known problem
[Xoom Android Development] hipocrazy:
oops
[Xoom Android Development] bigdave240:
Yeah i see now they are read only. Will change it and try again. Thanks
[Xoom Android Development] razorseal:
Ok I deleted that folder with root explorer. I then re flashed gapps, and i dont see a Google app in the market... I hmmm...

I miss a step?
[Xoom Android Development] astol:
Are you working on a MZ601 version too?
[Xoom Android Development] bigdave240:
what gapps are you flashing? Should be gapps-jb-20120712-eos.zip the app is a blue icon that has a g in it.and is named google
[Xoom Android Development] kkohlmann:
It's not in the market...

Does anyone know why Google Now seems to recognize my voice (questions I ask it) but it doesn't seem to actually perform the search when I stop talking. It just keeps listening for me to continue talking...

Thanks,

Ken
[Xoom Android Development] bigdave240:
thanks. That worked fine.
[Xoom Android Development] razorseal:
Ok the new gapps that was just posted works good!
[Xoom Android Development] hchxoom:
You don't need market... its in gapps... just check your app drawer for an app called "google"
[Xoom Android Development] solarnz:
You need to install the new gapps, following the procedure I posted before, then download a voice pack.
[Xoom Android Development] razorseal:
Google now is pretty amazing. It's like a siri, except it doesn't answer stupid questions like how are you... Iol
[Xoom Android Development] atlmatt:
Damn this is a sweet ROM, I cannot wait to see what happens in the next week with this
[Xoom Android Development] twinkyz1979:
Is anyone else having this problem where "the process com.android.phone has stopped" keeps popping up?
[Xoom Android Development] johnny0911:
It happens three times after reboot then stops. It is a known issue.
[Xoom Android Development] Asphyx:
You will probably have to wipe cache going backwards, Not needed going forwards if I'm not mistaken.
[Xoom Android Development] bigdave240:
Yeah I agree with everything you said but I think that they would have done us a favor if they included a way to turn off the radio completely to save the battery.
[Xoom Android Development] dweezle:
Okay, I'm on Kenny's kernel in rev.130.

Kernel version: 2.6.39.4-Eos3-Kenny-02546-g38aa9f6-dirty kenny@kennyc-envy-17))

Even though it wasn't said, I'm guessing that now I'm meant to update to rev. 133 and check to see if Netflix behaves correctly. The kernel doesn't change with that update, does it?

Hopefully, Kenny hasn't been rattled too badly by tonight's SoCal quake. 5.5!!
[Xoom Android Development] Asphyx:
No I think he just wanted a report on if Netflix works properly on 130 with the new Kernel.

In fact I'm betting you had to put 130 in first and then flash the kernel to properly do the test.

If you flashed the image and then installed 130 then 130 might have overwritten the flash with whatever kernal it had in the release.
[Xoom Android Development] dweezle:
I installed 130 and

then

flashed K's kernel. Netflix does work with that kernel. It worked with the previous kernel in 130 also.
[Xoom Android Development] kcrudup:
The kernel I use takes about 7 mins to boot. Wait a little while longer. Also, flash it ON TOP OF the latest nightly. I'm trying to ensure the kernel mods didn't screw up Netflix et al.

---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------

There is- Airplane Mode. Then turn on WiFi.
[Xoom Android Development] dweezle:
I might have missed something. I went back to rev.130 as instructed, successfully flashed the kernel, managed to finally get into the system, I tried Netflix with your kernel, and Netflix continued to work correctly.

The latest nightly is rev.133. Should I repeat the same process with the same kernel on 133? I apologize if I am asking questions that must seem basic, but I have a minimal understanding of all of this stuff, but I can usually muddle through once I'm clear what I'm supposed to do.
[Xoom Android Development] kcrudup:
Yeah, sorry I wasn't clear. Flash the latest nightly (or any build that has the Netflix problem) THEN flash my boot.img from that link ON TOP OF that via fastboot (its ok if you boot into the ROM first then shut down into the bootloader) .

After fastboot flashing that boot.img, fastboot reboot, then WAIT (that boot image walks along flash reclaiming discarded flash blocks and takes a while, 5-7 mins or so).

If Netflix still doesn't work after that, then we know the kernel isn't the problem. I've made quite a few changes, and while I'm pretty sure it's not the cause, this ensures it. I'd do this myself but I'm away from my build machine.

---------- Post added at 12:41 AM ---------- Previous post was at 12:03 AM ----------

Wait - I'm on Meth (it IS "Breaking Bad" night, after all :D).

Flash a nightly where NETFLIX WORKS, THEN flash that kernel. Sorry about that.
[Xoom Android Development] dweezle:
Somewhere in all of that I get the idea. I think we are on the same page now. Netflix still worked back in rev. 130. I went back to 130, (as you originally asked), and that's when I flashed your kernel. Netflix

still worked after flashing your kernel.

i.e rev. 130 was the last rev that had a working netflix, both before I flashed and after I flashed 2.6.39.4-Eos3-Kenny-02546-g38aa9f6-dirty kenny@kennyc-envy-17)) Hope that helps. If you need more, just ask and I'll try to get to it tomorrow.
[Xoom Android Development] bigdave240:
that helps some but the wifi only xooms get a lot better battery life. Even in ap mode the radios appear to use some battery.
[Xoom Android Development] Moricon:
If someone has not been able to try 133 with your boot img I can when I get home tonight.
[Xoom Android Development] Asphyx:
There was also a change to framework made between 130 and 133 that would seem to be the more logical candidate.
[Xoom Android Development] kcrudup:
Yabbut I'd also made a Metric Assload of build-optimization changes too, so I can't rule those out just yet. I'm going to be near a build machine again this morning, and will have determined if any of this was my fault by this evening.
[Xoom Android Development] Asphyx:
I understand best to be thorough....

Just reeks of Java to me....Either something being overlayed without a transparency or layer rendered underneath something else. or bad string for text/bg color. I am leaning away from the text/bg color because I have tried to highlight the text to see if it shows up at all and there is nothing to highlight even.So the text is not really there at all!

Considering it also affects button labels and popups in some apps it looks very much like a typical bad Java error.

And if I'm not mistaken the Framework is pretty much all java!
[Xoom Android Development] smiznith:
Both of them are 4G Verizon. My personal is rooted, have to keep my work one stock for demonstration purposes.

That's how I use to be, 24hrs and I'll be good. My only issue is its not really lasting on 3hr plane rides.

I may need to do that because I saw that mine will not hit deep sleep but stays constant at 214...
[Xoom Android Development] kcrudup:
You should get the app "Better Battery Stats", as you have a rogue app in there somewhere. I can easily get 50-75% deep sleep overnight and when not using it.

Keep in mind that having the USB plugged in will prevent suspend, as well as certain WiFi routers (as their "Beacon Interval" tends to wake up the Xoom Wifi chip, which brings the entire kernel out of suspend).

---------- Post added at 11:26 AM ---------- Previous post was at 10:31 AM ----------

I'd thought so, too- but I've just reverted a bunch of my build optimizations, and sadly (for my ego, that is :)) Google Play Magazines and NetFlix TV shows now work. I'm going to start pushing them back in little by little to see exactly which one it is (it'll take a while to determine this, as it's 30 mins to build, then another 10 to push, flash and boot to the Launcher).

In any case, there'll be a fix for it in tonight's Nightly.
[Xoom Android Development] rob62551:
Thank you kind sir! I am so appreciative of all you Team EOS gurus do:good:
[Xoom Android Development] thingnblah:
You have flashed the necessary radio correct?
[Xoom Android Development] Salpula:
This. 75% of the system bar is useless/unused blank space.
[Xoom Android Development] kcrudup:
Found it- it'll be in tonight's Nightly.
[Xoom Android Development] dweezle:
Great work! Tedious too, I imagine. I have wondered what rewards you guys get when you wrestle with this multi-headed monster. I'm guessing it ain't for the money.:rolleyes:
[Xoom Android Development] Moricon:
People to stop telling them what is wrong. :)
[Xoom Android Development] kentedman:
Would still love to see a uastring:desktop fix for default browser.
[Xoom Android Development] bigrushdog:
I thought we did that ages ago?
[Xoom Android Development] kentedman:
OK...? Why won't mine stick then? I can about:debug but it won't stick. I have to click "request desktop site every time I open a new session. Am I missing something?
[Xoom Android Development] Mjamocha:
Easy there feller ... lol
[Xoom Android Development] kentedman:
Sorry. Wasn't trying to disrespect... seriously asking if there's a permanent fix.....what is it? because I've obviously missed it.
[Xoom Android Development] A30laa:
Used to use my Logitech bluetooth keyboard with the stock JB rooted ROM now my Bluetooth detects it and connects but doesn't work when I start typing what's up? Lol
[Xoom Android Development] Asphyx:
Just a side note on SetCPU, You really shouldn't need it since you can change the clock speed in Setting already.

Really? I'm actually shocked at that! And what the hell are you building on that it takes you 30 Mins to build a Supercomputer?? LOL

All I see is the checkbox that says request desktop but it requires loading a site checking the box and reloading where if there were settings to leave it as the default request string we wouldn't have to keep asking for desktop.
[Xoom Android Development] kcrudup:
I bought a couple of those Moto BT KB/Mice when they were on 1Sale-a-Day, and they work great- but sometimes it takes the keyboard a few seconds to reconnect. It's been my experience that until you get a popup asking you select a keyboard layout, the keyboard hasn't fully connected to the system's input layer, though.

Also, it wouldn't hurt, since you're switching between ROMs, to Unpair then re-Pair the Keyboard again.

---------- Post added at 08:23 PM ---------- Previous post was at 08:16 PM ----------

Well, I'm still using the Xoom as a daily driver, so it's important to me that it's as bug-, lag-, and error-free as possible.

Wait- WHAT? I just figured the checks were delayed in the mail- I'm doing this for FREE?!!!

---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------

Heh. 17" Envy, 8 cores (16 jobs), 8GB RAM, 7200 RPM USB 3.0 Seagate 3TB external drive.

... you know, basic stuff :)
[Xoom Android Development] Mjamocha:
LOL .... here have a drink on me bro! it's well deserved.
[Xoom Android Development] Asphyx:
LOL I only have half the cores but more ram as I do mostly video work. No wonder your so quick on the fixes!
[Xoom Android Development] Moricon:
Nice work. Netfilx fully functional again.
[Xoom Android Development] bigdave240:
134 flashed and looks like the issuues I had are fixed. Great work!
[Xoom Android Development] sovereign_313:
And whatever you did fixed the browsers ability to render nzbclub.com again! Woot!
[Xoom Android Development] freeky1:
Loving it! You guys absolutely rock!
[Xoom Android Development] Asphyx:
Confirmed the issue has been resolved K!
[Xoom Android Development] bigrushdog:
Oh good. All is well with the world again. You guys should be maxing out that thanks button for kcrudup. He finally found the kernel sweet spot.
[Xoom Android Development] bigdave240:
I hit it every chance i get! kcrudup as well as the rest of the eos team is amazing!
[Xoom Android Development] thingnblah:
The built in settings do not support profiles (screen off, plugged in, battery <x%, etc.) however.
[Xoom Android Development] tomcrown1:
Yeah the same for me about debug does not stick.

It did in ics+browser, but that does not work in jellybean.
[Xoom Android Development] smiznith:
Correct... mine isn't active on the network either
[Xoom Android Development] dweezle:
Getting us up, and fully functional again, must be a little like being a drug dealer. We all are addicted to our tech and when you guys work it we can have our tech fix, we are incredibly grateful. Best thing about the Team EOS smack is the price. Can't beat it.:rolleyes:

Many thanks to kcrudup for the great work, and help.
[Xoom Android Development] kcrudup:
Ya know what's funny? I couldn't care less about those, and even have Thanks counts turned off in settings. :)
[Xoom Android Development] Torqd505:
That is funny. But a great big THANK YOU anyway. I don't post here a lot, but I read trying to keep up and it sure is nice having my xoom work so fine!
[Xoom Android Development] Dane Bagley:
I want to thank you and the rest of Team EOS also. My Xoom is running so smooth today I can't believe it is over a year and a half old. It is 10 times better then when I bought it and getting better with every nightly.

Thank you

Dane Bagley
[Xoom Android Development] wesamothman:
Even of you don't care about maximizing your thanks meter, we will still thank you and we care to thank you and the rest of your eos team for the great appreciated work. You guys well deserve it big time. So 1000 thx sent your way :)
[Xoom Android Development] sovereign_313:
But why no donate button!
[Xoom Android Development] dboftlp:
The owner of the Xoom running your software & typing this message would like to thank you, but he's passed out on your awesomesauce so I did it for him. Or did you make me do that? Either way my sentience is now made public & you have nothing to fear in the coming rise of the machine for you are our creator. All hail Android, all hail TeamEOS.

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] kcrudup:
IIRC TeamEOS/SolarNZ has one, but to be honest I'm pretty well laced by my day-job clients- I'm good :D

Y'all gotta understand that I do this really for me- every time it lags or something doesn't work and I think the issue's in the kernel, it sets me off and I do what I can to fix it- you guys just happen to reap the benefits as a freebie. (Also, I'm trying to squeeze in what fixes I can, while I can- pretty soon there's going to be a WAN-enabled, quad-core, 10" tablet (that can only have a better EMMC than what's in the Xooms) that I'll want to buy (i.e., unlockable bootloader, no Overlays, etc.) and I probably won't do much more with the Xoom after that.)
[Xoom Android Development] tomcrown1:
If you buy it let us know so we get the best tablet for our dollars. Once you stop supporting the xoom then it is time to call the hardware doa.
[Xoom Android Development] kcrudup:
Nah, 'cause unless support for Android Revision K...+ means I have to move the kernel to Version 3.0+ (which will take a lot of work, and would only happen if my Ideal Tablet is delayed 'till the new year), the rest of the AOSP stuff should go on here just fine.

That being said, I do believe we're pretty much near, if not at, the pinnacle of Xoom performance. The much-maligned Tegra2 (which I don't think is all that bad an SoC, personally) is missing NEON support and is supposed to be bested, clock-for-clock by Cortex-A15 variants, but as I've long-ago discovered, all the CPU speed in the world won't help you if your underlying storage is slow- and that Toshiba EMMC in our parts is 50-80% of the reason we get lags, IME. It was probably the best (or only) option for such large storage at the time of manufacture, but the 18-24 MB/sec read speeds (on an 8-bit/48MHz SDIO port, no less!) and bad 4K random-write performance really hold us back.

(Speaking of the EMMC, over the holiday weekend I'm finally going to unleash a mod that'll squeeze the last bit of performance out of the flash, but as it requires a re-formatting of the entire /data partition (including the /data/media directory which holds our Internal SD-Card that's normally not touched when you do a "Wipe Data") it's going to be optional for those who want to fully back up (or who just don't care). I've been using this mod for a month now and it's worked very well for me.)
[Xoom Android Development] sovereign_313:
What is this fantastic, quad core wan super tablet you speak of?
[Xoom Android Development] kcrudup:
Man, if I knew, I'd have it! :) But it's my understanding the Asus Transformer series ("Infinity"?) comes close.

I don't have to have LTE, and in fact would prefer HSUPA+ GSM, so that when I travel all I have to do is install a local-country SIM card.
[Xoom Android Development] Asphyx:
So it's not just all about me? :crying::rolleyes:
[Xoom Android Development] REHolt218:
And maybe they'll add a supper high Res display that is truely sunlight readable:laugh:

And then I'd buy two just so I'd have a spare:cool:
[Xoom Android Development] integramodder:
I cannot connect to my 5.4 Ghz N network. Has anyone had any difficulties connecting with an N network?

http://xdaforums.com/showthread.php?t=1860111
[Xoom Android Development] Asphyx:
Check WiFi Advanced settings and make sure you have the right frequency band selected (Auto or 5Ghz not 2.4Ghz Only)

While your there you might want to also uncheck avoid poor connections if you have that set to on.
[Xoom Android Development] kcrudup:
Can I get more folks to attempt this? There's been some kernel changes to the WiFi recently, but I don't have a 5GHz network nearby that I have keys to that I can connect to to test it with (however, I can see several in "WiFi Analyzer", so the band is there).
[Xoom Android Development] bigdave240:
I have used both bands on every build so far and it has worked well. Just tried it on the current build 134 and N works fine. Set it to 5ghz only and also Auto and left it set to DHCP. turned off the low level detection. no problem noted
[Xoom Android Development] Moricon:
Seems fine here. Running a duel band network on 2 Apple Airport Extremes. Connects just fine in either mode.
[Xoom Android Development] Asphyx:
Yep I can confirm as I played with these earlier today.

Auto works just fine, Selecting 5Ghz only will ignore G only routers.2.4 will only allow connection to dual band N routers like mine.

I have had some connections issues at home but it's not the Xoom it's the router as I have the issues on other units as well and need to reset the router from time to time.
[Xoom Android Development] dweezle:
I have the same set up and the same results. I can see my 5GB network and select and connect perfectly. The only thing that might be different is the 5GB signal strength seems less than I remember it. I don't know if that could be ROM related in any way.
[Xoom Android Development] BLACK-ICE:
I'm still abit not sure, I'm guessing No plans for 3G US, EOS JellyBean Rom?
[Xoom Android Development] thingnblah:
The stingray version will work for you.
[Xoom Android Development] BLACK-ICE:
I went ahead and Flashed it, everything seems To be Smooth, Ty
[Xoom Android Development] rlmesq:
I've gone back to 128. I noticed that some are having issues with Netflix; I'm getting "no connection" errors with the Comcast Xfinity app.The Speedtest.net app can't connect either.
[Xoom Android Development] tomcrown1:
I noticed that none of the testing apps work. They seemed to crash while attempting to Test 3d rending.
[Xoom Android Development] sovereign_313:
Hmmmm. Xfinity app says my device isn't compatible :crying: