yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] REHolt218:
Ot

1.. go to your /system directory and backup you're build.prop

2. Open the build.prop.zip and copy the build.prop file into your /system directory
[Xoom Android Development] mnaim:
No one knows how to fix wifi LEAP?
[Xoom Android Development] mutiny:
It's in the OP here: http://xdaforums.com/showthread.php?t=1443949
[Xoom Android Development] Nusince:
On the subject of build.props and market issues-

We are aware of the issues with the build footprint.

The long and short of it is that these are still engineering builds and are being seen by the market and certain apps as such. We are working on making some changes that will make EOS appear to be shipping builds as opposed to engineering builds that should help alleviate these issues that people are having.

PS - flashing different build.prop's will solve certain problems but it will also cause others. Dragons Ahead.
[Xoom Android Development] Ultrawoach:
I got the same issue... I hope we get a fix.
[Xoom Android Development] rmcsc:
Oh! No problem, then. I am Dragonborn.

FUS RO DAH!!
[Xoom Android Development] Nusince:
I used to use Honeycomb, but then I took an arrow to the knee...
[Xoom Android Development] gffmac:
If we knew which lines to edit we could just edit whats needed to the eos .prop.
[Xoom Android Development] ruvort:
Lol! And then did someone steal your sweet roll?

Sent from my Droid Incredible 2
[Xoom Android Development] Nusince:
The bigger issue is that this is an eng build type. build.prop edits do not change the fact that fundamentally at this point in time EOS is built as an engineering rom.

In a nutshell (and this is kind of boiled down here) the reason that this these are eng build types and not user or userdebug is that there is very active development on going against these builds. Engineering build types make it much easier to test changes made against the build and prior builds. Generally when builds are ready for release they migrate from an eng build type to a shipping (user) build type. It is a trade off between ease of general usability and ease of development.

As I mentioned we are working on options that will increase general usability for the user base with minimal impacts on the development process.
[Xoom Android Development] shakuyi:
strange ive tried this several times and it has not worked
[Xoom Android Development] rschenck:
I have been watching the noise running through the thread about the build.prop and I am glad some people have had good luck with hacking it into the build.

As for me... I have no intention of touching it.

My reasons are simple and probably quite unique. Stated simply, I don't like to buy software off the rack. I don't like software that is a bit of this and a bit of that. I like things to be whole. I believe that to make a first rate mobile rom you need to have a vision and a plan. It requires knowing where you want to go and the steps you will take to get there. At the end of the day, improvising leaves you with just that...an improvisation.

I have been fortunate, being unable to code myself, to enjoy the fruits over the last year of two great visions of how mobile roms should be....that of CyanogenMod and that of Team Eos.

Sure some of you may have the knowledge or feel the need to hack this mod and that file into Team Eos' vision...and that is great for you. I do not have that knowledge or need.

Personally, I will wait and let them put this rom together how they want, in the order they want, as they have said they will. I want to see where this vision goes, and I will support the road they choose. I trust Team Eos to make the right choices for their creation. No shortcuts asked, none required.
[Xoom Android Development] okantomi:
Nicely said. I am more than satisfied with the progress of this rom, to date.
[Xoom Android Development] joshndroid:
I totally understand your position on not changing the build.prop but in all honesty we are not hacking too much here or there.. Essentially we are just using it temporarily to allow us to play a few games that we cant at the moment once EOS gets them going no one is gonna use another build.prop it just provides a little more use for now.. A bandaid fix

Sent from my mind control device
[Xoom Android Development] REHolt218:
And besides that, it provides another reference point of information as to where the issues are. I see it as another step in the debug process that might help point team EOS in the right direction to fix the problem.

It's not that they aren't all smart guys and will probably figure it all out, but they are limited in what they can test. They are focused on certain areas of the development and we the users can sometimes help in the testing and debug process.
[Xoom Android Development] mcnob:
Slightly off-topic here but connected to wiping a new ROM install so thought it was worth an ask.

When re-installing and restoring ADW launcher, i always have to re-setup every single widget. Is this the way it works for everyone? It's just that someone once told me that he just restores ADW backup, reboots and everything is as it was.

Am i missing a vital setting somewhere?
[Xoom Android Development] mcakar:
Hi mcnob.

