yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] alex94kumar:
I like beanflinger personally, for daydream that is
[Xoom Android Development] laur3n.newm4n:
Is there any way to change the theme of the Daydream BW? I want to change the clock and the weather theme.
[Xoom Android Development] bigrushdog:
You'd have to do it manually or wait for theme devs to get caught up.
[Xoom Android Development] laur3n.newm4n:
Delete. Found ClockworkMod touch recovery for Xoom LTE.
[Xoom Android Development] alex94kumar:
what should we expect to see in the next nightly?
[Xoom Android Development] MikeCriggs:
+1 from my OG Note that just got some 4.2 love.
[Xoom Android Development] w4tcher:
Just flashed and got sound but no picture through HDMI. any ideas how to fix.
[Xoom Android Development] logitechor:
I know the developers are having a bit of trouble with some of this. I have CM10.1 latest with Teameos Gapps. Which gives me HDMI but no Photosphere. And pretty solid Bluetooth. I suspect it will resolve shortly.
[Xoom Android Development] dreamcwli:
Currently working HDMI leads to random reboots. For those want to have HDMI you can grab hwcomposer package from My Android 4.2.1 thread and flash it.

The hwcomposer patch is on Team EOS's code review but I don't know if they will enable it or not.
[Xoom Android Development] runandhide05:
We are testing HDMI right now..
[Xoom Android Development] mikejs78:
I'm having some issues with the multi-user feature. This happened back on 158 and I reverted back to EOS3 for a bit. Tried 160 today and same thing. When I add a new user, SuperSU hangs trying to grant root to /sys/bin/id and it does this repeatedly whenever I am using the second user. Reverted back to 155 for now..
[Xoom Android Development] runandhide05:
From what I've read root access does not work yet in any user that is NOT the owner.
[Xoom Android Development] mikejs78:
That's fine, but SuperSU just tries to load up automatically when I log into the second user. How do I prevent this?
[Xoom Android Development] NWinfuse:
Looking forward to the next build, so far 160 has been working great for me but it will be nice to have working hdmi
[Xoom Android Development] tdarren:
What's coming in the next nightly?

I haven't seen a new nightly for 3-5 days now. Seems odd it being a "nightly".

I am on 160 and general speed was drastically improved since 158 and first gapps. Looking forward to more nightly's.
[Xoom Android Development] rbruno66:
Is there a separate thread for Stingray? I searched but didn't see one. Thinking about trying the Wingray build on mine.
[Xoom Android Development] liftman-:
yea thier is a stingray thread eos3 stingray. and a stingray build. no radios yet.

brd is working on them but its a tough one.

hopefully he will take a break and spend some time with his rug rats:fingers-crossed:
[Xoom Android Development] NWinfuse:
I'm just happy there is an EOS 4.2 build at all so I'm not going to complain about the builds not actually happening "nightly" I take this as more of a work in progress than true nightly builds. These guys bust their butts on something that they aren't getting paid to do and they do an amazing job of it! I have nothing but respect for those here on XDA that take upon themselves to put together awesome ROMs for the rest of us.

Thanks for everything Team EOS! Keep up the good work, I truly appreciate it.
[Xoom Android Development] Dyelon:
Keeping tabs on this but staying on team eos 3 until this is more stable.....thanks so much team eos, looking forward to making the upgrade soon!
[Xoom Android Development] INDIANAJONNY:
I tried this since I use my Xoom often as an XBMC box. The hwcomposer got HDMI working, but then it starting rebooting every minutes. I wouldnt recommend it.
[Xoom Android Development] dyskinesia:
+1 nobody is forcing you to flash the newest and latest. It is understood there are issues and we are getting to use/test these ROMs for issues /stability. I'm thankful and appreciative and willing to add what I can which is usually logcats or error reports but knowing the nature of how these roms are developed and advanced I'm just happy someone is still interested in our xooms.
[Xoom Android Development] dreamcwli:
This is the reason why developers didn't make HDMI available at this moment. The new implementation is better than this one but still have random reboots so just wait us to solve the issue.
[Xoom Android Development] bigrushdog:
I'm gonna try and give some perspective here. 4.2 is not like past releases. Internally, much reverse compatability has been removed. That means that older devices, with older kernels and older proprietary resources will have difficulty maintaining compatibility with 4.2. So we are having to do things for the Xoom that we didn't do before. Up to this point, new Android releases just worked out the box. This is no longer the case. Many comparable devices, non nexus devices, like the Transformer 101,have had to fight a hardware battle from day one. Now it is a battle the Xoom will fight. What does this mean? If you want a flawless build , stick with 4.1.2.

