yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] cantos:
Anyone else seeing issues trying to open the Google Play Store and having it immediately minimize and close?
[Xoom Android Development] Mjamocha:
Thanks. Yeah, I know disabled voice. You still need a data plan to use with google voice and carrier data rates apply. Watch your bill carefully. GrooveIP would be a better choice requires no carrier and work over WiFi. Just say'n.
[Xoom Android Development] smiznith:
Anyone having wake issues? Just updated to 138 and have had to soft reset twice because it won't wake up.
[Xoom Android Development] daryldc1991:
Strange thing happened to me today, that I would like to share. Last night I downloaded 138 and flashed, from 136 to 138, while only wiping the davlik. This morning while using my xoom I noticed I had a 4G connection since I used its navigation to get to my first stop. After driving to work I then noticed I did not have a connection on the xoom, 3G or 4G. My phone had a 3G connection, but no connection on the xoom. This went on most of the day. I would have a 4G connection but no 3G connection. Finally while I had some idle time I decided to flash 138 again. This time I wiped the cache and davlik. 3G and 4G started working perfectly. From now on I think I will wipe Davlik and Cache before flashing new roms.
[Xoom Android Development] Asphyx:
Whats worse is VZW will send you bill information via SMS and charge you for receiving them!

I have one somewhere around here probably in the box I call the Cell Phone Graveyard! LOL

Check out GrooveIp. Both Incoming and outgoing voice calls and over WiFi too.

Agree!
[Xoom Android Development] bigdave240:
I have one of those bt gps modules too and it hasnt been used in a couple of years until i had to visit a bunch of cell sites to do maintenence. I used it with a current version of streets and trips and found the sites with no problem using lat/lon. Nothing else would allow me to import the coordinates from excel and then give me accurate directions to them. Even when you can see the tower you cantlways figure out how to get up to them. Nice to have the "old" technology sometimes lol
[Xoom Android Development] billblack:
I have had one instance of the tablet not waking up. I have also had 2 spontaneous reboots. I hadn't had any issues since the kernel changes a few builds back.
[Xoom Android Development] bacon612:
Hey. Thanks for sending this along. I tried to install the apk that you sent me but had to luck. I get an installer error that says "app not installed". I think you are right in thinking that my camera app issue is related to gallery because gallery won't open either. Any other ideas?
[Xoom Android Development] kcrudup:
Couple of things:

- I'll bet you anything it wasn't locked up, but unresponsive. Next time, wait 5 or 10 mins and see if it wakes up again.

- Unfortunately, this will happen from time-to-time.

There haven't been any substantial changes to the kernel since mid-August, and what you're seeing is a consequence of the larger size of the JB Virtual Machine, which leads to a larger memory footprint for some things overall. This is the result of the Achilles Heel of our Xooms, the slow EMMC (Flash) device that was chosen, and if the system has to do a number of writes (especially large ones, or small, random ones) the device is waiting for the I/O to complete before it can page in other memory, and in this case the timeout for keeping the password window expires before all the I/O is done. If your system was busy on a background task, or say had several complex web pages loaded, this can happen.