I usually just have to restore the adw backup and then the screen layout backup from adw and it's all good mate.

Mike.
[Xoom Android Development] PMDColeslaw:
Not sure if it helps you, but I have found that doing an advanced nandroid restore of the data from recovery is the fastest and most stable way to restore things after a wipe. It puts everything back where it belongs including widgets.
[Xoom Android Development] itlnstln:
I have never thought of doing that. I'm going to have to remember to try that the next time I need to do a full wipe.
[Xoom Android Development] solarnz:
This is bad practice. Why? Because it means you're not wiping.

The main reason why you need to wipe often is because signatures on some of the system applications have changed. These signatures are recorded in a database on the data partition when your device first boots, and if the signature changes, android revokes some of it's permissions, and this can cause unexpected behaviour and force closes.

tl;dr : Bad Idea. Will likely cause you, others and the developers head aches down the road.
[Xoom Android Development] Dokted:
camera

hi all. sorry to be a pest, but can anyone suggest a solution: my xoom camera is terrific until I try to rotate it to face me, then it all goes to hell. fades to black, nothing works, need to clear data in apps setting to get it to work at all again. Perhaps it doesn't like my face? T
[Xoom Android Development] scriptx:
If you must retain an app/settings after a wipe, titanium backup ftw. Titanium backup pro even let's you extract an app + data from a previous cwm nandroid backup. Easy peasy!
[Xoom Android Development] umbra6:
This is the exact reason some people are developers and some are end users...

As you know...this rom has the camera and HDMI drivers from the leaked rom. So in your words, this rom has a little of this and a little of that...

Me personally, I browse these forums to see what is being done as I build my own roms for my own devices...which includes a little of this and a little of that and personalized for myself. Heck, most of the ROMs on this site have a little bit of this and that from other sources.
[Xoom Android Development] Alxoom33:
What about using GAPPS Fixer after a flash without a full wipe? I take it that won't work very well? So, if that is no good, is there a safe way to get back you icons after a full wipe? Thanks,
[Xoom Android Development] gffmac:
Nice post, well written, that's one thing I've noticed about team EOS as well, very well written replys and informative answers.

All that's happening is people have noticed a loophole shall we say and as with the tradition of xda whether it be a dirty hack for a quick fix people will take the quick route until a more permanent solution shows its face, that's what xda is all about in my mind. The reason I love the android community is the constant messing around with the system files and learning along the way, just having an app/game running which wasnt before is a breakthrough in anyone's mind whether its the proper way of doing it or not. Rant over :-)

Long live team EOS lol
[Xoom Android Development] ErantyInt:
I just wanted to pop in and say a big 'Thank You' to everyone involved on this project. This has breathed life into my old Xoom, making it a beautiful and elegant piece of hardware. I've been with this build since day five, and it's just made leaps and bounds since then. ~95% functionality within 34 days just blows my mind. Keep up the good work, and I can't wait to see what comes next.

Sidenote:

With the latest R36 installed, I noticed something odd today with Titanium Backup. If I touch the screen at all, or attempt to do anything but watch it back up my apps + system data (batch), it fails. It will freeze on whatever item it's backing up, then say "Backup aborted by user" (or some such thing). It never used to do this, and it doesn't do this on my other devices (Epic 4G, SGST 10.1, and Nexus S).

Not sure if this is an app issue, or with the rom. Either way -- a negligible thing. Thought I'd give you the heads up and see what your experience with it is.

Thanks again!
[Xoom Android Development] mongday:
Sygic aura problem.

After I have installed the rom build#36 and Gapps 10.1. I found only one issue for me, it is when I try to open the sygic aura 11.2.3 I found some crash. If somebody can correct it please suggest me, thanks.
[Xoom Android Development] joshndroid:
I noticed this myself.. Had to sit xoom away on the table and not touch a thing till it is done lol don't think it is related to the rom though pretty sure it happened for me in 34