It means the Xoom is getting old. Android has left Xoom behind. Eos has not. Dreamcwli has come in as well and is doing amazing work. He is VERY talented and the Xoom community is blessed to have him on board. I'm certain between all of us, we'll get things running as they should. But it takes time now. Just some thoughts
[Xoom Android Development] M_Cheevy:
Change Log and Bugs List

I've noticed that the change log hasn't been updating on jenkins. I assume this is because the guy with the goo login has "retired"?

As I thought of this I also thought that a current "Bug List" would help cut down on repeat problem reports and complaints. It would also provide a single point of reference for the developers to track their own progress. I remember there used to be a change list prior to Jenkins that seemed to be more developer centric. Is that still active?

For myself, I've performed a full wipe, including the data partition, flashed 160 and 121209 gapps. Even with over clocking to 1600, and disabled animation, I've found it laggy. Amazon Kindle still gets stuck on the logo screen and fails to progress. Firefox was also crashing on load. Initially, these apps were restored by TB but when they failed, I de-installed, rebooted, and reinstalled. Unfortunately, both apps continued to fail.

On the positive side, I like some of the interface changes and am keeping an anxious eye on the developments. I also want to express my appreciation for teameos' continuing efforts and devotion to the Xoom community. :good:
[Xoom Android Development] NissanNick:
Sorry to be a pain but I am on 4.1.1 I want that flawless build... can someone please tell me what update 4.1.2 is and the gapp that goes with it. Thanks.
[Xoom Android Development] WarLion:
155 is the last buil for for 4.1.2 after 147 become a little bit laggy and was fix on 154

gaps for 155

gapps-jb-20120802-eos-signed
[Xoom Android Development] alex94kumar:
as i've said before, keep up the great work Team Eos! we all appreciate the hours of hard work!

Eos: Evolution Of Smooth!
[Xoom Android Development] fromthestars:
Is there any reason not to flash #155 with the latest 4.2 gapps?
[Xoom Android Development] WarLion:
you can try but you will had a boot loop
[Xoom Android Development] petrossa:
I did by accident, it booted but immediately many Google apps crash.
[Xoom Android Development] pkelly517:
The Kindle app still stalls when opened.

Release 160.
[Xoom Android Development] INDIANAJONNY:
Just curious. Where can I find cm10.1 for Xoom?
[Xoom Android Development] jase33:
take a look at steadyhawkins' G+ page
[Xoom Android Development] kentedman:
https://plus.google.com/104860219450510860872/posts/WZ5dFpNstQZ

and FYI.. I know this is the wingray thread but I have actually have a working 3G data connection after flashing CM 10.1 Stingray 12/15 build (still no 4g). Progress !!
[Xoom Android Development] bigrushdog:
If you can give me 3g I can likely give you lte
[Xoom Android Development] kentedman:
BRD... That's what we wanted to hear! Can't wait! Thanks !!!
[Xoom Android Development] BatGnat:
Hong Kong Variant

Does this rom support the Hong Kong variants partition layout?
[Xoom Android Development] waz675:
They symbolic link the system apps so if the HK partition layout is a smaller /system then yes, if it's different might pay to actually state what the HK layout is like sincebi can't recall it being specifically mentioned much if at all in the past year or sonics had an XOOM. Could be my pain affected memory though.
[Xoom Android Development] bigrushdog:
Not yet. But it's on the to-do list.
[Xoom Android Development] alex94kumar:
Looking forward to the next nightly. cant wait until bluetooth works properly!
[Xoom Android Development] runandhide05:
What's wrong with Bluetooth?
[Xoom Android Development] alex94kumar:
i have a bluetooth keyboard and it's not connecting to it. on 155 it connected with no issues at all. ill post a logcat
[Xoom Android Development] Taysider:
I'm running latest nightly and bluetooth connects ok
[Xoom Android Development] greenro89:
I am having troubles with my dock. Its stuck on the highest volume and won't turn down when docked..
[Xoom Android Development] runandhide05:
https://www.youtube.com/watch?v=uvjtNLMzcHg&feature=youtube_gdata_player
[Xoom Android Development] greenro89:
But from what I see it doesn't play through the dock speakers though..
[Xoom Android Development] ATZ-007:
Compare to EOS 3 is this faster and smoother?

