yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Kingsman1:
The reason why Omnirom wasn't upgraded after August 6 has to be because they were waiting for imminent releases of Android L. Yesterday Android Lollipop was released as a developer option. It will take a few more days to have the kinks worked out for release as a stable version to the primary Google sponsored devices. Once we see that, it should not take much time before Omnirom, CM, Schischu, Run and Hide, Team EOS or someone decides to work on it and get it ported over to us.

In the meantime, Omnirom doesn't crash on me except when I use the Chrome Browser. It will, however, tend to shut down completely after about 25 minutes (That's about the length of time it takes me to go from home to Church) from the time I turn the screen display off. Rarely, it will require a hard reset (power+ volume up). For the most part, this is the nicest, smoothest, most full featured Rom I've used on an Android tablet. It can, though, have some significant junk build up, so that I will use "Cache Master" to clear the junk once a day and sho a boost on other junk a couple of times a day to keep the system from lagging.

As it is,I really like Omnirom's Android 4.4.4
[Xoom Android Development] Gordon1M:
Thanks for the information, kingsman1.

Usually, but not always, freezing occurs after my Xoom has gone to sleep after it hasn't been used for a while. It won't "wake up". There are other issues as well. Sometimes I get the message that "Clock has stopped" and, occasionally when booting, there is a message about a problem with the launcher. Very slow loading of the stock browser seems to have been cured by using a cache cleaner. I have been using App Cache Cleaner. I have been unable to find Cache Master in the Play Store, that you have referred to.

Gordon
[Xoom Android Development] Cameron581:
Its going to be a month or more and it wasnt released it was announced. The code won't be out for a long time
[Xoom Android Development] Kingsman1:
Thanks so much Cameron.
[Xoom Android Development] Schischu:
Why no update? Well its pretty simple, I am running cm11 on my xoom as netflix does not work with omni on xoom.And I don't want to push OTA updates blindly without testing them.

So what we could do is that I will upload an update here, someone can test it and if it works it will be pushed as OTA.

Sound good?
[Xoom Android Development] taninos:
Netflix is a must have. It hasn't sense a rom without a workable DRM.
[Xoom Android Development] hochoch:
Have you guys tried upping the minimum clock speed? At least one, if not two levels. That seems to work best but it's not fool proof. I'm using trickstermod for this. Also make sure you're running the OC version of elemental x kernel, version 2.1.
[Xoom Android Development] chykal:
What about Netflix isn't working for you. It works for me on Omni right now.
[Xoom Android Development] slow1234:
Thanks for the suggestions...

I have tried min clock speed at 312 and 456, with the issue persisting. On the weekend I reinstalled the ROM and cleared out some unused apps. We'll see how that goes. I'll also try the 2.1 kernel if things haven't cleared up.
[Xoom Android Development] Gordon1M:
I have also tried the minimum clock speed at 312 and 456MHz but the problem continues.

My kernel version is showing as:

2.6.39.4-ElementalX-Xoom-2.0+

ubuntu@ubuntu-i8 #1

Wed Aug 6 18:18:58 CEST 2014​

Maybe I need to update the kernel, but I am not sure that I know how to do this.

Thank you

Gordon
[Xoom Android Development] hochoch:
i think there's just an issue with these things and it's something we have to live with unfortunately. upping the clock speed should help and you can find the newer kernel in the OP here:

http://xdaforums.com/showthread.php?t=2144360

just boot into TWRP, click install then locate the zip file. i would clear your dalvik/cache after installing as well.

i recommend TEAM EOS rom over this though as it has more active development.
[Xoom Android Development] slow1234:
The funny thing is, I came back to OMNI because I was getting too many SOD's with EOS! Now that SODs have been cropping up in the last few weeks on OMNI (even though I haven't done any ROM installs since I came back to OMNI), I may go back to EOS!

Historically when I've switched ROMs it has been due to new versions of Android. If I am staying with a 4.4.4 ROM do I need to wipe the data partition if I'm switching between OMNI and EOS?
[Xoom Android Development] hochoch:
Lol - I've tried all the 4.4.4 ones and the occasional SOD's are just something we as the xoom loyalists will have to live with I think. You can just do a standard factory reset/wipe then install EOS, no need to wipe your partition.
[Xoom Android Development] Kingsman1:
Sorry, I meant Clean Master

---------- Post added at 02:12 PM ---------- Previous post was at 02:01 PM ----------

Thank You Schischu, I'm really glad to hear from you. Unfortunately for this particular issue, I have never used Netflix, rather opting for Xfinity's film rental services.

---------- Post added at 02:56 PM ---------- Previous post was at 02:12 PM ----------