Sent from my mind control device
[Xoom Android Development] suboxide:
I just wanna know am I the only one that his front facing camera doesn't wanna work I just get the orange led and black screen after a min or so I get fc. It did work halfway last week when I flashed a from forget what number.
[Xoom Android Development] Illusive Man:
I'm running build 35 and loving it. I want to say thank you to the devs for their hard work on bringing us this ROM. I do have one question: Is there a way to force the stock browser to fetch the desktop version of a page rather than the mobile view? I see a setting to "get desktop view" but it is not persistent and has to be checked and re-checked when going to certain sites.
[Xoom Android Development] itlnstln:
Good to know. I will continue to use Ti Backup.
[Xoom Android Development] ssmithri:
Mine works fine on 34...
[Xoom Android Development] DeareN:
I don't mind using an english rom, I just want to know if I can read and write Greek text.. If anyone knows and the answer is yes I ll flash nighty 37 as soon as it comes out. I m tired of HC keyboard lag, I'm also tired of so many browser issues...
[Xoom Android Development] arrtoodeetoo:
Using Hacker's Keyboard, I was able to type in Greek and the characters showed up correctly.
[Xoom Android Development] ErantyInt:
I had to use Swiftkey Tablet to get Greek input, but the Greek language pack is included. Screens below. At least I think that's Greek... :confused:
[Xoom Android Development] PMDColeslaw:
I personally have done it many times without any issues. I only restore the data not the system. I didn't think it was any different than a batch restore of apps + data in titanium backup. Or using the restore from a nand in the titanium advanced menu which I haven't been able to get to work on the xoom so far.

You're the dev and you definitely know better. I'm just saying I haven't had that issue.
[Xoom Android Development] Nusince:
I actually had that same problem the other day on my Galaxy Nexus running stock 4.0.2 firmware. I'm not quite sure yet what the issue is to be honest.
[Xoom Android Development] wanderfowl:
36 is working great. I just bought the Boot Image changer to support Team EOS, which also works great. Thanks again, guys!
[Xoom Android Development] xBlackDroid:
Running de v10 of Gapps and i've some issue with email widget, say "can't install" ...

Whats the problem, using the 36 Build
[Xoom Android Development] Legato Bluesummers:
Its always been that way on my Xoom. I always have to put my tablet up on a high shelf or something while I restore and not touch it or it errors out on whatever one it was restoring when i touched it. Been that way since day one of being rooted for me. I have cats, 5 of them, so i gotta hide it where they won't jump up and try to scent/touch my tab. As they have failed restores on me before rubbing the screen with their faces.
[Xoom Android Development] joshndroid:
No problem really mate just a quirky thing.. Just a spitball here but Could u run a log cat while the app starts would this help see if the input is borked and allows any touch to be registered as the back button (i think its acting as back button.. as home allows u to use tibu in the background)?? Or would u need to do something else to see if it is app or rom related

Sent from my mind control device
[Xoom Android Development] rschenck:
Exactly....but I know that beyond very basic messing I do not have the knowledge or temperament to build the rom for myself. Others do and that is great, as I said. ADB makes me queasy and I try to avoid it whenever possible.

For me things just get messy here when the lines you mentioned blur....when the dev types get pissed off that there are end users asking questions, or the end users start thinking they know more then they do, bricking their phones and demanding to be rescued.
[Xoom Android Development] mikedyk43:
You are forgetting that there is a group of people that fall somewhere between Dev and End user. Beta testers are a vital part of the development process and have knowledge bases ranging from novice to dev status. Some post only problems and others post problems and possible solutions. Both are important since it is impractical for even a team of developers to test every aspect of any given ROM. One of the best things about this forum and Android in general is that the nature of open-source software allows for even the most inexperienced of users to stumble upon a problem/solution for a bug and ultimately contribute to the finished product.
[Xoom Android Development] brakmaren:
Nightly 36 with gapp 10.1 makes my sygic navigation say can't start to.

Reverting back to gapp 9 fixed it.

But i did NOT do a full wipe.Just cache and dalvik.

So it coul'd be my fault...
[Xoom Android Development] rschenck:
I see what you mean, however it is straying away from the salient point. I do not see self-Modding and hacking to be beta testing. Beta testing is running the software as provided and reporting on its behavior, especially any bugs or issues.

No one is helping Team EOS beta test by swapping build.prop files. They are not investigating why or how it changes things. 99% of people doing it have no idea what they are doing or where the file came from. They just want Asphalt 6 to work.