Also is there any Not Working list?
[Xoom Android Development] j3yps:
Thanks for this ROM, i just a Xoom as a gift...now planning on using it as a media player and "Music Sheet" for my gigs...hoping to get a good experience from this device with this ROM! ;)
[Xoom Android Development] rohitece06:
I am interested in knowing this too. I tried #160 but stutters were too much to handle for me. So I am back on #155. Can somebody shed some light on it?
[Xoom Android Development] runandhide05:
It has been stated before, we are shoe horning a OS that is not technically supported on the Xoom. And for that reason some of the first nightlies may not be perfect and 100% awesomeness, but that is to be expected on nightlies, in fact that is kind of the point of nightlies see what works, what doesn't and what needs tweeking.

If you need to be on the bleeding edge you may have a fee bumps in the road.

To give some comparison if you have any other eos supported devices eos4 is smooth as butter. It just goes to kind of show that the Xoom is getting old. But I'm sure it nothing that we will not iron out. ;)
[Xoom Android Development] rohitece06:
We have all the faith on you guys. Keep it up man :good:
[Xoom Android Development] EDNYLaw:
Team EOS for the WIN! Guys, the features on 162 are awesome! Two quick things, is it possible to make the back, home and recent a little larger on the left? I can see myself fat fingering them on occasion. Also, i looked through the gerrit and didn't see anything but is HDMI still MIA where picture is concerned, I'm unable to test at the moment. Thanks guys, this update is HUGE!

Sent from my Xoom kept alive by Team EOS
[Xoom Android Development] runandhide05:
As far as HDMI goes... There has been a commit push but it remains unmerged at this time. It causes too much instability.

Within a 24 hr period it cause about a dozen reboots for me.
[Xoom Android Development] alex94kumar:
I'm really liking the new drop down settings menu in 162.... saves me time when changing screen brightness :D

EDIT: Just noticed the Eos Control Center..... all I can say is WOW. amazing work guys!
[Xoom Android Development] EDNYLaw:
Just noticed that trying to access the navbar ring causes sytemui to become unresponsive. Toggling systembar modes corrects the issue.

Sent from my Xoom kept alive by Team EOS
[Xoom Android Development] NWinfuse:
just flashed 162 with 1209 Gapps and upon reboot noticed that the home button is missing from softkeys, anyone else have this issue? I have gone into recovery and flashed 162 and gapps a second time and I still have the same issue. That appears to be the only bug I am seeing at this point. I may have to just flash back to 160 for now unless of course someone has already found a fix. I have had no issues with this on any other build so far
[Xoom Android Development] dreamcwli:
I am still trying to fix this problem on kernel side. As you may notice system become as smooth as in 4.1 when hwcomposer support is enabled. This is a must fixed issue if we want to get best from Xoom.
[Xoom Android Development] EDNYLaw:
Home button is definitely present both in 4.2 navbar and "old" style ui.

Sent from my Xoom kept alive by Team EOS
[Xoom Android Development] alex94kumar:
This is going to sound like a total noob question, I apologize for my ignorance, but what does hwcomposer actually do?
[Xoom Android Development] dreamcwli:
Take a look at HW Composer part of this article.
[Xoom Android Development] alex94kumar:
Ah, I understand now. I see why Its so important to Eos.... Thanks!
[Xoom Android Development] NWinfuse:
Thanks, good to know that this issue is not present for someone else. I am redownloading 162 and trying again...hopefully better luck this time. Maybe I just got a bad download the first time as it did take forever to download.
[Xoom Android Development] runandhide05:
I saw it happen once, if it happens again to you, what actually happens is the key is there and present its just black in color, go to the soft key settings in the EOSCC and adjust the color to stock. See if that helps out
[Xoom Android Development] NWinfuse:
You rock man! I just realized the key was in fact there as you said but hadn't thought to just try adjusting the color. I guess its a small bug somewhere but hey if that's the only issue I see then that's awesome!

EDIT: sure enough resetting the color brought it back to normal
[Xoom Android Development] alex94kumar:
I'm excited to see what's to come next!
[Xoom Android Development] :
I saw you uploaded umts_everest version to goo!

I've a MZ605 and i have always used umts_everest version with 3G (with eos3)

I installed it, but now it says verizon wireless and I cant connect to 3G networks. Is this one the correct version for my tablet?

Besides that, i love old-school tablet ui, but quick launch targets are not working for me in that mod, and when tablet goes to that kind of "cinema mode" in which softkeys are replaced with little dots, the dots are in the center, not in the left.

And sometimes system ui crashes turning on-off the torch

Just small "bugs", i know there are more important things.

Thanks for this awesome rom teameos!

