yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] brittoking:
Just about everyone in this forum, if you actually read the posts, uses this as a daily driver, with very little negligible problems that have popped up in different builds. So your statement baffles me that it's FAR from being usable as an every day ROM. Furthermore if you are bothered by wiping data and dalvik, and the 30 second wait for the apps to "optimize", Means you really have no business flashing roms period. That step is sooooo very easy, it's odd you would even think to remark on it. I could agree with you, and would, if we needed to factory reset/wipe user data and manually repopulate every app after ever single solitary nightly.......sure that would be a "deal breaker" for a lot of people! My last statement would be regarding your statement about people "choosing" to use this ROM over stock...........Ummmmmm where is that Motorola Xoom 4g device ROM exactly? Who's choosing this over a ROM not even fully released by Motorola exactly? This IS a 4g device forum not wifi btw, And lastly to the members of EOS, congratulations on such a very, very functional ROM built from scraps and pieces. Your progress and level of polish is amazing, and greatly appreciated here.

EDIT: I own every Gameloft game made for the Xoom, and even some not natively built for it, and can play without so much as a line flashing thru the screen. NO GLITCHES HERE. Everyone's experience will be different granted, Xoom to Xoom, ROM to ROM, etc.
[Xoom Android Development] buzzdroidx:
Obviously there must be alot that is 'beyond' you. I haven't had a single problem with it so far. I use my tablet daily with moderate usage. All my Gameloft titles run great. Wiping is of no consequence, takes mere seconds to do. Maybe your lazy or maybe you just cant be bothered, but that's no excuse to comment like that in a DEVELOPMENT thread. This ROM runs buttery smooth for me at stock clocks. Unfortuneatly I can't compare it to the virgin ICS, and probably neither can the greater percent of posters here, so for us to think this rocks the socks off of our former HC experience.... well there you have it. And BTW since it could in "no way could this even come close to a daily driver for me yet" why post here at all go post in a forum that supports your "daily driver"

OH Brittoking you type faster than I do lol
[Xoom Android Development] nhlpreds98:
Thanks, I had no idea you could do this. Just fixed all my market updating issues.
[Xoom Android Development] otis_bartleh:
No problem.. :)
[Xoom Android Development] tomcrown1:
How come their is no nightly for 1-25-12. The change log does show EOS 33 with a bug fix, but none on the down load page.
[Xoom Android Development] liftman-:
on clean install:

twitter and +google not syncing in background and giving notification.

I can manually refesh

anyone else?

already tried clearing data
[Xoom Android Development] brittoking:
Haha! You said it perfectly though...IT'S A DEVELOPMENT THREAD......so help develop thru questions, bug reports, praise, etc. etc.
[Xoom Android Development] hammer4203:
For the record I wipe every time I flash a new nightly. All my games work fine on 32. Whatever nightly comes tomorrow I will wipe and manually install my apps and data to make sure titanium backup is not causing the dolphin browser to quit and the black screen flash every once in a while. Which I think is the issue. Thank you for all the work Team EOS!!!
[Xoom Android Development] jfvidalc:
Add me to the list of users with who use my xoom daily and update it daily (currently on build 32) and currently have no issues. The last time I did a factory reset was over 8 builds ago.