They are just self medicating at the suggestion of some other user and that is fine. However to say they are doing it as beta testing is like leaving over half your dinner and going to McDonalds instead then telling your wife you are helping her be a better cook. You won't be hungry anymore but I doubt she will thank you for the "lesson"....and tomorrow night you may find dinner cancelled.
[Xoom Android Development] bronisb:
not only for you, for me also Sygic does not work, also Waze ... I think that is a problem with the ICS, the applications are not compatible with this OS yet ...:(
[Xoom Android Development] afpapa:
Yep, it's all Greek to me! (so I can read it easily! :p )

I am on ~ 4-5 days old build and it runs perfectly in Greek.

There are several keyboards that can be used for Greek language input, my personal recommendation is swiftkey for tablets (paid). Very good!
[Xoom Android Development] donghungx:
some time i can't wake up the lock screen, i need hold power and up volume to restart it :(
[Xoom Android Development] banny7000:
I had something similar happen, pressed power then unlocked device held down home screen to change wallpaper then pressed gallery then screen went black. Had to do power volume up. It's the only time it's ever happened on my Xoom hopefully it was a one off. Build 36
[Xoom Android Development] solarnz:
New google apps package up 10.2.

You don't have to wipe for this package if you're coming from 10.1.

Only thing changed was facelock not rotating the screen while in setup.
[Xoom Android Development] Warell:
Sygic version 11.2.3 is now compatible with ICS.
[Xoom Android Development] bronisb:
downloaded, installed, still doesn't work ....

on manufacturer's website is not in the list MXOOM 604, is Xoom MZ505 Family Edition, Xoom MZ600, Xoom MZ601 / MZ603 / MZ605....:(
[Xoom Android Development] f1ux:
The latest version still doesn't work for me. Does on my sgs2 with ics though
[Xoom Android Development] zandrzejz:
Sygic works very well on my Xoom mz604 with Chinese ics. This also does not Sygic problem only cooked roms.
[Xoom Android Development] joshndroid:
Relax buddy no one is trying to convert u.. U stated u wanted to keep what EOS provides, thats great everyone understands your point of view.. The build prop change does do some good however small.. the devs have said they have their build prop is different because of the builds status.. that is also fine we all understand that as well.. Myself and others just wanted a few more games to play, its not devaluing anything android or what eos has provided it was an issue that until a couple of days ago was not explored or mentioned and as soon as there was 'noise' the devs put the word out, with a clear and concise response as always.. This also affirmed our previous specultion whether the build prop was indeed the culprit to why games worked on one rom and not another (this fact alone would be of great help to an end user as it provides a basis which stops irrelevant posts saying but this game works on blah rom) Also, as for what the differences were there was a link posted with the differences between the build props on here, did u view that?.. Im not trying to come across as having a dig at you.. Im just trying to establish what we have concluded through these last few pages which have side tracked the thread over debates on personal views on editing the open source rom that is provided for our own device and the ability for us to 'try' to offer help whatever user we may be

I apologize for the post length and off topic nature, i have applied my own 2c and will try to be on topic in future

Sent from my mind control device
[Xoom Android Development] dadoc04:
Great work team eos
[Xoom Android Development] kev0153:
You're not married are you? ;-) j/k

On a side note to get back on track. Does anybody use facelock and is a contacts wearer? When I put my glasses on it seems to confuse it. i turning off for now.
[Xoom Android Development] Legato Bluesummers:
I just flashed the newest nightly and gapps and the wierdszt thing happened...I wasn't even bothering watching my Xoom boot cause I knew it would be a while with it being after the wipe and all. I randomly look over to see if it booted and after the EOS boot animation a screen popped up and said "updating Android" 1/286 applications. Then went all the way from 1/286 to 286/286 applications and finished and just booted as normal. Was that supposed to happen? Never saw that screen before....ever
[Xoom Android Development] rschenck:
That normally happens every time I flash a new ICS build on my Galaxy S....so yes I think it is normal for ICS and we will likely see it from now on.

Another step forward, Team EOS?
[Xoom Android Development] REHolt218:
I use faceunlock and wear reading glasses. It can recognize me with or without the glasses.

There is an option in security to improve recognition. Try using it with your glasses on and see if that helps.

r

I saw that occur on the first couple of ics builds I tried. Have not seen it in awhile though.
[Xoom Android Development] torespen:
Has anyone gotten SPB shell 3d to work with this build?.. or ICS for that matter?
[Xoom Android Development] mongday:
Sygic 11. 2. 3 doesn't work with Lastes build(37) , Gapp 10. 2.
[Xoom Android Development] basilbrush68:
Just installed build 37 with 10.2 and everything is running really well except for ad-hoc wifi.

My ad-hoc network (teathered cellphone) appears with a star, but can't connect.

Has anyone seen ad-hoc wifi work yet?
[Xoom Android Development] macarmody:
Problem has been submitted and discussed widely in most ics forums. A few claim success but most do not. Tethering via Bluetooth seems to work fine.

https://bugs.teameos.org/show_bug.cgi?id=30
[Xoom Android Development] X-Mod:
Did you just replace build.prop?
[Xoom Android Development] canecbr600:
Great work guys! I'm loving the huge boost in performance, especially the browser not crashing all the time! Quick question, I tried face unlock, it just disentangle work well cause I keep my house pretty dark. How do I get slide unlock back? I switched to pin unlock, and now slide, and face are greyed out n not a option. Thanks!
[Xoom Android Development] PMDColeslaw:
ICS does that after a Dalvik wipe. Instead of just taking forever to boot, it shows you what its doing.
[Xoom Android Development] RampageRR:
This is correct. Just rebuilding dalvik cache, and instead of doing it behind the scenes during the boot animation, you get this cool bar to feel like you've accomplished something.
[Xoom Android Development] cdred:
Is the link down? Getting 500 internal server error.
[Xoom Android Development] dirtymindedx:
TORCH FIX

Open up recovery and install the torch fix. BRD allowing me to post this on megaupload.

http://www.megaupload.com/?d=K8NKVM1G
[Xoom Android Development] lpasq:
>>>> +1 <<<<
[Xoom Android Development] jmandawg:
some better mirrors would be nice, this one is slow when it works
[Xoom Android Development] REHolt218:
Thanks! I am now complete. With the dictionary fix in the Stingray thread and the torch fix from here, every app and feature that I use is now fixed.

I'm loving it!!!
[Xoom Android Development] xBlackDroid:
Does rom server is Off?
[Xoom Android Development] dirtymindedx:
Which link are we talking about. I can add a megaupload link if necessary post a reply and I will do it shortly.
[Xoom Android Development] ajk1311:
Could you please provide a link for the latest nightly (build 37 i believe)?? That would be awesome!
[Xoom Android Development] GinoSylum:
The latest Gapps is needed too.... the original servers are down and we can't get anything
[Xoom Android Development] ajk1311:
Here is a post from the Stringray thread that has gapps 10.2 with a dictionary fix included

http://xdaforums.com/showpost.php?p=21401740&postcount=448
[Xoom Android Development] xBlackDroid:
+1

10char
[Xoom Android Development] dirtymindedx:
if google is down no links possible
[Xoom Android Development] GinoSylum:
Im new to this rom, so a version a day or so old is fine with me. I just want to get it up and running. I can update to the most current version whenever.

Would someone be able to post an older one? 36 or 35? :D
[Xoom Android Development] :
my gps don't fix in build 37.

gapps v10.2 are english only.
[HTC Rezound] tehknics:
Has anyone else had any problems connecting to their PC's?

My new Rezound takes anywhere from 2 to 5 minutes to be recognized on my year old Dell Latitude. After that time the Internal and External SD cards finally pop up on Autoplay (and become available via Windows Explorer). I tried a co-workers identical laptop and it had the same issues. However, I recently plugged it into a 6 month newer Dell Latitude and it works without any problems :confused:

I've also downloaded just about every Android/HTC USB driver I could find at some point too lol.

BTW, it does start to charge on "Charge Only" mode, but the VZW popup garbage still takes the same 2-5 minutes to be recognized. After that point Easy Tether and PDAnet start to work as well.

Anyone else having the same problem?

Thanks!
[HTC Rezound] marclile:
don't seem to have that problem on mine. the drives show up within just a few seconds after i plug it in.