Edit:And sometimes a red edge appears.
[Xoom Android Development] petrossa:
Awesome build 162. So far no major issues except that the developer tab seems to be missing from settings and the occasional flashing screen. Smooth as silk in normal use. You rock!
[Xoom Android Development] alex94kumar:
tap your build number in settings>about tablet 7 times
[Xoom Android Development] bigrushdog:
Darn I thought I fixed that. Ugh.
[Xoom Android Development] alex94kumar:
No worries man. Some of the most complicated things in life are solved through trial and error
[Xoom Android Development] NWinfuse:
Definitely not a big deal, I was just happy to find it was easy to fix. I'm sure at some point you'll figure out whats causing the issue.
[Xoom Android Development] tadiv:
latest gapps?

What's the story behind the brd_gapps_4.2.1_latest_12_16_12_neon.zip file? Can that be used with 162 - should it be used with 162?

Thanks,

Tom
[Xoom Android Development] runandhide05:
Do not use those on Xoom

Use ONLY the gapp package in the OP

Those are for neon devices which the Xoom is not, also those won't fit in the system
[Xoom Android Development] tadiv:
I'm learning - I asked before I flashed!

Thanks!

Tom

P.S. Just curious because it was in the goo directory...
[Xoom Android Development] alex94kumar:
When in doubt, follow instructions in OP :D
[Xoom Android Development] bigrushdog:
Definitely NOT for Xoom. But I recommend it for tuna series, or grouper. It's a really good gapps pack. It's my personal stash. Homegrown baby :laugh:
[Xoom Android Development] rohitece06:
I cant see the changelog on jenkins. has it moved? I just wanted to know if hardware composer is enabled yet or not. I am going to start experimenting with this ROM after that build.
[Xoom Android Development] HuckFinn:
Somewhat random lockups...

I've experienced some strange lockups on both 160 and 162. It does not happen all the time but the events leading up to the lockup are the same.

I will be doing something on the xoom and the screen will dim due to inactivity. If I tap the screen to "wake" the xoom sometimes the screen will shut off and the only way to get it back on is to reboot (volume+ and power). I have not seen anyone else report this so felt I should mention it. As I said I saw this on 160 after a clean install.
[Xoom Android Development] alex94kumar:
could i flash dreamcwli's hwcomposer for eos and see how it works out? because i can just flash 162 and it will write over it, erasing it, correct?
[Xoom Android Development] bigrushdog:
Here's the deal. The hwcomposer work by dreamcwli is solid dev work. However, in order for the work to be stable, will require some kernel work as well. Until then, his work results in frequent reboots. So, we have enough issues at the moment. I can't afford more instability. I may come up with a temporary solution for users who wish to use dreamcwli's work.
[Xoom Android Development] alex94kumar:
I understand. Now, i know people have been whining about this, but i'm asking this as a serious question. On 4.2, will there always be launcher lag (and in other places too) because of the lack of hwcomposer? I do not care one bit about the lag, believe me, i'm just curious about it
[Xoom Android Development] dreamcwli:
I think it is OK if there are no other changes on libsurfaceflinger.so in Team EOS ROM or you can build it with hwcomposer support enabled. Since this is still an experimental feature at the moment, I think it is not worth spending much time on making workaround there. Users can simply flash back if they think it is too instable to use and developers can concentrate on resolving important hardware issues like LTE, 3G and kernel to make them work.
[Xoom Android Development] alex94kumar:
Agreed, some lag on the launcher is the least of our worries right now
[Xoom Android Development] istrait:
Mine does the same but is proceeded by a bright flash as the screen goes to full brightness then goes to sleep, wont wake up and requires a reboot....
[Xoom Android Development] runandhide05:
Get nova launcher. Beats the pants off of stock launcher anyways.

And you can tweek Nova to make it give a smoother feel as well.
[Xoom Android Development] petrossa:
Using ADW launcher, it also works as smooth as can be. I had nova, but adw beats it by a mile. Seriously.
[Xoom Android Development] BatGnat:
Thanks!

What are the chances of using the partition that gets hidden (in the HK version), for solving the system space issue.... It's 4gb isnt it...;)
[Xoom Android Development] logitechor:
Now using Teameos ROM with Gapps. Photosphere works. Hwcomposer installed so HDMI works. Some problems with reboots. But all in all - great and thank you.
[Xoom Android Development] christianpeso:
I did get this on 160 as well. Guess they were SODs. Even after I forced a restart,sometimes after it would restart and then go to sleep by itself, I would still not be able to wake it up. Sometimes I had to do some kind of activity after a restart just so the screen wouldn't go black and get an SOD. Was very random.
[Xoom Android Development] tadiv:
I can't seem to find the dock setting in 162... Is it gone, or am I just not looking in the right place? Also, in 160, the audio selection under the dock settings is greyed out and not selectable...