Now, if you see it happening again, if you have the ability plug it into a computer with "adb" and you'll see that it's actually up. (HOWEVER if you discover it's truly hung when you do that, please let me know and send me the last_kmsg!)

---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------

That was really just a co-incidence, and you likely had a transient Network problem. There's no information carried in the Dalvik Cache (and definitely not in the /cache directory) that has anything to do with LTE connectivity. We haven't changed those APKs since late July so there's going to be no change for wiping the Dalvik cache to update.

The system keeps track of the Dalvik and Framework revisions, and if it decides a wipe is necessary, it'll do it on its own. Also, the /cache directory ("Cache") isn't used by the system 99.9% of the time, so that's not going to buy you anything either.
[Xoom Android Development] Mjamocha:
go to your system/app folder ... place the Gallery Google.apk in there

check permissions - should be -( rw-rw-r ) reboot.
[Xoom Android Development] wesamothman:
Guys, if I may step in here to explain how the US LTE capable carriers block the SMS for a provisioned data plan SIM due to my telecom line of work.

First, as opposed to GSM 3g network, that allows SMS to flow if HSS node is not present in the network, LTE setup is totally evolved with more features and speed, etc...

I have explained 3g SMS call flow here,

http://xdaforums.com/showthread.php?p=30467674

For LTE , usually the carriers introduce a technology called IMS (IP multimedia subsystem) which is needed as a core sort of box in their network that in turn includes a sub box called HSS (home subscriber server) where lte users profiles are stored in which SMS is blocked by choice for the data sim of subscriber provisioning . Had this been unblocked, some other tweaks and integration can take place in the network to allow SMS over LTE .

I could go in more details but that is it in short. I hope I made sense explaining.
[Xoom Android Development] Mjamocha:
nope does not compute - speaking foreign techno language, can't understand! Just kidding - :)
[Xoom Android Development] kcrudup:
Ah! That explains the "MotoImsServer" proprietary APK we need for LTE.

We might need your expertise in a little while, as I want to bring in support for another LTE Mini-PCI device soon.
[Xoom Android Development] daryldc1991:
I am sure you are right, but I have always wiped davlik and cache before flashing nightlies until I read on this forum it wasn't necessary unless some major changes were made to the rom. The one time I do not wipe davlik and cache I get intermittent data connection. Should I go back to wiping both as before? Or am I missing something else? I use my Xoom for work everyday so any help is greatly appreciated.
[Xoom Android Development] kcrudup:
I'm sure it was just a co-incidence, and if anything the reboot kicked the OTA connection enough to fix your connection. But I, too, use (and need) my X every day, it's on LTE 80-90% of the day, and I never wipe /cache nor Dalvik.
[Xoom Android Development] Asphyx:
I don't wipe a thing when upgrading to the next nightly and I rarely have any issues that are not known issues of the ROM.

(Which hasn't happened since N132)

I do flash GApps after every new flash though despite the notion that we don't really have to but it goes so quick why not?

I have noticed one or two lockups a few days ago but nothing since. Not a biggie really!
[Xoom Android Development] kcrudup:
Folks, PLEASE let me know when these happen. Also, if you're running any late build (last two weeks from this date), if you think you've got a lockup, wait a few minutes and see if you can power on. If it turns out you can turn it on later, let me know about that, too.
[Xoom Android Development] Asphyx:
Will do, the Two lockups were minutes apartand once I rebooted, since then nothing bad!
[Xoom Android Development] liftman-:
just upgraded from old nightlys - no factory reset.

calendar not syncing.

anyone got a fix?

thxs

Edit

Did a factory reset I'm good

Thanks

edit 2

wow what improvements since the end of july.

i was going to wait till the quick launch was back, glad i didnt wait.

thanks team eos!!!
[Xoom Android Development] bigrushdog:
Sup stranger? Long time no holla! When you gonna put in some work around here lol?
[Xoom Android Development] rlmesq:
http://xdaforums.com/showthread.php?p=29267377
[Xoom Android Development] liftman-:
been a while. my dad passed away in end of june, that and works been crazy. hopefully my head will clear soon.

you guys have been doing a great job!
[Xoom Android Development] Chelseablue:
I just flashed from 137 to 138 and everything seems good except that my browser is shutting on me constantly. As a page loads it will send me back to my home screen. I reopen the browser and the page will reload and then close again. Always after that second time it takes me back to my browser's home page.I'm not getting FC messages or anything either. Its pretty frustrating - especially when I'm typically a long message.

Any idea what could be going on?
[Xoom Android Development] bigdave240:
I am having the exact same issue. Only the stock browser seems to be affected. I attempted to restore from a previous nandroid and the problem was not resolved. Something gets broken and restoring doesnt overwrite it? I was finally able to get back by restoring a nandroid from 134, then in recovery do a factory reset. Then restore the same nandroid and it cleared the problem. I tried to flash 138 again and the problem returned. Not sure if it is related but i noticed that in facebook even without checking the box for Request desktop site it looks like it is doing so anyway? I can tell because the chat box only shows up if that is checked but in this version it shows up without the box checked.
[Xoom Android Development] paulfm:
I haven't had the browser crash in 138 but I have had periods of lag. Sometimes the Xoom becomes unresponsive for 30 - 45 seconds and then comes back. This is the first version that I have seen this lag. It hasn't been bad enough to get me to revert back to a previous version but it is very noticeable.
[Xoom Android Development] bigdave240:
for me 138 ran smooth for a couple of days before this started with the browser. then it was crash, crash, crash. but other than the stock browser seemed to work just fine.
[Xoom Android Development] paulfm:
I had the same with the lag. I didn't have it for a day or so then it kicked in. I use the stock browser a lot with no kick-outs though.
[Xoom Android Development] Asphyx:
kcrudup

Ok had a little rebooting fit last night and it may be related to battery charge as my best guess.

Used the unit quite a bit yesterday and ran the battery down to 25-30% and the unit gave me a charge warning. it eventually shut down on it's own. I rebooted and saw the battery warning so I shut it down for the night till I got home, Restarted it and put it on the dock and noticed 3 or 4 reboots within the first hour. I went to bed, The unit finally locked up around 2:15 AM (The dock clock was stuck at that when I woke up)

Device unresponsive and had to Hold VolUp and Power to get the unit to reboot and all has been fine since then.

You asked for some reports on lockups in regards to memory writes and how long before it comes back but the final lockup didn't come back after 8 hours (2:15 till when I got my lazy ass up! LOL) and I'm guessing that perhaps the available power may have affected those writes to memory (maybe restarting with low battery affected the ram state?)

Just letting you know but everything seems good after that last reboot from lock.
[Xoom Android Development] tomcrown1:
Same for me. I wonder if a code was put in to keep the about:browser code.

Since the debug now stays.
[Xoom Android Development] Schaweet:
I am on build 114 still as my Xoom was neglected unfairly. Trying to get back into the most recent recent version. I've read endless pages and so far i gather i should do a full wipe. What are the most recent gapps? I should be good on the recent radio. Anything else i should know that I missed?

Sent from my EOS LTE JB Xoom.
[Xoom Android Development] airesch:
Use the gapps from the op, there isn't anything newer that will work without having to delete stuff from the system partition after flashing the rom.
[Xoom Android Development] kcrudup:
First- yes, a few days ago we'd turned on "Debug" by default in the Browser because of demand here in the forums about wanting to be able to persistently set the "Desktop" UA. Apparently this is causing some people to have issues, but as all it should be doing is allowing the "Debug" menu to be seen in the "Settings" menu, I'm not sure what's going on here.

For those of you with issues that are using TiBu, can you "Wipe Data" (for just the Browser) and see if this clears up the issue(s)?

Next:

Are you sure this is the first version you've seen this in? I haven't made any significant changes to the kernel (other than fixes for WiFi that come from upstream and are on many other devices as well) in about three weeks.

What were you doing at the time?

A few weeks ago, we turned on "Discard" (AKA "TRIM") for the Data partition. What this does is let the EXT4 filesystem tell the EMMC that it's no longer using certain data blocks, so that the EMMC may mark these internally, the idea being that when the EMMC has to allocate a fresh block (from its pool of erased blocks, as those are the only ones that can be written with fresh data) it won't have to do a time-consuming and lag-creating "Garbage Collection" where it has to move data around to find free space). I now wonder if there's times where if a lot of data has been erased that the EMMC has to dispatch all of these "Discard" operations at once- and any time the EMMC is busy, the device lags (slow internal flash storage is 90% of the reasons why you'll have lagging on Android devices).

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

