yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] cdred:
First off, installed nightly 55 and its running great. I'm just glad that I can just even use a Xoom ever again after the events of the last 2 days. Woke up Fri morning and the front facing camera just went out for no apparent reason. On day 29,18 hrs. If I had bought the tablet first thing in the morning instead of just before store closed, would have been screwed. 30 day warranty to the second on receipt. Got another one that was dead in box. Had manager open 3rd one in store that also had a defective front camera outta box. Finally went to their other store and got a replacement that worked. Came home and unlocked, rooted and installed nightly 49 from a nandroid backup and then nightly 55. ALL is good in the hood again. If I had to go to another Tab because there we no more Xooms in store, would have been horrible seeing how ICS development seems to be best with TeamEos. Thanks again guys.
[Xoom Android Development] mr_wrong_0:
Just looking for any more info about whether anyone is able to connect to ad-hoc networks on these latest builds. I know most phones can tether in other modes but many cannot so ad-hoc support is important to a lot of users.
[Xoom Android Development] 24v:
I keep getting a warning message in the status bar that says..

"Eos Overclocking Values have not been applied due to recent reboot."

I am running Nightly 55 with the 10.4 gapps. I will try to wipe cache and dalvic and reflash the nightly and gapps.

{edit}So I tried wiping Dalvic and Cache and reboot, that did not fix it. So then I wiped again, and reflashed 55 and gapps, and that appears to have fixed it.{/edit}
[Xoom Android Development] dadoc04:
Epic........ just epic
[Xoom Android Development] leglerreddin:
You need to go to settings, then system, then performance and check set clock values on boot
[Xoom Android Development] okantomi:
Wow! What a run of strange luck!

Glad it finally worked out.:
[Xoom Android Development] ChadH42:
so far 55 is very stable.
[Xoom Android Development] Xoom Master:
would it be bad to run the Xoom at 1600mhz as an over clock? I have it at 1504mhz right now..
[Xoom Android Development] davidsos:
That depends on the CPU that landed on your Xoom in the factory. I've been running at 1.6 Ghz for months without a glitch. BRD from Team eos that cooks our ROMs runs his @ 1.7 Ghz. Some folks can't get past 1.2 Ghz. SetCPU, the app, has a stress test that is a good indicator of your CPU's stability. If it passes, from my experience, it's safe to set that freq. for booting up with. If you boot to a freq. that causes an immediate crash, you will have to reinstall the ROM again or worse, factory wipe and restore your apps and data from backup. Titanium BU is a good thing - hint :cool:
[Xoom Android Development] cdred:
+1. What are the odds? But so far, everything good on nightly 55.
[Xoom Android Development] solarnz:
Correct, not all Xoom's can handle 1.7GHz.

Mine can only handle 1.408.

On this rom, if you use the built in overclocking the rom will detect if the device has rebooted within the last 4 minutes. If it has, it will not apply any overclocking you have applied.
[Xoom Android Development] davidsos:
Originally Posted by davidsos

That depends on the CPU that landed on your Xoom in the factory. I've been running at 1.6 Ghz for months without a glitch. BRD from Team eos that cooks our ROMs runs his @ 1.7 Ghz. Some folks can't get past 1.2 Ghz. SetCPU, the app, has a stress test that is a good indicator of your CPU's stability. If it passes, from my experience, it's safe to set that freq. for booting up with. If you boot to a freq. that causes an immediate crash, you will have to reinstall the ROM again or worse, factory wipe and restore your apps and data from backup. Titanium BU is a good thing - hint

Outstanding ;) You guys should tell us when you do something clever like that, it would probably save a lot of worries for those who are trying to find their CPU's limits. By the way, this ROM is out of sight, AOK.

Didn't know you were from oz.
[Xoom Android Development] REHolt218:
On an early version of Honeycomb I mistakenly set mine to boot on 1.7 and it continually crashed on boot. Rather than wipe everything, I got a plastic bag full of crushed ice and held it to the back of my xoom. I was able to get a stable boot and promptly remove the set on boot option. I was later able to set 1.6 and have been stable on that ever since.

Luckily with the new detection feature you won't have to resort to that kind of foolishness.:D
[Xoom Android Development] rschenck:
Actually that was sort of brilliant in a Gilligan's Island kind of way.
[Xoom Android Development] Xoom Master:
Maybe a rom issue? In the market its trying to make me repurchase the apps to install them.. they are in the not installed section.
[Xoom Android Development] rschenck:
No, market issues are not a rom problem usually. Go to the EOS wiki link in my sig, in the how to section there is a page about fixing market problems.