When a new build is out, I just go into recovery, run a nandroid backup, wipe cache/dalvik cache, and install the latest build followed by the latest gapps. After the reboot, my xoom is running without any problems (overclocked at 1500, with setcpu profile with lower clock when screen off).
[Xoom Android Development] kcrudup:
Since it only matters once you boot (Recovery doesn't examine nor build the Dalvik cache, and only monitors the /cache partition looking for an OTA update) it doesn't matter if you wipe before flashing a ROM or after, as long as it's done before the first boot.
[Xoom Android Development] SamuriHL:
Good to know. Just out of habit I've always done it after flashing, but, before rebooting.
[Xoom Android Development] otis_bartleh:
That is good to know, I've always done it before flashing, also out of habit! :)
[Xoom Android Development] tonesto7:
Hi Everyone i'm having an issue connecting to the wireless at work...

We use a hidden SSID named "DWIFI" 802.11x PEAP MSCHAPv2...

I seem to be getting this error and i'm not sure if its a wireless driver issue or not.... Here is the logcat output from MotoDev...

Could someone shead some light on this please?

01-25 18:42:48.051: INFO/wpa_supplicant(4177): wlan0: Authentication with 00:3a:98:62:61:60 timed out.
01-25 18:42:48.111: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
01-25 18:42:48.111: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
01-25 18:42:50.011: INFO/wpa_supplicant(4177): wlan0: Trying to associate with 00:3a:98:62:61:60 (SSID='DWIFI' freq=2412 MHz)
01-25 18:42:50.041: INFO/wpa_supplicant(4177): wlan0: Associated with 00:3a:98:62:61:60
01-25 18:42:50.041: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
01-25 18:42:50.761: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17 -> NAK
01-25 18:42:51.091: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
01-25 18:42:51.091: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
01-25 18:42:51.681: INFO/wpa_supplicant(4177): EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
01-25 18:42:51.991: INFO/wpa_supplicant(4177): wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
01-25 18:42:52.011: WARN/wpa_supplicant(4177): EAPOL: Failed to set WEP key to the driver.
[Xoom Android Development] thehotboy:
i too use this as a daily driver n have only done 1 factory reset in +20 nightlies i've flashed n have encountered no problems what so ever .. i can't even believe that this is an alpha ROM considering how amazing it is .. TeamEOS has done a great job & has helped me love my xoom even more
[Xoom Android Development] brittoking:
My exact process as well, including the overclock speed and screen off lower clock!
[Xoom Android Development] kcrudup:
FWIW, I've been building and using the Team EOS stuff (with a (very) few of my own changes) for about 3 weeks now, and it is my daily driver (YMMV, of course, and I couldn't care less about games and have no idea how well they run, but all's been well for me and I need my X up and running daily for my business purposes).
[Xoom Android Development] rdtshaw:
Omg, this rom is unbelievable. I have flashed alot of Roms, (phones and other tablets),and this is one of the most trouble free ones I have used. This is BEYOND acceptable as a daily driver. Battery life is better, and running it under clocked is even better with no noticeable speed issues. I'm in IT and I work out of my car. My xoom has replaced my laptop for 95% of my needs, and is even better with ICS. Remote control, exchange client and web browsing are working great for me. Always a bummer to see the negative and unproductive posts like that.
[Xoom Android Development] oldblue910:
I think you all misinterpreted my post. The ROM is a great start, just in my opinion, it's not stable enough to use as a daily driver for what *I* use my Xoom for. Maybe I didn't do a very good job phrasing my words properly. Again, I'm a software developer and I understand how these things go.

Didn't mean to ruffle any feathers. :D
[Xoom Android Development] kcrudup:
Not always, if it's done objectively and with some common sense and valuable feedback (i.e., "U guys suck!" posts can KMA). There's no such thing as a perfect build, but this set of nightlies come close, and will only get better once Moto releases the real build (so T-Eos can snatch the goodies out of it to incorporate into their build:) ). Personally, I'm pretty happy with the efforts of T-Eos.

