yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Taysider:
Adding Screenshot toggle

Is it possible to add a screenshot toggle in the Settings>Interface>Enabled toggles

Great Rom :fingers-crossed:
[Xoom Android Development] Eun-Hjzjined:
Just set a long press action for the task menu key. Thats what I do.
[Xoom Android Development] Taysider:
Hi Do you mean EOS settings> Softkey Settings?

If so I still can't get it to work:confused:
[Xoom Android Development] Dyelon:
Reflash of 135 working better than before but still occasional few second hang and just got a reboot while tablet in standby chilling
[Xoom Android Development] istrait:
Same here... softkey settings just freeze
[Xoom Android Development] Taysider:
Got it, Sundays morning, brain out of gear :D
[Xoom Android Development] Northantrim:
Sorry to ask, but will this ever be back on Goo, and is the latest build still 135?
[Xoom Android Development] xoom68:
They are on Goo for me, and yes 135 is the latest according to the update listings.

http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/

http://jenkins.teameos.org/job/wingray/
[Xoom Android Development] Northantrim:
Ahh yes. So it is. I was looking for 'eos' and not 'teameos' :rolleyes:
[Xoom Android Development] dj_ghosie:
Hi Team,

I have 2 questions looking for answers:

1. Will the gapps be switching to the CM10 version?

2. Is there any team members going to replace their Xoom with TF700?

Cheers!
[Xoom Android Development] Taysider:
Q1. No idea

Q2. No

Happy with my Xoom:highfive:
[Xoom Android Development] runandhide05:
q1 don't flash non eos gapps you are asking got problems .

eos gapps synlinks many things to / data because of the limited space on / system partition

q2 don't no
[Xoom Android Development] TheBlueRaja:
So did you test it? Do you stream media? Because if you didn't or you don't you probably never noticed, yet it is there and it shouldn't happen.
[Xoom Android Development] elsworth1983:
Threads quiet tonight :) things must be looking good :)
[Xoom Android Development] xoom68:
No new builds for over 4 days now....it is what It is I suppose.
[Xoom Android Development] lancemoreland:
They are for me. 135 runs great.
[Xoom Android Development] TheJeeks:
Are there any plans to integrate some themes with the releases?
[Xoom Android Development] runandhide05:
No need, theme chooser is built in, just download your avorit from the market or from the theme chooser app thread and install then go to setting, interface, theme chooser. Apply theme and all set
[Xoom Android Development] Dyelon:
still getting hangs. one every couple hours of use.

btw I really like the soft key long press toggles....the screen shot is implemented great, just like on asus transformer.
[Xoom Android Development] jaymode:
I am also experiencing slowdowns, freezes and reboots while watching videos in the browser on build 135. Had been over clocked but reduced speeds to stock and experienced the same issues.
[Xoom Android Development] DefinityX:
I'll second that there is some definite latency when the screen is off. Is it a CPU dropping off issue? Or just something in the WIFI set up? And the download doesn't cut off, just drops to (in my rough experiments) maybe 10% the "screen on" speed?

Best fix for me so far? Leave the screen on...
[Xoom Android Development] uzi2:
There was a similar issue in the early days of CM9. It was soon fixed in an update. Not sure that the cause was revealed in the thread.

TheBlueRaja will have the answers there.

Swyped from my Xoom
[Xoom Android Development] elsworth1983:
135 is great for me 2 Gf had a hic up with her sims game but that wont bother me that's her problem lol
[Xoom Android Development] RacerX780:
How can you determine if an issue you are having is due to the app or the ROM? (Besides changing ROMS)

I've been having Dolphin for Pad browser close on me while just browsing various websites. I'm trying to narrow it down to certain sites.... but it seems to be very random, but often enough that it's a pain.

Doesn't seem to have problems with other browsers.. and I just installed the Dolphin Beta, which hasn't crashed on me yet.

I've been using the Dolphin Pad browser for some time... so at least since I did a total wipe of my xoom, which was back when the JB nightly first came out. But it's also possible the sites that are causing it to close/crash I never went to until recently... or maybe they changed something on their site that is causing the issue.

I'm on nightly 135... and other then this, I have no other problems. I can't remember if it happened with a previously nightly... I think I was on 132 prior to 135... and 128 before that.

So with 3 potential spots for problems... (website itself, rom, browser) is there any way to narrow down the issue??

Thanks!!!