However, try going to Manage Apps and clearing the cache for the market.
[Xoom Android Development] davidsos:
Originally Posted by davidsos

That depends on the CPU that landed on your Xoom in the factory. I've been running at 1.6 Ghz for months without a glitch. BRD from Team eos that cooks our ROMs runs his @ 1.7 Ghz. Some folks can't get past 1.2 Ghz. SetCPU, the app, has a stress test that is a good indicator of your CPU's stability. If it passes, from my experience, it's safe to set that freq. for booting up with. If you boot to a freq. that causes an immediate crash, you will have to reinstall the ROM again or worse, factory wipe and restore your apps and data from backup. Titanium BU is a good thing - hint

Clever thinking, goes to show that cooler heads prevail. Isn't this ROM fantastic?
[Xoom Android Development] 24v:
No, I had that checked. I even tried unchecking it, reboot, then recheck, reboot. Made no difference.
[Xoom Android Development] eddyther:
great feature!

good to know.
[Xoom Android Development] rschenck:
Dear Team EOS...While we are on the subject, I am still waiting for the feature where my Xoom reads my post on tapatalk, decides I am talking crap and discards the post before slapping me twice in the face. Please get on that, the sooner the better

Also the /make pony command still doesn't work. What the h-e-double-toothpicks are you people doing with your time?????
[Xoom Android Development] fprice02:
For the life of me I can't remember how to change the name/model number. It currently lists as Full Android on Wingray. For some of the games I purchased (asphalt 6, Captain America etc) i believe it needs to say Motorola Xoom or just Xoom. Or is the game reading the 4.0.3? Is there a way to change the name/model number? Thanks in advance.
[Xoom Android Development] jgardner:
You'll have to change your build.proc in /system to get it to show. You'll see in there the specific values (can't remember off the top of my head), but it's something like vendor and model.
[Xoom Android Development] rmcsc:
What maxoxa is saying here, for all you people that can't open up a translator, is, basically, calm the f*** down. Drivers will come when they're released.

Sacre bleu, I see what you did there! Do you really speak 3 languages. That would be a relief, knowing I'm not the only one here capable of doing so.

But I digress.

I had been trying to change the values so they registered as a Verizon Xoom on the Market but I've gotten no such luck. If you get it to work, care to share it?

Also, I have had some apps not open for me / crash that didn't happen in the other AOSP ROM. They show a black screen, then crash. This is a hardware acceleration problem, right? If so,how come I could get them to run on the other ROM? Sheer luck, I guess? One example would be the recent 10¢ app Train Conductor 2.
[Xoom Android Development] REHolt218:
Drew Garen has a build of ICS with working 3g. I have a US Verizon 3g/4g Xoom, and when i put "network Mode" to "CDMA" 3g works.

In LTE/CMA mode I get nothing.
[Xoom Android Development] rschenck:
I figured it was something like that...even without the translator.

However I was not just being anglocentric. XDA has a rule that posts should be in english, and they have banned over it in the past. Google translate may at times be hilarious, but it is better then getting banned.
[Xoom Android Development] rockhumper:
Has anyone else noticed that they are getting issues with backups in cwm being completed correctly? My last three backups done in recovery mode have said something about needing to skip boot img. Then when i flash a backup it is clearly not loading my previous backup....it goes through the motions but then it comes up with the new boot animation and other features that were not part of my last backup
[Xoom Android Development] REHolt218:
I have not seen that. I have made several back-ups today and yesterday with no issues.
[Xoom Android Development] rockhumper:
Did you make your back up in recovery or using clockwork?
[Xoom Android Development] btate0121:
yeah, running into this right now actually. I suspect its switching from the cwm 3 rc 4 to the cwm 3 via from manager that did it. Going to reflash ,y original cwm version to verify in a minute
[Xoom Android Development] jgardner:
I believe all I changed was the following and it showed up as a Motorola Xoom in Amazon

ro.product.model=Xoom

ro.product.brand=motorola
[Xoom Android Development] REHolt218:
I used CWM
[Xoom Android Development] xBlackDroid:
Well if someone want watch a little about this rom before install it, i make a little video, i hope no body bother this

http://www.youtube.com/watch?v=sWkXowvTfrE&feature=youtu.be
[Xoom Android Development] rockhumper:
Ok i will try that instead of doing it in recovery. Maybe doing it through rom manager will work for me.

One more question for all...are u having problems where every few times of going into the gallery u get more and more random empty blank thumbnails? Im talking hundreds....i have lots of wallpapers externally and i keep gettimg hundreds of black empty pictures in my albums...but in the actual folder using root explorer there is no sign of anything funky

---------- Post added at 02:23 PM ---------- Previous post was at 02:22 PM ----------

Pulling the sd card and putting it back in fixes the problem...forgot to add that...the fix is only temporary though
[Xoom Android Development] sodaboy581:
Good job at spelling the Team name wrong multiple times. "Eon"? No, it's "Eos".
[Xoom Android Development] Xezuka:
Excellent work!
[Xoom Android Development] rockhumper:
Where did u change this info? I have the same problem with android market....some apps will not work because my device says all android wingray
[Xoom Android Development] atcwoody:
+1 on gallery pix not showing. However my music is displaying and playing just fine with Player Pro.
[Xoom Android Development] double1:
Just switched over from the og rom and this one is fast as bleep with the oc kernal. Great job. Was wondering if there was a change log between the different nightlies so we can see what's changed?
[Xoom Android Development] jgardner:
You have to change /system/build.prop

I used ES File Explorer, then go into the settings and at the bottom enable Root Explorer and Mount File System. Then you can move up from the /sdcard folder and go into /system. As always, I'd recommend either a nandroid backup and/or backing up the build.proc file.
[Xoom Android Development] Arknox:
You need to reboot after, in order toi take the modifications into account
[Xoom Android Development] cdred:
On nightly 56 and all is well. WiFi seems to connect quicker and getting better wifi speeds.
[Xoom Android Development] joeyddr:
Just had a reboot with 56 while the screen was off and it was charging
[Xoom Android Development] al mon:
Reboots on Nightly - It would probably help to know if you were over clocked when it rebooted. In the past, many reboots could be attributed to running the device at a high CPU speed and the CPU/thermal regulator kicks in.

Please when reporting reboots also include OC status.
[Xoom Android Development] joeyddr:
it was OC to 1504 like it was with 55 and 49 and HC stabily...
[Xoom Android Development] fidju:
Try bumping it down to 1200. ICS is already screaming fast and 1200 has been completely stable for me on every single nightly so far.
[Xoom Android Development] rschenck:
Overclocking is a very finicky science. A setting that hums along perfectly on one build may burst into flames with the next.
[Xoom Android Development] JamesRC:
Great build thank you! The only issue I have us the browser crashes when trying to run BBC I player in HD... only tested nightly 56 so may not have ever worked!
[Xoom Android Development] eddyther:
@bigrushdog, problem solved with the last build! :)
[Xoom Android Development] pr1vate piles:
Just updated and working fine. All apps working without any problems.
[Xoom Android Development] slacka-vt:
Very obvious improvement with wifi on build 56. A video podcast I'm subscribed to would always buffer and fail after 5 minutes on previous nightlies. On this build I watched the entire 45 minute video with not so much as hiccup. I always watch while in bed so the AP and my proximity to it is consistent. Thanks so much.. Awesome work.
[Xoom Android Development] fidju:
Browser loading speeds feel a little faster for me on 56, but YouTube HD videos are still not buffering fast enough and Netflix is stuttering as per usual.
[Xoom Android Development] mongday:
Change log of Jan,31 is