(... So the next time someone considers posting something akin to: "Moto sucks" or "Moto's abandoned us" or "Moto should hire <insert Developer or Team here>, they can do what Moto can't", just keep in mind that there's more to releasing a quality ROM than just putting one out there.)
[Xoom Android Development] danyzfr6:
I have had no problems at all with this ROM. EVERYTHING works, 4G, 3G, WiFi, GPS. I was prepared to give up some things to run ICS, but, to my surprise, everything seems to just work. And not only work, but work better than the Xoom Honeycomb stock ROM. Good job guys!
[Xoom Android Development] liftman-:
brd where did you get the 9m in /system?

thx
[Xoom Android Development] razorseal:
To be honest with you. I have no problems. And im on 27.

My up time right now is 90 hours.

To tell you how much I use it... I use this thing straight for 7-12 hours a day on 4G and wifi at night. , and sometimes kill the battery. My Xoom is extensively used. And not once did i have a problem where it became unusable. The worst I've had is 2 force closest in a row with the browser. And one force close on usaa app. Besides that its been running stellar. Which is the reason i saw no need to upgrade to a new nightly.
[Xoom Android Development] hammer4203:
alrighty then! To verify what I thought was causing my issues. I wiped and installed nightly 36 with gapps 10.4. All apps pushed from my PC in android market. Only restored data to apps like dolphin, medscape, xda, etc from titanium backup. No more black flash on the screen and dolphin is working smother now. I did notice that system data in titanium is different than what is in the new nightly. My thoughts are don't restore anything put an apps data, no system stuff at all. It seems to cause an issue with the new nightly. And that does make sense, because if the nightly changes system data and titanium restores old data, it would screw something up. At least I don't have to hunt all my favs in my browser down.
[Xoom Android Development] SamuriHL:
Um, restoring system data from titanium when going to a new rom is a VERY bad idea. It's pretty much the same as not wiping the cache. :) You're simply restoring the things that are likely to cause problems. I don't even restore app data on a lot of apps. I do for games and such, but, most apps I restore only the app. And doing it this way, I never seem to have major issues. Restoring system data is definitely not a good idea when doing roms.
[Xoom Android Development] Asphyx:
I completely agree on this. Titanium Backup is a useful tool to restore apps to the same ROM it was made from but not the best way to go when you are chasing a nightly development ROM. When I was helping the devs work on the CM7 for D2G we found it neccesary to ignore any bug reports from those who used it!

Well I find it plenty stable so I don't know what you are using it for. Are there issues? Of Course there MUST be it's an AOSP build and comes with all the issues AOSP brings to the table. If AOSP was perfect there would be a whole slew of Google Programmers looking for work right now.

It may not be as stable to you as the ICS Soak Test floating around but then again it doesn't have the bloat from Moto, Has NTFS support via USB and a whole bunch of improvements that most folks don't notice without reading this thread.

Most of the folks posting issues are chasing Nightly builds and flashing a new rom each time one is released. They are bound to have issues due to bugs included in the new nightly or due to bad flashes and wipes. Many are probably also using Titanium Backup which I have already commented on.

If you read the threads you would find that Release .27 is the most stable so far and you should probably use that as your daily driver.

Install, set it up and make a nandroid before you go trying one of the later releases and if you find it unstable you can always flash back to your daily driver!

Some folks are just flash happy and flash anything that they see released. Not the best practice. Try them out, read what issues get reported and if you have them, run back to your nandroid Daily driver and wait for the next release.

Some folks just don't get how these things work.

If you had mentioned what WAS Unstable for you then maybe people would not have gotten on you...
[Xoom Android Development] otis_bartleh:
Also agree, thats why I only restore user apps with data, and not restore anything from the system backups. Then MBP for home screen icons. It really is a great combo for restoring almost everything but system data, and have had almost no problems through any nightlies, and my Xoom has also seem quite a few times of 7+ hours of straight use and been extremely stable...
[Xoom Android Development] Asphyx:
Even then, Depending on the app it can mess up some settings from the previous data structure that are not compatible with a new build.

Should not be a big issue if your restoring a Backup from a previous install of the same rom but it's not a sure thing that Titanium won't introduce problems.

Titanium is not really meant to do anything but be a backup for losing a system and having to reflash that same system and get back where you were.

Not really the tool for going Rom to Rom.

It does work but not always with the best result.

If you want to play with Dev Releases and make Bug Reports most Devs prefer you don't throw Titanium into the equation.

I won't speak to Team EOS' position on this though.
[Xoom Android Development] SamuriHL:
I need to grab MBP so I can backup the home screen icons. That's one thing I really hate doing. What I'd like to do is restore my HC backup, snapshot my home screen icons, and then restore the Team EOS ICS build and restore the home screens. Cause what I have set now is just a shell of what I had before cause I'm too lazy to take the time to set them up again....mainly in case I have to factory reset again.

---------- Post added at 12:30 PM ---------- Previous post was at 12:24 PM ----------

I honestly haven't had an issue restoring most apps with no data except for games or things I know won't interfere with the system. And that's on both my phone and Xoom. But your point is very valid. If you do run into problems, it'd behoove you to nandroid what you have, factory reset the rom you're having issues on, and restore apps from the market cleanly. Then if the problem persists, you're good to restore your nandroid, and if it goes away, get setting stuff up. :D
[Xoom Android Development] otis_bartleh:
I completely see your points. I tend to not make bug reports based on this same reason, I'll post here instead seeing if others have the same issue. I don't want to make a bug report knowing I am restoring stuff, even if it isn't system data. Although this method has always seemed to work well for me, I do understand it's never guaranteed! Thats why there are pros and cons to playing with nightlies... With this rom, I love the nightlies, downloading newest now... :)
[Xoom Android Development] Asphyx:
I use Elixr for all Icons. It will let you make a backup of each widget you have created that you can easily restore and place on the screen. I have yet to see an App that restores Widgets to their position but I tend to favor Widgets that allow you to backup their config and once I have restored all my apps It's pretty easy to restore my screens the way I want them.
[Xoom Android Development] otis_bartleh:
That sounds pretty cool! None of my widgets really need configuration, but I think I'll check that out anyway. I'd love for an app to save and restore widgets in the same location, now that would be awesome...