Hi Gordon,

This latest kernel is the one in Omnirom's August 6 release. I've not noted any issues with it,

The minimum CPU speed of 216 seems to work well, but I've had absolutely no problems upping the maximum CPU speed to 1600.

By the way, be sure to get the latest version of PA_GAPPS 4.4.4 stock, and upgrade to the latest version of Superuser 2.13.

Blessings,

Rob
[Xoom Android Development] rodspi:
My freezing issue gone for over a week after...

I had freezing issue multiple times a day until I rebooted into twrp recovery (external SD card removed) and wipe everything except the system partition. I rebooted gave the rom 10-15 minutes to settle, before I did any of the first boot setup. I set the cpu to 1504 max and 456 min for good measure. I really stalled my apps manually and restored selected apps data from backup files from external storage.
[Xoom Android Development] slow1234:
Since starting with a fresh OMNI reinstall (factory reset/system/data/cache/dalvik wipe) and installing the flar 2.1 kernel, my frequency of SODs has dropped way down, which I'm happy about. Since I did both processes at once, I don't know whether it has been the fresh install or the new kernel which has fixed things.
[Xoom Android Development] tnfsmith:
Superuser is now 2.16

Sent from Tapatalk MZ601 - TeamEOS 4.4.4 Kitkat nightlies
[Xoom Android Development] sdthelord:
Same
[Xoom Android Development] tnfsmith:
TeamEOS not rather than situation, my Xoom MZ601 free went deep sleep sometime. Just not find out why. I am on everest version
[Xoom Android Development] mmidgley:
I've been running a 4.2.2 CM rom on my two wingrays for many months. Today I decided to try a 4.4.4 rom and I chose Omni (came up first in google "xda xoom kitkat"; I may want to try a team eos rom on my other xoom). I have no experience with Omni or TWRP. Either I'm out of touch, or the instructions at the start of the thread leave out a few steps dealing with TRWP: I had trouble getting the Wipes to work, mostly with Cache. Was I required to mount cache? (kept getting errors regarding cache wipe) Besides cache, wipes did work if I did them one at a time--but finally I had to use the Format option to get Cache to be cleared. Then at first boot I was too impatient and a few minutes into it restarted which I think lead to the decryption error. More wipes and reboots and patience and now its up.

Of all that I use I noticed:

Google Maps [latest version] opens for a few seconds and then FCs (tried clearing app's data), while the one in PA_Gapps modular mini runs fine.

Choosing Performance settings causes Settings to FC. (wanted to play with overclocking)

Is this just how it is, or am I doing something wrong?

thanks,

m.
[Xoom Android Development] huanhoho:
Forget this post. The problem is now solved and had nothing with the ROM. ;)

Please DELETE the post.
[Xoom Android Development] Mr_IceSlice:
Do I need to fix this, or switch ROMs?

Hey guys,

I've had this ROM since my last post on this thread (about a month, I think) and for the most part, it seems to be doing great. But, there are some issues. Below I list my issues; I have some options: (A) Get help from y'all. (B) Switch to a different ROM.

1. Overclock isn't working. But underclock does work. When in the performance menu is settings, I set the overclock to 1400, and the clock speed does go up to 1400, but the either just a few seconds later or 45 second later, my Xoom reboots. But its not a full reboot, it skips the red 'Dual Core' screen a proceeds with the OMNI boot screen. Once booted, the clock speed has been reset to 1000. If the 'apply on boot' option has been enabled, my Xoom will reboot over and over. :/ I'm not sure what is causing this, any insight on this would be nice. I really want that overclock.

2. Toggleable values in setting don't always hold their values. WiFi behaves normally, but bluetooth turns itself on, location access turn itself off, and input method keeps defaulting to AOSP, even though I keep choosing Google Keyboard.

3. Reboots and freezes. Given, this doesn't happen too often, it seems to happen once a week at least. And it seems that everything gets laggy before a reboot.

So these are my issues. If it's as simple as a kernel, great. But whatever the problem your support is highly regarded. ;)

Now on to the next order of business:

Is this even the best ROM/right ROM for me??

This is my first ROM to ever run, mainly because I'm a stock lover, but 4.1.2 just wasn't cutting it for me. So I found this video and I got the ROM. But there is also TeamEOS's 4.4.4 ROM, and CyanogenMod's 4.4.4 ROM. It looks like someone from every ROM has worked with someone else from every other ROM, which makes it hard to choose which is the best. TeamEOS boast of stability and regular updates, OMNI hasn't had a single update in the time I've had it, and AFAIK CyanogenMod has a much larger team of developers yet in their post they brag on nothing.