If by "Build 114" you mean you've been running one of our JB builds, I wouldn't unless you're having issues after the upgrade.
[Xoom Android Development] Schaweet:
Yep I'm on an EOS jb build. I'll flash and see.

Sent from my EOS LTE JB Xoom.
[Xoom Android Development] bigdave240:
i did the Wipe Data and so far its holding good. I'll give it some time and let you know.

Nope. After a few minutes it started crashing again. Debug somehow eating up memory?
[Xoom Android Development] kcrudup:
It shouldn't be- it's just as if you'd turned on Debug by typing "about:debug" in the address field.

Humor me- go into "Setttings->Debug->User Agent", set it to something, then set it to something else, and see if you still get crashes.
[Xoom Android Development] bigdave240:
So far it seems to be working after changing thr ua string as you suggested.

A little more info. When i set it to android it works fine but if i set it to desktop that is when it starts crashing again. Leaving it at android seems to be fine. That may explain why it worked for a couple of days at when 138 first came out. I may have changed it at that point to desktop.
[Xoom Android Development] Mjamocha:
UA Desktop settings work fine here, no problems.
[Xoom Android Development] kcmoney13:
This might have been answered but I read back a few pages and couldn't find anything.

I have been getting terrible battery life. I think most likely its the kernel. But could be wrong. Can anyone let me know what they are running or where I can find it?