-R
[Xoom Android Development] Taysider:
While running Dolphin Beta did you uninstall Dolphin browser. This could cause problems as the beta as the new HTML5 engine
[Xoom Android Development] burt_ie:
I am still running 135 and had a few random reboots at the start but it's been fantastic for the last few days with no problems whatsoever. All my problems with seem to have vanished lol :)
[Xoom Android Development] painterceessie:
135 is running great.

From the beginning it's all good.

Thanks again Team EOS:good:
[Xoom Android Development] Taysider:
Same here, the guys are doing a great job
[Xoom Android Development] TheBlueRaja:
Yeah,

It was me that pointed that out too, not 100% sure what the fix was though, IIRC i think they went back to a different set of WiFi drivers. DefinityX, different governors don't seem to alleviate the issue so i suspect its to do with the driver or the ROM.

I've included a graph of me downloading Linuxmint from the UK where i am based.

You will see a nice average of around 3.5mbps with screen on (take my word for it), then it just drops completely when the screen goes off (2 times are shown) then if i put the screen on again it ramps back up almost right away.

Ping times go through the roof too.

My Xoom is about 50cm from my router while im doing this, full signal.
[Xoom Android Development] kuroguy:
I notice the same thing with adownloader, but this has been happening as long as i can remember.
[Xoom Android Development] jonnyhardaker:
Have flashed AwesomeBeats v3 on my Xoom (EOS 3 nightly 135) but it's not showing up on SETTINGS/SOUND/MUSIC EFFECTS, in fact that menu was missing before I installed the standard DSP manager apk.

Once I installed the standard DSP manager apk I reflashed the .zip but still nothing. I can now see SETTINGS/SOUND/MUSIC EFFECTS but my only options are 'MusicFX' (already selected) or 'DSP Manager', 'AwesomeBeats' isn't in that list and I have no separate awesomebeats app.

I've had a search in this thread but can't see a solution. Can anybody help?
[Xoom Android Development] RacerX780:
No, I didn't uninstall Dolphin prior to installing Dolphin Beta.

Haven't really been using the Dolphin Pad today... just been using the beta. So far that hasn't crashed or anything. And I like it, so I'll probably just continue to use that instead of Dolphin Pad and see how it does over the next week or so.
[Xoom Android Development] solarnz:
1.) No.

2.) Not as far as I know.

You're asking for support for a modification that is not supported by this rom... Good luck.
[Xoom Android Development] jaymode:
I believe this may be an application issue where the app does not obtain a wifilock for hi performance. With a regular lock, the WiFi will drop into a power saving mode and reduce transfer speeds, which sounds like what you are experiencing. See this link for more information:

http://emuneee.com/2012/07/android-development-tip-full-power-wifi/
[Xoom Android Development] DefinityX:
Interesting little tweak there... however... (lol, there's always at least one, eh?) I know for me, it happens with Downloading from stock browser or Chrome, using the stock Download manager, etc. It's all stock stuff....So... does this fall back on Google's Cave-o-coders?
[Xoom Android Development] jaymode:
Without looking at the code yet, my guess would be yes. The download manager code is part of the AOSP source so it should be easy to check however I don't have the source for 4.1 downloaded yet.
[Xoom Android Development] jonnyhardaker:
Thanks for your help. I see that many users have got this mod working with EOS3 so assume it must be doable and hoped somebody could point me in the right direction.
[Xoom Android Development] summer_love:
Anyone else getting system ui FCs on 137?
[Xoom Android Development] elsworth1983:
Cheers again Team Eos DL 137 now :D
[Xoom Android Development] okantomi:
Re: tf700, I wish you would...we could use your talent over there!
[Xoom Android Development] alex94kumar:
have you activated the user profiles on JB at all?
[Xoom Android Development] istrait:
My system settings freezes up when I go to the softkey settings and the ring settings.
[Xoom Android Development] elsworth1983:
Just checked on mine what u said and Its fine for me :-\
[Xoom Android Development] deiss:
Flash with 137.

Really more faster than 135 and previous one

Working really good
[Xoom Android Development] mptpro:
"Unfortunately system UI has stopped" error when pressing "Back", "Home, "Recent" softkeys.

I upgraded from n128 to n130 today. Before the upgrade, no problems, immdetiaely after flashing I get the above error. Once the error occurs the Navigation Bar dissapears, then reappers within a few seconds, but when pressing one of the softkeys the error is back.

The function of the keys does not work. In other words, if I press "Home" softkey, I get the error and the Xoom does NOT "go" home. So, once I've booted into my Xoom, opened any app, I'm stuck in that app until I reboot!

I do NOT have the "Softkey custom settings" enabled.

Any help is appreciated.

UPDATE: I went back to n128 and all is fine. No other changes. So, it must be something with n130.
[Xoom Android Development] JT man:
[/COLOR]

I'm having the same problem here...
[Xoom Android Development] TheJeeks:
I also got "Unfortunately system UI has stopped" with 137, I flashed back 135 and order was restored.
[Xoom Android Development] Dyelon:
Flashed 137, everything working great so far!! Whoo!

I love all the home ring designations, a lot of fun

Thanks team eos...I hope us telling you what was going wrong the past couple weeks has been more helpful than annoying .....I really do appreciate the work you do. If you didn't then I'd have a hopelessly outdated tablet....but with this ROM it makes my gfs Asus tf201 look mediocre hah!
[Xoom Android Development] Dyelon:
Hm maybe spoke too soon....just got a reboot while a YouTube video was paused. :(
[Xoom Android Development] Taysider:
Running 137 since yesterday and all going smoothly, you guys are doing fantastic work :)
[Xoom Android Development] Darkman:
Question to TeamEOS

wrong thread sorry...
[Xoom Android Development] jonoathome:
Think I might wait till we have a 100% stable release before I jump from ICS..

Seems from reading through the thread there is one or 2 issues that require ironing out..
[Xoom Android Development] waz675:
Why even bother posting this? Trying to force devs to fix one or two issue that you haven't even mentioned. I've been installing basically every update since the first day teamEOS released this Job ROM. Have only had one small issue (ran slow beginning 'one day) but has been fine for at least 2-3 weeks personally for me.
[Xoom Android Development] elsworth1983:
I agree that post by "jonoathome" is stupid i have been seem as you i was in it from the beginning and only had 1 reboot and that was youtube so all i did was remove the youtube.apk and download it from the playstore and its been fine ever since
[Xoom Android Development] nigeldr:
137 successfully flashed and running well, none of the softkey errors reported earlier happening here.
[Xoom Android Development] Cjunior:
Is just me or every time I flesh the Google apps it delete the camera app
[Xoom Android Development] DevilStrider:
I see we still can't copy a life over 4 gigs.
[Xoom Android Development] draiken:
137 flashed and running fine, just one reboot with flash video paused.

XOOM seems faster and snappier
[Xoom Android Development] nadiros:
If by "life" you mean "file" than no you can't. AFAIK that is the limitations of a FAT32 partition, and not a ROM or device issue.
[Xoom Android Development] TheJeeks:
So, any solution for the softkeys problem on 137?
[Xoom Android Development] summer_love:
Nope, pretty much all I've done is change the clock colour & the quick settings, everything else is stock.
[Xoom Android Development] painterceessie:
I was also from the beginning and I had One problem and that was a game that I played alot with my son,sometimes it was FC.

I can only say Team EOS JB is the best build for my xoom.

It came with honeycomb,that was awful:crying:
[Xoom Android Development] Brandonxcore:
Running the 137 build Is it normal to get around a 3,000 score on quadrant with no overclocking with this rom? It's awesome regardless, lol. I beat the transformer at 1.5ghz, really not sure how I beat a quad core? but anyways, AWESOME! :D

Stock

1.5ghz overclock, still not sure how it's beating a tegra 3 O.o
[Xoom Android Development] jonoathome:
Don't get me wrong, I've been using Team Eos on my xoom from Day Dot..

I've got my xoom running how I like it.. However I'm like most on here and tend to be a flasholic and therefore ever so attracted to the Jelly Bean goodness that Eos has to offer.

However although I'm very tech minded, and more ways than most can resolve the majority of issues.. I was waiting for official stable release before jumping Ship, also there is one or two features missing from Jelly Bean build, I've come accustomed to with ICS, such as the hide status bar thing..

If the issues are really that basic, I may give it a whirl though..

Anyone have a list of the known issues. ?

Thanks..
[Xoom Android Development] Dyelon:
still getting reboots during VPlayer video playback....wah
[Xoom Android Development] waz675:
That's why we nandroid backup and restore if changing a rom series isn't for us. :cyclops:

Known issues kind of strange as we all don't suffer from each/any for the main. I won't try to think back, my chronic pain coupled with our 2 kids both under age of 3 is giving me a headache this morning looking after them. My wife is coming down with it too and I luckily had the same bug apparently but got over it in one day thanks to loading up of stuff like spirulina :silly:

Great phone btw. I have one. 2 devices the same? You'll like JB XOOM methinks heh
[Xoom Android Development] BadFish79:
Ever since flashing JB (earlier this week) from ICS, my notifications menu acts odd. When pulling up the notification window, the clock and everything in the right hand lower corned disappear until I close out the notifications. I don't get a nice little "X" to clear out and of the notifications. I have to swipe them all individually. Is there a setting I'm overlooking that did this, or is it how JB works? I miss the "X" to quickly quickly clear them out.
[Xoom Android Development] nadiros:
Sounds like a bad flash. Did you full wipe coming from ICS?

In JB clear all notifications is there in the same place....looks kinda like a mini staircase I guess, lol
[Xoom Android Development] BadFish79:
I did do a full wipe. I can reflash. I was hoping that going from 135 to 137 would fix it. Odd that that whole corner (clock, WiFi and connection icons) would disappear when opening the notifications.
[Xoom Android Development] scottgti:
I'm pretty sure that is how it is supposed to be. All of that info is then available in the notification area that is opened.
[Xoom Android Development] Taysider:
You're correct that is what the notification bar does
[Xoom Android Development] scottgti:
From the stingray thread-
[Xoom Android Development] NoP_Compiler:
yahoo! I'll do my first upgrade then :) (from v127).

--
[Xoom Android Development] elsworth1983:
just had a look on http://jenkins.teameos.org/view/Tablets/job/wingray/changes and it looks like 138 is on its way soon Thanks Again Team Eos :silly:
[Xoom Android Development] scottgti:
Looks like a few builds failed. Wingray looks also to be failing. It shouldn't take 3 hours to build. :(
[Xoom Android Development] Taysider:
+1
[Xoom Android Development] uzi2:
You may need to wait for 139 as 138 failed.

Swyped from my Xoom
[Xoom Android Development] elsworth1983:
Oh well looks like it isnt safe our Team Eos's Xoom's :o
[Xoom Android Development] scottgti:
I was really ready for the kernel updates. Eagerly awaiting 139. Thanks TEAM EOS. :thumbup:
[Xoom Android Development] Brandonxcore:
Im having a issue with the google voice search, it doesn't work, well it notices my voice, but doesnt pickup words, I flashed back to stock, and made sure it wasn't my device, and it wasn't, it worked fine, sorry if this issue has been already fixed in advanced.

edit: Nvm fix'd, all you have to do is download the offline voice recognition package in the language settings :)
[Xoom Android Development] solarnz:
139 is up.

http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/EOS-wingray-20120823-139.zip

http://mirror1.teameos.org/roms/eos3/nightlies/wingray/EOS-wingray-20120823-139.zip
[Xoom Android Development] pr1vate piles:
Woop Woop, Downloading off mirror link, thank you.
[Xoom Android Development] elsworth1983:
Cheers team eos DL 139 and going to flash 139 before bed
[Xoom Android Development] Taysider:
Flashed 139 and a quick check around everything seems to be working.

Great work guys :D
[Xoom Android Development] solarnz:
So I've been throwing around a few ideas...

I know that sometimes our file mirrors can go down, or are extremely slow. But the thing is that they're either free for us to use, or very cheap.

What I would like to do is use a content-delivery system, such as amazon cloudfront.

Obviously these systems cost money. Quite a considerable amount of money for us.

However what I am proposing is a system where for a small fee, say $3 you get to download 100 zip files from the content distribution system. This content distribution system would provide much much faster and reliable downloads.

Obviously we would still have the free mirrors available, those aren't going anywhere. However for those that want to get the zip files as quickly and reliably possible this would be a good option.

Is this something you guys would be interested in? A content delivery system like this is simply too expensive for us to afford ourselves. However for a small charge, I think this could work.
[Xoom Android Development] alex94kumar:
Solarnz, I would happily pay you a "donation" of 3 dollars. Hell, your work on this device is worth a hundred times more than that. But yes, I think this is a very good idea
[Xoom Android Development] elton.de.nascimento:
I like you idea solarnz . . .the payment would be by palpal?
[Xoom Android Development] logitechor:
I too would pay. I download enough RMS already. Great idea.
[Xoom Android Development] burt_ie:
Iam up for that! Great idea :)
[Xoom Android Development] rob62551:
3 dollars, more than well spent! Thanks for these great nightlys.
[Xoom Android Development] HuckFinn:
Great idea

I would happily donate some $$$ to support this.

In fact I would also support an early release program such that paid supporters get access to the releases maybe 24 hours in advanced on the paid servers. This would hopefully encourage people to support your efforts. I know that might cause a little bit of an uproar, but in the end you would still be providing the FREE service to everyone. Anyone who complained would just be showing how ungrateful they are, but that is just my humble opinion. If you can afford a Xoom, you can afford a few bucks to support the guys who are keeping it updated with the latest and greatest features.
[Xoom Android Development] scottgti:
Updated to 139. Seems great. Thanks. 2 things I have noticed, just curious about what others are seeing-

1. In landscape press apps. Press home. Tapping side of screen, instead of swiping, results in nothing. Rotate to portrait, rotate to landscape. Tap side of screen now results in swipe. This was mentioned previously, just curious if everyone is seeing it.

2. I stream music, with bluetooth, all day. When I tap on Google Now, while streaming, voice prompt (Saying "Google" ) doesn't work. But, tapping voice search, then the back button brings me to Google now and voice prompt works.

3. Nothing to do with this rom, but I got a new WiFi router and now my xoom can't get my location without GPS on. Any help?

Thanks for the help, and thanks team eos. :beer:
[Xoom Android Development] HairyMerkin:
Why not use torrents?
[Xoom Android Development] istrait:
I would go for this too.. also, 139 fixed all of my issues... softkeys and rings work, much faster speedwise, no rebooted... thanks again..
[Xoom Android Development] Dyelon:
139 working great whoo whoo!

EDIT: man News360 widget keeps crashing on me....anyone else experiencing this? Its one of my favorite widgets
[Xoom Android Development] highKo:
+1 for the torrent idea. Some devs+community used torrents in the HTC Incredible S forums and it worked well. I usually downloaded a rom in 1-2 minutes and they we're seeded for a long time
[Xoom Android Development] istrait:
+2 for torrent, but i still would not mind paying.........
[Xoom Android Development] nadiros:
#139 smooth as silk and no issues to report.

Thanks a lot guys, and great job figuring out the issues and fixes. Sounds like

kcrudup had his work cut out for em eh! Cheers :victory:
[Xoom Android Development] NoP_Compiler:
Which gapps should I flash with v139?

I only have available those that "came" with v127 (gapps-jb-20120802-eos-signed.zip) and those does not include googlenow (maybe gnow is a separate download?).

Thanks

--
[Xoom Android Development] fidju:
Why not give this a try? http://www.engadget.com/2012/08/09/ota-update-center-encourages-pc-free-upgrades-for-custom-roms/
[Xoom Android Development] uzi2:
You have the latest EOS gapps, but you don't need to flash them again.

No wipes, just flash the new Rom and your existing gapps will be preserved.

Swyped from my Xoom
[Xoom Android Development] solarnz:
Google Now should be included in those google apps.

That isn't a hosting service.

Torrents don't quite fit what I had in mind - they're not a consistent delivery system and not I would consider a replacement.

Don't forget I do also mirror everything I upload to goo.im to mirror1.teameos.org
[Xoom Android Development] Sihaz:
Anyone having trouble with Google currents on 139? I can't read any articles anymore. It loads up the front page and shows the thumbnails but won't let me read anything. Have tried u installing etc... thanks in advance.
[Xoom Android Development] Taysider:
$3, Count me in. :D
[Xoom Android Development] elsworth1983:
Sounds good to me :)