Simply put, do I fix the ROM I have now (OMNI), or do I get a different ROM? And if so, which one??

Thanks for not tl;dr-ing this.

#MotoFTW
[Xoom Android Development] bschmidy10:
I went thru the same thing you are now... Tried them all for an extended period of time. I like unofficial cm11 the best... Omni could be the best if it were updated frequently and eos is great too but seems to be unstable sometimes and doesn't perform as well for me. Cm11 is updated about once a month and they are working on cm12 for it now :)
[Xoom Android Development] jeffjaslow:
I cannot get Google Maps 9.1.0 to work.

Tried to uninstall, clear Cache and Davlik Cache, install update clear cache and Davlik cache, reboot...no luck. Tried clearing mock location in developer options.

Google maps still crashes.

Uninstall updates and all works fine.

Thanks for any help.
[Xoom Android Development] dsbnz:
Its not working on my cm 10.1 wingray either. However i also noticed the v9 update was pulled from Play Store (it now shows v8.4.1 as latest available version, with no update pending). Could be issues with v9 on devices/roms prior to android 5?
[Xoom Android Development] Schischu:
I'm currently uploading a new version "omni-4.4.4-20141130-1704+0100-xxx-HOMEMADE.zip" for all devices.

I just tested it on my wingray and all looks good.

Wingray is already online. The other will follow in the next hours.

This will probably be the last version for omni-4.4.4 as the new development focus will be on getting lollipop running.

Statistic (ROM | Downloads):
omni-4.4.4-20140806-1812+0200-wingray-HOMEMADE.zip 12712
omni-4.4.4-20140806-1836+0200-everest-HOMEMADE.zip 6982
omni-4.4.4-20140806-1857+0200-stingray-HOMEMADE.zip 2017
omni-4.4.4-20140806-1920+0200-stingray_cdma-HOMEMADE.zip 1357
[Xoom Android Development] slow1234:
Thanks for all your effort on the Xoom - I have very much appreciated it!