Thanks on advance
[Xoom Android Development] mptpro:
Incorrect. Google Voice on the Xoom (for txting and listening to voice mails) works over wifi-only. No data plan needed.

However, on regular phones a data plan is required to use Google voice for calling.
[Xoom Android Development] bigdave240:
Need a lot more info. What version are you running, what version did you upgrade from, have you flashed the radios, when did this start, and finally what do you mean by terrible battery life? Those answers will get you started to find if anything is wrong.
[Xoom Android Development] kcrudup:
As well as a voice plan- GV makes standard phone calls, but they call special incoming numbers that GV then routes to your call (vs. calling your destination directly).
[Xoom Android Development] tjrocks91:
cm10 stringray nightlies blow away the team eos nightlies
[Xoom Android Development] kcrudup:
How nice of them! Don't let the door hit you in the ass on the way out, m'kay?!
[Xoom Android Development] freeky1:
What makes them so much better?
[Xoom Android Development] kcrudup:
... and for an easy way to see this in action, turn on "Show CPU Usage" via "Settings->Developer Options". Along with the load-average numbers at the top, you'll also see a bar with three colors on it:

"Green" bar length is %CPU time spent on Android activities/"Red" bar length is %CPU time spent on kernel activities/"Blue" bar length is %time the system is "Waiting" (for IRQ or I/O)

That last one, the "blue" line is a measure of how long the tablet is waiting on I/O to complete, and its length is a function of how many I/Os are in-progress and watiing to complete. If the "blue" bar is long, your system is going to be laggy and unresponsive. Unfortunately, while we've been making changes to improve the I/O performance, it ultimately comes down to the EMMC Flash chip getting them done fast enough, and that's where our performance bottleneck is.

I finally got rid of my slow-as-sh!t Evo Shift on the (US) Sprint network and replaced it with a Moto Photon Q. No matter what I throw at this phone, it never lags- and that's 'cause its I/O Wait performance is far better, mostly due to it's better kernel and much-improved EMMC Flash chip.

I can't wait for someone to put out a new 10", WAN-enabled tablet- it's so mine!
[Xoom Android Development] sovereign_313:
http://www.engadget.com/2011/11/14/htc-jetstream-review/

Close... But uh... Seriously? Dual core? I personally hate sense too, but.... Close.

Sovereign
[Xoom Android Development] hax0red:
I picked up a used but mint condition 32GB Xoom tonight for $180 with case and I am really pleased. Having owned a Nexus 7 and Galaxy tab 10.1 this tablet has a lot of features and was ahead of it's time at release when compared to other android tablets but it still doesn't quite live up to the iPad 2 software wise it makes up for it in features like sd slot as well as 32GB of storage, flash for rear camera and dual speakers on both sides of the tablet.

Anyways I tried a few roms and the EOS ROM scored 1,300-1,600 higher when comparing other roms overclocked. I was able to easily get 4,534 with EOS Jellybean @ 1.6ghz. The I/O went through the roof with the EOS rom for some reason?
[Xoom Android Development] rockjock2020:
Kcrudup a few pages back you hinted at a mod that would speed things up a little more but would require a full data and user partition wipe. Did I miss the link or are you still working on it? Or did those changes already get implemented into the current kernel?

Thank
[Xoom Android Development] tomcrown1:
Could the mod be the CM10 rom?
[Xoom Android Development] kcrudup:
The necessary code in the kernel and the Android system has actually been in place for a while- I just haven't done the writeup. I will before mid-week.

Everybody's a goddamn comedian this weekend. :rolleyes: CM's Xoom kernel hasn't got many of the improvements I've sweated so many hours on.
[Xoom Android Development] Asphyx:
Tried CM10 it sucked compared to this...
[Xoom Android Development] bigdave240:
Usually the haters come out when you're ahead so take it as praise lol
[Xoom Android Development] kevdliu:
Kenneth put a lot of work into performance improvements so if you think something else is better at least give some constructive feedback.