type: stats

rowCount: 0

runTimeMilliseconds: 48

What is the change?

Thank you.
[Xoom Android Development] rschenck:
If the changelog is empty, then no changes were included in this Nightly.
[Xoom Android Development] davidsos:
This should make it into the next build.

Add Wireless Tether controller to Eos Quick Settings.

http://bb.teameos.org/changes/401
[Xoom Android Development] Hasilpuri:
Hows the battery life on 56? Its only lasting just over 24 hours after moderate use.
[Xoom Android Development] jonman364:
That looks like it is for tethering a device to your Xoom, not tethering your Xoom to another device, providing the Xoom with Internets. Wifi Xooms would not need this feature.
[Xoom Android Development] cdred:
+1 on reboot. I have been running @ 1408 max, 816 min ondemand. Happened only once though. Will continue to monitor and post results. Nightly 56 running good with improved wifi as reported earlier.
[Xoom Android Development] 619headman:
How's 57? i had a lot of freezes at 53
[Xoom Android Development] joeyddr:
another reboot with 57 running @1.4ghz..... same thing screen off and charging.
[Xoom Android Development] emreng:
ics @1,2ghz is really fast enough in my opinion. i don't need for higher frequencies. no reboots at that point w/ wingray_57. so far so good.
[Xoom Android Development] lucifergil:
Got sleep of death twice today on nightly 56.
[Xoom Android Development] joeyddr:
does it just not wake up when you get that?
[Xoom Android Development] lucifergil:
Yep, I had to use volume up+power to reboot.
[Xoom Android Development] edboston:
Were you overclocked?
[Xoom Android Development] lucifergil:
I am overclocked but I am also one of the lucky few that can run at 1700 with 75mv undervolting stable for an hour of benchmarks. As far as I know, the xoom goes to deep sleep when the screen is of where OC/UV is irrelevant.