Also, I just noticed on the most recent change log, it mentions being able to toggle on wifi and bluetooth while in airplane mode, but I've been able to do that. Am I missing something, or reading the changelogs wrong?
[Xoom Android Development] hammer4203:
I had no idea doing a full restore could cause so much chaos. I do know that Team EOS has made one hell of a working system here! So far nightly 36 has been perfect! Thanks!!
[Xoom Android Development] hammer4203:
Wifi and Bluetooth both toggle when in airplane mode. That's why I just started from scratch to see if it made a difference. It really does!
[Xoom Android Development] SamuriHL:
I'm rebooting into 36 now. I simply did a wipe of cache and dalvik. But I decided to throw a backup on after doing the cache wipe and upgrade so it took a bit longer. I've not had any problems with any of the nightlies tbh. And I use my Xoom quite a bit.
[Xoom Android Development] bigrushdog:
Can you clarify? I'm half awake ...
[Xoom Android Development] iNdioNicarao:
I have a Verizon Motorola Xoom that i got off contract (NO data plan/service) if i had airplane mode on (4G radio off) would not allow me to control the bluetooth and wifi from the quick settings. Going into the settings screen to enable/disable was never an issue. This request was put in to accomodate folks like myself that have a 3g/4g radio but don't want to use it and DO want to be able to control the bluetooth and wifi from the quick settings menu.

:D
[Xoom Android Development] stevefxp:
Why not go into Settings/More/Mobile Networks