Thanks,

Tom
[Xoom Android Development] grey.ghost:
Nice job on the Rom so far. I notice screen flickers very often, and the kindle app doesn't respond, since I need that for school, I'll have to go back to 4.1.2 for the time being, but I really hate to leave this setup.
[Xoom Android Development] petrossa:
Same here. Random lockups
[Xoom Android Development] gibbs1984:
Anyone else's sounds gone, when I try to select a sound for the list there is only Silent there?

Sorry, on 162 with 12/09 Gapps.

EDIT: Reflashing the ROM didn't change anything. I've gone into the zip file and all the .ogg files are there in /system/media/audio/alarms/.

God knows what is happening but they're back now :D

Really good update from 158, nearly buttery smooth and appreciating all the work you guys are putting in, awesome job! :)
[Xoom Android Development] SAHorowitz:
Hello all. So far love the rom. I am currently running 162 w/gapps 12-09. I am having one issue and wanted to ask if anyone else is having it. I use the Sixaxis app to allow me to play games with the PS3 controller. When I was on stock 4.1.2 everything worked fine. Since upgrading to this rom, I cannot get the PS3 controller to connect. When I start the connection, the WiFi turns off, Bluetooth does not turn on (normally WiFi isn't affected -- stays on, and Bluetooth automatically turns on). Has anyone else got Sixaxis to work with this? Is the fact that WiFi gets affected and Bluetooth does not come on a known thing?

Thanks.

SAHorowitz
[Xoom Android Development] alex94kumar:
xoom supports PS3 controllers over USB OTG, i play shadowgun dead zone and pwn n00bs that way
[Xoom Android Development] SAHorowitz:
Thanks for the reply, but I prefer sixaxis app. It has touch emulation.
[Xoom Android Development] Dyelon:
On a related issue, does anybody play halo 4 on this board? Add my gamer tag:

l2evolverOcelot (the first character is an L )

I play most of the popular multiplayer games so any team EOS groupies feel free to add me!
[Xoom Android Development] simonbarsinistr:
I flashed 162 with the 12/16 gapps this morning, and the improvement in smoothness is very pronounced! It's really coming along well, great work guys!
[Xoom Android Development] alex94kumar:
what's new on the 12-16 gapps? anything noticeable?
[Xoom Android Development] NWinfuse:
Where did you find eos 1216 gapps?

Edit: found them on goo
[Xoom Android Development] bigrushdog:
Make sure you flash the xoom only gapps. The other gapps is for n7, gnex, and other devices. Another nightly tonight. Fixes Kindle, and issues with some other apps. Fixes 0 percent battery tile. Other minor issues fixed. WIP
[Xoom Android Development] NWinfuse:
Looking forward to trying out the next build. Thanks for all the hard work
[Xoom Android Development] RacerX780:
It is possible to use the Youtube app from EOS 155 with the latest nightly? I don't really care for 4.2.16... would rather have the old one back.
[Xoom Android Development] simonbarsinistr:
I have not noticed anything new. I know some things are removed until they're bug fixed. I think it was photosphere, and I can't remember what else.
[Xoom Android Development] fvlserevere:
...

I flashed nightly 163 and I think team eos have merged something weird into the code, something like ultrasonic speed. Thank you.
[Xoom Android Development] runandhide05:
Photosphere is in there only thing removed was exchange and email due to it being built in ROM now
[Xoom Android Development] rookie8155:
Where do I download Google apps for this ROM? The link on first page does not work. I will appreciate your help.
[Xoom Android Development] runandhide05:
http://goo.im/devs/teameos/roms/eos4/gapps/gapps-jb-20121216-EOS-XOOM-ONLY.zip
[Xoom Android Development] alex94kumar:
http://goo.im/devs/teameos/roms/eos4/gapps

Dang it RnH, beat me to it lol
[Xoom Android Development] mongday:
Dose it hot word detection work for now?
[Xoom Android Development] EDNYLaw:
Great job on 163, running great. I have one suggestion if it's possible. Can you combine the two UIs so we can have landscape buttons on the left and portrait buttons in the middle? Selectable, so people can choose of course. Just a thought, but keep up the great work. It's really appreciated, thanks guys!

Sent from my Xoom kept alive by Team EOS