I got my first SOD on nightly-53 after the new kernel was introduced, so I think it is kernel related. For now I'll revert to nightly 48 until all these problems are resolved.
[Xoom Android Development] inmanster:
52 was rough for me this past weekend. Had random reboots and the death sleep at standard clock speed and WiFi off. Flashed 56 yesterday morning and so far no reboots or and funny business and battery life is great. Today I've on and off the WiFi at work and I'm overclocked to 1408 with 91% battery life left (unplugged since 6:30am).
[Xoom Android Development] Blondblueyed_girl:
Running nightly-56, with no over clocking. This is the best so far, no lockups or other problems, except HD Video running from sites like youtube still dropping some frames, but its not too bad and hard to see. All in all running much smoother than all previous nightlys. Well done guys
[Xoom Android Development] TheBlueRaja:
Are there any faster download links available? i only ever manage around 33kbps from the goo server.
[Xoom Android Development] okantomi:
Someone posted something on governors yesterday from rootzwiki and it did indicate that certain governors can take the device into such a deep sleep that it's hard to wake up. Also, undervolting may affect that process. With a new kernel, the parameters may have changed some. It's worth experimenting a bit.
[Xoom Android Development] joeyddr:
got another reboot plugged in and charging with no overclocking at all...
[Xoom Android Development] Mindoy:
Hi all,

Since 56, I have a lot of Sleep Of Death. Before, never have problem.

My Xoom stuck sometimes at Motorola logo.

BAck to 49.
[Xoom Android Development] WarLion:
I go back to nigth 50 on 56 after a few minutes using my xoom become real slow ,
[Xoom Android Development] bpick:
For what its worth, I always immediately switch to on demand governor and 1200. I have never experienced a single issue. I have flashed EOS and RogueCM9 without issue many times.

Maybe there is something to the governor theory?
[Xoom Android Development] jodtalingchan:
Since there are few complaints about reboot, why don't you guys try build 54? It is very rock stable for me with OC 1200 / 400 interactive gov...
[Xoom Android Development] eddyther:
I have v. 56, interactive at 1504 with no problems (since v. 32). I never had a single reboot or deep death.
[Xoom Android Development] stonebear:
I was using the Stachre ICS rom and flashed EOS 57...I did a full wipe before flashing EOS but I am getting FC's on some things, Gmail and Market.

I have done some searching about it and it seems that choosing "fix permissions" might help?

edit

I think it might have fixed it. No FC's for a while now.

another edit

7 hours later, been using the Xoom off and on doing various things and no FC's. So fixing permissions does seem to have fixed it.
[Xoom Android Development] jessman1988:
I hate to troll but what's the status on ad hoc connectivity? If its not high on the EOS agenda I promise to respect that what no further inquiries. Is it just me or do a bunch of us have OG droids? I know I should just opt for a newer phone but it's just not in the cards right now. I switch from 1ghz to 1.6 when benchmarking but I've never had a random reboot. Its quite curious how some have these issues while others don't. Thanks as always for your great efforts and strides with ics, EOS. I've found a rom to stick with. No more switching for me. :)
[Xoom Android Development] eddyther:
did you flash the gaps just after the rom and before the reboot?
[Xoom Android Development] stonebear:
Yes.