I'm not sure if it has been a placebo effect, but this 20141130 version feels a whole bunch smoother and zippier!
[Xoom Android Development] ro.chi:
Google Maps V9 crash: clear Apps data and cache, disable satelite view and now work...
[Xoom Android Development] slow1234:
Since you mentioned this, I tried out Google Maps for the first time since updating this ROM. V9.1 does indeed crash. HOwever, for me clearing the app data and cache do not seem to resolve the issue. :( I am going to try uninstalling it and reinstalling from Play Store as opposed to via the most recent PAGapps Modular Full package.
[Xoom Android Development] jeffjaslow:
Google maps 9.2.0 works?
[Xoom Android Development] Gordon1M:
Google Maps v9.1.1 is also crashing for me after updating to the latest Omni ROM. This happens as soon as I try to zoom to street level. I have tried reinstalling Maps and clearing data but that doesn't help.
[Xoom Android Development] slow1234:
Looks like folks with the 4.4.4 cyanogen Xoom ROM are in the same boat. In that thread, people are suggesting going back to PAGapps package from the end of October to get an older Maps version.

Maps updated to 9.1.1 for me last night and still issues too.

EDIT: 9.1.2 also broken. I will use MapQuest or Waze instead.
[Xoom Android Development] buffal0b1ll:
Old maps apks here http://www.apkmirror.com/apk/google-inc/maps/
[Xoom Android Development] Gordon1M:
Maps 8.4.1 seems to work fine for me (thanks buffal0b1ll). I had hoped that the new ROM might provide some improvement with regard to the tablet becoming totally unresponsive once or twice a day (requiring a Vol-up/Power on reboot) but it's no better. Maybe this problem has nothing to do with the ROM. I still see the "Clock has stopped" message on boot and something that I have not seen before is "Google calendar sync has stopped working". This appears from time to time.
[Xoom Android Development] brewer75:
I use TeamEOS latest 4.4.4 builds and also had problems with the Google Map updates. Supposedly it has to do with Lollipop readiness but I have a Verizon Galaxy S3 running stock 4.4.2 and it has handled the map updates with absolutely no problems. At this point in time, it seems we need to be happy with the 8.4.1 version!
[Xoom Android Development] digitalnerd:
Hi All

Getting ready to wipe and reload my WiFi Motorola Xoom with this ROM. Couple of questions before I do.

The instructions say to use to R.A.H._TWRPv2.6.3_BigPart_selinux.zip but I see TWRPv2.8.1.0-Wingray-BigPart.zip was just recently released. Should I use that instead?

Recent posts indicate there is an issue with Google Maps, what is the latest recommended Gapps download I should use?

I assume these are the latest and greatest :

omni-4.4.X-201XXXXX-wingray-HOMEMADE_XXXX.zip

UPDATE-SuperSU-v1.86.zip

BigPart is something new to me but I assume my device supports it. Need to read up on it more but as I understand it applies to partitions. Anyone care to enlighten me?

Looking forward to putting the mighty Xoom back to work!
[Xoom Android Development] slow1234:
The latest OMNI can be found in the first post of this thread.

TWRP 2.8.1.0 bigpart will work.

The latest SuperSU can be found as a flashable zip at: http://xdaforums.com/showthread.php?t=1538053

I use the latest Full Modular PAGapps package, the latest of which can be found at: http://xdaforums.com/showthread.php?t=2397942

This package works fine with the exception of Google Maps which you'll need to downgrade to v8.4.1 to get to work on the Xoom. Chrome also has issues on the Xoom with custom 4.4.4 ROMS. The last version of Chrome that worked reliably for me was v33. I'm sure archived apks of both these apps can be found somewhere.
[Xoom Android Development] ro.chi:
Maps 9.2.0 seems to work fine for me
[Xoom Android Development] slow1234:
That would be great if 9.2 is working. Where did you find that version? My Play Store only shows version 9.1.2.
[Xoom Android Development] digitalnerd:
Thanks for the info!

Accidently downloaded the stock instead of modular gapps package. Other than that doofus move everything is looking great so far!

Previous APKs can be found here [Thanks buffal0b1ll!]

http://xdaforums.com/showpost.php?p=57291642&postcount=1134

Although ro.chi says Maps 9.2.0 is working for him/her.

psst, over here ---> http://www.apkmirror.com/apk/google-inc/maps/
[Xoom Android Development] slow1234:
Thanks!
[Xoom Android Development] brewer75:
I just downloaded Google Maps v9.2.0 from the Play Store and it does seem to be working fine on my 4.4.4 Wingray! :good:
[Xoom Android Development] da-pharoah:
Two questions I have:

One, how do go about changing the softnav buttons to be on the lower left side of the xoom versus the middle. I cant find the option for that if there even is one.

And 2, anyone able to get bike rivals working on this rom? Its fc's on me and I havent looked at the log yet, but just curious
[Xoom Android Development] Obsy:
I will answer only to first questions because I don't play games on phone/tablet. Since KitKat (Android 4.4) softnav buttons remains on center and you cannot change... It's in Google's API. It also discussed this issue in the past.
[Xoom Android Development] da-pharoah:
Sorry then I must have missed it. Well ok then ill have to reflash team eos and see what the option is. I know its on that rom.
[Xoom Android Development] huey1945:
[ROM][4.4.4] OmniROM-Wingray UK Wifi

Hi Guys

I just flashed to above following the guide, all seemed to go well till after re-boot

then I got Omni splash screen up, with colour changes, now I have a steady Omni logo

on with eyes blinking from time to time, but has been like that for over 20 mins or so

Not sure if something is broken or not, advice or guidance needed ??

Much appreciated..

P.S im running Original Xoom 10.1" Wifi U.K model which previously I had on JB 4.2.2

nightly build 202..
[Xoom Android Development] hochoch:
I'm running the cm11 big part and am able to use an xposed module called tabletkat which brings back the old style layout with the nav buttons on the left. I had ui force closes using it on other Roms tho so your milage may vary.
[Xoom Android Development] Obsy:
Good to know this. Unfortunately I use ART which doesn't like Xposed or vice-verse... I have used with this and mostly my wife use the tablet which doesn't care . Anyway thanks!
[Xoom Android Development] charos:
Which Omni version is the most stable (most lag free) ?

Been switching Omni,Eos4 ,cm11 for a year now and all roms after a month or so get way too laggy to be usable . I'm even thinking of going back to honeycomb official and see the performance ! I
[Xoom Android Development] da-pharoah:
So quick question, do you do any cpu min/max changes? Or even change the governor?
[Xoom Android Development] charos:
Yes, I tried a few different combinations. Currently is set 1Ghz min and 1.4 max with performance and row. A bit more responsive but still annoying!
[Xoom Android Development] da-pharoah:
Lol thats awesome. I havent yet had a min at that level on the xoom. I always had it on demand to be at max supported value per the kernel. Sounds like your kinda spoiled and im kinda jealous... :)
[Xoom Android Development] charos:
Lol! I'm trying again from scratch with Omni and default settings. Let's see what nonsense settings I'll end up using soon!
[Xoom Android Development] :
I flashed the supersu zip from the link in the OP and don't see it after rebooting in the settings menu. It was working fine before I did the latest OTA. Anyone have any ideas?