---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------

Same thing I was thinking glad I read a post back ;)
[Xoom Android Development] jodtalingchan:
$3 .. why not?
[Xoom Android Development] NoP_Compiler:
Thanks. I'm now in v139 (first time I update my EOS rom).

Thanks eos team!

--
[Xoom Android Development] dilema:
$3 is great. Hell even $5 would be doable
[Xoom Android Development] adityamunshi:
How come Wifi direct is disabled in these JB roms ?
[Xoom Android Development] NoP_Compiler:
Can anybody show here the paypal addresses to donate both to EOS Team and Goo?

--
[Xoom Android Development] Taysider:
If you go to Goo site you can donate there :D
[Xoom Android Development] scottgti:
And my notification area is unresponsive to touch. Anyone else?
[Xoom Android Development] bigrushdog:
WifiDirect is not disabled. Its in Wifi -- advanced. In fact I enabled the NSD checkbox so you can disable service discovery if you so wish.
[Xoom Android Development] edboston:
Deleted
[Xoom Android Development] eddyther:
Currents is working fine here.

Edited: only one or two of my links work. All the rest bring to a black page that says loading...:banghead:
[Xoom Android Development] alex94kumar:
I would even give like 10 bucks to have access to a service like that.
[Xoom Android Development] drewski_1:
i'm on 137 and i'm not seeing it in Wifi-Advanced.

was this added for 139?