In which ways is CM faster? app load times? UI interactions? etc
[Xoom Android Development] wesamothman:
Team eos ROM is incomparable with other roms out here. You may find more features somewhere else, maybe... but with the massive performance tweaks, mods, enhancements , efforts, been put into this ROM by team eos makes it number ONE. Not every thing that glitters, shines, is gold...

The maturity of this ROM is unique. Eos mates work it out for fun and to provide all what is best for the community for free. Have we ever thought of supporting them with donations? Appreciation at least means more than money here. You guys are awesome. I am watching the reviews, open, merged mods of what yet to come in this ROM and I have nothing to say better than...
[Xoom Android Development] kcrudup:
This. We might not be perfect, but we're willing to do what we need to, to get there.

That being said, it's still a free country- so use whichever ROM works for you. Just remember though that the people who work on the Xoom ROMs for EOS use this thing every day, and hate when things don't work exactly right and will attempt to make it better.
[Xoom Android Development] Chelseablue:
I don't post to often here unless its to ask a question or something. But I have to say, if you don't like something you should keep your opinions to yourself. And as stated before if you must criticize keep it constructive, trolling doesn't help anything. Team EOS, just as the guys working on CM, do fine work and they should be respected for that.
[Xoom Android Development] mariojp:
Google voice will allow you to send texts and receive texts from your actual cell number. I use it everyday.
[Xoom Android Development] hax0red:
I totally agree with this. EOS ROM was my last choice (I usually try the CM roms first since the code should be more refined, but not lately) due to the options/adjustments mentioned seemed minimal and I always like completely modded roms which this is, but only in ways of performance which I think is ideal for this aging unit that honestly only disappoints in higher end 3D games IMO.

Also, I never comment on roms. Most roms are usually a disappointment in a few ways but so far this has not been one of those times.

Any chance we could get more out of the GPU with another kernel? I'm stable at 1.6ghz(1.7 crashes after a few mins) max right now with the included kernel in this rom.
[Xoom Android Development] kcmoney13:
Thanks for the reply. I am running 138 came from 137. I have been having issues since I upgraded to jelly bean. ICS seemed to be running fine.

I just updated the radio and that didn't seem to do anything. I am not to familiar with kernel or radio updates so if so if someone could link me to what they are using that would be a huge help.

By terrible battery life if mean 2 hours. I even have the airplane mode turned on with just WiFi. Thanks in advance.
[Xoom Android Development] bigdave240:
does your 4g work? I assume it probably doesn't so you have to use Rogue recovery and flash the radios. Other recoveries may not flash correctly! Here is a link to the file you need to flash: http://goo.im/devs/teameos/radios put it on your sd card, boot into recovery and flash. It takes a few minutes to work so be patient. That should fix the battery issue.
[Xoom Android Development] bigrushdog:
I'm gonna chime in here just to bury any nonsense. Me and steady and TDR, the cm maintainers, are friends and go back longer than most of you have been around. The aosp community would not exist as it does today without pioneers like cyanogen, koush, and others. All of us are indebted to them. We have nothing but love for cyanogenmod, aokp and others. We, as TeamEos developers and users must not be distracted by flamers, trolls, and other human subspecies who would wish to divide us. We are all really one community.

This matter is considered squashed.

/end public service announcement
[Xoom Android Development] Mjamocha:
Thank you-Yes, I know. You Missed the point. We were discussing native Sms function with out ...never mind.
[Xoom Android Development] JoshWithrow:
I'm on 138 and keep getting FCS in he browser. Can I provide anything to help with the diagnosis?
[Xoom Android Development] Chelseablue:
I've found that setting the UA String to iPad gives me desktop sites (most of the time) and no FCs
[Xoom Android Development] tomcrown1:
I was not being funny. I was wondering if the new Mod you had mention was CM 10 since I know you and the other mods work together.

If I remember correctly you had posted that you had something new comming out and would post it soon.
[Xoom Android Development] JoshWithrow:
Sweet Jeebus that did the trick!