EDIT: Reflashed the OTA and SuperSU in the same session. Rebooted, installed SuperSU, and was good to go!
[Xoom Android Development] Kingsman1:
Have you tried using Clean Master? This controls junk buildup, laginess, overheating, etcetera. It gives notice of what you need to do to keep your tablet running swiftly. I'll take the time to run it twice a day.
[Xoom Android Development] :
You need to do three things to make sure that your Xoom stays usable. You need to overclock it to 1.6 GHz, make sure that TRIM runs as frequently as possible, and that you keep as much internal storage free as possible.

These devices use incredibly old flash storage which hasn't been aging well. It's one of the main reasons why old Android phones are so "slow" nowadays. TRIM makes sure that you're always writing to the fastest storage left in the device's memory. And keeping as much storage free as possible makes sure that the best and fastest storage is always available to use for temporary things like cache.
[Xoom Android Development] Kingsman1:
Just a couple of other things you can do. Not only run the CPU at 1.6 GHz max, but also at 216 GHz min. Then go into developer options and all three animation options need to be set at .25 to .3. This will give you very much improved performance characteristics.
[Xoom Android Development] xyz_969:
Do we need to do anything special for this?

By reading up on the topic, on some web sites it was claimed that TRIM should be working properly in Android 4.3 and above (by the operating system) so if that's true, then in 4.4.4 there is no need to do anything. Is that correct, or is a separate activity / app (like LagFix) needed for this?
[Xoom Android Development] :
35%+ battery while charging without being touched for one hour

85%+ battery while off charger without being touched for one hour

You should NOT need an app for this. But there ARE specific triggers to make sure it runs.
[Xoom Android Development] xyz_969:
And these are... ? :)

(I mean, specific settings or...)
[Xoom Android Development] :
I just listed them in my last reply...
[Xoom Android Development] haybill:
Love the ROM--any way to change the Boot Animation?
[Xoom Android Development] matt4321:
Yeah, grab a new animation, the one you want, then throw it in /system/media/ and rename to bootanimation.zip
[Xoom Android Development] haybill:
Thanks Matt, will have a go.
[Xoom Android Development] ifti_a:
Hi

Is this ROM still being updated ?

Thanks
[Xoom Android Development] PirateGorilla:
E: can't mount /cache

Can anyone help?

Seems like a common issue but no solution, if you can point me to the right direction I would really appreciate it.
[Xoom Android Development] BobbaLouie:
That happened to me when I didn't follow the partitioning instructions to the letter.
[Xoom Android Development] Kingsman1:
Try running Clean Master or Lagfix. I run Clean Master once a day and the Old Xoom still runs very fast.
[Xoom Android Development] diffstyle:
mount issue

Hey guys, I have been trying to get this to work all day. I installed TWRP BigPart and am able to successful boot into it. Once in there I

1. Flash the BigPart TWRP from SD Card

2. Without rebooting go to "wipe" and select everything but SD. Then i get an error saying FAILED because it is unable to /mount data, cache and all the other ones selected.

I just can't seem to figure out what step i'm missing or doing wrong. Has anyone encountered this and figured it out?

If i just go ahead and flash, it gets stuck on the boot animation.
[Xoom Android Development] atimus:
I think after 1 you need to "format data", then reboot to recovery and make 2.
[Xoom Android Development] deanr1977:
im also stuck on boot? been waiting about 10mins now.... how long till i should reboot back into recovery & reflash?

No worries ive reflashed & seams fine now
[Xoom Android Development] slab100:
broke it!

this thread probably not looked at any longer, but thought i would dust off the old xoom and see if i could install a rom to sppeed up the old bugger and would appreciate any help

installed TWRP v2.6.3 bigpart

completely wiped the internal storage dalvic cache etc,

tried to install omni-4.4.4-20141130-1704+0100-wingray-HOMEMADE (as have wifi edition, and checked md5sum) but got below error

E: error executing updater binary in zip

error flashing zip

updating partition details...

then a big red FAILED

so now cant do anything

anyone any ideas?

thanks
[Xoom Android Development] shpitz461:
That TWRP is old, try with latest...
[Xoom Android Development] Schischu:
Cooming soon to you Xoom: :o
[Xoom Android Development] matt4321:
Awesome!!!

Did you solve the boot image problem?
[Xoom Android Development] shpitz461:
WOW Schischu!

I thought you're incredible with 4.4.x, but this one takes the cake!!!

One question though: Is there a reason you use EX 2.0 and not 2.1?