The message you have entered is too short. Please lengthen your message to at least 10 characters.
[Xoom Android Development] aR_ChRiS:
Nightly 58 seems to have solved the sleep problems on my tablet (but not my own sleep problems =( )
[Xoom Android Development] inmanster:
56 was rock solid for me. After work last night I used it for viewing pdf files while writing Arduino sketches on my laptop while watching UNC play Wake. Streamed watched a couple video files on it to put me to sleep and then this morning read an epub while eating breakfast. Before coming to work I used Root Explorer to do some file maintenance played a quick little time killing game. Battery life was great and it was always responsive. Seemed solid enough to be a daily drive for me.

This morning I'm going to flash 58 and see if it gets even better.
[Xoom Android Development] joeyddr:
really? only thing that changed was init.d support.. according to the changelogs.
[Xoom Android Development] bZerk:
Is there any nifty way to get USB-host to work with this ROM?
[Xoom Android Development] okantomi:
Should be working...works for me.
[Xoom Android Development] bZerk:
Yeah, sorry about that. Seems like I had a bad USB-cable, and I also have camera that none of the remote-apps in market has full support for. :o
[Xoom Android Development] Dyelon:
Hey guys, I'm need of some SERIOIUS help.

I'm running a nightly from a few weeks ago, and everything's been great. But today, I used font installer from the market and I changed ALL of my fonts to a custom font....it said it needed to reboot to process changes but upon doing so I have been in a constant boot loop

I tried wiping Davlik cache, regular cache

I tried flashing a zip called "fontfix.zip" from a thread for a similar problem...did not work

I just get TEAM EOS blue logo spinning forever....

Anyone have any advice besides restoring to before I even installed the ROM? I REALLY don't want to lose all of my data

Also, to add, I tried USB mounting the internal memory but my computer did not seem to recognize it
[Xoom Android Development] btate0121:
a suggestion... i'm not responsible if you break something LOL...

I would personally try flashing the rom again if you still have it on your SD.

boot into recovery and flash it without wiping anything.. I think that may flash over whatever you've changed without erasing your data.

If you don't have the zip on your xoom still you should try using a card reader to load it on your micro SD and try it that way.

I hope this helps!
[Xoom Android Development] Dyelon:
DING DING DING!

We have a winner!

Thanks man, did the trick completely! I really appreciate it! Now I can try my Jot Pro that just came in the mail...!

EDIT: crap now my market is FCing upon opening...wtf!

EDIT2: When I rebooted, it basically flashed the ROM again with the "optimizing application 1 of 166" message before it would boot....is this going to happen everytime?
[Xoom Android Development] btate0121:
OOOPS... forgot a step. You should have reflashed both the gapps and the rom. That should fix ya.

I would go back into recovery.. flash the rom... then the gapps then reboot.

I keep forgetting this is a custom rom (i'm running the stock one) and you'll need gapps to get the market, mail, etc.

I hope this helps (more completely)
[Xoom Android Development] Dyelon:
hey dude thanks alot....I can't ****ING believe I forgot to flash the GAPPS zip AGAAAAIIINNNNNN....

I did the SAME. EXACT. THING. LAST. TIME. I. EVEN. POSTED. ABOUT. IT.

*shaaaaammeeee*
[Xoom Android Development] dirtyyy:
On my WiFi bar at bottom corner I seem to get a couple of random pixels show up over it. I thought this was a problem with build 44 but now running 58 I see it still has the problem.

Anyone else notice this, any ideas?

Thanks
[Xoom Android Development] zacharias.maladroit:
nope, reboot & see yourself ;)

it's only doing that after flashing some additional stuff

or doing some major upgrade
[Xoom Android Development] niko_slo:
What are you guys using for benchmarking???
[Xoom Android Development] Cubanluke88:
People really need to stop ****ting this thread up with problems outside the scope of the rom. If you start doing tweaks to your xoom that are questionably related to this rom, don't post here. Post in the q/a forum.
[Xoom Android Development] dirtyyy:
Wifi icon glitch

This is the wifi glitch i seem to be getting.

It goes on and off. Also a little bit more occurs when my wifi signal strength is higher.

I first noticed this on Eos nightly 44 but thought nothing of it as i thought it would be cleaned out soon after but now going onto Eos nightly 58 it still has it.

Has anyone else come across this problem? I take it this isn't suppose to happen..

Thanks in advance
[Xoom Android Development] okantomi:
No, it does it when you have wiped the dalvik cache (as you should) because the dalvik virtual machine will rebuild. Maybe I'm not explaining it right, but welcome to nightly builds!
[Xoom Android Development] solarnz:
Are you referring to the triangles in the wifi signal icons?