Uncheck Data Enabled and then you have no data, but still can control Wifi/BT/Etc?
[Xoom Android Development] kcrudup:
That doesn't actually turn the radio off, though- so it still sucks down power. It's the same as turning on WiFi but not Airplane Mode- the battery-draining LTE radio is still on (which can benefit GPS fixes, but that's about it :)) even though you're not using it for data.
[Xoom Android Development] nubsors:
I feel the same way. I don't even think I will return to stock when the official ROM is out. It's basically pointless now. This ROM is better is all but one respect... Google Movies.
[Xoom Android Development] liftman-:
late night with the hookers,

9 megs free in /system? where did it com from?

remember it was under a meg free, face lock crap was using like 18megs in pittpatt.

you had me move it to /data and symlink (which worked)
[Xoom Android Development] solarnz:
... I shrunk the kernel. CIFS and NFS are now built into the kernel instead of as extra modules. Each of these modules were 3MB each.
[Xoom Android Development] liftman-:
ahh thanks

I hope your getting your share of booze and also
[Xoom Android Development] johnny0911:
I did a quick look over the recent post and didn't see anything with random reboot with Bluetooth and google music. I have been having random reboots when playing music over bluethooth' about every 5 min or so. Anyone else?
[Xoom Android Development] SamuriHL:
With 36 I'm getting random reboots with it just sitting on the dock. I have a feeling it's wifi related as I don't have BT enabled and I'm not even doing anything with it when the reboots happen. It's rebooted about 4 or 5 times on me today.
[Xoom Android Development] johnny0911:
That is interesting because mine was also in the dock when I was having reboots, so just put it in the dock and listened to some music for about an hour and no reboots. Only seems to happen when I have Bluetooth on running 36 gapps v10.
[Xoom Android Development] SamuriHL:
Mine rebooted on me a few minutes ago out of the dock. Only activity was trying to redownload 32 as I intend to go back and see if the issue continues. It's still downloading so hopefully it doesn't reboot again in the middle of it. Yes, I should keep the downloads. But up until now I hadn't had a problem.
[Xoom Android Development] Pihrana:
I had the same issue (Random reboots that is) with #36.... My solution was to reflash #32. Then perform a factory reset. Flash #36, Flash G-apps 10v4, and its been working fine ever since....
[Xoom Android Development] SamuriHL:
Yea, that's most likely in my future but I'm not in the mood to deal with a factory reset right now. I'm back on 32 for the moment and if that's stable I'll hang with that until the next nightly. If the next one gives me reboots again, I'll factory reset at that point and go fresh.
[Xoom Android Development] EtchG:
I was having a fatal sleep issue when the CIFS and NFS modules were brought in. Making them part of the kernel rather than add ons appears to have corrected the problem I was having. Been on all day and not one deep sleep.

I had one sudden reboot shortly after flashing #36, but after that things have been pretty smooth.

Now if the ROM gets a full IPSEC VPN (Group name and password) I will have pretty much everything needed to do do my work while on call without having to drag my work system out.

I must tip my hat to the EOS team on just how awesome they all are.
[Xoom Android Development] tomcrown1:
I get random reboots while viewing the browser on 36. Did a fresh install and still get the reboots even thou I am not over clock.
[Xoom Android Development] SamuriHL:
I suspect a network issue with 36, personally. My Xoom has been ROCK solid up until then. I'm back on 32 with nothing more than a cache and dalvik wipe and I've not had a single issue since I booted.
[Xoom Android Development] johnny0911:
Yeah I think I'm going back to 32 as well.
[Xoom Android Development] rajones19:
Same here. Several fatal lockups today, which I have never, ever, experienced on the Xoom. #32 is running rock solid.
[Xoom Android Development] SamuriHL:
Yea, it's still stable for me on 32. So let's hope the issue is identified and fixed in the next nightly.
[Xoom Android Development] jfvidalc:
I've been running on bld36 since early this afternoon with no problems.
[Xoom Android Development] buzzdroidx:
I loaded 36 up this morning and it hasn't rebooted once. Browsed the interwebs, listened to alot of music google talked all on wifi and nary a problem here stock clocks etc
[Xoom Android Development] SamuriHL:
Are you people that aren't having issues doing factory resets?
[Xoom Android Development] johnny0911:
I did factory reset, dev cash, wipe cash all the normal stuff. This is the first problem I've had.
[Xoom Android Development] SamuriHL:
So you did a factory reset and are still having problems. Ok, something weird's going on then.
[Xoom Android Development] nhvrod:
36 caused mine to reboot every 5 minutes or so. I just flashed back to yesterday's and all is well.

Sent from my Galaxy Nexus
[Xoom Android Development] liftman-:
You guys restoring goo apps and data in tibu are dragging crud back in after you wipe.
[Xoom Android Development] otis_bartleh:
User apps only here...

Also had serious rebooting issues that I've never seen before, full factory reset prior, like always. The reboots first were happening after I restored my apps. So I reflashed the ROM and didn't install any apps, just browsed the web, still happened... Restored my 32 and all has been good again, might actually go back to 27 or so, that's when it was flawless on mine... Factory reset and cleared caches between each flash too...
[Xoom Android Development] SamuriHL:
Yea, I haven't cleared my apps in quite a while....basically since I started using this rom. But I do wipe the cache and dalvik every single time I upgrade to a new nightly. And I've not had any problems at all up until 36. Going back to 32, with the same apps + cache/dalvik wipe, has been rock solid again. So while I agree that tbu app+data restore is probably not the best of ideas, I don't think it's the cause of this issue.
[Xoom Android Development] razorseal:
Does data usage in settings show wifi and mobile?

Cuz it shows 490 mb in 4 days which sounds alot lol
[Xoom Android Development] jfvidalc:
I haven't done a factory reset since the early 20's build. Bld 36 is running OK for me.
[Xoom Android Development] Pihrana:
How can you check your tablets 'up' time? I did the above and didn't have any Issues for the rest of the day / evening... just got up and my tablets screen was on (sitting in my dock). I always make sure I turn the screen off before sleeping... So the only thing I can think is that it has rebooted at some point in the night.

Anyway, #37 downloaded so time to move on :-)